Print

[danthaman673]

QUOTE(DT778 @ Aug 9 2010, 06:13 PM)

I plan on using this to fix the corrupted saves on my modded system's hard drive but the 360 has the e74 error. Will I still be able to fix the save files or do I have to get the system working again?

You should be able to fix saves without needing the console functioning as they are stored on disk/mem unit. You  might want to use a different KV when u resign.

Brgds/Dan

PS: I've had a dig around for the .bat files and the full versions are alluding me (we usually manually add file names and use various different versions depending on the situtaion where we're usually hurried, so the full version that includes the scripted/audio file names, the compare AND the audio seems to have gone walkabout..) I may have to give u a more basic version if the others can't be found.

[DARKFiB3R]

CODE

XNand Healer GUI v0.51 by Tingedace

------- nand1.bin --------
NandPro v2.0b by Tiros

Looking for usb interface device
FlashConfig:008A3020
256MB Nand Detected
Starting Block:0x000000
Ending   Block:0x000FFF
Configured for Large Block Nand
Reading
0FFF

------- nand2.bin --------
NandPro v2.0b by Tiros

Looking for usb interface device
Incompatible ARM hardware for this version of NandPro!
Can not continue


Press any key to continue . . .

Not enough time in between reads?

[ImRickJamesB1tch]

DARKFiB3R I experienced that once or twice with 2b. I then made the upgrade to version 2e and have done about 30 dumps (dump 1 consoles nand about 8 times for testing) and have not had that again. Definitely think it was a version b issue.

Try upgrade to 2e and see if that resolves that issue.

[DT778]

Having trouble with this program.

When I select read nand it goes to the command window and I get
"'C:\Documents' is not recognized as an internal or external command, operable program or batch file.

Have the settings pointing to the correct folders with the nand 2.0b and findsec 0.62 exe files.
Net Framework 3.5
Windows XP

Have the system connected via LPT and this is what shows up in NAND Connection Status on the top of the main program window
Device Address: 0378
NAND Type: Pre-Jasper
Flash Config: 01198010
Block Range: 0x000 -> 0x3FF

Tried using nand 2.0e as well as the 0.4 version of this program and still got the same problem.

[ImRickJamesB1tch]

DT778 as stated in one of my previous posts, this is a bug.

If you have your nandpro in a directory with spaces, it will throw that error. Move your NandPro folder to the root of your c drive so it looks like this C:\NandPro. Change your path in Xnand Healer and try again...

[DT778]

Thanks again, put it in a folder with no spaces and it worked.

Writing the nand after you uncripple it should only take a second right? If so then I've uncrippled the drive yet it still shows as corrupted when I connect it to a clean 360. Since the modded 360 has the e74 error I'm guessing I need to get that system working so the xbox can send the info to the hard drive to uncorrupt the files on there. What do you guys think?