From 4c4f1047cdd9d88cd4b16780b53adcccda2aa870 Mon Sep 17 00:00:00 2001 From: melontini <104443436+melontini@users.noreply.github.com> Date: Sat, 5 Oct 2024 00:54:32 +0700 Subject: [PATCH] Mention custom AVB keys --- README.md | 6 ++++++ brands/google/README.md | 2 ++ 2 files changed, 8 insertions(+) diff --git a/README.md b/README.md index 4a617cd..717fea7 100644 --- a/README.md +++ b/README.md @@ -70,6 +70,12 @@ If you know of specific details/unlocking methods, please PR them or drop them i # Misc info +## Custom AVB Keys + +Custom Android Verified Boot keys is a feature which allows you to run a custom OS with a locked bootloader. + +It's rare to see a device which supports custom AVB keys, but some devices can be found [here](https://github.com/chenxiaolong/avbroot/issues/299). + ## Universal SOC-based methods ### Kirin diff --git a/brands/google/README.md b/brands/google/README.md index 4e0a2ae..37d953e 100644 --- a/brands/google/README.md +++ b/brands/google/README.md @@ -4,5 +4,7 @@ Allows unlocking on almost any non-carrier locked device, but is also a pioneer in making rooting and custom ROMs painful with things like Safety Net and Play Integrity. With the latest feat being RCS messaging which requires DEVICE integrity to work. (To prevent "spam", of course) +Google is also one of the few OEMs to support custom AVB keys. + *** Authored by [melontini](https://github.com/melontini). \ No newline at end of file