[Android Software/Hacking General [Developers Only]] lebigmac:
Hello @mions_lv thanks for uploading your logs.

Error 73 (CAN'T_CREATE) can be easily fixed with troubleshooting repair script (Linux only) that's included in the v1.31d BUNDLE. ✅

It would be cool if some genius could tell me why Error 73 (CAN'T_CREATE) occurs only on android device but not inside linux using exactly the same lpmake arguments. It's still a big mystery to me. Selinux is disabled.

Hello. Thanks for sharing your log files! (y)

It looks like your device have the COW error. Here are 2 possible solutions for you and at least one of them will most likely cause bootloop. Be prepared to restore a backup of your super_original.bin if you get stuck in a bootloop. Proceed at your own risk!

Option A:

adb shell
su
cd /data/local/tmp/systemrw_1.31d
> ./img/system_a-cow.img
./tools/lpmake --metadata-size 65536 --super-name super --sparse --metadata-slots 3 --device super:9126805504 --group cow:0 --group qti_dynamic_partitions_a:9126805504 --partition system_a:none:3096711168:qti_dynamic_partitions_a --image system_a=./img/system_a.img --partition system_ext_a:none:484626432:qti_dynamic_partitions_a --image system_ext_a=./img/system_ext_a.img --partition product_a:none:1508950016:qti_dynamic_partitions_a --image product_a=./img/product_a.img --partition vendor_a:none:1969164288:qti_dynamic_partitions_a --image vendor_a=./img/vendor_a.img --partition odm_a:none:134217728:qti_dynamic_partitions_a --image odm_a=./img/odm_a.img --partition system_a-cow:none:0:cow --image system_a-cow=./img/system_a-cow.img --output ./img/super_fixed.bin

exit; exit

adb pull /data/local/tmp/systemrw_1.31d/img/super_fixed.bin
adb reboot bootloader
fastboot flash super super_fixed.bin

Option B:

adb shell
su
cd /data/local/tmp/systemrw_1.31d
./tools/lpmake --metadata-size 65536 --super-name super --sparse --metadata-slots 3 --device super:9126805504 --group qti_dynamic_partitions_a:9126805504 --partition system_a:none:3096711168:qti_dynamic_partitions_a --image system_a=./img/system_a.img --partition system_ext_a:none:484626432:qti_dynamic_partitions_a --image system_ext_a=./img/system_ext_a.img --partition product_a:none:1508950016:qti_dynamic_partitions_a --image product_a=./img/product_a.img --partition vendor_a:none:1969164288:qti_dynamic_partitions_a --image vendor_a=./img/vendor_a.img --partition odm_a:none:134217728:qti_dynamic_partitions_a --image odm_a=./img/odm_a.img --output ./img/super_fixed.bin

exit; exit

adb pull /data/local/tmp/systemrw_1.31d/img/super_fixed.bin
adb reboot bootloader
fastboot flash super super_fixed.bin

Hi it was about time you guys finally got a custom recovery!

I'm sure there's an easy way to fix error 73 on the device itself. I don't see why it should work in linux but not in android. :unsure:

Hi master @munjeni

Thanks for your comment!

I think you were right all along and folks without a super partition don't even have 'shared_blocks feature' 😂

That means I put all that extra code in there for nothing! :ROFLMAO:

How many total lines of code is the final version of your super sophisticated tool?

Hello. Thank you for the kind words. It works? Please show screenshot or log. Thanks! (y)

Enjoy debloating your device! Don't forget to create lots of backups before modifying your system to your liking. Always reboot your device after every system modification to see if there's a bootloop!

Hi @Bontot7. Thanks for feedback. Please show screenshot or log. Thank you! (y)

I'm happy it works for you. Please see my comment to harvey above. Same advice applies to you ;) Enjoy debloating your device!

Hello. You mean script actually works inside emulator? What a surprise!

Can you boot into recovery inside emulator? Then you can flash super with dd. I take no responsiblity if you brick your emulator :LOL:

Why are you running it in emulator? Try running script from real device while booted into Android. It won't flash anything to your device don't worry 😉

Hi tomxyz. Please send me your log files. Thanks. Were you able to fix your bootloop by restoring the original unmodified super image? :unsure:

Hello psi.singh. Thank you for the good news! (y) I'm happy it works for you. What exactly is MIUIMix ? Is this custom ROM?

Could you please send me your log files? Thank you. It helps with further development of the script ;)

Thank you for chiming in (y) Did you try the script yet?

Hello @hallo6459

Please send me your log files. Thank you. It helps understand what happened on your device.

After successfully running script the file size difference between super_fixed and super_original is normal. One file is sparse while the other one is in raw format.

What happens if you do this while booted into Android?

Hi @Myt7930 In next version of script I will try to fix this error. Don't worry ;)

In the meantime please try launching script manually according to the instructions. Good luck!

Thanks for your feedback @PEACH-PIT. I don't understand why it throws error 73 in Android and in Linux it just works using the same lpmake arguments?!

Hi @mathan7. Please send me your log files so I can take a closer look. Thank you.

Hi @QanTnkz. In next version of script all cow related stuff will be automatically removed from arguments list. Hopefully this will fix cow error ;)

Try running script in emulator then :LOL: Good luck!