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

[2FG]

Plex is crapware too!

@Golly try mobilism.org

[bananaz]

Nope, plex is THE best. Especially if you get the lifetime pro version, you get also dvr to record tv shows, etc. And now they support the auto subtitles download from opensubtitles, so it's a great all rounder for TV section.
Why do you call it crapware? Any reason? You see plex as bloat?

OT: my 2nd shield is during shipping (we do not have it in my country, so I ordered from amazon), I hope not to brick this one as well. I am planning on giving droidmote another go. Does it work well with 7.2.2 on darcy?

[ProPeace]

My Shield is actually going back from your Full 1.7 to Nvidia stock 7.1,
will update to stock Nvidia 7.2,
and then, will go for your full 1.8.

Good work, zulu99 ! ^^

May I suggest you to indicate the release date of your firmwares,
in your first post,
when you're posting a new firmware.

It will make it easier for us to find the first post of the topic for your new version...

[Mogster]

If you don't like it, disable it. Also, try Shortcut Creator for shortcuts and widgets.

[zulu99]

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

Please do not use the word bricked when you are in bootloop.

Bricked means when you can't go anymore in fastboot to flash samething.

When fastboot work, you can go in fastboot also with the hardware method, pressing A and B on controller while the device boot, explained in first post.

Anyway try update fastboot from google and retry.
https://dl.google.com/android/repositor ... indows.zip

I installed the firmware on my shield tv 2017 and 2015 many times. And many users already installed full android 1.8 without problems.

PS
Since i have the bootloader unlocked from the first day like many users, i suggest to start the stock firmware at least one time with the bootloader unlocked and after flash full Android.

Anyway if fastboot work, reinstall the stock 7.2.X firmware, update to last 7.2.X firmware, reboot and after retry install full Android with the updated fastboot binary downloaded from google.

[zulu99]

Hey friends, this game is not too bad as alternative to pubg mobile and fortnite, also because work everywhere.

P.S.
I'm recording with full Android 1.8

[zulu99]

Just a small off topic:

Do you know what is the real reason that an hardware controller is better than controller on phone for FPS games ?

The main problem of the controller on phone, is that you can't do 3 actions at same time, example move, aim and shoot.

On hardware controller instead you can.

To solve this problem, especialy for windows and linux games, because for Android games is not so important because users with a touch screen have the same problem, can't do 3 action at same time, i added an option in droidmote client, "fast shoot in FPS". When this option is enabled, you can click the left stick while moving with a variation of pressure, threfore you can move, aim and shoot at same time.

This option is not perfect on all phones, i calibrated it on my galaxy s8, but can improve.

Since this new functionality can be used also on Android games, i advice you that who play with DroidMote, can have serious advantage over regular touch screen users.

Therefore attention ! A droidmote user can easly kill you in pubg mobile and others similar games

Apart the joke, i'm trying to solve the main problem of a touch screen, 3 actions at same time. Because with thumbs you can do only two concurrent actions generally.

PS
Volume buttons are not good for the third action and also a tap on back of the phone is not good, if you have suggestions, i'm open to listen you.

[2FG]

just bought TPC in the hope it's as simple as just adding a file to get the thing to play pubg when im finally ready!?!?!?

ok so i just rebooted and am stuck on mobile view ie third of screen in middle of tv and I cant for the life of me remember how to put things right, anyone please

[2FG]

Z would you recomend installing TWRP now to make good a full backup now things are kinda settling down??

[2FG]

@TDD I had same, I just reflashed stock 7.2 and tried again, it worked for me. GL!!