can we flash Oos through twrp? also can we flash Oos rom from custom rom? if so what are the instructions? thx in advance. yes i have a lot of questions lol
freddienuxx said:
can we flash Oos through twrp? also can we flash Oos rom from custom rom? if so what are the instructions? thx in advance. yes i have a lot of questions lol
Click to expand...
Click to collapse
I'm also curious about this. My current method is to just use the MSM tool whenever I want to go back to stock but it is definitely time consuming. As far as I know TWRP is still early in development and a lot of things that should normally work dont work perfectly
I have definitely flashed OOS through TWRP (from AA to BA, not a custom rom), but haven't had any issues since I did it. That being said I would assume the steps would be to flash, factory reset, then root etc.
Haunt3r said:
I have definitely flashed OOS through TWRP (from AA to BA, not a custom rom), but haven't had any issues since I did it. That being said I would assume the steps would be to flash, factory reset, then root etc.
Click to expand...
Click to collapse
hm that is great to hear, however, when I attempt to flash oos 11.2.7.7AA (from oos 11.2.4.4AA) I get an error saying that I am missing /system_ext, /product, and /odm partitions. did you do anything other than simply install oos via twrp, because I am not sure why I am getting this error
thirtythr33 said:
hm that is great to hear, however, when I attempt to flash oos 11.2.7.7AA (from oos 11.2.4.4AA) I get an error saying that I am missing /system_ext, /product, and /odm partitions. did you do anything other than simply install oos via twrp, because I am not sure why I am getting this error
Click to expand...
Click to collapse
To my knowledge you cannot flash from 2.4.4AA to 2.7.7AA because it is an incremental update, at least through twrp. (I've never flashed anything but full roms via twrp). I actually fully switched to the EU firmware from the Global firmware because of the global version seemingly going fully to OTA updates and not providing full ROMs like the EU version.
Haunt3r said:
To my knowledge you cannot flash from 2.4.4AA to 2.7.7AA because it is an incremental update, at least through twrp. (I've never flashed anything but full roms via twrp). I actually fully switched to the EU firmware from the Global firmware because of the global version seemingly going fully to OTA updates and not providing full ROMs like the EU version.
Click to expand...
Click to collapse
no you are right, but I have the full update via oxygen updater, so these errors of missing partitions are extremely frustrating.
thirtythr33 said:
no you are right, but I have the full update via oxygen updater, so these errors of missing partitions are extremely frustrating.
Click to expand...
Click to collapse
there is no "full" update for 7.7aa it's solely an OTA
Haunt3r said:
there is no "full" update for 7.7aa it's solely an OTA
Click to expand...
Click to collapse
yeah man there is, came out June 28th, check oxygen updater or oneplus software download.
lol either way I can't flash it so fml
Haunt3r said:
there is no "full" update for 7.7aa it's solely an OTA
Click to expand...
Click to collapse
Yes there is, it came out a few days ago about 3gb's on OnePlus website...
Ah ****. Had no idea. Might flash back to aa if they're releasing full updates. Only reason I switched to eu was that reason. Definitely weird you're running into issues with it though
Haunt3r said:
Ah ****. Had no idea. Might flash back to aa if they're releasing full updates. Only reason I switched to eu was that reason. Definitely weird you're running into issues with it though
Click to expand...
Click to collapse
yeah man we have to wait insane long for AA full updates. yeah my issue is very frustrating and I've tried everything short of msm, I just don't see how it is possible that twrp reports I am missing those partitions yet my phone boots, but slot B is f'd, and I can't flash full AA update either through twrp or local upgrade.
Okay so if we do flash the full ota through recovery what's the correct process on this to keep twrp and magisk without needing a PC to push the recovery and root back onto the device?
Related
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?
My op3 is running on cm14.1 jgcaap and I was planning to go back to OOs. I want to flash 3.2.8. Should I flash through twrp or adb side load ?
MM MaD said:
My op3 is running on cm14.1 jgcaap and I was planning to go back to OOs. I want to flash 3.2.8. Should I flash through twrp or adb side load ?
Click to expand...
Click to collapse
You can do either but ensure two things for avoiding a possible bootloop. One is the TWRP and the other is wiping all except internal storage before flashing the ROM.
You should have the modified TWRP 3.0.2-23.
Wipe, flash ROM and flash TWRP before booting as the existing TWRP is likely to be overwritten by the stock recovery. Speaking from experience!
Though I was going from 3.2.7 to 3.2.8, TWRP was overwritten which I found only after booting and when I tried to get back into recovery.
Hi. what's the difference between the official and modded twrp? And is it better to have which one? Thanks
jfodra said:
Hi. what's the difference between the official and modded twrp? And is it better to have which one? Thanks
Click to expand...
Click to collapse
The reason of the existence of the modified TWRP is the inability of the original one to deal with the OOS community builds. The modified version is capable of flashing these builds.
Some older versions of recoveries have problems flashing some newer android version so you should always use the newest TWRP release out there and since the original release is a little bit outdated, the modified one is the better choice if you want to use Nougat
If you want to stay with Marshmallow then the original TWRP release would also do the trick for you (I use the original one too)
lekronop said:
The reason of the existence of the modified TWRP is the inability of the original one to deal with the OOS community builds. The modified version is capable of flashing these builds.
Some older versions of recoveries have problems flashing some newer android version so you should always use the newest TWRP release out there and since the original release is a little bit outdated, the modified one is the better choice if you want to use Nougat
If you want to stay with Marshmallow then the original TWRP release would also do the trick for you (I use the original one too)
Click to expand...
Click to collapse
Ooohh. If i flashed the modified one, i could still be able to flash the official oos builds? I'm going to use the toolkit provided and it seems that uses the modified twrp one.
jfodra said:
Ooohh. If i flashed the modified one, i could still be able to flash the official oos builds? I'm going to use the toolkit provided and it seems that uses the modified twrp one.
Click to expand...
Click to collapse
Yes this is no problem, you can flash the older builds with the modified twrp, so no worries.
lekronop said:
Yes this is no problem, you can flash the older builds with the modified twrp, so no worries.
Click to expand...
Click to collapse
Oh okay. Thanks a lot for the clarifications.
jfodra said:
Oh okay. Thanks a lot for the clarifications.
Click to expand...
Click to collapse
No problem, but even if the modified one couldn't handle older android versions then you can always flash another twrp which works for your desired task. So if you have twrp 3.0.2-23 installed you can go back to 3.0.2-1 or even lower without any problems
lekronop said:
No problem, but even if the modified one couldn't handle older android versions then you can always flash another twrp which works for your desired task. So if you have twrp 3.0.2-23 installed you can go back to 3.0.2-1 or even lower without any problems
Click to expand...
Click to collapse
Oh. Okay. Just a question though, does unlocking the bootloader also wipes the files in the phone such as the images and music?
jfodra said:
Oh. Okay. Just a question though, does unlocking the bootloader also wipes the files in the phone such as the images and music?
Click to expand...
Click to collapse
Yes it does.. That's the reason I unlock the bootloader as soon as I get a new device
i was on freedom os . i am back on stock oxygen os but i have 2 issues.
1) when i got an update to 3.2.7 it showed in german that there is an update even though the language i chose was english
2) The boot animation shows the freedom os splash screen and then the boots into stock. Ihave got the boot animation of stock os but need instructions on how to flash the zip.
Can someone throw light on the above 2 issues?
Just read about details about HUAWEI's new stock recovery called eRecovery. It seems users can no longer roll back and forth between stock ROMs, can only roll back to certain available versions.
Always keep your ROM latest: by using eRecovery, HUAWEI will no longer provide individual update.app file for manual update via SD. If EMUI system become unusable, eRecovery can help to update to latest Stock ROM to recover, during this process, user data may be wiped (like a full wipe in TWRP).
What if I want to downgrade?
If during the recovery process, eRecovery still can detect an earlier version of EMUI than your current version, then you can flash it, as a downgrade.
If during the recovery process, eRecovery detects the same version of EMUI as current one, then you have to flash it.
nice info...liked your signature as well buddy :good:
Be aware, i (and other members too) never saw this method working fine. Someone can say the inverse?
RedSkull23 said:
Be aware, i (and other members too) never saw this method working fine. Someone can say the inverse?
Click to expand...
Click to collapse
Old news mate. May be it was working on MM
shashank1320 said:
Old news mate. May be it was working on MM
Click to expand...
Click to collapse
Ouch, didn't noticed OP date. But, if Huawei removed firmwares from their site, where this recovery would obtain files so? Better to remain on fully safe methods like TWRP backups
RedSkull23 said:
Ouch, didn't noticed OP date. But, if Huawei removed firmwares from their site, where this recovery would obtain files so? Better to remain on fully safe methods like TWRP backups
Click to expand...
Click to collapse
TWRP back-up is always best when messed up.
Seeing all over the section people messing up and then want to rollback but with no file
shashank1320 said:
TWRP back-up is always best when messed up.
Seeing all over the section people messing up and then want to rollback but with no file
Click to expand...
Click to collapse
To me it is the first thing that someone should do as installed a custom recovery
RedSkull23 said:
To me it is the first thing that someone should do as installed a custom recovery
Click to expand...
Click to collapse
Yup but many are not following these things and messing badly.
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
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?