It’s happening again!

  • FooBarrington@lemmy.world
    link
    fedilink
    English
    arrow-up
    1
    arrow-down
    1
    ·
    1 day ago

    There’s nothing stopping manufacturers from permanently locking the bootloader. Some do and others don’t suggesting that the industry does not have a universal preference.

    Some manufacturers have stopped allowing unlocking their bootloaders, some bootloaders have been hacked by the community. It’s not like this is a static system.

    I do think Google wants it to be inconvenient enough to run a version of Android they haven’t blessed as one’s main phone that it has no chance to become mainstream, but that’s about the prospect of an OEM not bundling Google’s apps and store, not hobbyists running custom builds.

    No, Google is also trying to stop hobbyists running custom builds from accessing services built on their software (the aforementioned SafetyNet). Hackers keep finding ways around this, but Google keeps trying to lock them out.

    • Zak@lemmy.world
      link
      fedilink
      English
      arrow-up
      3
      ·
      1 day ago

      No, Google is also trying to stop hobbyists running custom builds from accessing services built on their software (the aforementioned SafetyNet). Hackers keep finding ways around this, but Google keeps trying to lock them out.

      That’s a side effect. If Google really wanted to interfere with hobbyists, they would mandate hardware-based attestation and all the current workarounds would be broken. It would be much harder to create workarounds for that.

        • Zak@lemmy.world
          link
          fedilink
          English
          arrow-up
          1
          ·
          1 day ago

          It appears phones as old as the Android 8 era can support this and phones that shipped with Android 13 or newer always do. I had the impression it had been universal a little longer.