2017 Nvidia Sheild Root Status / FAQ

[brandonb21]

As of right now the 2017 Nvidia Shield CAN be rooted. Updated 1/26/2017

What we do know So far.

1. How to access Fast boot mode?

there are two ways to access fast boot. The first way to access fast boot mode,

1. Buy a male to male USB 3 cable, & plug it into the USB port furthest away from the hdmi port.
2. In settings of the shield, go to storage.
3. Enable USB transfer
4. In settings go to about, then build version.
5. Click on build version 5 times.
6. Under settings, go to developer options.
7. Enable USB debugging.
8. Make sure you have the latest drivers installed from Nvidias website.
9. Download ADB Command prompt/fastboot
10. Type "adb devices"
11. You may get a prompt on your shield about allowing debugging, if so make sure you allow it.
12. Type "adb devices" again if a device shows up then great! move on to the next step.
13. Type "adb reboot bootloader"

The second way of getting into fastboot mode, is the following

1. Unplug your power cable from the device.
2. Plug in your Shield game controller in the usb closest to the hdmi port.
3. Hold down buttons A & B.
4. While holding down the two buttons, put in your power cable.
5. Keep holding down the buttons.
6. If all done correctly you should see the fast boot menu now on your screen.

Congratulations your device should now be in the fastboot menu, Note in order to navigate the fast boot menu you will need your game controller plugged into the usb port next to the hdmi port.

2. Is their a download link for the latest OTA update?

Yes, you can get 5.0.1 from here, http://ota-downloads.nvidia.com/ota...-full_ota-1749719_832.2408.20170116175313.zip

3. What will happen if i try and install twrp on my shield?
Your device will try to boot it, then it will reboot and repair the recovery partition of your shield, then boot into androids 7.0 operating system.

4. A unofficial version of TWRP is out
https://forum.xda-developers.com/shield-tv/development/recovery-twrp-shield-android-tv-2017-t3545544 use at your own risk!

5. Recovery images are out for the 2017 Shield (16GB Only)
5.01 Retail: http://developer.download.nvidia.co...1/nv-recovery-image-shield-atv-2017-5.0.1.zip
5.01 Developer: http://developer.download.nvidia.co...ry-image-shield-atv-2017-5.0.1-dev_rooted.zip

 

[brotbuexe]

Can't you directly boot the twrp.img without flashing it first?

fastboot boot twrp...img

Then install SuperSU from there?

 

[Ichijoe]

Can't you directly boot the twrp.img without flashing it first?

fastboot boot twrp...img

Then install SuperSU from there?

You probably could... But, that in-and-of itself isn't exactly the problem. It's the unfortunate way Google have started implementing System Updates on Nougat going forward. They've call this System the a/b System.

To simply explain it, on Devices which support it. (Like the new Shield 2017, possibly the 2015 post update?), there are now Two System Partitions. The active one, which we have always known. (And, indirectly referencing in your question.), and, the new mirrored System Partition that has Two jobs. One to make System (e.g. Security), Updates simplier, and the other is to make sure the first System Partition does NOT get corrupted by allowing One to say root it or by installing "malicious" Software (i.e. SuperSU) onto the Device. Without it blasting it straight out of existence again.

So yes you could try to load TRWP up from somewhere, and install SuperSU. Like you've always done. But, as soon as you start to reboot it again the a/b System will revert your hard work again.

 

[brotbuexe]

You probably could... But, that in-and-of itself isn't the problem. It's the way Google have started implementing System Updated on Nougat going forward. They call that System the a/b System.

I read it is the same in pixel devices. So I hope it is just an update for SuperSU to recognize this on the new shield.

 

[brandonb21]

Can't you directly boot the twrp.img without flashing it first?

fastboot boot twrp...img

Then install SuperSU from there?

pretty much what the guy above said, it will detect a modification in the recovery partition and fix it, then boot into android.

 

[HUYI]

so are we SOL indefinitely or will there ever come a time where we can override the two partitions so root sticks? ie is it possible.

 

[brandonb21]

so are we SOL indefinitely or will there ever come a time where we can override the two partitions so root sticks? ie is it possible.

I dont think we are SOL. i think the developer of twrp for shield just needs to update it. im not a developer. so i dont know, but here is some good news, i was talking to nvidia and they will be releasing a prerooted image for the 2017 shield.

Hello Brandon,

Thank you for contacting NVIDIA Customer Care.

This is Kenny, assisting you in regards to your query about the ISO Image download availability for the SHIELD TV Console V2.

Please be informed that the image isn't available for this unit yet. This is our download centre : https://developer.nvidia.com/gameworksdownload where it will be available once the Image is available for this unit.
So you may check this website often to see the availability.

Disclaimer : Rooting the device will void the software warranty of the unit.

Unfortunately we don't have any ETA on this Brandon,

As it's a new device it may be added there in sometime. However I can't give you a precise date about this. Sorry.
You can register there as a developer and wait for the Image release.

Regards,
NVIDIA Customer Care

 

[HUYI]

I dont think we are SOL. i think the developer of twrp for shield just needs to update it. im not a developer. so i dont know, but here is some good news, i was talking to nvidia and they will be releasing a prerooted image for the 2017 shield.

0_0 whaaa! cool i can't wait for that that's awesome news! so cool that nvdia have given us support like this.

i will install when it's available but it seems it's going to be a long wait till it's available, maybe late spring summer my guess, hopefully sooner.

and it's obvious that it will void warranty..

 

[brotbuexe]

pretty much what the guy above said, it will detect a modification in the recovery partition and fix it, then boot into android.

But if you just fastboot the twrp.img you wouldn't touch the recovery partition.

You would change the boot.img and /data for systemless root while flashing SuperSU. So at the next boot the system has to check if you changed the boot img/partition, and I guess the supersu installer has to take care of this verification.

There would be not much of a problem to not have twrp directly on the device, as you can always boot the img through fastboot.


Does booting the twrp img via fastboot works on the 2017 shield?

 

[brandonb21]

But if you just fastboot the twrp.img you wouldn't touch the recovery partition.

You would change the boot.img and /data for systemless root while flashing SuperSU. So at the next boot the system has to check if you changed the boot img/partition, and I guess the supersu installer has to take care of this verification.

There would be not much of a problem to not have twrp directly on the device, as you can always boot the img through fastboot.


Does booting the twrp img via fastboot works on the 2017 shield?

i did "fastboot boot twrp.img" and it booted into the android OS

 

[AndroidUser00110001]

From what I gathered from recovery logs and tearing apart the boot.img I do not think the Shield 2017 uses two system partitions like the Pixel. I have only seen one partition.
I was able to modify the boot.img to make it not secure, flashed it and it booted fine. It was not replaced with stock boot. I then tried to flash TWRP with the not secure boot.img but TWRP would not boot.
I believe TWRP needs new zImage from Shield 2017 and a few variables need to be tweaked too for it to work on the Shield 2017.
I am going to download the OmniROM source files and try to compile TWRP for the Shield 2017. Should be a quick fix for the current Shield TWRP device maintainer to make so I am a little hesitant to take the time to set everything up. With my luck the current maintainer will build TWRP for Shield 2017.

*Edit*
I attached the modified boot.img which is insecure for whoever wants to play with it.
Make sure you have ADB enabled and your PC has been authorized to use ADB with your Shield2017...

 

[brandonb21]

But if you just fastboot the twrp.img you wouldn't touch the recovery partition.

You would change the boot.img and /data for systemless root while flashing SuperSU. So at the next boot the system has to check if you changed the boot img/partition, and I guess the supersu installer has to take care of this verification.

There would be not much of a problem to not have twrp directly on the device, as you can always boot the img through fastboot.


Does booting the twrp img via fastboot works on the 2017 shield?

From what I gathered from recovery logs and tearing apart the boot.img I do not think the Shield 2017 uses two system partitions like the Pixel. I have only seen one partition.
I was able to modify the boot.img to make it not secure, flashed it and it booted fine. It was not replaced with stock boot. I then tried to flash TWRP with the not secure boot.img but TWRP would not boot.
I believe TWRP needs new zImage from Shield 2017 and a few variables need to be tweaked too for it to work on the Shield 2017.
I am going to download the OmniROM source files and try to compile TWRP for the Shield 2017. Should be a quick fix for the current Shield TWRP device maintainer to make so I am a little hesitant to take the time to set everything up. With my luck the current maintainer will build TWRP for Shield 2017.

*Edit*
I attached the modified boot.img which is insecure for whoever wants to play with it.
Make sure you have ADB enabled and your PC has been authorized to use ADB with your Shield2017...

Sounds great! good luck on the twrp port!

 

[grodri19721]

Yes good luck dude

 

[GhostRider5666]

As of right now the 2017 Nvidia Shield CANNOT be rooted. Updated 1/20/2017

What we do know So far.

1. How to access Fast boot mode?

there are two ways to access fast boot. The first way to access fast boot mode,

1. Buy a male to male USB 3 cable, & plug it into the USB port furthest away from the hdmi port.
2. In settings of the shield, go to storage.
3. Enable USB transfer
4. In settings go to about, then build version.
5. Click on build version 5 times.
6. Under settings, go to developer options.
7. Enable USB debugging.
8. Make sure you have the latest drivers installed from Nvidias website.
9. Download ADB Command prompt/fastboot
10. Type "adb devices"
11. You may get a prompt on your shield about allowing debugging, if so make sure you allow it.
12. Type "adb devices" again if a device shows up then great! move on to the next step.
13. Type "adb reboot bootloader"

The second way of getting into fastboot mode, is the following

1. Unplug your power cable from the device.
2. Plug in your Shield game controller in the usb closest to the hdmi port.
3. Hold down buttons A & B.
4. While holding down the two buttons, put in your power cable.
5. Keep holding down the buttons.
6. If all done correctly you should see the fast boot menu now on your screen.

Congratulations your device should now be in the fastboot menu, Note in order to navigate the fast boot menu you will need your game controller plugged into the usb port next to the hdmi port.

2. Is their a download link for the latest OTA update?

Yes, you can get 5.0.1 from here, http://ota-downloads.nvidia.com/ota...-full_ota-1749719_832.2408.20170116175313.zip

3. What will happen if i try and install twrp on my shield?
Your device will try to boot it, then it will reboot and repair the recovery partition of your shield, then boot into androids 7.0 operating system.

I can get into the boot menu but none of my buttons on my controller work? I have it all plug in as the steps show. I just received it and maybe it not paired right?

 

[brandonb21]

I can get into the boot menu but none of my buttons on my controller work? I have it all plug in as the steps show. I just received it and maybe it not paired right?

the controller has to be plugged in before going into fastboot menu, also X is to go down and Y is to go up and A is to select an option.

 

[GhostRider5666]

the controller has to be plugged in before going into fastboot menu, also X is to go down and Y is to go up and A is to select an option.

Everything is plugged in. I did adb root bootloader no controller and did the steps with the A and B buttons.

 

[brandonb21]

Everything is plugged in. I did adb root bootloader no controller and did the steps with the A and B buttons.

maybe it was B and Y to go up and down. you know your controller is working if it vibrated going into fastboot mode, then it's working correctly

 

[GhostRider5666]

I fastboot oem unlocked and it booted up and shut down now It doesn't power back up and in device manager it shows APX?

 

[brandonb21]

I fastboot oem unlocked and it booted up and shut down now It doesn't power back up and in device manager it shows APX?

apx?, i oem unlocked mine and everthing went fine.

 

[GhostRider5666]

apx?, i oem unlocked mine and everthing went fine.

I don't know, I can't even get it to power on?