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.

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

Shield TV Pro 2015 - Can't connect through fastboot USB, suggestions?

(For the full story, check this thread over at nVidia support forums: https://forums.geforce.com/default/.../shield-pro-2015-can-t-get-it-up-and-running/)
Long story short, I'm trying to flash my nVidia Shield TV Pro 2015 with v7.0.2 recovery image, because I could not get past the initial nVidia "looking for experience upgrade", and thus not use the device at all.
I unlocked bootloader by fastboot, rebooted, flashed staging and boot.img, reboot (like flash-all.bat and nVidia Instructions says), but after the reboot neither of my two Windows 10 computers can recognize the Shield in fastboot mode as a USB device.
I've tried:
* Uninstall/ reinstall drivers through Device Manager
* Registry "hack" for disabling a check performed by Windows for USB devices (https://forum.xda-developers.com/android/general/fix-unknown-usb-device-device-t3375320)
Any ideas on how to successfully connect to it through fastboot, in order to finish the flashing process?
Are there other ways of restoring it, like putting a image to a USB stick, go to recovery?

Soft bricked phone: looking for advice

Hi
I would like to ask for some advice.
I've recently soft bricked my MI2S. I can boot to recovery (TWRP 2.8.1) and fastboot. The phone isn't recognised by Windows or Ubuntu, so I can't flash anything with fastboot. Actually, fastboot, adb or MiFlash don't detect the phone. I've tried to use a USB stick with an OTG cable, but TWRP doesn't detect the USB stick. If I boot to system, it stays on the MI logo (I can wait a full night, it won't change).
My question is, do I have a problem with my USB port? I'm equipped to solder a new one, if necessary. Or is my connection problem due to another reason? I wouldn't want to go through soldering if it is for nothing. Especially, when I started to mess up with the phone, it was locked with a different MI account (it was my wife's account, but it took me a few days to connect the dots together), and I couldn't connect with MiFlash, adb or fastboot either.
The steps I did to get it soft bricked:
Flashed TWRP 2.8.1 with fastboot
Rebooted to recovery
Rebooted to MIUI (a few times)
Attempted to flash TWRP 3.5.0 (my memory fails a bit there, I think I did it via fastboot)
The last didn't work because I'm still on TWRP 2.8.1
And I can't add any more zip file to flash via recovery, nor can I use adb sideload or flash with fastboot.
Any advice or comments are more than welcome. You may just have an idea that I didn't think of.
Regards
Matt

Quick update:
I don't know if you would agree, but I can't see my issue to be a software one (the device not being recognised)
I've ordered a USB port directly from China and I'll see if I can unbrick the phone from that point.

It's great that you can still access to recovery and fastboot.
First, I advice you to back up your data.
If you cannot use adb sideload or flash with fastboot.
Try in fastboot mode
- fastboot erase cache;
- fastboot erase system;
- fastboot erase userdata.
See if that can solve your issue.

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