Update Sprint Samsung Galaxy Nexus to Jelly Bean 4.1 Team EOS custom ROM

Team EOS Jelly Bean custom ROM Update for Sprint Galaxy Nexus

Sprint Samsung Galaxy Nexus has received a new custom ROM installation that you can flash easily using the instructions I’ve listed in this article. This custom ROM has been created by the popular Team EOS and it will bring a customized Jelly Bean release for the Sprint model of Galaxy Nexus. Read the entire tutorial before beginning to install this Android 4.1 Team EOS custom ROM firmware files.

The Android 4.1 custom ROM by Team EOS will bring multiple improvements and  numerous new features and services that can be used only with Jelly Bean firmware. This ROM is an early version and it might have some bugs and errors which is why you should use it only for testing purposes. The Team EOS ROM is an nightly build and it might have all the features included but it can still have problems. However, the Google Now service works and this is the main reason why you should try this release.

Now that you know all of this general info, you should move to the preparation guide and learn what steps you need to take so that you;ll correctly configure the device for the Jelly Bean 4.1 ROM installation. Use the comments field in case you can’t understand some instructions. Here’s what you need to do before moving to the tutorial guide:

  • The Team EOS Jelly Bean custom ROM works only with the Sprint Galaxy Nexus device. Do not attempt to install it on any other smartphone or tablet system.
  • Your device should be rooted and CWM Recovery image should be installed on it. This universal tutorial guide for Galaxy Nexus devices HERE will help you root and flash CWM Recovery.
  • Your device’s bootloader should be unlocked.
  • The tutorial guide will ask you to wipe all data and factory reset, which is why you should create a full backup of the currently installed ROM. If you wish to backup only several files, then you should move them on the device’s sd card, as this one will be left unchanged by the custom ROM install process.
  • To save applications, SMS, Call Logs and APN Settings, then you should use the following Android tools: AppBAK for Android apps backups | SMS backup & restore | Call Logs backup & restore | APN Settings Backup & Restore.
  • Enable USB Debugging option for your phone.
  • If you wish to save the Phone Contacts, then you should sync them with your Gmail account. In case you don’t know how to do it, then you should use this guide here.
  • Charge the phone’s battery until it reaches at least 70% power level and this will prevent it from powering off while you’re flashing the new custom ROM files.
  • This tutorial is destined to be used only by advanced Android users and in case you have problems in completing the tutorial, then you should use the comments section and tell us exactly where you got stuck. We will help you finish the installation of EOS Jelly Bean 4.1 custom ROM on your Sprint variant of Galaxy Nexus phone.

Now that you’ve read all of the above, move to the tutorial guide. Make sure that you apply all the steps I’ve listed. Do not skip any steps as that will result in a failed attempt to flash the new ROM.

Install Team EOS Jelly Bean custom ROM on Sprint Galaxy Nexus

  1. Download the Jelly Bean Team EOS custom ROM zip HERE. Save it on your PC. Make sure to download the latest Nightly build.
  2. Next, download the GApps zip file HERE. This file will install Google Apps, tools that you need in order to gain control over all Jelly Bean features.
  3. Move these two files on your Sprint Galaxy Nexus sdcard. After you’ve completed this task you should power OFF the phone and boot into CWM Recovery mode.
  4. Press ‘power’ + ‘volume down’ + ‘volume up’. This will open Fastboot mode. Select ‘Recovery mode’ and confirm that you wish to boot it. Now your device will boot into CWM Recovery mode and you can move to the next step.
  5. Now select ‘wipe data/ factory reset’ and confirm this action. Now your device will see that all files removed from your phone’s memory, which means that only the applications will be deleted and the ‘sdcard’ contents will be left unchanged. After the wipe data process is complete you should continue with the custom ROM installation.
  6. Select ‘install zip from sdcard’ and from the next screen you have to select ‘choose zip from sdcard’. Find the Jelly Bean custom ROM zip and install it.
  7. Repeat step 6 but this time you have to install the GApps zip. When both, Google Apps and custom ROM zips, have been successfully installed you should return to the main CWM Recovery screen.
  8. Select ‘reboot system now’ and wait for the first boot process into Team EOS Jelly Bean 4.1.1 custom ROM completes. Note that this will take a while before completion and you should wait. If the first boot process takes over 15 minutes to complete or the device gets stuck in a boot loop, then it means that the custom ROM installation failed and you will have to remove the phone’s battery, re-insert it and restart the entire tutorial and the second time you should manage to complete the update.

When the Android 4.1.1 Jelly Bean home screen boots normally, it means that you have successfully flashed the new Team EOS custom ROM and you are now free to start using the device. However, if you wish to force the ‘voice recognition search’ to work with Google Now service, then you should use the guidelines below:

  • Open Settings from the Android app drawer.
  • Open ‘Language & input’ and after that you need to scroll to the ‘Speech’ menu.
  • Click ‘Voice search’.
  • Tap ‘Download offline speech recognition’. Swipe to the ‘All’ button.
  • Now download all the speech packs you want to use as your language.
  • That’s it, now your device will be able to run offline voice speech recognition service.

If you have any extra questions, then please use the comments section and you will get the answers you’re looking for. Use this new custom Jelly Bean Android 4.1.1 ROM at your own risk and make sure that you know the risks that you’re taking when flashing such custom installations. Remember that we cannot be blamed in case your device starts showing errors and multiple services will display ‘force close’ pop-ups.