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?
Related
This guide is based on a guide by Candanga on the i9000 forums, and some commands from supercurio
Please hit thanks on their posts and show them some love for the write up.
-----------------------------------------------------------------------------------------------------------------------
I’ve compiled a quick guide to instruct how to make a copy of the /efs folder. I’ve found in many threads suggestions about backing up this folder but the methods itself are very general. Most of the times they suggest to “root and copy the folder” with Root Explorer or similar, but usually it’s not that easy or it just doesn't work for everyone.
This guide ASUMES you have read this Excellent Guide by Darkstrikerfirst:
H E R E <-- Make sure to read the ADB Guide.
I recommend doing this with a Mobile just taken out of the box or with any Official ROM of its Service Provider. If you have already Flashed your phone with another ROM but its working fine, then you can use that /efs also.
Why the /efs folder?
This is a very sensitive system folder that contains Phone-specific information such as the IMEI (encrypted in the nv_data.bin), wireless devices MAC addresses, product code (also in the nv_data.bin), and much more. Often users trying to change product codes or trying to unlock the mobile will end up corrupting data in this location.
Why back it up?
Well, let’s resume it saying that backing-up this little folder will keep you away from Samsung service centres.
***WARNING: I take no responsibility to any damage caused by the methods cited and/or written here. Their sole purpose is to back-up data and not to alter in any way the integrity of the original files of the mobile***
What you will need:
Rooted SGS II to get permissions as a SU (Super User) and perform the backup
I would suggest learning a little about the terminal commands used (in case you are not familiar with them), as it’s better to know what you are doing rather than typing strings like a little chimp without knowing what they are; if you are a little lazy, then you have a good chance bricking your mobile. <- Busybox Commands(or Google them)
Terminal Emulator by Jack Palevich (available from the market) <-Terminal Emulator or use ADB which is included in the SDK Development Tools
The standard prompt of terminal (adb) is a $ sign. Once you enter “SU” it will become a # Sign.
***NOTE: Make sure to keep an eye on the screen of your SGS II during this process, because it may request SU permissions [currently doesn't on CF-root]; else, you will get an error (just if it’s the first time). In Terminal Emulator you will need to reset the app after granting permissions cause it usually freezes***
*Remember: to use ADB you need to enable USB DEBUGGING under Applications/Development in your SGS II.
Here are 3 methods, I recommend that you do both Clean and RAW.
Basic, unix permissions lost :
Code:
su
busybox cp -a /efs /sdcard/efs/
Clean :
Code:
su
busybox tar zcvf /sdcard/efs/efs-backup.tar.gz /efs
After this, you will end up with the file efs-backup.tar.gz in your INTERNAL SDCARD in sdcard/efs/, which is a “tarball” or a ZIP of the /efs folder. That file is your backup. You can expand it with Winrar.
You can also back up the mmcblk0p1 (where /efs is stored) under /dev/block which can greatly support in recovering your IMEI in case of a screw-up:
RAW :
Code:
su
cat /dev/block/mmcblk0p1 > /sdcard/efs/efs_dev-block-mmcblk0p1.img
Same thing, the target is the INTERNAL SDCARD in sdcard/efs/, so go ahead and copy the file.
+1 just do it....
Can this not be tasked by using a root file explorer and copying efs folder as i have always done .
jje
JJEgan said:
Can this not be tasked by using a root file explorer and copying efs folder as i have always done .
jje
Click to expand...
Click to collapse
From the thread:
I’ve found in many threads suggestions about backing up this folder but the methods itself are very general. Most of the times they suggest to “root and copy the folder” with Root Explorer or similar, but usually it’s not that easy or it just doesn't work for everyone.
Click to expand...
Click to collapse
And just copying the folder won't preserve permissions etc.
JJEgan said:
Can this not be tasked by using a root file explorer and copying efs folder as i have always done .
jje
Click to expand...
Click to collapse
As long as you don't copy it to /sdcard, because it's VFAT and you'll lose the permissions settings on the files. If you copy it to /data or something then that's fine.
bumpity bump
RyanZA said:
As long as you don't copy it to /sdcard, because it's VFAT and you'll lose the permissions settings on the files. If you copy it to /data or something then that's fine.
Click to expand...
Click to collapse
Thanks the SGS 1 EFs i copied was copied to external sd card and then copied off to PC . Did likewise on SGS 2 using Super Manager .
So according to what you are saying that was not going to back up if needed .
jje
JJEgan said:
Thanks the SGS 1 EFs i copied was copied to external sd card and then copied off to PC . Did likewise on SGS 2 using Super Manager .
So according to what you are saying that was not going to back up if needed .
jje
Click to expand...
Click to collapse
It would probably have worked, but it would have made your EFS files readable and writable by any app that tried - not the end of the world since it's unlikely that any apps would try, but you still might as well avoid it if you can. I don't think there are any executables in EFS or anything that this will actually break though.
Thanks i did lose IMEI at one flash on SGS1 but a second flash recovered it .
I do like full backup of original firmware and anything else before playing with phone .
jje
I've done all 3 forms of backup myself. . Clean, raw and basic
thanks for the info. have had close calls previously and having backups would have helped ease the stress
Updated first post
Vodafone Fimrware backup BUKE1
Guys,
Have got a new samsung from Vodafone UK , but the firmware kernel seems a bit different, BUKE1. Is this something now and is the above method correct to backup the entire firmware so that it might be useful for vodafone samsung users. Is there an easy guide to backup the firmware ?
Regards
VJ
Guys can someone give me a bit of advice pleeeease
I followed this guide but am a bit worried i might have messed it up, i'm comfortable with command prompt as i'm a software dev but haven't used linux commands much.
Anyway i used the ADB shell from the Android SDK tools and entered the first command to backup the efs directory to the internal sdcard....
Basic, unix permissions lost :
Code:
su
busybox cp -a /efs /sdcard/efs/
Click to expand...
Click to collapse
And i got a lot of
Code:
cp: can't preserve ownership of 'sdcard/efs/...' : Operation not permitted
messages flashing up?
However i checked to see if the backup had been made and it had? What does this mean?
Next i compressed it using...
Clean :
Code:
su
busybox tar zcvf /sdcard/efs/efs-backup.tar.gz /efs
Click to expand...
Click to collapse
Which seemed to work as i have the file in the place i expect
When i did the next step...
You can also back up the mmcblk0p1 (where /efs is stored) under /dev/block which can support greatly to recover your IMEI in case of a screw-up:
RAW :
Code:
su
cat /dev/block/mmcblk0p1 > /sdcard/efs_dev-block-mmcblk0p1.img
Same thing, the target is the INTERNAL SDCARD in sdcard/efs/, so go ahead and copy the file.
Click to expand...
Click to collapse
It completed really quickly, with no messages telling me it was done but when i checked root explorer i couldn't find /dev/block/mmcblk0p1?
What has it done with it? I have dev/block/ but there is no mmcblk0p1? Although i do have /sdcard/efs_dev-block-mmcblk0p1.img. Should i have both?
From what i understand cat concatenates files and prints them to standard output, so i'm assuming the > is piping the std output to the internal sdcard?
Sorry for the questions but i thought i understood what i was doing but the last step and the "can't preserve ownership of.." messages from the first step threw me
Could someone explain this to me a little ;p
These aren't steps but rather separate methods achieving different things. Don't bother about the first one - it notes unix permissions lost , which is why you are seeing the can't preserve ownership messages. The files still backup but correct r/w permissions do not. You may as well chuck the files really, since you managed the tarball (second instruction). Just grab this and backup to external storage, in case you ever need it.
The raw backup will be under sdcard as you have found - stash this away somewhere safe too. You won't find mmcblk0p1 in root explorer as it is a partition, not a folder.
Thanks for the swift reply simion_levi
These aren't steps but rather separate methods achieving different things. Don't bother about the first one - it notes unix permissions lost , which is why you are seeing the can't preserve ownership messages. The files still backup but correct r/w permissions do not. You may as well chuck the files really, since you managed the tarball (second instruction). Just grab this and backup to external storage, in case you ever need it.
Click to expand...
Click to collapse
Do if i move the tarball to the external drive i can get rid of the sdcard/efs directory i copied to the internal card? The tarball has all the correct permissions?
The raw backup will be under sdcard as you have found - stash this away somewhere safe too. You won't find mmcblk0p1 in root explorer as it is a partition, not a folder.
Click to expand...
Click to collapse
Ok i didn't realise it was a partition, so i've just created an image of the partition that the efs folder resides on? Should i copy this to my external sd card as well?
Cheers brother
No problem! Yes, you've got it - backup the tarball and the partition image to computers, external drives etc so you can recover back to the phone in case of future catastrophe. The sdcard/efs directory can be deleted as the tarball contains exactly the same files (but with correct permissions).
Awesome, will get it done later. Out of interest how do you recover the partition image in the event of a disaster occurring?
Sent from my GT-I9100 using XDA App
One question please, since i stumbled on this one almost by luck.
Is there anything else to save before departing from stock?
Thanks.
Okay, so this guide assumes I already rooted my phone, but as a newbie I am completely in the dark about what does and what does not potentially harm the /efs. I would rather backup EVERYTHING before I flash/change anything, but from what I have read so far I need at least root to do backups.
Would it be safe to flash the Lite'ning Rom v1.1, coming from stock I9100XWKE2/I9100XENKE1/I9100XXKDJ/I9100XWKE2, and then backup mmcblk0p1?
Thanks!
Hi all!
I have bought the new Huawei P6S Dual Sim (China Unicom version).
It's multilanguage and has Android 4.2.2
I rooted it successfully (bootloader is already unlocked) but I can't change files on the system directory (I need to replace the apns_conf.XML). There is a security lock? What's happen?
Thanks in advance at all
try root browser from the playstore. This automatically sets the right permissions for files and folders Hope this helps!
Sent from my P6-U00 using Tapatalk
lootjelo said:
try root browser from the playstore. This automatically sets the right permissions for files and folders Hope this helps!
Sent from my P6-U00 using Tapatalk
Click to expand...
Click to collapse
Thanks ,
I tried it, but unsuccessfully.
It seems there is a protection (by Huawei) on the system folders. I can change files in other folders (with R/W mounting) but not in the \system folder
NolanBart said:
Thanks ,
I tried it, but unsuccessfully.
It seems there is a protection (by Huawei) on the system folders. I can change files in other folders (with R/W mounting) but not in the \system folder
Click to expand...
Click to collapse
Hi
This phone is the most heavily secured phone I have ever seen. The /system partition has at least three protection methods
1) mounted as read-only
2) some files have the "immutable" bit set on the ext4 file system. #chattr -i file will remove the immutable bit
3) since KK firmware Huawei applied a new security mechanism by which the kernel seems to discard any modification done to /system even when it's remounted as RW. With this mechanism any change is rolled-back by the time /system is remounted as RW even after a reboot.
From the shell command line I have found a way to solve the first two but I still have no clue of how to solve the third one. Does anybody have any clue on how to solve it?
abequer said:
Hi
This phone is the most heavily secured phone I have ever seen. The /system partition has at least three protection methods
1) mounted as read-only
2) some files have the "immutable" bit set on the ext4 file system. #chattr -i file will remove the immutable bit
3) since KK firmware Huawei applied a new security mechanism by which the kernel seems to discard any modification done to /system even when it's remounted as RW. With this mechanism any change is rolled-back by the time /system is remounted as RW even after a reboot.
From the shell command line I have found a way to solve the first two but I still have no clue of how to solve the third one. Does anybody have any clue on how to solve it?
Click to expand...
Click to collapse
Have you found a solution for problem 3??
rs06085 said:
Have you found a solution for problem 3??
Click to expand...
Click to collapse
No I haven't. Regretfully my P6S broke last week and I'm no longer able to keep this development
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 everyone,
I would like to modify some files in root/vendor/etc but i can't because of permission. I'm root, I can access file with solid explorer but can't modify anything. I try to modify attributes of the folder but it gives me a error.
Is there a bypass for the scoped storage of android 11?
Thx !
You can use ADB root to modify it by using terminal commands. Not ideal but a possibility
Robert314 said:
You can use ADB root to modify it by using terminal commands. Not ideal but a possibility
Click to expand...
Click to collapse
I would like to change the name of a file inside etc in vendor folder, do you know how I could do it ? Or could you point me a guide ? I'm not sure how to search a solution for this case
Robert314 said:
You can use ADB root to modify it by using terminal commands. Not ideal but a possibility
Click to expand...
Click to collapse
Apparently I can't run ADB root, I got "adbd cannot run as root in production builds", well I will dig further to find a solution
Greenspoof said:
I would like to change the name of a file inside etc in vendor folder, do you know how I could do it ? Or could you point me a guide ? I'm not sure how to search a solution for this case
Click to expand...
Click to collapse
Root Browser Classic - Apps on Google Play
Fully customizable Root Browser for Android users and rooted superusers
play.google.com
Try this file manager. Its a good root file manager and as it's old I might bypass scoped storage
which rom? right now i use arrow and it is the only one that can mount system as R/W.maybe there are others but a have not trid all of them.MIUI does not support it due to dynamic partitions,
hexisg said:
which rom? right now i use arrow and it is the only one that can mount system as R/W.maybe there are others but a have not trid all of them.MIUI does not support it due to dynamic partitions,
Click to expand...
Click to collapse
It's indeed the stock one. As debloated, I find it the best
Robert314 said:
Root Browser Classic - Apps on Google Play
Fully customizable Root Browser for Android users and rooted superusers
play.google.com
Try this file manager. Its a good root file manager and as it's old I might bypass scoped storage
Click to expand...
Click to collapse
I tried but didn't work, scoped storage is really awful, but thx anyway!