This just a quick guide to hopefully make it a little easier for people new to Hide My Applist (often referred to as HMA from hereon in
In the simplest terms it aims to stop one app detecting a list of other installed apps, most notably it can often help stop your say banking app detecting if you have any of the apps it considers harmful on their apps on internal blacklist - like the magisk app, or like one of found the other day, the banking app wouldnt run with Teamviewer installed as it flagged this as riskware. Android 13 was flagged to have this functionality inbuilt, but its early days yet to see whether this is indeed in effect and effectual
-
A ROM with a working Magisk root installation (see links to threads for official Magisk and Magisk Delta below), this means ideally you should have a passing Integrity check (successor to SafetyNet) - currently for most people this requires:
-
Universal SafetyNet Fix Official from kdrag0n from https://github.com/kdrag0n/safetynet-fix or alternately 2.3.1 Mod 2.1 (or better) from Displax https://github.com/Displax/safetynet-fix/releases (depending on which version is later and more effective on your device - if in doubt, try the kdrag0n offical first).
Please Note: At time of writing (6/2/22023 DD/MM/YYYY) Kdrag0n's offical USNF 2.4.0 does have some issues, if you experience any, please use Displax's 2.3.1 Mod 2.1 (or better) instead.
-
If running Magisk official, Shamiko with Enforce Deny List toggled OFF from https://github.com/LSPosed/LSPosed.github.io/releases
-
If running Magisk Delta, check with https://forum.xda-developers.com/t/discussion-magisk-delta-another-unofficial-third-party-magisk-fork.4460555/ for best hiding method
-
A renamed Magisk Manager app - i rename mine App, because im lazy and it puts it at the top of the App list when im adding it to HMA both during setup, and after restoring HMA config after a new ROM flash/factory reset, and HMA install
Please Note: The method used to pass Integrity Check, and for Magisk hiding methods, and therefore referenced modules like Shamiko, may change at any time, so please visit and Watch the following XDA threads
- Universal SafetyNet Fix: https://forum.xda-developers.com/t/magisk-module-universal-safetynet-fix-2-3-1.4217823/
- Magisk - The Age Of Zygisk: https://forum.xda-developers.com/t/discussion-magisk-the-age-of-zygisk.4393877/
- Magisk Delta: https://forum.xda-developers.com/t/discussion-magisk-delta-another-unofficial-third-party-magisk-fork.4460555/
-
Lsposed: https://github.com/LSPosed/LSPosed/releases
Either Zygisk or Riru version depending on your fork of Magisk
For most people on the official Magisk builds, this will be the Zygisk build
For people on the Magisk Delta build by huskydg my current understanding is:
- if you have enabled Zygisk in your Magisk Manager, you should install the Zygisk build
- if you have disabled Zygisk in your Magisk Manager, you should install the Riru build
-
Hide My Applist (a v3 branch apk): https://github.com/Dr-TSNG/Hide-My-Applist/releases
Note #1 (Versions): Its now SAFE to use the downloader in Lsposed Manager to download it (at original time of putting up this guide it was only serving the older v2 builds)
Note #2 (Bootloops): HMA v2 also used a companion magisk module, that if you forgot uninstall when uninstalling HMA itself, would cause a bootloop. HMA v3 DOES NOT require a magisk module to achieve its purpose, so please DO NOT attempt to install HMA v3 over the top of HMA v2, or install the magisk module from HMA v2 separately, in conjunction with HMA v3. If you have HMA v2 installed, please uninstall the HMA v2 magisk module via Magisk Manager, then remove HMA, and reboot, before installing HMA v3
-
Install Lsposed
From your launcher, open your Magisk Manager app (yours is hopefully renamed as mentioned earlier) and switch to the Modules tab (at bottom), then tap Install From Storage at the top of screen.
On the next screen, select the directory where you stored the Lsposed zip, and then tap it
The Lsposed module will now install, and when complete you should tap Reboot to reboot your device
After your device reboots, you will see a prompt to add a shortcut to your launcher, you can manually place it, but i usually just tap Add Automatically, and let it sort it out, for me, as my main launcher screen is full, this overflows onto a second launcher screen...
-
Install HMA
Select the directory where you stored the HMA apk, and install it
After install is complete, you should see a notification in the notification bar, pull down your notification bar and tap the Xposed Module Is Not Activated Yet notification
When the HMA app opens, tap to toggle the Enable Module toggle to On, make sure the ONLY scope that HMA is applied to is System Framework, then tap the gear icon towards bottom right to go to HMA's Settings
-
Configure HMA
When the Settings screen opens, tap on Template Manage
On the next screen tap Create A Blacklist Template
On the following screen, type root into the Template Name box, then tap Edit List, just below and to the right
Selecting root, HMA and lsposed apps...
On the following screen, you'll see a list of all your apps, select the following, by tapping to tick them:
- Magisks renamed (hidden) app - mines always App (because as i said, im lazy and its easy to add)
- HMA - obviously
- Any Xsposed/LSposed apps
When youre done, tap the back navigation key, swipe back or tap the back arrow in top left to return to main HMA screen
-
Configure Apps
From the main HMA Settings menu, tap App Manage
On the following screen, you'll see a list of all your apps, select any which you want to hide root, HMA and any xposed/lsposed modules from, by tapping to tick them
This will normally be:
-
Google Pay/Wallet
-
Banking apps
-
Any "detection" apps (see list in Testing HMA section below for common detection apps)
i.e. Any apps which complain about root or other sensitive app detection are a candidate for adding here.
For each app you add, do the following:
-
Tap the toggle to the right of Enable Hide to enable hiding
-
Under Template Config (toward bottom) tap Using 0 Template
On the popup window that appears:
-
You should now see a screen similar to this for the app you just configured
When youre done, tap back navigation key, swipe back or tap the back arrow in top left to return to app list, and repeat the above few steps for each app you wish to hide root, HMA and any xposed/lsposed modules from
When youre done selecting all apps you wish to hide root, HMA and any xposed/lsposed modules from, tap the back navigation key, swipe back or tap the back arrow in top left to return to main HMA screen
-
-
Finalizing And 1st Boot
Close out from HMA
Reboot your device to activate HMA and the configuration you just setup
After reboot has completed, launch HMA from your launcher
You should show the following screen, showing the status as Activated
Please Note:
- Any time you make a configuration change in HMA, you need to reboot for it to take effect
- It can take several minutes on first boot after being configured, for HMA to take effect. Ive noticed this on several ROM flashes. I would wait a good 5 minutes before testing, or opening any apps you have hidden via HMA after this first initial boot.
Of course you're probably going want to test the apps you primarily installed HMA to assist with, but you can of course test with the following test apps (some of which you may have had installed already and added during the Configure Apps step.
One, Applist Detector, is linked in the main screen of HMA itself, but not installed by default, so on tapping it for the first time, it will prompt you to download it, or you can grab it before hand from https://github.com/Dr-TSNG/ApplistDetector/releases/
The other well known detection tools are:
-
Momo from https://t.me/magiskalpha (TG only...may need to scroll to find)
-
Ruru from https://github.com/byxiaorun/Ruru/releases (Github)
-
Oprek Root Detector from https://play.google.com/store/apps/details?id=com.godevelopers.OprekCek (Google Play Store)
-
TB Checker - SafetyNet & Root from https://play.google.com/store/apps/details?id=krypton.tbsafetychecker (Google Play Store)
-
Security Check - Device Compliance from https://play.google.com/store/apps/details?id=com.hce.compliance.checker (Google Play)
Please Note:
- After adding apps to the root blacklist or other configuration changes, you need to not only reboot to allow the changes to take effect, but also to force close and clear data for any of the above testing apps before testing again.
- The results of the tests are beyond the scope of this guide, and best discussed in the main Magisk threads, not here, as this is merely a guide for HMA, and as such would be the worst place to have your posts seen due to the low volume of traffic. Also please do not PM me about test results, all such PM's will go directly to /dev/null/
-
HMA is still dectected by X detection app:
You may need to activate Vold App Data Isolation - Be aware a couple of people have reported that toggling this on has ended in tears for them, these people though have non-standard setups, using modules and apps which i and most people dont run and wouldnt recommend, and so therefore their experiences may be due to changes they have made to their systemns outside the scope of this guide.
The following issues were highlighted, thanks stillhard
- https://github.com/Dr-TSNG/Hide-My-Applist/issues/253
- https://github.com/Dr-TSNG/Hide-My-Applist/issues/247
Now that youve been warned, should you wish to enable Vold App Data Isolation:
From the HMA home screen:
- Tap Settings (gear icon in bottom right)
- Scroll to Module section
- Tap Data Isolation
- Tap to toggle Vold App Data Isolation to ON
-
Tap the back navigation key, swipe back or tap the back arrow in top left to return to main HMA screen
-
Reboot device
To save recreating the root blacklist template and apps list, you can backup HMA's config and restore it after a clean ROM flash or post factory reset
Backup:
- From the main HMA screen scroll down if need be (due to ad placement) and tap Backup
- Locate where you want to save the HMA_Config.json (prenamed) file and then tap Save
- Copy HMA_Config.json off device for safe keeping
Restore:
- Copy HMA_Config.json onto device if needed
- Run through the setup as above until you reach the main HMA window at the Configure HMA stage
- From the main HMA screen scroll down if need be (due to ad placement) and tap Restore
- Locate where you stored the [B]HMA_Config.json[/B] (prenamed) file and then tap Restore
- If you rename (hide) the Magisk Manager app, and you should, you will need to add the (new) renamed Magisk Manager's app to the root blacklist template after restoring the HMA config:
- From the main HMA screen, tap Manage Template
- Tap root template
- Tap Edit List (the first one) to the right of X Apps Invisible
- Scroll to find your renamed Magisk Managers app and select it
- Tap the back navigation key, swipe back or tap the back arrow in top left to return to main HMA screen
- Close out from HMA
- Reboot your device to activate HMA and the configuration you just restored
Please report any issues you may find with the guide above via the Issues tab