[RECOVERY] [UNOFFICIAL] TWRP - Shield Android TV 2017 & 2015 - All Models

[AndroidUser00110001]

Flash at your own risk!
Not responsible for any damage you may do by attempting to modify stock software!

Recovery will work on all Shield 16GB 2015, Shield Pro 2015 & Shield 2017 16GB. All models...

You need ADB and FASTBOOT to get this installed.
You can follow this guide HERE or HERE

See attachments below for download.
Update 02/01/17
Added proper device info for 2017 Shield 16GB to allow OTA updates. Should work but not 100% sure if it will.

Extract img file from within zip folder
Reboot to bootloader

Use one of the two following commands
To flash recovery
fastboot flash recovery recovery.img

To boot into recovery without flashing
fastboot boot recovery.img

---
Thanks to TWRP for making the sources available and to @Steel01 for his work on TWRP for original shield which this was ported from.

 

[Slayerkodi]

Might be a stupid question but will this be OK to use on the 1st gen 16gb version aswel?

 

[AndroidUser00110001]

Might be a stupid question but will this be OK to use on the 1st gen 16gb version aswel?

I doubt it since 2015 TWRP did not work on 2017.

 

[brandonb21]

Might be a stupid question but will this be OK to use on the 1st gen 16gb version aswel?

The files system files between 2017 and 2015 are different you can try it, you wont hurt anything, but i doubt it will work. if you do try it do fastboot boot and not fastboot flash

 

[Slayerkodi]

My laptops broke so won't be doing this anytime soon, will see if there is a way to flash twrp to recovery without a PC because as far I know android to android adb or fastboot does not work

 

[darkuni]

I'll definitely test it in a few hours when I get home.

 

[jonasgrosch]

not booting for me

 

[AndroidUser00110001]

not booting for me

4K TV?

If yes, hook it up to 1080 TV or monitor.

 

[jonasgrosch]

4K TV?

If yes, hook it up to 1080 TV or monitor.

no it'S 1080p. tried by flashing and direct booting. both will kinda flash the screen after booting, turn off the shield and reboot it after.
the short flashing screen is the only difference to my tests with the unhacked image of twrp.

 

[brandonb21]

no it'S 1080p. tried by flashing and direct booting. both will kinda flash the screen after booting, turn off the shield and reboot it after.
the short flashing screen is the only difference to my tests with the unhacked image of twrp.

your bootloader unlocked?

 

[jonasgrosch]

your bootloader unlocked?

yes of course

 

[brandonb21]

yes of course

other people in the Q&A thread are saying it works fine. try another 1080p tv/monitor and make sure your using 5.0.1 non developer image on your 2017 shield

 

[jonasgrosch]

other people in the Q&A thread are saying it works fine. try another 1080p tv/monitor and make sure your using 5.0.1 non developer image on your 2017 shield

tried with another screen. nothing changed. still not working

---------- Post added at 10:25 PM ---------- Previous post was at 10:18 PM ----------

tried with another screen. nothing changed. still not working

nevermind. got it working by disconnecting usb connection to my pc right after executing the boot command.

 

[AndroidUser00110001]

Are all the partitions showing up in TWRP that should be? I never put TWRP on my 2015 Shield Pro so not sure what should be showing up.

On my 2017 I can only write to the TWRP folder using the USB cable connected to my PC. I tried to put in a USB stick but TWRP did not recognize it nor does it recognize External Storage.

I have USB hard drive formatted for internal storage so not sure if that is why I don't see any partitions in TWRP and can only write to the TWRP folder.

I am about to build TWRP from source and was just wondering what partitions shows up from more experienced users so I can adjust the TWRP settings so more partitions show up if that is the cause....

 

[brandonb21]

Are all the partitions showing up in TWRP that should be? I never put TWRP on my 2015 Shield Pro so not sure what should be showing up.

On my 2017 I can only write to the TWRP folder using the USB cable connected to my PC. I tried to put in a USB stick but TWRP did not recognize it nor does it recognize External Storage.

I have USB hard drive formatted for internal storage so not sure if that is why I don't see any partitions in TWRP and can only write to the TWRP folder.

I am about to build TWRP from source and was just wondering what partitions shows up from more experienced users so I can adjust the TWRP settings so more partitions show up if that is the cause....

I just got an email from nvidia and they processed my rma and now waiting for a tracking number i doubt il see mine till next week or i would help you out.

 

[gunner007dc]

I was able to unlock the bootloader, enable USB debugging.

I tried flashing the TWRP image, however attempting to boot into recovery gives the sad little android man with the red exclamation (NO COMMAND)

If I attempt to just boot the image I see the TWRP splash screen, then a few seconds later the system reboots.

 

[brandonb21]

I was able to unlock the bootloader, enable USB debugging.

I tried flashing the TWRP image, however attempting to boot into recovery gives the sad little android man with the red exclamation (NO COMMAND)

If I attempt to just boot the image I see the TWRP splash screen, then a few seconds later the system reboots.

try disconnecting the usb cable going from your pc to your android box right after hitting enter after typing "fastboot boot twrp.img"

seems to be a bug. make sure it downloads the image all the way before disconnecting.

 

[gunner007dc]

Yep that seemed to do it. I flashed TWRP already, just when I typed adb reboot recovery, you just have to disconnect the USB. Then it booted into TWRP just fine.

Stupid question, but is it best practice to just install the dev image + SuperSU at this point. It's what I'm currently running, but didn't know if it was just better to run stock image + SuperSU. (or maybe dev is needed for root)

 

[brandonb21]

Yep that seemed to do it. I flashed TWRP already, just when I typed adb reboot recovery, you just have to disconnect the USB. Then it booted into TWRP just fine.

Stupid question, but is it best practice to just install the dev image + SuperSU at this point. It's what I'm currently running, but didn't know if it was just better to run stock image + SuperSU. (or maybe dev is needed for root)

use the retail one, the dev image can run beta drivers such as graphic drivers that may or may not cause issues at some point. and the developer image dosent get ota updates.

 

[yojoe600]

Was able to root mine as well by pulling out the usb cable while booting into twrp. Thanks Guys!