Related
I've flashed Magisk, but because I can't get Xposed to work, I'd like to remove Magisk and install SuperSU, but I don't know how. I tried to flash the uninstaller via TWRP and it says everything is fine, but after rebooting it just stays installed. If I try to flash SuperSU anyway I get stuck on boot. I have to flash stock boot.img via TWRP and then Magisk magically reappears. I tried using MiFlash but it refuses to do anything. It says no permission.
One possible solution, I guess, would be to flash stock ROM via TWRP. Can this be done? Any other ideas? Or am I just stuck with Magisk until a new version is available?
Filip013 said:
I've flashed Magisk, but because I can't get Xposed to work, I'd like to remove Magisk and install SuperSU, but I don't know how. I tried to flash the uninstaller via TWRP and it says everything is fine, but after rebooting it just stays installed. If I try to flash SuperSU anyway I get stuck on boot. I have to flash stock boot.img via TWRP and then Magisk magically reappears. I tried using MiFlash but it refuses to do anything. It says no permission.
One possible solution, I guess, would be to flash stock ROM via TWRP. Can this be done? Any other ideas? Or am I just stuck with Magisk until a new version is available?
Click to expand...
Click to collapse
Magisk is pretty much "useless" for now. Because it is based on system-less root, and cannot be updated (because still in testing phase! Newer Xposed module from Magisk requires latest Magisk root binary, which is pretty out of option atm as we can't update to the latest binary). The only solution if you want to have proper root access is:
1. Head over to Xiaomi MIUI website and download the full stock ROM again, and then flash it via fastboot (choose flash_all_except_storage.bat if you want to preserve your data).
2. Once flashed, reboot back to bootloader and unlock it.
3. While still in bootloader flash the correct CF-Auto root boot image for your ROM (contains SuperSU 2.82 binary, https://desktop.firmware.mobi/device:1748)
4. Wait patiently and it will automatically reboot. Install SuperSU from Play Store if you want root management app.
5. If you need Xposed, download the Xposed apk from XDA and then install it normally (not via recovery).
6. ??? Profit
*DO NOT INSTALL permanent TWRP as it will cause your phone stuck in boot loop.
@soralz
Thanks for your help, but no luck. I understand what I'm supposed to do, but I can't get MiFlash to work. When I try to flash stock image I get a "Permission Denied" error. (I have unlocked my bootloader successfully). I tried flashing modified stock image from here But then I couldn't boot. My only solution is to flash stock boot.img via TWRP and I can boot, but I stay stuck with Magisk.
So far, the only options I can think of is to wait for a recovery-flashable ROM, a new software update or a new version of Magisk.
Filip013 said:
@soralz
Thanks for your help, but no luck. I understand what I'm supposed to do, but I can't get MiFlash to work. When I try to flash stock image I get a "Permission Denied" error. (I have unlocked my bootloader successfully). I tried flashing modified stock image from here But then I couldn't boot. My only solution is to flash stock boot.img via TWRP and I can boot, but I stay stuck with Magisk.
So far, the only options I can think of is to wait for a recovery-flashable ROM, a new software update or a new version of Magisk.
Click to expand...
Click to collapse
You couldn't boot, are you using permanent TWRP?
Have you tried download the Full ROM from here and run this (as attachment)?
http://en.miui.com/download-333.html
Btw, place the folder under 1 directory only eg: as attachment. (I tried in multiple directory eg: "D:\Phones\ROM\Stock ROM", it just wouldn't flash)
@soralz
OMG!!! I can't believe it. MiFlash refused to let me flash because I tried to do that from the wrong location. Weird??!!
Good. I’ve managed to follow your instructions and success!! Just a minor note, I couldn't flash the modified boot.img directly via fastboot, it still won't let me. But I just booted TWRP (without flashing) and then flashed it from there. Again, THANK YOU!
BTW, yes, I had flashed permanent TWRP and then unsuccessfully tried to remove it.
Filip013 said:
@soralz
OMG!!! I can't believe it. MiFlash refused to let me flash because I tried to do that from the wrong location. Weird??!!
Good. I’ve managed to follow your instructions and success!! Just a minor note, I couldn't flash the modified boot.img directly via fastboot, it still won't let me. But I just booted TWRP (without flashing) and then flashed it from there. Again, THANK YOU!
BTW, yes, I had flashed permanent TWRP and then unsuccessfully tried to remove it.
Click to expand...
Click to collapse
Oh you manage to fix that? Good for you then. And yes you cannot have permanent TWRP and SuperSU at the same time. The CF-auto root for me I just click root.bat and done. btw side note, you will lose root after each update, besure to check out the new patched boot image. I m sure in the future we will have automated process, don't need to re-root manually after each update
Hi,
I've downgraded my phone ZE520KL couple months ago but I've forgotten that VOLTE is only available on 7.0...
I've recieved the OTA notification, downloaded the package on the phone, but when it reboots it is going on TWRP & then if I'm rebooting it doesn't continue the upgrade process.
What am I missing? (on my previous phones this wasn't so tricky...) Should I use the Install method directly from TWRP? If Yes on which zip? Is it possible to find the one that I've downloaded directly with my phone?
bibile said:
Hi,
I've downgraded my phone ZE520KL couple months ago but I've forgotten that VOLTE is only available on 7.0...
I've recieved the OTA notification, downloaded the package on the phone, but when it reboots it is going on TWRP & then if I'm rebooting it doesn't continue the upgrade process.
What am I missing? (on my previous phones this wasn't so tricky...) Should I use the Install method directly from TWRP? If Yes on which zip? Is it possible to find the one that I've downloaded directly with my phone?
Click to expand...
Click to collapse
Same like me before. Have you rooted your phone yet? if yes then try this, it work for me though (Backup your phone is recommended)
1. Download busybox, supersu and no-verity file
2. Using flashfire app, choose flash zip or ota option
3. Add ota 'WW-ZE520Kl-.....'
4. Add firmware 'UL-ASUS-....'
5. Remove tickmark from 'Inject supersu'
And flash, it will reboot but do not boot to system. You must boot to twrp, flash no-verity file, busybox and supersu or your phone will not boot. Then reboot, done.
If this method is helpful, do reply to me
Btw, sorry for my poor english.
[email protected]@ said:
Same like me before. Have you rooted your phone yet? if yes then try this, it work for me though (Backup your phone is recommended)
1. Download busybox, supersu and no-verity file
2. Using flashfire app, choose flash zip or ota option
3. Add ota 'WW-ZE520Kl-.....'
4. Add firmware 'UL-ASUS-....'
5. Remove tickmark from 'Inject supersu'
And flash, it will reboot but do not boot to system. You must boot to twrp, flash no-verity file, busybox and supersu or your phone will not boot. Then reboot, done.
If this method is helpful, do reply to me
Btw, sorry for my poor english.
Click to expand...
Click to collapse
Thanks, works wonderfully! Flashfire flashed the new OTAs successfully but the phone didn't then boot (or it bootlooped). A quick Google search led me to your response and the dm-verity file fixed the boot!
I also didn't flash Busybox in case you needed to know and before flashing the OTAs I checked the "Automount" and "Mount systeam as R/W" in Flashfire otherwise the app would just get stuck in a blank screen.
EDIT: WiFI isn't working, tried already deleting the files in /data/misc/wifi, /persist and /data/misc/dhcp as suggested in various threads but still nothing. Anyone know how to fix it before I attempt to do a full backup and wipe?
vEEGAZ said:
Thanks, works wonderfully! Flashfire flashed the new OTAs successfully but the phone didn't then boot (or it bootlooped). A quick Google search led me to your response and the dm-verity file fixed the boot!
I also didn't flash Busybox in case you needed to know and before flashing the OTAs I checked the "Automount" and "Mount systeam as R/W" in Flashfire otherwise the app would just get stuck in a blank screen.
EDIT: WiFI isn't working, tried already deleting the files in /data/misc/wifi, /persist and /data/misc/dhcp as suggested in various threads but still nothing. Anyone know how to fix it before I attempt to do a full backup and wipe?
Click to expand...
Click to collapse
Deleting files in /data/misc is not helped. Try this:
1. Check your selinux permissive or enforcing. If permissive, you should re-root your phone. Remember to flash busybox too or it will may some crash. Still not working follow step 2.
2. Re-flash the ROM using twrp. No data will be lost. Don't forget to re-root or it will not boot.
3. Try the lastest fw .68 or .75 though someone told that the .28 ota file had issue on wifi.
[email protected]@ said:
Deleting files in /data/misc is not helped. Try this:
1. Check your selinux permissive or enforcing. If permissive, you should re-root your phone. Remember to flash busybox too or it will may some crash. Still not working follow step 2.
2. Re-flash the ROM using twrp. No data will be lost. Don't forget to re-root or it will not boot.
3. Try the lastest fw .68 or .75 though someone told that the .28 ota file had issue on wifi.
Click to expand...
Click to collapse
Reflashing through TWRP worked Although I did it after backing up all the apps and did a factory reset which didn't even fix the wi-fi problem. But then Flashfire is useless if TWRP is capable of flashing OTAs right?
vEEGAZ said:
Reflashing through TWRP worked Although I did it after backing up all the apps and did a factory reset which didn't even fix the wi-fi problem. But then Flashfire is useless if TWRP is capable of flashing OTAs right?
Click to expand...
Click to collapse
Not really. Since OTA file can't flash through twrp. It really annoying for someone (like me ), so for the easiest way is just flash it using Flashfire, no need to use computer to flash stock recovery .
@vEEGAZ
yep, that's what I've been saying for months. I've never used anything but TWRP to flash my phone. I've downgraded, gone custom and back to stock many times.
@[email protected]@
I flash OTA's through TWRP every time there's an update.
wang1chung said:
@vEEGAZ
yep, that's what I've been saying for months. I've never used anything but TWRP to flash my phone. I've downgraded, gone custom and back to stock many times.
@[email protected]@
I flash OTA's through TWRP everything there's an update.
Click to expand...
Click to collapse
When my phone still in 6.0.1, flashed OTA's throgh twrp it said 'not correct phone...' but after upgraded 7.0 it succeeded although i don't need it anymore.
[email protected]@ said:
When my phone still in 6.0.1, flashed OTA's throgh twrp it said 'not correct phone...' but after upgraded 7.0 it succeeded although i don't need it anymore.
Click to expand...
Click to collapse
edit your updater-script and it'll flash no problem.
[email protected]@ said:
When my phone still in 6.0.1, flashed OTA's throgh twrp it said 'not correct phone...' but after upgraded 7.0 it succeeded although i don't need it anymore.
Click to expand...
Click to collapse
Yeah that's what I encountered aswell back 2-3 years ago, I remember I couldn't flash any OTAs via TWRP but apparently now you can. That's why I also used Flashfire in the first place but after running out of all options for the wi-fi problem I decided to give TWRP a try et voilà, it worked
wang1chung said:
edit your updater-script and it'll flash no problem.
Click to expand...
Click to collapse
I've tried that and still not working.
@[email protected]@
I JUST did it....on 1711.75 now. There was no recovery partition update either so I didn't have to reflash TWRP after :good:
I did have a bootloop issue after but fixed that by flashing the no-verity file. I'm not sure if that's related to having magisk installed though.
wang1chung said:
@[email protected]@
I JUST did it....on 1711.75 now. There was no recovery partition update either so I didn't have to reflash TWRP after :good:
I did have a bootloop issue after but fixed that by flashing the no-verity file. I'm not sure if that's related to having magisk installed though.
Click to expand...
Click to collapse
1. After reflashing rom through twrp, i lost my twrp. Oh, but when i use Flasfire, it isn't lost.
2. Not sure but after flashing ROM your boot will change to normal so it may not related to magisk or supersu. Maybe it beacause of the twrp, i've tried reflash stock recovery once and i can updated it without flash no-verity file though i've installed magisk.
[email protected]@ said:
1. After reflashing rom through twrp, i lost my twrp. Oh, but when i use Flasfire, it isn't lost.
2. Not sure but after flashing ROM your boot will change to normal so it may not related to magisk or supersu. Maybe it beacause of the twrp, i've tried reflash stock recovery once and i can updated it without flash no-verity file though i've installed magisk.
Click to expand...
Click to collapse
1. You will only lose TWRP if there is a recovery partition update in the stock firmware, yes, but that doesn't happen with every update. I think I read of a way to block it from updating the recovery partition but can't find the article right now. If flashfire works, use it, I just like TWRP for the other features like making and restoring nandroid backups.
2. I dirty flashed the update again through TWRP, verified the bootloop issue and then installed magisk (through TWRP) and it resolved the bootloop issue. No-verify file not required.
wang1chung said:
1. You will only lose TWRP if there is a recovery partition update in the stock firmware, yes, but that doesn't happen with every update. I think I read of a way to block it from updating the recovery partition but can't find the article right now. If flashfire works, use it, I just like TWRP for the other features like making and restoring nandroid backups.
2. I dirty flashed the update again through TWRP, verified the bootloop issue and then installed magisk (through TWRP) and it resolved the bootloop issue. No-verify file not required.
Click to expand...
Click to collapse
1.Ok, i got it.
2. The way using TWRP is keep the root ( root or not boot) and stock recovery is contrary ( can't root but will boot) or just flash custom kernel through twrp (not root required).
simple question :
- you are talking about OTA & Firmware...
I've downloaded again from asus website Version WW-V14.2020.1711.75 (I assume it is the latest firmware). Are you simply giving the example of an OTA that is released post the firmware version I have to install to have the 7.0 base?
Or is it anything that I'm missing...
From your explanations I should only :
- install flashfire
- flash the latest firmware
- boot into TWRP & flash no verity
- reboot the system
Right?
bibile said:
simple question :
- you are talking about OTA & Firmware...
I've downloaded again from asus website Version WW-V14.2020.1711.75 (I assume it is the latest firmware). Are you simply giving the example of an OTA that is released post the firmware version I have to install to have the 7.0 base?
Or is it anything that I'm missing...
From your explanations I should only :
- install flashfire
- flash the latest firmware
- boot into TWRP & flash no verity
- reboot the system
Right?
Click to expand...
Click to collapse
Yep, you can also flash the latest .zip via TWRP instead of using Flashfire, it's 100% working for me. Just REMEMBER to flash the no-verity file otherwise you'll end up in a bootloop.
I have newest oreo fw from asus website. Ive unlocked bootloader with official app. Now i want WTRP and root with magisk. I want to know how to flash updates to get all wroking?
1. Flash TWRP via fastboot?
2. Flash Magisk via TWRP?
3. When update will release i must flash whole fw from asus website with TWRP and then no-verity file to boot?
4. Or can i use flashfire app to flash fw from asus website and then no-verity zip?
What is the best solution to have updated system without use PC? Step by step guide will be great THX
Im confuse.
Im using 1711.75 with magisk 15.3 and twrp 3.2.1.0
I have the full firmware of initial oreo
I just have to install flashfire
Flash the full firmware oreo that i have then rboot to twrp to flash no verify zip?
ktl20 said:
I have newest oreo fw from asus website. Ive unlocked bootloader with official app. Now i want WTRP and root with magisk. I want to know how to flash updates to get all wroking?
1. Flash TWRP via fastboot?
2. Flash Magisk via TWRP?
3. When update will release i must flash whole fw from asus website with TWRP and then no-verity file to boot?
4. Or can i use flashfire app to flash fw from asus website and then no-verity zip?
What is the best solution to have updated system without use PC? Step by step guide will be great THX
Click to expand...
Click to collapse
iamROOTX said:
Im confuse.
Im using 1711.75 with magisk 15.3 and twrp 3.2.1.0
I have the full firmware of initial oreo
I just have to install flashfire
Flash the full firmware oreo that i have then rboot to twrp to flash no verify zip?
Click to expand...
Click to collapse
The safest and true way to flash any ota update without any issues by using stock recovery, don't use twrp or flashfire or any other apps.
follow the steps below:
1. When you are rooted and twrp installed, to getback to full stock boot and recovery without wiping data, flash the latest raw image available. For oreo the latest available one for ze520kl is WW_ZE520KL_15.0410.1712.31_M3.10.47.16_Phone-user.raw.zip.
2. Now flash the ota update available normally via stock recovery.
3. Flash oreo support twrp-3.2.1-0 and magisk zip.
4. Done.
I'm periodically upload the latest available ota update for ze520kl in the ze520kl ota update links thread.
Here is the latest one.
Hello
I got no answer on P8 lite 2017 thread so I try here.
I was on B180 (PRA-LX1C432 - P8 lite 2017) rooted with magisk
There were no updates available in settings/update, but connecting to PC HiSuite B194 appeared (which seems to be for Honor 8 lite by the way). It downloaded it, pushed it to phe phone, but when rebooting it goes to twrp... so obviously I'm still on B180
I imagine we have to flash back stock recovery before updating ? And then twrp again, magisk flash, etc ?
About OTA over magisk I found that on P9 forum:
1) unroot by Magisk Uninstaller, find the download link in the post https://forum.xda-developers.com/sho...63&postcount=1
2) flash from TWRP original stock boot img
3) wipe Dalwik and Cache from TWRP
3) flash from fastboot original stock recovery
4) let it make OTA update but select in the System Update settings to use Full (not differential) update - it will not delete your apps and settings
maybe the safest way indeed...
But as I "catch" the full ota update, maybe I can use fastboot to flash only system and boot, and then reflash magisk ?
anyone ?
Thanks !
sambastrakan said:
Hello
I got no answer on P8 lite 2017 thread so I try here.
I was on B180 (PRA-LX1C432 - P8 lite 2017) rooted with magisk
There were no updates available in settings/update, but connecting to PC HiSuite B194 appeared (which seems to be for Honor 8 lite by the way). It downloaded it, pushed it to phe phone, but when rebooting it goes to twrp... so obviously I'm still on B180
I imagine we have to flash back stock recovery before updating ? And then twrp again, magisk flash, etc ?
About OTA over magisk I found that on P9 forum:
1) unroot by Magisk Uninstaller, find the download link in the post https://forum.xda-developers.com/sho...63&postcount=1
2) flash from TWRP original stock boot img
3) wipe Dalwik and Cache from TWRP
3) flash from fastboot original stock recovery
4) let it make OTA update but select in the System Update settings to use Full (not differential) update - it will not delete your apps and settings
maybe the safest way indeed...
But as I "catch" the full ota update, maybe I can use fastboot to flash only system and boot, and then reflash magisk ?
anyone ?
Thanks !
Click to expand...
Click to collapse
I did this a few days ago!
My base:
Stock rom, Magisk, Xposed.
My steps:
1. Downloaded OTA on phone
2. Extracted stock recovery with huawai update.app extractor from the downloaded OTA
3. Fastboot flash recovery stockrecovery.img via PC
4. Boot phone, installed OTA without problems
Then I noticed my phone was oem locked again and root was gone.... I made a adb backup (TiBa needs root)
5. Unlocked oem again IT WIPED ALL DATA
6. Fastboot flash recovery TWRP.img
7. Boot, patch boot.img via Magisk, restore all apps etc.
Done!
Gesendet von meinem FRD-L09 mit Tapatalk
sambastrakan said:
Hello
I got no answer on P8 lite 2017 thread so I try here.
I was on B180 (PRA-LX1C432 - P8 lite 2017) rooted with magisk
There were no updates available in settings/update, but connecting to PC HiSuite B194 appeared (which seems to be for Honor 8 lite by the way). It downloaded it, pushed it to phe phone, but when rebooting it goes to twrp... so obviously I'm still on B180
I imagine we have to flash back stock recovery before updating ? And then twrp again, magisk flash, etc ?
About OTA over magisk I found that on P9 forum:
1) unroot by Magisk Uninstaller, find the download link in the post https://forum.xda-developers.com/sho...63&postcount=1
2) flash from TWRP original stock boot img
3) wipe Dalwik and Cache from TWRP
3) flash from fastboot original stock recovery
4) let it make OTA update but select in the System Update settings to use Full (not differential) update - it will not delete your apps and settings
maybe the safest way indeed...
But as I "catch" the full ota update, maybe I can use fastboot to flash only system and boot, and then reflash magisk ?
anyone ?
Thanks !
Click to expand...
Click to collapse
Did you try it? I also want to OTA update to B392 but I don't want to erase my phone. After some experiences, every time you update, the OEM locks. Is there a way to restore apps and all setttings via TWRP backup/restore option? Sorry if the question is completely wrong, I'm quite new at this.
Hello all awesome members, i have searched google, xda and even bing for answers but none have answerd me yet.
So i have an OP5 wich is running Oxygen os 5.1.2 and now i want to update it to the latest.
Things i have tried:
Download and update through the phone updater: Fail
Recovery manager: Fail
ADB sideload: Fail.
To be clear i don't care if i loose root i just want my phone back to fully stock.
So how do i get there? what am i missing?
Can you tell us more details, what ROOT method you are use? If you are using TWRP + Magisk, it's easy to update. Just download Full Update (not OTA) mostly OnePlus 5 will detected if our device ROOTED then will download Full ROM.
Then Goes to Custom Recover, Clear Cache dan Dalvi, install Full Update ROM and flash Magisk again and done
jauhari said:
Can you tell us more details, what ROOT method you are use? If you are using TWRP + Magisk, it's easy to update. Just download Full Update (not OTA) mostly OnePlus 5 will detected if our device ROOTED then will download Full ROM.
Then Goes to Custom Recover, Clear Cache dan Dalvi, install Full Update ROM and flash Magisk again and done
Click to expand...
Click to collapse
I diskussionen use twrp and magisk bit when i Tried to update via twrp i get error 7. I want it to get normal again
last time i searched around and got myself in a hard brick situation. please make a guide for this. Noob here
Ashiq.makkar said:
last time i searched around and got myself in a hard brick situation. please make a guide for this. Noob here
Click to expand...
Click to collapse
If you are rooted using Magisk, look here.
Let me know if you need help.
thank you but i tried this and got installation problem when trying to update
For me it worked to do an OTA update with the same version installed.
For example, my phone was rooted to 1.1.7 and I could not update to 1.1.8. So I downloaded 1.1.7 and updated via OTA. After that I could update to 1.1.8 normally. However, the phone must be rooted again.
For the OTA update you have to download the whole OS (https://forum.xda-developers.com/t/...-os-repo-of-nothing-os.4464039/#post-87101175) and then dial *#*#682#*#* in your phone. Now a menu opens in which you can select the OS by browse in the upper right corner. My data has been preserved during the update.
D4yan said:
For me it worked to do an OTA update with the same version installed.
For example, my phone was rooted to 1.1.7 and I could not update to 1.1.8. So I downloaded 1.1.7 and updated via OTA. After that I could update to 1.1.8 normally. However, the phone must be rooted again.
For the OTA update you have to download the whole OS (https://forum.xda-developers.com/t/...-os-repo-of-nothing-os.4464039/#post-87101175) and then dial *#*#682#*#* in your phone. Now a menu opens in which you can select the OS by browse in the upper right corner. My data has been preserved during the update.
Click to expand...
Click to collapse
can you please explain the exact steps?
I'm currently on 1.1.7 rooted with magisk
using some modules and lsposed
Short Guide:
Pretty sure this works across the board with most devices.
If you're doing a OTA and not a manual update:
1. Go into Magisk ~> Uninstall Magisk ~> Restore Images
2. Update via OTA (Do not reboot)
3. Go back into Magisk ~> Install ~> Install to Inactive Slot (After OTA)
4. Reboot
HermitDash said:
Short Guide:
Pretty sure this works across the board with most devices.
If you're doing a OTA and not a manual update:
1. Go into Magisk ~> Uninstall Magisk ~> Restore Images
2. Update via OTA (Do not reboot)
3. Go back into Magisk ~> Install ~> Install to Inactive Slot (After OTA)
4. Reboot
Click to expand...
Click to collapse
tried this. after uninstall magisk by restore images, tried to update via OTA and still getting installation problem
Ashiq.makkar said:
tried this. after uninstall magisk by restore images, tried to update via OTA and still getting installation problem
Click to expand...
Click to collapse
How to manually sideload Nothing OS OTA updates on your Nothing Phone 1
To get the latest Nothing OS update onto your Nothing Phone 1 sooner, you can sideload the update manually. Here's how to do it.
www.xda-developers.com
Manually update yourself to the latest and then reroot.
HermitDash said:
How to manually sideload Nothing OS OTA updates on your Nothing Phone 1
To get the latest Nothing OS update onto your Nothing Phone 1 sooner, you can sideload the update manually. Here's how to do it.
www.xda-developers.com
Manually update yourself to the latest and then reroot.
Click to expand...
Click to collapse
tried manual update and keeps getting different source build is required
I was on 1.1.8 rooted with magisk.
My knowledge isnt the best but my way to update is:
1. Deinstall Magisk.
2. Flash stock boot.img (my version was 1.1.8 so i flash stock boot.img from 1.1.8)
3. Install Update normal over stystem updater
4. Reinstall magsik, done.
I tried it also with restoring magisk and update it over OTA. It worked and it installed, but after I installed Magisk to new slot and restart, it bootlooped 3 times and go back to old version. I think the new Android Versions install the update while restarting. So if you install to new slot with magisk you'll reboot with no OS on the Slot installed. I think the best way is just to uninstall magisk, install update and patch boot img