Everytime I try to flash Amons Recovery Image I get to the "push flash_image /system/bin" command line and I get an error message saying the file is read-only. Someone please help, I'm running ROOTED 2.1.
Steve4TIS said:
Everytime I try to flash Amons Recovery Image I get to the "push flash_image /system/bin" command line and I get an error message saying the file is read-only. Someone please help, I'm running ROOTED 2.1.
Click to expand...
Click to collapse
adb shell
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
then try to push
Spencer_Moore said:
adb shell
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
then try to push
Click to expand...
Click to collapse
or adb remount its shorter
T.C.P said:
or adb remount its shorter
Click to expand...
Click to collapse
but my way is more fun!!
Spencer_Moore said:
but my way is more fun!!
Click to expand...
Click to collapse
true but my way is for the lazy people out their that dont want to type all that in
T.C.P said:
true but my way is for the lazy people out their that dont want to type all that in
Click to expand...
Click to collapse
or flash threw fastboot! less prone to the problems that way has.
Could you post steps to do this with fastboot?
Tried and still get "read only file system" message. Using a PC if it makes a difference. Any more help would be great
Steve4TIS said:
Tried and still get "read only file system" message. Using a PC if it makes a difference. Any more help would be great
Click to expand...
Click to collapse
try this:
open up cmd
type in
cd\
cd androidsdk\tools
adb remount
and u should be good bro
Related
I am running custom rom Rooted 2.1 v0.3.
Ever since flashing to the custom rom, when i try to push a file, such as:
adb push bootanimation.zip /system/media
I get the error:
Failed to copy.... Read-only file system.
I didn't have this error before flashing to the rom. Does this have something to do with superuser whitelist?
I have tired:
mount -oremount,rw /dev/block/mtdblock3 /system
and it didn't work and I tired:
adb remount
winch returned:
Operation not permitted.
This is ticking me off since I didn't have this problem until flashing the rom.
EDIT: Now if I try:
adb push bootanimation.zip /system/media,
I get:
Permission denied.
This is crazy.
I need help also. Rooting for first time and trying to get recovery.img on and keep getting read only errors. Tried remount to no avail. Help please
su
mount -o rw,remount /Dev/block/mtdblock3 /system
file system is case sensitive!
if anyone know what command to execute an install or push of "any.apk" via Android Terminal Emulator. It would help me greatly.
p.s.
make sure you have developer mode enabled "settings" and accept su permissions. Also have BusyBox
fKngFtd said:
su
mount -o rw,remount /Dev/block/mtdblock3 /system
file system is case sensitive!
if anyone know what command to execute an install or push of "any.apk" via Android Terminal Emulator. It would help me greatly.
p.s.
make sure you have developer mode enabled "settings" and accept su permissions. Also have BusyBox
Click to expand...
Click to collapse
...it's a lowercase d in dev.
mount -o rw,remount /dev/block/mtdblock3 /system
n2imagination said:
I need help also. Rooting for first time and trying to get recovery.img on and keep getting read only errors. Tried remount to no avail. Help please
Click to expand...
Click to collapse
I had the same problem. From what I could tell, I had the wrong ADB driver somehow. So I downloaded the drivers from the HTC website and went to device manager (Win7) and updated the driver software which fixed the problem. But I think i just lucked out when i stumbled onto that, I feel a blind retard with epilepsy trying to draw a circle on an etch-a-sketch when I'm doing things like rooting. But, it couldn't hurt to try it.
fKngFtd said:
su
if anyone know what command to execute an install or push of "any.apk" via Android Terminal Emulator. It would help me greatly.
Click to expand...
Click to collapse
adb install -l whatever.apk (from tools dir in sdk)
`mods said:
I am running custom rom Rooted 2.1 v0.3.
Ever since flashing to the custom rom, when i try to push a file, such as:
adb push bootanimation.zip /system/media
I get the error:
Failed to copy.... Read-only file system.
I didn't have this error before flashing to the rom. Does this have something to do with superuser whitelist?
I have tired:
mount -oremount,rw /dev/block/mtdblock3 /system
and it didn't work and I tired:
adb remount
winch returned:
Operation not permitted.
This is ticking me off since I didn't have this problem until flashing the rom.
EDIT: Now if I try:
adb push bootanimation.zip /system/media,
I get:
Permission denied.
This is crazy.
Click to expand...
Click to collapse
Did you ever get this fixed? I have the same problem!
I have the same problem also. I've been using SDK just fine for over a month or two, and now that I'm on V3, no worky. Somethings obviously going on. But what?!
LexusBrian400 said:
I have the same problem also. I've been using SDK just fine for over a month or two, and now that I'm on V3, no worky. Somethings obviously going on. But what?!
Click to expand...
Click to collapse
I think the proper permissions were not set for this ROM. Hopefully jcase can modify the file and re-upload the ROM =)
at least that's what I've gathered... someone PLEASE correct me if I'm wrong
edit: I looked at the script file and it seems like rw permissions are set properly???
jcase - any insight?
I personally get a bunch of "Out of memory" errors when trying to follow the recovery walk-through.
post baleeted
Hey guys. I've done commands in adb many times. I'm still new to it, but I never remember having this issue.
I've ran CM6 for months, and nightly's as well. I'm running a custom compiled CM6 right now though.
adb remount I get
remount failed, operation not permitted.. and in default.prop ro.secure is set to 1. I changed to 0 but still can't do remount. Any other suggestions?
Thanks!
For a workaround, try remounting through shell - mount -o rw,remount /system, or the full command (mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system).
is that a temporary fix, or for good. or just a work around?
Just a workaround. It's a command in OS itself that does the same job as "adb remount" - which is, remounts.
I just can't think of anything that would cause adb remount to fail, so I have no suggestions for you to try. But in case you want to be able to do something without getting stuck, and wait for the solution without being in a hurry - I've posted the workaround.
I don't have a solution to solve it once and for all, but every time you want to remount, use
PHP:
adb root
before your commands
excellent.
adb root
adbd is being restarted
adb remount succeeded .
Thanks dude! that will work for now til cooker fixes that. lol
Jack_R1 said:
For a workaround, try remounting through shell - mount -o rw,remount /system, or the full command (mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system).
Click to expand...
Click to collapse
Tried this and it appeared to succeed but I didn't get the results I wanted.
After doing this I tried push c:\com.amazon.mp3.apk \system\app\ and it repeated it back to me, but when I look in that directory, it's not there. What am I doing wrong?
Wrong direction of slashes:
push c:\com.amazon.mp3.apk /system/app/
And you shouldn't be doing it from the ADB shell. The remount is done in the shell, the push is done outside of it.
Jack_R1 said:
Wrong direction of slashes:
push c:\com.amazon.mp3.apk /system/app/
Click to expand...
Click to collapse
Ahhhh, I was wondering about that! Thank you!!
And you shouldn't be doing it from the ADB shell. The remount is done in the shell, the push is done outside of it.
Click to expand...
Click to collapse
So once I perform the remount I exit out of the shell?
operation not permitted.
"adb push" gets you "not permitted"?
try "adb root" first, as suggested above.
Jack_R1 said:
"adb push" gets you "not permitted"?
try "adb root" first, as suggested above.
Click to expand...
Click to collapse
adb root gets me something along the lines of "not supported on a stock build."
EDIT
ok...
adb shell
su
mount -o rw,remount /system
then i get this:
Usage: mount [-r] [-w] [-o options] [-t type] device directory
So it appears it's not actually registering the command?
Then I try
push c:\com.amazon.mp3.apk /system/app/
and I get: failed to copy 'c:\com.amazon.mp3.apk' to '/system/app/com.amazon.mp3.apk' : Read-only file system.
You need to use the full command, since you're running sh, not bash.
Look for the full command in my post.
Yes, currently it doesn't do a thing.
Jack_R1 said:
You need to use the full command, since you're running sh, not bash.
Look for the full command in my post.
Yes, currently it doesn't do a thing.
Click to expand...
Click to collapse
So I tried the full command and exited out to "dos" command prompt and tried again. This time I got "failed to copy.... ....permission denied."
Ok, try without exiting. I'm not sure it'll do anything useful, though.
There is some problem with either your ADB setup or the ROM you're using. Or you're just not rooted.
Jack_R1 said:
Ok, try without exiting. I'm not sure it'll do anything useful, though.
There is some problem with either your ADB setup or the ROM you're using. Or you're just not rooted.
Click to expand...
Click to collapse
Found another thread on another board. I just flashed amon ra's recovery and booted up from there, and it appeared to let me copy!
But then it wouldn't let me cd to system/app. It let me cd to system, but not to app. Weird... I booted back up and there's no evidence of the "copied" apk, anywhere.
What...
the...
****.
Thanks to all for your patience with my super-noobish ass, I'm hoping you're not as frustrated with me as I am with this.
When you're in the recovery, your system isn't mounted. You need to mount it first.
Use almost the same command as for remount, but leave out the "remount" option. Just "-o rw".
Your copy went to void.
Jack_R1 said:
When you're in the recovery, your system isn't mounted. You need to mount it first.
Use almost the same command as for remount, but leave out the "remount" option. Just "-o rw".
Your copy went to void.
Click to expand...
Click to collapse
lol, awesome, thanks. I'll fiddle with it some more in the morning.
Why isn't there a link somewhere to a simple instruction manual? It would be so much easier if I could read up on this myself without bugging all of you guys.
Of course there is. My sig has it in bold, and you can find everything there. It's just that people tend to rush asking questions instead of reading
Jack_R1 said:
Of course there is. My sig has it in bold, and you can find everything there. It's just that people tend to rush asking questions instead of reading
Click to expand...
Click to collapse
I've seen a couple of the basic noob guides to adb and I've seen the google definition of adb functions but it doesn't include instructions on how to do the stuff you're walking me through.
Will take a look at those links shortly. Btw, I'm on a MT3G though I don't think that makes a difference at this level.
I had my stuff deleted, however im having to redo it, im following this "http://forum.xda-developers.com/showthread.php?t=581635&page=32" and it worked perfect the first time, now i keep getting an error that says the files are read only. Whats wrong?
Moved to general Are you perm. rooted? How are you deleting them?
nbunn said:
I had my stuff deleted, however im having to redo it, im following this "http://forum.xda-developers.com/showthread.php?t=581635&page=32" and it worked perfect the first time, now i keep getting an error that says the files are read only. Whats wrong?
Click to expand...
Click to collapse
You need to mount /system as rw. In the terminal enter
Code:
mount -o rw,remount -t ext3 /dev/block/mmcblk0p26 /system
Then remove as before.
cloverdale said:
You need to mount /system as rw. In the terminal enter
Code:
mount -o rw,remount -t ext3 /dev/block/mmcblk0p26 /system
Then remove as before.
Click to expand...
Click to collapse
It told me permission denied, and operation not permitted?
nbunn said:
It told me permission denied, and operation not permitted?
Click to expand...
Click to collapse
Did you enter su first?
cloverdale said:
Did you enter su first?
Click to expand...
Click to collapse
yes i did, ill try again
Hope this is the right place to post this.
My Atrix is rooted stock 1.83 .
I'm trying to "adb push" some OGG files to "/system/media/audio/" to add-to and replace some of the existing system sounds, especially that bloody annoying keypress (typewriter) sound, but I'm getting the following error (which makes sense):
Read-only file system
Tried using Root Explorer, same issue...again makes sense since its mounted as Read only on boot.
I tried booting into recovery mode, but I can't access the phone via ADB at all, even with USB Debug enabled. I also tried "adb remount" command, no luck either. I get an error "operation not permitted".
So, does anyone know the correct sequence of commands I need in ADB to remount the Atrix /system folder as RW??
What I have been doing is using adb push to the /sdcard then using adb shell then su then
mount -t rfs -o remount,rw /dev/stl5 /system
Then cp /sdcard/whatever /system/media
Sent from my MB860 using XDA App
EDIT: im at my computer now so I can write this easier to understand, lol
Lets say the file you want to change is called whatever.ogg
Code:
adb push whatever.ogg /sdcard/whatever.ogg
adb shell
su
mount -t rfs -o remount,rw /dev/stl5 /system
cp /sdcard/whatever.ogg /system/media/audio/notifications
when you access root explorer, does it let you know that it has been granted supervisor privilages? Does it give you the option to change from read to write? what did you use to root? I had to run the original Aroot three times before if finally gave me root.
You're the best, worked perfectly Can't believe that hideous typewriter sound is gone, it only took me 1.5 years as an Android user to finaly say enough is enough. Whomever thought it was a good idea to mimic the sound of an 1800's typewriter on a 21st century device needs to be fired.
Thanks again.
aver2one said:
What I have been doing is using adb push to the /sdcard then using adb shell then su then
mount -t rfs -o remount,rw /dev/stl5 /system
Then cp /sdcard/whatever /system/media
Sent from my MB860 using XDA App
EDIT: im at my computer now so I can write this easier to understand, lol
Lets say the file you want to change is called whatever.ogg
Code:
adb push whatever.ogg /sdcard/whatever.ogg
adb shell
su
mount -t rfs -o remount,rw /dev/stl5 /system
cp /sdcard/whatever.ogg /system/media/audio/notifications
Click to expand...
Click to collapse
i need help
im using a clone samsung galaxy tab2.tried to change the system font with root browser and it bricked.the phone dont have cwm so i didnt back up my rom.any command in adb that can be used to change the font folder
Obiechina said:
im using a clone samsung galaxy tab2.tried to change the system font with root browser and it bricked.the phone dont have cwm so i didnt back up my rom.any command in adb that can be used to change the font folder
Click to expand...
Click to collapse
Well congrats! that was the dumbest thing ever. NEVER attempt something like that unless you have CWM or equivalent installed, have a backup, and know what you are doing.
Have you tried to read your device's xda forum?
Please Help
Hahaha, can you help me?
i want to change my /system/framework folder by using the POWER and UP volume keys
i had a backup of my system/framework in my SD..
What should i do?
First of I had no idea where to post this as it's not "device specific"
I'd been undertaking framewokr-res changes fine up until yesterday when I started to recieve an Invalid Argument error in ADB shell.
The command that I am using with ADB is;
su
stop
cp /sdcard/framework-res.apk /system/framework/framework-res.apk
chmod644 /system/framework/framework-res.apk
sync
start
Click to expand...
Click to collapse
But after "cp /sdcard/framework-res.apk /system/framework/framework-res.apk" I'm now recieving, "cannot remove /system/framework/framework-res.apk Invalid Argument"
Where's that come from, I've never had it before, any ideas please?
I'm no noob btw, I've searched google and the forums here to no avail.
Regards.
SWFlyerUK said:
First of I had no idea where to post this as it's not "device specific"
I'd been undertaking framewokr-res changes fine up until yesterday when I started to recieve an Invalid Argument error in ADB shell.
The command that I am using with ADB is;
But after "cp /sdcard/framework-res.apk /system/framework/framework-res.apk" I'm now recieving, "cannot remove /system/framework/framework-res.apk Invalid Argument"
Where's that come from, I've never had it before, any ideas please?
I'm no noob btw, I've searched google and the forums here to no avail.
Regards.
Click to expand...
Click to collapse
My first guess is that the system partition is mounted read-only, but that seems like an odd message.
Is this on a different device than you normally use, or one that has worked before in the past?
Yep just that device, just tried on my Nexus S and it's still working on, but not on my Archos 70. Is there anyway I can mount as r/w with ADB to ensure its read and write?
Thanks for the response, appreciated.
SWFlyerUK said:
Yep just that device, just tried on my Nexus S and it's still working on, but not on my Archos 70. Is there anyway I can mount as r/w with ADB to ensure its read and write?
Thanks for the response, appreciated.
Click to expand...
Click to collapse
I don't know anything about the device, but if it is rooted, busybox mount has a remount option:
Code:
busybox mount -o remount,rw /system
Sorry where do I enter that, just the CMD in the Android SDK? I've not used Busy Box commands before.
on the command line just like your other commands above.
I'm doing something wrong as this is what I'm getting;
No, as part of the commands you are running on the device via adb shell:
Code:
su
stop
[COLOR="Red"]busybox mount -o remount,rw /system[/COLOR]
cp /sdcard/framework-res.apk /system/framework/framework-res.apk
chmod644 /system/framework/framework-res.apk
sync
start
Yet another error;
mount: can't find /system in /proc/mounts
May aswell give up at this rate
Apparently that device uses some other mounting format that standard android.
Ok cheers, champ, I'm sure I'll find a solution, like I said, it worked before, but after a full reformat last night thats no the error that I'm getting.