ANSWERED PhatKey extraction failed on ms repaired console

professor_jonny

VIP Member
So I have a ms repaired console and I can't get the key from it I first tried with a sub 13xxx kernel and it would not work then i tried with 17150 and still nothing.

any one have any ideas ?
i have never had problems before


Code:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
JungleFlasher 0.1.96 Beta (323)
Session Started Wed Jan 14 10:59:57 2015
 
This is a Wow 64 process running on 2 x 64 bit CPUs 
portio64.sys Driver Installed 
portio64.sys Driver Started, thanks Schtrom ! 
Found 6 I/O Ports.
Found 1 Com Ports.
Found 4 windows drives A: C: D: E:
Found 0 CD/DVD drives
 
Drive is Lite-On.. 
Sending Vendor Intro to port 0xD480
Status 0x51
Re-sending Vendor Intro: 
............
Serial flash found with Status 0x52
 
Extracted drive key failed Verification !
 
 
PhatKey extraction failed!
 

Oggy

Staff member
Troll Eating Dogs
Mar 1, 2010
3,367
128
Try without the probe (seriously!)
 

professor_jonny

VIP Member
It did not fear any better.

Code:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
JungleFlasher 0.1.96 Beta (323)
Session Started Wed Jan 14 11:39:24 2015
 
This is a Wow 64 process running on 2 x 64 bit CPUs 
portio64.sys Driver Installed 
portio64.sys Driver Started, thanks Schtrom ! 
Found 6 I/O Ports.
Found 1 Com Ports.
Found 4 windows drives A: C: D: E:
Found 0 CD/DVD drives
 
Drive is Lite-On.. 
Sending Vendor Intro to port 0xD480
Status 0x51
Re-sending Vendor Intro: 
....................................
Device Intro failed!
 
PhatKey extraction failed!
 

GeekHeat

VIP Member
Jun 28, 2013
1,819
88
lancashire
I know it stating the obvious, but are all leads in correctly and have u got another liteon drive u can try your probe on.
 

15432

VIP Member
Nov 14, 2010
703
68
Russia
older JF versions should write the extracted key in the log (before verification attempt). you can 'grab' it and test on any donor drive.

but the best way is to do MRA and read the whole firmware (if we have another revision, that's pretty interesting)
 

Game_Over

Staff member
Top TX Brass
Dec 2, 2010
5,359
138
127.0.0.1
If all else fails you can decrypt the nand and get the key that way.
 

professor_jonny

VIP Member
older JF versions should write the extracted key in the log (before verification attempt). you can 'grab' it and test on any donor drive.

but the best way is to do MRA and read the whole firmware (if we have another revision, that's pretty interesting)
I had to do the old mra hack and it worked perfectly fine to get the keys all modded now thanks.

I tried another drive same model just to see and it worked with the probe method so it must be something special with that drive or my toung was poking out in the wrong direction :)

dump was reported as stock by jungle flasher.

Edit: forgot to mention I had to flash with dos flash I could not enter vendor mode 0x72 after I reverted the MRA hack.
 
Last edited: