[MAGISK][TWRP][ARM32/64][A8+]Universal Read Only to Read Write for android (RO2RW) | Auto converting SUPER "system partitions" to read/write mode

[LeeGarChat]

In any case, I can refuse setenforce, because I came up with another way to migrate files. Selinux-permisive is needed to copy with full rights and context. But in the new version there will be another way discovered by me

Yes. Its working. But a dont try booting. Nevermind, later ill trst it

Spoiler: Screenshots

Dirty code

mkdir vendor
umount vendor
mount -r /dev/block/mapper/vendor_a ./vendor && {
 echo "mounted vendor"
} || {
mount -r -t ext4 /dev/block/mapper/vendor_a ./vendor && {
 echo "mounted vendor"
} || {
mount -t ext4 /dev/block/mapper/vendor_a ./vendor && {
 echo "mounted vendor"
} || {
mount -t ext4 /dev/block/mapper/vendor_a ./vendor && echo "mounted vendor" || exit 1
}

}
}

cd vendor
rm -f /data/local/tmake/vendor_file_contexts1
for dir in $(find -type d) ; do
ls -lZad $dir/* >> /data/local/tmake/vendor_file_contexts1
done
cd ..
echo "/vendor(/.*)? u:object_r:vendor_file:s0" > ./vendor_file_contexts
awk '{print "/vendor/"$9" "$5}' ./vendor_file_contexts1 >> ./vendor_file_contexts
sed -i 's|\/\.\/|\/|g' ./vendor_file_contexts
sed -i 's|\.|\\.|g' ./vendor_file_contexts
sed -i 's|\+|\\+|g' ./vendor_file_contexts
make(){
./make_ext4fs -J -T 1230764400 \
        -S ./vendor_file_contexts \
        -l "$(du -sb ./vendor | awk '{print int($1*2)}')" \
        -a vendor -L vendor \
        ./vendor.img ./vendor
}
make

 

[LeeGarChat]

Summary of RO2RW: A set of new features will be implemented and existing issues will be fixed where possible, including no longer requiring a disabled selinux. Trial support for converting RW2RO EXT4-2-F2FS, F2FS-2-EXT4, EXT4-2-EROFS will be implemented, that is, conversion to different file systems.

My Telegram support group and link to full message blog

 

[LeeGarChat]

I came up with one solution to the problem without special crutches in the form of garbage removal for large ROMs, I need feedback on which of the options to implement. There will be a RO2RW pre-process that will need to be done, Explanation of methods on telegra.ph

 

[agabey_42]

i had updated my phone. (mi 11 venus). the system has become erofs again. i used the latest version to make the system rw and it is very successful.

 

[nagper]

I came up with one solution to the problem without special crutches in the form of garbage removal for large ROMs, I need feedback on which of the options to implement. There will be a RO2RW pre-process that will need to be done, Explanation of methods on telegra.ph

I'd opt for variant2.
Phones nowadays has more then 100GB of storage, if someone wants RW access can might can sacrifice the extra space.
Variant1 sounds dangerous indeed, someone might can risk his bricking phone btw to move this forward.

 

[nagper]

I've just tried your RO2RW script, works without any problems, even has the option to remove bloatware on the fly, perfect.
I did not flash the result btw as i want to go back to a RO file system.

I wonder if i can leave the ext4 conversion out completely like this:

mount -o loop erofs_partition_exported_by_lpunpack.img /mnt
mkfs.erofs --exclude-regex=YouTube no_youtube.img /mnt/
img2simg no_youtube.img no_youtube_sparse.img

Would it work to flash the resulting image partition (and not the whole super partition) with fastboot?

Although @LeeGarChat has already responded that i need to be careful creating a new erofs file system, i wonder if i risk anything by testing it.
I mean can i safely overwrite a particular partition in fastboot (if the size is less then the original one) in case i have the original partitions as a result of running lpunpack?
Can I simply flash the original one via fastboot in case the file system I've created/flashed has problems and leads to a boot-loop?

 

[LeeGarChat]

I flashed the script in a magic then in black window I did su and then ro2rw then I chose sparse and force and then i fapboot and I flash the soup and swiped data. How do I verify it worked

 

[AmericanRebel]

So.......what specific selections am I suppose to select when flashing this? I will be using TWRP (Unofficial). My device is OnePlus 8T Global (converted from T-Mobile) A13 F_15.

 

[kissa67zwi]

Samsung А73 is not installed

 

[kissa67zwi]

Why not?

Tell me how to install it correctly on Samsung A73...You are welcome.I tried to install it, but it gives three errors when installing via TWRP.Help.Or if you can make a script for A73, please...I'm from Russia and I don't understand English...I am writing to you with a translator

 

[kissa67zwi]

After booting, constantly rebooting

 

[LeeGarChat]

That's a nice log

It doesn't look right, since the DFE function was worked out, and there was no selection menu for DFE, and there was no Force_start:enable . It should not be

I don’t have time to answer questions now, because I work a lot at my job, because I need money. And in my free time I think about the algorithm, the process of writing code is slowly going on, but I would not say that this is good, because in better times I could do what I wrote in a couple of weeks, I could write the same thing in a couple of nights. It is very difficult to think about all this, despite the fact that in order to test this script, I have to constantly transfer it to the phone, which takes time and causes inconvenience

I also do not have enough memory to download different ROMs of different devices and look at their structure for better optimization.

 

[LeeGarChat]

No one likes a Debby downer or a negative Nancy.

Answer me this please. Why can't your script mount vendor_dlkm?

The log file that you sent showed that you do not have a physical vendor_dlkm partition, so there is nothing to mount. For example, send the output response of the

mount |  grep "vendor_dlkm"

 

[Fatal_Scythe]

Hi, thanks for this Tool.

Unfortunately I'm having problems with almost all my Apps crashing when flashing the Super-RW.img in Fastboot. Also I can't edit any Files for example Build.prop. When editing & saving the Build.prop becomes empty which - of course - causes the Phone to bootloop on the next reboot.

My Phone is a Realme GT2 Pro running Android 13 btw.

 

[starbucks2010]

Hello,

Is there any possibility to run this script offline on stock fw files?

Thanks.

 

[Star_Eagle]

Could anyone please take the time to explain how to install and run this?

I've been trying to gain access to my phones super partition (Ulefone power armor 13) to try installing a GSI on it with TWRP.

 

[JedidroidX]

Will this work on a Oneplus 8T Tmobile Variant Oxygen OS 13? Any info is much appreciated.

Update on my post: I have tried flashing the script via TWRP on Oxygen OS 12 and no dice. I tried with numerous file explorers and write access is not granted. I have also tried the script as a magisk module and still no dice. I don't have any magisk modules installed except the script, no Overlay module. Perhaps it's a kernel issue which was noted in the OP.

However this was the closet to obtaining write access to the system partition and I hope active development will continue. The script has a lot of potential, I wish it was something I overlooked from obtaining write access.

One question: Is there a way to modify the images created after saving them for future flashing? As my main goal is too eliminate the GmsCore.apk from Oxygen OS. When selecting apps to delete I could not find GmsCore as the app is bigger than the max 150 mb in app selection of the script, perhaps increase it to a higher value if possible.

Update again: I just want to say thank you very much for this script as I was able to rid the awful Google spyware from my Oxygen OS 13 setup. It appears that I was able to delete when selecting the value size of apps to be selected for deletion. Still was not able to achieve true write access within a file explorer but still a brilliant script indeed!!!

 

[pr3dicament]

Will this work on a Oneplus 8T Tmobile Variant Oxygen OS 13? Any info is much appreciated.

Update on my post: I have tried flashing the script via TWRP on Oxygen OS 12 and no dice. I tried with numerous file explorers and write access is not granted. I have also tried the script as a magisk module and still no dice. I don't have any magisk modules installed except the script, no Overlay module. Perhaps it's a kernel issue which was noted in the OP.

However this was the closet to obtaining write access to the system partition and I hope active development will continue. The script has a lot of potential, I wish it was something I overlooked from obtaining write access.

One question: Is there a way to modify the images created after saving them for future flashing? As my main goal is too eliminate the GmsCore.apk from Oxygen OS. When selecting apps to delete I could not find GmsCore as the app is bigger than the max 150 mb in app selection of the script, perhaps increase it to a higher value if possible.

Update again: I just want to say thank you very much for this script as I was able to rid the awful Google spyware from my Oxygen OS 13 setup. It appears that I was able to delete when selecting the value size of apps to be selected for deletion. Still was not able to achieve true write access within a file explorer but still a brilliant script indeed!!!

I have a OnePlus 8T but it's the international version. If you run into problems and it doesn't work for you, don't be surprised. Their script did not work for me, neither did lebigmac or whatever, i ended up just doing it myself. Unless you clear enough space lol.. why do that when you can just do a couple of commands and that would be it? This SEEMS complex but it's probably one of the easiest things to do.

Update: It's much easier just to disable it yourself.. however, I'm glad it (kind of?) worked for ya? I don't know, you seemed kind of vague. For me, I couldn't get the script to work because I would run out of "space" no matter what, even with an empty 256GB. I did eventually get r/w working for myself, but it wasn't via any script. It's just a few simple commands and partitioning correctly after MSM (yeah, I know. Just use a VM through linux and just use USB passthrough and you'll be able to install the drivers., that's what i do)

PM me and we'll see if I can help you obtain 100% r/w access for your entire file system.

P.S. I just noticed you said it might be a "kernel issue" -- it's a file system issue. It has nothing to do with the kernel unless you just mean it loads the partitions...

Erofs stands for Enhanced Read-Only File System. It's not going to r/w through explorers, i.e root explorer (that's the best one to use, to hell with the rest of them) untl it's f2fs or ext4. Right now, you're using erofs. It didn't convert your system r/w, which is why you're still limited in that area. It's still erofs. Read only. You can delete things via TWRP but that's all, you cannot do it within the system when it has erofs. Erofs was designed to make Android phones faster but in my opinion, it's just as fast as the rest of them if you're talking about the naked eye. I don't see or feel a difference between it regarding speed, in fact I noticed erofs seems more likely to start lagging, freezing.. it's not a good file system.

 

[pr3dicament]

Hello,

Is there any possibility to run this script offline on stock fw files?

Thanks.

It's got nothing to do with root and TWRP has permissions to change partitions, but I'm not sure with their script. I'm not currently looking at it.. I'm currently making a testing environment. That being said, I will say a strong maybe, but others should chime in here.

 

[JedidroidX]

I have a OnePlus 8T but it's the international version. If you run into problems and it doesn't work for you, don't be surprised. Their script did not work for me, neither did lebigmac or whatever, i ended up just doing it myself. Unless you clear enough space lol.. why do that when you can just do a couple of commands and that would be it? This SEEMS complex but it's probably one of the easiest things to do.

Update: It's much easier just to disable it yourself.. however, I'm glad it (kind of?) worked for ya? I don't know, you seemed kind of vague. For me, I couldn't get the script to work because I would run out of "space" no matter what, even with an empty 256GB. I did eventually get r/w working for myself, but it wasn't via any script. It's just a few simple commands and partitioning correctly after MSM (yeah, I know. Just use a VM through linux and just use USB passthrough and you'll be able to install the drivers., that's what i do)

PM me and we'll see if I can help you obtain 100% r/w access for your entire file system.

P.S. I just noticed you said it might be a "kernel issue" -- it's a file system issue. It has nothing to do with the kernel unless you just mean it loads the partitions...

Erofs stands for Enhanced Read-Only File System. It's not going to r/w through explorers, i.e root explorer (that's the best one to use, to hell with the rest of them) untl it's f2fs or ext4. Right now, you're using erofs. It didn't convert your system r/w, which is why you're still limited in that area. It's still erofs. Read only. You can delete things via TWRP but that's all, you cannot do it within the system when it has erofs. Erofs was designed to make Android phones faster but in my opinion, it's just as fast as the rest of them if you're talking about the naked eye. I don't see or feel a difference between it regarding speed, in fact I noticed erofs seems more likely to start lagging, freezing.. it's not a good file system.

I appreciate the feedback! I would like to give an update: So it seems that I have converted to Ext4 from erofs using both methods via TWRP and as a magisk module. Afterwards I tried both super images after flashing in fastboot and it seems write access is still not granted and no fingerprint sensor...it booted without having to format via TWRP method and I think that's because I enable DFE (disabe force encyption) which is an option within the script.

So two issues using without data formating...NO fingerprint sensor and no write access......And when formatting data and booting into system I could not pass the android setup screen because when creating the rw super image I deleted the ridiculous GmsCore apk which is embedded into the android setup of Oxygen OS 13. hahaha but of course it would be.

Wondering if its possible to delete all apps responsible for the android setup screen after formatting data...would that bypass setup and take me straight to the oneplus launcher home screen? And if so, what apk's should be deleted when creating the super image?

So I created another super image with GmsCore and passed the android setup screen but still not fingerprint sensor and no write access. I would definitely like to make my system completely write access so I can have Oxygen OS 13 without you know what....GMSCORRRE.....sorry for capping that....also would like fingerprint sensor to work.....sooo I would like to try your methods of acquiring write access and I am very familiar with the msm tool but as in how to acquire write access using msm is new to me. Please enlighten me as I am very interested! Thank you!