Search This thread

NoRue

New member
May 10, 2020
2
0
This is NOT WORKING for the MOTOROLA phone, specifically the MOTO ONE 5G ACE. The script did not unlock the partitions as they separated in lpmake. I looked at the files on Windows and Linux, and they are all as they were before. Why this is only working on the Xiaomi and the One Plus is beyond me. Anybody got this working on LG, Sony, Moto, Samsung?

Yes!SONY can't use it !
Device : Xperia 1 Mark II
 
  • Wow
Reactions: lebigmac

Simich007

New member
Apr 11, 2021
2
2
excellent, i did it and it finally finished with a message saying Congratulations...
but when it reboots the system partition is still read-only. the twrp and magisk are in place and i have su but "mount -o rw,remount /" says it's read-only and the partition can't be written. i've tried it multiple times with the same result. what should i do ?
Similar story I have, everything goes successfully, but after downloading to the system any file manager with rut access can't change system, vendor, product. Tried to stitch created super_fixed.bin as an image through adb, everything has passed successfully, but there is no result. Ulefone armor x7pro, 10 android.
 

Attachments

  • lpdump.txt
    1.1 KB · Views: 5
  • mylog.txt
    5.2 KB · Views: 8
Last edited:

lebigmac

Senior Member
Jan 31, 2017
711
364
Yes!SONY can't use it !
Device : Xperia 1 Mark II

PS C:\adb> adb shell "ls -Alg /dev/block/by-name | grep 'super'"
lrwxrwxrwx 1 root 16 1970-02-02 16:40 super -> /dev/block/sda23

POCO X3 pro, doesn't work

Hi. Please give more info about your specific error and share your log files thank you.

Similar story I have, everything goes successfully, but after downloading to the system any file manager with rut access can't change system, vendor, product. Tried to stitch created super_fixed.bin as an image through adb, everything has passed successfully, but there is no result.

Thanks for the log files. That's weird.
Your log looks pretty good to me.
Try unpacking super_fixed.bin with lpunpack
Bash:
adb shell
cd /data/local/tmp/makesysrw_1.27
./tools/bin/lpunpack ./files/super/super_fixed.bin

and see if you can mount it as read write in linux. If you don't have linux installed simply boot into a ubuntu live installation disk
Bash:
adb pull /data/local/tmp/makesysrw_1.27/files/super/system.img
sudo su
mkdir /mnt/dir
mount -t ext4 -o loop,rw ./system.img /mnt/dir
 
Last edited:

f1^ter

Member
Jan 8, 2016
46
40
32
Nadym
Sony Xperia 1 II
Hello dear! Android 11, Sony xperia 1 Mark II. Here is the log, what is the problem, a fix file is not created? My log files. If you need to provide something-let me know!
 

Attachments

  • lpdump.txt
    2 KB · Views: 10
  • mylog.txt
    8.1 KB · Views: 11

zgfg

Senior Member
  • Oct 10, 2016
    5,155
    2,451
    Working on my POCO X2 Device with super partition using v1.24....
    Working on MIUI 12 global stable ANDROID 11 and Latest Xiaomi.eu beta roms...
    A question please regarding to Xiaomi.eu - did you use it with the recent MIUI 12.6 like 21.4.1 or 21.4.7

    And actually more important question - did you try to update Xiaomi.eu from e.g. 21.4.1 to 21.4.7 while having the previous system mounted as read-write?

    Xiaomi.eu does not update by OTA but by downloading and flashing the zip file from TWRP, but I'm interested if dirty flashing the new Xiaomi.eu zip file works fine when the previous Xiaomi.eu was mounted read-write and wether maybe the newly flashed (updated) Xiaomi.eu automatically remains writable?
     

    saginesht

    Member
  • Oct 14, 2013
    42
    22
    26
    Kanyakumari
    A question please regarding to Xiaomi.eu - did you use it with the recent MIUI 12.6 like 21.4.1 or 21.4.7

    And actually more important question - did you try to update Xiaomi.eu from e.g. 21.4.1 to 21.4.7 while having the previous system mounted as read-write?

    Xiaomi.eu does not update by OTA but by downloading and flashing the zip file from TWRP, but I'm interested if dirty flashing the new Xiaomi.eu zip file works fine when the previous Xiaomi.eu was mounted read-write and wether maybe the newly flashed (updated) Xiaomi.eu automatically remains writable?
    I tried it on latest xiaomi miui 12.6 roms.... Working..... Tried dirty flashing weekly 21.4.7 rom over rw system partitions and it makes the system read only... U have to make it rw again ....
     
    Last edited:
    • Like
    Reactions: lebigmac and zgfg

    ITGrouch

    Member
    Dec 27, 2012
    31
    4
    Near Music City USA
    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🤪
    I have a Moto G Power and I get Error! Failed to create super_fixed.img file. I am on stock Android 10 and rooted. Since we have the same phone, Did you ever run into the same problem as I did and how did you fix it? Or did it complete without the error?
     

    lebigmac

    Senior Member
    Jan 31, 2017
    711
    364
    Similar story I have, everything goes successfully, but after downloading to the system any file manager with rut access can't change system, vendor, product. Tried to stitch created super_fixed.bin as an image through adb, everything has passed successfully, but there is no result. Ulefone armor x7pro, 10 android.

    Simich007 did you try mounting your partitions as read write?
    Bash:
    su
    
    mount -o remount,rw /
    mount -o remount,rw /vendor
    mount -o remount,rw /product

    Tried it and I get the same error creating super_fixed.bin I am about the throw in the towel and forget about it.

    Please don't give up yet. Don't worry sooner or later we will fix this problem and everybody will be happy ;)
    I am working on a possible solution but I need more feedback from people with slot A/B device. Thanks.

    Can any one help mylogs! Oneplus 8 android 11

    @chintoocool are you using stock android or custom ROM? Can you please post output of this command? Thanks.

    Code:
    mount
     
    Last edited:

    Kherham

    Senior Member
    May 8, 2017
    119
    21
    Joinville - SC

    WOW. I'm searching for something like this for days. But let me do a noob question.

    At this momento am using a custom MIUI rom with Android 10. I tried to use another rom with A11 but ever got my storage encrypted and ever when I need to update my rom, need to do that [email protected]#$#$% format data as you can see in my screenshot. After installing this script my storage will be decrypted ever? Ever when I back to recovery everything will be there (decrypted)? I really hope so.

    Thanks for your work bro.
     

    Attachments

    • ecrypted.jpeg
      ecrypted.jpeg
      123.4 KB · Views: 22

    lebigmac

    Senior Member
    Jan 31, 2017
    711
    364
    WOW. I'm searching for something like this for days. But let me do a noob question.

    At this momento am using a custom MIUI rom with Android 10. I tried to use another rom with A11 but ever got my storage encrypted and ever when I need to update my rom, need to do that [email protected]#$#$% format data as you can see in my screenshot. After installing this script my storage will be decrypted ever? Ever when I back to recovery everything will be there (decrypted)? I really hope so.

    Thanks for your work bro.

    Try boot into Android system, setup PIN code and then reboot to TWRP and enter PIN code to decrypt /sdcard
    You can also try installing the flashable zip from /data/local/tmp/
     
    Last edited:

    Top Liked Posts

    • There are no posts matching your filters.
    • 3
      Anybody want to try v1.31c ? Please keep in mind this version has not been thoroughly tested yet so you are trying it at your own risk!

      I was forced to change project name from makesysrw to systemrw AKA sysRW because some ruthless and spineless cyber pirate hacker who is also a member here has stolen my project, deleted all original info from script and replaced with his own meaningless words that had nothing to do with the project and then released as his own. He even hacked into my update-binary and changed the program title to his own bogus meaningless program title! Can you believe it? Talk about a lazy spineless hacker thief. This was also the reason why I had to stop the development of the Android app sadly. It was so close to being finished! Plagiarism and cyber piracy at its finest by a fellow forum member. It's unbelievable! Where has the mutual respect gone nowadays? And no apology or thanks from the guy to this date (been waiting since March 14th when I first caught him red-handed). Rest in peace open source!

      Anyways please let me know if this new version works on your device. I've finally figured out where this annoying lpmake error 73 is coming from and found 2 new ways to prevent it from happening. This error 73 seems to be related to Android 11.

      TWRP error 255 is not fixed yet but installing script manually should work (see manual installation instructions inside script if some ruthless hacker hasn't deleted it yet together with original source, credits, disclaimer and whatnot...)
      If your custom recovery cannot decrypt and mount /data partition yet then try manually running script from within Android!
      Good luck!
      3
      @thelavip @BlazingKahn35 @nttuan @kpykpy @harpreet.s @m3nty @f1^ter @ITGrouch @Articul8Madness @Xiaoleng
      Here is v1.30_gamma for anyone who wants to beta test it. I added some additional slot A/B functionality. Please let me know if it works for you or not. Thank you.
      3
      Finally I think I found the cause of super_fixed.bin creation error
      if the command arguments are too long, some device simply drops the command whether in adb or terminal emulator; the purpose might be to prevent command injection; this explains the instant weird crash

      As a temporary solution before Mr. lebigmac fix this problem, u may need to generate the super_fixed.bin by yourslef; the toturial is below.
      This may also fix the problem system mounted as rw on Android but still not writible

      1. run makesysrw on your Android device
      2. copy every .img located in /data/local/tmp/makesysrw_xx/files/super to an Ubuntu PC
      3. on Ubnuntu mount every partation as rw using terminal (eg: "sudo mkdir -p /tmp/product_a && sudo mount -o loop,rw,sync product_a.img /tmp/product_a")
      4. on Ubuntu open file manager as superuser ("sudo nautilus"); then locate to /tmp, find all partitions and modify any thing in each partition (you may create a text file, write a few lines, and copy this text file to all these partitions)
      5. unmount all paritions; use lpmake for linux (https://forum.xda-developers.com/t/guide-ota-tools-lpunpack.4041843/) to manually create super_fixed.bin

      #run lpmake for linux like this
      ./otatools/bin/lpmake COPY_PASTE_YOUR_ARGUMENTS_HERE

      6. fastboot flash super_fixed.bin to your device
      All partitions modified in step 4 should now be writable on your device
      3
      Now all of a sudden it just works on all input files regardless of whether they are read-only or read-write without having to do any modifications to the source code!? Thanks to precious feedback by @chintoocool all I did was move getCurrentSize() function from makeRW() function into makeSuper() function. And now it just works without throwing that annoying lpmake error 73. WTF! It's such a mystery to me.
      Did I just magically fix the annoying lpmake error 73 (that has been plaguing us for 2 months now) just like that by randomly moving some functions around in the script?! It required some serious detective work for sure. Big thanks to everyone who gave helpful feedback and contributed to fixing it.
      2
      @lebigmac

      Moto G Fast & Moto E (2020) - Working on both!

      You just need an external sdcard to get around the storage requirements. I unzipped it to tmp, set permissions, and ran it with these arguments in Orange Fox...

      Code:
      cd /data/local/tmp/makesysrw_1.31
      ./makesysrw size=20 out=/external_sd/super.img

      It worked flawlessly. You wrote a beautiful script! Thank you so much!
    • 56
      If you can't get this script to work on your device check out the brand new sophisticated superrepack tool by @munjeni



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

      Creation date: February 2021
      Updated: May 2021

      Requirements:
      • rooted STOCK Android 10 or newer (custom ROM should already be read-write!)
      • Custom recovery is recommended but no longer required in latest version
      • at least 20 GB free space on phone for dumping data
      Description:
      A script for all Android power users that wish to make their read-only Android 10+ system read-write-able again to remove bloatware and make more thorough customizations to their device.

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

      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 make your adjustments. 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 and want to skip that process next time you install the .zip then put this in line #2 of config.ini :
      Code:
       in=./img/super_original.bin 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.
      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.
      The script can be run both inside custom recovery and inside Android operating system. If you run it in Android you will need to fastboot flash the patched images manually!
      Optional arguments: (replace x with your custom value)
      • in=x : *THIS IS IGNORED IF YOU HAVE NO SUPER PARTITION*
        With this flag you can specify an existing super image as input and skip the entire dumping of the super image process. Here you can use the super_original.bin which you dumped earlier with 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 HAVE NO SUPER PARTITION*
        With this argument you can specify the output path of the new patched super file.
        If omitted, default output value is ./img/super_fixed.bin
      • size=x : *ONLY RECOMMENDED IF YOU HAVE SUPER PARTITION*
        With this parameter you can specify the extra free space (in megabytes) that will be added to each partition. 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:
      Code:
      # Run this command *IF YOU HAVE NO SUPER PARTITION*
      ./systemrw.sh
      
      # Run this command if you're first time user *AND YOU HAVE SUPER PARTITION*
      # Specify the extra free space in megabytes for each partition:
      ./systemrw.sh size=15
      
      # Plug an existing super image into the script like this *ONLY IF YOU HAVE 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 HAVE SUPER PARTITION*
      ./systemrw.sh in=./img/super_original.bin out=./custom/path/super_fixed.bin size=15

      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"

      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 into:
      /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!

      NOTE:
      I did not come up with all this by myself. After searching for a solution for countless days without success, going even as far as learning hex editing - I 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). So I take absolutely no credit for the underlying core mechanisms of the script. I'm only the amateur who put it all together into a compact script so that everybody can enjoy an Android system that's read-write-able again. Just like it used to be in Android 9 or earlier. Before this annoying 'shared_blocks feature' was implemented.

      Credits:
      Huge thanks to @Kolibass for allowing me to use his partition tools for Android. Without your tools this script would not work on the Android platform! This genius also showed me how to flash a 8GB file to my partition in just under 30 seconds! Much faster than fastboot! I still can't believe it!
      Big thanks to @Brepro1 for allowing me to basically copy his awesome tutorial and make it into a script. Without your tutorial guiding me I couldn't have created this script.
      Thanks @AndyYan your great tutorial also helped me a lot for automating the script especially the lpdump part.
      Also big thanks @munjeni for allowing me to use his superunpack 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.
      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:
      This is open source software and is provided as is without any kind of warranty or support whatsoever.
      By using and viewing this software you agree to the following terms:
      Under no circumstances shall the author be held responsible for any damages or negative consequences that may arrise from the (inappropriate) use of this software.
      All responsibility, liability and risk lies with the end-user. You hereby agree not to abuse this software for illegal purposes.
      The end-user is free to improve the underlying algorithm (as long as no malicious code is added) as well as redistribute this script in his own project as long as the comment and title section of the script (lines #1 - #65) as well as the included update-binary are not modified or removed.

      Please make sure to post your feedback, suggestions and improvements in the official thread right here.
      Enjoy customizing your read-write-able Android device!


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


      1-jpg.5235933


      Download v1.31d *NEW*
      current status:
      experimental
      Please click my like button below if you like my work! Thanks!

      Confirmed working on these devices :

      Xiaomi Poco X3 NFC
      Xiaomi Poco X3 Pro
      Xiaomi Poco X2 - Android 10/11
      Xiaomi Poco X2 - Android 11 (v1.24)
      Xiaomi Poco F2 Pro - Android 11 (v1.26)
      Xiaomi Mi 10 T Lite - Android 11
      Xiaomi Mi 10 T lite - Android 11 - TWRP
      Xiaomi Mi 10 - Android 11
      Xiaomi Mi 10 Ultra - Android 11
      Xiaomi Mi Note 10 Lite - Android 11 - OrangeFox
      Xiaomi Redmi 9 - Android 10
      Xiaomi Redmi 9 - Android 10 (v1.26)
      Xiaomi Redmi Note 9 Pro joyeuse - Android 10
      Xiaomi Redmi Note 9 Pro gauguin (China) - Android 10
      Xiaomi Redmi 9T - Android 11 - TWRP
      Xiaomi Redmi K30 - Android 10
      Xiaomi Redmi K30S Ultra(China), Android 11 (v1.29)

      Asus Rog Phone 3 - Android 10 - TWRP
      OnePlus Nord - Android 11 (v1.24)
      Doogee S96Pro - Android 10 (v1.26)
      F150 model B2021 - Android 10
      Realme C12 - Android 11
      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). I bundled my sh program (which I used to develop the script) with the archive this time. Hopefully this will prevent avoidable sh-related syntax errors for some folks. The flashable installer binary automatically launches the script with the proper arguments using this bundled sh program (it's inside the tools folder).

      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
      If the script works on your device please write me your phone model, Android version, script version and if you have super partition or not. Also please send me your log files.

      I will add you to the list of success and it will be helpful for further development. Thank you!
      4
      @lebigmac
      I am happy to say that, all the things went fine with my Realme C12.

      I have removed original super.img right after lpunpack finishes. This makes me use your tool with just 15GiB free space.

      A small thing is that, in your update-binary, please create a dir /data/local/tmp if it does not exist.
      If it does not exist, your tool will fail to install.
      It will be not present if a person clean flashes your tool(wipe data).

      Also system RW works fine, but vendor RW gives operation not permitted.
      Do I need use chattr with the block of vendor?


      Also, we can use like this sh makesysrw.sh. Advantage of this is that, we don't need to make it executable and shebang is ignored.

      Thanks

      Hello HemanthJabalpuri. Did you actually get my script to work on your device? This is wonderful news.

      Thanks for the suggestion about creating /data/local/tmp folder if it doesn't exist. I will do it in the next version.

      vendor RW gives operation not permitted.
      Do I need use chattr with the block of vendor?


      Operation not permitted? I never seen this error before. Do you get this error in the script or elsewhere?
      Sorry I don't know what is chattr.

      Also, we can use like this sh makesysrw.sh. Advantage of this is that, we don't need to make it executable and shebang is ignored.

      Thank you very much for this precious piece of advice. Some people have old sh version in their twrp that don't even support basic array functions. Do you think it's possible to bundle my own sh file (that I used for development) with the flashable zip and rule out any sh compatibility issues this way?

      In the next version of the script I would like to remove twrp completely from the requirement list so that everybody can enjoy a system that's read write-able, not only those with twrp. Some devices have no twrp or orange fox available.

      No Orangefox recovery too for Oneplus 7T , unfortunately. Oneplus really messed up 7T's decryption with android 10. I'm hoping for it to fixed with OOS 11 update which too, got delayed because they didn't care for its decryption issues in the first place. Its mind boggling that the 7T doesn't have a working TWRP even after 1 ½ years of being launched.

      Hi shady_soldier
      Yes that kind of sucks I agree. I wish I knew how to actually compile recovery. Too bad I'm only an amateur!
      I tried to compile Xiaomi stock recovery the other day but no luck so far...

      @lebigmac Any chance to uninstall It?
      Thx!!

      Hi Morello12. Did you actually run the script successfully or not?
      Sure simply delete the entire folder /data/local/tmp/makesysrw_1.15c

      But is it a new version or what?
      Does it work without disabling DM-verify?

      No. Disable dm verity and verification is always a good idea!
      @Ayoub$# You could also try flashing an empty vbmeta with fastboot if you can't disable dm verity manually.

      Code:
      fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
    Our Apps
    Get our official app!
    The best way to access XDA on your phone
    Nav Gestures
    Add swipe gestures to any Android
    One Handed Mode
    Eases uses one hand with your phone