yashsingh1/xdaforums huggingface dataset:
[Shield Android TV Android Development] ACiDxCHRiST:
During setup it will force you to install the latest update before you ever get to the home screen, or have control. Not sure if setting it up without internet is possible but that would be a way to avoid updating it. By the time you see the screen telling you to update during the initial setup, it is too late to disconnect the internet as it has likely already downloaded it in the background.

You can always grab the developer images from NVIDIA's site and flash whatever version you want through fastboot as long as your bootloader is unlocked without losing any data. But if you haven't unlocked the bootloader yet, unlocking it will trigger a data wipe.
[Shield Android TV Android Development] bp328i:
Thanks I found that out. I flashed back to 7.2 but then was like if I can't root yet might as well take the update back to 7.2.1, so yeah I just wasted time flashing 7.2.

But now that I see a post or two above about rooting 7.2 with Magisk I might give that a go.
[Shield Android TV Android Development] TheUndertaker21:
No if you use patch boot.

Do a quick Google search you'd know more about it.
[Shield Android TV Android Development] ACiDxCHRiST:
Negative Ghostrider, DO NOT TRY IT WITH THE 2017. Magisk + 7.2 on the 2017 will bootloop.
[Shield Android TV Android Development] bp328i:
I was going to try on my Pro. Do you know if anybody has tried on the Pro yet?
[Shield Android TV Android Development] ACiDxCHRiST:
Oh, ok then, carry on.
[Shield Android TV Android Development] darkuni:
I'm too old to learn something new ... I guess I'll wait for TWRP to get fixed. :D
[Shield Android TV Android Development] bp328i:
Have you heard of anybody trying it on the Pro yet. I just flashed back to 7.2, just waiting on getting your apps ready screen.

---------- Post added at 05:24 AM ---------- Previous post was at 04:27 AM ----------

I just did the same on the Pro with 7.2 and Magisk 18 worked fine.
[Shield Android TV Android Development] ACiDxCHRiST:
I wonder why it works on the Pro but not the 2017.
[Shield Android TV Android Development] darkuni:
I think there is voodoo nonsense in the 2017 firmware. After rooting my 2017? I constantly get told every power up that my system is compromised and I could relock everything. Sucks. Google crap I'm told.
[Shield Android TV Android Development] nanerasingh:
2017 model. I flashed devloper rooted 7.2, in setupwizard it download 7.2.1, before ging to launcher screen it ask to restart as update finished.but i power off directly. It ask again to install 7.2.1. I click install but i power off it directly AGAIN when it booted on the Screen for unlockbootloader(note) then pwer on. After boot it asked to install later selection. Then double click your remote home button or click home button and you will be on launcer screen and enable adb debugging. Adb root works.

In this way i am still on 7.2 with adb root. You guys try same.

After getting root i disable com.nvidia.ota and clear the update data. Now no more update notifications.
[Shield Android TV Android Development] Mogster2K:
The Pro hardware was not changed when the 2017 model was introduced, so it is nearly identical to the 2015 16GB model.

Also, we should probably take the Magisk discussion to a new thread. We're cluttering up Steel01's thread with unrelated stuff. :-/
[Shield Android TV Android Development] SyberHexen:
I have a shield 2017 "Darcy" running 7.2 dev rooted with magisk no problems here

I manually patched the 7.2 dev rooted boot image with magisk manager app on another device

From bootloader

fastboot boot boot.img

After device booted, I installed magisk manager from USB drive.

Then installed magisk to boot thru magisk manager.

Felt like this was a round about method as you could flash boot.img from the bootloader as well.. but I like to test boot before flashing and didn't feel like rebooting
[Shield Android TV Android Development] ACiDxCHRiST:
Wow. Would you send me the boot.img that you originally booted from?
[Shield Android TV Android Development] SyberHexen:
Yes can do.

Try this

https://drive.google.com/file/d/1flHgSLRTs1E6jfOS_WVRUsDb-pcjHJV-/view?usp=drivesdk
[Shield Android TV Android Development] ACiDxCHRiST:
Well, holy ****. That worked. I decided to skip 7.2 and just try to reproduce your method on 7.2.1 and it worked fine.

I grabbed the full update OTA from my Shield and extracted the boot.img from it. I put the boot.img on my Pixel 2 XL running Oreo and patched it with Magisk v18. I copied patched_boot.img back to my PC. After I finished updating the Shield to 7.2.1, I hit it with a

'adb reboot bootloader'

'fastboot boot patched_boot.img'

I opened Magisk Manager, did a Direct Install of v18, then rebooted.

I don't know if I could have done 'fastboot flash' instead, but the fact that it booted tells me that patching it from my phone and not the Shield is what made it successful. Thanks for the info man. I am up and running on the latest Shield Update with Magisk root on a 2017.
[Shield Android TV Android Development] SyberHexen:
Wow legitt! :svetius:

Honestly I'm pretty sure I tried same method for 7.2.1 and I got stuck at the logo.

Any chance that you could dump your magisk rooted 7.2.1 boot.img ?
[Shield Android TV Android Development] ACiDxCHRiST:
I figured it out. AVB (Android Verified Boot). I feel so stupid because I should have known this was probably the issue. Starting with Shield Experience Upgrade v7.2, you need to have the "Preserve AVB 2.0/dm-verity" option checked when you click Install in Magisk Manager to patch the boot.img

I ran through the whole process from the beginning on one of my Shield TVs.

Download the FULL OTA (Make sure you have the "Provide full system upgrades" option selected. It is the very last option in the DEVELOPER OPTIONS menu)

Extract the boot.img from the OTA

In Magisk Manager, check the box for the "Preserve AVB 2.0/dm-verity" option

Click Install and select your boot.img

Copy patched_boot.img to PC

Install the OTA on the Shield

Once update is finished and back on the home screen,

'adb reboot bootloader'

'fastboot flash boot patched_boot.img'

'fastboot reboot'

Works perfectly.
[Shield Android TV Android Development] whiteak:
*** deleted post***
[Shield Android TV Android Development] sconnyuk:
Hello guys hoping someone can shed some light here for me.

I just purchased an Nvidia Shield 2017 16gb model and after initial setup it upgraded and did so again so I'm currently running 7.2.1.

I have looked at the guide to root on here but for some reason can't get the driver's correctly installed on my computer (tried 2 computers and 2 A to A usb leads, it recognises ADB commands i.e: ADB devices lists my device and I can get it to reboot to bootloader correctly but while at bootloader screen my computers device manager shows a yellow triangle to which trying to install driver gives me error code 10 device cannot start.

I've bootloader and erased my data (as expected) but after a little more reading it seems as though I cannot install (even if I get my driver situation sorted out) twrp as it isn't compatable with 7.2.1.

Can someone please :

1: Tell me if I'm able to root this somehow and any help would be very grateful.

2: Let me know if I'm doing anything wrong with ADB driver installation ?

Thanks alot guys.

*edit*

Having read the latter comments in here ive managed to get adb working (although everytime i boot into bootloader i normally have to uninstall the driver then reinstall it, unsure if this is normal?)

From what ive read im now able to flash a modded boot.img which i have tried but now get an error while trying to flash it:

C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash boot boot.img

target reported max download size of 67108864 bytes

sending 'boot' (14115 KB)...

FAILED (data transfer failure (Unknown error))

finished. total time: 5.017s

Anyone shed any light on this for me please ?
[Shield Android TV Android Development] ACiDxCHRiST:
Download the drivers from here: http://developer.download.nvidia.com/mobile/shield/SHIELD_Family_WHQL_USB_driver_201801.zip

Extract that to a folder somewhere. Use the included PDF for basic instructions to install. You will have to do it twice, once for adb while the Shield TV is booted, and then again while the Shield is in fastboot/bootloader mode. That will get rid of your yellow triangle. You should not have to uninstall/install the drivers again once they are both installed correctly.

Download the SDK Platform-Tools directly from Google here: https://developer.android.com/studio/releases/platform-tools

Ever since Google started offering the SDK Platform-Tools to download separately from the whole SDK, there is no reason to use Minimal ADB anymore.

'adb devices' and 'fastboot devices' commands can be used to verify your drivers are installed correctly.

Once your environment is setup, you can follow the instructions from my last post to get root with Magisk.
[Shield Android TV Android Development] sconnyuk:
thanks for the help, but my new problem is the error failing to transfer, this is happening on two different computers and using/trying two different A to A cables.

after the drivers have installed, i can 'fastboot devices' and it correctly shows but my next command to send over the modded image as above a few posts always fails.

I have modified my post to show the error and wondering if you might know the cause of it ?

Thanks.
[Shield Android TV Android Development] ACiDxCHRiST:
Install the latest SDK Platform-Tools tools that I linked. The version of fastboot that you have may not be updated.

Once you extract the platform-tools folder, follow these instructions: https://helpdeskgeek.com/windows-10/add-windows-path-environment-variable/

Put the platform-tools folder to your System PATH variable and that will allow you to invoke 'adb' and 'fastboot' commands from anywhere without having to worry about providing the full path to adb.exe or fastboot.exe on the command line. This is not required, but makes things a lot easier.

Is your bootloader unlocked? If not, it needs to be unlocked. Be warned, that unlocking it will trigger a data wipe, and all your data will be lost.
[Shield Android TV Android Development] sconnyuk:
Ive copied the platform tools folder to the root of my C: drive and im just about to edit (add) the variable. do i just point it to C:\platform tools ? or does it need to be %SystemRoot%\C:\platform tools ? sorry but this isnt something ive done before and it only mentions basics in the guide.

Yes is the answer to my bootloader being unlocked, when in bootloader mode, i used controller to scroll down to 'unlock bootloader' to which it did and rebooted/wiped all my data.

Still having issues after following your instructions with the driver install, i have to uninstall everytime i get to fastboot mode, sometimes it wont install correctly. im hoping this what im trying what you have suggested works ?

Anyway i appreciate your help.

*edit*

Followed your instructions and this is what im getting:

C:\platform-tools>fastboot devices

0324418110831 fastboot

C:\platform-tools>fastboot flash boot boot.img

Sending 'boot' (14115 KB) FAILED (Write to device failed in SendBuffer() (Unknown error))

Finished. Total time: 5.041s

Forgot to mention im using whiteak's pre modded boot.img from a few posts up.
[Shield Android TV Android Development] MrCrc:
Hi,

is there a possibility to get (Magisk-patched or not) boot.img of 7.2.1 for foster model (2015)?

Why? I bought a box on ebay (factory reset was done by seller) and i do not found an update file on internal storage with es file manager). Now I am on 7.2.1...

regards

Crc

Gesendet von meinem ONEPLUS A5000 mit Tapatalk
[Shield Android TV Android Development] ACiDxCHRiST:
You should not need to uninstall the driver, the device that shows up with a yellow triangle is a separate device from the adb mode device. Both of the drivers are in the same folder but you will need to install them twice. Once when in adb mode, then reboot to bootloader and go to device manager again, right click on the different device that has the yellow triangle, Update Driver, and "have disk", navigate to the folder with the driver, and OK.

As for the PATH, specify the full path to the folder. C:\platform-tools

You can grab the 7.2 image off of NVIDIA's site, extract it to a folder, install it using Fastboot, copy the boot.img to your Shield TV storage. Install Magisk Manager, patch the 7.2 boot.img with the "Preserve AVB 2.0/dm-verity" option checked, copy patched_boot.img back to your PC, reboot Shield TV to bootloader, 'fastboot flash boot patched_boot.img', then 'fastboot reboot'. Enable Developer Options and enable the very last item in Developer Options which is "Provide full system upgrades", Check for Update and download it but don't install it, Install a Root Explorer and navigate to /data/data/com.nvidia.ota/app_download, open the ZIP file in there and extract the boot.img, Use Magisk again to patch it making sure the "Preserve AVB 2.0/dm-verity" option is checked, copy patched_boot.img back to your PC, Install the OTA on your Shield TV, Reboot Shield TV to bootloader, 'fastboot flash boot patched_boot.img', then 'fastboot reboot'
[Shield Android TV Android Development] sconnyuk:
I do understand your helping me and i do really appreciate it, i do the same when im on here if there is anything i can help with others. i have renamed the platform-tools folder to platform tools, that is why i have left out the - .

I also understand that the driver needs installed twice, and i think it has installed correctly now as when i boot to bootloader it is recognised without any fuss.

I still have issue with failing to flash from within bootloader mode/fastboot. It fails everytime.

The boot.img im using is from a post on page 16 on this thread, could that be my issue ?

I cant rule it out at the moment because i do not know the password google allocated to my nvidia developer account, therefore i cannot download the developer 7.2.0 and extract my own boot.img from there (unless you could upload a virgin 7.2.0 boot.img i could try patching it myself ?

Again thanks alot for your help i really want magisk on this box :)
[Shield Android TV Android Development] ACiDxCHRiST:
I don't know what to tell you man. Here is a Magisk v18.0 patched Shield Experience Upgrade v7.2.1 boot.img for 2017 Shield TV: https://drive.google.com/open?id=1ZW6GdL1ppNaoEM3IGlgdUvDJCRf4R8_m

-Edit

I removed the download as I don't want people randomly downloading and trying it without making sure that it specifically matches their model.
[Shield Android TV Android Development] sconnyuk:
Excellent I will try this.

By the way, there isn't any reason for me to be on a developer ROM is there ?

As I'm only on stock 7.2.1.

I'll let you all know how it goes with this boot.img you have given.

Thanks alot.
[Shield Android TV Android Development] ACiDxCHRiST:
The pre-rooted Shield TV Developer OS Image only enables SU over ADB. Magisk will allow ADB and Apps to use SU. So no, there is no need for a pre-rooted Developer Image. A Magisk rooted Retail OS will have more capability than a pre-rooted Developer OS.
[Shield Android TV Android Development] sconnyuk:
Thanks for uploading that unfortunatly i get the same output with it:

C:\Users\sconn>fastboot flash boot patched_boot.img

Sending 'boot' (14115 KB) FAILED (Write to device failed (Unknown error))

Finished. Total time: 5.016s

I appreciate all the help but im stumped.

I will have to try in the morning as its getting late.

Thanks again.
[Shield Android TV Android Development] ACiDxCHRiST:
I have posted a full [GUIDE] to rooting v7.2 with Magisk in General. It also has the information on how to update to v7.2.1

https://xdaforums.com/shield-tv/general/guide-root-nvidia-shield-experience-t3882254

Any further discussion that doesn't involve TWRP should be directed there so that we don't continue to clog up Steel01's thread.
[Shield Android TV Android Development] nadia p.:
Hello Steel01, I wanted to thank you for all your effort and support here.

In reading through the threads for this topic I find it difficult to learn which version of TWRP works with which version of Android & Nvidia OS on the various platforms of Shield TV. Is there a way to list this in a sticky post here or perhaps there's another page/site that contains this information? If there was something like this for example it would help people quite a bit.

TWRP 3.2.3.0 for Shield TV*

SHIELD TV 2017 (16GB) rooted, unrooted, installed on device, booted only. All confirmed working...

SHIELD TV Pro (500GB)

SHIELD TV 2015 (16GB)

SHIELD TV China

Please forgive my ignorance as I'm still learning. Sadly I have not attempted to install or use TWRP 3.2.3.0 (latest) on my 2017 (16GB) device since from the reports I've read say that it's not working. I've not found anything so far to confirm that it is, and under which conditions, which OS, etc... . Does this make sense?

Per your suggestion I have also tried researching this information on Team-Win-Recovery-Project however there isn't an easy way, that I have found, to filter the information specifically to Shield TV and more specifically to the 2017 (16GB) model I own.
[Shield Android TV Android Development] Steel01:
TWRP should work on all variants, even dev boards. I posted about this a couple pages ago. I personally have foster_e_hdd and darcy. There's only a coupe instances where the latest version won't work. First is on 4k TVs and fixing that is... not easy. Secondly is devices with stock 7.2.x or newer. The bootloader and kernel majorly changed, so I'm going to have to rebuild stuff once the source drop happens. Still... Waiting...
[Shield Android TV Android Development] darkuni:
They are really trying the goodwill of the community by holding on to that source code.
[Shield Android TV Android Development] Steel01:
Last time I asked about it, an 'approval' process was mentioned. So, I'm not on the inside and as such can't say anything for certain. But just hearing that word makes me wonder how many non-engineers have to check boxes before the public ever sees code.
[Shield Android TV Android Development] Downunder35m:
I was able to get TWRP working after manually porting and slightly modifying files from the new stock recovery.

Not really too hard as it only involves matching the fastab files to the plat and non plat files and the usual other suspects.

Backups work fine but all write access fails or results in corruption.

But the problem is not entirely the new kernel and bootloader.

There is a "backdoor" to gain full root access on the 7.2 firmwares and all it takes is the right DTB.

Well, that and of course making sure the entire system is installed without encryption and verity to start with.

For that a zip is available.

It should be relatively easy to include this into TWRP so it will work on unprotected and unsecure devices.

After all, if we root we already want those restrictions to be gone.

Enabling all TWRP features on the new stock kernel and system might be hard though.

I contacted the Nvidia support several times inregards to the false rooting statements of the 7.2 developer firmwares and the lack of sources available.

At first they were unaware of the rooting problems then just stated that they would not actually support rooting anyway....

As for kernel sources and after trying hard a few times I was informed that currently they see no rush for releasing them as the majority of changes are just conform with the latest Google requirements.

The rest is closed source and won't be published anyways.

Seems like they are considering to close the doors for true rooting to protect the system.
[Shield Android TV Android Development] darkuni:
Thanks for all the efforts with this!

When you say system isn't encrypted - you're talking about the Android system encryption, right? That's an "opt in" thing currently, right? MOST of us aren't going to be.

If I'm reading this right - you're saying we have a shooting solution; but there are more parameters around making this work. ... and there is more system/version specific nonsense "per bootloader" we have to deal with; meaning that if you release a TWRP that supports 7.2 ... it may not support 7.2.x or 7.3 ... etc?

If you need testers, let me know. Be happy to help.
[Shield Android TV Android Development] nadia p.:
Sorry to post this question but I've not been able to boot to TWRP after following these steps. I was wondering if there was a specific guide for Shield TV 2017 (16GB) remote only (with USB keyboard & mouse)?

ADB method

adb reboot bootloader

fastboot flash recovery twrp-3.2.3-0-foster.img

fastboot reboot

hold down both A and B keys at the same time to boot into the fastboot screen.

from here I can't figure out how to boot to TWRP.

APK method

transfer me.twrp.twrpapp-26.apk to /storage/emulated/0/Download/

navigate to the Downloads folder using ES/X-plore file manager and launch the TWRP application

the TWRP menu pops up, check [x] appropriate boxes, next screen is to patch, backup, etc...

I believe the correct thing to do is to first backup the entire system, which I tried but then got stuck at selecting the folder to output the recovery.img file into. I navigated to /storage/emulated/0/Download/ but couldn't figure out how to finalize this step to tell TWRP it's this folder to continue.

---------- Post added at 06:49 PM ---------- Previous post was at 06:45 PM ----------

I forgot to include I have read and attempted to following the instructions posted HERE on TWRP's site following the ADB method but it did not reboot into TWRP for some reason.
[Shield Android TV Android Development] Downunder35m:
@ nadia P: The pure basics to get TWRP working again on 7.2 are not that hard.

Won't work with lower firmwares but should still work with upcoming ones until Nvidia makes drastic changes again.

Only real downer is still the faulty write access but if it won't involve building it from scratch TWRP should be available soo for testing.

In the meantime I am sure the official support will catch up too and provide a proper solution
[Shield Android TV Android Development] nadia p.:
My Shield TV 2017 (16GB) is currently on Nvidia 7.1.0. So I hope to find a solution for that. I don't plan to update to 7.2.x since it breaks other Apps that I use. Following the APK method it seems to launch ES file manager then it's stuck there even after navigating to Downloads. With only a mouse I can't figure out how to tell TWRP Manager that's the folder to continue. There's no way, that I could find, to quite ES and switch back to TWRP Manager.
[Shield Android TV Android Development] Mogster2K:
Zulu99 mentioned something similar - that dm-verity was enabled in darcy's DTB file, preventing any custom firmwares from executing. Foster does not seem to have this problem.

He's provided a patched DTB here - use at your own risk: http://bit.ly/2CxB1hS (WARNING! ONLY FOR 2017 DARCY MODEL!)

Original post here.
[Shield Android TV Android Development] J85maurice:
So I also own a minix u1. It is 4k as well and the twrp I have flashed on it supports 4k tv's. Is there anyway to fork this version for the shield? Once all the newest firmware is sorted out of course... Luckily I have an old 1080 tv at my house lol
[Shield Android TV Android Development] nadia p.:
TWRP 3.2.3.0 foster with Nvidia 7.1.0

Hello Downunder35m, If it is not too much trouble can you (or someone) please point me how to get TWRP 3.2.3.0 foster with Nvidia 7.1.0 by using a USB keyboard and USB mouse, since I own the 2017 Remote Only model? Is there a step-by-step guide or video showing how to install and get this working?

In addition if there are certain modifications that need to be done so I'm able to backup and recover that backed-up data please let me know that too.