yashsingh1/xdaforums huggingface dataset:
[Shield Android TV General] Slayerkodi:
ok i thought i figured it out but it only booted that first time, i reinstalled to try to get wifi working but it didnt work, it looks like its going to load but then it says it will reboot in 30 seconds and turns off. i have tried to follow the instructions but i dont know where im going wrong. can someone look at this and see what the problem is please. https://pastebin.com/ZTa6C0QE

---------- Post added at 06:53 PM ---------- Previous post was at 06:21 PM ----------

This is whats happening to me https://youtu.be/vNz_QvDx30Q
[Shield Android TV General] yahoo2016:
I did not receive email notification and missed this thread for a while. I do not have SATV 2017 and am wondering what changes of SATV 2017 have made to make older L4T kernel not working. If I know the difference, I could make a new kernel for SATV 2017.
[Shield Android TV General] abdul.malek:
For one, it's using a different DTB, but there shouldn't be any difference between the SATV Pro 2017 and 2015. Similar to Slayerkodi's problem above, you can see in the video that it's looking for the rootfs and not finding it, so my guess is that something's amiss with the init files so the boot images no longer work. May be as simple as recognising the SD or external USB as a different drive.
[Shield Android TV General] yahoo2016:
That's what I thought. As I recall SATA 2017 16GB removed micro SD slot and the DTB could be different.

For Ubuntu to work for SATV 2015, the DTB must be from L4T, which DTB do you use for SATA 2017? What happens if you use DTB from L4T?
[Shield Android TV General] Slayerkodi:
sorry i should have mentioned, i have satv 16gb 2015 on version 5.0 rooted and bootloader unlocked. i have followed many instructions and most of them seem to succeed in the file making but i always get same message after 9 or 10 seconds. and im using 16 usb stick to boot. It did boot for me once and i saw wifi wasnt working so i decided to start again to get wifi working - since then i have not booted once.
[Shield Android TV General] yahoo2016:
Is your L4T rootfs on USB drive, did you use "sda1.img"? Have you replaced DTB from L4T?
[Shield Android TV General] abdul.malek:
For me, yes and yes. I've also tried using the microSD version (mmcblk1p1.img) which also fails. Strange part is that the same microSD/USB rootfs works fine on my 2015 16GB SATV. I'm currently building a recovery image of SATV 1.3 firmware so I can downgrade the 2015 and 2017 Pro first.
[Shield Android TV General] yahoo2016:
Those images were built a while ago and the first post mentioned L4T 24.2, not L4T 24.2.1. Have you tried L4T 24.2 rootfs and DTB instead of L4T 24.2.1?
[Shield Android TV General] abdul.malek:
24.2 rootfs and DTB don't work either, just checked. Just finishing compiling the 1.3 firmware from source, going to rollback the SATV Pro 2015 to 1.3, and then start from there. Possible that the 5.0 firmware has changed something to prevent us from doing this.
[Shield Android TV General] yahoo2016:
I wasn't aware SATVs have been updated to 5.0.

ROM images of 3.x can be downloaded from the following link:

https://developer.nvidia.com/shield-developer-os-images

But it appears downgrade from 5.x to any earlier versions could brick SATVs.
[Shield Android TV General] abdul.malek:
I can confirm 1.3 is a bad idea. Downgrading to 1.3 hardbricked the device, I'll recover it by pulling the drive tomorrow or the day after. Trying out 3.0 later today to see what that does on another SATV Pro I have sitting here.

AA
[Shield Android TV General] Slayerkodi:
ok so i tried L4T 24.2 and L4T 24.2.1, and seem to get the same error so i gave up and thought i would try dual booting - http://www.videomap.it/forum/viewtopic.php?f=25&t=1580&start=410#p3636, i had no luck with this either and the steps are so basic i know nothing went wrong i just get stuck with green nvidia logo no matter how many times i flash the recovery img they provided so im guessin this is something to do with being on 5.1 yet when i read the instructions for installing zulu nougat full android firmware it says "*** You MUST start the procedure with the stock firmware Nougat 5.1 ALREADY installed.

*** Once your Shield TV 2015 has upgraded to stock Nvidia Android TV Nougat, you CANNOT LONGER DOWNGRADE THE BOOTLOADER (blob file) to Marshmallow or older, otherwise you will HARD BRICK your device."

so this is making me think i have no idea what is causing this.

edit: just found this when looking to downgrade .

"Tutorial: Restore to Stock Image (Shield TV 2015)

DO NOT ATTEMPT TO ROLL BACK FROM ANDROID 7 (Nougat) V5.x!! WE HAVE REPORTS OF BRICKS.

This returns your Shield Android TV to “stock” V3.2 with Android 6 (aka Marshmallow)."
[Shield Android TV General] Slayerkodi:
im gonna backup my 1.2tb of adopted storage and flash the full nougat firmware then try again from there following this https://www.youtube.com/watch?v=LQaYb4oVHVc&feature=youtu.be
[Shield Android TV General] yahoo2016:
According to posts by SlayerKodi, downgrade from 5.x to 3.x could also brick SATVs.
[Shield Android TV General] abdul.malek:
I downgraded a 2017 Pro, the downgrade from 5.x to 3.x bricks the device but the bootloader still works, so in theory i could put it back to 5.0. When I downgraded from 5.0 to 1.3, I lost access to fastboot as well. Next steps? Anyone want to share an older working SATV Pro SHDD Image that I can dd?
[Shield Android TV General] yahoo2016:
According to the following thread, SATV Pro can always be unbricked:

https://xdaforums.com/shield-tv/development/nvidia-shield-tv-ssd-t3402580

And link to SHDD image:

https://xdaforums.com/showpost.php?p=67426622&postcount=23
[Shield Android TV General] Slayerkodi:
when you open the sd should you see what you see inside rootfs folder or should you see a rootfs folder with contents

---------- Post added 10th May 2017 at 12:20 AM ---------- Previous post was 9th May 2017 at 11:28 PM ----------

ok no worries all working for me with wifi now, not sure what the issue was before - im thinking maybe the "fastboot -w" command i used to erase data during the wipe must of helped somehow as i followed the same exact steps as i did before i migrated and it just worked. i have disabled wifi for now as i know i read somewhere about ubuntu upgrading itself and messing up and there was a code to prevent this but i cant seem to find it. can anyone post it here if oyu know what im talking about?

edit: realised i dont even have a browser installed, anyone have any commands for installing any browser so i can try surf the net at least lol.
[Shield Android TV General] yahoo2016:
I don't believe Ubuntu will automatically upgrade, it always prompts if you want to upgrade.

For browser, you can use "/usr/bin/chromium-browser". Firefox could be installed but it crashed last time when I tried.
[Shield Android TV General] Slayerkodi:
Thank you for that, much appreciated. When I had chromium opened I tried to pin in to the taskbar but it does not launch from there, is there a way I could make a clickable link so the Mrs doesn't have to use terminal as she's terrible with stuff like that. Also I noticed when viewing YouTube the videos were playing like triple speed and had no audio so changed the audio output to the nvidia one and now I can have sound and the music is playing correctly but I have no video lol is there any way to fix this? I heard about cuda but didn't really read what's its about, does it give you correct drivers or something, is it worth installing? Do I need it?
[Shield Android TV General] ithuestad:
Hello, I have been playing around with the SATV 2017 for a while now and I've managed to run Ubuntu from the SDcard using a USB to SD adapter, but I want to run linux natively from the emmc. For the 2015 model I believe all it took was copying the contents of the sdcard to mmcblk0p29 and then using fastboot to flash the appropriate image file, however the 2017 model won't mount this partition. Its listed in the \dev directory but I'm not really sure what to do next, can I format the mmcblk0p29 partition or is there a different set of instructions to make linux native on the 2017 SATV?
[Shield Android TV General] yahoo2016:
I do not have SATV 2017, for SATV 2015, you boot to Ubuntu on SD card, create a working folder, download rootfs from Nvidia to the working folder, decompress and apply binary, then copy rootfs from working folder to emmc partition using "sudo cp -a [working folder] [emmc mount point] && sync".

You could try format partition partition 29 or use fastboot to erase partition 29.
[Shield Android TV General] MartiniGM:
This is pretty awesome. I own a Shield Pro 2017 edition and now I've copied the filesystem to a Samsung UHS-grade sdcard, placed it into the internal sdcard slot and booted the Shield with your "mmcblk0p1.img" boot image and the system runs Ubuntu soo smooth. Thought "Full Android" was the way to use the Shield, but this is might end up as my prime OS! :good::good::good:
[Shield Android TV General] abdul.malek:
Okay, can confirm it boots fine with one exception. The mmcblk0 doesn't even show up in lsblk on the SATV pro 2017. Possible that the mmc has been removed on the pro? Nothing shows up on lspci.
[Shield Android TV General] yahoo2016:
That's very interesting if SATV Pro 2017 removed emmc.

SATV 2015 Pro and 16GB share the same hardware, e.g., emmc, HDD connector.

It appears SATV 2017 tried to save cost by removing unused components.
[Shield Android TV General] praveenonwww:
Is it possible to downgrade SATV Pro 500GB (2015) from 5.x firmware to 3.x?

I have SATV Pro 500GB (2015) and SATV 16GB ( 2017) with 5.x firmware, I tried using the boot provided in first thread for SATV 16GB ( 2017) with 5.x, it just shown the ubuntu UI but after that it disappear.

Is there any boot image available for 5.x firmware or is there any way to downgrade these devices to 3.x firmware. Thanks
[Shield Android TV General] yahoo2016:
If you have SATV Pro, you should back up your HDD first following this link:

https://xdaforums.com/shield-tv/general/guide-migrate-to-ssd-hdd-size-satv-pro-t3440195

Then you can try down grade using ROM 3.x images from the following link:

https://developer.nvidia.com/shield-developer-os-images

According to the following thread, SATV Pro can always be unbricked:

https://xdaforums.com/shi...v-ssd-t3402580

And link to SHDD image of SATV Pro 2015:

https://xdaforums.com/sho...2&postcount=23
[Shield Android TV General] abdul.malek:
Question, are you also not seeing the internal mmc when you run lsblk on the pro 2017 or do i have something weird going on?
[Shield Android TV General] xkrys:
Does it work with the last Shield TV 2017 ?
[Shield Android TV General] yahoo2016:
I don't have SATV 2017, I'd recommend SATV 2017 Pro which will not brick if you clone the HDD and keep the original HDD.

With HDD backup, you could try downgrade to ROM 3.x and use the images from the OP.

Downgrading SATV 1027 16 GB could brick it. If you brick one SATV 16 GB, it'd be more expensive than SATV Pro.
[Shield Android TV General] Afeld88:
Hello yahoo2016, thank you for your work, First off I was wondering if there is any way to get to a command line from the login screen for ubuntu, had been working fine for weeks as my primary os, flashed to the user data partition of my 2015 emmc 16gb, however a couple of days ago , trying to login to ubuntu gives me failed to start session message in red under the password dialog box, ctrl+alt+f1 only puts shield tv to sleep instead of opening a command line, so I cannot reinstall a broken ubuntu desktop, I have tried several times to enter HW recovery mode with usb plugged into pc as well as otg cable, is there anyway to get a cli or recovery mode via my Linux pc thru an ssh?
[Shield Android TV General] yahoo2016:
You should be able to connect SATV to a PC/laptop using a micro USB to USB cable and hold power button while plug in power until SATV enter recovery mode.
[Shield Android TV General] Afeld88:
Hello yahoo thanks for the quick reply , I have tried that method multiple times, however it just boots up into Linux, however a couple of tries it will briefly show the nvidia splash screen for a split second as if it's trying to enter recovery but continues with boot up to Linux, however when I try to switch from ubuntu username to kodi desktop environment with same password I can boot into kodi, perhaps you have some insight ? Maybe recovery mode is taking longer or Linux has suppressed it? Or maybe there is a way to get to terminal from kodi?
[Shield Android TV General] yahoo2016:
What was your ROM version when you flashed Ubuntu? ROM 3.x should be able to boot to recovery mode reliably using the above method. I did not update my SATVs to 5.x and wasn't aware behavior of ROM 5.x.

It's important to make sure recovery mode always works, otherwise SATV could be bricked.

I have not installed Kodi on SATV. There are ways to add serial console port to SATV by soldering thin wires to some pads. If you want to try it, the photos and instructions should be in this thread or maybe another threads.
[Shield Android TV General] Afeld88:
Yes I was on the upgraded rom to 5.x on a 2015 16gb shield, I had made sure that recovery mode worked and was able to get into it after I installed ubuntu, the whole Linux install is fine and didn't cause any issue this came about out of the blue , kodi had worked prior on ubuntu and still works , I even try to switch to the account named nvidia and I also get failed to start session , but Can boot into kodi from ubuntu login , since I can get into kodi and my boot log is not showing any errors there should be a water me to get to a terminal or task manager to reinstall my ubuntu desktop.is there a way to ssh into a system and command it from my pc?
[Shield Android TV General] yahoo2016:
I consider recovery mode non-working a bug of boot loader. Nvidia screwed up boot loader for ROM version 2.x and caused many bricked SATVs. Nvidia was kind enough to replace my bricked SATV 16GB.

Nvidia seems fixed boot loader bug for ROM version 3.x, but introduced new bug on ROM5.x which couldn't be fixed by downgrading to 3.x.

I recommend contact Nvidia from the following link for boot loader recovery mode bug:

http://www.nvidia.com/object/support.html

It may be a known bug.
[Shield Android TV General] xkrys:
Actually I already got a SATV 16GB 2017 with a 5.x rom.

As of now I did the following:

- unpack L4T rootfs from https://developer.nvidia.com/embedded/dlc/l4t-sample-root-filesystem-24-2-1

- apply binaries

- copy rootfs (cp -a) to a ext4 usb stick

- unlock the shield bootloader

- flash the corresponding dtb from L4T

- enter bootloader with shield controller

- unplug the controller and plug the usb stick instead (usb port near HDMI)

- do a "fastboot boot" with the sda1.img from the OP

No success so far...

I'm stuck on NVIDIA logo. I guess that's because the images from the OP is for 3.x ROM

Any idea what to do from there ?
[Shield Android TV General] yahoo2016:
Can you still boot to recovery mode? From what I read, I believe other users can only boot to Ubuntu after downgrading to ROM 3.x. But downgrading ROM could cause other issues, such as recovery mode not working. I can try to upgrade my SATV 2015 Pro to ROM 5.x and install Ubuntu when I find some time.

I tried but was not able to upgrade my SATV 2015 Pro to ROM 5.1. After downloading 5.1, install, restart, it came back as 3.3. I believe update failed because I have cloned 250GB SSD instead of original 500GB SHDD.
[Shield Android TV General] xkrys:
Yes I can go to recovery mode and after few seconds I got a screen with an opened android robot, a warning icon, and a "No command" message.

---------- Post added at 01:57 PM ---------- Previous post was at 01:46 PM ----------

You were successful booting ubuntu from a SATV 2017 5.x ? 16GB or Pro ?

Did you use the files from the OP ?
[Shield Android TV General] Afeld88:
Okay , update. I have yet to contact nvidia, still haven't gotten into recovery mode but I after attempting to login to console with Ctrl alt f1 I was able to reboot and login via terminal console and have apt -f install and removed kodi and auto removed all other unused packages, however attempting to remove and install ubuntu desktop I am running into issues because this is a custom l4t ubuntu release and not regular ubuntu so the packages/versions shield needs are not the standard commands , so I am trying to install all of the unmet dependencies and also having the same issue of not being able to rebuild the desktop/session/nautilus etc... since the console terminal is available to me is there anything you could suggest ? Is it possible to write the rooted to a sd cars from my ubuntu pc and place in shield and use terminal to copy it from ad to internal again?
[Shield Android TV General] yahoo2016:
You could decompress L4T rootfs to SD card, apply binaries to it and use the same "cp -a && sync" command to copy rootfs from SD card to user data partition (you may need to format user data partition first), but if something goes wrong and you do not have recovery mode working, your SATV could be bricked.
[Shield Android TV General] Afeld88:
As of now I don't have access to recovery, I believe bootloader bug for ROM 5.1 for satv 2015 16gb is to blame, at this point I consider the shield a brick anyway , rebuilding custom aarch64 Linux packages is quite a task, however thinking now I may not be able to cp -a to userdata since I have it already mounted as rootfs , will give it a shot later and keep the group posted.
[Shield Android TV General] yahoo2016:
When you downgraded ROM to 3.x did you use Developer ROMs from the link below?

https://developer.nvidia.com/shield-developer-os-images
[Shield Android TV General] Afeld88:
I did not downgrade , I installed and booted the fully functioning ubuntu on 5.1 firmware
[Shield Android TV General] Afeld88:
update, good news and false alarms, boot loader was accessible after many more tries than usual in different manners, I came to see it was my choice of cord for some reason , I am reinstalling and moving forward , again,the info is a successful installation with a 2015 16gb shield tv with latest firmware 5.1 boot loader working
[Shield Android TV General] ithuestad:
I've been running ubuntu off an SDcard on the 2017 SATV 16gb model but would like to move to the local emmc drive. The user partition appears to be mmcblk0p33 (is this correct?) and if so I don't think there is an image file provided that will run the OS off this partition (assuming this is the route to running Ubuntu natively). Is there a resource where I can find a built image file for this partition, or will I have to make one (i've never made one before so I'm not sure what I would be getting myself into)?
[Shield Android TV General] yahoo2016:
I can make an image for mmcblk0p33 tomorrow.
[Shield Android TV General] yahoo2016:
mmcblk0p33.img can be download from here:

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

Please try it use "sudo fastboot boot mmcblk0p33.img"
[Shield Android TV General] xkrys:
Could explain how did you achieved to boot off an SD Card please ?

I'm also trying to flash L4T on eMMC but I'm wondering how ? Did you successed ?
[Shield Android TV General] ithuestad:
Thank You. It took me a while, but I could only get the image to properly work for L4T 24.2.0

L4T 24.2.1 worked initially, but wouldn't boot after update/upgrade.

I now have a gen 2 shield booting into ubuntu successfully and running code.

thanks again.

---------- Post added at 12:00 PM ---------- Previous post was at 11:48 AM ----------

Hi, there are some great resources in this thread that go through unlocking the bootloader for the shield, using ADB/fastboot, and preparing the L4T sdcard. If you're just getting started I would suggest looking into unlocking the bootloader first. The instructions up to step 3 part 6 in the link ( http://nvidiashieldzone.com/shield-...rial-root-shield-android-tv-2017-16gb-nougat/ ) helped me out immensly before I discovered this forum.
[Shield Android TV General] chtulu:
mmcblk0p29.img" is for booting to rootfs on partition 29

Hi,

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

What does it mean "if only Ubuntu is needed"?

Can all the other 32 partitions be deleted?

Has the mmcblk0p33.img image made for R24.2.1?

Does the image need to be made for each Linux for Tegra version and why?

What change need to be made for each new version?

Also please note that the user data partition on the shield TV 2017 is mmcblk0p33.img.

Thanks.
[Shield Android TV General] yahoo2016:
(1). If "User Data" partition is overwritten, you won't be able to use Android.

(2). Other partitions are small, SATV can be bricked if some other partitions are deleted.

(3). https://xdaforums.com/showpost.php?p=72587978&postcount=523.

(4). Versions of L4T rootfs must match kernel Image.

(5). To use L4T for SATV, kernel configuration file need to be changed to build kernel for SATV.
[Shield Android TV General] chtulu:
Hi,

Thank you very much indeed. So, as far as I understood, the mmcblk0p33.img image, contains the drivers and L4T FileSystem. Is that correct?

Is there any way to just use the eMMC for Linux? 16GB is not much and I would need as much space as possible.

Thanks
[Shield Android TV General] yahoo2016:
All images are kernel only which will boot to rootfs on different devices/partitions.

You need to download L4T rootfs from Nvidia and copy it to different devices/partitions as mentioned in the 1st post.

The User Data partition of 16GB SATV is at least 12GB. If 12GB is not enough, you'd need to use external storage such as SD card/USB drive.

I recommend use SATV Pro for Linux development.
[Shield Android TV General] abdul.malek:
New 28.1 L4T includes a 4.4 kernel. Taking a crack at building kernel from source to boot.
[Shield Android TV General] LM209:
Hello, does anyone have maybe an image for the Shield 2015 16Gb variant and how to do the correct flash on the memory?

Would be very nice
[Shield Android TV General] chtulu:
how to compile the kernel

Hi,

yahoo2016, thank you very much for all the answers.

Could you please let me know how to compiler the kernel and make the boot.img?

Is it ok to use source_release.tbz2 for the source?

Once you got the zImage, how do you get the bootimg.cfg and ramdisk?

Thanks.
[Shield Android TV General] chtulu:
how to compile the kernel

Hi,

Well, I finally found the missing link in your first post, to initrd's tar.

Were do I get from, the values for bootimg.cfg, once I modified the init.c file?

"L4T24.2 dtb from L4T24.2 rootfs "/boot" needs to be flashed".

My dtb is: tegra210-darcy-p2894-0050-a04-00.dtb, but I can not find it in the /boot folder of the rootfs. I have three tegra210-jetson...... files there.

thanks.
[Shield Android TV General] yahoo2016:
The offsets in init.c were from this thread:

https://xdaforums.com/shield-tv/general/ubuntu-utopic-nvidia-shield-tv-t3150352

I only changed rootfs partitions.

Later versions (27.x and 28.x) of L4T may have removed the other dtbs, L4T24.2.x should have dozens of dtbs including dtbs for SATV ("foster") in rootfs/boot after run "apply_binaries.sh".

Also there should be "foster" dtb in "Linux_for_Tegra/kernel/dtb", see link:

https://xdaforums.com/showpost.php?p=64722818&postcount=84
[Shield Android TV General] chtulu:
Hi,

Thanks again.

I'm trying l4t 28.1, so I guess there is no hope for the latest kernel, since there is no dtb.

As for the initrd, I noticed that you have twice the some usb firmware, one in lib/firmware and another in etc/firmware. Is that any reason why? Should it be only in lib/firmware?

Also, in init.c, why /dev is mounted twice? One in /dev/ and one in /dest/dev?

Thanks
[Shield Android TV General] crnkoj:
Is it not so that we can compile the dtb while compiling the kernel?