Release 0.5.0-beta

[tsterbak]

This release adds:

• Allow flashing a custom recovery with a toggle switch.
• Display device specific notes at the image selection step (thanks to @anon1892)
• Include the commands fastboot_flash_recovery and fastboot_reboot_recovery (thanks to @anon1892)
• Add support for Samsung Galaxy S5 LTE (klte).
• Add support for Mi439 (Redmi 7A & co.) (thanks to @anon1892)
• Add support for lavender (Xiaomi Redmi Note 7) (thanks to @anon1892)
• Add support for ginkgo (Xiaomi Redmi Note 8 / 8T) (thanks to @anon1892)
• Add support for garden (Xiaomi Redmi 9A & co.) (thanks to @anon1892)
• Add support for rosemary (Xiaomi Redmi Note 10S & co.) (thanks to @anon1892)
• Add support for miatoll (Xiaomi Redmi Note 9 Pro / 9S ... Poco M2 Pro) (thanks to @anon1892)
• Add support for davinci (Xiaomi Mi 9T / Redmi K20) (thanks to @anon1892)
• Add support for raphael (Xiaomi Mi 9T Pro / Redmi K20 Pro) (thanks to @anon1892)
• Add support for vayu (Poco X3 Pro) (thanks to @anon1892)
• Add support for cupid (Xiaomi 12) (thanks to @anon1892)

Fixes:

• make fastboot_unlock_critical properly accessible.
• Add missing alternative device codes for Samsung S9 and S10 (thanks to @MagicLike)
• Fix the bug with the progress bar percentages (resolves Install OS progress goes to 100% but need more time to complete #181)
• Display the scroll bar by default if scrolling is necessary
• An info text box for additional images

Other news:

• Actions for releases are upgraded (by @MagicLike)
• Reworked the device request template as form (by @MagicLike)
• Updated bootloader unlock info (by @freechelmi)

Todo:

• Test flashing with already installed recovery.
• Add new devices to the README
• Update the website with new devices

[tsterbak]

This is most likely the final state for the release planed on Friday. Feel free to test it or suggest things that are missing :)
Thanks for everyone involved so far!

[ghost]

Wow, happy to see all these changes being merged!
There is occurrence of untested optional metadata in README, but not in device confs neither in code : I checked too fast or it was forgotten in the process? (The code just shows a warning when the device is untested...)

[tsterbak]

There is occurrence of untested optional metadata in README, but not in device confs neither in code : I checked too fast or it was forgotten in the process? (The code just shows a warning when the device is untested...)

I removed it from the configs, because the config validation failed. But good point, I will better fix the validation and put the metadata field back, where required :)

[MagicLike]

There is occurrence of untested optional metadata in README, but not in device confs neither in code : I checked too fast or it was forgotten in the process? (The code just shows a warning when the device is untested...)

I removed it from the configs, because the config validation failed. But good point, I will better fix the validation and put the metadata field back, where required :)

Will you fix it before the release or will it be part of 0.4.6 / a hotfix?

[tsterbak]

Will you fix it before the release or will it be part of 0.4.6 / a hotfix?

I will fix it for this release.

[MagicLike]

Will you fix it before the release or will it be part of 0.4.6 / a hotfix?

I will fix it for this release.

Then I will not approve the configs where a untested tag is needed 👍

[MagicLike]

Will you fix it before the release or will it be part of 0.4.6 / a hotfix?

I will fix it for this release.

@tsterbak Should we wait with the release for this? #287 (comment)

[MagicLike]

LGTM - just waiting for the untested metadata to get fixed for cupid, davinci, ginko, miatoll, raphael, rosemary and vayu.

[tsterbak]

@tsterbak Should we wait with the release for this? #287 (comment)

No, it think we can go out like this. This will also be a test for the "untested" metadata. If we start supporting untested devices, I guess this is the way to go :)

[tsterbak]

This release will be postponed until Monday, since I want a bit more time for testing and not release Friday afternoon :D

[RaptaG]

Are the upcoming devices tested?

[ghost]

Are the upcoming devices tested?

Some are, some aren't, but behaves the same way others tested device do. See untested metadata.

[RaptaG]

Some are, some aren't, but behaves the same way others tested device do. See untested metadata.

I see, miatoll (my device) is untested sadly and I fear in case of something bad happens, I don't wanna risk my main device.. Does anybody here who has this model (and is willing to) test it?

[tsterbak]

It is released now! 🎊
Also, I decided to release it as 0.5.0-beta, since quite a lot of things were added and I thought following semantic versioning a bit better would be good.

Great work everyone involved! :)