Database Develop

[Q] Odin wont flash back to stock

Hello people.
This started couble of weeks ago when my phone suddendly went to factory mode. it wasent rooted and i was running 4.3 so i took it to the repair center. They told me that the phones circuit board needed to be replaced and it would cost 281€. Since the same phone new was only 299€ i declined their repair. then i went on a search for way to repair the phone my self. I wound some ways but they needed a root acces. So i tried to downgrade my phone back to 4.1.2 but for some reason Odin started to give me this error...
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9305XXBMI3_I9305NEEBMH1_I9305XXBMH3_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> tz.img
<ID:0/003> NAND Write Start!!
<ID:0/003> sboot.bin
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<ID:0/003> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
And then when i restarted my phone it keeps giving me yet another error saying that "Firmware upgrade encountered an issue. please select recovery mode in Kies & try again. In kies the phone wont connect to it. it just keeps loading. Now im asking for some help if some1 has an idea or a way to fix this.
I can give more info if needed.

it fails cause you are trying to flash 4.1.2...once you got 4.3 you can't go back...i'm guessing that you get that error when it tries to install the old bootloader(without knox counter)....

spiderman07 said:
it fails cause you are trying to flash 4.1.2...once you got 4.3 you can't go back...i'm guessing that you get that error when it tries to install the old bootloader(without knox counter)....
Click to expand...
Click to collapse
yeah i figured that out. tryed to follow a guide but it dident work... but flashed to 4.3 and that worked and auto rooted my phone and factory mode gone and everything is back to normal

[Q] soft bricked after failed downgrade from 5.0 lollipop

I apparently did not do enough reading prior to trying to downgrade my AT&T S5 to 4.4.2 after taking the OTA 5.0 update.
I am now stuck at either the 'firmware upgrade failed' or phone constantly going to the recovery menu (depending on if i've tried to push an AP file via Odin).
I know understand downgrading is impossible at this point, but I'm trying to find a way to get my phone back up and running. Any assistance on what file(s) I can push via Odin to resolve would be greatly appreciated. My device was not rooted prior to the OTA lollipop update so I'm limited to the 'stock' recovery options.

DamnYank! said:
I apparently did not do enough reading prior to trying to downgrade my AT&T S5 to 4.4.2 after taking the OTA 5.0 update.
I am now stuck at either the 'firmware upgrade failed' or phone constantly going to the recovery menu (depending on if i've tried to push an AP file via Odin).
I know understand downgrading is impossible at this point, but I'm trying to find a way to get my phone back up and running. Any assistance on what file(s) I can push via Odin to resolve would be greatly appreciated. My device was not rooted prior to the OTA lollipop update so I'm limited to the 'stock' recovery options.
Click to expand...
Click to collapse
You need to flash the OC4 stock kernel.

muniz_ri said:
You need to flash the OC4 stock kernel.
Click to expand...
Click to collapse
Muniz, i would be more than happy to. I've been searching though for a 5.0 sm-g900a tar/md5 file that i can load/flash via Odin but I have not been able to find any (other than a 'pre-rooted' one but I want to stay stock/ unrooted if possible).
Do you have any tips on where I could find it?
Thank you!

muniz_ri said:
You need to flash the OC4 stock kernel.
Click to expand...
Click to collapse
I found your other thread, i tried using your G900A_OC4_Stock_Rooted_Firmware.tar.md5 file via Odin and selecting it for the AP field. When executing, Odin gives me:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> G900A_OC4_Stock_Rooted_Firmware.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Added!!
<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> boot.img
<ID:0/004> NAND Write Start!!
<ID:0/004> system.img.ext4
<ID:0/004> FAIL! (Auth)
And the phone screen shows SECURE CHECK FAIL: system

It looks like I was able to resolve with the info in this post:
http://forum.xda-developers.com/att...phone-trying-to-downgrade-to-4-t3076706/page4
Sorry for not finding that sooner, usually my search-fu is pretty solid but my searches just weren't hitting that (or Muniz's other stock files available from androidfilehost).

T-Mobile G920T S6 downgrade 6.0.1 to 5.1

Hi, have a T-Mobile G920T S6 with 6.0.1 and want to downgrade to 5.11. Receiving the following odin FAIL error:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> G920FXXU2BOFJ_G920FOXA2BOFJ_G920FXXU2BOFJ_HOME.tar .md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin engine v(ID:3.1005)..
<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> sboot.bin
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
and following error on the phone:
"Sw rev check fail device 4 binary 2"
Tried (2) different original Samsung ROMs:
G920TUVU2COF6_G920TTMB2COF6_G920TUVU2COF6_HOME.tar.md5
on (2) different versions of Odin 10.+. No luck with any fixes in forums.
Any help would be greatly appreciated.
Thanks,
-Todd

cogancorp said:
Hi, have a T-Mobile G920T S6 with 6.0.1 and want to downgrade to 5.11. Receiving the following odin FAIL error:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> G920FXXU2BOFJ_G920FOXA2BOFJ_G920FXXU2BOFJ_HOME.tar .md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin engine v(ID:3.1005)..
<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> sboot.bin
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
and following error on the phone:
"Sw rev check fail device 4 binary 2"
Tried (2) different original Samsung ROMs:
G920TUVU2COF6_G920TTMB2COF6_G920TUVU2COF6_HOME.tar.md5
on (2) different versions of Odin 10.+. No luck with any fixes in forums.
Any help would be greatly appreciated.
Thanks,
-Todd
Click to expand...
Click to collapse
I thought I'd read that 6.0 was not going to prevent flashing back to 5.0 but I may be wrong. If I may inquire, what is your reasoning in wanting to go back to LP?

cwhiatt said:
I thought I'd read that 6.0 was not going to prevent flashing back to 5.0 but I may be wrong. If I may inquire, what is your reasoning in wanting to go back to LP?
Click to expand...
Click to collapse
Hi, thanks for the reply. All of the phones in our office are on 5.1 and we wanted to clone a new phone to save the time of setting up. We did a test run on 6.0.1 and the battery performance was horrible. Even on a rooted S6 phone with Greenify and most of the boatware frozen we got half the life as a 5.1. Let me know if you have any info on how to downgrade.
Thanks again for the note.
-Todd

coagncorp said:
Hi, thanks for the reply. All of the phones in our office are on 5.1 and we wanted to clone a new phone to save the time of setting up. We did a test run on 6.0.1 and the battery performance was horrible. Even on a rooted S6 phone with Greenify and most of the boatware frozen we got half the life as a 5.1. Let me know if you have any info on how to downgrade.
Thanks again for the note.
-Todd
Click to expand...
Click to collapse
Not sure of what MM setup you ran, but to each his own and if you like LP better by all means for what you like!
First question, you have a T model device correct? 920T or 925T?
I ask because I read that you mention a Tmo based device, but the tar file showing from your ODIN shot show a tar file meant for "F" device?
You will definitely want to make sure and use the correct file for your actual device! Maybe the shot was a generic one, IDK, but that is very important!
And to downgrade, I did this many times when MM first came out and I began my ROM update build.
Just check this post. Confirmed working and can be done in just a couple minutes.
The reason the odin fails at the sboot.img part is because if the screenshot is accurate and you tried flashing a F based tar on your T based device, it's because sboot.img is the bootloader and they aren't compatible with eachother.
Good luck and if you want the most customizable S6 rom for any device, check my OZOP v14 for LP and OZOP v5 is current MM build!
Hope the info works out for you!

coagncorp said:
Hi, thanks for the reply. All of the phones in our office are on 5.1 and we wanted to clone a new phone to save the time of setting up. We did a test run on 6.0.1 and the battery performance was horrible. Even on a rooted S6 phone with Greenify and most of the boatware frozen we got half the life as a 5.1. Let me know if you have any info on how to downgrade.
Thanks again for the note.
-Todd
Click to expand...
Click to collapse
Also, if you had a rooted S6, maybe try Deep Sleep battery saver over greenify. I have a flat S6 which is rooted and running stock firmware and Deep Sleep and I average about 17hours between charges with a 4hr 10min SOT.
Sent from my SM-G920T using XDA-Developers mobile app

stangdriver44 said:
Not sure of what MM setup you ran, but to each his own and if you like LP better by all means for what you like!
First question, you have a T model device correct? 920T or 925T?
I ask because I read that you mention a Tmo based device, but the tar file showing from your ODIN shot show a tar file meant for "F" device?
You will definitely want to make sure and use the correct file for your actual device! Maybe the shot was a generic one, IDK, but that is very important!
And to downgrade, I did this many times when MM first came out and I began my ROM update build.
Just check this post. Confirmed working and can be done in just a couple minutes.
The reason the odin fails at the sboot.img part is because if the screenshot is accurate and you tried flashing a F based tar on your T based device, it's because sboot.img is the bootloader and they aren't compatible with eachother.
Good luck and if you want the most customizable S6 rom for any device, check my OZOP v14 for LP and OZOP v5 is current MM build!
Hope the info works out for you!
Click to expand...
Click to collapse
Any ideas why i cannot downgrade, I perfer lollipop, and I have downgraded before, recently I jumped on your newest MM rom, and now I want to go back to Lollipop, but it wont allow me to flash the bootloader or modem, so I tried a whole firmware, and it still gives me this message

za33ck said:
Any ideas why i cannot downgrade, I perfer lollipop, and I have downgraded before, recently I jumped on your newest MM rom, and now I want to go back to Lollipop, but it wont allow me to flash the bootloader or modem, so I tried a whole firmware, and it still gives me this message
Click to expand...
Click to collapse
Just a noob question, what does apple has to do with android?

britchel said:
Just a noob question, what does apple has to do with android?
Click to expand...
Click to collapse
lol wow, I fixed it, wrong image attached.

Soft Bricked N920T hopefully just need a PIT file, but not entirely sure.

note 5 N920T
Successfully flashed Sick/Flu ROM about 2-weeks ago and it was (is) excellent. It was like getting an entirely new phone in battery life and speed. Long story short, tried to add fingerprint scans and bricked it--only to find out this was the one caveat to the ROM. So proceeded to reflash ROM while talking with family during Thanksgiving--I had really prepared the first time and felt pretty comfortable doing it again--but not being focused I ended up deleting the wrong information and soft bricking it.
At this juncture the only item still visible on the internal drive is TWRP. I AM able to boot into ODIN mode and the software does recognize my phone and I am also able to boot into TWRP. Other than that I do not have any OS on the phone at this time. I've downloaded the original firmware, but multiple attempts at flashing it have failed. Hours and hours of reading it seems that I may be missing a PIT file (?), but I haven't been able to confirm that is the actual problem or locate the specific N920T PIT file anyways. Seems like many of the discussion strings died in 2015
I can provide more details about the failure messages I read on ODIN and my phone during reflash attempts if anyone has the patience and time to help me. I spent essentially 13 hours straight all over the internet with no success and am reaching the point of throwing it into a fire

<ID:0/006> 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/006> Odin engine v(ID:3.1203)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> SingleDownload.
<ID:0/006> sboot.bin
<ID:0/006> cm.bin
<ID:0/006> FAIL!
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Attempts at flashing stock ROM.
Please does anyone have suggestions? I have scoured all prior threads in this regard and had no success

Wyattthomas said:
<ID:0/006> 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/006> Odin engine v(ID:3.1203)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> SingleDownload.
<ID:0/006> sboot.bin
<ID:0/006> cm.bin
<ID:0/006> FAIL!
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Attempts at flashing stock ROM.
Please does anyone have suggestions? I have scoured all prior threads in this regard and had no success
Click to expand...
Click to collapse
If you need the PIT file you can get it here but you'll have to create an account in order to see the download links.
http://www.sammobile.com/forum/showthread.php?t=30106
By the way don't use an old firmware, you have to use the very last firmware you were using before ever doing anything to it.

I did find the PIT file several hours ago and it doesn't appear to have been the problem. Its actually the only file that will "successfully" flash on the phone.
I've tried flashing the original android firmware that was on device originally as well as the most recent android firmware. Between each attempt the computer and phone were reset. No dice.

Wyattthomas said:
I did find the PIT file several hours ago and it doesn't appear to have been the problem. Its actually the only file that will "successfully" flash on the phone.
I've tried flashing the original android firmware that was on device originally as well as the most recent android firmware. Between each attempt the computer and phone were reset. No dice.
Click to expand...
Click to collapse
Have you tried booting into recovery and flashing a downloaded rom? You should be able to get into twrp and then flash from there... If you can't get into twrp then reflash twrp and try again.

MrMike2182 said:
Have you tried booting into recovery and flashing a downloaded rom? You should be able to get into twrp and then flash from there... If you can't get into twrp then reflash twrp and try again.
Click to expand...
Click to collapse
WELL-------IT flippin' worked!!!!!!!!!!!!!1
So I HAD also tried flashing the new ROMs with TWRP several times before but that wasn't working either. Later on I realized that I was off by a couple months on the latest Android 6.1.1. update and repeated ODIN flashes with new bootloaders/PIT files etc all continued to fail. Didn't think about trying the TWRP flash again
I am going out for a drink. This phone ruined my Thanksgiving, but for the records I'm immediately flashing the Sick as Hell ROM again. I know exactly how to do it in my sleep now. AVOID USING FINGERPRINT lock and it is otherwise an amazing ROM. Fast, Fast, Fast, and battery goes all damn day. Spotify hack is wonderful too.

Wyattthomas said:
WELL-------IT flippin' worked!!!!!!!!!!!!!1
So I HAD also tried flashing the new ROMs with TWRP several times before but that wasn't working either. Later on I realized that I was off by a couple months on the latest Android 6.1.1. update and repeated ODIN flashes with new bootloaders/PIT files etc all continued to fail. Didn't think about trying the TWRP flash again
I am going out for a drink. This phone ruined my Thanksgiving, but for the records I'm immediately flashing the Sick as Hell ROM again. I know exactly how to do it in my sleep now. AVOID USING FINGERPRINT lock and it is otherwise an amazing ROM. Fast, Fast, Fast, and battery goes all damn day. Spotify hack is wonderful too.
Click to expand...
Click to collapse
Create a full backup first so you have something to fall back on and restore if anything goes wrong again.

MrMike2182 said:
Create a full backup first so you have something to fall back on and restore if anything goes wrong again.
Click to expand...
Click to collapse
First thing I did. I've since backed it up about 3 more times...never again will I make that fatal error.

G870A, at&t pushed update, boot loop, tried odin and flash but rev check fail.

Wife goes to sleep, wakes up in morning phone is showing update status bar on phone and it is very warm. Fast forward an hour and we go to work, she picks up phone and it is in a boot loop with the Galaxy initial boot screen then reboots forever. Stock, never rooted, no problems until now. Take phone to ATT they claim this happens, and say just restore to factory. Wife says fine and brings device home as they said it will be 15 to 30 minutes to do it in the store. They said if that doesn't work take to best buy 40 mins from house (meh). I factory reset / wipe data, then wipe cache. Still boot loops. Read up a bit on here and most point to using Odin 3.09 downloaded two firmwares from different sites in case one was bad(G870AUCU1ANE4_G870AATT1ANE4_G870AUCU1ANE4_HOME.tar.md5). Put phone into download mode, open odin get ID com blue, load AP file previously mentioned (tried both incase one had an issue). Make sure Auto reboot and F. reset time are checked then hit start.
Odin reports:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> G870AUCU1ANE4_G870AATT1ANE4_G870AUCU1ANE4_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> SingleDownload.
<ID:0/005> aboot.mbn
<ID:0/005> NAND Write Start!!
<ID:0/005> FAIL! (Auth)
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Phone reports:
Odin mode
product name: SM-G870A
current binary: samsung official
system status: official
reactivation lock: off
knox warranty void: 0x0
Qualcomm secureboot: Enable (CSB)
AP SWREV: S1, T2, R1, A2, P1
Secure Download: Enable
UDC Start
SW REV CHECK FAIL : [aboot] Fused 2 > Binary 1
Tried multiple USB ports
Tried Factory white cable / Aukey cables, etc
Tried different computers
I'm sure it is something stupid I'm missing... Can you downgrade from 6.0.1 to 4.4.2? I read people were saying you couldn't but some people said you can. I just want a functional phone at this point so I can have my phone back as she stole mine until this is fixed. Suggestions?
So I guess a second fold question is there a way to block OTA updates if I can get this fixed? Because screw AT&T, and their inability to stand up behind the software updates they send out saying it's your problem phone isn't in warranty.
TL;DR Two days before xmas and ATT bends us over, corrupts firmware, I tried Odin with 4.4.2 and get failures, begging for insight on how to fix.
Thanks in advance, and Merry Christmas.

Svyn said:
Wife goes to sleep, wakes up in morning phone is showing update status bar on phone and it is very warm. Fast forward an hour and we go to work, she picks up phone and it is in a boot loop with the Galaxy initial boot screen then reboots forever. Stock, never rooted, no problems until now. Take phone to ATT they claim this happens, and say just restore to factory. Wife says fine and brings device home as they said it will be 15 to 30 minutes to do it in the store. They said if that doesn't work take to best buy 40 mins from house (meh). I factory reset / wipe data, then wipe cache. Still boot loops. Read up a bit on here and most point to using Odin 3.09 downloaded two firmwares from different sites in case one was bad(G870AUCU1ANE4_G870AATT1ANE4_G870AUCU1ANE4_HOME.tar.md5). Put phone into download mode, open odin get ID com blue, load AP file previously mentioned (tried both incase one had an issue). Make sure Auto reboot and F. reset time are checked then hit start.
Odin reports:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> G870AUCU1ANE4_G870AATT1ANE4_G870AUCU1ANE4_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> SingleDownload.
<ID:0/005> aboot.mbn
<ID:0/005> NAND Write Start!!
<ID:0/005> FAIL! (Auth)
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Phone reports:
Odin mode
product name: SM-G870A
current binary: samsung official
system status: official
reactivation lock: off
knox warranty void: 0x0
Qualcomm secureboot: Enable (CSB)
AP SWREV: S1, T2, R1, A2, P1
Secure Download: Enable
UDC Start
SW REV CHECK FAIL : [aboot] Fused 2 > Binary 1
Tried multiple USB ports
Tried Factory white cable / Aukey cables, etc
Tried different computers
I'm sure it is something stupid I'm missing... Can you downgrade from 6.0.1 to 4.2.2? I read people were saying you couldn't but some people said you can. I just want a functional phone at this point so I can have my phone back as she stole mine until this is fixed. Suggestions?
So I guess a second fold question is there a way to block OTA updates if I can get this fixed? Because screw AT&T, and their inability to stand up behind the software updates they send out saying it's your problem phone isn't in warranty.
TL;DR Two days before xmas and ATT bends us over, corrupts firmware, I tried Odin with 4.2.2 and get failures, begging for insight on how to fix.
Thanks in advance, and Merry Christmas.
Click to expand...
Click to collapse
Look in the Merry Early Christmas thread. Someone posted a link to an 870 tarball package you can downgrade to using Odin. Worked for me and I was on the latest MM release with my active.

Thanks, and sorry for late reply as it took a while to read the tons of pages on that thread. So on page 28, (Merry [early] Christmas Thread) I followed the active reset back to 5.1.1. Link here: (Active G870A tarball). So followed the directions and loaded BL / AP / CP / CSC in Odin3 v 3.11. Recieved the "pass" in 3:35 info below. Then reset the factory data and a cache reset. It started by loaded the typical Samsung splash, then went over to AT&T splash (white background) and would then power down. Would not boot the phone. Now the phone is really stuck in a boot loop and wont stop. I can't even get into recovery mode now so that made it worse... If I attempt to get into recovery mode it shows recovery mode in blue upper left corner, but just continually reboots. So I am guessing this is what is considered hard bricked instead of soft bricked... Anyone else have any suggestions?
Edit: left the phone for 10 minutes with no battery, added battery and it lets me go into boot loader again. Direct from phone:
Phone Info:
Android system recovery <3e>
LRX21T.G870AUCU2BOF3
Going to try to flash one more time and see if it changes anything.
Final Edit: No change, back to continual boot loop even on 5.1.1 (see above) Anyone else have any suggestions on how to get out of this boot loop? Going to leave the battery out and attempt to get back into bootloader (power / home / vol up).
<ID:0/004> 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..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<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> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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/004> Odin engine v(ID:3.1101)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<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> sbl1.mbn
<ID:0/004> rpm.mbn
<ID:0/004> tz.mbn
<ID:0/004> sdi.mbn
<ID:0/004> NON-HLOS.bin
<ID:0/004> boot.img
<ID:0/004> recovery.img
<ID:0/004> system.img.ext4
<ID:0/004> persist.img.ext4
<ID:0/004> modem.bin
<ID:0/004> Transmission Complete..
<ID:0/004> Now Writing.. Please wait about 2 minutes
<ID:0/004> Receive Response from boot-loader
<ID:0/004> cache.img.ext4
<ID:0/004> RQT_CLOSE !!
<ID:0/004> RES OK !!
<ID:0/004> Removed!!
<ID:0/004> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)

Svyn said:
Thanks, and sorry for late reply as it took a while to read the tons of pages on that thread. So on page 28, (Merry [early] Christmas Thread) I followed the active reset back to 5.1.1. Link here: (Active G870A tarball). So followed the directions and loaded BL / AP / CP / CSC in Odin3 v 3.11. Recieved the "pass" in 3:35 info below. Then reset the factory data and a cache reset. It started by loaded the typical Samsung splash, then went over to AT&T splash (white background) and would then power down. Would not boot the phone. Now the phone is really stuck in a boot loop and wont stop. I can't even get into recovery mode now so that made it worse... If I attempt to get into recovery mode it shows recovery mode in blue upper left corner, but just continually reboots. So I am guessing this is what is considered hard bricked instead of soft bricked... Anyone else have any suggestions?
Edit: left the phone for 10 minutes with no battery, added battery and it lets me go into boot loader again. Direct from phone:
Phone Info:
Android system recovery <3e>
LRX21T.G870AUCU2BOF3
Going to try to flash one more time and see if it changes anything.
Final Edit: No change, back to continual boot loop even on 5.1.1 (see above) Anyone else have any suggestions on how to get out of this boot loop? Going to leave the battery out and attempt to get back into bootloader (power / home / vol up).
<ID:0/004> 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..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<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> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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/004> Odin engine v(ID:3.1101)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<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> sbl1.mbn
<ID:0/004> rpm.mbn
<ID:0/004> tz.mbn
<ID:0/004> sdi.mbn
<ID:0/004> NON-HLOS.bin
<ID:0/004> boot.img
<ID:0/004> recovery.img
<ID:0/004> system.img.ext4
<ID:0/004> persist.img.ext4
<ID:0/004> modem.bin
<ID:0/004> Transmission Complete..
<ID:0/004> Now Writing.. Please wait about 2 minutes
<ID:0/004> Receive Response from boot-loader
<ID:0/004> cache.img.ext4
<ID:0/004> RQT_CLOSE !!
<ID:0/004> RES OK !!
<ID:0/004> Removed!!
<ID:0/004> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
Click to expand...
Click to collapse
Well...I'm sorry but I don't think I'm going to be any more help here. Seems to me from that log that it successfully flashed, which tells me that you may have a hardware problem going on. If I'm reading right, since the flash you did boot into recovery and perform a factory reset? That would have been my only other thought.

Thanks for the help, yes I did as soon as the first boot as per instructions. I even re-flashed, then upon first attempt to boot went to recovery menu and re-cleared cache and restore to factory to verify I didn't miss. Only thing I can think of is that upon the update it ran out of battery and corrupted a file somewhere good... I am at a miss because it was working perfect before (for the last 2 years +). Even did a factory restore mid this year to clear data and speed it up. If anyone else has any suggestions I'm all ears. Next to call ATT direct and see if they can do anything. BB said call ATT.

Svyn said:
Thanks for the help, yes I did as soon as the first boot as per instructions. I even re-flashed, then upon first attempt to boot went to recovery menu and re-cleared cache and restore to factory to verify I didn't miss. Only thing I can think of is that upon the update it ran out of battery and corrupted a file somewhere good... I am at a miss because it was working perfect before (for the last 2 years +). Even did a factory restore mid this year to clear data and speed it up. If anyone else has any suggestions I'm all ears. Next to call ATT direct and see if they can do anything. BB said call ATT.
Click to expand...
Click to collapse
The tarball should have you at a stock OF3 firmware, so it isn't corrupted if the flash was successful (which it appears to be). I'm going to have to agree that there is likely a hardware issue behind your problem.
As a final shot, you can try pulling the battery, with the battery out hold the power button for at least 30 seconds. Reinsert the battery, immediately boot into recovery, factory reset/clear cache, reboot again directly into download mode.
Now you can use my guide to flash the OF3 tarballs and get up and running.
If that doesn't work, I'd definitely lean towards hardware failure.
Good luck!

Thanks Joxer,
I called ATT today before and they pointed me to Samsung, which then pointed to me a local best buy Samsung kiosk. They (Samsung) were nice and accommodating I don't fault them at all. I fault ATT for pushing the update and ruining the phone. ATT claims if its less that 35% battery it wont update, but I don't know why they don't force the phone to be plugged in to prevent low battery from occurring. Or I wish there was a log somewhere you could read to find out what happened / caused the issue.
That is the guide I used before esp the bold part. I tried it twice and everything took but it just wont boot past att splash. The first time it attempts to boot it goes from Samsung splash, to a secondary splash then direct to the att white screen which gives false hope but after 25 minutes of sitting at this screen it still does nothing. When pulling the battery it goes right back to the boot loop. I also took the device to Samsung at BB today and they successfully flashed (after waiting 1.5 hrs for a download of the software) the newest firmware to the device. Same thing goes right to att white splash screen upon initial boot after a flash and then just hangs there. I would love to know what that firmware did to the hardware on the device (maybe overheat?), because previous to that it was working perfect.
Now we have to figure out if we go get a new phone (get bent over), or attempt to send it back into Samsung direct and get it fixed which we didn't have a ton of luck before where phones that came back seemed to have more problems than when they went in (referb shuffle), or to see if we can find a used one (ebay / clist).
Thanks everyone for the help.
Edit: Called att again, talked to a rep told them the steps I took and they waived (by charging me $112 for the warranty claim, then giving credit the next month). Sending a new phone out, so hopefully this phone works and arrives in good condition. Wish I had a better resolve for other people who might have searched and found this thread, but I imagine something got damaged from the heat in the phone. Thanks again everyone for the help and time.
IJoxer said:
The tarball should have you at a stock OF3 firmware, so it isn't corrupted if the flash was successful (which it appears to be). I'm going to have to agree that there is likely a hardware issue behind your problem.
As a final shot, you can try pulling the battery, with the battery out hold the power button for at least 30 seconds. Reinsert the battery, immediately boot into recovery, factory reset/clear cache, reboot again directly into download mode.
Now you can use my guide to flash the OF3 tarballs and get up and running.
If that doesn't work, I'd definitely lean towards hardware failure.
Good luck!
Click to expand...
Click to collapse

Svyn said:
Thanks Joxer,
I called ATT today before and they pointed me to Samsung, which then pointed to me a local best buy Samsung kiosk. They (Samsung) were nice and accommodating I don't fault them at all. I fault ATT for pushing the update and ruining the phone. ATT claims if its less that 35% battery it wont update, but I don't know why they don't force the phone to be plugged in to prevent low battery from occurring. Or I wish there was a log somewhere you could read to find out what happened / caused the issue.
That is the guide I used before esp the bold part. I tried it twice and everything took but it just wont boot past att splash. The first time it attempts to boot it goes from Samsung splash, to a secondary splash then direct to the att white screen which gives false hope but after 25 minutes of sitting at this screen it still does nothing. When pulling the battery it goes right back to the boot loop. I also took the device to Samsung at BB today and they successfully flashed (after waiting 1.5 hrs for a download of the software) the newest firmware to the device. Same thing goes right to att white splash screen upon initial boot after a flash and then just hangs there. I would love to know what that firmware did to the hardware on the device (maybe overheat?), because previous to that it was working perfect.
Now we have to figure out if we go get a new phone (get bent over), or attempt to send it back into Samsung direct and get it fixed which we didn't have a ton of luck before where phones that came back seemed to have more problems than when they went in (referb shuffle), or to see if we can find a used one (ebay / clist).
Thanks everyone for the help.
Edit: Called att again, talked to a rep told them the steps I took and they waived (by charging me $112 for the warranty claim, then giving credit the next month). Sending a new phone out, so hopefully this phone works and arrives in good condition. Wish I had a better resolve for other people who might have searched and found this thread, but I imagine something got damaged from the heat in the phone. Thanks again everyone for the help and time.
Click to expand...
Click to collapse
Glad to see you got it worked out, even if it did involve having to swap devices. I will say, I've been an AT&T customer for over 20 years and although I don't like their locked BL BS, their customer service has always been good.

Update:
Received new (refurbished) phone from warranty claim last week. Plug battery from old S5 active into new phone and had a warm welcomed boot loop. Interesting, then dug through the box and found a new back plate and battery. Put new battery in new phone works fine. Plug new battery into old phone (boot loop continues). I would venture to bet that the battery overheated when updating, then pooched something on the charging circuitry of the old phone along with the battery. New phone is up and running so far so good. Wife has phone back so I get mine back. Thanks again for the help! :good: