yashsingh1/xdaforums huggingface dataset:
[Shield Android TV General] Steel01:
Well, CM is still eluding me (stupid tsec stuff again, the bane of my ports...), but I think TWRP is pretty solid now. Ran a couple backups and restored countless times today while fighting with CM, never had a problem. I came up with a better way to differentiate the models (the property ro.hardware) and that seems to work okay. I need some 16 GB testers to verify that, though. Still haven't gotten around to shrinking the image to fit on the partition, though.

twrp-multirom-20150613-UNOFFICIAL-foster.img

Note to devs and a question:

I ran into a problem with the unified build thing today. CM (and likely other roms) hardcodes the partition locations into the update-script. I'm currently working around that by feeding TARGET_RECOVERY_FSTAB a mostly bogus fstab and creating those as symlinks in recovery. On recovery and rom boot, it detects the model and uses the correct fstab, however. Does anyone have a better idea than that? Cause I really don't want to maintain two separate builds for a one file (the fstab) difference...
[Shield Android TV General] zulu99:
fastboot flash recovery twrp-multirom-20150613-UNOFFICIAL-foster.img

target reported max download size of 67108864 bytes

sending 'recovery' (28356 KB)...

OKAY [ 0.923s]

writing 'recovery'...

FAILED (remote: Partition write failed!)

finished. total time: 0.941s

just with this recovery, the one in the first post not produce that
[Shield Android TV General] zulu99:
Just for Info, i updated the Full Android firmware for Shield TV. The last version is 1.2

I will open a specific thread for this firmware in xda when also Shield TV will have a good forum section like all others Android devices.

For the moment you can download the firmware and follow my works from Google Plus:

https://plus.google.com/+VideomapIt/posts/Yi3y76D8RWP
[Shield Android TV General] AndroidTVTech1:
Internal SD Card
[Shield Android TV General] mtbowl:
This is killing me trying to do with one monitor between my shield and my pc. Failed at oem unlock. Didn't get to the prompt fast enough
[Shield Android TV General] Steel01:
Ummmm... Yeah. I said it would do that. Twice, in fact. It's too big. The recovery partition is 25.5 MB and the multirom twrp is currently 28 MB. I've got to poke at the kernel defconfig and see what I can rip out for the recovery to make the kernel smaller than 19 MB. Not as easy here compared to arm since arm64 doesn't do kernel decompression and it doesn't appear that fosters bootloader handles it either. Anyways, fastboot boot works just fine for now. And this one should work much better than the one in the OP.
[Shield Android TV General] mtbowl:
Is there a way to script this out? So I start it on my pc and I could watch my shield for prompts?
[Shield Android TV General] zulu99:
Thanks. Multirom is a must have on this device. with usb3 we can start android custom firmwares and linux distros like a charm.

I leave you on this valuable work, then we have many things to discuss about the firmware. I saw that you play well with the private stuff of Nvidia.

I lost more than 4 days 24/24 to create my firmware.

Nvidia publish a very negative public source code. You need many private blob that are only on the stock firmware also only to start.

The stock android source code is full of Nvidia modifications not public and many parts not even follow the google guidelines for Android.

Specially in the input subsystem. Like the shield portable and tablet.

I don't understand how Google can call a device modified so hard: "Certified Device"

For sure the Nvidia modifications break compatibility with many of this guidelines:

https://source.android.com/devices/input/overview.html

For Users that not know:

A device that is not Android standard can create problem to developers with apps in google play because the OS below work in another way from what is expected.
[Shield Android TV General] aznmode:
I just got the Pro version and have enabled usb debugging but when I type "adb devices" in command prompt my device shows up offline so i can't run any other adb commands. Any ideas?
[Shield Android TV General] mtbowl:
Is there a command that will tell me if I succeeded in unlocking bootloader? I did it and it deleted everything including the twrp.img and the su.zip.
[Shield Android TV General] Steel01:
[MENTION=6046289]mtbowl[/MENTION]: That really sounds like it succeeded. Now you just need to fastboot boot the recovery image and sideload the supersu zip to root it.

Well, not much progress today. I think I'm closer, but it's still not booting. Had a couple headdesk moments when I found some problems with my device tree though... TSecCheckPermissions is still failing which causes hwcompser to fail. I *think* that has to do with TLK not coming up correctly. I'm having to rerun another clean build before I can continue testing, though. Which means it'll be sometime tomorrow.

Is the input system really that non-standard? Plug the controller in wired and it acts just like any other hid controller. The only non-standard thing is the wifi-direct wireless pairing. I've got that half working on the tablet and portable and expect it to work a bit better on CM here (once I get it booting...). And as far as I can tell, the remote is a standard bluetooth device all the way. Though, I don't have one, so that's second hand knowledge.

Does Nvidia's aosp even boot? I haven't tried yet, but from fighting with CM, I'm really wondering how broke that code drop is... The init files are significantly different at least.
[Shield Android TV General] zulu99:
Input subsystem of Android not mean just controller, mean all input devices that you can connect to Android. All is documented by Google in this pages. https://source.android.com/devices/input/overview.html

If you want an example, two fingers on my app DroidMote simulate an hardware multi touch trackpad with real two fingers. It works on all firmware and devices also on Nexus Player. Because it emulate a real hardware and Android handle it. Just on stock firmware of Shield devices it produce a restart of the device because this part was modified from standard Android. ( solved in my app removing the multi touch spots when you do mt gestures) This is a basic part, not a part that a manufacturer can change without breack compatibility.

Fortunately in my full Android firmware for Shield Android TV box it work like on all others original Android devices

https://youtu.be/hDG9X_Q_E60

P.S.

Tested xposed framework on my firmware and it work very well. I tested force immersive mode module that is very useful in this firmware when you want same leanback apps in full screen like in Android TV.
[Shield Android TV General] bunny0007:
Got this error when i trying to boot recovery or flash recovery

downloading 'boot.img'...

FAILED (data transfer failure (Unknown error))

finished. total time: 6.314s

Got it fixed, seems to be a driver issue with the fastboot driver on my windows 8 computer, it works fine with my second windows 7 laptop.
[Shield Android TV General] tyvar1:
http://xdaforums.com/t/shield-tv
[Shield Android TV General] Mechcondrid:
if it's a point you were trying to make sir, you have failed......
[Shield Android TV General] tyvar1:
Wopsie totally forgot to write the text. I was going to tell him that I recommend him to post this also in the new Nvidia Shield TV devices forum. :)
[Shield Android TV General] Steel01:
Except that that's not really a forum... Maybe eventually.

So, still stuck on CM (or any aosp based rom, likely). Getting the following snippets.

D/libEGL ( 499): loaded /vendor/lib64/egl/libEGL_tegra.so
D/libEGL ( 499): loaded /vendor/lib64/egl/libGLESv1_CM_tegra.so
D/libEGL ( 499): loaded /vendor/lib64/egl/libGLESv2_tegra.so
D/NVSI ( 499): ### NVSI v2 TEST DEBUG OUTPUT ###
D/NVSI ( 499): TegraVersion is t210
D/NVSI ( 499): Read AID: `0x1ed0449f'
D/NVSI ( 499): ### VALID CONFIGURATION ###
W/libEGL ( 499): eglInitialize(0x1) failed (EGL_NOT_INITIALIZED)

E/phs:fs ( 252): Unable to open file "/mnt/tmp/fc0": No such file or directory
E/phs:fs ( 252): Unable to open file "/mnt/tmp/fc0": No such file or directory
W/phs:machine( 252): Could not open "/mnt/tmp/fc0": No such file or directory. Trying later.
E/phs:fs ( 252): Unable to open file "/mnt/tmp/fc1": No such file or directory
E/phs:fs ( 252): Unable to open file "/mnt/tmp/fc1": No such file or directory
W/phs:machine( 252): Could not open "/mnt/tmp/fc1": No such file or directory. Trying later.

I'm pretty sure my last real problem is figuring out what creates those files. On stock, they're owned by graphics. Or it could be the other way around. Figure out why EGL isn't initializing and the hwcomposer module creates them. Either way, I'm still stuck...

Edit:

Okay, this is going no where fast. Think I'm going to switch back over to working on TWRP and Multirom for a while. If anyone with CM or AOSP experience is interested, my code is available on CM-Shield.

For TWRP, all I really need to do is shrink the kernel enough to fit. Should be easy enough to rip out all networking, sound, etc. I tried that earlier, going through the defconfig like a deranged loony with a machete. Only it didn't boot afterwards... I'll have to try that more measuredly later. Multirom for some reason is skipping the boot screen. I double checked everything and it all installed correctly. So, I get to do some printf style debugging next go around.
[Shield Android TV General] Steel01:
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.
[Shield Android TV General] JohnHenryIron:
[MENTION=1416222]Steel01[/MENTION] you've been kicking ass. Enjoy that break
[Shield Android TV General] ericvh:
Check to make sure you told the pop-up that it was okay to debug from that computer. Until you verify the host the debug won't work.
[Shield Android TV General] ooBONGoo:
anyone tried flashing the new OTA over their rooted pro model? I'm wondering if a dirty flash will work. I'm assuming that the same can be done with the shield tv as with the shield tablet.. but i'm not sure if there is a full OTA available to download and test it out. This is based on needing the full OTA to update a rooted shield tablet.

*update* downloaded the ota and tried flashing that they twrp. Kept getting a failed with an "error executing updater binary zip". ��

Edit again* by golly I think it did flash! I got 1.2!!! And still rooted..
[Shield Android TV General] bunny0007:
And mabye check windows device manager if adb drivers are installed.
[Shield Android TV General] sonicadvance1:
I updated using the regular update path inside of Android. It worked, and all it did was eat my root install.
[Shield Android TV General] ooBONGoo:
What I actually did was fast booted into twrp and installed the downloaded ota zip. Flashed that.. Reflashed supersu, and voila! Still rooted.
[Shield Android TV General] aznmode:
Didn't figure this out till I hooked up the tablet into my win XP PC. Thank you. After that I was able to run adb commands correctly and unlock the device, but now when I fastboot the twrp recovery and go to TWRP, I cannot see my supersu.zip that I pushed to the /scard folder. If I reboot the tablet normally and use ES File explorer I see the file in my /sdcard folder. I've also tried copy the supersu.zip to my micro sd card and in TWRP I cannot access the files in my micro sd.

Update: see my post below this
[Shield Android TV General] aznmode:
Thanks. This is the TWRP that worked on my Pro version. I was able to finally read my /sdcard/ content and flash supersu. Also this twrp version is not upside down and mouse works using one of the usb ports instead of having to use an OTG adapter. I'm now rooted! Could you add to the OP?
[Shield Android TV General] alwaysbless:
My root was gone after the 1.2 update. I havent even been able to get the thing to boot as a matter a fact. Intially after updating it went into the launcher fine but when I tried to boot recovery again to flash supersu back it went in stopped booting. Once it stopped booting i connected it to a windows pc and re-ran the all of recovery stuff off the nvidia site and it writes successfully but still doesnt boot. Pretty much soft bricked mine so be careful guys.
[Shield Android TV General] ooBONGoo:
Sorry to hear that. Usually best to reflash supersu right after you flash the ota update. These were the steps i took to dirty flashing my pro:

1. Downloaded 1.2 OTA but don't install.

2. Moved 1.2 OTA from data/data/com.nvidia.ota/files/ROM folder to /sdcard

3. Put latest SuperSU zip file on /sdcard.

4. Connect shield TV to computer and adb reboot bootloader.

6. On bootloader screen fastboot boot twrp.img (Steel01's foster version)

5. In TWRP mount system in mount tab (if you don't, when flashing the OTA you'll keep getting a error mounting /system)

6. Flash install OTA (will say failed after flash and will also say error executing updater binary.. Just ignore)

7. Flash supersu.

8. Reboot (will ask about flashing SuperSU again.. Say YES)

9. Money.

Now I don't know if this will work for others but it did work for me. When I first dirty flashed, all the failed errors I kept getting in TWRP made me think I was unsuccessful, but checking the "about" in system after reboot showed I was now on 1.2. Checked update and system said i was up to date. After that verified my root apps (TB, LP, RE, etc..) and I still had root. Updated busybox and been rolling since. I had a feeling updating the shield tv OTA should be similar to updating my rooted shield tablet.
[Shield Android TV General] arnold88:
Twrp working on 16GB version

Thanks for your work - I am able to boot to recovery and flash supersu, which was broken by Nvidia OTA v1.2 (apparently, we will be able to use OTA with root, but will lose root each time.) At least everything is right side up and USB's are working.
[Shield Android TV General] ooBONGoo:
You won't lose root of you flash supersu right after you flash the Ota. Basically do it all before you reboot back the system.
[Shield Android TV General] bunny0007:
Have you tried to flash the factory image from nvidia from fastboot?

I did that on mine and all worked, after that i let it update to 1.2 and booted twrp and rooted.
[Shield Android TV General] jerflash:
I have to ask... What are you guys doing with root on this device? I don't really see much reason for it at all. I would only consider it for apps to sd which already works. I am rooting and playing with my nexus player on that you really have to
[Shield Android TV General] meber:
You can't use ES File Explorer or any file explorer for that matter to write to the SD card without root.
[Shield Android TV General] jerflash:
You know what you are right sir and that is a big one.
[Shield Android TV General] lartomar2002:
I believe that was true only with KitKat because Google forgot and messed up but now since Lollipop that issue has been corrected. if you could not write to /ex sdcard then how could you put games on the ex sdcard. If I am wrong please forgive my ignorance, maybe I am misunderstanding something.
[Shield Android TV General] JohnHenryIron:
You are wrong. It's not that google messed up. That was their full intention. It's a means of protecting your files. Unfortunately for must of us, it's just a hassle. From what I understand there is a simple command switch that if a manufacturer chooses they can allow access to external memory. They loosened the restrictions a bit for lollipop, but the app creator had to implement it. Not exactly sure how it changes in lollipop.

---------- Post added at 06:15 PM ---------- Previous post was at 06:12 PM ----------

Oh, and root is needed for and sixaxis controller and adaway! No commercials on you tube, and ps3 controllers on shield. And xposed if it works well with Android TV
[Shield Android TV General] lartomar2002:
Thanks for enlightening me. If we can move or install games to exsdcard then doesn't it mean the same as writing to exsdcard?
[Shield Android TV General] aznmode:
I rooted so I can run droidmote server (requires root) on the shield to control the device using my phone as a mouse+kb which runs the droidmote client on. If you didn't already know, the last 2 updates disabled the mouse function on the game contoller. Plus the mouse function on that is not the best IMO. I could buy a bluetooth kb with mouse pad but that's more $ to spend and another device I have to worry about charging.
[Shield Android TV General] jerflash:
I have a mouse Logitech dongle plugged in via OTG so I can keep both USB ports open. Also I can confirm USB hubs do work
[Shield Android TV General] JohnHenryIron:
System apps have full access.

It's a shame the touchpad on the remote doesn't work. I can't understand why they would disable it..... Which someone is sure to find a way to turn it back on using root ; p

I'm gunna check out droid-mote.

Ps - adaway also removes adds from pandora & iheartradio!
[Shield Android TV General] zulu99:
Just for information:

Mouse and keyboard are not sufficient for many apps and multi-touch-only games. Very often you need real multi-touch gestures ( two fingers swipe rotate zoom scroll) or the touchmouse to click on some game menu that are not supported by mouse action. Also you need the touch profiles that are very useful to play with touch-only games.

So DroidMote is not just mouse and keyboard but many others things that help you to interact well with a device without touch screen.

( if you want use all apps that Google Play offers )

The best solution in Google Play from 4 years,

also Nvidia used many base concepts of DroidMote and it closes these concepts within its controller. This is a fact, because all Shield devices are recent, DroidMote is sold in Google Play from many time before and is compatible with all Android devices, so you don't need a customized firmware of the manufacturer with proprietary things inside. You are free to use which firmware you want.

An hardware mouse and keyboard is more useful on a desk not on a couch.

This is not an advertisement but just what i think.

http://www.videomap.it/dmcguide.htm

p.s.

I updated the full Android Firmware to 1.3 version. Based on last stock 1.2 update.

Now we have all, also hevc h265 4K hw decode.

But i found a more beautiful thing. You can install xposed framework and with it unleash the full potential of your device.

infact with some xposed modules you can set some Android TV specific apps with a specific dpi value ( 320 for Android tv ) and full screen. So in full Android you can have also the Android TV ecosystem like in the stock firmware + all others millions apps from Google Play.

https://plus.google.com/+VideomapIt/posts/Yi3y76D8RWP

I think that when a person buys an hardware, he must be free to install inside the software that prefers. But unfortunately today many companies are more interested to sell services, so with many proprietary drivers and software, trying to force users to use only and exclusively its services. This is not good for the future of IT. This is a general concept that is valid also for many others manufacturer. Should not be so especially on an Open Source OS that use the Linux Kernel. Android is becoming every day a more closed OS. But you can change that with your wallet.
[Shield Android TV General] lartomar2002:
Is the USB Hub powered or not powered?
[Shield Android TV General] jerflash:
Non powered
[Shield Android TV General] JohnHenryIron:
I've had a problem where my logitec wireless RF keyboard & mouse keep cutting out. Apparently it's a known issue and it has to do with the USB not supplying constant power. People have been saying a powered usb hub has been the solution
[Shield Android TV General] snnn:
I want to run stunnel as a long running background process. AFAIK, without rooting, there is even no way to put an executable file into android phones/boxes.
[Shield Android TV General] lartomar2002:
Can anyone tell me how well the Kobi and Nvidia console passthrough 5.1 surround sound works. I never could get it to work with my Ouya
[Shield Android TV General] nitr0burn:
Among using apps that require root for their features, the big thing for me is to enable ADB over wifi so I'm not stuck with a cable and a laptop hooked to it. Also for better debugging.

---------- Post added at 07:52 PM ---------- Previous post was at 07:51 PM ----------

wrong and wrong. USB 3.0 ports will supply more than enough power. I tried a powered usb hub and it didn't help at all, nor did it for almost everyone else. I also have another dongle based wireless keyboard + touchpad that has not had any issues at all while if I swapped it for the logitech it would have the inconsistent connection.

-edit-

Well, for some reason my logitech keyboard & touch pad isn't doing it at the moment. I haven't tried it in a few weeks as it was a major pain in the ass when it disconnects. Maybe the 1.2 upgrade fixed it. weird. nice to know I may be able to use it again. Will have to test a bit longer.
[Shield Android TV General] lartomar2002:
So, what is this secret "dongle based wireless keyboard + touchpad"?
[Shield Android TV General] machx1111:
I applaud you and your noble effort. Keep up the great work. I have not received my device yet but I plan on trying root soon as I get it!
[Shield Android TV General] nitr0burn:
Logitech k400. Probably the most popular choice for use with streaming boxes.

While that wasn't working I've been using a rii mini n7. (riitek dot com)

Primarily used the shield tv while in bed so it's perfect and has illuminated keys which is a major drawback with the Logitech as I find the keys off center vs a keyboard with no touchpad so I'm always shifted over a letter.
[Shield Android TV General] ericvh:
Ubuntu on Nvidia Shield TV

[IMG="Boot screeen Ubuntu on NVIDIA Shield TV"]https://lh3.googleusercontent.com/Y0hFSaK5JnPXan-Kn9J-zI_ifOh287jSh-grMAg1iPHA=w2668-h2000-no[/IMG]

So, hacking around a bit with the TWRP image and a customer kernel I built, I built a boot.img that just mounts an sdcard and chroots into Ubuntu, sets up the network, starts X and now I have a nice, cheap, arm64 desktop/development environment.

Current cut is a bit hack-ish, so I'm going to do some more cleanup and then I'll post detailed instructions here for folks that are interested.
[Shield Android TV General] brandogg:
Definitely interested.