Database Users

[Q] OTA update to 4.2.2 problems

My 7 is unlocked and rooted, using Nexus Root Toolkit. I did an OTA to get to 4.2.1 some time ago and that went well. Root and unlock persisted. I am now getting OTA options for 4.2.2 from the System menu. First time I got and error in Android's belly. I restarted and was still in 4.2.1. System then said that I was up to date. A week or so later System told me again that OTA was available and I got the same result.
Any suggestions as to how I can do the update?

rsipson said:
My 7 is unlocked and rooted, using Nexus Root Toolkit. I did an OTA to get to 4.2.1 some time ago and that went well. Root and unlock persisted. I am now getting OTA options for 4.2.2 from the System menu. First time I got and error in Android's belly. I restarted and was still in 4.2.1. System then said that I was up to date. A week or so later System told me again that OTA was available and I got the same result.
Any suggestions as to how I can do the update?
Click to expand...
Click to collapse
You have two choices
1. Flash the stock 4.2.2 image using fastboot from here https://developers.google.com/android/nexus/images
Or
2. Flash this in CWM recovery (note this link is for the wifi model) http://android.clients.google.com/p....signed-nakasi-JDQ39-from-JOP40D.6ece895e.zip

You have to restore everything except relocking bootloader ... To be able to update ...when u finish ..just re-root
Sent from my Nexus 7 using xda premium

Same thing happened to me, I had to unroot and then root again after update.
Sent from my HTC Desire S using xda app-developers app

heat361 said:
You have two choices
1. Flash the stock 4.2.2 image using fastboot from here https://developers.google.com/android/nexus/images
Or
2. Flash this in CWM recovery (note this link is for the wifi model) http://android.clients.google.com/p....signed-nakasi-JDQ39-from-JOP40D.6ece895e.zip
Click to expand...
Click to collapse
Thanks for your post. I tried this using Clockwork and got a very long error message. I will quote part of it.
assert failed_apply_patch_check("/system/bin/debuggerd", "a2323a0c8 and a lot more
This is followed by error in file
I saw something about busybox changing some system files.
Any ideas??

How do I unroot without whipping all data?
Sent from my Nexus 7 using xda app-developers app

Search this forum for "OTA debugged"
There are only a few threads - read them all before you take any action.
This particular problem appears to be caused by StickMount.
You don't need to delete everything, nor do you need to flash the ENTIRE stock image - only the boot.img and system.img (via fastboot) without doing a factory reset or any other wiping.
This will unroot the ROM, and (of course) prevent StickMount from working. So you should over flash a SuperSU root kit afterwards (via custom recovery).
This very same problem may recur on the next OTA - so for goodness sake's, make a nandroid backup before you re-install StickMount and give it root privileges.

bftb0 said:
Search this forum for "OTA debugged"
There are only a few threads - read them all before you take any action.
This particular problem appears to be caused by StickMount.
You don't need to delete everything, nor do you need to flash the ENTIRE stock image - only the boot.img and system.img (via fastboot) without doing a factory reset or any other wiping.
This will unroot the ROM, and (of course) prevent StickMount from working. So you should over flash a SuperSU root kit afterwards (via custom recovery).
This very same problem may recur on the next OTA - so for goodness sake's, make a nandroid backup before you re-install StickMount and give it root privileges.
Click to expand...
Click to collapse
Sorry for being a numpty... can someone put the above into a mini step by step guide for me.. I'm stuggling with the terminology.
I rooted my Nexus and have since forgotten anything techie regarding it. I have StickMount and cannot update to 4.2.2..
How do i flash boot.img and system.img via fastboot, where do i get these files from, what versions etc do i need? And over flash SuperSU root kit?
What is OTA?
Basically, I think i need a newbie guide. I am techie enough to achieve most things normally.. i just don't know the android system at all, and what i did know to be able to root it i have completely forgotten!
Any guidance would be very much appreciated. Cheers.

[Q] OTA Updates with Root

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

[Q] Downloaded 4.4.3 but not installed

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.

Issue updating to Android 5.0

I get this error while trying to attempt to update to the latest android 5.0 in twrp...
while installing the new zip file it says:
package expects build fingerprint of google/mantaray/manta: 4.4.4/ktu84p/1227136: user/release-keys or google/mantaray/manta:5.0/LRX21P/1570855:user/release-keys; this device has google/mantaray/manta:4.3/JWR66V/737497:user/release-keys
but my nexus 10 is already on 4.4.4

Your build.prop isn't standard, get the original one, or just use the factory image to update.

Rusty! said:
Your build.prop isn't standard, get the original one, or just use the factory image to update.
Click to expand...
Click to collapse
what i need to install to correct his to the correct build.prop of 4.4.4?
ps. my last 4.4.4 was updated directly OTA..

Just download the 5.0 factory image, remove -w from the flash-all script and it will update you. Less dicking around that way.

inspiron41 said:
I get this error while trying to attempt to update to the latest android 5.0 in twrp...
while installing the new zip file it says:
package expects build fingerprint of google/mantaray/manta: 4.4.4/ktu84p/1227136: user/release-keys or google/mantaray/manta:5.0/LRX21P/1570855:user/release-keys; this device has google/mantaray/manta:4.3/JWR66V/737497:user/release-keys
but my nexus 10 is already on 4.4.4
Click to expand...
Click to collapse
Exactly the same here when flashing OTA via TWRP.
The build.prop file hasn't been modified as far as I know.
Where/how to get the file please?

CBers said:
Exactly the same here when flashing OTA via TWRP.
The build.prop file hasn't been modified as far as I know.
Where/how to get the file please?
Click to expand...
Click to collapse
I found the best way around this is to install the factory nexus 10 lollipop version. It's actually quite easy or even easier than the OTA method. Just make sure you delete the -w from the .bat file to keep all your data. It worked perfectly for me.
Sent from my Nexus 5 using XDA Free mobile app

inspiron41 said:
I found the best way around this is to install the factory nexus 10 lollipop version. It's actually quite easy or even easier than the OTA method. Just make sure you delete the -w from the .bat file to keep all your data. It worked perfectly for me.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Thanks inspiron41 - I'll give it a go at the weekend.
Which file is the -w in please?

CBers said:
Thanks inspiron41 - I'll give it a go at the weekend.
Which file is the -w in please?
Click to expand...
Click to collapse
Go to this website:
http://www.androidpolice.com/2013/1...riants-of-nexus-7-2012-and-2013-and-nexus-10/
It has detail instruction and jump down to step 3 regarding to -w
Sent from my Nexus 5 using XDA Free mobile app

I was having the same issue as the OP. So after reading this thread, I've performed the following:
Downloaded Android 5.0 factory image from: https://developers.google.com/android/nexus/images
Followed the instructions at this site, AND MADE SURE TO REMOVE '-w' AS INSTRUCTED, TO PRESERVE DATA: http://www.androidpolice.com/2013/1...riants-of-nexus-7-2012-and-2013-and-nexus-10/
It was pretty easy. I've been waiting about 30 minutes looking at the boot graphic. Hope it turns out OK. But it is easier than playing with the OTA.

After being stuck in a bootloop, I had to factory reset and now all is well.
Sent from my HTC One using Tapatalk

Darnell_Chat_TN said:
After being stuck in a bootloop, I had to factory reset and now all is well.
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
...i've been having the same issue since the 5.0.0 update.
I even had to perform a total wipe to get 5.0.0 onto my N10, and even after that I still have a bad signature on my tablet. Now the problem is back installing 5.0.2 OTA, and I do not want to wipe everything again. So please where is that build.prop file, and how do I fix it? or rather, what the eff has gone wrong here, why, and who's responsible for unbreaking it?

[Lemmy] said:
...i've been having the same issue since the 5.0.0 update.
I even had to perform a total wipe to get 5.0.0 onto my N10, and even after that I still have a bad signature on my tablet. Now the problem is back installing 5.0.2 OTA, and I do not want to wipe everything again. So please where is that build.prop file, and how do I fix it? or rather, what the eff has gone wrong here, why, and who's responsible for unbreaking it?
Click to expand...
Click to collapse
Yea, I flashed the 5.0.1 factory image later. Now, I tried to flash the 5.0.2 OTA and it said it saw a 5.0.1 signature and was expecting 5.0.1, or something of that sort. It's basically the same issue all over again... No issues flashing 5.0.2 to my kids' N7s that are 100% stock.
My N10 is unlocked and rooted. There must be something in the customizations that cause this issue.

Darnell_Chat_TN said:
Yea, I flashed the 5.0.1 factory image later. Now, I tried to flash the 5.0.2 OTA and it said it saw a 5.0.1 signature and was expecting 5.0.1, or something of that sort. It's basically the same issue all over again... No issues flashing 5.0.2 to my kids' N7s that are 100% stock.
My N10 is unlocked and rooted. There must be something in the customizations that cause this issue.
Click to expand...
Click to collapse
and again, trying to flash the 5.1 OTA and it says there is a 4.4.2 signature so it wont install... but I have re-flashed the stock image several times by now. I just do not get it.

[Lemmy] said:
and again, trying to flash the 5.1 OTA and it says there is a 4.4.2 signature so it wont install... but I have re-flashed the stock image several times by now. I just do not get it.
Click to expand...
Click to collapse
Why not just update using the 5.1 factory image? I run unlocked stock/rooted on my N10, and that's the method I always use to update. Would also do it this way on my N5 and now N6. Just fastboot flash all the images from the factory image manually (READ: EXCEPT USERDATA). You can also skip flashing the recovery if you run a custom recovery. However, for the sake of completion, I include flashing the stock recovery. Then I let it boot up normally. Then I'll boot back into the bootloader and flash TWRP and flash SuperSU. Updating this way is easier for me since I don't have to worry about the OTA failing due to customizations I may have made to the system (especially now with the new way Android updates after 5.0).

I've already had to upgrade my tablet by flashing stock for the last three upgrades, and every single time I ended up havnig to wipe the tablet clean and install and configure everything from scratch. I'm still hoping that at some point I wouldn't have to do that anymore...
---------- Post added at 08:57 AM ---------- Previous post was at 08:49 AM ----------
could this all be because my tablet is rooted and has CWM recovery installed?

[Lemmy] said:
I've already had to upgrade my tablet by flashing stock for the last three upgrades, and every single time I ended up havnig to wipe the tablet clean and install and configure everything from scratch. I'm still hoping that at some point I wouldn't have to do that anymore...
---------- Post added at 08:57 AM ---------- Previous post was at 08:49 AM ----------
could this all be because my tablet is rooted and has CWM recovery installed?
Click to expand...
Click to collapse
That's weird. I can't remember the last time I had issues using the stock images, and most people seem to be okay doing it. How are you flashing it? I follow Method 2 from this OP: http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008. I just skip the command that flashes userdata, and it always works. I always flash the new cache image because when I would just erase it, it would be forever stuck in the bootanimation.
Before 5.0, being rooted didn't affect upgrading via OTA. Now, however, any little modification to the system (including being rooted) will cause the OTA to fail everytime. Also using a custom recovery like CWM will cause it to fail. So if you really want to go the OTA route, the least you would have to do is completely unroot (inside the SuperSU app itself) and flash the stock recovery. If you've uninstalled any system apps, you have to reinstall them or it will also fail.

charesa39 said:
That's weird. I can't remember the last time I had issues using the stock images, and most people seem to be okay doing it. How are you flashing it? I follow Method 2 from this OP: http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008. I just skip the command that flashes userdata, and it always works. I always flash the new cache image because when I would just erase it, it would be forever stuck in the bootanimation.
Before 5.0, being rooted didn't affect upgrading via OTA. Now, however, any little modification to the system (including being rooted) will cause the OTA to fail everytime. Also using a custom recovery like CWM will cause it to fail. So if you really want to go the OTA route, the least you would have to do is completely unroot (inside the SuperSU app itself) and flash the stock recovery. If you've uninstalled any system apps, you have to reinstall them or it will also fail.
Click to expand...
Click to collapse
My N10 is with stock ROM 5.0.1 and stock recovery but rooted with unlocked bootloader (and custom launcher). I have two questions:
1) I can unroot it through SuperSU. Do I have to switch back to the stock launcher before trying the OTA installation of 5.1?
2) I remember last time I could gain root by simply installing SuperSU. After flashing the 5.1 factory image, can I still get root this same way, or do I have to install, for example, TWRP and then flash SuperSU?
Thanks!

mj56gt said:
My N10 is with stock ROM 5.0.1 and stock recovery but rooted with unlocked bootloader (and custom launcher). I have two questions:
1) I can unroot it through SuperSU. Do I have to switch back to the stock launcher before trying the OTA installation of 5.1?
2) I remember last time I could gain root by simply installing SuperSU. After flashing the 5.1 factory image, can I still get root this same way, or do I have to install, for example, TWRP and then flash SuperSU?
Thanks!
Click to expand...
Click to collapse
1) No, you can keep whichever launcher you are using whether it be Trebuchet, Google Now Launcher, Nova, etc. since it's more of just an app and not a system mod.
2) As far as I know (or thought), you've always had to flash SuperSU using a custom recovery unless your ROM already came pre-rooted. In which case, all you would have to do is install SuperSU from the Play Store. But to answer your question, after flashing the factory image, you would have to flash a custom recovery like TWRP and then flash SuperSU using said custom recovery. However, that's not complicated at all. After flashing the factory image, it just takes like another 5 minutes to flash TWRP, boot into it, flash SuperSU, boot into the OS, verify root status, then power off, boot back into the bootloader and flash the stock recovery (if you don't want to keep the custom recovery). While you're at it, after flashing SuperSU, why not flash the Translucent Nav/Status Bar Mod found here: http://forum.xda-developers.com/showthread.php?t=2771708 provided by @hanspampel. He's done a great service for us. It's the easiest and best mod for the stock N10 right now that restores the translucent decor that Google decided to disable on our device. I flashed it on my N10 after upgrading to 5.1 and it works flawlessly. But that's just a suggestion.

charesa39 said:
1) No, you can keep whichever launcher you are using whether it be Trebuchet, Google Now Launcher, Nova, etc. since it's more of just an app and not a system mod.
2) As far as I know (or thought), you've always had to flash SuperSU using a custom recovery unless your ROM already came pre-rooted. In which case, all you would have to do is install SuperSU from the Play Store. But to answer your question, after flashing the factory image, you would have to flash a custom recovery like TWRP and then flash SuperSU using said custom recovery. However, that's not complicated at all. After flashing the factory image, it just takes like another 5 minutes to flash TWRP, boot into it, flash SuperSU, boot into the OS, verify root status, then power off, boot back into the bootloader and flash the stock recovery (if you don't want to keep the custom recovery). While you're at it, after flashing SuperSU, why not flash the Translucent Nav/Status Bar Mod found here: http://forum.xda-developers.com/showthread.php?t=2771708 provided by @hanspampel. He's done a great service for us. It's the easiest and best mod for the stock N10 right now that restores the translucent decor that Google decided to disable on our device. I flashed it on my N10 after upgrading to 5.1 and it works flawlessly. But that's just a suggestion.
Click to expand...
Click to collapse
Thanks a lot for the suggestions! Have a wonderful weekend...

Never mind

[Q] No Lollipop OTA

Hi all
By now, I would assume that Google has finished the rollout of the lollipop OTA for the Nexus 4 (mako)
but I have a problem
Short Story
I still don't have lollipop OTA because Google thinks I'm rooted
Long Story
My brand new Nexus 4 (arrived 3 days ago) came with 4.2.2
I opened the box and immediately unlocked the bootloader (fastboot oem unlock) and then installed twrp (fastboot flash recovery openrecovery............img)
After that, I went into twrp to check if it was flashed correctly, and it worked fine BUT as I was about to reboot, twrp asked if i wanted to install SuperSU and I accidentally pressed "yes".
after the phone booted, I found it wasn't acually rooted but it installed an app called "SuperSU Installer"
I ignored it, and went through 4 ota updates (from 4.2.2 to 4.4.2) and the otas stopped (there was not updates available after 4.4.2)
After the updates, I found that the ota have removed twrp and was overwritten by stock recovery SO I went back to bootloader and flashed twrp again (which worked just fine).
Then I done some seaching on Google and found that I'm not getting lollipop becasue I have some traces of rooting (the "SuperSu Installer" that somehow managed to survive 4 OTA's)
I went no to flash the full root (the actual SuperSu) and then do a "Full Unroot" from there (worked fine) and the phone is now unrooted.
BUT still not Lollipop OTA
I gave up and tried to do the update manually (Downloaded flashalbe ZIP from Android Police) but TWRP refuses to flash it
The question is, what to do now?

http://forum.xda-developers.com/showthread.php?t=2807446
Don't wait for Google. I have been running L for months now.
Sent from my Nexus 4 using Tapatalk

AgEnT x19 said:
Hi all
By now, I would assume that Google has finished the rollout of the lollipop OTA for the Nexus 4 (mako)
but I have a problem
Short Story
I still don't have lollipop OTA because Google thinks I'm rooted
Long Story
My brand new Nexus 4 (arrived 3 days ago) came with 4.2.2
I opened the box and immediately unlocked the bootloader (fastboot oem unlock) and then installed twrp (fastboot flash recovery openrecovery............img)
After that, I went into twrp to check if it was flashed correctly, and it worked fine BUT as I was about to reboot, twrp asked if i wanted to install SuperSU and I accidentally pressed "yes".
after the phone booted, I found it wasn't acually rooted but it installed an app called "SuperSU Installer"
I ignored it, and went through 4 ota updates (from 4.2.2 to 4.4.2) and the otas stopped (there was not updates available after 4.4.2)
After the updates, I found that the ota have removed twrp and was overwritten by stock recovery SO I went back to bootloader and flashed twrp again (which worked just fine).
Then I done some seaching on Google and found that I'm not getting lollipop becasue I have some traces of rooting (the "SuperSu Installer" that somehow managed to survive 4 OTA's)
I went no to flash the full root (the actual SuperSu) and then do a "Full Unroot" from there (worked fine) and the phone is now unrooted.
BUT still not Lollipop OTA
I gave up and tried to do the update manually (Downloaded flashalbe ZIP from Android Police) but TWRP refuses to flash it
The question is, what to do now?
Click to expand...
Click to collapse
A couple of things, you'll get the ota if your rooted, it just won't flash. The other is you can't flash the ota update zip in twrp. You need to sideload it in the stock recovery. You have to 100% stock and not rooted for it to flash. Otherwise it will fail
Sent from my Nexus 9 using XDA Free mobile app

jd1639 said:
A couple of things, you'll get the ota if your rooted, it just won't flash. The other is you can't flash the ota update zip in twrp. You need to sideload it in the stock recovery. You have to 100% stock and not rooted for it to flash. Otherwise it will fail
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
Thanks for your reply
I think I will wipe everything and install factory image since I didn't install anything on it yet
I assume it will make the phone 100% stock (just like it was in its box)
right?

AgEnT x19 said:
Thanks for your reply
I think I will wipe everything and install factory image since I didn't install anything on it yet
I assume it will make the phone 100% stock (just like it was in its box)
right?
Click to expand...
Click to collapse
Yep. Just flash the 5.0.1 factory image. You should be able to use the flash-all.bat in the factory image. It will wipe your device but since you haven't set anything up that shouldn't be a problem
Sent from my Nexus 9 using XDA Free mobile app

jd1639 said:
Yep. Just flash the 5.0.1 factory image. You should be able to use the flash-all.bat in the factory image. It will wipe your device but since you haven't set anything up that shouldn't be a problem
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
you mean flash-all.sh
I mainly use Linux
Anyway, thanks for your help

AgEnT x19 said:
you mean flash-all.sh
I mainly use Linux
Anyway, thanks for your help
Click to expand...
Click to collapse
That'll work too
Sent from my Nexus 9 using XDA Free mobile app

So I just got my mako few days ago....came with JB stock immediately updated to kk but nothing since. Its been 6 days without a notification for lp. Any ideas besides flashing factory.IMG and I tried the play services trick also.

aaronrw said:
So I just got my mako few days ago....came with JB stock immediately updated to kk but nothing since. Its been 6 days without a notification for lp. Any ideas besides flashing factory.IMG and I tried the play services trick also.
Click to expand...
Click to collapse
You have two choices
1. Wait for the OTA (you will eventually get lollipop)
2. Update manually by following this great guide
http://www.reddit.com/r/Android/comments/2mgh8o/nexus_4_lollipop_ota_link_and_update_guide/
Note: The above method is exactly like updating from Setting>About Phone>System Updates (i.e. All your apps, data, files....etc will be kept)
BUT is different from flashing factory image (which completely wipes the phone making it just like it was in its box)