Database Develop

Will Nexus 6 get OTA updates if rooted and custom recovery is installed?

I'm new to the nexus line. Just wondering if OTA updates will work after rooting my device or do I have to return to stock to get the update? Currently I'm rooted stock , decrypted, and TWRP recovery installed. Should I return to full stock locked or what?

gwojo22 said:
I'm new to the nexus line. Just wondering if OTA updates will work after rooting my device or do I have to return to stock to get the update? Currently I'm rooted stock , decrypted, and TWRP recovery installed. Should I return to full stock locked or what?
Click to expand...
Click to collapse
ive hear any alteration on the system files will stop the ota from installing. i assume that means recovery as well

gwojo22 said:
I'm new to the nexus line. Just wondering if OTA updates will work after rooting my device or do I have to return to stock to get the update? Currently I'm rooted stock , decrypted, and TWRP recovery installed. Should I return to full stock locked or what?
Click to expand...
Click to collapse
shelooga said:
ive hear any alteration on the system files will stop the ota from installing. i assume that means recovery as well
Click to expand...
Click to collapse
sheloga is correct. You'd have to revert back to full stock or wait for someone to make a flashable zip.

Can't you just flash the stock recovery and take the OTA? Or do you have to fully unroot and reflash the factory image?

I would like to pay close attention time to this thread because that is one is the main questions that I have. I hear so many different solutions towards this. I usually wait for a flashable zip but I would want to see someone either wrote a write up or make a video. Subscribed.

My understanding (from looking at the lollipop OTA updater-script) is it checks EVERY file for changes, including other partitions. You must be 100% stock with nothing extra in system (SuperSU apk or busybox etc).

gwojo22 said:
I'm new to the nexus line. Just wondering if OTA updates will work after rooting my device or do I have to return to stock to get the update? Currently I'm rooted stock , decrypted, and TWRP recovery installed. Should I return to full stock locked or what?
Click to expand...
Click to collapse
get and being able to apply are two differing things. unless you make it so you cant receive, then you will get an ota. problem is, that you will not be able to apply the update. 1. you can flash the factory img. 2. you can wait for someone to upload a flashable zip. 3. or you can do what most noobs do, and waste your time. what most noobs do is unroot, and flash the stock recovery, then wait for the update.

BLUF: wait until OTA is made available in a recovery flash method. 90% of the time the OTA updates are patching security holes and other less important features.
Having been with a handful of different android devices in the past several years, I've always gone the route of flashing from recovery vs. OTA.
The LG G3 for example had an OTA just recently that broke rooting. It was fixed by a Dev, but that's the only update found in OTA.
Sent from my Nexus 6 using XDA Free mobile app

Once you root the phone you cannot receive OTA updates. However, you arent out of luck when updates are released. Because you have a custom recovery, its easy to just download the update file when its released and install it that way. Once the AOSP updates are uploaded from Google, its all yours. Most people who dont receive their OTA and dont have a custom recovery will typically install it on their own but using ADB.

simms22 said:
get and being able to apply are two differing things. unless you make it so you cant receive, then you will get an ota. problem is, that you will not be able to apply the update. 1. you can flash the factory img. 2. you can wait for someone to upload a flashable zip. 3. or you can do what most noobs do, and waste your time. what most noobs do is unroot, and flash the stock recovery, then wait for the update.
Click to expand...
Click to collapse
I read in one of RootSU's threads (I think) that as of Lollipop, OTA via ADB sideload is the only option to apply an update. Any thoughts?

wvcadle said:
I read in one of RootSU's threads (I think) that as of Lollipop, OTA via ADB sideload is the only option to apply an update. Any thoughts?
Click to expand...
Click to collapse
no thoughts.
i just flash aosp hours after it appears there. or just wait for @rascarlo to add it to his rom, then i flash

HyperM3 said:
Because you have a custom recovery, its easy to just download the update file when its released and install it that way. Once the AOSP updates are uploaded from Google, its all yours. Most people who dont receive their OTA and dont have a custom recovery will typically install it on their own but using ADB.
Click to expand...
Click to collapse
wvcadle said:
I read in one of RootSU's threads (I think) that as of Lollipop, OTA via ADB sideload is the only option to apply an update. Any thoughts?
Click to expand...
Click to collapse
After Android 5.0, you can't sideload the OTA file if you have made any changes to the system partition. You need to be completely stock to take OTA. You can just download the new factory images and extract the various img files from it and just flash those manually in ADB, thereby overwriting your modified system partition with the new factory system image (you can skip overwriting the userdata if you want to preserve your data). No need to revert back to stock (old image) and then take OTA - unnecessary step.

HyperM3 said:
Once you root the phone you cannot receive OTA updates. However, you arent out of luck when updates are released. Because you have a custom recovery, its easy to just download the update file when its released and install it that way. Once the AOSP updates are uploaded from Google, its all yours. Most people who dont receive their OTA and dont have a custom recovery will typically install it on their own but using ADB.
Click to expand...
Click to collapse
I understand what your saying. Is there any difference between the OTA and AOSP? Like modem or kernel? I actually like the stock on this device. It seems like there are problems with the AOSP ROMS that are available now such as Netflix and Play Movies not working.
I'm coming from Samsung devices which were completely different as far as rooting and return to stock. I would go to SamMobile to get the stock firmware on my Galaxy S5. Where do I find stock firmware for the nexus?

gwojo22 said:
I understand what your saying. Is there any difference between the OTA and AOSP? Like modem or kernel? I actually like the stock on this device. It seems like there are problems with the AOSP ROMS that are available now such as Netflix and Play Movies not working.
I'm coming from Samsung devices which were completely different as far as rooting and return to stock. I would go to SamMobile to get the stock firmware on my Galaxy S5. Where do I find stock firmware for the nexus?
Click to expand...
Click to collapse
From google
https://developers.google.com/android/nexus/images

hlxanthus said:
From google
https://developers.google.com/android/nexus/images
Click to expand...
Click to collapse
How does one do this on a Mac? Could you perhaps link us? All I'm finding is guides for windows unfortunately

waqar.qu said:
How does one do this on a Mac? Could you perhaps link us? All I'm finding is guides for windows unfortunately
Click to expand...
Click to collapse
You need to install ADB and fastboot. After that, you can use the 'fastboot' command directly from Terminal. I've found that the easiest way to update Lollipop on my Nexus 6 is to:
Download image from Google
Decompress the archive, AND the second archive which was contained within the first one. Note: The recovery, boot, and system images are in the second archive.
Open Terminal, change directory to the extracted folder, and run these commands (they skip overwriting the userdata partition):
fastboot flash bootloader <bootloader file name here>.img
fastboot flash radio <radio file name here>.img
fastboot reboot-bootloader (VERY IMPORTANT TO DO THIS STEP)
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
fastboot reboot
You need to restore root at this point; you can use these instructions if you're unfamiliar with the procedure.

[Q] Rooted 5.0.1, OTA update to T-mo 5.1 offered, failed. How to proceed?

Hello everyone. My Nexus 6 has been running standard 5.0.1, which I rooted (using WugFresh's Nexus Root Toolkit - very useful software) . SuperSU has been installed, along with BusyBox, with TWRP as the custom recovery. My service is on T-Mobile, and just today my system update informed me that the 5.1 OTA update was ready to download and install. I allowed it the right to download and it claimed to be rebooting to install. Unfortunately, it rebooted into TWRP (I am guessing it expected the standard recovery)? I told TWRP it to simply reboot into the OS, and it appear the update has failed - nothing has changed. I'm still on 5.0.1 as shown in the settings etc.. Furthermore, attempting to check for System Updates again show no updates available; it seems it has "forgotten" that OTA 5.1 exists and/or assumes that it has already been pulled down properly? This is my first time updating a stock, yet rooted, ROM - I'm used to flashing or using another update system included in custom ROMs such as Cyanogen . I had hoped that since the OTA update was offered, it would have worked without the necessity to wipe my data as in a normal flash. I am guessing the error was in using the OTA update at all, or perhaps having TWRP installed? So I guess I am trying to figure out the best path forward from here.
I am to understand that the T-Mobile OTA 5.1 update activates a number of new features ,including VOLTE etc... so I want to be sure I get the correct ROM, as well as any baseband changes that may be necessary. I still have TWRP and the like, so I assume I could flash the update manually, if I was sure it was the right build and I got all the needed files. Now, I have to wonder, it appears that during the original OTA update, it did download the ROM somewhere. Perhaps I could find it on my device and select it in TWRP to update? Or would that not provide all the necessary files , overwrite something, or otherwise cause problems? Anyone point me in the correct direction perchance? Thanks.
Edit: I may have not been prompted for another OTA update because my battery was < 50%. Plugging it in and seeing if this changes anything. I read on Tmo's page that >50% battery is necessary to "qualify" for the update?
Also, according to https://support.t-mobile.com/docs/DOC-18109 - the Tmo 5.1 is "LMY47M". This build is not available yet at https://developers.google.com/android/nexus/images - only the "D" and "E" versions. Does this "M" version include VoLTE calling? I'm seeing discussion about these differing versions, yet very little solid information. I can't believe Google would split the ROM by carrier for a Nexus device! That's insane... having to look for all the custom ROMs that are built with the proper carrier specific build in mind!

a phone that is pure stock can take an ota. a phone that has any files changed, or not pure stock can not flash an ota, doesnt matter how many otas you try. you will have to flash the factory img.

So I should wait until 5.1 LMY47M is available and simply flash it via TWRP? Will I need to wipe anything at all when I flash it? Will I need to flash anything else, like Gapps? Rooting will need to be performed again? If I was running a custom ROM I'd know what to expect, but I'm a bit out of my element here.

RanceJustice said:
So I should wait until 5.1 LMY47M is available and simply flash it via TWRP? Will I need to wipe anything at all when I flash it? Will I need to flash anything else, like Gapps? Rooting will need to be performed again? If I was running a custom ROM I'd know what to expect, but I'm a bit out of my element here.
Click to expand...
Click to collapse
you cant flash it in twrp. you can flash the factory img via fastboot while youre in the bootloader. or you can flash a 5.1 custom rom, that will be easier.

RanceJustice said:
So I should wait until 5.1 LMY47M is available and simply flash it via TWRP? Will I need to wipe anything at all when I flash it? Will I need to flash anything else, like Gapps? Rooting will need to be performed again? If I was running a custom ROM I'd know what to expect, but I'm a bit out of my element here.
Click to expand...
Click to collapse
If you want to take the OTA, do the following:
Download the 5.0.1 factory zip.
Extract all of the files.
To unroot, fastboot flash the system.img.
Fastboot flash the stock recovery.img.
If you are unencrypted, fastboot flash the stock boot.img.

RanceJustice said:
Hello everyone. My Nexus 6 has been running standard 5.0.1, which I rooted (using WugFresh's Nexus Root Toolkit - very useful software) . SuperSU has been installed, along with BusyBox, with TWRP as the custom recovery. My service is on T-Mobile, and just today my system update informed me that the 5.1 OTA update was ready to download and install. I allowed it the right to download and it claimed to be rebooting to install. Unfortunately, it rebooted into TWRP (I am guessing it expected the standard recovery)? I told TWRP it to simply reboot into the OS, and it appear the update has failed - nothing has changed. I'm still on 5.0.1 as shown in the settings etc.. Furthermore, attempting to check for System Updates again show no updates available; it seems it has "forgotten" that OTA 5.1 exists and/or assumes that it has already been pulled down properly? This is my first time updating a stock, yet rooted, ROM - I'm used to flashing or using another update system included in custom ROMs such as Cyanogen . I had hoped that since the OTA update was offered, it would have worked without the necessity to wipe my data as in a normal flash. I am guessing the error was in using the OTA update at all, or perhaps having TWRP installed? So I guess I am trying to figure out the best path forward from here.
I am to understand that the T-Mobile OTA 5.1 update activates a number of new features ,including VOLTE etc... so I want to be sure I get the correct ROM, as well as any baseband changes that may be necessary. I still have TWRP and the like, so I assume I could flash the update manually, if I was sure it was the right build and I got all the needed files. Now, I have to wonder, it appears that during the original OTA update, it did download the ROM somewhere. Perhaps I could find it on my device and select it in TWRP to update? Or would that not provide all the necessary files , overwrite something, or otherwise cause problems? Anyone point me in the correct direction perchance? Thanks.
Edit: I may have not been prompted for another OTA update because my battery was < 50%. Plugging it in and seeing if this changes anything. I read on Tmo's page that >50% battery is necessary to "qualify" for the update?
Also, according to https://support.t-mobile.com/docs/DOC-18109 - the Tmo 5.1 is "LMY47M". This build is not available yet at https://developers.google.com/android/nexus/images - only the "D" and "E" versions. Does this "M" version include VoLTE calling? I'm seeing discussion about these differing versions, yet very little solid information. I can't believe Google would split the ROM by carrier for a Nexus device! That's insane... having to look for all the custom ROMs that are built with the proper carrier specific build in mind!
Click to expand...
Click to collapse
Please take a bug report and find the OTA link inside. Instructions here: https://www.reddit.com/r/nexus6/comments/2zlqid/psa_if_you_receive_the_tmobile_51_ota_update/

[Q] Returning to un-rooted 5.0 on XT1095?

I'm assuming that since I've rooted my Pure Edition that once the official 5.1 OTA comes it will fail to install just like 5.0-5.02 on my N7 did. I'm wondering how I can get back to unrooted without wiping the phone out (if that's possible). I can't seem to find the factory 5.0 image at the Motorola site so right now I'm assuming I'll have to install the 4.4..4 image and then let the OTA's roll in?
When I ran into this on my N7 other than rooting the only system installed app I had added in was better battery stats and removing root and getting rid of (at least I think I got rid of it) BBS the OTA failed still and I had to just flash the system.img from the factory image. On my XT1095 I only have SuperSU installed. I never installed BBS or any other new apps as system apps so maybe telling SuperSU to unroot and clean up will work?

Maybe I'm wrong, but I was under the impression you could still receive the OTA with root as long as you were on stock recovery, you would just lose root access in the process. I could be way off, though. I have always had TWRP on my rooted phones. I am pretty confident that you cannot switch back to stock recovery from TWRP without wiping. You can always use Helium Pro to back everything up. Unlike TiBu, it does not require root. Or you could just wait on someone to release a .zip of the OTA and flash it manually.

Paddington said:
Maybe I'm wrong, but I was under the impression you could still receive the OTA with root as long as you were on stock recovery, you would just lose root access in the process. I could be way off, though. I have always had TWRP on my rooted phones. I am pretty confident that you cannot switch back to stock recovery from TWRP without wiping. You can always use Helium Pro to back everything up. Unlike TiBu, it does not require root. Or you could just wait on someone to release a .zip of the OTA and flash it manually.
Click to expand...
Click to collapse
It used to be that way before 5.0. Something changed in 5.0+ and now if certain parts of the file system are off at all from stock, OTA will fail. That's why I mentioned the example of my Nexus 7 failing the update from 5.0 to 5.02. I don't know if Motorola is keeping the same kinds of checks as Nexus OTA's though. I do still have the stock recovery. If I need TWRP for something I just temporarily boot it with fastboot instead.

Any luck with this? I too would like to unroot. Still stock recovery.

flyinion said:
I can't seem to find the factory 5.0 image at the Motorola site
Click to expand...
Click to collapse
Here you go:
http://www.graffixnyc.com/motox.php
flyinion said:
so right now I'm assuming I'll have to install the 4.4..4 image and then let the OTA's roll in?:cyclops:
Click to expand...
Click to collapse
No, 4.4.4 won't boot with the 5.0 boot.img. And NEVER attempt to downgrade the bootloader (motoboot.img) or partition table (gpt.bin) of a Motorola Moto X. These are NOT Nexus devices.

Thanks very much! So...in an abundance of caution, I should be able to flash boot.img and that will get rid of root? Or system.img too? And neither of those affect my data? Edit: I am rooted on 22.21.11 XT1095 with stock recovery
Hmm. Not available on that site anymore but found it at http://motofirmware.center/files/file/76-tmo_xt1095_50_lxe2246-11_cid9_cfcxmlzip/

Mnemoch said:
Thanks very much! So...in an abundance of caution, I should be able to flash boot.img and that will get rid of root? Or system.img too? And neither of those affect my data? Edit: I am rooted on 22.21.11 XT1095 with stock recovery
Click to expand...
Click to collapse
Just flash 5.0 system.img that is all you need unless you flashed a custom kernel
Personally I would not take the OTA - I would use Motorola Device Manager to update. If you are rooted you can uninstall MotorolaOTA and then when people report the OTA is being pushed, flash system back to stock and then let MDM update you - you will have a copy of the 5.1 fxz on your computer then.

Thanks for the advice, I will check out MDM and yes, waiting for the OTA to be published officially.
That other link I posted for the full image file was corrupt, but I found http://graffixnyc.com/development/motox2014/lollipop/22.21.11/ which has system.img available. But this is huge! Does it seem correct to you by any chance? Should be able to flash without losing my data?
JulesJam said:
Just flash 5.0 system.img that is all you need unless you flashed a custom kernel
Personally I would not take the OTA - I would use Motorola Device Manager to update. If you are rooted you can uninstall MotorolaOTA and then when people report the OTA is being pushed, flash system back to stock and then let MDM update you - you will have a copy of the 5.1 fxz on your computer then.
Click to expand...
Click to collapse

Thanks guys, I did find the image and had downloaded it from that link a while back. I also picked up the mfastboot tool, but I'm not sure how to use it to flash a system.img. That download has a bunch of system.img_sparsechunk.n files where .n is a number from 0-7 but there's no "base" system.img file. Do I just tell it to flash file 0 and it will pick up the rest of them automatically?

flyinion said:
Thanks guys, I did find the image and had downloaded it from that link a while back. I also picked up the mfastboot tool, but I'm not sure how to use it to flash a system.img. That download has a bunch of system.img_sparsechunk.n files where .n is a number from 0-7 but there's no "base" system.img file. Do I just tell it to flash file 0 and it will pick up the rest of them automatically?
Click to expand...
Click to collapse
No you have to do each 1 at a time. Regular fastboot can flash the sparsechunks - you only need mfastboot if the image is a single file.
fastboot flash system sparsechunk0
then when it is done
fastboot flash system sparsechunk1
until you have flashed them all

JulesJam said:
No you have to do each 1 at a time. Regular fastboot can flash the sparsechunks - you only need mfastboot if the image is a single file.
fastboot flash system sparsechunk0
then when it is done
fastboot flash system sparsechunk1
until you have flashed them all
Click to expand...
Click to collapse
Ah ok, I thought I needed mfastboot from what I was able to read around here. So the standard fastboot that comes with the android sdk can be used on the chunks?

Actually I think maybe I understand now. I read something a little bit ago about the difference between fastboot and mfastboot (Motorola Fastboot) and that the latter was created due to a file size limitation with the original fastboot. It didn't go into more detail than that. My assumption instantly was motorola was splitting the system image up into chunks and created that new fastboot to handle that. Seems it's the other way around? Google's fastboot can handle chunks and Moto's can handle a single image that is larger than what the standard fastboot can so they don't have to split it up in the first place?

Which download has chunks, the zip that we can't download any more or the system.img that I found? Should I try to extract it?
flyinion said:
Actually I think maybe I understand now. I read something a little bit ago about the difference between fastboot and mfastboot (Motorola Fastboot) and that the latter was created due to a file size limitation with the original fastboot. It didn't go into more detail than that. My assumption instantly was motorola was splitting the system image up into chunks and created that new fastboot to handle that. Seems it's the other way around? Google's fastboot can handle chunks and Moto's can handle a single image that is larger than what the standard fastboot can so they don't have to split it up in the first place?
Click to expand...
Click to collapse

Mnemoch said:
Which download has chunks, the zip that we can't download any more or the system.img that I found? Should I try to extract it?
Click to expand...
Click to collapse
Oh, the one that doesn't work anymore. I downloaded it a few weeks ago. Not sure when it got taken offline since the link is there, but yeah I see the download doesn't work any longer. If you have just a single system.img and not a bunch of system.img_sparsechunk.n files then you have a different image.

Anyone unrooted since the OTA came out?

JulesJam said:
No you have to do each 1 at a time. Regular fastboot can flash the sparsechunks - you only need mfastboot if the image is a single file.
fastboot flash system sparsechunk0
then when it is done
fastboot flash system sparsechunk1
until you have flashed them all
Click to expand...
Click to collapse
Anyone use this process to unroot stock 22.21.11?
And if so, did you get and take the 5.1 OTA or did you sideload it?
Thanks

eKeith said:
Anyone use this process to unroot stock 22.21.11?
And if so, did you get and take the 5.1 OTA or did you sideload it?
Thanks
Click to expand...
Click to collapse
Unrooting using this method does work!

Maybe unrelated, but in my confusion as to what's going on, is it at all possible to flash the 5.1 ota update over a custom rom? I'm currently on resurrection remix that's running on 5.1.1, but I really want to go back to stock. Thanks in advance.

dcdrew713 said:
Maybe unrelated, but in my confusion as to what's going on, is it at all possible to flash the 5.1 ota update over a custom rom? I'm currently on resurrection remix that's running on 5.1.1, but I really want to go back to stock. Thanks in advance.
Click to expand...
Click to collapse
Not possible. You have to flash the stock rom first, then take the ota.
Sent from my XT1095 using Tapatalk

Any idea what stock rom to use? 5.0? Sorry, I'm not the best with this stuff anymore, haha.

Not a noob, but still confused.

I have a nexus 6. I have been using custom ROMs from the days of xperia mini pro. Never had a Nexus before. I want to have root in my nexus 6 for ad blocking cereberus and more. But this time I don't want custom ROMs. I just need the OTA's. I know OTA's dont happen automatically after root. So please tell me should I root and put a custom recovery, Or just root for manually updating the OTA's. Where can I get all the OTA's ?? I know it's a lot of questions.. Please.

Quick answer: Isn't going to happen.
Reason: Lollipop wont install OTA if you modify /system, because it is now written as a block, unlike previous versions of android.
IF you root, you have modified /system.
Consequence: you will not update by OTA while rooted. It will fail.
Possible workaround: You can however AFAIK, unroot and then take an OTA, but I'll let others confirm this, please don't take me saying it as factual.
Factory image flash: always works, but you have to await the release after the updates.

mad_rulzzz said:
I have a nexus 6. I have been using custom ROMs from the days of xperia mini pro. Never had a Nexus before. I want to have root in my nexus 6 for ad blocking cereberus and more. But this time I don't want custom ROMs. I just need the OTA's. I know OTA's dont happen automatically after root. So please tell me should I root and put a custom recovery, Or just root for manually updating the OTA's. Where can I get all the OTA's ?? I know it's a lot of questions.. Please.
Click to expand...
Click to collapse
FWIW: I would recommend that you:
1) Unlock bootloader
2) Decide if you want uncrypted kernel, or not (since it wipes data, just like unlocking bootloader).
3) Fastboot flash TWRP recovery.
4) Download SuperSU .zip and flash it in recovery.
5) Now, when a new OTA comes out, they usually show up here > http://forum.xda-developers.com/nexus-6/general/ref-nexus-6-stock-ota-urls-t2906493
6) You can download your current factory image here > https://developers.google.com/android/nexus/images
7) Unzip your current factory image. Fastboot flash the system.img and that will unroot and restore the stock recovery.
8) Fastboot flash the stock boot.img if you have a custom kernel (or an unencrypted stock kernel).
9) Relax and wait for the OTA.

RW-1 said:
Quick answer: Isn't going to happen.
Reason: Lollipop wont install OTA if you modify /system, because it is now written as a block, unlike previous versions of android.
IF you root, you have modified /system.
Consequence: you will not update by OTA while rooted. It will fail.
Possible workaround: You can however AFAIK, unroot and then take an OTA, but I'll let others confirm this, please don't take me saying it as factual.
Factory image flash: always works, but you have to await the release after the updates.
Click to expand...
Click to collapse
I knew about the OTA failing due to the system partition getting changed while rooting. I think what I was looking for what cam30era just explained!!!

mad_rulzzz said:
I have a nexus 6. I have been using custom ROMs from the days of xperia mini pro. Never had a Nexus before. I want to have root in my nexus 6 for ad blocking cereberus and more. But this time I don't want custom ROMs. I just need the OTA's. I know OTA's dont happen automatically after root. So please tell me should I root and put a custom recovery, Or just root for manually updating the OTA's. Where can I get all the OTA's ?? I know it's a lot of questions.. Please.
Click to expand...
Click to collapse
You can just update in fastboot without an OTA. Just flash the new bootloader, system and possibly the new boot.img in fastboot and reroot. Erase and flash cache.img afterwards. Thats how i do it at least.

mad_rulzzz said:
I knew about the OTA failing due to the system partition getting changed while rooting. I think what I was looking for what cam30era just explained!!!
Click to expand...
Click to collapse
What he just explained is what I said, unroot and take the OTA.... He listed how as well.

RW-1 said:
What he just explained is what I said, unroot and take the OTA.... He listed how as well.
Click to expand...
Click to collapse
Yup.

@rw_1 @cam30era thanks guys

I would do what gee2012 said.
From what I have seen the OTA and the images are released pretty close together.
Instead of flashing images to get back to stock and waiting for the OTA. and then re-rooting
Just download the image files from Google. Manually flash all the files EXCEPT user data if you want to keep your data.
Re-root.
You are now updated and don't have to wait for OTA.
Either way works so it depends on which you are happier with.

mad_rulzzz said:
@rw_1 @cam30era thanks guys
Click to expand...
Click to collapse
Welcome. And BTW: there's a button for that.

gee2012 said:
You can just update in fastboot without an OTA. Just flash the new bootloader, system and possibly the new boot.img in fastboot and reroot. Erase and flash cache.img afterwards. Thats how i do it at least.
Click to expand...
Click to collapse
Just to be sure I understood right:
If I don't care about app data or settings ( I have titanium backup),
1)I can just unlock the boot loader
2)Flash the latest factory image from [developers.google.com/android/nexus/images]
3)Root using chain fire's tool
And repeat the process when the factory image of the next version is uploaded by google.
one last thing... Does Google upload factory images after each OTA happens?

cam30era said:
Welcome. And BTW: there's a button for that.
Click to expand...
Click to collapse
My BAd!!

mad_rulzzz said:
If I don't care about app data or settings ( I have titanium backup),
1)Can I just unlock the boot loader
2)Flash the latest factory image from [developers.google.com/android/nexus/images]
3)Root using chain fire's tool
And repeat the process when the factory image of the next version is uploaded by google.
Does Google upload factory images after each OTA happens? i.e; If Nexus 6 receives an OTA to 5.2, will they upload the 5.2 factory image soon?
Click to expand...
Click to collapse
When you unlock the bootloader it will wipe the contents of your SD card. Make sure it is backed up on your PC.
Unfortunately, not every OTA gets published as a factory image. Most, but not all. Case in point: LMY47M.

cam30era said:
Unfortunately, not every OTA gets published as a factory image. Most, but not all. Case in point: LMY47M.
Click to expand...
Click to collapse
I noticed that.... But that build is only for T-Mobile users, I guess...
Minor Differences, for example; If you take the android builds for Indian phones they are required by law to display the SAR rating. So I wouldn't worry about LMY47M, unless they have changed something to fix the memory leaks.

mad_rulzzz said:
I noticed that.... But that build is only for T-Mobile users, I guess...
Minor Differences, for example; If you take the android builds for Indian phones they are required by law to display the SAR rating. So I wouldn't worry about LMY47M, unless they have changed something to fix the memory leaks.
Click to expand...
Click to collapse
Correct. M is intended for T-Mobile. My point, though, is that Google doesn't always, 100% of the time publish a factory image for every OTA.

OTA with a rooted device?

Hi everyone, it's been a while since I started thinking to root my Moto G 2 but I still want to run on stock kernel & ROM. We are still waiting for the update to Android 5.1 and I was wondering if I could get the OTA safely with a rooted device. If not, I would wait for the official update and after this I'm going to root it; otherwise I would root it now. Thanks in advance.

I think you should wait for the OTA update and root after the update.

You won't receive any OTA updates from Motorola if you have flashed custom recovery and rooted your device

Copy that, thank you guys.

Nahuwii said:
You won't receive any OTA updates from Motorola if you have flashed custom recovery and rooted your device
Click to expand...
Click to collapse
If I understood it right, @luke! wants to run stock rom after rooting. So there is absolutely no problem to boot into TWRP 2.8.5.0, make a nandroid backup and flash latest superSU from there. OTA just cares about custom recovery and changes in system. So when an OTA arrives just restore your nandroid backup or revert the changes you made like unfreezing systemapps, uninstalling things like adaway and there will be no problem to install OTA.
Even if you flash twrp instead of booting into it,you can easily flash back the custom recovery. As long you stay stock this is all an easy thing. And also after flashing a custom rom there are ways to get back to the original firmware. @luke!:If you need any help pm me.

Wolfcity said:
If I understood it right, @luke! wants to run stock rom after rooting. So there is absolutely no problem to boot into TWRP 2.8.5.0, make a nandroid backup and flash latest superSU from there. OTA just cares about custom recovery and changes in system. So when an OTA arrives just restore your nandroid backup or revert the changes you made like unfreezing systemapps, uninstalling things like adaway and there will be no problem to install OTA.
Even if you flash twrp instead of booting into it,you can easily flash back the custom recovery. As long you stay stock this is all an easy thing. And also after flashing a custom rom there are ways to get back to the original firmware. @luke!:If you need any help pm me.
Click to expand...
Click to collapse
Great! Thank you, very appreciated If I have some problems, I will pm you. Thanks in advance