QUOTE(Textbook @ Sep 27 2006, 02:53 PM)
eXOBeX, I thought of a good "check" for X360SAM. I've already talked to one person who somehow had a bad original dump of the firmware (all FF's) but was the correct size, so the process continued and it ended up putting FF FF FF FF FF FF FF FF into his xtreme firmware and flashing his drive. No good firmware backup, no more DVD drive in that 360.
A good check would be to check the key range area and make sure it isn't all FF's or 00's. flash78 had a program called keygen.exe that was basically like KDX from DOS, just printed out the drive key on screen.
This is so true, 2 VERY important things that you MUST to do BEFORE you EVER patch or modify your orig.bin is to verify the filesize and then VERIFY the file has a valid key.
I know someone who also bricked his drive because his extracted orig.bin was only 48k. Assuming that all files should be 256k, If X360SAM could verify the filesize and abort before patching, i think alot of bricked drives could be saved. Maybe there is a dos command we can just add to the existing batch files to check for this.
I also like the keygen.exe v0.46 app becuase it displays the key in dos and dumps it to a text file. But the file has a dpmi problem when run outside of XP and is useless on a bootdisk. But it does show the same key as the current tools like 360FWToolbox. If X360SAM could display the key and then prompt to continue or
abort would be perfect.
If anyone knows how to get the dpmi working on a boot disk, please show the configuation and what files are needed. I download the files but it still didnt work right for me.
I'm not bad mouthing X360SAM, i think its a great tool. I just think these 2 features can make it an even better tool. I know you could still have a 256k file and be shown a bad key, but at least the user might have a chance to save the drive from becoming a brick.