Print

[GiampyXBS]

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.

[pakigno]

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?  

[GiampyXBS]

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.

[Matthaeus]

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.

[GiampyXBS]

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

[Matthaeus]

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.

[pakigno]

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  

[GiampyXBS]

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 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.

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

[Matthaeus]

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.

[damn!]

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.

[joliverio]

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

[UseN3t]

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  

[checker6]

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?

[LiarInGlass]

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?

[keztheking]

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