MagiskHide doesn't work on "Mes Paiements" (PayLib) - Magisk

Device: Samsung Galaxy Note9 (SM-N960F)
Android: 10 (Q)
ROM: N960FXXS4DTA5_DevBase_v7.1
Magisk : Canary 20306 (last build)
Manager : Canary 277 (last build + hidden)
Xposed: No
SafetyNet : OK (ctsProfile + basicIntegrity)
List of MagiskHidden apps: FateGO, Googlr Pay, La Banque Postale (Mes Paiements), Revolut, knox*, GMS
The app: https://play.google.com/store/apps/details?id=com.lbp.peps
Description:
Even with the latest version of Magisk and the app hidden, when I start the application, I always get a message telling me that the device has been rooted. (Error code 81)
Google Pay is working with the DB modification, Revolut is working, Fate:GO is working but I can't get Mes Paiements working. (So I can't even use my credit card on Internet :cyclops
What I tried:
I tried to unpack the APK and see what trigger the message that telling me the root is detected:
https://i.imgur.com/SWHD5iT.png
If you feel skilled/brave enough or if you have any clue, don't hesitate to tell me.

Same here, with LyfPay (Paylib), on OnePlus 6.
Works fine before Lyfpay last update.

Hi guys,
Same for me too with paylib (caisse d'épargne) with last update 1.8.0 from december.
The app just tell me it no more compatible with my phone...

Do you have "TWRP" folder inside root directory? Try to delete/rename it, reboot and try again.

Micdu70 said:
Do you have "TWRP" folder inside root directory? Try to delete/rename it, reboot and try again.
Click to expand...
Click to collapse
Same problem.
Did you manage to ride over the error 81 ?

marwanpro said:
Same problem.
Did you manage to ride over the error 81 ?
Click to expand...
Click to collapse
I don't use Paylib, but I know "TWRP" folder can be detected for some apps and block them.

Try to download Mes Paiements and try to dodge the error
(L'erreur s'affiche instant au démarrage de l'appli, donc t'es vite fixé)

marwanpro said:
Try to download Mes Paiements and try to dodge the error
(L'erreur s'affiche instant au démarrage de l'appli, donc t'es vite fixé)
Click to expand...
Click to collapse
I can go to "Activation" screen without any issue.
I enabled Magisk Hide for "La Banque Postale" before starting the app.
I use latest Stable Magisk (20.3) with "Hide Magisk Manager" option (rename Magisk Manager app to something else).
You can try to clear app data of this app too.
EDIT: Don't remember why but I renamed any "Magisk" word from filenames in phone's memory too (e.g.: Magisk zip installer and uninstaller).

Hi,
For me, LyfPay app (Paylib Crédit Mutuel), no problem to launch and use Credit Mutuel app and LyfPay app, I can pay with flashcode but I can't pay with NFC.
I enabled Magisk Hide for "Crédit Mutuel" and 'Lyfpay" before starting the app.
I use latest Stable Magisk (20.3) with "Hide Magisk Manager" option (rename Magisk Manager app to something else).
I've cleared app data of Lyfpay app.
However, I'll test by changing the name of TWRP directory and all Magisk filenames...
I'll keep you informed !
Thanks.

It doesn't change...
Rename all files and directories of TWRP and Magisk. Hide Magisk, apps.
I've send a mail to the app contact, they tell me that my phone was rooted... They see the root by an another way...

Hello,
Same for me with Paylib (Caisse d'Epargne).
The old 1.7.1 version works with my Galaxy S8 with Android 9.
But no matter what I try, on my new Galaxy S20, it does not work...

Hello,
I have the same issue (Paylib Caisse d'Epargne), i have tried everything you told in this topic. Nothing work ....
Someone have the solution ?

I do not know if the following will be useful for your issue, but this is how I get my root be hidden from the Crédit Mutuel (CM) app.
I have a Lineage OS 16 (Android 9) running on my Samsung A5 2017 device with Magisk 20.4 and Magisk Manager 7.5.1 installed (with of course Manager hidden by a random package name and the CM app processes checked in Magisk Hide).
Despite all that and after cleaning the CM app storage data and cache, and even after a fresh reinstallation of the CM app, rebooting, etc..., my CM app still started by the warning that my phone was rooted !
Actually, my Samsung phone uses two storage: the internal one (32 Gb) and a Samsung SD card (32 Gb), formatted as extended internal storage.
The CM app was installed on the SD card rather than the native internal storage, along with some installation files I used for rooting the phone (including the magisk.zip and magisk_manager.apk files).
Here is what worked fine for me:
- First, after reading your discussion above, I deleted the previous installation files from the SD card, because those files could indicate that Magisk or whatever rooting methods had been applied on my device.
- Second, and this may be what resolved the issue for me, I moved the CM app from the SD card to the native internal storage, so that it is now installed on a separate storage than the Magisk Manager packages.
Well, now I have a functional root that the CM app does not see anymore.

I don't have a separate SD slot... I deleted files but still don't work.

bolo59 said:
I do not know if the following will be useful for your issue, but this is how I get my root be hidden from the Crédit Mutuel (CM) app.
I have a Lineage OS 16 (Android 9) running on my Samsung A5 2017 device with Magisk 20.4 and Magisk Manager 7.5.1 installed (with of course Manager hidden by a random package name and the CM app processes checked in Magisk Hide).
Despite all that and after cleaning the CM app storage data and cache, and even after a fresh reinstallation of the CM app, rebooting, etc..., my CM app still started by the warning that my phone was rooted !
Actually, my Samsung phone uses two storage: the internal one (32 Gb) and a Samsung SD card (32 Gb), formatted as extended internal storage.
The CM app was installed on the SD card rather than the native internal storage, along with some installation files I used for rooting the phone (including the magisk.zip and magisk_manager.apk files).
Here is what worked fine for me:
- First, after reading your discussion above, I deleted the previous installation files from the SD card, because those files could indicate that Magisk or whatever rooting methods had been applied on my device.
- Second, and this may be what resolved the issue for me, I moved the CM app from the SD card to the native internal storage, so that it is now installed on a separate storage than the Magisk Manager packages.
Well, now I have a functional root that the CM app does not see anymore.
Click to expand...
Click to collapse
Thanks for your reply Bolo59, but I think we have all the same problem, not with the bank app (Crédit Mutuel, Banque Postale, Caisse d'épargne, ...) but with the NFC pay app (Lyfpay Crédit Mutuel, Mes Paiements La Banque Postale, Paiement mobile Caisse d'épargne, ...).
Latest NFC Pay Apps since February detect root.

Hi, I just installed LineageOS 17.1 (in order to get better OS with less bugs... I don't care about root etc.) on an umidigi F1 with Magisk but I cannot access to "Credit Mutuel" app anymore even with this app addede to the Magisk hide list (with magisk hidden, renamed, TWRP directory removed etc.).
The app still recognized the rooted device.
How did you do in order to get it working? Otherwise does someone knows how could I debug it?

Teetoow said:
Hi, I just installed LineageOS 17.1 (in order to get better OS with less bugs... I don't care about root etc.) on an umidigi F1 with Magisk but I cannot access to "Credit Mutuel" app anymore even with this app addede to the Magisk hide list (with magisk hidden, renamed, TWRP directory removed etc.).
The app still recognized the rooted device.
How did you do in order to get it working? Otherwise does someone knows how could I debug it?
Click to expand...
Click to collapse
I'm stilll searching to get Crédit Mutuel from the latest version working on my device.
The latest version working with the now called "Zygisk" (the new Magisk Hide) is the V9.13.0.
You can download it via Aptoide.

Hey there.
Magisk 25.1 with Zygisk, LSPosed and Shamiko installed and configured. XPrivacyLUA with most restrictions on Paylib app. Shamiko on blacklist configured, but Paylib still detects root.
I have no clue what to do more to pass the check…

Related

Raiffeisen Twint (https://play.google.com/store/apps/details?id=ch.raiffeisen.twint)

Hi everyone,
I am using the application Raiffeisen Twint (version 1.2.16.0, https://play.google.com/store/apps/details?id=ch.raiffeisen.twint) on my Magisk's rooted Google Pixel (Android 8.0, Nov. 2017) without problems for a while, but since Magisk 14 versions, the application stopped working and the application reports that root is detected.
I have successfully updated to Magisk 14.5 (from 14.2), but root is still detected by the application, even with Magisk Hide activated for the application and the Magisk Manager package moved to a random name (could also be related to the updated application).
I have cleared the data of the application several times and it doesn't help and root is still detected by the application...
Anyone has a idea?
Thanks for your answers!
Like I said in the Magisk support thread, I can hide Magisk from that app just fine (on Magisk v14.5 beta)...
You don't happen to have any other mods that might trigger an app looking for root (like Xposed)? Can your device pass SafetyNet? Have you previously been rooted with any other root method and do you have any remnants of that left (root management apps, etc)? Do you have any apps that are known to be used for questionable purposes. By "questionable purposes" I mean getting access to paid features without paying, etc. Not necessarily that you use the app for this, but that the app might be used in such a manner... Etc, etc, etc. Every little detail might count.
Hi Didgeridoohan,
Thanks for helping me!
I do not have any mods installed in Magisk and also no Xposed. My device is passing SafetyNet!
I have performed a factory reset last week and since that I only rooted my device with Magisk 14.2, so no other rooting applications used. For details, I have unlocked bootloader, TWRP recovery installed and developer options and USB debugging activated.
My settings in Magisk are:
I have following applications installed on my device:
https://pastebin.com/pmt4jBMV
Do you see any applications with "questionable purpose"?
I get this message in the application:
Thanks a lot!
At a quick glance everything looks ok...
I did some experimenting with the other Raiffeisen apps you have installed, in case they also detect root and "tell" on you. At least one of them did detect root, but from what I could see it didn't make any difference for Twint.
I also tested installing a few of the root apps you had installed (in case the app looks for certain known apps), but that didn't make any difference either. I could still successfully hide root.
My guess is that it's something along these lines tough. That it's using another app or detecting a root app. You could start experimenting with that. Clearing data for the other Raiffeisen apps and adding them to MagiskHide and also removing root apps. Try disabling USB debugging and developer options as well (didn't make difference for me, but worth a shot).
Simple. Change name of package from settings in Magisk Manager, then MAKE SURE you add twint app to magisk hide list, then ERASE DATA of twint app, change package name once again and run twint. Working with Magisk 14.5. Screens if u want available. Or video.
Hi Didgeridoohan, Hi Mamama07,
Thanks for your help, but sadly none of your suggestions did worked... until the update of the application released yesterday, to fix problem related to rooted devices! [emoji3]
Thanks anyway again for your help! [emoji106]
I had the same problem (with BCV Twint) and after a few tries, changing Magisk Package Name worked!

Root detected by GO MOBILE banking app

I've been scratching my head for weeks now this app keeps on detecting root on my device. I've previously tried canary build, but currently on 20.1 and it still detects it. App is MagiskHided, Magisk Manager repackaged, both SafetyNet basicIntegrity and ctsProfile is passed. My other banking app that also checks for root works, even the rootbeerFresh is showing all green and this app still detects root. I don't know what else to try.
Device Info:
OnePlus 6T running Evolution X rom (Android 10), I also tried on OOS pie, doesn't work as well.
Magisk 20.1
This app used to work just by MagiskHide and repackaging Magisk Manager, since the update, I think they changed something. Any help is appreciated.
I tested it right now and had no issues starting the app once added to the Hide list. OnePlus 3T, Android 9 (ArrowOS), Canary build 20302 with hidden Manager build 269.
That means Magisk can hide from the app just fine and there might be something about your specific setup that's being detected. Could be an app, could be a directory on your storage, could be the ROM itself (this is the second time lately that I've seen a user having issues with root detection on Evolution X, on a Poco F1 though. May be unrelated.).
As always, there are a lot of hiding tips available here:
https://didgeridoohan.com/magisk/MagiskHide#hn_Hiding_root_from_apps
Didgeridoohan said:
I tested it right now and had no issues starting the app once added to the Hide list. OnePlus 3T, Android 9 (ArrowOS), Canary build 20302 with hidden Manager build 269.
That means Magisk can hide from the app just fine and there might be something about your specific setup that's being detected. Could be an app, could be a directory on your storage, could be the ROM itself (this is the second time lately that I've seen a user having issues with root detection on Evolution X, on a Poco F1 though. May be unrelated.).
As always, there are a lot of hiding tips available here:
https://didgeridoohan.com/magisk/MagiskHide#hn_Hiding_root_from_apps
Click to expand...
Click to collapse
DId you MagiskHide it beforehand or did you try without MagiskHide first? I want to make sure that the app doesn't "remember" that it has detected root previously
terraflops said:
DId you MagiskHide it beforehand or did you try without MagiskHide first? I want to make sure that the app doesn't "remember" that it has detected root previously
Click to expand...
Click to collapse
I made sure that it could detect root first, so I opened it once without adding it to MagiskHide (got the same screen you showed above). And, I did not have to clear any data for the app after adding it to the list, it just started up without issue.
terraflops said:
DId you MagiskHide it beforehand or did you try without MagiskHide first? I want to make sure that the app doesn't "remember" that it has detected root previously
Click to expand...
Click to collapse
any luck for this problem?
I also have this issue. Any luck?!
I have the same issue and finally found a solution for it ! Change the folder twrp name on internal storage was a trick but don't forget to hide the aplication go mobile from magisk hide then boom I can use the banking aplication on my root devices .
I'm not using any xposed so if you are on xposed try rename the folder of it usually it store on folder download on the internal if that doesn't work try to uninstal the xposed application on your mobile menu(you can instal it again after you're done with banking)
Another trick that I found latelly was I change the recovery ....any recovery besides the twrp (orangefox,pitchblack,batik etc)
Aldino21 said:
I have the same issue and finally found a solution for it ! Change the folder twrp name on internal storage was a trick but don't forget to hide the aplication go mobile from magisk hide then boom I can use the banking aplication on my root devices .
I'm not using any xposed so if you are on xposed try rename the folder of it usually it store on folder download on the internal if that doesn't work try to uninstal the xposed application on your mobile menu(you can instal it again after you're done with banking)
Another trick that I found latelly was I change the recovery ....any recovery besides the twrp (orangefox,pitchblack,batik etc)
Click to expand...
Click to collapse
Awsome maaan, like that simple trick could be solve the pricky app

Epic Seven game root detected!

Hi all , i wanted to try Epic Seven on my rooted mi 9 with magisk 20.4 but even if i used magisk Hide the game detects the root device. Any solution to fix It?
Me too, i don't know how to bypass the root detection of Epic Seven.
I used Magisk Hide but the game still detect it, i used a module like RootCloak but still detect the root and
i've installed RootBeerFresh for test Magisk Hide on it with RootCloak but RootBeer say " Not Rooted " and i have only the " SeLinux Flag Enabled (Experimental) " who have a red cross.
I tried to switch the SeLinux mode to enforcing and restarted my phone but still show a red cross on RootBeerFresh.
( Strangely, the battery is set to 0 and can't unlock my phone in a certain delay so i disabled my lock code )
I've also tried to UNROOT my phone by uninstalling Magisk (with Magisk Manager) and this time, Epic Seven accept my phone to use the game.
I think, Epic Seven check if the Magisk ( not the Manager ) is installed on the system but don't know how to hide him cuz when i use Magisk Hide on other apps and games like Love Live! SIF who also have a root detection, Magisk Hide has successfuly bypased the game but some game like Epic Seven or Guardian Tales seems to have a "deep" root detection.
And when i've installed RootCloak for the first time for hide Epic Seven, the game detect that i've installed RootCloak on my Internal Storage.
If i wanted to bypass the Epic Seven's root detection it's because i wanted to link the game to my microSD to ensure that the game download all the data on it by using the Xposed module " XInternalSD ", so the game don't gonna take too much space on my Internal Storage.
If you whant more infos on my phone :
I have a Samsung Galaxy J6+ (32 Go) with a microSD.
Installed the Custom Rom : EvolutionX 4.4 ARM64
Version : Android 10
Magisk 20.4 & Magisk Manager
EdXposed Manager, Modules : HiddenCore Module, RootCloak and XInternalSD
So you are telling there Is no way to fix It!!! Obviously without unistall magisk
Probably but i think that there is a way to bypass it but i don't know how to do it.
PhyroJ6-55843 said:
Probably but i think that there is a way to bypass it but i don't know how to do it.
Click to expand...
Click to collapse
if you find any solution can you share it with us?
Yes, i'll share it if i find a solution.
Have you renamed any files named magisk on your storage to something else and have you disabled is USB debugging?
toolhas4degrees said:
Have you renamed any files named magisk on your storage to something else and have you disabled is USB debugging?
Click to expand...
Click to collapse
I tryed ti find magisk location but with no results! Do you know the directory? Magisk 20.4
Use magisk hide and then freeze magisk manager with SD maid or titanium backup, this worked for me with a banking app which would detect root otherwise
JetzNicht said:
Use magisk hide and then freeze magisk manager with SD maid or titanium backup, this worked for me with a banking app which would detect root otherwise
Click to expand...
Click to collapse
I freezed It with sd maid but It didn't work
They are using a bug in magisk to identify it so won't work as long you have it installed.
https://github.com/topjohnwu/Magisk/issues/2406
in the link there is a patched version that should works
The patched one works , but you can't install modules so people who have chinese phones( which originally wouldn't have google play services in the rom ) will still fail safety net cause you can't install a certified fingerpint. Some games even check for that ( dragalia lost ) .
A users in the bug report said that you can modify the source of the default magisk to make it work . But i'm not really an expert with building from github and i don't know in which part of the code to look.
cispinox said:
The patched one works , but you can't install modules so people who have chinese phones( which originally wouldn't have google play services in the rom ) will still fail safety net cause you can't install a certified fingerpint. Some games even check for that ( dragalia lost ) .
A users in the bug report said that you can modify the source of the default magisk to make it work . But i'm not really an expert with building from github and i don't know in which part of the code to look.
Click to expand...
Click to collapse
where can i find the patched one?

Question Help Needed - BDO Bank App Says Phone is Is High Risk/Rooted

This is my only financial app that won't work. BDO is a Philippines bank. My US banking apps all open fine.
I'm on EU 12.5.7 Stable. Flashed to 12.5.7 around ~2 weeks ago.
Anyway around this? BDO is possibly the worst banking app on earth - so I'm not entirely surprised it appears to be drunk here.
Thanks in advance!
Move to union bank or metro
You need to root and use Magisk...... then enable Magisk Hide and rename Magisk Manager. That is the only way if you unlocked the bootloader.
dhwalker6 said:
This is my only financial app that won't work. BDO is a Philippines bank. My US banking apps all open fine.
I'm on EU 12.5.7 Stable. Flashed to 12.5.7 around ~2 weeks ago.
Anyway around this? BDO is possibly the worst banking app on earth - so I'm not entirely surprised it appears to be drunk here.
Thanks in advance!
Click to expand...
Click to collapse
Delete the twrp folder using a file explorer app ( it will be empty and safe to delete) and the message goes away and you can install. I tried this for another user.
Sathelp said:
Delete the twrp folder using a file explorer app ( it will be empty and safe to delete) and the message goes away and you can install. I tried this for another user.
Click to expand...
Click to collapse
This worked - ty!
What's the path of that folder?
It is just in the normal storage, like where you download and documents folder sit.
You mean SD Card (internal)root directory? I have no TWRP folder in that directory.
BDO Digital Banking app opens but can't log-in, BDO Online app opens then close after the popup of Poterntial suspicious activity
I refer to the Xiaomi EU ROM. This has an open bootloader but shows as locked. If you are using a different ROM, then may be it won't work the same. If you have never installed twrp, then you won't have the folder.
I've had a lot of trouble with the BDO app, but I just got it working, on a Note 10 pro, running MIUI 12.5.9, unlocked and rooted. I'm not sure if all of these things were necessary, but this is what I did.
1. Delete the TWRP folder on the phone
2. Changed the name of Magisk in it's settings (I used Mi Cloud).
3. Added the BDO app to the DenyList, with Enforce DenyList on.
4. Added the Universal SafetyNet Fix module to Magisk.
SafetyNet passes, and DRM Info shows Widevine L1, and Netflix also works, for what it's worth.
Doesn't work for me. I even unroot my phone (Poco F1, EU ROM) but still got the error.
Will just use their website instead
BDO is so sht. Deleting the TWRP folder worked for me. Thanks!
With magisk you can hide root from apps
Since the BDO app update on Nov. 21, 2022, it's been broken again. Even with Magisk 25.2, Universal SafetyNetFix 2.4.0, with the app on the DenyList (enforced). I had a backup of the old app v6.2, so I restored that, and that's what I've been using. It only works for quick balance now, though, they disabled full access.
It may not be Magisk. In the past, if it detected a TWRP folder, that would do it. It could be something like that again, but not sure what. There's no TWRP folder, of course. v6.2 doesn't complain.
How to Hide Root from Apps via Magisk DenyList [Android 13]
In this comprehensive guide, we will show you the steps to hide root from apps and games using Magisk Denylist on Android 12.
www.droidwin.com
And all is good
That Is done already, and YASNAC passes. The new BDO app v6.3 still fails.
Tested both BDO banking and BDO online out of curiosity. Got the jailbreak/rooted device message at first.
After i deleted TWRP folder, tried again and can get to login screen , no more warnings.
I'm on xiaomi.eu V14.0.6 TKACNXM , not rooted.BDO app tested is v6.3.
Interesting. I did more testing with it today, but still no luck with it. I'm also running xiaomi.eu, but rooted, which I need for other things.
I do notice, under the DenyList, in addition to:
www.mobile.bdo.com.ph
There's a second entry for v6.3 that isn't there on v6.2:
www.mobile.bdo.com.ph_zygote
Both are checked, though. I also checked again to make sure there weren't any twrp folders I could find anywhere, so I don't think it's that.
I finally got the BDO app working with magisk and xiaomi.eu (I'm on 14.0.1.0 now, android 13), by using Magisk Delta, which is not official magisk.
[Discussion] Magisk Delta - Another unofficial third-party Magisk fork
This is not an officially supported topjohnwu project. If you are looking for official Magisk source, please go to this page Introduction Custom Magisk fork by HuskyDG. Sync with official Magisk adding back MagiskHide...
forum.xda-developers.com
It works with Magisk Delta, Zygisk, and SuList.
I could not get it to work with official Magisk v25.2. It may work with the later canary builds, but I haven't tried it. Also, to be clear, the BDO app works with xiaomi.eu without a problem if I'm not using magisk. Either way, though, you need to delete any TWRP folders.

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?

Categories

Resources