LITEON DG-16D2S LT+2.0 Flash question

n0syst3m

VIP Member
Sep 17, 2011
203
0
North East ;)
if everythings went well and flashed ok then your key will be in the JF key db :)

Test it on your console and find out 4 sure if everythings 100%
 

DärkRaven

Full Member
Feb 24, 2010
88
0
Here's the log

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

JungleFlasher 0.1.88 Beta (280)

Session Started Wed Oct 05 20:09:45 2011



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

portio64.sys Driver Installed 

portio64.sys Driver Started, thanks Schtrom ! 

Found 6 I/O Ports.

Found 1 Com Ports.

Found 8 windows drives A: C: D: E: F: G: I: K:

Found 2 CD/DVD drives D: G:



Loading firmware file C:\XBOX\xbox drive key\Dummy.bin

MD5 hash:  87bcedd238ff79563278340b27185b50

Inquiry string found

Identify string found

Drive key @ 0xA030 F84B4C5B4C9519A34F1E3CFB1DE712A5

Firmware Osig: [PLDS    DG-16D2S        7485]

Firmware is:  DVDKey32 extract                

Loading firmware file C:\XBOX\xbox drive key\Dummy.bin

MD5 hash:  87bcedd238ff79563278340b27185b50

Inquiry string found

Identify string found

Drive key @ 0xA030 F84B4C5B4C9519A34F1E3CFB1DE712A5

Firmware Osig: [PLDS    DG-16D2S        7485]

Firmware is:  DVDKey32 extract                

Loading firmware file C:\Users\Tiago\Desktop\ieXtreme LT 2.0\Latest_iXtreme_and_Stock_Firmware_Pack\Firmware\LTPlus-025-v2.0.bin

MD5 hash:  0264149996f783b54629c1598072e50e

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



Target rev is LT 02510C, serial info not copied



Sending Lite-On-Erase request to port 0xA880

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

Drive returned Status 0xD0

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

Serial flash found with Status 0x72

Manufacturer ID: 0xC2

Device ID: 0x11

Flash Name:  MXIC(MX25L2005)

Flash Size:  262144 bytes



Getting Status from port 0xA880

SPi flash found with Status 0x72



Sending Chip Erase to Port 0xA880

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 0xA880

Drive is Lite-On..
like i said it looks fine just didnt get the key verified at the end for some reason : o you guys think its fine?

Edit: burned Deux Ex Human revolution works fine, Don't have any XDR3 games yet so those I cant say if they work but at least the pre XDR3 games seem to be booting. Hopefully its nothing serious :)
 
Last edited:

GhostFace606

VIP Member
Jan 31, 2011
802
0
TanonymousX
Is that mandatory GhostFace606? I had to unplug everything to test if a pre XDR3 game would boot. Might this bring me any issues with XDR3 games or?
Outroing the drive once is mandatory,some times you have stubborn drives that will not realease from jf,it's ok to do to outro more than once all that your doing at this point is realeasing the drive from jf.

Slim drives are worse I always have to outro at least twice.

But never do I put the drive back in my xbox or anyone's until I get the key verified in jf feel more confident when in see the key has been verified.
 
Last edited:

DärkRaven

Full Member
Feb 24, 2010
88
0
Outroing the drive once is mandatory,some times you have stubborn drives that will not realease from jf,it's ok to do to outro more than once all that your doing at this point is realeasing the drive from jf.

Slim drives are worse I always have to outro at least twice.
Hm, but the outro went fine, if you take a peek at the log it shows "drive is Liteon" at the end so everything went fine. I'm just wondering about the key verification thing though. Like I said pre XDR3 games are booting fine.
 

sp4rkst4rt3r

VIP Member
Oct 9, 2010
2,126
0
North-West (UK)
Connect your drive to JF and refresh your port then load your dummy.bin to source. Right click in the source are and scroll down to 'Verify Key' and JF will verify it for you :)
 

DärkRaven

Full Member
Feb 24, 2010
88
0
Connect your drive to JF and refresh your port then load your dummy.bin to source. Right click in the source are and scroll down to 'Verify Key' and JF will verify it for you :)
Key NOT in KeyDB
Key is: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Key has been tested and verified, thanks C4eva !

Yup Sp4kst4rt3r Thats twice you've saved my butt today, thanks mate :)

i decided i wanted to keep my key to myself for some reason :p