yashsingh1/xdaforums huggingface dataset:
[Shield Android TV General] baileyjr:
I update recently, but I didn't accept the OTA.

I downloaded the image and flashed all the partitions via adb except for userdata and recovery. That way I retained all my current apps,data and TWRP. After that it was just a case of re-flashing SuperSU from recovery. There is a discussion on it a few pages back.
[Shield Android TV General] melo_mx:
My Nvidia shield pro seems to hang and still there after "fastboot boot twrp-2.8.6.0-shieldtv-unofficial.img"

It says completed on the command prompt, but the screen remains stuck in fastboot.

I got a new system from the Nvidia pro recall, do you guys think it's patched?
[Shield Android TV General] darkuni:
No, 1.4 no longer allows for temp boot to custom recovery. You'll need to FLASH it ... my tutorial has been updated to reflect this.

http://nvidiashieldzone.com/index.php/shield-android-tv/root-shield-android-tv/

Root Procedure, Step 8.
[Shield Android TV General] NeutralTerritory:
Working With Shield TV Version 2.0

I was able to root my device on 2.0 for any of you who wanted to update but didn't know if it would still work or not. :)
[Shield Android TV General] baileyjr:
I'm just waiting for the full firmware download to appear in the Nvidia download zone. I think the OTA failed for me the last time as it detected root. Were you rooted previously and if so did you unroot before applying the OTA
[Shield Android TV General] aggiemarine07:
mine was rooted and it accepted the update with no major problems (rebooted like 4 times) but now its un-rooted.

To root it again do I need to flash and wipe everything? Or do I simply go back into TWRP and re-flash the SuperSU zip file? (ideally I don't want to lose all my userdata)

EDIT: So i decided to give it a go and see what happens. Bottom line - i didnt lose my user data. heres what happened:

-shield TV accepted the OTA update

-rebooted, now I do NOT have root permissions like before

-all previous settings (i.e. developer mode, oem unlock, etc) were still good. supersu.zip was still on device

-ran "adb reboot bootloader"

-ran "fastboot devices" to confirm

-ran "fastboot flash recovery twrp.zip"

-hit power button once and selected "reboot recovery to kernel"

-rebooted into TWRP, selected install supersu.zip

-bingo, rooted again (confirmed with my sixaxis app to make my PS4 controller work with the shield tv!)
[Shield Android TV General] JohnHenryIron:
Not positive, but since it's not a custom firmware I believe you can just follow darkuni's guide he made without doing a full wipe
[Shield Android TV General] Steel01:
If you've unlocked your bootloader once, you never have to again regardless of updates. So yes, you can reflash twrp and reroot without having to wipe user data a second time.

After updating to 2.0, it seems we still can't fastboot boot anything. I also can't seem to get the hardware method of bringing up fastboot to work. I'm going to try flashing back to the 1.3 bootloader and see if the 2.0 system still boots and works. I don't expect to see any problems with that. But I can't safely do dev work if I can't get to recovery when I break the boot image...
[Shield Android TV General] duanim:
i got the pro version, try to root the 2.0 no nothing, flash twrp again no supersu zip in sd card try pushing and sideload no nothing. i was rooted in 1.4 and did the OTA 2.0, i did a backup in 1.4 thank god. some sugestion,or wait for the full ota to download
[Shield Android TV General] baileyjr:
I accepted up update but it failed because it was expecting the stock recovery and I had flashed TWRP. After flashing back the stock 1.4 recovery I was able to accept the update without and issues. Then I reflashed TWRP and installed the SuserSu.zip to get root back
[Shield Android TV General] Steel01:
I rooted using twrp and supersu. I flashed twrp and immediately booted into it using the fastboot menu on device. Sideloaded Beta 2.49 and rebooted. Adb'ed in and su worked.

And people, people, *please* stop saying twrp breaks otas. IT DOES NOT. TWRP will flash ANY ota correctly, incremental or full. It's rooting that prevents *only* the incremental otas. I selected the option in the update utility to grab the full ota and my rooted console with twrp updated *just fine*.

On my other note, flashing the blob from 1.3 did restore proper fastboot functionality (fastboot boot, etc). I haven't full tested the 2.0 system with the 1.3 bootloader, but it did boot correctly before I went back to work on CM. Anyone interested in this can run the following on an extracted 1.3 recovery archive:

fastboot flash staging blob

Then reboot the system. Mine went black on the first boot, presumably because the blob update didn't reset the system correctly, but it booted fine after that.
[Shield Android TV General] BenjiHansell:
I can confirm that I updated from 1.4 to 2.0 on a rooted shield with TWRP flashed as an OTA with no problems at all. Thank you for porting TWRP :)
[Shield Android TV General] mta1981:
from a total noob stand point, is there a problem rooting the pro version? A couple guys saying it locks up? Im on 2.0. I want to root cuz I was bummed to find out that you dont have the full google play store on android tv. Does side loading apks work or should I just go for the full android rom thats available?
[Shield Android TV General] duanim:
if you follow and look how to do it you will root the console,i got the pro version its just time one hour to unlock the bootloader and maybe 15 minutes to install the twrp and supersu. the console is no the problem the problem is how to do it in windows.in youtube and right here in XDA developers you find the info.to update the 2.0 from twrp recovery after you are rooted,download the the update,look for the zip file in es explorer check root explorer and look ,dont remember now,google is you best freind.

for full play store is for mobil device no for tv platform,yes you can sideload,if you want play store and not sideload,install the full android rom
[Shield Android TV General] NisseDILLIGAF:
ok.. I've read this thread up and down and I'm sorry if I missed it...

I'm about to flash twrp and root my NSTV... Can I flash when in v2.0 or do I have to downgrade to 1.4?

I hope someone answers soon, because I came all the way to booting fastboot and then started question myself.. so now I'm watching fastboot on my TV... hehe ;)

Thanx!

EDIT: my wife and daughter just came home... I'll have to do this another time :)
[Shield Android TV General] lartomar2002:
This says it works with OTA 2.0 http://nvidiashieldzone.com/index.php/shield-android-tv/root-shield-android-tv/
[Shield Android TV General] visitor29:
Root works on 2.0 ota. I did it on shield pro 500gb and can confirm 100%. Procedure is same as you doing like on 1.4 and you no need downgrade. Just follow slowly without rush

http://nvidiashieldzone.com/index.php/shield-android-tv/root-shield-android-tv/
[Shield Android TV General] mow4cash:
I'm having an issue getting the bootloader to display on the TV, I've tried two different samsungs. It's in fastboot but the Tv won't display. I've been able to get a flicker and one time it actually worked for a little bit. I have flashed TWRP and was able to access it, then I realized I deleted the system, reflashed 2.0, then flashed TWRP again. ADB into recovery but it's the stock android guy. Every time I try to flash TWRP it works from command but I can't access the TV screen to view it. I'm afraid to unlock the device again and reflash for fear the TV won't display it and I'll get hung somwhere. The first time I unlocked it by guessing the taps. I guess that's why the system was deleted. Why can't the TV display the bootloader correctly?
[Shield Android TV General] wakkaday:
how you guys findign rooting it? is it worth it
[Shield Android TV General] turtledope:
thx

Got mine rooted today :)
[Shield Android TV General] wakkaday:
Do you still have access to nvidia shield hub ?
[Shield Android TV General] KING SKILLZ:
Thanks OP, just got this and i am up and rooted!
[Shield Android TV General] gregdeberg:
Hello :)

Root on the 2.0 version but now a 2.1 is OTA ready but when my shield reboot , i go directly in the TWRP recovery (normal i supposed) but how to do this update please ?

Thanks
[Shield Android TV General] Nekromantik:
Only way at the moment is to re flash 2.0 then flash OTA.

Then re root.
[Shield Android TV General] Steel01:
Does the ota utility not offer a full ota? If the full ota is there, twrp should work with it out of the box. Then just re-root. I haven't tried yet, but will in a couple hours.
[Shield Android TV General] duanim:
i took the ota copy to sd card/download,go to twrp install and failed,set differents way no luck,set permision selinux,md,zip verification,nothing,reboot,black screen and like slow,when back to twrp with pc connection and restore thanks god for backup in twrp.,so waiting .....

---------- Post added at 11:15 PM ---------- Previous post was at 11:13 PM ----------

[QU

no please to much work and time
[Shield Android TV General] tillaz:
We need stock recovery to flash from fastboot then should work can someone upload it ?

EDIT:

Just flashed stock recovery and the update looked to install but then said error...
[Shield Android TV General] melo_mx:
I just downloaded the developers edition of 2.0 yesterday... did a full wipe and root. Next day, 2.1? FML

Definitely skipping 2.1
[Shield Android TV General] kyrusdemnati:
is the a video guide to root?

i have a mac..???
[Shield Android TV General] baileyjr:
I saw you refer to that option in a previous post, but I can not for the life of me see that option anywhere?
[Shield Android TV General] Steel01:
Oops, I forgot to post back to this last night. Yeah, doesn't look like 2.0 has the full ota option in it anymore. I don't know if it's completely gone or it just isn't showing for the 2.1 update. So yeah, looks like people will need to flash system and recovery from the 2.0 recovery image to use the 2.1 incremental update.

If someome has a link to the full ota, please post it. That can be used by twrp to update a rooted system.

I noticed today that nvidias ota's check the build fingerprint of the recovery. Makes flashing an incremental much more painful since system isn't the only thing that has to be in sync.
[Shield Android TV General] patt2k:
Now that's pretty crazy nvidia being supportive from day one :)

I might buy it in few months.. we'll see what happens :)
[Shield Android TV General] sonicadvance1:
You'd have to hold my hand on this one. I'm an software developer, not an OS developer.

Every time I try dealing with Android I tend to get frustrated instead of accomplishing anything.

Here's the mounted partitions

rootfs / rootfs ro,seclabel 0 0
tmpfs /dev tmpfs rw,seclabel,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,seclabel,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,seclabel,relatime 0 0
selinuxfs /sys/fs/selinux selinuxfs rw,relatime 0 0
debugfs /sys/kernel/debug debugfs rw,relatime,mode=755 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
none /sys/fs/cgroup tmpfs rw,seclabel,relatime,mode=750,gid=1000 0 0
tmpfs /mnt/asec tmpfs rw,seclabel,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,seclabel,relatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
pstore /sys/fs/pstore pstore rw,relatime 0 0
tmpfs /mnt/tmp tmpfs rw,seclabel,relatime,mode=775,gid=1003 0 0
/dev/block/platform/tegra-sata.0/by-name/APP /system ext4 ro,seclabel,noatime,data=ordered 0 0
/dev/block/platform/tegra-sata.0/by-name/CAC /cache ext4 rw,seclabel,nosuid,nodev,noatime,nodelalloc,data=ordered 0 0
/dev/block/platform/tegra-sata.0/by-name/UDA /data ext4 rw,seclabel,nosuid,nodev,noatime,discard,data=ordered 0 0
adb /dev/usb-ffs/adb functionfs rw,relatime 0 0
/dev/block/platform/tegra-sata.0/by-name/FCT /mnt/factory ext4 ro,context=u:object_r:factory_file:s0,relatime,data=ordered 0 0
/dev/fuse /mnt/shell/emulated fuse rw,nosuid,nodev,noexec,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0

Here's the available partitions

major minor #blocks name

253 0 524288 zram0
8 0 488386584 sda
8 1 3072 sda1
8 2 256 sda2
8 3 256 sda3
8 4 2048 sda4
8 5 256 sda5
8 6 256 sda6
8 7 2048 sda7
8 8 2048 sda8
8 9 2048 sda9
8 10 6144 sda10
8 11 2048 sda11
8 12 4096 sda12
8 13 4096 sda13
8 14 6144 sda14
8 15 79 sda15
259 0 2048 sda16
259 1 2048 sda17
259 2 131072 sda18
259 3 26112 sda19
259 4 4096 sda20
259 5 26112 sda21
259 6 2097152 sda22
259 7 262144 sda23
259 8 786432 sda24
259 9 2048 sda25
259 10 32768 sda26
259 11 2048 sda27
259 12 8192 sda28
259 13 8192 sda29
259 14 16384 sda30
259 15 8192 sda31
259 16 484936632 sda32
179 0 15388672 mmcblk0
[Shield Android TV General] Steel01:
Yes, the fstabs for the emmc and sata editions are different. I'm trying to make one code base to support both. For the ROMs, this looks to be trivially simple. For recoveries, I haven't found documentation to confirm whether what I'm doing will work or not (duplicating fstab entries, letting the mount error handlers ignore the invalid ones). So, the build below should work, but it might blow up too. I can't test yet, so beware of dragons. As long as you don't try to write anything (flashing, backups, etc) until you verify the correct partitions are mounted, it should be safe.

https://www.androidfilehost.com/?fid=23991606952613713
[Shield Android TV General] sonicadvance1:
How sad, the mouse doesn't come up on that one, so I can't navigate the interface.
[Shield Android TV General] Steel01:
No mouse at all? That's odd. The build options are nigh identical to the tablets. I'll take another look next time I'm poking at it. Can you adb to the device when it's booted to this twrp? I'm curious to know if the mouse is being detected at all (/sys and /dev entries). If you can, try otg and the real ports (well, real ports when adbing and kmsg for a previous otg attempt). Maybe one of these days my dev work will be enough to earn a prerelease model to work on so I don't have to do work almost blind for 2 weeks.
[Shield Android TV General] AndroidTVTech1:
I just want to say thanks for your SHIELD Android TV rooting method, it worked like a charm for me. My new SHIELD Android TV devices seems to be working a lot smoother now after rooting!
[Shield Android TV General] sonicadvance1:
Last bit in kmsg when I plug in my mouse to the USB OTG port.

Plugging in to the USB host ports yields nothing being output in kmsg

<4>[ 100.063736] tegra-i2c tegra21-i2c.3: no acknowledge from address 0x3a
<6>[ 100.614156] nvhdcp: link verified!
<6>[ 101.763696] extcon-gpio-states 1.extcon: Cable state 2
<6>[ 101.823488] otg state changed: SUSPEND --> HOST
<6>[ 101.828067] No Device Node present for smmu client: tegra-ehci.0 !!
<5>[ 101.834399] platform tegra-ehci.0: No DT found, got swgids from fixup(101004000)
<6>[ 101.842015] tegra USB phy - inst[0] platform info:
<6>[ 101.846827] port_otg: yes
<6>[ 101.849446] has_hostpc: yes
<6>[ 101.852239] phy_interface: USB_PHY_INTF_UTMI
<6>[ 101.856517] op_mode: TEGRA_USB_OPMODE_HOST
<6>[ 101.860608] qc2_voltage: 0
<6>[ 101.863314] hot_plug: disabled
<6>[ 101.866375] remote_wakeup: enabled
<3>[ 101.869787] usb_phy: inst:[0] couldn't get regulator avdd_usb: -517
<3>[ 101.876177] usb_phy: Couldn't get regulator avdd_pll_utmip: -517
<3>[ 101.882176] usb_phy: inst:[0] Failed to init clocks
<3>[ 101.887064] tegra-ehci tegra-ehci.0: failed to open USB phy
<6>[ 115.663697] extcon-gpio-states 1.extcon: Cable state 0
<6>[ 115.723488] otg state changed: HOST --> SUSPEND
<6>[ 118.883695] extcon-gpio-states 1.extcon: Cable state 1
<6>[ 118.943487] otg state changed: SUSPEND --> PERIPHERAL
<6>[ 119.342851] tegra-udc tegra-udc.0: notification status (0,1,0) (0x0, 0x2)
<6>[ 119.504797] android_work: did not send uevent (0 0 (null))
<6>[ 119.631353] android_work: sent uevent USB_STATE=CONNECTED
<6>[ 119.639371] android_usb gadget: high-speed config #1: android
<6>[ 119.645202] tegra-udc tegra-udc.0: connected to SDP
<6>[ 119.650109] tegra-udc tegra-udc.0: notification status (0,1,0) (0x2, 0x2)
<6>[ 119.657014] android_work: sent uevent USB_STATE=CONFIGURED
[Shield Android TV General] Steel01:
Wha....?? Well yeah, if the device tree node is missing, it's probably not going to work. Question is, why is it missing? I'll have to do some research and see if there's any difference between the emmc and sata dtb versions. But wait, adb works on the very same plug? Now my head hurts...

There's absolutely no kmsg response when using the usb host ports? That also surprises me. I'd expect the kernel to handle that independent of the os. But I guess not. I'll try to google some devices with host ports and see if they did anything special to get them working in TWRP.

Oh, I should have asked the first time... But, can you run mount and see if the sata partitions mounted? If those didn't work, I might have to split the builds apart anyways.
[Shield Android TV General] sonicadvance1:
They definitely weren't mounted.

I was able to mount them manually by myself(sda22 being the system partition)

Any way you want to lower the latency on these message and responses?

IRC or something?
[Shield Android TV General] Steel01:
Meh, okay. I'll have to see if there's some other way to dynamically alter the fstab. Maybe the vendor init function runs before mounts... I think it does, I might be able to just rewrite the thing on the fly. Probably cleaner that way too, if a bit confusing to someone not knowing what to look for.

And no, not tonight, sorry. It's way late for me. And I won't likely have a long enough single free block of time to work on this until Thursday night. If this hasn't been resolved by then, maybe we can work something out.
[Shield Android TV General] Steel01:
Well, I'm not finding much about host USB ports and twrp via Google. What little I found seems to indicate they just work. I wonder if it might have to do with USB 2.0 vs. USB 3.0 differences, but I'll have to get mine and dig into a booted system.

So, my first posted recovery was built out of a modified omni tree. I use omni for my other twrp builds as recommended by upstream. But omni doesn't support 64-bit, so I had to hack a few things around to make it compile. CM has better 64-bit support, so the build below is out of that. There are no device tree changes, so I don't expect partitions to automount, but some magic might make the mouse work.

https://www.androidfilehost.com/?fid=23991606952614113

[MENTION=3380605]sonicadvance1[/MENTION]:

Ya know, if all else fails, you can extract the supersu script and run the important commands in updater-script manually. I haven't looked, but I wouldn't expect it to be much more than copying su and tweaking a couple selinux files.

Edit:

Oh, for anyone booted to any of the builds with adb access: I need to content of /proc/cmdline. And I need it for both models. I should be able to use that to differentiate the models.
[Shield Android TV General] patt2k:
Don't wanna go off-topic on you but is it possible for recovery on Razer Forge? XDA needs to add Android TV suport asap..

is bootloader needed unlocked needed for it? let's say if Razer supplied tools to unlock bootloader. Thanks and sorry for going little off-topic!
[Shield Android TV General] sonicadvance1:
I managed to root it using the regular version of the recovery and mounting all the directories manually.

Then just doing a regular install through the twrp interface.

I can give you an output of /proc/cmdline of the pro model later today.
[Shield Android TV General] Steel01:
Bootloader needs unlocked at a minimum. I don't have or want a Forge, so I don't know anything beyond that. Someone would have to build a kernel and device tree based on whatever code Razer released (if any).

[MENTION=3380605]sonicadvance1[/MENTION]: Yeah, that'd work too. Hopefully I'll have twrp working better by the time I get mine so I don't have to do something like that.
[Shield Android TV General] Luxferro:
It's an Android TV device. It has all that built in.
[Shield Android TV General] Batfink33:
It had the Android TV Google Play store apps which are very limited but you can sideload normal apps.
[Shield Android TV General] BenjiHansell:
anyone who hasn't already, please put a request in here:

http://xdaforums.com/showthread.php?t=1660354

this device needs it's own XDA forum, the Nexus Player and Fire TV have them

something I would ask if a forum existed:

does anyone know the actual max clock speed of the A53 and A57 CPU cores in the Tegra X1? I know that the GPU is clocked at 1.0 GHz but neither Nvidia's own X1 page nor Wikipedia's Tegra page quote any CPU clock speeds, I've been looking for months
[Shield Android TV General] darkuni:
Hey, in support of the device I'm working on a modest FAQ on my modest website for the Shield console.

http://greenrobotgamer.com/shieldzone/2015/05/28/nvidia-shield-you-have-questions-we-have-answers/

If you guys have any ideas of stuff that should be there to help promote/support/encourage NVidia Shield Android TV, let me know.

Looking forward to getting my root on when I have time to sit down and do it.
[Shield Android TV General] STVInterested:
Install Linux?

Hello everyone who rooted de ShieldTV,

In Europe we have to wait ... but the STV is very interesting....

Could someone try to install and run the android app "linux Deploy" and install one linux in a USB3 disk.

I would like to install a "running in background" ubuntu in the shieldtv to manage my private cloud (LAMP + ftp server + smtp+imap.... and dlna server... etc etc).

Compared with my actual server one little core of the X1 will be enought to run everything very good (I test it with mediatek dual core and works fine)

Thanks and excuse my bad english
[Shield Android TV General] visitor29:
Same happened with me yesterday only one solution i see here - i did reinstall 2.0 through fastboot, installed on first boot 2.1 and then after factory reset through setting (1st option fast factory reset). P.s. Why i did factory reset after 2.1 - coz every time after manual fastboot restoring system see only 11gb instead of 500gb(i don't know why this happening bug or something like that...) , but factory resets through gui its goes back to normal
[Shield Android TV General] Segitz:
I did it the way described in nvidiashieldzone... I.e. download the full 2.0 update, edit the bat and comment the userdata line. Flash it and reboot. All data still present. Needs to be rerooted, but the same twrp still works.
[Shield Android TV General] kyrusdemnati:
can you root the latest version of nvidia i think its 2.1 firmware

please advise?
[Shield Android TV General] duanim:
steel001

i konw that twrp multirom is not working,but my question how i can install 2 roms the full android and the stock ,the way that do i think is downgrade to 1.3 to flash the full or i can copy firts the stock one or you tell me,the whole rom in my PC. after root the devive and flash twrp,do a backup for stock or full,how i can install the copy one from the pc to twrp backup,like to have to differents rom for restore,like multirom.

i will appreciated thanks

---------- Post added at 09:51 PM ---------- Previous post was at 09:40 PM ----------

just thinking i dont think that works in this way.

wishing for multirom in the feature
[Shield Android TV General] kyrusdemnati:
in this root

does everything work i.e. controller all the settings bluetooth and so on

any reason not to root?
[Shield Android TV General] baileyjr:
Everything works :D :good:
[Shield Android TV General] kyrusdemnati:
i was trying to root via a mac, struggling a bit via the command prompt / terminal thing

i have put all the files on desktop

in terms of the supersu.zip file can i not just copy that into the root internal sd, as i can see that folder when i connect via the mini usb to my macbook..
[Shield Android TV General] sandog12:
Is there any reason to use the developers img since u still need to root?
[Shield Android TV General] duanim:
Wandering too,what's the different
[Shield Android TV General] baileyjr:
The full image is now available on the Nvidia Download page https://developer.nvidia.com/gameworksdownload