Related
Hi, do i need install systemless SuperSU always in twrp before install magisk v11 if I want use new MagiskSU instead??
If I try install Magisk v11 with superSU uninstalled and phone unrooted TWRP give me error and installation fails and if I install superSU and after Magisk v11, Magisk manager say system is using SuperSU instead MagiskSU. How do I install Magisk with MagiskSU??
I have Samsung Galaxy S4 with optimized LineageOS 14.1
Read the pinned Magisk thread...
Unroot again using unSu by osm0sis (Google) before flashing magisk
Installation Instructions
If you're already rooted with MagiskSU, Magisk phh's superuser (not original), or Official Systemless SuperSU
Install/upgrade Magisk Manager from Play Store
Install/upgrade Magisk as prompted in the application
Reboot and you're done!!
If you're not rooted, or something went wrong and you need a clean start
(Recommended) Restore your boot image back to stock
Download the latest Magisk zip file
If you choose to use SuperSU (only support Android 6.0+), first flash SuperSU in systemless mode
Flash Magisk zip
Reboot, and update the stub Magisk Manager to the latest from Play Store
Click to expand...
Click to collapse
I read 200 times but when I install Magisk without SuperSU (because I want MagiskSU) TWRP give me an error and install fail... read my initial post first please....
Error:
Code:
! SU image mount failed...
! Please immediately flash SuperSU now
! Installation will complete after flashing SuperSU
[B]Updater process ended with ERROR: 1
Error installing zip file 'sdcard/Download/Magisk v11.1/Magisk-v11.1.zip[/B]
dhaern said:
I read 200 times but when I install Magisk without SuperSU (because I want MagiskSU) TWRP give me an error and install fail... read my initial post first please....
Error:
Click to expand...
Click to collapse
You need to FULLY unflash superSU using the zip that the other person told you to google.
PartyPlease said:
You need to FULLY unflash superSU using the zip that the other person told you to google.
Click to expand...
Click to collapse
Ok I will try unflash with the zip, I was using unroot inside superSU menu but installation instructions dont say nothing about the unflash with an extrenal script
dhaern said:
Ok I will try unflash with the zip, I was using unroot inside superSU menu.
Click to expand...
Click to collapse
Yeah that button doesn't work for systemless superSU. It doesn't roll back your boot.IMG like it should.
Worst case scenario, flash the stock boot.img and then flash magisk.
Thanks guys, I installed Magisk v11.1 with MagiskSU working, Magisk Hide enabled but I have CTS mismatch error now in Safetynet test. I guess I cant do nothing about this error. Optimized LineageOS 14.1 and Samsung Galaxy S4
EDIT: Finally I passed the Safetynet test (no CTS mismatch error) disabling ADB interface in developer options. Thanks for Magisk, amazing.
PartyPlease said:
Yeah that button doesn't work for systemless superSU. It doesn't roll back your boot.IMG like it should.
Worst case scenario, flash the stock boot.img and then flash magisk.
Click to expand...
Click to collapse
ahh, this would explain why my boot.img was not the same after "unrooting"! thanks for clearing this up for me...
dhaern said:
Thanks guys, I installed Magisk v11.1 with MagiskSU working, Magisk Hide enabled but I have CTS mismatch error now in Safetynet test. I guess I cant do nothing about this error. Optimized LineageOS 14.1 and Samsung Galaxy S4
EDIT: Finally I passed the Safetynet test (no CTS mismatch error) disabling ADB interface in developer options. Thanks for Magisk, amazing.
Click to expand...
Click to collapse
By disabling ADB interface, do you mean the USB debugging part? for some reason I am still getting Safetynet error.
vicky_ag said:
By disabling ADB interface, do you mean the USB debugging part? for some reason I am still getting Safetynet error.
Click to expand...
Click to collapse
Yeah I said USB debugging option, when I disabled this I passed Safetynet test.
dhaern said:
Yeah I said USB debugging option, when I disabled this I passed Safetynet test.
Click to expand...
Click to collapse
Thanks but doesn't seem to work for me.
dhaern said:
Yeah I said USB debugging option, when I disabled this I passed Safetynet test.
Click to expand...
Click to collapse
Thanks for this hint; got my build "passed" now appreciate it
What settings are you guys using in Magisk? I have disabled BusyBox, enabled Magisk Hide and systemless hosts. Superuser options are Access to "Apps and ADB" and Automatic Response set to prompt
I'm still having an issue installing Magisk on my phone with RAMROM V10. It gives me an ERROR 1.
It has been suggested that I should re-flash my boot.img with TWRP following the instruction:
Place your BOOT.img on your sdcard
Reboot into TWRP recovery
Tap "Install"
In the bottom right corner tap "Install Image"
Select your BOOT.img
Select the Boot Partition, then swipe to confirm Flash
However, when I follow the step, my TWRP cannot seem to find BOOT.IMG in my SD Card (I know it is there). What did I do wrong? Can anyone help?
i think the .img thingy is only for twrp.img files. You have to use another method to place your boot image like. -> make a backup of only your boot image via twrp backup function. Then duplicate that backup folder of twrp containing only the newly just regernated files, in the twrp folder. Then replace the su-modified boot file there with your original boot file, you obviously have to rename your boot image to fit the right name. (eg. with the logo image -> logo.bin changes to logo.emmc.win -> etc;.) Then use the twrp restore function to restore your "original" boot logo.
Hierarchy folder view would be like:
TWRP->folder 1 (original folder, in case something goes wrong)-> boot file and others
->folder 2 (our modified folder)-> files
sm00th4f3 said:
i think the .img thingy is only for twrp.img files. You have to use another method to place your boot image like. -> make a backup of only your boot image via twrp backup function. Then duplicate that backup folder of twrp containing only the newly just regernated files, in the twrp folder. Then replace the su-modified boot file there with your original boot file, you obviously have to rename your boot image to fit the right name. (eg. with the logo image -> logo.bin changes to logo.emmc.win -> etc;.) Then use the twrp restore function to restore your "original" boot logo.
Hierarchy folder view would be like:
TWRP->folder 1 (original folder, in case something goes wrong)-> boot file and others
->folder 2 (our modified folder)-> files
Click to expand...
Click to collapse
FIY: Flashing regular boot.img files works just fine with "Install Image" in TWRP (of course, YMMV, depending on your device).
Last time I have to re flash my phone.
No big deal, it works, but somethings goes wrong.
Now I want to install the April path of Android one and it fails.
The reason is that Magisk could not find the original boot image.
Also the uninstallation of Magisk fails because of the same reason.
So I need to know where should be the backup file?
And I need the unpatched boot image from Android One 10.0.7.0.PDLMIXM
Thanks
I got the boot image, but where should I store it so Magisk could find it?
questionatxda said:
I got the boot image, but where should I store it so Magisk could find it?
Click to expand...
Click to collapse
Extract the Magisk zip...replace boot.img, re zip and flash
And where I can find the magisk zip file?
Did you know the folder name?
Thanks
questionatxda said:
And where I can find the magisk zip file?
Did you know the folder name?
Thanks
Click to expand...
Click to collapse
Just download Magisk like anyone else and extract that.
Sorry, I have still some questions
I have the magisk download zip, of course.
But there is no boot image inside and I didn't know that there are should be one.
During the magisk installation magisk make a backup of the original boot image and if you want to do a OTA update it will restore this boot image. And I'm searching for this backup boot image.
questionatxda said:
Sorry, I have still some questions
I have the magisk download zip, of course.
But there is no boot image inside and I didn't know that there are should be one.
During the magisk installation magisk make a backup of the original boot image and if you want to do a OTA update it will restore this boot image. And I'm searching for this backup boot image.
Click to expand...
Click to collapse
My apologies, I miss understood. Magisk has it's own boot. Not same as kernel. In order to get kernel one you gotta use terminal commands I believe. Google could help with that. I'm not too sure. Sorry I can't help any further that I can think of atm.
questionatxda said:
And I'm searching for this backup boot image.
Click to expand...
Click to collapse
The backup is stored in /data.
I reflash the phone again and now it works.
Didgeridoohan said:
The backup is stored in /data.
Click to expand...
Click to collapse
I used to do a backup of the unpatched boot.img file so I could flash it via fastboot if something goes wrong. But after I updated to Magisk 20.4 it's not possible to copy the boot.img.gz file anywhere. Not via SMB to my computer and even not to the internal Downloads folder.
I'm using Solid Explorer which has root access.
boot.img.gz is -rw-r--r-- so it should be readable by everyone?
This worked until Magisk 20.3.
emale999 said:
I used to do a backup of the unpatched boot.img file so I could flash it via fastboot if something goes wrong. But after I updated to Magisk 20.4 it's not possible to copy the boot.img.gz file anywhere. Not via SMB to my computer and even not to the internal Downloads folder.
I'm using Solid Explorer which has root access.
boot.img.gz is -rw-r--r-- so it should be readable by everyone?
This worked until Magisk 20.3.
Click to expand...
Click to collapse
What do you mean with "not possible"?
Have you tried other methods/apps? Are there error messages? What happens when you try? Etc, etc... Details are necessary.
Didgeridoohan said:
What do you mean with "not possible"?
Click to expand...
Click to collapse
SolidExplorer says "open failed: EACCES (Permission denied)" when trying to copy this file.
Any suggestions for other methods? adb?
Never had permission issues with SolidExplorer before...so I didn't expect that it's an issue with SolidExplorer
Hey! I recently got banned from Snapchat and I now want to uninstall that thing.
I installed the Magisk modules: Riru - Core & Riru - EdXposed
I installed the EdXposed Installer apk
How do I completely remove EdXposed? (I saw an uninstaller at the EdXposed Github. Do I need this?)
Just delete the edxposed modules, the app, and that's it
Sent from my Xiaomi Mi 8 Lite through Tapatalk
Fedray said:
Just delete the edxposed modules, the app, and that's it
Sent from my Xiaomi Mi 8 Lite through Tapatalk
Click to expand...
Click to collapse
Does EdXposed modify files on the system partition? Or only Xposed?
SebiAi said:
Does EdXposed modify files on the system partition? Or only Xposed?
Click to expand...
Click to collapse
That's the advantage of magisk modules, they don't modify anything on your system, if you disable or delete them everything goes back to original
Sent from my Xiaomi Mi 8 Lite through Tapatalk
Fedray said:
That's the advantage of magisk modules, they don't modify anything on your system, if you disable or delete them everything goes back to original
Sent from my Xiaomi Mi 8 Lite through Tapatalk
Click to expand...
Click to collapse
I mean the apk itself. Does it modify system files?
SebiAi said:
Hey! I recently got banned from Snapchat and I now want to uninstall that thing.
I installed the Magisk modules: Riru - Core & Riru - EdXposed
I installed the EdXposed Installer apk
How do I completely remove EdXposed? (I saw an uninstaller at the EdXposed Github. Do I need this?)
Click to expand...
Click to collapse
Just flash the uninstaller zip from here, and it'll remove all remnants of EdXposed. I had a look at the flashable zip and it is deleting the modules created in Magisk Manager as well as the following two folders (which don't get removed if you just remove the modules from Magisk Manager):
/data/misc/riru/modules/edxposed/
/data/misc/riru/modules/edxp/
shadowstep said:
Just flash the uninstaller zip from here, and it'll remove all remnants of EdXposed. I had a look at the flashable zip and it is deleting the modules created in Magisk Manager as well as the following two folders (which don't get removed if you just remove the modules from Magisk Manager):
/data/misc/riru/modules/edxposed/
/data/misc/riru/modules/edxp/
Click to expand...
Click to collapse
Can I flash this through Magisk Manager? I don't have TWRP installed.
SebiAi said:
I mean the apk itself. Does it modify system files?
Click to expand...
Click to collapse
No
chalseu said:
Can I flash this through Magisk Manager? I don't have TWRP installed.
Click to expand...
Click to collapse
No
Sent from my Xiaomi Mi 8 Lite through Tapatalk
chalseu said:
Can I flash this through Magisk Manager? I don't have TWRP installed.
Click to expand...
Click to collapse
If you don't have TWRP, then just delete the following folders (if they exist for you) using a root file explorer and reboot, you should be good:
/data/adb/modules/riru_edxposed/
/data/adb/modules/riru_edxposed_sandhook/
/data/adb/modules/riru_edxposed_whale/
/data/misc/riru/modules/edxposed/
/data/misc/riru/modules/edxp/
anyone tried on android 10 yet ??
got bootloop on gsi
TheUndertaker21 said:
anyone tried on android 10 yet ??
got bootloop on gsi
Click to expand...
Click to collapse
Successfully uninstalled on Pie (uninstalled apk, disabled both Riru Modules, Reboot, Boot in TWRP, Flashed uninstall)
shadowstep said:
If you don't have TWRP, then just delete the following folders (if they exist for you) using a root file explorer and reboot, you should be good:
/data/adb/modules/riru_edxposed/
/data/adb/modules/riru_edxposed_sandhook/
/data/adb/modules/riru_edxposed_whale/
/data/misc/riru/modules/edxposed/
/data/misc/riru/modules/edxp/
Click to expand...
Click to collapse
I've deleted the riru folder since I've also uninstalled the Riru - Core module thinking it was necessary. Now, I'm afraid to reboot. Lol
chalseu said:
I've deleted the riru folder since I've also uninstalled the Riru - Core module thinking it was necessary. Now, I'm afraid to reboot. Lol
Click to expand...
Click to collapse
most likely impossible that it will bootloop.
I'm on android 10 (lineageOS 17) and followed the instructions from the Youtube Vanced telegram channel.
1. Download and install MagsikHide Props Config via Magisk (download link below) then Reboot
2. Download any Android Terminal Emulator
3. Type "su" then "props" WITHOUT quotation marks
4. Type "1" for Edit device fingerprint
5. Type "f" for Pick a certified fingerprint
6. Type "18" for Xiaomi
7. Type "17" for Xiaomi Pocophone F1
8. Type "y" for yes
-Would you like to activate device simulation?
Type "n" for no
9. Then reboot by typing "y"
After all that, you can check the SafetyNet. If both passes, congrats!
Click to expand...
Click to collapse
It triggered both ctsProfile and basicIntegrity. The edXposed uninstaller was a .bin file, and after I renamed it to .zip and flashed it in TWRP the safetyNet issues still remain.
No bootloop though.
I uninstalled the Edxposed Manager app. Switched in Magisk Manager Settings to "Core only Mode" and rebooted. Then cleared cache of play services and cache and storage of play store after force stopping both. Deactivated "Core only Mode" and rebooted. SafetyNet Check passes again.
Nevermind
I read the instructions in the prior post wrong.
Works now
lucidBrot said:
I'm on android 10 (lineageOS 17) and followed the instructions from the Youtube Vanced telegram channel.
It triggered both ctsProfile and basicIntegrity. The edXposed uninstaller was a .bin file, and after I renamed it to .zip and flashed it in TWRP the safetyNet issues still remain.
No bootloop though.
I uninstalled the Edxposed Manager app. Switched in Magisk Manager Settings to "Core only Mode" and rebooted. Then cleared cache of play services and cache and storage of play store after force stopping both. Deactivated "Core only Mode" and rebooted. SafetyNet Check passes again.
Click to expand...
Click to collapse
The only method that's working flawlessly as of Aug 2020. Thanks kind stranger
Fedray said:
NoNo
Sent from my Xiaomi Mi 8 Lite through Tapatalk
Click to expand...
Click to collapse
Can I flash this via ADB sideload?
I installed EdXposed but it bootloops if I try to boot my phone with root enabled. If I flash a non-rooted bootloader, then I can boot.
So now what I want to do is uninstall an EdXposed that's installed on a phone without root -- is that possible by any chance? Probably not?
Edited to add: And there's no TWRP available (Android 11 Pixel 4a).
I solved my problem; here's how:
1.
Code:
fastboot flash magisk_patched.img
2. Boot into the bootloop, and connect USB. Adb is usable during the bootlooping!
3.
Code:
adb shell magisk --remove modules
4. Reboot into safe mode.
5.
Code:
adb shell su
6.
Code:
rm -rf /data/misc/riru/
7. Reboot!
eater99999 said:
I solved my problem; here's how:
1.
Code:
fastboot flash magisk_patched.img
2. Boot into the bootloop, and connect USB. Adb is usable during the bootlooping!
3.
Code:
adb shell magisk --remove modules
4. Reboot into safe mode.
5.
Code:
adb shell su
6.
Code:
rm -rf /data/misc/riru/
7. Reboot!
Click to expand...
Click to collapse
I have the same problem, but after step 3 my phone is automatically reboots to Bootloader Mode.
How did you manage to go to Safe mode from there?
Guys, I use Mi8 with ROM 9.10.11 Eu rooted. Eveything worked smoothly except I cannot delete system files manually. I used Solid Explorer, Root Explorer, etc but still cannot delete it. How can I delete the system files manually?
cheetahlm said:
Guys, I use Mi8 with ROM 9.10.11 Eu rooted. Eveything worked smoothly except I cannot delete system files manually. I used Solid Explorer, Root Explorer, etc but still cannot delete it. How can I delete the system files manually?
Click to expand...
Click to collapse
In root explorer, mount the system directory as R/W. Then delete.... If it doesn't work, then your Magisk root isn't working properly.
Agimax said:
In root explorer, mount the system directory as R/W. Then delete.... If it doesn't work, then your Magisk root isn't working properly.
Click to expand...
Click to collapse
Thanks for your advice
Which version of Magisk you use?
I use v20.
cheetahlm said:
Thanks for your advice
Which version of Magisk you use?
I use v20.
Click to expand...
Click to collapse
I use the latest Canary. As of now it's Magisk 20.1-59fd38bb (20001) and Magisk manager 7.35-5ffbeaa (246)
Agimax said:
In root explorer, mount the system directory as R/W. Then delete.... If it doesn't work, then your Magisk root isn't working properly.
Click to expand...
Click to collapse
Dear Agimax... I follow your advice... also using the last Magisk of Canary... but still cannot mount system directory as R/W. How to know that the Magisk isn't working properly?
I think this issue concern only miui 11 on Q. I had the same on china beta.
Agimax said:
In root explorer, mount the system directory as R/W. Then delete.... If it doesn't work, then your Magisk root isn't working properly.
Click to expand...
Click to collapse
mar.ur said:
I think this issue concern only miui 11 on Q. I had the same on china beta.
Click to expand...
Click to collapse
Yes you right... I've got the problem on MIUI 11 Android 10... with previously MIUI, there was no problem....
mar.ur said:
I think this issue concern only miui 11 on Q. I had the same on china beta.
Click to expand...
Click to collapse
cheetahlm said:
Yes you right... I've got the problem on MIUI 11 Android 10... with previously MIUI, there was no problem....
Click to expand...
Click to collapse
cheetahlm said:
Dear Agimax... I follow your advice... also using the last Magisk of Canary... but still cannot mount system directory as R/W. How to know that the Magisk isn't working properly?
Click to expand...
Click to collapse
I don't have problems with Root Explorer or any other app needing root on Q. Just an FYI Root explorer has a R/W button that toggles to R/O that you will need to press if it doesn't ask you to remount automatically. I would try re-installing Magisk from the Magisk manager itself and choosing the Direct Install option. If it can't re-install itself, it will error out and means you don't have root. Using Magisk Canary builds work without issues for me on Q. I have included screenshots showing root.
FYI i also originally installed 10.3.5 Official Global Stable -wiped and Formatted DATA. I had dirty flashed all of the weekly EU ROMS starting with 9.9.27, then 10.11, then 10.17 today. I only flashed latest Canary Magisk after every weekly dirty flash.
Agimax said:
In root explorer, mount the system directory as R/W. Then delete.... If it doesn't work, then your Magisk root isn't working properly.
Click to expand...
Click to collapse
Agimax said:
I don't have problems with Root Explorer or any other app needing root on Q. Just an FYI Root explorer has a R/W button that toggles to R/O that you will need to press if it doesn't ask you to remount automatically. I would try re-installing Magisk from the Magisk manager itself and choosing the Direct Install option. If it can't re-install itself, it will error out and means you don't have root. Using Magisk Canary builds work without issues for me on Q. I have included screenshots showing root.
FYI i also originally installed 10.3.5 Official Global Stable -wiped and Formatted DATA. I had dirty flashed all of the weekly EU ROMS starting with 9.9.27, then 10.11, then 10.17 today. I only flashed latest Canary Magisk after every weekly dirty flash.
Click to expand...
Click to collapse
Dear Agimax, you are great...!!!
Press R/W toggle and then..... done......!!!
I've searced for around more than one week for that...
THANK YOU VERY MUCH AGIMAX......!!!
Hi friends, every time I try to root the 11.0.1.0 Global, my phone end up in Bootloop (goes to TWRP every time). I tried to flash disable dm verity, but same results.
I'm using TWRP unnoficial (twrp-3.3.1-25-raphael-mauronofrio.img) but tried with the official too, same results.
This time I will try to flash Magisk v18, or older.
I'm using Mi 9T Pro Global Rom.
Clear Cache and Dalvik cache in TWRP
XblackdemonX said:
Clear Cache and Dalvik cache in TWRP
Click to expand...
Click to collapse
Okay, now I'm unrooted, what steps I need to do? TWRP >> Flash Magisk >> Flash DM Verity >> Wipe Cache/Dalvik? Or only Flash Magisk via TWRP and Wipe Caches?
Edit: same results, tried to flash magisk and clear cache and dalvik, bootloop again.
Edit²: tried to do a Factory Reset on TWRP and system booted up normally, Magisk Manager says that I'm rooted, but I can't install any module. Tested AdAway do get root, and all ok.
Edit³: Magisk Manager requested for some "additional files", I pressed to install and he rebooted the phone, now I'm stuck again in TWRP. Tried to clear Cache and Dalvik cache, same results.
RobertPirainoBR said:
Hi friends, every time I try to root the 11.0.1.0 Global, my phone end up in Bootloop (goes to TWRP every time). I tried to flash disable dm verity, but same results.
I'm using TWRP unnoficial (twrp-3.3.1-25-raphael-mauronofrio.img) but tried with the official too, same results.
This time I will try to flash Magisk v18, or older.
I'm using Mi 9T Pro Global Rom.
Click to expand...
Click to collapse
install magisk 19.3
Video install
https://drive.google.com/file/d/16vDfZDWBgtY8_ECB8aRWNed_6mqctY5T/view
@redmiK20ProIndonesia
RobertPirainoBR said:
Hi friends, every time I try to root the 11.0.1.0 Global, my phone end up in Bootloop (goes to TWRP every time). I tried to flash disable dm verity, but same results.
I'm using TWRP unnoficial (twrp-3.3.1-25-raphael-mauronofrio.img) but tried with the official too, same results.
This time I will try to flash Magisk v18, or older.
I'm using Mi 9T Pro Global Rom.
Click to expand...
Click to collapse
To install magisk on the global version, you must first remove the encryption.
1. return the system to its original state so that it boots, most likely it is flash via MiFlash (or via twrp ROM version for twrp)
2. flash DFE-script, reboot from twrp in twrp ( https://drive.google.com/open?id=1mFVdDlnp32g2AjdKlMq6tZcqK0krP-js )
3. format data-yes, reboot in system
4. check in the settings that encryption is disabled
5. flashing magisk in twrp
kancutluh said:
install magisk 19.3
Video install
https://drive.google.com/file/d/16vDfZDWBgtY8_ECB8aRWNed_6mqctY5T/view
@redmiK20ProIndonesia
Click to expand...
Click to collapse
alex9yust said:
To install magisk on the global version, you must first remove the encryption.
1. return the system to its original state so that it boots, most likely it is flash via MiFlash (or via twrp ROM version for twrp)
2. flash DFE-script, reboot from twrp in twrp ( https://drive.google.com/open?id=1mFVdDlnp32g2AjdKlMq6tZcqK0krP-js )
3. format data-yes, reboot in system
4. check in the settings that encryption is disabled
5. flashing magisk in twrp
Click to expand...
Click to collapse
I will try this now. I can do this with dirty flash? I'm able to boot system, with Magisk v20.1 installed and partially working (if I install the additional content in Magisk Manager will Bootloop again, and I can't install modules).
RobertPirainoBR said:
I will try this now. I can do this with dirty flash? I'm able to boot system, with Magisk v20.1 installed and partially working (if I install the additional content in Magisk Manager will Bootloop again, and I can't install modules).
Click to expand...
Click to collapse
You can flash the magisk-uninstaller 20.1.
and after format data-yes all your data will be gone.
Go to /data/adb/magisk/chromeos find "futility" file. Permission 644 for it.
Go to /data/adb/magisk find "BusyBox" file and permission 664 for it.
Reboot and done.
In future, when you flash any rom on k20 pro. Remember that do it if you flash magisk.
Good luck!
(Solution from 4pda)
shinigami_tsin said:
Go to /data/adb/magisk/chromeos find "futility" file. Permission 644 for it.
Go to /data/adb/magisk find "BusyBox" file and permission 664 for it.
Reboot and done.
In future, when you flash any rom on k20 pro. Remember that do it if you flash magisk.
Good luck!
(Solution from 4pda)
Click to expand...
Click to collapse
Wow this seems to have worked!
shinigami_tsin said:
Go to /data/adb/magisk/chromeos find "futility" file. Permission 644 for it.
Go to /data/adb/magisk find "BusyBox" file and permission 664 for it.
Reboot and done.
In future, when you flash any rom on k20 pro. Remember that do it if you flash magisk.
Good luck!
(Solution from 4pda)
Click to expand...
Click to collapse
This is great. I downloaded magiskhide and had to enable it through terminal then it showed up in the drop down browser for magisk but wasnt in modules list of magisk. None of the modules seem to download and go there. Is it supposed to be like that?
Vanmanman said:
This is great. I downloaded magiskhide and had to enable it through terminal then it showed up in the drop down browser for magisk but wasnt in modules list of magisk. None of the modules seem to download and go there. Is it supposed to be like that?
Click to expand...
Click to collapse
Same here, trying to install modules but don't show up on modules tab.
RobertPirainoBR said:
Same here, trying to install modules but don't show up on modules tab.
Click to expand...
Click to collapse
Yeap!
1. Flash magisk via twrp (suggest pitchblack)
2. Delete 2 files
3. Reboot (→solved bootloop)
4. Open magisk manager and update (if failed, close app and try again and agian) → after auto reboot (after 5 seconds), can solved issue "can not flash modules - of course with all modules flashed, it's showed in list).
RobertPirainoBR said:
Same here, trying to install modules but don't show up on modules tab.
Click to expand...
Click to collapse
Solution is here https://forum.xda-developers.com/mi-9t/help/phone-stuck-bootloop-try-to-install-t4007259
1. I back up my Internal storage to my PC
2. Format Data (In TWRP: Wipe -> Format Data)
3. I reboot back into recovery
4. I connected my device to PC via a cable and copy two files: "Magisk-v20.1.zip" and "Disable_Dm-Verity_ForceEncrypt_10.20.2019.zip" into Internal storage. Then rename "Disable_Dm-Verity_ForceEncrypt_10.20.2019.zip" to "Disable_ForceEncrypt.zip"
4. I flash "Magisk-v20.1.zip", then I reboot back into recovery again.
5. I flash "Disable_ForceEncrypt.zip" . Reboot to system and setting my phone like after flash a new room, and then I installed "MagiskManager-v7.4.0.apk"
It's working for me!
You can download "Disable_Dm-Verity_ForceEncrypt_10.20.2019.zip" here: https://forum.xda-developers.com/and...crypt-t3817389
Vanmanman said:
Solution is here https://forum.xda-developers.com/mi-9t/help/phone-stuck-bootloop-try-to-install-t4007259
1. I back up my Internal storage to my PC
2. Format Data (In TWRP: Wipe -> Format Data)
3. I reboot back into recovery
4. I connected my device to PC via a cable and copy two files: "Magisk-v20.1.zip" and "Disable_Dm-Verity_ForceEncrypt_10.20.2019.zip" into Internal storage. Then rename "Disable_Dm-Verity_ForceEncrypt_10.20.2019.zip" to "Disable_ForceEncrypt.zip"
4. I flash "Magisk-v20.1.zip", then I reboot back into recovery again.
5. I flash "Disable_ForceEncrypt.zip" . Reboot to system and setting my phone like after flash a new room, and then I installed "MagiskManager-v7.4.0.apk"
It's working for me!
You can download "Disable_Dm-Verity_ForceEncrypt_10.20.2019.zip" here: https://forum.xda-developers.com/and...crypt-t3817389
Click to expand...
Click to collapse
doesn't work, tried and stuck on boot loop
Vanmanman said:
Solution is here https://forum.xda-developers.com/mi-9t/help/phone-stuck-bootloop-try-to-install-t4007259
1. I back up my Internal storage to my PC
2. Format Data (In TWRP: Wipe -> Format Data)
3. I reboot back into recovery
4. I connected my device to PC via a cable and copy two files: "Magisk-v20.1.zip" and "Disable_Dm-Verity_ForceEncrypt_10.20.2019.zip" into Internal storage. Then rename "Disable_Dm-Verity_ForceEncrypt_10.20.2019.zip" to "Disable_ForceEncrypt.zip"
4. I flash "Magisk-v20.1.zip", then I reboot back into recovery again.
5. I flash "Disable_ForceEncrypt.zip" . Reboot to system and setting my phone like after flash a new room, and then I installed "MagiskManager-v7.4.0.apk"
It's working for me!
You can download "Disable_Dm-Verity_ForceEncrypt_10.20.2019.zip" here: https://forum.xda-developers.com/and...crypt-t3817389
Click to expand...
Click to collapse
I tried in many ways but did not succeed
Khaledms said:
I tried in many ways but did not succeed
Click to expand...
Click to collapse
Not sure sorry. I ended up waiting for a better version of Magisk to come out. Have you tried Magisk 20.3 on K20/mi96t android 10 miui 11?
Hi guys,
Try to format data in TWRP before the first reboot. Remember, this will clear your data.
It is very easy to get bootloop because of cryptography.
Good luck!