Print

[Martinchris23]

Disable the VIA driver in Device Manager and use Dosflash32 1.7 beta to read the drive.

Then use FirmTool 1.3 to import the data from the dummy.bin into the ixtreme firmware.

Finally use DOSFlash32 to erase and write the new firmware to the drive.

[Modify_inc]

QUOTE(Martinchris23 @ Jan 3 2009, 08:24 PM)

Disable the VIA driver in Device Manager and use Dosflash32 1.7 beta to read the drive.

Then use FirmTool 1.3 to import the data from the dummy.bin into the ixtreme firmware.

Finally use DOSFlash32 to erase and write the new firmware to the drive.

using DOSFlash instructions, I was finally able to get the correct keys and I believ OI knowwhat step I was missing before.  I have to power on the driver, hit eject, then power off the drive, then push the drive half way in, then power it back on.  I was poweringt he drive on, ejecting the tray, than without power it off, pushing t he tray half way back in. So I was leaving the power on the entire process, which I didn't do when Ifollowed the direction usingt he DosFlash instructions.  

So basically the dummy file is my original bin with all the correct data?  I can use Firmtool 1.3 and import the dummy.bin to the hack.bin ixtreme firmware, then erase and flash?

You told me to disable the VIA driver, yet as I thought when I did so, the DOSFlash didn't see my drive anymore.  I had to keep it enabled, and it still worked, since I was now using the correct method to get my drive ready to read.

I'm little nervous about erasing and writing, I hope I can't mess anything up.  Is there anyway to verify my dummy file is correct before I try to erase and flash?

[Martinchris23]

Sorry, I was under the impression you'd installed the PortIO driver in place of the VIA driver. If you've gotten a good DVD key from DOSFlash and it's created the dummy.bin file, you're safe to go ahead and erase then write the new firmware back to it.

[Modify_inc]

ok quick question befoer I jump to far into this.  I just used JungleFlasher to make my Lite_CFC.bin file, so I have a valid hacked bin ready to go.  Should I use the JungleFlasher to erase and flash or would the Flashdos32 be better for my setup using a VIA chipset?  I noticed in the begining of the JungleFlasher, it says to unisnatll all of my VIA drivers, which seems like a lot of work.  The DosFlasher doesn't say anything about removing my VIA drivers.  Is DosFlasher better for use with the VIA Chipset?

Thanks again guys, without your help today, I would still be going in circles.

I just tried the Dosflash32, and selected Erase, then clicke Erase Liteon on the bottom and it instantly tells me 'No known flash chips on this port'.  I know I'm using the correct port, it the same one I used to read with earlier.  What could I be doing wrong, is it that hard to erase?

UPDATE: I goofed, I did a standard Erase, not the Liteon Erase. Let me try that.  I noticed there is not a Liteon Write.  I don't guess I can using the standard write can I?  IF not, then what am I suppose to do?

[Modify_inc]

I did the Liteon Erase, it came back successful.  The instructions say to power off the drive and then back on.  I did, and my computer froze up.  I had to reboot, I hope it safe to try to write to now.  I will give it a try now.

Update: When I power the drive on again, my computer froze up again.  I can't do anything to it if it keeps freezing on me.  What could be going casuing this?  Where do I go from here? When I turn the power off again on the Xtractor, after about 20 seconds I can use my computer again.

[woody21_1]

its freezing because the computer is looking for the drive on sata but can see somethings connected and is continually polling the sata ports to see what type of flash chip is present.

i have issues in windows and found it much easier to use dos and the newest version of dosflash in dos, dosflah 32 wont see my sata  and jungleflasher locks the computer solid.

i couldnt even erase the drive fully in windows and have tried many times, my hdds are on the onboard via8237 and screwing with the drivers to install portio for the via 6421 takes out all the via drivers and windows refuses to boot until i give it its driver files back  

i read the key in windows fine, create my firmware then boot dos and erase and flash from there, erasing can take several attempts sometimes to get the correct status but works everytime.

[Modify_inc]

Thanks guy, it working great and plays backups now.

I rebooted, opend JungleFlasher, went to MTK Flash 32, my flash chip properties were already correct. Clicked write, and it wrote much faster than other drives I noticed, verified successfully.

Thanks again guys for your help.  The only bad thing out of this whole ordeal is that fact I accidently wrote the flash earlier using DosFlash32 to my standard DVD drive.  I noticed when I clicked write earlier own, that the drive properties was describing my dvd drive in my computer.  I figured, it wasn't really flashing my drive, since it probally has a differnt flash type and all.  Sure enough when I rebooted my computer it hung, and I notcied my eject button didn't work on my PC's computer drive.  I looked in the BIOS, and it wasn't seeing  my drive.  I unplugged the drive and the computer booted with no problems.  So the real problem about that drive is, it was a Samsung D162C flashed to read 360 games, yes I was pissed.

Anyone know how to recover a bad flash to a Samsung D162C DVD Drive???

[Martinchris23]

Unplug the power connector from it and leave the IDE cable in place. Boot into Windows and plug the power cable back in - if the system doesn't freeze, check DosFlash32 and see if you can access the drive via its port address. If so, reflash with the Kreon 1.00 firmware.

[Modify_inc]

QUOTE(Martinchris23 @ Jan 3 2009, 11:48 PM)

Unplug the power connector from it and leave the IDE cable in place. Boot into Windows and plug the power cable back in - if the system doesn't freeze, check DosFlash32 and see if you can access the drive via its port address. If so, reflash with the Kreon 1.00 firmware.

Thanks, I will give it a shot.