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

[zulu99]

I highly recommend staying with FAO 1.7 for now. Moving to 1.8 requires updating the stock rom to 7.2.1, but that has massive problems right now. TWRP is broken, rooting is partly broken, and there are a huge number of complaints on the Nvidia forums: https://forums.geforce.com/default/board/159/shield-tv/

Absolutly i don't think this.

Despite Nvidia is a shit company, have a new kernel, 4.9 kernel, while old stock firmware have just 3.8 kernel, is an extraordinary thing.

Therefore first or after you must update.

Despite few Nvidia problems that can be corrected easly with next 7.2.2, full Android 1.8 work very well.

Root with magisk work well.

TWRP is not more necessary with Magisk, and when you have root, you can do everything twrp do, also manually.

Apart this, for twrp developers is easy create an update version with a new kernel.

My suggestion is that you can update to full Android 1.8 without problems.

P.S.
Root is broken just for idiots that not know that they need a custom dtb on darcy. Many of this idiots, read only xda forum and Nvidia forum

I'm usually very modest, but I want to clarify something. Thanks to all the work I've done over the last few years on full Android, apart from the Nvidia developers, no one knows Shield TV better than me in the panorama of independent developers.

From the next year, i will help also Android TV users, maybe i will open a new thread in this forum. I understund after long time that also this users need help, but many of this will never flash a custom firmware. For this reason i will help with root and with mods that can do also not tech users.

The custom boot images and the dtb file for darcy, are flashable also on the stock firmware to root Android TV in the proper way.

I will contonue to create and use exclusivly full Android in my house, but when is possible, i will create my gameplay on Android TV.

[zulu99]

Is implied in the command fstboot -w posted in the guide.

Anyway i write here more explictly.

To update from 1.7 to 1.8, you must erase old data. This is a completly new firmware. Without erase data you will have a semi working firmware or a firware that not start.

[zulu99]

if it is not yet clear

To write system partition in darcy ( shield tv 16GB 2017 model )

you must install my custom dtb file also on android tv

and reinstall magisk without preserve dm-verity. deleselect AVB and force encryption in magisk manager and make it install itself.

[MickG]

Well said mate,Many happy returns and Happy New Year,....cheers and respect

[zulu99]

I made a video on how to share the hardware controller trought the phone in the hope that will be simple for every Shield Android TV user.

On full Android is not necessary because i restored the custom IMEs for Shield TV like on all other Android devices

If you are far away from Shield TV, connecting to the bluetooth of the phone is also better than connecting to the bluetooth of Shield TV, because with less distance you will have more stability and less lag. But a direct connect with the usb cable is always better.

HAPPY NEW YEAR TO EVERYONE

[Mogster]

I highly recommend staying with FAO 1.7 for now. Moving to 1.8 requires updating the stock rom to 7.2.1, but that has massive problems right now. TWRP is broken, rooting is partly broken, and there are a huge number of complaints on the Nvidia forums: https://forums.geforce.com/default/board/159/shield-tv/

Absolutly i don't think this.

Despite Nvidia is a shit company, have a new kernel, 4.9 kernel, while old stock firmware have just 3.8 kernel, is an extraordinary thing.

Therefore first or after you must update.

Despite few Nvidia problems that can be corrected easly with next 7.2.2, full Android 1.8 work very well.

Root with magisk work well.

TWRP is not more necessary with Magisk, and when you have root, you can do everything twrp do, also manually.

Apart this, for twrp developers is easy create an update version with a new kernel.

My suggestion is that you can update to full Android 1.8 without problems.

P.S.
Root is broken just for idiots that not know that they need a custom dtb on darcy. Many of this idiots, read only xda forum and Nvidia forum

I'm usually very modest, but I want to clarify something. Thanks to all the work I've done over the last few years on full Android, apart from the Nvidia developers, no one knows Shield TV better than me in the panorama of independent developers.

From the next year, i will help also Android TV users, maybe i will open a new thread in this forum. I understund after long time that also this users need help, but many of this will never flash a custom firmware. For this reason i will help with root and with mods that can do also not tech users.

The custom boot images and the dtb file for darcy, are flashable also on the stock firmware to root Android TV in the proper way.

I will contonue to create and use exclusivly full Android in my house, but when is possible, i will create my gameplay on Android TV.

Hmm, I have to disagree with you here. I don't doubt your expertise with the ShieldTV, but 7.2 does bring some unfixable problems, at least for foster. I used to modify the boot image to place /data on an external SSD, but that no longer works and I don't know why. I also cannot boot Linux4Tegra (Ubuntu 16.04) - again, it fails and I don't know why. Both of them just hang at the Nvidia logo. The foster bootloader cannot be downgraded - flashing the old bootloader does nothing. The version does not change. Also, fixing TWRP is currently impossible until Nvidia releases the kernel source code. Take a look at the fstab.{foster_e|darcy} files - notice something missing? /system and /vendor are no longer mounted from the fstabs. So how how do they get mounted? TWRP can't function without this information. The TWRP thread on XDA is filled with complaints but no real solutions, at least not for foster.

So, maybe it's an improvement for darcy, but for foster it's been a nightmare. That's why I can't recommend it. Also, Happy New Year to you too.

[zulu99]

Hmm, I have to disagree with you here. I don't doubt your expertise with the ShieldTV, but 7.2 does bring some unfixable problems, at least for foster. I used to modify the boot image to place /data on an external SSD, but that no longer works and I don't know why. I also cannot boot Linux4Tegra (Ubuntu 16.04) - again, it fails and I don't know why. Both of them just hang at the Nvidia logo. The foster bootloader cannot be downgraded - flashing the old bootloader does nothing. The version does not change. Also, fixing TWRP is currently impossible until Nvidia releases the kernel source code. Take a look at the fstab.{foster_e|darcy} files - notice something missing? /system and /vendor are no longer mounted from the fstabs. So how how do they get mounted? TWRP can't function without this information. The TWRP thread on XDA is filled with complaints but no real solutions, at least not for foster.

So, maybe it's an improvement for darcy, but for foster it's been a nightmare. That's why I can't recommend it. Also, Happy New Year to you too.

First:
All this things are not related to full Android and to Android TV

Second:
The fact that you don't know how to do some things, don't means that this things are not possible. You must just familiarize with the new kernel and dtb.

P.S.
system and vendor are mounted in the dtb file, for this reason i called idiot some xda developers......in darcy with dm-verity enabled, but disabled in my custom dtb, instead on all others models dm-verity is not enabled.

With dm-verity enabled, you can't write the system partition also if you have root with magisk. To write the system partition you must disable dm-verity with a custom dtb and reflash magisk deselecting force encryption and dm-verity


All this are stupidities already discussed from long time in many developers forums, the real shit made by Nvidia is his Android framework modification made on purpose to fight concurrents.

This is the real and hard shit that fortunatelly i solved in few days and corrected in full Android.

Nvidia is assuming really a not correct behaviour on his Shield TV and companies like this, should be removed the possibility to use the kernel source code.

If it were possible, I would do a law for which companies that cheat can not use the linux kernel.

Nvidia is not a correct company and is the ruine of the open source world, is a company that, for the sake of all, should completly fail.

If you can, do not buy Nvidia chips.

[greystash]

Will FAO 1.8 already work with shield experience 7.2.2 test images?

[zulu99]

Will FAO 1.8 already work with shield experience 7.2.2 test images?

Sure the kernel is the same

[GollyJer]

zulu99,

Please feel free to say "no, not going to try this". I'm fine with that answer but I thought I'd ask in case you want to give it a shot.

I'm trying with all my might to get color filtering to work with the Shield. To improve sleep my family and I use nighttime orange/red overlay on all our devices but the Shield is the last holdout.

CF.lumen is the champ as far as color customization goes. Is there any chance you can try installing CF.lumen on your FAO v1.8 and see if it works?

I'm hoping it works with these two settings.


With 7.1.2 fully rooted, per your instructions, I'm only able to get the Driver: Performance: Mode working.

However, in this mode none of the DRM video services work. You can see my question to chainfire here.

Thanks again for all your amazing work and Happy New Year!!