“Bricking,” “hard bricking,” and “soft bricking” became inexorably intertwined during the early days of flashing custom Android ROMs
Comment on HP fails to derail claims that it bricks scanners on multifunction printers when ink runs low
hoot@lemmy.ca 1 year ago
Do people not know what “bricking” means? This article is about HP disabling features if the printer runs out of ink.
If they bricked it, it would be unrecoverably broken, never to function again.
ozymandias117@lemmy.world 1 year ago
Rai@lemmy.dbzer0.com 1 year ago
HTC Dream and G2 user/modder here
I’m not familiar with that. Brick means “your item is now a brick.”
I’ve never heard of hard or soft.
bitwolf@lemmy.one 1 year ago
Soft brick is like when you mess up fastboot and need to use Qualcomms tool to repartition and repair fastboot.
Generally you cannot do this, but the tool leaked for some devices, this it’s softbricked
ozymandias117@lemmy.world 1 year ago
QC uses the firehose protocol to load software that early, but that’s a good overview
The tools are generally available to flash, but manufacturers may not offer the next signed bootloader as something you can easily download (that one then implements fastboot)
ozymandias117@lemmy.world 1 year ago
At that time, “Hard Brick” was getting used for the hardware was damaged
“Soft brick” was something like a boot loop where the device was unusable, but something like a DFU flash could repair (using DFU since every manufacturer had their own boot flash implementation back then)
At some point after that, people just went back to saying “bricked” for both
Misconduct@startrek.website 1 year ago
As someone that rooted their phones a lot back in the day it’s wild how vividly I remember this and it went down exactly as you described lol
lemann@lemmy.one 1 year ago
A bit like most Inkjets when the unreplaceable waste ink pad dries up 😭
Sit through a whole turn on sequence, just for the screen to say the manufacturer’s equivalent of “Bin me, I’m dead” with the only option being to power off
mwguy@infosec.pub 1 year ago
A more accurate term would be that they ransom the functionality of the product they sold until you pay the ransom.
fubo@lemmy.world 1 year ago
Or maybe they engineered a “multifunction” device with shitty error handling: if any subsystem has an error, all subsystems fail. A junior engineer filed a bug report about it and submitted a patch. The PM didn’t consider the bug launch-critical enough to merit an engineer’s time to review the patch. The system shipped with the bug intact. The PM was rewarded for launching the product on time, and got promoted into a different position. A year later when the users start fussing, the people on the team say “we never heard of that problem.”
(This is hypothetical. Tech companies do be like that sometimes though.)
mwguy@infosec.pub 1 year ago
Just because they accidentally made ransomware doesn’t make it not ransomware.
fubo@lemmy.world 1 year ago
Exactly, yeah. The incentives within the company generate shitty behavior towards users, even if no individual wrote out a design for that shitty behavior.
SlopppyEngineer@discuss.tchncs.de 1 year ago
And if this was in the first version, everybody would understand. If it’s still in version 5, it’s by design.