yashsingh1/xdaforums huggingface dataset:
[Shield Android TV General] Kamikaze01:
just go through this Tutorial.

Everything worked like a charme...

ADB find the shield, i patched the boot.img and copy it to the developer img.

But after fash-all.bat my shield stuck at reboot... i see the "nvidia" Logo and nothing happen.

I can still enter fastboot mode with my controller and then i got a serial number when tiping "fastboot devices"

So i try to put every single command

fastboot flash staging blob
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash vendor vendor.img
fastboot reboot

but still stuck on "nividea" Spash screen :( What else can i do?

i even flashed the whole dev image without patched boot.img - then install magisc and patched the boot.

Then flash the dev imgage with patched boot.img.... --> stuck on "nvidia" screen :(

It seems, that after patching the boot.img with magisc, something went wrong and it stuck on boot.

If i did not patch the boot.img, i can flash the developer image with no problems...

is there a problem with Magisk?

I almost tried EVERYTHING (flashing developer image, normal stock image, patch this boot.img or that boot.img... but I CANT ROOT MY SHIELD).

Here on github is something about this problem...
[Shield Android TV General] mLgz0rn:
Patching the boot.img does not work on pie unless you have the 2017 model and use the canary build of magisk to patch it while being on the developer image.

Take a look at this thread https://xdaforums.com/shield-tv/development/kernel-overclock-kernel-2-22-ghz-t3943079 for an alternative.
[Shield Android TV General] Kamikaze01:
Thank you [MENTION=7186920]mLgz0rn[/MENTION] for your answer... Finally I got it sorted with twrp :)

I am rooted in 8.0.1 :)

Phuuh.... Happy again ;)
[Shield Android TV General] elliwigy:
ur forgetting a data wipe.. i.e. fastboot -w
[Shield Android TV General] DumbKing@letthemeatspam:
I don't have a wired mouse, is there any other way to do this?
[Shield Android TV General] ldeveraux:
I've used a wireless mouse with dongle, should be no difference.
[Shield Android TV General] DumbKing@letthemeatspam:
I only have a bluetooth one unfortunately
[Shield Android TV General] Kamikaze01:
i think after unlock bootloader everythink should be wiped ?!?

Anyway - i got my root with TWRP and Magisk :) so for me everythink is working now :)
[Shield Android TV General] elliwigy:
i use a bluetooth keyboard/mouse just fine.. it has a usb dongle tho..

u can go to goodwill or somewhere and get a usb mouse for close to nothing as well
[Shield Android TV General] elliwigy:
technically yes but you should reboot and setup device before going back in to root n install twrp

i wipe each time i install new firmware.. if i get hangs or boot loops usually a wipe fixes it for me..

either way, urs is working now so good job!

im probably going to purchase the new model.. xda reporting some best buys are now selling them early :)
[Shield Android TV General] Ghisy:
Hi,

Would anyone mind sharing the best process to apply the update from the 8.0 dev (rooted) ROM to the 8.0.1 patch that got released not too long ago please? I need to keep TWRP and root of course!

Thanks!
[Shield Android TV General] elliwigy:
did the dev ed get an update? if u let it update itll update to stock 8.0.1 im pretty sure..
[Shield Android TV General] Ghisy:
It did not. But not sure what happens if I let it update to 8.0.1. I don't want to break root and all.
[Shield Android TV General] mLgz0rn:
You will anyways.

Magisk needs to be flashed/patched after you update.
[Shield Android TV General] elliwigy:
yea.. like he said, when updating ota it installs updated boot n recovery n other partitions removing ur patched stuff.. best bet is to update manually n patch wat u need to before updating it
[Shield Android TV General] SkOrPn:
Thanks but I posted in the wrong thread for some odd reason.
[Shield Android TV General] DumbKing@letthemeatspam:
Has anyone tried flashing 8.0 with the new version of Magisk 20.1? I'm still getting stuck on the Nvidia logo, any help is appreciated.
[Shield Android TV General] s3phir0th115:
I'm getting the same thing, even with doing a data wipe along with flashing the boot image. Flashing the original, unpatched boot.img seems to make it boot again, but it'd still be nice to have Magisk.
[Shield Android TV General] mLgz0rn:
https://xdaforums.com/shield-tv/development/kernel-overclock-kernel-2-22-ghz-t3943079
[Shield Android TV General] equlizer:
Silly question. Someone told me you will loose netflix when rooting this device. Wouldn't magisk hide fix that problem just like on any other android device?
[Shield Android TV General] SkOrPn:
I watch Netflix HD every single day year after year after year on my rooted shield TV. Never once been a problem.
[Shield Android TV General] shub:
kernal

Hi All

its been long since i did any custom flashing....

i have the 2017 Sheild and i manage to load twrp and push the magisk_shieldtv_pie_r2...device is rooted and the app is showing in the side-loader

does this confirm i have the correct Kernal or i should be flashing the kernel_r1,4. to gain extra performance?

if so, how do i flash the kernel_r1.4?
[Shield Android TV General] pop4xda:
I tried flashing kernel 1.4 and got stuck at Nvidia on booting.

My shield is 2017 16gb version.

Only magisk_shieldtv_pie_r2 works for me.
[Shield Android TV General] shub:
ah - is this a known issue?
[Shield Android TV General] kcls:
Hey y'all! I have a 2017 Shield and I'm attempting root on a macbook pro with only USB C ports. I cannot get the shield TV to show up under ADB devices. I can, however, get the shield to show up on ADB over the network. But I don't have an external keyboard, so once I get into the bootloader using adb reboot bootloader, I'm stuck again. I need to be able to use fastboot commands to flash and unlock everything, and that obviously only works over USB in the bootloader.

I tried using both the USB -> USB C cable that came with my Pixel 3, as well as several different micro USB cables with a micro USB -> USB C converter to plug into my laptop. I've tried all the USB ports on my laptop, and I've tried both USB ports on the back of the Shield, though both the bootloader and the screen shown after enabling usb debugging tell me the USB port furthest from the HDMI port is the one to use. I tried both just to be sure.

I was going to go pick up a USB A -> A cable later today and use a friend's windows laptop to try this again, but does anyone know if there might be something I'm missing?
[Shield Android TV General] nadia p.:
I would like to revert back to 6.3.0, however when I do, it forces the 7.2.1 update which puts me back to square one. I've not found a successful way to prevent this from happening so far. If I can't revert back to 6.3.0 I'd then attempt 7.1.0 since everything was working fine for me there. The 7.2.0 and 7.2.1 have broken a few things from working and I can't find a solution there either. I even tried debugging which IP Addresses to block and add them to the firewall in my router. There are so many this method doesn't seem to work.

Thanks for your comments. :)
[Shield Android TV General] ACiDxCHRiST:
If userdata.img exists in the image that you are flashing or if you see one of the lines in flash-all.bat starting with "fastboot -w" then that is the same as a data wipe and will trigger Initial Setup. Extract the image that you are trying to install and edit the flash-all.bat to remove the command "fastboot flash userdata userdata.img" or delete "-w " depending on which one applies to your situation.
[Shield Android TV General] nadia p.:
After examining several of the OS Image packages for "Shield TV" it seems the only one that contains the userdata.img file is found in the SHIELD TV Pro (500GB) hierarchy found HERE. As the userdata.img seems to be contained in a more complex package with an internal hard drive it may not work properly for the SHIELD TV 2017 (16GB) model I own. I've not found anyone that has tried this and reported it working 100%.

SHIELD TV 2017 (16GB) -- NVIDIA SHIELD TV 2017 Developer Only OS Image 6.3.0 (2018-01-31)

nv-recovery-image-shield-atv-6.3.0-dev_rooted.zip

flash-all.bat

PATH=%PATH%;"%SYSTEMROOT%\System32"
fastboot flash staging blob
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash vendor vendor.img
fastboot reboot
[Shield Android TV General] Largewoodenspoon:
Hi there.

Can I do this guide but with 7.2.1 straight off?

Many thanks and merry Christmas!
[Shield Android TV General] nadia p.:
Hello Largewoodenspoon, I'm sorry, I'm unclear what you mean. The 2017 (16GB) I have is currently at 7.2.1 because of forced updates. I've been able to successfully flash 6.3.0 and 7.1.0 however since it wipes everything it then forces the updates back to 7.2.1. Logically there should be a simple way to (A) block the IP addresses to only allow Google Play so one can sign-in but prevent access to Nvidia's forced lookup and downloads. e.g. install a hosts file with blocked IP's. (B) Unpack the *.img that contains OTA, rename it to _OTA so later if required it can renamed and used but in the mean time the other programs can't access it. Repack the *.img and flash that. (C) Somehow backup the existing data currently on the device where it understand the ADB connection, already signed-in to Google Play, etc.... then install that last before rebooting so you regain access through ADB and manage things yourself, before the forced install is complete.

---------- Post added at 04:30 PM ---------- Previous post was at 04:15 PM ----------

Hello ACiDxCHRiST, I believe this workaround may work since 7.2.x is close enough to 7.1.0 that overwriting only the boot.img while the rest remains the same won't affect the integrity of the install. I have a few questions. Is the state of the bootloader locked or unlocked on your device before you flash the "patched" boot.img? Also which version of OS are you extracting the boot.img to be patched (Developer Only or Recovery)? I may have missed this information in your original posting. Once I know the exact state the device is in and which boot.img to patch I'd like to try reverting back to 7.1.0 to see if I can manage to not refuse the update and see if I can at least get that working with the other apps as before these 7.2.x problems (for me anyway) started.
[Shield Android TV General] MrCrc:
Hi,

[MENTION=3373302]ACiDxCHRiST[/MENTION]: Thank you for your tutorial. Now I am on 7.2.1 dev rooted on foster model...

Regards

Crc

Gesendet von meinem ONEPLUS A5000 mit Tapatalk
[Shield Android TV General] ACiDxCHRiST:
Not yet, because NVIDIA hasn't posted the Dev/Recovery images for v7.2.1 yet. You need to be on v7.2.0 then follow the steps in Optional Stuff and Additional Information to Download the OTA, patch the boot.img, and install it to get to rooted v7.2.1

If you are already on v7.2.1, just follow the guide to get on v7.2.0.

I think you are under the impression that flashing causes a data wipe and that is

NOT

the case. Once you go through the Initial Setup and are forced to update to v7.2.1 and reach the Home Screen on v7.2.1, flashing v7.1 or v7.2 will

NOT

cause another data wipe and force you to update.

You can use either the RECOVERY or the DEVELOPER image, it does not matter.

If you are going to flash a different version from the one you have installed, you need to flash the whole flash-all.bat

Do not flash a v7.2.0 boot.img to a v7.2.1 install by itself (or any other combination). The only time you should flash ONLY the boot.img is if it is a Magisk patched version of the same version that is currently installed.

Your bootloader needs to be unlocked to flash ANYTHING in bootloader/fastboot mode.
[Shield Android TV General] nadia p.:
If I'm following you here's what I understand for:

SHIELD TV 2017 (16GB) model P2897.

1. The bootloader is currently unlocked. sign booting to standard Home Screen.

2. Nvidia 7.2.1 is the current OS, originally I had installed 6.3.0 developer (rooted) that was force updated.

3. Signed-in to Google Play, installed Magisk Manager 6.2.1 and X-plore File Manager

3. I have followed this guide and patched the boot.img file from 7.1.0 developer (rooted) and hope to be able to then run flash-all.bat (with the patched boot.img) and revert back to 7.1.0, unless I have to revert to 7.2.0 first. This part I'm not clear on.

4. From there I should be able to still have access to Home Screen after rebooting and Cancel the 7.2.1 update and change the optional settings per your suggestion.

5. When finished to not lock the bootloader as it will then wipe the data, correct?

This may then get me back to a state which the Apps that were broken in 7.2.x will work again.

Am I following you or have I really missed something badly?
[Shield Android TV General] ACiDxCHRiST:
Yes, if you have an unlocked bootloader and are on v7.2.1 past the Initial Setup and on the OS Home Screen, perform steps E through F. Just replace all mentions of v7.2 with v7.1

There is no need to go to v7.2 first if you want to be on v7.1

NEVER lock the bootloader if you have anything other than 100% stock full RECOVERY Image installed. Never even try it.
[Shield Android TV General] nanerasingh:
i have 2017(16gb) model,

7.2 devloper OS to 7.2.1 ota update, then it again updated with one more ota 7.2.1.(dont know why two times 7.2.1)

Currently System info shows unknown Nvidia version.

So i want to know how to get existing boot.img as no root working.?

Or how to downgrade back to any previous version? and start the guide mention in this thread.?

If anyone provide me patched boot img will work?
[Shield Android TV General] ACiDxCHRiST:
Follow the guide to downgrade to v7.2.0
[Shield Android TV General] nanerasingh:
Can you tell me which post? Thanks
[Shield Android TV General] nanerasingh:
Skip forced update,

I have got once succeed on developer rooted 7.2 to pass the force upgrade and go to home screen without updated to 7.2.1.I am not 100% sure if it will work for others becasue i just did it once.

1.Was on 7.1 then I flashed 7.2 developer version.Go to setup wizard and configured google account wifi everything.Then it will ask for update and let it download updates.

2.After update click restart. Note:- When shield reboot and at Corrupted unlocked bootloader screen just directly power off shield and boot again. Dont let it go to Recovery update otherwise it will update to latest 7.2.1.

3.After reboot will be on setup wizard screen again but directly to update again and let it downlaod again and restart and power as mentioned in step 2 above.

4.Reboot this time you will see a screen to install update later or now. click later and click remote home button & you will be on HOME screen and change setting dont update auto update,adb debugging on. and clear the ota updates-adb shell pm clear com.nvidia.ota

i am not sure if this will work on non rooted 7.2 images.

I will recheck this method again.i updated to latest OTA 7.2.1 on my developer rooted 7.2.And i lost the adb root on 7.2.1.Due to adbd production build.Will downgrade to 7.2.currntly i dont have 7.2.1 stock boot.img for magisk install further dig.
[Shield Android TV General] zulu99:
with dm-verity enabled you can't write system partition.

to disable dm-verity on darcy you need a custom dtb that you can find on my forum

and.....

flash a bad boot image not brick the device, just a bad bootloader can brick the device.

if you flash a bad boot image, you can flash another because the bootloader is working.

before write guides on root, study how android work !
[Shield Android TV General] ACiDxCHRiST:
Thanks for the information.
[Shield Android TV General] nanerasingh:
Can anybody tell me is it safe to flash all 7.1 firmware on my 7.2.1 firmware?

please give me some small guide to downgrade to 7.1.
[Shield Android TV General] ACiDxCHRiST:
Literally just follow the guide replacing all mentions of v7.2 with v7.1

At the end, you will be on v7.1
[Shield Android TV General] pop4xda:
Just curious why you wanted to downgrade from 7.2.1 to 7.1.

I'm still on SU rooted 7.1 and considering to upgrade to 7.2.1 with Magisk root.
[Shield Android TV General] melo_mx:
Hey guys,

Decided to replace my shields hard drive with a SSD Samsung 860 pro 500GB.

Followed this guide to get the latest update installed (Shield Experience 7.2.1 with root). Everything worked perfectly!

Thanks alot for the guide!
[Shield Android TV General] Downunder35m:
With no offense meant in any way I feel the need to clearify a few things:

Post 1 does not works as I was at this stage about 2 weeks ago already.

What it does is give you root rights but not for writing to any vital part of the partitions.

Basically useless.

It looks good at a first glance but at least on the Darcy models will fail to give you write access, not even a pull through ADB works.

All of my collected results and soon a proven and working way to fully root under 7.2(.1) is available here.

This includes tested to work downgrade options in post 3.

Within the next 24 hours a fully working solution will be made available there by myself or a good friend of mine who figured it out and tested it already.

I will still work on a clean firmware that includes a full root but for the desperate there will be a fix before the year is over :)
[Shield Android TV General] DumbKing@letthemeatspam:
I had this same problem with MacBook Pro and USB C cable. There's something wrong with the android tools / adb or fastboot in the way that it handles USB C, but I couldn't find anything from google on it

My solution was to find windows laptop and use that

Also I think the latest Magisk fixes the boot loop issues we were having so we should be all good to go now!
[Shield Android TV General] elliwigy:
Nice! To clarify you flashed 20.2? How did you update it? I'm going to try tomorrow. Just not sure if you just updated through magisk manager or twrp and if you had to do any steps from the original method?

Also was it a clean/fresh install or did you just update? Reason I'm asking is because if you had it set up to change verifiedboot state to get around the hanging on boot then the modules would have still been in place i.e might not have noticed if this is still an issue since u already had it setup if that makes sense..
[Shield Android TV General] cHECKjAM:
How can one add a entry in the hostfile of a rooted shield easiest way? Possible with a filemanager like total commandor? Or do I have to use adb and do like a pull/push or something?
[Shield Android TV General] DumbKing@letthemeatspam:
great question I tried to go from 20.1 (Nvidia shield TV 8.0.1) to 20.2 in magisk using the direct install method but I got a boot loop again :(

Were you able to update to 20.2?
[Shield Android TV General] elliwigy:
nope, same here lol.. even tried through twrp like we do with the special zip but still wouldnt boot
[Shield Android TV General] DumbKing@letthemeatspam:
weird it says it was fixed here:

https://github.com/topjohnwu/Magisk/commit/476b61c4c9675b87d027aa43f559c360affbc5c9
[Shield Android TV General] elliwigy:
yea i kno.. i been goin back n forth there also on it.. need to do more testing and provide more data to assist them in figuring it out
[Shield Android TV General] dandemonic:
Is yours the 2019 shield?

Updated my 2017, 8.0.1 from stable 20.1 to 20.2 ok but had to reinstall V4A drivers

I originally used rootfan's modded magisk zip via adb twrp, to root 8.0, then magisk manager for stable versions since.

2 days ago I updated stable 20.2 to 20.3 and app warned no magisk installed.

Tried restarting twice, still no magisk, so left fixing it for another day, and turned off at power brick.

Was going to sort it next day, maybe roll back to 20.2 via adb twrp.

Turned on next day, from completely powered off at the wall, and now magisk works.

Have turned off completely several times since and magisk still works.

No idea if helpful, just sharing what happened for me.

rootfan's OP of shield kernel thread mentions canary magisk working for models they support but I haven't tried.
[Shield Android TV General] elliwigy:
yes, i have nstv pro 2019

and they should have it fixed by next release.. [MENTION=4180946]rootfan[/MENTION] was kind enough to jump on github and tell them what needed to be done
[Shield Android TV General] toddre:
I have two of the 2017 boxes and no joy past 20.2. Tried several times both with a direct install and by booting TWRP and have had no success with 20.3 or Canary build as of Friday the 10th
[Shield Android TV General] devynel:
Shield Experience 8.0.2

Okay folks, hope all is going well in root-land.

So my teenager decided to update my shield tv 2017 to 8.0.2 OTA and I've lost root.

Anyone figured this one out yet or am I the first idiot in the village? :)
[Shield Android TV General] devynel:
Okay... All sorted! 20.2 works. :)

I need to avoid 20.3 and 20.4.

Happy days!
[Shield Android TV General] I_did_it_just_tmrrow:
Did you talk about the magisk versions?

So your kids update to the official ota 8.0.2 and you install magisk 20.2 successfully?

What is your device a foster or darcy?
[Shield Android TV General] devynel:
Correct and I'm Darcy.

I went back to basics. Once into TWRP I activated ADB Sideloading and pushed(with 'adb sideload Magisk-v20.2.zip') the 20.2 up and, lo, worked first time.

Thought I'd have a go at 20.3 and 20.4 but they didn't work for me but at least I have root back, which means rclone works, which means my Plex pulls from Google Drive. Yay!
[Shield Android TV General] DumbKing@letthemeatspam:
I can confirm latest magisk canary fixes the problems and we are back to rooting with Magisk on SHIELD 8.0+
[Shield Android TV General] vanzan:
Guys been a while since I checked in. I'm on 8.0.0 with Magisk 20.3. How would I go about updating to 8.0.2 without losing root? Maybe I should leave well enough alone going by the comments above!
[Shield Android TV General] vanzan:
This stuff is baffling. I was rooted, on 8.0.0 and had frozen the updater with Titanium and thought I was sorted. Then I checked Magisk Manager and it somehow said Magisk was not installed! I flashed 20.3 again, it installed but lo and behold a few days later it was gone again! LOL. So I installed the Canary Magisk Manager, switched to the Canary channel and flashed the canary magisk in TWRP. Manager did not show it as being there at all. Uninstalled Manager and went back to the old version. Flashed 20.3, unfroze the updater and updated to 8.0.2 (8.1.1 not showing for some reason).

For the laugh Installed Canary Manager again and flashed canary magisk with TWRP again but still not working. I haven't a clue about all this stuff. Bloody confusing. How come since I had Magisk 20.3 installed and had root and had the updater frozen that I lost root for no reason? Ridiculous.

Think I'll just leave it unrooted as I have a nervous breakdown everytime I go messing with Magisk and bootloaders and TWRP etc. Don't want to lose my data.

:edit: I THINK I HAVE ROOT! Canary Magisk doesn't show any magisk as being installed but I can browse the root files in a file explorer!
[Shield Android TV General] 1975Mark42:
Which canary file(s) did you use for flashing and/or manager? Do you have a link? Thanks!

---------- Post added at 05:38 PM ---------- Previous post was at 05:26 PM ----------

Which canary file(s) did you use for flashing and/or manager? Do you have a link? Thanks a lot!!
[Shield Android TV General] trohn_javolta:
I'm still on shield experience 7.2.3, rooted via magisk as described in the first post. I plan on updating to latest shield experience and want to have root. Since I already have a lot of stuff set up I don't wann mess this up.

So you just normaly updated your magisk rootet shield, then booted into twrp and flashed magisk 20.2.zip and that's it?

No need to enable -> provide full system upgrades, extract boot.img from /data/data/com.nvidia.ota/app_download, patch that boot.img with magisk, update system and then in fastboot mode do -> fastboot flash boot patched_boot.img?
[Shield Android TV General] I_did_it_just_tmrrow:
I think they used this, but I am not sure.

[MENTION=4828143]vanzan[/MENTION] [MENTION=9688438]DumbKing@letthemeatspam[/MENTION] can you help?