Database Develop

[HOW TO] Remove ads using adfree android

This was created when we didn't have S-OFF yet.
If you have S-OFF or /system overlay script you won't need to go through all the steps simply download adfree android.
I know most of you will be able to do this. But I believe that it might not be as easy for the beginners. So here is a little walk through.
!NEEDs ROOT!
1. Download Adfree Android
2. Wait for it to determine local hosts then click on download and install hosts.
Now it will try to replace /system/etc/hosts but fail (it should reboot the phone but it didn't reboot mine)
4. go to adb and reboot your phone into recovery (with power on+volume down OR the command: "adb reboot recovery")
5. Open up the recovery-windows (start recovery-windows (make sure your in the right directory))
6. mount your system and sdcard you might be able to just use mount and mount everything but I've mounted them serperatly.
Here's how: "adb shell mount /system" next "adb shell mount /sdcard"
7. Now we're going to put it in the etc directory where it should be: "adb shell cp /sdcard/hosts /system/etc"
8. reboot the phone ("adb reboot")
That should remove most of the adds.
I know it's explained on a really low level of knowledge but I wanted to make it accessible for all of you.
Only the needed codes:
Code:
1. adb reboot recovery
2. start recovery-windows
3. adb shell mount /system
4. adb shell mount /sdcard
5. adb shell cp /sdcard/hosts /system/etc
6. adb reboot

has it the option to only block browser ads? when I tried it time ago it couldn't. I don't like to block the app ads

No it removes the adds everywhere. It simply blocks the links to adds. it doesn't actually remove them. they are still being called but they just don't show up.

Hi,
I have this very same problem for a long time now, with the constant reboots etc.
Followed your steps, but after the reboot, as soon as I press the button to update the hostfile, it reboots my phone
Thanks anyway...

PirateNL said:
Hi,
I have this very same problem for a long time now, with the constant reboots etc.
Followed your steps, but after the reboot, as soon as I press the button to update the hostfile, it reboots my phone
Thanks anyway...
Click to expand...
Click to collapse
Do you have root access?
Have you checked if the hosts file is at the root of your SD?

A good guide, if a little misplaced, but another option is the /system overlay.

JonasDroid said:
Do you have root access?
Have you checked if the hosts file is at the root of your SD?
Click to expand...
Click to collapse
Yes and yes

where is the most recent hosts file? I'm using a vibrant and it says it worked, but of course, it doesn't. And it doesn't copy the hosts file to my sdcard either ? odd

Hello ,
Finally I got Adfree working
Ok it's not perfect because app continue to reboot the phone after updating the hosts file ,
and we need to copy it manually in recovery mode but it better than nothing
Thank you very much JonasDroid for this little How to .
PS:
For me step 5
JonasDroid said:
Code:
5. adb cp /sdcard/hosts /system/etc
Click to expand...
Click to collapse
was
Code:
adb shell cp /sdcard/hosts /system/etc
Bye.

Yeah indeed its adb shell cp thx for letting me know
Sent from my Legend using XDA App

Can you link me the apk of adfree? I can't download the app from my phone

BTW it's 'ADs" single d
short for advertisment (notice the single d?)

Fixed that English is not my main language
Sent from my Legend using XDA App

JonasDroid said:
5. Open up the recovery-windows (start recovery-windows (make sure your in the right directory))
Click to expand...
Click to collapse
Can't get "start recovery-windows" to work. What is the "right directory"?
Things seems to have worked for me without that portion. Many thanks, I will now change my review in the market for that app from one star to three stars. If they include a note describing this problem upfront I may bump it up further.

It could simply be called start recovery (depending on where you got your rooting tools)(if you've got the from The Unlockr you'll need the -windows)
If you have S-OFF or if you use an /system overlay script these steps aren't needed. (It was created when we didn't have S-OFF for our legends yet.)

Anyone having problems with adfree scripts on Legend since Froyo update? Neve had a problem witha rooted 2.1, but have lots of problems since rooted Froyo 2.2
It seems HTC may have some service which is checking for modifications to symlinks etc.

When I run adfree in my S-off CM7, i get an java.io.EOFException.
Someone else having this?

I had some problems at first, but reinstalling adfree android from market seemed to help. No problem now with CM7 (01/03 from ali ba) and s-off.

adfree no block ads!
Hi,
i install the adfree on my legend with 2.2 with sense.
i did download the host from the app all work ok got a message say it was success install and need to restart the phone.
i did it but still get all the ad like before on all apps.
pls help!

Have you followed the steps? (explained in first post)
Note that you should have a rooted legend (if you don't know what that is then you don't have one)

[Literally Step by Step Guide] Retain Root from ICS to JB

Update:
Holy crap, I just thought of something like, way stupid simple.
Just update Su before updating to 4.1. Then simply use OTA Rootkeeper like normal.
Again, I sincerely apologize for not realizing this sooner, and wasting a lot of time.
I guess I'll keep this guide here for people who forgot to update su before updating. Sorry guys.
---------------------------------------------------------------------------------------------------------------------
You might want to read this all the way through, THEN do the steps. Good Luck.
Remember to have Unknown Sources enabled.
First off, you're going to need to start off with ICS, rooted. Thats a pretty straight forward process, and can be accomplished totally with the AHD Utility (Here). Go ahead and install OTA Root keeper, we're going to need that.
After Root Keeper is installed, locate it with your favorite file manager, I prefer Root Explorer, but anything that can mount with r/w is great. It's going to be in /data/app. Copy the APK to /system/app and install it. Do this exact same thing with your file manager's APK. This way, they wont be uninstalled when we update to 4.1.
Run OTA Rootkeeper. Backup Su, and temp unroot. From here, you can upgrade to 4.1 without losing your essentials by using stock recovery to flash the 4.1 zip.
So that's finished, you're now in Jelly Bean and you decide not to read the rest of this because you think "oh i know where this is going, I flashed roms back on the atrix 4G all the time, im a PRO at this phone stuff" and you've restored root with Rootkeeper, and you're like "wat the heck, i dont have root, lying tutorial". Have no fear, we're not done yet.
In JB, open Rootkeeper and restore root from backup.
Now go update the Superuser app from Google Play (Anyone else ever call it Market still?)
Ok, almost done. If you were to go in to Superuser and update the binary, it would not work (I don't have an explanation for why, it just says Root failed. Probably since we're not actually rooted (but we have su so wtf mate)) So what we're going to need to do is go download the binary here from androidsu.com.
Extract the su binary from the zip and put it on your SD card. On your phone, using that trusty File explorer from earlier, mount the fs as r/w and put su in /system/bin. Make sure permissions are all checked EXCEPT Group Write and Others write. (I don't know if it makes a difference, but I don't want to mislead you.)
Alternatively, you can use ADB. Mount the file system as r/w on the phone. Put su on the root of your hard drive, and use " adb push c:/su /system/bin "
Then it's done. Test root from adb with " adb shell su " and from the phone by using any root app, or typing "su" in terminal emulator. Or just root checker.

Thanks for making this so easy! Updated to JB without losing anything. However, I hit a snag. Everything was okay until I tried to update su.bin via ES File Explorer. I couldn't write to system/bin, and couldn't get the app to gain root access again. Now I'm stuck with no root... Can I adb the file in, or somehow write to system/bin? Or will I have to do this all over again? I just really don't want to lose any settings.

doublea70 said:
Thanks for making this so easy! Updated to JB without losing anything. However, I hit a snag. Everything was okay until I tried to update su.bin via ES File Explorer. I couldn't write to system/bin, and couldn't get the app to gain root access again. Now I'm stuck with no root... Can I adb the file in, or somehow write to system/bin? Or will I have to do this all over again? I just really don't want to lose any settings.
Click to expand...
Click to collapse
Yes. The un-updated version of Su should be enough to give ADB root, so you can use ADB to remount the filesystem with r/w, then push the new su.
For future readers who don't know:
First, navigate to ADB in the terminal of your choice (Command Prompt on Windows, Terminal on Linux/OS X. I'll be using Windows.)
Do this by typing
Code:
cd /your directory ADB is in/
In my case, it now says "C:/Users/MyName/Desktop/ADB" because I keep ADB on my desktop like a silly person.
Now, remount your filesystem in ADB with read/write access. The command is
Code:
adb shell su mount /system rw
Now, we can push that new SU binary with ease, with
Code:
adb push c:/The_Directory_you_keep_su_in/ /system/bin
In my case, It was just "adb push c:/su /system/bin" because I keep files I want to push on the root of my hard drive, like a silly person.
Now, switch system back to read only with
Code:
adb shell su mount /system ro
All done, use Superuser app to Check for updates. It should say you're up to date, and if you update anyway, it'll do it without failing.

Is there another method to this? I have this problem idk why it says I have root saved but it won't let me restore? I don't have computer access and my root keeper says I have root?
Sent from my MB886 using Tapatalk 2

Gaining root access... fail!
ripin150 said:
Update:
Holy crap, I just thought of something like, way stupid simple.
Just update Su before updating to 4.1. Then simply use OTA Rootkeeper like normal.
Again, I sincerely apologize for not realizing this sooner, and wasting a lot of time.
I guess I'll keep this guide here for people who forgot to update su before updating. Sorry guys.
---------------------------------------------------------------------------------------------------------------------
You might want to read this all the way through, THEN do the steps. Good Luck.
Remember to have Unknown Sources enabled.
First off, you're going to need to start off with ICS, rooted. Thats a pretty straight forward process, and can be accomplished totally with the AHD Utility (Here). Go ahead and install OTA Root keeper, we're going to need that.
After Root Keeper is installed, locate it with your favorite file manager, I prefer Root Explorer, but anything that can mount with r/w is great. It's going to be in /data/app. Copy the APK to /system/app and install it. Do this exact same thing with your file manager's APK. This way, they wont be uninstalled when we update to 4.1.
Run OTA Rootkeeper. Backup Su, and temp unroot. From here, you can upgrade to 4.1 without losing your essentials by using stock recovery to flash the 4.1 zip.
So that's finished, you're now in Jelly Bean and you decide not to read the rest of this because you think "oh i know where this is going, I flashed roms back on the atrix 4G all the time, im a PRO at this phone stuff" and you've restored root with Rootkeeper, and you're like "wat the heck, i dont have root, lying tutorial". Have no fear, we're not done yet.
In JB, open Rootkeeper and restore root from backup.
Now go update the Superuser app from Google Play (Anyone else ever call it Market still?)
Ok, almost done. If you were to go in to Superuser and update the binary, it would not work (I don't have an explanation for why, it just says Root failed. Probably since we're not actually rooted (but we have su so wtf mate)) So what we're going to need to do is go download the binary here from androidsu.com.
Extract the su binary from the zip and put it on your SD card. On your phone, using that trusty File explorer from earlier, mount the fs as r/w and put su in /system/bin. Make sure permissions are all checked EXCEPT Group Write and Others write. (I don't know if it makes a difference, but I don't want to mislead you.)
Alternatively, you can use ADB. Mount the file system as r/w on the phone. Put su on the root of your hard drive, and use " adb push c:/su /system/bin "
Then it's done. Test root from adb with " adb shell su " and from the phone by using any root app, or typing "su" in terminal emulator. Or just root checker.
Click to expand...
Click to collapse
After following all the steps. When i install root checker, it is telling me i don't have root.
Below is what i got back from superuser:
Su Binary Updater
Downloading Manifest... Okay!
Parsing manifest.. Okay!
Latest version = 3.1.1
Checking installed version = 3.1.1
Upacking sutools... okay!
Checking current install path.. /system/bin/su
Downloding new binary.. okay!
Gaining root access... fail!
Any idea to help?

[Q] Can't use Adblockers...

Hello,
I'm writing this text here because i can't use some applications, like ADAWAY or ADFREE.
It appears that my system partition is not rewritable (i can saw it when i type mount | grep system in the terminal.
My ROM is actually CM11 ( the stable one) and i had the same problem with PAC ROM.
Anybody know how to fix it?
I'm rooted, i have SUPERSU, etc...
Thanks a lot !

Nogara said:
Hello,
I'm writing this text here because i can't use some applications, like ADAWAY or ADFREE.
It appears that my system partition is not rewritable (i can saw it when i type mount | grep system in the terminal.
My ROM is actually CM11 ( the stable one) and i had the same problem with PAC ROM.
Anybody know how to fix it?
I'm rooted, i have SUPERSU, etc...
Thanks a lot !
Click to expand...
Click to collapse
First thing you should try to enter in phone terminal :
su
mount -o rw,remount /system
You can also enter it in adb shell from your computer (type : adb shell, and then the command I gave.)
When you enter the command from the computer, be sure to give all the permission from your phone ( for adb and for root, they'll appear on the screen)
If this doesn't give any error your problem well be fixed. If you get a permission denied we will need to use another trick.

It looks like it didn't worked, i still have ro and not RW.
i still have ads.

For the ro problem, try reflash supersu zip and update binary
For the ads, lucky patcher have a option to patch the host file (no need the constant use of adb apps)

Nogara said:
It looks like it didn't worked, i still have ro and not RW.
i still have ads.
Click to expand...
Click to collapse
What was the output of the command?

Hello,
i took a screenshot of the terminal, i put it in the attached files.
For super SU, i already reflashed it a lot of times as the binary and it didn't work.
I don't know what happens to LuckyPatcher, i can't install it when i take it from the official website, even if i take an older version, it says that i can't open the file (.apk file, it should work, i allowed unknown sources in security settings and i have already installed some .apk)
(by the way sorry for my bad english, i'm french)

Nogara said:
Hello,
i took a screenshot of the terminal, i put it in the attached files.
For super SU, i already reflashed it a lot of times as the binary and it didn't work.
I don't know what happens to LuckyPatcher, i can't install it when i take it from the official website, even if i take an older version, it says that i can't open the file (.apk file, it should work, i allowed unknown sources in security settings and i have already installed some .apk)
(by the way sorry for my bad english, i'm french)
Click to expand...
Click to collapse
Tu as fait une faute de frappe. Le slash est collé contre System :
Code:
mount -o rw,remount /system
You made a typo in your command.

Nogara said:
Hello,
i took a screenshot of the terminal, i put it in the attached files.
For super SU, i already reflashed it a lot of times as the binary and it didn't work.
I don't know what happens to LuckyPatcher, i can't install it when i take it from the official website, even if i take an older version, it says that i can't open the file (.apk file, it should work, i allowed unknown sources in security settings and i have already installed some .apk)
(by the way sorry for my bad english, i'm french)
Click to expand...
Click to collapse
Download the apk that I uploaded for you here:
https://mega.co.nz/#!E8omUKoS!4NKB9Q_NGuvitN-eq4Fe8fVSg95uC7u0xs82k8NtXVo
And move it to /data/app ,give right permission and reboot phone and see if lucky patcher is on launcher

You can also utilize the FX File Manager application with their Root Add-On. It works perfectly and is the root management app of my choice personally. It mounts and remounts partitions easily without needing to type a single command and the interface is much better than the Root Explorer Jrummy created

xmodgames issue with supersu

Hi all,
I have SuperSU Pro 2.46 installed on a lifetab P8912.
Everything worked and I got checked with rootchecker that everything works fine.
Xmodgames also starts with the message that it has root permissions granted.
The ClashofClans mod has a problem: "Mod start fails. Please confirm XModgames is authorized with root permission".
What can I do ? Does anybody else encounter the same problem or fixed that already ?
THANKS a lot for your help,
Alecz

alecz2012 said:
The ClashofClans mod has a problem: "Mod start fails. Please confirm XModgames is authorized with root permission".
Click to expand...
Click to collapse
This should be brought to the attention of the developer of "ClashofClans" -- it might be looking for 'su' at a hard-coded path. You could test for this (and perhaps even fix the problem for you) by copying or linking '/system/xbin/su' to other common paths -- such as '/system/bin/su'.
At a terminal enter:
which su
It should reply '/system/xbin/su'.
Frank

hmm, thanks , but perhaps I didn't find the right shell to work with:
I do not have write access to that folder /system/bin
Shall I chmod 777 to that folder, at least temporary ?
Sorry for not having worked since a long time on linux..

alecz2012 said:
I do not have write access to that folder /system/bin
Click to expand...
Click to collapse
That partition is normally mounted for reading only, not for writing. Remount it as writable, copy the file, then remount as read-only again:
mount -o remount,rw /system
cp /system/xbin/su /system/bin
mount -o remount,ro /system
The SuperSU installation script will delete that copy when you flash the update again so it isn't permanent, and there is only a small chance that this is the problem.
Frank

Hi Frank,
your mount description worked fine, but still I get the error when starting the mod from xmodgames.....
Perhaps you got another tip or trick .....
THX
Alex
Frank Westlake said:
That partition is normally mounted for reading only, not for writing. Remount it as writable, copy the file, then remount as read-only again:
mount -o remount,rw /system
cp /system/xbin/su /system/bin
mount -o remount,ro /system
The SuperSU installation script will delete that copy when you flash the update again so it isn't permanent, and there is only a small chance that this is the problem.
Frank
Click to expand...
Click to collapse

alecz2012 said:
Perhaps you got another tip or trick .
Click to expand...
Click to collapse
In a terminal, run
logcat -c
Then run the application which is failing to get root; then immediately after it fails run
logcat -d > /sdcard/dump.txt
Then examine '/sdcard/dump.txt' to see if it contains an error message which might help.
Frank

Hi Frank,
done, but in the txt file it is a bunch of - at least for me - magic !
I can find lotz of krsdk stuff, looks like a former try of kingroot is still existant and might prevent something there, or perhaps that's because xmodgames is checking for kingroot ...
Really do not know .....
Anyway,
I think I am getting closer , but still the last mile to take
Frank Westlake said:
In a terminal, run
logcat -c
Then run the application which is failing to get root; then immediately after it fails run
logcat -d > /sdcard/dump.txt
Then examine '/sdcard/dump.txt' to see if it contains an error message which might help.
Frank
Click to expand...
Click to collapse

alecz2012 said:
...looks like a former try of kingroot is still existant and might prevent something there, or perhaps that's because xmodgames is checking for kingroot ...
Click to expand...
Click to collapse
That's a very reasonable guess. I assume that you rooted with Kingo Root then replaced that with SuperSU. Maybe Kingo Root is still active on your device. Maybe SuperSU did not install and the root checker found Kingo's 'su'. Take a good look at both installations and try to figure out what is there. Does the SuperSU Android application run? See if 'su' will tell you whose it is by running
su --version
Frank

Kingroot didn't work when I tried it, therefore I went through the SuperSU installation.
su --version gives me
"2.45:SUPERSU"
Best regards,
Alex
Frank Westlake said:
That's a very reasonable guess. I assume that you rooted with Kingo Root then replaced that with SuperSU. Maybe Kingo Root is still active on your device. Maybe SuperSU did not install and the root checker found Kingo's 'su'. Take a good look at both installations and try to figure out what is there. Does the SuperSU Android application run? See if 'su' will tell you whose it is by running
su --version
Frank
Click to expand...
Click to collapse

I can't see what's happening from here but the cause could very well be the incomplete KingRoot attempt. It might be that your solution is to revert to stock to remove that Kingo stuff then root again using the procedure that succeeded.
Frank

i have same problem as OP, i have moto e stock 5.0.2 rooted with supersu can anyone help me

demoakka said:
i have same problem as OP, i have moto e stock 5.0.2 rooted with supersu can anyone help me
Click to expand...
Click to collapse
Same problem with me also i really need the mod working, few other apps like freedom is working but gltools arent working

The ClashofClans mod has a problem: "Mod start fails. Please confirm XModgames is authorized with root permission".
same problem with me also..

xmodgames needs to be updated, not SuperSU.

Some problem for me with Xmod for Boom Beach. Before i updated to Android 5.0.1 it was working.
Edit: Had an old Xmod version which i installed from titanium backup. New Xmod Version fixed the problem for me.

i have this problems but i have runned root please help me

~
i have Samsung Tab 10.5 (SN-T805) .. and it has the same issue
me and one of my expert friends analyzed the application to see what is the problem, we found out that XMODGAMES doesn't check the root properly
So, if there was an expert person that can reverse engineer the application and fix this issue, that would be great
PS: we don't have time to do it, because of our final college exams, we might do it in the summer.
~

alecz2012 said:
Hi all,
I have SuperSU Pro 2.46 installed on a lifetab P8912.
Everything worked and I got checked with rootchecker that everything works fine.
Xmodgames also starts with the message that it has root permissions granted.
The ClashofClans mod has a problem: "Mod start fails. Please confirm XModgames is authorized with root permission".
What can I do ? Does anybody else encounter the same problem or fixed that already ?
THANKS a lot for your help,
Alecz
Click to expand...
Click to collapse
make ur device language tu english

My xmodgames can't work either?have you found a way to fix it?

Here is the solution How to run Xmod games in android lollipop

[Q] Trouble with R/W access

Hey all
I'm having some trouble getting r/w access back on system on my 5803 on .726 firmware.
I have root and working recovery, just no r/w on system. Every time I check system access in terminal it sits at "ro" and not "rw"
I had full access in Kitkat, but when I flashed Lollipop I seemed to have lost r/w access. I have tried updating my recovery, RICDefeat, and byeselinux, all to no avail.
I feel like I'm busy missing something completely obvious, but I can't for the life of me figure out where I'm going wrong. Can any of you fine souls help?

Can you enable r/w acces using adb?
Open command line window, type adb shell (with device connected in debugging mode), then su, then mount -o remount,rw /system.
Don't know if this works for Lollipop, but I do see other users struggling to get full r/w permissions with the latest LP firmware.
Cheers.

chris5s said:
Can you enable r/w acces using adb?
Open command line window, type adb shell (with device connected in debugging mode), then su, then mount -o remount,rw /system.
Don't know if this works for Lollipop, but I do see other users struggling to get full r/w permissions with the latest LP firmware.
Cheers.
Click to expand...
Click to collapse
It seems that I can enable that way, but it doesn't persist after a reboot. And mounting system in recovery doesn't seem to do anything either. If I try run certain things in recovery it seems like they don't really work. I can change recoveries and ROM, but things like debloating scripts don't seem to work. It's quite strange.

Can you use Script Manager from Play Store to run a script at boot to enable root access? Not the best solution but may work?
Peace

chris5s said:
Can you use Script Manager from Play Store to run a script at boot to enable root access? Not the best solution but may work?
Peace
Click to expand...
Click to collapse
I suppose I could, but that's not gonna solve my problem with flashing things in recovery

Still struggling with this :/

Download this file, run .bat and ready. No need to restart.
https://mega.co.nz/#!tcEDFD4I!hrpQZxmq2Af8BFUS-ciCYBGVpEJ1LvVn_nLb2SYqAWc

pedro5148 said:
Download this file, run .bat and ready. No need to restart.
https://mega.co.nz/#!tcEDFD4I!hrpQZxmq2Af8BFUS-ciCYBGVpEJ1LvVn_nLb2SYqAWc
Click to expand...
Click to collapse
Thanks for the suggestion, but it doesn't work.