Database Users

[TUT] Getting a clean 4.1.1 Experience - Steps to Flash Stock 4.0.4 and then 4.1.1

First up, let me tell you that doing this is not necessay to get the OTA or having a smooth JB experience. The JB OTA installs without a wipe which means the data is preserved.
UPDATE: Google has put up the full image for 4.1.1 [i9023, i9020a and i9020t] . Now you do not need to clean flash ICS and then JB. Follow the part 1 of the guide below and flash the JB image instead of ICS. Nothing more to it.
Thanks anshumandash for pointing it out
That being said, I wanted to have the real stock image on my Nexus S and then Upgrade to JellyBean. Below are the steps that I took.
Go to this GoogleAndroidImages page and download the appropriate image for your phone & download. Since mine is an international version a.k.a I9023, I chose that ROM.
The download will be a tar.gz file. Use a utility like 7Zip to uncompress it. The tar.gz will have a .tar file inside and the /tar file will have a folder. Extract the folder to your PC. For my download, the folder was named soju-imm76d
Next Steps will wipe your phone, completely
Reboot your phone into bootloader mode.
Open a command prompt, navigate to the folder in step 2.
Enter the below commands, the image file names are for my download, modify it to the file names in your folder before running (I assume that you have fastboot working)
fastboot flash bootloader bootloader-crespo-i9020xxkl1.img
fastboot reboot-bootloader
fastboot flash radio radio-crespo-i9020xxki1.img
fastboot reboot-bootloader
fastboot -w update image-soju-imm76d.zip​
After the last step, the phone reboots and takes you to the initial setup screen.
Additionally, I reflashed CWM and the the JellyBean OTA along with superuser. Below are the steps for that
Download the OTA from google server. This thread by oldblue910 is kept updated with the latest updates. Currently it has OTA's for I9023 and I9020A
Download the superuser from androidsu website. This is the RC version 3.2
Download the latest clocworkmod recovery touch-version non-touch-version
For simplicity sake, put all the files downloaded at a single folder
Reboot phone into bootloader mode.
Open a command prompt and go to the folder in step 4.
Now execute this fastboot command to flash the CWM recovery. Change the filename to the file you have downloaded.
fastboot flash recovery recovery-clockwork-6.0.0.7-crespo.img​
Now using the vol down key choose to go to recovery.
There, using the options, navigate to the install zip from sdcard and first install the OTA and then the superuser zip file.
Reboot. You now have rooted JB
PS: I additionally did a fastboot oem lock and fastboot oem unlock back to back to wipe my sdcard too
Reason for this post?
Originally Posted by dEris
Because if you're not on stock 4.0.4 image, you cannot flash the OTA zip. You get a Status 7 error.
This isn't "his" way. It's the official Google way if you go to the Google site to download stock images
Click to expand...
Click to collapse

Whats the difference/benefits between ur "way" and just flashing JB zip with proper clean install?
thanks in advance ;-]

greg2826 said:
Whats the difference/benefits between ur "way" and just flashing JB zip with proper clean install?
thanks in advance ;-]
Click to expand...
Click to collapse
Because if you're not on stock 4.0.4 image, you cannot flash the OTA zip. You get a Status 7 error.
This isn't "his" way. It's the official Google way if you go to the Google site to download stock images.

I think this was the exact way I did it as well:thumbup: I must have skipped one step during the process though because my "SD" didn't get wiped.

turchs
This doesn't apply to the i9020a Nexus S
-_-

karleeezy said:
This doesn't apply to the i9020a Nexus S
-_-
Click to expand...
Click to collapse
Yes it does! I9020A OTA in the thread below!
http://forum.xda-developers.com/showthread.php?t=1736645

dEris said:
Because if you're not on stock 4.0.4 image, you cannot flash the OTA zip. You get a Status 7 error.
This isn't "his" way. It's the official Google way if you go to the Google site to download stock images.
Click to expand...
Click to collapse
ok got it
my thanks went 2 u

Couldn't you just do a factory reset after installing the OTA package?

Thank you, your tutorial was helpful. Needed to go back to stock.

FirePoncho86 said:
Yes it does! I9020A OTA in the thread below!
http://forum.xda-developers.com/showthread.php?t=1736645
Click to expand...
Click to collapse
Got it! Thanks, dude!

jithinsarath said:
First up, let me tell you that doing this is not necessay to get the OTA or having a smooth JB experience. The JB OTA installs without a wipe which means the data is preserved.
That being said, I wanted to have the real stock image on my Nexus S and then Upgrade to JellyBean. Below are the steps that I took.
Go to this GoogleAndroidImages page and download the appropriate image for your phone & download. Since mine is an international version a.k.a I9023, I chose that ROM.
The download will be a tar.gz file. Use a utility like 7Zip to uncompress it. The tar.gz will have a .tar file inside and the /tar file will have a folder. Extract the folder to your PC. For my download, the folder was named soju-imm76d
Next Steps will wipe your phone, completely
Reboot your phone into bootloader mode.
Open a command prompt, navigate to the folder in step 2.
Enter the below commands, the image file names are for my download, modify it to the file names in your folder before running (I assume that you have fastboot working)
fastboot flash bootloader bootloader-crespo-i9020xxkl1.img
fastboot reboot-bootloader
fastboot flash radio radio-crespo-i9020xxki1.img
fastboot reboot-bootloader
fastboot -w update image-soju-imm76d.zip​
After the last step, the phone reboots and takes you to the initial setup screen.
Additionally, I reflashed CWM and the the JellyBean OTA along with superuser. Below are the steps for that
Download the OTA from google server
Download the superuser from androidsu website. This is the RC version 3.2
Download the latest clocworkmod recovery touch-version non-touch-version
For simplicity sake, put all the files downloaded at a single folder
Reboot phone into bootloader mode.
Open a command prompt and go to the folder in step 4.
Now execute this fastboot command to flash the CWM recovery. Change the filename to the file you have downloaded.
fastboot flash recovery recovery-clockwork-6.0.0.7-crespo.img​
Now using the vol down key choose to go to recovery.
There, using the options, navigate to the install zip from sdcard and first install the OTA and then the superuser zip file.
Reboot. You now have rooted JB
PS: I additionally did a fastboot oem lock and fastboot oem unlock back to back to wipe my sdcard too
Click to expand...
Click to collapse
Well written. I'm sure you helped hundreds of stressed out newcomers with this. :laugh:

chronophase1 said:
I must have skipped one step during the process though because my "SD" didn't get wiped.
Click to expand...
Click to collapse
yeah.. the fastbbot oem lock and fastboot oem unlock after the 4.0.4 flash wipes the SD
rhadrio said:
Couldn't you just do a factory reset after installing the OTA package?
Click to expand...
Click to collapse
The OTA is essentially an upgrade, it builds atop the existing ICS 4.0.4 rom. I had so much mods on top of my rom that I wasnted to have a clean start. Besides, there has been multiple reports of an error 7 in case of non stock or certain moded roms.
karleeezy said:
Got it! Thanks, dude!
Click to expand...
Click to collapse
Glad I could help
I am already missing the various tweaks I had on the CM9 RC2 and other mods

jithinsarath said:
yeah.. the fastbbot oem lock and fastboot oem unlock after the 4.0.4 flash wipes the SD
Click to expand...
Click to collapse
Thanks for the tutorial. Thinking of doing the update this way. I have a i9020a rooted with 4.0.4 and when I try to do OTA update I got signature verification error in CWM 5.8.0.2.
For the wipe, from what I understand, you just execute the lock command above which wipes the SD and then unlock it with the second command? Sorry total newbie on this.

That is exactly what i did when the OTA zip pacage first showed up here on xda. Good guide. Im rocking mine with simple kernel

I followed the first part of the guide to restore to stock, and then did the OTA update. It all went well except one little catch: after the OTA update for 4.1.1, I flashed the CWM 6.0.0.7, and then realize that I forgot to copy the root zip file onto SD. Had to reboot the phone and copy the file over. After that I go into bootload mode again and try to go to recovery, ends up with a red exclaim mark and phone is locked. Had to do a battery pull, restart the phone, and then reflash that CWM image, and immediately after that, go to recovery and do the root zip install. Not sure why is that. Have not tried to do the recovery again but I'm glad that I'm now on JB and rooted. Thanks OP !

I keep gettin status 7 error.
When i install the OTA through the phone itself (by letting it restart the phone and install it) i get the exclamation mark.
Im on Stock 4.0.4 and not rootet. Is there anyway to install this OTA without fully wipe it?

d960 said:
Thanks for the tutorial. Thinking of doing the update this way. I have a i9020a rooted with 4.0.4 and when I try to do OTA update I got signature verification error in CWM 5.8.0.2.
For the wipe, from what I understand, you just execute the lock command above which wipes the SD and then unlock it with the second command? Sorry total newbie on this.
Click to expand...
Click to collapse
The lock command just lock the bootloader, it is the unlock command that will wipe the SD. It will also ask you for a confirmation on your phone's screen...
d960 said:
I followed the first part of the guide to restore to stock, and then did the OTA update. It all went well except one little catch: after the OTA update for 4.1.1, I flashed the CWM 6.0.0.7, and then realize that I forgot to copy the root zip file onto SD. Had to reboot the phone and copy the file over. After that I go into bootload mode again and try to go to recovery, ends up with a red exclaim mark and phone is locked. Had to do a battery pull, restart the phone, and then reflash that CWM image, and immediately after that, go to recovery and do the root zip install. Not sure why is that. Have not tried to do the recovery again but I'm glad that I'm now on JB and rooted. Thanks OP !
Click to expand...
Click to collapse
when you rebooted the phone to copy the su.zip, the OS restored the oroginal recovery. That's why you got the red exclamation mark. To get the CWm, you can flash it again in fast boot, go into recovery and then ask the CWM to reboot.. if it is 6.0.0.7, before reboot it will ask for the recovery to be made overwrite proof (a nice new feature in v6), choose yes and you are good to go..

alireza_simkesh said:
I keep gettin status 7 error.
When i install the OTA through the phone itself (by letting it restart the phone and install it) i get the exclamation mark.
Im on Stock 4.0.4 and not rootet. Is there anyway to install this OTA without fully wipe it?
Click to expand...
Click to collapse
Status 7 error comes when you have some kind of custom rom or may be some core mod applied to your rom. I am not aware of a way to get this proceed without full wipe: You can try the below though:
1. Flash the stock 4.0.4 for your phone without data wipe (you can wipe the dalvik cache though). This will make sure you are on the "stock".
2. Try the OTA
or you can backup using titanium backup, and then follow my guide. Restore the apps after flashing 4.0.4 and the try OTA.
It will be good it you take a nandroid backup before doing either of the above.

jithinsarath said:
Status 7 error comes when you have some kind of custom rom or may be some core mod applied to your rom. I am not aware of a way to get this proceed without full wipe: You can try the below though:
1. Flash the stock 4.0.4 for your phone without data wipe (you can wipe the dalvik cache though). This will make sure you are on the "stock".
2. Try the OTA
or you can backup using titanium backup, and then follow my guide. Restore the apps after flashing 4.0.4 and the try OTA.
It will be good it you take a nandroid backup before doing either of the above.
Click to expand...
Click to collapse
Flash image or zip?

ironia. said:
Flash image or zip?
Click to expand...
Click to collapse
OK, I'm confused now
As I understand, flashing the .img WILL wipe out the apps & data.
However, I have flashed the CM9 nightlies zip multiple times without loosing the data. Here we are dealing with a stock zip, so I am not sure. You can try the zip method after taking a nandroid backup.

Lost root after 4.1.2

I was running stock 4.1.1 rooted with NO cwm and I accepted the OTA undate two days ago. Now, I have SU still installed but nothing can obtain root permissions. I used Wugz toolkit to reflash su binaries through TWRP a few times and still no dice. Any thoughts?

Trickee360 said:
I was running stock 4.1.1 rooted with NO cwm and I accepted the OTA undate two days ago. Now, I have SU still installed but nothing can obtain root permissions. I used Wugz toolkit to reflash su binaries through TWRP a few times and still no dice. Any thoughts?
Click to expand...
Click to collapse
Here you go. Just follow the directions. It works fine for 4.1.2.
http://www.talkandroid.com/guides/misc/how-to-unlock-and-root-the-nexus-7/

veeman said:
Here you go. Just follow the directions. It works fine for 4.1.2.
http://www.talkandroid.com/guides/misc/how-to-unlock-and-root-the-nexus-7/
Click to expand...
Click to collapse
Welp, I've never actually used adb to push anything manually myself, but now is as good as time as any to try it. The link to CWM on that page is dead. Where else can I get it?

Trickee360 said:
Welp, I've never actually used adb to push anything manually myself, but now is as good as time as any to try it. The link to CWM on that page is dead. Where else can I get it?
Click to expand...
Click to collapse
http://www.clockworkmod.com/rommanager
You can download the Touch Recovery on the right side for Google Nexus 7 version. But make sure when you put in
Code:
fastboot flash recovery recovery-clockwork-touch-6.0.1.0-grouper.img
for step 5. instead of what they put.

veeman said:
http://www.clockworkmod.com/rommanager
You can download the Touch Recovery on the right side for Google Nexus 7 version. But make sure when you put in
Code:
fastboot flash recovery recovery-clockwork-touch-6.0.1.0-grouper.img
for step 5. instead of what they put.
Click to expand...
Click to collapse
got it. thanks much

Will only boot to stock recovery
veeman said:
You can download the Touch Recovery on the right side for Google Nexus 7 version. But make sure when you put in
Code:
fastboot flash recovery recovery-clockwork-touch-6.0.1.0-grouper.img
for step 5. instead of what they put.
Click to expand...
Click to collapse
Every time I reboot into recovery from the bootloader after flashing any recovery (except stock), it fails to boot into recovery. What happens is it shows the Google/Unlocked screen for a couple seconds, goes black (this is where it should enter recovery), but then shows the Google screen again and boots normally. I have tried this with two CWM recoveries and a TWRP recovery, both plugged into a computer and not. when flashing recovery it says OKAY. It seems as if something has gotten corrupted.
Before updating to 4.1.2 everything was working. To get the 4.1.2 update to install, I had to revert back to stock recovery and also revert back to the stock wallet app. Now 'su' is still a command, but it does not do what it is supposed to and no apps have root.
:'(

jphilli85 said:
Every time I reboot into recovery from the bootloader after flashing any recovery (except stock), it fails to boot into recovery. What happens is it shows the Google/Unlocked screen for a couple seconds, goes black (this is where it should enter recovery), but then shows the Google screen again and boots normally. I have tried this with two CWM recoveries and a TWRP recovery, both plugged into a computer and not. when flashing recovery it says OKAY. It seems as if something has gotten corrupted.
Before updating to 4.1.2 everything was working. To get the 4.1.2 update to install, I had to revert back to stock recovery and also revert back to the stock wallet app. Now 'su' is still a command, but it does not do what it is supposed to and no apps have root.
:'(
Click to expand...
Click to collapse
You can just root again and you will have root access.

I lost root too, so I just opened wugtoolkit and hit root. no unlock needed so no loss of programs either.

jphilli85 said:
Every time I reboot into recovery from the bootloader after flashing any recovery (except stock), it fails to boot into recovery. What happens is it shows the Google/Unlocked screen for a couple seconds, goes black (this is where it should enter recovery), but then shows the Google screen again and boots normally. I have tried this with two CWM recoveries and a TWRP recovery, both plugged into a computer and not. when flashing recovery it says OKAY. It seems as if something has gotten corrupted.
Before updating to 4.1.2 everything was working. To get the 4.1.2 update to install, I had to revert back to stock recovery and also revert back to the stock wallet app. Now 'su' is still a command, but it does not do what it is supposed to and no apps have root.
:'(
Click to expand...
Click to collapse
Any news about this. I stay in the same problem.

Here's my experience:
Stock ROM, rooted, custom kernel.
Got the notification for the 4.1.2 OTA update, so I did a nandroid backup in TWRP. Then I flashed back to the stock recovery and boot.img.
I was thinking that I might lose root, based on other's problems. Looked into installing Root Keeper by Voodoo. In the description it said the same feature is built into SuperSU. Problem was it's built into the paid version, which I didn't have (discovered this after it was too late). Installed 4.1.2 OTA. I lost root. My bootloader was updated to 3.41. I also was not able to flash a recovery. Fastboot flash would not work, Wugs toolkit didn't work. Tried several methods. After reading several threads that have been pretty active for the last few days, here's what finally worked for me. Found it in another thread, which I can't find at the moment.
adb reboot bootloader
fastboot flash bootloader bootloader-grouper-3.34.img from the JRO03D factory image
fastboot flash recovery TWRP img
fastboot reboot-bootloader
TWRP recovery started up :laugh:.
flashed SuperSU to re-root, it was sucessful.
updated busybox binaries.
installed OTA rootkeeper, so hopefully this won't happen again.
I'm not really sure I want to try flashing the 3.41 bootloader.
What a pain in the A.
Now it's time to flash faux kernel.

jayyo said:
Here's my experience:
Stock ROM, rooted, custom kernel.
Got the notification for the 4.1.2 OTA update, so I did a nandroid backup in TWRP. Then I flashed back to the stock recovery and boot.img.
I was thinking that I might lose root, based on other's problems. Looked into installing Root Keeper by Voodoo. In the description it said the same feature is built into SuperSU. Problem was it's built into the paid version, which I didn't have (discovered this after it was too late). Installed 4.1.2 OTA. I lost root. My bootloader was updated to 3.41. I also was not able to flash a recovery. Fastboot flash would not work, Wugs toolkit didn't work. Tried several methods. After reading several threads that have been pretty active for the last few days, here's what finally worked for me. Found it in another thread, which I can't find at the moment.
adb reboot bootloader
fastboot flash bootloader bootloader-grouper-3.34.img from the JRO03D factory image
fastboot flash recovery TWRP img
fastboot reboot-bootloader
TWRP recovery started up :laugh:.
flashed SuperSU to re-root, it was sucessful.
updated busybox binaries.
installed OTA rootkeeper, so hopefully this won't happen again.
I'm not really sure I want to try flashing the 3.41 bootloader.
What a pain in the A.
Now it's time to flash faux kernel.
Click to expand...
Click to collapse
So, the bootloader 3.41 is the problem?

Southmad said:
So, the bootloader 3.41 is the problem?
Click to expand...
Click to collapse
For some people, yes. No idea why.

veeman said:
http://www.clockworkmod.com/rommanager
You can download the Touch Recovery on the right side for Google Nexus 7 version. But make sure when you put in
Code:
fastboot flash recovery recovery-clockwork-touch-6.0.1.0-grouper.img
for step 5. instead of what they put.
Click to expand...
Click to collapse
Would that image work ok for Galaxy s3? Or there is no difference at all, just matter the 4.1.2 android version?
Cuz i updated my device throught Kies (cuzz from the device itself it didnt allow, stating that the image has been modifyied :angel: ) and after that even with the persistent mode on Super SU the root is gone

[Q] Kitkat 4.4 OTA Update failed to install

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.

[Q] stock rooted Lollipop OTA fails?

All,
Thanks in advance for any help you can provide. I have a Nexus 4 that I rooted and installed CWM recovery on, but I never installed any new kernels, ROMs, or radios. I'm currently on 4.4.4 and I want to upgrade to Lollipop. The OTA upgrade failed. So I tried returning to stock recovery and doing both the OTA and adb sideloading the OTA zip. Both fail.
The error message is "Package expects build fingerprint of google/occam/mako:4.4.4/KTU84P/1227136:user/release-keys or google/occam/mako:5.0/LRX21T/1576899:user/release-keys; this device has google/occam/mako:4.4/KRT160/907817:user/release-keys." (But I definitely have 4.4.4 on my phone, not 4.4.0.)
The extra difficulty is that I really, really do not want to wipe my phone. I have a lot of apps with a lot of configuration and other user data. So is there anything I can do? I guess I should try unrooting somehow? Or is there some other zip I can download that, through some type of recovery, will install the OTA without doing this check and also without wiping me?
Thanks again!

moriarty00 said:
All,
Thanks in advance for any help you can provide. I have a Nexus 4 that I rooted and installed CWM recovery on, but I never installed any new kernels, ROMs, or radios. I'm currently on 4.4.4 and I want to upgrade to Lollipop. The OTA upgrade failed. So I tried returning to stock recovery and doing both the OTA and adb sideloading the OTA zip. Both fail.
The error message is "Package expects build fingerprint of google/occam/mako:4.4.4/KTU84P/1227136:user/release-keys or google/occam/mako:5.0/LRX21T/1576899:user/release-keys; this device has google/occam/mako:4.4/KRT160/907817:user/release-keys." (But I definitely have 4.4.4 on my phone, not 4.4.0.)
The extra difficulty is that I really, really do not want to wipe my phone. I have a lot of apps with a lot of configuration and other user data. So is there anything I can do? I guess I should try unrooting somehow? Or is there some other zip I can download that, through some type of recovery, will install the OTA without doing this check and also without wiping me?
Thanks again!
Click to expand...
Click to collapse
OTA wants complete stock and obviously it doesn't think so about your phone. One option could be to back up to the cloud or some place outside the phone with TiBu (or whatever backup app you trust), then flash lollipop and try restore from TiBu. Another option would be to unroot (Supersu has an option to completely unroot), then retry.

Actually, I figured out what works! This was on a stock rooted device with stock recovery, but I bet it would work with custom recovery too. Instructions modified from https://pay.reddit.com/r/nexus4/comments/1qny3f/howto_update_your_stock_w_lte_nexus_4_without/ .
1. Download the image you want from https://developers.google.com/android/nexus/images . Extract it, extract the .zip file inside it too, and collect all of the .img files into one folder.
2. adb reboot bootloader (and wait until the bootloader comes up)
3. fastboot flash bootloader bootloader-mako-makoz30f.img (or whatever file has a similar name, if you got a different image than I did)
4. fastboot reboot-bootloader (and wait until the bootloader comes back up)
5. fastboot flash radio radio-mako-m9615a-cefwmazm-2.0.1701.04.img (or whatever file has a similar name, if you got a different image than I did)
6. fastboot reboot-bootloader (and wait until the bootloader comes back up)
7. fastboot flash boot boot.img
8. fastboot flash recovery recovery.img
9. fastboot flash system system.img
10. fastboot format cache
11. fastboot reboot
12. Don't panic unless you've seen the startup animation for at least 15 minutes without anything else happening.
I lost root, but I imagine re-custom-recoverying and re-rooting won't be any harder than the first time around.

Hi moriarty00,
I'm going to try the same procedure, thank you for posting this.
Can you confirm that your data and app are safe after the upgrade?

moriarty00 said:
Actually, I figured out what works! This was on a stock rooted device with stock recovery, but I bet it would work with custom recovery too. Instructions modified from https://pay.reddit.com/r/nexus4/comments/1qny3f/howto_update_your_stock_w_lte_nexus_4_without/ .
1. Download the image you want from https://developers.google.com/android/nexus/images . Extract it, extract the .zip file inside it too, and collect all of the .img files into one folder.
2. adb reboot bootloader (and wait until the bootloader comes up)
3. fastboot flash bootloader bootloader-mako-makoz30f.img (or whatever file has a similar name, if you got a different image than I did)
4. fastboot reboot-bootloader (and wait until the bootloader comes back up)
5. fastboot flash radio radio-mako-m9615a-cefwmazm-2.0.1701.04.img (or whatever file has a similar name, if you got a different image than I did)
6. fastboot reboot-bootloader (and wait until the bootloader comes back up)
7. fastboot flash boot boot.img
8. fastboot flash recovery recovery.img
9. fastboot flash system system.img
10. fastboot format cache
11. fastboot reboot
12. Don't panic unless you've seen the startup animation for at least 15 minutes without anything else happening.
I lost root, but I imagine re-custom-recoverying and re-rooting won't be any harder than the first time around.
Click to expand...
Click to collapse
Wow, a 12-step program
I simply rolled back my changes, and applying the OTA was as simple as pressing the "restart and install" button Here are some steps:
I used the app Flashify from Play Store to flash stock 4.4.4 recovery. I downloaded the stock factory image from google's own site (this one), used 7zip to extract the archives (tgz and tar), found "recovery.img" and transfered that to my phone. Then chose that file in Flashify.
Uninstalled all apps that made system changes, like Xposed framework and mods, BetterBatteryStats etc.
Removed Root with SuperSU cleanup function
Rebooted for good measure and apply OTA from notification - wait an hour or two for it to complete
Profit (do we still say that on the internet? Getting old here...)
I don't know if certain ways to get root will break the OTA. I used towel-root, and apparently SuperSU was able to undo that completely.

DrDruge said:
Hi moriarty00,
I'm going to try the same procedure, thank you for posting this.
Can you confirm that your data and app are safe after the upgrade?
Click to expand...
Click to collapse
Yup, perfectly safe! Just make sure not to flash other images, like userdata.img.

venu123 said:
OTA wants complete stock and obviously it doesn't think so about your phone. One option could be to back up to the cloud or some place outside the phone with TiBu (or whatever backup app you trust), then flash lollipop and try restore from TiBu. Another option would be to unroot (Supersu has an option to completely unroot), then retry.
Click to expand...
Click to collapse
If I unroot with Supersu how do I get root back?

moriarty00 said:
Yup, perfectly safe! Just make sure not to flash other images, like userdata.img.
Click to expand...
Click to collapse
Thank you!
Unfortunately the steps did not work for me, maybe I had some irreversible modifications or I had followed a different rooting procedure.
Or maybe I made a mistake in the upgrading steps.
Anyway, I had to flash the whole ROM and now everything is working fine.

Hey!
Basically I have similar problem with upgrading from 4.4.4 to 5.0 using OTA. Log from TWRP says:
Package expects build fingerprint of google/occam/mako:4.4.4/KTU84P/1227136:user/release-keys or google/occam/mako:5.0/LRX21T/1576899:user/release-keys; this device has google/occam/mako:4.3/JWR66V/737497:user/release-keys.
Click to expand...
Click to collapse
Phone has been rooted using Nexus Root Toolkit. And as long as there wouldn't be a problem with flashing using adb and wiping all data, there is one setback... My nexus is somehow broken. Communication via USB does not work, at all. Neither phone nor PC sees other device. Certified LG service centre nearby said that it is problem with main board, so generally repair is unprofitable.
So question is: How do I update to 5.0 and then root, without USB connection to my PC?

OTA path

Does anyone know where is located the downloaded OTA?

yes but you need root
its in \cache
i have the update also but cant flash as i loaded the twrp recovery image and only stock recovery can run the ota

MAX_G said:
yes but you need root
its in \cache
i have the update also but cant flash as i loaded the twrp recovery image and only stock recovery can run the ota
Click to expand...
Click to collapse
Thanks. I couldn't find it, so I updated and now I lost root...
Strange isse, before OTA update (I have stock recovery) I wanted to NAND backup through TWRP boot, but phone wasn't found by fastboot neither adb... So I updated without backupping. Now too phone isn't found by fastboot, so I cannot neither root!
USB debug is on like always, I already tried to disable and enable again, but no way