Database Info

Android 6.0/EMUI 4.0 for Mediapad X2 | B209 updated | out of beta now

**************
Currently it seems there is no way to update incremental files in emui 4.0, unless you get it from huawei directly. Updater has no option of local update now. Some people told me that unzipping zip file and placing update.app from zip in dload folder and then pressing power+volup+volminus during boot, they are able to install update. Can someone confirm this.
Btw i have successflly updated these files as i got it from huawei direclty(my imei is on beta list)
***********
Update : 24th March
EMUI 4.0 is out of beta now. B209 is out, exepct to receive direct update from huawei soon. Meanwhile you are welcome to update from file i am sharing. You need to be on B208 to apply this update.
link : http://bit.do/B209zip
Whats new : quite stable.
----------------------------------------------------------------------------------------------------------------------------------
Update : 12th Mar
B205 to B208 update has come. This is again beta build. You need to be on B205 to upgrade using this zip. Process to goto B205 is written below. Rooting and other processes are all same.
link : http://1drv.ms/24W4VU2
----------------------------------------------------------------------------------------------------------------------------------
Update :4th Feb
Here is beta build for GEM 703L only.
You need to be on B112 to apply this update zip.
Process :
- Be sure you are on B112 and unrooted.
- reame the downloaded file to update.zip and place it in dload folder in sd card.
- Goto Updater > Menu > Local Update > apply update.
- thats it.
Whats new :
- Android 6.0 beta.
- Will update anything else if i come to know.
How to Root :
- Get SuperSu 2.67 from here : http://download.chainfire.eu/897/SuperSU/BETA-SuperSU-v2.67-20160121175247.zip
- Install twrp recovery. For process search this forum.
- Before installing supersu zip, in twrp go to Advanced and enter Terminal Command and type in "echo SYSTEMLESS=true>>/data/.supersu"
- This will force SuperSU to use systemless root which will patch the bootloader instead of the system and work root properly.( Thanks to ajsmsg78 for pointing out)
How to get back to 5.1 :
- After installing twrp, make sure you have any twrp installable rom on sd card.
- Goto twrp recovery and wipe system(must), data, cache.
- install twrp installable zip rom. reboot.
Note : This is beta build and may not be perfect. If you screw up your device, only you are responsible.
Download link : http://1drv.ms/1X52Vna
----------------------------------------------------------------------------------------------------------------------------------
Many of you would be aware 1 batch of beta(B202) is already released. I was not one of them to get the update. Hoping to be in the second list.
Meanwhile if anyone has got hold on the update file, please share it here.
Btw i am expecting to get in 1 week or so.

Reserved

OMG I love it already despite being a beta version. The display can be fully switched to a tablet experience without any bugs on icons. It is looking good already but I'm sure bugs on other elements (e.g. camera) will be fixed with each update.

Installing now.

Hmm......to install this and rom it, or not to install it yet. That is the question. I hope they don't encrypt the boot.img on Marshmallow on the X2. The Mate 8 ships with an encrpyted bootloader and although I have a rom for it there are a few major bugs I haven't been able to figure out how to fix yet. Someone let me know if TWRP works on this and I'll put together a ROM.

Is this reversible back to B112, just in case..??

hagba said:
Is this reversible back to B112, just in case..??
Click to expand...
Click to collapse
According to the Chinese forums it is. I'm upgrading my 702L to it now and gonna try and put out a rom for it.
---------- Post added at 02:59 AM ---------- Previous post was at 02:18 AM ----------
OK, TWRP 5.1.1 confirmed working with this. Root should be working as well.

ajsmsg78 said:
According to the Chinese forums it is. I'm upgrading my 702L to it now and gonna try and put out a rom for it.
Click to expand...
Click to collapse
twrp recovery is installed without problem. But when i tried to install supersu zip, boot loop started. I tried with SuperSu2.66 and 2.67(systemless root).
To go back to 5.1, chinese mentiones some method. But this is what i tried and works.
- After installing twrp, make sure you have any twrp installable rom on sd card.
- Goto twrp recovery and wipe system(must), data, cache.
- install twrp installable zip rom. reboot.
After this you can keep factory image of B112 in dload folder and press power, vol up and vol down together to install it.

bark1234 said:
twrp recovery is installed without problem. But when i tried to install supersu zip, boot loop started. I tried with SuperSu2.66 and 2.67(systemless root).
To go back to 5.1, chinese mentiones some method. But this is what i tried and works.
- After installing twrp, make sure you have any twrp installable rom on sd card.
- Goto twrp recovery and wipe system(must), data, cache.
- install twrp installable zip rom. reboot.
After this you can keep factory image of B112 in dload folder and press power, vol up and vol down together to install it.
Click to expand...
Click to collapse
Gotcha. Thanks. I'm gonna try and make a pre-rooted rom out of this and hopefully get root working properly. From watching SuperSU root my Mate 8 (works fine) and watching it root my X2 it seems like it's not rooting properly. The root process takes about 10 seconds more on my Mate 8. It's not patching the kernel like it's supposed to and defaulting to the old root method which causes a bootloop. Supposedly if we terminal command echo SYSTEMLESS=true in TWRP it will force the systemless root.

Great. right now i am back to 5.1 for the lack of root. if you can get ir rooted i will be back to 6.0

bark1234 said:
Great. right now i am back to 5.1 for the lack of root. if you can get ir rooted i will be back to 6.0
Click to expand...
Click to collapse
OK, got it working. In TWRP before you flash SuperSU 2.67 you have to go to Advanced and enter Terminal Command and type in echo SYSTEMLESS=true>>/data/.supersu
This will force SuperSU to use systemless root which will patch the bootloader instead of the system and work properly.

ajsmsg78 said:
Gotcha. Thanks. I'm gonna try and make a pre-rooted rom out of this and hopefully get root working properly. From watching SuperSU root my Mate 8 (works fine) and watching it root my X2 it seems like it's not rooting properly. The root process takes about 10 seconds more on my Mate 8. It's not patching the kernel like it's supposed to and defaulting to the old root method which causes a bootloop. Supposedly if we terminal command echo SYSTEMLESS=true in TWRP it will force the systemless root.
Click to expand...
Click to collapse
Ok,will wait for this one,please mention what is not working properly.

ajsmsg78 said:
OK, got it working. In TWRP before you flash SuperSU 2.67 you have to go to Advanced and enter Terminal Command and type in echo SYSTEMLESS=true>>/data/.supersu
This will force SuperSU to use systemless root which will patch the bootloader instead of the system and work properly. I'm gonna try incorporating the patched boot.img into my custom rom and see if I can get it to boot with root.
Click to expand...
Click to collapse
Ok so can you confirm if i follow above method in my 6.0 room it will root properly?
please confirm so that i will go ahead nd reinstall 6.0 beta

bark1234 said:
Ok so can you confirm if i follow above method in my 6.0 room it will root properly?
please confirm so that i will go ahead nd reinstall 6.0 beta
Click to expand...
Click to collapse
Yep. You'll see a difference in the rooting process after you enter that command. It will say it's patching the boot image when rooting. It will boot, then reboot once. Then boot right up. This is normal for the systemless root procedure. If I get this rom working, if you wanna try flashing it while still on B112 and let me know if it boots for you.
---------- Post added at 04:27 AM ---------- Previous post was at 04:21 AM ----------
The ROM i made boots but i have the same bugs as on my Mate 8. Wifi doesn't connect and the external SD says it's corrupt (it's really not) I think it's something in the installer-script.

Thanks man, I rooted successfully.

bark1234 said:
Thanks man, I rooted successfully.
Click to expand...
Click to collapse
No problem, thanks for sharing the beta.

bark1234 said:
Update :4th Feb
Here is beta build for GEM 703L only.
You need to be on B112 to apply this update zip.
Process :
- Be sure you are on B112 and unrooted.
- reame the downloaded file to update.zip and place it in dload folder in sd card.
- Goto Updater > Menu > Local Update > apply update.
- thats it.
.
Click to expand...
Click to collapse
Thanks! Prerequisite is to be on stock B112?

bark1234 said:
Update :4th Feb
How to get back to 5.1 :
- After installing twrp, make sure you have any twrp installable rom on sd card.
- Goto twrp recovery and wipe system(must), data, cache.
- install twrp installable zip rom. reboot.
.
Click to expand...
Click to collapse
submits TWRP backup also to go back to 5.1.1?

tbatliner said:
Thanks! Prerequisite is to be on stock B112?
Click to expand...
Click to collapse
yes

letschky said:
submits TWRP backup also to go back to 5.1.1?
Click to expand...
Click to collapse
Your question is not clear.

System Update with hidden Root

Hello guys, first Sry for my bad English...
I have an wired idea but I don't know it's Funktion or not because of that I quest you guys and hope that anybody have experience with these.
How anybody who use magisk know, you can hide your root to apps and system too, when I hide the root to system update then he only want to download an ~300 MB update (actually installed version: 1.5.6 because the problem in 1.5.7/8 (original os and no twrp installed)). Also it is possible to update my system at these way and I have root after the update or what can happen?
Your Patrick

Xyz00777 said:
Hello guys, first Sry for my bad English...
I have an wired idea but I don't know it's Funktion or not because of that I quest you guys and hope that anybody have experience with these.
How anybody who use magisk know, you can hide your root to apps and system too, when I hide the root to system update then he only want to download an ~300 MB update (actually installed version: 1.5.6 because the problem in 1.5.7/8 (original os and no twrp installed)). Also it is possible to update my system at these way and I have root after the update or what can happen?
Your Patrick
Click to expand...
Click to collapse
To keep root with an update, you need to flash the full update in TWRP, reflash TWRP, reboot recovery then reflash root. Otherwise, you will need to do the steps all over again every time you update to get root back.

mikex8593 said:
To keep root with an update, you need to flash the full update in TWRP, reflash TWRP, reboot recovery then reflash root. Otherwise, you will need to do the steps all over again every time you update to get root back.
Click to expand...
Click to collapse
Thanx
Thanks for the fast answer
Also what I have to do now is:
1. Download the actual OS
2. Change recovery with twrp
Reboot recover
3. Flash OS with twrp (first full clean?)
4. Flash twrp
5. Reboot to recovery and flash magisk
Did I lose at these way my data? Or did I do here an dirty flash? When yes what data recovery tool do you recommend? Titanium?
And after these, I can update my device per OTA updates and I don't lose my root?

Xyz00777 said:
Thanx
Thanks for the fast answer
Also what I have to do now is:
1. Download the actual OS
2. Change recovery with twrp
Reboot recover
3. Flash OS with twrp (first full clean?)
4. Flash twrp
5. Reboot to recovery and flash magisk
Did I lose at these way my data? Or did I do here an dirty flash? When yes what data recovery tool do you recommend? Titanium?
And after these, I can update my device per OTA updates and I don't lose my root?
Click to expand...
Click to collapse
You can install TWRP or you can just install the OTA and then just follow steps to root again the same you did before.

mikex8593 said:
You can install TWRP or you can just install the OTA and then just follow steps to root again the same you did before.
Click to expand...
Click to collapse
So what i done is:
downlaod OS
temp recovery with twrp
flash OS
start os (now warnigns or anything all okay)
temp recovery with twrp again
flash magisk
reboot system
and now i got the message that my system have an internal problem and i have to go to the developer.
What I did wrong?

Xyz00777 said:
So what i done is:
downlaod OS
temp recovery with twrp
flash OS
start os (now warnigns or anything all okay)
temp recovery with twrp again
flash magisk
reboot system
and now i got the message that my system have an internal problem and i have to go to the developer.
What I did wrong?
Click to expand...
Click to collapse
Flash magisk 16.4.

OTA after root

Simple question. Will I be able to do OTA updates if I root and install twrp? If yes, will I need to root and install twrp again after each update?

vaggosgr said:
Simple question. Will I be able to do OTA updates if I root and install twrp? If yes, will I need to root and install twrp again after each update?
Click to expand...
Click to collapse
Yes, you are able to use ota. (full roms must be flashed, os knows if you have root so it will download it.
Yes, updates will replace boot img with stock so you need to get twrp and root again. You have two options:
1. Download full rom zip (Funk has links for both stable and betas here on xda in the guides section)
2. Boot to recovery, flash full rom. (DO NOT REBOOT)
3. Flash twrp (use Blu spark latest, it always works)
4. Reboot to twrp, flash magisk.
Option two:
1. Install OTA from system, when it tells you install is complete, reboot to finish DON'T DO IT
2. Open magisk app, go to downloads and search for a/b twrp and install it ( there is only one module) after install is done DON'T REBOOT.
3. Go to main screen of magisk, press install, install, install to inactive slot (after ota) and after that install is complete, it's done.
Things to think about when updating: some Magisk modules may not be up to date when you update, this can cause bootloop. Some modules can cause system UI to force close. If you get this, use magisk uninstaller and see if you can reboot, if it works, then atleast you know it's modules.
There is also a possibility that substratum and swift installer can cause system UI force close aswell. Before install uninstall so you can install again after all is done.

whizeguy said:
Yes, you are able to use ota. (full roms must be flashed, os knows if you have root so it will download it.
Yes, updates will replace boot img with stock so you need to get twrp and root again. You have two options:
1. Download full rom zip (Funk has links for both stable and betas here on xda in the guides section)
2. Boot to recovery, flash full rom. (DO NOT REBOOT)
3. Flash twrp (use Blu spark latest, it always works)
4. Reboot to twrp, flash magisk.
Option two:
1. Install OTA from system, when it tells you install is complete, reboot to finish DON'T DO IT
2. Open magisk app, go to downloads and search for a/b twrp and install it ( there is only one module) after install is done DON'T REBOOT.
3. Go to main screen of magisk, press install, install, install to inactive slot (after ota) and after that install is complete, it's done.
Things to think about when updating: some Magisk modules may not be up to date when you update, this can cause bootloop. Some modules can cause system UI to force close. If you get this, use magisk uninstaller and see if you can reboot, if it works, then atleast you know it's modules.
There is also a possibility that substratum and swift installer can cause system UI force close aswell. Before install uninstall so you can install again after all is done.
Click to expand...
Click to collapse
Good write up.

vaggosgr said:
Simple question. Will I be able to do OTA updates if I root and install twrp? If yes, will I need to root and install twrp again after each update?
Click to expand...
Click to collapse
Simple reply.
No, you need full roms to flash manually.
And yes, you need to reflash TWRP after each update.
Ok filarako?
Sent from my ONEPLUS A6003 using Tapatalk

*system error* said:
Good write up.
Click to expand...
Click to collapse
Works like a charm :good:
used option 2
Thank you very much Whizeguy !

Losing TWRP and Magisk after update

I'm running stock ROM on unlocked bootloader with root through Magisk. I've been using TWRP, but changed over to Blu_spark TWRP recently.
Every time I update my OS Ota, I lose TWRP and Magisk. The Magisk app is installed, but the ROM is not rooted. If course, if I try to install patch the system so it's rooted through the Magisk app, it says that it can't unpack the file. If I reboot to recovery to install from there, I get the stock recovery, not TWRP.
I tried to re-install TWRP and Magisk once before, and borked my phone. I had to quote and start from scratch. I lost all data since I wasn't rooted and Titanium Backup would not run.
What is the proper way to get TWRP and Magisk back after an OTA update?

Flash them after you flash update zip. If you don't you will lose recovery and root every time. Gets overwritten by stock recovery. Normal behavior
Sent from my ONEPLUS A6003 using Tapatalk

So you're saying that instead of doing the OTA update, I should download the update from here, and manually update it ? Can I just install the update? I'm rooted, (well, I was) so the OTA will only download the full update. Is that required instead of the update?
I really have to do a full re-install for every update? That sucks. A lot.

Full reinstall? No. You just have to flash the full ROM. This doesn't mean, you'll loose all your data: Just TWRP, Magisk and (if you have it) your custom kernel. You only have to flash TWRP (or simply boot into it), Magisk and kernel (again: if you have it) after the update. Done.

MickyFoley said:
Full reinstall? No. You just have to flash the full ROM. This doesn't mean, you'll loose all your data: Just TWRP, Magisk and (if you have it) your custom kernel. You only have to flash TWRP (or simply boot into it), Magisk and kernel (again: if you have it) after the update. Done.
Click to expand...
Click to collapse
Ok. Cool. I tried that last time, but it failed. As a result, I'm a bit anxious about doing it again. Hopefully, I won't have any problems this time.
Thanks for the info.

I have had similar troubles as you, here's an overview of how to solve those problems.
OTA through OS:
Download and install OTA
Use Magisk Manager to download the TWRP A/B retention script and install it
Install Magisk to current and inactive slot
Reboot

Guys I am using latest blu_spark twrp. my bootloader is unlocked and I am running oxygenOS openbeta23. Following is my problem.
My flash order: (Note: already I have bue_spark twrp recovery running without issues)
1. Flash the full OTA(openbeta)
2. Flash the blu_spark twrp zip file on both active and non active slots.
3. Flash the latest magisk zip file. If step 3 is not successful means I will try to reboot in to recovery and again flash the magisk installer zip.
Until some time back all this worked fine. But for last 2-3 times although the flashing process of twrp zip on both slots ends with success message, when I reboot to recovery from twrp in order to flash magisk, the device boots in to stock recovery. I don't know how even after flashing twrp zip on both slots successfully why the devices bootbback to stock recovery. Then to have blu_spark twrp I have to connect my device to a computer in fastboot mode and then boot in to custom recovery using the blu_spark twrp image file and again flash the blu_spark twrp zip file which is inconvenient and also requires a computer.
Am I missing anything here?? If yes why this method was working perfectly before? Please somebody help.
Regards,
Sivabalan K

I flash in following order my stable updates
Flash full rom zip
Flash bluespark recovery
Restart into bluespark recovery
Flash magisk
Restart into Android
Everything works flawless. Magisk installed with all the modules running

Hi guys,
Don't you need to disable lock pattern/PIN or fingerprint/face ID? And don't need to uninstall magisk modules?
I never update my OP6 from my initial unlock/twrp/magisk and I'm a bit anxious to do it now...
Thanks
PS : I'm using original twrp (3.2.3-1), is this a problem?

[SOLVED] OTA with ROOT...

I ask before in "guide to root motorla g stylus":
really is no way to work OTA while Magisk installed? i mean some Magisk Hide Props Config, or not install TWRP or anything? i actualy have Nokia 7 Plus (unlocked via unoficial method) and last year while not installed TWRP is possible check system update, install over air (while Magisk is installed), before reboot run MagiskManager, install Magisk to other slot, reboot, started from updated slot with Magisk installed, without need flash stock boot img before ota and flash manualy patched boot img after OTA... sure have Moto G Pro additional check or limitation and this not work? thanks...
Click to expand...
Click to collapse
without reaction, then try make separated thread, i actualy have one week "Motorola Moto G Pro" (XT2043-7), rooted, and wait for OTA, UpdateCheck in Settings not show me, try LMSA Rescue/Download and show me same version as have installed QPRS30.80-109-2-7...
Questions:
- Have any user of same phone, without root, already showed Octorber OTA?
- Is on rooted posible UpdateCheck with show if OTA avaiable?
- Have any working solution for OTA update on rooted phone without need connected with PC? Similar or same as i write about Nokia7Plus?
(i mean without flash back stock img, make ota, patch new boot.img file in MagiskManager, flash it via TWRP booted...
i think without PC be sure posible flash back stock boot.img to boot partition, before OTA, maybe download zip of full "rom" and extract boot.img, patch via MagiskManager, but not flash patched
EDIT: Sollution here

The answers to your first two questions are yes. When on stock I successfully updated. And while rooted there was a notification for ota update, it would download, but fall to install. I came across a way to do it without having to connect to pc. Some said it was successful but I was not able to try. It has something to do with placing your original boot.img into a a folder on one of the root directories but I had no idea how in the hell they came up with the system path to the file (encrypted??) Because I didn't have any of the folders on my phone and was to lazy at the time to ask for help. It was also an older thread so I didn't feel like bringing up a thread that old.

without root you updated system to higher (with Ocrober security patches) version than QPRS30.80-109-2-7 (this version have September security patches) ?
second part of you answer i think not understand, with rooted phone, put boot.img in "a" directory in one (which?where?) root folder and OTA services flash it before upgrade/reboot???

please, anyone with "Motorola Moto G Pro" (XT2043-7), channel "reteu", have already displayed update notification for "QPRS30.80-109-2-8" ?

Yesterday i finally get OTA notify with QPRS30.80-109-2-8, with Magisk installed, ofcourse failed install, then i find this solution, to update OTA over Air with Magisk installed without need any steps with PC
Code:
1. Settings System/DeveloperOptions/AutomaticSystemUpdate=Disable
2. Settings System/SystemUpdate/.../SmartUpdate=Disable
3. MagiskManager UninstallMagisk/RestoreImages
4. Settings System/SystemUpdate "doing normal update and wait for finish"
5. After OTA Instralled [B]NOT[/B] Restart
6. MagiskManager MagiskInstall/InstallToInactiveSlotAfterOTA/LetsGo "wait for finish"
7. After Magisk installed tap to Reboot button in Magisk Instalation wIndow...

Very nice writeup. With respect to step 3, I never installed Magisk Manager (I simply did the patch of boot.img) so what should I do to restore image? With respect to step 5, how do I get to that point? Is it a prompt after rebooting?

flroots said:
[...] step 3, I never installed Magisk Manager (I simply did the patch of boot.img) so what should I do to restore image?
Click to expand...
Click to collapse
you must have installed Magisk via TWRP (only temporary booted is enough), this make backup image which is latter in MagiskManager used for restore
flroots said:
[...] step 5, how do I get to that point? Is it a prompt after rebooting?
Click to expand...
Click to collapse
this is normal OTA screen, is show if you check update and if available, then show progress about installing, only is need after ota finished, not using reboot button in this OTA screen, but make steps 6 and 7

k3dar7 said:
you must have installed Magisk via TWRP (only temporary booted is enough), this make backup image which is latter in MagiskManager used for restore
Click to expand...
Click to collapse
I installed Magisk Manager via download of apk file (not TWRP). I then clicked on Magisk and chose "Select and patch a file". The end result was getting root. I never actually did a separate install of Magisk or Magisk Manager. I wonder if your step 3 will work in this case.
k3dar7 said:
this is normal OTA screen, is show if you check update and if available, then show progress about installing, only is need after ota finished, not using reboot button in this OTA screen, but make steps 6 and 7
Click to expand...
Click to collapse
Thanks

flroots said:
I installed Magisk Manager via download of apk file (not TWRP). I then clicked on Magisk and chose "Select and patch a file". The end result was getting root. I never actually did a separate install of Magisk or Magisk Manager. I wonder if your step 3 will work in this case.
Click to expand...
Click to collapse
Understand, but as i write, you must have installed Magisk via TWRP, with this method, Magisk make backup of boot image to "/data/magisk_backup_SomeRandomStrings/boot.img.gz", this file is used when you doing step 3, but if you only patch stock boot file, then ofcourse this backup is not created... i sugest you:
- revert boot to stock via same way as you flash patched before, but using stock boot.img
- boot TWRP (NOT flash, use command is section "Boot") and install Magisk.zip oficial release
- if on your phone/touchscreen variant not work touchscreen in TWRP, then (while still is booted TWRP) install it using adb

Thanks.

I have a couple questions:
1. Is it true that one shouldn't do an OTA unless the corresponding firmware can be downloaded due to the fact that you will lose root and not be able replace it until the corresponding boot.img can be obtained?
2. When downloading firmware from LMSA, does it download the latest or does it download your current version?

flroots said:
I have a couple questions:
1. Is it true that one shouldn't do an OTA unless the corresponding firmware can be downloaded due to the fact that you will lose root and not be able replace it until the corresponding boot.img can be obtained?
2. When downloading firmware from LMSA, does it download the latest or does it download your current version?
Click to expand...
Click to collapse
1. NO - i with Magisk installed, receive OTA October (delayed) and November, and hope with december be same
not need wait for avaiable boot.img, because with "Boot TWRP & Flash MagiskZip" is patched onthefly "any" version of boot partition on device.
2. not sure, i not use LMSA

k3dar7 said:
1. NO - i with Magisk installed, receive OTA October (delayed) and November, and hope with december be same
not need wait for avaiable boot.img, because with "Boot TWRP & Flash MagiskZip" is patched onthefly "any" version of boot partition on device.
Click to expand...
Click to collapse
Thanks, that sounds great. Would you mind elaborating the steps involved? I have TWRP and Magisk installed now.

k3dar7 said:
Yesterday i finally get OTA notify with QPRS30.80-109-2-8, with Magisk installed, ofcourse failed install, then i find this solution, to update OTA over Air with Magisk installed without need any steps with PC
Code:
1. Settings System/DeveloperOptions/AutomaticSystemUpdate=Disable
2. Settings System/SystemUpdate/.../SmartUpdate=Disable
3. MagiskManager UninstallMagisk/RestoreImages
4. Settings System/SystemUpdate "doing normal update and wait for finish"
5. After OTA Instralled [B]NOT[/B] Restart
6. MagiskManager MagiskInstall/InstallToInactiveSlotAfterOTA/LetsGo "wait for finish"
7. After Magisk installed tap to Reboot button in Magisk Instalation wIndow...
Click to expand...
Click to collapse
Do these steps cause loss of data? Thanks

flroots said:
Do these steps cause loss of data? Thanks
Click to expand...
Click to collapse
i ofcourse not garant ;-) but for me nothing lost, also installed magisk modules is preserved...

k3dar7 said:
Yesterday i finally get OTA notify with QPRS30.80-109-2-8, with Magisk installed, ofcourse failed install, then i find this solution, to update OTA over Air with Magisk installed without need any steps with PC
Code:
1. Settings System/DeveloperOptions/AutomaticSystemUpdate=Disable
2. Settings System/SystemUpdate/.../SmartUpdate=Disable
3. MagiskManager UninstallMagisk/RestoreImages
4. Settings System/SystemUpdate "doing normal update and wait for finish"
5. After OTA Instralled [B]NOT[/B] Restart
6. MagiskManager MagiskInstall/InstallToInactiveSlotAfterOTA/LetsGo "wait for finish"
7. After Magisk installed tap to Reboot button in Magisk Instalation wIndow...
Click to expand...
Click to collapse
Tried the above steps, but OTA update unsuccessful. Discovered that phone still rooted so obviously step 3 did not work for me. What should I try next? How about fastboot of original boot.img?

flroots said:
Tried the above steps, but OTA update unsuccessful. Discovered that phone still rooted so obviously step 3 did not work for me. What should I try next? How about fastboot of original boot.img?
Click to expand...
Click to collapse
step 3 restore boot image(what show you MagiskManager as output while you restore images??), but without reboot you have ofcourse still root, and you can't reboot if you want patch boot in other slot after ota via MagiskManager....
but i don't know reason why OTA failed anyway restoring original boot.img via fastboot be i think possible (not try in MotoGPro but manytime with Nokia7Plus)

k3dar7 said:
step 3 restore boot image(what show you MagiskManager as output while you restore images??), but without reboot you have ofcourse still root, and you can't reboot if you want patch boot in other slot after ota via MagiskManager....
but i don't know reason why OTA failed anyway restoring original boot.img via fastboot be i think possible (not try in MotoGPro but manytime with Nokia7Plus)
Click to expand...
Click to collapse
Thanks. Magisk simply says, "restoration done". Once I fastboot boot.img will I need to re-install magisk from scratch or should I continue with steps 6 and 7?

flroots said:
Thanks. Magisk simply says, "restoration done". Once I fastboot boot.img will I need to re-install magisk from scratch or should I continue with steps 6 and 7?
Click to expand...
Click to collapse
maybe magisk backup boot.img have already twrp inside if you install twrp before magisk?
anyway, if you flash stock boot.img, then step 6&7 is not applicable, because this need booted rooted system

btw: method above work for me also while i upgrade from Android10 to Android11 ;-)