Internet of Things startup Garadget remotely bricked an unhappy customer’s WiFi garage door for giving a bad Amazon review and being rude to company reps. Garadget device owner [Robert Martin] found out the hard way how quickly the device can turn a door into a wall. After leaving a negative Amazon review, and starting a thread on Garadget’s support forum complaining the device didn’t work with his iPhone, Martin was banned from the forum until December 27, 2019 for his choice of words and was told his comments and bad Amazon review had convinced Garadget staff to ban his device from their servers.
The response was not what you would expect a community-funded startup. “Technically there is no bricking, though,” the rep replied. “No changes are made to the hardware or the firmware of the device, just denied use of company servers.” Tell that to [Robert] who can’t get into his garage.
This caused some discontent amoung other customers wondering if it was just a matter of time before more paying customers are subjected to this outlandish treatment. The Register asked Garadget’s founder [Denis Grisak] about the situation, his response is quoted below.
It was a Bad PR Move, Martin has now had his server connection restored, and the IOT upstart has posted a public statement on the matter.– Garadget
This whole debacle brings us to the conclusion that the IoT boom has a lot of issues ahead that need to be straightened out especially when it comes to ethics and security. It’s bad enough to have to deal with the vagaries of IoT Security and companies who shut down their products because they’re just not making enough money. Now we have to worry about using “cloud” services because the people who own the little fluffy computers could just be jerks.
[stompyonos] bricked his Samsung Captivate. Not wanting to be without a phone for a while, he researched a fix online and found shorting a pair of pins on the USB port would put the phone into download mode, saving his phone. The only problem for this plan is [stompy] didn’t have any resistors on hand. Instead, he came up with a wonderful MacGyverism using a piece of paper, a bit of graphite, and a pair of paper clips.
The process of unbricking a Captivate requires a 300 or 330 kΩ resistor across pins 4 and 5 of the mini USB port. This can be done with a few resistors, but [stompy] only had a multimeter lying around. After scribbling a good bit of pencil lead on a piece of paper, he attached two paper clips to make a variable resistor, dialed it in to about 300 kΩ, and cut up an old Nokia charger for its USB plug.
Not bad for a very easy fix that didn’t cost [stompyonos] a dime, and certainly better than a $500 paperweight.
We’ve all had that sinking feeling as a piece of hardware stops responding and the nasty thought of “did I just brick this thing?” rockets to the front of our minds. [Florian Echtler] recently experienced this in extremis as his hacking on the University of Munich’s Microsoft Surface 2.0 left it unresponsive. He says this is an 8,000 Euro piece of hardware, which translates to around $10,000! Obviously it was his top priority to get the thing working again.
So what’s the first thing you should do if you get your hands on a piece of hardware like this? Try to run Linux on the thing, of course. And [Florian] managed to make that happen pretty easily (there’s a quick proof-of-concept video after the break). He took a Linux kernel drive written for a different purpose and altered it to interface with the MS Surface. After working out a few error message he packaged it and called to good. Some time later the department called him and asked if his Linux kernel work might have anything to do with the display being dead. Yikes.
He dug into the driver and found that a bug may have caused the firmware on the USB interface chip to be overwritten. The big problem being that they don’t just distribute the image for this chip. So he ended up having to dump what was left from the EEPROM and rebuild the header byte by byte.
Continue reading “A tale of (un)bricking a $10k Microsoft Surface unit”
[Paul] let me know about a new way to get a hacked kernel on a XBox 360. A new timing attack will soon allow you to install an older kernel
with without having the CPU key which was the catch 22 situation before. The proof of concept ressurected a bricked XBox by doing some interesting things to one of the NAND (memory) blocks on the machine.
Great news for the homebrew/hacking scene!