Oh no! Not Error 73 againError 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).
/**
* Can't create (user) output file.
* A (user specified) output file cannot be created.
*/
#define EX_CANTCREAT 73
I have flashed on my motorola g 5g plus. I have rebooted into twrp and can mount the boot, system and vendor partitions.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!
setGlobalVars(){
pDumpDir="./nosuper"
sDumpDir="./img"
mkdir -p $pDumpDir $sDumpDir
)@pandavova thanks for the nice log files feedback! It's very helpful.
Oh no! Not Error 73 again
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
Add img folder to flashible zipI Have "dd: ./img/super_original.bin: no such file or directory
systemrw: Error: Failed to dump file to: ./img/super_original_bin
Please help
How to uninstall this..back to r/o...??Don't worry guys I will fix /img path error very soon!
In the meantime please try manual installation as described here
Click here
I get error unknown partition super_fixed.bin
Fastboot error: can not determine image filename for super_fixed.bin
Poco F3, Android 11. Date is available.Which device are you using? I've seen this error before. Maybe /data partition unavailable?
adb shell
su
mount -o remount,rw /
mount -o remount,rw /odm
mount -o remount,rw /product
mount -o remount,rw /system_ext
mount -o remount,rw /vendor
mount | grep dm- | head -5
chmod +x /data/local/tmp/sysrw_*VERSION*/sysrw
adb shell
su
cd /data/local/tmp/sysrw_1.33
chmod +x ./sysrw
# Run program with default settings [RECOMMENDED]
./sysrw
# Specify existing super image as input [OPTIONAL]
./sysrw in=./img/super_original.img
# Specify patched super image output file path [OPTIONAL]
./sysrw out=./img/super_patched_new.img
# Specify the extra free space (in megabytes) to be added to each sub-partition of super.img [OPTIONAL]
./sysrw size=15
# Specify whether or not the patched super image should be output in raw file format [OPTIONAL]
./sysrw -r
# EXPERT EXAMPLE (Warning! This command could potentially corrupt your system. Only use at your own risk in recovery mode!)
./sysrw in=img/super_original.bin out=`realpath /dev/block/by-name/super` -r
/data/local/tmp/sysrw_*VERSION*/img
/data/local/tmp/sysrw_*VERSION*
chmod +x ./sysrw
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./data/local/tmp
directory and that the containing files are not encrypted in custom recovery!/data/local/tmp/systemrw_1.32/log/
This is awesome! Unfortunately, it doesn't support Android 12 yet : ( .
sdkCheck(){
sdkVersion=`getprop ro.build.version.sdk`
if [ $sdkVersion -lt 29 ]; then
printf "$app: Please install Android 10 or newer and try again\n\n" && exit 1
else
android=$(($sdkVersion - 19))
fi
printf "$app: Current Android version: %s\n" $android
}