Rooting was never an easy process on Samsung Galaxy Note 2, a device that promised to be an alternative for the 7-inch touchscreen solution. With a 5.5-inch HD Super AMOLED screen, a quad-core processor and an original Android 4.1 preinstalled, Galaxy Note 2 is a device that can a lot of things but has its own few limitations. That’s why, a root process is need in order to release the full power of this amazing phone. Because rooting means first wide privileges and a reconfiguration of the original stock, users that have Samsung Galaxy Note 2 are trying each day enter into the deep sides of the subsystem, ones succeeding, others messing things very bad.
Once you rooted the device, advantages are priceless: full access to all the system, you can run special applications with root permissions, enable tethering or control app permissions. To better understand imagine that you are in Windows and you gain Admin privileges. But there are some disadvantages too: you lose warranty, the most important of them, you expose yourself at security risks or you can damage the device. For other information about rooting process you can read this tutorial.
So what is with the XXUEMK4 Jellybean 4.3 Android Firmware? XXUEMK4 Jellybean 4.3 Android Firmware is, as you would easily guess, a special release for Samsung Galaxy Note 2, a version that can be used to update the device until the Android KitKat 4.4 upgrade will be available. Android 4.3 Jelly Bean new firmware has lot of amazing futures, including Galaxy Gear Support and TRIM Support for a speed boost. It can be manually installed with the help of ODIN as you will see bellow, but also taking a change with Samsung KIES. The following tutorial will explain how to use Android 4.3 build XXUEMK4 firmware in a rooting.
How to Root Galaxy Note 2 running XXUEMK4 with Android 4.3 Firmware:
Before you begin:
- Activate USB Debugging Mode – Go to Settings, then Applications. Once here, choose Development and tick USB debugging.
- Make sure you have at least 70-80% battery life.
- Backup SMS, Contacts, Call Logs, multimedia content (move to SD Card or MicroSD), APN, MMS Settings (go to Apps-Settings-Wireless and Network-Mobile Networks-Access Point Names and copy them in Notepad).
- You can backup data even with Samsung KIES or ClockworkMod, TWRP already installed on the device to be rooted. To use ClockworkMod or TWRP read this tutorial.
- Verify to have an unlocked device not depending on any career.
- Go to Settings-About phone and make sure you have the GT-N7100 model as the rooting may be a big mess because the the Android 4.3 XXUEMK4 Jelly Bean firmware works ONLY on this model.
Now, after all this checks, lets see how to do a correct root without any „leakage”:
- Grab Jellybean 4.3 Firmware from this page and Odin from here.
- Download the Rooting tools here.
- Unrar downloaded archives and execute Odin.exe as Admin.
- Shut down smartphone.
- Press Volume Down+Menu Button+Power On in the same time. Now you are in Download Mode.
- Plug in your device to PC via USB cable.
- ID is now available ( COM section becomes yellow if the drivers are loaded properly and wait for “Added!” message). If the drivers were not been properly installed use another USB port / flash.
- Enter PDA and choose the rooting file from the root tool archive.
- Choose F. Reset Time and Auto Reboot from Odin and Re-Partition option ( only if you select .pit file ).
- Hit „Start” and the firmware update is ready to be loaded.
- Wait up to 4 minutes.
- The device auto reboots.
- You will see a „PASS message” with green background placed in the top of Odin.
- Plug out the USB and boot it into Recovery Mode – press at a same time Volume UP+Home+Power.
- Select Factory Reset-Wipe Data from the menu.
- Power off. Done!
Note! The process may fail ( find out if the rooting is ok with „Root Checker” application downloadable from Google Play Store ). In this case, follow again same steps above after reset the phone by removing the battery and reinserting it.
Some users complained so far that the Knox Security app is blocking the SuperSU. To solve this problem use Titanium Backup and block: Knox Notification Manager v1.0, Knox v3.0; v1.0; Agent v1.0 and the Store v1.0.