Database Develop

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

[Tool][Aroma] Magisk Manager Recovery Tool V2.5

Warning: It's not a Magisk module!
Description
This is a Magisk module management tool that can be used in Recovery mode.
It's based on Aroma Installer.
You can manage almost everything in Magisk with this tool.
You can manage installed modules, enable/disable core only mode, and even manage Root rights.
What can it do
1. Enable/Disable modules
2. Enable/Disable modules mount
3. Remove modules at next reboot (support undo)
4. Remove modules directly
5. Enable/Disable Magisk core only mode
6. Enable/Disable Magisk Hide
7. Enable/Disable Zygisk
8. Enable/Disable DenyList
9. View module descriptions, versions, authors, etc.
10. View module content (directory structure)
11. Shrinking magisk.img (useable for Magisk v18.1 and earlier)
12. Clear MagiskSU logs
13. Manage Superuser rights
Feature
1.Friendly interface & easy to use.
2.Supported older recovery or even CWM.
Download
Github releases
or Download the latest version v2.5 via XDA
How to use
1. Reboot to recovery mode
2. Flash it
3. Enjoy!
Note
1. Only supported arm & arm64 architecture.
2. Will get stuck at Recovery for some device. This is a bug in Aroma Installer binary file and I can not fix it(about: see this issue).
3. If your device is using Qualcomm soc and model is greater than {660, 7xx, 835}, then this tool does not support it.
Github
https://github.com/Pzqqt/Magisk_Manager_Recovery_Tool
Thanks
DualBootUtilities (framework)
Magisk Manager for Recovery Mode (mm) (code of mount magisk.img)
ElementalX Kernel (Aroma Installer theme)
p7zip (7za)
tree (tree)
micropython (micropython binary)
usqlite (μSQLite library module for micropython)
If you have other questions, you can ask me in this post.

Changelog
V1.0 Alpha:
Initial Release
V1.0 Alpha5:
1.Now can recognize update & remove flag. Not allowed to operate modules with these flags to ensure stability.
2.Show "version" & "author", instead of "description".
V1.0 Alpha7:
1.Add switch to enable/disable auto_mount.
2.Draw a new "delete" icon.
V1.0 Alpha9:
1.More friendly user tips.
V1.1 Alpha:
1.If the zip binary is already have in /system/xbin or /system/bin, use it first.
2.Add a "Shrinking magisk.img" option
V1.1 Alpha2:
1.Fix "Error 1" if have not installed any Magisk modules.
V1.1 Alpha3:
1.Arch check: no longer check ro.build.version.sdk.
2.If module removed/with update flag/with remove flag, immediate prompt.
3.Fix wrong printing method in shrink-magiskimg.sh
V1.2 Alpha:
1.Give up zip, use 7za
V1.3 Alpha:
1.Improve magisk.img mount method
2.Draw a fake Magisk logo
3.Show module ID on title
4.Add an option to show module description
5.Version text italic
6.Code clean
V1.4 Alpha:
1.Show different icons depending on the module status
2.Adjust the method of getting module description
3.Add an option to enable/disable Magisk core only mode
4.Remove all unnecessary "-ex" parameters
5.Code clean
V1.5 Alpha:
1.No longer use textbox to return execution results (all use Alert dialog)
2.Dynamic enable/disable module(auto_mount) options
3.Adjust UI & some text (make it look more like the Magisk Manager app)
4.Code clean
V1.6 Alpha:
1.Support operate /data/adb/modules directory (compatible with magisk.img). And make some adjustments to the UI
2.7za: set compression method to 0 (reduce startup time by at least 30%)
3.Show more execution details when flashing
4.Shrinking magisk.img: only show results, no details
5.Code clean
V1.7 Alpha:
1.Force use DroidSansFallback font
2.Use an easier way to create symbolic link
3.Faster way to get magisk.img size
4.Mount /system as readonly
5.Support reading build.prop from system-as-root devices
6.Show installed Magisk version code in the welcome interface
7.Show magisk.img information (size & free) in the welcome interface
8.Remove useless partition information in the welcome interface
9.Show module's size on subtitle
10.Add an option to show module's recursive directory listing
11.Add an option to remove module at next reboot (and can undo this operation)
12.Code clean
V1.8 Alpha:
1.Show magisk.img used size instead of free size
2.Use an easier way to show installed Magisk version
3.License: change to GPL-3.0
4.Handle compatibility with Magisk v19.0
5.Code clean
Hotfix: Fix cannot handle modules with exception path
V1.9 Alpha:
1.Handle modules with exception path (module ID/directory name endswith \r)
2.Improve the mount_image & symlink_modules method again
3.With the help of Aroma Installer's built-in file_getprop function, reduce startup time by at least 50%
4.Add -h flag to du command
5.Improve generate icon prop method, shorten the interface conversion time
6.Hide unavailable options directly
7.Get the module's enabled/disabled status accurately
8.Add an option to clear the MagiskSU logs
9.Add an option to remove all saved apps MagiskSU permissions
10.Add an option to reject all saved apps MagiskSU permissions
11.Add an option to allow all saved apps MagiskSU permissions
12.Add build script
13.Code clean
V2.0 Alpha:
1.List installed modules: sort by module id(case insensitive) or sort by module name
2.Add a debug option to enable geek mode, it will disable a lot of unnecessary "operational success" dialog in this tool
3.Add an option to uninstall Magisk(include latest Magisk-uninstaller package)
4.Add an option to manage Root rights
5.Remove some residual options from v1.9
6.Some UI & text adjustments
7.Code clean
V2.1 Alpha:
1.Automatic creation modules dir when MAGISK_VER_CODE > 18000
2.Automatic creation /data/adb/magisk.img when MAGISK_VER_CODE <= 18000(drop check /data/magisk.img)
3.Shrink magisk.img: Fix sometimes "awk: not found"
4.Give some sorting tasks to sqlite3
5.Rebuild tree binary with Android ndk
6.Include a prebuilt sqlite3 binary(built with Android ndk)
7.List installed modules: force sort by module name
8.Some UI & text adjustments, and remove "Geek mode" debug option
9.Update Magisk uninstaller to 20190501
10.Drop unused resources
11.Show more execution details
12.Code clean
V2.2:
1.Install Magisk internal busybox before use(make sure all common commands are available)
2.No need mount /system now
3.Force use prebuilt sqlite3 binary
4.Unblock the restriction of force remove modules
5.Root manager: show the uid of item in list
6.Update sqlite3 binary to 3290000
7.Rebuild 7za with Frankenstein NDK(reduce binary size by 40%)
8.Real-time calculation of modules number and total size
9.Add an option to enable/disable MagiskHide
10.Update Magisk uninstaller to 20191011
11.Added "About" interface... and some easter eggs
V2.3:
1.Fix "Clear MagiskSU logs" not working on Magisk v20.2+
2.Add module backup/restore options(Experimental)
3.Update Magisk uninstaller to 20200110
4.Update sqlite3 binary to 3300100
V2.4
1. Move the binary files to the bin directory
2. Use Aroma's "include" method to simplify overly long and complex code
3. Fix an issue where sometimes the name of backed up module was incorrectly displayed
4. Unmount all unnecessary partitions when preparing
5. Add MagiskHide warning for v20.4+
6. Disable core only mode switch in Magisk v21.0+
7. Disable MagiskHide switch if Magisk version number >= 23010
8. Add an option to enable/disable Zygisk
9. Add an option to enable/disable Deny List
10. Move Magisk Core Only Mode, MagiskHide, Zygisk and Deny List to the new "Magisk Settings" menu
11. Handling the case where no some key in the Magisk database
12. Remove the uninstall Magsik option
V2.5
1. Compatible with Magisk 24305+
2. Rewrite some script with Python (use micropython as the interpreter)
3. aroma-config: Use magisk busybox's sh instead of /sbin/sh
4. Module size is not displayed for now (until I find a way to reimplement it)

Works great thanks

Updated

Pzqqt said:
Warning: It's not a Magisk module!
Description
This is a Magisk module management tool that can be used in Recovery mode.
It's based on Aroma Installer.
This tool will allows you to perform certain operations, such as enabling, disabling, and removing, on the installed Magisk modules.
Feature
1.Friendly interface & easy to use.
2.Supported older recovery or even CWM.
Download
Google Drive
or Download the latest version v1.2 Alpha via XDA
How to use
1.Reboot to recovery mode
2.Flash it
3.Enjoy!
Note
1.Only supported arm & arm64 architecture. Not supported x86 & x64 architecture.
Github
https://github.com/Pzqqt/Magisk_Manager_Recovery_Tool
Thanks
I borrowed some of the code and resources for the following projects.
If I infringe on the interests of anyone. Please tell me. I will deal with it in time.
DualBootUtilities(framework)
Magisk Manager for Recovery Mode (mm)(code of mount magisk.img)
ElementalX Kernel(Aroma Installer theme)
p7zip(7za binary)
If you have other questions, you can ask me in this post.
Click to expand...
Click to collapse
I can't thank you enough for this app. It saved me from a troublesome module. (I'm looking at you, xposed)
It's easy to use, and has nice UI.
Again, thank you very much!

gamalkevin said:
I can't thank you enough for this app. It saved me from a troublesome module. (I'm looking at you, xposed)
It's easy to use, and has nice UI.
Again, thank you very much!
Click to expand...
Click to collapse
Welcome

Now you can see the status of each module more intuitively, just like this

Well known, magisk.img was removed in Magisk v18.2 build.
The modules will be installed in the /data/adb/modules directory.
It is beneficial to do so. Of course we will follow it.
Magisk Manager Recovery Tool has been updated to v1.6-Alpha. Now it supports operating /data/adb/modules directory to manage modules.

What is the difference between CH magisk recovery and magisk recovery zip

sachin karinki said:
What is the difference between CH magisk recovery and magisk recovery zip
Click to expand...
Click to collapse
I'm gonna take a guess that CH means chinese

Thanx for this tool:good: Is it possible to get a non-transparent theme? On my Z1c the aroma installer is transparent, which makes it hard to read anything.. Thanx again

Ænimal said:
Thanx for this tool:good: Is it possible to get a non-transparent theme? On my Z1c the aroma installer is transparent, which makes it hard to read anything.. Thanx again
Click to expand...
Click to collapse
Transparent theme? Maybe it's a bug in your recovery or Aroma Installer. no problem on my device. Sorry I cannot fix it. Youneed to find a solution yourself.

Thank you for your great work!
God bless you ?️?️?️

Ænimal said:
Thanx for this tool:good: Is it possible to get a non-transparent theme? On my Z1c the aroma installer is transparent, which makes it hard to read anything.. Thanx again
Click to expand...
Click to collapse
What version of twrp are you using ? The latest ? Flash the latest and test it
The official site of twrp is: http://twrp.me

joluke said:
What version of twrp are you using ? The latest ? Flash the latest and test it
The official site of twrp is: http://twrp.me
Click to expand...
Click to collapse
Thanx, I know, but there are no official updates for my device. I'm using 3.2.3-0 and everything else is working fine. I'll just wait for an update of the other magisk manager for compatibility with Magisk 18.2..

Absolutely easier than the vi text editor based one, keep it up!

Hey...
Why not go one step further...
Add in flashing magisk from your tool (external zip)
And
Add in removing magisk from your boot.img (ala the uninstall button in the Manager app)

rignfool said:
Hey...
Why not go one step further...
Add in flashing magisk from your tool (external zip)
And
Add in removing magisk from your boot.img (ala the uninstall button in the Manager app)
Click to expand...
Click to collapse
This will increase the zip file size and is reinventing the wheel.

v2.0-Alpha release!
This is probably the most powerful release d to date.
Magisk Manager Recovery Tool is no longer a simple Magisk modules management tool. It has to be a real "Magisk Manager for Recovery Mode".:fingers-crossed:
Now what can it do?
1.Enable/Disable modules
2.Enable/Disable modules mount
3.Remove modules at next reboot(support undo)
4.Remove modules directly(useable for Magisk v18.1 and earlier)
5.Enable/Disable Magisk core only mode
6.View module descriptions, versions, authors, etc.
7.View module content(directory structure)
8.Shrinking magisk.img(useable for Magisk v18.1 and earlier)
9.Clear MagiskSU logs
10.Manage Superuser rights
11.Uninstall Magisk
Enjoy it!

Hello. Could you tell me if it works on Android pie with rom samsung? Thx

[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?

How to root Android 11 with Magisk

This is the guide that how you can root Android 11 ROMs without failing safetynet​
This is only tested in Asus Max M2 (Try at your own risk if in any other phone)
Requirements :
Android 11 (eg. Pixel Experience 11 Beta)​
Download three files attached in below​
Custom recovery any available​
And patience​
Guide :
Boot phone to recovery mode
Mount all partitions in Mount section
Flash MakeMeSAR file
Flash Magisk-v21.2 file
Then reboot
Go to Magisk manager
Then go to Magisk settings
Click on hide Magisk manager
Then rename it to different name such as JARVIS or anything
Then scroll down and enable MagiskHide
Then done
If your CTS profile still fails then flash the Safetynet fix file in Magisk
Reboot
Now your phone rooted with Magisk without failing Safetynet.
If this guide is helpful for you then hit Thanks

Jarvis ??

Surendra R sonawane said:
Jarvis ??
Click to expand...
Click to collapse
Soo what ?

[Solved][Question] How to delete /system/xbin files via Magisk Module?

Today I have installed Built-In BusyBox module by zgfg to overwrite meefik's busybox binaries in /system/xbin which I couldn't remove due Resource or Device Busy error.
Then I found out that busybox is one of the ways to detect modified android so I want to remove it but module unfortunately doesn't come with uninstaller so I am stuck with busybox in my /system/xbin directory with no way to remove. All I found on Magisk's docs is to replace files or directories not remove them but 2018's version said that removal is possible, just that it is hassle or something.
Can anyone help?
Additional info: I don't have any Custom Recovery and don't tell me to get one.
Click to expand...
Click to collapse
NOTE! To help others with same problem I am planning to compile answer as Magisk Module so please open PR in this repo:
Click to expand...
Click to collapse
GitHub - UltraStudioLTD/BuiltIn-BusyBox-Uninstaller: Uninstall busybox
Uninstall busybox. Contribute to UltraStudioLTD/BuiltIn-BusyBox-Uninstaller development by creating an account on GitHub.
github.com

Have you tried removal via TWRP?
How to disable Magisk modules without Magisk and TWRP recovery
Hi, I installed an incompatible Magisk module in the past, which cause bootloop of my phone. Co I dirty flashed my ROM (Pixel Experience) to get my phone work again. My current situation is that I cannot flash Magisk because an incompatible...
forum.xda-developers.com

lemon567 said:
Have you tried removal via TWRP?
How to disable Magisk modules without Magisk and TWRP recovery
Hi, I installed an incompatible Magisk module in the past, which cause bootloop of my phone. Co I dirty flashed my ROM (Pixel Experience) to get my phone work again. My current situation is that I cannot flash Magisk because an incompatible...
forum.xda-developers.com
Click to expand...
Click to collapse
I don't have TWRP and I can't install any Custom Recovery.
Please don't tell me to follow that or this instructions to install them, I followed everything and still no luck.

What you could do is enter safmode of your phone (Google how to enter safe mode for your phone) and remove the files manually or use the BusyBox cleaner zip and flash it in magisk manager and if you're lucky it will remove it
Release v1.29.0-YDS-201807132149 · yashdsaraf/bb-bot
Bot to compile, package and release busybox for all android architectures - Release v1.29.0-YDS-201807132149 · yashdsaraf/bb-bot
github.com

Unfortunately safe mode in my phone is kinda broken, I think. Cause every 3rd party app was not only disabled but also disappeared like magic. Also I don't trust unknown ZIPs so I haven't tried that link.
**I solved problem by disabling every Magisk module I had, rebooting and after that it succeed in deletion with no problem**