restore hdd game install after ban with nand backup?

[corpo]

So change 3F was correct. "recommendation" algo is not perfect because of secdata.bin is crypted and no possibility to select good one.

Thanks Corpo for support and alexandre229 for testing

You're welcome
Notice that when the banned secdata is written the first time, the fsroot is the immediate next block (as only secdata is updated). This should help you with your algo for selecting the right good secdata (which your tool did right in this case). But simply select the secdata from the latest fsroot update as target and everything should be fine. As soon as you have a wrong timestamp in the fsroot updates, this means that the console couldn't access live to set the clock right (if unplugged, of course)

[Ski-lleR]

If i'm not banned, but want to erase possible detection record, can i use the most old secdata (i have 03-23-09, just before the drive is flashed) for prevent futur ban ?

[Pacote-san]

Maybe you can try this apps (for 16MB) :



Available http://x360.gx-mod.com/modules/news/article.php?storyid=2349

Tried on another box....

It gave me block 361 to erase, i erased and still banned...

strange... flashtool told me that my secdata was on block 362, so wasnt i suppose to erase block 363? will flash my backup and try again

[boby2pc]

So change 3F was correct. "recommendation" algo is not perfect because of secdata.bin is crypted and no possibility to select good one.

Thanks Corpo for support and alexandre229 for testing

You're welcome
Notice that when the banned secdata is written the first time, the fsroot is the immediate next block (as only secdata is updated). This should help you with your algo for selecting the right good secdata (which your tool did right in this case). But simply select the secdata from the latest fsroot update as target and everything should be fine. As soon as you have a wrong timestamp in the fsroot updates, this means that the console couldn't access live to set the clock right (if unplugged, of course)

This is quite good idea. I will make "omit timestamp checking" as default, because good secdata might be created offline.

I will consider Your sugggestions about "recommnded update". I thought that the last-1 online (timestamp>2005-01-01) secdata update should be correct, but it seems that is not always good.

[corpo]

This is quite good idea. I will make "omit timestamp checking" as default, because good secdata might be created offline.

I will consider Your sugggestions about "recommnded update". I thought that the last-1 online (timestamp>2005-01-01) secdata update should be correct, but it seems that is not always good.

Or you can ask the user if he has started his console without the dvd drive since the ban, as it is an uncommon case I believe. It's the only way to reproduce this special case

[boby2pc]

Or you can ask the user if he has started his console without the dvd drive since the ban, as it is an uncommon case I believe. It's the only way to reproduce this special case

Well, that will be good.
1) Eliminate every console start without dvd drive (timestamp 33766001)
2) Find last online update as banned one
3) Get last online update before pt.2. If it fails get last before pt.2 offline.

what do You think ?

[corpo]

Seems okay to me

[Pacote-san]

Well im in the middle of a mindf*** here....

On my other xbox i tried again flashing the backup and then erasing 0x0361 without sucess, tried 0x0363 and no go either...

Using bob app he only finds a good Timestamp (2009-11-12) and one from 2004, i tried bob app on my other xbox and it found lots of valid timestamps...tried with my other xbox flashing and still BANNED!

I give up, i will upload the file and see if someone here can help hehe

Here, http://www.megaupload.com/?d=KM4C8244

If someone could help

Thanks

[Pacote-san]

UPDATE: I tried reading the secdata used block (362 according to flash tools) and reading a old secdata block (376 which appears 6 times on hex workshop)

Overwrited block 362 with 376 but now i get Secdata is invalid

Erasing blocks 361 and 363 got me E71

I bought this xbox yesterday, its possible that the owner got banned on 12-11 as stated in the last secdata, and played some game which updates the console (fifa 10 perhaps) and so now the console doesnt have any old valid secdata so no way to enable hdd install again?


UPDATE2: Remembering now, when i got home i opened the xbox so i could do some mods since its a 2006 model that gets very hot, after the mods i think i turned the cnosole on withou the drive one time... maybe this fuc** up my secdata?

[boby2pc]

UPDATE: I tried reading the secdata used block (362 according to flash tools) and reading a old secdata block (376 which appears 6 times on hex workshop)

Overwrited block 362 with 376 but now i get Secdata is invalid

Erasing blocks 361 and 363 got me E71

I bought this xbox yesterday, its possible that the owner got banned on 12-11 as stated in the last secdata, and played some game which updates the console (fifa 10 perhaps) and so now the console doesnt have any old valid secdata so no way to enable hdd install again?


UPDATE2: Remembering now, when i got home i opened the xbox so i could do some mods since its a 2006 model that gets very hot, after the mods i think i turned the cnosole on withou the drive one time... maybe this fuc** up my secdata?

it looks like it was updated to newest DASH and banned at once or someone tried to do something with the filetables which directs to secdata in 370 and 376 because they are invalid, BUT
i will try to recover that, be patient and don't delete anything else !
It may be unrecoverable because of dash update, but we will see.

[corpo]

well, it's impossible, if he got banned on 12/11, that the box was not with 2.0.8955.
Now, if the box was banned last year, then upgraded with a game, I'm afraid you're stuck in a dead end

[Pacote-san]

The owner started to annouce his x360 to sale on 19/11 so yes, he was banned on 12/11, and the dash was already updated to 8955

The nand itself was never dumped as i checked the points and they were clean when i soldered the cable.

Well, while i wait for you guys help i will flash back the nand since its E71 now hehe

Thanks for the effort

[corpo]

Can you post a log of boby2pc's tool on your nand backup (yeah, I know, I'm lazy :p)

[Pacote-san]

Can you post a log of boby2pc's tool on your nand backup (yeah, I know, I'm lazy :p)

No problem

findsecdata v0.3 2009-11-25 by boby2pc
Controller version 1
Last filetable change: 0x99
ECC change: 0x99 Filetbl: 0x0363 Secdata: 0x0362 Timestamp: 33766001 2004-04-13
ECC change: 0x98 Filetbl: 0x0361 Secdata: 0x0360 Timestamp: 3B6D05E2 2009-11-12

Checking secdata:
0362 with bad datetime

Extracting secdata:
secdata0360.bin

Extracting filetables:
filetable0361.bin

Creating patched filetables:
Patchedfiletable0363By0361.bin

Recommended use:
nandpro.exe lpt: -W16 secdata0360.bin 362 1
nandpro.exe lpt: -w16 Patchedfiletable0363By0361.bin 363 1

Press ENTER

[boby2pc]

Pacote: I sent You mail, try it.

[Pacote-san]

Pacote: I sent You mail, try it.

IT WORKED!!! Intalling NFS Shift in the 20GB HDD

The firts command was enough:

nandpro.exe lpt: -W16 secdata0376.bin 362 1
nandpro.exe lpt: -w16 Patchedfiletable0363By03D3.bin 363 1

Thanks very much dude

So how did you fixed secdata that was on block 376? It was invalid before right?

[boby2pc]

Pacote: I sent You mail, try it.

IT WORKED!!! Intalling NFS Shift in the 20GB HDD

The firts command was enough:

nandpro.exe lpt: -W16 secdata0376.bin 362 1
nandpro.exe lpt: -w16 Patchedfiletable0363By03D3.bin 363 1

Thanks very much dude

So how did you fixed secdata that was on block 376? It was invalid before right?

Great, have fun!
There was gap between filetable versions which application doesn't accept.
I'm working on application to support such NAND bug. Tonight or tomorrow I will release it with
better "recommendations" mechanizm.

Just realeased new version 0.4

[alexandre229]

Are you shure ?

I think you have an error:

nandpro.exe lpt: -W16 secdata01D2.bin 0E3 1
nandpro.exe lpt: -w16 Patchedfiletable00E4By00DA.bin 0E4 1

Because if i write a file table to a secdata, i don't think is working good...

What do you think ?

I will write my backup again and test the patching.

I let you know.

After new test,  bad news is not working.

For others tests, i will do it tomorow because in europe it is late.

by

Hello,

1) I have deleted step by step:

0x00E2/0x00E1
0x00E0/0x00DF
0x00DE/0x00DD

Test bad

2) deleted:

0x00DC/0x00DB (secdata banned)

Test bad

3) deleted:

0x00E4/0x00E3

Test success

The patch not working ...

Before deleted E4/E3 i have dumped this two blocks and compared it with secdata01D2.bin and Patchedfiletable00E4By00DA.bin (for checking if writing was good) and no difference was found.

I don't understand why patching don't working.

[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 ?

[corpo]

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.