Develop Bugs

[Q] Help about rooting and other stuff

Sorry if this question has been asked before, but i could not find any.
So i got the Nexus beast yesterday, and it's already blazing me off with it's greatness. But i got a few problems though:
1. I got the jakjuxw, not the jakju, will i get the same updates as the jakju OTA, but only a week later or so?
2. I did not root the phone before starting using it, but i regret that now. Is there any way i can root it and NOT lose all of my apps and data? I have spent so many hours to customize this device and i dont want to start all over (yes i know about app backup's, but they are slow)
3. If i root but stay with the stock rom, will i still be getting the original OTA updates or does i have to flash the roms manually and wipe the phone every time?
I'd appreciate it if anyone could answer all the questions =)

Baguett said:
Sorry if this question has been asked before, but i could not find any.
So i got the Nexus beast yesterday, and it's already blazing me off with it's greatness. But i got a few problems though:
1. I got the jakjuxw, not the jakju, will i get the same updates as the jakju OTA, but only a week later or so?
Click to expand...
Click to collapse
Not sure about this, it probably depends on what they want to release. I don't think there's any kind of guarantee they'll get the same updates, but there's also probably no reason why they wouldn't.
2. I did not root the phone before starting using it, but i regret that now. Is there any way i can root it and NOT lose all of my apps and data? I have spent so many hours to customize this device and i dont want to start all over (yes i know about app backup's, but they are slow)
Click to expand...
Click to collapse
You need to unlock the bootloader to root, and unlocking the bootloader wipes the device. Sorry. Someday an exploit might be found for ICS that allows you to root without unlocking.
3. If i root but stay with the stock rom, will i still be getting the original OTA updates or does i have to flash the roms manually and wipe the phone every time?
Click to expand...
Click to collapse
If you keep stock recovery, you'll still get OTA updates when rooted. If you use custom recovery like ClockworkMod, you'll have to do them manually (but you won't need to wipe). In both cases, applying the update will probably cause you to lose root and you'll have to re-root. This is easy if you've unlocked the bootloader.
If you root by using some future exploit, you might find that the update you just installed removed root and closed the hole that allowed you to gain it without unlocking the bootloader, and now you're left stuck without root. I'd say just unlock the bootloader now and be done with it. It'll be a pain, but then you don't need to worry about it again.

phazerorg said:
If you keep stock recovery, you'll still get OTA updates when rooted. If you use custom recovery like ClockworkMod, you'll have to do them manually (but you won't need to wipe). In both cases, applying the update will probably cause you to lose root and you'll have to re-root. This is easy if you've unlocked the bootloader.
Click to expand...
Click to collapse
ok thanks
Just unlocked it and rooted it, but i think im gonna install the official google 4.0.2 rom, i wil get the OTA updates then too right?
edit: how am i able to flash a rom without CWM? Also do i really not need to wipe my phone if i use CWM? i had to do it on my Desire.

Baguett said:
ok thanks
Just unlocked it and rooted it, but i think im gonna install the official google 4.0.2 rom, i wil get the OTA updates then too right?
Click to expand...
Click to collapse
Yes, but the updates will probably unroot you. You should be able to just re-root after. If using CWM you can probably flash superuser right after flashing the update and not lose root at all. This is what I always did with my Nexus One when I still had the rooted stock ROM.
edit: how am i able to flash a rom without CWM?
Click to expand...
Click to collapse
If the ROM comes as images (like the Google factory images) you can flash with fastboot. The Google ones come with a script that uses fastboot to do it for you.
Also do i really not need to wipe my phone if i use CWM? i had to do it on my Desire.
Click to expand...
Click to collapse
I meant installing updates here... you don't usually need to wipe if you are installing updates to your current ROM, such as OTA updates to the stock ROM. You need to wipe if you're changing ROMs. It's probably no different than your Desire.

Does rooting only removes the ability for OTA updates?

Hey guys just received my n7 yesterday and am very pleased with this, however I have some questions.
Does rooting (only) removes your OTA updates access? I also own a Galaxy S4 (rooted) and I can't get OTA, it says it's modified, but I did flash a custom update on it and kernel. So if I just root my n7, and not flash anything, I will still get OTA's correct? I just want to use some apps which requires root access and not planning to flash a custom rooms or anything. Thanks for any help.
Sent from my Nexus 7 using Tapatalk 4

Mine is always rooted, and I get all OTAs.
Sent from my Nexus 7 using xda app-developers app

You just need to have the stock recovery to receive OTAs.

Username invalid said:
You just need to have the stock recovery to receive OTAs.
Click to expand...
Click to collapse
So if I have twrp installed, i won't receive them?
Sent from my Nexus 7 using Tapatalk 4

Takes 10 seconds to reflash the stock recovery.

UPDATE: SuperSU-v1.55 added the fix for the OTA update issue, so this post is no longer necessary unless you are using an older version of SuperSU
This post also applies to JSS15Q update.
I actually went through and tested JWR66N rooted with SuperSU and the JSS15J OTA update. I expected it to work but it exited with an error.
Ironically the JSS15J OTA actually did patch every single file successfully but near the end while setting permissions, it came up with an error, so after reboot you'll actually be running with all JSS15J rom files, except your build will still say JWR66N, you'll still be running the JWR66N recovery, and you'll still be running the 3.05 bootloader.
I tracked down the issue and put together a fix for it. If you want, it is attached to this post. You just run it after installing SuperSU, so basically:
adb reboot bootloader
fastboot boot twrp.img
within TWRP
install UPDATE-SuperSU-v1.51.zip (SuperSU v1.55 or greater incorporates the OTA fix)
install UPDATE-SuperSU-v1.55.zip
install UPDATE-SuperSU-ota.zip (can be chain installed, just make sure you choose to install it 2nd)
reboot
You'll need to redo these steps (both the installs) after you receive the OTA to preserve root and ability to receive future OTAs.
Also as others have mentioned it is best to be running stock recovery (which the above commands will allow you to do because twrp is never flashed on the tablet) I've attached the stock recovery for JSS15J in case someone needs it.
If you make ANY modifications or delete files from the stock ROM with your new root privileges, then you will greatly increase the chances of the OTA failing. Adding new files is normally fine.

Well shoot - now you have me worried. I did install TWRP, but never considered that would block OTAs. Do they attempt to install and fail?
Sent from my Nexus 7 using xda app-developers app

rmm200 said:
Well shoot - now you have me worried. I did install TWRP, but never considered that would block OTAs. Do they attempt to install and fail?
Click to expand...
Click to collapse
On some platforms, especially when flashing bootloaders and/or radios, the stock recovery pulls some funky maneuvers to get that done. Often custom recoveries are not privy to those maneuvers. Also sometimes custom recoveries will experiment with custom kernels which don't always have the bootloader and/or radio devices mapped the same as the stock kernel. This can lead to problems to.
Thus it is safest to use stock recovery to flash OTAs.
I have flashed the complete JSS15J OTA except for the bootloader part using TWRP and it works ok. All the ROM files are patched.
I just didn't feel like risking my tablet with the bootloader flash portion of JSS15J OTA using twrp. It might work fine. I just know from the past the potential for issues are higher in that section of the OTA flash.

Is it common for nice folk on here to upload a stock zip of say for example, 4.3.1 when it releases so that we can flash it through a custom recovery (e.g., TWRP, CWM etc.), without having to change our custom recoveries?

It was common on other platforms I've used, but I don't know about here.

Root will not prevent an OTA update from coming in and installing, and a custom recovery won't "block" (it just won't be able to complete the install of it automatically). I have been installing OTA updates on rooted Nexus devices with custom recoveries since the Nexus One, and assuming the new Nexus 7 works the same way, the following applies:
If you are running stock ROM, your deivce will receive the notification and download the update, even if rooted
If you are running stock recovery, the update will install automatically as normal
If you are running a custom recovery like CWM or TWRP, it will fail to install automatically but it will still have downloaded to the device and you can use the custom recovery to install it yourself (I've never had this fail)
If you have modified files in /system, the OTA update is pretty much guaranteed to fail regardless of which recovery you use
If you successfully install the OTA update, you will no longer have root, so flash SuperSU using a custom recovery after the OTA update installs
Also:
You can always look for the OTA zip URLs on XDA and just download the update yourself to flash if you don't want to wait for it to come to your device (this is what I always do)
You can flash factory images instead of the update, without losing data (see other threads for how)
If you want to keep stock recovery installed, you can always use fastboot to boot a custom recovery without flashing it, in case you ever need it
The above is accurate and correct as far as I'm aware from my own experience over the years with Nexus devices. I'm sure someone will be happy to correct me if anything is wrong Hope this helps.

phazerorg said:
Root will not prevent an OTA update from coming in and installing, and a custom recovery won't "block" (it just won't be able to complete the install of it automatically).
Click to expand...
Click to collapse
I thought the same about root not blocking the OTA update install from being successful, but that was with years of using superuser.
With SuperSU (I am not sure which version introduced it) they set the immutable flag on a file in almost every OTA. I believe this is to support some OTA survival mode. This causes the OTA to fail in the section where it sets permissions. All the files are patched at that point, but the build.prop hasn't been modified to reflect the new version # and the bootloader and recovery haven't been flash.
You'll essentially be running JSS15J but your software will report it is on JWR66N, your bootloader wouldn't have been patched, and you would be running JWR66N recovery.

TheAltruistic said:
Is it common for nice folk on here to upload a stock zip of say for example, 4.3.1 when it releases so that we can flash it through a custom recovery (e.g., TWRP, CWM etc.), without having to change our custom recoveries?
Click to expand...
Click to collapse
yes the ota update zip always gets posted so you can manually flash with a custom recovery...
just keep in mind you need to keep your files stock otherwise it might not work
Sent from my Nexus 7 2

nolook said:
yes the ota update zip always gets posted so you can manually flash with a custom recovery...
just keep in mind you need to keep your files stock otherwise it might not work
Sent from my Nexus 7 2
Click to expand...
Click to collapse
When you say keep your files stock what does that mean exactly? I have titanium backup app installed would that be one of them? Thanks.

Mightym83 said:
When you say keep your files stock what does that mean exactly? I have titanium backup app installed would that be one of them? Thanks.
Click to expand...
Click to collapse
Titanium backup is an app, I assume with files he is targeting e. G. Config files.
Sent from my Nexus 7 (2013)

Mightym83 said:
When you say keep your files stock what does that mean exactly? I have titanium backup app installed would that be one of them? Thanks.
Click to expand...
Click to collapse
It means don't modify or delete any files in /system
Don't remove a system app that shipped with the tablet. You can install a new version as that just hides the one in /system, but if you remove or modify the original, then the OTA will very likely fail (depending on how complex the OTA is)
Adding files is ok.

Alright, so here's my scenario. Hopefully someone can tell me what should happen:
I am running the stock ROM on my Nexus 7 (2013), but I have ClockWorkMod Recovery installed and I'm using Koush's Superuser app for root permissions. The only system file that I think I have changed is my hosts file because of Adaway. That is easily reverted, though.
So can I just download the OTA, install it manually from the custom recovery (flashing the update.zip file), and then re-flash Koush's superuser app back onto the device?
Will that go smoothly, and will the newer build number be accurately reflected in my About Phone afterward?
(that last part is just my OCD talking)

phazerorg said:
:
[*]If you are running a custom recovery like CWM or TWRP, it will fail to install automatically but it will still have downloaded to the device and you can use the custom recovery to install it yourself (I've never had this fail)
Click to expand...
Click to collapse
This was very helpful, and this is the category i fall in. However, i have installed a kernel. does that change anything?
So basically what you are saying is this, with my current set up:
1 - i will get the update, it will download, but wont install. I should boot into TWRP and install the file that way. Correct? Where is the downloaded file stores?
2 - I can just wait for the download to be posted on here, and just install via twrp.
3 - either way, after installing it, i will lose root. I should then boot into twrp and flash supersu.
Correct?

Theoretically it could work. I believe the flash has worked with twrp.
Personally I always put stock recovery back to flash ota's though especially if there is a bootloader (or radio if you have a mobile version) because on some platforms they involve special procedures that may not be in the custom recovery.
On nexus it looks like it will work with custom recovery but it takes so little effort to put stock recovery back I just do it automatically.
Having said that, I've seen one person post it worked on twrp but haven't read an experience on cwm. Not saying it will or won't work.

If we are running the stock ROM, but have it rooted with the custom recovery, why cant we just use Wegfresh's nexus toolkit to Unroot and image using the updated IMG file?
Then go through and use it to recreate the root\custom recovery again?

Permanent root

I am new to the whole understanding of root on non-Nexus devices seeing how I had to root my Nexus 4 after each update and I had a fair bit of knowledge hacking/modding/rooting the Nexus.
Kedros over at oppoforums (http://www.oppoforums.com/threads/how-to-root-your-oppo-find-7a-w-oppo-recovery.11309/) provided a root method that is permanent. I have no plans to install custom ROMs nor do I feel the need to flash a custom recovery (ex. TWRP).
My question is:
1. Will I still receive OTA updates from Oppo after I root?
2. If no to step 1, will flashing ColorOS updates remove the "permanent" root?
Thanks.

Root and OTA
anwedr said:
I am new to the whole understanding of root on non-Nexus devices seeing how I had to root my Nexus 4 after each update and I had a fair bit of knowledge hacking/modding/rooting the Nexus.
Kedros over at oppoforums provided a root method that is permanent. I have no plans to install custom ROMs nor do I feel the need to flash a custom recovery (ex. TWRP).
My question is:
1. Will I still receive OTA updates from Oppo after I root?
2. If no to step 1, will flashing ColorOS updates remove the "permanent" root?
Thanks.
Click to expand...
Click to collapse
1. Yes. OTA updates will work so long as you're using stock recovery and haven't made drastic changes to the /system partition.
2. Flashing an incremental (OTA) update in recovery will have the same effect as tapping "install update" from the about phone menu. You will lose root. If you flash a complete dump of the /system you will lose root as well since you are replacing /system.
Losing root isn't a big deal. Just flash again from recovery. You could try the OTA survival option built into SuperSu. I didn't bother trying because it takes less than a minute to reboot to recovery and flash SuperSu/su binary. What might be a big deal with the OTA update is that it wipes /data. This is odd because the pop-up that appears prior to installing the update specifically states that you won't lose apps or data. Your custom ROM plans may change after you use ColorOS. I hate it. It's glitchy and has a huge memory footprint. I'd recommend trying the 2.0 beta. I haven't had my Find 7a for long, but I've had no bugs thus far with the 2.0 beta. It's available on the Oppo Forums.
-Sent from my Panasonic 3DO

Is it possible to root the OP3 without a custom recovery?

I don't really need a custom recovery (I don't know of any features custom recovery will give me I really need?) and for now I'm fine running stock roms (I always give stock a few weeks just as a baseline before I start custom roms) but I was wondering, how would one go about rooting the OP3 without installing a custom recovery?
Is it possible / easily doable? Or am I better off just to flash some custom recovery and ditch the stock one?
The reason I don't want to go away from stock just yet is I know oneplus is still updating the rom and custom recoveries, historically, have made OTA updates problematic.

Rooting will also mess up Ota too, but if u install a custom recovery, now that we have stock recovery it will be very easy to revert back for OTAs, there should be a way to root without a custom recovery but I am not sure how though, but with how oneplus makes it so easy to unlock bootloader and flash customers stuff there is really no need to stay stock

You can simply connect your OP3 to a PC and boot to TWRP without flashing it:
fastboot boot twrp.img
Then do a backup with twrp before rooting. I use the above method with systemless root
and also don't really need a custom recovery at this point. This might change once CM13 matures on the OP3...
OTAs might work this way in the future. If they don't, restore your system + boot (kernel) partition
and try the OTA again.
edit: implying your bootloader is already unlocked

pileot said:
I don't really need a custom recovery (I don't know of any features custom recovery will give me I really need?) and for now I'm fine running stock roms (I always give stock a few weeks just as a baseline before I start custom roms) but I was wondering, how would one go about rooting the OP3 without installing a custom recovery?
Is it possible / easily doable? Or am I better off just to flash some custom recovery and ditch the stock one?
The reason I don't want to go away from stock just yet is I know oneplus is still updating the rom and custom recoveries, historically, have made OTA updates problematic.
Click to expand...
Click to collapse
As far as I know, you'd have to have TWRP to get root.
I don't think getting it rooted will mess up the OTA updates, other users sprovide flashable zips for the OTA anyway.. so you can still flash the zips manually with TWRP to keep you updated.
Sent from my ONEPLUS A3000 using XDA-Developers mobile app

To get root yes, you would need TWRP to flash to certain partitions but to keep root no. Your phone will operate just fine with root and stock recovery. Check what the user a few posts above mine said about temporary flashing TWRP to achieve your short term goals

AcmE85 said:
You can simply connect your OP3 to a PC and boot to TWRP without flashing it:
fastboot boot twrp.img
Then do a backup with twrp before rooting. I use the above method with systemless root
and also don't really need a custom recovery at this point. This might change once CM13 matures on the OP3...
OTAs might work this way in the future. If they don't, restore your system + boot (kernel) partition
and try the OTA again.
edit: implying your bootloader is already unlocked
Click to expand...
Click to collapse
So have you actually done this by temporary booting twrp and then using the systemless root and still have stock recovery? Also how do I root systemless? Really wanna know because wanna keep stock recovery and have root

TheSvensson said:
So have you actually done this by temporary booting twrp and then using the systemless root and still have stock recovery? Also how do I root systemless? Really wanna know because wanna keep stock recovery and have root
Click to expand...
Click to collapse
Yes, I have the stock recovery and it is rooted.
The recovery partition has nothing to do with all the other partitions except that it can read and write them.
This is the zip I flashed to get systemless root:
https://www.androidfilehost.com/?fid=24591000424939898
Some users reported that some Root-apps are not supported this way.
I am using Titanium Backup, Adaway, Trimmer and Root Explorer without issues.
Keep in mind that I did not get any OTA so far since running this setup, so I am not sure if official OTAs will or will not work.
All I did was manually flash OxygenOS 3.1.3 in TWRP (not flashed but booted) and reflash the root package afterwards.

AcmE85 said:
You can simply connect your OP3 to a PC and boot to TWRP without flashing it:
fastboot boot twrp.img
Then do a backup with twrp before rooting. I use the above method with systemless root
and also don't really need a custom recovery at this point. This might change once CM13 matures on the OP3...
OTAs might work this way in the future. If they don't, restore your system + boot (kernel) partition
and try the OTA again.
edit: implying your bootloader is already unlocked
Click to expand...
Click to collapse
I have an unlocked bootloader and tried this on my PC:
C:\adb>fastboot boot twrp.img
downloading 'boot.img'...
OKAY [ 0.709s]
booting...
OKAY [ 0.373s]
finished. total time: 1.092s
Nothing happens, bootloader start screen stays frozen. Until I hold down the power button. Might you know why?

AcmE85 said:
You can simply connect your OP3 to a PC and boot to TWRP without flashing it:
fastboot boot twrp.img
Then do a backup with twrp before rooting. I use the above method with systemless root
and also don't really need a custom recovery at this point. This might change once CM13 matures on the OP3...
OTAs might work this way in the future. If they don't, restore your system + boot (kernel) partition
and try the OTA again.
edit: implying your bootloader is already unlocked
Click to expand...
Click to collapse
i tried to boot into twrp recovery with above command, but the phone seems to be stuck in the bootloader and not responding. Any ideas?
edit: comment above describes exact same behaviour, sorry for double post

Sorry, don't know. Booting takes a couple seconds on my device though.
I am using this recovery img: http://www6.zippyshare.com/v/iK6tCE6D/file.html
Got it from XDA, but unfortunately don't know anymore who build it.

AcmE85 said:
Sorry, don't know. Booting takes a couple seconds on my device though.
I am using this recovery img: http://www6.zippyshare.com/v/iK6tCE6D/file.html
Got it from XDA, but unfortunately don't know anymore who build it.
Click to expand...
Click to collapse
Thanks, that twrp img worked for me. The one I was using didnt allow me to boot to it.

AcmE85 said:
Keep in mind that I did not get any OTA so far since running this setup, so I am not sure if official OTAs will or will not work.
Click to expand...
Click to collapse
Any chance you know if you get OTA by now?
I really like the Op3 and dont wont to change anything except i would like to habe root access. Your method seems to be the best way to achieve that.

hahamuntz said:
Any chance you know if you get OTA by now?
I really like the Op3 and dont wont to change anything except i would like to habe root access. Your method seems to be the best way to achieve that.
Click to expand...
Click to collapse
The updater will recognize root on your device and download the full 1.3 gb Rom file.
But after updating root will be gone, so you will have to reflash root after each ota.

AcmE85 said:
The updater will recognize root on your device and download the full 1.3 gb Rom file.
But after updating root will be gone, so you will have to reflash root after each ota.
Click to expand...
Click to collapse
Thanks for the quick answer
Just to make sure, if I root using this method nothing will change, except I have root access, my bootloader is unlocked and the updates will be big, but I can update the normal way, I will just lose the root access? Is that correct or am I missing something?

hahamuntz said:
Thanks for the quick answer
Just to make sure, if I root using this method nothing will change, except I have root access, my bootloader is unlocked and the updates will be big, but I can update the normal way, I will just lose the root access? Is that correct or am I missing something?
Click to expand...
Click to collapse
One more thing:
If you have TWRP, automatically installing the big OTA will remove it and go back to the stock recovery.
I always manually move the downloaded ota from android/data/com.oneplus.ota/files/.OnePlusOta
to my download folder, boot into TWRP and flash it + SuperSU on my own.

AcmE85 said:
One more thing:
If you have TWRP, automatically installing the big OTA will remove it and go back to the stock recovery.
I always manually move the downloaded ota from android/data/com.oneplus.ota/files/.OnePlusOta
to my download folder, boot into TWRP and flash it + SuperSU on my own.
Click to expand...
Click to collapse
So you have TWRP installed? I thought you won't get OTAs if you have a custom recovery? So i could just flash TWRP and root and still get OTAs?

hahamuntz said:
So you have TWRP installed? I thought you won't get OTAs if you have a custom recovery? So i could just flash TWRP and root and still get OTAs?
Click to expand...
Click to collapse
Yes, OTAs will come and because of Root you will get the full OTA regardless, which does not cause any issues with TWRP.
I tried my previous method and the regular OTA would fail because of root which changes the kernel or the system partition.
OnePlus reacted to this and introduced the full rom OTAs at some point.
So with root on my device this is how I do OTAs now:
- get the OTA notification for the full rom
- download but don't install
- move the downloaded zip from android/data/com.oneplus.ota/files/.OnePlusOta to my download folder
- manually boot into twrp and flash full rom zip + SuperSU

AcmE85 said:
Yes, OTAs will come and because of Root you will get the full OTA regardless which does not cause any issues with TWRP.
Click to expand...
Click to collapse
Okay, thanks so much for your help

Receiving OTA updates while rooted

I'm planning on rooting my Moto Z Play but staying on the stock ROM as it has better battery life (according to XDA members) compared to LineageOS. I also really like Moto Display and all of the other exclusive features to this ROM.
However, I still want to receive OTAs after doing so. I've read that an app called FlashFire can help me with this.
Question 1: Do the OTAs download even if your system is rooted? I've read that some phones do download the OTAs, but fail when the flashing starts as they have a custom recovery, while some phones don't even download at all once it detects that you're rooted.
Question 2: Will it work even if I have TWRP installed?
Thank you.

Hi i dont think you can receive OTAs after unlocking bootloader and iff you do they will fail on installation as you have said. Secondly in my opinion you are right and i have tried almost all the roms on here and by far the stock N is the best rom for fluidity battery life app compatibility etc so i went back to stock but the deodexed N debloated version because im rooted. Iff i were you i would not root at this time because i think Official Oreo is about to be released for our phone and it would be a good idea to hangon a while but that is entirely your choice.

djdelarosa25 said:
However, I still want to receive OTAs after doing so. I've read that an app called FlashFire can help me with this.
Click to expand...
Click to collapse
Never really tested Flashify and FlashFire. If you succeed please write how it works, which steps to do to be on the safe side
djdelarosa25 said:
Question 1: Do the OTAs download even if your system is rooted? I've read that some phones do download the OTAs, but fail when the flashing starts as they have a custom recovery, while some phones don't even download at all once it detects that you're rooted.
Click to expand...
Click to collapse
Download fine. Install fails, yes.
djdelarosa25 said:
Question 2: Will it work even if I have TWRP installed?
Click to expand...
Click to collapse
No. That's why I never install twrp, I just boot it when needed. You need a computer and a cable every time you want to start twrp, but recovery partition stays untouched using fastboot boot.
Idea is:
1. Take a backup of boot partition before rooting
2. Install the kernel you need to avoid f2fs problems, then Magisk. Both modifies the boot partition, nothing else.
When an OTA arrives, you restore your backup of boot partition and everything is stock. OTA is supposed to work fine.

In theory, if I just run TWRP off from the PC and flash SuperSU on my phone without flashing TWRP, I would be rooted, right? And the OTAs would install, but I will lose root access?

djdelarosa25 said:
And the OTAs would install, but I will lose root access?
Click to expand...
Click to collapse
No. SuperSU modifies boot partition. OTA do not install while boot partition is modified.
You need to restore NANDROID backup of original stock boot partition prior to rooting, then you should be fine for install OTA.
---------- Post added at 11:45 ---------- Previous post was at 11:29 ----------
Just an additional hint: Modifying logo also prevents OTA. If you suppress that unlocked bootloader warning with a different logo, of course you need to restore the original logo partition before applying OTA.

tag68 said:
No. SuperSU modifies boot partition. OTA do not install while boot partition is modified.
You need to restore NANDROID backup of original stock boot partition prior to rooting, then you should be fine for install OTA.
Just an additional hint: Modifying logo also prevents OTA. If you suppress that unlocked bootloader warning with a different logo, of course you need to restore the original logo partition before applying OTA.
Click to expand...
Click to collapse
That's a pity. Oh well, I might just have to wait for Oreo.
Thanks a lot!

"'Just an additional hint: Modifying logo also prevents OTA"
Actually...not my experience. I have an unlocked bootloader, flashed a stock rom file by file, except for logo.bin, which is a modded one to get rid of the annoying "untrustworthy" startup screen.
All worked well and recently got the OTA update all installed as normal by the system.
Will wait now to get the official oreo update before i muck around further.
Actually, on the 22-2-8 build on the phone now it runs really well and battery life is great. Getting over 2 days in my usage pattern easy.
Camera good as well. Got some nice photos of the local beach last night.

You can get back to stock, and get ota's
https://forum.xda-developers.com/moto-z-play/how-to/guide-relock-bootloader-to-lasted-stock-t3718190

Note: Lock of Bootloader is not required to get OTA update. It makes sure that you do no action which prevents OTA, but if you take care this does not happen (for instance not rooting which modifies system or boot partition), you eg can take advantage of Nandroid backup only booting TWRP for this purpose.