yashsingh1/xdaforums huggingface dataset:
[Shield Android TV General] Downunder35m:
Strangeland16 first: I think it is only a server issue and you should trust the error message for now.

If all login details are correct and it does not work 24h later than consider a factory reset, install the stock firmware and check if all works fine.

If it then fails after rooting it we have to check what the issue might be.

On the general note of the rooting on 7.2.X:

We should revert back to manual firmware updates only.

Reason is my recent experience when stuffing my Shield up - never do serious firmware or flashing work if you struggle to keep your eyes open....

Once you got enough of the messing around and just want to watch some movies in the evening it is best to flash a working firmware and rest.

I did so with the 7.1 .

Next day I though, what the heck, just get TWRP going and try some modded firmware to see how it works.

Well, TWRP did not show when called through Fastboot.

Screen went off with no signal but the light on the Shield stayed on.

To my surprise I had full ADB root access and SU in the shell thanks to the installed Magisk I guess.

Not 100% sure if I really tried the right version I tried them all and none worked.

Unpacked the one I used from the beginning from its archive again but no luck either.

Of course the stock 7.1 recovery will work through fastboot if called!?

Nope, same result just no ADB access at all.

Until I find a way make my bootloader accept a custom recovery I am a bit stuck now :(

What to do to prevent future problems with the bootloader?

Unless we get Pie or some really intense changes happen a new firmware should just work fine on the current bootloader.

In the flash-all.bat you can comment the line(s) in regards to the blob files.

On the block based updates you are a bit stuck as without TWRP you can not sideload a modified firmware zip.

And once the lines in the updater script are changed the zip is too.

The offical recovery images for download should always be the standard flashable .img files we can use directly in fastboot.
[Shield Android TV General] nadia p.:
Hello Downunder35m, I'm sure you are far more advanced that me in all of this. I was from the factory on 7.2.1 (no mods, etc...). I first reverted back to 6.3.0 developer which was fine accept I didn't understand that I needed to unlock the bootloader first, then sign-in etc..., then flash back. I did this all at once, then it forced me to update back to 7.2.1. I followed this guide and I've successfully reverted back to 7.1.0 without any problems, in fact the Apps that were broken because of 7.2.1 are now working again on Shield TV 2017 (16GB). So far I'm unable, because I'm new to all of this, to test how "rooted" I am. If there's something I can send you or assist you with please don't hesitate to ask. I've not had success with TWRP yet, since I only have the remote and a USB keyboard and USB mouse and have not figured out how to make it work. One report noted issues with the USB cable. I found I needed the latest Min. ADB & Fastboot software for Win10Pro to help me.
[Shield Android TV General] bonisaw:
Thank you, everything worked perfectly!

Mine is a 2017 16gb Shield (Darcy), I was running 7.2.0 with TWRP/SuperSU and decided to upgrade to 7.2.1, little did I know I would completely lose TWRP/SuperSU.

Just did your method and downgraded from regular 7.2.1 (OTA - incremental) to dev 7.2.0 (full) then upgraded to regular 7.2.1 (OTA - full), both patching boot.img as mentioned. Worked flawlessly. No bootloader issues, no partition issues, no issues at all and I kept all my data.

My reason to have root is because my external USB drive is formatted as EXT4 and the system doesn't recognize it, so I have to mount it manually and make a script to run on boot, also need to do a "setenforce 0" so the other apps can access it. I just moved my script from /sbin/supersu/su.d/ to /data/adb/post-fs-data.d/ and it worked, no problem at all. The USB drive is mounted and I can access it from Kodi.

I can run Termux with root (tsu) and LFTP works fine under it, I can also access my SSH server with root (su) and it works fine too.

When booting TWRP via fastboot stopped working (stuck on Nvidia logo) I was scared that rooting would have been patched and that would ruin it for me as I need it.... phew!
[Shield Android TV General] nadia p.:
If you have updated your ROM to 7.2.0 or later in any way TWRP won't work.

WARNING

If you have updated your Shield TV* to Nvidia 7.2.0 or later in any way either through Over-The-Air (OTA) updates or flashing OS DO NOT use TWRP 3.2.3.0 or earlier !!!

Why? Read this...

1. Black screen after flashing TWRP 3.2.3.0 to Nvidia 7.1.0 on Shield TV 2017 (16GB)

2. Shield TV 2017 (16GB) How to... DTB... but more importantly read THIS post by Downunder35m.
[Shield Android TV General] elliwigy:
meh.. i prefer fastboot flashing any day.. avoids all the troubles lol
[Shield Android TV General] nadia p.:
Yes, I've learned my lesson the hard way. :( We don't know what we don't know until we later learn. ;)
[Shield Android TV General] elliwigy:
seems to happen a lot with newer firmwares.. especially when u start hittin oreo and pie
[Shield Android TV General] bp328i:
Same here, I'm on 7.2.2 rooted on both my 2017 Pro and 2017 16gb.

I'm good without twrp for the time being.
[Shield Android TV General] slowgrind:
Nvidia shield 2017 darcy

Following rooting guide, it bricked/blackscreened darcy device. Images used were in nv-recovery-image-shield-atv-7.2.1-dev_rooted.zip. Was this supposed to be for shield 2015 model and not for 2017 model?

Patched boot.img adb pulled after magisk mod was 13,774,848 bytes long, original boot.img before adb pull was 13,531,136 bytes long. Was it the wrong boot.img I have used?

Now darcy device only shows as APX in windows device manager, I only managed to install a driver to make it show as Android Bootloader Interface. Is there anything that can be done to unbrick the shield now?

Thank you

---------- Post added at 05:08 PM ---------- Previous post was at 04:51 PM ----------

https://patchwork.ozlabs.org/project/linux-tegra/list/

Some code patches if interesting to anybody
[Shield Android TV General] nadia p.:
Hello slowgrind, which exact model of SHIELD TV* do you own and which Nvidia OS did you download?

Above you've talked about 2017 (aka Darcy) and 2015 models. The correct links to Nvidia's Recovery and Developer OS images is HERE. Check to make sure you've downloaded the correct software for

your

device. Note there are two flavors of 2015 models, SHIELD TV Pro (500GB) and SHIELD TV 2015 (16BG).

Do you still have ADB access to your device from your computer?
[Shield Android TV General] slowgrind:
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?
[Shield Android TV General] ACiDxCHRiST:
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
[Shield Android TV General] Largewoodenspoon:
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!
[Shield Android TV General] blue1978:
Is xposed available for shield? Moving from rooted fire tv 2 and want xposed edge pro. Thanks.
[Shield Android TV General] pop4xda:
Yes, if you can get root successfully.

I'm using Xposed edge pro on shield too.
[Shield Android TV General] nadia p.:
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.
[Shield Android TV General] jinx10000:
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...
[Shield Android TV General] iLLNiSS:
It has in the past. If it is linking to the non 2017 for you it's not the first time :)
[Shield Android TV General] jinx10000:
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.
[Shield Android TV General] jionny:
I am on 7.1 developers image foster can I use this guide to go to 7.2
[Shield Android TV General] ACiDxCHRiST:
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.
[Shield Android TV General] jionny:
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.
[Shield Android TV General] ACiDxCHRiST:
Oh yeah, I guess I didn't pay attention to that in your post. Foster doesn't need it.
[Shield Android TV General] Largewoodenspoon:
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!
[Shield Android TV General] ACiDxCHRiST:
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.
[Shield Android TV General] elliwigy:
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
[Shield Android TV General] Adromir:
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
[Shield Android TV General] mp33pm:
Does this work on 7.2.1? Thanks!
[Shield Android TV General] f30R:
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 :/
[Shield Android TV General] Topcatsheild:
Many thanks great tutorial

I have a question with regards to ota. I have extracted boot.img.p renamed taking .p off but magisk can't patch image. Wanting to upgrade to 7.2.2. I guess I will wait until developer image comes out.
[Shield Android TV General] PhoenixTank:
Darcy/2017 7.2.2

I've uploaded the stock boot.img and a magisk patched_boot.img for

Darcy (Shield TV 2017) 16GB on 7.2.2.

I don't know if the 16GB's boot images are compatible with the 2017 Pro model, so please don't brick yourself.

The official full 7.2.2 recovery images should be available soon anyway according to reps on the Nvidia forums, but for the impatient root users (like me) enjoy:

https://androidfilehost.com/?w=files&flid=288488
[Shield Android TV General] Topcatsheild:
PhoenixTank many thanks for image.
[Shield Android TV General] yfrancoi:
Good guide, thank you AcidxChrist !

I managed to root my 7.2.0 shield with this method.

Now how can i block updates for nvidia in a host file or other ways ? I just don't want to upgrade by accident when i see that nvidia is trying to shut root off.

What url does the shield go to check for upgrades ?

Does anyone know ?

Regards,

---------- Post added at 04:06 AM ---------- Previous post was at 04:04 AM ----------

Also if you ever need to clear data how do you bypass upgrades ?
[Shield Android TV General] thedemonschild:
PhoenixTank is it really difficult to make boot.img.p into an img that magisk can patch? Could you please tell me how you did it? I would like to learn because no one is as impatient as me and I like to be able to fix things like this myself. Thanks!!!

Edit: I have literally looked all over the web for like 2 hours trying to find this information to no avail. Please help me out!!!
[Shield Android TV General] liljah36388:
so i know it says make sure to use download correct image file for my model but im currently on the ShieldTV Pro 500gb 7.2.2 and only available download is 7.2.1... should i still try and root or wait for the 7.2.2 to become available for download? thanks for any help in advance
[Shield Android TV General] hardwarechaos:
Hi,

FYI: 7.2.2 dev images are out.

I am on patched 7.2.1 now.

Anyone knows if it is enough to just flash the system.img and don't use the 7.2.2 boot img to update?

Regards
[Shield Android TV General] liljah36388:
Where did u find them?? I've logged in as a developer on the nvidia site I only can see 7.2.1...

P.S. I did manage to get root tho and I'm running 7.2.2... I was already updated to 7.2.2 so I ended up taking a chance and used the 7.2.1 img and patched w Magisk and flashed w no problems downloaded root checker and it stated im rooted so I'm guessing I'm in the clear :fingers-crossed: so far so good lol
[Shield Android TV General] hardwarechaos:
Hi

https://developer.nvidia.com/gameworksdownload shows 7.2.2 for me

If you downgraded, how are you still on 7.2.2? :confused:

Regards
[Shield Android TV General] liljah36388:
Ahh yea it's there now lol must've added 2day but after I checked I did checked @ like 2am lol couldnt sleep... n yea idk I did checked it I used 7.2.1 and flashed successfully but for some reason wen I loaded it still said I was on 7.2.2 so I was like ahh ok it didnt work.. so I tried side loading SuperSU n it stated something was in the place of where it needed to b (something like that) but not that it was not rooted so that's wen I checked w rootchecker n it said rooted so lol not complaining here lolll but yea I was confused 2 lol
[Shield Android TV General] DumbKing@letthemeatspam:
im confused does this method in the first post work with the 7.2.2 image from Nvidia?
[Shield Android TV General] hardwarechaos:
Hi,

QUOTE=DumbKing@letthemeatspam;78700117]im confused does this method in the first post work with the 7.2.2 image from Nvidia?[/QUOTE]

after I accidently updated my patched 7.2.1 to 7.2.2 I had to try it and it worked just like 7.2.1.

Regards
[Shield Android TV General] mLgz0rn:
I just tried with 7.2.2 and I end up in a bootloop.

If I flash the stock boot again it boots fine.

So doesn't seem to work for me.

Edit:

Got it working by doing "adb disable-verity"
[Shield Android TV General] DumbKing@letthemeatspam:
Do I do that before flash? my usb-a to usb-c cable isn't detecting the shield when I plug it into my mac so I have to order a new one before I test this out
[Shield Android TV General] mLgz0rn:
You have to do it before you flash the patched boot, while you have the shield booted up, then through adb type adb disable-verity.

Another way that should also work, before you patch the boot image in magisk, check the "preserve avb 2.0/dm-verity" in magisk if it's not and then patch the boot image.

You only need to do either of these steps if your shield fails to boot after flashing the patched boot image.
[Shield Android TV General] thedemonschild:
Ok, so I must be doing something very wrong to have bricked 2 shield tvs in less than 3 days. I'm not looking to fix these two as I don't have anyway to; they are in APX mode and I've stopped looking for a solution and have accepted that they are DOA. Anyway, I would like to backup files with nvshare and wheelie or some other program. I am not entirely sure what files I need or what software. Is there anything out there that can save me from APX mode if I have the right files? Thanks in advance guys!!!!

Edit: I know where I messed up and don't need help in that department. I just need to know if there is a way to restore from APX mode with the proper files.
[Shield Android TV General] mLgz0rn:
There is not, since only Nvidia can recover a bricked device that is in APX mode.
[Shield Android TV General] DumbKing@letthemeatspam:
Wait, you followed this guide and bricked your device? Should people be following this guide then? Should I just follow the official nvidia guide?

http://developer.download.nvidia.co...ATV_2017/7.2.2/HowTo-Flash-Recovery-Image.txt
[Shield Android TV General] mLgz0rn:
If you follow the guide correctly there is no way to brick your device.

He properly downloaded the image for another shield device than the one he has.

Or flashed the wrong blob file, that will make your shield hardbrick into APX mode.

it even says so in the first part of the guide.

"Download the ***CORRECT*** NVIDIA SHIELD Experience Upgrade v7.2 Image for your model

(You will need to register for a Developer Account if you don't already have one. Flashing the wrong image will BRICK your device)"
[Shield Android TV General] Davepratt1987:
is there any way to modify /system? im having a hard time

im on 7.2.1 rooted
[Shield Android TV General] mLgz0rn:
how are you trying to do it? and what are you trying to do? :p

You might need to do adb disable-verity through adb then reboot to be able to modify the /system
[Shield Android TV General] Davepratt1987:
I tried that an it doesn't seem to work!

An it just pops up all the commands for adb starting with -a an ending in ANDROID_LOG_TAGS!

it doesn't give me any confirmation that adb disable-verity worked.

An Yes my adb detects my Sheild tv
[Shield Android TV General] mLgz0rn:
What adb version are you using?
[Shield Android TV General] Davepratt1987:
1.0.32..... nm I have 1.4.3 now an it says (verity cannot be disabled/enabled - USER BUILD)!
[Shield Android TV General] mLgz0rn:
Oh wait, are you running the developer build or ota of Nvidia shield experience?
[Shield Android TV General] Davepratt1987:
Im guess it's ota because I updated through settings! But I didn't want to update to latest version 7.2.2 because I heard you can't root it with magisk because of you do it won't boot..... But I just tried it In fastboot... Fastboot oem disable_dm_verity an it says it worked but when I rebooted an tried removing an app from system/priv-app to debloat through root explorer it says it failed!

Should I download the stock 7.2.1 from Nvidia developer website an fastboot flash it an then try it?
[Shield Android TV General] mLgz0rn:
I'm on 7.2.2 with magisk.

Adb disable-verity wont work since you are not on the developer build. There has been added some crazy amount of protection to the rom...
[Shield Android TV General] Davepratt1987:
So do I download the 7.2.2 stock rom from Nvidia developer website an do a full flash through fastboot?

Nm I'm doing it anyways an see what happens!

An I know it's kinda bs
[Shield Android TV General] mLgz0rn:
Ya!

And then read this post I made here on how to get magisk working and the device to boot.

https://xdaforums.com/showpost.php?p=78715291&postcount=95

You only need to disable-verity if your patched boot is not patched with "preserve avb 2.0/dm-verity".

Heres a different scenarios where you shield don't boot.

You patch the boot without preserve avb 2.0/dm-verity, this will give you are bootloop, since dm-verity is enabled, this can be fixed by flashing the stock boot again and then do adb disable-verity then flash the patched boot. This way you will have magisk and verity will be disabled.

You can also patch the bootimage again with preserve avb 2.0/dm-verity and then flash it, but with this dm-verity won't be disabled, and if you do adb disable-verity it will probably give you bootloop when you reset, and then you will have to patch a boot that doesn't have preserve avb 2.0/dm-verity
[Shield Android TV General] Davepratt1987:
I'll probably do adb disable-verity then flash the patched boot.img.... I just did it an it booting me into bootloader. What I did is did the command adb disable-verity it says it work! Then I rebooted into bootloader then flashed the patched boot.img an it's not booting! I hate Nvidia right now

Nm I got it thank you so much for your help!
[Shield Android TV General] mLgz0rn:
Was preserve avb 2.0/dm-verity checked in magisk when you patched the boot? You need to uncheck it, then patch the boot.
[Shield Android TV General] Largewoodenspoon:
So, I'm still too chicken **** to update to 7.2.2 dev image and try to root....Even though a really decent guy on here pm'd me some help....

For a few reasons :

I'm unsure as to have to do a clean install, factory reset etc.

I've got a 128gb usb as adapted storage, will this affect anything if I unplug it to flash a new image?

What about the dm verity when patching the boot img?

Does the patched boot img need to be renamed afterwards?

Is it really full root?

So many questions I know.

I'm still on 7.1.0 on 2017 16gb model.

Does patching the boot.img have to be done on the exact device? That's to say, how come you can't just use a universal image with boot.img already modified?

I'm probably being stupid, but I'm just asking before I potentially brick my shield!
[Shield Android TV General] Largewoodenspoon:
I'm replying to myself.... Lol

All fine and done.

7.2.2 dev os fully rooted with magisk.

Not hard at all. Dont know why I was worried!