Originally Posted by yahoo2016
Did you make sda1 boot.img 28.2 from L4T 28.x source?
I do not have SATV 2017, but as you described, dtb of SATV 2017 may be compatible with L4T 28.x.
Well, initially I tried your sda1 boot.img, but the kernel restarted after 30 seconds due to panic, so I took apart the boot.img and created a new inetramfs and it worked. I was able to see the Ubuntu desktop (your zImage + my initramfs + rootfs 24.2.1 + no flashing of dtb). Unfortunately I made the mistake of leaving the mounting of partition 29 in the init.c, so both sda1 and partition 29 were mounted and then I switched off the shield. This may have caused the shield to reboot every time after the Nvidia logo, when using the shield normally as android. I did try to make the kernel from L4T 28.2.1 source but I did not know that I had to put some cmdline in the config file in order for the kernel to show what happens on the console, so my kernel did not work or maybe worked, I do not know since I can not see anything and I tested without putting the usb (rootfs) in, so even if it worked I would have not be able to see the desktop.
What I think is that the flashing of the dbt is necessary in older ROM (I use the latest ROM 5.2), that is because in older ROM you had to flash the dtb also. I'm now trying to get the android back and then I will work on L4T 28.1.
Another thing, that I noticed, is that there are two partitions concerning the rootfs, the APP partition, which contains the rootfs and the UDA partition, which should be empty and used as data space, so the rootfs should go in the APP partition and not the UDA partition, in the shield 2017 APP -> mmcblk0p19 and UDA -> mmcblk0p33