Related
I flashed the following factory firmware image on my XT1541;
Retail Europe (2GB) - XT1541_OSPREY_RETEU_2GB_5.1.1_LPI23.72-33_cid7
from here and followed the steps on this page to do so.
I updated to MM through OTA, flashed TWRP from here through fastboot, booted in to TWRP and flashed SuperSU v.2.65 from here.
I then reboot the phone and it gets stuck on the white "unlocked bootloader" screen.
I've repeated this process twice now, same thing. :/
Any ideas?
EDIT: I tryed flashing factory 5.1.1 through fastboot again, to get the phone working. But now I can't even do that.
When I enter "fastboot flash partition gpt.bin" I get the following error;
(bootloader) Preflash validation failed
FAILED (remote failure)
If you have a twrp backup from marshmallow, restore system. Then flash superSU 2.62-3 from here http://download.chainfire.eu/751/SuperSU/BETA-SuperSU-v2.62-3-20151211162651.zip.
SuperSU 2.65 don't detect properly the need to install it in systemless mode and try to install in system. V.2.62 is only systemless.
If you don't have the system backup, I don't know how to revert the modifications made by v. 2.65, but it's possible.
Good luck.
coolizard said:
If you have a twrp backup from marshmallow, restore system. Then flash superSU 2.62-3 from here http://download.chainfire.eu/751/SuperSU/BETA-SuperSU-v2.62-3-20151211162651.zip.
SuperSU 2.65 don't detect properly the need to install it in systemless mode and try to install in system. V.2.62 is only systemless.
If you don't have the system backup, I don't know how to revert the modifications made by v. 2.65, but it's possible.
Good luck.
Click to expand...
Click to collapse
Thank you. I did not have a backup, but I was able to flash factory 5.1.1 by skipping gpt.bin.
I then updated to MM through OTA, flashed TWRP and SuperSU v2.62-3.
Is there a reason why later versions of SuperSU do not install systemless on our phone and therefor cause the bootloop?
coolizard said:
If you have a twrp backup from marshmallow, restore system. Then flash superSU 2.62-3 from here http://download.chainfire.eu/751/SuperSU/BETA-SuperSU-v2.62-3-20151211162651.zip.
SuperSU 2.65 don't detect properly the need to install it in systemless mode and try to install in system. V.2.62 is only systemless.
If you don't have the system backup, I don't know how to revert the modifications made by v. 2.65, but it's possible.
Good luck.
Click to expand...
Click to collapse
I had a similar experience with v2.65. I know systemless root is experimental and all the current versions are beta. But I don't understand the reports from others indicating 2.65/2.65/2.67 work just fine on their G3. Is it possible that once 2.62-3 is installed, the later versions will flash properly?
Flash this supersu file , it will remove all latest binaries of supersu. And your phone will start.
https://download.chainfire.eu/204/SuperSU
Then flash supersu2.63 to root.
Astug said:
I flashed the following factory firmware image on my XT1541;
Retail Europe (2GB) - XT1541_OSPREY_RETEU_2GB_5.1.1_LPI23.72-33_cid7
I updated to MM through OTA
Click to expand...
Click to collapse
Where did you find OTA for XT1541_OSPREY_RETEU_2GB_5.1.1_LPI23.72-33_cid7? I've flashed this factory image but I haven't received OTA for this build and I haven't found an OTA file on Internet.
Could you share the OTA that you've used?
Osid said:
Where did you find OTA for XT1541_OSPREY_RETEU_2GB_5.1.1_LPI23.72-33_cid7? I've flashed this factory image but I haven't received OTA for this build and I haven't found an OTA file on Internet.
Could you share the OTA that you've used?
Click to expand...
Click to collapse
Here.
I received the OTA on my phone though.
Astug said:
Here.
I received the OTA on my phone though.
Click to expand...
Click to collapse
The thread linked contains only MY OTA for XT1541 2GB.
Are you really sure that tour source build was LPI23-72.33 ?
hi guys.....
i had recently unroot my moto g3 and install stock root to use my jio sim.
but i really miss the root access so, is there any way to to have root access.
when i flash supersu it will get stuck into bootlogo and will not proceed.
i waited for half an hr but no sign of booting up
anyone have a way to get root access to stock rom plzz help........
Just flash this super user zip file
http://forum.xda-developers.com/attachment.php?attachmentid=3655401&d=1456122222
is supersu installing systemless?
make sure to do this first in twrp terminal: "echo SYSTEMLESS=true>>/data/.supersu"
Sushilsingh said:
hi guys.....
i had recently unroot my moto g3 and install stock root to use my jio sim.
but i really miss the root access so, is there any way to to have root access.
when i flash supersu it will get stuck into bootlogo and will not proceed.
i waited for half an hr but no sign of booting up
anyone have a way to get root access to stock rom plzz help........
Click to expand...
Click to collapse
You already have an existing thread on this problem, and were told what needs to be done and where to go to get that information and additional assistance... Why are you not using the resources that were given to you previously? There is no magic fix, something was done incorrectly or you are using the incorrect files.
The answer and all support you will need are in this thread: http://forum.xda-developers.com/2015-moto-g/general/guide-how-to-root-moto-g-2015-model-t3448572
acejavelin said:
You already have an existing thread on this problem, and were told what needs to be done and where to go to get that information and additional assistance... Why are you not using the resources that were given to you previously? There is no magic fix, something was done incorrectly or you are using the incorrect files.
The answer and all support you will need are in this thread: http://forum.xda-developers.com/2015-moto-g/general/guide-how-to-root-moto-g-2015-model-t3448572
Click to expand...
Click to collapse
buddy i just install a clean XT1550_OSPREY_RETASIA_DS_2GB_6.0.1_MPI24.107-55_cid7_subsidy-DEFAULT_CFC.xml.zip
stock rom and twrp twrp-osprey-3.0.2-r1.img as you told.
and that command also
echo SYSTEMLESS=true>>/data/.supersu
cat /data/.supersu
it shows systemless=true
and installed latest supersu SR1-SuperSU-v2.78-SR1-20160915123031.zip from its official site
after that i wipe cache and dalvik.
i reboot it.
and its get reboot without supersu (root) permission.
what should i do?
Sushilsingh said:
buddy i just install a clean XT1550_OSPREY_RETASIA_DS_2GB_6.0.1_MPI24.107-55_cid7_subsidy-DEFAULT_CFC.xml.zip
stock rom and twrp twrp-osprey-3.0.2-r1.img as you told.
and that command also
echo SYSTEMLESS=true>>/data/.supersu
cat /data/.supersu
it shows systemless=true
and installed latest supersu SR1-SuperSU-v2.78-SR1-20160915123031.zip from its official site
after that i wipe cache and dalvik.
i reboot it.
and its get reboot without supersu (root) permission.
what should i do?
Click to expand...
Click to collapse
So you fastboot flashed the ROM and verified it booted successfully (an initial boot is essential prior to rooting, it sets up the RAM disk and other boot image things the first time), rebooted, flashed TWRP (3.0+) and backed up, did the echo command and flashed SuperSU 2.78 SR1 and it still failed?
Flash the 2.62-3 beta of SuperSU https://download.chainfire.eu/751/SuperSU/ it forces systemless install regardless of detected options. You can update normally in the Play Store, then update the binary in the app.
One of those two methods will work, if it doesn't then you have something more going on then meets the eye or there is a piece of information you are not giving us. This is a tested and working process on every single known Moto G 2015 variant.
BTW, clearing cache and dalvik is not required when rooting, you are just increasing the time it takes to boot for no reason.
acejavelin said:
So you fastboot flashed the ROM and verified it booted successfully (an initial boot is essential prior to rooting, it sets up the RAM disk and other boot image things the first time), rebooted, flashed TWRP (3.0+) and backed up, did the echo command and flashed SuperSU 2.78 SR1 and it still failed?
Flash the 2.62-3 beta of SuperSU https://download.chainfire.eu/751/SuperSU/ it forces systemless install regardless of detected options. You can update normally in the Play Store, then update the binary in the app.
One of those two methods will work, if it doesn't then you have something more going on then meets the eye or there is a piece of information you are not giving us. This is a tested and working process on every single known Moto G 2015 variant.
BTW, clearing cache and dalvik is not required when rooting, you are just increasing the time it takes to boot for no reason.
Click to expand...
Click to collapse
well, all the things get installed successfully but even the installation of supersu.zip file also
but it always reboot without any root access or supersu app
i try to install supersu from playstore but it wont help much
after that i tried BETA-SuperSU-v2.62-3-20151211162651.zip this version
and this version does the job
thanks buddy, i really appreciate your help.
acejavelin said:
So you fastboot flashed the ROM and verified it booted successfully (an initial boot is essential prior to rooting, it sets up the RAM disk and other boot image things the first time), rebooted, flashed TWRP (3.0+) and backed up, did the echo command and flashed SuperSU 2.78 SR1 and it still failed?
Flash the 2.62-3 beta of SuperSU https://download.chainfire.eu/751/SuperSU/ it forces systemless install regardless of detected options. You can update normally in the Play Store, then update the binary in the app.
One of those two methods will work, if it doesn't then you have something more going on then meets the eye or there is a piece of information you are not giving us. This is a tested and working process on every single known Moto G 2015 variant.
BTW, clearing cache and dalvik is not required when rooting, you are just increasing the time it takes to boot for no reason.
Click to expand...
Click to collapse
Thanks, thats works for me..! i tried 3 time until work
PD: (when you root, install recovery or unlock bootloader without enough time happens this kind of things)..
[Guide] XT1575 Update To NPH25.200-22 Nougat After Modifying Your System & Re-Root
THIS GUIDE IS NOW DEPRECATED. THERE IS NO NEED ANYMORE TO GO THROUGH THE UPDATING PROCESS AS THERE IS A FULL NOUGAT FACTORY IMAGE AVAILABLE (Build NPH25.200-22). FIRMWARE AVAILABLE HERE: https://forum.xda-developers.com/moto-x-style/general/xt1575-moto-x-pure-edition-factory-t3704142 BE SURE TO THANK @acejavelin FOR TRACKING DOWN THE FIRMWARE PACKAGE FOR US.
Notes:
-YOU ATTEMPT THIS AT YOUR OWN RISK IF YOU FLASHED ANY FIRMWARE PREVIOUSLY NOT FOR THE XT1575 US VERSION
-This guide will have 2 parts. 1 for those that kept their systems read only/systemless, and 1 for those that did not.
-Whether you live booted TWRP or Installed TWRP, if you chose to allow system modifications your OTA will likely fail (you'll need part 2).
-Restoring a TWRP backup will not work and will cause an OTA to fail due to having to allow system write access in TWRP - You Need Part 2.
-This guide assumes you have basic ADB knowledge and already know what fastboot is and how it works.
-Thanks to @gokart2 for the OTA and @acejavelin for the return to stock guides
Part 1: Those That Tweaked Systemlessly Currently On 24.49-18-16 (Will only work if you kept TWRP read only/used systemless root):
1: Disable & Remove systemless Xposed within Magisk Manager and all other Magisk modules. Reboot and wait for Art cache to rebuild.
2: Remove any adblock hosts within your adblock app if installed, or any other root level system altering apps like Greenify (don't worry, you'll get them back).
3: Remove Magisk by booting into TWRP and flashing the current Magisk Removal zip. Reboot.
4: For systemless SuperSu you need to consult their thread as I do not use it. (I'll update this if someone knows the correct process).
5: ADB reboot bootloader and fastboot flash the stock recovery. Latest MM recovery links at the bottom of this post. (rename file to recovery.img).
6: Move the OTA Blur_Version.24.231.16.clark_retus.retus.en.US.zip to the root of your internal sd card (NOT in a folder). File links at the bottom of the post. Thanks @gokart2
7: ADB reboot recovery, when "no command" is listed, hold power + tap volume up then release to access recovery options. Choose "apply update from phone storage". Choose the file and wait for the flash. It's a large update so be patient (about 10-20min). Choose reboot manually in recovery after flash succeeds. Enjoy Nougat!
8: For root you can go ahead and flash TWRP again or live boot TWRP (fastboot boot twrp.img) and then flash Magisk 14.0 from TWRP. Works perfectly.
Part 2: Those That Have Done Everything - TWRP Write Access, Custom Roms, On Older Firmware, Etc (XT1572 Build Flashers Do This At Their Own Risk):
1: Flash the latest full factory image available (24.49-18-8) available here: https://forum.xda-developers.com/mo...de-return-to-stock-relock-bootloader-t3489110. Thank @acejavelin for the thread while your at it. Follow the directions in that guide, it's well detailed and accurate - however read my notes just below first:
NOTES:
-Omit the "fastboot oem lock begin" & "fastboot oem lock" commands to remain bootloader unlocked.
-Omit the "fastboot erase userdata" command if you want to dirty flash and keep all of your data. I recommend clean, you can always root & restore each apps data with Titanium after the Playstore installs everything.
-The "fastboot oem fb_mode_set" instead of "fastboot oem lock begin" & "fastboot oem fb_mode_clear" instead of "fastboot oem lock" I've found to be unnecessary if staying unlocked. Your choice.
-The "fastboot flash partition gpt.bin" & "fastboot flash bootloader bootloader.img" commands will likely fail due to version mismatches. This is ok.
-The "fastboot flash modem NON-HLOS.bin" tends to fail too. For this, just run the command again until it succeeds.
2: After flashing 24.49-18-8 take the OTA to 24.49-18-16. Reboot. OTA zip provided below if you prefer to sideload.
3: Either install the 7.0 OTA the normal way via the update center or just side load it using the directions above. I recommend side loading due to the file size being very close to 1GB.
4: For root you can go ahead and flash TWRP again or live boot TWRP (fastboot boot twrp.img) and then flash Magisk 14.0 from TWRP. Works perfectly!
For Xposed, See My Guide Here: https://forum.xda-developers.com/showpost.php?p=74014516&postcount=96
Stock MM 24.49-18-16 Recovery: https://mega.nz/#!aZpC2RzQ!Fy3GTo_XYPjB1lwuHffCUUERuvnsyvON3kS8kMJ9Cm8
Stock MM 24.49-18-16 Recovery Mirror: https://drive.google.com/file/d/0BxxRfNko9QDKNS1NdnAyZVp6dVU/view?usp=sharing
24.49-18-8 OTA to 24.49-18-16: https://mega.nz/#!yZx2FLzR!cWfKIAYe5VyuadLI55UNHJvwWU98CXUi1g0DO1pDoKg
NPH25.200-22 OTA: https://mega.nz/#!HVhWWLxK!h-8G3vO3Sye_YwypyIJyWb2_79Ow34vNiDnMl2Q8uJg
NPH25.200-22 OTA Mirror: https://drive.google.com/file/d/0B3gPYUZ4nRLwOHJKQnNYczNEMHc/view?usp=sharing
MD5 for NPH25.200-22 OTA: 74d1a4b135200661cc4efd248f99ce33
Stock 7.0 NPH25.200-22 Recovery: https://mega.nz/#!TNoHQAjI!5U2w4p_G7pHlW6Mak7LqFR_PeWUDpSLc7S3OiUs_Qf8
Alrighty. I got back to stock 6.0 with the 18-16 update. I couldn't get the OTA via the system update, so I tried doing it via ADB. That threw up a "status 7 error". I then copied the file to my internal storage and selected update via SD Card in recovery. It hung on "Patching System Files" for a while, but in the end it moved on and worked fine. Thanks for the awesome guide!
Thread updated with downloads for the 24.49-18-8 OTA to 24.49-18-16 zip.
I exctracted the 7.0 Stock recovery to replace if you decide to flash TWRP and want to go back to the stock recovery for future updates (HAHAHA yeah right!). Download link in OP. The 7.0 Recovery is different than the MM recovery. They are not interchangeable. Don't flash the 7.0 recovery on MM.
Question... can those of us who are rooted, custom roms, with TWRP, not just flash a stock unrooted TWRP backup from here: https://forum.xda-developers.com/moto-x-style/development/pure-firmware-tuff-wip-t3224833
Then, flash the stock recovery like it says... and take the update? Isn't that easier than this method?
Bwangster12 said:
Question... can those of us who are rooted, custom roms, with TWRP, not just flash a stock unrooted TWRP backup from here: https://forum.xda-developers.com/moto-x-style/development/pure-firmware-tuff-wip-t3224833
Then, flash the stock recovery like it says... and take the update? Isn't that easier than this method?
Click to expand...
Click to collapse
It probably won't work. Once TWRP is given write access to your system (which is required to flash a full rom or restore a backup) any OTA's will fail. Plus any modem/bluetooth mismatches will cause a failure too. Fastboot flashing a stock image is really very easy & pretty much a guarantee that everything will work properly. However, if your able to get it to work, please let us know...though I don't think it will.
annoyingduck said:
It probably won't work. Once TWRP is given write access to your system (which is required to flash a full rom or restore a backup) any OTA's will fail. Plus any modem/bluetooth mismatches will cause a failure too. Fastboot flashing a stock image is really very easy & pretty much a guarantee that everything will work properly. However, if your able to get it to work, please let us know...though I don't think it will.
Click to expand...
Click to collapse
Once I do this, I can just reinstall TWRP and Magisk, backup the stock 7.0 and if I ever decided, just flash a custom rom later on?
hey thanks for the help on this one. I was so worried because I got stuck on th May security update OTA-wise.
question: I messed with the LatAm version of Nougat, so when I tried to re-lock the bootloader, it game the preflash error.
After this proper update flash, is there a way to run the bootloader CMD to just re-lock the bootloader?
Here's the recovery before the 7.0 one, just incase.. Was bored. Ok, I won't lie....didn't see u posted the 7.0 recovery....lol.:good::highfive:
Bwangster12 said:
Once I do this, I can just reinstall TWRP and Magisk, backup the stock 7.0 and if I ever decided, just flash a custom rom later on?
Click to expand...
Click to collapse
Yup. TWRP flashes and works, magisk v14 works, and so far systemless xposed api24 is working.
EsteBandido4444 said:
hey thanks for the help on this one. I was so worried because I got stuck on th May security update OTA-wise.
question: I messed with the LatAm version of Nougat, so when I tried to re-lock the bootloader, it game the preflash error.
After this proper update flash, is there a way to run the bootloader CMD to just re-lock the bootloader?
Click to expand...
Click to collapse
What is everyone's fascination with relocking the bootloader? You do not need to relock your bootloader. You cannot relock the bootloader unless all your system partitions match. Use my part 2 section. Read the notes, skip the bootloader lock commands. Leave your bootloader unlocked, get up and running on nougat, then you can issue the lock commands if you really want a locked bootloader.
How exactly do you flash the 24.49-18-16 OTA? I'm stuck at this part
EDIT nevermind didn't read lol
Amp699435 said:
How exactly do you flash the 24.49-18-16 OTA? I'm stuck at this part
Click to expand...
Click to collapse
Copy the file to the root of your internal storage. Reboot into recovery. Hold power = volume up & release to access menu options. Choose apply update from storage. Select the OTA.zip package and let it install. (Directions are clearly written in OP.)
Does it matter which version you're on? I'm currently on MPSH24.49-18-4 with the May 2016 security update.
GrandAdmiral said:
Does it matter which version you're on? I'm currently on MPSH24.49-18-4 with the May 2016 security update.
Click to expand...
Click to collapse
Part 1 implies that you are on MPSH24.49-18-16 (dec), for part 2 - no it doesn't matter. Go ahead and start with the full firmware available MPSH24.49-18-8 and follow the steps from there.
annoyingduck said:
Part 1 implies that you are on MPSH24.49-18-16 (dec), for part 2 - no it doesn't matter. Go ahead and start with the full firmware available MPSH24.49-18-8 and follow the steps from there.
Click to expand...
Click to collapse
Ok. Was going to have to follow option two anyway because of how I rooted...
Now I also take it that flashing Magisk is recommended, but optional?
GrandAdmiral said:
Ok. Was going to have to follow option two anyway because of how I rooted...
Now I also take it that flashing Magisk is recommended, but optional?
Click to expand...
Click to collapse
Root is completely up to you. It's noted so users know that TWRP/Root are working. My logic with any XDA thread is that your bootloader is unlocked and you want root, but that's me...
annoyingduck said:
Root is completely up to you. It's noted so users know that TWRP/Root are working. My logic with any XDA thread is that your bootloader is unlocked and you want root, but that's me...
Click to expand...
Click to collapse
Gotcha. I know I'm going to root again, but I've never used Magisk before so I wasn't sure of that piece.
annoyingduck said:
Part 1 implies that you are on MPSH24.49-18-16 (dec), for part 2 - no it doesn't matter. Go ahead and start with the full firmware available MPSH24.49-18-8 and follow the steps from there.
Click to expand...
Click to collapse
I am running Dirty Unicorns right now and when i looked up what I'm on in fastboot, it showed MPSH24.49-18-16. Would I just follow part 2 and use MPSH24.49-18-8 or something? I thought I had to use at least the version I'm on or newer.
GrandAdmiral said:
Does it matter which version you're on? I'm currently on MPSH24.49-18-4 with the May 2016 security update.[/QUOTE
Your issue is that TWRP has modified your
System, any restoring of the stock rom will fail to update. So yes, you'll need to go through part 2 and downgrade and work your way back up.
Click to expand...
Click to collapse
I downloaded the zip (it took a while).
Restored to stock like 3 different ways but still hit a road block. I went the adb sideload route but got status error 7 because my build fingerprint wasn't correct. I tried searching for the right build I need, but I'm not an expert and couldn't find the right set of files that I was sure I knew how to restore. I ended up restoring my AICP backup.
If somebody could PM me and give me a hand (messaging through Hangouts or something) that would be AWESOME!
I'm planning trying to snag an XL 2 pre-order next week, but until then the less headache the better! Plus stock Nougat looks better on a Swappa listing
Trying to sideload via recovery 24.49-18-16 but I keep getting "("unexpected contents:EMMC:/dev/block/bootdevice/by-name/boot...". I've also tried installing from the phone but the same error appears in recovery. Any ideas?
Unlocked, Magisk-rooted, TWRP 3.1.1 beta working. Updated from .010 to .018 to get rid of "System Update" notice that failed to install, but I had to "flash-all" factory image as I could NOT get .018 OTA image to sideload. Failed immediately.
Cannot sideload .011 (8.1) OTA image, tried with all versions of TWRP. Fails immediately.
And, TWRP 3.2 will both sideload and zip-install from 3.1.1 beta, but after reboot, I'm back to beta.
Please tell me what I'm missing: any help appreciated. TIA
You might try using flashfire to install the ota.zip image. It's worked for me on other rooted phones.
neuron617 said:
Unlocked, Magisk-rooted, TWRP 3.1.1 beta working. Updated from .010 to .018 to get rid of "System Update" notice that failed to install, but I had to "flash-all" factory image as I could NOT get .018 OTA image to sideload. Failed immediately.
Cannot sideload .011 (8.1) OTA image, tried with all versions of TWRP. Fails immediately.
And, TWRP 3.2 will both sideload and zip-install from 3.1.1 beta, but after reboot, I'm back to beta.
Please tell me what I'm missing: any help appreciated. TIA
Click to expand...
Click to collapse
- Uninstall Magisk to unroot
- Flash the system.img and boot.img from whatever version/factory image you're on to confirm you are stock (this should also uninstall twrp if you went with the install method over the temp boot)
- Then follow the instructions on Google's OTA page (download OTA, boot into Stock Android Recovery, hold power and press volume up, select Apply update from ADB to sideload OTA)
- Flash custom kernel if desired (via fastboot, I'm using Flash Kernel), temp boot twrp and sideload Magisk (14.3 worked for me with 8.1)
foosion said:
You might try using flashfire to install the ota.zip image. It's worked for me on other rooted phones.
Click to expand...
Click to collapse
Thanks; I'll check it out.
Ra6idr0y said:
- Uninstall Magisk to unroot
- Flash the system.img and boot.img from whatever version/factory image you're on to confirm you are stock (this should also uninstall twrp if you went with the install method over the temp boot)
- Then follow the instructions on Google's OTA page (download OTA, boot into Stock Android Recovery, hold power and press volume up, select Apply update from ADB to sideload OTA)
- Flash custom kernel if desired (via fastboot, I'm using Flash Kernel), temp boot twrp and sideload Magisk (14.3 worked for me with 8.1)
Click to expand...
Click to collapse
Thanks for confirming what I was coming to suspect: have to unroot and ditch TWRP to move ahead. I appreciate this.
What is point of "systemless" root, however, if you have to unroot to get OTA update?
neuron617 said:
Thanks for confirming what I was coming to suspect: have to unroot and ditch TWRP to move ahead. I appreciate this.
What is point of "systemless" root, however, if you have to unroot to get OTA update?
Click to expand...
Click to collapse
Systemless root shouldn't change anything on the system partition. All changes are made to the kernel. Note that when rooting with Magisk you provided a boot.img rather than the system.img. the suggestion to reflash the system image is to nuke any changes you may have made to it. An OTA will fall off you have done any tinkering.
Unrooting should be as simple as restoring the original boot image.
Sent from my Pixel 2 using Tapatalk
PiousInquisitor said:
Systemless root shouldn't change anything on the system partition. All changes are made to the kernel. Note that when rooting with Magisk you provided a boot.img rather than the system.img. the suggestion to reflash the system image is to nuke any changes you may have made to it. An OTA will fall off you have done any tinkering.
Unrooting should be as simple as restoring the original boot image.
Sent from my Pixel 2 using Tapatalk
Click to expand...
Click to collapse
Ahhh... I really appreciate that clarification.
Y'all are the best: @ foosion, @ Ra6idr0y, @PiousInquisitor
Many thanks and Happy Holidays!
Full steps on how to take OTA updates when rooted with Magisk, TWRP & Custom Kernel?
I tried to take the 5.1.6 OTA by using these steps: https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md but it didn't work properly.
Could someone give me a list of the full steps that will keep Magisk, TWRP and Blu Spark Kernel installed? When I did the steps above it kept Magisk after rebooting, but didn't keep the custom kernel, so I rebooted to recovery to reinstall the kernel. However it was replaced with OxygenOS Recovery and it automatically wiped my device.
There is no way for you to take OTA with twrp and kernel persisted.
You need to understand how update works. Apparently, the update replaces your boot partition and your kernel is exactly implemented in the boot partition.
The changes will get overwritten. Thus, you will need to reinstall the kernel by yourself.
And as what I just mentioned, there is no specific recovery partition on A/B partitioning method. When boot partition get overwritten, the twrp will also be replaced by the stock recovery.