I have a problem with making a /system folder into read/write permission. I made root (TWRP 3.2.3, SuperSU-v2.82 - in TWRP is unchecked read-only) and the problem is tablet freezes EVERY time a make change from RO to RW.
I used Root explorer, ES file explorer, Root file manager, Super manager... Every time when I change it and press "ok" tablet freezes. Also I try via terminal "mount -o rw,remount /system", nothing, a download apk "Mount system RO RW ROOT" and apk said it did it, by when I check in file explorer it is still read only. (also I try via fastboot and comannds pull and push and it said that file is read only)
I really need to make changes in /system/build.prop and I'm out of options...
Anyone?
Related
I'm interesting in make some changes in init.rc file.
As I have read, I must get copy of boot.img, unpack it, add my changes to init.rc file, pack and push back new boot.img to phone, and after reboot my changes will be considered. (I can't just change init.rc file, that is at / directory, due to it will be rewritten at next reboot.)
So I try:
adb shell
su
fdisk -l /dev/block/mmcblk0
fdisk outputs list of all partition (mounted and unmounted) which are on phone.
I'm intersting in boot:
9 147456 163839 8192K 0700 BOOT
where 9 - is partition number, so my partition (device to mount) is /dev/block/mmcblk0p9.
Then I remount rootfs to read/write permissions:
mount -o rw,remount rootfs /
Create directory (mount point) /boot:
mkdir /boot
And then try to mount boot partition to /boot:
mount -t auto /dev/block/mmcblk0p9 /boot
but retrive "mount: No such device".
Are anybody faced with this ?
Thanks in advance for you help.
PS:
List of partitions can be also obtained by:
ls -l /dev/block/platform/dw_mmc.0/by-name
Edited:
I have sources, but I don't want to rebuild their, due to a large amount of time compilation. (I must make many changes in init.rc file and recompile all CyanogenMod it's very expensive).
I have tried to build only module tied, as I think, with init.rc (system/core/rootdir), just type mmp:
ila:~/cm_s4/cm_12_1/system/core/rootdir$ mmp
and obtained next line:
Install: /home/ila/cm_s4/cm_12_1/out/target/product/i9500/root/init.rc
but, no line such as (for example, when I type mmp in external/hello_world):
Pushing: /system/bin/hello_world
Hi I have an HTC ONE rooted. I would like to modify a file in the /system/etc folder, but even if I mount through the terminal the file system in write mode, when I try to modify something with my editor, it says "only read file system".
The command I used is
"mount -o rw, remount -t rootfs /system"
Any suggestion? Android version is 4.3
Thanks!
You have to change the permission if you are not allowed.
chmod 777 file_path
It will give permission to read/write/execute to all the users,group,other
Update
Before this do execute the below commands
adb shell
su
mount -o rw,remount rootfs /
For rooted device:
Goto
ES File Explorer
From left Menu Enable Root Explorer
Click on the same row (Root Explorer) a pop-up list will occur.
Select Mount R/W > select RW for both root(/) and system (/system) path.
OK
NOW YOU CAN EVEN REPLACE(OVERWRITE) any /system/etc folder.
Tested on My 4.4.2 OS
Enjoy !!!!
I'm trying to run sqlite3 on my rooted Nexus 4. I've gotten as far as pushing the executable to /sdcard but I cannot execute it. I'm running stock Android 4.3, rooted with SuperSU 1.45.
The file looks like this:
-rw-rw-r-- root sdcard_rw 36860 2013-09-30 17:29 sqlite3
So far:
chmod 777 sqlite3 does nothing
File.setExecutable() returns false (but File.exists() returns true).
Is there a better way to do this?
SD cards are usually formatted as FAT32 and mounted with all files unexecutable. SD card directory on Nexus 4 is a simulated one, but still the system prevents any file in it to be marked as executable. You need to move your file outside of your SD card to mark it as executable.
I know this is an old question.
But I want to suggest another work around for this problem by creating disk .img file in sdcard then mount it on /data/
Well, I know it was quite redundant, but at the very least it could be used as workaround if your internal disk was low on space.
Here, some instructions in case needed.
adb shell to your device,
go to /sdcard (mouting point may vary on each device)
dd if=/dev/zero of=<your-new>.img bs=1M count=0 seek=2048. This creates a new image file called <your-new>.img change the seek value to the size you want (e.g 2048 = 2GB). If dd not available, try to install busybox first, then from dd change into busybox dd
Format <yout-new>.img, in my case I used ext2. eg. mke2fs -F ubuntunew.img
Mount <your-new>.img to /data. eg. mount -o loop /sdcard/<your-new>.img /data/<your-mount-point>. If mount command not available use busybox.
Ok. That's all
References:
https://forum.xda-developers.com/showthread.php?t=2743108
https://linuxonandroid.uservoice.com/knowledgebase/articles/74683-how-to-i-give-linux-more-space
chmod 777 sqlite3 does nothing...
chmod +x doesn't work... I get "bad mode".
The "Bad Mode" is from a+x, +x, etc. Remember, its octal. Try:
chmod 0777 sqlite3
And Yuichi is probably correct - /mnt/sdcard is likely mounted with noexec.
I use a Samsung Dart - SGH-T499 with Android v2.2.2 on it.
Now I need to edit the /system/etc/bluetooth/audio.config file. For that I rooted my phone using the SuperOneClickv2.3.3-ShortFuse. And browsed the file-system using Root Explorer. But I am unable to edit the permission of the audio.config. Could you please help me?
You also need to ensure that the /system directory, as it's a filesystem, is mounted read-write. In the adb shell use -o rw,remount as parameters to the mount command to do this. First you need to determine what ( hardware / physical / logical ) device that particular filesystem is stored on - use the mount command on its own to see the list and select the one which has /system as its mount point.
Can you not issue a
chmod 777 /system/etc/bluetooth/audio.config
...from the adb shell?
How to pre-install an Android application?
Because I have a specific device, and I wanted to make my application pre-installed.
I'm assuming you're talking about a rom here.
If you want the user to be able to delete the application you should put the .apk file in "/data/app"
If you want to have the app behave like a system app (like e-mail or calendar) you can put the .apk in "/system/app"
First we need all the pre-requisites needed.
We need to root our device to have super user capability, In my case I root my nexus one
Im not responsible if your device brick so be careful.
(http://forum.xda-developers.com/showthread.php?t=611829)
install superuser
(http://www.appbrain.com/app/superuser/com.noshufou.android.su)
Install BusyBox (to do shell command "cp") -- available in android market
(http://www.appbrain.com/app/busybox/stericson.busybox)
Execute the following commands in the terminal emulator to remount the /system directory as read/write and to install the application into the /system/app directory (http://www.nexusforum.net/nexus-one-application-day/524-nexus-one-app-day-2-8-10-powermanager.html):
adb shell
su
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
cp /sdcard/sample.apk /system/app
Thanks for all those who helped me.