Skip to main content

How to Install Android 4.2.1 Jelly Bean AOKP Build 2 ROM on T-Mobile Samsung Galaxy S3 T999



The second build of AOKP (Android Open Kang Project) custom ROM based on Android 4.2.1 Jelly Bean for T-Mobile’s variant of Samsung Galaxy S3 with model number T999 has recently been released. Aside from the fact that it brings the latest Android version, it also comes with cool features many Android users want to see in their devices. AOKP ROMs are often based on AOSP (Android Open Source Project) firmware stuffed with stock features, bug fixes and performance boosters. Users who are willing to take the risk just to know what this ROM brings can proceed at their own risk. We have crafted a few reminders and requirements for you so everything will work like a charm.
Reminders
  • Never forget to backup all your important data before you flash Android 4.2.1 Jelly Bean AOKP Build 2 ROM in your device just to keep them safe.
  • This is an unofficial ROM. Once installed, you device’s warranty will be considered void. There are also some risks that you might damage or brick your device so be extra careful.
  • This custom ROM was built for Samsung Galaxy S3 under T-Mobile or those that have model number T999. Please check the model number of your phone by going to Settings > About phone.
  • This guide is intended for reference purposes only, you may or may not follow the guide we provide below.
Requirements
  • Check that your Galaxy S3 T999 has at least 70% battery. That should be enough to complete the flashing of this ROM. If you can, it is most recommended you fully-charge your phone before anything else.
  • Install necessary drivers if you haven’t already. This is to make sure your phone can be detected properly by your computer.
  • Enable USB Debugging in your phone.
  • Your device should be rooted and ClockworkMod Recovery installed.
Step-by-step Guide to Flashing Android 4.2.1 Jelly Bean AOKP Build 2 ROM
  1. Connect your phone to your computer using the original USB cable. Check if it is properly detected by your computer by going to “My Computer.” If you can find your device, try to browse to any directories in it. If you can do so, then there is a good connection between your device and your computer. Otherwise, re-install drivers.
  2. Download AOKP Build 2 ROM directly into the root directory of your phone’s internal memory. [LINK]
  3. Download Google Apps into the same directory as with the custom ROM. [LINK]
  4. If you are done downloading those two packages, turn your device OFF.
  5. Boot your phone into Recovery Mode: press and hold VOLUME UP, HOME and POWER buttons simultaneously until the screen flashes.
  6. Make a Nandroid backup of your current ROM. This is a fail-safe in case everything gets corrupted during the process. You can just restore your current ROM via ClockworkMod Recovery. To do so, choose Backup and Restore > Backup and return to main menu after.
  7. Perform a full data wipe: Wipe Data/Factory Reset > Yes. Return to the main menu after wiping data.
  8. You also need to wipe Dalvik cache: Wipe Cache Partition > Wipe Dalvik Cache.
  9. Start flashing AOKP custom ROM: Install zip from SD Card > Choose zip from SD Card. You’ll automatically be brought by ClockworkMod Recovery to the root directory of your device’s internal memory. All you need to do is find the zipped file (aokp_d2tmo_jb-mr1_build-2.zip) you downloaded a while back. Wait until the flashing is done. You will be brought back to the main menu.
  10. Follow step #9 but choose the zipped Google Apps (gapps-jb-20121212-signed.zip) instead of the ROM. Wait until the flashing is done and that you are brought back to the main menu.
  11. Choose Reboot System Now option.
The entire process may take several minutes to complete. Be patient, wait and never interrupt during the flashing. The first reboot may take a minute but wait until your device becomes active before using it.

Comments

Popular posts from this blog

How to fix Samsung Galaxy Note 8 that no longer charges

Many Samsung Galaxy Note 8 owners took to online forums to complain about their phones that reportedly stopped charging for some reason. Others, of course, contacted Samsung about it and while the company didn't provide further information about the problem, it somehow acknowledged that there were indeed reports about said problems. Samsung takes all reports of this kind, of course, seriously. We have received only a very small number of customer inquiries that can be linked to charge management. Unfortunately, we can only comment on the matter further, if we have more detailed information about the affected devices. But isolated or not, those who are affected by the problem may not be able to use their devices anymore. But charging problems may actually not that complicated and I know some owners who have actually made their devices charge and turn on again. That's what I'm going to share with you today--the fix. What to do if your Galaxy Note 8 won't charge

Samsung Galaxy S7/S7 Edge Notification Light Colors and their Meaning

LED indicators are among the key components of every Samsung Galaxy devices including the latest Galaxy S7 and S7 edge variants. In this post, I have elaborated each of the notification light colors you can see on your device so those who are not yet familiar with them would have an idea of what each of these colors mean when they manifest on your Galaxy device. Generally, the LED indicator is located on the upper-left front of a Galaxy device, displaying various colors such as blue, red, and green. These three colors are used to indicate standard notifications and functions of your device.  To give you more hints, here's what each of these colors mean: Blue - the blue LED either appears to be pulsing or blinking. A pulsing blue light indicator means that the device is turning on or off. A blinking blue light indicator on the other hand indicates that you have an unread notification, missed call, or messages. A blinking blue light also shows when you are voice recor

How to Solve Google Play Store Server Error on Samsung Galaxy S3

Are getting Google Play Store error 403 on your phone today? Here are the solutions to your problem: How to Fix Google Play Store Error 403 Also read: Galaxy S3 Play Store error 403 after 4.3 update   Scenario:  I’m wondering if you could help me solve an annoying problem I have with my Samsung Galaxy S3 play store server. It’s been a couple of months now since I tried to access Google play store server with my phone but I keep getting a server error message. Usually, the message prompted on a grey screen. I can’t remember a time that I’d changed anything on my GS3 phone settings that’s why I’m wondering how I got this error. In an attempt to get this problem resolved with my own, I tried to clear the cache, restarted my phone and then uninstalled the updates. But still, it didn’t work out. I also contacted the tech support and all they told me to do was the same thing I did, clearing the cache and rebooting the phone. Appreciate if you have any workarounds for this one. Solu