This is a list of phone manufacturers that lock their bootloaders to prevent people from installing custom operating systems (LineageOS etc) to remove bloatware and spyware/tracking.

all 13 comments

sorted by: hot top controversial new old
[–] 64 points 11 months ago (4 children)

They care about your data, which is why they’ve taken steps to ensure they always have access to the data that they care so much about.

  • source
  • hideshow 4 child comments
  • [+] 41 points 11 months ago (3 children)
  • [–] 22 points 11 months ago (1 child)

    So..almost every company.. It would have been easier to make a list about the companies who do allow bootloader unlock

  • source
  • hideshow 1 child comment
  • [–] 12 points 11 months ago

    Samsung? I'm pretty sure I saw bootloader unlocking in developer options though...

    DO NOT UPDATE to OneUI 8

    Checks System Info

    OH SHIT.

  • source
  • [–] 7 points 11 months ago (1 child)

    The Amazon Fire Phone is conspicuously absent from this list.

  • source
  • hideshow 1 child comment
  • load more comments (-1 replies)
    [–] 6 points 11 months ago

    Wait what, Energizer makes phones?

  • source
  • [–] 1 point 11 months ago
    19 comments in c/android@lemmy.world view that post
    [–] 31 points 3 months ago* (last edited 3 months ago) (3 children)

    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.

  • source
  • hideshow 3 child comments
  • [–] 3 points 3 months ago (2 children)

    Does this still apply after installing GrapheneOS and locking the bootloader again?

  • source
  • parent
  • hideshow 2 child comments
  • [–] 6 points 3 months ago (1 child)

    I think it does not apply since the verified boot key is replaced.

    This thread seems to back this theory up: https://discuss.grapheneos.org/d/444-how-do-i-unlock-the-bootloader-in-grapheneos/3

    The GrapheneOS factory images flash a non-stock Android Verified Boot key which needs to be erased to fully revert back to a stock device state. Before flashing the stock factory images and before locking the bootloader, you should erase the custom Android Verified Boot key to untrust it

    Would love if someone could fully confirm, though.

  • source
  • parent
  • hideshow 1 child comment
  • [–] 16 points 3 months ago (5 children)

    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.

  • source
  • hideshow 5 child comments
  • [–] [S] 17 points 3 months ago

    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.

  • source
  • parent
  • [–] 32 points 3 months ago* (2 children)

    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

  • source
  • parent
  • hideshow 2 child comments
  • [–] 6 points 3 months ago

    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.

  • source
  • parent
  • [–] 11 points 3 months ago (6 children)

    Mentioning Apple just seems redundant? iPhones don’t have custom firmware, at least not current ones. I think you could install Android on a 3GS, but it wouldn’t be current.

    No one’s buying an iPhone to unlock the bootloader, they’re doing it because it’s what others have, they use other Apple tech, or they want a decade of updates (that lose features).

  • source
  • hideshow 6 child comments
  • [–] 31 points 3 months ago (5 children)

    They don't have custom firmware because it's locked down, not because of their product line's existence.

    If iPhones were as easy to mod as Pixels, then the sheer amount of potential users would probably mean a custom firmware would be swiftly developed.

    So yeah, we should name and shame them, even if Apple has no interest in opening the gates.

  • source
  • parent
  • hideshow 5 child comments
  • [–] 8 points 3 months ago* (4 children)

    iOS itself is closed source so unlockable bootloader wouldn't make modding it much easier. Custom Android roms are based on AOSP which is easy to modify and can be used with existing properietary drivers extracted from official firmware. Alternative OSes for Android phones exist but their users are tiny minority even in custom ROM community. Porting a Linux-based OS to an iPhone and making it fully functional would be a humongous task.

  • source
  • parent
  • hideshow 4 child comments
  • [–] 2 points 3 months ago* (3 children)

    Wouldn't both the Asahi Linux project and the prior examples of android managing to be ran on iPhone 5 models and below be solid examples to the contrary?

  • source
  • parent
  • hideshow 3 child comments
  • [–] 1 point 3 months ago

    Asahi only really supports M1 and M2 macs, only even for them it's not 100% support. Though I guess it's comparable to how postmarketos / Ubuntu touch and other such Linux OSes work on Android devices.

  • source
  • parent
  • [–] 1 point 3 months ago

    Really hard not impossible. Even then we're decades away from even starting anything like that. Last jailbreak for ios was in ios 17 i believe? iOS is at 26 rn it did switch from 18 to 26 tho. Apple literally hired all the jailbreak devs to patch the exploits. There aren't even exploits that would help you personalize the phone and have better privacy since ios 18 and maybe a bit of early versions of 26. That's why I changed my phone when I messed up my password and had to update it.

    Also the android on early iphones doesn't even work fully, it's a start yes but yea. And apple just also killed hackingtosh (mac in non apple machines) when they stopped to support intel. They could reverse ingenier the arm chip or whatevs, asahi has already done some reverse engeniering in the Apple m1 chip.

    I don't think you have to jailbreak mac? idk i've never used one. So ye if we were to get custom stuff for ios it would take a lot years to even get a jailbreak and more years to get anything else and for that point almost anyone would be using that version of ios since you can't "downgrade".

  • source
  • parent
  • [–] 2 points 3 months ago

    Huh, I went into this thinking of Pokémon fanroms

  • source
  • [–] 2 points 3 months ago

    fantastic resource, thanks for sharing!

  • source
  • 10 comments in c/privacy@programming.dev view that post
    [–] 23 points 11 months ago* (last edited 11 months ago) (8 children)

    Yeah, I dunno how accurate, let alone comprehensive, this repo of shame is.

    From: https://github.com/zenfyrdev/bootloader-unlock-wall-of-shame/blob/main/brands/cat/README.md

    Cat's phones have the OEM Unlock option in the settings app, but the typical fastboot flashing unlock/fastboot oem unlock just returns an unknown command error.

    They didn't bother to list what model they tested before deeming the entire brand "Terrible". I have two CAT S22 Flips (still daily driving one of them), and both of them unlocked immediately with the fastboot command and without requiring an unlock key.

    Mostly moot, though. You can still get CAT phones on the secondhand market but Bullit Group (the manufacturer of their branded phones) went out of business in April 2024.

    I'm honestly not sure why you'd buy a phone from a tractor company anyways.

    Because their phones are rugged AF and nearly indestructible.

  • source
  • hideshow 8 child comments
  • [–] 3 points 11 months ago (5 children)

    How indestructuble do they compare to a classic Nokia, or a GameBoy?

  • source
  • parent
  • hideshow 5 child comments
  • [–] 2 points 11 months ago (4 children)

    I don't say this lightly, but completely on par with a classic Nokia with the exception of the touch screen. Not that I've damaged it, but touch screens are the weak point in all modern phones.

  • source
  • parent
  • hideshow 4 child comments
  • [–] 2 points 11 months ago (3 children)

    Now that's interesting to know. I like 90's-level-of-indestructibility devices.

  • source
  • parent
  • hideshow 3 child comments
  • [–] 2 points 11 months ago (2 children)

    Unfortunately they don't make them anymore, and they're stuck on Android 11. I have two, and one of them is running a GSI ROM for Android 13 but it's got issues with VoLTE so it's not my daily driver.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 1 point 11 months ago (1 child)

    , and they’re stuck on Android 11

    From a technological perspective, wouldn't that be a win? Each Android version since then is worse (not to mention the changes to the Store). I wonder if, considering these are devices indestructible enough to last, potentially beyond industries, are they equipped with the provisions to upgrade or change the OS out-of-band. Imagine one of those thingies running LineageOS.

  • source
  • parent
  • hideshow 1 child comment
  • [–] 2 points 11 months ago

    Honestly, I prefer A11 and agree it's gotten worse sense. Thinking mostly along the lines of security patches and the like.

    The GSI ROM I'm running on my secondary one is LineageOS on top of the stock system (basically how GSI images work). There's no official LineageOS support, but I'm honestly not sure what the limitation is; may just be no one willing to maintain it.

  • source
  • parent
  • [–] 6 points 11 months ago*

    The effort is appreciated and while some brands can definitely be undoubtedly terrible (like Apple which doesn't have a single phone the expressively allow you to unlock), many brands have a mix of phones that allow unlocking.

    I'd much rather have a long table I can filter and sort than just a blanket "this brand is terrible and should be avoided". Also, that verdict should be reached by a list of common criteria with a point system. It should just be the author of a page that decides a company's rating.

  • source