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.

Manual unlock & root - without toolkit

Hi all,
Finally received my nexus 4 after suuuch a long wait.
I went the nexus root as I'd really like to learn all the ins and outs of android. I'm working as a web dev now (nothing with java).
This is my first android device and I will soon want to unlock, root and try manually amend system files.
I have some questions though:
1. Can I unlock the phone through the terminal manually and without toolkit? I want to do everything myself.
2. Are there any tutorials on manually rooting a nexus 4 (I saw a gnex). I don't want to use a tool kit for now.
3. I'd like to try start amending (very basic) some System files. Will it be easy to transfer over the code when updates come?
Thanks!

Check the sticky in the general forum. Great stuff by efrant. http://forum.xda-developers.com/showthread.php?t=2010312

nm3th said:
Check the sticky in the general forum. Great stuff by efrant. http://forum.xda-developers.com/showthread.php?t=2010312
Click to expand...
Click to collapse
Thanks for the link but I have already read that. What I want to do is manually perform the tasks he mentions. When he says to download a toolkit , I want to skip that and manually do what the toolkit does to have a better understanding of the OS.

Did you actually read it? He gives a step by step from unlocking the bootloader, to installing the drivers needed to run adb/fastboot, root, etc. No toolkit; exactly what you're asking for.

nm3th said:
Did you actually read it?
Click to expand...
Click to collapse
Yes I have. I guess I must of misunderstood what platform tools are.
Why do I need those? The android development bridge cannot work without that?

Platform-tools-v16 contains the files needed to run adb and fastboot. Adb (android debug bridge) allows you to communicate with your device from your pc. Fastboot allows you to update the flash file system. You will need this if you don't already have the sdk installed. Just follow the instructions and it'll be a good learning experience. Good luck.
**edit** I'm not on my system with the sdk, so I can't check, but I don't think fastboot is included with the sdk anymore, only adb is.

monkeying. around said:
Hi all,
Finally received my nexus 4 after suuuch a long wait.
I went the nexus root as I'd really like to learn all the ins and outs of android. I'm working as a web dev now (nothing with java).
This is my first android device and I will soon want to unlock, root and try manually amend system files.
I have some questions though:
1. Can I unlock the phone through the terminal manually and without toolkit? I want to do everything myself.
2. Are there any tutorials on manually rooting a nexus 4 (I saw a gnex). I don't want to use a tool kit for now.
3. I'd like to try start amending (very basic) some System files. Will it be easy to transfer over the code when updates come?
Thanks!
Click to expand...
Click to collapse
its the same as on the gnex, exactly. its the same on all nexus devices. fastboot oem unlock, fastboot a custom recovery, flash either a custom rom or the su binaries in that new recovery, then reboot and profit

nm3th said:
You will need this if you don't already have the sdk installed. Just follow the instructions and it'll be a good learning experience. Good luck.
Click to expand...
Click to collapse
OK thanks that clears another point up. I'm not really after learning how to flash etc but more about the OS as a whole. Would also like to slowly attempt to amend some changes in the system files but I'll go ahead and do that guide.
simms22 said:
its the same as on the gnex, exactly. its the same on all nexus devices. fastboot oem unlock, fastboot a custom recovery, flash either a custom rom or the su binaries in that new recovery, then reboot and profit
Click to expand...
Click to collapse
OK thanks will try tackle it this weekend.
Can you guys answe my other question? What about people who amend the files how so they go about updating the system where. Updates are released?

monkeying. around said:
Can you guys answe my other question? What about people who amend the files how so they go about updating the system where. Updates are released?
Click to expand...
Click to collapse
Make a backup of whatever file you are modifying and when there is an update, revert back to the old file and you should be able to flash the OTA. Or just flash the stock image using the instructions from my first reply, then flash the OTA.

Androidrootz.com has tutorials for manual or tool kits rooting via windows or Mac. I did the Mac version and it was a piece of cake and I am no pc expert. They have info for unrooting and flashing clockwork mod recovery.
Good luck,
Ian B

nm3th said:
Make a backup of whatever file you are modifying and when there is an update, revert back to the old file and you should be able to flash the OTA. Or just flash the stock image using the instructions from my first reply, then flash the OTA.
Click to expand...
Click to collapse
Ok that should sort out the updating but after updated what do I do with the backup/modified file. I will have to remodify everything again correct?
Mr Ian B said:
Androidrootz.com has tutorials for manual or tool kits rooting via windows or Mac. I did the Mac version and it was a piece of cake and I am no pc expert. They have info for unrooting and flashing clockwork mod recovery.
Good luck,
Ian B
Click to expand...
Click to collapse
Thanks I saw this tutorial and video although I found a better one. Like I said before I thought this was the plug n
Play version. Any will root the traditional way I guess.

there's another guide in this forum, maybe you like that one
http://forum.xda-developers.com/showthread.php?t=2018179

OK guys just backed up all my data to my computer. I've downloaded the platform tools but there seems to be a contradiction here.
Do I have to download the .IMG file that is 300+ mb?
cause some tutorials say I don't.

The IMG file is for just in case you goof up and need to get your phone back up and running.

nm3th said:
The IMG file is for just in case you goof up and need to get your phone back up and running.
Click to expand...
Click to collapse
OK thanks. Now I get it.
Regarding the updates, if I am unlocked and have root access with no other changes, I can successfully install the update correct?
Only thing I will lose is root access?

What will happen if I do a factory data reset on a unlocked + rooted device?

monkeying. around said:
What will happen if I do a factory data reset on a unlocked + rooted device?
Click to expand...
Click to collapse
You lose installed apps and data but maintain root
Sent from my Nexus 4 using Tapatalk 2

What about if I've flashed cwm recovery? To the boot loader. Would that get overwritten
Or is that not affected since its in the bootloader...before you get to the os.

monkeying. around said:
What about if I've flashed cwm recovery? To the boot loader. Would that get overwritten
Or is that not affected since its in the bootloader...before you get to the os.
Click to expand...
Click to collapse
It will not erase that as you said unless you flash back to the stock recovery image as the boot and recovery is separate. You can wipe data and reflash all day long if you want.

[Q] Software update using sideload and fastboot

Hi this is my first post and i hope its in the correct place and all
My nexus 7 (2013) is stuck in an android update circle where it constantly fails.
I tried to so the update to jss15q 4.3 using sideload where got so close but it said "signature verification failed" why could that be and can i stop it needing a verification?
I then tried to do it using fastboot and got so close again but got
:checking version-bootloader failed"
:device version-bootloader is "flo-03.05"
:Update requires "flo-03.14"
is there a way to correct either of them?
I am not rooted and i have downloaded the jss15q from developers google themselves (and i have debugging enabled)
Thanks for any help
Joe

Do you have the LTE version of the nexus or the WiFi version?

Guhrasoh said:
Do you have the LTE version of the nexus or the WiFi version?
Click to expand...
Click to collapse
I have the wifi only version.

joeyt90 said:
I have the wifi only version.
Click to expand...
Click to collapse
Follow this thread: http://forum.xda-developers.com/showthread.php?t=2382051 to unlock the bootloader (your data on the device will be lost). Make sure you reboot the device at least once after unlocking and before you do anything else with it!
After that you can flash or boot TWRP and try to install the update with TWRP, if that fails you can flash a full factory image (the above thread contains all the information needed).

Guhrasoh said:
Follow this thread: http://forum.xda-developers.com/showthread.php?t=2382051 to unlock the bootloader (your data on the device will be lost). Make sure you reboot the device at least once after unlocking and before you do anything else with it!
After that you can flash or boot TWRP and try to install the update with TWRP, if that fails you can flash a full factory image (the above thread contains all the information needed).
Click to expand...
Click to collapse
What exactaly do i have to do on that page to be able to continue the methods i am trying to use? If i just unlock the bootloader willi be able to update the boot loader from version-bootloader "flo-03.05" to "flo-03.14" then download jss14q using fast boot or is it not that easy?
Thanks again
P.S I dont want to root yet and Is it possible to just update the bootloader without unlock bootloader or do you have to unlock before you can update?
Thanks

If you want to use fastboot and the factory images you need to be unlocked.
Which file did you feed it when you "sideloaded" it? It needs to be the OTA file.

sfhub said:
If you want to use fastboot and the factory images you need to be unlocked.
Which file did you feed it when you "sideloaded" it? It needs to be the OTA file.
Click to expand...
Click to collapse
Hi I used the image from Google developers for nexus which was a zip file. Where could get the ota file from.
By unlocking do you mean just unlocking boot loader?
Thanks Joe

joeyt90 said:
Hi I used the image from Google developers for nexus which was a zip file. Where could get the ota file from.
By unlocking do you mean just unlocking boot loader?
Click to expand...
Click to collapse
Yes, bootloader must be unlocked to use the factory image restore.
As to the zip file, the zip file from the google developer site is a factory image. It is not meant to be sideloaded, only used in fastboot-style restores.
If you want to go the sideload route, what you want is the appropriate OTA zip (JWR66N->JSS15Q, JSS15J->JSS15Q), which you can get in the download section of this thread:
http://forum.xda-developers.com/showthread.php?t=2415497
If you'd rather do the factory image to JSS15Q, then I suggest you unlock the bootloader and use this post:
http://forum.xda-developers.com/showthread.php?p=44888268#post44888268
Personally, I'd go the factory image restore route, it is less hassle.

sfhub said:
Yes, bootloader must be unlocked to use the factory image restore.
As to the zip file, the zip file from the google developer site is a factory image. It is not meant to be sideloaded, only used in fastboot-style restores.
If you want to go the sideload route, what you want is the appropriate OTA zip (JWR66N->JSS15Q, JSS15J->JSS15Q), which you can get in the download section of this thread:
http://forum.xda-developers.com/showthread.php?t=2415497
If you'd rather do the factory image to JSS15Q, then I suggest you unlock the bootloader and use this post:
http://forum.xda-developers.com/showthread.php?p=44888268#post44888268
Personally, I'd go the factory image restore route, it is less hassle.
Click to expand...
Click to collapse
PERFECT!!!
Thank you so much to everyone who helped me on here my device is now running 4.3 version jss15q and what a difference from jwr66n.
I used the Unlock bootloader and then use factory images and it worked a treat!!
Again i cannot thank you enough i called google and the people who suplied my nexus and they both said they didnt know!!
WAHOO!!!:good::good::good::laugh::laugh:

[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?

[GUIDE] Sideload NOF27B/C on Stock, TWRP, Custom Kernel, Mods, Root - Updated 3/6/17

Follow at your own risk, I take no responsibility. This guide is for any stock(seems to work with mods) rom. I used TWRP RC1, but could possibly work with alpha 2(for adb sideload only). Not sure if this method is "better" than using flash-all.bat without -w, but the file download was smaller.
Required Files and Locations they should be placed:
TWRP RC1 Image placed in the same folder as your FASTBOOT executable
TWRP RC1 zip installer placed on phones internal storage
SuperSU 2.79 SR3 zip installer placed on phones internal storage
NOF27B or NOF27C - Rogers OTA placed in the same folder as your ADB executable
Ensure the TWRP and SuperSU zip installers are loaded onto the phones internal storage and the OTA zip and TWRP image are in the ADB/FASTBOOT executables folder.
Boot into current TWRP recovery
Make a full backup in TWRP
Connect the phone to the computer
In TWRP select the Advanced menu, click ADB sideload option
On the computer open a command window and navigate to the location of your ADB executable/OTA zip
Only execute one adb sideload command for your specific device
Execute the following command(Non-Rogers): adb sideload sailfish-ota-nof27b-8130b5a8.zip
Execute the following command(Rogers): adb sideload sailfish-ota-nof27c-fb487658.zip
Only execute one adb sideload command for your specific device
The command window should be displaying a percentage and the TWRP should be displaying the standard OTA step 1 and 2 - Let this complete
Click Reboot System and let the OTA finish installing
At this point TWRP and Root are gone, but can be restored
With the device powered off, hold volume down and turn on the device. Your device should now be in the bootloader.
With the device connected to the computer run the following command from the previous step's command window: fastboot boot twrp-3.0.2-0-RC1-fastboot-sailfish.img
Install twrp-pixel-installer-sailfish-3.0.2-0-RC1.zip in TWRP
Install SR3-SuperSU-v2.79-SR3-20170114223742.zip in TWRP
Click Reboot System
Install Kernel/Mods
Remember to restore any /system specific edits such as the tether build.prop edit, host file edits, or custom boot animations.

This is amazing!. I have downloaded the full factory image already. followed by your guide, Can I just use an OTA package to upgrade NMF26O to latest build? I have rooted and twrp installed

bush911 said:
This is amazing!. I have downloaded the full factory image already. followed by your guide, Can I just use an OTA package to upgrade NMF26O to latest build? I have rooted and twrp installed
Click to expand...
Click to collapse
Just remove the -w argument from the flash-all.bat and flash the factory image...

Thank you dude, so what's the difference between full factory image and full ota zip, and ota automatically downloaded to phone.
the factory image is around 1.8 G and full ota zip is around 800 M, but the ota automatically downloaded to phone is only 47 M
Juli112 said:
Just remove the -w argument from the flash-all.bat and flash the factory image...
Click to expand...
Click to collapse

I had good luck with this method getting to NMF26O. Just a couple of things to note. Make sure you have the latest ADB files, and while it probably is assumed that you are using TWRP RC1 I'm pretty sure this did not work in Alpha2. Also, when the OP mentions losing TWRP it actually completely removes recovery so don't freak out if you try to boot into it expecting stock recovery and get a no data (or something like that if I remember correctly) error. There is no reason to check, but last time I was curious to see if it would leave TWRP in place. All is fine as long as you can get to bootloader. One other thing is the fact that this is an OTA. I would not do this unless coming from NMF26O but that is just me.
I am in no hurry to do this update since by all accounts it adds no functionality, but I was going to try it this way again. I wonder if anyone has any reason other than habit to continue to use the flash all method.

Juli112 said:
Just remove the -w argument from the flash-all.bat and flash the factory image...
Click to expand...
Click to collapse
so should we sideload the OTA over Q or download the factory image and remove the -w flag and run flash all.bat?

can this process be done if we are running stock rooted but with weta 2.2.1 installed? or does it need to be totallly stock? thanks

quinejh said:
can this process be done if we are running stock rooted but with weta 2.2.1 installed? or does it need to be totallly stock? thanks
Click to expand...
Click to collapse
This is only for updating stock. If you want of weta then use the full image and remove the -w from the flashall bat file.

thank you! worked great!

quinejh said:
can this process be done if we are running stock rooted but with weta 2.2.1 installed? or does it need to be totallly stock? thanks
Click to expand...
Click to collapse
Because I'm groovy like that... (And had a nandroid backup) I went ahead and took the jump of sideloading the OTA update over weta 2.2.1. Personally, I wasn't too concerned about botching up the system, as the weta ROM is going away. Instead the author is now compiling his mod(s) to layer over this stock build. I'm assuming that the OTA sideload went without a hitch because weta is designed around the stock image. Of course, I had to install some of my mod's again that were lost in the "update"
**DISCLAIMER**
I'm not claiming or declaring the OTA update is safe to install over weta 2.2.1. I'm only giving my experience so others can weigh out the risks for themselves, if they decide to roll the dice. :silly:

I followed this method and everything went smoothly. I have the new update, supersu and elemental kernel but now I can not use android pay

rohitece06 said:
I followed this method and everything went smoothly. I have the new update, supersu and elemental kernel but now I can not use android pay
Click to expand...
Click to collapse
I don't use Pay, but did you update to the latest Elemental kernel 1.03?

spiller37 said:
I don't use Pay, but did you update to the latest Elemental kernel 1.03?
Click to expand...
Click to collapse
Yes I did.

rohitece06 said:
Yes I did.
Click to expand...
Click to collapse
Try Franco's, his is patched for pay. Just to try and narrow it down here.

rohitece06 said:
Yes I did.
Click to expand...
Click to collapse
You might also try the patched stock kernel that was just updated.

spiller37 said:
You might also try the patched stock kernel that was just updated.
Click to expand...
Click to collapse
Thanks it worked with patched stock kernel although I lost root and when I installed SuperSu 2.79 SR2 android pay stopped working.

Is something up with the OP or is it just my XDA app causing it to show like this..

aholeinthewor1d said:
Is something up with the OP or is it just my XDA app causing it to show like this..
Click to expand...
Click to collapse
Not sure why it displays this way in the two XDA apps. If anyone knows how to fix the formatting I would be grateful for the solution.

rohitece06 said:
Thanks it worked with patched stock kernel although I lost root and when I installed SuperSu 2.79 SR2 android pay stopped working.
Click to expand...
Click to collapse
Oh I didn't realize root and pay could work simultaneously on the pixel yet. Not sure which thread, but there was discussion on using the dual slots to run one slot stock with pay and one slot stock with root. Then dual booting between them.

spiller37 said:
Oh I didn't realize root and pay could work simultaneously on the pixel yet. Not sure which thread, but there was discussion on using the dual slots to run one slot stock with pay and one slot stock with root. Then dual booting between them.
Click to expand...
Click to collapse
it was working before this January pixel update