Nandbackup of 8509 not working after update to 8955

[MRA]

I have here a jasper console of which I made a backup of Dash 8509. Afterwards i updated to 8955 and now if I flash the old image back to the console the console won´t boot it just gives 3LOD. Why is that? CB, CD, CE didn´t changed. Are there even fuses blown if only CF/CG changes?

[damox]

Yes the efuse will still increment. EVERY update (well newer updates anyway) will increase the ldv.

Why don't you try and increment your old dump, and reflash?

[neonpolaris]

Out of my own personal curiosity, what is your purpose for rolling back to 8509?

[MRA]

OK, it is totally logical that the LDV is incremented. Every update til now just updated the CF/CG. CB/CD was only updated once til now. The purpose of going back to 8509 is: The Box has a HDD Lock and the update to 8955 overwrote the old secdata.bin. So it is not possible to unlock the HDD anymore. The 8509 dump still has the old secdata and so unlocking might still be possible.

EDIT: Oh yes, and incrementing the LDV in the 8509 dump doesn´t work either. The Box wont boot.

Is there a way to use the secdata.bin from my old dump to create a unbanned 8955 image?

[Arakon]

You could still extract secdata from the old dump and insert it into the new flash.

[neonpolaris]

The Box has a HDD Lock and the update to 8955 overwrote the old secdata.bin. ...  The 8509 dump still has the old secdata...

I see, thanks for answering, do post if Arakon's suggestion (or whatever else) works for you.

[MRA]

Just for further info here is some output of findsecdata, I hope it doesn´t become to confusing!

Here the output from the 8509 dump:

findsecdata v0.62 2009-12-09 by boby2pc
Controller version 2
Last filetable change: 0x33
ECC change: 0x33 Filetbl: 0x0181 Secdata: 0x0180 Timestamp: 3B7378BB 2009-11-19
ECC change: 0x2F Filetbl: 0x03A3 Secdata: 0x039D Timestamp: 3B3771A6 2009-09-23
ECC change: 0x28 Filetbl: 0x0199 Secdata: 0x03B1 Timestamp: 3B3598CF 2009-09-21

Checking secdata:
03B1 containts not 0 values above offset 1024 or zeros below 1024 (overwritten)

Searching for recommended

Extracting secdata:
secdata0180.bin
secdata039D.bin

Extracting filetables:
filetable0181.bin
filetable03A3.bin

Creating patched secdata:
Patchedsecdata0180.bin
Patchedsecdata039D.bin

Creating patched filetables:
Patchedfiletable0181By03A3.bin

Use:
nandpro.exe lpt: -w16 Patchedsecdata039D.bin 180 1
nandpro.exe lpt: -w16 Patchedfiletable0181By03A3.bin 181 1

Here the output from the 8955 dump:

findsecdata v0.62 2009-12-09 by boby2pc
Controller version 2
Last filetable change: 0x3E
ECC change: 0x3E Filetbl: 0x0162 Secdata: 0x038A Timestamp: 33766001 2005-11-22
ECC change: 0x36 Filetbl: 0x0389 Secdata: 0x0180 Timestamp: 3B7378BB 2009-11-19

Checking secdata:

Searching for recommended

Extracting secdata:
secdata038A.bin
secdata0180.bin

Extracting filetables:
filetable0162.bin
filetable0389.bin

Creating patched secdata:
Patchedsecdata038A.bin
Patchedsecdata0180.bin

Creating patched filetables:
Patchedfiletable0162By0162.bin

Use:

Old secdata.bin not found. Console might be not banned, already patched or secdata.bin overwritten.

--------------------

First of all I´m somehow confused about the timestamp of the newest secdata.bin in the 8955 dump. It is 2005, but maybe this is an issue of findsecdata. I don´t know yet. The Box was updated 2 days ago I think so it should be 2010 in my opinion.
As I was not able to restore to 8509 I also tried was Arakon was suggesting. I took the "good" secdata.bin from the 8509 dump (offset 0x39D*4200) and copied it to offset 0x38A*4200 of the 8955 dump. Then I corrected the timestamp in the filetable at 0x162*4200 to the correct value (3B3771A6 = 2009-09-23). When I try to boot the console I see something I never had before. The console tries to update and then says on bootup that i can´t be updated and to contact the service. Just take a look:

http://www.multiupload.com/Z0TAC5CNBD

Seems like unlocking this console is not possible. Or any of you has any suggestions? It is a new Jasper with Flashconfig 23010, that´s the only "unusual" about it.

[maximilian0017]

Looks like it tries to start an update from the HDD or other Memorydevice.

Make sure the xbox is off
Hold the sync button and power on using the poweron button of the Xbox
Keep holding the Sync button until the dash is displayed.

Strange that the update wont work.

[MRA]

No memorycars or HDD is connected to the console. Removing a failed update with the syncbutton doesn´t work either.

[maximilian0017]

No memorycars or HDD is connected to the console. Removing a failed update with the syncbutton doesn´t work either.

It looks like the console is missing something and wants to add it through the update(like the avatars)

Flashconfig 23010 points to a Jasper with the new Southbridge, Nandpro has a problem with it with writing and then creating ECC data for it +W(Tiros is planning to update it), you arent using this mode if i read correctly but maby that can explain the troubles you are having.

You can manualy download the update and execute it with the help of a Memory stick, maby that will help it to boot again.

This is ofcourse on your own risk.

[MRA]

Already tried to apply the update manually. If I put in a disc or a stick with a systemupdate the error message is not shown and the system hangs at the xbox logo. I think I just have to accept that its not possible to unlock this one.

[maximilian0017]

Already tried to apply the update manually. If I put in a disc or a stick with a systemupdate the error message is not shown and the system hangs at the xbox logo. I think I just have to accept that its not possible to unlock this one.

Thats a shame, you could always contact Boby2pc if the error is connected to findsecdata or retry with the new version of Nandpro if it comes out.

Good luck