Note: repost just for heads up

  • Lka1988@sh.itjust.works
    link
    fedilink
    English
    arrow-up
    28
    ·
    edit-2
    20 hours 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 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.

    • eleitl@lemmy.zip
      link
      fedilink
      English
      arrow-up
      2
      ·
      15 hours ago

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

      • Fmstrat@lemmy.world
        link
        fedilink
        English
        arrow-up
        3
        ·
        10 hours 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
    15
    ·
    2 days 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.

    • oblivion96@discuss.tchncs.de
      link
      fedilink
      English
      arrow-up
      35
      ·
      2 days ago

      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

    • RelativeArea1@sh.itjust.worksOP
      link
      fedilink
      English
      arrow-up
      16
      ·
      2 days 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.

    • Browse8474@lemmy.world
      link
      fedilink
      English
      arrow-up
      5
      ·
      1 day 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.

  • CerebralHawks@lemmy.dbzer0.com
    link
    fedilink
    English
    arrow-up
    14
    arrow-down
    5
    ·
    1 day 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
      31
      arrow-down
      1
      ·
      1 day 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
        8
        ·
        1 day 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
          2
          ·
          23 hours 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?

          • deadcream@sopuli.xyz
            link
            fedilink
            English
            arrow-up
            1
            ·
            15 hours 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.

          • Untamed_Star@lemmy.blahaj.zone
            link
            fedilink
            English
            arrow-up
            1
            ·
            21 hours ago

            i think there are some jailbreaks for the iphone and not the ios but a similar problem since they will stop being manifactured eventually.

          • Untamed_Star@lemmy.blahaj.zone
            link
            fedilink
            English
            arrow-up
            1
            ·
            21 hours 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”.