Database Users

will i recieve OTA?

Hi, i just rooted my nexus 7, with custom recovery and unlocked bootloader. Just wanna know will i still recieve ota from google for my tablet? of i would have to relock my bootloader and flashh the stock recovery before i can recieve the ota...?

Since you have flashed a custom recovery, you'll have to flash back the original recovery in order to do a ota.
It doesn't matter if your rooted or if you have a unlocked boot loader.
BTW, You will loose root if you don't use ota keeper from the market.
Sent from my Xperia Arc

mazlano27 said:
Hi, i just rooted my nexus 7, with custom recovery and unlocked bootloader. Just wanna know will i still recieve ota from google for my tablet? of i would have to relock my bootloader and flashh the stock recovery before i can recieve the ota...?
Click to expand...
Click to collapse
First question is why would you care? Its not like there are OTA's happening all the time. there has been basically one OTA since the device first came out and most people got it as soon as they started to use their device.
Second, if you have a custom recovery, that will stop it from working.
IF you put the recovery back, the question of if you will lose Root or not really depends on the OTA type. Most OTA's are incremental, meaning they only contain the changes of the system, not the whole system. If it is an incremental, unless there is something in the OTA that seeks out and removes root, it most likely will not affect it. However, if you have made any real changes to the system (removed system programs) the OTA may fail to run as it assumes everything in a normal system is there.
IF the OTA is a full system update like what the Kindle Fire was doing for a long time, it will flush the complete system area and load a new one, that effectively removes root since when it is done, it is no longer physically there. OTA Root keeper won't help you in those cases since the entire system area get wiped. Getting root back is trivial though as hard as it was originally.
I'd tend to think that the OTA's will be incremental... and I see little need or desire by Google to be hunting down root since it is a Nexus device and it is designed to allow for that. Its not like it is a phone like device where the Wireless operator is having a cow as to whether or not you gained access... its supposed to have that kind of access.
However, it really doesn't matter. When the next OTA comes out, there will be a number of devs which will take it apart and release an update you can use with the recovery you currently have and root and will keep root just fine. these typically get released within hours that someone notices a new OTA in the wild and sometimes you can get it before you actually even have a chance to get the real OTA over the wire.
So not a real big deal. I'd just stay where you are and when one comes out watch to see what gets released to mimic it.
Note changing the state of the bootloader will wipe your device. Unlocking will wipe it and locking it will wipe it. You are best off, unlocking it and just leaving it that way.

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.

Wanting to unlock and root but also want Marshmallow asap

Should I wait to unlock and root if I want to get Marshmallow or is there a way to get it unlocked and rooted?

I would think as long as you do not stray from the stock software you would still get the OTA update. I do not think unlocking the bootloader and simply rooting the phone would prevent the OTA but I could be wrong.

campbellc1052 said:
I would think as long as you do not stray from the stock software you would still get the OTA update. I do not think unlocking the bootloader and simply rooting the phone would prevent the OTA but I could be wrong.
Click to expand...
Click to collapse
Would rooting and then updating break something though? I thought I may have read that somewhere on here.

I just looked into it a little bit more and I think as long as you do not flash a non-stock recovery image you should just be able to disable any system modifications such as xposed and unroot and the update would come through. You can probably find more information on this on google or the moto forums.

Im sure the devs will capture the OTA and make a flashable version, that's usually what happens. It usually doesnt take more than a day after the OTA to do it.

My plan is to wait until after Marshmallow is out before unlocking the bootloader if rooting. Since we have a unlock available we don't have to worry about updates breaking exploits so I am in no rush. The phone is pretty amazing even without root. Once Marsh is out I will test drive a bit and go from there. It could take a week before a dev drops the update or it could take hours... you never know.

Hmmmmm well I'm unlocked and rooted with TWRP..
But there is a Back to Stock zip..
So once Marshmallow comes out ,I'll just go back to Stock and take the OTA...

ttkyles said:
Hmmmmm well I'm unlocked and rooted with TWRP..
But there is a Back to Stock zip..
So once Marshmallow comes out ,I'll just go back to Stock and take the OTA...
Click to expand...
Click to collapse
Yeah, if you have already done it I'm sure someone can assist in getting you the files needed. Even if a dev can walk me through I don't mind pulling it for you. Maybe there will be a back to stock using the marshmallow image then just reroot after installing twrp and you are good to go

campbellc1052 said:
I just looked into it a little bit more and I think as long as you do not flash a non-stock recovery image you should just be able to disable any system modifications such as xposed and unroot and the update would come through. You can probably find more information on this on google or the moto forums.
Click to expand...
Click to collapse
Root breaks the ability to take an OTA, even using the supersu unroot feature the OTA will fail. The only way to take an OTA is to flash a fully stock system and recovery.

BladeRunner said:
Root breaks the ability to take an OTA, even using the supersu unroot feature the OTA will fail. The only way to take an OTA is to flash a fully stock system and recovery.
Click to expand...
Click to collapse
From what I understand it's not so much root that affects the ability to take an OTA it is the bootloader flag and recovery image. Also I think that while a new OTA would completely overwrite the system directory, since we can unlock bootloader, you can just re-flash SuperSU without issue.

I have to say that I'm a bit confused because Motorola have stated that unlocking the bootloader won't affect OTA updates here - https://motorola-global-portal.cust...tail/a_id/91999/p/1449,8620/kw/bootloader OTA
Can anyone clear this up for sure? I'd say a custom recovery would definitely affect them but not just unlocking the bootloader.

skttrbrain said:
I have to say that I'm a bit confused because Motorola have stated that unlocking the bootloader won't affect OTA updates here - https://motorola-global-portal.cust...tail/a_id/91999/p/1449,8620/kw/bootloader OTA
Can anyone clear this up for sure? I'd say a custom recovery would definitely affect them but not just unlocking the bootloader.
Click to expand...
Click to collapse
That's right...unlocking the bootloader alone won't stop an OTA. The custom recovery will be the issue. Basically if you're rooted and running TWRP all you have to do is follow the instructions in the Return To Stock thread and you're good to go for an OTA. Its a pretty simple process.

Can't take OEM updates after unlocking bootloader and installing TWRP

I've unlocked the bootloader and installed TWRP on my girlfriend's Moto G5 Plus, but now whenever she tries to take OEM updates, the device reboots into the updating stage and then fails at an image of a dead Android. I'm at work currently without access to the device, but before I get home I was wondering if anyone else has had similar issues or has a resolution to this issue?
Thank you!

Huntereb said:
I've unlocked the bootloader and installed TWRP on my girlfriend's Moto G5 Plus, but now whenever she tries to take OEM updates, the device reboots into the updating stage and then fails at an image of a dead Android. I'm at work currently without access to the device, but before I get home I was wondering if anyone else has had similar issues or has a resolution to this issue?
Thank you!
Click to expand...
Click to collapse
You can't get those automatic updates if you have modified the phone system (e.g. unlock bootloader)... if this is what you mean.
I'm still not very used to moto devices but, from what I've read so far, you have to install updates via fastboot.

luizlee86 said:
You can't get those automatic updates if you have modified the phone system (e.g. unlock bootloader)... if this is what you mean.
I'm still not very used to moto devices but, from what I've read so far, you have to install updates via fastboot.
Click to expand...
Click to collapse
Yes, that's true stuff! Also, you'll keep getting the update notifications. To end that nightmare, you need to purchase the paid version of Titanium Backup and 'freeze' the Motorola Update Service

luizlee86 said:
You can't get those automatic updates if you have modified the phone system (e.g. unlock bootloader)... if this is what you mean.
I'm still not very used to moto devices but, from what I've read so far, you have to install updates via fastboot.
Click to expand...
Click to collapse
djroese33 said:
Yes, that's true stuff! Also, you'll keep getting the update notifications. To end that nightmare, you need to purchase the paid version of Titanium Backup and 'freeze' the Motorola Update Service
Click to expand...
Click to collapse
Dang! That's unfortunate! I might just install a custom rom for her or something, then. Thanks for the information!

Huntereb said:
Dang! That's unfortunate! I might just install a custom rom for her or something, then. Thanks for the information!
Click to expand...
Click to collapse
I may be wrong.. but AFAIK custom roms don't have the one button navigation feature.

I haven't tested on modern phone but i know that if you want to install successfully an OTA update you need: 1) stock recovery (with TWRP it will fail) 2) an untouched system partition (you must install supersu in systemless mode).
Another way is via flashfire from the play store.
Hope this could help you

luizlee86 said:
I may be wrong.. but AFAIK custom roms don't have the one button navigation feature.
Click to expand...
Click to collapse
Yeah, you're wrong
Enviado desde mi XT1681 mediante Tapatalk

Huntereb said:
I've unlocked the bootloader and installed TWRP on my girlfriend's Moto G5 Plus, but now whenever she tries to take OEM updates, the device reboots into the updating stage and then fails at an image of a dead Android. I'm at work currently without access to the device, but before I get home I was wondering if anyone else has had similar issues or has a resolution to this issue?
Thank you!
Click to expand...
Click to collapse
You can still take OEM updates even if you have unlocked your bootloader. Your phone needs to have stock rom and stock recovery. Since you installed TWRP, its failing to update. Flash stock recovery image and you'll be able to update just fine.

luizlee86 said:
I may be wrong.. but AFAIK custom roms don't have the one button navigation feature.
Click to expand...
Click to collapse
Yes it has but that feature no name like onekey navigation....you can set in fingerprint gesture menu whatever you want

I have a general question about updates. On my G5 plus I'm still on the January 1st Android security level. I unlocked my bootloader but kept the recovery and rom stock.
Will I get OTA updates normally and just be able to install them through the OS? Or do I have to find the update online and install via fastboot?

welp11 said:
I have a general question about updates. On my G5 plus I'm still on the January 1st Android security level. I unlocked my bootloader but kept the recovery and rom stock.
Will I get OTA updates normally and just be able to install them through the OS? Or do I have to find the update online and install via fastboot?
Click to expand...
Click to collapse
You will get all updates via OTA:highfive:, the unlock of bootloader won't prevent you to get updates:laugh:
In extrema ratio flash via fastboot but you won't need that:good:

luizlee86 said:
You can't get those automatic updates if you have modified the phone system (e.g. unlock bootloader)... if this is what you mean.
I'm still not very used to moto devices but, from what I've read so far, you have to install updates via fastboot.
Click to expand...
Click to collapse
djroese33 said:
Yes, that's true stuff! Also, you'll keep getting the update notifications. To end that nightmare, you need to purchase the paid version of Titanium Backup and 'freeze' the Motorola Update Service
Click to expand...
Click to collapse
Wait, so if an ota rolls out, it'll fail. But you can manually flash with fastboot. But even after fastboot flashing, it'll still notify you that an update is waiting?? Even if you manually applied that update?
I'd rather not freeze the service as I do want to know when the next ota comes along that I'll want to flash.

Achieve temporary root to push build.prop changes?

As a US customer, I'm hesitant to unlock the bootloader and lose warranty after owning the phone for less than 48 hours. My last phone died due to a power button failure that happened a month after the warranty ran out. I'll probably eventually start flashing roms and all that fun, but for now I'm going to keep it boring and stock for at least a little bit.
I want to made a minor modification to the build.prop file, but I understand I need root access to save it again. Or, I can do it through TWRP's mount over USB, but that would also require the bootloader to be unlocked. I know in the past I've had phones that allowed temporary root with some sort of exploit or another, and would persist until reboot at least. Is there anything like that on the Moto G5+? Or am I stuck voiding my warranty for one measly line of text in a file?

Dishe said:
As a US customer, I'm hesitant to unlock the bootloader and lose warranty after owning the phone for less than 48 hours. My last phone died due to a power button failure that happened a month after the warranty ran out. I'll probably eventually start flashing roms and all that fun, but for now I'm going to keep it boring and stock for at least a little bit.
I want to made a minor modification to the build.prop file, but I understand I need root access to save it again. Or, I can do it through TWRP's mount over USB, but that would also require the bootloader to be unlocked. I know in the past I've had phones that allowed temporary root with some sort of exploit or another, and would persist until reboot at least. Is there anything like that on the Moto G5+? Or am I stuck voiding my warranty for one measly line of text in a file?
Click to expand...
Click to collapse
There is no known way to achieve root access without unlocking the bootloader, sorry.

Alright. Well, I guess I can always just unlock the bootloader to install TWRP, but don't bother rooting. I can mount and update the build.prop from the TWRP screen I believe.
I've heard that rooting causes some issues with OTA updates and passing safetynet. If I just unlock and replace the bootloader, will it effect those things as well? Or is that only for rooting?

Dishe said:
Alright. Well, I guess I can always just unlock the bootloader to install TWRP, but don't bother rooting. I can mount and update the build.prop from the TWRP screen I believe.
I've heard that rooting causes some issues with OTA updates and passing safetynet. If I just unlock and replace the bootloader, will it effect those things as well? Or is that only for rooting?
Click to expand...
Click to collapse
I don't think you understand, ANY change to the system, even just mounting /system read-write which TWRP would have to do to make changes, can cause any future OTA update to fail... Maybe... We don't what the OTA update script checks exactly as it isn't the same every time.

acejavelin said:
I don't think you understand, ANY change to the system, even just mounting /system read-write which TWRP would have to do to make changes, can cause any future OTA update to fail... Maybe... We don't what the OTA update script checks exactly as it isn't the same every time.
Click to expand...
Click to collapse
Shoot, that's messed up.
I already unlocked bootloader and booted in twrp (didn't flash into it though), but I'm stuck anyway where it keeps asking for a password I didn't set up in order to make changes to system. So you're saying once I get past that step, it might already break OTA??
Shoot.

Dishe said:
Shoot, that's messed up.
I already unlocked bootloader and booted in twrp (didn't flash into it though), but I'm stuck anyway where it keeps asking for a password I didn't set up in order to make changes to system. So you're saying once I get past that step, it might already break OTA??
Shoot.
Click to expand...
Click to collapse
Yes, that's exactly what I'm saying.
I can't remember on this device if the password is your PIN or you have to flash the dm-verity decrypt patch to get past that though.
Unlocking the Bootloader by itself won't effect OTA updates that we have seen, but we do know the script is capable of checking that... So, yeah.

acejavelin said:
Yes, that's exactly what I'm saying.
I can't remember on this device if the password is your PIN or you have to flash the dm-verity decrypt patch to get past that though.
Unlocking the Bootloader by itself won't effect OTA updates that we have seen, but we do know the script is capable of checking that... So, yeah.
Click to expand...
Click to collapse
So just swiping yes to modify system in TWRP does something that the OTA script detects? Even if I don't actually do any modifications?
I guess I don't really care that much as long as I'm still notified that there's an update and can do it manually. I'm just worried because I found a thread about the most recent update, and it seems folks who were rooted and/or otherwise had OTA fail had a hard time nailing down a reliable way to apply the update to their phones. Will this be a problem going forward?

Dishe said:
So just swiping yes to modify system in TWRP does something that the OTA script detects? Even if I don't actually do any modifications?
Click to expand...
Click to collapse
most times the script checks whether the md5 of the system partition has been changed
so as long as you dont modify anything on the system partition OTA should work fine
any small change to system partition will break future OTA

ckret said:
most times the script checks whether the md5 of the system partition has been changed
so as long as you dont modify anything on the system partition OTA should work fine
any small change to system partition will break future OTA
Click to expand...
Click to collapse
Aw man, so one build.prop line added will mess it up. Welp, guess I'm not going to get OTA either way now. I'll just reflash to stock if/when an update comes out, or flash the update directly if someone makes it available when it happens. Its worth it to bypass Moto's crummy camera processing.