Go Back Forums > General Chat > Tablets and Smart Phones
Tablets and Smart Phones Got that new HTC or Samsung Galaxy ? Discuss mobile devices, pads and tabs here.

Thread Tools Display Modes
New Nexus 7 Factory Images Not Available; JBQ Leaves AOSP
PhazeDelta1's Avatar
Videocard: EVGA 1080 FTW
Processor: Intel i7 6700k
Mainboard: Asus Sabertooth Z170
Memory: 32GB Corsair 2666MHz
Soundcard: Magni 2 Uber/Modi 2 Uber
PSU: EVGA SuperNOVA 1000 G3
Default New Nexus 7 Factory Images Not Available; JBQ Leaves AOSP - 08-08-2013, 00:43 | posts: 15,652 | Location: USA

Now thatís a doozy, isnít it? Before proceeding, letís take a moment for that to better sink in. In addition to support from the AOSP, one of the hallmarks of the Nexus program has traditionally been the availability of factory restore images. This is more than a simple convenience for Nexus device owners. Rather, it allows for users to safely and reliably restore their devices to their factory state.

As a result of the availability of factory restore images, Nexus device owners always had a safety net available for when (not ďifĒ here at XDA) they decide to leave the confines of stock software and venture into the realm of aftermarket development. And the loading of unsupported firmware was always a relatively supported task, as evidenced by the availability of the simple command fastboot oem unlock.

There have been minor inconveniences along the way, however, as exemplified by the Nexus One and Nexus 4 factory images. Ultimately, these issues were all resolved in some way or another. For the Nexus One, HTC was able to release factory images. And for the Nexus 4, Google released the images after some time had passed. However one thing links these devices, along with the new Nexus 7 (2013): Qualcomm.

As a quick refresher, the Nexus One used the original Snapdragon system-on-a-chip with a single core Scorpion CPU mated to an Adreno 200 GPU. The Nexus 4 uses the Snapdragon S4 Pro, which features four Krait CPUs and an Adreno 320 GPU. Finally, the Nexus 7 uses a potentially lower-binned Snapdragon 600, which has been relabeled as an S4 Pro. And coincidentally, all of these devices have faced significant setbacks in their factory image availability.

The suspicions of Qualcommís intrusion into the procedure were then confirmed by the former technical lead of the AOSP, Jean-Baptiste Queru, when he wrote the following on Google+:

Well, I see that people have figured out why Iím quitting AOSP.

Thereís no point being the maintainer of an Operating System that canít boot to the home screen on its flagship device for lack of GPU support, especially when Iím getting the blame for something that I donít have authority to fix myself and that I had anticipated and escalated more than 6 months ahead.
While this was the most clearly the issue has thus far been stated, his followers knew something was amiss ever since JBQ tweeted on the matter back on July 30th:

That feeling when lawyers sabotage the launch you spent 6 months working on? I haz it. Sad sad sad sad sad sad.
The bottom line of the factory image drama is simple: We currently have no officially supported way to factory restore our Nexus devices. We donít know if this will be solved by Google and Qualcomm like it was for the Nexus 4, or if this will remain a longer-standing issue requiring the intervention of an OEM partner, as was the case with the Nexus One. And finally, this forced the man ultimately in charge of the technical side of the Android Open Source Project to resign.

Luckily, there are options available for users looking to restore their factory firmware, thanks to XDA Senior Member ATGAdmin who released a factory restore package for users in need. In fact, a certain editor-in-chief of a certain mobile development forumís news site already had to make use of such accommodations after some late-night flashing without adequate precautions left him with an unusable slab. However, these images are unsupported, and it would ultimately be better if they were to come from Google themselves.

Because of this issue, and past issues like it, the future direction of the Android Open Source Project is unfortunately all too nebulous. Itís times like these that weíre grateful that other open source options are beginning to emerge.

Today is a sad day for Android

So I'm going to go out on a limb here and say this will probably apply to any Android device that had a Qualcom chipset. Not just the Nexus devices.

Last edited by PhazeDelta1; 08-08-2013 at 00:45.
Reply With Quote
Ancient Guru
DesGaizu's Avatar
Videocard: JetStream 980 Ti 1400MHz
Processor: i5-2500K 4.5 GHz
Mainboard: Gigabyte Z68XP-UD4
Memory: 16GB DDR3 2133MHz
Soundcard: D1+A2+/X2 Fidelio
PSU: Seasonic X-850 Gold
Default 08-08-2013, 02:52 | posts: 3,600 | Location: UK

Originally Posted by PhazeDelta1 View Post
So I'm going to go out on a limb here and say this will probably apply to any Android device that had a Qualcom chipset. Not just the Nexus devices.

No just the new nexus 7. This happened when the nexus 4 came out also (has a quad core qualcom) but was sorted a few months after release.

Hopefully this will get sorted too but it's sad that it's pushed him out of his job.
Reply With Quote
Pill Monster
Videocard: 7950 Vapor-X 1100/1500
Processor: AMD FX-8320 @4.7
Mainboard: ASUS Sabertooth 990FX R2
Memory: 8GB HyperX Beast 2400
Soundcard: X-Fi Fatal1ty, Wharfedale
PSU: AcBel M8 750 Bronze
Default 08-08-2013, 03:12 | posts: 25,234 | Location: NZ

It'll get leaked.
Reply With Quote

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump

Powered by vBulletin®
Copyright ©2000 - 2017, Jelsoft Enterprises Ltd.
vBulletin Skin developed by:
Copyright (c) 2017, All Rights Reserved. The Guru of 3D, the Hardware Guru, and 3D Guru are trademarks owned by Hilbert Hagedoorn.