Android and openness is something we talk about all the time, but the recent developments in the industry point towards inherent flaws with this very premise. Be it from bloggers, political institutions or corporations, Android is seemingly not open enough. The “War on Openness” is ironically becoming an open war, where many players are increasing their stakes and scope to try and land a bigger hold - or at the very least, restrict Google’s - on what is the world’s...
Motorola to Unlock Atrix Bootloader in Future Update?
Well, it seems as if we’re either in the Twilight Zone or in a parallel universe now. First HTC and now Motorola appear to be playing nicely with us enthusiasts. In the latest version of the Motorola Atrix bootloader intended for Hong Kong and Taiwan devices, the bootloader appears to be unlockable upon entering everyone’s favorite fastboot oem unlock command twice.
Two days ago, XDA forum member tsouza noticed a rather strange incident posted in hex was observed in a thread asking for leaked keys on the Motorola support forums. While not exactly leaked keys, upon decoding, it read as follows:
Greetings, fellows. We know that you are dying for the unlocked bootloader. Moto is not the only “player” that has an influence over decision – carriers have their say in it too, so don’t just blame us – contact the carriers too. As a fellow engineer – my personal opinion is to not limit knowledgeable users by locked bootloader. But I also think that modding of the system sw voids the warranty – would you be willing to void a warranty by unlocking and modding the phone? Anyway, this is meant as a tongue-in-cheek little joke, not something to be taken seriously or to have conclusions drawn from it, nor is it in anyway representative of an official company view. Have fun!
Not the keys you were looking for? Certainly not. However, this gave XDA forum member eval- the idea to poke around the ascii and hex of several recent Atrix bootloaders. This paid off, as his search of the latest Hong Kong and Taiwan version of the bootloader yielded the following tasty morsel:
$ strings CG42.img | grep INFO ... INFOUnlocking your device can permanently VOID your warranty. INFOThis process cannot be reversed. If you wish to proceed, INFOreissue the unlock OEM command containing the unique ID INFOof your device:
Ultimately, this takes us back to our unfortunate frien-emies, our mobile providers. As always, it is they who fundamentally control the capabilities and functionality of our devices, at least initially. For us unfortunate souls in the US, this means AT&T, a company known for disabling basic Android functionality such as side loading applications from the start. Android is not the iPhone, and it will never be the iPhone. Locking it down to make it similar to the iPhone is not the answer. However, in one fell swoop, a move such as allowing an unlockable bootloader on a sanctioned device would alleviate much or all of the generally bad opinions and publicity AT&T has earned. AT&T, we implore you to do the right thing and not hinder the power users who would, in turn, become your biggest advocates and volunteer sales people.
Venture forth to the original thread to keep updated on any further developments. As for the possibility of an unlocked bootloader on your own personal device, you now know who to contact.
Want something on the XDA Portal? Send us a tip!
Smartphone cameras have advanced so tremendously over the past few years that they have almost completely replaced point and shoot digital cameras for the most of us. Furthermore, since our smartphones are always with us, the majority of us end up taking tons of photos throughout the lifespan of our devices. But what happens to all the old photos you take? Do you store them on an external hard-drive or keep them backed up to an online cloud service like Flickr? Let us know what your favorite way of storing old photos is and why.
Before the release of Android 5.0 Lollipop, the Holo Design guidelines served as the official reference for Android design, right from IceCream Sandwich to KitKat. However, updates to the guidelines were few and far between, leading to a lack of synchronization between Android design and current UI/UX trends. Google seems to have learned from their mistake the last time around, and earlier this week, a significant update was released for the Material Design guidelines, marking the second revision in less...