[ROM][Full Android Oreo for Shield TV][v.1.10]

[GollyJer]

Last question on this...

@zulu99
I'm sure I could set the permissions I want in the full version of Android you provide. Can the default Nvidia launcher be used with your ROM?
I like their launcher but want all the power that comes with the full ROM.

[zulu99]

Last question on this...

@zulu99
I'm sure I could set the permissions I want in the full version of Android you provide. Can the default Nvidia launcher be used with your ROM?
I like their launcher but want all the power that comes with the full ROM.

I not tested, but it does not make sense, at least for me.
Because the launcher of Android TV, make the OS static and less flexible like an old media player used in dvd players of some years ago. If you need a multimedia interface you can use Kodi or others apps.

For the other question on permissions, with root you can grant any permission to an app but generally the app ask for the permission. Otherwise with terminal emulator you can grant the permission manually. Write system settings, generally is a permission of system apps.... But you can grant also this permission manually.

[GollyJer]

I not tested, but it does not make sense, at least for me.
Because the launcher of Android TV, make the OS static and less flexible like an old mediaplayer used in dvd players of some years ago. If you need a multimedia interface you can use Kodi or others apps.

100% agree with you. I have a fully customized Kodi setup that I really like, but for the wife and kids the Nvidia interface works well. It always has the next episode for Netflix/Prime/Hulu queued up in a row without having to open the app directly. I'd like to give them the simple access and me the "power" of Kodi and full Android by putting a link to Kodi & Nova launcher in the Nvidia launcher. Sideload Launcher works great to access non-TV apps from the Nvidia interface.

Do you know of anyplace to download the Shield launcher I can't find it on any of the apk sites.

For the other question on permissions, with root you can grant any permission to an app but generally the app ask for the permission. Otherwise with terminal emulator you can grant the permission manually. Write system settings, generally is a permission of system apps.... But you can grant also this permission manually.

CF.Lumen asks for permission but when you click OK the redirection to System Settings never happens. Nvidia must have it disabled.
Luckily I found another way. This app, App Ops works great for updating ALL permission for every installed app.

[zulu99]

I not tested, but it does not make sense, at least for me.
Because the launcher of Android TV, make the OS static and less flexible like an old mediaplayer used in dvd players of some years ago. If you need a multimedia interface you can use Kodi or others apps.

100% agree with you. I have a fully customized Kodi setup that I really like, but for the wife and kids the Nvidia interface works well. It always has the next episode for Netflix/Prime/Hulu queued up in a row without having to open the app directly. I'd like to give them the simple access and me the "power" of Kodi and full Android by putting a link to Kodi & Nova launcher in the Nvidia launcher. Sideload Launcher works great to access non-TV apps from the Nvidia interface.

Do you know of anyplace to download the Shield launcher I can't find it on any of the apk sites.

For the other question on permissions, with root you can grant any permission to an app but generally the app ask for the permission. Otherwise with terminal emulator you can grant the permission manually. Write system settings, generally is a permission of system apps.... But you can grant also this permission manually.

CF.Lumen asks for permission but when you click OK the redirection to System Settings never happens. Nvidia must have it disabled.
Luckily I found another way. This app, App Ops works great for updating ALL permission for every installed app.

with adb
adb -d shell pm grant your.app android.permission.WRITE_SECURE_SETTINGS

with su:
pm grant your.app android.permission.WRITE_SECURE_SETTINGS

something like this, with adb or with su in terminal

when i comment in the forum from the phone i can't write everything i want, a pc is more flexible

[beatvr]

thank you for all the hard work!
Working like a charm over here!

[GollyJer]

Got the permissions working. Thanks!

Do you know of anyplace to download the Shield launcher?
I tried using an apk extractor but it doesn't appear in the list (that I can tell).

[2FG]

ok so no touch and hold, meaning no widgets and no shortcuts

[2FG]

never used it but will look if needs be, I always use Nova but issues currently as stated above! what specifically do you want from a launcher??

nb. if you have what you want downloaded try an app called Solid Explorer, it will unzip automatically + many many more benefits!!

T

[Mogster]

why put Amazon of all things on??? also plex etc etc is unecessary! Bug with adding new accessories! (settings keep closing)

Plex is included in the Stock ROM, so why not include it here?

[TDD]

Bricked, stuck at green Nvidia logo.

I followed the instructions for Shield TV 16GB 2017 darcy to the letter. Downloaded all the correct files, made sure my shield was updated to Oreo 7.2.1. Everything went fine except at the end with the "fastboot -w" command, check the full log attached.

Now when I boot it shows the unlocked bootloader screen with the press A to pause message, and then it moves on to the nvidia logo, screen flashes briefly, then stays at the nvidia logo, and if I also have it connected to the PC via the usb next to the heat exhaust, then eventually windows picks it up as a"Tegra device" in device manager, and it's with a yellow exclamation mark, and I can't run adb. (Whereas before I had the drivers installed and it showed it as an ADB device etc)

Here's the full log of the whole procedure. Before doing this, I set the shield to developer mode to enable adb and reboot to fastboot via console. Because my keyboard did not support holding A and B to enter fastboot, but curiously it did support pressing A to confirm the oem unlock.

Code: Select all

C:\adb\platform-tools>adb devices
List of devices attached
0321518077208   unauthorized


C:\adb\platform-tools>adb reboot fastboot
error: device unauthorized.
This adb server's $ADB_VENDOR_KEYS is not set
Try 'adb kill-server' if that seems wrong.
Otherwise check for a confirmation dialog on your device.

C:\adb\platform-tools>adb reboot fastboot

C:\adb\platform-tools>adb devices
List of devices attached
0321451077208   device

C:\adb\platform-tools>adb reboot bootloader

C:\adb\platform-tools>adb reboot bootloader

C:\adb\platform-tools>fastboot oem unlock
(bootloader) erasing userdata...
(bootloader) erasing userdata done
(bootloader) erasing cache...
(bootloader) erasing cache done
(bootloader) Unlocking bootloader...
(bootloader) Bootloader is unlocked now.
OKAY [  2.918s]
Finished. Total time: 2.920s

C:\adb\platform-tools>fastboot flash system "C:\Shield\Ful
l Android Oreo for Shield TV_1.8\system.img"
Sending sparse 'system' 1/19 (65532 KB)            OKAY [  1.725s]
Writing sparse 'system' 1/19                       OKAY [  1.409s]
Sending sparse 'system' 2/19 (65532 KB)            OKAY [  1.704s]
Writing sparse 'system' 2/19                       OKAY [  1.436s]
Sending sparse 'system' 3/19 (65386 KB)            OKAY [  1.705s]
Writing sparse 'system' 3/19                       OKAY [  1.667s]
Sending sparse 'system' 4/19 (63517 KB)            OKAY [  1.683s]
Writing sparse 'system' 4/19                       OKAY [  1.505s]
Sending sparse 'system' 5/19 (65532 KB)            OKAY [  1.734s]
Writing sparse 'system' 5/19                       OKAY [  1.359s]
Sending sparse 'system' 6/19 (63144 KB)            OKAY [  1.631s]
Writing sparse 'system' 6/19                       OKAY [  1.343s]
Sending sparse 'system' 7/19 (65532 KB)            OKAY [  1.686s]
Writing sparse 'system' 7/19                       OKAY [  1.352s]
Sending sparse 'system' 8/19 (63828 KB)            OKAY [  1.670s]
Writing sparse 'system' 8/19                       OKAY [  1.376s]
Sending sparse 'system' 9/19 (65511 KB)            OKAY [  1.760s]
Writing sparse 'system' 9/19                       OKAY [  1.617s]
Sending sparse 'system' 10/19 (62660 KB)           OKAY [  1.626s]
Writing sparse 'system' 10/19                      OKAY [  1.361s]
Sending sparse 'system' 11/19 (65532 KB)           OKAY [  1.734s]
Writing sparse 'system' 11/19                      OKAY [  1.348s]
Sending sparse 'system' 12/19 (62972 KB)           OKAY [  1.683s]
Writing sparse 'system' 12/19                      OKAY [  1.511s]
Sending sparse 'system' 13/19 (65532 KB)           OKAY [  1.695s]
Writing sparse 'system' 13/19                      OKAY [  1.421s]
Sending sparse 'system' 14/19 (63492 KB)           OKAY [  1.650s]
Writing sparse 'system' 14/19                      OKAY [  1.354s]
Sending sparse 'system' 15/19 (64195 KB)           OKAY [  1.696s]
Writing sparse 'system' 15/19                      OKAY [  1.482s]
Sending sparse 'system' 16/19 (64309 KB)           OKAY [  1.687s]
Writing sparse 'system' 16/19                      OKAY [  1.476s]
Sending sparse 'system' 17/19 (64380 KB)           OKAY [  1.696s]
Writing sparse 'system' 17/19                      OKAY [  1.361s]
Sending sparse 'system' 18/19 (65532 KB)           OKAY [  1.730s]
Writing sparse 'system' 18/19                      OKAY [  1.366s]
Sending sparse 'system' 19/19 (55422 KB)           OKAY [  1.495s]
Writing sparse 'system' 19/19                      OKAY [  1.373s]
Finished. Total time: 71.345s

C:\adb\platform-tools>fastboot flash system "C:\Shield\Ful
l Android Oreo for Shield TV_1.8\vendor.img"
Sending sparse 'system' 1/8 (65380 KB)             OKAY [  1.729s]
Writing sparse 'system' 1/8                        OKAY [  1.410s]
Sending sparse 'system' 2/8 (63745 KB)             OKAY [  1.663s]
Writing sparse 'system' 2/8                        OKAY [  1.440s]
Sending sparse 'system' 3/8 (65428 KB)             OKAY [  1.723s]
Writing sparse 'system' 3/8                        OKAY [  1.437s]
Sending sparse 'system' 4/8 (65533 KB)             OKAY [  1.696s]
Writing sparse 'system' 4/8                        OKAY [  1.626s]
Sending sparse 'system' 5/8 (65236 KB)             OKAY [  1.728s]
Writing sparse 'system' 5/8                        OKAY [  1.416s]
Sending sparse 'system' 6/8 (65532 KB)             OKAY [  1.795s]
Writing sparse 'system' 6/8                        OKAY [  1.831s]
Sending sparse 'system' 7/8 (65532 KB)             OKAY [  1.741s]
Writing sparse 'system' 7/8                        OKAY [  1.387s]
Sending sparse 'system' 8/8 (48342 KB)             OKAY [  1.305s]
Writing sparse 'system' 8/8                        OKAY [  1.208s]
Finished. Total time: 30.050s


C:\adb\platform-tools>fastboot flash boot "C:\Shield\magis
k_boot_darcy_7.1.2-v1.img"
Sending 'boot' (14115 KB)                          OKAY [  0.464s]
Writing 'boot'                                     OKAY [  0.306s]
Finished. Total time: 0.793s

C:\adb\platform-tools>fastboot flash dtb "C:\Shield\tegra2
10-darcy-p2894-0050-a04-00.dtb"
Sending 'dtb' (263 KB)                             OKAY [  0.031s]
Writing 'dtb'                                      OKAY [  0.022s]
Finished. Total time: 0.089s

C:\adb\platform-tools>fastboot -w
Couldn't parse erase-block-size '0xUnknown var!'.
Couldn't parse logical-block-size '0xUnknown var!'.
mke2fs 1.44.3 (10-July-2018)
Creating filesystem with 2977379 4k blocks and 745472 inodes
Filesystem UUID: e64a514e-09ef-11e9-a5eb-eba522d81cd4
Superblock backups stored on blocks:
        32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208

Allocating group tables: done
Writing inode tables: done
Creating journal (16384 blocks): done
Writing superblocks and filesystem accounting information: done

Couldn't parse erase-block-size '0xUnknown var!'.
Couldn't parse logical-block-size '0xUnknown var!'.
mke2fs 1.44.3 (10-July-2018)
Creating filesystem with 65536 4k blocks and 65536 inodes
Filesystem UUID: e66a0ec6-09ef-11e9-8ad4-9f43ac367ceb
Superblock backups stored on blocks:
        32768

Allocating group tables: done
Writing inode tables: done
Creating journal (4096 blocks): done
Writing superblocks and filesystem accounting information: done

Erase successful, but not automatically formatting.
File system type No partition present with this name. not supported.
Erasing 'userdata'                                 OKAY [  0.131s]
Sending 'userdata' (3032 KB)                       OKAY [  0.093s]
Writing 'userdata'                                 OKAY [  0.085s]
Erasing 'cache'                                    OKAY [  0.024s]
Sending 'cache' (120 KB)                           OKAY [  0.027s]
Writing 'cache'                                    OKAY [  0.021s]
Erasing 'metadata'                                 FAILED (remote: 'No partition
 present with this name.')
Finished. Total time: 0.827s

C:\adb\platform-tools>fastboot reboot
Rebooting
Finished. Total time: 0.018s

C:\adb\platform-tools>adb devices
List of devices attached


C:\adb\platform-tools>fastboot devices

C:\adb\platform-tools>adb devices
List of devices attached