[Q] how do i put files in a read only directory on a rooted evo - EVO 4G Q&A, Help & Troubleshooting

how would one add an mp3 file to the read only directory
( system/media/audio/alarms )
the stock ones really don't wake me up
from what i do know the directory is a read only directory and really would like to
put this alarm.mp3 in the that read only folder...
appreciate your help and thanks in advance...

I highly suggest you buy the app "root explorer"

would astro do the same thing?...
Sent from my PC36100 using XDA App

are you fully rooted? if not, i know the answer.

I think I am...how would one confirm?... appreciate your help
Sent from my PC36100 using XDA App

if you have the android sdk set up use "adb remount". It should say something like partition remounted successfully. If you see that then all of your read only directories will be reset to read/write. Afterwards just reboot your phone and it will set everything back to normal.

thank you.....i tried that command and received this error:
remount failed: Operation not permitted
does this mean that I'm not fully rooted? what next?
appreciate your help xHausx ...

1candydick said:
thank you.....i tried that command and received this error:
remount failed: Operation not permitted
does this mean that I'm not fully rooted? what next?
appreciate your help xHausx ...
Click to expand...
Click to collapse
could be, do you have the superuser app in your app drawer? a few more things you can try is typing:
adb shell {enter}
mount system {enter}
at this point you will see either a $ or # sign, the # sign means you have root. If you see the $ type:
su {enter}
if that doesn't change it to a # then try typing
sh0 {enter}
su {enter}
if that still doesn't work then you need to use an exploit to get root. However, if it does work and you see # then type:
mount -t yaffs2 -o remount,rw /dev/block/mtdblock4 /system {enter}

You can put these on your SD card too, you just have to put it in /media/audio/alarms (you can also use "notifications" or "ringtones" instead for those).

mv and chmod should work

Related

Uninstalling WaveSecure from Modaco ROM

I just installed the Modaco ROM on my Desire (It is awesome BTW) but i don't like the WaveSecure program and i can't seem to be able to find it in /system/app to remove it!
Is there a way to delete this program off the phone!?
I would like to learn how to do this also
Don't think you can unless you use the online kitchen (I don't like it so removed it from mine)
I believe:
adb remount
adb shell rm /system/app/com.wsandroid.apk
Click to expand...
Click to collapse
Doesn't seem to work mate.
Code:
C:\DevTools\android-sdk-windows\tools>adb remount
remount succeeded
C:\DevTools\android-sdk-windows\tools>adb shell
# rm /system/app/com.wsandroid.apk
rm /system/app/com.wsandroid.apk
rm: can't remove '/system/app/com.wsandroid.apk': Directory not empty
#
plasmafire said:
Doesn't seem to work mate.
Code:
C:\DevTools\android-sdk-windows\tools>adb remount
remount succeeded
C:\DevTools\android-sdk-windows\tools>adb shell
# rm /system/app/com.wsandroid.apk
rm /system/app/com.wsandroid.apk
rm: can't remove '/system/app/com.wsandroid.apk': Directory not empty
#
Click to expand...
Click to collapse
Running as admin?
Same here. Running as admin - nevertheless "Directory not empty"
Edit: solved. Run SUBFS on phone and mounted /system RW. After that tried again in cmd - voila!
Insomnious said:
Same here. Running as admin - nevertheless "Directory not empty"
Edit: solved. Run SUBFS on phone and mounted /system RW. After that tried again in cmd - voila!
Click to expand...
Click to collapse
+1
For noobs like me: It's actually SUFBS, not SUBFS. Google for the apk, install the app, in the menu there's an option "mount /system RW". Activate and then run the adb commands above in a cmd window on your PC. Et voila!
(Just realised this is a Desire thread, this worked for me on my Nexus too)

Need Help with ADB

i'm new to adb. i finally got it working. the correct string is added to Path, it's in my root directory C:\. i'm able to list my device, list directories, and even push/pull (did test to sdcard). i cannot, however, mount the /system directory to r/w.
this is what's happening
C:\android\android-sdk_r06-windows\android-sdk-windows\tools> adb remount
remount failed: Invalid argument
i'm in recovery trying to do this. anyone know what's going on or can maybe lend some help? thank you
mrvirginia said:
i'm new to adb. i finally got it working. the correct string is added to Path, it's in my root directory C:\. i'm able to list my device, list directories, and even push/pull (did test to sdcard). i cannot, however, mount the /system directory to r/w.
this is what's happening
C:\android\android-sdk_r06-windows\android-sdk-windows\tools> adb remount
remount failed: Invalid argument
i'm in recovery trying to do this. anyone know what's going on or can maybe lend some help? thank you
Click to expand...
Click to collapse
if you do not have a rooted, NAND unlocked, phone, you will not be able to mount /system
timothydonohue said:
if you do not have a rooted, NAND unlocked, phone, you will not be able to mount /system
Click to expand...
Click to collapse
it is rooted and NAND unlocked lol
i was actually able to push but not where i wanted.
i did
adb push com.htc.resources.apk /system/framework
but that's not where it needs to go
so i then did
adb push com.htc.resources.apk /system/framework/
and it says /system/framework is a directory, which i know lol that's where i need the file to go.
oh yeah, and i got it mounted as r/w. so now i'm just having trouble getting the file where it needs to be with the whole "is a directory" error instead of it actually pushing the file. still unable to pull a file from that location, though.
try writing the filename. it 'should' append it automatically, but if not then try
adb push com.htc.resources.apk /system/framework/com.htc.resources.apk
timothydonohue said:
try writing the filename. it 'should' append it automatically, but if not then try
adb push com.htc.resources.apk /system/framework/com.htc.resources.apk
Click to expand...
Click to collapse
this will prob work but...
now i'm getting "error: more than one device and emulator"
edit: i'm going to reboot and start all over. not sure how to kill it off since this is a little new to me ha
timothydonohue said:
try writing the filename. it 'should' append it automatically, but if not then try
adb push com.htc.resources.apk /system/framework/com.htc.resources.apk
Click to expand...
Click to collapse
this was a successful push, but the file is still not updating so i'm lost now
also, trying to pull this file back out is not working using
C:\android\android-sdk_r06-windows\android-sdk-windows\tools>adb pull /system/fr
amework/com.htc.resources.apk com.htc.resources.apk
remote object '/system/framework/com.htc.resources.apk' does not exist
edit: this is what i'm looking at
C:\android\android-sdk_r06-windows\android-sdk-windows\tools>adb shell mount -o
rw, remount /dev/block/mtdblock3 /system
adb server is out of date. killing...
* daemon started successfully *
BusyBox v1.15.3 (2010-02-06 17:13:19 CET) multi-call binary
Usage: mount [flags] DEVICE NODE [-o OPT,OPT]
Mount a filesystem. Filesystem autodetection requires /proc be mounted.
Options:
-a Mount all filesystems in fstab
-r Read-only mount
-w Read-write mount (default)
-t FSTYPE Filesystem type
-O OPT Mount only filesystems with option OPT (-a only)
-o OPT:
loop Ignored (loop devices are autodetected)
[a]sync Writes are [a]synchronous
[no]atime Disable/enable updates to inode access times
[no]diratime Disable/enable atime updates to directories
[no]relatime Disable/enable atime updates relative to modification ti
me
[no]dev (Dis)allow use of special device files
[no]exec (Dis)allow use of executable files
[no]suid (Dis)allow set-user-id-root programs
[r]shared Convert [recursively] to a shared subtree
[r]slave Convert [recursively] to a slave subtree
[r]private Convert [recursively] to a private subtree
[un]bindable Make mount point [un]able to be bind mounted
bind Bind a directory to an additional location
move Relocate an existing mount point
remount Remount a mounted filesystem, changing its flags
ro/rw Read-only/read-write mount
There are EVEN MORE flags that are specific to each filesystem
You'll have to see the written documentation for those filesystems
C:\android\android-sdk_r06-windows\android-sdk-windows\tools>adb pull /system/fr
amework/com.htc.resources.apk com.htc.resources.apk
remote object '/system/framework/com.htc.resources.apk' does not exist
/system is under mtdblock4 on our device.
if you need to mount /system as read/writeable from adb, you should just be able to use
adb remount
if you are doing it in shell, use mount -o remount,rw -t yaffs2 /dev/block/mtdblock4 /system
timothydonohue said:
/system is under mtdblock4 on our device.
if you need to mount /system as read/writeable from adb, you should just be able to use
adb remount
if you are doing it in shell, use mount -o remount,rw -t yaffs2 /dev/block/mtdblock4 /system
Click to expand...
Click to collapse
yeah adb remount won't work for me either.
C:\android\android-sdk_r06-windows\android-sdk-windows\tools>adb remount
adb server is out of date. killing...
* daemon started successfully *
remount failed: Invalid argument
i'm going to try mtdblock4
also, if you are having issues with the adb daemon, use
adb kill-server
adb start-server
that'll reboot the adb daemon
timothydonohue said:
also, if you are having issues with the adb daemon, use
adb kill-server
adb start-server
that'll reboot the adb daemon
Click to expand...
Click to collapse
thanks. yeah i started just killing it in task manager
after using "mount -o remount,rw -t yaffs2 /dev/block/mtdblock4 /system" and trying to pull, i'm still getting /system/framework/com.htc.resources.apk does not exist
yeah, not sure what to tell you then. i can't piddle around in my own, because i'm on cm6, and won't have that.
are you sure it exists?
adb shell
# cd /system/framework
# ls
that will tell you what's in there. if you can't see it, it's not there.
from a brand new shell, (or bounce back up to the root directory)
try
find -name "*resources*.*"
that should tell you every file that contains 'resources' as a part of the file name, and where it is located.
timothydonohue said:
yeah, not sure what to tell you then. i can't piddle around in my own, because i'm on cm6, and won't have that.
are you sure it exists?
adb shell
# cd /system/framework
# ls
that will tell you what's in there. if you can't see it, it's not there.
from a brand new shell, (or bounce back up to the root directory)
try
find -name "*resources*.*"
that should tell you every file that contains 'resources' as a part of the file name, and where it is located.
Click to expand...
Click to collapse
it exists. i navigated to it using root explorer. but according to this, it doesn't exist
C:\android\android-sdk_r06-windows\android-sdk-windows\tools>adb shell
adb server is out of date. killing...
* daemon started successfully *
/ # cd /system/framework
cd /system/framework
/sbin/sh: cd: can't cd to /system/framework
/ #
you can't navigate to the folder if /system isn't mounted. if you just restarted the adb server, then it won't be mounted.
timothydonohue said:
you can't navigate to the folder if /system isn't mounted. if you just restarted the adb server, then it won't be mounted.
Click to expand...
Click to collapse
that was prob the case, can't remember if i re-mounted or not when i was doing that. regardless, i was positively mounted when trying to push/pull and it wasn't working so i guess i'll just have to wait for someone to put it in a flashable zip.
i hate adb
thanks for your help dude

[Q] Rooting G2 - Failed to copy : Read-only file system

Hey,
I'm following the tutorial over at G2 Hacks:
g2hacks.co m/g2-hacks/how-to-root-g2-phone
(omit the space between 'co' and 'm/')
I came across a problem at the beginning of the cmd portion.
This is what I type and the error I get.
Code:
C:\AndroidSDK\tools>adb push su \sdcard\su
failed to copy 'su' to '\sdcard\su': Read-only file system
How do you solve this problem?
EDIT: Go to 3rd post.
kpaekn said:
Hey,
I'm following the tutorial over at G2 Hacks:
g2hacks.co m/g2-hacks/how-to-root-g2-phone
(omit the space between 'co' and 'm/')
I came across a problem at the beginning of the cmd portion.
This is what I type and the error I get.
Code:
C:\AndroidSDK\tools>adb push su \sdcard\su
failed to copy 'su' to '\sdcard\su': Read-only file system
How do you solve this problem?
Click to expand...
Click to collapse
If you're wanting to root, go straight to the source; the guide in the Wiki here is based on the work the devs who actually found the means to root the device.
http://forum.xda-developers.com/wik...sion#Rooting_the_Vision_.28G2.2FDZ.29_and_DHD
Sent from my T-Mobile G2 using XDA App
I was following the tutorial from the Wiki Guide:
ht tp://forum.xda-developers.co m/wiki/index.php?title=HTC_Vision#Rooting_the_Vision_.28G2.2FDZ.29_and_DHD
(omit the space between 'ht' and 'tp' , 'co' and 'm/')
I came across a problem under the TEMP ROOT section.
This is what I type and the error I get.
Code:
C:\AndroidSDK\tools>adb push su \sdcard\su
failed to copy 'su' to '\sdcard\su': Read-only file system
How do you solve this problem?
kpaekn said:
I was following the tutorial from the Wiki Guide:
ht tp://forum.xda-developers.co m/wiki/index.php?title=HTC_Vision#Rooting_the_Vision_.28G2.2FDZ.29_and_DHD
(omit the space between 'ht' and 'tp' , 'co' and 'm/')
I came across a problem under the TEMP ROOT section.
This is what I type and the error I get.
Code:
C:\AndroidSDK\tools>adb push su \sdcard\su
failed to copy 'su' to '\sdcard\su': Read-only file system
How do you solve this problem?
Click to expand...
Click to collapse
Is USB debugging turned on and is the SDcard not mounted?
Sent from my T-Mobile G2 using XDA App
Sounds like the SD card is mounted on your PC and not the phone ? It needs to be mounted on the phone or this won't work.
Sent from my HTC Desire Z
All that command does is copy that file from your computer to the sdcard. You could accomplish the same thing by dragging and dropping that file to the sdcard.
The 'push' command just means "copy from location A to location B"
Sent from my HTC Vision using XDA App
You could always just mount the SDcard... but anyway, to solve this type in "adb remount" and enter the command before pushing the file
Sent from my HTC Vision using XDA App
USB debugging is on and SD is not mounted to my computer.
I tried directly copying the files onto the sdcard, but when I need to push rage, busybox, etc. I cannot access the data folder graphically from the computer.
So I'll still need to use cmd.
I tried the remount, but this is what I get:
Code:
C:\AndroidSDK\tools>adb remount
remount failed: Operation not permitted
kpaekn said:
USB debugging is on and SD is not mounted to my computer.
I tried directly copying the files onto the sdcard, but when I need to push rage, busybox, etc. I cannot access the data folder graphically from the computer.
So I'll still need to use cmd.
I tried the remount, but this is what I get:
Code:
C:\AndroidSDK\tools>adb remount
remount failed: Operation not permitted
Click to expand...
Click to collapse
The adb remount error is expected (the command requires your ro.secure prop to be set to 0, which you can't do until you have rooted).
So you were able to copy files to the SD card? Just to verify again, you should try mounting the SD card to you computer (so it shows up as a device on your computer's file explorer), copy over a file, unmount the card from your computer (and remember to also hit the button on phone to do so), and then try the ADB push commands again.
Ok, with the phone on plug it into your computer and mount USB storage. Drag and drop 'su' and superuser.apk into the sdcard then unmount USB storage. Make sure USB debugging is on at this point (you'll see it in the notification task bar). Do these commands:
Code:
adb push rage /data/local/tmp/rage
adb push busybox /data/local/tmp/busybox
adb push root /data/local/tmp/root
adb shell chmod 0755 /data/local/tmp/*
Then in the terminal app type:
Code:
/data/local/tmp/rage
You'll see some message pop up saying something about 'forked #### childs' and that's temp root. Then follow the instructions on running gfree to gain full root. Btw, you can just copy and paste all those commands if you think you'll make a mistake.
You may also be able to run the '/data/local/tmp/rage' command with the 'adb shell' command, never tried it myself though.
kpaekn said:
I was following the tutorial from the Wiki Guide:
ht tp://forum.xda-developers.co m/wiki/index.php?title=HTC_Vision#Rooting_the_Vision_.28G2.2FDZ.29_and_DHD
(omit the space between 'ht' and 'tp' , 'co' and 'm/')
I came across a problem under the TEMP ROOT section.
This is what I type and the error I get.
Code:
C:\AndroidSDK\tools>adb push su \sdcard\su
failed to copy 'su' to '\sdcard\su': Read-only file system
How do you solve this problem?
Click to expand...
Click to collapse
Oh come on !!!
the path separator in linux (and the phone is a linux computer) is / and not \ !!!
So the command is:
Code:
C:\AndroidSDK\tools>adb push su /sdcard/su
Just to tell you something about the unix shell:
The \ char is a so called escape character that you use to tell the shell that it should not ignore the next character even if it is a white space (i.e. space)
You would use it if you have to specify a path that contains spaces:
i.e.:
Code:
mkdir dir\ with\ 3\ spaces
will create a directory with the name "dir with 3 spaces". This would not work without the \ characters.
have fun - Guhl
Haha... it's funny how simple the answer was.
Thanks for your guys' help.

[Q] How to change build.prop using adb?

Hello folks,
I have a Wildfire, running CM7 #36, Jacob's 4.1 Kernel flashed.
Now I wanted to edit the /system/build.prop to get access to further apps (rom manager pro, e.g.).
After remounting system via
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
I wanted to copy/remove or whatever the /system/build.prop, but I only get
# rm /system/build.prop
rm: can't remove '/system/build.prop': Directory not empty
What does this mean? /system/build.prop is surely not a directory (ls -al).
Any help would be appreciated - can't post in the development-forums because of unsufficient number of posts - thanks,
Guntram
Don't remove it...
Pull build.prop using adb, edit and push it back to /system
Sent from my HTC Wildfire using XDA App
Hello Kevin1625,
unfortunately, this gives the same message (which I don't understand anyways?):
Code:
$ adb push build.prop /system
failed to copy 'build.prop' to '/system/build.prop': Directory not empty
Any ideas?
Are you doing this via terminal??
Adb is used on your computer.
Sent from my HTC Wildfire using XDA App
Mount system via recovery.
Open a cmd
cd into your tools folder
adb pull /system/build.prop
Edit it.
adb push build.prop /system/build.prop
adb reboot
I think youre trying to adb shell, there is no need.
Sent from my HTC Wildfire using XDA App
Thanks kevin2516 (what are these numbers for?)!
Seems, that build.prop is somehow blocked, when trying to access it on the running phone.
When I adb push on the mounted /system in recovery, everything seems to work fine.
Except, that I don't get the wanted result (Rom Manager Premium in the market) :-(.
Did you got it running, using SympMarket (which only once gave me >4000 video results - but I'm not able to reproduce ;( )?
If so, do you remember how?
Thanks a lot,
Guntram
thank you so much man! saved my phone after i accidently set PPI to 280 :L
and you should also adb shell chmod 644 /system/build.prop
Device says that system directory can not be accessed when pushing the file

ADB Push Fails - Read Only File System; Unable to remount. Bad root?

Hey all,
I was trying to push nano to my phone and I get this:
C:\>adb push nano /system/bin
failed to copy 'nano' to '/system/bin/nano': Read-only file system
Trying remount:
C:\>adb remount
remount failed: Operation not permitted
Then from ADB shell, I try:
c:\>adb shell
[email protected]:/ $ su
su
[email protected]:/ # mount -o rw,remount /system
mount -o rw,remount /system
[email protected]:/ #
[email protected]:/ # exit
exit
[email protected]:/ $ exit
exit
c:\>adb push nano /system/bin
failed to copy 'nano' to '/system/bin/nano': Permission denied
Any ideas? I'm rooted the superuser and busybox installed.
I rooted using this method:
http://forum.xda-developers.com/showthread.php?t=1956432
Apps get elevated privileges without error. Terminal emulator allows me to view system files. Unfortunately I need to edit some program files in /data/data and there doesn't seem to be any editor available (vi is acting very glitchy). I discovered this problem when I tried to push nano to my phone.
I also tried to access /data using gEditor and it says:
file list
/data
cannot change the directory.
Something is very wrong here. Do I need to re-root using a different method? Please advise. Thanks!
Update: I was able to get adb to work. It turns out I never flashed an unsecured boot image.
However, my nano installation doesn't work and gEditor crashes when I try to access the data folder. That will be for another thread.
For remount and push/pull commands to work, download adbd insecure from playstore . That's the only way you will be able to do the aforementioned commands.
Thanks for the tip. After rerooting the phone with an unsecured image I was able to use adb. I am able to use adb right now without adbd installed however.
Sent from my SGH-T889 using xda app-developers app
I was going crazy allover looking for an answer, and found it here...
Thanks.
Not compatible
teshxx said:
For remount and push/pull commands to work, download adbd insecure from playstore . That's the only way you will be able to do the aforementioned commands.
Click to expand...
Click to collapse
Is there any other option?? That software is not compatible with my android!!
You will have to flash a kernel which has adb secure set to 0.
Sent from my SGH-T889 using xda app-developers app

Categories

Resources