If I mount a write protected system partition with a command like "mount uw /", how important is it that I end with a "mount r /" before finishing/rebooting/shutting down/whatever? I'm a linux noob clearly.
On a similar topic, with our phones in root explorer, how important is it to return to RO access after making changes with RW?
Thanks
Related
In the instructions from this article:
http:***//droidbasement.com/db-blog/?p=70
it is said that mounting the /system partition from recvovery is possible but I don't find find any option for that... So, is it a mistake or is there really an option to do it?
venezia64 said:
In the instructions from this article:
http:***//droidbasement.com/db-blog/?p=70
it is said that mounting the /system partition from recvovery is possible but I don't find find any option for that... So, is it a mistake or is there really an option to do it?
Click to expand...
Click to collapse
using a computer with adb set up, connect to usb and on computer, in command prompt, type:
adb shell mount -a
(should mount /system rw. Just did it and it did for mine)
It is possible in AmonRa's recovery. Go to console and type "mount /system" without the quotes. This can also be for "mount /sdcard" "mount /system/sd" and any partition in fstab.
FaJu said:
It is possible in AmonRa's recovery. Go to console and type "mount /system" without the quotes. This can also be for "mount /sdcard" "mount /system/sd" and any partition in fstab.
Click to expand...
Click to collapse
Hello... not on a nexus one.
A) No console on nexus recovery because
B) It has no physical keyboard.
Oh ****... I thought I was in the Dream forum. My bad!
So I guess it was just a mistake in the article and that only ADB mount will do the trick. Thanks guys
Hi Guys,,
I have installed CF3D on my GNote but when I was about to install CF Drivers it says that my /system is insufficient, so I check it right away by using df -k on a terminal emulator and found out that 100% space used on /dev/block/mmcblk0p9. My solution to this is to remove some system app, I have tried Titanium backup but no good,so i decided to use root explorer and delete some app is system/app, the weird thing is that i could not mount the /system as r/w, so i decided to remount /system as rw using a terminal emulator, i used this command
mount -o rw,remount /dev/block/mmcblk0p9 /system
but still i could not delete data on /system/app... another weird thing is that I could not list the directories or files in the /system using "ls" command in terminal emulator, the error says, "value too large for defined data type".
My questions
1. is this part of the mmc_cap_erase bug, because if i remember very well, i have flashed something on cwm which causes FC's on my device right after that, my internal sd card and external sd card is unreadable , and then when it ask to reformat it and i click yes, then everything is ok, after that i changed ROM (from criskelo v8 to kingdroid v3) and i never encountered that bug again.
2. is there any way to mount /system as r/w? or is there any other way to uninstall system app. Ive tried every "free apps" on the market to uninstall system app but i could not find a successful one.
3. if this is part of the mmc_cap_erase bug, can i used the fix in this thread http://forum.xda-developers.com/showthread.php?t=1667886 to solve my problem??
Thanks to those who are willing to give me some advice.
I would like to mount an ext2 partition that is readable/writable without root privilege. My hope is to put a Debian installation on it. I figure I might as well be able to use the partition for general storage as well. Unfortunately, my current setup insists on root access to touch the partition. Is there any way my regular CM7 user privilege can read/write to the ext partition?
Update:
My last phone (before it was run over by a car) would not allow the remounting of /system as read/write. Now that I have a N1, I mounted system as rw [mount -o remount -o rw /system] and edited /system/etc/init.d/05mountsd. The $SD_EXT_DIRECTORY line formerly read "$BB chmod 771" (I think). It is editied to read "$BB chmod 777".
Linux experience tells me that this is weird; I would rather change ownership, but it appears that Android abuses the user concept. I am not a user; applications are users. I do not believe that I have a user to give SD rights. I guess as long as no one ever wants multi user Android its OK. Otherwise it will end up biting them in the ass--a la multiuser windows.
I'm attempting to format my external sdcard to ext2, just one single partition (no apps2sd magic).
The reasons are to have the ability to store >4GB files on the card, faster read times, and not needing compatibility with any M$ systems/PCs/Junk, journaling (>ext2) is not needed.
At the moment, I'm running a CM based ROM (cyanfox) and will likely try this out on a moto/stock based ROM after.
Here is my progress so far :
I'm able to mount the SD manually, though with some hoops being involved. The bionic will not mount it automatically, and is constantly telling me that it is unsupported/empty/needs to be formatted in the storage menu, and a permanent notification.
In a terminal shell, I can mount the device (/dev/block/vold/179:97) by specifying the type only as ext4. This is definitely not ideal, but I get errors when the type is specified as ext2 or ext3. (error : mount: Operation not supported on transport endpoint ).
At the moment, I've made an init script to mount the sd at /storage/sdcard1 but this doesn't cause android to think that the actual sd is mounted properly (empty sd notification still exists). Though it is at least mounted.
And I have edited the fstab file at root to change the sd type from vfat to ext2, but this file rewrites itself at boot. Unfortunately I'm not able to set an immutable bit on the file.. (android is not a type writer).
The ext2 filesystem has been checked for errors, does have files written to it, and is able to be read/written to in android after manually mounting it. Android just insists on a fat partition though.
Any help/tips would be appreciated. I'll update this thread in case anyone else would like to apply this as well.
Also, if I'm missing something blatantly obvious, please let me know
Yes i can't mount any partiotion of the sd card to the phone under lollipop, i tried everything, this is because i can't use link2sd or foldermount, so i tried using commands in terminal emulator like mount -t sdext4 -o rw /dev/block/vold/179:66 /data/sdext2 , the command seems to works at first but the folder is still empty, i used the directory bind commands lime mount -o bind but this isn't working either, it seem that lollipop broke something in this phone or is using another metod.
Foldermount isn't working for me either. Be aware of namespace isolation for mount as default in SuperSU. Check it here http://su.chainfire.eu/#how-mount
Same Here. I have Stock 5.0.2, root, TWRP. I can create a Mountscript with Link2SD, but after the neccessary reboot, it is impossible to move items since "/data/sdext2 could not be mounted". I think, some boot procedure from Motorola messes with the Link2SD Skript.
Okay little UPDATE: If you go into supersu and disable this namespace option, sdext2 can be mounted. Link2SD warns, that the mounting isn't possible while booting , so the apps moved by Link2SD are invisible. If you do a quick reboot from Link2SD, the apps can be seen. So it works, but is rather complicated. Also, not every app seems to be movable...