awesome-android/avbroot
3
0
Fork 0
mirror of https://github.com/chenxiaolong/avbroot.git synced 2026-07-03 14:05:11 +02:00
Code Issues Packages Projects Releases Wiki Activity

Merge pull request #243 from chenxiaolong/repair_mode

Browse Source 
README.md: Document Repair Mode
This commit is contained in:
Andrew Gunnerson
2023-12-29 20:39:22 -05:00
committed by GitHub
parent da17935972 124629dc45
commit c9633682ef
1 changed files with 18 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
README.md
+18
View File
@@ -233,6 +233,24 @@ This is especially important for some custom OS's because their system updater a
To self-host a custom OTA server, see [Custota](https://github.com/chenxiaolong/Custota).
## Repair mode
Some devices now ship with a Repair Mode feature that boots the system with a fresh `userdata` image so that repair technicians are able to run on-device diagnostics without needing the user's credentials to unlock the device.
When the device is rooted, it is unsafe to use Repair Mode. Unless you are using release builds of Magisk/KernelSU signed with your own keys, it's trivial for someone to just install the Magisk/KernelSU app while in repair mode to gain root access with no authentication.
To safely use Repair Mode:
1. Unroot the device by repatching the OTA with the `--rootless` option (instead of `--magisk` or `--prepatched`) and flashing it.
2. Turn on Repair Mode.
3. After receiving the repaired device, exit Repair Mode.
4. Flash the (rooted) patched OTA as normal.
Because the unrooting and rooting are done by flashing OTAs, the device's data will not be wiped.
## avbroot modules
avbroot's Magisk/KernelSU modules can be downloaded from the [releases page](https://github.com/chenxiaolong/avbroot/releases).