Hi,
Is there a way to have both Magisk and Encryption?
I've tried to sideload Magisk installer from TWRP but I get the verification error after rebooting to system.
Thanks.
Related
Tried to use auto option for boot image location and it chooses mmcblk0p40 but gives installation error, tired about 4 others and same error. Also when I choose magiskhide it says I am not rooted with magisksu and safetynet says CTS profile mismatch. I'm on H90120l
k00lguy105 said:
Tried to use auto option for boot image location and it chooses mmcblk0p40 but gives installation error, tired about 4 others and same error. Also when I choose magiskhide it says I am not rooted with magisksu and safetynet says CTS profile mismatch. I'm on H90120l
Click to expand...
Click to collapse
Have you tried running the uninstaller for magisk in TWRP and then flash the 13.2 zip
8bitbang said:
Have you tried running the uninstaller for magisk in TWRP and then flash the 13.2 zip
Click to expand...
Click to collapse
I tried installing the new magisk manager and now it doesn't say there is an update available so i tried just flashing the update in TWRP and got an error, will try uninstaller next.
I have installed magisk 14 via twrp. After some time it shows magisk not installed error.. but after restarting device it is working fine but after some time I'm getting same error.. please help..
use magisk installer to wipe magisk.then make clean install
I installed systemless Xposed through magisk and it got my phone stuck in bootloop so I tried to fix it by using HWOTA8 and used the OTA.bat fixed the problem but when I installed Magisk again the problem happens again so is there anyway to delete all modules installed by Magisk from recovery?
CodeRida said:
I installed systemless Xposed through magisk and it got my phone stuck in bootloop so I tried to fix it by using HWOTA8 and used the OTA.bat fixed the problem but when I installed Magisk again the problem happens again so is there anyway to delete all modules installed by Magisk from recovery?
Click to expand...
Click to collapse
there is a mount magisk zip to flash in recovery. but don't have link ready, just search on google, should be easy to find
—Problem—
Boot loop... is there anyway to solve this problem without a reset?
—generel Infos—
Device: OnePlus 5 (rooted)
OS: oxygenos 9.0.3
Recovery: TWRP
Other: using EDXposed &
Nethunter Kernel
—the reason?—
I think it was the experimental setting in GravityBox Pie. There was a warning but I didn’t read it because ... I don’t know. The setting required a reboot but after that I stuck in the boot loop.
—what I ´ve tried—
I saw a guide on xda how to disable xposed modules via twrp. The problem was that I was using EDXposed. It was a different. But I deleted a similar file via twrp file manager ( /data/data/com.[IdontKnowTheExactPackgeName].xposed.manager/shared_prefs/[SomethingWithModules])
I tried to reboot but without success
I installed mm ( a for twrp to disable/enable magisk modules and more)
In mm I disabled the EDXposed Module und riru Core Module ( Im not sure if I was riru)
I tried to reboot but without success
I flashed magisk uninstaller and after flashing was done( magisk couldn’t restore boot image or something like that but the flash worked so I ignored it) I got the error: error creating fstab ( the same error occurred when wiping cache/dalvic)
I tried to reboot but without success
I wanted to flash EDXposed but it didn’t work because I haven’t magisk installed
So I flashed magisk again ( this solved the fstab error) and after that the EDXposed uninstaller. Both flashes worked
I tried to reboot but without success
Now I gave up and hope that you have an ansewer
Master Luca said:
—Problem—
Boot loop... is there anyway to solve this problem without a reset?
—generel Infos—
Device: OnePlus 5 (rooted)
OS: oxygenos 9.0.3
Recovery: TWRP
Other: using EDXposed &
Nethunter Kernel
—the reason?—
I think it was the experimental setting in GravityBox Pie. There was a warning but I didn’t read it because ... I don’t know. The setting required a reboot but after that I stuck in the boot loop.
—what I ´ve tried—
I saw a guide on xda how to disable xposed modules via twrp. The problem was that I was using EDXposed. It was a different. But I deleted a similar file via twrp file manager ( /data/data/com.[IdontKnowTheExactPackgeName].xposed.manager/shared_prefs/[SomethingWithModules])
I tried to reboot but without success
I installed mm ( a for twrp to disable/enable magisk modules and more)
In mm I disabled the EDXposed Module und riru Core Module ( Im not sure if I was riru)
I tried to reboot but without success
I flashed magisk uninstaller and after flashing was done( magisk couldn’t restore boot image or something like that but the flash worked so I ignored it) I got the error: error creating fstab ( the same error occurred when wiping cache/dalvic)
I tried to reboot but without success
I wanted to flash EDXposed but it didn’t work because I haven’t magisk installed
So I flashed magisk again ( this solved the fstab error) and after that the EDXposed uninstaller. Both flashes worked
I tried to reboot but without success
Now I gave up and hope that you have an ansewer
Click to expand...
Click to collapse
Try reflashing rom you are using again in recovery.so dirty flash over existing one
Sent from my LEX820 using Tapatalk
bilausdaniel said:
Try reflashing rom you are using again in recovery.so dirty flash over existing one
Sent from my LEX820 using Tapatalk
Click to expand...
Click to collapse
Still in boot loop ( I let it boot for 18 min )
Did you tried to disable xposed on booting?
There is key combination when system boots up, to disable xposed, and so all modules.
Go into recovery, and boot up again from there (normal boot), and when logo appears click at least 3 times power button, and xposed will understand it need to disable itself.
That should work.
And if you have some data in phone, you can make app backup from recovery and if you have files you can connect to PC and copy those files on PC.
I am currently having this problem. Some fully updated systems on some devices won't boot into safe mode. Among those devices are many Xiaomi Devices. I can only boot into fastboot mode.
I've got Orange Fox so theoretically I should be able to delete Riru, effectively disabling exposed, however, Orange Fox is asking for a decryption password and I can't access files to delete them.
ADB sideload failed.
Not sure if I can even do a wipe back to default state.
brasscupcakes said:
I am currently having this problem. Some fully updated systems on some devices won't boot into safe mode. Among those devices are many Xiaomi Devices. I can only boot into fastboot mode.
I've got Orange Fox so theoretically I should be able to delete Riru, effectively disabling exposed, however, Orange Fox is asking for a decryption password and I can't access files to delete them.
ADB sideload failed.
Not sure if I can even do a wipe back to default state.
Click to expand...
Click to collapse
go in twrp and to android/adb/modules.. module there reboot phone
bilausdaniel said:
go in twrp and to android/adb/modules.. module there reboot phone
Click to expand...
Click to collapse
delete that module in there
Hello,
yesterday I got a notification to update Magisk to v.21.3. I did it directly with Magisk Manager.
Since then I'm having problems with some apps and I notice that a new version of Magisk was release just to fix this problem.
When I try to install the v.21.4 with the Magisk Manager there is an option unchecked but I do not know if I have to check it or no.
Keep AVB 2.0/dm-verity
I do not know what is this. When I update to v.23.1 I did not have that option, was direct but now when I want to update to 21.4 from Magisk Manager I have this option and I do not know what to do.
Thanks
I assume nobody answered you because you could have just googled it.
Disable DM-Verity or Android Verified Boot without TWRP
In this tutorial, we will show you the steps to disable DM-Verity or Android Verified Boot (AVB) without using TWRP Recovery.
www.droidwin.com