[chrneu]

It's relatively easy. It's basically a command for each step you want to do and it tends to fail gracefully nowadays.

If you can install a linux distro you can flash a custom rom on a well-supported phone.

If it were more mainstream I could see GUI apps to manage all this for people, if they don't already exist. Idk I just use adb.

[paulryanrogers]

It's also high risk. I've bricked two phones doing it.

[a456463]

I flash phones almost every other week. And tablets. I have been flashing since Androids came out. But never bricked. But maybe that is why I don't have any problems.

[Onawa]

I've been flashing phones for over 2 decades and have never bricked a phone. How did you manage that?

[microtonal]

Lots of people brick their phones by relocking the bootloader when the Android SPL before flashing was newer than the newly flashed OS when the phone has downgrade protection (e.g. Fairphone 6). The Fairphone/e Foundation forums are pretty full of people making this mistake. Then the only solution is paying Fairphone to fix it.

[brnt]

Same here. Just follow the LineageOS steps.

[user3939382]

Are you seriously implying that flashing phones doesn’t risk bricking them or you’re not aware of that risk are you serious?

[kllrnohj]

"flashing" a phone is largely the same as any OTA update. There's of course always a risk of it going wrong, disk failures are always possible, but it's exceptionally hard to do so accidentally. Especially with custom ROMs where they basically never include a new bootloader, so "flashing" is no different than installing an OS on a desktop system - it's just writing to the boot partition. Which you can always do again since the bootloader is still available.

[microtonal]

It is not 'largely the same as OTA' on phones with downgrade protection. Once you lock the device again, it's game over because the bootloader refuses to boot an older version of the OS, and you cannot unlock the phone anymore. Happens all the time in the /e/OS and Fairphone forums.

It really depends on the device. E.g. Pixel is quite hard to brick. Though they do sometimes increment the anti-rollback version:

https://developers.google.com/android/images

In that case you have to be careful to not flash an older version to both slots and lock the bootloader, which is possible, because many non-Google/GrapheneOS images are often behind on security updates.

[kllrnohj]

It is still largely the same, those downgrade protections apply to OTAs as well. Those anti-rollback don't brick the device, either. It might not boot to a working OS, but you can still get back to the bootloader to flash something newer. Unless you blindly lock the bootloader without testing if it boots first and the bootloader can't be unlocked again I guess, but that's quite a sequence of bad choices all around

[luz666]

I am seriously unaware of the risks and also flashing brand new phones :)

[wolrah]

> Are you seriously implying that flashing phones doesn’t risk bricking them or you’re not aware of that risk are you serious?

Yes, that is generally the case. As a general rule with an Android phone reflashing the OS itself or the bootloader carries no risk of bricking the device (meaning making it impossible to recover without specialized hardware and/or opening up parts that were not intended to be opened).

There are plenty of ways to "soft-brick" a device such that you might need to plug it in to a computer, and adb/fastboot can definitely be a pain in the ass to use (especially on Windows), but if you have a device with an unlocked bootloader it's very rare to be able to actually brick the device while doing normal things.

Now, if you're doing abnormal things like reflashing the radio firmware you can absolutely brick some devices there, but you don't have to do that just to boot an alternative OS and generally shouldn't be doing it without very good reason and specific knowledge of exactly what you're doing.

I'm not going to say there are no devices where the standard process to flash an alternative OS is dangerous, but none of the relatively common ones I've ever owned or used have been built that way because OEMs don't want their own official firmware updates to be dangerous either.

tl;dr: It is sometimes possible to brick a device by flashing the wrong thing incorrectly, but the risk of doing that if you are just installing an alternative OS through a standard process is basically zero.

[crtasm]

Potential for a brick varies massively depending on phone model, doesn't it?

[Markoff]

it's pretty much impossible to hard brick phone, you can almost always recover it

I'm running custom ROMs for the last 15 years

[eldaisfish]

That describes relatively easy for you, but not for the average person who can’t even be bothered to change the default ringtone.

[keyringlight]

The challenge I've found when looking for instructions for flashing one of my old phones is the assumption of knowledge some rom builders have, or perhaps an assumption about their audience. This seems like it has the potential to bit someone in the ass because if they're relying on other sources like the lineageOS wiki or forum posts elsewhere for example there's no guarantee it'll stay available, complete, or relevant to their variant over time. It's an added burden for what is a gracious volunteer role, but it's a handicap if they want more people using the fruits of their labor.

[yellowapple]

I can't be bothered to change my phone's default ringtone and yet I've had very little issue installing LineageOS and GrapheneOS on the various phones I've owned over the years.