Hey Guys,
I got a simply question, I got root but I don't know if I got FULL ROOT, How to check that?
Yes, on Play Store there are 1000 of apps but I don't trust them.
Any commands from Terminal to Determine if I have Full Root?
eclyptos said:
Hey Guys,
I got a simply question, I got root but I don't know if I got FULL ROOT, How to check that?
Yes, on Play Store there are 1000 of apps but I don't trust them.
Any commands from Terminal to Determine is I have Full Root?
Click to expand...
Click to collapse
Uhm open a terminal and make a file in "/system" I guess. You can do that using the following command: "touch /system/roottest.txt".
Better answer provided here.
B1nny said:
Uhm open a terminal and make a file in "/system" I guess. You can do that using the following command: "touch /system/roottest.txt".
Click to expand...
Click to collapse
I executed that command but I don't get anything, not even the file in Device>System..
See the Pic..
eclyptos said:
I executed that command but I don't get anything, not even the file in Device>System..
See the Pic..
Click to expand...
Click to collapse
Get root in terminal first by typing
Code:
su
Then mount system as RW and make a directory by typing
Code:
mount -o remount,rw system
mkdir /system/test
or, mount system using root explorer and then do this
Code:
su
mkdir /system/test
Trust me, you have full root....
Ok.
I just Check in.
gregbradley said:
Get root in terminal first by typing
Code:
su
Then mount system as RW and make a directory by typing
adb shell mount -o remount,rw system
mkdir /system/test[/code]
Trust me, you have full root....
Click to expand...
Click to collapse
A bit confused here with that code....
adb shell mount -o remount,rw system
mkdir /system/test[/code]
It have to be like that in Terminal?
eclyptos said:
I just Check in.
A bit confused here with that code....
adb shell mount -o remount,rw system
mkdir /system/test[/code]
It have to be like that in Terminal?
Click to expand...
Click to collapse
Check his post again, he corrected himself.
I edited my post
@gregbradley
I think I have a problem, what you think? It tells me that system/test is Read-Only..
use root explorer to mount system then try the mkdir again
or just root explorer to mount system..as soon as you can do that you have root.....
Full root just means you keep root after a reboot and the security of the RIC has been disabled
gregbradley said:
use root explorer to mount system then try the mkdir again
or just root explorer to mount system..as soon as you can do that you have root.....
Full root just means you keep root after a reboot and the security of the RIC has been disabled
Click to expand...
Click to collapse
I am not familiar with that, which Root Explorer are you referring too?
eclyptos said:
I am not familiar with that, which Root Explorer are you referring too?
Click to expand...
Click to collapse
root explorer
look on the play store
or use any explorer that can gain root...and just modify something in system...change permission, delete or make a file...
if you just reboot your phone and run an app that requires root and it works then you have full root.
gregbradley said:
if you just reboot your phone and run an app that requires root and it works then you have full root.
Click to expand...
Click to collapse
ok...I will try...at the moment I was using ES File Explorer and it not allow me to make or paste any file in system folder...
..I will keep you updated...
eclyptos said:
ok...I will try...at the moment I was using ES File Explorer and it not allow me to make or paste any file in system folder...
Click to expand...
Click to collapse
then you have root, and if you reboot and can still do this you have "full" root
..I will keep you updated...
Click to expand...
Click to collapse
There is no need... I am really unsure on why you are asking this. Seeing as you have posted loads of help posts about this I would expect you to know the difference and know that you have full root.
Trust me, you have it.
eclyptos said:
ok...I will try...at the moment I was using ES File Explorer and it not allow me to make or paste any file in system folder...
..I will keep you updated...
Click to expand...
Click to collapse
If you are not allowed to modify system that's because is not mounted as Rw. Go to ES, make sure you have turned on root explorer and then click on root explorer. A pop up will appear, then select where says mount system as Rw.
gregbradley said:
then you have root, and if you reboot and can still do this you have "full" root
Click to expand...
Click to collapse
This I don't get it...
gregbradley said:
There is no need... I am really unsure on why you are asking this. Seeing as you have posted loads of help posts about this I would expect you to know the difference and know that you have full root.
Trust me, you have it.
Click to expand...
Click to collapse
I know, sometime I cooking my brain instead of my phone and I missing stupid things...and learn small thing.
luis4ever said:
If you are not allowed to modify system that's because is not mounted as Rw. Go to ES, make sure you have turned on root explorer and then click on root explorer. A pop up will appear, then select where says mount system as Rw.
Click to expand...
Click to collapse
You see! OMG! That was the stupid thing...sooo stupid! You are the man. Now everything is working.
ES was granted by Su and it now allow me to modified System files and folders.
After executing the commands in Terminal I find a new folder named "test" in System. Thanx to @gregbradley
Thank you all!
You see! OMG! That was the stupid thing...sooo stupid! You are the man. Now everything is working.
ES was granted by Su and it now allow me to modified System files and folders.
After executing the commands in Terminal I find a new folder named "test" in System.
Thank you all!
Click to expand...
Click to collapse
Glad you solved the problem
wow....
gregbradley said:
wow....
Click to expand...
Click to collapse
lol...
Related
Do u have to have root to push a file?
jm1999 said:
Do u have to have root to push a file?
Click to expand...
Click to collapse
Si... It's needed
i think you can still push to the sdcard without, however thats probably not what youre looking to do
Root refers to superuser level commands. ADB, DDMS are all development tools independent of user privileges.
disgustip8ted said:
i think you can still push to the sdcard without, however thats probably not what youre looking to do
Click to expand...
Click to collapse
Or to any of the folders on the device with write access. Just not system folders (or any folder that's read only, or doesn't even give you read access), which as far as I can tell is the only reason why you'd use adb commands instead of a file browser like astro.
What is the proper way to uninstall apps such as facebook, amazon on a rooted n1?
Any help would be appreciated. sorry for the n00b question.
noonerealy said:
What is the proper way to uninstall apps such as facebook, amazon on a rooted n1?
Any help would be appreciated. sorry for the n00b question.
Click to expand...
Click to collapse
System -> Applications -> Manage -> All
Then select the app and click "Uninstall".
For apps like amazon mp3, you'll need to use adb shell and "rm" apps manually, or use a rom with these removed.
Code:
adb remount
adb shell <---(this should give you a prompt with a "#", not "$")
cd /system/apps (or something along those lines)
rm "specific app" (will be something along the lines of "com.something.android.apk")
That should do it. You just need to find out what the app names are that you want to delete. I'm not sure what all the proper names are, shouldn't be too hard to find.
will this remove data from apps also?
thanx for the answer so fast man, I like things simple and clean.
anyone now how to add the reboot option on stock rooted 2.2?
thanx in advance
I just realized that you can also use Root Explorer from the market.
I located com.amazon.mp3.apk inside /system/app/ folder using Root Explorer
and when i try to delete the file it says "com.amazon.mp3.apk" cannot be deleted because the file system is read-only
okay, so how do i delete this app really?
slickromeo said:
I located com.amazon.mp3.apk inside /system/app/ folder using Root Explorer
and when i try to delete the file it says "com.amazon.mp3.apk" cannot be deleted because the file system is read-only
okay, so how do i delete this app really?
Click to expand...
Click to collapse
adb shell
su
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
or just use
adb remount
I successfully used Root Manager app to remove the amazon mp3 apk. Very simple actually.
slickromeo said:
I located com.amazon.mp3.apk inside /system/app/ folder using Root Explorer
and when i try to delete the file it says "com.amazon.mp3.apk" cannot be deleted because the file system is read-only
okay, so how do i delete this app really?
Click to expand...
Click to collapse
When using Root Explorer, it automatically loads in a read-only (R/O) mode to protect you from accidentally deleting important files. To modify system files, click the gray button at the top left that says R/W (read-write). This will allow you to delete any file regardless of permissions. Be careful.
Can ASTRO do this or does it have to be Root Explorer?
Remove the relevant entry from /data/data as well.
You should probably also update the package manager:
Code:
pm uninstall <package>
galaxys said:
Can ASTRO do this or does it have to be Root Explorer?
Click to expand...
Click to collapse
Astro can delete, but YOU need to remount.
ES File Explorer can remount at CM/HiAPK roms.
thanks. really helpful
Using Nook Color, CM7 nighly 107.
Got Netflix working a while back by modifying the build.prop file using ES File Explorer - no issues.
Tried again to make some mods and cannot save it anymore. ES reports "writable - NO"
Tried to "su chmod 666" it and it comes back with "File system read-only"
Is anybody else seeing this? What am I missing?
Thanks...
I encountered a similar situation during the build.prop edit while using ES File Explorer on my NC running CM7 on internal memory.
Possibly, the permissions in the program need to be changed to enable it to "write".
Here's what I did: Menu==>Settings==>Root options. "Check" Root Explorer and if my memory serves me correctly, click "Yes" to get past the "Experimental Feature", toggle the "Cyanogen Mod" (if you're using CM7) radio button, click OK and check the "Mount File System" box to make the system writable.
Now, it should be writable. Hope this helps.
dhyamato said:
... check the "Mount File System" box to make the system writable.
Click to expand...
Click to collapse
Thanks for the tip, that wasn't it
I remember setting those originally. I just checked again and "Root Explorer" and "Mount FIle System" are both checked.
mwilli20 said:
Using Nook Color, CM7 nighly 107.
Got Netflix working a while back by modifying the build.prop file using ES File Explorer - no issues.
Tried again to make some mods and cannot save it anymore. ES reports "writable - NO"
Tried to "su chmod 666" it and it comes back with "File system read-only"
Is anybody else seeing this? What am I missing?
Thanks...
Click to expand...
Click to collapse
In 106 SU wasn't working correctly until I reinstalled it. You can't modify build.prop without superuser rights. Check the thread about SU / Superuser missing in 106 (and I bet 107) for instructions. It worked for me.
DiDGR8 said:
Check the thread about SU / Superuser missing in 106 (and I bet 107) for instructions. It worked for me.
Click to expand...
Click to collapse
Interesting... the OP withdrew his post: (apparently it's back in 107)
http://forum.xda-developers.com/showthread.php?t=1131369
However when I checked it, the SU app was misbehaving, Force closing, refusing to respond to the menu command. So I reinstalled it. Now it's OK.
Unfortunately I still cannot edit the build.prop file.
I don't think it's a superuser problem because without SU access ES cannot even see the system folder!!! I can see it, and edit the file, just cannot save it.
You might try fixing permissions under recovery.
have you tried the app: nook netflix fixer?
I've changed it successfully on the past 6 consecutive nightlies using adbwireless pull/push. However since 106 I've hsd to reflash su. N108 hasn't given me the su issue. Is it fixed?
Same problem with the build.prop file: cannot save changes, or copy over it. Running in nightly 108 today. Tried both Root Explorer and ES File manager.
I think you need to change the build.prop file properties to be rw using chmod. Don't forget to mount system as rw before doing the chmod.
Sent from my Huawei Ascend using XDA App
foltz61 said:
I think you need to change the build.prop file properties to be rw using chmod.
Click to expand...
Click to collapse
Tried that (sudo chmod 666...), get the same message. "file system is read-only"
backup and restore fresh start....?
I'm not great at linux but I do it differently. Try chmod +rw /system/build.prop . Make sure you have system mounted as RW first. I'd also check superuser to make sure whatever terminal/file explorer you are using still has root privileges.
Sent from my Huawei-M860 using XDA App
foltz61 said:
Try chmod +rw /system/build.prop
Click to expand...
Click to collapse
666 is the same thing as +rw in this case...
It looks like the "fresh start" suggestion a couple of posts up is the best
All those numbers always confuse me . Sorry. Good luck.
Sent from my Huawei-M860 using XDA App
bike2002 said:
have you tried the app: nook netflix fixer?
Click to expand...
Click to collapse
Thanks! That did it!
Does anybody know why this app can modify the build.prop file while ES File Explorer cannot?
I had to mount the folder containing build.prop with rw access in order to use chmod. I think the latest version of the netflix fixer may do the same (see my post in that thread). In short, I used;
Code:
su
busybox mount -0 rw,remount /dev/block/mmcblk1p3 /system
in the terminal before using the chmod command in order to give myself rw permissions in the folder. I'm only two days old at this, so it beats me why root doesn't have normal rw permissions on the folder.
NCKevo said:
I had to mount the folder containing build.prop with rw access in order to use chmod...
Click to expand...
Click to collapse
Thanks for the tip. I ran the command successfully (by the way, small typo, I believe it's -o not -0) and was able to chmod and edit the file with vi.
That's where confusion began. I reboot and after the reboot I was able to modify the file without remounting the /system directory. The mount command does not surive a reboot does it?
Have you tried just pulling the build.prop
Code:
c:/<target_folder> adb pull /system/build.prop
then editing it with note pad then pushing it back and rebooting>
mwilli20 said:
That's where confusion began. I reboot and after the reboot I was able to modify the file without remounting the /system directory. The mount command does not surive a reboot does it?
Click to expand...
Click to collapse
That is confusing. What are the full (i.e. ls -l) permissions on the file now? (It's possible that it somehow ended up with o+w, but I don't understand how - vi isn't exactly known for changing permissions on-the-fly.)
Rodney
Hello,
I need some help with permission setting. Im trying to edit the pppd-ril.options file in system/etc/ppp/peers/ but it is not write enabled.
Using rooted file explorers still brings no avail to setting the write permission.
Tried to use chmod 777 using terminal emulator but it says the system is read only
Also tried exploring with QPST, but can't see the system folder at all.
I need to edit this file as it contains 3G settings I need to adjust.
Help would be much appreciated!
From the terminal
busybox mount -o remount,rw /system
You seem can read chinese
haha
Thanks much! I edited the file and can finally enjoy China Telecom 3G on western ROM!
mvp3 said:
You seem can read chinese
haha
Click to expand...
Click to collapse
Congratulations!
Hashcode said:
Congratulations!
Click to expand...
Click to collapse
just transfered work
Using Root Browser I am unable to delete or rename the install-recovery.sh file. Does anyone know why? Thank you. I also tried ES file explorer.
You need to have R/W privileges. Do you have root?
Mark Once Again said:
You need to have R/W privileges. Do you have root?
Click to expand...
Click to collapse
Yes root has been verified. Thanks for any help you can give Mark.
I use root explorer. Just navigate to the file. Make sure the permissions are R/W. If not, just push the Mount button so that it shows R/W instead of R/O. Should be good to go....
Mark Once Again said:
I use root explorer. Just navigate to the file. Make sure the permissions are R/W. If not, just push the Mount button so that it shows R/W instead of R/O. Should be good to go....
Click to expand...
Click to collapse
Thanks Bro. Good to go now.
I had the same problem, which is how I found this thread, and was not able to resolve it by remounting /system RW. However it turns out the file had the immutable attribute "i". I was able to remove the attribute and delete the file via:
Code:
su
chgattr -i /system/etc/install-recovery.sh
rm /system/etc/install-recovery.sh
recovery upgrade
how to upgrade the recovery. i have a old recovery. i want upgrade it to touch philz recovery plz help