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

[kgreen]

Hello ，do it work on NVIDIA SHIELD TV China edition？

 

[britoso]

Any way to recover after flashing TWRP

Bought a new shield tv ( 16GB/2017 )
I did not read the fine-print notes for the 1.5 nougat full android ROM (zulu99), it was trying to say that flashing TWRP will brick your device... (should have been in bold/large font/red IMO)
It said to either:
1. only boot to that recovery image, dont flash it
2. immediately flash superSU as thats what "fixes things" and allows it to boot.

I flashed the "UNOFFICIAL-twrp-3.0.2-ALL-Shields-build2.zip" recovery and was hoping to flash superSU at the next boot....bricked it.

Any way to get my device into fastboot mode now?
Tried booting while holding A and B on a USB keyboard as I did earlier, it ends up at a corrupt message and then a blank screen.

C:\Users\username\Downloads\Shield\unzipped>fastboot flash recovery recovery.img
target reported max download size of 67108864 bytes
sending 'recovery' (15140 KB)...
OKAY [  0.361s]
writing 'recovery'...
OKAY [  0.681s]
finished. total time: 1.042s


C:\Users\username\Downloads\Shield\unzipped>fastboot reboot
rebooting...

finished. total time: 0.079s

edit: Exchanged that brick, got another 2017 device. This time I unlocked,flashed system, flashed vendor, fastboot -w, and then BOOTED to this recovery.img.
Yet again its not booting into 3.0.2 recovery, and neither can I get into fastboot.
Another brick?

C:\unzipped>fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 0.392s]
booting...
OKAY [ 0.004s]
finished. total time: 0.400s

Does this recovery not work as claimed with the latest 2017 16GB Shield TV ?

update: returned the second device too.

 

[kobos311]

It may be suggested to get Nvidia Developer forums access, it's sad to see the communities either lack of need for customization of the Shield, or lack of Nvidia Hardware training...

Just a.. Nudge.

Feel free to pm me.

 

[Steel01]

Question: why is anyone using this over official? Afaik, there aren't any problems with official. If there are, they need reported and I need to go fix them.

@ comment about lack of development: Lineage is still being worked on. Isn't a whole lot of discussion here about it, but I'm still actively supporting custom rom development. Just not any derivative roms like there are for the shield tablet.

 

[britoso]

Question: why is anyone using this over official? Afaik, there aren't any problems with official. If there are, they need reported and I need to go fix them.

@ comment about lack of development: Lineage is still being worked on. Isn't a whole lot of discussion here about it, but I'm still actively supporting custom rom development. Just not any derivative roms like there are for the shield tablet.

Is there an official release for Darcy (2017) ? I only see a release for Foster (2015)
https://twrp.me/nvidia/nvidiahshieldandroidtv.html

Zulu99 (left xda) points at this thread as the only recovery for both 2015 and 2017... but this bricked two devices for me.

 

[Steel01]

Is there an official release for Darcy (2017) ? I only see a release for Foster (2015)
https://twrp.me/nvidia/nvidiahshieldandroidtv.html

Zulu99 (left xda) points at this thread as the only recovery for both 2015 and 2017... but this bricked two devices for me.

Foster and darcy are unified in everything I release. The official twrp recovery and Lineage releases both support several models. Namely here: foster_e (2015 emmc), foster_e_hdd (sata/pro), and darcy (2017 emmc). In theory the china version will boot too.

And it should be pretty hard to brick an nvidia device. Now, foster did have some *really* bad bugs earlier in relation to flashing and bootloader stuff. But I haven't seen those lately. Should always be able to use the controller to get to the bootloader and flash a new recovery and all. If something doesn't work right, report it in the appropriate thread.

 

[britoso]

Foster and darcy are unified in everything I release. The official twrp recovery and Lineage releases both support several models. Namely here: foster_e (2015 emmc), foster_e_hdd (sata/pro), and darcy (2017 emmc). In theory the china version will boot too.

And it should be pretty hard to brick an nvidia device. Now, foster did have some *really* bad bugs earlier in relation to flashing and bootloader stuff. But I haven't seen those lately. Should always be able to use the controller to get to the bootloader and flash a new recovery and all. If something doesn't work right, report it in the appropriate thread.

Do you have a link to said releases?

I had given up on nvidia shield after two bricks (never gets to fastboot/bootloader after about 20 tries...), but i may attempt it again if I see proof it works

Edit: found it https://forum.xda-developers.com/shield-tv/development/recovery-twrp-shield-android-tv-t3510456

 

[Steel01]

Do you have a link to said releases?
I had given up on nvidia shield after two bricks (never gets to fastboot/bootloader after about 20 tries...), but i may attempt it again if I see proof it works

I'm the twrp and lineage maintainer. The official releases on each site. So, for twrp, you already linked it.

I've had some issues with getting to fastboot on darcy, but that normally is due to the controllers battery being dead. Trying plugging it in for a while before trying to get to the bootloader again. Apparently it doesn't get enough power from just being plugged into to the device during boot. Once it had some charge, holding a/b worked for me every time.

 

[britoso]

I'm the twrp and lineage maintainer. The official releases on each site. So, for twrp, you already linked it.

I've had some issues with getting to fastboot on darcy, but that normally is due to the controllers battery being dead. Trying plugging it in for a while before trying to get to the bootloader again. Apparently it doesn't get enough power from just being plugged into to the device during boot. Once it had some charge, holding a/b worked for me every time.

Thanks for replying Steel01! I love TWRP on my other devices!!!
I didnt get the version with game controller, so i was getting in via a usb keyboard and pressing keys A and B.
After flashing/booting this recovery it refused to get in and complained about corruption.

Maybe it was the system/vendor ROM that caused it, but the zulu99 full android ROM is the only ROM I am interested in. Spoiled by having the same full android experience on my nexus player for the last 3 years.

 

[tuszyn]

Hi,

I'm trying to root my Shield 2017 16GB, but i seem to be doing something wrong. My bootloader is unlocked.
After i have uploaded the twrp (is it official or unofficial from this thread) to my shield and i'm rebooting into recovery:
- If nothing is connected to the shield or connected is the game pad it will start, but i have zero control. And the mouse if i connect it later after being in recovery is not being powered on as i see it.
- If the mouse or keyboard is connected during boot it will hold on the nvidia logo while going to recovery. I did wait several hours but i did not load recovery.

I did some reading but found no posts with similar problem. Can someone help me out?

I want to root because the shield is not having wifi, as the mac address is set to 02:00:00:00:00:00 and a back flash to earlier version of the original system did not help.