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
Related
My shield won't boot, and every indication is that it needs to be reflashed with the system OS, per a few threads here. I can get to the fastboot menu, but I can't get adb to recognize the device. I have tried several rounds of adb drivers-the android SDK, the 2015 NVidia USB drivers, and the 2018 NVidia drivers. I used USBDView to verify that the Shield is connected to USB, and checked the VendorID and ProductID and verified that it was listed in the driver INF. Still, the adb utility doesn't show the device.
I'm in way over my head as far as trying to reflash this, and I'm hoping someone who has this device and already has success in flashing it might be willing to reflash it for me?
Fastboot and ADB are different, check you are connected VIA fastboot with a USB to USB cable. You should have fastboot in the same folder you are trying to ADB
To check connection
<folder> fastboot devices
To flash the firmware
Download the full recovery image here
https://developer.nvidia.com/gameworksdownload
Unzip to your fastboot folder
run the flash_all.bat
<folder> fastboot flash_all.bat
Be patient, it will take a while, do not unplug. Let it run its course and it will reboot when complete.
This should get it working, it did for me.
(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?
I have nexus 7 2012 wifi. Its most recent update had some bugs so I tried to reinstall an older firmware using adb (i got the firmware from google website). The tablet entered a boot loop during installation and the adb (on ubuntu terminal) gave me an error so I disconnected it. The device is now off when I try to turn it on (or even into recovery mode) the screen doesn't turn on, the device gets hot and I hear some strange noise from the PCB. I think I destroyed the bootloader or something like that. when I run the command ($ lsusb )on the terminal the device is recognized as Nvidia device (but adb doesn't detect it). any help?
IS there any way to install firmware without detecting the device?
Thanks in advance.
If it is being recognised as an Nvidia device it's possible that it is now in APX mode, and if that's the case, you can reflash the bootloader with a tool called NvFlash. There is a (Windows) tutorial here: https://android-forums-app.blogspot.com/2016/03/tutorial-how-to-unbrick-nexus-7-using.html
I vaguely remember having to flash the bootloader like this because the tablet was dead but I don't remember using wheelie or blob.bin, only NvFlash.
You can get the latest bootloader from here, for a Wi-Fi model you will need the grouper file: https://forum.xda-developers.com/showthread.php?t=2417097
I had previously unlocked my bootloader, installed the latest Magisk, and created and booted a patched recovery.img to gain root access. I recently updated to SHIELD Software Experience Upgrade 8.2, but for some reason, fastboot no longer detects my 2019 SHIELD TV Pro when I am trying to send commands on the bootloader menu. It detects my device just fine when I boot up Android and successfully executes any ADB commands that I send, so it is only a fastboot problem. I made sure to install the latest drivers for fastboot, but while my Surface detects my SHIELD without errors, fastboot still cannot find it. After hours of trial and error, I decided to finally sign up here to see if anyone could help me.
Here is a similar issue with a different device a few months ago:
https://forum.xda-developers.com/galaxy-a20/help/fastboot-sm-a205u-t4135987
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