Database Develop

[Q] unlocking

Ok, hope I don't get too much heat over this, my old device was a Samsung with unlocked bootloader, so everything was easily flashed.
Anyway, as to the best order of things, I'm still on AT&T 4.2.2 pre camera update, so I easily rooted with with pwnmymoto. I have Xposed installed with a few modules.
For the unlock steps -looks like this is the best guide: http://forum.xda-developers.com/showpost.php?p=51363645&postcount=394 and using: https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-c
Q: Is my recovery from pwnmymoto "stock" as it needs to be for unlocking process?
Can I just uncheck/disable the modules I have with xposed, or do I need to delete the framework? (which sounds like the only way is to use RSD to install the original ROM?)
Should I also unfreeze any files? (I think I only froze the one's related to motorola OTA)
My intent is to get to 4.4.2, and I know it's optimal to remove things from pwnmymoto (I know unlocking will wipe everything but my ROM), so probably after I've installed TWRP and rooted, to flash the file for AT&T 4.4.2 http://forum.xda-developers.com/moto-x/general/-t2688009 or does it need to be incremental, as I'm on 4.2 (i.e flash 4.2 camera update, then 4.4, etc.) -sorry if I seem a bit confused
Thanks in advance! any and all help is very much appreciated!

Hopefully not too many questions -if any has the best suggestion for any, would be great

M973 said:
Hopefully not too many questions -if any has the best suggestion for any, would be great
Click to expand...
Click to collapse
Just to be clear if you eant 4.4.2 stock use the xposed framework disabler, it said leaving the modules was ok according to the link you posted. I don't know personally.
But honestly if your unlocking the bootloader then just go to 4.4.2 first then unlock since you'll lose everything. I believe bootloader unlock wipes the system parition too. I don't know for sure.

drago10029 said:
Just to be clear if you eant 4.4.2 stock use the xposed framework disabler, it said leaving the modules was ok according to the link you posted. I don't know personally.
But honestly if your unlocking the bootloader then just go to 4.4.2 first then unlock since you'll lose everything. I believe bootloader unlock wipes the system parition too. I don't know for sure.
Click to expand...
Click to collapse
I think 4.4.2 isn't fully released yet OTA for AT&T, so it would be flashing to stock and taking each OTA in sequence to 4.4 I think? I believe the framework disabler is a zip that needs to be flashed, so that would only be after I have a custom recovery.
I just don't want to mess up anything, want to make sure I have the right recovery for unlocking, and that I've disabled anything that could cause an issue.
Edit: from the pwnmymoto thread, Jcase writes: "In the process we remove stock recovery, so OTAs will not be a worry."
I guess that means i don't have stock recovery?
Edit: I was thinking I needed stock recovery, I guess I just need fastboot which is what I have?
I just want to make sure, if anyone has unlocked from pwnmymoto
Thanks

M973 said:
I think 4.4.2 isn't fully released yet OTA for AT&T, so it would be flashing to stock and taking each OTA in sequence to 4.4 I think? I believe the framework disabler is a zip that needs to be flashed, so that would only be after I have a custom recovery.
I just don't want to mess up anything, want to make sure I have the right recovery for unlocking, and that I've disabled anything that could cause an issue.
Edit: from the pwnmymoto thread, Jcase writes: "In the process we remove stock recovery, so OTAs will not be a worry."
I guess that means i don't have stock recovery?
Edit: I was thinking I needed stock recovery, I guess I just need fastboot which is what I have?
I just want to make sure, if anyone has unlocked from pwnmymoto
Thanks
Click to expand...
Click to collapse
np problem bro, happy rooting! may the flash be ever in your favor

[Q] XT1053 4.4.4 Root?

Hey guys does anyone have step-by-step guide on how i can root this phone? I am not able to find a guide for XT1053 (T-Mobile) on 4.4.4. Specifically I want to install a 5.0 rom because I'm tired of waiting for the update. Any help will be appreciated;

stuntman2128 said:
Hey guys does anyone have step-by-step guide on how i can root this phone? I am not able to find a guide for XT1053 (T-Mobile) on 4.4.4. Specifically I want to install a 5.0 rom because I'm tired of waiting for the update. Any help will be appreciated;
Click to expand...
Click to collapse
http://forum.xda-developers.com/moto-x/general/ref-complete-moto-x-guides-information-t2603358

You'll have to unlock the bootloader. No way around it.

Should I be nervous about unlocking the bootloader?
Didn't my Samsung phone come with it already unlocked?

Should you be nervous? Google the pros and cons then decide for yourself.
No phone nor tablet comes with an unlocked bootloader.

I have an XT1053 and just recently unlocked the bootloader through the Motorola site. I waited until now because my original warranty just expired and knew that unlocking the bootloader would void my warranty. I wanted to unlock the bootloader under 4.4.4 because I didn't know if there would be any problems once Lollipop was offered as an update. The unlock process went very smoothly and took only a few minutes. You probably already know that unlocking wipes your phone, so be prepared to reinstall apps and other files. I have not rooted yet because I'll probably wait to do that after the Lollipop OTA comes around. Even then, I may not root because I'm really pretty happy with the phone as it is. For me, unlocking the bootloader was just of way of preserving the future option to root.

stuntman2128 said:
Hey guys does anyone have step-by-step guide on how i can root this phone? I am not able to find a guide for XT1053 (T-Mobile) on 4.4.4. Specifically I want to install a 5.0 rom because I'm tired of waiting for the update. Any help will be appreciated;
Click to expand...
Click to collapse
Go to YouTube and search for qbking77 channel on how to unlock bootloader moto 2013.. Step by step tutorial with video
Sent from my XT1053 using XDA Premium 4 mobile app

mac1996 said:
Go to YouTube and search for qbking77 channel on how to unlock bootloader moto 2013.. Step by step tutorial with video
Sent from my XT1053 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
unlocking bootloader isn't a problem. I mainly want to know how i can put a custom recovery (prefer CWM because i've had it on previous phone). That way i can straight up install a custom rom that is already rooted without rooting stock. I just really want 5.0 really tired of 4.4.4

stuntman2128 said:
unlocking bootloader isn't a problem. I mainly want to know how i can put a custom recovery (prefer CWM because i've had it on previous phone). That way i can straight up install a custom rom that is already rooted without rooting stock. I just really want 5.0 really tired of 4.4.4
Click to expand...
Click to collapse
Do you have fastboot?
if yes, go to your phone bootloader.
Connect to your computer by USB.
Type the following in cmd. (place your recovery img file in fastboot directory)
fastboot flash recovery (your recovery name).img
Sent from my XT1053 using XDA Free mobile app

Check the sticky threads. There's only a year and halfs worth of information available to you here and all over the rest of the internet.

stuntman2128 said:
unlocking bootloader isn't a problem. I mainly want to know how i can put a custom recovery (prefer CWM because i've had it on previous phone). That way i can straight up install a custom rom that is already rooted without rooting stock. I just really want 5.0 really tired of 4.4.4
Click to expand...
Click to collapse
At any point after unlocking the bootloader... To flash recovery, did you do the following...
Start the phone in Fastboot/Bootloader mode.. then from the PC type...
mfastboot flash recovery YourRecovery.img
mfastboot reboot-bootloader
Follow onscreen directions to use vol down key and highlight recovery, then use vol up to select/enter recovery. Once in recovery you can reboot the phone and proceed with whatever you want.
Failure to reboot-bootloader and entering recovery immediately after flashing recovery (i.e. doing something else first) can result in the recovery not sticking.

4.4.4
a year old post by dray_jr says the following:
4.4 to 4.2.2 Pre Cam will Brick
4.2.2 Post Cam to 4.2.2 Pre Cam will Brick.
4.4.2 to to anything will Brick
4.4 to 4.2.2 Post Cam you are ok
Click to expand...
Click to collapse
can someone explain this to me? I got my phone around august 2014, it came with 4.4.3 and right now I'm on 4.4.4.
If I use the motorola website and follow their bootloader unlock steps am I fine? will I have any brick issues stated from the quote above?

Thread
Nevermind guys, found the perfect thread for 4.4.4 root!
Thread: http://forum.xda-developers.com/moto-x/moto-x-qa/step-step-instructions-unlocking-t2649738
Final question: I don't have to install supersu root if i install CM12 once i get into TWRP recovery am i correct? (since cms come rooted)

Would flashing a JB kernel (and only the kernel) work to root it as described here?: http://forum.xda-developers.com/crossdevice-dev/sony/guide-xperia-kitkat-4-4-4-rooting-t3003520

Completely different phone. What works on one does not always apply to another. If it worked on the Moto X, don't you think someone would've tried and documented it s sometime in the last 18 months?

nhizzat said:
Completely different phone. What works on one does not always apply to another. If it worked on the Moto X, don't you think someone would've tried and documented it s sometime in the last 18 months?
Click to expand...
Click to collapse
Of course its a different phone, but since the Moto X also came with JB stock, I was just wondering whether the same method would work for the ones who are stuck with 4.4.4 and no root.
And no, I don't think that every method has been tried already. the Razr I JB root with a locked BL for example only happened, cause I asked jcase nicely if he could code an app that uses an exploit. So, many times, without asking nothing will happen...

dagoban said:
Of course its a different phone, but since the Moto X also came with JB stock, I was just wondering whether the same method would work for the ones who are stuck with 4.4.4 and no root.
And no, I don't think that every method has been tried already. the Razr I JB root with a locked BL for example only happened, cause I asked jcase nicely if he could code an app that uses an exploit. So, many times, without asking nothing will happen...
Click to expand...
Click to collapse
I don't proclaim to know the ins and outs of all things android, but I do know this.. Just because a phone has android 4.4.4 doesn't mean its the same 4.4.4 with the same exact flaws and vulnerabilities, susceptible to the same exact root processes. Its why an exploit to root one phone, often doesn't work to root another.
In the case of the Moto X with a locked bootloader, JCASE has come out with many processes exploiting vulnerabilities for Android and the Apps on the Moto X to not only root it, but disable its write protection. As new OTA's have patched an exploit, he came out with other ways.
Starting wth 4.4.2, the vulnerability in the bootoader to disable write protection has been patched.
Jcase's Sunshine tool works on the X with 4.4.3 and lower, and only SOME with 4.4.4. It needs temp root first, etc. For whatever reason, we don't have a way to even temp root the 2013 X on 4.4.4 enough to allow Sunshine to do its work. And despite being asked many times, Jcase pretty much said in the Sunshine discussion threads that v3.0 wont have Moto X 4.4.4 support (unless he changed his mind and I missed it). Yet sunshine and its root processes, etc work on other phones (HTC) with 4.4.4.
But back to the thread you link...
On the X, due to its security measures, with a locked bootloader, you can only flash the Moto signed ROM for your phone. Nothing else. Because of this, you can't flash a custom recovery. To flash items, we use mFastboot and RSDLite. They need the img files, or bin files. If we make our own, they wont be signed, so they wont flash to a phone with a locked bootloader. And you can't package them into a flashable ZIP because stock recovery looks for the Moto digital signature (which we don't have and can't fake), and you can't install TWRP/CWM/Philz/etc to flash that way. So if you manage to pull the JB kernel out of the Moto SBF file, you wont be able to flash it.
Due to write protection on the 2013 X, any changes made to /System and a few other places, will be lost at power off/on. In other words, if you do manage to flash it (or push via adb), it wont stick due to write protection.
We've seen people try and manipulate their phone by trying to DOWNGRADE their ROM. Well, this doesn't work either. GPT.BIN (partition table), and Motoboot.img (bootloader, TZ, and a few other things) get in the way. Even on an X with an Unlocked bootloader, you can't downgrade these parts. Enough who attempted this have ended up bricking their phone immediately, or with later taking an OTA. Sure you can try to flash just system.img, and while that has less risk for bricking, people who have tried this were still not able to use the older Root Exploits (that worked if you hadn't upgraded already). People have tried flashing everything but GPT.BIN and MotoBoot.img. Again, it didn't help with rooting. Not to mention with a missmatched system.img or other parts, features on the phone may not always work properly (going Settings -> Security comes to mind), and you are at risk of bricking should you take an OTA update.
Since that process exploits a vulnerability, and its out there (so the vulnerability is in the public), I'm sure if it worked or was possible, JCASE, Beaups, or others would have put something together.
Now, back on topic of the XT1053... it has an Unlockable bootloader. Unlocking the bootloader disables write protection, and allows you to flash non-moto stuff. So unlocking the bootloader, flashing TWRP, reboot bootloader, enter TWRP and root, is quick, easy, effective, and doesn't rely on vulnerabilities on the phone to be exploited so patches/updates haven't got in the way. Plus you don't have to wait for someone to find them and create a repeatable process.

[Q] Upgrading to Lollipop from locked bootloader, rooted, Kitkat.

Hello all,
With news that the Z3 and Z3 compact are starting to get Lollipop today I am sure a lot of people are going to be coming to the boards asking this exact question. So I wanted to start a thread that can help people find the answer quickly. (I'll update the OP as useful info comes in.)
I am currently on a D5803 running 4.4.4, with a locked bootloader and am rooted. I used This how-to to get where I am.
What is the best way to upgrade to Lollipop for me?
Is there a way to keep root? A pre-rooted FTF file?
Will all DRM features remain?
Will I need to reinstall anything? Recovery? Busy Box? SU?
Does this upgrade require a full wipe?
Thanks for any help
If anyone wants to check if their bootloader is locked:
Dial *#*#7378423#*#* . Then go to -> "Service Info" -> "Configuration". If there is:
Bootloader unlock allowed - Yes << this means that your Bootloader is Locked
Bootloader Unlocked - Yes << this means that your bootloader is unlocked

just wonder...
i definitly want to root my Z3C.
Should i root with KK 4.4 or wait for Lollipop(and root later) !?

TheTomcraft said:
just wonder...
i definitly want to root my Z3C.
Should i root with KK 4.4 or wait for Lollipop(and root later) !?
Click to expand...
Click to collapse
You root on KK then you can update to Lollipop and keep root.

The problem seems to be getting recovery working, or keeping it working. Can anyone comment on whether they've tried the below:
1) Flash pre-rooted D5803_23.1.A.0.690_Customized_NCB rooted.zip containing Lollipop 5.0.2 in TWRP
2) Flash Z3C-lockeddualrecovery2.8.3-RELEASE.flashable.zip in TWRP
3) Flash UPDATE-SuperSU-v2.46.zip in TWRP
4) Flash the stock D5803_23.1.A.0.690_Baltic_Generic.ftf and exclude system (and data/cache from the wipe section to keep settings)?
In the other recovery threats NUT seems to think his recovery should still work?

Sean09 said:
The problem seems to be getting recovery working, or keeping it working. Can anyone comment on whether they've tried the below:
1) Flash pre-rooted D5803_23.1.A.0.690_Customized_NCB rooted.zip containing Lollipop 5.0.2 in TWRP
2) Flash Z3C-lockeddualrecovery2.8.3-RELEASE.flashable.zip in TWRP
3) Flash UPDATE-SuperSU-v2.46.zip in TWRP
4) Flash the stock D5803_23.1.A.0.690_Baltic_Generic.ftf and exclude system (and data/cache from the wipe section to keep settings)?
In the other recovery threats NUT seems to think his recovery should still work?
Click to expand...
Click to collapse
Recovery isn't working, but I'm happy with just root for now, which works great.
I didn't flash the stock after SuperSU, don't see any reason to and works for me.

frason said:
Recovery isn't working, but I'm happy with just root for now, which works great.
I didn't flash the stock after SuperSU, don't see any reason to and works for me.
Click to expand...
Click to collapse
could you please write what exactly you did to achieve this. Step by step guide would be awesome. Thanks!

gruev said:
could you please write what exactly you did to achieve this. Step by step guide would be awesome. Thanks!
Click to expand...
Click to collapse
Flashed "D5803_23.1.A.0.690_Customized_NCB rooted.zip" in TWRP.
Without rebooting, flashed "UPDATE-SuperSU-v2.46.zip" in TWRP.
Done, working root.

q.
frason said:
Flashed "D5803_23.1.A.0.690_Customized_NCB rooted.zip" in TWRP.
Without rebooting, flashed "UPDATE-SuperSU-v2.46.zip" in TWRP.
Done, working root.
Click to expand...
Click to collapse
Did you wipe? or flash over?

newbie2006 said:
Did you wipe? or flash over?
Click to expand...
Click to collapse
I wiped it (had too much crap on the phone anyway, so worth it), restored what I wanted with Titanium Backup when done.
---------- Post added at 10:24 PM ---------- Previous post was at 10:19 PM ----------
I also tried with flashing lockeddualrecovery but recovery doesn't work. So need to wait for an update on that one I guess.

Any ideas about what could go bad if I don't wipe data?
Also, do you still have drm?

I succesfully flashed lolipop with this method without data wipe. I still have root and DRM keys. The only thing I lost was data of some app's with external data linked to SD card with Link2SD. And some root app's started to claim about busybox not installed properly. Besides that everything works like a charm

frason said:
Flashed "D5803_23.1.A.0.690_Customized_NCB rooted.zip" in TWRP.
Without rebooting, flashed "UPDATE-SuperSU-v2.46.zip" in TWRP.
Done, working root.
Click to expand...
Click to collapse
When you flash those do you have system read and write as well? Do we need to worry about the RICDefeat in doing all this for the upgrade? Is RICDefeat integrated into that?

1.Flash the tft of lollipop
2.Get the zip of XZDualRecovery 2.8.3 Advanced Stock Kernel from http://nut.xperia-files.com/ and supersu from http://forum.xda-developers.com/showthread.php?t=1538053
3.Flash the boot.img in AndroPlusKernel with cable on flashtool
4.Reboot in recovery
5.Flash XZDualRecovery 2.8.3 Advanced Stock and supersu
6.Enjoy
Sorry，it should be with UB

about not working recovery
Dont know it thats issue, but I have same clue.
On KitKat after applying all steps to root 4.4.4 rom recovery was working until I changed busybox.
Oryginaly busybox was in version 1.20.2-jb - with that recovery was working.
I need some other tools and updated busbox to version 1.22.1 and recovery wasnt working (starting recovery end up with bootloop, but could start to system).
Returning back to recovery 1.20.2-jb fixed problem.

frason said:
Recovery isn't working, but I'm happy with just root for now, which works great.
I didn't flash the stock after SuperSU, don't see any reason to and works for me.
Click to expand...
Click to collapse
Sean09 said:
The problem seems to be getting recovery working, or keeping it working. Can anyone comment on whether they've tried the below:
1) Flash pre-rooted D5803_23.1.A.0.690_Customized_NCB rooted.zip containing Lollipop 5.0.2 in TWRP
2) Flash Z3C-lockeddualrecovery2.8.3-RELEASE.flashable.zip in TWRP
3) Flash UPDATE-SuperSU-v2.46.zip in TWRP
4) Flash the stock D5803_23.1.A.0.690_Baltic_Generic.ftf and exclude system (and data/cache from the wipe section to keep settings)?
In the other recovery threats NUT seems to think his recovery should still work?
Click to expand...
Click to collapse
I was hoping by adding step 4, it would be possible the encrypt device. Sadly it still creates a bootloop.

in my case I received the notification update via OTA, have Kit Kat with root if I update, will i lose root?

skaarax said:
in my case I received the notification update via OTA, have Kit Kat with root if I update, will i lose root?
Click to expand...
Click to collapse
I want to know about this too.
And what is a safe process for us (locked bootloader, rooted 4.4) to upgrade to 5.02 or 5.1 in the future.
I heard that unlocking bootloader will causes the camera not working properly (at least the auto mode would be messed up)
Does TWRP requiring unlocking bootloader?
Thanks guys.

I'm resurrecting this thread as I've got the same question as previous posters and I've not been able to find an answer elsewhere on the forum.
Basically, I've got a phone with a Bootloader which can't be unlocked. I upgraded/rooted it last year. It's still on KitKat. Is there any way I can upgrade it to Lollipop or Marshmallow without going through the downgrade/flash pre-rooted ROM procedure, without losing root? In other words, can I make use of TWRP which I installed in order to flash the rooted ROM last time? If so, how? (I'm not keen on using KingRoot unless somebody can convince me that handing over my IMEI info is safe.)
Thanks in advance.

Just flash a pre-rooted 5.1 zip made with prf creator whilst still on root+recovery KK. That's how I updated my M2 from rooted 4.4.4 KK to rooted 5.1 lollipop whilst retaining my locked bootloader. No sure if it's working for mm yet though this way

Help rooting?

Hello all,
Im totally confused as to how to go about rooting my device c6902. Ive owned a couple of android devices and Ive rooted them all, however....with this device and there seem to be different ways people have rooted from reading the threads and im totally confused, So far I have unlocked the bootloader, and upgraded the device OTA to lollipop .242 (before the bootloader was unlocked), I dont intend installing any custom firmware, just want root so I can use TB and maybe delete a few bloatwares with root explorer and use xposed.
Im confused as to whether:
1. I have to downgrade firmware to kitkat, just to get root, then upgrade back to official firmware?
2. Ive been under the impression that a custom recovery and supersu, is enough to get root. It doesnt work that way on this device?
3. I saw some oneclick root programs that worked on the z1 compact would any work here
Just trying to know more about the phone and understand, so any help is appreciated. Thanks in advance.

bigmeech084 said:
Hello all,
Im totally confused as to how to go about rooting my device c6902. Ive owned a couple of android devices and Ive rooted them all, however....with this device and there seem to be different ways people have rooted from reading the threads and im totally confused, So far I have unlocked the bootloader, and upgraded the device OTA to lollipop .242 (before the bootloader was unlocked), I dont intend installing any custom firmware, just want root so I can use TB and maybe delete a few bloatwares with root explorer and use xposed.
Im confused as to whether:
1. I have to downgrade firmware to kitkat, just to get root, then upgrade back to official firmware?
2. Ive been under the impression that a custom recovery and supersu, is enough to get root. It doesnt work that way on this device?
3. I saw some oneclick root programs that worked on the z1 compact would any work here
Just trying to know more about the phone and understand, so any help is appreciated. Thanks in advance.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2631291
Using the guide on the link I just posted, you are not required to unlock the bootloader, unlocking the bootloader without backing up the TA partition can cause problems with your phone.
You need to downgrade to KitKat 4.4.4 with kernel 108, then root it with easyroot install supersu and rootchecker to make sure your phone is rooted, the use NUTs recovery to create a recovery partition, after that search XDA forums for a pre-rooted lollipop flashable zip and install that, and voila you should be on lollipop with root and recovery.
I am not sure about one-click root programs.

demon148 said:
http://forum.xda-developers.com/showthread.php?t=2631291
Using the guide on the link I just posted, you are not required to unlock the bootloader, unlocking the bootloader without backing up the TA partition can cause problems with your phone.
You need to downgrade to KitKat 4.4.4 with kernel 108, then root it with easyroot install supersu and rootchecker to make sure your phone is rooted, the use NUTs recovery to create a recovery partition, after that search XDA forums for a pre-rooted lollipop flashable zip and install that, and voila you should be on lollipop with root and recovery.
I am not sure about one-click root programs.
Click to expand...
Click to collapse
Thanks for your help.
I already unlocked the bootloader though. Do I need to downgrade the whole kitkat rom or flash just the kernel? thanks

Figured out. Thanks

[Q] rooted, unlocked, TWRP recovery, stock, Verizon OTA help

I have a Verizon Nexus 6 that is rooted, unlocked, custom TWRP recovery and stock running 5.1 build LMY47E and I am getting the OTA notification for the 5.1.1 update. I have searched a good deal of places and haven't found the answer to how I might go about getting the update. I have been out of the rooting game for several years, so I am rusty and need a little help. I wasn't sure if there was a way to take the update and stay rooted or if I have to completely undo everything back to stock. Any info would be a great help and appreciated.

I could be mistaken, but I don't think that you can take an OTA amd remain rooted. I think it will break root, and you will have to re-root.
What I would suggest is to just flash a custom ROM that is build on 5.1.1 like Beans' PureNexus. That is what I am running, and it is great.
http://forum.xda-developers.com/nexus-6/development/rom-pure-nexus-project-t3148214

evolefty said:
I have a Verizon Nexus 6 that is rooted, unlocked, custom TWRP recovery and stock running 5.1 build LMY47E and I am getting the OTA notification for the 5.1.1 update. I have searched a good deal of places and haven't found the answer to how I might go about getting the update. I have been out of the rooting game for several years, so I am rusty and need a little help. I wasn't sure if there was a way to take the update and stay rooted or if I have to completely undo everything back to stock. Any info would be a great help and appreciated.
Click to expand...
Click to collapse
a.demarco said:
I could be mistaken, but I don't think that you can take an OTA amd remain rooted. I think it will break root, and you will have to re-root.
What I would suggest is to just flash a custom ROM that is build on 5.1.1 like Beans' PureNexus. That is what I am running, and it is great.
http://forum.xda-developers.com/nexus-6/development/rom-pure-nexus-project-t3148214
Click to expand...
Click to collapse
When installing a recovery, the updater script looks at system and boot. This means that you can not be rooted and and have the stock, encrypted kernel. You also need to have stock recovery to install the OTA.
You can download the 5.1.1 factory image from Google and flash the boot.img, system.img, bootloader.img, and radio.img. Then, while still in bootloader, select "recovery" and you will boot to TWRP where you can flash the SuperSU.zip.

a.demarco said:
I could be mistaken, but I don't think that you can take an OTA amd remain rooted. I think it will break root, and you will have to re-root.
What I would suggest is to just flash a custom ROM that is build on 5.1.1 like Beans' PureNexus. That is what I am running, and it is great.
http://forum.xda-developers.com/nexus-6/development/rom-pure-nexus-project-t3148214
Click to expand...
Click to collapse
The OTA will not install when the device is rooted

cam30era said:
When installing a recovery, the updater script looks at system and boot. This means that you can not be rooted and and have the stock, encrypted kernel. You also need to have stock recovery to install the OTA.
You can download the 5.1.1 factory image from Google and flash the boot.img, system.img, bootloader.img, and radio.img. Then, while still in bootloader, select "recovery" and you will boot to TWRP where you can flash the SuperSU.zip.
Click to expand...
Click to collapse
Just checked again and yes I am rooted, with TWRP and I also checked and the device is not encrypted, so maybe that is why I am getting the notification. I really appreciate your input on getting the update installed.

evolefty said:
Just checked again and yes I am rooted, with TWRP and I also checked and the device is not encrypted, so maybe that is why I am getting the notification. I really appreciate your input on getting the update installed.
Click to expand...
Click to collapse
You'll get the notification. You just can't flash it.

I'm not sure there's been a full, satisfactory answer to this thread (or a few others). Would using something like Nexus Root Toolkit to 1) unroot 2) restore stock recovery, 3) accept the OTA. Will this work?
- Does this relock the bootloader? (Would we then have to unlock, thus wiping the device?)
- Can we successfully re-root and flash recovery? (Or will new 5.1.1 versions be needed?)
At some point, to get 5.1.1 going, should I just backup and flash the whole bloody image from Google?

DogzOfWar said:
I'm not sure there's been a full, satisfactory answer to this thread (or a few others). Would using something like Nexus Root Toolkit to 1) unroot 2) restore stock recovery, 3) accept the OTA. Will this work?
- Does this relock the bootloader? (Would we then have to unlock, thus wiping the device?)
- Can we successfully re-root and flash recovery? (Or will new 5.1.1 versions be needed?)
At some point, to get 5.1.1 going, should I just backup and flash the whole bloody image from Google?
Click to expand...
Click to collapse
- OTA`s will not install if the sytem, boot and recovery are modified in any way.
- Reflashing the stock image will NOT lock the bootloader
- And yes you can flash a custom recovery and reroot after updating.
Or flash the latest stock rom with TWRP from here http://forum.xda-developers.com/nexus-6/development/fxz-nexus-6-recovery-flashable-fastboot-t3066052.

gee2012 said:
- OTA`s will not install if the sytem, boot and recovery are modified in any way.
- Reflashing the stock image will NOT lock the bootloader
- And yes you can flash a custom recovery and reroot after updating.
Or flash the latest stock rom with TWRP from here http://forum.xda-developers.com/nexus-6/development/fxz-nexus-6-recovery-flashable-fastboot-t3066052.
Click to expand...
Click to collapse
So the question that started this thread: My system is technically modified. Can I unroot and replace recovery, and now be in a sufficiently "unmodified" state? OR, do I have to lock the bootloader in order for the OTA to continue?
I think the OP and myself are trying to do the same thing: We're lazy, we don't want to wipe, we don't want to lose data, we just want the OTA without having to reflash the whole thing. Does anyone know if this is possible?

DogzOfWar said:
So the question that started this thread: My system is technically modified. Can I unroot and replace recovery, and now be in a sufficiently "unmodified" state? OR, do I have to lock the bootloader in order for the OTA to continue?
I think the OP and myself are trying to do the same thing: We're lazy, we don't want to wipe, we don't want to lose data, we just want the OTA without having to reflash the whole thing. Does anyone know if this is possible?
Click to expand...
Click to collapse
Best/easiest is to:
- fastboot erase system
- fastboot flash system system.img
- flash the stock boot and recovery.img if needed
- adb sideload the OTA in stock recovery
This will not wipe your device
And you don`t have to lock the bootloader ever unless you have too RMA it or send it in for service, OTA`s will even install with a unlocked bootloader.

DogzOfWar said:
So the question that started this thread: My system is technically modified. Can I unroot and replace recovery, and now be in a sufficiently "unmodified" state? OR, do I have to lock the bootloader in order for the OTA to continue?
I think the OP and myself are trying to do the same thing: We're lazy, we don't want to wipe, we don't want to lose data, we just want the OTA without having to reflash the whole thing. Does anyone know if this is possible?
Click to expand...
Click to collapse
Supplementing that: using the "unroot" function in SuperSU is not sufficient with Lollipop. It still leaves the vestiges of a few modified files that will cause an OTA to fail.
gee2012 said:
Best/easiest is to:
- fastboot erase system
- fastboot flash system system.img
- flash the stock boot and recovery.img if needed
- adb sideload the OTA in stock recovery
This will not wipe your device
And you don`t have to lock the bootloader ever unless you have too RMA it or send it in for service, OTA`s will even install with a unlocked bootloader.
Click to expand...
Click to collapse

gee2012 said:
Best/easiest is to:
- fastboot erase system
- fastboot flash system system.img
- flash the stock boot and recovery.img if needed
- adb sideload the OTA in stock recovery
This will not wipe your device
And you don`t have to lock the bootloader ever unless you have too RMA it or send it in for service, OTA`s will even install with a unlocked bootloader.
Click to expand...
Click to collapse
Thanks for the info and I really appreciate your input. What are your feelings on using Wug's toolkit to unroot and go back stock, take the update, then re-root and flash the custom recovery. I have never used a toolkit before, but that seems to be the popular method. Like I said at the beginning I am new to all of this, the last device I rooted and really messed around with was the droid x so bear with me as I am learning. I am currently reading about Wug's and will look at the method you just spoke of, but any info would be great.

evolefty said:
Thanks for the info and I really appreciate your input. What are your feelings on using Wug's toolkit to unroot and go back stock, take the update, then re-root and flash the custom recovery. I have never used a toolkit before, but that seems to be the popular method. Like I said at the beginning I am new to all of this, the last device I rooted and really messed around with was the droid x so bear with me as I am learning. I am currently reading about Wug's and will look at the method you just spoke of, but any info would be great.
Click to expand...
Click to collapse
I don`t like Toolkits tbh because like with all automated applications the unexperienced user has no idea whats going/has zero control over whats happening and if something goes wrong they can`t fix the issue. Imo its best to learn adb/fastboot/sideload.

gee2012 said:
I don`t like Toolkits tbh because like with all automated applications the unexperienced user has no idea whats going/has zero control over whats happening and if something goes wrong they can`t fix the issue. Imo its best to learn adb/fastboot/sideload.
Click to expand...
Click to collapse
Gotcha, and completely understand. I will do some reading on that method and again thanks for your help.

evolefty said:
Gotcha, and completely understand. I will do some reading on that method and again thanks for your help.
Click to expand...
Click to collapse
Read the sticky threads http://forum.xda-developers.com/nexus-6/general/nexus-6-sticky-roll-thread-t3061066, this is a good start. Adb and fastboot isn`t that hard but its very safe and effective

gee2012 said:
Read the sticky threads http://forum.xda-developers.com/nexus-6/general/nexus-6-sticky-roll-thread-t3061066, this is a good start. Adb and fastboot isn`t that hard but its very safe and effective
Click to expand...
Click to collapse
Will do, and that is the method I used to root for the simple fact to learn.

evolefty said:
Will do, and that is the method I used to root for the simple fact to learn.
Click to expand...
Click to collapse
Good luck

gee2012 said:
- OTA`s will not install if the sytem, boot and recovery are modified in any way.
- Reflashing the stock image will NOT lock the bootloader
- And yes you can flash a custom recovery and reroot after updating.
Or flash the latest stock rom with TWRP from here http://forum.xda-developers.com/nexus-6/development/fxz-nexus-6-recovery-flashable-fastboot-t3066052.
Click to expand...
Click to collapse
In that link you sent I am not seeing the VZW version of 5.1.1. Can we use the "International" version?
Thank you.

needoZ said:
In that link you sent I am not seeing the VZW version of 5.1.1. Can we use the "International" version?
Thank you.
Click to expand...
Click to collapse
Yes, use the LMY47Z build.

DogzOfWar said:
So the question that started this thread: My system is technically modified. Can I unroot and replace recovery, and now be in a sufficiently "unmodified" state? OR, do I have to lock the bootloader in order for the OTA to continue?
I think the OP and myself are trying to do the same thing: We're lazy, we don't want to wipe, we don't want to lose data, we just want the OTA without having to reflash the whole thing. Does anyone know if this is possible?
Click to expand...
Click to collapse
Bootloader does not have to be locked to take an OTA. You can not be rooted or modified in any way however.
gee2012 said:
I don`t like Toolkits tbh because like with all automated applications the unexperienced user has no idea whats going/has zero control over whats happening and if something goes wrong they can`t fix the issue. Imo its best to learn adb/fastboot/sideload.
Click to expand...
Click to collapse
While I agree, once you have "paid your dues" and flashed without automation then the NRT is a great tool, so long as you have an understanding of what it is doing.