Related
Probably I missed this question being answered somewhere, but I am tired of searching for it, so here it goes...
I decided not to root my device for now, and I am trying to get the most of it with stock limitations. Generally it is fine, but what bothers me most is the fact that i seem to be unable to write any files on phones internal memory. Is it so, that all / filesystem is inaccessible for write, or is there a dir where i could store some files i would like my phone to be able to access while sdcard is unmounted?
I may be wrong but thats the limitations of a "stock" phone,if you want access to the files you would have to root AFAI
That's exactly the impression I have, and I don't like the idea. I'm ex WM5/WM6 user, and I simply cannot understand why can't I have let's say /tmp/ dir just for myself...
banannq said:
That's exactly the impression I have, and I don't like the idea. I'm ex WM5/WM6 user, and I simply cannot understand why can't I have let's say /tmp/ dir just for myself...
Click to expand...
Click to collapse
Any reason for not rooting then? there are plenty stock roms/alternatives out there.
I grown tired of constantly tweaking my previous htc smartphone, decided to keep this one stock at least for now. I know rooting is an open door I will not want to close
and also I think there's no rooting method for gingerbread so far, is there?
As much as I know a downgrade is involved,I know what you mean about tinkering with the phone!It gets obsessive at times
You should have access to /data/local or at the very least /data/local/tmp
That's where fiels get pushed for rooting.
-Nipqer
The problem is I cannot even open /data directory
How are you trying to access the /data folder?
Cause if its some file manager app, some of them will only read sdcard.
-Nipqer
I'm used fre3vo to get temproot on my device (Z, Android 2.3.3),
and after that called:
mount -o remount,rw -t ext3 /dev/block/mmcblk0p25 /system
i can write to /system, but after reboot or remount into readonly all my changes dissapearing. Should i need S-OFF on my device? Can i get S-OFF without rollback to v1.34 on temp rooted 2.42?
Yeah the emmc is write protected when you are s-on, so any changes to /system will dissappear on reboot.
Unfortunately you cannot get s-off without downgrading to 1.34.
-Nipqer
Nipqer said:
How are you trying to access the /data folder?
Cause if its some file manager app, some of them will only read sdcard.
-Nipqer
Click to expand...
Click to collapse
Normaly I use total commander for android, but tried also ES File explorer, Linda manager, andexplorer... all of them basicaly let me view / folders (with exception of /data, /root, /cache etc) so i think it is filesystem condition rather than file manager fault...
banannq said:
Normaly I use total commander for android, but tried also ES File explorer, Linda manager, andexplorer... all of them basicaly let me view / folders (with exception of /data, /root, /cache etc) so i think it is filesystem condition rather than file manager fault...
Click to expand...
Click to collapse
try root explorer. you can still view directories without root (the app will just tell you that it failed to request superuser access). I'm pretty sure everything under /data is r/w access by default. My phone is rooted so I can't verify whether or not you can write to that directory on stock (I'd assume you could as long as there's free space available) but I can definitely recall being able to look at all my directories on stock using root explorer.
sephiroth1439 said:
try root explorer. you can still view directories without root (the app will just tell you that it failed to request superuser access). I'm pretty sure everything under /data is r/w access by default. My phone is rooted so I can't verify whether or not you can write to that directory on stock (I'd assume you could as long as there's free space available) but I can definitely recall being able to look at all my directories on stock using root explorer.
Click to expand...
Click to collapse
I guess it doesn't matter what software i use android simply locks me out of internal phone memory. It sucks, because phone was advertised as having over 1GB of internal storage space (no mention about it being inaccessible), and i can't even store ringtones on my device (have to use sdcard, and suffer side effect of it being unmounted at times). What a shame... with all the greatness, android sucks at very simple things
banannq said:
I guess it doesn't matter what software i use android simply locks me out of internal phone memory. It sucks, because phone was advertised as having over 1GB of internal storage space (no mention about it being inaccessible), and i can't even store ringtones on my device (have to use sdcard, and suffer side effect of it being unmounted at times). What a shame... with all the greatness, android sucks at very simple things
Click to expand...
Click to collapse
Don't blame Android for your carrier locking down your device
Sent from my HTC Vision using XDA App
Hi
I recently restored my Nexus with the toolkit but when it put the files back, I think a permissions problem has occurred. I can rename folders, but I can't delete them. I have a rather large folder that I can't get rid of. When I try in various programs, it says delete failed, or no permissions, etc.
I am rooted, and have installed Terminal emulator, but am not terribly familiar with how to use it.
Any tips would be helpful.
Thanks
warlock257 said:
Hi
I recently restored my Nexus with the toolkit but when it put the files back, I think a permissions problem has occurred. I can rename folders, but I can't delete them. I have a rather large folder that I can't get rid of. When I try in various programs, it says delete failed, or no permissions, etc.
I am rooted, and have installed Terminal emulator, but am not terribly familiar with how to use it.
Any tips would be helpful.
Thanks
Click to expand...
Click to collapse
Simple solution might just be that your file explorer app doesn't have root access. Force stop it in apps->settings, check your superuser app and clear any saved entries for it, and launch the app again. It should request root privileges.
Where are the files/folders in question located? If they're in a secure place like /system/ then it's more likely to be the above scenario. If they're just in your sdcard folder, are they user made, or at all special?
Edit: Also in the future, this sort of thing is what the Q&A forum is for.
JoeSyr said:
Simple solution might just be that your file explorer app doesn't have root access. Force stop it in apps->settings, check your superuser app and clear any saved entries for it, and launch the app again. It should request root privileges.
Where are the files/folders in question located? If they're in a secure place like /system/ then it's more likely to be the above scenario. If they're just in your sdcard folder, are they user made, or at all special?
Edit: Also in the future, this sort of thing is what the Q&A forum is for.
Click to expand...
Click to collapse
I was using Root explorer, and have granted it root access
It is in /SDcard, so it shouldn't be anything that's protected
warlock257 said:
I was using Root explorer, and have granted it root access
It is in /SDcard, so it shouldn't be anything that's protected
Click to expand...
Click to collapse
Did you check the permissions for what you're trying to delete? They're displayed right in the normal view in root explorer, and you can edit them from the long press menu.
Anything unusual about the files/folders themselves? Were they created on the phone? By you? By apps? Copied and pasted over USB from a computer? You could try deleting from your computer over USB.
As for command line options, you can try 'rm -r [path]' for a folder and just 'rm [path]' for a file. rm is the delete(remove) command, -r is the recursive flag to apply the action to all items in the directory if a directory is the target. Pretty sure that you can do that straight from terminal emulator on your phone, and from a command prompt over usb you'd need to use 'adb shell' first.
JoeSyr said:
Did you check the permissions for what you're trying to delete? They're displayed right in the normal view in root explorer, and you can edit them from the long press menu.
Anything unusual about the files/folders themselves? Were they created on the phone? By you? By apps? Copied and pasted over USB from a computer? You could try deleting from your computer over USB.
As for command line options, you can try 'rm -r [path]' for a folder and just 'rm [path]' for a file. rm is the delete(remove) command, -r is the recursive flag to apply the action to all items in the directory if a directory is the target. Pretty sure that you can do that straight from terminal emulator on your phone, and from a command prompt over usb you'd need to use 'adb shell' first.
Click to expand...
Click to collapse
In root explorer the info under the folder says
rwxrwxr -x
I'm pretty sure that the problem started when I restored from the nexus toolkit on pc. I had a similar problem with my camera in that it couldn't save pictures to a folder, but all I did was rename the folder, and the camera app created a new one.
rm -r [path] in terminal emulator says "permission denied"
EDIT
upon further googleing, the 'chmod' command might be what I want, but I'm not sure which syntax is right.
warlock257 said:
In root explorer the info under the folder says
rwxrwxr -x
I'm pretty sure that the problem started when I restored from the nexus toolkit on pc. I had a similar problem with my camera in that it couldn't save pictures to a folder, but all I did was rename the folder, and the camera app created a new one.
rm -r [path] in terminal emulator says "permission denied"
EDIT
upon further googleing, the 'chmod' command might be what I want, but I'm not sure which syntax is right.
Click to expand...
Click to collapse
For chmod you want 'chmod [number] [path]', where number is a string that's a bit complicated to explain. You can learn about it by googling chmod probably better than I could type it out here on the fly. But if you use 777, it should assign full permissions, which would display as rwxrwxrwx in root explorer.
You can achieve the exact same effect in root explorer though, long press and choose permissions and you'll get a 3x3 grid. All boxes checked= full permissions, same as chmod 777. The three lower boxes for special permissions should be unchecked (fyi, they would turn chmod's numeric component into a 4 digit number, and as far as I know, android doesn't really use them at all).
Also, did you type su in terminal first? It doesn't innately have root (just like any app) so you need to do that and confirm the popup first. You'll need to do this before using chmod, and if you didn't do it before using rm, try it again.
Worth a try but just for reference, rwxrwxr-x is the normal permissions set for folders on the sdcard, so that's not immediately looking like a problem.
at the top of root explorer, theres a button that says mount r/w. press it, now it should say mount r/o. go ahead and delete that file now
simms22 said:
at the top of root explorer, theres a button that says mount r/w. press it, now it should say mount r/o. go ahead and delete that file now
Click to expand...
Click to collapse
Found the button, but didn't work
JoeSyr said:
For chmod you want 'chmod [number] [path]', where number is a string that's a bit complicated to explain. You can learn about it by googling chmod probably better than I could type it out here on the fly. But if you use 777, it should assign full permissions, which would display as rwxrwxrwx in root explorer.
You can achieve the exact same effect in root explorer though, long press and choose permissions and you'll get a 3x3 grid. All boxes checked= full permissions, same as chmod 777. The three lower boxes for special permissions should be unchecked (fyi, they would turn chmod's numeric component into a 4 digit number, and as far as I know, android doesn't really use them at all).
Also, did you type su in terminal first? It doesn't innately have root (just like any app) so you need to do that and confirm the popup first. You'll need to do this before using chmod, and if you didn't do it before using rm, try it again.
Worth a try but just for reference, rwxrwxr-x is the normal permissions set for folders on the sdcard, so that's not immediately looking like a problem.
Click to expand...
Click to collapse
it might be the files within the folder, rather than the folder itself. going into it, some of the files have a shield on them
When I go into its permissions, some of them were unchecked. I checked the 9 at the top, and it says:
"permissions change was not successful. Please note that some files systems (e.g. SD card) do now allow permission changes."
warlock257 said:
Found the button, but didn't work
it might be the files within the folder, rather than the folder itself. going into it, some of the files have a shield on them
When I go into its permissions, some of them were unchecked. I checked the 9 at the top, and it says:
"permissions change was not successful. Please note that some files systems (e.g. SD card) do now allow permission changes."
Click to expand...
Click to collapse
Well under normal circumstances, individual files on your sdcard should have permissions rw-rw-r--, and folders have rwxrwxr-x. (For reference, this is read as read, write, execute for Root, System, and Other, with dashes indicating that a permission is denied. So rwxrwxr-x means all permissions are granted to all three groups except for write to Other). This ties into larger aspects of the OS that basically exist to stop individual apps from reading or writing whatever they want without being included in groups.
The fact that you can't do something that shouldn't require elevated permissions, and you're getting that kind of error when you try to execute commands with higher permissions, suggests to me that your sdcard partition is using the wrong filesystem. Sort of sounds like a program tried to treat it like a real sdcard and formatted it to something else, in which case I have a hunch you're going to need to back up your data and do a full reset.
You might get a simpler solution if you ask in the thread for the toolkit you used. It's not something I have any experience with so good luck.
Out of curiosity, are you on Jellybean now? Jellybean changed the address for the sdcard partition, so if the toolkit wasn't updated to reflect this, it seems like the likely place things may have gone wrong.
---------- Post added at 07:04 PM ---------- Previous post was at 06:53 PM ----------
Actually if you want to check if it's using the right filesystem, run the command 'mount' from terminal. It'll give you a bunch of information, probably towards the bottom will be a line that mentions sdcard. Mine reads as
/dev/fuse /storage/sdcard0 fuse [more info about how it's currently mounted]
Yours -should- say that if you're on JB. If you're not, it should say something instead of /storage/sdcard0 (maybe /mnt/sdcard? I forget how it was on ICS). If it says something in place of fuse that may be the problem.
..I actually think mount used to say that the sdcard block was formatted as yaffs2, while everything else was formatted as ext4. Or maybe I just looked up that it was yaffs2 online, not from terminal on my phone? I wonder if this whole thing is the reason why some people seem bootloop-prone when flashing JB roms, if the changes have cut out access to important information about the filesystem, it may be triggering a really long error scan if their sdcard partition is large.
yes, backed up in ICS, and went to Jellybean.
doing a 'mount', I believe the line reads
/dev/fuse /storage/sdcard0 fuse rw,nosuid,nodev,realtime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
The files that have the shield icon have permissions:
rw-rw-r--
Yeah so everything that I can think of for you to check seems to be displaying as though normal. Although I don't know what aspect of these files root explorer is reading to mark them as protected and put the little shield on them.
You've tried these methods (rm, chmod) on individual files within the folder too, right? I guess this comes more from experience deleting protected files in windows, but I've found that sometimes a folder will deny deletion as long as it contains protected files, but it's relatively easy to give yourself permission to delete the individual files one by one, after which the folder goes down too. Possibly time consuming without a batch function, but easy.
My understanding of the fuse filesystem, by the way, is that it's just a virtual layer that allows the sdcard block to be treated differently than everything else on the phone, which is important for what happens when you plug it into a computer and the device is read. And I believe that the sdcard is supposed to be formatted as yaffs2 (everything else is ext4). Not sure how to check that directly, but it's possible that it has been changed to something else. But unless you can't delete -anything- on the sdcard, this seems unlikely.
JoeSyr said:
Yeah so everything that I can think of for you to check seems to be displaying as though normal. Although I don't know what aspect of these files root explorer is reading to mark them as protected and put the little shield on them.
You've tried these methods (rm, chmod) on individual files within the folder too, right? I guess this comes more from experience deleting protected files in windows, but I've found that sometimes a folder will deny deletion as long as it contains protected files, but it's relatively easy to give yourself permission to delete the individual files one by one, after which the folder goes down too. Possibly time consuming without a batch function, but easy.
My understanding of the fuse filesystem, by the way, is that it's just a virtual layer that allows the sdcard block to be treated differently than everything else on the phone, which is important for what happens when you plug it into a computer and the device is read. And I believe that the sdcard is supposed to be formatted as yaffs2 (everything else is ext4). Not sure how to check that directly, but it's possible that it has been changed to something else. But unless you can't delete -anything- on the sdcard, this seems unlikely.
Click to expand...
Click to collapse
yeah, I tried deleting files individually on the phone, and in windows. Wont let me do anything.
I guess the only sure fire method of clearing these files at the moment is to do a factory reset.
I can back up my stuff with titanium, so not that big a deal.
Your assistance has been much appreciated
:good:
warlock257 said:
yeah, I tried deleting files individually on the phone, and in windows. Wont let me do anything.
I guess the only sure fire method of clearing these files at the moment is to do a factory reset.
I can back up my stuff with titanium, so not that big a deal.
Your assistance has been much appreciated
:good:
Click to expand...
Click to collapse
Try deleting them directly from /data/media instead. If you're able to delete them there, reboot afterwards to ensure /storage/sdcard0, /sdcard, and /mnt/sdcard are updated properly.
Sent from my Galaxy Nexus
Cilraaz said:
Try deleting them directly from /data/media instead. If you're able to delete them there, reboot afterwards to ensure /storage/sdcard0, /sdcard, and /mnt/sdcard are updated properly.
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
That worked :laugh:
It's gone from all those folders.
Thanks very much!!!!!
warlock257 said:
That worked :laugh:
It's gone from all those folders.
Thanks very much!!!!!
Click to expand...
Click to collapse
+1 This worked for me as well. Thanks for posting...:good:
Had the same problem. Deleting through the /media path worked.
Cilraaz said:
Try deleting them directly from /data/media instead. If you're able to delete them there, reboot afterwards to ensure /storage/sdcard0, /sdcard, and /mnt/sdcard are updated properly.
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
+4 You Sir are a genius! Thanks given!
Cilraaz said:
Try deleting them directly from /data/media instead. If you're able to delete them there, reboot afterwards to ensure /storage/sdcard0, /sdcard, and /mnt/sdcard are updated properly.
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
Sorry to necro this thread almost 4 years later, but I had the exact same issue with deleting a folder on internal storage (Android Lollipop). Regardless if you're still here on XDA or not: thanks for this solution.
So.. Not really a I9250, but I guess my problem on i9100 is the same.
For some weird reason this just happened to WhatsApp directory.. But whatever.
After digging deeper and deeper in recovery, it seems like the folder wasn't own by media_rw group, but root
I just had to run
Code:
chown -R 1023:1023 <folder-path>
For some weird reason neither chown nor ls -l were correctly working when booted on normal system
Cilraaz said:
Try deleting them directly from /data/media instead. If you're able to delete them there, reboot afterwards to ensure /storage/sdcard0, /sdcard, and /mnt/sdcard are updated properly.
Click to expand...
Click to collapse
@Cilraaz, I have no idea if you're still on XDA but after at least a week of intense searching I found your advice which solved my problem! Thank you.
My problem was on i9500 (still) running stock Lollipop. I've been preparing to install a custom recovery, and did a TWRP (2.8.7.0) nandroid backup. Problem was I then couldn't find the TWRP backup folder. It would only show in TWRP's file manager. Root Browser didn't show it with SU privileges, nor ES File Browser and connecting it to the PC didn't help either. It's only after looking in /data/media/0 that I could find the TWRP folder.
Hey guys, I recently updated my Moto Z Play, retin version to Oreo...Rooted it via magisk and installed xposed.. So far everything seems good and the battery has also improved a lot.. The only thing that bugs me right now is that i am unable to modify /system files... I was trying to change my bootanimation.zip file...Used RootExplorer, FX Explorer, Root Browser but to no avail..All of them were denied RW permission... Tried booting into TWRP and mounting system as RW, moved the bootanimation.zip to system/media and as soon as i rebooted my device, the change was reverted... It seems any change we make to /system is reverted back due to verification at boot... Is there a way to enable RW access so that i can modify /system files... Thanks
mhp1995 said:
Hey guys, I recently updated my Moto Z Play, retin version to Oreo...Rooted it via magisk and installed xposed.. So far everything seems good and the battery has also improved a lot.. The only thing that bugs me right now is that i am unable to modify /system files... I was trying to change my bootanimation.zip file...Used RootExplorer, FX Explorer, Root Browser but to no avail..All of them were denied RW permission... Tried booting into TWRP and mounting system as RW, moved the bootanimation.zip to system/media and as soon as i rebooted my device, the change was reverted... It seems any change we make to /system is reverted back due to verification at boot... Is there a way to enable RW access so that i can modify /system files... Thanks
Click to expand...
Click to collapse
Try looking for a system_root folder that Magisk creates and see if you can change it there.
Milly7 said:
Try looking for a system_root folder that Magisk creates and see if you can change it there.
Click to expand...
Click to collapse
Nope, there is no such folder in my phone... Is it just me without RW /system access or is it with every oreo devices? How do you guys access and modify /system files on oreo?
Idea of Magisk is not to modify system. Please read documentation and questions other peoples asked.
tag68 said:
Idea of Magisk is not to modify system. Please read documentation and questions other peoples asked.
Click to expand...
Click to collapse
I know but on 7.1(nougat) with magisk and xposed installed, I was able to modify system files.. I used to do all kind of build prop edits & other stuff but on oreo I am facing issues with installation of busybox as well as modifying system files...
My problem is the opposite: it is way too easy to mount system rw. One click ona button in TC, and I won't be able to do OTA without flashing system again.
So, I don't want to find out if system is mounting rw on my mobile. These modifications you want to do are better to do in Magisk way. If you do a system update, you keep your Magisk settings, so modifications will stay. OTA will only require uninstall of Magisk. Why do you want to do them the hard, incompatible way?
tag68 said:
My problem is the opposite: it is way too easy to mount system rw. One click ona button in TC, and I won't be able to do OTA without flashing system again.
So, I don't want to find out if system is mounting rw on my mobile. These modifications you want to do are better to do in Magisk way. If you do a system update, you keep your Magisk settings, so modifications will stay. OTA will only require uninstall of Magisk. Why do you want to do them the hard, incompatible way?
Click to expand...
Click to collapse
+1
<deleted>
On some device you can do this function in recovery.....
TWRP can do these changes when you disable the "mount system as RO" in mount settings. But you'll have to flash a zip that removes dm-verity too, otherwise it won't boot up. Magisk will most likely fail to change the bootanimation on many devices because it can't replace it soon enough.
Hello There. I rooted with magisk today. Evrrything worked fine until I tried to change something in /system folder.
I have read in the internet that u wont have access to system folder if you are on root with magisk. It says u need to modify the .mirror folder. In this ./system/media I try to change the bootanimation. zip, but I cant change or delete the stock one. I think I do not have root acess in this folder. But I can use apps like Greenify without problems. Have I done something wrong? I gave different file exporer full root access I am using:
Mi10t Lite
MIUI 12.0.8 (GLOBAL)
Android 10
Gauguin
Magisk Version is the newest: 21.4
Magisk Manager: 8.0.7
I think i found the answer...:
System partition locked to read only in Android 10
Help, I don't know what I did but after installing a custom ROM, I noticed that my system partition cannot be mounted as read/write. I tried "mount -o rw,remount /system" command on a terminal
android.stackexchange.com
Create a Magisk module to modify files in /system partition.
_mysiak_ said:
Create a Magisk module to modify files in /system partition.
Click to expand...
Click to collapse
How do I do that?
Francescohub said:
How do I do that?
Click to expand...
Click to collapse
Either create your own module from scratch following the Magisk guide, or adapt one of the existing ones.
You're trying the mount -o rw,remount as root (means: you did a "su" before the "mount")?
Maybe a "blockdev --setrw /dev/block/dm-X" helps (see which dm- is mounted as system for the X).
Greetz
Kurt
hello
also i tried to modify mixer_paths_cdp.xml in / vendor / etc, but i am not able to get myself a magisk module
You can use for example this very simple Magisk module as a template.
Create desired folder structure in the zip file, add your xml files for modification, remove the AOD overlay apk/folder and try to flash it.
Keep TWRP at hand if you mess up something so you can delete the module from recovery if necessary.
I stumbled upon this solution for RW system partition in Android 10+. Someone brave enough might give it a try. https://forum.xda-developers.com/t/script-mount-system-as-read-write-android-10.4240703/
_mysiak_ said:
I stumbled upon this solution for RW system partition in Android 10+. Someone brave enough might give it a try. https://forum.xda-developers.com/t/script-mount-system-as-read-write-android-10.4240703/
Click to expand...
Click to collapse
i can't download it
carabot said:
i can't download it
Click to expand...
Click to collapse
Works for me.. Anyway, you should provide your feedback/complaints to the author.
download ok
I hope not to do any damage
Hello! I just rooted my Rog 6 with Magisk to be able to edit my build.prop file. Unfortunately it seems to be read only. If I could get the filesystem mounted in TWRP it should be no problem. But since there is no TWRP yet i'm stuck. I did a lot of research but cannot come up with the solution. Anybody here can help?
Thanks in front!
Well you must be in os12 same issue with me but in different device
senna33 said:
Hello! I just rooted my Rog 6 to be able to edit my build.prop file. Unfortunately it seems to be read only. If I could get the filesystem mounted in TWRP it should be no problem. But since there is no TWRP yet i'm stuck. I did a lot of research but cannot come up with the solution. Anybody here can help?
Thanks in front!
Click to expand...
Click to collapse
did you use a file explorer that supports root and try to change the permission on the file?
I'm on Android 12 and used Root Explorer. The permissions cannot be changed because it's not mounted as writable. The buildprop editor app also cannot save. Thanks for your replies!
senna33 said:
I'm on Android 12 and used Root Explorer. The permissions cannot be changed because it's not mounted as writable. The buildprop editor app also cannot save. Thanks for your replies!
Click to expand...
Click to collapse
i don't understand how a device is rooted if you can't modifie system files
nadejo said:
i don't understand how a device is rooted if you can't modifie system files
Click to expand...
Click to collapse
That's kinda how I feel about it. Root Checker Pro says I have root, I can run Su in a terminal and I get a popup asking for superuser rights when I use a function that requires root. I attached some screenshots from Root Checker Pro
The problem is that the partitions (system vendor and co) are only integrated as R/O and cannot be easily integrated as R/W
I thought the whole point of root was to be able to do such things . If i would edit the build.prop file in system.img then flash that in recovery mode, would that work?
no the partitions ( system vendor ) have a write protection (I would not be surprised if the asus rog with android 12 uses the file formart efros ) this had to be converted to ext4 so that you can mount the partitions with rw)
senna33 said:
I thought the whole point of root was to be able to do such things . If i would edit the build.prop file in system.img then flash that in recovery mode, would that work?
Click to expand...
Click to collapse
ChrisFeiveel84 said:
no the partitions ( system vendor ) have a write protection (I would not be surprised if the asus rog with android 12 uses the file formart efros ) this had to be converted to ext4 so that you can mount the partitions with rw)
Click to expand...
Click to collapse
I converted still same
Mr Hassan said:
I converted still same
Click to expand...
Click to collapse
then it didn't work.
because if the partitions are converted correctly and the write protection is removed then you should be able to change files in e.g
(I also tried it on my oneplus 9p without success, but even after the alleged conversion, the partitions were still EROFS)
ChrisFeiveel84 said:
then it didn't work.
because if the partitions are converted correctly and the write protection is removed then you should be able to change files in e.g
(I also tried it on my oneplus 9p without success, but even after the alleged conversion, the partitions were still EROFS)
Click to expand...
Click to collapse
Yes i converted successfully
Not maked whole super
Just maked vendor system product
And did u believe with one command
Its even get press RW in root explorer
But still not in whole partitons so not able to modify anything
But Most important thing
I get fully rw in dev block mapper
Even i copy paste files there with change permissions
So i believe i doing mistake somewhere
Otherwise little bit achievement
Not yet but hope if i get some dev knowledge then can fix it fully
If the partitions are not converted from erofs to ext4, it remains with ro because erofs cannot be mounted as rw
Mr Hassan said:
Yes i converted successfully
Not maked whole super
Just maked vendor system product
And did u believe with one command
Its even get press RW in root explorer
But still not in whole partitons so not able to modify anything
But Most important thing
I get fully rw in dev block mapper
Even i copy paste files there with change permissions
So i believe i doing mistake somewhere
Otherwise little bit achievement
Not yet but hope if i get some dev knowledge then can fix it fully
Click to expand...
Click to collapse
how did you try to convert the images to ext 4 without write protection?
ChrisFeiveel84 said:
how did you try to convert the images to ext 4 without write protection?
Click to expand...
Click to collapse
There's thread available on xda but as i told useless
What u think as i said upper if device
Dev block mapper have full root
But not possible to edit system vend or anything
ChrisFeiveel84 said:
how did you try to convert the images to ext 4 without write protection?
Click to expand...
Click to collapse
see this
OnePlus8:/ # mount | grep "dm-0"
/dev/block/dm-0 on / type ext4 (rw,seclabel,relatime)
OnePlus8:/ # mount | grep "dm-19"
/dev/block/dm-19 on / type ext4 (rw,seclabel,relatime)
OnePlus8:/ # mount | grep "dm-3"
and still i,m not able to edit these parts
can you change something in the images (which you changed, which you then flashed to your cell phone) if you copy them to your pc? if not, then the images still have write protection
ChrisFeiveel84 said:
can you change something in the images (which you changed, which you then flashed to your cell phone) if you copy them to your pc? if not, then the images still have write protection
Click to expand...
Click to collapse
Men see upper logs its converted to ext4
just because it means that you have successfully converted to ext4 does not mean that the write protection is out.... that's why I asked if you can edit files in the ext4 images on the pc, because if that doesn't work, the images still have one write protection (even ext4 can have a write protection )
as examples on the 7t, the images are in ext4 but still have write protection so that you cannot change anything in the images. even if they are integrated as rw because the system.img or vendor.img that is in the super partition is write-protected
ChrisFeiveel84 said:
just because it means that you have successfully converted to ext4 does not mean that the write protection is out.... that's why I asked if you can edit files in the ext4 images on the pc, because if that doesn't work, the images still have one write protection (even ext4 can have a write protection )
as examples on the 7t, the images are in ext4 but still have write protection so that you cannot change anything in the images. even if they are integrated as rw because the system.img or vendor.img that is in the super partition is write-protected
Click to expand...
Click to collapse
But in os10 os11 is possible
But don't know how to fix this os12
Is there anyway to remove write protection?