Database Users

[GUIDE] Root & recovery WITHOUT oem unlock & wipe (2.3.2 & older, plus now 2.3)

[GUIDE] Root & recovery WITHOUT oem unlock & wipe (2.3.2 & older, plus now 2.3)
UPDATE #2 - Fitchman has reported successful root and rom flash without unlocking the bootloader by using Ginger Break. Full details in this post: http://forum.xda-developers.com/showpost.php?p=13236136&postcount=135
UPDATE - IMPORTANT: This method does not work with Android 2.3.3. Search the forum or this post in this thread for a way to update to 2.3.3 and root without unlocking if you haven't updated yet.
Alternatively, use this method on 2.3.2 and lower, then use titanium to back up everything, store it on your laptop (along with all your sdcard's data), then do the oem unlock step first and then continue from there with the rest of the guide.
Not my original idea, but a consolidation of a discussion between inakipaz and shrivelfig and myself in another thread and being posted here for easier finding by future root-seekers.
Shrivelfig's tested the method to re-root a previously rooted pone with a re-locked bootloader, and inakipaz has done it on a phone that's never had the bootloader unlocked.
The advantage here is that those who chose not to root when they first got the phone won't lose any app data or sdcard data like the methods that have you unlock the bootloader do. The disadvantage is your bootloader remains locked, which may prevent you flashing certain things in the future.
edit: see ravidavi's posts below; he's shown you can even flash custom roms that are clockwork compatible while having a locked bootloader with this method.
Download these two files:
clockwork recovery v3.0.0.5 or clockwork recovery v3.0.0.5 mirror if above not working
su-2.3.6.1-ef-signed.zip
Koush's blog for the latest clockwork updates (find Nexus S in the list).
Also, if you don't already have the necessary android sdk and drivers on your computer, get them from here: http://developer.android.com/sdk/index.html and install them. Some Windows users report better luck just installing pdanet. There's a decent guide for Windows users on installing the sdk here.
Place the recovery file on your laptop where you can access it while using the sdk fastboot commands.
Place the su zip one in the top level folder of your sdcard.
Put your phone in fastboot mode (power off, then hold volume up and power key at the same time until the phone boots to a white screen).
Use fastboot to boot the phone into the clockwork recovery:
Code:
fastboot boot recovery-clockwork-3.0.0.5-crespo.img
If you're not sure how to get fastboot working on your computer, follow the excellent instructions that Allgamer gives in this GUIDE, but don't do the oem unlock command!
Once in clockwork, flash the su file to the phone by following these steps below.
To navigate in the clockwork recovery, you use the volume keys to scroll up/down through the menus, and the on/off button to select what's highlighted.
(note: some report success without these first 3 steps, others don't get a succesful root without, I recommend doing them)
select mounts and storage.
select mount /system
select go back
select install ZIP from sdcard
select choose zip from sdcard
select su-version#-signed.zip file you downloaded earlier
select yes - install su-version#-signed.zip
confirm it says "Install from sdcard complete"
select go back
select reboot
After the phone reboots, you should be rooted, with a locked bootloader, and none of your data erased.
That said, never hurts to have a backup of your precious data on the sdcard that you can copy over to the computer.
This method doesn't install busybox, so go to the Market and download/install busybox directly, or get Titanium Backup and check it's "problems?" button and let it install busybox for you. There's also an app called root checker that supposedly verifies you have a working root on your phone.
Once you have a successful root installed, I'd suggest getting back into clockwork recovery and running a nandroid back up from clockwork's backs and restore menu. Then copy that file from your sdcard (in the /clockwork/backups folder) to your laptop for safe-keeping and an easy full system restore to a known working config.
Usual disclaimers about I'm not responsible for damage to your phone or loss of data apply. Use any rooting method at your own risk.
Thanks and all the real credit go to inakipaz, shrivelfig and allgamer, and of course to koush, and ChainsDD for the superuser apk.

Worked perfectly. I used fastboot from my Mac (outlined in the stickied Mac Root thread). Root checker verifies that I have root.
And by the way, my phone and I are both root/ROM cherry. First android phone, first time rooter. Will work up the guts to flash a ROM soon, but of course there's no chance of doing THAT without unlocking the bootloader.
Thanks to all involved in this!

yeah! good work!

Srsly. Awsom.
Someone sticky this....

Question: When you do the fastboot boot command, does that overwrite the stock recovery with Clockwork? Or is it just booting into the recovery img without actually flashing it?
I would think this method also gives you a way to back up before unlocking the bootloader.
1) fastboot boot into Clockwork as described here
2) Full nandroid backup from Clockwork
3) Mount "SD" from Clockwork over USB, copy everything to computer (since it wipes everything)
4) Go back and unlock the bootloader as usual, resulting in a full wipe
5) Flash Clockwork Recovery again through whichever method
6) Mount "SD" from Clockwork over USB, copy the backup back to phone
7) Restore nandroid
And now you've unlocked the bootloader without amnesia =)
ravidavi said:
And by the way, my phone and I are both root/ROM cherry. First android phone, first time rooter. Will work up the guts to flash a ROM soon, but of course there's no chance of doing THAT without unlocking the bootloader.
Thanks to all involved in this!
Click to expand...
Click to collapse
Are you sure you need to unlock the bootloader to flash a ROM? Now that you have root, try installing ROM Manager from the Market, and see if it lets you flash custom recovery with bootloader still locked. If so, then yes you can install a ROM!
Also, the fact that you're able to boot into Clockwork using "fastboot boot" - that also means you can install a ROM .zip file right from there.

cmstlist said:
Question: When you do the fastboot boot command, does that overwrite the stock recovery with Clockwork? Or is it just booting into the recovery img without actually flashing it?
Click to expand...
Click to collapse
"fastboot boot" only launches the recovery no unlock needed. "fastboot flash" flash the recovery

cmstlist said:
Are you sure you need to unlock the bootloader to flash a ROM? Now that you have root, try installing ROM Manager from the Market, and see if it lets you flash custom recovery with bootloader still locked. If so, then yes you can install a ROM!.
Click to expand...
Click to collapse
It worked! Here's the process I used, starting from a completely unmodded Nexus S.
1: Use the method detailed here to gain root access without unlocking the bootloader.
2: Using a root-enabled file explorer (I used Super Manager), rename install-recovery.sh (in /etc) to install-recovery.sh.old . You'll need to remount as r/w to do this. NOTE: You don't *have* to do this step, but if you don't, then you can only use clockwork once after which it will be erased on reboot.
3: Using ROM Manager, install Clockwork Recovery.
4: Pleasure yourself, because your bootloader is still locked and nothing was erased.
I have yet to try actually flashing a custom ROM. Does this mean that it can also be done without unlocking bootloader?

Well damn, whaddaya know. I just flashed MoDaCo r10 without unlocking the bootloader, and without losing any personal data on /sdcard.
I figure someone at XDA should like this.
Pretty much followed distortedloop's advice. Starting from a fully stock Nexus S with Android 2.3.2 (GRH78C):
* Root using the method on this thread.
* Rename install-recovery.su to install-recovery-old.su. (in /bin)
* Install Clockwork Recovery from ROM Manager.
* Download whatever ROM you want (compatible with Clockwork), rename to update.zip, and copy to sdcard.
* Reboot into Clockwork.
* Wipe cache, reset to factory (IF REQUIRED BY NEW ROM). This was my first install of MoDaCo, and that requires it. This step does NOT erase your personal files on sdcard, just all android-related files.
* Install update.zip from Clockwork.
* Continue self-pleasuring ... you now have a custom rom without touching your bootloader or wiping your personal sdcard data.
Maybe it's just because I'm a noob here, but it seems to me that this is a BIG deal. All root/ROM installation methods that I've seen so far have required an unlocked bootloader. This seems to be the first time a Nexus S has been unlocked and custom-ROM'd without unlocking the bootloader and wiping the entire /sdcard.
Ravi

Yeah, it's pretty clear that the unlock the bootloader step isn't necessary for most of what we want to do. Just a habit from earlier devices, perhaps?
What's really odd is now we have to wonder what's the purpose of the oem unlock erasing your sdcard? Speculation was that it was a security feature to keep people from accessing your data if they stole your phone; they couldn't flash something on the phone to get access, but clearly they can. Fastboot into a custom recovery and you own the phone.
Perhaps this is a security hole Google will try to fix some day?
At any rate, I wish we'd discovered this sooner, it would have saved several people some grief in having to lose saved games (Angry Birds!) when they finally decided to root.

distortedloop said:
Yeah, it's pretty clear that the unlock the bootloader step isn't necessary for most of what we want to do. Just a habit from earlier devices, perhaps?
...
At any rate, I wish we'd discovered this sooner, it would have saved several people some grief in having to lose saved games (Angry Birds!) when they finally decided to root.
Click to expand...
Click to collapse
You say "for most of what we want to do." Could you think of a case where you would need to unlock it now? It's now shown to be unnecessary for rooting and installing custom recovery/ROM.
Is there any way to get the word out? This thread isn't stickied, and all the stickied threads on rooting & custom ROMs currently assert that you have to unlock the bootloader.
Ravi

ravidavi said:
You say "for most of what we want to do." Could you think of a case where you would need to unlock it now? It's now shown to be unnecessary for rooting and installing custom recovery/ROM.
Click to expand...
Click to collapse
I'm thinking that something like Superboot might need to have the bootloader unlocked, since it replaces the boot image, right? But I'm not sure.
ravidavi said:
Is there any way to get the word out? This thread isn't stickied, and all the stickied threads on rooting & custom ROMs currently assert that you have to unlock the bootloader.
Ravi
Click to expand...
Click to collapse
There's only a page and a half of posts in the development section right now, so it's not likely to disappear any time soon, but you could ask a mod (theimpaler747 is ours) via PM to sticky it. I thought about asking myself, but seemed a bit tacky to ask for my own thread.
Meanwhile, I'd been linking people to various posts I'd made in other threads suggesting this might work, but once inakipaz and shrivelfig confirmed it, I'm just now pointing people here. I just hope people see this before wiping their phones unnecessarily.
Really, the other guides should just be updated to skip the oem unlock step. That's really the only different thing we're doing here.

i'm just waiting for more people "newbies" to confirm this actually works for them, before making it a sticky

In theory if you really really screw up your phone, you might need fastboot flash in order to recover it. But if fastboot also lets you boot into an img recovery... then you still have a recovery route that doesn't require unlocking.
Sent from my Nexus One using XDA App

I know it's a noob question and all since all you're doing is flashing a custom recovery but will you still be able to get OTA updates after doing this as well?
Sent from my Nexus S using XDA App

qreffie said:
I know it's a noob question and all since all you're doing is flashing a custom recovery but will you still be able to get OTA updates after doing this as well?
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
yes because you still have the original recovery installed

distortedloop said:
Perhaps this is a security hole Google will try to fix some day?
Click to expand...
Click to collapse
This would be my guess.
But how? Is it possible to plug this with just a software update? Time will show, I guess.
This (security hole) should also make it possible to do perfect out-of-the-box OS backups. And restores. The problem is that nobody's going to do a backup without playing with their shiny new toy first.

shrivelfig said:
This would be my guess.
But how? Is it possible to plug this with just a software update? Time will show, I guess.
This (security hole) should also make it possible to do perfect out-of-the-box OS backups. And restores. The problem is that nobody's going to do a backup without playing with their shiny new toy first.
Click to expand...
Click to collapse
I can confirm that the Nexus One does not allow this "fastboot boot" on a locked bootloader. Maybe this was just an oversight?
It is entirely possible to plug this with a software update: Samsung/Google could issue a signed update that includes a bootloader upgrade. This has been done many times by HTC for example.

I can confirm that this method works, without unlocking the BL or erasing the SD part.

This is pretty cool. I wish I new about this before I unlocked the bootloader days after I received my phone. I too wonder if this was intentional or an oversite. Google did want this phone to be for developers, but like other's said, this is also a bit of a security hole. The wiping of the sd card on unlock would protect the person if the phone was stolen, like if there was confidential corporate stuff on there. Even if you password protect your phone, someone could fastboot clockwork, mount the sd card and retrieve all the information that was on there.

cmstlist said:
It is entirely possible to plug this with a software update: Samsung/Google could issue a signed update that includes a bootloader upgrade. This has been done many times by HTC for example.
Click to expand...
Click to collapse
It's also been done by Samsung with some versions of the Galaxy S line (some of the "leaked" roms, and even one official kies push (IIRC) changed the bootloader, causing people the ability to use 3 button mode for Odin access, and causing others to lose it.

[Q] New to modding, easiest way to install Kernel?

Hey guys, getting my Nexus 4 for Christmas and looking to install Franco Kernel.
I was wondering the best way to install it, I have searched for tuts but nothing is clear. I know he has an app for his kernel, does this require root to use? It doesn't mention it.
Any help would be greatly appreciated.

Go here and download the All In One script: http://forum.xda-developers.com/showthread.php?t=1995688
You're going to need to unlock the bootloader (will wipe your phone), so follow the steps in doing that.
Next, you'll need the latest CWM Recovery: http://forum.xda-developers.com/showthread.php?t=1995440
Follow those steps. Then download the Franco kernel .zip from its appropriate thread and flash it in CWM.

Shnew said:
I was wondering the best way to install it, I have searched for tuts but nothing is clear. I know he has an app for his kernel, does this require root to use? It doesn't mention it.
Click to expand...
Click to collapse
First thing I'm going to tell you - Go back and read the OP. Because he actually does have instructions in it (Although very minimal).
http://forum.xda-developers.com/showpost.php?p=34375927&postcount=1
Here's the quick and simple of how to do it.
1. Download the Nexus 4 Toolkit -- http://forum.xda-developers.com/showthread.php?t=1995688 (READ THE OP COMPLETELY)
2. Unlock the bootloader.
3. Install custom recovery.
4. TAKE A BACKUP!
5. Transfer kernel files to device.
6. Use recovery to flash files.
7. Hold breath while booting.

DO NOT USE TOOLKITS. Especially if you're new to modding.
That's like saying, I want to overclockmy computer. Just give me a toolkit where I can one click and overclock my computer.
Read more here http://forum.xda-developers.com/showthread.php?t=1469909
Do it the proper way and download ADB drivers
http://forum.xda-developers.com/showthread.php?t=1514942 (enable USB debugging)
set up ADB environment
adb reboot bootloader
fastboot oem unlock
unlock bootloader on phone
download clockwork recovery or TWRP (i suggest TWRP)
put the .img file of recovery into your /platform-tools/
fastboot flash recovery <name-of-file>.img
then boot into recovery and there you can flash your ROM, gapps, kernel.
In the long run, IT WILL PAY OFF because eventually YOU will be faced with a problem with your phone and you won't be able to recover your phone because you dont know basic fastboot or adb commands all simply because you wanted to use a toolkit. People are already asking on how to use adb / fastboot in Q&A, we can reduce the clutter by not having people use toolkits and actually learning how adb / fastboot works when it isn't a very complicated thing to do at all

netsyd said:
4. TAKE A BACKUP!
Click to expand...
Click to collapse
Make sure the boot partition is checked when you are backing up. To return to the stock kernel, (if you ever need to) you will need to restore this backed up boot image.
Sent from my Nexus 4

Can I just root and use the stock recovery to flash franco kernel? I want to be able to download ota from google in the future...

hophamson said:
Can I just root and use the stock recovery to flash franco kernel? I want to be able to download ota from google in the future...
Click to expand...
Click to collapse
no you need custom recovery

Unlock the bootloader, install a custom recovery and flash the zip.
Sent from my Nexus 4, powered by CyanogenMod via XDA Developers app.

[Q] I was just wondering if

I am on stock nexus 7 2012 and just thinking that if I root my n7 unlock its boot loader and try to update nexus with adb side load command, would it work or end up in bricking my tablet?

First - unlock, then root. I don't think it's possible to brick the device unless u screw up a bootloader. Semibricks could be easily undone.

Well thanks
holynoob said:
First - unlock, then root. I don't think it's possible to brick the device unless u screw up a bootloader. Semibricks could be easily undone.
Click to expand...
Click to collapse
Well thanks, I'm kinda new, I am learning but I am just scared of one thing, it is I guess if I flash a zip file I won't obviously receive a update, or even update it with adb sideload?
Anyways I am too lazy to unroot, root, unroot for a ota oh and I also messed up my device. Flashing a factory image with wug's toolkit, got stuck on sending system and sat there for like 3 hours! Gave it to get repaired and they flashed it. Soft bricked it was . So one last question if I flash a zip and use adb sideload will it work or not. Thanks:laugh:

If you want to update using zip of this kind: 094f6629314a.signed-nakasi-JOP40C-from-JZO54K.094f6629.zip, then adb sideload is good to go. And here is a guide www.androidpolice.com/2012/11/13/an...he-nexus-7-now-manual-download-link-available.
If you want to install from factory image (smth like this: nakasi-krt16s-factory-da7dee49.tgz) then use flash-all.bat in the archive, BUT ALL YOUR DATA WILL BE WIPED.
And finally if you want to install custom ROM then use custom recovery.

Thanks!
Oh, so flash zip with twrp or cwm and boot up and it will be updated. Thanks.

Sarmad Ishtiaq said:
I am on stock nexus 7 2012 and just thinking that if I root my n7 unlock its boot loader and try to update nexus with adb side load command, would it work or end up in bricking my tablet?
Click to expand...
Click to collapse
Always ask question in Q&A section and yes if u unlock and root it wont brick it u just have to extra careful about what ur doing.
Read my friend read every thing.

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

[INFO] [GUIDE] [HOW TO] Nexus 6 OTA help desk

Here is a dedicated thread for Q&A and general info on OTA's for the Motorola Nexus 6. Please feel free to discuss all things OTA related and ask any questions you may have.
*Bootloader lock status has no effect on OTA pass or fail.*
To summarize, an OTA (Over The Air) is a software update pushed to nexus devices directly from Google. You will receive a notification when one is available for your device. The files are generally large in size and downloading via WiFi is recommended.
With Android 5.0 and up, OTA updating has changed significantly from previous versions. In the past, you could be stock, rooted, with stock recovery and OTA's would flash successfully. This is no longer possible in lollipop. Absolutely no system or kernel modifications can be present in order for the OTA to flash. This means that if you have unencrypted the stock kernel, the OTA will fail. The phone must be in a "out of box" state.
As always, you are not required to take the OTA as there are other options available. If you are already rooted, unlocked and using a custom recovery, you can use an updated custom ROM provided by the amazing development community here at XDA. Factory images are released by Google prior to OTA's being pushed out so most, if not all, of the custom ROMs are updated before you'll even see an OTA notification. Also, there are stock, rooted ROMs available as well.
*Factory images*
You can always update or return to stock via factory images direct from Google. Link to this guide provided in post #2
*Sideloading*
Another feature available to use is the sideload option. With the use of a few simple ADB commands, you can apply the OTA via sideload. Sideloading will require connecting to your PC and a working ADB/fastboot connection. Directions for sideloading are in post #3.
*Updating while rooted, unlocked, and having a custom recovery via fastboot*
This is quite simple with basic knowledge of fastboot/ADB. Download the factory image, extract the system image and flash with fastboot. Then flash TWRP and SuperSU again. You can also flash the boot image if desired. However if you are unencrypted, this will encrypt the device.
Many, MANY thanks to the development community, themers, modders and other talented people here at XDA.
Thanks @El Daddy for guidance and advice.​

Helpful links:
*Please hit the thanks button for the OP's of the XDA threads below if the threads were helpful in any way.*
Beginners guide:
Thanks @xBeerdroiDx
http://forum.xda-developers.com/showthread.php?t=2948481
Setting up and using ADB and fastboot:
Thanks @rootSU
http://forum.xda-developers.com/showthread.php?t=3006500
Factory images installation instructions:
(Including the fastboot flash method for flashing individual images):
Thanks @Mr hOaX
http://forum.xda-developers.com/showthread.php?t=2954008
OTA files:
Thanks @oldblue910
http://forum.xda-developers.com/showthread.php?t=2906493
*For rooted/unlocked users only*
OTA zip files and radio files (TWRP flashable):
Thanks @Q9Nap
http://forum.xda-developers.com/showthread.php?t=3066052
Radio thread (fastboot flashable):
Thanks @zephiK
http://forum.xda-developers.com/showthread.php?t=2969380​

Directions for sideloading
*These directions are based on Android SDK, Windows OS and a 100% stock Nexus 6*
This is just a simple, well known, user guide to using sideload.
Make sure your SDK is updated!​
Download the OTA file to your PC, rename it to update.zip and transfer into the platform-tools folder of your SDK.
Connect your Nexus to your PC with your OEM USB cable.
Hold shift and right click on platform-tools folder and select open command prompt here.
Type: adb devices
If your serial number comes up, you are good to go. If not, check out your drivers in device manager. You may need to manually point your PC to their location. Also, you may need to uninstall any other Android drivers that are not associated with your Nexus.
Type: adb reboot bootloader
Select recovery mode from your phone using the volume down key. Once you've highlighted recovery mode, press power to select it.
It looks like a restart but the the dead android appears with red exclamation point. When that happens, hold power button and press volume up once.
Once in recovery, use the volume down key to select apply update from adb and push power to select it.
When your phone says now send file,
type: adb sideload update.zip
If all goes well, you'll see things progress and your Nexus will restart when complete. If you encounter the device not found error after beginning, unplug your USB and reconnect. I had to do it twice, but it works.

How do we install ota zip

if you are running stock you should be able to use wug toolkit and have it flash this zip file

What about stock-ish? I'm assuming since I'm rooted with my device unencrypted, that I can't flash this, right?

Flashing now. Will post back when done.
EDIT: Flash went perfect ^.^ 5.1 is all set.

knitler said:
Flashing now. Will post back when done.
EDIT: Flash went perfect ^.^ 5.1 is all set.
Click to expand...
Click to collapse
Were you completely stock?
Sent from my Nexus 6 using XDA Premium 4 mobile app

instructions for mac
http://www.androidcentral.com/how-manually-upgrade-your-nexus#slide5

I have a modded boot image and it failed to install. Guess ill have to nuke and start over to get this OTA in place.

http://www.androidpolice.com/2015/0...gs-android-5-1-ota-roundup-for-nexus-devices/ I just want to flash the radio but it looks line it's 20 MB bigger than the last

Is anyone creating a flashable zip that works with TWRP?

@oldblue910,
Thank you very much. ADB sideload went flawlessly (completely stock 5.0.1 of course).

I probably already know the answer but here is my situation... I am on the stock image but unlocked boot loader, rooted, and twrp recovery. The only way I can remain stock and not lose my current state other than root and a few apps that rely on root is to... Unroot, relock boot loader and put back stock recovery... Then OTA or side load? Theres no other option right?

I think I'm on the same situation as edif30
Stock image
rooted
unlocked bootloader
TWRP recovery
How can i sideload w/o losing root?

edif30 said:
I probably already know the answer but here is my situation... I am on the stock image but unlocked boot loader, rooted, and twrp recovery. The only way I can remain stock and not lose my current state other than root and a few apps that rely on root is to... Unroot, relock boot loader and put back stock recovery... Then OTA or side load? Theres no other option right?
Click to expand...
Click to collapse
You could flash the 5.0.1 factory image except for the userdata.img and radio.img and side load the OTA. Or you can wait for the 5.1 factory image and remove the "-w" from the flash-all script.
You will lose root and TWRP. but your data will remain intact.

So I'm all stock, unrooted, with a still-locked bootloader. I can flash the OTA without unlocking and without losing my data, right?

stevexyz0 said:
So I'm all stock, unrooted, with a still-locked bootloader. I can flash the OTA without unlocking and without losing my data, right?
Click to expand...
Click to collapse
Yep, just use ADB sideload.

So I had stock 5.0.1 with a custom kernel. I flashed the stock boot.img from the factory image using TWRP and I unrooted from in the SuperSU app, so I should be stock all around except for recovery. When I try to flash the OTA in TWRP it gives the following error message:
Package expects build fingerprint of google/shamu/shamu:5.0.1/LRX22C/1602158:user/release-keys or google/shamu/shamu:5.1/LMY47D/1743759:user/release-keys; this device has google/omni_shamu/shamu:5.0.2/LRX22G/dees_troy01130854:eng/test-keys.
Any idea why TWRP would think I was running 5.0.2?

cam30era said:
@oldblue910,
Thank you very much. ADB sideload went flawlessly (completely stock 5.0.1 of course).
Click to expand...
Click to collapse
Mine too but how long did it stay on the GOOGLE screen before booting?