Hello
I tried to download the android 5.1.1 on my Gear S but when i try to enter the commands in Adb shell
mount: mounting /dev/block/mmcblk0p24 on /data failed: Device or resource busy
Related
Hi,
I succeeded at installing the recovery image using flashrec and making the nandroid backup. Now I'm trying to go to the next step of the rooting tutorial for noobs: MODIFYING THE CODE TO GET ROOT ACCESSS
This is my cmd (administrator rights) in Fastboot USB Mode:
Code:
c:\sdk\tools>fastboot devices
HT**KL****** fastboot
c:\sdk\tools>adb devices
adb server is out of date. killing...
* daemon started successfully *
List of devices attached
This is my cmd (administrator rights) in "normal mode":
Code:
c:\sdk\tools>adb devices
List of devices attached
HT**KL****** device
c:\sdk\tools>adb shell mount /system
Usage: mount [-r] [-w] [-o options] [-t type] device directory
c:\sdk\tools>adb push su /system/bin/
failed to copy 'su' to '/system/bin//su': Read-only file system
c:\sdk\tools>adb push su /system/bin
failed to copy 'su' to '/system/bin/su': Read-only file system
c:\sdk\tools>adb shell rm /system/app/Superuser.apk
rm failed for /system/app/Superuser.apk, Read-only file system
c:\sdk\tools>adb push su /system/bin/
failed to copy 'su' to '/system/bin//su': Read-only file system
c:\sdk\tools>adb shell mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /syste
m
mount: Operation not permitted
c:\sdk\tools>adb shell chmod 777 /system
Unable to chmod /system: Read-only file system
I am running Windows 7 (x64), I downloaded the latest adb tools and usb drivers using SDK Setup.exe. I installed the ADB drivers properly (using the manual wizard to browse to the usb_driver folder and restarting my computer) for the fastboot USB and for "normal mode" with the option debugging usb active.
Information of my current Rom ("Orange Belgium")
HBOOT-1.76.0007 (HERO10000)
RADIO-6.35.06.18
Aug 4 2009,19:43:30
I couldn't find anything by google that solved the problem... I hope you guys can help me out..
First and foremost, please post questions like this in the Q&A, or GENERAL section next time. This part will be moved for you though.
Ok,... I think your making this more difficult than need be. I haven't looked at the link you provided as my phone is playing up..
Take a look at BTDAGs guide linked in my signature... If you have already successfully installed the custom recovery, all you need to do now is pick a custom ROM to download and flash using the recovery.
Sent from my HTC Hero using XDA App
That is quite an old guide you're following. Try mine, or the one here http://villainrom.co.uk/viewtopic.php?f=107&t=2028 or there is universal androot - which will just give you root access on any rom.
you should use this to mount system in read/write-mode:
Code:
# mount -o rw -t yaffs2 /dev/block/mtdblock3 /system
alternatively put adb shell in front of:
Code:
>adb shell mount -o rw -t yaffs2 /dev/block/mtdblock3 /system
And by the way, you should do this from recovery mode (which is accessed by keeping home-button pressed down while turning on. I assume that you have a custom recovery)
Moved to Q&A as not development
Managed to put the recovery rom on it, thanks!
sorry to post it this late. can you pls explain how you resolve? if its available in some other thread, can someone guide me there. have been doing search on the forum for a while now. thanks!
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
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 !
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.
i need to mount android emulator system partion as rw by adb commands
adb -s emulator-5554 shell mount -o rw,remount
adb -s emulator-5554 shell mount -o rw,remount /system
adb -s emulator-5554 shell mount -o rw,remount /data
adb -s emulator-5554 shell mount -o rw,remount /data/data
and i got always this error
Usage: mount [-r] [-w] [-o options] [-t type] device directory
could not open /proc/mounts
Click to expand...
Click to collapse
also i try to put it into writable system by cmd
or edit file path and add -writable-system next to it but still fail
i hope some one can help me here