Theory about why Netflix & Amazon refuse to play after SSD Update...

Ichijoe

Senior Member
Feb 11, 2007
605
92
48
Frankfurt am/Main
Ok I just managed to really screw up my nSATVP last week by basically deleating the bootloader from my Device.... Why did I go and, do that for? You ask. Well thats 'cause I signed up for nVidias Beta Test Program for v5.0.1 which hasn't been released yet. And like always TWRP choked on it, and the Shield couldnt install the OTA. So in a fit of desperation I decided to stupidly downgrade it back to v3.3.0. which resulted in the Black Screen of Death. Though as a consolation I still had Fastboot, at that time.

In any case I managed to recover my Shield, via the SSD Conversion Thread(s), where someone was kind enough to post the needed start, and end bins which can then be copied to the SSHD/SSD. Of course this comes at a cost. You loose Netflix, and of course Amazon as well... Some People have likened this to be down to the ESN (Netflix: Electronic Serial Number).

Having a bit of a nose 'round... I'm inclined to think its more down to the lose of Widevine L1.... At the moment I only have L3 access. And, I'd be willing to jump in a fire at this point as the cause.

What I was wondering was it it could be possible to copy the missing /data/mediadrm/IDM1013L1 Files back from a working Shield TV?
 

wikkid76

New member
Oct 13, 2014
3
2
0
I was hoping you'd get a response.

I lack the technical know how to find a solution to this. But I do have a 1st gen shield running that start and end bin files, and I (stupidly) tossed the original Shield drive before finding out Netflix and Amazon would be broken.

I've done a fair bit of reading and have yet to see a fix, or really anyone working on one.

Would love to have my 1st gen Shield able to work with Netflix and Amazon once again.
 

Ichijoe

Senior Member
Feb 11, 2007
605
92
48
Frankfurt am/Main
Well my understanding on this matter is that once you lose Widevine L1, than that's it! The only way to get it back would be to send it back to nVIDIA (Or hereafter The Factory), and let them to reset it. As only the Factory can install either L1, or L2 Widevine. Widevine L3 (The lowest level DRM Setting), however can be installed pretty much by anyone. As unlike L1, and L2 which are Factory set. L3 is Field settable, so we're just SOL.

Perhaps I might try contacting nVIDIA at some point about what it would cost to fix this outside of warranty. My only fear is that it would likely be the same price as a new Shield.

So the plan (for me) right now is to just suck it up, and lay some money again to the side, and pick up another Pro, down the line. And than strip the SSHD, and create the start, and end bin, backups, and than make multiple on, and off site copies of that. Than most likely, as not resell the broken Shield TV on FleeBay. To recoup some of the loss.

The morale of the story here is if your going to root, and install TWRP on your Shield Pro. You should first make the appropriate backups, and for the same reasons. It's rather disappointing in hindsight that all the How To's out there never bother to mention it. There are plenty of veiled threats about downgrading the Shield. But, bricking the Shield TV that way is way to easy. Easier than it should be.
 
Last edited:

hallydamaster

Senior Member
Aug 27, 2010
515
147
63
Copenhagen, Denmark
I was hoping you'd get a response.

I lack the technical know how to find a solution to this. But I do have a 1st gen shield running that start and end bin files, and I (stupidly) tossed the original Shield drive before finding out Netflix and Amazon would be broken.

I've done a fair bit of reading and have yet to see a fix, or really anyone working on one.

Would love to have my 1st gen Shield able to work with Netflix and Amazon once again.
Well my understanding on this matter is that once you lose Widevine L1, than that's it! The only way to get it back would be to send it back to nVIDIA (Or hereafter The Factory), and let them to reset it. As only the Factory can install either L1, or L2 Widevine. Widevine L3 (The lowest level DRM Setting), however can be installed pretty much by anyone. As unlike L1, and L2 which are Factory set. L3 is Field settable, so we're just SOL.

Perhaps I might try contacting nVIDIA at some point about what it would cost to fix this outside of warranty. My only fear is that it would likely be the same price as a new Shield.

So the plan (for me) right now is to just suck it up, and lay some money again to the side, and pick up another Pro, down the line. And than strip the SSHD, and create the start, and end bin, backups, and than make multiple on, and off site copies of that. Than most likely, as not resell the broken Shield TV on FleeBay. To recoup some of the loss.

The morale of the story here is if your going to root, and install TWRP on your Shield Pro. You should first make the appropriate backups, and for the same reasons. It's rather disappointing in hindsight that all the How To's out there never bother to mention it. There are plenty of veiled threats about downgrading the Shield. But, bricking the Shield TV that way is way to easy. Easier than it should be.
I'm trying to locate the partition containing the serial number.

If any of you guys could post me an output of the nct partition, it would be a help hopefully.

Extract it using this dd command:

Code:
dd if=firstpart.bin of=nct.bin skip=20480 count=4096
Substitute "firstpart.bin" with whatever your bin file has for a name.
 
  • Like
Reactions: Ichijoe

Ichijoe

Senior Member
Feb 11, 2007
605
92
48
Frankfurt am/Main
Ok heres the nct.bin File you asked for. you can find (I think... according to my Hex editor on Linux), the S/N @ Offset 040014.

Please note that since I can not post *.bin Files to this Board I took the liberty of simply renaming it *.zip instead.
SO PLEASE REMEMBER to rename this back to *.bin. Before you start looking at it.

BTW: Assuming your going to do what i think your going to do with this how would you re-insert this again?
To the File which you (or I), ripped it from, or to the SSHD direct?

Thanks
 

Attachments

Last edited: