yashsingh1/xdaforums huggingface dataset:
[Shield Android TV General] emanuelstanciu:
Once again, thanks for all your help [MENTION=7098998]yahoo2016[/MENTION]!

I managed to get it working finally and it was a mix of things.

So, first it was the dtb that was the issue. You image didn't work, so I ruled out the OS.

The dtb in your G Drive is incorrect (at least for me). I tried to flash the dtb from you and from the Android source. This was the mistake. I needed the foster dtb from the rootfs/boot folder. That did the trick and it started to use the screen.

Then I started to do some advanced configuration and updated the OS to Ubuntu 16.04.1 to get all the ubuntu goodies and to have it a bit more speedy. Also changed the unity with LXDE to reduce the resource consumption.

All is good now, thanks a lot for all your effort. What are you using your rig for? Any interesting projects?
[Shield Android TV General] yahoo2016:
Glad you have it working. I just downloaded and checked the dtb, it has md5sum of:

f188fac0358ea123ad0b88f2d66744e7

Dated 05/17/2016. Same as the one I'm using.

What is md5sum of the dtb you downloaded from Gdrive and the one working for you?

Wrong dtb could bricked SATV (at least for ROM after 2.1 and before 3.0). It's always good idea to run md5sum on dtb before it was used.

BTW, I'm still struggling to have console messages displayed on monitor for SATV. For Jetson TX1, many text messages are displayed before Desktop shows up, The rootfs and kernel image are identical for SATV and TX1, it could be differences in dtb or boot loader.
[Shield Android TV General] senselessDev:
[MENTION=7191545]deerish[/MENTION]

One of the pads you have marked and connected on the cable's head is GND. The other one on the head was not probed by me during powerup yet to see if it is a UART pin.

But probably they are the outer ones. I wonder how you figured it out? Is fastboot already printing something so you can start without the IO board connected?

Besides, I'm figuring out what is what on the mainboard pads and the J501 connector. Current status is availabe here.

Another idea i had is to change the dtb to map the uart pins to the left half that is easier accessible. Unfortunatley, I never fiddled around with dtbs so far and hence I guess I will be without success on this one.

Edit: seems that someone already had no luck on dtb uart remapping.
[Shield Android TV General] emanuelstanciu:
I checked both md5 hashes and they do match, but I flashed the other dtb probably 10 times before the one in the boot folder worked. Not entirely sure what happens, I probably should buy another SATV and do that from scratch and see/document if the steps work. Once again, thanks a lot for all your help.
[Shield Android TV General] ahmed68:
hi everybody

I need help from u

that's my work but I cant boot to Linux For Tegra R24.1

sd card sony 64 class 10

sudo fdisk -l

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

sudo mkfs.ext4 /dev/sdx

sudo mkdir /mnt/sdx

sudo mount /dev/sdx /mnt/sdx

cd ../

sudo ./apply_binaries.sh

sudo dd if=l4t24rootfs of=/dev/sdx

sudo dd if=Linux_for_Tegra/rootfs of=/dev/sdx

sudo tar -pxvf Tegra210_Linux_R24.1_armhf.tbz2

sudo tar xpfv ../../Tegra_Linux_Sample-Root-Filesystem_R24.1_armhf.tbz2

sudo rsync -av ~/Linux_for_Tegra/rootfs/* /mnt/sdx

dtb i take it from JetPack 2.2.1 (tegra210-foster-e-hdd-p2530-0932-e02-00.dtb),from yahoo2016 (tegra210-foster-e-p2530-0930-e02-00.dtb). foster-e for 16gb , foster-e-hdd for 500gb.

https://mega.nz/#!d0YBBIgb!0_ubz7FYOfLTkqQNqH7vyb-AE1CUIFPdBwLkO7Oeo80

boot.img i try all but i cant boot (all yah002016,i make by "initrd")

i dont need android how i can replace it with ubuntu

i can backup android any time i make backup.img itest it work for any 500gb hdd

https://mega.nz/#!cshkTToa!llfeAfwT7UOx88-NcTVQkukRChw7Xv4RZCJty90-aeI

plz help
[Shield Android TV General] yahoo2016:
I recommend following the following steps from Nvidia L4T24.1 "Getting Started" to create SD card by first download the following 3 files:

http://developer.nvidia.com/embedded/dlc/l4t-jetson-tx1-driver-package-24-1-64-bit

http://developer.nvidia.com/embedded/dlc/l4t-sample-root-filesystem-24-1-64-bit

http://developer.nvidia.com/embedded/dlc/l4t-documentation-24-1

To extract Tegra Linux Driver Package

•Extract the package manually by executing the following command:

$ sudo tar -vxjf Tegra210_Linux_R24.1.0_aarch64.tbz2

2. Extract the compressed rootfs as follows:

•Navigate to the rootfs directory of the extracted NVIDIA driver package with this command:

$ cd Linux_for_Tegra/rootfs

$ sudo tar jxpf ../../Tegra_Linux_Sample-Root-Filesystem_R24.1.0_aarch64.tbz2

3. Run the apply_binaries.sh script to copy the NVIDIA user space libraries into the target file system:

$ cd ..

$ sudo ./apply_binaries.sh

To copy the file system to an external storage device (e.g., /dev/mmcblk0p1)

1. If your device is not formatted as Ext4, enter the following command to format it with an Ext4 file system:

$ sudo mkfs.ext4 /dev/mmcblk0p1

2. If needed, mount your device with the following command:

$ sudo mount /dev/mmcblk0p1 /mnt

2. copy the rootfs directory that is included in the release by executing the following commands from <your_L4T_root>/Linux_for_Tegra/:

$ cd rootfs

$ sudo cp -a * /mnt && sync

6. After copying the content to the external disk or device, unmount the disk and connect it to the target Tegra device.

The next step is to replace dtb, it's important to make sure you have SATV ROM 3.x and above. Assuming you have 16GB SATV, you should use "tegra210-foster-e-p2530-0930-e02-00.dtb" dated 05/17/2016 in L4T24.1 and run md5sum:

md5sum tegra210-foster-e-p2530-0930-e02-00.dtb

It should have md5sum:

f188fac0358ea123ad0b88f2d66744e7

Put rooted SATV in recovery mode and run:

sudo fastboot flash dtb tegra210-foster-e-p2530-0930-e02-00

Before you build your boot.img you can try my boot.img from the following link:

http://xdaforums.com/showpost.php?p=67433510&postcount=249
[Shield Android TV General] yahoo2016:
You have done and documented very impressive reverse engineering. May be it's possible to build traces out the outer 2 pads (Y10/Y11) which are most likely the TD/RD pins of UART using the following pen:

http://www.mcmelectronics.com/product/20-4930?green=D578E2D4-63AB-56E7-BE94-CA97D24BD086
[Shield Android TV General] ahmed68:
dear yahoo2016

I do all and use your boot.img from

http://xdaforums.com/showpost.php?p=67433510&postcount=249[/QUOTE]

but I cant boot black screen then goto android.

when I flash dtb with (tegra210-foster-e-p2530-0930-e02-00.dtb) the shield cant boot at all

I think its for shield 16gb but I have 500gb (foster-e/foster-e-hdd)

---------- Post added at 09:38 PM ---------- Previous post was at 09:34 PM ----------

dear emanuelstanciu

wish dtb and boot img you use to boot (rootfs/boot) I take it but I cant boot
[Shield Android TV General] yahoo2016:
I only have 16GB SATV. To install Linux on SATV Pro may need different approach. I can think about it but I do not have Pro to try.
[Shield Android TV General] ahmed68:
thank you very much for help , if i can make it boot i will inform you
[Shield Android TV General] yahoo2016:
Since you have SATV Pro, did you use the dtb with dm5sum:

02fa295091e044d276bb998c2b5c9c04 tegra210-foster-e-hdd-p2530-0932-e02-00.dtb

When you boot to Andriod, can you check if SD card shows as /dev/mmcblk0p1?

Have you tried:

sudo fastboot boot boot.img?
[Shield Android TV General] ahmed68:
dear yahoo2016

can you tel me how to make SD card /dev/mmcblk0p1

the original (nv-recovery-image-shield-atv-pro-3.2.0-dev_rooted) dtb have dm5sum: c2d642581c733e00b1eebdae08024ae2

I take dtb from l4t/boot/tegra210-foster-e-hdd-p2530-0932-e02-00.dtb have dm5sm:02fa295091e044d276bb998c2b5c9c04

today I try boot-hypriot-shieldtv.img + sd-card-nvidia-shieldtv.img ver0.9 its work only for hypriot OS
[Shield Android TV General] yahoo2016:
In my previous post, I should say:

When you boot to Android, can you check if SD card shows as /dev/mmcblk1p1?

(/dev/mmcblk0 is 16GB SATV internal emmc). I'm not sure external SD card on SATV Pro shows as /dev/mmcblk0p1 or /dev/mmcblk1p1)

My laptops have SD card slots and the first partition show as "/dev/mmcblk0p1". rootfs should be on partition 1.

From your first post:

It seems you put SD card in SD card to USB adapter but you did not have partition 1, In your case, the first partition should be "/dev/sdx1". Partition 1 on SATV should show as "/dev/mmcblk1p1".

Under Ubuntu, I used "gparted" to create partition 1.
[Shield Android TV General] yahoo2016:
I tried to probe Y10 and Y11 pins in your drawing by soldering 2 very thin wires to them, neither showed UART data while boot to Android or Ubuntu.

Then I noticed deerish has different PCB, his PCB does not have Column Y!!! (see attached from deerish's original post and from your link). Deerish's PCB has only one hole for screw and it's on the other side of the PCB.

So Y10/Y11 may no be UART pins.
[Shield Android TV General] senselessDev:
I have found UART TX pin: It is Y9 in my counting. Unfortunatley, 1.8V UART - no adapter for this voltage here atm. Therefore probing it with the scope and transferring to the pc -> sigrok to decode. Thats what I'm currently trying.

I'll check deerish's pic soon

Edit: Hmm, very strange, that his UART was also around there when he has another pinout. I guess his spring-contact-header must be another one, too. [MENTION=7191545]deerish[/MENTION] was your shield one of the first ones available? I guess my version is the newer one, because I bought it in February this year.

Edit2: It seems to be 115200 8N1 by the way.
[Shield Android TV General] senselessDev:
Finally, I got the scope -> SCPI -> csv -> sigrok-cli chain up and running.

I have attached the first few lines of the booting process (generated from over 20 MPoints of scope data; for everthing of the boot process i have to sample slower; have to figure out how slow).
[Shield Android TV General] yahoo2016:
Great, I'll try Y9.

I got mine last December and have the same PCB as yours.
[Shield Android TV General] senselessDev:
I have uploaded a longer boot process to the git repo https://github.com/senselessDev/shield-android-tv-reverse-engineered/tree/uart-exploration/uart
[Shield Android TV General] yahoo2016:
I was able to solder a thin wire to Y9, re-attached the cable and boot to Android. The signal level was about 2v at Y9, so I tried 3V IO CP2103 UART to USB converter with 1K resister in serial for safety. It worked, see attached log from putty. I believe most 3V UART to USB converter should be able to receive signal from 1.8V UART. To drive 1.8V UART receiver from 3V UART transmitter, protection resister can be used (e.g 1K resister to limit current to few mA).
[Shield Android TV General] ahmed68:
mmcblk1p1 or mmcblk0p1
[Shield Android TV General] ahmed68:
dear emanuelstanciu

wish dtb and boot img you use to boot (rootfs/boot) I take it but I cant boot
[Shield Android TV General] anchung.chen:
Dear yahoo2016 : Great work. Would you post a picture of showing the "solder a thin wire to Y9, re-attached the cable" ? I would like to follow your work on my bricked shield TV (blank screen after upgrade .dtb from v 1.4) to access u-boot.

Thank you very much.
[Shield Android TV General] ahmed68:
Dear yahoo2016

thanks a lot, thank you very much, all right now, i boot to Ubuntu and its update to 16.04 , the problem in sd parted , I do the next:

1.sudo fdisk -l

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

sudo mkfs.ext4 /dev/sdx1

sudo mkdir /mnt/mmcblk0p1

sudo mount /dev/sdx1 /mmcblk0p1

cd Linux_for_Tegra/rootfs

2.sudo cp -a * /mnt/mmcblk0p1 && sync

3.fastboot flash dtb tegra210-foster-e-hdd-p2530-0932-e02-00.dtb(I take it from L4T/rootfs/boot)

4.fastboot flash boot boot.img (satvL4t24.tar.gz , your build has been the best)

now its work and update thank you very much for your great work and support.

have any chance to move rootfs from sd card to hdd ,I don't need any android.

thank you very much
[Shield Android TV General] yahoo2016:
I took a photo (attched) when I soldered wires on Y10 and Y11 according to deerish's photo, the wire on Y11 should be on Y9. I have not tested Y10.

In order to re-attach the cable, the wires and solder must be very thin.

Please post your progress on uboot. I did try "uboot-dtb.bin" for Jetson TX1, but it did not work for SATV (I tried "fastboot boot uboot-dtb.bin").
[Shield Android TV General] yahoo2016:
Glad it's working. I saw your first post you did not have partition 1.

Which partition do you want to put rootfs? I can make a boot.img to boot to that partition.
[Shield Android TV General] ahmed68:
dear yahoo2016

when I scan sshd by TestDisk & PhotoRec I see

1. boot sda21

2. system sda22

3. cache sda23

4. data 32

I don't see any mmcblk1p1 or mmcblk0p1 but they work only with rootfs=system sda22=mmcblk0p1

or you can see the original boot.img for shield pro.

if you can make the boot.img it well greet.
[Shield Android TV General] yahoo2016:
When you boot to ubuntu or adb shell, can you do "df -h" and show the results?

I currently have only 2 "boot.img", one for external SD card "/dec/mmcblk1p1" and one for external USB drive of 16GB SATV "/dev/sda1".

It seems for SATV Pro, you have partitions "/dev/sda2x", after you do "df -h", you can decide which partition to use and I can make a new "boot.img".
[Shield Android TV General] ahmed68:
dear yahoo2016

I boot to Ubuntu and run "df -h", the sd card see "/dev/mmcblk1p1

https://mega.nz/#!Yt5DEbYA!eBRt9AvFl5yJwkERuYAuNBivdOkycShC8baU2X5iZ_A

https://mega.nz/#!Z8QziS6R!ffGYbmlTIKYMoM1ULEcd_vi9jRhCbYi6G8nVzXvqSCM

https://mega.nz/#!swhS3Q5L!jriQqxc-S-GQbrSQOzhnC7C_zuQjBnVB9TUa12sx5Fk

https://mega.nz/#!88IS2T7B!IUJc1aI4yRul4AprfpjWYVSsqkTqiOrEeAGBEy2zfWc

https://mega.nz/#!xgAHzBrD!FHSbfqglAUec9rn_5dqJrqFkjKb0EjqoQMUX3r8BzSo
[Shield Android TV General] yahoo2016:
I'm surprised that hard disc did not show in your "df -h", did you include everything from "df -h".

I did "df -h" on my 16GB SATV and it showed internal emmc ("/dev/mmcblk0px") and external SD card ("/dev/mmcblk1px")..

You can also boot to Android and use "adb shell df" from a PC connected to SATV using a OTG cable to find hard disc partitions, e.g., on my 16 GB SATV, I got:
[Shield Android TV General] anchung.chen:
Dear yahoo2016:

In post #286, you said "Flash Wrong dtb could bricked SATV (at least for ROM after 2.1 and before 3.0)", Does this mean fastboot mode is unreachable even by using Hardware power-on method ? I am really worry to brick the SATV again. And how about Flash wrong dtb with ROM 3.x ? Thanks for all your help !!!
[Shield Android TV General] yahoo2016:
I have read several posts that owners of SATVs bricked their pre 3.x SATVs by flashing wrong dtbs. There are so many posts on this and other forums that SATVs were bricked by updating SW(ROM) before ROM 3.x, I bricked mine too.

I have been very careful about replacing dtbs, other owners replaced 3.x dtbs with L4T24.1 dtb before I did.

It seems Nvidia fixed bootloader bug and Hardware recovery mode for ROM 3.x worked more reliably.

SATV 3.x owners (such as ahmed68) even flashed SATV Pro 3.x with the wrong L4T24.1 dtb for 16GB SATV, it'd brick SATV for ROM 2.x.

The above are only I read from the forums. There are always risks for bricking SATVs.
[Shield Android TV General] ahmed68:
root@ahmed-Z97-HD3:~# adb shell df

* daemon not running. starting it now on port 5037 *

* daemon started successfully *

Filesystem Size Used Free Blksize

/dev 1.4G 64.0K 1.4G 4096

/sys/fs/cgroup 1.4G 12.0K 1.4G 4096

/mnt 1.4G 0.0K 1.4G 4096

/system 1.9G 1.6G 361.1M 4096

/cache 248.0M 316.0K 247.7M 4096

/vendor 743.9M 259.0M 484.9M 4096

/data 455.1G 1.5G 453.6G 4096

/storage 1.4G 0.0K 1.4G 4096

/factory/wifi_config 3.9M 56.0K 3.8M 4096

/mnt/factory 11.7M 64.0K 11.7M 4096

root@ahmed-Z97-HD3:~#

but i cant see sd card
[Shield Android TV General] praveenonwww:
[MENTION=7098998]yahoo2016[/MENTION] Thanks for the info.

I am try to put the root file system on the ShieldTV 16GB internal partition

I can modified the Kernel init.c to point the root to specified location in below code.

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

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

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"); // 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"

}

But I am not getting the way to flash the specific partition. Running fastboot is failing.

Can you please let me know how can I flash the ubuntu filesyetem to Shield Android internal partition.
[Shield Android TV General] yahoo2016:
If you don't need Android, you could use 12 GB partition 29 (User data) for rootfs.

I have not tried, but when you boot SATV to Ubuntu, can you mount /dev/mmcblk0p29 to /mnt and use the "sudo cp -a" to copy rootfs to partition 29?

Have you tried to flash compressed rootfs by:

"sudo fastboot flash usersdata rootfs"

Some kernels will take compressed rootfs. SATV may use "sudo fastboot flash system .." to flash compressed Android rootfs to system partition.
[Shield Android TV General] yahoo2016:
That's correct. Under Linux, it should be "/dev/sda32".

Will you be able to regenerate "boot.img" by replacing "/dev/mmcblk1p1" with "/dev/sda32" in "intc.c" ?

I'm at work, if you have issues to generate "boot.img" for "/dev/sda32", I can do it after work.
[Shield Android TV General] hallydamaster:
According to this output, I think the internal EMMC on the Pro should be mounted under /dev/mmcblk0

The EMMC is just empty, so it would be a perfect place to have the rootfs wouldn't it?

Just wondering if you could build a boot.img that point to that?

[IMG="SATV ls -al output"]https://i.imgsafe.org/4612d9a668.png[/IMG]
[Shield Android TV General] yahoo2016:
I don't have SATV Pro to try. If someone with SATV Pro is interested to try and make a partition on EMMC (e.g., mmcblk0p1) I can make a boot.img for it.

I'm not sure if fastboot can access EMMC of SATV Pro, boot to Ubuntu on SD may be needed to copy rootfs to EMMC of SATV Pro.
[Shield Android TV General] hallydamaster:
I was thinking of trying with DD on the SATV booted into TWRP, it has a terminal built into the recovery. So if you want me to try, I am up for it.

I don't have a jetpack environment running though, but do you think it would work with the prebuilt hypriot image?:

https://github.com/hypriot/image-builder-nvidia-shieldtv/releases

Otherwise I would be happy to try if someone has a prebuilt L4T image I could use.
[Shield Android TV General] praveenonwww:
[MENTION=7098998]yahoo2016[/MENTION] I tried flashing the rootfs in userdata of SATV 16GB.

====================================================

fastboot flash userdata TEST.img

target reported max download size of 67108864 bytes

Invalid sparse file format at header magi

erasing 'userdata'...

OKAY [ 3.270s]

...

writing 'userdata'...

OKAY [ 0.107s]

finished. total time: 175.195s

====================================================

Then I modified the boot.image with init.c

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

but still it is not booting when I ran the command

fastboot boot boot.img

Any pointer to verify.
[Shield Android TV General] yahoo2016:
I'm planning to generate multiple boot images this weekend for:

/dev/mmcblk1p1 (SD)

/dev/sda1 (USB drive)

/dev/mmcblk0p29 (User Data of 16GB SATV)

/dev/sdaxx (HDD Partition of SATV Pro)

/dev/mmcblk0axx (EMMC Partition of SATV Pro)

I have not tested rootfs other than L4T.
[Shield Android TV General] hallydamaster:
I'll just keep an eye out for the boot.img. Then try if anything works. :)
[Shield Android TV General] yahoo2016:
How did you generate "test.img". Have you tried to copy "test.img" to SD card and use my "boot.img"?

Have you tried copy L4T rootfs to ubuntu on SD card apply binary drivers. mount /dev/mmcblk0p29" on "/mnt" and use "sudo cp -a" to copy roofs to mmcblk0p29? You should erase mmcblk0p29 first.

You may refer to steps in the following link but on SATV Ubuntu instead of host PC, use mmcblk0p29 instead of mmcblk0p1:

http://xdaforums.com/showpost.php?p=67956659&postcount=290
[Shield Android TV General] praveenonwww:
I used dd to generate the test.img from sd card image.

I used fastboot to flash the test.img.

After from modified boot.img it was going to black screen after NVIDIA logo screen

Just I am able to login to the box using remote ssh. But UI is not coming, I will create new rootfs. However the same rootfs in sdcard is booting in UI.
[Shield Android TV General] yahoo2016:
May be the problem is "dd". What's the size of your SD? If the size of SD card (mmcblk1p1) is different from mmcblk0p29, the copy may not be correct.
[Shield Android TV General] ahmed68:
hi all

anybody try this

https://duo3d.com/Docs/install-arm#NVIDIAJetsonTX1

and

https://duo3d.com/Docs/install-arm

and

http://elinux.org/Jetson/TX1_Cloning
[Shield Android TV General] yahoo2016:
I have 5 boot images in the following link with device name as part of the file name, for SD, USB, Internal EMMC, and internal HDD, e.g.,

boot_mmcblk1p1.img for SD card.

boot_sda1.img for USB drive.

boot_mmcblk0p29.img for User Data partition of internal EMMC of 16GB SATV.

boot_mmcblk0p1.img for internal EMMC of SATV Pro (not verified).

boot_sda32.img for internal HDD of SATV Pro(not verified).

I tested boot_mmcblk1p1.img (SD), boot_sda1.img (USB) and boot_mmcblk0p29.img (User Data partition of internal EMMC) on my SATV.

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

To install a clean copy of L4T rootfs on internal EMMC, I used similar approach described in the following link:

http://xdaforums.com/showpost.php?p=67956659&postcount=290

but used Ubuntu on SD in the same SATV to copy rootfs to mounted /dev/mmcblk0p29.

To clone rootfs on SD to internal EMMC or HDD, the following should work, e.g., for User Data partition of 16GB SATV:

(1). sudo mkfs.ext4 /dev/mmcblk0p29 (clean User Data partition on EMMC)

(2). sudo mount /dev/mmcblk0p29 /mnt (mount User Data Partition on EMMC to /mnt)

(3). cd / (Change to root directory of Ubuntu on SD).

(4). sudo cp -a * /mnt && sync (copy rootfs to User Data Partition on EMMC).
[Shield Android TV General] ahmed68:
today I try

boot_mmcblk1p1.img for SD card. its work

I cant clone rootfs from SD to internal EMMC or HDD the sshd non readed

soon I wont to test boot_mmcblk0p1.img and boot_sda32.img

yahoo2016 thank you so much for your support
[Shield Android TV General] yahoo2016:
Since SD card is working, I recommend boot to SD card Ubuntu and clone rootfs on SD to internal HDD:

(1). sudo mkfs.ext4 /dev/sda32 (clean User Data partition on HDD)

(2). sudo mount /dev/sda32 /mnt (mount User Data Partition on HDD to /mnt)

(3). cd / (Change to root directory of Ubuntu on SD).

(4). sudo cp -a * /mnt && sync (copy rootfs to User Data Partition on HDD).
[Shield Android TV General] ahmed68:
I try but he see only sda one part 500gb
[Shield Android TV General] yahoo2016:
You may want to keep your 500GB SATV HDD and replace it with another HDD (e.g., SSD) and use "parted" or "gparted" to create partitions you like.

If the HDD is "sda", you can create partition 1 for rootfs and use "boot_sda1.img".
[Shield Android TV General] ahmed68:
because i keep only one part boot and dtb all other I erase it . I well backup it and try

fastboot erase cache

fastboot erase recovery

fastboot erase system

fastboot erase vendor

fastboot erase userdata
[Shield Android TV General] ahmed68:
dear yahoo2016

if I replace hdd with other how I can to boot In fastboot to flash boot.img and dtb.
[Shield Android TV General] yahoo2016:
I don't have SATV Pro. You can follow this llink:

http://xdaforums.com/shield-tv/development/nvidia-shield-tv-ssd-t3402580
[Shield Android TV General] yahoo2016:
How did you find you have "only sda one part 500gb"?

Did you try "ls /dev/sd*" ?