yashsingh1/xdaforums huggingface dataset:
[Shield Android TV Android Development] AndroidUser00110001:
Are all the partitions showing up in TWRP that should be? I never put TWRP on my 2015 Shield Pro so not sure what should be showing up.

On my 2017 I can only write to the TWRP folder using the USB cable connected to my PC. I tried to put in a USB stick but TWRP did not recognize it nor does it recognize External Storage.

I have USB hard drive formatted for internal storage so not sure if that is why I don't see any partitions in TWRP and can only write to the TWRP folder.

I am about to build TWRP from source and was just wondering what partitions shows up from more experienced users so I can adjust the TWRP settings so more partitions show up if that is the cause....
[Shield Android TV Android Development] brandonb21:
I just got an email from nvidia and they processed my rma and now waiting for a tracking number i doubt il see mine till next week or i would help you out.
[Shield Android TV Android Development] brandonb21:
try disconnecting the usb cable going from your pc to your android box right after hitting enter after typing "fastboot boot twrp.img"

seems to be a bug. make sure it downloads the image all the way before disconnecting.
[Shield Android TV Android Development] brandonb21:
use the retail one, the dev image can run beta drivers such as graphic drivers that may or may not cause issues at some point. and the developer image dosent get ota updates.
[Shield Android TV Android Development] yojoe600:
Was able to root mine as well by pulling out the usb cable while booting into twrp. Thanks Guys!
[Shield Android TV Android Development] brand0n9:
how do u install supersu with the usb cable disconnected?
[Shield Android TV Android Development] AndroidUser00110001:
Enable MTP in TWRP, plug USB cable in and then transfer SU to the internal drive?
[Shield Android TV Android Development] Slayerkodi:
So this IS working for shield 2015 now??
[Shield Android TV Android Development] darkuni:
Alright guys ... After everyone started talking about having to unplug the cable, I restored to stock and tried to root again.

And - as people have said - TWRP won't boot with the cable in. VERY ODD.

When I enable MTP and insert the cable again - it beeps a few times and reboots. So can't get SuperSU on that way.

My solution? I used a cheap USB 3.0 4 port hub. Put the mouse and flash drive with SuperSU on it into the other USB port.

Poof - mouse with TWRP and USB Storage mounted.

While that is all fine and well - I'd prefer a method without the hub.

Anyone have any other ideas? NOTHING USB works in the outer USB port other than the USBtoPC cable.

I can't find another reliable way.
[Shield Android TV Android Development] AndroidUser00110001:
Strange. I can't mount USB and never had to pull the cable out. I can mount MTP.

Not sure if this could be it but do you have the latest ADB/Fastboot files?
[Shield Android TV Android Development] darkuni:
Yeah, I got the latest and greatest.

What's funny is ... the FIRST time I did it? It was fine! ADB sideload - no problem.

Since then? No TWRP without jerking the cable out.
[Shield Android TV Android Development] demdream:
great thnk for the works !
[Shield Android TV Android Development] darkuni:
Did we make any headway in avoiding the Google corruption screen with TWRP?

I actually managed to get a RED screen telling my device was corrupted and could not be trusted ;)
[Shield Android TV Android Development] AndroidUser00110001:
No not yet.
[Shield Android TV Android Development] SwisSwiss:
hey android user,

first off...great work and thank you for this... it is to my understanding this will not work for the 2017 pro version correct?....I believe I read somewhere that trying to root your 500gb shield will effectively give you 11gb of usable space afterwards is this true?

regards

Jeff
[Shield Android TV Android Development] AndroidUser00110001:
Thanks!

I have not tested it on Shield 2017 Pro but others have said it works fine.
[Shield Android TV Android Development] AndroidUser00110001:
Posted a new build which should allow TWRP to handle OTA updates for 2017 Shield 16GB models.

If someone can post the build.prop file for 2017 Shield Pro then I should be able to add that to the list too for OTA updates
[Shield Android TV Android Development] SwisSwiss:
ill try rooting my shield later tonight or tomorrow and if I succeed ill try to get you what you seek....
[Shield Android TV Android Development] AndroidUser00110001:
Thanks. If you have ADB you don't need to be rooted to grab build.prop

ADB pull /system/build.prop
[Shield Android TV Android Development] SwisSwiss:
oh snap! didnt know this
[Shield Android TV Android Development] SwisSwiss:
so I tried using an old usb A- A cable I had lying around (one i got eons ago to connect a printer) and it doesn't seem to work. there is no communication between my laptop and the shield pro despite usb debugging, so im guessing only usb 3.0 cables do the trick.... your going to have to be a little more patient for the prop build :s.... iv ordered the cable and Ill hopefully get it tomorrow if not then after the weekend...
[Shield Android TV Android Development] g1dtf:
Trying to re-root my 2015 after updating to 5.02 however when I type "Fastboot boot twrp.img" I am getting "data transfer failure" error and the shield reboots. I have tried pulling the USB after issuing the command but cant get it to boot into TWRP to install SuperSU.
[Shield Android TV Android Development] AndroidUser00110001:
Did you update your fastboot/adb files? May need the latest version.
[Shield Android TV Android Development] SwisSwiss:
I cant seem to get my laptop and shield to interact...according the tutorial on this site im suppose to "enable USB" in storage (im not talking about usb debugging thats not a problem) however the "enable USB" appears for like a second then vanishes... I was able to turn it one just before it disappeared but didnt solve anything.... this leads me to think its either a wrong USB cable again, despite it being a 3.0 this time....

or my laptop security programs are blocking it some how... the only way iv been able to get the two to communicate is via bluetooth.... if i turn bluetooth off on my laptop it wont show in devices and printers or device manager despite being connected to usb..... any insights?

i feel the solution is in plain sight but its zooming over my head
[Shield Android TV Android Development] AndroidUser00110001:
Do you have the USB storage device plugged into the correct port on Shield? If you do not have USB storage device then you do not need to turn it on...
[Shield Android TV Android Development] HarmfulMushroom:
I sent you a copy of mine through PM.
[Shield Android TV Android Development] AndroidUser00110001:
Got it. Thanks!
[Shield Android TV Android Development] HUYI:
will twrp ever get support for 4k tvs, unofficial and official? i'm getting closer to getting a 4k tv so i'm sol if i do.
[Shield Android TV Android Development] HarmfulMushroom:
Hey I had the same issue, I was using a USB male to male cable I made myself but nothing was working. Computer not seeing anything. I didn't realize the 2017 Pro has a micro usb port, that is the port you need to use. I'm embarrassed to say how long it took me to realize that, but as soon as you swap cables you're computer will see it!

Just FYI, the cable it came with does not work well at all for fastboot. You might want to find another one.

Also I think I enabled both network and usb storage by quickly enabling the settings before they vanished. You just have to be very fast.
[Shield Android TV Android Development] SwisSwiss:
*face palm*...thank you!... managed to root thanks to your post....

EDIT: spoke to soon, thx to harmful mushroom I was able to make a step forward though.... so I was able to unlock boot loader (wasnt sure but when i entered the command again it said bootloader is already unlocked) however i seem to be unable to boot the recovery image..

this is the error I get...

D:\Minimal ADB and Fastboot>fastboot boot recovery.img

downloading 'boot.img'...

FAILED (data transfer failure (Unknown error))

is it the cable that sucks?

EDIT 2: yep it was the cable that sucked, used the one that came with a ps4 controller and it worked
[Shield Android TV Android Development] SwisSwiss:
success!!! I confirm this works on the shield tv 2017 Pro, no memory loss after rooting and used a micro usb to usb A cable (thanks again harmfulmushroom) thank you for all the time put into this, adroid user you still need the build.prop?
[Shield Android TV Android Development] AndroidUser00110001:
Got the build.prop for 2017 Pro. Looks like 2017 Pro is exactly the same as the 2015 Pro.

When you got your 2017 Pro did it ask to upgrade as soon as you booted? If so then someone can grab the update URL for the 2017 Pro and should be able to flash it on the Pro since so far it looks like there are no changes between the 2015 and 2017 models.
[Shield Android TV Android Development] SwisSwiss:
yeah, updated immediately no ifs, no buts, no coconuts....
[Shield Android TV Android Development] HarmfulMushroom:
Same for me unfortunately. I thought you could still grab the url by clicking on check for update but I guess not... Next time an update goes live I'll sniff out the url. Or logcat it, whichevers easiest.
[Shield Android TV Android Development] AndroidUser00110001:
Not sure if it is a TWRP theme issue or something different in TWRP code. Trying to figure it out but I have no 4K screen to test with. A separate TWRP for 4K screens may need to be built.

I am a bit confused as what it can be. Don't 4K screens fall back to 1080 or whatever the resolution is of input device?

Does bootloader and stock recovery show on 4k screens?
[Shield Android TV Android Development] AndroidUser00110001:
4K Test

Anyone with 4K monitor want to test this to see if TWRP is displayed?

The UI will be off...just wondering if anything will be displayed now. If so then I can fix up the UI layout.
[Shield Android TV Android Development] AndroidUser00110001:
Asked in how to build TWRP thread about 4K issues...

If anyone wants to pull the log...
[Shield Android TV Android Development] SwisSwiss:
I may be saying something completely stupid but....a while back i was looking into why my genisis emulator console would not play game gear games and as it turns out its not a question of "scaling" or program writing but rather an issue related to the amount of color used by the two systems.... could this be the case for 4K tvs too?
[Shield Android TV Android Development] AndroidUser00110001:
Could be. It's one of the things I was going to try but do not have a 4K TV to test with :) No one has responded to my 4K test build yet so will wait and see if this first fix covered it.
[Shield Android TV Android Development] edjanx:
Installing TWRP on a 2017 500 GB Shield using a 4K HDR10 / Dolby Vison TV

I just finished unlocking the bootloader on a 2017 500GB Shield using the guide here:

http://nvidiashieldzone.com/shield-...t/tutorial-root-shield-android-tv-pro-nougat/

I've got an LG 55" OLED w/HDR and Dolby Vision. Unless I'm mixing my concerns, I believe I got around the 4K limitation when unlocking the bootloader by setting my Shield Video Video output setting down to 1080p. When unlocking, the stock bootloader displayed fine.

The TWRP available on the 'nvidiashieldzone' site is "TWRP (Hacked; Darcy), v 3.0.2h", and now that I'm ready for that step, I'm not sure which to install, so opinions are welcomed.

Thanks,

Janx
[Shield Android TV Android Development] AndroidUser00110001:
That's an older version. Try the recovery attached to the first post in this thread.
[Shield Android TV Android Development] SwisSwiss:
I used the one found here and it worked flawlessly
[Shield Android TV Android Development] ammadkhan:
shield pro 2015 nougat not flashing with this recovery twrp

I have shield pro 2015

recently i had updated to nougat.

my bootloader is unlocked but i am not able to flash twrp image.

is there any solution

this error comes every time

target reported max download size of 67108864 bytes

sending 'recovery' (15140 KB)...

FAILED (data transfer failure (Unknown error))

finished. total time: 5.030s
[Shield Android TV Android Development] jionny:
I didnt even know about the new twrp I used the darcy hack version on my 2017 pro and it worked fine
[Shield Android TV Android Development] sdv79:
UNOFFICIAL-twrp-3.0.2-ALL-Shields-build4K.zip NOT work: Samsung UE55KS9000+ Shield 16GB 2017
[Shield Android TV Android Development] lavero.burgos:
Thanks for this. It worked out of the box on my 2015 16gb shield tv.

I've used it to root full android nougat and also to go back to stock nougat 5.0.2 by flashing the OTA, though it gave same errors but my shield booted and worked just fine.

I've also wiped system, dalvik, data (including media), cache without issues.

For the record i used a 1080p tv and the original usb cable that came with my shield tv. Always use high quality cables and make sure it works well for big file transfers.

Enviado desde mi Moto X via Tapatalk!
[Shield Android TV Android Development] imaleecher:
I was receiving the same issue until I ordered a new USB 3.0 Male to Male cable and that fixed the issue. This was the one I ordered.

https://www.amazon.com/gp/product/B003VTZ07U/ref=oh_aui_detailpage_o04_s00?ie=UTF8&psc=1
[Shield Android TV Android Development] Ichijoe:
I'm not sure how you mentioned to test this. I'm fairly sure this would load fine over a 4k Display, once permanently installed as the system recovery. However just loading it up though fastboot without installing it as system recovery, just ends in the same 'ol black screen.

So than not much use for me then, as I have since sworn off from ever installing TWRP as system recovery on the Shield. Having done so has already cost me my Widevine L1 Status, and cause of that I'm no longer able to use Amazon, or Netflix on my Shield TV.

So I really hope someone will manage to crack the Nut on how to get TWRP to fastboot boot though fastboot over 4k. But, but for me this isn't that release.
[Shield Android TV Android Development] AndroidUser00110001:
Do you have the pro model and try to switch out the hard drive?
[Shield Android TV Android Development] HUYI:
could be a while, i don't get my 4k tv for another couple of weeks or so, one guy here did downgrade the display to 1080p to install twrp so that could work i guess.
[Shield Android TV Android Development] Ichijoe:
Yes I have the '15 Pro, no I never swapped the SSHD, as I unfortunately had nothing to replace it with.

My problems began after I requested joint the 5.0.1 Beta Program, about what, Three Weeks ago now? Sadly TWRP does not apperently play nice with the Nougat Updates. I recall having to reinstall the Stock OS, before installing v5.0 as well. So I thought I could get away with downgrading the Shield back to v.3.3.0 again. Well I thought wrong, and hard bricked it.

Thankfully this thread managed to let me recover my Shield, but I lost all the original DRM Keys that Device might have had. The practical upshot of which is I no longer can access either Amazon, or Netflix. So the idea of a maformed ESN, seems unlikely. As the ESN is surly almost a randomly generated number. That is dependent upon the Device Administrator, and the local WiFi Network. From what I can tell it will also change if you do a Factory Reset. So while that guess might be closer than I'm personally willing to admit. It seems more likely to me that the permanent lose of L1 Widevine is more likely the culprit here.

You can download a tool called DRM Info to check this. I'm fairly sure the Shield should be a Level 1 class Device. After using the Backup here it degraded to a L3 Status.

As things are I can not see any other way then sending the Shield back to nVIDIA (Presumably at cost), to be repaired. The only question is, is it worth it?

As an aside.. I'd love to see this fork into a method of creating what would otherwise be know round these parts as a nandroid backup. Probably to late for me. But, for those with a similar setup with out an older 1080 i/p Set, and need to install TWRP as System Recovery, just to use it. This step would likely save them from ever finding themselves in a similar situation.

Of course with all of this being on a mere removable Drive, it makes it much simpler. So I doubt this could be even done on the 16Gb version.

In any case I plan on replacing that Unit at some point before long, and when I do. Stripping the SSHD, and creating it's Backup snapshot will be of the outmost priorites for me.

Yeah I must have gotten One of the very last '15 3D Sets before they went extinct. :)

I thought I could use that mode to force 1080p as that's the only supported 3D mode, and just live with. Spilt Screen at worst. But alas that doesn't work for, Fastboot boot (mode). The only way I can get TWRP to show up on my Display is to flash it as my Recovery. Normally not a problem. Assuming it could deal with OTA Updates, which it can't. Which eventually lead to even larger problems for me. And as I might have mentioned the loss of pretty much anything that required L1 access to Widevine.

So I if you can't fastboot load TWRP over, a 4k I would begrudgingly take it to a relitves house who had an older set, and prepare to eat crow. As for me installing TWRP is now on my sh-- list of things NOT to do or recommend.
[Shield Android TV Android Development] HarmfulMushroom:
There was a new upgrade to 5.1, here is the url to download it. This was from my 2017 pro console.

http://ota-downloads.nvidia.com/ota...-full_ota-1915764_848.4973.20170215003807.zip

Let me know if you need anything else, I'll finish upgrading later tonight just in case there is something else.
[Shield Android TV Android Development] AndroidUser00110001:
I had issues when I enrolled in the beta program too but have not checked if my DRM keys got screwed up. I do not use Amazon or Netflix but will try it out to see if anything happened.
[Shield Android TV Android Development] Ichijoe:
Unless you got soo screwed up, that the only viable means of recovery was to flash the Start, and End Bin Files from the SSHD > SSD Migration Thread. I doubt you have much to fear.

Unfortunately flashing TWRP on my Shield TV, instead of just loading it threw Fastboot. Has lead me to make some very stupid mistakes regarding the Bootloader. Which in turn only left me with this One alternative. I can NOT say that I was somehow ignorant of the fact that in having done so that I would presumably lose Netflix than forever. That much I probably could have lived with. Alas as per the rumors I doubt the problem lays solly in the ESN (i.e. Netflix: Electronic Serial Number),. As that Number can, and should change with each Factory Reset, or possibly under a different Network. In fact if you ran your Shield offline (not that you would want to mind), the ESN will change to 'UNKNOWN'. That for me was a large clue. Also the fact that Amazon should somehow use this as a means to lock Prime down. Is also to me ludicrous. And the simple fact is what used to be a L1 Widevine Device has since been degraded into a an L3 One.

Thus why I wished I knew about all of that before hand. It could have saved me so much stress.

BTW: I would like to stress that my 'Issues' were TWRP, and 4k related. As I have made the misfortune step to upgrade to a 4k Panel, and ditch the old HDReady 720p Panel. I can not just simply, load TWRP up, as One does via a Fastboot, and expect it to run. Not even the last reportedly 4k fix can do that for me!

No in order to use TRWP, and I can even on my 4k'er. I'll have to replace my Recovery with it, only then will it load up. Which is great if all you want to do is flash SuperSU. NOT so great when it hijacks the updater and causes the OTA to fail. Which in turn lead to me the SSD thread.
[Shield Android TV Android Development] AndroidUser00110001:
I messed up my 2015 Pro and tried to recover it using the SSD Migration thread but that didn't work and I broke my HD ribbon cable :) Going over my steps I think there was a bigger problem because of no video being outputted by shield which lead me to do stupid things too.

I usually have Netflix disabled and it shows UNKNOWN too for the ESN.

So with 4K TVs if you install TWRP and not boot into then it works? You can always flash TWRP, do what you need to do and then flash back the stock recovery.
[Shield Android TV Android Development] AndroidUser00110001:
Thanks! I believe the 2015 Pro and 2017 Pro are identical in hardware and use the same ROM images.

Anyone have the link for the 2017 GB? I was in the beta preview and the preview 2 ended up being the official update so I never got a chance to grab the OTA file...
[Shield Android TV Android Development] Ichijoe:
No TWRP only works once I've installed it as the Recovery. It does not simply work (like one would expect it to), by just simply loading it up though Fastboot.

fastboot boot recovery TWRP-*.img on a 1080i/p Set *GOOD!*

fastboot boot recovery TWRP-*.img on 4k *Black Screen!*

fastboot install recovery TWRP-*.Img - then subsequently loading directly into TWRP (over 4k [MENTION=921577]1080P[/MENTION]), WORKS!

nVIDIA OTA Updates have all failed me under TWRP.

The idea was to first revert the recovery back to stock. Alas being on Nougat it would seem that the Shield was ignoring the Marshmallow version. As I was neither able to load it or install it.

So the next step was to try downgrading back to Marshmallow. Alas that led me to lose all Video (nVIDIA Logo), as well. I was at least able to patch up a Netbook with ADB Fastboot in order to enter Fastboot Mode. Alas what I didn't have was the recovery.img for Nougat, and the recovery.img for Marshmallow was not working for me.

I seen someone suggest erasing the bootloader, and recovery. And thought I'd try that. And that's where I got into trouble. And I had to eventually use the Start, and end *.bin Files in order to halfway recover my Shield TV.
[Shield Android TV Android Development] lavero.burgos:
You have widely messed with your Shield TV by being in beta program, flashing back to MM from Nougat and flashing non official recovery and root. You've done it all.

If you know and accept the consecuences of being a guinea pig then just deal quietly with it.

It is known (if you do your homework and research before messing around which is always a good and the correct practice to follow) that if you mess with the bootloader you can really hard brick your device and not soft brick like i read it's happened to you too. Nvidia does have the tools to recover a hard bricked Shield TV and thus easily accepts them for RMA if you have the receipt and is under warranty but even warranty can be avoided if you just talk them and convince them or provide a receipt of a friend with a Shield TV same model as yours and still under warranty. I also know that in Europe warranty period is longer compared to USA.

Please stop repeating the same over and over again and work together with the dev to test and find a solution or simply just wait for the next patch fix to test.

Having said all that i again want to mention that I've flashed this twrp recovery and also have flashed OTA zip with it to go back to stock 5.0.2 in my Nvidia Shield TV 16GB 2015 from full android nougat with errors yes but without issues as the system booted up in stock just fine.

I still have DRM L1 so my Shield TV is in good condition and has not been affected or corrupted at all by TWRP.

Enviado desde mi Moto X via Tapatalk!
[Shield Android TV Android Development] savagepagan:
You just may need a better quality cable. I had to do the same as you by pulling out the cable after sending the command. Then I changed cables and it worked without having to pull the cable out.
[Shield Android TV Android Development] D-an-W:
I didn't test it on our 4K TV but the TWRP release in the first post worked fine with the latest SHIELD TV update but

ONLY

when I replaced the USB cable that has worked fine with previous updates with the cable supplied with my XBOX One Elite controller (Go figure!).