I'm thrilled to know it finally supports Nougat. Thanks rovo89 and all the developers!
Now I have issues installing the zip. I tried to use TWRP to flash the lastest zip (Pixel, 7.1.2, sdk25, arm64), but it kept saying "/system could not be mounted". Here's the log:
https://pastebin.com/89wefwCR
Same problem; Pixel Xl running PureNexus and Magisk 13.3
pixel xl here. xposed could not be installed from recovery, but could be installed from the xposed installer app. I could also be uninstalled from that app. However, uninstall exposed zip could not be flashed, for the same problem - can't mount system. I'm not comfy messing with xposed until uninstall zip works. That uninstall zip has saved me so many times.
I just figured out the way to install Xposed v88 on a Pixel XL phone.
If you have used Xposed on other diveces before, you probably know that the Xposed framework you are about to install is a .zip package , and you may want to use a 3rd-party recovery (like TWRP) to install it, just like you always did with other android phones.
However, the recovery method does not work with Pixel, at least at this time.
This is caused by Pixel's totally different partition plan, known as "A/B system partition"(which means there are two /system partitions). It seems that TWRP can't perfectly support Pixel's A/B partitions. (But why TWRP can install Super SU flawlessly into a Pixel? Anyone have an idea?)
An alternative way is using Flashfire to install .zip packages, and Flashfire supports Pixel's partitions.
So here's my attempt to install Xposed with Flashfire:
root the Pixel by fastboot boot twrp.img and install SuperSU.
reboot and install Flashfire.
copy xposed-v88-sdk25-arm64.zip to Pixel's internal memory. (xposed-v88 could not be the latest version when you are reading this)
run Flashfire, select the zip package, choose Slot A, check Auto-mount and Mount /system read/write
hit FLASH.
after reboot, install Xposed Installer (apk) and you will see Xposed is ready for use.
note: I reset my Pixel by flashing factory image (fash-all.bat) and I'm not using Magisk.
What is the advantage of using flashfire over the method I described above?
my method is:
1) open xposed app
2) hit install
However, if xposed jacks up your phone (not saying that xposed will do that, but I know messing about with it I've had situations with certain modules that wouldn't let me boot into system), you can't flash the "uninstall" zip with flashfire.
That's what's stopping me right now. I know I can always go back to a TWRP nandroid, but sometimes I don't have a zero day backup on hand. I liked the safetynet (pun intended) of always being able to flash uninstall xposed zip from recovery.
KuroCanvas said:
I just figured out the way to install Xposed v88 on a Pixel XL phone.
If you have used Xposed on other diveces before, you probably know that the Xposed framework you are about to install is a .zip package , and you may want to use a 3rd-party recovery (like TWRP) to install it, just like you always did with other android phones.
However, the recovery method does not work with Pixel, at least at this time.
This is caused by Pixel's totally different partition plan, known as "A/B system partition"(which means there are two /system partitions). It seems that TWRP can't perfectly support Pixel's A/B partitions. (But why TWRP can install Super SU flawlessly into a Pixel? Anyone have an idea?)
An alternative way is using Flashfire to install .zip packages, and Flashfire supports Pixel's partitions.
So here's my attempt to install Xposed with Flashfire:
root the Pixel by fastboot boot twrp.img and install SuperSU.
reboot and install Flashfire.
copy xposed-v88-sdk25-arm64.zip to Pixel's internal memory. (xposed-v88 could not be the latest version when you are reading this)
run Flashfire, select the zip package, choose Slot A, check Auto-mount and Mount /system read/write
hit FLASH.
after reboot, install Xposed Installer (apk) and you will see Xposed is ready for use.
note: I reset my Pixel by flashing factory image (fash-all.bat) and I'm not using Magisk.
Click to expand...
Click to collapse
Thanks you guys, I've reported it on Github to rovo, and installed Xposed inside its app. Thanks God it worked.
Issue: https://github.com/rovo89/XposedInstaller/issues/384
I think @KuroCanvas and @mistermojorizin have the right guess.
Worked
The man the man...You are the man
Hi,
Sometimes I have some problems with my devices and want to disable Magisk just to be sure it's not the cause of the problems. My question is - if I uninstall it from Magisk Manager, and then after some time reinstall again will all modules with their configurations remain untouched? If not then is there any way to backup them somehow? Thanks in advance.
As long as you restore the stock boot image and keep the Magisk image intact, you'll have temporarily disabled Magisk and all your modules will still be installed and intact. Just flash the Magisk zip again to enable.
Easiest way to do this should be to use the "Restore Images" option when pressing "Uninstall" in the Manager.
Thank you. will do this that way. When installing again can't I just use "Install" from Magisk Manager?
You can patch your boot image and then flash the patched image manually. You can not install Magisk directly, since that requires superuser access...
Thanks, works like a charm.
Re: Temporarily Disable Magisk & Complete Removal?
Didgeridoohan said:
As long as you restore the stock boot image and keep the Magisk image intact, you'll have temporarily disabled Magisk and all your modules will still be installed and intact. Just flash the Magisk zip again to enable.
Easiest way to do this should be to use the "Restore Images" option when pressing "Uninstall" in the Manager.
Click to expand...
Click to collapse
Thanks! :good:
"...Easiest way to do this should be to use the "Restore Images" option when pressing "Uninstall" in the Manager." - That's what I did on Galaxy S5 SM-G900M (klteub) running Official 16.0 build 2019-03-04 klte + Open GApps ARM 9.0 Pico + Magisk v18.1 to temporarily disable Magisk so I could test an unofficial addonsu alternative.
Note that a manual reboot is required to disable Magisk after using "Restore Images" as the reboot is not automatic like when using Completely uninstall.
I have 2 questions:
I see that the 99-magisk.sh survival script is still in /system/addon.d/ so if I update the firmware would it restore Magisk & re-enable it?
I'm happy with the addonsu so would running the Latest Uninstaller from the Magisk thread completely delete 100% of the files installed by Magisk & the mods it made to the original setup & in /Data?
***
Hi, when i select the restore image option it says "stock backup does not exist" but i have it in root/data...
DISCLAIMER
I am not responsible for any damage to your device during this procedure, you are responsible for any damage (if it occurs) that occurs with your device during the procedure.
Requirements:
Unlocked Bootloader
Rooted Device
TWRP
Magisk Manager
Instructions:
In the stock rom open the Magisk Manager
Enter the Download section in your Magisk Manager
Use the search function and type "Xposed Framework"
Will appear several options choose the one that was only with the name of "Xposed Framework"
Tap the icon next to the module name
And select the option to download (do not click on install because it will not work)
Browse to the location where the Xposed Framework installer was saved on your device
Download and install the Xposed Framework (apk)
TWRP Instructions:
Turn off your device, and enter the TWRP Recovery Mode
Backup your phone! (In case of something wrong, you can recover after)
Go to the Xposed Framework installer and install/flash
Restart your device in the system (do not panic! it may take a while to start)
If all happens well, in the xposed app will be saying that the "Xposed Framework version xx is active."
Sorry for my bad English...
a thank you from time to time help.
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
NONE OF THESE ARE MY WORK, THANK THE DEVELOPERS
YOU NEED ASHYX TWRP - https://forum.xda-developers.com/ga...overy-twrp-3-1-0-1-samsung-galaxy-j3-t3573607
BEFORE STARTING - Some apps like Pokemon Go detect BusyBox apps, Xposed Installer and the Magisk Manager. Enable the general Magisk Hide as well Magisk Hide for the specific app in Magisk Manager. Activate in Magisk Manager 'Repackage Magisk Manager with random package name.'
Then you have to try renaming the package name of the Xposed Installer apk with APK Editor or something else.
STEP 1 - Download the Magisk 18.0 zip and move to External SD Card - http://www.mediafire.com/file/4rmzov...%29.zip/file.
STEP 2 - Install the Xposed Installer app but DO NOT INSTALL IT FROM THE APP, YOU WILL GET SOFT BRICKED - https://forum.xda-developers.com/showthread.php?t=3034811
STEP 3 - Download the generic Samsung Xposed zip and uninstaller by wanam and move to External SD Card - https://forum.xda-developers.com/xposed/unofficial-xposed-samsung-lollipop-t3180960.
STEP 4 - Uninstall Xposed completely if you had it already.
STEP 5 - Unroot in SuperSU. MAKE SURE YOU SELECT 'RESTORE STOCK BOOT IMAGE' OR YOU WILL HAVE TO REFLASH THE BOOT IMAGE FROM ODIN.
STEP 6 - Reboot to TWRP and flash the Magisk zip. Reboot to system and wait a while, make sure everything is working properly.
STEP 7 - Reboot to TWRP and flash the generic Samsung Xposed zip.
STEP 8 - Reboot to system and and wait a while, make sure everything is working properly. Enable in the Xposed Installer 'No Device Check' or download it - https://forum.xda-developers.com/xposed/modules/xposed-device-check-t3199705.
STEP 9 - Install BusyBox and then delete any BusyBox app.
Now you should pass SafetyNet.