restore hdd game install after ban with nand backup?

[Pacote-san]

Oh and by the way i testes XVAL and i got

0000000000000400
Console banned

But i can try to play games from HDD but it asks for the disc on the drive (as i have no drive....)
I thing a hdd cripped console wouldnt let you even select this option am i right?

if you got 0x0400 then hdd install are disabled ...
Banned console allow you to choose but then refuses to launch (same as if the game was installed from another xbox)

Strange....

I checked all 11 occurences of SECDATA.bin on my dump and im sure that block 0364 is the last one from ban.... Flash tool also confirms it....

Just erased it with e16 command, booted the console and i still got the same X value....

[corpo]

Strange....

I checked all 11 occurences of SECDATA.bin on my dump and im sure that block 0364 is the last one from ban.... Flash tool also confirms it....

Just erased it with e16 command, booted the console and i still got the same X value....

flash tool reports secdata at block 363 ?
edit : yes, you reported it in a previous post.
Haven't tried -e myself, but should work the same, did you try to flash a blank 0x4200 bytes files instead ?
Try removing power from the console. And beware, console logs the number of boots without dvd drive in secdata. That's maybe what's wrong in your case : fsroot is no more @364 since secdata has been updated since your dump. What you can try is restoring your full backup, then -e block 364 then boot to test xval
Then, when you receive your drive, don't forget to restore your full backup again to wipe the "without drive" boot count.

[Pacote-san]

Strange....

I checked all 11 occurences of SECDATA.bin on my dump and im sure that block 0364 is the last one from ban.... Flash tool also confirms it....

Just erased it with e16 command, booted the console and i still got the same X value....

flash tool reports secdata at block 363 ?
edit : yes, you reported it in a previous post.
Haven't tried -e myself, but should work the same, did you try to flash a blank 0x4200 bytes files instead ?
Try removing power from the console. And beware, console logs the number of boots without dvd drive in secdata. That's maybe what's wrong in your case : fsroot is no more @364 since secdata has been updated since your dump. What you can try is restoring your full backup, then -e block 364 then boot to test xval
Then, when you receive your drive, don't forget to restore your full backup again to wipe the "without drive" boot count.

Hmm did not know that either... and i have boot the console after i dumped the nand.bin so test it. Will flash it back , erase 364 block and boot the console with a dvd drive (i have the drive and its working with the proper key, it just doesnt have the laser inside lol

[Pacote-san]

Thanks Corpo   

Reflashed with the backup, right after that erased block 364, booted with the dvd drive just to be sure

Xval check:

0000000000000000
Secdata is Clean

 

[joeyddr]

Nothing wrong, but a nandpro lpt: -e16 0x364 would have made things faster
Use Xval to know about banned or not

so flashtool to find the secdata.bin block then -e16 0xwhateverthatblockis...

nearly : take to block next to secdata, this is the one needed to erase

so say flashtool is reporting 0x0158 then i should pick?

[Pacote-san]

Nothing wrong, but a nandpro lpt: -e16 0x364 would have made things faster
Use Xval to know about banned or not

so flashtool to find the secdata.bin block then -e16 0xwhateverthatblockis...

nearly : take to block next to secdata, this is the one needed to erase

so say flashtool is reporting 0x0158 then i should pick?

erase 0x0159

But you can use hex workshop to confirm

[boby2pc]

I wrote little program to extract secdata.bin and filetable of NAND dump.
It uses patch latest secdata.bin method (not delete method).

megashares FindSecDatav0.62

sendspace FindSecDatav0.62




In v0.11 Fixed regional settings problem.

In v0.2 support for 256 MB and 512 MB NANDs implemented.

In v0.3 Different NAND controller support

In v0.4
         - "ommit timestamp" parameter removed - this is now default
         - added parameter to show more recomendations
         - "recommandation" algoritm changed
         - support for gaps in filesystem table version

v.0.41
         - added bypassing FF version records in filesystem
         - more accurate timestamp - used for visual purposes only

v.0.42
         - added parameter to show time part of timestamp in filetables

v.0.5
         - added support for large blocks
v.0.6
         - block rellocation support
         - now for 256MB and 512MB Jaspers is only needed dump of 0x600 blocks:
                nandpro lpt: -r256 raw.bin AE0 600
           or   nandpro lpt: -r512 raw.bin AE0 600
           so only about 1h dumping
v.0.61
         - protection to use large block controller with small 24MB dump.
v.0.62
         - additional secdata.bin checking. Checks if non-zero values exists below offset 1024.
         - fixed app crashes on checking filetable change nr.1
         - fixed to ommit doubled banned records
         - displaying changes: "overwritten" when block has bytes other than 0 above offset 1024 or zeros below 1024
         - option added to ommit block rellocation
         - option added to view all filetable entries

It's v0.62 version so test it.

[joeyddr]

the app crashed on 2 machines complaining about the date

[warpjavier]

Crash for me also. Tried with 2 different dumps.

[jz_5_3]

fixed jasper hdd installation manually.

[warpjavier]

How?
Can you explain how you did it?
I've been trying for 3 days without success.

Thanks

[sawwa]

Doesn't do anything.



I tried on 3 other pc and 2 other nand dump.

[ffriozi]

fixed jasper hdd installation manually.

Please Explain to us !!! what model? 16, 256 or 512 mb ?

[jz_5_3]

The idea is the same, you just have to locate the lastest update of secdata.bin and the one before that. There have been 7 secdata.bin entries in my jasper nand. use filesystem version # to identify.

How?
Can you explain how you did it?
I've been trying for 3 days without success.

Thanks

[boby2pc]

fixed regional settings problem. Link updated to new version

[warpjavier]

The idea is the same, you just have to locate the lastest update of secdata.bin and the one before that. There have been 7 secdata.bin entries in my jasper nand. use filesystem version # to identify.

How?
Can you explain how you did it?
I've been trying for 3 days without success.

Thanks

I know is the same, I found 6 on my dump where just two are valid. One banned and one unbanned, but when I replace the banned one with the unbanned one, I get secdata invalid with XVal.
Could you please explain how you did it?

Thanks

[jz_5_3]

hmm, I did not copy the content of old secdata.bin. instead, I changed the block offset of the secdata.bin in the new one to point the the previous good one. This is because I need to change the timestamp anyway and by doing this, I only need to re-calculate the ECC of the only page in the filesystem table. so basically three changes in one page: block offset, timestame, and ecc. that is all.

[warpjavier]

hmm, I did not copy the content of old secdata.bin. instead, I changed the block offset of the secdata.bin in the new one to point the the previous good one. This is because I need to change the timestamp anyway and by doing this, I only need to re-calculate the ECC of the only page in the filesystem table. so basically three changes in one page: block offset, timestame, and ecc. that is all.

I did that but didn't change the timestamp.
So basically you edit the newest filesystem table to point to the good secdata, and also change the timestamp with the timestamp of the previous version, then you recalculate the ecc?

I'll try it.

[sandungas]

fixed regional settings problem. Link updated to new version

0.11 still is having problems with the timestamps, is showing me a date of year 2004
After this... a pair of errors: bad datetime & old secdata not found

Im anxious to see exactly what the program does, thx

[boby2pc]

fixed regional settings problem. Link updated to new version

0.11 still is having problems with the timestamps, is showing me a date of year 2004
After this... a pair of errors: bad datetime & old secdata not found

Im anxious to see exactly what the program does, thx

It searches for valid secdata and only extracts with valid datetime in filetable and where secdata is not overwritten.

Are You sure that one with date 2004 is good ? (In my NAND I found one secdata with date 2004 and it was damaged then I decided to omit that records)

Added new parameters ("-ots") to application (v0.12) which allows to ommit timestamp checking, but it's not recommmended.