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

AT&T Software Update

After rooting I deleted all of the AT&T and Facebook software. I note that the AT&T Software Update check button remains under Phone Settings, but more disturbingly was a pop-up this morning stating that AT&T Update was checking for updates! Fortunately I happen to be in a wifi-only area right now -- no cell coverage so the "network is not available".
So far Google has NOT been my friend. Is anyone aware of a switch to fully disable or script to remove this? Thanks! --Larry

Assuming you've flashed a custom recovery image, then when it asks to install the update, just "let it". It will reboot the phone into the recovery, and you can immediately cancel. The phone will never prompt you to update after that even though you're still on the old version.
Sent from my HTC first using xda premium

nuclear_eclipse said:
Assuming you've flashed a custom recovery image, then when it asks to install the update, just "let it". It will reboot the phone into the recovery, and you can immediately cancel. The phone will never prompt you to update after that even though you're still on the old version.
Sent from my HTC first using xda premium
Click to expand...
Click to collapse
But if doesn't find an update & reboot to recovery, will it simply keep searching (& using battery)?
I rebooted and the popup hasn't returned, but I still would like to disable/remove the whole thing.

amphi66 said:
But if doesn't find an update & reboot to recovery, will it simply keep searching (& using battery)?
I rebooted and the popup hasn't returned, but I still would like to disable/remove the whole thing.
Click to expand...
Click to collapse
Nuke the 2 zips in /system/etc/security. That will kill OTAs altogether
Sent from my HTC first using Tapatalk 2

jmz said:
Nuke the 2 zips in /system/etc/security. That will kill OTAs altogether
Sent from my HTC first using Tapatalk 2
Click to expand...
Click to collapse
"zips" deleted. Thank you!

amphi66 said:
"zips" deleted. Thank you!
Click to expand...
Click to collapse
Because I can't leave well enough alone (& with "zips" deleted & other AT&T apps deleted) since I couldn't remove it, I pressed the "AT&T Software Update" button in Settings. Surprisingly, after a brief search the phone began to download an update! I forced an immediate reboot to recocery and did a backup restore to insure it was stopped.
Question: As I am running build 1.08.502.1 CL180011, Baseband version 1.15.40.00.13_2_10.64.40.33AL what is this update trying to do and should I let it try to install. I certainly do not want to impact my s-off, root, or deodexed ROM.
Thanks.

How to get a download URL for a Nexus OTA update

I always see people asking how to get the download url every time there's an ota, so I thought I'd post this where it can be found, rather than get lost on page 137 of the ota announcement thread like always seems to happen.
The following requirements must be met:
latest stock android (ota or factory image will do)
stock recovery (you will get an error if you try to install an ota with a custom recovery)
contrary to common belief, root does not matter!!
adb installed on your computer (installing the android sdk is the most common way to do this)
When you get the ota notification DO NOT download the update, and DO NOT reboot your phone!
plug your usb cable into your computer (not a front port)
open the command terminal (start>accessories>cmd or type cmd in the search under the start menu)
enable usb debugging (settings>development>enable usb debugging)
type the following line exactly as it's written then press enter
adb logcat
it will print out a whole bunch of text below this line in the command terminal.
start the OTA download.
copy and paste everything from the terminal into a notebook text document and attach it to your post if you can't find the url in this text yourself. someone will help you, for sure!
now it is safe to reboot your phone and install the update

It's OTA Update season for Nexus users...this thread needs to be up top so we can ensure we get the OTA link ASAP
Good luck, everyone!!

To the top!!!!

Looking forward to kit kat
Sent from my Nexus 4 using xda app-developers app

kitkat available for nexus4?
Sent from my Nexus 4

Wouldn't it make more sense to do it in this order:
1. Receive update notification
2. Start recording logcat
3. Begin download
4. Stop logcat
CMIIW
Sent from my AOSP on Mako using Tapatalk

sayogs said:
kitkat available for nexus4?
Sent from my Nexus 4
Click to expand...
Click to collapse
not yet.

For those that have root, by far the easiest way is to look in /cache before installing the update. The file will be there after you download it.

I'm on stock 4.3 with custom recovery and LTE radio .84 to get the 4.4 OTA I will need to return to stock recovery? I know applying the OTA I will loss LTE.
Sent from my Nexus 4 using Tapatalk

LowQue27 said:
I'm on stock 4.3 with custom recovery and LTE radio .84 to get the 4.4 OTA I will need to return to stock recovery? I know applying the OTA I will loss LTE.
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
LTE mod has modified the system files.
You need to get the original system files.
Also just download the factory image from Google when it's available instead of the hassle with OTA.
Sent from my Nexus 4 using xda app-developers app

failly said:
LTE mod has modified the system files.
You need to get the original system files.
Also just download the factory image from Google when it's available instead of the hassle with OTA.
Thanks. I didn't think losing LTE would be this tough choice. (LTE vs. 4.4.) FML.
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse

//

I am sad! I still haven't gotten 4.4 on my Nexus 4.

Rody2k6 said:
I am sad! I still haven't gotten 4.4 on my Nexus 4.
Click to expand...
Click to collapse
Don't worry! Nobody did!

The OTA is now live, guys!! It's worth noting this post by Dan Morrill:
(In reference to clearing Google Play Services appdata in an attempt to force the OTA notification)
Dan Morrill said:
Doing this changes the primary ID by which Google knows your device. As far as the servers are concerned, the device was basically factory reset. There are many downstream effects of this, but a big one is that this invalidates the tokens used by any app that uses GCM (which is nearly all the Google apps, and a ton of third-party apps.)
How apps react to GCM IDs changing varies by app. With Play Store you have to log out and log back in, I think Gmail usually handles it transparently eventually but won't get new mail notifications for a while, etc. Some apps you may have to clear data on to recover. All apps will simply stop getting GCM push-messages, until they get a new GCM ID; some do this frequently, others rarely, and some apps use the GCM ID as an ID on their own servers (as it is opaque and basically random), so other things besides push messages may not work.
Nothing bursts into flames, but it makes a ton of nuisances on the device, including some that can look pretty mysterious. Your mileage will vary depending on what apps you use.
All of this can be avoided by just doing an 'adb sideload' if you are impatient.
----------
Rollouts are conducted in phases. Typically they start at 1% of devices for around 24 - 48 hours; we watch the return rates and resulting device checkins and error reports (if any), and make sure nothing looks wrong before sending it to more. Then typically it goes to 25%, 50%, 100% over the course of a week or two.
What the percentages mean is that when your device checks in, it has a 1% chance (for example) of being offered the OTA. If it doesn't (randomly) get an offer, it will never get an offer until the next batch.
IOW, once your device checks in and gets turned down, that's it until the next batch. Mashing on the "check for updates" button just causes your device to check in again, and get automatically turned down again. Think about how that makes your device feel! WON'T SOMEONE PLEASE THINK OF THE PHONES?!
That said, once the new batch does start, hitting that button does give you a new roll of the dice -- but once. Since devices usually only check in for system updates every 24 hours (I think? Certainly on a many-hours basis) this can get you your shot sooner than it would happen on its own.
So, mash away. Just be patient, and mashing on it more often than once or twice a day isn't going to gain you anything.
Edit: also, keep in mind that this isn't first-come/first-served. You're not racing other devices to get your slot in the current batch, or something.
Click to expand...
Click to collapse
Source:
Android Police

Sorry, couldn't get adb logcat, but here's screenshot of /cache folder for OTA 4.4 https://twitter.com/caplang/status/403643070748446720/photo/1

No need of worrying.
Just download the update and flash it through adb sideload by going into recovery.
Sent from my GT-P3100 using xda app-developers app

thanks pal,it helps

Nexus 7 32GB Will not get OTA

Hi, I just got a nexus 7 32GB to replace my 16GB. The problem is that I'm not getting the OTA. I'm stock 100%, but don't want to install 4.3 via adb.
I have tried the following:
1 - clearing cache and data from framework services, then look for update. = NOTHING
2 - clearing cache and data from framework services, stopping service, then look for update. = NOTHING
3 - clearing cache and data from framework services, restart, then look for update. = NOTHING
4 - clearing cache and data from framework services, stopping services, restart, then look for update. = NOTHING
Been doing this for 2 days now, do you guys have any other suggestions. Or maybe using only one method from above over and over.
Thank you!!!

Seems like adb is your only option. Besides, rooting and playing with your tablet is fun and teaches you more of your device. You'll also appreciate the fact that since this is a nexus device, the factory image is readily available at your disposal if anything happens.

You have a nexus device. You are on a developer web site.
Why on Earth would you wait for an OTA? Grab the image from Google's Nexus Images site and flash it.

GldRush98 said:
You have a nexus device. You are on a developer web site.
Why on Earth would you wait for an OTA? Grab the image from Google's Nexus Images site and flash it.
Click to expand...
Click to collapse
And that, my friends, is logic
Sent from my SGH-M919 using xda app-developers app

It's a lot more fun to flash it manually, and you learn a lot in the process. Next time your Nexus bricks, you'll now how to fix it (if you didn't copy paste commands )

Don't want to unlock bootloader, that is the logic. Don't want to flash via adb, read it, it's in the first post. I'll do it if it's my last option, i'll wait a couple of days, if no OTA by then, i'll flash. Thank you all!!!

Did you try hard rest
Sent from my SGH-M919 using Tapatalk 2

Hi, zcucurullo...
There are links for Jellybean 4.3 OTA .zips here (you'll have to wade through a fair amount of text to find 'em) for both WiFi only Nexus 7(Grouper/Nakasi) and WiFi/3G Nexus 7(Tilapia/Nakasig) which you should be able to flash via stock recovery and ADB (unfortunately), but without unlocking the bootloader.
Some instructions here.
--------------------------------------
I can't think of any other way of doing it to be honest... other than as Nasser suggests, and try a hard reset/factory reset (although you will loose all your data).
Kind of odd though, you haven't been pestered with endless notifications about the OTA, which has been available for, I think, 4 weeks now.
Anyway... good luck.
--------------------------------------
Edit & additional...
XDA Recognized Contributor, oldblue910, maintains an archive of Nexus 7 Stock OTA URLs here... http://forum.xda-developers.com/showthread.php?t=1745781
Rgrds,
Ged.

I have nexus 7 32gb. Got the ota when it was released.
Skickat från min Galaxy Nexus med Tapatalk 4

GedBlake said:
Hi, zcucurullo...
There are links for Jellybean 4.3 OTA .zips here (you'll have to wade through a fair amount of text to find 'em) for both WiFi only Nexus 7(Grouper/Nakasi) and WiFi/3G Nexus 7(Tilapia/Nakasig) which you should be able to flash via stock recovery and ADB (unfortunately), but without unlocking the bootloader.
Some instructions here.
--------------------------------------
I can't think of any other way of doing it to be honest... other than as Nasser suggests, and try a hard reset/factory reset (although you will loose all your data).
Kind of odd though, you haven't been pestered with endless notifications about the OTA, which has been available for, I think, 4 weeks now.
Anyway... good luck.
--------------------------------------
Edit & additional...
XDA Recognized Contributor, oldblue910, maintains an archive of Nexus 7 Stock OTA URLs here... http://forum.xda-developers.com/showthread.php?t=1745781
Rgrds,
Ged.
Click to expand...
Click to collapse
Thank you my friend, will try hard reset, don't have anything inside at the moment. Do I have to add my google account before trying the update after the reset?:cyclops:

Hard reset did not do the trick, still on 4.2.2 i'll give it a few more days and will try to connect to different internet providers just to see. Thank you all!!!

Oops

zcucurullo said:
Hard reset did not do the trick, still on 4.2.2 i'll give it a few more days and will try to connect to different internet providers just to see. Thank you all!!!
Click to expand...
Click to collapse
by changing the internet provider will your device get priority for OTA update even if you are in the same country? or does having a different internet provider change your device information for OTA update?
i thought it does by device firmware information, as long as your online, you will eventually get firmware OTA update?
i'm confused, not that it matters. just curious how OTA updates are actually pushed.

FYI installing the factory image from Google does not install over adb, it installs over fastboot

Just change your vpn to some US location and then try 1 and 2 as given in op. (preferably 2.)

lekhwani said:
Just change your vpn to some US location and then try 1 and 2 as given in op. (preferably 2.)
Click to expand...
Click to collapse
I saw somewhere that if google can't find your device you wont get the update. That's why I wanted to try out using internet from different carriers. Thank you all for your help on the issue.

AuroEdge said:
FYI installing the factory image from Google does not install over adb, it installs over fastboot
Click to expand...
Click to collapse
Fastboot adb, etc... Just want to get OTA. Don't want to push manually to device by downloading the update and connecting via USB and using fastboot command. Dont want to unlock bootloader also. So the problem is OTA. Thank you!!!

lekhwani said:
Just change your vpn to some US location and then try 1 and 2 as given in op. (preferably 2.)
Click to expand...
Click to collapse
SOLVED, SOLVED, SOLVED.
JAJAJAJAJA, you rule, just changed my VPN to a free Canadian one, and the nexus 7 is downloading the Update as I type. Thank you, Thank you, Thank you!!!

Force ota update

Android 4.4.3 Force Update Procedure found :
Disable Google Services Framework and Restart the Phone...now clear cache and Enable the framework and check for the Update.....!!

It's been known for a while.
Also, don't do it... http://www.androidpolice.com/2013/1...to-never-clear-google-service-framework-data/
Sent from my Nexus 4 using Tapatalk

Force it but after you will have many problems to resync the phone whit playstore!

I have always forced it this way and have never had any problems with anything afterwards. I just have to accepts G Play terms and conditions after I do it. It might be something Google engineers don't want us doing. I think this process generates a new ID for the phone, which Google might not want.

It doesn't make a difference in getting ota. It is a wasted effort.

raul6 said:
It doesn't make a difference in getting ota. It is a wasted effort.
Click to expand...
Click to collapse
You're wrong, it does. I have always gotten my OTA doing this.
I was also wrong though. I just noticed that my Facebook messenger notifications aren't getting through. So don't do this people, flash the factory images without -w flag instead.

TheNikkoMan said:
You're wrong, it does. I have always gotten my OTA doing this.
I was also wrong though. I just noticed that my Facebook messenger notifications aren't getting through. So don't do this people, flash the factory images without -w flag instead.
Click to expand...
Click to collapse
The syncing problem will resolve itself in a matter of hours. There is no permanent damage done.

Is it really that serious to get the update from OTA with zips and images and roms floating all over the place. We make too much of an incremental update as well..Just my opinion

Just tried it didn't work. Not too fussed about the effects as it only lasts for a few hours.

playya said:
Is it really that serious to get the update from OTA with zips and images and roms floating all over the place. We make too much of an incremental update as well..Just my opinion
Click to expand...
Click to collapse
I did it because the micro USB port is broken, I'm unrooted and have stock recovery (bad situation).
Also, it does work. You just have to repeat the process until it works, it never works the first time.