zlacker

>>dang+yy1
> In short, it was remote bricked, by giving it commands to rotate a bit. > But luckily it automatically readjust itself to earth automatically every half year exactly for these events.

I remember when bricking something meant it was totally unrecoverable. Now it means "temporarily not working but will automatically heal".

>>burnte+AB
Nothing is ever truly unrecoverable. If a device was built, it can be built again.

What is bricked vs recoverable has always greatly depended on time and effort, individual skill level, available hardware/software tools, documentation, crypto keys, physical access, willingness to replace individual parts etc.

Sometimes, even within an org, some teams e-waste expensive devices that aren't bricked deeper than what other teams recover from as part of everyday workflow.

Taking a typical network device as an example, where do you draw the line? Driving to a remote location to plug the cable into another port, pressing a reset button, booting from USB, flashing a new firmware with TFTP, plugging in an external or internal console cable, opening the case and soldering a header to get access to the console, doing the same with no documentation, or an unknown (but maybe Google-able or reverse engineerable) password, flashing firmware with JTAG, shipping the device back to the engineers (or shipping an engineer to the device)...? It's always been arbitrary.

>>Ao7bei+jl1
If you can't fix it or find someone who can, it is bricked.

If you are able to fix it then it is not bricked.

One device may be bricked to one person but not to another. But that must still be the definition, right? Otherwise the word has no meaning.

>>belter+(OP)
Stub for arguing about what "bricked" means. These comments were originally replies to >>36941191 , but we moved them because the offtopic discussion was choking the thread.

Normally I'd have marked the entire subthread offtopic, but hutzlibu's comment deserves to be at the top, even if it does use the word "bricked" wrong.