Read Only File System after Rooting - Redmi Note 9 Questions & Answers

When I rooted my device , Redmi Note 9 MIUI 12.5.2 , It gave me all root privileges except an error of " Read-Only File System " .
I can change some system files, but some files Can't be changed or deleted or edited anyway.
I wanted to change the Boot Animation, so I took a zip file and deleted the boot animation.zip from system/media , but as soon as I delete , somehow it magically gets restored. I am not able to overwrite that file.
I tried to install magisk but it shows read only file system . I did also try mount -o remount commands , but Nothing works.
Please help me in this situation!!

You cant mount system as read-write.

Try this:
[Closed] Universal SystemRW / SuperRW feat. MakeRW / ro2rw (read-only-2-read/write super partition converter)
Welcome to the one and only, the original, universal, System-RW / Super-RW feat. Make-RW / ro2rw (read-only-2-read/write super partition converter) by lebigmac Also known as: THE-REAL-RW, FULL-RW, EXT4-RW, EROFS-RW, EROFS-2-RW, F2FS-RW...
forum.xda-developers.com

VD171 said:
You cant mount system as read-write.
Click to expand...
Click to collapse
Could you please tell me how to do it. I've tried " mount -o remount,rw / " but even after doing so, I wasn't able to install magisk

vulcanY said:
Could you please tell me how to do it. I've tried " mount -o remount,rw / " but even after doing so, I wasn't able to install magisk
Click to expand...
Click to collapse
I said you can NOT mount system as read-write.

VD171 said:
I said you can NOT mount system as read-write.
Click to expand...
Click to collapse
Sir, I did flash the script specified by you , but still nothing works

vulcanY said:
Sir, I did flash the script specified by you , but still nothing works
Click to expand...
Click to collapse
Are you sure?
Just post your question in the thread and @lebigmac soon will reply you.
He will love your feedback

VD171 said:
You cant mount system as read-write.
Click to expand...
Click to collapse
VD171 said:
Try this:
[Closed] Universal SystemRW / SuperRW feat. MakeRW / ro2rw (read-only-2-read/write super partition converter)
Welcome to the one and only, the original, universal, System-RW / Super-RW feat. Make-RW / ro2rw (read-only-2-read/write super partition converter) by lebigmac Also known as: THE-REAL-RW, FULL-RW, EXT4-RW, EROFS-RW, EROFS-2-RW, F2FS-RW...
forum.xda-developers.com
Click to expand...
Click to collapse
VD171 said:
I said you can NOT mount system as read-write.
Click to expand...
Click to collapse
VD171 said:
Are you sure?
Just post your question in the thread and @lebigmac soon will reply you.
He will love your feedback
Click to expand...
Click to collapse
Hi @VD171 @vulcanY
What do you mean system cannot be mounted as rw on your Redmi Note 9 ? Does it have shared_blocks read-only feature? You can check like this
Bash:
adb shell
su
tune2fs -l /dev/block/dm-0
What about the other partitions? /vendor , /product, /system_ext, /odm? Same problem? I know /odm can sometimes cause trouble...
If you're lucky next version (which is coming very soon) might do the trick but I can't 100% guarantee it yet

lebigmac said:
Hi @VD171 what do you mean system cannot be mounted as rw on your Redmi Note 9 ? Does it have shared_blocks read-only feature? You can check like this
Bash:
adb shell
su
tune2fs -l /dev/block/dm-0
What about the other partitions? /vendor , /product, /system_ext, /odm? Same problem? I know /odm can sometimes cause trouble...
If you're lucky next version (which is coming very soon) might do the trick but I can't 100% guarantee it yet
Click to expand...
Click to collapse
This is the Output of that command

Well it looks like my script successfully removed the shared_blocks read-only feature from your device
Unfortunately you still have read-only error for some reason. There must be additional protection features enabled on your device. To find out more info about your specific read-only error you can run dmesg immediately after remounting your partition as rw like this:
Bash:
adb shell
su
mount -o remount,rw /
dmesg > /sdcard/dmesg_output.txt

Again After remount it shows Read Only Error and here is the dmesg_output.txt

vulcanY said:
Again After remount it shows Read Only Error and here is the dmesg_output.txt
Click to expand...
Click to collapse
Your dmesg looks really long.
Try to reboot the device, mount as read-write and then save dmesg output again.

Even after reboot, the size is same

Related

Question : "magisk hide unable to watch hidelist" any way to fix?

i use oneplus 3 with OxygenOs 3.5.5 when i use the rom (stock) and install magisk and enable magisk hide it hides root and safetynet succeed and it unmounts
But when i start from the beginning on the stock rom and install RR on the rom (customrom) and full unroot and reinstall magisk and enable magisk hide and reboot i get this in the log and it doesn't unmount :
HTML:
MagiskHide: starting MagiskHide Daemon
MagiskHide: Unable to watch /magisk/.core/magiskhide/hidelist
any help please to get it to unmount and hide root ?
to know after i installed RR and full unrooted safetynet passed
ahmedsasker said:
i use oneplus 3 with OxygenOs 3.5.5 when i use the rom (stock) and install magisk and enable magisk hide it hides root and safetynet succeed and it unmounts
But when i start from the beginning on the stock rom and install RR on the rom (customrom) and full unroot and reinstall magisk and enable magisk hide and reboot i get this in the log and it doesn't unmount :
HTML:
MagiskHide: starting MagiskHide Daemon
MagiskHide: Unable to watch /magisk/.core/magiskhide/hidelist
any help please to get it to unmount and hide root ?
to know after i installed RR and full unrooted safetynet passed
Click to expand...
Click to collapse
Run the following commands in a terminal emulator:
Code:
su
cd /magisk/.core/magiskhide
sh disable
sh enable
You're probably gonna get an output that the hidelist can't be created because of a permissions issue. That probably means the Magisk image doesn't get mounted properly at boot.
Another user (@gunner007dc) that had this issue fixed it by using a different kernel.
Didgeridoohan said:
Run the following commands in a terminal emulator:
Code:
su
cd /magisk/.core/magiskhide
sh disable
sh enable
You're probably gonna get an output that the hidelist can't be created because of a permissions issue. That probably means the Magisk image doesn't get mounted properly at boot.
Another user (@gunner007dc) that had this issue fixed it by using a different kernel.
Click to expand...
Click to collapse
that is what i get and safetynet doesn't pass still ..
Code:
[email protected]:/magisk/.core/magiskhide # sh disable
MagiskHide: Stopping MagiskHide daemon
disable[27]: can't open /magisk/.core/magiskhide/hidelist: No such file or directory
1|[email protected]:/magisk/.core/magiskhide # sh enable
MagiskHide: Removing dangerous read-only system props
touch: '/magisk/.core/magiskhide/hidelist': Read-only file system
chmod: chmod '/magisk/.core/magiskhide' to 40755: Read-only file system
chmod: chmod 'rm' to 100755: Read-only file system
chmod: chmod 'list' to 100755: Read-only file system
chmod: chmod 'enable' to 100755: Read-only file system
chmod: chmod 'disable' to 100755: Read-only file system
chmod: chmod 'add' to 100755: Read-only file system
grep: /magisk/.core/magiskhide/hidelist: Bad file descriptor/magisk/.core/magiskhide/add[14]: [: 0: unexpected operator/operand
enable[65]: can't open /magisk/.core/magiskhide/hidelist: No such file or directory
MagiskHide: Starting MagiskHide daemon
to know without the magisk and have root removed with the custom rom the safetynet passes so what is wrong ?
if magisk doesn't get mounted properly how could i fix that ?
i tried to install another karnel whick support systemless root and i got bootloop maybe cuz of the custom rom RR so i can't install another karnel while the one i tried the only one i saw that support systemless root
please anyway to make magisk work ? (i tried the two versions under 12.0 too)
ahmedsasker said:
that is what i get and safetynet doesn't pass still ..
Code:
[email protected]:/magisk/.core/magiskhide # sh disable
MagiskHide: Stopping MagiskHide daemon
disable[27]: can't open /magisk/.core/magiskhide/hidelist: No such file or directory
1|[email protected]:/magisk/.core/magiskhide # sh enable
MagiskHide: Removing dangerous read-only system props
touch: '/magisk/.core/magiskhide/hidelist': Read-only file system
chmod: chmod '/magisk/.core/magiskhide' to 40755: Read-only file system
chmod: chmod 'rm' to 100755: Read-only file system
chmod: chmod 'list' to 100755: Read-only file system
chmod: chmod 'enable' to 100755: Read-only file system
chmod: chmod 'disable' to 100755: Read-only file system
chmod: chmod 'add' to 100755: Read-only file system
grep: /magisk/.core/magiskhide/hidelist: Bad file descriptor/magisk/.core/magiskhide/add[14]: [: 0: unexpected operator/operand
enable[65]: can't open /magisk/.core/magiskhide/hidelist: No such file or directory
MagiskHide: Starting MagiskHide daemon
to know without the magisk and have root removed with the custom rom the safetynet passes so what is wrong ?
if magisk doesn't get mounted properly how could i fix that ?
i tried to install another karnel whick support systemless root and i got bootloop maybe cuz of the custom rom RR so i can't install another karnel while the one i tried the only one i saw that support systemless root
please anyway to make magisk work ? (i tried the two versions under 12.0 too)
Click to expand...
Click to collapse
Looks like what for a strange reason /magisk is mounted as read-only. Try mount as rw:
Code:
mount -w -o remount /magisk
Deic said:
Looks like what for a strange reason /magisk is mounted as read-only. Try mount as rw:
Code:
mount -w -o remount /magisk
Click to expand...
Click to collapse
Code:
[email protected]:/ $ su
[email protected]:/ # mount -w -o remount /magisk
[email protected]:/ # cd /magisk/.core/magiskhide
[email protected]:/magisk/.core/magiskhide # she disable
sh: she: not found
127|[email protected]:/magisk/.core/magiskhide # sh disable
MagiskHide: Stopping MagiskHide daemon
disable[27]: can't open /magisk/.core/magiskhide/hidelist: No such file or directory
1|[email protected]:/magisk/.core/magiskhide # sh enable
MagiskHide: Removing dangerous read-only system props
touch: '/magisk/.core/magiskhide/hidelist': Read-only file system
chmod: chmod '/magisk/.core/magiskhide' to 40755: Read-only file system
chmod: chmod 'rm' to 100755: Read-only file system
chmod: chmod 'list' to 100755: Read-only file system
chmod: chmod 'enable' to 100755: Read-only file system
chmod: chmod 'disable' to 100755: Read-only file system
chmod: chmod 'add' to 100755: Read-only file system
grep: /magisk/.core/magiskhide/hidelist: Bad file descriptor/magisk/.core/magiskhide/add[14]: [: 0: unexpected operator/operand
enable[65]: can't open /magisk/.core/magiskhide/hidelist: No such file or directory
MagiskHide: Starting MagiskHide daemon
[email protected]:/magisk/.core/magiskhide #
I still get the same result ...
ahmedsasker said:
I still get the same result ...
Click to expand...
Click to collapse
If you type just:
Code:
su
mount
and look for a line that starts something like:
Code:
/dev/block/loop0 on /magisk
In the parenthesis at the end of the line, the text should start with "rw". Does it?
Didgeridoohan said:
If you type just:
Code:
su
mount
and look for a line that starts something like:
Code:
/dev/block/loop0 on /magisk
In the parenthesis at the end of the line, the text should start with "rw". Does it?
Click to expand...
Click to collapse
No it it does start with ro
Code:
/dev/block/loop0 on /magisk type ext4 (ro,seclabel,noatime,data=ordered)
ahmedsasker said:
No it it does start with ro
Code:
/dev/block/loop0 on /magisk type ext4 (ro,seclabel,noatime,data=ordered)
Click to expand...
Click to collapse
Ok. Next, try:
Code:
mount -o remount,rw /magisk
If that doesn't work, try:
Code:
mount -o remount,rw -t ext4 /dev/block/loop0 /magisk
Didgeridoohan said:
Ok. Next, try:
Code:
mount -o remount,rw /magisk
If that doesn't work, try:
Code:
mount -o remount,rw -t ext4 /dev/block/loop0 /magisk
Click to expand...
Click to collapse
I tried both and it keeps telling me that it is read-only
Code:
[email protected]:/ $ su
[email protected]:/ # mount -o remount,rw /magisk
'/dev/block/loop0' is read-only
ount -o remount,rw -t ext4 /dev/block/loop0 /magisk <
'/dev/block/loop0' is read-only
ahmedsasker said:
I tried both and it keeps telling me that it is read-only
Code:
[email protected]:/ $ su
[email protected]:/ # mount -o remount,rw /magisk
'/dev/block/loop0' is read-only
ount -o remount,rw -t ext4 /dev/block/loop0 /magisk <
'/dev/block/loop0' is read-only
Click to expand...
Click to collapse
Hm... I have no idea...
From your earlier posts I assume you've already uninstalled and reinstalled Magisk a few times, right? Have you tried an unofficial beta snapshot (both Magisk and the Manager)?
I still say you should try a different kernel. I don't know what you mean with "supports systemless root", but I'd try flashing a kernel like Elemental over the one that comes with RR and then install Magisk. Maybe even try installing and running Kernel Auditor, like it says in the link I posted earlier.
Didgeridoohan said:
Hm... I have no idea...
From your earlier posts I assume you've already uninstalled and reinstalled Magisk a few times, right? Have you tried an unofficial beta snapshot (both Magisk and the Manager)?
I still say you should try a different kernel. I don't know what you mean with "supports systemless root", but I'd try flashing a kernel like Elemental over the one that comes with RR and then install Magisk. Maybe even try installing and running Kernel Auditor, like it says in the link I posted earlier.
Click to expand...
Click to collapse
I meant that it was written that it supports systemless root in the XDA forums plus I tried to flash elementalx karnel and went into boot loop ...
I'll try the snapshot one now and thanks alot <3
ahmedsasker said:
I meant that it was written that it supports systemless root in the XDA forums plus I tried to flash elementalx karnel and went into boot loop ... How can I uninstall the elementalx karnel to try another one without reflashing the whole rom ?
I'll try the snapshot one now and thanks alot <3
Click to expand...
Click to collapse
Dirty flash the ROM or open up the ROM zip, extract the boot.img and flash that in TWRP.
Didgeridoohan said:
Dirty flash the ROM or open up the ROM zip, extract the boot.img and flash that in TWRP.
Click to expand...
Click to collapse
OMG thanks alot it works well now and passes with the snapshot version <3
thanks again x3
Didgeridoohan said:
Dirty flash the ROM or open up the ROM zip, extract the boot.img and flash that in TWRP.
Click to expand...
Click to collapse
please do you know compatible version of systemless xposed with snapshot magisk ! cuz latest v87 after I flash it, closed installer says that there's not framework installed but normal official one works
systemless xposed v87 was working fine on magisk v12
i installed the official one now and it is working very well
what is the difference between systemless xposed and the normal one ? (cuz both got caught by safety net)
ahmedsasker said:
please do you know compatible version of systemless xposed with snapshot magisk ! cuz latest v87 after I flash it, closed installer says that there's not framework installed but normal official one works
systemless xposed v87 was working fine on magisk v12
i installed the official one now and it is working very well
what is the difference between systemless xposed and the normal one ? (cuz both got caught by safety net)
Click to expand...
Click to collapse
It's very likely the Xposed Magisk module needs to be updated to work with v13... I don't use Xposed though, so I wouldn't know.
The difference between system and systemless xposed is that one is installed into system and the other one is systemless. :laugh: Seriously... That's the difference. They'll both trigger SafetyNet. Systemlessness is not about passing SafetyNet.
Didgeridoohan said:
Run the following commands in a terminal emulator:
Code:
su
cd /magisk/.core/magiskhide
sh disable
sh enable
You're probably gonna get an output that the hidelist can't be created because of a permissions issue. That probably means the Magisk image doesn't get mounted properly at boot.
Another user (@gunner007dc) that had this issue fixed it by using a different kernel.
Click to expand...
Click to collapse
In my device, no file in /magisk/...why?:crying::crying:
Hooxp17 said:
In my device, no file in /magisk/...why?:crying::crying:
Click to expand...
Click to collapse
No idea. I can't see your device and I can't read your mind... Meaning: you've given very few details.
I'm gonna make a guess though: are you taking about the ".core" folder? It's a hidden folder, so if your file explorer isn't set to see hidden files and folders you won't see it.
If this is not your issue, give more details.
Didgeridoohan said:
Dirty flash the ROM or open up the ROM zip, extract the boot.img and flash that in TWRP.
Click to expand...
Click to collapse
Which ROM? How to Dirty Flash? I have G5 Plus
brandonsisco said:
Which ROM? How to Dirty Flash? I have G5 Plus
Click to expand...
Click to collapse
Uhm... That was a specific advice for a specific issue...
What's your issue?
Didgeridoohan said:
Run the following commands in a terminal emulator:
Code:
su
cd /magisk/.core/magiskhide
sh disable
sh enable
You're probably gonna get an output that the hidelist can't be created because of a permissions issue. That probably means the Magisk image doesn't get mounted properly at boot.
Another user (@gunner007dc) that had this issue fixed it by using a different kernel.
Click to expand...
Click to collapse
hello, i have a problem with magisk, so i found your post. but in the terminal emulator can't see this file.. can you help me?

Help with Magisk module

Hi,
It's nice you do not have to mod .prop files with Magisk module's system.prop .
But how do you mod .xml files ?
I'm struggling here...
Here is the bash I'd like to run, but it will need RW rights on /cust and /product
Code:
cp /cust/hw/eu/xml/hw_defaults.xml /cust/hw/eu/xml/hw_defaults.xml.BACKUP && cp /product/etc/xml/hw_launcher_default_config.xml /product/etc/xml/hw_launcher_default_config.xml.BACKUP && sed -ie 's/<integer settings.global.hw_4g_show="0" reset="true"/<integer settings.global.hw_4g_show="1" reset="true"/g; s/<string app_name_two_lines="false"/<string app_name_two_lines="true"/g; s/<string hw_add_4g_only="250"/<string hw_add_4g_only="208"/g; s/<string hw_data_roam_option="26006,27211"/<string hw_data_roam_option="ALL"/g' /cust/hw/eu/xml/hw_defaults.xml && sed -ie 's/<item name="config_desktopCellsOptionItems" reset="true">4x5,4x4,5x4,5x5</<item name="config_desktopCellsOptionItems" reset="true">4x6,4x5,4x4,5x4,5x5,5x6</g; s/<item name="config_IconTitleSize">12</<item name="config_IconTitleSize">9</g' /product/etc/xml/hw_launcher_default_config.xml
Any idea where to put this code into my magisk module ?
How should I'll be able to replace, via terminal cmds, files on /product & /cust (oreo huawei device)
oslo83 said:
Hi,
It's nice you do not have to mod .prop files with Magisk module's system.prop .
But how do you mod .xml files ?
I'm struggling here...
Here is the bash I'd like to run, but it will need RW rights on /cust and /product
Code:
cp /cust/hw/eu/xml/hw_defaults.xml /cust/hw/eu/xml/hw_defaults.xml.BACKUP && cp /product/etc/xml/hw_launcher_default_config.xml /product/etc/xml/hw_launcher_default_config.xml.BACKUP && sed -ie 's/<integer settings.global.hw_4g_show="0" reset="true"/<integer settings.global.hw_4g_show="1" reset="true"/g; s/<string app_name_two_lines="false"/<string app_name_two_lines="true"/g; s/<string hw_add_4g_only="250"/<string hw_add_4g_only="208"/g; s/<string hw_data_roam_option="26006,27211"/<string hw_data_roam_option="ALL"/g' /cust/hw/eu/xml/hw_defaults.xml && sed -ie 's/<item name="config_desktopCellsOptionItems" reset="true">4x5,4x4,5x4,5x5</<item name="config_desktopCellsOptionItems" reset="true">4x6,4x5,4x4,5x4,5x5,5x6</g; s/<item name="config_IconTitleSize">12</<item name="config_IconTitleSize">9</g' /product/etc/xml/hw_launcher_default_config.xml
Any idea where to put this code into my magisk module ?
How should I'll be able to replace, via terminal cmds, files on /product & /cust (oreo huawei device)
Click to expand...
Click to collapse
Hello,
If you are already aware that these modifications will be in the actual filesystems and not masked by Magisk, you can put that code into config.sh as a function and call that from update-binary.
Regards.
Thanks
JayminSuthar said:
If you are already aware that these modifications will be in the actual filesystems and not masked by Magisk
Click to expand...
Click to collapse
I am aware it will mod the actual files but i'm not sure how with magiskmodule I could mod some files AND THEN straighly use them to mask the originals.
JayminSuthar said:
, you can put that code into config.sh as a function and call that from update-binary.
Click to expand...
Click to collapse
You kind of lost me
I previously tried with post-fs-data.sh but i think my problem is i can't mod these file but i can make temporary copies somewhere (need to find where) then erase originals and then move temporary copies where originals where.
Instead of just should use something like:
Code:
sed -e 's/. /. /g' originalfile > /tmp/file.bak
rm originalfile
mv /tmp/file.bak originalfile
If I understand you correctly, /cust and /product are directly in the root of your device, not in /system? In that case you can't use Magisk to Magic Mount the files. That can only be done to /system or /vendor.
You should be able to edit the files in place though, you'll just have to mount the partitions as rw (and then back to ro when you're done). Something like this (but check the command syntax first, I don't know it fully from memory):
Code:
mount -o rw,remount /cust
<Do your thing here>
mount -o ro,remount /cust
Didgeridoohan said:
If I understand you correctly, /cust and /product are directly in the root of your device, not in /system? In that case you can't use Magisk to Magic Mount the files. That can only be done to /system or /vendor.
You should be able to edit the files in place though, you'll just have to mount the partitions as rw (and then back to ro when you're done). Something like this (but check the command syntax first, I don't know it fully from memory):
Code:
mount -o rw,remount /cust
<Do your thing here>
mount -o ro,remount /cust
Click to expand...
Click to collapse
You caught it up, I forgot about the rootfs being ro
I'll try and report.
It worked, thank you very much.
Now I'm facing some problem to make a module submission...
Code:
Bad Request:*https://github.com/oslo83/EMUI_Tap2wake*is not a valid Magisk Module!
Reason:*module.prop*does not exist on*masterbranch
....

Question Failed to mount /system_root (Block device required) read-only rw remount failed

Hello
Since a couple of days I am trying to get access to the read-only root directory on my phone to change and add some files there, without any success.
I've tried several things like:
@lebigmac SystemRW / SuperRW Script
Remounting via many different root file managers
Adb commands
Tried it on Evo X, riceDroid, MIUI A11+12, TWRP & OrangeFox Recovery
Formatting data, change file system
...
Is there a way to make it writeable or at least add a file to /apex/com.android.runtime/etc/ ?
I have heard people create a magisk module for that purpose, is that necessary?
Mi 11 Venus, Magisk 25.2, Evolution X 6.7 ROM
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Hello @bongmeiister. Thanks for your interest in my SystemRW/SuperRW feat. MakeRW by lebigmac project I have to specify the author name because sadly my program (or parts thereof) were stolen on multiple occasions by multiple ruthless intellectual property thieves that are also members in this very forum and then I was deleted from my own program (don't you just hate it when that happens?) and my code was republished by these thugs as if they created my program from scratch. Like WTF right?! (not allowed to write any names or you can get banned)
Anyways.
Why my script didn't work on your device? If you send me the log from your phone /data/local/tmp/systemrw_1.32/log then I can take a look at your results.
If you check your mount output you can see lots of different /apex mounts.
Bash:
adb shell
su
mount | grep /apex
I noticed that on my Xiaomi Poco X3 NFC device (which I used to develop my SystemRW/SuperRW feat. MakeRW script) I can remount all subpartitions as RW just fine but for some reason I cannot remount apex as rw?!
Bash:
mount -o remount,rw /apex/com.android.runtime
mount: '/dev/block/loop22'->'/apex/com.android.runtime': Invalid argument
Here is the root of your problem:
Bash:
/dev/block/loop22 on /apex/com.android.runtime type ext4 (ro,dirsync,seclabel,nodev,noatime)
As you can see it is mounted read-only.
lebigmac said:
Hello @bongmeiister. Thanks for your interest in my SystemRW/SuperRW feat. MakeRW by lebigmac project I have to specify the author name because sadly my program (or parts thereof) were stolen on multiple occasions by multiple ruthless intellectual property thieves that are also members in this very forum and then I was deleted from my own program (don't you just hate it when that happens?) and my code was republished by these thugs as if they created my program from scratch. Like WTF right?! (not allowed to write any names or you can get banned)
Anyways.
Why my script didn't work on your device? If you send me the log from your phone /data/local/tmp/systemrw_1.32/log then I can take a look at your results.
If you check your mount output you can see lots of different /apex mounts.
Bash:
adb shell
su
mount | grep /apex
I noticed that on my Xiaomi Poco X3 NFC device (which I used to develop my SystemRW/SuperRW feat. MakeRW script) I can remount all subpartitions as RW just fine but for some reason I cannot remount apex as rw?!
Bash:
mount -o remount,rw /apex/com.android.runtime
mount: '/dev/block/loop22'->'/apex/com.android.runtime': Invalid argument
Here is the root of your problem:
Bash:
/dev/block/loop22 on /apex/com.android.runtime type ext4 (ro,dirsync,seclabel,nodev,noatime)
As you can see it is mounted read-only.
Click to expand...
Click to collapse
Here are my logs, just flashed the flashable.zip with the little trick #sdkCheck under Android 12. Here is the outcome. Unfortunately the root directory together with most of its subdirectories stay read-only and can't be mounted rw.
Look at the top answer of this thread inability to remount system I think therein lies the problem, not sure tho.
It always says failed to mount /system_root
I'm going forward and look for a solution to get access to this read-only partitions.
Thanks for the log!
bongmeiister said:
It always says failed to mount /system_root
Click to expand...
Click to collapse
That error has nothing to do with my SystemRW/SuperRW feat. MakeRW script. That's TWRP related error (or Orangefox in this case).
Your mylog.txt looks good to me
And phone still boots after automatically flashing super_fixed.bin in recovery.
If no bootloop that's already a partial success right there
Did you check if shared_blocks read-only feature was successfully removed from your subpartitions by my SystemRW/SuperRW feat. MakeRW script?
Bash:
adb shell
su
for i in `seq 0 5`; do tune2fs -l /dev/block/dm-$i | grep -e "volume" -e "features"; done
lebigmac said:
Thanks for the log!
That error has nothing to do with my SystemRW/SuperRW feat. MakeRW script. That's TWRP related error (or Orangefox in this case).
Your mylog.txt looks good to me
And phone still boots after automatically flashing super_fixed.bin in recovery.
If no bootloop that's already a partial success right there
Did you check if shared_blocks read-only feature was successfully removed from your subpartitions by my SystemRW/SuperRW feat. MakeRW script?
Bash:
adb shell
su
for i in `seq 0 5`; do tune2fs -l /dev/block/dm-$i | grep -e "volume" -e "features"; done
Click to expand...
Click to collapse
Yes, script worked great! Here is the outcome after checking for the shared_blocks read-only feature:
The custom recovery seems to have problems mounting the system_root probably because of the Android 12 encryption and A/B partition, since this stuff things got tough... Yesterday I successfully Disabled Force Encryption for more freedom!
bongmeiister said:
Yes, script worked great!
Click to expand...
Click to collapse
That's wonderful news! Congratulations for getting my old script to work on your Android 12 device.
Can you do this now?
Regarding the /apex you will have to do some more research. Hopefully you can find the answer to this /apex problem and share it here with us! Good luck in your quest!
And enjoy debloating and customizing your stock ROM until satisfaction
lebigmac said:
That's wonderful news! Congratulations for getting my old script to work on your Android 12 device.
Can you do this now?
Regarding the /apex you will have to do some more research. Hopefully you can find the answer to this /apex problem and share it here with us! Good luck in your quest!
And enjoy debloating and customizing your stock ROM until you satisfy your personal preferences!
Click to expand...
Click to collapse
Thank you very much, working like charm!
Regarding the /apex I was looking quite a while now for a solution, but seemingly since Android 10 you can not mount /system_root that easily anymore.
https://developer.android.com/about/versions/11/privacy/storage#other-apps-data
So whatever, I gave up on that one, the changes were not that important anyway.
i'm planning to edit the file at /apex/com.android.conscrypt/javalib/conscrypt.jar to be able to bypass ssl pinning but looks like i'll give it up

Merlin /system RW, is this possible ? magisk & adb_root installed

Hi, can't have full access to /system folder with adb
Installed magisk OK
Installed magisk extension module 'adb_root' OK
Code:
adb root
adbd is already running as root
but when I try to delete :
Code:
adb shell rm - f /system/app/CloudService/CloudService.apk
receive Read-only file system
any help ?
Code:
adb shell
mount -o rw,remount /
/dev/block/dm-1 is read-only
Code:
adb disable-verity
verity cannot be disabled/enabled - USER build
tried 'systemrw_1.32' and 'systemrw_1.32_modded' with no success, the installation seems to have been just fine
then flashed the only file I found into /img folder with command :
Code:
fastboot flash super super_fixed.bin
but at the end, even if all is gone fine, the command give always same answer as read-only :
Code:
mount -o rw,remount /
/dev/block/dm-1 is read-only
is there a way to make MERLIN as /system RW ???
matteo555 said:
tried 'systemrw_1.32' and 'systemrw_1.32_modded' with no success, the installation seems to have been just fine
then flashed the only file I found into /img folder with command :
Code:
fastboot flash super super_fixed.bin
but at the end, even if all is gone fine, the command give always same answer as read-only :
Code:
mount -o rw,remount /
/dev/block/dm-1 is read-only
is there a way to make MERLIN as /system RW ???
Click to expand...
Click to collapse
With PixelExperienceRecovery. Mount system then with adb remuont it rw. It is mounted in mnt/system/system.

Question Renaming a system file?

I have a rooted Pixel 7 and It was suggested that I rename a system file to prevent the system from updating itself (despite my having turned off all such options). My first attempt was to merely try renaming the file, but that didn’t work because the file systems in mounted RO.
I did some looking around, and the common approach to dealing with this issue is to remount the file system. Following is a ‘screen grab’ of my abd session:
Code:
cheetah:/ $ su
cheetah:/ $ ls /product
app etc fonts framework lib lib64 lost+found media overlay priv-app tts usr wallpaper
(this has the directory I want, so this file system)
cheetah:/ $ mount | grep product
/dev/block/dm-15 on /product type ext4 (ro,seclabel,relatime)
(this is a mounted file system)
cheetah:/ # mount -o rw,remount /product
'/dev/block/dm-15' is read-only
cheetah:/ # mount -o rw,remount -t ext4 /product
'/dev/block/dm-15' is read-only
cheetah:/ # mount -o rw,remount /dev/block/dm-15 /product
'/dev/block/dm-15' is read-only
(three attempts to remount – all failed)
So, now what should I try?
groston said:
I have a rooted Pixel 7 and It was suggested that I rename a system file to prevent the system from updating itself (despite my having turned off all such options). My first attempt was to merely try renaming the file, but that didn’t work because the file systems in mounted RO.
I did some looking around, and the common approach to dealing with this issue is to remount the file system. Following is a ‘screen grab’ of my abd session:
Code:
cheetah:/ $ su
cheetah:/ $ ls /product
app etc fonts framework lib lib64 lost+found media overlay priv-app tts usr wallpaper
(this has the directory I want, so this file system)
cheetah:/ $ mount | grep product
/dev/block/dm-15 on /product type ext4 (ro,seclabel,relatime)
(this is a mounted file system)
cheetah:/ # mount -o rw,remount /product
'/dev/block/dm-15' is read-only
cheetah:/ # mount -o rw,remount -t ext4 /product
'/dev/block/dm-15' is read-only
cheetah:/ # mount -o rw,remount /dev/block/dm-15 /product
'/dev/block/dm-15' is read-only
(three attempts to remount – all failed)
So, now what should I try?
Click to expand...
Click to collapse
I haven't used this, but maybe it can help you.
Lughnasadh said:
I haven't used this, but maybe it can help you.
Click to expand...
Click to collapse
Thank you. Seems like this might work, but after reading several pages, I am not sure how to install/use overlayfs. I have a Windows system - any chance you could point me to something that provides some guidance?
groston said:
Thank you. Seems like this might work, but after reading several pages, I am not sure how to install/use overlayfs. I have a Windows system - any chance you could point me to something that provides some guidance?
Click to expand...
Click to collapse
I've never used this before but I believe once you flash the module it makes the /system RW so you can start making modifications. There's a README that provides some information. I don't know of any other guides besides the information on that Github page.
Checking out the thread below might reveal a solution and/or give a clue or hint...
Pixel 7 Pro Stuck in read only mode (rooted with magisk 26.1) Am I missing something? HELP
Everything ive tried in FX Explorer fails. No matter what I try, for example editing build.prop or anything else, it constantly says read only. i cannot use any method to allow write access. Did i miss something when i rooted with Magisk? I dont...
forum.xda-developers.com
simplepinoi177 said:
Checking out the thread below might reveal a solution and/or give a clue or hint...
Pixel 7 Pro Stuck in read only mode (rooted with magisk 26.1) Am I missing something? HELP
Everything ive tried in FX Explorer fails. No matter what I try, for example editing build.prop or anything else, it constantly says read only. i cannot use any method to allow write access. Did i miss something when i rooted with Magisk? I dont...
forum.xda-developers.com
Click to expand...
Click to collapse
Good suggestion. I installed FX File Explorer, gave it the appropriate permissions, but was unable to change the /product filesystem to read/write.
groston said:
Good suggestion. I installed FX File Explorer, gave it the appropriate permissions, but was unable to change the /product filesystem to read/write.
Click to expand...
Click to collapse
When you say "gave it the appropriate permissions", just to confirm -- that doesn't mean that you changed the security permissions on the folder & files, correct? I hope it means you did not do what the OP in that thread had done and actually did enable root access particularly (hoping that's what you meant on "gave it appropriate permissions").
Because, in certain cases, I've changed permissions on files/folders vs. simply enabling root access mode....
Apologies in advanced if my inquiry seems fairly obvious (to the point of insulting maybe; it is not meant to be), but you never know and many foolish things has been done/assumed on this site that missed many (obvious) things because it wasn't confirmed....

Categories

Resources