SLIM 16D2S (spoofed as 9504) -> 16D4S 9504 migration questions

[Panteras.Psytone]

Hi. I've got XBOX Slim with 16D2S 7485 drive flashed as 16D4S 9504... Somehow it worked until Gears of War 3 13146 dashboard update - now it's stuck on update error 3151-335a-b800-0401-c000-003c which i believe due to impossibility to flash my drive. So i dumped key, serial, identify, inquiry and (as result of these) Dummy bins with PhatKey method (probing MPX01). With "Parse Firmware" window saying:"Key sector area is incomplete or invalid!" at the end of process. To be shure that extracted key is right - I made MRA Hack and dumped entire flash memory. But still - JungleFlasher cant load it as Source or target, saying that "Parse Failed!". So now i'm using WinHEX to manually edit all these bins...

1. key.bin from PhatKey and A030 string in dummy.bin from MRA Hack differs. Correct me please if i am wrong - the right key is in A030, and key.bin consist of some wrong data?

Yesterday i've bought a new drilled unlocked Winbond 16D4S 9504 with different serial number on the case and in dummy read from it's flash (???).

2. Should i change it or leave as is? Could it make some problems in future (with new dashboard update) with console checking the drive?

I've restored keysector area with LizardFix method... but 2AFF0-2AFFF "second key" (i dont know right title for it) is empty. I've heard that sometimes xbox checks it... so don't want to loose it. Cause in the future it could became a regular check...

3.Which one second key should i write into dummy.bin (which i want to use as source in future) - the old one from 16D2S or the new from 16D4S? Is this "second key" motherboard related, or its just internal key of the drive, that has no relation with MB, DVDkey (the usual key) and key sector area?

4.What are the parameters for key sector restoration process in 9504 - does it depends on serials, second key.

PS: I just want to make maximum correct dummy with right key, key sector, second key and serials. And make XBOX work again...
PPS: Sorry for my awful English!

 

[majesstik]

not sure that jf is going to support spoofing at this point. way too much work for what you want to do if you ask me. id just get a slim drive. but if you really want to try, id start with update on usb and latest 0272 flashed to drive and try to update console that way. then flash with lt3.0

 

[x360ccm]

if you use the lizfix correct then you got your new dummy for your 9504 drive.

the prob you have is what dash was you trying to update to before you got stuck in the loop.

and what was the dash you was on before you tried to update your dash.

 

[Panteras.Psytone]

not sure that jf is going to support spoofing at this point. way too much work for what you want to do if you ask me. id just get a slim drive. but if you really want to try, id start with update on usb and latest 0272 flashed to drive and try to update console that way. then flash with lt3.0

I'd like to flash my new 9504. But i'm not sure about DVDKey, Keyarea, "second key" and serials.

Just opened full memory dump (Lite-OFW) from 16D2S in JF 1.67 as Target, and it shows same DVD Key as in Key.bin from PhatKey. But it's not the A030 string from this Lite-OFW.bin! :crazy:So... it seems that Key.bin is correct and A030 string is not? It's also shows MODEL Rev and OSIG of Lite-OFW as DG-16D2S 7485

 

[Panteras.Psytone]

After some experimenting with dumping and flashing - it seems that key placed at A030 string only in Dummies, not full dumps. sorry. So Key.Bin is correct. Sorry... Now i need to find out - should i

a.) copy-past 2A000-2AFFF from 16D2S dump to 16D4S dummy,
b.) copy-past 2A000-2AFEF and take 2AFF0-2AFFF from original (i hope it is original) 16D4S firmware
c.) Generate 2A000-2AFEF with LizardFix and take 2AFF0-2AFFF from unknown 16D2S firmware
d.) Generate 2A000-2AFEF and take 2AFF0-2AFFF from original 16D4S firmware...

4 combinations of old/generated key sector, old/new second key.

 

[jeremy790]

Sounds like you are over complicating this process. If you have a good key.bin and new pcb just do a manual spoof with JF and you should be good to go. BTW I've seen severaThal box's do this with that update due to spoofed drives. This is a good example of why auto spoofing drives is no longer supported. Manual spoofing of keys from the same model drive is not a big deal. So that being said if it where system I was working on I would have just purchased a whole new drive and manually spoofed the key

 

[Alex99id]

Hy

About this : 3151-335a-b800-0401-c000-003c

How you have done the update ? With a backup disk?

---------- Post added at 19:19 ---------- Previous post was at 19:17 ----------

If so, try update with the same original game disk.

 

[Panteras.Psytone]

Hy

About this : 3151-335a-b800-0401-c000-003c

How you have done the update ? With a backup disk?

---------- Post added at 19:19 ---------- Previous post was at 19:17 ----------

If so, try update with the same original game disk.

No. Gears of War 3 disk. It asked for update to launch the game.

 

[Ubergeek]

get a 9504 drive with stock and your key then run the update again

simple !