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

Pachacouti

Senior Member
Jul 8, 2020
232
44
52
The Capital above the Lower one...
Is it possible to make the system partition contained in super to auto resize itself using your script?

I was reading how to resize system and cottoned on to a method to have the available space adjust itself automatically, like if I deleted the product partition, the system would adapt to the availble space?

From what Ive read here, we're one step away from a completely rw system in this so called ro system...

It's like this as I see it:

So we resize, and change the format to a rw format, this is to make it rw perm, and have the resize we need to adjust automatically to any freed up space on the fly


Found:

For those looking for the actual resizepart command, I think this is what the OP had in mind: sudo parted /dev/mmcblk0 resizepart 3 100% where /dev/mmcblk0 is the drive and 3 is the partition


Can the above be added/adapted to the script? (for each partition within super?) - oh, and to super itself?? (random idea, mount bind super.img to super.img on sdcard...)

Ps, this will fix no space left problems :)

Ps, found here:

 
Last edited:

lebigmac

Senior Member
Jan 31, 2017
884
516
Yes auto-resize feature is easy to do. Don't worry I will add it soon when I have more time ;)

If you check the amazing superrepack tool by @munjeni (link in first post) he has already implemented this special feature long time ago. I'm only beginner programmer but that guy is a real expert (y)
 
Last edited:
  • Like
Reactions: Pachacouti

The_Tablet

Member
Jun 14, 2019
10
1
Toronto
Google Pixel 2 XL
hey @lebigmac! i finally figured out the issue. basically, i'd extracted systemrw_1.32_flashable.zip into a folder in /data/local/tmp called "systemrw_1.32", making the directory structure look like this:
Code:
data/
├─ local/
│  ├─ tmp/
│  │  ├─ systemrw_1.32/
│  │  │  ├─ systemrw_1.32/
│  │  │  │  ├─ tools/
│  │  │  │  ├─ config.ini
│  │  │  │  ├─ systemrw.sh
as a result, systemrw.sh was unable to find the tools directory because it was actually located in a subdirectory within the expected directory, which the script obviously doesn't know about as the location is hardcoded as "/data/local/tmp/systemrw_1.32/".

so after moving everything in that rogue subdirectory up one directory, so it looked like this (as intended) :

Code:
data/
├─ local/
│  ├─ tmp/
│  │  ├─ systemrw_1.32/
│  │  │  ├─ tools/
│  │  │  ├─ config.ini
│  │  │  ├─ systemrw.sh

the script finally worked! (see attached logs).

i booted into twrp and flashed the images, and my system is now finally(!) r/w!

sorry for the wild goose chase there, and i send my sincerest thanks over to you and everyone else who made this possible! :3
 

Attachments

  • sysrw_log_2021-09-25.txt
    6.3 KB · Views: 10
  • Love
Reactions: lebigmac

krasevalex

Member
Jun 10, 2019
13
11
57
Philadelphia
Hi @Ricardo Cruz. Thanks for your feedback. It looks like your device is not recognized by adb?

Did you get the sysrw_repair script to work inside your Linux environment? What was the problem?

Was super_fixed.bin created successfully and did you fastboot flash it to your super partition yet?
What is the result? Can you do this now?

1-jpg.5235933



Hi @krasevalex. Thanks for your feedback. Please send me your log files from this folder. Thanks.
/data/local/tmp/systemrw_1.32/log/

You can successfully boot device after flashing super_fixed.bin AND you can remount partitions as R/W? That sounds like a success to me. Congratulations!

I think you need to run script again with larger custom size and generate new super_fixed.bin with the repair script and fastboot flash it manually to your super partition.
After that everything should work as expected.

Bash:
adb shell
su
cd /data/local/tmp/systemrw_1.32
./systemrw.sh in=`ls -l /dev/block/by-name/super | awk '{print $NF}'` size=50


/system is only in Android 9 and earlier. In Android 10+ it's called /
I repeated all procedure (./systemrw.sh size=50 => error code 73 in the phone => repair script in Ubuntu) and result this time is very good. The system is RW, nothing wrong with build.prop. Now I have full root. :)
So far everything's great. Thank you very much for this script.
 
  • Love
Reactions: lebigmac

fire7ly

Member
Apr 16, 2021
21
7
Screenshot_PBRP_2021-09-27-01-29-00.png

sir I`m tried this earlier but I'm not getting Success I'm try it again today and got error 255
idk why it occur..
my device Spec are:-
Realme C3 RMX2027 Helio G70
rn on Realme UI 1.0 Android 10.
 

Pachacouti

Senior Member
Jul 8, 2020
232
44
52
The Capital above the Lower one...
View attachment 5419775
sir I`m tried this earlier but I'm not getting Success I'm try it again today and got error 255
idk why it occur..
my device Spec are:-
Realme C3 RMX2027 Helio G70
rn on Realme UI 1.0 Android 10.
This error is a twrp error I believe, seems twrp no longer correctly interprets the adb sideloaded file name as package.zip, notice package zip in log?

Bet your sideloaded zip was NOT called package.zip, I've seen this in stock recovery too

Something is trying to flash a zip, or has renamed your file, or is looking for a file called flashable.zip, most likely a typo in the script.. or twrp... or recovery lol.. I'm betting incorrectly imported twrp recovery...img
 
Last edited:

fire7ly

Member
Apr 16, 2021
21
7
This error is a twrp error I believe, seems twrp no longer correctly interprets the adb sideloaded file name as package.zip, notice package zip in log?

Bet your sideloaded zip was NOT called package.zip, I've seen this in stock recovery too

Something is trying to flash a zip, or has renamed your file, or is looking for a file called flashable.zip, most likely a typo in the script.. or twrp... or recovery lol.. I'm betting incorrectly imported twrp recovery...img
I'm using pbrp sir it`s something mounting issue I guess.
 

fire7ly

Member
Apr 16, 2021
21
7
@lebigmac sir one more update I'm run this script in system mode and it did rebuild my super but when I'm flash super_fixed as fastboot flash super super_fix.img my device not boot anymore it always reboot to bootloader I'm disable all vbmeta verity and verification too but it give reboot to bootloader it seems Realme UI custom partition My_Product massed or corrupt coz driver not loading from that. Can you help me.. I Wanna be make it r/w.. thanks in advance logs attached here..
 

Attachments

  • mylog.txt
    6 KB · Views: 3
  • Screenshot_2021-09-27-14-03-31-40.jpg
    Screenshot_2021-09-27-14-03-31-40.jpg
    224.6 KB · Views: 26
  • lpdump.txt
    2.9 KB · Views: 5
  • dmesg.log
    481.8 KB · Views: 2
  • Like
Reactions: lebigmac

fire7ly

Member
Apr 16, 2021
21
7
Yup, the file package.zip not found :) because no file called package.zip exists.

(Should say name of zip being used, not 'package.zip')
I`m run this in system and result here!
@lebigmac sir one more update I'm run this script in system mode and it did rebuild my super but when I'm flash super_fixed as fastboot flash super super_fix.img my device not boot anymore it always reboot to bootloader I'm disable all vbmeta verity and verification too but it give reboot to bootloader it seems Realme UI custom partition My_Product massed or corrupt coz driver not loading from that. Can you help me.. I Wanna be make it r/w.. thanks in advance logs attached here..
 

lebigmac

Senior Member
Jan 31, 2017
884
516
@lebigmac sir one more update I'm run this script in system mode and it did rebuild my super but when I'm flash super_fixed as fastboot flash super super_fix.img my device not boot anymore it always reboot to bootloader I'm disable all vbmeta verity and verification too but it give reboot to bootloader it seems Realme UI custom partition My_Product massed or corrupt coz driver not loading from that. Can you help me.. I Wanna be make it r/w.. thanks in advance logs attached here..
Hi @fire7ly thanks for your log files.
I noticed you made a little mistake with the file path but script still worked nevertheless when launched manually. I'm surprised.

Screenshot_2021-09-27-14-03-31-40_error.jpg


According to your script log everything went well. All read-only restrictions have been successfully removed from your super image. I'm not sure what exactly is causing bootloop on your device. Some devices don't like modified super images... There must be some kind of special protection feature inside your device that prevents it from booting into the super image if it has been modified. That's my guess. You could try to check logcat while device is trying to boot to find out more info about the exact bootloop reason.

Can you undo bootloop simply by flashing original stock super image? You might have to flash stock vbmeta as well. Good luck!
 
Last edited:

fire7ly

Member
Apr 16, 2021
21
7
Hi @fire7ly thanks for your log files.
I noticed you made a little mistake with the file path but script still worked nevertheless when launched manually. I'm surprised.

View attachment 5420301

According to your script log everything went well. All read-only restrictions have been successfully removed from your super image. I'm not sure what exactly is causing bootloop on your device. Some devices don't like modified super images... There must be some kind of special protection feature inside your boot.img that prevents the device from booting into the super image if it has been modified. That's my guess. You could try to check logcat while device is in bootloop to find out more info about the exact bootloop reason.

Can you undo bootloop simply by flashing original stock super image? You might have to flash stock vbmeta as well. Good luck!
sir as you say I'm take log and my dev friend read and say me its problem from My_Product partition which is causing issue that My_Product is custom partition by Rui inside super, script decrease size of that partition. I'm flashed all vbmeta to disable verification & verity. this is the right path as you suggest in your tutorial I'm using "*" coz idk right name of folder that time... this have version name too so I'm just add * to assume to get right path by chmod command..
main thing is was under /data/local/tmp/systemrw_1.32/systemrw.sh
can you look into this again in attached my device log earlier..
thanks in advance
 
  • Like
Reactions: lebigmac

fire7ly

Member
Apr 16, 2021
21
7
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!
 

fire7ly

Member
Apr 16, 2021
21
7
@lebigmac sir I'm unpack super with lunpack and compare both of super_fix.bin and manually pulled one super.img
and there are something like mounting issue. partition name not show its just show version.0001.img insted of my_company.img can you check this out.. idk what`s wrong with it..I can send compare list to you..
soon..
 

Jr.17

Member
Aug 25, 2021
12
2
so I did Everything ran First Script gave error code 73 so booted up my linux ran recovery script it after 10-15 minutes said it was succesful and it was all unlock so i did a quick check on my phone and im still locked.
went back to the P.C did a remount
mount -o remount,rw /

and gave me no output checked phone again same thing files looked so i assume i missed something
 

Top Liked Posts

  • There are no posts matching your filters.
  • 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
    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!
    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
    1
    Hi @Kira565 to fix error 73 click here


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

    @season 8 @012345678 Did you try adding Android 12 support in script yet?
    Simply add these 2 lines between line #403 and #404, save file and try again. Good luck!
    Bash:
    elif (( $sdkVersion == 31 )); then
            android=12
    sorry for the misinformation , i got so exited and i had so much fun having my phone sysrw i felt it was a year maybe 😁😁😁😁😁 , anyway
    trying out your linux method fix for the repair zip using linux mint
    i will report that im currently waiting for the script to flash super_fixed.bin at bootloader 😵😵😵😵😵

    it booted into bootloader but in terminal its saying waiting for any device and its taking so long ,
    should i do something or should i wait???


    Edit : things are happening ,

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

    the command was : fastboot flash super super_fixed.bin
    afterwards i rebooted into twrp and i re-enabled virity and verification on slot b then slot a
    then i rebooted into android and BANG mount -o remount,rw / worked on terminal
    and finally i have RW System on latest stock android 11 on asus ROG III

    A/B partitions

    thanx @lebigmac thanx @poyiqqq thanx @harpreet.s

    😵 😵 😵 😵 😵 😁😁😁😁😁
    1
    @lebigmac sir one more update I'm run this script in system mode and it did rebuild my super but when I'm flash super_fixed as fastboot flash super super_fix.img my device not boot anymore it always reboot to bootloader I'm disable all vbmeta verity and verification too but it give reboot to bootloader it seems Realme UI custom partition My_Product massed or corrupt coz driver not loading from that. Can you help me.. I Wanna be make it r/w.. thanks in advance logs attached here..
  • 104
    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
    automated bash script for Android 10 and newer

    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 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 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 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 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 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
    10
    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!