Okay, I need help and I feel dumb..

Search This thread

attbrandon

Senior Member
Apr 4, 2013
78
60
I rooted my s4 just to try it and I'm stuck trying to get it to go back to stock.

I have a note 3 now and I've got everything going well with that but the s4 (I have the I337).

I have it rooted and the phone will start and is a perfectly functional android phone, but whenever I try to get it into recovery mode I can only get it to go to download mode. Odin flashes to stock fail with this:

<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I337UCUAMDB_I337ATTAMDB_I337UCUAMDB_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> aboot.mbn
<ID:0/005> NAND Write Start!!
<ID:0/005> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)

the stock flash was linked to by others I found on XDA.

Also, details about the phone:

Jelly Bean 4.2.2
Baseband I337UCAMF3
Clockworkmod 6.0.4.4

Thanks for any and all help!
 
I rooted my s4 just to try it and I'm stuck trying to get it to go back to stock.

I have a note 3 now and I've got everything going well with that but the s4 (I have the I337).

I have it rooted and the phone will start and is a perfectly functional android phone, but whenever I try to get it into recovery mode I can only get it to go to download mode. Odin flashes to stock fail with this:

<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I337UCUAMDB_I337ATTAMDB_I337UCUAMDB_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> aboot.mbn
<ID:0/005> NAND Write Start!!
<ID:0/005> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)

the stock flash was linked to by others I found on XDA.

Also, details about the phone:

Jelly Bean 4.2.2
Baseband I337UCAMF3
Clockworkmod 6.0.4.4

Thanks for any and all help!

You cannot add a custom recovery to MF3 if the phone came with that firmware you will get hard brick

Sent From My Galaxy S4 SAMSUNG-SGH-I337 Running On New Deadly Venom v1.3.6 Jelly Bean 4.3

---------- Post added at 04:55 PM ---------- Previous post was at 04:51 PM ----------

You cannot add a custom recovery to MF3 if the phone came with that firmware you will get hard brick

Sent From My Galaxy S4 SAMSUNG-SGH-I337 Running On New Deadly Venom v1.3.6 Jelly Bean 4.3

I wish I could help more but I'm on the road hopefully someone will explain it better then what I mention.

Sent From My Galaxy S4 SAMSUNG-SGH-I337 Running On New Deadly Venom v1.3.6 Jelly Bean 4.3
 

DeadlySin9

Senior Member
Sep 2, 2012
1,475
703
Google Pixel 8 Pro
Because you are on MF3, the bootloader is locked and there is no exploit. Therefore, custom recoveries won't install. The reason ODIN is failing is because you are using the MDB files instead of MF3. It is impossible to downgrade the firmware back to any previous version. If you want a recovery, the most you can get is Safestrap, but make sure you read up plenty on it before you install it, as it is not a normal recovery and is not even installed to the recovery partition.
 

ramiijabedd

New member
Mar 19, 2014
1
0
need help

every time i try to reset my galaxy s4 att to stock it fails heres what it says



<OSM> Enter CS for MD5.. <OSM> Check MD5.. Do not unplug the cable.. <OSM> Please wait.. <OSM> I337UCUAMDB_I337ATTAMDB_I337UCUAMDB_HOME.tar.md5 is valid. <OSM> Checking MD5 finished Sucessfully.. <OSM> Leave CS.. <ID:0/005> Added!! <ID:0/005> Odin v.3 engine (ID:5).. <ID:0/005> File analysis.. <ID:0/005> SetupConnection.. <ID:0/005> Initialzation.. <ID:0/005> Get PIT for mapping.. <ID:0/005> Firmware update start.. <ID:0/005> aboot.mbn <ID:0/005> NAND Write Start!! <ID:0/005> FAIL! (Auth) <OSM> All threads completed. (succeed 0 / failed 1)
 

megamanDJ

Senior Member
Jan 21, 2014
63
13
New Orleans
every time i try to reset my galaxy s4 att to stock it fails heres what it says



<OSM> Enter CS for MD5.. <OSM> Check MD5.. Do not unplug the cable.. <OSM> Please wait.. <OSM> I337UCUAMDB_I337ATTAMDB_I337UCUAMDB_HOME.tar.md5 is valid. <OSM> Checking MD5 finished Sucessfully.. <OSM> Leave CS.. <ID:0/005> Added!! <ID:0/005> Odin v.3 engine (ID:5).. <ID:0/005> File analysis.. <ID:0/005> SetupConnection.. <ID:0/005> Initialzation.. <ID:0/005> Get PIT for mapping.. <ID:0/005> Firmware update start.. <ID:0/005> aboot.mbn <ID:0/005> NAND Write Start!! <ID:0/005> FAIL! (Auth) <OSM> All threads completed. (succeed 0 / failed 1)

Grab the MF3 Odin flashable tars and flash them the same way to get back to complete factory stock. Or you can get the MK2 tars and update to 4.3 and use Saferoot to easily get root since you already have drivers installed. Then look up how to install Safestrap for MK2, (which is really not too difficult), and TWRP v3.71to use as a recovery.
 
  • Like
Reactions: ramiijabedd

Top Liked Posts

  • There are no posts matching your filters.
  • 1
    every time i try to reset my galaxy s4 att to stock it fails heres what it says



    <OSM> Enter CS for MD5.. <OSM> Check MD5.. Do not unplug the cable.. <OSM> Please wait.. <OSM> I337UCUAMDB_I337ATTAMDB_I337UCUAMDB_HOME.tar.md5 is valid. <OSM> Checking MD5 finished Sucessfully.. <OSM> Leave CS.. <ID:0/005> Added!! <ID:0/005> Odin v.3 engine (ID:5).. <ID:0/005> File analysis.. <ID:0/005> SetupConnection.. <ID:0/005> Initialzation.. <ID:0/005> Get PIT for mapping.. <ID:0/005> Firmware update start.. <ID:0/005> aboot.mbn <ID:0/005> NAND Write Start!! <ID:0/005> FAIL! (Auth) <OSM> All threads completed. (succeed 0 / failed 1)

    Grab the MF3 Odin flashable tars and flash them the same way to get back to complete factory stock. Or you can get the MK2 tars and update to 4.3 and use Saferoot to easily get root since you already have drivers installed. Then look up how to install Safestrap for MK2, (which is really not too difficult), and TWRP v3.71to use as a recovery.