yashsingh1/xdaforums huggingface dataset:
[Android Software/Hacking General [Developers Only]] lebigmac:
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!
[Android Software/Hacking General [Developers Only]] lebigmac:
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.
[Android Software/Hacking General [Developers Only]] chintoocool:
Here my logs its working perfectly 👌
[Android Software/Hacking General [Developers Only]] chintoocool:
Here Method 2 logs
[Android Software/Hacking General [Developers Only]] pandavova:
Error 73 on my Sony Xperia 5 ii with systemrw_1.31b.

I did flash from Android and not from TWRP (because TWRP doesn't work).
[Android Software/Hacking General [Developers Only]] lebigmac:
@pandavova thanks for the nice log files feedback! It's very helpful.

Oh no! Not Error 73 again :confused:

sysexits.h

@sebj84 @alansworld2010@gmail

SystemRW_v1.31c *NEW* is available for download HERE

I have bundled it together with the troubleshooting repair script v1.31c (Linux only) for all those unfortunate ones that still experience the mysterious lpmake error 73.

The flashable.zip is inside the bundle.zip
[Android Software/Hacking General [Developers Only]] totmakina:
I have flashed on my motorola g 5g plus. I have rebooted into twrp and can mount the boot, system and vendor partitions.
[Android Software/Hacking General [Developers Only]] reynaldio19:
work fine on my device, Poco X3 Pro, if error img folder, just add img folder into flashible zip. Latest version script v1.31c
[Android Software/Hacking General [Developers Only]] BartoszDylewski:
I Have "dd: ./img/super_original.bin: no such file or directory

systemrw: Error: Failed to dump file to: ./img/super_original_bin

Please help
[Android Software/Hacking General [Developers Only]] lebigmac:
I don't understand why this is happening. In script I have this code:

Therefore it should create ./img folder before calling dd command...

In the meantime try running script manually.
[Android Software/Hacking General [Developers Only]] BartoszDylewski:
Wait

Edit: There was an error extracting the file. Please install unzip.........

(error 255)
[Android Software/Hacking General [Developers Only]] lebigmac:
Got a screenshot? Please send me your recovery log from /tmp/recovery.log

How about you install it manually then? Manual installation instructions should be inside script (if some ruthless malicious hacker hasn't deleted them yet) or in first post of this thread.

Good luck!
[Android Software/Hacking General [Developers Only]] Ygrek178:
Redmi note 9 pro(joyeuse). I recently flashed 1.31 and everything was fine, but on 1.31c such a problem:

)
[Android Software/Hacking General [Developers Only]] monsterz77:
How to back to r/o..??(uninstall this script)
[Android Software/Hacking General [Developers Only]] reynaldio19:
Add img folder to flashible zip
[Android Software/Hacking General [Developers Only]] svoc:
I get error unknown partition super_fixed.bin

Fastboot error: can not determine image filename for super_fixed.bin
[Android Software/Hacking General [Developers Only]] _BJIAD_:
Script and so in UNIX format, what does he need?
[Android Software/Hacking General [Developers Only]] lebigmac:
Don't worry guys I will fix /img path error very soon! And I'll look into that unzip error too ;)

In the meantime please try manual installation as described here

or go back to v1.31
[Android Software/Hacking General [Developers Only]] monsterz77:
How to uninstall this..back to r/o...??
[Android Software/Hacking General [Developers Only]] lebigmac:
Click here

You didn't run the fastboot flash super command properly

Which device are you using? I've seen this error before. Maybe /data partition unavailable?
[Android Software/Hacking General [Developers Only]] _BJIAD_:
Poco F3, Android 11. Date is available.
[Android Software/Hacking General [Developers Only]] macubex1991:
Can I ask something..

Can I resize product partition and

Add to system partition?

My system partition free size is 44mb only while product partition is 2.2gb.

Thank you.
[Android Software/Hacking General [Developers Only]] larsx5:
Hi Guys! Is it possible to install this script into pixel 4a? As I understood, we don't have TWRP or other recovery options.

Please advise.

Have a great time!
[Android Software/Hacking General [Developers Only]] lebigmac:
Hi. Give it a try and let us know. Good luck!
[Android Software/Hacking General [Developers Only]] larsx5:
Hi, could you please explain how to install it? Currently I have Magisk on my phone.Thanks.
[Android Software/Hacking General [Developers Only]] lebigmac:
Please check manual installation instructions inside script if some ruthless spineless hacker thief hasn't deleted them yet. Good luck
[Android Software/Hacking General [Developers Only]] Keven11:
Here is the log and lpdump from the 1.31c version on moto g9+. I hope it helps.
[Android Software/Hacking General [Developers Only]] lebigmac:
Thank you Keven. Does the same error happen when you launch script manually?
[Android Software/Hacking General [Developers Only]] Keven11:
That log was from it being launched manually. But yes, if I remember correctly it was the same error when flashed as well.
[Android Software/Hacking General [Developers Only]] lebigmac:
@Keven11 @_BJIAD_ @reynaldio19 @Ygrek178 @BartoszDylewski

Try this v1.31d

I just tried it on my Xiaomi device without any issues. It's pretty much the same exact thing as v1.31c except I added in an empty img folder lol. Thanks @reynaldio19 for feedback!

In next version of script I will try to add the option to install script to external sd card rather than to /data/local/tmp.

This will tremendously help those folks that currently cannot mount or decrypt /data in recovery due to Android 11 limitation.

I had same error signal 6 in TWRP but in OrangeFox it works perfectly. I think this error is related to your TWRP.

If you don't have OrangeFox you can launch script manually from terminal. Good luck!
[Android Software/Hacking General [Developers Only]] kpykpy:
Spoiler content hidden.
[Android Software/Hacking General [Developers Only]] lebigmac:
@kpykpy your lpmake arguments look good to me. Did you try yet the included sysrw_repair script (linux only) ? It's made specifically to fix lpmake error 73. Good luck!
[Android Software/Hacking General [Developers Only]] Androidlady:
Confirmed on Rog3

**Additional Info: Stock ROM .143 Root+magisk

Actually it is very easy and painful.

1. download script. Put it in internal storage.

2. Boot to twrp and mount all partitions.

3. install ZIP file

4. Boot back to recovery

5. Format

6. Boot to system

DONE

I would like to thank the developers for this great script!
[Android Software/Hacking General [Developers Only]] lebigmac:
Hi thanks for your interest in this project. Just run script from custom recovery or from within Android. If you encounter lpmake error 73 then run the included troubleshooting repair script (Linux only) afterwards.

Maybe
[Android Software/Hacking General [Developers Only]] zeestats:
Hi bro...

Can we apply it on mi 10T?
[Android Software/Hacking General [Developers Only]] Keven11:
Hi Lebigmac, when you mod the script to output to external storage(SD). Would you also make it delete the original super before packing the new one? That should solve the storage issue. Just a thought.... I'll get you the results from this script very soon. Thanks again a for all you do. Stay rad!
[Android Software/Hacking General [Developers Only]] Androidlady:
Thank you. I did it, and it worked flawlessly.

https://xdaforums.com/t/script-andr...t-system-read-write-r-w.4247311/post-85022279
[Android Software/Hacking General [Developers Only]] zeestats:
Not working on Mi10T....
[Android Software/Hacking General [Developers Only]] lebigmac:
@Androidlady I'm happy it worked for you. Could you please send me your log files? Thank you. It will help me to make the script even better. And you can safely skip steps 4 & 5 in your comment ;)

Hi @zeestats. Please send me your log files if you want me to fix it. Thank you.

Hi Keven11 thanks for your message. It's already possible to output the super_fixed.bin to a custom location using the script's out=x argument. And this patched super file will be automatically deleted after successful flash from recovery.

You can also skip dumping of the original super and directly use your super partition block device as input to the script using the in=/dev/block/sda? parameter.
[Android Software/Hacking General [Developers Only]] Androidlady:
Like i said im new here, tell me how to grab the logs, and ill send them to you.

Will i lose R/W if i factory reset, flash stock firmware, install fota, format or any other recovery?
[Android Software/Hacking General [Developers Only]] arifn82:
not working for me sir. i am using redmi note 10 pro miui android 11. latest twrp by nebrassy. auto install shows this. and manual install sh script did not do anything..please sir, help me
[Android Software/Hacking General [Developers Only]] lebigmac:
Try installing script folder manually or try flashable.zip in orangefox after mounting /data partition. Error signal 6 is related to your twrp...

Your TWRP cannot mount and decrypt /data partition properly. This is new Android 11 limitation I believe.

Please send me this file /tmp/recovery.log
[Android Software/Hacking General [Developers Only]] zeestats:
How to get log.... anybody guide me please...

I'm using Mi10T with EU beta rom..

I got an error 255 while flashing the latest zip...
[Android Software/Hacking General [Developers Only]] bob4294967296:
Hello! It worked on my device (Xiaomi Mi 10T lite -- Global 12.0.9 QJSEUXM).

Thank you a thousand times @lebigmac !

Note that it was not out-of-the-box for my device and here is what I did (it may not work for everyone): because path `/data/local/tmp` was encrypted (same issue as @walid77dz), I first checked that nothing important was inside, then removed the local folder (on Android).

After that, I jumped into OrangeFox and copied the folder systemrw_1.31d on `/data/local/tmp` by keeping the folder structure (the script is on `/data/local/tmp/systemrw_1.31d/systemrw.sh`).

With the terminal, the script was run (without forgetting --size=100) successfully (after a few minutes).

After this step, I erased the files I copied (/data/local/*) and reboot into system. (Note: When I forgot this step, I booted back into recovery.)

So a quick list:

- Download folder and extract it to external SD

- Check and remove (TotalCommander + Root) /data/local

- Reboot to Orangefox and copy systemrw_1.31d from SD to the right place (with recovery explorer)

- Open Terminal and run:

- cd /data/local/tmp/systemrw_1.31d`

- chmod +x systemrw.sh

- ./systemrw.sh --size=100

- Wait for a few minutes

- Erase with recovery explorer `data/local/*` (important)

- Reboot to system

- Post a message here
[Android Software/Hacking General [Developers Only]] zeestats:
Brother can you please make this guide more simple by steps you have done....

Step1

Step2

.

.

.

Thank you..
[Android Software/Hacking General [Developers Only]] kpykpy:
easy use system_repair.sh on windows10 for lpmake super_fixed.bin

Spoiler content hidden.
[Android Software/Hacking General [Developers Only]] Keven11:
Still the same lpmake error 73. Here are the logs... Etc from both flashing from recovery and running manually from termux. Still a no go on the Moto g9+.
[Android Software/Hacking General [Developers Only]] Mikeyd7186:
I have only 16gb of storage is there any way to still do this I get stuck due to storage and am on moto g power 2021 I already moved everything over and deleted everything that I can
[Android Software/Hacking General [Developers Only]] _BJIAD_:
Everything came out successfully with a script 1.29, and manual installation. Poco F3, a11.
[Android Software/Hacking General [Developers Only]] waseemmongol67:
Hey bro can you post a tutorial that how can we do this or a video link in which same method is using....? calvinddude spain
[Android Software/Hacking General [Developers Only]] Keven11:
I'm going to try to run the repair script from a rooted phone connected to the Moto g9+ via otg usb adapter. As my machine is going to be waiting on a coolant pump for a while yet. So, I am stuck with my laptop running windows. Very few things in life piss me off like windows does. The only thing windows Excel's at.
[Android Software/Hacking General [Developers Only]] Keven11:
To get around the storage issue you need to use the "out" option and run it to output to your sd card (has to be setup as external storage not adopted) assuming that you have one. So I am going to show you how assuming you have one that is at least 32gb's. If it's a 32gig card then you should copy all your data to a computer and format it as external storage or "portable" as Moto calls it. So unzip it, open the folder and you should see 2 folders. One is META-INF the other is systemrw_1.31. Move the systemrw_1.31 folder to data/local/temp. Set permissions to 0755 using either a root explorer or in termux: Run "su" (without quotation marks) "chmod 0755 /data/local/temp/*" the asterisk will set perms on the entire folder. Then also in termux as root (or su) "cd /data/local/tmp/systemrw_1.31c" (or "...1.31d" depending on the version). Then "./systemrw.sh size=30 out=/external_sd/super.bin". I hope that helps.
[Android Software/Hacking General [Developers Only]] Keven11:
Delete this
[Android Software/Hacking General [Developers Only]] Keven11:
I forgot to mention that before doing this you will have to delete everything in your /data/local/tmp folder. The only stuff in there will be from flashing the script the first time. You can run those commands from the terminal that is in your custom recovery if you want to. Which recovery are you using? I'm just curious.
[Android Software/Hacking General [Developers Only]] Keven11:
Did you run the repair script with your device in recovery? Also, everytime I've tried this I keep getting an error about having the adb binaries and device usb drivers installed. I do have the drivers and adb/fastboot installed. Do I need to install the Linux adb/fastboot package?
[Android Software/Hacking General [Developers Only]] srdjanLeo:
This actually worked!!! Thanks!

Is there a way, perhaps, to make this work with VENDOR folder? I'm using Samsung S9 Pixel Experience A11 ROM, and I need Vendor folder to be r/w as well. Thanks and keep up good work!
[Android Software/Hacking General [Developers Only]] lebigmac:
Hi. By default script will try to change system, product and vendor from R/O to R/W. Thanks.

Hi Keven11. The troubleshooting repair script should work while phone is in custom recovery or in Android mode.

What result do you get if you type this in your Linux terminal? which adb

If you're using virtual Linux machine make sure you enable USB connections before running repair script and make sure you can properly connect to phone through the USB cable!

Hi @kpykpy what custom size did you use? Maybe it was too much? Try with smaller custom size ;) Good luck!

Hi @Mikeyd7186. As Keven already mentioned you could use the script's out=/custom/path/super_fixed.bin parameter to export the patched super file to your external SD card.

You could also skip dumping of original super by directly using your super partition block device as input to the script like this (make sure you've got a backup of your original super image on your computer in case something goes wrong!)

adb shell
su
cd /data/local/tmp/systemrw_1.31d
chmod +x ./systemrw.sh
./systemrw.sh size=15 out=/external_sd/super_fixed.bin in=`ls -l /dev/block/by-name/super | awk '{print $NF}'`

Hi @zeestats log should be here /tmp/recovery.log

Hi @ctopoj2015 try downloading through proxy. Good luck!
[Android Software/Hacking General [Developers Only]] kpykpy:
in log.zip

15MB
[Android Software/Hacking General [Developers Only]] kpykpy:
i edited script

on windows10 install debian from microsoft store

move files from phone from super dir to pc

and run repair script on pc

//you try

on windows10 install debian from microsoft store

connect phone to pc

check adb devices on this debian

and run repair script on this debian
[Android Software/Hacking General [Developers Only]] Keven11:
Ahhh ok, that's the part I was missing. Thanks.
[Android Software/Hacking General [Developers Only]] lebigmac:
@Keven11 don't worry in next version of troubleshooting repair script I will include platform-tools ;)
[Android Software/Hacking General [Developers Only]] skinlab:
can this be flashed in magisk?
[Android Software/Hacking General [Developers Only]] skinlab:
double post
[Android Software/Hacking General [Developers Only]] lebigmac:
Hello thanks for your interest in this project. No idea what you mean. It can be flashed in custom recovery (TWRP, OrangeFox, PBRP)

If you get error signal 6 in recovery try decrypt and mount /data partition first!
[Android Software/Hacking General [Developers Only]] skinlab:
I tried to do it manually and it said permission denied. I have the Motorola One 5G Ace metro pcs

I dont think there is a recovery for this phone yet
[Android Software/Hacking General [Developers Only]] skinlab:
Im a dope .. I didnt run su.. But now when i run it in terminal emulator nothing happens
[Android Software/Hacking General [Developers Only]] Keven11:
I think I got debian working on windows. With phone connected via usb with the command "which adb" I get "/usr/bin/adb". So I hope that I can finally get this to work.
[Android Software/Hacking General [Developers Only]] xatornet:
Hi there,

First of all, great project.

Secondly, I'm using a Oneplus 8T with the latest OOS beta 5. Script works while creating super_original.bin, then does all the imgs but, on the last step, creating the big super_fixed.img, my device seems to lack space (error 70) , or something. I've tried to use output:/sdcard/IMGs/superfixed.bin or similar but, It won't do it.

What can I do? It's fresh formatted. I'll append the whole console log.
[Android Software/Hacking General [Developers Only]] xatornet:
delete this
[Android Software/Hacking General [Developers Only]] lebigmac:
Hi thanks for feedback. Can you please send me myargs.txt and lpdump.txt they should be inside /data/local/tmp/systemrw_1.31d/log/

It's the OnePlus COW error. @BlazingKahn35 had the same problem.

It's possible to solve this puzzle don't worry ;)

Maybe a small modification to the script source code can make it work on all OnePlus devices (y)
[Android Software/Hacking General [Developers Only]] xatornet:
Sure, there you have it both, I hope it helps
[Android Software/Hacking General [Developers Only]] lebigmac:
@xatornet if you check your lpdump output you can see that there is only 1.45 GB free space available in your super image but your cow files require a total of 1.62 GB. Can we simply skip the cow files when putting everything back together? Will OnePlus still boot without cow files? What exactly are these COW partitions in OnePlus devices good for anyway?

In your lpdump output total cow size is 0 bytes but on your device total cow size is 1742626816 bytes or 1.62 GB. Which one is the true size?

What happens if you run these commands? These are the same lpmake arguments without the cow files.

adb shell
su
cd /data/local/tmp/systemrw_1.31d
./tools/lpmake --metadata-size 65536 --super-name super --sparse --metadata-slots 3 --device super:7516192768 --group cow:0 --group qti_dynamic_partitions_b:6438256640 --partition system_b:none:1440481280:qti_dynamic_partitions_b --image system_b=./img/system_b.img --partition system_ext_b:none:1252487168:qti_dynamic_partitions_b --image system_ext_b=./img/system_ext_b.img --partition product_b:none:1493516288:qti_dynamic_partitions_b --image product_b=./img/product_b.img --partition vendor_b:none:1688379392:qti_dynamic_partitions_b --image vendor_b=./img/vendor_b.img --partition odm_b:none:72867840:qti_dynamic_partitions_b --image odm_b=./img/odm_b.img --output ./img/super_fixed.bin
[Android Software/Hacking General [Developers Only]] xatornet:
Well... I thought you could tell me what where those cow images... Cuz I've never ever seen them, even using the payload dumper, there are none. I don't know why or how they get created :-(

Also, on the commands you've posted, this happens:

C:\Users\Alex>adb shell

OnePlus8T:/ $ su

OnePlus8T:/ # cd /data/local/tmp/systemrw_1.31d/

i_dynamic_partitions_b --image odm_b=./img/odm_b.img --output ./img/super_fixed.bin <

Invalid sparse file format at header magic

Invalid sparse file format at header magic

Invalid sparse file format at header magic

Invalid sparse file format at header magic

Invalid sparse file format at header magic

Then i've rebooted, system works but still no RW
[Android Software/Hacking General [Developers Only]] lebigmac:
@xatornet check in /img folder (next to /log folder) if super_fixed.bin was successfully created. If it was then try flashing it in fastboot and report back... And please show some screenshots. Thanks!

If flashing is unsuccessful you can always flash back super_original.bin the same way. Good luck!
[Android Software/Hacking General [Developers Only]] xatornet:
Yes, it was created:

OnePlus8T:/data/local/tmp/systemrw_1.31d # ls -l ./img

total 20629756

-rw-r--r-- 1 root root 72867840 2021-05-22 01:05 odm_b.img

-rw-r--r-- 1 root root 1493516288 2021-05-22 01:06 product_b.img

-rw-r--r-- 1 root root 5911617000 2021-05-22 01:08 super_fixed.bin

-rw-r--r-- 1 root root 7516192768 2021-05-22 01:05 super_original.bin

-rw-r--r-- 1 root root 1402888192 2021-05-22 01:06 system_b-cow.img

-rw-r--r-- 1 root root 1440481280 2021-05-22 01:06 system_b.img

-rw-r--r-- 1 root root 339738624 2021-05-22 01:05 system_ext_b-cow.img

-rw-r--r-- 1 root root 1252487168 2021-05-22 01:06 system_ext_b.img

-rw-r--r-- 1 root root 1688379392 2021-05-22 01:06 vendor_b.img

and seems to flash something, but no luck with allowing RW. Don't know what the hell has OnePlus done with OOS...