[Closed] Universal SystemRW / SuperRW feat. MakeRW / ro2rw (read-only-2-read/write super partition converter)

[lebigmac]

v1.22 added to first post
That should fix your issue @Articul8Madness
@nttuan I'm not sure if this will work for you but you can try it.

 

[nttuan]

I tried version 1.22 and still the same issue. Please see the attached files.

 

[lebigmac]

@nttuan can you successfully run lpmake command manually?
Check the excellent Brepro1 tutorial and the excellent AndyYan tutorial on how to do this. Thanks.

@nttuan I have a possible solution for you. Check your PM

 

[kory-vadim]

@nttuan can you successfully run lpmake command manually?
Check the excellent Brepro1 tutorial and the excellent AndyYan tutorial on how to do this. Thanks.

@nttuan I have a possible solution for you. Your group size is not large enough to fit all the individual partitions inside in raw format. The solution is to convert all files into sparse before running lpmake command.
This is easier said than done though. I know it's possible because I've done it before in version 1.04 and earlier but right now I'm facing this problem:

lpmake --metadata-size 65536 --super-name super --metadata-slots 2 --sparse --output ./super_fixed.bin --device super:8589934592 --group qti_dynamic_partitions:8254596872 --image system=./system_sparse.img --partition system:none:2771027928:qti_dynamic_partitions --image product=./product_sparse.img --partition product:none:1186084560:qti_dynamic_partitions --image vendor=./vendor_sparse.img --partition vendor:none:1297484384:qti_dynamic_partitions
lpmake I 04-01 00:13:56 14374 14374 builder.cpp:1012] [liblp]Partition system will resize from 0 bytes to 2771030016 bytes
lpmake I 04-01 00:13:56 14374 14374 builder.cpp:1012] [liblp]Partition product will resize from 0 bytes to 1186086912 bytes
lpmake I 04-01 00:13:56 14374 14374 builder.cpp:1012] [liblp]Partition vendor will resize from 0 bytes to 1297485824 bytes
lpmake E 04-01 00:14:03 14374 14374 images.cpp:338] [liblp]Image for partition 'system' is greater than its size (2887667712, expected 2771030016)

I've already told you several times that you don't need to convert to sparse, because lpmake will still write a raw image to super.img.
Also, why are you merging the super section into a file? It takes time and a lot of space, pull the images directly from the super section.

 

[quanqw]

It don't work on my g8 android 10. It show error: 225

 

[quanqw]

@nttuan can you successfully run lpmake command manually?
Check the excellent Brepro1 tutorial and the excellent AndyYan tutorial on how to do this. Thanks.

@nttuan I have a possible solution for you. Your group size is not large enough to fit all the individual partitions inside in raw format. The solution is to convert all files into sparse before running lpmake command.
This is easier said than done though. I know it's possible because I've done it before in version 1.04 and earlier but right now I'm facing this problem:

lpmake --metadata-size 65536 --super-name super --metadata-slots 2 --sparse --output ./super_fixed.bin --device super:8589934592 --group qti_dynamic_partitions:8254596872 --image system=./system_sparse.img --partition system:none:2771027928:qti_dynamic_partitions --image product=./product_sparse.img --partition product:none:1186084560:qti_dynamic_partitions --image vendor=./vendor_sparse.img --partition vendor:none:1297484384:qti_dynamic_partitions
lpmake I 04-01 00:13:56 14374 14374 builder.cpp:1012] [liblp]Partition system will resize from 0 bytes to 2771030016 bytes
lpmake I 04-01 00:13:56 14374 14374 builder.cpp:1012] [liblp]Partition product will resize from 0 bytes to 1186086912 bytes
lpmake I 04-01 00:13:56 14374 14374 builder.cpp:1012] [liblp]Partition vendor will resize from 0 bytes to 1297485824 bytes
lpmake E 04-01 00:14:03 14374 14374 images.cpp:338] [liblp]Image for partition 'system' is greater than its size (2887667712, expected 2771030016)

It don't work on my g8 android 10. It show error: 225.

 

[quanqw]

:/ $ su
# ./makesysrw.sh
-------------------------------------------------------------------------
| makeSystemRW v1.22 automated script by lebigmac @xda 2021 |
| Thanks @Kolibass @Brepro1 @munjeni @AndyYan @gabrielfrias @YOisuPU |
| without your help this script would not be possible! |
------------------------------------------------------------------------
makesysrw: Phone is not in TWRP recovery mode. Ignoring
makesysrw: Initiating procedure...

makesysrw: Unable to locate super partition on device. Ignoring
makesysrw: Partition detected: product_a @ /dev/block/sda26
makesysrw: Dumping product_a to: /data/local/tmp/makesysrw_1.22/files/nosuper/product_a.img
4194304+0 records in
4194304+0 records out
2147483648 bytes (2.0 G) copied, 29.128942 s, 70 M/s
makesysrw: Successfully dumped product_a

makesysrw: Current size of product_a.img in bytes: 2147483648
makesysrw: Current size of product_a.img in MB: 2048
makesysrw: Current size of product_a.img in 512-byte sectors: 4194304

makesysrw: Increasing filesystem size of product_a.img to 5242880 512-byte sectors...
resize2fs 1.44.4 (18-Aug-2018)
Resizing the filesystem on /data/local/tmp/makesysrw_1.22/files/nosuper/product_a.img to 655360 (4k) blocks.
The filesystem on /data/local/tmp/makesysrw_1.22/files/nosuper/product_a.img is now 655360 (4k) blocks long.

makesysrw: The filesystem of product_a.img was successfully resizedmakesysrw: Removing 'shared_blocks feature' of product_a.img...
e2fsck 1.44.4 (18-Aug-2018)
makesysrw: Read-only lock of product_a.img successfully removed

makesysrw: Shrinking size of product_a.img back to minimum size...
resize2fs 1.44.4 (18-Aug-2018)
Resizing the filesystem on /data/local/tmp/makesysrw_1.22/files/nosuper/product_a.img to 472989 (4k) blocks.
The filesystem on /data/local/tmp/makesysrw_1.22/files/nosuper/product_a.img is now 472989 (4k) blocks long.

makesysrw: Current size of product_a.img in bytes: 1937362944
makesysrw: Current size of product_a.img in MB: 1847
makesysrw: Current size of product_a.img in 512-byte sectors: 3783912

========================================================================

makesysrw: Please reboot into bootloader and flash the file(s) manually
makesysrw: Partition detected: product_b @ /dev/block/sda27
makesysrw: Dumping product_b to: /data/local/tmp/makesysrw_1.22/files/nosuper/product_b.img
4194304+0 records in
4194304+0 records out
2147483648 bytes (2.0 G) copied, 27.364214 s, 75 M/s
makesysrw: Successfully dumped product_b

makesysrw: Current size of product_b.img in bytes: 2147483648
makesysrw: Current size of product_b.img in MB: 2048
makesysrw: Current size of product_b.img in 512-byte sectors: 4194304
./tools/bin/tune2fs: Bad magic number in super-block while trying to open /data/local/tmp/makesysrw_1.22/files/nosuper/product_b.img
makesysrw: Current size of product_b.img in bytes: 2147483648
makesysrw: Current size of product_b.img in MB: 2048
makesysrw: Current size of product_b.img in 512-byte sectors: 4194304

========================================================================

makesysrw: Please reboot into bootloader and flash the file(s) manually
makesysrw: Partition detected: system_a @ /dev/block/sda24
makesysrw: Dumping system_a to: /data/local/tmp/makesysrw_1.22/files/nosuper/system_a.img
7856128+0 records in
7856128+0 records out
4022337536 bytes (3.7 G) copied, 54.771102 s, 70 M/s
makesysrw: Successfully dumped system_a

makesysrw: Current size of system_a.img in bytes: 4022337536
makesysrw: Current size of system_a.img in MB: 3836
makesysrw: Current size of system_a.img in 512-byte sectors: 7856128

makesysrw: Increasing filesystem size of system_a.img to 9820160 512-byte sectors...
resize2fs 1.44.4 (18-Aug-2018)
Resizing the filesystem on /data/local/tmp/makesysrw_1.22/files/nosuper/system_a.img to 1227520 (4k) blocks.
The filesystem on /data/local/tmp/makesysrw_1.22/files/nosuper/system_a.img is now 1227520 (4k) blocks long.

makesysrw: The filesystem of system_a.img was successfully resized
makesysrw: Removing 'shared_blocks feature' of system_a.img...
e2fsck 1.44.4 (18-Aug-2018)
makesysrw: Read-only lock of system_a.img successfully removed

makesysrw: Shrinking size of system_a.img back to minimum size...
resize2fs 1.44.4 (18-Aug-2018)
Resizing the filesystem on /data/local/tmp/makesysrw_1.22/files/nosuper/system_a.img to 680479 (4k) blocks.
The filesystem on /data/local/tmp/makesysrw_1.22/files/nosuper/system_a.img is now 680479 (4k) blocks long.

makesysrw: Current size of system_a.img in bytes: 2787241984
makesysrw: Current size of system_a.img in MB: 2658
makesysrw: Current size of system_a.img in 512-byte sectors: 5443832

========================================================================

makesysrw: Please reboot into bootloader and flash the file(s) manually
makesysrw: Partition detected: system_b @ /dev/block/sda25
makesysrw: Dumping system_b to: /data/local/tmp/makesysrw_1.22/files/nosuper/system_b.img
7856128+0 records in
7856128+0 records out
4022337536 bytes (3.7 G) copied, 53.732777 s, 71 M/s
makesysrw: Successfully dumped system_b

makesysrw: Current size of system_b.img in bytes: 4022337536
makesysrw: Current size of system_b.img in MB: 3836
makesysrw: Current size of system_b.img in 512-byte sectors: 7856128

makesysrw: Increasing filesystem size of system_b.img to 9820160 512-byte sectors...
resize2fs 1.44.4 (18-Aug-2018)
Resizing the filesystem on /data/local/tmp/makesysrw_1.22/files/nosuper/system_b.img to 1227520 (4k) blocks.
The filesystem on /data/local/tmp/makesysrw_1.22/files/nosuper/system_b.img is now 1227520 (4k) blocks long.

makesysrw: The filesystem of system_b.img was successfully resized
makesysrw: Removing 'shared_blocks feature' of system_b.img...
e2fsck 1.44.4 (18-Aug-2018)
makesysrw: Read-only lock of system_b.img successfully removed

makesysrw: Shrinking size of system_b.img back to minimum size...
resize2fs 1.44.4 (18-Aug-2018)
Resizing the filesystem on /data/local/tmp/makesysrw_1.22/files/nosuper/system_b.img to 224148 (4k) blocks.
The filesystem on /data/local/tmp/makesysrw_1.22/files/nosuper/system_b.img is now 224148 (4k) blocks long.

makesysrw: Current size of system_b.img in bytes: 918110208
makesysrw: Current size of system_b.img in MB: 875
makesysrw: Current size of system_b.img in 512-byte sectors: 1793184

========================================================================

makesysrw: Please reboot into bootloader and flash the file(s) manually
makesysrw: Partition detected: vendor_a @ /dev/block/sda22
makesysrw: Dumping vendor_a to: /data/local/tmp/makesysrw_1.22/files/nosuper/vendor_a.img
3481600+0 records in
3481600+0 records out
1782579200 bytes (1.6 G) copied, 23.576392 s, 72 M/s
makesysrw: Successfully dumped vendor_a

makesysrw: Current size of vendor_a.img in bytes: 1782579200
makesysrw: Current size of vendor_a.img in MB: 1700
makesysrw: Current size of vendor_a.img in 512-byte sectors: 3481600

makesysrw: Increasing filesystem size of vendor_a.img to 4352000 512-byte sectors...
resize2fs 1.44.4 (18-Aug-2018)
Resizing the filesystem on /data/local/tmp/makesysrw_1.22/files/nosuper/vendor_a.img to 544000 (4k) blocks.
The filesystem on /data/local/tmp/makesysrw_1.22/files/nosuper/vendor_a.img is now 544000 (4k) blocks long.

makesysrw: The filesystem of vendor_a.img was successfully resized
makesysrw: Removing 'shared_blocks feature' of vendor_a.img...
e2fsck 1.44.4 (18-Aug-2018)
makesysrw: There was a problem removing the read-only lock of vendor_a.img
1|:/data/local/tmp/makesysrw_1.22 #

Can you please post screenshots and a copy of the lpdump.txt and the myargs.txt files in the folder. Also, do you have TWRP or did you flash it through fastboot. Thanks!

I run it via terminal.

 

[lebigmac]

I've already told you several times that you don't need to convert to sparse, because lpmake will still write a raw image to super.img.
Also, why are you merging the super section into a file? It takes time and a lot of space, pull the images directly from the super section.

@kory-vadim you are absolutely right. Lpmake will automatically convert from sparse to raw before writing new super_fixed.bin so there is no point in using img2simg before running lpmake. I can confirm this.

The reason why I am dumping original super partition to image file on local storage is for backup purposes before new super_fixed.bin is flashed irreversibly to block device. Feel free to deactivate the dd function if you want

@quanqw thanks for your log. It's looking good. Apparently system_a.img and system_b.img have been successfully patched. Did you try flashing them yet in fastboot?
Please make a backup of the original files first.

For flashing you can do

adb pull /data/local/tmp/makesysrw_1.22/files/nosuper
adb reboot bootloader
fastboot flash system_a ./system_a.img
fastboot flash system_b ./system_b.img

 

[quanqw]

@quanqw thanks for your log. It's looking good. Apparently system_a.img and system_b.img have been successfully patched. Did you try flashing them yet in fastboot?
Please make a backup of the original files first. For some reason my script forgot to backup your original files.

You can make backup like this
dd if=/dev/block/sda25 of=./system_b_original.img

This is my error.

makesysrw: The filesystem of vendor_a.img was successfully resized

makesysrw: Removing 'shared_blocks feature' of vendor_a.img...

e2fsck 1.44.4 (18-Aug-2018)

makesysrw: There was a problem removing the read-only lock of vendor_a.img

 

[lebigmac]

@quanqw In that case we must try to figure out why e2fsck command failed for vendor_a.img
Can you run the command manually?
e2fsck -y -E unshare_blocks ./vendor_a.img

 

[kpykpy]

failed create super_fixed.img
free space 230GB
adb shell "ls -Alg /dev/block/by-name | grep 'super'"
lrwxrwxrwx 1 root 16 1970-01-17 12:45 super -> /dev/block/sda19

 

[Rahamatulla]

Working in REDMI K30 Device

 

[Vishal_SG]

Great! Partitions are rw now.
My device is POCO X2 and i can confirm its working . Tried both A10 and A11. thank you all for your hard work

 

[Vishal_SG]

Any downside of this? impact on performance or anything?

 

[lebigmac]

@lebigmac has made more progress than anybody and should be commended for his genius.

Thanks for your compliments

Hopefully soon I can offer support for all devices. It's not easy but I might have found a possible solution thanks to very helpful feedback by @kpykpy

 

[RavenRein]

Thanks a lot for this, finally i can get rid unwanted apps.

 

[YasuHamed]

is there a way to WIPE super partitions while flashing cusom roms?
i have SURYA (POCO NFC)

 

[lebigmac]

is there a way to WIPE super partitions while flashing cusom roms?
i have SURYA (POCO NFC)

It could be possible with fastboot erase super
but I've never done this before and therefore cannot recommend it

Thanks a lot for this, finally i can get rid unwanted apps.

You're welcome. Did it work on your device?

Any downside of this? impact on performance or anything?

Congratulations for getting it to work on your device!
No downsides to making your system r/w

Working in REDMI K30 Device

Congratulations! Is your device slot A only? Please send me your text files next to the script. Thanks!

 

[Rahamatulla]

makeSystemRW v1.22​

automated bash script by lebigmac for Android 10 and above​

Creation date: February 2021
Updated: March 2021

Requirements:

• STOCK Android 10 or newer (custom ROM should already be read-write!)
• Custom recovery is recommended but no longer required in latest version
• at least 20 GB free space on phone for dumping data

Description:

A script for all Android power users that wish to make their read-only Android 10+ system read-write-able again to remove bloatware and make more thorough customizations to their device.​

In a nutshell this is what the script is doing:

• dumps your existing super OR your system / product / vendor partitions depending on whether or not you have super partition
• extracts embedded read-only partitions (system, vendor, product...) from super if applicable
• makes these partitions read-write-able
• joins everything back together to new super.img OR NOT depending on whether or not you have super partition
• flashes read-write-able images back to device using the super fast Kolibass technique (only in recovery mode)

User data is not affected.

Installation:

Installation of the script has never been this easy!​

Download the flashable zip below, do NOT enable zip signature verification and simply install it in your custom recovery (WORKS IN BOTH TWRP AND ORANGEFOX!)​

The installer binary will auto-detect whether or not your device has a super partition and launch the script accordingly with the proper command line arguments.​

Flashable zip custom usage:

You can set these custom installation arguments in the included config.ini file.​

Simply extract the flashable.zip and modify the makesysrw_*VERSION*/config.ini file and make your adjustments. Then compress the makesysrw_*VERSION* and META-INF folders again as a new .zip and install it.​

​

First line of config.ini contains the script arguments for those WITHOUT super partition.​

By default this line is completely empty (no space).​

​

Second line of config.ini contains the script arguments for those WITH super partition.​

For example if you already dumped your super_original and want to skip that process next time you install the .zip then put this in line #2 of config.ini :​

 in=./files/super/super_original.bin size=100

​

Remember if you decide to use custom arguments in config.ini then the first character should always be an empty space. If no arguments are used such as by default in line #1 (no super) then the line should be completely empty, no space, nothing.​

Script usage:

If you've got no super partition then simply call the script with no arguments from the shell.​

If you've got a super partition I would recommend using the optional size=100 parameter as well to give some extra free space (in MB) to each partition.​

The script can be run both inside custom recovery and inside Android operating system. If you run it in Android you will need to fastboot flash the patched images manually!​

​

Optional arguments: (replace x with your custom value)

• in=x : *THIS IS IGNORED IF YOU HAVE NO SUPER PARTITION*
  With this flag you can specify an existing super image as input and skip the entire dumping of the super image process. Here you can use the super_original.bin which you dumped earlier with makesysrw or the official unsparsed super.img from your downloaded firmware. (unsparse with simg2img)
  If omitted, makesysrw will dump super image from phone to ./files/super/super_original.bin
  (path is relative to the script)
• out=x : *THIS IS IGNORED IF YOU HAVE NO SUPER PARTITION*
  With this argument you can specify the output path of the new patched super file.
  If omitted, default output value is ./files/super/super_fixed.bin
• size=x : *ONLY RECOMMENDED IF YOU HAVE SUPER PARTITION*
  With this parameter you can specify the extra free space (in megabytes) that will be added to each partition.
  If omitted, default extra size is 0 (shrink to minimum)

Examples:

# Run this command *IF YOU HAVE NO SUPER PARTITION*
./makesysrw.sh

# Run this command if you're first time user *AND YOU HAVE SUPER PARTITION*
# Specify the extra free space in megabytes for each partition:
./makesysrw.sh size=100

# Plug an existing super image into the script like this *ONLY IF YOU HAVE SUPER PARTITION*
./makesysrw.sh in=./files/super/super_original.bin size=100

# Specify both the input file as well as the output destination *ONLY IF YOU HAVE SUPER PARTITION*
./makesysrw.sh in=./files/super/super_original.bin out=./custom/path/super_fixed.bin size=100

To check whether or not you've got a super partition on your device you can run this command:

adb shell "ls -Alg /dev/block/by-name | grep 'super'"

Troubleshooting:

If you get error 255 when trying to install flashable zip then try to install it manually.​

Make sure the script folder was correctly extracted to:​

/data/local/tmp/makesysrw_*VERSION*​

If you can't run the script try making the file executable like this: chmod +x ./makesysrw.sh​

If you still can't get it to work run which sh in your shell and replace the shebang in the first line of the script with the output of that command. Don't remove the first two #! symbols though. Then save the file and try again.​

Make sure you have full read write access to the /data/local/tmp directory and that the containing files are not encrypted in custom recovery!​

NOTE:

I did not come up with all this by myself. After searching for a solution for countless days without success, going even as far as learning hex editing - I coincidentally came across a couple of very interesting threads burried deep inside the new forum interface where this method has been described by various enthousiasts (links can be found in the credits section below). So I take absolutely no credit for the underlying core mechanisms of the script. I'm only the amateur who put it all together into a compact script so that everybody can enjoy an Android system that's read-write-able again. Just like it used to be in Android 9 or earlier. Before this annoying 'shared_blocks feature' was implemented.​

Credits:

Huge thanks to @Kolibass for allowing me to use his partition tools for Android. Without your tools this script would not work on the Android platform! This genius also showed me how to flash a 8GB file to my partition in just under 30 seconds! Much faster than fastboot! I still can't believe it!​

Big thanks to @Brepro1 for allowing me to basically copy his awesome tutorial and make it into a script. Without your tutorial guiding me I couldn't have created this script.​

Thanks @AndyYan your great tutorial also helped me a lot for automating the script especially the lpdump part.​

Also big thanks @munjeni for allowing me to use his superunpack tool in the previous version. It helped me to understand how these super images work.​

Thanks @bynarie for making available his otatools package! A part of it was bundled with the previous version which helped me to create this version.​

More thanks @gabrielfrias for his helpful comment​

Thanks @YOisuPU and of course @topjohnwu for discovering the 'shared_blocks feature'​

Disclaimer:

This is open source software and is provided as is without any kind of warranty or support whatsoever. By using and viewing this software you agree to the following terms:​

Under no circumstances shall the author be held responsible for any damages or negative consequences that may arrise from the (inappropriate) use of this software.​

All responsibility and liability lies with the end-user. You hereby agree not to abuse this software for illegal purposes. Use this software at your own risk!​

Please feel free to improve this script as you see fit (as long as you don't add anything malicious).
And make sure to post your feedback, suggestions and improvements in the official thread right here.
If you decide to use my work in your project please send me a message and include a link to this official thread in your project. Thank you.

Download v1.22
current status: experimental/semi-stable
Seems to work well with slot A only devices
Please click my like button below if you like my work! Thanks!

Confirmed working on these devices :
Xiaomi Poco X3 NFC
Xiaomi Redmi Note 9 Pro joyeuse - Android 10
Xiaomi Mi 10 T Lite - Android 11
Xiaomi Mi 10 T lite - Android 11 - TWRP
Xiaomi Mi 10 - Android 11
Xiaomi Mi Note 10 Lite - Android 11 - OrangeFox
Xiaomi Redmi 9T - Android 11 - TWRP

Asus Rog Phone 3 - Android 10 - TWRP
​

Working in Poco X2 (Redmi K30) miui eu stable Android 10

 

[Rahamatulla]

Great! Partitions are rw now.
My device is POCO X2 and i can confirm its working . Tried both A10 and A11. thank you all for your hard work

But we lose 10gb storage.... If we erase super from fastboot will the system restore to read only? will it effect /data/media?