How to Update Galaxy Nexus (Maguro) With Milestone 6 AOKP Firmware

Samsung Galaxy Nexus has already received the official Android 4.1.1 Jelly Bean update which gives you the completely stock Android experience on the Galaxy Nexus GT-I9250. However,  I am sure that most of the people who happen to own Google’s latest Galaxy Nexus smartphone have stumbled across this dilemma at least once since they got their device: Should I keep going with the stock ROM or try a custom one? The thing is, it is not always easy to choose between the two, especially if your device is already among the top dogs in the Android world. Of course, this is your worst nightmare decision if you own the Galaxy Nexus, as it is currently the first device to receive all the Google made Android goodies, and going to a custom ROM might even delay the updates and fixes by a little bit. For this reason, we will present an easy and safe way of updating your Samsung Galaxy Nexus with the AOKP Milestone 6 Custom ROM.

What better it can get for Galaxy Nexus when it’s talked about one of the most successful project named as Android Open KANG Project (AOKP). AOKP has good bunch of developers who really come up with custom firmwares which are highly feature rich and come with many add on features which we will be checking out in the due course of this article.

Major changes to Milestone 6 since Milestone 5:

  • Removed FB sync
  • Added ability to hide sender and/or message body in notifications (Mms)
  • Added CM9 T-Mobile theme manager
  • Added Sense 4 style Task switcher (you have the option of choosing from stock/web os/sense 4 now)
  • Added ability to play boot sound (disabled by default) — read instructions in ROM Control > General > Boot sound
  • added delayed ring feature to Phone
  • added Emoji to Mms (enable in Mms settings)
  • added AOKP wallpapers app
  • added USB tether toggle,
  • added AOKP clock widgets
  • added notification counters
  • added nav bar widgets
  • added AOKP stats (www.stats.aokp.co) — you can opt out
  • added bluewall firewall – RC > General UI > Less Notification Sounds — limits the number of notification sounds an app can play per X seconds, so like 1 GTalk ping/30s, but notifications will still be coming in
  • added “copy to clipboard” option in “Share” dialogs throughout Android
  • added hardware info in about screen
  • added new music layout to lockscreen (you can choose between old and new)
  • added nfc toggle
  • added nfc polling settings (Settings > More > NFC polling mode)
  • fixed DRM issues

As we all know that rooted device is needed for custom ROM installation. In case if your device is not rooted then follow this guide “How to Root Samsung Galaxy Nexus” or through GNex Toolkit v7.8. If you already have rooted Galaxy Nexus, follow this step by step tutorial to install this ROM.

Note: You follow all the instructions at your own risk, we’re not responsible in any case if your phone is bricked.

Prerequisites before Updating Milestone 6 AOKP Firmware:

  • Ensure that your phone is rooted with help of Root Checker App.
  • Ensure that your phone has at least 60-70% battery life.
  • Backup all your contacts, logs, sms and rest of useful data.
  • Backup your existing ROM with help of CWM Recovery.

Steps to Update Galaxy Nexus with Milestone 6 AOKP Firmware:

  • Install latest CWM on your device.
  • Download Milestone 6 AOKP Firmware zip file on your PC.
  • Copy downloaded ROM zip file to the root of your phone’s SD card.
  • Reboot your phone into CWM recovery. Once entered in recovery mode, follow below mentioned steps.
  • First take Nandroid Backup then perform Factory Reset followed by Wipe Data, Clear Dalvik Cache, and then Clear Cache Data.
  • Now select option “install zip from sd card” then choose the zip file that you previously moved to you’s phone’s SD card and then follow on screen instructions.
  • After process completes, reboot your phone and enjoy your Milestone 6 AOKP Firmware.

Note: Just in a rare case if the device is not updated and it gets into the boot loop mode, you need to again clear the cache from the recovery mode and retry the whole process from the start.

Leave a Comment

Your email address will not be published.

*