Model P2897, 16GB 2017 darcy. No adb, no fastboot, only APX mode. As I said, I used nv-recovery-image-shield-atv-7.2.1-dev_rooted.zip. Almost completely dead. Nvflash.exe job?
[GUIDE] Root NVIDIA SHIELD Experience Upgrade v7.2 with Magisk v18.0
- Thread starter ACiDxCHRiST
- Start date
Looks like you flashed the 2015 image to your 2017.
The file name for the SHIELD TV 2017 is:
nv-recovery-image-shield-atv-7.2.1-2017-dev_rooted.zip
Hi guys. Happy new year!
So, I'm still a bit confused here.
I've got the 2017 16gb unit. Fully rooted with magisk 18 on dev os image with unlocked bootloader.
I'm on 7.1.
I only ever booted into twrp via fastboot/adb to flash the image.
So, can I actually somehow update to 7.2.1 dev or even 7.2.2 test image whilst keeping full root!?
If so, what's the actual step by step process and what are the consequences? Presumably no more twrp.
Many thanks guys!
Sent from my [device_name] using XDA-Developers Legacy app
yes you can update and root bit no twrp yet, but don't bother too many bugs stay on 7.1 with twrp
Is xposed available for shield? Moving from rooted fire tv 2 and want xposed edge pro. Thanks.
Hello Largewoodenspoon, what ACiDxCHRiST was saying is that based on the file you listed previously:
nv-recovery-image-shield-atv-7.2.1-dev_rooted.zip <--- NOT 2017, for some other device.
nv-recovery-image-shield-atv-7.2.1-2017-dev_rooted.zip <-- 2017 for your device.
You grabbed the incorrect download by mistake from HERE and installed it. This is what caused your device to fail.
I did the exact same thing. Chose the link for 2017 device but 2017 wasn't in the zip name. After I flashed it, my 2017 unit had no power at all. Sent it back and already got a new one.
https://developer.nvidia.com/gameworksdownload#?search=SHIELD%20TV%202017%20Developer&tx=$additional,shield
Can someone link me to the correct 2017 image zip file or at least the correct boot.img for the 2017?
Edit: Nevermind, found the stock images with 2017 in the file title. Bet the fact that the 2017 developer's image appears to be linking to the 2015 image is causing a few bricks...
Last edited:
It has in the past. If it is linking to the non 2017 for you it's not the first time
It's showing the right version now but I had that link bookmarked so I know it's the one I used. It didn't have 2017 in the zip file name when I imaged it and it was a smaller file. 1.09 GB vs 1.1 GB.
Or I'm losing my mind... lol.
I looked to verify but the only zip I kept was the stock image that worked fine.
Or I'm losing my mind... lol.
I looked to verify but the only zip I kept was the stock image that worked fine.
I am on 7.1 developers image foster can I use this guide to go to 7.2
You can. But as has been mentioned in this thread, it won't give you FULL root permissions. If you are like me and just need root permissions for certain apps and Magisk Modules, it will work just fine. If you need to edit the build.prop or other things, you will have to flash a modified DTB as well.
I have been trying to get clarification. DTB file is for Darcy only right? I have the Pro version(foster). I have not seen anything where DTB is needed for foster so just want to make sure.
Oh yeah, I guess I didn't pay attention to that in your post. Foster doesn't need it.
Hi again guys.
I think in my previous post a couple of days ago I was unclear as to where I am at.
I'm on a 2017 16gb unit. Rooted fully with magisk v18 on nvidia experience 7.1 dev image.
I've not attempted to update to 7.2 or 7.2.1 or 7.2.2 test image which I believe is knocking around.
All I'm wanting to do is update to 7.2.1 with full root functionality. But it's a bit confusing.
Am I best to stay where I am for now guys. I'm just paranoid about the 7.2.1 update nag I keep getting!
Sent from my [device_name] using XDA-Developers Legacy app
Go to
[Settings > Device > Apps > System upgrade > Notifications]
Turn that off. Update nag gone.
Follow the guide to get Magisk root on v7.2+
Like has been mentioned, it won't be full root, but many things will work. Magisk Modules, many apps that require root permissions, read access to whole filesystem, Adaway with Systemless hosts, etc. will all work.
If you need/want to edit the build.prop or do some other things which require writing to the /system partition that Magisk can't do for you systemlessly, then you will also need to flash a modified DTB.
Last edited:
you can have full root without any dtb files.. all I did was started fresh, flashed the full 7.2.1 developer os images in fastboot.. set it up.. installed magisk manager.. patched the boot.img with v18 magisk.. reboot to fastboot.. "fastboot boot patched_boot.img".. once booted open magisk manager and install the zip by selecting direct install..
if you are having issues with "full root" try disabling dm-verity.. all you need to do is type "adb disable-verity" then reboot..
i tested full root by deleting play store and a number of other system apps.. and yes, they stayed gone after multiple reboots and a factory reset..
This was done on a 2017 16gb shield tv..
as mentioned in another root thread on here, there was issues with trying to root using the ota files that users had to flash a dtb file.. the full dev images were released on 12/27 tho for 7.2.1 and come with a root shell out of the box making it easy..
keep in mind twrp still doesnt work.. probably wont until someone updates it.. when i tried to boot it, it just hangs and never boots.. i also had issues at first bcuz i didnt wipe.. once i did a factoryreset everything went quick and smooth
if you are having issues with "full root" try disabling dm-verity.. all you need to do is type "adb disable-verity" then reboot..
i tested full root by deleting play store and a number of other system apps.. and yes, they stayed gone after multiple reboots and a factory reset..
This was done on a 2017 16gb shield tv..
as mentioned in another root thread on here, there was issues with trying to root using the ota files that users had to flash a dtb file.. the full dev images were released on 12/27 tho for 7.2.1 and come with a root shell out of the box making it easy..
keep in mind twrp still doesnt work.. probably wont until someone updates it.. when i tried to boot it, it just hangs and never boots.. i also had issues at first bcuz i didnt wipe.. once i did a factoryreset everything went quick and smooth
I am thinking about trying something entirely different right now. I am cooking a Rom from the stock images that might possibly work while still being on the 7.1 firmware. I am not sure if it will reliably work, but it might be a possibility.
Even if 7.2 firmware is required, it still might lead to a full rooting solution with magisk, but can someone on 7.2+ can do me a favor and tries to make a dump of the partition layout? Even if system partition is not mounted, I need to know if the partition is present (or if the identifier changed). I can't access my own shield rn and it's still running on 7.1 and I don't want to upgrade it yet
Even if 7.2 firmware is required, it still might lead to a full rooting solution with magisk, but can someone on 7.2+ can do me a favor and tries to make a dump of the partition layout? Even if system partition is not mounted, I need to know if the partition is present (or if the identifier changed). I can't access my own shield rn and it's still running on 7.1 and I don't want to upgrade it yet
Do anyone have the boot.img from OTA 7.2.2 for the Shield 2015 16gb? I forgot to grab the OTA zip before I updated :/
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone