When i try to push or pull anything it says, e/ddms the file cannot be pushed because its a read-only file system. Any help?
Mdawg112 said:
When i try to push or pull anything it says, e/ddms the file cannot be pushed because its a read-only file system. Any help?
Click to expand...
Click to collapse
You have to remount the FS in read/write mode.
With adb it's 'adb remount'.
smw6180 said:
You have to remount the FS in read/write mode.
With adb it's 'adb remount'.
Click to expand...
Click to collapse
Ha, I feel stupid now.
Mdawg112 said:
Ha, I feel stupid now.
Click to expand...
Click to collapse
Happens to everyone at times. Don't sweat it
So what do you do, if you run adb remount
and it still say's read-only system when trying to push?
been dealing with it for a few days, looked all around the forums and didn't find anything that helped :-/
jubi23 said:
So what do you do, if you run adb remount
and it still say's read-only system when trying to push?
been dealing with it for a few days, looked all around the forums and didn't find anything that helped :-/
Click to expand...
Click to collapse
Good question. Unfortunately I have no idea. Never seen it fail. theoretically there's a command line you can run in adb shell to mount the FS read/write, but I can't remember it off the top of my head.
Something like mount -o rw /dev/m3blk (as I said I can't remember the exact filesystem name). I'd do a search for 'mount -o' on the forums. It's been posted more than once and I'm too lazy to find it for you
I believe you're refering to
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
if so, tried that too :-/ still nothing
i read someone had reformatted their card on xp vs 7, so tried that to and still nothing haha
i give up
thanks btw
Yeah, I'm having the same problem as you sometimes. Other times it works. It's very strange! It annoys me. Anyone have any idea on a fix?
jubi23 said:
I believe you're refering to
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
if so, tried that too :-/ still nothing
i read someone had reformatted their card on xp vs 7, so tried that to and still nothing haha
i give up
thanks btw
Click to expand...
Click to collapse
Yeah that's the one, thanks.
Have you tried that from recovery? Are you using a2sd and if so, what ext?
Are you able to mount the card as a disk drive? Are you sure the SD card isn't going bad on you?
Sounds like you've checked anything else I would have thought of...wish I could help.
Have you tried that from recovery? Are you using a2sd and if so, what ext?
Are you able to mount the card as a disk drive? Are you sure the SD card isn't going bad on you?
Click to expand...
Click to collapse
Well i'm actually trying to flash a new recovery (all in the pursuit of installing flipz new fresh rom with ext4 haha), so was doing it from the computer
I tried using a2sd but i'm pretty sure it didn't work, because i went to ext4 and to my knowledge fresh 2.0d can't use ext4, so yea, i fail
i am able to mount the card as a disk drive and can move things back and fourth via explorer, play music, everything except this seems to be fine, it's only a few weeks old, so i really hope it's not dying
jubi23 said:
Well i'm actually trying to flash a new recovery (all in the pursuit of installing flipz new fresh rom with ext4 haha), so was doing it from the computer
I tried using a2sd but i'm pretty sure it didn't work, because i went to ext4 and to my knowledge fresh 2.0d can't use ext4, so yea, i fail
i am able to mount the card as a disk drive and can move things back and fourth via explorer, play music, everything except this seems to be fine, it's only a few weeks old, so i really hope it's not dying
Click to expand...
Click to collapse
That could be it. ext4 doesn't play nicely with ext3 based stuff. It's 'semi' backward compatible (meaning you can mount ext4 as ext3) but it seems to have some serious inconsistencies that way. I'd recommend a re-partition and then upgrade ext3->ext4 AFTER you install the new ROM.
Heh. I had all KINDS of problems restoring an ext3 based nandroid after upgrading to ext4. Had to repartition and then restore the nandroid to get it to work.
well, loaded recovery, re-partitioned my sdcard, upgraded to ext3 and left it there, still nothing
the sd card wouldnt have any bearing on the ability to adb remount.
the /system partition is stored on the phone itself, so the mount -o ..yadda yadda
remounts the /system partition in this case /dev/block/mtdblock3.
the only reason a sd card would come to play is if youre runnign a2sd, in which case it makes symlinks (shortcuts) to the sdcard, if the sdcard is formatted improperly then a2sd will either cause a bootloop, or crash and then youre phone should boot normally but you wont have access to your ext4 partition (the partition with your apps).
im not sure how to fix a problem with adb remount, perhaps try a new version of the SDK or just a clean one.
good luck
I'm wondering if there is something wrong with my mounting
When i'm in the shell
if i cd /sdcard
then do a ls
nothing is returned
I've also directly copied the recovery image from my computer to the sdcard, and attempted to run the flash_image command and it says no such file or directory
I do have usb debugging enabled and am selected to mount the sdcard, is there some other step or something i'm missing?
nenn, i had actually just a little bit ago downloaded the latest sdk on a completely different machine and still same results
Alrite, so I was able to copy the image recovery from
explorer and flash from.terminal on my phone
Although I'd prefer to work from the pc, anyone have any other possible ideas?! I'm at a loss
-------------------------------------
Sent from my HERO200
I was wondering if there is an app that allows you to put an update (nighty) on an sd card without having to remove the card and attaching it to your computer.
I have wifi pro and that doesn't look like it allows me to do that and just hooking the nook to my pc doesn't look like it gives me the option either. Am I missing something?
I've haven't done myself yet but heard people mentioned about the app called "Root Explorer"??? or "Root Folder" or something with "root".
Download nightly build directly on the NC then use the app to drag the zip file over the "boot" partition.
I think it should be able to do, not done that myself.
The best I can offer is, if you eject the card long enough to start booting to stock, then re-insert it before stock fully loads (on one of the splash screens), the boot partition will be mounted as storage and you can connect to your PC by USB to drop an update file in there.
It might help you out if the issue is not having access to a card reader, but you still have to pop the card out and back in.
ETA: I never had any luck getting an update on the root of any SD, even one formatted for storage, using a file manager.
NookColorUMS allows you to mount any partition. Turn off compatibility mode in spare parts and then reboot to see app in full screen.
http://forum.xda-developers.com/showthread.php?t=952456
If you're running off of SD and adb is working then:
adb shell busybox mkdir /sdcard/boot
adb shell busybox mount /dev/block/mmcblk1p1 /sdcard/boot
adb push ***UPDATEFILE*** /sdcard/boot
adb reboot recovery
If running from EMMC then:
adb shell busybox mkdir /sdcard/boot
adb shell busybox mount /dev/block/mmcblk0p1 /sdcard/boot
adb push ***UPDATEFILE*** /sdcard/boot
adb reboot recovery
Hello all! New user here. I looked in the forums for this and can't find this question answered, but I am sure I missed it. My apologies before hand if that's the case.
I have a Nook with a 16GB SanDisk card with CM7 running off the card itself, which allows me to dualboot back to the original Nook software if I want to.
My question is this. Is there a way to automatically update CM7 and/or Google Apps without copying them to my Sd card on my PC, booting into recovery, etc?
I know there's the paid version of Rom Manager, but if I read that correctly, that only works when the Nook has CM7 running on the Nook directly and not on the SD card?
Thanks in advance for your time!
You can use adb and mount the boot partition to an empty folder on the partition CM7 sees as the SD card and push the nightly to that location... then just use adb's reboot recovery command...
(FIRST TIME ONLY) adb shell mkdir /sdcard/boot
adb shell mount /dev/block/mmcblk1p1 /sdcard/boot
adb push (UPDATE FILE) /sdcard/boot
adb reboot recovery
Thanks!
I will give this a try! Let's see if I can not break my root.
DizzyDen said:
You can use adb and mount the boot partition to an empty folder on the partition CM7 sees as the SD card and push the nightly to that location... then just use adb's reboot recovery command...
(FIRST TIME ONLY) adb shell mkdir /sdcard/boot
adb shell mount /dev/block/mmcblk1p1 /sdcard/boot
adb push (UPDATE FILE) /sdcard/boot
adb reboot recovery
Click to expand...
Click to collapse
Hi all,
i formatted my sdcard with ext3, but CM7 doesn't mount it. I changed the 'vfat' in the fstab to 'ext3', but it still dosn't mount the card. I can manually mount it with 'mount /dev/block/mmcblk0p1 /sdcard', but then I can only access /sdcard via Terminal Emulator or the adb shell. Root explorer says that it is not mounted although it is mounted. Does anybody know how to fix that?
Mister Ypsilon said:
Hi all,
i formatted my sdcard with ext3, but CM7 doesn't mount it. I changed the 'vfat' in the fstab to 'ext3', but it still dosn't mount the card. I can manually mount it with 'mount /dev/block/mmcblk0p1 /sdcard', but then I can only access /sdcard via Terminal Emulator or the adb shell. Root explorer says that it is not mounted although it is mounted. Does anybody know how to fix that?
Click to expand...
Click to collapse
Hey dude, I feel ya. I wanted to ext3 all the way, but google thought Android users would rather use fat for their sdcards so we're bound to trying to work around it. You might want to look at your sdcard permissions, check that you have "X" permissions for user, group and other, or just go crazy and do "chmod -R 777 /sdcard".
You could look into what this guy did: http://android.modaco.com/topic/308568-how-can-i-bind-mount-eg-systemsdxxx-sdcardxxx/#entry1511967
but I backed out mainly because it looks too much like more trouble than its worth.
Good luck!
Hi
Nexus 7 is rooted and trying to update ROM...Stuck on Google logo screen at start-up..
Can get into cwm recovery.
Trying to put rom in storage so I can flash it.
In the mounts and storage menu when i select mount /sdcard...Nothing happens.
When i select mount /system...the name changes to unmount /system
I just need to access the storage so i can flash my rom
I cannot see the flash storage on my computer when I select mount /sdcard or /system
So I tried just pushing the rom from adb.
#adb devices
#adb mount /sdcard (command does not work)
#adb mount /system (command does not work)
#adb push SmoothROM-v4.1.zip /sdcard/SmoothROM-v4.1.zip (just get back " _ " No transfer rates or anything)
Please help me flash this ROM
Thank You
-----------------------------------------------------------------------
Ok I fixed it...I pushed the rom using qtadb....with that software i could see the filestructure...i pushed the file to /data/media (i think)...and i could find the zip from clockwork...rom just installed...works great...
Please can some clarify how the storage works in nexus 7? Where is the sdcard files? is it stored in /data/media ?
why did the adb mount command did not work?
Adb push (file name) /mnt/sdcard/(final directory of your choice)
Shouldn't need to mount anything