[Shield Android TV Q&A, Help & Troubleshooting] Riverphoenix:
I wanted to share my experience in reviving my 2017 Shield Pro 500gb. I was at the point that it wouldn’t even turn on and all I would get is a black screen then after some time I would get 3 green flashes then the Shield would power off.

I was at the stage in which I couldn’t even backup the device and starting from scratch seemed very unlikely from my reading online. I had tried so many different things before I finally came to what follows.

Things I used

Samsung Evo 500GB

Nvidia shield TV pro files (someone kindly uploaded online) https://xdaforums.com/t/nvidia-shield-tv-ssd-done.3402580/page-2#post-67426622

nv-recovery-image-shield-atv-pro-7.2.3-dev_rooted https://drivers.softpedia.com/get/g...Android-TV-Pro-Developer-Firmware-7-2-1.shtml

DD command line using Linux ( you can use Windows)

Rufus

OTG cable

ADB and Fastboot Drivers

SATA Adapter

First up I dismantled the Shield which although not overly complicated, you just have to be careful with the wires as the must be unplugged and SATA connector from the HDD.

So the HDD being completely dead I decided if I was going to successfully revive the shield I would use a SSD instead. I plugged the SSD into my windows laptop and reformatted it to a GPT partition scheme with a FAT32 filesystem using Rufus.

Now I would switch from Windows to Linux (I know you can do this with windows but all my previous successes have been through Linux) and find the folder containing – start.bin and end_976574630.bin and open your terminal. Plug your ssd into your linux running computer. Here I would use the command $sudo su and then the command fdisk -l to find what letter your drive is identified by. Let’s say the drive is identified as sdd.

Next write the command $dd if=start.bin of=/dev/sdd bs=4M

This process can take around 15 minutes give or take. Once the process has been completed enter $dd if=end_976574630.bin of=/dev/sdd seek=976574630. This will not take as long as the previous process. Make sure that you can see no errors once the process is complete and safely eject the drive.

Now it’s time to reassemble the Shield making sure again not to damage any wires and everything is correctly reconnected.

After I plugged it bag into power I just let it sit trying to boot for about ten minutes before turning it off.

For the next part I used Windows and you need to make sure you have the ADB and fastboot drivers installed on your computer. Find the folder named nv-recovery-image-shield-atv-pro-7.2.3-dev_rooted and open terminal, PowerShell etc here.

Fastboot reboot the hardware way

- Disconnect power cable

- Connect Shield to a computer using an USB cable connected to the micro USB port of the Shield.

- Connect power cable to SHIELD

- As soon as the green LED turns on -BUT NOT BEFORE- hold down the power button

- Count to three, then immediately release the power button

- i.e. one-one thousand, two-one thousand, three-one thousand.. LIFT!

- You should now see the fastboot menu on the screen.

To confirm the device is in fastboot mode type the command $fastboot devices and you should see your device listed. Now one at a time type the following commands.

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

Your Shield will begin to boot and will probably appear to stay on the four dots that turn into the Android logo for a little while. Give it 15 min and then unplug the power and repower the Shield. Now you will see your past boot and next setting the language and internet settings. Once you’ve done that you will be asked for Google credentials and the moment you’ve been waiting for the Nvidia Shield home screen. When I did it there was an update for 8.0 available which I did and everything worked fine. I then noticed an update for 9.0. Do not do this you will be back to square one which I found the hard way. For some reason it seems 8.0 that is compatible for this Shield model.

I just want to say a lot of this in formation has come from sources and articles I have read and have put together to suit my needs.

Big thanks to Tilator from XDA Developers and to Yaneca XDA Developer