restore hdd game install after ban with nand backup?

[alexandre229]

I have found something:

When i compare the secdata01D2.bin extracted by FSD and the same part in the nand.bin, it lacks a line in secdata01D2.bin.

Is it normal ?

Yes, this file miss the ECC information. To compare, you need to -R16 instead of -r16 when you dump the block.
But this is made this way, as this file is flashed with -W16 and not -w16

boby2pc, did you know about +w16 / +W16 nandpro's commands ? They fix ecc when writing. Don't know if it's usefull to you.

This is my error !!
I have flashed with -w16 and not -W16 => i'm dummy
It's clearly writed in application
After a new test, all working fine with patching

Sorry

Thanks

[sandungas]

boby2pc have you seen the code of the timestamp tool that cmonkey did ?
Works like a charm translating timestamps
http://www.xboxhacker.net/index.php?topic=12778.msg87672#msg87672

[boby2pc]

I have found something:

When i compare the secdata01D2.bin extracted by FSD and the same part in the nand.bin, it lacks a line in secdata01D2.bin.

Is it normal ?

Yes, this file miss the ECC information. To compare, you need to -R16 instead of -r16 when you dump the block.
But this is made this way, as this file is flashed with -W16 and not -w16

boby2pc, did you know about +w16 / +W16 nandpro's commands ? They fix ecc when writing. Don't know if it's usefull to you.

Yes, I know difference between +w16 and +W16, l_oliveira told me about that, because I didn't know about that few days ago. I use both of them showing the recommended patches in my application

The one of more important things is that it sometimes not work properly, and it's not possible to fix that issue.
The +W option recalcuates whole 0x10 bytes of ECC data, but in fact ECC it rebuids block number, FF byte and last 4 byte ECC data. For many records this is correct, for example secdata.bin record, but for filetables records it ommits one important (third) byte in ECC data. It is change version. When we simply do read -R and -W the block then that information dissapears, and XBOX don't see that block as one version of the filetables.

That one byte I used in application to find most recent filetable change. And for that one byte I generate the Patchfiletable file with ECC data with that one byte filled, so applying patch with -w option is important.

[corpo]

I forgot about fsroot revision stored in ecc fields, making +W useless
Anyway, my post made alexandre229 notice his mistake, so it's not a total loss ...

[boby2pc]

boby2pc have you seen the code of the timestamp tool that cmonkey did ?
Works like a charm translating timestamps
http://www.xboxhacker.net/index.php?topic=12778.msg87672#msg87672

Thank You very much for info. A few days ago I tried to find algoritm to convert it properly, but with no success.
That's why algoritm in my application is not perfect, but it's quite ok, because it only shows datetime and not process it.

I will try to implement proper algoritm in next version, thanks

[Pacote-san]

Just tried findsecdata 0.4 on my friends nand (jasper 16mb) and it worked perfectly

Thanks again

[110007]

hi

i have a programmer and i read nand with it.
how can change the secdata on nand.bin directly and write it on nand chip and restore my hdd for copying game on it?

Thanks

[l_oliveira]

Yes, I know difference between +w16 and +W16, l_oliveira told me about that, because I didn't know about that few days ago. I use both of them showing the recommended patches in my application

The one of more important things is that it sometimes not work properly, and it's not possible to fix that issue.
The +W option recalcuates whole 0x10 bytes of ECC data, but in fact ECC it rebuids block number, FF byte and last 4 byte ECC data. For many records this is correct, for example secdata.bin record, but for filetables records it ommits one important (third) byte in ECC data. It is change version. When we simply do read -R and -W the block then that information dissapears, and XBOX don't see that block as one version of the filetables.

That one byte I used in application to find most recent filetable change. And for that one byte I generate the Patchfiletable file with ECC data with that one byte filled, so applying patch with -w option is important.

Due to that stuff on how nandpro handles ECC regeneration would not be a better procedure to retrieve file table information from the nand dump and instead of changing the file tables around, why not just flash the older secdata contents on top of the current existing secdata ? I've done it and I know it works. Much easier than deal with the filesystem tables.

[nazster]

For some reason I am getting this message and I just can't install any game on harddrive

[boby2pc]

Yes, I know difference between +w16 and +W16, l_oliveira told me about that, because I didn't know about that few days ago. I use both of them showing the recommended patches in my application

The one of more important things is that it sometimes not work properly, and it's not possible to fix that issue.
The +W option recalcuates whole 0x10 bytes of ECC data, but in fact ECC it rebuids block number, FF byte and last 4 byte ECC data. For many records this is correct, for example secdata.bin record, but for filetables records it ommits one important (third) byte in ECC data. It is change version. When we simply do read -R and -W the block then that information dissapears, and XBOX don't see that block as one version of the filetables.

That one byte I used in application to find most recent filetable change. And for that one byte I generate the Patchfiletable file with ECC data with that one byte filled, so applying patch with -w option is important.

Due to that stuff on how nandpro handles ECC regeneration would not be a better procedure to retrieve file table information from the nand dump and instead of changing the file tables around, why not just flash the older secdata contents on top of the current existing secdata ? I've done it and I know it works. Much easier than deal with the filesystem tables.

I agree with You this will be best solution but it works only sometimes. Problem is with timestamp of secdata.bin. The file have encrypted somewhere his timestamp which is related to timestamp in filetable. If those two values differs the XBOX doesn't see that file.

[boby2pc]

For some reason I am getting this message and I just can't install any game on harddrive

0.42 Released so try it with this version

Could You send me Your NAND backup for better testing ?

[ILIN]

I wonder what will happen on next update. Won't console cripple at all because of nand modification?

[corpo]

I wonder what will happen on next update. Won't console cripple at all because of nand modification?

I guess nothing special will happen : no file is modified. fsroot corruption (erasing the latest fsroot to revert to the previous secdata) can occur when you switch off the console when nand is updating, and the boby2pc way of doing things is truely impossible to detect.

[nazster]

0.42 Released so try it with this version

Could You send me Your NAND backup for better testing ?

Thanks for the quick reply.

I tried the new program but for some reason it gives error. i am uploading the file on megaupload will send you a message as soon as its done.

Thanks again

[soulnos]

I've ran into a bit of a hitch. I dumped my nand and used 360 HDFR v1.03 to create the zero'd out Secdata. I then used nandpro to write the Secdata.bin. Something must have went wrong. HDD functionality was not restored and I'm also getting two blinking red lights on the left. I'm not sure if the red lights are from the soldering or the nand write. I'm going to try it again now with bob's tool and see if I get better results.

[Mossolb]

Hi boby2pc, great program, I was able to restore my hdd on my Xeon 360 but I'm stuck at a wall with my Falcon 360. I've dumped the nand 4 times now, and 2 more times after logging on xbl to verify the console is still banned (nand did change in the hex editor after logging on xbl and hash check did not verify with the dumps before logging on xbl).



Only two different values, no single value that sticks out. For more info I had updated NXE from my HDD that was connected on another 360, then it connected to XBL and right away it said my Falcon 360 was banned, kernel is the latest.


Edit*
@soulnos 360 HDFR v1.03 worked for you? it wouldn't load any of the dumps on xp, vista, or win7, and v1.02 would crash halfway loading the files.

[nazster]

here is the link to the nand file

www.pittmandu.com/nand.bin

[boby2pc]

Hi boby2pc, great program, I was able to restore my hdd on my Xeon 360 but I'm stuck at a wall with my Falcon 360. I've dumped the nand 4 times now, and 2 more times after logging on xbl to verify the console is still banned (nand did change in the hex editor after logging on xbl and hash check did not verify with the dumps before logging on xbl).



Only two different values, no single value that sticks out. For more info I had updated NXE from my HDD that was connected on another 360, then it connected to XBL and right away it said my Falcon 360 was banned, kernel is the latest.


Edit*
@soulnos 360 HDFR v1.03 worked for you? it wouldn't load any of the dumps on xp, vista, or win7, and v1.02 would crash halfway loading the files.

Sometimes the old secdata.bin is overwritten (so far 3 man I tried to help with no success). Each occurence I verified myself downloading their NAND dump to search propper secdata and confirm that it's not possible.
It usually happend when there were few updates of system after ban (game patch or system update).

I hope my app is wrong about Your NAND, but upload it, I will check it myself.

[110007]

plz sombody answer me
 

i have a programmer and i read nand with it.
how can change the secdata on nand.bin directly and write it on nand chip and restore my hdd for copying game on it?

[Mossolb]

Sometimes the old secdata.bin is overwritten (so far 3 man I tried to help with no success). Each occurence I verified myself downloading their NAND dump to search propper secdata and confirm that it's not possible.
It usually happend when there were few updates of system after ban (game patch or system update).

I hope my app is wrong about Your NAND, but upload it, I will check it myself.

Here is my nand http://www.mossolb.com/files/falcon_nandtest.rar

This 360 was played a lot less than the other one I was able to restore prior to the banning, that is all I can think of.

Edit* fixed the link if anyone else wants to play with it.

Thanks for your help boby2pc.