Issues with XPrivacy and PMP - LeEco Le Pro3 Questions & Answers

I have successfully installed Magisk v8, SuperSU and Xposed. However, the xposed module xprivacy and PMP do not seem to work. PMP says that it does not get root access. xprivacy freezes the phone.
Did anyone successfully install these modules or did you run into similar issues? Many thanks.
EDIT: I believe the issues can be solved if PHH's Superuser is used instead of SuperSU. Further testing needed.

After I switched to PHH, PMP (Protect My Privacy) works. However, xprivacy does still not work. The problem is that the normal xprivacy window (that allows you to grant or deny permissions) does not appear.
Has anyone successfully installed xprivacy on the Le Pro 3? Thanks.
EDIT: I finally managed to properly enable xprivacy. It was my fault. Not all xprivacy-related processes were enabled in EUI's autostart manager. It is not sufficient to simply enable xprivacy in xposed.

Related

Help needed: Xposed FakeGapps not working on P8 Gratitude V3

I'm going slightly mad...
Removed all google Apps; Installed latest xposed v86 (after pre-installed didn't work, too) and FakeGapps 1.1. Also installed microG from f-droid. All went fine, no errors. When I use microG self-check, however, it tells me my system doesn't spoof signatures. And of course no apps (phonesky, GmsCore) have got correct signatures. Xposed logs are empty.
Any advice?
Thanks.
install again all google Apps
Seriously? I want to get rid of them!
Hello,
I have the same problem (Ascend P7 with Android 5.1.1, magisk, phh superuser, systemless xposed 86.5).
Removed all Gapps, installed fakegapps 1.1 and microg core+framework+droidguard helper.
System spoofs signature on microg self-check: off.
xposed log empty (note: xposed saves it to storage/emulated/0/xposedinstaller instead of data/data/de.robv.../log)
tilleulenspiegel: did you manage to get a workaround to it?
Used android 11 with LSposed : added/enabled gmscore to fakegapps module and now it works

A Few Magisk/Substratum Questions

I just recently did a full fastboot restore. In the past I've always used SuperSU, this time I went with Magisk. Glad I did because it's great. I love that you can fastboot boot TWRP and leave the system read-only and still flash Magisk. I have some Magisk questions that hopefully someone can clear up for me that Googling isn't making clear:
1: The option in Magisk's settings for Systemless Adblock Hosts - does enabling that work with the normal AdAway that you get from F-Droid? Or is that specifically for the Unified Ad Hosts module within Magisk?
2: Does using the normal AdAway break safety net & the ability to take an OTA down the road (if hosts & Magisk are removed)?
3: Does the Unified Ad Hosts module need to be used, or is the normal AdAway OK to use? Or is it that module intended to be used alongside AdAway?
4: I noticed a Greenify4Magisk module - does this module need to be installed in order to use Greenify? I'm used to systemless SuperSU which Greenify just worked. Looking for clarity on Greenify + Magisk.
5: Does using the Xposed Magisk Module allow for Gravity Box customization, that then can be reverted in order to take an OTA? Using the standard Xposed + Systemless SuperSU and removing it later would still leave traces behind that caused OTA's to fail, is the purpose of the dedicated Magisk Xposed modules to solve this issue?
6: (Not Magisk related): Does using a simple Substratum navbar theme (or any Substratum Legacy theme) & then removing it break OTA's? I like to change my navbar to the Pixel one, but still want to easily take the OTA when it arrives next century...
annoyingduck said:
I just recently did a full fastboot restore. In the past I've always used SuperSU, this time I went with Magisk. Glad I did because it's great. I love that you can fastboot boot TWRP and leave the system read-only and still flash Magisk. I have some Magisk questions that hopefully someone can clear up for me that Googling isn't making clear:
1: The option in Magisk's settings for Systemless Adblock Hosts - does enabling that work with the normal AdAway that you get from F-Droid? Or is that specifically for the Unified Ad Hosts module within Magisk?
2: Does using the normal AdAway break safety net & the ability to take an OTA down the road (if hosts & Magisk are removed)?
3: Does the Unified Ad Hosts module need to be used, or is the normal AdAway OK to use? Or is it that module intended to be used alongside AdAway?
4: I noticed a Greenify4Magisk module - does this module need to be installed in order to use Greenify? I'm used to systemless SuperSU which Greenify just worked. Looking for clarity on Greenify + Magisk.
5: Does using the Xposed Magisk Module allow for Gravity Box customization, that then can be reverted in order to take an OTA? Using the standard Xposed + Systemless SuperSU and removing it later would still leave traces behind that caused OTA's to fail, is the purpose of the dedicated Magisk Xposed modules to solve this issue?
6: (Not Magisk related): Does using a simple Substratum navbar theme (or any Substratum Legacy theme) & then removing it break OTA's? I like to change my navbar to the Pixel one, but still want to easily take the OTA when it arrives next century...
Click to expand...
Click to collapse
I can answer a couple of these.
1) the add-on for adblocking in magisk is separate from adblock. You have to use a terminal app to update your HOSTS file.
4) Greenify works just fine without the module. To the best of my knowledge the module you are referring to is for using boost mode on Greenify, which basically allows apps you have hibernated with gcm functionality to still receive gcm push updates.
aybarrap1 said:
I can answer a couple of these.
1) the add-on for adblocking in magisk is separate from adblock. You have to use a terminal app to update your HOSTS file.
4) Greenify works just fine without the module. To the best of my knowledge the module you are referring to is for using boost mode on Greenify, which basically allows apps you have hibernated with gcm functionality to still receive gcm push updates.
Click to expand...
Click to collapse
I was under the impression after reading up on ad away that the systemless hosts toggle in magisk handles ad away as well, and is not just for the ad blocking module with terminal emulator.
Ad away is ok to use and the module I believe the module is not needed. Magisk systemless hosts is compatible with ad away
1: The option in Magisk's settings for Systemless Adblock Hosts - does enabling that work with the normal AdAway that you get from F-Droid? Or is that specifically for the Unified Ad Hosts module within Magisk?
Click to expand...
Click to collapse
Yes it works, fully compatible, does not trigger SafetyNet, no need for Unified Ad Hosts module.
2: Does using the normal AdAway break safety net & the ability to take an OTA down the road (if hosts & Magisk are removed)?
Click to expand...
Click to collapse
It does break, it edit hosts files directly in system folder, use it with Magisk and systemless hosts enabled for SafetyNet certification
3: Does the Unified Ad Hosts module need to be used, or is the normal AdAway OK to use? Or is it that module intended to be used alongside AdAway?
Click to expand...
Click to collapse
Normal AdAway if you have "systemless hosts" activated in Magisk Manager
4: I noticed a Greenify4Magisk module - does this module need to be installed in order to use Greenify? I'm used to systemless SuperSU which Greenify just worked. Looking for clarity on Greenify + Magisk.
Click to expand...
Click to collapse
Not needed, it just enable the boost mode for Greenify without triggering SafetyNet
5: Does using the Xposed Magisk Module allow for Gravity Box customization, that then can be reverted in order to take an OTA? Using the standard Xposed + Systemless SuperSU and removing it later would still leave traces behind that caused OTA's to fail, is the purpose of the dedicated Magisk Xposed modules to solve this issue?
Click to expand...
Click to collapse
It does (my own experience), but IT'S NOT THE PURPOSE OF DEDICATED MAGISK XPOSED TO SOLVE THIS ISSUE, but it solved for me. (of course you need android Marshmallow 6.x.x, Nougat 7.x.x does not have Xposed)
6: (Not Magisk related): Does using a simple Substratum navbar theme (or any Substratum Legacy theme) & then removing it break OTA's? I like to change my navbar to the Pixel one, but still want to easily take the OTA when it arrives next century...
Click to expand...
Click to collapse
I'm not sure about this one '^^, but if it changes stuff in system folder will **** up the OTA.
@Spencervb256 Thanks. @dollarbr Thanks man, I like how you answer questions. You answer them the way I write them which automatically makes you a superior being . Thanks again.
annoyingduck said:
@Spencervb256 Thanks. @dollarbr Thanks man, I like how you answer questions. You answer them the way I write them which automatically makes you a superior being . Thanks again.
Click to expand...
Click to collapse
No problem bro, for me, being answered is already good enough, the way the answer is presented is not a problem, since it does solve the problem, if you need anything else and i can answer just ask :good:

no root adblocker works

Using official 15.1 and I have tried to use adblockers but they are not working I have used energized with systemless root on magisk, that didn't work also tried adaway with and without using systemless root and problem still there. Can't use adblockers. Only have 4 magisk modules running which is busybox, cloudflare, lkt and magiskhide props config.
Any help with this as its annoying.

[Question] How to fake 'Official' Device Status on SM-T350

Hello, I have an SM-T350 rooted with Magisk, how can I fake the Device Status to show Official under settings?
(Right now it says Custom)
Using an Edxposed Module named "Firefds Kit" To install edxposed YouTube or Google Search "How to Install edxposed on Android (Version Goes Here)" then once installed, go to the hamburger menu of the exposed manager app and select downloads, then search Firefds Kit, then select the one for your android, for example, the one for Android Pie would be Firefds Kit [P], then install the latest version, select modules in the hamburger menu, and turn on Firefds Kit, restart, then open the firefds kit app, then go to the hamburger menu, tap security, then turn on "fake official status", restart, and check settings, THIS WILL NOT MAKE APPS LIKE SECURE FOLDER AND S HEALTH (If you sideload it since your on a tablet) THINK YOUR ON OFFICIAL BINARY. to do that, you need to patch one of the system files using a text editor in a root browser and restart, and for secure folder, it is under security in firefds kit, turn on enable secure folder, restart, try to enable it, restart, then hopefully the icon in apps should be there, tap it and set it up.
CaptainChris2018 said:
Using an Edxposed Module named "Firefds Kit" To install edxposed YouTube or Google Search "How to Install edxposed on Android (Version Goes Here)" then once installed, go to the hamburger menu of the exposed manager app and select downloads, then search Firefds Kit, then select the one for your android, for example, the one for Android Pie would be Firefds Kit [P], then install the latest version, select modules in the hamburger menu, and turn on Firefds Kit, restart, then open the firefds kit app, then go to the hamburger menu, tap security, then turn on "fake official status", restart, and check settings, THIS WILL NOT MAKE APPS LIKE SECURE FOLDER AND S HEALTH (If you sideload it since your on a tablet) THINK YOUR ON OFFICIAL BINARY. to do that, you need to patch one of the system files using a text editor in a root browser and restart, and for secure folder, it is under security in firefds kit, turn on enable secure folder, restart, try to enable it, restart, then hopefully the icon in apps should be there, tap it and set it up.
Click to expand...
Click to collapse
Thanks but I have Android 7.1.1 which only works with Xposed not Edxposed so will this work with Xposed? Also what about passing safetynet? I thought safetynet wouldn't pass with Xposed installed? Also when you said "to do that, you need to patch one of the system files using a text editor in a root browser and restart" which system file were you talking about? What do I need to patch? Can I do it without a module?
JJcoder said:
Thanks but I have Android 7.1.1 which only works with Xposed not Edxposed so will this work with Xposed? Also what about passing safetynet? I thought safetynet wouldn't pass with Xposed installed? Also when you said "to do that, you need to patch one of the system files using a text editor in a root browser and restart" which system file were you talking about? What do I need to patch? Can I do it without a module?
Click to expand...
Click to collapse
The system file patch is only if you have s health and want it to work. since you are on a tablet you must likely have notsideloaded it, I don't know if you can do it without a module, the process should be the same with xposed
CaptainChris2018 said:
The system file patch is only if you have s health and want it to work. since you are on a tablet you must likely have notsideloaded it, I don't know if you can do it without a module, the process should be the same with xposed
Click to expand...
Click to collapse
Well, I can't really do it with Xposed because safetynet won't pass plus when I go into Xposed installer (Magisk version) after installing the Xposed Framework Magisk module it still says "Xposed framework is not installed" when I open Xposed installer. So, I may just have to try this on my S8 which runs Android Pie
JJcoder said:
Well, I can't really do it with Xposed because safetynet won't pass plus when I go into Xposed installer (Magisk version) after installing the Xposed Framework Magisk module it still says "Xposed framework is not installed" when I open Xposed installer. So, I may just have to try this on my S8 which runs Android Pie
Click to expand...
Click to collapse
Did you install it properly or turn on Magisk Hide? Since it makes safteynet pass
CaptainChris2018 said:
Did you install it properly or turn on Magisk Hide? Since it makes safteynet pass
Click to expand...
Click to collapse
Yes, MagiskHide was on but I don't think MagiskHide can hide Xposed even if it is system-less. Also, yes I installed Xposed correctly by first installing the Magisk module and then by installing the Magisk compatible Xposed installer app. I don't really know how to solve these two problems
JJcoder said:
Yes, MagiskHide was on but I don't think MagiskHide can hide Xposed even if it is system-less. Also, yes I installed Xposed correctly by first installing the Magisk module and then by installing the Magisk compatible Xposed installer app. I don't really know how to solve these two problems
Click to expand...
Click to collapse
you need a special xposed apk made for the magisk xposed
elliwigy said:
you need a special xposed apk made for the magisk xposed
Click to expand...
Click to collapse
I know, that's what I meant by the "Magisk compatible Xposed installer"

rooted ROM with Magic is not autorized with my Bank app

Hello, I was using EvolutionX_5.8 ROM rooted with Magisk 2.3 and virtually all applications work as intended with this one. Previously, it even worked with my banking app as well. Magisk allowed not to be visible by the application and it opened normally. Alas, since this summer the banking app crashes, the bank no longer wants to allow rooted ROMs, but Magisk got around the problem. Who encountered this problem and was able to fix it. thanks in advance
Enable magisk hide, then download the magiskhide props config. After restarting, setup the module, reset the data and cache from the banking app. Maybe this work
Thank you very much, I found the solution by taking inspiration from a bypass for another secure banking application
I needed to enable the "Hide Magisk App" setting in conjunction with Airfrozen. It was not enough to freeze the Magisk app.
Note: this is not the MagiskHide setting I'm referring to; this setting has been enabled all the time. The steps that worked for me (Magisk 23.0) were: 1. In Magisk, first add Crédit Mutuel to the masking list (of course) 2. In Magisk, do not use "Hide Magisk Application". That is to say. the app is listed as Magisk in the app drawer. 3. Then install Airfrozen and grant root access (I wouldn't get the root access prompt unless # 2 above was done) 4. Now in Magisk turn on "Hide Magisk App" and follow this process to rename "Settings" or the like. 5. Now open Airfrozen and select “Settings” (or whatever name you used in 4). Freeze it. 6. The Crédit Mutuel application is now launched and loads the login screen Hope this helps someone

Categories

Resources