• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!
Search This thread

120503

Member
May 3, 2012
6
1
Works on Redmi Note 9 Pro(gauguin, China Edition, 12.0.11.0.QJSCNXM, Miui 12, Android 10. There is a super partition). Thanks so much
 
Last edited:
  • Love
Reactions: lebigmac

chintoocool

Member
Aug 4, 2014
26
7
@thelavip @BlazingKahn35 @nttuan @kpykpy @harpreet.s @m3nty @f1^ter @ITGrouch @Articul8Madness

I noticed when running the script manually from the shell, lpmake will actually work as expected.

So I urge anyone with lpmake error creating super_fixed.bin to launch the script manually like this to find out more about what exactly is causing lpmake to fail. Thank you.

Bash:
cd /data/local/tmp/makesysrw_1.28
./makesysrw.sh size=50 in=./files/super/super_original.bin

Or if you don't want to launch entire script you can simply just launch lpmake manually like this using the lpmake arguments from myargs.txt:
Bash:
cd /data/local/tmp/makesysrw_1.28
./tools/bin/lpmake `cat ./myargs.txt`
 

Attachments

  • Screenshot_20210414-095810.jpg
    Screenshot_20210414-095810.jpg
    692.1 KB · Views: 79

Xiaoleng

Member
Apr 14, 2021
9
4
Not working on my Xperia 10 II (XQ-AU52); factory-shipped Android 10 with super; shows "repacking super failed" tried both in twrp and in terminal emulator; logs attached below
 

chintoocool

Member
Aug 4, 2014
26
7
@thelavip @BlazingKahn35 @nttuan @kpykpy @harpreet.s @m3nty @f1^ter @ITGrouch @Articul8Madness

I noticed when running the script manually from the shell, lpmake will actually work as expected and show the actual error.

So I urge anyone with lpmake error creating super_fixed.bin to launch the script manually like this to find out more about what exactly is causing lpmake to fail. Thank you.

Bash:
adb shell

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

Or if you don't want to launch entire script you can simply just launch lpmake manually like this using the lpmake arguments from myargs.txt:
Bash:
adb shell

cd /data/local/tmp/makesysrw_1.28
./tools/bin/lpmake `cat ./myargs.txt`
 

Attachments

  • Screenshot_20210414-095810.jpg
    Screenshot_20210414-095810.jpg
    692.1 KB · Views: 42
  • lpdump.txt
    2.7 KB · Views: 10
  • myargs.txt
    184 bytes · Views: 11
  • mylog.txt
    1.1 KB · Views: 8

f1^ter

Member
Jan 8, 2016
47
41
32
Nadym
Sony Xperia 1 II
@thelavip @BlazingKahn35 @nttuan @kpykpy @harpreet.s @m3nty @f1^ter @ITGrouch @Articul8Madness @Xiaoleng

Please try the new v1.29
I have fixed the bug where lpmake produces no output @ end of script.
Hopefully this will give more info about what's wrong with slot A/B devices.
After version 1.29, everything worked out! BUT, after turning on the device, the system does not have a boot. After the logo, restart and so on again. Is there any way to restore the original .bin? I attach logs.
 

Attachments

  • lpdump.txt
    2.3 KB · Views: 9
  • mylog.txt
    8.8 KB · Views: 13
  • Wow
Reactions: lebigmac

lebigmac

Senior Member
Jan 31, 2017
929
553
To restore original super image you can do

Code:
adb pull /data/local/tmp/makesysrw_1.29/files/super/super_original.bin

adb reboot bootloader

fastboot flash super super_original.bin

Or you can flash it back from recovery

To those that get bootloop :
Did you successfully disable dm-verity and verification? My script attempt to do this automatically when launched from recovery using these 2 commands:

Code:
avbctl disable-verification
avbctl disable-verity

If you have no custom recovery or your recovery have no avbctl binary you can try to flash empty vbmeta file like this (you can find empty vbmeta file here at XDA forum)

Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
 
Last edited:
  • Like
Reactions: f1^ter
Confirmed working on my moto g power (sofia) XT2041-4ss (Super Partition)

Confirmed working on my moto g7 (river) XT1961-1 (No Super)

Nice work!! Keep it up🤪
The reason why the script worked for you is that the Moto G7 Power was on Android 9 Pie, and R/W unlocked as soon as you get root. No probs there.
Many variants of Moto G Power also came with Android Pie out the box, one of the last. That could be the reason why.
Native Android 10 Moto isn't that simple.
 

gessler2244

Member
Nov 5, 2016
24
6
Xiaomi Mi Max 3
I installed the zip 1.29, all went fine except these two errors in log:
There was an error of removing the read-only lock of system.img. Ignoring
and
There was an error of removing the read-only lock of vendor.img. Ignoring
I have an Poco X3 NFC and use Arrow OS Vanilla newest build.
Any ideas what could cause that? Thanks in advance and many thanks to lebigmac for the scipt.
 

lebigmac

Senior Member
Jan 31, 2017
929
553
I installed the zip 1.29, all went fine except these two errors in log:
There was an error of removing the read-only lock of system.img. Ignoring
and
There was an error of removing the read-only lock of vendor.img. Ignoring
I have an Poco X3 NFC and use Arrow OS Vanilla newest build.
Any ideas what could cause that? Thanks in advance and many thanks to lebigmac for the scipt.

Hi gessler2244 thanks for your feedback. Could you please post your log? Thanks.
These 2 errors probably happened because there is no shared_blocks flag to remove from those files because you're using custom ROM that already has read-write capability.

Did you run the script in recovery? Was the super image still flashed properly despite these 2 errors? And did you get a bootloop at all or was it able to boot into Android system successfully?
 
Last edited:

lebigmac

Senior Member
Jan 31, 2017
929
553
@f1^ter @mrsergey
You can try to disable dm-verity and verification like this:
ALWAYS MAKE BACKUP OF ORIGINAL VBMETA FIRST!

Bash:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta_disabled.img
 
Last edited:

gessler2244

Member
Nov 5, 2016
24
6
Xiaomi Mi Max 3
I'll try this later At home, Image was flashed as far as I remember, and no bootloop,, booted fine, I run the script in twrp recovery Last version from brigudav.
 

Attachments

  • mylog.txt
    5.4 KB · Views: 12

gessler2244

Member
Nov 5, 2016
24
6
Xiaomi Mi Max 3
Flashed via fasrboot The Vbmeta Image, flashed fine, then I rebooted to recovery and run the script again, but no luck it seems, what I find strange also is in the hw info app under partitions /vendor it states : /dev/blockdm-2 fs:read-only. Is this normal, can it be changed? Thousand thanks.
 

Attachments

  • mylog.txt
    5.4 KB · Views: 11

lebigmac

Senior Member
Jan 31, 2017
929
553
Flashed via fasrboot The Vbmeta Image, flashed fine, then I rebooted to recovery and run the script again, but no luck it seems, what I find strange also is in the hw info app under partitions /vendor it states : /dev/blockdm-2 fs:read-only. Is this normal, can it be changed? Thousand thanks.

Thanks for sharing your log. It looks good. Also your phone is still booting normally into Android after flashing super_fixed.bin and even after flashing empty vbmeta. This is good sign.

Did you try the most obvious thing yet? This should work since you are using custom ROM...
Bash:
adb shell
su
mount -o remount,rw /
mount -o remount,rw /vendor
mount -o remount,rw /product

If your custom ROM cannot do this I suggest going back to stock Android and try again my script ;)
Good luck!
 
Last edited:

gessler2244

Member
Nov 5, 2016
24
6
Xiaomi Mi Max 3
Yes I tried all that, and just tried after these commandos if I can write in /vendor , this is possible, but I can´t write in /vendor/etc , and trying mount -o remount,rw /vendor/etc gives error: /vendor/etc not found in proc/mounts. Well maybe switching to any other custom is better..... But MIUI I don´t really want again. Anyway thanks a lot and script seems to work good on most devices.
 
  • Haha
Reactions: lebigmac

Top Liked Posts

  • There are no posts matching your filters.
  • 3
    i use poco m3 rom xtrv hellas....your script is rock..i remove permanently bloatware with root explorer...nice job
    Hi @masricky I'm happy you like the script. Please send me your log files from this folder. Thanks (y)
    /data/local/tmp/systemrw_1.32/log/

    Enjoy tinkering with your fully read/write-able device and make lots of backups before modding stuff! :love:(y)

    Yes it's true. I wrote this script but it wouldn't exist as such without
    Thank you to everyone who contributed positively to this project! :D(y)
    Also keep in mind script is not perfect for all devices out there yet. Rest assured I'm always working hard on next version ;)(y)
    2
    Thanks! It works flawlessly (although I had to do it manually, it's easy enough). My device is a Redmi Note 9S (curtana). If I update my device, do I need to remake the fixed super.img or should I flash the one made before the update?
    Hi @LanceLot9980. Congratulations for getting the script to work on your device! Enjoy a fully read/write-able device! :love:(y)
    If you upload your log files from script folder and a screenshot of your system mounted as r/w then I can add you to the list of successful devices on front page ;)(y)

    @LanceLot9980 yes I noticed your question but I was on the road.
    If you update OTA this will most likely restore the shared_blocks read-only feature on your super partition which means you will have to run script again if you want to go full r/w again ;)
    Thanks! It works flawlessly (although I had to do it manually, it's easy enough). My device is a Redmi Note 9S (curtana). If I update my device, do I need to remake the fixed super.img or should I flash the one made before the update?
    The flashable zip gave you error 255? Don't worry I already fixed this issue in next version ;) Hopefully I can release it soon!
    2
    hi and thank's for your work...
    I have an issue with your script, I flash it on twrp on my renoir on A11 LOS and the flash is correct but at the end got these errors messages
    failed to mount system/ext/product/vendor (invalid argument) here are the logs and the ss...

    when I try to copy a .xml on vendor partition got, no more space available and it copy a .xml but empty..
    Hello @rayman95. You're welcome. Thanks for your log files and the screenshot (y)
    Don't worry about this TWRP related error at the very end. This has nothing to do with the script. This only means you must reboot the device. That's all ;)(y)
    Failed to mount '/system_ext' (Invalid argument)
    Failed to mount '/product' (Invalid argument)
    Failed to mount '/vendor' (Invalid argument)

    According to your log it looks like everything worked as expected but I think you must run script again with larger custom size. Which custom size did you use? I can't see it in the log :(
    Hopefully I can release that new version soon. The included auto-resize feature should fix this kind of issue in next version ;)(y)



    it worked great on poco x3 pro, but vendor didn't, when I try to edit an XML located in "vendor/etc/device_features" it doesn't work, even so, thank you very much for the work.
    Hi @Revokke. You're welcome. Thanks for your feedback.
    Please feel free to send me your log files from this folder and I'll have a look at your specific issue. Thanks (y)
    /data/local/tmp/systemrw_1.32/log/

    Which MIUI version number are you using? Official stock MIUI or Xiaomi.eu ROM ?
    What do you mean it doesn't work? I just tried it on my device and it just works. I can create and delete files in this directory /vendor/etc/device_features
    Make sure you remount /vendor partition as rw before copying or deleting files.
    If you can only write empty files to /system, /product or /vendor that means you must run script again with larger custom size. Good luck! (y)
    2
    @tids2k için çok fazlaki geri bildiriminiz için teşekkür edilir. Evet, bu bootloop bekleniyordu. Sanırım bu, [2470925]@Hippie459MN[/KULLANICI]'nın birkaç gün önce genel Sony Xperia amiral gemisi yemekta aynı inatçı çekirdekli paniksi.
    gerçek betiğin bir sürüm, Almanya'da kötü durumdaki 255, motorola sürücüsündeki can sıkıcı 73 ve bu inatçı hata siniri gibi bu sorunlardan bazılarını çözecektir. Tam Android 12 olur de harika olurdu.




    Merhaba [KULLANICI=11226285]@kafeinsiz[/KULLANICI] geri bildiriminiz için teşekkürler! Senaryomun Xiaomi azda çok memnunum. Tebrikler! Okunabilir/yazılabilir bir ürünlerden çıkarılabilir!:Aşk :()

    mevcut özel boyutlar=25 (MB) mi kullandınız?

    Android 11 çalıştırdığınızdan emin misiniz? Günlüğünüzde söylüyor diyor ki:
    Evet kesinlikle A11. A10 bir hata nedeniyle burada görünüyor.
    1
    Can you please look into my logs. It shows successful but not got rw capabilities. In twrp after last line of mylog.txt there were two line warning regarding something Mount related
  • 110
    If you can't get this script to work on your device check out the brand new sophisticated superrepack tool by @munjeni


    logo_large.jpg

    SystemRW© v1.32 by lebigmac

    Creation date: February 2021
    Updated: August 2021

    Requirements:
    • rooted STOCK Android 10 or newer (custom ROM should already be R/W!)
    • 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 only used for dumping data and for storing script files
    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've got 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've got super partition
    • flashes read/write-able images back to device using the super fast Kolibass technique (only in recovery mode)

    NOTE:
    • Extract BUNDLE.zip (the included sysrw_repair.zip is only for fixing error 73!)
    • Before launching script make sure you've got full read/write access to the /data partition by first decrypting and then mounting /data partition as R/W!
    • Before running this experimental software on your device it is recommended to make a full backup of your device (just in case you are unlucky enough to end up in an irreversible bootloop)
    • 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 you've got a super partition on your device you can run this command: adb shell "ls -l /dev/block/by-name/super"
    • To check whether or not your device has the notorious shared_blocks read-only feature you can run these commands in Android:
      Bash:
      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
    Manual installation:
    • Extract flashable.zip and copy systemrw_*VERSION* folder into /data/local/tmp/
    • run this command to make the script executable:
      chmod +x /data/local/tmp/systemrw_*VERSION*/systemrw.sh
    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 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 included config.ini file and then save the file. Then compress the systemrw_*VERSION* and META-INF folders again as a new .zip and install it in recovery.
    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.bin and want to skip that process next time you install the .zip then put this in line #2 of config.ini :
    in=`ls -l /dev/block/by-name/super | awk '{print $NF}'` size=15
    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 (see examples below).
    If you've got a super partition I would recommend using the optional size=15 parameter as well to give some extra free space (in MB) to each partition.
    Optional script arguments:
    Replace x with your custom value
    • in=x *THIS IS IGNORED IF YOU'VE GOT 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 systemrw or the official unsparsed super.img from your downloaded firmware. (unsparse with simg2img). It's also possible to use your super partition block device as input.
      If omitted, systemrw will dump super image from phone to ./img/super_original.bin
      (path is relative to the script)
    • out=x *THIS IS IGNORED IF YOU'VE GOT NO SUPER PARTITION*
      With this argument you can specify the output path of the new patched super file.
      If omitted, default output value is ./img/super_fixed.bin
    • size=x *ONLY RECOMMENDED IF YOU'VE GOT SUPER PARTITION*
      With this parameter you can specify the extra free space (in megabytes) that will be added to each partition. There is a limit as to how much extra free space you can add per partition. Check your lpdump.txt to find out the exact maximum extra size.
      If omitted, default extra size is 0 (shrink to minimum)

    Examples:
    Bash:
    adb shell
    su
    cd /data/local/tmp/systemrw_1.32
    chmod +x ./systemrw.sh
    
    # Run this command *IF YOU'VE GOT NO SUPER PARTITION*
    ./systemrw.sh
    
    # Run this command if you're first time user *AND YOU'VE GOT SUPER PARTITION*
    # Specify the extra free space in megabytes for each partition:
    ./systemrw.sh size=15
    
    # Plug an existing super image into the script like this *ONLY IF YOU'VE GOT SUPER PARTITION*
    ./systemrw.sh in=./img/super_original.bin size=15
    
    # Specify both the input file as well as the output destination *ONLY IF YOU'VE GOT SUPER PARTITION*
    ./systemrw.sh in=./img/super_original.bin out=./custom/path/super_fixed.bin size=15
    
    # EXPERT EXAMPLE:
    ./systemrw.sh in=`ls -l /dev/block/by-name/super | awk '{print $NF}'` out=./img/super_fixed.bin size=50

    Uninstallation:
    • To free up space and keep script as well as r/w capability you can simply delete /img subfolder at /data/local/tmp/systemrw_1.32/img
    • To delete script and keep r/w capability you can simply delete whole script folder at /data/local/tmp/systemrw_1.32
    • 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 (inside /tools/ subfolder - also available in recovery).

    Troubleshooting:
    If you get error 255 in custom recovery when trying to install flashable zip then try to install it manually. If you encounter this error please send me this file /tmp/recovery.log
    Make sure the script folder was correctly extracted to:
    /data/local/tmp/systemrw_*VERSION*
    If you can't run the script try making the file executable like this: chmod +x ./systemrw.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!
    If you get bootloop after successfully flashing super_fixed.bin then you can undo bootloop simply by re-flashing original stock super image and re-enabling dm-verity and verification with the included avbctl binary (inside /tools/ subfolder - also available in recovery). Those are the only changes performed by the script.
    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 enthousiasts (links can be found in the credits section below). Therefore 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 5GB 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.
    Big thanks @munjeni for allowing me to use his 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.
    More thanks @gabrielfrias for his helpful comment
    Thanks @YOisuPU and of course @topjohnwu for discovering the 'shared_blocks feature'
    Thanks @HemanthJabalpuri for assisting me in optimizing the underlying algorithm!

    Disclaimer:
    #Disclaimer v2.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 ensue from the (inappropriate) use of this software.
    • All responsibility, liability and risk lies with the end-user. You hereby agree not to abuse this software for illegal purposes.
    • Under no circumstances shall the comments & title section of the script (lines #1 - #65) as well as the included update-binary be modified or removed by the end-user without the original author's explicit consent.
    • Under no circumstances shall the end-user steal and / or abuse my entire SystemRW project or parts thereof (including but not limited to my update-binary, my script, my program logo, my program name or the names of my functions and my variables and more...) only to rename and republish my SystemRW project (or parts thereof) as his / her own without even mentioning original source or original credits!!! (yes this actually happened :( perpetrated by a fellow forum member...)
    • Unauthorized re-uploads of any files contained within this project to 3rd party websites are not permitted without the original author's prior consent!
    • The end-user is allowed to improve the underlying algorithm (as long as no malicious code is added) and post his/her improvements, results and feedback right here in the official SystemRW project thread @ xda-developers.com
    • If the end-user wants to integrate my SystemRW project into his/her own project then he/she shall first ask me (the original author) for permission.
      If you want to make a video tutorial about my script please contact me first!
      Thank you! I can give you high resolution project logo and more!

    Please make sure to post your feedback and suggestions in the official thread right here.
    Enjoy customizing your fully read/write-able Android device! And feel free to share your Android system mods with other users in this thread! Thanks!


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


    1-jpg.5235933


    Confirmed working on these devices:




    Download v1.32 mirror #1


    Download v1.32 mirror #2

    current status: experimental

    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 button below.

    Thanks! Your support is very much appreciated!

    Donate
    12
    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!
    6
    New version 1.20 is ready! DOWNLOAD HERE
    Good news for those that don't have TWRP or couldn't get it to work in their TWRP. Now the script can also be run directly inside Android. Keep in mind that you will have to flash the patched images manually in this case using fastboot flash.

    The zip can still be flashed in TWRP (make sure zip signature verification isn't checked). This time I bundled my device's stock sh binary (which I used to develop the script) with the archive. Hopefully this will prevent avoidable sh-related syntax errors for some folks. The flashable zip installer update-binary automatically launches the script with the proper arguments using this bundled sh program (it's inside the tools subfolder).

    To those that were having difficulties running the previous version due to empty partitions or multiple partition groups inside their super : this has finally been fixed :D

    Please give this new version a try and let me know if it works for you or not and I will add it to the first post. Thanks for your feedback!
    5
    I try to redo the procedure, i want to change the size. but i get error, can't remove lock.

    Good news. New hotfix available HERE
    I got rid of that buggy get minimum size function and reworked the size querying algorithm a little bit. Should be more stable now.

    Next step will be to make the script compatible with those devices that have empty partitions embedded inside their super partition...
    Also ronnie was complaining about syntax error but I have yet to find the syntax error... If anyone finds it please let me know so I can fix it. Thank you!