Search the Community
Showing results for tags 'bricked'.
Found 2 results
A botched wireless update for a remotely accessible smart lock system has bricked hundreds of them. The locks suffered a “fatal error,” according to device’s manufacturer LockState, rendering them unable to locked. Customers are asked to either return impacted locks for repair, or request a replacement. “We realize the impact that this issue may have on you and your business and we are deeply sorry. Every employee and resource at LockState is focused on resolving this for you as quickly as possible,” wrote Nolan Mondrow, CEO of LockState in an email sent to customers last week. More than 500 customers using model 6000i RemoteLocks are impacted, the company told Threatpost. In total, about 11 of the company’s keyless lock systems in use today are affected. The 6000i allows customers to remotely manage and monitor doors, and alerts them when assigned codes are used to open a lock using a keypad. “After a software update was sent to your lock, it failed to reconnect to our web service making a remote fix impossible,” Mondrow said. In lieu of using a keypad code, many impacted customers can use a physical key that comes with the locks, according to LockState. The company told Threatpost that on Aug. 7 the company mistakenly sent out an over-the-air firmware update to its 6000i systems meant for its 7000i model locks. The update caused first-generation models of the 6000i locks to malfunction, rendering them unable to be locked and no longer able to receive over-the-air updates. “After the push happened, we immediately notified those who received the update, and a few hours later we wrote with repair/replacement options,” according to the company in a statement to Threatpost. The 6000i locks were commercially available to anyone, but were also part of its Airbnb Host Assist marketing partnership. Approximately 200 Airbnb customers were impacted, LockState said. A number of Airbnb customers took to Twitter to complain about the problem. Airbnb did not return a request to comment on this story. The botched update and bricked locks come as more pressure is put on IoT device makers to focus on shoring up device security and reliability. It’s also not the first time a keyless door system has caused owners headaches. In May, the New York Attorney General Eric Schneiderman settled with Safetech Products over the sale of insecure Bluetooth door and padlocks. The issue in this case had less to do with a fatal error and more to do with Safetech sending clear text passwords via Bluetooth between the locks and the user’s smartphone. Last year, SecuRing warned a growing number of Bluetooth devices used for keyless entry and mobile point-of-sales systems that are vulnerable to man-in-the-middle attacks. Article Another Article
SlimRock posted a topic in Software ChatHi Everyone , As the title states, my problem is that today I was trying to update my SAMSUNG Galaxy Ace S5830 to Android 4.4.2 KitKat with CyanogenMod 11 ROM using the method http://www.ibtimes.c...install-1430916 , After downloading the Custom CWM, ROM & copy pasting the said zip files to the SD card, tried the CWM in Recovery mode but it didn't worked due to "not a valid update zip" error, Idk whether it was due to either my phone was not rooted or something else. So then went ahead with rooting my phone using SuperOneClick v2.3.3 and renamed the CWM file "ClockworkMod Recovery 220.127.116.11" to update.zip, Voila this time CWM was installed. While performing this step, I have not cleared the cache and not deleted the data but after this Recovery mode stopped working though phone was working without any issues. So I thought the issue might be due to some CWM error & then downloaded & installed the ROM Manager app from the Google play link : https://play.google....utta.rommanager and selected the option Reboot into recovery and since then display is stalled at SAMSUNG LOGO see in the pic : http://i.imgur.com/4k9k5ku.jpg and now I am unable to use the handset. I did tried the workaround given in this link http://www.droidview...830-using-odin/ with the odin v4.42 but Windows was unable to detect the USB device, although I have installed the latest SAMSUNG_USB_Driver_for_Mobile_Phones_v18.104.22.168 Drivers. These are the Windows error screenshots : http://prntscr.com/2s3we4, http://prntscr.com/2s40ni, & after Uninstalling the USB drivers nothing is changed http://prntscr.com/2s40ur, http://prntscr.com/2s41pn That being said, any help will be highly appreciated. Edit Note : Topic Title Changed to Solved! :)