im running 2.3.4 android version..
unlocked bootloader....followed the instruction in this link to root my atrix
http://forum.xda-developers.com/showthread.php?t=1202883
but after entering this command
/preinstall/dosu
im getting this error..
please see cmd log below
C:\>cd atrix
C:\atrix>adb shell
$ /preinstall/dosu
/preinstall/dosu
bash: groups: command not found
[email protected]:/# /bin/mount -o remount,rw /system
/bin/mount -o remount,rw /system
[email protected]:/# cp /preinstall/su /system/bin/
cp /preinstall/su /system/bin/
cp: write error: Read-only file system
[email protected]:/# chmod 6755 /system/bin/su
chmod 6755 /system/bin/su
chmod: /system/bin/su: Read-only file system
[email protected]:/#
vdpraneeth said:
im running 2.3.4 android version..
unlocked bootloader....followed the instruction in this link to root my atrix
http://forum.xda-developers.com/showthread.php?t=1202883
but after entering this command
/preinstall/dosu
im getting this error..
please see cmd log below
C:\>cd atrix
C:\atrix>adb shell
$ /preinstall/dosu
/preinstall/dosu
bash: groups: command not found
[email protected]:/# /bin/mount -o remount,rw /system
/bin/mount -o remount,rw /system
[email protected]:/# cp /preinstall/su /system/bin/
cp /preinstall/su /system/bin/
cp: write error: Read-only file system
[email protected]:/# chmod 6755 /system/bin/su
chmod 6755 /system/bin/su
chmod: /system/bin/su: Read-only file system
[email protected]:/#
Click to expand...
Click to collapse
this is the other more error im getting
# /bin/mount /system -o remount,rw
/bin/mount /system -o remount,rw
mount: block device /dev/block/mmcblk0p12 is write-protected, mounting read-only
/system file remains read only
vdpraneeth said:
im running 2.3.4 android version..
unlocked bootloader....followed the instruction in this link to root my atrix
http://forum.xda-developers.com/showthread.php?t=1202883
but after entering this command
/preinstall/dosu
im getting this error..
please see cmd log below
C:\>cd atrix
C:\atrix>adb shell
$ /preinstall/dosu
/preinstall/dosu
bash: groups: command not found
[email protected]:/# /bin/mount -o remount,rw /system
/bin/mount -o remount,rw /system
[email protected]:/# cp /preinstall/su /system/bin/
cp /preinstall/su /system/bin/
cp: write error: Read-only file system
[email protected]:/# chmod 6755 /system/bin/su
chmod 6755 /system/bin/su
chmod: /system/bin/su: Read-only file system
[email protected]:/#
Click to expand...
Click to collapse
I have an unlocked AT&T Atrix (MB860) with GB 2.3.4 and I have exactly the same problem: that the /system folder remains stubbornly read only, no matter what I do. I have tried a lot of the methods I found in the forums and elsewhere, but to no avail. I suspect the only effective solution will be to install a full .sbf image with an already rooted /system folder, but that will be the very last resort. We are not the only ones with this problem; I have seen the messages of a few others. On some phones, the easy methods just do not seem to work.
So, have you, or others, found an acceptable solution other than to install a rooted sbf image?
I'm a Sony user so not sure if this applies too but is USB debugging on?
Sent from my LT18i using xda premium
/system remains read only
I have an unlocked AT&T Atrix (MB860) with GB 2.3.4 and I have exactly the same problem: that the /system folder remains stubbornly read only, no matter what I do. I have tried a lot of the methods I found in the forums and elsewhere, but to no avail. I suspect the only effective solution will be to install a full .sbf image with an already rooted /system folder, but that will be the very last resort. We are not the only ones with this problem; I have seen the messages of a few others. On some phones, the easy methods just do not seem to work.
So, have you, or others, found an acceptable solution other than to install a rooted sbf image?
I don't remember how i rooted the phone but specifing the filesystem might help
try using
/system/bin/mount -t ext3 -o remount,rw /system
Click to expand...
Click to collapse
Related
can't remount...trying to push .apk
sh-3.2# ./adb devices
List of devices attached
TA07302MDF device
sh-3.2# ./adb remount
remount failed: Operation not permitted
sh-3.2# ./adb shell
$ su
#
you can see i have root
droid x2 liberty 3 rom moto one click root
fixed it for anyone else having trouble
sh-3.2# ./adb devices
List of devices attached
TA07302MDF device
sh-3.2# ./adb remount
remount failed: Operation not permitted
sh-3.2# ./adb shell
$ su
# mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
# chmod 777 /system/framework
# exit
$ exit
sh-3.2# ./adb push framework-res.apk system/framework/
1055 KB/s (4096287 bytes in 3.788s)
sh-3.2#
thetdy said:
fixed it for anyone else having trouble
sh-3.2# ./adb devices
List of devices attached
TA07302MDF device
sh-3.2# ./adb remount
remount failed: Operation not permitted
sh-3.2# ./adb shell
$ su
# mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
# chmod 777 /system/framework
# exit
$ exit
sh-3.2# ./adb push framework-res.apk system/framework/
1055 KB/s (4096287 bytes in 3.788s)
sh-3.2#
Click to expand...
Click to collapse
accually you could just us this
# mount -o remount,rw /dev/block/mtdblock3 /system
should work just fine without the -t yaffs2 i know it works on the samsungs
Hello, I have a serious problem.
I am using adb for hacking my Android Galaxy 5 smartphone.
Wifi got broken because I can't make file /data/misc/wifi/wpa_supplicant.conf executable.
Issuing chmod 755 have no effect, even after remounting the system as rw with command
Code:
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
Consequence: Wifi is broken. I have no idea about how to prevent this behaviour of chmod. Can you help me?
Solved: I was confunding two files: wpa_supplicant and wpa_supplicant.conf. Sorry
"Operation not permitted"
What is causing this? I really want to push some files to my EVO.
Help
I have done it previously on other Roms i have flashed. I am currently on Goodies 1.5.
typhoonikan said:
"Operation not permitted"
What is causing this? I really want to push some files to my EVO.
Help
I have done it previously on other Roms i have flashed. I am currently on Goodies 1.5.
Click to expand...
Click to collapse
I believe the adb binary has to be replaced with one that has permission to do this, it is often disabled in stock builds.
an easy way around this is
adb shell
su
mount -o remount rw, /system
modplan said:
I believe the adb binary has to be replaced with one that has permission to do this, it is often disabled in stock builds.
an easy way around this is
adb shell
su
mount -o remount rw, /system
Click to expand...
Click to collapse
I typed just as you did. No help.
My results as copy and pasted:
c:\Android>adb shell
[email protected]:/ $ su
su
[email protected]:/ # mount -o remount rw, /system
mount -o remount rw, /system
[email protected]:/ # exit
exit
[email protected]:/ $ exit
exit
c:\Android>adb remount
remount failed: Operation not permitted
typhoonikan said:
I typed just as you did. No help.
My results as copy and pasted:
c:\Android>adb shell
[email protected]:/ $ su
su
[email protected]:/ # mount -o remount rw, /system
mount -o remount rw, /system
[email protected]:/ # exit
exit
[email protected]:/ $ exit
exit
c:\Android>adb remount
remount failed: Operation not permitted
Click to expand...
Click to collapse
What I posted remounts the system partition read/write. No need to adb remount after that, you can write to /system at that point.
I am trying to make a simple shell script and I am getting constant errors.
So i made a test.sh file and saved it in /data because /sdcard is excuetable protected.
The shell file contains:
#!/system/bin/sh
cd /sdcard
mkdir test
su -c "rm /data/test.sh"
echo Done!
So then I typed the command chmod 777 /data/test.sh
I also tried chown root:shell /data/test.sh
And then /data/test.sh and it returned: tmp-mksh: /data/test.sh: No such file or directory
So then I tried running: sh /data/test.sh and it returned:
No such file or directoryrd
Done
I even tried executing the script from a root shell interface but still no luck same result as above.
Forgot to mention I am running 4.4.4 on a moto g that is rooted and has busybox installed.
HI,
I can't delete "/system/etc/install-recovery.sh" on my rooted device.
Code:
[email protected]:/ $ su
su
[email protected]:/ # mount -o remount,rw /system
mount -o remount,rw /system
[email protected]:/ # cd /system/etc
cd /system/etc
[email protected]:/system/etc # rm install-recovery.sh
rm install-recovery.sh
rm failed for install-recovery.sh, Operation not permitted
255|[email protected]:/system/etc # chown shell install-recovery.sh
chown shell install-recovery.sh
Unable to chown install-recovery.sh: Operation not permitted
10|[email protected]:/system/etc #
Anyone knows why ?
(My device is Redmi 1 by the way)
Thanks.
Slash