Note: repost just for heads up
I find this blurb on Pixels interesting:
OTAConfigNoZeroTouchPrebuilt is an app on Pixels that checks for a carrier lock. When a Pixel first connects to the internet, this system app will immediately check if the device is carrier locked. If it’s not or is locked to a carrier that doesn’t restrict unlocking, it will retrieve a token from Google’s servers which will allow bootloader unlocks. If the token cannot be received, then the bootloader cannot be unlocked. This means if Google’s servers ever go down, you will not be able to unlock your Pixel’s bootloader, as it won’t have the token.
Mostly because unlocking the bootloader and rooting my Pixel 9 Pro was the very first thing I did to it before installing my SIM card (yes, I still use a physical one). I also skipped the wifi setup.
Edit: in all seriousness, this is a handy list.
Does this still apply after installing GrapheneOS and locking the bootloader again?
Are we sure about the Fairphone? I set one up with LineageOS the other day and had no issues, nor did I have to register anywhere, as far as I can remember.
On Fairphone, for every OEM unlock you need a working internet connection, and for the first OEM unlock you need to get an activation code from Fairphone using your phones IMEI/serial number. So I’d say this classification is correct. I also have a Fairphone and everything worked without problems, but it is still 100% controlled by Fairphone even on already sold devices.
Not sure about older Fairphones. I have a FP5.
See https://www.fairphone.com/de/bootloader-unlocking-code-for-fairphone
I must be misremembering then! Thanks for the correction.
tbf, I’m not sure about older Fairphones (I have a FP5 and I needed to do that)
There is a bypass to do it offline
https://www.datenrei.ch/blog/2024/05/25/fp-oem-unlock-all.html
Still deserves the spot on the list though
considering that fairphone decided to include an unnecessary option on their site to “request for an unlocking code” even tho their devices can be easily unlocked via dev mode. I kinda understand the thought of the github author/s that it would just take a board meeting and deciding to enshittify their product, the possibility of it is super low but not zero.
They also have anti rollback, You cannot lock the bootloater if current rom security version is older than the one it had before.
They do warn of this but still bad as it makes the phone a brick if you do lock it.
fantastic resource, thanks for sharing!
Huh, I went into this thinking of Pokémon fanroms
