Did Google fix this issue?

[Ondrashek06]

To clarify, a few years ago, the FBI used Google Pixel phones loaded with custom backdoored ROMs to catch criminals in Operation Trojan Shield.

But what I'm worrying about is the fact that if you flashed a custom ROM without the ability to unlock the bootloader (like FBI's ArcaneOS) and then locked the bootloader, your phone was essentially locked permanently and you couldn't get back the stock ROM in any way.

Do the new Pixels still have this flaw? Or do they have a recovery system in case of a fucked-up flash?

 

[Deleted member 702243]

verified boot just doesnt work that way

 

[KleinesSinchen]

Do the new Pixels still have this flaw? Or do they have a recovery system in case of a fucked-up flash?

Many devices have an emergency download mode (EDL) which doesn't care for flashing (un)lock – sometimes it requires things (software, signing keys) only the manufacturer has. Example: [XDA Developers] Help! FP5 stuck in FastBoot Mode.
Not a Pixel, but a similar situation as you said: OEM unlocking is disabled → can't unlock flashing… but the main operating system doesn't boot… can't allow OEM unlock. Full circle.

I guess it would be possible to create a custom OS for Pixel that disables OEM unlocking and doesn't offer enabling it again (what would be a stupid idea). I've no idea if current Pixels offer some EDL and what you would need, but I guess Google should be able to flash it back to stock.

custom backdoored ROMs to catch criminals in Operation Trojan Shield.

I'll have to look that up, sounds interesting. Prisons are full of idiots. If one plans criminal activities involving computers(phones), they should buy things in a brick and mortar store with cash. I better stop here. It could be interpreted as condoning crime and giving hints.
On the other side, since so-called "law enforcement" isn't beyond reproach and can be evil and do illegal things towards non-criminals, thinking of countermeasures against them isn't equal to being a criminal.

verified boot just doesnt work that way

How is that supposed to answer the question?

 

[The Real Jdbye]

To clarify, a few years ago, the FBI used Google Pixel phones loaded with custom backdoored ROMs to catch criminals in Operation Trojan Shield.

But what I'm worrying about is the fact that if you flashed a custom ROM without the ability to unlock the bootloader (like FBI's ArcaneOS) and then locked the bootloader, your phone was essentially locked permanently and you couldn't get back the stock ROM in any way.

Do the new Pixels still have this flaw? Or do they have a recovery system in case of a fucked-up flash?

I'm not sure it would even allow you to lock the bootloader with a custom ROM installed since that might brick the phone.

Every Android device has a recovery mode, and fastboot. Recovery mode can be overwritten but fastboot can't. It's limited what you can do from fastboot, but you can flash partitions, which would allow you to restore a bricked recovery or flash a new system image, it may even allow you to boot an .img directly without flashing it. Often you can also do bootloader unlock from fastboot.

 

[KleinesSinchen]

I'm not sure it would even allow you to lock the bootloader with a custom ROM installed since that might brick the phone.

Yes, Pixels allow installing a custom key and it makes AVB actually useful compared to stock. You define what is protected by locked bootloader instead of what manufacturer offers by default.

Unfortunately few devices allow this.

 

[Deleted member 702243]

How is that supposed to answer the question?

it's not possible to run a modified OS on a Pixel without getting a very obvious screen that tells you you are running a different OS

This is verified boot doing its job

but you're right, the question was the second part of the post and not the first one, that's my mistake

but this same verified boot is also why there can be no such thing as an emergency recovery mode that just lets you flash anything regardless of bootloader lock

Post automatically merged: Dec 11, 2024

what is the worry here, anyway?

if the worry is a custom os having oem unlocking disabled preventing you from re-unlocking, ask the people who made it to make an update that fixes this. if you don't trust them to be willing to make an update to get you out of this mess, you shouldnt be using an os from people you dont trust in the first place

if the worry is getting a phone with a modified backdoored os that doesnt let you enable oem unlocking, verified boot ensures you will know if the os is modified so you know this phone is no good

if you're worried about locking the bootloader while oem unlocking is disabled, and being unable to re-unlock, well... don't do that, I guess

if it's just the curiosity of knowing if it's still possible or not, well I cant fault you for wanting to learn more about how everything works, but then I don't get why you describe it as an issue that needs to be fixed. if it's not this, phones can be bricked in other ways anyway. if you fear the possibility of locking yourself like this, then just don't do it, and if you fear the possibility of buying a phone that ends up coming in a semi-bricked state like this, you could also receive one that just doesnt work at all anyway and you wouldnt be any better off

the way you worded your post seems to imply some kind of worry over a potential issue but I don't see how realistic the situation actually is