I'm on 4.2.2 right now, rooted and happy. I bought SuperSU Pro to get the "survival mode" option, and checked it. Now I'm trying to do the 4.3 OTA upgrade.
It downloads fine, and during the install, the android with the spinning blue globe appears, and the bar fills up about 10% of the way then the phone reboots. It refuses to update, and upon boot up it says "Software Update Failed!". No error messages, codes, or anything to search by.
Any ideas?
I'm trying to keep root with my upgrade to 4.3
Wiltron said:
I'm on 4.2.2 right now, rooted and happy. I bought SuperSU Pro to get the "survival mode" option, and checked it. Now I'm trying to do the 4.3 OTA upgrade.
It downloads fine, and during the install, the android with the spinning blue globe appears, and the bar fills up about 10% of the way then the phone reboots. It refuses to update, and upon boot up it says "Software Update Failed!". No error messages, codes, or anything to search by.
Any ideas?
I'm trying to keep root with my upgrade to 4.3
Click to expand...
Click to collapse
just flash 4.3 firmware ftf file through flashtool....
Wiltron said:
I'm on 4.2.2 right now, rooted and happy. I bought SuperSU Pro to get the "survival mode" option, and checked it. Now I'm trying to do the 4.3 OTA upgrade.
It downloads fine, and during the install, the android with the spinning blue globe appears, and the bar fills up about 10% of the way then the phone reboots. It refuses to update, and upon boot up it says "Software Update Failed!". No error messages, codes, or anything to search by.
Any ideas?
I'm trying to keep root with my upgrade to 4.3
Click to expand...
Click to collapse
Have you flash the Recovery to your 4.2.2 version? If yes the OTA will not install
One more point, you cannot keep your root when you update from 4.2.2 to 4.3 via OTA too.
You can't update via OTA when rooted for some "strange" reason. You need to do that with PC Companion. I couldn't do that even when I was updating firmware in 4.2.2.
Related
Verizon 6 here...got prompted to update. Downloaded and was ready for the install and reboot. Phone rebooted. Still 5.0? And device up to date. How can i redownload? Please help
StrangeTimes said:
Verizon 6 here...got prompted to update. Downloaded and was ready for the install and reboot. Phone rebooted. Still 5.0? And device up to date. How can i redownload? Please help
Click to expand...
Click to collapse
Do you have a custom recovery and/or rooted? If so, the OTA fails. The reminder will probably come back in a day or so.
Same thing happened to me. I received the notice literally seconds after rooting and flashing custom recovery. I tried it anyway for ****s and grins, and it failed of course. After rebooting post failure, mine also stated it was up to date.
I did it the hard way, flashed system and radio using fastboot. All up to date now. :good:
Bone stock no root or anything. Would hard reset work? Or will it reprompt soon?
It's hard to say exactly, but given the image was just posted by Google today, and OTAs are already pushing out, you may see it again tomorrow.
I cleared the framework. Still nothing.
Connect to a charger, it reappear and I was able to update. BTW make sure you on WiFi
So wifi connect to charger and clear framework. Will try. Anyone else have solutions?
Yet to repop update. Still getting the up to date...
StrangeTimes said:
Verizon 6 here...got prompted to update. Downloaded and was ready for the install and reboot. Phone rebooted. Still 5.0? And device up to date. How can i redownload? Please help
Click to expand...
Click to collapse
Same thing is happening on my Nexus 7 2013. I've tried it 5 different times.
Sent from my SM-N900V
Same here... fully stock and unrooted Nexus 6 with VZW sim. Got an update notification. Tried to update and the notification just went away and now says I'm up-to-date even thought the update never installed... still on 5.0.
Any solutionsnyet? Hard reset phone does nothing btw
Man... Was really hoping to wake up to the update popping up again. No dice.
att nexus 6 failed 5.0.1
Got notification on att nexus 6 completely stock, for the update to 5.0.1, after accepting the install and agreeing for the restart, it never restarted or updated anything. Still on 5.0. Checking for updates shows that i'm "up to date" and attempting to side load the update via ADB fails.
Got the ota update just now. Install was successful.
Today my XT1068 offered me the 22.26.1.en.GB update, but it's failing to install.
The phone reboots and attempts to install the update. The progress bar gets to approximately 1/4 to 1/3 of the way across before a red triangle appears and the phone reboots back to KitKat.
My phone was rooted (using SuperSU), but I used SuperSU's built-in clean-up feature to unroot my phone before applying the Lollipop update.
The bootloader is unlocked, but the recovery is stock; I did not install a custom recovery but instead booted TWRP temporarily to install SuperSU.
I'm comfortable fiddling with adb and fastboot, and with digging around the filesystem. Any suggestions of where I can look to find any error messages which might shed some light on why the update failed? Could the failure be related to the previous rooting of my phone, or could something else be breaking the update?
@Loganberry
Have you modified /system files in any way?
If yes you have to restore them back.
If nothing helps, with unlocked bootloader it's propably much faster to just flash your stock firmware again and do ota than to search why it doesn't work.
I can confirm that ota update can be performed on rooted phone .I was thinking that is not possible but I was curious and tried.
I was on unlocked bootloader and rooted KK , german firmware 21.85.23 with instaled xposed framework and gravity box.
Update was successful without any error and for now everything work ok.
Loganberry said:
Today my XT1068 offered me the 22.26.1.en.GB update, but it's failing to install.
The phone reboots and attempts to install the update. The progress bar gets to approximately 1/4 to 1/3 of the way across before a red triangle appears and the phone reboots back to KitKat.
My phone was rooted (using SuperSU), but I used SuperSU's built-in clean-up feature to unroot my phone before applying the Lollipop update.
The bootloader is unlocked, but the recovery is stock; I did not install a custom recovery but instead booted TWRP temporarily to install SuperSU.
I'm comfortable fiddling with adb and fastboot, and with digging around the filesystem. Any suggestions of where I can look to find any error messages which might shed some light on why the update failed? Could the failure be related to the previous rooting of my phone, or could something else be breaking the update?
Click to expand...
Click to collapse
flash the GB 4.4.4 in my signature then try to update OTA again
dpdp73 said:
@Loganberry
Have you modified /system files in any way?
If yes you have to restore them back.
If nothing helps, with unlocked bootloader it's propably much faster to just flash your stock firmware again and do ota than to search why it doesn't work.
Click to expand...
Click to collapse
reefuge said:
flash the GB 4.4.4 in my signature then try to update OTA again
Click to expand...
Click to collapse
Yeah, I'd forgotten about Busybox and a couple other apps which modifed /system. Reflashing from scratch was the easier option.
I flashed GB 4.4.4 as advised and the Lollipop update then applied without any problems. Thanks for the assistance.
I currently have a rooted stock 4.4.4 on my S5 (G900A) along with xposed framework. Two days ago, AT&T downloaded the Lollipop OC4 rom and since then it has been prompting me to let it install the downloaded update. I have been telling it not to since from what I gathered I will be losing root and there is currently no way to root the OTA OC4 for G900A.
Problem: Today, the OTA update popped up again and said it will automatically install the update in 30 seconds whether or not if I want it, which prompted me to turn the phone off. Turning the phone back on results in the same results in the same autoupdate in 30 seconds prompt in less than a minute after the boot up. How can I stop the OTA from pushing itself through at this point so I can stay on the 4.4.4 with root. Note that the phone is still on warranty and the Knox is not tripped and I don't want to trip it either.
I have reversed the Xposed overwrite for the status so now the phone is no longer showing official but custom instead both during the power up and in the device menu. I have also rebooted into recovery and cleared cache. Neither one of them prevented the OTA from telling me that it will auto update in 30 seconds at the following reboot.
Can someone help me stop this OTA so I can keep my current 4.4.4 with root?
Thanks
YasharF said:
I currently have a rooted stock 4.4.4 on my S5 (G900A) along with xposed framework. Two days ago, AT&T downloaded the Lollipop OC4 rom and since then it has been prompting me to let it install the downloaded update. I have been telling it not to since from what I gathered I will be losing root and there is currently no way to root the OTA OC4 for G900A.
Problem: Today, the OTA update popped up again and said it will automatically install the update in 30 seconds whether or not if I want it, which prompted me to turn the phone off. Turning the phone back on results in the same results in the same autoupdate in 30 seconds prompt in less than a minute after the boot up. How can I stop the OTA from pushing itself through at this point so I can stay on the 4.4.4 with root. Note that the phone is still on warranty and the Knox is not tripped and I don't want to trip it either.
I have reversed the Xposed overwrite for the status so now the phone is no longer showing official but custom instead both during the power up and in the device menu. I have also rebooted into recovery and cleared cache. Neither one of them prevented the OTA from telling me that it will auto update in 30 seconds at the following reboot.
Can someone help me stop this OTA so I can keep my current 4.4.4 with root?
Thanks
Click to expand...
Click to collapse
Just freeze the software update thing with TiBu
Sent from my SM-G900A using Tapatalk
If your rooted I'm pretty sure the ota will fail anyways...then do like @Rakuu said and freeze the Att software update app so it doesn't bug you about the update.
Rakuu said:
Just freeze the software update thing with TiBu
Sent from my SM-G900A using Tapatalk
Click to expand...
Click to collapse
What is the name of the software update thing? Exact name? Assuming that it may not fail and may push through I only get a 30 sec window to do it and reboot.
nutt_case said:
If your rooted I'm pretty sure the ota will fail anyways...then do like @Rakuu said and freeze the Att software update app so it doesn't bug you about the update.
Click to expand...
Click to collapse
I don't want to risk finding out the hard way that it pushed through. What exactly is the name of the item that I need to freeze?
YasharF said:
I don't want to risk finding out the hard way that it pushed through. What exactly is the name of the item that I need to freeze?
Click to expand...
Click to collapse
Therws no finding out the hard way, it will fail. Its called att software update or something, the icon is a white and red arrow pointing opposite directions, i'd check for you but im on a tmobile rom so i dont have it. Just turn on airplane mode and it should prevent it from downloading.
Sent from my SM-G900A using Tapatalk
Rakuu said:
Therws no finding out the hard way, it will fail. Its called att software update or something, the icon is a white and red arrow pointing opposite directions, i'd check for you but im on a tmobile rom so i dont have it. Just turn on airplane mode and it should prevent it from downloading.
Sent from my SM-G900A using Tapatalk
Click to expand...
Click to collapse
You missed my question. The update has already downloaded and gone through 2 days of grace period. Now it is giving 30 sec to force install itself, not to force download. I know the download fails if the device is in custom state instead of official state, and I am at a point beyond your experience.
Can someone with AT&T Rom please help me identify what exactly the item that I need to freeze is called? Thanks.
YasharF said:
Can someone with AT&T Rom please help me identify what exactly the item that I need to freeze is called? Thanks.
Click to expand...
Click to collapse
Att software update
@Rakuu is correct though, if your status is custom update will fail.
nutt_case said:
Att software update
@Rakuu is correct though, if your status is custom update will fail.
Click to expand...
Click to collapse
Sweet! Thank you I just did a quick reboot and with Titanium Backup Pro froze it, and did a reboot. Although the force update gave me the 30 sec warning while I was trying to navigate Titanium Backup, I did not get a notification after freezing it and rebooting. Now, I got to play the waiting game and hope that one of the devs can figure out how to root OC4 / stock Lollipop on S5 G900A.
YasharF said:
Sweet! Thank you I just did a quick reboot and with Titanium Backup Pro froze it, and did a reboot. Although the force update gave me the 30 sec warning while I was trying to navigate Titanium Backup, I did not get a notification after freezing it and rebooting. Now, I got to play the waiting game and hope that one of the devs can figure out how to root OC4 / stock Lollipop on S5 G900A.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=3076803
If your looking to get on rooted 5.0 then you can follow the above thread...it will also not update the bootloader so you can still downgrade if needed.
The update will not install if you're rooted, but the process is just annoying as ever. If you've frozen the updater apk with Titanium BackUp then you'll be fine. I froze that back in October of 2014 and haven't been bothered since. Every so often a security notice flashes in the statusbar but nothing else.
I just received the OTA update notice from my Xperia Z to version 10.6.A.0.454
I have downloaded it and tried to do the update, but it just failed.
I can see my phone can enter the setup screen with the Android robot icon, but when the progress bar starts to run, it just simply reboot itself.
My current version is 10.5.1.A.0.292, rooted, I can't really remember which tool i used to root my device, but I am sure I was not using flashtool and never use that.
Is there any log i can see what caused the fail or what can I do to upgrade?
PCC is not a choice at the moment since my computer don't have enough space in C drive to perform the phone update, but i will be able to try 10 hours later.
FelixWan said:
I just received the OTA update notice from my Xperia Z to version 10.6.A.0.454
I have downloaded it and tried to do the update, but it just failed.
I can see my phone can enter the setup screen with the Android robot icon, but when the progress bar starts to run, it just simply reboot itself.
My current version is 10.5.1.A.0.292, rooted, I can't really remember which tool i used to root my device, but I am sure I was not using flashtool and never use that.
Is there any log i can see what caused the fail or what can I do to upgrade?
PCC is not a choice at the moment since my computer don't have enough space in C drive to perform the phone update, but i will be able to try 10 hours later.
Click to expand...
Click to collapse
ota dosnt work on rooted and unlocked bl devices, try to unroot and do a full reset and then try to update again
usman_fareed said:
ota dosnt work on rooted and unlocked bl devices, try to unroot and do a full reset and then try to update again
Click to expand...
Click to collapse
I don't know if my device is unlocked.
But in this case, can I update using PCC?
if not, i guess i will just use flashtool...
FelixWan said:
I don't know if my device is unlocked.
But in this case, can I update using PCC?
if not, i guess i will just use flashtool...
Click to expand...
Click to collapse
if you have recovery installed then the zip from here http://forum.xda-developers.com/xperia-z/general/stock-c6602-customized-10-6-0-454-t3114152 its pre rooted
thanks for the suggestions
but the question is kind of fixed by update using PCC...
another problem of overheat comes out after update though ~"~
I have (or had) an AT&T branded S5 that was previous rooted and running Safestrap (I don't recall the BL version). Due to some EXTREME idiocy on my part, I took an OTA update two days ago, which updated and synched everything to G900AUCU2ANG3.
Naturally, this borked root. But there's some weirdness going on. Even after the OTA update, the phone's device status still says "Custom". And I still see the custom text when the phone boots. Is this Knox related?
Further oddness is that the phone keeps trying to pull down a second OTA update that looks identical to the first based on the filesize (over 400 MB). It goes through the motion, boots into recovery, and starts installing this second update, but stops partway through. Upon rebooting, the phone tells me the update was interrupted and can't be installed.
I realize I may never get root back, but I'm alarmed the phone's status still says "Custom" and that it's trying (and failing) to install this second OTA update.
I've tried factory resetting the phone, both within KitKat and via recovery, but these issues remain. Should I just reapply NG3 via Odin?
Thanks in advance!
fleggett1 said:
I have (or had) an AT&T branded S5 that was previous rooted and running Safestrap (I don't recall the BL version). Due to some EXTREME idiocy on my part, I took an OTA update two days ago, which updated and synched everything to G900AUCU2ANG3.
Naturally, this borked root. But there's some weirdness going on. Even after the OTA update, the phone's device status still says "Custom". And I still see the custom text when the phone boots. Is this Knox related?
Further oddness is that the phone keeps trying to pull down a second OTA update that looks identical to the first based on the filesize (over 400 MB). It goes through the motion, boots into recovery, and starts installing this second update, but stops partway through. Upon rebooting, the phone tells me the update was interrupted and can't be installed.
I realize I may never get root back, but I'm alarmed the phone's status still says "Custom" and that it's trying (and failing) to install this second OTA update.
I've tried factory resetting the phone, both within KitKat and via recovery, but these issues remain. Should I just reapply NG3 via Odin?
Thanks in advance!
Click to expand...
Click to collapse
What does your "android version" say in settings. If your still on 4.4.2 you can downgrade bank to nce and reroot with towel root.
dirtydodge said:
What does your "android version" say in settings. If your still on 4.4.2 you can downgrade bank to nce and reroot with towel root.
Click to expand...
Click to collapse
Yes, I'm still on 4.4.2. Like I wrote in my OP, though, I'm VERY concerned that this second OTA update keeps failing. I'm also perplexed as to why the device is still in some sort of custom state since I thought taking the OTA update would, in essence, reset everything except user data.
Is my phone borked in some way? I mean, it works just fine otherwise, but the device's inability to install this second OTA update really sticks in my craw.
I might reapply NG3 via Odin and see what happens. Couldn't hurt, right?
fleggett1 said:
Yes, I'm still on 4.4.2. Like I wrote in my OP, though, I'm VERY concerned that this second OTA update keeps failing. I'm also perplexed as to why the device is still in some sort of custom state since I thought taking the OTA update would, in essence, reset everything except user data.
Is my phone borked in some way? I mean, it works just fine otherwise, but the device's inability to install this second OTA update really sticks in my craw.
I might reapply NG3 via Odin and see what happens. Couldn't hurt, right?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=3149146
If you want root, go to the OP in that post, scroll down to step 4 or the notes section and download the "downgrade to nce.zip" flash that in odin "ap" slot. Then root with towel root. After that you can either download titanium backup and fees the ota's or use that same thread to upgrade to the OF2 version and keep root.
Edit:
If you want to just take the OTA's and not root your phone then still download the "downgrade to nce.zip" flash in odin but don't root. The ota's will push through with no problem then. But you won't be able to downgrade and root if you take the OTA's all the way up to oc4 i believe.