Database Users

Noob question about update

I hate to ask to questions here but im pretty desperate and confused. Ive tried searching for a solution to my problem but i cant seem to find a definite one.
I have a stock rooted Nexus 4 running on 4.2.1. Months ago, when the android 4.3 was first released, i disabled the OTA update notification somehow (forgot how!). Now when i tried chekcing for OTA update, my phone can only update to 4.2.2.
I did download the 4.2.2 update hoping that it might help my phone detect the 4.3 update after flashing it on my phone. But after flashing the 4.2.2 zip file using CWM, the installation failed due to some verification problem.
Now im at lost. I just want to update my phone to 4.3.
Do i need to unroot first? Or can i just manually update my phone through the computer using some toolkit or something?

Yes u will need to unroot your device first before it can be detected for an update. Since you already have cwmr+rooted; why not just download 4.3 stock image from Google site or from xda and flash it via cwmr? When installation fails; it could be due to bad download.
Sent from my Nexus 4 using Tapatalk
---------- Post added at 03:25 AM ---------- Previous post was at 03:24 AM ----------
Edit: for 4.3 make sure to download the 4.3 bootloader. Flash the boot loader before flashing 4.3 ROM.
Sent from my Nexus 4 using Tapatalk

My recommendation is to update to the latest recovery first, older recoveries will have issues with flashing: http://forum.xda-developers.com/showthread.php?t=1995440
Before you flash a rom, make sure to do a factory reset wipe.
If you want to flash stock 4.3 through CWM, go here: http://forum.xda-developers.com/showthread.php?t=2010887, it can receive OTA.
Or if you want to flash a clean factory image using fastboot: http://forum.xda-developers.com/showthread.php?t=2010312

eksasol said:
My recommendation is to update to the latest recovery first, older recoveries will have issues with flashing: http://forum.xda-developers.com/showthread.php?t=1995440
Before you flash a rom, make sure to do a factory reset wipe.
If you want to flash stock 4.3 through CWM, go here: http://forum.xda-developers.com/showthread.php?t=2010887, it can receive OTA.
Or if you want to flash a clean factory image using fastboot: http://forum.xda-developers.com/showthread.php?t=2010312
Click to expand...
Click to collapse
So do i just flash it through cwm like any other zip file? Sorry for asking too many questions. I used to know this stuff until i got busy with my studies.

I'm not sure what you mean by it. If its a rom.zip or a flashable package, then you can flash it through recovery. And if its not, it wouldn't work if you try anyway.

K if this is all confusing to you just download the toolkit, it will do everything for you.
If you wanna do manually; first download all the files to ur SD card.
1. Download latest cwm recovery (from above post)
2. Download 4.3 ROM
http://forum.xda-developers.com/showthread.php?t=2010887
3. Download 4.3 bootloader
https://www.copy.com/s/JniBu/4.3 files (mako)
Once you copy all these files to our SD card. Reboot to cwm recovery.
1. Flash latest cwm recovery
2. Reboot to recovery again
3. Wipe data/factory reset
4. Flash 4.3 bootloader
5. Flash 4.3 ROM
6. Wipe cache partition + dalvic
7. Reboot and enjoy
Sent from my Nexus 4 using Tapatalk

OTA update to 4.3 isnt available anymore. Atleast thats what my phone said yesterday when i was doing OTA from 4.2.2 to 4.3. "Only available untill Nov 3rd xx:yy AM" (dont remember exact time)

4.4 update problem

Can't update from 4.3 Using stock kernel ( swapped from franco to install the ota)
Tried CWM and TWRP, both fail.
here what happens: https://www.dropbox.com/s/6a1oesuwa3zgk1h/2013-11-14%2004.12.43.jpg?m

the same problem, the same CWM version

Not sure if it helps, but I followed this guide and now I am on KitKat

Download the JWR66Y factory image, extract everything and flash the system.img in fastboot mode, which should restore any changes made to the system partition. Try again after that

I'm having the same issue. I was on JWR66V and tried to update to 4.4 in cwm but it wanted me to be on JWR66Y... so after much hunting around I finally found a working JWR66Y flash able zip and was able to update to that.
However, I noticed that supersu got screwed up in the process, saying it couldn't find binaries. I downloaded and flashed the latest supersu, but that had no effect. I figured I would go ahead and try updating to 4.4 anyway and fix the root issue later...
The 4.4 update seemed to be going OK in cwm until I hit that same issue you did at about 75%. I've seen elsewhere that certain versions of supersu have been causing update problems. My only other thought is maybe I need to update my cwm to a newer version.

Eregoth said:
Download the JWR66Y factory image, extract everything and flash the system.img in fastboot mode, which should restore any changes made to the system partition. Try again after that
Click to expand...
Click to collapse
Why not getting directly the kitkat-image and flash boot.img and system.img in fastboot mode? No further update needed ...
Sent from my Nexus 7 using xda app-developers app

[Q] 4.4.2 Stock Recovery

Hey guys!
I saw last week that I had an OTA notification to update to 4.4.3 (currently running 4.4.2 KOT49H). I downloaded it and when I rebooted to install I figured out that I had TWRP 2.7 installed and that I couldn't install OTA updates with a custom recovery
So, I'm asking, is it possible to flash stock recovery back with odin and then install the OTA? And can someone please direct me to where I could get the stock recovery for 4.4.2?
All I've found in restoring the recovery is flashing a factory image (which would completely wipe my device), but hopefully that's not the only way
Thanks!

dragancla said:
Hey guys!
I saw last week that I had an OTA notification to update to 4.4.3 (currently running 4.4.2 KOT49H). I downloaded it and when I rebooted to install I figured out that I had TWRP 2.7 installed and that I couldn't install OTA updates with a custom recovery
So, I'm asking, is it possible to flash stock recovery back with odin and then install the OTA? And can someone please direct me to where I could get the stock recovery for 4.4.2?
All I've found in restoring the recovery is flashing a factory image (which would completely wipe my device), but hopefully that's not the only way
Thanks!
Click to expand...
Click to collapse
EDIT: Nevermind, found everything I needed with Unified Android Toolkit. If anyone needs the stock recovery, here it is: http://www.mediafire.com/download/1x5zbfo426lc0x5/recovery-stock-kot49h-razor.img
Now, another thing disturbs me: when I tried to update, it just showed me an icon with a broken down Droid and the text Error! beneath it. I'm not soft-bricked or anything, just that I couldn't update. Could it be because I flashed another kernel?

Razor is the 2013 model. You might want to mention that before people here download your link and ruin their grouper or tilapia....
Why wouldn't you just download the stock images straight from Google? You didn't need to downgrade anything and you don't use Odin with a nexus....
Sent from my Nexus 5

dragancla said:
EDIT: Nevermind, found everything I needed with Unified Android Toolkit. If anyone needs the stock recovery, here it is: http://www.mediafire.com/download/1x5zbfo426lc0x5/recovery-stock-kot49h-razor.img
Now, another thing disturbs me: when I tried to update, it just showed me an icon with a broken down Droid and the text Error! beneath it. I'm not soft-bricked or anything, just that I couldn't update. Could it be because I flashed another kernel?
Click to expand...
Click to collapse
Possibly...
Any modifications you may have made to your Nexus 7 (other then rooting and a Custom Recovery installed) will almost certainly cause an OTA to fail... as an OTA first runs a checksum verification test on all system files to ensure they are the original system files.
If they've been modified by the user, they cannot be 'patched', ie. updated... so the OTA aborts with no changes made.
Anyway... you really should be posting your question(s) here...
http://forum.xda-developers.com/nexus-7-2013
...as the Razor recovery you posted clearly identifies your device as a second generation Nexus 7(2013), and as @Pirateghost points out, posting that recovery in this forum could potentially mess up other peoples devices, if they were to flash it.
Rgrds,
Ged.

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

Android 5.0.0 to 5.0.1 Update

So I grabbed the 5.0.1 OTA, I have a rooted with custom recovery N4 with stock Lollipop, I flashed the 'KRT16O' (4.4.4) Stock recovery to 'Adb Sideload' the 5.0.1 OTA. I could not find Stock Lollipop recovery. It gives the error as shown in the picture attached, my opinion is that I should have Stock "Lollipop" Recovery to do that, RIght? Than What seems to be the problem?
Thanks in Advance...
UPDATE 1: Possible Solution
So, turns out you should be completely stock, means you should have stock recovery and NO ROOT. Stock Recovery can be Installed through 'Wugfresh' and unroot through SuperSu Setting. BUT, if you have modified even a single thing, YOU WILL A FACE ERROR as shown in the second screenshot. SO you will have to 'Fastboot Flash' the system.img from Factory image. I'm downloading The 5.0.0 Factory image right now and it will be downloaded by 2 hours.

alipashang77 said:
So I grabbed the 5.0.1 OTA, I have a rooted with custom recovery N4 with stock Lollipop, I flashed the 'KRT16O' (4.4.4) Stock recovery to 'Adb Sideload' the 5.0.1 OTA. I could not find Stock Lollipop recovery. It gives the error as shown in the picture attached, my opinion is that I should have Stock "Lollipop" Recovery to do that, RIght? Than What seems to be the problem?
Thanks in Advance...
Click to expand...
Click to collapse
You can get the stock recovery from the nexus factory images here . I would suggest just flashing the factory 5.0.1 image (don't flash userdata or cache and you should be fine).

I think OTA is only from 5.0.0 to 5.0.1.I'm having the same problem too and nobody seems to have an answer so I'll just get the factory images, flash all except user data
alipashang77 said:
So I grabbed the 5.0.1 OTA, I have a rooted with custom recovery N4 with stock Lollipop, I flashed the 'KRT16O' (4.4.4) Stock recovery to 'Adb Sideload' the 5.0.1 OTA. I could not find Stock Lollipop recovery. It gives the error as shown in the picture attached, my opinion is that I should have Stock "Lollipop" Recovery to do that, RIght? Than What seems to be the problem?
Thanks in Advance...
Click to expand...
Click to collapse

So what was Google supposed to change in 5.0.1? I think it was something important, but... I don't remember

You mean bringing silent mode back, getting a hold on the countless graphical glitches (yes, mine were all clean flashes) and maybe even grace us with a 3.10 kernel?
I was hoping on that as well, but it looks like we really are the rearmost wheel on the Google cart.

alipashang77 said:
So I grabbed the 5.0.1 OTA, I have a rooted with custom recovery N4 with stock Lollipop, I flashed the 'KRT16O' (4.4.4) Stock recovery to 'Adb Sideload' the 5.0.1 OTA. I could not find Stock Lollipop recovery. It gives the error as shown in the picture attached, my opinion is that I should have Stock "Lollipop" Recovery to do that, RIght? Than What seems to be the problem?
Thanks in Advance...
Click to expand...
Click to collapse
I had the same problem. I was on stock lollipop 5.0, rooted, with stock recovery. Tried sideloading the ota (for 5.0 > 5.0.1, about 18mb file) but it gave error. Turned out the mini sdk i was using was old version, 1.0.31. So I downloaded the newer version, 1.0.32, and then was able to update successfully.
Am attaching the rar file here, see if that helps

parkourz said:
So what was Google supposed to change in 5.0.1? I think it was something important, but... I don't remember
Click to expand...
Click to collapse
i dont know what they fixed or updated, i am seeing the same bugs that 5.0 had... still "slow" performance and the infinite recent task bug xD...

matiamb said:
i dont know what they fixed or updated, i am seeing the same bugs that 5.0 had... still "slow" performance and the infinite recent task bug xD...
Click to expand...
Click to collapse
I think it was something with security... but good to know that nothing has changed before flashing it

did we get a new kernel with 5.0 update?

alipashang77 said:
So I grabbed the 5.0.1 OTA, I have a rooted with custom recovery N4 with stock Lollipop, I flashed the 'KRT16O' (4.4.4) Stock recovery to 'Adb Sideload' the 5.0.1 OTA. I could not find Stock Lollipop recovery. It gives the error as shown in the picture attached, my opinion is that I should have Stock "Lollipop" Recovery to do that, RIght? Than What seems to be the problem?
Thanks in Advance...
Click to expand...
Click to collapse
I have the same problem. I definitely have Android 5.0, root and PhilZ Touch 6.46.3 recovery. So I found out that I have old one, the newest one is 6.58.0 BUT as author Phil3759 said, it is a dead project now and without further updates. So I will try the 6.58.0 and than other custom recovery.
EDIT: Recovery update did not help, still getting 4.4.2 fingerprint.

VinceCZ said:
I have the same problem. I definitely have Android 5.0, root and PhilZ Touch 6.46.3 recovery. So I found out that I have old one, the newest one is 6.58.0 BUT as author Phil3759 said, it is a dead project now and without further updates. So I will try the 6.58.0 and than other custom recovery.
Click to expand...
Click to collapse
I don't think I will work. Starting from lollipop, the update process is not like previous versions. It needs the system partitions to be completely unmodified. That includes the recovery partition and root to be hidden (temporary unroot in the supersu app). I tried to flash ota file with adb sideload and twrp and also cwm (both newest version) and failed. It can only be flashed successfully with stock recovery.

I heard what you are saying from more guys so I will try that.
EDIT: I made unroot and flashed stock recovery but getting error 7, which is basically the same as with custom recovery.

hk.happy said:
I had the same problem. I was on stock lollipop 5.0, rooted, with stock recovery. Tried sideloading the ota (for 5.0 > 5.0.1, about 18mb file) but it gave error. Turned out the mini sdk i was using was old version, 1.0.31. So I downloaded the newer version, 1.0.32, and then was able to update successfully.
Am attaching the rar file here, see if that helps
Click to expand...
Click to collapse
I have a rooted Nexus 4 (SuperSU installed), with stock recovery too. Can you tell me what's the easiest method to update from 5.0.0 to 5.0.1 and KEEP ROOT?

There is no solution yet.

VinceCZ said:
There is no solution yet.
Click to expand...
Click to collapse
Guys, for the ota to work you need to be unrooted and 100% stock recovery, system, and kernel.
Sent from my Nexus 5 using XDA Free mobile app

veketash said:
I have a rooted Nexus 4 (SuperSU installed), with stock recovery too. Can you tell me what's the easiest method to update from 5.0.0 to 5.0.1 and KEEP ROOT?
Click to expand...
Click to collapse
I'm not sure but I think it will break root no matter how you update from 5.0.0 to 5.0.1, and you will have to flash supersu zip again, but again, i'm not sure....

Unroot only and stock recovery is not enough, because than came install-recovery.sh error 7.

VinceCZ said:
Unroot only and stock recovery is not enough, because than came install-recovery.sh error 7.
Click to expand...
Click to collapse
Flash the system, recovery, and boot images from 5.0 in fastboot. Then try the ota
Sent from my Nexus 5 using XDA Free mobile app

I suppose it will delete user settings and all, will it not?

VinceCZ said:
I suppose it will delete user settings and all, will it not?
Click to expand...
Click to collapse
no, it won't delete anything.
Sent from my Nexus 5 using XDA Free mobile app