Database Users

[Solved] I'm afraid I really bricked my Shield TV 2015

Hi everyone,
As mentionned in the title I'm afraid I bricked my Shield TV (model 2015, 16GB).
It was previously running StockRestyle 3.0 Marshmallow (from zulu99: https://forum.xda-developers.com/shield-tv/development/rom-t3321787) and all was fine with it.
But since Nvidia announced Nougat for the Shield TV, I wanted to give it a try.
Thus, I tried to flash the official recovery images from Nvidia, but I think I made the mistake to flash the Nougat version instead of the Marshmallow one.
So, here is what I've done:
- I copied the official Nougat recovery images on my PC in my adb folder
- I ran the flash-all.bat
- it started all right, but was then stuck for several minutes
- the shield TV rebooted itself but was stuck on the Nvidia logo
- after several minutes without change nor messages on the command, I quit the command terminal.
Later, I tried to start the process again without success.
Now, I can have access to the bootloader using the hardware procedure (long-press on the power button).
Unfortunately, it says on the top "Production mode: fused" (see the attached pictures).
From the bootloader, I tried "Forced recovery" -> I got a black screen -> Fail
I also tried the "Boot recovery kernel" -> I got the screen image with the android robot down with an warning symbol (see the attached pictures)
I tried adb and fastboot without success.
When I reboot the bootlaoder, with the shield connected to my PC with an OTG cable, the shield is detected but there is a warning message on my PC (it's not well recognized).
Also, "fastboot devices" returns nothing.
Technically, the shield is l still under warranty since it's less than 2 years old, but I'm afraid this "Production mode: fused" message would void it!
Any similar situation or suggestion?
Thank you in advance and have a nice day.

Hi, that production mode: fused is normal. I checked and I have it. I think it is there since I unlocked the bootloader. I run Full Android Nougat from @zulu99 without issues.
Do not keep trying to flash things just to flash. While you be able to boot into bootloader you can recover it (remember this) but is also true that if you mess with the bootloader you can brick your device. You're just soft bricked not hard bricked.
First, post the complete version of the bootloader, in the screenshot I can't see the whole version.
For later (do not attempt to flash anything until we go thru some checks):
Try with another known working USB cable and/or reinstalling fastboot drivers. And do not use flashall.bat, you will do it command by command.
Enviado desde mi Moto X mediante Tapatalk

That's what happens when you don't follow directions

Here is a picture with the complete version of the bootloader.
I followed quite well the instructions a year ago when I was trying to evaluate the pros and cons of Stock ROM, Stock Restyle and Full Android. Unfortunately @zulu99 posts have been closed since then.
Thus I forgot I had to revert back to standard Marshmallow first ;-(

I also tried two others USB OTG cables.
With on of them I managed to get "fastboot devices" recognizing a device, and I don't have this warning message on my PC (it's not well recognized) when starting the bootloader.
What should I do next?

Problem solved!
Since I guess the issue was mainly due on the suddenly defective OTG cable (it worked in the beginning of my last try, since I managed to flash some parts), I started the procedure again with with the official recovery 5.0.2.
- I started the bootloader using the HW method: long-press on the power button during powering up, until the bootloader appears
- Then,
* fastboot -w
- Then, again, I had to start the bootloader using th HW method
- Then, I followed most of the points described in the flash-all.bat files (except the adb commands)
* fastboot flash staging blob
* fastboot flash boot boot.img
* fastboot reboot
- Again, I had to start the bootloader using th HW method
- Then,
* fastboot flash recovery recovery.img
* fastboot flash system system.img
* fastboot flash vendor vendor.img
* fastboot reboot
- and voilà: I got Nougat running. Then the time it took me to enter my email credentials and so on, the OTA update to 5.1 was downloaded and ready to install.
A few minutes and a reboot later, I have the latest version running.
Thanks guys.

Your issue was the USB cable, if there is no good connection the flash can be incomplete thus corrupted. It is better to run the commands manually one by one so you know if it was successful on each flash or identify where it got stuck. Your lucky it didn't fail while flashing blob.
Probably failed after the boot flashing and fastboot reboot.
I suggest you get another USB cable, always use high quality cables. The internet is flooded with Shield TV users with TWRP, flashing issues and bricked devices because of a bad USB cable.
Enviado desde mi Moto X mediante Tapatalk

I tried doing the same thing and i got errors when flashing system and vendor files. It says that data is too large.

Shield tv is not working

Shield has Android TV 2017
I am following this process and the shield is not working.
—–
fastboot oem unlock
twrp boot (fail)
Infinite reboot
(controller a,b key pushing
power cable in)
hw mode bootloader connect to pc
(pc recovery img “fastboot-all.bat” Execution)
error devices not connect after install 2 things finished
—
shield tv Does not wake from sleep mode
pc to connect (pc devices manager display others-apx)
hw mode is not working
How can I recover it?

If your shield TV doesn't boot correctly, fastboot-all.bat won't work because you need to have adb working.
You should indeed rather follow the instructions given on Nvidia website, i.e. for Shield TV 2015 16GB with Marshmallow or newer installed:
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
Before that, be sure you use a good quality USB OTG cable.

Sounds like you can't boot into fastboot or bootloader mode.
If you can't, it means that you are hard bricked.
If you already had latest Nvidia experience version 5.1, there was no need to reflash the whole recovery image, PLUS you don't mention what recovery image you flashed.
To sum up your error was eather a bad usb cable (this a very known issue now, shield is picky) AND/OR wrong blob (which is the bootloader and it comes in all nvidia recovery image packages) flash.
What makes the device brick is a corrupted bootloader.
If bad USB and fail while flashing blob (which again is the bootloader), it gets corrupted.
If wrong blob flash (by using one that is not for you device model OR when attempting to downgrade to MM or lower bootloader), it gets corrupted.
Moral of the story:
Never mess with the bootloader a.k.a blob if you dont know what you're doing.
I know there are many hard bricked users around so better start reading. Take your time and make sure you understand all the instructions and also the pros and cons of the restore/unbrick method.
NOTE: just so you know next time for Shield TV 2017 , when you unlock bootloader and flash TWRP recovery or custom firmware you must root, because root with SuperSU disables some checks Nvidia run at boot. If you don't root, then your Shield will be stuck at boot.
- Sent from my Tapatalk Hub -
If I helped hit the Thanks button. Follow Me! ~ Buy Me a Coffee ~ Full Android for ShieldTV and Nexus Player

SOLVED - Fastboot with no adb - any help?

Hi,
rooted 2017 16GB ShieldTV.
Unlocked bootloader.
TWRP was not installed just used to boot once and installed SuperSU (I feel like an idiot learning this only after)
Played with it - removed some critical system apps, and also managed to disable USB debugging (this only as I thought that TWRP was installed - and felt safe to do ANYTHING)
Now - boot to fastboot happens, but there is no adb.
Any saving method?
Original recovery gives options to ADB sideload and USB update.
Tried to use this by putting official Nvidia stock image on USB and but it reports signature failed, and refuses to flash.
Any help?
Thanks guys

SOLVED
Writting this as soon as I could cool down.
Situation:
- Shield ATV 16GB 2017. SW Nougat 5.2
- Unlocked bootloader (every boot gives that safety warning)
- System bootloop on Android circles animation (managed to root it previously and removed some critical apps by mistake)
- NO USB debugging
- NO custom recovery (as process for rooting only used TWRP to flash SuperSU, nothing else)
- Entering fastboot possible only by hardware method (controller connected by USB, hold A+B buttons while Shield is plugged off 10sec, then plug Shield in. Two short vibrations of controller and fastboot screen appears.)
However - NO adb in fastboot. (pinging with adb devices gives NO response). Only option that works is entering official recovery which gives options for adb sideload or update from USB. However - no zip file is accepted due signature check (and I tried tons of them)
Tools
1. Windroid
https://forum.xda-developers.com/showthread.php?t=2499926
2. Proper TWRP build
http://nvidiashieldzone.com/download/twrp-3-1-1-1-shield-tv/
3. Custom flashable rom (I used Lineage OS for Shield - lite and without Gapps - to speed up booting into environment that works). Put it onto USB drive
4. Oficial Nvidia recovery image (https://developer.nvidia.com/shield-open-source)
5. Minimal ADB and Fastboot (http://nvidiashieldzone.com/download/minimal-adb-and-fastboot/)
6. Nvidia controller plugged into USB port next to HDMI
7. Male-to-male USB cable (for ADB)
8. USB mouse
Process
1. Start Windroid and choose device (Nvidia, Shield TV)
Windroid will automatically download resources in Data folder (incl. TWRP that did not work for me), so dont block it with firewall.
2. Download proper TWRP from link above, and replace the one in Windroid Data/Recoveries folder using same name (Recovery1.img). You will notice difference in sizes. One that Windroid downloads is 25mb, while the one from link is ~ 16mb.
3. Enter fastboot on ShieldTV using hardware method (above mentioned with A+B buttons)
4. Now quickly In Windroid click button Refresh - and status will be updated to Fastboot
5. Then again in Windroid - click Flash TWRP and accept safety questions.
6. After successful flash - reboot into TWRP (here you need USB mouse - so you can unplug Nvidia controller, and plug mouse)
7. In TWRP - Choose Install - navigate to external USB and select flashable zip (Lineage ROM as above)
8. Once booted - enable USB debugging again. (you could be prompted on the Shield TV to allow your PC as debugging device, if so, say yes)
Getting back to full stock ROM with TWRP and unlocked bootloader
1. Install Minimal ADB and Fastboot you downloaded
2. Extract boot.img, system.img and vendor.img from Nvidia stock recovery image (leave other files out), and place these files into Minimal ADB and Fastboot folder (it is in Program Files x86)
3. While on (in LineageOS) connect Shield TV with PC using male-to-male USB cable
4. Start Minimal ADB from destkop icon and run following commands (commands are only in italic)
adb devices (checks if device is online. Its a must to proceed)
adb reboot bootloader (reboots to fastboot)
fastboot flash boot boot.img
fastboot flash system system.img (will take longer as its a big file)
fastboot flash vendor vendor.img
Once finished - reboot to TWRP, plug in USB mouse (instead of controller) to navigate, and perform Factory Reset.
If you wish to root you can do it via TWRP (which is what I did, flashing SuperSU previosly downloaded to USB)
Thats it - you are back from the dead!

Post updated - with process how to go back to stock

Thanks for this guide. It saved my ass!

Hi phnikola
thank you very much for your super instructions.
With this tool I could bring my TV Shield 2017 back to life, which got stuck in the Boot Animation.
I thought it was a trash can case, also contacted NVIDIA support to see what they were saying.
So I can also send the possible to me for the purpose of repair saved, thanks to you!!!!!!!!!!!!!!!!!!
Greetings Akki

NVIDIA shield tv 2015 stuck after flash-all.bat

After updating my shield tv to Oreo I successfully downgraded to 6.3.0 so that I could play PUBG mobile using octopus app. Well now that PUBG mobile detects the octopus app and bans players for using the app I wanted to go back to Oreo. I downloaded the recovery image 7.1.0 and got my device recognized by my pc windows 10. Ran the command adb devices and my device was recognized. I proceeded to run the adb Fastboot devices and my pc recognized my device. I then ran the adb reboot bootloader command. Then I ran the flash-all.bat command. This is where I’m stuck. My device is stuck in bootloader. My pc no longer detects my device when I run the adb devices or Fastboot. I am able to boot to recovery kernel on the shield. I have tried to apply update from adb but I think I’m not getting the correct files. If I select apply update from adb My PC does recognize my device as sideload. No Fastboot devices found. Please help me get my device back to Oreo or just operating.

Fix it
Hi did you manage to fix your shield as I have the same problem

I bricked my shield tv
I bricked my 2015 16gb shield tv. Powers up then turns off immediately

You must install the USB Drivers from NVIDIA, there is a separate driver that your computer needs to communicate while in fastboot/bootloader. So just because ADB works, does not mean Fastboot will work.

I have repaired several SHIELD TV 2015,And I can add shield TV 2015 storage。32G /64G /128G。Just need to replace EMMC.
https://item.taobao.com/item.htm?spm=a1z38n.10677092.0.0.594c1debq5W8P3&id=576292085112
The link above is to buy the chip and repair the machine by oneself.
https://item.taobao.com/item.htm?spm=a1z38n.10677092.0.0.594c1debq5W8P3&id=576414610358
This link needs to be sent to China to replace FLASH chips.

My NVIDIA is dead ?no os no fastboot mod no adb and no recognize by my PC for install the drivers i have just the NVIDIA boot logo who freeze after booting

How do I Activate USB debugging

Hey guys, I know this isn't super active anymore, but I tried looking and tried posting elsewhere, and I can't find the answer I need. I'm sure it's something super simple I've overlooked.
I was gifted a 2015 Nvidia Shield TV Pro that was never used, so when I turn it on it gets stuck forever asking for my google login and won't proceed (like this thread here).
I can access the fastboot menu on the unit, and I've installed the PC drivers - BUT
When I open command and type "adb devices" it shows no devices connected.
I'm TOLD this is because I need to activate USB debugging on the unit, but how can I toggle on the USB debugging if I can't get past the google sign-in for a first-time set up?
Am I approaching this wrong?
PLEASE help!

Hello, I have exactly the same issue.
I would be really grateful if someone could help us.

i think you must set your SHIELD in FASTBOOT mode and after flash the stock firmware from https://developer.nvidia.com/gameworksdownload (you can't set FASTBOOT mode from ADB because of the wrong login)
to set fastboot mode look here : https://nvidia.custhelp.com/app/ans...invoke-the-android-fastboot-menu-on-shield-tv

Thanks conduisant! It helped.
I have spent some time to flash new recovery:
How far I was able to proceed:
I downloaded ADB Fastboot drivers
I downloaded recovery image (nv-recovery-image-shield-2017-atv-8.2.3)
I connected Nvidia Shield 2017 (model: P2897) with USB-A-to-USB-A cable to the PC
I was able to see "unknown device" so I installed ADB drivers (SHIELD_Family_WHQL_USB_driver_201801)
In device manager I can see my shield (as a Android Bootloader Interface)
I can access fastboot (pressing A+B on controller during turn on of shield)
I opened CMD and type "fastboot devices" - press enter - I can see my device is listed "03xxxxxxx fastboot"
I am able to execute "fastboot oem unlock", so bootloader is unlocked
I am able to write recovery image by using following commands written in instructions:
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 oem lock
fastboot reboot
(no errors, everything was "OKAY")
But after the device restart , I can post only until the nvidia logo and that is it. Unfortunately I do not even know which was the original (stock) version of system in nvidia shield pre-installed. I tried to flash several versions of recovery images, but nothing helped. I can still see only nvidia logo :-(
But what I noticed, my Fastboot looks pretty different. I do not see my bootloader version, also some options are missing (lock bootloader, unlock bootloader etc.)
I also tried another options - boot recovery kernel, safe mode, but only nvidia logo every time.What is strange, when I turn-on the device, the Fastboot is automatically booted (I do not even hold A+B to initiate fastboot) I need to select continue.
So now I am not even able to try login into the shield anymore. I guess I already bricked the device :-(

what you have done is pretty correct !
Shield seems to be hard bricked, you can also try to flash TWRP + lineage OS ROM only to see if the SHIELD still not boot...i've no other idea

Thank conduisant for your effort!
Unfortunately, I am not able to boot into the TWRP.
I tried to flash TWRP what I have found here on forum:
UNOFFICIAL-twrp-3.0.2-ALL-Shields-build2.zip
But no success.
I tried to also flash official TWRP:
twrp-3.2.3-0-foster.img
But also no success.
I do not know which offical recovery to flash before LineageOS ROM (or it does not matter?)
Unfortunately, for some reason my gamepad in Fastboot stopped working (gamepad is connectied via USB to the shield, closest to HDMI port)
It just rumble when Fastboot booted and blinks blue led. I tried to charge gamepad - or - another nvidia shield gamepad but it does not work.
Also USB keyboard does not work. Looks like the USB port does not work properly anymore, so I am not able to click "Continue" in fastboot anymore to post at least until nvidia logo.
Luckily, the bootloader is still unlocked, so I am able to flash anything but I have already lost my mind.
I need another coffee and one full-day of meditaion.

i've got 2017 SHIELD, and i've flashed this TWRP last days + this LINEAGE OS : and all working good
TWRP = https://eu.dl.twrp.me/foster/twrp-3.7.0_9-0-foster.img.html
LINEAGE OS = https://download.lineageos.org/foster
when USB debugging is ON, only one USB port is activate for USB devices (keyboard for example) : it's the port near HDMI, the other port (near fan grid) is for ADB connection for the PC