Tips & Tutorials

Root Nexus 7 2013 on Android 6.0 MRA58V Marshmallow with SuperSU 2.52

Here is how to root Nexus 7 2013 on Android 6.0 MRA58V Marshmallow update. This update has just arrived a couple of days later after another minor bug fix was released for this tablet. We don’t have any official list of changes in this build yet, but we have a working root tutorial for you all. The best part is, you don’t have to install a custom kernel just to gain root access on your tablet. Why would you think about rooting? Read: Benefits of rooting an Android device. We will be using a beta release of SuperSU 2.52 for rooting this tablet. You can now root Android 6.0 Marshmallow on Nexus 7 using the tutorial below.

As you continue reading below, we will guide you through all the steps of how to root Nexus 7 on Android 6.0 MRA58V Marshmallow software update with backup tips and other important points given below that you should keep in mind. Read our list of the essential root apps available! Again, be aware that this guide will not show you how you can install a custom recovery. Let’s continue with the tutorial below.

Nexus 7 2013 - Android 5.1.1


Disclaimer: All the custom ROMs and firmwares, official software updates, tools, mods or anything mentioned in the tutorial belong to their respective owners/developers. We ( or the developers are not to be held responsible if you damage or brick your device. We don’t have you on gun point to try out this tutorial 😉

Root Nexus 7 Android 6.0 MRA58V Details:

Android 6.0 Marshmallow is now available for the Nexus 5, Nexus 6 and Nexus 7 phones. These are the major changes in Preview 3 release of Android 6.0, as per Google:

This final Android 6.0 Marshmallow MRA58V build brings the whole feature list detailed previously at Google I/O as well as fixes the bugs found in last Developer Preview. The new Nexus system images have also received updates and have been refined to offer better testing capabilities without having an actual Nexus phone. Some major features include: Permissions UI, Doze, App Standby etc.

In case you want to update Nexus 7 to Android 6.0 MRA58V Marshmallow using the official OTA software update or with the official factory image, read the following tutorials:

Also, you might be interested in the following posts:

ASUS Nexus 7 USB Drivers

You will need to connect your Android tablet with the computer. For that, please make sure you have installed the Android 6.0 USB drivers for Samsung Nexus 7 properly. If not, you can download the latest official drivers from our Android USB Drivers section here:

Download Samsung Nexus 7 USB drivers!

Backup and Other Important Tips

Done with the USB drivers? Perfect. The tutorial is on the next page, but first, please take a look at the following tips and important points you need to take care of. These are important, as we don’t want anyone losing their personal data or apps:

Always backup your important data that you might need after you install a new custom ROM, an official software update or anything else. Make a backup for just in case, you never know when anything might go wrong. See below for some tips on how to backup data:

Samsung users can also back up data using Samsung KIES. If you backup data manually, you get more options what to choose from and it is very easy to move data across Android devices from different manufacturers, i.e moving Samsung Galaxy Note backup data to ASUS One X.

If you already have a custom recovery (ClockworkMod, TWRP etc.) installed on your tablet, we strongly recommend you to also backup using that as it creates a complete image of your existing tablet set up.

A few more optional tips that you should remember:

1. Having problems connecting your Android tablet to the computer? You need to enable USB debugging mode. See here: How to Enable USB Debugging — for Gingerbread, Ice Cream Sandwich and Marshmallow.

2. Make sure your Android device is charged up to 80-85% battery level. This might help you: How to Check Battery Percentage. Why? Because, if your tablet goes off suddenly while installing a custom ROM, flashing an official firmware update or installing mods etc. — your tablet might get bricked or go dead permanently. No one wants that, right?

4. Most of the tutorials and how-to guides on Team Android are for factory unlocked Android phones and tablets. We recommend NOT to try our guides if your tablet is locked to a carrier, unless we have specified the carrier name or device model.

If you find the above tips useful and they were helpful to you, please consider giving us a +1 or LIKE to thank us!

All set and ready? Good. You can now go to next page and root Nexus 7 on Android 6.0 MRA58V software version.

About the author

Haris Nadeem

He lives on everything Android; has countless devices, apps and games to play with everyday. Currently serving as the Chief Editor at Team Android.


  • Couldn’t get this to work. Made it to the last step, but whenever I reboot, I just get stuck in a bootloop. I tried both recoveries and still no luck. Anyone else experiencing problems?

      • jis, thank you very much. I flashed beta SU and the elemental kernal and Voila! I have root. This was the only way I could get root. I hope I don’t mess up too many things or burn my Nexus up with that Kernal, but I tried to remain conservative when choosing each option.

        • Let see to change to different kernel as the first level and modifying default kernel values as another level. I don’t think it’s wise to skip the first level to the next from the start.
          I was conservative too as much as to select only default values in Aroma installer, because I never use different kernel so far. I decided that I’ll start tampering with OC values etc. after a few weeks of use without any problems.

    • John, jis is right on the money. I’ve got my Nexus 7 rooted with the brand new build, MRA58V. When I used the above method I got stuck in a bootloop. Flashed MRA58U and Wugfresh could not see my bootloader as being unlocked. I stupidly updated my Nexus 7 and got the same build as before, but decided too dig deeper and followed jis’ advice to you. Good Luck!

  • I have MRA58K, which was a PITA to install given that I was rooted previously and didn’t want to wipe (I have TWRP and am unlocked). It’s working fine with ElementalX, but I would like to go to MRA58V and am thinking that the OTA will not work because I’m not stock. When I was on Lollipop I’d learned to do updates by extracting the boot.img and system.img from the developer’s site and just fastboot flashed them. This worked safely, but just required me to do a simple reroot which TWRP typically handled for me. Will I able to do the same procedure in Marshmallow? I’m doing a Nandroid backup right now, but would prefer to not get stuck mucking with this thing for hours and hours.

    • Sure, read the XDA post in my first post here. Just modify one line in the flash-all.bat script from “fastboot -w update” to “fastboot update” and your data rest intact after udating to mra58v. Then install the latest TWRP and from TWRP install ElementalX-N7-5.05 and BETA-SuperSU-v2.52.

      • I was able to successfully update with wiping. Thanks for writing back…

        For simplicity sake, I downloaded the MRA58V and unzipped it, as all that was needed was boot.img and system.img. In case someone else needs to do it, here’s the commands I used:

        fastboot flash system system.img
        fastboot flash boot boot.img
        fastboot format cache
        fastboot reboot

        I had to reroot afterwards…

  • Also having problems – bootloop time. Can get to recovery mode, but unable to actually boot with it just sitting at the spinning circles animation. Can’t see the device in windows explorer, though fastboot in a cmd does discover it. Already was updated to MRA58V before I started. Anyone any idea how to fix without a complete factory reset?

  • Same problems than most of folks here: got bootloop on my Nexus 7 and unable to do anything to fix it until i wipe the data/factory resest. Fortunately i made a backup.
    This beta of SuperSU 2.52 is the main cause of this bootloop. I stay on 2.46 ’til the problem is solved.

Leave a Comment