Lollipop Leak Available for the Sprint Galaxy S5

Since the Android 5.0Lollipop’s official release not too long ago, we’ve seen … more

CPU Spy Gets an Android Lollipop Makeover

At some point in the distant past, you probably heard of CPU Spy for Android by XDARetired … more

Amazon Fire TV Stick vs Chromecast – XDA TV

There is no doubt that Amazon is a huge player in many markets, and they want to be a huge … more

Fight the Heat and Conserve Battery with EaseUS Coolphone

Memory hungry Android applications are often responsible for making our device … more

Welcome to XDA

Search to go directly to your device's forum

Register an account

Unlock full posting privileges

Ask a question

No registration required
Post Reply

[Q] Can't Odin soft brick Getting Fail on Auth. How to fix?

OP kruuth

18th February 2014, 02:36 PM   |  #1  
OP Senior Member
Thanks Meter: 9
 
300 posts
Join Date:Joined: Oct 2010
I took my S4 from MF3 down to MK2. Then I stupidly installed TWRP and it got stuck on:

"FIrmware upgrade encountered an issue. Please select recovery mode in Kies and try again"

I tried using kies to fix this but that doesn't work either. The recovery says at the top:

ODIN MODE
PRODUCT NAME: SGH-I337
CURRENT BINARY: Samsung Official
KNOX KERNEL LOCK:0x0
KNOX WARRANY VOID:0x0
CSB-CONFIG-LSB:0x30
WRITE PROTECTION:Enable
eMMC BURST MODE:enable

KIES goes to emergency recovery and gets as far as decompressing binary files. After that it sits at "Firmware emergency stopped due to Galaxy S4(SGH-I337)error. If the prolblem persists, please contact the Samsung service centre.

Odin errors like this:

<ID:0/005> Firmware update start..
<ID:0/005> sbl1.mbn
<ID:0/005> NAND Write Start!!
<ID:0/005> sbl2.mbn
<ID:0/005> sbl3.mbn
<ID:0/005> rpm.mbn
<ID:0/005> aboot.mbn
<ID:0/005> FAIL! (Auth)

How do I fix this?

*EDIT: With ODIN, it writes:
START [224,140]
BAR [248,1440]
SW REV. CHECK FAIL : FUSED 4, BINARY:2
Last edited by kruuth; 18th February 2014 at 02:39 PM. Reason: More info
18th February 2014, 02:50 PM   |  #2  
jd1639's Avatar
Recognized Contributor
Minnetonka, MN
Thanks Meter: 3,788
 
10,849 posts
Join Date:Joined: Sep 2012
You should be able to get your phone working with Odin. Read this thread http://forum.xda-developers.com/show...php?p=49687770

Sent from my Nexus 5
The Following User Says Thank You to jd1639 For This Useful Post: [ View ]
18th February 2014, 03:20 PM   |  #3  
OP Senior Member
Thanks Meter: 9
 
300 posts
Join Date:Joined: Oct 2010
Quote:
Originally Posted by jd1639

You should be able to get your phone working with Odin. Read this thread http://forum.xda-developers.com/show...php?p=49687770

Sent from my Nexus 5

Interestingly, I get the startup sound, and I get it to be recognized in windows, but no display. What happened?
18th February 2014, 04:28 PM   |  #4  
jd1639's Avatar
Recognized Contributor
Minnetonka, MN
Thanks Meter: 3,788
 
10,849 posts
Join Date:Joined: Sep 2012
Quote:
Originally Posted by kruuth

Interestingly, I get the startup sound, and I get it to be recognized in windows, but no display. What happened?

There's no display on the phone? If Odin recognizes your device I would go ahead and try to flash the tar.

Sent from my Nexus 5
18th February 2014, 04:37 PM   |  #5  
SelfElevated2's Avatar
Senior Member
Thanks Meter: 263
 
809 posts
Join Date:Joined: Oct 2012
First you didn't go down. You went up to mk2. And you need to Odin the mk2 stock tar. The boot loader will block you from trying to Odin mf3 or any thing before mk2.

Future reference you are on a locked boot loader. U cannot flash a custom recovery or use anything other than stock kernel.

Look into safe strap If you get your phone working again
Last edited by SelfElevated2; 18th February 2014 at 04:39 PM.
18th February 2014, 06:40 PM   |  #6  
OP Senior Member
Thanks Meter: 9
 
300 posts
Join Date:Joined: Oct 2010
D'oh. You're correct. Thanks.

Quote:
Originally Posted by SelfElevated2

First you didn't go down. You went up to mk2. And you need to Odin the mk2 stock tar. The boot loader will block you from trying to Odin mf3 or any thing before mk2.

Future reference you are on a locked boot loader. U cannot flash a custom recovery or use anything other than stock kernel.

Look into safe strap If you get your phone working again

Post Reply Subscribe to Thread
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes