GENERAL rrod error 64

cindijanel

Full Member
May 22, 2014
31
0
Well, I attempted my first flash this week and thought it went okay. drive keys matched and everything seemed okay until I put it back together. the bottom right section flashes red and the screen shows error 64. I looked it up and is a dvd drive error probably because of wrong firmware. Obviously I am a noob so how do I fix this before it gets worse?
 

nofeloniesyet

VIP Member
Jan 16, 2011
4,830
128
Nowhere
flash the orig fw back to it,make sure u update to very latest dash,then try reflashing.what fw did it say you were on?
 

cindijanel

Full Member
May 22, 2014
31
0
It a while to get it done right so here is my entire log

Loading firmware file C:\Users\bolen_000\Desktop\Dummy.bin
MD5 hash: 0cc34b1c369455ad5e24b3393687edae
Inquiry string found
Identify string found
Drive key @ 0xA030 C5EC19525F0E20F0F6F4C699D96DEF9F
Firmware Osig: [PLDS DG-16D2S 0251]
Firmware is: PhatKey Extract
Drive is Lite-On..
Key found in KeyDB at record (1 - Desktop)
Key is: C5EC19525F0E20F0F6F4C699D96DEF9F
Key has been tested and verified, thanks C4eva !
Sending Vendor Intro to port 0x0000
Status 0x51
Re-sending Vendor Intro:
.
Serial flash found with Status 0x52
Extracted drive key failed Verification !

PhatKey extraction failed!
Drive is Lite-On..
Key found in KeyDB at record (1 - Desktop)
Key is: C5EC19525F0E20F0F6F4C699D96DEF9F
Key has been tested and verified, thanks C4eva !
Sending Vendor Intro to port 0x0000
Status 0x51
Re-sending Vendor Intro:
.
Serial flash found with Status 0x52
Extracted drive key passed Verification !
key returned: C5EC19525F0E20F0F6F4C699D96DEF9F
0000: 05 80 00 32 5B 00 00 00 - 50 4C 44 53 20 20 20 20 ...2[...PLDS
0010: 44 47 2D 31 36 44 32 53 - 20 20 20 20 20 20 20 20 DG-16D2S
0020: 30 32 35 31 30 43 41 30 - 41 30 44 36 30 38 43 47 02510CA0A0D608CG
0030: 37 33 38 38 30 38 30 30 - 33 34 38 20 20 20 00 00 73880800348 ..
0040: 00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 ................
0050: 00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 ................
0000: 05 80 00 32 5B 00 00 00 - 50 4C 44 53 20 20 20 20 ...2[...PLDS
0010: 44 47 2D 31 36 44 32 53 - 20 20 20 20 20 20 20 20 DG-16D2S
0020: 30 32 35 31 30 43 20 20 - 00 00 00 00 00 00 00 00 02510C ........
0030: 00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 ................
0040: 00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 ................
0050: 00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 ................
0000: C0 85 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 ................
0010: 00 00 00 00 44 36 30 38 - 43 47 37 33 38 38 30 38 ....D608CG738808
0020: 30 30 33 34 38 20 20 20 - 00 00 00 00 00 00 32 30 00348 ......20
0030: 31 35 43 30 20 20 4C 50 - 53 44 20 20 20 20 47 44 15C0 LPSD GD
0040: 31 2D 44 36 53 32 20 20 - 20 20 20 20 20 20 20 20 1-D6S2
0050: 20 20 20 20 20 20 20 20 - 20 20 20 20 20 20 00 00 ..
0060: 00 00 00 0B 00 00 00 04 - 00 02 06 00 00 00 00 00 ................
0070: 00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 ................
0080: 03 00 78 00 78 00 E3 00 - 78 00 00 00 00 00 00 00 ..x.x...x.......
0090: 00 00 00 00 00 00 00 00 - 02 02 00 00 68 00 00 00 ............h...
00A0: 00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 ................
00B0: 20 20 00 00 ..
0000: 44 36 30 38 43 47 37 33 - 38 38 30 38 30 30 33 34 D608CG7388080034
0010: 38 20 20 20 FF FF FF FF - FF FF FF FF FF FF FF FF 8 ............
0020: FF FF FF FF FF FF FF FF - 41 30 FF FF FF FF FF FF ........A0......
0030: FF FF FF FF FF FF FF FF - FF FF FF FF FF FF FF FF ................
0040: FF FF FF FF FF FF FF FF - FF FF FF FF 41 30 FF FF ............A0..

Dummy.bin file saved to Dummy.bin
Loading firmware from buffer
Inquiry string found
Identify string found
Drive key @ 0xA030 C5EC19525F0E20F0F6F4C699D96DEF9F
Firmware Osig: [PLDS DG-16D2S 0251]
Firmware is: PhatKey Extract
Key database updated
XECUTER X360USB PRO removed.
XECUTER X360USB PRO attached.
Drive is Lite-On..
Key found in KeyDB at record (1 - Desktop)
Key is: C5EC19525F0E20F0F6F4C699D96DEF9F
Key has been tested and verified, thanks C4eva !
Loading firmware file C:\Users\bolen_000\Desktop\Serial.bin
MD5 hash: 5f9dc2d8bf60f1fbde4d1a2f03a8648e
Inquiry string found
Identify string found
Drive key @ 0xA030 C5EC19525F0E20F0F6F4C699D96DEF9F
Firmware Osig: [PLDS DG-16D2S 0251]
Firmware is: PhatKey Extract
Drive is Lite-On..
Key found in KeyDB at record (2 - Desktop)
Key is: C5EC19525F0E20F0F6F4C699D96DEF9F
Key has been tested and verified, thanks C4eva !
Sending Vendor Intro to port 0x0000
Status 0x51
Re-sending Vendor Intro:
.
Serial flash found with Status 0x52
Extracted drive key passed Verification !
key returned: C5EC19525F0E20F0F6F4C699D96DEF9F
0000: 05 80 00 32 5B 00 00 00 - 50 4C 44 53 20 20 20 20 ...2[...PLDS
0010: 44 47 2D 31 36 44 32 53 - 20 20 20 20 20 20 20 20 DG-16D2S
0020: 30 32 35 31 30 43 41 30 - 41 30 44 36 30 38 43 47 02510CA0A0D608CG
0030: 37 33 38 38 30 38 30 30 - 33 34 38 20 20 20 00 00 73880800348 ..
0040: 00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 ................
0050: 00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 ................
0000: 05 80 00 32 5B 00 00 00 - 50 4C 44 53 20 20 20 20 ...2[...PLDS
0010: 44 47 2D 31 36 44 32 53 - 20 20 20 20 20 20 20 20 DG-16D2S
0020: 30 32 35 31 30 43 20 20 - 00 00 00 00 00 00 00 00 02510C ........
0030: 00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 ................
0040: 00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 ................
0050: 00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 ................
0000: C0 85 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 ................
0010: 00 00 00 00 44 36 30 38 - 43 47 37 33 38 38 30 38 ....D608CG738808
0020: 30 30 33 34 38 20 20 20 - 00 00 00 00 00 00 32 30 00348 ......20
0030: 31 35 43 30 20 20 4C 50 - 53 44 20 20 20 20 47 44 15C0 LPSD GD
0040: 31 2D 44 36 53 32 20 20 - 20 20 20 20 20 20 20 20 1-D6S2
0050: 20 20 20 20 20 20 20 20 - 20 20 20 20 20 20 00 00 ..
0060: 00 00 00 0B 00 00 00 04 - 00 02 06 00 00 00 00 00 ................
0070: 00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 ................
0080: 03 00 78 00 78 00 E3 00 - 78 00 00 00 00 00 00 00 ..x.x...x.......
0090: 00 00 00 00 00 00 00 00 - 02 02 00 00 68 00 00 00 ............h...
00A0: 00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 ................
00B0: 20 20 00 00 ..
0000: 44 36 30 38 43 47 37 33 - 38 38 30 38 30 30 33 34 D608CG7388080034
0010: 38 20 20 20 FF FF FF FF - FF FF FF FF FF FF FF FF 8 ............
0020: FF FF FF FF FF FF FF FF - 41 30 FF FF FF FF FF FF ........A0......
0030: FF FF FF FF FF FF FF FF - FF FF FF FF FF FF FF FF ................
0040: FF FF FF FF FF FF FF FF - FF FF FF FF 41 30 FF FF ............A0..

Dummy.bin file saved to Dummy.bin
Loading firmware from buffer
Inquiry string found
Identify string found
Drive key @ 0xA030 C5EC19525F0E20F0F6F4C699D96DEF9F
Firmware Osig: [PLDS DG-16D2S 0251]
Firmware is: PhatKey Extract
Key database updated
Loading firmware file C:\Users\bolen_000\Desktop\Dummy.bin
MD5 hash: 0cc34b1c369455ad5e24b3393687edae
Inquiry string found
Identify string found
Parse Failed !
Drive is Lite-On..
Key found in KeyDB at record (2 - Desktop)
Key is: C5EC19525F0E20F0F6F4C699D96DEF9F
Key has been tested and verified, thanks C4eva !
Sending Vendor Intro to port 0x0000
Status 0x51
Re-sending Vendor Intro:
........................................................................
Device Intro failed!
PhatKey extraction failed!
Drive is Lite-On..
Key found in KeyDB at record (2 - Desktop)
Key is: C5EC19525F0E20F0F6F4C699D96DEF9F
Key has been tested and verified, thanks C4eva !
Sending Vendor Intro to port 0x0000
Status 0x51
Re-sending Vendor Intro:
........................................................................
Device Intro failed!
PhatKey extraction failed!
Drive is Lite-On..
Key found in KeyDB at record (2 - Desktop)
Key is: C5EC19525F0E20F0F6F4C699D96DEF9F
Key has been tested and verified, thanks C4eva !
Sending Vendor Intro to port 0x0000
Status 0x51
Re-sending Vendor Intro:
........................................................................
Device Intro failed!
PhatKey extraction failed!

No Drive Detected! DVDkey files extraction aborted!
Drive is Lite-On..
Key found in KeyDB at record (2 - Desktop)
Key is: C5EC19525F0E20F0F6F4C699D96DEF9F
Key has been tested and verified, thanks C4eva !
Sending Vendor Intro to port 0x0000
Status 0x51
Re-sending Vendor Intro:
........................................................................
Device Intro failed!
PhatKey extraction failed!
Drive is Lite-On..
Key found in KeyDB at record (2 - Desktop)
Key is: C5EC19525F0E20F0F6F4C699D96DEF9F
Key has been tested and verified, thanks C4eva !
Sending Vendor Intro to port 0x0000
Status 0x51
Re-sending Vendor Intro:
........................................................................
Device Intro failed!
PhatKey extraction failed!
Drive is Lite-On..
Key found in KeyDB at record (2 - Desktop)
Key is: C5EC19525F0E20F0F6F4C699D96DEF9F
Key has been tested and verified, thanks C4eva !
Sending Vendor Intro to port 0x0000
Status 0x51
Re-sending Vendor Intro:
........................................................................
Device Intro failed!
PhatKey extraction failed!
Drive is Lite-On..
Key found in KeyDB at record (2 - Desktop)
Key is: C5EC19525F0E20F0F6F4C699D96DEF9F
Key has been tested and verified, thanks C4eva !
Sending Vendor Intro to port 0x0000
Status 0x51
Re-sending Vendor Intro:
........................................................................
Device Intro failed!
PhatKey extraction failed!
Drive is Lite-On..
Key found in KeyDB at record (2 - Desktop)
Key is: C5EC19525F0E20F0F6F4C699D96DEF9F
Key has been tested and verified, thanks C4eva !
Sending Vendor Intro to port 0x0000
Status 0x51
Re-sending Vendor Intro:
........................................................................
Device Intro failed!
PhatKey extraction failed!
Drive is Lite-On..
Key found in KeyDB at record (2 - Desktop)
Key is: C5EC19525F0E20F0F6F4C699D96DEF9F
Key has been tested and verified, thanks C4eva !
Sending Vendor Intro to port 0x0000
Status 0x51
Re-sending Vendor Intro:
........................................................................
Device Intro failed!
PhatKey extraction failed!

Getting Status from port 0x0000
Invalid Status 0x0
Loading firmware file C:\Users\bolen_000\Desktop\jungle\JungleFlasher v0.1.96 Beta (323)\firmware\Latest_iXtreme_and_Stock_Firmware_Pack\Firmware\LTPlus-0225-v3.0.bin
MD5 hash: 1a38d3a2a6519339599fa1866642c513
Genuine LT plus v3.0
Drive key @ n/a FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF
Firmware Osig: [PLDS DG-16D4S 0225]
Firmware is: LT-Plus 3.0
Loading firmware file C:\Users\bolen_000\Desktop\jungle\JungleFlasher v0.1.96 Beta (323)\firmware\Latest_iXtreme_and_Stock_Firmware_Pack\Firmware\LTPlus-0225-v3.0u.bin
MD5 hash: db5c70eaaabb53501c2c4f53dce9abfd
Genuine LT plus v3.0 (9504 upgrade)
Drive key @ n/a FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF
Firmware Osig: [PLDS DG-16D4S 0225]
Firmware is: LT-Plus 3.0
Loading firmware file C:\Users\bolen_000\Desktop\jungle\JungleFlasher v0.1.96 Beta (323)\firmware\Latest_iXtreme_and_Stock_Firmware_Pack\Firmware\LTPlus-0251-v3.0.bin
MD5 hash: d14fe82b96741b7a18e5c1e7adbf0a98
Genuine LT plus v3.0
Drive key @ n/a FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF
Firmware Osig: [PLDS DG-16D2S 0251]
Firmware is: LT-Plus 3.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 0x90
................
Serial flash found with Status 0x72
Manufacturer ID: 0xC2
Device ID: 0x11
Flash Name: MXIC(MX25L2005)
Flash Size: 262144 bytes
Sending Vendor Outro to port 0x0000
 

Antalpromille

VIP Member
Aug 4, 2011
3,146
0
Borås, sweden
You are supposed to write the FW to the drive after you erase it.
 

cindijanel

Full Member
May 22, 2014
31
0
ok, I opened JF back up, and I have a file called latest Iextreme and stock firmware pack in the firmware folder. in JF under drive properties it says drive not detected. can you point me in the right direction? if you get me back to the probing point I think I can take it from there. So, I did everything right except for not writing the fw after erasing?
 

Antalpromille

VIP Member
Aug 4, 2011
3,146
0
Borås, sweden
Load your source (your extracted dummy that is), load the target FW. Re-erase the drive and when you have got it intro'ed just writer the FW to it.
 
  • Like
Reactions: cindijanel

cindijanel

Full Member
May 22, 2014
31
0
Is this lookin right?

Sending Lite-On-Erase request to port 0x0000
..............
Drive returned Status 0x0
...........
Serial flash found with Status 0x72
Manufacturer ID: 0xC2
Device ID: 0x11
Flash Name: MXIC(MX25L2005)
Flash Size: 262144 bytes
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 Slim Lite-On..
Key found in KeyDB at record (4 - Desktop)
Key is: C5EC19525F0E20F0F6F4C699D96DEF9F
Key has been tested and verified, thanks C4eva !
 

GeekHeat

VIP Member
Jun 28, 2013
1,805
88
lancashire
Is this lookin right?

Sending Lite-On-Erase request to port 0x0000
..............
Drive returned Status 0x0
...........
Serial flash found with Status 0x72
Manufacturer ID: 0xC2
Device ID: 0x11
Flash Name: MXIC(MX25L2005)
Flash Size: 262144 bytes
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 Slim Lite-On..
Key found in KeyDB at record (4 - Desktop)
Key is: C5EC19525F0E20F0F6F4C699D96DEF9F
Key has been tested and verified, thanks C4eva !
looks good to me.
 
  • Like
Reactions: cindijanel

nofeloniesyet

VIP Member
Jan 16, 2011
4,830
128
Nowhere
Is this lookin right?

Sending Lite-On-Erase request to port 0x0000
..............
Drive returned Status 0x0
...........
Serial flash found with Status 0x72
Manufacturer ID: 0xC2
Device ID: 0x11
Flash Name: MXIC(MX25L2005)
Flash Size: 262144 bytes
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 Slim Lite-On..
Key found in KeyDB at record (4 - Desktop)
Key is: C5EC19525F0E20F0F6F4C699D96DEF9F
Key has been tested and verified, thanks C4eva !
should work now
 
  • Like
Reactions: cindijanel

meads1970

BANNED
Jul 5, 2011
721
0
Lancashire
Is this lookin right?

Sending Lite-On-Erase request to port 0x0000
..............
Drive returned Status 0x0
...........
Serial flash found with Status 0x72
Manufacturer ID: 0xC2
Device ID: 0x11
Flash Name: MXIC(MX25L2005)
Flash Size: 262144 bytes
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 Slim Lite-On..
Key found in KeyDB at record (4 - Desktop)
Key is: C5EC19525F0E20F0F6F4C699D96DEF9F
Key has been tested and verified, thanks C4eva !
perfect :cool2:
 
  • Like
Reactions: cindijanel

cindijanel

Full Member
May 22, 2014
31
0
ok, the error 64 is gone but now it wont read legit games. put nba2k14 in an it said reading then said "open tray". is it a flashing issue or hardware damage of some kind? Fixable?
 

cindijanel

Full Member
May 22, 2014
31
0
Sending Lite-On-Erase request to port 0x0000
..............
Drive returned Status 0x0
...........
Serial flash found with Status 0x72
Manufacturer ID: 0xC2
Device ID: 0x11
Flash Name: MXIC(MX25L2005)
Flash Size: 262144 bytes
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 Slim Lite-On..
Key found in KeyDB at record (4 - Desktop)
Key is: C5EC19525F0E20F0F6F4C699D96DEF9F
Key has been tested and verified, thanks C4eva !

is it supposed to say drive is Slim Lite-on? it was a phat flash
 

CptKlink

Senior Member
May 2, 2014
122
0
I have a feeling you flashed the wrong firmware to the drive. If your flashing a phat lite on drive you need the file called LTPlus-0251-v3.0.bin from the firmware pack. you can get the pack from this link http://www.ixtreme.net/ixtreme-lt-lite-touch-download/21442-ixtreme-lt-3-0-download.html . Don't auto load the firmware pick it manually. How to do that is once you load your source Firmware (dummy.bin) click on the Open Target Firmware button and select the LTPlus-0251-v3.0.bin file. And don't forget to click on the spoof source to target button once you load/open the target firmware.

If you really wanted you could send me your dummy.bin and i will prepare the target firmware for you if you like then i could send you back the ready to be flashed LT+3.0 firmware for your drive. But its pretty easy to do your self.
 
Last edited:
  • Like
Reactions: cindijanel

cindijanel

Full Member
May 22, 2014
31
0
I loaded the dummybin then loaded the ltplus-0251-v3.0.bin file and spoofed it. but when I go to do the liteon erase and write I get a unhandled exception error message. on the mtk tab it says status 0x0 in flash chip properties and the other fields are blank. is that right?