[Q] Cannot install stock firmware - ODIN fail - Galaxy S 5 Q&A, Help & Troubleshooting

All,
As I noted in another thread, when I worked on my wife's new Galaxy S5, I let it upgrade to Android 5.0, then rooted it, then made some mistakes while restoring apps via Titanium Backup. In order to undo those mistakes, I want to roll back to the beginning and start over. To that end, I have been trying to reinstall stock firmware on the phone but I keep running into the same problem:
Code:
<ID:0/022> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> G900PVPU1ANCB_G900PSPT1ANCB_G900PVPU1ANCB_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/022> Odin v.3 engine (ID:22)..
<ID:0/022> File analysis..
<ID:0/022> SetupConnection..
<ID:0/022> Initialzation..
<ID:0/022> Get PIT for mapping..
<ID:0/022> Firmware update start..
<ID:0/022> aboot.mbn
<ID:0/022> NAND Write Start!!
<ID:0/022> FAIL! (Auth)
<ID:0/022>
<ID:0/022> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Based on reading here and elsewhere, I have tried the following:
Factory reset the phone
Verified that USB debugging is enabled and that allow remote lock is disabled
Ran Odin as Administrator
Use different versions of Odin (have tried 1.3, 1.85, 3.07, and 3.09)
Tried different firmware versions
Reinstalled Samsung drivers
Tried different computers and different USB cables
Regardless of what I have tried, I keep getting the same error.
The phone still works - I can boot it, so it is not bricked. I was also able to successfully re-root the phone (using the CF Auto Root approach). Based on my reading, it seems that replacing the PIT file is a next step to try, but it also seems that this is a fast way to killing a phone, so I am hesitant to try.
The phone in question is a Sprint Samsung Galaxy S5, SM-G900P. The kernel is currently Android 5.0, build version LRX21T.G900PVPU2B0D3. I would like to replace with with the stock 4.4.4 kernel (found here: http://stockroms.net/file/GalaxyS5/SM-G900P/G900PVPU1ANCB_G900PSPT1ANCB_SPR.zip). If replacing the PIT file is the next thing to try, can you please point me to the specific one to use? If not, can you suggest something else to try?
Thank you.

Same here
I'm having exactly the same issue. Trying to downgrade from BOD3 to kit kat 4.4.2 NE5 in order to unlock my S5 G900P.
Hope someone has a workaround for this.

Sorry dumb question, what did you use to root a 5.0 firmware? I thought towelroot only works on 4.4.2?

Starting with BOD3 u cant downgrade anymore
Hope this will work 4 u.....it worked on my G900P :
1. Install CWM with odin...Philz: http://downloadandroidrom.com/file/G...2-klte.tar.md5
2. Download Galaxy S5 Rooted Stock ROMs and kernel, flashable zips, and copy to your SD card
3. Reboot in recovery ...wipe data/cache/dalvik....install the zips(kernel and rom)
4.Reboot to system and enjoy ur downgrade
thanks to bto001 here: http://forum.xda-developers.com/sprint-galaxy-s5/general/solution-to-sim-unlock-od3-downgrade-t3128120

What finally worked was to install the same version of the stock firmware.

Related

[Q] [Q[ GT-I9505 odin fail while trying to restore 4.2.2 Firmware

Good Evening.
I had issues with my Rooted 4.2.2 (knox enabled firmware) and i wanted to unroot and flash my phone back to the Stock non Rooted Firmware.
Im well aware I cant Downgrade to a stock firmware With no Knox..So What i am trying to do is to flash the Official non rooted
I9505XXUDMH6_I9505OXXDMH4_I9505XXUDMH6_HOME (EUR) firmware That my phone had before it got Soft-brick.
I get to errors from Odin When i am doing the recovery Process
1) I Got this:
There is not PIT partition Table
so Ive Used a .pit file From this http://forum.xda-developers.com/showthread.php?t=2265477 Thread
and Ive retried the Process with CSB_signed_Fusion3_EUR_0325_V2.pit file But i got the Following Error:
2)
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9505XXUDMH6_I9505OXXDMH4_I9505XXUDMH6_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> sbl2.mbn
<ID:0/005> NAND Write Start!!
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/005> Removed!!
<ID:0/005> Added!!
So I am Pretty Much At a dead end with not knowing what else to do I would appreciate if anyone can Help me With this Issue
Thank you in advance.
P.S
I am using Odin 3.07 or 3.09 and i get the same issues
my Knox_warrinty_void is at 0x1
My Phone Model is GT-9505 region unlocked
also I have tried every Usb Port on My computer and used 2 different Cables 1 from My S4 and 1 from my S1
Unfortunately i don't have access to a different computer atm, but the above Process is done to a fresh install of Windows 7 SP1 PRO (x64) Partition on my Current PC.
If i check NAND erase all in odin and then Try to Flash The.pit along with Firmware will this help or it will make it worse?
Please any ideas ? :/
EDIT: I have finally found a solution
I went to the Following site [htt]p://forum.legija.net/showthread.php/69405-Boot-repair-Samsung-galaxy-S4-%28i9505-and-similar%29-via-USB-Cable and Downloaded the Attached file
the Ive connected my phone in Download mode and then run the program from the above site.
the Ive Run odin And i Flashed the .pit file alone without the firmware, Doing it this way have fixed the boot issue and i had my 4.2.2 Firmware and S4 up and running.
Then Ive upgraded to 4.3 (I9505XXUEMKF_I9505OXXEMK3_I9505XXUEMKF)
I've encountered a couple of issues and unstable boots and random restarts but ive managed to fix this by re partitioning PIT table and Flashing 4.3 firmware again. it seems Stable for the time being at least with no random crashes or reboots.
Dertheante said:
Please any ideas ? :/
EDIT: I have finally found a solution
I went to the Following site [htt]p://forum.legija.net/showthread.php/69405-Boot-repair-Samsung-galaxy-S4-%28i9505-and-similar%29-via-USB-Cable and Downloaded the Attached file
the Ive connected my phone in Download mode and then run the program from the above site.
the Ive Run odin And i Flashed the .pit file alone without the firmware, Doing it this way have fixed the boot issue and i had my 4.2.2 Firmware and S4 up and running.
Then Ive upgraded to 4.3 (I9505XXUEMKF_I9505OXXEMK3_I9505XXUEMKF)
I've encountered a couple of issues and unstable boots and random restarts but ive managed to fix this by re partitioning PIT table and Flashing 4.3 firmware again. it seems Stable for the time being at least with no random crashes or reboots.
Click to expand...
Click to collapse
Can you explain in more detail as to how you use those files to resurrect your i9505? The thread's description does not explain how to use the files: (galaxy_S4_9505.exe, bootloader + pit.bl)
The bootloader file is not recognized by odin and there is no indicator as to what the galaxy_S4_9505.exe file actually does.
Thanks much

[Q] Odin FAIL after Nand write start

Hey, guys. I left my G2 to go back to my GS4, and I'm having a bit of trouble. I'm trying to get back to an earlier firmware to gain root and flash custom recovery. Currently on NB1 firmware. TowelRoot does not work.
Anyway, I downloaded the stock ATT Firmware for my phone. UCUAMDL. When I go to Odin, Auto reboot and F reset time is checked. Re-Partition is not checked. Odin sees my phone. I hit PDA or AP and load my firmware file and hit start. Everytime, it fails after Nand write start.
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I337UCUAMDL_I337ATTAMDL_I337UCUAMDL_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>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1
I have tried v1.85, 3.04, 3.08, and 3.09. I have tried various USB ports on my computer. I have tried 2 different cables. I always run as admin. I have tried running in compatibility mode. Kies is not installed. I have uninstalled and reinstalled drivers.
Any help?
Your phone has a locked boot loader which prevents a full downgrade. If you are on stock NB1, you can adb sideload the NC1 OTA update file. The all things AT&T should have the link.
Sent from my SGH-I337 running GPE using Tapatalk
jmjoyas said:
Your phone has a locked boot loader which prevents a full downgrade. If you are on stock NB1, you can adb sideload the NC1 OTA update file. The all things AT&T should have the link.
Sent from my SGH-I337 running GPE using Tapatalk
Click to expand...
Click to collapse
If I sideload NC1, will I be able to install custom recovery and flash custom ROMs? Or will that require the MK2 downgrade to flash custom recovery after root?
N12X93R said:
If I sideload NC1, will I be able to install custom recovery and flash custom ROMs? Or will that require the MK2 downgrade to flash custom recovery after root?
Click to expand...
Click to collapse
You will be able to root using towelroot and install touchwiz based custom roms. There is a version of the google play edition that works (there are some known issues though).
The stock recovery cannot be replaced. We have a special recovery (this recovery is available during normal boot itself) called safestrap that can be used to flash the custom roms.
All things AT&T
jmjoyas said:
You will be able to root using towelroot and install touchwiz based custom roms. There is a version of the google play edition that works (there are some known issues though).
The stock recovery cannot be replaced. We have a special recovery (this recovery is available during normal boot itself) called safestrap that can be used to flash the custom roms.
All things AT&T
Click to expand...
Click to collapse
Oh, wow. What happened? I guess Samsung stuck it to us one final hard time. Made things so much harder. Thanks for the clarification.
Unfortunately you cant install Safestrap Recovery while on NC1. At least I haven't been able to at all. Really f'n hating this crappy updated phone I got from ATT as a replacement for my broken old on with the good bootloader.
You should be able to, once you set selinux to permissive mode. Towelroot was also updated to do the same.
Sent from my SGH-I337 running GPE using Tapatalk
N12X93R said:
Hey, guys. I left my G2 to go back to my GS4, and I'm having a bit of trouble. I'm trying to get back to an earlier firmware to gain root and flash custom recovery. Currently on NB1 firmware. TowelRoot does not work.
Anyway, I downloaded the stock ATT Firmware for my phone. UCUAMDL. When I go to Odin, Auto reboot and F reset time is checked. Re-Partition is not checked. Odin sees my phone. I hit PDA or AP and load my firmware file and hit start. Everytime, it fails after Nand write start.
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I337UCUAMDL_I337ATTAMDL_I337UCUAMDL_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>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1
I have tried v1.85, 3.04, 3.08, and 3.09. I have tried various USB ports on my computer. I have tried 2 different cables. I always run as admin. I have tried running in compatibility mode. Kies is not installed. I have uninstalled and reinstalled drivers.
Any help?
Click to expand...
Click to collapse
If you are on NB1 you can go back to MK2 to root or update to NC1 to use TowelRoot .
If you want to downgrade to MK2 and root please follow the steps in post 1, 2, 3 at here.
.

Soft Brick?? HELP!

Ok, so I rooted my phone using a method where i flashed an older kernel then used towelroot to root, and then flashed back to NJ4. All was going well, and i installed the safestrap recovery. Then, today i was tryin to install the CM12 for the S4, and i messed up where i put the files for this, so when i was in safestrap, it told me it failed. I hit reboot, and that is when my phone essentially 'soft bricked'. I tries to boot up, fails and goes into download mode. I tried pulling out the battery, tried to go into recovery, but i cant do it. I tried to flash 4.2.2. stock s4 firmware thru odin, but it kept saying "Can't open the serial(COM) port." and fails. I can't do anything right now, please help im panicking Dx
UPDATE: I tried again to flash stock and now when i try to boot it tells me "firmware upgrade encountered an issue.." now when i try to flash something it won't let me because odin fails and says
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I337MVLUAMDJ_I337MOYAAMDJ_I337MVLUAMDJ_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> boot.img
<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)
HELP
Someone wiser then me will probably come in but if you can get to download mode no big worries. The com port issue makes me think drivers or the USB port. I would try different USB port and potentially uninstall drivers and reinstall. I believe skip makes a tool kit for s4 today may help. Can you see the device in adb?
McAwesome said:
Someone wiser then me will probably come in but if you can get to download mode no big worries. The com port issue makes me think drivers or the USB port. I would try different USB port and potentially uninstall drivers and reinstall. I believe skip makes a tool kit for s4 today may help. Can you see the device in adb?
Click to expand...
Click to collapse
I updated my last post btw. Dumb question but...what is adb?
EDIT:
Got it. I found a link to a rootable 4.4.2 md5 file and flashed it and it worked!
Not compatible
Well CM12 CM11 no CM period is compatible with out S4 because of the locked bootloader and youre trying to use the wrong firmware in odin once you upgrade to 4.4.4 or 4.4.2 you can no longer downgrade and go down to 4.2.2 so stop trying that you need to either download NB1 or NI1 odin files and restore it that way thats if you havent completely messed up youre phone Good Luck!

[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

Looking to Root a Samsung Galaxy Tab E

I would like to know if there is a way to root my Galaxy Tab E, T377V, Android ver 7.1.1
I have tried a couple guides using Odin, Magisk, TWRP and CF Auto Root. None of those worked and all tries failed in Odin. I'm assuming it's because I can't find a version of TWRP for my model T377V.
If anyone has any help or suggestions I would greatly appreciate it.
Thanks
I have Odin version 3.14.1 installed on my PC along with the latest version of the Samsung USB drivers. I can boot my tablet into the download screen, then I connect it to the PC with a USB cable. I open Odin and it shows "added!", then I click the AP button and selected the CF-Auto_root file. Below is the info taken right from Odin....
<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..
<ID:0/004> Odin engine v(ID:3.1401)..
<ID:0/004> File analysis..
<ID:0/004> Total Binary size: 28 M
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> NAND Write Start!!
<ID:0/004> SingleDownload.
<ID:0/004> recovery.img
<ID:0/004> FAIL!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I assume I'm doing this correctly, especially after reading several guides. I thought I would post the info in case it helps anyone who tries to help me. I tried doing this with TWRP, but that failed also (I'm assuming because I can't find a file for my model T377V, even though most of the guides say you can root a Verizon version of the tablet).
dougdraws said:
I would like to know if there is a way to root my Galaxy Tab E, T377V, Android ver 7.1.1
I have tried a couple guides using Odin, Magisk, TWRP and CF Auto Root. None of those worked and all tries failed in Odin. I'm assuming it's because I can't find a version of TWRP for my model T377V.
If anyone has any help or suggestions I would greatly appreciate it.
Thanks[/QUOTE
I found this :
Root is working for the SM-T377V!
!! Great news! Your curiosity got me thinking about this again, and I got root working fully!
We finally have a working Root for the Samsung SM-T377V Galaxy Tab E 8.0" (Verizon)!
The trick is to use KingoRoot. (not Kingroot)
http://www.kingoapp.com/
First, downgrade the stock ROM to the very first version that Verizon shipped with. Build RU1AOL7, dated 2016.02.11. It's about 1.5gig, and I have no way to host such a large file, so search for it before you ask for mine. I found it pretty easily directly from Verzion. Use ODIN to flash it, yadda yadda yadda.
Then, use the Windows version of KingoRoot to actually root the tab. You will need to enable Developer Mode and USB Debugging, which KingoRoot walks you through if you don't know how. Be sure to uncheck the "Install recommended software" checkbox to avoid the bloatware they try to sneak by you.
After it finishes successfully, reboot the tab. During the boot, a message will pop up that says Android is Optimizing 1 new app. Badda boom, you're rooted!
Click to expand...
Click to collapse

Categories

Resources