Root access on the Sprint, U.S. Cellular, and T-Mobile variants of the Moto X has been relatively simple and straightforward, as Motorola hasn’t put too many safeguards in the way of consumers messing with their devices for these carriers. However, Verizon and AT&T customers haven’t been so lucky. However, that might change very soon for Verizon customers, as developer Justin Case of TeamAndIRC has achieved root on their Moto X, and the procedure also applies to the new DROID phones. The root isn’t permanent at this time and you might want to hold off on any OTA updates if you’re planning on going through with the root.
It’s great news nonetheless and hopefully Justin Case comes out with a more stable method sooner than later.
In unexpected news, Verizon’s brand new HTC One actually has an unlockable bootloader. No, we aren’t joking. the HTC Dev bootloader unlock process works on Big Red’s version of the phone, and even though that means it isn’t a full S-Off unlock, it’s still going to give you enough room to flash custom ROMs and the like. As a cherry on top, there are already easy root files available and a version of CWM recovery has already been ported.
Knowing Verizon, this was probably not intentional and it could very easily be patched up relatively quickly. If you have a new HTC One, you may want to consider following the links below to go ahead and get your device unlocked before Verizon patches anything up.
via: Droid Life
You’ve read that title right folks. Only a few days after the device went on sale do we have an exploit that gives root access to the little HDMI dongle. The folks over at GTVHacker found this exploit. As you know the Chromecast is supposed to be running a simplified version of the ChromeOS however the folks at GTVHacker believe it to be more of a modified Google TV Release. It appears that the bootloader, binaries, init scripts and kernel are from Google TV. This allowed GTVHackers their access.
They’ve been able to build an exploit that allows people to gain a root shell through port 23 via telnet of the device. While this is interesting in itself, Google could send out an update to the dongle and close this loop hole. The team explains the loop hole:
“By holding down the single button, while powering the device, the Chromecast boots into USB boot mode. USB boot mode looks for a signed image at 0×1000 on the USB drive. When found, the image is passed to the internal crypto hardware to be verified, but after this process the return code is never checked! Therefore, we can execute any code at will.”
The GTVHacker’s Wiki page hosts the file and if you feel like tinkering with it you can download it from there. While this news doesn’t mean much for the average person, it was only a matter of time before someone would attempt to exploit the Chromecast. Hit the source link below for a full detailed explanation of how the exploit works. If you’re interested in seeing it in action you can check out the YouTube video after the break. Enjoy!
XDA Senior Member frapeti has developed an application called ‘Android Bot Maker’ which is an automation tool for your Android device which essentially turns it into a bot, making repetitive tasks easy. The program features a numerically ordered “Actions” list of all the automated actions that the user has programmed the device to carry out. Sequences can be rearranged, saved, imported, cleared, and shared onto various cloud social networks connected to the service. There is also a toggle feature to prevent the device from sleeping while the application is in use.
The program is still in its beta phase so there may be some bugs, but developer frapeti has encouraged users to offer suggestions and reports in the application thread via the source. Of course your device will have to be rooted and running at least Android 4.1 to run the application— check out the source for the application thread on the XDA Developers site. Hit the break for the app’s Play Store link.
If you’re an avid root/modder in the Android community then rooting tool-kits should be nothing new to you. Today an all-in-one root plus recovery installer has been made available for the Verizon Samsung Galaxy S 4. The instructions seems relatively easy (if you’re familiar with this kind of stuff), so just make sure you follow the directions thoroughly.
If it runs Android, it’s going to be tinkered with. The new, yet-to-be-released OUYA console is no exception. Some devs on XDA have officially unofficially ported CWM recovery to the little gaming box. This opens the doors for flashing custom ROMs and kernels on the box, although since the device is really aimed at controlling your TV, I wouldn’t expect to see too many ROMs for the OUYA. Performance-tuned kernels are definitely possible, though.
The device will need to be rooted first, but if you’re interested, hit the links below to check out how it’s done.
Good news for those of you that are tired of your generic boot animations on your Android devices— a forum member on XDA Developers, Vincent8111, has compiled about 400 custom boot animations into a single program for your convenience.
The BootAnimation Changer runs on Windows and stores an extensive collection of boot animations, sorted by name or file size, and varies from the opening sequence of the Simpsons, to anime, to colorful abstract patterns, to an obvious favorite, the Android mascot.
One of the coolest new features in Android 4.2 was multi-user supports. The feature is only available for tablets, although a bit of modding will enable it for phones as well. The new easiest way to get multiple user accounts enabled is the Modaco Toolkit, at least on rooted phones running Android 4.2.
First, you’ll need to download and install the Xposed Framework, which is a fairly new tool for Android developers to add tweaks to system framework. The Modaco Toolkit is a module for the Xposed Framework. Installing the Toolkit will enable all of the multi-user options after a reboot. This mod definitely works on AOSP 4.2 ROMs,but no word on if it’ll work on skinned versions of Android. Hit the links below to test it out on your rooted device, after making a backup, of course.
As promised, Dan Rosenberg aka djrbliss on the XDA Developers forum released some additional details about his attempts to unlock the Samsung Galaxy S 4. Yesterday he posted a pic showing the unlocked bootloader that seemed to indicate he had recovery capabilities. He confirmed that in his latest post on the subject where he reports his work will allow custom kernels and recoveries.
Rosenberg also confirmed he had achieved the unlocking on an AT&T variant of the Galaxy S 4. However, he is not planning to release any details until Verizon starts to ship their version later this month. If you think you will be interested in unlocking your new Galaxy S 4 using Rosenberg’s tools, he does recommend that you not accept any OTA updates prior to his publishing his release despite the risk of missing out on security updates.
source: XDA Developers forum
News today from Twitter where security guru Dan Rosenberg, @djrbliss, posted an image of a Samsung Galaxy S 4 with what appears to be an unlocked bootloader that he managed to hack. Rosenberg had already achieved root on the new devices on launch day when he figured out an unlock tool intended for Motorola devices would also work on the Galaxy S 4 thanks to the use of Qualcomm chips. The downside is that nothing much can be done once rooted and the risk related to bricking a brand new device is a little higher than normal as no recovery options or stock images are available yet. Hopefully Rosenberg’s work is about to change some of that as his image appears to indicate that he has recovery running. Rosenberg is expected to release more details later today on exactly what he has achieved and how others may replicate his efforts.