Hello. I'm stuck in a bootloop and need help. I have android 7.1.1 with the October security update and the latest franco kernel. Bootloader is unlocked. Here is what happened.
Flashed TWRP and rooted with magisk. Attempted to install xposed SDK25 module through magisk. Restarted phone and xposed did not show up in magisk as installed, all my other modules were also gone.
I'm now thinking that magisk is somehow broken so I attempt to uninstall it through the manager. Phone reboots and is now in a bootloop.
What should I do?
A new install of course.
Press vol down and on/off at the same time.
Go to Recovery.
In TWRP Wipe system/data/cache.
Install your rom and gapps again and reboot system.
See if this solves your boot loop.
If it boot correctly, then install your custom apps.
@ReneZeiss: He doesn't need to wipe data or cache to resolve this. Doing so would be overkill. All he needs to do is reinstall the ROM, because from his description it sounds like his kernel ramdisk became corrupted when Magisk tried restoring the untouched version.
@sandman96: You don't say whether you're running the stable version of Magisk (14.0) or are on the beta channel (14.6). If the problem occurred on the beta channel, switch to the stable channel. If on the stable channel, try the beta channel. Also, after reinstalling your ROM, but before installing Magisk, take a nandroid backup.
Strephon Alkhalikoi said:
@ReneZeiss: He doesn't need to wipe data or cache to resolve this. Doing so would be overkill. All he needs to do is reinstall the ROM, because from his description it sounds like his kernel ramdisk became corrupted when Magisk tried restoring the untouched version.
@sandman96: You don't say whether you're running the stable version of Magisk (14.0) or are on the beta channel (14.6). If the problem occurred on the beta channel, switch to the stable channel. If on the stable channel, try the beta channel. Also, after reinstalling your ROM, but before installing Magisk, take a nandroid backup.
Click to expand...
Click to collapse
Thanks for the replies. I ended up reflashing from a factory image. Was able to restore all my data except for text messages but I'm working on getting those from a twrp backup.
I had the stable version of magisk installed. I'm just not going to try the xposed framework again lol.
I find Xposed to be more trouble than it's worth. I only used it on my Dell Streak as there were some patches for Android 2.3.x that were never integrated into the ROMs I produced for that device. I briefly tried it on my Galaxy S4 and promptly uninstalled it. My N6 never had it.
Xposed fans don't like me much, mostly because I wish it would go die in a fire.
The few times I tried installing Xposed thru the Magisk Repo caused Magisk to screw up for me too. Solution is just install the Xposed app then flash Xposed in TWRP lol. For some reason the Repo install method doesn't seem to work often if at all, least for me lol. Flashing in TWRP like you would if you had SuperSU has worked 100% of the time for me :-/
::Edit:: oh yea lol, if you take anything from the experience take the lesson learned of why TWRP makes it extremely simple to make a complete backup of everything disable compression of backups and that minute or two of extra wait time is worth it when something happens, since it's not a matter of IF, only a matter of WHEN lol.
Related
Hello,
I have a problem with my 3T. I updated magisk yesterday via magisk manager from 11.2 to 11.5. After the update my screen was completely black, the funny thing is if I press my power button long enough the reboot menu pops up. I can boot into recovery, the bootanimation is working but the ROM itself isn't visible.
I tried reflashing magisk via recovery, ROM+magisk via recovery, ROM via recovery and uninstalled magisk via recovery. Nothing works, the last thing I can try is a complete factory reset.
Does anyone has maybe an idea what else I can do?
I would appreciate any form of hint
yup i had the same thing, used the brick recovery tool and was fine but when i re unlocked the bootloader i forgot it wipes internal data and lost all my pics music and titanium backups. Very annoyed to say the least.
EuEra said:
yup i had the same thing, used the brick recovery tool and was fine but when i re unlocked the bootloader i forgot it wipes internal data and lost all my pics music and titanium backups. Very annoyed to say the least.
Click to expand...
Click to collapse
That solved my issue, didn't realize that I really bricked my device. Sadly it wiped my data also!
Thanks for your advice!
I've experienced this about 3 times over the last 4 months, and had to restore a full backup each time. Basically afraid to do anything with Magisk at this point. This really needs to be fixed.
It's probably because the Magisk updater is interfering with the kernel.
Every time Magisk is updated, I always dirty flash my current ROM and flash the new version of Magisk over it. I can then flash a custom kernel and everything still works flawlessly.
Anova's Origin said:
It's probably because the Magisk updater is interfering with the kernel.
Every time Magisk is updated, I always dirty flash my current ROM and flash the new version of Magisk over it. I can then flash a custom kernel and everything still works flawlessly.
Click to expand...
Click to collapse
I did that when i switched from official to open beta, and everything went fine, then i installed a module, rebooted and got blackscreen again
Anova's Origin said:
It's probably because the Magisk updater is interfering with the kernel.
Every time Magisk is updated, I always dirty flash my current ROM and flash the new version of Magisk over it. I can then flash a custom kernel and everything still works flawlessly.
Click to expand...
Click to collapse
It's not the kernel, the black screen has occurred twice when just installing a module with no modifications to /boot.
dre-z said:
Hello,
I have a problem with my 3T. I updated magisk yesterday via magisk manager from 11.2 to 11.5. After the update my screen was completely black, the funny thing is if I press my power button long enough the reboot menu pops up. I can boot into recovery, the bootanimation is working but the ROM itself isn't visible.
I tried reflashing magisk via recovery, ROM+magisk via recovery, ROM via recovery and uninstalled magisk via recovery. Nothing works, the last thing I can try is a complete factory reset.
Does anyone has maybe an idea what else I can do?
I would appreciate any form of hint
Click to expand...
Click to collapse
Fix for me was to boot twrp, manually wipe system, data, caches etc (NOT internal storage box), then clean install the OS in twrp. Keeps your data and encryption then.
Just happened again. Ugh. Anybody manage to recover their existing data partition from this?
---------- Post added at 01:21 PM ---------- Previous post was at 01:15 PM ----------
I think this is the fundamental issue: https://github.com/topjohnwu/Magisk/issues/185
I've not experienced anything like this on my OP3T. I did see something similar on my Nexus 6 a couple of times, but could never quite get a grip on what caused it (I had a lot of other issues with that device ).
Is there any particular module that has been known to cause the issue (for testing)?
Didgeridoohan said:
I've not experienced anything like this on my OP3T. I did see something similar on my Nexus 6 a couple of times, but could never quite get a grip on what caused it (I had a lot of other issues with that device ).
Is there any particular module that has been known to cause the issue (for testing)?
Click to expand...
Click to collapse
Nope, I've had this happen with multiple modules, including App Systemizer, ad-free YouTube, and OP3/T channel bonding enabler. Based on the file size changes in magisk.img, I legitimately think that the linked GitHub issue is the root cause. I think the only consistent repro is to flash different versions of modules while rebooting repeatedly.
Problem might be corrupted magisk.img during resize.
vemacs said:
Just happened again. Ugh. Anybody manage to recover their existing data partition from this?
---------- Post added at 01:21 PM ---------- Previous post was at 01:15 PM ----------
I think this is the fundamental issue: https://github.com/topjohnwu/Magisk/issues/185
Click to expand...
Click to collapse
I had the same issue when trying to install xposed 87.1 through MagiskManager (black screen and repeated vibration).
On my J5 I just removed the battery and booted into twrp, then I uninstalled magisk with the uninstall-zip, wiped dalvik an cache, rebooted once and everything works.
I reinstalled magisk in twrp and installed xposed 87.0 through the material xposed-installer and everything works.
No data loss.
The issue on GitHub was closed with a comment saying that it's likely fixed in latest Magisk (13.1). FWIW I haven't seen it occur after running 13 beta for a while.
My op3 was bricked again today after the update. Funny thing is, this time I had not installed any module. So the problem doesn't seem to be fixed.
pls someone should help me i tried to root my android v10 infinix note8i with magisk patch boot img file using adb fastboot when i tranfer the file and reboot the phone is not booting and not gettig into recovery mode, just blank screen when a turn on pls help me out with solution
same but my problem is kind of stupid because someone rooted my phone in another way and magisk says it is installed and needs updating but it is actually not and the biggest problem is when i unroot my phone the stupid rmm locks gets enabled and boom i can't open twrp recovery because it is not an offical binary so i got stuck there i flashed a stock rom got it fixed but i still can't do it
Hi guys,
i tried some Roms for my op3 (sultans 14.1 / OOS OB) and always got WiFi problems, when installed Magisk + some modules. (Google Assistant Enabler and Dolby Atmos Lenovo with audiolib v4)
Running Magisk alone, it did not has problems. Also it seems that the problems came with Android 7, but unsure.
Could only be fixed by clean flashing the rom (dirty flashing and uninstalling Magisk did not help).
Someone can explain, how it is possible?
kmsg was something like wifi couldnt suspend device, and did a random reboot. before it rebooted it could not connect to any WiFi-network.
if needed, i can add some more complete logs
Code:
[ 324.876840] PM: Some devices failed to suspend, or early wake event detected
[ 325.063045] legacy_suspend(): wiphy_suspend+0x0/0x68 returns -11
cl0g said:
Hi guys,
i tried some Roms for my op3 (sultans 14.1 / OOS OB) and always got WiFi problems, when installed Magisk + some modules. (Google Assistant Enabler and Dolby Atmos Lenovo with audiolib v4)
Running Magisk alone, it did not has problems. Also it seems that the problems came with Android 7, but unsure.
Could only be fixed by clean flashing the rom (dirty flashing and uninstalling Magisk did not help).
Someone can explain, how it is possible?
kmsg was something like wifi couldnt suspend device, and did a random reboot. before it rebooted it could not connect to any WiFi-network.
if needed, i can add some more complete logs
Code:
[ 324.876840] PM: Some devices failed to suspend, or early wake event detected
[ 325.063045] legacy_suspend(): wiphy_suspend+0x0/0x68 returns -11
Click to expand...
Click to collapse
Remove all modules and reboot into recovery.
Wipe caches and reboot.
I have found that I can end up with WiFi, Bluetooth, SIM issue if something happens with the modules.
Before I figured out what it was, I was re-installing the ROM, etc.
Try just deleting the modules and wiping the caches and rebooting.
@tech_head
Thanks for your answer, but this was unnecessary.
I did not ask for a solution to resolve this on my phone, but a explanation, how Magisk(+modules) mess with kernel/firmware or something.
If you read the whole post, then you would have seen, that it was fixed by clean flashing the Rom.
Thanks anyway.
cl0g said:
@tech_head
Thanks for your answer, but this was unnecessary.
I did not ask for a solution to resolve this on my phone, but a explanation, how Magisk(+modules) mess with kernel/firmware or something.
If you read the whole post, then you would have seen, that it was fixed by clean flashing the Rom.
Thanks anyway.
Click to expand...
Click to collapse
Hi,
I actually did read the whole post and was offering a solution that DID NOT require re-installing the ROM.
I'm not 100% sure why the problem persist but I have seen it affect Bluetooth, Wireless and SIM recognition.
Typically it happens after a reboot. Wiping the cache on my phone causes it more than 50% of the time if I don't disable modules first.
I don't know why it happens but you are right, removing Magisk does not solve the problem.
There is something corrupted in the data partition and the only way to clean that up is to remove the modules and wipe the cache or do what you proposed.
Nevermind
I recently had the same problem. I'm currently trying to fix it without reinstalling. I've uninstalled all modules, cleared both caches and still no wifi and I'm getting random crashes. Has anyone found fix a reliable fix?
While posting, I tried resetting my network and everything started working again. If this happens again, I'll try that first.
BTW
Also, it happened after a failed installation of Crossfire and Tethering, both thru Magisk. Tethering actually installed but after the reboot, I've got no wifi.
I was able to fix the wifi problem by following this tutorial: https://************/root-razer-phone-fix-wifi-root/
But: JUST UNTIL INSTALLING TWRP INSTALLER. Until this step I got a working wifi (I am on Android Pie Custom rom). After flashing Magisk v18 or v19 same problem as before: No more wifi. Su installer does not work on my Razer Phone 1 ( failure while patching sepolicy, no permission ), so what to do? Any hints?
Best regards and thx in advance
Michael
mellus said:
I was able to fix the wifi problem by following this tutorial: https://************/root-razer-phone-fix-wifi-root/
But: JUST UNTIL INSTALLING TWRP INSTALLER. Until this step I got a working wifi (I am on Android Pie Custom rom). After flashing Magisk v18 or v19 same problem as before: No more wifi. Su installer does not work on my Razer Phone 1 ( failure while patching sepolicy, no permission ), so what to do? Any hints?
Best regards and thx in advance
Michael
Click to expand...
Click to collapse
Ugh. I'm having the same issues after upgrading to canary channel Magisk 20.4 on my Razer Phone 2. My WiFi was rock solid on the previous version, but for some reason my WiFi now flashes on and off like a strobe. Weirdly, it doesn't seem to have the issue at my house, but it constantly craps the bed at my work. The work connection is 5Ghz and my home one is 2.4Ghz, so that could be a difference. However, before my attempted upgrade, both worked perfectly.
I tried uninstalling my Magisk modules, flashing the Razer stock boot image, wiped Dalvik cache, flashed Arter/TWRP boot image, Arter kernel zip, Magisk 20.3 stable and reactivating modules. No change at all. WiFi is still garbage.
Are you telling me I'm going to have to flash the entire stock image and wipe my phone to get back full functionality?
im having the same problem, on miui i tried tp downrage magisk, that worked. currebtly searchin best way to downrage cause i forgot what i did. but if anyone stuck at this problem:
Without data wiping (luck method):
Remove modules
Reboot into recovery
wipe caches
reboot
done
Downrage magisk (maybe not fix):
Uninstall ALL modules
Delete Magisk from the app
flash downrage magisk
(eg. uninstall 24.1, install 23.0)
wipe caches
reboot
done
Data wiping (i forgot about should we flash magisk via magisk app with recovery mod on, if this dont work try enabling recovery mode):
Just Re-install Magisk via recovery
Clean everything BUT leave boot not wiped
flash rom WITHOUT boot
let it 10-30 minutes booting
go to recovery
flash rom's stock boot
reboot
finish rom's installation
install MAGISK APP
confirm additional installation
reboot
done
So here are a few things I have been through in the past 48 hours:
I flashed a custom ROM (FreedomOS) for the 3T. Could not get OK Google to work and it is essential to me especially when driving. Other people had mentioned every custom ROM was like this at the moment so I made the switch back to factory. This is where the hell begins. I wanted to try out Magisk so I could play Pokemon GO and use Android Pay, and I thought "oh what a perfect time to do just that". 4 hours of work and the SafetyNet was still tripping, only to find out I needed Magisk 13.0, which is incompatible with the OP3T boot image. Now, that could have been because I installed SuperSU prior and that patches the boot image but I had been through enough to the point of just going stock with SuperSU only. So about 10 dirty flashes later and a few hours of waiting for TWRP to load (F2FS can suck my @#$*), I find out that if you don't want to lost your data partition, there is only one very specific way to install SuperSU.
1) Wipe system and caches
2)Install OOS full rom
3)Boot into OS
4)Reflash TWRP (because OOS removes it)
5)Flash SuperSU
6)Boot into OS again
7)THEN, and only THEN can you install additional things such as ARISE or custom fonts
It appears after you flash the factory ROM through TWRP, TWRP loses all commands. So anything flashed after that doesn't actually do anything. I thought maybe it was because the new recovery is there and so maybe TWRP just needed to be reflashed before the OS was even booted, that however, resulted in a beautiful slew of corrupted fonts, no root access and broken hardware keys (even the power button). So please, learn from this XDA users, as I have the hard way. Now I'm off to go change F2FS to EXT4, fun stuff.
EDIT: On top of everything I just said, it seems none of the SuperSU zips are working now. Does not affect my phone whatsoever. It's almost like it isn't mounting /system...
EDIT 2: Great. Rooting now bootloops me and the logcat is saying AtCmdFwd service errors and BindNDK sensor server unavailable. I'm going back to FreedomOS and will just suffer from never having OK Google again.
EDIT 3: FreedomOS no longer even starts booting. Stuck at bootloader logo. Guess I'm flashing stock OOS unrooted for now. Going to have to deal with ugly default fonts and crappy audio
Try blusparks twrp for OnePlus 3t.. that fixed a lot of my issues with flashing, instead of supersu try magisk instead.
Install twrp - OOS - Magisk - Kernel - what ever else.. but see if it boots. If not, try holding the power button for 12-15 seconds until the screen goes black but the notification led turn red.. plug your phone into the computer and do a unbrick from there with the msm tool.. once it all boots, flash a custom rom over the stock rom and then factory reset from there, I'm just throwing ideas out there.
1. Factory reset.
2. Install official OOS.
3. Reboot to recovery.
4. Install TWRP.
5. Install Magisk, custom kernel, debloater etc.
6. Reboot to OOS.
When upgrading to newer OOS version, skip factory reset. I never wipe caches and everything works. If safety net fails, check that hide is enabled on Magisk settings. If still failing, use Universal SafetyNet Fix.
Forget SuperSu, Magisk does same thing. And with Magisk you can play PoGo. Forget EXT4, it doesn't give you anything, it's going to be history.
Where are you getting that Magisk 13 is incompatible? I'm currently running OB10 with Magisk 13 and ElementalX kernel. Rooted, SafetyNet pass. @heiskanenej instructions above sound like what you need to do. Start fresh.
Solved
xKroniK13x said:
Where are you getting that Magisk 13 is incompatible? I'm currently running OB10 with Magisk 13 and ElementalX kernel. Rooted, SafetyNet pass. @heiskanenej instructions above sound like what you need to do. Start fresh.
Click to expand...
Click to collapse
Ok, I will eventually try blu_sparks TWRP (that was the plan anyways), but I am back in working order. So Magisk did not bootloop my device, and v13 works on OOS. It wasn't working on FreedomOS but it even passes SafetyNet on OOS. I have ARISE and Dolby installed and couldn't be more satisfied. Did not have to wipe /data, it's like the whole thing never even happened. I will likely change to EXT4 as soon as I get the chance to backup my data partition, I haven't seen any benefit to F2FS whatsoever. Appreciate the tips, XDA rocks!
EDIT: Still takes forever to boot blu_spark TWRP but eh, I'll keep it. Will update when switch to EXT4, only reason to switch
I do the flashing in a rude way
1. Flash OOS from TWRP.
2. Flash magisk, arise, etc..
3. Reboot
4. Boot into recovery, flash any custom kernel etc..
Changing to ext4 is not required, if you are on OOS. f2fs is way better in performance over ext4 for the stock/freedom.
Sent from my OnePlus 3T using Tapatalk
Question for those you you way smarter than I'll ever hope to be. I randomly lost root and TWRP on my 3T and I have no idea how this happened.
Quick (or not so quick) background - I was stock rooted OOS 4.1.6. I disabled AdAway for a bit yesterday to gain access to something it was blocking (done it many times) and when I re-enabled it my phone was stuck in a boot loop afterwards. Weird, but not concerning. I booted into TWRP and restored a backup. OOS 4.1.3 was my latest backup, so after successfully loading that up, I flashed the full 4.1.6 OTA and SuperSu as I've done before to update. Worked fine. Was adding my preferred mods via Substratum and Magisk and I messed up. Couldn't get Substratum to work properly and couldn't get Magisk to update to 13.1. I verified I had root, which I did. Went back to TWRP and reflashed 4.1.6 and SuperSU. When my phone was up and running again I didn't have root. Weird, so I tried again, still couldn't get SuperSU to flash properly. Got frustrated and figured I haven't had a clean install since getting the device in January. Every update I've flashed via TWRP has been dirty. So, factory reset, blah, blah, blah. Done it plenty of times with many devices. Flashed the OTA and SuperSu again, but noticed SuperSu failed. Rebooted recovery to try again, but it went to the stock recovery. My phone is working fine now, but I'm without root and I no longer have TWRP.
What might have caused this to happen? And how can I avoid it in the future? I know how to get it back (I'll do it after work) but it's frustrating.
What version of TWRP are you using? A few of the past versions have been having problems.
If you're already using Magisk anyways, just flash the Magisk zip and use that as your rooting solution. IIRC, the more recent versions of Magisk are no longer compatible with SuperSU anyways.
Anova's Origin said:
What version of TWRP are you using? A few of the past versions have been having problems.
If you're already using Magisk anyways, just flash the Magisk zip and use that as your rooting solution. IIRC, the more recent versions of Magisk are no longer compatible with SuperSU anyways.
Click to expand...
Click to collapse
I was using 3.0.4-1. Never had an issue before. But after I factory reset my phone and clean flashed the 4.1.6 update I ended up with the stock recovery. Unless I'm mistaken, I can't flash Magisk until I have TWRP again. I know how to get it back, I was more curious as to how this may have happened in the first place. What would have caused my root and custom recovery to disappear?
Rodeojones said:
I was using 3.0.4-1. Never had an issue before. But after I factory reset my phone and clean flashed the 4.1.6 update I ended up with the stock recovery. Unless I'm mistaken, I can't flash Magisk until I have TWRP again. I know how to get it back, I was more curious as to how this may have happened in the first place. What would have caused my root and custom recovery to disappear?
Click to expand...
Click to collapse
My mistake, I meant to ask SuperSU version, not TWRP. If SuperSU failed to root your phone after dirty flashing OOS (even if there was not error message), OOS will replace your recovery with the stock one.
Anova's Origin said:
My mistake, I meant to ask SuperSU version, not TWRP. If SuperSU failed to root your phone after dirty flashing OOS (even if there was not error message), OOS will replace your recovery with the stock one.
Click to expand...
Click to collapse
I was using version 2.8.2. Regardless, you answered my question as to how it happened in the first place, so thanks.
i run china k20 pro on indian miui 11.01.0
i installed twrp -21 version
installing magisk 20 provides root access however magisk manager asks to something which results in bootloop to recovery
ignoring that request, the module i wanted to install [energized ] asks for updating to magisk 20.1 which also leads to bootloop to recovery.
is there anything to do ? or just wait for magisk 20.2 to be released and then try it
p.s installing magisk was the only way to prevent redmi recovery from overwriting twrp, i don't know if this has any importance
i'm in kinda similar situation ,
installed magisk v20.1 and everything went fine , but when trying to install viper4android it asked me do install busybox , i did it within magisk now it only boots to fastboot , to fix it and make it boot agian i used magisk_uninstaller.zip
boots fine now but can't install magisk again if i do that it will stuck on fastboot screen .
so for your case i suggest using magisk uninstaller.zip
but hope that some one help to install magisk agian
eLcTrOn said:
i'm in kinda similar situation ,
installed magisk v20.1 and everything went fine , but when trying to install viper4android it asked me do install busybox , i did it within magisk now it only boots to fastboot , to fix it and make it boot agian i used magisk_uninstaller.zip
boots fine now but can't install magisk again if i do that it will stuck on fastboot screen .
so for your case i suggest using magisk uninstaller.zip
but hope that some one help to install magisk agian
Click to expand...
Click to collapse
yeah i used magisk uninstaller to make the phone work normally
Glad it worked . Are u able to install magisk again ?
eLcTrOn said:
i'm in kinda similar situation ,
installed magisk v20.1 and everything went fine , but when trying to install viper4android it asked me do install busybox , i did it within magisk now it only boots to fastboot , to fix it and make it boot agian i used magisk_uninstaller.zip
boots fine now but can't install magisk again if i do that it will stuck on fastboot screen .
so for your case i suggest using magisk uninstaller.zip
but hope that some one help to install magisk agian
Click to expand...
Click to collapse
Dont install Viper4android via magisk. Just download the package and install in via TWRP. Use this guide
I have this exact problem right now but even with other versions of magisk, I encounter the same issue. Any suggestions?
Same problem here with magisk I guess it is a compatibly issue with MIUI 11
Yep, it's a MIUI11 issue and the reason I haven't shifted over to it. I suspect whatever release of magisk is in the pipeline will fix it provided it's been reported.
In the meanwhile I've read 19.4 works; you could try the canary builds if that seems to old for your liking... just be careful.
Had the same problem, its because of data encryption.
You guys need to format data before installing magisk.
winesh said:
Had the same problem, its because of data encryption.
You guys need to format data before installing magisk.
Click to expand...
Click to collapse
Even with data formatting 20.1 causes issues: In fact, it seems latest Magisk build seems to be causing issues on all (or, many) builds of MIUI 11.
For k20 pro, 19.3/.4 seems smartest to install and then update via magisk manager
I believe other phones (mi 9?) need even older versions like 17.2, so I wouldn't be surprised if future updates continue to push the installation build back.
AvgZing said:
Even with data formatting 20.1 causes issues: In fact, it seems latest Magisk build seems to be causing issues on all (or, many) builds of MIUI 11.
For k20 pro, 19.3/.4 seems smartest to install and then update via magisk manager
I believe other phones (mi 9?) need even older versions like 17.2, so I wouldn't be surprised if future updates continue to push the installation build back.
Click to expand...
Click to collapse
I'm hoping the Magisk situation gets fixed. I checked the Magisk support thread and only saw one post about a bootloop with a Mi9T Pro (again, likely data encryption) so I'm given the impression MIUI might be off the radar for Magisk bug fixes.
I've had a couple of issues with Magisk 20.1 on MIUI10 - nothing critical but a couple times Magisk Manager has frozen (i.e. kill the process, relaunch and it works) and a couple hangs when root apps have been launched for the first time (again, kill + relaunch, a few times if necessary). Smooth sailing otherwise but gives me the impression that Magisk isn't without flaws on MIUI. One response was to dump MIUI altogether but I'd rather have a stable hardware experience for now. I tested a lot of custom ROMs on my last device and based on that, I'd like to stick to MIUI for a while.
Out of curiousity what are the other bugs with MIUI11 aside from it not working with encryption?
droident said:
I'm hoping the Magisk situation gets fixed. I checked the Magisk support thread and only saw one post about a bootloop with a Mi9T Pro (again, likely data encryption) so I'm given the impression MIUI might be off the radar for Magisk bug fixes.
I've had a couple of issues with Magisk 20.1 on MIUI10 - nothing critical but a couple times Magisk Manager has frozen (i.e. kill the process, relaunch and it works) and a couple hangs when root apps have been launched for the first time (again, kill + relaunch, a few times if necessary). Smooth sailing otherwise but gives me the impression that Magisk isn't without flaws on MIUI. One response was to dump MIUI altogether but I'd rather have a stable hardware experience for now. I tested a lot of custom ROMs on my last device and based on that, I'd like to stick to MIUI for a while.
Out of curiousity what are the other bugs with MIUI11 aside from it not working with encryption?
Click to expand...
Click to collapse
Other than standard app compatibility issues, I haven't heard of any major MIUI11 bugs, which is fantastic to hear.
I have tried all sorts. MI9T MIUI 11.0.1.0 and magisk just causes recovery bootloop . Gonna try magisk 19.4 if thats a thing mentioned in a previous reply
I use Miui 11.0.3 together with Magisk. I used the following procedure:
1. Copy Magisk 20.1 (for twrp) to your internal storage (e.g. downloads)
2. Install Magisk via TWRP
3. Don't reboot (it will cause bootloop).
4. Do factory reset (it will remove your Data). Your bootloader will remain patched.
5. Reboot your phone, do initial config.
6. Install Magisk Manager and run it so you will see that Magisk is installed.
7. DON'T install additional files suggested by Magisk Manager (or you will end up in bootloop again)
8. Enjoy your rooted K20Pro!
I got the same problem on my k20 pro (with MIUI EU).I try driffent ways provided by magisk official but no one works.I have to flash the system. It's not a good idea for intalling V4A on this phone
XedosMD said:
I use Miui 11.0.3 together with Magisk. I used the following procedure:
1. Copy Magisk 20.1 (for twrp) to your internal storage (e.g. downloads)
2. Install Magisk via TWRP
3. Don't reboot (it will cause bootloop).
4. Do factory reset (it will remove your Data). Your bootloader will remain patched.
5. Reboot your phone, do initial config.
6. Install Magisk Manager and run it so you will see that Magisk is installed.
7. DON'T install additional files suggested by Magisk Manager (or you will end up in bootloop again)
8. Enjoy your rooted K20Pro!
Click to expand...
Click to collapse
Does your phone remain encrypted after you do these steps? I doubt...
For some reasons, I wanna keep my phone encrypted.