Having trouble accessing nVidia Shield TV fastboot? If so, look here - Shield Android TV Q&A, Help & Troubleshooting

For the last 5 or 6 hours i've been pulling my hair out trying to get into fastboot on my Shield TV.... Everyone says it's all about timing... I say - 'pay no attention to what nVidia tell you to do to ENTER fastboot'.
I did this by accident and have been able to do it again and again on my 16gb and 500gb. The secret is - DON'T leave HDMI connected.
This should work on their other devices too.
1. Unplug EVERYTHING from your Shield.
2. Connect ADB cable
3. Turn power on (with cable disconnected)
4. Connect power cable to Shield
5. Count to 2 THEN hold down power button
6. Profit?
Feel free to connect HDMI now.

sloshedpuppie said:
For the last 5 or 6 hours i've been pulling my hair out trying to get into fastboot on my Shield TV.... Everyone says it's all about timing... I say - 'pay no attention to what nVidia tell you to do to ENTER fastboot'.
I did this by accident and have been able to do it again and again on my 16gb and 500gb. The secret is - DON'T leave HDMI connected.
This should work on their other devices too.
1. Unplug EVERYTHING from your Shield.
2. Connect ADB cable
3. Turn power on (with cable disconnected)
4. Connect power cable to Shield
5. Count to 2 THEN hold down power button
6. Profit?
Feel free to connect HDMI now.
Click to expand...
Click to collapse
I wish this was posted a month ago when I bricked my SATV (Shield Android TV) by updating to ROM 2.1. I could not get to recovery mode. It took 3 weeks to get my SATV replaced.
The replacement SATV could not get into recovery mode after OTA update to 2.1. I reverted to ROM 1.3 and do not have any recovery mode issue since.
This approach (disconnecting HDMI) could debrick many SATVs which could not boot to Android or other OS and failed recovery mode.

Thank you very much for the useful tips.

Related

[Q] Nexus 7 2012 does not charge, does not boot to bootloader - please help

Hi guys,
I have a Nexus 7 2012 which has become almost completely unresponsive.
Possible cause:
Last thing I remember is that I had it in my pocket and when I looked at it later - it was in bootloader mode. I pressed the power button and since then I have not been able to wake it up.
The device does not charge because I cannot feel the battery to be warm after a whole night of charging. I cannot turn it on no matter how long I keep the power button presses. I have tries two minutes on the clock. I cannot enter into bootloader by pressing power and volume down, even though I keep pressing them for two minutes also on the clock.
So I removed the back cover and pulled out the battery connector. Reconnected but there has been no change in condition.
The device shows the following signs of life.
When the battery plug is pulled out I connect it to my Windows 8 PC via the USB cable and I push on the Power button for about 10 seconds, I get in the Windows Device Manager in Other Devices a new(unrecognized) device named APX. When I pull out the USB cable the I hear the windows usb disconnect sound and the device disappears.
When I connect the battery, I connect the USB to my PC. I don't push any buttons and after 15 or so seconds I get a message USB device not recognized in the USB controllers section of the Windows Device Manager. When I press and hold the Power button (or Power and volume down buttons), after 10 sec The unrecognized device is moved to the Other Devices section and again is called APX.
I cannot turn it on. I cannon boot into bootloader. I have tried almost any approached listed here an on Google (about 10 different step by step guides) and I remain in this position.
Please help me bring it back to life. Hope it's possible. What should I try. I am fairly technical and can understand most instructions.
Had same problem,the only solution found charging via dock station.My 5 years old child broke usb port trying insert cable.

How do you put SATV into fastboot/recovery using the power button?

Anyone have a link to a video showing how to use the power button to put this thing into fastboot/recovery?
I have a unresponsive unit that I want to flash. Seems like I can't get it into recovery but I'm not sure if I'm doing it correctly.
Here are my steps:
- Unplug everything from shield and unplug power from wall
- Plug in USB OTG cable from computer to shield tv (no lights from shield at this point)
- Plug in power cable to shield tv (power still unplugged from wall, no change to shield)
- Hold power button on shield tv for 3 seconds (nothing happens on shield, no lights or indication)
- Let go of power button and plug in power adapter to wall (light on shield turns on at this point)
- Nothing happens, no HDMI output and no indication from PC that a device is connected.
Any help?
FYI from nVidia website:
Code:
HW method:
- Disconnect power cable
- Insert USB OTG cable and make sure to connect other end to a host PC
- Connect power cable to SHIELD
- Quickly start pressing power button for ~3 seconds
- Do not hold the button and connect power supply afterwards
- HDMI TV should be always connected to SHIELD
I've booted mine over 100 times and only got in to work once, and can't reproduce the results. I have posted a similar thread, and couldn't find anything, but I'm terrified of something causing an unbootable device again because of this reason. If I find anything else to help out, I'll let you know, but my best advice is just keep trying, a lot. Don't quote me here, bit I think when I got it to boot sucessfully, I wasn't holding the button, I was tapping it for 3 seconds. Fairly quickly, but not super fast tapping. Some users report holding it works, but that didn't seem to for me.
Its a ***** to do with the hardware buttons but I have done it when I had a bootloop. If you can get it to boot normally its far easier to do it via adb "adb reboot bootloader". And if your rooted you can just use a sideloaded reboot manager app.
Yes doing it with a rebooting app or by connecting to a computer is the way to go.
baileyjr said:
Its a ***** to do with the hardware buttons but I have done it when I had a bootloop. If you can get it to boot normally its far easier to do it via adb "adb reboot bootloader". And if your rooted you can just use a sideloaded reboot manager app.
Click to expand...
Click to collapse
tailslol said:
Yes doing it with a rebooting app or by connecting to a computer is the way to go.
Click to expand...
Click to collapse
It's not responding, so they basically need to recover a soft brick, which is why I'm going to assume that they posted here. Someone needs to figure out a better trick, or they need a better method for any successor to this. Especially since it supports fastboot oem unlock.
kdb424 said:
It's not responding, so they basically need to recover a soft brick, which is why I'm going to assume that they posted here. Someone needs to figure out a better trick, or they need a better method for any successor to this. Especially since it supports fastboot oem unlock.
Click to expand...
Click to collapse
i hope nvidia put a timer trick or something to boot it in recovery mode ,maybie hold the button some secs.
maybie you will find some info in the shield documentation?
edit:found something i guess :
HW method:
- Disconnect power cable
- Insert USB OTG cable and make sure to connect other end to a host PC
- Connect power cable to SHIELD
- Quickly start pressing power button for ~3 seconds
- Do not hold the button and connect power supply afterwards
- HDMI TV should be always connected to SHIELD
Alternative method:
- Perform software shutdown on SHIELD by holding Power button for 10 seconds
- Connect USB OTG cable to SHIELD
- Start pressing power button for 3 seconds
- HDMI TV should be always connected to SHIELD
then you can use nvidia full recovery images to flash the shield to factory firmware.
tailslol said:
i hope nvidia put a timer trick or something to boot it in recovery mode ,maybie hold the button some secs.
maybie you will find some info in the shield documentation?
edit:found something i guess :
HW method:
- Disconnect power cable
- Insert USB OTG cable and make sure to connect other end to a host PC
- Connect power cable to SHIELD
- Quickly start pressing power button for ~3 seconds
- Do not hold the button and connect power supply afterwards
- HDMI TV should be always connected to SHIELD
Alternative method:
- Perform software shutdown on SHIELD by holding Power button for 10 seconds
- Connect USB OTG cable to SHIELD
- Start pressing power button for 3 seconds
- HDMI TV should be always connected to SHIELD
then you can use nvidia full recovery images to flash the shield to factory firmware.
Click to expand...
Click to collapse
Been through it all. Soft bricked my shield, and spent an hour trying that. Only got it to work once and stopped playing with it.
kdb424 said:
Been through it all. Soft bricked my shield, and spent an hour trying that. Only got it to work once and stopped playing with it.
Click to expand...
Click to collapse
I got it to work with the hardware (plugging in the power cable) method as mine was in a bootloop. I found it difficult because it hard to know exactly where the power button was because its not a raised button. Once I figured out the specific location of the power button I could do it reasonably consistently, like 1 in every 3 attempts. Of course your device may just be faulty unfortunately.
baileyjr said:
I got it to work with the hardware (plugging in the power cable) method as mine was in a bootloop. I found it difficult because it hard to know exactly where the power button was because its not a raised button. Once I figured out the specific location of the power button I could do it reasonably consistently, like 1 in every 3 attempts. Of course your device may just be faulty unfortunately.
Click to expand...
Click to collapse
Correct me if I'm wrong, but the power button is the whole thing. If I touch anywhere on the button at all, it'll put my shield to sleep, or wake it. That being said, I could have a faulty device as you have stated. I'd really like someone to put a video on youtube of a sucessfull run just to try to match it as close as possible, because 1/. runs is much better than my 1/100 or so runs.
No,it is just the nvidia logo,it is written in the manual and on the plastic cover when you un box it.
A user from another german forum got the right trick for timing, so it should work nearly every time to enter the bootloader :
HW method:
- Disconnect power cable
Click to expand...
Click to collapse
it's needed to make sure that the device is switched off
- Insert USB OTG cable and make sure to connect other end to a host PC
Click to expand...
Click to collapse
If you want only to test how to enter the bootloader, it's not mandantory atm.
- Connect power cable to SHIELD
- Now WAIT for ~2 seconds
Click to expand...
Click to collapse
Just count: 21...22.. if you don't know how long are ~2 seconds
Now press the power-button for ~6 seconds
Click to expand...
Click to collapse
The power-button is the sensor area with the NVIDIA Logo on the shield TV
- HDMI TV should be always connected to SHIELD
Click to expand...
Click to collapse
yes, otherwise you can't see anything.
Click to expand...
Click to collapse
Is there a visual cue for holding for 6 seconds? I noticed the NVIDIA splash screen appears right around 2.5-3 seconds, is that too late or right when I should begin holding power?
What worked for me was letting the unit sit unplugged WITHOUT the OTG cable for about 10 or 15 minutes. I then prepared myself to plug the ac adapter back in and almost immediately pressing the 'on' button thereafter. Got to the bootloader and was able to recover from there.
According to the Nvidia Shield information page, you plug the computer into the Shield's micro usb. Unplug the Shield's power. Wait like 10 seconds or so. Plug it back in. As soon as you see the light come on, wait for about 2 secs. Then hold down the power button till the bootloader comes up. It should come up within 6 secs, maybe sooner. That's it. Basically like what scorpio16v quoted. What Nvidia doesn't tell you, is that it doesn't have to be plugged into your computer. For example, I was able to get my Shield TV to bootloader using this built in hardware method by plugging it into my OG Shield via otg adapter on the micro usb cable.
Saw this on the Shield User Guide:
Reset Using NVIDIA Button on SHIELD
To access the fastboot menu:
1.
Turn off your SHIELD.
2.
Unplug the power cable from your SHIELD..
3.
Connect your SHIELD to your PC/Mac/Linux machine's micro USB port.
4.
Plug the power cable back into your SHIELD.
5.
Wait 2 seconds, and then hold the NVIDIA button for 5-6 seconds until you see the fastboot menu on the display.
Here's a link to the guide
http://support-shield.nvidia.com/android-tv-user-guide/index.htm#t=About_SHIELD.htm
I don't know about fastboot but to reboot into Recovery, simply attach a USB keyboard and press ALT +PRINT SCREEN + i (same as the Ouya)
dark_saian said:
I don't know about fastboot but to reboot into Recovery, simply attach a USB keyboard and press ALT +PRINT SCREEN + i (same as the Ouya)
Click to expand...
Click to collapse
good to know!
it seems it works on fire tv too!

Ployer MOMO9W (Windows 10) - Bricked, Drivers, Recovery. BIOS Insyde

Some time ago I've bought Ployer MOMO9W tablet. It was "bricked" by disabling USB ports, and have installed Windows 8.1. But factory there was Windows 10. Someone tried to "back" to previous system. There, also touch drivers were wrong and can't be operated also by touch - so bricked. But I've recovered it. All was OK.
But... there was some my further going. I've found that this tablet have similar Onda V891w (not Onda V891). And this tablet has version of Dual Boot. I've tried to flash that BIOS, because many people said (on Chineese forums) that it will work. Yes, after flashing, BIOS was ok. Some things not worked, then I - in lack of time, wanted to go back, to "my" Ployer MOMO9w BIOS and stay on it. Accidentially I flashed wrong BIOS. All was ok, during restart.
Now the tablet has dying response.
I tried to flash it by USB or SD card. In this BIOS (Insyde) some people said that it have Recovery mode and can be back again by this method. Not using SPI Programmer. Only by copying BIOS file on USB and run device.
To start this procedure, I have to do some combinations, like: disconnect power (or even battery - this was for laptops, but this tablet have connectable battery), connect USB with BIOS, hold VOL+ (also version to hold VOL+ and VOL-), then connect power, and then press power button to run device. For laptops, combinations was on keyboard some like WIN+B, or Fn+Esc etc. But on tablet, without connecting keyboard it's quite impossible.
I don't know if I done something wrong, but instructions for laptops are different (combined key press on keyboard, connect power). In this tablet I have only 1 micro USB port. It's for charging, or for OTG. I used also Y cable which can in same time charge and OTG. There I can connect USB disk and connect power.
There is also NO HDMI to view what's going on screen.
This tablet now:
Give some reactions, because when I connect USB power cable it takes some power (used measuring device), and green diode at microUSB port flashes very shortly one time. Then tablet still takes some power, for about ~17seconds, and again, power down, and green diode flashes again.
When I hold power button, tablet sometimes power OFF, measuring device show no power drain,
When I connect USB or charging, it wakes up, and diode flashes again as above. Don't need press power, it starts automatically
Holding power, and trying to start it with VOL keys and power, seems have no effect
I had some reactions before, when tablet, when restarting, it reads USB (pendrive), because diode on it flashes, but flashed some times, and stops. And again, restarts, etc.
BIOS was: Insyde. File: MOMO.W89EBBN03
Wrong BIOS, was and modified version of this - MOMO.W89EBBN03, but I did not want flash this. In mistake, file was in Flash folder and there were no back and stop process. After that, I thought it was OK file.
Model: Ployer MOMO9W (Windows 10 single OS)
SN: P805: MO90W V03 32 1510.10C077
RAM: 2GB, HDD (eMMC) 32GB, Intel Atom Baytrail Z3735F
I have some original BIOSes, but I don't know if names are ok. Because to run Insyde BIOS Recovery, I have to put file on USB disk with proper name. It could be BIOS.fd, or BIOS.ROM, or W89EBBN03.fd/.rom/.bin etc. In some folders I have these files in BIOS pack:
H2OFFT-S.efi
MOMO.W89EBBN03.ROM
STARTUP.nsh
I attach some photos of internals around WINBOND (25Q64FWIG). And also micro USB port, where is diode, that flashes green (previously, when charged it was light still on red). So duo color.
Can you help me bring this tablet back to work? It's really good. Have fast Hynix eMMC (160mb/s read and 85mb/s write).
I've never used a SPI Programmer device, but I see that legs of this BIOS are short and could be problem, to hold it by clamp. But, if possible, I would like to nt use this tool (because I don't have it).
Similar tablet: Onda v891w, maybe someone with this device will help.
Thank you
----- E01
When I off the tablet, and connect charger (with measuring device), it's value is jumping from ~1A to 0,07, and then green diode flashes. I' connecting it directly, just to charge the tablet. No other devices, HUBs etc, just charging. When I flashed BIOS, on Windows 10 battery show ~56%. Now it seemt like it's restarting, because a lack of power. Question: Is battery "empty" or by flashing BIOS some parameters are not properly read?
Also, when I disconnect battery and charge cable, also directly, all is the same as at battery, but are a little bit different values.
Maybe that info helps someone to help me 0
Hi Oeriel,
I got a same device as yours, Ployer MOMO 9W,
but as I checking the system information through the Windows 10 administrative tools,
the BIOS version/Date showing INSYDE Corp. MOMO.W89EBBN01, 10/24/2014,
so the BIOS your wrong flashing was the W89EBBN03 making the dying situation.
So if this thread alive, I will backup mine and send you.
Hi, I'm looking for the momo9w drivers (for the touchscreen, if someone wants to share them )
thanks

[Shield TV Pro 2017] Device potentially bricked after changing HDD for SSD

Hello,
I've potentially bricked my Shield TV and want to see if I can salvage it from it's current state.
What have I done to the device
I unlocked the bootloader
I opened the device and took out the HDD
I replace it with an SSD (which data i cloned from the HDD)
After that the Shield TV wouldn't boot up. I connected the old HDD to no avail. The HDD was working fine before.
I know can't get the device to boot up in fastboot. It still turns on, as indicated by the green led.
What have I tried
Cold booted the device (turn it off and seperate it from power for 15 - 20 minutes)
Used the controller (Pressing A+B) after inserting the power cable to get into fastboot. Controller rumbles. Nothing happens afterwards.
Hold the "power button" on the device for 5 - 6 sec to get into fastboot. Doesn't work, just turns the device off.
Connected the Shield TV to my PC and then try to enter fastboot. Device is detected by Windows as "Unknown usb device". "Windows has stopped this device because it has reported problems. (Code 43)"
I'm pretty stuck at this point. Is there any know way to revive my device?
Or is it simply bricked beyond repair?
Best regards
Same thing happened to me. Nvidia support emailed this procedure. Worked for some, not for others.
-> Unplug all the cables and keep the device off for good 2-3 minutes.
-> Plug the Power cable, controller through USB (Wired) and Ethernet cable to the ATV. Do not connect HDMI cable.
-> The device will power on. Keep it idle for about 5 minutes and keep tapping A button on the controller. Continue tapping for about a few seconds.
-> Now leave the device is this state without the HDMI cable for good 15 to 20 minutes and plug the HDMI cable.
-> See if the ATV displays any output
Hi @Makenshi2k have you managed to fix it? I have the same situation
@qqhorus tried your solution but it didn't work for me
uncenty said:
Hi @Makenshi2k have you managed to fix it? I have the same situation
@qqhorus tried your solution but it didn't work for me
Click to expand...
Click to collapse
Unfortunately no. The device is bricked.
I haven't found any way to restore it.

Can't seem to get OEM unlocking to work on T290

Okay, weird problem here. I'd like to unlock the bootloader on the Samsung Galaxy Tab A 8.0 2019, but can't seem to recreate the blue screen asking if I'd like to enter download mode or unlock the bootloader. I've read that I should press both volume keys and plug in the device while holding the keys until that blue screen appears. However, for me this doesn't do anything except "boot" the charging thing (where you see the current battery percentage), I held the keys for about 30 seconds but didn't get anything different. When I press Power + Volume up I get that Android Recovery screen, but can't seem to unlock the bootloader from there either. I tried rebooting to bootloader, but that just gave me the download mode instantly (on a black screen with my tablet logo) - this way I also had no choice to unlock the bootloader. Anyone know what I should do here? I'm kind of stuck
Edit: fastboot oem unlock just tells me it's waiting for device, however adb can find my device (OEM unlocking and USB debugging is on)
Tizu69 said:
Okay, weird problem here. I'd like to unlock the bootloader on the Samsung Galaxy Tab A 8.0 2019, but can't seem to recreate the blue screen asking if I'd like to enter download mode or unlock the bootloader. I've read that I should press both volume keys and plug in the device while holding the keys until that blue screen appears. However, for me this doesn't do anything except "boot" the charging thing (where you see the current battery percentage), I held the keys for about 30 seconds but didn't get anything different. When I press Power + Volume up I get that Android Recovery screen, but can't seem to unlock the bootloader from there either. I tried rebooting to bootloader, but that just gave me the download mode instantly (on a black screen with my tablet logo) - this way I also had no choice to unlock the bootloader. Anyone know what I should do here? I'm kind of stuck
Edit: fastboot oem unlock just tells me it's waiting for device, however adb can find my device (OEM unlocking and USB debugging is on)
Click to expand...
Click to collapse
With the tablet off, plug the cable into a PC only. (not a charger) Then, while holding down both vol up and down, plug the cable into the tablet. After a couple of second, the screen should appear with the unlock option instructions.
lewmur said:
With the tablet off, plug the cable into a PC only. (not a charger) Then, while holding down both vol up and down, plug the cable into the tablet. After a couple of second, the screen should appear with the unlock option instructions.
Click to expand...
Click to collapse
I am doing that, but the tablet just shows the charging animation that appears when the device is off. By the way, the device is on Android 11, is that maybe the problem somehow?
Tizu69 said:
I am doing that, but the tablet just shows the charging animation that appears when the device is off. By the way, the device is on Android 11, is that maybe the problem somehow?
Click to expand...
Click to collapse
It has nothing to do with what version of Android you are on. It should enter the download mode before Android even starts to load. Have you tried using another USB cable? They can be very touchy about detecting the data connection rather than just power. As I said, I don't have a 290, but on my 500 it helps to connect to the PC via a USB 2.0 hub rather than directly to the PC.
lewmur said:
It has nothing to do with what version of Android you are on. It should enter the download mode before Android even starts to load. Have you tried using another USB cable? They can be very touchy about detecting the data connection rather than just power. As I said, I don't have a 290, but on my 500 it helps to connect to the PC via a USB 2.0 hub rather than directly to the PC.
Click to expand...
Click to collapse
I now tried 3 or 4 different cables with no luck. I'm still assuming that it has something to do with the software, and I noticed today that the tablet actually runs OneUI Core, whatever that means.

Categories

Resources