Dead Philips.PCDV5016 (rebadged LiteOn SOHD-16P9S)

vbimport

#1

with no reason at all restarted the pc and the drive “dead Philips.PCDV5016 (rebadged LiteOn SOHD-16P9S)” gives me the blink LED behavior
no eject and not recognized by bios and halts the booting for a min or so and all the drives on the same ide is not read

is there is any way to save it and re flash the firmware with Philips or lite on firmwares


#2

[QUOTE=websh;2158234]…and all the drives on the same ide is not read[/QUOTE]

Tried changing the IDE cable for a fresh one? :slight_smile:


#3

Tried changing the IDE cable for a fresh one?

oh u think i’m that stupid :):):slight_smile:


#4

i tried mtkflash dos and got a msg says
port: 170 , master/slave: b0

any comments
of course nothing changed still blinking led


#5

[QUOTE=websh;2158330]oh u think i’m that stupid :):):)[/QUOTE]

Not at all :flower: - I experienced similar symptoms (LED blinking, drive not recognised by BIOS etc) with a Plextor CD-RW I once had. Explored all the software options I could, and finally figured out (by accident) that the IDE cable wasn’t seated snugly enough.

So it’s often the case that the simplest things can be overlooked by us all :wink:


#6

just kidding Arachne but i didn’t ask for help unless i exhaust all logic possibilities

and after many trials with mtkflash and xsf i discoverd that the drive uses an ALI chipset M5721D

is there any tool to dos flash the ali based drives?


#7

Have you tried XSF v212s with the “/L” option?

Note: on my system it hangs the USB keyboard. :confused:


#8

Have you tried XSF v212s with the “/L” option?

Note: on my system it hangs the USB keyboard.

i’ll try it this evening
but when i searched for trhe file found XSF v212s & 212i

is this means IDE & Sata versions ??

and the parameter /L does what exactly ?


#9

tried what u said
i get “no pci 9050 serial chip” msg
and using older ver i get error 27

tried some stuff and now getting 2 msg’s :

“no pci 9050 serial chip”
“port 3> 0170/B0 F/W not found”


#10

The drive must be a mess if it can’t detect the firmware version.

If that drive on port 3 is the correct drive then you would use this command line:
xsf212s 3 W firmware.bin

I just hope the non volatile area (eeprom) has not been lost. :frowning:


#11

The drive must be a mess if it can’t detect the firmware version.

If that drive on port 3 is the correct drive then you would use this command line:
xsf212s 3 W firmware.bin

I just hope the non volatile area (eeprom) has not been lost.

well i already tried this command in the trials and got the same massage
seems it’s totally ruined