were still trying try in this order..click phat key turn switch off, probe mxp01, turn switch on click ok key successful turn switch off, unprobe, turn switch on click ok
As i said before mate i cannot do any of that as JF doesnt detect the drive unless its in vendor intro mode and it wont let me do the probe process
right im running out of ideas now try the tray half open trick and press L083 INFO ...hard when you havent got the drive in front of you..
Try doing this to get the key evo. Probe it at the mx Point and instead of pressing the button on the probe flick your ck3 switch on and off it will say 0x52 but will give u an error if so do it again but this time with pressing the button down Ive had with some lites on it kept getting 0x51 and this seemed to solve the issue. EDIT: Try Going into The JF Irc and ask there
yeah also give this a shot but try my suggestion also im sure ive had this problem with an 8 series before and ive just rembered tray half open and pressing l083info got me the key .
Ye that method I found out above is what sorted out two lite ons i had I know one of them was 8 series not sure on the other 1
Right Here's the lowdown on this 8 series drive READ THIS CAREFULLY AS IT STATES EXACTLY WHAT IS HAPPENING (And believe me when i say i have flashed plenty of drives to know what im talking about people) Step 1) Connect the drive up with USBPro and CK3 adapters Step 2) Opened JF and the drive is powered on BUT DOES NOT SHOW UP IN DRIVE PROPERTIES Step 3) Went to MTK3 Tab and put drive in vendor mode via Intro/Device ID Step 4) Tried Reading drive key and read the key and FW and dumped it but when i save it it said Lite-On Dump file saved to Lite-OFW.bin Loading firmware from buffer Parse Failed ! Loading MTK_Flash source file Step 5) I Cannot LO83 or probe the drive with Probe 3 due to drive not showing up in drive properties as IT WILL NOT LET ME Step 6) I cannot even make a dummy of the original key as i cannot get the key from the firmware file due to above error nor the relevant files needed to make the file itself. Now im stumped on this drive as i clearly cannot figure out what the hell is up with it. If anyone can find a solution to this it would be greatly helped and would be appreciated very muchly.
Problem solved on this drive The drive is Completely Blank so this thread can be closed ADMINS. Thanks for your help everyone