Robin Hoods Playground

Hello

I have a lite-on 83850c fitted with a LT-switch 1.5 xecuter ck3 pro connection kit

when i get to write mode i get this massage

I have loaded lite-on OFW in source and LT+ in target

JF Log :

JungleFlasher 0.1.76 Beta (166)

Session Started Tue Nov 30 10:37:29 2010



This is a Wow 64 process running on 4 x 64 bit CPUs

portio64.sys Driver Installed

portio64.sys Driver Started, thanks Schtrom !

Found 8 I/O Ports.

Found 1 Com Ports.

Found 2 windows drives C: E:

Found 1 CD/DVD drives E:



Loading firmware file C:\Users\stresshead\Desktop\New Folder (2)\OFW\Lite-OFW.bin

MD5 hash: 0380b2333985d19c56b6bf62e94df5d2

Drive key @ n/a KEY REMOVED

Firmware Osig: [PLDS DG-16D2S 8385]

Firmware is: Stock

Auto-Loading firmware file C:\Users\stresshead\Desktop\firmware\LTPlus-838.bin

MD5 hash: f5ec9fa4b16d624ca71074ac6e6641d9

Genuine LT-Plus

Drive key @ n/a 77777777777777777777777777777777

Firmware Osig: [PLDS DG-16D2S 8385]

Firmware is: LT-Plus

Spoofing Target

DVD Key copied to target

Inquiry string copied to Target

Identify string copied to Target

Serial data copied from Source to Target

Calibration data copied from Source to Target





Sending Lite-On-Erase request to port 0x1CC0

..............

Drive returned Status 0x80

......

Serial flash found with Status 0x72

Manufacturer ID: 0xC2

Device ID: 0x11

Flash Name: MXIC(MX25L2005)

Flash Size: 262144 bytes



Getting Status from port 0x1CC0

Invalid Status 0x80

Sending Vendor Outro to port 0x1CC0

Please see screen Shot below

http://img15.imageshack.us/img15/7909/invalide.jpg


if you need any more information just ask

many thanks

Set the lt switch mode to normal turn the drive on (should be green light on switch) your drive should bee seen in mtk, hit intro, wait for the yes or no prompt, turn off drive, switch the clip to write, turn back on, and hit yes in jungle flasher.

You should get a successful 72 status, now switch back to normal, light will go green, now hit read.

From there proceed with the flash, lite-on erase, power off, then on, then write.

(If after the erase it fail's just try the intro again, but cut the drive off then on you should find the drive again)

hello thanks butr still no joy

thinks its JF does like my drive would IPrep do the same job

wont work in JF still getting 0x80 error

My solution...

Solder off the LT switch and repair the 3 trace cuts manually with a bit of resistor wire and solder, provided that you have a valid dump of you're drive and you're 100 % sure you have the correct key. Then follow CoFrees video bellow from 11.34 .It's exactly the same procedure to flash IN for you're drive.



NOTE: Were CoFree loads in the LT 1.1 for the 9 series drive as the target firmware, don't do this, for you load in the new LT + 83850c v1 or v2 as target deppending on what you're drive is

Sop what my saying is that its my LT switch cause the problem that why im get 0x80 Error when i click the write button

Doctor360 wrote:Sop what my saying is that its my LT switch cause the problem that why im get 0x80 Error when i click the write button

Do you ever get a 72 status? You can try cutting the drive off, pressing write, cutting it on, you should get a 72 status that way.

HaGGardSmurf wrote:

Doctor360 wrote:Sop what my saying is that its my LT switch cause the problem that why im get 0x80 Error when i click the write button

Do you ever get a 72 status? You can try cutting the drive off, pressing write, cutting it on, you should get a 72 status that way.

Yeah Get the 72 Status quite a few time and all the right prop in the right hand side after the power cycle

but as soon as i press the write button its say Getting status from port 0x1CC0 then says Invalid Status 0x80 its like some how it lost my drive in the process of getting the 72 status and then to writing drive its loses the drive

Have you done the erase before the write? Or gone straight from read to write?

Yes i did the Erase before the write cause i already have a good copy of the Read dump

still get the same 0x80 error

Do you think it could be a bad VIA port