I see a large number of posts stating that users ended up with their device going into a bootloop after flashing TWRP.
If TWRP is flashed to the /recovery/ partition, how is it possible for the device to go into a bootlop during a normal start up?
Asked
Active
Viewed 44 times
0
-
1when altered a partition, that fails to pass the dm-verity sanity check – alecxs Aug 18 '20 at 20:55
-
what relation does dm-verity have with android verified boot? – Dinesh Gami Aug 18 '20 at 21:10
-
2dm-verity is verified boot (at runtime) while AVB is verification of partitions (during flash or boot) – alecxs Aug 18 '20 at 21:16
-
is there any relation between unlocking the bootloader and dm-verity or AVB? – Dinesh Gami Aug 19 '20 at 13:40
-
1that are three different pieces in the chain of trust, but it all goes hand in hand – alecxs Aug 19 '20 at 14:14
-
so dm-verify needs to be disabled via adb first prior to installing a custom recovery or else the device will boot loop? – Dinesh Gami Aug 22 '20 at 11:07
-
1you can flash custom recovery and install disable_dm-verity.zip or no-verity-opt-encrypt.zip or magisk.zip to disable dm-verity. if AVB is problem for custom recovery, you can flash empty vbmeta.img to disable AVB – alecxs Aug 22 '20 at 14:55
-
Does this answer your question? What creating bootloop when flashing TWRP? – alecxs Jan 10 '21 at 18:13