I9505 soft-bricked odin fails flashing roms

Search This thread

C4scade

New member
Feb 14, 2014
2
0
I come from an Omega ROM v19 (4.3) rooted on a Galaxy S4
I tried to flash back the stock ROM that was a 4.2.2 and ODIN came with that message
Code:
<ID:0/008> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9505XXUEMJ5_I9505OXAEMJ5_I9505XXUEMJ5_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/008> Odin v.3 engine (ID:8)..
<ID:0/008> File analysis..
<ID:0/008> SetupConnection..
<ID:0/008> Initialzation..
<ID:0/008> Get PIT for mapping..
<ID:0/008> Firmware update start..
<ID:0/008> SingleDownload.
<ID:0/008> sbl2.mbn
<ID:0/008> NAND Write Start!! 
<ID:0/008> sbl3.mbn
<ID:0/008> rpm.mbn
<ID:0/008> aboot.mbn
<ID:0/008> FAIL! (Auth)
<ID:0/008> 
<ID:0/008> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1

In download mode after the flash fails, appears this message
Code:
START [224,1440]
SW REV. CHECK FAIL : fused : 4, Binary : 3

I cant't solve that soft-brick, i tried on different USB ports but seems that is not working, even changing ODIN version
Can you help me?
PS: Sorry for my bad english :)
 
Last edited:

Ricardo_Is

Senior Member
May 4, 2011
1,661
851
São Paulo
I come from an Omega ROM v19 (4.3) rooted on a Galaxy S4
I tried to flash back the stock ROM that was a 4.2.2 and ODIN came with that message
Code:
 Added!!
 Enter CS for MD5..
 Check MD5.. Do not unplug the cable..
 Please wait..
 I9505XXUEMJ5_I9505OXAEMJ5_I9505XXUEMJ5_HOME.tar.md5 is valid.
 Checking MD5 finished Sucessfully..
 Leave CS..
 Odin v.3 engine (ID:8)..
 File analysis..
 SetupConnection..
 Initialzation..
 Get PIT for mapping..
 Firmware update start..
 SingleDownload.
 sbl2.mbn
 NAND Write Start!! 
 sbl3.mbn
 rpm.mbn
 aboot.mbn
 FAIL! (Auth)
 
 Complete(Write) operation failed.
 All threads completed. (succeed 0 / failed 1

In download mode after the flash fails, appears this message
Code:
START [224,1440]
SW REV. CHECK FAIL : fused : 4, Binary : 3

I cant't solve that soft-brick, i tried on different USB ports but seems that is not working, even changing ODIN version
Can you help me?
PS: Sorry for my bad english :)

Did you solved it?
If you have a nandroid backup just restore.
Before you try flash other stock firmware by Odin, perform a full wipe (Data/Cache and Dalvik).
Maybe it can solve your bad flash.

Edit : Did you check MD5 of your firmware?


? from my GT-I9300 NeatROM™ Slim AOSP V.2.8 ?
 
Last edited:

SecretMojo

Member
Feb 15, 2014
14
2
Did you solved it?
If you have a nandroid backup just restore.
Before you try flash other stock firmware by Odin, perform a full wipe (Data/Cache and Dalvik).
Maybe it can solve your bad flash.

Edit : Did you check MD5 of your firmware?


? from my GT-I9300 NeatROM™ Slim AOSP V.2.8 ?

Sorry for my bad english but
i also got the same error with odin :

aboot.mbn
FAIL! (Auth)

got no sound and got a black screen when calling mic also not working
flashing custom roms wont fix it any way to install stock i9505 rom without odin or kies ?
's it fixable any ideas ??
 

C4scade

New member
Feb 14, 2014
2
0
Did you solved it?
If you have a nandroid backup just restore.
Before you try flash other stock firmware by Odin, perform a full wipe (Data/Cache and Dalvik).
Maybe it can solve your bad flash.

Edit : Did you check MD5 of your firmware?


? from my GT-I9300 NeatROM™ Slim AOSP V.2.8 ?

Man, i don't think that a nandroid backup can solve a binary error.. and yes, i checked the firmware md5, it's ok, it is from sammobile.com
 

ranger4740

Senior Member
Jan 17, 2011
1,497
447
Melbourne
I'd say if you've got aboot fail then your trying to flash older rom on a phone that's had newer rom on it aka Knox already.

Sent from my GT-I9505 using xda app-developers app
 

mgolejnik

Member
Feb 8, 2012
6
1
Elgin
DONE!!!

Flash the ''i9505 pit'' file on odin in pda. That will fix ;)

Hi
I like to share how I fixed my S4 using ODIN 3.09

1. I flash the ''i9505 pit'' file on odin in pda (JUST THIS ONE FILE)
2. I used CF-Auto-Root-jflte-jfltexx-gti9505.tar
3. I tried to use Firmware with 4.3 because the phone had updated android to 4.3 v. but in the ODIN program appeared FAIL!
4. So I decided to install an older Firmware (with 4.2.2 v.) and it helped
Thank you for all the advice and good work XDA TEAM!!!
 
  • Like
Reactions: HackT3k

CarlM34

Senior Member
Dec 31, 2012
2,968
3,191
GPS anyone???
carlmccluskey.com
Hi
I like to share how I fixed my S4 using ODIN 3.09

1. I flash the ''i9505 pit'' file on odin in pda (JUST THIS ONE FILE)
2. I used CF-Auto-Root-jflte-jfltexx-gti9505.tar
3. I tried to use Firmware with 4.3 because the phone had updated android to 4.3 v. but in the ODIN program appeared FAIL!
4. So I decided to install an older Firmware (with 4.2.2 v.) and it helped
Thank you for all the advice and good work XDA TEAM!!!

Hi there,

Just out of interest, How did you manage to flash 4.2.2 firmware via Odin to a phone that had had the 4.3 firmware installed via an update??

I (and many others) are aware that 4.3/4 firmware has the KNOX enabled boot-loaders making it impossible to downgrade stock firmware:confused:

Or have I completely misunderstood your resolution/fix?

:eek:
 

mgolejnik

Member
Feb 8, 2012
6
1
Elgin
Hi there,

Just out of interest, How did you manage to flash 4.2.2 firmware via Odin to a phone that had had the 4.3 firmware installed via an update??

I (and many others) are aware that 4.3/4 firmware has the KNOX enabled boot-loaders making it impossible to downgrade stock firmware:confused:

Or have I completely misunderstood your resolution/fix?

:eek:

But I never wrote that I had installed version 4.3 / 4. This is the version which is installed this time: I9505XXUFNB9_I9505O2UFNA2_I9505XXUFNB9_HOME.tar after this I flash CF-Auto-Root-jflte-jfltexx-gti9505.tar and now it is rooted and it is KNOX (but not for long)

Maybe I made a mistake. If so, sorry
...
I MADE MISTAKE!!! I am so sorry for that!!!

I9505XXUFNB9_I9505O2UFNA2_I9505XXUFNB9_HOME.tar it is newest version it's 4.4.2!!! I am sorry again.
 
Last edited:

AbdulRahims06p

New member
Apr 4, 2018
1
0
I'm Also Having a problem with my samsung s4 gt-i9505 (INS)

i was trying to flash my phone with 4 files of firmware with Odin3 v3.10.6
and while flashing i got this problem
<ID:0/008> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> AP_I9500XXUHPI1_CL9155695_QB10809785_REV00_user_low_ship.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> BL_I9500XXUHPI1_CL9155695_QB10809785_REV00_user_low_ship.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> MODEM_I9500DDUHPE1_REV01_CL1856465_SIGNED.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CSC_ODD_I9500ODDHOJ1_CL5979820_QB6580299_REV00_user_low_ship.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/008> Odin engine v(ID:3.1005)..
<ID:0/008> File analysis..
<ID:0/008> SetupConnection..
<ID:0/008> Initialzation..
<ID:0/008> Set PIT file..
<ID:0/008> DO NOT TURN OFF TARGET!!
<ID:0/008> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
if you have any solution please reply
 

Top Liked Posts

  • There are no posts matching your filters.
  • 1
    Flash the ''i9505 pit'' file on odin in pda. That will fix ;)
    1
    DONE!!!

    Flash the ''i9505 pit'' file on odin in pda. That will fix ;)

    Hi
    I like to share how I fixed my S4 using ODIN 3.09

    1. I flash the ''i9505 pit'' file on odin in pda (JUST THIS ONE FILE)
    2. I used CF-Auto-Root-jflte-jfltexx-gti9505.tar
    3. I tried to use Firmware with 4.3 because the phone had updated android to 4.3 v. but in the ODIN program appeared FAIL!
    4. So I decided to install an older Firmware (with 4.2.2 v.) and it helped
    Thank you for all the advice and good work XDA TEAM!!!