I just bought my Nexus 7 today, and out of the box every time I get a notification about the update, I choose install, and when it begins, after a while it crashes. It has an image of the android mascot with a latch open and a red triangle with an exclamation mark on it. I reboot, and it's like nothing ever happened.
How am I able to update this device to 4.2?
for oncneJ
Try deleting the downloaded update, then redownloading it.
If that does not work try a factory reset.
Chances are it failed verification of your system files when it tried to update, and rendered you custom recovery useless.
And there are reports of it deleting the factory recovery as well.
My best advise is to manually update using ADB or nexus toolkit or install a custom recovery and manually install it using that.
I had the same issue upgrading to 4.2.1.
But everything happened so fast I couldn't see what the issue was.
I then booted into twrp. Looked in the /system/cache folder and the zip was in there.
Tried to install again. And this time I could read the error message.
I had renamed a couple of system files. The update couldn't find these files so the update failed.
So I renamed them back and installed the update from twrp without issue afterwards.
Sent from my Nexus 7 using Tapatalk 2
I've tried redownloading mine 4 times...will a factory reset really work?
Sent from my Nexus 7 using xda app-developers app
It might.
But a factory reset doesn't touch system files.
So if the issue is that there is a modified system file causing the update to fail. Then it may not work.
If it doesn't, you could try flashing the stock firmware using the Nexus Root Toolkit, and try the update again.
If anyone else has better ideas, then feel free to correct me
Hope it works for you mate
Sent from my GT-I9300 using Tapatalk 2
How do I reflash this thing?
I don't have a custom recovery installed, and using the toolkit, I tried to install Superuser but it failed to install. Also installing an older bootloader version failed (even after unlocking the bootloader)
I tried a factory reset but it didn't help. It says something about assert failing and cannot verify. Does this mean that my recovery is really messed up?
You need to tell us exactly how you've messed up your stock N7, or at least what your current state is. Your thread starts out sounding like a stock OTA upgrade failed, and then we learn you tried to root it, and failed at a couple of steps.
The OEM upgrade process from 4.1 to 4.2.1 is sequential. You go from 4.1 to 4.1.1 to 4.1.2 to 4.2 to 4.2.1. How did you try to shortcut the sequence?
I'm not the lowest of the low, but I am the slowest of the slow. 49.6 mpg avg for 38k miles in non-hybrid Scion xB
I have a friend who does have everything stock, and the OTA update gives him the triangle of death. Does he need to install it manually?
Related
Received 4.2 ota so I protected root and proceeded to install.
Device rebooted and went straight to android with red exclamation mark then booted back to 4.1.2 with no option to try again?
I am stock rom, rooted and unlocked, but without cwm installed. Can someone tell me what I have to so next so I can try again.
I never had this problem last time when updating to 4.1.2
Many thanks.
Sent from my Nexus 7 using Tapatalk 2
exactly the same problem here
same here and im not rooted
You have to have STOCK BOOT, STOCK RECOVERY & the device MUST BE BOOTLOADER LOCKED (>fastboot oem lock).
Boot loader doesn't need to be locked and you can have a custom recovery, too. But this will be removed during the OTA install. The same for root, I.e. after the update fastboot flash recovery again and then flash superSU and you are done.
Sent from my Nexus 7 using xda app-developers app
If you flashed the 720p camera mod that might be the problem. I had the same issue till I restored the original media_profiles.xml
Sent from my Nexus 7 using XDA Premium HD app
Same here. I got the notification and whent it rebooted it was still 4.1.2. I tried to upgrade manually through recovery (TWRP) but the installation failed, so no 4.2. Are you sure the bootloader needs to be locked? When I upgraded to 4.1.2 i installed the update normally and had to re-root and re-install custom recovery. Anyone has solved this issue?
+1 rooted, cwm and uninstalled all blotware.. when i try to install ota 4.2
it gets me some errors and dosent install...
Dont wanna lose my data and dunno what to do :s
Not sure if y'all are still stuck on 4.1.2 or prior, but turns out it was the 720p camera mod after all, as AntiPhotonz pointed out earlier.
Using these instructions, I restored the old media_profiles.xml in the /system/etc/ folder. To be safe, I renamed the current (modified) media_profiles.xml to media_profiles.xml.new. I then rebooted, and tried to update OTA. My OTA updater didn't recognize that I was not on the latest version, so I downloaded the signed zip directly to my internal sd card, and then rebooted into CWM and flashed it that way.
I then updated to 4.2.1. via OTA. I may flash the new 720p profile zip when I am able. The zip did not exist when I first tried to apply the mod; let's hope this will be much less messy.
hi,
apologies if this has been asked before but my searches have not found a clear answer. i have a 2012 nexus 7 Rooted and running JB 4.2.2.
the OTA update to JB 4.3 fails everytime. it gets so far and then shows the android logo with a red triangle exclamation and just "error"
it reboots back to home screen after a minute or two.
my device was rooted using WUGS toolkit and TWRP recovery. i just did the basic rooting so i could use stickmount and have done nothing funny with the device since.
i have seen many guides about flashing 4.3 update that will wipe the device which i really want to avoid.
will it work if i just un-root and re-lock the device with the toolkit and then run the OTA update or is it more complicated than that.
Lemegeton300 said:
hi,
apologies if this has been asked before but my searches have not found a clear answer. i have a 2012 nexus 7 Rooted and running JB 4.2.2.
the OTA update to JB 4.3 fails everytime. it gets so far and then shows the android logo with a red triangle exclamation and just "error"
it reboots back to home screen after a minute or two.
my device was rooted using WUGS toolkit and TWRP recovery. i just did the basic rooting so i could use stickmount and have done nothing funny with the device since.
i have seen many guides about flashing 4.3 update that will wipe the device which i really want to avoid.
will it work if i just un-root and re-lock the device with the toolkit and then run the OTA update or is it more complicated than that.
Click to expand...
Click to collapse
Same Here!, I had TWRP recovery and I'm rooted, so Just Flashed stock recovery and I though I can update easily. But now I can't!
-By the way, I did not change any system file.
Since you have Stickmount did your error message reference a bad file check on 'debuggerd' in the /system/bin folder? It seems Stickmount may replace or alter that file and you have to put back an original for 4.2.2 to successfully flash the update with TWRP. After replacing 'debuggerd', the update flashed just fine for me. Are you sure you didn't get any text other than 'Error'? Are you sure you didn't freeze or delete any system apps?
It also happened to my nexus 4, they recommended to use this way: (It won't erase the data)
http://forum.xda-developers.com/showthread.php?t=2377307
hey, the error has no message or info. it literally says the word "error" with red exclamation and thats it. i have not touched any of the system apps or done anything that could upset the system files.
i will try the suggestion from alipashang77, thanks
sorry but those instructions are for the samsung galaxy nexus phone.
does not apply to my nexus 7 tablet.
any suggestions
Lemegeton300 said:
sorry but those instructions are for the samsung galaxy nexus phone.
does not apply to my nexus 7 tablet.
any suggestions
Click to expand...
Click to collapse
There's tonnes of older posts with all the info you'll need. Gotta just search more.
Ota will erase everything except your internal/external sd cards. Plus ota wont work if anything system wise had been altered. You'd have to Odin stock 4.2.2 then do ota.
No reason why you can't just flash a 4.3 rom like anything else tho.
And in all cases, wiping your data and apps is best. You gotta back it up. Restore after. Apps and their data anyway. Restoring system app data is never ever a good idea.
Sent from my cellular telephone
Device won't update via OTA with a custom recovery. And 4.3 OTA will fail if you're rooted. So in order to get OTA make sure you have stock recovery and unroot, then as long as you haven't modified anything system wise it should update successfully. And no, OTA updates will not wipe any data.
Sent from my Nexus 7 using xda premium
thanks everyone. its finally updated to 4.3. i backed up my data and then flashed the stock 4.3 image and that failed and the device would not boot. i thought it was bricked but it let me flash the 4.2.2. image and then the 4.3 OTA update worked.
:good::good::good::good::good:
hi guys i know that the previous reply was that flashing to the 4.2.2 worked then the OTA worked, however i have an explaination for people that were stuck like me
i JUST managed to upgrade my nexus 7 to 4.3 (JWR66Y)
i found a helpful link to upgrade from http://forum.xda-developers.com/showpost.php?p=34552123&postcount=1
after following all the steps, my i wasnt able to flash the bootloader (bootloader-grouper-4.23.img).
after doing some googling today, i found that it is the bootloader in the 4.3 update that is different (according to http://forum.xda-developers.com/showthread.php?t=2417097&page=2) and that you need the JWR66V bootloader img file (which is also the bootloader-grouper-4.23.img) they explain it in the link above, and have a download link for it there.
so in order to do the update, what you need to do is follow the steps from the 1st link (extract all the files etc in place), but before flashing, copy the bootloader from the 2nd link into your platform-tools folder, then follow the steps to flash.
as long as you follow the steps, and skip step 10, you will keep your data also
hope that helped
95Z28 said:
Device won't update via OTA with a custom recovery. And 4.3 OTA will fail if you're rooted. So in order to get OTA make sure you have stock recovery and unroot, then as long as you haven't modified anything system wise it should update successfully. And no, OTA updates will not wipe any data.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Per WugFresh's advice, if you're rooted and using stock reovery, you still can OTA update.
Link: http://www.wugfresh.com/nrt/faqs/
vndnguyen said:
Per WugFresh's advice, if you're rooted and using stock reovery, you still can OTA update.
Link: http://www.wugfresh.com/nrt/faqs/
Click to expand...
Click to collapse
Past OTAs would be successful when rooted, you would usually just lose root access. But the 4.3 OTA won't work while rooted, you'll just keep getting the failed message.
Sent from my Galaxy Nexus using xda premium
95Z28 said:
Past OTAs would be successful when rooted, you would usually just lose root access. But the 4.3 OTA won't work while rooted, you'll just keep getting the failed message.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
ok thanks. I'm on 4.3 and only root with stock recovery. So if the 4.4 available I will unroot and then OTA. Thanks!
Hi everyone, I'm having a hell of a time trying to update my phone from 4.2.2 to 4.3 (stock rom). I have searched the forums (or tried to) and have done general Google searches, but nothing with my problems came up. I rooted my phone a while back, lost root when my phone updated to 4.2.2, then used wugfresh's Nexus Root Toolkit to get it back. Ever since 4.3 came out, I have been unable to update. I was using TWRP, and when updating through the phone it would simply dump me back there and not continue. I was then instructed to manually flash through TWRP, which I tried to do, but halfway through the flash it simply stops. I believe it said "signature verification failed". Someone had me try using the NRT to push the update as well, but that hasnt worked either. It just fails.
After asking around some more, I was instructed to flash the stock recovery, which I have now done. Now when I try to update (through the phone), it takes me to stock recovery, starts installing the update, and (yet again) halfway through the android guy just has an X on it and it says "failed". With Kit Kat supposedly coming out in two days, I really want to be ready to get the update asap. Could anybody help me out?
Also, if possible I would like there to be a way to do so without losing the data on my phone. But its not necessary.
I am sorry if this same problem has come up before. I tried going through other threads and the ones suggested after typing in the thread title.
Why don't you just use the toolkit to bring you back to stock and unroot? Once that is done you will get the update OTA
I am on stock, and I am getting the update OTA. It is just failing to install every time I try to install the update.
Your did something wrong when going back to stock. Did you unroot and relock the boot loader?
Sent from my Nexus 4 using XDA Premium 4 mobile app
Or you can just flash all the .img file of the 4.3 using adb.
To blankit, no I did not unroot or relock the bootloader. I simply re-flashed the stock recovery. Relocking my bootloader would cause me to lose all my data, and by all accounts has nothing to do with installing updates. I will try disabling root access.
To arffrhn, flashing the .img through adb is what I have done through different toolkits. No matter how I have gone about trying to manually flash the 4.3img or install through the OTA update, it is failing.
To blankit, no I did not unroot or relock the bootloader. I simply re-flashed the stock recovery. Relocking my bootloader would cause me to lose all my data, and by all accounts has nothing to do with installing updates. I will try disabling root access.
To arffrhn, flashing the .img through adb is what I have done through different toolkits. No matter how I have gone about trying to manually flash the 4.3img or install through the OTA update, it is failing.
I did same thing without any problems after I unrooted and installed stock kernel.
Just use Wug toolkit and factory 4.3 image.
Now open image and extract radio, bootloader and system img.
Now use Wug and flash only these img.
Then reroot and start flashing custom kernel or roms.
Sent from my NookColor using Tapatalk 4
If everything else fail, do it manually.. Seek this thread.. http://forum.xda-developers.com/showthread.php?t=2010312.
Never do anything using toolkits.. Manual way is always the best.
this tool may help you:
Have you ever get into a situation where you have a custom recovery on a stock rom and then get a OTA update then you find out that you need to flash the stock recovery to flash?, well this Nexus 4 Stock Recovery Flasher will sort it all out.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2413550
I have a Nexus 7 (2012) with 4.4, rooted, TWRP 2.6.0.0. I'm trying to update to the 4.4.2 OTA update, but it's not working. Whether I run it from the system notification prompt or try to install the file manually (in /cache) via TWRP, it fails with this error:
"/system/fonts/Roboto-Bold.ttf" has unexpected contents.
Then it says there's an error executing the updater binary, an error flashing zip file, etc. All the standard stuff when it bombs out of an install.
I did change my font using ROM Toolbox Pro a while back, but I restored the original font and tried running it again. Still got the error. I tried downloading a fresh copy of the .ttf file and replacing the one in /system/fonts, but still got the error. It seems a little silly for the whole update to crash due to a font file, but whatever...
Can anyone help me figure out what's going on, and how to get this OTA to install properly? Thanks in advance!
Probably it's easier to flash the 4.4.2 factory image resp. system.img and boot.img of it manually than trying to recover the correct 4.4 state.
There are already some posts where I described how to do it and there is also a post in my blog describing the process.
Sent from my Nexus 7 using xda app-developers app
AndDiSa said:
Probably it's easier to flash the 4.4.2 factory image resp. system.img and boot.img of it manually than trying to recover the correct 4.4 state.
There are already some posts where I described how to do it and there is also a post in my blog describing the process.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Well, after every failure, it reboots and goes right back to functioning perfectly as it was on 4.4. But, I will consider the direct flash of 4.4.2 if no one else has any other suggestions. Thanks!
I got the 4.4.3 update notification and downloaded it. When it rebooted for the install, it went into TWRP recovery. Not sure what to do with that, I rebooted. Now I am still on 4.4.2 and getting the "up to date" when I check for updates.
I am rooted running stock ROM. Does being unlocked and rooted with custom recovery prevent an OTA install of updates?
I vevs
Sent from my Nexus 7 using XDA Premium 4 mobile app
I'm also looking for help updating to 4.4.3. I uninstalled Xposed and tried to flash the update zip with TWRP but the install failed. Does the update need to be installed via adb sideload?
Sent from my Nexus 7 using Tapatalk
When my n7 was on 4.3.1 stock rooted with unlock bootloader i updated via ota and twrp can handle it. I dont know about 4.4.3. There is a thread discussing this matter but i dont remmember where, i think is in the general. I never used side load but im using nrt nexus root toolkit for udpating to 4.4.3 and it work fine.
vs980
Same problem!!
Exactly same has happened to me. I got the notification for update than i downloaded it, it was about 70 mb , then rebooted my device, goes to TWRP recovery than what ?? I just restarted my device and in settings its still on 4.4.2 what to do Now ????
Hey all
What does TWRP stand for please?
I also got the notification to update to 4.3.3 but after downloading, when the installation began I got an error screen with the android dude lying on his back. I switched my nexus off and on again and I'm still on 4.2.2.
Now I get the same message when I check for updates.
How can I get my tablet to update again please?
My nexus is a regular unrooted tablet with the stock ROM that was installed via the previous ota update.
Many thanks
Sent from my Nexus 7 using XDA Free mobile app
hmmmm, sounds odd. same thing happened to me.
maybe TWRP(Team Win Recovery Project) cant handle it, or we should have updated it first. Or maybe we should have used CWM or Stock Recovery.
but the strange thing is that the tablet cannot find the update again!!
i'll try to update NRT (Nexus Root Toolkit) and see if i can update using that.
Don't install it, until there's an answer in http://forum.xda-developers.com/showthread.php?t=2786758 - a couple of us did install it, and we've lost root, but more importantly, recovery has been wiped, and I've been unable to reflash CWM with fastboot.
My wife and son got the 4.4.3 update notification on each of their 2012 Nexus 7 this morning. I told them not to install the update; I'll handle it when I get home this afternoon. My 2013 Wifi-only Nexus 7 needed to be on stock recovery in order to install the 4.4.3 OTA, so I assume the same is true for the 2012 Wifi-only Nexus 7. I'll do the same that I did for the 2013 N7:
1) restore stock recovery, 2) adb sideload the OTA or just install it from the tablet, then 3) re-install custom recovery and re-root.
Update: I installed stock recovery, then tried to download and install the update on the device, and got an "Error" message with Android on its back and an exclamation point in a red triangle. I long-pressed the power button to reboot and it's still on 4.4.2 and says it's up to date.
So, I downloaded the update to my computer and tried an adb sideload. When I did that and watched the update fail I saw the detailed error message that "/system/bin/debuggerd has unexpected contents". Probably something from an app requiring root. So, I downloaded the 4.4.2 factory image from the google developer's site, used 7zip to extract the system image file and flashed it to the device. After that I was able to adb sideload the update, then reinstalled TWRP. When I tried re-rooting using NRT, there was no SuperSU on the device, so I installed it from the Play Store and when I opened it I chose to install binaries through TWRP. When it booted into TWRP it immediately began flashing an old Titanium Backup file named "update.zip", which I did not want to happen. That screwed up a couple of apps, but nothing that couldn't easily be fixed. My lesson is to not leave any files named "update.zip" in the root directory.
GrillMouster said:
My wife and son got the 4.4.3 update notification on each of their 2012 Nexus 7 this morning. I told them not to install the update; I'll handle it when I get home this afternoon. My 2013 Wifi-only Nexus 7 needed to be on stock recovery in order to install the 4.4.3 OTA, so I assume the same is true for the 2012 Wifi-only Nexus 7. I'll do the same that I did for the 2013 N7:
1) restore stock recovery, 2) adb sideload the OTA or just install it from the tablet, then 3) re-install custom recovery and re-root.
Update: I installed stock recovery, then tried to download and install the update on the device, and got an "Error" message with Android on its back and an exclamation point in a red triangle. I long-pressed the power button to reboot and it's still on 4.4.2 and says it's up to date.
So, I downloaded the update to my computer and tried an adb sideload. When I did that and watched the update fail I saw the detailed error message that "/system/bin/debuggerd has unexpected contents". Probably something from an app requiring root. So, I downloaded the 4.4.2 factory image from the google developer's site, used 7zip to extract the system image file and flashed it to the device. After that I was able to adb sideload the update, then reinstalled TWRP. When I tried re-rooting using NRT, there was no SuperSU on the device, so I installed it from the Play Store and when I opened it I chose to install binaries through TWRP. When it booted into TWRP it immediately began flashing an old Titanium Backup file named "update.zip", which I did not want to happen. That screwed up a couple of apps, but nothing that couldn't easily be fixed. My lesson is to not leave any files named "update.zip" in the root directory.
Click to expand...
Click to collapse
good jub. But if we flash stock rom again, all our data will be lost. And backing up 32gb of data and restoring them each time is a pain in the a*s. I'm tired and sick of it. So this time, i'd rather not install the update, than having to reinstall all my apps and reconfigure them and copy files back and ....
So... To hell with 4.4.3 this time if it wont work properly.
But there is something in my mind.
Guys, how many of you have stickmount installed?
I remember an error coused by it. Maybe it is the reason the update failed...
hamid_valad said:
good jub. But if we flash stock rom again, all our data will be lost. And backing up 32gb of data and restoring them each time is a pain in the a*s. I'm tired and sick of it. So this time, i'd rather not install the update, than having to reinstall all my apps and reconfigure them and copy files back and ....
So... To hell with 4.4.3 this time if it wont work properly.
But there is something in my mind.
Guys, how many of you have stickmount installed?
I remember an error coused by it. Maybe it is the reason the update failed...
Click to expand...
Click to collapse
Flashing stock recovery.img and stock system.img does not wipe all my data. Everything was still there: all my media, files, apps, and app data.
I think you're right about the Stickmount app. I did have it on my son's tablet, and I had to flash system. Last night I updated my wife's tablet. She did not have Stickmount, so the OTA installed without me having to flash system. Just to be safe I did flash stock recovery first. I put TWRP back on and re-rooted after the OTA.