S5 Active (G870A) stuck at AT&T logo - AT&T Samsung Galaxy S 5

I was having issues with the WiFi on my phone so I made backups to the SD card, removed it and did a factory reset on the phone. I'm not sure what it was running at the time, but not lolipop. It now boots to AT&T logo and heats up until I pull the battery out (I've waited upwards of 30 mins). I tried flashing stock and 0F3 roms with odin and I get the error:
<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/003> Added!!
<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> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
And on the phone it says "SW REV CHECK FAIL : [aboot]Fused 2 > Binary 1"
I've tried flashing with PIT, tried flashing the boot loader, G870AUCU1ANE4_Full_Odin, and G870A_OC5_Bootloader, to no avail. I also downloaded Samsung Kies 3 and tried to do Firmware upgrade and initialization, which also didn't work. It comes up to Firmeware emergency recovery and asks for a recovery code (which I don't have). I've also tried from recovery mode to factory data reset and also tried to flash the roms from external SD. Is there anything else I can try or something I am missing that can get this working? Any help would be greatly appreciated.

Related

Samsung SM-G870A ATT Stuck in Downloading Mode - need help please

Issues began when I installed Lollipop on rooted phone. When flashing a custom rom it will not boot up. I cannot get to a recovery screen but can put it in download mode (Odin). I have downloaded the stock ATT rom and attempted to flash with odin but it fails everytime. I get the following on the screen.
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Binary 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.1100)..
<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> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1
I have updated the samsung drivers and do not know where to go from here. any help is appreciated.
Gdogius

Note 4 keeps booting into recovery

Hello all, I have looked everywhere and no one seems to be having the same problem as I have here.
So here is the problem: My note 4 keeps going into recovery and is giving me a few messages.
1) In the stock Android recovery that it boots into, on the bottom it displays "dm-verity verification failed..."
2) When clicking on "apply update from external storage", it gives me "Update from external storage is disabled"
Background:
In a previous post, I was trying to install Xposed framework and had an issue where it would not install. A friendly user suggested I install a different APK and flash a zip file through TWRP. I then installed TWRP through a play store app and booted into it. I installed the zip file, wiped data (including Dalvik) and the problem started.
So I tried flashing original N910T Rom through Odin and this is the log I got
BTW I am still able to access TWRP through holding Volume Up:Homeower but when phone boots up it goes into Android Recovery mode automatically, no bootloop. I tried clearing Data but that didnt help. Should I clear "System" through TWRP and reflash?
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N910TUVU1ANIH_N910TTMB1ANIH_N910TUVU1ANIH_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin engine v(ID:3.1005)..
<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> aboot.mbn
<ID:0/006> NAND Write Start!!
<ID:0/006> sbl1.mbn
<ID:0/006> rpm.mbn
<ID:0/006> FAIL! (Auth)
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Superdudekk said:
So I tried flashing original N910T Rom through Odin and this is the log I got
BTW I am still able to access TWRP through holding Volume Up:Homeower but when phone boots up it goes into Android Recovery mode automatically, no bootloop. I tried clearing Data but that didnt help. Should I clear "System" through TWRP and reflash?
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N910TUVU1ANIH_N910TTMB1ANIH_N910TUVU1ANIH_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin engine v(ID:3.1005)..
<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> aboot.mbn
<ID:0/006> NAND Write Start!!
<ID:0/006> sbl1.mbn
<ID:0/006> rpm.mbn
<ID:0/006> FAIL! (Auth)
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
you may need this
http://forum.xda-developers.com/not...f-g-c-t-w8-t3282641/post64569392#post64569392
Unfortunately I tried that but I found a solution! A helpful youtube video showed that with these new Samsung Phones, you can connect to Kie3 or Smart Switch and click "Emergency Software Recovery and Initialization", enter your model and serial number and the program will automatically wipe and flash OEM Samsung ROM onto the phone. Only bad thing is that you have to re-root the phone. Great solution for soft bricks.

Modem.bin fail in odin when trying to restore to 4.1.2

Recently I installed Clockwork Mod on my sisters Samasung Galaxy I8190N and attempted to flash lollipop on it. Much to my disappointment somewhere in the process I failed. Now when the phone boots I see the lollipop loading animation, but it goes no further during the boot. I can no longer access the Clockwork Mod recovery with up+power+home button. But can still access the download mode. So I tried to reinstall the 4.1.2 using odin, however with odin I get the following error when trying to flash using the PDA/AP:
Code:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Binary 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.1100)..
<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> boot.img
<ID:0/003> NAND Write Start!!
<ID:0/003> modem.bin
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
On the phone (in download mode) it says Custom Modem Binary installed.
Any help in getting my sisters phone back to how it was before she gave it to me (default 4.1.2) would be greatly appreciated!
Edit: I realise after posting that this would of been better in the troubleshooting forum, apologies for that.
Factory reset or flash original firmware from sammobile

Odin firmware flashing always fails

I have a Galaxy note 10.1 running kitkat 4.4.2 (GT-N8000)
Yesterday i was browsing the internet when suddenly the device decided to shut down and went on a restart boot loop where it would show the "Samsung galaxy note 10.1" screen for a while and then reboot and re-show the same screen
i have tried entering recovery mode but the tablet keeps restarting without end the only thing i can access is download mode
So recently i tried flashing using Odin but when ever i try to flash any file it shows this error
Code:
<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> Added!!
<ID:0/003> Odin engine v(ID:3.1203)..
<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> FAIL!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I have tried flashing a stock recovery so i can try and wipe the current data
I have tried to download multiple stock roms from jelly bean to kitkat which all ended up failing
I have tried flashing the tablet with a "Repair rom" which contains the BL AP CSC and Modem files
i think that if i can still access the download mode that there is some hope to recover?
Any solutions?
Thanks in advance.
If i posted this in the wrong section forgive me i have just started out

Phone hard bricked out of nowhere, need some advice on what to do next.

I was using an app to disable the Android APK Signature verification to install the Youtube Vanced APK. Phone rebooted and suddenly I no longer had a system partition. I've tried going through ODIN and flashing the CSC, HOME_CSC, AP, PIT, etc., and in most cases it simply hangs when it tries to write to a partition, then tells me "Complete(Write) operation failed.", I've also tried toggling the Re-Partition option in the Options tab of Odin, but that doesn't help either.
I want to try to do a nand erase, as nothing else seems to working, but I don't know the consequences of that. I can currently still boot into TWRP, as no flashing attempts in Odin were successful, and I've already backed up everything other than the System and System Image options to an SD card. If I do a nand erase, what should I do after?, should I just flash everything normally with that option checked? I'll also post a log from a failed Odin flash if that helps at all.
Code:
<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/003> Odin engine v(ID:3.1301)..
<ID:0/003> File analysis..
<ID:0/003> Total Binary size: 808 M
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> NAND Write Start!!
<ID:0/003> SingleDownload.
<ID:0/003> sboot.bin
<ID:0/003> param.bin
<ID:0/003> up_param.bin
<ID:0/003> cm.bin
<ID:0/003> keystorage.bin
<ID:0/003> recovery.img
<ID:0/003> modem.bin
<ID:0/003> Transmission Complete..
<ID:0/003> Now Writing.. Please wait about 2 minutes
<ID:0/003> Receive Response from boot-loader
<ID:0/003> modem_debug.bin
<ID:0/003> Transmission Complete..
<ID:0/003> Now Writing.. Please wait about 2 minutes
<ID:0/003> Receive Response from boot-loader
<ID:0/003> cache.img
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Daniel41550 said:
I was using an app to disable the Android APK Signature verification to install the Youtube Vanced APK. Phone rebooted and suddenly I no longer had a system partition. I've tried going through ODIN and flashing the CSC, HOME_CSC, AP, PIT, etc., and in most cases it simply hangs when it tries to write to a partition, then tells me "Complete(Write) operation failed.", I've also tried toggling the Re-Partition option in the Options tab of Odin, but that doesn't help either.
I want to try to do a nand erase, as nothing else seems to working, but I don't know the consequences of that. I can currently still boot into TWRP, as no flashing attempts in Odin were successful, and I've already backed up everything other than the System and System Image options to an SD card. If I do a nand erase, what should I do after?, should I just flash everything normally with that option checked? I'll also post a log from a failed Odin flash if that helps at all.
Code:
<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/003> Odin engine v(ID:3.1301)..
<ID:0/003> File analysis..
<ID:0/003> Total Binary size: 808 M
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> NAND Write Start!!
<ID:0/003> SingleDownload.
<ID:0/003> sboot.bin
<ID:0/003> param.bin
<ID:0/003> up_param.bin
<ID:0/003> cm.bin
<ID:0/003> keystorage.bin
<ID:0/003> recovery.img
<ID:0/003> modem.bin
<ID:0/003> Transmission Complete..
<ID:0/003> Now Writing.. Please wait about 2 minutes
<ID:0/003> Receive Response from boot-loader
<ID:0/003> modem_debug.bin
<ID:0/003> Transmission Complete..
<ID:0/003> Now Writing.. Please wait about 2 minutes
<ID:0/003> Receive Response from boot-loader
<ID:0/003> cache.img
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
"Total Binary size: 808 M"
You aren't flashing all the required files in odin. Total binary size should be between 4000 and 6000 M (Mb).
Frick_trump said:
"Total Binary size: 808 M"
You aren't flashing all the required files in odin. Total binary size should be between 4000 and 6000 M (Mb).
Click to expand...
Click to collapse
Yup, I was skipping out on the AP file since I didn't want to flash the system yet, only recovery because the real system ap wouldn't flash in another attempt.
For anyone reading in the future, I had to do a nand erase and reflash the latest version of the the system software (all files). An older version wouldn't work, then had to reset a few times to be able to toggle the OEM Unlock option.

Categories

Resources