Database Develop

Need Help Mount /system

Everything is working in my kingdroid v3.0
but when i install chainfire it asks for installation of driver
and could not write to /system
i used root explorer and everything else but the /system r/o cant be changed to
its stuck at R/W and i cannot copy or do whatever ...
i try to set permissions but it says read-only .... how can i change this into R/O mode????????

[Q] Xperia Z reebot when writing to system

After folowing all the steps on this guide (http://forum.xda-developers.com/showthread.php?p=41997803#post41997803) to finnaly have .253 rooted, it seems I can't write to system. Every time I try to uninstall system app using titanium backup, the phone reboots. The selected app is uninstalled, but I have to do it one by one, cause it reboots always after unistalling. Same when trying to integrate dalvik cache files to the rom with Titanium Backup or to integrate an updated app to the room. When I open the File Manager, the phone instantly reboots too... Any idea about how can I fix it?
Thanks!
Rebooting Fixed!
If someone else is facing the same problem, I fixed rebooting issue while writing to system following this guide, thanks to the user [NUT]:
[XZDualRecovery][v2.3 RELEASE] cwm 6.0.3.2 & twrp 2.5.0.0 [locked bootloader]
CWM Usage warning: Root can be lost (almost worst case), a bootloop can be experienced (worst case) or a reboot upon remounting /system to be able to write to it (most cases, relatively harmless) when using CWM and before a reboot out of recovery answering the question 'ROM may flash recovery, fix it?' question is answered with 'yes'. This can be recovered from by opening a terminal app and typing the following commands:
Code:
su
/system/bin/stop ric
mount -o remount,rw /system
chmod 755 /system/etc/install-recovery.sh
Alternatively you can boot in to TWRP and go to the Advanced menu -> File manager and look for /system/etc/install-recovery.sh to set permissions 755 on it.

You need to reroot, as that is the issue.
From me to you.

hum...
It means... downgrade to.434, root again,... reflash .253?

.LEONARDO. said:
It means... downgrade to.434, root again,... reflash .253?
Click to expand...
Click to collapse
Whichever way you want, but this is a root related problem.

Xperia Z rebooting while writing to system FIXED
Rebooting Fixed!
If someone else is facing the same problem, I fixed rebooting issue while writing to system following this guide, thanks to the user [NUT]:
[XZDualRecovery][v2.3 RELEASE] cwm 6.0.3.2 & twrp 2.5.0.0 [locked bootloader]
CWM Usage warning: Root can be lost (almost worst case), a bootloop can be experienced (worst case) or a reboot upon remounting /system to be able to write to it (most cases, relatively harmless) when using CWM and before a reboot out of recovery answering the question 'ROM may flash recovery, fix it?' question is answered with 'yes'. This can be recovered from by opening a terminal app and typing the following commands:
Code:
su
/system/bin/stop ric
mount -o remount,rw /system
chmod 755 /system/etc/install-recovery.sh
Alternatively you can boot in to TWRP and go to the Advanced menu -> File manager and look for /system/etc/install-recovery.sh to set permissions 755 on it.

Root problem

I rooted my C5303. When I give Link2SD root permission or set mount options to R/W in ES Explorer, my phone reboots in 5 seconds. I also can't install CWM on my phone, because immediately after giving root permission, my phone reboots. Help please!
Edit: Fixed by rooting again.

how can i mount system at 5.1 (UL,Root,Stock-Rom)?

Hey there browsing with all those ads is a real pain, therefore i wanted to edit the hosts-file since adaway didn't worked.
Therefore i wanted to use the content of this page and add it to my hosts-file:
http://someonewhocares.org/hosts/
problem is, i can't mount /system with total commander although root is working (flashtool installed busybox fine as the root popup comes up and asking for root).
the bootloader is unlocked and via adb shell in root mount i also get:
Code:
[email protected]:/ # mount -o remount,rw /system
mount -o remount,rw /system
mount: Operation not permitted
is there another way? can i somehow flash the hosts-file trough recovery?

You must not have full root. Install RIC Killer or XZDR to defeat this protection.

i thought only "temp root" existed besides the full root? well NUTS Dual Recovey is also installed... gonna check out the RIC Killer...
:Edit: Ok, neither the "Windows" RIC-Reboot Remount Fix worked, as the ZIP-Version trough Dual Recovery....
what would be the best way to reinstall root (altough it is an system app?)

The command you specified works fine for me. Further, root explorer via ES Explorer.
What root APK do you have installed? SuperSU, for example, has a "complete unroot" command you can use unroot.... but since there's no one-click root for 5.1.1, re-rooting isn't possible without reflashing. I suppose a dirty flash back over top 51.1 isn't as risky as between versions, so you could try that in order to re-root.
How did you root initially? My process for 5.1.1 has been to flash the FTF, SuperSU, and XZDR all in one go, no reboots between. People have had issues getting full root to work especially if the SuperSU and XZDR steps are separated by a reboot.

sorry for the long pause i was at vacation and there i had no chance to try something (since a backup would be needed first in case of fire )
I've been installing a prerooted tft the day 5.1.1 came out. RIC Killer didn't worked and fully unrooting well... doesn't work either
Flashing a zipped SuperSU or something like that won't work? I mean - i can unroot it go to XZDR and flash it again - this should work right?

[Fix] Systemless SU - Some apps not seeing root

There have been quite a bit of people with issues with Systemless root, there are some apps that are not recognizing root, i had this issue with my Oneplus One on COS 13.1 and now the same thing works with our OnePlus 3 on OxygenOS
I had come across this on another forum, i don't recall where so i don't want to take the credit for this, i just want to provide the fix for people who have this phone and having issues
Download Terminal from app store and type
Code:
su
mount -o remount,rw /system
touch /system/bin/su
mount -o remount,ro /system
reboot

Thank you ! Before I try this , can you tell me what this method is doing ? All I can tell is that it is mounting something as read only instead of read write

I belive it creates a dummy file bc some apps require it to show as a system file

SDMU said:
Thank you ! Before I try this , can you tell me what this method is doing ? All I can tell is that it is mounting something as read only instead of read write
Click to expand...
Click to collapse
Code:
1. su
2. mount -o remount,rw /system
3. touch /system/bin/su
4. mount -o remount,ro /system
5. reboot
1. To get root privileges
2. Remounts /system partition in writable mode
3. Creates an empty file called su to /system/bin/ folder
4. Remounts /system partition to read only mode.
5. reboot
Edit. As stated above, some apps still check root access by looking su file in /system/bin folder

Squabl said:
1. To get root privileges
2. Remounts /system partition in writable mode
3. Creates an empty file called su to /system/bin/ folder
4. Remounts /system partition to read only mode.
5. reboot
Edit. As stated above, some apps still check root access by looking su file in /system/bin folder
Click to expand...
Click to collapse
This defeats the purpose of a system less su, I.e., not modifying the system partition. Step 3 modifies the system partition.
The reason apps are not seeing the su in system less state is because they have been written incorrectly. Chainfire already said these apps should be re written

candiesdoodle said:
This defeats the purpose of a system less su, I.e., not modifying the system partition. Step 3 modifies the system partition.
The reason apps are not seeing the su in system less state is because they have been written incorrectly. Chainfire already said these apps should be re written
Click to expand...
Click to collapse
Yes, it "disables" systemless root and afterwards it is just a root and banking apps and ota updates etc will fail. I don't need systemless root so I have modified my system partition to get some poorly coded apps to function. This method is not recommended if you need systemless root and it's a good thing that you pointed that out!