Hacker News new | ask | show | jobs
by Someone1234 1728 days ago
Bricked is a [current] state (wherein there's no official recovery workflow available, and the device is as usable as a brick).

To give an example, certain dead devices can be saved after being baked in the oven to re-seat components that have worked loose. According to the "No True Bricking" argument that constantly comes up, those devices were never really bricked because they were later fixable, even though you're literally performing a re-manufacturing step.

In fact what exactly would a "True Bricking" look like? Even in cases where a major component dies, if you desolder it, and re-solder a new one is that a "True Bricking?"

See I have zero patience for the "No True Bricking" stuff since it is a logical Swiss cheese.

2 comments

The requirement for electronics knowledge and skills is a clear dividing line for me.

I've recovered and hacked devices for friends using software. Especially phones which have recovery functions I can use but I've also hacked some older game consoles. I can't do anything if electronics skills are required though. At that point it becomes specialized repair work.

I suppose nothing's really bricked if you're smart enough. Just desolder a chip, reprogram it and resolder it back in? I don't know how. I tried to learn what I could but it turned out hardware is a lot harder than software.

You obviously have some patience for it because you spent the time to make some pretty good arguments as to why you can unbrick something. I think you have me convinced.