Related
Hi Every body,
In quit new in Android.
I just finaly rooted en S-Off my Desire.
Now I want to copy a file in to a system map, but I cant safe in that map.
Is there a way that I can Chmod the right, so I can Copy too their.
Check the file system you're trying to copy to, it might well be mounted as read-only. If you have permanent root you should be able to remount it as read/write.
steviewevie said:
Check the file system you're trying to copy to, it might well be mounted as read-only. If you have permanent root you should be able to remount it as read/write.
Click to expand...
Click to collapse
I am permanent root, waht should i do to get the map Write.
Is their een special chmod tool.
I use ES file Explorer.
Redbaser said:
I am permanent root, waht should i do to get the map Write.
Is their een special chmod tool.
I use ES file Explorer.
Click to expand...
Click to collapse
You need to mount /system as read/write :
Code:
mount -o remount,rw /system
Make your changes, then when you're done :
Code:
mount -o remount,ro /system
steviewevie said:
You need to mount /system as read/write :
Code:
mount -o remount,rw /system
Make your changes, then when you're done :
Code:
mount -o remount,ro /system
Click to expand...
Click to collapse
From my Pc then it is:
Code:
adb shell
Code:
su
Code:
mount -o remount,rw /system/media/audio/notifications
Code:
exit
Code:
exit
Redbaser said:
Code:
mount -o remount,rw /system/media/audio/notifications
Click to expand...
Click to collapse
No, you need to remount the /system file system (/system/media/audio/notifications) is just a directory within that file system.
Then go into that directory and make any changes that you need to. Then remount it as read-only when you're done.
steviewevie said:
No, you need to remount the /system file system (/system/media/audio/notifications) is just a directory within that file system.
Then go into that directory and make any changes that you need to. Then remount it as read-only when you're done.
Click to expand...
Click to collapse
I did it whit my terminal emulator,
just you told.
I want to copy a file in that directory, it want work, premision denied
I typed
su
#mount -o remount, rw /system
Then I tried to copy
Redbaser said:
I did it whit my terminal emulator,
just you told.
I want to copy a file in that directory, it want work, premision denied
I typed
su
#mount -o remount, rw /system
Then I tried to copy
Click to expand...
Click to collapse
Check your steps again. I just created a new file in that directory fine.
Did the su work ?
You're not typing that "#" symbol, are you ? That's the command prompt when you're root.
steviewevie said:
Check your steps again. I just created a new file in that directory fine.
Did the su work ?
You're not typing that "#" symbol, are you ? That's the command prompt when you're root.
Click to expand...
Click to collapse
I treid again, I type su, then $ change in #
I type mount -o remount, rw /system (puch enter)
I open ES file Explorer, the directory is still no Rightable only Read.
I
Redbaser said:
I treid again, I type su, then $ change in #
I type mount -o remount, rw /system (puch enter)
I open ES file Explorer, the directory is still no Rightable only Read.
Click to expand...
Click to collapse
The problem is ES File Explorer isn't running as the root user. So you can do a "chmod 777 /system/media/audio/notifications" then it will work.
steviewevie said:
The problem is ES File Explorer isn't running as the root user. So you can do a "chmod 777 /system/media/audio/notifications" then it will work.
Click to expand...
Click to collapse
Wich App do i need or how can i made the explorer as root user.
Redbaser said:
Wich App do i need or how can i made the explorer as root user.
Click to expand...
Click to collapse
Are you not comfortable doing it via the command line ? There is an "experimental" option within ES File Explorer to let it run as root, but I just tried it, and it doesn't work on the stock ROM.
I checked and it looks like one of the other main explorers, Astro, doesn't work as root either.
Maybe try the Root Explorer app (hmm, though I see you have to pay for it) ? Anyone else have recommendations ?
steviewevie said:
Are you not comfortable doing it via the command line ? There is an "experimental" option within ES File Explorer to let it run as root, but I just tried it, and it doesn't work on the stock ROM.
Click to expand...
Click to collapse
I so new whit android, I Realy dont now what are you mean, Sorry
Redbaser said:
I so new whit android, I Realy dont now what are you mean, Sorry
Click to expand...
Click to collapse
If you are willing to pay for the "Root Explorer" app, which you will find on the Android market, then that should do what you want (i.e. give you a file explorer app that will work as root).
The instructions for installing 19mountsdboot are found here: http://forum.xda-developers.com/showthread.php?p=22858059#post22858059
I unrared 19mountsdboot-rev2.rar, and 19mountsdboot is in /sdcard/Download.
My problem is when I try to copy that file to /etc/init.d. Using Terminal Emulator,
cd /etc/init.d
cp /sdcard/Download/19mountsdboot .
cp: can't create './19mountsdboot': Read-only file system
Using ES File Explorer, I also get a "Read-only file system" error.
What am I missing?
Thanks
OrionNav said:
The instructions for installing 19mountsdboot are found here: http://forum.xda-developers.com/showthread.php?p=22858059#post22858059
I unrared 19mountsdboot-rev2.rar, and 19mountsdboot is in /sdcard/Download.
My problem is when I try to copy that file to /etc/init.d. Using Terminal Emulator,
cd /etc/init.d
cp /sdcard/Download/19mountsdboot .
cp: can't create './19mountsdboot': Read-only file system
Using ES File Explorer, I also get a "Read-only file system" error.
What am I missing?
Thanks
Click to expand...
Click to collapse
/etc/init.d is a root location. You must have root access and /system set to r/w.
So set terminal emulator in su (root) mode. Type su enter and the prompt will change to a #. Then you can try it. Set /system to r/w.
Also ES File Explorer must also be put in root mode and set /system to r/w before you can do it.
Edit: if you use the flashable zip, it does everything for you. Just put that zip into the boot partition of the SD and boot to SD recovery. It will install automatically. And it puts it in /data so it survives the update to a new ROM. I highly recommend you use that method.
Sent from my Nook HD+ running CM10.1 on emmc.
The latest update to .368 restricts access to /system, in particular 'mount -o remount,rw /system' won't give write access.
With the SuperSU 'supolicy' tool and a current busybox there is an easy way around the protection:
Code:
/system/xbin/supolicy --live \
"allow init_shell unlabeled file {execute execute_no_trans}"\
"allow {init_shell kernel} {device unlabeled mmc_block_device} blk_file {getattr read write open ioctl}"\
"allow init_shell kernel process setsched"\
"allow init_shell {rootfs labeledfs} filesystem {mount umount remount}"
mknod /dev/loop2 b 7 2
losetup /dev/loop2 /dev/block/mmcblk0 -o 96468992
mount -t ext4 /dev/loop2 /system
The number in the losetup command is the position of the system partition in bytes in the internal memory. (This number in blocks (bytes = blocks * 512) is displayed in the expert mode of fdisk)
This works because we do not use the device corresponding to the system partition but construct an equivalent device.
Chainfires adbd Insecure app. Try the app first but if you still can't mount and push files read this thread - [HOW TO]Make your favorite kernel adbd insecure to run ADB as root on /system
Click to expand...
Click to collapse
I can now just adb remount and have access to the system.
I could not write to /system because I somehow lost the XZDualRecovery during the last update. When installed that does the magic at startup and enables a "remount,rw" of /system. In particular it has nothing to do with .368 as I initially suspected.
The flashable zip of the XZDualRecovery contains the necessary scripts and modules.
The method proposed in my initial post has the advantage, that it builds on (heavily used) features of the (Linux) kernel and is independent of the kernel version. Kernel modules on the other hand often only work with the kernel they were compiled for.
Far from an expert, so please let me know what I'm missing. Ran all commands successfully, rebooted, but still seems like no system rw access. Does this actually create that access, or does this only enable the ability to get access, and now there's another step? Thanks
Those commands grant immediate write access, but this is not persistent.
If you need a persistent solution, you should install the XZDualrecovery (which you should do anyway!).
Then a "mount -o remount,rw /system" gives you write access.
njhuiz said:
Those commands grant immediate write access, but this is not persistent.
If you need a persistent solution, you should install the XZDualrecovery (which you should do anyway!).
Then a "mount -o remount,rw /system" gives you write access.
Click to expand...
Click to collapse
Thanks, I'll give it a try, (switched ROMs at the moment, but not for long).
I have an unlocked Bootloader, root (working!) and XZDualRecovery. I' running prerooted 5.1 Android Stock ROM. I can't write to system... I tried many commands via ADB.
Is there any workaround?
FrikandelChris said:
I have an unlocked Bootloader, root (working!) and XZDualRecovery. I' running prerooted 5.1 Android Stock ROM. I can't write to system... I tried many commands via ADB.
Is there any workaround?
Click to expand...
Click to collapse
This works for me - [2014.11.10][ROOT] adbd Insecure v2.00, install it, tick Enable insecure adb, then run...
Code:
[B]adb remount[/B]
...and that should allow you.
mount -o remount,rw /system
Works for me on 5.1 with XZDualRecovery installed (locked BL, Xposed installed, Linux adb host).
I just spent a long time trying to get write access on my Z1C, too. I'm on MX ROM and wanted to debloat some of the software.
Turns out I just had to set the SE Linux from Enforced to Permissive, then using the mount -o remount,rw /system went fine.
Code:
su -c setenforce 0
mount -o remount,rw /system
exit
EDIT:
The "su -c setenforce 0" should make the change to Permissive permanent. Will check.
EDIT 2:
I had to get the app SELinuxModeChanger (http://forum.xda-developers.com/showthread.php?t=2524485) in conjunction with the adbd Insecure app to finally get it to work reliably, now...
I tried all the solution in this post but I failed every time... Someone to explain me how I have to do?
Envoyé de mon D5503 en utilisant Tapatalk
xander59 said:
I tried all the solution in this post but I failed every time... Someone to explain me how I have to do?
Envoyé de mon D5503 en utilisant Tapatalk
Click to expand...
Click to collapse
Did you try all of them, (terminal commands in op, adb insecure app, mount -o remount command, selinux permission change..)? If so, and you still can't rw, I'd say it might be a problem with your ROM. I have used RockZ1 and MX ROM recently, and initially had issues, but at least one of these things worked for me.
In fact, I read again the topic and I have the version 21 of dual recovery, so I have the r/w permission... But i can't still see an app when I'm moving its to /system/app and set right permission
Envoyé de mon D5503 en utilisant Tapatalk
With a root browser or a terminal app you should be able so see all files... which app did you use?
xander59 said:
In fact, I read again the topic and I have the version 21 of dual recovery, so I have the r/w permission... But i can't still see an app when I'm moving its to /system/app and set right permission
Envoyé de mon D5503 en utilisant Tapatalk
Click to expand...
Click to collapse
Not sure about that... I've definitely had apps that won't install or won't open before. I'm not sure what makes something compatible or not. Maybe email developer.
It was an issue to kill the app before moving it to system app
Envoyé de mon D5503 en utilisant Tapatalk
SGP621-RICDefeat
The SGP621-RICDefeat.zip will work on latest .216 stock. It's not a flashable zip but it contains a install.bat file, wich will remove the write to system protection. Then you can download an app from play store to mount system as RW and RO.
Don't remember where i found it though, but it was somewhere in the Z1 compact forum.
XperienceD said:
This works for me - [2014.11.10][ROOT] adbd Insecure v2.00, install it, tick Enable insecure adb, then run...
Code:
[B]adb remount[/B]
...and that should allow you.
Click to expand...
Click to collapse
well when i try to tick the enable insecure adb it says could not patch,,
i am currently on 14.6.A.1.236
ok well kingroot saves the day.,
Look at this. Worked for me. Very easy. http://forum.xda-developers.com/z3-...-sgp621-lollipop-23-1-0-690-noba-ftf-t3058400
Hello everyone
following Problem: tried to Flash ARISE. but flashing ARISE fails cause r/o system
... opened terminal in TWRP and Mount | grep /System
Output: /dev/block/platform/msm_sdcc.1/by-name/system /system ext4 rw,seclabel,relatime,data=ordered
so i see, ist rw...but i cant Flash... still get read-only file error..
i also tried mount -o remount,rw /System
Mount | grep /System, again, and Output also same as before...
Output: /dev/block/platform/msm_sdcc.1/by-name/system /system ext4 rw,seclabel,relatime,data=ordered
still get Read-only file System Error...
someone have a solution or an advise? when i go to Mount in TWRP i can check System (without active Checkbox for ro mounting), and still got the Errors...
aivilon said:
Hello everyone
following Problem: tried to Flash ARISE. but flashing ARISE fails cause r/o system
... opened terminal in TWRP and Mount | grep /System
Output: /dev/block/platform/msm_sdcc.1/by-name/system /system ext4 rw,seclabel,relatime,data=ordered
so i see, ist rw...but i cant Flash... still get read-only file error..
i also tried mount -o remount,rw /System
Mount | grep /System, again, and Output also same as before...
Output: /dev/block/platform/msm_sdcc.1/by-name/system /system ext4 rw,seclabel,relatime,data=ordered
still get Read-only file System Error...
someone have a solution or an advise? when i go to Mount in TWRP i can check System (without active Checkbox for ro mounting), and still got the Errors...
Click to expand...
Click to collapse
Unlock the system partition by typing "reboot disemmcwp" in the system or TWRP terminal or ADB shell
kossie12 said:
Unlock the system partition by typing "reboot disemmcwp" in the system or TWRP terminal or ADB shell
Click to expand...
Click to collapse
tried this... phone reboots, i hold power up to go directly back to twrp... still no rw...
here is what log of ARISE says:
cp: can't create directory '/system/etc/sws': Read-only file system
cp: can't create directory '/system/etc/srs': Read-only file system
cp: can't create '/system/etc/permissions/com.huawei.audioalgo.xml': Read-only file system
cp: can't create '/system/etc/firmware/isp_dts.img': Read-only file system
cp: can't create '/system/etc/firmware/hifi_6403_tfa.img': Read-only file system
cp: can't create '/system/etc/firmware/hifi_6403.img': Read-only file system
cp: can't create '/system/etc/firmware/hifi_6402_2spk.img': Read-only file system
cp: can't create '/system/etc/firmware/hifi_6402.img': Read-only file system
cp: can't create directory '/system/etc/firmware/can_nxp': Read-only file system
cp: can't create directory '/system/etc/dts': Read-only file system
cp: can't create directory '/system/etc/codec': Read-only file system
cp: can't create directory '/system/etc/audio': Read-only file system
cp: can't create '/system/framework/com.huawei.audioalgo.jar': Read-only file System
#EDIT1:
Still the same error after
umount /System
Mount -o rw /system
Could you try in terminal app?
Su
reboot disemmcwp
kossie12 said:
Could you try in terminal app?
Su
reboot disemmcwp
Click to expand...
Click to collapse
Su not found
Sudo not found
aivilon said:
Su not found
Sudo not found
Click to expand...
Click to collapse
Seems like you are not rooted. Arise needs a rooted device
kossie12 said:
Seems like you are not rooted. Arise needs a rooted device
Click to expand...
Click to collapse
Lol not possible cause I have SuperSU on it installed runs perfectly asked me for permission for applications if they need root
kossie12 said:
Seems like you are not rooted. Arise needs a rooted device
Click to expand...
Click to collapse
I also installed Los without any problems
aivilon said:
I also installed Los without any problems
Click to expand...
Click to collapse
It was possible to make a new file in /etc and in /system with root explorer... The reload was possible without an error
kossie12 said:
Seems like you are not rooted. Arise needs a rooted device
Click to expand...
Click to collapse
Think i found the problem...
/System gets dismounted every time i try to flash ARISE
After i mount it rw over terminal, its there, flash ARISE, try to remount, cant find in /proc/mount
Wtf
aivilon said:
Think i found the problem...
/System gets dismounted every time i try to flash ARISE
After i mount it rw over terminal, its there, flash ARISE, try to remount, cant find in /proc/mount
Wtf
Click to expand...
Click to collapse
Not sure why that is happening..
Maybe someone else can help you.
I didn't run into any problems installing, but im on stock B10 (G variant).
kossie12 said:
Not sure why that is happening..
Maybe someone else can help you.
I didn't run into any problems installing, but im on stock B10 (G variant).
Click to expand...
Click to collapse
I think file system was corrupted... Restored the system from the 03.03.17, mounted over mount menu in twrp, installed...
Seems that it has worked for now cause i have esra, viper4arise etc... Strange
aivilon said:
I think file system was corrupted... Restored the system from the 03.03.17, mounted over mount menu in twrp, installed...
Seems that it has worked for now cause i have esra, viper4arise etc... Strange
Click to expand...
Click to collapse
Good to hear it works for you now.
Now its time to enjoy some music :laugh:
kossie12 said:
Good to hear it works for you now.
Now its time to enjoy some music :laugh:
Click to expand...
Click to collapse
Thanks ?
Jep a little bit better, but still not perfect :silly:
Hello dear community,
I'm now struggling for some days to enable ad-blocking on my Huawei Nova with Android 7 Nougat (CAN-L01C432B340). I simply only need root to edit the hosts file and then un-root my device (that can be easily done by flashing boot.img via fastboot again). Reason for un-root is to be able to play Pokemon Go which has a root-block.
Following steps have been tried with root enabled
First things first: The normal way of using AdAway to create a hosts file does not work anymore: It seems to be impossible to remount the /system partition with r/w (read more) with the app.
So I tried many things so far to gain r/w while Android is booted up
Reversed the order on how we give the options to mount as suggested in chainfires posts: mount -o rw,remount /system fails (same does mount -o remount,rw /system)
Installing busybox to have another (probably working) mount command: Installation fails because of no rw on /system (doh)
Flashing busybox installable zip: The binaries seem to be gone when Android is booted up (but are visible in TWRP)
Using another busybox installer seem to be able to at least temporary flash busybox to /system/bin. Yet, busybox mount -o rw,remount /system did not make /system rw.
Flashing systemless AdAway also fails (similar to flashing busybox, the files are written but mystically, all changes are gone after booting into android).
Now I unrooted my device
Then I thought, why not use TWRP and mount the partition with rw there and copy my own custom-made hosts-file to /system. And hey, mounting with rw works! Also even writing and all kind of stuff.
But now the bummer: No matter what I do, the hosts file, formerly written to e.g. the /system partition is reverted back to default after a reboot to android. The strange thing: My modification is still there and visible in TWRP
Investigating on how the hosts file is managed in a booted-up android, I found out, /system/etc/hosts is symlinked to /vendor/etc/hosts.
So I mounted the /vendor partition in TWRP and copied the hosts file there.
mount /dev/block/platform/soc/7824900.sdhci/by-name/vendor /system && cp /external_sd/hosts /system/etc
After a reboot, I noticed /vendor/etc/hosts (= /system/etc/hosts) just has the default entries :crying: Strangely, when I now root my device again, the hosts-file shows my entries (but I need to be un-rooted )
It seems like that all changes done to any partition are somehow reverted back by the kernels drive-mapper. Does anyone have an idea on how to write a hosts-file to my system, which persists when I boot up android and does not require to be permanently rooted?