LITEON DG-16D2S JF no longer detecting drive after failed erase
- Thread starter CrashanBurn
- Start date
Had a PC standing around ready for delivery.
Tried to power it by connecting it to that.
But exact same problem, powers on, then off again after a few seconds.
Only thing i can think of is the CK3mini being broken.
Gonna take apart my xbox, and connect that drive.
See if it is any different.
Tried to power it by connecting it to that.
But exact same problem, powers on, then off again after a few seconds.
Only thing i can think of is the CK3mini being broken.
Gonna take apart my xbox, and connect that drive.
See if it is any different.
It's definitely a drive issue.
I plugged in my own drive and the power from CK3mini stays on.
Plug the other one in, and it turns off after a few seconds.
I plugged in my own drive and the power from CK3mini stays on.
Plug the other one in, and it turns off after a few seconds.
Do you have a VIA card or another sata chipset you could also try?
Differant usb ports for usb pro?
Differant usb ports for usb pro?
Got the USB ports at the back of the computer, using front USB usually.
Don't have a VIA card sadly.
Don't have a VIA card sadly.
Was just messing around.
Figured i put my drive into the one i was supposed to flash.
So they got a working console, since i have no spare drive available(aside mine).
So i checked the folder which is supposed to have the dvd key from the broken drive.
But turns out JF only saved the dummy.bin, no identify, inquiry, key, serial.bin files.
So something more must have gone wrong.
I did not pay attention to it, since JF said the key was verified.
But apparently not saved.
Figured i put my drive into the one i was supposed to flash.
So they got a working console, since i have no spare drive available(aside mine).
So i checked the folder which is supposed to have the dvd key from the broken drive.
But turns out JF only saved the dummy.bin, no identify, inquiry, key, serial.bin files.
So something more must have gone wrong.
I did not pay attention to it, since JF said the key was verified.
But apparently not saved.
So you have both keys for both boxes.
The thing is you need to get the drive into 0x72 (vendor mode) to write fw to it. As you cant do this for what reason is unsure.
I personally would look at onboard sata on a pc and try recover from there. Seems strange the usbpro wont get the mode back.
The other thing would be flash another drive to ensure the usbpro see the 0x72 status but you could end up with 2 stuck drives
The thing is you need to get the drive into 0x72 (vendor mode) to write fw to it. As you cant do this for what reason is unsure.
I personally would look at onboard sata on a pc and try recover from there. Seems strange the usbpro wont get the mode back.
The other thing would be flash another drive to ensure the usbpro see the 0x72 status but you could end up with 2 stuck drives
Yeah, might have to see if i can find a PC that works with onboard sata.
But since from what i can tell files are missing from this drive i am unsure if even that matters.
the only file JF saved was the dummy.bin, no key.bin ect...
But since from what i can tell files are missing from this drive i am unsure if even that matters.
the only file JF saved was the dummy.bin, no key.bin ect...
Dummy.bin is all you will need, load it into source on firmware32 tab and you will see all your info there
Oh i figured something would be stored in those other files.
Guess there is still a tiny bit of hope then.
---------- Post added at 13:38 ---------- Previous post was at 13:30 ----------
Tried on this PC's sata, but can't figure out which port it would be on.
But its no VIA ship so not sure its even worth checking.
Guess there is still a tiny bit of hope then.
---------- Post added at 13:38 ---------- Previous post was at 13:30 ----------
Tried on this PC's sata, but can't figure out which port it would be on.
But its no VIA ship so not sure its even worth checking.
Last edited:
This might have happened because you plugged in the power cable inverted
so now the board is messed up. As when you plug in your other drive the power is not an issue.
You can switch the board or just dump your key and flash the other key on your drive
until you get a spare
so now the board is messed up. As when you plug in your other drive the power is not an issue.
You can switch the board or just dump your key and flash the other key on your drive
until you get a spare
Pretty sure i never put the cable in the wrong way.
Considering i was able to read out the key something else must have gone wrong.
I was actually able to get it erased earlier today.
But not long after the erase the CK3mini went down again.
Considering i was able to read out the key something else must have gone wrong.
I was actually able to get it erased earlier today.
But not long after the erase the CK3mini went down again.
Last edited:
i can assure you i went over every possible cable i could.
USB Port, USB cable, Sata cable, power cable, both molex to mini and mini to drive, tried powering it through PC.
Nothing of that worked.
What i still find weird is that it seems to work for a few seconds if i leave everything disconnected for a while.
I left it be for some hours, and then it sometimes stays powered for like 20 seconds.
Thats how i managed to get it into 0x72 earlier.
But as soon as the CK3 powers down its all gone again.
USB Port, USB cable, Sata cable, power cable, both molex to mini and mini to drive, tried powering it through PC.
Nothing of that worked.
What i still find weird is that it seems to work for a few seconds if i leave everything disconnected for a while.
I left it be for some hours, and then it sometimes stays powered for like 20 seconds.
Thats how i managed to get it into 0x72 earlier.
But as soon as the CK3 powers down its all gone again.
- Mar 1, 2010
- 3,346
- 128
The opening paragraph made me lol....
It failed erase but now it doesnt show or eject.
Errm, that kind of means it is erased....
I've erased Lite-On's upwards of 3000 times and it's never failed
It failed erase but now it doesnt show or eject.
Errm, that kind of means it is erased....
I've erased Lite-On's upwards of 3000 times and it's never failed
Well thats what it looked like to me.
Since it did not give me anything else but this in my log
Getting Status from port 0x0000
Invalid Status 0x80
Hence why i assumed it was a failed erase.
But even so, if it did erase then there is no reason why suddenly it would power down the ck3
I don't have another drive which i can flash right now.
But i know when connecting my own drive, which already is flashed the ck3 keeps on running.
But i know when connecting my own drive, which already is flashed the ck3 keeps on running.
meads1970
BANNED
one of the very fist drives i flashed i put the power source cable the wrong way round into the back of the drive by accident ,i was able to read it and dump the drive files but that was all as i killed the drive:rolleyes2: