EDIT: Added soft- to the title, since it was pissing people off. Maybe I’m still wrong. Idk, it’s just a meme.

  • Tb0n3@sh.itjust.works
    link
    fedilink
    English
    arrow-up
    62
    arrow-down
    3
    ·
    edit-2
    2 months ago

    If you didn’t need to buy a new phone you didn’t brick it. The name comes from the device becoming as useful as a brick. IE filling physical space.

    • Albbi@lemmy.ca
      link
      fedilink
      arrow-up
      19
      arrow-down
      2
      ·
      2 months ago

      Yeah, bricking something makes it completely unusable anymore: ie. turned into nothing more than a brick. If you can access it and restore functionality then it wasn’t bricked.

    • Rexios@lemm.ee
      link
      fedilink
      arrow-up
      16
      arrow-down
      6
      ·
      edit-2
      2 months ago

      There is hard and soft bricking. Soft bricking means the phone is unusable, but fixable. Hard bricking means the phone is permanently unusable.

      • MeThisGuy@feddit.nl
        link
        fedilink
        arrow-up
        13
        arrow-down
        7
        ·
        2 months ago

        would you build a house out of soft bricks? no… they don’t exist.
        bricking is permanently fucking it up. as useful as a phone as a brick. aka a paper weight

        • southsamurai@sh.itjust.works
          link
          fedilink
          arrow-up
          16
          arrow-down
          1
          ·
          2 months ago

          The term exists, and has been used in rooting circles since at least 2012 that I know of, since that was when I rooted my first device and ran across the term.

          While it certainly doesn’t make much sense as a term, that’s different from the term not existing.

        • Rexios@lemm.ee
          link
          fedilink
          arrow-up
          6
          arrow-down
          1
          ·
          2 months ago

          Would you build a house out of a metaphorical term? It’s not literal. If a phone doesn’t boot it’s as useful as a brick until you fix it.

        • ulterno@lemmy.kde.social
          link
          fedilink
          English
          arrow-up
          5
          arrow-down
          2
          ·
          edit-2
          2 months ago

          Soft Brick => You can build the house with a lot of them, but when the wolf huffs and puffs, it will fall.

          Hard Brick => The house you build, will not be breakable by the wolf’s huffing and puffing.

          CC BY-NC-SA 4.0

  • fernandu00@lemmy.ml
    link
    fedilink
    arrow-up
    15
    ·
    2 months ago

    I was astonished that I installed lineage with microg on my xiaomi last year and without bricking it not even once.

    • DavidGarcia@feddit.nl
      link
      fedilink
      arrow-up
      8
      ·
      2 months ago

      it usually is pretty painless if you don’t buy a brand new device or a very popular one. but idiot me always gets a 2 month old extremely obscure device.

    • Fugtig Fisk@feddit.dk
      link
      fedilink
      arrow-up
      5
      ·
      2 months ago

      Xiaomi is pretty complicated though isn’t it?. You need to register with xiaomi to get permission if i am not wrong?

      • fernandu00@lemmy.ml
        link
        fedilink
        arrow-up
        4
        ·
        2 months ago

        Yeah but once you do that and unlock the bootloader, installing lineage was too easy. Last time I tried that (it was called cyanogenmod yet) I spent a hole weekend trying to recover my nexus 4

  • umbrella@lemmy.ml
    link
    fedilink
    arrow-up
    6
    ·
    edit-2
    2 months ago

    no but seriously we need better instructions and community.

    trying to find telegram channels to get support from teenagers isnt the best. they will have to learn that lesson all over again wont they?

  • communism@lemmy.ml
    link
    fedilink
    arrow-up
    6
    ·
    2 months ago

    Misuse of bricking aside—I’ve never had an issue with installing GrapheneOS. Never actually used another degoogled AOSP-based OS, so can’t compare it, but I’d definitely say GrapheneOS is at least very “normie”-friendly in terms of being easy and intuitive to use, and simple enough to install so long as you know how to read and are capable of following instructions (which I’m aware many users are not…)

    • Hellfire103@lemmy.caOP
      link
      fedilink
      English
      arrow-up
      2
      ·
      2 months ago

      Well, GrapheneOs is a bit easier. GOS uses a WebUSB installer, which does a lot of the work for you.

      LineageOS requires things like ADB and Fastboot. In my case, however, it was a Samsung device, so I had to install Windows and then mess around with Odin.

      I also ended up soft-bricking the device by trying to sideload the OS before it had finished downloading.

    • Hellfire103@lemmy.caOP
      link
      fedilink
      English
      arrow-up
      2
      ·
      2 months ago

      It seems to be running well on my Galaxy Tab A7. Definitely better than One UI or whatever it came with.

    • Hellfire103@lemmy.caOP
      link
      fedilink
      English
      arrow-up
      1
      ·
      2 months ago

      Well, you can still get pretty far with GrapheneOS. Pixels can be re-locked, which is a feature I wish all Android devices had.

    • DarkCloud@lemmy.world
      link
      fedilink
      arrow-up
      27
      arrow-down
      1
      ·
      2 months ago

      Really depends on your phone, different models present different levels of difficulties from very easy to literally impossible.

        • aStonedSanta@lemm.ee
          link
          fedilink
          arrow-up
          7
          ·
          2 months ago

          Haha you expect people to read? I just copy and paste the commands in terminal and yolo it.

          /s of course lol

          • ulterno@lemmy.kde.social
            link
            fedilink
            English
            arrow-up
            5
            ·
            2 months ago

            Can confirm.

            I work with developers who refuse to read the documentation that I spent hours, creating and refuse to read the code which has easily been made available (at their own demand) - and then come to me asking for explanations that are already written.

    • Godort@lemm.ee
      link
      fedilink
      arrow-up
      8
      ·
      2 months ago

      There are loads of people out there that want stuff like this but dont have computer-related hobbies.

      It makes perfect sense if you understand what you’re doing at each step, but if you’ve never used a command line before, each instruction would look like arcane gibberish.

    • DavidGarcia@feddit.nl
      link
      fedilink
      arrow-up
      6
      ·
      2 months ago

      I remember a time when MicroG didn’t exist, we has to walk barefoot 50 miles uphill both ways in a snowstorm just to get the privilege of bicking my device twice a day

      • GolfNovemberUniform@lemmy.ml
        link
        fedilink
        arrow-up
        6
        arrow-down
        1
        ·
        2 months ago

        I’m still not wise enough to comprehend the life of custom ROM users back then. Reading manuals of that era always causes my brain to error out before even finishing the initial reading.