yashsingh1/xdaforums huggingface dataset:
[Android Software/Hacking General [Developers Only]] Greenspoof:
I had a error with previous version about cow error. But with last version, no cow error. The script worked! Thx again ;)
[Android Software/Hacking General [Developers Only]] Greenspoof:
Magic script, everyone who see this, go with closed eyes, it's pur magic, Android 11 with r/w, so easy
[Android Software/Hacking General [Developers Only]] season 8:
Please update for android 12, thanks
[Android Software/Hacking General [Developers Only]] lebigmac:
Hi @xen423

Thanks for your feedback. I will add you to the list of successful devices on front page 😉

I'm happy that script works as expected on your OnePlus 8T device.

Enjoy a fully read/write-able system! :love:(y)

Hi @Hippie459MN

Thanks for your interest in this project. It's nice to see some Sony users interested in making their next gen devices into fully read/write-able flagships!

If you're running stock Android 11 and your bootloader is unlocked I don't see why it shouldn't work. And with the flashable zip it's basically a 1 click solution ;)

After installing and running script please send me your log files from /data/local/tmp/systemrw_1.32/log/

Thanks!

Good luck 😉 (y)

Hi @DeviLL2014

Thanks for your feedback. I checked your dmesg output and only found this. Search for avc and you should see the errors.

Spoiler content hidden.

Hi @BC-19

Thanks for your interest in this project. Please send me your log files from this folder

/data/local/tmp/systemrw_1.32/log/ Thanks!

If you want to support this project then please feel free to click the donate button on front page. Thanks! Your support is much appreciated 😉(y)

That new autoresize feature is already implemented but next version is not ready yet. Still working on some new features. Don't worry soon it will be released. Stay tuned ;)

Hi @Greenspoof

Thanks for the nice words. Please send me your log files from this folder

/data/local/tmp/systemrw_1.32/log/ Thanks!

I am happy that script finally works as expected on modern OnePlus devices.

Enjoy a fully read/write-able system! :love:(y)

Hi @HyperCriSiS

You are running it right but you are running the wrong script. The included sysrw_repair script is Linux only! Try the other Android script that's inside the flashable.zip file and then please send me your log files from

/data/local/tmp/systemrw_1.32/log/ Thanks. Good luck (y)

Hi. Does Android 12 have shared_blocks read-only feature?

You can check it like this:

adb shell
su
touch /sdcard/my_tune2fs.txt
for x in `ls -l /dev/block/by-name | awk '{print $NF}'`; do tune2fs -l $x>>/sdcard/my_tune2fs.txt; done

Also run these commands:

adb shell
su
touch /sdcard/my_dm_tune2fs.txt
for x in `seq 0 5`; do tune2fs -l /dev/block/dm-$x>>/sdcard/my_dm_tune2fs.txt; done

Then please upload these 2 files here : /sdcard/my_tune2fs.txt and /sdcard/my_dm_tune2fs.txt

Thanks (y)
[Android Software/Hacking General [Developers Only]] JimmyMX:
Ok

it's like this :

I have Asus ROG III

stock android 11

twrp latest

rooted with latest magisk

I have Xposed working and some modules installed on Xposed

I too have some modules installed on magisk

I have plenty of free storage

I have RW system

the question is: I want to install a full update package from Asus , after wards I should probably lose RW system

how should I approach this with 💯 success and without having to wipe data?

thank you
[Android Software/Hacking General [Developers Only]] lebigmac:
Hi @JimmyMX. Thanks for your feedback. Please feel free to upload your log files from

/data/local/tmp/systemrw_1.32/log/

I am happy that script works as expected on your Asus ROG III device :D

Enjoy a fully read/write-able system :love:(y)

After installing new OTA from your manufacturer you will have to run script again. Just don't wipe /data in the process!

Good luck! 😉 (y)
[Android Software/Hacking General [Developers Only]] 我是十七:
E:\platform-tools>adb shell

Spoiler content hidden.
[Android Software/Hacking General [Developers Only]] 我是十七:
Starting TWRP 3.5.2_9-0-2bc3eccd on Thu Jan 22 10:49:22 1970

Spoiler content hidden.
[Android Software/Hacking General [Developers Only]] Hippie459MN:
Yup, stock android 11 with unlocked bootloader and root via Magisk. Silly question but the Sony Xperia 1 iii doesnt have a custom recovery yet so would I just copy the systemrw_1.32 folder from the flashable zip to the /data/local/tmp directory then run the command (chmod +x /data/local/tmp/systemrw_1.32/systemrw.sh) in something like Terminal Emulator on the phone itself? Thats where I am a little confused on what to use to run the command. Just want to make sure I do it right.
[Android Software/Hacking General [Developers Only]] Miustone:
That's what i did on My Xperia 5. Without success... But Yours has a super Partition so idk If it works for You.
[Android Software/Hacking General [Developers Only]] lebigmac:
@Miustone what results do you get if you run these commands?

adb shell
su
touch /sdcard/my_blk_features.txt
for i in /dev/block/by-name/*; do tune2fs -l $i>>/sdcard/my_blk_features.txt; done
[Android Software/Hacking General [Developers Only]] lebigmac:
@Miustone

Thanks for the command output above. It looks like your device doesn't have shared_blocks read-only feature.

And now please send me output of the commands below. Thanks (y)

adb shell
su
touch /sdcard/my_dm_features.txt
for i in `seq 0 5`; do tune2fs -l /dev/block/dm-$i>>/sdcard/my_dm_features.txt; done
[Android Software/Hacking General [Developers Only]] Miustone:
J9210:/ # for i in `seq 0 5`; do tune2fs -l /dev/block/dm-$i>>/sdcard/my_dm_features.txt; done

tune2fs: No such file or directory while trying to open /dev/block/dm-0

Couldn't find valid filesystem superblock.

tune2fs: No such file or directory while trying to open /dev/block/dm-1

Couldn't find valid filesystem superblock.

tune2fs: No such file or directory while trying to open /dev/block/dm-2

Couldn't find valid filesystem superblock.

tune2fs: No such file or directory while trying to open /dev/block/dm-3

Couldn't find valid filesystem superblock.

tune2fs: No such file or directory while trying to open /dev/block/dm-4

Couldn't find valid filesystem superblock.

tune2fs: No such file or directory while trying to open /dev/block/dm-5

Couldn't find valid filesystem superblock.

+

tune2fs 1.45.4 (23-Sep-2019)

tune2fs 1.45.4 (23-Sep-2019)

tune2fs 1.45.4 (23-Sep-2019)

tune2fs 1.45.4 (23-Sep-2019)

tune2fs 1.45.4 (23-Sep-2019)

tune2fs 1.45.4 (23-Sep-2019)

(We are talking over PM now. I've updated My last post)
[Android Software/Hacking General [Developers Only]] Kira565:
Lo probé en mi motorola one fusion y funcionó muy bien para mí, gracias por esa contribución.
[Android Software/Hacking General [Developers Only]] JimmyMX:
ok

so i installed new OTA

then rebooted everything was fine

then i installed magisk ok

i rebooted , things still ok

then i rebooted to twrp i installed sw script

now im fkd , twrp doesnt recognize data partition and is saying faild to mount data bad argument

tried the twrp file manager nothing is in sd card its like data got encrypted and twrp cant decrypt and not asking for the passcode like it used to

i fell its something wrong with your script man , i still didnt wipe data just yet , but i think thats the only way out right now

please replay ASAP

THANX
[Android Software/Hacking General [Developers Only]] JimmyMX:
ok

so i installed new OTA

then rebooted everything was fine

then i installed magisk ok

i rebooted , things still ok

then i rebooted to twrp i installed sw script

now im fkd , twrp doesnt recognize data partition and is saying faild to mount data bad argument

tried the twrp file manager nothing is in sd card its like data got encrypted and twrp cant decrypt and not asking for the passcode like it used to

i feel its something wrong with your script man , i still didnt wipe data just yet , but i think thats the only way out right now

please reply ASAP

THANX
[Android Software/Hacking General [Developers Only]] lebigmac:
Are you sure it's not a problem related to your twrp? Can you boot into Android and check if script worked?
[Android Software/Hacking General [Developers Only]] JimmyMX:
are you serious right now ???1

boot into android !!!!

my phone is bootlooping into twrp , and no twrp is fine thank you
[Android Software/Hacking General [Developers Only]] lebigmac:
To undo bootloop simply restore original stock super image and re-enable dm-verity and verification with the included avbctl binary (/tools subfolder). Those are the only changes performed by the script.

The script doesn't affect /data partition. It only uses project path in /data partition for dumping files and doing its job.
[Android Software/Hacking General [Developers Only]] JimmyMX:
restore , you mean install firmware or what??

can you explain please im currently locked out of my phone with twrp saying data partition 0mb

should i format data or wipe everything or what should i do
[Android Software/Hacking General [Developers Only]] lebigmac:
Twrp should have avbctl binary by default.

adb shell
avbctl enable-verity
avbctl enable-verification

Now fastboot flash your stock read-only super image to your super partition and you have just undone all changes that the script has done to your device. Congratulations.

If you ask me you shouldn't have installed that OTA since script was working fine in previous firmware version. Maybe Asus closed this R/W vulnerability in their latest OTA?
[Android Software/Hacking General [Developers Only]] JimmyMX:
ok

thanx for the reply

im currently extracting payload.img

should i excute avbctl commands in twrp terminal or adb on pc

and can you give me the command to fastboot flash the super image exactly

and for the OTA i cant stay not updated updates bring battery improvements and secuity patches thats all

Edit: i executed the avb commands in twrp , i first ran the commands Get-

on slot a and slot b to know the status of dm-verity and verification slot a gave disabled and slot b gave enabled

and after that i rebooted to slot a twrp which is different than slot b twrp one is 3.1.51 and one is 3.1.52

then i rebooted into slot a system without flashing stock super img ,

now im back on android but the system is not rw anymore ,

what should i do now to get rw system ??

by the way your a life saver i cant thank you enough , but MAY THE FORCE BE WITH YOU ❤️❤️❤️❤️❤️❤️

and for the record this is exactly what happend to me a year ago when i told you i HAD to wipe , it was back then my fault not to ask for help

anyway thank you sir
[Android Software/Hacking General [Developers Only]] 012345678:
not working anymore on Android 12 Miui on Mi 11 Ultra :(
[Android Software/Hacking General [Developers Only]] JimmyMX:
hello

it is odd indeed

i tried this method on asus ROG III with a b partitions but everytime i set active slot to b and boot into recovery twrp is telling me that it cannot mount data and data partition is 0mb

do you have any idea about how to fix this

im running it on android 11 stock

thanx
[Android Software/Hacking General [Developers Only]] Kira565:
"Be careful with this comment" Yesterday I published that the script worked very well on my motorola one fusion and yes and what I did later was change my bootanimation but after trying several it brikeo me and I tried to copy the original bootanimation and remove the one that I had placed but the recovery at the time of doing the process told me that it only had reading not writing and I gave it the option to mount but it only left me in reading I could not modify it in conclusion I had to install the software again since I formatted it And it did not work for me well I installed the android again today I already did it root I installed the recovery and now that I try to use the script again it gives me error # 73 both in the recovery and the manual installation I would appreciate if you can give me help on how use the repair.zip to see if it helps me fix my problem. Edit excuse my English I am using a translator. Again I would appreciate your help with that error 73 Thank you.
[Android Software/Hacking General [Developers Only]] lebigmac:
Hi @Kira565 to fix error 73 use the included sysrw_repair script (linux only)

sysrw_repair script instructions

A year ago this script didn't exist yet ;)

@season 8 @012345678 Did you try adding Android 12 support in script yet?

Simply add these 2 lines between line #403 and #404, save file and try again. Good luck!

elif (( $sdkVersion == 31 )); then
android=12

Hello @Kira565 thank you for the nice words. Congratulations! I am happy that my script works well on your motorola one fusion device. Did you experience error 73 during the process?

Have fun optimizing and customizing your fully read/write-able device! :love:(y)

Please send me your log files from this location thank you! (y)

/data/local/tmp/systemrw_1.32/log/

Hello @EveryYest thank you for your log file. It's unusual to have no super partition but WITH shared_blocks feature on all partitions!

Did you end up fastboot flashing all those .img files from the /nosuper/ subfolder? And phone actually booted afterwards? That is amazing news! I can't believe the script actually works on your Pixel 2 XL (2017) device!

Congratulations! Enjoy a fully read/write-able device! :love:(y)

Could you please run the code below and send me this file thank you (y) /sdcard/my_lpdump.txt

/data/local/tmp/systemrw_1.32/tools/lpdump>/sdcard/my_lpdump.txt
[Android Software/Hacking General [Developers Only]] JimmyMX:
sorry for the misinformation , i got so exited and i had so much fun having my phone sysrw i felt it was a year maybe 😁😁😁😁😁 , anyway

trying out your linux method fix for the repair zip using linux mint

i will report that im currently waiting for the script to flash super_fixed.bin at bootloader 😵😵😵😵😵

it booted into bootloader but in terminal its saying waiting for any device and its taking so long ,

should i do something or should i wait???

Edit : things are happening ,

after the script sysrw.sh repacked the super fixed partition on linux it restarted to bootloader to flash the super partition but didnt finish i unplugged the phone and returned to windows and flashed the super fixed.bin via fastboot and finally it flashed all 21/21 in my case,

the command was : fastboot flash super super_fixed.bin

afterwards i rebooted into twrp and i re-enabled virity and verification on slot b then slot a

then i rebooted into android and BANG mount -o remount,rw / worked on terminal

and finally i have RW System on latest stock android 11 on asus ROG III

A/B partitions

thanx @lebigmac thanx @poyiqqq thanx @harpreet.s

😵 😵 😵 😵 😵 😁😁😁😁😁
[Android Software/Hacking General [Developers Only]] Kira565:
Alguien ayúdeme. ¿Cómo ejecuto el script para el error 73 en una máquina virtual Linux?
[Android Software/Hacking General [Developers Only]] lebigmac:
@JimmyMX

Congratulations! I can't believe you actually got it to work in the end using the harpreet workaround :ROFLMAO:

What was the problem? Did you experience error 73 or what?

Could you please send me all your log files from this folder? Thanks! It helps with fixing bugs.

/data/local/tmp/systemrw_1.32/log/

Enjoy a fully read/write-able device! :love:(y)

You've been using the script for almost a year now? That's great! How do you like the project so far?

If you like this project and want to support further development of SystemRW & the creation of more amazing projects like this then please feel free to donate to the developer by clicking the Donate button on front page. Thanks! Your support is very much appreciated! (y)

Hi @Kira565 please see my reply to you here

Try this:

Extract sysrw_repair_v1.32_proper.zip on your computer

Open Terminal window inside this folder ./sysrw_repair_v1.32_proper/sysrw_repair_v1.32/

Make repair script executable: chmod +x ./sysrw_repair.sh

Execute the repair script in your Linux terminal app: ./sysrw_repair.sh

After repair script finishes you can fastboot flash super super_fixed.bin
[Android Software/Hacking General [Developers Only]] dna1982:
Finally succeeded on OnePlus 8 Pro (Android 11 OOS_11.0.9.9.IN11AA).

But I still need to run "mount -o remount,rw /system_root" in TWRP to get /system_root to be writable.

Is this normal?
[Android Software/Hacking General [Developers Only]] Keven11:
Did the script run, and flash the super_fixed.bin file all correctly/successfully? If yes, then you don't need to run that from recovery. Termux or most other full featured terminal emulators work fine for this.
[Android Software/Hacking General [Developers Only]] dna1982:
First run script in TWRP, got 73 error. Then run repair script in Debian 11, create and flash super_fixed.bin file successfully.

Now you can debloat the hell out of it.
[Android Software/Hacking General [Developers Only]] trunghaut1:
Successfully flashed on Redmi Note 10 Pro MIUI 12.5 android 11 without error. I can change /system to RW.

But I can only rename or delete files in /system, moving files to /system fails on Root Explorer app (magisk root), reboot is still working at this time.

Then I try to move the file in twrp file manager with "rw remount" command and it works, but my phone gets bootloop when reboot :((
[Android Software/Hacking General [Developers Only]] Ringsofsaturn777:
Yes I'm sure I'm on Crdroid 7.10......And it can't mount R/W without your script...

And the flashing error was my fault.... systemrw_1.32_flashable.zip and sysrw_repair_v1.32_proper.zip were in the same zip....

I flashed without extracting.

Thank You
[Android Software/Hacking General [Developers Only]] Ringsofsaturn777:
Successfully flashed and working on Redmi 9 power (MIUI 12.0.10)

Flashed via Orange Fox
[Android Software/Hacking General [Developers Only]] lebigmac:
Hi @trunghaut1. Thanks for your feedback.

Congratulations! I am happy that script works as expected on your Redmi Note 10 Pro device running MIUI 12.5 (Android 11). :love: (y)

Please send me your log files from this folder, thanks (y)

/data/local/tmp/systemrw_1.32/log/*

Don't forget bootloop can always happen if you modify the wrong system file ;) Always make lots of backups! What kind of bootloop was it? Stuck at the MIUI logo?

It looks like you ran script without custom size parameter or with size=0. By default this will shrink each partition to minimum size before flashing super partition. Then you can only delete stuff from /system path but not copy stuff to it. You get the annoying insufficient space error in your file explorer app.

To fix this try running script again with larger custom size.

On Xiaomi devices size=25 or size=50 seems to work well. Good luck!

Enjoy a fully read/write-able device! :love:(y)

Hi @dna1982

Thanks for your feedback.

Congratulations! I am happy that script works as expected on your OnePlus 8 Pro device running (Android 11 OOS_11.0.9.9.IN11AA) :love:(y)

Error 73 is mysterious. It only happens on about 50% of devices I believe.

Please send me your log files from this folder. Thanks! (y)

/data/local/tmp/systemrw_1.32/log/*

Enjoy a fully read/write-able device! :love:(y)

Hi @Keven11 thanks for chiming in.

That's true. Script can be run both in Android and custom recovery mode ;) (y)

Hi @Ringsofsaturn777

Thanks for your feedback.

Congratulations! I am happy that script works as expected on your Redmi 9 power device running MIUI 12.0.10 - Android 11 :love: (y)

How did you like the script?

Please send me your log files from this folder. Thanks! (y)

/data/local/tmp/systemrw_1.32/log/*

Enjoy customizing your fully read/write-able stock Android device! :love:(y)
[Android Software/Hacking General [Developers Only]] 7GHz:
Nice one! Tested working with Samsung Galaxy Tab S6 Lite LTE (SM-P615) on A11.
[Android Software/Hacking General [Developers Only]] Hippie459MN:
With the help of lebigmac in private chat, I got this somewhat figured out and the script ran perfect but my new Sony Xperia 1 iii does not have a custom recovery yet so I have to flash the file manually in fastboot/bootloader. Silly question, so I dont screw something up here, what would the proper flash command procedure be for this? Thanks.
[Android Software/Hacking General [Developers Only]] xpxc:
systemrw: Initiating procedure...

systemrw: Device is in Android mode. Ignoring

systemrw: Current device: samsung

systemrw: Current Android version: 10

systemrw: Current SELinux status: Enforcing

systemrw: Unable to locate super partition on device. Ignoring

systemrw: /system is already R/W capable. Ignoring

systemrw: /product is already R/W capable. Ignoring

systemrw: /vendor is already R/W capable. Ignoring

systemrw: Adjusting permissions...

systemrw: Attempting to disable dm-verity and verification...

systemrw: Partition detected -> system @ /dev/block/sda22

systemrw: NO 'shared_blocks feature' detected @ system. Ignoring

systemrw: Partition detected -> vendor @ /dev/block/sda23

systemrw: NO 'shared_blocks feature' detected @ vendor. Ignoring

systemrw: There was a problem removing read-only restriction(s) of your device. Abort

He did not execute successfully
[Android Software/Hacking General [Developers Only]] Bonoboo:
UPD: here solutions

@lebigmac, huge thanks for this script, it's so vital now.

But I have problem. Device: Redmi Note 10 Pro with LineageOS 18.1 but MIUI's vendor.

After flashing script /vendor can be writeable. But not /vendor/etc folder. Nor in Android, nor in TWRP.

If in recovery execute mount -o remount,rw /vendor files can be renamed, but if copy there any or edit via nano they became 0 bytes in size.

Some observations. RootExplorer show different partition size. In root of /vendor - 1.64 GB, in /vendor/etc - 349 MB used. This size is same as /product partition.

Tried to mount as R/W it too, not helps. As I can say, there no symlink to /product

Command mount | grep vendor/etc shows this:

overlay on /vendor/etc type overlay (ro,seclabel,relatime,lowerdir=/product/vendor_overlay/30/etc:/vendor/etc,override_creds=off)

I searched thread, found same unresolved post.

Also tried to flash script with "size=50" as was suggested for similar case, same.

Please, help to solve this mystery. All I need is to edit fstab.* files.

Also here link to firmware-vendor.
[Android Software/Hacking General [Developers Only]] DeadRRR:
Doesn't work on Xiaomi Redmi Note 9, it install's everything and then i want to "try mount -o remount, rw /", its say:

1|redfin:/ # mount -o rw,remount /

'/dev/block/dm-2' is read-only
[Android Software/Hacking General [Developers Only]] lebigmac:
Hi. Try this and please report back your results. Thanks. Good luck!

fastboot flash super super_fixed.bin

Hi. You cannot set selinux to permissive? That's quite restrictive but what do you expect from Samsung... Next time you should get Xiaomi device. It's much more open source friendly.

Are you using custom ROM? Then chances are your device is already fully r/w capable.

Please check manually if your device have shared_blocks read-only feature and report back your results. Thanks.

adb shell
su
touch /sdcard/my_tune2fs_output.txt
for i in `seq 0 5`; do tune2fs -l /dev/block/dm-$i>>/sdcard/my_tune2fs_output.txt; done

Hi. I'm happy you like my script.

Are you saying script works as expected but /vendor/etc is still read-only while /vendor itself is r/w? That's odd. Did you try remounting /vendor/etc as rw?

Please send me your log files from script folder. Thanks.

And please check manually if your /vendor and /vendor/etc partitions have shared_blocks read-only feature and report back your results. Thanks. See my answer to xpxc above on how to do this.

Also please keep in mind this script was designed for stock firmware and not for custom ROM. Custom ROM should be fully r/w capable by default otherwise it's missing some key features IMHO.

Hi. Saying only 'doesn't work' is not very helpful. Please provide screenshot and your log files from script folder if you want me to look into your issue. Thanks.