|
LiteOn 93450C Bad Flash
|
|
|
WheelCC
Newbie
|
18. October 2011 @ 17:01 |
Link to this message
|
I believe I might have bricked or in some way destroyed my LiteOn drive. The drive is pre13141 and currently has lt + 1.1. I was trying to flash the 93450C drive with a CK3 Probe and a Connectivity Kite Lite. I have a sata connection which has worked for several Samsung drives. I have a p45 chipset and Win7 x64.
I pressed the PhatKey in JungleFlasher and folowed the instructions but the key extraction failed. I tried to repeat the process but now JungleFlasher won't recognize my drive. Also the drive stopped working in the xbox. When i try to eject it just says "Opening" and nothing else, the drive is completely quiet and doesn't react at all.
Is the drive completely ruined or can it be saved in any way?
|
|
Advertisement
|
 |
|
|
|
peluynati
Senior Member
|
18. October 2011 @ 23:36 |
Link to this message
|
|
did you outro the drive?
|
|
WheelCC
Newbie
|
19. October 2011 @ 02:54 |
Link to this message
|
|
No, was I suposed to do that? I pressed Phatkey again but it couldn't recognize the drive any more.
|
|
Modking30
AfterDawn Addict
|
19. October 2011 @ 15:07 |
Link to this message
|
Originally posted by WheelCC:
No, was I suposed to do that? I pressed Phatkey again but it couldn't recognize the drive any more.
Yes you are. Otherwise do you have a dump of the OFW? These things are tough to brick. It might not be showing up because you sent and erase. If you have the OFW, just resend the erase and reflash.
|
Senior Member
|
19. October 2011 @ 15:49 |
Link to this message
|
|
Are we sure these liteon drives that seem to become non flashable don't have a mra based device in them. I have ran across a system I was flashing for a friend that it happened to. Turns out it has a litekey v1.3 in it. I think the litekey must have been set to block writing to the chip. We just replaced his drive and flashed it. I will at a later time replace this ones pcb if I can not figure out what the problem is.
|
|
peluynati
Senior Member
|
19. October 2011 @ 16:24 |
Link to this message
|
|
i'm having an issue right now with a liteon, batman game is causing weird codes, keeps saying damaged download content, and there is no download content, burnt it to 3 verbatims which were used in other systems with no issue, but this one box keeps throwing the code, first time at 15%, then 32%, and now 54%, i changed the drive in it with another liteon and its still throwing that code, any ideas?
|
|
WheelCC
Newbie
|
19. October 2011 @ 16:29 |
Link to this message
|
Quote:
Yes you are. Otherwise do you have a dump of the OFW? These things are tough to brick. It might not be showing up because you sent and erase. If you have the OFW, just resend the erase and reflash.
If you read what I wrote you'll se that the drive froze after i tried to extract the DVDkey by using PMT. I never got to the stage of erasing the drive and i have neither the DVDkey nor the dummy.bin.
Some other people I talked to suggested that I probed the wrong point and not MPX01 and burned the drive by doing so. I haven't found anyone with the exact same problem as me. Am I a lousy finder or is this unusal? ^^
This message has been edited since posting. Last time this message was edited on 19. October 2011 @ 16:34
|
|
Modking30
AfterDawn Addict
|
19. October 2011 @ 16:59 |
Link to this message
|
Originally posted by WheelCC:
Quote:
Yes you are. Otherwise do you have a dump of the OFW? These things are tough to brick. It might not be showing up because you sent and erase. If you have the OFW, just resend the erase and reflash.
If you read what I wrote you'll se that the drive froze after i tried to extract the DVDkey by using PMT. I never got to the stage of erasing the drive and i have neither the DVDkey nor the dummy.bin.
Some other people I talked to suggested that I probed the wrong point and not MPX01 and burned the drive by doing so. I haven't found anyone with the exact same problem as me. Am I a lousy finder or is this unusal? ^^
I doubt you can burn the pcb by probing the wrong hole but I have never done that. If you didn't erase, then I'd say its your crappy chipset. Get a via card like everyone else.
|
|
WheelCC
Newbie
|
19. October 2011 @ 17:10 |
Link to this message
|
My chipset has worked fine for several other drives but I can understand if it doesn't work with LiteOn drives but how can my chipset have ruined my drive :S. As i said the drive doesn't work in the 360 either and doesn't respond to any open/close commands. It's completely dead and became so after I tried to extract the key, never erased.
|
|
peluynati
Senior Member
|
19. October 2011 @ 17:16 |
Link to this message
|
|
did you by any chance hit the 0x00 button at the bottom?
|
|
WheelCC
Newbie
|
19. October 2011 @ 17:22 |
Link to this message
|
|
I never used the "MTK Flash 32" tab, the only thing I did was press PhatKey and probe MPX01. Also i tested the drive with the Connectivity kit again and it doesn't respond to the connectivity kit eject button either.
|
|
peluynati
Senior Member
|
19. October 2011 @ 17:29 |
Link to this message
|
|
are you sure you did not plug the drive in upside down?
|
|
WheelCC
Newbie
|
19. October 2011 @ 17:33 |
Link to this message
|
|
I checked that several times before starting up the drive and I did not force-plug anything in. I'm allmost 100% sure it was correctly plugged in.
|
|
Advertisement
|
|
|
|
peluynati
Senior Member
|
19. October 2011 @ 18:19 |
Link to this message
|
|
the only time i have seen what you describe the drive was plugged in upside down and fried, look around the r707 area of the board and see if you see anything fried.
|
