So, I just rooted using Towelroot and root is working, but Adaway cannot apply the hosts file...ever.
Is it because I didn't unlock the bootloader? Or is this like the HTC One which requires S-Off before it can overwrite system files? This is my first Asus and I haven't seen anything on this.
For the time being, I have Adfree working, but I'd just like to know why I can't use Adaway.
Scratch that. I'm good. After a reboot, Adaway seems to be working fine.
greyhulk said:
Scratch that. I'm good. After a reboot, Adaway seems to be working fine.
Click to expand...
Click to collapse
For me, Adaway has been acting kind of strange for the last couple of weeks where it just spins and spins and never updates or I get some error message. Prior to that, it was pretty solid. Perhaps there are server issues somewhere.
Related
When I installed Xposed, everything seemed to be in order aside from a subjectively longer reboot than normal. The only module I have installed (and the only reason atm for me having Xposed installed) was to kick the pesky ISIS app past the "Your phone is rooted" message. Both apks were downloaded from XDA as well. After several unbearably long freezes and general sluggishness reminiscent of my Evo 3D, I ended up uninstalling ISIS as well as Xposed which returned my phone to its normal speedy operation. It should be noted however that while it was runny slow and freezing, ISIS did function properly and allowed me to add things as if I weren't rooted. I'd be more than happy to re-install and try again, but I thought I'd pick the brains of the big wigs here first and see if anyone had any thoughts before I do so. Also if it matters, my GS5 is the T-Mobile version.
darkavalanche said:
When I installed Xposed, everything seemed to be in order aside from a subjectively longer reboot than normal. The only module I have installed (and the only reason atm for me having Xposed installed) was to kick the pesky ISIS app past the "Your phone is rooted" message. Both apks were downloaded from XDA as well. After several unbearably long freezes and general sluggishness reminiscent of my Evo 3D, I ended up uninstalling ISIS as well as Xposed which returned my phone to its normal speedy operation. It should be noted however that while it was runny slow and freezing, ISIS did function properly and allowed me to add things as if I weren't rooted. I'd be more than happy to re-install and try again, but I thought I'd pick the brains of the big wigs here first and see if anyone had any thoughts before I do so. Also if it matters, my GS5 is the T-Mobile version.
Click to expand...
Click to collapse
I have no noticable lag or freezing with Xposed installed with several modules running. I did have the issue with ISIS not wanting to run with a rooted device but RootCloak fixed that for me.
There is a issue with s-health service fc that cause this slow down. In this same forum you can find some workaround i don't remember (even though I've used it)
Please check the existing thread.
OK, so this is an interesting one that's not the end of the world but odd non the less.
My phone 64GB CW bought from GPS. Rooted only, stock recovery still. Lightflow, and carrier tether check disabled are the only two mods I really wanted.
My friend 64GB CW bought from GPS. Stock no root.
His phone will play crossy road just fine, Mine will boot it until it gets to the developer name then crash out.
Anyone else had weird quirks with apps like this after root? I've seen one thread about it and it said to clear the cache in recovery, and that didn't work for everyone. I haven't felt the need to put a 3rd party recovery on yet so I really can't do that quickly.
meest said:
OK, so this is an interesting one that's not the end of the world but odd non the less.
My phone 64GB CW bought from GPS. Rooted only, stock recovery still. Lightflow, and carrier tether check disabled are the only two mods I really wanted.
My friend 64GB CW bought from GPS. Stock no root.
His phone will play crossy road just fine, Mine will boot it until it gets to the developer name then crash out.
Anyone else had weird quirks with apps like this after root? I've seen one thread about it and it said to clear the cache in recovery, and that didn't work for everyone. I haven't felt the need to put a 3rd party recovery on yet so I really can't do that quickly.
Click to expand...
Click to collapse
Doesnt the stock recovery have a wipe cache option? It did on the 5
I've got a rooted 64GB MB and it plays Crossy Road just fine.
rootSU said:
Doesnt the stock recovery have a wipe cache option? It did on the 5
Click to expand...
Click to collapse
If there is I'm not sure how to get to it? I'm assuming a command of some sorts via ADB or Fastboot? This is my first Nexus device since my GNex since i'm on Verizon. So is my Friend though. Both of us still encrypted also. I've uninstalled and installed 4-5 times also. Cleared app cache a few times also.
I find it really strange as well. I download it, closes on developers name screen. Tried on two different roms and both don't work . Maybe just a bug. Not much info to be found on the issue.
jellybsly55 said:
I find it really strange as well. I download it, closes on developers name screen. Tried on two different roms and both don't work . Maybe just a bug. Not much info to be found on the issue.
Click to expand...
Click to collapse
What sort of similar changes have you been making? DPI changes, kernel changes or something else that may be common between the ROMs. Also, I am assuming you wiped in between the ROMs, if so did you restore data. I am just thinking out loud though. Logcats would probably help you find the cause of the problem.
Crossyroads has worked for me on stock, rooted or not, chroma, slimlp, try clearing data on the game, install from playstore and dont restore from TiBu if you are.
Donjuanal said:
Crossyroads has worked for me on stock, rooted or not, chroma, slimlp, try clearing data on the game, install from playstore and dont restore from TiBu if you are.
Click to expand...
Click to collapse
Yeah it's quite weird. (Nexus 5 though, shouldn't really make a difference). I don't even have a cache/date to clear since the game won't boot up enough to make one i think . Quite strange, just wanted to say that the OP isn't only one
It crashed everytime on my N6 so I emailed the developer and he said it doesn't work with ad blockers installed.. So I disabled the adblocker I had running and crossy road loaded just fine with exact same setup.. So if you have adblockers that's probably the issue.
meest said:
OK, so this is an interesting one that's not the end of the world but odd non the less.
My phone 64GB CW bought from GPS. Rooted only, stock recovery still. Lightflow, and carrier tether check disabled are the only two mods I really wanted.
My friend 64GB CW bought from GPS. Stock no root.
His phone will play crossy road just fine, Mine will boot it until it gets to the developer name then crash out.
Anyone else had weird quirks with apps like this after root? I've seen one thread about it and it said to clear the cache in recovery, and that didn't work for everyone. I haven't felt the need to put a 3rd party recovery on yet so I really can't do that quickly.
Click to expand...
Click to collapse
See attached pic
We need min min guard for lollipop or something that let's us choose which apps to block ads.
Hey guys, i installed xposed on stock android nexus 6p (rooted obviously). But now i am getting these errors:
com.android.providers.partnerbookmarks this one seems to occur whenever i open a google chrome link in an app.
android.process.media This one seems to occur randomly.
It is not really bad yet, it happens every once in a while, but if there is a fix, that'd be great.
EDIT: I haven't had the errors in a while, even when i opened chrome links. Maybe my phone just needed a restart which i did. But i'm still a bit concerned.
Has anyone else had random reboots with their R1 HD? I get a few a day and am not sure what the cause is. I have a Prime version converted to OEM and have unlocked the bootloader and rooted it. I am thinking it is related to the "Standby intelligent power saving" mode, but haven't had it long enough to test this theory. If anyone else has had this issue, let me know and if you fixed it.
linuxgator said:
Has anyone else had random reboots with their R1 HD? I get a few a day and am not sure what the cause is. I have a Prime version converted to OEM and have unlocked the bootloader and rooted it. I am thinking it is related to the "Standby intelligent power saving" mode, but haven't had it long enough to test this theory. If anyone else has had this issue, let me know and if you fixed it.
Click to expand...
Click to collapse
I have never experienced an issue of random reboots on Prime w/ conversion, or with Prime itself. I have manually removed amazon bloat and some Google bloat. Only issue I seem to have is apps disappearing from adopted storage, more so on Prime. Do you have any third party software that may be causing this? Or possibly defective hardware? Try running a stress test see if possibly a hardware issue...
https://play.google.com/store/apps/details?id=com.into.stability
kal250 said:
I have never experienced an issue of random reboots on Prime w/ conversion, or with Prime itself. I have manually removed amazon bloat and some Google bloat. Only issue I seem to have is apps disappearing from adopted storage, more so on Prime. Do you have any third party software that may be causing this? Or possibly defective hardware?
Click to expand...
Click to collapse
I don't have any apps that I haven't used on other phones before with no issues. I doubt it's a hardware issue unless it's just a bad design. I am wondering if the power button itself is getting pressed while in my pocket. When I get a case that can give it a bit more protection I should be able to see if that's the problem.
Edit: I'll try out that app and see what it shows if/when I see it reboot again.
linuxgator said:
I don't have any apps that I haven't used on other phones before with no issues. I doubt it's a hardware issue unless it's just a bad design. I am wondering if the power button itself is getting pressed while in my pocket. When I get a case that can give it a bit more protection I should be able to see if that's the problem.
Edit: I'll try out that app and see what it shows if/when I see it reboot again.
Click to expand...
Click to collapse
Quick update... I flashed the OEM ROM again, this time without rooting it, and I haven't had any issues (yet). @kal250, is your phone rooted?
linuxgator said:
Quick update... I flashed the OEM ROM again, this time without rooting it, and I haven't had any issues (yet). @kal250, is your phone rooted?
Click to expand...
Click to collapse
Yes, my bootloader is unlocked, TWRP installed, and rooted, no issues. Except occasional problems with apps on SD (adopted), but not sure if its rom related or if apps just don't like being on SD.... No issues with random reboots.
kal250 said:
Yes, my bootloader is unlocked, TWRP installed, and rooted, no issues. Except occasional problems with apps on SD (adopted), but not sure if its rom related or if apps just don't like being on SD.... No issues with random reboots.
Click to expand...
Click to collapse
What root method did you use?
Sent from my BLU R1 HD using Tapatalk
linuxgator said:
What root method did you use?
Click to expand...
Click to collapse
Here..... second post
http://forum.xda-developers.com/r1-hd/how-to/guide-convert-to-prime-rollback-ota-t3432499
Yep, that's the method I used. However, I also converted to a system root so I could use a few apps that don't like systemless root. I'm beginning to think that may have had something to do with it. Or maybe just a bad flash at some point. It's been running strong without a reboot since I manually did it yesterday evening after reflashing the system. If it makes it through the day, I may try rooting it again.
Thanks again for your help.
Sent from my BLU R1 HD using Tapatalk
linuxgator said:
Yep, that's the method I used. However, I also converted to a system root so I could use a few apps that don't like systemless root. I'm beginning to think that may have had something to do with it. Or maybe just a bad flash at some point. It's been running strong without a reboot since I manually did it yesterday evening after reflashing the system. If it makes it through the day, I may try rooting it again.
Thanks again for your help.
Click to expand...
Click to collapse
I went with systemless root
I run stock on my Nexus 6p and I've been more or less content to run SuperSU. Really, the only thing I use root for is CF.Lumen. Chainfire is pretty much the only reason I root these days. I also keep mine unencrypted. I was having to at one point just to get sRGB color mode to stick after reboot. I'm not sure if that's still an issue anymore, but I continue not to encrypt and just run a modified stock boot image.
In any case, I haven't paid much attention to Magisk in quite some time and I noticed looking around today that it seems to have come a long way. I know at some point it's moot since I root, but I flash the new system and vendor images each month and update my modified boot image, mainly just to get rid of the damn notification to update. It sure would be nice to get Android Pay working as well as be able to run CF.Lumen. In my case, since I'm flashing the updated stock images each month, would it be stupid to expect Magisk Hide to more or less consistently work? Should I bother with it? Anyone else out there have a similar use case to mine and had good luck with Magisk Hide?
Thanks for weighing in.
Cheers,
Chad