ANSWERED Authorisation Failed!

B

bruno12345

Junior Member
Apr 9, 2011
23
0
Brasil
I've got a previously flashed (another guy did it) 0272.

I've got the key, the dummy.bin, and the OFW my self (a lt2.0 firmware)

I've sucessfully READ.
And then, used the OFW (lt2.0) as source firmware, with the correct key.

and then LT 3.0 as target firmware and spoofed the key. They both matched.

Then, i go to MTK Flash 32 tab, and clicked Write (the drive was SPI status 0x00) and this is the JF log

Getting Status from port 0x0000
SPi flash found with Status 0x72

Getting Status from port 0x0000
SPi flash found with Status 0x72

Sending Chip Erase to Port 0x0000
Erasing:
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: ................
Dumped in 5062mS

Write verified OK !

Restoring sector 0x3E000.

Sending Sector Erase to Port 0x0000
Erasing: 0x3E000
Writing: 0x3E000
............
Authorisation Failed!
Restore Verify Failed !


This is the JF log.

Now i dont know what to do, i cant slim key (it says SlimKey Extraction failed)

and the DVD key appears as "Not Found"
 
rroddr

rroddr

Full Member
Jun 30, 2010
66
0
I don't know what your using for flashing but I know whenever I tried using onboard sata to do a slim it miserably failed

I was using via6421 pci card for a long time (2 1/2 years)

Now I use a Maximus 360 lizard I never have any slims that fail flash also i use the ck3 pro and probe 3 I didn't like the probed that came with my unit..
 
B

bruno12345

Junior Member
Apr 9, 2011
23
0
Brasil
EDIT:

Found it out by myself the solution, after 40 minutes of try and fail, i found a way.

flashing dummy.bin as source, and stock as target...

then the drive was back to normal.

then read key, saved OFW. Used OFW as source, and LT3.0 as target and OOOOOOOH YEAH, its all working.

thanks all.


MODS CAN CLOSE THIS TOPIC
 
Last edited:
J

Jahaziel

VIP Member
May 28, 2010
177
0
Bradenton, FL
thanks for this useful thread after flashing many slims i came across this prob and now its working again!! :) thought it was my first bad kamikaze. thank you
 
T

tflis007

Noob Account
Feb 6, 2011
2
0
I got the same problem using ck3 pro usb.

what i try to do is:

1. Take damaged 0225 drive out and extract key from it
2. Buy new 9504 drive
3. Using JF 0.1.92 (304) open firmware from 0225 as source and firmware for 9504 as target.
4. Spoof source as target.

result:

Serial flash found with Status 0x72
Sending Device ID request to port 0x0000
Spi Status: 0x00
Manufacturer ID: 0xEF
Device ID: 0x11
Flash Name: Winbond/NEX(W25P20/NX25P20)
Flash Size: 262144 bytes
Getting Status from port 0x0000
SPi flash found with Status 0x72
Sending Chip Erase to Port 0x0000
Erasing:
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: ................
Dumped in 3860mS
Write verified OK !
Restoring sector 0x3E000.
Sending Sector Erase to Port 0x0000
Erasing: 0x3E000
Writing: 0x3E000
............
Authorisation Failed!
Restore Verify Failed !

I tried to use dummy as source and stock as target but still the same. :crazy:
 
Oggy

Oggy

Staff member
Troll Eating Dogs
Mar 1, 2010
3,346
128
Youre trying to spoof a slim drive.

Use 0225 as target.

It doesnt auth, just like the 360 wouldnt permit it, JF doesnt
 
jsinger47

jsinger47

Troll Eating Dogs
Feb 6, 2011
8,133
128
Grand Rapids, MI
tflis007 said:
I got the same problem using ck3 pro usb.

what i try to do is:

1. Take damaged 0225 drive out and extract key from it
2. Buy new 9504 drive
3. Using JF 0.1.92 (304) open firmware from 0225 as source and firmware for 9504 as target.
4. Spoof source as target.

result:

Serial flash found with Status 0x72
Sending Device ID request to port 0x0000
Spi Status: 0x00
Manufacturer ID: 0xEF
Device ID: 0x11
Flash Name: Winbond/NEX(W25P20/NX25P20)
Flash Size: 262144 bytes
Getting Status from port 0x0000
SPi flash found with Status 0x72
Sending Chip Erase to Port 0x0000
Erasing:
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: ................
Dumped in 3860mS
Write verified OK !
Restoring sector 0x3E000.
Sending Sector Erase to Port 0x0000
Erasing: 0x3E000
Writing: 0x3E000
............
Authorisation Failed!
Restore Verify Failed !

I tried to use dummy as source and stock as target but still the same. :crazy:
Click to expand...
Your problem is lack of grasping concepts. If the orig drive is 0225, you should flash a replacement pcb with 0225

If spelling error, I blame Tapatalk.
 
  • Like
Reactions: capsone
J

jorgekikon

Noob Account
Jul 1, 2011
1
0
bruno12345 said:
EDIT:

Found it out by myself the solution, after 40 minutes of try and fail, i found a way.

flashing dummy.bin as source, and stock as target...

then the drive was back to normal.

then read key, saved OFW. Used OFW as source, and LT3.0 as target and OOOOOOOH YEAH, its all working.

thanks all.


MODS CAN CLOSE THIS TOPIC
Click to expand...
Thanks a lot this saved my Drive
 
You must log in or register to reply here.