I have Android 7.0 and I want any way / tool to convert System to RW without root, I know there is a method already but it's only for Android 10+ and devices that have dynamic partion.
How do I make System.img RW?
you don't want to convert system rw.
you want to mount system rw.
impossible without root.
Related
Hey there?
I've got a question which I can't seem to find anywhere else and YES I have searched this forum and google. However, I may miss it.
Anyway, I've mapped my android phone as a network drive using Samba and changed the smb.conf file to show the System Root directory as well. However, system root is default set as R/O so to mange files USING my computer I need to change the permission to R/W using a file manager (such as root explorer). This is annoying, as I have to keep doing this in order to write to certail directories.
What I wish to do is create a massive guide on all of this to help out the community, however I need one little bit of information.
I would like the / directory (root) to be mounted as R/W as default so that I can quickly edit files on my PC without having to constantly change it to R/O.
If this has been answered before, I do apologize.
Thanks in advance.
Regards,
xxSHABSxx
EDIT:
To make things a bit clearer.
I want something that will automatically mount my phone's root dir into rw upon boot, without custom apps/having to manually mount as rw everytime it reboots. And yes I understand there are apps that do this.
Yes, the root file system is read-only, but it's also volatile. It's restored from the initramfs in the boot image each time you reboot the phone, so only mounting it writeable, doesn't do you very much anyway.
In /init.rc you find a line:
Code:
mount rootfs rootfs / ro remount
This remounts your root read-only. Remove this, and it'll stay writeable. But again, all edits to the root file system are volatile. To change this, you must flash a new boot.img
An easier way would be a root-app remounting it writable again after boot.
kuisma said:
Yes, the root file system is read-only, but it's also volatile. It's restored from the initramfs in the boot image each time you reboot the phone, so only mounting it writeable, doesn't do you very much anyway.
In /init.rc you find a line:
Code:
mount rootfs rootfs / ro remount
This remounts your root read-only. Remove this, and it's stay writeable. But again, all edits to the root file system are volatile. To change this, you must flash a new boot.img
An easier way would be a root-app remounting it writable again after boot.
Click to expand...
Click to collapse
Ahh I figured as much, since Google didn't offer any solutions to me. And flashing is way much more effort than simply having an app that does it for you.
Anyway thanks for the reply!
xxshabsxx said:
Ahh I figured as much, since Google didn't offer any solutions to me. And flashing is way much more effort than simply having an app that does it for you.
Click to expand...
Click to collapse
Or do like I did, move the root to a real ext3 non-volatile file system instead.
Hello,
How to convert from EROFS file system to ext4 or any other compatible for write operations?
In POT-LX1 vendor and system is EROFS (Extendable Read Only File System)
To remove encryption from POT-LX1 you have to use adb shell and copy vendor image and then find with hex editor file-encryption lines and remove them in order to leave user-data unencrypted.
But If we can convert it to normal ext4 then we could put root apps to system directory priv-apps and use root.
I am still looking for a way to root my POT-LX1
Hi,
Nice to hear that any positive findings?
Thanks,
goldybewon
Huawei P30 Pro. 8/256
Did u was successful in this?
I wanted to delete some files from the system like some useless system apps/themes etc. I was trying to root my phone with magisk. The magisk would install but I couldn't make any kind of changes because I found it was read-only! Now if I want it to mount read-write, it just won't. Any solutions, anyone?
Resmi Note 9S Curtana, OFox R11 installed with xiaomi.eu 12.0.1.0, android 11
Try this script from this thread.
You can't mount system because of dynamic partitions (super partition). The script linked above doesn't mount system rw, it just makes a new super partition.
The real way to make edits to dynamic partitions is with adb remount which replaces the old 'mount -o rw, remount /system' method.
The practical way to make edits is systemlessly with a magisk module.
Adb remount info
Dynamic partitions info
jwchips said:
You can't mount system because of dynamic partitions (super partition). The script linked above doesn't mount system rw, it just makes a new super partition.
The real way to make edits to dynamic partitions is with adb remount which replaces the old 'mount -o rw, remount /system' method.
The practical way to make edits is systemlessly with a magisk module.
Adb remount info
Dynamic partitions info
Click to expand...
Click to collapse
I feel superdumb but @jwchips , where am I supposed to put those commands- in custom recovery terminals, in Windows command prompt or in a terminal emulator app?
Plz someone teach me step by step. I can't rw system by root explorer in miui rom, but I can do it in aosp rom. I don't know what causing this result. Since android 2 to android 11. Every upgrade time I struggle a lot. Now I spend 2 mouth to search internet but for code noob like me, get nothing. I'm still study it hope a newvice tutorial post.
same problem here, ive tried different zips and also doing it manually, no success
Azamsm said:
I wanted to delete some files from the system like some useless system apps/themes etc. I was trying to root my phone with magisk. The magisk would install but I couldn't make any kind of changes because I found it was read-only! Now if I want it to mount read-write, it just won't. Any solutions, anyone?
Resmi Note 9S Curtana, OFox R11 installed with xiaomi.eu 12.0.1.0, android 11
Click to expand...
Click to collapse
Why not try debloater magisk?
GitHub - sunilpaulmathew/De-Bloater: An application using the power of Magisk to debloat unwanted system apps!
An application using the power of Magisk to debloat unwanted system apps! - GitHub - sunilpaulmathew/De-Bloater: An application using the power of Magisk to debloat unwanted system apps!
github.com
Build.prop file accidentally got empty and haven't rebooted yet. Any ways to restore it?
Am i screwed?
You have a customer recovery? Then you can dirty flash your rom
I definitely would have done that if i did.
But TWRP was never released for my phone (poco x3 gt)
Depends the device and android version I guess...
I would do getprop and edit the output to build.prop form.
Notice to chmod the file correctly, 644 or whatever..
I think you can reboot safely because build.prop is inside super partition and therefore read-only.
of course you can download stock ROM from xiaomifirmwareupdater and extract build.prop from super.img, but it's more easy to flash super.img from fastboot.
aIecxs said:
I think you can reboot safely because build.prop is inside super partition and therefore read-only.
of course you can download stock ROM from xiaomifirmwareupdater and extract build.prop from super.img, but it's more easy to flash super.img from fastboot.
Click to expand...
Click to collapse
Nvm my phone just got an OTA update.
I just have to restore the root now
aIecxs said:
I think you can reboot safely because build.prop is inside super partition and therefore read-only.
Click to expand...
Click to collapse
And it's empty like how? Weird crap anyway... ok now, so who cares...
Idk but /system /vendor /product /system_ext /odm are ro dynamic partitions inside super partition, either OP did re-duplicate blocks with e2fsck -E unshare_blocks and disabled avb/dm-verity to allow remount rw / system_root (would break OTA), or it simply wasn't written to build.prop at all (magisk systemless overlay)? "empty" could also mean does not exist/no permissions...
https://github.com/Yuyuko1024/device_xiaomi_chopin/blob/lineage-18.1/rootdir/etc/fstab.mt6891
TWRP is available btw
https://forum.xda-developers.com/t/twrp-unofficial-3-6-0-poco-x3-gt-redmi-note-10-pro-5g.4369207
Hello
Its about getting rw in erofs system OS12
I unpack rom resize it and edit some
Changes then repack and flash
But its still same after flash
Nothing changed everything back to stock conditions
I think I'm missing something or few commands to remove write protection
And make it fully rw
In cmd i get rw selcetable etc
In root explorer also change to rw but still nothing able to change
Is there anyone can able to help I'll donate