Note: repost just for heads up

  • Lka1988@sh.itjust.works
    link
    fedilink
    English
    arrow-up
    0
    ·
    3 months ago

    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. I skipped through all of the setup steps.

    • eleitl@lemmy.zip
      link
      fedilink
      English
      arrow-up
      0
      ·
      3 months ago

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

      • Fmstrat@lemmy.world
        link
        fedilink
        English
        arrow-up
        0
        ·
        3 months ago

        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.

  • toothpaste_sandwich@thebrainbin.org
    link
    fedilink
    arrow-up
    0
    ·
    3 months ago

    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.

  • CerebralHawks@lemmy.dbzer0.com
    link
    fedilink
    English
    arrow-up
    0
    ·
    3 months ago

    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).

    • Truscape@lemmy.blahaj.zone
      link
      fedilink
      English
      arrow-up
      0
      ·
      3 months ago

      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.

      • deadcream@sopuli.xyz
        link
        fedilink
        English
        arrow-up
        0
        ·
        3 months ago

        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.

        • Truscape@lemmy.blahaj.zone
          link
          fedilink
          English
          arrow-up
          0
          ·
          3 months ago

          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?