I have noticed this issue with other ROMs as well.I'm on Pie Pixel 9.0 right now with the latest build and latest Magisk version 18.0.It says successfully flashed in TWRP,but after rebooting I can't see the Magisk icon appearing on the homescreen.I have tried previous versions of Magisk as well.On other ROMS I have to flash magisk 4x or even 6x again and again just to make it show on the homescreen and reboot a dozen of times.
Install Magisk Manager app manually.
Related
for some reason whenever I flash supersu or Magisk the phone just hangs at the MI logo with 7.6.15 global beta rom, I do the same flash method every time and this is the first time it has happened..
try 1
zcx twrp, flash 7.6.15, flash supersu, reboot and it doesnt boot
try 2
zcx twrp, flash 7.6.15, flash magisk, reboot and it doesnt boot
try 3
zcx twrp, flash 7.6.15, reboot, -boots fine
edit:
try 4 .
zcx twrp, flash 7.6.15, flash just supersu 2.82, reboot and it boots, so now I can say it has something to do with Magisk or Xposed
so I might now try to flash Magisk, but run the xposed uninstaller incase the magisk.img image still carries xposed module from previous installs this way I can narrow it down from xposed or magisk
I'm having the same issue. I try to flash Super SU after flashing MIUI 7.6.15 and I also try to flash Xposed but it hangs on the Mi logo and won't boot properly. If I hols the power button down for ten seconds to turn the phone off and then get to recovery mode by holding down the volume up button with the power button I can reflash MIUI and it works fine on its own. Wonder is it a Super SU issue? Might try an older version of MIUI....
Same issue, tried everything. :'(
Magisk and zcx super su working but not xppsed niether systemless nor solarwarez editon.
+1
just updated my phone via zcw twrp. su and magisk works fine, only xposed got me stuck at the logo.
No problem with magisk v12, boot normal
Problem with xposed v87, stuck in logo
now back to v7.6.7, and waiting for FIX
Flashed v87.1 xposed
Worked
adiversion said:
Flashed v87.1 xposed
Worked
Click to expand...
Click to collapse
Link?
Sent from my kenzo using XDA Labs
Flash the modified xposed, it's working with the latest global beta. Link:
https://forum.xda-developers.com/xposed/unofficial-xposed-miui-t3367634/page77
Btw: why u guys still use xposed? Any recommendations for modules except YouTube adaway which I should try?
the issue is with SuperSu 2.86, should flash Supersu 2.76, im in build 7.6.8+Supersu 2.76 and all works fine and Xposed not work fine in this builds
Hi guys,
Just got notified that new magisk is available for install. Is it stable and working with the v30 (running Oreo v21a)?
I had a magisk update soft brick some phones before that's why I'm asking...
Cheers
clouds5 said:
Hi guys,
Just got notified that new magisk is available for install. Is it stable and working with the v30 (running Oreo v21a)?
I had a magisk update soft brick some phones before that's why I'm asking...
Cheers
Click to expand...
Click to collapse
See the last few pages of WTF thread. 17.0 boot loops. 17.1 fixes boot loops, but best to uninstall 16 Magisk in TWRP before installing 17.1. Run the uninstaller.
However, there's problems with Magisk Hide on 17.x right now. It crashes for a lot of people.
Thx, I'll stick with 16.0 for the moment. No issues with it and I'm not missing anything so...
17.0 made my stock rom bootloop.
17.1 works fine for me.
It probably makes no difference how you install it, but I used the patch boot image option then flashed the patched boot.img using fastboot.
use dd to get an image of your currently working boot partition
patch that boot.img with magisk manager to 17.1 and copy to PC
use fastboot to flash that patched_boot.img and then reboot (or fastboot boot TWRP.img then reboot from there to be extra safe)
I'm on 21B and that works for me. I have not tried a different way so I can't confirm/deny any other method yet
Sent from my LGE V30 using XDA Labs
21a here i just clean flashed with 17.1 ._.
I'm getting issues with 17.1 and magisk hide.. Is there any fixes? Thanks in advance
So just want to make sure.. can I run the magisk Uninstaller by flashing the zip in TWRP and the flashing 17.1 in TWRP to reinstall magisk?
Hi All,
Just to let people know. I believe the issue is with the Magisk Manager App. I'm currently still using Magisk 17.1. However, I've uninstalled the Magisk Manager and re-installed Magisk Manager 5.8.3 instead. I can now use Magisk Hide without crashing. Maybe others can give this a try as well.
silver311 said:
Hi All,
Just to let people know. I believe the issue is with the Magisk Manager App. I'm currently still using Magisk 17.1. However, I've uninstalled the Magisk Manager and re-installed Magisk Manager 5.8.3 instead. I can now use Magisk Hide without crashing. Maybe others can give this a try as well.
Click to expand...
Click to collapse
This worked for me as well.
1. Uninstall Magisk 16 in TWRP using the latest MagiskUninstaller.
2. Flash Magisk 17.1
3. Boot up and un-install MagiskManager 5.9.1
4. Install MagiskManager 5.8.3.
As expected, the SafetyNet check doesn't work but some of the modules I use are being updated to the new template which prevents them from running on Magisk 16.0.
Anyone know how to get rid of the pop-up to update MagiskManager every time the app is opened?
The lastest pop-up on MagiskManager shows the 6.0 version and the changelog shows that it is designed for Magisk 17.2
Anyone has tried with these new modules?
trekminal said:
The lastest pop-up on MagiskManager shows the 6.0 version and the changelog shows that it is designed for Magisk 17.2
Anyone has tried with these new modules?
Click to expand...
Click to collapse
Yes, discussed over in WTF thread.
https://forum.xda-developers.com/showpost.php?p=77687418&postcount=1798
Thanks.
I updated to MagiskManager 6.0 but it shows me the option to update to Magisk 17.1, not the 17.2
I will wait some days until 17.2 will be available through the main app.
Any else have magisk manager crashing when using selecting #magisk hide from the magisk manager menu?
running 20d us998
with magisk 17.1
magisk manager 6 (although 5.9.1 did the same thing)
and root checker remover
someone on the magisk support thread recommended deleting the hidelist file which didn't really do anything. Problem is still occuring even with the new hidelist.
I rooted my phone this morning and flashed xposed on magisk right after. Also flashed the Google sans font module and the cloudfare module. And then I rebooted the device. But it has been stuck on the boot screen for almost an hour.
Does any one know what could have caused this? Any notable fixes?
Not all magisk modules and xposed are compatible. Flash stock firmware
Most probably its the xposed, there is no way right now to use XPOSED on miui based on 8.1 oreo.
zaydenQ said:
I rooted my phone this morning and flashed xposed on magisk right after. Also flashed the Google sans font module and the cloudfare module. And then I rebooted the device. But it has been stuck on the boot screen for almost an hour.
Does any one know what could have caused this? Any notable fixes?
Click to expand...
Click to collapse
Xposed is the culprit.
Here's how you uninstall problematic magisk module from twrp since you're stuck in bootloop
https://magiskroot.net/uninstall-ma..._Module_with_Magisk_Manager_for_Recovery_Mode
Thanks to everybody for their replies. I flashed the stock ROM using MiFlash tool and it worked. Thankfully didn't lose anything important in the process.
There's a list of "reliable" magisk modules for Poco F1? I just installed AnxCam (MIUI Cam Port) and Youtube Vanced and I'm impressed with'em.
If he uninstalled magisk instead as stated in link below, would that work? Isn't it systemless?
https://magiskroot.net/uninstall-magisk-module-twrp/
I just updated my Redmi Note 3 (mido) to MIUI 11 (global version).
I unlocked the bootloader officially.
- from the Developer option mentioned "Unlocked"
- during bootup, there's "Unlocked" text.
so, I flash TWRP in with ADB (fastboot flash recovery),
then, I flashed Magisk in recovery, with LazyFlasher (in view of I got stuck in bootloop afterwards).
the issues here is,
no SuperUser access - no permission asked when I open BusyBox/Root Checker app.
there's a Magisk icon on the homescreen, no issues opening it.
passed SafetlyNet.
both Magisk Manager, and Magisk ticked green.
any workaround for this?
got it sorted out.
after reading from "https://forum.xda-developers.com/redmi-note-4/help/how-to-upgrade-miui-10-rooted-to-miui-11-t4006971",
noticed there're issues with Magisk 20.1
I downgraded to MIUI 10 (but using the Xiaomi.EU version), used Magisk 20.1, also no root.
so, I used Magisk 20.0, and it works!
:victory:
11.0.3.0 miui global rom installed 2 different Xiaomi Mi 9 phones (one is M1902F1G, other is M1902F1A)
Following procedures were applied to the phone M1902F1G.
1. TWRP is installed M1902F1G phone. (Worked)
2. Magisk 20.3 was installed via TWRP (Worked)
3. Magisk Manager is properly installed on the phone. Working FINE
Following procedures were applied to the phone M1902F1A.
1. TWRP is installed M1902F1A phone. (Worked)
2. Magisk 20.3 has been installed via TWRP (NOT Worked) BOOTLOOP started and TWRP bootloader opened again.
3. After Phone was flashed Magisk Manager Uninstaller, the phone has been working properly.
I have tried all 20.x, 19.x and 18.x versions of Magisk. There was no improvement is observed.
Is there anyone who has any idea to solve the problem?
nukecore said:
11.0.3.0 miui global rom installed 2 different Xiaomi Mi 9 phones (one is M1902F1G, other is M1902F1A)
Following procedures were applied to the phone M1902F1G.
1. TWRP is installed M1902F1G phone. (Worked)
2. Magisk 20.3 was installed via TWRP (Worked)
3. Magisk Manager is properly installed on the phone. Working FINE
Following procedures were applied to the phone M1902F1A.
1. TWRP is installed M1902F1A phone. (Worked)
2. Magisk 20.3 has been installed via TWRP (NOT Worked) BOOTLOOP started and TWRP bootloader opened again.
3. After Phone was flashed Magisk Manager Uninstaller, the phone has been working properly.
I have tried all 20.x, 19.x and 18.x versions of Magisk. There was no improvement is observed.
Is there anyone who has any idea to solve the problem?
Click to expand...
Click to collapse
You can found the solution by searching google Xiaomi Mi9t Recovery bootloop after magisk install #2492, because XDA does not permit link insertion for new users.