yashsingh1/xdaforums huggingface dataset:
[Shield Android TV General] elliwigy:
i updated my nstv pro 2019 version from 20.3 to 20.4.. had to manually bind mount system then installed 20.4 magisk.zip
[Shield Android TV General] kings121:
Is there any info on rooting the 2015 shield tv pro on the latest android version?
[Shield Android TV General] DumbKing@letthemeatspam:
Sorry for late response did not see till now. The latest stable Magisk 7.5.1 and Magisk 20.4 works just great! Let me know if you need help
[Shield Android TV General] shaheen7m:
Can i root my shield pro 4K 2019 with thus guide? I am not able to find the right firmware from Nvidia site.
[Shield Android TV General] elliwigy:
the most recent firmware for nstv pro 2019 model was pushed in march 27th, is 8.1.1 and can find it here:

https://developer.nvidia.com/gameworksdownload

you can also dl tye developer firmware at that link
[Shield Android TV General] shaheen7m:
Thanks mate, will try this today. Developer or recovery image should i get? Any advice?
[Shield Android TV General] elliwigy:
recovery firmware is stock. Developer firmware is userdebug.. it depends on what youre looking for
[Shield Android TV General] shaheen7m:
Thanks mate. I assume i need developer firmware for this purpose... Thanks
[Shield Android TV General] elliwigy:
that doesnt matter.. both can be rooted
[Shield Android TV General] shaheen7m:
Wow.. perfect... If the stock can be rooted, why the stock already shipped with shield pro can't be? If the shipped firmware can be, i can skip some steps... Sorry for the silly questions
[Shield Android TV General] elliwigy:
stock firmware can be rooted, no one ever said it couldnt be
[Shield Android TV General] shaheen7m:
Makes perfect sense. Thanks for being patient and replying to my every silly questions... Can't wait to root my device and try rclone..
[Shield Android TV General] wildnux:
Hi, I have a Nvidia Shield TV 2017 and I had been using magisk to patch boot image and flash the patched boot image using fastboot before Shield Experience 8.0. After Pie, it stopped working and I had gave up on root for sometime now. Today I got Shield Experience 8.2 update and the recovery images are also available so I gave it a go again. I tried patching boot.img and recovery.img as well (using recovery option), but each time after I flash and reboot, magisk manager shows magisk is not installed. I am using latest canary magisk manager.

Is there a way to make magisk work with Nvidia Shield TV 2017 with Shield Experience 8.2?
[Shield Android TV General] DumbKing@letthemeatspam:
I am also interested in this... anyone figure it out?
[Shield Android TV General] elliwigy:
flash it in twrp
[Shield Android TV General] tinhsoftware:
Do you twrp flash magisk stable or canary build? Thank
[Shield Android TV General] elliwigy:
ive used both.. older versions didnt work
[Shield Android TV General] George@xda:
Hi, I rooted my Shield TV 2017 with Shield Experience 8.2 by flashing a patched boot.img, witch I made on my rooted Phone with MagiskManager v7.5.1.apk and Magisk v20.4. Everything works well!
[Shield Android TV General] pop4xda:
Flash that patched boot.img via trwp recovery?
[Shield Android TV General] George@xda:
I flashed with fastboot flash boot magisk_patched.img.
[Shield Android TV General] DumbKing@letthemeatspam:
so just to be clear you followed guide at beginning of this thread using latest version of Magisk and the Developer Images and it worked? Thank you!
[Shield Android TV General] George@xda:
With a small deviation: E.5 to E.10 I performed on another Android system.

On the Shield I completely installed the developer upgrade 8.2.0 with flash-all.bat, according to NVIDIA instructions, before flashing only magisk-pached(boot).img with fastboot.

And yes, it worked.
[Shield Android TV General] cHECKjAM:
Hey mate. You seem to know a lot about this.

So if both developer image and stock/recovery image can be rooted, what are really the difference between them? What are the usecases or downsides for the developer version?

I want to go for the developer version just because you can skip google login on this version I have heard, but are there any downsides for me to use the dev version compared to stock/recovery?

Also why do people root in general for the nvidia shield TV?

I have the 2019 PRO model and I would like to root to be able to mass uninstall a lot of the crap that is preinstalled since Im not gonna use any of them. Is this possible without root?

Also I would love to get AFwall or any other firewall running on the shield but I dont think it works. Do you know of any way to get firewall functions in there_?
[Shield Android TV General] cHECKjAM:
First page says to not lock bootloader unless default nvidia rom. But what about the official nvidia Dev rom?

The new 2019 pro will not have ai upscaling enabled unless locked bootloader.

Also with Dev room can I just install magisk manager through a normal apk install and have it give root?

Thinking if that would not require special image then and just use latest dev room that has root. Put on magisk and then lock bootloader..?
[Shield Android TV General] George@xda:
Hi there, because you have written to me with a PM, I would like to share a few thoughts on this subject in general. First, I rooted a Shield TV 2017 as described using the developer OS. Unfortunately, I don't know if this approach works with the Shield TV 2019 Pro. Secondly, the APK's installed by me, that require root access, work well on my Shield TV 2017. I guess that would also work on a rooted Shield TV 2019 as well. If you may use the method described here to root your Shield TV 2019 Pro, I'll also consider buying this box to use AI, even if I would have to lock the bootloader afterwards.
[Shield Android TV General] cHECKjAM:
Hey Buddy.. nice to see a response!

Mate I have a hard time understanding everything..

1. If using dev image what is the minimum amount of effort needed to run something that requires root, like AFwall? Do you really need twrp and doing stuff through there?

2. Can you lock bootloader if using dev image?
[Shield Android TV General] George@xda:
1. An installed developer OS should be additionally rooted so that APK's that need root can work well. But I really can't say what stable method is needed to root the Shield TV 2019 Pro.

2. You can lock or unlock the bootloader with developer OS as often as you want. Always when you unlock, you lose all users data.
[Shield Android TV General] cHECKjAM:
I tried adb install AFwall+ on the developer image but it claims to be missing root.

So I did what you said above and patched the boot.img on another device with magisk 20.4

then in fastboot I did the fastboot flash magisk_boot.img

now stuck in bootloop.. Dunno how to get out of it.. Guess I have to disconnect harddrive and connect the keyboard in there now and boot it up to fastboot that way. Then reflash everything...

Just annoying that I dont seem to understand how to get root on this latest developer image.. And the only active person in the entire community last 10 days has been you.. This place is virtually dead..
[Shield Android TV General] cHECKjAM:
Anyone managed to root a 2019 Pro model with 8.2 Dev image yet?

I really want to be able to put magisk on this machine to be able to run apps that require root on it.
[Shield Android TV General] ldeveraux:
I'm sure you checked here, saw it hasn't been rooted yet, and decided to ask again? :D

I think this is the best you'll get
[Shield Android TV General] pinkBEAT:
Is this still relevant for 8.2.0 Shield version on a 2017 Shield?

Hello, I have a 2017 Shield...16GB. Looking to root it....first time rooting anything. Want to be thoroughly informed b4 proceeding. About 4 months ago I add a 500GB Seagate Fast SSD drive and adopted it as Internal storage because there were a lot more apps I wanted to install and I wanted to get off the adopted thumbdrive. Then I decided I want to use the Plex server on Shield instead of my laptop so I don't have to always have it on. This is the problem I've run into that makes me want to root...If u tell the Plex server to save data to your external HDD it still saves certain data on Shield's internal drive which is eating up my Shield's internal storage quickly. Don't have the option to make it save all data to the adopted storage either and I thing a lot of apps are storing on Shield and not the ssd as well. So what the hell was the use of getting the SSD? Anyway, I've read that if u root it, delete the Plex server and download the Plex server app from the Google store, you can put it on the adopted storage and have its data stored there too as well. This would actually make use of the SSD as I thought it would work in the first place. Now I have to do a dog and pony dance just to have that logical function, otherwise Shield is useless as a Plex server to me. Damn, remote doesn't work half the time either. So, I've decided to try the root route. I'm on the Shield version 8.2.0 and want to make sure this still works, where to get the right updated files for my version and is it going to break any functions or services? Forgive me if I haven't read all 44 pages here. I've read 3 so far. Can't really find any updated info for 2020 regarding the 2017 Shield root. Just really aggravated I have to do this. I mean who thinks up that they will offer a Plex server as a feature, through a 16 GB drive in there, tell u that u can expand storage with an ssd then not let u move all that server data to said adopted ssd or all of it to even an external drive? I've only been able to set my movie library up and now I've only got 2.1GB left on Shield internal. Sorry, went off on a rant.
[Shield Android TV General] cHECKjAM:
Hey buddy,

Which TWRP file did you use?

Im planning to flash and root my 2017 Pro 16gb model with 8.2 developer image (developer image because I want to bypass google signin requirement).

I understand most of these steps but I dont know what TWRP we need to use for this process..? First page instructions of this guide does not mention it either.
[Shield Android TV General] George@xda:
Hi there,

I didn't use any TWRP file to flash and root my Shield TV 2017 (not Pro) 16 GB with 8.2 developer image.
[Shield Android TV General] cHECKjAM:
Thanks buddy.

I managed to get 8.2 Developer image flashed and rooted with magisk as well, on a Shield Pro 2017 16gb.

However I got a weird problem.. I did the same procedure on 2 devices, the exact same devices.

And none of them can actually connect to a bluetooth device. It never finds any bluetooth device when I search for them.

Does your device find bluetooth devices?

I think maybe the fact that I skipped google login has an effect on this.. In the setup screen I hit the combo Up Up Left Left and hit "skip setup" so I dont need to login with google account.

I need to reflash everything from scratch and try another method by [MENTION=5827138]mrhamed[/MENTION] to bypass google setup and see if that works.
[Shield Android TV General] George@xda:
Hi,

My box finds and works well with Bluetooth.
[Shield Android TV General] ldeveraux:
I don't know what you quoted, but don't do that. You can disable OTA updates in Titanium Backup by searching for "OTA" and "update" and disabling intelligently.
[Shield Android TV General] ldeveraux:
I completely misread the forum, thought this was for another device. You can ignore what I said previously, sorry!
[Shield Android TV General] Ghisy:
Hey, I have the same device and just updated to 8.2.2 Developer image but lost root.

How do I install Magisk 23 on this? Should I patch the boot.img on another device and flashboot flash it to the Shield TV?

I'm also interested in installing TWRP as well (I had it before updating) but I can't find an up-to-date guide anywhere.

Thanks!
[Shield Android TV General] twistedumbrella:
As long as your bootloader is unlocked, it really is as simple as patching the boot and flashing it to the device.

If recovery is still a separate partition (newer partition layouts moved it into the boot image), that is just like flashing a boot image using "recovery" instead of "boot" as the target.
[Shield Android TV General] Ghisy:
Yeah, my bootloader is unlocked. So I can just flash the patched boot.img then? Even though this is a dev build that's supposed to be pre-rooted?

Edit: I just flashed a patched boot.img and now Magisk states: "Abnormal state: An "su" command that does not belong to Magisk is detected. Please remove the other unsupported su".

I've never seen that message before!
[Shield Android TV General] twistedumbrella:
The system is rooted in the sense that it has a completely unrestricted su available, but most apps and such weren't designed to properly support that. What you can do is to move the "true root" su to a backup folder, but keep it in case you ever decide to drop magisk. It's unfortunate magisk doesn't adapt the same way that older superuser apps did, but that's one size fits all for you.
[Shield Android TV General] Ghisy:
So I flashed the stock boot.img again, I don't have this message in Magisk anymore. There seems be to be some kind of conflict between the Magisk patched boot.img and the one pre-installed by Nvidia in the developer image.

I wonder if maybe I should patch and flash the recovery.img instead. Magisk FAQ states that this should be flashed if the device doesn't have the ramdisk option (Magisk on my Shield TV shows "Ramdisk : No").
[Shield Android TV General] Neuken6969:
Hello hope this thread is not dead, I just got an 8gb shield tv (tube). Doing research I think it's called mdarcy, running pie. Can this be rooted??
[Shield Android TV General] Ghisy:
Doesn't NVidia offer the dev firmware for the 2019 model as well? It comes pre-rooted but only for adb apparently.

I have the 2017 model and I'm also searching for a way to use root on the latest (8.2.3) dev firmware. I can't seem to be able to install Magisk on this and no guide is up to date... :(
[Shield Android TV General] Neuken6969:
Sorry, my (tube) android tv 8gb is pre rooted? Or the dev files are pre rooted? I have a 8gb tube.
[Shield Android TV General] ¿GotJazz?:
Does the rooting process in the OP work with the latest Shield TV (2018) v8.2.3 Stock boot.img and Magisk Manager v23.0?
[Shield Android TV General] nebulah:
Successfully rooted 8.2.0 developer OS yesterday with Magisk 23 on 2017 Shield 16GB. The patch has to be on boot.img even those ramdisk:NO in the magisk app.

Got the error message around duplicate SU detected but root still seems to work ok.
[Shield Android TV General] jamiethomaswhite:
Well, now I'm definitely hoping this thread isn't dead. I use my Shield 24/7 literally, and right now it is bricked.

I naively followed this guide, as it seemed more up to date:

https://xdaforums.com/t/guide-8-2-3-magisk-root-magiskhide-twrp.4328569/

Unfortunately, as the comments below on that thread point out, the script has an error. Result: my my cherished sweetheart is now dead.

Alas, I have passed this point and the Shield is now no longer connected to or responding to adb or fastboot calls. Even connecting/disconnecting from the USB port I can't see any activity. I cannot get the combination to force it to boot into bootloader mode. I just get a solid green light the moment I plug it in and that's the only indication it's alive.

Please, please for the love of all that is entertaining, help me ;_;
[Shield Android TV General] George@xda:
I rooted the 9.0.0 Developer OS with Android 11 on my Shield TV 2017 yesterday using the method described by me earlier here for 8.2.0. And this time I pached with Magisk 23. It works great.
[Shield Android TV General] Ghisy:
Wait, Android 11 is available for the 2017 Shield TV? I don't see it on NVidia's page!
[Shield Android TV General] George@xda:
You are right. It's gone again. Maybe this link can give a hint:

Nvidia releases recovery images for Shield Experience 9.0.0 based on Android 11, OTA rollout imminent

Shield Experience 9.0.0 recovery images are now available for the Shield TV 2019 Pro, Shield TV 2019, Shield TV 2017, Shield TV Pro 2015, and Shield TV 2015.

www.xda-developers.com
[Shield Android TV General] Ghisy:
I found a sub Reddit explaning that NVidia took the images down. They're probably beta firmwares that weren't supposed to be released yet.

I might actually wait until it officially drops again. My Shield TV works fine, don't wanna risk botching it.
[Shield Android TV General] joshworx:
Hey guys, I'm just wondering, is it supposed to hang at the Nvidia logo, or did the flashing process not work in that case?
[Shield Android TV General] Largewoodenspoon:
Right, I'm confused now.

My question is this :

Can I update from 7.0 (fully rooted magisk) to latest nvidia experience with full magisk root?

Thanks guys.
[Shield Android TV General] melo_mx:
I followed these steps and they worked great for me. I have full root, full speed, and the latest shield experience.

At least I can confirm this works for the 500GB 2015 version.

Even followed the optional instructions to upgrade to 7.2.1 with adb pulling the update from the shield. Magisk modules work as well

It all works greatly. Not sure why original poster is taking so much heat
[Shield Android TV General] nadia p.:
[SUCCESS] I revert back to 7.1.0 from 7.2.1 without any issues! :)

Thank you ACiDxCHRiST! I wanted to confirm following your guide works perfectly just as you said on a Shield TV 2017 (16GB). I was able to

successfully

downgrade to 7.1.0 without any issues. I had to reboot twice to get things to refresh so I could access the Google Play store, after the first reboot when attempting there was only a spinning circle. After rebooting it cleared it up. I have the nag screen to request to update to 7.2.1 but I'm able to dismiss that and continue. I can't say how pleased I am to be able to use my system again. I'm unclear why 7.2.x broke a few Apps that I was using, but now using 7.1.0 everything is as expected.

I wonder if following these same exact steps one could downgrade to 6.3.0 without any issues as well. For now I'm delighted with 7.1.0 until I can figure out how to use TWRP and backup my entire system.
[Shield Android TV General] whiteak:
It's not about taking heat, we have just tried to make OP aware that using the methods described here will not grant Full Root access for the 2017 Darcy model, (other models, I can't say as I only own 2017 Darcy models). 3 of us have now tried to make OP aware. For myself, I don't see the point of trying to get Root access if you are only going to end up with a Partial Root and not with Full Root access, I am the opposite of the OP where I like to delete the crap from the system Partition, but again that is just my personal preference. I have managed a way to get Full Root access on my 2017 Darcy model, there is a way it can be done.
[Shield Android TV General] Roamin64:
I used the boot.img that ACiDxCHRiST posted in the TWRP thread , https://xdaforums.com/showpost.php?p=78496132&postcount=163 and everything seems good. My bootloader was already unlocked and this was just a case of losing root after an upgrade. I used minimal ADB and Fastboot interface, only booted the boot.img with "fastboot boot boot.img" and then installed the Magisk manager from post 1 of this thread. I installed root with the manager, rebooted and tested my sixaxis and it worked. Tried Adaway but it couldn't write the host file. Returned in magisk and activated systemless hosts, rebooted and adaway worked no probs. Mounted root with write enable in x-plore and managed to change permissions of a file deep in the root folder. Seems like everything is working fine.

Did I really need to flash the boot.img ? Seems simply booting it once did the trick for me.
[Shield Android TV General] ACiDxCHRiST:
I was not aware when I posted this that it was not full root. I mentioned before that I don't modify the system partition if I can avoid it. I don't need to modify the system partition. The point of Magisk is to be able to do things systemlessly that would normally require modifying the system partition. As opposed to other rooting methods that all seem to have ceased development. Adaway with Systemless hosts works for me. Root Explorer being able to navigate /data/data/ works for me. Magisk Modules work for me. And to that extent, Magisk currently does everything that I need from it. So when all of that worked, I didn't look for any solutions beyond that.

I would have tested the /system write permissions when [MENTION=8898246]whiteak[/MENTION] mentioned it; but like I said in the response, a system.img for v7.2.1 is not available for download yet and I didn't feel like spending another 30 mins flashing v7.2 then upgrading to v7.2.1 again to restore an unmodified /system partition if I was able to modify it.

For those that need full root permissions to modify their /system partition and do other things, they are likely the type of people that have the technical knowledge to seek out or figure out how to do what they want. They aren't the type of people that "follow rooting guides"

There is only one person that was a dickhead. [MENTION=8898246]whiteak[/MENTION] and [MENTION=2772353]Downunder35m[/MENTION] were perfectly respectful and helpful in pointing out the shortcomings of this method, they have also provided the additional information necessary to achieve full root permissions.

I will update the original post with the additional information/files needed to achieve proper root sometime in the future for completeness.

As for some of the small innacuracies like writing that the "wrong boot.img" will brick your device instead of writing the "wrong image", DOES IT REALLY ****ING MATTER? Again, Target Audience here guys! The people who know better, already ****ing know better. The point of the warning is to make people pay attention to the image and files that they are downloading and flashing. If they use the wrong ****, they have the potential to render their device inoperable.

Also, to anyone that just wants to piss on this thread, or me for taking the time to put this together and share it, there is nothing preventing you from taking the time and writing a more complete and accurate guide.
[Shield Android TV General] nanerasingh:
As my test on 2017 16gb 7.2.2 official TWRP patched the boot img i got root access but not fully write.

I used the DTB and flashed from fastboot and reboot without any reset -w command.

No issue of unresponsiveness and boots up normal.I tried edit build.prop in system via ES explorer and reboot the see the persistent and rw works.

So system dm-verity patch by DTB works.
[Shield Android TV General] Strangeland16:
Hi I've rooted my shield all works except Nvidia games when I try to log in I get a login failed unable to log you in at this time.try later. Is this as a result of rooting does root break Nvidia games please ??

---------- Post added at 01:26 PM ---------- Previous post was at 01:20 PM ----------

Nevermind worked it out adblock was the problem thanks anyway