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

lebigmac

Senior Member
Jan 31, 2017
873
507
@Leandro344 @wv8023

Okay folks I just uploaded a long overdue hotfix for you.
This should fix error signal 6 and maybe also error 255 in recovery. Thanks for all the feedback you guys gave me!
This time I've included the official platform-tools in the sysrw_repair tools subfolder.
Error 73 and 70 still need to be fixed within the script.
Check first post for download link. Enjoy!

Warning to OnePlus users: COW error is not fully fixed yet! Make sure you backup your original super before flashing!
 
Last edited:
Okay folks I just uploaded a long overdue hotfix for you.
This should fix error signal 6 and maybe also error 255 in recovery. Thanks for all the feedback you guys gave me!
This time I've included the official platform-tools in the sysrw_repair tools subfolder.
Error 73 and 70 still need to be fixed...
Check first post for download link. Enjoy!

Warning to OnePlus users: COW error is not fully fixed yet! Make sure you backup your original super before flashing!
Awesome! An amazing feat in and of itself. You sir are A GOD!
 
  • Haha
Reactions: lebigmac

rakoncwy

Member
Jul 17, 2021
27
11
I tried it on Realme GT, but the same symptom.
boot infinite loop.

And it cannot be restored with the "super_original.bin" file.

Realme gt does not have a proper recovery tool, so recovery is very difficult.
 

Attachments

  • mylog.txt
    4.4 KB · Views: 8
  • lpdump.txt
    6 KB · Views: 2
  • Sad
Reactions: lebigmac

lebigmac

Senior Member
Jan 31, 2017
873
507
@wv8023

Make sure you have created a img folder inside the systemrw folder. The script won't make one for you, so it just fails to dump super_original.
@tha_mechanic That's not true. The script will try to create ./img folder in current path if it doesn't exist.
And the sysrw_repair script is bundled together with the img folder ;)

I tried it on Realme GT, but the same symptom.
boot infinite loop.

And it cannot be restored with the "super_original.bin" file.

Realme gt does not have a proper recovery tool, so recovery is very difficult.

@rakoncwy Your log looks very unusual.

To undo the boot loop you could try reactivating the verity and verification as well as restoring original stock super image.
Sometimes messing with the vbmeta can cause boot loop.

Just boot into recovery and try reactivating verity and verification using the avbctl program that's included in the script's tools subfolder.

If your device have no custom recovery simply flash the stock vbmeta.img and stock super.img using fastboot. You can download these files from your device manufacturer's website.
This should re-enable both dm-verity and verification.

The script only modifies super partition and vbmeta partition.

Good luck!
 
Last edited:
Your log looks very unusual.

To undo the boot loop you could try reactivating the verity and verification as well as restoring original stock super image.
Sometimes messing with the vbmeta can cause boot loop.

Just boot into recovery and try reactivating verity and verification using the avbctl program that's included in the script's tools subfolder.

If your device have no custom recovery simply flash the stock vbmeta.img and stock super.img using fastboot. You can download these files from your device manufacturer's website.
This should re-enable both dm-verity and verification.

The script only modifies super partition and vbmeta partition.

Good luck!
HaHa😂?? What's so funny Mr Hamburger? Hmmm? I congratulate u on overcoming a hurdle in these hard times, and you laugh at me? Phh! Whatever!,,....................,...................Lulz
 
Last edited:
  • Haha
Reactions: rhewins2268

DeathShot9

Senior Member
Sep 4, 2015
64
15
Boston
It looks like the maximum amount of downloads per day was reached (70).
I've attached the download to this post. Enjoy!
Thank you.

I am trying to run this on my Xperia 1II. I just used Newflahser to flash the latest Android 11 US firmware from XperiFirm (58.1.A.5.222-R6B) and I installed Shinyquagsire24's TWRP but when I run the script it says:

Code:
Installing zip file '/sdcard/Download/systemrw_1.32_BUNDLE.zip'
Unmounting System...
tw_has_recovery_partitio
E: Unable to open block device /dev/block/loop19: No such device or address
E: Unable to open block device /dev/block/loop19: No such device or address
E: Unable to open block device /dev/block/loop18: No such device or address
E: Unable to open block device /dev/block/loop17: No such device or address
Error installing zip file '/sdcard/Download/systemrw_1.32_BUNDLE.zip'
Updating partition details...
...done
 

lebigmac

Senior Member
Jan 31, 2017
873
507
HAHAHAHA. Okay, it's running now, I'll let you know how it goes. Thanks :)

Edit: Got Error 73. NBD, I don't have time to boot into Linux right this minute, but I'll do it later tonight.
Before you run the linux repair script please open the sysrw_repair.sh script file with text editor and change version number from 1.31d to 1.32 and save file.
I forgot to do that!
 
Last edited:
  • Like
Reactions: DeathShot9

DeathShot9

Senior Member
Sep 4, 2015
64
15
Boston
Before you run the linux repair script please open the sysrw_repair.sh script file with text editor and change version number from 1.31d to 1.32 and save file.
I forgot to do that!
I woke up, finally booted up Ubuntu MATE on my laptop, thought it was going to be a nightmare to get working, then one sudo apt-get install android-sdk-platform-tools and adb devices later and I'm running the script. Script does its thing, restarts phone, './img/super_fixed.bin':no such file or directory.

Immediately I get on here, don't read your reply, and start reading through every page in the thread until I get to your reply. I updated the script version number and found my phone was at 5% battery xD

Recharging phone and laptop, going to try again in a few minutes!
Edit: this time I got a popup saying I don't have enough storage on my drive, is there a workaround for this, or do I need to make a larger live USB with persistent storage?

Edit 2: Tried a VM last night, it didn't work, so this time I decided to read the error more carefully, it turns out VMWare defaults to a USB 2 controller which doesn't work with my phone. Setting it up to USB 3.1, got it to work. The only thing is once it restarts and the phone reconnects it doesn't get registered in fastboot and just sits on <waiting for any device>. I guess my next step for now is to try a larger live disk.

Edit 3: Without going into too many details, Ubuntu live managed to physically damage my laptop, and I'm very upset. Is there any way to do this without Linux?
 
Last edited:
  • Wow
Reactions: lebigmac

DeathShot9

Senior Member
Sep 4, 2015
64
15
Boston
Sorry for the double post but I think at this point it's better to just start fresh.

I had to step away because the runaway shutdown script that cooked my laptop really got me upset but I got around to testing it and I am having the same problem with the live system as I did my VM. I am thinking that this might be a Sony thing. Sony has their bootloader and also their download mode which work slightly differently than a lot of other android systems.

Right now it's all speculation, so I'm uploading the logs for reference. I don't see the super_fixed.bin file anywhere. How do I preserve it or generate it so that I can try and flash it manually?
 

Attachments

  • log.txt
    2.2 KB · Views: 2
  • lpmake_output.txt
    879 bytes · Views: 2
  • myargs.txt
    868 bytes · Views: 3
  • Like
Reactions: lebigmac

lebigmac

Senior Member
Jan 31, 2017
873
507
Hi @DeathShot9 thanks for your feedback. Apparently I didn't thoroughly test the sysrw_repair script before release 🤦‍♂️🌴
In your sysrw_repair log something is wrong. Let's solve the problem together ;)

Initiating procedure...
Pulling all *.img files from phone to ./img folder. Please wait...
/data/local/tmp/systemrw_1.32/img/odm_a.img: 1 file pulled, 0 skipped. 94.3 MB/s (1499136 bytes in 0.015s)
/data/local/tmp/systemrw_1.32/img/odm_b.img: 1 file pulled, 0 skipped.
/data/local/tmp/systemrw_1.32/img/product_a.img: 1 file pulled, 0 skipped. 126.7 MB/s (1617293312 bytes in 12.169s)
/data/local/tmp/systemrw_1.32/img/product_b.img: 1 file pulled, 0 skipped.
/data/local/tmp/systemrw_1.32/img/system_a.img: 1 file pulled, 0 skipped. 91.3 MB/s (2091855872 bytes in 21.859s)
/data/local/tmp/systemrw_1.32/img/system_b.img: 1 file pulled, 0 skipped. 6.1 MB/s (374607872 bytes in 58.431s)
/data/local/tmp/systemrw_1.32/img/vendor_a.img: 1 file pulled, 0 skipped. 12.8 MB/s (966987776 bytes in 72.008s)
/data/local/tmp/systemrw_1.32/img/vendor_b.img: 1 file pulled, 0 skipped.

Pulling myargs.txt file from phone to current folder
/data/local/tmp/systemrw_1.32/log/myargs.txt: 1 file pulled, 0 skipped. 0.4 MB/s (868 bytes in 0.002s)

Attempting to run lpmake for linux using arguments from myargs.txt. Please wait...
lpmake I 07-25 17:57:23 37563 37563 builder.cpp:1012] [liblp]Partition system_a will resize from 0 bytes to 2091855872 bytes
lpmake I 07-25 17:57:23 37563 37563 builder.cpp:1012] [liblp]Partition system_b will resize from 0 bytes to 374607872 bytes
lpmake I 07-25 17:57:23 37563 37563 builder.cpp:1012] [liblp]Partition product_a will resize from 0 bytes to 1617293312 bytes
lpmake I 07-25 17:57:23 37563 37563 builder.cpp:1012] [liblp]Partition vendor_a will resize from 0 bytes to 966987776 bytes
lpmake I 07-25 17:57:23 37563 37563 builder.cpp:1012] [liblp]Partition odm_a will resize from 0 bytes to 1499136 bytes
lpmake E 07-25 17:57:23 37563 37563 images.cpp:448] [liblp]open image file failed: /data/local/tmp/systemrw_1.32/img/system_a.img: No such file or directory
lpmake E 07-25 17:57:23 37563 37563 images.cpp:326] [liblp]Could not open image for partition: system_a

Successfully created patched super image at /home/ubuntu-mate/Desktop/sysrw_repair_v1.32/img/super_fixed.bin

Rebooting phone into bootloader for flashing super_fixed.bin...
There was a problem flashing the super partition

Apparently the files were pulled correctly from phone but the paths are wrong. Please allow me to fix that for you.
Try this fixed version of the sysrw_repair script. Better luck this time!

If this actually works I'll update the first post and reupload the whole BUNDLE.
Done
 

Attachments

  • sysrw_repair_v1.32_proper.zip
    9.3 MB · Views: 24
Last edited:
  • Like
Reactions: DeathShot9

DeathShot9

Senior Member
Sep 4, 2015
64
15
Boston
Hi @DeathShot9 thanks for your feedback. Apparently I didn't thoroughly test the sysrw_repair script before release 🤦‍♂️🌴
In your sysrw_repair log something is wrong. Let's solve the problem together ;)



Apparently the files were pulled correctly from phone but the paths are wrong. Please allow me to fix that for you.
Try this fixed version of the sysrw_repair script. Better luck this time!

If this actually works I'll update the first post and reupload the whole BUNDLE.
Running the script right now, I'll update this with the result.
Edit 1: it's been throwing some "Invalid sparse file format at header magic" messages, but it's still doing something, since the directory size is growing, so I'm letting it run.

Edit 2:
Congratulations! Successfully flashed the super partition Your partitions should now have rw capability

XQ-AT51:/ $ ls -l /dev/block/by-name/super lrwxrwxrwx 1 root root 16 1970-12-27 04:34 /dev/block/by-name/super -> /dev/block/sda89
 

Attachments

  • log.txt
    1.4 KB · Views: 5
Last edited:
  • Like
Reactions: lebigmac

DeathShot9

Senior Member
Sep 4, 2015
64
15
Boston
The only issue i got on using this flashable fix was i cant mount vendor partition but system and product partition can be modified and are mountable
Same. I just finished de-bloating all the system apps but I'm stuck with "Title 3 months free trial" (yeah, that's the actual name of the app), linkedin, and some random "call of duty" that is already old. I'm crossing my finger this script might be modifiable to fix /oem, if not then I know that for the Xperia 1II the Russian firmware does not have the "/oem" partition and so if I scrap everything I've done, and flash that, I won't have to deal with it. I prefer not to use the Russian one though because I lose some functionality with my carrier in the US.

When I try mount -o remount,rw /oem I get '/dev/block/bootdevice/by-name/oem_a' is read-only
 
  • Like
Reactions: lebigmac

Top Liked Posts

  • 1
    hi @lebigmac
    thanks for your project.
    i hope, i do realy realy hope, that new script with auto-size feature will be released soon in systemrw_1.33.
    1
    Thanks for the confirmation. It looks like script worked as expected and successfully removed shared_blocks read-only feature from your device.
    I don't know why your device is still read-only!? It doesn't make any sense. There must be another read-only protection feature hidden somewhere deep inside your device...

    Can you do this? (see picture below)
    Also run dmesg immediately after remount command. Maybe we can figure out what's the problem.
    Bash:
    adb shell
    su
    mount -o remount,rw /
    dmesg>/sdcard/dmesg_devill2014.txt

    1-jpg.5235933
    1
    I had a error with previous version about cow error. But with last version, no cow error. The script worked! Thx again ;)
  • 2
    is there any tutorial on how to use sysrw_repair_v1.32 ? :

    1- Sorry for spamming the thread.
    2- Thank you Keven11 and lebigmac
    3- Finally I got it, first flashed the stock rom (android 11) and started it just to create the /data/media/ folder. Right after that I turned off the device, flashed the twrp and magisk, and placed the systemrw_1.32 in the /data/local/tmp/ folder. I started the script from the twrp terminal "sh /data/local/tmp/systemrw_1.32/systemrw.sh size=15. After getting the error "73" screen, I started sysrw_repair_v1.32 in vmware emulating linux mint... And everything went really well! :)

    View attachment 5425517
    It is definitely a journey. Well worth the work, and time invested in then end. Also, it helps many people understand their devices just that much more. I am glad that you were successful.

    Also, everytime a person manages to get this to work for themselves, and explains how they did. That alone helps many others. So thank you for putting in the work, and sharing your experience.
    2
    1- Sorry for spamming the thread.
    2- Thank you Keven11 and lebigmac
    3- Finally I got it, first flashed the stock rom (android 11) and started it just to create the /data/media/ folder. Right after that I turned off the device, flashed the twrp and magisk, and placed the systemrw_1.32 in the /data/local/tmp/ folder. I started the script from the twrp terminal "sh /data/local/tmp/systemrw_1.32/systemrw.sh size=15. After getting the error "73" screen, I started sysrw_repair_v1.32 in vmware emulating linux mint... And everything went really well! :)

    c74256c2706c6e8f74e5858e4aa85f57.gif
    2
    Thanks. But you can tell in more detail. Where to get the super_original.bin and super_fix files. Please write detailed instructions.
    this script have 2 mode one is from recovery flash as zip second have run it in android environment.
    if you run this in recovery then it patch and flash super automatically.
    second if you run it in android environment with as mention location of /data/local/tmp/here_your_script_folder/here_script.sh then it create a "img" folder inside of script folder then pull super from your device make a backup and rename that to super_orignal.bin then extract that super and patch r/w capability then make that again super and rename it as super_fix.img so simply you get two bin files inside "img" folder
    if you wanna r/w your device flash super_fix.img from bootloader.
    if you wanna go back to original state "flash super_orignal.bin" from bootloader.
    directory tree will like this :-
    data/ ├─ local/ │ ├─ tmp/ │ │ ├─ systemrw_1.32/ │ │ │ ├─img/ │ │ │ │ ├─super_orignal.bin │ │ │ │ ├─super_fix.bin │ │ │ ├─ tools/ │ │ │ ├─ config.ini │ │ │ ├─ systemrw.sh
    thanks this for @The_Tablet
    That's it!
    1
    Hola, [USER = 11816235] @Ricardo Cruz [/ USER]. Envíeme sus archivos de registro desde esta carpeta. Gracias.
    /data/local/tmp/systemrw_1.32/log / [/ ICODE] Simplemente conecte el teléfono a la computadora usando un cable usb-c a usb-a. [URL='https://forum.xda-developers.com/t/script-android-10-universal-mount-system-read-write-r-w.4247311/page-23#post-84901531'][B]Aquí[/B][/URL] puede encontrar las instrucciones oficiales del script de reparación de resolución de problemas (solo Linux). [/QUOTE] Hello, sorry for the delay, I imagine that these are the files that you ask me [/QUOTE]
    1
    I had a error with previous version about cow error. But with last version, no cow error. The script worked! Thx again ;)
  • 101
    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

    *NEW* SystemRW v1.32 *NEW*
    automated bash script by lebigmac for Android 10 and above

    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.

    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)
    User data is not affected.

    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!
    • 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"
    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

    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 experience bootloop after successfully flashing super_fixed.bin then your device probably has additional protection features that prevent it from booting modified super images. Try to undo bootloop simply by flashing original stock super image. You might have to flash stock vbmeta as well. 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.
    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 V1 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. 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 any files included in this project be re-uploaded to 3rd party websites without the original author's explicit consent. That means NO RE-UPLOADS of my files please! Thank you!
    • Under no circumstances shall the end-user disrespect, abuse or steal my project for his own disturbed purposes! The end-user also agrees not to steal my program logo or program name or the names of my functions and variables (and more) only to re-publish them as his/her own without even mentioning the original source.
    • The end-user is encouraged to improve the underlying algorithm (as long as no malicious code is added) and post his/her modifications, results and feedback right here in the official SystemRW project thread @ xda-developers.com
    • If the end-user wants to re-publish my work in 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 this project & the creation of more amazing projects like this then please feel free to donate to the developer by clicking the link below. Thanks! Your support is very much appreciated!

    Donate
    9
    If the script works on your device please send me your log files from this folder:
    /data/local/tmp/systemrw_1.32/log/

    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!
    4
    Great news! Flashable zip is almost ready! I'll upload it later today. Any volunteers want to beta test the new flashable zip to help me iron out any bugs? Please send me a message. Thanks!

    Installing the script has never been this easy. Simply swipe with finger inside TWRP and it's automatically installed to correct location on your phone.
    Then it checks a config file for any custom script execution arguments and launches the script with these arguments depending on whether or not your phone has a super partition.

    Let me tell you it was not easy to create this flashable zip installer but I had lots of fun learning about this whole flashable zip concept the past few days.