zlacker

[return to "NASA mistakenly severs communication to Voyager 2"]
1. burnte+AB[view] [source] 2023-07-31 14:23:09
>>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".

2. mindsl+lV[view] [source] 2023-07-31 15:33:49
>>burnte+AB
> I remember when bricking something meant it was totally unrecoverable

It may have seemed that way to you, but actually no. "Bricked" has generally referred to devices that are likely straightforwardly recoverable, but for a lack of documentation from the manufacturer.

3. dang+yy1[view] [source] 2023-07-31 18:14:08
>>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.

◧◩
4. burnte+nH1[view] [source] 2023-07-31 18:51:53
>>mindsl+lV
No, that's not true, and it's never been true. The definition was always "turned into a device which is electronically indistinguishable from a brick and unrecoverable." Maybe an expert could do some deep diving to bring it back, but if it's beyond recovery to most folks, then we'd call it a brick. If you have to desoldier a flash chip and sldier on a new one with a filesystem that isn't trashed or with corrected software, then we've debricked it, but that's really a deep level repair.
◧◩◪
5. mindsl+UJ1[view] [source] 2023-07-31 19:05:21
>>burnte+nH1
Your division of "experts" vs "most folks" is doing a lot of work here, and speaks to my point.

Most folks don't really know how to use say Android fastboot or recovery modes either, yet we wouldn't call a device with a wiped system partition "bricked".

Most "bricks" are things like a bootloader getting erased. Reflashing that through the standard process of JTAG or another debug protocol is a straightforward action (after all, the manufacturer has to get the first bootloader on there to begin with). The port pinout and config info just hasn't been publicly documented by the manufacturer, which is what pushes it into the domain of "experts".

◧◩◪◨
6. burnte+m32[view] [source] 2023-07-31 20:45:05
>>mindsl+UJ1
If doctors create the term "heart attack" and laypeople misuse it, that doesn't change the definition.
[go to top]