[Shield Android TV General] emanuelstanciu:
It turned out not to be the dtb or hdmi or anything else, it was probably the whole blob and firmware. I reflashed the SATV with 3.2.0 from the nvidia site and restored the Android environment and then cross flashed the boot and recovery to have the L4T boot first.

All is booting and now I can use ssh to access the machine.

One additional issue came up now, I cannot start/use the X server with your rootfs in the archive you mentioned. This one does untar correctly and I don't see the locks and such and it does successfully boot/update, etc. But I cannot start X. Do you have any thoughts on this?

I did the hold command before updating anything and if I start X I get this:

ubuntu@tegra-ubuntu:~$ startx

X.Org X Server 1.15.1
Release Date: 2014-04-13
X Protocol Version 11, Revision 0
Build Operating System: Linux 3.8.0-2-mustang aarch64 Ubuntu
Current Operating System: Linux tegra-ubuntu 3.10.96 #1 SMP PREEMPT Wed Jun 22 19:29:03 EDT 2016 aarch64
Kernel command line: androidboot.modem=none androidboot.serialno=04239150155960000317 androidboot.security=enabled tegraid=21.1.1.0.0 memtype=0 vpr_resize ddr_die=1536M@2048M ddr_die=1536M@3584M section=256M usb_port_owner_info=0 lane_owner_info=0 emc_max_dvfs=1 androidboot.touch_vendor_id=0 androidboot.touch_panel_id=63 androidboot.touch_feature=0 touch_id=0@63 video=tegrafb no_console_suspend=1 console=ttyS0,115200n8 debug_uartport=lsport,2 earlyprintk=uart8250-32bit,0x70006000 maxcpus=4 usbcore.old_scheme_first=1 lp0_vec=4096@0xfdfff000 nvdumper_reserved=0xfcf00000 core_edp_mv=1125 core_edp_ma=4000 tegra_fbmem=8388608@0x92caa000 is_hdmi_initialised=1 power_supply=Adapter gpt android.kerneltype=normal
Build Date: 12 February 2015 03:00:16PM
xorg-server 2:1.15.1-0ubuntu2.7 (For technical support please see REMOVED SO I CAN POST)
Current version of pixman: 0.30.2
Before reporting problems, check REMOVED SO I CAN POST
to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.1.log", Time: Tue Jul 26 13:53:50 2016
(==) Using config file: "/etc/X11/xorg.conf"
(==) Using system config directory "/usr/share/X11/xorg.conf.d"
Initializing built-in extension Generic Event Extension
Initializing built-in extension SHAPE
Initializing built-in extension MIT-SHM
Initializing built-in extension XInputExtension
Initializing built-in extension XTEST
Initializing built-in extension BIG-REQUESTS
Initializing built-in extension SYNC
Initializing built-in extension XKEYBOARD
Initializing built-in extension XC-MISC
Initializing built-in extension SECURITY
Initializing built-in extension XINERAMA
Initializing built-in extension XFIXES
Initializing built-in extension RENDER
Initializing built-in extension RANDR
Initializing built-in extension COMPOSITE
Initializing built-in extension DAMAGE
Initializing built-in extension MIT-SCREEN-SAVER
Initializing built-in extension DOUBLE-BUFFER
Initializing built-in extension RECORD
Initializing built-in extension DPMS
Initializing built-in extension Present
Initializing built-in extension DRI3
Initializing built-in extension X-Resource
Initializing built-in extension XVideo
Initializing built-in extension XVideo-MotionCompensation
Initializing built-in extension SELinux
Initializing built-in extension XFree86-VidModeExtension
Initializing built-in extension XFree86-DGA
Initializing built-in extension XFree86-DRI
Initializing built-in extension DRI2
Loading extension GLX
Loading extension NV-GLX
Loading extension NV-CONTROL

I looks like it's trying to start the X11 bit, but I would love the actual output to go on the HDMI output screen to be able to work straight onto my desktop setup. Any idea on this?

Thanks a lot, your support has been amazing so far.