Stuck on boot animation screen? [SOLVED] - Shield Android TV Q&A, Help & Troubleshooting

I tried to root my NSTV and got as far as flashing the .zip file in TWRP but after I rebooted, it's now stuck in the boot animation screen with the dancing colored circles?
Any ideas please?
SOLUTION
First download Recovery OS Image from here: https://developer.nvidia.com/gameworksdownload
SHIELD RECOVERY IMAGE FLASHING INSTRUCTIONS
To follow the instructions in this guide, you will need adb and fastboot.
 These tools are provided as part of the Android SDK:
http://developer.android.com/sdk/index.html
Before flashing this recovery image to your SHIELD, connect your SHIELD
 via USB to the PC where you downloaded this recovery image.
Next, put your SHIELD into fastboot mode using one of the following methods:
SW method:
- Boot to android home screen
- Connect the device to linux/windows system
- Open terminal (on linux); command prompt (on windows).
- Type "adb reboot bootloader" in terminal/command prompt
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
Fastboot menu navigation:
- Single tap on touch button for navigations between different menu.
- Hold down touch button for 4 second and release for selecting any menu
To flash this recovery image to your SHIELD, run the following commands from
 the directory where you extracted the recovery image package. If this is the
first time you have done this procedure, you must unlock the bootloader. Get
 DTB file name to use for flashing for your product(see below):
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash userdata userdata.img
fastboot flash staging blob
fastboot flash dtb <DTB file name>
Unlocking the Bootloader
Your SHIELD may have shipped with a locked bootloader. To update the device,
you must unlock the bootloader using the following:
- fastboot oem unlock
- It will take you to '!!! READ THE FOLLOWING !!!' page.
- Two selectable options are available. 'Confirm' and 'Back to menu'.
- Select 'Confirm' to unlock the bootloader.
Unlock may take upto 2 hours for pro device.
Get <DTB file name>
- For base sku use dtb file "tegra210-foster-e-p2530-0930-e02-00.dtb"
- For pro sku use dtb file "tegra210-foster-e-hdd-p2530-0932-e02-00.dtb"

old thread i know, but still very helpful!
after updating to 3.2 yesterday and then trying to root it again (lost after the update), i was stuck at the boot animation screen for-ev-ver!!
used this guide to fix and was successful, however there was one change that i had to make: after extracting the 3.1 recovery image....there was no "userdata.img" file. so in place of that file, i flashed the "vendor.img", which was in the extracted folder along with the other files i needed to flash.
in the end what worked for me was the following:
downloaded the 3.1 recovery OS image from the link provided in OP. extracted/unzipped the image file to a folder, then from that folder i flashed the following files in this order:
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash vendor vendor.img
fastboot flash staging blob
fastboot flash dtb tegra210-foster-e-p2530-0930-e02-00.dtb
worked like a charm for me, booted up fine, ran updates and when it was done it asked if i wanted to update to version 3.2 ....i said yes and when that finished, i tried to root it once again. all went smoothly this time. not sure what went wrong the first time, but i am now on version 3.2, rooted, and did not even lose any data along the way!!
hardest part for me was getting into the bootloader (using HW method posted above). took me quite a few tries before i nailed it, lol
thanks for posting @Neo3D

Just tried to do it, but failed:
C:\adb>fastboot flash recovery recovery.img
target reported max download size of 67108864 bytes
sending 'recovery' (22712 KB)...
FAILED (data transfer failure (Unknown error))
finished. total time: 5.014s

I;m stuck,it won't except the tegra darcy or tegra foster. Help please i am sitting her stuck!

Related

Adb fastboot shield recovery image flashing instructions (RETURN TO STOCK)

This is Nvidia's own instruictions which I just followed works great! For new members please be aware that you may have to edit a command given in the instructions below which I will point out (depends on what OTA you have downloaded) for example
fastboot flash dtb tegra124-tn8-p1761-1270-a04-e-battery.dtb Highlighted in red is the name you may have to change within the extracted ota, Just look in the extracted file and locate the .dtb now just copy and paste the name of your .dtb and change the fastboot command --> example--> fastboot flash dtb tegra144-tn8-p1761-1270-a04-xda-battery.dtb
Please Read Carefully!
Follow here to get OTA
http://forum.xda-developers.com/shield-tablet/general/shield-tablet-otas-t2847116
What you must have
You need a unlocked boot loader instructions further below.
Also in cmw recovery, please wipe all partions! and reboot in to fastboot mode whilst still in recovery!
SHIELD RECOVERY IMAGE FLASHING INSTRUCTIONS
To follow the instructions in this guide, you will need adb and fastboot.
These tools are provided as part of the Android SDK:
http://developer.android.com/sdk/index.html
or you can just download this little .exe Minimal ADB and Fastboot this is what I used.please extract your recovery.zip into where you have installed Minimal ADB and Fastboot example c:\program files x86\Minimal ADB and fastboot.
https://docs.google.com/file/d/0B1S0LCuXCnnmSWh6NGJmSE1BUWc/edit?usp=sharing
Before flashing this recovery image to your SHIELD, connect your SHIELD
via USB to the PC where you downloaded this recovery image example same as above c:\program files x86\Minimal ADB and fastboot.
Next, put your SHIELD into fastboot mode using one of the following methods:
SW method 1:
- Boot to android home screen
- Connect the device to linux/windows system
- Open terminal (on linux); command prompt (on windows).
- Type "adb reboot bootloader" in terminal/command prompt
HW method 2 :
- Turn off the device
- Press and hold "Back"+"Home"+"SHIELD" buttons till device boots
To flash this recovery image to your SHIELD, run the following commands from
the directory where you extracted the recovery image package. If this is the
first time you have done this procedure, you must unlock the bootloader (see
below):
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash userdata userdata.img
fastboot flash staging blob
fastboot flash dtb tegra124-tn8-p1761-1270-a04-e-battery.dtb <---------------------------------------------------------------------
Now restart your device
now wait a min or two and you have just returned to stock!
Unlocking the Bootloader
Your SHIELD may have shipped with a locked bootloader. To update the device,
you must unlock the bootloader using the following:
- fastboot oem unlock
- Press the Home button on the device to highlight "Unlock".
- Press the Shield button to confirm the unlock. Your device's bootloader is now unlocked.
Also worth noting that on Linux, you can install the "android-tools" package that gives you ADB and Fastboot anywhere.
For example, on fedora 20, run:
$ sudo yum install android-tools
Make sure you run fastboot with su- privileges (not doing this caused me no end of frustration before finding out why my device wasn't detected).
MRobbo80 said:
This is Nvidia's own instruictions which I just followed works great! For new members please be aware that you may have to edit a command given in the instructions below which I will point out (depends on what OTA you have downloaded).
Unlocking the Bootloader
Your SHIELD may have shipped with a locked bootloader. To update the device,
you must unlock the bootloader using the following:
- fastboot oem unlock
- Press the Home button on the device to highlight "Unlock".
- Press the Shield button to confirm the unlock. Your device's bootloader is now unlocked.
Click to expand...
Click to collapse
Umm having a little trouble unlocking. Am I to understand that you unlock with the device turned on ? because otherwise there isn't a home button...and where is the shield button ? I only have power and volume
buttons. This looks like the unlock method for the Shield not the Shield Tablet.
Sent from my Shield Tab
Wulfpk said:
Umm having a little trouble unlocking. Am I to understand that you unlock with the device turned on ? because otherwise there isn't a home button...and where is the shield button ? I only have power and volume
buttons. This looks like the unlock method for the Shield not the Shield Tablet.
Sent from my Shield Tab
Click to expand...
Click to collapse
Your device should first be turned on. Then connect to PC and open a command prompt in your Android tools folder (where the ADB file resides) and type, "ADB reboot bootloader" (without the quotation marks).
Can I flash a ROW image in a US device?

[Q] Flashing a recovery to I9505 (jgedlte)

I've been trying during the last few hours to flash CWM/TWRP to my S4. Before starting, my phone was simply rooted (with CF-auto-root and Odin).
So I ran
Code:
fastboot oem unlock
and now I'm trying to flash with
Code:
fastboot flash recovery <recovery.img>
, but I keep getting the following error:
Code:
sending 'recovery' (9588 KB)...
OKAY [ 0.419s]
writing 'recovery'...
FAILED (remote: FAILSecure - Secure check failed)
finished. total time: 1.224s
(This one is from a run with recovery-clockwork-6.0.4.7-jfltexx.img, I also tried openrecovery-twrp-2.6.3.0-jgedlte.img and got the same error).
I ran
Code:
fastboot erase recovery
to see if it would help, but it did not do any better in the next tries to flash.
Now, I DID manage to boot into CWM with
Code:
fastboot boot recovery-clockwork-6.0.4.7-jfltexx.img
, but I rather flash it (Especially now that I erased the stock recovery.)
I also tried Odin and Heimdall, but Odin simply crashes when I hit "Start" and Heimdall fails to to communicate with my phone.
EDIT: Great. When booting with "fastboot boot", TWRP's touch doesn't work. CWM's touch doesn't work either, so I use the non-touch version, but when trying to install CM with ADB sideload, adb on my PC doesn't recognize CWM. What am I supposed to do now...?
Jon-G said:
I've been trying during the last few hours to flash CWM/TWRP to my S4. Before starting, my phone was simply rooted (with CF-auto-root and Odin).
So I ran
Code:
fastboot oem unlock
and now I'm trying to flash with
Code:
fastboot flash recovery <recovery.img>
, but I keep getting the following error:
Code:
sending 'recovery' (9588 KB)...
OKAY [ 0.419s]
writing 'recovery'...
FAILED (remote: FAILSecure - Secure check failed)
finished. total time: 1.224s
(This one is from a run with recovery-clockwork-6.0.4.7-jfltexx.img, I also tried openrecovery-twrp-2.6.3.0-jgedlte.img and got the same error).
I ran
Code:
fastboot erase recovery
to see if it would help, but it did not do any better in the next tries to flash.
Now, I DID manage to boot into CWM with
Code:
fastboot boot recovery-clockwork-6.0.4.7-jfltexx.img
, but I rather flash it (Especially now that I erased the stock recovery.)
I also tried Odin and Heimdall, but Odin simply crashes when I hit "Start" and Heimdall fails to to communicate with my phone.
EDIT: Great. When booting with "fastboot boot", TWRP's touch doesn't work. CWM's touch doesn't work either, so I use the non-touch version, but when trying to install CM with ADB sideload, adb on my PC doesn't recognize CWM. What am I supposed to do now...?
Click to expand...
Click to collapse
This process will trigger knox to 0x1
1. Download the recovery you want:
Download philz touch revovery from here:
https://goo.im/devs/philz_touch/CWM_Advanced_Edition/jflte/?page=4 (download the one with .tar.md5 extension)
Download TWRP here:
http://techerrata.com/browse/twrp2/jfltexx (download the one with .tar extension)
2. Download odin3 (v3.10.0) here:
https://mega.co.nz/#!OANlQZBS!GIq9q4Yy72syVYh36Q2whYIg85PST0QJhtIBrRh5MCk
3. Connect your phone in download mode to your PC (Don't reboot into download mode, shut down your phone and then boot into download mode) (you may have to install the driver, here: https://mega.co.nz/#!HQd12QYY!wuM2FvxmScI8rQIdosPaS6CLcvI4-yJNHHOiR3Rv0I0)
4. Open Odin click AP button, choose the file you downloaded and then click start.
5. Your phone will reboot, shut down your phone and try to boot into recovery (hold volume up and home and then press and hold power button release the power button when the blue text appears but keep pressing volume up and home, release those when the screen goes black).
6. You should now be in your chosen recovery.
jeffrey268 said:
This process will trigger knox to 0x1
1. Download the recovery you want:
Download philz touch revovery from here:
https://goo.im/devs/philz_touch/CWM_Advanced_Edition/jflte/?page=4 (download the one with .tar.md5 extension)
Download TWRP here:
http://techerrata.com/browse/twrp2/jfltexx (download the one with .tar extension)
2. Download odin3 (v3.10.0) here:
https://mega.co.nz/#!OANlQZBS!GIq9q4Yy72syVYh36Q2whYIg85PST0QJhtIBrRh5MCk
3. Connect your phone in download mode to your PC (Don't reboot into download mode, shut down your phone and then boot into download mode) (you may have to install the driver, here: https://mega.co.nz/#!HQd12QYY!wuM2FvxmScI8rQIdosPaS6CLcvI4-yJNHHOiR3Rv0I0)
4. Open Odin click AP button, choose the file you downloaded and then click start.
5. Your phone will reboot, shut down your phone and try to boot into recovery (hold volume up and home and then press and hold power button release the power button when the blue text appears but keep pressing volume up and home, release those when the screen goes black).
6. You should now be in your chosen recovery.
Click to expand...
Click to collapse
You are giving him instructions for the I9505. I think he has a I9505G, so he should not follow your instructions. You are giving him a recovery for the I9505. The I9505G is a different model.
If Heimdall fails to communicate with your phone, then you don't have the correct drivers installed. TWRP doesnt have a non touch version. So my guess is that you flashed the recovery for a different device.
If the phone is already rooted just use ROM Manager or TWRP Manager apps from Google Play.
Both will just wipe out and overwrite any existing recovery image and replace it with the one you want. Problem solved right from the phone. No ADB shell needed.
Thanks guys. I managed to flash both philz (That link you gave me, although it is for I9505 and I do have a I9505G) and TWRP.
Both work, but besides them the phone is completely bricked.
Jon-G said:
Thanks guys. I managed to flash both philz (That link you gave me, although it is for I9505 and I do have a I9505G) and TWRP.
Both work, but besides them the phone is completely bricked.
Click to expand...
Click to collapse
If you can boot to recovery the phone is not a complete brick.
Once you are in recovery you can flash anything you want. You should be able to flash any new ROM and it will boot right up.

[GUIDE]Oneplus X MAC Root Guide

This guide will help mac users with rooting their Oneplus X
BEFORE STARTING!
This could void the warranty of your device.
I won’t be held responsible for anything that happens from doing this tutorial so please proceed at your own risk.
All your data will be erased, so please make a back-up!
Please enable usb debugging in developer options(tap 7 times on build number).
Connect your phone to your mac and you will see Oneplus Drivers in your finder.
Double click on AndroidFileTransfer(OSX).dmg
Drag Android File transfer to the programs folder.
Step 1: Setting up ADB and FASBOOT and unlocking the bootloader
- Power off your phone and hold power button+volume up
- The phone should enter fastboot mode
- Go to https://drive.google.com/drive/u/0/folders/0B-baud5R8XkwLWYxcHNmbGZTY1U
and download the 3 files.
- Go ahead and unzip fastboot.zip then copy over the recovery.img file into fastboot folder.
- Open Terminal
- In Terminal type the following with hitting enter at the end of each line:
cd downloads
cd fastboot
chmod 755 *
./fastboot-mac oem unlock
- Your phone will reboot and you will be asked to unlock the bootloader. Just hit the Power button and unplug
your phone
- Phone will reboot
- Setup your phone
- Copy the UPDATE-SuperSU-2.78.zip to the internal storage of your OnePlus X using Android File Transfer.
- Power off your phone and hold power button+volume up, you should enter fastboot.
- Re-connect the USB cable once in fastboot mode.
Step 2: Flashing custom recovery and rooting
- Open terminal
- In Terminal type the following with hitting enter at the end of each line:
./fastboot-mac flash recovery recovery.img
./fastboot-mac erase cache
- Wait for it to finish and unplug your phone
- Hold down power and volume down for 20 seconds.
- The phone should boot into recovery.
- Once in TWRP recovery, choose “Install”
- Choose the Super SU zip file you copied over to your phone earlier.
- Swipe to flash.
- Choose “Reboot System”.
- If twrp asks your to disable stock recovery, swipe to disable.
YOUR OPX WILL REBOOT AND IS NOW ROOTED!
To check, open to superSU app and check for errors, no errors=rooted!
Thanks to https://theunlockr.com/ for the windows tutorial.
Need help ? Post a comment and I will help. :good:
Noticed spelling mistakes? Please let me know
ᕕ( ಠ‿ಠ)ᕗ
Just hijacking this post here to say, way to go buddy !
jk, reserved
Sorry guys, I know this is a very old thread but I've tried this so many times and did not work. My problem is that nothing happens in my device when I type the command to unlock the bootloader using Terminal.
I get the following message: Brunos-MacBook-Pro:fastboot Brunolima$ ./fastboot-mac oem unlock
...
OKAY [ 0.001s]
finished. total time: 0.001s
Brunos-MacBook-Pro:fastboot Brunolima$
And then that's it. It doesn't reboot and when i manually reboot it is in the same state as before.
Any ideas guys?
Hey, I've been trying the same thing. Didn't have your specific issue but I think it may be related to the fact that it's already unlocked.
That said, I to make everything work I basically used this guide + the commands from the official TWRP guide at the page "TWRP for OnePlus X" + the command from a guide in the official OnePlus guide called "[GUIDE] ONYX: How to Unlock Bootloader, Install Custom Recovery, Root, Take EFS Backup & More !!" --- sorry but I can't post links.
All in all the commands I've used where:
adb reboot bootloader
fastboot devices
fastboot oem unlock
fastboot oem device-info
fastboot flash recovery twrp.img
fastboot boot twrp.img
brunolimaam said:
Sorry guys, I know this is a very old thread but I've tried this so many times and did not work. My problem is that nothing happens in my device when I type the command to unlock the bootloader using Terminal.
I get the following message: Brunos-MacBook-Pro:fastboot Brunolima$ ./fastboot-mac oem unlock
...
OKAY [ 0.001s]
finished. total time: 0.001s
Brunos-MacBook-Pro:fastboot Brunolima$
And then that's it. It doesn't reboot and when i manually reboot it is in the same state as before.
Any ideas guys?
Click to expand...
Click to collapse

Yotaphone 2 soft bricked, step-by-step help

Yotaphone2 from china
YD206-> YD201
android 4.4.3-> Firmware 5.0.0-EU1.187a.zip
Hello, first post!
I bought my first android phone and ofcource tried to upgrade it to Android 5.0 Lollipop using yotaphone flasher program. I ended up to a jammed android logo ->softbricked phone..
The problem was finally solved by using fastboot program. You can find it in yotaphone_flasher folder, which you probably already have if you're in this situation.
So I do not recommend trying to update OS using yotaphone flasher, I would use fastboot, it is easier than you think and above all it seems to be the safest way to update as fas as i know.
If you want to know more about the fastboot: https://forum.xda-developers.com/showthread.php?t=2277112
This is a walkthrough made by androidnoob. Use at your own risk:
Download yotaphone flasher if you don´t allready have it: ftp://fw.ydevices.com/YotaPhone2/YotaPhoneFlasher/
Install yotaphone_flasher.exe and use it to download the firmware.
The default folder is C: Program Files (x86) / yotaphone_flasher, in that folder you will find fastboot.exe and firmware folder.
Copy the following files from the firmware folder to yotaphone_flasher folder (same folder you have fastboot.exe), you will need them later in the updating phase:
userdata.img
system.img
boot.img
Make sure that Yotaphone 2 is in downloading mode:
Simultaneously press the power + vol down until the display reads downloading. It may take more than one reboot so keep pressing until it appears.
Connect your phone to a computer via USB Cable.
Open the fastboot.exe. You can only do it in the command prompt, so press shift + right mouse at yotaphone_flasher folder-> Choose to open a command prompt. (Now you have to press enter after every command line)
In the command prompt, type the following:
fastboot
fastboot devices
If you see your phone's serial number, the connection works.
Start wiping memory, type:
fastboot erase system -w (this will erase everything, including your user data)
fastboot erase boot
And it´s time to install the update, type:
fastboot flash userdata userdata.img
fastboot flash -S 512M system system.img (For me installing in parts was a game changer. It´ll take some time so don´t panic)
fastboot flash boot boot.img
fastboot reboot
Yotaphone 2 will reboot. Wait 5-30 minutes, and the update is complete! Later my phone automatically updated 5.0.0-EU1.124b, so you can probably download this firmware using yotaphone flasher at the beginning of this process. I haven´t yet installed a sim so no idea if there are more issues.
This walkthrough has been compiled from various sources, so thanks to all for sharing! Hope this helps someone in trouble.
Yes, you can update your phone using manual fastboot commands. For convenience, a 4pda user rewrited YotaFlasher to a more polished version, making it flash system fastboot flash -S 512M system system.img command. I uploaded the new YotaFlasher in this guide.
You saved my day, the other methods did not work, I must add that it must be exclusively with the original cable, the others still with the error of "powered by android"
sotka said:
And it´s time to install the update, type:
fastboot flash userdata userdata.img
fastboot flash -S 512M system system.img (For me installing in parts was a game changer. It´ll take some time so don´t panic)
fastboot flash boot boot.img
fastboot reboot
Click to expand...
Click to collapse
Hi, Could you tell me how to install the system.img in parts? I have a 1.4gb system.img file that I am trying to install on a bootlooping Yotaphone 2.
I keep getting a "Invalid sparse file format at header magi" when I do the second step, which I think is linked to the .img being too large. But I have no idea how to make it smaller. Thanks for any help!

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

Categories

Resources