|
|
|
|
|
|
by zozbot234
2256 days ago
|
|
|
> The reason seems to be there are no way for them to get around the bootloader of a standard Android phone to boot an encrypted UBport. How so? The bootloader only boots what is in the boot partition, it shouldn't even care about anything else if it's properly unlocked. The only issue on standard AOSP is that encryption there affects the entire 'userdata' partition, so the OS must manage to boot and prompt for a password while only accessing the "system" partition, which is relatively small on many devices. But that's no different than booting a system that has had its userdata wiped (either as part of bootloader unlock or for recovery). |
|
|