Related
Since we currently can't write to /system while Android is running, the AdFree app is unfortunately unusable. However, here is the hosts file that the app supplies you with, so you can still put it into your phone manually.
Download the attached file, unzip it and place the hosts file on your sdcard. Then, open up a command prompt, load up your recovery menu (using the instructions in toastcfh's guide) and type:
Code:
adb shell
mount /system
mount /sdcard
cp /sdcard/hosts /system/etc/hosts
exit
Now you're AdFree
As in AD free while on the web only? Or does this block the ADs that are displayed within certain programs? Like Spare Parts for example.
VoXHTC said:
As in AD free while on the web only? Or does this block the ADs that are displayed within certain programs? Like Spare Parts for example.
Click to expand...
Click to collapse
Everytime the phone goes to download an ad, it gets blocked. So in both the browser and inside apps.
a) not development
b) i already did this thread
http://forum.xda-developers.com/showthread.php?t=695196&highlight=adfree
I'm guessing this requires root?
Also, those commands can't work AFAIK, because mount needs two arguments.
Or am I missing something here? I'm new.
I have actually had 0 problems running adfree right out of the box. Installed, ran and bam no ads. Didn't have to modify nothing through ADB.
superevilllama said:
I have actually had 0 problems running adfree right out of the box. Installed, ran and bam no ads. Didn't have to modify nothing through ADB.
Click to expand...
Click to collapse
U running 2.2? BC I see lots more adds since 2.2, it blocks some but not most.
Sent from my PC36100 using XDA App
You know, to my embarassing discovery, I never noticed (as I found this thread from google) but this is the forum specifically for EVO.
I'm running a DX (so 2.1), so that may be the problem. But still, I wouldn't think such things would be different in the OS. Guess the package it differently. Oh well. Not gonna bother rooting my toy just yet, hehe. Sorry bout the confusion.
AdFree is working perfect on CM7 nightly 23 & 25 & MikFroyo 4.5 but it does not work if you have BusyBox 1.18.3 but works perfect with BusyBox 1.17.1. I did not test other versions but I think the problem is related to BusyBox 1.18.3 by today 03/19/11.
Still there are ads running on some apps
like moneycontrol, and more.
Gregalous said:
Since we currently can't write to /system while Android is running, the AdFree app is unfortunately unusable. However, here is the hosts file that the app supplies you with, so you can still put it into your phone manually.
Download the attached file, unzip it and place the hosts file on your sdcard. Then, open up a command prompt, load up your recovery menu (using the instructions in toastcfh's guide) and type:
Code:
adb shell
mount /system
mount /sdcard
cp /sdcard/hosts /system/etc/hosts
exit
Now you're AdFree
Click to expand...
Click to collapse
earth08 said:
Still there are ads running on some apps
like moneycontrol, and more.
Click to expand...
Click to collapse
Its not updated, try absolute system tools from the Android Market. It downloads an updated script
If anyone is interested I created an app (Warning: requires ROOT) that allows you to enter one or more URLs and/or file paths and merges them and installs them as hosts. You may find the source-code here: https://code.google.com/p/android-ad-blocker/
I'll try to fix bugs for it but I can't promise I'll have time.
Edit: I made a new version because the old one had some issues transferring large files. You may find it here: http://dl.dropbox.com/u/8443626/android-ad-blocker.apk
Adfree works fine, Am I missing something? I just ran it, it updated my host file. I checked again and it said it's the latest version
Sent from my PC36100
karilofyore said:
If anyone is interested I created an app (Warning: requires ROOT) that allows you to enter one or more URLs and/or file paths and merges them and installs them as hosts. You may find the source-code here: https://code.google.com/p/android-ad-blocker/
I'll try to fix bugs for it but I can't promise I'll have time.
Click to expand...
Click to collapse
Can u help me... on how to use ur app
Sent from my °•EvO HD•°
Can u explain this process... where is the guide from toast...
Sent from my °•EvO HD•°
acme64 said:
Adfree works fine, Am I missing something? I just ran it, it updated my host file. I checked again and it said it's the latest version
Sent from my PC36100
Click to expand...
Click to collapse
x2 im confused
@ acme64 : Some people in market comments complained that it doesn't work fine anymore and it's a root app with closed source. Since it was simple to write a similar tool I did it for myself mainly.
@ Don74y3 : The way to use the application is to put a URL to a hosts file. You may use for example the one in the screenshot (I can't put the link here because of forum rules but use Google to search for "hosts file winhelp2002" and from the first link, take the address from "To view the HOSTS file in plain text form") and then click "Apply". What the program does is get that file and put it in your (rooted) Android phone. That file in turn lets the phone avoid domains that serve ads or malware. The app can take more URLs and merge them, but that's not necessary. After clicking "Apply" it is recommended to reboot the phone to make sure the changes go into effect. You will see that the pages load faster and without ads.
P.S. I'm not affiliated with the guys that make that hosts file, though I'm grateful for their work.
Unable to figure out system mount point.
Can you please help with this?
MattSkeet said:
Unable to figure out system mount point.
Can you please help with this?
Click to expand...
Click to collapse
Hi, the programs tries to figure out where the /system partition is mounted on your phone (this is because it has to switch it to read-write, put the hosts file and switch it back to read-only). I wrote the program to parse the output of the "mount" command.
Unfortunately it seems that on your phone the output is far different than what I expected. I don't know how to fix this unless you can send me the output of that command on your phone - by PM for example. To do this use adb (try to Google for how to get Android Debug Bridge) with your phone connected: run "adb shell" from a command prompt and at the shell prompt type "mount" without quotes and send me the output - at least the line that contains "/system".
Hi,
I have a different question.
I used adFree but then decided that I actually wanted see the ads on my apps.
I removed AdFree but the ads are still gone.
Is there a way to bring them back?
Hello,
This is a dead easy fix to get tethering working completely with android-wifi-tether (http://code.google.com/p/android-wifi-tether/):
UPDATE
New development version has support for this rolled in, instructions are no longer necessary:
http://code.google.com/p/android-wi...name=wireless_tether_2_0_2-pre14.apk&can=2&q=
Steps:
1. Open adb shell (start cmd.exe, run "adb shell")
2. Issue the following commands:
- "mkdir /sdcard/android.tether"
- "cat /etc/firmware/fw_bcm4329_ap.bin > /sdcard/android.tether/fw_bcm4329.bin"
3. Download and install the android-wifi-tether application, start tethering.
Your log from android-wifi-tether should look like the attached image.
Happy configuration free tethering!
NOTE: This works because of the two separate firmwares that HTC has included in /etc/firmware. One is specific for AP-mode and must be more open to this kind of stuff. The original bug stemmed from the usual firmware dropping ARP requests pretty consistently, possibly as a powersaving measure.
The second firmware is loaded using the firmware_path option when loading the bcm4329.ko kernel module.
anyone else confirm this working please.
I confirm this working...
You will need to have root to run the app of course but 2 or 3 people have confirmed it on bug 362 already on the google project.
Not working for me
AWESOME!!!
actually i ever use wifi tether but this is pretty cool because it actually worked. i know on the heroC we had issues with wifi tether all of a sudden not wrking after 2.1. nice to see that its been fixed. good work spreading the word
ya. it will get SU permissions,
i can find the connection.
i connect to it. but no data transmitting.
would be cool if someone can confirm 4g is able to be tethered.
fdot said:
ya. it will get SU permissions,
i can find the connection.
i connect to it. but no data transmitting.
Click to expand...
Click to collapse
same here. any ideas?
toastcfh said:
would be cool if someone can confirm 4g is able to be tethered.
Click to expand...
Click to collapse
Not confirming but based on what I read harry_m stated the wifi tether app uses the current connection, so in theory if you switch between 3g and 4g the app will switch accordingly.
i can confirm
I originally flashed with toast's rom. Used the recovery .bat to install Flipz's stock root rom.
I then flashed toast's radio rom.
wifi tether did NOT work.
I then performed the above instructions, and viola, it works fine. (i am posting via wifi tether)
I want to thank everyone who is hard at work on these projects, you guys are awesome.
fdot said:
ya. it will get SU permissions,
i can find the connection.
i connect to it. but no data transmitting.
Click to expand...
Click to collapse
Check that the log screen looks exactly like mine does. Did you get any errors when you issued the adb commands?
Look on your sdcard for the android.tether folder and see if fw_bcm4329.bin file exists there.
toastcfh said:
would be cool if someone can confirm 4g is able to be tethered.
Click to expand...
Click to collapse
dcmtnbkr said:
same here. any ideas?
Click to expand...
Click to collapse
It should work according to one of the comments given about the issue. http://code.google.com/p/android-wifi-tether/issues/detail?id=362#c36
Because I am weary of rooting my phone not being able to return it to stock, I am gonna try it with the unrevoked root first.
goodfellaslxa said:
I originally flashed with toast's rom. Used the recovery .bat to install Flipz's stock root rom.
I then flashed toast's radio rom.
wifi tether did NOT work.
I then performed the above instructions, and viola, it works fine. (i am posting via wifi tether)
I want to thank everyone who is hard at work on these projects, you guys are awesome.
Click to expand...
Click to collapse
i followed this same exactly.
andrew500 said:
Check that the log screen looks exactly like mine does. Did you get any errors when you issued the adb commands?
Look on your sdcard for the android.tether folder and see if fw_bcm4329.bin file exists there.
Click to expand...
Click to collapse
no errors in adb.
and the .bin file is sitting in the directory.
and the log looks like yours.
running toasts ROM
can't get this to work
followed instructions, and when i click on the tether button it instantly says: unable to start tethering, please try again!
log screen is completely blank
any ideas?
fdot said:
i followed this same exactly.
no errors in adb.
and the .bin file is sitting in the directory.
Click to expand...
Click to collapse
I meant the screen in android-wifi-tether, does it look like the screen cap I included? It should have a debug line about the loaded firmware on the first item.
- Didn't see the edit you made with that screen:
Have you done the OTA update? Could be the SD card bug possibly. The log screen shows it didn't load the external firmware.
"Unable to start teterhing try again"
I skimmed this thread, I am using toast's rom.
I have just applied the Unrevoked root. I cannot access the sdcard via adb shell. Any ideas?
When i send command
"cat /etc/firmware/fw_bcm4329_ap.bin > /sdcard/android.tether/fw_bcm4329.bin"
it gives me error msg
"cannot creat /sdcard/android.tether/fw_bcm4329.bin: directory nonexistent"
i followed this same exactly.
no errors in adb.
and the .bin file is sitting in the directory.
Click to expand...
Click to collapse
I meant the screen in android-wifi-tether, does it look like the screen cap I included? It should have a debug line about the loaded firmware on the first item.
- Didn't see the edit you made with that screen:
Have you done the OTA update? Could be the SD card bug possibly. The log screen shows it didn't load the external firmware.
Click to expand...
Click to collapse
I have not done the ota.
-------------------------------------
Sent via the XDA Tapatalk App
Well I know I'm not the only one who got a bad WiMax MAC address after trying to update my WiMax radio image. I should learn to not try and fix things if they aren't broken
If you've gotten the dreaded "00:16:08:00:24:05" MAC address like I did, this guide will help you fix it. You'll need fastboot set up, a NAND unlocked phone with Toast's part 2 method, your correct MAC address for WiMax, and the files below.
FILES:
New radio
New WiMax
You MUST download & flash these again even if you already have. I don't care if you think you already have the right ones, download these. If you don't, don't ask me for help if you use the wrong ones.
STEP 1: Fix MAC
First, get your right MAC address. It can be found under the battery by the WiMax tag, or on your box under the WiMax barcode. It should be 12 digits long, with no colons in it. If it were supposed to be "00:16:08:00:24:05" it would look like 001608002405 on the box. Write that address down with a colon between every two characters to get it in the right format.
Next, boot your phone into fastboot mode. If you don't know how to do this, hold down volume and press power to boot into the bootloader. After it brings up the menu where "FASTBOOT" is highlighted, press power. It should say "FASTBOOT USB" in red where it previously said "HBOOT" in green.
On your PC, open a shell. First off, lets see if you have a bad MAC, run
Code:
fastboot oem wimaxrmac
It should return something like
Code:
INFOcmd_wimaxrmac
INFODev MAC = *Your MAC address will be here*
OKAY
If it doesn't match the code you wrote down, then you have a bad MAC. If it does match the code you wrote, then skip to step 2.
To fix it, you need to run:
Code:
fastboot oem wimaxwmac *Address you wrote down here*
Like if you wanted it to be "00:16:08:00:24:05" then you would run:
Code:
fastboot oem wimaxwmac 00:16:08:00:24:05
It should return something like:
Code:
INFOcmd_wimaxwmac
IFNOWrite OK! MAC = *Address you entered here*
OKAY
Then just run
Code:
fastboot reboot
To reboot back into Android with your correct MAC address.
STEP 2: Flash the images again
Now push those files to your SD card & reboot into recovery.
Once you're in recovery, flash the "evo.2.05.00.06.10.zip" file. Reboot from the menu like it tells you. Once you're in Android, update your Profile & update your PRL.
Now reboot into recovery again, this time flash the "evo.wimax.25641_r01.zip" file. Reboot again from the menu, and guess what. Once again, update your Profile & PRL. Reboot one more time for good measure, and you should have working 4G. I haven't been able to confirm 4G myself, but others have reported it working with my method. My logcat no longer shows any 4G errors and neither does the kernel log, plus all the data now matches how it was before my update, so that leads me to believe it's working.
I wrecked my MAC with the update and fixed it like this, but I haven't had a chance to try out 4G yet since I won't be going into the city where I'll have coverage until Saturday.
Please post here if it works for you or if it isn't clear then just post & I'll try and clear it up.
Regards,
Jesse C.
EDIT: As a few posters had trouble, it came to my attention that you MUST have run Toast's root part 2 image to have access to fastboot oem commands.
EDIT 2: Now full 4G fix.
Thank you so much!
Sent from my PC36100 using XDA App
On it.....!!!!
It's possible this may only update the MAC and not the key, Joshua (unrevoked) told me and a few others that was their main issue.
Let's see what results show.
Hot damn!!!! It works!!!
Neotelos_com said:
It's possible this may only update the MAC and not the key, Joshua (unrevoked) told me and a few others that was their main issue.
Let's see what results show.
Click to expand...
Click to collapse
If it really is the key, we can modify that here too. If we can pull a copy off a working device, we can write it with fastboot too I'm pretty sure
Geniusdog254 said:
If it really is the key, we can modify that here too. If we can pull a copy off a working device, we can write it with fastboot too I'm pretty sure
Click to expand...
Click to collapse
My understanding is the key is specific to each MAC, either way someone reported it works.
We just need people to post their before and after MAC address to confirm.
It does seem there are two variations of the bad MAC from different roms (at least from reports I've heard).
Well i changes the mac....i dont know if 4G is working on it.....
ON XP opening a shell using CMD? I'm not sure how to communicate with my EVO. Been without 4G for a while, trying to get it back up and running.
( waiting for device )
*nevermind*
Sleep..needed badly
Travyevo said:
ON XP opening a shell using CMD? I'm not sure how to communicate with my EVO. Been without 4G for a while, trying to get it back up and running.
Click to expand...
Click to collapse
You need adb from the Android SDK.
You also need to set your phone for USB debugging.
If you look around there's hundreds of tips on doing all this.
asrebel said:
*nevermind*
Sleep..needed badly
Click to expand...
Click to collapse
are you in fastboot?
Neotelos_com said:
My understanding is the key is specific to each MAC, either way someone reported it works.
We just need people to post their before and after MAC address to confirm.
It does seem there are two variations of the bad MAC from different roms (at least from reports I've heard).
Click to expand...
Click to collapse
I saw the same thing. I ended up with the one i posted in the OP but it seems they all start with the 00:16:08 characters.
I don't think its safe to post the after MAC address, sicne it's unique to every device. It won't hurt anything, but I'd rather keep mine private
Neotelos_com said:
You need adb from the Android SDK.
You also need to set your phone for USB debugging.
If you look around there's hundreds of tips on doing all this.
Click to expand...
Click to collapse
ADB appeared to install when i connected it. I'll take a look.
Thanks
my fastboot doesn't seem to recognize the 'oem' command. Is that a function of fastboot?
Anyone 4G back working using this method?
rocolema said:
my fastboot doesn't seem to recognize the 'oem' command. Is that a function of fastboot?
Click to expand...
Click to collapse
Yes. It should work for everyone. Do you have the newest fastboot?
david279 said:
Anyone 4G back working using this method?
Click to expand...
Click to collapse
I thought you said you had it working? Do you not have 4G or did it not fix the 4G errors
It fixed my MAC address. I have no 4G to test to see if thats working.
This is an interesting method.
I have restored my MAC via a different route, but I believe if I were to flash an offical wimax right now, I would lose my MAC again. What I have done requires modification to the wimax.img file.
Does this persist through reboots? If it does, this would likely be the best answer to the problem of the bad mac addresses.
david279 said:
It fixed my MAC address. I have no 4G to test to see if thats working.
Click to expand...
Click to collapse
Ah okay. I'm in the same boat
I have this really odd issue with my Z3 in that I cannot, on any network (wireless or carrier), resolve through DNS forum.xda-developers.com. I first noticed it because my XDA premium HD app couldn't connect to the forums at all. I did a bit of digging and managed to uncover that I can't connect to anything related to the forums. I CAN however connect to the main portal on www.xda-developers.com.
What I have tried:
1. Different wireless networks - no luck.
2. Other devices - all work fine on all the tried networks.
3. Carrier network (Rogers CA) - no luck, but again with other devices no problem
4. Ping and nslookup through Fing network tools - not able to resolve
5. Ping and nslookup through terminal emulator - not able to resolve
6. hosts file just has the standard localhost entry
7. Browse with Chrome just gives the standard error for unresolvable DNS
8. So far I have only seen this happen on the forums.xda-developers.com address.
I am running a Z3 (D6603) with a custom ROM per below.
Pre-rooted ROM from this thread: http://forum.xda-developers.com/z3/general/d6603-5-0-2-flashable-stock-23-1-0-690-t3056361
D6603_23.4.A.0.546_Customized_US_SuperSU_XZDR2.8.2 1 thanx to @julianbl
It's an odd one for sure, so if anyone has any creative ideas for me to test out please let me know. Thanks in advance.
use titanium backup or something similar to disable/uninstall "PrototypeProtection".
It's an app that sony uses to block certain sites when the bootloader is unlocked.
Julián
Go in Root Explorer,
Mount in R/W
Go to: system/etc/hosts
Try to add a xdadevs rule,
examp:
#207.244.72.9 http://forum.xda-developers.com
then reboot your device just normal.
i hope it works,
- bram
julianbl said:
use titanium backup or something similar to disable/uninstall "PrototypeProtection".
It's an app that sony uses to block certain sites when the bootloader is unlocked.
Julián
Click to expand...
Click to collapse
I should note that I have not unlocked my bootloader. I tried this and it has unfortunately had no effect. Open to other suggestions though, thanks for trying.
[EDIT] I may have spoken too soon. I tried connecting after disabling (freezing) that app and didn't have any luck. I rebooted the phone, and things are back online. I will do some further testing to get concrete and repeatable behavior documented. Thanks @julianbl
bramybram said:
If you see a rule wiht xda-developers.com in it
Click to expand...
Click to collapse
Thank for the suggestion. As noted in my OP though, the hosts file is empty except for the default localhost entry.
Swaziboy said:
Thank for the suggestion. As noted in my OP though, the hosts file is empty except for the default localhost entry.
Click to expand...
Click to collapse
Try to add a XDA Rule with a "#" before the rule instead?
bramybram said:
Go in Root Explorer,
Mount in R/W
Go to: system/etc/hosts
Try to add a xdadevs rule,
examp:
#207.244.72.9 http://forum.xda-developers.com
then reboot your device just normal.
i hope it works,
- bram
Click to expand...
Click to collapse
bramybram said:
Try to add a XDA Rule with a "#" before the rule instead?
Click to expand...
Click to collapse
Thanks for your desire to help - given what we've found out so far this isn't a HOSTS file issue. There is no entry in the hosts file, and as such any DNS resolution for the domain should leverage DNS servers based on DHCP settings.
In my mind, adding a rule in the HOSTS file to force resolution of the domain, might work but it's not a real fix as to why this is happening.
Refer to my previous note that the suggestion to block the "PrototypeProtection" app is what has resolved the issue so far.
Thanks again though @bramybram, appreciate your willingness to help.
Hey there, I had the same issue... It is quite frustrating, I guess it's some bug in the firmware you installed (since I used the same to flash my z3)... I resolved it by flashing another firmware, I suggest you the D6603_23.4.A.0.546_Customized_NCB_SuperSU_XDR2.8.2 1 (https://mega.co.nz/#!GJQVBL6K!x8bB2HS-TbpbZTb5IamrJB_xduDMHl9j6jQyAqrJpVQ) one, it worked for me
Hi everyone.
I don't know why i have this "module". Only install the other one and nothing more.
I try to delete it then restart phone but it doesn't go away.
Not a problem, just aesthetic
That's weird....
If you are bothered and you don't mind re-installing/re-flashing all your modules again, you could try the adb command
Code:
adb wait-for-device shell magisk --remove-modules
and that should remove all your modules including that unknown weird one.
Also, if for whatever reason that doesn't work, I read somewhere that Magisk has its data folder outside of the internal storage folder and is more in the root data folder -- so if one wiped their phone, all the Magisk data (deny list i imagine, on top of modules) would still survive -- and you might consider finding and deleting that folder and reinstall/re-flash Magisk. CAUTION: I imagine this has a chance of bringing up some glitches or bugs (incompatibilities) when the app connects-to/works-in-conjuction-with the patched init_boot.
If you are still sure you wish to do that, I believe I found the folder which I put in spoilers below...
Spoiler: Magisk root folder
root: /data/adb
These are just a couple of ideas...hope it helps...
Thx for your help !
The adb command works.
Plathoon said:
Thx for your help !
The adb command works.
Click to expand...
Click to collapse
I also have the same problem.... ".core" and i cannot delete it...its like a bug or something like that?
Plathoon said:
Thx for your help !
The adb command works.
Click to expand...
Click to collapse
Hello, I have the same problem where I have to apply those lines, in the bootloader, recovery? I tried both and neither worked. Thank you in advance
is this the official version downloaded from an official source? check the magisk forum
febo17 said:
Hello, I have the same problem where I have to apply those lines, in the bootloader, recovery? I tried both and neither worked. Thank you in advance
Click to expand...
Click to collapse
sorry for the very late reply...been a busy couple of weeks and am only catching up on things now...I'm fairly positive you figured it out already, but in case you haven't and/or any other person reading this looking for the answer...
I've never used the line before, but as I understand it, after turning off your phone and before connecting your phone to the computer, open up the cmd and run the command when you've changed the directory to the platform-tools folder. I believe the "wait-for-device" part has it running but on standby to activate once you plug your phone to the computer and it powers on (and tries to load up)...
I imagine once it does, it'll run the command and is executed before it goes any further loading up the module that is causing the issue/bootloop...
Hopefully I am correct and this helps...
simplepinoi177 said:
sorry for the very late reply...been a busy couple of weeks and am only catching up on things now...I'm fairly positive you figured it out already, but in case you haven't and/or any other person reading this looking for the answer...
I've never used the line before, but as I understand it, after turning off your phone and before connecting your phone to the computer, open up the cmd and run the command when you've changed the directory to the platform-tools folder. I believe the "wait-for-device" part has it running but on standby to activate once you plug your phone to the computer and it powers on (and tries to load up)...
I imagine once it does, it'll run the command and is executed before it goes any further loading up the module that is causing the issue/bootloop...
Hopefully I am correct and this helps...
Click to expand...
Click to collapse
in fact I had already applied that line and it didn't work either in fastboot or in ell recovery. It worked for me, to my surprise, with the phone on. all modules were deleted
What version of Magisk are you using, and where did you download it from?