Related
I have a rooted HTC One, running stock rom. I installed ad block but it also blocks any MMS sending and receiving. Is there a work around for this? Or another ad block program that would be useful? I also noticed ad block is using majority of my data. I assume that is ads that it is blocking. Is there a way to get them to not even load? ie. not use any bandwidth blocking ads?
I use Ad Away. It doesn't actually do any active blocking itself, it merely reroutes any requests to ad sites to localhost, so it comes up blank. Uses absolutely nothing in terms or resources that I'm aware of it, and has no effect on messages.
May I ask where you got the ad away zip file? All I can find is the apk.
Dude instal apk ,run it ,instal host ,no ads voila.
It's hosted on F-Droid now that it's booted from play.
Make sure to have your system partition writable
Sent from my HTC One using xda app-developers app
There's also ad block plus.
http://db.tt/qNnY4Q2i
Extract that to system/etc and reboot.
Done.
Hey, I have the HTC One Dev Edition and it is telling me that I need to ROOT the phone. I thought all these phones were already factory "rooted" or is bootloader unlocked not the same as "rooted" ?
schn1tt3r said:
Hey, I have the HTC One Dev Edition and it is telling me that I need to ROOT the phone. I thought all these phones were already factory "rooted" or is bootloader unlocked not the same as "rooted" ?
Click to expand...
Click to collapse
Nope, an unlocked bootloader just gives you the access to root
ArmedandDangerous said:
Nope, an unlocked bootloader just gives you the access to root
Click to expand...
Click to collapse
I see, time to follow youtube vid. So far, as an iOS to Android convert, Ads is the one thing that is making me want to go back to iOS. On iOS, I just installed Cydia and then adblock from sources. Gotta make this AdAway 2.3 work and I think I will have no more complaints.
Apologies if this is blindingly obvious, but I've googled and searched and have found a lot of conflicting information this, so bear with me:
I went through the Moto bootloader unlock process for my Rogers Moto X and when I boot into fastboot it says it's unlocked. I then installed SuperSU and it seems to be working when I launch apps that require SU access. And some sites say if I'm on 4.4.3 it's impossible to make /system writeable. Basically, I'm still unable to install stuff that writes to /system like Busybox.
I've read about how /system is write-protected but haven't figured out how to actually fix this - some posts say start in recovery and I should be able to write to /system, others say it should work after I've gone through the Moto bootloader unlock process.
Can anyone here help a rsomewhat-newb get this sorted?
neil.io said:
Apologies if this is blindingly obvious, but I've googled and searched and have found a lot of conflicting information this, so bear with me:
I went through the Moto bootloader unlock process for my Rogers Moto X and when I boot into fastboot it says it's unlocked. I then installed SuperSU and it seems to be working when I launch apps that require SU access. And some sites say if I'm on 4.4.3 it's impossible to make /system writeable. Basically, I'm still unable to install stuff that writes to /system like Busybox.
I've read about how /system is write-protected but haven't figured out how to actually fix this - some posts say start in recovery and I should be able to write to /system, others say it should work after I've gone through the Moto bootloader unlock process.
Can anyone here help a rsomewhat-newb get this sorted?
Click to expand...
Click to collapse
You flashed the latest version of TWRP custom recovery?
samwathegreat said:
You flashed the latest version of TWRP custom recovery?
Click to expand...
Click to collapse
Think so - this was the image file I used: twrp-2.6.3.1-ghost-4.4.img
neil.io said:
Think so - this was the image file I used: twrp-2.6.3.1-ghost-4.4.img
Click to expand...
Click to collapse
That might be the issue. It might not be compatible with 4.4.3
Try this one: http://techerrata.com/browse/twrp2/ghost
Also, which version of SuperSU are you using? There was a new one released recently. Find it here: http://download.chainfire.eu/451/SuperSU/UPDATE-SuperSU-v2.01.zip (Flash it from within TWRP - install ZIP)
Please update, and then advise whether or not your issue is resolved.
EDIT: Also, make sure you are using the "stericson" busybox variant. Others have been reported to cause issues.
Thanks a lot for the fast responses - really appreciated.
I redid recovery using the version you linked to and also reinstalled SuperSU (I was using the current version already). When I try to install Busybox using the Stericson version as you mentioned I get an immediate error that it wasn't able to open a shell w/ root access. Running Root Checker tells me that root access is working, so I'm not sure what I've missed.
Again, many thanks!
neil.io said:
Thanks a lot for the fast responses - really appreciated.
I redid recovery using the version you linked to and also reinstalled SuperSU (I was using the current version already). When I try to install Busybox using the Stericson version as you mentioned I get an immediate error that it wasn't able to open a shell w/ root access. Running Root Checker tells me that root access is working, so I'm not sure what I've missed.
Again, many thanks!
Click to expand...
Click to collapse
Open SuperSU, and check to see if busybox is listed under apps. There should be a green "#" symbol next to it. It SHOULD have prompted you to grant access to it, so perhaps at some point you either denied the su request, or didn't see it. If you see a RED "#" symbol, tap it, and change to "Grant".
Please advise...
It is, and it did have a green # beside it. I tried removing it and it requested permission as expected, but still failed.
I can't seem to get anything to install to system - Adaway also fails, for example.
neil.io said:
It is, and it did have a green # beside it. I tried removing it and it requested permission as expected, but still failed.
I can't seem to get anything to install to system - Adaway also fails, for example.
Click to expand...
Click to collapse
I would suggest a full return to stock (follow the return to stock thread in the general sub-forum). This is not normal....
You appear to be using the XT1053, correct? Take caution to NOT downgrade or you could end up with a brick.
Flashing the entire stock SBF can actually fix a corrupted filesystem - this is my best guess at what might fix your issue.
samwathegreat said:
Flashing the entire stock SBF can actually fix a corrupted filesystem - this is my best guess at what might fix your issue.
Click to expand...
Click to collapse
Thanks again for the help. I just flashed the stock SBF and that seems to have fixed whatever was blocking Adaway from properly writing its hosts file, but Busybox stubbornly refuses to install. I got the permission request for SU when I launched it, but it fails just after I initiate the install. I tried changing the location to /system/bin with no luck.
Any other suggestions? I'm ready to give up for now, but it's frustrating when my Nexus 4 was so simple to set up.
neil.io said:
Thanks again for the help. I just flashed the stock SBF and that seems to have fixed whatever was blocking Adaway from properly writing its hosts file, but Busybox stubbornly refuses to install. I got the permission request for SU when I launched it, but it fails just after I initiate the install. I tried changing the location to /system/bin with no luck.
Any other suggestions? I'm ready to give up for now, but it's frustrating when my Nexus 4 was so simple to set up.
Click to expand...
Click to collapse
How did you SBF to stock? Did you use RSD Lite? Did you retain userdata, or wipe everything (suggested)?
The stericson variant installs fine for me...granted I'm on 4.4.2 (the latest for my variant).
I did NOT use smart install...just used regular install to /system/xbin (You might consider trying smart install if you haven't yet...)
Honestly, I'm out of ideas. Although the "stericson" variant is recommended, perhaps you should try another version from the market if you need busybox.
I've done extensive searches and haven't found anyone else having a similar issue - even with Moto X on 4.4.3
I gave up and used the recovery method. Really odd - it does seem like the other installer apps couldn't mount /system as writeable, but it's weird that other apps that installed to that area worked.
Anyway, thanks again!
So I successfully unlocked and rooted my phone with various methods because Boost Mobile didn't make it easy, and then managed to root via TWRP,
The reason why I rooted the phone is because I want to remove bloatware like Connection Optimizer and Boost Zone.
I got a hold of a root explorer copy and managed to delete the .apk files with their respective helping files.
On top of that, I got another application to remove the installed apps and it worked.
So, after a while of using the phone without a hassle, it just randomly turns off.
And when I boot it up again, the apps are back and more annoying than before.
I have no idea how to change folder permissions (I forgot, I did it once on LG Venice but that was a while ago)
And I really need help, the bloatware takes up to 2gb and its annoying with the constant bombardment of notifications.
Please, if you can, HELP ME.
CHR$+RND said:
So I successfully unlocked and rooted my phone with various methods because Boost Mobile didn't make it easy, and then managed to root via TWRP,
The reason why I rooted the phone is because I want to remove bloatware like Connection Optimizer and Boost Zone.
I got a hold of a root explorer copy and managed to delete the .apk files with their respective helping files.
On top of that, I got another application to remove the installed apps and it worked.
So, after a while of using the phone without a hassle, it just randomly turns off.
And when I boot it up again, the apps are back and more annoying than before.
I have no idea how to change folder permissions (I forgot, I did it once on LG Venice but that was a while ago)
And I really need help, the bloatware takes up to 2gb and its annoying with the constant bombardment of notifications.
Please, if you can, HELP ME.
Click to expand...
Click to collapse
Have you flashed a kernel with write protection removed? http://forum.xda-developers.com/showpost.php?p=57174863&postcount=1
I've got the BOOST as well and that kept the bloatware off but occasionally they will try and re-download from the Play Store so I had to turn automatic updating of apps off and update apps manually as they come.
EDIT: I was waiting for my new user time limit to submit this. Didn't see the exact same answer posted above. That kernel worked for me (Boost 510). The later ones with performance enhancements did not. I am now bloat free.
emaggot said:
EDIT: I was waiting for my new user time limit to submit this. Didn't see the exact same answer posted above. That kernel worked for me (Boost 510). The later ones with performance enhancements did not. I am now bloat free.
Click to expand...
Click to collapse
I have that already flashed, that's the one I posted. I've now got just a base system by uninstalling EVERYTHING you can imagine. I'm just saying occasionally it would try and re-download some apps but now I've got automatic updating turned off it doesn't do it anymore.
dipspit said:
Have you flashed a kernel with write protection removed? http://forum.xda-developers.com/showpost.php?p=57174863&postcount=1
I've got the BOOST as well and that kept the bloatware off but occasionally they will try and re-download from the Play Store so I had to turn automatic updating of apps off and update apps manually as they come.
Click to expand...
Click to collapse
This method didn't work out, every time I do the command it either doesn't go through or fastboot stops responding.
CHR$+RND said:
This method didn't work out, every time I do the command it either doesn't go through or fastboot stops responding.
Click to expand...
Click to collapse
Your phone has to be in FASTBOOT not the os, but I assume you know that. Try adb kill-server and then adb start-server and then do the fastboot flash boot b.img or turn the computer off and turn it back on and try again. I've had this problem a couple times, these two methods worked.
dipspit said:
Have you flashed a kernel with write protection removed? http://forum.xda-developers.com/showpostphp?p=57174863&postcount=1
I've got the BOOST as well and that kept the bloatware off but occasionally they will try and re-download from the Play Store so I had to turn automatic updating of apps off and update apps manually as they come.
Click to expand...
Click to collapse
I did this and it worked. However, the ability to change cameras is now missing. I had an option where I could change to front camera and now no camera app I get gives me the option to switch.
CHR$+RND said:
I did this and it worked. However, the ability to change cameras is now missing. I had an option where I could change to front camera and now no camera app I get gives me the option to switch.
Click to expand...
Click to collapse
Yeah, the dev's are looking into it. It's a known issue.
Hey Guys,
I have an original (2013) Moto X 1060 (Verizon) that I rooted using this method. http://forum.xda-developers.com/moto-x/general/moto-x-root-pogress-60-t3071602 It's been working great with no problems until today when my phone decided to update my google wallet app to the new android pay. Whenever I try to add a card to android pay I'm getting the error "Android Pay Cannot be used...... Google is unable to verify that your device or the software running on it is android compatible."
Googling has led me t believe that this is an error related to the app detecting root. I tried both of these methods, but neither has worked. http://bit.ly/1LnwzAZ http://bit.ly/1LnwEog . I've tried each separately with rebooting in between as well as trying them together all to no avail.
Other than following the guide above the only root-related things I have modified on the phone are the removal of some verizon apps via titanium backup and adding the following xposed module: "NoSafeVolumeWarning".
One thing that I noted was when I uncheck "Enable Superuser" inside of SuperSu 2.46 it displays a message saying "Uninstall Failed !" It still displays the "Superuser is disabled and hidden" underneath the box and if i enable it again and disable it it does not pop up with the uninstall failed message. Does this have something to do with write protection?
Any help would be greatly appreciated!
Thanks,
Adam
johnnyboy239 said:
Hey Guys,
I have an original (2013) Moto X 1060 (Verizon) that I rooted using this method. http://forum.xda-developers.com/moto-x/general/moto-x-root-pogress-60-t3071602 It's been working great with no problems until today when my phone decided to update my google wallet app to the new android pay. Whenever I try to add a card to android pay I'm getting the error "Android Pay Cannot be used...... Google is unable to verify that your device or the software running on it is android compatible."
Click to expand...
Click to collapse
Having the exact same issue. Just upgraded to 5.1 today, xposed Rootcloak as well as No Device Check installed. Also tried Disable SU. Still get the same issue.
Same. I tried uninstalling SU, Hide My Root, and Rootcloak...nothing has worked. Found out today that the app updated when I went to buy something at Walgreen's. How ****ing embarrassing is that?
So I have not yet found a solution to this and am still hoping someone has one. In the mean time, you can install this app http://www.apk4fun.com/share/7185/ (doesn't need to be from this site, it's just an old version of google wallet, and the one I used), go into settings>apps>google play services>manage data clear all data, and reboot. I just tried it at cub foods and it worked fine, but of course you do have to go into the app first, and I had to disconnect it from the app store with titanium backup so it wouldn't update to android pay again.
Was able to get Amex card working after uninstalling Xposed. However, I think I'm going to pass on Android Pay until they allow pin codes on the app, not the phone.
Same problem, few apps frozen with TiBu and xposed installed. Any other work around? s
johnnyboy239 said:
So I have not yet found a solution to this and am still hoping someone has one. In the mean time, you can install this app http://www.apk4fun.com/share/7185/ (doesn't need to be from this site, it's just an old version of google wallet, and the one I used), go into settings>apps>google play services>manage data clear all data, and reboot. I just tried it at cub foods and it worked fine, but of course you do have to go into the app first, and I had to disconnect it from the app store with titanium backup so it wouldn't update to android pay again.
Click to expand...
Click to collapse
check to see if your phone allows pin codes to be deactivated at times. I have mine set to not be used at home work and if I am carrying the phone. It is quite useful feature in settings Lockscreen but I am on COS 12.1 OnePlus basically CM
I haven't tried it yet, but I think they only way we'll get this working on root is to install it on stock unrooted, back it up with TiB or Helium, root and then reinstall/restore.
Lots of fail here as well. All the tricks you all listed + some others. It seems there is a lack of consistency for those that resolved. Some just say disabling root, uninstall busybox, uninstall xposed, rootcloak, device checker for play services, etc.
Nothing yet has worked for me. Luckily I backed up Wallet just before taking the update, so I may go back until the community has a solution.
Ezekial said:
Lots of fail here as well. All the tricks you all listed + some others. It seems there is a lack of consistency for those that resolved. Some just say disabling root, uninstall busybox, uninstall xposed, rootcloak, device checker for play services, etc.
Nothing yet has worked for me. Luckily I backed up Wallet just before taking the update, so I may go back until the community has a solution.
Click to expand...
Click to collapse
I'm in the same boat. Couldn't get AP to work. Just loaded up the previous version of Wallet. Now have two wallet apps, but whatever. Both appear to be working.
Has anyone tried to get Android Pay working by re-locking the bootloader and temp unrooting on a Nexus device (say, a tablet), then getting AP up and running, and then checking to see if it was usable on your other device(s)??....I was curious if Android Pay would work on ALL of your devices once it was set up properly. Working with lock, unlocking, rooting, etc. is much easier on a Nexus than it would be to work on a Moto, or similar.
Does this make any sense?
KenNashua said:
Was able to get Amex card working after uninstalling Xposed. However, I think I'm going to pass on Android Pay until they allow pin codes on the app, not the phone.
Click to expand...
Click to collapse
Tried AP for the first time at Panera today and failed...seems even with Root Cloak on AP and Google Play Service as well as No Device Check, it still fails.
Hello -
I followed the three video tutorial on how to get rid of the Amazon ads, stop OTA updates. That worked fine.
I have been loading up apps when I noticed that one of the apps could not work cause it needs root access. Root Checker showed my phone was not rooted.
Confused cause I thought I rooted, then followed the videos exactly to get rid of the ads, finalized by doing a factory reset.
Any ideas? Should I just try to root the again? Follow video 1? I do have TWRP installed.
Thanks
Kannon
kannonman said:
Hello -
I followed the three video tutorial on how to get rid of the Amazon ads, stop OTA updates. That worked fine.
I have been loading up apps when I noticed that one of the apps could not work cause it needs root access. Root Checker showed my phone was not rooted.
Confused cause I thought I rooted, then followed the videos exactly to get rid of the ads, finalized by doing a factory reset.
Any ideas? Should I just try to root the again? Follow video 1? I do have TWRP installed.
Thanks
Kannon
Click to expand...
Click to collapse
Start over here...
http://forum.xda-developers.com/r1-hd/how-to/guide-convert-to-prime-rollback-ota-t3432499
kannonman said:
Hello -
I followed the three video tutorial on how to get rid of the Amazon ads, stop OTA updates. That worked fine.
I have been loading up apps when I noticed that one of the apps could not work cause it needs root access. Root Checker showed my phone was not rooted.
Confused cause I thought I rooted, then followed the videos exactly to get rid of the ads, finalized by doing a factory reset.
Any ideas? Should I just try to root the again? Follow video 1? I do have TWRP installed.
Thanks
Kannon
Click to expand...
Click to collapse
if twrp is still installed, go download latest supersu from chainfire's website, install the zip from twrp. simple.