Around a week ago, BLU issued a broken software update for its Life One X2 phone. In at least some cases, users who applied the update were locked out of their phones. Late this afternoon, BLU's official Twitter account—which, much to the chagrin of affected users, was silent on the subject for almost a week—issued a statement that the problem had been fixed via a new update.
Some of the most interesting additions to Android often come from unofficial sources. Maligned though they may be, Google has incorporated many features previously only found in manufacturer skins into AOSP, and custom ROM developers add new features more or less as they feel like it, some of which are quite useful. For example, the CyanogenMod development team is working on a new integrated system for handling "locked" apps, applications that can't be accessed by the user without a password or other validation mechanism.
If you updated your Verizon Galaxy S4 to the latest over-the-air build, or bought one after it was already installed, you might already be aware that it's been especially resistant to root attempts. Savvy power users have stayed well away from the updated VRUAME7 firmware, which makes rolling back to an earlier build impossible. But as is so often the case, two enterprising XDA-Developers posters have solved at least some of the problems, and released a new rooting method for the latest OTA.
The exploit comes from (or at least, was posted by) XDA members DoomLoRD and PWM978, among others.
Samsung Galaxy S4 owners on Verizon, there's a new update available for your phones. But don't bother checking your Settings menu for an over-the-air prompt: it's only available via the Verizon Software Upgrade Assistant after connecting the device to a PC. Standard users should be fine, but rooted users (or those who intend to root or flash a new ROM sometime in the future) should avoid this one. According to several posters on XDA, the VRUAME7 patches existing root methods, and flashes a new version of the locked bootloader that prevents users from flashing a pre-release kernel, effectively blocking another path to root.
It was only yesterday that Cyanogen definitively confirmed AT&T's treacherous move to lock down the Galaxy S4's bootloader, but there is light at the end of that tunnel. No thanks to AT&T but to security researcher extraordinaire and a person I admire Dan Rosenberg, a.k.a. the magician, a.k.a. the root whisperer.
Dan, who is responsible for numerous root and unlock exploits, tweeted this photo of his Galaxy S4 earlier today:
There are no instructions or blog posts explaining the unlock at Dan's blog yet - these should be coming in the future. When, you might ask? This part is not decided just yet, for a good reason (put down your pitchforks).
So, you were thinking about picking up a Kindle Fire HD, rooting it, and throwing a ROM on it for an impressive $200 tablet? Turns out that idea may not work out as well as we initially thought: both the Kindle Fire HD and the second gen KF have locked bootloaders. Bummer.
This may not mean that custom ROMs are impossible on these devices, only that it's more improbable.
For those who may not know, the bootloader is responsible for checking the firmware's signature before a device boots. In this case, if it doesn't match what Amazon says it should, then it simply won't do anything.
Verizon has taken some flack lately for being the only US carrier to lock the bootloader. Workarounds have been implemented, but Samsung's taken it a step further by announcing a developer version of the device. Today they...well, they haven't quite made good on that promise, but they have created a landing page for the device on their site that announces the 32GB Pebble Blue version will be "coming soon".
It doesn't look like pre-orders are available yet, although we know the device will retail for $599 when it finally launches. Previously, Verizon had tried to claim that Samsung was responsible for the locked bootloader, but since virtually every other version of the device did not have a locked bootloader, and now Samsung is going out of its way to get an unlocked version in the hands of its customers, it's a little tough to stomach that idea.
Those wondering whether Motorola's recently-announced Atrix HD will carry a locked bootloader can exhale – in a string of tweets earlier this evening, Moto confirmed that, yes, the Atrix HD's bootloader will be locked and signed.
That being said, Moto indicated that their "goal" is to provide a way to "unlock the bootloaders on our devices to those who wish to do so," adding that more details are "to come."
@kulow_atx Motorola ATRIX HD at AT&T will have a locked bootloader to meet requirements; (1/2)
Of the four major US carriers to receive the Galaxy S III, Verizon is the only one to lock down the bootloader. This has made a lot of people very angry and been widely regarded as a bad move. Nevertheless, enterprising hackers over at XDA and RootzWiki have successfully managed to circumvent the lock, achieve root, and flash ClockworkMod recovery. If you're on Verizon and anticipating owning a Galaxy S III, congratulations: your phone is yours again.
The process is laid out on both sites. Achieving root seems to be a fairly simple process if you're familiar with Odin (a common, easy-to-use tool for flashing Samsung devices).
Forget about GPS issues, it looks like ASUS has a bigger problem on its hand with the Transformer Prime: a locked/encrypted bootloader. Like with other devices, as soon as the development community found out about this, there were some rather irritated people. The typical backlash against the company has now started on popular social networking sites, along with a petition that has managed to get over 200 signatures in just a few hours.
This is definitely not the type of publicity that ASUS wants surrounding the world's first quad-core tablet, and users are hoping that the Taiwanese manufacturer will eventually reverse its decision and open the device.