Project

General

Profile

Install UA on your Galaxy Tab 2 7.0 / Tab 2 10.1 (GSM)


You need a custom recovery installed on your device. You can follow this instruction to get a custom recovery installed on your device via Heimdall.

Install via recovery

Install via TWRP:

  1. backup all important files (e.g. contacts) and store them on your MicroSD-Card or on your PC/Laptop
  2. copy the rom and gapps you like to install to your MicroSD-Card (make sure Gapps match the Android version of the Rom!)
  3. boot into TWRP
  4. make a backup of your current running rom and store it on your MicroSD-Card or on your PC/Laptop (some of the following are named slight different depending on the recovery you use)
  5. Make a full wipe:
    • wipe -> format data -> type "yes" to continue (Warning! Format Data will format your internal Storage! Make sure you have made a backup of important data! This can't be undone!
      Note: This step is needed to use encryption on your internal storage, "Format Data" will keep some space for the "footer" which is needed by encryption!)







    • wipe cache
    • wipe dalvic cache
    • wipe/format system



  6. reboot your recovery once!





  7. Back in recovery you now flash the rom
  8. flash gapps
  9. reboot and give your device some time to do it's first boot!


Installing a custom recovery via heimdall

Samsung devices come with a unique boot mode called Download Mode which is very similar to Fastboot Mode on some devices with unlocked bootloaders. Heimdall is a cross-platform, open source tool for interfacing with Download Mode on Samsung devices. The preferred method of installing a custom recovery is through this boot mode. Rooting the stock firmware is neither recommended nor necessary.

  1. Download and install the Heimdall Suite from here
    • Windows: Extract the Heimdall suite and take note of the directory holding heimdall.exe. You can verify Heimdall is working by opening a command prompt in this directory and typing heimdall version. If you receive an error, be sure that you have the Microsoft Visual C++ 2012 Redistributable Package (x86/32bit) installed on your computer.
    • Linux: Pick the appropriate installation package based on your distribution. The -frontend packages are not required for this guide. After installation, heimdall should be available from the terminal; type heimdall version to verify installation succeeded.
    • Mac: Install the dmg package. After installation, heimdall should be available from the terminal; type heimdall version to verify installation succeeded.
    • Building from source: The source code for the Heimdall Suite is available on Github. For more details about how to compile the Heimdall Suite, please refer to the README file on Github under the relevant operating system directory.
  2. Download recovery - You can directly download a recovery image using the link below, or visit TWRP site to check for the latest version of recovery for your device (if your device can be found there).Recovery: Download
  3. Power off the Galaxy Tab 2 7.0 / Tab 2 10.1 (GSM) and connect the USB adapter to the computer but not to the Galaxy Tab 2 7.0 / Tab 2 10.1 (GSM), yet.
  4. Boot the Galaxy Tab 2 7.0 / Tab 2 10.1 (GSM) into download mode: Hold '''Power''' and '''Volume Up'' . Accept the disclaimer on the device. Then, insert the USB cable into the device.
  5. Windows (only) driver installation - ''Skip this step if you are using Linux or Mac''
A more complete set of the following instructions can be found in the [Zadig User Guide](http://github.com/pbatard/libwdi/wiki/Zadig).
  1. Run `zadig.exe` from the Drivers folder of the Heimdall Suite.
  2. Choose Options » List All Devices from the menu.
  3. Select Samsung USB Composite Device or MSM8x60 or Gadget Serial or Device Name from the drop down menu. (If nothing relevant appears, try uninstalling any Samsung related Windows software, like Samsung Windows drivers and/or [Kies](http://en.wikipedia.org/wiki/Samsung_Kies)).
  4. Click '''Replace Driver''' (having selecting "Install Driver" from the drop down list built into the button).
  5. If you are prompted with a warning that the installer is unable to verify the publisher of the driver, select '''Install this driver anyway.''' You may receive two more prompts about security. Select the options that allow you to carry on.
  6. At this point, familiarize yourself with the ''Flashing with heimdall'' notes below so that you are prepared for any strange behaviour if it occurs.
  7. On the computer, open a terminal (or Command Prompt on Windows) in the directory where the recovery image is located and type:
heimdall flash --RECOVERY recovery.img
  1. A blue transfer bar will appear on the device showing the recovery being transferred.
  2. Unplug the USB cable from your device.
NOTE: Be sure to reboot into recovery immediately after having installed the custom recovery. Otherwise the custom recovery will be overwritten and the device will reboot (appearing as though your custom recovery failed to install).
  1. Manually reboot the phone into recovery mode by performing the following. Hold '''Power''' and '''Volume Down'''
  2. The Galaxy Tab 2 7.0 / Tab 2 10.1 (GSM) now has a custom recovery installed. Continue to the next section.

Notes about Flashing with heimdall

  • In Windows 7 UAC (User Account Control) may need switching off. Once Heimdall is finished it can be re-enabled.
  • Protocol initialization can fail if the device is connected via a USB hub - connect the USB cable directly to the PC.
  • It may be necessary to run the heimdall flash command as root in Linux or Mac OS X:
  • sudo heimdall flash [...]. Typical symptoms of this are:
    • a blue bar doesn't show up after the process has finished
    • Failed to confirm end of file transfer sequence!
  • It may be necessary to capitalize the name of the partition on some devices. Try `--KERNEL` instead of `--kernel` and/or `--recovery` instead of `--RECOVERY`.
  • If on Linux 64bit you get "unable to execute ./heimdall: No such file or directory", try the 32bit version and make sure to run it with sudo.
  • On Mac OS X you may see this message: "ERROR: Claiming interface failed!". If so, you need to disable the default USB drivers with the following commands:
sudo kextunload -b com.apple.driver.AppleUSBCDC;
sudo kextunload -b com.apple.driver.AppleUSBCDCACMControl;
sudo kextunload -b com.apple.driver.AppleUSBCDCACMData;
  • If you have installed Samsung Kies, you may further need to unload those USB drivers with the following commands:
sudo kextunload -b com.devguru.driver.SamsungComposite;
sudo kextunload -b com.devguru.driver.SamsungACMData
sudo kextunload -b com.devguru.driver.SamsungACMControl
  • Using Heimdall version 1.4.0 (the latest version available for download on the Glass Echidna website) you may see this message or one similar to it:
Error: Failed to confirm end of PIT file transfer!
  • If you experience this error, get the latest version on GitHub with the issue patched.
  • The stock ROM may overwrite your custom recovery on boot. To prevent this, boot immediately into recovery after leaving Download Mode instead of letting the ROM boot up normally. If your recovery is overwritten, simply redo the steps you followed above and catch it before it boots next time.
  • Some users have reported connection errors if the device is connected to a USB hub. If you experience such errors it is recommended that you try connecting your device to a USB port on the motherboard.
  • Antivirus software may prevent Heimdall from connecting properly. Disable your antivirus before proceeding.
  • When Heimdall fails to connect, the Download mode may get stuck, making all further attempts fail too. To retry, you may need to restart the Download mode: turn off the phone by holding Power for 5-10 seconds (or by pulling out the battery), then boot into Download mode and run Heimdall again.
  • If Heimdall fails to connect (errors related to initializing the protocol, or transferring data):
    • if you just installed the driver, try rebooting your computer and trying again.
    • if you still have troubles after reboot, in Zadig try installing the libusbK driver rather than the WinUSB driver.
(Template based on https://wiki.cyanogenmod.org/w/Template:Samsung_install)