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

OTAs and CWM/TWRP

I'm reading the threads and seeing a consistent pattern (and experienced it myself). Referring at least to 4.1.2 -> 4.2 and 4.2 -> 4.2.1, it seems that you can do the OTA update if you if you have CWM but not TWRP. If you accept the OTA and have CWM, it will reboot into CWM, apply the update, ask if you want to preserve recovery and su, and reboot you into the new version.
If you have TWRP, though, it seems people get stuck at error 7 or similar.
When a larger version comes out in the future though I suspect we'll have to flash by hand as the OTA could blow away custom recovery; but for the two mentioned above at least, it wont kill CWM and installs fine with it in place.
I've loved TWRP in the past, but in this case it looks like CWM is handling the OTAs more gracefully. It's just a random chance that I have the latest CWM on my N7 instead of TWRP.

I have never used twrp, but I have done the last updates through cwm recovery and kept recovery and kept root. Definitely recommend cwm recovery.

I just got the OTA here, on TWRP 2.3.2.1, Nexus 7 no 3G. No errors, just worked.

Yeah just got the new update and I'm still rooted
-Google

iGoogleNexus said:
Yeah just got the new update and I'm still rooted
-Google
Click to expand...
Click to collapse
And you are using which recovery?

Both work. If they don't something else is going on.
Sent from Tapatalk XDA Premium
<><><><><><><><><><><><>
Nexus 7
Clean ROM 3.0 - Leankernel 0.8.x

jb0ne said:
And you are using which recovery?
Click to expand...
Click to collapse
CWM ...
-Google

Worked for me using TWRP
Sent from my SAMSUNG-SGH-T989 using xda premium

Just took the 4.2.1 update im still rooted using TWRP...

Status 7 is usually a security thing regarding the signature I think. If anything CWM has signature verification off by default.
Sent from my Nexus 7 using XDA Premium HD app

I really don't understand why people are having such a hard time understanding what is wrong when they receive an error message with the OTA update.
It's not complicated people. You don't need to be a friggin' brain surgeon or a senior level developer. The error message TELLS YOU what the issue is.
Verifying current system...assert failed: apply_patch_check("/system/SOMEFILE")
Guess what? Something is wrong with SOMEFILE. You either modified it, deleted it, "froze" it in TiBu, or did something else that is causing the update to break.
If you look at the updater-script, you can see everything thing the OTA does. It's just a long batch script basically.
The ONLY way this 4.2.1 OTA update is going to fail due to recovery is if you are using the wrong recovery for your device (ie: grouper on talapia, etc.).

I hear what you are saying but....my N7 is stock, untouched, unlocked & rooted, yet I had problems with CWM & TWRP with the OTA and flashing the update manually.
I had to go back to stock recovery for both updates.
But I can see in this thread some have the OTA update working fine, one thing we all have in common is the N7, yet varied results.

jersonf said:
I hear what you are saying but....my N7 is stock, untouched, unlocked & rooted, yet I had problems with CWM & TWRP with the OTA and flashing the update manually.
I had to go back to stock recovery for both updates.
But I can see in this thread some have the OTA update working fine, one thing we all have in common is the N7, yet varied results.
Click to expand...
Click to collapse
Was your unit a 3G or Wi-Fi only model?

OTA?
I hate to be the hater, but why would anyone here take an OTA? The reason this site exists is specifically to help people to not use the stock software. If cwm survives OTAs it is probably an accident, lol.
Sent from my Nexus 7 using xda premium

brizey said:
OTA?
I hate to be the hater, but why would anyone here take an OTA? The reason this site exists is specifically to help people to not use the stock software. If cwm survives OTAs it is probably an accident, lol.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
What are you talking about?
XDA is in no way a site dedicated exclusively to "help people not use the stock software". It's a place where people can discuss their hardware/software including stock/custom/etc. usage and modifications. So not only is your comment 100% incorrect, but it's also contrary to this thread in particular. The thread title clear talks about using a CUSTOM recovery with an update to the stock software. So even if you were right (you aren't), your point is counter-intuitive.
There are many people here that are either mostly or completely stock. That's their personal preference and it's completely fine and acceptable. And it most certainly doesn't mean they don't deserve help or assistance here.
---------- Post added at 03:17 PM ---------- Previous post was at 03:13 PM ----------
Also, while OTA updates are written in such a way to remove suid root on the su binary and reinstall the stock recovery image, most new custom recoveries have a work around in place to prevent this. Not to mention it's trivial to restore them back after the update.

brizey said:
OTA?
I hate to be the hater, but why would anyone here take an OTA? The reason this site exists is specifically to help people to not use the stock software. If cwm survives OTAs it is probably an accident, lol.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
No accident ... I updated my N7 from 4.1 to 4.2 still rooted.. And I just updated again to 4.2.1 ... Don't know about you but I love these kind of updates
Also I like my devices stock, rooted and a few tweaks here and there along with rooted applications... I'm sure there are many of me out there.
-Google

I prefer to never actually flash the recoveries.. just adb boot them as required - that means my system is always stock for the updates and I can pick a recovery at random should I want them (although generally I only use them to get a root shell to install su when I get a new phone).

I am rooted stock with cwm touch and the ota fails staus 7. I'm pretty sure I didn't do anything to "break" the update for myself. It's kind of funny the clockwork stops and asks about flashing an untrusted rom and then doesn't allow it. I would rather sit out of this whole 4.2 bs anyway.

I was rooted and stupidly just clicked the update to 4.2.1 without thinking, it didn't even occur to me to take any measures to keep root or custom recovery. So I lost both. It only took a few minutes with Wugs' toolkit to fix though.

I've taken three OTAs with TWRP and had no problems with any of them.
Sent from my Nexus 7 using Tapatalk HD

Prevent phone updates

Now that root has been achieved, I want to be sure to keep it. So, to prevent Moto from patching/removing root, how should I go about preventing my phone from downloading any updates Moto will surely push out? Until I know they are root-safe at least.

I believe that we are all going to have to wait a couple more days as they continue to work on the root process. Right now we cannot write to the system partition. And whatever it is that you need to freeze is on that partition. So they plan on releasing an update soon that will address that.

Ah ok that makes a lot of sense.
Sent from the sexiest Moto X ever created using the XDA Premium app

thepolishguy said:
I believe that we are all going to have to wait a couple more days as they continue to work on the root process. Right now we cannot write to the system partition. And whatever it is that you need to freeze is on that partition. So they plan on releasing an update soon that will address that.
Click to expand...
Click to collapse
We can freeze stuff in /system. I've already gone through and frozen a whole ton of crap. Not sure off the top of my head what we need to freeze to prevent OTAs, but it can be done with our current root situation.
Sent from my XT1058 using XDA Premium 4 mobile app

_MetalHead_ said:
We can freeze stuff in /system. I've already gone through and frozen a whole ton of crap. Not sure off the top of my head what we need to freeze to prevent OTAs, but it can be done with our current root situation.
Sent from my XT1058 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I froze the app called something OTA. Assuming that works. Don't we usually have to OK an OTA install anyways? They don't just happen without consent do they?

rmead01 said:
I froze the app called something OTA. Assuming that works. Don't we usually have to OK an OTA install anyways? They don't just happen without consent do they?
Click to expand...
Click to collapse
Depends on the method of root, they could patch the app or process that allows the exploit....

For this reason alone, I uninstalled root for now. I'd rather wait until jcase puts together a completed permanent root and sorts out most of the major issues.

Just make a change to the /system partition. Then ota will fail. Or just select no if they ever pop up ?
Sent from my XT1058 using XDA Premium 4 mobile app

Any updates on this? Would freezing the OTA app work or is there some other process?

5.1.1 just got released!

So 5.1.1 for the att Samsung galaxy s6 has finally been released! Now I do hope the memory leak issue will get addressed in this build, but I am wondering if we should avoid updating to it if we are rooted? I wonder how long it will take for our custom roms to update to this.
http://www.androidcentral.com/samsung-galaxy-s6-s6-edge-received-android-511-update-att

Well I hope someone puts up a .tar file for us to flash this instead of relying on the OTA. I jut do not like OTA updates. Something always seems to go wrong

Never had a issue when plugged in with wifi. Never DL walking around and still using phone. That is why everyone has a problem. Not sure if your case but throwing it out there.
Sent from my SAMSUNG-SM-G925A using XDA Free mobile app

I just can't get the update at all. It's not showing up.
Sent from my SAMSUNG-SM-G920A using Tapatalk

Over WIFI? Nothing? I was just release so maybe it's a rolling release. Hmmm
Sent from my SAMSUNG-SM-G925A using XDA Free mobile app

Yeah even wifi. I changed the date multiple times still nothing. Just depressing. I bought the device straight out so the locked bootloader is sad enough but making the updates ota only is just crazy.
Sent from my SAMSUNG-SM-G920A using Tapatalk

Unfortunately S6 active isn't mentioned anywhere

Hope that the update comes out for s6 active soon and someone provide with a .tar file flashing with Odin

Been trying to update my wife's phone since last night and everytime it says that the update failed. I have tried 3 times and no luck.

Enable all the apps you previously disabled. Set the time forward and try again.

jrodsep said:
Been trying to update my wife's phone since last night and everytime it says that the update failed. I have tried 3 times and no luck.
Click to expand...
Click to collapse
Same thing. Haven't tried with disabled apps enabled yet though.

SilentLunatic said:
Enable all the apps you previously disabled. Set the time forward and try again.
Click to expand...
Click to collapse
How can I check that? Where do I need to look at to see if she has disabled by accident something? Thanks in advance

jrodsep said:
How can I check that? Where do I need to look at to see if she has disabled by accident something? Thanks in advance
Click to expand...
Click to collapse
Settings -> Applications -> Disabled

Installing now - let's see how bad AT&T cocked up the update.

I have no apps disabled, non rooted, and still am getting install failed.
I did uninstall some apps when I first got the phone. Could that be causing the failed update?

Successfully updated to 5.1.1.. Seems a bit smoother but other than that, nothing big..checked if they added any sort of shutter control..nope
Sent from my SAMSUNG-SM-G920A using XDA Free mobile app

Has anyone tried to run older root methods yet to see if anything works? Sometimes with new OTAs, previous exploits are overlooked.
Sent from my SAMSUNG-SM-G920A using Tapatalk

The memory management is sooo much better. Flipboard stays open on all day now

I think Ive seen it somewhere but cant seem to find it. Is there a wayto unroot or flash din files to take the 5.1.1 update. I am currently rooted and used flash fire to get to OF3. Can I just odin the oe2 files and take the update?

Does it have better performance than one of those ultra lite rom's? I am considering of getting off of my custom rom so I can take this update.

Stock Note 3 (Android 5.0)

I have a note 3 with at&t that's never been rooted but I would like to. Can sometimes point me in the right direction to get started?
Sent from my SAMSUNG-SM-N900A using XDA-Developers mobile app

Anyone can point us to the right direction for rooting?
Sent from my Nexus 10 using Tapatalk

zubero said:
Anyone can point us to the right direction for rooting?
Sent from my Nexus 10 using Tapatalk
Click to expand...
Click to collapse
+1 for OC2, I mean all, I, am, seeing is Downgrade options to 4.4 KitKat then towel root then Safestrap then flash slotted Updated Lollipop Rom? All, I want is to remove bloat and use exposed, is there a root for OC2? Without downgrading thanks

Here's the video for downgrading and rooting. Then after that you can use any of the builds available. I'm using Alliance v12. Works like a charm,I almost gave up on my phone and was about to buy a new one. After downgrading to NC2,rooted and the pushing in Alliance 12 it's back. Thank you community.
https://youtu.be/QL6V7Y8vNms
Sent from my Nexus 10 using Tapatalk

zubero said:
Here's the video for downgrading and rooting. Then after that you can use any of the builds available. I'm using Alliance v12. Works like a charm,I almost gave up on my phone and was about to buy a new one. After downgrading to NC2,rooted and the pushing in Alliance 12 it's back. Thank you community.
https://youtu.be/QL6V7Y8vNms
Sent from my Nexus 10 using Tapatalk
Click to expand...
Click to collapse
So you downgraded to NC2 which I'm assuming is 4.4.2 becuase Im on NJ5, downgraded to NC2 or Jellybean I think and rooted with towel root and installed safestrap via the instructions, but when I try to reboot into Safestrap after installing and it installs, I grant it Superuser, and click Reboot to Recovery and nothing happens, any ideas? Becuase I need Safestrap, so I can flash Alliance, or Backup or anything else, but there are SO MANY conflicting OP's, regaurding Safestrap "it abandoned", "it only works on 4.2.2", "there's a work around for Safestrap on 4.4.4, by flashing Kitcat Kernal" "or Safestrap will work on on OC1 also with correct kernel"
All I want is to be on the "LATEST FIRMWARE FOR THIS PHONE, THAT WILL ALLOW ME TO EFFECTIVELY USE SAFESTRAP, TO BACK UP, FLASH, AND RUN ALLIANCE ETC..."
IF that means being someone a beer, I'm cool with that, been around here for awhile and had many Samsung phone Notes One, Two, S3, S4, but never had to deal with this bootloader crap, just so frustrated at this point[emoji726]
Sent from my SAMSUNG-SM-N900A

Did you install busybox before installing safestrap?
Sent from my DROID Turbo using XDA-Developers mobile app

Yeah I'm pretty sure I did I mean I have Busy box installed of course, and Safestrap, and I'm not sure in what order, however if Busy box was causing the issue, then Safestrap would not install at all, right? But yes now that I remember, when I got this phone it was already updated to OC1 (at that time the latest build) after try to sift through all the different out dated tutorials, I finally just did what I mentioned above, but Safestrap "Installs fine", "Allows me to grant SU", then "allows me to (click)" reboot to recovery" then FAIL.... nothing happens, on NJ5, I know Safestrap ended development at some point, and don't you also have to flash a certain kernel in order for SS to work on KK? So Confused
Sent from my SAMSUNG-SM-N900A

You need to install Busybox, then open busybox and tell it to install it into the system
Then open safestrap and do likewise.
I did this on nc2 no idea how it'll work on an older version.
Sent from my DROID Turbo using XDA-Developers mobile app

mrkhigh said:
You need to install Busybox, then open busybox and tell it to install it into the system
Then open safestrap and do likewise.
I did this on nc2 no idea how it'll work on an older version.
Sent from my DROID Turbo using XDA-Developers mobile app
Click to expand...
Click to collapse
so mrkhigh, thank you by the way first! off, to your response, so as far as you know "Safestrap" did not require any additional steps, to work on 4.3, like an updated kernel, which I know makes no sense to me eithier, other than the permission changes that occured at the true root level on NJ5 Update, and SafeStrap itself not being a true recovery, in the word of true TWRP, per this pain in my @$$ bootloader, which I have already made knowen in this community, AND others, is simply a loophole, to the "right to modify" ruling by the FTC some years back, if you will to the carriers, at&fee included among others
Sent from my SAMSUNG-SM-N900A