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

ACiDxCHRiST · Dec 24, 2018

(Note before you begin: If you have a SHIELD TV 2017, you will need a quality Male-to-Male USB Type A cable to connect your SHIELD TV to a PC. If you have a SHIELD TV 2015 or a SHIELD TV Pro, you may be able to just use a regular micro USB cable, because those two models have a micro USB port)

A. Download these files to your PC:

B. Setting up Android SDK Platform-Tools on your PC:

C. Installing the Official NVIDIA SHIELD family Windows USB Drivers on your PC:

On your SHIELD TV, enable developer options and debugging (Instructions HERE)
Using a Male-to-Male USB Type-A Cable, connect the USB port further away from the HDMI port on your SHIELD TV to your PC
On your PC, extract the Official NVIDIA SHIELD family Windows USB Drivers somewhere where you can find them
Open Device Manager and find the new device
Right-click it and select Update driver
Select "Browse my computer for driver software"
Input the path to the folder where you extracted the Official NVIDIA SHIELD family Windows USB Drivers earlier (make sure the "Include subfolders" option is checked)
Click Next and Install the Driver (if there is more than one option, select the one relating to ADB or Android Device Bridge)
Open a Command Prompt and type:
Code:
```
adb devices
```
On your SHIELD TV, a prompt will pop up asking you to allow ADB access from your computer. Check the box to remember your selection and then Grant Access
On your PC, the Command Prompt should show the serial number of your SHIELD TV
(You may have to run the 'adb devices' command again since it may have timed out the first time waiting on you to authorize the ADB connection on the SHIELD TV)
Boot the SHIELD TV into bootloader/fastboot mode by typing the command:
Code:
```
adb reboot bootloader
```
(Alternatively, you can enter bootloader/fastboot mode by following the instructions HERE)
On your PC, open the Device Manager again and find the new device (it will probably have an error with a yellow triangle)
Right-click it and select Update driver
Select "Browse my computer for driver software"
Input the path to the folder where you extracted the Official NVIDIA SHIELD family Windows USB Drivers earlier (make sure the "Include subfolders" option is checked)
Click Next and Install the Driver (if there is more than one option, select the one NOT relating to ADB or Android Device Bridge)
Open a Command Prompt and type:
Code:
```
fastboot devices
```
The Command Prompt should show the serial number of your SHIELD TV

D. Unlocking the bootloader on your SHIELD TV (CAUTION: THIS WILL WIPE YOUR DATA AND FACTORY RESET YOUR SHIELD TV)

E. Installing Magisk Manager on your SHIELD TV and Patching your boot.img

F. Installing Magisk rooted SHIELD Experience Upgrade v7.2 on your SHIELD TV:

Optional Stuff and Additional Information:

whiteak · Dec 24, 2018

Hey mate, just curious if you have full root access, eg, can you uninstall system apps or delete their folders in system/apps, only asking as I also thought I had gained full root access with patching the boot.img with Kantjers version of Magisk, but when I try to uninstall a system app or try and delete their respective folders, even though it appears in Magisk that I have full root access, when I try to uninstall or delete a system app folder, I actually don't have full root access.

ACiDxCHRiST · Dec 24, 2018

whiteak said:
Hey mate, just curious if you have full root access, eg, can you uninstall system apps or delete their folders in system/apps, only asking as I also thought I had gained full root access with patching the boot.img with Kantjers version of Magisk, but when I try to uninstall a system app or try and delete their respective folders, even though it appears in Magisk that I have full root access, when I try to uninstall or delete a system app folder, I actually don't have full root access.

I don't modify the system partition if I can avoid it. I just disable System Apps if I want them gone; however, I am fully confident that I could delete anything in /system if I wanted to. Is /system mounted as +rw? Not all Root File Managers are created equal. I recommend Root Explorer. It is not the most modern and feature rich file manager, but when it comes to Root File Managers specifically, I haven't found any other that can compare.

whiteak · Dec 24, 2018

Thanks for the reply, not a big deal, was just curious if you actually did have full root access as it appears I do as well until I actually need it to do something like delete a system app etc. I may try flashing your patched boot.img and see if I get the same results as my patched boot.img, may just come down to the fact that I'm using Kantjers version of Magisk etc, wouldn't think it would be any different, but never know I guess until I try. Thanks again.

ACiDxCHRiST · Dec 24, 2018

whiteak said:
Thanks for the reply, not a big deal, was just curious if you actually did have full root access as it appears I do as well until I actually need it to do something like delete a system app etc. I may try flashing your patched boot.img and see if I get the same results as my patched boot.img, may just come down to the fact that I'm using Kantjers version of Magisk etc, wouldn't think it would be any different, but never know I guess until I try. Thanks again.

I would test it for you if I had a system.img for v7.2.1 that I could reflash real quick. I just don't feel like flashing v7.2.0 then updating to v7.2.1 again to restore an unmodified system partition.

sconnyuk · Dec 24, 2018

ACiDxCHRiST said:
A. Download these files to your PC:

Download the Android SDK Platform-Tools HERE

Download the Official NVIDIA SHIELD family Windows USB Drivers HERE

Download Magisk Manager APK (Link to latest version at time of writing is HERE)

Download the ***CORRECT*** NVIDIA SHIELD Experience Upgrade v7.2 Image for your model HERE
(Flashing the wrong boot.img will BRICK your device You will need to register for a Developer Account if you don't already have one)

B. Setting up Android SDK Platform-Tools on your PC:

On your PC, extract the Android SDK Platform-Tools somewhere where you can find them

Add the platform-tools folder to PATH in the Windows System Environment Variables (Instructions HERE)

C. Installing the Official NVIDIA SHIELD family Windows USB Drivers on your PC:

On your SHIELD TV, enable developer options and debugging (Instructions HERE)

Using a Male Type-A to Male Type-A USB Cable, connect the USB port further away from the HDMI port on your SHIELD TV to your PC

On your PC, extract the Official NVIDIA SHIELD family Windows USB Drivers somewhere where you can find them

Open Device Manager and find the new device

Right-click it and select Update driver

Select "Browse my computer for driver software"

Input the path to the folder where you extracted the Official NVIDIA SHIELD family Windows USB Drivers earlier (make sure the "Include subfolders" option is checked)

Click Next and Install the Driver (if there is more than one option, select the one relating to ADB or Android Device Bridge)

Open a Command Prompt and type:

Code:

adb devices

On your SHIELD TV, a prompt will pop up asking you to allow ADB access from your computer. Check the box to remember your selection and then Grant Access

On your PC, the Command Prompt should show the serial number of your SHIELD TV
(You may have to run the 'adb devices' command again since it may have timed out the first time waiting on you to authorize the ADB connection on the SHIELD TV)

Boot the SHIELD TV into bootloader/fastboot mode by typing the command:

Code:

adb reboot bootloader

(Alternatively, you can enter bootloader/fastboot mode by following the instructions HERE)

On your PC, open the Device Manager again and find the new device (it will probably have an error with a yellow triangle)

Right-click it and select Update driver

Select "Browse my computer for driver software"

Input the path to the folder where you extracted the Official NVIDIA SHIELD family Windows USB Drivers earlier (make sure the "Include subfolders" option is checked)

Click Next and Install the Driver (if there is more than one option, select the one NOT relating to ADB or Android Device Bridge)

Open a Command Prompt and type:

Code:

fastboot devices

The Command Prompt should show the serial number of your SHIELD TV

D. Unlocking the bootloader on your SHIELD TV (WARNING: THIS WILL WIPE YOUR DATA AND FACTORY RESET YOUR SHIELD TV)

Plug the NVIDIA SHIELD TV Game Controller or a USB Keyboard into the USB port closest to the HDMI port on your SHIELD TV

In bootloader/fastboot mode on your SHIELD TV, select "Unlock Bootloader", read the message and confirm
(Use the Y and X buttons to scroll UP and DOWN, and the A button to confirm selection, if your button presses aren't doing anything you need to reboot the SHIELD TV into bootloader/fastboot mode with the Controller or Keyboard already plugged in)

On your PC, open a Command Prompt and reboot your SHIELD TV to the OS by typing:

Code:

fastboot reboot

E. Installing Magisk Manager on your SHIELD TV and Patching your boot.img

On your PC, extract the NVIDIA SHIELD Experience Upgrade v7.2 Image that you downloaded to somewhere where you can find it

Find the boot.img file in the folder that you extracted it to

Open a Command Prompt and type:

Code:

adb push boot.img /storage/emulated/0/Download/

Install Magisk Manager by typing 'adb install [path-to-Magisk-Manager-APK]' example:

Code:

adb install C:\MagiskManager-v6.1.0.apk

On your SHIELD TV, open Magisk Manager [Settings > Device > Apps > Magisk Manager > Open]
(The Magisk Manager App Interface is not designed to be operated with an Android TV Remote so I suggest you install the NVIDIA SHIELD TV app on your phone. Once paired with your SHIELD TV, the app has an option to let you use a virtual mouse to navigate and interact with apps on your SHIELD TV. Alternatively, you can plug in a USB Mouse into the USB port closest to the HDMI port on your SHIELD TV)

If Magisk Manager automatically pops up and asks you if you would like to Install Magisk, select Cancel

Make sure the "Preserve AVB 2.0/dm-verity" option is checked, and then select "Install"

Select "Patch Boot Image File"

Using the Virtual Mouse on the NVIDIA SHIELD TV remote app on your phone, or a USB Mouse, navigate to the "Download" folder on your internal storage and select the boot.img file that you copied over then click Open

Magisk Manager will take a few moments to patch the boot.img (pay attention to the message in the console about the path to the patched_boot.img - It should be "/storage/emulated/0/Download/patched_boot.img"

On your PC, in the Command Prompt type:

Code:

adb pull /storage/emulated/0/Download/patched_boot.img

F. Installing Magisk rooted SHIELD Experience Upgrade v7.2 on your SHIELD TV:

On your PC, navigate to the folder where you extracted the NVIDIA SHIELD Experience Upgrade v7.2 Image

Find the boot.img and rename it to boot.img.bak

Rename the patched_boot.img to boot.img

Open a Command Prompt and type:

Code:

adb reboot bootloader

Once the SHIELD TV is in bootloader/fastboot mode, type:

Code:

flash-all.bat

(It will take a few minutes for the flashing process to finish and then the SHIELD TV will automatically reboot to the OS)

Optional Stuff and Additional Information:

Disable Auto-Upgrades by going to [Settings > Device > About > System upgrade > Auto-upgrade]

Enable Full OTA's instead of Partial/Differential by going to [Settings > Preferences > Developer options > Provide full system upgrades]
(It is the very last option at the bottom and this is very important when using a rooted device and modifications to the System partition are likely)

If you want to upgrade to a new OTA update with root without waiting on NVIDIA to post the Developer/Recovery images, the downloaded OTA file is in

Code:

/data/data/com.nvidia.ota/app_download

(You will need a root file explorer to be able to access this directory)

You can extract the boot.img from the OTA zip and patch it using the same method described in step E.5 through E.10

You can then install the OTA the normal way [Settings > Device > About > System upgrade > Check for upgrade]
(Make sure you have copied the OTA zip or extracted the boot.img to somewhere on your Internal Storage like "/storage/emulated/0/Download" before you install the OTA because the system will delete the file in "/data/data/com.nvidia.ota/app_download" when it installs the update and you will be unable to get it after that)

Copy the patched_boot.img that you made with Magisk to your PC

Reboot to bootloader/fastboot mode with:

Code:

adb reboot bootloader

Manually flash just the Magisk Patched boot:

Code:

fastboot flash boot patched_boot.img

Manually reboot back to the OS with:

Code:

fastboot reboot

Thankyou ever so much for putting this together but after following exactly what you said in this guide this is what i get:

C:\Users\sconn\nv-recovery-image-shield-atv-7.2.0>flash-all.bat
Sending 'staging' (6436 KB) FAILED (Write to device failed in SendBuffer() (Unknown error))
Finished. Total time: 10.295s
Sending 'boot' (14115 KB) FAILED (Write to device failed (Invalid argument))
Finished. Total time: 15.641s
< waiting for any device >

ACiDxCHRiST · Dec 24, 2018

sconnyuk said:
Thankyou ever so much for putting this together but after following exactly what you said in this guide this is what i get:

C:\Users\sconn\nv-recovery-image-shield-atv-7.2.0>flash-all.bat
Sending 'staging' (6436 KB) FAILED (Write to device failed in SendBuffer() (Unknown error))
Finished. Total time: 10.295s
Sending 'boot' (14115 KB) FAILED (Write to device failed (Invalid argument))
Finished. Total time: 15.641s
< waiting for any device >

Do you have a 2015 or a 2017 SHIELD TV? Assuming you didn't edit that directory name, it should be nv-recovery-image-shield-atv-2017-7.2.0

If you have a 2017 and did manage to flash that image without an error, it would have bricked your SHIELD TV.

Do you still have Minimal ADB installed? I kind of feel like your fastboot.exe is outdated. I feel like your Minimal ADB install is registered to PATH and whenever a command calls fastboot, it is running the outdated fastboot in your Minimal ADB install.

sconnyuk · Dec 24, 2018

ACiDxCHRiST said:
Do you have a 2015 or a 2017 SHIELD TV? Assuming you didn't edit that directory name, it should be nv-recovery-image-shield-atv-2017-7.2.0

If you have a 2017 and did manage to flash that image without an error, it would have bricked your SHIELD TV.

Do you still have Minimal ADB installed? I kind of feel like your fastboot.exe is outdated. I feel like your Minimal ADB install is registered to PATH and whenever a command calls fastboot, it is running the outdated fastboot in your Minimal ADB install.

I have 2017 Shield TV 16gb, which is on stock 7.2.1
I am using platform tools you suggested previously.

im quite sure im downloading the correct version, yes i do rename certain folders when i extract (just like i did with platform-tools to platform tools etc.
Im wondering if because im using standard usb 2.0 a to a cable is problem ? , aswell as both my laptop and desktop computers are older usb 2.0 models?
Both cables i have are usb 2.0 a to a but never had problems using with other devices including amazon fire tv 2 4k box when i had to recover it. Also i can adb push/pull/install no problems.
I have tried selecting unlock bootloader again just to triple check its unloacked and it reports bootloader is already un locked.
Im running out of ideas to be honest, quite the nightmare im having.

ACiDxCHRiST · Dec 24, 2018

sconnyuk said:
I have 2017 Shield TV 16gb, which is on stock 7.2.1
I am using platform tools you suggested previously.

im quite sure im downloading the correct version, yes i do rename certain folders when i extract (just like i did with platform-tools to platform tools etc.
Im wondering if because im using standard usb 2.0 a to a cable is problem ? , aswell as both my laptop and desktop computers are older usb 2.0 models?
Both cables i have are usb 2.0 a to a but never had problems using with other devices including amazon fire tv 2 4k box when i had to recover it.
I have tried selecting unlock bootloader again just to triple check its unloacked and it reports bootloader is already un locked.
Im running out of ideas to be honest, quite the nightmare im having.

I don't see USB 2.0 being an issue. You could try locking then unlocking your bootloader again.

Also try running with an elevated Command Prompt with admin rights.

sconnyuk · Dec 24, 2018

ACiDxCHRiST said:
I don't see USB 2.0 being an issue. You could try locking then unlocking your bootloader again.

Also try running with an elevated Command Prompt with admin rights.

Yes i always use admin rights with CMD.
I will try re locking and unlocking again later today. (i cant see how nobody else has had issues like mine)
Thanks, il report back.

---------- Post added at 09:00 AM ---------- Previous post was at 08:36 AM ----------

Just tried re locking my bootloader then unlocking again and get same output:
Just for your info the download im using is 'nv-recovery-image-shield-atv-2017-7.2.0.zip' like i said i had a few downloaded alreadyh so just renamed it.
C:\Users\sconn\nv-recovery-image-shield-atv-7.2.0>flash-all.bat
Sending 'staging' (6436 KB) FAILED (Write to device failed in SendBuffer() (Unknown error))
Finished. Total time: 6.297s
Sending 'boot' (14115 KB) FAILED (Write to device failed (Invalid argument))
Finished. Total time: 15.853s
< waiting for any device >

ACiDxCHRiST · Dec 24, 2018

sconnyuk said:
Just tried re locking my bootloader then unlocking again and get same output:
Just for your info the download im using is 'nv-recovery-image-shield-atv-2017-7.2.0.zip' like i said i had a few downloaded alreadyh so just renamed it.
C:\Users\sconn\nv-recovery-image-shield-atv-7.2.0>flash-all.bat
Sending 'staging' (6436 KB) FAILED (Write to device failed in SendBuffer() (Unknown error))
Finished. Total time: 6.297s
Sending 'boot' (14115 KB) FAILED (Write to device failed (Invalid argument))
Finished. Total time: 15.853s
< waiting for any device >

I googled your error and I found a post that said changing cables fixed the problem. So that is at least one piece of information that points towards your hardware setup being the issue. I don't know what else to tell you.

sconnyuk · Dec 24, 2018

ACiDxCHRiST said:
I googled your error and I found a post that said changing cables fixed the problem. So that is at least one piece of information that points towards your hardware setup being the issue. I don't know what else to tell you.

Yes even though I've got 2 here I'm going to try another, now if my local computer shop is open today I'll grab one to try.
As soon as I get a cable I'll report back and let you know, at the very least this might help someone with any issues that turn out to be similar to mine.
I was even thinking of trying to get twrp on or even boot to it to flash the boot.img but it's a no go on 7.2.1 and more so it's a no go because nothing will flash through fastboot for me at the moment.
I'll be in touch. ?

ACiDxCHRiST · Dec 24, 2018

sconnyuk said:
Yes even though I've got 2 here I'm going to try another, now if my local computer shop is open today I'll grab one to try.
As soon as I get a cable I'll report back and let you know, at the very least this might help someone with any issues that turn out to be similar to mine.
I was even thinking of trying to get twrp on or even boot to it to flash the boot.img but it's a no go on 7.2.1 and more so it's a no go because nothing will flash through fastboot for me at the moment.
I'll be in touch.

Here is the cable that I use: https://www.amazon.com/Cable-Matters-2-Pack-Male-Black/dp/B00HSS9IDW

sconnyuk · Dec 24, 2018

Finally, i decided to butcher 2 good thick usb cables and bodge a new a to a cable together and it flashed first time

Thanks for all your help.
Cannot understand how i have had issues with 2 different cables but now we know this device must be picky.

ACiDxCHRiST · Dec 24, 2018

sconnyuk said:
Finally, i decided to butcher 2 good thick usb cables and bodge a new a to a cable together and it flashed first time
Thanks for all your help.
Cannot understand how i have had issues with 2 different cables but now we know this device must be picky.

Awesome

sconnyuk · Dec 24, 2018

ACiDxCHRiST said:
Awesome

So from a virgin 7.2.1 we can after all flash a modded boot ??.
Just have to wait for a TWRP that is working on 7.2.1 now.
Thanks again for your help, I'd probably of given up after all that untill you mentioned the lead.
I did have a sneaky feeling myself but wasn't gunna try a new one till after Christmas.

ACiDxCHRiST · Dec 24, 2018

sconnyuk said:
So from a virgin 7.2.1 we can after all flash a modded boot .
Just have to wait for a TWRP that is working on 7.2.1 now.
Thanks again for your help, I'd probably of given up after all that untill you mentioned the lead.
I did have a sneaky feeling myself but wasn't gunna try a new one till after Christmas.

What do you need TWRP for?

nadia p. · Dec 24, 2018

Thank you ACiDxCHRiST, for creating a new guide. It takes a considerable amount of time to first find a solution that is repeatable, document everything, test it, etc... :good: well done.

I have a question for you if I may. I've been trying to understand what Magisk actually patches. I've read through their web site and other than rooting it doesn't go into to many details about what else it patches or modifies. Do you have any additional information about this?

Once you've installed the patched_boot.img, and you first boot your Nvidia Shield TV are you required to first connect to the internet, then sign-in to Google Play and assuming the existing Nvidia Experience software is not already updated to the latest release, does it begin to download the and force you to install the latest update?

sconnyuk · Dec 24, 2018

ACiDxCHRiST said:
What do you need TWRP for?

Just for backups, I'd like to get my system all setup exactly like I want it and then create a backup.
Also if any magisk/xposed modules make my box not boot to restore also ??

ACiDxCHRiST · Dec 24, 2018

nadia p. said:
Thank you ACiDxCHRiST, for creating a new guide. It takes a considerable amount of time to first find a solution that is repeatable, document everything, test it, etc... :good: well done.

I have a question for you if I may. I've been trying to understand what Magisk actually patches. I've read through their web site and other than rooting it doesn't go into to many details about what else it patches or modifies. Do you have any additional information about this?

Once you've installed the patched_boot.img, and you first boot your Nvidia Shield TV are you required to first connect to the internet, then sign-in to Google Play and assuming the existing Nvidia Experience software is not already updated to the latest release, does it begin to download the and force you to install the latest update?

The SHIELD TV will only force you to update when you are going through the Initial Setup after a data wipe. If you follow the guide exactly as written and your bootloader is not unlocked yet, you will be forced to update to v7.2.1 after unlocking the bootloader. But since there aren't any more data wipes and the last step is to flash the v7.2.0 image that we modified, you will end up on v7.2.0 without being forced to do the Initial Setup again. In fact, you could likely use the same steps in the guide to install other versions.

As for what Magisk patches, it modifies the bootloader to trick the OS into thinking that the SU binary is in the system partition without actually modifying the system partition.

sconnyuk said:
Just for backups, I'd like to get my system all setup exactly like I want it and then create a backup.
Also if any magisk/xposed modules make my box not boot to restore also

Roger that, makes sense.

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

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Similar threads

Top Liked Posts