( Edit : While people are certainly free to install Magisk, Lineage does not support it since there is a native su option; when Magisk causes issues they're on their own. )
11-01 01:03:39.167 E/AdAway (9038): Failed to update hosts file. 11-01 01:03:39.167 E/AdAway (9038): org.adaway.model.hostsinstall.HostsInstallException: Root access denied 11-01 01:03:39.167 E/AdAway (9038): at org.adaway.model.hostsinstall.HostsInstallModel.applyHostsFile(HostsInstallModel.java:455) 11-01 01:03:39.167 E/AdAway (9038): at org.adaway.ui.home.HostsInstallViewModel.lambda$update$2$HostsInstallViewModel(HostsInstallViewModel.java:124) 11-01 01:03:39.167 E/AdAway (9038): at org.adaway.ui.home.-$$Lambda$HostsInstallViewModel$hr_O0jGNR8I8qQyGthIQYups81s.run(Unknown Source:2) 11-01 01:03:39.167 E/AdAway (9038): at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167) 11-01 01:03:39.167 E/AdAway (9038): at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641) 11-01 01:03:39.167 E/AdAway (9038): at java.lang.Thread.run(Thread.java:764) 11-01 01:03:39.167 E/AdAway (9038): Caused by: org.sufficientlysecure.rootcommands.util.RootAccessDeniedException: stdout line is null! Access was denied or this executeable is not a shell! 11-01 01:03:39.167 E/AdAway (9038): at org.sufficientlysecure.rootcommands.Shell.<init>(Shell.java:134) 11-01 01:03:39.167 E/AdAway (9038): at org.sufficientlysecure.rootcommands.Shell.startRootShell(Shell.java:54) 11-01 01:03:39.167 E/AdAway (9038): at org.sufficientlysecure.rootcommands.Shell.startRootShell(Shell.java:63) 11-01 01:03:39.167 E/AdAway (9038): at org.adaway.model.hostsinstall.HostsInstallModel.applyHostsFile(HostsInstallModel.java:439) 11-01 01:03:39.167 E/AdAway (9038): ... 5 more
I can't seem to get Adaway to request root on android 10. Every other app will request root, but for some reason I can't get Adawy 4.2.9 to request it. 3.3 will request but won't apply hosts file. I have systemless module enabled, core only mode is disabled.
I'm at a loss, this is driving me nuts as I really can't function without adaway working. I keep trying, only to end up going back to pie due to it not working. Any help would be appreciated.
Pixel 1 XL
LOS 10 unofficial
Edit: Not sure why it double posted within the same post.
It looks like there is some sort of issue, or at least, not as stable as expected in Android 10...
Actually, it should be enough for me to test and try to reproduce.
If I don't get the same behavior, I will ask for more logs
...(snipped since unrelated)...
I will have a look at Android 10 in the coming weeks (I would prefer say "days" but I am quite busy those last weeks) and plan to make a release with translation updates.
Thanks again all!
So it looks like your /data/adb/magisk.db is broken (our your Magisk Manager is not in sync with your Magisk). In this database all settings for Magisk Hide and Magisk SU are stored.
To check it, boot into TWRP, use internal filemanager to move this db out of the way (rename it to magisk.db.save e.g.) and reboot. Then try again.
If it does not solve your problem, you may boot into TWRP again and put your saved database back into place...
i gave this a try, other apps request root, adaway does not. but thanks for the tip
Update: thx to post of guest4711 i was finally able to solve the issue.
i edited the magisk.db file manually with sqlite and added under policies table a line:
then symbolic linked magisk su to system/xbin
ln -s /sbin/su /system/xbin/su
rebooted and adaway is working again.
From the steps you describe.
I didn't see you mention AdAway requesting and gaining root access.
I haven't run into it lately, for me, it was always Magisk related.
All other apps / modules seem to work fine but, AdAway always showed me when my Magisk install was broken.
I know I've seen others mention just being able to toggle SU on or off/on for AdAway in Magisk's Superuser settings. If you take a look at the log file in Magisk, you should see a su request once or twice while AdAway is updating (or attempting) to update the hosts file.
May be a change coming down the line but, for now I would still recommend enabling the magisk systemless module.
I would also recommend to use Magisk systemless module if you are running Magisk as root solution.
Here is the link to my sponsor page: https://github.com/sponsors/PerfectSlayer
I am kind of new to this kind of this and I honestly want to know what you think about it: the principle of monthly fee and the tiers I choose (Too expensive? Too cheap? Any reward idea?).
GitHub takes no fee and double the donation the first year so I though it was a good idea to try it.
You are an example of the complexity of the problem. You do not have a system as root (SAR) device*, but are on Magisk 20. I think this is the core of your problem.
I personally would be interested in what would happen if you deleted the systemless hosts module itself, rebooted, then tried to install a hosts file. It will error out again I'm sure.
Then re-enable systemless hosts which should download the module again, reboot and try again with Adaway.
If that doesn't work, I would revert Magisk to 19.3 (which was still a SAR A10 fix) or earlier. I'm sure that will work.
*SAR devices are all minimally released with 9.0
---------- Post added at 08:29 ---------- Previous post was at 08:27 ----------
This exists. It's called DNS logging.
|ad block, adaway, adblock, adblocker, source|
|Thread Tools||Search this Thread|