Shield Android TV rooted

Search This thread

edjanx

Senior Member
Nov 5, 2008
79
16
Scranton
Shield won't recognize Windows 10 PC

Why would resolution make a difference. I no longer have a 1080p tv, I only have a Sony XBR55X850C 4k UHD tv?

According to nvidiasshieldzone (nvidiashieldzone.com/shield-android-tv/android-7-nougat/tutorial-root-shield-android-tv-pro-nougat/), "TWRP doesn’t currently work on 4k displays! Use a 1080p display to complete this tutorial." I simply set the Shield back to 1080p since I have a new LG OLED 4K HDR.

I followed everything from the guide link above exactly, and even purchased the USB 3 cable they tested with, but my new Shield 500G simply doesn't recognize the PC. I tried every port between the Shield and PC, enabled, then disabled, then re-enabled USB debugging, rebooted the Shield and PCs several times. I even setup a different Windows 10 PC without success, and both PCs can detect my Nexus 6p fine with ADB, so any suggestions would be appreciated.

I also had one question on the Shield USB ports. They are supposed to be USB 3.0, but they don't have the usual blue coloring. Anyway to confirm I've actually got USB 3 on my Shield?

Thanks,
Janx
 
Last edited:

darkuni

Senior Member
Sep 12, 2010
378
75
According to nvidiasshieldzone (nvidiashieldzone.com/shield-android-tv/android-7-nougat/tutorial-root-shield-android-tv-pro-nougat/), "TWRP doesn’t currently work on 4k displays! Use a 1080p display to complete this tutorial." I simply set the Shield back to 1080p since I have a new LG OLED 4K HDR.

I followed everything from the guide link above exactly, and even purchased the USB 3 cable they tested with, but my new Shield 500G simply doesn't recognize the PC. I tried every port between the Shield and PC, enabled, then disabled, then re-enabled USB debugging, rebooted the Shield and PCs several times. I even setup a different Windows 10 PC without success, and both PCs can detect my Nexus 6p fine with ADB, so any suggestions would be appreciated.

I also had one question on the Shield USB ports. They are supposed to be USB 3.0, but they don't have the usual blue coloring. Anyway to confirm I've actually got USB 3 on my Shield?

Thanks,
Janx

Hmmm.... There shouldn't be any reference to USB 3 cables for the Pro tutorial.

You use the microUSB port for the Pro unit - old and new.
 
  • Like
Reactions: edjanx

jionny

Senior Member
Aug 23, 2013
538
134
Hmmm.... There shouldn't be any reference to USB 3 cables for the Pro tutorial.

You use the microUSB port for the Pro unit - old and new.
I also have the 2017 500gb model just went through the same problem and finaly rooted, you need to use the micro usb in the controller slot and plug the other end into your pc and navigate with the shield power button while in the bootloader
 
  • Like
Reactions: edjanx

darkuni

Senior Member
Sep 12, 2010
378
75
I changed the wording on the guide to be a bit more clear :)

It is important to note that there is no 2017 version of Shield TV Pro. The Pro model has not changed; only the underlying OS.
 

jionny

Senior Member
Aug 23, 2013
538
134
I changed the wording on the guide to be a bit more clear :)

It is important to note that there is no 2017 version of Shield TV Pro. The Pro model has not changed; only the underlying OS.
Also the controller, at least I would think because I have been told numerous times that the controller works for booting into bootloader however I have never gotten it to work after numerous attempts, so am I wrong to assume its the 2015 controller that works for that and not the 2017 model?
 

darkuni

Senior Member
Sep 12, 2010
378
75
Also the controller, at least I would think because I have been told numerous times that the controller works for booting into bootloader however I have never gotten it to work after numerous attempts, so am I wrong to assume its the 2015 controller that works for that and not the 2017 model?

You would use the old bootloader access method (should be a video with the guide under IF SOMETHING GOES WRONG).

https://www.youtube.com/watch?v=yivWH4363s8

The controller access is only for the 16gb 2017 edition.

I haven't tested the bootloader access with Pro under NOUGAT, but since that is pre-OS level stuff, I believe it should still work.
 

jionny

Senior Member
Aug 23, 2013
538
134
You would use the old bootloader access method (should be a video with the guide under IF SOMETHING GOES WRONG).

https://www.youtube.com/watch?v=yivWH4363s8

The controller access is only for the 16gb 2017 edition.

I haven't tested the bootloader access with Pro under NOUGAT, but since that is pre-OS level stuff, I believe it should still work.

My experience is the controller does not work for getting into the bootloader, either method stated
 
Last edited:

Top Liked Posts

  • There are no posts matching your filters.
  • 27
    I just managed to get TWRP running on the new Shield console, and installed SuperSU successfully. Two caveats: the display is upside down, and the USB host ports don't work. I had to plugin a mouse via an OTG cable in order to interact with it. ETA: That's only an issue when booted to TWRP. Everything's working fine in the stock ROM after rooting.

    Procedure:
    - enable developer tools / USB debugging
    - adb push supersu.zip /sdcard
    - adb reboot bootloader
    - fastboot oem unlock
    - fastboot boot twrp-2.8.6.0-shieldtv-unofficial.img
    - unplug USB cable, connect mouse via USB, install SuperSU

    TWRP boot image is attached. Off to explore...

    EDIT: by request, some more detailed instructions:

    • On the Shield device, head to Settings -> About, and click "Build number" 7 times. This will enable Android's Developer options.
    • Go to Settings -> Developer options, and enable USB debugging.
    • Install the ADB/fastboot drivers and utilities if you don't already have them. When "adb devices" shows your Shield, you're good to go.
    • Download and extract recovery.zip from this thread.
    • Head to the SuperSU forum and download the latest version.
    • Open a command prompt and navigate to the directory where you downloaded everything. (Google this for your OS if you don't know how).
    • With the Shield still booted, run "adb push supersu.zip /sdcard" (change supersu.zip to appropriate file name). This will upload the SuperSU update zip to your device, which you'll install from TWRP.
    • If that worked fine, run "adb reboot bootloader". Your device should shut down, and display the Fastboot screen after a few seconds.
    • FOLLOW THE NEXT THREE INSTRUCTIONS AT YOUR OWN RISK. This WILL wipe all your user data, back it up with ADB first if you want to preserve it. DISCLAIMER #2: I have no idea if there are any DRM keys or anything that get wiped when this is done (this was the case on my Xperia Z3 Compact). I will say that Grid streaming still works fine after doing this.
    • This step will unlock your bootloader to enable booting unsigned images.
    • Run "fastboot devices" and make sure your Shield is visible.
    • Run "fastboot oem unlock" and follow the prompts on the screen. Your bootloader is now unlocked.
    • Now, boot the TWRP image with: "fastboot boot twrp-2.8.6.0-shieldtv-unofficial.img" - Note: I used this instead of "fastboot flash" so I could keep the stock recovery around, to grab an image of it after rooting.
    • You should now see a TWRP recovery menu (upside down for now).
    • Connect a keyboard or mouse via OTG cable, and select "Install", navigate to your SuperSU zip, select it, and follow the prompts.
    • Click "reboot" and you should now be rooted.
    7
    Quick warning for Pro owners: OEM Unlock takes about 92 minutes. Just be warned and ready for it...
    4
    Well, life has finally caught up to me. I need to take a break for a couple weeks. I may work on some small stuff during that time, but I won't be making any big pushes for anything. If somebody else wants to pick up and finish sooner, everything I've done is on Github. The patches against multirom are here (of interest are the ones with aarch64 in the name) and the repo can be used to build cm, twrp, and multirom (only twrp working, of course). The cm-12.1-mrom branch of the foster kernel has the attempt at a kexec patch. Don't know if it works because multirom hasn't worked right yet. Last I tried, the fdt patch didn't compile, so that might need reverted and fixed. CM is like I mentioned last post, no change there. And somehow, the twrp recovery image needs to slim down 3-4 MB. Probably easiest to trim the kernel and split the defconfig for cm and twrp.
    4
    Doh instructions mean touch button on the shield itself lmao - I was thinking it was the controller smh. in the end i just hardware rebooted back into fastboot mode and now im trying to flash zulus custom system img to console. Not sure what step i missed as I followed instructions to a T just seems like after unlocking bootloader it was done for some reason.

    @zulu99 - I dled your system img of 125 mb and when i go to flash it only appears to be writing smaller size 64578 kb / 23221 kb).

    target reported max download size of 67108864 bytes
    erasing 'system'...
    OKAY [ 0.405s]
    sending sparse 'system' (64578 KB)...
    OKAY [ 1.563s]
    writing 'system'...
    OKAY [ 3.630s]
    sending sparse 'system' (23221 KB)...
    OKAY [ 0.583s]
    writing 'system'...
    OKAY [ 0.864s]
    finished. total time: 7.045s

    Also, when i follow your instructions for ./fastboot -w it just hangs there and does nothing (should it take 30+ min?).

    @op - I also tried booting and flashing twrp recovery linked in your first post and was unable to get into recovery using either method.

    I think imma just try and go back to the stock ota since not having much luck does anyone have any ideas how to flash that back via fastboot? Lollipop roms look much different so all Im seeing is a boot.img and this dat file which looks it probably has everything in due to its size but not sure what to do with it.

    The rar file is 245MB and when you extract the system.img the size of system.img is 665MB

    I think you have problem with your pc / usb otg cable, specially if the command fastboot -w, that just clear user data , not work.

    On shield is just little hard to go in bootloader mode:

    HW method:
    Disconnect power cable
    Insert USB OTG cable and make sure to connect other end to a host PC
    Connect power cable to SHIELD
    Quickly start pressing power button for ~3 seconds
    Do not hold the button and connect power supply afterwards
    HDMI TV should be always connected to SHIELD

    The first day was hard to go in fastboot, wont to others devices, but after 2 or 3 times, all is simple and work well.
    I flashed my Shield millions times.


    So. The the important fact is that with full android firmware the device became really useful. Work very well and the hardware is strong.
    Specially you can have all android apps without limitations directly from Google Play.

    For the controller i can use it wired but with the trick above i can use it also from my couch. Tested many things and all work very well.

    But i repeat, this is just the start.

    https://goo.gl/ko3G4m

    I hope to see a specific thread for this device in xda forum so i can help better.
    3
    Not really sure where to put this since there's no Shield TV section but once you root it you can enable hardware mpeg-2 decoding pretty easily

    In an adb shell run the following:
    su -
    mount -oremount,rw /system

    download /system/etc/media_codecs.xml

    Add the following to the <decoders></decoders> section:
    HTML:
            <MediaCodec name="OMX.Nvidia.mpeg2v.decode" type="video/mpeg2">
                <Feature name="adaptive-playback" />
            </MediaCodec>

    Re-upload the file to the device replacing the current one. Reboot the device and mpeg-2 decoding will be enabled. You can also do this for vc1 by adding the following:
    HTML:
            <MediaCodec name="OMX.Nvidia.vc1.decode" type="video/vc1">
                <Feature name="adaptive-playback" />
            </MediaCodec>


    Your first version I used adb shell and just manually installed su from twrp so unsure if it worked as I don't have the proper cable for mouse control :(