Bad-flash-recovered LiteOns

Since there are appearently random reports about mtkflash failing to recover bad-flashed drives sometimes, I'll try to find a system in these reports.

If you ever had a bad-flashed LiteOn drive, then please provide the following information:

- which LiteOn drive
- reason for bad flash (if you know it)
- mainboard w/ chipset
- recovery: (a) without any problem, (b) worked only as secondary single slave (c) other special means necessary, but worked (d) didn't work

Note: A BIOS hang upon drive detection is nothing special and not worth being mentioned as an issue.

If you have tried different PCs to revive a drive, then provide information on all PCs you've tried, if you remember them.


OK, I'll start:

40125S
Mainboard: MSI MS-6163 (iBX440)
reason: stupid me used an obsolete version of mtkflash
recovered without any problem

40125S
Mainboard: MSI K7T266 Pro2 RU (KT266A)
reason: 2 mediatek drives shared one channel => both bad flashed simultaneously
recovery: possible only as secondary single slave

These information were collected from postings below:

40125s
Mainboard: epox 4g4a+ (i845G)
reason: deliberate
recovered successfully as primary slave

165H,
Mainboard: Epox EP-8k5a3+
reason: flashed firmware for burner into dvd-rom
recovered without any problem

Memorex 48MAXX (LTR-48125W)
Reason: bad sector on floppy
Mainboard: Abit KG7 (AMD-761)
Recovery: without any problem.

163D
Mainboard: Gigabyte AMD 751
reason: Official Firmware Crashed in windows Xp Pro
Recovered without any problem

48125W
Mainboard: Gigabyte AMD 751
reason: converted to non-compatible drive
recovery: no problem

40125W
Mainboard: unknown Trigem, i810
reason: failed to write a bank
recovery: no problem

Flashed 40125W -> 48125W
Mainboard: ABIT ST6 (i815)
Reason: 2 drives shared one channel -> bad flash
Board: Gigabyte 6BXC (iBX440)
recovery: only as secondary slave

LTD 163
Mainboard: Epox 8kha
reason: Official Firmware hangs in windows 98 SE
Recovered without any problem


----------------------------------------------------------------------

16102b
Chipset: i810
reason: Windows flasher caused a bad flash
recovery: impossible; had to use another PC

---

Last edited by alexnoe; 27-10-2002 at 23:21.

40125s
epox 4g4a+ (intel 845g)
deliberate - switched power off during flash (dont ask why)
Wont go past hd detction, no way to skip (f4 , esc etc did nothing) disconnected drive, rebooted and set all hd to NONE (instead of auto). Reconnect drive reboot, this time doesnt try to detect, gets to floppy and flash ok. Drive was primary slave.

16102b

unkown....but it died using the Windows Liteon flasher

intel i810 (would not work....switched it over to an unknown 486 ....)

After the switch it worked like a charm...and on any channel ( I used it to flash the recovery and the update I was trying to do in the first place.

I overclocked my 32123s to 40125s using Maiks' format. The cd/rw at its' original configuration worked great. Now at 40125s, when I try to copy an audio cd, it stalls and hangs at 53 % read and indicates that the liteon is idle and the program is not responding. After I oc'd, I ran the nero tool and it indicated that all was OK. It recognized the new f/w (XSU1) and gave all the drive information as I expected. Here is my info.
My OS is XP pro. Motherboard Asus P4S533. 2.4 ghz 533 CPU. 256 DDR pc2700 ram. Liteon 32x12x40 CD/RW f/w XS0K.
I updated the IDE from ASUS's site and forced ASPI driver.
My cd/rw is the secondary master and my CD rom is the secondary slave. Both are connected on the same cable. Can anyone help?

@Papabear:
This thread is intended only to collect information about bad flashed drives and their recovery, in order to find out if there are special chipsets, special boards or the such that are likely to fail when attempting a bad flash recovery.
It is not really intended for techincal support...

Hi,

This wasn't deliberate, but still useful for this post.

Epox EP-8k5a3+ AMD XP 2000+
LiteOn 165H, LiteOn 48125W

Stupid me created 2 batch files to run from Dos:

1. mtkRead.bat to read-out/save the existing f/w

2. mtkFlash.bat to flash device 4 (48125w)

Problem was I changed my 48125w from device 4 to 3, but forgot to alter the mtkFlash.bat, started mtkFlash.bat and finished up flashing my LiteOn 165H (brand-new that day) with the 48125w f/w.

Thought 165H was history, got the 165H f/w on disk, ran mtkFlash.bat again, flash finished, RE-Booted and presto, one working 165H.

Cheerz

Don't know if this will help. Was changing my Memorex 48MAXX to a LTR-48125W this morning so I could use the new VS08 firmware and experienced the following. . .

Drive: Memorex 48MAXX (LTR-48125W)
Reason for bad flash: Error reading bad sector on floppy disk
Mainboard: Abit KG7 (AMD-761)
Recovery: (a) without any problem. (once I got everything on a disk that didn't croak)

Note: Drive was slave on the secondary IDE channel. LiteOn DVD-ROM LTD-163 was the master on the secondary IDE channel, but I physically removed the IDE cable before the flash to avoid a possible problem. Then that sneaky floppy disk tried to hose me.

Alex you should make this a sticky thread mate !! its very usefull

im still trying to fix my 163D ill edit my post if i fix it or not ! im still panacing

Wooohooooo i recoved it hehe

====================================

LiteON DVDRom163 D
Mainboard: Gigabyte AMD 751
reason: Useless Official Firmware Crashed in windows Xp Pro
Recovered without a hitch with mtkflash.......

---

Last edited by ViRuS2k; 16-10-2002 at 06:00.

Well, we have so many stickies already...but OK.

I hope I get more reports about difficult recoveries, because that are the ones I want to find a system for...

Well overclocking recoverys :P

============================

48125W Vs08 into 52246S
Mainboard: Gigabyte AMD 751
reason: Didnt work flashed from dos flash went perfect but it wasnt reconized in bios nor windows the name changed to : TE52R-6S
===============
recovery : recovered with mtkflash from dos with vso8 bin

==========================================

48125W Vs08 into 48246S
Mainboard: Gigabyte AMD 751
reason: Didnt work flashed from dos flash went perfect but it wasnt reconized in bios nor windows the the name wasnt even viewable also the led stayed green ............................
===============
recovery : recovered with mtkflash from dos with vso8 bin


===========================================

163D into a 165H :/
Mainboard: Gigabyte AMD 751
reason: Flashed perfectly problem was on reboot it wasnt reconized in the bios also the led didnt blink on reboot ! AKA dead drive !!!
Recovered without any problem with mtkflash

====================================


ohh well hehe

LiteON LTR-40125W

I use ST (screenthief) to capture the flash process,and it cause like the picture


Mainboard: I don't know ,it's a sucky Emachiens T1090 and mainboard is maded by Trigem and use Intel 810

- recovery: Perfect it work as good as it should be

mtkflash

LTD 163 (master on secondary IDE)
Mainboard: Epox 8kha
reason: Official Firmware hangs in windows 98 SE
Recovered without any problem

Flashed 40125W -> 48125W
Mainboard: ABIT ST6 (i815)
Primary Master: BTC BDV212B (DVD w/ Mediatek chipset)
Primary Slave:40125W

Reason: Set latest MTKFlash to flash primary slave(40125W). However, MTKFlash flashed my DVD drive. (known issue with MTKFlash and two mediatek chipset devices on same channel).

Recover: Was able to reflash the 40125W to 48125W. However, had to move DVD drive to secondary slave on a Gigabyte 6BXC(iBX440) to recover the DVD drive. (Boot from A-drive, then plugged in the IDE cable after I got to the DOS prompt).

LITEON 40X12X48 ==>48x12x48
SOLTEK SL-75DRV5
VIA APOLLO KT333

All seemed well until reboot and light stayed on ( crapped my pants
Burner was not detected in BIOS
Used Mtkflash v148 Vs08.bin ( )
Burner is on Secondary Master

Flashed OK 10 times and is detected as a 48x12x48 LTR-48125W

I haven't a clue why the first one failed, it worked the second time.

Thanks CD Freaks!!!!!!!!

- Lite-on 40125s (Pacific Digital)
- Intel 850 (original P4 one, from Dell 8100)

- Partial update firmware.
- During flashing it freezes at BANK 3 (50%). I have tried with 3 different versions of the firmware. When I start up it recognizes the drive, but I no lights come on and XP keeps asking what I want to do with this blank cd (there is non in the drive).

I know this is mainly a solutions board, but if someone can help me then I will write the correct recovery. Thanks.

Lite-on 165H (Pacific Digital)
Epox 8KHA+ Latest BIOS VIA chipset (KT266+8233)
After attempted firmware update to a RPC 1 firmware the drive no longer functioned and was not recognisable in BIOS. Unknown why it was a bad flash! (think it was a bad bin download) It claimed it had worked when i did it.
Had to restart with DOS bootdisk without the drive plugged in to get past BIOS then plug it in and use MTK Flash to reflash it with a new copy of the firmware.

/me again (it took me half a hour to recover my drive after a dozens of flash

40125W
Mainboard: unknown Trigem, i810





Reason : Don't listen to expert (I flash 6s0a to my 40125W) -->

bad flash , I can't even boot into Windows . I must disconnect the drive and enter BIOS to set Flobby boot first (usually CD-ROM bot first)

Boot by flobby disc ,and bad flash again
reason : I use wrong command
mtkflash 3 w /b /m vs08.bin (dunno why I put /m

try again,and bad flash again
reason : after flash though succesful or not the LED in the drive will flash (green) a couple times.We must wait until the green-LED flashing is done to process any other flash,but I use arrow key to repeat the flash process --> Bad flash again


Finally,I type correct command and wait until the green LED flashing is done to flash.Now Recovered without any problem





sorry for my crappy English

1st you need to make a boot disk so you can boot into dos or you need to use the cmd command in the run dialog on winxp.. place mtkflash on the same boot disk and FIRST back up your current working firmware especially if it is for a memorex or other rebadged drive

you need to know what port your drive is on mine is on the secondary ide controller as the master this makes it port # 3 it goes like this assuming no partitions other than a single one on your HDD's 1= c drive, 2 = D drive and it is slaved off drive one
on secondary ide port you would have port 3 your E drive and port 4 your F drive as you can see you need to know that if for instance your cdrw was the slave on the primary ide port it would be port 2 in that case and so on

to back up the orig firmware at the a: prompt with the diskette in the drive with mtkflash on it type
mtkflash 3 R /B /M 6ws3.bin where 6ws3 is the name of the original memorex firmware and 3 is the port MY drive is on (use the correct one for your config.)(use any 8 char. name you want but it is best to preserve the orig name) now be patient and WAIT while it does its thing it can take a while as it rolls through 1% to 100% several times !

at the end do a dir on the floppy to insure the backed up file is there it will be listed in this example as 6ws3.bin

don't bother to reboot ignore the message !!

Now you should have also previously copied the 6so8.bin (or 6s0a in the case of the latest revison) to the floppy

type , again at the A; prompt

mtkflash 3 W /B 6s08.bin and hit enter

it will write to the banks of the chip each in turn and give you the reboot message again this time go ahead and remove the floppy and reboot and you should be looking at a lite-on drive on your system now .. I suggest testing it setting it up etc with your nero or whatever SW you use then downnload the 6s0a executable from liteonit.com and use the windows flasher to update it like you would any other lite-on drive. (if you used any FW older than 6s0a.bin)

I'm not sure what drive you have so I will cross post this PM on the boards in case you need to request the original bin file for your drive form someone there so you can use this same process to reflash it back to oem I have the 6ws3.bin Memorex 52maxx if that is the one you need and I will email it to you if you need it

---

Last edited by lagger; 18-01-2003 at 00:12.

Lite-on LTR-16102B
Power failure during flash
Asus A7M266 MB, chip set AMD-761
Burner doesn't work at all now. The green light stay on all the time. I tried to reflash and I get this message:

Error: Can't found LTR-16102B firmware: OSO1-OS9Z! This flash utility only supports LTR-16102B firmware: OS01-OS9Z.
Detected drives: HA#0-ID#0; Lite-on LTR-16102B 015B

I am running Win-XP.
I removed the burner and installed it in a machine running Win-98, but it didn't help. I tried it as a secondary master and a primary slave but it still didn't work or reflash. I even tried Flashfix and I got this message: "Couldn't find bytes to patch".
Under properties the firmware revision used to say OSoF, now it says O15B. Is there any chance of recovering the CD-burner?
Any help would be greatly appreciated

you will need to locate the bin file for the original FW and reflash it in dos with mtkflash.. there are several references to firmware files and locations here at cdfreaks . so doa search with the search function above

OK I created a bootable disk to boot into Dos and found the origional firmware (OS0b.ace). I read the instructions and from dos I used mtkflash and flashed the burner. This is what the screen said:
Flash Type : SST(SST39SF020)

Updating.....Bank0 OK!
Updating.....Bank1 OK!
Updating.....Bank2 OK!
Updating.....Bank3 OK!
UPdating.....Finished!(6AD9)

>>> Please REBOOT your PC !

So I rebooted and now the CMOS setup and the computer does not recognize the Cd burner at all. The green light is on all the time. I tried flashing it several times, but it is still dead.

Thanks for the help. I finally fixed the problem. There is a bin file, location:
/ http://www-user.tu-chemnitz.de/~noe/LiteOn/Firmwares
that restored my CD-burner to its origional firmware. Every thing works great now. Once again thanks.

Hi !

You should have unziped the file ( .ace -> . bin ) before the flashing procedure ?

The record is supposed to be like that :

updating.....bank 0 OK !
updating.....bank 1 OK !
updating.....bank 2 OK !
updating.....bank 3 OK !
updating.....bank 4 OK !
updating.....bank 5 OK !
updating.....bank 6 OK !
updating.......finished ( EA8D)
*** Please REBOOT your PC !

Well I have just had the same fun as above.

Flashed several times with both my orignal backup and the 48x firmware and both left me with green light on and no drive.

I had been using mktflash 1.62 for flashing until I went and got the older 1.55.

I first flashed back to the original and it worked. I then flashed to the VS0B and again it worked.

So just in case you think that using the latest version of mktflash is good... try using 1.55 instead.