Tutorial: Restore to Stock Image (Shield TV 2015)

This returns your Shield Android TV (2015; 16GB) to “stock” V6.2 with Android 7 (aka Nougat). If your Shield TV doesn’t have a power button or has a built in hard drive? This isn’t the right tutorial. Check out the Shield TV (2017; 16GB) tutorial or the Shield Android TV (Pro; 500GB) tutorial.

There are numerous reasons you may wish to do this; mostly if you can’t perform an OTA upgrade after rooting – you may need to return to stock before you can accept the upgrade.

Note: There is no current way to roll back the Shield TV to Marshmallow (pre-5.0).  If you have a solution, please email me.

37 Responses to Tutorial: Restore to Stock Image (Shield TV 2015)

  1. jps shield says:

    I am stuck in a boot loop. Are you sure the .bat file is correct for flashing back to stock?

    If I use nv-recovery-image-shield-atv-pro-upgrade1_3_500GB.zip it get stuck in boot loop.

    If I use nv-ota-foster-na-3.2-500gb-full.zip i get stuck in boot loop.

    I looked at the .bat file and it reads as follows:

    fastboot flash recovery recovery.img
    fastboot flash boot boot.img
    fastboot flash system system.img
    fastboot flash userdata userdata.img
    fastboot flash staging blob
    fastboot flash dtb tegra210-foster-e-hdd-p2530-0932-e02-00.dtb

    some of these files are missing from nv-ota-foster-na-3.2-500gb-full.zip
    I tried to just extract the nv-recovery-image-shield-atv-pro-upgrade1_3_500GB then nv-ota-foster-na-3.2-500gb-full.zip over the top of it and I still get boot look freezing on the android dots.

    I will keep trying but I think there is an issue with this guide.

  2. jps shield says:

    I figured it out. Your guide may work but it did not in my case. I have the newest version 500gb Pro. Latest updates etc…I had messed up my google play store with a modded one. So I was just restoring to fix the google play store. This guide, nor the guide from the menu worked for me. This is what worked.

    minimal_adb_fastboot_v1.4_setup.exe from their site
    nv-recovery-image-shield-atv-pro-3.2.0.zip from nvidia developer site

    I did not use the flash-all.bat file or command, but suspected it may be the issue. My shield was reporting back that it was already unlocked. I manually followed their list of commands

    If you are CERTAIN that your SHIELD device OS is currently running Android
    Marshmallow or newer (i.e. the Android version is 6.0 or greater), follow
    these intructions:

    *** Prerequisites:
    1. Ensure that the bootloader is unlocked (see above step)

    *** Flashing instructions:
    1. Execute these commands on the host PC:

    fastboot flash staging blob
    fastboot flash boot boot.img
    fastboot flash recovery recovery.img
    fastboot flash system system.img
    fastboot flash vendor vendor.img
    fastboot reboot

    This worked!!!!! 😀



    • administrator says:

      Strange. I should be using the same exact image. Restoring to stock should completely nuke the thing. Unless they did something strange with 3.2’s full image. I’ll give it another look when I get the 500GB one on the bench.

  3. jps shield says:

    Oh and after I was done, for some reason it only showed 30gb instead of 500gb. So i had to do a full erase where the android robot logo shows up then it was all good. Storage shows back up correctly. Yes weird.

  4. I used flash all bat . Light comes on wont boot up cant get into fastboot. I tryed everything

  5. I did try that its looking for apx driver i used flash all bat
    that is what killed it
    Thanks for your reply

  6. Well i fixed it RMA it if you use FLASH ALL BAT. i Would be
    very careful

    • administrator says:

      Sure, the process of restoring your machine to stock is approved and actually put out by NVidia themselves. I just made it into an easier tutorial 🙂

  7. MixPlanet . says:

    I have NVIDIA SHIELD tv 16gb how to rewrite the system . if the USB debugging off.lost all data

  8. MixPlanet . says:

    I tried everything, and lock and unlock oem, and stock image,format system ,format cache , internal storage 0MB when l go in twrp inside, but catches the SD card 32gb working, I did Setup and installing the new update system, accidentally lost power at home, and so Systema shows now dead android red exclamation mark,received and damage the first day tv shield,not have time turn on debuging enable,

  9. MixPlanet . says:

    C:\Program Files\Minimal ADB and Fastboot>fastboot getvar all
    (bootloader) version-bootloader: 1.0
    (bootloader) version-baseband: 2.0
    (bootloader) version-mts: NO SUPPORT YET!
    (bootloader) version: 0.4
    (bootloader) 04243150351810000333
    (bootloader) mid: 001
    (bootloader) product: t210ref
    (bootloader) secure: No
    (bootloader) unlocked: Yes
    (bootloader) partition-size:bootloader: 0x0000000000200000
    (bootloader) partition-type:bootloader: basic
    (bootloader) partition-size:recovery: 0x0000000001980000
    (bootloader) partition-type:recovery: basic
    (bootloader) partition-size:boot: 0x0000000001980000
    (bootloader) partition-type:boot: basic
    (bootloader) partition-size:dtb: 0x0000000000400000
    (bootloader) partition-type:dtb: basic
    (bootloader) partition-size:system: 0x0000000080000000
    (bootloader) partition-type:system: ext4
    (bootloader) partition-size:cache: 0x0000000010000000
    (bootloader) partition-type:cache: ext4
    (bootloader) partition-size:userdata: 0x00000002d8e63e00
    (bootloader) partition-type:userdata: ext4
    finished. total time: 0.032s

  10. MixPlanet . says:

    can’t open /dev/block/platform/sdhci-tegra.3/by-name/misc

  11. Atilano Reza says:

    Hello tried going back to stock . But I don’t think it work. when the shield restarts it’s like nothing happened it starts without all my settings. Any Ideas what going on?

  12. ok im really new to this so i bought a shield tv 500gb the guy have a custom android running version 6 so i want to restore back to factory but i cant i went in the android setting and restore from there but now im at the welcome screen to android i just want to follow these steps u lay out but how do i connect the shield to my pc and also how do i install the drivers tnks

  13. hey when i follow the instruction to restore using minimal adb and fastboot it say no device fount what should i do tnks

  14. About Point 4: “Wait and watch. Be patient.”
    Exactly how patient is One expected to be? Is the Andy Screen (With spinning Orb) to be considered normal?


  15. Hi,
    I have a shield tv 2015.
    I flash the recovery image for shield tv 2017 by mistake.
    I flash it because after the ota update to android 7.0 allot of things doesn’t work.
    Everithing was run fine but after the reboot the shield dosn’t boot anymore.
    Now is in APX mode. I try software mode, i try hw mode on reboot but nothing works.
    What can i do?

    • administrator says:

      Word on the street is that if you flash 2017 on 2015, you now have a brick and will need to RMA it. I’ve not heard of a successful recovery.

      • After two days , I’ve solved my problem with fastboot (USB DEVICE UNKNOWN). ITS VERY HARD TO FIND.
        My miniUSB male -> To USB male Original Nvidia works OK for to chargue devices, transfer files, for the ADB, and… until some time ago , also worked OK for fastboot. I’ve changed the shield firmware , fullandroid , rooted, my Shield TV, almost 30 times . That’s because I’m mantaining a tutorial about fullandroid in a spanish forum.

        But that cable is broked now. Doesnt work with fastboot. But thats crazy: ALL the other functions , works all OK.

        I’ve tested with a brand new unused origninal cable and fastboot works OK. UNBELIAVABLE

        • administrator says:

          No shocker here at all. That’s why the tagline of this site is: Got a problem? It’s probably your USB cable. 9 times out of 10 — that’s the issue.

          I’m hoping if you’re borrowing content here for translation we’re getting credit/linkback 🙂

  16. grimjawh says:

    Hi iam trying to restore my shield tv 16g 2015. I have all the files in the adb folder, when i type fastboot devices it gives me the device, but when i then go and and try to flash nothing happens. for example when i type:

    fastboot flash staging blob and hit enter nothing happens it just hangs. you know how i can fix that?

    thanks in advance

    • administrator says:

      Poor cables or USB port issues can cause a device to show up, but not allow the quality necessary for data transfer. Do you get an error or does it just sit there?

  17. hello guys,

    i have the 2015 shield pro updated to nougat. may i do a factory reset with power button ? my Bootloader are unlocked normally.

  18. 磊 王 says:

    Hi,I have the 2015 shield pro,and want the root permission of the system.But I cannot get it without a 1080P TV.Can you make a backup of system with “root” permission by using “dd” commond in Linux.The backup can also rescue the system.Thanks very much.

    • administrator says:

      You may be able to venture out on your own and get a newer TWRP that does support 4K.

      You may consider getting ahold of a cheap small TV. I have a little Naxa that does the job very well.

  19. Joe Webb says:

    Did a factory reset and now I just have a power light no signal to TV….1st gen pro edition…. Any ideas thanks in advance.

    • administrator says:

      Looks like you restored using the wrong tutorial. This is not the Pro tutorial, it is the 16GB tutorial. Have you attempted a hard boot to bootloader?

  20. Hi! I have a 2015 16gb version with the latest Oreo. The issue is that recently the devices randomly reboots and has issues with video playback. I saw somewhere that these are known bugs with oreo. So i would like to returm to Nougat. I dont need root but i would need the plex server running. Can this guide be used to return roll back from 8 to 7? I am asking because i saw lot of posts with bricked shield tvs. I have never tried to tinker with shiled tv before but i have quite a lot of experience with all these kind of stuff on android phones. Many thanks

    • administrator says:

      Rolling back a major version is apparently a pretty much guaranteed brick. Couple folks at XDA claim they pulled it off – but I’ve received far too many emails about bricked attempts to recommend trying it. I would say that the 2015 units (16/Pro) may be a little less locked down and MAY possibly be easier – but I just can’t recommend it. Perhaps someone else has a foolproof solution?

Leave a Reply