Now i'm on lineageOS 18, i want to modify my status bar and another system aspects. Can you suggest me any magisk module or zip archive for TWRP?
I use these two, make sure you Install the zygisk version of LSPosed, if you're on Magisk 24.3+.
Fox's Mmm (https://github.com/Fox2Code/FoxMagiskModuleManager)
LSPosed zygisk (https://github.com/LSPosed/LSPosed/releases)
M1KTA said:
Now i'm on lineageOS 18, i want to modify my status bar and another system aspects. Can you suggest me any magisk module or zip archive for TWRP?
Click to expand...
Click to collapse
I think there is some apps for your status bar.
And "system aspects" can be found in build prop, tho can you be more detailled about what you mean by this
Related
Systemless Adblocker
Requirements
Magisk V7 is required to be installed on your device!
Magisk - The Universal Systemless InterfaceFeatures
Adblocker which does not affect system partition
Will be updated frequently (so you got latest blocked websites)
Compatible with latest magisk version (and updatable with Magisk Manager)
Source
Github
Tkkg1994 said:
Systemless Adblocker
Requirements
Magisk V7 is required to be installed on your device!
Magisk - The Universal Systemless InterfaceFeatures
Adblocker which does not affect system partition
Will be updated frequently (so you got latest blocked websites)
Compatible with latest magisk version (and updatable with Magisk Manager)
Source
Github
Click to expand...
Click to collapse
Seems interesting, but no download links ? Should we build it ourselves ?
host files are systemless by default with magisk installed, why not just use adaway?
Modules are now downloaded directly through the magisk manager. Kinda like how xposed installer is
casual_kikoo said:
Seems interesting, but no download links ? Should we build it ourselves ?
Click to expand...
Click to collapse
Waiting for john to add this to his repo system
ibrokemypie said:
host files are systemless by default with magisk installed, why not just use adaway?
Click to expand...
Click to collapse
As far as I know adaway patches system files and no magisk/host file that's why I do this
slothdabski said:
Modules are now downloaded directly through the magisk manager. Kinda like how xposed installer is
Click to expand...
Click to collapse
Exactly, waiting for john to add my adblocker
Magisk mounts the hosts file by default. You can find it in /magisk/.core/hosts. Adaway will then modify this file as it is mounted over the actual /system file.
bumpaneer said:
Magisk mounts the hosts file by default. You can find it in /magisk/.core/hosts. Adaway will then modify this file as it is mounted over the actual /system file.
Click to expand...
Click to collapse
Got it. Will close thread
Sent from my SuperMan powered SM-G930F
The AROMA package in question is this one. I've posted a couple of times in that thread, but it appears the developer has abandoned it, and I'd like to take up repackaging the installer (which modifies /system), into a Magisk module. Has anyone got any idea how I can go about doing it, preferably with 'options' attached, i.e. users can choose which apps/widgets they would like installed.
Scramjet said:
The AROMA package in question is this one. I've posted a couple of times in that thread, but it appears the developer has abandoned it, and I'd like to take up repackaging the installer (which modifies /system), into a Magisk module. Has anyone got any idea how I can go about doing it, preferably with 'options' attached, i.e. users can choose which apps/widgets they would like installed.
Click to expand...
Click to collapse
For me its just impossible to "convert an AROMA Installer into a Magisk Module", Magisk is an "system", AROMA Installer is an custom recovery feature. The first thing is for the android system, the second is for an custom recovery.
The second problem: you cannot implementing an "select menu" in an Magisk module that would managing the Magisk stuff.
Rom said:
For me its just impossible to "convert an AROMA Installer into a Magisk Module", Magisk is an "system", AROMA Installer is an custom recovery feature. The first thing is for the android system, the second is for an custom recovery.
Click to expand...
Click to collapse
What I meant is for the payload in the installer, to be converted into a Magisk module. They both serve a similar purpose: to add/change/replace/remove files from the filesystem. One does it directly, the other, 'systemlessly'.
Rom said:
The second problem: you cannot implementing an "select menu" in an Magisk module that would managing the Magisk stuff.
Click to expand...
Click to collapse
That's OK. What if we know exactly what to select in the Aroma installer, and then create the Magisk module based on just that?
Scramjet said:
What I meant is for the payload in the installer, to be converted into a Magisk module. They both serve a similar purpose: to add/change/replace/remove files from the filesystem. One does it directly, the other, 'systemlessly'.
That's OK. What if we know exactly what to select in the Aroma installer, and then create the Magisk module based on just that?
Click to expand...
Click to collapse
I haven't got more knowledges in that to answer u about your question, maybe another devs could help u..sorry
Scramjet said:
The AROMA package in question is this one. I've posted a couple of times in that thread, but it appears the developer has abandoned it, and I'd like to take up repackaging the installer (which modifies /system), into a Magisk module. Has anyone got any idea how I can go about doing it, preferably with 'options' attached, i.e. users can choose which apps/widgets they would like installed.
Click to expand...
Click to collapse
** shameless advertising
Try this module template
https://forum.xda-developers.com/apps/magisk/module-template-magisk-module-template-t3620235
It can install both in /system and magisk. And I can also guide you with putting options in the installer (in shell)
Scramjet said:
The AROMA package in question is this one. I've posted a couple of times in that thread, but it appears the developer has abandoned it, and I'd like to take up repackaging the installer (which modifies /system), into a Magisk module. Has anyone got any idea how I can go about doing it, preferably with 'options' attached, i.e. users can choose which apps/widgets they would like installed.
Click to expand...
Click to collapse
I have one that works great for me. What I did was remove the installtheme.sh type run _programs from updater_script for all the mods. Instead the "installs" collected in a magisk module. After all was installed that was wanted I had one install that you chose that zipped the magisk template module to the sdcard. After the Aroma finished, in TWRP you hit the back button. Go to install, find that zip and flash it. I used the evilvrtheme magisk template.
It's going to take some time for you, you have to make a module for each option.
One module for HMS_Gallery_GP2 another one for HMS_Music_GP and so on.
Then delete apk from that Aroma Installer and put your modules there. Last step is to modify updater-script to flash relative module for each option instead of extracting apks into /system partition
Here is an exert from my updater-script. The first one is the module zip maker. The other two are examples of the mods bring installed. The second thing being extracted is the magisk config.sh. i have these in separate folders in my Aroma, one for each configuration I have. My default is empty of system installs since my mods are almost entirely vrtheme mods. This is the one sticky area because the wrong config.sh file can cause problems. I only have a few that need system installs. If you default to empty, the worst thing that can happen is the system mod doesn't install. The alternative is a messed up phone.
Scramjet said:
What I meant is for the payload in the installer, to be converted into a Magisk module. They both serve a similar purpose: to add/change/replace/remove files from the filesystem. One does it directly, the other, 'systemlessly'.
That's OK. What if we know exactly what to select in the Aroma installer, and then create the Magisk module based on just that?
Click to expand...
Click to collapse
Did you ever get your Aroma installer going?
Tulsadiver said:
Did you ever get your Aroma installer going?
Click to expand...
Click to collapse
No, I haven't really worked on it yet. Got sidetracked by life—I'm planning on trying to get it to work this weekend, but no promises.
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
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
I'm creating a OneUI 2.0 Rom for some potato phone, and I have Magisk auto-install. I want it so that Magisk already comes with a pre-installed module, which is 2GB ZRAM Enabler. How can I make the module auto-install?
If you already have the Magisk zip in there, getting auto-installed, just add the module zip the same way (after Magisk installs, of course).
Should work in theory, but it depends a bit on the module...