[GUIDE] Root NVIDIA SHIELD Experience Upgrade v7.2 with Magisk v18.0

[DumbKing@letthemeatspam]

I flashed with fastboot flash boot magisk_patched.img.

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!

 

[George@xda]

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!

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.

 

[cHECKjAM]

that doesnt matter.. both can be rooted

Sent from my SM-G988U using Tapatalk

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_?

 

[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..?

 

[George@xda]

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..?

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.

 

[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?

 

[George@xda]

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?

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.

 

[cHECKjAM]

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.

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..

 

[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.

 

[ldeveraux]

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.

I'm sure you checked here, saw it hasn't been rooted yet, and decided to ask again?

I think this is the best you'll get

 

[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.

 

[cHECKjAM]

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!

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.

 

[George@xda]

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.

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.

 

[cHECKjAM]

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.

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 @mrhamed to bypass google setup and see if that works.

 

[George@xda]

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 @mrhamed to bypass google setup and see if that works.

Hi,
My box finds and works well with Bluetooth.

 

[ldeveraux]

---------- Post added at 08:40 PM ---------- Previous post was at 07:59 PM ----------

Now how do I prevent my shield from ever updating again without my consent? Anything at root level I could do to make sure it can't ever happen?

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.

 

[ldeveraux]

like i said tegraota.apk is removed to stop updates. This works 90% of the time and is the only way to keep from updating automatically that i know off. But i still come home some times and The System has been updated . I left that for someone who asked. It was both an answer and a cautionary tale.

I completely misread the forum, thought this was for another device. You can ignore what I said previously, sorry!

 

[Ghisy]

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

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!

 

[twistedumbrella]

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!

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.

 

[Ghisy]

As long as your bootloader is unlocked, it really is as simple as patching the boot and flashing it to the device. As long as nothing changed and the recovery is still a separate partition, that is just like flashing a boot image using "recovery" instead of "boot" as the target.

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!