jungle flasher bricked my drive but i was able to recover to a good flash.. check out my log maybe it can help someone.


After trying to erase a Lite-On drive with Junky Flasher before you write the new firmware. The program or
power cycle process decided to corrupt and brick my drive. Unbelievably in the end I was able to force the
firmware flash and fix/unbrick the drive. Jungle flasher is unstable and not perfected. I don't recommend it
to anyone until all the bugs are fiqured out.

It can and may make a Banana out of your Lite-On drive.

After many failed attempts and the program becoming non-responsive often. Here is the proof.


~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~JungleFlasher 0.0.26 BetaSession Started Mon Jan 19 13:14:29 2009

Found 6 I/O Ports.

Found 2 Com Ports.

Found 3 windows drives.

Found 1 CD/DVD drives. (This was not the Lite-On drive but one in the computer so the Lite-On drive is completely bricked)

Sending Vendor Intro to port 0xCD40 (This is the port the Lite-On drive was on but obviously not recognized as seen below)

Invalid Status

Re-sending Vendor Intro:

Manufacturer ID: 0x0

Device ID: 0x0

Flash Name: Unknown type

Flash Size: n/a (As you can see the drive is bricked, there is no communication or information from it at all)

Loading DVDkey source file Inquiry string

Found Identify string

FoundDVD key

Found @ 0xA030 key is (000000000000000000000000000000000000) (this was obtained before Jungle

flasher Banana'd the lite-on drive, Key extraction was straight forward)

Firmware is a Lite-On or Benq Dummy OSIG: PLDS DG-16D2S 7485

Firmware type is: DVDKey32 extract

Loading target file C:\Documents and Settings\ix15-liteon.binTarget

File MD5 hash is: d8aaa30797c7680109b395bc3a380d5f

Genuine Lite-On iXtreme 1.5 FinalInquiry area found

Current DVD key is 000000000000000000000000000000000000

Firmware is a Lite-On encrypted iXtreme OSIG: PLDS DG-16D2S 7485

Firmware type is: iXtreme v1.5 12XDVD Key copied to target

Inquiry string copied from Source to Target

Identify string copied from Source to Target

Serial strings copied from Source to Target

Target f/w saved as: C:\Documents and Settings\Desktop\Lite_CFW.bin

Getting Status from port 0xCD40SPi flash found with Status 0x72 (How is this possible with the above shown device)

Sending Chip Erase to Port 0xCD40

Writing target buffer to flash
Writing Bank 0: ................
Writing Bank 1: ...............
Writing Bank 2: ................
Writing Bank 3: ................

Flash Verification Test !
Reading Bank 0: ................
Reading Bank 1: ................
Reading Bank 2: ................
Reading Bank 3: ................

Write verified OK !

(So as seen with your own eyes. Jungle flasher bricks the drive and then after not being able to interface said bricked
drive it simply gets a 0x72 status with flash and erases it and writes new firmware. I never even clicked the erase lite-on
button at all. All I did was click write once the Lite_CFW.bin was loaded and it force wrote to that invalid status port.)

What sata chipset were you using?

I used this just now for a lite-on and worked without a hitch seems more like a user error to me