Related
Xposed Framework MIUI7 Android 5.1 ARM64 Edition
The following version works for me with Xiaomi Note Pro (Leo) China Developer ROM as of the 5.12.31 release. All credit to SolarWarez @ 4PDA. I am only sharing what I found. More about Xposed Framework.
Installation Instructions
1. Download the file xposed-v78-sdk22-arm64-MIUI-edition-by-SolarWarez-20151124.zip attached to this post or from the author's repository: https://yadi.sk/d/MvDH_yDGkhP5y/MIUI
MD5 Sum: e20ed3a478f7478f7578471d031ef993
SHA1 Sum: c96a6fe88ae5f83093c6454adf8164edf6f077c4
Note that the repository also has versions for Android 5.0 and regular (32-bit) ARM, and that newer versions might eventually be posted there too.
2. Install ZIP in TWRP recovery or sideload with ADB (Advanced → ADB Sideload and adb sideload <filename>.zip). Get TWRP here if you don't have it yet.
3. Wipe caches, reboot into system and run the Xposed Installer:
adb install XposedInstaller_3.0_alpha4.apk
Note that this is the regular, unmodified version of the installer by rovo89. I am mirroring it here because otherwise there is no official archive of older versions, and a new version in the future might break compatibility with the ported framework.
MD5 Sum: 7ff821c9c916622206862170a4c0c197
SHA1 Sum: 3e84a3895a8c0e812bad85b98e5f176266215fb4
4. Install whatever Xposed modules you wish to use. For example, for MinMinGuard, which I can confirm to be working with this version:
adb install tw.fatminmin.xposed.minminguard_v44_4f4c73.apk
5. Enable the installed modules in the Xposed Settings, and reboot again to activate them.
Disclaimer
Whatever you decide to do with any of these files, you do at your own risk. Note that Xposed problems will generally result in an endless boot loop. Please make sure you are comfortable recovering from whatever might happen before attempting to install it.
Potential Issues
Wiping the cache (a necessary installation step) appears to also reset your lockscreen wallpaper to the default one in MIUI (not the desktop wallpaper though).
To recover from a bootloop due to a failing module, enter the recovery (hold the Volume Up key while booting) and:
adb pull /data/data/de.robv.android.xposed.installer/conf/modules.list
Use your favorite text editor to remove the module responsible for the problem from the list, followed by:
adb push modules.list /data/data/de.robv.android.xposed.installer/conf/
For more serious bootloops, wiping the system partition and installing the ROM again is probably the fastest way to resolve any problem if you don't know how to undo the steps that caused it in the first place.
Update: mirrored a newer version (80) from post #5 below. Thank you for sharing, basten1899! Note: I haven't tried this version myself yet.
Aqq123 said:
Xposed Framework MIUI7 Android 5.1 ARM64 Edition
The following version works for me with Xiaomi Note Pro (Leo) China Developer ROM as of the 5.12.31 release. All credit to SolarWarez @ 4PDA. I am only sharing what I found. More about Xposed Framework.
Installation Instructions
1. Download the file xposed-v78-sdk22-arm64-MIUI-edition-by-SolarWarez-20151124.zip attached to this post or from the author's repository: https://yadi.sk/d/MvDH_yDGkhP5y/MIUI
MD5 Sum: e20ed3a478f7478f7578471d031ef993
SHA1 Sum: c96a6fe88ae5f83093c6454adf8164edf6f077c4
Note that the repository also has versions for Android 5.0 and regular (32-bit) ARM, and that newer versions might eventually be posted there too.
2. Install ZIP in TWRP recovery or sideload with ADB (Advanced → ADB Sideload and adb sideload <filename>.zip). Get TWRP here if you don't have it yet.
3. Wipe caches, reboot into system and run the Xposed Installer:
adb install XposedInstaller_3.0_alpha4.apk
Note that this is the regular, unmodified version of the installer by rovo89. I am mirroring it here because otherwise there is no official archive of older versions, and a new version in the future might break compatibility with the ported framework.
MD5 Sum: 7ff821c9c916622206862170a4c0c197
SHA1 Sum: 3e84a3895a8c0e812bad85b98e5f176266215fb4
4. Install whatever Xposed modules you wish to use. For example, for MinMinGuard, which I can confirm to be working with this version:
adb install tw.fatminmin.xposed.minminguard_v44_4f4c73.apk
5. Enable the installed modules in the Xposed Settings, and reboot again to activate them.
Disclaimer
Whatever you decide to do with any of these files, you do at your own risk. Note that Xposed problems will generally result in an endless boot loop. Please make sure you are comfortable recovering from whatever might happen before attempting to install it.
Potential Issues
Wiping the cache (a necessary installation step) appears to also reset your lockscreen wallpaper to the default one in MIUI (not the desktop wallpaper though).
To recover from a bootloop due to a failing module, enter the recovery (hold the Volume Up key while booting) and:
adb pull /data/data/de.robv.android.xposed.installer/conf/modules.list
Use your favorite text editor to remove the module responsible for the problem from the list, followed by:
adb push modules.list /data/data/de.robv.android.xposed.installer/conf/
For more serious bootloops, wiping the system partition and installing the ROM again is probably the fastest way to resolve any problem if you don't know how to undo the steps that caused it in the first place.
Click to expand...
Click to collapse
can you update v80: xposed-v80-sdk22-arm64-MIUI-edition-by-SolarWarez-20160217.zip? thx a lot
works perfectly
tanks
I've been waiting for xposed v80 too. Newest flat style colored bar can't run on outdated xposed.
padely said:
I've been waiting for xposed v80 too. Newest flat style colored bar can't run on outdated xposed.
Click to expand...
Click to collapse
SolarWarez shared here : http://yun.baidu.com/s/1eRv58cE#dir/path=%2FXposed%2Fv80%2FMIUI
basten1899 said:
can you update v80: xposed-v80-sdk22-arm64-MIUI-edition-by-SolarWarez-20160217.zip? thx a lot
Click to expand...
Click to collapse
Done, thanks!
Newest versions of Xposed for MIUI are
posted on XDA by SolarWarez in this thread.
Universal Systemless Installer for Xposed Framework
>> disclaimer: imagine the most horrible possible outcome and multiply it by 6
(did you get the Megamind joke ?) , you have been warned though <<
what is this ?
basically its an on-the-fly systemless converter/installer for xposed framework
the beauty is that you can install the latest releases of Xposed Framework: systemless
install it from twrp like any other zip
queu your rom with supersu and this zip
it will automatically detect the needed framework (which you still have to download)
versions:
xposed-usi-v0.1l (8bce9f8)
- revised bootdetection properly
- revised file attribute detection completely
- revised loopback options
- updated mount script
- added multiarch archive check (arm/arm64/x86/x64/mips/mips64)
xposed-usi-v0.1k (3f236e6)
- revised imgsize
- revised unpack method
- revised mount script and init.rc
xposed-usi-v0.1j (b96ab4c)
- revised mount options, removed comma for compatibility busybox,toolbox and toybox
- added diskfree check for /tmp
- revised paths and librarypaths properly
- rollback aapt search
- fixed chown problem for toolbox
xposed-usi-v0.1i (5ff57eb)
- removed awk for compatibility whether busybox,toolbox and toybox
- fixed search for paths with spaces
- revised librarypath
- added aapt check, if not found, apkname defaults to filename (omnirom)
- removed incorrect 64-bit patch check
- revised mount process and cleanup
xposed-usi-v0.1h (75403d1)
- revised imgsize detection, revised imgbuild (reduced by 30%)
- added sanity checks throughout the script
- boot.img backup to /data or /cache, with md5sum and origin
- removed some obsolete loops, added log optimizations
- added 1mb imgsize buffer for inline patching
xposed-usi-v0.1g - Changed imgsize detection, fixed ui_print, some minor bugs and typo's (124184f)
xposed-usi-v0.1f - Changed abi detection, fixed apk install for /cache (ac0e0f0)
xposed-usi-v0.1e - Changed bootpartition detection (997e0af)
xposed-usi-v0.1d - Some bug fixes (edf3c9b)
xposed-usi-v0.1c - MIUI / TouchWiz support (untested) (89d44b6)
xposed-usi-v0.1b - first public beta (c1f9fb7)
xposed-usi-v0.1a - non-public release
features:
universal: works on all devices xposed is written for (auto-detect cpu and sdk)
futureproof: compatible with any future versions of xposed-framework ( v87+ )
trustability: installs and patches the official xposed-framework zipfiles
compatible: also works with any unofficial release although not tested
secure: xposed.img is mounted read-only
small: smallest possible footprint for xposed.img
requirements:
twrp (tested with 3.0+)
supersu (tested with 2.65+)
urls/credits
rovo89 - xposed framework
chainfire - systemless idea & tools
topjohnwu - systemless xposed idea
dvdandroid - xposed-installer
romracer - systemless xposed
gh2923 - arm64 tester (awesome guy :good
HypoTurtle - proof of concept for supersu image/su.d
FAQ
why did you write it?
i thought i could do a better job, you decide
is it safe?
backup your device, in case the installation fails just restore your boot partition
its the first release and beta, make no assumptions,
how to install ?
>>> WARNING: it will overwrite /data/xposed.img without prompt! <<<
download supersu by chainfire
download the xposed-usi-v*.zip (download link below)
download the proper xposed-v*-sdk*-*.zip version for your device
and place it alongside or in a subfolder (auto-detect)
Official Xposed Framework
Xposed for Samsung/TouchWiz
Xposed for MIUI
download one of the installers below
Xposed Installer by dvdandroid or
Xposed Installer by romracer
and place it alongside or in a subfolder (auto-detect)
queue and install supersu 2.65+ followed by xposed-usi-v*.zip
(already on supersu?, just install the xposed-usi-v*.zip)
reboot
how do i know what version of xposed i need ?
run the xposed installer by dvdandroid
or run the xposed-usi-*.zip
both will show which version you need
bugs/problems:
probably, i only have one device
donate:
bitcoin address: 1HPRug5MFDp2eA3rr4kDEhV1gEguinRnpQ
download: (latest version is at the bottom of the list)
saved for future reference
Customized Frameworks and Installers
(supported from 0.1c and above)
Do you want your custom Xposed Framework supported ? Follow these rules:
installer searches for: "xposed-v*-sdkAPI-ARCH-*.zip"
API = 21, 22, 23 ... etc
ARCH = arm, arm64, x86, x64, mips, mips64 (case insensitive)
zipfile must contain "/system" folder with the xposed system files.
Do you want your custom Xposed Installer App supported ? Follow these rules:
installer searches for: "*xposed*installer*.apk" (case insensitive)
I'l try and give report
Minions_Army said:
I'l try and give report
Click to expand...
Click to collapse
Thanks mate, appreciate it
st0rm77 said:
Thanks mate, appreciate it
Click to expand...
Click to collapse
Failed on xperia m running rr 569 lp
Edit
My fault
I'm not install xposed framework official before
Test again
On my hammerhead nexus 5
Failed too
Minions_Army said:
Failed on xperia m running rr 569 lp
Edit
My fault
I'm not install xposed framework official before
Test again
Click to expand...
Click to collapse
I changed the bootpartition detection, tested it and it should run now.
Updated to xposed-usi-v0.1.e
BTW: the recovery.log file is now copied after the installation and can be found in same directory as the ZIP file, with the same name.log (xposed-usi-v0.1e.zip.log) just to make things easy.
st0rm77 said:
I changed the bootpartition detection, tested it and it should run now.
Updated to xposed-usi-v0.1.e
BTW: the recovery.log file is now copied after the installation and can be found in same directory as the ZIP file, with the same name.log (xposed-usi-v0.1e.zip.log) just to make things easy.
Click to expand...
Click to collapse
I'll try latest build
Might want to try the latest version.
@everyone: i need some more testers, so if you're up for it, post away.
I need to wait more feed backs before installing this one. Sdk22 user here anyway
MrBrowseGierza said:
I need to wait more feed backs before installing this one. Sdk22 user here anyway
Click to expand...
Click to collapse
Updated version to >> 0.1h <<
It works flawlessly on my own device, so try it out and if you run into problems let me know.
First time the folder name contains a space, it just says error.
After I rename the folder, it still failed, and the log is as follows:
Code:
I:operation_start: 'Flashing'
正在安装刷机包 '/sdcard/1/SystemlessXposed_by_st0rm77/xposed-usi-v0.1h.zip'
检查 MD5 文件…
跳过 MD5 校验：无法找到 MD5 文件
I:Zip does not contain SELinux file_contexts file in its root.
I:Legacy property environment initialized.
******************************
Universal Systemless Installer
for Xposed Framework
ver: 0.1h
written by: st0rm
Licensed under: GPL v2
******************************
- Mounting /system(ro), /data, /cache
- Setting library path: /system/lib64
- Cpu architecture: arm64-v8a/arm64, sdk23
*************
Image builder
*************
- UnZipping into TMPDIR: /tmp/30499
Archive: /sdcard/1/SystemlessXposed_by_st0rm77/xposed-usi-v0.1h.zip
inflating: /tmp/30499/arm64-v8a/sukernel
creating: /tmp/30499/common/
creating: /tmp/30499/common/ramdisk/
inflating: /tmp/30499/common/ramdisk/init.xposed.rc
creating: /tmp/30499/common/ramdisk/sbin/
inflating: /tmp/30499/common/ramdisk/sbin/mount_xposed.sh
/tmp/updater[176]: awk: not found
! Failed: /sdcard/1/SystemlessXposed_by_st0rm77/xposed-v86-sdk23-arm64.zip is corrupt
***********
Cleaning up
***********
- Unsetting library path
- Unmounting
- Removing TMPDIR: /tmp/30499
I checked the xposed-v86-sdk23-arm64.zip, the md5sum it is just the same as the official. Then I down a new one, but it still failed.
I'm using Oneplus 3, TWRP 3.0.2-0.
Sorry for my poor English...
gh2923 said:
First time the folder name contains a space, it just says error.
After I rename the folder, it still failed, and the log is as follows:
Code:
I:operation_start: 'Flashing'
正在安装刷机包 '/sdcard/1/SystemlessXposed_by_st0rm77/xposed-usi-v0.1h.zip'
检查 MD5 文件…
跳过 MD5 校验：无法找到 MD5 文件
I:Zip does not contain SELinux file_contexts file in its root.
I:Legacy property environment initialized.
******************************
Universal Systemless Installer
for Xposed Framework
ver: 0.1h
written by: st0rm
Licensed under: GPL v2
******************************
- Mounting /system(ro), /data, /cache
- Setting library path: /system/lib64
- Cpu architecture: arm64-v8a/arm64, sdk23
*************
Image builder
*************
- UnZipping into TMPDIR: /tmp/30499
Archive: /sdcard/1/SystemlessXposed_by_st0rm77/xposed-usi-v0.1h.zip
inflating: /tmp/30499/arm64-v8a/sukernel
creating: /tmp/30499/common/
creating: /tmp/30499/common/ramdisk/
inflating: /tmp/30499/common/ramdisk/init.xposed.rc
creating: /tmp/30499/common/ramdisk/sbin/
inflating: /tmp/30499/common/ramdisk/sbin/mount_xposed.sh
[SIZE="5"]/tmp/updater[176]: awk: not found[/SIZE]
! Failed: /sdcard/1/SystemlessXposed_by_st0rm77/xposed-v86-sdk23-arm64.zip is corrupt
***********
Cleaning up
***********
- Unsetting library path
- Unmounting
- Removing TMPDIR: /tmp/30499
I checked the xposed-v86-sdk23-arm64.zip, the md5sum it is just the same as the official. Then I down a new one, but it still failed.
I'm using Oneplus 3, TWRP 3.0.2-0.
Sorry for my poor English...
Click to expand...
Click to collapse
Poor English is better than 'No English'
There isnt a problem with your files, >> awk is missing << and the script does a check for you to make sure the zip file isnt broken. (contains files)
No awk, no correct check it seems, i will work something out for you.
Please download en run tool-test zip file, post logfile as attachment
st0rm77 said:
Poor English is better than 'No English'
There isnt a problem with your files, >> awk is missing << and the script does a check for you to make sure the zip file isnt broken. (contains files)
No awk, no correct check it seems, i will work something out for you.
Please download en run tool-test zip file, post logfile as attachment
Click to expand...
Click to collapse
That is to say, some busybox command not support?
st0rm77 said:
Updated version to >> 0.1h <<
It works flawlessly on my own device, so try it out and if you run into problems let me know.
Click to expand...
Click to collapse
Thanks, work perfectly fine on my LG G3 dual SIM D856.
MrBrowseGierza said:
Thanks, work perfectly fine on my LG G3 dual SIM D856.
Click to expand...
Click to collapse
And we have a winner
Thanks for posting the result mate :good:
I want to test. I have an htc m10. I have Xposed v85. I just tried v86 and im having lots of problems. Im not to good with this stuff so im not sure how to install it. Im going to do a fresh install of rom and Xposed. I have you're file, Xposed v85, and my rom ready to go. After I flash my rom, boot and restore my apps. Then? Im not sure what to do with you're file and the Xposed v85 file. Do I flash them both?
Sent from my 2PS64 using XDA-Developers mobile app
gh2923 said:
That is to say, some busybox command not support?
Click to expand...
Click to collapse
Well it seems you have no busybox in /sbin at all instead i found toolbox,
which is limited and does not have awk.
So i have to work around this somehow. I would hate to include a complete installation of busybox for all architectures.
Im working on a solution.
l1ttl3z said:
I want to test. I have an htc m10. I have Xposed v85. I just tried v86 and im having lots of problems. Im not to good with this stuff so im not sure how to install it. Im going to do a fresh install of rom and Xposed. I have you're file, Xposed v85, and my rom ready to go. After I flash my rom, boot and restore my apps. Then? Im not sure what to do with you're file and the Xposed v85 file. Do I flash them both?
Sent from my 2PS64 using XDA-Developers mobile app
Click to expand...
Click to collapse
Did you read the how to install from the first post ?
Download your rom
Download supersu (see 1st post)
Download xposed-usi- latest version (see 1st post)
Download xposed version you want (85 in your case)
Download xposed-installer-apk (see 1st post)
Put only these files in a new folder
folder/yourrom.zip
folder/supersu*.zip
folder/xposed-usi-*.zip
folder/xposed-v85-*.zip
folder/xposed-installer*.apk
Start TWRP and navigate to your folder
Select your yourrom.zip and press "Add more Zips"
Select your supersu*.zip and press "Add more Zips"
Select --> xposed-usi-*.zip and "Swipe to install"
And that should do it
st0rm77 said:
Well it seems you have no busybox in /sbin at all instead i found toolbox,
which is limited and does not have awk.
So i have to work around this somehow. I would hate to include a complete installation of busybox for all architectures.
Im working on a solution.
Click to expand...
Click to collapse
I'm using H2OS, maybe it just delete many things...
Perhaps I should first flash a systemless busybox?
Like this one:
http://forum.xda-developers.com/android/software-hacking/tool-busybox-flashable-archs-t3348543
It's 0:40am, sorry but I have to go to sleep
NETWORK FIX
from mobspyguy and all owners that install [8.1.0] Resurrection Remix 6.0.0 and got network error
ORIGINAL LINK
link to original post
https://forum.xda-developers.com/note-4/snapdragon-dev/rom-resurrection-remix-6-0-0-t3768963
NETWORK FIX
Download RR OREO ROM
First install RR-O-v6.0.0-20180410-trlte-Official.zip
https://androidfilehost.com/?fid=746010030569968068
after setup go back into recovery and dirty flash
RR-O-v6.0.0-20180425-trlte-Official.zip
https://androidfilehost.com/?fid=746010030569971088
after install u will have latest oreo RR rom with network
FINISHED
NOW IF YOU WISH TO CONTINUE WITH ROOTING AND XPOSED YOU CAN CONTINUE
INSTALLING MAGISK
Download
Latest Magisk Manager
https://github.com/topjohnwu/MagiskManager/releases/download/v5.7.0/MagiskManager-v5.7.0.apk
install on phone after reboot into recovery
Flash Latest Magisk
https://github.com/topjohnwu/Magisk/releases/download/v16.0/Magisk-v16.0.zip
restart into rom phone root
INSTALLING XPOSED INSTALLER
https://dl-xda.xposed.info/modules/de.robv.android.xposed.installer_v33_36570c.apk
after installing locate your android version
SDK 21: Android 5.0 | SDK 22: Android 5.1 | SDK 23: Android 6.0 | SDK 24: Android 7.0 | SDK 25: Android 7.1 | SDK 26: Android 8.0 | SDK 27: Android 8.1
in our case we are using SDK 27 as is android 8.1
https://forum.xda-developers.com/xposed/unofficial-systemless-xposed-t3388268
boot into recovery and
install this sdk
https://forum.xda-developers.com/attachment.php?attachmentid=4493762&d=1525539009
Is Netflix working with this my man?
I have installed Xposed Framework v89 [SDK23_arm64_v89.0_2017.12.17] on my Sony Xperia E5803 Z5 Compact [MM 6.0.1] but it is not active. See attached “Xposed error log 2018.07.11, 09.21 AM.log”.
Code:
Could not load libxposed: dlopen failed: cannot locate symbol
"_ZN3art6mirror6Object5CloneEPNS_6ThreadEPNS0_5ClassE" referenced by
"/system/lib/libxposed_art.so"...
Any help will be appreciated. :fingers-crossed:
Device: E5803 (Sony Xperia Z5 Compact)
Android version 6.0.1 (SDK 23)
ROM: 32.2.A.5.11 [E5803_Customized US_1298-3109_32.2.A.5.11_R4C]
Build fingerprint: Sony/E5803/E5803:6.0.1/32.2.A.5.11/3656371468
Platform: arm64-v8a, 64-bit binary
Xposed Installer: v 3.1.5 (was v3.0.1 by dvdandroid 26/11/16)
Xposed Framework: version 87 (SDK23_v87_2016.11.24, the modules were working fine)
TWRP: v3.0.2-0
Attached:
Xposed error log 2018.07.11, 09.21 AM.log
I read Xposed won’t work after March security patch. However this is not applicable to me since I have blocked every type of patch/update, at least I think I have.
I had a perfectly working Xposed Framework v87 (SDK23_v87_2016.11.24), the modules were working fine. Then I installed v89 OTA, couldn’t get it to become active.
So I booted into TWRP recovery and flashed the uninstaller “xposed-uninstaller-20180117-arm64.zip”
I wiped the Dalvik cache and tapped Reboot, "Android is starting... Optimizing app 148 of 355." (This took 23 minutes).
I booted normally, then I rebooted into TWRP recovery and flashed zip Xposed Framework v89 [SDK23_arm64_v89.0_2017.12.17]
Same error after booting into the system “Xposed v89 is installed but not active”
Update:
I disabled (unchecked) modules MinMin Guard and Neo Power menu. Did not make any difference on reboot. Same error
I have almost the same experience with you. I have been looking for solutions for the past three days, but I still have no results.
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