Topic: Liteon Incomplete "drive Serial" (please Read All) (Read 348 times)

GiampyXBS · « **Reply #45 on:** January 29, 2009, 10:38:00 AM »

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

jt1 · « **Reply #46 on:** January 29, 2009, 03:31:00 PM »

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.

mucho181 · « **Reply #47 on:** January 29, 2009, 04:09:00 PM »

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

jt1 · « **Reply #48 on:** January 29, 2009, 05:17:00 PM »

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

mucho181 · « **Reply #49 on:** January 29, 2009, 07:04:00 PM »

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 ?

pricemeista33 · « **Reply #50 on:** January 29, 2009, 08:27:00 PM »

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.

GiampyXBS · « **Reply #51 on:** January 29, 2009, 10:59:00 PM »

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)

GiampyXBS · « **Reply #52 on:** January 30, 2009, 12:17:00 AM »

(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

...

gaatjenixaan · « **Reply #53 on:** January 30, 2009, 12:38:00 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..

Demonmirc · « **Reply #54 on:** January 30, 2009, 02:07:00 AM »

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.

jt1 · « **Reply #55 on:** January 30, 2009, 02:18:00 AM »

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.

lazyeye · « **Reply #56 on:** January 30, 2009, 05:55:00 AM »

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.

mucho181 · « **Reply #57 on:** January 30, 2009, 07:15:00 AM »

QUOTE(GiampyXBS @ Jan 30 2009, 08:53 AM)

(errata corrige,can't edit)

here is the Hex edit from the hacked.bin
IPB Image

an here the dummy.bin
IPB Image

i think it would be better if i send the box to m$ cause the waranty seal is good

but thanks 4 all

mucho181 · « **Reply #58 on:** January 30, 2009, 08:07:00 AM »

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

GiampyXBS · « **Reply #59 on:** January 30, 2009, 08:21:00 AM »

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!

Author Topic: Liteon Incomplete "drive Serial" (please Read All) (Read 348 times)