c0d3z3r0

Tested by manually expire the session cookie. You're right, thanks! :)

uhm? just tried with incognito mode and I can view it without signing in.

> So... either they should release a firehorse binary that can wipe devices, or they should add a small bit of code that can wipe and flash without needing a firehorse binary.

And how should they add code to a ROM of yet bricked devices?

> As I read it, dmitrygr was saying that the ostensible reason you can't do anything is fear of evil maid attacks, but that ostensible reason doesn't explain why there isn't a wipe+access mode. And "the bootloader is corrupt" isn't the reason, because this is about the pre-bootloader code.

Well, ask Google? :-)

Read the post from dmitrygr again or mine. The bootloader does not get loaded, because the verification fails. That means there is no way to wope or reset the device. Without a signed firehorse binary you can't do anything, because EDL just won't talk to you.

More details: https://blog.quarkslab.com/analysis-of-qualcomm-secure-boot-...

Sorry, actually I meant pads. However, there's nothing there that could bridge them.

Btw. there were several reports of signature validation errors right before the phone finally "died".

Keyboard missing. Press F1 to continue. :P

Mostly correct. Just a slight correction: You not only need the right image to flash, which you do get from google (factory images) but you need a signed firehorse/edl binary the boot ROM will accept.

Read again. It does. The boot ROM fails to verify the bootloaders (XBL) signature for some reason.

Don't compare Qualcomm to Mediatek... it's different

Definitely not possible, since the board is not located under the battery but more like "around" it. (I know, because I had opened multiple Pixel 3 in the past) Also, the probability of just shorting exactly the right two pins is reeeeeeeaaaaaaally low

Phones are stuck in EDL mode with no way to recover, due to Google not releasing the signed firehorse files.

https://issuetracker.google.com/issues/192008282

https://www.google.de/search?q=pixel+3+brick&tbm=nws

I am not affected (yet). If anyone from Germany is interested in figuring out what the issue is and can risk losing their data, feel free to ping me on libera IRC. I have the ability to desolder and dump the UFS memory to start some investigation.

This is an iteration of Allan's code