Database Develop

Failed OTA to 4.2

I had the notification for 4.2 update yesterday morning and after pondering for the day I decided to initiate the upgrade which for some reason or another the update failed.
Is there anyway of finding out why the update failed and since the failure I've had no further notifications of the update so how can I try the update again?
Thanks
Jon

Update just failed for me too, which having read up, looked like it might have been because of having an alternate recovery installed.
So I removed the recovery .................UPDATE FAILED
Removed root.....................................UPDATE FAILED
Locked Bootloader..............................UPDATE FAILED
Full system wipe.................................UPDATE FAILED
You can force a retry by going to App,------All-------Google Services Framework and stopping the process and wiping the data
Then checking for update manually.
Some folks say you can have problems with Play and push notification after the framework wipe, but as I had gone the route of restoring to default, I wasn't bothered as I will just do the same again.
I wonder if there is a deeper issue however, than just my tablet.
Phil
jonchill said:
I had the notification for 4.2 update yesterday morning and after pondering for the day I decided to initiate the upgrade which for some reason or another the update failed.
Is there anyway of finding out why the update failed and since the failure I've had no further notifications of the update so how can I try the update again?
Thanks
Jon
Click to expand...
Click to collapse

did you guys did anything or change anything from system, like change the proxyprovider.apk for flash support? Mine failed through OTA and even via manual update but then I changed back the those apks and things went well and now I am on 4.2. Just sharing my experience and hope it can help you guys. somewhat.

If you guys replaced the stock recovery, deleted or froze any stock apps,or modified any system configuration files, OTA is going to fail.

My tablet updated just fine and it is both rooted and unlocked. My galaxy nexus which is the same (both rooted and unlocked) for some reason fails on the 4.2 update.

I had the exact same problem over the past two days, I don't have a custom recovery, just unlocked bootloaded and root.
just lou said:
If you guys replaced the stock recovery, deleted or froze any stock apps,or modified any system configuration files, OTA is going to fail.
Click to expand...
Click to collapse
OOOOOH! I froze then deleted the KOREAN IME app, because why the heck do I need a Korean app on my tablet? Hmm, so what are my options? Can I just redownload the Korean IME off the play store and OTA will work then?
Was there any other forced IME like Chinese that's 'baked in' to the Google ROM? I forgot if I may have deleted any others, but I think it was only Korean.

just lou said:
If you guys replaced the stock recovery, deleted or froze any stock apps,or modified any system configuration files, OTA is going to fail.
Click to expand...
Click to collapse
That explains it then I've deleted and frozen stock apps.
Thanks

I'm the same, i deleted system apps.
Is the only way to fix this to use a pc and adb the 4.1.2 zip and gapps?
Is there any way to fix it from the device itself?
(I've tried flashing the 4.1, 4.1.2 and 4.2 via CWM)
Would reflashing the 4.1 gapps help?
Sent from my Nexus 7 using xda premium

I had the same problem. Used titanium backup and the "integrate system apps updates into ROM" option and then couldn't update to 4.2.
Tried several things I read in this forum but nothing worked.
Had to erase everything and flash the stock ROM I downloaded from Google. They have a 4.2 stock ROM too so didn't need to update afterwards.
Then restore all your apps from backup and you are set.
Sent from my Nexus 7 using Tapatalk 2

Wow, all because a damn Korean IME app? Geez, what a pain, Google. :|

Chocoburger said:
Wow, all because a damn Korean IME app? Geez, what a pain, Google. :|
Click to expand...
Click to collapse
The alternative is that you restore your system folder to its original state (i.e. get hold of that Korean IME app, stick it back in /system/app and set the correct permissions). I had to do this with Google Wallet but it can be done if you know exactly what you've changed and avoids flashing a factory image and setting your device up again (albeit that Titanium makes this relatively painless now).

Have a brand new 32 GB N7, and having the same update fail, right out of the box, like wtf

CFRTim said:
Have a brand new 32 GB N7, and having the same update fail, right out of the box, like wtf
Click to expand...
Click to collapse
Me too. Also a 32gb N7. I owned it less than a week. Multiple factory resets didn't correct the issue either. I returned it to the store for a refund. Didn't want to keep a device that would never install updates.

I have 32 gigabyte Nexus 7 and it came with Android 4.2 out of the box so I guess no problems with the updates
Sent from my Nexus 7 using XDA Premium HD app

CFRTim said:
Have a brand new 32 GB N7, and having the same update fail, right out of the box, like wtf
Click to expand...
Click to collapse
So your saying you opened it, turned it on, signed in.....then your status bar should show system update available, click it, accept, let it do its thing and it just failed?
Sent from my Nexus 7 using Tapatalk HD

If you search the forums this has been addressed and solved. You need to reflash the os - you don't need root. Use wugs toolkit. Its a problem on googles end where the nexus was formatted incorrectly, and a reflash fixes it.
Sent from my Nexus 7 using Tapatalk HD

Yep. Got the Android robot on his back, with the triangle/exclamation point on top of him, after downloading, restarting and almost complete install. I've tried multiple times and miserably failed each time, at the same point. Eventually, I was able to manually update it using Wug's Nexus Toolkit, since all other methods failed. Thank you Wug
Sent from my Nexus 7 using Tapatalk 2

[Q] Really messed up phone, OTA Failed [Help Needed]

Okay, I've tried everything I can think of, and I've managed to really confuse my phone and myself.
I took the 4.4 OTA update, and about halfway through it failed. The phone would not boot currently, upon booting the colors would go all jacked up with bars and lines. So..okay thats not good. Knowing some of the security features by hitting them head on in Odin, I finally settled for flashing only the AP image. Which gave me a booting 4.3 system with no wifi.
I tried to manually run the OTA in recovery at this point, and it fails with "error 7 /csc/contents.db has unexpected contents" I think that it what it said because this phone runs through the update pretty fast. However, it fails to update the system, but formats my data and cache.
So now I have what I assume is the 4.4 BL and 4.4 Baseband, running a 4.3 system with no wifi.
Is there any way to fix this csc issue so that it will update to a full working 4.4 system.
Phone: SGH-I537 (AT&T S4 Active)
BL: Assuming 4.4 BL since the 4.3 one will not flash due to "fuse..." error of sorts
BB: xxxxxNC9
AV: Android 4.3

Okay, So I managed to get my device working on 4.3 again. Obviously you cannot reflash the boot loader due to samsung's security mess; but you can still flash CSC, Phone, and PDA back down to the 4.3 versions and it will boot up and run. This has worked once so far, but after I applied the 4.4 update again, back to square one. I'm thinking AT&T has sent me the incorrect update file via their OTA updater.
Edit: I have no audio now...
Edit 2: Took the AT&T OTA again to see if it would fix...forget it. I'm stuck with 4.4 BaseBand (with audio thankfully), Android 4.3 system, and no wifi again.

Bleedin_Sarge said:
Okay, So I managed to get my device working on 4.3 again. Obviously you cannot reflash the boot loader due to samsung's security mess; but you can still flash CSC, Phone, and PDA back down to the 4.3 versions and it will boot up and run. This has worked once so far, but after I applied the 4.4 update again, back to square one. I'm thinking AT&T has sent me the incorrect update file via their OTA updater.
Edit: I have no audio now...
Edit 2: Took the AT&T OTA again to see if it would fix...forget it. I'm stuck with 4.4 BaseBand (with audio thankfully), Android 4.3 system, and no wifi again.
Click to expand...
Click to collapse
How did you get audio back
Sent from my SAMSUNG-SGH-I537 using xda app-developers app

gatoraid84 said:
How did you get audio back
Sent from my SAMSUNG-SGH-I537 using xda app-developers app
Click to expand...
Click to collapse
If you have not messed up the phone already, do not try this. It will get you stuck between a rock and a hard place.
Use odin to flash the 4.3 BaseBand. (I did this while flashing the 4.3 system also...) After that is done, take the 4.4 update. Then flash the 4.3 system ONLY from odin. You'll wind up with a 4.3 phone using the 4.4 baseband. But it fixed some issues for me. You'll get your audio back, but wifi will be broke again. I no longer have a modded s4a to mess with, my sustained water damage. So I was swapped for a new one. You should have an ML2 build, and an NC9 BaseBand.
It seems that the 4.4 update completely breaks the graphics subsystem and also updates you to a half baked BaseBand. And going to AT&T wont help you, even though it is their update that did this. Be very careful when updating to 4.4, it could leave you with a heavily confused phone. Also, the 4.4 update did not contain a boot loader far I could see by manually running the update. I'm assuming that is how I am able to still boot 4.3 after the failed 4.4 update. If you need any more information from my rough road with their broken OTA, just ask.

5.01 OTA disapeared

I have a question. Last night I went to about phone and check for an update and there it was 5.01 I selected to install it then it said it was going to restart and then banner went away and the phone never restarted. I tried checking for update again and its not there anymore plus my phone is at 5.0 . I was wondering if anyone has experienced this and what the solution was. Also If I where to update it manually will that mess anything up with my updates of were I get it from now. So for example my phone is from Motorola where does it get its updates from same place as Google play store? So I ask this because I think the people who post the updates they are for Google play edition and I don't want to turn my phone into Google play edition if its different from the Motorola version.
Thanks,

You're not alone. Several threads on this in general forum and Q&A. Consensus so far is hang tight and the update should resurface.
Sent from my Nexus 6 using XDA Free mobile app

Factory image is still on Google website. Grab it there.

bluh5d said:
I have a question. Last night I went to about phone and check for an update and there it was 5.01 I selected to install it then it said it was going to restart and then banner went away and the phone never restarted. I tried checking for update again and its not there anymore plus my phone is at 5.0 . I was wondering if anyone has experienced this and what the solution was. Also If I where to update it manually will that mess anything up with my updates of were I get it from now. So for example my phone is from Motorola where does it get its updates from same place as Google play store? So I ask this because I think the people who post the updates they are for Google play edition and I don't want to turn my phone into Google play edition if its different from the Motorola version.
Thanks,
Click to expand...
Click to collapse
Same thing happened here, I assumed it was due to me having unlocked bootloader & custom recovery. So I just manually flashed the factory image update using ADB. Easy peasy. You can do the same.
Cheers

If I manually flash the image will it change where my future otas come from ? Like doesnt a motorola nexus 6 updates come from a different server than a google play nexus 6 ?

Same thing for me, except I was waiting to be able to charge up my phone before installing. By the time I got to a charger it was gone. I'll probably just wait for it to resurface.

Same same here. Fully stock. Is the common theme for people experiencing this that they are on VZW? I am. Tmo bought phone with VZW sim.
Fyi, rebooting and charging havent helped.
I know i can manually update, but I'm hoping to confirm that the OTA process still works correctly with my stock phone running on VZW.

Its not only VZW.. I'm T-Mobile and the same happened

SirRastusBear said:
Same thing happened here, I assumed it was due to me having unlocked bootloader & custom recovery. So I just manually flashed the factory image update using ADB. Easy peasy. You can do the same.
Cheers
Click to expand...
Click to collapse
Did you flash the 5.0.1 completely (all partitions), or did you just flash system.img to get the 5.0.1 update? I'm trying to figure out the easiest way to get from 5.0 to 5.0.1 since I'm (stock) rooted and have thus modified the system partition, so can't do the OTA.

mlevin said:
Did you flash the 5.0.1 completely (all partitions), or did you just flash system.img to get the 5.0.1 update? I'm trying to figure out the easiest way to get from 5.0 to 5.0.1 since I'm (stock) rooted and have thus modified the system partition, so can't do the OTA.
Click to expand...
Click to collapse
Flashed each separately.
Flash bootloader image
Reboot bootloader (important)
Flash radio image
Flash recovery image
Flash boot image
Flash system image (takes a while)
Flash userdata image ONLY if you want to wipe your own data
Reboot when done
Flash custom recovery
Install SuperSU from custom recovery
Reboot
Profit
Cheers

Those like me who don't want to manually flash.. I just got off the phone with Google, and apparently within 24-48 hours the update will be available again for those devices affected by this hiccup. I'll wait.

[Q] XT1092 in bootloop after update

So this is a bit of a comedy of errors on my part...
I took the OTA update to lollipop and (foolishly) followed the same method as on KK to get root, putting myself in a bootloop. I got myself out of it by clearing the userdata and the cache.
I went about sorting everything and achieved root using the chainfire method, that was fine and I then went about reinstalling the xposed modules I had before. Foolishly, I didn't double check the status of xposed on Lollipop and consequently put myself back in a bootloop (idiot). I redid what had worked earlier, clearing the userdata and the cache to no avail.
Obviously, the problem was not the same as before and I needed to disable xposed, but in clearing the userdata I not only removed the xposed_disable.zip file to do this and also turned off adb so I can't push it.
The bootloader is fine and I can use fastboot, but can't push anything across. I hadn't replaced the recovery but can boot into twrp. However, I cannot flash it because I cannot push it over using adb.
I can't work out exactly how far I need to go back/what exactly I need to flash in order to put this all back together again.
I would be very grateful for any help that people can give on this.

Seems you need a .19 stock system partition image to get rid of the bootloop. Hope somebody can backup his system after OTA and share his image,otherwise you have to wait for official release or take risk to downgrade.
----------------------------
If you can boot from TWRP, you can try put the Xposed-Disabler-Recovery.zip in an USB SD card(maybe need formatted to particular filesystem like ext4) linked your phone with otg cable,then mount the sdcard and flash the zip file via TWRP.

If you're not worried about going back with a full wipe to KK, you can follow this link here Seeing that you can get your phone into fastboot, it'll work fine.

HAXTREME said:
If you're not worried about going back with a full wipe to KK, you can follow this link here Seeing that you can get your phone into fastboot, it'll work fine.
Click to expand...
Click to collapse
Thank you! This seems to have solved the problem (whatever exactly it was) and the mobile data is fine which was what I was most unsure about.
I'm curious, my device was a XT1092GB (or at least, I believe it was a GB) and now shows as a 'reteu' where I believe it used to show as 'retgb'. This isn't a problem as it all seems to work, but should I be expecting the Lollipop OTA update to come through? I deliberately didn't follow through on the last part of that thread and install 5.0 that way, I didn't want to tempt fate! However, I would like the update if possible and am unsure which way to go about doing it.
Again, many thanks for all the suggestions everyone. This is why android is awesome

Its a stock EU 4.4.4 so the OTA should come through. Even if it doesn't, I'm sure there's a 5.0 retgb firmware doing the rounds on this forum.

HAXTREME said:
Its a stock EU 4.4.4 so the OTA should come through. Even if it doesn't, I'm sure there's a 5.0 retgb firmware doing the rounds on this forum.
Click to expand...
Click to collapse
I guess even if the 5.0 OTA doesn't come through (for the reasons as given here, any following OTA updates should be fine, right?
If not, do you reckon then 5.0 rom given in the link you sent would be appropriate or would this be a better route?
Thanks for the help!

[Q] XT1068 OTA Lollipop update failing

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.