Google's approach to releasing preview firmware for upcoming versions of Android is evolving into a pretty cool system that allows developers to simply sign up a device and wait for the OTAs to come rolling in. However, no product launch is perfect, and this one is causing some real problems for some users. Complaints started rolling into the Nexus Help Form and AOSP Issue Tracker about devices that were left unable to boot after attempting to install the OTA. This problem is greatly compounded by the fact that many users are not able to unlock their bootloaders, which means they can't fix the issue with a factory image. Read More
The most recent over-the-air update for the Nexus 9, the one that totally wasn't what you were actually waiting for, has apparently bricked the device for some owners. A couple folks affected by this 5.0.2 issue have taken to Google's product forums to ask what gives.
The person who opened this thread was told to perform a factory reset in recovery mode (as well as the bootloader, which has a separate factory reset option). It didn't fix things. Nor did it work for our very own Cameron Summerson, who went through this headache this morning. He was able to fix his Nexus 9 only after flashing the factory image manually. Read More
When we buy gadgets, it's usually with the expectation that their useful lifetime will carry us at least until we're ready to replace them, and hopefully well beyond. Most people assume their smartphones should last at least two years, in part because contract customers in the US are accustomed to unreasonably high upgrade prices for mid-term upgrades, and also because most manufacturers have adopted yearly release cycles that fit well with this pace. The expectations for tablets aren't as well defined, but most customers seem to want about 3 years or so. Even when we're done with a device, we want to be the ones to end the relationship, rather than wake up and find our hardware dead beyond hope. Read More
If you own a Sony SmartWatch, you may want to ignore the impending update to the SmartWatch app on the Play Store right now. Some users are reporting that, after updating the required app, their watches are experiencing random reboots, notifications no longer working, and random disconnects. We've reached out to Sony for comment, but so far we've heard nothing back.
It appears that version 1.2.33 of the software began causing problems. The current app has now been bumped to version 1.2.34, however it's unclear if this update fixes the problem and allows users to upgrade safely. What is clear is that if you already updated to 1.2.33, and your device was then bricked, you won't be able to update to 1.2.34, as the device disconnects right away. Read More
Update: After receiving a distraught email from Team ACS, it has been brought to our attention that their root method may not be the cause of signal loss on the Epic 4G Touch. We're currently researching the details and will update this post accordingly.
Update x2: According to new information we received, there have been reports of this same issue happening on non-rooted phones. We're not sure how things got twisted around to point the finger at rooted devices, but we do know that Sprint is looking into it.
Have you rooted your Epic Touch 4G? Apparently, some users who have tried to flash Zedomax and ACS's custom kernel have experienced a loss of signal bug. Read More
When we leaked the official ROM and radio image for the HTC Thunderbolt's Gingerbread update last week, users were understandably excited. An official Sense, Gingerbread ROM was probably highest on the list of demands for Thunderbolt users (aside from better battery life, perhaps).
Unfortunately, at this time, we have to officially advise anyone using any ROM based on this leak to revert to a Froyo build or to CyanogenMod 7 as soon as possible. This includes any and all third-party Gingerbread ROMs for the HTC Thunderbolt not based on CM7.
We don't take announcing this lightly, but we do so erring on the side of caution because of the extent to which this problem bricks the phone. Read More
Update: Shortly after the update botch was noticed by Notion Ink, they halted distribution of the update in question because it was not downloading completely. If you have a bricked Adam, here is the fix as e-mailed to Notion Ink Fan:
No one here at Android Police has a device to test this fix on - so be careful, and read the warning.
How to flash your Adam and get it working again
This fix is recommended only if your Adam has stopped booting up after installing the over-the air system update on 24 January. Please don't use the method indicated to flash your Adam with any ROM not from Notion Ink, as it would probably damage your Adam irreparably.
There’s been a lot of discussion lately about the bootloader of the Droid X, and more specifically, whether the ‘eFuse’ will render your phone inoperable if you choose to replace the boot loader.
If you’re not up to speed with the story, it all started with this post a few days ago on MyDroidWorld, which claims that the Droid X boot loader is fitted with eFuse technology, which can physically brick the phone if you try to alter the boot loader in any way. Altering the boot loader is needed to install a custom recovery, which is then capable of doing full Nandroid backups and restores, as well as allows for installing custom ROMs. Read More
HTC and Sprint are working together to accommodate EVO 4G owners whose phones were bricked after this week’s initial update. Without adding very much detail, HTC stated that Sprint Corporate stores can be of service. You can find the closest store using this tool.
If you have already updated successfully and your phone boots up fine, you don't have to do anything. If you haven't applied the OTA update yet, you can now safely do so, as the bricking issue has been fixed.
If, however, the initial update made your phone go blank or get stuck in a boot loop, it's time to head over to your local Sprint store. Read More