Tutorial: Root Shield Tablet K1 (Marshmallow)

This root procedure works on all known Marshmallow versions on the Shield Tablet K1.  Click the titles to expand each section in turn.

[eliteaccordion][elitetoggle title=”Step 1: Pre-Requisites and Warnings”]

Download the following items:

Data Destruction Notice

Unlocking the bootloader will ERASE EVERYTHING internally (not on your external SD card if present; adopted storage users may want to make a backup of their SD card contents).  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.

The process of rooting will not destroy any data.

[/elitetoggle][/eliteaccordion]

[eliteaccordion][elitetoggle title=”Step 2: Preparation”]

  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 from the ZIP file (and do yourself a favor and rename it to something easy like twrprecovery.img). Put this in your Minimal ADB and Fastboot folder (usually c:\program files(x86)\Minimal ADB and Fastboot).
  5. Copy supersu.zip (it may be named differently; you downloaded it above) into your Minimal ADB and Fastboot folder. Do not extract it.
  6. Plug your Shield Tablet K1 into the PC with USB cable.
    Note: Not all USB cables are created equally!  Those included with cheap portable batteries, etc. may NOT be reliable enough to handle data transfer.  Using the one included with your smartphone is usually safe as it is rated for charging AND for data transfer.  Not all USB ports are the same.  Some on the back of the PC may work better than those on the front.  If you use a USB 3.0 port (you can tell if it is blue inside) and you have issues, try a USB 2.0 port.
  7. Confirm drivers for ADB are installed:
    1. On your PC, go to Device Manager.  Find the yellow (!) ADB device (depending on your version of Windows, it may read differently).  If none exist, you probably already have drivers.  Skip to step 8.
    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.
  8. Enable Developer mode on Shield Tablet K1
    1. On the Shield Tablet K1, go to Settings->About->Build (tap 7 times on the BUILD to unlock developer mode)
  9. Enable USB Debugging on Shield Tablet K1
    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.

[/elitetoggle][/eliteaccordion]

[eliteaccordion][elitetoggle title=”Step 3: Root Procedure”]

Root Procedure

  1. Reboot into Bootloader on Shield Tablet
    1. Launch Minimal ADB and Fastboot from the Start Menu or icon.  This puts you in a black DOS box.
    2. Type “adb devices” and make sure your Shield Tablet K1 appears.  Note: If you didn’t have a popup on your Shield Tablet K1 screen in Step 9.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 Tablet K1 when you run “adb devices” you’re ready to proceed.
    4. Type “adb reboot bootloader” and hit enter.  The Shield Tablet K1 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 to unlock bootloader.
    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 (skip if you already unlocked your bootloader)
    1. Type in “fastboot oem unlock” and hit enter.  EVERYTHING ON THE TABLET WILL BE LOST!
    2. You will see a prompt on the Shield Tablet K1.
    3. Confirm to unlock the bootloader. Do not be impatient!  Let it finish.
  4. Reboot to Shield Tablet K1 Interface
    1. Once the bootloader is unlocked, reboot the Shield Tablet K1 and return to the Shield tablet K1 main interface.
  5. Repeat Preparation: Steps 8 and 9 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 Tablet K1 screen for the authorization prompt.
  6. Deleted
  7. Reboot to Bootloader
    1. Type “adb reboot bootloader” and hit enter. The Shield Tablet K1 should reboot into the bootloader screen.
  8. Fastboot with TWRP
    1. Type “fastboot devices” and make sure your Shield Tablet K1 is visible.
    2. If your Shield Tablet is listed, type “fastboot boot twrprecovery.img” (or whatever you named it) and hit enter.  If your TRWP image filename has a space in it, you may have issues.  Note: You should have extracted the .ZIP file you downloaded into a .IMG file.  If you aren’t sure, you probably have HIDE FILENAME EXTENSIONS turned on within Windows.  You want to turn this OFF while doing this sort of work.
    3. Deleted
    4. After 15 seconds or so, you should see the TWRP Recovery screen.  Note: This experimental version has some UI issues, just keep at it.
    5. You may be prompted with something to do with the system being READ ONLY.  Accept the default and swipe.
  9. Install SuperSU
    1. Select Advanced.
    2. Select ADB Sideload.
    3. Follow the instructions to Swipe to Start Sideload
    4. In the Minimal ADB and Fastboot window on your PC, type in “adb sideload supersu.zip”.
    5. SuperSU will install (watch the Shield Tablet K1 screen)
      Note: Technically, sideload is a different “driver” than standard ADB or FASTBOOT. If you get an error message about devices not being found; check your Device Manager for a yellow (!) – it might read MTP or ANDROID DEVICE or something similar. Update that driver by right clicking and updating – then select BROWSE MY COMPUTER and choose LET ME SELECT … Scroll on that list until you see NVIDIA, select it then choose Android ADB Interface Version xxxx (highest one you have). This will enable sideload to work.
  10. Reboot to System
    1. Select Reboot System (Answer NO if asked anything about fixing or restoring ROOT)
  11. Run SuperSU application and apply any updates
    1. Once you are back up and running (first boot can take a little longer – and it may reboot one or more times on its own) find the SuperSU app installed on the Shield Tablet K1.  Run it and perform any upgrades (select Use Normal if asked).
  12. You are now rooted!  Test your root apps now.

[/elitetoggle][/eliteaccordion]

[eliteaccordion][elitetoggle title=”If Something Goes Wrong”]

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

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

Follow the instructions in our Tutorial: Restore to Stock Image K1

[/elitetoggle][/eliteaccordion]

[eliteaccordion][elitetoggle title=”Changelog and Credits”]
This process comes from this XDA thread.  I take no credit for the act; all I’m doing is documenting an easy way to do it.  This tutorial assumes you are running a Shield Tablet K1 (not Shield Tablet original) and you have the OTA installed that upgrades you to Marshmallow.

  • 2016-12-07: Beautified and condensed the root process considerably.  Updated Minimal ADB and Fastboot from 1.3.1 to 1.4.1.
  • 2016-04-14: Updated to SuperSU 2.71; Updated to new TWRP based on 3.0 multirom
  • 2016-02-18: Updated with new Downloader tool; added LTE images.
  • 2016-02-06: Added MD5 hashes for files and COPY buttons for commands for accuracy and convenience
  • 2016-01-24: Added link to restore to Stock Image
  • 2015-12-31: Made changes to reflect a missing step of rebooting to TWRP properly (thanks Exile1975)
  • 2015-12-30: Updated version to systemless Chainfire SuperSU with TWRP Recovery.
  • 2015-12-29: Initial Version with phh’s supersu.

[/elitetoggle][/eliteaccordion]

126 Responses to Tutorial: Root Shield Tablet K1 (Marshmallow)

  1. Fowwoled

    Followed the instructions for marshmallow root. Worked just fine. Rooted again ☺

    • ok tell me if this is right I have been having huge problems with charging my tablet it wont reconize any charger or cpu. I just got off live chat with nvidia and what the rep wanted me to do is unlock the bootloader and gave me steps to do it, Is this a blessing in disguise and I know have documentation on being told to unlock bootloader so I can root it now and unrooot if have any issues so able to send in for repairs or is this a trap from the rep but he didnt realize I keep records of this shit just cause of reps not doing job correctly. down below is what I have for steps and in my email is saved copy of conversation.

      SHIELD TABLET K1 RECOVERY IMAGE FLASHING INSTRUCTIONS

      To follow the instructions in this guide, you will need adb and fastboot.
      These tools are provided as part of the Android SDK:
      http://developer.android.com/sdk/index.html

      Before flashing this recovery image to your SHIELD TABLET, connect your SHIELD TABLET
      via USB to the PC where you downloaded this recovery image.

      Next, put your SHIELD TABLET into fastboot mode using one of the following methods:
      SW method:
      – Boot to android home screen
      – Connect the device to linux/windows system
      – Open terminal (on linux); command prompt (on windows).
      – Type “adb reboot bootloader” in terminal/command prompt

      HW method:
      – Turn off the device
      – Press “Volume Down” -> “Power”, hold “Volume Down” and leave Power buttons till device boots

      To flash this recovery image to your SHIELD TABLET, run the following commands from
      the directory where you extracted the recovery image package. If this is the
      first time you have done this procedure, you must unlock the bootloader (see
      below):

      fastboot flash recovery recovery.img
      fastboot flash boot boot.img
      fastboot flash system system.img
      fastboot erase userdata
      fastboot flash staging blob

      Unlocking the Bootloader
      Your SHIELD TABLET may have shipped with a locked bootloader. To update the device,
      you must unlock the bootloader using the following:
      – fastboot oem unlock
      – Press the “Volume Down” button to select “Unlock bootloader” option on device
      – Press the “Power” button to confirm the unlock. Your device’s bootloader is now unlocked.

    • i’m having an issue. i get the bootloader unlocked fine but when i flash twrp and reboot, it doesn’t show up…just an android with an red exclamation mark. any help would be great! thanks!

    • hi, I’ve been trying to root my Tablet K1. But now he is no longer even in boot menu? My PC displays a pop-up when I plug it in. but when I try to install than drivers not working too HELP ???

    • atul kumar says:

      Does wiping with twrp on nvidia shield k1 makes it lose it’s root access

  2. Daniel Ray says:

    I followed the directions. It all worked well unlocking the bootloader. When i try to flash root enabled boot image, it says ok and it finishes. But when I restart the device I still have no root access.

  3. Daniel Ray says:

    I was being a dummy, I downloaded the wrong app. Thank you for your support.

  4. Tried five times to flash twrp adb says OK but no twrp screen shows up

  5. I rebooted to recovery and twrp is working. I have supersu installed and I have root so it worked. Thanks for your post. I guess twrp is buggy like you said.

    • Hi, thanks a lot. I used the method with pph SU and it works perfectly (on shield k1 with MM).
      But now I saw that to use the app Xposed I must have recovery twrp, so can I flash on my tablet this recovery without problem? Or should I go back to factory settings and repeat everything from the beginning (and if the answer is yes as I delete pph user)?

  6. Is it OK to flash the xposed module or should I skip it for now?

  7. B4Ultra says:

    FOR ANYONE WHO IS STUCK AT THE NVIDIA SHIELD LOGO AFTER UNLOCKING THE BOOT LOADER, HOLD POWER AND VOLUME DOWN UNTIL IT IS OFF AND THEN PRESS THE POWER BUTTON, IT WILL NOT BRICK YOUR DEVICE

  8. stucky in recovery mode need help…
    can i contact you personally via livechat?

  9. Hi
    I give it a try too but after a complete reboot TWRP is gone… Just writes an error message when trying to boot in recovery..
    TWRP flashes correctly
    SuperSU installs also
    So Rooting works, just TWRP gots bricked at the end, why, no idea…

    • administrator says:

      Did you do a “fastboot BOOT recovery twrp.img” or a “fastboot FLASH recovery twrp.img”?

      There are times when TWRP doesn’t seem to “stick”. There is a fix – I’ll add it to the documentation.

  10. Hey Admin, great write up but I am having some trouble. Bootloader unlocked no problem. I don’t have a micro or OTG, did not come equipped with one from factory.

    So I cannot follow those exact instructions to get the SuperSU installed. When I copy to my main directory it’s showing up as an empty file when I’m in reboot mode. Do I need to put on a micro for it to load correctly?

    And we are to load the SuperSU file UNZIPPED, correct? The k1 will unzip it for me to use the app once flashed? I am having trouble with this portion.

    Victory lap time!!! Tell me what to do! Thanks man cheers

    • administrator says:

      As long as you didn’t use Adoptive storage already you SHOULDN’T HAVE to. But I would think the next step is a flash or microSD card for SuperSU.

  11. Hello Admin. Thank you very much for this. Unlicked just fine. However I’m stuck on step 8. When I try to flash recovery I get the following error:

    sending ‘recovery’ (11460 KB)…
    FAILED (data transfer failure (Unknown error))

    retrying only changes it to:

    sending ‘recovery’ (11460 KB)…
    FAILED (remote: (Timeout))

    Also, I can’t push superuserbeta.zip via adb, I had to copy it directly on the pc. Now, I can’t even copy anything to the SD via windows file explorer when the K1 is connected via usb. It’s like I can’t send any file to the tablet. Any advice, please?

    Thank you 🙂

  12. Aidan Estell says:

    After part 3 of step 8, Mine just boots to the nvidia boot screen. How long should I wait?

    Its been approx 5 mins?

  13. FYI to anyone else that has this issue. If after your first initial boot after flashing TWRP and gaining root, if you don’t have wireless (WiFi won’t turn on) then do a warm restart (Hold POWER and hit Restart). It should come back afterwords.

  14. hi, i need help fixing my shield tablet.
    i have successfully installed supersu, but the device froze at logo screen.
    so, i went to bootloader menu and typed fastboot erase user data
    then, the tablet loop to twrp like this :

    http://content.screencast.com/users/sthetix/folders/Default/media/098aca98-496b-4c04-8ca0-3e135e9b92ec/image.jpg

    after that, the tablet wont boot and it seems like dead.
    my pc recognize it as APX on device manager.
    and i cant boot to bootloader now.

  15. Dan Blue says:

    Hi

    Good job, it’s working fine.
    Root with SuperSu 2.66 and Xposed v79 installed

    For TWRP experimental, some graphical issues, but Backup, restore, wipe, flash, SD and OTG access are Ok.

  16. vitz3r says:

    Hello, just need a bit of insight with regards to the issue I’m having.
    When I try to flash the twrprecovery.img I get the following in the dos window:

    sending ‘recovery’ …
    FAILED <command write failed >
    finished. total time: 0.003s

    What should I do?

    • administrator says:

      I’ve seen this a couple of times. It is a failure in the USB chain somewhere. Too long of USB, poor USB cable (aka one made for POWER and not for DATA), daisy chainging USB cables, using hubs or front USB port instead of one built into the motherboard on the back.

      • Seph Potter says:

        I’ve tried 2 separate USB cables, 1 from a galaxy note 2 and the other that came supplied with sony xperia z3. I’ve also used direct usb ports from the mobo and not the front ones? very frustrating as every time I try to load recovery it fails 🙁

  17. Hey all,

    Just got my tablet today. I decided only to unlock the bootloader for now and will root later when things are a bit more stable for Marshmallow. In any event, I got the tablet, updated OTA to Marshmallow and followed the instructions above.

    A couple things of note:
    -I had to set my USB type to PTP for Windows 10 to recognize it, otherwise it just said MTP and wouldn’t update the drivers.
    -I didn’t realize that running “adb reboot bootloader” was all you needed to do for fastboot to be ready to go.
    -Finally, I had to plug the usb cable into a direct usb (2.0) port on the board, one of the front ones I was using kept resulting in a fastboot failure.

    TThanks for the help!

  18. Maksim Gejer says:

    hmmmm

    HELP 🙂

    C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oen unlock
    usage: fastboot [ ]

    commands:
    update reflash device from update.zip
    flashall flash boot, system, vendor and if found,
    recovery
    flash [ ] write a file to a flash partition
    flashing lock locks the device. Prevents flashing partitions
    flashing unlock unlocks the device. Allows user to flash any partition except the ones that are related to bootloader
    flashing lock_critical Prevents flashing bootloader related partitions
    flashing unlock_critical Enables flashing bootloader related partitions
    flashing get_unlock_ability Queries bootloader to see if the device is unlocked
    erase erase a flash partition
    format[:[][:[]] format a flash partition.
    Can override the fs type and/or
    ………
    .
    .


    ..
    .

    .
    -l with “devices”, lists device paths
    -p specify product name
    -c override kernel commandline
    -i specify a custom USB vendor id
    -b specify a custom kernel base address.
    default: 0x10000000
    -n specify the nand page size.
    default: 2048
    -S [K|M|G] automatically sparse files greater
    than size. 0 to disable

    C:\Program Files (x86)\Minimal ADB and Fastboot>

  19. Maksim Gejer says:

    Could you make a video would be very great

  20. fredzlux says:

    I have the new K1 but with Lollipop (stock) and I don’t want to upgrade to Marshmallo now because of the compass bug.
    Can I use this procedure and this zip file for rooting Lollipop one the K1, admin?

  21. Seph Potter says:

    Hi guys, I’ve followed the tutorial and im stuck at step 8. Fastboot with TWRP! When i type command “fastboot flash recovery ‘recovery.img’ (what i renamed the image), it flags up with an error and cannot load? Any help please would be much appreciated, thanks in advance : )

    • administrator says:

      USB cable is the likely issue. No daisychaining. Use a USB that came with a phone for data use – not one that came with a power adapter or external battery. Don’t use a hub. Use the port in the back of the computer. It always seems to be one of these.

      • Seph Potter says:

        Yeah I’ve tried the official cables that came with phone handsets and the rear ports but with no success. Not really sure what to try, I’ve also attempted different download mirrors for the TWRP?

  22. Fireknox525 says:

    Whenever I enter “fastboot flash recovery twrp.img” it just gives me the message “error could not load:twrp.img” Any help?

    • administrator says:

      Sounds like the file is misnamed or has a double extension (aka twrp.img.img) when you renamed it.

      From Min ADB, do a DIR and see what the filename is …

  23. No Name says:

    Easy to follow root instructions thanks!

    Having one issue, in ES File Explorer, I was able to click on the Download as well as the “sdcard” options in the Local tab. How exactly do I get this back, I’m confused as to how I would transfer via FTP and where it is going now. Can I create symbolic links or something of this nature?

    Thanks in advances!

    • No Name says:

      When I click on the following from within ES File Explorer:
      Home = “/sdcard/ is not found”
      Download = “/storage/emulated/0/Download is not found”

      I also seem unable to login via FTP now without error, like as a result of it not forwarding to the sdcard path, leaving me unable to side load as I was previously.

      Any help would be appreciated.

      • No Name says:

        System restart got the sdcard working fine again as internal storage.

        Please delete posts as necessary. Thanks again for the tutorial, now I can move onto using a ps3 controller and get some Tasker profiles going on my k1.

    • administrator says:

      Read my article on Adoptive Storage…

  24. ROBERTO SARABIA GALVAN says:

    Hello such, sincerely first of all ..
    The tutorial seems excellent !!!. It is still almost the same steps to unlock the bootloader to install recovery and root as in android 5.1.1

    The point is that already ise such and such you publish it on android 6.0 the matter is that it does not work when I try to install the TWRP recovery installation check but I get when trying to enter the custom recovy (or surprise follows the recovery of manufactures) and let alone root

    I invite you to realize this video tutorial, I assure you would save a lot of doubts and only lose a few minutes to film, would save time answering our questions and concerns you as repetitive

    Think about it !!!

    Thanks in advance for your time you spend on and help keep us abreast, follow si !!! excellent work … greetings from Mexico !!!!

    • kissc00l says:

      Hello.

      That’s true and …. normal. Because when you follow this fantastic tuto, you should notice that this fastboot command doesn’t install TWRP recovery but only boot on (“fastboot boot recovery.img” and not “fastboot flash recovery.img”)
      Regards

  25. illusions88 says:

    Hi i cant seem to get into TWRP recovery since all i get is this after flashing twrp recovery:

    E:\Program Files (x86)\Minimal ADB and Fastboot>fastboot boot recovery
    cannot load ‘recovery’: No such file or directory

  26. Ss Alxs says:

    Does this still work after doing basically yesterdays OTA update?
    thanks

  27. caninedragon says:

    I am so very lost, I accidentally updated to 6.0 today and was dismayed to find that some of my apps no longer work properly. They worked fine on Lollipop and I would love to roll back. The problem is that windows 10 does not, and will not, accept my tablet as anything other than an “MTP Mobile device” Any attempts to accept ADB are met with a message saying that the folder i’ve selected does not contain a compatible driver. I don’t know how to get my desktop to recognize it as an android device, more specifically, I don’t understand why it won’t allow me to uninstall the mtp driver and install the ADB one.

  28. Seph Potter says:

    Hi guys, I rooted my shield tablet (K1) a few weeks back, but like a few days later the new software update was released! I really need this new update on my device which fixes the controller mapping for xbox 360 controller. I’ve read that once rooted the update can’t be applied, so what steps should I be taking to get this update? Sorry if there is already a thread about this! I’m a total noob with this kind of stuff, thanks in advance.

  29. Hi i have a nvidia shield tablet k1 and updated to the latest version of android Marshmallow OTA 1.1 but now i cant access recovery or flash stock lollipop using Minimal ADB and Fastboot. Cannot root and cannot flash twrp. Anyone’s help will be appreciated. Thanks in advance.

  30. Im stuck on 3-3 When i type “fastboot boot recovery”i get cannot load ‘recovery’ no such file or directory

  31. Jeffrey Chen says:

    Hello. I’ve rooted other devices before and usually, it’s perfectly fine and easy. For my tablet, I’m not too sure why, but whenever I attempt to flash the TWRP img, it always comes up as “error: cannot load ‘twrp-20151227-EXPERIMENTAL-shieldtablet-m.img'”. I know how to install SuperSu binaries from recovery, it’s just that the recovery won’t flash. Any help would be greatly appreciated.

  32. PROXYMITY says:

    Hi guys,

    thanks for this tutorial!

    I got a *little* problem which prevents me from even getting access to the device:
    When I “adb devices” and the demon starts, the list is completly empty. Yep, Ive done the preparation segment, installed drivers, tryed different USB-A microUSB-B cables, tryed different USB-Slots on my machine, activated dev-options and stuff.

    Maybe the cause is when enabling USB-debugging; I dont get asked when swithing it on – but Im also not getting asked when executing “adb devices” (other than mentioned in the tutorial).

    Might be the problem located at Windows 10 (x64, Pro; maybe someone here can confirm that its caused by the OS – or not)?

    Felt lucky, finally deciding to root it.. and ran into this.. I bet thats a sign.. 😀

    Have a great weekend,
    Proxy

    • administrator says:

      If you never got prompted on the Tablet to “Allow this PC to connect”, then ADB will never work.

      So you’ve tried the things on my list already. I use Windows 10 (64bit) myself and it works for me. You may have a driver mismatch issue. Do you have another Android device (phone, etc) you’ve attached to this PC and used ADB on? If so, you’ll probably have to clean those out. I THINK I have a FAQ entry for that on the site. If not, let me know and we’ll see what we can do.

      The other option? Go into Developer Tools, turn OFF ENABLE USB DEBUGGING, flip it back on, select REVOKE (the entry right under it) then plug the PC in again. You SHOULD get prompted for the security access.

      This is most likely an issue with drivers though 🙁

  33. When trying to flash the twrp recovery img the adg fastboot screen keeps going to the help menu. Unable to get past this.Help please

  34. I am flashing the TWRP image

  35. kissc00l says:

    Hello,

    first af all, thank you for your Tuto. It wroked fine on my Shield Tablet K1 with Marshmallow (Tablet 1.1, the new one) but… I would like now to install TWRP on my Shield Tablet, not just boot on with Fastboot to root it with TWRP/SuperSu.
    So I’ve typed this command:
    “fastboot flash twrpShield.img” (twrpshield.img is the name I’ve choosed 😉 )
    but this command returns an error. Yet, when I’ve typed “fastboot boot twrpshield.img”, it worked successfully.
    So I think this TWRP version can’t be installed on the K1 with Marshmallow. Maybe I should use TWRP 3.0.x.0, but can’t find the one for Shield K1.
    Do you have a link?
    Best regards.

  36. dylan murphy says:

    Just wanted to say a huge thank you for this tutorial, worked great for me. Also, to others with adoptive storage already turned on, I was able to do this whole process just fine without taking it out, only hang up is that you have to reformat the storage if you leave it in there (mine is stuck). It didn’t have any impact on me pushing SuperSU and I was able to reformat the storage afterwards (I was worried the storage would be permanently inaccessible as the tutorial made it seem, like that the device would never recognize it again or something.) Anyway, thanks again, great work and super easy as far as these things go.

  37. Yavga says:

    Me again, after studying matters a bit further the culprit of a failing root was a non-existing driver on my pc from Avatron “Air Device”.
    every time I connected my Shield through USB this driver somehow linked itself to the Shield K1

    I managed to root now 🙂 Thanks for the tut!
    (Done on 6.0.1)

  38. Quaqqer says:

    I have update 1.3, can I use this root method? And do I have to swap out any files or something?

  39. After i flash TWRP i go to boot via the rocker method and i get the dead android, if i try to boot via “fastboot boot recovery” i get cannot load ‘recovery’: No such file or directory. followed all steps of the above.

  40. Rui Liu says:

    Hi, I got an issue here, after successfully installing SuperSU, I rebooted system from twrp, and then my tablet keeps rebooting very long and it seemed staying in the rebooting loop and never stop. NVIDIA log shows there, and under that, there is Powered by Android. Any ideas?

    And I tried fastboot devices, my device is not shown any more. All the other steps are fine.

    • administrator says:

      did you “fastboot flash boot xxxxx.img” or did you “fastboot boot xxxxx.img”? And are you using the img that we provided or a different one?

  41. monte says:

    Hey! I could really really use some help. I get to Step 6.1 of the Root Procedure before I get stuck. Just some background, I’m trying to root the Nvidia Shield K1 Tablet (as you would expect in this forum) and it runs on 6.0.1. As for the PC, I’m using a Microsoft Surface Pro 4 that runs on Windows 10 and I need this computer for school so the less riskier the better if that’s relevant in terms of what I’m downloading. So when I type in “adb push supersubeta.zip /sdcard/”, it just shows me tons of adb commands and what they accomplish and does not say anything about copying over correctly or not. You can probably tell, but I’m new to all this so be liberal in your explanations and jargon. I’m genuinely interested in learning this type of stuff though so I’d love it if you could walk the newbie through this

  42. monte says:

    Never mind. I figured it out. Thank you so much for this guide. Reading the comments sure helped a ton too. Thank you everyone.

  43. Hi i am trying to install supersu but when i try it is blank how do i fix it?

  44. Tom Hand says:

    It worked! But, I had to copy the su.zip to the SD card via the cardreader on my Windows PC. Also, flashing the image only worked with a short, high-quality USB cable.

    Now that it’s rooted, is it possible to encrypt?

    I was also wondering how to change the network hostname from android-xxxxxxxxxxxxxxx to something else. A search of the filesystem didn’t turn up any clues.

  45. Julius Anthony Savella says:

    Need help badly anyone pls. Just got my k1 tablet and bootlader is locked. And no “unlock bootloader” option, im running 6.0.1. I’ve trying to unlock and root but im runiing out of luck. Im using latest windows 10. Pls pls pls help me kind sir

  46. Tallungan Mitch says:

    Stuck on step 6.1 and cannot figure out what i am doing wrong here. completely migrated my data from my SD card back to my internal storage, also completely removed the card itself and it still gives me the No such file or directory message

    Where am i going wrong

    Thanks

  47. Is it possible to reroot my K1 without loosing everything? I rooted awhile back and reflashed it back to stock. I have a 256GB micro set to adoptive storage with alot of games installed already. would like the ability to use titanium backup.

  48. timmyd says:

    I have tried twice to root my K1. I have rooted other devices so not sure why I am having problems with this one. I am using the most recent SuperSU file named UPDATE-SuperSU-v2.46. Is there another SU file that I can try? After I install SU with TWRP, and reboot, it just hangs on the nvidia bootup screen. I then flashed the 1.4.0 recovery file and tried a second time. Same results. Any help will be greatly appreciate 🙂 I am wanting use this for live streaming (broadcasting) so need to root it and tweak it just a bit. THANKS!!

  49. why does the downloadable twrp version support multirom?

  50. mike trost says:

    Will this work fine with the newest update 1.5? Also if they release new ota updates I decide to update will it let me? I know I would probably lose root jw some of my other device’s block the updates with root access..

  51. Nik M says:

    Followed the instructions for marshmallow root. Worked up fine to..ABD Sideload..slided then waited. i`ve got , failed. What am i doing wrong ? cheers

  52. Nik M says:

    ok. sorted out…the problem was that supersu.zip had this (supersubeta.zip) format. changed that and all good.

  53. hey man, im on the adb sideload part.. when i put “adb sideload supersu.zip” (without the aphostrophe) on Minimal ADB and Fastboot, it says “cannot read supersu.zip” what do i do? is this part important? or can i just download supersu directly in my tablet?

    • wait, when i swipe adb sideload am i supposed to wait for it to finish when it says “Starting adb sideload features” or am i supposed to type the “adb sideload supersu.zip”?? im very confused and impatient right now. need answers ASAP pls

      • administrator says:

        When you swipe it, it puts the tablet is SIDELOAD mode – Windows may take a few minutes to see it the first time. You type and run the sideload command as soon as your computer recognizes it. You can try it anytime – if it can’t see the tablet, nothing bad will happen.

    • administrator says:

      If you can put SuperSU.zip on your tablet, boot to TWRP – you can install it from there. We use Sideload because it works regardless of adoptive storage settings.

  54. Can I install TWRP instead only to boot

  55. why I have to sign with facebook twitter and so. What is with data protection?

Leave a Reply