Related
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
It Is Now A Part Of The Main Module Of MultiFunctions & Its Thread https://forum.xda-developers.com/apps/magisk/module-multifunctions-bootloop-t3933386.
Click to expand...
Click to collapse
Introduction:
Simple Module To Clear The Dalvik Cache.
- Doing The Same Functionality Of Wiping Dalvik/ART Cache Thru TWRP Recovery
- Useful For Solving/Fixing Some Problems With The Installed Apps
- Removing All Remnants Of The Uninstalled Apps
- After The Installation & 1st Reboot, It Clears The Dalvik Cache & Disables Itself (Maybe It Takes About 5 Min. To Finish The Process)
- After Doing Its Functionality, Check The Free Space Of Internal Storage Which Should Be Increased/Maximized A Little Bit
- Enabling The Module = Doing Its Functionality & Disabling Itself (Next Reboot)
Current Version: 1.0.3.3
- For Magisk Users, Disable Magisk Core Only Mode From The Section Of Settings In Magisk Manager Which Is Required As An Essential Step To Activate The Functionality Of ClearDalvikCache
- For Activating The Functionality Of ClearDalvikCache, Use Any Root File Explorer Such MiXplorer --> Root --> data --> DreamerMods --> MultiFunctions --> DalvikCache --> Delete The File Of Disable From The Folder Of Active --> Reboot
Created: May.08.2018
Updated: May.09.2019
Download Link: Click Here
- For The Module Which Is Ended Its Name With v1300, It Supports Magisk v13.1(1310) To v13.6(1360)
- For The Module Which Is Ended Its Name With v1400, It Supports Magisk v14.0(1400) To v15.3(1531)
- For The Module Which Is Ended Its Name With v1500, It Supports Magisk v15.0(1500) To v17.3(17300)
- For The Module Which Is Ended Its Name With v17000, It Supports Magisk v17.0(17000) To v17.3(17300)
- For The Module Which Is Ended Its Name With v18000, It Supports Magisk v18.0(18000) To v18.1(18100)
- For The Module Which Is Ended Its Name With v19000, It Supports Magisk v19.0(19000) To The Latest Version
- For The Module Which Is Ended Its Name With Unity, It Supports Any-Rooting-Tool Such As SuperSU, Lineage-AddOnSU & Magisk
Installation:
- Magisk Manager --> Modules --> Add (+) --> Choose The Downloaded File --> Reboot
- Or Flash It Thru TWRP Recovery
- Or Flash It Thru ADB Sideload --> adb sideload Module.zip --> Reboot
- Or Using A Flash-Tool (Flasher) Such FlashFire, Flashify Or Rashr --> Flash ZIP File (Flash A Flashable ZIP File) --> Choose The Downloaded File --> Reboot
General Info:
- To Disable The Module For Magisk Users, Open Magisk Manager --> Modules --> The Module --> Tap On The Check Box/The True Icon --> Reboot
- To Enable The Module For Magisk Users, Open Magisk Manager --> Modules --> The Module --> Tap On The Uncheck Box --> Reboot
- To Uninstall The Module For Magisk Users, Open Magisk Manager --> Modules --> The Module --> Tap On The Bin Icon --> Reboot
- To Disable The Module For All Users [Non-Magisk Users & Magisk Users], Use Any Root File Explorer Such MiXplorer --> Root --> data --> DreamerMods --> MultiFunctions --> The Module --> Copy The File Of Disable To The Folder Of Active (Or Delete The File Of Disable From The Folder Of Inactive) --> Reboot
- To Enable The Module For All Users [Non-Magisk Users & Magisk Users], Use Any Root File Explorer Such MiXplorer --> Root --> data --> DreamerMods --> MultiFunctions --> The Module --> Delete The File Of Disable From The Folder Of Active (Or Copy The File Of Disable To The Folder Of Inactive) --> Reboot
- To Uninstall The Module For All Users [Non-Magisk Users & Magisk Users] (Unity), Reflash The Module
- In-Case Of Facing A Bootloop/Bootscreen/Blackscreen Issue Due To Installing/Configuring An App, Download SafeMode4Magisk From This Thread https://forum.xda-developers.com/apps/magisk/module-safe-mode-bootloop-bootscreen-t3847422 Then Flash It
- In-Case Of Facing A Bootloop/Bootscreen/Blackscreen Issue Due To Adding App/Activity/Process To Magisk Hide, Download ClearHideList4Magisk From This Thread https://forum.xda-developers.com/apps/magisk/module-hide-list-bootloop-bootscreen-t3849208 Then Flash It
- In-Case Of Facing A Bootloop/Bootscreen/Blackscreen Issue Due To Flashing A Module, Download CoreOnlyMode4Magisk From This Thread https://forum.xda-developers.com/apps/magisk/module-core-mode-bootloop-solver-modules-t3817366 Then Flash It
Click On Thanks Button If The Module/Post Is Useful (Dreamer(3MF))
>>> Sharing A Good Thought Is Gold <<<
----------------------------------------------------------------------------------------------------------------
SELinux Mode Inverter - Microsoft Intune Company Portal Hider - Other Modules
----------------------------------------------------------------------------------------------------------------
Reserved for News/Updates #1
Downloading
Enviado desde mi ONEPLUS A5010 mediante Tapatalk
Updated ClearDalvikCache4Magisk To v1.0.2!
Changelog: Checking Its Path.
liver20 said:
Downloading
Enviado desde mi ONEPLUS A5010 mediante Tapatalk
Click to expand...
Click to collapse
Did You Try The Latest Version?
Dreamer(3MF) said:
Did You Try The Latest Version?
Click to expand...
Click to collapse
Here we go
Enviado desde mi ONEPLUS A5010 mediante Tapatalk
For Magisk v1400, Download ClearDalvikCache4Magisk-v1.0.2(v1400)(3MF).zip
Kindly Be Informed That
- For The Module Which Is Ended Its Name With v1400, It Will Support Magisk v14.0(1400) To v15.3(1531)
- For The Module Which Is Ended Its Name With v1500, It Will Support Magisk v15.0(1500) To The Latest Version Which Is Currently v16.4(1642)
I Am Asking Our Mates To Share The Feedbacks/Ideas/Questions To Enhance/Modify The Module.
I used the v1500 file and it worked perfectly. I don't know how you'd better it.
Works just fine.
Thanks a lot.
Sent from my SM-N910F using Tapatalk
u81 said:
I used the v1500 file and it worked perfectly. I don't know how you'd better it.
Works just fine.
Thanks a lot.
Sent from my SM-N910F using Tapatalk
Click to expand...
Click to collapse
Thanks Mate. I Am Thinking Of Creating A Module For Cleaning Social Media Apps Cache So What Is Your Opinion About That & The Apps Which You Would Like To Be Included?
That would be awesome as that is indeed the second biggest drain.
WhatsApp , Facebook, Facebook messenger & Instagram being the worst.
Look forward to that effort.
Dreamer(3MF) said:
Thanks Mate. I Am Thinking To Create A Module For Cleaning Social Media Apps Cache So What Do You Think About That & The Apps Which You Would Like To Be Included?
Click to expand...
Click to collapse
Sent from my SM-N910F using Tapatalk
u81 said:
That would be awesome as that is indeed the second biggest drain.
WhatsApp , Facebook, Facebook messenger & Instagram being the worst.
Look forward to that effort.
Sent from my SM-N910F using Tapatalk
Click to expand...
Click to collapse
The Main Problem Is There Are 2 Categories The First One Is The App Which Its Data Is Kept On Its Servers Continuously Such As Facebook/Instagram & The Second One Is The App Which Its Data Is Kept On Its Servers Temporarily Such As WhatsApp/Facebook Messenger.
You Can Return The Data Of The 1st Category App But Not For The 2nd Category App So What About That?
Dreamer(3MF) said:
The Main Problem Is There Are 2 Categories The First One Is The App Which Its Data Is Kept On Its Servers Continuously Such As Facebook/Instagram & The App Which Its Data Is Kept On Its Servers Temporarily Such As WhatsApp/Facebook Messenger.
You Can Return The Data Of The 1st Category App But Not For The 2nd Category App So What About That?
Click to expand...
Click to collapse
I would love to answer that if I only I could.
I'm completely dumb in those respects.... Sorry
Sent from my SM-N910F using Tapatalk
Thanks you for providing this module
For Passing The SafetyNet, Check This Post https://forum.xda-developers.com/ap...playstore-services-data-t3789498/post76682978.
good job
@ultradj83 Try The Following
- Download ClearDalvikCache4Magisk From This Thread https://forum.xda-developers.com/apps/magisk/module-dalvik-cache-t3787264 & Flash It Thru Magisk Manager Then Reboot
- If It Didn't Work, Try The Mentioned Steps In The Following Post https://forum.xda-developers.com/ap...ll-modules-magisk-v13-3-t3800435/post77044632
- If It Didn't Work, Download CoreOnlyMode4Magisk From This Thread https://forum.xda-developers.com/apps/magisk/module-core-mode-bootloop-solver-modules-t3817366 & Flash It Thru TWRP Recovery (Or Thru Magisk Manager Then Reboot)
Hi, great module.
Does somebody know a similar module for Xposed??
I mean, I used it with Magisk, but I passed to SuperSu.
So I would know a similar module/app that can do the cleaning, without to have to always go to TWRP??
Any idea, or work around??
Thx.
How is this different from simply manually cleaning cache/dalvik in recovery?
It Is Now A Part Of The Main Module Of MultiFunctions & Its Thread https://forum.xda-developers.com/apps/magisk/module-multifunctions-bootloop-t3933386.
Click to expand...
Click to collapse
Introduction:
Simple Module To Boot The Android Into Safe Mode.
- In-Case Of Facing A Bootloop Issue Due To Installing/Configuring An App, Flash This Module
- This Module Disables All Installed Apps (User Apps) & Also The Root Access By Enabling Safe Mode & After Booting, Uninstall Any App Which Caused The Bootloop/Issue (From Settings --> Apps --> The App --> Storage --> Clear Cache --> Clear Data --> Uninstall) Then Reboot (Rebooting The Android Is Required To Get Back To The Normal Mode)
- Safe Mode Gives The Device The Ability To Not Open Any App Which Is Installed As A User App, And A "Safe Mode" Badge Will Appear In The Lower Left Corner Of The Screen
- After The Installation & Booting, It Puts The Android In Safe Mode & Disables Itself
- Enabling This Module = Doing Its Functionality & Disabling Itself (Next Reboot)
Current Version: 1.0.3.3
- For Magisk Users, Disable Magisk Core Only Mode From The Section Of Settings In Magisk Manager Which Is Required As An Essential Step To Activate The Functionality Of SafeMode
- For Activating The Functionality Of SafeMode, Use Any Root File Explorer Such MiXplorer --> Root --> data --> DreamerMods --> MultiFunctions --> SafeMode --> Delete The File Of Disable From The Folder Of Active --> Reboot
- For Using The Module Thru ADB Shell/TWRP Terminal [The Module Must Be Pre-Installed Via Magisk Manager/TWRP Recovery/ADB Sideload], Write The Following Commands --> rm -f /data/DreamerMods/MultiFunctions/SafeMode/Active/disable (Click On Enter) --> reboot (Click On Enter)
Created: Sept.26.2018
Updated: May.09.2019
Download Link: Click Here
- For The Module Which Is Ended Its Name With v1300, It Supports Magisk v13.1(1310) To v13.6(1360)
- For The Module Which Is Ended Its Name With v1400, It Supports Magisk v14.0(1400) To v15.3(1531)
- For The Module Which Is Ended Its Name With v1500, It Supports Magisk v15.0(1500) To v17.3(17300)
- For The Module Which Is Ended Its Name With v17000, It Supports Magisk v17.0(17000) To v17.3(17300)
- For The Module Which Is Ended Its Name With v18000, It Supports Magisk v18.0(18000) To v18.1(18100)
- For The Module Which Is Ended Its Name With v19000, It Supports Magisk v19.0(19000) To The Latest Version
- For The Module Which Is Ended Its Name With Unity, It Supports Any-Rooting-Tool Such As SuperSU, Lineage-AddOnSU & Magisk
Installation:
- Flash It Thru TWRP Recovery
- Or Magisk Manager --> Modules --> Add (+) --> Choose The Downloaded File --> Reboot
- Or Flash It Thru ADB Sideload --> adb sideload Module.zip --> Reboot
- Or Using A Flash-Tool (Flasher) Such FlashFire, Flashify Or Rashr --> Flash ZIP File (Flash A Flashable ZIP File) --> Choose The Downloaded File --> Reboot
General Info:
- To Disable The Module For Magisk Users, Open Magisk Manager --> Modules --> The Module --> Tap On The Check Box/The True Icon --> Reboot
- To Enable The Module For Magisk Users, Open Magisk Manager --> Modules --> The Module --> Tap On The Uncheck Box --> Reboot
- To Uninstall The Module For Magisk Users, Open Magisk Manager --> Modules --> The Module --> Tap On The Bin Icon --> Reboot
- To Disable The Module For All Users [Non-Magisk Users & Magisk Users], Use Any Root File Explorer Such MiXplorer --> Root --> data --> DreamerMods --> MultiFunctions --> The Module --> Copy The File Of Disable To The Folder Of Active (Or Delete The File Of Disable From The Folder Of Inactive) --> Reboot
- To Enable The Module For All Users [Non-Magisk Users & Magisk Users], Use Any Root File Explorer Such MiXplorer --> Root --> data --> DreamerMods --> MultiFunctions --> The Module --> Delete The File Of Disable From The Folder Of Active (Or Copy The File Of Disable To The Folder Of Inactive) --> Reboot
- To Uninstall The Module For All Users [Non-Magisk Users & Magisk Users] (Unity), Reflash The Module
- In-Case Of Facing A Bootloop/Bootscreen/Blackscreen Issue Due To Adding App/Activity/Process To Magisk Hide, Download ClearHideList4Magisk From This Thread https://forum.xda-developers.com/apps/magisk/module-hide-list-bootloop-bootscreen-t3849208 Then Flash It
- In-Case Of Facing A Bootloop/Bootscreen/Blackscreen Issue Due To Flashing A Module, Download CoreOnlyMode4Magisk From This Thread https://forum.xda-developers.com/apps/magisk/module-core-mode-bootloop-solver-modules-t3817366 Then Flash It
Click On Thanks Button If The Module/Post Is Useful (Dreamer(3MF))
>>> Sharing A Good Thought Is Gold <<<
----------------------------------------------------------------------------------------------------------------
SELinux Mode Inverter - Clear Dalvik Cache - Core Only Mode - Other Modules
----------------------------------------------------------------------------------------------------------------
Reserved for News/Updates #1
Reserved for News/Updates #2
Cool!! Look like I gave you some idea, for a proper Safe Mode Module, for the whole Android system.
The other was a Safe Mode, kind , for only Magisk.
Cool to can boot Android in Safe Mode, just by flash a zip thru TWRP, as getting in Safe Mode with hard keys is very frustrating...
Anyway both goes to my ToolBox.
:good:
saoudien07 said:
Cool!! Look like I gave you some idea, for a proper Safe Mode Module, for the whole Android system.
The other was a Safe Mode, kind , for only Magisk.
Cool to can boot Android in Safe Mode, just by flash a zip thru TWRP, as getting in Safe Mode with hard keys is very frustrating...
Anyway both goes to my ToolBox.
:good:
Click to expand...
Click to collapse
P.S. CoreOnlyMode4Magisk Is For Uninstalling/Disabling Magisk Modules Which Caused The Booloop/Bootscreen Issue But SafeMode4Magisk Is For Uninstalling User Apps & Also Clearing Cache&Data Of User/System Apps Which Caused The Booloop/Bootscreen Issue
Dreamer(3MF) said:
P.S. CoreOnlyMode4Magisk Is For Uninstalling/Disabling Magisk Modules Which Caused The Booloop/Bootscreen Issue But SafeMode4Magisk Is For Uninstalling User Apps & Also Clearing Cache&Data Of User/System Apps Which Caused The Booloop/Bootscreen Issue
Click to expand...
Click to collapse
Yep I got well
One is for Magisk, BootLoop caused by guilty Magisk Modules, so possibility to remove them >>> CoreOnlyMode
And SafeMode, is for the Android OS itself, so App guilty BootLoop.
Hope it may help other, our litle chat
Hi, I have a problem I enabled core mode in the magisk manager menu to bypass safety, restarted it worked I logged into the app. But then i disabled the core only mode and rebooted my phone booted the first screen where it says Samsung but won't go into the boot loading screen. The LED Light is on but the screen is just black and doesn't change. I flashed this zip to re-enable the core only mode and my phone will boot but I can't disable core only without it getting stuck on a black screen. Any help would be appreciated
Apexpredator12 said:
Hi, I have a problem I enabled core mode in the magisk manager menu to bypass safety, restarted it worked I logged into the app. But then i disabled the core only mode and rebooted my phone booted the first screen where it says Samsung but won't go into the boot loading screen. The LED Light is on but the screen is just black and doesn't change. I flashed this zip to re-enable the core only mode and my phone will boot but I can't disable core only without it getting stuck on a black screen. Any help would be appreciated
Click to expand...
Click to collapse
This Thread Is For SafeMode4Magisk Not CoreOnlyMode4Magisk But Anyway Check This Post From The Thread Of CoreOnlyMode4Magisk.
Dreamer(3MF) said:
Introduction:
Simple Module To Open Magisk In Core Only Mode To Help For Removing Any Module Which Causes A Bootloop.
- In-Case Of Facing A Bootloop Issue Due To Flashing A Module, You Need To Put A Copy Of CoreOnlyMode4Magisk On SD-Card/Internal Memory Then Flash This Module Thru TWRP Recovery
- This Module Disables All Magisk Modules By Enabling Magisk Core Only Mode & After Booting, You Can Disable Magisk Core Only Mode From The Section Of Settings In Magisk Manager Then Removing/Disabling The Module(s) Which Caused The Bootloop/Issue From The Section Of Modules In Magisk Manager Then Reboot (Rebooting The Android Is Required To Load The Rest Of Modules)
Click to expand...
Click to collapse
Cool module thankyou.
Updated SafeMode4Magisk To v1.0.0A!
Changelog: Checking The Paths
- For The Module Which Is Ended Its Name With v1300, It Supports Magisk v13.1(1310) To v13.6(1360)
- For The Module Which Is Ended Its Name With v1400, It Supports Magisk v14.0(1400) To v15.3(1531)
- For The Module Which Is Ended Its Name With v1500, It Supports Magisk v15.0(1500) To The Latest Version Which Is Currently v17.2(17200)
- For The Module Which Is Ended Its Name With v17000, It Supports Magisk v17.0(17000) To The Latest Version Which Is Currently v17.2(17200)
Updated MultiFunctions4Magisk To 1.0.3.3!
Changelog: SafeMode Is A Sub-Module Of The Main Module Of MultiFunctions Which Supports Currently The Following Functions [Clearing DalvikCache-PlayStoreWithServices-MagiskHideList, Changing The SELinux Mode, Booting The Android Into Safe Mode & Opening Magisk In Core Only Mode]
- For The Module Which Is Ended Its Name With v1300, It Supports Magisk v13.1(1310) To v13.6(1360)
- For The Module Which Is Ended Its Name With v1400, It Supports Magisk v14.0(1400) To v15.3(1531)
- For The Module Which Is Ended Its Name With v1500, It Supports Magisk v15.0(1500) To v17.3(17300)
- For The Module Which Is Ended Its Name With v17000, It Supports Magisk v17.0(17000) To v17.3(17300)
- For The Module Which Is Ended Its Name With v18000, It Supports Magisk v18.0(18000) To v18.1(18100)
- For The Module Which Is Ended Its Name With v19000, It Supports Magisk v19.0(19000) To The Latest Version
- For The Module Which Is Ended Its Name With Unity, It Supports Any-Rooting-Tool Such As SuperSU, Lineage-AddOnSU & Magisk
Kindly Be Informed That
- For Magisk Users, Disable Magisk Core Only Mode From The Section Of Settings In Magisk Manager Which Is Required As An Essential Step To Activate The Functionality Of SafeMode
- For Activating The Functionality Of SafeMode, Use Any Root File Explorer Such MiXplorer --> Root --> data --> DreamerMods --> MultiFunctions --> SafeMode --> Delete The File Of Disable From The Folder Of Active --> Reboot
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
Introduction:
Modules For SuperSU
- Download The Module Of MultiFunctionsPlus To Do The Next Functions [Clearing DalvikCache-PlayStoreWithServices-MagiskHideList, Changing The SELinux Mode, Booting The Android Into Safe Mode, Opening Magisk In Core Only Mode, Controlling The Virtual Memory (Swap), Changing The Swappiness Value, Keeping MagiskDaemon-MagiskHide Running, Changing DoubleTap2Wake(DT2W) Status, Fixing PlayStore Device Certification Status - Passing SafetyNet, Enabling The Low Ram Configurations, Disabling The Other Magisk Modules, Disabling The Magisk General Scripts & More] From This Thread https://forum.xda-developers.com/apps/magisk/module-social-media-cache-advanced-t3799155 (Unity Version)
Created: Nov.13.2018
Updated: Dec.23.2019
Download Link: Mentioned In The Above Threads (Download Unity Version)
** Unity Installer: It Supports Any-Rooting-Tool Such SuperSU, Lineage-AddOnSU & Magisk
- P.S. If You Flash The Same Version Of Module Twice, The Module Will Remove Itself But If The Version Of Second Time Is Higher Than The Version Of First Time, The Module Will Update/Upgrade Itself
Installation:
- Flash It Thru A Custom-Recovery Such TWRP Recovery --> Reboot
- Or Flash It Thru ADB Sideload --> adb sideload TheFileNameOfModule.zip --> Reboot (P.S. Renaming The File To Have A Short One Is Recommended Such mfm.zip Before Using ADB Sideload)
- Or Using A Flash-Tool (Flasher) Such EX Kernel Manager, FK Kernel Manager, FlashFire Or Flashify --> Flash ZIP File --> Reboot
>>>Dreamer(3MF)<<<
>>> Sharing A Good Thought Is Gold <<<
----------------------------------------------------------------------------------------------------------------
Other Modules
----------------------------------------------------------------------------------------------------------------
Reserved For News/Updates #1
Reserved For News/Updates #2
Thanks Dreamer!
Reserved For News/Updates #3