-
First of all, hi to all. My first post.
Second, sorry for my bad english, i hope to be quite readable in this post.
This can be (potentially) a method for recreate (partially/full) the "Drive Serial" data for those of who missed it. The fact to be fully or partially recreatable depends on the help from the user here. So read it please.
All you know that for the correct extraction of data from liteon, updated tools are required (such as DosFlash 1.7+,DVDKey 1.2+, DVDKey32 0.7+, Firmtool 1.3.1+ and so on). If the data was extracted with previous tools the "Drive serial" isn't complete for this DVD reader...eg. Firmtool 1.3.1+ report it with a warning : lite-on serial appears to be partially incomplete.
I flashed my drive before that those updated tool-set was available, so i was trapped in the net of who have a good local iXtreme, but a (future) problematic one in LIVE!
I decided to try to solve this question, so Googling for it, i was surprised that no info about the "Drive Serial" can be retrieved...starting doing it myself (or at least try to do it).
So here is the part.
The "Drive Serial" can be read from 0x1ff00 in the dummy.bin file created by the tool or directly from the target spoofed firmware, with an hex editor or using jungleflasher (load from dumped data).
A typical incomplete "Drive Serial" looks like this:
CODE
0000: 44 36 30 38 43 47 38 33 - SS SS SS SS SS SS SS SS D608CG83SSSSSSSS
0010: 31 20 20 20 FF FF FF FF - FF FF FF FF FF FF FF FF 1 ............
0020: FF FF FF FF FF FF FF FF - 41 30 FF FF FF FF FF FF ........A0......
0030: FF FF FF FF FF FF FF FF - FF FF FF FF FF FF FF FF ................
0040: FF FF FF FF FF FF FF FF - FF FF FF FF 41 31 FF FF ............A1..
SS SS SS = My hidden data.
"FF FF FF ..." may be "58 58 58 ..." if the serial data is read from the target firmware prepared with firmtool 1.3.1+.
Searching for those dumps over internet i found some interesting patterns and source for intuition. So found that
a typical complete "Drive Serial" can be this (call this A0 version) :
CODE
0000: 44 36 30 38 43 47 38 33 - SS SS SS SS SS SS SS SS D608CG83SSSSSSSS
0010: 31 20 20 20 FF FF FF FF - YY YY YY YY YY YY YY YY 1 ....YYYYYYYY
0020: YY YY YY YY YY YY 58 58 - 41 30 FF FF ZZ ZZ ZZ ZZ YYYYYYXXA0..ZZZZ
0030: ZZ ZZ ZZ ZZ ZZ ZZ ZZ ZZ - ZZ ZZ ZZ ZZ ZZ ZZ 00 00 ZZZZZZZZZZZZZZ..
0040: FF FF FF FF FF FF FF FF - FF FF FF FF 41 31 FF FF ............A1..
or this (call this non A0 version):
CODE
0000: 44 36 30 38 43 47 38 33 - SS SS SS SS SS SS SS SS D608CG83SSSSSSSS
0010: 31 20 20 20 FF FF FF FF - YY YY YY YY YY YY YY YY 1 ....YYYYYYYY
0020: YY YY YY YY YY YY 58 58 - KK KK FF FF ZZ ZZ ZZ ZZ YYYYYYXX....ZZZZ
0030: ZZ ZZ ZZ ZZ ZZ ZZ ZZ ZZ - ZZ ZZ ZZ ZZ ZZ ZZ ZZ ZZ ZZZZZZZZZZZZZZZZ
0040: FF FF FF FF FF FF FF FF - FF FF FF FF 41 31 FF FF ............A1..
So i was thinking that a "Serial Number" is an identifier and must be visible in some manner, otherwise it was a key !!! Not thinking so bad...
Let's go with order.
The ...SSSSSSSS... data is surely present from the dump, it's our DVD Serial Number printed here (except for the last number that seems to be always 0 or 1):
(IMG:http://www.freeimagehosting.net/uploads/cfc467676a.jpg)
The YYYYYYYYYYYYYYXX is the optical serial number, is always 16 chars length and (from my dumps) it always end up with "XX". The most of times it start with "8" (eg 8C,8G,8F).
It can be retrieved here :
(IMG:http://www.freeimagehosting.net/uploads/04be7367a5.jpg)
The ZZZZZZZZZZZZZZZZZZ[ZZ] is the dvd-mobo serial number and is slightly different, it depends on the fact that 0x0028 is "A0" or something else.
If it's "A0" then the length is always (from my dumps) 18 chars.
If it's not "A0" then the length is always (from my dumps) 20 chars.
But it always start with "S4P8"
It can be retrieved removing both covers of the dvd unit and face it up (with the optical led up). Pay attention at the led/photoled, be carefull : do no touch, do not expose to direct strength light, do not incinerate for who smokes.. (IMG:style_emoticons/default/biggrin.gif) ..and bla bla bla.
The photo is a bit dark but you can find it easly :
(IMG:http://www.freeimagehosting.net/uploads/cf69428a67.jpg)
Now the questions directed to all contributors are 2 :
1) A0 or non A0?
I found this value in the my incomplete dump (dummy.bin)
CODE
...
0020: FF FF FF FF FF FF FF FF - 41 30 FF FF FF FF FF FF ........A0......
...
Is this value dumped or autogenerated from the old tools? because if it is dumped we have 1 more info directly from the "problematic" dummy.bin/spoofed firmware...if it is autogenerated, we need to know how to retrieve it! (Remember that this can help us to find out the length of the dvd-mobo sn, read the doubt at the point 2).
Can someone point this question to the attention of the programmers? (eg. Geremia, C4Eva...)
2) The perfidious number
Looking on the dvd-mobo label i have a second number (2 digits) in bottom-right corner
(IMG:http://www.freeimagehosting.net/uploads/ca19952c1a.jpg)
I called it perfidious because my label sn length is 18...so i'm not sure if i need to add those 2 digits (depends on the dump/generation of the previously "A0") and create a 20 chars length sn or if the sn is complete.
Can any of you post your experience related to those questions?
For any of you that have a correct dump (18/20 chars, A0/not A0 in the dummy.bin) : can check if the "perfidius" number is the last part of the dvd-mobo sn or if the entire sn is simply write in the 2 rows of the label and the perfidious is not correlated to sn?(with the box opened for the hack,removing both covers and write down a number take approximatively 15 seconds for you, but this is very helpfull for us)
The most we are, the better is for the complete "Drive Serial" recreation!
Thank you for your contribution.
Have a good hack.
This post has been edited by GiampyXBS: Jan 26 2009, 08:59 AM
-
noone is interested in solve this kind of problem?
possible?
-
I am, though I used the newer flasher and still have mine.
I just saw this post and it tickled my fancy, I've been looking around on the net for Info.
I'll post back if I find anything, but I think it's a great Idea you have.
-
QUOTE(originalmacnut @ Jan 26 2009, 10:48 PM)

I am, though I used the newer flasher and still have mine.
I just saw this post and it tickled my fancy, I've been looking around on the net for Info.
I'll post back if I find anything, but I think it's a great Idea you have.
Thank you originalmacnut, i'll wait your here ...
-
Nice post, thanks for the info... It will be a relief to those who may have lost their info using Xtractor 2.7 etc....
This post has been edited by podger: Jan 27 2009, 03:14 AM
-
Nice find bud, very nice find.
Well done.
For the record, Ive verified this, and it is infact 100% true.
-
QUOTE(GiampyXBS @ Jan 26 2009, 02:42 PM)

noone is interested in solve this kind of problem?
possible?
Yes, it has been brought to the attention of the developers. Thank you so much for your efforts!
-
-
Does that mean we won't need a Connectivity kit?
-
QUOTE(ibbi @ Jan 27 2009, 05:13 AM)

Does that mean we won't need a Connectivity kit?
NO, the key must always be dumped via COM & SATA!
This mean that anyone who lose his drive serial data could regenerate it and hope to (not) be banned such any other friend with iXtreme on liteon !
-
QUOTE(OggyUK @ Jan 27 2009, 03:51 AM)

Nice find bud, very nice find.
Well done.
For the record, Ive verified this, and it is infact 100% true.
I have no words to thank OggyUK, he verified the process and, expecially, submit this to the attention of the developers !
Thank you...now i can relax a bit.
-
Can you get your drive Serial With This? If so This needs to be Posted TO The tuturials imma check it out and see 4 myself thnaks tho
-
Ok, heres a little more visual proof.
QUOTE
0000: 44 36 30 38 43 47 38 33 - 32 39 30 33 30 30 45 39 D608CG83290300E9
0010: 30 20 20 20 FF FF FF FF - 38 47 32 35 30 37 30 34 0 ....8G250704
0020: 31 37 41 33 31 34 58 58 - 41 30 FF FF 53 34 50 38 17A314XXA0..S4P8
0030: 38 30 31 30 30 30 30 30 - 31 33 36 31 32 32 00 00 80100000136122..
0040: FF FF FF FF FF FF FF FF - FF FF FF FF 41 31 FF FF ............A1..
(IMG:http://i330.photobucket.com/albums/l432/OggyBST/n1222230561_292267_7458.jpg)
And
(IMG:http://i330.photobucket.com/albums/l432/OggyBST/n1222230561_292266_3592.jpg)
-
+1
Well done Giampy!
-
Giampy you were right, after discussion last night I checked. I can confirm of all the reads of the drive I did only 1 contained the right-full information. I have opened my drive and checked all matching info and will now be reflashing my drive with the correct firmware.
Thanks Giampy
-
I'm happy to help some of you...but just another question...
Is there someone that have this "particular" type of dummy.bin (at 0x1ff00):
CODE
0000: 44 36 30 38 43 47 38 33 - 30 38 31 30 30 30 57 35 D608CG83081000W5
0010: 31 20 20 20 FF FF FF FF - 38 47 30 39 31 36 31 38 1 ....8G091618
0020: 31 37 32 35 31 34 58 58 - A1 89 FF FF 53 34 50 38 172514XX....S4P8
0030: 37 32 33 30 30 30 30 30 - 31 37 39 39 31 37 36 34 7230000017991764
0040: FF FF FF FF FF FF FF FF - FF FF FF FF 41 31 FF FF ............A1..
It's particular because:
1) "A0" is missing after "XX"
2) The S4P8... sn is 20 chars length
If so...can check what's write on the sticks and post a result?
Thank you!
-
Thankyou GiampyXBS, looking forward for the outcome!
-
so guys if i used JF to read my key and saved my key, inquiry and identify. but did not generate a dummy.bin immidiately. but did this later on in the "firmwaretool 32"tab by using the "load from dump files" button. will that be fine???
I used the first version of JF, should i be save or do i have these problems in my firmware as well?
-
dangerpaki:
that "load from dump files" has moved... Unfortunately, it was incorrectly used in tutorials. It is only intended for picking up old files..
Good news tho with Giampy discovery, you can rebuild you serial data, if you are willing to open your DVD drive...
-
Off topic: I wonder what happens when the QR barcode is scanned with a Nokia Mobile phone.
-
My N95 didnt pick them up, first thing I tried
-
"A0" probably is not necessary as it's already locate in ixtreme fw...
-
QUOTE(OggyUK @ Jan 27 2009, 11:53 PM)

My N95 didnt pick them up, first thing I tried
Hmm, wonder what they are there for then.
-
QUOTE(jack_herer @ Jan 27 2009, 10:57 PM)

"A0" probably is not necessary as it's already locate in ixtreme fw...
"A0A1" is also the firm revision on the stick,it has its own sense...the goal is to reproduce the original complete sn.
May exist a drive with only "A1" firm rev. and different "S4P8" serial number length?
Noone has the strage dump above in the dummy.bin?
Came on people, don't be shy...
-
i am not to sure what this means to me. I have dummy.bin, hacked.bin, key.bin, identify.bin and inquiry.bin. I did not do it my self but had a modder do it for me as i didn't want to take a chance at my first 360. So am i safe? as i can see from reading the posts is that dummy.bin = drive serial. So if i have the dummy files then i still should be alright.
edit
i reread the thread so it dose not matter if i have a dummy file, as it maybe incomplete. How can i check this if mine is incomplete or complete?
P.S I thought that M$ can't read the firmware so if they can't then this is not needed. correct me if i am wrong!!
This post has been edited by wendy360: Jan 28 2009, 02:42 AM
-
QUOTE(wendy360 @ Jan 28 2009, 03:29 AM)

i am not to sure what this means to me. I have dummy.bin, hacked.bin, key.bin, identify.bin and inquiry.bin. I did not do it my self but had a modder do it for me as i didn't want to take a chance at my first 360. So am i safe? as i can see from reading the posts is that dummy.bin = drive serial. So if i have the dummy files then i still should be alright.
edit
i reread the thread so it dose not matter if i have a dummy file, as it maybe incomplete. How can i check this if mine is incomplete or complete?
P.S I thought that M$ can't read the firmware so if they can't then this is not needed. correct me if i am wrong!!
Load up the latest JungleFlasher (0.0.43 Beta), select the tab Firmware Tool 32 and click Load Source Firmware on the right hand side. Select your Dummy.bin, and if you get a message saying Dummy.bin is missing some drive specific information youre Dummy is incomplete.
-
I posted this question about 3 days ago but can't seem to locate it in the forums to check for any responses. I asked this same question concerning the "serial information" within the dump. I have compared information from three or four different dumps and found out that there was indeed a difference in the key info located in the serial. I don't know why this was or what caused it or anything but wish for someone to pinpoint what the cause is. Now I'm having the E65, 66 error when I successfully flash my MS25 to a Lite-On as Jungle Flasher verifies the write as OK. Dunno what's the freakin problem but I want to use my MS25 as my Lite-On is jacked and I thought that the key, identify, and inquiry files were extracted properly with "360Xtractor" or maybe this software is definitely the problem. I really need to know if I can hex edit specific information in order for my drive to operate properly.
-
Alternatively you can put the latest Firmtool (1.3.1 I think) and Make iXtreme firmware.bat in the same folder as your Dummy.bin and hacked iXtreme Lite-on firmware. Double click Make iXtreme firmware.bat, follow the instructions, and if you get:
***Warning***
Lite-on serial appears to be partially incomplete.
You have an incomplete Dummy.bin.
The question is how does one avoid this and ensure a complete serial extraction every time?
-
QUOTE(wendy360 @ Jan 28 2009, 02:29 AM)

...
P.S I thought that M$ can't read the firmware so if they can't then this is not needed. correct me if i am wrong!!
if you are sure, then why you worry about this?
the reality is that we know very little about microsoft checks (apart the fact that the LiteOn seems to be not dumpable (is it true?...may be...or not...))
QUOTE(WildBomber @ Jan 28 2009, 03:01 AM)

Load up the latest JungleFlasher (0.0.43 Beta), select the tab Firmware Tool 32 and click Load Source Firmware on the right hand side. Select your Dummy.bin, and if you get a message saying Dummy.bin is missing some drive specific information youre Dummy is incomplete.
...or manually open your dummy.bin with an hex editor at 0x1ff00 and read the first post
-
i did get a message in jungleflasher. i hexed the dummy file.
after 1ff00 which is the the drive key or whatever
all i see are YYYYYYY from 1ff10 to 1ff40 and there is a A0 and A1 in between; So this means that my dummy.bin is incomplete right?
Since i did not flash it my self, what can i do? i don't really want to open the xbox and the drive to get all the info. I do not think the modder that this for me will do this. It was to much hassel then it was worth to do it myself. It would have cost me the same amount of money to buy all the equipment and flash it. Or i just pay someguy the same amount of money and get it done without the hasselso somthing not working or mebreaking the xbox.
This post has been edited by wendy360: Jan 28 2009, 03:26 AM
-
QUOTE(GiampyXBS @ Jan 28 2009, 12:42 AM)

May exist a drive with only "A1" firm rev. and different "S4P8" serial number length?
I don't think so. check your spoofed fw and A0 A1 will be always located in the serial string.
my opinion is that complete string should be 20 chars length, but it's impossible to know for sure,
because ixtreme serial has 18 chars, but that string -seems- to be missing of 2 chars...
-
QUOTE(wendy360 @ Jan 28 2009, 04:21 AM)

i did get a message in jungleflasher. i hexed the dummy file.
after 1ff00 which is the the drive key or whatever
all i see are YYYYYYY from 1ff10 to 1ff40 and there is a A0 and A1 in between; So this means that my dummy.bin is incomplete right?
Since i did not flash it my self, what can i do? i don't really want to open the xbox and the drive to get all the info. I do not think the modder that this for me will do this. It was to much hassel then it was worth to do it myself. It would have cost me the same amount of money to buy all the equipment and flash it. Or i just pay someguy the same amount of money and get it done without the hasselso somthing not working or mebreaking the xbox.
If you don't want to open your drive and follow the information given by GiampyXBS, then your only other option is to sell it for the same price as it would cost you to buy a new Xbox, plus the amount it would cost you to get it flashed and do it again, this time bringing this thread to your flasher's attention.
-
yeah that sounds like a good idea, but who is to say that this means that i will get banned for sure? I think this is not a big threat beacsue if M$ could read this then why can't they read other things about the FW and ban people, If M$ could read the drive FW then this would not matter as they would just check other things that are different from the original to ban people.
This post has been edited by wendy360: Jan 28 2009, 04:11 AM
-
QUOTE(wendy360 @ Jan 28 2009, 03:21 AM)

all i see are YYYYYYY from 1ff10 to 1ff40 and there is a A0 and A1 in between; So this means that my dummy.bin is incomplete right?
Sorry, yes
QUOTE(wendy360 @ Jan 28 2009, 03:21 AM)

Since i did not flash it my self, what can i do? i don't really want to open the xbox and the drive to get all the info. I do not think the modder that this for me will do this. It was to much hassel then it was worth to do it myself. It would have cost me the same amount of money to buy all the equipment and flash it. Or i just pay someguy the same amount of money and get it done without the hasselso somthing not working or mebreaking the xbox.
To flash your liteon, you need only a sata PC (or a sata card) and your drive data(key,inquiry,identify and dummy).
Someone say that have bad serials data it's not a problem, but if you like to restore them you need to open your box!
-
That is pimp!
-
Quick Noob guide to identifying and repairing.
-
Dummy.bin says this:
0000: 44 36 30 38 43 47 38 32 - 34 38 30 39 30 42 4B 39 D608CG8248090BK9
0010: 30 20 20 20 FF FF FF FF - FF FF FF FF FF FF FF FF 0 ............
0020: FF FF FF FF FF FF FF FF - 41 30 FF FF FF FF FF FF ........A0......
0030: FF FF FF FF FF FF FF FF - FF FF FF FF FF FF FF FF ................
0040: FF FF FF FF FF FF FF FF - FF FF FF FF 41 31 FF FF ............A1..
but when i press spoof source to firmware, jf says this:
0000: 44 36 30 38 43 47 38 32 - 34 38 30 39 30 42 4B 39 D608CG8248090BK9
0010: 30 20 20 20 FF FF FF FF - 38 47 33 31 30 37 35 30 0 ....8G310750
0020: 31 37 45 34 31 34 58 58 - 41 30 FF FF 53 34 50 38 17E414XXA0..S4P8
0030: 38 31 34 30 30 30 30 30 - 31 31 34 34 34 33 00 00 81400000114443..
0040: FF FF FF FF FF FF FF FF - FF FF FF FF 41 31 FF FF ............A1..
Is the drive flashed with the correct serial, or do i need to dissamble it again?
Program I used to get the key, inquiry & identify: xtractor reader 2.7
Program I used to make the dummy.bin: JFv043b
Thanks in advance,
-
QUOTE(UseN3t @ Jan 28 2009, 12:34 PM)

Dummy.bin says this:
0000: 44 36 30 38 43 47 38 32 - 34 38 30 39 30 42 4B 39 D608CG8248090BK9
0010: 30 20 20 20 FF FF FF FF - FF FF FF FF FF FF FF FF 0 ............
0020: FF FF FF FF FF FF FF FF - 41 30 FF FF FF FF FF FF ........A0......
0030: FF FF FF FF FF FF FF FF - FF FF FF FF FF FF FF FF ................
0040: FF FF FF FF FF FF FF FF - FF FF FF FF 41 31 FF FF ............A1..
but when i press spoof source to firmware, jf says this:
0000: 44 36 30 38 43 47 38 32 - 34 38 30 39 30 42 4B 39 D608CG8248090BK9
0010: 30 20 20 20 FF FF FF FF - 38 47 33 31 30 37 35 30 0 ....8G310750
0020: 31 37 45 34 31 34 58 58 - 41 30 FF FF 53 34 50 38 17E414XXA0..S4P8
0030: 38 31 34 30 30 30 30 30 - 31 31 34 34 34 33 00 00 81400000114443..
0040: FF FF FF FF FF FF FF FF - FF FF FF FF 41 31 FF FF ............A1..
Is the drive flashed with the correct serial, or do i need to dissamble it again?
Program I used to get the key, inquiry & identify: xtractor reader 2.7
Program I used to make the dummy.bin: JFv043b
Thanks in advance,
A couple of big giveaways that its not correct.
1 - It wasnt present in Source, so, YOUR unique data couldnt have been copied
2 - You used Xtractor Reader - this doesnt issue the cdb's to get 01ff00 data in full - Its been discussed many times before that you shouldnt obtain data using this
3 - JungleFlasher states when loading that all serial data isnt present when loading key/inq/ident and tells you what to use to dump again.
-
Using OggyUK's serial section as an example, when I manually restored 1 of my incomplete dummy files, the last part in row 0030 reads FF FF instead of 00 00.
For example:
0000: 44 36 30 38 43 47 38 33 - 32 39 30 33 30 30 45 39 D608CG83290300E9
0010: 30 20 20 20 FF FF FF FF - 38 47 32 35 30 37 30 34 0 ....8G250704
0020: 31 37 41 33 31 34 58 58 - 41 30 FF FF 53 34 50 38 17A314XXA0..S4P8
0030: 38 30 31 30 30 30 30 30 - 31 33 36 31 32 32 FF FF 80100000136122..
0040: FF FF FF FF FF FF FF FF - FF FF FF FF 41 31 FF FF ............A1..
instead of
0000: 44 36 30 38 43 47 38 33 - 32 39 30 33 30 30 45 39 D608CG83290300E9
0010: 30 20 20 20 FF FF FF FF - 38 47 32 35 30 37 30 34 0 ....8G250704
0020: 31 37 41 33 31 34 58 58 - 41 30 FF FF 53 34 50 38 17A314XXA0..S4P8
0030: 38 30 31 30 30 30 30 30 - 31 33 36 31 32 32 00 00 80100000136122..
0040: FF FF FF FF FF FF FF FF - FF FF FF FF 41 31 FF FF ............A1..
which all the examples of complete dummy files seem to show.
I've opened up 1 of my complete dummy files in a hex editor to test, and again it shows the values 00 00 in that particular section. Is there anything I'm doing wrong? How do I get it to read 00 00 instead of FF FF?
-
QUOTE(UseN3t @ Jan 28 2009, 12:34 PM)

Dummy.bin says this:
0000: 44 36 30 38 43 47 38 32 - 34 38 30 39 30 42 4B 39 D608CG8248090BK9
0010: 30 20 20 20 FF FF FF FF - FF FF FF FF FF FF FF FF 0 ............
0020: FF FF FF FF FF FF FF FF - 41 30 FF FF FF FF FF FF ........A0......
0030: FF FF FF FF FF FF FF FF - FF FF FF FF FF FF FF FF ................
0040: FF FF FF FF FF FF FF FF - FF FF FF FF 41 31 FF FF ............A1..
but when i press spoof source to firmware, jf says this:
0000: 44 36 30 38 43 47 38 32 - 34 38 30 39 30 42 4B 39 D608CG8248090BK9
0010: 30 20 20 20 FF FF FF FF - 38 47 33 31 30 37 35 30 0 ....8G310750
0020: 31 37 45 34 31 34 58 58 - 41 30 FF FF 53 34 50 38 17E414XXA0..S4P8
0030: 38 31 34 30 30 30 30 30 - 31 31 34 34 34 33 00 00 81400000114443..
0040: FF FF FF FF FF FF FF FF - FF FF FF FF 41 31 FF FF ............A1..
Is the drive flashed with the correct serial, or do i need to dissamble it again?
Program I used to get the key, inquiry & identify: xtractor reader 2.7
Program I used to make the dummy.bin: JFv043b
Thanks in advance,
I could be wrong but from memory I think that may be the serial info contained in the Lite on firmware. Open the target firmware (Lite on 1.5ixtreme)in Jf and check info. That happened to me on 1 spoofing where the ixtreme info was placed in my Dummy.bin info.
-
QUOTE(Demonmirc @ Jan 28 2009, 09:04 AM)

I could be wrong but from memory I think that may be the serial info contained in the Lite on firmware. Open the target firmware (Lite on 1.5ixtreme)in Jf and check info. That happened to me on 1 spoofing where the ixtreme info was placed in my Dummy.bin info.
Yeah you are right.
I opened the LIteon ixtreme as target in JF and there was valid serial info in there. I then used a dummy without a serial as source and spoofed.The serial information in the target firmware stayed the same.
When I did the same steps using a dummy.bin with valid serial as a source, the target serial was over written.
-
Anyone think there will be a CLI release to fix dummy.bin?
-
I wish I could edit my posts, (mod merge?)
Right I found:
On your DVD case you have a HW ver, mine reads A0A1. Within my dummy.bin A0 and A1 are present.
My drive serial is 17 characters. However only 16 are present in my dummy.bin. The last char on my sticker is a 1. On the dummy.bin it is a 0
I know its mentioned in the first post, but no-one has elaborated, why this happens?
Has anyone else got 1 on there serial changed to a 0?
@WildBomber: I got that also, oggy's ss shows a (.) for FF values, where my hex editor shows Y values as the text string. However 00 is also a . so you will no see any differnace when using text only. Simply change the hex value to 00 00, hope that makes sense.
This post has been edited by jt1: Jan 28 2009, 09:08 PM
-
QUOTE(jt1 @ Jan 28 2009, 10:33 PM)

I wish I could edit my posts, (mod merge?)
Right I found:
On your DVD case you have a HW ver, mine reads A0A1. Within my dummy.bin A0 and A1 are present.
My drive serial is 17 characters. However only 16 are present in my dummy.bin. The last char on my sticker is a 1. On the dummy.bin it is a 0
I know its mentioned in the first post, but no-one has elaborated, why this happens?
Has anyone else got 1 on there serial changed to a 0?
@WildBomber: I got that also, oggy's ss shows a (.) for FF values, where my hex editor shows Y values as the text string. However 00 is also a . so you will no see any differnace when using text only. Simply change the hex value to 00 00, hope that makes sense.
This is crazy as the 360Xtractor tool has jumbled all of my information up like the serial number. It completely changed the last 7 characters and rearranged my model no., HW Ver., and FW Ver. for example: I have FW ver. 74850C, but when I opened it up in Hex Workshop, I see 4508C7 and the same for the other information. I need a tut on what needs to be done in Hex Workshop though so I can edit the information as it should appear for the mobo to recognize.
Hey Oggy if you know which information is suppose to go first and which is to precede please post.
-
QUOTE(pricemeista33 @ Jan 29 2009, 02:40 AM)

This is crazy as the 360Xtractor tool has jumbled all of my information up like the serial number. It completely changed the last 7 characters and rearranged my model no., HW Ver., and FW Ver. for example: I have FW ver. 74850C, but when I opened it up in Hex Workshop, I see 4508C7 and the same for the other information. I need a tut on what needs to be done in Hex Workshop though so I can edit the information as it should appear for the mobo to recognize.
Hey Oggy if you know which information is suppose to go first and which is to precede please post.
Dude just read the first post, explains everything.
-
QUOTE(mucho181 @ Jan 29 2009, 04:30 PM)

...than i put my drive back to the 360 an it plays no orig games or backups.
Wrong key sympton...
Try if it can read a DVD video....if not may be the optical len...
-
Has anyone done a hex compare on a CFW.bin to check if a jf/dvdkey32/dosflash full valid dump to a hex edited dummy cfw. Do they match are are there still differances?
Just wondering if the serial is the only missing information. Ta.
-
QUOTE(GiampyXBS @ Jan 29 2009, 07:14 PM)

Wrong key sympton...
Try if it can read a DVD video....if not may be the optical len...
DVD's works well ?? hmm 2 bad ! 
I will order then a samsung ms28 an replace it with my bricked liteon
anyway thx
-
QUOTE(mucho181 @ Jan 29 2009, 11:45 PM)

I will order then a samsung ms28 an replace it with my bricked liteon
Its pretty much impossible to brick your liteon aslong as youve dumped your files correctly. However if you havnt dumped them youve lost your whole xbox not just your drive! Make sure you press the copy source to target in jungle flash. Or you can make a cfw in firmtool by typing firmtool dummy.bin hackedliteon.bin
where hackedliton.bin is your ix1.5 fw.
Your dumps look okay. Its probly a matter of a bad customfirmware.
Try doing it in dos.
www.sn.im/liteon-dos-jt1 www.sn.im/liteon-dos-jt1-nopdf
-
QUOTE(jt1 @ Jan 30 2009, 01:53 AM)

Its pretty much impossible to brick your liteon aslong as youve dumped your files correctly. However if you havnt dumped them youve lost your whole xbox not just your drive! Make sure you press the copy source to target in jungle flash. Or you can make a cfw in firmtool by typing firmtool dummy.bin hackedliteon.bin
where hackedliton.bin is your ix1.5 fw.
Your dumps look okay. Its probly a matter of a bad customfirmware.
Try doing it in dos.
www.sn.im/liteon-dos-jt1 www.sn.im/liteon-dos-jt1-nopdf
so ok i'd did it in dos with the new frimtool 1.3
an it says
**** Success *****
drive key copied
drive serial copied
**** WARNING ****
lite-on serial appears to be partially incomplete ?????
your hacked frimware i now ready to be flashed.
------
so ok anyway i flashed it with my new bin an the same...
than i put in manualy the drive serial like here in the manual (first post)
and it says
**** Success *****
drive key copied
drive serial copied
your hacked frimware i now ready to be flashed.
------
Ok flashed it and again the same thing all flahs were perfect or ok.
i'm really confused cause on day bevor its work perfectly with the liteon to by an elite xbox but is the biggest problem its not mine
i try to make it for an friend with CK3 Pro and the Probe. wich option do i got ???
Thx for trying to helping me out *thumbs up*
QUOTE(jt1 @ Jan 28 2009, 07:50 PM)

Anyone think there will be a CLI release to fix dummy.bin?
may this "CLI release" (i dont know what it is) will help me out ?
-
QUOTE(mucho181 @ Jan 29 2009, 04:30 PM)

hey first sorry for my bad english im from germany,
Can someone tell that i did evrything right ? i flashed my drive with jf 0.0.26 get the key.bin, inq.bin, and id.bin than i load all them to build a dummy file und spoofed it with the ix15-lite. evrything was great no problems etc. than i'v erased the drive and flash it evrything was ok. than i put my drive back to the 360 an it plays no orig games or backups. i build antoher dummy and flashed the drive again an nothing changed.
her is my log from jugle flasher
~~~~~~~~~~~~~~~
JungleFlasher 0.0.26 Beta
Session Started Wed Jan 28 19:35:56 2009
Found 6 I/O Ports.
Found 2 Com Ports.
Found 7 windows drives.
Found 0 CD/DVD drives.
Sending DVDKey request to I/O port 0xE100 and COM3
I have this EXACT SAME PROBLEM and please don't tell me to read the first post as if I hadn't done so already. I really believe that it's the INQUIRY information if you take a look at how the info is rearranged, ie. PLDS, 74850C, and DG-16D2S is all written as:
47 58C0 LPSD GD
1-D6S2
If there's anyone out there who will either write up a quick "Hex Workshop", "as that's what I'm using", tut or post what we need to do in order to get our information as it should be so the Lite-On can perform once again with iX1.5 and it would be greatly appreciated.
-
QUOTE(mucho181 @ Jan 30 2009, 05:13 AM)

QUOTE(pricemeista33 @ Jan 30 2009, 05:03 AM)

I have this EXACT SAME PROBLEM and please don't tell me to read the first post as if I hadn't done so already. I really believe that it's the INQUIRY information if you take a look at how the info is rearranged, ie. PLDS, 74850C, and DG-16D2S is all written as:
47 58C0 LPSD GD
1-D6S2
If there's anyone out there who will either write up a quick "Hex Workshop", "as that's what I'm using", tut or post what we need to do in order to get our information as it should be so the Lite-On can perform once again with iX1.5 and it would be greatly appreciated.
I will tomorrow try to write the inq.bin in right orde to see what happen it cant be worster ....
@pricemeista: give me a couple of days i'll try to make a small app to check/patch the Serial Data, which is what we're talking on.
@pricemeista & mucho181:
1) The identify (not the inquiry) info came in a byte-swapped word (2 bytes swapped) directly from the bus,most info comes in this manner from different bus of different devices. Also all our inquire data are byte-swapped, so it's right.
2) Changing your serial info probably doesn't resume the drive, the only sensible parameter from the drive and the box seems to be the dvd-key, so...
3) Have you dumped the key only once? have you only 1 key.bin? more than once? from the same app or from different apps (in this case you can compare the key.bin data)?
4) Try to hex view at 0xA030 of the spoofed firm, you MUST find your key, if it's not there, there was a problem in the spoofing procedure with your app. If it's there ...sorry but i'm thinking that your key is wrong
...
Wrong key sympton : the box doesn't play backup & original games, it plays only DVD video (for which the de/encryption is not required, i suppose, so the key isn't needed)
-
(errata corrige,can't edit)
QUOTE(GiampyXBS @ Jan 30 2009, 07:35 AM)

Try to hex view at 0xA030 of the spoofed
Dummy.bin, you MUST find your key, if it's not there, there was a problem in the spoofing procedure with your app. If it's there ...sorry but i'm thinking that your key is wrong

...
-
Does this serial data looks good??
0000: 44 36 30 38 43 47 38 33 - 31 38 31 36 30 30 55 58 D608CG83181600UX
0010: 31 20 20 20 FF FF FF FF - 38 47 32 31 31 36 33 32 1 ....8G211632
0020: 31 37 44 35 31 34 58 58 - 41 30 FF FF 53 34 50 38 17D514XXA0..S4P8
0030: 37 32 39 30 30 30 30 30 - 32 32 33 39 33 31 00 00 72900000223931..
0040: FF FF FF FF FF FF FF FF - FF FF FF FF 41 31 FF FF ............A1..
-
QUOTE(gaatjenixaan @ Jan 30 2009, 08:14 AM)

Does this serial data looks good??
0000: 44 36 30 38 43 47 38 33 - 31 38 31 36 30 30 55 58 D608CG83181600UX
0010: 31 20 20 20 FF FF FF FF - 38 47 32 31 31 36 33 32 1 ....8G211632
0020: 31 37 44 35 31 34 58 58 - 41 30 FF FF 53 34 50 38 17D514XXA0..S4P8
0030: 37 32 39 30 30 30 30 30 - 32 32 33 39 33 31 00 00 72900000223931..
0040: FF FF FF FF FF FF FF FF - FF FF FF FF 41 31 FF FF ............A1..
Yes, that looks good.
-
QUOTE(mucho181 @ Jan 30 2009, 02:40 AM)

may this "CLI release" (i dont know what it is) will help me out ?
CLI, I was just refering to a command line interface to save users hex editing. Turns out its not that hard to do! So just forget I said that. (alough it would be good!)
So it wouldnt help you saying you have hexed it allready. It looks as if your key is invalid, could you be using a key off the wrong xbox possibly? Other than that youve gto a wrong dump. The firmware is not dependant on the full serial information. But you MUST have the right key!
@gaatjenixaan: Looks fine, you can compare it to oggys post.
-
I had the weirdest thing, i digged out several dummy´s with JungleFlasher .26 BETA on different drives, JF logs shows the drive serials obtained perfectly.
Still JF has failed to add the information into dummy.bin, and this happened on 5 different machines/drives.
Main thing is, the complete drive serial is located at JF.log´s, cause i did every drive read in different folder and after dumping the bins and after creating dummy´s i saved the whole dir´s with jf.log as .zip.
I compared those jf.log serials on dvd drive labels and they match.
So now i just dug out the jf.log´s, inserted the drive serials to liteon_CFW.bin that was created at the time (this way no other drive information was not changed but that drive serial) So now the firmwares contains also the correct drive serials.
Dunno, seems like there has been something fishy at that 1st beta of Jungleflasher cause the updated beta reads and saves drive serials perfectly.
-
QUOTE(GiampyXBS @ Jan 30 2009, 08:53 AM)

(errata corrige,can't edit)
here is the Hex edit from the hacked.bin

an here the dummy.bin

i think it would be better if i send the box to m$ cause the waranty seal is good
but thanks 4 all
-
i think so too because my first drive i've flashed was with the serial prot (com1) and this one works well and the second one (this one wich is bricked ?) was withe the USB (com3) port so there is maybe a big Problem with the USB port an JF 0.026 hmm ......
-
QUOTE(mucho181 @ Jan 30 2009, 04:43 PM)

i think so too because my first drive i've flashed was with the serial prot (com1) and this one works well and the second one (this one wich is bricked ?) was withe the USB (com3) port so there is maybe a big Problem with the USB port an JF 0.026 hmm ......
i dont think is a JF related problem, but how windows handle and menage the usb-com adapters (emulating a com port)
The road to retrieve the key from the Xbox mobo exists but is a milestone!
-Using a TimeAttack (hardware...infectus?) the get a valid sign and reboot the xbox in the base (no patched) kernel
-Starting with an old kernel (1888)
-Upgrade to 4532 (and another version ... may be 4553?)
-Prepare the King Kong Exploit disk
-With the KK disk boot into linux
-Dump fuses and keys...
-Upgrade gradually (in accordance with fuses) to the actual dashboard
...a pain in the *ss!
-
Is it possible to correct your bin in a hex editor or should i wait for GiampyXBS program?Srry for nub question but im so confused.And thanks GiampyXBS for getting this great info!
-
Nevermind that was a stupid question but ive a new question.My drive serial looks like this
0000: 44 36 30 38 43 47 38 33 - 34 38 30 39 30 30 33 51 D608CG834809003Q
0010: 30 20 20 20 FF FF FF FF - FF FF FF FF FF FF FF FF 0 ............
0020: FF FF FF FF FF FF FF FF - 41 30 FF FF FF FF FF FF ........A0......
0030: FF FF FF FF FF FF FF FF - FF FF FF FF FF FF FF FF ................
0040: FF FF FF FF FF FF FF FF - FF FF FF FF 41 31 FF FF ............A1..
Why dont i have the SS hiden data?
Ic you released that program 4days ago
great
-
Can someone help me?
I did my first ever flash, using JF .43. have all the original files from the dump using the Connectivity kit pro and probe, although JF froze just before it was power cycled and asked to save the log, so I haven't got the log.
Firstly how can I check that my data that I have is OK? Can I use something to open the .bin files?
If I have all the information needed, i'll be a very happy man. I used the tutorial by JF, although it was late, I was tired and I'd been on the pop
-
QUOTE(wackojacko99 @ Feb 2 2009, 06:03 PM)

...
Firstly how can I check that my data that I have is OK? Can I use something to open the .bin files?
...
Any hex editor is good or JF, compare the data with the first post.
Or the simple app that i created, here.
-
So, this is the third 360 I bought. I got the xtractor tool and probe, extracted the key and all, made a dummy file, and patched my lite-on. So, it just gave me the error code E-64. The next morning, the guy who sent me the xtractor sent me an email linking to this page, and I got the serial dummy.bin fixer, used it to fix the dummy.bin I had created with jungleflasher. I tried it again, and it's still giving me the bad firmware error code! I tried making a new dummy.bin, and it did the same thing. So I tried loading the original firmware on, but then the 360 just kept rebooting on its own. I've tried flashing it so many times, but it's still just showing E-64.
Any ideas? Please, please please help!
-
ok, this is an super interesting post, so sorry for me english, i am from spain, ok, i read it and modify my dummy.bin, but i have a question, you do the firmtool dummy.bin ix15.bin,now you have the ixtrem file with your data of your drive, ok so if you edit the ix15.bin and go to the position 0x1ff00, you can see that in this positio now, is not your data of the drive, now you have this... D608CG833907010F0 ÿÿÿÿ8G31075017E414XXA0ÿÿS4P881400000114443, why????i dont known, but if you edit the original file of the ixtrem (ix15-liteon.bin) you can see that as default this file contais this inforamtion, and i dont known why firmtool dont put here my information of my drive...any people look this??.
for a good ixtrem....my driver serial must be in the hacked file,dont you?
thanks
-
QUOTE(Giru @ Feb 3 2009, 06:31 PM)

i dont known why firmtool dont put here my information of my drive...any people look this??
Are you using v1.3.1?
Caster.
-
i am using v1.3 but not says v1.3.1 by caster, why??
-
QUOTE(Giru @ Feb 3 2009, 11:31 PM)

ok, this is an super interesting post, so sorry for me english, i am from spain, ok, i read it and modify my dummy.bin, but i have a question, you do the firmtool dummy.bin ix15.bin,now you have the ixtrem file with your data of your drive, ok so if you edit the ix15.bin and go to the position 0x1ff00, you can see that in this positio now, is not your data of the drive, now you have this... D608CG833907010F0 ÿÿÿÿ8G31075017E414XXA0ÿÿS4P881400000114443, why????i dont known, but if you edit the original file of the ixtrem (ix15-liteon.bin) you can see that as default this file contais this inforamtion, and i dont known why firmtool dont put here my information of my drive...any people look this??.
for a good ixtrem....my driver serial must be in the hacked file,dont you?
thanks
You are so right as I am having the exact same problem with my Lite-On. I have used Giampy's Bin Fixer and it does fix the dummy.bin, but I believe that this iXtreme FW isn't legit as those we have gotten from C4eva. Maybe C4eva needs to be the one who builds the iXtreme 1.5 for us all as there is a problem with this iXtreme version. If anyone thinks different please post your thoughts. All I get on one of my Lite-On drives is "Open Tray" when trying to play a DVD, original, or backup.
-
QUOTE(Kurt Hectic @ Feb 4 2009, 01:42 AM)

I just checked.
and...

Like Giru, I also have the same thing under this address.
I used newest firmtool (1.3, not 1.31 if it's not the same).
Then
firmtool dummy.bin ix15.bin
got the info about "serial info copied"
So what? The liteon I flashed today with this prepared firmware doesn't contain all (and correct) serial data?

That's right Kurt,
Even when I use JF, it tells me that "Warning, Serial Information Bad" and then it locks up my system so I have to reboot. That LiteOn you flashed today may or may not work properly depending on the iXtreme CFW you obtained.
-
hi guys!!well caster syas right, use firmtool v1.3.1 to make the ixtrem whit dummy data correctly, if when you xtract the data is bad, correct it and then use firmtool v1.3.1 and it will generate a ixtrem correctly, many thanks caster!!!
-
Ok, but where would I get it?
I've checked. Ix15 archive has the "1.3 FINAL",
in "tools" section I see only 1.2.
Plus
in 1.3 readme I saw info about proper serial handling. I though it was the newest.
-
i dont known if here is allowed to put some directon, search on google for firmtool v1.3.1 and you get a url...
see you, good night!!
-
That's not the point. I though I was using the most "official" or "our" source for such files.
I though that authors of such programs care about keeping things updated, especially when it comes to important and dangerous matters (like flashing without a serial).
I kinda wanted to "sound the alarm".
But now I see that I misinterpreted a few threads - assuming that "my source" is the main site for all things connected with xbox scene. I guess I was wrong.
I've downloaded the correct version now.
Words cannot describe my frustration when I opened the readme.txt and saw:
" v1.3.1 - Fixed a Lite-On serial copying issue. "
Life is brutal, I guess.
Oh well. Those two Lite-ons are going to stay without a serial forever (or until ban) cause they're my friend's consoles and they don't want to hear about opening them again, not to mention the fact I'm not too eager to tell then "hey, I did it wrong - I've got to do it all again" 
They have a correct key, I've got proper dummy.bin files in case of ban alarm in the future, and they're playing on the backups just offline. Online means putting the original discs in the drive. So I think... no... I hope everything is going to be OK.
BTW. flashing under dosflash16 is still OK, and all the serial data will be properly flashed if I was using proper hacked.bin, right?
-
QUOTE(Kurt Hectic @ Feb 4 2009, 01:42 AM)

I just checked.
and...

Like Giru, I also have the same thing under this address.
I used newest firmtool (1.3, not 1.31 if it's not the same).
Then
firmtool dummy.bin ix15.bin
got the info about "serial info copied"
So what? The liteon I flashed today with this prepared firmware doesn't contain all (and correct) serial data?

@Kurt Hectic,Giru
You MUST use the firmtool 1.3.1 (not the 1.3) to spoof the full liteon serial data, it's ok (i think that the new JF may be ok). Of course with the 4 files (inquiry,identify,key and dummy) dumped before the first flash, otherwise you need to recreate the serial data using the labels on/in the dvd drive.
-
QUOTE(GiampyXBS @ Jan 26 2009, 09:26 AM)

First of all, hi to all. My first post.
Second, sorry for my bad english, i hope to be quite readable in this post.
This can be (potentially) a method for recreate (partially/full) the "Drive Serial" data for those of who missed it. The fact to be fully or partially recreatable depends on the help from the user here. So read it please.
All you know that for the
correct extraction of data from liteon, updated tools are required (such as DosFlash 1.7+,DVDKey 1.2+, DVDKey32 0.7+, Firmtool 1.3.1+ and so on). If the data was extracted with previous tools the "Drive serial" isn't complete for this DVD reader...eg. Firmtool 1.3.1+ report it with a warning : lite-on serial appears to be partially incomplete.
I flashed my drive before that those updated tool-set was available, so i was trapped in the net of who have a good local iXtreme, but a (future) problematic one in LIVE!
I decided to try to solve this question, so Googling for it, i was surprised that no info about the "Drive Serial" can be retrieved...starting doing it myself (or at least try to do it).
So here is the part.
The "Drive Serial" can be read from 0x1ff00 in the dummy.bin file created by the tool or directly from the target spoofed firmware, with an hex editor or using jungleflasher (load from dumped data).
A typical
incomplete "Drive Serial" looks like this:
CODE
0000: 44 36 30 38 43 47 38 33 - SS SS SS SS SS SS SS SS D608CG83SSSSSSSS
0010: 31 20 20 20 FF FF FF FF - FF FF FF FF FF FF FF FF 1 ............
0020: FF FF FF FF FF FF FF FF - 41 30 FF FF FF FF FF FF ........A0......
0030: FF FF FF FF FF FF FF FF - FF FF FF FF FF FF FF FF ................
0040: FF FF FF FF FF FF FF FF - FF FF FF FF 41 31 FF FF ............A1..
SS SS SS = My hidden data.
"FF FF FF ..." may be "58 58 58 ..." if the serial data is read from the target firmware prepared with firmtool 1.3.1+.
Searching for those dumps over internet i found some interesting patterns and source for intuition. So found that
a typical
complete "Drive Serial" can be this (call this A0 version) :
CODE
0000: 44 36 30 38 43 47 38 33 - SS SS SS SS SS SS SS SS D608CG83SSSSSSSS
0010: 31 20 20 20 FF FF FF FF - YY YY YY YY YY YY YY YY 1 ....YYYYYYYY
0020: YY YY YY YY YY YY 58 58 - 41 30 FF FF ZZ ZZ ZZ ZZ YYYYYYXXA0..ZZZZ
0030: ZZ ZZ ZZ ZZ ZZ ZZ ZZ ZZ - ZZ ZZ ZZ ZZ ZZ ZZ 00 00 ZZZZZZZZZZZZZZ..
0040: FF FF FF FF FF FF FF FF - FF FF FF FF 41 31 FF FF ............A1..
or this (call this non A0 version):
CODE
0000: 44 36 30 38 43 47 38 33 - SS SS SS SS SS SS SS SS D608CG83SSSSSSSS
0010: 31 20 20 20 FF FF FF FF - YY YY YY YY YY YY YY YY 1 ....YYYYYYYY
0020: YY YY YY YY YY YY 58 58 - KK KK FF FF ZZ ZZ ZZ ZZ YYYYYYXX....ZZZZ
0030: ZZ ZZ ZZ ZZ ZZ ZZ ZZ ZZ - ZZ ZZ ZZ ZZ ZZ ZZ ZZ ZZ ZZZZZZZZZZZZZZZZ
0040: FF FF FF FF FF FF FF FF - FF FF FF FF 41 31 FF FF ............A1..
So i was thinking that a "Serial Number" is an identifier and must be visible in some manner, otherwise it was a key !!! Not thinking so bad...
Let's go with order.
The
...SSSSSSSS... data is surely present from the dump, it's our DVD Serial Number printed here (except for the last number that seems to be always 0 or 1):

The
YYYYYYYYYYYYYYXX is the optical serial number, is always 16 chars length and (from my dumps) it always end up with "XX". The most of times it start with "8" (eg 8C,8G,8F).
It can be retrieved here :

The
ZZZZZZZZZZZZZZZZZZ[ZZ] is the dvd-mobo serial number and is slightly different, it depends on the fact that 0x0028 is "A0" or something else.
If it's "A0" then the length is always (from my dumps) 18 chars.
If it's not "A0" then the length is always (from my dumps) 20 chars.
But it always start with "S4P8"
It can be retrieved removing both covers of the dvd unit and face it up (with the optical led up). Pay attention at the led/photoled, be carefull : do no touch, do not expose to direct strength light, do not incinerate for who smokes..

..and bla bla bla.
The photo is a bit dark but you can find it easly :
Now the questions directed to all contributors are 2 :1)
A0 or non A0?I found this value in the my incomplete dump (dummy.bin)
CODE
...
0020: FF FF FF FF FF FF FF FF - 41 30 FF FF FF FF FF FF ........A0......
...
Is this value
dumped or
autogenerated from the old tools? because if it is dumped we have 1 more info directly from the "problematic" dummy.bin/spoofed firmware...if it is autogenerated, we need to know how to retrieve it! (Remember that this can help us to find out the length of the dvd-mobo sn, read the doubt at the point 2).
Can someone point this question to the attention of the programmers? (eg. Geremia, C4Eva...)
2)
The perfidious numberLooking on the dvd-mobo label i have a second number (2 digits) in bottom-right corner

I called it perfidious because my label sn length is 18...so i'm not sure if i need to add those 2 digits (depends on the dump/generation of the previously "A0") and create a 20 chars length sn or if the sn is complete.
Can any of you post your experience related to those questions?
For any of you that have a correct dump (18/20 chars, A0/not A0 in the dummy.bin) : can check if the "perfidius" number is the last part of the dvd-mobo sn or if the entire sn is simply write in the 2 rows of the label and the perfidious is not correlated to sn?(with the box opened for the hack,removing both covers and write down a number take approximatively 15 seconds for you, but this is very helpfull for us)
The most we are, the better is for the complete "Drive Serial" recreation!
Thank you for your contribution.
Have a good hack.
My DVD serial no. has 17 characters though. Does this matter (D608CG830809011EV), why isn't the last letter (V) not included when using "Giampy's Dummy Bin fixer"?
OK here's my Serial information from the corrected dump from "Giampy's Dummy Fixer".
0000: 44 36 30 38 43 47 38 33 - 30 38 30 39 30 31 31 45 D608CG830809011E
0010: 30 20 20 20 FF FF FF FF - 38 47 31 35 30 31 31 31 0 ....8G150111
0020: 31 37 44 34 31 34 58 58 - 41 30 FF FF 53 34 50 38 17D414XXA0..S4P8
0030: 37 32 34 30 30 30 30 30 - 31 37 37 37 32 31 00 00 72400000177721..
0040: FF FF FF FF FF FF FF FF - FF FF FF FF 41 31 FF FF ............A1..
Now I've compared mine to the example posted by Giampy and there is some serious issues going on with my information here. I don't understand what is causing this to happen. Jungle Flasher keeps telling me that my serial information is bad when I check by going to the "DVDKey Extract" and selecting "Get Key, Select Dummy Bin, Open as Source. Can someone please analyze this for me and post your thoughts? What do I need to do to get this drive to fire up originals, DVDs and backups?
-
QUOTE(GiampyXBS @ Feb 4 2009, 06:47 AM)

The last letter doesn't matter, it's always a 0 or 1 in the sata dump (may be a crc of the dvd serial?)
what are the issues? the serial data structure looks fine...
If the latter is your problem,then it's probably a dvd-key problem (wrong dump), so it's not related with serial data. The serial data may be usefull only if M$ can retrieve it for the LIVE access (in the future? may be or not).
if you misunderstood the problem, i apologize...
Hey thanks for the quick reply Giampy,
I think my key may have been compromised or scrambled in some manner just as my other infor was. Is there a way to recover the original key at all? I guess I'm screwed then for retrieving the original key isn't possible now. Thanks anyhow.
-
Well i have a Question?
If the Xbox 360 motherboard only has 1 key and i extracted the key and it siad it was incomplete then i flashed it and games worked so that means its correct right just asking?
-
QUOTE(BombTester @ Feb 4 2009, 04:17 PM)

Well i have a Question?
If the Xbox 360 motherboard only has 1 key and i extracted the key and it siad it was incomplete then i flashed it and games worked so that means its correct right just asking?
This thread is about the "DRIVE SERIAL" not your dvd key.Your 360 will work with incomplete serial data as long as your dvd key of your mobo and your dvd rom matches.Incomplete serial data is just a high risk of getting banned in the future.
-
HI !
yesterday i was reading about incomplete serial drive, and now i read in my lector all label's(dvd,opt,pcb) and put here in my dummy.bin and also reflashing and all is ok,but serial drive is here:
0000: 44 36 30 38 43 47 38 33 - 30 39 30 39 30 30 4C 51 D608CG83090900LQ
0010: 30 20 20 20 FF FF FF FF - 38 47 31 38 31 33 37 32 0 ....8G181372
0020: 31 37 43 32 31 34 58 58 - 41 30 FF FF 53 34 50 38 17C214XXA0..S4P8
0030: 37 31 39 30 30 30 30 30 - 30 35 34 36 33 34 00 00 71900000054634..
0040: FF FF FF FF FF FF FF FF - FF FF FF FF 41 31 FF FF ............A1..
and this is the old dummy.bin
0001ff00h: 44 36 30 38 43 47 38 33 30 39 30 39 30 30 4C 51 ; D608CG83090900LQ
0001ff10h: 30 20 20 20 FF FF FF FF FF FF FF FF FF FF FF FF ; 0 ÿÿÿÿÿÿÿÿÿÿÿÿ
0001ff20h: FF FF FF FF FF FF FF FF 41 30 FF FF FF FF FF FF ; ÿÿÿÿÿÿÿÿA0ÿÿÿÿÿÿ
0001ff30h: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF ; ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ
0001ff40h: FF FF FF FF FF FF FF FF FF FF FF FF 41 31 FF FF ; ÿÿÿÿÿÿÿÿÿÿÿÿA1ÿÿ
my question is, my new serial drive is correct because now i see FF and any space,what you say?
...sorry about my english, i'm a spanish boy, and i try to put my serial drive ok.thanks
-
QUOTE(podger @ Jan 27 2009, 07:34 PM)

dangerpaki:
that "load from dump files" has moved... Unfortunately, it was incorrectly used in tutorials. It is only intended for picking up old files..
Good news tho with Giampy discovery, you can rebuild you serial data, if you are willing to open your DVD drive...
ok just rechecked my created dummy.bin and it isn't correct it misses the information for the last two (i used the dummy.bin fixer). so i'll have to open my drive and give it the correct information. and save a new dummy.bin. which i will then use to spoof my ixtreme liteon. this is correct right?
so' i know what i'll be doing in the weekend then
-
QUOTE(deejayexe @ Feb 5 2009, 02:29 PM)

HI !
yesterday i was reading about incomplete serial drive, and now i read in my lector all label's(dvd,opt,pcb) and put here in my dummy.bin and also reflashing and all is ok,but serial drive is here:
0000: 44 36 30 38 43 47 38 33 - 30 39 30 39 30 30 4C 51 D608CG83090900LQ
0010: 30 20 20 20 FF FF FF FF - 38 47 31 38 31 33 37 32 0 ....8G181372
0020: 31 37 43 32 31 34 58 58 - 41 30 FF FF 53 34 50 38 17C214XXA0..S4P8
0030: 37 31 39 30 30 30 30 30 - 30 35 34 36 33 34 00 00 71900000054634..
0040: FF FF FF FF FF FF FF FF - FF FF FF FF 41 31 FF FF ............A1..
and this is the old dummy.bin
0001ff00h: 44 36 30 38 43 47 38 33 30 39 30 39 30 30 4C 51 ; D608CG83090900LQ
0001ff10h: 30 20 20 20 FF FF FF FF FF FF FF FF FF FF FF FF ; 0 ÿÿÿÿÿÿÿÿÿÿÿÿ
0001ff20h: FF FF FF FF FF FF FF FF 41 30 FF FF FF FF FF FF ; ÿÿÿÿÿÿÿÿA0ÿÿÿÿÿÿ
0001ff30h: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF ; ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ
0001ff40h: FF FF FF FF FF FF FF FF FF FF FF FF 41 31 FF FF ; ÿÿÿÿÿÿÿÿÿÿÿÿA1ÿÿ
my question is, my new serial drive is correct because now i see FF and any space,what you say?
...sorry about my english, i'm a spanish boy, and i try to put my serial drive ok.thanks
Looks perfect !
QUOTE(dangerpaki @ Feb 5 2009, 03:42 PM)

ok just rechecked my created dummy.bin and it isn't correct it misses the information for the last two (i used the dummy.bin fixer). so i'll have to open my drive and give it the correct information. and save a new dummy.bin. which i will then use to spoof my ixtreme liteon. this is correct right?
so' i know what i'll be doing in the weekend then

Yes, that's right.
Enjoy 
-
QUOTE(GiampyXBS @ Feb 4 2009, 06:47 AM)

The last letter doesn't matter, it's always a 0 or 1 in the sata dump (may be a crc of the dvd serial?)
what are the issues? the serial data structure looks fine...
If the latter is your problem,then it's probably a dvd-key problem (wrong dump), so it's not related with serial data. The serial data may be usefull only if M$ can retrieve it for the LIVE access (in the future? may be or not).
if you misunderstood the problem, i apologize...
Hey Giampy I have just one more question........
If I ran my dummy.bin file through the Bin Fixer and it gave me all greens on everything, then why is Jungle Flasher telling me that the serial information is bad still? How will I know if it's my key if I have received a green for it as well?
-
You know, for someone that only joined on January 29th, GiampyXBS has really got it goin' on. Pure genius man!
I've checked the dummys for all the liteons I've done to date and only the very first one is bad. Luckily its a work colleagues drive so I'll get him to bring it back to me and redo it.
-
QUOTE(GiampyXBS @ Feb 8 2009, 09:19 AM)

does JF give some deep infos about it?
did u use the right patched dummy file?
Thank you MickRick...i was lucky

I am so happy that I read this topic and worked hard to make my hacked FW "100% perfect". However I am still not sure if my LiteOn drive have the right FW inside. I cannot write my LiteOn FW under JF 0.4.3 because my computer hangs so I make the following steps under DOS
- Check my Dummy.bin; key.bin, inquiry.bin and identify.bin with your app DSDBFixer (I am very impressed with your findings GiampyXBS!!!!) : Shows that everything is fine (I also double check the PCB S/N, OPT S/N and Driver S/N, all match perfectly)
- I use this dummy.bin and merge with ix15.bin using Firmtool 1.3.1. The firmtool 1.3.1 make a "new" ix15.bin with my key inside. The application informs that my key was correctly merged (green colors). I rename ix15.bin to LITE_CFW.BIN under windows XP (because DOSFLASH 1.7 I used only accepts to write my FW if I use this name, so i change the name to LITE_CFW.BIN)
- I create a DOS BOOT with the following apps and file inside one folder that I create: L-O-ERAS.EXE; DOSFLASH.EXE and my hacked FW LITE_CFW.BIN. Boot my computer and under pure DOS I make the following:
1) Type "L-O-ERAS DD60" (of course without ", DD60 is my SATA port)
Many times get FF80 status result, keep retyping this instruction until get FF72 status
2) Type "DOSFLASH", application ask me to choose the right Sata port, in my case I select item "4"
Type "W" (write LiteOn), first time fail
Type again "DOSFLASH", "4", "W", this time ask for the FILENAME: I type "LITE_CFW.BIN"
Shows >> ERASING.....
Shows >> WRITING BANK 0....
Shows >> WRITING BANK 1....
Shows >> WRITING BANK 2....
Shows >> WRITING BANK 3....OK!
Shows >> DATASUM ECE6
(Liteon driver open, close and power on the laser diode normally)
Questions: Are these steps correct? Can I consider my FW OK? Because now when I try extract my key again using any app that I have always say my keys are invalid, how to check if everything is fine? I tried so many times and I do not have confidence whether the key extractors applications are right or wrong, any ideas? Can I connect the driver to Xbox?
Many thanks if I can receive some feedback and sorry for my long post, i tried to make this post with all details i could get
-
QUOTE(joliverio @ Feb 16 2009, 01:15 PM)

Questions: Are these steps correct? Can I consider my FW OK? Because now when I try extract my key again using any app that I have always say my keys are invalid, how to check if everything is fine? I tried so many times and I do not have confidence whether the key extractors applications are right or wrong, any ideas? Can I connect the driver to Xbox?
Many thanks if I can receive some feedback and sorry for my long post, i tried to make this post with all details i could get
Looks perfect...
To test the dvd simply try to play an original/backup game, if the key is good you must not have any trouble.
I tried to extract my key (that is good) from an ix15 flashed on my dvd...but i fail,cant get it.
I dont know if the sata-com trick works again with the ix15 fw on the drive!
Sorry, if someone knows...post the confirm here.
-
QUOTE(GiampyXBS @ Feb 17 2009, 12:03 AM)

Looks perfect...
To test the dvd simply try to play an original/backup game, if the key is good you must not have any trouble.
I tried to extract my key (that is good) from an ix15 flashed on my dvd...but i fail,cant get it.
I dont know if the sata-com trick works again with the ix15 fw on the drive!
Sorry, if someone knows...post the confirm here.
Many thanks for your confirmation, I am happy to hear that my flash seems perfect
Yea, my Xbox still can plays originals, backups and DVDs region locked normally; however I cannot extract a "good" key from the LiteOn anymore using any available app (anyway, I have my key already...), and the flash process that I describe is the only one who did not corrupt the dummy.bin and hacked FW files
-
I tried to extract my dvd key from my hacked lite on without any results.I thought it was me and i just gave up
So we need someone who determines whats wrong.I can imagine people not having made a back up and not being able to read the key again when they need it again.I know its stupid but that how people are
-
Yep your right its not necessary.I just wanted to check if my bins would match with my first dump and that was stupid when i think of it now.The only thing we can compare i think is the serial data/dvd key.
-
i need little help, heres some of my key extraction screenshots



as u can see, my status is BAD, also my key slightly changes too..
What am i doing wrong? is it my usb driver? i know i did everything correctly in making the extraction tool and check it over 10x or more because i couldnt find out what i was doing wrong, HELP PLZ!!
-
QUOTE(phoduma @ Feb 20 2009, 10:29 PM)

i need little help, heres some of my key extraction screenshots



as u can see, my status is BAD, also my key slightly changes too..
What am i doing wrong? is it my usb driver? i know i did everything correctly in making the extraction tool and check it over 10x or more because i couldnt find out what i was doing wrong, HELP PLZ!!
I think its not a good idea to use the usb-serial adapter...
btw this topic is for serial data not the KEY, its better if you start a new thread for readability reasons, so someone can surely help you.
-
QUOTE(GiampyXBS @ Feb 21 2009, 07:25 AM)

I think its not a good idea to use the usb-serial adapter...
btw this topic is for serial data not the KEY, its better if you start a new thread for readability reasons, so someone can surely help you.
can i have an answer to my question please?
-
QUOTE(pakigno @ Feb 21 2009, 10:20 AM)

can i have an answer to my question please?

You are the first that post a non A0 version,some people think that it's a wrong extraction.
Did you try to extract the inquiry and identify with another tool? (eg dosflash)
Does your inquiry/identify files looks good? Was the key correctly extracted?
Did you dump data more than once?
You can post inq/ident files here if you cant check from yourself.
-
Unfortunately i did not find out about these issues until after i flashed my liteon.
I flashed my liteon using jungleflasher .26 and dosflash16.
I used your excellent program to rebuild my dummy file.
The patched dummy file reads
CODE
0000: 44 36 30 38 43 47 38 35 - 30 38 31 32 30 30 45 37 D608CG85SSSSSSSS
0010: 31 20 20 20 FF FF FF FF - 38 4A 32 36 31 31 35 31 1 ....YYYYYYYY
0020: 31 37 43 39 31 34 58 58 - 41 30 FF FF 53 34 50 38 YYYYYYXXA0..S4P8
0030: 43 30 38 30 30 30 30 30 - 30 32 39 33 38 34 00 00 ZZZZZZZZZZ9384..
0040: FF FF FF FF FF FF FF FF - FF FF FF FF 41 31 FF FF ............A1..
Which looks correct, but after i flash the drive (and dump the files) the serials then read
CODE
0000: 44 36 30 38 43 47 38 35 - 30 38 31 32 30 30 45 37 D608CG85SSSSSSSS
0010: 31 20 20 20 FF FF FF FF - 38 4A 32 36 31 31 35 31 1 ....YYYYYYYY
0020: 31 37 43 39 31 34 58 58 - 00 00 FF FF 53 34 50 38 YYYYYYXX....ZZZZ
0030: 43 30 38 30 30 30 30 30 - 30 32 39 33 30 32 38 34 ZZZZZZZZZZ930284
0040: FF FF FF FF FF FF FF FF - FF FF FF FF 41 31 FF FF ............A1..
1ff28 and 1ff29 - the A0 (after the xx) is missing
and the 02 is inserted in the dvd-mobo serial number
I performed the same read on the drive 18 times, 9 seemed successful - these matched each other identically, the other were very similar to the good dumps expect at positions 1ff28 and 1ff29 – ie where A0 should be. I reflashed my drive and repeated the process a couple of times just to verify it wasn’t a bad write.
Is the Ixtreme firmware altered not to give out the 1ff28 and 1ff29 bytes in the same way that the original firmware does? Is this normal? Can other people get the A0 to show up on their flashed drive?
Here is the output after I ran your program on the dummy file (generated from the drive after I flashed it with all the correct serials)
QUOTE(Giampys fixer ouput)
08:07:53.921 : Checking inquiry data...
08:07:53.921 : Inquiry data looks good.
08:07:53.921 : Checking identify data...
08:07:53.937 : Identify data looks good.
08:07:53.937 : Checking DVD key...
08:07:53.937 : DVD Key looks good.
08:07:53.937 : Checking DVD serial number...
08:07:53.937 : DVD serial number looks good.
08:07:53.937 : Checking OPTICAL serial number...
08:07:53.937 : OPT serial number looks good.
08:07:53.937 : Checking PCB serial number...
08:07:53.953 : Error on PCB serial data check: 'A0' HW ver not found (will be automatically fixed) (0x1FF28)!
08:07:53.953 : Error on PCB serial data check: footer PCB sn not found (will be automatically fixed) (0x1FF3E)!
08:07:53.953 : PCB serial number looks good.
08:07:53.953 : Found those problems in dummy.bin (read above): 'A0' HW ver not found,footer PCB sn not found
Also, my drive serial label has an extra letter on the end ie E7R - im assuming this is normal and you just drop the R.
Interestingly when you use blank serial numbers FF-FF in a source dummy file and spoof them to the ixtreme firmware you get this
Ixtreme before spoof
CODE
0000: 44 36 30 38 43 47 38 33 - 33 39 30 37 30 31 30 46 D608CG833907010F
0010: 30 20 20 20 FF FF FF FF - 38 47 33 31 30 37 35 30 0 ....8G310750
0020: 31 37 45 34 31 34 58 58 - 41 30 FF FF 53 34 50 38 17E414XXA0..S4P8
0030: 38 31 34 30 30 30 30 30 - 31 31 34 34 34 33 00 00 81400000114443..
0040: FF FF FF FF FF FF FF FF - FF FF FF FF 41 31 FF FF ............A1..
after
CODE
0000: FF FF FF FF FF FF FF FF - FF FF FF FF FF FF FF FF ................
0010: FF FF FF FF FF FF FF FF - 38 47 33 31 30 37 35 30 ........8G310750
0020: 31 37 45 34 31 34 58 58 - FF FF FF FF 53 34 50 38 17E414XX....S4P8
0030: 38 31 34 30 30 30 30 30 - 31 31 34 34 34 33 00 00 81400000114443..
0040: FF FF FF FF FF FF FF FF - FF FF FF FF FF FF FF FF ................
JungleFlash allows you to flash/clear the dvd serial number and the A0 and A1, but not the optical serial number and dvd-mobo serial.
-
QUOTE(Matthaeus @ Feb 26 2009, 06:41 AM)

I must have been really tired when i made that post (i was), as most of the answers to my questions are on the last 2 pages

Sorry
Just to be clear, Giampy has said that these may not be fully extractable with the ixtreme firmware, but what is the format or your serials after dumping a drive flashed with all the correct details?
For me, the A0 (after the xx) is always missing and 02 is inserted before the last two digits in the dvd-mobo serial number
ie
0000: 44 36 30 38 43 47 38 35 - 30 38 31 32 30 30 45 37 D608CG85SSSSSSSS
0010: 31 20 20 20 FF FF FF FF - 38 4A 32 36 31 31 35 31 1 ....YYYYYYYY
0020: 31 37 43 39 31 34 58 58 - 00 00 FF FF 53 34 50 38 YYYYYYXX....ZZZZ
0030: 43 30 38 30 30 30 30 30 - 30 32 39 33 30 32 38 34 ZZZZZZZZZZ93
0284
0040: FF FF FF FF FF FF FF FF - FF FF FF FF 41 31 FF FF ............A1..
Thanks.
That's an interesting question ...
Now my box is assembled, i try a sata dump as soon as i re-open it for testings purpose (an homemade connectivity kit, without use the xbox to power the drive), meanwhile, can someone extract the serials data from (with the ix firmware) and compare to the canonical type?
Btw,the serials are in the dummy.bin file, and this file is autogenerated from the tools only if they can extract a (good) key, apparently (for me) i can't extract the key after flashing the ix15 on the drive.
So the question is, how did you dump the serials after flashing the ix firmware on it?
-
This is how my patched dummy source looks.
0000: 44 36 30 38 43 47 38 35 - 30 38 31 32 30 30 45 37 D608CG85SSSSSSSS
0010: 31 20 20 20 FF FF FF FF - 38 4A 32 36 31 31 35 31 1 ....YYYYYYYY
0020: 31 37 43 39 31 34 58 58 - 41 30 FF FF 53 34 50 38 YYYYYYXXA0..S4P8
0030: 43 30 38 30 30 30 30 30 - 30 32 39 33 38 34 00 00 ZZZZZZZZZZ9384..
0040: FF FF FF FF FF FF FF FF - FF FF FF FF 41 31 FF FF ............A1..
QUOTE(GiampyXBS @ Feb 26 2009, 07:06 AM)

.........how did you dump the serials after flashing the ix firmware on it?
I just repeated the process as if the drive was the original Microsoft/liteon firmware.
I also tried using Firmware tool 1.3.1, and a few others - they all produce the same results.
QUOTE(GiampyXBS @ Feb 26 2009, 07:06 AM)

Btw,the serials are in the dummy.bin file, and this file is autogenerated from the tools only if they can extract a (good) key, apparently (for me) i can't extract the key after flashing the ix15 on the drive.
When you say key, i assume your talking about dvdkey and jungleflasher .43 beta and how it dumps the drivekey 6 times and if they don’t match it aborts?
Interestingly, as mentioned before - i repeated the dumping a number of times and half of them produced different serial information where A0 should be - the rest of the strings were all identical - this was using JF.43 beta (where it checks your dvdkey to ensure a good read) - so it is still possible with JF.43 beta to pass on corrupted information, at least where A0 is (ff29 & ff28).
I tried a few different things and found that jungleflasher .26 beta (with and WITHOUT using the probe) produced the exact same serials as JF.43.
Try using JF .26b dvdkey32 and see what happens - the serials will be shown in the output at the bottom of dvdkey32 – you don’t need to load the files.
Cheers, Matthaeus.
-
QUOTE(GiampyXBS @ Feb 23 2009, 05:44 PM)

You are the first that post a non A0 version,some people think that it's a wrong extraction.
Did you try to extract the inquiry and identify with another tool? (eg dosflash)
Does your inquiry/identify files looks good? Was the key correctly extracted?
Did you dump data more than once?
You can post inq/ident files here if you cant check from yourself.
i have used jungleflasher 0.23 and dvdkey32 to extract inquiry, identify and key several times, all the files look good and the key is correct. Than i create the ixtreme firmware with firmtool 1.3.1 without any type of errors or warnings messages, so i flashed the drive and all works perfect...
i don't understand if is better for me to reflash the drive with a0 and less two number
-
QUOTE(Matthaeus @ Feb 26 2009, 10:45 AM)

This is how my patched dummy source looks.
0000: 44 36 30 38 43 47 38 35 - 30 38 31 32 30 30 45 37 D608CG85SSSSSSSS
0010: 31 20 20 20 FF FF FF FF - 38 4A 32 36 31 31 35 31 1 ....YYYYYYYY
0020: 31 37 43 39 31 34 58 58 - 41 30 FF FF 53 34 50 38 YYYYYYXXA0..S4P8
0030: 43 30 38 30 30 30 30 30 - 30 32 39 33 38 34 00 00 ZZZZZZZZZZ9384..
0040: FF FF FF FF FF FF FF FF - FF FF FF FF 41 31 FF FF ............A1..
I just repeated the process as if the drive was the original Microsoft/liteon firmware.
I also tried using Firmware tool 1.3.1, and a few others - they all produce the same results.
When you say key, i assume your talking about dvdkey and jungleflasher .43 beta and how it dumps the drivekey 6 times and if they dont match it aborts?
Interestingly, as mentioned before - i repeated the dumping a number of times and half of them produced different serial information where A0 should be - the rest of the strings were all identical - this was using JF.43 beta (where it checks your dvdkey to ensure a good read) - so it is still possible with JF.43 beta to pass on corrupted information, at least where A0 is (ff29 & ff28).
I tried a few different things and found that jungleflasher .26 beta (with and WITHOUT using the probe) produced the exact same serials as JF.43.
Try using JF .26b dvdkey32 and see what happens - the serials will be shown in the output at the bottom of dvdkey32 you dont need to load the files.
Cheers, Matthaeus.
Uhmmm...looks like an ix15 issue, its quite improbable that JF pass random data ONLY for the A0 part of the serial...!
Pakigno has the same kind of serial data...
Btw, did you receive the same right key via rs232 dumping after the flash? (may be my homemade extractor that is faulty)
QUOTE(pakigno @ Feb 26 2009, 10:53 AM)

i have used jungleflasher 0.23 and dvdkey32 to extract inquiry, identify and key several times, all the files look good and the key is correct. Than i create the ixtreme firmware with firmtool 1.3.1 without any type of errors or warnings messages, so i flashed the drive and all works perfect...
i don't understand if is better for me to reflash the drive with a0 and less two number

Packigno, your serial data is related to a dump before or after flashing the drive the first time?
If you dump after the first flash, may be that your serials are correct but the ix15 give you wrong data,in this case isn't usefull redump and reflash!
Can someone try a sata dump with ix15 firmware on the drive? (or do i need to disassembly my box?)
-
What i said before concerning my serial dumps was not quite correct, at the ff29 & ff28 bytes i said i got 9 the same, while the rest were sporadic - not all of the 9 were the same, they were just not 'real' hex values - so my editor dropped the ascii conversion. This is a list of the ff29 & ff28 (A0) bytes, as you can see, the results are not random.
JF .4
22 8A FF FF
34 89 FF FF
34 89 FF FF
22 8A FF FF
EC 89 FF FF
00 00 FF FF
E4 89 FF FF
JF .2 - I believe i was power cycling the drive between attemps here.
00 00 FF FF
35 89 FF FF
00 00 FF FF
E4 89 FF FF
35 89 FF FF
00 00 FF FF
35 89 FF FF
00 00 FF FF
QUOTE
did you receive the same right key via rs232 dumping after the flash?
Yes, all of my drivekeys were correct. I'm doing it via usb - all the other data seems fine.
It definitely looks like it's the ixtreme firmware, i just meant that jf will pass on the 'corrupted/wrong' A0 - not that it creates it. But i suppose this is not an issue if this doesn't happen with the original liteon firmware.
Cheers, Matthaeus.
-
I mentioned this issues on Dec. 29on xbh (link), but no one really cared. But fine that there seems to be a solution for the "lost" keys.
-
QUOTE(GiampyXBS @ Feb 27 2009, 12:16 AM)

Uhmmm...looks like an ix15 issue, its quite improbable that JF pass random data ONLY for the A0 part of the serial...!
Pakigno has the same kind of serial data...
Btw, did you receive the same right key via rs232 dumping after the flash? (may be my homemade extractor that is faulty)
Packigno, your serial data is related to a dump before or after flashing the drive the first time?
If you dump after the first flash, may be that your serials are correct but the ix15 give you wrong data,in this case isn't usefull redump and reflash!
Can someone try a sata dump with ix15 firmware on the drive? (or do i need to disassembly my box?)
I took my Key with CK3 and make everything "correctly" to keep my hacked Ix15 with all the serials inside (my previous posts shows that). I can try to help in order to get a conclusion about this case, however my knowledge is limited (I am not a noob but I am not an expert, so who I am?
hehehe..), for example I do not know the steps I should do to give you the Dummy source, how to open the bin file and read it correctly? What else I should do? Let me know and I will post my results here
-
I just patched my serial data, but I used my nokia phone to read the images on the lite-on drive. Someone at the 360 factory made one letter unreadable, but this method worked instead. Just cover you laser, it's using the flash to make more light
-
I got the issue with not having a complete dummy even when i tried multiple times to dump it in the new jungleflasher. So i went to rebuild it and remembered i tore off the pcb sticker. Am I out of luck?
-
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?
-
worked like a charm for me but did notice that some liteons have the numbers marked oover in pen and also some of the stickers with the numbers on are really dark and hard to see
-
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!
-
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
-
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...
-
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?
-
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.
-
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.
-
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
-
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!
-
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!!!
-
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
-
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.
-
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.
-
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
-
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
-
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
-
hmmm..... dunno, i cant get my drive to read anything

no one here with a similar problem like mine?
regards
r2k
-
as said in this thread before, i can say that i now have 2 liteons which DONT work witout the correct Serial Number ......
One Drive was restaured by using the Stickers, the Other drive wont read anything, no game, np movie, nothing ...
The Box displays always "Lade Öffnen" when a disk is inserted
regards
r2k
-
QUOTE(paul543 @ Apr 30 2009, 01:10 AM)

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
Me too... Cant get the serials correctly patched with the gyampi's program...
-
how important is it to have the correct serial data?
after reading i belive mine is wrong but my xbox works perfectly, what could happen without it?
-
Easy answer.
The serials were never there in the first place, and the 360 fw utilis copy them JUST IN CASE.
There's other threads discussing this.
-
Jungleflasher will ask you if you want to rebuild the data...
All you have to do is open the drive and match up the labels, quite simple.
-
try to dump 2 or 3 times again
if u get always that error...well use that dump without adding info
as stated in post before no info in the beginning --> no info in the end
bye
-
if u ask a girl wanna fuc*?
and she says yes!
how many times will u ask again?
-
QUOTE(totoz @ Mar 18 2010, 10:44 PM)

if u ask a girl wanna fuc*?
and she says yes!
how many times will u ask again?
lol, thanks for your help totoz. I followed your advice, and it worked. Sorry for being such a noob. This issue was just confusing the hell out of me.
If you don't mind, I still have a couple of questions. I don't really get the "no info in the beginning --> no info in the end"-part. Accoding to my understanding, it is possible to add the missing serial data using either a hex-editor, or JungleFlasher's Serial Rebuilder Applet. Will you please explain?
-
CODE
0001FF00 44 36 31 30 43 47 39 33 39 39 31 33 30 30 31 33 D610CG9399130013
0001FF10 4E 20 20 20 FF FF FF FF 39 49 31 33 31 34 35 39 N ....9I131459
0001FF20 31 36 42 30 31 34 58 58 41 30 FF FF 53 34 50 39 16B014XXA0..S4P9
0001FF30 39 31 37 30 30 30 30 30 31 38 36 37 31 33 00 00 91700000186713..
0001FF40 FF FF FF FF FF FF FF FF FF FF FF FF 41 32 FF FF ............A2..
Now, rebuilt dummys from legacy files (74850c / 83850c using key / inquiry / identify will not have this in dummy.bin, and you wont have it in your iXtreme.bin of old - thus why JF mentioning pre-dating 1.5 as dvdkey 1.0, 1.1 and dvdkey 32 pre 0.7 didnt dump it.
If you flashed iX with one of these, then MRA, the data above wont be present, so JF warns you incase you wish to rebuild it .... If it was there, and you didnt include it, it 'should' be rebuilt for completeness.
However,
Some drives (just like the penultimate paragraph in JungleFlasher says, do not have this data as defualt, usually refurbished consoles, or, drives reflashed after manufacturing.
The area in a FULL ***50c stock dump can and if it is should be left blank, but JF can only check 0x1ff00 and warn you - Just like backups on LT, its up to you to ensure any data that is/should (or not) be present is included.
CODE
0001FF00 44 36 30 39 43 47 39 33 36 39 31 35 30 30 35 41 D609CG936915005A
0001FF10 58 20 20 20 FF FF FF FF FF FF FF FF FF FF FF FF X ............
0001FF20 FF FF FF FF FF FF FF FF 41 30 FF FF FF FF FF FF ........A0......
0001FF30 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF ................
0001FF40 FF FF FF FF FF FF FF FF FF FF FF FF 41 32 FF FF ............A2..
The above is data from a 93450c without the data, as you can see the drive barcode and h/w revision is there, but, laser and pcb serials arent.
JF will warn that the data is missing, again, some cases it should be rebuilt. If its a 100% stock, MRA dump, then do not rebuild
IT WASNT THERE TO BEGIN WITH, DONT ADD IT
-
It's always possible, it doesnt make it right to be there.
-
Therfore,
if it wasnt there to begin with, dont add it
-
QUOTE(OggyUK @ Mar 19 2010, 02:10 PM)

Therfore,
if it wasnt there to begin with, dont add it

Cool stuff. Thanks for all your help. It is appreciated. I understand now (or at least I think so
)