[Q] Losing R/W and hosts file reverts - Moto X Q&A

I rooted with Jcase's Slapmymoto root method. I have Adaway installed. After a while of using the phone with no reboots or anything, the hosts file will revert and I lose r/w access to files in the system folder.
I had this problem with my HTC One as well and never found a solution. If I reboot the phone into "recovery", it simply reboots the phone and then I have r/w access and I can apply my hosts file again, but this is never permanent.
What did I do wrong and what can I do to fix it? The phone is still rooted when this happens. It just takes away my ad blocking and ability to modify system files until I reboot.

I have what is probably the same problem, where the AdAway modification to hosts goes away after a reboot.

psilosome said:
I have what is probably the same problem, where the AdAway modification to hosts goes away after a reboot.
Click to expand...
Click to collapse
I'm going to try the AdFree blocker instead
http://forum.xda-developers.com/showthread.php?t=2350984

greyhulk said:
I rooted with Jcase's Slapmymoto root method. I have Adaway installed. After a while of using the phone with no reboots or anything, the hosts file will revert and I lose r/w access to files in the system folder.
I had this problem with my HTC One as well and never found a solution. If I reboot the phone into "recovery", it simply reboots the phone and then I have r/w access and I can apply my hosts file again, but this is never permanent.
What did I do wrong and what can I do to fix it? The phone is still rooted when this happens. It just takes away my ad blocking and ability to modify system files until I reboot.
Click to expand...
Click to collapse
You would best to ask this in the slapmymoto thread
Sent from my XT1060 using Tapatalk

jwthompson said:
You would best to ask this in the slapmymoto thread
Sent from my XT1060 using Tapatalk
Click to expand...
Click to collapse
Maybe, but I had this exact issue with my HTC One as well, and it was not rooted using his method, so it seems like more of a general issue.
Sent from my SAMSUNG-SM-N900A using Tapatalk

AdFree seems to have the same problem for me. These threads looks relevant:
http://forum.xda-developers.com/showthread.php?t=2551113
http://www.reddit.com/r/MotoX/comments/1st9tk/locked_bootloader_root_limitations/

Related

[Q] activating stagefright..having trouble switching false to true.

i'v rooted my phone, now trying to activate stagefright..i used blade buddy, but didn't seem to do the trick. i've tried writing in true with several different apps but it telling me can not write file : /sytem/ built.prop. cannot someone help??
Using blade buddy did you do a menu > save?
Sent from my Zio using XDA Premium App
yeah, but when i go back to the system folder build.prop it still says false.
Use Root Explorer or whatever file manager you use with R/W access and then manually edit the build.prop and reboot.
i've used antek file explorer and es file explorer and a couple other ones, but neither let it r/w. could it be because of the busybox version i'm using??
how do i know which version of busybox i need to be using. i'm still using the stock rom. havent flashed to openzio rom yet..afraid to brick my phone, being a noob and all lol.
Busybox is part of superuser permissions or root. Download the Busy Box Installer from Mr. Steine Ericcson(prolly messed up his name spelling). I'm using the latest "unstable" version with no problems. Busybox version isn't going to matter for R/W access. Are you sure you're rooted? You can't get R/W access without root.
i'm rooted using Z4root...using busybox installer from the market, v1.19. ive re-rooted to make sure i am. is there another way to root this phone??
i checked root access and it says "alternate su binary location: /sbin/su: permission denied". does that have something to do with it??
Yeah that may have something to do with it. I wrote the below before I saw the permission denied.
Sounds rooted to me. You need to get a file manager with R/W access. Then get it on R/W and manually edit the file. Everything I've ever used that changed stagefright was a shaky app at best. As more time goes by, manually editing it thru whatever means is always the best choice. Apps take up space and really don't save that much time. This includes any other settings you want to play with. Editing yourself and rebooting is always the most assured way of success.
This post belonged in the Stagefright Thread Stickied to the top of the forum, by the way. And if you would have read the Stagefright thread you would have seen everything I'm telling you now, there. Just for future reference. There was no reason for this thread.
I would unroot with z4 and try Universal Androot or Super One Click.
so i guess root explorer is the only way to go..cause the other apps ive used seem to have r/w properties but still dont work. well thanks for the help, i'll have to buy root explorer i guess..by the way, where to i find the busy box installer you mentioned??
i'm really new to this..sorry for wasting a thread. thanks for all the help anyway
Anything that has R/W access should work. If the R/W isn't working your root is messed up. So I would suggest unrooting it and rerooting it again with something else or even trying again. Let me see what Mattix or someone says about your error.
sweet..thanks. if nothing else, i'll just re-root with universal androot or super one-click. the phone seems to running pretty good, but when i play angry birds, it lags really bad..to the point that its almost unplayable. i get between 720-740 when i benchmark with Antutu.
so i re-rooted with universal androot, and still not getting permission to edit system files, namely stagefright. it either says you do not have permission to edit file..or cannot write system file build.prop what am i doing wrong or do i need something else to do this?? i'm using antek file explorer, could that be the problem??
Just install the latest OpenZio ROM release -- I have defaulted stagefright to "off" to address an issue with certain ringtones not showing up in tone selection.

[Q] Creating a back door

Some of the recent posts have suggested that we may soon see a patch for the root exploit we currently have.
Being that we have root now is there some place we could hide SU where we could access it later should root be closed on us, allowing re-rooting of the device? It would have to be some place that does not get overwritten when an update is pushed...and I am not sure if that even exists on Android.
Not easily, since system is one of two partitions that doesn't have nosuid or noexec set.
Sent from my DROID3 using xda premium
Dunno about that, but I've been told there are a couple root methods being saved for later....
So I guess I am correct in assuming that the entire /system gets overwritten during an update?
I just played a bit with /root but cannot get anything to run with the current permissions of the mount.
For my understanding am I correct in the belief that all system directories get overwritten "/sys/ /system/"?
slow88lx said:
Dunno about that, but I've been told there are a couple root methods being saved for later....
Click to expand...
Click to collapse
Thank god for this!
Sent from my DROID3 using XDA App
calash said:
So I guess I am correct in assuming that the entire /system gets overwritten during an update?
I just played a bit with /root but cannot get anything to run with the current permissions of the mount.
For my understanding am I correct in the belief that all system directories get overwritten "/sys/ /system/"?
Click to expand...
Click to collapse
It doesn't get overwritten, but the update does reset all permissions. Thus, the su executable will still be there after the update, but will be chmodded 0755.
Just brainstorming so feel free to tell me I'm wrong
What about replacing a suid binary. Ping is the one I am thinking of right now. Would the update replace that file?
Sent from my DROID3 using Tapatalk
calash said:
Just brainstorming so feel free to tell me I'm wrong
What about replacing a suid binary. Ping is the one I am thinking of right now. Would the update replace that file?
Click to expand...
Click to collapse
Looking at the permissions set in the update's script, it doesn't look feasible. If I'm reading them right, PING's permissions only allow it access to the NET_RAW group, which doesn't give us anything useful. Everything else is just as unhelpful.
Anyone know if it would be possible to fastboot flash an older recovery to a device with a newer bootloader, then temproot that and use it to permroot the device?
Xenoproctologist said:
Looking at the permissions set in the update's script, it doesn't look feasible. If I'm reading them right, PING's permissions only allow it access to the NET_RAW group, which doesn't give us anything useful. Everything else is just as unhelpful.
Anyone know if it would be possible to fastboot flash an older recovery to a device with a newer bootloader, then temproot that and use it to permroot the device?
Click to expand...
Click to collapse
Sorry to go off topic, but am I the only one who's wondering how ironic it is that a user named "xenoproctologist" is responding to a thread titled "Creating a Back Door"?
Freud would have a goddamn field day with this!
rynosaur said:
Sorry to go off topic, but am I the only one who's wondering how ironic it is that a user named "xenoproctologist" is responding to a thread titled "Creating a Back Door"?
Freud would have a goddamn field day with this!
Click to expand...
Click to collapse
No, no... I only use pre-existing back doors. ^_^
I would rather have bugs than no root. I sat on my droid3 until root was available rather than activating it.
Would it be possible in that case to run FOTAkill on a rooted d3? If so, would it help?
I noticed a couple of OTA/update related apks while noodling with Titanium.... could those be frozen to prevent updates?
hiddenhandgun said:
I would rather have bugs than no root. I sat on my droid3 until root was available rather than activating it.
Would it be possible in that case to run FOTAkill on a rooted d3? If so, would it help?
I noticed a couple of OTA/update related apks while noodling with Titanium.... could those be frozen to prevent updates?
Click to expand...
Click to collapse
There are only one or two lines in build.prop that need to be changed to prevent receiving OTAs or update notifications. Search on the DroidX forums and you'll find these values.
Editing the build.prop is not the best way to prevent OTA updates.
It will cause issues with Market and other functions that read those strings for various reasons.
Disabling by freezing or renaming BlurUpdater_VZW.apk and FOTA.apk is safer and will not affect anything else adversely.
cellzealot said:
Editing the build.prop is not the best way to prevent OTA updates.
It will cause issues with Market and other functions that read those strings for various reasons.
Disabling by freezing or renaming BlurUpdater_VZW.apk and FOTA.apk is safer and will not affect anything else adversely.
Click to expand...
Click to collapse
Thanks. I'll give that a go.
There is always something being worked on to retain/get root again after a patch. There is also a good reason it doesn't get talked about in any kind of detail.

OTA Update Issue

My Droid 3 is rooted and I received the OTA notification. It downloads fine, reboots the phone, and begins to update. About 1/3 the way to update, the Android turns into an Exclamation point and reboots. Once back to home screen I get an Update Failed error.
Here is what I did so far:
-Defrosted all apps then rebooted
-Restored all system apps with Pete's One Click Root
-Pulled Battery for 5 min
-Factory Reset Phone
After each of these steps I tried to install the update and same thing. Will not get past 1/3. Any suggestions?
u need to rsd the swu.zip in order to get the update
OK, where can I get the swu.zip?
lacesout said:
OK, where can I get the swu.zip?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1255198
here u will find it along with rsdlite n adb fastboot. (make sure U read all that b4 U do it)
mrcastillo said:
http://forum.xda-developers.com/showthread.php?t=1255198
here u will find it along with rsdlite n adb fastboot. (make sure U read all that b4 U do it)
Click to expand...
Click to collapse
Thank you, this work!
lacesout said:
My Droid 3 is rooted and I received the OTA notification. It downloads fine, reboots the phone, and begins to update. About 1/3 the way to update, the Android turns into an Exclamation point and reboots. Once back to home screen I get an Update Failed error.
Here is what I did so far:
-Defrosted all apps then rebooted
-Restored all system apps with Pete's One Click Root
-Pulled Battery for 5 min
-Factory Reset Phone
After each of these steps I tried to install the update and same thing. Will not get past 1/3. Any suggestions?
Click to expand...
Click to collapse
lacesout, had the same experience. Used one-click method to root, then used psouza4's bloat script to remove, then restore apps when the update became available. These were my only mods. Went to /system/app and all app's are back with the proper apk extension. Update downloads fine, then hangs at 1/4 to 1/3 of install. Anyone else with similar experience or thoughts as to what's hanging the OTA install?
If you used the script to re-bloat the system, use root explorer and double check all the ".bak"s were removed. I don't remember which one, but I remember there was a file or two the script skipped over.
Also, if you did a nandroid before debloating, you can restore it, then go get the update. (The second option is what worked for me).
Sent from my DROID3 using XDA App
nu2droid said:
If you used the script to re-bloat the system, use root explorer and double check all the ".bak"s were removed. I don't remember which one, but I remember there was a file or two the script skipped over.
Also, if you did a nandroid before debloating, you can restore it, then go get the update. (The second option is what worked for me).
Sent from my DROID3 using XDA App
Click to expand...
Click to collapse
Thanks for the reply and the tip on root explorer, it's an elegant tool, more intuitive to use than the freeware apps.
All the file extensions in /system/app are either .apk or .odex with the exception of Fota.apk.bak, and Fota.odex.bak. As the first time I heard of nandroid was your post, I unfortunately didn't use it, so I don't know if these were the extensions before I used psouza's bloat removal script. Fota was not on the list of scripts to remove/rename in his original post.
As Fota is the "firmware over the air" app, it is suspicious that it's the only one with a .bak ext. I am using root explorer to rename both, removing the .bak, and then will attempt another update.
Success! "Your phone has been upgraded to 5.6.890.en US version". Have lost root, at least for the moment. Will deal with that tomorrow. Last thing to do before going to bed is find the "Thanks" button. Thanks for setting me on the right path. P.
Unable to root after OTA to .890
One click root not longer works. After clicking "run_to_root_your_droid3.sh" on PC (Ubuntu 10.04) I get no prompts on screen, but phone does reboot twice. No su privileges after boot. Busybox is installed in /system/xbin and there is nothing I can do about it as I can't mount r/w. Using Root Explorer and Script Manager as tools.
I realize I'm going to have to increase my learning curve here. Would appreciate any links to relative threads on this topic, or suggestions on what to try next (I have searched, but need some direction).

How to acces "system" folder on Droid 3?

If a connect it to the PC, i cannot see the system folder. (is there any trick I am not aware of?)
If i use a folder manager, i cannot put a ringtone in the system/media folder...its probably protected or so.
does it HAVE to be rooted or so?
thank you.
Root is required to make changes to /system
Sent from my DROID3 using xda premium
If you wanna put a ringtone in /system/media use root explorer. That's the easiest way for you, if you're advanced and wanna get familiar with adb, adb push it
Sent from my DROID3 using Tapatalk
THANK YOU.
I assumed that
but is the ROOT safe at this time? i have red a lot of issues after ROOTing...
Uhh... root is kinda never safe? Haha. Idk what you mean by that
Sent from my DROID3 using Tapatalk
getting root itself normally isnt a big issue.. normally people run in to more trouble when they have attempted flashes that go awry.
I used to flash my HTC Touch Pro 2 with a CUSTOM Rom almost every month... for more than 1 year..and no issues there...
but the number of topics with problems after booting the D3...made me think again when modding this phone...
With just a root, you should be ok. I feel that just rooting does very little, and as said before, the issues only arise when we try to take advantage of what root enables us to do...freezing, modding, flashing, etc.
i just want to put a custom ringtone (mp3 file) in the ringtones folders.
the ringtones from this phone..are really stupid.
any ideas which does not include root?
Well I use the MIUI music app and when it asks me to choose a ringtone I just chooose it through that
Sent from my DROID3 using xda premium
Use Ringdroid, it's free in market. Ringdroid allows you to crop and edit audio files, turn them in to ringtones and set them as default.
worked perfectly with ringdroid
if i unistall the application, the ringtone will remain?
use root explorer. Thats how i get to it.
bogdan_wrc said:
[...]any ideas which does not include root?
Click to expand...
Click to collapse
VincentDHam said:
use root explorer. Thats how i get to it.
Click to expand...
Click to collapse
nope. if i try to move with root explorer a file in system folder, it says i can not do that. probably because the phone is not rooted.
bogdan_wrc said:
nope. if i try to move with root explorer a file in system folder, it says i can not do that. probably because the phone is not rooted.
Click to expand...
Click to collapse
Exactly. Do not be afraid to root it, you can unroot it whenever you like.
Sent from my XT860 using Tapatalk
Root explorer isn't nedded anymore. ES file explorer can browse as root, and it's free.

Phone shuts down immediately when I use Root Explorer

I got a weird situation. My phone just shuts down when I use Root Explorer, randomly. It has happened while I made a zip of a system file, mounted R/W, deleting a system file. It appears to be completely random. Tried clearing root permissions for it and reaenabled it but it still happens. A reinstall of Root Explorer didn't help either. Any idea what's the problem?
On KA03 ROM, locked bootloader and rooted.
sacredsoul said:
I got a weird situation. My phone just shuts down when I use Root Explorer, randomly. It has happened while I made a zip of a system file, mounted R/W, deleting a system file. It appears to be completely random. Tried clearing root permissions for it and reaenabled it but it still happens. A reinstall of Root Explorer didn't help either. Any idea what's the problem?
On KA03 ROM, locked bootloader and rooted.
Click to expand...
Click to collapse
you probably have not stopped ric, on these devices there is a service called ric which resets the device when system is mounted r/w
lilstevie said:
you probably have not stopped ric, on these devices there is a service called ric which resets the device when system is mounted r/w
Click to expand...
Click to collapse
How do I stop ric?
sacredsoul said:
How do I stop ric?
Click to expand...
Click to collapse
adb stop ric, do you use supersu or superuser?
sacredsoul said:
I got a weird situation. My phone just shuts down when I use Root Explorer, randomly. It has happened while I made a zip of a system file, mounted R/W, deleting a system file. It appears to be completely random. Tried clearing root permissions for it and reaenabled it but it still happens. A reinstall of Root Explorer didn't help either. Any idea what's the problem?
On KA03 ROM, locked bootloader and rooted.
Click to expand...
Click to collapse
That happened to me a few days back, its shows as if you have root but in reality you don't. I tried re-rooting but it would no let me do it again because the superuser.apk already existed. I deleted it and lost root completely but still it would not let me re-root. In the end I just flashed a different rom again as the one one I had flashed was pre-rooted.
So my advice would be to flash and unrooted ROM and then root instead of a pre-rooted ROM (maybe this wasn't your case but it is very similar to what happened to me!!)
lilstevie said:
adb stop ric, do you use supersu or superuser?
Click to expand...
Click to collapse
Followed this post and all is well so far. No more random shut offs! Thanks for pointing me in the right direction. :good:
http://forum.xda-developers.com/showpost.php?p=39514293&postcount=2124
lilstevie said:
adb stop ric, do you use supersu or superuser?
Click to expand...
Click to collapse
sacredsoul said:
Followed this post and all is well so far. No more random shut offs! Thanks for pointing me in the right direction. :good:
http://forum.xda-developers.com/showpost.php?p=39514293&postcount=2124
Click to expand...
Click to collapse
lilstevie pointed you in the right direction, superSU causes these. Superuser or the new, Koush's Superuser app don't do this.

Categories

Resources