My GrapheneOS was cracked by Belgian police

n3t_admin

b8r2 okay, I call the bluff here: so after the "feds" entered the (maybe incorrect) duress PIN, they were like: oh, it's wrong, have a nice day Sir! They didn't ask for a different PIN, they didn't retry it, they didn't ask why it was wrong? So many questions...

b8r2

n3t_admin okay, I call the bluff here: so after the "feds" entered the (maybe incorrect) duress PIN, they were like: oh, it's wrong, have a nice day Sir! They didn't ask for a different PIN, they didn't retry it, they didn't ask why it was wrong? So many questions...

Due to operational security, I cannot share every detail about the device or what occurred, but the key fact remains: the duress PIN was entered, the secure wipe did not execute, and the data was subsequently accessible.

b8r2

Novalissoide The USB-wipe mention was in response to an earlier comment, not something I used on the device. The device itself was running standard GrapheneOS, and the issue occurred solely with the native duress PIN, which failed to trigger the secure wipe.

Novalissoide

b8r2 The USB-wipe mention was in response to an earlier comment, not something I used on the device

No further questions from me.

Hathaway_Noa

b8r2

You had USB wipe on your phone, which means you had wasted app infrastructure on your phone. Don't pretend it's not true. Also the way you write and speak makes me think you are not a criminal phisser but rather someone who is trying to make grapheneOS look bad.

b8r2

Novalissoide No further questions from me.

What makes you think ADB or Shizuku were used on the device?

b8r2

Hathaway_Noa You had USB wipe on your phone, which means you had wasted app infrastructure on your phone. Don't pretend it's not true. Also the way you write and speak makes me think you are not a criminal phisser but rather someone who is trying to make grapheneOS look bad.

The mention of a “USB wipe” was in response to an earlier comment it was not something installed or used on my device. I did not use Wasted or any third-party app. The issue I’m reporting concerns only the native GrapheneOS duress PIN, which failed to trigger the secure wipe. Nothing else contributed to the outcome.

Byteang3l

b8r2 what surprises me is you allegedly have had a warrant for pre-meditated murder since the creation of this post according to your attorney, yet here you are readily talking to us on this forum. How do you manage that especially with an ankle monitor on?

b8r2

Byteang3l I don't have a ankle monitor.

Novalissoide

b8r2 well, the use of Wasted. And that Adb, Shizuku and Developer options causes around two thirds of the issues with screenlock that I tried to help users with.

Hathaway_Noa

b8r2 you literally said on Twitter:

"the USB duress also failed"

Byteang3l

b8r2 Basically i was suspected of a murder. I went to jail, got out on a ankle monitor because there was not enough evidence.

Your comment literally says you have an ankle monitor, or did they take it off after your warrant was issued without arresting you? This story has more holes than Swiss cheese buddy.

b8r2

Byteang3l Ankle monitor was taken off roughly 4months before the warrant.

b8r2

Novalissoide none of those were used. The device was a standard GrapheneOS installation

hemingway

b8r2 After the duress PIN was entered, the device remained powered on and no wipe occurred

Did it say "incorrect pin entered" or did it unlock the device? That's why I'm wondering about the fed's reaction since you mentioned you could not see what happened after the pin was entered.

b8r2

hemingway The device did not display “incorrect PIN” nor did it unlock.

b8r2

Hathaway_Noa This was a response to someone, i most likely confused with it

indigomadelin Insults don’t change the facts of what happened. I’ve stated the technical details I can share, and personal attacks don’t add anything to the discussion.

Byteang3l

b8r2 and what we want to know is how this data became accessible afterwards, there's a vital piece of this story missing between duress allegedly failing and your phone being unlocked and fully accessible, duress failing doesn't explain that.

b8r2

Byteang3l and what we want to know is how this data became accessible afterwards, there's a vital piece of this story missing between duress allegedly failing and your phone being unlocked and fully accessible, duress failing doesn't explain that.

The factual part I can confirm is that the duress PIN was entered, the secure wipe did not execute, and the data ultimately became accessible. I cannot provide specifics beyond that.

Byteang3l

Hathaway_Noa USB duress is a feature where the phone wipes itself when a USB with data transfer is connected to the phone, this feature is available on the highly insecure wasted app.

Good to know, learn something new every day.

hemingway

b8r2 The device did not display “incorrect PIN” nor did it unlock.

Okay. When the duress pin did nothing, did the 'fed' retry the pin? Were they able to reenter it or did the device become frozen and unresponsive?

Byteang3l

b8r2 The factual part I can confirm is that the duress PIN was entered, the secure wipe did not execute, and the data ultimately became accessible. I cannot provide specifics beyond that.

If you're unwilling to share that absolutely crucial piece of information, then there's nothing we can do for you, especially given your post mentioning USB duress which isn't a native GrapheneOS feature. I've poked enough holes in this narrative to happily bow out of this now, this was fun.

indigomadelin

If low IQ was a crime, you would deserve a life sentence.

« Previous Page Next Page »