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

[Q] Unlock bootloader, still get updates?

Does having my bootloader unlocked affect getting updates? I have no interest in installing custom roms(for now), and mainly just want root to block ads, install seeder to fix this damn lag, and possibly connect a ps3 controller to play games. Figured I'd just unlock and root. I didn't plan on installing cwm so I could still get updates straight from google. I know an update would just overwrite root, but not sure if the bootloader would affect it. My galaxy nexus I always installed custom roms so I don't know how the bootloader affected OTA's. thanks guys.

In principle it should not affect updates.
Have a look at a prior OTA update's installer script
./META-INF/com/Google/android/updater-script
The OTAs perform binary patching on individual files, one by one. (That is why OTAs can be so small.) Before they perform the patching, a checksum is performed on every file on the tab/phone targeted for patching. If even one of those checksums fail, the entire install is aborted.
In addition the version of the recovery is sometimes checked, too - so merely having a custom recovery can trip up an OTA if that type of assert() check is performed.
To put that in general terms, you could say that an OTA update will almost always succeed if you merely add things to a ROM and leave the stock recovery in place.
If you want to flash stuff without altering the stock recovery just use a soft boot of a custom recovery, e.g. "fastboot boot custom-recovery-image-file.img"
If an OTA fails, don't get scared - you can simply unpack it, modify the updater-script file to remove the failing assert(), re-zip it and flash it. This would need to be done with a custom recovery, though as the modified OTA would no longer be correctly signed.
HTH

Yes but don't remove any of the Google apps that come preinstalled, don't edit the build prop, and that might be it.
Sent from my Nexus 7 using Tapatalk 2

BrianDigital said:
Yes but don't remove any of the Google apps that come preinstalled, don't edit the build prop, and that might be it.
Click to expand...
Click to collapse
yep.
The most recent OTA had the boot image file as one of its patching targets, so it was also subject to checksum verification during the initial assert() sequence of "updater-script".
I guess that means that if you hook anything into the boot sequence that needs to be in the ramdisk, that will trip up the OTA, as it is pretty typical for OTA updates to diddle the kernel or ramdisk. I guess that if you want to stay on a near-factory base distro including new ota updates, that puts the onus on you to either
(a) check the installers of the stuff you flash to make sure the boot image is not being re-packed -or-
(b) maintain a chain of pure stock backup sequences: then you can then restore them, run the OTA patch kit on them, make a new nandroid backup, and re-run your custom flashes. Probably use TiB to restore your apps on top of that, too. Almost like an OS re-install sequence, frankly.
cheers

thanks guys! Does an update from google relock the bootloader? I'm guessing not since its a nexus and they're okay with us unlocking it but just wondering. Just trying to decide if its worth it. I feel myself using my nexus 7 less cause of the latest update. It's smooth once its running but turning the screen on after its been sitting, it take some time to get together.

tu3218 said:
thanks guys! Does an update from google relock the bootloader? I'm guessing not since its a nexus and they're okay with us unlocking it but just wondering. Just trying to decide if its worth it. I feel myself using my nexus 7 less cause of the latest update. It's smooth once its running but turning the screen on after its been sitting, it take some time to get together.
Click to expand...
Click to collapse
Whoops (old timers disease) I said "bootloader" in that post above where I should have said "boot partition" or "boot image". (Now corrected.)
Updates typically don't touch the bootloaders. Interesting question though - if you replace a bootloader via fastboot, does it change the lock status? To that Q I don't know the answer from direct experience.
Maybe I'll give it a try. Ugh that's gonna be a lot of backup/restore ops.
In the meantime, have you seen a page with links to (older) *full* ROM install bundles that Google no longer has on their site? I only got a N7 in early Jan '13, so I don't have any of those older full-ROM+bootloader fastboot-based install bundles.

bftb0 said:
Whoops (old timers disease) I said "bootloader" in that post above where I should have said "boot partition" or "boot image". (Now corrected.)
Updates typically don't touch the bootloaders. Interesting question though - if you replace a bootloader via fastboot, does it change the lock status? To that Q I don't know the answer from direct experience.
Maybe I'll give it a try. Ugh that's gonna be a lot of backup/restore ops.
In the meantime, have you seen a page with links to (older) *full* ROM install bundles that Google no longer has on their site? I only got a N7 in early Jan '13, so I don't have any of those older full-ROM+bootloader fastboot-based install bundles.
Click to expand...
Click to collapse
Nah I haven't seen that. To be honest I've been so busy with flashing roms on my sgs3. I finally have settled down on a rom for my phone so I figured I'd give my nexus 7 a go. But I'd rather not be performing the whole backing up/flashing/modding on both. Its so much lol Plus my tablet I need to be dependable when I need it. That's why I hadn't planned on running roms, just basic root for blocking ads, etc. Before the last update this thing was so fast and enjoyable to use. It still is but its not to where it use to be. I was going to go back but I don't like knowing I'm not on the latest.

and mainly just want root to block ads, install seeder to fix this damn lag, and possibly connect a ps3 controller to play games.
Click to expand...
Click to collapse
Seeder doesn't fix lag. Doesn't work. If your n7 is lagging then there is another cause.
Sent from my Nexus 7 using Tapatalk HD

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.

Can I update with Dec 2016 security patch if my phone is rooted?

Or do I need FlashFire?
I believe that this is the same update as the one in this post
https://forum.xda-developers.com/moto-x-style/general/maintenance-release-dec-2016-security-t3557903

You need full unroot, stock kernel, stock recovery and no system partition modification

lukas77 said:
You need full unroot, stock kernel, stock recovery and no system partition modification
Click to expand...
Click to collapse
could you tell me how I can do this? Is there a general guide?

Wow... how many times are we going to answer this question every single time an update comes out?!?!
A phone must be 100% stock to take an OTA... stock recovery, stock system partition, stock boot partition... or the update will fail.
You need to either restore your pre-root backup (you did one with TWRP, right?) or flash a factory image that is the same version or newer than you have installed. Period, those are the proper answers to how to go back to stock so you can get an OTA.

acejavelin said:
Wow... how many times are we going to answer this question every single time an update comes out?!?!
A phone must be 100% stock to take an OTA... stock recovery, stock system partition, stock boot partition... or the update will fail.
You need to either restore your pre-root backup (you did one with TWRP, right?) or flash a factory image that is the same version or newer than you have installed. Period, those are the proper answers to how to go back to stock so you can get an OTA.
Click to expand...
Click to collapse
I apologize, this was my first time rooting my phone so I don't know a lot. I was able to root my phone, thanks to your thread on rooting.
I plan on using this thread by you to go back to stock.
https://forum.xda-developers.com/mo...de-return-to-stock-relock-bootloader-t3489110

ThanuTK said:
I apologize, this was my first time rooting my phone so I don't know a lot. I was able to root my phone, thanks to your thread on rooting.
I plan on using this thread by you to go back to stock.
https://forum.xda-developers.com/mo...de-return-to-stock-relock-bootloader-t3489110
Click to expand...
Click to collapse
I hope it helps... Just remember to search around the forums or Google a bit before asking a question. I apologise if I sounded a little snappy, I had just answered some very dumb PM's that frustrated me and then this was the first open thread I saw, sorry if I was a bit abrupt.

This question has been answered a whole lot so it gets a little frustrating sometimes to see a new thread pop up for this issue. That being said and you being new to rooting, I can't stress this enough: please search and read through the threads (and know the XDA rules of course). This device has been out for a while and by now, a large majority of the questions, issues, and whatever else you may have is addressed in these forums. If you do run across anything that there is no answer for, by all means ask away.

Guys there is any chance of volte update because jio expanding their services to next one year
Can it is possible that after nought update it is possible

Suri149 said:
Guys there is any chance of volte update because jio expanding their services to next one year
Can it is possible that after nought update it is possible
Click to expand...
Click to collapse
Possible? Yes, but it isn't likely and I certainly don't expect it to happen. Lenovo has shown no interest in updating the Pure/Style to support Jio, or even fixing the current VoLTE issues on supported carriers for that matter.

Hey could you also tell me how important the android security updates are? are they critical ? without it would my phone be vulnerable?

ThanuTK said:
Hey could you also tell me how important the android security updates are? are they critical ? without it would my phone be vulnerable?
Click to expand...
Click to collapse
Well on this I have a pretty strong opinion, and it isn't always well liked... I work in the IT industry with networks, so security is kind of a big deal to me... but Android security updates are essentially worthless, and are only a marketing ploy to make the company look better.
For example, lets look at some major vulnerabilities that have supposedly affected MILLIONS of Android devices... Dirty Cow is a good one, I am in a group here on XDA that is trying to use this vulnerability for something, anything really, but mainly for rooting difficult devices, and in a modern device it is almost impossible because of all the other parts of Android that help keep it secure like DM-verity and SELinux, end result is no usable exploit in almost all cases, although we have some results in cases where we are in complete control of the device with hands on adb access, but even then it is very rare and device specific, not something that you could just download a random malware app and have it affect you, I would need the device in hand. Then there are the terrible ones like Quadrooter, Stagefright, and Towelroot that affected millions, no tens of millions of devices, but have you ever heard of anyone being actually effected by a real exploit of that vulnerability? Nope, me neither, because for the most part these have only been exploited in a lab and not in real life... Because in a modern (I am talking Marshmallow or maybe even Lollipop) there are other things that protect the device, application sandboxing, DM-verity, SE Linux, and IntentFirewall, are all things that would likely protect the device even IF (and that's a big IF) one of these vulnerabilities did happen to be exploited on a device.
So are security updates important... no, not from a technical perspective in real life for the average user, but I certainly wouldn't reject them if they are easy to apply. I accept and apply every single one, even though I know the chances of something happening if I don't are probably less than that of me winning the Powerball Lottery Jackpot twice in two consecutive weeks, or about the same as being stuck by lightning while being bitten by a shark.
Now, none of what I am saying applies to other updates which are often bundled with security updates, or upgrades.

My thoughts exactly on the security updates. The only "evidence" I have heard about has been a couple of individuals who do not appear to understand why an app from some unknown source or dodgy websites along with crazy permission requirements might infect their phone. I acknowledge this as a human exploit though and not on the part of Android.

If I make current twrp backup, wipe, restore original Stock unrooted twrp backup, flash Stock recovery, take ota, reflash twrp and restore only data from the backup in first step would that essentially preserve user apps/data? Otherwise I will just freeze Moto update apk and wait for 7.0 to full wipe.
Update: Nm, I guess at that point without restoring system to preserve settings I may as well just use Titanium Backup :silly:

I'm rooted and using Xposed, but got the Dec update using a completely stock TWRP backup of system and boot posted here. Afterwards I simply had to reroot and reinstall my Xposed framework in TWRP, but all my modules which were still installed worked and maintained their settings. Couple of other minor cosmetic things I had to redo, but for me this worked very well without having to fully return to stock and reinstall everything from scratch. YMMV, and also do your own TWRP backup first just in case.

roaming4gnome said:
If I make current twrp backup, wipe, restore original Stock unrooted twrp backup, flash Stock recovery, take ota, reflash twrp and restore only data from the backup in first step would that essentially preserve user apps/data? Otherwise I will just freeze Moto update apk and wait for 7.0 to full wipe.
Update: Nm, I guess at that point without restoring system to preserve settings I may as well just use Titanium Backup :silly:
Click to expand...
Click to collapse
Dahenjo said:
I'm rooted and using Xposed, but got the Dec update using a completely stock TWRP backup of system and boot posted here. Afterwards I simply had to reroot and reinstall my Xposed framework in TWRP, but all my modules which were still installed worked and maintained their settings. Couple of other minor cosmetic things I had to redo, but for me this worked very well without having to fully return to stock and reinstall everything from scratch. YMMV, and also do your own TWRP backup first just in case.
Click to expand...
Click to collapse
This is actually a valid way of doing it, but with so many variables to the state of your device prior to doing this the possible outcomes vary a lot.
But @Dahenjo has pretty much the proper procedure... if I was going to try it I'd do it that way... backup, restore stock, take OTA, reroot, reflash Xposed, restore user data... 99% of everything should be intact.

acejavelin said:
Well on this I have a pretty strong opinion, and it isn't always well liked... I work in the IT industry with networks, so security is kind of a big deal to me... but Android security updates are essentially worthless, and are only a marketing ploy to make the company look better.
For example, lets look at some major vulnerabilities that have supposedly affected MILLIONS of Android devices... Dirty Cow is a good one, I am in a group here on XDA that is trying to use this vulnerability for something, anything really, but mainly for rooting difficult devices, and in a modern device it is almost impossible because of all the other parts of Android that help keep it secure like DM-verity and SELinux, end result is no usable exploit in almost all cases, although we have some results in cases where we are in complete control of the device with hands on adb access, but even then it is very rare and device specific, not something that you could just download a random malware app and have it affect you, I would need the device in hand. Then there are the terrible ones like Quadrooter, Stagefright, and Towelroot that affected millions, no tens of millions of devices, but have you ever heard of anyone being actually effected by a real exploit of that vulnerability? Nope, me neither, because for the most part these have only been exploited in a lab and not in real life... Because in a modern (I am talking Marshmallow or maybe even Lollipop) there are other things that protect the device, application sandboxing, DM-verity, SE Linux, and IntentFirewall, are all things that would likely protect the device even IF (and that's a big IF) one of these vulnerabilities did happen to be exploited on a device.
So are security updates important... no, not from a technical perspective in real life for the average user, but I certainly wouldn't reject them if they are easy to apply. I accept and apply every single one, even though I know the chances of something happening if I don't are probably less than that of me winning the Powerball Lottery Jackpot twice in two consecutive weeks, or about the same as being stuck by lightning while being bitten by a shark.
Now, none of what I am saying applies to other updates which are often bundled with security updates, or upgrades.
Click to expand...
Click to collapse
Real good explanation. Good balance of technological and practical
Sent from my iPhone using Tapatalk Pro

acejavelin said:
Well on this I have a pretty strong opinion, and it isn't always well liked... I work in the IT industry with networks, so security is kind of a big deal to me... but Android security updates are essentially worthless, and are only a marketing ploy to make the company look better.
For example, lets look at some major vulnerabilities that have supposedly affected MILLIONS of Android devices... Dirty Cow is a good one, I am in a group here on XDA that is trying to use this vulnerability for something, anything really, but mainly for rooting difficult devices, and in a modern device it is almost impossible because of all the other parts of Android that help keep it secure like DM-verity and SELinux, end result is no usable exploit in almost all cases, although we have some results in cases where we are in complete control of the device with hands on adb access, but even then it is very rare and device specific, not something that you could just download a random malware app and have it affect you, I would need the device in hand. Then there are the terrible ones like Quadrooter, Stagefright, and Towelroot that affected millions, no tens of millions of devices, but have you ever heard of anyone being actually effected by a real exploit of that vulnerability? Nope, me neither, because for the most part these have only been exploited in a lab and not in real life... Because in a modern (I am talking Marshmallow or maybe even Lollipop) there are other things that protect the device, application sandboxing, DM-verity, SE Linux, and IntentFirewall, are all things that would likely protect the device even IF (and that's a big IF) one of these vulnerabilities did happen to be exploited on a device.
So are security updates important... no, not from a technical perspective in real life for the average user, but I certainly wouldn't reject them if they are easy to apply. I accept and apply every single one, even though I know the chances of something happening if I don't are probably less than that of me winning the Powerball Lottery Jackpot twice in two consecutive weeks, or about the same as being stuck by lightning while being bitten by a shark.
Now, none of what I am saying applies to other updates which are often bundled with security updates, or upgrades.
Click to expand...
Click to collapse
So i recovered and now wifi is not working. From the other thread i see that others have this issue as well. What are my options now?

ThanuTK said:
So i recovered and now wifi is not working. From the other thread i see that others have this issue as well. What are my options now?
Click to expand...
Click to collapse
Its a radio version issue... your radio firmware doesn't a match what the kernel wants. You need to flash the right ones. You will have tell me more details of how you recovered.

acejavelin said:
Its a radio version issue... your radio firmware doesn't a match what the kernel wants. You need to flash the right ones. You will have tell me more details of how you recovered.
Click to expand...
Click to collapse
I used XT1575 to update and then just followed the directions. Does that answer your question? if not could you please clarify your question ?
https://androidfilehost.com/?fid=745425885120703327
In the other thread i see people using MPH24.49-18-4 FIRMWARE to fix this issue, but you stated that this might cause issues in the future, so i dont know what to do. Thanks again for helping me and understanding my lack of knowledge with all of this.
https://forum.xda-developers.com/mo...bootloader-t3489110/post69432451#post69432451

ThanuTK said:
I used XT1575 to update and then just followed the directions. Does that answer your question? if not could you please clarify your question ?
https://androidfilehost.com/?fid=745425885120703327
In the other thread i see people using MPH24.49-18-4 FIRMWARE to fix this issue, but you stated that this might cause issues in the future, so i dont know what to do. Thanks again for helping me and understanding my lack of knowledge with all of this.
https://forum.xda-developers.com/mo...bootloader-t3489110/post69432451#post69432451
Click to expand...
Click to collapse
The only difference in your links is one is a later build than the other one. Either one should work fine but if I had my choice, I might pick the first update and then use OTA to get to present. NOTE: I had to restore my September 1 backup with TWRP as the December 1 security patch broke my Bluetooth and I use Bluetooth all the time, it is too important to me to lose over a stupid security patch. I have since frozen the updater to avoid being nagged to death install the December 1 update again. When the next "real" OTA comes along, I will thaw the updater so I can take it and *hope* that the Bluetooth issue is solved. I will of course *always* make a TWRP backup prior to doing *any* update so I always have a way to back out of it in the event something is broken over the latest security patch OTA. HTH

Oreo official update finally released

Not much going on here but the G4 Plus has been finally updated to Oreo. While many of you have unlocked or rooted already, those of you that have not and are on retail should be able download and run this.
Amazon versions may never get this update.
I am curious if there will ever be an easy way for Amazon phones to get this retail update if they are not bootloader unlocked.
When you run the update you will get an error that the ro.product.name does not match (athene_amz instead of athene).
If that small hurdle was overcome and the installer proceeded I am not sure if the phone would not boot loop to recovery because of the system and bootloader mismatch. Does anybody know?

I'm curious if you ever made any progress with updating your Amazon variant? I'm in a similar situation with the Amazon version (xt1625) that is ineligible for the bootloader unlock, and I'd love to find a way to update and squeeze a little more life out of the phone.
I noticed you posed some questions about it in multiple threads but I never saw any actual replies, so thought I'd ask. I'm not knowledgeable in the area, but if there is a way to amend the update file and make it flashable on the Amazon version, I'd give it a shot and see how it goes.
Thanks for any info.
milesius said:
Not much going on here but the G4 Plus has been finally updated to Oreo. While many of you have unlocked or rooted already, those of you that have not and are on retail should be able download and run this.
Amazon versions may never get this update.
I am curious if there will ever be an easy way for Amazon phones to get this retail update if they are not bootloader unlocked.
When you run the update you will get an error that the ro.product.name does not match (athene_amz instead of athene).
If that small hurdle was overcome and the installer proceeded I am not sure if the phone would not boot loop to recovery because of the system and bootloader mismatch. Does anybody know?
Click to expand...
Click to collapse

teeterteeter said:
I'm curious if you ever made any progress with updating your Amazon variant? I'm in a similar situation with the Amazon version (xt1625) that is ineligible for the bootloader unlock, and I'd love to find a way to update and squeeze a little more life out of the phone.
I noticed you posed some questions about it in multiple threads but I never saw any actual replies, so thought I'd ask. I'm not knowledgeable in the area, but if there is a way to amend the update file and make it flashable on the Amazon version, I'd give it a shot and see how it goes.
Thanks for any info.
Click to expand...
Click to collapse
I modified the oem.prop file on the update image by adding AMZ to the athene names. I will upload that here when I get a chance. I haven't actually tried this because my bootloader is locked and I cant wipe this phone as I use it for work.

I flashed Stock Oreo 8.1 OPJ28.111-22. Very slow.
Tried both ElementalX and loonykernel with magisk root, slow, lots of changes... still slow. Whole interface lags. Very slow!
Removed moto apps, still slow.
IDK what else to remove or change...
Trying now again (full wipe and flash) but I'm going back to Nougat Stock after this.