I know there are a lot of you that might want to get into rooting and utilizing custom ROMs, but just don’t know where to start. Although it’s always best to do things the manual way, we can understand why some of you might want something that’s quick, simple, and has everything in one place. That’s exactly what toolkits do. They allow you to unlock and root your device as well as flash custom recoveries and a whole bunch of other stuff.
Well XDA member mskip has a toolkit available for the international Galaxy S III (i9300) as well as 3 of the 4 U.S. Galaxy S III’s (AT&T, T-Mobile, and Sprint). Obviously Verizon isn’t included since the bootloader is locked. The U.S. variants get one universal toolkit, while the international version has its own. Hit the break to see a list of all the features, download links, and forum links.
It used to be called the Galaxy Nexus Root toolkit, but with version 1.5, it’s now called the Nexus Root Toolkit because it supports all Nexus devices, including the Nexus 7. WugFresh is famous for giving us the quick and easy way to unlock and root the Galaxy Nexus as well as flash it back to stock and re-lock it. There really couldn’t be anything simpler, although we do encourage you to go about things the manual way, which isn’t all the much harder.
Nonetheless, we understand that some of you might be a little nervous and that’s where the Nexus Root Toolkit comes in. It can even flash zips, install apps, restore android backup files, and flash/boot img files with just a double click. This new version now supports all Nexus devices. Hit the break for instructions and download links.
Today the CynaogenMod team announced CM9 support for three U.S. Galaxy S III devices. It doesn’t take a rocket scientist to figure out that Verizon’s version didn’t make the cut. For now they are supporting the AT&T, T-Mobile, and Sprint versions. They did mention the Verizon version and their original intent, but nothing was said about the U.S. Cellular version. Hit the break for their statement.
Sure the Amazon Kindle Fire might not be at full fledged Android tablet, but that shouldn’t stop you from having the full experience including Jelly Bean 4.1.1. XDA member Hashcode just posted an AOSP based Jelly Bean ROM. This is a beta so there are some issues like the HD codecs (YouTube and Netflix). The good news is this will be fixed shortly as Texas Instruments is updating the libion code. Other oddities is the screen over rotates and the dev is having an issue turning on UMS. These are all issues that will be fixed shortly.
It was only a matter of time before we saw the first batch of Google devices get the anticipated Jelly Bean update since you know— it had just released Android 4.1 to the AOSP and all. And so just when you thought life with the GSM/HSPA+ version of the Galaxy Nexus couldn’t get any better, it just got better as it is officially getting the smooth and buttery update. According to its Nexus+ page, Google highlights owners of the HSPA+ variant of the Galaxy Nexus will receive an OTA prompt indicating the update will happen “over the next several days”.
Google also took some time to reiterate its other developer devices including the CDMA versions of the Galaxy Nexus, Nexus S and Motorola Xoom WiFi are next in line to get that VIP treatment.
source: Nexus – Google+
Thanks to LastStandingDroid over at the XDA forums, the Samsung Galaxy S II (I9100) has received an Android 4.1 Jelly Bean SDK port. With any SDK port, the build is fairly rough and one should expect many things to either not work, or not work correctly. Although there is a short list of things that do work:
With the release of the source code for Android 4.1 Jelly Bean, we can expect to see a bunch of ROMs soon, but some of you might want create your own port from the source. To help you along, XDA member dastin1015 put together a guide to get you started compiling Jelly Bean on Ubuntu. It covers the setting up of the build environment, connecting to and downloading from the repository, adding a device, and building. Just hit the source link below to get started.
In the next year, I’m expecting to see more and more Android-related media devices and set-top boxes such as the Nexus Q. Last week we told you about a new Android-based gaming console called OUYA, but we really didn’t know much about it. Well it just became a Kickstarter project so we have more details.
The concept and idea behind the project is to make it easier for developers to bring a console game to market. Every OUYA console is a developer kit and there won’t be a need to purchase a license or an expensive SDK. So basically no licensing fees, retail fees, or publishing fees so anyone can create the next big title. All games will have the freemium model so everyone will at least be able to try any of the ones they’re interested in.
Sure the Nexus Q is going to be a revolutionary media device for us Android users, but don’t forget— at the end of the day, it’s still a Nexus product and so you know what that means? It means that the Nexus Q is meant to be tinkered with and improved upon silly. After seeing the Q get unlocked and rooted for all kinds of tomfoolery, it was time to see what else could be done with the device. Well thanks to XDA Forum member fredc888, we are now one step closer to being able to see the full potential and take full advantage of the Q’s ability to run apps and games. fredc888 was able to successfully connect a Bluetooth-compliant HID mouse to the device. Yes friends a Bluetooth mouse. That is definitely big time.
While this is an exciting achievement, it is one that should be taken with extreme caution. As you might expect, the Q doesn’t have a traditional Bluetooth menu to allow it to connect to other devices outside of Android phones and tablets, so the Bluetooth stack configuration file must be directly edited to allow input devices and connect to them automatically and naturally— this step requires unlocking the bootloader, which effectively wipes the device’s data partition. Should you make an oopsies, unbricking options for the Nexus Q are limited and that means users should take extraordinary precaution when writing to the device.
Despite the significant risk to the Nexus Q– you can’t help but be excited at the idea of connecting additional gadgets to the device. So if you’re feeling a little lucky, brave or just plain curious, be sure to check out the complete thread— which you can find at the source link below.
source: XDA Forums
Well while the Verizon Galaxy Nexus is one step closer to truly becoming a “Nexus”, Sprint’s Galaxy Nexus is still lacking AOSP support, so what gives? Well, for one thing Verizon’s Galaxy Nexus— also known as toro— only has experimental binaries at this point and Sprint’s Galaxy Nexus— also known as toroplus— well… is not getting even an experimental build of the various binaries. And not only that— Sprint’s Galaxy Nexus is not only getting the cold shoulder from Google Developers, but there are no immediate plans to offer support for that version of the device as indicated by Jean-Baptiste Queru:
“As far as toroplus, the situation is unchanged: there are no plans to support it as a target device for custom AOSP builds.
This is certainly a bit of a messy situation unfolding. Considering the resounding success of the Nexus S 4G and the fact loyal Sprint customers have been eager to have the Galaxy Nexus, Sprint (and Google) would best figure out some type of compromise or solution and soon. The loyal Nexus customers deserve at least that much.
source: Android Police