no root adblocker works - Nexus 6P Q&A, Help & Troubleshooting

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.

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

Issues with XPrivacy and PMP

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.

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:

MagiskHide not working on Sunpass App

Magisk Hide works on some apps. I use an app called Sunpass and it was recently updated. It detects root and Magisk Hide doesn't work. Any idea on what can be done?

Someone is using Smali Patcher?

Hi, was using Smali Patcher, the Magisk module to do spoofing in Pokémon GO , in my OP5 with Android 9 without any problems, but now I try to use It in my OP8 Pro and It doesn't works.
I have the Magisk correctly installed and I pass the Safety Net, and the module is correctly installed too, but when I use the fake GPS, my location doesn't moves of my real location, and I don't have any error in the game or Magisk.
aitormix said:
Hi, was using Smali Patcher, the Magisk module to do spoofing in Pokémon GO , in my OP5 with Android 9 without any problems, but now I try to use It in my OP8 Pro and It doesn't works.
I have the Magisk correctly installed and I pass the Safety Net, and the module is correctly installed too, but when I use the fake GPS, my location doesn't moves of my real location, and I don't have any error in the game or Magisk.
Click to expand...
Click to collapse
Maybe the module hasn't been updated to lastest magisk
How have you managed to make Pogo run? What magisk version do you use? I have Magisk hide enabled. I have renamed Magisk Manager. I use hiddencore with edxposed I pass SafetyNet but Pogo doesn't log me in. I get the Unable to authenticate error!

Categories

Resources