How come I can't get AdBlock to work properly? - ZTE Axon 7 Questions & Answers

I am rooted and unlocked using the latest B29 update, US model. Most other root apps work fine, titanium, root explorer, etc. But when i try to add AdBlock it says failed to create host files, and something about creata sym link, but can't create it. Any ideas why this wont work? Thank you in advance

You need to disable Emmc write protection after root.. Search the forum they have given the commands to disable it thru terminal or adb
Sent from my ZTE A2017U using Tapatalk

adb shell reboot disemmcwp

Would write protection cause that error? I never had errors like that before disabling WP, just that the changes wouldn't stick.

Small Suggestion. Buy a Raspberry Pi 3 for $35. Install Pi-Hole as a DNS Server. . Configure the Raspberry Pi-Hole as the DNS on your router. Your entire Network devices are protected from Ads. Simple low cost solution to protect all devices in one shot.
Sent from my ZTE A2017U using Tapatalk

I am having the same problem, but I have tried reboot disemmcwp. SuperSu shows it has granted Adaway root, Adaway gives me the message "Either the su binary could not be found or you did not allow root permission for Adaway...."
I have reinstalled the app several times and deleted Adaway storage.
Is it possible I have BusyBox installed in the wrong location?
PS I am on Cyanogen

Kama45 said:
I am having the same problem, but I have tried reboot disemmcwp. SuperSu shows it has granted Adaway root, Adaway gives me the message "Either the su binary could not be found or you did not allow root permission for Adaway...."
I have reinstalled the app several times and deleted Adaway storage.
Is it possible I have BusyBox installed in the wrong location?
PS I am on Cyanogen
Click to expand...
Click to collapse
If you're on CM, you don't need to use SuperSU.
Settings > Developer Options > Root Access

Related

[HELP] How to ROOT multi user

Hello
Firstly sorry for my english
I'll tried to explain my problem
I successfull to root my device but only the main user account but I can't obtain access root in others account.
How can I do this ?
Thanks
At the moment you can't until Google updates that feature to allow that. The multiuser is in its infancy. We will just have to wait I guess.
Sent from my Nexus 10 using Tapatalk HD
Thanks for your answer
waiting for this ...
It's actually the su binary which is tied to the primary user only at the moment... not sure how, or if, it can be built otherwise!
Furthermore, it is not even possible to enable developer settings (via build no) for second users, right?
So, without USB-Debugging no adb to backup second user apps (w/ data) using the Toolkit..
Is there any chance to fully backup second user apps? Apart from nand of course, as I would like to backup/restore apps for a switch to CM10.
Superuser 3.3 now supports multi-user root... 3 modes... Owner only, Owner controlled & User controlled... I will post an update zip here once I built su & Superuser tonight!
craigacgomez said:
Superuser 3.3 now supports multi-user root... 3 modes... Owner only, Owner controlled & User controlled... I will post an update zip here once I built su & Superuser tonight!
Click to expand...
Click to collapse
Wow... That would be truly amazing! Sounds like you are mod'ing the apps yourself, or are they updating to include the feature? I'm pumped at this possibility! Thanks craig!
Sent from my Nexus 10 using Tapatalk 2
djd338 said:
Wow... That would be truly amazing! Sounds like you are mod'ing the apps yourself, or are they updating to include the feature? I'm pumped at this possibility! Thanks craig!
Sent from my Nexus 10 using Tapatalk 2
Click to expand...
Click to collapse
Nope... not my mod... official updates to Superuser... I've just built it with the new changes!!
Here you go... Superuser-3.3-arm.zip
Notable Changes (from Superuser 3.2):
1. Android 4.2+ multi-user support [3 mode -> Owner only, Owner controlled & User controlled]
2. Better handling of applications with multiple root (su) requests
Flashing using a custom recovery (TWRP or CWM). I recommend wiping data for the Superuser app and re-granting your root apps su access to avoid any problems.
NOTE: Even though Superuser 3.3 supports multiple users, you root apps may not... so there is no guarantee that all root apps will work fine in multi-user mode. For those app, you will need to wait for the app developers to update their apps to support multiple users.
craigacgomez said:
Nope... not my mod... official updates to Superuser... I've just built it with the new changes!!
Here you go... Superuser-3.3-arm.zip
Notable Changes (from Superuser 3.2):
1. Android 4.2+ multi-user support [3 mode -> Owner only, Owner controlled & User controlled]
2. Better handling of applications with multiple root (su) requests
Flashing using a custom recovery (TWRP or CWM). I recommend wiping data for the Superuser app and re-granting your root apps su access to avoid any problems.
NOTE: Even though Superuser 3.3 supports multiple users, you root apps may not... so there is no guarantee that all root apps will work fine in multi-user mode. For those app, you will need to wait for the app developers to update their apps to support multiple users.
Click to expand...
Click to collapse
So, could I use this updated su to change ROM control settings for multiple users on aokp?
Sent from my Nexus 10 using xda app-developers app
jrod091 said:
So, could I use this updated su to change ROM control settings for multiple users on aokp?
Sent from my Nexus 10 using xda app-developers app
Click to expand...
Click to collapse
I don't know if RC settings are global or user specific... depends of the settings... if the setting is specific to the user context, it will work, otherwise it won't...
drykc said:
Hello
Firstly sorry for my english
I'll tried to explain my problem
I successfull to root my device but only the main user account but I can't obtain access root in others account.
How can I do this ?
Thanks
Click to expand...
Click to collapse
If you are using SuperSu, the dialog asking for root permission shows up on the owner's user account. In SuperSu, only the owner can grant superuser privileges.
Sent from my Nexus 4
Is Superuser 3.3 good for Nexus7? the file says "arm" - Nexus 7 is not an arm processor...
Vlad7777 said:
Is Superuser 3.3 good for Nexus7? the file says "arm" - Nexus 7 is not an arm processor...
Click to expand...
Click to collapse
Should probably ask in the n7 forum...
Sent from my Nexus 10 using xda app-developers app
Vlad7777 said:
Is Superuser 3.3 good for Nexus7? the file says "arm" - Nexus 7 is not an arm processor...
Click to expand...
Click to collapse
The SoC in the Nexus 7 is Tegra 3, which has an ARM processor. You're fine.
Sent from my Nexus 10
Vlad7777 said:
Is Superuser 3.3 good for Nexus7? the file says "arm" - Nexus 7 is not an arm processor...
Click to expand...
Click to collapse
Lol of course n7 has an arm cpu!
For android phones and tablets, there's arm, mips, and x86. Any good android will 98% likely be arm. Motorola released an x86 (Intel) phone, and I'm sure there's a few other ones out there. And if you have mips, you probably got a cheapy Chinese tablet. xP
Swiped from my Nexus 10 using xda-developers app
Sorry for hijacking.
My main reason for root is to restore application data. Will I be able to restore the data on both the primary user and also the secondary user if I have root (either through the main or secondary user)
Did i do something wrong?
I had supersu installt- and need multiuser acsess . So i install Superuser in recovery with the zipfile .
But now no root app will work- with no user.:crying:
notice main user by starting: sorry i cant get root.... this was a try by /system/bin/su .
2 notice by superuser -on screen and in the log: superuser rights of ..app... are denied.
What do i do now ?
Kind regards
gandalf
1234556789 said:
Did i do something wrong?
I had supersu installt- and need multiuser acsess . So i install Superuser in recovery with the zipfile .
But now no root app will work- with no user.:crying:
notice main user by starting: sorry i cant get root.... this was a try by /system/bin/su .
2 notice by superuser -on screen and in the log: superuser rights of ..app... are denied.
What do i do now ?
Kind regards
gandalf
Click to expand...
Click to collapse
It sounds like the zips don't play very well together.
Boot into recovery.
Mount /system
Delete /system/app/Superuser.apk
Delete /system/bin/su (if it exists)
Delete /system/xbin/su (if it exists)
Clear the Dalvik cache to err on the safe side.
You should now be unrooted. (In fact you could boot up, and you should see there is no superuser app installed)
Now, just flash the superuser zip again to root your device.
KlipperKyle said:
It sounds like the zips don't play very well together.
Boot into recovery.
Mount /system
Delete /system/app/Superuser.apk
Delete /system/bin/su (if it exists)
Delete /system/xbin/su (if it exists)
Clear the Dalvik cache to err on the safe side.
You should now be unrooted. (In fact you could boot up, and you should see there is no superuser app installed)
Now, just flash the superuser zip again to root your device.
Click to expand...
Click to collapse
Thanks for it- but how i delete the files? On backup+restore i only can delete backups. Am i blind?
..............................................................................................................
edit: Tried a solution with nexus toolkit 4.2 i root once more, install superuser und install theupdate to 3.3.
get root for the main user- rootapps work-
but only the main user had root- i tried the update fixer -....gaining root acsess...fail.
so what is wrong?- had anybody a solution?
Kind regards
gandalf
1234556789 said:
Thanks for it- but how i delete the files? On backup+restore i only can delete backups. Am i blind?
..............................................................................................................
edit: Tried a solution with nexus toolkit 4.2 i root once more, install superuser und install theupdate to 3.3.
get root for the main user- rootapps work-
but only the main user had root- i tried the update fixer -....gaining root acsess...fail.
so what is wrong?- had anybody a solution?
Kind regards
gandalf
Click to expand...
Click to collapse
It sounds like you have Superuser 3.3 installed and working, right? In order to use Superuser 3.3 with another user account, you need to go to its preferences and change Multi-user Mode to something other than "Owner Only."
"Owner only" means that only the owner can su.
"Owner controlled" means that the owner is the only one who can set and deny root permissions. Any filters are applied to all users.
"User controlled" means that each user can define allow/deny filters. Only use this option if you really trust other users.
Don't update to the version of Superuser on the Play Store. The version on the Play Store is 3.1.3. You already have 3.3 flashed on your system partition. Because you won't need the version on the Play Store, you can also stay away from ChainsDD's Superuser Update Fixer. (The update fixer is for an entirely different issue than the one you have.)
If you have installed these packages, you should uninstall them.
For future reference:
I should have been clearer about deleting files in custom recoveries. If you use TWRP, there is a built-in file manager under the Advanced menu. If you use ClockworkMod, you should use ADB commands: (ADB is a tool found in the Android SDK)
Code:
adb shell
cd /system
ls -al
[I](You should see a bunch of directories. If not, make sure /system is mounted.
This is an option in one of the recovery menus; I can't remember which
one offhand.)[/I]
rm app/Superuser.apk
rm bin/su
rm xbin/su
Then reflash the Superuser zip.

Titanium backup not working on 6.0.1

I can't delete any system apps with it anymore, does anybody else have the same problem or even a fix for it?
Working fine on 6.01 for me, Did you try uninstalling and reinstalling it?
I just updated to 6.0.1 myself, rooted using superSU 2.61. I too cannot delete system apps using titanium. I tried to uninstalled and reinstall the app (via playstore) but it didn't help.
I also tried to do the same via the root explorer option in ES file explorer and it didn't work. I tried to toggle the root explorer option in ES, but after I turned it off I couldn't turn it on again. Root checker does say that I have root, and other root apps e.g. adaway, xprivacy still work.
Any help and suggestion is most welcome!
case-sensitive said:
I just updated to 6.0.1 myself, rooted using superSU 2.61. I too cannot delete system apps using titanium. I tried to uninstalled and reinstall the app (via playstore) but it didn't help.
I also tried to do the same via the root explorer option in ES file explorer and it didn't work. I tried to toggle the root explorer option in ES, but after I turned it off I couldn't turn it on again. Root checker does say that I have root, and other root apps e.g. adaway, xprivacy still work.
Any help and suggestion is most welcome!
Click to expand...
Click to collapse
hey guys, "system less root"
That would modify system... Just freeze the apps.
geoff5093 said:
That would modify system... Just freeze the apps.
Click to expand...
Click to collapse
Some people still want to recover the space.
With systemless root you will need to modify the system in TWRP to get titanium and ES working correctly.
It's as simple as going into TWRP and mounting the system R/W.
You then need to open the terminal in the following places:
/system/bin and execute "touch su"
/system/xbin and execute "touch su"
This will create zero byte files for SuperSu to come along and swap/link to on boot so that ES and TiBu can ask for root and get it.
They will then operate as you expect.; with the caveat that you are on your own when you start tinkering and may break something.
tech_head said:
Some people still want to recover the space.
With systemless root you will need to modify the system in TWRP to get titanium and ES working correctly.
It's as simple as going into TWRP and mounting the system R/W.
You then need to open the terminal in the following places:
/system/bin and execute "touch su"
/system/xbin and execute "touch su"
This will create zero byte files for SuperSu to come along and swap/link to on boot so that ES and TiBu can ask for root and get it.
They will then operate as you expect.; with the caveat that you are on your own when you start tinkering and may break something.
Click to expand...
Click to collapse
Pretty sure you lose Android Pay with this method though, just FYI if you care about that.
But if you are running Xposed you broke it anyway. There is a way to get it working.
You will need to remove the empty su files you just created to be able to add cards.
You will need to use a Xposed module to hide modifications to the system so that the device check comes back clean.
It's a pain, but if you want Xposed, TiBu, ES and Android Pay, that is the price.
Sent from my Nexus 6P using Tapatalk
I usually use this app:
https://play.google.com/store/apps/details?id=com.jumobile.manager.systemapp
I'm not on 6.0.1 at the moment so I can't test if it works. Anyone wanna test it out and report back?
WizeGuyDezignz said:
I usually use this app:
https://play.google.com/store/apps/details?id=com.jumobile.manager.systemapp
I'm not on 6.0.1 at the moment so I can't test if it works. Anyone wanna test it out and report back?
Click to expand...
Click to collapse
Doesn't work. Apps restore themselves.

AdAway on stock nougat- copying of host file failed

hello im getting the following message everytime i try and download the lists "copying of host file failed! please read help for more information"
ive just updated to the android 7.0 through the developer program, twrp custom recovery installed with root access build number NRD90M
just wondering what could be causing this and if i can do anything to try and fix it thanks
Is your /system set to read only, or read/write? If read only, adaway will not be able to update /system/etc/hosts
dratsablive said:
Is your /system set to read only, or read/write? If read only, adaway will not be able to update /system/etc/hosts
Click to expand...
Click to collapse
i have it set to read write im gonna try to flash the systemless hosts right now ill update how it goes
flashing the AdAway_systemless_hosts_v2.zip in the recovery, then unistalling and reinstalling the app seems to have worked
you can also use Magisk now to enable complete systemless root and then the hosts file /system/etc will be forwarded to the systemless version
I didn't even install Adaway, I just downloaded a host file and replaced it in /etc/
Works good enough for me and one less app running...
kennehh said:
hello im getting the following message everytime i try and download the lists "copying of host file failed! please read help for more information"
ive just updated to the android 7.0 through the developer program, twrp custom recovery installed with root access build number NRD90M
just wondering what could be causing this and if i can do anything to try and fix it thanks
Click to expand...
Click to collapse
In the exact same boat. Frustrating. Tried Adfree, to no avail. Adaway, to no avail. Tried the adaway bind zip file, making hosts writable, and even System to writable. Nothing.
treoo0_1 said:
In the exact same boat. Frustrating. Tried Adfree, to no avail. Adaway, to no avail. Tried the adaway bind zip file, making hosts writable, and even System to writable. Nothing.
Click to expand...
Click to collapse
i have fixed this by converting adaway from user apps to system apps using Link2SD, reboot and adaway working properly again
Very old thread, but I've had exactly the same problem installing AdAway on the last 3 or 4 phones -- all but one running Nougat 7.0, the other on Oreo 8.1. This was when trying to install AdAway versions 3.1 and 3.3.something.
I finally got it to write hosts file updates using one of the following, not sure which was the key:
-- Installed version 3.2 which had been running problem-free on an old phone for years. The biggest difference is this older phone is running Resurrection Remix 5.8.3 (Nougat 7.1.2).
-- Before trying to update the hosts file on this fresh install, I went straight to AdAway preferences and set "Check for updates daily", "Enable webserver", and "Start webserver on boot". After making those settings I tapped Download Files and Apply Ad Blocking, and it successfully wrote to the hosts file.
Again I don't know which was the fix. It seems weird that version 3.2 would work when a version just before and after it didn't work for me. But of course it is possible that the version is the difference. It seems even more weird that those 3 little preference settings make any difference at all . . . unless it's just the act of writing changes to the AdAway app itself.
Before installing 3.2, using Root Explorer I checked permissions on the working phone and one non-working phone, for the systems and etc folders, and for the hosts file itself. (In all cases AdAway is/was set to use /systems/etc/hosts.) I also checked Android permissions in the Apps list. All permissions were exactly the same on both phones: 0755 for system, 0755 for etc, and 0644 for hosts. No permissions assigned via Android.
Hoping this bump will also get fresh attention from somebody who might know the details of a real answer.
@Moondroid
Why the hell you trying to make some really old ass version of it work instead of installing the newest version? Lol
I've been using 4.2.7 and though its kind of weird on a fresh install I need to update and apply the hosts twice before searching for newer hosts comes back its up to date. But at least it works.

Adaway fails to find su binary on Moto x style (pure)

I have rooted almost every phone I've had and have always used the same rom, superuser app, etc. I recently switched from dirty unicorns 6.0 to aicp 7.0 because of an Android os problem. I have both SuperSU & magisk manager apps and binaries installed ( both came with rom for some reason and can't get rid of either, didn't mind too much) and when I open adaway it asks for superuser permissions and I grant it, then another window will pop up saying it can't find the su binary or I didn't grant it root access. I went through some other forums and tried using a terminal emulator to be able to rewrite system, But came back with saying "there is no such file or directoryā€¯. I then tried installing "mount /system ro/re (root)" from the play store, it said it was successful. So I tried adaway again and still says the same thing. Any other ideas?
Magisk has own "hosts", you don't need adaway. @as.hs
dzidexx said:
Magisk has own "hosts", you don't need adaway. @as.hs
Click to expand...
Click to collapse
I checked magisk and I see what you are saying (I think) and checked the option but it says it doesn't get rid of ads, it just supports adblocker apps, does that mean I still don't need an adblocker?
I'm using AdClear app, it does the work for me. Also we can select individual app in which we want ads blocked
https://forum.xda-developers.com/android/apps-games/app-adclear-root-version-ad-blocker-t3309011

Magisk v 11.6 SafetyNet [issue]

What's guys.
I've done root on my Moto G5 Plus, everything is fine, except for 2 things.
First, I was unable to make Freedom work, but I've download Root Explorer and everything is good.
Second, is about this thread and Magisk root.
As I play Super Mario Run, there's a opition at Magisk called Madisk Hide.
But it is not working properly, as a press SafetyNet check and I receive a error CTS profile mismatch.
Could someone help with that?
PS: Sorry for my bad english.
I'm getting the same CTS profile mismatch.
Follow Steps :
1. Enable Magisk hide
2. Disable Android Debugging
3. Clear mario app data
It should work.
Mrdeviljv said:
Follow Steps :
1. Enable Magisk hide
2. Disable Android Debugging
3. Clear mario app data
It should work.
Click to expand...
Click to collapse
The problem is the mismatch on Magisk.
I tried that.
I have to download using Apteoide, beucase of root, the game was hide on playstore.
I've already tried that with no sucess.
I can play the game on the first level and tutorial, but when it's download the data, the game doesn't work anymore...
I have the same 'CTS profile mismatch' with Magisk, and Root Uninstaller says "have rooted but have not rw permission in /system" (Or something like that..)
i can't uninstall bloatware, i'm using led apk and other root functions, but uninstaller not working and adfree also fails blocking ads (sorry bad english)
Leodev said:
I have the same 'CTS profile mismatch' with Magisk, and Root Uninstaller says "have rooted but have not rw permission in /system" (Or something like that..)
i can't uninstall bloatware, i'm using led apk and other root functions, but uninstaller not working and adfree also fails blocking ads (sorry bad english)
Click to expand...
Click to collapse
In android n you have to mount system partition in order to remove bloatware follow below steps :
1.install busybox and terminal app
2.issue following command in terminal
Su
Now grant root access to terminal
3.now issue following command
busybox mount -o rw,remount system
That's it now you should be able to remove bloat.make sure to install busybox as mentioned in step 1

Categories

Resources