yashsingh1/xdaforums huggingface dataset:
[Shield Android TV General] ahmed68:
dear yahoo2016

when i use boot_mmcblk1p1.img it work very well but i can see the part of hdd i try boot.img make it by (cm-12.1,initrd) i see all part of hdd ,then i format the part by sudo mkfs.ext4 /dev/sda32

tell me plz how to use sudo cp -a * /dev/sda32 && sync icant see rootfs.

you try to edit /home/roo/Linux_for_Tegra/rootfs/boot/extlinux/extlinux.conf

TIMEOUT 30

DEFAULT primary

MENU TITLE p2371-2180 eMMC boot options

LABEL primary

MENU LABEL primary kernel

LINUX /boot/Image

FDT /boot/tegra210-jetson-tx1-p2597-2180-a01-devkit.dtb

APPEND fbcon=map:0 console=tty0 console=ttyS0,115200n8 androidboot.modem=none androidboot.serialno=P2180A00P00940c003fd androidboot.security=non-secure tegraid=21.1.2.0.0 ddr_die=2048M@2048M ddr_die=2048M@4096M section=256M memtype=0 vpr_resize usb_port_owner_info=0 lane_owner_info=0 emc_max_dvfs=0 touch_id=0@63 video=tegrafb no_console_suspend=1 debug_uartport=lsport,0 earlyprintk=uart8250-32bit,0x70006000 maxcpus=4 usbcore.old_scheme_first=1 lp0_vec=${lp0_vec} nvdumper_reserved=${nvdumper_reserved} core_edp_mv=1125 core_edp_ma=4000 gpt android.kerneltype=normal androidboot.touch_vendor_id=0 androidboot.touch_panel_id=63 androidboot.touch_feature=0 androidboot.bootreason=pmc:software_reset,pmic:0x0 root=/dev/mmcblk0p1 rw rootwait

i change

1.FDT /boot/tegra210-jetson-tx1-p2597-2180-a01-devkit.dtb to FDT /boot/tegra210-foster-e-hdd-p2530-0932-e02-00.dtb(for satv pro)

2.root=/dev/mmcblk0p1 rw rootwait to root=/dev/mmcblk1p1 rw rootwait (for sd card)

here confg for cpu and ram but i dont toch it

boot_mmcblk1p1.img better than boot.img , ineed boot.img to edit hdd only

you can see here

https://wiki.archlinux.org/index.php/Syslinux

http://www.hybridego.net/entry/Android-–-NVIDIA-Jetson-TK1
[Shield Android TV General] yahoo2016:
"Linux_for_Tegra/rootfs/boot/extlinux/extlinux.conf" is for uboot used on Jetson TX1. SATV does not use uboot.

Please post output from "ls /dev/sd*" when you boot to Ubuntu on SD card.
[Shield Android TV General] ahmed68:
root@tegra-ubuntu:~# ls /dev/sd*

/dev/sda /dev/sda14 /dev/sda2 /dev/sda25 /dev/sda30 /dev/sda7

/dev/sda1 /dev/sda15 /dev/sda20 /dev/sda26 /dev/sda31 /dev/sda8

/dev/sda10 /dev/sda16 /dev/sda21 /dev/sda27 /dev/sda32 /dev/sda9

/dev/sda11 /dev/sda17 /dev/sda22 /dev/sda28 /dev/sda4

/dev/sda12 /dev/sda18 /dev/sda23 /dev/sda29 /dev/sda5

/dev/sda13 /dev/sda19 /dev/sda24 /dev/sda3 /dev/sda6

root@tegra-ubuntu:~#

this when i boot sdcard with boot.img (cm-12.1+initrd) but i replace image and zimag from /Linux_for_Tegra/kernel to /cmOutDir1/arch/arm64/boot.

today i start from sshd data part, i use boot_sda32.img but it not work for me then i try boot_mmcblk0p29.img not work problem with cpu id 3.

i make the boot.img and i chang /initrd/init.c

#include <sys/mount.h>

#include <unistd.h>

#include <linux/reboot.h>

#include <fcntl.h>

extern char **environ;

int main(int argc, char **unused) {

mount("/dev", "/dev", "devtmpfs", 0, NULL);

mount("/dev/sda32", "/dest", "ext4", 0, NULL);

// mount Android system

//	mount("/dev/mmcblk0p29", "/mnt", "ext4", 0, NULL);

mount("/dev", "/dest/dev", NULL, MS_BIND, NULL);

chroot("/dest");

chdir("/");

char * const argv[] = { "/sbin/init", NULL };

execve(argv[0], argv, environ);

}

your boot_mmcblk1p1.img the best but it for sdcard you can make for hdd im sure your boot.img the best becouse you now what to do and how the system work

thank u so much my for your help i well test all the boot.img wish you do .
[Shield Android TV General] yahoo2016:
So you do have "/dev/sda32", why did you post earlier that you have "only sda one part 500gb"?

You should be able to follow what I did for "/dev/mmcblk0p29" but use "/dev/sda32" instead.
[Shield Android TV General] ahmed68:
dear yahoo

when i use boot_mmcblk1p1.img i cant see the part of hdd for that i try make boot.img when i boot with him i see all of part

now i boot with hdd when i use boot_sda32.img or boot_mmcblk0p29.img i have error

boot.img wish i do not verey good. but i can install and boot from hdd . ihop you can make boot_sda32.img and boot_mmcblk0p29.img work.

thanks
[Shield Android TV General] yahoo2016:
"boot_mmcblk0p29.img" only work for User Data partition of 16GB SATV.

When you boot using "boot_mmcblk1p1.img" to Ubuntu on SD card and do "ls /dev/mmcblk*" what do you see? do you see "/dev/mmcblk0p1"?

If you see "/dev/mmcblk0p1" from Ubuntu, you can try copy rootfs to "/dev/mmcblk0p1" and use "boot_mmcblk0p1.img".

Make sure you use L4T 24.1 dtb when you use "boot_xxxxxx.img".
[Shield Android TV General] ahmed68:
hi yahoo2016

i see it like dev/mmcblk0

the dtb i take from /Linux_for_Tegra/rootfs/boot/tegra210-foster-e-hdd-p2530-0932-e02-00.dtb

how i can see the error of the system

have any chance update to ubuntu 16.04
[Shield Android TV General] yahoo2016:
When you boot to Ubuntu on SD card, can you run "gparted" to examine partitions of "/dev/mmcblk0" and "/dev/sda"?

You could use "gparted" to change partition table and make EXT4 partition on "/dev/mmcblk0" of SATV Pro.

Change partition table of "/dev/mmcblk0" of 16GB SATV may brick it.

Change partition table of "/dev/sda" of SATV Pro may brick it.

It seems SATV Pro uses GPT for HDD partition which may not be supported by L4T 24.1 by default.

Older "boot.img" from CM source may have GPT support by default.

If you have 2 USB to serial adapters or one USB to serial adapter and a PC with RS232 serial port, you could use USB console to see errors during boot.

You would need to plug the USB to serial adapter to one of the USB3 ports of SATV for debug and connect the RS232 port to a PC or another serial to USB adapter at 115200 baud.
[Shield Android TV General] ahmed68:
i have jtag ,uart and kl-line(ftd232) wish one i can use and how need any prog.

i can test it i replace orig sshd and make a copy i restore it 10 time with any 500gb hdd,ssd . when i run sudo cp -a * /mnt/mmcblk0p29 && sync first time there to mush error.

then i do that

sudo fdisk /dev/sda32 # input n, p ,1, enter, enter, w

sudo mkfs.ext4 /dev/sda32

sudo mkdir /mnt/mmcblk0p29

sudo mount /dev/sda32 /mnt/mmcblk0p29

cd Linux_for_Tegra/rootfs/

sudo cp -a * /mnt/mmcblk0p29 && sync

all end ok .

tel me plz how i can update to ubuntu 16.04
[Shield Android TV General] yahoo2016:
Ubuntu 16 and L4T24.2 are coming (this month?):

https://devtalk.nvidia.com/default/topic/955918/jetson-tx1/software-road-map-/
[Shield Android TV General] ahmed68:
dear yahoo 2016

I install rootfs to emmc dev/mmcblk0 first I boot by sd card and enable root user ,

sudo fdisk /dev/mmcblk0 # input n, p ,1, enter, enter, w

sudo mkfs.ext4 /dev/mmcblk0

sudo mkdir /mnt/mmcblk1p1

sudo mount /dev/mmcblk0 /mnt/mmcblk1p1

cd Linux_for_Tegra/rootfs/

sudo cp -a * /mnt/mmcblk1p1 && sync

its work better and faster .

when I run test system there one error dmi all other test pass ok.

4k work only in hdmi 1.4 android support hdmi 2 I think in Ubuntu 16.04 will be support hdmi 2.

cant install kodi and vlc (broken pakag) .

wait for Ubuntu 16.04 but we must now how to make bootloader .

thank you for help .
[Shield Android TV General] anchung.chen:
Dear yahoo2016,

Could I flash the L4T Ubuntu rootfs to the internal empty 16GB eMMC of SATV Pro ?

And I am also wondering about why Nvidia keep the empty 16GB eMMC on SATV Pro.

Thank you.
[Shield Android TV General] yahoo2016:
It appears that ahmed68 did that. I don't have SATV Pro, If you want to try it, we can discuss the steps, I'd recommend boot Ubuntu from SD card and copy rootfs from SD card to emmc of SATV Pro. When you boot Ubuntu from SD card, can you see partitions of mmcblk0 using gparted?
[Shield Android TV General] anchung.chen:
Thank such quick reply.

I think that I know how to copy the rootfs to emmc of SATV Pro ( boot Ubuntu from SD card, use gparted for creating partition and fsarchiver for restoring a rootfs backup).

But I am a little bit concern about doing this, Is it has any side effect ? And Why is there an empty eMMC on SATV Pro ?
[Shield Android TV General] yahoo2016:
I believe it's cheaper to mass produce one type of main boards rather than 2 versions for 16GB and 500GB models. (I wish Nvidia did the same for the IO cards).

If it's empty, I don't believe it has side effect. Others also tried to copy 16GB ROM to emmc of SATV Pro.
[Shield Android TV General] ahmed68:
when i clone the sshd to emmc I cant boot from emmc but now I see it like sdcard (in Linux for tegra) only I can copy rootfs for Ubuntu.
[Shield Android TV General] yahoo2016:
You could put Ubuntu rootfs on EMMC of SATV Pro and use the following trick to dual boot Android or Ubuntu:

http://xdaforums.com/shield-tv/general/trick-to-dual-boot-android-ubuntu-os-t3324994

As you mentioned EMMC is faster than most SD cards.
[Shield Android TV General] anchung.chen:
Hi yahoo2016:

I like to install L4T R24.1 on sda32 of internal SATA Disk on SAVT pro.

First I boot to L4T on sdcard with the newer kernel boot_mmcblk1p1.img from post #333, but I could not find sda32 partition.

Then I try boot to L4T on sdcard with the old kernel boot.img from post #249, It shows sda32 in /dev directory correctly.

What is difference between these two kernel ? And I will try boot_sda32.img later .

Thank your kindly help.
[Shield Android TV General] yahoo2016:
I believe I changed kernel command line in order to have kernel printk displayed on HDMI monitor. Some Android related commands were removed. I'll put back everything tomorrow morning.
[Shield Android TV General] ahmed68:
if any one have SATV (non pro) , and like to help can do that

1.boot to fastboot and run :

a.fastboot erase cache

b.fastboot erase recovery

c.fastboot erase system

d.fastboot erase vendor

e.fastboot erase userdata

2. boot to ubuntu (L4T) and run:

dd if=/dev/mmcblk0 | gzip -c > /path/to/backup.img.gz

then but it in mega drive or other

it will be less than 100mb

that enough to boot into fastboot and flash the emmc
[Shield Android TV General] ahmed68:
dear yahoo2016

I but rootfs into emmc and flash boot by boot.img from android then I flash recovery by boot_mmcblk0p1.img

from android I use this prog. (Quick+Boot+v4.8+Plus.apk) to Choose from where to boot.
[Shield Android TV General] yahoo2016:
Please try attached boot*.img:

https://drive.google.com/file/d/0Bz5kaPQJx_AgcGFJSDRlWTlRazA/view?usp=sharing

All versions of boot*.img showed all EMMC partitions of my 16GB SATV. It seems the issue is only for SATV Pro.

This version does not show console out on HDMI monitor, but does show console out on USB. A USB to serial adapter and a NULL Modem adapter is needed to connect from USB3 port of SATV to serial port of PC. If the PC does not have serial port, 2 USB to serial adapters will be needed with RD<->TD and TD<->RD.
[Shield Android TV General] anchung.chen:
I try the bootimgs3/boot_mmcblk1p1.img, and it shows all SSHD partitions of my SATV Pro.

I am grateful for your help.
[Shield Android TV General] yahoo2016:
Thanks for point out the issue for SATV Pro.

In one the dmesg's you attached, there is "androidboot.serialno". If it matches your SATV, you may want to delete it (it does not match my SATV).
[Shield Android TV General] ahmed68:
you can test this boot.img I make it for SATV pro

https://mega.nz/#!lg5kjYiK!7eoNEx2HCkrJf8cnwMQ8BykImrA8hGPnK0QKLWnBYdc
[Shield Android TV General] ahmed68:
you can see in this photo
[Shield Android TV General] anchung.chen:
What is the difference between your image and yahoo2016's image ?

Do you see all sda1 to sda32 in the /dev directory by using your image ?

I will try it later. Thank you.
[Shield Android TV General] ahmed68:
nothing only test it and tel me if it work will or not .
[Shield Android TV General] anchung.chen:
I test your boot.img in sdcard directory, and it works. All sda1 to sda32 are in /dev directory.

Thank you.
[Shield Android TV General] yahoo2016:
When you replace original SATV Pro HDD, can you delete sda32 and use the space to create 2 partitions (sda32 and sda33), one for Android (sda32) and one for Ubuntu rootfs (sda33)?

I can create boot.img for sda33.
[Shield Android TV General] anchung.chen:
Since the Android' GPT partition table on the SSHD/eMMC is not standard, It is not easy to delete or create partition in ubuntu. There are only 32 partition entry and all are used.

I will try to create new GPT header with 34 partition entry, so two extra partitions could be used by ubuntu.

---------- Post added at 02:33 AM ---------- Previous post was at 02:32 AM ----------

Hi yahoo2016:

Do you know how to run 32-bit L4T ubuntu R24.1 ? I install it on sd-card with 32-bit tegra driver installed, but I got "low resolution graphics" warning message and could not go to ubuntu desktop. Do I need to flash 32-bit L4T kernel and dtb ?
[Shield Android TV General] yahoo2016:
Even for 32 bit L4T 23.x, the kernel was 64 bits. Have you tried replacing 32 bit dtb?
[Shield Android TV General] anchung.chen:
I try to flash 32-bit dtb in Tegra210_Linux_R24.1.0_armhf/kernel/dtb/tegra210-foster-e-hdd-p2530-0932-e02-00.dtb, got same result. May try to use ssh to login in and look around.

Thank you for your help!!!
[Shield Android TV General] yahoo2016:
Have you run "apply_binaries" in 32 bit driver package to 32 bit rootfs ?

dmesg from ssh or print from USB console may help troubleshooting.

I don't believe there is 32 bit kernel source or defconfig for Tegra X1. Kernel has always been 64 bits.
[Shield Android TV General] anchung.chen:
The 32-bit L4T ubuntu is now running. The problem had been traced to the wrong owner and permission attributes of . and .. in uSD card root directory. It may come from my method of formatting the uSD card or the way of copying rootfs.

Because the arm64 version of L4T ubuntu does not provide chromium-browser application in repository, so I try to use the 32-bit L4T ubuntu version.
[Shield Android TV General] sashavingardt:
Hi yahoo2016, I've tried boot_mmcblk1p1.img, boot_sda1.img and boot_mmcblk0p29.img and they all dump stack/kernel panic. Any ideas?
[Shield Android TV General] yahoo2016:
Did you copy L4T 24.1 rootfs to SD card when using boot_mmcblk1p1.img?
[Shield Android TV General] sashavingardt:
Yessir. rootfs is on the sd card. Flashed tegra210-foster-e-p2530-0930-e02-00.dtb. Crossed the T's, dotted the I's. I've built kernels with tegra21_defconfig, shieldTv_defconfig. Tried all the boot images you've posted. Not sure what I'm missing here.

---------- Post added at 11:27 PM ---------- Previous post was at 11:24 PM ----------

Most of the kernels I've built result in a blank screen (cm-12.1 and official kernel sources). After maybe a minute or so the box reboots.
[Shield Android TV General] yahoo2016:
If you can see boot messages on HDMI monitor when using "boot_mmcblk1p1.img", but got "kernel panic", the problem is most likely rootfs on SD card. "boot_mmcblk1p1.img" has being tested by several users.

Can you describe how did you partition SD card and copy rootfs to it?
[Shield Android TV General] crnkoj:
That is true, can use uncompressed, or bz2, xz, gz compressed. Btw I was thinking, it might even be possible to netboot it, have kernel and initramfs that brings up Ethernet in booting, than boot your shield from the network, possibly even boot several shields from same.
[Shield Android TV General] yahoo2016:
I found rootfs on SD cards could be problematic. The kernel/ramdisk are very stable as long as the "boot.img" was built right, I had many issues with SD cards, e.g., the Kingston U3s haven't worked for me, SD cards flashed with older HP 6910 always worked but the same rootfs flashed with newer HP Z-book failed to work (although "rsync" worked 10 times faster on Z-Book).

Many other people also had SD card issues due to wide range of makers and grades.

I'm tempting to shrink one of the large user partitions ( 8GB?) of internal emmc and put 2GB rootfs there.
[Shield Android TV General] Helios747:
Is having the rootfs on USB an option? Would sure as heck be faster than SD.
[Shield Android TV General] yahoo2016:
I have not tried, but I believe the "Image" would be the save, only "init.c" in "initrs" directory needs to be changed from:

mount("/dev/mmcblk1p1", "/dest", "ext4", 0, NULL);

to, e.g.

mount("/dev/sda1", "/dest", "ext4", 0, NULL);

The device name "/dev/sda1" might change.

USB3 drives could be faster than SD card (I could not have Kingston 32 GB U3 SD cards working).
[Shield Android TV General] yahoo2016:
I installed Cuda 7.0 for Android on my Shield TV a week ago but did not have a chance to test it. Linux development on Shield TV is my main objective.

My Shield TV was bricked yesterday right after I installed Nivdia official rooted ROM 2.1 (I had some issues with 1.3). I'm still waiting for RMA.

BTW, I tried to put L4T rootfs on internal emmc "userdata" partition (/dev/mmcblk0p29) and changed "init.c" to load L4T rootfs from "/dev/mmcblk0p29" and it worked, but I could not create 1 more partition for L4T rootfs because the maximum number of primary partitions is 29. I don't understand why Shield Android TV created 29 partitions with only less than 10 meaningful.

Android won't start when "userdata" is overwritten.
[Shield Android TV General] Helios747:
I had the EXACT same thing happen rooting that version.

They RMA'd mine without issue. I just got it from FedEx today.

I think I'll just root my shield tv the old fashioned way with TWRP. I don't know what they did with their image that caused that to happen.
[Shield Android TV General] crnkoj:
weird, i did the same with the first one and it all worked fine. BTW where did you RMA it to (where you bought or nvidia directly)?

about creating the boot.img, mind writing the process for that ?
[Shield Android TV General] yahoo2016:
Many members of this forum and other forums have reported the same issue for Shield TV:

https://forums.geforce.com/default/topic/893616/bootloader-issues/?offset=5

http://xdaforums.com/showpost.php?p=64371396&postcount=178

http://xdaforums.com/showpost.php?p=64456425&postcount=26

http://xdaforums.com/showpost.php?p=64456825&postcount=27

https://forums.geforce.com/default/...flashing-2-0-shield-tv-firmware-brick-device/

https://www.reddit.com/r/ShieldAndr...d_android_tv_update_14_can_brick_pro_devices/

and more for Shield Tablet:

http://xdaforums.com/shield-tablet/help/shield-tablet-stuck-apx-mode-black-t3074446

http://www.ez-pg.com/q-shield-tablet-stuck-in-apx-mode-black-screen-no-bootloader.html

https://devtalk.nvidia.com/default/topic/852145/nvidia-shield-tablet-bricked-/

My shield TV was bought by company for research, I'm not in hurry to have it repaired during holidays. It was not purchased from Nvidia, I though I could get technical support from Nvidia and bring attention to them for the issue. I did receive RMA from Nvidia and should get replacement in a week.

Do you mean generating "boot.img" from "Image"? From the first post, you can download my "initrd", make changed to "init.c" and run "make".
[Shield Android TV General] crnkoj:
I see. Is it not necessary to use this abootimg tool/program to package the initrd and the zimage together?
[Shield Android TV General] yahoo2016:
"abootimg" is in the last line of "Makefile".
[Shield Android TV General] crnkoj:
ooops missed that. Thanks.
[Shield Android TV General] yahoo2016:
You only need the last line if you don't make change to the ramdisk (you could change the path to ramdisk from /tmp to other locations).

I started to learn u-boot, I have built u-boot for TK1 and TX1 (I have TK1s and have TX1 in order). I'll see if it's possible to install u-boot as 2nd stage bootloader for Shield TV and enable u-boot netconsole.
[Shield Android TV General] dieter.reuter:
If you only want to replace the kernel in boot.img you can use the following command, which is easier to use.

abootimg -u boot.img -k Image

Here we just replace the kernel "Image" in the boot image file "boot.img".

---------- Post added at 02:14 PM ---------- Previous post was at 01:59 PM ----------

@yahoo2016:

Do you have an idea how to change the kernel or settings, so that it uses a specific video resolution by default?

Right now, I can only use a video monitor (like a TV). As soon as I attach my large screen computer monitor I didn't get a display at all.

I'd like to use a computer resolution like 1920x1080p60 or smaller (or 3440x1440p50 for my LG widescreen display), but the ShieldTV is only using 1280*720p60 or 1920x1080i60 - both resolutions didn't work on my monitor at all.

If the ShieldTV would detect the right resolution or using at least a default computer resolution, it would be even better to use.
[Shield Android TV General] yahoo2016:
I have not tried it but I recall a member posted changing kernel command line for default resolution (I can't try it now without a working Shield).

I believe if correct nvidia drivers are loaded correctly, most resolutions should be supported. I believe my setup using the kernel/ramdisk and rootfs in the first post worked for many resolutions including lower res computer monitors.
[Shield Android TV General] dieter.reuter:
Ok, I understand.

I'm running my own built root filesystem right now only. It's based on Debian Jessie for ARM64 and will be the next generation of our HypriotOS (see http://blog.hypriot.com) to run Docker container technology on the Nvidia boards. I'd like to support the ShieldTV and Jetson TX1, maybe the TK1 later on with 32-bit (I do have a Jetson TK1 DevKit in my lab too).

But until now, I didn't installed any of the specific Nvidia drivers or software on it. So, I think I'll try it again with the L4T roots which is based on Ubuntu 14.04, just to check if there is a better support of the correct monitor modes.
[Shield Android TV General] yahoo2016:
If you want to try kernel command line, you can edit the last line of "bootimg.cfg" file included in my "initrd" tar file from the first post:

bootsize = 0x18d5800
pagesize = 0x800
kerneladdr = 0x10008000
ramdiskaddr = 0x11000000
secondaddr = 0x10f00000
tagsaddr = 0x10000100
name = mrom20150630-01
cmdline =

I could not remember exactly, but it could be something like

cmdline = "res=1280x720"
[Shield Android TV General] crnkoj:
Hey, did you use Ubuntu 15.10 or 14.04 for compiling this, i did all as you described with ubuntu 64 15.10 and i keep getting compile errors...
[Shield Android TV General] yahoo2016:
I was using ubuntu X64 14.04 LTS (I updated OP to clarify), but I'll install Ubuntu 15 on one of my laptops.

I may need to update OP after trying Ubuntu 15.
[Shield Android TV General] dieter.reuter:
I'm running Ubuntu 14.04.1 LTS (GNU/Linux 3.13.0-44-generic x86_64) in a Vagrant box too, and it's works well. Didn't tried it with 15.04 or 15.10.
[Shield Android TV General] sashavingardt:
Using parted:

(parted) mklabel gpt

(parted) mkpart ESP fat32 1MiB 513MiB

(parted) set 1 boot on

(parted) mkpart primary ext4 513MiB 100%

Then:

sudo mkfs.ext4 /dev/sdb2

sudo mkdir /mnt/SDReader

sudo mount /dev/sdb2 /mnt/SDReader

sudo cp -a ~/Linux_for_Tegra/rootfs/* /mnt/SDReader

unmount.

Yahoo2016, thank you for your help on this!

---------- Post added at 01:10 AM ---------- Previous post was at 01:00 AM ----------

I think I know what it is ))) Trying out single partition with a msdos partition table. Think this might be it. Thank you for pointing this out. Will report back soon.

---------- Post added at 01:31 AM ---------- Previous post was at 01:10 AM ----------

Booted a stock kernel and it totally worked! Thank you, yahoo2016. You are awesome. So appreciated!
[Shield Android TV General] sashavingardt:
yahoo2016, so now I can boot into Ubuntu. But it seems to be running extremely slowly after a minute or so, almost to a grinding halt. The system is completely unusable. Have you experienced any of this?

Thank you
[Shield Android TV General] yahoo2016:
What apps were you running?

Have you replaced Wifi firmware files in L4T rootfs with Wifi firmware files for SATV?

Have you checked memory leak?
[Shield Android TV General] anchung.chen:
Hi Yahoo2016:

The TX1 L4T-R24.2 is out, but I could not boot the new kenel on SATV.

Try to do investigation now ???