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.
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.
Hello,
My wife has a Nexus 4.
I unlocked the bootloader, flashed TWRP, rooted it, and installed busybox.
Yesterday she handed me her phone and it was sitting in TWRP.
She said she got a message saying there was an update and she clicked okay.
I asked her if she saw anything going on but she wasn't paying attention so I didn't know if the update was applied or not.
So... I just rebooted the system from within TWRP.
Looking at her "about phone" it still shows that she is on 4.2.1 and when I check for updates it says she is up to date.
Questions:
What to do now?
Why wasn't the update applied? ... in the past on my Nexus 7 I have done OTA updates with rootkeeper installed and TWRP applied them automatically.
Was the update file deleted from her phone or can I find it somewhere in TWRP and apply it?
Is it like a normal .zip that you install or is it another process?
I'm in the same situation, unsure what to do.
I don't want to have to to do a factory reset for a minor update.
EDIT: Also installing the OTA.ZIP in TWRP fails
Got there in the end:
a) If you want to keep your data & settings and are running the stock rom; only flash boot.img, system.img, and recovery.img (optional) with fastboot.
Here is the JOP40D factory image if you need it. occam-jop40d-factory-ca7602f0.tgz - 327.21 MB
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2145848
Once I did that i was able to flash the OTA.ZIP, no loss of data. I used wugfreshes tool for the flashing btw.
I lost root and my APN settings
alexroborock said:
Got there in the end:
http://forum.xda-developers.com/showthread.php?t=2145848
Once I did that i was able to flash the OTA.ZIP, no loss of data. I used wugfreshes tool for the flashing btw.
I lost root and my APN settings
Click to expand...
Click to collapse
There must be a better way to do this.
That is a huge security risk flashing someone else's untrusted image onto your phone.
What about adb sideload?
You can download the image directly from Google
Sent from my Nexus 4 using Tapatalk 2
You need stock recovery for the ota update to work.
Sent from my Nexus 4 using xda app-developers app
Got my N4 yesterday. Rooted stock 4.2.1, installed latest version of TWRP, setup google account. Got the update to 4.2.2 message and clicked ok.
My TWRP recovery installed the update automatically without any problems.
silverramsrt said:
Got my N4 yesterday. Rooted stock 4.2.1, installed latest version of TWRP, setup google account. Got the update to 4.2.2 message and clicked ok.
My TWRP recovery installed the update automatically without any problems.
Click to expand...
Click to collapse
Did you lose root?
Rizy7 said:
Did you lose root?
Click to expand...
Click to collapse
Yes. The update replaced the recovery_from_boot.p or whatever file and the insecure boot image I had. I just reflashed TWRP, did a factory reset and installed CM anyway.
I have a stock rooted Nexus 4 running Android 4.3 (JWR66V) and a custom recovery. Recently, the JWR66Y update showed up on my phone and I turned on OTA survival mode in SuperSU and proceeded to install the update. It booted into TWRP and proceeded to install up until a certain point but then it froze. I cancelled the installation and rebooted my device and I even got the "Updating Applications" indicator on the first boot. However, I checked the version and it was still on JWR66V and my device no longer shows an update available. I did the exact same thing with my Nexus 7 (2013) with the JWR66Q update and the same thing happened. Is there any way I can install an OTA update on a rooted device? Every time an update is available for one of my devices, I end up doing a full factory reset of my device to install an update. I have only been able to find things like Clean ROM and Shiny ROM and while I do appreciate the work these developers are doing for the community, I would prefer to be able to either download a fully stock and non-deodexed flashable zip for my device or find a way to install the OTA update without losing root. It would also be great if I could do so without a computer because I currently only have a Chromebook. Thank you very much.
Are you sure it was the update to the Y version? What did the file size show as in the system update notification? There have been 2 very small (1.8mb) updates which don't change the build number, maybe that's what you installed.
I am also stock rooted and have received each system update as usual, remember they take time to roll out world wide.
Sent from my Nexus 4 using Tapatalk 2
Nathanation said:
Are you sure it was the update to the Y version? What did the file size show as in the system update notification? There have been 2 very small (1.8mb) updates which don't change the build number, maybe that's what you installed.
I am also stock rooted and have received each system update as usual, remember they take time to roll out world wide.
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
Now that you mention it, I'm actually not sure. However the update didn't complete either way. It froze on a step involving the boot.img (sorry I can't remember exactly what it was doing). I don't really need a fix for it anymore as I have already manually installed the updates using a friends computer but I only know how to do so by flashing the factory image and losing all of my data along the way. But just so I know for future updates, do you use OTA Survival mode or OTA Rootkeeper or anything like that or do you simply install the update as you would on a non-rooted device? Thanks for your reply.
KeanuKe said:
Now that you mention it, I'm actually not sure. However the update didn't complete either way. It froze on a step involving the boot.img (sorry I can't remember exactly what it was doing). I don't really need a fix for it anymore as I have already manually installed the updates using a friends computer but I only know how to do so by flashing the factory image and losing all of my data along the way. But just so I know for future updates, do you use OTA Survival mode or OTA Rootkeeper or anything like that or do you simply install the update as you would on a non-rooted device? Thanks for your reply.
Click to expand...
Click to collapse
The root isn't the problem. The custom recovery is. You need to be on stock recovery for the update.
xda6969 said:
The root isn't the problem. The custom recovery is. You need to be on stock recovery for the update.
Click to expand...
Click to collapse
Can I fastboot flash the stock recovery after I've already flashed a custom recovery and still have root? And if the answer to that is "yes" will I still be rooted after the next OTA update?
I am having the same problem. Both my nexus 4 and 7 recieved an update (1.8MB) but it seems that i cannot get the update to install. Both devices were rooted using the Nexus Root Tool kit.
When i got the update the devices booted in recovery mode with TWRP. Do not know what to do. I saw no update in the baseband or build number.
I am running stock android.
Please advise
Hello, I'm in a bit of a confusing situation so I hope that someone can shed light on it.
Last night I got a notification that my phone is ready to install the 4.4 update. I didn't have the time or the battery to install it then, so I just left my phone until today. Today, I happily pressed the update button, my phone restarted, it started to update and when the bar was a little more then a third full it stopped and said "Error!" (Thanks for a very informative error message Google! ) I restarted my phone, and now my phone reports that it's up to date?! I tried tapping the Check now, but it keeps saying it's up to date. I checked my cache folder, and there is a .zip file containing the update.
My phone is rooted, I used the Nexus 4 Rootkit, but I DIDN'T install a custom recovery or try to install any custom ROMs. (I'm happy with the stock one) I only installed SuperSU so I can grant root access to some apps and that's it. I didn't install any tweaks.
Now if I'm not mistaken, the OTA update should have worked on my phone, because everything is stock. So why did this happen and why I'm not receiving the update prompt again?
Also as a side note: When I went into the fastboot mode and tried to launch the Recovery mode, it said "No command!" and I had restart my phone.
No, you're wrong. You should've gone to SuperSU app and pressed the "full unroot" button before trying to OTAupdate. This would've replaced the modified bin files for root by the original files, allowing the OTA to be applied successfully.
This happens because the rooting process modifies some system files, so the OTA detects a non-stock scenario and aborts its installation. Also when the OTA fails, a flag marks this update as a "fail update" so your system will continue to show you that it's "updated" as he thinks the only update available isn't suitable for you. He is just waiting for the next OTA update.
Now you have to install the OTA via sideload / adb. I would recommend to make a full nandroid backup before everything else. Then fully unroot your phone and apply the OTA using adb.
This is exactly what happened to me when trying to update from 4.2.2 to 4.3. I was root (obtained with Nexus 4 Toolkit from WugFresh) with stock recovery. Just root, nothing else. Then I tried to install OTA, because with older versions to be root was not a problem. But now it is, and my OTA failed as it failed to you.
Then I managed to manually apply the OTA doing what I told you: first backup, then unroot, and finally using the sideload / adb process button present in the toolkit, following its advices at each pont (very VERY well explained for non-experts). You will need to manually download the OTA update to 4.4. Look for that in these forums.
Hope this helps!
LORD MJ said:
Hello, I'm in a bit of a confusing situation so I hope that someone can shed light on it.
Last night I got a notification that my phone is ready to install the 4.4 update. I didn't have the time or the battery to install it then, so I just left my phone until today. Today, I happily pressed the update button, my phone restarted, it started to update and when the bar was a little more then a third full it stopped and said "Error!" (Thanks for a very informative error message Google! ) I restarted my phone, and now my phone reports that it's up to date?! I tried tapping the Check now, but it keeps saying it's up to date. I checked my cache folder, and there is a .zip file containing the update.
My phone is rooted, I used the Nexus 4 Rootkit, but I DIDN'T install a custom recovery or try to install any custom ROMs. (I'm happy with the stock one) I only installed SuperSU so I can grant root access to some apps and that's it. I didn't install any tweaks.
Now if I'm not mistaken, the OTA update should have worked on my phone, because everything is stock. So why did this happen and why I'm not receiving the update prompt again?
Also as a side note: When I went into the fastboot mode and tried to launch the Recovery mode, it said "No command!" and I had restart my phone.
Click to expand...
Click to collapse
nyepo said:
No, you're wrong. You should've gone to SuperSU app and pressed the "full unroot" button before trying to OTAupdate. This would've replaced the modified bin files for root by the original files, allowing the OTA to be applied successfully.
This happens because the rooting process modifies some system files, so the OTA detects a non-stock scenario and aborts its installation. Also when the OTA fails, a flag marks this update as a "fail update" so your system will continue to show you that it's "updated" as he thinks the only update available isn't suitable for you. He is just waiting for the next OTA update.
Now you have to install the OTA via sideload / adb. I would recommend to make a full nandroid backup before everything else. Then fully unroot your phone and apply the OTA using adb.
This is exactly what happened to me when trying to update from 4.2.2 to 4.3. I was root (obtained with Nexus 4 Toolkit from WugFresh) with stock recovery. Just root, nothing else. Then I tried to install OTA, because with older versions to be root was not a problem. But now it is, and my OTA failed as it failed to you.
Then I managed to manually apply the OTA doing what I told you: first backup, then unroot, and finally using the sideload / adb process button present in the toolkit, following its advices at each pont (very VERY well explained for non-experts). You will need to manually download the OTA update to 4.4. Look for that in these forums.
Hope this helps!
Click to expand...
Click to collapse
Thanks. Unfortunetly the OTA update failed even when I tired ADB sideload, so I had to flash the factory image. Now it works like a charm.
LORD MJ said:
Thanks. Unfortunetly the OTA update failed even when I tired ADB sideload, so I had to flash the factory image. Now it works like a charm.
Click to expand...
Click to collapse
It failed because you have modified files in your system, such as modified gps.conf or build.prop, custom kernel and non-official radio will give errors too.
I did a "flash stock+unroot" and relocked my device via the Wug app and it still errors
eksasol said:
It failed because you have modified files in your system, such as modified gps.conf or build.prop, custom kernel and non-official radio will give errors too.
Click to expand...
Click to collapse
I really have no idea how did that happen. Maybe some app modified it or I messed some things up. I'm now going to make a full backup of my phone, so I can apply the next OTA with much less pain.
LORD MJ said:
I really have no idea how did that happen. Maybe some app modified it or I messed some things up. I'm now going to make a full backup of my phone, so I can apply the next OTA with much less pain.
Click to expand...
Click to collapse
The OTA update can fail for many reasons, it could be due to any changes to the /system partition which is what root does, such as changes to gps.conf file, changes in build.prop, different kernel or radio.
If you're going to make a full backup, what you should do is flash a full factory image (link in my signature, and provided you already backup your data.) Then boot into a custom recovery to make a full backup, (not flash the recovery, but: fastboot boot twrp.img) When you do the backup make sure the boot (kernel) and recovery partition are selected. However, you can't backup the radio partition, but that should be fine unless you intend to use the LTE radio.
I have a similar problem. I have ROOTED device with TWRP recovery and stock 4.3 android (obtained OTA before rooting), and I just got notification that my OTA update to 4.4 is ready to be installed.
So I clicked Restart and Install button and the phone restarts(as it should) but after that it went in TWRP recovery and waited for some instruction I suppose. I didn't know what to click exactly, so I clicked Reboot from TWPR menu and it went in fastboot mode. From fastboot I chose Start and phone turns on. Updating didn't even start..
So, were there something that I could do when I was in TWRP recovery that could initiate updating process, or I never had a chance?
What exactly I should do to get that update on my phone? Sorry for my English and if was unclear.
Hello. I have a nexus 4 that until recently i was running on 4.3 with a custom kernel from faux123 and paranoid android rom and twrp custom recovery.
Finally i decided to update it to stock 4.4 for which i restored a nandroid i had made back when the phone had stock 4.3 on it. Also, the nandroid had happened to have stock rom but custom kernel (same faux123 one). Also, before restoring nandroid i made ti backup for my apps which i successfully restored after nandroid restore.
So now i decided to flash the default 4.3 kernel which i did successfully. Now i thought i was ready for the ota update since i had everything stock except recovery so i went ahead and checked for updates.
First up was jwr66y(before that i was on 66v) which successfully downloaded and installed. Then came the 240 mb 4.4 update which downloaded but while installing after reboot gave me the dead android with 'error' message.
I then rebooted the phone which works ok but shows 4.3 as my version and also tells me im already up to date on checking for updates. So now i decided to flash ota manually using zip. However now on booting in recovery, it doesnt take me to the TWRP screen but simply shows dead android with no command message.
Also, root seems to be gone. However rest of the phone works alright. How do i fix this and successfully install 4.4 kitkat? Please help. Also can anybody shed light on why it might have happened so i can prevent it in the future.
Sent from my Nexus 4 using xda app-developers app
Tinfoil Hat Tom said:
Hello. I have a nexus 4 that until recently i was running on 4.3 with a custom kernel from faux123 and paranoid android rom and twrp custom recovery.
Finally i decided to update it to stock 4.4 for which i restored a nandroid i had made back when the phone had stock 4.3 on it. Also, the nandroid had happened to have stock rom but custom kernel (same faux123 one). Also, before restoring nandroid i made ti backup for my apps which i successfully restored after nandroid restore.
So now i decided to flash the default 4.3 kernel which i did successfully. Now i thought i was ready for the ota update since i had everything stock except recovery so i went ahead and checked for updates.
First up was jwr66y(before that i was on 66v) which successfully downloaded and installed. Then came the 240 mb 4.4 update which downloaded but while installing after reboot gave me the dead android with 'error' message.
I then rebooted the phone which works ok but shows 4.3 as my version and also tells me im already up to date on checking for updates. So now i decided to flash ota manually using zip. However now on booting in recovery, it doesnt take me to the TWRP screen but simply shows dead android with no command message.
Also, root seems to be gone. However rest of the phone works alright. How do i fix this and successfully install 4.4 kitkat? Please help. Also can anybody shed light on why it might have happened so i can prevent it in the future.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Flash the complete 4.4 KRT16S factory image. Download from here and extract the zip to your adb/platform tools directory. Make sure your drivers are working properly. If you don't want your data wiped, edit flash-all.bat and remove -w. Connect your phone and boot into the bootloader (you can do this by opening cmd in adb directory and entering "adb reboot bootloader"). Now simply run the flash-all script and wait for it to complete. You are now on KitKat 4.4
Flash TWRP and anything else you want to flash. Download and flash the 4.4.2 update if you want.
Thanks a lot for the quick reply. I managed to get root and twrp back using wugfresh's kit. It seems to me that twrp is not good with OTAs(there is a page on their site re. this) which might be the reason for this mess.
So now instead of flashing the zip using adb, can i do it with twrp? I dont have much experience with adb since i have always used twrp. (I am not averse to using cmd but the 480 mb download for the sdk just to get adb and stuff puts me off).
Do I necessarily need to wipe my data to install the kitkat update?
Sent from my Nexus 4 using xda app-developers app