[Android General] zarkotom:
I am attempting this method of flashing a GSI but I'm getting an error on process #2 of patching the recovery.img. I am pasting the log:

View attachment 6100059

General
Run chmod a+x script2.sh

open: ../r.img failed with 2: No such file or directory

./script2.sh: line 8: /home/runner/work/Patch-Recovery/Patch-Recovery/magiskboot: No such file or directory

./script2.sh: line 9: /home/runner/work/Patch-Recovery/Patch-Recovery/magiskboot: No such file or directory

./script2.sh: line 10: /home/runner/work/Patch-Recovery/Patch-Recovery/magiskboot: No such file or directory

./script2.sh: line 11: /home/runner/work/Patch-Recovery/Patch-Recovery/magiskboot: No such file or directory

./script2.sh: line 12: /home/runner/work/Patch-Recovery/Patch-Recovery/magiskboot: No such file or directory

./script2.sh: line 13: /home/runner/work/Patch-Recovery/Patch-Recovery/magiskboot: No such file or directory

./script2.sh: line 14: /home/runner/work/Patch-Recovery/Patch-Recovery/magiskboot: No such file or directory

./script2.sh: line 15: /home/runner/work/Patch-Recovery/Patch-Recovery/magiskboot: No such file or directory

./script2.sh: line 16: /home/runner/work/Patch-Recovery/Patch-Recovery/magiskboot: No such file or directory

./script2.sh: line 17: /home/runner/work/Patch-Recovery/Patch-Recovery/magiskboot: No such file or directory

./script2.sh: line 18: /home/runner/work/Patch-Recovery/Patch-Recovery/magiskboot: No such file or directory

./script2.sh: line 19: /home/runner/work/Patch-Recovery/Patch-Recovery/magiskboot: No such file or directory

./script2.sh: line 20: /home/runner/work/Patch-Recovery/Patch-Recovery/magiskboot: No such file or directory

cp: cannot stat 'new-boot.img': No such file or directory

wc: recovery.img: No such file or directory

usage: avbtool add_hash_footer [-h] [--image IMAGE]

[--partition_size PARTITION_SIZE]

[--dynamic_partition_size]

[--partition_name PARTITION_NAME]

[--hash_algorithm HASH_ALGORITHM] [--salt SALT]

[--calc_max_image_size]

[--output_vbmeta_image OUTPUT_VBMETA_IMAGE]

[--do_not_append_vbmeta_image]

[--algorithm ALGORITHM] [--key KEY]

[--signing_helper APP]

[--signing_helper_with_files APP]

[--public_key_metadata KEY_METADATA]

[--rollback_index ROLLBACK_INDEX]

[--rollback_index_location ROLLBACK_INDEX_LOCATION]

[--append_to_release_string STR]

[--prop KEY:VALUE] [--prop_from_file KEY:PATH]

[--kernel_cmdline CMDLINE]

[--setup_rootfs_from_kernel IMAGE]

[--include_descriptors_from_image IMAGE]

[--print_required_libavb_version]

[--chain_partition PART_NAME:ROLLBACK_SLOT:KEY_PATH]

[--flags FLAGS] [--set_hashtree_disabled_flag]

[--use_persistent_digest] [--do_not_use_ab]

avbtool add_hash_footer: error: argument --partition_size: expected one argument

Error: Process completed with exit code 2.
code

Anyone got a clue why this is happening? I am trying it with stock A145R firmware, February 2024 security patch version, same result with April 2024 version, I am downloading the earliest available version to try as well (October 2023).

This is the last method of flashing a GSI I have left to try. Nothing has worked, furthest I've gotten has been a bootloop on AOSP (flashed via TWRP).