Database Develop

LG V20 - Magisk && Magisk Hide

LG V20
Model: US996
ROM: Weta
Kernel: Stock
Many others on the LG V20 have managed to get magisk working on their device, sometimes by using other kernels and forcing uninstalls of conflicting packages. However, none of this has worked on the US996 model. I was hoping the beta might resolve some of these issues but it has not; and has actually caused another one.
Beforehand, even without MagiskSU I was still able to use MagiskHide (for snapchat) but recently I've completely lost the option of MagiskHide on the latest MagiskManager. Usually you can enable the service via the settings but its no-longer there.
Why is MagiskHide gone? How can I help get MagiskSU on my model? Thank you.
I apologize if I have missed some relevant information to this topic.

guys pls im gonna lose my snapchat streaks if i cant get magisk hide working,,

nothing?

Try to use Universal SafetyNet Fix v2 beta 3 module for Magisk v12, you can find it in this forum, is always in the first page
Remember to install F-Droid Privileged module, just in case.

Logs are always a good idea (Magisk log, etc). Also, I'd try running this in terminal:
Code:
su
magiskhide --disable
magiskhide --enable

Didgeridoohan said:
Logs are always a good idea (Magisk log, etc). Also, I'd try running this in terminal:
Click to expand...
Click to collapse
Thank you sir! I've tried all the normal "fixes" and it wasn't until I opened terminal and STARTED magiskhide (wasn't enabled at all)

magiskhide wasnt found as a valid command

Ceruleancerise said:
magiskhide wasnt found as a valid command
Click to expand...
Click to collapse
And you're on the beta? If so you've got serious issues with your installation and it's no wonder things aren't working. And I'm still not seeing any logs...

will provide logs later today, sorry for slow replies

Hi I'm running stock kernel and weta rom on the vs996 model of the v20 does magisk support second screen and does it fix the staic screen on my model?

Cant find Enable Busybox in Magisk settings and ctsProfile not succesfull

Hello.
After many many reinstall of magisk I still cant find "Enable Busybox" in Magisk settings
I have "magisk core only mod" , "Magisk Hide" and "Systemless Host" BUT "Enable Busybox" is missing/not visible in my settings of Magisk.
I also got error when Safety Net check. Only bacisintegry is successfull. ctsProfile do not pass the test.
But, I can still download and update payed and free apps from Google Play Store.
Anyone what to do for getting "Enable Busybox" to be visible in my Magisk settings?
And, since ctsProfile not pass safetyscheck..can that be because for that missing "Enable Busybox" in settings?
Running lineageOS 14.1 and samsung J5 ( 2016 ) , SM-J510FN
Magisk 14.0
Regards
Rolf

Busybox: There is no toggle like that (hasn't been for some time). There's a Busybox module in the Downloads section of the Manager. Use that.
The failed ctsProfile check doesn't have anything to do with Busybox. Take a look here for more info on passing SafetyNet: https://forum.xda-developers.com/apps/magisk/guide-magisk-troubleshooting-t3641417
You don't need to pass SafetyNet to be able to download and install most apps. There are a few who use the Certified status in the Play store (Netflix) and some that won't function if you don't pass SafetyNet (Android Pay).

Didgeridoohan said:
Busybox: There is no toggle like that (hasn't been for some time). There's a Busybox module in the Downloads section of the Manager. Use that.
The failed ctsProfile check doesn't have anything to do with Busybox. Take a look here for more info on passing SafetyNet: https://forum.xda-developers.com/apps/magisk/guide-magisk-troubleshooting-t3641417
You don't need to pass SafetyNet to be able to download and install most apps. There are a few who use the Certified status in the Play store (Netflix) and some that won't function if you don't pass SafetyNet (Android Pay).
Click to expand...
Click to collapse
Thanks for responding and a celearly anwer Didgeridoohan
I will check that link about safetynet. Thanks
Anyway, I guess there are no point/neccesary installing Busybox module in Magisk when I already have Bysybox Pro installed on my device?
I have noticed that my Netflix will not load so hope I got that safetyNet up running in Magisk.
Regards
Rolf

[email protected] said:
Thanks for responding and a celearly anwer Didgeridoohan
I will check that link about safetynet. Thanks
Anyway, I guess there are no point/neccesary installing Busybox module in Magisk when I already have Bysybox Pro installed on my device?
I have noticed that my Netflix will not load so hope I got that safetyNet up running in Magisk.
Regards
Rolf
Click to expand...
Click to collapse
SafetyNet Fixed by doing this:
https://forum.xda-developers.com/apps/magisk/xiaomi-safetynet-fix-t3600431
BUT, still Netflix Error/not compatibel vs my device when download from Google Play. Got a message in that error message downloading Netflik from Netflix's site. Doing that..and Netflix up running
Thanks again Didgeridoohan for pointing me in the right direction
Regards
Rolf

I thought with the newest version of magisk, busy box is integrated already? I ran a test and it states I have it and it's active but certain apks tell me it's not present in device when installing. Should I setup module in magisk also? Don't want to double stack anything.

SlimPickens89 said:
I thought with the newest version of magisk, busy box is integrated already? I ran a test and it states I have it and it's active but certain apks tell me it's not present in device when installing. Should I setup module in magisk also? Don't want to double stack anything.
Click to expand...
Click to collapse
There is a busybox integrated into Magisk, for use by Magisk...
If you wan't busybox for the rest of your system, install the busybox module from the Magisk repo.

Didgeridoohan;73790549There's a Busybox module in the Downloads section of the Manager. Use that.
The failed ctsProfile check doesn't have anything to do with Busybox. Take a look here for more info on passing SafetyNet: [url said:
https://forum.xda-developers.com/apps/magisk/guide-magisk-troubleshooting-t3641417[/url]
You don't need to pass SafetyNet to be able to download and install most apps. There are a few who use the Certified status in the Play store (Netflix) and some that won't function if you don't pass SafetyNet (Android Pay).
Click to expand...
Click to collapse
Actually, in my case, the ctsProfile check does correlate with the busybox module. I am trying a new ROM on my galaxy s7 which doesn't contain a busybox, thus Viper4Android does not want to install its driver (and Busybox checker says "no"). ctsProfile did pass. After I downloaded the BusyBox module in Magisk Manager, cts doesn't pass, but basic integrity still does.

Peter.1997 said:
Actually, in my case, the ctsProfile check does correlate with the busybox module. I am trying a new ROM on my galaxy s7 which doesn't contain a busybox, thus Viper4Android does not want to install its driver (and Busybox checker says "no"). ctsProfile did pass. After I downloaded the BusyBox module in Magisk Manager, cts doesn't pass, but basic integrity still does.
Click to expand...
Click to collapse
If you only need busybox for Viper4Android, try the awesome ViPER4Android FX module (available in the Magisk repo). It doesn't need busybox...

Yup, only vor Viper. I already installed this module (and also the seperate one for Magisk 14.0+), but the Viper app always wants to install the driver on its own again..

Peter.1997 said:
Yup, only vor Viper. I already installed this module (and also the seperate one for Magisk 14.0+), but the Viper app always wants to install the driver on its own again..
Click to expand...
Click to collapse
Judging from your two posts, I'd say something's wrong with your Magisk installation... Magisk log and magisk_debug.log (from /data) might show something interesting.

Jumping onto that thread as it seems to fit quite well.
If a Moderator feels the need for a new topic pls let me know.
Facts:
Android 6 with Magisk 12 and SuperSu 2.79/2.82 and Xposed 87 running fine for quite a time.
Only Magisk manager was updated inbetween a few times
Now with a few free days after christmas and all the new releases out, i went for an update session.
- cleaned supersu with 0smosis unSu
- TWRP flashed clean stock boot.img
- TWRP flashed Magisk 15.1. All good and seemed to work
Then i wanted to update to xposed v89.
The installer failed with "updater process ended with error 1"
Dug into the TWRP-Logs and found the following:
Code:
/tmp/updater: line 91: /data/adb/magisk/busybox: not found
! Unable to extract zip file!
Now it was time to inspect the Magisk-Log:
Code:
12-29 23:56:59.699 269 269 I Magisk : * Setting up internal busybox
12-29 23:56:59.700 273 273 E Magisk : execvpe failed with 2: No such file or directory
Interesting.
As i knew about the changes from 12->15 regarding internal busybox, i cleaned the Magisk Manager Cache as recommended somewhere
and wanted to go for the official module "Busybox for Android NDK 1.27.2".
After installing it showed up as "not available - please reboot"
I went for the logs again and found the following:
Code:
Installing Busybox_for_Android_NDK-1.27.2.zip
Busybox Installer Script by osm0sis @ xda-developers
Mounting...
Extracting files...
update-binary[109]: unzip: not found
Also a quick check of /data/magisk showed no signs of busybox.
Any hints where to dig deeper to get busybox (and unzipping in TWRP back ??
Time, a few Skills and Tools available.
Didnt attach the logs, cause those above are imho the only relevant facts.
If somebody needs sth specific to rule sth out, i will of course happily deliver them.
Thank everybody and keep up the good work !!

Sebastl said:
Jumping onto that thread as it seems to fit quite well.
If a Moderator feels the need for a new topic pls let me know.
Facts:
Android 6 with Magisk 12 and SuperSu 2.79/2.82 and Xposed 87 running fine for quite a time.
Only Magisk manager was updated inbetween a few times
Now with a few free days after christmas and all the new releases out, i went for an update session.
- cleaned supersu with 0smosis unSu
- TWRP flashed clean stock boot.img
- TWRP flashed Magisk 15.1. All good and seemed to work
Then i wanted to update to xposed v89.
The installer failed with "updater process ended with error 1"
Dug into the TWRP-Logs and found the following:
Code:
/tmp/updater: line 91: /data/adb/magisk/busybox: not found
! Unable to extract zip file!
Now it was time to inspect the Magisk-Log:
Code:
12-29 23:56:59.699 269 269 I Magisk : * Setting up internal busybox
12-29 23:56:59.700 273 273 E Magisk : execvpe failed with 2: No such file or directory
Interesting.
As i knew about the changes from 12->15 regarding internal busybox, i cleaned the Magisk Manager Cache as recommended somewhere
and wanted to go for the official module "Busybox for Android NDK 1.27.2".
After installing it showed up as "not available - please reboot"
I went for the logs again and found the following:
Code:
Installing Busybox_for_Android_NDK-1.27.2.zip
Busybox Installer Script by osm0sis @ xda-developers
Mounting...
Extracting files...
update-binary[109]: unzip: not found
Also a quick check of /data/magisk showed no signs of busybox.
Any hints where to dig deeper to get busybox (and unzipping in TWRP back ??
Time, a few Skills and Tools available.
Didnt attach the logs, cause those above are imho the only relevant facts.
If somebody needs sth specific to rule sth out, i will of course happily deliver them.
Thank everybody and keep up the good work !!
Click to expand...
Click to collapse
Sounds like your TWRP isn't up to the job... It's probably too old (info which would have been in the log ) or otherwise missing some features...
Updating TWRP or letting the Manager patch a boot image that you then flash manually are two possible solutions.

Thank you very much for the quick reply Didgeridoohan.
That is of course water on the mills of the "always include logs" - people. Apparently for a reason
TWRP Version is/was 3.02.
After you suggested patching the image from Magisk Manager, i tried that and got a quick and dirty "Failed".
But i realized that now the option "Direct Install (recommended)" was available.
It wasnt when i did the initial setup.
As i had nothing to loose, i tried that to reinstall and after the next reboot -
Bingo! Now the busybox binary is/was available and therefore the Busybox Module and consequently also Xposed respective everything which depends on unzipping/busybox works.
Strange - but somehow problem solved.
I didnt see anything in the TWRP changelogs from 3.02 up to 3.2.1 - but hey...
Hope that helps someone.
Greetings and a nice 2018 !

Magisk is consistently causing my Settings app to hang after booting

I have no proof of this, but this has been happening on my Note 4 (SM-N910T) ever since v13.3, and now on v14.0. I also bought a Huawei Honor 6X about a week ago, it's now happening there too. I didn't feel that this was worth posting about, figuring it might be device-specific or ROM-specific. But now that it's happening on 2 devices I've changed my mind.
Note 4:
Android 7.1.2 (CMRemix)
Xposed unofficial by PurifyOS (system mode)
Kernel sets SELinux to permissive on boot
Magisk v14.0
No Magisk modules installed
Honor 6X:
Android 7.1.2 (Resurrection Remix)
Xposed (systemless Magisk version)
Kernel sets SELinux to permissive on boot
Magisk v14.0
No Magisk modules installed
Description of the issue:
After powering on/rebooting, I can't open system Settings app for up to a minute or so. It just hangs on a white screen. It then either gives a message stating that Settings isn't responding, or, if I manually close Settings with the Recent button then try to reopen it, it repeats the same behavior but will eventually open. Sometimes I need to access Settings immediately after boot to make changes. Device is otherwise responsive, Magisk appears to work fine.
I have tried clean ROM installs on both devices, with full wipes beforehand, and latest stable Magisk. I've also tried with and without Xposed, results are the same. This didn't happen before v13.3, v11.x and v12.x didn't exhibit this behavior. But back this I was using systemless SuperSU in conjunction with Magisk. I suspect that MagiskSU may be the culprit.
MagiskSU is also noticeably slower (when compared to SuperSU or non-Magisk Phh's Superuser) at responding to SU requests, even with a setting of auto-grant and the lowest possible timeout (10 seconds), and global mount namespace. This may be due to the fact that does more than just rooting, it is logical to assume that it has more background processes running since it is also a systemless framework, whereas the other 2 solutions only manage root access.
Last, my file managers oftentimes won't let me delete/modify certain files/folders in the system partition, with a message like "device or resource busy", or flat-out denying access. System is remounted as RW. This only happens with Magisk, but never with SuperSU or Phh. I do use Magisk for systemless mods, but sometimes I want to make direct midifications to /system. Magisk, as a root solution, shouldn't be denying my ability to do this, since I own my devices, not Magisk.
Right now I'm primarily concerned with the Settings issue, but I figured the other issues are worth mentioning. I'm still on the fence, I may return to SuperSU, or Phh, trying Magisk again after a few more stable releases. But if this can be resolved then I'll give it another chance.
I'm posting the logs for my Honor 6X, one is the Magisk log from /cache, the other is /data/anr/traces.txt. Attempts to get a logcat during boot were unsuccessful.
Thanks for any help!

Magisk saves a log during boot that you might find useful. It's /data/magisk_debug.log. A logcat from when the device has booted up and you're trying to open up the Settings might also be interesting.
Have you tried on a stock ROM? Both those ROMs you're using are related and may have similar ROM specific issues...

dont open setting immediately after reboot. open it after a minute. not really a problem

It is not Magisk problem that cause this problem but it is the rom...i'm also using RR 7.1.2 on bacon and Magisk v14 and have no problem at all but we bacon user does encountered this problem in RR build in July and the devs fixed this on August build....
Sent from my A0001 using Tapatalk

@all: I've been super busy lately, not much time to post anywhere. But getting back to this.....I doubt this is a ROM issue. My reasoning is that it would occur with or without Magisk if that were the case. I don't get this issue when using SuperSU or non-Magisk Phh Superuser (regular). This only occurs when Magisk is installed, since v13.3, but not before that version. It has also occurred on Huawei stock EMUI firmware.
@24imelqui: Just because you don't consider something to be a problem doesn't mean it isn't a problem for others. I have a need to be able to access my Settings app immediately after booting. Your comment isn't useful in the least, if you can't post something helpful then don't post at all. /Ignored.....
@iPusak Gaoq™: isn't Bacon a Nexus device (not sure, never owned one)? Can you reference something where this has been reported? And fixed? Like something on XDA or GitHub or whatever? If this can be proven to be ROM issue then I'll post something to my devices' devs to see if it can be fixed in later releases.
I'm attaching several logs, this time a logcat as well. No such debug log exists in /data, and Magisk v14.0 has no options in the Manager app for debug logging.

AnonVendetta said:
@all: I've been super busy lately, not much time to post anywhere. But getting back to this.....I doubt this is a ROM issue. My reasoning is that it would occur with or without Magisk if that were the case. I don't get this issue when using SuperSU or non-Magisk Phh Superuser (regular). This only occurs when Magisk is installed, since v13.3, but not before that version. It has also occurred on Huawei stock EMUI firmware.
@24imelqui: Just because you don't consider something to be a problem doesn't mean it isn't a problem for others. I have a need to be able to access my Settings app immediately after booting. Your comment isn't useful in the least, if you can't post something helpful then don't post at all. /Ignored.....
@iPusak Gaoq™: isn't Bacon a Nexus device (not sure, never owned one)? Can you reference something where this has been reported? And fixed? Like something on XDA or GitHub or whatever? If this can be proven to be ROM issue then I'll post something to my devices' devs to see if it can be fixed in later releases.
I'm attaching several logs, this time a logcat as well. No such debug log exists in /data, and Magisk v14.0 has no options in the Manager app for debug logging.
Click to expand...
Click to collapse
There have been issues previously, where it seems like it's a Magisk thing but it's really a ROM issue. Some things Magisk does (and it does a few more things than just root your device) can sometimes bring problems out into the light...
I believe bacon refers to the OnePlus One (Nexus devices are all named after aquatic creatures). Looking in the RR thread over in those forums I'd guess you'll find your information somewhere around here: https://forum.xda-developers.com/on...tion-remix-t3507102/post73283623#post73283623
About your logs: I'm not too good at reading logcats, so no help from me there. But, I see something there in your Magisk log... Have you tried disabling Xposed?
There are things going on when a device with Magisk starts, so depending on your setup it might take a short while (30-ish seconds for me on my daily driver) before root requests start being accepted. If the ROM settings require root, that might be the reason why it won't open straight away when booting up your device.

OK, back again, Xposed disabled this time in the app (but still installed), so not active.

Here is the full changelog on the build where the devs fixed the issues on settings freeze/fc on startup....
https://forum.xda-developers.com/showthread.php?p=73304715
Sent from my A0001 using Tapatalk

request rejected, no prompt to grant access

heeeeey!
old magisk user, it was working like a charm on my galaxy s20, but lately something broke!
I have installed Magisk version 97b72a59 (20419)
and magisk manager version 8.0.7 (4834)
When I open an app that requires root access, nothing happens, and after a while, i get the toast message that denied superuser rights.
11-16 21:36:12.620 5867 27034 D Magisk : su: request from pid=[27031], client=[9]
11-16 21:36:12.620 5867 27034 D Magisk : su: request from uid=[10452]
11-16 21:36:12.620 5867 27034 D Magisk : magiskdb: query magiskhide=[0]
11-16 21:36:12.620 5867 27034 D Magisk : magiskdb: query su_fingerprint=[0]
11-16 21:36:20.462 5867 25942 W Magisk : su: request rejected (10452)
11-16 21:36:20.462 5867 25942 E Magisk : write failed with 32: Broken pipe
Click to expand...
Click to collapse
i have seen that it happens a lot, but there isn't any solution on these threads!
any suggestions?
thank you in advance for your help!

Go to magisk manager and manually grant root permission to that app in question

miravision said:
Go to magisk manager and manually grant root permission to that app in question
Click to expand...
Click to collapse
thank you for your reply!
on this page, on magisk manager app, I get the message "no app has asked for superuser permission yet"!

Install root checker app and check if it prompts you for root access, else magisk is configured to always reject root access in magisk settings

miravision said:
Install root checker app and check if it prompts you for root access, else magisk is configured to always reject root access in magisk settings
Click to expand...
Click to collapse
As expected, root checker app reports "Sorry! Root access is not properly installed on this device."
On magisk manager settings, i have set "automatic response" to "grant" instead of "prompt" but nothing changed.
any other options?

Unroot and reinstall latest magisk

miravision said:
Unroot and reinstall latest magisk
Click to expand...
Click to collapse
that's my last resort.
I am trying to repair it, rather than uninstalling and installing it again...

@sakis_the_fraud You see that broken pipe in your log? That suggests you're seeing an issue that was present in builds around v21 and fixed in v21.4.
I suggest you update to a more recent Magisk release instead of trying to troubleshoot further...

Didgeridoohan said:
@sakis_the_fraud You see that broken pipe in your log? That suggests you're seeing an issue that was present in builds around v21 and fixed in v21.4.
I suggest you update to a more recent Magisk release instead of trying to troubleshoot further...
Click to expand...
Click to collapse
thank you for your reply!
The reality is that I'm trying not to mess a lot with these just to be safe!
OK so If I got it correctly, i should do these steps:
select uninstall from magisk manager app,
reboot
and then "Patch the boot (Kernel) image via Magisk" as described in Stage 6 of the link?
any precautions and measures that i should take in order to avoid or minimize failure?

sakis_the_fraud said:
thank you for your reply!
The reality is that I'm trying not to mess a lot with these just to be safe!
OK so If I got it correctly, i should do these steps:
select uninstall from magisk manager app,
reboot
and then "Patch the boot (Kernel) image via Magisk" as described in Stage 6 of the link?
any precautions and measures that i should take in order to avoid or minimize failure?
Click to expand...
Click to collapse
No matter how you choose to update, there's always a risk of failure. Only way to minimise any damages is to make sure you have a backup of any important data before updating.
You should be able to do a direct update in the Magisk app (but since you're jumping a few versions it's a very good idea to have that backup ready). Only thing to mind is that the update to v22+ requires you to not have the Magisk app repackaged with a random name, so make sure you've restored that before updating. This should be the easiest way of doing things...
If you're on the Canary channel (since you have a Canary release installed now), keep in mind that the current Canary (23014) has some major changes from previous Magisk versions. The Hide list has been replaced with a Deny list and there's now a new feature: Zygisk (it's very similar to Riru, if you know that that is). If you're not ready for those kind of changes yet, make sure to be on the stable update channel...
If you don't want to do a direct update the linked guide should work.

Didgeridoohan said:
No matter how you choose to update, there's always a risk of failure. Only way to minimise any damages is to make sure you have a backup of any important data before updating.
You should be able to do a direct update in the Magisk app (but since you're jumping a few versions it's a very good idea to have that backup ready). Only thing to mind is that the update to v22+ requires you to not have the Magisk app repackaged with a random name, so make sure you've restored that before updating. This should be the easiest way of doing things...
If you're on the Canary channel (since you have a Canary release installed now), keep in mind that the current Canary (23014) has some major changes from previous Magisk versions. The Hide list has been replaced with a Deny list and there's now a new feature: Zygisk (it's very similar to Riru, if you know that that is). If you're not ready for those kind of changes yet, make sure to be on the stable update channel...
If you don't want to do a direct update the linked guide should work.
Click to expand...
Click to collapse
Ohhhh I see!
There are major changes listed on the changelog...
I found the "magisk_patched.tar" that I have used on my initial installation, do you believe that if i could flash it will solve this problem?
It's clear that I don't want the latest, i want the one working with minimal risk because I found out that i haven't installed TWRP at all

sakis_the_fraud said:
Ohhhh I see!
There are major changes listed on the changelog...
I found the "magisk_patched.tar" that I have used on my initial installation, do you believe that if i could flash it will solve this problem?
It's clear that I don't want the latest, i want the one working with minimal risk because I found out that i haven't installed TWRP at all
Click to expand...
Click to collapse
If that patched file is from an earlier release of Magisk, and you want to use that version, it's probably best to uninstall Magisk and flash that.
If you want a newer release you can either just choose the stable update channel and do a direct update to v22.1 (you'll be able to update to v23 after that), or you can download the v21.4 zip from GitHub and install that zip from the module section of the Magisk app.
You've got many options. Only you can decide what's best for you...

Didgeridoohan said:
If that patched file is from an earlier release of Magisk, and you want to use that version, it's probably best to uninstall Magisk and flash that.
If you want a newer release you can either just choose the stable update channel and do a direct update to v22.1 (you'll be able to update to v23 after that), or you can download the v21.4 zip from GitHub and install that zip from the module section of the Magisk app.
Click to expand...
Click to collapse
thank you for your help so far!
When i select uninstall i get two options "restore images" and "complete uninstall" what should i choose in order to keep my data?
If i go with the direct update to v22.1, then will i have to flash something? this is "safer"?

sakis_the_fraud said:
thank you for your help so far!
When i select uninstall i get two options "restore images" and "complete uninstall" what should i choose in order to keep my data?
If i go with the direct update to v22.1, then will i have to flash something? this is "safer"?
Click to expand...
Click to collapse
No worries.
To avoid incompatibilities between different Magisk versions you'd have to do a complete uninstall. If you do the direct update you don't have to do anything else then pick "Update" in the Magisk app and then "Direct install".
To say if one or the other is safer is hard to say since there quite a few variables that come into play. Doing an uninstall might cause issues if you've previously disabled encryption, as an example. On the other hand there might also be issues when doing a direct install.
Personally I would go for a direct install, but make sure that I have my firmware's/ROM's unpatched boot image at hand so I can install that and get my device up and running again without any further damage (hopefully). Magisk only alerts the boot image (or in some cases recovery image), which makes it very safe and easy to revert if there are problems. You rarely end up with an irreparable loss unless you start trying to fix stuff without actually knowing what you're doing.

Didgeridoohan said:
Personally I would go for a direct install, but make sure that I have my firmware's/ROM's unpatched boot image at hand so I can install that and get my device up and running again without any further damage (hopefully). Magisk only alerts the boot image (or in some cases recovery image), which makes it very safe and easy to revert if there are problems. You rarely end up with an irreparable loss unless you start trying to fix stuff without actually knowing what you're doing.
Click to expand...
Click to collapse
I made it!
I finally went with direct install as it appears to be less disruptive, first it updated the app, then I selected "direct install (recommended)". Afterwards it started to patch ramdisk, repacked and flashed the image. One reboot later and the root status is back! I really missed my adblock!!!
thank you for your help!

Hide My Applist not working on Android 13

Is anyone else having issues with Hide My Applist on Android 13? It doesn't seem to be working for me. The Zygisk module of the version on the Play Store causes a bootloop and the latest CI/CD build from GitHub never activates.
[Bug] Hide My Applist Service Does Not Start on Android 13 · Issue #168 · Dr-TSNG/Hide-My-Applist
Steps to reproduce/复现步骤 Install the latest Hide My Applist CI build (at the time of this posting, this was the latest build). Activate Hide My Applist in LSposed. Reboot phone. Open Hide My Applist...
github.com

I came here to look into this. I just updated and installing ran me into a bootloop. to bad.. I game alot and use it quite often

Yup, I had to disable the module to get Android 13 to boot. When I updated, I was troubleshooting for 30 minutes until I figured out that one of my modules were causing the problem. Unfortunate that it's not compatible with A13 yet.

Anyone aware of another app with similar ability ?

chmilar said:
I came here to look into this. I just updated and installing ran me into a bootloop. to bad.. I game alot and use it quite often
Click to expand...
Click to collapse
chmilar said:
Anyone aware of another app with similar ability ?
Click to expand...
Click to collapse
Since making this post, the bug preventing it from working on Android 13 has been fixed. It's not on the Play Store yet and only available from the CI/CD pipeline.
Final fix for Android 13 · Dr-TSNG/[email protected]
An Xposed module to intercept applist detections. Contribute to Dr-TSNG/Hide-My-Applist development by creating an account on GitHub.
github.com

David B. said:
Since making this post, the bug preventing it from working on Android 13 has been fixed. It's not on the Play Store yet and only available from the CI/CD pipeline.
Final fix for Android 13 · Dr-TSNG/[email protected]
An Xposed module to intercept applist detections. Contribute to Dr-TSNG/Hide-My-Applist development by creating an account on GitHub.
github.com
Click to expand...
Click to collapse
I ran into the same issue and solved it.
1. Install the Android 13 compatible release from GitHub
2. Do NOT activate the Xposed module
3. Reboot
4. Open Hide My Applist and go to settings, tap 'Force clean runtime environment (root)'
Alternatively, manually deleting /data/system/hide_my_applist_* should fix the problem.

evl3 said:
I ran into the same issue and solved it.
1. Install the latest release from GitHub (login needed)
2. Do NOT activate the Xposed module
3. Reboot
4. Open Hide My Applist and go to settings, tap 'Force clean runtime environment (root)'
Alternatively, manually deleting /data/system/hide_my_applist_* should fix the problem.
Click to expand...
Click to collapse
I just upgraded my Pixel 6 Pro to Android 13, but I installed the CI/CD build on Android 12 and made sure it was working first. The migration from 12 to 13 was painless. No bootlooping at all, and Hide My Applist is working perfectly!

And now there is an official v3.0.0 BETA build with support for Android 13.
Release V3.0.0 Beta · Dr-TSNG/Hide-My-Applist
Uninstall Magisk module! 务必卸载 Magisk 模块！ Support Android 13 Use more effective interception method for higher version systems No longer need the Magisk module, make sure to uninstall it, or you wi...
github.com

Does anyone know if it's possible to hide/block certain apps' access to internal/external storage using Hide My Applist? I'm mostly interested in restricting access to the external SD card. Altering app's permission (regardless of app or hooks definition) only works temporary since access is granted through the app's Android Manifest. I'm talking about those few pesky apps out there that keep on abusing and writing (random) data on SD card.
Note: restricting access to internal storage is possible with Storage Isolation module but I just couldn't find any way of restricting app's access to the external SD card.
I'm on Android 10, rooted with Magisk 25.2
Thanks!

nacos said:
Does anyone know if it's possible to hide/block certain apps' access to internal/external storage using Hide My Applist? I'm mostly interested in restricting access to the external SD card. Altering app's permission (regardless of app or hooks definition) only works temporary since access is granted through the app's Android Manifest. I'm talking about those few pesky apps out there that keep on abusing and writing (random) data on SD card.
Note: restricting access to internal storage is possible with Storage Isolation module but I just couldn't find any way of restricting app's access to the external SD card.
I'm on Android 10, rooted with Magisk 25.2
Thanks!
Click to expand...
Click to collapse
Hide My Applist isn't the right tool for doing this. The tool you're looking for is Storage Isolation. I use it on my phone and can attest to its quality.

David B. said:
Hide My Applist isn't the right tool for doing this. The tool you're looking for is Storage Isolation. I use it on my phone and can attest to its quality.
Click to expand...
Click to collapse
Thanks for the suggestion! I agree, I've been using Storage Isolation as well (as mentioned in the note above) however, SI was designed to isolate only Internal Storage - it doesn't do anything for external SD card.

nacos said:
Thanks for the suggestion! I agree, I've been using Storage Isolation as well (as mentioned in the note above) however, SI was designed to isolate only Internal Storage - it doesn't do anything for external SD card.
Click to expand...
Click to collapse
Oh, sorry. Somehow I had missed your reference to Storage Isolation. I really should read more carefully, I guess. As far as I am aware, Storage Isolation is the only tool that allows for management of redirecting where apps write files. I think your best chance at getting what you want would be to get in touch with the Storage Isolation devs and ask them to add this feature.

David B. said:
And now there is an official v3.0.0 BETA build with support for Android 13.
Release V3.0.0 Beta · Dr-TSNG/Hide-My-Applist
Uninstall Magisk module! 务必卸载 Magisk 模块！ Support Android 13 Use more effective interception method for higher version systems No longer need the Magisk module, make sure to uninstall it, or you wi...
github.com
Click to expand...
Click to collapse
Does anyone else have a Work (or other) profiles on their device? HMA 3.0.5 only finds apps within the base User profile, but I need to hide work profile apps from others. The old version of HMA was able to see all apps. Work apps do not show up in the list of apps that can be manipulated. Can anyone else confirm?

David B. said:
And now there is an official v3.0.0 BETA build with support for Android 13.
Release V3.0.0 Beta · Dr-TSNG/Hide-My-Applist
Uninstall Magisk module! 务必卸载 Magisk 模块！ Support Android 13 Use more effective interception method for higher version systems No longer need the Magisk module, make sure to uninstall it, or you wi...
github.com
Click to expand...
Click to collapse
What is not fully clear to me here:
up to now LsPosed was basis for HideMyApplist, but with the comment here:
"
No longer need the Magisk module, make sure to uninstall it, or you will bootloop"
What "Magisk module" is meant by this and is LSPosed still required then?
As example:
Android 13
Magisk
LsPosed installed and module activated (shows also under magisk modules)
HideMyAppList 3.0.5 installed (which does not require further "Magisk module.."
When opening HideMyAppList it shows as:
Module activated
System service NOT running
-> What is the wrong step here and how do I make the system service run?
-> Last one is solved, reboot fixed it.
Here I do not get phototan app to run on A13 (neither with pure denylist from magisk as it used to run for quite long time, nor with LsPosed + HideMyApp List).
Is anyone able to run this app successfully on A13? (with latest google services and such installed..).
Same issue also happening with TAN2Go App btw with which I just played around now.

Annil said:
What is not fully clear to me here:
up to now LsPosed was basis for HideMyApplist, but with the comment here:
"
No longer need the Magisk module, make sure to uninstall it, or you will bootloop"
What "Magisk module" is meant by this and is LSPosed still required then?
Click to expand...
Click to collapse
Older versions of Hide My Applist had a Magisk module that needed to be installed in addition to activating the Xposed module. The newer versions do not have this module, as all of the functionality is built directly into the app itself. What is meant by this statement is that if you have the Magisk module for an older version installed, you need to uninstall it before upgrading to the latest version because if you do not, your phone will bootloop.

it did the same thing for 3.0.5, install the module and bootloop A13 TT
edit : oh nvm i installed the wrong version, but weird behaviour the system service is not running properly ... hmm
edit : cant use for all cusrom, some of it may have some bugs TT, had to changed to CherishOS but it works fine now

David B. said:
Older versions of Hide My Applist had a Magisk module that needed to be installed in addition to activating the Xposed module. The newer versions do not have this module, as all of the functionality is built directly into the app itself. What is meant by this statement is that if you have the Magisk module for an older version installed, you need to uninstall it before upgrading to the latest version because if you do not, your phone will bootloop.
Click to expand...
Click to collapse
signed in just to upvote this. Ty for clarification!

Koss4c said:
signed in just to upvote this. Ty for clarification!
Click to expand...
Click to collapse
You're welcome! I'm glad it was helpful to you!

Hey guys, unfortunately my phone is bootlooping now, because of having problems with some banking apps I wanted to update HideMyAppList to 3.1.1, since restart its in bootloop
Is there any chance to resolve this issue`?
Would be so thankful if anyone could help me

braisel said:
Hey guys, unfortunately my phone is bootlooping now, because of having problems with some banking apps I wanted to update HideMyAppList to 3.1.1, since restart its in bootloop
Is there any chance to resolve this issue`?
Would be so thankful if anyone could help me
Click to expand...
Click to collapse
Do you have TWRP installed?