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 !
Related
Hello all,
I am trying to push a file to my system, however I do not seem to be able to mount my system partition.
When I try to execute the following command, I always get the error "Operation not permitted" :
Code:
adb shell mount -o remount,rw -t yaffs2 /dev/block/mtdblock2 /system
My phone is rooted and my USB debugging is on !!
Anyone no what could cause this. It has always worked when I was still on 1.6 (rooted) and now it doesn't allow me access.
When I use Rootexplorer, I have R/W access, so root works.
Anyone has any tips or advise ?
Try...
adb shell
su
mount -o remount,rw -t yaffs2 /dev/block/mtdblock2 /system
Tried that, and get permission denied
Should have added, make sure your screens on on the phone and allow SuperUser access when you type su.
never mind, one sec
Hi,
I have just installed wolfs 2.3 with hotfix and am having trouble with adb commands
I have tried pushing files to /data/data and I get this error
Code:
failed to copy 'name of file here' to 'path here' : Permission denied
However, if i boot into recovery and manually mount data it works.
My question is
what is the code to mount the data partition from adb?
I know
Code:
adb remount
mounts the system partition but i need the data partition mounted.
I have never ran into this before, all my adb commands worked whilst the phone was turned on...
any help please.
More issues
Code:
adb remount
does not work....permission denied
Also, using apk manager I cannot push sytem files to /system/app
This is quite irritating
The correct command is:
Code:
mount -o remount,rw -t yaffs2 /dev/block/mtdblock2 /system
Code:
adb shell
su
mount -o remount rw /system
works for me.
How can I do this without a sd card... thanks in advance.
Sent from my LG-VM670 using Tapatalk
Flash the recovery image?
Root
Adb push a flash_image binary to /system/bin or xbin
adb push recovery.image to /cache or something
flash_image recovery /cache/recovery.img
I'm trying to flash the recovery without a SD card, because my phone can't mount a SD card anymore. So I'm using the recovery here http://www.lg-phones.org/lg-optimus-v-custom-recovery.html and Flash_image to flash it, but I need ADB codes to do so. I'm not very good with ADB, so I need the ones without the flash_image recovery /sdcard/ recovery-thunderc-v-1.2.0-GNM.img /sdcard/ part. :/
Curiousn00b said:
I'm trying to flash the recovery without a SD card, because my phone can't mount a SD card anymore. So I'm using the recovery here http://www.lg-phones.org/lg-optimus-v-custom-recovery.html and Flash_image to flash it, but I need ADB codes to do so. I'm not very good with ADB, so I need the ones without the flash_image recovery /sdcard/ recovery-thunderc-v-1.2.0-GNM.img /sdcard/ part. :/
Click to expand...
Click to collapse
It the same thing as tvall has mentioned but I will make it more easy for you.
As mentioned in the link that you have provided, just do this instead:
A) Type in 'adb remount'
B) Copy recovery-thunderc-v-1.2.0-GNM.img to platform-tools directory where android SDK is installed.
C) Do a 'adb push recovery-thunderc-v-1.2.0-GNM.img /system/xbin'
[Now the recovery image is inside your phones memory @/system/xbin location]
Following are the existing steps from the link: Modified step is made bold.
1) mount -o remount,rw -t yaffs2 /dev/block/mtdblock5 /system
2) cat /sdcard/flash_image > /system/bin/flash_image
3) chmod 755 /system/bin/flash_image
4) mv /system/etc/install-recovery.sh /system/etc/install-recovery.sh.bak
5) mount -o remount,ro -t yaffs2 /dev/block/mtdblock5 /system
6) flash_image recovery /system/xbin/recovery-thunderc-v-1.2.0-GNM.img
7) reboot recover
tvall said:
Flash the recovery image?
Root
Adb push a flash_image binary to /system/bin or xbin
adb push recovery.image to /cache or something
flash_image recovery /cache/recovery.img
Click to expand...
Click to collapse
developer++ said:
It the same thing as tvall has mentioned but I will make it more easy for you.
As mentioned in the link that you have provided, just do this instead:
A) Type in 'adb remount'
B) Copy recovery-thunderc-v-1.2.0-GNM.img to platform-tools directory where android SDK is installed.
C) Do a 'adb push recovery-thunderc-v-1.2.0-GNM.img /system/xbin'
[Now the recovery image is inside your phones memory @/system/xbin location]
Following are the existing steps from the link: Modified step is made bold.
1) mount -o remount,rw -t yaffs2 /dev/block/mtdblock5 /system
2) cat /sdcard/flash_image > /system/bin/flash_image
3) chmod 755 /system/bin/flash_image
4) mv /system/etc/install-recovery.sh /system/etc/install-recovery.sh.bak
5) mount -o remount,ro -t yaffs2 /dev/block/mtdblock5 /system
6) flash_image recovery /system/xbin/recovery-thunderc-v-1.2.0-GNM.img
7) reboot recover
Click to expand...
Click to collapse
Thanks alot guys, I really appreciate it, but I get stuck at
C:\android-sdk\platform-tools>adb remount
remount succeeded
C:\android-sdk\platform-tools>adb push recovery-thunderc-v-1.2.0-GNM.img /system
/xbin
cannot stat 'recovery-thunderc-v-1.2.0-GNM.img': No such file or directory
C:\android-sdk\platform-tools>
I'm starting to learn more, as I knew alot back when I first rooted my phone. As time went by..... easier ways were made.
Help plz.
EDIT: Been messing around with it, but still no go. This is what I got. Keep in mind I messed with some stuff if it doesn't look right..... :s
C:\android-sdk\platform-tools>adb remount
remount succeeded
C:\android-sdk\platform-tools>adb shell
# mount -o remount,rw -t yaffs2 /dev/block/mtdblock5 /system
mount -o remount,rw -t yaffs2 /dev/block/mtdblock5 /system
# chmod 755 /system/bin/flash_image
chmod 755 /system/bin/flash_image
# mv /system/etc/install-recovery.sh /system/etc/install-recovery.sh.bak
mv /system/etc/install-recovery.sh /system/etc/install-recovery.sh.bak
mv: can't rename '/system/etc/install-recovery.sh': No such file or directory
# mount -o remount,ro -t yaffs2 /dev/block/mtdblock5 /system
mount -o remount,ro -t yaffs2 /dev/block/mtdblock5 /system
# flash_image recovery /system/xbin/recovery-thunderc-v-1.2.0-GNM.img
flash_image recovery /system/xbin/recovery-thunderc-v-1.2.0-GNM.img
failed with error: -1
error reading /system/xbin/recovery-thunderc-v-1.2.0-GNM.img header# flash_image
recovery /system/xbin/recovery-thunderc-v-1.2.0-GNM.img
flash_image recovery /system/xbin/recovery-thunderc-v-1.2.0-GNM.img
failed with error: -1
error reading /system/xbin/recovery-thunderc-v-1.2.0-GNM.img header# /system/xbi
n/flash_image recovery /system/xbin/recovery-thunderc-v-1.2.0-GNM.img
/system/xbin/flash_image recovery /system/xbin/recovery-thunderc-v-1.2.0-GNM.img
/system/xbin/flash_image: permission denied
#
Bump...
Sent from my LG-VM670 using Tapatalk
I have made inline comments. Just take note of it.
Curiousn00b said:
C:\android-sdk\platform-tools>adb remount
remount succeeded
C:\android-sdk\platform-tools>adb push recovery-thunderc-v-1.2.0-GNM.img /system
/xbin
cannot stat 'recovery-thunderc-v-1.2.0-GNM.img': No such file or directory
Click to expand...
Click to collapse
Here the 'recovery-thunderc-v-1.2.0-GNM.img' file should be present inside the C:\android-sdk\platform-tools directory. Also check if the spelling is correct.
Curiousn00b said:
C:\android-sdk\platform-tools>adb remount
remount succeeded
C:\android-sdk\platform-tools>adb shell
# mount -o remount,rw -t yaffs2 /dev/block/mtdblock5 /system
mount -o remount,rw -t yaffs2 /dev/block/mtdblock5 /system
# chmod 755 /system/bin/flash_image
chmod 755 /system/bin/flash_image
# mv /system/etc/install-recovery.sh /system/etc/install-recovery.sh.bak
mv /system/etc/install-recovery.sh /system/etc/install-recovery.sh.bak
mv: can't rename '/system/etc/install-recovery.sh': No such file or directory
Click to expand...
Click to collapse
This error came because there is no file called 'install-recovery.sh' inside /system/etc. This is fine since you are anyways not going to use that file.
Curiousn00b said:
# mount -o remount,ro -t yaffs2 /dev/block/mtdblock5 /system
mount -o remount,ro -t yaffs2 /dev/block/mtdblock5 /system
# flash_image recovery /system/xbin/recovery-thunderc-v-1.2.0-GNM.img
flash_image recovery /system/xbin/recovery-thunderc-v-1.2.0-GNM.img
failed with error: -1
error reading /system/xbin/recovery-thunderc-v-1.2.0-GNM.img header# flash_image
recovery /system/xbin/recovery-thunderc-v-1.2.0-GNM.img
flash_image recovery /system/xbin/recovery-thunderc-v-1.2.0-GNM.img
failed with error: -1
error reading /system/xbin/recovery-thunderc-v-1.2.0-GNM.img header# /system/xbi
n/flash_image recovery /system/xbin/recovery-thunderc-v-1.2.0-GNM.img
/system/xbin/flash_image recovery /system/xbin/recovery-thunderc-v-1.2.0-GNM.img
/system/xbin/flash_image: permission denied
#
Click to expand...
Click to collapse
This part I am not that clear but it might be that the recovery 'recovery-thunderc-v-1.2.0-GNM.img' is corrupt or may be 'flash_image' is corrupt. You can also check for the amount of free memory by typing in 'df' and 'free' respectively. df would give you phone memory stats and free would give you RAM stats. Verify if anything is too low.
For the last permission denied error do a 'ls -l' at /system/xbin and check for the permissions.
I will look around to see if I can get some clues till then, lets wait for someone who can help you better.
[ADVICE: Since you are playing around with system binaries make sure you take a backup of /system/bin atleast.]
developer++ said:
I have made inline comments. Just take note of it.
Here the 'recovery-thunderc-v-1.2.0-GNM.img' file should be present inside the C:\android-sdk\platform-tools directory. Also check if the spelling is correct.
This error came because there is no file called 'install-recovery.sh' inside /system/etc. This is fine since you are anyways not going to use that file.
This part I am not that clear but it might be that the recovery 'recovery-thunderc-v-1.2.0-GNM.img' is corrupt or may be 'flash_image' is corrupt. You can also check for the amount of free memory by typing in 'df' and 'free' respectively. df would give you phone memory stats and free would give you RAM stats. Verify if anything is too low.
For the last permission denied error do a 'ls -l' at /system/xbin and check for the permissions.
I will look around to see if I can get some clues till then, lets wait for someone who can help you better.
[ADVICE: Since you are playing around with system binaries make sure you take a backup of /system/bin atleast.]
Click to expand...
Click to collapse
I tried again about 8 hours ago. I got through everything with no error, but when I got to recovery, it was still the old one. I'll try again once I get home.
Sent from my LG-VM670 using Tapatalk.
Other option (if your phone is rooted)
Install RomManager and install CWM or alternative.
If you're not rooted you need to do that first.
After that you can flash any recovery you want and you don't need to mess with adb
You can try to flash a recovery via LGMDP. I've flashed CWM 4.0 by this way.
_Arjen_ said:
Other option (if your phone is rooted)
Install RomManager and install CWM or alternative.
If you're not rooted you need to do that first.
After that you can flash any recovery you want and you don't need to mess with adb
Click to expand...
Click to collapse
Rom manager bricks the Optimus.
Dan_Jacques said:
You can try to flash a recovery via LGMDP. I've flashed CWM 4.0 by this way.
Click to expand...
Click to collapse
Sent from my LG-VM670 using Tapatalk
I got it flashed, thanks to Jerryscript.
Sent from my LG-VM670 using Tapatalk
Curiousn00b said:
Rom manager bricks the Optimus.
Sent from my LG-VM670 using Tapatalk
Click to expand...
Click to collapse
well most time i did it via rom manger and all time it was a sucess ,still lgmdp is good option but rom manger does it quiet easily just make sure u ahve a good internet connection so that its not disrupted when downloading better connected via wifi orelse better to go wth lgmdp method
Curiousn00b said:
I got it flashed, thanks to Jerryscript.
Sent from my LG-VM670 using Tapatalk
Click to expand...
Click to collapse
You can share the solution and provide a link so that in the future if someone has the same problem he can visit this thread and get things sorted out.
Edit the title of the thread to SOLVED
developer++ said:
You can share the solution and provide a link so that in the future if someone has the same problem he can visit this thread and get things sorted out.
Edit the title of the thread to SOLVED
Click to expand...
Click to collapse
I never found out how to change the thread name.
And ill edit the post tomorrow. I also have another question.
Sent from my LG-VM670 using Tapatalk
Can someone with a sd card, and adb, test this out? I don't want to test it out, cause without a sd card mounter, if it doesn't work, I'm screwed. If it doesn't work, I'm sure you have a nandroid on your sd card, hopefully. Please and thank you.
http://www.addictivetips.com/mobile/how-to-install-a-rom-to-an-android-phone-device-without-sd-card/
Sent from my LG-VM670 using Tapatalk
"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 have an Acer A210 and have modified the boot.img to have ro.secure=0 and ADB root. Then I had to mount the /system partition but that is not so easy:
Code:
C:\>adb shell
[email protected]:/ # mount -o remount,rw /system
mount -o remount,rw /system
mount: Operation not permitted
C:\>adb push busybox /data/local/tmp
1065 KB/s (777216 bytes in 0.712s)
126|[email protected]:/data/local/tmp # chmod 755 busybox
chmod 755 busybox
[email protected]:/data/local/tmp # ./busybox mount -o remount,rw /system
./busybox mount -o remount,rw /system
mount: permission denied (are you root?)
Currently the only way to mount /system rw is this:
Code:
cd /system/xbin/
mount -o remount,rw /dev/block/platform/sdhci-tegra.3/by-name/APP /system/
So now I have root (pushed su and busybox from A510 and installed SuperUser from ChainsDD) but installed applications that want to mount /system rw cannot do that. I think because of the mounting problem. Also a custom CWM 6.0.1.4 cannot mount /sdcard but it works with ADB.
Thanks for help with that!
MaluNoPeleke said:
So now I have root (pushed su and busybox from A510 and installed SuperUser from ChainsDD) but installed applications that want to mount /system rw cannot do that. I think because of the mounting problem. Also a custom CWM 6.0.1.4 cannot mount /sdcard but it works with ADB.
Thanks for help with that!
Click to expand...
Click to collapse
Acer implemented in kernel "system RW protection" (I don't know how to call that)- kernel prohibits such operations. Only workaround is compiling a custom kernel with this feature disabled.
As for recovery- check /etc/fstab if sdcard mountpoint (stored in init.rc or init.[device name].rc) matches the one recovery uses (/etc/fstab)
Thanks for that! Is it hard to disable the system rw security in the kernel? I haven't done that before. Is there a tutorial from another Acer tablet?
How can I check the fstab content in the recovery? It was built by the recovery builder.
Thanks!
MaluNoPeleke said:
Thanks for that! Is it hard to disable the system rw security in the kernel? I haven't done that before. Is there a tutorial from another Acer tablet?
Click to expand...
Click to collapse
It's a kernel config option only, for a510 it's CONFIG_ACER_SECURE_MOUNT and it is accessible in menuconfig or by hand- in .config change "CONFIG_ACER_SECURE_MOUNT=yes" to "# CONFIG_ACER_SECURE_MOUNT is not set" (as for kernel compilation- there are many tutorials floating around)
MaluNoPeleke said:
How can I check the fstab content in the recovery? It was built by the recovery builder.
Click to expand...
Click to collapse
Start recovery and just
Code:
adb shell
cat /etc/fstab
or
Code:
adb pull /etc/fstab [path on your pc]
I've never used any recovery builder but kernel and ramdisk/initramfs (where recovery is placed) are separate files, you can unpack boot.img and just modify what you need (note- linux machine required, virtual one will do)
Is it already disabled in the source code?
Code:
[email protected] ~/Dokumente/kernel $ grep -R -i 'CONFIG_ACER_SECURE_MOUNT*' ./*
./arch/arm/configs/picasso_mf_defconfig:# CONFIG_ACER_SECURE_MOUNT is not set
./arch/arm/configs/picasso_m_defconfig:# CONFIG_ACER_SECURE_MOUNT is not set
./arch/arm/configs/picasso_e_defconfig:# CONFIG_ACER_SECURE_MOUNT is not set
./arch/arm/configs/picasso_e2_defconfig:# CONFIG_ACER_SECURE_MOUNT is not set
./arch/arm/configs/picasso2_defconfig:# CONFIG_ACER_SECURE_MOUNT is not set
./fs/Makefile:ifeq ($(CONFIG_ACER_SECURE_MOUNT),y)
It seems that it's disabled.
Is there a zip file for Acer 210 tablet now 4/2013
dobie62 said:
Is there a zip file for Acer 210 tablet now 4/2013
Click to expand...
Click to collapse
There is a real lot available for A210:
Pure root (German)
CWM recovery (German)
Custom Kernel
CM 10.1 like ROM
What are you looking for?
regards Uwe
This is it but in English please.
A210
Are the A210 and the A510 similar enough to use the same kernel, ROM's or Recovery?