CDRLabs.com

I deleted my firmware completely when I tried to flash my Liteon JLMS LTD-166s drive. Since that the BIOS doesnt find the drive anymore, so I cant flash it anymore. Does anyone know a possibility to flash my drive?

mtkflash in DOS or MTK WinFlash in Direct IDE Port Mode

mtkflash in DOS.

Yeah, either will fix it.

What should fix it?

I tried the link in your sig, but I did only find the ltrflash-program there. I tried the versions 1.11 and 1.11b, but in both the same happened:

When I started the program, I got this error message:

Access violation in address 00403408 in modul 'LTNFLASH.EXE'. Read of address FFFFFFFDC.

I couldnt select any drives in the program, althought I still have a working Acer CD-burner. I know, that the program can only flash Liteon drives, but I think, that it maybe would also recognize other drives and say, that they arent Liteon drives, when you try to flash them.

So I didnt select any drive, and pressed go. It sayed something like "clearing Unit Attention", but before the status bar showed anything, this error appeared on a Bluescreen:

"A fatal exception OE has occurred at 0028:C02A27A8 in VXD VWIN32(5) + 000012D0. The current application will be terminated"

Note, that even all addressses were always the same, even after a reboot.

No, LtnFlash cannot currently flash dead drives, but mtkflash in DOS and MTK WinFlash Windows (in Direct IDE Port Mode) can flash dead drives. Digi's Site has binary firmwares to use with these programs.

The problem is that I cannot use Mtk Winflash in direct IDE mode, because the Flash Drive button is grayed out. This is independent from what IDE port I select, althought I still have a working CD-RW drive on the primary slave. I also tried the ATAPI mode to see, if it finds the working drive there, but it didnt find anything.

How can I make mtkflash in DOS to flash my dead drive?

Hey.. I'm TechHEad from over at the [H], sorry the direct port IDE thing didn't work out.

Ok: Put mtkflash.exe and the binary firmware in the same directory on your HDD.
2)Boot to DOS

3)use this syntax: mtkflash w /b 1/2/3/4 filename.bin

Put mtkflash w /b 1 filename.bin if the drive is on your Primary Master. Put 2 if on Prim Slave, 3 if on Sec Master, and 4 if on Sec Slave.

Should work.. make sure that the drive has no disc inside.

I tried this using a dr-dos boot disk (because it sayed, that I should use it on the webpage, where I downloaded mtkflash). It didnt do anything.

Ok, I have flashed it now in DOS w/ firmware DS14 in the normale F8 DOS-mode. The flash worked, but my drive is still not recognized by the BIOS.

I dont have the original firmware (DS08) anymore. Can someone please extract it from his LTD-166s drive and mail it too me (I will send a pm w/ my e-mail adress).

Using the older version wont work out any better than a newer one. I don't know what to suggest beyond this.

http://digi.rpc1.org/binaries.htm

You didnt understand: the DS14 firmware doesnt work at all on my drive. It isbt even recognized by the BIOS w/ this firmware. I cannot even open the drive, and the LED also doesnt work (I dont have a disk in the drive, but the LED should be blinking at bootup).

I also have another problem: mtkflash doesnt work anymore. It only says "MTKFLASH by Joseph LIn, MTK 1998 (Ver 1.62)". After that nothing happens. the only thing, that still works is to enter just mtkflash, which shows the parameters. It doesnt have something to do w/ the drive, because it also happens, when I enter "mtkflash 2 c", which should only chek the still working CD-RW drive. I also tried to redownload it and to use version 1.55, but none of this helped. I also tried to use F8 DOS-mode, a bootdisk and the COMMAND-promt in Windows.

Do you know a different flash-program, that I could use instead of mtkflash? It should support direct IDE mode, because the BIOS still doesnt find the drive.

Maybe this thread has some useful information.

No, this there was no usefull information in this thread. I think, the only things I need are the DS08 firmware and a different flash program.

My DVD-drive was working before I tried to flash it and deleted the firmware.

I tried the older version of mtkwinflah (1.5.3.5 instead of 1.3.5.6), and sometimes it hangs when it shows "Initialize Device", and sometimes it says

Press Browse Load Bin/Hex & Flash
ERR: fail to identify the flash type!
Please wait a moment...
Complete! Please restart your computer.

and after that the BIOS still doesnt recognize the drive (I used firmware ds0b).

Edit:

I forgot to mention, that the HHD-LED is always on since I reflas´hed the drive w/ ds14. So the mobo does know, that there is something on that channel, but it doesnt know what it is, so it asumes, that it is a HDD.
and after that the BIOS still doesnt recognize the drive (I used firmware ds0b).

dhc014 sended me a newer version of mtkflash (1.8), but it also didnt work. When I tried to flash, the program said "ERR: Fail to Initial IDE port, please reboot PC". It cannot be a IDE-problem, because I also tried it using the other other channel. After that, I tried to check the other drive by typing "mtkflash 2 c", but this time it hang like in the previous versions.

The only strange thing is, that after the reboot the floppy-drive also stoped working and made a strange sound and vibrated (got Floppy Disk error in BIOS, had to chang halt on: all errors, but disk).

This may be a VERY stupid question, but are you sure that your drive is a 166S and not a 165H?
Make sure!

bhairavp wrote:This may be a VERY stupid question, but are you sure that your drive is a 166S and not a 165H?
Make sure!

It says 166s on the top of the drive, and it also sayed it in Windows when the drive still worked.

I tried to use wflash, a utilitly for LiteOn drives. I used the wflash filename.bin /ss /all command. It sayed this:


LiteOnIT CDRW flash Utility For DOS Ver 0.1
Try to recover the drive with ATAPISoftReset
Try to recover the drive with ATAPISoftReset
Try to recover the drive with ATAPISoftReset
Inquiry + ATAPISoftReset Fail

Program Terminated with error code: 16: BSY_DRG_HI


After this I tried to flash the secondary master w/ wflash filename.bin /sm /all. I dont have a drive on the secondary master, so I wanted to see, if the error would be the same, and the program reported exact the same.

Edit: mtkflash also reported the same error when I tried to flash the secondary slave as when I trie to flash the secondary master.

There is nothing wrong with MtkFlash or the DS14 firmware. The original DS0B (not DS08) firmware is available at the site already given you by dhc014 at digi's site, but won't make any difference.

I would try changing the IDE cable, making sure that the IDE cable and power cables are properly seated and start over again.

I have already tried the other IDE-cable, so that cant be the problem.

My DVD-ROM drive originally had the DS08 f/w.

MrBurns wrote:I have already tried the other IDE-cable, so that cant be the problem.

If you physically changed the cable and checked the connections including the power cable as I suggested, disregard the following:

If by the quoted statement above you mean you accessed the other IDE cable to which your DVD-ROM was not attached with the flashing software, then this was a useless and pointless exercise. What result did you expect with a procedure which is not to be used except with Liteon drives? The very fact that you got the same error accessing a connection with no drive attached as the connection with the drive attached might indicate that there could be a physical fault in the DVD-ROM IDE cable.

If you haven't physically replaced the DVD-ROM IDE cable with a known good or new cable, it can be the problem.

Inertia wrote:[If you haven't physically replaced the DVD-ROM IDE cable with a known good or new cable, it can be the problem.

I have tried the primary cable. I know, that it works, because I have my HDD connected at the other connctor from this, and normally I use the connector I tested for the CD-RW drive. Of course when I tried to flash the drive on this connection, I used mtkflash 2 w /b filenam.bin, because the drive was on the primary slave instead of the secondary slave.