Print

[joliverio]

QUOTE(LiarInGlass @ Mar 8 2009, 06:50 PM)

Is it necessary to fix the serial error?

I do play on Live sometimes, but not all the time with backups.

I sucessfully flashed to 1.51, but is it necessary to fix this serial problem or when 1.6 will it be easier to just wait and re do the entire flashing process to get perfect serial information?

QUOTE(checker6 @ Mar 9 2009, 03:01 AM)

I tried flashing another liteon with the same problem of bad dummy.bin or incomplete i guess.  I was able to recreate the serial information, but i still have one that i dont have the pcb serial for.  Is this going to be a ban risk?  I have been playing it on 1.5 without the serial information i am assuming without getting banned.  Does anyone know if this is going to be a CRITICAL thing to do or not?

Definitely it is a breach, only future will know!

[Calcvictim]

Ok guys,

I read the thread but I am unclear on a couple of things.

1)is there a way to extract inquiry, identify and key files to have complete info?
1b)if so what is the method?
1c)if not what files need to be hex edited in order to insert the info, the original extraced files or the spoofed firmware?



Thanks

[lebthug]

QUOTE(Calcvictim @ Mar 16 2009, 11:47 PM)

Ok guys,

I read the thread but I am unclear on a couple of things.

1)is there a way to extract inquiry, identify and key files to have complete info?
1b)if so what is the method?
1c)if not what files need to be hex edited in order to insert the info, the original extraced files or the spoofed firmware?
Thanks

If you want full info use jungleflasher and create dummy.bin at time of key extract. The extra info is directly in dummy.bin and can't be generated from key, inquiry and identity files, at least not completely.

GiampyXBS released a utility to verify / edit the serial info with pictures of the stickers. You can use that and load your dummy.bin to check it out after u extract if u want to make sure, or to add missing info if ur unable to use the latest JF to get the complete info. Look for it in this forum...

[Calcvictim]

QUOTE(lebthug @ Mar 17 2009, 12:49 AM)

If you want full info use jungleflasher and create dummy.bin at time of key extract. The extra info is directly in dummy.bin and can't be generated from key, inquiry and identity files, at least not completely.

GiampyXBS released a utility to verify / edit the serial info with pictures of the stickers. You can use that and load your dummy.bin to check it out after u extract if u want to make sure, or to add missing info if ur unable to use the latest JF to get the complete info. Look for it in this forum...

Does the info get retained when spoofing dummy.bin into ix1.51, does it only get retained when using dvdkey32 or something else?

[fatvince]

Thanks GiampyXBS, I had the 3 files from the original modder, then used jungleflasher to create a dummy.bin, then used your tool to insert the extra information, then used jungleflasher again to spoof it to 1.51, then used dosflash to flash my drive. Couldn't have done it without you because no matter how many times i tried (50+) I just could not get my drive in the half-open state.  

[Neo_9000uk]

I have already extracted the the info from the drive using jungleflasher.. including the dummy.bin but still no extra info that i need. Looks like i will have to locate the serials myself using the pics provided at the front of this thread.

Cheers All.

[ibbi]

Inquiry

CODE

0000: 05 80 00 32 5B 00 00 00 - 50 4C 44 53 20 20 20 20 ...2[...PLDS    
0010: 44 47 2D 31 36 44 32 53 - 20 20 20 20 20 20 20 20 DG-16D2S        
0020: 37 34 38 35 30 43 41 30 - 41 31 44 36 30 38 43 47 74850CA0A1D608CG
0030: 38 34 31 39 30 33 30 32 - 33 31 55 20 20 20 00 00 8419030231U   ..
0040: 00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 ................
0050: 00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 ................

Identify

CODE

0000: C0 85 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 ................
0010: 00 00 00 00 44 36 30 38 - 43 47 38 34 31 39 30 33 ....D608CG841903
0020: 30 32 33 31 55 20 20 20 - 00 00 00 00 00 00 37 34 0231U   ......74
0030: 38 35 30 43 20 20 50 4C - 44 53 20 20 20 20 44 47 850C  PLDS    DG
0040: 2D 31 36 44 32 53 20 20 - 20 20 20 20 20 20 20 20 -16D2S          
0050: 20 20 20 20 20 20 20 20 - 20 20 20 20 20 20 00 00               ..
0060: 00 00 00 0B 00 00 00 04 - 00 02 06 00 00 00 00 00 ................
0070: 00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 ................
0080: 03 00 78 00 78 00 E3 00 - 78 00 00 00 00 00 00 00 ..x.x...x.......
0090: 00 00 00 00 00 00 00 00 - 02 02 00 00 68 00 40 00 ............h.@.
00A0: 00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 ................
00B0: 20 20 00 00                                         ..            

Drive  serial

CODE

Blank

Am I safe to play on live? I don't have my dummy.bin.. only my spoofed SAM_CFW.bin
Is it possible if i can rebuild my dvdserial?
btw my lite on is spoofed as samsung because it smoked out but i still have the drive.

p.s my xbox plays just fine so my key is correct

[HERiTAGE]

Dude, fantastic!
I've been able to return my drive back to life after trying to update to 1.51 with an incomplete dummy file.
I got the open tray error every time...

Did your process (which is impeccably well explained btw) and i got it working first time!
Seriously, you are my new hero!

Btw my dummy file was in it's structure almost exactly like the one you showed on your "proof" post from the first page.

Also, i have this a weird drive because my first XXXXXX set of numbers that are on my drive's cover are not the same i had on my dummy file... So i thought i was fucked. But i used the ones from the dummy file along with the other data retrieved from inside the drive and it worked.
Probably the fact that my xbox360 is a refurb can explain why the data is different in the drive cover? I dunno...

Anyway, muchas gracias!

[RDubbs007]

When I flashed my liteon the first time, i used xtractor to get the id files and that is all it did... the dummy.bin file that it made did not include the PCB label id or the OSN label id... it DID have the drive serial from the label though.  VERY NICE work on this program Giampy, with it I went back into my drive and collected this identification information, patched the dummy.bin with it and then made a new 1.51 with the dummy.bin files (followed by flashing in dos).

THANK YOU for this, otherwise I would have never known about it!!!

[render2k]

that would be interesting for me too, i can't read 3 digits after the first four : S4P8 xxx 00000118782

is there anyway to get these numbers back?

thx

[ToBbErT]

There are two ways to get good data serial. With a valid dump from your original firmware or using the stickers on the drive and rebuild it. There's no other method atm. Try using a magnifying-glass and bright light.

[pricemeista33]

QUOTE(render2k @ Apr 29 2009, 03:33 PM)

that would be interesting for me too, i can't read 3 digits after the first four : S4P8 xxx 00000118782

is there anyway to get these numbers back?

thx

WOW, I told someone on the Scene that I believed that M$ is inking out that information or at least portions of it on new drives. I had the same exact problem, but I just used information from any other PCB and it worked flawlessly. Only one thing though...going on Live is not encouraged as this information is now different than the original so the ban hammer will be coming. I don't go Live with that console anyways. Hope that helps someone.

[pricemeista33]

QUOTE(GiampyXBS @ Feb 8 2009, 12:35 AM)

does JF give some deep infos about it?
did u use the right patched dummy file?

Thank you MickRick...i was lucky  

Hey sorry I didn't reply for some time as it was a faulty drive that I had. I knew it had to be after trying everything in the arsenal and it still failed. I have replaced the drive and it's all good now thanks to Giampy. Thanks man

[render2k]

here's what i want to do ...... i have a Xbox360, the original drive was a GDR-3120L-47 (bricked it seems) and the KEY from that Box, now i have this liteon drive (without the Dumps unfortunaly ..... ) I cannot read the PCB Sticker to repair the Serial, so what can i do now to make this drive work on the Xbox360?

thx

[paul543]

I'm curious what is causing incomplete drive serial numbers.
Could it be the new xboxes manufactured in March 2009?

I've no problem getting a valid key, but can't get the drive serial. I tried dosflash (dos) , dosflash (windows), jungleflasher and tried via USB and DB9 connection. No luck. I did get the key each and every time, but invalid serial info.

Could this be an error on my part? Faulty equipment or whatever? I was under the impression if one get's the key, then the drive serial data should also work.

Thanks