• Unlock bootloader (depending on vendor, you have to do an online verification),
  • flash a recovery.img,
  • load into recovery mode (which, depending on the phone, might need extra work)
  • wipe some caches,
  • select new os/rom image,
  • pray it doesn’t brick your phone.

You’d think someone would’ve learned a thing or two from the easy graphical installations linux and even windows have been offering since the late 2000s.

    • Troy Dowling@lemmy.world
      link
      fedilink
      arrow-up
      7
      ·
      10 months ago

      If you don’t mind me polling your opinion: do you recommend Graphene for someone previously used to Cyanogen / Lineage? I recently upgraded to a Pixel 8 from quite an old handset and I’m not particularly fond of the stock ROM. Much has changed since the last time I had to think about this stuff! I primarily care about privacy, and use my cell for little more than phone calls, messaging, and its camera.

      • czech@low.faux.moe
        link
        fedilink
        English
        arrow-up
        7
        ·
        10 months ago

        Yes- I’d recommend Graphene to anyone who can live without Google Pay. I’ve only been using it for a month but everything has worked without issue and with the added benefit of “storage scopes” and Google Play sand-boxing.

    • breakfastmtn@lemmy.ca
      link
      fedilink
      arrow-up
      4
      ·
      10 months ago

      I decided to install Graphene before looking up the installation and was blown away by how easy it is. I’d been on stock android for years and was expecting a similar experience as OP describes. My very old custom ROM folder is filled with files with names like ‘confirmedsafeblob’ and ‘bricksafe’ that I don’t even know what they are anymore but speak to some past misery. Then beep-boop done with the web installer.