Print

[whitey76]

Not bitching, but just wondering if anyone has had a problem with the dumps taking forever with this program. I have used nandpro many times, and it usually takes about 35 to 40 mins to dump the nand. This program automaticly dumps twice, and it's taken over 2hrs. I was just checking the program out to see how it worked, and its pretty nice, but I'm not sure about the extra long time it takes. (IMG:style_emoticons/default/unsure.gif)

[HeenHill]

Been trying it out and seems like a good program. Uses 100% CPU though

[tense_lion]

i only wish i had this last week. if for some reason i have to jtag another system i will, without a shadow of a doubt use this.

[Yacker]

Sounds like this just reads the entire nand.  Would be nice if there was an option to read only like first 2MB and then does the work to write xellous to the board so I can flash the rest of the nand with the 360.  Otherwise this takes a long time huh?

[BadBloke]

QUOTE(sektor1062 @ Apr 9 2010, 05:17 AM)

Yeah, but does it work on my up-to-date console yet?
Yeah and thanks etc, you're the love of my life.

Just to further spoon-feed :

Please understand that this application is NOT a hack, let alone a new one.
It is merely a GUI that is used to automate the process of nand editing (and make it quicker).
So the JTAG hack stays the same, and NO, consoles with kernel > 7371 will NOT be exploited.

That's why I threw in a CB Autodetection routine in the first place. Because it has to be exploitable.

QUOTE(ydgmms @ Apr 9 2010, 06:58 AM)

can i use a Xellous XBR with this? Like if I throw in the Xellous section into the XBR bins will youre program work, or does it do some CRC checking to find the 'right' XBR for the detected motherboard?

I like Xellous over Xell. Why? I dont know, really. But it made dumping/writing the BB easier.

ooh yeah; does it auto fix bad blocks too?

Well it does not do any CRC checking, just checks the filename.That said I have NOT tested using it with Xellous XBR, but once you get XBR up and running, installing Flash360 and updating to Xellous is already too easy

AutoHacker ignores bad blocks. The reason is that the controller reallocates them automatically upon writing the NAND. I have never ever seen an xbox fail due to bad blocks.

QUOTE(whitey76 @ Apr 9 2010, 09:08 AM)

Not bitching, but just wondering if anyone has had a problem with the dumps taking forever with this program. I have used nandpro many times, and it usually takes about 35 to 40 mins to dump the nand. This program automaticly dumps twice, and it's taken over 2hrs. I was just checking the program out to see how it worked, and its pretty nice, but I'm not sure about the extra long time it takes.

I am wondering about this too. There shouldn't be the slightest of deceleration of the process.
No-one ever noticed anything like that during the tests... If there is anyone else who is experiencing this let me know.

QUOTE(HeenHill @ Apr 9 2010, 10:04 AM)

Been trying it out and seems like a good program. Uses 100% CPU though

Shouldn't use 100%, not even on a fairly old PC. That said, it is FAR from optimized, and it IS a CPU-hungry app, mostly due to the use of the SDL library and the high level of the compiler. Working on it, but don't expect miracles unless I rewrite the whole thing on a lower-level (version 3 maybe, but not soon at all).
It uses 50% on my Intel Atom (netbook) and less than 40% on my Athlon 3200+.

QUOTE(Yacker @ Apr 9 2010, 08:19 PM)

Sounds like this just reads the entire nand.  Would be nice if there was an option to read only like first 2MB and then does the work to write xellous to the board so I can flash the rest of the nand with the 360.  Otherwise this takes a long time huh?

Well, there is an option called "Read Bootloader" which reads from block 0 to 1000 on a BB Jasper. That means the first 4096 blocks, which is 64MB. Pretty better than 256 or 512 MB, and still VERY safe and simple. What you are describing is an advanced method that is mostly used by people who do this very often, and are familiar with the process. Implementing such a feature would defeat the purpose, because if someone does this so often, he should just get/build a USB spi flasher.

The whole point of this app is to enable users who would just flash their own console do the JTAG hack (one-off jtagging, so they should be patient which is the price for not reading enough to do the Xellous method ) if someone is so familiar with this process, I don't see why they should use AutoHacker.

There are, of course, exceptions which would be a "professional" which hacks a lot of consoles. Such people are using USB and when combined with AutoHacker, the amount of time needed for a full "Read/Read/Compare/Patch/Write" cycle is 10 minutes for 16MB NANDs and 30 minutes for BB Jaspers, which is ridiculously fast.

That said, if this becomes a much-requested feature, I will try to implement it.  

[rami1]

Very informative tool, thanks!  

[rami1]

Liked the Commodore logo, remind me of some good things from the past...
The commodore had many great games, and I also remember the time I spent on cracking games using machine code/assembly.

This post has been edited by rami1: Apr 9 2010, 11:03 PM

[reddwarf]

QUOTE(deilzfcjk @ Apr 8 2010, 05:52 PM)

talk about spoon feeding. Thats all there is to it. Now people will not do research.  It's beginning to be too simple. I rmember in December. I was rewriting my bad blocks using winhex. and omg. I almost bricked my 360. But ,i knew what I was doing.
Nand pro was still in it's infancy. I kept getting error on my ghetto rigged LPT dumper. I got it done in about 2-3 days. I freakin hate hex. I used nandcompare and I forgot everything by now. Thanks for the good work guys.

Look I have done this many times, but anything that simplifies a task is benefit.  It may also bring more people in as they ask themselves "so how does this work".  Don't make the assumption it kills research.

[cabb360]

Great work on the program works great used it on 2 xenon and works like a charm. So I was google to use this app on a Jasper 512 with 6723 cb which should be exploitibla but the program says cb is not exploitible so Ima little confused now is Jasper cb6723 exploitable or not I haven't had the pleasure of jtaging one yet till this one I have.  So before I go is this cb version good .  Thanks guys

[ZprivateZ]

Jasper Arcade (256/512): 6723 or lower is Exploitable

[sonic88]

QUOTE(cabb360 @ Apr 10 2010, 06:29 PM)

Great work on the program works great used it on 2 xenon and works like a charm. So I was google to use this app on a Jasper 512 with 6723 cb which should be exploitibla but the program says cb is not exploitible so Ima little confused now is Jasper cb6723 exploitable or not I haven't had the pleasure of jtaging one yet till this one I have.  So before I go is this cb version good .  Thanks guys

The program warns me about my CB6723 also, its a jasper 512.
Thx for a great flash/hack tool that will save ppl a lot of time. (IMG:style_emoticons/default/smile.gif)

[gamesquest1]

im getting that too, was happy to see this, making peoples lives easier then booooooooooom (slight exageration) 6723 not exploitable, is there some unexploitable 6723 cb ive not heared of coz this program has got me worried now dont wanna dump all this for no reason, hopefully its a mistake on the programmers side, probs still gonna do the dump like but ill be soooo pissed if there is a unexploitable 6723 that ive not heared off and that there is no mention of else where apart from this program

This post has been edited by gamesquest1: Apr 10 2010, 11:45 PM

[BadBloke]

Don't worry guys, it is just a bug that is worth 2 bytes. Unfortunately it makes all the difference. Anyways, 6723 is, of course, still exploitable and  I have already compiled the corrected version, will probably upload AutoHacker 2.1 tomorrow, featuring:

 - Fixed bug where 6723 reports as "not exploitable" .
 - Added self-check upon startup (check that all necessary files are in place - better safe than sorry).
 - Probably if it doesn't find exctracted .bin files in the XBR folder, it searches for the packed ones (.zip and .rar) and if found automatically extracts them - of course this happens only the first time - something like a quick installation procedure. Currently beta-testing this.

Later updates will definitely include much more optimized code and a slicker GUI, but I'm in a rush to get the 6723 bug patched, so for now, no GUI updates or optimizations.

This post has been edited by BadBloke: Apr 11 2010, 02:59 AM

[danthaman673]

I don't think using this app is a good idea untill it addresses the issue of bad blocks, Otherwise you could easily end-up bricking console (as about 20-30% of consoles I've seen have bad blocks) Also it is possible to have two matching dumps that are both bad and have dumped in exactly the same (bad)way. I recomend 3 and checking against a known good to make sure only the areas that are meant to be different are.

 Otherwise keep-up the good work bad bloke ur GUI is almost release-worthy. Perhaps give people more control over dumping.

PS: CONTRARY TO RUMOURS THERE ARE SOME KERNALS POST 7371 THAT ARE EXPLOITABLE!!! (QUITE A FEW ACTUALLY!!) YES I HAVE DONE A COUPLE BEFORE IT'S JUST THAT WE RECOMEND YOU UPDATE TO 7371 1ST (IT'S NOT BECAUSE IT'S THE LATEST EXPLOITABLE KERNAL) CD/CB IS BETTER INDICATOR anyway , I really think if you have these skills then you should put them to better use than 'Spoon Feeding'    Why not make the app for the ppl who do a lot of JTAG dumps (At the moment we use scripts, We always do at least 4 dumps) We could sure use the help. If average every-day ppl can't use the miriad of noob-friendly stuff that's already out there then they probably shouldn't be doing it themselves.   ( when they inevitably stuff it up they bring it to guys like us to pickup the pieces )
 If you are interested in helping to develop this into a pro app (like the JTAG equiv of jungleflasher) then drop us a line  
PPPS: You guys have prolly just been lucky u haven't bricked any consoles yet (If the bad blocks are in some/most places it won't matter that much)


 

[BigSteel]

I just used this on a Falcon and it worked perfect.  Super simple...thanks.