I purchased my tab in China. Samsung China has deleted all Google apps from the pre-installed rom. As a result, the Chinese GT 10.1 community has compiled an Google app pack (GoogleServeice_P7510.zip) to bring back those apps.
I flashed it immediately after I rooted the tab. The Google apps were installed successfully. I entered my google account after the boot and every google app was running without a glitch. But not long after that I found I could no longer enter browser settings anymore. It would always give me a FC when I tried to do so. I then downloaded the dolphin browser. So this problem was bypassed.
Then I found there was something wrong with the superuser, I could not adb remount/push, and it couldn't be revoked by the apps that required root access.
This problem was partially resolved later by flashing the OC kernel for GT 10.1, which secured adb privileges. But the superuser was still problematic. Then I found out that after I flashed any zip other than root.zip in recovery, be it the kernel.zip, the su_busybox_tools.zip or google_servicepack.zip, the superuser icon in the app drawer would always become 4 times smaller (2 time in both height and length) than the superuser app "installed" by root.zip, as well all other apps.
There seemed to be something wrong with this version of superuser app (small icon). Whenever I opened an app that required root access, the superuser prompt window would not pop out. But if I flashed the root.zip again, the big-icon superuser app would be back. And other apps can revoke it most of time. However, it was not perfectly stable. Somethimes, it still failed to be revoked. I have flashed the root.zip among the other 3 zips for many times to get this conclusion.
I then applied the V6 SuperCharger script and flashed the su_busybox tools for GT 10.1 right before that, because SuperCharger script required busybox. However, due to the superuser problem, the SuperCharger script was not fully working. After reboot, part of the settings was changed back to default, because 99supercharger.sh couldn't be run on boot with root and there's not init.d folder in GT Tab 10.1. Then I flashed the OC kernel hoping it will fix all the problems. After that, I surprisingly found out that I was able adb remount and push. But the icon of the superuser app was again back to the small one. So the apps requiring root could not revoke it for permission.
As a result, I flashed the root.zip again. At this moment, superuser works normally, even after some reboots. SetCPU and script manager are able to automatically acquired root access on boot. But when I rechecked the supercharger script, current pages(minfree) were still showing blank.
Other problems include backspace and enter keys not working in terminal emulator/console. And the problem I just found - the notification ringtone list in the system settings and other app (e.g. Gmail) settings was blank. I could not change ringtone, although the system can play it without problem. And the ogg files are still there in /system/media/notifications.
Since all Android devices works more or less the same. I hope some of you phone experts can shed some light on these problem. The user base of Android tabs has made it less supported than Android phones. It'll be highly appreciated if all these annoying problems get fixed.
Thank you!
I know it was removed from the market.. I have the latest adway from F-droid but it doesn't work.. And yes I am rooted.
Is there any Adblockers that are working? Or ways to fix Adaway?
Randomacts said:
I know it was removed from the market.. I have the latest adway from F-droid but it doesn't work.. And yes I am rooted.
Is there any Adblockers that are working? Or ways to fix Adaway?
Click to expand...
Click to collapse
I had this problem so I uninstalled it and reinstalled it and now its working great..
Sent from my Nexus 5 using XDA Premium 4 mobile app
AdAway works fine. You need to either reboot before installing the APK, or clear out all recent apps before hand.
Yup, works fine for me also
Check your Superuser/SuperSU app to make sure you gave it permission, or;
Uninstall the app, reboot and reinstall, or;
Run fix permissions in CWM/TWRP.
Just to chime in here:
I have noticed that Adaway does fail to apply updated Hosts files. If you just keep telling it to update, it will usually work the second or third time. But it does fail for me the first time almost every time. I'm not sure if it's a r/w issue with Kitkat or just some kind of general compatibility issue.
If by "not working" you mean it fails to apply the host file, just keep trying. It should work eventually.
I know there's a dedicated SuperSU thread but being a newbie on this forum I cannot post there.
I have Teclast P78HD tablet (A31 and Android 4.4.2) which I have rooted using Kingo. There is no custom recovery available for this model, AFAIK, so zip option is out of question I think. Kingo installed SuperSU 1.9.1 which does work, but as Play offered an update I accepted it, got 2.0.1. A big mistake.
The system still works, it prompts to grant root access when an app needs it. But I cannot run the SuperSU app anymore, it asks if I want to update. If I select yes after a while it fails and tells to reboot and try again. Which of course gives the same result. Selecting cancel closes the program. Uninstalling the update returns the system back to working 1.9.1. I have tried also Settings / Cleanup / Reinstall and Settings / Cleanup / Switch superuser app but both fail similarily. I also tried to replace the APK in /system/app using ES File Explorer but this method also makes an app to ask for update.
Any ideas how to update SuperSU on this tablet? Maybe I should just forget the problem and use the current one, but it is somewhat old and the changelog lists many, many changes. Plus Play keeps offering an update which is somewhat annoying
Boffortes said:
I know there's a dedicated SuperSU thread but being a newbie on this forum I cannot post there.
I have Teclast P78HD tablet (A31 and Android 4.4.2) which I have rooted using Kingo. There is no custom recovery available for this model, AFAIK, so zip option is out of question I think. Kingo installed SuperSU 1.9.1 which does work, but as Play offered an update I accepted it, got 2.0.1. A big mistake.
The system still works, it prompts to grant root access when an app needs it. But I cannot run the SuperSU app anymore, it asks if I want to update. If I select yes after a while it fails and tells to reboot and try again. Which of course gives the same result. Selecting cancel closes the program. Uninstalling the update returns the system back to working 1.9.1. I have tried also Settings / Cleanup / Reinstall and Settings / Cleanup / Switch superuser app but both fail similarily. I also tried to replace the APK in /system/app using ES File Explorer but this method also makes an app to ask for update.
Any ideas how to update SuperSU on this tablet? Maybe I should just forget the problem and use the current one, but it is somewhat old and the changelog lists many, many changes. Plus Play keeps offering an update which is somewhat annoying
Click to expand...
Click to collapse
uninstall supersu and try this one. some people have issues with supersu and have found superuser to work correctly.
Hello,
I'm running the latest June (N build) stock and rooted with EX Kernel, downloaded and installed the latest version of Adaway and then downloaded and applied files for adblocking, then rebooted. However, it doesn't seem to be blocking any ads in Google Chrome. Not sure what the issue is, as it's worked on PureNexus ROM for me before and says it's blocking ads. Anyone else experiencing something similar? I don't have systemless root checked off in settings but that's because I'm using SuperSU and not Magisk.
SuperSU tends to install as systemless and you can check it in the settings. If some of the options are grayed out due to saying something like "Not available in systemless mode" then you are on a systemless root so you will have to enable the Systemless Hosts in AdAway.
It's not the rom, Supersu, or Adaway. The hosts file that is being downloaded by default is offline. If you check the Adaway forum you'll see the fix (basically unchecking the hosts file and adding a new one).
Start here:
https://forum.xda-developers.com/showthread.php?t=2190753&page=930
Due to mounting issues with the current root solution on Android 10, Adaway doesn't seem to be able to either write to the hosts file or modify it. Has anyone found a solution?
Thanks....
floepie said:
Due to mounting issues with the current root solution on Android 10, Adaway doesn't seem to be able to either write to the hosts file or modify it. Has anyone found a solution?
Thanks....
Click to expand...
Click to collapse
Really? Mine is working exactly as in Pie. I am rooted with magisk 19.3 and have systemless hosts module installed. Adaway has no issue writing to this hosts file.
clcdev said:
Really? Mine is working exactly as in Pie. I am rooted with magisk 19.3 and have systemless hosts module installed. Adaway has no issue writing to this hosts file.
Click to expand...
Click to collapse
Thanks! Got it working. There is no module any longer, as it is a setting in the app itself - a setting which you just tap with no dialog, only a "toasted" confirmation.
floepie said:
Thanks! Got it working. There is no module any longer, as it is a setting in the app itself - a setting which you just tap with no dialog, only a "toasted" confirmation.
Click to expand...
Click to collapse
When I click that checkbox, I got the confirmation on the bottom that says Adaway was granted Superuser rights, but the box doesn't actually check, and nothing changes. Am I missing something stupid?
Go to setting in magisk and enable this module, restart, and then adaway should work.
I've tried that. Got all messages showing up that it's fine. Rebooted and still see ads in certain pages.
Unfortunately best solution thus far is the AdGuard app but that's VPN and draining juice.
wbgenetic said:
I've tried that. Got all messages showing up that it's fine. Rebooted and still see ads in certain pages.
Unfortunately best solution thus far is the AdGuard app but that's VPN and draining juice.
Click to expand...
Click to collapse
Just to make sure; you also checked the systemless mode in AdAway?
(after reboot to enable magisk systemless module)
If it blocks most ads you may want to add another hosts source.
Mother_Teresa said:
Just to make sure; you also checked the systemless mode in AdAway?
(after reboot to enable magisk systemless module)
If it blocks most ads you may want to add another hosts source.
Click to expand...
Click to collapse
I have the same problem. Pixel 2 XL, Android 10. Magisk works, safetynet works. Adaway doesn't. The systemless hosts module in magisk shows as enabled, the tick box on adaway doesn't work (when I tap it nothing happens). When I select enable adblocking in Adaway it starts building the hosts file and ends with an error message "remount failed. Remounting the partition as read/write failed!".
airmark said:
I have the same problem. Pixel 2 XL, Android 10. Magisk works, safetynet works. Adaway doesn't. The systemless hosts module in magisk shows as enabled, the tick box on adaway doesn't work (when I tap it nothing happens). When I select enable adblocking in Adaway it starts building the hosts file and ends with an error message "remount failed. Remounting the partition as read/write failed!".
Click to expand...
Click to collapse
Are you using the latest AdAway? Maybe you need to update the app itself.
Hmmm can I add other stuff to the hosts file? Sort of like easy lists for different languages like adblocker on chrome for PC? This might do the trick if possible.
hunfatal said:
Are you using the latest AdAway? Maybe you need to update the app itself.
Click to expand...
Click to collapse
Version 4.2.9. F-droid says it's the latest
wbgenetic said:
Hmmm can I add other stuff to the hosts file? Sort of like easy lists for different languages like adblocker on chrome for PC? This might do the trick if possible.
Click to expand...
Click to collapse
Yes, checks settings
So most ads get blocked but not all?
adaway forum to get latest version and gossip.
I also had issues getting AdAway running on Android 10, but managed to get it going eventually. I had the same issues as the others: "Enable systemless mode" checkbox was "toasting" but not checking in AdAway, despite tapping the "Systemless hosts" item in Magisk and getting successful-looking toast notifications.
Steps that worked for me:
Take note of any settings you have in AdAway, as they are about to go away
Completely uninstall AdAway. This means Force Stop, Clear Cache, Clear Data, then Uninstall
Reboot
Open Magisk Manager --> Settings --> Tab the "Systemless hosts" item. You should get the toast notification.
Install the latest version of AdAway (v4.2.9 as of now, as others have mentioned)
Open AdAway --> Preferences. With luck, you'll see that Enable systemless mode is checked already (pretty sure mine was). If not...maybe try checking it now.
AdAway should work now. Make sure to poke around and add back any customizations you used to have.
Hope that helps!
I stopped using adaway in favor of DNS66 for about two years now. Might be worth a shot if you're still having issues with Adaway
https://f-droid.org/en/packages/org.jak_linux.dns66/
HypromanGT said:
I also had issues getting AdAway running on Android 10, but managed to get it going eventually. I had the same issues as the others: "Enable systemless mode" checkbox was "toasting" but not checking in AdAway, despite tapping the "Systemless hosts" item in Magisk and getting successful-looking toast notifications.
Steps that worked for me:
Take note of any settings you have in AdAway, as they are about to go away
Completely uninstall AdAway. This means Force Stop, Clear Cache, Clear Data, then Uninstall
Reboot
Open Magisk Manager --> Settings --> Tab the "Systemless hosts" item. You should get the toast notification.
Install the latest version of AdAway (v4.2.9 as of now, as others have mentioned)
Open AdAway --> Preferences. With luck, you'll see that Enable systemless mode is checked already (pretty sure mine was). If not...maybe try checking it now.
AdAway should work now. Make sure to poke around and add back any customizations you used to have.
Hope that helps!
Click to expand...
Click to collapse
FIXED : Did same twice didn't work untill i gave permission of storage to the app before launching it
driss.sadok said:
FIXED : Did same twice didn't work untill i gave permission of storage to the app before launching it
Click to expand...
Click to collapse
I have done step by step and doesnt work, i've got android 9, but it doesnt metter still cant make it work. Root works, hosts i've checked with file menager is also full, updated sources. Checked with 3 browsers and i still see alot of ads...
smile20 said:
I have done step by step and doesnt work, i've got android 9, but it doesnt metter still cant make it work. Root works, hosts i've checked with file menager is also full, updated sources. Checked with 3 browsers and i still see alot of ads...
Click to expand...
Click to collapse
have you enabled systemless hosts in magisk?
gvsukids said:
have you enabled systemless hosts in magisk?
Click to expand...
Click to collapse
Yes, in magisk manager, restarted system, then installed adaway, gave permission to storage before first turn on, then checked systemless host setting in Adaway menu, but it was already on, downloaded sources, restarted system and now it supposed to wotk, but it doesn....There was just one reason i've rooted system, and it doesnt work...
Try enabling the hosts before installing adaway. Are you using the fdroid version?
gvsukids said:
Try enabling the hosts before installing adaway. Are you using the fdroid version?
Click to expand...
Click to collapse
This is how i've done . First enabled in magisk manager, then installed Adaway. I've downloaded direct Adaway apk from frdroid site.