Verizon’s Samsung Galaxy S5 is receiving an update (software version KOT49H.G900VVRU1ANE9) which is bringing a bunch of bug fixes to the device, but also seems to be breaking root access to the device, according to a number of users around the web.
The update keeps the phone at Android 4.4.2, and update’s Verizon’s Caller Name ID, Message+ and Cloud apps.
Team Win posted its official custom recovery for both the Samsung Gear Live and the LG G Watch today, giving users the ability to add customer ROMs to the devices.
Once you’re in custom recovery, the options on the screen are a bit small for a smartwatch screen, so an upcoming interface update will most likely resize the buttons. Otherwise, everything works fine. Of course you’ll need an unlocked bootloader before you do anything.
The Nexus Root Toolkit from Wugfresh has become insanely popular since the interest in unlocking bootloaders and rooting devices has expanded to “normal” consumers.
Now, those with an LG G Watch will be able to root and unlock the device just as easily as Wugfresh’s Nexus solution provides.
If you’re one of the many who jumped ship from their stable Android version to try out the Android L Developer Preview, you definitely noticed it’s not exactly the most polished thing in the world (not even close, actually).
No reason to be mad at Google, though — it’s just a developer preview, and we’re lucky to have something before launch.
As most Android enthusiasts tend to do, we looked ahead, and hoped for Google to upload an updated factory image of the L Developers Preview. But according to Googler Rich Hyndman, it ain’t happening.
Chainfire’s SuperSU app has been updated today to build in support for the Android L developer preview. Before now, rooting the developer preview involved a few workarounds with custom boot images so root permissions should work properly, but that should all be fixed up now.
If you’ve been using the L developer preview, have you tried rooting it yet, or are you fine with using a non-rooted device?
source: XDA Developers
Verizon and AT&T did an excellent job of locking down their version of the Galaxy S 5, preventing any type of root exploit on the device for several months after release. Tons of people put up money for a bounty to get their Galaxy S 5 unlocked, topping out at around $18,000, and today developer Geohot from XDA gets to claim that bounty.
Geohot, known for tons of jailbreak exploits on Apple devices and the PS3, found a vulnerability in the Linux kernel that Android is based on to achieve root access on the GS 5. As a side effect to that exploit, the root method should work on most newer Android devices, including the previously unrootable Galaxy Note 3 and plenty of other devices.
If you’ve got a Galaxy S 5 (or other device you need to root) hit the link to test out the Towelroot app. Let us know how it goes in the comments.
source: XDA Developers
With a new version of Android ready to start rolling out on a large scale before too long, including to the AOSP, some changes in the system will likely create some new challenges and require some additional work on the part of developers who create apps that rely on a rooted device. The first of these changes involves SELinux and some adjustments to make it even more secure. The tighter settings mean developers will have to invoke more complicated context switching for their apps. It also appears Google is switching the default runtim compiler for Android to ART which will create some challenges. Finally, it looks like Google is going to require PIE (Position-Independent Executable) for non-statically built executables.
The Moto E ships with close to stock Android and an unlockable bootloader, so it was pretty obvious it wouldn’t take long before the device was rooted and ready for custom ROMs. Thanks to XDA, you can now root the device and install an unofficial TWRP recovery on the device.
The root process is pretty simple and uses Chainfire’s SuperSU updater and can be done with the stock recovery or TWRP. Flashing the recovery takes a bit longer, but it’s still relatively painless thanks to Motorola keeping the Moto E an open device. However, Motorola hasn’t released the source code for the Moto E kernel, so touch screen support is a bit weird in recovery, but that’s a small price to pay.
You can get the complete (and short) instructions at the link below.
source: XDA Developers
The Paranoid Android team have always been in the forefront when it comes to adding some awesome features into their AOSP based ROM’s. With previous features like Halo, you can expect the team to always come up with interesting features. Today they’ve released their newly developed feature, dubbed as “Hover,” into their beta builds, and so far I think it looks amazing and very practical. The video below can give you a much better idea of what it is than me explaining it, so check it out after the break and let us know what you think about it! Just remember that it’s still in beta so don’t be surprised to find some bugs if you decide t give it a shot.
With Sprint releasing the Harman Kardon edition of their HTC One M8, it left a slight bad taste to current HTC M8 users that have already bought the device. Although in due time, I figured there would be a dev(s) out there that would be able to port the software of the HK edition into regular HTC M8′s. As always, that didn’t take too long as a dev from the trusty XDA site by the name of baadnewz has done just that. If your phone is rooted and has a custom recovery, you can turn your M8 into the HK edition with a few steps. Users that have tried it are already reporting a much improved audio experience while listening to music through their headphones.
Sadly, the only part of the HK edition that wasn’t able to be ported was the support for FLAC files, although that shouldn’t be too much of a problem considering most 3rd party music players on the Play Store offer that support. Check out the XDA thread if you wish to give this a shot!
via: Cult of Droid