How to Update Galaxy Tab Pro 8.4 3G SM-T321 to KitKat 4.4.2 ZCU1AND2
To have Android 4.4.2 KitKat delivered on your Galaxy Tab Pro 8.4 3G SM-T321, we have this guide for you. If you go with it, you’ll discover just how much more your tablet can offer.
If your tablet experiences something like Android 4.4.2, you’ll soon have more reasons to play with it. That has to do with the features it comes with. These are all delivered by one particular official firmware: ZCU1AND2. Last month was its release date and China is the country to have access to it.
If you don’t mind losing your tablet’s root access and its system partition, you will get rewarded with many goodies. The update has much to offer, such as battery improvement and new features. The new KitKat is also popular for bringing customization tweaks and new apps. Dealing with an update doesn’t mean dealing with security problems.
The tablet will lose its system partition and root access, but its data and internal / external SD cards won’t be ruined. But be sure to apply this tutorial only on the Samsung SM-T321. By using this model, you won’t risk bricking your device; you will do that if another gadget’s used.
The new firmware can’t be delivered on your tablet with KIES. The only other method, besides this guide, that you can use its this: OTA. This option, however, does need a device with stock ROM. Our tutorial doesn’t.
Prerequisites
Before immersing yourself in our guide, though, some pre-requisites apply:
- install USB drivers for the Galaxy Tab Pro 8.4 SM-T321 on your laptop;
- Windows has to be your laptop’s OS of choice;
- go to your notebook and disable, on it, the programs which protect it against various security problems;
- the tablet’s security software must also be turned off;
- the battery on your tablet needs to be charged;
- create some backups for the data on your tablet;
- a full NANDroid backup must be created after that;
- USB Debugging must be turned on.
Step by step instructions
- Since your tablet needs the , download it on your laptop. The latter also needs the presence of Odin v3.09. The files contained by these packages must be extracted on the previous device; use, for this step, WinRar, 7Zip or WinZip.
- Odin v3.09.exe is the file that must then be launched on your laptop. After opening it there, your tablet has to be booted in Download Mode via certain steps. Here they are: press and hold Home, Power and Volume Down for a while, then stop when a boot message comes up; once you see it appear, press Volume Up.
- The Galaxy Tab Pro SM-T321 can be plugged to the notebook with this: the tablet’s USB cord. After using it, you should wait for Odin to start the search for your gadget.
- Upon coming across it, you’ll soon notice the screen displaying a blue sign. This reveals the following: the two devices are now connected to one another as they should be. Continue by doing this: add the firmware file to AP / PDA.
- The step that comes up tells you to activate F. Reset Time and Auto Reboot. What should be done now is easy: uncheck Re-partition and then begin the firmware’s installation. This requires you to simply tap “Start“ and then wait for about 12 minutes (15 minutes at most).
- The installation of the ZCU1AND2 on your tablet will be signaled by “Pass”. But that’s not all: once this message is displayed in a green background, the Galaxy Tab Pro 8.4 3G SM-T321 will restart.
- If the device is done with the latter, you will have to perform this guide’s last step. To accomplish this, disconnect the tablet from your laptop. To end this quickly, the USB cable needs to be taken out.
- [sc name=”banner-jos”]After you’re done with this final step, you have to actually launch the new OS. This requires tapping some important options: Settings and About Tablet. When you’ve done as instructed, the Android 4.4.2 will be ready to introduce all of the novelties we promised earlier.
Get a taste of them first, then decide if they’re what you had in mind. If any of them doesn’t feel right, you have the option of restoring the old ROM. The NANDroid backup file was created for this action, so use it. But there’s a catch: getting the old ROM back means giving the upgrade up.
If this procedure left you with questions, fire them away below.