Boot from SD

[BeReal]

Should have mentioned #5 also
Yep answer is also here read number #21....
Also the type of card you use may have some effect message number #2

Its all new and just found recently (less than 24 hours) at the time of writing
Give it a week or so but it is looking good
Real good..

Cheers

Thank you again! Much appreciated
I'll definitely be going out to make a purchase on a speedy SD card.
Hopefully things stay looking good,...real good lol.

Cheers

[blinkone]

Hey, thanks for the reply, I appreciate it. I read msg #4

"Arrr This has got my attention!! So are you saying that i could flash a rom to a sd card by selecting (Startup) instead of (Product) & once its inserted in to the draco it will boot from sd card :-) leaving the orignal system rom intact on the device..so if i was to eject the sd card it will then boot the orignal system rom..Or have i miss understood you."

I hope the one I have quoted was the one you were referring to, if not I'm sorry. But I was basically wondering if things like booting up, or read and write speeds would be slower due to the SD card?

Thanks Again

The only speed difference i notice is the boot up speed it is about 8 seconds quicker booting from the sd card,Games play fine with no lag films are playing fine too, i am using a 32GB class 10 samsung evo sd card....Stock rom still intact on my system & finless rom on my sd card, i love this set up i cant find a down side

[geekbuying]

anyone see this ?

http://www.armtvtech.com/armtvtechforum/viewtopic.php?f=578&t=79707

[no_spam_for_me]

anyone see this ?

http://www.armtvtech.com/armtvtechfo...?f=578&t=79707

Do you read this thread

[no_spam_for_me]

:
First I was using the sdk and finally got it to build properly, and packed it into a livesuit image. I used phoenixcard to burn the sdk linux image in startup mode and it was successful!

I went further and unpacked the image from the sdk and the 20141230 ubuntu image. I figured out that by swapping the little rootfs.fex and rootfs.fex.iso from the sdk image to the 20141230 ubuntu image that it would burn. So I imagine it is a problem with partitioning and the size of the rootfs.
At the point the 8GB card I made would boot only to the splash screen and the kernel image.
I read through the .fex files with a hex editor and found that the rootfs.fex is written to the 7th partition, so I used dd to write rootfs.fex to /dev/sdb7. Now it boots from my sd card.
:
I've also been experimenting with other ways to boot from the sd card.
So far I've figured out where to write boot0_sdcard.fex and u-boot.fex, but I'm still working on where everything else goes, but it can at least boot to the first splash screen.

I try to understand what you have done!

If I unpack the 'sun9iw1p1_ubuntu_jaws_p1.img' (Tronsmart_Draco_AW80_ubuntu_20141230) I get

       141.658 aultls32.fex
       155.026 aultools.fex
     5.340.280 boot.fex
        32.768 boot0_nand.fex
        32.768 boot0_sdcard.fex
     7.732.224 bootloader.fex
         1.770 cardscript.fex
        81.920 cardtool.fex
        59.460 config.fex
        16.384 dlinfo.fex
       131.072 env.fex
        14.656 fes1.fex
         2.584 image.cfg
 1.862.270.976 rootfs.fex
           512 split_xxxx.fex
        65.536 sunxi_mbr.fex
        80.064 sys_config.fex
         2.688 sys_partition.fex
       901.120 u-boot.fex
       132.608 usbtool.fex
             4 Vboot.fex
             4 Vbootloader.fex
             4 Venv.fex
             4 Vrootfs.fex
<DIR>          _iso

<DIR> _iso

       7.732.224 bootloader.fex.iso
   1.862.270.976 rootfs.fex.iso

I can't find s little rootfs.fex, only the big rootfs.fex ("1.862.270.976 rootfs.fex" which is the rootfs.fex.iso)...

:
swapping the little rootfs.fex and rootfs.fex.iso from the sdk image to the 20141230 ubuntu image
:

So which fex's do you replace?

:
I read through the .fex files with a hex editor and found that the rootfs.fex is written to the 7th partition, so I used dd to write rootfs.fex to /dev/sdb7. Now it boots from my sd card.
:

How do you get partition 7 ?
By running PhoenixCard 3.1.0 (Startup !) with an Android.img? Or the sdk linux image?

---

---

If I take a clean fresh card and have a look at it with WinHEX:

Name              Size       1st sector    
(Root directory)  4,0 KB            30.120     
Idle space                       
Free space        7,3 GB         
Boot sector      19,0 KB                 0     
FAT 1             7,3 MB                38     
FAT 2             7,3 MB         15.079   
Volume slack      0,5 KB         15.431.616

000000000   EB 58 90 4D 53 44 4F 53  35 2E 30 00 02 08 26 00   ëXMSDOS5.0   &
000000010   02 00 00 00 00 F8 00 00  3F 00 FF 00 3F 00 00 00        ø  ? ÿ ?   
000000020   C1 77 EB 00 C1 3A 00 00  00 00 00 00 02 00 00 00   Áwë Á:          
000000030   01 00 06 00 00 00 00 00  00 00 00 00 00 00 00 00                  
000000040   00 00 29 27 07 7A 5C 4E  4F 20 4E 41 4D 45 20 20     )' z\NO NAME 
000000050   20 20 46 41 54 33 32 20  20 20 33 C9 8E D1 BC F4     FAT32   3ɎѼô
000000060   7B 8E C1 8E D9 BD 00 7C  88 4E 02 8A 56 40 B4 08   {ŽÁŽÙ½ |ˆN ŠV@´
000000070   CD 13 73 05 B9 FF FF 8A  F1 66 0F B6 C6 40 66 0F   Í s ¹ÿÿŠñf ¶Æ@f 
000000080   B6 D1 80 E2 3F F7 E2 86  CD C0 ED 06 41 66 0F B7   ¶Ñ€â?÷â†ÍÀí Af ·
000000090   C9 66 F7 E1 66 89 46 F8  83 7E 16 00 75 38 83 7E   Éf÷áf‰Føƒ~  u8ƒ~
0000000A0   2A 00 77 32 66 8B 46 1C  66 83 C0 0C BB 00 80 B9   * w2f‹F fƒÀ » €¹
0000000B0   01 00 E8 2B 00 E9 48 03  A0 FA 7D B4 7D 8B F0 AC     è+ éH  ú}´}‹ð¬
0000000C0   84 C0 74 17 3C FF 74 09  B4 0E BB 07 00 CD 10 EB   „Àt <ÿt ´ »  Í ë
0000000D0   EE A0 FB 7D EB E5 A0 F9  7D EB E0 98 CD 16 CD 19   î û}ëå ù}ëà˜Í Í
0000000E0   66 60 66 3B 46 F8 0F 82  4A 00 66 6A 00 66 50 06   f`f;Fø ‚J fj fP 
0000000F0   53 66 68 10 00 01 00 80  7E 02 00 0F 85 20 00 B4   Sfh    €~   …  ´
000000100   41 BB AA 55 8A 56 40 CD  13 0F 82 1C 00 81 FB 55   A»ªUŠV@Í  ‚  ûU
000000110   AA 0F 85 14 00 F6 C1 01  0F 84 0D 00 FE 46 02 B4   ª …  öÁ  „  þF ´
000000120   42 8A 56 40 8B F4 CD 13  B0 F9 66 58 66 58 66 58   BŠV@‹ôÍ °ùfXfXfX
000000130   66 58 EB 2A 66 33 D2 66  0F B7 4E 18 66 F7 F1 FE   fXë*f3Òf ·N f÷ñþ
000000140   C2 8A CA 66 8B D0 66 C1  EA 10 F7 76 1A 86 D6 8A   ŠÊf‹ÐfÁê ÷v †ÖŠ
000000150   56 40 8A E8 C0 E4 06 0A  CC B8 01 02 CD 13 66 61   V@ŠèÀä  Ì¸  Í fa
000000160   0F 82 54 FF 81 C3 00 02  66 40 49 0F 85 71 FF C3    ‚TÿÃ  f@I …qÿÃ
000000170   4E 54 4C 44 52 20 20 20  20 20 20 00 00 00 00 00   NTLDR

After PhoenixCard 3.1.0 (Product)
Because WinHEX isn't able to determine the FileSystem I'm searching for 'MSDOS5.0'

Offset       0  1  2  3  4  5  6  7   8  9  A  B  C  D  E  F
02E5031F0   CD CD CD CD CD CD CD CD  CD CD CD CD CD CD CD CD   ÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍ
02E503200   EB 3C 90 4D 53 44 4F 53  35 2E 30 00 02 08 20 00   ë<MSDOS5.0    
02E503210   02 00 00 00 00 F0 00 00  00 00 00 00 00 00 00 00        ð         
02E503220   A7 47 D4 00 05 35 00 00  00 00 00 00 02 00 00 00   §GÔ  5         
02E503230   01 00 06 00 00 00 00 00  00 00 00 00 00 00 00 00                  
02E503240   80 00 29 6F 00 00 00 20  20 20 20 20 20 20 20 20   € )o           
02E503250   20 20 46 41 54 33 32 20  20 20 00 00 00 00 00 00     FAT32         
02E503260   00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00

=> in front of the MBR
=> At Linux sdb and sdb1 (the FAT32 partition)


After PhoenixCard 3.1.0 (Startup !)
Because windows want to format it and WinHEX isn't able to determine the FileSystem I'm also searching for 'MSDOS5.0' and what a surprise, I find it

Offset       0  1  2  3  4  5  6  7   8  9  A  B  C  D  E  F
066EF4FF0   00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00                  
066EF5000   EB 3C 90 4D 53 44 4F 53  35 2E 30 00 02 08 20 00   ë<MSDOS5.0    
066EF5010   02 00 00 00 00 F0 00 00  00 00 00 00 00 00 00 00        ð          
066EF5020   FF CF A0 00 2A 28 00 00  00 00 00 00 02 00 00 00   ÿÏ  *(          
066EF5030   01 00 06 00 00 00 00 00  00 00 00 00 00 00 00 00                   
066EF5040   80 00 29 6F 00 00 00 20  20 20 20 20 20 20 20 20   € )o            
066EF5050   20 20 46 41 54 33 32 20  20 20 00 00 00 00 00 00     FAT32

=> at a much more higher offset (so maybe out of the range where Errorssoft like to look)

I'm using Linux to have a look at the SD...
sudo fdisk -l
=>

Disk /dev/sdb: 7901 MB, 7901020160 bytes
1 heads, 62 sectors/track, 248898 cylinders, total 15431680 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000
 
   Device Boot      Start         End      Blocks   Id  System
/dev/sdb1         4890624    15429630     5269503+   b  W95 FAT32
/dev/sdb2   *       73728      106495       16384    6  FAT16
/dev/sdb3               1     4890624     2445312   85  Linux extended
/dev/sdb5          106496      139263       16384   83  Linux
/dev/sdb6          139264      172031       16384   83  Linux
/dev/sdb7          172032     1744895      786432   83  Linux
/dev/sdb8         1744896     1777663       16384   83  Linux
/dev/sdb9         1777664     1843199       32768   83  Linux
/dev/sdb10        1843200     3416063      786432   83  Linux
/dev/sdb11        3416064     3448831       16384   83  Linux
/dev/sdb12        3448832     3481599       16384   83  Linux
/dev/sdb13        3481600     3547135       32768   83  Linux
/dev/sdb14        3547136     3579903       16384   83  Linux
/dev/sdb15        3579904     4890623      655360   83  Linux

=> a lot of partitions

sudo cfdisk /dev/sdb

FATAL ERROR: Bad primary partition 3:
Press any key to exit cfdisk

because 1 and 2 are ok
sudo cfdisk /dev/sdb3

FATAL ERROR: Bad primary partition 1: Partition begins after end-of-disk
Press any key to exit cfdisk

(4 => doesn't exist)
5 => "Unknown partition table type" at cfdisk
6-15 = no errors at cfdisk....

So I placed it at the Draco, give it some minutes (maybe 5) and will see what happen back at Linux...

Also 1..15 and the same at cfdisk but some automounts
mount

:
/dev/sdb11 on /media/ich/PRIVATE type vfat (rw,nosuid,nodev,uid=1000,gid=1000,shortname=mixed,dmask=0077,utf8=1,showexec,flush,uhelper=udisks2)
/dev/sdb2 on /media/ich/Volumn type vfat (rw,nosuid,nodev,uid=1000,gid=1000,shortname=mixed,dmask=0077,utf8=1,showexec,flush,uhelper=udisks2)
/dev/sdb12 on /media/ich/FE38-08B2 type vfat (rw,nosuid,nodev,uid=1000,gid=1000,shortname=mixed,dmask=0077,utf8=1,showexec,flush,uhelper=udisks2)

ich@ich-VirtualBox:~$ ls -al /media/ich/PRIVATE
total 12
drwx------  3 ich  ich  4096 Jan  1  1970 .
drwxr-x---+ 5 root root 4096 Jan  7 13:22 ..
drwx------  2 ich  ich  4096 Jan  1  1980 LOST.DIR
ich@ich-VirtualBox:~$ ls -al /media/ich/Volumn
total 4318
drwx------  4 ich  ich    16384 Jan  1  1970 .
drwxr-x---+ 5 root root    4096 Jan  7 13:22 ..
drwx------  2 ich  ich     2048 Jan  1  1980 bat
-rw-r--r--  1 ich  ich  3686454 Jan  1  1980 bootlogo.bmp
-rw-r--r--  1 ich  ich        8 Jan  1  1980 config.fex
-rw-r--r--  1 ich  ich   344813 Jan  1  1980 font24.sft
-rw-r--r--  1 ich  ich   357443 Jan  1  1980 font32.sft
drwx------  2 ich  ich     2048 Jan  1  1980 LOST.DIR
-rw-r--r--  1 ich  ich      512 Jan  1  1980 magic.bin
ich@ich-VirtualBox:~$ ls -al /media/ich/FE38-08B2
total 22
drwx------  3 ich  ich  16384 Jan  1  1970 .
drwxr-x---+ 5 root root  4096 Jan  7 13:22 ..
drwx------  2 ich  ich   2048 Jan  1  1980 LOST.DIR

df

Filesystem     1K-blocks      Used Available Use% Mounted on
:
/dev/sdb11         16336         8     16328   1% /media/ich/PRIVATE
/dev/sdb2         130798      7282    123516   6% /media/ich/Volumn
/dev/sdb12         16334         2     16332   1% /media/ich/FE38-08B2

sudo file -s /dev/sdb??

/dev/sdb1: Linux rev 1.0 ext4 filesystem data, UUID=57f8f4bc-abf4-655f-bf67-946fc0f9f25b (needs journal recovery) (extents) (large files)
/dev/sdb2: x86 boot sector, code offset 0x0, OEM-ID "        ", sectors/cluster 4, root entries 512, Media descriptor 0xf8, sectors/FAT 256, sectors 262144 (volumes > 32 MB) , dos < 4.0 BootSector (0x0), FAT (16 bit)
/dev/sdb3: x86 boot sector; partition 1: ID=0x83, starthead 0, startsector 106495, 32768 sectors; partition 2: ID=0x85, starthead 0, startsector 1, 4857856 sectors, code offset 0x0
/dev/sdb5: data
/dev/sdb6: data
/dev/sdb7: Linux rev 1.0 ext4 filesystem data, UUID=57f8f4bc-abf4-655f-bf67-946fc0f9f25b (extents) (large files)
/dev/sdb8: data
/dev/sdb9: ASCII text, with no line terminators
/dev/sdb10: data
/dev/sdb11: x86 boot sector, code offset 0x58, OEM-ID "android ", sectors/cluster 8, sectors 32768 (volumes <=32 MB) , heads 4, FAT (32 bit), sectors/FAT 32, Backup boot sector 2, serial number 0x1c9208b2, label: "PRIVATE    "
/dev/sdb12: x86 boot sector, code offset 0x3c, OEM-ID "BSD  4.4", sectors/cluster 4, root entries 512, sectors 32768 (volumes <=32 MB) , sectors/FAT 32, heads 4, serial number 0xfe3808b2, unlabeled, FAT (16 bit)
/dev/sdb13: data
/dev/sdb14: data
/dev/sdb15: Linux rev 1.0 ext4 filesystem data, UUID=57f8f4bc-abf4-655f-bf67-946fc0f9f25b (needs journal recovery) (extents) (large files)
ich@ich-VirtualBox:~$ sudo file -s /dev/sdb16

ich@ich-VirtualBox:~$ sudo blkid /dev/sdb1
/dev/sdb1: UUID="57f8f4bc-abf4-655f-bf67-946fc0f9f25b" TYPE="ext4" 
ich@ich-VirtualBox:~$ sudo blkid /dev/sdb2
/dev/sdb2: SEC_TYPE="msdos" LABEL="Volumn" TYPE="vfat" 
ich@ich-VirtualBox:~$ sudo blkid /dev/sdb3
ich@ich-VirtualBox:~$ sudo blkid /dev/sdb5
ich@ich-VirtualBox:~$ sudo blkid /dev/sdb6
ich@ich-VirtualBox:~$ sudo blkid /dev/sdb7
/dev/sdb7: UUID="57f8f4bc-abf4-655f-bf67-946fc0f9f25b" TYPE="ext4" 
ich@ich-VirtualBox:~$ sudo blkid /dev/sdb8
ich@ich-VirtualBox:~$ sudo blkid /dev/sdb9
ich@ich-VirtualBox:~$ sudo blkid /dev/sdb10
ich@ich-VirtualBox:~$ sudo blkid /dev/sdb11
/dev/sdb11: LABEL="PRIVATE" UUID="1C92-08B2" TYPE="vfat" 
ich@ich-VirtualBox:~$ sudo blkid /dev/sdb12
/dev/sdb12: SEC_TYPE="msdos" UUID="FE38-08B2" TYPE="vfat" 
ich@ich-VirtualBox:~$ sudo blkid /dev/sdb13
ich@ich-VirtualBox:~$ sudo blkid /dev/sdb14
ich@ich-VirtualBox:~$ sudo blkid /dev/sdb15
/dev/sdb15: UUID="57f8f4bc-abf4-655f-bf67-946fc0f9f25b" TYPE="ext4"

mkdir TEST
sudo mount -t ext4 /dev/sdb7 ./TEST
ls -al ./TEST

total 76
drwxr-xr-x. 17 root root 4096 Jan  1  1970 .
drwxr-xr-x  24 ich  ich  4096 Jan  7 13:59 ..
drwxr-xr-x.  2 root root 4096 Oct 24 11:19 app
drwxr-xr-x.  2 root root 4096 Oct 24 11:16 backup
drwxr-xr-x.  4 root 2000 4096 Jan  2  1970 bin
-rw-r--r--.  1 root root 3760 Oct 24 11:16 build.prop
drwxr-xr-x.  8 root root 4096 Oct 24 11:19 etc
drwxr-xr-x.  2 root root 4096 Oct 24 11:16 fonts
drwxr-xr-x.  3 root root 4096 Oct 24 11:18 framework
drwxr-xr-x.  6 root root 8192 Oct 24 11:16 lib
drwx------.  2 root root 4096 Jan  1  1970 lost+found
drwxr-xr-x.  3 root root 4096 Oct 24 11:16 media
drwxr-xr-x.  2 root root 4096 Oct 24 11:16 preinstall
drwxr-xr-x.  2 root root 4096 Oct 24 11:18 priv-app
drwxr-xr-x.  3 root root 4096 Oct 24 11:16 tts
drwxr-xr-x.  8 root root 4096 Oct 24 11:16 usr
drwxr-xr-x.  5 root 2000 4096 Oct 24 11:16 vendor
drwxr-xr-x.  2 root 2000 4096 Oct 24 11:16 xbin

df

 
Filesystem     1K-blocks      Used Available Use% Mounted on
:
/dev/sdb7         774064    667644    106420  87% /home/ich/TEST

sudo umount ./TEST

sudo mount -t ext4 /dev/sdb1 ./TEST
ls -al ./TEST

total 112
drwxrwx--x. 26 ich  ich  4096 Jan  2  1970 .
drwxr-xr-x  24 ich  ich  4096 Jan  7 13:59 ..
drwxrwx--x.  2 ich  ich  4096 Jan  2  1970 app
drwx------.  2 root root 4096 Jan  1  1970 app-asec
drwxrwx--x. 15 ich  ich  4096 Jan  2  1970 app-lib
drwxrwx--x.  2 ich  ich  4096 Jan  1  1970 app-private
drwxrwxrwx.  2 root root 4096 Jan  1  1970 audio
drwx------.  5 ich  ich  4096 Jan  2  1970 backup
lrwxrwxrwx.  1 root root   45 Jan  1  1970 bugreports -> /data/data/com.android.shell/files/bugreports
drwxrwxrwx.  2 root root 4096 Jan  1  1970 camera
drwxrwx--x.  2 ich  ich  8192 Jan  2  1970 dalvik-cache
drwxrwx--x. 70 ich  ich  4096 Jan  2  1970 data
drwxr-x---.  2 root 1007 4096 Jan  1  1970 dontpanic
drwxrwx---.  3 1019 1019 4096 Jan  1  1970 drm
drwxrwx---.  2 root ich  4096 Jan  1  1970 HWML
-rw-------.  1 root root    2 Jan  1  1970 .layout_version
drwxr-x--x.  3 root root 4096 Jan  2  1970 local
drwxrwx---   2 root root 4096 Jan  1  1970 lost+found
drwxrwx---.  5 1023 1023 4096 Jan  2  1970 media
drwxrwx---.  2 1031 1031 4096 Jan  1  1970 mediadrm
drwxrwx--t. 15 ich  9998 4096 Jan  1  1970 misc
drwx------.  2 root root 4096 Jan  2  1970 property
drwxrwx--x.  2 ich  ich  4096 Jan  1  1970 resource-cache
drwx--x--x.  2 ich  ich  4096 Jan  1  1970 security
drwxr-x---.  3 root 2000 4096 Jan  1  1970 ssh
drwxrwxr-x. 11 ich  ich  4096 Jan  2  1970 system
-rw-------.  1 root root    0 Jan  2  1970 system.notfirstrun
drwx------.  2 ich  ich  4096 Jan  1  1970 systest
drwx--x--x.  2 ich  ich  4096 Jan  1  1970 user

df

 
Filesystem     1K-blocks      Used Available Use% Mounted on
:
/dev/sdb1        5186616    604560   4582056  12% /home/ich/TEST

sudo umount ./TEST

sudo mount -t ext4 /dev/sdb15 ./TEST
ls -al ./TEST

total 16
drwxrwx---.  4 ich  2001 4096 Jan  2  1970 .
drwxr-xr-x  24 ich  ich  4096 Jan  7 13:59 ..
drwx------.  2 ich  ich  4096 Jan  2  1970 backup
drwxrwx---   2 root root 4096 Jan  1  1970 lost+found

df

 
Filesystem     1K-blocks      Used Available Use% Mounted on
:
/dev/sdb15        645056     10724    634332   2% /home/ich/TEST

sudo umount ./TEST

[geekbuying]

Do you read this thread

I am blind.

[deadhp1]

I didn't use the android image at all.

When I used the sdk to build/pack linux it generated a rootfs that was about ~40mb. I unpacked that image and grabbed the ~40mb rootfs.fex and rootfs.fex.iso.
uploaded them here: http://www.mediafire.com/download/69...rootfs_fex.zip

Then I unpacked the Lubuntu image, backed up the 1.8gb rootfs.fex and rootfs.fex.iso.

Next I replaced the 1.8gb rootfs.fex and rootfs.fex.iso in the Lubuntu image with the ~40mb rootfs.fex and rootfs.fex.iso. At this point the ~40mb rootfs.fex and rootfs.fex.iso are basically dummy files.
They are just there to make the image burn with phoenixcard since it seems to have a problem handling the 1.8gb rootfs files.
(Probably any files could be used since the max size for the partition is contained in sys_partition.fex)

Repacked the Lubuntu image and burned in startup mode with phoenixcard.

The last step was to dd the backed up 1.8gb rootfs.fex to the 7th partition on the sd card which for me was /dev/sdb7.(I found this by reading u-boot.fex and searching for root. It's looking for root in /dev/mmcblk0p7)

sudo dd if=rootfs.fex of=/dev/sdb7 bs=1k

I'm not a huge fan of the way phoenixcard works, it really does seem to create a bad partition table which makes it rather hard to do anything related to partitions. At least this seemed to work for now.

A better solution would be to use a different u-boot rather than the u-boot from the sdk/images.
I haven't gotten that far...yet.

[no_spam_for_me]

OK...
you use the small/little 40mb rootfs.fex and rootfs.fex.iso of the SDK instead of the big 1,8GB rootfs.fex and rootfs.fex.iso of the original img and repacking the img and use PhoenixCard (Startup !) to write this img to the SD...
Then you use the big 1,8GB rootfs.fex to place it at 7 (by dd at Linux)...

THX

"... seems to have a problem handling the 1.8gb rootfs files." => I think so too

"... it really does seem to create a bad partition table ..." => it seems so

[cs918s]

New RKM ROM, I'll try it with Boot from SD , and will confirm if it is working

瑞科美RKM-A80-4.4-6335-20150108_v2.7z

http://pan.baidu.com/wap/link?uk=2923110658&shareid=2900783784&third=3

[no_spam_for_me]

The only speed difference i notice is the boot up speed it is about 8 seconds quicker booting from the sd card,Games play fine with no lag films are playing fine too, i am using a 32GB class 10 samsung evo sd card....Stock rom still intact on my system & finless rom on my sd card, i love this set up i cant find a down side

I am not surprised...
=> I found this at the net

-----------------------------------------------------------------------
CrystalDiskMark 3.0.2 x64 (C) 2007-2013 hiyohiyo
                           Crystal Dew World : http://crystalmark.info/
-----------------------------------------------------------------------
* MB/s = 1,000,000 byte/s [SATA/300 = 300,000,000 byte/s]

           Sequential Read :    43.794 MB/s
          Sequential Write :    19.895 MB/s
         Random Read 512KB :    41.337 MB/s
        Random Write 512KB :    35.828 MB/s
    Random Read 4KB (QD=1) :    10.999 MB/s [  2685.3 IOPS]
   Random Write 4KB (QD=1) :     3.604 MB/s [   880.0 IOPS]
   Random Read 4KB (QD=32) :    11.522 MB/s [  2813.1 IOPS]
  Random Write 4KB (QD=32) :     3.594 MB/s [   877.5 IOPS]

  Test : 100 MB [F: 0.0% (0.0/29.3 GB)] (x5)
  Date : 2014/08/11 20:49:03
    OS : Windows 8  [6.2 Build 9200] (x64)

Notice that it's got a [B]great[/B] random write speed! Far better than sequential, even… this would be great as a ReadyBoost drive.


I'm currently running comparison tests on a Sandisk card (SD, 16GB,  UHS-I, "Extreme", from a DSLR). It's got better sequential write, but  far worse random.
And here it is:
-----------------------------------------------------------------------
CrystalDiskMark 3.0.2 x64 (C) 2007-2013 hiyohiyo
                           Crystal Dew World : http://crystalmark.info/
-----------------------------------------------------------------------
* MB/s = 1,000,000 byte/s [SATA/300 = 300,000,000 byte/s]

           Sequential Read :    43.521 MB/s
          Sequential Write :    41.397 MB/s
         Random Read 512KB :    41.590 MB/s
        Random Write 512KB :     3.752 MB/s
    Random Read 4KB (QD=1) :     5.950 MB/s [  1452.6 IOPS]
   Random Write 4KB (QD=1) :     1.102 MB/s [   269.0 IOPS]
   Random Read 4KB (QD=32) :     4.791 MB/s [  1169.7 IOPS]
  Random Write 4KB (QD=32) :     1.106 MB/s [   270.1 IOPS]

  Test : 100 MB [F: 9.1% (1.4/14.8 GB)] (x5)
  Date : 2014/08/11 20:56:05
    OS : Windows 8  [6.2 Build 9200] (x64)

(Source: https://www.ozbargain.com.au/node/156131 )
Incredible QD values!
I also ordered a '32GB Samsung EVO Class 10 UHS-I Micro SD'
(but this one for the RK3288 running Linux or Android... and maybe later also one for the A80, we will see...)

---

EDIT:
At USB 2.0 also well

Velocidades a través de lector USB2.0:

-----------------------------------------------------------------------
CrystalDiskMark 3.0.3 x64
-----------------------------------------------------------------------
Sequential Read : 21.762 MB/s
Sequential Write : 16.563 MB/s
Random Read 512KB : 21.167 MB/s
Random Write 512KB : 20.334 MB/s
Random Read 4KB (QD=1) : 5.395 MB/s [ 1317.1 IOPS]
Random Write 4KB (QD=1) : 1.552 MB/s [ 378.8 IOPS]
Random Read 4KB (QD=32) : 6.061 MB/s [ 1479.7 IOPS]
Random Write 4KB (QD=32) : 1.238 MB/s [ 302.3 IOPS]

(Source: http://www.amazon.es/review/RX9G8RN8...tore=computers )

or

Crystal Dew World
-----------------------------------------------------------------------
* MB/s = 1,000,000 byte/s [SATA/300 = 300,000,000 byte/s]

Sequential Read : 20.702 MB/s
Sequential Write : 13.297 MB/s
Random Read 512KB : 20.354 MB/s
Random Write 512KB : 17.836 MB/s
Random Read 4KB (QD=1) : 5.325 MB/s [ 1300.2 IOPS]
Random Write 4KB (QD=1) : 2.652 MB/s [ 647.4 IOPS]
Random Read 4KB (QD=32) : 5.381 MB/s [ 1313.8 IOPS]
Random Write 4KB (QD=32) : 2.676 MB/s [ 653.3 IOPS]

(Source: http://www.amazon.co.jp/%E6%97%A5%E6.../dp/B00KGNUUMY )
At this link you can also see, that you will get different results at same USB-speed with different reader... BUT anyway, the results are all fine
(Of cause also depends on the size)

[trebor]

Have an SD card reader built into the my PC, also went and purchased a USB 3 SD/TF card reader.

Burning a boot SD with inbuilt card reader, about 67 seconds to burn.
Using USB3 SD card reader, about 37 seconds burn.

Using Kodi in the RKM.img on SD boot noted lagging/skipping and most buffered
before playing, includes all the Jelly Fish.mkv from 30 to 60 Frames
also samples from no_spam.
Only seen with the 60frame Jellyfish using Draco's internal memory same setup.
Apart from that its pretty snappy running of the SD cards

System takes about 95 seconds for first boot of RKM.img
At reboot system boots in 25 seconds.
Using Samsung Evo 32/10 cards

Cheers

Further Testing with mkv's, from Seagate USB3 HDD all 100% no buffering or micro stutter.

[no_spam_for_me]

Card: http://www.freaktab.com/showthread.p...l=1#post267203
Reader: Transcend TS-RDF5K (USB 3.0)

Rom: stock (Tronsmart Draco AW80 - homlet 4.4.2-a80-v2.0rc3 - 141025)
PC => ~70 sec
First boot:
- ~ 85 sec till launcher
- ~ 115 sec till screen-size shrinks < 100% (I think at that moment boot-up is complete)
Second boot:
- ~ 50 sec till launcher
- ~ 80 sec till screen-size shrinks < 100%

100%
DPI=240
performance

First run at stock KODI seems to be much longer as at eMMC/NAND...

HDD (WD Element 2.5" 1TB USB 3.0) at USB 2.0:
- Jellyfish 60 and 120 Mbps (http://jell.yfish.us/) FINE
- Planet Earth From Pole to Pole 1080p (http://www.mediafire.com/download/td...80p_sample.mkv) the same known some micro-stutters at the beginning during the camera movement between the mountains...
- also the same as at eMMC/NAND with my samples...

[tototo12]

boot linux on sd without flash

hello

is there any option to install bootable linux on a sd card without flash android ?

thank you

[no_spam_for_me]

32 GB Samsung EVO Class 10 UHS-I Micro SD

This card is really a beast

At Transcend TS-RDF5K (USB3.0)

-----------------------------------------------------------------------
CrystalDiskMark 3.0.1 (C) 2007-2010 hiyohiyo
                           Crystal Dew World : http://crystalmark.info/
-----------------------------------------------------------------------
* MB/s = 1,000,000 byte/s [SATA/300 = 300,000,000 byte/s]
 
           Sequential Read :    46.363 MB/s
          Sequential Write :    27.292 MB/s
         Random Read 512KB :    44.496 MB/s
        Random Write 512KB :    37.425 MB/s
    Random Read 4KB (QD=1) :     6.675 MB/s [  1629.7 IOPS]
   Random Write 4KB (QD=1) :     3.102 MB/s [   757.3 IOPS]
   Random Read 4KB (QD=32) :     7.374 MB/s [  1800.2 IOPS]
  Random Write 4KB (QD=32) :     3.418 MB/s [   834.4 IOPS]
 
  Test : 50 MB [J: 0.0% (0.0/29.8 GB)] (x2)
  Date : 2015/01/12 12:01:31

Too bad they throttle the speed at 45 but that's only important at backup the SD...
Much more important are QD and the Random Write 512KB at using at the device

At Notebook Reader

-----------------------------------------------------------------------
CrystalDiskMark 3.0.1 (C) 2007-2010 hiyohiyo
                           Crystal Dew World : http://crystalmark.info/
-----------------------------------------------------------------------
* MB/s = 1,000,000 byte/s [SATA/300 = 300,000,000 byte/s]
 
           Sequential Read :    18.763 MB/s
          Sequential Write :    16.678 MB/s
         Random Read 512KB :    18.652 MB/s
        Random Write 512KB :    16.267 MB/s
    Random Read 4KB (QD=1) :     3.527 MB/s [   861.2 IOPS]
   Random Write 4KB (QD=1) :     2.708 MB/s [   661.1 IOPS]
   Random Read 4KB (QD=32) :     4.439 MB/s [  1083.7 IOPS]
  Random Write 4KB (QD=32) :     2.949 MB/s [   719.9 IOPS]
 
  Test : 50 MB [H: 0.0% (0.0/29.8 GB)] (x2)
  Date : 2015/01/12 12:07:46

I don't understand which standard this reader is, because it's faster than spec 1.01 (12.5 MB/s) but slower than spec 2.00 (25 MB/s) http://en.wikipedia.org/wiki/Secure_Digital#Speeds

Card: http://www.freaktab.com/showthread.p...l=1#post267203
Reader: Transcend TS-RDF5K (USB 3.0)

Rom: stock (Tronsmart Draco AW80 - homlet 4.4.2-a80-v2.0rc3 - 141025)
PC => ~70 sec
First boot:
- ~ 85 sec till launcher
- ~ 115 sec till screen-size shrinks < 100% (I think at that moment boot-up is complete)
Second boot:
- ~ 50 sec till launcher
- ~ 80 sec till screen-size shrinks < 100%
:

PC => ~80 sec
First boot:
- ~ 230 sec till launcher
- ~ 250 sec till screen-size shrinks < 100% (I think at that moment boot-up is complete)


Stop, something's goes wrong...

Again at Transcend TS-RDF5K (USB3.0)
H2testw 1.4
" With H2testw can verify the integrity and other parameters of USB flash drives or flash drives ... The software writes a gigabyte test files on each disk. It then reads the data consisting partly of fixed sequences of numbers, some of pseudo-random numbers again. This is followed by a check of the test data to be exhaustive, integrity and damage." (google translate)

http://www.heise.de/download/h2testw.html

Fertig, kein Fehler aufgetreten.
Sie können die Testdateien *.h2w jetzt löschen oder nach Belieben
nochmals überprüfen.
Schreibrate: 19,0 MByte/s
Leserate: 40,1 MByte/s
H2testw v1.4

-----------------------------------------------------------------------
CrystalDiskMark 3.0.1 (C) 2007-2010 hiyohiyo
                           Crystal Dew World : http://crystalmark.info/
-----------------------------------------------------------------------
* MB/s = 1,000,000 byte/s [SATA/300 = 300,000,000 byte/s]
 
           Sequential Read :    45.756 MB/s
          Sequential Write :    39.545 MB/s
         Random Read 512KB :    43.782 MB/s
        Random Write 512KB :    32.763 MB/s
    Random Read 4KB (QD=1) :     6.280 MB/s [  1533.1 IOPS]
   Random Write 4KB (QD=1) :     2.695 MB/s [   657.9 IOPS]
   Random Read 4KB (QD=32) :     6.825 MB/s [  1666.2 IOPS]
  Random Write 4KB (QD=32) :     2.948 MB/s [   719.6 IOPS]
 
  Test : 50 MB [J: 0.0% (0.0/29.8 GB)] (x2)
  Date : 2015/01/12 14:04:47

PC => ~50 sec
First boot:
It's ONLY 20 SEC faster than the values above (210/230)...
BUT
Second boot:
- ~ 30 sec till launcher
- ~ 33 sec till screen-size shrinks < 100%
ALSO first run at stock KODI is much faster than at the QUMOX

Conclusion:
Maybe the build in reader is spec 3.0 and because the read (Sequential/Random 512) at the QUMOX is much faster, the first boot is also much faster at the QUMOX...
But of cause we need the running system and not the preparing system

[trebor]

Creating Startup sd card

Curios if any others having trouble creating startup.
It appears either some evil has taken over my PC,
card reader has failed or SD cards have failed.

Mini Tool Partition shows that there is unallocated space on SD. after formatting to normal with phoenix.
HPUSB format clears it up, as well as Minitool
SD card can be used normally, or create Product, cannot burn startup.
Cards tested ok to use in other devices.

Cheers