yashsingh1/xdaforums huggingface dataset:
[Shield Android TV Android Development] Steel01:
Finally got around to updating official twrp. If you've had problems in the past, please try again. This works on all models again: old emmc, new emmc, and sata. As an added bonus, I recently picked up a Jetson TX1 and it works on there too. Gonna release a flash package for that one of these days.

NOTE: Still haven't been able to do anything for the 4k display problem. Yes, mine fall back to 1080p for recovery. I assume the ones that don't work are not failing back for some reason. I may build a 4k specific unofficial version some time and see if that works for the others. Don't know if that will make any difference, though.
[Shield Android TV Android Development] darkuni:
Time to retire Hacked Darby?
[Shield Android TV Android Development] Steel01:
I've seen you mention this 'hacked darby' a couple times, but apparently am out of the loop. No clue what you're referring to there.
[Shield Android TV Android Development] darkuni:
That's okay ... I just grabbed your new official build.

Shield TV Pro - Works great. I'll test it on the Shield TV 2015 at some point - but if it works on the pro, I'm certain it works great on the 2015 16GB.

Shield TV 2017 - Not only does it work great, but no longer do I have to jerk the USB cable out after executing fastboot boot twrp.img. If that wasn't enough of a bonus, ADB Sideload appears to work (it failed one time I tried it - but I rebooted and tried again). This is great news.

I can't recall where I go the hacked darby twrp - but the first days of Shield TV 2017, it was the only one that worked.

Thanks a bunch for this. I can update my tutorials to be a lot more simple now.

---------- Post added at 06:49 PM ---------- Previous post was at 06:35 PM ----------

The hacked DARCY (it's been a long weekend) came from this thread. Just for reference.
[Shield Android TV Android Development] jeky82:
is this one the correct one to flash on 2017 model?

https://twrp.me/nvidia/nvidiahshieldandroidtv.html
[Shield Android TV Android Development] ClintE1956:
Received sata version Saturday (kudos to Newegg, less than 2 day ship time with normal shipping!?).

Played around with unit for a little while, then decided I want to run some apps that aren't available in Shield Play Store. Gotta keep things simple for WAF (stock launcher), so looks like Flashify multi-boot is the way to go. First step, root this thing.

Enabled dev menu, adb usb debugging.

Drivers on PC working for adb and fastboot modes.

Let it sit at unlock bootloader screen for a long time (factory wipe?), console on pc finally returned success status messages, "Please wait..." on Shield fastboot screen went away.

Restarted to system main screen (fresh out-of-box again), enabled adb usb debugging, then rebooted back to fastboot.

Tried to boot temporary TWRP image, just sat at same screen as unlocking ("Please wait..." or whatever) for a long time.

Unplugged power, waited a minute and plugged back in, came up to main launcher screen quickly.

Restarted to fastboot, tried to just flash TWRP via adb, unit immediately restarted to main launcher screen.

Tried both TWRP procedures again, same results.

Everything else seems to work fine.

Should I try to unlock bootloader again?

Maybe factory reset first?

Thanks for any suggestions, criticisms etc.
[Shield Android TV Android Development] Steel01:
[MENTION=4872616]ClintE1956[/MENTION]: Glad to see I'm not the only one running into this... Chances are, it's a problem with the USB cable. It's seeming more and more that the cables shipped with the shield devices don't handle adb on foster very well. They work perfect for roth and shieldtablet, but no end of troubles on foster. Do you have other cables to try? Also, I'm going to link this to a bootloader dev I'm in contact with.
[Shield Android TV Android Development] jionny:
Forgive me but is this the pro version you are referring to? if so it takes at least 2 hours to unlock the bootloader
[Shield Android TV Android Development] ClintE1956:
Interesting. I did try a different USB cable and swapped USB ports on PC with same results.

---------- Post added at 02:08 PM ---------- Previous post was at 02:02 PM ----------

Yes, pro version, and it did take about that long. The console messages on the PC about writing data seemed to verify that the procedure was successful.

When I attempt to boot a temporary TWRP image, it shows same message "Please wait...". Is it trying to unlock again? I didn't get a confirm message like when I issued the "fastboot oem unlock" command.
[Shield Android TV Android Development] Steel01:
No, it should just boot. But due to either a bug or a bad cable, weird things can happen in fastboot. For me, any time I try to fastboot boot or flash on my foster_e_hdd, the device just resets without actually processing the command. I had been having the same issue on darcy until I bought a new USB 3 cable, now it works consistently. I'm waiting to hear back from my contact on the bootloader team again now.
[Shield Android TV Android Development] ClintE1956:
Isn't the Shield's micro USB port only 2.0 spec? If so, a USB 2.0 computer port connected to it should work properly with good quality cable.

Please correct me if I'm in error.
[Shield Android TV Android Development] Steel01:
So, this isn't a straight forward answer... Yes, the *micro* usb port is 2.0 afaik. The host ports are 3.0. For darcy, the 2017 emmc model, the is no micro usb port. One of the host ports is convertible and can be used with an a-to-a cable for adb and bootloader. I'm not certain what spec it uses for the client mode. But either way, a 3.0 cable should be better shielded and all. And is backwards compatible.
[Shield Android TV Android Development] DJarkIV:
I just asked a question regarding the convertible port in the Q&A thread. Any idea if adding "persist.convertible.usb.mode=host" to the build.prop (on stock ROM), followed by factory reset will gain me simultaneous use of that port without having to turn adb on/off? It's becoming a real pain
[Shield Android TV Android Development] Steel01:
Some updates have been pushed and 3.2.1.0 has been released as of a few hours ago. Everything should work, sans the problem with a handful of 4k displays. If any issues are found, new or old, please report. I'm more easily able to push updates and fixes now.
[Shield Android TV Android Development] ClintE1956:
3.2.1.0 installed & working great!

USB behavior is a little different than 3.2.0.0.

Setup:

Shield TV Pro (newer version with new controller & remote)

Micro USB port connected to PC (which is rarely powered on)

First USB3 port (closest to HDMI) connected to Shield controller (only when using fastboot) using micro USB cable that came with Shield

Second USB3 port connected to Anker USB3 10-port powered hub with generic wireless mouse receiver, Logitech Mini Remote Control Keyboard (DiNovo) receiver, Unitek USB 3.1 single-drive dock (SSD installed) all plugged in & powered on

When using 3.2.0.0 & computer powered off, I could restart into recovery and mouse would work.

With 3.2.1.0, I have to unplug USB hub's data cable after restarting into recovery then reconnect it to get mouse to work. This is when the computer is powered off.

If I power on computer, then mouse works when restarting into 3.2.1.0.

This is definitely not an issue for me; just wanted to mention it.

I also noticed I cannot restart into fastboot mode without the computer powered on when it's connected to the micro USB port on the Shield (not that I would have any reason to do this, as any fastboot work requires the computer). When I attempt this, the unit just restarts to stock launcher.

Many thanks to devs, and please keep up the great work!
[Shield Android TV Android Development] Sivabalan:
Guys can we use usb 2.0 male to male cable for fastboot related work in shield TV??
[Shield Android TV Android Development] MWin123:
Does the offical guide from the TWRP website work?

Apparently you can install TWRP via the TWRP app, if you have root. It also mentions a regular installation with fastboot, but there's no mention that you have to use a special usb cable or that you need the Shield controller. Is this info true?

Although I definitely don't like this part.

I bought the 2017 NVIDIA SHIELD TV with 16 GB without the controller. I'm on Android 7.0 and it says SHIELD Android TV SW-Version 6.3.

I also read something about issues with 4k. Does TWRP not work with my 4k TV or was that fix in the meantime?
[Shield Android TV Android Development] xd4d3v:
delete
[Shield Android TV Android Development] Mogster2K:
I found something odd... I recently got a 4K TV, and while 3.2.1.0 does not work if I use "fastboot boot", it does work if I flash it and then boot from recovery.
[Shield Android TV Android Development] mLgz0rn:
Is there anyway to fix not being able to see the internal user storage? Also not being able to mount sd card/usb otg?

At the moment I am only able to see the root of the internal storage.
[Shield Android TV Android Development] Andy4Shurr:
After updating to Oreo I get "error 1", unable to mount vendor when attempting to flash magisk. Do we need an updated TWRP for the new oreo firmware?

EDIT: I got it to work by manually patching the boot.img in magisk and flashing via ADB. Is this a TWRP or Magisk issue then?
[Shield Android TV Android Development] Mogster2K:
I don't know, but Zulu99's Full Android has the same problem. At least we have a workaround that, y'know, works. ;)
[Shield Android TV Android Development] Andy4Shurr:
Hopefully it will be fixed before we have a magisk update.
[Shield Android TV Android Development] laharl_22:
2015 ROM and twrp work on 2017 version ?
[Shield Android TV Android Development] Amd4life:
Can you please detail your workaround method to use magisk?

Thanks
[Shield Android TV Android Development] aVlkaFenryka:
1) download the developer/stock OS from nvidia

2) unpack .zip and find boot.img

3) use the NSTV or another android device and install the magisk manager app

4) in the app: click install

5) in the app: choose patch boot.img

6) in the app: remember the outpot path from the terminal log to the patched_boot.img

7) boot to recovery (TWRP) and install/flash the patched_boot.img to boot partition
[Shield Android TV Android Development] Amd4life:
Awesome!!! Works perfect
[Shield Android TV Android Development] BigMatza:
I just got my 2017 16GB this week, and it's on the latest Oreo build. I've unlocked the bootloader and rooted, and everything's going well. I just wanted to ask the XDA community what the sudden trend is towards using "fastboot boot" (which I used) instead of "fastboot flash". I've always just flashed TWRP in the past. But lately I'm seeing mixed messages about flash causing issues in Oreo. I'm not sure if it's specific to the Shield, or if it's all Oreo devices.

Could someone please take a minute to spell this out? Why wouldn't I want to flash TWRP and keep it on the box?
[Shield Android TV Android Development] ldeveraux:
"fastboot flash" is a permanent recovery replacement, while "fastboot boot" is temporary. This device is so quirky, that many people just want to boot recovery to root/install custom ROM, rather than have TWRP permanent.
[Shield Android TV Android Development] whiteak:
Can you not just flash Magisk in twrp or does this not work on the Shield?
[Shield Android TV Android Development] Mogster2K:
Flashing Magisk in TWRP works on the 2015 model, but it might not work on the 2017 model.
[Shield Android TV Android Development] whiteak:
Thanks, I ended up just patching the boot.img and flashing the patched boot.img through Fastboot. Installed Magisk Manager, Stock 2017 Shield now rooted with Magisk.
[Shield Android TV Android Development] darkuni:
FYI: Update 7.2 appears to break TWRP. Sits on the NVIDIA boot screen. Hopefully we'll see an update on TWRP soon!
[Shield Android TV Android Development] Steel01:
I'm gonna need kernel source for the new release before I can make an update. So, until then, gotta wait.
[Shield Android TV Android Development] darkuni:
I reached out to Nvidia. Can't get anything any faster than the official release cycle. Damn shame.
[Shield Android TV Android Development] iLLNiSS:
Came here to say this! Thanks for confirming.
[Shield Android TV Android Development] Steel01:
I reached out to a contact as well. Doesn't know where it's at in the process. It's not cool, though. Since it's a GPL violation to release a binary kernel without source being available. Even though Nvidia is better than a lot of manufacturers, they're still technically violators every single release.
[Shield Android TV Android Development] darkuni:
So uh ... where is that source code, NVidia? :D
[Shield Android TV Android Development] ahmao:
looks nvidia shield experience 7.2 breaks twrp. the boot stuck at nvidia logo. have to flash back to 7.1 to get twrp installed, rooted, and there is no data lost.

https://developer.nvidia.com/gameworksdownload

http://developer.download.nvidia.co...ATV_2017/5.1.0/HowTo-Flash-Recovery-Image.txt

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 Android Development] darkuni:
Yep .. Steel is waiting for the required legal release of the kernel source code so he can fix :D
[Shield Android TV Android Development] TheUndertaker21:
mine is stuck on bootloop but i can wait for steel since i don't use my shield much
[Shield Android TV Android Development] darkuni:
Yeah, I never flash TWRP; just boot to it - in case of situations like this.
[Shield Android TV Android Development] ErAzOr2k:
was anyone able to downgrade from 7.2?
[Shield Android TV Android Development] Mogster2K:
Nope. My foster just hangs on the Nvidia logo when I try to boot anything. I guess I have to wait for the official 7.2 download.

Edit: I don't know if it matters, but Nvidia has a 4.9 kernel source at "git://nv-tegra.nvidia.com/linux-4.9.git". However, they forgot to set the HEAD ref so you have to pick a branch after cloning.

Edit 2: Nevermind, it won't compile (missing files.) Unless I picked the wrong defconfig. I think this repo was made for the new Jetson boards.
[Shield Android TV Android Development] bubbablacksmith:
Was wondering why when I tried to boot into twrp it would just hang forever. Glad to know it's not just me. I will keep an eye out on this thread, thanks to those who end up fixing this issue! Much appreciated.
[Shield Android TV Android Development] bp328i:
So annoyed right now. I flashed the NVIDIA SHIELD ANDROID TV Pro Developer Only OS Image 7.1.0 and now my Shield Pro won't boot. I can get into the bootloader fine and I even ran factory reset from the bootloader (almost 3 hours to complete, which I expected) but when the Shield tries to boot it just sits on the Nvidia screen. Also when I try to run boot recovery kernel from the bootloader it also just sits on the Nvidia screen.

I flashed via

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

Anyone know if this thing is now a brick?
[Shield Android TV Android Development] psycho_asylum:
I'm quite literally in the same position, albeit with a non-Pro. We'll have to wait for them to release the kernel sources for a new TWRP build and/or the 7.2 stock image. I saw on the geforce forums that the image should be out today.
[Shield Android TV Android Development] bp328i:
I ordered the 16gb version and it's being delivered tomorrow. Any suggestions on what I should not flash?
[Shield Android TV Android Development] psycho_asylum:
Based on what I've read over the past few days, you shouldn't flash anything if it gets updated to 7.2. If the device is on an older Shield Experience when you receive it (it should be 7.1 or older anyway) then you should be fine.
[Shield Android TV Android Development] bp328i:
Thanks, so hopefully when the stock 7.2 image is released I won't have a 500gb brick sitting here anymore.

Then I can use the new 16gb one in the bedroom.
[Shield Android TV Android Development] iLLNiSS:
I did the OTA upgrade to 7.2, realized I lost root and there is no root for 7.2 yet.

I can't really say the exact process I did but it took a bit of messing around as I was getting stuck at the nvidia logo.

I 'think' what solved it was using the batch file included with the prerooted developer 7.1 image as manually running the commands (for whatever reason) would cause it to get stuck at the logo. This was using the stock recovery.

If it matters this was on the 16gb 2017 model and was just purchased this month. Bootloader was unlocked the whole time. I don't remember what version it shipped with.
[Shield Android TV Android Development] Downunder35m:
I have a thread for the possible downgrade options, might help some people to check.

TWRP fails because in the new Fstab configuration we no longer have a system partition listed.

Vendor can't be accessed either so most of the required things fail to work and TWRP won't do a thing.

To make it short: once stuffed try to flash the 7.1 boot image first.

If not enough then you need to flash the full 7.1 - through the batch file and not manually please.

But only if the Shield was fully setup prior you get to the home screen, in all other cases you will be forced to update to 7.2.

Might be easier to just install the 7.2 directly, set it all up and then downgrade to the 7.1 to skip the update ;)
[Shield Android TV Android Development] Mogster2K:
Meh. I can't even use the batch file. It requires being able to boot into the regular system, and my foster just sticks at the green logo.
[Shield Android TV Android Development] bp328i:
Same issue on my Pro.
[Shield Android TV Android Development] AthieN:
FYI everyone - I was at 7.1, skipping the 7.2 update due to losing root and just a few minutes ago, my device AUTOMATICALLY updated to 7.2.1! It did not give me an option. I turned it on, got some message about 7.2.1 being available and the next thing I knew, it was rebooting and installing 7.2.1!

Luckily, the update completed successfully and I'm at least up and running. But I did lose root and don't see a way to get it back atm until I can get my hands on a 7.2.1 bootloader...

So if you don't want this to happen, I'd suggest turning off automatic updates asap!
[Shield Android TV Android Development] bubbablacksmith:
Is it possible you accidentally hit select on the remote and told it to install?

I know when I turned on my one Shield tonight (7.1), it was presenting me with a "What's new in 7.2.1" full screen update menu.

On the right side there was 2 options, to install or remind later. I believe by default the install button was selected, so if you hit OK it would have installed immediately. I told it to remind later and it didn't bother me again.
[Shield Android TV Android Development] AthieN:
That makes sense. The device was sleeping and I usually press select on my Logitech remote to wake it up. So doing that probably triggered the update and restart... Freaked me out though because I was beginning to think that Nvidia was going to start shoving updates down our throats automatically! Lol
[Shield Android TV Android Development] Mogster2K:
Well, the source is still not out, but they did finally post the 7.2 images.

https://developer.nvidia.com/gameworksdownload

Which version of the Shield do you have? I've heard that Magisk currently works on the 2015 models but not the 2017s.
[Shield Android TV Android Development] bp328i:
I'm not seeing the 7.2. images posted.
[Shield Android TV Android Development] bubbablacksmith:
Weird, I see them all at the top of the list.

You will need to be logged in, but here's direct links to the developers images.

2015 16gb shield 7.2.0 developers image

https://developer.nvidia.com/rdp/assets/nv-recovery-image-shield-atv-7.2.0-dev_rooted.zip

2017 16gb shield 7.2.0 developers image

https://developer.download.nvidia.c...ry-image-shield-atv-2017-7.2.0-dev_rooted.zip
[Shield Android TV Android Development] bp328i:
I logged in and still don't see them...it is weird. Any chance you can link me to the 7.2 for the Pro? I need to try to get it back up and running.
[Shield Android TV Android Development] bubbablacksmith:
Does this work? This is the Pro 7.2.0 dev image.

https://developer.download.nvidia.c...ery-image-shield-atv-pro-7.2.0-dev_rooted.zip
[Shield Android TV Android Development] bp328i:
Thanks but it's saying

File not found or link expired
[Shield Android TV Android Development] bubbablacksmith:
Weird.

Okay here's an alternative. I downloaded it and then re-uploaded it to my dropbox.

7.2.0 developer's image for the 2015 Pro Shield TV.

https://www.dropbox.com/s/dd4pl4nf73oteq7/nv-recovery-image-shield-atv-pro-7.2.0-dev_rooted.zip?dl=1
[Shield Android TV Android Development] bp328i:
Thank you so much, downloading it now. For some stupid reason I updated to 7.2 and then flashed the 7.1 dev image and it won't boot past the Nvidia logo.
[Shield Android TV Android Development] bubbablacksmith:
No problem. Hope it helps to fix your issue.
[Shield Android TV Android Development] bp328i:
I'm going to tired at work tomorrow because I'm doing it now. I'll let you know how it goes.

Thanks again!
[Shield Android TV Android Development] Downunder35m:
The only image of help for someone with a stuffed Shield would be the recovery image as the rest more or less require working devices.

If you see only the Nvidia logo but then nothing else happens during boot:

Connect the controller with the cable, hold A and B pressed while you re-power the shield - you should get tinto the bootloader mode.

When power is connected the controller vibrates, keep holding A and B until you see the bootloader screen.

From there and with a male to male cable in the first USB port you can flash the recovery image.
[Shield Android TV Android Development] bp328i:
Just wanted to say thanks again, my Pro is back up and running. It did auto update to 7.2.1 and wouldn't let me go any further without rebooting to install 7.2.1, no root but it's up and working again.

When this all started I ordered a new 16gb version, now I have my Pro back in the living room and my new 16gb for the bedroom.

---------- Post added at 10:37 PM ---------- Previous post was at 10:34 PM ----------

I got my Pro back up and working with the file bubbablacksmith posted.
[Shield Android TV Android Development] psycho_asylum:
Same but I used the non-root image that was on the download page. It updated to 7.2.1 successfully.
[Shield Android TV Android Development] bp328i:
Good to at least be back up and running. When this all started Monday night I ended up ordering a 16gb Shield. Now I have one for the living room and one for the bedroom.

I can think of a lot worse things than to have two working Shields...lol
[Shield Android TV Android Development] banderos101:
Yeah, i can feel your pain.......you lucky so and so :)
[Shield Android TV Android Development] AthieN:
I have the 2017 model.
[Shield Android TV Android Development] Mogster2K:
Well, /system and /vendor are mounted on partitions 19 and 21 respectively, but I'm not sure how. Maybe in the init binary in the ramdisk?
[Shield Android TV Android Development] TheUndertaker21:
I can confirm that I'm rooted on 7.2 with magisk 18

Shield tv 2015

I just disabled system upgrade with titanium backup so it doesn't upgrade to 7.2.1
[Shield Android TV Android Development] darkuni:
Magisk doesn't require TWRP? Don't know much about it.