[Q] Project-V adb Root access - Vibrant Q&A, Help & Troubleshooting

I have recently switched back to Project-V and adb does not seem to have root access. When I try the command "adb remount" I get the error: "remount failed: operation not permitted"
I am able to manually mount my system r/w with Root Explorer, but not with adb. Any ideas?

Check your permissions of root with superuser.

Related

[Q] /system folder read/write via adb remount

Hi,
I recently pushed some fixes to my Hero's system folder and mounted it with read/write access via the adb remount command. All this is as expected so no problems. I was wondering however if I could remount it with read only access again, just for security until I need to gain access again.
Any help or tips with this would be appreciated!
Update:
OK guys sorry but I have answered my own question here. Digifail had the info!
"adb remount
This command remounts /system to be read/write, rather than the default read-only. Useful when modifying system applications or other root-only operations. It is advised to reboot after using this option so that the system will mount /system read-only again (for whatever reason, running "adb remount" a second time does not return /system to read-only status). "
Guess a reboot will sort this.

[Q] Rooted or not?

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

[Q] Help With VM heapsize

Right now i have a boot loop. What i did was that I changed the heapsize to 12 in the /system/build.prop (wanted to be fast) and now it just wont boot. I guess its too low so i did a logcat on adb and it says:
Code:
W/dalvikvm( 1323): JNI_CreateJavaVM failed
E/AndroidRuntime( 1323): JNI_CreateJavaVM failed
Luckily, root explorer saves everything with a file ending .bak. What I did was I used adb to pull the file, renamed it to simply build.prop but when I try to push it back into /system/ it says that the partition is only in read-only. So i try to adb shell and remount the system partition but then I get:
Code:
C:\Users\Alex>adb shell
$ su
su
[1] + Stopped (signal) su
$ su
su
[2] + Stopped (signal) su
[1] Segmentation fault su
What do i do?!?!!?? help, i've tried my best..... oh, and my phone is the motorla spice xt300 running 2.1 stock
Restore to previous working condition backup will do.
Accidentally sent from my Google Nexus S using XDA Premium
only problem is that development isnt that good for my phone. plus it has a locked bootloader which makes it worse so I dont have a nandroid backup.
You should be able to change it with Root Explorer. Did you make sure to check the R/W option on Root Explorer? It will then allow you to change read-only files.
prboy1969 said:
You should be able to change it with Root Explorer. Did you make sure to check the R/W option on Root Explorer? It will then allow you to change read-only files.
Click to expand...
Click to collapse
He's in a boot loop
Sent from my Transformer TF101 using Tapatalk
yeah, being in a bootloop really sucks.....
Bump, anyone know how to fix this problem?
Bump again, phone still in bootloop ):
Bump again ):

[Q] unable to chmod read-only file system

Hi,
i've rooted my vodafone 858 but it didn't install super user although i can type "su" command in adb shell.
now i'm trying to delete files located in /mnt/asec (downloaded packages) due to low phone memory.
so i tried to do it but when i do the command "rm" for files located in there it tells me permission denied so i entered super user mode and i tried "rm" it tells me "unable to chmod <path> read-only file system" so how can i get past the read only?
Wich way did u use to root ur phone?
I think you´ll need the superuser.apk and the terminal emulator.apk
In the emulator u might type in you commands like su and the emulator will request root acces.
This way worked for me
Get superuser + busybox and why not use some root file manager to remove them?
Sent from Galaxy Ace which just landed on "MOON"

Permanent root for zte citrine? (zte 716bl) rw permissions?

I Have root but when I change permissions of /System with root explorer it says I can't change it. I have tried adb and several RW commands to mount system as RW oon Terminal Emulator. Also when I reboot root is lost. I used KingoRoot. Please help me to get permanent root and disable kernel write protection. So we can gain access to permanent root! What am I missing guys?

Categories

Resources