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

Status
Not open for further replies.
Search This thread

tids2k

Senior Member
Apr 21, 2009
2,740
955
Sydney
Google Pixel 6 Pro
hi @lebigmac im back. could you please clarify "
systemrw: Congratulations! Your image(s) should now have R/W capability
systemrw: Please reboot into bootloader and flash the file(s) manually "

Which file do we need to flash in bootloader, the fixed_super.img ? If so what are the commands ?

Tried on crDroid 8.2 on Pixel 6 Pro on Android 12.

Could run " mount -o remount, rw / " - does not confirm device is read-only, however when copying files for eg. hosts to /etc it failed . any suggestions ?

C:\Users\ADAM>adb push hosts /etc/
adb: error: failed to copy 'hosts' to '/etc/hosts': remote couldn't create file: Permission denied
hosts: 1 file pushed, 0 skipped. 6.3 MB/s (3254933 bytes in 0.491s) fails too.
 

lebigmac

Account currently disabled
Jan 31, 2017
1,342
995
hi @lebigmac im back. could you please clarify "
systemrw: Congratulations! Your image(s) should now have R/W capability
systemrw: Please reboot into bootloader and flash the file(s) manually "

Which file do we need to flash in bootloader, the fixed_super.img ? If so what are the commands ?

Tried on crDroid 8.2 on Pixel 6 Pro on Android 12.

Could run " mount -o remount, rw / " - does not confirm device is read-only, however when copying files for eg. hosts to /etc it failed . any suggestions ?

C:\Users\ADAM>adb push hosts /etc/
adb: error: failed to copy 'hosts' to '/etc/hosts': remote couldn't create file: Permission denied
hosts: 1 file pushed, 0 skipped. 6.3 MB/s (3254933 bytes in 0.491s) fails too.
Welcome back @tids2k
You can flash super_fixed.bin like this from your computer:
Bash:
adb pull /data/local/tmp/systemrw_1.32/img/super_fixed.bin
adb reboot bootloader
fastboot flash super super_fixed.bin

Good luck! (y)
 
Last edited:

Denny@83

Member
Sep 14, 2021
20
5
41
italy
Hi. Sure why not. Did you check the manual installation instructions @ front page yet?
Good luck (y)




Hi. Did you try size=0 yet? Then you can always delete useless bloatware to free up some space that way ;)(y)
Don't worry next upcoming version already has working auto-resize() feature that should fix this issue (y)

You're not supposed to flash the repair.zip file. Extract it on your Linux PC and launch the repair script that's inside in terminal as root. Good luck(y)




Hi. Thanks for your feedback. Did you try yet the repair script on a Linux machine while phone is plugged in? Good luck!(y)
What result do you get from this command?
Bash:
adb shell
su
getprop ro.build.version.sdk




Hi. Sorry this tool is arm64-v8a only at the moment but if you want I can upload the armeabi-v7a tools with next version! (y)

You can check your ABI version like this:
Bash:
adb shell
su
getprop | grep abi




Hi. Did you try manually remounting your partitions yet? Like this:
Good luck! (y)
working-jpg.5525671





Hi. Are you Motorola user? Hopefully next upcoming version will be less error 73 prone and offer better compatibility with various Motorola devices out there ;)(y)
Wish me luck (y)




Hi. Did you try size=0 yet? Then you can always delete useless bloatware to free up some space that way ;)(y)
Don't worry next upcoming version already has working auto-resize() feature that should fix this issue (y)




Hi. That's way too much! On Xiaomi devices you can usually go up to 500 MB. On OnePlus devices I would recommend size=0 (shrink to minimum).
Don't worry next upcoming version already has working auto-resize() feature that should fix this issue ;)(y)
Hi Lebigmac
I manually remounted partitions as you suggested, it works, I found I installed nano in system/etc

thanks
 

Attachments

  • Screenshot_20220221-151808.jpg
    Screenshot_20220221-151808.jpg
    193.6 KB · Views: 73
  • Cattura1.PNG
    Cattura1.PNG
    30.6 KB · Views: 2,082
Last edited:
  • Love
Reactions: lebigmac
Jun 30, 2018
45
7
Hello just taking my time here to say a HUGE THANKS to all the people involved in this project! Everything went as smoothly as possible with the flashable zip file(w/adjustment to available size). IDEK what would I do to get into this trouble in googling a risk free solution to just replace a .ttf in system lol.

Device: Poco F3
ROM: Xiaomi.eu 12.5.19 stable(Android 11)
Recovery: Official Poco F3 TWRP

Again I cannot thank you guys enough(esp in the modding community) for your hardwork and dedication to make the modded android experience as best as possible!
(Note: There're some mounting errors displayed in TWRP right at the very end of the process but I think it's just negligible because my device booted just fine with the correct free size space and rw root lol)
Log files: mylog.txt & lpdump.txt
 
  • Love
Reactions: lebigmac

dna1982

Senior Member
Mar 12, 2011
121
47
systemrw: Congratulations! Your image(s) should now have R/W capability
systemrw: Deleting /data/local/tmp/systemrw_1.32/img/super_fixed.bin to free up some space
systemrw: Please reboot to system...

Worked like a charm on Oneplus 9 Pro with OOS 11.2.10.10 (Android 11) and twrp-3.6.0.
Kudos to OP.
 

Attachments

  • log.rar
    4.3 KB · Views: 11
  • Love
Reactions: lebigmac

Denny@83

Member
Sep 14, 2021
20
5
41
italy
Hi Lebigmac
I manually remounted partitions as you suggested, it works, I found I installed nano in system/etc

thanks
Hi Lebigmac
I edit my previous post... I were wrong, the script doesn't work properly.
Nano is installed systemlessly through magisk module, and also modifications in hosts file are done systemlessly through adaway....
I attach other screenshots:

system partition is not rw, I can't write any file....
I created a text file in vendor partition, you see in screenshots; but I can't edit file, I can't write nothing, it remains empty. While saving modifications, it says I haven't enough space....
the same things happen in product partition..

Now restarted the phone...bootloop..... try to flash my super backup...
 

Attachments

  • Cattura.PNG
    Cattura.PNG
    11.7 KB · Views: 30
  • Screenshot_20220224-115348.jpg
    Screenshot_20220224-115348.jpg
    94.6 KB · Views: 30
  • Screenshot_20220224-115421.jpg
    Screenshot_20220224-115421.jpg
    151.2 KB · Views: 30

lebigmac

Account currently disabled
Jan 31, 2017
1,342
995
@Denny@83 What size parameter did you use? size=0 ? Try run script again with size=50 parameter

Can you do this?

working-jpg.5525671


According to your screenshot below your / (/system), /product and /vendor subpartitions are rw! Congratulations! :love:(y)
I think you just need to create more empty space that's all ;) Don't worry brand new upcoming version which is just around the corner has working auto-resize feature already implemented ;)(y)

cattura1-png.5542849
 
Last edited:
  • Like
Reactions: Jason Hugg

vyaskd

Senior Member
Jan 11, 2011
335
19
Google Pixel 6 Pro
Google Pixel 7
If the script works on your device please send me your log files from this folder:
/data/local/tmp/systemrw_1.32/log/

And please write your phone model - Android version - firmware version

Then I can add you to the list of successful devices and it will be helpful for further development. Thank you!(y)
Flashed on my OnePlus 9, working system rw, thnx a lot for ur work. Can u tell me what problems I may face if factory reset my phone?
 

Noob developer01

New member
Feb 21, 2022
3
0
WOW! Finally it worked! Big thank to @lebigmac who really helped me in private chat!


First of all, my device:
Xiaomi Mi 10T Lite, MIUI V.12.0.1.0 (Android 11)

I was managed to run this script with following commands :

cd /data/local/tmp/makesysrw_1.15 ./makesysrw.sh in=./files/super/super_original.bin size=100

After this, it worked without problems.

I have orangefox recovery installed, but I used to fastboot in TWRP Recovery, cause I faced some problems with orangefox.
(for this, just download your TWRP, connect your phone in fastboot and run:
"fastboot boot .\twrp...........img"

After the script has finished, my phone rebooted successfully. I opened root explorer and created a test folder in /system. The program asked me to mount /system as read write (mount -o remount,rw /) and e voila, remount sucessfully and write rights worked!

Thanks man
How to managed script??
Reply plzz🙂
 

Denny@83

Member
Sep 14, 2021
20
5
41
italy
@Denny@83 What size parameter did you use? size=0 ? Try run script again with size=50 parameter

Can you do this?

working-jpg.5525671


According to your screenshot below your / (/system), /product and /vendor subpartitions are rw! Congratulations! :love:(y)
I think you just need to create more empty space that's all ;) Don't worry brand new upcoming version which is just around the corner has working auto-resize feature already implemented ;)(y)

cattura1-png.5542849
Hi Lebigmac, I did exactly what you said; when I launched the script I used size = 15...
I don't think it' only a problem of space, because when I tried to create a file in /system, it said there wasn't enough space - while in vendor and product i could create an empty file.
However I attach the logs of the script; I'm on slot B but in log I read current slot is 1...
Another question: super original is 10 Gb, while super fixed in 6 Gb.
According to you, the cause of the bootloop I had after creating an empty file under vendor partitions is due to lack of space in super partition or a security feature of the phone ?
I'll wait for the new script before try doing another attempt (there will be the possibility to write images on external sdcard instead of internal storage?)---Thanks for your Job!!!
 

Attachments

  • mylog.txt
    9.7 KB · Views: 18
  • Like
Reactions: lebigmac
Status
Not open for further replies.

Top Liked Posts

  • There are no posts matching your filters.
  • 243
    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, F2FS-2-RW, EROFS-2-EXT4-CONVERTER, F2FS-2-EXT4-CONVERTER, Super Resizer/Flasher, SYSTEM-RW / PRODUCT-RW / VENDOR-RW / ODM-RW, root enhancer, real root, FULL ROOT, RW MULTI TOOL and many more aliases!
    (NOTE: Full F2FS-RW support coming in 1. quartal 2023 ! Get your Samsungs ready!)



    The prophecy has finally been fulfilled.
    Making Android ten years younger!
    Inspiring a whole generation of talented developers and empowering the open source community.
    The Pandora's Box has been fully unlocked at last!
    The genie has been unleashed from within the bottle!
    Sesame! Open up now!
    Let the Olympic Android System Modding Games (OASMG) begin!
    The power is now in YOUR hands! And don't forget:
    With great power comes great responsibility!


    Creation date: February 2021
    Updated: January 2023

    Requirements:
    • rooted STOCK Android 10 or newer
    • at least 10+ 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.
    Script only modifies super and vbmeta partitions. /data partition is not affected. It's only used for dumping data and for storing script files.
    In a nutshell this is what the script is doing:
    • dumps your existing super partition
    • extracts embedded read-only sub-partitions (system, system_ext, odm, vendor, product...) from specified super image
    • makes these sub-partitions read/write-able using the one and only original MakeRW/ro2rw algorithm
    • joins everything back together to new super.img
    • flashes read/write-able patched super image back to device using the super fast Kolibass technique (only available in recovery mode)

    NOTE:
    • The script can be run both inside custom recovery and inside Android operating system.
      If you run script in Android mode you will need to fastboot flash the patched image(s) manually!
    • To check whether or not the script worked correctly you can run this code:
      Bash:
      adb shell
      su
      mount -o remount,rw /
      mount -o remount,rw /odm
      mount -o remount,rw /product
      mount -o remount,rw /system_ext
      mount -o remount,rw /vendor
      mount | grep dm- | head -5
    Manual installation:
    • Extract flashable.zip and copy sysrw_*VERSION* folder into /data/local/tmp/
    • run this command to make the script executable:
      chmod +x /data/local/tmp/sysrw_*VERSION*/sysrw
    Automatic 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 TWRP, OrangeFox and PBRP!)
    The update binary will auto-detect the arguments in config.ini and launch the script accordingly

    Flashable zip custom usage:
    You can easily modify the custom script execution arguments in the included config.ini file. Simply extract the flashable.zip, edit the included config.ini file with notepad and then save the file. Next compress the sysrw_*VERSION* and META-INF folders again as a new flashable .zip and install it in recovery. Have fun playing around with your config.ini :D(y)

    Script usage:
    Simply execute the program from the terminal shell with or without custom arguments
    Optional script arguments:
    Replace x with your custom value
    • in=x
      Specify existing super image as input [OPTIONAL]
      Omitting this parameter is equivalent to using in=@auto which is equivalent to using your super block device as input
    • out=x
      Specify patched super image output file path [OPTIONAL]
      Omitting this parameter is equivalent to using out=@auto
      and the patched super image will be saved as ./img/super_patched.bin by default
    • size=x
      Specify the extra free space (in megabytes) to be added to each sub-partition of super.img [OPTIONAL]
      Omitting this parameter is equivalent to using size=@auto which will activate the auto-resize feature
    • -r
      Specify whether or not the patched super image should be output in raw file format [OPTIONAL]
      Omitting this parameter will create a sparse patched super image by default

    Usage examples:
    Bash:
    adb shell
    su
    cd /data/local/tmp/sysrw_1.33
    chmod +x ./sysrw
    
    #  Run program with default settings [RECOMMENDED]
    ./sysrw
    
    # Specify existing super image as input [OPTIONAL]
    ./sysrw in=./img/super_original.img
    
    # Specify patched super image output file path [OPTIONAL]
    ./sysrw out=./img/super_patched_new.img
    
    # Specify the extra free space (in megabytes) to be added to each sub-partition of super.img [OPTIONAL]
    ./sysrw size=15
    
    # Specify whether or not the patched super image should be output in raw file format [OPTIONAL]
    ./sysrw -r
    
    # EXPERT EXAMPLE (Warning! This command could potentially corrupt your system. Only use at your own risk in recovery mode!)
    ./sysrw in=img/super_original.bin out=`realpath /dev/block/by-name/super` -r

    Uninstallation:
    • To free up space and keep script as well as r/w capability you can simply delete /img subfolder at /data/local/tmp/sysrw_*VERSION*/img
    • To delete script and keep r/w capability you can simply delete whole script folder at /data/local/tmp/sysrw_*VERSION*
    • To undo all changes performed by the script you can simply reflash original stock read-only super image and re-enable dm-verity and verification either through adb/fastboot or with the included avbctl binary.

    Troubleshooting:
    If you can't get this script to work on your device check out the brand new sophisticated superrepack tool by @munjeni
    If you get any errors from the update-binary in your custom recovery during installation of the flashable .zip then please send me this log file /tmp/recovery.log
    and a screenshot of your error. Thanks! (y)
    Make sure the script folder was correctly extracted to:
    /data/local/tmp/sysrw_*VERSION*
    If you can't run the script try making the file executable like this: chmod +x ./sysrw
    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've got full read / write access to the /data/local/tmp directory and that the containing files are not encrypted in custom recovery!
    If you get a bootloop after successfully creating and flashing super_patched.bin then that's probably because you didn't properly disable your dm-verity and verification.
    To undo any bootloop simply re-flash original stock read-only super image and re-enable dm-verity and verification with the included avbctl binary or through adb/fastboot. Those are the only changes performed by the script. If you have any more questions just ask in this thread. Good luck!

    About:
    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 accidentally came across a couple of very interesting threads burried deep inside the new forum interface where this method has been described by various rw enthousiasts (links can be found in the credits section below). Therefore most credit goes to these rw enthousiasts. 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 these annoying 'shared_blocks' and 'EROFS' read-only features were implemented.

    Credits:
    Huge thanks to @Brepro1 for allowing me to use his awesome tutorial and make it into a script. Without your tutorial guiding me I couldn't have created this script.
    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!
    Big thanks @munjeni for allowing me to use his amazing superunpack V1 tool in the initial version. It helped me to understand how these super images work.
    Thanks @AndyYan your great tutorial also helped me a lot for automating the script especially the lpdump part.
    Thanks @bynarie for making available his otatools package! A part of it was bundled with the initial version which helped me to create this universal version. It's still part of the troubleshooting repair script to fix error 73.
    Thanks @HemanthJabalpuri for assisting me in optimizing the underlying algorithm!

    Disclaimer:
    #Disclaimer v3.0​
    This open source software 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 that may occur from the (inappropriate) use of this software (or parts thereof).
    • All responsibility, liability and risk lies with the end-user. You hereby agree not to abuse this software for illegal purposes.
    • Please don't steal, hack, crack, mod, hex-edit, decompile, rebrand and / or abuse this software or parts thereof. Thank you!
    • This software can be re-uploaded to 3rd party websites indefinitely as long as the software itself (or any parts thereof) were not modified by unauthorized 3rd parties without the original author's prior knowledge and explicit written consent
    • This software (or parts thereof) were provided for free only for non-commercial, educational, personal, legal purposes
    • To use this software (or parts thereof) for commercial purposes, please rent a commercial usage license
      Thank you very much for your support! Thanks to your amazing support I can continue working on this project and other interesting projects like this. :D(y)

    Enjoy debloating and customizing your fully read/write-able next-gen Android device! :love:(y)

    Please post your feedback, suggestions and your Olympic Android System Mods (OASMG) @ the official SystemRW / SuperRW feat. MakeRW / ro2rw by lebigmac links below. Thanks :D(y)

    https://xdaforums.com/t/universal-s...tition-converter-resizer-by-lebigmac.4247311/

    https://xdaforums.com/t/closed-the-...n-converter-erofs-rw-ext4-rw-f2fs-rw.4536821/


    v1-31d_01-jpg.5309953
    v1-31d_03-jpg.5309957


    1-jpg.5235933


    working-jpg.5525671


    Confirmed working on these devices:


    Download

    current status: experimental


    If you like this project and want to support further development of it & the creation of more amazing projects like this then please feel free to donate to the original developer lebigmac by clicking the button below. Thanks! Your support is very much appreciated!

    Donate
    25
    Thread Closed

    Hello everyone

    As helpful as @lebigmac may be, no one – not even us – is above XDA's Forum Rules. Our work as moderators usually remains in the background but it felt necessary to provide some transparency here. After consulting our team I have decided to ban the OP of this thread for three months and it will remain locked until OP requests to open it back up after the ban expires. For some of you this will come as a complete surprise and may seem unfair but I would like to stress that we have invested a massive amount of energy and a mountain of patience to come to a resolve with lebigmac. Several moderators were involved. Despite our many efforts, (s)he persisted to openly accuse people of plagiarism, inciting conflict, call out the people involved and communicated in a very condescending and demeaning way.
    We of course regret this course of action. Developers and development is everything to us but boundaries must be respected. After several earlier time-outs we had no other option but to proceed this way. We're hoping this will bring back some peace in this feud as well. With so much going on in the world we really don't need opposing developer parties. Open source is about cooperation and improving existing code, not about bitter fights over protecting your own code, which is based on the work of others anyway. One questionable screenshot aside, there hasn't been any viable proof of plagiarism provided to us related to this project.

    Thank you all for your understanding and as always we remain available to answer your questions and concerns via PM. Have an amazing day!

    Kind regards
    Timmy
    Senior Moderator
    17
    If the script works on your device please send me your log files from this folder:
    /data/local/tmp/systemrw_1.32/log/

    And please write your phone model - Android version - firmware version

    Then I can add you to the list of successful devices and it will be helpful for further development. Thank you!(y)
    17
    Allow me to add some more information to above post of my teammate @Timmmmaaahh!

    The account of the author of this thread has been permanently suspended. In your own interest, I ask everybody not to promote a banned user or his website, blog, work etc. on XDA. Thanks very much for your cooperation.

    Regards
    Oswald Boelcke
    Senior Moderator
    10
    Okay I know you guys have been waiting a long time... Thanks for your patience, loyalty, support and your interest in this amazing project for the past year! Unfortunately there's lots of dubious copycats floating around by now. Remember you saw it here first ;)(y)
    The one and only, the original
    SystemRW / SuperRW featuring MakeRW by lebigmac
    This month new version should be ready :D(y)
    I'm working on it hard 🛠️⚙️⛏️🔧✂️🔨
    Hopefully we can start beta testing in 2nd half of April May June July August September October and then it should be ready for final release :love:
    I'm so excited!


    This is awesome! Unfortunately, it doesn't support Android 12 yet : ( .

    The new version has support for Android 12 and beyond! :ROFLMAO:

    Bash:
    sdkCheck(){
        sdkVersion=`getprop ro.build.version.sdk`
        if [ $sdkVersion -lt 29 ]; then
            printf "$app: Please install Android 10 or newer and try again\n\n" && exit 1
        else
            android=$(($sdkVersion - 19))
        fi
        printf "$app: Current Android version: %s\n" $android
    }