[Q] OTA update keeps failing to install - Galaxy S 5 Q&A, Help & Troubleshooting

So I'm using the AT&T S5(SM-G900A) and I just flashed a clean sock firmware through odin. After I flashed it I wanted to install the new OTA but every time I try, it boots into recovery to install the update, but it only gets to like 31% and says update failed. Can anyone please help me figure out what's going on? I'm pretty sure it's the NG3 update because I'm on NCE right now.

I ended up getting it fixed thanks to muniz_ri. Here's his post that helped me get it fixed if anyone runs into this problem: http://forum.xda-developers.com/att-galaxy-s5/general/g900and3tong3keeprootota-zip-t2862299

Related

OTA Update Fails

Wtf got the ota update and its starts all good but then it hangs a yellow ! appears.. what can i do? i even did a factory reset i only was rooted and i took care of that.
zero313 said:
Wtf got the ota update and its starts all good but then it hangs a yellow ! appears.. what can i do? i even did a factory reset i only was rooted and i took care of that.
Click to expand...
Click to collapse
at least you are getting something OTA
Ditto
Unfortunately, I get the same thing. I was rooted, but I unrooted (not quite as thoroughly as you did, as I only used the "Unroot" option, but we got the same results). Wonder if it is something wrong with the update...
seanfrisbey said:
Unfortunately, I get the same thing. I was rooted, but I unrooted (not quite as thoroughly as you did, as I only used the "Unroot" option, but we got the same results). Wonder if it is something wrong with the update...
Click to expand...
Click to collapse
Did you change ANYTHING when rooted? Did you freeze, rename, modify or delete ANY of the files in the original ROM in any way, shape or form?
Same thing here
When I bought this device 3 weeks ago, I rooted it with z4root. Not too long after an update disabled z4root on the tablet.
I thought no big deal, but then today comes and I the OTA update won't work.
Anyone more experienced than me have any ideas of how to get this update applied properly?
Me too. Update failed to install. Not sure why. I have also tried unrooting.
FloatingFatMan said:
Did you change ANYTHING when rooted? Did you freeze, rename, modify or delete ANY of the files in the original ROM in any way, shape or form?
Click to expand...
Click to collapse
I'm confused, if I froze an application, didn't unfreeze it but did a factory reset...wouldn't that resolve the issue?
ok so i woke up this morning and my a500 notified me the there was an update available so as you can imagine I was very happy to finally have this, so i updated and when it was done it said update successuful but when I checked it still said 3.01......WTF
Not rooted ever..
Those interested in getting back their OTA, properly backing up their original ROMS or restoring them, please follow the tutorials in this thread:
Going back to stock TUTORIAL
Be helpful and provide your firmware if you have a backup so we can build a database for those who don't.
Be sure to report what is working and what is not working for you once you've tried the tutorials!
Unlike the 14 threads on these matter I take the responsibility as OP to upgrade my original post as firmwares and new info becomes available.
Let's create a focused troubleshooting and tutorial thread,
Thanks.
I'm rooted via gingerbreak and the update worked fine while still rooted. It did break root. Just had to re-apply gingerbreak and all is good, back to root with latest update.
gingerbreak worked with official 3.1 ?
it didn't work with 'leaked' 3.1 ?
OTA
Ok after long night and hours of research i found out a lot.
1 if you have modded ad hoc in wpa_supplicant file recover the original file
2 if you have modded the phone.apk and telephoneyprovider.apk to save battery this is the reason why you won't get the update.
i put these files back and instantly got an update, i mean the exact second i set those back
i can't believe this my updates keep failing to install. FING POS i tried everything, factory reset
i have tried everything, even factory reset, it fails while installing after reboot
acer support are a bunch of retards, they don't even know they sell tablets????????
need help i can't upgrade, it fails every time
does anyone know where the install logs are
the log is \cache\recovery\last-log
Oklahoma City, OK noon CST
First attempt failed:
Changed the wpa_supplicant back to original and all went smooth the second time
I never changed anything and it failed.
**Edit: I rebooted my devices and left it completely alone after unzip and it rebooted into recovery mode and seems to be installing **
I had the same problem, It was pretty disheartening.... but I unrooted my device, re-booted and tried again and SUCCESS!!!
But now I can't get it to re-root using gingerbreak... HELP!
SUCCESS!
Ok. I got OTA update 4.010.08 (122.71 MB) this morning. It failed.
So I unrooted my device. Re-started it and tried again... SUCCESS!
I tried using Gingerbreak to root it again. FAIL!
So I used this: http://forum.xda-developers.com/showthread.php?t=1138228
SUCCESS!
Hope this helps those of you who are having problems.
No need to unroot nor go to stock.
I had the same issues. Then I simply used Acer Recovery to install stock recovery and everything worked fine.
Ceger
Acer Recovery?
Did Acer Recovery come with the tablet?
I tried the update numerous times over the last 4 days. Most of the time the download would fail, which I put down to my slow internet connection and overloaded Acer servers. But about 5 times it would finish downloading and then error out on install with a message about the update being invalid. I tried rebooting several times during this process. I have never rooted the tablet and only have a few apps installed as it was a recent purchase.
Finally it worked when I ejected the external SD card and rebooted. It may be a coincidence, but anyone else who gets the "invalid update" warning during install on an unrooted device may wish to try this prior to the download/install.

[Q] Nexus 7 update help

Hi Everyone,
I am currently running android 4.3(JWR66v) I flashed it using fastboot, so it is clean.
After that I rooted it and installed CWM v6.3.6 and BusyBox pro.
That is the only changes I did to my device,everything else is stock.
2 day ago I got a system update notification, looking in the cache folder I found this :
"8b2531d9d9a686c7dcf347513ce8141d59a251c6.signed-nakasi-JWR66Y-from-JWR66V.8b2531d9.zip"
I confirmed the reboot/Install but it failed with the classic (Status 7) I do not understand what is going on ?
Do I need flash my device again with a factory to get the update to install ?
I had the same setup since I bough this device last year and It had no trouble what so ever upgrading before(Unlocked+rooted+CWM)
This is supposed to be a nexus device but it sure doesn't act like one,
Can some one please help ?
Had the same problem going from 4.2.2 to 4.3. Same as you, stock rooted, but had TWRP as my recovery. I did go back to stock recovery, but no go. Ended up doing clean install. However, going from JWR66V to JWR66Y, I had no problem. Took OTA without even having to install stock recovery.
You must not be as stock as you think. My guess is you must have altered something in system that they are checking on. Hope someone with more knowledge is able to help you out because it is a PITA to have to clean install for every update. Good luck.

No stock recovery on stock 4.4.2 OTA

Hey guys.
So I recently went back to stock using the KDZ method. Once on stock, I took a couple of OTAs to get to 4.4.2. Now I want to root, so I picked up ioroot25 and tried it out.
The problem is that when I go through the process in ioroot, the phone reboots to go into recovery and all that happens is I get a screen with the little android icon knocked over, and ioroot says device not found.
Anybody have any ideas that might help? It'd be much appreciated. Thanks!
Anybody have any idea? It's really frustrating.

ODIN Hangs on system.img.ext4 step when flashing SM-G900P

Good afternoon -
Hopefully a quick question. I've been unable to find a clear and concise answer to this question so far.
TL;DR version: When Trying to flash stock firmwares, ODIN starts the flash but hangs on system.img.ext4 install. No error, just hang. Eventually I killed and tried again a few times (with different rom files too), same result. Left flash running overnight, same result. Was able to flash TWRP without issue. Please help! Not sure what I'm doing wrong here.
Detailed version:
I wanted to put Android 6.0 or 6.0.1 on my Sprint Galaxy S5 (SM-G900P). Previously I was running BOG1 I believe (Can't remember for sure) It was rooted so I couldn't use install via OTA Update. I made a backup of my previous rom So /hopefully/ I can go back if necessary. Here's the issue right now:
I downloaded the ...PCA Build from here: galaxys5update.com/galaxy-s5-stock-firmware.
Then wiped dalvik and regular cache, then put phone in download mode, and ran ODIN 3.XX.X (I tried a number of versions, 3.10.something, 3.07.something, 3.11.something (sorry for the lack of complete info, not in front of that computer right now so I don't have the exact details).
I loaded the Tar.md5 file into the proper spot in ODIN, then start the install. It starts running, I can see the progress in the information window. Then it gets to "system.img.ext4" and appears to freeze. I've let it go for 20-30 mins before disconnecting. I tried a different rom file and same result, ODIN just hangs. No error, just a hang. I left it running a flash overnight and it was still stuck at system.img.ext4 when I woke up this morning.
I was able to successfully flash TWRP but that's not really the solution.
Any help you might have would be greatly appreciated.
Thanks,
C
Update: I flashed a nandroid backup from right before I started all this. It installed fine. I'm back to my Android 5.0. However, WIFI has stopped working, and the phone stops responding a little bit after the screen turns off, requiring a battery pull and reboot. Additionally, making or accepting calls causes a reboot.
Another update: Tried KIES to install new Firmware through normal update method, it starts but then hangs at 3%.
So any help you might have would be really appreciated!
same problem
I have the same problem. Did you ever find a solution to the system hang on that file problem???
cjs678 said:
Good afternoon -
Hopefully a quick question. I've been unable to find a clear and concise answer to this question so far.
TL;DR version: When Trying to flash stock firmwares, ODIN starts the flash but hangs on system.img.ext4 install. No error, just hang. Eventually I killed and tried again a few times (with different rom files too), same result. Left flash running overnight, same result. Was able to flash TWRP without issue. Please help! Not sure what I'm doing wrong here.
Detailed version:
I wanted to put Android 6.0 or 6.0.1 on my Sprint Galaxy S5 (SM-G900P). Previously I was running BOG1 I believe (Can't remember for sure) It was rooted so I couldn't use install via OTA Update. I made a backup of my previous rom So /hopefully/ I can go back if necessary. Here's the issue right now:
I downloaded the ...PCA Build from here: galaxys5update.com/galaxy-s5-stock-firmware.
Then wiped dalvik and regular cache, then put phone in download mode, and ran ODIN 3.XX.X (I tried a number of versions, 3.10.something, 3.07.something, 3.11.something (sorry for the lack of complete info, not in front of that computer right now so I don't have the exact details).
I loaded the Tar.md5 file into the proper spot in ODIN, then start the install. It starts running, I can see the progress in the information window. Then it gets to "system.img.ext4" and appears to freeze. I've let it go for 20-30 mins before disconnecting. I tried a different rom file and same result, ODIN just hangs. No error, just a hang. I left it running a flash overnight and it was still stuck at system.img.ext4 when I woke up this morning.
I was able to successfully flash TWRP but that's not really the solution.
Any help you might have would be greatly appreciated.
Thanks,
C
Click to expand...
Click to collapse
I don't know if I have ever gotten that error before. You can try to update your samsung drivers on your computer, and make sure you are using the cable your phone came with. It sounds silly, but I have had issues with ODIN if I am not using the original cable.

Bricked my phone: Can anybody help?

I upgraded the firmware on my phone to install Bad Boyz Oreo ROM. My phone did not like it. It sent the phone into a constant bootloop.
Since that time, I've tried everything. I'm not a noob to this. I was able to use a Sprint Nougat RUU, which installed successfully with no errors, but it stayed on the HTC green and white screen. No bootloop, just stayed on the screen. I installed TWRP, and flashed an older version of Viper ROM. It's just stuck ont he Venom logo. Not doing anything.
I'm downloading another RUU at the moment. Not sure it's going to do anything.
Can anybody get me to a point where the phone works again? I can't upgrade until July, and I am using my old M8 till I get this fixed.
Thanks!
Mother****er! I just installed Bad Boyz again, using the Magisk and it's booting. What's the issue using the SuperSU optionk
Can U plz provide a link of the same?
Hi there... i am too stuck on a bootloop since i tried updating to Oreo 8.0. Now i have got access only to the download mode. Would appreciate if u can guide how to get rid of the bootloop

Categories

Resources