LITEON 74850 Updating to LT+2.0, can't get past 0x80...

A

allisd00m

Junior Member
Sep 22, 2011
12
0
Devon, UK
OK, using an X360USB Pro and CK3 pro. Flashed drive to 1.9 a few weeks back, then a couple days later 1.91. Had the latest dashboard from first to current flash. I did the same as when I updated to 1.91:

Loaded dummy file, auto loaded 2.0 (which added in correct key etc), then went to flash tab, drive and everything (drive, USBpro) was detected, port 0x0000. Clicked erase, said OK, waited for the 0x90 status to flick the switch on the CK3 but it just went to 0x80, which I've tried power cylcing multiple times but nothing. Refreshing ports made the drive become undetectable (erased). Tried flashing, power cycling, can't get past 0x80.

Looked up on this and seems different causes, fixes etc but none of which have helped me. Not tried writing in DOS yet as it will be a last resort (looks complicated)

log:





~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

JungleFlasher 0.1.88 Beta (280)

Session Started Mon Oct 03 16:32:02 2011



This is a Wow 64 process running on 8 x 64 bit CPUs

X360USB PRO detected, Version 0.18



Found 1 I/O Ports.

Found 2 Com Ports.

Found 5 windows drives A: C: D: E: F:

Found 1 CD/DVD drives E:



Loading firmware file C:\Users\Ben\Desktop\archive\JungleFlasher v0.1.88 Beta (280)\firmware\Dummy_2.bin

MD5 hash: ab2bf13c132ab****************

Inquiry string found

Identify string found

Drive key @ 0xA030 ************************

Firmware Osig: [PLDS DG-16D2S 0251]

Firmware is: PhatKey Extract

Auto-Loading firmware file C:\Users\Ben\Desktop\archive\JungleFlasher v0.1.88 Beta (280)\firmware\LTPlus-025-v2.0.bin

MD5 hash: 0264149996f783b******************

Genuine LT plus v2.0

Drive key @ n/a FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF

Firmware Osig: [PLDS DG-16D2S 0251]

Firmware is: LT-Plus 2.0

Spoofing Target

DVD Key copied to target

Target is LT - ID strings not copied to Target

Serial data already matches



Target rev is LT 02510C, serial info not copied



Sending Lite-On-Erase request to port 0x0000

..............

Drive returned Status 0x80

....................

Device Intro failed!



Sending Lite-On-Erase request to port 0x0000

..............

Drive returned Status 0x80

....................

Device Intro failed!



Sending Lite-On-Erase request to port 0x0000

..............

Drive returned Status 0x80

....................

Device Intro failed!



Sending Lite-On-Erase request to port 0x0000

..............

Drive returned Status 0x80

....................

Device Intro failed!




Any ideas?:facepalm:

Thanks.
 
Last edited:
A

allisd00m

Junior Member
Sep 22, 2011
12
0
Devon, UK
I just tried that a few times and no luck. After I power cycle for the second time and wait for it to finish (and fail), when I click Liteon erase again it just restarts the process rather than go to any other status.

UPDATE: oh my god, this may sound ridiculous, but I thought just to triple, quadruple, whatever check just before I posted that, I would try again. just to have the EXACT same set up as times before, I replaced the SHORT power cable to the CK3 pro to the longer one that comes with the Probe (what I used before) as well as changing the molex cable. Following that tutorial, well, I'll post the log of what happened:

Code: 
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

JungleFlasher 0.1.88 Beta (280)

Session Started Mon Oct 03 17:59:11 2011



This is a Wow 64 process running on 8 x 64 bit CPUs 

X360USB PRO detected, Version 0.18



Found 1 I/O Ports.

Found 2 Com Ports.

Found 6 windows drives A: C: D: E: F: G:

Found 1 CD/DVD drives E:



Loading firmware file C:\Users\Ben\Desktop\archive\xbox\JungleFlasher\Firmware\Dummy.bin

MD5 hash:  ab2bf13c132ab13fdf55ad21d630ecb6

Inquiry string found

Identify string found

Drive key @ 0xA030 XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

Firmware Osig: [PLDS    DG-16D2S        0251]

Firmware is:  PhatKey Extract                 

Auto-Loading firmware file C:\Users\Ben\Desktop\archive\JungleFlasher v0.1.88 Beta (280)\firmware\LTPlus-025-v2.0.bin

MD5 hash:  0264149996f783b54629c1598072e50e

Genuine LT plus v2.0

Drive key @ n/a XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

Firmware Osig: [PLDS    DG-16D2S        0251]

Firmware is:  LT-Plus 2.0                     

Spoofing Target

DVD Key copied to target

Target is LT - ID strings not copied to Target

Serial data already matches



Target rev is LT 02510C, serial info not copied



Sending Lite-On-Erase request to port 0x0000

..............

Drive returned Status 0x80

....................

Device Intro failed!



Sending Lite-On-Erase request to port 0x0000

..............

Drive returned Status 0x80

....................

Device Intro failed!

Lite-On-Erase NOT sent 



Sending Lite-On-Erase request to port 0x0000

..............

Drive returned Status 0x80

....................

Device Intro failed!



Sending Lite-On-Erase request to port 0x0000

..............

Drive returned Status 0x80

....................

Device Intro failed!



Sending Lite-On-Erase request to port 0x0000

..............

Drive returned Status 0x0

.........

Serial flash found with Status 0x72

Manufacturer ID: 0xEF

Device ID: 0x11

Flash Name:  Winbond/NEX(W25P20/NX25P20)

Flash Size:  262144 bytes

Lite-On-Erase NOT sent 



Getting Status from port 0x0000

SPi flash found with Status 0x72



Sending Chip Erase to Port 0x0000

Erasing:

Writing target buffer to flash

Writing Bank 0: ................

Writing Bank 1: ................

Writing Bank 2: ................

Writing Bank 3: ................



Flash Verification Test !

Reading Bank 0: ................

Reading Bank 1: ................

Reading Bank 2: ................

Reading Bank 3: ................

Write verified OK !



Sending Vendor Outro to port 0x0000

Drive is Lite-On.. 



Key found in KeyDB at record (1 - Downloads)

Key is: XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

Key has been tested and verified, thanks C4eva !


very very very weird, but it appears to be working. Can't thank you enough man...
 
Last edited by a moderator:
manwithoutname

manwithoutname

1
Jun 4, 2010
3,080
0
A

allisd00m

Junior Member
Sep 22, 2011
12
0
Devon, UK
Unless I'm mistaken - and I very well could be - isn't my drive key personal to my motherboard, and needed just to match up with my personal hardware? I.e. anybody trying to use my drive key wouldn't get very far if paired with their own specific hardware keys?
 
Last edited:
manwithoutname

manwithoutname

1
Jun 4, 2010
3,080
0
That is correct ...
 
S

Slider21

Junior Member
Dec 20, 2010
16
0
Essex
Could m$ not trace your xbox if on live and this could lead to a possible flag.

Sorry if im wrong only trying to help
 
Last edited:
manwithoutname

manwithoutname

1
Jun 4, 2010
3,080
0
Trust me this as friendly as it gets on here :D
 
manwithoutname

manwithoutname

1
Jun 4, 2010
3,080
0
So you think that MS will devise a system to scan the net for DVD drive keys? With today's technology and the vast number of users all detection methods are based on automated systems and this what caused the last MS major ban problems.

Even if I worked for MS I wouldn't think of looking for DVD keys as this doesn't prove anything and it's not practical. The detection has to come from within the console it self else MS has no grounds of enforcing the ban with the terms of law.

If you think about it, car number plates are being cloned and we've seen how people use this to evade parking and driving fines. Yet you don't see everyone hiding their number plates.
 
You must log in or register to reply here.