Develop Bugs

OTA Update for rooted g pad

Hi!
Has anyone installed the update OTA on a rooted g pad?
Is it safe to do it or it's not possible?
How can I install the update if I am rooted and keep my root?

goldengutz13 said:
Hi!
Has anyone installed the update OTA on a rooted g pad?
Is it safe to do it or it's not possible?
How can I install the update if I am rooted and keep my root?
Click to expand...
Click to collapse
I have seen people reporting problems in other threads here on XDA. Here in the US they haven't yet released the OTA update. If this is anything like my experience with my phone (a GS3). OTA update of a factory rom when rooted often does seem to cause problems. The only device I haven't had problems with taking an OTA when rooted were a Nexus device (Nexus 7) and something running CyanogenMod.

muiriddin said:
I have seen people reporting problems in other threads here on XDA. Here in the US they haven't yet released the OTA update. If this is anything like my experience with my phone (a GS3). OTA update of a factory rom when rooted often does seem to cause problems. The only device I haven't had problems with taking an OTA when rooted were a Nexus device (Nexus 7) and something running CyanogenMod.
Click to expand...
Click to collapse
so I have to unroot it first, install update then root again?

I have a related question - how to unroot and install OTA??
I tried to install, but it didn´t work, tablet said there´s no OTA for rooted devices.
I unrooted using SuperSU, but the situation is still the same.

Dekxster said:
I have a related question - how to unroot and install OTA??
I tried to install, but it didn´t work, tablet said there´s no OTA for rooted devices.
I unrooted using SuperSU, but the situation is still the same.
Click to expand...
Click to collapse
I used the LG Support Tool method which involves putting the tablet into download mode and doing the update recovery procedure in the LG Support Tool. This (after a long download process) should result in a tablet which is identical to what came in the box. (in the US the procedure currently installs 4.2.2). When it finished the download and install, it reboots the tablet, if you then are stuck in a boot loop, simply do the key combination for a factory reset and it then should boot.
The unroot procedure via SuperSU does seem to leave something behind that the OTA still detects...
If you need further details I have another post in one of these threads detailing exactly what I did...
---------- Post added at 01:05 PM ---------- Previous post was at 01:01 PM ----------
goldengutz13 said:
so I have to unroot it first, install update then root again?
Click to expand...
Click to collapse
That is what I plan on doing once the US version is released, however it is potentially a little more complicated since I have heard that LG has patched the LOKI vulnerability which means no custom roms or custom recovery until a new boot loader vulnerability is found, or until you revert to the original boot loader instead of the new one in the 4.4.2 release (if possible)...

muiriddin said:
That is what I plan on doing once the US version is released, however it is potentially a little more complicated since I have heard that LG has patched the LOKI vulnerability which means no custom roms or custom recovery until a new boot loader vulnerability is found, or until you revert to the original boot loader instead of the new one in the 4.4.2 release (if possible)...
Click to expand...
Click to collapse
Nah. You can bet that within 48 hours after the US version is released, there will be a flashable build available with root and recovery.

Subtleone said:
Nah. You can bet that within 48 hours after the US version is released, there will be a flashable build available with root and recovery.
Click to expand...
Click to collapse
True, more than likely a flash-able version will exist once someone makes it.

It already has a work around for loki by reinstalling the old aboot
http://forum.xda-developers.com/showthread.php?t=2698267
Just do steps 2 and 3.
Works fine on mine
Sent from my LG-V500 using xda app-developers app

I upgraded Via OTA my rooted lgpad and when it rebooted... stuck in recovery.
So i had to flash with lg tool.
I did not lose any data but a bit of time.
My suggestion is to flash with lg tool and then root again.
sent from tablet

I think the issue with this procedure is the recovery / bootloader, not the rooting itself. Still, you will most likely end with an unbootable OS. You are better off flashing via recovery a perfectly stock, pre-rooted image, like this http://forum.xda-developers.com/showthread.php?t=2707363

Trunkam said:
I upgraded Via OTA my rooted lgpad and when it rebooted... stuck in recovery.
So i had to flash with lg tool.
I did not lose any data but a bit of time.
My suggestion is to flash with lg tool and then root again.
sent from tablet
Click to expand...
Click to collapse
When you use the lg tool (pc software) did it automatically download the kitkat update?
Did you encounter any issue when you used lg tool?

Trunkam said:
I upgraded Via OTA my rooted lgpad and when it rebooted... stuck in recovery.
So i had to flash with lg tool.
I did not lose any data but a bit of time.
My suggestion is to flash with lg tool and then root again.
sent from tablet
Click to expand...
Click to collapse
So you did NOT unroot first?
Steps you did were: (with rooted only g pad)
Update via pc lg tool
Root using IOROOT25.zip method
This correct?

goldengutz13 said:
When you use the lg tool (pc software) did it automatically download the kitkat update?
Did you encounter any issue when you used lg tool?
Click to expand...
Click to collapse
I had to click on "recover" Something sorry I have no my PC now.. I left it at work. But I think you'll find.
U got some option and considering lgpad did not boot after update.. I had only one.
It's the procedure that you got to follow after you set gpad in download mode.
No issue at all, just one thing: after rooting you will have to flash a custom recovery if you need, because flashing with lg, flash even lg stock recovery.
erwaso said:
So you did NOT unroot first?
Steps you did were: (with rooted only g pad)
Update via pc lg tool
Root using IOROOT25.zip method
This correct?
Click to expand...
Click to collapse
No I did not unroot.. But only because I did not think about it. And that's the reason why gpad was not able to boot to system and I had to flash it via lg software.
I set gpad in download mode,,then flash via lg software, root with ioroot and finally flashed with flashify custom recovery
Hope to have helped guys
Now I'll go to sleep!
tapatalked..

I updated to version 4.4.2 Via OTA my rooted gpad and not had any problems
Steps:
1- factory reset
2- update via OTA
Attention: I think the rom has to be original (no eliminated sys apps with titanium or other) because it goes check the integrity of the rom (4.2.2)
------------------------------------------------------------ Edit --------------------------------------------------------------------------
3- Rooted with IOroot25

I've done an OTA update on my rooted G Pad, no issues either. I didn't do a factory reset, just did the update.

I updated my rooted v500 2 days ago using LGs PC software. The process took around 45 minutes and resulted in a successful KitKat update, however I no longer have root. I have a few strange issues with random unmounting of the SD card, which happened about 4 times while Play Music was copying 2gig of on device songs to it. I also seem to have lost quiet mode - maybe it's been moved out of the sound settings menu - would appreciate a comment if anyone knows where it is.
Sent from my LG-V500 using Tapatalk

Hugo-PT said:
I updated to version 4.4.2 Via OTA my rooted gpad and not had any problems
Steps:
1- factory reset
2- update via OTA
Attention: I think the rom has to be original (no eliminated sys apps with titanium or other) because it goes check the integrity of the rom (4.2.2)
Click to expand...
Click to collapse
I froze a few apps using rom toolbox, think that would matter?
---------- Post added at 07:29 AM ---------- Previous post was at 07:28 AM ----------
GePeKo said:
I updated my rooted v500 2 days ago using LGs PC software. The process took around 45 minutes and resulted in a successful KitKat update, however I no longer have root. I have a few strange issues with random unmounting of the SD card, which happened about 4 times while Play Music was copying 2gig of on device songs to it. I also seem to have lost quiet mode - maybe it's been moved out of the sound settings menu - would appreciate a comment if anyone knows where it is.
Sent from my LG-V500 using Tapatalk
Click to expand...
Click to collapse
The development section has a thread on IOROOT and it works. Have at it! I'll do this whole thing when the kids nap lol

erwaso said:
I froze a few apps using rom toolbox, think that would matter?
Click to expand...
Click to collapse
with frozen apps you shall have no problems.

Verizon LG G Pad 8.3 system update

I rooted this tablet last week (just rooted, I left it stock) and this morning I notice there is a system update waiting to be installed. I am reading Lollipop is starting to roll out in Asia somewhere now but I am in the US lol. I thought it wasn't possible to get OTA updates once you root? If I allow this to update will I get unrooted, would it even work?
I foolishly allowed it to update after checking in Supersu to not allow the root to be lost and now I keep booting directly into TWRP lol. How do I wipe this tablet from TWRP so that it is fully stock again (NO ROOT)? I see a factory reset option in TWRP do I need to include all the partitions in the advanced wipe or is just the normal wipe method enough? Or will this not work at all? I already tried to restore the phone using TWRP to my backup and that didn't seem to work.

Anthony-m said:
I rooted this tablet last week (just rooted, I left it stock) and this morning I notice there is a system update waiting to be installed. I am reading Lollipop is starting to roll out in Asia somewhere now but I am in the US lol. I thought it wasn't possible to get OTA updates once you root? If I allow this to update will I get unrooted, would it even work? .
Click to expand...
Click to collapse
Simply rooting a device doesn't keep it from TRYing to update via OTA. Rooting can prevent an OTA from succeeding, plus can hard or soft brick if you try to take an OTA, although usually only if you've gone beyond just rooting by installing a custom recovery or changing the contents of any partition besides Data by, fire example, downgrading your bootloader (aboot.img) or modem, running a custom kernel, debloating system apps, etc.
There are at least three variants of the G Pad 8.3. I have the VK810.4G, which do you have?
I know on the VK810.4G, Verizon just released a very, very minor update from LG build #23A to 24A. Still KitKat.
I foolishly allowed it to update after checking in Supersu to not allow the root to be lost and now I keep booting directly into TWRP lol.
Click to expand...
Click to collapse
There's the main problem, you had a custom recovery installed. OTAs are applied with the stock recovery, that's why it (probably soft) bricked it.
How do I wipe this tablet from TWRP so that it is fully stock again (NO ROOT)? I see a factory reset option in TWRP do I need to include all the partitions in the advanced wipe or is just the normal wipe method enough? Or will this not work at all? I already tried to restore the phone using TWRP to my backup and that didn't seem to work.
Click to expand...
Click to collapse
You might not be able to fix it from TWRP. You could try @autoprime 's fix recovery zip available the same page his flash2 scripts are. You'll have to Google:
autoprime flash2
Click to expand...
Click to collapse
.
Otherwise, you'll have to restore to 100% stock unrooted and start from scratch. Two methods.
One is using LG's official Mobile Tool, which will download the latest official ROM in KDZ format (takes 20+ minutes to download) and flash it with your tablet in Download mode (probably with the tablet off, hold both up and down volume buttons in and while holding them, turn the tablet on.
I've got to go do something so hopefully someone else will help further or I can get back to you later, dont know when though.
Good luck!
Sent from my VK810 4G

I did the TWRP terminal commands from the thread listed below and it got me right out of that jam...
http://forum.xda-developers.com/lg-g-pad-83/help/vk810-download-mode-boot-loop-t2991512

OK now that I am up and running fine the system update message keeps popping up. This time I KNOW not to try and upgrade while rooted. Is there any way I can stop the tablet from constantly giving me the upgrade message? Can I do anything from TWRP to stop this?

Anthony-m said:
... This time I KNOW not to try and upgrade while rooted. Is there any way I can stop the tablet from constantly giving me the upgrade message? Can I do anything from TWRP to stop this?
Click to expand...
Click to collapse
Don't install TWRP. I was rooted (w/ stock recovery) with 23A, and the OTA update worked fine (still rooted).

DeanGibson said:
Don't install TWRP. I was rooted (w/ stock recovery) with 23A, and the OTA update worked fine (still rooted).
Click to expand...
Click to collapse
TWRP is already installed..
Can I uninstall TWRP, keep root , do the update and then reinstall TWRP? If so how? Is there any other way around this issue, any way of not having the tablet continue to ask me to upgrade? Thanks BTW...

Anthony-m said:
TWRP is already installed..
Can I uninstall TWRP, keep root , do the update and then reinstall TWRP? If so how? Is there any other way around this issue, any way of not having the tablet continue to ask me to upgrade? Thanks BTW...
Click to expand...
Click to collapse
Yes, you can do that, but I don't know the steps. Others here do.
Why do you want TWRP? I thought the usual reason was to install custom ROMs (in which case you won't receive any OTA updates). If you just want to root, it's an unnecessary complication (as you have discovered).

DeanGibson said:
Yes, you can do that, but I don't know the steps. Others here do.
Why do you want TWRP? I thought the usual reason was to install custom ROMs (in which case you won't receive any OTA updates). If you just want to root, it's an unnecessary complication (as you have discovered).
Click to expand...
Click to collapse
Thanks Dean, and yes I do agree with you about it being a complication. I was always under the assumption if I rooted a phone that I needed to also use some sort of recovery god forbid I had an issue with the phone not booting up or something so I could possibly fix the issue, make a backup/install a backup etc. Maybe I will ****can it if someone will tell me how to do so without losing my data or root.

Anthony-m said:
Thanks Dean, and yes I do agree with you about it being a complication. I was always under the assumption if I rooted a phone that I needed to also use some sort of recovery god forbid I had an issue with the phone not booting up or something so I could possibly fix the issue, make a backup/install a backup etc. Maybe I will ****can it if someone will tell me how to do so without losing my data or root.
Click to expand...
Click to collapse
FYI I just froze the update using Titanium backup pro and my problem is solved for now..

What Steps Do I Take To Update From 2.19.40.20?

So I've stayed at 2.19.40.20 because I wanted to wait to see if a better way to unlock the bootloader would be found, but I've given up and unlocked my bootloader (the unoffical way).
I want to get up to speed and update to the latest OTA.
Can I just flash the latest one or do I need to download every one til the newest update and sideload them individually?
If I have to do each one can I just load them one after the other, or do I need to reboot the phone and let it fully load to the OS for every update?

I did side load the latest one when I was coming from the 18 something that came with my phone. Loading the full 1.1gig firmware did the trick.

So just for clarification, to take me from 2.19.40.20 to 2.20.40.139 I should just flash the latest Stock ROM from the ASUS site?
DiGecko said:
I did side load the latest one when I was coming from the 18 something that came with my phone. Loading the full 1.1gig firmware did the trick.
Click to expand...
Click to collapse

Azdinflash said:
So just for clarification, to take me from 2.19.40.20 to 2.20.40.139 I should just flash the latest Stock ROM from the ASUS site?
Click to expand...
Click to collapse
Yes that should do it.

I was seriously dreading having to update, but this shows that my worries were unfounded, thanks!
I don't need to unroot as I'm flashing the whole rom, right?
The_wolf88 said:
Yes that should do it.
Click to expand...
Click to collapse

Azdinflash said:
I was seriously dreading having to update, but this shows that my worries were unfounded, thanks!
I don't need to unroot as I'm flashing the whole rom, right?
Click to expand...
Click to collapse
You need to unroot and make sure you are sideloading the whole 1.1 gig one.

DiGecko said:
You need to unroot and make sure you are sideloading the whole 1.1 gig one.
Click to expand...
Click to collapse
Does unrooting include removing Xposed?

Yes, and don't try to install it after you get to 139 firmware, as far as I know it still causes bootloop.

Wait, if I flash the 1.1 gig stock ROM, do I lose everything in the internal memory?
DiGecko said:
Yes, and don't try to install it after you get to 139 firmware, as far as I know it still causes bootloop.
Click to expand...
Click to collapse
I did a little digging, and it seems that the bootloop was fixed a few days ago:
http://forum.xda-developers.com/zenfone2/general/guide-to-install-xposed-installer-t3116476/page26
J M L said:
There's a new Xposed out, v78, which claims to fix a bootloop on 5.0 roms due to a security fix. I haven't tried it yet because I'm running a backup. Here is the thread and changelog.
We want the sdk21-x86 version.
Installed with no problem in TWRP with the flash able zip. Took a few minutes to boot, but seems to be working.
Click to expand...
Click to collapse

Good to know. No, you would not loose anything, at least I did not. Everything migrated over without any issues.

So I've gotten through sideloading the current version with no hiccups. Booted into system fine, it's the right version in the About section, and my internal memory came through intact.
I've flashed TWRP, and booted into it to install SuperSU when I got this message: "TWRP may have detected an unmodified system partition"
It explains that I can keep it as read only and make it easier to take official updates, but then TWRP will not be able to stop the stock ROM from replacing it and will not offer to root my device.
Should I keep it "Read Only" or should I allow the modification?

Guide [Simple]: OTA update with rooted and unlocked

Hi,
This guide is based in my first post about how to do it with the Moto G4: http://forum.xda-developers.com/moto-g4/how-to/guide-simple-ota-update-rooted-unlocked-t3510126
(Read it for full info).
Then, here the updated info for the Moto G5+:
1) If you are in NPN25.137-33 and like to apply the last OTA, but you have rooted and/or flashed a custom recovery (TWRP) + custom kernel, then you can.
2) Requirements: original SYSTEM and BOOT partitions. If you have flashed another version, then restore the originals. You can use any backups from you, or you can download from here: http://drive.google.com/open?id=0B6-Tz_7kDyxsZnVNa0pldnhndG8
(Thank you to GtrCraft: http://forum.xda-developers.com/showpost.php?p=72387571&postcount=15)
3) To apply the OTA download this ZIP and install it from the TWRP recovery (it's not required to have the TWRP flashed, you can start it from the fastboot util): http://www.sendspace.com/file/7w75rw
This file is the original OTA (shared by the user olive23) and patched by me to remove the check for the fingerprint of the running firmware. Then it can run over the TWRP.
Warning: Don't install this OTA if you don't have the exact version of the required firmware.
4) After install the OTA, reboot and check the new version. At that point the ROM isn't rooted. Then, you need to re-root.
That's all!

Tried flashing and it fails.

You need stock recovery to flash OTA's

GtrCraft said:
You need stock recovery to flash OTA's
Click to expand...
Click to collapse
Isn't that the point of this post? He said he patched the OTA update so it could be flashed with TWRP.
3) To apply the OTA download this ZIP and install it from the TWRP recovery (it's not required to have the TWRP flashed, you can start it from the fastboot util): http://www.sendspace.com/file/7w75rw
This file is the original OTA (shared by the user olive23) and patched by me to remove the check for the fingerprint of the running firmware. Then it can run over the TWRP.
Click to expand...
Click to collapse

bvsbutthd101 said:
Isn't that the point of this post? He said he patched the OTA update so it could be flashed with TWRP.
Click to expand...
Click to collapse
Well the OTA isn't meant for reteu firmware. So that will bring problems with it

bvsbutthd101 said:
Tried flashing and it fails.
Click to expand...
Click to collapse
Because isn't for your device OR you have modified SYSTEM or BOOT.

GtrCraft said:
You need stock recovery to flash OTA's
Click to expand...
Click to collapse
FALSE!
GtrCraft said:
Well the OTA isn't meant for reteu firmware. So that will bring problems with it
Click to expand...
Click to collapse
TRUE! :silly:

manos78 said:
Because isn't for your device OR you have modified SYSTEM or BOOT.
Click to expand...
Click to collapse
Installing TWRP and rooting doesn't change the SYSTEM or BOOT right? Must just not be for my device then. I have the US 4gb model (XT1687)

bvsbutthd101 said:
Must just not be for my device then. I have the US 4gb model (XT1687)
Click to expand...
Click to collapse
Probably. This OTA is from user "olive23".
I don't have (still) received any OTA in my XT1685 (EU 3/32).

manos78 said:
Probably. This OTA is from user "olive23".
I don't have (still) received any OTA in my XT1685 (EU 3/32).
Click to expand...
Click to collapse
Here's the OTA for the US 4gb model if you're interested. :good:
https://drive.google.com/open?id=0BxqNotAWlwLUQ1Fzcjc2YXd4QzA

bvsbutthd101 said:
Installing TWRP and rooting doesn't change the SYSTEM or BOOT right? Must just not be for my device then. I have the US 4gb model (XT1687)
Click to expand...
Click to collapse
I have the same US model and this is supposed to be for it but it didn't work for me either, got errors during flash of OTA zip in TWRP that various partitions weren't accessible &/or verifiable. Even tried it a second time after a full restore to stock and had similar errors. I restored SYSTEM too (not sure that our rooting process works for systemless yet, meaning it would change SYSTEM), so that wasn't the problem in my case. Restored stock again and will wait to see if I get OTA normally.
bvsbutthd101 said:
Here's the OTA for the US 4gb model if you're interested. :good:
https://drive.google.com/open?id=0BxqNotAWlwLUQ1Fzcjc2YXd4QzA
Click to expand...
Click to collapse
So did you get this OTA normally as a system update, indicating that we should be receiving it now?

Dahenjo said:
I have the same US model and this is supposed to be for it but it didn't work for me either, got errors during flash of OTA zip in TWRP that various partitions weren't accessible &/or verifiable. Even tried it a second time after a full restore to stock and had similar errors. I restored SYSTEM too (not sure that our rooting process works for systemless yet, meaning it would change SYSTEM), so that wasn't the problem in my case. Restored stock again and will wait to see if I get OTA normally.
So did you get this OTA normally as a system update, indicating that we should be receiving it now?
Click to expand...
Click to collapse
I got the update weeks ago. I've been postponing until someone makes it's flashable. I ripped it from my phone when I got it so yes, it's from my phone.

bvsbutthd101 said:
I got the update weeks ago. I've been postponing until someone makes it's flashable. I ripped it from my phone when I got it so yes, it's from my phone.
Click to expand...
Click to collapse
Thanks. I wonder why I haven't gotten anything and had phone since it came out on 3/31. I'm on NPN25.137-33 with a 4GB XT1687 from Amazon ($299 full-price without ads) on AT&T if carrier matters. Rooted or not we should still get the notifications as you have.

Dahenjo said:
Thanks. I wonder why I haven't gotten anything and had phone since it came out on 3/31. I'm on NPN25.137-33 with a 4GB XT1687 from Amazon ($299 full-price without ads) on AT&T if carrier matters. Rooted or not we should still get the notifications as you have.
Click to expand...
Click to collapse
Yeah I got mine the day it came out from amazon, using on Verizon.

Here is a flashable stock zip based on reteu firmware:
https://drive.google.com/open?id=0B6-Tz_7kDyxsU2NlTERsSzZsalk

U have*67 files??

Same Here
US variant XT1687 4/64GB on Sprint but no OTA notification. Maybe I should just wait another week before flashing this. Not sure if there is something in the SIM the server notices and stops updates on some carriers. But maybe the SIM is how they decide, not sure what else they could go by other than IP to detect the carrier.
bvsbutthd101 said:
Yeah I got mine the day it came out from amazon, using on Verizon.
Click to expand...
Click to collapse

I also have XT1687 4/64G US on 25.137-33 + root & TWRP, and no OTA notification.
So, is there a way to go to -67 (flash over TWRP, restore back to -15 stock)?
I could not understand the right answer from all the thread on the subject.

Sorry for this noob question: I have just rooted a brand new phone. After the first login the OTA warning popped out so I downloaded it. When finished I got a loop on the recovery; I fastbooted boot and got my phone working again ... what do I have to do? Thanks.

Hi,
My upgraded guide: http://forum.xda-developers.com/g5-plus/how-to/guide-complex-ota-update-magisk-rooted-t3688175

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.