restore hdd game install after ban with nand backup?

[gesatec]

thanks...unfortunatly ... I dont have any chance to restore it

regards, Gesatec

[darknight]

Hi, i have my 1st nand:




Then, i followed the tutorial.
it didn't worked, so i made a second backup of the nand that i have now in the xbox:



What i did wrong? I replaced with zeros the 0x03D98
Shouldn't this work?

Can u help? Thanks.

[boby2pc]

Hi, i have my 1st nand:




Then, i followed the tutorial.
it didn't worked, so i made a second backup of the nand that i have now in the xbox:



What i did wrong? I replaced with zeros the 0x03D98
Shouldn't this work?

Can u help? Thanks.

First of all do You have two identical original copies of Your nand ?
if no I can't help, esspecialy if you used delete method

[darknight]

I have 7 original dumps, all different btw, i was worried about this, but, i read somewhere that could happen and it could be ok
I compare the files in hex editor and total commander and all of them seems to have info in different blocks.
It seems not ok right? Do you think is something wrong with my lpt programmer/pc? Should i try usb? Thanks.

[Arakon]

If it's different every time, then obviously some data is garbage. Don't try to flash that until you can get a flawless copy that matches between dumps. Try shortening the cable.

[boby2pc]

I have 7 original dumps, all different btw, i was worried about this, but, i read somewhere that could happen and it could be ok
I compare the files in hex editor and total commander and all of them seems to have info in different blocks.
It seems not ok right? Do you think is something wrong with my lpt programmer/pc? Should i try usb? Thanks.

It could happen if you have bad blocks in Your nand. It shows 250 error during making dump in nandpro.

If for all dumps it's the same region then You should check individually to read that blocks with nandpro.
If the read fails all the times then it's bad block and could skip that block.

You should check every region serveral times.

Then we could start to look for good patch.

Did You use v0.61 of findsecdata ?


Something more about Your log:
there is something really strange with Your block 0 which findsecdata found indexes to filetables which coudn't happen.

[darknight]

Yes i have some 250 errors in nand reading, but always in the same blocks.
Yes i used 0.61v of findsecdata.

Arakon, What cable are u referring to?

After much reading, i am pointing to the normal 4148 diode i am using is the problem cause! I will try another one, What reference do you recommend me?
What u're using?

[boby2pc]

Yes i have some 250 errors in nand reading, but always in the same blocks.
Yes i used 0.61v of findsecdata.

Arakon, What cable are u referring to?

upload your dump to fileserver and give me link

[Arakon]

Yes i have some 250 errors in nand reading, but always in the same blocks.
Yes i used 0.61v of findsecdata.

Arakon, What cable are u referring to?

After much reading, i am pointing to the normal 4148 diode i am using is the problem cause! I will try another one, What reference do you recommend me?
What u're using?

The wires and the lpt cable. especially the wires going to the MB.

[ZerOneX]

Like Arakon said.... I received several errors with a long cable (1 M)... after that I reduced the cable for 30 cm... no errors since them.

[darknight]

Like Arakon said.... I received several errors with a long cable (1 M)... after that I reduced the cable for 30 cm... no errors since them.

I have the exactly size for cables go from xbox360 to pc, may be 25cm. Do u think it could be the diode 4148 i am using?

[CrimsonIdol]

Right, I've now started my sixth dump of a 512 MB Jasper using an LPT cable. ~24 hours per dump, hooray...

Each time I've gotten a 250 error on block 550 and a 210 OR 218 error on blocks 555 and 556. Two of the dumps seems to have bad data elsewhere, however three dumps are similar except for blocks 555 and 556 (offsets between 15FEA00 and 1606E00).

(I did use Nandpro 2.0 for the three first dumps and Nandpro 2.0b for the last two. Well, three with the one I've just started)

Soldering and wiring seem to be fine, I've got a short cable (~25 cm), the diode is soldered on to the motherboard, not the DB25 plug. I've checked connections using a multimeter. The entire cable has about the same resistance as the resistor itself, so no loss there. The diode tester on the Fluke gives me the same value over the length of the cable compared to just measuring across the diode.

(I'm tempted to try out the PIC-solution since we just got a new PIC programmer at work, but it seems getting the right PIC is difficult here. That, and it seems only reading works for 256MB/512MB Jaspers at the moment. Not a big problem I guess, but still...)

FindSecData (v0.61) gives me the same suggestions for secdata.bin on each dump, but I guess that's because the blocks where this resides is identical on each dump.

[boby2pc]

Each time I've gotten a 250 error on block 550 and a 210 OR 218 error on blocks 555 and 556. Two of the dumps seems to have bad data elsewhere, however three dumps are similar except for blocks 555 and 556 (offsets between 15FEA00 and 1606E00).

so You have 3 bad blocks, nothing to worry about. Repeat reading those 3 blocks individually and it this is the same result  then skip them.

(I did use Nandpro 2.0 for the three first dumps and Nandpro 2.0b for the last two. Well, three with the one I've just started)

Don't use ver. 2.0 anymore. It hangs on writing to 256 and 512 NANDs. Use only 2.0b.

FindSecData (v0.61) gives me the same suggestions for secdata.bin on each dump, but I guess that's because the blocks where this resides is identical on each dump.

give us findsecdata log for confirmation. Do backup of recommended two blocks, and patch NAND with recommended.

[darknight]

boby2pc, can you check please?

Nands:
1st original:-----------
2nd original: ----------
3rd original: ---------

final (in xbox now) after zerod: ---------

thanks

[jedidias]

First of all do You have two identical original copies of Your nand ?
if no I can't help, esspecialy if you used delete method

What if I only have 1 copy of my nand and the same issue that darknight has?
 

[boby2pc]

What if I only have 1 copy of my nand and the same issue that darknight has?
 

what have you done, describe it , give screenshot of findsecdata

[darknight]

boby2pc, i am dumping a new bin with nandpro20b, as soon as possible i will upload it, here is the last one that i dumped last night with nandpro20:
-------------

and my findsecdata result:

[boby2pc]

boby2pc, i am dumping a new bin with nandpro20b, as soon as possible i will upload it, here is the last one that i dumped last night with nandpro20:

Checked Your NANDs. The first I coudn't download but it doesn't matter propobly.

I checked it from other side, starting to find valid secdata.bin. You have two valid secdata.bin in Your NAND. The banned one and the second one with timestamp 2005-11-22. I don't know when this second one was created but I suppose it's banned one as well, created when You booted XBOX without DVD drive.

the one think you could test is to write that secdata.bin on current secdata.bin (because current timestap is 2005-11-22 as well then we don't need to correct timestamp in filetable)

do backup:
nandpro lpt: -r256 backup1.bin 199 1
do (with large R and W):
nandpro lpt: -R256 test1.bin 7b1 1
nandpro lpt: -W256 test1.bin 199 1

if it won't help then in my opinion it's unrecoverable, but I will check Your current full dump when You will complete it.

[darknight]

thanx boby2pc, waiting for finishing this dump.

[kitopa]

Code:

Hi,

I got a probleme with my nan Dump.
[code]
findsecdata v0.61 2009-12-01 by boby2pc
Controller version 1
Last filetable change: 0x40
ECC change: 0x40 Filetbl: 0x012E Secdata: 0x0357 Timestamp: 3B725296 2009-11-18
ECC change: 0x38 Filetbl: 0x0356 Secdata: 0x013A Timestamp: 33766001 2005-11-22
ECC change: 0x34 Filetbl: 0x0139 Secdata: 0x0138 Timestamp: 33766001 2005-11-22
ECC change: 0x33 Filetbl: 0x0137 Secdata: 0x0136 Timestamp: 33766001 2005-11-22
ECC change: 0x32 Filetbl: 0x0135 Secdata: 0x0134 Timestamp: 33766001 2005-11-22
ECC change: 0x31 Filetbl: 0x0133 Secdata: 0x0132 Timestamp: 33766001 2005-11-22
ECC change: 0x30 Filetbl: 0x0131 Secdata: 0x0130 Timestamp: 33766001 2005-11-22
ECC change: 0x2F Filetbl: 0x012F Secdata: 0x012E Timestamp: 3B6D49C4 2009-11-13

Checking secdata:
012E containts not 0 values above offset 1024

Searching for recommended

Extracting secdata:
secdata0357.bin
secdata013A.bin
secdata0138.bin
secdata0136.bin
secdata0134.bin
secdata0132.bin
secdata0130.bin

Extracting filetables:
filetable012E.bin
filetable0356.bin
filetable0139.bin
filetable0137.bin
filetable0135.bin
filetable0133.bin
filetable0131.bin

Creating patched secdata:
Patchedsecdata0357.bin
Patchedsecdata013A.bin
Patchedsecdata0138.bin
Patchedsecdata0136.bin
Patchedsecdata0134.bin
Patchedsecdata0132.bin
Patchedsecdata0130.bin

Creating patched filetables:
Patchedfiletable012EBy0356.bin
Patchedfiletable012EBy0139.bin
Patchedfiletable012EBy0137.bin
Patchedfiletable012EBy0135.bin
Patchedfiletable012EBy0133.bin
Patchedfiletable012EBy0131.bin

Use:
nandpro.exe lpt: -w16 Patchedsecdata013A.bin 357 1
nandpro.exe lpt: -w16 Patchedfiletable012EBy0356.bin 12E 1

I've tried with the command, no way. Even zered 0x0357.

I need help

Ps: Here is my


I've tried with the command, no way. Even zered 0x0357.

I need help Wink