Database Users

Rooting and OTA updates

I am looking into rooting my Nexus S so I can install an ICS ROM. This is my first time rooting so got a question.
How will OTA updates work for me? Will the ICS update just work or will I have to in root to get the official OTA update?
Sry if this has been asked before couldn't find a clear answer.
Sent from my Nexus S using XDA App

Don't do OTAs. Any update released by Google or your manufacturer will be released here, rooted, within hours.
If you take an OTA you will lose root and could even find your phone locked again (as unlikely as that is with the NS, better safe than sorry. Ask the EVO users who took the GB OTA )
Sent from my Nexus S 4G using Tapatalk

Rooting requires flashing custom recovery
OTA requires stock recovery to work properly
So if your phone has custom recovery the OTA will not work.

Alright, thanks alot for the quick responses guys.
Sent from my Nexus S using XDA App

Once the ota is downloaded.....
* Put the zip on sdcard
* Reboot into custom recovery
* Manually flash it
* Directly after that, in the same recovery session, flash latest superuser zip
* Wipe cache
* Reboot

I run stock, so i'll add my two cents into this conversations. A few key points:
OTA's will NOT lock the boot loader
OTA's will work with CWM installed (The OTA will however remove CWM and needs to be manually applied)
OTA's will remove root access (the permissions on the binary get changed)
I have never seen an OTA on XDA that was pre-rooted. i have seen ROM packages that incorporate the OTA that are pre-rooted (installing these usually means a wipe of the device is needed)
if you replace the ROM on the phone, you will not get OTA updated. you must remain mostly stock to obtain them.
Custom kernels or custom google apps on stock roms will cause the OTA update to fail, however you will notified that the update is available.
I hope this answers your questions.

Good points.
What i do in order to maintain the full software (removing system apps, any system changes) is change the permissions of whatever i dont want to "000"
This will allow the verifying of OTA to flash.

snandlal said:
Good points.
What i do in order to maintain the full software (removing system apps, any system changes) is change the permissions of whatever i dont want to "000"
This will allow the verifying of OTA to flash.
Click to expand...
Click to collapse
This does not always work, such as installing the "Black" version of gmail over top the original, the world-wide version of navigation or using market enabler to change the prop.build file. any of these changes will cause the OTA signature to fail.
Though if you are simply removing a system app, then yes, that would work well.
Also to be noted and this just occurred to me, if the OTA is a full ROM version, then the signature won't matter and it will just install. For ICS, this is what i'm expecting.

I'm on the fence about rooting. I know there are advantages like custom ROMs and added features, but I'm somewhat of a newb at this. While the instructions (for the Mac) seem simple enough, I always feel like something inevitably goes wrong or there's some variable I've either overlooked or don't understand that screws things up.
I definitely don't want to brick my phone.
I don't even know what I'm asking in my post, but I guess... what are some advantages of rooting? And if I root, is it fully reversible?
I'm also confused by some of the terminology. What is clockwork recovery? Is that a sort of ROM? I keep seeing that phrase every time I read instructions. Likewise, what's a bootloader? What's fastboot? Also, what's a kernel?
And after I root (as you can see, I am really tempted to), what happens next? How do I choose which ROM works for me? Is it a matter of flashing them and trying each of them out?
I'm afraid of entering the world of root, but I want to. Advice? Does it matter what baseband, or kernel or build number I have?
I'm on Android 2.3.6

Matridom said:
I run stock, so i'll add my two cents into this conversations. A few key points:
OTA's will NOT lock the boot loader
I hope this answers your questions.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1145056
I know it's not likely, particularly with this phone, but it can happen. I maintain that if you're going to go through the process of unlocking your phone and putting a rooted ROM on it that you might as well wait for a modified OTA ROM to get posted by a trusted dev before just installing what the carrier hands out to you.
I guess maybe I should have said "re-lock"?

onthecouchagain said:
I'm on the fence about rooting. I know there are advantages like custom ROMs and added features, but I'm somewhat of a newb at this. While the instructions (for the Mac) seem simple enough, I always feel like something inevitably goes wrong or there's some variable I've either overlooked or don't understand that screws things up.
I definitely don't want to brick my phone.
I don't even know what I'm asking in my post, but I guess... what are some advantages of rooting? And if I root, is it fully reversible?
I'm also confused by some of the terminology. What is clockwork recovery? Is that a sort of ROM? I keep seeing that phrase every time I read instructions. Likewise, what's a bootloader? What's fastboot? Also, what's a kernel?
And after I root (as you can see, I am really tempted to), what happens next? How do I choose which ROM works for me? Is it a matter of flashing them and trying each of them out?
I'm afraid of entering the world of root, but I want to. Advice? Does it matter what baseband, or kernel or build number I have?
I'm on Android 2.3.6
Click to expand...
Click to collapse
OK, let's clear a few things up here.
CWM or ClockWorkMod is a custom recover that can be installed on the phones. This step is needed because the default recovery on the nexus does not allow for updates to be installed that are unsigned. CWM does, so it's a necessary step to installing the SU binary (aka root your phone) or installing custom ROMs
The bootloader is the basic system on your phone that reacts to the power on and hands over operations to Android. The equivalent in the PC world would be a BIOS.
fastboot is a utility that is provided by google that allows you to send commands to the bootloader and direct it's operations. It's needed to unlock the bootloader (so you can replace parts of it.. like recovery with CWM)
Interestingly enough, you can boot your phone to a custom recovery WITHOUT replacing your existing stock recovery by using fastboot.
Rooting your phone is simply installing and providing the proper rights to the SU binary to allow you to have full administrative rights to the phone, the superuser application is almost always bundled with it as it allows for a form of control as to what applications can use root access. Rooting your phone allows you to install some very interesting application, most popular are titanium backup (let's you back up app data and restore them after a reset) and removing advertising (adfree/adaway or it's like) Root can also be used by some applications that allow you to "cheat" at games.
rooting your phone is reversable, though not always the easiest to do. With the stock ROMS, it's fairly easy, you just re-apply the latest OTA and it will kill Root access on your device.
When it comes to custom ROMs the vast majority come pre-rooted to save you the hassel of doing it yourself.
On other phones where the bootloader remains locked, you have to use an exploit to gain root access, this then allows you to modify the OS and install custom roms and CWM while keeping the bootloader locked. Since the Nexus line can be unlocked, it's not needed.
Please note, root access is NOT required to install a custom ROM.
---------- Post added at 02:02 PM ---------- Previous post was at 01:56 PM ----------
MaxCarnage said:
http://forum.xda-developers.com/showthread.php?t=1145056
I know it's not likely, particularly with this phone, but it can happen. I maintain that if you're going to go through the process of unlocking your phone and putting a rooted ROM on it that you might as well wait for a modified OTA ROM to get posted by a trusted dev before just installing what the carrier hands out to you.
I guess maybe I should have said "re-lock"?
Click to expand...
Click to collapse
That's a link to a non-nexus phone. The question here is in regards to the nexus device and i believe my statement stands 100% true. Since it's a self proclaimed "newby" asking questions, i don't want to confuse the post with un-needed and non-relevant information.

Matridom, wow thanks. That clarifies a few things.
So, you say root access isn't required to flash custom ROMs? Let's say for example, I want to flash an ICS ROM, or even a ROM that allows me to have Backlight Notifications?
I don't need root? If I don't need root, how do I flash those ROMs?

Matridom said:
That's a link to a non-nexus phone. The question here is in regards to the nexus device and i believe my statement stands 100% true. Since it's a self proclaimed "newby" asking questions, i don't want to confuse the post with un-needed and non-relevant information.
Click to expand...
Click to collapse
I'm not sure why it's so invalid to advise that he wait for someone to post an OTA that has been vetted for those of us who have unlocked our phones; I respect your opinion (even if you clearly don't mine), but your statement that I am providing "un-needed" and "non-relevant" information is a bit harsh.
The fact of the matter is that Sprint has had at least one OTA released (for the EVO 4G) that re-locked bootloaders and caused a lot of consternation for people who took the OTA on their unlocked phones and found themselves waiting months for a new exploit to be found. Those who waited had a rooted version of the OTA available on the forums very quickly, so if those who took the OTA had just waited they wouldn't have been stuck.
tl;dr: If you went to the trouble of unlocking your phone in the first place I don't see why you would rush to take an un-vetted update OTA.

MaxCarnage said:
I'm not sure why it's so invalid to advise that he wait for someone to post an OTA that has been vetted for those of us who have unlocked our phones; I respect your opinion (even if you clearly don't mine), but your statement that I am providing "un-needed" and "non-relevant" information is a bit harsh.
The fact of the matter is that Sprint has had at least one OTA released (for the EVO 4G) that re-locked bootloaders and caused a lot of consternation for people who took the OTA on their unlocked phones and found themselves waiting months for a new exploit to be found. Those who waited had a rooted version of the OTA available on the forums very quickly, so if those who took the OTA had just waited they wouldn't have been stuck.
tl;dr: If you went to the trouble of unlocking your phone in the first place I don't see why you would rush to take an un-vetted update OTA.
Click to expand...
Click to collapse
The key here is that SPRINT released an OTA for a SPRINT branded device. This has zero relevance to updates provided by Google for Nexus devices.

MaxCarnage said:
I'm not sure why it's so invalid to advise that he wait for someone to post an OTA that has been vetted for those of us who have unlocked our phones; I respect your opinion (even if you clearly don't mine), but your statement that I am providing "un-needed" and "non-relevant" information is a bit harsh.
The fact of the matter is that Sprint has had at least OTA released (for the EVO 4G) that re-locked bootloaders and caused a lot of consternation for people who took the OTA on their unlocked phones and found themselves waiting months for a new exploit to be found. Those who waited had a rooted version of the OTA available on the forums very quickly, so if those who took the OTA had just waited they wouldn't have been stuck.
tl;dr: If you went to the trouble of unlocking your phone in the first place I don't see why you would rush to take an un-vetted update OTA.
Click to expand...
Click to collapse
The issue at heart here is that fact that the OTA for the nexus line of phones comes straight from google and are not "tweaked" in any way by the carriers. (exception nexus 4g has additional applications required for CDMA support)
One of the selling features of the nexus phones is the fact that unlocking the bootloader is officially supported.
In regards to other phones getting their bootloader locked, I've experienced first hand the pains of that, having a galaxy S and the 2.3 installing a new bootloader and really screwing things up for me. In those cases, i agree with you whole heartily and to wait for pre-cracked roms that can be installed.
My question to you would be to please show an example of a nexus S getting it's booloader locked due to an OTA update as that is the phone we are discussing.
---------- Post added at 02:49 PM ---------- Previous post was at 02:47 PM ----------
onthecouchagain said:
Matridom, wow thanks. That clarifies a few things.
So, you say root access isn't required to flash custom ROMs? Let's say for example, I want to flash an ICS ROM, or even a ROM that allows me to have Backlight Notifications?
I don't need root? If I don't need root, how do I flash those ROMs?
Click to expand...
Click to collapse
All you would need to do is to unlock the bootloader, install CWM, then apply the .zip associated with the ROM you wish to install. I would however carefully read the installation instructions for the rom as in some cases, it might be a multi-step process (such as going from a 2.2 rom to a 2.3).
Many ROMS also do not come with the google apps and secondary zip file needs to be applied to get those running (cyanogenMod does this)
I wanted to add, that the process of unlocking your bootloader will erase EVERYTHING on the phone, including the SDcard partition. So make sure you back up anything of importance.

Matridom said:
My question to you would be to please show an example of a nexus S getting it's booloader locked due to an OTA update as that is the phone we are discussing.
Click to expand...
Click to collapse
I can't provide an example because, as I have already stated, this was a precautionary suggestion only.
I'm not going to get into a debate with you over this; I've made my point and you've made yours. Thanks.

Matridom said:
This does not always work, such as installing the "Black" version of gmail over top the original, the world-wide version of navigation or using market enabler to change the prop.build file. any of these changes will cause the OTA signature to fail.
Though if you are simply removing a system app, then yes, that would work well.
Also to be noted and this just occurred to me, if the OTA is a full ROM version, then the signature won't matter and it will just install. For ICS, this is what i'm expecting.
Click to expand...
Click to collapse
Good point again but the trick is to put your apps in /system/framework
Along with framework-res.apk.
This will add a dex file to /data/dalvik-cache, which is needed for saving upon reboot

Does flashing another radio that's different from your original radio impact the ability to apply an OTA?

suksit said:
Rooting requires flashing custom recovery
OTA requires stock recovery to work properly
So if your phone has custom recovery the OTA will not work.
Click to expand...
Click to collapse
Rooting doesn't require flashing custom recovery.

iboj007 said:
Does flashing another radio that's different from your original radio impact the ability to apply an OTA?
Click to expand...
Click to collapse
No. It doesnt

OTA Custom Recovery Misconception

Is it a misconception that an OTA update received on your phone will not install if you have a custom recovery? I just read an article on how an update will fail if you are running a custom recovery. However, when I updated from 4.2.1 to 4.2.2.. All I did was accept the OTA update notification I got on my phone and it installed fine through the TWRP recovery I had flashed on my Nexus.

It won't install automatically, as you found out. It has been said many times over that you are easily able to install the downloaded OTA yourself in your custom recovery.

peedub said:
It won't install automatically, as you found out. It has been said many times over that you are easily able to install the downloaded OTA yourself in your custom recovery.
Click to expand...
Click to collapse
Sorry maybe I didnt word my post correctly but what I am trying to say that it does install automatically. I got the update notification on my phone and it installed fine.

Rizy7 said:
Sorry maybe I didnt word my post correctly but what I am trying to say that it does install automatically. I got the update notification on my phone and it installed fine.
Click to expand...
Click to collapse
Yes its not new info as this has been discussed before in a number of threads back when the last OTA first came out.

Had a similar question, and in the spirit of not starting a new thread...
was this OTA just lucky in that regard?
ie. I want to root (for ads.. no other compelling reason for me.. I'm happy otherwise).. and would like to do so in a way that makes me as forward compatible for future OTA updates (ie. don't want to have to wipe data).
since I'm not looking for lots of typical custom recovery features, I'm wondering if I should even bother with a custom recovery.. and/or if any are likely to allow me to accept OTAs directly OTA.
thanks!

zim2dive said:
Had a similar question, and in the spirit of not starting a new thread...
was this OTA just lucky in that regard?
ie. I want to root (for ads.. no other compelling reason for me.. I'm happy otherwise).. and would like to do so in a way that makes me as forward compatible for future OTA updates (ie. don't want to have to wipe data).
since I'm not looking for lots of typical custom recovery features, I'm wondering if I should even bother with a custom recovery.. and/or if any are likely to allow me to accept OTAs directly OTA.
thanks!
Click to expand...
Click to collapse
Rooting your phone does not keep you from being able to update it. If all else fails you can always download the OTA and update it through your custom recovery. Which is what a lot of people did instead of waiting for Google to push it to their phone, myself included. Also you don't have to have a custom recovery installed if you don't want to after you root the phone. You could use one of the toolkit's to root it and it will install a temporary custom recovery used just for rooting then remove it when its done. Or just flash the stock recovery image after you root if you do it another way. If you go through the process of rooting I would recommend unlocking the bootloader too while you are at it but be warned this will erase all your memory so backup first.

[Q] regarding: Loki + TWRP + Motochopper CASUAL

Hey folks.
I attempted to ask this in the most relevant thread, but as a new user I can not.
My question pertains to the CASUAL root tool for the S4.
Developed by AdamOutler.
Described in the thread "[ROOT[RECOVERY] Loki + TWRP + Motochopper CASUAL-R527b release"
The tool looks pretty amazing.
But I do have some questions.
Please forgive me in advance I am an UBER NEWBIE.
Many of the terms thrown around here are completely foreign to me.
(Yes, I've searched for that knowledge - but perhaps you are underestimating my noobness. )
(Yes, I have read the "[HOW-TO] The All-In-One Root/Backup/Flash Guide - [I337 & I337M]" thread as well... it helped but... yeah still a noob.)
FYI: The only reason I want to root my S4 (AT&T) is so I can remove the crappy bloatware, and also configure the anti-theft/find-phone features of the avast! app.
Ok so on to the questions...
1) Once this is done what's to stop some update from my carrier un-doing it all?
2) If that were to happen how much pain would I be in for?
3) If the only way to protect one's self from this is to somehow disable OS/firmware updates... is the only way to get future OS updates through a ROM?
4) This TWRP thing seems to be a backup/recovery tool?
I gather that it also enable ROMs flashing, etc?
I've read others like "Titanium Backup" because it can freeze/remove the bloatware.
Are they both kinda the same thing?
Will the two conflict?
5) This "Nandroid" is another backup tool?
Am I correct in my understanding that the TWRP leverages nandroid - or are they comepeting solutions.
6) Is Nandroid a system function or some other tool that needs installed?
Thanks a bunch folks!
~Doug

DougYITBOS said:
Hey folks.
I attempted to ask this in the most relevant thread, but as a new user I can not.
My question pertains to the CASUAL root tool for the S4.
Developed by AdamOutler.
Described in the thread "[ROOT[RECOVERY] Loki + TWRP + Motochopper CASUAL-R527b release"
The tool looks pretty amazing.
But I do have some questions.
Please forgive me in advance I am an UBER NEWBIE.
Many of the terms thrown around here are completely foreign to me.
(Yes, I've searched for that knowledge - but perhaps you are underestimating my noobness. )
(Yes, I have read the "[HOW-TO] The All-In-One Root/Backup/Flash Guide - [I337 & I337M]" thread as well... it helped but... yeah still a noob.)
FYI: The only reason I want to root my S4 (AT&T) is so I can remove the crappy bloatware, and also configure the anti-theft/find-phone features of the avast! app.
Ok so on to the questions...
1) Once this is done what's to stop some update from my carrier un-doing it all?
2) If that were to happen how much pain would I be in for?
3) If the only way to protect one's self from this is to somehow disable OS/firmware updates... is the only way to get future OS updates through a ROM?
4) This TWRP thing seems to be a backup/recovery tool?
I gather that it also enable ROMs flashing, etc?
I've read others like "Titanium Backup" because it can freeze/remove the bloatware.
Are they both kinda the same thing?
Will the two conflict?
5) This "Nandroid" is another backup tool?
Am I correct in my understanding that the TWRP leverages nandroid - or are they comepeting solutions.
6) Is Nandroid a system function or some other tool that needs installed?
Thanks a bunch folks!
~Doug
Click to expand...
Click to collapse
1) Once this is done what's to stop some update from my carrier un-doing it all?
If you root you will not be able to get updates any longer.
2) If that were to happen how much pain would I be in for?
Its not going to happen because you are rooted.
3) If the only way to protect one's self from this is to somehow disable OS/firmware updates... is the only way to get future OS updates through a ROM?
The only way you will get updates is ODIN back to stock. Again, no worries.
4) This TWRP thing seems to be a backup/recovery tool?
I gather that it also enable ROMs flashing, etc?
I've read others like "Titanium Backup" because it can freeze/remove the bloatware.
Are they both kinda the same thing?
Will the two conflict?
TWRP - is a recovery, so you can perform nandroid backups, and to flash roms, and to restore backups. Nothing more, nothing less.
Titanium Backup is a app you use within the rom, to backup and restore apps with, you can read more on this going to the market, it will explain this app's features and what it does.
They are not the same, 2 different programs, that do 2 different things.
Question 5 & 6 answered in #4 answer.
Hope this helps, kinda down and dirty, try and do some reading on all of the above.
Appreciate the thanks.
Thank you and good luck.

Thanks a bunch TheAxman
You said...
TheAxman said:
1) Once this is done what's to stop some update from my carrier un-doing it all?
If you root you will not be able to get updates any longer.
3) If the only way to protect one's self from this is to somehow disable OS/firmware updates... is the only way to get future OS updates through a ROM?
The only way you will get updates is ODIN back to stock. Again, no worries.
Click to expand...
Click to collapse
So does the Root tool (in this case the CASUL script by Adam) do something to shut down carrier updates or I need to do something extra?
Also if one were to ODIN back to stock... and get an update... and then re-root...
I assume you could get an old backup from an external storage area and try to get all your "stuff" back?

DougYITBOS said:
Thanks a bunch TheAxman
You said...
So does the Root tool (in this case the CASUL script by Adam) do something to shut down carrier updates or I need to do something extra?
Also if one were to ODIN back to stock... and get an update... and then re-root...
I assume you could get an old backup from an external storage area and try to get all your "stuff" back?
Click to expand...
Click to collapse
Once you root,, it changes the rom status to custom, so the update see's that and does NOTHING. if you odin back to stock, un-root, you can force updates, but be careful with updates, carriers are patching things so we can not do what we do, and that is to run custom roms on phones THAT WE OWN!
And btw, if this person xBeerdroiDx gives me a thanks, he is saying I did ok... If you seem to have anymore questions, his guide is one of the best....
[HOW-TO] The All-In-One Root/Backup/Flash Guide - [I337 & I337M]
http://forum.xda-developers.com/show....php?t=2314494
Thanks to xBeerdroiDx - For this great Startup Guide

Thanks again!

DougYITBOS said:
Thanks again!
Click to expand...
Click to collapse
Your quite welcome, if you have any other questions, feel free to ask them in the thread I gave you or mine.
http://forum.xda-developers.com/showthread.php?t=2295557

Sorry to hijack the thread, but I figured Axman may know.
In the past on my S2, I would flash a lot of roms. maybe after every 5 or 10 I would odin back to stock, boot it up, re-root, re-twrp, then flash another rom. just to get a very clean slate in a sense.
If I were to do this with the S4, you dont think the ATT update would get pushed in the 30 mins to an hour that the phone is in its stock state, do you? I dont want to get mf3'd.

orlandoxpolice said:
Sorry to hijack the thread, but I figured Axman may know.
In the past on my S2, I would flash a lot of roms. maybe after every 5 or 10 I would odin back to stock, boot it up, re-root, re-twrp, then flash another rom. just to get a very clean slate in a sense.
If I were to do this with the S4, you dont think the ATT update would get pushed in the 30 mins to an hour that the phone is in its stock state, do you? I dont want to get mf3'd.
Click to expand...
Click to collapse
hehe it could, but highly unlikely, and if you feel that it may happen, do what I do, remove the sim until you get rooted, and then put the sim back in and complete the setup. Your not going to get calls in that time period anyways.
Good luck.
btw..this is cool, name please.
Dog: [Pitbull Sharpei Mix] Rom: Stock

TheAxman said:
hehe it could, but highly unlikely, and if you feel that it may happen, do what I do, remove the sim until you get rooted, and then put the sim back in and complete the setup. Your not going to get calls in that time period anyways.
Good luck.
Click to expand...
Click to collapse
ah good idea. i suppose airplane mode would accomplish the same thing as well

orlandoxpolice said:
Sorry to hijack the thread, but I figured Axman may know.
In the past on my S2, I would flash a lot of roms. maybe after every 5 or 10 I would odin back to stock, boot it up, re-root, re-twrp, then flash another rom. just to get a very clean slate in a sense.
If I were to do this with the S4, you dont think the ATT update would get pushed in the 30 mins to an hour that the phone is in its stock state, do you? I dont want to get mf3'd.
Click to expand...
Click to collapse
I'm just throwing my limited experience out. I have never went back to stock via Odin simply to get a "clean slate." Completing a full wipe including a system format in recovery will be sufficient for a clean OS. I would reserve Odin flashing as a last resort for when problems aren't being remedied by a full wipe and format via recovery.

CamFlawless said:
I'm just throwing my limited experience out. I have never went back to stock via Odin simply to get a "clean slate." Completing a full wipe including a system format in recovery will be sufficient for a clean OS. I would reserve Odin flashing as a last resort for when problems aren't being remedied by a full wipe and format via recovery.
Click to expand...
Click to collapse
Thank you sir, appreciate the help, and yes, good idea.

TheAxman said:
Thank you sir, appreciate the help, and yes, good idea.
Click to expand...
Click to collapse
might have been a placebo effect for me, lol.

TheAxman said:
1) Once this is done what's to stop some update from my carrier un-doing it all?
If you root you will not be able to get updates any longer.
2) If that were to happen how much pain would I be in for?
Its not going to happen because you are rooted.
3) If the only way to protect one's self from this is to somehow disable OS/firmware updates... is the only way to get future OS updates through a ROM?
The only way you will get updates is ODIN back to stock. Again, no worries.
4) This TWRP thing seems to be a backup/recovery tool?
I gather that it also enable ROMs flashing, etc?
I've read others like "Titanium Backup" because it can freeze/remove the bloatware.
Are they both kinda the same thing?
Will the two conflict?
TWRP - is a recovery, so you can perform nandroid backups, and to flash roms, and to restore backups. Nothing more, nothing less.
Titanium Backup is a app you use within the rom, to backup and restore apps with, you can read more on this going to the market, it will explain this app's features and what it does.
They are not the same, 2 different programs, that do 2 different things.
Question 5 & 6 answered in #4 answer.
Hope this helps, kinda down and dirty, try and do some reading on all of the above.
Appreciate the thanks.
Thank you and good luck.
Click to expand...
Click to collapse
Correct me if I'm wrong, but its my understanding if you're rooted and still stock the MDL will still update to MF3 unless you either completely flash a custom ROM or rename the OTA files that At&t have on our devices.
where you end up, depends on where you start.
AT&T SGH-I337 32G

lilbigdude1 said:
Correct me if I'm wrong, but its my understanding if you're rooted and still stock the MDL will still update to MF3 unless you either completely flash a custom ROM or rename the OTA files that At&t have on our devices.
where you end up, depends on where you start.
AT&T SGH-I337 32G
Click to expand...
Click to collapse
somewhat, but as soon as you root, your phone status is custom correct? therefor how can it update? Yes, it is better to do a custom rom, but you can still stay on MDL and never get updates, freezing the samsung update will work, but I gave the easiest way in his situation.

TheAxman said:
Once you root,, it changes the rom status to custom, so the update see's that and does NOTHING. if you odin back to stock, un-root, you can force updates, but be careful with updates, carriers are patching things so we can not do what we do, and that is to run custom roms on phones THAT WE OWN!
Click to expand...
Click to collapse
Hi...I'm another noob with a question about this. I also just used CASUAL to root my phone yesterday. I am definitely rooted but my Device Status actually still shows Official. Following the info in another thread, I used ES File Explorer's Root Manager to rename the wssyncmldm.apk.
Info from: http://forum.xda-developers.com/showthread.php?t=2268946
The thread was actually written for a previous update, but renaming the apk should still be relevant.
Maybe this was overkill, but...

texasniteowl said:
Hi...I'm another noob with a question about this. I also just used CASUAL to root my phone yesterday. I am definitely rooted but my Device Status actually still shows Official. Following the info in another thread, I used ES File Explorer's Root Manager to rename the wssyncmldm.apk.
Info from: http://forum.xda-developers.com/showthread.php?t=2268946
The thread was actually written for a previous update, but renaming the apk should still be relevant.
Maybe this was overkill, but...
Click to expand...
Click to collapse
I was just rooted and it showed custom status after, so no updates, you must check the status. just flashing a kernel will change the status, if you are going to root and install a recovery, some things are to go without saying.
Btw, I have learned, that nothing with information is an overkill, if you haven't notice xda is a bunch of peoples ideas and such, and many do not work for others, it is a hit miss.

TheAxman said:
I was just rooted and it showed custom status after, so no updates, you must check the status. just flashing a kernel will change the status, if you are going to root and install a recovery, some things are to go without saying.
Btw, I have learned, that nothing with information is an overkill, if you haven't notice xda is a bunch of peoples ideas and such, and many do not work for others, it is a hit miss.
Click to expand...
Click to collapse
Yeah...maybe I am referring to the wrong thing, but I was surprised that Settings > More > About Device > Status > Device Status still said "Official" on mine. I know CASUAL succeeded. TWRP is installed, SuperUser is installed. And I was able to use ES File Explorer's Root Manager to change system to R/W and rename the apk. So even though I'm very much an android novice, I'm pretty certain I'm rooted. I don't necessarily plan to flash a rom yet...but since I was still on MDL I wanted to retain the current ability to do so!
Is there some other place that it would show Custom as opposed to Official? That's actually why I went ahead and renamed that file.

texasniteowl said:
Yeah...maybe I am referring to the wrong thing, but I was surprised that Settings > More > About Device > Status > Device Status still said "Official" on mine. I know CASUAL succeeded. TWRP is installed, SuperUser is installed. And I was able to use ES File Explorer's Root Manager to change system to R/W and rename the apk. So even though I'm very much an android novice, I'm pretty certain I'm rooted. I don't necessarily plan to flash a rom yet...but since I was still on MDL I wanted to retain the current ability to do so!
Is there some other place that it would show Custom as opposed to Official? That's actually why I went ahead and renamed that file.
Click to expand...
Click to collapse
I did not mean to confuse anyone. Yes you did the right thing by renaming the the file. if your device says official then this step is needed. mine said custom. umm i stand corrected fellows..another step is needed. thanks for the oversight. i am only human..im not a animal.

TheAxman said:
I did not mean to confuse anyone. Yes you did the right thing by renaming the the file. if your device says official then this step is needed. mine said custom. umm i stand corrected fellows..another step is needed. thanks for the oversight. i am only human..im not a animal.
Click to expand...
Click to collapse
if you are paranoid then there are 3 files you can freeze. i cant remember which ones, but one is att update something something, thats all i can remember.
im no help

I think everyone gets the picture.
Sent from my GT-I9505 using xda premium

A way to find OTA filename for those who already installed any OTA and are rooted

There is a procedure to fool OTA system in order to make it receive the OTA again. So you have a second chance to grab the filename and make a lot of people here happy
Update: Thanks to @Sleeepy2 we know this method works in the nexus 6 :good:
DISCLAIMER: It's an unharmed procedure, but be warned, you will change build.prop so anything (bad) should happen if you do it incorrectly, most probably a bootloop. If you have doubts, don't do it.
Needs to be rooted.
So if there is a brave enought one, the procedure is just to change two values of the /system/build.prop file to make it looks a previous android version for the OTA system.
For instance, If you have received to OTA to LMY47M your build.prop file will have these values:
ro.build.date.utc=1425686543
and
ro.build.fingerprint=google/shamu/shamu:5.1/LMY47M/1774234:user/release-keys
If you change these lines by the equivalent lines from another version of android, the OTA system will check the OTA availability with the other android version. So, If before receiving the OTA your android version was 5.0.1 LRX22C you can change both lines with:
ro.build.date.utc=1416527965
and
ro.build.fingerprint=google/shamu/shamu:5.0.1/LRX22C/1602158:user/release-keys
That are the LRX22C version lines.
Save build.prop file and reboot your nexus 6.
Once rebooted check for OTA updates (It will be checked as LMY47D) and download it, if it's not downloading yet (don't apply the OTA, just download it).
While it's downloading, or even after it's download, open a terminal emulator (for instance this one: https://play.google.com/store/apps/details?id=jackpal.androidterm) and execute these two commands (will ask for superuser permission):
su
logcat | grep zip
And wrote down the OTA link for us
When you finish just revert the build.prop changes done and delete the file /cache/update.zip (it's the OTA downloaded, and you don't need it), then reboot your system to leave it in it's normal situation.
Thank you very much in advance.
And, If you are kindly enough, you may check for the rest of OTAs from other android versions (the LMY47E OTA to LMY47M should be very useful too). Here are all known versions build.prop lines to play with:
Code:
LMY47M
ro.build.date.utc=1425686543
ro.build.fingerprint=google/shamu/shamu:5.1/LMY47M/1774234:user/release-keys
LMY47I:
ro.build.date.utc=1425442825
ro.build.fingerprint=google/shamu/shamu:5.1/LMY47I/1767468:user/release-keys
LMY47E:
ro.build.date.utc=1424577649
ro.build.fingerprint=google/shamu/shamu:5.1/LMY47E/1748839:user/release-keys
LMY47D:
ro.build.date.utc=1424322888
ro.build.fingerprint=google/shamu/shamu:5.1/LMY47D/1743759:user/release-keys
LRX22C:
ro.build.date.utc=1416527965
ro.build.fingerprint=google/shamu/shamu:5.0.1/LRX22C/1602158:user/release-keys
LRX21O:
ro.build.date.utc=1415319727
ro.build.fingerprint=google/shamu/shamu:5.0/LRX21O/1570415:user/release-keys
LNX07M:
ro.build.date.utc=1414346119
ro.build.fingerprint=google/shamu/shamu:5.0/LNX07M/1543455:user/release-keys
-----
KXH21.6-F1.12:
ro.build.date.utc=1416355004
ro.build.fingerprint=motorola/shamu_factory/shamu:4.4.4/KXH21.6-F1.12/25:userdebug/release-keys
Most of them will give you old and known OTAs, but some will give new OTAs for all of us. And the final test build probably doesn't give any OTA
Thanks and best regards.

I changed by build.prop and rebooted and no update which I checked.

xpack90 said:
I changed by build.prop and rebooted and no update which I checked.
Click to expand...
Click to collapse
But you previously installed the LMY47M/E, no?
If yes, Please, wait several minutes and keep checking, you eventually must receive the OTA again before the rest of people.
Check too if build.prop file was correctly changed (sometimes a number is missing or something).
Thanks and best regards.

No sorry I thought this was for people who wanted the update not those who had it

xpack90 said:
No sorry I thought this was for people who wanted the update not those who had it
Click to expand...
Click to collapse
Don't worry and thanks for trying.

Rogers Canada
http://android.clients.google.com/p...ed-shamu-ota-LMY47D-from-LRX22C-fullradio.zip

Sleeepy2 said:
Rogers Canada
http://android.clients.google.com/p...ed-shamu-ota-LMY47D-from-LRX22C-fullradio.zip
Click to expand...
Click to collapse
First of all, thank you very much. Unfortunately that's one of the known OTAs.
You can see all known OTAs here:
http://forum.xda-developers.com/nexus-6/general/ref-nexus-6-stock-ota-urls-t2906493
But as I said, thank you very much. You demonstrated the method works for Nexus 6 too

oops, yeah it is know. I didn't fully read and thought you just wanted confirmation that it works on the N6.
And yes it does

OK, I got the OTA you're looking for (47M) but am currently unlocked and not rooted. If I oem unlock and perform this, how do we know for sure that it will prompt me again for the OTA?
I'm certainly willing to try when I get home later this evening (if no one has posted it by then), but would hate for my data to get wiped for nothing ...

YankInDaSouth said:
OK, I got the OTA you're looking for but am currently unlocked and not rooted. If I oem unlock and perform this, how do we know for sure that it will prompt me again for the OTA?
I'm certainly willing to try when I get home later this evening (if no one has posted it by then), but would hate to for my data to get wiped for nothing ...
Click to expand...
Click to collapse
Unfortunately I cannot guarantee that you receive the OTA again.
In my opinion it shouldn't work because the GMS/GCS ID is used to check OTAs, and if you perform an "oem unlock" you will lose your data so a new GMS/GCS ID will be assigned to your device, making it a totally different device for google.
If I were you I shouldn't try. It's a pity, but I'm being sincere.
Thanks and best regards.

VivaErBetis said:
Unfortunately I cannot guarantee that you receive the OTA again.
In my opinion it shouldn't work because the GMS/GCS ID is used to check OTAs, and if you perform an "oem unlock" you will lose your data so a new GMS/GCS ID will be assigned to your device, making it a totally different device for google.
If I were you I shouldn't try. It's a pity, but I'm being sincere.
Thanks and best regards.
Click to expand...
Click to collapse
I appreciate you being straight up about it! I will hold off as I'd prefer not to lose my data and not be able to get the community what they want/need.
If only I had know that it would be this long before people started receiving the OTA I definitely would have held off on installing it!! Don't know why I was the "chosen one" LOL

YankInDaSouth said:
I appreciate you being straight up about it! I will hold off as I'd prefer not to lose my data and not be able to get the community what they want/need.
If only I had know that it would be this long before people started receiving the OTA I definitely would have held off on installing it!! Don't know why I was the "chosen one" LOL
Click to expand...
Click to collapse
Don't worry, the OTA will eventually show up, sooner or later. The real problem is our lack of patience

I've added the build.prop info for 5.1 LMY47I build. The OTA seems to be delivered for Australian users.

Android 6.0 Marshmallow

Dumb question, but I'll ask anyway if I root will I not be able to receive OTA updates? Because I know whenever I did that with my Note 4 that if I tried it would give a message saying operating system is modified or something in that nature.

joe1blue said:
Dumb question, but I'll ask anyway if I root will I not be able to receive OTA updates? Because I know whenever I did that with my Note 4 that if I tried it would give a message saying operating system is modified or something in that nature.
Click to expand...
Click to collapse
You will not be able to take the ota. You have two options when marshmallow comes out.
1) Use the return to stock tool and take the ota them reroot
2) Wait for a flash able zip to become available.

TrenchKato said:
2) Wait for a flash able zip to become available.
Click to expand...
Click to collapse
Which will most likely be faster available than waiting for the OTA.

I'm not sure that will be the case for the MXPE. Fastboot shows the OS as "original," leading me to believe that OTA updates may work. Remember that on the Note 4, et al, unlocking the bootloader wasn't supported by the OEM or carrier. Since Moto is supplying the unlock codes, I suspect that OTA updates will not be disabled on the MXPE as long as no other OS changes are made. I could be wrong, but we'll find out when the time comes.

Tanker Bob said:
I'm not sure that will be the case for the MXPE. Fastboot shows the OS as "original," leading me to believe that OTA updates may work. Remember that on the Note 4, et al, unlocking the bootloader wasn't supported by the OEM or carrier. Since Moto is supplying the unlock codes, I suspect that OTA updates will not be disabled on the MXPE as long as no other OS changes are made. I could be wrong, but we'll find out when the time comes.
Click to expand...
Click to collapse
Chances are, if you unlocked your bootloader, you flashed a custom recovery. You can't take an OTA through a custom recovery -- not because it's "blocked," but because the OTA tool is not written to work with that recovery.

Could be. Easy enough to fix if so. Just tell TWRP to allow the OS to overwrite it, the reflash TWRP after the update.

Can't you just flash the stock recovery to take the OTA? Sure, you'll lose root, but you could still take the OTA, then flash your custom recovery again. Is there anything, other than a stock recovery, that prevents OTA updates?
I wish we had a release date. Getting excited for the new features. Should have kept my Nexus 5!

jonathanbailie said:
Can't you just flash the stock recovery to take the OTA? Sure, you'll lose root, but you could still take the OTA, then flash your custom recovery again. Is there anything, other than a stock recovery, that prevents OTA updates?
I wish we had a release date. Getting excited for the new features. Should have kept my Nexus 5!
Click to expand...
Click to collapse
A modified system will prevent the install. You would need to flash the system image as well.
Sent from my XT1575 using Tapatalk

I know some owners rooted their device for different reasons other than roms, but imo better to wait for 6.0 for OTA first. This phone comes with pure Android rom. Not like you need to remove bloat apps. Just need custom roms and kernels which is slow developing. Maybe the devs don't want to waste time with lp and their also waiting for marshmallow. I'm surprised how slow this device is moving under development. Oneplus one didn't have mass sale but their development was quick. Being so similar with nexus 6, hopefully we can get some love with MXP.
Sent from my XT1575 using XDA Free mobile app

I have been holding out on unlocking for this reason. I'm lazy and don't want to set everything up again so I will use Marsh to back everything up first then I will go to town

Tanker Bob said:
I'm not sure that will be the case for the MXPE. Fastboot shows the OS as "original," leading me to believe that OTA updates may work.
Click to expand...
Click to collapse
OTA will not work for rooted MXPE's.
1) Rooting the MXPE requires you to load an alternative recovery (TWRP), which doesn't work with the OTA installation scripts.
2) Rooting the MXPE modified /system files. And OTA updates check /system integrity before it runs the update. Rooted phones will fail that integrity check, and will fail to OTA for that reason.
You could restore your MXPE to stock conditions (un-root, and load stock recovery) to have it accept an OTA. I'm sure that most people will do that, and then re-install TWRP and re-root after that is done. However, I'd recommend you wait a bit for other people to try this first, just in case there are any issues and to verify that root is still available in Android Marshmallow 6.0

Makes sense. Somebody has to be first. I will do a nandroid backup before attempting to update by any means.

Prior comments in this thread:
"You will not be able to take the ota. You have two options when marshmallow comes out.
1) Use the return to stock tool..."
and
"You could restore your MXPE to stock conditions (un-root, and load stock recovery) to have it accept an OTA..."
I just wanted to clarify that the Return to Stock tool does not currently remove TWRP...
Factory image will appear here once available: https://motorola-global-portal.custhelp.com/app/standalone/bootloader/recovery-images
(Must log in with Motorola registered ID or gmail address)
Keep in mind you will see a Moto X (2nd Gen) Pure Edition already there...that is not ours.

hijax2001 said:
Prior comments in this thread:
"You will not be able to take the ota. You have two options when marshmallow comes out.
1) Use the return to stock tool..."
and
"You could restore your MXPE to stock conditions (un-root, and load stock recovery) to have it accept an OTA..."
I just wanted to clarify that the Return to Stock tool does not currently remove TWRP...
Factory image will appear here once available: https://motorola-global-portal.custhelp.com/app/standalone/bootloader/recovery-images
(Must log in with Motorola registered ID or gmail address)
Keep in mind you will see a Moto X (2nd Gen) Pure Edition already there...that is not ours.
Click to expand...
Click to collapse
More clarification: Restore-To-Stock-Tool does replace TWRP. Have a gander inside the zip. I spy recovery.img within. What do you see?

PiousInquisitor said:
More clarification: Restore-To-Stock-Tool does replace TWRP. Have a gander inside the zip. I spy recovery.img within. What do you see?
Click to expand...
Click to collapse
Yup, you're correct ... I just used the tool earlier today and I do indeed have stock recovery.
Sent from my XT1575 using Tapatalk

Sharing my experience... good it's supposed to. Didn't for me, for some reason, until 2nd power cycle. It is stock recovery now though. Sorry for the confusion.