lock up

[pluto_00]

USING JF lite on would not go into 72 status always failed

I closed the drive powerd it down ... now it don't eject or anything ...

I tryed making a bootable USB it boots from it but i only get a blinking underscore and firmtool does not run ...


So what goes wrong ?
I use IPREP 008.8 to make it

I really don't get it ... tryed a floppy also , no succes.

If I try a older Iprep i get a fault from .NET framework ...

any ideas on this one ?

[sadalius]

Did you get your custom firmware made? If so, your going to have to use CoFree's recover a lite on after freezing guide to finish it off. Check it out here: viewtopic.php?f=195&t=3226" onclick="window.open(this.href);return false;

[pluto_00]

yeah man i did

but that is the problem i can't get my USB to boot
so no dos no recover

do i need an older iprep to make it ?

What files exactly must be on that boot USB ?

it just don't run the things that are on it so there must be going something wrong


this is whats on my USB to boot from

DosFlash.exe
dosflash.typ
firmtool.exe
ix15Benq.bin
ix15-liteon.bin
ix15-sam.bin
l-o-eras.exe
Lite_CFW.bin

[dalecheesy]

The blinking cursor normally indicates that your pc can't boot from FAT32 (which the newer iprep formats the usb in) you can use hp format tool to create a Fat16 bootable usb then just copy the iprep files over, if you are using the iprep program to build the stick remove the make bootable tick as it should be formatted in Fat16 through the hptool already.

you can also boot from an msdos startup floppy and when you get to the A:\ prompt change the destination to your usb (type B:\ and if it corresponds to your usb it should change the A:\ to B:\) when it changes to the B:\ prompt type Dir which should show you the contents of your usb drive.

Also enable usb legacy devices in your bios and check which device is set as the first boot.

Sounds much more complicated than it really is.

[pluto_00]

Lol I found some other trick ...

I looked into Xbins and downloaded the lite-on-erase
That thing contains a lot to run from the command prompt in windows

So i did almost the same as in dos instead of using l-o-eras it was lite-on-erase(space) port numer

2 times and got a 72 status no FF in front of it

I redownloaded the older JF and copyed the key too the IX 1.5 tryed the erase again and then just went on writing ...

And it turned out ok ! :p

drive was not even listed in JF or anything ...

It just popt back to life :p

[dalecheesy]

Glad your sorted pluto.

[sadalius]

Now thats plum nifty man. I wouldn't of thought of that approach, but glad to know there is more than a couple ways to skin the lite-on cat.

[pluto_00]

Yeah i amased myself with that lol

Thnx for the quick reply's

the info about that being FAT32 and stuff i did not know about that from the newer Iprep.

We will heal the world , euh, i mean the lite-on's :p