Hi, I have an atrix running adeo 0.1, (deodexed), and initially rooted with the oneclick method, then redone with dg's aRoot mod. I just noticed yesterday my system partition always mounts as r/w on boot, is that normal? If not, any idea what's wrong / how to change? Thanks in advance, you guys here are always the best help.
I assume because of root access, this is normal. correct me if i'm wrong
its just i dont ever remember the system partition mounting as r/w... and ive always run a rooted phone. anybody else want to do a quick check on their phone and see? thanks!
Mine mounts as R/O. Rooted with superoneclick.
PixoNova said:
Mine mounts as R/O. Rooted with superoneclick.
Click to expand...
Click to collapse
thanks for checking. after reading i found out its a feature of the aroot method i used. i had used superoneclick before and it mounted as r/o.
id rather keep the system partition r/o and mount it r/w only when needed, just to be safe. thanks guys!
Related
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
Well, I tried a few things. DarkTremor didn't work for me, not sure why. I tried firerat's script for apps2ext, but it required rw access to /system to install. I tried editing the script, as well as doing everything manually, still no joy.
So, my question is thus: any pointers?
EDIT:
Another, related, question: could I symlink /data/app to /sd-ext/app? Would that work, assuming I mounted the ext partition early in the boot sequence?
I got it now.
Swyped from my Galaxy Tab
My droid 2 is rooted and bootstrapped. I sbf'd to stock then updated to 2.3 then rerooted. No wipe no clear cache. Contacts ok, phone works fine. Just ran bootstrap again as I am getting ready for custom rom install. When I hit REBOOT RECOVERY and navigated around I noticed my system is apparently not mounted. It says mount system. Should I mount system now or leave it alone? I do not understand what exactly I am doing by mounting system. Please advise.
Sent from my DROID2 using Tapatalk
Mounting basically gives bootstrap the ability to change, delete, or alter anything in the system folder. This must be done to install custom roms.
Sent from my DROID2 using XDA App
I must mount system before I install zip from sd, or is this typically done after installation? I'm still reading and trying to take all this in and put it together into a cohesive process in my mind before I proceed. I've come this far w/o bricking(he knocks on wood).
Sent from my DROID2 using Tapatalk
it depends,
if the update zip is written correctly you don't need to mount system.
for example all Fission update-zips since 2.3 mount system themselves so you don't have to worry.
if you are unsure, you should always mount system.
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.
*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