yashsingh1/xdaforums huggingface dataset:
[X Style (Pure) Q&A, Help & Troubleshooting] BooBzi:
Nop, could find solution, so I did full wipe, and restored my backup file with 5.1.1. Also flashed stock logo, boot and modem, so it can boot my old 5.1.1. Moto.

Will wait for some kind of european ROM with Marshmallow, or TWRP update. Maybe later will try again to go fully stock and upgrade to Marshmallow, maybe will find something that will work, right now I just need my "phone" back so I can use it as daily driver.
[X Style (Pure) Q&A, Help & Troubleshooting] JayShams:
I just finished flashing TruPureXMM. I'm in the middle of restoring all my apps, and I still need to re-fix the WiFi, but otherwise my experience is working well. You might want to check that out.
[X Style (Pure) Q&A, Help & Troubleshooting] BooBzi:
For wifi you should flash modem from his thread: https://www.androidfilehost.com/?fid=24269982087017262

Its Pure modem with band 12 fix.

I was using his Rom for some hours and didnt like it, my personal opinion:

Good: easy to install; twrp, supersu, xposed is working.

Bad: modified kernel (had more problems with it, it was draining battery so fast - 4 little cores was always online for ~900-1440MHz, and 1 big core always online for same frequancy as little cores, only one big core was going idle), so I didnt like all this modifications to stock kernel, also I didnt like that mine EU version now is listed as US version XT1575, and last that I noticed after some hours of usage is that on secret menu, mine 3G network was listed as WCDMA, but on EU of mine Style same 3G is using GSM auto method. I suppose that there can be some difficulties in EU countries - after changing settings to 4G, I loosed signal, and only after restart I got it back.

Thats the main reasons why I want european rom, or to modifie stock eu MM with xposed.
[X Style (Pure) Q&A, Help & Troubleshooting] ChadMan097:
I think in that case I did flash SuperSU the old way for Stock Moto Marshmallow. I then did a TWRP backup to go back to full stock and tried rooting using systemless, but something isn't right. It's showing up, apps are asking for permission, but its acting odd. The apps can't get permission and Viper for example just crashes and other apps just keep saying something is wrong. My TWRP is messed up to. It was pushed correctly, but it seems very unstable. I can't flash any ROMs and if I plug it into my computer to send a file, when I reboot it no longer shows it in my directory to install. Sometimes if I hit reboot device, it only reboots recovery or just ignores the command entirely. I think I will revert it back to moto standard and try again, but this has been a little weird.
[X Style (Pure) Q&A, Help & Troubleshooting] patt2k:
Either do systemless or 2.52 had same issue til I flashed 2.52 ;)
[X Style (Pure) Q&A, Help & Troubleshooting] BooBzi:
Solved my issue here.
[X Style (Pure) Q&A, Help & Troubleshooting] donebrasko:
fastboot flash modem NON-HLOS.bin

Where and how do I type this? I have everything else done.
[X Style (Pure) Q&A, Help & Troubleshooting] Kennyeni:
Hi,

I followed this instructions and I have two problems:

It only boots using

flashboot boot boot.img

(in fact I can't do the

fastboot reboot-bootloader

command because the previous command just boots the phone)

There's no wifi, I tried flashing the modem linked before but I think that's for 5.1.1 so it didn't work
[X Style (Pure) Q&A, Help & Troubleshooting] BooBzi:
For this you need adb files on your PC.

You should read this thread, for how to get this files on your PC.

Then:

Basically, open terminal within adb driver folder, connect phone via USB to PC with USB Debugging ON, and you are ready to go - boot your phone into fastboot mode (shut down phone first, and then power+volume down) and now your are ready to use this command: fastboot flash modem NON-HLOS.bin, but remember to put this "NON-HLOS.bin" file into folder where you opened terminal from.

But if you experience problems, I suggest just install TruPureXMM ROM. It whould be much easier!

Good luck!
[X Style (Pure) Q&A, Help & Troubleshooting] BooBzi:
Hello!

Have you read my other thread?

I have explained all my steps there, my device is Moto X Style (XT1572).

But I can suggest also use TruPureXMM ROM. Right now I am using this rom for about month, you could try it!

Good luck!
[X Style (Pure) Q&A, Help & Troubleshooting] De@thst@lker:
No luck with reflashing NON-HLOS.bin

I tried systemless root on my moto x pure marshamallow. Now the wifi is not working at all. I tried reflashing the NON-HLOS.bin but no luck there. Is there any way to solve this issue? Or should i revert back to lollipop seems like it is working just fine for others on lollipop.
[X Style (Pure) Q&A, Help & Troubleshooting] BooBzi:
Lets start from beginning.

What is your device codename (region)?
[Shield Android TV General] yahoo2016:
Update (08/26/2017) Update:

I updated my SATV Pro 2015 to ROM 5.x, I did not have to replace dtb file. The img files from link below seem still working.

The following have been tested for SATV ROM 3.x.

Latest boot images based on L4T24.2 for external SD card, USB drive, internal EMMC and internal HDD can be downloaded from:

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

Where,

"mmcblk1p1.img" is for booting to rootfs on external SD card.

"sda1.img" is for booting to rootfs on external USB drive (or SD card in USB adapter), or internal SATA HDD of modified 16GB SATV.

"mmcblk0p29.img" is for booting to rootfs on partition 29 (User Data) of internal eMMC of 16GB SATV if only Ubuntu is needed.

"mmcblk0p1.img" is for boot to rootfs on partition 1 of internal eMMC of SATV Pro.

"sda32.img" is for booting to rootfs on partition 32 (User Data) of HDD of 500GB SATV Pro if only Ubuntu is needed.

"sda33.img" is for booting to rootfs on partition 33 of HDD of 500GB SATV Pro for Ubuntu (modification of HDD partition table is needed).

"sda34.img" is for booting to rootfs on partition 34 of HDD of 500GB SATV Pro for Ubuntu (modification of HDD partition table is needed).

You will need to download L4T24.2 driver package and rootfs from Nvidia (https://developer.nvidia.com/embedded/linux-tegra), apply binary drivers to rootfs and copy it to external SD card/USB drive, see this post:

http://xdaforums.com/showpost.php?p=69202451&postcount=421

or internal eMMC or HDD (of SATV Pro):

http://xdaforums.com/showpost.php?p=69202672&postcount=422

L4T24.2 dtb from L4T24.2 rootfs "/boot" needs to be flashed. To find dtb name for your SATV, type the following in recovery mode:

sudo fastboot oem dtbname

Flash the wrong dtb will likely brick the SATV!!!

To have Wifi working, "/lib/firmware/brcm/fw_bcmdhd.bin" need to be replaced with the one from SATV (in /system/vendor/firmware/bcm4354).

To build kernel from source, download the latest L4T kernel source, modify tegra21_defconfig by adding "CONFIG_ANDROID=y", example configuration file can be downloaded from the following link

https://xdaforums.com/showpost.php?p=69078331&postcount=417
[Shield Android TV General] kdb424:
Thanks for this. I'll see if I can get something booting. Very much appreciated. Glad to see some real dev going into these boxes lately. Not discrediting all the amazing devs so far, just commenting the interest is really ramping up!
[Shield Android TV General] crnkoj:
thanks for the post, i was reading some things, we do have the issue with the device trees for full linux sort of. found a rather good explanation for dtbs here https://events.linuxfoundation.org/sites/events/files/slides/petazzoni-device-tree-dummies.pdf if anyone is interested. i was now checking in the cm12.1 kernel under arch/arm/boot/dts and saw there are many foster dts, to build dtbs at kernel compile time. Do we need to use tegra124-loki-foster.dts or tegra124-loki-foster-p2530-0900-c00-00.dts for the 16 gb shield, i know for the pro there is tegra124-loki-fosterhdd-p2530-0900-c00-00.dts

btw i have the l4t with cuda and your prebuilt kernel working and am running some testes with a specialized cuda program, it appears it can do around 330Gflops on the gpu (assuming the maximum of 512gflops it appears already to be good performance), second thing, comparing the single and quad core performance it has a speedup of 3.3 going from 1 to 4 cores, while going from 32bit l4t to 64bit ubuntu from the other thread here, the 64 bit one is around 13% faster both in single and quadcore computation (obviously cant compare cuda speed). on the 64 bit version it needs 3 minutes to compute something that a 2600k needs 1 minute. so the 2600k appears to be for this use approx (only) 3 times faster
[Shield Android TV General] yahoo2016:
I'm very interested in Cuda testing on Shield TV, I posted on Nvidia TX1 board:

https://devtalk.nvidia.com/default/...da-7-0-jetson-tx1-performance-and-benchmarks/

I thought Nvidia advertised Tegra X1 maximum of 1TFlops.

How did you test 64 bit version?

Which Cuda tests did you run?
[Shield Android TV General] crnkoj:
firstly to the perfromance it advertises 512gflops/s single precision fp32 and 1tflops/s half precision fp16, you can check here

http://www.anandtech.com/show/8811/nvidia-tegra-x1-preview/2

i think its just marketing with 1Tflop...

secondly i think you misunderstood me, maybe my post was a bit confusing

i managed to test CUDA on the L4T 32 bit, but not on the 64 bit Ubuntu.

the 330 GFLOPs were on L4T 32 bit using a program called CHARMM for molecular dynamics (actually a friend tested it through ssh). That was just a short test to see the peak.

We tested the CPU performance with the same program, this time both on 32 bit L4T and 64 bit Ubuntu, there 64 bit Ubuntu was 13% faster, both single threaded and 4 threaded (comparing 1 cpu to 4 cpus/whole SOC), and the speedup multiplier between 1 and 4 threads was 3,3, which is better than that on a 2600k (it has 3,2). The difference in speed in this CPU only test was however comparing the 2600k and the shield on maximum performance (eg shield 4 threads, i think 2600k he tried with ht turned on so 8 threads) was of a factor of 3, 2600k = 1 minute, shield = 3 minutes. CPU only speed.

We are now testing with more demanding parameters so it takes longer, so we can compare the time it takes on the shield on the GPU/CUDA to the time it takes on x86 with a dedicated gfx (660 gtx or 960 gtx), with more demanding/longer parameters because the early setup stage is too long to compare the calculations time for the GPU part otherwise.

Thats why i asked you for the way of building the kernel so i could build my own to have the system on an usb drive. furthermore it would be interesting to be able to boot with a proper linux and not android dtb, but as far as i understood [MENTION=1416222]Steel01[/MENTION] one should not change the dtb on the partition, as otherwise the bootloader fails to start and we have a brick... Thats why the kexec method or alternatively the append dtb to kernel method would be better, but than wed need to reduce the size of the kernel/initramfs so that we could append the dtb to it, again needing another kernel/initramfs. After that id probably try with proper 64 bit linux and try to perhaps get 32 bit cuda to work on it. or alternatively being stuck waiting for nvidia to release 64 bit l4t/cuda/drivers binaries, because i dont believe that 32 bit nvidia drivers are going to work on a 64 bit linxu system (eventually perhaps as multilib, but thats even more complicated on arm as on x64)
[Shield Android TV General] yahoo2016:
Thanks for clarifications. I also noticed dtd issue, the normal linux kernel build involved the following steps:

make O=$TEGRA_KERNEL_OUT dtbs
make O=$TEGRA_KERNEL_OUT modules
make O=$TEGRA_KERNEL_OUT modules_install INSTALL_MOD_PATH=<your_destination>

I installed the outputs to my L4T rootfs, but the Android boot loader/kernel won't use them.

It's possible but more dangerous to repartition internal emmc to fix larger kernels That was done for chroubuntu on Chromebook CB5.
[Shield Android TV General] yahoo2016:
Ideally, I'd like kernel and rootfs on external SD (the way I'm running ubuntu on my Chromebook CB5). It seems the only way would be to have multiroom or u-boot working.

I made changes to makefile of Link 1 such that the ramdisk is only 480 KB instead of 2 MB.

The "maxPef.sh" scrip to set CPU/GPU clocks is critical to maximize performance.
[Shield Android TV General] crnkoj:
I think you can forget uboot. Perhaps multirom, especially as the new pixel c tablet uses the same chipset and I think more people will use and develop for it. Yeah all the tests until now were with the stock governor and speeds. Have to retest all now...
[Shield Android TV General] yahoo2016:
I found someone even installed u-boot for Galaxy:

http://xdaforums.com/galaxy-s2/general/uboot-bootloader-true-multiboot-t1680898

I like my Tegra K1 based Chromebook CB5, it's truly double boot (Ctl U for external Ubuntu and Ctl D for stock ChromeOs). I'll not even consider an overpriced Pixel C which does not have SD slot or USB 3 port or HDMI port. Shield TV is much better than Pixel C for hacking. I'll look into multiRom for shield, I got impression it failed to build for arm64.
[Shield Android TV General] crnkoj:
uhms, i meant, that now that the pixel c is out, more people will develop for it and we can use their work/cooperate
[Shield Android TV General] yahoo2016:
I also keep tracking of Jetson TX1 board, people are trying to install Android for TX1s (they did for TK1). I'm trying to understand how boot loaders were installed to new Tegra devices. I flashed boot loader to my Jetson Tk1 using nvidia flash script many times.
[Shield Android TV General] crnkoj:
yeah cuz TK1 is a developer board and its open, the shield is a consumer devie and if you wish to use nvflash you need the SBK key - securebootkey, which nvidia wont give out, thats a given
[Shield Android TV General] yahoo2016:
That's what I read from other thread that Nvidia broke their boot loader through OTA update, has not fixed the issue and won't give out the SBK - securebootkey.

I have to read more about SBK. I found the following from Nvidia are interesting:

http://http.download.nvidia.com/tegra-public-appnotes/tegra-boot-flow.html

http://http.download.nvidia.com/tegra-public-appnotes/bct-overview.html
[Shield Android TV General] serige:
First time trying to build an rootfs image here, I probably did it wrong since the screen went dark right after booting and never go anywhere.

I followed OP's steps to build L4T rootfs. Then under Linux_for_Tegra/rootfs, I did

find ./ | cpio -H newc -o > ../rootfs.img

Then I dumped the image to my sd card:

dd if=../rootfs.img of=/dev/mmcblk0 bs=4194304 oflag=sync

Can anyone point out the correct way of making a L4T image? Many Thanks!
[Shield Android TV General] yahoo2016:
I should finish the post with ways to flash rootfs. The contents of Linux_for_Tegra/rootfs should be copied to sd card with permissions preserved. The way I do it is.

(1). cd to Linux_for_Tegra/rootfs.

(2). "sudo tar -cpf ../rootfs.tar *

(3). format SD card ("sudo mkfs.ext4 /dev/mmvblk0p1")

(4). Mount SD card "sudo mount /dev/mmcblk0p1 /mnt".

(5). "cd /mnt"

(6). sudo tar -xpf [path to rootfs.tar]

I updated first post for steps of copying rootfs to SD card.
[Shield Android TV General] crnkoj:
Actually it's faster with rsync

Let's say sdcard is mounted to /mnt

1. cd to /mnt

2. rsync -av /path/to/rootfs/* .

And done
[Shield Android TV General] yahoo2016:
Thanks for the easier way to sync rootfs between development PC and target SD card. I did the other way to keep a copy of "rootfs.tar "on network drive so I can access it from other locations.

I'll include your way to the first post.
[Shield Android TV General] crnkoj:
You could do the same on a network drive, just unpack the rootfs into a directory, than

rsync -av 192.168.1.2:/rootfs/* /desiredmountpoint

Or rsync -av /hdd_mountpoint/rootfs/* /sd_mountpoint

clearly it is a bigger mess on the hdd as its not one archive but a whole rootfs, though in its own directory, but you can edit the rootfs directly on the hdd.
[Shield Android TV General] yahoo2016:
I edited the first post to include your even simpler one command to sync rootfs.

I found "sudo tar -cpf" did not compression rootfs (2GB), I should use "sudo tar -cjpf" to generate compressed rootfs (700 MB).
[Shield Android TV General] rxg846zebra:
Interesting, now that you mention it, the LED on my keyboard is never ON during the process. I will try to get my hands on a powered USB hub and let you know the result.

Thanks!
[Shield Android TV General] yahoo2016:
I tried and it worked. I used the same microSD card to make sure it worked in the microSD slot of SATV, I then put the microSD card into a microSD to USB adaptor and plugged it in one of the USB3 ports. I have KB/mouse plugged in the other USB3 port through a powered USB hub.

I made a new "init_usb.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 rootfs to first partition of external sd card
//	mount("/dev/mmcblk1p1", "/dest", "ext4", 0, NULL);
// mount rootfs to user data partition of internel emmc
//	mount("/dev/mmcblk0p29", "/dest", "ext4", 0, NULL);
// mount rootfs to first partition of USB
mount("/dev/sda1", "/dest", "ext4", 0, NULL);
mount("/dev", "/dest/dev", NULL, MS_BIND, NULL);
chroot("/dest"); // make /dest the new root
chdir("/"); // change to new root

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

execve(argv[0], argv, environ); // excute "/sbin/init"
}

and modified makefile:

all:
aarch64-linux-gnu-gcc init.c -o init -static
find ./ | cpio -H newc -o > /tmp/nvidia_initrd
rm -f /tmp/nvidia_initrd.gz
gzip /tmp/nvidia_initrd
abootimg --create ../cmOutDir1/boot.img -f bootimg.cfg -k ../cmOutDir1/arch/arm64/boot/Image -r /tmp/nvidia_initrd.gz

usb:
aarch64-linux-gnu-gcc init_usb.c -o init -static
find ./ | cpio -H newc -o > /tmp/nvidia_initrd
rm -f /tmp/nvidia_initrd.gz
gzip /tmp/nvidia_initrd
abootimg --create ../cmOutDir1/boot.img -f bootimg.cfg -k ../cmOutDir1/arch/arm64/boot/Image -r /tmp/nvidia_initrd.gz

I used "make usb" to make USB version of "boot.img"
[Shield Android TV General] Sompom:
Also working on USB boot

Interestingly, totally independently from yahoo2016, I have also been trying to get my Shield TV to boot from USB, with approximately equal success.

The specifics:

I have a 64 GB PNY USB 3.0 drive with two partitions; partition 1 is NTFS, for Android and general storage, partition 2 is ext4 and has "Tegra_Linux_Sample-Root-Filesystem_R23.1.1_armhf.tbz2" extracted onto it.

I have also modified my init.c in similar ways to yahoo2016; mine mounts partition 2, has a sleep in case the USB subsystem needs a second to come up, and tries to touch a file (for debugging; in case the drive mounts but then something else fails. It doesn't)

#include <sys/mount.h>
#include <unistd.h>
#include <linux/reboot.h>
#include <fcntl.h>
#include <stdio.h>

extern char **environ;

int main(int argc, char **unused) {
mount("/dev", "/dev", "devtmpfs", 0, NULL);
sleep(1);
mount("/dev/sda2", "/dest", "ext4", 0, NULL);
fclose(fopen("/dest/touchLastBoot", "ab+"));
//mount("/dev/mmcblk1p1", "/dest", "ext4", 0, NULL);
// mount Android system
// mount("/dev/mmcblk0p19", "/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);
}

I think I used the zImage built by the shieldTv_defconfig included in the cm-12.1.tar.gz, but it may have been the defconfig linked alone in the first post. My 1080p monitor came up with "Source out of range", if that helps.

I definitely used the source in cm-21.1.tar.

I have had a bit of success:

The Shiled has booted twice, seemingly at random (I can't reliably reproduce it). Once was last night, and I have no idea what configuration I used. Once was just now, with the configuration described above.

For both boots, the USB was plugged directly into the Shield.

Following one of the suggestions here, I tried booting with a powered USB hub. It did not boot using the same boot.img which worked once before. I haven't pursued this very far.

While booting, if I repeatedly press the num lock and watch the LEDs, it continues going on and off until about a second after boot (Presumably, the "sleep(1)" in my init.c). After this time, the LED on the flash drive is solid (it was previously flashing a bit) and the keyboard LED does not change any more.

Pre-post edit: It just booted again! I am quite confused at this point. The only thing I did differently was I left it in fastboot for the whole time I was writing this post. I don't know what this could have to do with anything, but I am not a wizard... (I am still using fastboot boot boot.img because this isn't really working yet!)

After-post edit: If waiting is the key, which I strongly doubt at this point, 13 minutes does not appear to be enough.
[Shield Android TV General] rxg846zebra:
Sorry for the late reply, I've been occupied with something else.

So what you have posted is basically what I have done yesterday, but I was not able to get SATV to boot from USB that way. I have tried connecting the USB drive to SATV through a self-powered USB Hub, but with no luck. In fact, I am not sure if that would really work, as one of my colleagues pointed out to me, since the power of the downstream slots are controlled by the upstream slot in a USB hub, so if the USB master is not working, connecting through a self-powered USB Hub would not help?

Anyways, having read Sompom's reply, I was curious what would have happened if I too toggle the "Num lock" key on my keyboard during the boot process? So using the same boot.img (e.g. no sleep, no fopen/fclose in init.c), with USB drive connected directly to one USB slot and keyboard connected to another on SATV), I notice there is a short period of time when pressing the "Num lock" key would actually toggle the LED on my KB. What is more interesting is that a particular pattern of presses (I know this sounds ridiculous, it's like doing Morse code, but I have tried several times to confirm that) would actually get the SATV to boot from USB. And here is what I have found:

OnOffOn: FAIL

OnOffOnOff: FAIL

OnOffOnOffOn: FAIL

OnOffOn(Then pause for about 0.5 sec)OffOn: SUCCESS

Basically any sequence of presses would do after the short pause (except for no press).

I don't know what exactly is happening, but I have tried your configuration with USB drive connecting directly to SATV and a keyboard connecting to SATV through a self-powered USB hub and that did not work for me. Furthermore, I was never able to toggle the keyboard LED in this configuration. Do you mind trying to boot without power hub and share what kind of miniSD to USB adapter and power hub you are using?

I don't know if it would help, but I've used your second shieldTv_deconfig file to build my kernel (e.g. with FRAMEBUFFER , DUMMY_CONSOLE and FONT8x8 and FONT_8x16 OFF).

UPDATE: I have just tried booting with miniSD to USB adapter, and it just worked without interference. Random note: if I remove the miniSD while telling the kernel to mount the miniSD slot, it hangs at the "Booting from recovery kernel" screen just like what happened when booting from USB drive.

Thanks.
[Shield Android TV General] yahoo2016:
I used Kingston Class 10 U1 microSD cards with USB adapters similar to the following:

http://www.amazon.com/Kingston-Mobility-Includes-MBLY10G2-32GB/dp/B00519BEQO

I flashed USB version kernel to boot partition of SATV internal emmc and was able to boot from microSD in USB adapter dozens times without USB hub.

The second shieldTv_deconfig file should be used, the first one has issues with some monitors.
[Shield Android TV General] rxg846zebra:
Right, I have tested with a miniSD to USB adapter too and it worked fine. I am wondering if that's an issue with USB 3.0 as Sompom is seeing something similar.