[RECOVERY] [OFFICIAL] TWRP for Shield Android TV

[Steel01]

Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.



DOWNLOAD:
Most devices can be updated quickly and easily within TWRP if you already have version 2.8.4.0 or higher installed
1) Download the latest version from our website on your device
2) Reboot to TWRP
3) Hit Install and tap the "Images..." button in the lower right
4) Browse to the location of the TWRP image on your device and select it
5) Select recovery from the partition list and swipe to flash
OR:
You can find more information and download links on our website.
SHIELD Android TV 2015/2017 direct link
SHIELD Android TV 2019 direct link

BUGS:
If you have found a bug, please consider posting it to our github issues log. It's pretty much impossible for us to keep up with the more than 40 threads that we have for the devices that we "directly" support. If you have a significant problem that cannot be answered in this thread, contact us via our website, or find us in our IRC channel below. If you see someone that's struggling, feel free to point it out to us. We need your help to help us keep track of all of our devices! Thanks!

SUPPORT:
Live support is available via #twrp on Freenode with your IRC client or just click this link.

 

[Steel01]

NOTES:
Due to the lack of a touchscreen on the device, you will need to have a mouse plugged in. A keyboard should work as well for typing input.

KNOWN ISSUES:
Cannot display at 4K. There have been a few reports that some 4K TVs wont display this recovery, but others will properly switch to 1080p mode and work just fine.

Build and device page will be up shortly. Got some fun recursive references going on here. Build is live.

Anyways, I know, I know, it's about time, right? Just haven't had too much motivation to work on this device. As powerful as it is, it's been a bit of a pain to work on. True built from source custom roms are still crippled due to hdmi audio not working, etc. But afaik, this recovery is 100% working, no problems. But if you find anything wrong, please let me know here.

 

[Mogster2K]

Hmm, it seems adopted storage still isn't getting mounted correctly. The "Micro SDCard" selection is only 15 MB. Also, it's not picking the correct time for backups. The terminal shows two errors when typing "ls -l":

__bionic_open_tzdata: couldn't find any tzdata when looking for CST6CDT,M3.2.0,M11.1.0!
__bionic_open_tzdata: couldn't find any tzdata when looking for posixrules!

 

[Steel01]

Hmm, it seems adopted storage still isn't getting mounted correctly. The "Micro SDCard" selection is only 15 MB.

Really? Blast... I pulled the same fix that worked on the tablet, but didn't actually test it on this platform. Guess I'll have to do some tinkering. Not a whole lot of time for a couple weeks, though.

Also, it's not picking the correct time for backups.

I see that on my other devices too. Not certain how to get the correct time, if possible. I'll look into it later.

The terminal shows two errors when typing "ls -l":

__bionic_open_tzdata: couldn't find any tzdata when looking for CST6CDT,M3.2.0,M11.1.0!
__bionic_open_tzdata: couldn't find any tzdata when looking for posixrules!

I've seen this on my other devices as well. No idea what's up...

 

[snipz]

Damn still no 4k suppport

 

[vegeta340]

I have shield connected to yamaha amplituner and then to 4k TV, no issues with TWRP.

 

[TheUndertaker21]

Does this support 4k TV finally?

 

[banderos101]

Does this support 4k TV finally?

Doesnt look like there is.

But it seems like vegeta has stumbled upon one way for now, indicatative that the issue may be from the direct hdmi connection from the shield to a 4k tv. Maybe theres a cheap 4k compatible hdmi splitter/switcher/combiner out there or perhaps one you own already, that can be tested depending on your urgency for twrp

 

[Ichijoe]

Alas this doesn't even work on my Monitor with an HDMI to DVI converter. Actually it does work, once it finishes booting up that is. But for TWRP it's a standard Black Screen then.

Is it really that hard to code TWRP to output a 4k.. barring that a locked 1080 signal? This all said it worked very well on my Old Man's FHD LG TV have the command, and a moment latter it was there. So installing SuperSu successfully, and a full boot latter I packed it back up, and took it home with my again.

 

[jaydee 77]

EXPERIENCE UPGRADE 5.0 (Android 7.0 Nougat)

Does v3.0.2-0 work with SHIELD EXPERIENCE UPGRADE 5.0 (Android 7.0 Nougat)?

 

[MysteryIII]

Does v3.0.2-0 work with SHIELD EXPERIENCE UPGRADE 5.0 (Android 7.0 Nougat)?

Update isn't released yet. So nobody can say for sure.

 

[Ichijoe]

From what I thought I knew about Android, the Recovery Partition is fully independent of the OS One. This said from what I read about Nougat, where we used to just have the One OS Partition, from Nougat going forward we'll now have Two. An active One, and the other that will be used for active updates. This should be interesting for those on low spec Devices such as the 16Gb Shield. As the Android OS has traditionally taken about 4Gb of Storage. So can we expect that to double now?

About the only thing that could theoretically happen is that the Update overwrites the Recovery Partition. But I don't think this will be a problem.

But, to pass along some helpful info which I made an enquiry about in a different Thread. Once you have flashed TWRP as your recovery, and as far as I can tell you have to have it installed, and not merely loaded from a fastboot command line. You can simply install SuperSU again. (And you will have to do that again anyway.)
Which could be a problem if your like me, and stuck with just the One 4k (2160p), TV. Then this is a more round about way to reinstall SuperSU again after the Update.

Just do the following:
Login to your shield via ADB..

$ adb reboot recovery
$ adb shell
$ twrp install /sdcard/SuperSU.Zip

 

[Steel01]

The a/b system partition thing is only being done on new devices. We will not repartitioned and lose space due to the upgrade.

The current twrp works just just fine with N ROMs. The worst thing you will see is a couple errors saying a log command isn't found when installing the update. This happens on all ROMs, all devices. It isn't fatal and can be safely ignored. Other than that, everything will continue to work as before. Flashing, backup/restore, etc. No problems at all. No, I haven't seen the official update yet, but I've done some work with cm-14.1 which is the same core stuff.

 

[brandonb21]

The a/b system partition thing is only being done on new devices. We will not repartitioned and lose space due to the upgrade.

The current twrp works just just fine with N ROMs. The worst thing you will see is a couple errors saying a log command isn't found when installing the update. This happens on all ROMs, all devices. It isn't fatal and can be safely ignored. Other than that, everything will continue to work as before. Flashing, backup/restore, etc. No problems at all. No, I haven't seen the official update yet, but I've done some work with cm-14.1 which is the same core stuff.

this dosent work at all on the new shield. just reboots after flashing then it reflashes stock recovery

 

[Ichijoe]

Well I guess the question is does the "new" Shield TV (Slim), actually count as a "New Device"? That supports Google's new a/b System?

 

[brandonb21]

Well I guess the question is does the "new" Shield TV (Slim), actually count as a "New Device"? That supports Google's new a/b System?

so fair the only thing that has been discovered with this new "model" is the usb identifiers have changed abit.

 

[Steel01]

Hmmm... Kinda surprised it doesn't boot at all. Maybe the dtb and kernel changed enough that the newer bootloader balks at them. I won't have one in hand until probably next week. Once I do, I'll make something work.

Previously I would have said no, darcy doesn't have a/b updating. But... The more I look through the code drop, the more it looks like it actually does. But I won't be able to confirm until I got my hands on it.

 

[brandonb21]

Hmmm... Kinda surprised it doesn't boot at all. Maybe the dtb and kernel changed enough that the newer bootloader balks at them. I won't have one in hand until probably next week. Once I do, I'll make something work.

Previously I would have said no, darcy doesn't have a/b updating. But... The more I look through the code drop, the more it looks like it actually does. But I won't be able to confirm until I got my hands on it.

is their anything i can do to help you in the time being to help development along?

 

[brandonb21]

Hmmm... Kinda surprised it doesn't boot at all. Maybe the dtb and kernel changed enough that the newer bootloader balks at them. I won't have one in hand until probably next week. Once I do, I'll make something work.

Previously I would have said no, darcy doesn't have a/b updating. But... The more I look through the code drop, the more it looks like it actually does. But I won't be able to confirm until I got my hands on it.

heres the 2017 5.0.1 image if this helps http://ota-downloads.nvidia.com/ota...-full_ota-1749719_832.2408.20170116175313.zip

 

[Steel01]

Well, I'm still waiting on a darcy. I hear it's supposed to ship this week. Sorry for the wait, but it's hard to do any development without the device. That or the update for the original 2015 one I've already got. Once I get my hands on something to test with, I should get something out pretty quick.

And yeah, the ota link helps. I went and compared a bunch of stuff and I think I have it ready to go, just can't test it yet.