FORUMS

Stock Recovery Images and OTA Library w/ Guides

171 posts
Thanks Meter: 184
 
By MidgetMob, Senior Member on 30th December 2014, 09:21 PM
Post Reply Email Thread
I'd like to start off by thanking the XDA community for getting me started on the path to organizing these files. I noticed that there are a lot of posts scattered here and there with OTA downloads, sideloading, stock recovery images, and the like so I figured I'd attempt to start an all-in-one thread. The goal is to group together anything that is stock (meaning 'from Nvidia'), basic rooting/TWRP, and guides for the mentioned topics. I will gladly maintain this thread as long as there is interest in it, however I will appreciate any feedback. I am, after all, an XDA noob.

I am not responsible for any damage you cause to your tablet while following these steps. If you brick your tablet, cause it to explode, or your tablet simply decides that you're not worthy of it anymore and runs off to France to be with its mistress, that's on you.

Thanks to @stanglx for their contribution to the Driver Installation guide.


This thread currently contains mirrors for all available OTAs and Recovery Images related to the NVIDIA SHIELD Tablet, as well as a few guide.

To Do:
  • Clean up driver installation guide.





Basic Setup

Driver Installation

Enable Developer Mode
  1. On your tablet, go to Settings -> About Tablet
  2. Tap the 'Build Number' section 10 times
  3. On your tablet, go to Settings -> Developer Settings
  4. Enable 'Developer Mode' and plug your tablet into your computer
  5. When your tablet throws up a prompt, check the box that says 'Always trust this device' and select 'OK'

Initial ADB Driver Installation
  1. Download the driver package and extract it
  2. On your computer, go to Control Panel -> Device Manager
  3. There should be a device with the name 'SHIELD Tablet' or similar with an exclamation mark next to it.
  4. right-click the device and select 'Properties'
  5. Select the 'Driver' tab and click 'Update Driver'
  6. Select 'Browse' and then browse for the folder where you extracted the drivers to
  7. Let the driver load and you should be good to go

Future ADB Driver Installation
If you ever have problems with the ADB driver, follow this method to reinstall it.
  1. On your computer, navigate to Control Panel -> Device Manager
  2. Navigate to the device labeled 'SHIELD Tablet' or similar
  3. Right-click the device and select 'Update Driver Software', select 'Browse my computer', and then select 'Let me pick'
  4. Uncheck 'Show Compatible Hardware' and browse under 'Android' for the 'ADB Composite Driver'
  5. Load the driver and you should be good to go

Fastboot Driver Installation
  1. Reboot to your bootloader
  2. On your computer, navigate to Control Panel -> Device Manager
  3. Navigate to the device labeled 'SHIELD Tablet' or similar
  4. Right-click the device and select 'Update Driver Software', select 'Browse my computer', and then select 'Let me pick'
  5. Uncheck 'Show Compatible Hardware' and browse under 'Android' for the 'Fastboot Driver'
  6. Load the driver and then open a command prompt for fastboot on your computer
  7. Type 'fastboot devices' and your device should be listed

Booting to Bootloader

Option 1 - Can only be done if your tablet is already turned on. You must have ADB as well as drivers installed for your tablet.
  1. Plug your tablet into your computer
  2. If you get a prompt on your tablet, make sure to check 'Always allow from this computer' and press 'OK'
  3. Open a command prompt in your ADB directory
  4. Type 'adb reboot bootloader'
  5. Your tablet should now be at its bootloader

Option 2
  1. Make sure your tablet is turned off
  2. Hold the volume-down button and tap the power button once
  3. You can let go of the volume-down button as soon as the backlight comes on
  4. You should now be at the bootloader

Unlocking Bootloader
You may void your warranty by unlocking your bootloader. You will need fastboot for this.
  1. Plug your tablet into your computer
  2. Boot into your bootloader
  3. Open a command prompt in your fastboot directory
  4. In the command prompt, type 'fastboot devices' and make sure your device is listed
  5. In the command prompt, type 'fastboot oem unlock'
  6. Your bootloader should now be unlocked

Booting to Recovery
  1. Boot into your bootloader
  2. Use the volume buttons to select the 'Recovery Mode' option
  3. You should now be in recovery mode
  4. Only For Stock Recovery
    Code:
    When you see the android icon, hold the volume-up button and tap the power button

Flashing Custom Recovery
You must have fastboot drivers installed as well as an unlocked bootloader.
  1. Plug your device into your computer
  2. Reboot to your bootloader
  3. On your computer, open a command prompt in your fastboot directory
  4. Enter the command 'fastboot flash recovery <filename>' where <filename> is the path to your custom recovery image
  5. Navigate to the 'Recovery Mode' option on your device and select it
  6. You should now be at your custom recovery


Recovery Images
You will need fastboot as well as an unlocked bootloader for this. Recovery images wipe everything but an unlocked bootloader.
Your warranty may be void if you follow these steps.

Flashing the Recovery Image
  1. Extract your desired recovery image to a directory of your choosing
  2. Enter your bootloader
  3. Enter the following commands one by one - replace {dir} with the directory you extracted the recovery image to
    Code:
    fastboot flash recovery {dir}/recovery.img
    fastboot flash boot {dir}/boot.img
    fastboot flash system {dir}/system.img
    fastboot flash userdata {dir}/userdata.img
    fastboot flash staging {dir}/blob
    fastboot flash dtb {dir}/tegra124-tn8-p1761-1270-a04-e-battery.dtb
  4. Reboot your device and you should be good to go

Optional Steps


Flashing a Custom Recovery
Follow the instructions in 'Basic Setup' as your custom recovery will have been wiped

Root Your Device
You can also use 'adb sideload' to install SuperSU.
  1. Place your desired SuperSU zip somewhere on your device
  2. Reboot into your recovery
  3. Install SuperSU

    For Stock Recovery:

    1. From the main menu, select 'apply update from external SD card'
    2. Navigate to wherever you placed the SuperSU zip and select it

    For TWRP:

    1. From the main menu, select 'Install'
    2. Navigate to wherever you placed the SuperSU zip and select it
    3. Swipe right to begin flashing

    For CWM:

    1. From the main menu, select the 'install zip' option
    2. Navigate to wherever you placed the SuperSU zip and select it
  4. Reboot after your recovery is finished flashing the zip
  5. You should be rooted once again


OTAs
OTAs act as patches, therefore you will keep most, if not all, of your user-related data.
If you are rooted, you can only flash full OTAs. Incremental OTAs will not find the correct version on your device.

Flashing via sideload
This method requires adb/fastboot.
  1. Reboot to your recovery (follow directions in 'Basic Setup')
  2. Have your device enter sideload mode

    For Stock Recovery:

    1. On the main menu, select 'apply update from ADB'
    2. You should now be in sideload mode

    For TWRP:

    1. On the main menu, select 'Advanced'
    2. Select 'ADB Sideload'
    3. Swipe right to enter sideload mode

    For CWM:

    1. On the main menu, select 'install zip'
    2. Select 'install zip from sideload'
    3. You should now be in sideload mode
  3. Open a command prompt for ADB on your computer
  4. Enter the command 'adb sideload <filename>'
  5. Reboot when sideloading is complete
  6. You should now be updated

Flashing via TWRP/CWM
  1. Place the desired OTA zip somewhere on your device
  2. Reboot to your custom recovery (follow directions in "Basic Setup")
  3. Install the zip file

    For TWRP:

    1. Select the 'Install' option on the main menu
    2. Browse to the location of the OTA zip
    3. Select the zip file and swipe right to flash

    For CWM:

    1. Navigate to 'install zip'
    2. Select option 1 or 2 depending on where you placed the OTA zip
    3. Browse to the location of the zip and select it
    4. Select 'Yes' and CWM will begin to flash the OTA
  4. Reboot when your custom recovery is finished flashing and you should be updated

Optional: Re-Root Your Device
You can also use 'adb sideload' to install SuperSU.
  1. Place your desired SuperSU zip somewhere on your device
  2. Reboot into your recovery
  3. Install SuperSU

    For Stock Recovery:

    1. From the main menu, select 'apply update from external SD card'
    2. Navigate to wherever you placed the SuperSU zip and select it

    For TWRP:

    1. From the main menu, select 'Install'
    2. Navigate to wherever you placed the SuperSU zip and select it
    3. Swipe right to begin flashing

    For CWM:

    1. From the main menu, select the 'install zip' option
    2. Navigate to wherever you placed the SuperSU zip and select it
  4. Reboot after your recovery is finished flashing the zip
  5. You should be rooted once again


Downloads
I will give links to Dropbox and my personal server if the mirrors below go over their limit. Just PM me. Recovery images are directly from NVIDIA GameWorks.


Code:
Marshmallow (6.0.x) | v4.0 to v4.4
Lollipop    (5.1.x) | v3.1 to v3.1.1
Lollipop    (5.0.x) | v2.1 to v2.2.2
KitKat      (4.4.x) | v1.0 to v1.2.1

Links for all of the downloads: Recovery Images | Everything Else | MD5 Hashes

Recovery Images

LTE (RoW)
Code:
Update 4.4   | Google Drive | MEGA | Mediafire
Update 4.3   | MEGA
Update 4.2   | MEGA
Update 4.1   | MEGA
Update 4.0.1 | MEGA
Update 3.1.1 | Google Drive | MEGA
Update 2.2.2 | MEGA
Update 1.2.1 | MEGA
LTE (US)
Code:
Update 4.4   | Google Drive | MEGA | Mediafire
Update 4.1   | MEGA
Update 3.1.1 | Google Drive | MEGA
Update 2.2.2 | MEGA
Update 1.2.1 | MEGA
WiFi
Code:
Update 4.4   | Google Drive | MEGA | Mediafire
Update 4.3   | MEGA
Update 4.2   | MEGA
Update 4.1   | MEGA
Update 4.0.1 | MEGA
Update 3.1.1 | Google Drive | MEGA
Update 2.2.2 | MEGA
Update 1.2.1 | MEGA
Factory      | MEGA

OTAs

Incremental

LTE (RoW)
Code:
Update 4.3   to 4.4   | MEGA | pCloud
Update 4.2   to 4.3   | MEGA | pCloud
Update 4.1   to 4.2   | MEGA | pCloud
Update 4.0.1 to 4.1   | MEGA | pCloud
Update 3.1   to 3.1.1 | MEGA
Update 2.2.1 to 3.0   | MEGA | flash at your own risk
Update 2.2   to 2.2.1 | MEGA
Update 2.1   to 2.2   | MEGA
Update 2.0   to 2.1   | MEGA
LTE (US)
Code:
Update 4.3   to 4.4   | MEGA | pCloud
Update 4.2   to 4.3   | MEGA | pCloud
Update 4.1   to 4.2   | MEGA | pCloud
Update 3.1   to 3.1.1 | MEGA
Update 2.2.1 to 3.0   | MEGA | flash at your own risk
Update 2.2   to 2.2.1 | MEGA
Update 2.1   to 2.2   | MEGA
Update 2.0   to 2.1   | MEGA
WiFi
Code:
Update 4.3   to 4.4   | MEGA | pCloud
Update 4.2   to 4.3   | MEGA | pCloud
Update 4.1   to 4.2   | MEGA | pCloud
Update 4.0.1 to 4.1   | MEGA | pCloud
Update 3.1   to 3.1.1 | MEGA
Update 2.2.1 to 3.0   | MEGA | flash at your own risk
Update 2.2   to 2.2.1 | MEGA
Update 2.1   to 2.2   | MEGA
Update 2.0   to 2.1   | MEGA
Update 1.0   to 1.1   | MEGA
Update 1.0   to ??    | MEGA | this update does not correspond to any build number I can find

Full

LTE (RoW)
Code:
Update 4.4   | MEGA | pCloud
Update 4.3   | MEGA | pCloud
Update 4.2   | MEGA | pCloud
Update 4.1   | MEGA | pCloud
Update 4.0.1 | MEGA | pCloud | re-release of 4.0
Update 3.1.1 | MEGA
Update 3.1   | MEGA
Update 3.0   | MEGA | flash at your own risk
Update 2.2.1 | MEGA
Update 2.2   | MEGA
Update 2.1   | MEGA
Update 2.0   | MEGA
Update 1.2.1 | MEGA
Update 1.2   | MEGA
LTE (US)
Code:
Update 4.4   | MEGA | pCloud
Update 4.3   | MEGA | pCloud
Update 4.2   | MEGA | pCloud
Update 4.1   | MEGA | pCloud
Update 3.1.1 | MEGA
Update 3.1   | MEGA
Update 3.0   | MEGA | flash at your own risk
Update 2.2.1 | MEGA
Update 2.2   | MEGA
Update 2.1   | MEGA
Update 2.0   | MEGA
Update 1.2.1 | MEGA
Update 1.2   | MEGA
WiFi
Code:
Update 5.0   | MEGA | pCloud
Update 4.4   | MEGA | pCloud
Update 4.3   | MEGA | pCloud
Update 4.2   | MEGA | pCloud
Update 4.1   | MEGA | pCloud
Update 4.0.1 | MEGA | pCloud | re-release of 4.0
Update 3.1.1 | MEGA
Update 3.1   | MEGA
Update 3.0   | MEGA | flash at your own risk
Update 2.2.1 | MEGA
Update 2.2   | MEGA
Update 2.1   | MEGA
Update 2.0   | MEGA | gave me some trouble when going from 1.2.1 to 2.0, had to do a system restore.
Update 1.2.1 | MEGA
Update 1.2   | MEGA
Update 1.0   | MEGA

Utilities

SHIELD Tablet USB Drivers
Code:
SHIELD Family Driver - WHQL       | Google Drive | MEGA
SHIELD Tablet Driver - WHQL (Old) | Google Drive | MEGA
TWRP Recovery
Code:
TWRP v3.0.2.2 by TWRP     | MEGA | Marshmallow
TWRP v2.8.7.1 by romracer | MEGA | Lollipop
CWM Recovery
Code:
CWM v6.0.5.2 by romracer | MEGA
SuperSU
Code:
SuperSU For CWM/TWRP/MobileODIN v2.65 by chainfire | MEGA
SuperSU For CWM/TWRP/MobileODIN v2.46 by chainfire | MEGA
The Following 87 Users Say Thank You to MidgetMob For This Useful Post: [ View ] Gift MidgetMob Ad-Free
30th December 2014, 10:27 PM |#2  
Senior Member
Thanks Meter: 43
 
More
Thanks! Wish you made this thread 2 days ago!!! I went crazy finding some of these...

Some suggestions to add based on my journey.. I have added rough instructions which need to be cleaned up.

A. I didnt know to get into the stock android recovery. I went crazy thinking my stock recovery was corrupt.. I reloaded, etc. etc. I finally found someone who set me straight.

Boot into the Boot Loader - Turn unit off. Hold down the down volume then power button.
Boot into the Nvidia Recovery - While in the boot loader select Recovery Mode. When at the "No Command" screen hold Volume Up and Tap Power.

B. I had major issues getting ADB to work when in CWM, Nvidia Recovery or PhilZ. but fastboot worked fine while in the bootloader. ADB worked fine while booted in the OS. Just didnt work while in recovery mode (trying to sideload an image).

Load Nvidia Drivers. There are two drivers that need to load with a single install base. A bootloader driver that is used for Fastboot and the ADB Composite Driver used for ADB while in recovery OR Android OS.

To install the driver:
1. Enable Developer Mode on the tablet - Go into About and Tap the Last selection 10 times.
2. Go Into Developer Mode and enable "Usb Debugging"
3. Plug the shield tablet into a USB 2.0 port
4. Go into device manager
5 Identify the device with an ! next to it. It should say shield tablet OR just a device id
6 Right mouse click and click update driver software. Select Browse my computer for driver software.
7. At the "Browse my computer for driver software" screen click Browse. Navigate to the driver folder (which you extracted from a zip) and allow the driver to load.

To Fix ADB in Recovery or Fastboot driver issues, ADB must first be working while in the Android OS - see above.
(Generally the Nvidia method will work for fastboot and for ADB while in android OS - but some times ADB fails to be recognized while in recovery) -

Fastboot:
1. While connected to the PC Boot the tablet into the boot loader. Go into FastBoot Protocol.
2. Type the command fastboot devices - if your device lists, its working. If not stay in the boot loader and goto Alternate Driver Load Method below.

ADB:
1. While connected to the PC Boot the tablet into the recovery (CWM, Philz, Nvidia). To boot into recovery see instructions above.
2. While in the recovery navigate to ADB side load for ZIP function and go into that function. The tablet should read waiting for command, or sideload zip, etc. Each recovery is slightly different but similar statement will be made.
3. Now that the tablet is waiting for an ADB command follow Alternate Driver Load Method:

Alternate Driver Load Method:
4. Go into windows device manager. Identify the device with an ! next to it. It should say shield tablet OR just a device id
5. Right mouse click and click update driver software. Select Browse my computer for driver software.
6. At the "Browse my computer for driver software" screen click Browse. Click "Let me pick from a list of device drivers on my computer".
10. UNCHECK "Show Compatible Hardware".
11. Under Manufacturer find and select the category Android. Under Model select ADB Composite Driver (while in Recovery) OR Fastboot Driver (while in the bootloader).
Profit
The Following 8 Users Say Thank You to stanglx For This Useful Post: [ View ] Gift stanglx Ad-Free
6th January 2015, 09:43 PM |#3  
Senior Member
Flag Warrington
Thanks Meter: 105
 
More
Thank you both for this! I've been going mad trying to update mine.
12th January 2015, 06:47 AM |#4  
Senior Member
Thanks Meter: 13
 
More
This does not work for me, every time I try it, it reboots to my previous rom, the PACMAN rom....

anyone know how to get by this?

**EDIT** SOLVED
For some reason I was losing my CWM recovery and would get "no command" error when attempting to go to recovery. I reloaded CWM back in, then using adb I skipped the first step "flash recovery.img" I skipped that and just did the rest. In between each I selected fastboot protocol . Unplugged the devices, then rebooted and finally I'm back to 1.2.1
12th January 2015, 02:51 PM |#5  
Senior Member
Thanks Meter: 43
 
More
Yes... this is a known issue with CWM - and it doesnt happen all the time either - which makes no sense to me, and why I have not bothered with CWM recovery partition. I will just flash boot into CWM when I need it. I never need it when I am not hope in front of my PC.

PS - the no command is the first step to getting into the Nvidia recovery.

Glad you got it worked out... Your method was exactly the same way I was able to successfully use CWM to flash a new rom.

Quote:
Originally Posted by DFA1

This does not work for me, every time I try it, it reboots to my previous rom, the PACMAN rom....

anyone know how to get by this?

**EDIT** SOLVED
For some reason I was losing my CWM recovery and would get "no command" error when attempting to go to recovery. I reloaded CWM back in, then using adb I skipped the first step "flash recovery.img" I skipped that and just did the rest. In between each I selected fastboot protocol . Unplugged the devices, then rebooted and finally I'm back to 1.2.1

12th January 2015, 04:02 PM |#6  
Senior Member
Thanks Meter: 43
 
More
Nvidia 2.1 Recovery Image
Nvidia has posted the official NVIDIA SHIELD Tablet LTE and WIFI US Recovery OS Image

https://developer.nvidia.com/gameworksdownload
The Following 2 Users Say Thank You to stanglx For This Useful Post: [ View ] Gift stanglx Ad-Free
16th January 2015, 07:16 AM |#7  
Senior Member
Thanks Meter: 30
 
More
Hi I just received my tablet..I rooted it and have custom recovery.. Im currently on the latest build so can I just flash these incremental otas as they are released in cwm?
20th January 2015, 10:03 PM |#8  
Senior Member
Thanks Meter: 98
 
More
Quote:
Originally Posted by MidgetMob

Downloads - Full OTAs
LTE (RoW)

Code:
Update 1.2.1 | MEGA

Thank you, and an FYI, the above item is corrupt on mega as only 571 MB instead of 701MB (fails archive test).
Here is the direct link to the same file from nVidia:
RoW 1.2.1 OTA from nVidia
26th January 2015, 02:37 PM |#9  
MidgetMob's Avatar
OP Senior Member
Thanks Meter: 184
 
More
Quote:
Originally Posted by mmad81

Hi I just received my tablet..I rooted it and have custom recovery.. Im currently on the latest build so can I just flash these incremental otas as they are released in cwm?

If you're on the latest build why would you flash any updates? Unless of course you're simply talking about flashing them after downgrading your android version, in which case yes you can do that.


Quote:
Originally Posted by DFA1

This does not work for me, every time I try it, it reboots to my previous rom, the PACMAN rom....

anyone know how to get by this?

**EDIT** SOLVED
For some reason I was losing my CWM recovery and would get "no command" error when attempting to go to recovery. I reloaded CWM back in, then using adb I skipped the first step "flash recovery.img" I skipped that and just did the rest. In between each I selected fastboot protocol . Unplugged the devices, then rebooted and finally I'm back to 1.2.1

By flashing the stock recovery.img you were overwriting CWM as CWM replaces recovery.img. By skipping the step to flash the stock recovery.img you combined both restoring a factory image and adding in CWM. Generally you'd just flash the CWM recovery.img right after flashing the stock recovery package.


Quote:
Originally Posted by zarish

Thank you, and an FYI, the above item is corrupt on mega as only 571 MB instead of 701MB (fails archive test).
Here is the direct link to the same file from nVidia:
RoW 1.2.1 OTA from nVidia

Thanks for letting me know, must have been a corrupted download. The link has been updated to the 701MB OTA.


The 2.1 recovery images should be up within the next few hours. 2.1 images are up.
The Following User Says Thank You to MidgetMob For This Useful Post: [ View ] Gift MidgetMob Ad-Free
27th January 2015, 04:00 PM |#10  
MidgetMob's Avatar
OP Senior Member
Thanks Meter: 184
 
More
Google Drive links updated. No need to request access anymore.
The Following User Says Thank You to MidgetMob For This Useful Post: [ View ] Gift MidgetMob Ad-Free
9th February 2015, 09:05 PM |#11  
Junior Member
Thanks Meter: 2
 
More
Might be slightly off topic or the wrong area, but does anyone have a stock Shield Emulator Skin for Android Studio? I cannot find anyone/anywhere that has made it and I am still rather new to development and so I do not know myself how to make it properly
Post Reply Subscribe to Thread

Tags
compilation, ota, recovery, shield, tablet

Guest Quick Reply (no urls or BBcode)
Message:
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes