At this point, I definitely intend to not let the fuse get burned in mine. I might insist Google take it back, since it's essentially a bomb waiting to go off (and likely would infect any warranty replacement I might get in the future).
Conversation
This Tweet is from an account that no longer exists. Learn more
Right now, my best option seems to be LineageOS (A12-based) anyway. But it would be nice to have the option to use/try Graphene again without it damaging my phone (which is what I consider burning the fuse for now). Couldn't it be an option the user gets prompted to approve?
1
This Tweet is from an account that no longer exists. Learn more
Giving the user a choice doesn't weaken it.
Users can still choose to burn their fuse.
The other day, told me they're not anti-owner-control, but forcing an irreversible fuse burn on users when it would be easy to give an option, doesn't reflect that...
1
There is no way to provide an option for that. It's a necessary step as part of securing the platform. End users don't get a choice about moving to Android 13 if they want security updates, regardless of what OS you run.
1
2
The OS is what burns the fuse. It should be entirely possible to remove that code, and make it conditional on a post-installation prompt.
If the user says "no", they can still use the modified Android 13 without burning the fuse.
1
We aren't going to disable a security fix that has no impact on end users.
1
1
For example, this means I cannot even _try_ GrapheneOS anymore, without losing my ability to keep using LineageOS if I change my mind.
2
1
Android 12.1 boots with Android 13 SoC firmware. The reason you can't flash stock Android 12.1 factory images is because flashing factory images for stock OS or GrapheneOS also flashes all of the firmware. They said they may make a new Android 12.1 release with updated firmware.
Flashing factory images updates the SoC and radio firmware followed by flashing the OS, and it checks to make sure that the matching firmware version has been flashed. It is possible to manually flash the OS images and it will boot, but the OS wasn't tested to work with that.
2
Is this wrong then? Or did I misunderstand him?
Sounds like he's saying Android 12 will NOT work with the Android 13 firmware (anymore?)
Quote Tweet
Replying to @LukeDashjr @flawedworlddev and @deadair3210
It won’t boot, as the main A12 system does not know how to work with the new bootloader and TEE stuff.
1
I'm pretty sure it can boot. It's almost certain that there is stuff broken but that applies regardless of whether the boot chain firmware counter is updated. The boot chain firmware counter applies to bootloader and TEE, but secure element has a totally separate counter.
1