Database Users

[HELP] Bricked phone, now Odin and Kies rejecting firmware reset

Last night I bricked my phone, trying to flash the stock modem (NAE) on mobile Odin. As of right now, it does not boot, simply being stuck at the SAMSUNG GALAXY S4 screen. It will not boot into recovery, instead rebooting to the same screen once more. Kies will not see the connection, and I have reinstalled it, the drivers, etc.
Odin does the same thing, but sees the connection. All I get is this after trying to flash the firmware (both with Auto Reboot and F. Reset Time on and off)
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> L720VPUFNAE_L720SPTFNAE_L720VPUFNAE_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
And the firmware that I am using is the "L720VPUFNAE_L720SPTFNAE_L720VPUFNAE_HOME.tar.md5." I don't know what to do, and I was thinking that someone could help me here.

Were you on NG2 perhaps? If so, you cannot go back to NAE and that would explain the Odin failure.
Go to www.sammobile.com and download the NG2.tar and give that a try.

If only I had thought of that (which I couldn't have)! Thanks, this worked. I was on the NC6 version of the ROM, and have downloaded/installed this. It works like a charm except one thing; the data seems to either not be working, or extremely slow at times. That, and the messaging does not appear to work. Wifi is the same way at times.

Novorone said:
If only I had thought of that (which I couldn't have)! Thanks, this worked. I was on the NC6 version of the ROM, and have downloaded/installed this. It works like a charm except one thing; the data seems to either not be working, or extremely slow at times. That, and the messaging does not appear to work. Wifi is the same way at times.
Click to expand...
Click to collapse
If you were on NC6 you have a triband model (720T) and need NG5.tar.

[Help] G900A unable to flash with ODIN trying to bring phone to stock - was towelroot

Hi,
I am trying to unroot my wife's Samsung Galaxy S5 SM-G900A. I went ahead and did unroot via SU, then reboot. I've done a reset/wipe via recovery mode which was successful this was all after attempting to flash to stock ROM and it kept failing. I was hoping unrooting and wiping data and cache would help but none has I keep running into the same problem in ODIN see below:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> G900AUCU1ANCE_G900AATT1ANCE_G900AUCU1ANCE_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
I have tried multiple Samsung branded USB cords in multiple USB ports (even on multiple computers) all with the same issue. I went ahead and downloaded the G900A PIT file and tried to install that with ODIN but that failed as well. I have debug mode enabled it didn't change anything. I have also used multiple versions of ODIN both v3-1.85 and v3-3.07 both produce same error.
the rom I'm trying to flash to is: G900AUCU1ANCE_G900AATT1ANCE_G900AUCU1ANCE_HOME.tar.md5 the PIT I ended up trying was SM-G900A_pit.pit.
This phone was originally rooted with towelroot I think at one point I put a ROM on the phone after an update came out that took root away. That rom allowed me to re-root with towelroot and I ended up freezing a ton of the apps and the autoupdate so it wouldn't ever happen again.
Model Number: SAMSUNG-SM-G900A
Android Version 4.4.2
Baseband version: G900AUCU2AND3
Kernel version: 3.4.0-2178781 [email protected] #1 TUE JUL 22 13:58:46 KST 2014
Build Number: KOT49H.G900AUCU2AND3
If anyone could provide any help in getting this phone back to stock I would really appreciate it

meh i gave up. took it to AT&T they said they had no way to hook it up to flash it which is strange I've read some stores were able to force a flash after people encountered this issue with ODIN but oh well. turned it in for an upgrade for the wife

S4 GT-I9506 is stuck on Firmware upgrade encountered an issue

this model seems difficult (gt-i9506)
i tried to root it via towelroot, then kingoroot, these failed but then now the reboot is stuck on "firmware upgrade encountered an issue"
ive tried Kies firmware recovery but the download fails after 80%,
ive tried the sammobile download the ROM this too fails, network drops out tried this 3 times
i want to try Kies emergency recovery but cant find any recovery code
im stuck i dont know what to do now been researching for 4 hours cant find solution :crying:

could anyone please help?? am going crazy over this spent 2 days researching and finding nothing

Download a complete stock rom and flash it with ODIN. You have to uninstall KIES beforehand (they are conflicting).

thanks for reply...
i took kies off and this is what Odin is giving me...
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9506XXUAMHF_I9506VAUAMH3_I9506XXUAMHD_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> aboot.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL! (Auth)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
the device says this.....
SW REV CHECK FAIL: [aboot]Fused 1 > Binary0
does this highlight anything that could be going wrong?

Not sure... but looks like the rom is not for that device. Are you sure you have a i9506?

on samsmobile GT-I9506/VAU/ Roms (i cant post link)
well the first ROM was 4.2 android (bottom of ROM list), so then tried 4.4 (top of ROM list) android it failed again but with different Odin errors...
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9506XXUCNJ1_I9506VAUCNJ1_I9506XXUCNK1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
<ID:0/003> Added!!
can anyone see the fault here...?? no error came up on the device, only on Odin this time

Did you restart after KIES de-installation? Was USB driver successfully missing (so you had to install one manually for ODIN)? If not, you probably still have drivers/files running from KIES.
Otherwise, try a different computer to double check its not the system.

If you originally updated to Android 4.4.x or later on this device, you cannot install 4.3.x or lower as Knox within the bootloader will actively prevent Odin from functioning. As to Odin, make sure you're using the original cable, are not using a hub, have Kies disabled or uninstalled, and use a different USB port. Odin sometimes is picky about the ports it uses.
If you can get the ROM issue resolved, use CF-Autoroot to root, keeping in mind that you will trip the Knox flag in doing so. Towelroot and other one-click root methods don't work on your device.

FIXED IT!!!!!!! :laugh::silly::good::cyclops:
Moved all operations to a different PC running XP with no kies on it
The error still occurred "write fail"
So instead i tried Odin 3.09 instead of 3.07 but most of all i changed usb cables, found an original cable off my mates Nokia
then boom!!! she starting writing!!!
Thankyou so much you legends, you are now my best friends forever!!!
Strangely the new flash, all my old previous data & apps are still on there??? somehow the network is not locked either which i was fearing being a vodafone ROM
still want to root it though

Flashing a ROM through Odin doesn't wipe the data partition, which is why your apps are untouched.

SM-N9009 (china telecom) Firmware upgrade encountered an issue.

I own SM-N9009 (china telecom) unit, running 5.0 Lollipop version with PDA no. N9009KEU2GPB1 build date 02-23-2016. Initially, the problem was, I coudn't install G apps like Youtube, Google play services, Google play store etc.. I did some researches online how to make solutions for it. Then i found out in order to install G apps i have to root first my device, i downloaded CF-Auto-Root-hlte-h3gduosctc-smn9009 file that also contains odin on it, while on the process and almost 20-25mins have passed and downloading process had stopped or it never continued and only reached maybe 40% and i got annoyed and i disconnected the device from the PC. I removed the battery, reinserted and tried to turn it on when it opened the display showed like this: "Firmware upgrade encountered an issue. Please select recovery mode in kies & try again". I tried to flash using the firmware i just downloaded but unforfunately it was failed again results show like this:
<ID:0/012> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/012> Odin engine v(ID:3.1101)..
<ID:0/012> File analysis..
<ID:0/012> SetupConnection..
<ID:0/012> Initialzation..
<ID:0/012> Get PIT for mapping..
<ID:0/012> Firmware update start..
<ID:0/012> SingleDownload.
<ID:0/012> aboot.mbn
<ID:0/012>
<ID:0/012> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Is there any advice/suggestion how to fix this?
Thank you.

Since Odin stops when trying to flash aboot.mbn, there could be four possible issues:
the firmware is not for your phone;
the firmware has a bootloader that is older than the bootloader on the phone;
try a different USB cable; or
try a different USB port.

FAIL! SHA256 is Invalid error trying to Root

I, along with several other users, have been getting a SHA256 is invalid error when trying to do the root from this thread:
http://forum.xda-developers.com/att-note-7/how-to/root-complete-stock-ph1-setup-root-t3463187
The fail comes in at the step when trying to flash the Sprint userdebug firmware in the AP slot.
I tried using different computers, cables, and ODIN and all that happened was I managed to brick my phone (but then fix it by flashing the stock ATT files thankfully)
One thing I noticed is that the firmware is downloaded as an MD5 instead of a TAR file, but I assume this has no bearing on the error.
Does anyone have any solution to this problem? It seems there are many people who have been able to acquire root, so there must be some solution available.
Any help is greatly appreciated as root access will be incredibly beneficial!
This is what the log looks like in the Odin version provided in the post:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin engine v(ID:3.1205)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> FAIL! SHA256 is invalid
<OSM> All threads completed. (succeed 0 / failed 1)

Luigiman765 said:
I, along with several other users, have been getting a SHA256 is invalid error when trying to do the root from this thread:
http://forum.xda-developers.com/att-note-7/how-to/root-complete-stock-ph1-setup-root-t3463187
The fail comes in at the step when trying to flash the Sprint userdebug firmware in the AP slot.
I tried using different computers, cables, and ODIN and all that happened was I managed to brick my phone (but then fix it by flashing the stock ATT files thankfully)
One thing I noticed is that the firmware is downloaded as an MD5 instead of a TAR file, but I assume this has no bearing on the error.
Does anyone have any solution to this problem? It seems there are many people who have been able to acquire root, so there must be some solution available.
Any help is greatly appreciated as root access will be incredibly beneficial!
This is what the log looks like in the Odin version provided in the post:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin engine v(ID:3.1205)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> FAIL! SHA256 is invalid
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
You have the wrong version of Odin. I replied to your comment in another thread with the link. But it's someone who uploaded a copy of the fixed Odin from one of the root threads.
It was post #168 or #186. I'm away from that tab now.
I know you have the latest version, but you need the other version that's cooked to work with this spirit root package

grmcrkrs said:
You have the wrong version of Odin. I replied to your comment in another thread with the link. But it's someone who uploaded a copy of the fixed Odin from one of the root threads.
It was post #168 or #186. I'm away from that tab now.
I know you have the latest version, but you need the other version that's cooked to work with this spirit root package
Click to expand...
Click to collapse
Well, this did in fact move me past the SHA256 Invalid error but I was presented with a new error:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin engine v(ID:3.1203)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Set PIT file..
<ID:0/005> DO NOT TURN OFF TARGET!!
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> SingleDownload.
<ID:0/005> emmc_appsboot.mbn
<ID:0/005> lksecapp.mbn
<ID:0/005> xbl.elf
<ID:0/005> FAIL! (Auth)
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
And on the phone:
SW REV CHECK FAIL : [aboot]Fused 2 > Binary 1
[1]eMMC write fail: aboot
Then, my phone bricked. Again. Luckily I already fixed this once and I fixed it again.
At this point I assume I just have some unrootable version of the phone and can live with it I suppose.
Bricking a phone this expensive isn't fun despite the fact that I have fixed it.

they slipped a new bootloader in with the "green battery" icon update. this new updated bootloader checks and will not allow a downgrade in version. root method #patched
i took the update on my defective device, just to test this. you are lucky, i am unable to get my device back to ATT stock, i am bricked.

cordell12 said:
they slipped a new bootloader in with the "green battery" icon update. this new updated bootloader checks and will not allow a downgrade in version. root method #patched
i took the update on my defective device, just to test this. you are lucky, i am unable to get my device back to ATT stock, i am bricked.
Click to expand...
Click to collapse
Guess I'm bricked too.. same issues.. if a new update comes out, will that get loaded and allow the device to start working again? I thought bricked was the device not even turning on.
Mine turns on and everything works find except i have no cell reception at all - circle w/line through it. can seem to get it rooted and this all happened just after the last update but not sure if it was related. Samsung thinks I rooted the phone but I've never done that in my life so not I have no choice but to try in order to get a working phone back... but that doesn't seem to be working either.. ugh. $800 for a phone that worked for 8 months...

Same as you. Everything works but cell service
MellowJoe said:
Guess I'm bricked too.. same issues.. if a new update comes out, will that get loaded and allow the device to start working again? I thought bricked was the device not even turning on.
Mine turns on and everything works find except i have no cell reception at all - circle w/line through it. can seem to get it rooted and this all happened just after the last update but not sure if it was related. Samsung thinks I rooted the phone but I've never done that in my life so not I have no choice but to try in order to get a working phone back... but that doesn't seem to be working either.. ugh. $800 for a phone that worked for 8 months...
Click to expand...
Click to collapse
hAVE YOU BEEN ABLE TO DO ANYTHING

Luigiman765 said:
Well, this did in fact move me past the SHA256 Invalid error but I was presented with a new error:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin engine v(ID:3.1203)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Set PIT file..
<ID:0/005> DO NOT TURN OFF TARGET!!
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> SingleDownload.
<ID:0/005> emmc_appsboot.mbn
<ID:0/005> lksecapp.mbn
<ID:0/005> xbl.elf
<ID:0/005> FAIL! (Auth)
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
And on the phone:
SW REV CHECK FAIL : [aboot]Fused 2 > Binary 1
[1]eMMC write fail: aboot
Then, my phone bricked. Again. Luckily I already fixed this once and I fixed it again.
At this point I assume I just have some unrootable version of the phone and can live with it I suppose.
Bricking a phone this expensive isn't fun despite the fact that I have fixed it.
Click to expand...
Click to collapse
But see, it failed at the aboot part.
Try flashing the combination file for your current bootloader version. Once that is installed try again.
Combination Files always ship with the revision 1 aboot for that binary version. And they are signed. So you can downgrade to a revision A aboot file by using the Combination files.
This might help. PrinceComsy's version of ODIN or Jester's version of ODIN are the ones usually used for AT&T devices with checksum errors.
(i.e When you see a build like 3CQB2 or 5BPK1 or something like that. The first digit on the build is the bootloader revision or binary version of the firmware. That second digit is the aboot revision. The last 3 digits are the time the build was created and its revision number.
When I had my AT&T Note 5, I had updated to Binary 3 aka Marshmallow. I couldn't go back to the binary 2, LP 5.1.1 builds to root anymore. Using the combination file for binary 3 I was able to flash a binary 2 AP file overtop of the rest of the binary 3 combination firmware. And it booted up just fine! I was able to downgrade and root because of the combination file.