Hey all!
Those of you monitoring the unofficial LineageOS thread may have seen me talking about this already. I've been having issues with Magisk. I'm running their beta versions for 13.0.
So here's the story...
I have wanted to pass SafetyNet since May, when I got this phone and rooted it. I obviously went to Magisk, and when I realized that 11.6 was not passing SafetyNet, I decided to try the 13 betas. These didn't pass either, but since they were more recent than 11.6, I stuck with them. But when I heard of the Universal SafetyNet Fix Module, I immediately tried it.
Bottom line, these are my issues:
1. Magisk will not install the module. I go to Magisk Manager -> Modules -> + and select the ZIP for the module. Magisk gives me a toast saying "Installation error!" (See screenshot).
2. Okay, so now I want to start fresh and see if it works then. I boot into TWRP, flash the lastest Magisk uninstaller (08 June), and boot. Nope! Stuck on the "device unlocked" screen with ID: bad key.
3. Uhh.. maybe the stock boot image will work? I go to TWRP and flash the stock boot.img taken from the stock firmware. Still ID: bad key and I'm stuck again.
And I can boot successfully if I flash a Magisk 13.0 beta.
So, does anybody have any solutions? I think I may just have to reflash stock firmware.. not my top choice. Thank you for any help and reading through my long post :good: :highfive:
Try to install magisk v12, it always worked for me on every rom with safetynet fix ( try also the previous uninstaller )
eskamhl said:
Try to install magisk v12, it always worked for me on every rom with safetynet fix ( try also the previous uninstaller )
Click to expand...
Click to collapse
Will give it a shot and update when I see results.
Edit: Nope. I've a feeling that I'll have to start from scratch by flashing stock firmware.
Try flashing the safetynet fix in trwp.
triggerlord said:
Try flashing the safetynet fix in trwp.
Click to expand...
Click to collapse
Tried already. Still no.
Well, as far as I can see you messed up your installation. Start from scratch:
1. Go to TWRP and wipe system, data, cache and dalvik cache.
2. Install LineageOS, GAPPS, Magisk 12 and the stable version of the safetynet fix
3. Reboot and setup your nice and clean system again.
Bottom-line: don't keep messing with an already messed up system. Start clean again. And really: don't install stock boot.img on LineageOS: that's asking for trouble! To be honest: I'm astonished it even booted!!
smitharro said:
Well, as far as I can see you messed up your installation. Start from scratch:
1. Go to TWRP and wipe system, data, cache and dalvik cache.
2. Install LineageOS, GAPPS, Magisk 12 and the stable version of the safetynet fix
3. Reboot and setup your nice and clean system again.
Bottom-line: don't keep messing with an already messed up system. Start clean again. And really: don't install stock boot.img on LineageOS: that's asking for trouble! To be honest: I'm astonished it even booted!!
Click to expand...
Click to collapse
Lol, was doing this all on the stock ROM. See my original response to triggerlord's post.
Edit: issues fixed with a clean install of the pure Nexus ROM. I'm assuming this would be the case with a clean install of the stock ROM, but I am definitely not switching anytime soon (this ROM is amazing!)
Related
I have a moto g5 plus xt1687 and I was able to unlock the boot loader and install TWRP successfully. I then install no-verity-opt-encrypt-5.1.zip without trouble and reboot to TWRP again. When I try and install Magisk v14 I get the error message "/system could not be mounted"
I have wiped the system earlier so I do not have an operating system installed anymore but I can get into TWRP. What are my solutions? Thanks.
Flash a custom rom in TWRP or reflash stock with fastboot.
Sent from my Moto G (5) Plus using Tapatalk
Custom rom
riggerman0421 said:
Flash a custom rom in TWRP or reflash stock with fastboot.
Sent from my Moto G (5) Plus using Tapatalk
Click to expand...
Click to collapse
Where can I find the custom rom for moto g5 plus xt1687? Thanks
s_beckett said:
I have a moto g5 plus xt1687 and I was able to unlock the boot loader and install TWRP successfully. I then install no-verity-opt-encrypt-5.1.zip without trouble and reboot to TWRP again. When I try and install Magisk v14 I get the error message "/system could not be mounted"
Click to expand...
Click to collapse
Hi,
If you install the ElementalX custom kernel v1.02 then you fix the error.
Futhermore, with this kernel you don't need the "no-verity-patch"... as I advise that this patch writes the SYSTEM partition... so you lost the option for OTAs.
Here the thread to download this custom kernel:
http://forum.xda-developers.com/g5-plus/development/kernel-elementalx-1-00-moto-g5-plus-t3614211
Regards!
ElementaX
manos78 said:
Hi,
If you install the ElementalX custom kernel v1.02 then you fix the error.
Futhermore, with this kernel you don't need the "no-verity-patch"... as I advise that this patch writes the SYSTEM partition... so you lost the option for OTAs.
Here the thread to download this custom kernel:
http://forum.xda-developers.com/g5-plus/development/kernel-elementalx-1-00-moto-g5-plus-t3614211
Regards!
Click to expand...
Click to collapse
I installed LineageOS and then ElementalX and when I reboot it takes me back to TWRP. Are my steps wrong? The bigger question is why am I getting the "/system could not be mounted" when I installed magisk v14 so remain unrooted??. I followed the steps carefully. What is a clear path out of this mess? Very frustrating. Any assistance is appreciated.
s_beckett said:
I installed LineageOS and then ElementalX and when I reboot it takes me back to TWRP. Are my steps wrong? The bigger question is why am I getting the "/system could not be mounted" when I installed magisk v14 so remain unrooted??. I followed the steps carefully. What is a clear path out of this mess? Very frustrating. Any assistance is appreciated.
Click to expand...
Click to collapse
Hi,
I'm on stock, so if you use LineageOS, then this is my recomendation:
- Reinstall Lineage and check that all works (remeber to do "wipe cache" after install it and before boot it).
- Then install the ElementalX-los version, and reboot. Check that all works.
- Finally, after a full reboot install Magisk v14.0.
If the error of mount in Magisk continues, ask @flar2 to fix the "los" version like the Stock-1.02.
Regards.
Some success
manos78 said:
Hi,
I'm on stock, so if you use LineageOS, then this is my recomendation:
- Reinstall Lineage and check that all works (remeber to do "wipe cache" after install it and before boot it).
- Then install the ElementalX-los version, and reboot. Check that all works.
- Finally, after a full reboot install Magisk v14.0.
If the error of mount in Magisk continues, ask @flar2 to fix the "los" version like the Stock-1.02.
Regards.
Click to expand...
Click to collapse
I was able to install magisk v14, then I installed PureNexus and the suggested gapps. When I reboot I kept going back to TWRP but if I go to the bootloader I am able to start the PureNexus OS without issue (no decrypt error). When I do a root check it indicates I am not rooted. What should I do in the proper order? Should I install no-verity-opt-encrypt-5.1. and "Magisk-v14 again without causing a problem, is that the solution? How many times can you reinstall that those files. Thank for your help.
s_beckett said:
I was able to install magisk v14, then I installed PureNexus and the suggested gapps. When I reboot I kept going back to TWRP but if I go to the bootloader I am able to start the PureNexus OS without issue (no decrypt error). When I do a root check it indicates I am not rooted. What should I do in the proper order? Should I install no-verity-opt-encrypt-5.1. and "Magisk-v14 again without causing a problem, is that the solution? How many times can you reinstall that those files. Thank for your help.
Click to expand...
Click to collapse
Sorry?
Magisk will need to be installed after then ROM and the Kernel.
Futhermore, if you use the proper kernel, you don't need to install the "no-verity-opt-encrypt-5.1".
Please, do it in this order:
1) Install PureNexus or your preferable ROM.
2) Boot and check it (don't configure, only a simple check).
3) Reboot to TWRP and install the ZIP of the custom kernel (I recomend ElementalX).
4) Boot and check it (again don't configure).
5) Reboot to TWRP and re-format the "Data" partition (select "f2fs" if it has another filesystem)... this will disable the "encryption enforcement" (as it formats withtout encryption and the kernel disables the enforcement).
6) Boot and configure.
7) Reboot to TWRP and install Magisk v14.
8) Boot and check MagiskManager, you're now rooted.
9) If you like install Xposed for Magisk and configure it.
That's all!
manos78 said:
Sorry?
Magisk will need to be installed after then ROM and the Kernel.
Futhermore, if you use the proper kernel, you don't need to install the "no-verity-opt-encrypt-5.1".
Please, do it in this order:
1) Install PureNexus or your preferable ROM.
2) Boot and check it (don't configure, only a simple check).
3) Reboot to TWRP and install the ZIP of the custom kernel (I recomend ElementalX).
4) Boot and check it (again don't configure).
5) Reboot to TWRP and re-format the "Data" partition (select "f2fs" if it has another filesystem)... this will disable the "encryption enforcement" (as it formats withtout encryption and the kernel disables the enforcement).
6) Boot and configure.
7) Reboot to TWRP and install Magisk v14.
8) Boot and check MagiskManager, you're now rooted.
9) If you like install Xposed for Magisk and configure it.
That's all!
Click to expand...
Click to collapse
First off really appreciate your help and patience with me. Followed your guidelines have root and PureNexus is working ok. One last issue that persists. Every time I reboot it goes directly to TWRP. I have to go to the bootloader and start the OS that way. How can I get it to boot directly into the OS? Thanks again.
s_beckett said:
First off really appreciate your help and patience with me. Followed your guidelines have root and PureNexus is working ok. One last issue that persists. Every time I reboot it goes directly to TWRP. I have to go to the bootloader and start the OS that way. How can I get it to boot directly into the OS? Thanks again.
Click to expand...
Click to collapse
This is because your bootloader thinks that it need to boot to the "recovery". So, try this:
1) Wipe cache.
2) Do a full power-off from the ROM.
manos78 said:
This is because your bootloader thinks that it need to boot to the "recovery". So, try this:
1) Wipe cache.
2) Do a full power-off from the ROM.
Click to expand...
Click to collapse
Unfortunately this did not work. Are there any other options?
s_beckett said:
Unfortunately this did not work. Are there any other options?
Click to expand...
Click to collapse
Enter into bootloader mode, connect your phone to the PC and type "fastboot continue" command in ADB.
manos78 said:
This is because your bootloader thinks that it need to boot to the "recovery". So, try this:
1) Wipe cache.
2) Do a full power-off from the ROM.
Click to expand...
Click to collapse
I have found success! I wiped the drive in TWRP and install Stoneware v67 then installed magisk v14 and the boot process is now directly to the OS and it is rooted. I did not load a custom ROM but it is working fine. Frankly, I really do not understand which ROM needs a custom one or not and wish there were clear instruction on this matter as there are so many ROMs and some did not install or work well when I tried them. In any event, I appreciate your ongoing assistance and patience with me.
s_beckett said:
I have found success! I wiped the drive in TWRP and install Stoneware v67 then installed magisk v14 and the boot process is now directly to the OS and it is rooted.
Click to expand...
Click to collapse
Great!
The behaviour you have observed is because at some point the "reboot cause" (the trigger that launch the recovery at every boot) isn't cleared or is everytime set incorrectly. If you found a method for clear the cause, then you can continue...
Hi,
I have a rooted OP5, running 5.1.7 and TWRP. I used Oxygen Updater to download the new android 9 ROM. I tried to install via TWRP, but got an error about zip compatability & a treble problem. I found a thread stating that I needed a newer TWRP to fix the treble problem, so I installed TWRP_3.2.3-Pie_siankatabg_OP5 , which said it had Pie support, from here:
https://androidfilehost.com/?fid=1322778262903996029
That worked fine, but when I tried to flash the 9 ROM, I got still got the same error. Another post said to remove compatibility.zip from the ROM zip. I did that, and it now installed, but it wouldn't boot. Re-flashing 5.1.7 booted fine. I tried another TWRP - twrp-3.2.3-0-20181227-codeworkx-nocompatcheck-cheeseburger from here:
https://forum.xda-developers.com/on...overy-twrp-3-2-1-0-oreo-oxygenos-5-0-t3725723
That installs, and boots to system, but won't boot to recovery, so I can't install the 9 ROM.
Any ideas where I go from here to upgrade to 9?
Thanks!
richstant said:
Hi,
I have a rooted OP5, running 5.1.7 and TWRP. I used Oxygen Updater to download the new android 9 ROM. I tried to install via TWRP, but got an error about zip compatability & a treble problem. I found a thread stating that I needed a newer TWRP to fix the treble problem, so I installed TWRP_3.2.3-Pie_siankatabg_OP5 , which said it had Pie support, from here:
https://androidfilehost.com/?fid=1322778262903996029
That worked fine, but when I tried to flash the 9 ROM, I got still got the same error. Another post said to remove compatibility.zip from the ROM zip. I did that, and it now installed, but it wouldn't boot. Re-flashing 5.1.7 booted fine. I tried another TWRP - twrp-3.2.3-0-20181227-codeworkx-nocompatcheck-cheeseburger from here:
https://forum.xda-developers.com/on...overy-twrp-3-2-1-0-oreo-oxygenos-5-0-t3725723
That installs, and boots to system, but won't boot to recovery, so I can't install the 9 ROM.
Any ideas where I go from here to upgrade to 9?
Thanks!
Click to expand...
Click to collapse
Hi, I got Pie to install with TWRP_3.2.3-Pie_siankatabg_OP5 on my device.
Go to this link:
https://forum.xda-developers.com/showpost.php?p=78523940&postcount=13
And follow my post on the part where it says:
" Notes for the Pie update: "
Let us know if those steps work for you. The firmware is linked to on there, pre-modified. Try flashing that pre-modified zip and see if your device boots.
richstant said:
Hi,
I have a rooted OP5, running 5.1.7 and TWRP. I used Oxygen Updater to download the new android 9 ROM. I tried to install via TWRP, but got an error about zip compatability & a treble problem. I found a thread stating that I needed a newer TWRP to fix the treble problem, so I installed TWRP_3.2.3-Pie_siankatabg_OP5 , which said it had Pie support, from here:
https://androidfilehost.com/?fid=1322778262903996029
That worked fine, but when I tried to flash the 9 ROM, I got still got the same error. Another post said to remove compatibility.zip from the ROM zip. I did that, and it now installed, but it wouldn't boot. Re-flashing 5.1.7 booted fine. I tried another TWRP - twrp-3.2.3-0-20181227-codeworkx-nocompatcheck-cheeseburger from here:
https://forum.xda-developers.com/on...overy-twrp-3-2-1-0-oreo-oxygenos-5-0-t3725723
That installs, and boots to system, but won't boot to recovery, so I can't install the 9 ROM.
Any ideas where I go from here to upgrade to 9?
Thanks!
Click to expand...
Click to collapse
It sounds like you did not follow the detailed flashing instructions in the first post here: https://forum.xda-developers.com/oneplus-5/how-to/official-oxygenos-4-5-2-7-1-1-ota-t3627003
Is your device storage encrypted or decrypted? Have you flashed magisk? Have you used an older magisk(your end link leads to my post where I mention that)? Have you downloaded the rom file without compatibility.zip or did you removed it on your own?
strongst said:
It sounds like you did not follow the detailed flashing instructions in the first post here: https://forum.xda-developers.com/oneplus-5/how-to/official-oxygenos-4-5-2-7-1-1-ota-t3627003
Is your device storage encrypted or decrypted? Have you flashed magisk? Have you used an older magisk(your end link leads to my post where I mention that)? Have you downloaded the rom file without compatibility.zip or did you removed it on your own?
Click to expand...
Click to collapse
Thanks for the links both, but still no go. I was on Magisck 17.1, uninstalled Magisk with the latest uninstaller, flashed the ROM with compatability.zip already removed. Same result as before - I get the oneplus logo, then it just reboots instead of starting the system. I've only wiped cache & dalvik, I don't really want to wipe more than that if I can help it - it is worth trying a system/vendor/data wipe? I recovered by flashing back to 5.1.7 (also updated to Magisk 18 while I was at it).
Any more ideas? One thing I find a little weird is that I'm on the @siankatabg TWRP, when I tried either the bluespark & codeworx TWPR, I couldn't get into recovery with either, I just got a blank screen with a LED staying on light blue. Only the siankatabg recovery works. Surely any of them should work? Does this point to a problem?
I'm not sure what you mean by encrypted or not - I get messages about unencrypting when going into recovery, which I assume means I am encrypted?
THanks!
richstant said:
Thanks for the links both, but still no go. I was on Magisck 17.1, uninstalled Magisk with the latest uninstaller, flashed the ROM with compatability.zip already removed. Same result as before - I get the oneplus logo, then it just reboots instead of starting the system. I've only wiped cache & dalvik, I don't really want to wipe more than that if I can help it - it is worth trying a system/vendor/data wipe? I recovered by flashing back to 5.1.7 (also updated to Magisk 18 while I was at it).
Any more ideas? One thing I find a little weird is that I'm on the @siankatabg TWRP, when I tried either the bluespark & codeworx TWPR, I couldn't get into recovery with either, I just got a blank screen with a LED staying on light blue. Only the siankatabg recovery works. Surely any of them should work? Does this point to a problem?
I'm not sure what you mean by encrypted or not - I get messages about unencrypting when going into recovery, which I assume means I am encrypted?
THanks!
Click to expand...
Click to collapse
Maybe try backing your device up, and then locking the bootloader. Try updating with stock recovery on a locked bootloader. If that works, you can then unlock the bootloader and copy your data back
richstant said:
Thanks for the links both, but still no go. I was on Magisck 17.1, uninstalled Magisk with the latest uninstaller, flashed the ROM with compatability.zip already removed. Same result as before - I get the oneplus logo, then it just reboots instead of starting the system. I've only wiped cache & dalvik, I don't really want to wipe more than that if I can help it - it is worth trying a system/vendor/data wipe? I recovered by flashing back to 5.1.7 (also updated to Magisk 18 while I was at it).
Any more ideas? One thing I find a little weird is that I'm on the @siankatabg TWRP, when I tried either the bluespark & codeworx TWPR, I couldn't get into recovery with either, I just got a blank screen with a LED staying on light blue. Only the siankatabg recovery works. Surely any of them should work? Does this point to a problem?
I'm not sure what you mean by encrypted or not - I get messages about unencrypting when going into recovery, which I assume means I am encrypted?
THanks!
Click to expand...
Click to collapse
Please use an older recovery like twrp-3.2.3-0-20181031-codeworkx-cheeseburger.img the actual pie recoveries require pie firmware(mentioned in last post of blue spark thread for example).
strongst said:
Please use an older recovery like twrp-3.2.3-0-20181031-codeworkx-cheeseburger.img the actual pie recoveries require pie firmware(mentioned in last post of blue spark thread for example).
Click to expand...
Click to collapse
OK, I understand now - if I use an older TWRP, or the siankatabg version, it works fine. I can then flash the Pie ROM, however it still won't boot - I get the oneplus logo, then it just reboots. However having done the Pie flash, I can then flash the more recent TWRPs (codeworx or Bluespark), and can now get into recovery fine. However Pie still won't boot - I've even tried re-flashing the Pie ROM from within the newer TWRPs, but the result is the same - it gets to the oneplus logo, then reboots. At this stage I guess wiping system/vendor/data is the only way forwards?
*Edit* - OK, so wiping everything fixed the issue, I'm now on Pie. Flashing Magisk didn't work when flashing the ROM, but I'll try again once it's finished downloading all my apps etc.
.
HMSS013 said:
Had my new OP5 rooted and almost everything was right in the world, but i flew too close to the sun by uninstalling a few apps I thought were expendable and eventually Google Play Services started crashing. When all troubleshooting failed I ended up flashing a fresh copy of OxygenOS (5.1.7) to my device, but every attempt to re-root the device has failed.
The first obstacle I ran into was that there was no access to Internal Storage in TWRP, I was able to fix that by Wipe > Format Data and then using Advanced Wipe to clean Dalvik/Cache/System/Data for good measure.
My next issue was that TWRP returned Error 7 when attempting to flash the stock OOS rom... after some digging I was able to clean the 'asserts' line from the updater-script file and now the rom will flash.
The headache has been getting the device re-rooted, and I feel like I've tried everything. I have to flash the SuperSU or Magisk zip (both fail to root the device) before reboot because the dm-verity encrypts on first boot and after that I can't access any storage to flash from internal memory. The three different dm-verity patches I've found don't prevent it. I also tried 'fastboot oem disable_dm_verity' to try and stop it but after talking with the device fastboot returns 'unknown command'.
My final effort to get around it was to flash a kernel that didn't force dm-verity (blu_spark kernel) but that returns Error 1: 'Unsupported Android Version' when I attempt to flash it.
I've tried dozens of variations on this, including a Lineage OS rom instead and also trying to sideload certain zips, but still no dice. Any and all help would be appreciated.
Click to expand...
Click to collapse
Which rom do you want to install?
HMSS013 said:
The first obstacle I ran into was that there was no access to Internal Storage in TWRP, I was able to fix that by Wipe > Format Data and then using Advanced Wipe to clean Dalvik/Cache/System/Data for good measure.
Click to expand...
Click to collapse
Hi, this one is because of your TWRP. Please flash Codework's TWRP and try that with it. It should solve your issue for sure. (same thing happened to me while I tried installing custom roms and every time I needed to wipe everything to see my internal storage again)
This guide can help you out with Error 7 on TWRP https://forum.xda-developers.com/showthread.php?t=2522762
I do believe your this issue you're having caused by TWRP. Also after rooting the phone, install magisk app. (you don't need to install supersu, it comes with magisk). After rebooting into system reboot your phone again once more it should show up on magisk app that you've successfully rooted your phone. Remember after flashing magisk you need to reboot twice in order for phone to realize it. Please try the steps I told you and let me know.
Also you don't need to flash dm-verity patch at all.
Try clean flash instructions with Codework's TWRP and root it with latest Magisk.
.
.
HMSS013 said:
I actually really like the Oreo version of OxygenOS, so when I had to resort to re-flashing to fix this mess I dug up one of the stock (5.1.7) roms, it served me well (assuming I can get it rooted, lol).
I'd be willing to move to Lineage if I absolutely have to, but if not, I'd really like to keep Oreo if at all possible.
Click to expand...
Click to collapse
For 5.1.7 try this twrp https://drive.google.com/file/d/1UlTftbe6wooAs4Fp0cjwXlOKmfQHgdfL/view?usp=drivesdk along with magisk 17.1.
Clean flash is recommended. If it didn't help, please list your steps again(detailed).
Don't use supersu and skip the other suggestions for now please.
.
I am trying to install magisk on stock nougat with elementalx installed but after reboot it wont boot and stuck on "your device is unlocked" mensage, I tried to find some tutorial but no success
Which magisk version are you using? Try magisk 18 or 17 and also try wiping your cache after flashing magisk and before you reboot.
Ensure also if you're switching root managers (e.g. if you're coming from supersu), that you've fully uninstalled the previous manager and reverted back to the stock kernel, for a clean start. Then, flash ElementalX 2.0.1 (for Nougat) then flash magisk. Wipe cache and reboot
echo92 said:
Which magisk version are you using? Try magisk 18 or 17 and also try wiping your cache after flashing magisk and before you reboot.
Ensure also if you're switching root managers (e.g. if you're coming from supersu), that you've fully uninstalled the previous manager and reverted back to the stock kernel, for a clean start. Then, flash ElementalX 2.0.1 (for Nougat) then flash magisk. Wipe cache and reboot
Click to expand...
Click to collapse
ty bro, i tried 18.3 but still stuck and only 17 works for me
None worked for me. I cant root the phone again after I reinstalled android.
lexie90 said:
None worked for me. I cant root the phone again after I reinstalled android.
Click to expand...
Click to collapse
What device do you have, and which stock ROM are you using? Root steps can be specific to a device and the ROM you're using.
stuck after flashing magisk zip
echo92 said:
Which magisk version are you using? Try magisk 18 or 17 and also try wiping your cache after flashing magisk and before you reboot.
Ensure also if you're switching root managers (e.g. if you're coming from supersu), that you've fully uninstalled the previous manager and reverted back to the stock kernel, for a clean start. Then, flash ElementalX 2.0.1 (for Nougat) then flash magisk. Wipe cache and reboot
Click to expand...
Click to collapse
I flashed the magisk zip file from twrp and rebooted but its stuck not booting after that i tried wiped all data and formatted also but still the same pls he
Suraj Rawat 271201 said:
I flashed the magisk zip file from twrp and rebooted but its stuck not booting after that i tried wiped all data and formatted also but still the same pls he
Click to expand...
Click to collapse
What device are you using, which ROM are you running and which magisk version have you been using?
I'm running Android 10 with EvoX rom and after last update of Magisk to 21.4 the phone is stuck on bootloop. After going to recovery and uninstalling Magisk I have the same problem, it's still in bootloop. What can I do to fix the problem?
Dirty flash ROM or if 1st step doesn't work factory reset and install everything
Same here. I don't want to do a factory reset.
I tried to:
- uninstall Magisk from twrp
- flash the boot.img of the rom
- flash the previous version 21.2 of magisk
but none of this worked!
I have the same Issue. Havoc 3.9., Magisk 21.4.
I tried to dirty flash the rom, uninstall magisk 21.4 via twrp, and flashing 21.2.
Didn't help. Occassionally I got into the system, but the screen is a bit more white than usually, I can type in my lock password, but after this, System UI fails.
Yesterday I flashed the fix for safetynet passing after the latest update, which made it work again, and I remember that at the relevant magisk forum, somebody mentioned that would affect System UI somehow. Now I am trying to repair the System UI to see if it works as a solution.
[email protected] said:
Yesterday I flashed the fix for safetynet passing after the latest update, which made it work again, and I remember that at the relevant magisk forum, somebody mentioned that would affect System UI somehow. Now I am trying to repair the System UI to see if it works as a solution.
Click to expand...
Click to collapse
What fix are you talking about? Where can I acquire it?
EDIT: In my case the bootloop was caused by the Systemless Xposed Framework module v90-beta2 by rovo89 (packaged by topjohnwu). Disabling that module allowed me to boot normally.
en_ha87 said:
I'm running Android 10 with EvoX rom and after last update of Magisk to 21.4 the phone is stuck on bootloop. After going to recovery and uninstalling Magisk I have the same problem, it's still in bootloop. What can I do to fix the problem?
Click to expand...
Click to collapse
Same problem occur with me ,i just unistall 21.4 and indtal 20.4 veraion but nothing happens then i just wait for 5-10 min on bootloop screen and it starts processing it's updating my new boot image ... This thing happens when i update my miui after completing the process i finally see my homescreen
Lars0n89 said:
What fix are you talking about? Where can I acquire it?
EDIT: In my case the bootloop was caused by the Systemless Xposed Framework module v90-beta2 by rovo89 (packaged by topjohnwu). Disabling that module allowed me to boot normally.
Click to expand...
Click to collapse
How can you install that Module from TWRP?
That i remember i never installed it, it's automatically loaded with magisk?
To solve this problem i had to format the phone, installing the OS again and also magisk v21.2. But Today i got the same problem... so maybe is not the versione of magisk. But I don't know of to solve it.
I tried also the sotck boot.img, but it stays some seconds on the boot screen of lineage OS and then reboot again stucking on Mi logo.
i also had to install stock rom, lost all the data on the phone. today i have to install custom rom, and will probably pass on the magisk, i don't need sh**t like this happening again.
I had to reinstall the rom from scratch, and needed to format data partition too. After flashing my ROM back, I installed magisk 21.2 and it works great.
I solved:
-go in fastboot mode
-flash twrp recovery
-go in twrp and with mtp insert magisk-uninstaller.zip and last magisk-21.4.zip
-run uninstaller.zip than installer.zip
-reboot in system
flavioggl said:
I solved:
-go in fastboot mode
-flash twrp recovery
-go in twrp and with mtp insert magisk-uninstaller.zip and last magisk-21.4.zip
-run uninstaller.zip than installer.zip
-reboot in system
Click to expand...
Click to collapse
Could you help me i got into a bootloop after doing the magisk direct update from the app. My discord is : SneezeOnYou2#8507
I believe that i have a backup in twrp just dont know how to flash or uninstall or what ever to do i dont want to lose my data. I can record my screen if you add me on discord.
flavioggl said:
I solved:
-go in fastboot mode
-flash twrp recovery
-go in twrp and with mtp insert magisk-uninstaller.zip and last magisk-21.4.zip
-run uninstaller.zip than installer.zip
-reboot in system
Click to expand...
Click to collapse
Thank you, brother. It was a simple solution but I forget to do that. After wasting 2 hours finally able to solve the problem. Thanks again.