Sorry if this has been asked before...
I'm on stock 2.1 rooted. In order for me to access /system or /data, I must mount it manually via recovery. Is there any way that they may be accessed (from the phone preferably, but at the very least from the computer) while the phone is booted?
Thanks In Advance
in short, no. Phones that can do that are S=OFF, whereas the Aria is S=ON. You have to be in Recovery to mess with the /system or /data stuff
It's helpful to know what its called.
So, would AlphaRev 2 work?
Hmmm, I installed Darktremor Apps2SD 2.7 Update 3r1 and now i can see /system in astro
NuNinja said:
Sorry if this has been asked before...
I'm on stock 2.1 rooted. In order for me to access /system or /data, I must mount it manually via recovery. Is there any way that they may be accessed (from the phone preferably, but at the very least from the computer) while the phone is booted?
Thanks In Advance
Click to expand...
Click to collapse
NuNinja said:
Hmmm, I installed Darktremor Apps2SD 2.7 Update 3r1 and now i can see /system in astro
Click to expand...
Click to collapse
When the phone is booted normal, the /system and /data partitions are mounted in readonly mode, that is why you see them in Astro. In order to write or modify these partitions, you need to have the phone in recovery mode and mounted as read/write.
I should have considered that.
It just seemed odd because I couldn't see it before and still cannot see /data...
NuNinja said:
I should have considered that.
It just seemed odd because I couldn't see it before and still cannot see /data...
Click to expand...
Click to collapse
When I fire up Astro, I can select the Up button and that will take me to / on the phone and I can see /acct, /cache, /data, etc. I have to scroll the screen, but all of the directories show up.
But if you open them, are they empty?
NuNinja said:
But if you open them, are they empty?
Click to expand...
Click to collapse
Astro doesn't run as a rooted application, therefore it can't see the contents of readonly folders. If you open up a terminal emulator window and type 'su' at the $ prompt to gain root access, then you could do a 'ls /data' and see the contents.
Related
Sorry guys, I thought I could handle this, but I just tried to update to Hakuro's new rom, but I think my problem is something else. Let me explain.
I used to have H's Cupcake build and I just wiped, installed the radio, installed the SPL and installed the new firmware. I used a Linux machine for format my 4gb memory card with 3gb fat and 1gb ext2 and I extracted the zip file into its own folder.
I have tried doing an "adb shell ls /system" and it shows there are no files there. Have I lost root access? Is that what would make that folder vanish for me?
if you're booted into recovery, /system isn't mounted.
is that the case?
Ah, yes. I guess I was getting a little over worried about nothing. So at least I don't have to worry about 'that' being the problem of why my phone keeps rebooting.
I can wait until the main thread gets unlocked... Unless anyone wants to share some ideas?
madelk said:
Ah, yes. I guess I was getting a little over worried about nothing. So at least I don't have to worry about 'that' being the problem of why my phone keeps rebooting.
I can wait until the main thread gets unlocked... Unless anyone wants to share some ideas?
Click to expand...
Click to collapse
if you didn't wipe, i'd def try that
I did. I expect that doing "adb shell ls /sdcard" should work in recovery, correct?
madelk said:
I did. I expect that doing "adb shell ls /sdcard" should work in recovery, correct?
Click to expand...
Click to collapse
/sdcard isn't mounted in recovery, either.
if you do:
adb shell
...then...
mount /sdcard
you can read / write to the card just fine
Ahh, I thought a messed up the Apps-SD step. I'm getting a message saying:
"mounting /dev/block/mmcblk0p1 on /sdcard failed: Invalid argument"
Hmm, my Linux machine sees the partitions just fine.
/dev/sdb2 fat32 2.74GiB
/dev/sdb1 ext2 1.00GiB
Both appear to be primary partitions.
I tried doing a "busybox df -h" in ADB and it didn't list my SD card.
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
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!
I've given up on reformatting the internal memory as EXT4 (my last post). However now, I want to mount an external SD card that is EXT4 (or any file format that has UNIX permissions). I can't get my device to mount the card, it says the filesystem is unsupported. Now, that's bull**** since Android has built in support for EXT. After searching threads here on XDA and Google, and even purchasing EzyMount as recommended, I can't get it to mount. I've tried BusyBox and mount commands (as root), with various errors such as "mount operation not supported on transport endpoint". I'm at my wit's end by now, trying to get some filesystem which has support for symlinks and UNIX permissions... any ideas?
kcattakcaz said:
I've given up on reformatting the internal memory as EXT4 (my last post). However now, I want to mount an external SD card that is EXT4 (or any file format that has UNIX permissions). I can't get my device to mount the card, it says the filesystem is unsupported. Now, that's bull**** since Android has built in support for EXT. After searching threads here on XDA and Google, and even purchasing EzyMount as recommended, I can't get it to mount. I've tried BusyBox and mount commands (as root), with various errors such as "mount operation not supported on transport endpoint". I'm at my wit's end by now, trying to get some filesystem which has support for symlinks and UNIX permissions... any ideas?
Click to expand...
Click to collapse
you fully rooted with custom kernel or only with rdlv etc?
First you gotta figure out how to mount this damn thing, gotta be possible.
Then you need to get this done on bootup, either in init.rc or init.d or smth.
You probably just use wrong commands? But I could be wrong, didnt try that yet but would also be interested. Having the file permissions also on SD would be nice, but it could cause trouble with mtp maybe?
zroice said:
you fully rooted with custom kernel or only with rdlv etc?
First you gotta figure out how to mount this damn thing, gotta be possible.
Then you need to get this done on bootup, either in init.rc or init.d or smth.
You probably just use wrong commands? But I could be wrong, didnt try that yet but would also be interested. Having the file permissions also on SD would be nice, but it could cause trouble with mtp maybe?
Click to expand...
Click to collapse
I am rooted, but stock ROM and kernel. MTP is for connecting to a computer? If it is, I don't need that. I have tried
mount -rw -t ext4 /dev/block/mmcblk1p1 /storage/extStorageCard
and variants switching the flags and options.
Interesting... I just typed that command in to make sure I didn't make any typos.... and my phone crashed and rebooted. I typed it again to see if it would cause another crash and it appears to have mounted the card! Whwn I type "df" at the prompt it now shows a 28.6 GB filesystem at that location, which has to be my sd card.
Why, how, I don't know. It works, it's all I can say.
*Redmi 7a MokeeOS PIE built in root*
Hi, I was able to root the ROM with mokee add-on su, but root apps give me error "unable to mount system R/W"
So I remounted using ADB:
>ADB ROOT
>ADB REMOUNT
It worked successfully as R/W. But it doesn't last as default. It automatically comes back to RO
.
.
*IN SHORT*
I want a way to mount system read/write permanently without worrying if it will automatically be set back READ ONLY
Any help I'd appreciate it
I tried fixing SELinux, didn't work.
I have the same problem, in stock is also like this, you can not move apps to the system partition because it can not mount as writable.
Luelu said:
I have the same problem, in stock is also like this, you can not move apps to the system partition because it can not mount as writable.
Click to expand...
Click to collapse
You can mount it with debugging as mentioned:
>ADB ROOT
>ADB REMOUNT
But the problem is, it's only temporarily