TeamBlackHat has publicly released a leaked official Gingerbread (Android 2.3.3) software update build for the Motorola DROID 2. To install the update, you must have the DROID 2 Bootstrapper by Koush. Instructions and download links below:
Installing Firmware 1. Download this file from the TBH app or download below 2. Use Bootstrap to get your phone into recovery. 3. Create a backup (This is not compatible with new firmware) 4. Install the Firmware using recovery
1. select install zip from sdcard 2. choose zip from sdcard 3. navigate to teamblackhat folder 4. select the file you downloaded 5.
TeamBlackHat has publicly released a leaked official Gingerbread (Android 2.3.3) software update build for the Motorola DROID X. To install the update, you must have the DROID X Bootstrapper by Koush. Instructions and download links below:
Installing Firmware 1. Download this file from the TBH app or one of the mirrors below 2. Use Bootstrap to get your phone into recovery. 3. Create a backup (This is not compatible with new firmware) 4. Install the Firmware using recovery
1. select install zip from sdcard 2. choose zip from sdcard 3. navigate to teamblackhat folder 4. select the file you downloaded
In typically blisteringly-quick fashion, the hackers at XDA have managed to root a Wi-Fi XOOM in no time at all - good news, considering that the root method for the regular XOOM was bricking the Wi-Fi models. It's worth noting that unlocking the XOOM's bootloader (which is required for root) wipes the device.
The current method does require some ADB commands, but certainly nothing tricky. Still, for those who are hesitant, it's likely that an automated method won't be far behind. The instructions, as posted by Xaositek:
This is it guys... HUGE props to MADindustries and modplan!
Download the Motorola WiFi Xoom Root Zip file and unzip it.
One of the ways Android protects application users from unwanted activities is by requiring every app to declare a set of permissions and allowing users to view those permissions during the installation phase. Don't like what an app can do? Just don't install it.
However, this all or nothing approach doesn't allow you to selectively turn off specific permissions, so if you don't like that an application accesses your phone state, you can't just disable that and still have the app installed. This forces you to either potentially compromise your privacy or miss out on what could be a great piece of software.
One of the most popular questions about rooting the ThunderBolt is how to undo the process and return to stock, which renews your eligibility for customer support. Well, here you go:
Please read the whole tutorial first, and pay attention to every detail. Note that your battery needs to be charged to at least 40% at the beginning of the process, and remember to check the MD5 sums of all downloaded files before diving in. As always, neither Android Police nor Team AndIRC are responsible for any damage this may cause to your phone, and, needless to say, returning to stock means you will no longer be able to use root apps like ShootMe and Titanium Backup.
DANGER: There is a link to download this unofficial, unsupported CM7 ROM in an XDA thread linked at the bottom of this post. Use of that software is 100% at your own risk, and unless you're a developer, there's not much reason to be playing with at this point. There is no data connectivity, no sound, and no Google Apps. Consider yourself warned.
A number of Gingerbread-hungry developers (including some from the CyanogenMod team, particularly Slayher) are hard at work preparing CyanogenMod 7 for its Thunderbolt debut, and progress is steadily being made. In the video above, you can see CyanogenMod 7 successfully booting up on the HTC Thunderbolt (albeit without the signature boot animation) and running through various simple tasks in Android.
Conspiracy theorists would have you believe that the ThunderBolt's signed (and locked) bootloader was all Verizon's doing, but it appears that isn't quite the case - the Incredible S, one of HTC's unlocked GSM phones, is shipping with a similar failsafe system. That basically means no custom ROMs for you (at least until a viable workaround is discovered).
Proof? Look no further than the contents of this Incredible S RUU:
From what our friends at AndIRC can tell (note that they don't have a device in hand), the Incredible S includes a signature check much like the one on the ThunderBolt.
If you've been looking to unlock your HTC Thunderbolt but have been putting it off until a one-click solution springs up, you may start rolling up your sleeves - you've got some downloading to do. dbzfanatic from xda released the first one-click easyroot + S-OFF, which uses AndIRC's lengthy, yet effective, instructions, but wraps them up in one easy to use package. The program runs on Windows and weighs in at over 800MB, so fire up your PCs and get ready for some heavy downloading.
This article deals with a couple of advanced topics. If you’re unfamiliar with some of the terms, hit up our primers here:
Amazon's upcoming Android Market competitor, the Amazon Appstore, is in hot water for its namesake. On Monday, Apple filed a lawsuit in a California federal court claiming Amazon had infringed on its trademark of the phrase "App Store." Apple applied for a trademark to this name way back in 2008, but it wasn't approved until January of 2010. Since then, Microsoft has filed a dispute with the trademark office alleging that the grant was improper. That complaint's outcome is still pending.
In the meantime, Amazon may have a difficult time asserting that its use of "Appstore" (as opposed to "App Store") doesn't violate Apple's trademark - it's hard to deny that Apple's App Store is a well-know name in the mobile world.
When you think of Android's openness, what comes to mind first? Is it the open source code of AOSP? Or maybe nearly 200 devices that run the Android now? Perhaps tethering, built right into the OS? How about the GPLv2 license requirement for manufacturers to publish all changes to the Linux kernel simultaneously with each phone's release?
If you are a custom ROM developer or even user, that last bit there probably occupies one of the top positions, and rightfully so - without it, proprietary changes to the kernel would remain hidden and would need to be reverse engineered. Manufacturers, however, don't seem to treat this license requirement seriously and typically delay the kernel source release by an indefinite number of days or even weeks.