LITEON DG-16D2S 02510c dead after erasing, JF wont detect

[TorchLight]

Ok, so, I was updating to LT 2.0 from 1.91 and i erased my liteon. The problem is after i erased, i got disrupted and erased again - thats where my problem started as now Jungleflasher wont detect my drive etc.

Here is the log:




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

JungleFlasher 0.1.88 Beta (280)

Session Started Mon Oct 03 12:38:45 2011



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

portio64.sys Driver Installed

portio64.sys Driver Started, thanks Schtrom !

Found 4 I/O Ports.

Found 0 Com Ports.

Found 10 windows drives C: D: E: G: H: I: J: K: L: M:

Found 2 CD/DVD drives E: M:



Drive is Lite-On..

Loading firmware file D:\my firmware\Dummy.bin

MD5 hash: 1c1ed8d7b37aa6881b9ecac15b32803a

Inquiry string found

Identify string found

Drive key @ 0xA030 00000000000000000000000000000000 < --- nulled out drive key - i do have it

Firmware Osig: [PLDS DG-16D2S 8385]

Firmware is: LO83info Extract

Auto-Loading firmware file C:\Users\xxx\Desktop\JungleFlasher v0.1.88 Beta (280)\firmware\LTPlus-838v1.1.bin

MD5 hash: 020325ef05290fa80baec9863041a11c

Genuine LT plus v1.1

Drive key @ n/a 77777777777777777777777777777777

Firmware Osig: [PLDS DG-16D2S 8385]

Firmware is: LT-Plus 1.1

Spoofing Target

DVD Key copied to target

Target is LT - ID strings not copied to Target

Serial data copied from Source to Target



Spoofing Target

DVD Key already matches

Target is LT - ID strings not copied to Target

Serial data already matches



Loading firmware file C:\Users\xxx\Desktop\JungleFlasher v0.1.88 Beta (280)\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 0xEC00

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

Drive returned Status 0xD0

.........

Serial flash found with Status 0x72

Manufacturer ID: 0xC2

Device ID: 0x11

Flash Name: MXIC(MX25L2005)

Flash Size: 262144 bytes



Sending Lite-On-Erase request to port 0xEC00

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

Drive returned Status 0x72

Manufacturer ID: 0x0

Device ID: 0x0

Flash Name: Unknown type

Flash Size: n/a

Unknown flash type Erase aborted !

Unknown flash type Write aborted !

Sending Vendor Outro to port 0xEC00


And thats it. The drive wont detect, so i cant write the firmware to it. I forgot i erased it as i previously said and now it's fluffed - any suggestions would be greatly appreciated !!


EDIT - after the second erase, i think i clicked it again according to the jf log - silly me - and also, i tried writing but obviously that failed.

also - when i try the erase command again i get the following


Sending Lite-On-Erase request to port 0xE880
..............
Drive returned Status 0x7F
....................
Device Intro failed!

 

[diaboliq20]

Outro/ATA reset power off the drive.....close jungle flasher - u obviously have your dummy.bin.
power on drive - restart JF then Liteon erase untill u get it intro'd correrctly....
having loaded ur dummy and spoofed the ket to the LT firmware, then write to ur drive

 

[BL4K3Y]

As long as you got the drive key (dummy.bin), run the Lite-On Erase command again. If it goes into Vendor mode but doesn't show the chip type (MXIC/Winbond), simply click Intro/Device ID and follow the prompts then you should be able to write new firmware to the drive.

 

[TorchLight]

Thanks for the reply guys, but im having a real hard time getting the drive back into vendor mode - i run the liteon erase command and keep getting the following


Sending Lite-On-Erase request to port 0xE880
..............
Drive returned Status 0xFF
....................
Device Intro failed!

 

[BL4K3Y]

Try this, it worked for somebody else earlier .

 

[diaboliq20]

Are u using the right SATA port?
From first log - Sending Lite-On-Erase request to port 0xEC00

From second log -
Sending Lite-On-Erase request to port 0xE880
..............
Drive returned Status 0xFF
....................
Device Intro failed!

 

[johnno2]

use dosflash 2.0

 

[TorchLight]

Are u using the right SATA port?
From first log - Sending Lite-On-Erase request to port 0xEC00

From second log -
Sending Lite-On-Erase request to port 0xE880
..............
Drive returned Status 0xFF
....................
Device Intro failed!

Thanks ever so much, after the drive wouldnt detect i messed around with those - thanks for pointing it out!

after i reswitched to the CORRECT sata port -


Sending Lite-On-Erase request to port 0xE880
..............
Drive returned Status 0xFF
....................
Device Intro failed!

Sending Lite-On-Erase request to port 0xEC00
..............
Drive returned Status 0x80
........
Serial flash found with Status 0x72
Manufacturer ID: 0xC2
Device ID: 0x11
Flash Name: MXIC(MX25L2005)
Flash Size: 262144 bytes
Sending Vendor Intro to port 0xEC00

Serial flash found with Status 0x72

Sending Device ID request to port 0xEC00
Spi Status: 0x00
Manufacturer ID: 0xC2
Device ID: 0x11
Flash Name: MXIC(MX25L2005)
Flash Size: 262144 bytes

Getting Status from port 0xEC00
SPi flash found with Status 0x72

Sending Chip Erase to Port 0xEC00
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 !

dont know why i introd the drive but oh well its working now - thanks alot everybody!