1. Are you ready for the Galaxy S20? Here is everything we know so far!

Nexus 7 2013 (wifi) Manual root guide - Mac!

Discussion in 'Android Devices' started by ajdroidx, Dec 17, 2013.

  1. ajdroidx

    ajdroidx Android Expert
    Thread Starter

    Okay, all. Here is my first guide!

    Disclaimer: I am NOT responsible for damaging your device(s) computers, wasted time, etc, should something go wrong.

    Also this guide assumes you have ADB set up and are comfortable using terminal, navigating to directories etc.

    This is NOT a script or batch file.


    How to manually root your Nexus 7 2013 wifi edition. On a mac.

    I am not responsible for breaking your device. Proceed at your own risk. You must have ADB set up and running. This guide does not go through driver or ADB set up. Other guides out there will walk you through this.

    Drivers should not be needed on your mac, once again however, make sure ADB is set up. I use Mountain Lion. I am assuming you know how to navigate folders and such using your Macs terminal console.

    Step one, Make sure you really want to do the. You could break your device, etc.

    Step two. Prep your device to unlock its boot loader. This will erase your whole device! On your device go to settings -> about device -> build number, and tap on it about 6 times to make you a developer. If you have already done this, nice!

    Once you are a "developer" go back into settings, and you should see { } Developer options -> USB debugging and check that, and press "okay" to the warning.

    Step 3
    Go ahead and go home, pull out your USB cable, and plug the puppy into your mac. Load up terminal on your mac and navigate to the android folder that contains ADB fast boot and other files.

    When you have terminal in the android directory, make sure ADB can see your device. Issue the command

    ./adb devices

    On your device, a dialog will pop up asking if you want to allow the communication, It will also offer a check box to remember your computer. Make sure it IS checked!

    Press okay then on your terminal console, you should get a string of numbers. If you see this, you should be in! BUT, make sure the device is "online" if it gives you a string of numbers and says "offline" check your device and make sure USB debugging is enabled and you allowed the connection to your mac

    If not, unplug everything, reboot if need to and try again. If the numbers do not show up after issuing

    ./adb devices

    that is a dot/adb devices.

    Probably stop right here.

    If you do get ADB to see your device and you get the string of numbers, proceed. If you do not feel comfortable, stop :)

    Step 4
    Okay, now you got a string of numbers, and an "online" message it is time for the fun to start. issue the following command:

    ./adb reboot bootloader

    After a few moments you will see Andy on his back, and "start" and some other info, look for lock state near the bottom and it will likely say locked.

    You ready for this? Issue the following command in terminal:

    ./fastboot oem unlock

    The device will give you a warning. Use the volume rocker to pick the one to unlock, If you want to back out, just say no and the device should reboot. If you do, a few commands will appear in terminal, wait for the device to reboot and when you get to the set up screen, go ahead and unplug your device and start your set up.

    Go ahead and set your device up to taste, enable USB debugging by tapping the build number again you did previously.

    If you don't want root or a custom recovery, you can stop here and not even enable usb debugging.

    If you want custom recovery, go to part two. Its about to get a bit more fun.

    This guide is written for Mac Mountain Lion users!

    Part Two: the custom recovery.
    I use TWRP (Team Win Recovery Pro) but you can use CWM should you chose. To flash the custom recovery you need the image. Depending on your device model, you will need to do some digging, in this case, just use google, but for this, we will use what I used:

    Techerrata Downloads - Browsing flo and download the latest image, to which ever one you like. When the image downloads, copy it over to your android folder where ADB lives and just drop it there (the main /android folder). Also copy the name of the file, I usually just highlight and copy while the file is downloading, but that is just me. Just make sure you get the name right for flashing it.

    Okay, now that the new recovery is downloaded from the web and moved over to the main android folder, its time to flash.

    THIS WILL OVERWRITE your current stock recovery!

    Once again, make sure USB debugging is on, terminal is pointed to your android directory and can see your device:

    ./adb devices

    Once you get a string of number and the device is online its time to get a new recovery:

    ./adb reboot bootloader

    Once you are in boot loader mode (which should now give you an "unlocked" device state you should be ready to go. Once again if you feel uncomfortable doing this, just press the power button on your device to start and your device will reboot.

    Issue the following command in terminal:

    ./fastboot flash recovery RecoveryFileName.img

    if all goes well terminal will read out a couple things, sending recovery okay writing 'recovery' then finished. You are done! If you don't see this happy message in terminal, then stop :)

    If you do see the happy message, reboot your device.

    After your device reboots, it is time to check out recovery. We could have probably just done this by selecting 'recovery mode' while you are still in the boot loader, but I like to reboot personally then go into recovery. Could be more of an OCD thing for me, :p

    Anyway, if you opt to just go into recovery after flashing it from the boot loader screen, you should be greeted with the TWRP screen (or CWM if you used that) if not, if there is nothing there, or if the stock recovery is still there, something ran amuck. You can reboot your device and we can figure out what went wrong later, sorry to leave you hanging here, but the long and short of it is, if you still have stock recovery, you are still good, if you got a black screen and a reboot or two don't work, you can reflash the recovery if ADB sees the device.

    Okay, all is good and you got TWRP installed, you probably want root.

    Part 3, Rooting.

    I use chainfires SuperSU. I grab the latest zip from his XDA thread, once again, just google his XDA thread, I will not link to it because of it being another forum. Make sure you get the CWM / TWRP flash able zip file and NOT from the playstore!

    I do things a little backwards I suppose, I download the file to my device from my device using chrome, the zip file will show up in my downloads folder on my device. You may need to click other to make sure you actually got it downloaded.

    Once you have the file downloaded, as of this guide SuperSU is v1.85 go ahead and reboot into recovery.

    I don't dig button mashing, so I put ADB to work for me. Just plug your device in, make sure ADB sees it,

    ./adb devices

    make sure it is online and proceed.

    ./adb reboot recovery

    You should see the TWRP welcome screen, from here you can go to install -> navigate to your downloads folder and locate your SuperSU zip select it then flash it. It should not take too long, After words, just go into reboot and reboot system.

    After it powers up look in your app drawer and you should see the SuperSu icon. You should have root!

    By now, I am sure you know how to make a nandroid backup, and know what to do from here

    WoohooGuy likes this.

    1. Download the Forums for Android™ app!



Nexus 7 (2013) Forum

The Nexus 7 (2013) release date was July 2013. Features and Specs include a 7.0" inch screen, 5MP camera, 2GB RAM, Snapdragon S4 Pro processor, and 3950mAh battery.

July 2013
Release Date

Share This Page