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
Hi Friends,
I have decided to create a new post, since I researched and it seems that my issue is not covered exactly by any previous thread.
I have Sony F5321, used years with Stock ROM. While playing a game, it turned off randomly, but when I play the same game while charging with USB cable (with AC charger or connected to a laptop), the phone was working fine. I have unlocked the bootloader and flashed LineageOS 16 (Android 9) in case a battery issue was solved better with LineageOS than with stock ROM. After some weeks with same (supposedly) battery issue, I decided to go back to Stock ROM. I have flashed OK with Flashtool (no errors), but phone is now stuck in Sony boot logo.
The status is:
1) Boot into Stock Rom: doesn’t work
2) Boot into recovery: doesn’t work
3) Force shut down (3 vibrations): works
4) Force reboot (1 vibration): doesn’t work, it stops at Sony boot logo
5) Charging while powered off: doesn’t work (no battery logo appears, red light)
6) Flashtool into flashmode: doesn’t work (it’s not detected)
7) Flashtool into fastboot mode: works, but I cannot do anything with that.
Please, your help, how can I get the phone works again? Preferably with Stock ROM, or any other stable ROM, but working! Thanks!
Nobody will help?
jayeffpee said:
Hi Friends,
I have decided to create a new post, since I researched and it seems that my issue is not covered exactly by any previous thread.
I have Sony F5321, used years with Stock ROM. While playing a game, it turned off randomly, but when I play the same game while charging with USB cable (with AC charger or connected to a laptop), the phone was working fine. I have unlocked the bootloader and flashed LineageOS 16 (Android 9) in case a battery issue was solved better with LineageOS than with stock ROM. After some weeks with same (supposedly) battery issue, I decided to go back to Stock ROM. I have flashed OK with Flashtool (no errors), but phone is now stuck in Sony boot logo.
The status is:
1) Boot into Stock Rom: doesn’t work
2) Boot into recovery: doesn’t work
3) Force shut down (3 vibrations): works
4) Force reboot (1 vibration): doesn’t work, it stops at Sony boot logo
5) Charging while powered off: doesn’t work (no battery logo appears, red light)
6) Flashtool into flashmode: doesn’t work (it’s not detected)
7) Flashtool into fastboot mode: works, but I cannot do anything with that.
Please, your help, how can I get the phone works again? Preferably with Stock ROM, or any other stable ROM, but working! Thanks!
Click to expand...
Click to collapse
Sounds like hardware failure to me, happened to me before... However, if you can get into fastboot, just go ahead and flash back to a custom kernel and recovery, and see if you can boot to recovery. That will tell you if it's not a hardware issue, then you can figure out how to get back to stock...
levone1 said:
Sounds like hardware failure to me, happened to me before... However, if you can get into fastboot, just go ahead and flash back to a custom kernel and recovery, and see if you can boot to recovery. That will tell you if it's not a hardware issue, then you can figure out how to get back to stock...
Click to expand...
Click to collapse
I tried a lot of things now. To confirm, I tried to use Flashtool in fastboot mode, but not sure where I get a custom kernel file to use with Fastboot menu option "select kernel to flash" but I have downloaded again lineage-16.0-20200511-UNOFFICIAL-kugo.zip file, should I take "boot.img" from unzipped directory? and how to flash the twrp-3.3.1-0-kugo.img file with Flashtool? which is the option to flash recovery using Flashtool in fastboot mode?
jayeffpee said:
I tried a lot of things now. To confirm, I tried to use Flashtool in fastboot mode, but not sure where I get a custom kernel file to use with Fastboot menu option "select kernel to flash" but I have downloaded again lineage-16.0-20200511-UNOFFICIAL-kugo.zip file, should I take "boot.img" from unzipped directory? and how to flash the twrp-3.3.1-0-kugo.img file with Flashtool? which is the option to flash recovery using Flashtool in fastboot mode?
Click to expand...
Click to collapse
Don't need Flashtool for fastboot. If you have the drivers installed, use your computer, and connect with the power off, holding the volume up button, and let go of the button when you see the blue led light, (if you don't get a blue led light, could be further evidence of a hardware issue). Now you're in fastboot mode.
Open a command prompt, and type "fastboot". If fastboot / adb is installed on your computer, and is set in the path, you will get a fastboot reply, if not, you will get, "fastboot is not recognized as a program or command...", or something like that. In that case, you need to either install fastboot, (look it up - it takes about 30 seconds), or, in the case of Linux or if you have the fastboot / adb files on your computer, but it's not in the Windows path, just change directory in your terminal to the directory where the files are, then try the command again.
Once you have fastboot working, just copy whatever you want to flash to the same directory you're in, and the commands are:
Kernel -
Code:
fastboot flash boot [name of file].img
Recovery -
Code:
fastboot flash recovery [name of file].img
ROM -
Code:
fastboot flash system [name of file].img
OEM (needed for recent AOSP -based roms) -
Code:
fastboot flash oem [name of file].img
Curious - how did you flash Lineage last time?
levone1 said:
Don't need Flashtool for fastboot. If you have the drivers installed, use your computer, and connect with the power off, holding the volume up button, and let go of the button when you see the blue led light, (if you don't get a blue led light, could be further evidence of a hardware issue). Now you're in fastboot mode.
Open a command prompt, and type "fastboot". If fastboot / adb is installed on your computer, and is set in the path, you will get a fastboot reply, if not, you will get, "fastboot is not recognized as a program or command...", or something like that. In that case, you need to either install fastboot, (look it up - it takes about 30 seconds), or, in the case of Linux or if you have the fastboot / adb files on your computer, but it's not in the Windows path, just change directory in your terminal to the directory where the files are, then try the command again.
Once you have fastboot working, just copy whatever you want to flash to the same directory you're in, and the commands are:
Kernel -
Code:
fastboot flash boot [name of file].img
Recovery -
Code:
fastboot flash recovery [name of file].img
ROM -
Code:
fastboot flash system [name of file].img
OEM (needed for recent AOSP -based roms) -
Code:
fastboot flash oem [name of file].img
Curious - how did you flash Lineage last time?
Click to expand...
Click to collapse
If I remember correctly, I have flashed the LineageOS (and also stock ROM downloaded by XperiFirm) with Flashtool in "flashmode", but then when I got the logo bootloop, it didnt work anymore. Only fastboot works. Not even booting in recovery mode seems to work.
I have already tried with fastboot in windows 10 cmd prompt (now called PowerShell).
fastboot flash boot boot.img --> works OK
fastboot flash recovery twrp-3.3.1-0-kugo.img --> works OK
fastboot flash system [system file].img --> there's no other IMG file inside LineageOS zip file besides boot.img, if you could provide another custom ROM zip file which includes both boot.img and system.img, please let me know
in addition. after flashing recovery OK, I tried "fastboot boot recovery" and the phone boots into bootloop again.
after shutting it off, there's no way to get into recovery mode. Only sony logo and red light (or no light)
jayeffpee said:
If I remember correctly, I have flashed the LineageOS (and also stock ROM downloaded by XperiFirm) with Flashtool in "flashmode", but then when I got the logo bootloop, it didnt work anymore. Only fastboot works. Not even booting in recovery mode seems to work.
I have already tried with fastboot in windows 10 cmd prompt (now called PowerShell).
fastboot flash boot boot.img --> works OK
fastboot flash recovery twrp-3.3.1-0-kugo.img --> works OK
fastboot flash system [system file].img --> there's no other IMG file inside LineageOS zip file besides boot.img, if you could provide another custom ROM zip file which includes both boot.img and system.img, please let me know
in addition. after flashing recovery OK, I tried "fastboot boot recovery" and the phone boots into bootloop again.
after shutting it off, there's no way to get into recovery mode. Only sony logo and red light (or no light)
Click to expand...
Click to collapse
So you tried to hold power and volume down to get into recovery? Also, if the only file in the LOS zip is a boot img, then the zip is incomplete. Try one of the Omni roms from the roms thread here. I've used them for N, O, and P, and they all work fine. There's a link to the Sony OEM files in the first post...
levone1 said:
So you tried to hold power and volume down to get into recovery? Also, if the only file in the LOS zip is a boot img, then the zip is incomplete. Try one of the Omni roms from the roms thread here. I've used them for N, O, and P, and they all work fine. There's a link to the Sony OEM files in the first post...
Click to expand...
Click to collapse
Yes, I tried vol+down while power on, and it stuck in sony logo white screen. Also tried from fastboot mode with "fastboot boot recovery" and "fastboot boot twrp.img" and it says "rebooting" but it only disables fastboot mode (windows' typical unplug drive sound), but phone get stuck with blue light.
its really strange. Is it possible that the phone has a battery HW issue that avoids it to charge (sometimes the empty battery big icon black screen appears), and that issue avoids recovery or reboot process?
jayeffpee said:
Yes, I tried vol+down while power on, and it stuck in sony logo white screen. Also tried from fastboot mode with "fastboot boot recovery" and "fastboot boot twrp.img" and it says "rebooting" but it only disables fastboot mode (windows' typical unplug drive sound), but phone get stuck with blue light.
its really strange. Is it possible that the phone has a battery HW issue that avoids it to charge (sometimes the empty battery big icon black screen appears), and that issue avoids recovery or reboot process?
Click to expand...
Click to collapse
Maybe specific to battery, but any issue with the main board is going to caused general wackiness... Could be what's happening. Maybe it would be worth it to try a new battery. Have you already tried different cables?
levone1 said:
Maybe specific to battery, but any issue with the main board is going to caused general wackiness... Could be what's happening. Maybe it would be worth it to try a new battery. Have you already tried different cables?
Click to expand...
Click to collapse
yes, I have 2 USB 3.0 cables. Both works perfectly with my other phone Moto G6 plus, in fast charge mode. it I can flash anything in fastboot mode, but cannot reboot into recovery, do you have other option to try? I downloaded and flashed the Sony OEM file (8.1/9/10) and flashed with fastboot normally. Then I have downloaded the Omni WEEKLY zip file, but in the Omni XDA thread, it says that the zip file must be flashed from Recovery (copied into the SD card), but I cannot access Recovery. I really want to revive this phone.
jayeffpee said:
yes, I have 2 USB 3.0 cables. Both works perfectly with my other phone Moto G6 plus, in fast charge mode. it I can flash anything in fastboot mode, but cannot reboot into recovery, do you have other option to try? I downloaded and flashed the Sony OEM file (8.1/9/10) and flashed with fastboot normally. Then I have downloaded the Omni WEEKLY zip file, but in the Omni XDA thread, it says that the zip file must be flashed from Recovery (copied into the SD card), but I cannot access Recovery. I really want to revive this phone.
Click to expand...
Click to collapse
Oh right - I forgot about that... Try AOSP https://androidfilehost.com/?fid=1899786940962592899 Unzip it and there should be a system img in it...
PHP:
levone1 said:
Oh right - I forgot about that... Try AOSP https://androidfilehost.com/?fid=1899786940962592899 Unzip it and there should be a system img in it...
Click to expand...
Click to collapse
Thanks for the link! I have downloaded and flashed all the IMG files inside with fastboot, everything OK. But the phone is still not rebooting to system nor to recovery mode. same behaviour. Stuck in sony logo.
Weird: I was just using it normally, it switched off and now it stays stuck on the Google logo; when entering recovery mode, I get TWRP"s splash screen and it stays there, so I cannot even recover.
Suggestions please??
Note 1: I'm pretty bad with this kind of stuff, need step-by-step instructions.
Note 2: rom is AOSP 7.1.2 but I guess is irrelevant, as even TWRP does not load.
Thanks in advance!!
Can you fastboot boot the TWRP recovery?
Hmmm dont know exactly what that means sorry; I mean I havent tried connecting it to the laptop and using thr ADB toolkit, but I can reset via Power+VolDown to the bootloader menu (? the android layind down and giving the option to StartSystem/ SwitchOff/ Restart/ RecoveryMode), and choosing RecoveyMode it tries to launch TWRP (it even shows the logo) but stays there on the splashscreen, doesn't quite manage to give me the TWRP menus
Someone?
AndDiSa said:
Can you fastboot boot the TWRP recovery?
Click to expand...
Click to collapse
let's see... I set in recovery mode, connect to the PC (does not recognise it), and with "fastboot boot twrp.img" it just sends/writes the file, the tab shows the Google logo with open lock, and then tries to launch Twrp, but as before, it just get stuck in the splashscreen "TeamWin Recovery Project 3.3.1.0" , so just the same.
Command "fastboot flash boot twrp.img" the same
Command "fastboot flash recovery twrp.img" the same
Command "adb devices" returns the list empty
Command "adb reboot recovery" returns "error: no devices / emulators found"
Command "fastboot oem unlock" returns "(bootloader) bootloader is already unlocked"
I tried running a tool called FirstAid (https://forum.xda-developers.com/devdb/project/dl/?id=16684) but does nothing for me
I'm lost, please help
Video and photos of the issue (device, not adb)
video: https://photos.app.goo.gl/GrFrmQhbyQeHVFZN7
Well, looking at your video it seems that there is no bootable ROM installed and also the recovery (for what ever reason) has some issues to start.
The fact, that you are able to boot into bootloader shows that at least it's not completely bricked ... but there's still the chance that the flash memory has some issues.
I would connect the device via usb with a PC and try to do a
fastboot boot <twrp-3.3.1-grouper.img>
to whether in that case the recovery is booting.
If this is successful, the next step would be re-flashing the recovery into the recovery partition and booing into recovery mode from the bootloader.
If this is successful, too, wiping and flashing a new ROM would be the last step.
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