How to Get the Galaxy Nexus & Nexus S Android 4.1.2 Updates Right Now

It appears that the Android 4.1.2 Jelly Bean update, that rolled out for the Nexus 7 tablet a short time ago, is now rolling out to the GSM models of the Samsung Galaxy Nexus and Nexus S. And if they are like the Nexus 7 update, they are likely rolling out slowly. That being said, there is a way to attempt to get the updates right now.

According to numerous tips, some GSM models of the Galaxy Nexus and Nexus S smartphones are currently receiving the upgrade to Android 4.1.2 Jelly Bean, Google’s latest piece of mobile software.

Like the Nexus 7 Android 4.1.2 Jelly Bean update that arrived last week, the Android 4.1.2 update appears to be an update aimed at improving stability and fixing some of the problematic bugs that users have been dealing with.

Read: Nexus 7 Android 4.1.2 Jelly Bean Update Rolling Out Slowly.

android-jelly-bean

Android 4.1.2 Jelly Bean has rolled out for some GSM Galaxy Nexus and Nexus S devices.

It also appears, according to The Verge, that the update comes with at least one new feature for Galaxy Nexus and Nexus S owners. While the Nexus 7 got the the ability to view the home screen in landscape mode, it doesn’t appear as though the Galaxy Nexus and Nexus S were graced with that feature. Instead, it looks like owners can now open the expanded Notifications that came with Android 4.1 Jelly Bean with one finger as opposed to one.

Advertisement

Obviously, that’s not a ground-breaking feature, but it’s certainly a welcomed one.

Again, the update is rolling out to GSM versions of the Galaxy Nexus and Nexus S. This means that those who own the devices on Sprint and Verizon are likely in for a much longer wait. Unfortunately, there is no word yet on when the Android 4.1.2 Jelly Bean updates for the Verizon Galaxy Nexus, Sprint Galaxy Nexus, and Nexus S 4G might roll out.

Over the weekend, the Motorola Xoom Wi-Fi only model started to receive its Android 4.1.2 Jelly Bean update which means the other Nexus devices are likely next in line to get this version of Jelly Bean though a release date remains unknown.

Those who own the GSM models of the Galaxy Nexus and Nexus S will be prompted when the update is available though it’s probably worth going into the devices settings to check for the update.

To do that, simply head to the About section of the Settings and Check for the update. If it’s indeed available, the download and installation process will begin. There is also a trick that those who own one of these devices should try in an attempt to get the update installed. Here are the instructions.

1. Go to Settings -> Apps -> All

2. Find Google Services Framework.

3. Tap on Force Stop.

4. Select Clear Data.

5. Head back to the Settings, go to About, and check for a System Update.

It may take a couple of tries but for many, a prompt to install the update will appear and Android 4.1.2 will begin to download and install.

In addition, those who own a Galaxy Nexus can install manually using the these instructions on XDA-Developers forums. Only those who are familiar with the process should attempt this.

Those that do will also want to make sure to select the proper version of the device before installing.

  

Comments

  1. AS says

    This is fallacy. This “method” only works if you’re already loaded to a Google OTA server, ready for the push. Here’s my personal copypasta with some more information:

    Some additional information: The way the OTA updates are handed out is by IMEI or internal unique identifier. Batches of these numbers are loaded onto the OTA servers, then when a phone checks in which it does on it’s own every few hours you are given the update.
    This only works if your unique identifying number has been loaded onto the OTA servers and at best it will only let you get the update an hour or two “earlier” than you would have already got it.
    Clearing the Google Services Framework resets a LOT of shit. For me when the JB update was rolled out to the EU GN’s, several of my sync options went FUBAR and some other data was reset/lost. It also fucks your Maps right up and you won’t be logged into a lot of accounts the first time you come to use them again.
    While this update may save you an hour, it was really not worth the bother for the amount of messing about I had to do to get everything back to normal from clearing the Google Services Framework. You will get the update when your phone identifier is loaded onto an OTA server AND NOT BEFORE. It is impossible to force the update using this method if it wasn’t already available to you.
    I just wanted to let people know that this is mostly a placebo. The reason some people do it once and it works is because they’re loaded onto an OTA server already. The reason it works for some people after 20 tries is because you sat there for 3 hours doing it while they approved the update for your batch.
    TL;DR – This works if the update is already available to you and not before. Updates are rolled out in batches. This method is mostly a placebo that will not save you days or probably even hours of waiting. Best to just wait and not lose your Google Services Framework data.

  2. sebster says

    Did not work for me unfortunately !! Is being in Canada the problem?! Is it because of my phone company ?

Leave a Reply