Byteang3l Even if the duress PIN didn’t trigger, this doesn’t automatically mean the device was easily accessible. AFU mode still keeps encryption keys in memory, the bootloader was locked, and accessing raw data would require very sophisticated hardware attacks that are not standard for police, and not something the Belgian government has access to, and certainly not in the time span mentioned here. Without detailed logs or evidence, it’s hard to accept this as proof of a GrapheneOS compromise, it could be an unusual one in a million bug, or a one in a billion flaw with your specific titan chip, but it’s not a widespread vulnerability as it stands now. If you can provide evidence down the line, we absolutely implore you to share it here when it becomes available, if the admins wanted this thread gone it already would be, so it should be here in the future when that information becomes available.
I understand your point AFU mode, a locked bootloader, and standard encryption do make unauthorized access difficult under normal circumstances. The issue I’m reporting is specific to the native GrapheneOS duress PIN failing to trigger the wipe. I’m not claiming a widespread vulnerability, only that in this case, the duress action did not execute as designed, and the data became accessible afterward.
I have shared all the factual details I can at this time. If additional evidence becomes available later, it will be provided. Until then, this post reflects exactly what happened on this device, without speculation about broader hardware capabilities or general security of GrapheneOS.