Related
Hi, I rooted my Vribrant, both ways (manually and with one click root). I installed terminal emulator. I tried the su command to check if I am root. The # appears normally. However I tried deleting a file with Root explorer, inside the system folder, and when I get back it's still there. I also tried deleting it manually from Terminal EMulator with these commands:
su
cd system/apps
rm Swype.apk
and I get this:
rm failed for Swype.apk, Read-only file system
I also tried:
su rm Swype.apk
and this is returned:
Permission denied.....
I also tried the exact same thing from adb shell (which I had to allow in superuser permissions program), but it gave me the exact same results. What's wrong? Am I doing something wrong? Thanks
In root explorer, try hitting the r/w button at the top and see if that works.
Sent from my SGH-T959 using XDA App
I know about the button. The strange thing is that inside system folder it grands me r/w permissions, and no matter how many times a press the r/o button it doesn't change. Still gives the results I said. However, besides root Explorer what's wrong with terminal emulator and adb?
I'm not 100% sure how to mount as root in adb. I wish I knew myself heh.
Did any of those root methods install the superuser app?
Sent from my SGH-T959 using XDA App
Terminal Emulator should return a "#" after typing "su"
Sent from my SGH-T959 using Tapatalk
From a terminal write
adb root. (will give root)
adb remount. (will remount system as r/w)
adb shell cp /system/app/swype.apk /system/app/swype.apk.bak
Adb shell rm /system/app/swype.apk
This link is what i used to use to gain rw permissions
http://android-tricks.blogspot.com/2009/01/mount-filesystem-read-write.html
Alternatively from terminal on the phone type
su
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
Assuming your sys partition is mntblock3
Sent from Conical. 07
rbirg said:
I'm not 100% sure how to mount as root in adb. I wish I knew myself heh.
Did any of those root methods install the superuser app?
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
Yes both methods installed the "Superuser Permission" app.
I7oobie said:
Terminal Emulator should return a "#" after typing "su"
Sent from my SGH-T959 using Tapatalk
Click to expand...
Click to collapse
It does normally.
linuxmotion said:
From a terminal write
adb root. (will give root)
adb remount. (will remount system as r/w)
adb shell cp /system/app/swype.apk /system/app/swype.apk.bak
Adb shell rm /system/app/swype.apk
This link is what i used to use to gain rw permissions
http://android-tricks.blogspot.com/2009/01/mount-filesystem-read-write.html
Alternatively from terminal on the phone type
su
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
Assuming your sys partition is mntblock3
Sent from Conical. 07
Click to expand...
Click to collapse
I tried the first method but it didn't work. When I entered adb root, it said "adbd cannot run as root in production builds". I searched a bit and found that I must have a rooted kernel for this to work. (I guess it's different from the root method I tried in "how to root vibrant").
Anyway the second way worked, where i replaced mntblock3 with stl9 for my phone. I tried the rm command and it worked! However as soon as I exited terminal, I couldn't delete other files. I had to retype the command. I can't do this everytime I need access in System folder. Why is this happenning? Does this have something to do with the fact that root explorer cannot change r/w to r/o mode while in system folder?
what if you open Superuser
Click on Root Explorer.
Click on Forget.
Open Root Explorer and grant Root Access and check to remember it.
work now?
Moved to Q&A, please post in the correct section.
s15274n said:
what if you open Superuser
Click on Root Explorer.
Click on Forget.
Open Root Explorer and grant Root Access and check to remember it.
work now?
Click to expand...
Click to collapse
No it didn't work. I also installed the latest version of SuperUser 2.3.6.1. But without a difference unfortunately.
What works for me, is installing sgs tools, and whenever I want to do write operations on system folder, run the appropriate script from sgs and then use root explorer......
Although I think there's something wrong? Why doesn't the mount r/w button work in root explorer, and why do I have to remount the file system through SGS tools, every time for it to work?
makes no sense to me either. Have you uninstalled RE and the installed it back granting root once reinstalled?
Yes several times.....
I am giving up. I just have to go through the whole process every time. I found some other people having this issue. I am on stock JI6 firmware. Maybe when I read a little bit more I will flash a custom rom.
Download and install Super Manager. Pretty handy program to use for Root users.
I'm not sure what the issue is,but mine does it too. I'm running the "unofficial" froyo JK2 build,flashed via ODIN,and I'm having the same issues. root works,root file explorer is stuck in rw,won't let me switch to ro,and it can't do anything to files in / or /system. manually remounting it from terminal or sgs tools works.
msnuser111 said:
I'm not sure what the issue is,but mine does it too. I'm running the "unofficial" froyo JK2 build,flashed via ODIN,and I'm having the same issues. root works,root file explorer is stuck in rw,won't let me switch to ro,and it can't do anything to files in / or /system. manually remounting it from terminal or sgs tools works.
Click to expand...
Click to collapse
At least I am not the only one with this problem.... haha
I forgot to mention that I use Root Explorer version 2.12.2
When I try a custom Rom I will post the results....
^ why not get the update, .4 is the most recent build. Do you have an illegal copy?
It's not only root explorer. It happens with other file explorers too like android mate and super manager... Inside system folder whatever, I do doesn't happen unless I unmount and remount like before
Can someone knowledgeable please submit a detailed post, which instructs how to remove any files added during the Root Process, as well as any other file permission changes or modifications of any other type?
I see many half assed posts in these forums made by unqualified members, which are nothing but a waste of time and clutter this great resource. I would appreciate it if this post could be addressed by those who truly understand this process.
The file that was used to Root the SCH-i905 from Verizon was the one attached to this post.
Thanks in advance! This could be a great learning tool if answered properly.
Can some one please respond? Or is it that everyone is too scared to post helpful information?
Well, since no one was of any assistance, I was forced to piece together information and come to an understanding of how this works, and how to fully reverse what was done by this Root Update.
To begin, I would like to mention, that removing Superuser.apk from the /system/app folder, along with 'su' from the /system/bin folder, will negate your Root Access, and put you back to your default levels of access. This will prevent Mobile Device Management Solutions, such as AirWatch, Zenprise, or MobileIron from detecting your device as being compromised.
I was not successful in removing these two files via the ADB shell, however I was successful when using a Terminal Emulator App on the Device itself.
1.) I began by installing a free Terminal Emulator from the Android Market.
2.) Launched the Terminal Emulator and typed 'su' , then pressed Enter to gain Root Shell Privileges.
3.) From the Root Shell, I typed the following commands to remount the '/System' Directory to gain Read/Write Access.
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
4.) I typed the following commands to remove 'Superuser.apk' and 'su'.
cd /system/app
rm Superuser.apk
cd /system/bin
rm su
5.) Type the following command to remount the '/System' Directory back to Read Only.
mount -o ro,remount -t yaffs2 /dev/block/mtdblock3 /system
6.) Sync your device with Google under Settings / Accounts & Sync.
7.) Reboot your device, and you are good to go.
It might be a good practice to perform a Factory Reset on your device after doing this, however this is not completely necessary. I tested the Air-Watch Agent installation after performing the procedure mentioned above, and the Air-Watch console no longer detected my device as being compromised.
I will add that on my sch-i905 I found the bin directory under system not under system/app. For me, replacing cd /system/app/bin with cd /system/bin did the trick but the rest worked a treat - thanks for the post!
Thanks for pointing out my typo. I corrected the path in my Post.
Thanks for this.
Does this restore the stock recovery that was replaced with Clockwork when the kernel.zip and recovery.zip files were flashed to obtain root? I do not totally understand the relationship between Superuser and CWR. I found a reference to a flashable stock recovery in post 14 here http://forum.xda-developers.com/showthread.php?t=1205639&page=2 , but I'm unclear on the instructions.
I'm trying to understand how, if possible, to return my VZW LTE Tab to out-of-the-box stock, if desired.
Rooted: Droid Incredible / Droid X / Thunderbolt / 3G-4G Xoom / Galaxy Tab 10.1 LTE
I have the Superuser icon showing up in my apps folder, but I don't appear to have root access. I can't su in the terminal emulator nor can I load apps that require root access. I also tried removing the Superuser.apk via a file manager with no luck.
Any idea how to remove this thing if I don't actually have root access?
---------- Post added at 09:25 PM ---------- Previous post was at 09:10 PM ----------
OK, I rooted again and fixed whatever was broken. Then I was able to apply these commands to unroot the device.
Thank you!
tbcpn said:
Thanks for this.
Does this restore the stock recovery that was replaced with Clockwork when the kernel.zip and recovery.zip files were flashed to obtain root? I do not totally understand the relationship between Superuser and CWR. I found a reference to a flashable stock recovery in post 14 here http://forum.xda-developers.com/showthread.php?t=1205639&page=2 , but I'm unclear on the instructions.
I'm trying to understand how, if possible, to return my VZW LTE Tab to out-of-the-box stock, if desired.
Rooted: Droid Incredible / Droid X / Thunderbolt / 3G-4G Xoom / Galaxy Tab 10.1 LTE
Click to expand...
Click to collapse
-----------------------------------------------------------------------------
-----------------------------------------------------------------------------
-----------------------------------------------------------------------------
Stock Recovery isn't required to Root the device. However, if you wish to install CWM via ROM Manager from the Android Market, Root Permissions are required.
If you use an ODIN Flash of CWM, there is no need for Root Permissions because you are flashing via ODIN.
The stock recovery zip file that you referenced in the other post should be fine.
Just use ODIN to Flash back to Stock Recovery and use the process that I mentioned to remove Root Permissions and Super User, and you should be all set to return your device after a Factory Wipe.
Cheers!
~Scott~ said:
I have the Superuser icon showing up in my apps folder, but I don't appear to have root access. I can't su in the terminal emulator nor can I load apps that require root access. I also tried removing the Superuser.apk via a file manager with no luck.
Any idea how to remove this thing if I don't actually have root access?
---------- Post added at 09:25 PM ---------- Previous post was at 09:10 PM ----------
OK, I rooted again and fixed whatever was broken. Then I was able to apply these commands to unroot the device.
Thank you!
Click to expand...
Click to collapse
-----------------------------------------------------------------------------
-----------------------------------------------------------------------------
Scott,
I'm sorry for just seeing your post. I'm sure that you figured it out by now. You need to gain Root Access to your device again to remove Super User. You are in a Catch22.
If you are using an SCH-I905, Root your device, then download Script Manager from the Android Market.
Run this very simple Bash Script that I wrote to remove Root and Super User.
Paste this into notepad and save it as Unroot.sh then run with Script Manager.
Code:
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
cd /system/app
rm Superuser.apk
cd /system/bin
rm su
mount -o ro,remount -t yaffs2 /dev/block/mtdblock3 /system
Be sure to run the Script as Root from within Script Manager. The app will kind of freeze up as soon as it runs, which is normal. This will certainly take care of your problem.
Thanks for your post of stockrec in a different post. You saved me a month ago with that one.
Cheers!
Will Samsung know if I rooted my GT 10.1 LTE after using these commands, and sending in for warranty?
Does anyone know how often airwatch checks for the root? anyway to bypass the checks?
Is this the same for the US Cellular 4G Tablet? I have been reading and all that I have found was WiFi only files. Which if I were to root with those I lose the 4G radio.
Perfect.. Just what I need. Thanks
Isn't root explorer just like every other file explorer? Why do more people use it and is always on tutorials?
if you need to edit system files with root aceess .. mount system as r/w , remove bloats ..in short advanced tasks .....you need it ...
if you haven't even rooted or don't want to touch system leave it
Because its fast, clean and you can use ROOT
Sent from my Galaxy ace using XDA App
1.) Inbuilt unzip
2.) Inbuilt unrar
3.) Inbuilt text editor (useful for modifying values of config files e.g. build.prop
4.) Full access /root
happily1986 said:
1.) Inbuilt unzip
2.) Inbuilt unrar
3.) Inbuilt text editor (useful for modifying values of config files e.g. build.prop
4.) Full access /root
Click to expand...
Click to collapse
= some advance tasks which only users that know what they are doing should do
as i have seen many dudes deleting system apps after which cry on xda
So I'm guessing its worth the money then. And as far as I've searched, there isn't a free version
you can also google it .
and can you edit the manufactor in build.prop to something like ... manufactor : ferrari?? and product name to : f40 ???
sent from my EVIL Galaxy Ace
I have no idea what you mean.
robinandroid said:
you can also google it .
and can you edit the manufactor in build.prop to something like ... manufactor : ferrari?? and product name to : f40 ???
sent from my EVIL Galaxy Ace
Click to expand...
Click to collapse
Sent from my Samsung Galaxy Ace using XDA App
robinandroid said:
you can also google it .
and can you edit the manufactor in build.prop to something like ... manufactor : ferrari?? and product name to : f40 ???
sent from my EVIL Galaxy Ace
Click to expand...
Click to collapse
yes you can. just a matter of a build.prop edit at the right parameter.
Because with default File Explorer you cannot Search, Copy, Paste ... etc
Root explorer use root permisions, it's the best, i use it and i'm verry happy with it !
R/W
Root Explorer does not let me mount the SD card as R/W. Any ideas on this? It use to let me...
BNAS said:
Root Explorer does not let me mount the SD card as R/W. Any ideas on this? It use to let me...
Click to expand...
Click to collapse
dude you seriously need to reconsider
your SD-CARD IS R/W ALWAYS
why you need root explorer to do that ??
BNAS said:
Root Explorer does not let me mount the SD card as R/W. Any ideas on this? It use to let me...
Click to expand...
Click to collapse
just restart the phone ......
madman_amit said:
dude you seriously need to reconsider
your SD-CARD IS R/W ALWAYS
why you need root explorer to do that ??
Click to expand...
Click to collapse
Dude.. To eliminate system apps you need root explorer. Default is R/O not R/W.
---------- Post added at 07:32 PM ---------- Previous post was at 07:30 PM ----------
prateek_gemini said:
just restart the phone ......
Click to expand...
Click to collapse
Restarted... Wiped cache, wiped davik cache, still no go. Used Nandroid to restore to a prior ROM I was using (Cog x2). Now it works. Found out that write protection on the SD partition was set to S-ON. Had to restore to a different ROM to get it back online. Super user was not granting permission to Root Explorer with Stock deodexed rooted ROM. Strange. Anyway, maybe someone else will come across this same issue and know that it is ROM related to write only partitions.
Thanks!
BNAS said:
Dude.. To eliminate system apps you need root explorer. Default is R/O not R/W.
---------- Post added at 07:32 PM ---------- Previous post was at 07:30 PM ----------
Restarted... Wiped cache, wiped davik cache, still no go. Used Nandroid to restore to a prior ROM I was using (Cog x2). Now it works. Found out that write protection on the SD partition was set to S-ON. Had to restore to a different ROM to get it back online. Super user was not granting permission to Root Explorer with Stock deodexed rooted ROM. Strange. Anyway, maybe someone else will come across this same issue and know that it is ROM related to write only partitions.
Thanks!
Click to expand...
Click to collapse
Hello. You want to mount r/w on your SD CARD. Madman is right. It's always r/w on the card.
System and card is different.
Sent from my GT-S5830 using Tapatalk
Hello everyone, I made the root using the "all in one" by condi.
the root is fine except that when I use the 'app' root app delete "to delete the files of sony, tells me that I need root permissions.
the version of Android 4.0.3 is R5A.
can someone help me? thanks
----------EDIT---------
with titanium backup I found out where they are system applications
/ locale / vendor / app. I tried to move "crash bandicoot" in / local / system / app and it says it is a read-only file so I can not uninstall it.
suggestions?
Athawulf said:
Hello everyone, I made the root using the "all in one" by condi.
the root is fine except that when I use the 'app' root app delete "to delete the files of sony, tells me that I need root permissions.
the version of Android 4.0.3 is R5A.
can someone help me? thanks
----------EDIT---------
with titanium backup I found out where they are system applications
/ locale / vendor / app. I tried to move "crash bandicoot" in / local / system / app and it says it is a read-only file so I can not uninstall it.
suggestions?
Click to expand...
Click to collapse
Try remounting root file system writable.
smgdev said:
Try remounting root file system writable.
Click to expand...
Click to collapse
thanks for the reply,
how to do what you told me?
Athawulf said:
thanks for the reply,
how to do what you told me?
Click to expand...
Click to collapse
Try root explorer or similar from Google Play
or try from terminal
su
mount -o remount,rw /system
or from pc
adb shell
su
mount -o remount,rw /system
stifilz said:
Try root explorer or similar from Google Play
or try from terminal
su
mount -o remount,rw /system
or from pc
adb shell
su
mount -o remount,rw /system
Click to expand...
Click to collapse
I used adb shell
mount: operation not permitted
Check your tablet screen after entering the su command, there should be a window asking you to grant root access. Give root access and you should be able to continue with the remount command.
Sent from my Sony Tablet S using xda app-developers app
So with Android 7 there seems to be a change in the way the system partition works and I tried a ton of ways to make my /system partition as writable. I tried an app, I tried terminal commands, and I tried a root file explorer. Nothing working; adaway wouldn't work without systemless zip flash. Emoji Switcher was also not working.
Well I found a fast and simple solution!
Install busy box and a terminal app
- Install busy box on system
- Open terminal app
- Run "su" (no quotes)
- Give the terminal app root access
- Then run "busybox mount -o rw,remount system" (no quotes)
- You should get no errors; it will actual do nothing, it will just go to the next line.
Now test that bad boy out and your system partition should be writeable. No more host errors in adaway!
Going to try this out. Been looking for a solution to this as well. Thanks.
Sent from my Nexus 6P using Tapatalk
---------- Post added at 08:50 PM ---------- Previous post was at 08:43 PM ----------
phillymade said:
Going to try this out. Been looking for a solution to this as well. Thanks.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
So if Busy Box is installed to data, do I need to uninstall and install to system for this to work properly. As of now I'm getting a not found error.
Sent from my Nexus 6P using Tapatalk
phillymade said:
Going to try this out. Been looking for a solution to this as well. Thanks.
Sent from my Nexus 6P using Tapatalk
---------- Post added at 08:50 PM ---------- Previous post was at 08:43 PM ----------
So if Busy Box is installed to data, do I need to uninstall and install to system for this to work properly. As of now I'm getting a not found error.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
Yeah you need your busybox installed on the system or it wont do anything
I have my busy box installed at /su/xbin
In terminal make sure you put su (then hit enter)
then type the command
If you put them together you get an error for some weird reason
Here is a picture of my busybox install https://www.dropbox.com/s/iwtutkots8bdd13/Screenshot_20160830-184451.png?dl=0
Will this thread make DPI change on rooted 7.0 possible ? :laugh:
ArminasAnarion said:
Yeah you need your busybox installed on the system or it wont do anything
I have my busy box installed at /su/xbin
In terminal make sure you put su (then hit enter)
then type the command
If you put them together you get an error for some weird reason
Here is a picture of my busybox install https://www.dropbox.com/s/iwtutkots8bdd13/Screenshot_20160830-184451.png?dl=0
Click to expand...
Click to collapse
I did su then enter and got the error. perhaps it's where I have busy box installed.
Sent from my Nexus 6P using Tapatalk
ps000000 said:
Will this thread make DPI change on rooted 7.0 possible ? :laugh:
Click to expand...
Click to collapse
Yeah dpi change it possible on Android 7! Currently running 420dpi!
phillymade said:
I did su then enter and got the error. perhaps it's where I have busy box installed.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
Make sure you install busybox on /su
This doesn’t work. After running this and then touch /sbin/su /system/bin/su /system/xbin/su
It says Read-only file system. Tried on the pixel c.
backslashV said:
This doesn’t work. After running this and then touch /sbin/su /system/bin/su /system/xbin/su
It says Read-only file system. Tried on the pixel c.
Click to expand...
Click to collapse
Wondering if this might help—running `blockdev --getro /dev/block/dm-0´ (my /system) returned “1” when I checked on Nexus 6P, and returned “0” after --setrw.
I wasn't able to sucessfully remount with the second command, however, due to ‘/system is busy’ or some such thing.
Code:
blockdev --setrw /dev/block/dm-0
mount -o remount,rw /system
You are a saint! While my /system was "writable" after root using Magisk, I couldn't change file permissions. Stumbled upon your method and was able to correct this, although I used my laptop. I had already installed busybox with Magisk, so I opened an adb shell, typed "su," then issued: busybox mount -o rw,remount system
Adaway, and AFWall+ is working fine and I was finally able to chmod 644 bootanimation.zip in /system/media of my Moto X Pure.
Thank you! :good:
Ericarthurc said:
So with Android 7 there seems to be a change in the way the system partition works and I tried a ton of ways to make my /system partition as writable. I tried an app, I tried terminal commands, and I tried a root file explorer. Nothing working; adaway wouldn't work without systemless zip flash. Emoji Switcher was also not working.
Well I found a fast and simple solution!
Install busy box and a terminal app
- Install busy box on system
- Open terminal app
- Run "su" (no quotes)
- Give the terminal app root access
- Then run "busybox mount -o rw,remount system" (no quotes)
- You should get no errors; it will actual do nothing, it will just go to the next line.
Now test that bad boy out and your system partition should be writeable. No more host errors in adaway!
Click to expand...
Click to collapse
* I installed BusyBox to /system/xbin using the app's install.
* I opened my Terminal app and typed su.
* I granted it access.
* I ran the exact command.
It just gave me another prompt as you said it should. But the File Manager that I have used on many rooted devices still won't let me check the box in its settings for Root Explore, even though it prompted me and I granted SuperUser access.
I don't get what I'm missing here.
UPDATE: I am now able to Apply Hosts in AdAway.
However, my File Manager that I have used in Root mode on every device still won't allow me to turn on "Root Explorer" mode. It did prompt me for SuperUser access and I did grant it (and double checked), but when I go to choose that option in the apps' Preferences, it says my device is not Rooted.
Any ideas?
Thank You.
Hi,
Okay, got it! Cancel my distress call.
Thank You!
Hi,
Had to redo my phone and while I can apply Hosts in AdAway (not being able to is a sure sign /System isn't Writable), when I try to make a change to my Build.Prop file found in /System it won't stay changed. I am using Nougat 7.0 with Magisk and every other Root app works fine.
Just for kicks, I tried running the commands you posted to see if it would help, but this time it didn't take the command (I do have BusyBox installed). Instead, it responded with; "Invalid Argument" as follows;
"mounting /dev/block/bootdevice/by-name/system on /system failed: Invalid Argument"
Then the prompt changed to "255|elsa:/ #"
Any ideas? It appears to see that BusyBox is installed, but it isn't working. Also, how do I check where my BusyBox is installed?
Thanks,
Dave