Database Users

Issue with Magisk and OTA version 7.1.2

I am having issues getting an OTA with Magisk 15.2 installed. MAgisk Manager is 5.5.3.
1. I did a flash of fastboot rom for the first december update of 7.1.2 without overwriting storage.
2. I unlocked the bootloader
3. I booted (did not flash) to 3.1.1 of TWRP and loaded Magisk 15.2. Everything worked fine.
4. I followed this guide https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md#ota-installation-tips and went Magisk Manager → Uninstall → Restore Stock Boot. I received a confirmation that the stock boot was restored. However, at this point, my google camera still works. This seems illogical if the stock boot is replaced.
5. When I download the second december OTA update I get a failure to install error at step 2 of 2.
Has anyone had similar issues or have solution? If I post to the Magisk threads, what logs will they require and how specifically must I create the logs and where will they be stored?

I didn't get a reply here. Mod, please delete this post. I will add it at Magisk thread.

Oh, wow. I have also installed magisk in the way you have. I hope it hasn't messed with your system. However I'm fully updated so have no way of trying your method of OTA.
Please update me if you do solve your issue incase I also have similar difficulties.

It is no major issue, it is just a pain in the butt to have to flash the fastboot rom to update... It take 15 minutes and a PC if you can't get OTA...
I'm just lazy.

ludditefornow said:
I am having issues getting an OTA with Magisk 15.2 installed. MAgisk Manager is 5.5.3.
1. I did a flash of fastboot rom for the first december update of 7.1.2 without overwriting storage.
2. I unlocked the bootloader
3. I booted (did not flash) to 3.1.1 of TWRP and loaded Magisk 15.2. Everything worked fine.
4. I followed this guide https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md#ota-installation-tips and went Magisk Manager → Uninstall → Restore Stock Boot. I received a confirmation that the stock boot was restored. However, at this point, my google camera still works. This seems illogical if the stock boot is replaced.
5. When I download the second december OTA update I get a failure to install error at step 2 of 2.
Has anyone had similar issues or have solution? If I post to the Magisk threads, what logs will they require and how specifically must I create the logs and where will they be stored?
Click to expand...
Click to collapse
4. restore boot image function will reflash stock boot.img to boot partition, but until reboot you are still using patched_boot.img which is loaded in memory. So you will not lose root access and all Magisk modules work (until reboot).
5. failed update could be due to tampered system partition (it is enough to mount it as RW in TWRP). Reflash fastboot images without data erase and do not modify system in any way afterwards.

_mysiak_ said:
4. restore boot image function will reflash stock boot.img to boot partition, but until reboot you are still using patched_boot.img which is loaded in memory. So you will not lose root access and all Magisk modules work (until reboot)
Click to expand...
Click to collapse
Thanks for the detailed reply.. this is the thing that confuses me. The Magical guide clear states to not reboot the phone after uninstalling the patched boot.. so how can the ota possibly pass?

ludditefornow said:
Thanks for the detailed reply.. this is the thing that confuses me. The Magical guide clear states to not reboot the phone after uninstalling the patched boot.. so how can the ota possibly pass?
Click to expand...
Click to collapse
OTA updater verifies system and boot partition (possibly other partitions too) - if they are intact, it applies the OTA patch to unused, secondary partitions. OTA updator doesn't care if your currently running boot image is patched or not, because it's not using files from RAM, but from ROM. Once update finishes its thing (stage 2/2), you install Magisk in backup boot partition, which after reboot becomes active. This is why it's possible to apply OTA while you're rooted with Magisk and you have A/B partition system (as long as you follow the guide).

"Installation Failed" MI A1 OTA UPDATE

Ok, why the f. did I get "installation failed" when installing OTA following this guide?
I followed the guide, I hit uninstall and "restore images" in magisk, it restored the stock image and when I tried running feb ota, I got "installation failed", why?
Also, why did my device get in a bootloop by just fully uninstalling magisk?
I had unlocked bootloader with systemless root, with no TWRP, never booted it, never flashed it, only fastboot commands I ran were oem unlock and boot patched_boot.img. I never touched system partition (on purpose), never installed anything other than a bunch of magisk modules, safetynet was always working, if it matters.
PSA FOR GOOGLE VISITORS:
Do not fully uninstall magisk after you get "installation failed", I got a bootloop and had to flash flash_all_except_storage.bat from mi a1 stock rom using miFlash (bottom right to select it, don't flash_all if you want your data).

Same thing happened with me... what exactly i done was...booted into patched boot.img using fastboot and after that used magisk manager and installed camera2api and just substratum.....but when i got notification of feb update... I tried to uninstall magisk manager using complete uninstall option....then restarted manually then it booted up and then suddenly shuts down and started showing a black screen with Android logo with (No command) written below it......to recover from this condition i again tried to use the same fastboot method for booting into patched boot... after which i was able to use my mobile.... normally but I'm not able to install feb update.... I'm downloading the complete stock rom.....but if there's any other method which can be efficient so plz inform....

Azeemkwow said:
Same thing happened with me... what exactly i done was...booted into patched boot.img using fastboot and after that used magisk manager and installed camera2api and just substratum.....but when i got notification of feb update... I tried to uninstall magisk manager using complete uninstall option....then restarted manually then it booted up and then suddenly shuts down and started showing a black screen with Android logo with (No command) written below it......to recover from this condition i again tried to use the same fastboot method for booting into patched boot... after which i was able to use my mobile.... normally but I'm not able to install feb update.... I'm downloading the complete stock rom.....but if there's any other method which can be efficient so plz inform....
Click to expand...
Click to collapse
Just like he said, yeah using Magisk means waving bye to OTA updates. This was the exact problem I faced where I installed Magisk module without TWRP for the joys of using substratum. Installating magisk won't taper your system, they said, you would still get the update, they said. Well NEWS FLASH for those, installing magisk tampers your system partitions and you are in a dreadlock situation where you can't do ****. People claim there are work arounds like you linked but no one has actually confirmed using it. And the worst part is that if you try to install the update even after uninstalling Magisk , it will still give you the error. How do I know? tried it, doesn't work. The only option which was left to me was to download the official Oreo ROM from MiUI global and flash it using MiFlash.

Flashing the boot.img from stock rom might solve the problem. If not, flash the stock rom using MiFlash with save user data option.

Alanjameson99 said:
Just like he said, yeah using Magisk means waving bye to OTA updates. This was the exact problem I faced where I installed Magisk module without TWRP for the joys of using substratum. Installating magisk won't taper your system, they said, you would still get the update, they said. Well NEWS FLASH for those, installing magisk tampers your system partitions and you are in a dreadlock situation where you can't do ****. People claim there are work arounds like you linked but no one has actually confirmed using it. And the worst part is that if you try to install the update even after uninstalling Magisk , it will still give you the error. How do I know? tried it, doesn't work. The only option which was left to me was to download the official Oreo ROM from MiUI global and flash it using MiFlash.
Click to expand...
Click to collapse
Thanks...now that's what I'm planning to do...install official rom through miflashtool

RavinduSha said:
Flashing the boot.img from stock rom might solve the problem. If not, flash the stock rom using MiFlash with save user data option.
Click to expand...
Click to collapse
Does the 'save user data'-option also preserve the apps installed?
Thanks!

Tiemichael said:
Does the 'save user data'-option also preserve the apps installed?
Thanks!
Click to expand...
Click to collapse
Yes it saves all user data including settings, apps and app data

I had the same issue. I used the tool linked below and the steps:
- Unlock Bootloader
- Flash Stock ROM
- Download ROM (and wait for that to happen)
- Keep UserData (and wait again)
- Lock Bootloader
After that I was able to install the update, then re-install Magisk and camera tweaks.
https://forum.xda-developers.com/mi-a1/how-to/tool-xiaomi-mi-a1-tool-drivers-unlock-t3742857

The guide mention in OP had worked for me for at least 3 updates including the major one from nougat to oreo with any issue. Be aware that mounting system partition as read AND WRITE brakes OTA. You don't even need to change anything just mounting it will brake it. That could easily happen using a root file explorer or a hosts file based add blocker if Magisk is not properly set (systemless hosts support toggle in Magisk settings).

Help! OTA Update 9.0.7 Now Magisk missing Safetynet

I installed update and now can no longer do Safetynet the option is missing in Magisk.
Also the wifi and modem does not work either. This only happened after updating to the new OTA.

Maybe This Will Help:
molitar said:
I installed update and now can no longer do Safetynet the option is missing in Magisk.
Also the wifi and modem does not work either. This only happened after updating to the new OTA.
Click to expand...
Click to collapse
So i just got the phone three days ago but maybe try rebooting your phone to TWRP or if you don't have it installed on your recovery go to a computer and launch ADB, what you want to do is temp boot into TWRP then sideload Magisk again.
To make things easier:
=============================
1. Boot into TWRP (Either through recovery or ADB)
2. Get your yourself the stock boot.img to clear things up on Magisk's end.
3. Sideload your Magisk zip.
4. Clear cache and dalvik cache
5. Reboot the phone.
If you don't flash a stock.img of the current OOS you are on safetynet may fail but reinstalling Magisk through TWRP should fix your safetynet issue. As far as WIFI goes try flashing the modem.img file for your current OOS version, this might do the trick but i am not so sure as this is my first time using a oneplus device.
Hope i have helped you out. Don't take OTAs, they break root as an OTA is just for stock OOS with no root so there is no support for rooted devices when it comes to these updates.
Edit: Try this if it doesn't work https://forum.xda-developers.com/oneplus-6t/how-to/9-0-7-patched-magisk-boot-img-t3875498

ROOT67 said:
So i just got the phone three days ago but maybe try rebooting your phone to TWRP or if you don't have it installed on your recovery go to a computer and launch ADB, what you want to do is temp boot into TWRP then sideload Magisk again.
To make things easier:
=============================
1. Boot into TWRP (Either through recovery or ADB)
2. Get your yourself the stock boot.img to clear things up on Magisk's end.
3. Sideload your Magisk zip.
4. Clear cache and dalvik cache
5. Reboot the phone.
If you don't flash a stock.img of the current OOS you are on safetynet may fail but reinstalling Magisk through TWRP should fix your safetynet issue. As far as WIFI goes try flashing the modem.img file for your current OOS version, this might do the trick but i am not so sure as this is my first time using a oneplus device.
Hope i have helped you out. Don't take OTAs, they break root as an OTA is just for stock OOS with no root so there is no support for rooted devices when it comes to these updates.
Click to expand...
Click to collapse
How do you install ota when rooted?

worldsoutro said:
How do you install ota when rooted?
Click to expand...
Click to collapse
I uninstalled magisk, did the regular OTA update, do not reboot, then install Magisk again on the inactive slot.
Ok fixed the problem I was having.. I had to do a complete factory wipe after installing Magisk. It's now working and I am using Oneplus Switch to restore my data backup now.

worldsoutro said:
How do you install ota when rooted?
Click to expand...
Click to collapse
See in OTA thread in general guide news section, procedure is clearly written

molitar said:
I uninstalled magisk, did the regular OTA update, do not reboot, then install Magisk again on the inactive slot.
Ok fixed the problem I was having.. I had to do a complete factory wipe after installing Magisk. It's now working and I am using Oneplus Switch to restore my data backup now.
Click to expand...
Click to collapse
Glad to hear it worked out for you.

P2XL OTA + Magisk install before reboot = keep root

Didn't see anyone else confirming that the Magisk OTA install works with Android 10, so... confirming that it does.
Let OTA finish but don't reboot.
Go to Magisk Manager and "Install" Magisk - select the bottom option (includes the OTA phrase)
Reboot
Profit.
No problems noticed in a half-day of use.

Did you do this from Pie or from Android Q beta? Also, did you uninstall Magisk from the manager before you did the OTA?

Anybody know if this worked smoothly with their Viper4Android app?

This worked form me going from Android 9 with Magisk to Android 10

I'm glad I waited and saw this before moving to Android 10. This worked like a charm for me as well.

gregoryx said:
Didn't see anyone else confirming that the Magisk OTA install works with Android 10, so... confirming that it does.
Let OTA finish but don't reboot.
Go to Magisk Manager and "Install" Magisk - select the bottom option (includes the OTA phrase)
Reboot
Profit.
No problems noticed in a half-day of use.
Click to expand...
Click to collapse
Is this working on Novemeber 2019? i am rooted with magisk and twrp , but the OTA says error to download, try again. and never downloads and installed it.
---------- Post added at 09:16 PM ---------- Previous post was at 09:16 PM ----------
gregoryx said:
Didn't see anyone else confirming that the Magisk OTA install works with Android 10, so... confirming that it does.
Let OTA finish but don't reboot.
Go to Magisk Manager and "Install" Magisk - select the bottom option (includes the OTA phrase)
Reboot
Profit.
No problems noticed in a half-day of use.
Click to expand...
Click to collapse
Is this working on Novemeber 2019? i am rooted with magisk and twrp , but the OTA says error to download, try again. and never downloads and install it.

Ota usually gives me error cant install so i flash factory image without (-w) wiping then i reflash kernel and magisk, result is updating to latest image with everything stays at it is

kmry said:
Is this working on Novemeber 2019? i am rooted with magisk and twrp , but the OTA says error to download, try again. and never downloads and install it.
Click to expand...
Click to collapse
Is your recovery stock? It may not be clearly stated as I haven't read the thread in its entirety, but the OTA will fail with TWRP installed. It likely will also fail if the system partition is modified.
EDIT: I re-read your post. You clearly note using TWRP.

Nightf0x_007 said:
Ota usually gives me error cant install so i flash factory image without (-w) wiping then i reflash kernel and magisk, result is updating to latest image with everything stays at it is
Click to expand...
Click to collapse
How do you flash it, with flash fire, trough TWRP or from fastboot?

kmry said:
How do you flash it, with flash fire, trough TWRP or from fastboot?
Click to expand...
Click to collapse
Factory image flash via adb using pc, then i boot to twrp and reflash kernel and magisk

Anyone know how to get the native led configuration without using a custom rom or the lightflow app?

Should I update Magisk and manager before I do this?
My Magisk installed is 18.1 and it lists 20.1 as available
Magisk Manager installed is 7.0 and 7.4 is listed as available

If you wanna follow the official instructions :
https://topjohnwu.github.io/Magisk/tutorials.html#ota-installation

Nightf0x_007 said:
Factory image flash via adb using pc, then i boot to twrp and reflash kernel and magisk
Click to expand...
Click to collapse
i decided to flash the complete ota trough TWRP, installed normally but TWRP was gone, so installed again, then magisk then EX kernel, thanks.

kmry said:
i decided to flash the complete ota trough TWRP, installed normally but TWRP was gone, so installed again, then magisk then EX kernel, thanks.
Click to expand...
Click to collapse
Yes this also works, this was the procedure i was following before, but i dont have twrp installed in my device, it causes bootloop and device sensors errors idk why so i fastboot it, once i tried updating by flashing ota zip via twrp but device didnt bootup maybe cause twrp is not installed so since that what i do is reflashing factory image without -w

Nightf0x_007 said:
Yes this also works, this was the procedure i was following before, but i dont have twrp installed in my device, it causes bootloop and device sensors errors idk why so i fastboot it, once i tried updating by flashing ota zip via twrp but device didnt bootup maybe cause twrp is not installed so since that what i do is reflashing factory image without -w
Click to expand...
Click to collapse
do i have to delete the "-w" command only on the "flash-all.bat" or on the "flash-all.sc" too?

kmry said:
do i have to delete the "-w" command only on the "flash-all.bat" or on the "flash-all.sc" too?
Click to expand...
Click to collapse
Just the flash-all.bat if your using Windows. :good:

kmry said:
do i have to delete the "-w" command only on the "flash-all.bat" or on the "flash-all.sc" too?
Click to expand...
Click to collapse
.bat file only

Update 11.1.1.1 and root?

What I need to do to upgrade and root version 11.1.1.1, I'm currently on a 9.0.16 rooted twrp magisk

Wheres the download link for the full OOS 11.1.1.1.1.1.1? Does OTA mean the full stock rom download or zip file just for update????

The way I did it from 10.3.8 and 10.3.12:
1) Boot into TWRP
2) Flash latest TWRP (twrp-installer-3.5.2_9-0-fajita.zip from official TWRP site) and Reboot to recovery
3) Flash the full OOS11 zip file. It will flash one of the two A/B slots - DO NOT YET REBOOT!!!
4) Directly after flashing the OOS11 zip flash twrp-installer-3.5.2_9-0-fajita.zip again
5) Reboot into recovery
6) Flash OOS11 zip again into the other slot - Again: DO NOT YET REBOOT!!!
7) Flash twrp-installer-3.5.2_9-0-fajita.zip again
8) Flash Magisk-v23.zip
9) Reboot
Looks more complicated than it really is. You just have to do everything twice to flash both slots. At least that's how I did it a couple of times and it worked without any issues.
!!!You could also Flash directly from the updater app without rebooting. Go into Magisk and install twrp A/B retention script and reinstall Magisk. I never did it that way because I always made a Nandroid backup before flashing everything.!!! See edit comment!!
Hope that helps.
Edit: I just read in another thread the Magisk route (A/B retentio...) leads to a Qualcomm Crashdump which needs unbricking via the MsmDownloadTool!!!
@ptuner: I usually go tp Settings -> System -> System Updates. Don't install, just but put the phone aside for some time. It will download the full zip into Internal memory/.Ota.
You download the full zip from any of the places you find via your search engine of choice.

MrBrainstorm said:
The way I did it from 10.3.8 and 10.3.12:
1) Boot into TWRP
2) Flash latest TWRP (twrp-installer-3.5.2_9-0-fajita.zip from official TWRP site)
3) Flash the full OOS11 zip file. It ill flash one of the two A/B slots - DO NOT YET REBOOT!!!
4) Directly after flashing the OOS11 zip flash twrp-installer-3.5.2_9-0-fajita.zip again
5) Reboot into recovery
6) Flash OOS11 zip again into the other slot - Again: DO NOT YET REBOOT!!!
7) Flash twrp-installer-3.5.2_9-0-fajita.zip again
8) Flash Magisk-v23.zip
9) Reboot
Looks more complicated than it really is. You just have to do everything twice to flash both slots. At least that's how I did it a couple of times and it worked without any issues.
!!!You could also Flash directly from the updater app without rebooting. Go into Magisk and install twrp A/B retention script and reinstall Magisk. I never did it that way because I always made a Nandroid backup before flashing everything.!!! See edit comment!!
Hope that helps.
Edit: I just read in another thread the Magisk route (A/B retentio...) leads to a Qualcomm Crashdump which needs unbricking via the MsmDownloadTool!!!
@ptuner: I usually go tp Settings -> System -> System Updates. Don't install, just but put the phone aside for some time. It will download the full zip into Internal memory/.Ota.
You download the full zip from any of the places you find via your search engine of choice.
Click to expand...
Click to collapse
all data is deleted yes?

ELAD098 said:
all data is deleted yes?
Click to expand...
Click to collapse
No, if you upgrade via TWRP as I described your data will NOT be wiped. But I always advice to make a full backup (nandroid and internal storage) before flashing anything!!

Are you satisfied by 11.1.1.1 generally ?
I was on 11 and rollback to 10 cuz battery issues. Can anyone give some info, are you satisfied with 11.1.1.1 ?

I am only using since last Wednesday but so far I am happy with it. The battery usage is identical to 10.3.12 with 0.7%/h (according to AccuBattery). Screen usage is probably the same. Can't really tell as I am not a heavy user.

Unfortunately I tried to install and got a brick
i can unlocked bootloader on 11.1.1.1
now i on 10.3.8 lock bootloader
i want to upgrade

I bricked mine too and used MSM tool to get to android 9, I installed TWRP 3.3.1-31 (pie version) and last version of Magisk, after that, I wiped all but internal storage, download OOS 11.1.1.1.1.1..1 and flashed with TWRP, done after like 5 min, I clean Dalvik cache and flash the same TWRP (3.3.1-31 pie version) + Magisk 23
Booted the system and noticed that Magisk wasn't installed so I got back to recovery, flashed once again Magisk and all Good until I fok up again in the future.
Messing around with rooted oos 11 only for 1 day so far and I already noticed the battery drain on this system is more (agressive)

I used adb to shut off the update notification posted by Sachin09.
Adb devices (for checking device is connected)
Adb shell
pm uninstall -k --user 0 com.oneplus.opbackup
exit
I have issues with phone after though. Phone says not online WiFi but I can watch youtube but I cannot open or view any attachments in gmail. I had Hotpot on when I ran the adb script. I'm wondering if that was a problem.
Question: If I repeat the adb script but swap install for uninstall, will it revert to normal? Any suggestions? I'm still on 10.3.12 and happy with it.

Jim44 said:
I used adb to shut off the update notification posted by Sachin09.
Adb devices (for checking device is connected)
Adb shell
pm uninstall -k --user 0 com.oneplus.opbackup
exit
I have issues with phone after though. Phone says not online WiFi but I can watch youtube but I cannot open or view any attachments in gmail. I had Hotpot on when I ran the adb script. I'm wondering if that was a problem.
Question: If I repeat the adb script but swap install for uninstall, will it revert to normal? Any suggestions? I'm still on 10.3.12 and happy with it.
Click to expand...
Click to collapse
Try to do a local update with full zip file. Maybe it help.
edited: try thiis command and see if it work
Code:
1. adb shell
2. cmd package install-existing com.oneplus.opbackup
3. exit
After that restart the phone.

Thank you! That worked. I'm back with the unwanted OS 11 update again.
I tried the "pm -k uninstall..." again which removed the update but the wifi and gmail issues returned.
I fixed it though. I rooted my 1+6T long ago. I have the TWRP and MAGISK zip files in root.
I booted into recovery, uninstalled Magisk with the uninstaller zip, installed TWRP..zip then installed Magisk..zip. I rebooted and now everything works.
I tested out OS 11.1.1.1.1 on my buddy's phone and I don't want that OS. Thank again for the help I needed. Jim44