Unable to mount /RW - Xperia Z5 Q&A, Help & Troubleshooting

Is anyone having the same issue?
Cant do it in ES Explorer or root Explorer.
On 6.01 and rooted.
Will
Sorry for the typos..am using auto correction.

i have the same issue build .253.

doinkydoink said:
Is anyone having the same issue?
Cant do it in ES Explorer or root Explorer.
On 6.01 and rooted.
Will
Sorry for the typos..am using auto correction.
Click to expand...
Click to collapse
sandeep_sp said:
i have the same issue build .253.
Click to expand...
Click to collapse
How did you guys root your phone? If you have rooted your Z5 using tobias.waldvogel's rootkernel, make sure you have disabled Sony RIC. It prevents mounting the /system partition for writing.
An extract from the thread by tobias:
Sony RIC is enabled. Disable?
I prefer not to disable it in order to keep my phone more secure. Unfortunately there are a lot of bad guys in this world and SELinux and RIC still can save us if someone discovers a new kernel exploit.
Sony RIC basically prevents mounting the /system partition for write. You can still modify it in recovery of of course, but if you require write access to /system without entering recovery then you need to disable it.
Read the complete thread here.

Related

[Q] Write to /system folder?

I am trying to place an app into the system/app/ folder of my Droid Maxx. I tried ES File Explorer and got "permission denied" each time, then read recommendations to buy Root Explorer which is good for situations like this as it can mount system as r/w so I tried that but it will not work either. I am rooted and on latest firmware update.
What would be preventing write permission for a root user? Is there any way around this? Push via ADB? Or would I run into the same problem via that method?
You will need to boot into your recovery to bypass write protection, make your changes, and then reboot normally.
Or follow the instructions to permanently remove the write protection.
http://forum.xda-developers.com/showthread.php?t=2551113
THANK YOU!
Teksu said:
You will need to boot into your recovery to bypass write protection, make your changes, and then reboot normally.
Or follow the instructions to permanently remove the write protection.
http://forum.xda-developers.com/showthread.php?t=2551113
Click to expand...
Click to collapse
You are awesome, thank you so much! I have been Googling all day and couldn't come up with much beyond Jcase's root method threads (which I already used but did me no good in overcoming this WP). I see this is a recent development, convenient!

[Q] I have a problem with data being deleted on reboot?

Hi,
I rooted my phone because I wanted to use an application called FolderMount, so I could store big chunks of data from apps onto my SD card.(it seems as though the SD card is useless on Android)I am using an HTC Desire 601, with Android version 4.2.2. Now my problem is that, I'm having an error with FolderMount because of something to do with external SD card r/w permissions.(no this is not specific to the app, it's a software wide problem, that's why I'm posting here.) So I found a "fix" that involved editing platform.xml and adding a line. However, everytime I try to edit it, either the phone just reboots, or no changes are made. Basically, the system folder is denying me r/w access. In root explorer there is a feature to mount it temporarily as r/w, but then if I reboot my changes are lost. This is a problem which I think is also not allowing me to install Busybox. Please help me with this. Thank you.
Jason1712 said:
Hi,
I rooted my phone because I wanted to use an application called FolderMount, so I could store big chunks of data from apps onto my SD card.(it seems as though the SD card is useless on Android)I am using an HTC Desire 601, with Android version 4.2.2. Now my problem is that, I'm having an error with FolderMount because of something to do with external SD card r/w permissions.(no this is not specific to the app, it's a software wide problem, that's why I'm posting here.) So I found a "fix" that involved editing platform.xml and adding a line. However, everytime I try to edit it, either the phone just reboots, or no changes are made. Basically, the system folder is denying me r/w access. In root explorer there is a feature to mount it temporarily as r/w, but then if I reboot my changes are lost. This is a problem which I think is also not allowing me to install Busybox. Please help me with this. Thank you.
Click to expand...
Click to collapse
Stock rom?
Which root app do you use?
LS.xD said:
Stock rom?
Which root app do you use?
Click to expand...
Click to collapse
I'm using the default version of Android that came with my phone, if that's what you mean. And umm what do you mean by which root app did I use?
Jason1712 said:
I'm using the default version of Android that came with my phone, if that's what you mean. And umm what do you mean by which root app did I use?
Click to expand...
Click to collapse
You said you "ROOTED" your phone. That means you have some kind of "SUPERUSER" app installed. I hope so at least
LS.xD said:
You said you "ROOTED" your phone. That means you have some kind of "SUPERUSER" app installed. I hope so at least
Click to expand...
Click to collapse
Oh okay I have the SuperSU app it's SuperSU v1.93 I don't know if it's the latest version. Sorry, I'm new to this rooting stuff. I only got this phone this Monday, and I only got to know about rooting the day after.
Jason1712 said:
Oh okay I have the SuperSU app it's SuperSU v1.93 I don't know if it's the latest version. Sorry, I'm new to this rooting stuff. I only got this phone this Monday, and I only got to know about rooting the day after.
Click to expand...
Click to collapse
Open SuperSU and check if access is granted for "FolderMount"
Do you use free FolderMount? Thats limited to 3links at all.
What type of sd card do you use?
LS.xD said:
Open SuperSU and check if access is granted for "FolderMount"
Do you use free FolderMount? Thats limited to 3links at all.
Click to expand...
Click to collapse
Yes, of course access is granted. I have only tried to create one link so far...so it can't be anything to do with the number of links permitted in FolderMount. I mean, I haven't been able to create a single working link. Precisely, the error I'm getting in FolderMount has something to do with sd card r/w permissions(I've linked a screenshot;maybe you've had this problem before and you solved it?)
The only possible fix I can find is the edit to platform.xml. I've contacted the developer; notice how it says "Attempt to patch my ROM"? Well the developer told me that when the patch is applied and when I reboot, the patch is erased because of the reboot(he said that seems to be the case) so I need to find a way to ensure that it isn't erased. I'm having the same problem here; when I make an edit, it's erased either immediately or after reboot. So that's why I need to find a way to fix this. Thanks, if you have a possible fix.
I've tried using DirectoryBind, but it doesn't work and I hear it's been broken since 4.2. I don't know how to revert back to a previous Android version for my device, so I'm stuck.
Jason1712 said:
Yes, of course access is granted. I have only tried to create one link so far...so it can't be anything to do with the number of links permitted in FolderMount. I mean, I haven't been able to create a single working link. Precisely, the error I'm getting in FolderMount has something to do with sd card r/w permissions(I've linked a screenshot;maybe you've had this problem before and you solved it?)
The only possible fix I can find is the edit to platform.xml. I've contacted the developer; notice how it says "Attempt to patch my ROM"? Well the developer told me that when the patch is applied and when I reboot, the patch is erased because of the reboot(he said that seems to be the case) so I need to find a way to ensure that it isn't erased. I'm having the same problem here; when I make an edit, it's erased either immediately or after reboot. So that's why I need to find a way to fix this. Thanks, if you have a possible fix.
I've tried using DirectoryBind, but it doesn't work and I hear it's been broken since 4.2. I don't know how to revert back to a previous Android version for my device, so I'm stuck.
Click to expand...
Click to collapse
Some files e.g. related to kernel will be generated on every boot. In that case you can't change em permanently. BUT you can try another solution so far Create a ext2/ext4 partition on your external sd and use Link2SD or APP2SD pro
In the superSU setting, try enabling option allow apps requesting root permission at start up(on boot).
Sent from my G610-U00 using xda app-developers app
LS.xD said:
Some files e.g. related to kernel will be generated on every boot. In that case you can't change em permanently. BUT you can try another solution so far Create a ext2/ext4 partition on your external sd and use Link2SD or APP2SD pro
Click to expand...
Click to collapse
Um..how do I do that?
Jason1712 said:
Um..how do I do that?
Click to expand...
Click to collapse
Do you have a custom recovery installed?
LS.xD said:
Do you have a custom recovery installed?
Click to expand...
Click to collapse
Yes.Philz-Touch Modified, Advanced CWM Recovery. At least, that's whats stated in the Desire 601 root guide.
Jason1712 said:
Yes.Philz-Touch Modified, Advanced CWM Recovery. At least, that's whats stated in the Desire 601 root guide.
Click to expand...
Click to collapse
This recovery has a built-i feature to parttition sd-card. Pls keep in mind that all data on sd will be deleted during the process. i look out for a guide.
Your recovery / Rom (Kernel) has to support this feature. I can't find this information. So pls be patient. I'll pm you as soon as i found a safe solution.
LS.xD said:
This recovery has a built-i feature to parttition sd-card. Pls keep in mind that all data on sd will be deleted during the process. i look out for a guide.
Click to expand...
Click to collapse
So I just have to do that? Just boot into recovery, then use the partition sd-card feature in my recovery, and then that's it? My sd card will be partitioned? Ok, then I download..Link2SD?
LS.xD said:
This recovery has a built-i feature to parttition sd-card. Pls keep in mind that all data on sd will be deleted during the process. i look out for a guide.
Your recovery / Rom (Kernel) has to support this feature. I can't find this information. So pls be patient. I'll pm you as soon as i found a safe solution.
Click to expand...
Click to collapse
Oh sorry, I didn't see this post before I posted my reply. OK, thanks a lot.

[Rom][Pre-Rooted][7.0][G920v] Offical nougat pre rooted rom

most of members the old method didn't work with him so i decide to make a pre rooted rom
*Do It AT YOUR OWN RISK!* I am not responsible for ANY damage to your device
Here is the video in how to install it all link that you will need it i put it in description of the video
please don't forget to hit thanks it takes 5 days from me to upload it
[YOUTUBE]
https://www.youtube.com/watch?v=NS0Ggcq0TfU[/YOUTUBE]
also you can open the video from here
https://www.youtube.com/watch?v=q8OT36kfo24
Tears of Joy . Woks Perfect.. Thank you @faw_wal
DDwhite said:
Tears of Joy . Woks Perfect.. Thank you @faw_wal
Click to expand...
Click to collapse
You Welcome
Many thanks faw_wal
I could place it in writing. the steps to follow
I do not know which file I should download first.
Additional I would like to know if you could share a script or a way to remove verizon apps, and keep a clean phone as if it were a total samsung
Thanks for this faw_wal
zpeady said:
Many thanks faw_wal
Click to expand...
Click to collapse
Enjoy
jotademanuel said:
I could place it in writing. the steps to follow
I do not know which file I should download first.
Additional I would like to know if you could share a script or a way to remove verizon apps, and keep a clean phone as if it were a total samsung
Click to expand...
Click to collapse
I'm sorry but it's a lot of steps to write it follow the video if video show to you black screen tonight i'm gonna to fix this problem
no-go
Tried many times, unable to get past the mounting of /system. Hard lock-up.
Edit: Had root on 7.0 finally. Looked like I was using the wrong sboot. I have too many...
Note: Tried to update superSU after I had everything how I wanted it. Lost root. Had to start over. Use caution...
I have gotten my phone rooted thanks for your help.
Now we need to find a way to bypass the system rw,remount freeze, which I think is being controlled by smu_protection or something like that.
EvilRubberDuck said:
Thanks for this faw_wal
Click to expand...
Click to collapse
You Welcome
AndroidFan16 said:
I have gotten my phone rooted thanks for your help.
Now we need to find a way to bypass the system rw,remount freeze, which I think is being controlled by smu_protection or something like that.
Click to expand...
Click to collapse
I think you phone now is rooted and you can mount system as rw just start adb
write adb shell then write su it will ask to get root from your device and then retry if doesn't work with download any explorer app like root explorer and you can edit system from it
lyphe said:
Tried many times, unable to get past the mounting of /system. Hard lock-up.
Click to expand...
Click to collapse
did you get root in super su ?
It works for the mount /system via adb? because I did it from root explorer but it freezes again, if works via adb, tell me, Im now in the 5.1.1 android rom version
does not work video ((
faw_wal said:
You Welcome
I think you phone now is rooted and you can mount system as rw just start adb
write adb shell then write su it will ask to get root from your device and then retry if doesn't work with download any explorer app like root explorer and you can edit system from it
Click to expand...
Click to collapse
Tried it on both, including
Code:
mount -o rw,remount /system
Freezing up
Especially with Amaze. Tried to write on the system partition and it hangs until I do a fresh reboot.
Has anyone tried if Samsung pay still works after root?
Ok, I'm in this nougat rom now, but the writable system still as a dream for us. I'll go back to the stock and enjoy of my Samsung apps instead of freezing my phone. Has someone knowledge about change the imei of this device? I want root for this. Or, if you know how to reboot the lollipop rooted rom correctly, can you explain me how?
Sent from my SM-G920V using XDA-Developers Legacy app
faw_wal said:
did you get root in super su ?
Click to expand...
Click to collapse
Edited original post. Finally got it working, but then lost it trying to update superSU binary.
ok i will corporate with @AndroidFan16 to figure what is the problem and when solve it i will publish it here
aceisaneight said:
Has anyone tried if Samsung pay still works after root?
Click to expand...
Click to collapse
Unsure if it "works" or not, as I never use it. However... It is bothering me to add my VISA-XXXX to Android Pay after boot. I'd say fairly good chance it does, simply because this root has thus far not touched /system for most of us. I do believe that is the red flag for SafetyNet/Pay (but I dunno. It does ask me however...)

Mounting /vendor as R/W on latest OOS

Hi.
I bought an OP6 2 days ago and I'm trying to get the NFC tag emulator app to work with my campus door card. Apparently this app requires write access to /vendor partition but that's read-only by default.
I tried to mount it using adb which resulted in "adbd cannot run as root in production builds" and in Root Browser which did absolutely nothing.
Is it even possible to mount that as RW on stock ROM? If yes, then how?
Any advice is really appreciated.
Screenshot from the app https://i.imgur.com/8WzEiTz.jpg
Thanks.
same question too ,do u find the solution ?

Magisk and /Systempartition rw???

Hey, thank you!
Yes, I really have some very important questions for someone who knows their stuff!
So: I have an almost unknown smartphone, a Beafon X5. With Android 7.0.
A great device, just for one.. "Modder" like me, a bit problematic, because absolutely no custom software can be found for it...
But now I've managed to trying Rootaccess For the device.. With your Awesome app, Mtk Easy root and magisk.
My questions :
# can I somehow change the /system/ directory to rwx 7777 for me? Because now it doesn't work, just because of the systemless root. (at least I think) The chown/chmod commands Not working.
It will be" read-only file system" every time printed. I just want to replace the boot animation.
# Question 2:
Why can I only use after every reboot, mtk-Easy-root again from new, to activate magisk?? Why didnt work magisk, Although the SU is insatlled? Only if the mtk script has been run before, I can use the superuser in the magisk Manager Serve.
Have you an idea for this Problem?
Thank you, and best wishes from germany!
by Felix
Rootbbit said:
Hey, thank you!
Yes, I really have some very important questions for someone who knows their stuff!
So: I have an almost unknown smartphone, a Beafon X5. With Android 7.0.
A great device, just for one.. "Modder" like me, a bit problematic, because absolutely no custom software can be found for it...
But now I've managed to trying Rootaccess For the device.. With your Awesome app, Mtk Easy root and magisk.
My questions :
# can I somehow change the /system/ directory to rwx 7777 for me? Because now it doesn't work, just because of the systemless root. (at least I think) The chown/chmod commands Not working.
It will be" read-only file system" every time printed. I just want to replace the boot animation.
# Question 2:
Why can I only use after every reboot, mtk-Easy-root again from new, to activate magisk?? Why didnt work magisk, Although the SU is insatlled? Only if the mtk script has been run before, I can use the superuser in the magisk Manager Serve.
Have you an idea for this Problem?
Thank you, and best wishes from germany!
by Felix
Click to expand...
Click to collapse
For question 1:
Android as a system (linux-like) mounts the system partition as ro (Read-only) by default when booting. In order to be able to modify it, you need to remount the desired partition as rw (read-write) as follows:
While being a root user (#) enter this command in adb or terminal on your phone:
Code:
mount -o rw,remount /system
To revert back to ro (you should do it after you're done), use:
Code:
mount -o ro,remount /system
For question 2:
That app is based on Mtk-su exploit. You can read an article from xda here. Basically, your device's bootloader stays locked, but root resets every reboot, because the attained privileges are only temporary. (su gets to run from /data/local/tmp).
Remember!!! You Bootloader is still locked, meaning AVB and dm-verity are still active. If you modify system (changing the total checksum), you will brick your device!!! And if you unlock the Bootloader, then what's the point of Mtk-su ..........
Hope I helped you somehow.
Schlank K:
Thank you, but I'm not a complete noobThank you, but I'm not a complete noob Thanks, really. But I tried these methods ed for a long time...
The same thing still happens, I mounted, there is no contradiction, but then nothing actually happened either...
Individual blocks can be mounted in the main directory, but not specifically the system/block. I actually only planned to do this stupid boot animation from the system/media folder. Delete/replace/rename/move zip, whatever, to finally get rid of the thing for my own ani...
And there it started. I've already spent several hours on the net to find a way. There are many options, but none have worked for me so far..
Looks like dm-verity is in effect. Disable it and then mount should work.
xXx yYy said:
Looks like dm-verity is in effect. Disable it and then mount should work.
Click to expand...
Click to collapse
Hey, thanks
I've already tried that. Detects my system Not.
AVB ( dm-verity ) is bootloader related. You typically use Fastboot to disable it.
Rootbbit said:
Hey, thanks
I've already tried that. Detects my system Not.
Click to expand...
Click to collapse
Rootbbit said:
Hey, thanks
I've already tried that. Detects my system Not.
Click to expand...
Click to collapse
In addition
xXx yYy said:
AVB ( dm-verity ) is bootloader related. You typically use Fastboot to disable it.
Click to expand...
Click to collapse
I've already tried that. My fastboot gets the same message. I have already tried the system block mounting, via dev/blocks/ but there I also get the read-only message.
Or mounting via busybox, I've already done everything.
I've googled a lot about it, and found nothing else that helps , otherwise I wouldn't have asked here on xda.
There are these read-only ROMs, how do I recognize them? Is ext4 not also read-only from manufacturer from
Thanks, guys
is your bootloader unlocked!?
you know disable-verity is adb applet, don't you?
you have been warned don't do this on locked bootloader. happy bricking..
btw there is such thing like magisk modules no need to modify system partition at all. just read the Magisk Developer Guides Module Tricks section

Categories

Resources