I thought I bricked my old phone but it turns out I just needed to open the phone, short a couple of pins 5-10 times and trying to quickly boot into flashboot, repeat if it didn't work.
It turns out I was a fool thinking that it was bricked after all.
Also it's basically the core of the highly-paid tech expert meme "not paid for turning the screw but to know which screw to turn".
If the issue is not easily troubleshootable and searchable then the keyword for it if the device doesn't reach stage X of boot will always be "bricked".
my point was that there was not "official" procedure to verify, I told him the story, he believed me, and went in the back and reset the password or something. They have the capability if they want to. He was a manager I think, and I didn't get to him through the reservations queue, I just walked up to the counter to find out if this was the place I should go, and after I asked my question he took an interest and solved the problem for me.
Seriously though, the last time I truely bricked something was because I overwrote the bootloader on a chip that had no other way to flash, and it was an all-in-one, so I couldn't solder to the chip and reprogram it directly. Now that was a brick. A board that I can still solder to a chip and bus pirate my way to victory, isn't a brick. Being able to do so wirelessly? psh.
Edit: I'm remembering now, that hardware was an Apple keyboard. I wanted to flash the firmware so I could have capslock be left Ctrl in hardware, but I flashed the wrong thing and then could not flash an updated image to it.
You're a person after my own heart. If there is a God, you're doing his/her/their work.
What was the hardware and firmware you were flashing?
You could just swap caps with one.
> Why not use an empty modifier and have your own shortcut keys that you can guarantee no other program uses?
Because that would require messy tinkering with multiple layers of software.