[Q] Unable to adb remount - Sprint HTC EVO 4G LTE

"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.

Related

[Q] Can't mount /system with ADB

So I'm totally unable to do anything to my /system in CWM via ADB.
Code:
> adb remount
remount failed: Operation not permitted
> adb push item.apk /system/app/item.apk
Failed: Permission denied
adb shell
$: su
Segmentation fault
$: rootsh
~# mount /system
mount: mounting /dev/block/mmcblk0p9 on /system failed: Device or resource busy
~# su
# mount /system
mount: mounting /dev/block/mmcblk0p9 on /system failed: Device or resource busy
# mount /system/app
can't find /system/app in /etc/fstab/
Pressing "unmount /system" in CWM results in "Error unmounting /system!" message. I tried pressing "Fix Permissions" but it didn't help. The only thing it did was that "su" results in "Segmentation fault" instead of "Permission denied". I just flashed my Lite'nin ROM again but it didn't fix anything.
I do have root access in normal OS so I can probably do some stuff in terminal emulator. But why is /system busy all the time?
try this:
adb shell
$ su
# mount -o rw,remount -t yaffs2 /dev/block/mmcblk0p9
kaukassus said:
try this:
adb shell
$ su
# mount -o rw,remount -t yaffs2 /dev/block/mmcblk0p9
Click to expand...
Click to collapse
Thanks. That apparently mounted the /system but adb was still unable to push the files there. Maybe that is because "su" is still not working, only "rootsh". So I moved the file to my sdcard and then moved it to /system in shell.
Jiia said:
Thanks. That apparently mounted the /system but adb was still unable to push the files there. Maybe that is because "su" is still not working, only "rootsh". So I moved the file to my sdcard and then moved it to /system in shell.
Click to expand...
Click to collapse
since you are using a Secured Kernel(probably the CF-Root with CWM), you have to push the files to /sdcard
and then copy the files from the sdcard to the /system directory.
you can only push files with adb directly to the /system directory, when you are using an insecured kernel.
kaukassus said:
since you are using a Secured Kernel(probably the CF-Root with CWM), you have to push the files to /sdcard
and then copy the files from the sdcard to the /system directory.
you can only push files with adb directly to the /system directory, when you are using an insecured kernel.
Click to expand...
Click to collapse
Oh. Thanks for the info, that cleared things up! I thought you only need to have a custom recovery in order to push with adb but apparently it's about the kernel.
kaukassus said:
try this:
adb shell
$ su
# mount -o rw,remount -t yaffs2 /dev/block/mmcblk0p9
Click to expand...
Click to collapse
this not working for me ,still can't mount the system i can't rm9 at ADB at all please help me !

[Q] adb remount?

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

Removing Bloat Help

Ok so the Rezound has the bootloader unlocked and rooted with 1click method.
Root Explorer, and Root Checker verify.
Going into adb I am trying to adb rm /system/app/".apk"
It doesnt work.
I tried adb remount and it is not letting me and says operation not permitted.
If I type in adb shell I get the $, then type in su and get #
Titanium Backup. More than worth the money. You can freeze, remove, and backup anything/everything.
Sent from my ADR6425LVW using xda premium
Code:
adb shell
su
busybox mount -o rw,remount -t / rootfs
rm /system/app/NameOfApp.apk
busybox mount -o ro,remount -t / rootfs
adb shell
$ su
su
# busybox mount -o rw,remount -t yaffs2 /rootfs
busybox mount -o rw,remount -t yaffs2 /rootfs
mount: can't find /rootfs in /proc/mounts
# rm /system/app/com.mobitv.client.nfl2010.apk
rm /system/app/com.mobitv.client.nfl2010.apk
rm failed for /system/app/com.mobitv.client.nfl2010.apk, Read-only file system
Try ROM Toolbox. You can find it free in Market.
Code:
busybox mount -o rw,remount -t yaffs2 /dev/block/mmcblk029p /system
This Will Mount The System As "read/write" And Switch It To "ro" To Go Back To "read-only"
Xtreme Outcast said:
Code:
busybox mount -o rw,remount -t yaffs2 /dev/block/mmcblk029p /system
This Will Mount The System As "read/write" And Switch It To "ro" To Go Back To "read-only"
Click to expand...
Click to collapse
I would suggest to drop the extra bits that someone could mis-type and shorten this to
"busybox mount -o remount,rw /system"
It's worked for me and takes a little chance out of the equation. Just my opinion take it for what it's worth.
I Was In A Rush Yesterday That I Typed In The Wrong Code And Just Realized It Now When He Said It Didn't Work. It's All Fixed Thanks For The Suggestions Always Appreciated On My Posts Or Threads.

shell root

any way to shell root any android device to get root access "#" , may be this might have been discussed many times .. I tried lot of ways but none works ..
stiphen said:
any way to shell root any android device to get root access "#" , may be this might have been discussed many times .. I tried lot of ways but none works ..
Click to expand...
Click to collapse
Rooting Android Wear?
jellycoder said:
Rooting Android Wear?
Click to expand...
Click to collapse
i just want to get # instead of $
stiphen said:
i just want to get # instead of $
Click to expand...
Click to collapse
I don't understand what you are trying to say. Kindly define your problem.
stiphen said:
any way to shell root any android device to get root access "#" , may be this might have been discussed many times .. I tried lot of ways but none works ..
Click to expand...
Click to collapse
Sure it's called root, To get full time shell root you unpack your boot.img change the default.prop to insecure repack and flash.
Just like below.
Code:
[email protected]:~/Desktop$ adb shell
[email protected]:/ #
jellycoder said:
I don't understand what you are trying to say. Kindly define your problem.
Click to expand...
Click to collapse
i tried below commands , superuser.apk gets installed and even devices reboots but i still not get root access "#"
Code:
adb devices
adb push psneuter /data/local/tmp
adb shell
$ cd /data/local/tmp
$ chmod 777 psneuter
$ ./psneuter
adb kill-server
adb devices
adb shell
# mount -o remount,rw -t rfs /dev/block/st19 /system
# exit
adb push busybox /system/bin
adb push su /system/bin
adb install Superuser.apk
adb shell
# chmod 4755 /system/bin/busybox
# chmod 4755 /system/bin/su
# mount -o remount,ro -t rfs /dev/block/st19 /system
# exit
adb reboot
stiphen said:
i tried below commands , superuser.apk gets installed and even devices reboots but i still not get root access "#"
Code:
adb devices
adb push psneuter /data/local/tmp
adb shell
$ cd /data/local/tmp
$ chmod 777 psneuter
$ ./psneuter
adb kill-server
adb devices
adb shell
# mount -o remount,rw -t rfs /dev/block/st19 /system
# exit
adb push busybox /system/bin
adb push su /system/bin
adb install Superuser.apk
adb shell
# chmod 4755 /system/bin/busybox
# chmod 4755 /system/bin/su
# mount -o remount,ro -t rfs /dev/block/st19 /system
# exit
adb reboot
Click to expand...
Click to collapse
Try
adb shell
su
vampirefo said:
Try
adb shell
su
Click to expand...
Click to collapse
/system/bin/sh: su: not found
stiphen said:
/system/bin/sh: su: not found
Click to expand...
Click to collapse
you have to have su for # to work.
vampirefo said:
you have to have su for # to work.
Click to expand...
Click to collapse
ok thanks i rooted my device with Impactor
stiphen said:
ok thanks i rooted my device with Impactor
Click to expand...
Click to collapse
Adbd insecure app also works. In your shell, just type SU and accept the SuperSU/SuperUser prompt

permission denied to write file despite rooted

I'm trying to put some firmware file under /system/vendor/firmware or /system/etc/firmware, it shows the fs is read only, so I remounted /system/ as read/write with
Code:
mount -o rw,remount /system
, and used su, but when I try to create any file under these 2 location, a permission denied error still occurs. I tried to do so in both termux and adb, the same result. What's causing this? Thanks
@kdlsw
Try
Code:
adb shell "su -c 'mount -o rw,remount -t auto /system'"
jwoegerbauer said:
@kdlsw
Try
Code:
adb shell "su -c 'mount -o rw,remount -t auto /system'"
Click to expand...
Click to collapse
Tried it, still the same error.
I'm not sure if this is the remount problem, if I don't remount, the error is different (Read-only file system), after remount it's permission denied.
@kdlsw
I'm pretty sure the MOUNT worked successfully, otherwise you'ld have got an error returned: I guess you got returned "remount succeeded".
It seems to me dm_verity is enabled what blocks writing to /system: Hence disable it and reboot, then run commands as needed
Code:
adb devices
adb disable-verity 2>nul >nul
adb reboot
adb wait-for-device
adb shell "su -c 'mount -o rw,remount -t auto /system'"
<YOUR ADDITIONAL COMMANDS HERE>
jwoegerbauer said:
@kdlsw
I'm pretty sure the MOUNT worked successfully, otherwise you'ld have got an error returned: I guess you got returned "remount succeeded".
It seems to me dm_verity is enabled what blocks writing to /system: Hence disable it and reboot, then run commands as needed
Code:
adb devices
adb disable-verity 2>nul >nul
adb reboot
adb wait-for-device
adb shell "su -c 'mount -o rw,remount -t auto /system'"
<YOUR ADDITIONAL COMMANDS HERE>
Click to expand...
Click to collapse
thank you! I'll try this! I also found a workaround, mounting the directory in recovery, and the problem is gone. Thanks!

Categories

Resources