Tutorial: Root Shield Android TV 16GB (Marshmallow)


  • 4/18/2016 – Updated TWRP and SuperSU to latest versions
  • 2/26/2016 – Removed 500GB references because this tutorial doesn’t work for it.
  • 2/22/2016 – Initial Tutorial posted

Here we go.  Rooting the Shield Android TV (16GB SKU) running Android 6.0 (aka Marshmallow).  This should work on all builds of Marshmallow moving forward.  Looking for the 500GB SKU tutorial?  Click here.

NOTE: TWRP doesn’t currently work on 4k displays!  Use a 1080p display to complete this tutorial.


Note 1: You will need to be able to see your PC AND the Shield TV’s HDMI out in order to perform this.  I used one monitor with two inputs and flipped back and forth as needed.

Note 2: Unlocking the bootloader will ERASE EVERYTHING internally (not on your external SD card if present).  Make sure you have everything saved off and backed up.  You’ll have to resign into Google – so if you use two-step authentication, be sure to have your Google Authenticator app ready.


  1. Install Minimal ADB and Fastboot if you do not already have it installed.
  2. Ensure the Shield Family drivers are extracted somewhere on your system and you know where they are.
  3. Make sure you know how to get to Device Manager on your PC.
  4. Extract TWRP Recovery image. Put this in your Minimal ADB and Fastboot folder (usually c:program files(x86)Minimal ADB and Fastboot).
  5. Copy supersubeta.zip into your Minimal ADB and Fastboot folderNote: If you’ve already created Adopted Storage, you’ll need to put SuperSuBeta.zip on a fresh SD card that hasn’t been adopted.
  6. Plug your Shield TV into the PC with USB cable.
  7. Plug your mouse into a USB port.
  8. Confirm drivers for ADB are installed:
    1. On your PC, go to Device Manager.  Find the yellow (!) ADB device.  If none exist, you probably already have drivers.  Skip to step 9.
    2. Right click the device and select Update Driver.
    3. When offered, browse your computer for the driver and point it to the Shield Family Drivers folder you extracted in Preparation Step 2 above.
    4. When finished with the driver install, the (!) yellow device should be gone.
  9. Enable Developer mode on Shield TV
    1. On the Shield TV, go to Settings->About->Build (tap 7 times on the BUILD to unlock developer mode) – you have to back out of Settings and go back in before Developer will appear.
  10. Enable USB Debugging on Shield TV
    1. Settings -> Developer -> Debugging; set to On
    2. A popup should appear asking for this PC’s authorization.  Check the Don’t ask again for this PC box and select Allow.  If it doesn’t show up now, it will later.

Root Procedure

  1. Reboot into Bootloader on Shield
    1. Launch Minimal ADB and Fastboot from the Start Menu or icon on the PC.  This puts you in a black DOS box.
    2. Type “adb devices” and make sure your Shield TV appears.  Note: If you didn’t have a popup on your Shield TV screen in Step 10.2 above, it probably will appear now.  You’ll have to authorize the PC before it will show up under adb devices.
    3. Once you see your Shield TV when you run “adb devices” you’re ready to proceed.
    4. Type “adb reboot bootloader” and hit enter.  The Shield TV should reboot into the bootloader screen.
  2. Verify Fastboot Drivers are installed:
    1. On your PC, go to Device Manager.
    2. See if a yellow (!) exists that mentions FASTBOOT.  If not, continue to Step 3.
    3. Right click the device and select Update Driver.
    4. When offered, browse your computer for the driver and point it to the Shield Family Drivers folder you extracted in Preparation Step 2 above.
    5. When finished with the driver install, the (!) yellow device should be gone.
    6. Type “fastboot devices” and make sure your Shield TV is visible.
  3. Unlock Bootloader
    1. Type in “fastboot oem unlock” and hit enter.
    2. You will see a PLEASE WAIT … appear on the Shield TV screen.  This will take several minutes.  Do not be impatient!  Let it finish.
  4. Reboot to Shield TV Interface
    1. Once the bootloader is unlocked, reboot the Shield TV and return to the Shield TV main interface.
  5. Repeat Preparation Steps 9 and 10 above to re-enable Developer/USB Debugging.  Note: at some point you will have to re-authorize your PC again; if an ADB command fails, be sure to look at your Shield TV screen for the authorization prompt.
  6. Push BETA-SuperSU-v2.71-20160331103524.zip to the Shield
    1. In the Minimal ADB and Fastboot DOS window, type: “adb push BETA-SuperSU-v2.71-20160331103524.zip /sdcard/”
    2. You should see text indicating the file was copied over correctly.Note: If you’ve already created Adopted Storage, you’ll need to put SuperSuBeta.zip on a fresh SD card that hasn’t been adopted.  Watch the video to see how to do this.
  7. Reboot to Bootloader
    1. Type “adb reboot bootloader” and hit enter. The Shield TV should reboot into the bootloader screen.
  8. Fastboot/Install  TWRP
    1. Type “fastboot devices” and make sure your Shield TV is visible.
    2. If your Shield TV is listed, type  “fastboot boot twrp-20160222-UNOFFICIAL-foster.img”
    3. After 15 seconds or so, you should see the TWRP Recovery screen
    4. If you are asked if you want to preserve Read Only on the system, accept the defaults.
  9. Ensure your mouse is plugged in and working.
  10. Install SuperSU
    1. Select INSTALL.
    2. Navigate and select BETA-SuperSU-v2.71-20160331103524.zip (if you are using a microSD card, click SELECT STORAGE and choose microSD – see the video for more details)
    3. Follow the instructions to Swipe to Flash
    4. SuperSU will install.
  11. Reboot to System
    1. Select SYSTEM REBOOT from the TWRP screen
    2. Answer DO NOT INSTALL if asked to install SuperSU
  12. Run SuperSU application and apply any updates
    1. Once you are back up and running (first boot can take a little longer and possibly bootloop once) find the SuperSU app installed on the Shield TV.  Run it and perform any upgrades (select “Use Normal” if asked).
  13. You are now rooted!

Video Version

If Something Goes Wrong

First, don’t panic.  It is pretty hard to permanently “brick” the Shield Android TV just by trying to root it.

No matter what may go wrong, flashing a stock image should put you back in working order.

This “fix” has similar requirements and pre-requisites as rooting itself.  You must be able to boot the Shield TV into Fastboot, it must be plugged into the computer and you must be able to see it with the command “fastboot devices”.  See above if you need to remedy this.

Obviously if your Shield Android TV is stuck in an infinite boot – you cannot reboot to Fastboot from your PC.  I have to do it the “hardware way”.  This is a tricky step and requires pretty good timing.  Do not worry if it doesn’t seem to work the first couple of times you try it.

Accessing Bootloader via Hardware

Restore Shield Android TV to Stock


  • NVidia Stock Shield TV Image (16GB image)
  • Shield TV in Fastboot, plugged into PC
  • Fastboot drivers installed on PC
  • Shield TV shows up in “fastboot devices” under Minimal ADB and Fastboot DOS box.
  • The Bootloader must be unlocked (but it should already be unlocked from your root attempt).

Restoration Procedure

  1. Extract the NVidia Stock Shield TV Image v1.3 (again, make sure you have the right one for your unit) into your Minimal ADB and Flashboot folder.  It shouldn’t overwrite anything; if it does, consider renaming what it was going to overwrite – just to be safe.
  2. Verify the Shield Android TV is in Fastboot by typing “fastboot devices” and hitting enter.  If you see the Shield TV show up, continue.
  3. Type “flash-all.bat” and hit enter.  Note: This erases EVERYTHING – returning the Shield Android TV to stock – like it just came out of the box.
  4. Wait and watch.  THIS CAN TAKE A LONG TIME – as in over an hour for the 500GB version of Shield Android TV.
  5. Once complete, reboot the Shield Android TV.  To select items from the Fastboot menu, TAP the power button to select … HOLD AND RELEASE (for two seconds) to select.
  6. You should now be back up and running.
Note: Some of this content was originally derived in part from XDA’s threads here and here.  

105 Responses to Tutorial: Root Shield Android TV 16GB (Marshmallow)

  1. Do I have to unlock boot loader again. I try to install twrp and it stays on for couple of mins then the it reboots

  2. Yantis Eddie says:

    Hi, I rooted my Shield TV Pro before with your old tutorial and it worked fine until I got the Marshmallow update. When I try to do it now, I can flash the new TWRP, but I can’t access any storage (both internal and MicroSD say they have 0 MB) and it reboots after a little while. (Could be five minutes, could be a few seconds.

    • administrator says:

      Updating from an older OS (5.1) to a newer one (6.0) should probably be done with a stock recovery and fresh OTA upgrade. Sometimes you can get away with it – but most of the time, you’ll see issues like this. Backup your stuff, restore to stock – OTA to the latest and I bet your problems go away.

  3. paul canales says:

    If I have used Adoptive Storage on mine microSD card or USB device is there a way to return it back to normal to used again for ordinary file storage with windows?

  4. Ryan Gee says:

    Hello, first and foremost thank you very much for the tutorial. I have a brand new Shield Android TV Pro (500 GB) which has been OTA updated to version 6.0. I’m attempting to root but I am stuck on section 10 (Install SuperSU) of the root procedure. When I first boot into TWRP, I do not see any option to “Swipe to allow modifications”, as is shown in your video. I am simply taken to the main selection page with the options to “Install”, “Backup”, “Restore” etc. Whenever I click on “Install” and then click to select my micro SD Card drive under “Select Storage”, it will not let me. No matter what I do, I cannot select my micro SD Card. Also, I tried this with a different micro SD card but this produced the same results. Note that my Shield Android TV is able to detect my micro SD card within the OS. Also, neither Micro SD card was set up as “adopted” storage. They are both removable storage only and formatted as FAT32. Any ideas as to what I may be doing wrong? Thank you in advance for any help and guidance.

    • administrator says:

      Did you go to MOUNT and make sure the microSD card was actually mounted? It may not have been. Without a mount, you cannot select it.

      • Ryan Gee says:

        Thank you. Per your feedback, I’ve now tried to mount the micro SD card via the ‘Mount’ option under the TWRP menu. Unfortunately this option does not allow me to mount anything. Under the ‘Select Partitions to Mount’ window, no matter which option I click on (System, Cache, Data, Micro SDcard, USB-OTG), nothing is selectable. I’ve even tried to click ‘Only mount system read-only’ and ‘Disable MTP’ (which I am allowed to click) but neither option allows to me select ‘Micro SDcard’. Is there perhaps another option or prerequisite that I can to pursue which will allow me to mount the micro SD card?

        • administrator says:

          Try reformatting the sd card into a different file system

          • Ryan Gee says:

            Just providing feedback. Utilizing the newly created ‘Root Shield Android TV 500GB’ guide via your site, I was able to fully root my device. The issue, as far as I can tell, turned out to the be the TWRP version after all. The TWRP version listed under the 500GB guide, (TWRP (Shield TV; Android 6.0; Unofficial)) worked without fail for my Shield Android TV Pro, as I am now rooted. Also, per your previous recommendation, I formatted my SD card to exFAT prior to using the different TWRP version. The reason why I rooted my device was so that I could use the Sixaxis Controller program with my DS3 controllers, but I just found out that the current version (0.8.3) does not work with 6.0. Back to using my USB cables for now. My understanding though, is that the developer is working on an update for use with 6.0. Thanks again for your help and guidance. /thumbsup

  5. Tried Rooting Nvidia Shield TV 2.1 with below steps:

    1. Downloaded and flashed NVIDIA SHIELD ANDROID TV Pro Developer Only OS 2.1 ( from https://developer.nvidia.com/shield-developer-os-images )

    2. Got OTA update for Marchmallow. and the TV is updated to Marshmallow.

    3. Followed the step in this page, it failed in step 10 Install SuperSU
    with error

    Not able to mount /system /data etc.

    NOTE: I am not having adaptive storage.
    Let me know what additional steps I need in order to get rid of Mount issue.

    • administrator says:

      Hi, sorry – I don’t support developer images; mostly because every time I’ve tried one? I’ve had issues. Perhaps someone on the forums or in the chat can help?

  6. I have used each step you have provided and I dos unlock the bootloader
    But when ever I try to root using twrp while using sd card with supersu error message appear withe E//:unmount issue???
    Could you help solving the matter please

  7. Kevin None says:

    OK, did this a month or so ago when still 5.1 using the same PC. My computer has updated a few times since, so therein may lie my problem. Now, all goes as it did, up to the point of Verify Fastboot Drivers are installed:

    On your PC, go to Device Manager.
    See if a yellow (!) exists that mentions FASTBOOT. If not, continue to Step 3.
    Right click the device and select Update Driver.
    When offered, browse your computer for the driver and point it to the Shield Family Drivers folder you extracted in Preparation Step 2 above.
    When finished with the driver install, the (!) yellow device should be gone.

    I see the yellow indicator, it says unknown device, click and it is the Shield TV, go to update drivers, goes right to the file on my desktop, as it should, then says no such file, although it’s right there and are good intact files….!

    Windows 7 PC and has had several Java updates, as well as general Windows updates(Thank you Microsoft..)in the past month.

    Any ideas what I need to do now?

    • administrator says:

      Maybe we can get a remote session going …drop on the chat

    • Kevin None says:

      I’m all good now. I uninstalled then reinstalled Minimal ADB. Went right through then. One note, and I forgot to mention this before – to reboot on MY shield when called for in this process, I can’t use an USB mouse. Instead I have to click down using the Shield touch pad on the case, then press and hold on “reboot” for maybe 20 seconds.
      This update did break a few apps that I liked. One was Advanced Task killer. worked fine in 5.1, does nothing now. Another is Purify, an app from Kingroot. It really sped things up in 5.1, but won’t work for Marshmallow 6.0. Oh well, the extra memory space is worth it and then some.
      Thanks again!

  8. Hey there, thanks for your excellent tutorial, I previously followed your guide to rooting 2.1 which worked great. To upgrade I restored to stock 2.1, upgraded to 3 and then rooted which all worked flawlessly. When It came to adaptive storage I tested using a 64GB Micro USB class 10, I found when I formatted the SD card for internal storage (Adaptive) it took forever (10-15 min) to format and then once up and running things where quite sluggish. I tested the speed of the micro SD by coping a large file using FTP which which was except able yet the system is sluggish. My testing is using Kodi Javis with a large video library which seems to have problems itself running on Shield. Have now moved back to 16GB internal storage.

    The question do you know if anyone else has had performance issues since moving to adaptive storage, should it take that long to format the external Micro SD card for external storage?

    Current in the process of putting older version of Kodi back on (just stock 16GB) and then testing, else may restore stock and start again.

  9. Brand new shield tv with mm on it.Unlocked bootloader and rooted.Twrp pushed as wel.Reboots fine but I cannot reboot into twrp.I tried adp and sideload installed. Itrestarts in the little android with a red exclamation mark on it Any any idea? I’d like to make nandroid. It seems that every time I restart after installing the twrp it reverts to stock recovery. Also su binary update fails.

  10. Also usb memory stick not visible in twrp.

  11. I just installed a 64 GB microSD in the system and format it as internal storage to increase room. After moving the files over everything fine but right now I can only see the native storage 16GB in TWRP and vice-versa I can only see the 64GB micro SD when Android is up&running. I cannot install any zip. It seems that storage management is still a mess at this stage in marshmallow.

  12. genasium says:

    Is it possible to unlock the full android playstore with a rooted shield tv?

  13. Andy Watts says:

    Hi. in upgraded to mm 5.0 but want to roll back to 2.1 as within 5.0 I’m unable to fully utilise my external USB drive. is this just a case of following the return to stock instructions flashing the 2.1 file you have in your link? cheers

    • administrator says:

      There is no successful path back to 2.1 that I know of. 🙁

      • Robert Hackbarth says:

        – L O L L I L O L L I L O L L I P O P –

        ..today I successfully downgraded my SATV
        so here my “SUCCESSFUL PATH BACK TO 2.1”..

        first flash the 2.1 developer firmware.
        disconnect internet, reboot and connect your controller

        and yes, now please W A I T !!!

        your device hangs up for some minutes (16gb-version).

        so don´t punch or shake your cake-box!

        just check if the letters on controller setup screen
        continuing animating then the SATV is ready
        to begin the initial setup procedure.

        …choose your language.

        next you will be asked for internet settings
        but first lets kick some ass using adb:

        adb root
        adb shell pm disable com.nvidia.ota

        :: ..BUSTED! 😛

        reconnect SATV to internet and setup your google account.


        update screen one time nags again 😮
        but you can now click to next step and ´~, :-

        8- B A N G !!

        welcome back to

        LOLLIPOP TV!

  14. Patka says:

    Hi! I can’t root my shield tv because in bootloader is still in infinity loop. I use this method, but i can’t finish.
    (Sorry my bad english)

  15. Hi,

    I noticed it says it has to see my PC and to use two monitors. Will a laptop not work instead?

  16. Alistair Hill says:

    Hi, I am having issues with the rooting process. Im a bit green so bear with me!
    I managed to get to the twrp menu after loading from the SD card. When I flash the box it loads/does its processes but doesn’t let me ‘swipe’ with my mouse or choose not to install superSU. It automatically reboots the device and superSU is nowhere to be seen.

    Any ideas?


  17. soso goga says:

    hello admin I want rooter my machine box nvidia shiel TV 16 go but I lack the style dir TWRP files * or I can find it I thank you reside in France is what you can not give us a clear translation in French thank you sofien! !!

  18. ryan stmarie says:

    Hello. Followed your guide when I had 2.1, worked like a charm on my 16gb Nvidia Shield TV. Everything went according to plan and my Shield still connected to windows fine (showing it’s internal file system). 3.0 came and now I could no longer see my android file system at all, which had a 1TB usb 3.0 drive added with adoptive storage, in windows when the shield was connected to my pc. I did a factory reset because things weren’t working (and I didn’t realize it had updated). I completed this guide again, and I had no errors that I saw, and everything seemed to go fine. SuperSU loads, Installed the file manager. Connected it to my computer and everything seemed fine, my internal storage was showing up. Then I added a 1TB usb3.0 drive through adoptive storage. Now, windows won’t show the contents of the android FS again, which is the whole reason I factory reset in the first place. Any clue on to what my issue could be here?

    • administrator says:

      Your PC will only “see” one location on your device; wherever “data” is. Have you watched my video? Adoptive Storage Explained With Index Cards? I think it would help you a LOT!


      • ryan stmarie says:

        Yeah, the problem was that I wasn’t able to access any files at all from the PC. I figured out my problem by doing research on some other devices and discovered that, at least for me, the problem was this.

        It takes the Nvidia Shield more then just a couple moments to show it’s contents again over a USB connection to PC. I shut off the shield, unplugged it from the PC, let it boot and waited about 10 minutes. When I plugged it back into the PC, everything was as it should be, and I could see the contents of the data folder again. Previously it was showing nothing at all on the Nvidia Shield TV, and no files would transfer to it, kicking back a permissions error.

        Thanks for your reply, I hope my experience can save someone from the imaginary failure that I thought I had on my hands. Patience was my lesson here.

        • ryan stmarie says:

          And I want to say, I think that there’s a misconception among many forums I have visited that people weren’t having success because they didn’t understand adoptive storage, when in fact, I think their problem may have been similar to mine, they just lacked the verbal acumen and vocabulary to properly explain what their problem is.

  19. Hi,

    I did follow all your steps on a new Shield 16Go and I even went a bit further by installing a full android on it (Stock Restyle from XDA developers) but now I’m facing quite some issues :
    – I can’t access anay longer android parameters. I’m stuck with Nova Launcher (preinstalled on Stock Restyle). I can’t even access Nova Launcher parameters. Only way to even access the icon is through the Play Store which bring me to the home screen where I can’t do anything.
    – I then decided to come back to the original firmware which I downloaded but your method for hard boot seems not to be working. I’ve tried about 30 times starting to count as you did on the tuto…

    I know that it seems that I’m a deep sh…. but your help would be much appreciated as I’m based in France there is almost nobody good enough technically speaking on this device to help me.

    => At the end what I’m looking for is a full play store on the Shield TV. Can you help top do that ? Hoping you will answer favourably my help request.
    Kind regards


    • administrator says:

      I’m sorry .. I cannot support “custom roms” on Shield devices. There are just too many variables.

      It sounds like the Shield TV may not be the right device for you. There are other Android based set top boxes that are “pure Android” (not Android TV) that have “Real Play Store” (i.e. not Android TV’s store).

      You will need to return to stock. Timing is tricky, but the hardware method should get you back to bootloader. You could try ADB – since the device boots up. ADB REBOOT BOOTLOADER

  20. valefoods says:

    Hi, anyway to get TWRP to work on 4k panels? Both my tvs and my monitor are 4k, afraid to start the rooting in case I can’t complete it. Thanks

  21. Topciu Topit says:

    Does anyone has a step by step tutorial on rooting shield using a mac?
    I have 2 macbooks and a mac mini. No windows PC.


  22. Hi my nvidia shield tv 16gb is in a bootloop can anyone help me

  23. […] rooted my android tv and dont know what to do.<link>. what kind of stable roms can i install?And is there any way to play games with a ps3 […]

  24. […] rooted my android tv and dont know what to do.<link>. what kind of stable roms can i install?And is there any way to play games with a ps3 […]

  25. J 2012 says:

    Hey. I think I may have soft bricked my shield, not sure. When I got the shield it upgraded to 3.0 fresh out of the box, I then decided to unlock the bootloader, then tried to root and install the 3.1 ota update with root, somewhere in the middle of that last step I messed up somewhere so then I decided to flash back to stock. Little did I know you can’t flash anything below 3.0 once you upgrade to it. I mistakingly flashed 2.1 and now I get a continuous Nvidia logo reboot with no way to seemingly get into the fastboot screen. Is there anywhere to get to it so I can flash the stock 3.0 or is my shield done for?

  26. J 2012 says:

    Forgot to mention it’s the 16gb version

  27. Wich TWRP I need to use? the one in pre-requisites or the last version on the twrp website?

  28. What do I do if there are graphical issues with my ppsspp and Mupen emulators? Some games won’t show the background or parts of characters? They seemed to work fine before the Marshmallow updates.
    Also, is there a control mapper for the Sheild TV like on the tablet for the shield controller? If not, will there be?

  29. Royd Baerga says:

    I did all the process and it was working fine until a few days. The unit was crashing apps and rebooting few times. I just flashed it back to stock and is back to normal. No idea why this was happening. Other than that great tutorial, great video but I will wait a little longer for bug fixed on Marshmallow. Good luck all 🙂

  30. Royd Baerga says:

    Ok the problem I was having with crashing and reboot was SD Card. Got now a new one from ScanDisk and is working great. I also tried with a 128GB USB stick drive and work good too but is was getting a little too hot to the touch so I’m staying with the sdcard for now.

  31. Kodi Joker says:

    Ok, I am making a mistake somewhere but not sure where.

    This whole part:

    Install Minimal ADB and Fastboot if you do not already have it installed.
    Ensure the Shield Family drivers are extracted somewhere on your system and you know where they are.
    Make sure you know how to get to Device Manager on your PC.
    Extract TWRP Recovery image. Put this in your Minimal ADB and Fastboot folder (usually c:program files(x86)Minimal ADB and Fastboot).
    Copy supersubeta.zip into your Minimal ADB and Fastboot folderNote: If you’ve already created Adopted Storage, you’ll need to put SuperSuBeta.zip on a fresh SD card that hasn’t been adopted.
    Plug your Shield TV into the PC with USB cable.
    Plug your mouse into a USB port.
    Confirm drivers for ADB are installed:
    On your PC, go to Device Manager. Find the yellow (!) ADB device. If none exist, you probably already have drivers. Skip to step 9.
    Right click the device and select Update Driver.
    When offered, browse your computer for the driver and point it to the Shield Family Drivers folder you extracted in Preparation Step 2 above.
    When finished with the driver install, the (!) yellow device should be gone.

    Does not work for me, I downloaded everything and all of it is in easily accessible folders on my desktop. Do I need to put some of this on the SD card before windows will recognize the Shield when I plug in the USB?

    I got into dev mode and enabled the debugging, plug the shield into my computer and when I try to update the driver from the Shield Family Drivers folder on my computer it says the drivers are not compatible with this device and will not let me update.

    “Copy supersubeta.zip into your Minimal ADB and Fastboot folderNote: If you’ve already created Adopted Storage, you’ll need to put SuperSuBeta.zip on a fresh SD card that hasn’t been adopted.” – this is the part that has me confused, Do I need SuperSuBeta and Minimal ADB and Fastboot on both my PC and the SD card?

    Right now I have everything on my PC and the SD card itself is empty.

    Sorry for the long post…

  32. Kodi Joker says:

    Ok, I am going to do this in 2 posts to make it easier to read.

    I did what the link said and still no go, I don’t see and ADB device in device manager and the unknown USB device I see still won’t let me install/update the driver for it. I have a laptop also and was going to try to connect that to the shield tonight to see if that works. I have never had a phone or anything attached to it so it should be “clean” as far as that goes.

    If the laptop doesn’t work I will message on here again and maybe setup a date/time for live chat or just shoot you my phone # and we can txt or call.

  33. Kodi Joker says:

    Now onto the other issue.

    I made the mistake of updating to 3.2 last night which did a few things.

    1 – update says you can connect to the Shield from a PC over the network….too bad Windows 10 won’t recognize ANY devices attached to my network except my printer and there seems to be no fix for it.

    2 – that update got rid of almost every useful program. No more emulators, ES File Explorer (browser access), Sideload Launcher or any other file manager that I can find on Google Play Store.

    So, now I almost NEED to root this thing so that I can do what I want to on it. Unless you have a different workaround to install the emulators/sideload launcher etc…

    Thanks again!

    • administrator says:

      I’ve noticed this too. Some apps are … MISSING since the update. X-Plore for one. You can install everything from the Web though.

      You can grab everything from apkmirror or similar.

      We can get you through the Win 10 thing. Check the new FAQ. There are some things to try in there.

  34. AHAC EL says:

    Just did the setup for my new Nvidia shield tv now, updated me to the 3.2. Is there a root for this version? I’m a rooter, what are the must have apps for shield tv? Root explorer? Aptoide? Etc. By the way your website rocks. Thanks admin

    • administrator says:

      Mouse Toggle and full write access to storage via Xplore is pretty much all I use root for these days.

      This root tutorial should work fine on 3.2

      Appreciate the compliment!

  35. Atilano Reza says:

    Hi Shane

    I finally figured out whyI was I was getting a black screen when trying to reroot my monitor is higher resolution and I read that there was a bug that i needed to use a 1080p screen.

  36. King Skemez says:

    when i go to reboot i lose connection, usb connection is spotty at best even tho when i do get it to connect initially and upgrade the drivers it says theyre up to date.

    • administrator says:

      Despite other comments, my experience has been – it’s the cable. If it isn’t the cable, it’s the port. If it isn’t the port, it is a USB driver conflict. If it isn’t a conflict? It is probably the Shield TV 🙁

  37. GoogleUser14 says:

    Hey administrator

    Your guide has worked perfect up until this step:

    “Push BETA-SuperSU-v2.71-20160331103524.zip to the Shield
    In the Minimal ADB and Fastboot DOS window, type: “adb push BETA-SuperSU-v2.71-20160331103524.zip /sdcard/”
    You should see text indicating the file was copied over correctly.Note: If you’ve already created Adopted Storage, you’ll need to put SuperSuBeta.zip on a fresh SD card that hasn’t been adopted. Watch the video to see how to do this.”

    I and others have an issue where the microSD card is stuck inside the shield tv. This is due to a faulty mechanism.

    Can you details steps on how to push supersu via a usb drive and not via the microSD.
    IE the command I would have to type in adb push BETA-SuperSU-v2.71-20160331103524.zip /sdcard/ but for usb drive.

    I also have a usb to microsd adapter, would a second microsd work in the usb.

    I am stuck, PLEASE HELP

    Much appreciated

  38. thank you sir, i have rooted according to your tutorial! Everything is explained well
    I had a problem when adb wasnt pushing SU file to sdcard. I had to manually remove sdcard, attach to a computer and copy it myself
    Everythin else is crystal clear!!!

  39. Hello, I have watched your videos and read and attempted to execute your procedure but am at a stopping point. In the written procedure all is going according to plan until step 8.2 At the execution point of 8.1 My shield displays the NVIDIA logo and then the screen goes blank. No twrp/team win. Have waited patiently….Have been executing procedure with laptop connected to shield. Shield displayed on HDTV via HDMI. At 8.2 with no response an added observation is that my TV does not sense an input and declares it on screen. The shield power light is still lit. Cannot “see” the shield on device manager via win10pro or fastboot devices on adb. Further observations, notes…I was on the latest 3.xx shield build. I am using an external HD as internal storage and an un-formated SD card, usb mouse (plugged into the shield) with the latest files that are on the top of this page. From studying the video, reading the procedure, reading everybody’s posts, I do note that the files you used in the video were/are older than what is posted at the top of this page. I am guessing you were on android 5.xxx and not 6.0 as I am now? I manage to get a tablet build#MRA58K.324774_793.8284 Full Android 1.5, Kernal 3.10.67+ builbrain@mobile-u64-1078 #1 Mon Oct 24 PDT 2016 loaded and it is promising but without root or twrp it is pretty dull to say the least. I am thinking of restoring the shield to it’s original build and starting over. Any hints or insight or just laughter would be greatly appreciated. Thank you very much for taking the time to put this page together I know how much work must have been involved and I realize that as NVIDIA pushes updates they surely will skew tutorials like this one. Thanks again. doc@efialchemy.com

  40. y2korn says:

    Done it. Unfortunately I had to search the web for a few things. I used this for TWRP: “Fastboot flash recovery TWRP-20160222-UNOFFICIAL-foster.img”. Also in the SuperSU push command I couldn’t see the “.” at “2.71” and also the space in front of “/sdcard/”. Anyway, thanks again for the tutorial. You can delete my comm’s so it doesn’t look like spam:)

  41. Hi guys, i accidentally upgrade to version 7.0 and lost my previous 6.0 root; do i need to wait for a 7.0 root tutorial? 🙁

  42. failed(command write failed) (no error) this is message i got when i tried to fastboot twrp image? why did this happen can you explain what i did wrong

  43. i tried to do the nougat root,but when i tried to adb the recovery image it said no such file in directory. and it is the directory.any help

    • administrator says:

      Do a DIR and hit enter from Minimal ADB box. Look for your TWRP file.

      Most people try and rename it and end up with double extensions. So your file is probably named twrpxxxxxxx.img.img which is why when you try to flash with twrpxxxxxx.img it doesn’t work.

  44. Piotr Paweł says:

    Hello. I just bought Nvidia shield tv pro 2017. and it has automatically updated to Android 6.1. And now the question is whether this manual will work on this version of android 6.1?

Leave a Reply