LITEON 74850 HELP!! Before I Smash My Drive :/

[B4DB01]

First Of All Sorry Im Sure This Topic Has Been Up Before BUt I Cant Seem To Find The Answer.. So Here Is The Scenario: Been Flashing Drives For Some Time, Using Probe 3 To Extract The Keys.. With Success


Recently I Was Given A Liteon Drive 74850c, And It KEEPS Saying Phatkey Failed.. I Managed To Extract It Once But Gave Me - 777777777.. < Which Is Surely Not They Key..:facepalm::facepalm::facepalm::facepalm::facepalm:

Now Im Stuck, I Have CK3 Lite, Probe 3.. Latest JF..
It Just WONT Extract They Key.. Someone Please Help Me? As You Have In Previous Times
:smile:

 

[garageinc]

do you have the latest jungle flasher. i believe the key location changed when liteons were updated to 025 firmware andold versions of jungle flasher may still look in the old place

 

[B4DB01]

Yes, I Have The LATEST JF, I Flashed My Own Drive To LT+ 2.0 Few Days Ago :/

 

[JessJess]

Has it been spoofed before? 77777777777 is what the some of 0800 firmware uses as default as they key.

And who broke your keyboard? Don't need a capital letter before every word.....

 

[RED IMPACT]

Sounds like a ripping drive! Have you got the console, has it been messed with, know the history of it?

if you got it from ebay sounds like a scam

 

[B4DB01]

Nah, Im Used To The Capitals, And They Had The Console For Ages, Just Wanted It Flashed, Been Working Perfectly..

 

[xbox360 hacker]

Well i think that if you could post your jungleflasher logs we might be able to help you more. remember the more info you provide the bigger the picture we can see

 

[bakley2578]

are you powering on with tray halfway open? before probing allot of times that works.

 

[DaveidWeba]

Nah, Im Used To The Capitals, And They Had The Console For Ages, Just Wanted It Flashed, Been Working Perfectly..

Man, I love it when I find people like you on the internet, because you were exactly like me when I was younger.

For Some Odd Reason, I Would ALWAYS Type Out My Sentences Like This. It Was Like, Second Nature To Me. I Think It Started Back In Red Alert 2 Days.
Anywho, I Thought I Was Alone In This Practice, But So Far I've Seen More Than 10+ Times In The Past Few Years Of Others Typing Like This.
I Had To Stop Because, It Was Kinda Hard For Others To Read What I Typed. But I'm REALLY Interested To Find Out Why On Earth Do People Even Start Typing Like This In The First Place?
It's Sure To Be A Profound Answer. Maybe We'll Never Know The True Reason, But I'd Like Hear A Hypothesis :smile:

Anywho, just wanted to leave a little shout out while I was passing through the forums. I won't take up any more time of yours than I already have, and good luck on getting your issue fixed, these are great guys and already they've helped me immensely

Btw, I found this Wikipedia which is quite interesting, pretty much suggests we were destined to be programmers :tongue:
http://en.wikipedia.org/wiki/CamelCase

 

[dragontm]

as stated above please put your JF log up here

 

[B4DB01]

Thanks For All The Responses So Far.. And Here Is The Log:.....


~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
JungleFlasher 0.1.89 Beta (284)
Session Started Wed Oct 19 14:16:05 2011
This is a 32 bit process running on 2 x 32 bit CPUs
portio32.sys Driver Installed
portio32.sys Driver Started, thanks Schtrom !
Found 6 I/O Ports.
Found 1 Com Ports.
Found 2 windows drives A: C:
Found 0 CD/DVD drives
Drive is Lite-On..
Sending Vendor Intro to port 0xEC00
Status 0x51
Re-sending Vendor Intro:
.............
Serial flash found with Status 0x52
Extracted drive key failed Verification !

PhatKey extraction failed!



If It Helps, My Dash is the latest one, which is higher than 2.0.13146.0
Its Something Like .13604

 

[tsquad131]

what drive did you have that you flashed with lt 2.0 before? it sounds like a sata problem since your not using a x360usb pro or your probe is broken

 

[B4DB01]

I've always flashed liteon's. 74850c..
My probe is working as I just tested it on another drive, its just this one drives key won't extract :/ it says serial flash found but then phatkey failed

 

[bandit123]

try redoing it and counting BANG ON 5 seconds when you power off then on i know its strange but try it

 

[bakley2578]

I've always flashed liteon's. 74850c..
My probe is working as I just tested it on another drive, its just this one drives key won't extract :/ it says serial flash found but then phatkey failed

Is the CD tray halfway open when you power up and try to probe? if it is not that can be your issue right there

 

[B4DB01]

I Have Tried Both The Above Methods Still No Luck..
If It Helps I've Attached An Image Of My JF Programme

 

[jsinger47]

try redoing it and counting BANG ON 5 seconds when you power off then on i know its strange but try it

5 seconds does NOT matter when you are using a no-capacitor probe

in fact, waiting time is detrimental in that case

all that is needed is a quick power cycle

---------- Post added at 12:57 ---------- Previous post was at 12:55 ----------

Is the CD tray halfway open when you power up and try to probe? if it is not that can be your issue right there

Tray position does NOT matter for phatkey

---------- Post added at 13:00 ---------- Previous post was at 12:57 ----------

I've always flashed liteon's. 74850c..
My probe is working as I just tested it on another drive, its just this one drives key won't extract :/ it says serial flash found but then phatkey failed

was this drive updated to 13146 dash with old ixtreme firmware, for example 1.6?

i've found that that can interfere with phatkey (MRA would be needed)

also, try cleaning MPX01 up, could be a poor connection

 

[B4DB01]

was this drive updated to 13146 dash with old ixtreme firmware, for example 1.6?

^ No It Wasnt, I Guess This Maybe The Problem, But Now It Is The Latest Dash, So What Next?

 

[B4DB01]

Another Thing Is, When I First Got It, It Was On Ixtreme 1.51, i tried to dummy from ixtreme, but somehow the drive got bricked, so then i unbricked it by flashing it to Stock 02510c without a valid key(dont ask why), so maybe that has caused this issue?