yashsingh1/xdaforums huggingface dataset:
[Shield Android TV General] GuyInDogSuit:
I mean how do you get the Pro key from the Play Store when it's not compatible with your Shield TV? I can only think of installing it on my phone (which is unrooted) and extracting it, then installing it on the Shield.
[Shield Android TV General] jionny:
pm me
[Shield Android TV General] GrandStar:
Can you still root at the latest update 6.3? Anyone here tried it yet?
[Shield Android TV General] GuyInDogSuit:
Yes, it still works. Next time, though, I'm just gonna flash the developer image and save myself the effort.
[Shield Android TV General] eturk01:
Yes, that would be so much easier! I had to reboot a bunch of times to get PC/USB recognized on port next to HDMI so I could use mouse on furthest port. PITA!

Where can we get the dev image?
[Shield Android TV General] GuyInDogSuit:
The latest one isn't up yet, unfortunately, and knowing them, it could take weeks.
[Shield Android TV General] Sivabalan:
Guys can we use usb 2.0 male to male cable for rooting procedure??
[Shield Android TV General] GuyInDogSuit:
Yes.
[Shield Android TV General] Sivabalan:
Bought a usb 2.0 cable and it worked fine for rooting the shield TV.
[Shield Android TV General] Parru:
I had problems to root with Magisk after failed update to 6.3 from 6.2 using Flashfire and Magisk 15.3. Only got black screen and after a while Shield did reboot. So I had use adb/fastboot to update. After this booted to Twrp for rooting. Magisk 15.3 install had "cannot mount /vendor" error and install failed. Also started to get "system corrupt" messages during boot.

Downgrade to 6.2, still error.

Didnt matter what image I did try, 6.2/6.3 recovery image or dev_rooted image

Full wipe, still same error.

Then I did to install Magisk 14.0 and suprise no errors on install and also "system corrupt" message on boot went away.

After Magisk Manager update to lastest version I was able to install Magisk 16 without problems.
[Shield Android TV General] foomanjackel:
Thanks, magisk 16 wouldn't install for me so I did same as you and tried v14. That worked, but after rebooting magisk manger would not update. So I downloaded the latest manager through my browser and installed it manually. That worked fine and the latest magisk manager updated magisk to version 16.

All is well now, thanks again
[Shield Android TV General] sebby64:
when I update rooted 6.3 to 7.0, then I lose root?
[Shield Android TV General] Sivabalan:
yes....wait for developer image to be release and flash it manually... I think we have to follow this step once we get the developer image....

https://xdaforums.com/showpost.php?p=75637186&postcount=4
[Shield Android TV General] EliotFR:
Hi guys,

The Downgrade Oreo 7.0.2 to 6.3 failed on a 2017 shield.

Now the Shield display a message who said me that the device software was corrupted and it stay stuck to the "NVIDIA" splashscreen.

I've test to acces at the fastboot without succes ( By the A+B method with a keyboard and a controller ).

So, what can i do ?

Is it hardbrick ?

Eliot
[Shield Android TV General] jionny:
Is the shield showing up as an APX device ?
[Shield Android TV General] darkuni:
I've never seen a successful downgrade from a major release point to a previous one. Many have tried and bricked, unfortunately. I've had a lot of people ask. I warn them away. :(
[Shield Android TV General] jionny:
I did a successful downgrade but then again mine is the pro and bootloader unlocked and rooted
[Shield Android TV General] darkuni:
Really? I have had many unhappy Oreo upgraders write and ask about a rollback. Might I ask what you did? Anything special?
[Shield Android TV General] EliotFR:
What is the apx mode ?

my display manager just show me a USB MTP device.
[Shield Android TV General] jionny:
just flashed the 6.3 developer image over the upgrade and worked perfectly
[Shield Android TV General] jionny:
device manager... because if it shows APX then it is bricked
[Shield Android TV General] darkuni:
Were you using a developer image of 7.x to begin with?

If you say with "dev images" across the board, maybe you're ok?

Last I checked dev images performed no OTA or upgrades. Is that still the case?
[Shield Android TV General] jionny:
I actually accepted a OTA 7.0.1 upgrade was on 6.3 developers image then I flashed then flashed 6.3 developers image
[Shield Android TV General] darkuni:
Interesting. So 6.x Dev images DID prompt you for an update. Did you lose root when you went to OTA 7.x?

Thanks a bunch for the info.
[Shield Android TV General] jionny:
yes I did lose root and also starting with 6.3 Nvidia implemented where even if you have root you can still take a OTA and it will install.. I found out also with oreo I had to have the latest twrp and supersu for the shield
[Shield Android TV General] Dany-69:
Hello guys :) One important question. The bootloader has to be unlocked in order to be able to flash the Developers image available here?

https://developer.nvidia.com/gamewo...HIELD TV 2017 Developer&tx=$additional,shield

Unlocking the bootloader lead the Shield to lose the Widevine L1 compatibility. My purpose is to root the device without losing Netflix HD and so on. :)
[Shield Android TV General] jionny:
I have been rooted and the bootloader has to be unlocked to achieve that. I also always use Netflix and have has zero problems with any type of compatibility issues
[Shield Android TV General] Dany-69:
You have answered none of my questions :D

1) I was referring to the developers system image available from nvidia...

I know the standard rooting procedure, but that was not my goal.

2) if the bootloader is unlocked, every Android device on the planet lose the Widevine L1 compatibility, lowering the security level to Widevine L3, which allow only SD for DRM contents.

You can verify this installing DRM Info from the play store:

https://play.google.com/store/apps/details?id=com.androidfung.drminfo&hl=it
[Shield Android TV General] jionny:
I don't know about that but what I do know is I have 7.1 developers image installed and I always get uhd and 4k from netflix with no problems
[Shield Android TV General] Dany-69:
Mmm so you've installed the developer image, but even unlocked the bootloader?

Bootloader unlocking was necessary for installing the developer image or is a conseguence of your root procedure? :o

Can you post a screenshots of DRM info for showing you widevine level? :D
[Shield Android TV General] brandonb21:
thats not good. no green light? maybe a bad power plug? put your ear up to the shield do you hear electrical noise?
[Shield Android TV General] GhostRider5666:
I hear electric noise. Did It brick itself? I never had this happen to me.
[Shield Android TV General] brandonb21:
it may have, maybe, if you do fastboot devices in cmd does it pop up? what about adb devices?
[Shield Android TV General] GhostRider5666:
Nothing?
[Shield Android TV General] brandonb21:
sounds like it killed its self. try unplugging it for 15mins and try getting into fastboot with the game controller method let it drain all the power. if it is bricked you still have hardware warranty through nvidia
[Shield Android TV General] brandonb21:
make any progress?
[Shield Android TV General] GhostRider5666:
Nope I think it's dead.
[Shield Android TV General] brandonb21:
RIP.. nvidia will cover it under their warranty. sounds like a hardware failure.
[Shield Android TV General] AndroidUser00110001:
Just getting the OmniROM and TWRP sources setup.

---------- Post added at 07:13 PM ---------- Previous post was at 07:08 PM ----------

If you are running linux try this

Power on Shield

open command prompt and type

ls /dev/sd*

See what sd* the shield is, it could be the last one listed.

then do this command

gdisk -l /dev/sdX

X bening what your shield is listed as

If you get a list of partitions let me know. You might be able to recover your shield depending on which partitions got hosed. You can flash boot.img and system.img and maybe blob since it is the only available img files to flash...
[Shield Android TV General] brandonb21:
my box bricked its self too. i was upgrading to 5.0.1 and my dog stepped on my power bar button shutting off in the middle of installation. and zero partitions are showing. and it smells burnt too. nvidia said they would replace it, sending it out tonight.
[Shield Android TV General] AndroidUser00110001:
I had issues with my Shield Pro 2015, got it within the past year but Nvidia will not warranty it since I can not locate the original receipt :)
[Shield Android TV General] brandonb21:
hopefully shipping wont take any longer then a few days.
[Shield Android TV General] loki495:
The 5.0.1 Developer (rooted) image for the 2017 16GB is available for download at NVIDIA already at https://developer.nvidia.com/gameworksdownload#?search=SHIELD%20TV%202017%20Developer&tx=$additional,shield
[Shield Android TV General] darkuni:
Doesn't show up for me. Also, I thought developer images didn't receive OTAs... no? We still need manual root :)

No downloads meet your criteria. Filtering by "SHIELD TV 2017 Developer", Additional: SHIELD.

I am logged in.
[Shield Android TV General] loki495:
Its not OTA. Its provided by NVIDIA for developers, and I do have the 2017 16GB so that meets my criteria? Filename says rooted already. Am I missing something?
[Shield Android TV General] darkuni:
I wonder why you can see it and I can't.... higher elevated account? I don't know.

From what I understand (and why I don't use them) is that developer images are locked to that version. So if 5.02 or 5.1 or whatever comes out? Your developer image won't get an OTA update. You have to get a new developer image (maybe a manual update? I don't know) if they release it.

I could be wrong. But that's what I understand.

Edit: Your screenshot shows 186 downloads are available. Mine shows 177 downloads available.

Willing to share? :)
[Shield Android TV General] loki495:
Well, flashed the images by running "flash-all.bat" from the nvidia download. Took a couple of minutes since it seems that "fastboot flash" sends packets of 60MB (system.img is almost 2GB, while the vendor.img is about 300MB). After it rebooted I confirmed I could "adb root" and "adb shell" with all permissions.

However, I wasn't able to get the "su" binary to be picked up by the SuperSU app. Here's what I did:

adb disable-verity (to be able to remount /system with rw permissions)

adb reboot

adb remount

adb push su /system/xbin

adb shell chmod 0755 /system/xbin

Going into shell without root and running su also did not work. This is what it looks like:

darcy:/ $ su

1|darcy:/ $ su -

1|darcy:/ $

it would just add the "1|" to the shell prompt. Not sure what it means. Same thing when trying to run anything as root. For example:

darcy:/ $ ls /sbin

ls: /sbin: Permission denied

1|darcy:/ $ su - ls /sbin

1|darcy:/ $

when /sbin is not empty.

But.... going into root shell and running "su - shell" did work and gave me the "shell" user's prompt.

Not sure where to go from here. Doesnt look like its the wrong binary. I also checked "echo $PATH" and /system/xbin is in there. What step am i missing? SuperSU app does not find the su binary as expected. Anybody know how to get su working, or has any ideas?

edit: maybe most of you know it, but don't try "adb enable-verity" after copying files. I wasn't sure what "verity" was until i did. After reboot it got stuck on nvidia logo, and I had to reflash the rooted image. Slowly, but I'm learning.
[Shield Android TV General] brandonb21:
I assume that you have in a folder on your PC the arm64 files su, supolicy and libsupol.so and the supersu apk that you can find in the supersu.zip

adb root

adb shell

mount -o remount,rw /system

adb push ./su /system/xbin/

adb push ./su /system/xbin/daemonsu

adb push ./supolicy /system/xbin/

adb push ./libsupol.so /system/lib64/

adb shell

chmod 0755 /system/xbin/su

chmod 0755 /system/xbin/daemonsu

chmod 0755 /system/xbin/supolicy

chmod 644 /system/lib64/libsupol.so

/system/xbin/daemonsu --auto-daemon &

adb install eu.chainfire.supersu.apk

Go in Android, start SuperSu app and accept to update the binary

Go in SuperSu settings and click on Install on system folder.

Restart and you have root.﻿-
[Shield Android TV General] slayerh4x:
We had this issue of the system overwriting TWRP after it was flashed. The dirtycow exploit is how they got it working on the LG V20 phone. Would that help at all here?

https://xdaforums.com/v20/development/h918-recowvery-unlock-v20-root-shell-t3490594
[Shield Android TV General] AndroidUser00110001:
TWRP...Done :)

Finally got it to boot. Let me test out and I will post it.
[Shield Android TV General] loki495:
Thanks for helping!

I tried this with the supersu downloaded from https://download.chainfire.eu/696/supersu/ but it still didn't work.

The mount command gave me a "Device busy error":

mount: '/dev/block/platform/sdhci-tegra.3/by-name/APP'->'/system': Device or resource busy

So i tried "adb remount" and continued....

No problems here...

This seems to run, but when hitting enter or running any other commands after that, it shows the command terminated. Running it without the & also shows it terminates right away.

darcy:/ # /system/xbin/daemonsu --auto-daemon &

[1] 4261

darcy:/ #

[1] + Done /system/xbin/daemonsu --auto-daemon

darcy:/ #

darcy:/ # /system/xbin/daemonsu --auto-daemon

darcy:/ #

darcy:/ # /system/xbin/daemonsu --help

SuperSU v2.45 (ndk:armeabi-v7a) - Copyright (C) 2012-2015 - Chainfire

Usage: su [options] [--] [-] [LOGIN] [--] [args...]

Options:

-c, --command COMMAND pass COMMAND to the invoked shell

-cn, --context CONTEXT switch to SELinux CONTEXT before invoking

-h, --help display this help message and exit

-, -l, --login pretend the shell to be a login shell

-m, -p,

-mm, --mount-master connect to a shell that can manipulate the

master mount namespace - requires su to be

running as daemon, must be first parameter

--preserve-environment do not change environment variables

-s, --shell SHELL use SHELL instead of the default detected shell

-v, --version display public version and exit

-V display internal version and exit

Usage#2: su LOGIN COMMAND...

Usage#3: su {-d|--daemon|-ad|--auto-daemon|-r|--reload}

auto version starts daemon only on SDK >= 18 or

if SELinux is set to enforcing

(call only from a root session)

Usage#4: su {-i|--install|-u|--uninstall}

perform post-install / pre-uninstall maintenance

(call only from a root session)

Usage#5: su --id pid

identify eldest parent of pid

(call only from a root session)

The app installs, but shows error "no su binary found and new one can't be installed" and it closes.
[Shield Android TV General] brandonb21:
nice, cant wait for the release from you, this should help until steel can get his shield and make an official version!

i think your using an outdated supersu. use this one https://s3-us-west-2.amazonaws.com/supersu/download/zip/SuperSU-v2.79-201612051815.zip and let me know how you make out.
[Shield Android TV General] AndroidUser00110001:
Root & TWRP...Done :)

Got Root and TWRP.

I hacked together TWRP to make it work. Will rebuild from sources but should make no difference.

Will post it in a few...

**EDIT***

Can be downloaded from here...

https://xdaforums.com/shield-tv/development/recovery-twrp-shield-android-tv-2017-t3545544
[Shield Android TV General] brandonb21:
did you flash it with fastboot flash recovery

or did you boot it with fastboot boot twrp.img
[Shield Android TV General] AndroidUser00110001:
fastboot boot

Link to download is in my post before this one...
[Shield Android TV General] brandonb21:
sweet! thank you! too bad im still waiting for my replacement from nvidia

i would just use TWRP now that its out to root your device!
[Shield Android TV General] loki495:
Still no luck. Same thing happens. Not sure if I hadn't noticed before, or because of the new supersu, but at least now it looks like the daemon does stay on, even when running it without &:

darcy:/system/xbin # ./daemonsu --auto-daemon

darcy:/system/xbin # ps | grep daemonsu

root 12220 1 11720 724 __skb_recv 202452b1f8 S daemonsu:mount:master

root 12224 1 11720 700 __skb_recv 202452b1f8 S daemonsu:master

However the new apk says it still doesn't find the su binary and it can't install it itself.

Awesome! I will be trying it soon if i can't get supersu to find the su binary. I'd eventually like to boot Full Android from USB, so probably need a custom recovery image to boot from usb, but that needs to be updated to darcy as well I believe, so not sure if i'll be able to keep both that and TWRP. If i can't get supersu to find su, i'll at least try to boot from it without flashing first. Unless i get impatient and just do it lol

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

Well you convinced me haha It bugs me nt having figured out what it was, but I guess no need to be making things harder than need to be. I will try fastboot boot and come back with results

Just one question. Would I flash the last zip you linked as it is?
[Shield Android TV General] brandonb21:
yup just put the zip on your sheild in a folder such as download folder, boot up twrp, and navigate to that folder and flash it. MAKE SURE YOUR BOOTLOADER IS UNLOCKED FIRST!
[Shield Android TV General] loki495:
Unlocking the boot loader is the first thing i did when I got the Shield so I wouldn't have to lose all the data.

Did you do it on stock 5.0.1 or the rooted Dev image? I flashed the Dev image, and couldn't get into twrp. I will try to revert to stock image.

Attempt #1:

fastboot boot Hacked-twrp-3.0.2-darcy.img

rebooted into nvidia shield, and rebooted into "no hdmi signal", with green light.

disconnecting and connecting it back boots back to android tv fine.
[Shield Android TV General] brandonb21:
Is your display 1080p or 4k? if its 4k for some reason 4k monitors/tvs will not work with twrp.
[Shield Android TV General] AndroidUser00110001:
No I used the no dev image.
[Shield Android TV General] loki495:
It is indeed 4K. Flashing the stock image and will try it on a 1080 tv
[Shield Android TV General] brandonb21:
yeah twrp wont work on a 4k tv. only 1080p tvs for now. once you root it and booted into android OS 1 time you can hook it up to your 4k tv again.
[Shield Android TV General] loki495:
Success!!

I was able to see twrp on my 1080 tv. Hooked up a wireless mouse w/wifi dongle, flashed supersu, and after 2 quick reboots I got 5.0.1 rooted on my shield 2017!

Thanks AndroidUser00110001 and brandonb21 for all your help!! If you guys need me to test anything else just let me know. I'm not a android/kernel/rom dev, but i know my way around linux and compilers if you need another tester or anything. Looking into getting into it, but I need to learn more.

Now, forgive me because i know its a bit off topic, but would you guys know if a recovery image to boot full android from usb for the 2015 would work with the 2017 shield? If no, no problem, you guys helped so much already. Thanks again!
[Shield Android TV General] brandonb21:
dont do it, my friend bricked his 2017 shield trying to use the 2015 recovery on the 2017, and it had to be sent to nvidia for a replacement.
[Shield Android TV General] loki495:
Thanks for the heads up. Not rushing into that yet then.

How about Xposed? Would it work as is, or would need an update as well?
[Shield Android TV General] brandonb21:
you mean the ROM development team? and their source ? if something isnt made specifically for the shield do not use it.
[Shield Android TV General] loki495:
I meant the Xposed framework in general. If it'll work as is for the 2017 or if it'll need an update. The framework is just a collection of apps/commands/wrappers that only require root right? So should work as is?

I just remember putting it on an old android tablet I had. Not sure if I'll need it or if it's worth it, but was just wondering, as it usually shows up as one of the "top things to do when rooted" for android devices
[Shield Android TV General] brandonb21:
i really dont know i never used it before.
[Shield Android TV General] yojoe600:
We are running nougat so I'm pretty sure xposed won't work. There is no Xposed for nougat.

Sent from my only One.
[Shield Android TV General] AndroidUser00110001:
Ha! I bricked my Shield Pro 2015 trying to get the 2017 update on it :)
[Shield Android TV General] darkuni:
YOU ROCK. TWRPed and Rooted Shield TV 2015 on Nougat. Now to update the tutorials and then do 2017 :) Glad Amazon overnighted me that male to male cable :) Chucked a couple bucks your way ...
[Shield Android TV General] AndroidUser00110001:
Thanks!

Just built a new recovery from source. Will post in the recovery thread but over the next few days I want to redo the Shield 2017 device tree from scratch so it works with the OmniROM 7.0 sources. Had to modify the Shield 2015 TWRP source files for the 2017 model and build with OmniROM 6.0 sources. I am sure there is no difference for the end user but I am anal like that...
[Shield Android TV General] darkuni:
Sounds great!

I have added the 2015/Nougat tutorial to Nvidia Shield Zone. Refactored into our newer tutorial format and tested it as I did it. Hopefully it helps someone out. Sigh ... now to do 2017 and Pro :)

http://nvidiashieldzone.com/shield-android-tv/tutorial-root-shield-android-tv-16gb-nougat/
[Shield Android TV General] AndroidUser00110001:
Did this recovery work on 2015 model too? Does the 2015 recovery need to be updated since the Nougat release? I hosed my 2015 Pro so can't test it.

If this does work on 2015 model with Nougat then once the current 2015 TWRP sources are updated with Nougat kernel source then one recovery should be needed for all Shields...
[Shield Android TV General] darkuni:
This was the 2015 model (I accidentally typed 2017 when I posted initially).

I'm getting ready to do the 2017 model. I suspect both will work fine.

---------- Post added at 05:27 AM ---------- Previous post was at 05:06 AM ----------

I have been unsuccessful on 2017 unit.

I unlocked the bootloader. I reboot and am given a screen saying it can't check my system for corruption see <some google link>.

I was able to boot to twrp - but every reboot I get that warning message - but TWRP does boot.

Try to SuperSU and it seemed to work, rebooting and the system isn't rooted.

Tried to repeat, SuperSU claims already patched :( Aborts

It looks like it reverses whatever SuperSU is doing.

Before I restore to stock ... anyone got ideas?

Update: After the second failed attempt, the system appeared to take it (warning screen is still there every full boot).

In trying to get my tutorials up to date, I'm not completely sure what "fixed" or allowed SuperSU to work. Is it just a "couple of boots", or did something happen when I tried to flash superSU ... I dunno.

---------- Post added at 06:00 AM ---------- Previous post was at 05:27 AM ----------

Here is the 2017 tutorial.

http://nvidiashieldzone.com/shield-...rial-root-shield-android-tv-2017-16gb-nougat/

I'll have to augment it once I get a chance to do it a few more times and figure out what the deal is.

Now ... time to do the Pro Sku :)
[Shield Android TV General] loki495:
I think the warning is normal. It's just letting you know that the bootloader is unlocked and technically vulnerable as its not protected and can be overwritten.

When I did it, after flashing supersu it booted to nvidia logo, then booted again, this time all the way to android, and supersu was working. Every reboot dos show the warning. Don't think we can get rid of it without locking the boot loader. Check the url it gives.
[Shield Android TV General] AndroidUser00110001:
The warning is normal. I think the kernel (boot.img) can be modified so it doesn't show the warning. Will try a few things out later today to get rid of that message.

---------- Post added at 09:15 AM ---------- Previous post was at 09:08 AM ----------

Wait...I am confused :)

Did the recovery for 2017 Shield work on 2015 Shield too?

If so that can save me lots of time :)
[Shield Android TV General] darkuni:
So sorry - it was a long night :P

Yes, recovery worked on BOTH the original Shield TV (2015) and the NEW Shield TV (2017). As a bonus, it also works on Shield TV Pro. :)

Most impressive.