this post was submitted on 09 Aug 2023
32 points (94.4% liked)

Android

9341 readers
15 users here now

A place to discuss anything related to Android or Android adjacent.

INFO:

Check Out Our Partner Communities:

!android@lemmy.world

founded 4 years ago
MODERATORS
JshKlsn@lemmy.ml
LucasDondo@lemmy.ml
32
Why disclaimers are important (lemmy.ml)
submitted 1 year ago by glibg10b@lemmy.ml to c/android@lemmy.ml
10 comments fedilink hide all child comments
 

User jAm-0 has issues getting into and out of his phone's bootloader. He attributes this to the bootloader being corrupt and wants to replace it.

jAm-0 posts "Is it possible to re-flash the stock bootloader? I believe mine is corrupt somehow. It's a bit hard to explain how it's acting without actually seeing it, but it acts sporadic and barely works half the time. For example I can't reboot into the bootloader via adb, trying to power off the phone via bootloader doesn't work, and 9/10 times I try to turn my phone on it goes right to the bootloader."

User return.of.octobot provides instructions to allow reflashing the bootloader. One of the steps is to run fastboot flashing unlock_critical, which allows the bootloader to be overwritten.

Overwriting the bootloader is the only way to hard brick most devices, and fastboot flashing unlock_critical tells Android you don't care and are willing to take the risk. Hard bricking makes a device unfixable on the software level.

return.of.octobot provides instructions, including the step of running fastboot flashing unlock_critical, without any disclaimer

jAm-0 has another question and receives responses from return.of.octobot and another user, nrage23. Again, no disclaimers are given and the word "brick" isn't even brought up.

nrage23 responds to another question with "You have to do the flashing unlock critical if you have not to flash things like bootloader, boot, and modem."

jAm-0 hard bricks their phone.

after nrage23 responds to the same question, jAm-0 responds with "Great to know, thanks for the info. Too bad my phone is hardbricked now. Wont power on. Wont connect to pc. No fastboot. No recovery. Beautiful paper weight"

top 10 comments
sorted by: hot top controversial new old
[–] mathemachristian@lemm.ee 19 points 1 year ago (1 children)

I mean yeah disclaiming risks is important, but googling what you're messing with is as important.

If I'm messing with a core component of something I'll google until I'm 100% certain of the effect of what I'm about to do.

If someone were to tell me to replace some part in the engine of my car, I'm for sure gonna google everything about that even if I trust that person completely before I even pop the hood of my car.

[–] glibg10b@lemmy.ml 8 points 1 year ago (1 children)

That's fair, though I've found it hard to find information on these topics. I still only half-understand what I'm doing when installing a custom ROM or sideloading Magisk because I usually just blindly follow the accompanying steps

[–] mathemachristian@lemm.ee 4 points 1 year ago (1 children)

Poor/cryptic documentation sucks for sure. It means you have to risk your device which just increases the difficulty to start with that kind of hobby for sure. The only alleviation I can think of is to again hit the forums. Ask about the risks involved and how to mitigate them if possible.

[–] glibg10b@lemmy.ml 2 points 1 year ago

I'll admit that I've never made a post on XDA. I just created an account -- hopefully I can get some of my burning questions answered

[–] Lojcs@lemm.ee 12 points 1 year ago (1 children)

I can't imagine someone who knows about flashing and hardbricking not knowing the risks associated with flashing a bootloader.

[–] Daefsdeda@sh.itjust.works 11 points 1 year ago

All though I'm inclined to agree. You don't know how much knowledge they have about a subject and only heard it from a friend for example.

[–] ramble81@lemmy.world 6 points 1 year ago

Sees the word "critical" in a command, doesn't think to look up what might just be "critical" about the command....

[–] hunt4peas@lemmy.ml 4 points 1 year ago (1 children)

What would have been the correct steps?

[–] TonyTonyChopper@mander.xyz 2 points 1 year ago (1 children)

Seems like these are the correct steps and they got unlucky, or interrupted the flashing or something

[–] hunt4peas@lemmy.ml 1 points 1 year ago

Hmm.