How to Root Nexus 7 (2013) on Jellybean 4.3 Android Firmware – Guide

For all those users who have already bought the Nexus 7 (2013) Android tablet, you can now root the device without much hassle. So, before we proceed onto the detailed guide on how to root the device, you will have to make sure that you have to follow all the list of quick pre requisites. Once you have rooted your Nexus 7 Android tablet, you can then install the apps which need the root access and also the custom ROM firmwares which will be coming out very shortly. Please note that the rooting process can be revoked or the device can be unrooted at any point of time.

NEXUS-7-2

Quick Pre Requisites:

  • All the data in your Nexus 7 (2013)  should be backed up with the help of below mentioned steps so as to make sure that just in case if the data gets lost or corrupted, the same can be restored with the help of below mentioned steps,

SMS – Use “SMS Backup & Restore app”,
Contacts – Sync with the Gmail application,
Images, Songs, Videos, Files – Copy to internal / External SD Card,
APN and MMS Settings – Note down from the path “Applications > Settings > Wireless and Network > Mobile Networks > Access Point Names

  • Enable the USB Debugging Mode in your computer from the path “Settings > Applications > Development > USB debugging”. Also, the minimum battery life should be a minimum of 40% or else there is a risk of device getting turned Off in the middle of firmware update.

Disclaimer: Follow all the instructions mentioned in this article as if there is any damage caused due to not following instructions then we shall not be held liable or responsible. Just in case if you face any issues then we will try our level best to address the same.

  • Make sure that you have installed the ADB in your computer which will facilitate the rooting process.

Assuming that you are done with all the above mentioned steps, proceed to the next page where we have mentioned the detailed guide on how to root your Nexus 7 2013 edition.

11 Comments
  1. Reply bob August 1, 2013 at 7:03 am

    Everyone who posts here, if you can get to the adb reboot bootloader piece, please post the BOOTLOADER VERSION. Mine is FLO-03.14

    I’m having the issue also

    • Reply bob August 1, 2013 at 7:04 am

      waiting for device.

      yeah, no greater or lessthan signs here…

    • Reply bob August 1, 2013 at 7:05 am

      oh, and I used the orig cable

    • Reply bob August 1, 2013 at 7:07 am

      fastboot devices
      shows nothing

      I’m fairly certain this is a driver issue. I took the update to 4.3 when it came OTA ( well, wifi air ) and nothing that works for others works for me.

  2. Reply Ajay Ranjane July 30, 2013 at 8:11 pm

    Will this work my HCL ME Connect 2G 2.0 Tab?
    If not then pls suggest me something else.

  3. Reply Lord Taximania July 28, 2013 at 4:00 pm

    I couldn’t get this to work. Then I re-read the article.
    With the help of the original USB cable.

    Worked first time ;-)

  4. Reply robert palmer July 28, 2013 at 7:26 am

    this guide implies that the TWRP built-in root will work on the N7 2013.

    It will not. It will bootloop the device. There is a problem getting /data mounted under TWRP which breaks the approach outlined here.

  5. Reply Watcher July 28, 2013 at 5:11 am

    I have done these directions 10 times over and I still can’t get past fastboot flash recovery openrecovery-twrp-2.6.0.0-flo.img (and I even tryed renaming it to “recovery.img” to no avail). It always gives me an error and I can’t proceed from there. I’ve even been on the XDA Developers website and they can’t seem to figure out why.

    • Reply Watcher July 28, 2013 at 5:16 am

      However, I was first doing what was prompted of me by activating “adb reboot bootloader” first and then to do the steps you had listed above. If I do your steps first, all I get is “”.

      • Reply Watcher July 28, 2013 at 5:17 am

        …all I get is .

        • Watcher July 28, 2013 at 5:18 am

          It won’t seem to let me place text in arrow brackets. Anyway, the text is “waiting for device”.

Leave a reply

Human Verification: In order to verify that you are a human and not a spam bot, please enter the answer into the following box below based on the instructions contained in the graphic.