Database Develop

Magisk Boot Loop Nexus 6P

Just upgraded magisk to 11 this morning from inside the app and it has been stuck rebooting the past ten minutes. Can anyone help?

can still get into Twrp though if that helps figure out solutions.

I have similar problem, on a OnePlus 3 with a CM13 based Rom.
After the update from 10.2 to 11 the start of Android never finished.
Temporary solution (until I have more time to produce a real bug report or someone else finds the problem) uninstalled Magisk via Uninstaller zip in TWRP and reinstalled Magisk 10.2 there.

Same problem for me on Pure Nexus when installing v11. Stuck on boot screen.

Had to flash Magisk Uninstaller, and re-flash Magisk 11 through TWRP. Seems to work, until I installed ViperFX (through Magisk) and it asked me to reboot - now I'm back in a boot loop.
Going to roll back to Magisk 10.2 until something gets fixed.

Flash the uninstaller script in TWRP and try again. And even if it seems to be bootlooping, let it sit. Mine stayed on boot animation for a good 5-10 minutes the first boot up on v11. If it still seems to be looping, try flashing a clean boot image and start over.
Nexus 6, Pure Nexus 01/21.

Okay, so I finally got it to boot doing the following:
1) Factory Reset
3) Format System
2) Reflash Rom, GApps
3) Boot into Rom
4) Reboot, flash Magisk
5) Boot back into Rom
I think the issue is if you are coming from 10.2 (or earlier) you need to remove SU before flashing magisk. Magisk has SU built in (though should work with SuperSU or phh's for now) but I think there is some issue when upgrading. Maybe try flashing your preferred SU package after you reboot into the rom after Magisk is installed.
---------- Post added at 03:20 PM ---------- Previous post was at 03:16 PM ----------
Didgeridoohan said:
Flash the uninstaller script in TWRP and try again. And even if it seems to be bootlooping, let it sit. Mine stayed on boot animation for a good 5-10 minutes the first boot up on v11. If it still seems to be looping, try flashing a clean boot image and start over.
Nexus 6, Pure Nexus 01/21.
Click to expand...
Click to collapse
Hehe, well, I only just found out about that before I nuked my phone.

OK for me the boot problem was fixed by restoring the boot partition from a backup without Magisk installed and the flashing version 11.
So the problem is mostly cased by something in the boot partition.
If you don't have a backup of the boot partition. Flashing the boot image of the ROM or the hole ROM should fix this.
At lest for me no need to reset everything.

Did a full unroot of supersu, told it to restore the backed up boot image, booted immediately into recovery, flashed magisk and magisksu stuck no problem. I like this all in one solution v11 brings.

It's viper4android now causing the bootloop... I flashed clean with magisk 11.1

lutanica said:
It's viper4android now causing the bootloop... I flashed clean with magisk 11.1
Click to expand...
Click to collapse
agreed. this seems to be unresolved right?

steveo17 said:
agreed. this seems to be unresolved right?
Click to expand...
Click to collapse
Still unresolved yes..

I fixed my bootloop problems doing the following:
1. Booted into recovery (TWRP)
2. Decrypted my data partition
3. Connected the phone to my PC
4. `adb shell`
5. rm -rf /data/magisk /data/magisk.img /data/stock_boot* /data/su/
6. Installed Magisk v11.1 by sideloading the zip
7. Rebooted
Proof:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

steveo17 said:
agreed. this seems to be unresolved right?
Click to expand...
Click to collapse
denvit said:
I fixed my bootloop problems doing the following:
1. Booted into recovery (TWRP)
2. Decrypted my data partition
3. Connected the phone to my PC
4. `adb shell`
5. rm -rf /data/magisk /data/magisk.img /data/stock_boot* /data/su/
6. Installed Magisk v11.1 by sideloading the zip
7. Rebooted
Proof:
Click to expand...
Click to collapse
And you've Viper4android installed and it's functioning?

I only heard about Magisk and its rooting abilities yesterday. So far I have always used SuperSU, but now I'd like to migrate. Now and again I'd like to use my banking app, and it's not allowed on rooted phones. I've tried rootcloak before, but for some reason I can't remember, didn't really work. So I would love it if this solution did.
However, when I install suhide required, it bootloops. So I reflash the whole system, bootloop remains. Only when I flash rm-suhide it does actually boot. But now I have to remove SuperSU and flash root again using the magisk.zip. When I do, it bootloops. Go figure.
I'm on the angler February update N4F26O.
Haven't tried the adb shell solution yet, but just about everything else.

denvit said:
I fixed my bootloop problems doing the following:
1. Booted into recovery (TWRP)
2. Decrypted my data partition
3. Connected the phone to my PC
4. `adb shell`
5. rm -rf /data/magisk /data/magisk.img /data/stock_boot* /data/su/
6. Installed Magisk v11.1 by sideloading the zip
7. Rebooted
Click to expand...
Click to collapse
Verified working with an extra step: after you reboot, remove SuperSU if you have it (app drawer, drag to uninstall). This seems to default the SU method to the MagiskSU, which allows it to pass safety net as well. Before I uninstalled SuperSU, I was getting safetynet fail CTS mismatches.
Also, after doing the quoted method, it did take a little longer than usual booting, give it 5 min at least.
Lastly, Viper4Arise doesn't work (driver won't load), probably because of something related to the new magisk, or because it preferred SuperSU.
Thanks

2hdq said:
I only heard about Magisk and its rooting abilities yesterday. So far I have always used SuperSU, but now I'd like to migrate. Now and again I'd like to use my banking app, and it's not allowed on rooted phones. I've tried rootcloak before, but for some reason I can't remember, didn't really work. So I would love it if this solution did.
However, when I install suhide required, it bootloops. So I reflash the whole system, bootloop remains. Only when I flash rm-suhide it does actually boot. But now I have to remove SuperSU and flash root again using the magisk.zip. When I do, it bootloops. Go figure.
I'm on the angler February update N4F26O.
Haven't tried the adb shell solution yet, but just about everything else.
Click to expand...
Click to collapse
Firstly unroot the SuperSU, flash the latest Magisk zip file v11.1. You don't need the suhide as the latest version of Magisk already has the necessary files to root your device. Hope this helped you

At the risk of sounding dumb, I couldn't figure out how to decrypt my data partition. I don't know if what I did made any actual difference but I did a nandroid of my data, rebooted twrp, restored data, entered the adb command, then installed magisk. Reboot to system, all set!
Hope this helps someone out.
Sent from my Nexus 6P using Tapatalk

I'm getting a constant boot loop (stuck at boot animation) each time I try to install magisk on my Oneplus 3. with OOS 4.0, it worked fine on MM but no go since updating to nougat.
Edit:Fixed it! I hadn't ran the uninstaller first. Once I did this it worked fine. Doh!

Hi on my lg g5 (with fulmics custom rom Android 7.0) magisk 11.1 crashes settings app, any solutions? I could revert back to 10.2?

Can't update magisk to v17

I try and install directly from magisk but when I go and flash the zip through app it says installation failed. Am I doing something wrong?

Me too
I try unistall magisk in recovery but non success
I'm blocked
Edit: i'm return at v16.6 and work
I don't update for Now Walt for more info

Ty for now I'll wait

same here
Edit:- can't go back to v16.0 either,i'm getting "updater process ended with ERROR: 1
Any suggestions?

1. Boot to TWRP
2. Flash latest uninstaller
3. Without rebooting flash Magisk v.17.0
4. Reboot
If needed install manager manually.

Karls0 said:
1. Boot to TWRP
2. Flash latest uninstaller
3. Without rebooting flash Magisk v.17.0
4. Reboot
If needed install manager manually.
Click to expand...
Click to collapse
If I don't have TWRP I just install it? Sorry for noob question but i'm new here

Karls0 said:
1. Boot to TWRP
2. Flash latest uninstaller
3. Without rebooting flash Magisk v.17.0
4. Reboot
If needed install manager manually.
Click to expand...
Click to collapse
Thanks mate,worked for me.

Hi,
I'm running a HTC 10 with Lineage OS 15.1 (8.1.0). I came from Magisk 16 and an update message appeard. I downloaded Magisk 17 and tried to install it via TWRP as usual. The installation stopped with an Error 2. After that I had a boot loop and had to reinstall the Lineage OS. After that it booted again. But I still get this error message when trying to install Magisk 17.
Very odd. Besides of that, GREAT WORK!
Cheers

lmrcarneiro said:
If I don't have TWRP I just install it? Sorry for noob question but i'm new here
Click to expand...
Click to collapse
Magisk uninstaller will not works without custom recovery so i think my instruction is not applicable in this situation.
chaos_since_78 said:
Hi,
I'm running a HTC 10 with Lineage OS 15.1 (8.1.0). I came from Magisk 16 and an update message appeard. I downloaded Magisk 17 and tried to install it via TWRP as usual. The installation stopped with an Error 2. After that I had a boot loop and had to reinstall the Lineage OS. After that it booted again. But I still get this error message when trying to install Magisk 17.
Very odd. Besides of that, GREAT WORK!
Cheers
Click to expand...
Click to collapse
Double check if the package is not corrupted, MD5 should be: 6237bfaf7dcf516b60922b5b26f2dca8.

Karls0 said:
1. Boot to TWRP
2. Flash latest uninstaller
3. Without rebooting flash Magisk v.17.0
4. Reboot
If needed install manager manually.
Click to expand...
Click to collapse
Thanks for this
but now i can't install universal fix for safetynet check

I'm not sure if Magisk v.17.0 is fully backward compatible. Maybe this is preventing the module from installing?

Karls0 said:
1. Boot to TWRP
2. Flash latest uninstaller
3. Without rebooting flash Magisk v.17.0
4. Reboot
If needed install manager manually.
Click to expand...
Click to collapse
thank you very much i installed twrp and followed your steps worked great

Karls0 said:
I'm not sure if Magisk v.17.0 is fully backward compatible. Maybe this is preventing the module from installing?
Click to expand...
Click to collapse
ok so wait for new fix thanks

On my pixel 1 it claims to install, but causes a bootloop. AND updating to the most recent manager breaks using v16. So I'm stuck with an old manager and v16

Yes, the new manager seems to not fit to Magisk v16. In my case it also broke something so I updated to v17.

Karls0 said:
Magisk uninstaller will not works without custom recovery so i think my instruction is not applicable in this situation.
Double check if the package is not corrupted, MD5 should be: 6237bfaf7dcf516b60922b5b26f2dca8.
Click to expand...
Click to collapse
I got it solved by uninstallion the former Magisk package with the uninstaller. After reboot I could reinstall version 17 and until now it works fine. Thanks.

uninstaller for me does not flash for me. error 255 v16 same error and 17.1 wont flash either error 2

Thanks.
I'm able to do the steps without error. But then it is in bootloop. Using redmi note 4g (dior) Dot os

adz63 said:
uninstaller for me does not flash for me. error 255 v16 same error and 17.1 wont flash either error 2
Click to expand...
Click to collapse
Have you tried rebooting TWRP when the errors appear, and where are the logs?
barathrr96 said:
Thanks.
I'm able to do the steps without error. But then it is in bootloop. Using redmi note 4g (dior) Dot os
Click to expand...
Click to collapse
Is this on a clean install of Magisk v17.1? Also, logs...

Didgeridoohan said:
Have you tried rebooting TWRP when the errors appear, and where are the logs?
Is this on a clean install of Magisk v17.1? Also, logs...
Click to expand...
Click to collapse
Thanks.. the device does not belong to me..
for the time being I have installed magisk v16.7 and did installed viper and removed it ..
so when I get the device next time in my hand I will try to flash and take logs..

[ROOT] Galaxy S9 and S9+ Official Stock 8.0 MAGISK - OFFICIAL

Hello everyone this a little guide for rooting your Galaxy S9 and S9+ (EXYNOS) with Magisk Official
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Quote:
READ THIS BEFORE ROOTING DEVICE
- In any case i'm not reponsable of the beginning of the 3rd World War if you find a way to build a time machine with this guide ! So keep your plans of the time machine in a secure place.
- Any of below said method to root will trip knox and void warranty forever.
- Root process needs wipe data so make backup of important data (including Internal Device storage) before proceed.
- As of now you will lose Samsung Pay and Secure folder forever if you root once, even unrooting won't help. (hope in future we can get it working on tripped knox device). Also you may not able to run some banking apps, you can use Magisk Hide
- OTA likely won't work once you root device.
- To unroot device completely, simply flash Samsung stock firmware, Remember, Unrooting won't revokes warranty nor you will be able to use Secure folder/Samsung Pay. Once rooted, these feature gone for you unless some magic happen in future and may find a way to use it.
Click to expand...
Click to collapse
Magisk hide 17.1 isn't working SafetyNet Fail
Take a look at the pictures at the end of this thread.
If your coming from my another thread about the Magisk 16.3 modified
1.Do a /data backup in TWRP
2.Wipe with TWRP
3.Use odin to update to the latest firmware from samsung
4.Root with this guide and restore.
Click to expand...
Click to collapse
How to proceed
1.Enable Developer Option (settings - about phone - Software information - Tap 7 times on build number to activate developer option in settings menu)
2.Enable OEM Unlock from developer option (if you don't have this option it means that your S9 is incompatible)
3.Download TWRP for S9 or S9+
4.Switch Off device
5.Press Vol down + Bixby + Power to reboot to download mode, press volume up when asked to continue to download mode
6.Download Odin and open it, Disable 'Auto reboot' from option menu of Odin
7.Select TWRP (tar image) with AP tab of Odin and Start
8.Once Successfully flashed, you will see 'Passed' in Odin tab
9.Disconnect device and hold Vol down + power till screen goes off, Now immediately press Vol Up + Bixby + Power to reboot to TWRP
10.Select to allow modification
11.From TWRP, Select WIPE menu - Then FORMAT DATA - You need to type 'yes' to perform wipe. WARNING : This will erase all data including Int SD storage from device
12.Once format device completes, go back and select REBOOT' Menu and then - 'RECOVERY', This will reboot to TWRP again
13.Flash no-verity-opt-encrypt-samsung-1.0 and then Magisk (you can also flash a kernel or xposed)
14.Once flash successfully finish, Reboot to System
14.1 Sometimes the manager doesn't install, you need to just install the manager with the link.
15.Open settings - Developer option - Look for OEM Unlock option. It will automaticaly change to unticked after some reboot don't panic! at the disco it's normal.
16.MAKE A BACKUP IN CASE OF BOOTLOADER RELOCK.
Enjoy ! You have your Galaxy S9 or S9+ watched by the organisation rooted.
Q&A:
Hey F10, why my magisk app isn't appearing or crashing when i lunch it ?
You have to delete the related folders of magisk at this path: /data/app
Hello dev, my phone is bootlooping after the flash help me plz.
You missed the dm-verity flash, just flash it.
Hi i tried to flash a kernel and i lost the root. I don't have any backup what should i do ?
Some kernel when flashing re enable the encryption of the / partition so the only way to go back is the backup. Without that you good to wipe and reflash magisk (and loosing all your data).
Does the magisk 17.2 (Beta) works on my Snine ?
Ya it's works.
Links:
Magisk 17.1 official:
[url]https://androidfilehost.com/?fid=962187416754474353[/URL]
Magisk Manager:
https://github.com/topjohnwu/Magisk/releases/download/manager-v5.9.1/MagiskManager-v5.9.1.apk
Xposed Oreo S9:
[url]https://forum.xda-developers.com/showthread.php?t=3034811[/URL]
Twrp S9:
[url]https://twrp.me/samsung/samsunggalaxys9.html[/URL]
Twrp S9+:
[url]https://twrp.me/samsung/samsunggalaxys9plus.html[/URL]

After doing this pc wont recognized phone any idea why?

yehuda2525 said:
After doing this pc wont recognized phone any idea why?
Click to expand...
Click to collapse
Check your driver.

update magisk manager
hi , i have already root my device thanks to you but with 16.3 modified version . so to update it do i need to install the 17.1 directly or i need to uninstalle it and install the new one ? thanx for the help:good:
edit : i did all this but nothing workes .
when i install it directly , after the reboot i found magisk but it crash.
i have uninstall it and reinstall but now there is no icon of it ?

ponthere said:
hi , i have already root my device thanks to you but with 16.3 modified version . so to update it do i need to install the 17.1 directly or i need to uninstalle it and install the new one ? thanx for the help:good:
edit : i did all this but nothing workes .
when i install it directly , after the reboot i found magisk but it crash.
i have uninstall it and reinstall but now there is no icon of it ?
Click to expand...
Click to collapse
Sometimes the manager disappear, you just need to reinstall it.
https://github.com/topjohnwu/Magisk/releases/download/manager-v5.9.1/MagiskManager-v5.9.1.apk

I did it but installation fail !!

Is it possible to install Magisk without TWRP on the S9+ ?
When I try to patch the boot image I get "Repackaging boot image.... ! Installation fail" The Magisk log file everything seems to work then it ends with " Cleaning up.... ! Installation failed" . I can probably patch the boot.img of the S9+ with my S7 Edge. Any idea if this would work?

yahavrave said:
Is it possible to install Magisk without TWRP on the S9+ ?
When I try to patch the boot image I get "Repackaging boot image.... ! Installation fail" The Magisk log file everything seems to work then it ends with " Cleaning up.... ! Installation failed" . I can probably patch the boot.img of the S9+ with my S7 Edge. Any idea if this would work?
Click to expand...
Click to collapse
Update with latest firmware from Samsung.

Not sure what you mean @frauchgu10. I have the latest OTA installed.

yahavrave said:
Not sure what you mean @frauchgu10. I have the latest OTA installed.
Click to expand...
Click to collapse
I don't know why but maybe this version is incompatible with this method. I will maybe do some test about that.

Maybe.. But do you think it wil work if I patched the latest boot image (for the S9+) on another phone (S7 Edge). What will happen if I try to flash it via Odin ?

Everything went smooth! Recovery installed, and rooted.
Thanks!

frauchgu10 said:
I don't know why but maybe this version is incompatible with this method. I will maybe do some test about that.
Click to expand...
Click to collapse
hi there,
im unable to root after the august 1 security patch running stock rom G965FXXU2BRGA_G965FOXM2BRG8_ILO on galaxy s9+
my phone lags then freezes permanently after flashing magisk and booting up . i haven't experienced this before the update
any ideas?
im thinking the update probably broke "No Verify Encrypt" because magisk is unable to keep dm-verity enabled .
i discovered this when opening magisk manager,the checkbox for preserve dm verity is not checked,and when i do enabled it it does nothing.tried restarting too
i tried various methods including issuing "echo KEEPVERITY=true>>/data/.magisk" command in recovery terminal after flashing magisk with no success ( i even tried flashing different magisk version ,latest version then the one before it and another one..etc) tried supersu too . i tried everything in "Magisk and MagiskHide Installation and Troubleshooting guide " documented in Magisk Troubleshoot Wiki (Didgeridoohan!)
my steps to rooting is the following :
enabling OEM unlock if not enabled
flashing twrp 3.2.3.0 star2lte
formating data then rebooting to recovery
Installing No Verify Encrypt 6.0 star zip file then rebooting to recovery again
installing rmm state bypass v2
flashing magisk ( tried different versions,customs ones too ,supersu)
rebooting to system
(gathered from various tutorials from highonandriod or other places)

What features are gone if i rooted my phone other than secure folder and samsung pay?

When rooted you can't update via OTA. Some games can detect root like pokemon go so you can not play these games without doing some tricks.

frauchgu10 said:
When rooted you can't update via OTA. Some games can detect root like pokemon go so you can not play these games without doing some tricks.
Click to expand...
Click to collapse
Okay, any others than that?

frauchgu10 said:
When rooted you can't update via OTA. Some games can detect root like pokemon go so you can not play these games without doing some tricks.
Click to expand...
Click to collapse
could you help me with my problem?
im having trouble with my device rooting,after the first boot my device freezes up and wont respond.
it seems that samsung patched some of the vulnerabilities used by the bypasses to achieve root,
after the august update. the device is unable to sustain the NO Verity OPT encrypt , the device seems to re-encrypt it self after the first boot
thanks alot man

mrwan74 said:
could you help me with my problem?
im having trouble with my device rooting,after the first boot my device freezes up and wont respond.
it seems that samsung patched some of the vulnerabilities used by the bypasses to achieve root,
after the august update. the device is unable to sustain the NO Verity OPT encrypt , the device seems to re-encrypt it self after the first boot
thanks alot man
Click to expand...
Click to collapse
I see Samsung reinforced the security I'm trying to do something about that. If you want a stable rom I suggest you to install the soldier9312 rom:
https://forum.xda-developers.com/ga...fd-n-stock-rom-soldier9312-1-0-t3771346/page1

frauchgu10 said:
I see Samsung reinforced the security I'm trying to do something about that. If you want a stable rom I suggest you to install the soldier9312 rom:
https://forum.xda-developers.com/ga...fd-n-stock-rom-soldier9312-1-0-t3771346/page1
Click to expand...
Click to collapse
okay thanks alot man i appreciate it

@frauchgu10
i came upon some new information that maybe would be helpful
ashyx ,a recognized contributor to the xda community said ,and i quote the following :
"Since Oreo Dm-verity flags are no longer in the Ramdisk. The flags are dtb based.
If the dtb isnt patched or dm-verity disabled in the kernel source then rooting will likely cause a boot loop.
Same goes for disabling forced encryption, the flags are no longer in the Ramdisk fstab, but usually located in the Vendor partition.
Magisk attempts to hex patch the kernel, but when Samsung update the firmware the hex patch offsets change and patching fails."
i hope this helps man
I truly appreciate everyone’s efforts and commitments Thank you for taking time out of your personal time to this :good::good::good::good:

magisk doesn't apply when flashing

Hello guys,
I made an update in TWRP and installed Havoc 2.4 to try it. After 1 hour I restored my backup and changed back to MIUI. I couldn't log in, so I cleaned the keyfiles to set a new pin.
I reflashed new Beta (25.4 MIUI - Xiaomi.eu) ROM and Magisk but root does not apply on my device... What is wrong? Seems that it's not possible to root anymore... Its does not give me any fails when installing the magisk 18.1 zip in TWRP...
thanks in advance

Have you tried a simple reboot? Usually it takes a reboot more to apply.

no it's not that. now its always booting into twrp when I try to flash magisk

makmak001 said:
no it's not that. now its always booting into twrp when I try to flash magisk
Click to expand...
Click to collapse
Extract the boot.image from the rom and place it in your downloads folder.
Now with Magisk Manager , download and install Magisk to that boot image
Magisk will write root to the boot.image file and then will automatically flash the the updated boot image, and restart to system >>> Issue resolved.

I fixed it by wiping data... now its working

tsongming said:
Extract the boot.image from the rom and place it in your downloads folder.
Now with Magisk Manager , download and install Magisk to that boot image
Magisk will write root to the boot.image file and then will automatically flash the the updated boot image, and restart to system >>> Issue resolved.
Click to expand...
Click to collapse
I have the same problem with magisk, after weekly update and after magisk installed, boot only TWRP. I tried with18.1 version but will not recognise. Boot image and Magisk 19.1 are in downloads but no success. Anyway, with this weekly update all people have loosen magisk, I have read in Xiaomi forum.

slave2007 said:
I have the same problem with magisk, after weekly update and after magisk installed, boot only TWRP. I tried with18.1 version but will not recognise. Boot image and Magisk 19.1 are in downloads but no success. Anyway, with this weekly update all people have loosen magisk, I have read in Xiaomi forum.
Click to expand...
Click to collapse
Nope, no issues on my Mi 8. Here is the trick. When updating do not flash Magisk until you out have booted into the system and ran updates and deleted cache and trash, then reboot to recovery and flash Magisk.
If the method that I described before in the previous post doesn't work, then unpack the boot image from the update and flash it to boot in recovery then flash Magisk Canary debug.
I have been doing this for every weekly update using the beta ROM.
I had an issue just once that was resolved by flashing SuperSu, booting to system confirming root, then reboot to recovery and removing Su, flashing the boot and Magisk Canary
Sent from my Xiaomi MI 8 using XDA Labs

slave2007 said:
I have the same problem with magisk, after weekly update and after magisk installed, boot only TWRP. I tried with18.1 version but will not recognise. Boot image and Magisk 19.1 are in downloads but no success. Anyway, with this weekly update all people have loosen magisk, I have read in Xiaomi forum.
Click to expand...
Click to collapse
Here you can see that I have root and latest update
Sent from my Xiaomi MI 8 using XDA Labs

tsongming said:
Nope, no issues on my Mi 8. Here is the trick. When updating do not flash Magisk until you out have booted into the system and ran updates and deleted cache and trash, then reboot to recovery and flash Magisk.
If the method that I described before in the previous post doesn't work, then unpack the boot image from the update and flash it to boot in recovery then flash Magisk Canary debug.
I have been doing this for every weekly update using the beta ROM.
I had an issue just once that was resolved by flashing SuperSu, booting to system confirming root, then reboot to recovery and removing Su, flashing the boot and Magisk Canary
Click to expand...
Click to collapse
Man has found the guilty in Xiaomi.eu/community.
It is not Magisk, but Viper 4.2. I have flashed Magisk, after reboot again in recovery and wanted to flash version 4.1. It was uninstalled, have no Viper, but Magisk is installed ?

slave2007 said:
Man has found the guilty in Xiaomi.eu/community.
It is not Magisk, but Viper 4.2. I have flashed Magisk, after reboot again in recovery and wanted to flash version 4.1. It was uninstalled, have no Viper, but Magisk is installed ?
Click to expand...
Click to collapse
I no longer use Viper because my phone has 1 speaker and for me Ainur Sauren works pretty well for all sounds.
For listening to music I have the Pro version of Power amp which has every wanted option such as dynamic compression, dynamic EQ, convolution reverb, limiting , tag editing, visualizations etc, I bought it 5 years ago for $3. Best 3 bucks that I ever spent!
Seriously, I can't recommend Poweramp highly enough, its worth its weight in gold.
Sent from my Xiaomi MI 8 using XDA Labs

TWRP and Magisk help

Hi everyone.
So I had a moto x4 for about year and a half before fricking up the charging port. So I recently acquired another one. Everything went smoothly the first month or so, with twrp properly installed and magisk too, but then I tried to install a magisk module and the phone bricked. I tried restoring via twrp backup but it didn't work and I ended up in a bootloop. So I flashed a stock rom. And when I wanted to install twrp it just didn't stick after a reboot and magisk would just get my phone stucked on the splashscreen.
I realized that, for whatever reason, a previous version of magisk would work (magisk 18.1) but I've no idea why. Magisk 18.1 is the only version that works. If I flash any other version from twrp my phone gets stuck on the splashscreen, same if I update magisk via magisk manager. And if I try to install any magisk module my phone won't start. But root permission works fine on other apps i.e. system app uninstaller, root explorer or swift installer.
Does anyone have any idea? It'd be greatly appreciated.
Thanks!!

Organics said:
Hi everyone.
So I had a moto x4 for about year and a half before fricking up the charging port. So I recently acquired another one. Everything went smoothly the first month or so, with twrp properly installed and magisk too, but then I tried to install a magisk module and the phone bricked. I tried restoring via twrp backup but it didn't work and I ended up in a bootloop. So I flashed a stock rom. And when I wanted to install twrp it just didn't stick after a reboot and magisk would just get my phone stucked on the splashscreen.
I realized that, for whatever reason, a previous version of magisk would work (magisk 18.1) but I've no idea why. Magisk 18.1 is the only version that works. If I flash any other version from twrp my phone gets stuck on the splashscreen, same if I update magisk via magisk manager. And if I try to install any magisk module my phone won't start. But root permission works fine on other apps i.e. system app uninstaller, root explorer or swift installer.
Does anyone have any idea? It'd be greatly appreciated.
Thanks!!
Click to expand...
Click to collapse
Please help me to root Moto X4, bootloader unlocked

hrushikesh.inc said:
Please help me to root Moto X4, bootloader unlocked
Click to expand...
Click to collapse
Wrong thread.
https://forum.xda-developers.com/moto-x4/help/moto-x4-f-q-s-thread-t3814393