Develop Bugs

[Q] Unsuccessful 4.4.2 Update on N72013

I just updated my NEXUS 7 2013 from 4.4 to 4.4.2 but after restarting, the Android version in settings still says 4.4.
I checked for updates again in System Updates menu but my device says the system is up to date.
My device is Nexus 7 2013 32G rooted under TWRP 2.6.3.1 recovery on Super SU root.
I previously applied a patch from sfhub "boot-ts10-lock.img" but i flashed "boot-ts-unlock.img" before updating to accept the whole update from 4.4.2 (in case a Touchscreen fix is included.).
I also tried updating manually using TWRP zip update but it failed.
here's the part of the prompt during TWRP update:
Verifying current system...
"/system/bin/debuggerd" has unexpected contents.
E: Error executing updater binary in zip '/sdcard/Dow...
Hope someone can help me find a solution for this. Thanks!

Step one : Go to the right forum.

Wrong subforum, but basically it's because you're rooted. The easiest solution is to just flash the system.img file from the factory image via fastboot and you should be good to go :good:

Thread moved to the right sub-forum and to the right section...

arviverona said:
I just updated my NEXUS 7 2013 from 4.4 to 4.4.2 but after restarting, the Android version in settings still says 4.4.
I checked for updates again in System Updates menu but my device says the system is up to date.
My device is Nexus 7 2013 32G rooted under TWRP 2.6.3.1 recovery on Super SU root.
I previously applied a patch from sfhub "boot-ts10-lock.img" but i flashed "boot-ts-unlock.img" before updating to accept the whole update from 4.4.2 (in case a Touchscreen fix is included.).
I also tried updating manually using TWRP zip update but it failed.
here's the part of the prompt during TWRP update:
Verifying current system...
"/system/bin/debuggerd" has unexpected contents.
E: Error executing updater binary in zip '/sdcard/Dow...
Hope someone can help me find a solution for this. Thanks!
Click to expand...
Click to collapse
ota updates only work on devices that are not modified i.e. patched but you can still be rooted (aosp browser, mods to system will bork any ota). if you do not know how to reverse the patch/mod you applied to you device you need to reflash a stock version of the system (search for stock images) then apply the ota.

OP: Uninstall stickmount (doing so will copy back the stock debuggerd), and try the OTA again.

Thanks guys!
I tried uninstalling the STICKMOUNT app but still update wont install OTA or manual method. Thanks anyway.
I guess i have to flash stock ROM.
Should i just use UNROOT setting in the Super SU menu rather than flashing stock ROM? i use stock rom and rooted it with SUPER SU.
Thanks,

arviverona said:
I tried uninstalling the STICKMOUNT app but still update wont install OTA or manual method. Thanks anyway.
I guess i have to flash stock ROM.
Should i just use UNROOT setting in the Super SU menu rather than flashing stock ROM? i use stock rom and rooted it with SUPER SU.
Thanks,
Click to expand...
Click to collapse
It's not root stopping the OTA. So unrooting is a waste of time. You can just put back the debuggerd file manually (using TWRP). You can find it in post 1 here:
http://forum.xda-developers.com/showthread.php?t=2534698
Direct link: http://forum.xda-developers.com/attachment.php?attachmentid=2403508&d=1384921832
...also make sure you have the latest TWRP. You will likely lose root once you do finally update, so be prepared to reroot using the latest SuperSU.

mdamaged said:
It's not root stopping the OTA. So unrooting is a waste of time. You can just put back the debuggerd file manually (using TWRP). You can find it in post 1 here:
http://forum.xda-developers.com/showthread.php?t=2534698
Direct link: http://forum.xda-developers.com/attachment.php?attachmentid=2403508&d=1384921832
...also make sure you have the latest TWRP. You will likely lose root once you do finally update, so be prepared to reroot using the latest SuperSU.
Click to expand...
Click to collapse
Is the debuggered flash work for DEB as well? I still havent taken the update to 4.4.2, its showing on my scree to touch and update. (rooted and unlocked), but if i plan to in the future, I will need that debuggered flash, newest SuperSU and newest TWRP (which i have now)

Duffmantp said:
Is the debuggered flash work for DEB as well? I still havent taken the update to 4.4.2, its showing on my scree to touch and update. (rooted and unlocked), but if i plan to in the future, I will need that debuggered flash, newest SuperSU and newest TWRP (which i have now)
Click to expand...
Click to collapse
It should work, worst case scenario, it will just complain ""/system/bin/debuggerd" has unexpected contents" ...stickmount made a copy of your debuggerd, it should still be in system/bin/debuggerd.backup, so you could restore that one or you could do a md5sum of that system/bin/debuggerd.backup with the one I linked and see if the md5sum matches, if it does, then the one I linked will work, if not, then make a flashable zip with the one that's in system/bin/debuggerd.backup and flash that one.
Just to reiterate what I stated earlier, if that debuggerd.backup is the correct one, then simply uninstalling stickmount SHOULD restore it without flashing, it worked for me going from 4.3 to 4.4.2. I verified this with md5sum before I took the OTA.
I can only postulate the reason it does not work for some is because the debuggerd.backup they have is from a older update, thereby the md5sum no longer checks out, so when they uninstall stickmount like I suggest, it's still the wrong debuggerd the update expects.

mdamaged said:
It should work, worst case scenario, it will just complain ""/system/bin/debuggerd" has unexpected contents" ...stickmount made a copy of your debuggerd, it should still be in system/bin/debuggerd.backup, so you could restore that one or you could do a md5sum of that system/bin/debuggerd.backup with the one I linked and see if the md5sum matches, if it does, then the one I linked will work, if not, then make a flashable zip with the one that's in system/bin/debuggerd.backup and flash that one.
Just to reiterate what I stated earlier, if that debuggerd.backup is the correct one, then simply uninstalling stickmount SHOULD restore it without flashing, it worked for me going from 4.3 to 4.4.2. I verified this with md5sum before I took the OTA.
I can only postulate the reason it does not work for some is because the debuggerd.backup they have is from a older update, thereby the md5sum no longer checks out, so when they uninstall stickmount like I suggest, it's still the wrong debuggerd the update expects.
Click to expand...
Click to collapse
Actually I dont have stickmount installed, if that makes a difference.

Duffmantp said:
Actually I dont have stickmount installed, if that makes a difference.
Click to expand...
Click to collapse
Well then your debuggerd should be stock, and this is all just academic. If the update fails, it won't be due to the debuggerd (unless there is some other app I do not know about that messes with debuggerd and you have that installed).

Duffmantp said:
Actually I dont have stickmount installed, if that makes a difference.
Click to expand...
Click to collapse
Xposed Framework installed? I know it modifies something in system/bin but can't remember exactly what it was.

wantabe said:
Xposed Framework installed? I know it modifies something in system/bin but can't remember exactly what it was.
Click to expand...
Click to collapse
That would be system/bin/app_process, using the uninstall feature in the xposed app restores it.

mdamaged said:
That would be system/bin/app_process, using the uninstall feature in the xposed app restores it.
Click to expand...
Click to collapse
That's it!

Questions about the OP3

I got my OP3 1-2 weeks . before i had a S4 (rooted). I'm really happy with this phone but i got some questions and problems.
1. When i video call via skype the camera will freeze in 50sec. when I switch the camera to the back and front it's fixed for 50 sec again and same thing happening again....
2. Rooting the OP3 is it safe to do ? And does someone got a guide for it ? I saw allot off them but I don't know which one works for Oxygen 3.2.1. I got some rooting experience with the S4 but rooting op3 is kinda different.
3. When i got a rooted op3 without a custom rom. Do i still get updates via System updates in the settings ?
Sorry for my bad English and thanks for reading.

1. Don't know
2. Yes, https://forums.oneplus.net/threads/...nlock-bootloader-flash-twrp-root-nandroid-efs
3. No after rooting you won't get updates

J_Dutch said:
1. Don't know
2. Yes, https://forums.oneplus.net/threads/...nlock-bootloader-flash-twrp-root-nandroid-efs
3. No after rooting you won't get updates
Click to expand...
Click to collapse
3. Wrong, with systemless SuperSU and/or systemless Xposed you still get OTA updates.
Proof: Myself (have the 3.2.1. OTA Update ready to download with systemless SuperSU and systemless Xposed.

crysen said:
3. Wrong, with systemless SuperSU and/or systemless Xposed you still get OTA updates.
Proof: Myself (have the 3.2.1. OTA Update ready to download with systemless SuperSU and systemless Xposed.
Click to expand...
Click to collapse
Ok, didn't know that. How do you install that?

J_Dutch said:
Ok, didn't know that. How do you install that?
Click to expand...
Click to collapse
Via TWRP both.
Here you can find the systemless SuperSU https://forums.oneplus.net/threads/guide-oneplus-3-how-to-unlock-bootloader-flash-twrp-root-nandroid-efs-backup-and-more.448149/
And here is systemless Xposed: http://forum.xda-developers.com/xposed/unofficial-systemless-xposed-t3388268

crysen said:
Via TWRP both.
Here you can find the systemless SuperSU https://forums.oneplus.net/threads/...wrp-root-nandroid-efs-backup-and-more.448149/
And here is systemless Xposed: http://forum.xda-developers.com/xposed/unofficial-systemless-xposed-t3388268
Click to expand...
Click to collapse
Seriously? I've been told several times installing a custom recovery and OTA is a no go...
But thanks, I'm still stock but I don't know for how long. I'm still a flashaholic inside.

crysen said:
3. Wrong, with systemless SuperSU and/or systemless Xposed you still get OTA updates.
Proof: Myself (have the 3.2.1. OTA Update ready to download with systemless SuperSU and systemless Xposed.
Click to expand...
Click to collapse
You are right that you will get a prompt for upcoming OTA updates.
But they won't install because your kernel and system are not stock.
My device is also rooted systemless and I can confirm that you will get an error inside TWRP
when trying to install the OTA patches.
When rooted, regardless which way, it is always necessary to flash the full rom zip.
So in the end @J_Dutch was right to say that you won't get updates
because you will always have to manually flash the full rom.
On the other hand, when somebody only uses TWRP (for backups for example) without modifying the system and kernel at all,
OTAs will work just fine.

AcmE85 said:
You are right that you will get a prompt for upcoming OTA updates.
But they won't install because your kernel and system are not stock.
My device is also rooted systemless and I can confirm that you will get an error inside TWRP
when trying to install the OTA patches.
When rooted, regardless which way, it is always necessary to flash the full rom zip.
So in the end @J_Dutch was right to say that you won't get updates
because you will always have to manually flash the full rom.
Click to expand...
Click to collapse
Oh thanks, I didn't know that, I would've flashed it via normal OTA after work otherwise

How to chose the right version of SuperSU.zip for flashing?

I flashed TWRP on my ZE551ML (Z00A-WW-2.20.40.198) and wanted to root a clean stock rom. I have successfully done so before on the same device by installing "BETA-SuperSU-v2.67-20160121175247.zip" downloaded from the official Chainfire site. I thought it would be better to have the newest version, so this time I tried to install "SR1-SuperSU-v2.79-SR1-20161221223537" from the same source. However, after installing that file, the phone stayed in a bootloop for around 10 minutes.
1. Is it normal for it to take that long, or does that mean that the second file is incompatible with my phone?
2. Did I chose the wrong file, and should I have tried to install "BETA-SuperSU-v2.67-20160121175247.zip"?
3. Which zip should I install?
I have uninstalled again, and my phone boots. What I am asking about here is which file to install.

Fiksdal said:
I flashed TWRP on my ZE551ML (Z00A-WW-2.20.40.198) and wanted to root a clean stock rom. I have successfully done so before on the same device by installing "BETA-SuperSU-v2.67-20160121175247.zip" downloaded from the official Chainfire site. I thought it would be better to have the newest version, so this time I tried to install "SR1-SuperSU-v2.79-SR1-20161221223537" from the same source. However, after installing that file, the phone stayed in a bootloop for around 10 minutes.
1. Is it normal for it to take that long, or does that mean that the second file is incompatible with my phone?
2. Did I chose the wrong file, and should I have tried to install "BETA-SuperSU-v2.67-20160121175247.zip"?
3. Which zip should I install?
I have uninstalled again, and my phone boots. What I am asking about here is which file to install.
Click to expand...
Click to collapse
Use the zip that worked before , you might have to update ...binaries after ..is all
Why you don't update to M is beyond me , the N lineage ROM is back on track by dev jrior too

timbernot said:
Use the zip that worked before , you might have to update ...binaries after ..is all
Why you don't update to M is beyond me , the N lineage ROM is back on track by dev jrior too
Click to expand...
Click to collapse
Thanks!
I've tried M already, but my favorite Xposed modules didn't work.
Is Xposed working on N?

Fiksdal said:
Thanks!
I've tried M already, but my favorite Xposed modules didn't work.
Is Xposed working on N?
Click to expand...
Click to collapse
You said the same a month back but yet you are having trouble with root
What will you miss exactly ?
Security updates to me are far more important

timbernot said:
Use the zip that worked before , you might have to update ...binaries after ..is all
Why you don't update to M is beyond me , the N lineage ROM is back on track by dev jrior too
Click to expand...
Click to collapse
timbernot said:
You said the same a month back but yet you are having trouble with root
What will you miss exactly ?
Security updates to me are far more important
Click to expand...
Click to collapse
Root is working beautifully on L, I've already installed the same SuperSU. Xposed modules are really important to me. One of my favorite modules, NetworkSpeedIndicator, didn't work for me on M. So I'm sticking with L for now. If I can get all my Xposed modules to work on M or N then I will happily upgrade

Help With Root

I'm a little lost on Root for the Pixel XL. I am currently running unlocked with Screw'd ROM - 3.1.2-****ery-20170712-1454. This is a BETA, but has been running really smooth for the last 2 days.
Security Patch Level - July 5, 2017
Vendor - NJH47D
Last time I tried to apply root while running PureNexus the phone continued to boot loop and I had to eventually flashall.bat and start over.
1. What version of SuperSU should I be flashing? The latest and newest or is there other versions that work better?
2. What are the correct steps? Is wipe cache/dalvik necessary before? Do I need to install anything on the phone beforehand?
Boot to TWRP, Flash SuperSU, Reboot? Easy as that?
I see this version being talked about a lot - SR3-SuperSU-v2.79-SR320170114223742.zip, but it isn't the latest available that I can see. The SuperSU thread states to install the latest version and using google brings me to many versions of SuperSU.
Lastly, after rooting will apps like SnapChat work? If not how to you bypass this?

So I just found some information after searching more. Some of it is dated. I currently have twrp-pixel-installer-marlin-3.1.0-0RC2.zip version for TWRP installed.
Is RC1 needed for root, and with what SuperSU version. Or which combination of RC2 and SuperSU work together?

jws86 said:
So I just found some information after searching more. Some of it is dated. I currently have twrp-pixel-installer-marlin-3.1.0-0RC2.zip version for TWRP installed.
Is RC1 needed for root, and with what SuperSU version. Or which combination of RC2 and SuperSU work together?
Click to expand...
Click to collapse
When I was rooted I initially was using RC1, I think my supersu was V2.8? And no Snapchat, Pokemon go, and Android pay, etc, will not work. So a little work around for Snapchat, you need to log in first then flash supersu, or just go with magisk and enable magisk hide to make life easier.

sakumaxp said:
When I was rooted I initially was using RC1, I think my supersu was V2.8? And no Snapchat, Pokemon go, and Android pay, etc, will not work. So a little work around for Snapchat, you need to log in first then flash supersu, or just go with magisk and enable magisk hide to make life easier.
Click to expand...
Click to collapse
Is there a guide to Root with Magisk somewhere floating around?

jws86 said:
Is there a guide to Root with Magisk somewhere floating around?
Click to expand...
Click to collapse
I believe it's the same as when you flash supersu, don't quote me on that

sakumaxp said:
I believe it's the same as when you flash supersu, don't quote me on that
Click to expand...
Click to collapse
Yeah I found the guide. It seems I need to flash stock image first before. So Magisk gives you the ability to root first, then download apps such as snapchat and still login if you use magisk hide?

jws86 said:
Yeah I found the guide. It seems I need to flash stock image first before. So Magisk gives you the ability to root first, then download apps such as snapchat and still login if you use magisk hide?
Click to expand...
Click to collapse
Correct, downloading isn't a problem, but it'll just prevent you from logging in since supersu, trips safetynet

sakumaxp said:
Correct, downloading isn't a problem, but it'll just prevent you from logging in since supersu, trips safetynet
Click to expand...
Click to collapse
I read through this thread: https://forum.xda-developers.com/pixel-xl/how-to/guide-stock-7-1-2-root-safetynet-ok-t3617347
Seems pretty straightforward, however currently I have a ROM installed I'm really liking. To do this I would have to flash back to stock image, then go through the root process. My question would be after rooting, if I went to flash Screw'd again, doesn't it wipe everything and I would lose root again, then just have to flash it after the ROM?

jws86 said:
I read through this thread: https://forum.xda-developers.com/pixel-xl/how-to/guide-stock-7-1-2-root-safetynet-ok-t3617347
Seems pretty straightforward, however currently I have a ROM installed I'm really liking. To do this I would have to flash back to stock image, then go through the root process. My question would be after rooting, if I went to flash Screw'd again, doesn't it wipe everything and I would lose root again, then just have to flash it after the ROM?
Click to expand...
Click to collapse
Myself I've never been on screwd before, I would assume so, but in my experience the pixel XL is more complicated than my previous phones

If you just want root you shouldn't need to flash the stock image again. You would need to do that if you wanted to flash a custom kernel but not for root. You need to download the modified version of Magisk for the Pixel XL. The official version doesn't work on the Pixels. I'm not currently rooted as I went back to stock but I was using Magisk. At that time the latest version wasn't stable but it might be fixed now. You need to boot into fastboot TWRP, flash the Magisk zip, flash the TWRP zip and then boot up. After you are booted up you install the Magisk Manager app. The tricky thing is installing the right version of Magisk Manager that works properly with the unofficial build of Magisk that you are using. You can get more information in the Resurrection Remix rom thread which for some reason is the official place where the modified version of Magisk is hosted if you can't find good info about which combination of unofficial Magisk and Magisk Manager you should be using. Also when I used Magisk you needed to enable core only mode for it to pass Safety Net but that may no longer be the case. You should be able to find the most up to date info either in the thread you cited or the RR rom thread. Just remember that official builds of Magisk do not work on the Pixel. You need to stick with one of the unofficial builds.

jhs39 said:
If you just want root you shouldn't need to flash the stock image again. You would need to do that if you wanted to flash a custom kernel but not for root. You need to download the modified version of Magisk for the Pixel XL. The official version doesn't work on the Pixels. I'm not currently rooted as I went back to stock but I was using Magisk. At that time the latest version wasn't stable but it might be fixed now. You need to boot into fastboot TWRP, flash the Magisk zip, flash the TWRP zip and then boot up. After you are booted up you install the Magisk Manager app. The tricky thing is installing the right version of Magisk Manager that works properly with the unofficial build of Magisk that you are using. You can get more information in the Resurrection Remix rom thread which for some reason is the official place where the modified version of Magisk is hosted if you can't find good info about which combination of unofficial Magisk and Magisk Manager you should be using. Also when I used Magisk you needed to enable core only mode for it to pass Safety Net but that may no longer be the case. You should be able to find the most up to date info either in the thread you cited or the RR rom thread. Just remember that official builds of Magisk do not work on the Pixel. You need to stick with one of the unofficial builds.
Click to expand...
Click to collapse
I think I got which versions of magisk and magisk manager I need to use from the other thread I had posted earlier. This helps to clear some things up for me though. I have both the .apk and the zip on my phone now. Getting a bit of a charge and I guess I'll go ahead and try it.

It worked, I'm officially rooted .Thanks for the help!

jws86 said:
It worked, I'm officially rooted .Thanks for the help!
Click to expand...
Click to collapse
Cool.

Installing OTA update while rooted (Magisk) and with TWRP recovery

I'm on the stock ROM (Build number: OPNS27.76-12-22-3), rooted via Magisk and have the latest TWRP as my recovery. Say, an OTA update arrives (hopefully) in the future, could I just sideload it from my computer via adb? I know that downloading the file and installing it using the phone won't work as I'm on TWRP (it requires stock recovery). Erfan Abdi's website allows the download of the OTA zip from Moto's servers if one wants to sideload it via adb (https://erfanoabdi.000webhostapp.com/). If not, how can I apply the OTA update?

no you can't apply the ota with a custom recovery as you made changes on partitions that ota.zip check if has some changes and i believe twrp is not ready to aply ota in any way because every manufacture has a way to make changes by ota so its almost impossible to made a generic way to apply ota to all the devices that twrp suports

jst98 said:
no you can't apply the ota with a custom recovery as you made changes on partitions that ota.zip check if has some changes and i believe twrp is not ready to aply ota in any way because every manufacture has a way to make changes by ota so its almost impossible to made a generic way to apply ota to all the devices that twrp suports
Click to expand...
Click to collapse
So I should flash the stock recovery back and then sideload the OTA?

djdelarosa25 said:
So I should flash the stock recovery back and then sideload the OTA?
Click to expand...
Click to collapse
flash stock, take the ota's via ota, and then mod system. At least that's what I do. pita but it works. I back up with TBPro and copy backup to PC (ota clears internal storage) before I do that so rebuild is pretty quick.

my last smartphone is just uninstall magisk and flash stock recovery to aply ota, but i never tried this on moto z play, so you should do a clean install of stock rom first, because i can't say with sure if it's gonna work as my last devices stops update on marshmallow , and magisk that i used on this phone is older

jst98 said:
my last smartphone is just uninstall magisk and flash stock recovery to aply ota, but i never tried this on moto z play, so you should do a clean install of stock rom first, because i can't say with sure if it's gonna work as my last devices stops update on marshmallow , and magisk that i used on this phone is older
Click to expand...
Click to collapse
I have to flash stock to take ota. ymmv. Let me know if AUG is out.

I just did an uninstall latest magisk uninstall and pogo doesn't work, so it's not clean, so will need to flash stock.

KrisM22 said:
I just did an uninstall latest magisk uninstall and pogo doesn't work, so it's not clean, so will need to flash stock.
Click to expand...
Click to collapse
there some things that have be analised here, first when you unistall magisk, the safetynet verification is gonna fail, and pogo can broke, and pogo is especially case, the pogo app checks storage to see if has some folder related magisk, that in most cases are left there to backup. and the ota check partition if you change something ota fails too.
stock ota is horrible to install if you have some changes in the device, so in almost all case, especialy if don't have advanced knowledge about all android work, the recomended is reflash system in same version that you are, and after this update.

jst98 said:
there some things that have be analised here, first when you unistall magisk, the safetynet verification is gonna fail, and pogo can broke, and pogo is especially case, the pogo app checks storage to see if has some folder related magisk, that in most cases are left there to backup. and the ota check partition if you change something ota fails too.
stock ota is horrible to install if you have some changes in the device, so in almost all case, especialy if don't have advanced knowledge about all android work, the recomended is reflash system in same version that you are, and after this update.
Click to expand...
Click to collapse
a) right. what I said. uninstall magisk is dirty - it doesn't clean everything up..
b) I could suggest TBPro to back up your system. Then be sure to copy that backup to your PC because flashing the stock will wipe internal storage. Then flash stock. Then use TBPro to restore stuff. At least that's sortof what I do.

what i did to update to latest security patch:
- flash uninstall magisk zip
- flash stock recovery
- take official ota
- reflash f2fs fix and magisk

JonasVFC said:
what i did to update to latest security patch:
- flash uninstall magisk zip
- flash stock recovery
- take official ota
- reflash f2fs fix and magisk
Click to expand...
Click to collapse
what security date are you on? Thanks.

KrisM22 said:
what security date are you on? Thanks.
Click to expand...
Click to collapse
june

JonasVFC said:
june
Click to expand...
Click to collapse
Thanks. That's what I'm on. I was wondering if Aug was out...

KrisM22 said:
Thanks. That's what I'm on. I was wondering if Aug was out...
Click to expand...
Click to collapse
Damn, Motorola's taking so long again.

djdelarosa25 said:
Damn, Motorola's taking so long again.
Click to expand...
Click to collapse
and then there's Pie... Apparently with Treble. I think a lot of new stuff coming at us soon...
I think it's about time for me to do some serious playing and looked and i see that Alberto97 is working on 9 ... hmmmmmmm.

JonasVFC said:
what i did to update to latest security patch:
- flash uninstall magisk zip
- flash stock recovery
- take official ota
- reflash f2fs fix and magisk
Click to expand...
Click to collapse
August security patch is out so I tried these steps.
It didn't work. While I sideloaded the update through adb, it showed that the system was modified and that it was mounted as R/W 40 times, also showing the most recent date and time that it happened. Keep in mind, I flashed the Magisk and Xposed uninstallers and cleared Dalvik and cache before the attempt to sideload.
I just flashed the original June build (omitting the 'fastboot erase userdata' command to save myself from a potential pain in the ass) and then did I proceed to sideload the update via adb. After that, I flashed the latest TWRP and rooted using the latest Magisk (and f2fs fix as well). My data is intact (except for the root modifications and Magisk modules) but that is miles better than starting from scratch off a factory data reset.
I guess I answered my own question, then . You can't

KrisM22 said:
and then there's Pie... Apparently with Treble. I think a lot of new stuff coming at us soon...
I think it's about time for me to do some serious playing and looked and i see that Alberto97 is working on 9 ... hmmmmmmm.
Click to expand...
Click to collapse
lol we are done. nothing new will come to us (owners of z1 play)

JonasVFC said:
lol we are done. nothing new will come to us (owners of z1 play)
Click to expand...
Click to collapse
yeah, lol, I'm playing with Pie. - Nothing new... HAH! silly rabbit.

djdelarosa25 said:
While I sideloaded the update through adb, it showed that the system was modified and that it was mounted as R/W 40 times, also showing the most recent date and time that it happened.
Click to expand...
Click to collapse
Do you have an idea how to easily display if system is modified (when, how often etc.)? I'd like to know if OTA could succeed after restoring boot partition for some Moto X Play and Moto Z Play with installed Magisk.

tag68 said:
Do you have an idea how to easily display if system is modified (when, how often etc.)? I'd like to know if OTA could succeed after restoring boot partition for some Moto X Play and Moto Z Play with installed Magisk.
Click to expand...
Click to collapse
Nope, sorry. Though, I failed to mention that I did flash the original boot.img after encountering the error and tried again. You guessed it, it still failed. Maybe try flashing both boot and oem to see if it would work?