I want to copy into the MoDaCo's ROM 2.8 the original files from system/media/bootscreen so I can have the original with sound
The only problem is that I tried to mount the /system folder and it says "mount: cannot read /etc/fstab : No such file or directory".
The progress flashing my phone went just fine but this command does not work.
Is there a way to FIX and make the /system/media/bootscreen folder to have read/write permitions ?
EDIT : Figured it out
I opened cmd and went to C:\SDK\tools
Then in cmd i wrote:
"adb shell"
"mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system"
"adb push boot.gif /system/media/bootscreen"
"adb push boot2.gif /system/media/bootscreen"
"adb push boot_bg.gif /system/media/bootscreen"
"adb push boot.mp3 /system/media/bootscreen"
"adb push boot_animation.xml /system/media/bootscreen"
Of course if you want to do the same just remove the " " from the commands
Download the original bootscreen files from here and put them into the SDK/tools folder.
adb shell mount -o remount,rw /system
does the trick, no need to specify filesystem or device, as it is already mounted. when you are done you should do a
adb shell mount -o remount,ro /system
to have it mounted ro again. btw, you only need to exchange boot_animation.xml, the sound is still there, it is just deactivated. and you could have used the update.zip that paul made for this purpose, it is in the first post of his thread... but this way you learned something, so even better
Now gonna try to make a windows vista boot sound and post the result
Has somebody made it already ?
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
Trying to install Clockwork recovery mod on my LG Optimus V and I am running into a few problems. The version of ROM Manager that I got from the market does not list my phone as a model to choose from when the Confirm your phone window appears. So, to get around this, I decided to try and install another recovery (such as Amon's) using an adb shell. Anytime I try to type a command while in the adb shell it returns the command and says "permission denied" next to it. The $ is there, my phone is rooted, the SD card is unmounted and USB Debugging ot turned on.
I can view my phone from adb devices and even look at the log of its activity with adb logcat.
The first command I type in is "adb shell mount -o rw,remount /dev/block/mtdblock3 /system". After I hit enter, it says mountperation not permitted.
I also can't boot into recovery mode at the moment because I had to choose a phone that is different from mine when I tried to flash Clockwork Recovery mod.
I'd greatly appreciate any help, I'll get some sleep and check back in a few hours.
ironpirat3 said:
The $ is there, my phone is rooted
Click to expand...
Click to collapse
The $ is normal user and not root (#).
Code:
> adb shell
$ su
# mount -o rw,remount /dev/block/mtdblock3 /system
Turns out I wasn't looking at my phone and allowing the su command through Superuser (feel really dumb now). Still, whenever I try to run a command starting with adb shell from the command prompt it says Operation not permitted.
Code:
>adb shell mount -o rw,remount /dev/block/mtdblock3 /system
mount: Operation not permitted
On a side note, how do I get out of my phone and back into command prompt after using the adb shell command?
ironpirat3 said:
Turns out I wasn't looking at my phone and allowing the su command through Superuser (feel really dumb now). Still, whenever I try to run a command starting with adb shell from the command prompt it says Operation not permitted.
Click to expand...
Click to collapse
Code:
>adb shell mount -o rw,remount /dev/block/mtdblock3 /system
mount: Operation not permitted
No. You run adb shell only, and then su, and then remount from the phone shell, NOT via adb. Clearly written in the example above.
To exit a shell, type exit.
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.
Hi guys,
So I'm in a spot of bother with my Android Tablet (Sony Tablet S) - I deleted the default launcher from the /system/app folder and when I power my device on I get a constant stream of force closes. It can't be used, all I can access is the settings menu.
I'm trying to push a launcher across into the system/app folder - it's rooted, and ADB is working.
Now here's the trouble.
I start CMD from platform-tools folder > adb devices > my device is listed.
adb shell > adb devices > no longer listed.
Any commands I enter in the shell, I "su" and its granted permissions, then adb push 1.apk /system/app > error: device not found. If I try the same without adb shell, then it's permission denied.
I'm pretty desperate to get this working, but any ideas please? I've contacted Sony, I hope that they will repair this, at a cost or not.
Thanks.
When you are in the shell, you don't need to type "adb" anymore, maybe that's it. "push" must be used with adb though, but not in adb shell.
For the permission problem, is /system/ mounted writeable? You could try running this line (not in shell):
Code:
adb shell mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
This should mount /system/ writeable. Then, try again with adb push. This might differ from device to device though, I don't know if it will work for you.
Other than that, I recommend you pose your question again in the subforum specific to your Android device: http://forum.xda-developers.com/forumdisplay.php?f=1294
Thanks for the response.
I've just run that, and got mount: operation not permitted.
Ok, try it again as follows:
Code:
adb shell
su
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
Ok, when I run that it works, but as soon as I push, I get device not found?
Anymore suggestions please?
what exactly do you type in when you push? Do you push after entering "adb shell"?
I've made some progress!
I've mounted the /data partition with busybox and now have GoLauncherX.apk in there. But I'm still getting all of the force closes and I pressing the home button, I can't get to the home, it's almost likes it's not installed....
I'll keep trying but it could be something else at fault.
You might need to reflash the ROM. To find out how that is done, check the subforum appropriate to your device.
If you deleted the stock launcher from the system partition, I would suggest you try to get it back there first.