Giter Club home page Giter Club logo

patch-recovery's People

Contributors

johx22 avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar

patch-recovery's Issues

Remove zip verification

Please add zip verification disabler script or something like that. I would like to have a way to flash root zips and since from fastboot is not possible maybe you can add patches to disable zip verification on recovery. Thank you

f-droid.org/F-Droid.apk.asc

"-----BEGIN PGP SIGNATURE-----

iQGzBAABCgAdFiEEgCqXmQFhEjRuH+/0egKeVN1dznoFAmS7wgwACgkQegKeVN1d
znoDVgv/dI2B+lTnfgNXT51lK8Z2yCjbW584tfVh6Y4joj+JC+YIxTfcXHqjCmvo
BLVAL/dQViPPsKp2ms4SWuRFOO6h1gcy407a4OYMBEMyQ/WmPDVYk9qJ8th+JSyF
Q27nyyOAgTzimp49Tyxq3ccHSqGl3zVM188p47Wb1fDXtOzMeuAMS4C0/r026T5u
0WuGZeTb1keIjpG2h+mgV5P4h71+41orQfS1i5aImVpo4CJj8AVR6w+MQ8XP3r7u
nGS3PFa6sbucfT6N59zzBVc1ebUwE+OwHy8NLTBLfhPGBSA27RQNNyRuTqPfgRx7
h+31L0AqTRNVO+bHftaeifi50LqE/zqVipLn0H6KA41McZnsGGhDABu7mdbG8IKN
f2ArUYb6RmoB5tVhapC0GtBuhZF8tjrIE1k6pvcVrUJ0hZw/BTqiGyBfLKvZfHUN
Jhc1iJQjl7Ehzlu8zJ8E4W/xZJ7enMLr6LDf0/3qt/wv1zhfHJvdgLbESizUiJMA
MRxCNOOF
=72aX
-----END PGP SIGNATURE-----"
https://f-droid.org/F-Droid.apk.asc#:~:text=%2D%2D%2D%2D%2DBEGIN%20PGP%20SIGNATURE,END%20PGP%20SIGNATURE%2D%2D%2D%2D%2D

Issue on step 2

I'm getting an error on process #2 of patching the recovery.img. I am pasting the log:

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.

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

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).

script2.sh fails to run

I've been trying to patch the recovery.img of my Galaxy A03 Core. I keep getting this error.

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

Can you help please?

Updated version of this repository

There are some issues with these scripts that I've spent a while fixing, and also the version of magiskboot used here is outdated, so if no update to fix these issues is intended, can you archive and/or link my repository to this one, so development can be moved?

Thank you~

where..?

i uploded my recovery.img to file hosting service.but where i need to paste that link.how to patch my recovery.img.?

FastbootD Access?

A friend of mine ask me to patch his stock recovery, done, and flashed it successful. But Booting into fastbootD seems a bit hard. Is there a way to boot into fastboot? command like: adb reboot fastboot, didnt work, just rebooting back to system.

Workflow Failing on Patch Process-2

it fails with:
open: ../r.img failed with 2: No such file or directory open: system/bin/recovery failed with 2: No such file or directory open: system/bin/recovery failed with 2: No such file or directory open: system/bin/recovery failed with 2: No such file or directory open: system/bin/recovery failed with 2: No such file or directory open: system/bin/recovery failed with 2: No such file or directory open: system/bin/recovery failed with 2: No such file or directory open: system/bin/recovery failed with 2: No such file or directory open: system/bin/recovery failed with 2: No such file or directory open: system/bin/recovery failed with 2: No such file or directory open: system/bin/recovery failed with 2: No such file or directory open: system/bin/recovery failed with 2: No such file or directory open: system/bin/recovery failed with 2: No such file or directory open: ../r.img failed with 2: 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.

Add a licence

Hello I am assuming you dont mind the project being open source, as such for others to use it legally there needs to be a license. Please read this GitHub article to better understand what I am asking, I have quoted it below.

"You're under no obligation to choose a license. However, without a license, the default copyright laws apply, meaning that you retain all rights to your source code and no one may reproduce, distribute, or create derivative works from your work. If you're creating an open source project, we strongly encourage you to include an open source license. The Open Source Guide provides additional guidance on choosing the correct license for your project."

Can you please add a license to the project, I generally use GPLV2 but whichever is in alignment with your views is fine.

Thank you - MrWicked

patched recovery break device (patched locally and installed by heimdall)

  • Steps to reproduce
  1. Clone repo
  2. Move recovery file in repo
  3. Make scripts executable
  4. Change path in Script2
  5. Run Script1
  6. Run Script2 with root
  7. Got recovery-patched.imp (not tar)
  8. Go to Samsung download mode
  9. Get device's recovery partition name
  10. Run heimdall flash --recovery recovery.img --no-reboot

Device show bootloader warning but cannot press power button and
keeps rebooting.

Fixed by restoring old recovery

it works but no effect

i followed instractions and it created sucsessfully but there is not any thing new and stuck in the normal fastboot

transfer.sh error

transfer.sh seems to be broken. When it finishes uploading the recovery image file, it gives an error 500 and doesn't generate a download link. I've tried other sites like mediafire and google drive but none of them seem to work.

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.