Since officially releasing the Nexus 7 (2013), Google’s latest device has been receiving positive reviews in general. However, some issues have come up, like some GPS problems that Google is aware of and is working on a solution. Another problem that surfaced that has the potential to impact Android fans beyond those who own the new Nexus 7 have been issues revolving around the release of Qualcomm binaries for the device. The issue was so contentious, that Jean Baptiste-Queru went so far as to submit his resignation and walk away from the AOSP project due to the difficulties in getting factory images released. Apparently the bad press related to that was more than Google could fathom as they have now released the factory image and binaries, including the Qualcomm files in question. » Read the rest
As excited as we are about the ushering of the new Nexus 7 tablet, there have been some quiet— but major technical snafus for the Android hardcore which has resulted in one of the most important pieces of the AOSP disappearing from the project all together. Tech stud Jean Baptiste-Queru officially confirmed the various rumors regarding his AOSP position and thus, confirmed that he was leaving everything all together because of his frustration with the difficulty of getting factory images for the newest Google tablet. Check out the following for his reasoning:
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.
The reasoning is certainly legit, but what’s really eye-opening is the part where he talks about a Google flagship device not being able to boot to the home screen because of the lack of GPU support. Android purists will recall that the Nexus 4— which also features a Qualcomm Snapdragon chip— originally didn’t have the factory image and source code released in full. Naturally the issues were addressed, but owners of the device weren’t able to enjoy the true Nexus experience since the source code/factory images couldn’t be modified. Now we’re going through the same exact issue as the Snapdragon-powered Nexus 7 doesn’t have the factory images available to the masses. Is it a coincidence that both devices that two Snapdragon-based Nexus devices have had factory image issues? Probably— but one thing’s definitely for sure: it’s certainly going to suck not having Jean Baptiste Queru for our AOSP needs. Hopefully the Android team will find some sort of fix or remedy for future Nexus devices.
source: Android and me
Some hawk-eyed hackers noticed something strange this morning: the factory images for the Nexus 4 seem to have disappeared from Google’s developer site. A factory image is a file that allows you to restore your device completely to stock in case something goes wrong while hacking and tinkering with your device. Interestingly, the Nexus 7, Nexus 10, and Galaxy Nexus factory images are all still available to download, indicating that the Nexus 4 factory images were deliberately pulled by Google to make some changes to the core code. Could it be that Google is trying to completely disable the recently discovered 4G antenna? We hope not. It’s anyone’s guess really, what Google is up to. Anyone have any good theories?
Source: Google Developers
Developers or others who enjoy flashing their phones have a nice new option available if they have a Verizon Galaxy Nexus smartphone. After starting the process of rolling out a Jelly Bean update to Verizon users earlier this week, the factory images are now available on the Google Developers site for download. Listed as version JRO03O, the file can be used to restore a Galaxy Nexus to factory state. Even if you are not inclined to flash your Galaxy Nexus for fun, you can always keep a copy of the image as a fail-safe in case something really bad happens with your phone.
source: Google Developers
Stock Jelly Bean factory images are now available for the Samsung Nexus S and Nexus S 4G. The builds are labeled as JRO03E and JRO03L respectively. I’m sure this will make many Nexus S developers happy!
You can head over to the source link for more information or download it yourself!
source: Google Developers
Have you been messing around a bit to much with the system files on your Jelly Bean powered Nexus device and want to return it back to its factory state? You in luck my friends as Google just released the factory 4.1.1 images for a few of the Nexus units, including the brand new Nexus 7. The devices with available factory images are as follows:
- Galaxy Nexus (yakju): Android 4.1.1 (JRO03C)
- Galaxy Nexus (takju): Android 4.1.1 (JRO03C)
- Nexus S (soju): Android 4.1.1 (JRO03E)
- Nexus S (sojua): Android 4.1.1 (JRO03E)
- Nexus 7 (nakasi): Android 4.1.1 (JRO03D)
As you can see, the Verizon Galaxy Nexus has been left of the list, and the Korean and Sprint Nexus S isn’t available either. This just goes to show that if you want to stay up to date with the latest Android OS it pays to go with a GSM kit. If you see your device listed above and want to grab its factory image, hit up the source link below.
source: Google Developers
Now that Verizon is pushing out the Android 4.0.4 update for their version of the Galaxy Nexus, Google has posted the IMM76K factory restore image. This image will allow those who have flashed custom software on their phones to restore their device’s original factory firmware… basically a way to get your phone back to stock in case things got a bit screwy. If you know what you’re doing, grab the files at the source link below.
So what do you do if you’ve totally screwed up your system software on your GSM Nexus device? You need to flash a factory image to get back to stock, and as luck would have it, Google has released the official 4.0.4 (build IMM76D) factory images for the international GSM version of the Galaxy Nexus and the European and T-Mobile unlocked Nexus S. Flashing these files will leave your phones as if they were brand new and completely updated.
Flashing a factory image requires that you are not shy around a command line and fastboot, so it’s not for the faint of heart. If you’re brave and own one of these Nexus devices, download the images at the source link below.
Good news for you owners of the Galaxy Nexus. The Android Building Google Groups page put up an announcement stating that a complete factory image for your Galaxy Nexus has been released. This image includes the bootloader, baseband, and the rest of the system. As we all know, Google phones have always been easy to root and the Galaxy Nexus continues this tradition. This factory image will restore your phone back to its factory state should you mess it up. If you are interested you can un-archive the package and check out all of the files individually, however, there is a “flash-all” script that has been added so that flashing to the factory state is easy to do.
Jean-Baptiste M. Queru, Software Engineer for the Android Open-Source Project, was quoted to say:
“hopefully this’ll be useful to people flashing custom AOSP builds, as it provides a clean supported way to return to factory state.”
Those of you who are interested in flashing your phone, you can head to the link below the break to get your image. If you haven’t rooted your phone yet and are interested in doing so, you can go here. This is certainly good news for the Android community. What about you guys? Does this help you breathe a little bit easier? » Read the rest