Install Magisk Module using TWRP - Magisk

Hi, how do I flash a Magisk Module using TWRP?
Simply flashing the Magisk Module in TWRP throws out an error code of 1.
I do not have Magisk (or the manager) installed because I have multiple apps with ridiculous root detection that can't be bypassed with MagiskHide.

Before you Need root
Inviato dal mio AC2003 utilizzando Tapatalk

Specifically, you'll need to have Magisk installed. Magisk modules can't be installed without Magisk...

Didgeridoohan said:
Specifically, you'll need to have Magisk installed. Magisk modules can't be installed without Magisk...
Click to expand...
Click to collapse
Got it, thanks!

Related

Magisk failed to start after installing a module. How to remove this module?

Hi,
after installing App Systemizer, Magisk failed to start after reboot. Magisk Manager shows the installed version (11.1) but no root (MagiskSU). The menu for deinstalling modules is not available.
How can I remove the App Systemizer?
(Magisk 11.1, LineageOS14.1)
hmpffff said:
Hi,
after installing App Systemizer, Magisk failed to start after reboot. Magisk Manager shows the installed version (11.1) but no root (MagiskSU). The menu for deinstalling modules is not available.
How can I remove the App Systemizer?
(Magisk 11.1, LineageOS14.1)
Click to expand...
Click to collapse
Use magisk-mount in this thread:
https://forum.xda-developers.com/apps/magisk/collection-magisk-modules-t3445257
After flashing, you can navigate to and delete the module's folder.
Thank you. Works now.
Interestingly, after installing magisk-mount Magisk started up correctly and with root. What…

Root using Magisk v14

Hello,
I just got my P10 (VTR-L29) yesterday, coming from a P8 Lite that I used to play a lot with and I already miss the adblock and the clean debloated system.
According to the new version of Magisk here, there is a new install method that works if you don't have a custom recovery like it used to be in the past. The new method modifies the boot.img via Magisk Manager, stores it in a folder and then you have to flash it with adb.
My question is: Do I have to unlock my phone in order to do that trick? Anyone else that tried something similar?
Nobody?
Maybe I'm not clear enough..
Steps to reproduce:
-install Magisk Manager 14 and use the inside app patcher
-find the patched boot.img on storage
-move the boot.img in PC storage
-use the PC in order to flash the patched boot.img
-reboot and wait
It's supposed to work that way but I don't want to unlock the bootloader,atleast for now.
Is it safe to do?
Xperias do not boot with the bootloader locked if boot.img is changed. I guess it will be the same for Huaweis.
So the only way to do that is to unlock the bootloader..seems like I have to do it lol.
Magisk v14 is working on my device. Unfotunately, i cannot pass safetynet. How about you guys?
Working but I Guess that You unlocked the bootloader,right?
You can try to use the universal safetynet fix, flash it in twrp and check.
Firicel69 said:
Working but I Guess that You unlocked the bootloader,right?
You can try to use the universal safetynet fix, flash it in twrp and check.
Click to expand...
Click to collapse
Already tried that (the new one for v14). Unfortunately, it didn't work.
Thank you anyway
garris_bibop said:
Magisk v14 is working on my device. Unfotunately, i cannot pass safetynet. How about you guys?
Click to expand...
Click to collapse
I had the same problem. Maybe my experience will help:
Open Magisk manager and check Log->Magisk. Are there any messages from MagiskHide? It should be.
Try this:
1. Open Magisk manager and disable Magisk hide.
2. Reboot
3. Open Magisk manager and enable Magisk hide.
I used commands in Terminal Emulator
Code:
su
magiskhide --disable
magiskhide --enable
At first it didn't work out but after a lot of desperate enabling/disabling and few reboots MagiskHide started to work (I couldn't determine the reason of its misbehaving).
For now I successfully pass SafetyNet checks.

Magisk 15.3 make me confused

I remember when I'm using Magisk 14.0 on Nougat 7.1.2 and Oreo 8.0 when i install module and then when i check module on Magisk Manager the module was installed
But when i install Magisk 15.3 on Oreo 8.1 when i install the module and then check on Magisk Manager the module doesn't installed properly even in twrp say instalation complete i try to install module via Magisk Manager first it was installed but when i reboot to recovery to install Magisk module which can be installed via recovery and then opening again module menu the module doesn't installed properly again instead it makes me more confused how to install module on Magisk 15.3
I forgot this
ZidanBlaster said:
I forgot this
Click to expand...
Click to collapse
Instead of all those screenshots it would have been more useful if you had provided the installation log, recovery log and Magisk log...
One thing to try is a complete uninstall and reinstall of Magisk.
Didgeridoohan said:
Instead of all those screenshots it would have been more useful if you had provided the installation log, recovery log and Magisk log...
One thing to try is a complete uninstall and reinstall of Magisk.
Click to expand...
Click to collapse
Ok when i trying to unistall and reinstall Magisk some of module can be installed but some of module doesn't installed properly when i check it the problem was being caused by this
I:Found no matching fstab entry for uevent device '/devices/virtual/block/loop1' - change
Here's the recovery log
ZidanBlaster said:
Ok when i trying to unistall and reinstall Magisk some of module can be installed but some of module doesn't installed properly when i check it the problem was being caused by this
I:Found no matching fstab entry for uevent device '/devices/virtual/block/loop1' - change
Here's the recovery log
Click to expand...
Click to collapse
And what about the Magisk log? Even better would be if you could install the v15.3 beta (only difference is more verbose logging) and provide the magisk_debug.log from /data/adb.
Didgeridoohan said:
And what about the Magisk log? Even better would be if you could install the v15.3 beta (only difference is more verbose logging) and provide the magisk_debug.log from /data/adb.
Click to expand...
Click to collapse
Ok i try later

[Q] How can I correctly uninstall EdXposed?

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?

Should I uninstall SuperSU before installing Magisk?

Hi!
I have rooted Samsung S7 Edge with android 7. I currently have SuperSU v2.79 installed. I want to install Magisk because I want to hide root from certain apps. Should I remove SuperSu before I install Magisk?
Other question is that here https://topjohnwu.github.io/Magisk/faq.html I read that Magisk no longer hides root because now the new way is to use Magisk modules. Do I even need Magisk at all or if I have TWRP 3.1.0.0 can this also be used to install those Magisk modules? Or would it be best to grab some older Magisk that has root hider there already?
sysctl said:
Hi!
I have rooted Samsung S7 Edge with android 7. I currently have SuperSU v2.79 installed. I want to install Magisk because I want to hide root from certain apps. Should I remove SuperSu before I install Magisk?
Other question is that here https://topjohnwu.github.io/Magisk/faq.html I read that Magisk no longer hides root because now the new way is to use Magisk modules. Do I even need Magisk at all or if I have TWRP 3.1.0.0 can this also be used to install those Magisk modules? Or would it be best to grab some older Magisk that has root hider there already?
Click to expand...
Click to collapse
yes u should, always use the latest one
Is it good enough to uninstall SuperSU app when android is running or should I reboot to TWRP and do some magic there?

Categories

Resources