Running Android or Linux from an SD card on a RK3288 device - An easy way to dual boot

[grant2258]

But yes ofcourse, thanks linuxium for the tools and the guide!

looks like the new tronsmart rom doesnt work with this script the boot.img format is a different has 3 files in it


./../../Tools/split_bootimg_pl boot.img
Page size: 16384 (0x00004000)
Kernel size: 6359048 (0x00610808)
Ramdisk size: 1183649 (0x00120fa1)
Second size: 116736 (0x0001c800)
Board name:
Command line:
Writing boot.img-kernel ... complete.
Writing boot.img-ramdisk.gz ... complete.
Writing boot.img-second.gz ... complete.



-rw-r--r-- 1 root root 6359048 Jan 17 16:44 boot.img-kernel
-rw-r--r-- 1 root root 1183649 Jan 17 16:44 boot.img-ramdisk.gz
-rw-r--r-- 1 root root 116736 Jan 17 16:44 boot.img-second.gz ===== <resource.img>


i see the script uses this as a resource.img if it finds the file guess somethings changed in the init or something.

update:

forget the above. Here is what happened and let it be a lesson to me I should have known better. I went to install a image and hit y for sdc and it wiped my linux( yea I know it was a stupid mistake). I reinstalled mint. Now i assumed it was all working because of last time.

I found out what the problem was thought. If your using mint 17 or ubuntu 14.04 update the cpio package at the very least. I just installed all the other updates after I got it working. The problem in linux mint 17.1 was the cpio package like i said.

This next fix also applies to ubunti 14.04 if your having problems the automounting system plays havock sometimes with this script so disable it as your normal user name. Just put the following in the terminal.

gsettings set org.cinnamon.desktop.media-handling automount-open false
gsettings set org.cinnamon.desktop.media-handling automount false



Before plugging in and sdcard. it mainly effects a card thats already been written already. The loopbacks in the script dont unmount propetly and neither does sdcard .It somehow flashes the system.img loopback mount instead if /dev/sdX. Anyway the above gets rid of that problem. Hope this helps some people.

[s3ntrax]

looks like the new tronsmart rom doesnt work with this script the boot.img format is a different has 3 files in it


./../../Tools/split_bootimg_pl boot.img
Page size: 16384 (0x00004000)
Kernel size: 6359048 (0x00610808)
Ramdisk size: 1183649 (0x00120fa1)
Second size: 116736 (0x0001c800)
Board name:
Command line:
Writing boot.img-kernel ... complete.
Writing boot.img-ramdisk.gz ... complete.
Writing boot.img-second.gz ... complete.



-rw-r--r-- 1 root root 6359048 Jan 17 16:44 boot.img-kernel
-rw-r--r-- 1 root root 1183649 Jan 17 16:44 boot.img-ramdisk.gz
-rw-r--r-- 1 root root 116736 Jan 17 16:44 boot.img-second.gz ===== <resource.img>


i see the script uses this as a resource.img if it finds the file guess somethings changed in the init or something.

update:

forget the above. Here is what happened and let it be a lesson to me I should have known better. I went to install a image and hit y for sdc and it wiped my linux( yea I know it was a stupid mistake). I reinstalled mint. Now i assumed it was all working because of last time.

I found out what the problem was thought. If your using mint 17 or ubuntu 14.04 update the cpio package at the very least. I just installed all the other updates after I got it working. The problem in linux mint 17.1 was the cpio package like i said.

This next fix also applies to ubunti 14.04 if your having problems the automounting system plays havock sometimes with this script so disable it as your normal user name. Just put the following in the terminal.

gsettings set org.cinnamon.desktop.media-handling automount-open false
gsettings set org.cinnamon.desktop.media-handling automount false



Before plugging in and sdcard. it mainly effects a card thats already been written already. The loopbacks in the script dont unmount propetly and neither does sdcard .It somehow flashes the system.img loopback mount instead if /dev/sdX. Anyway the above gets rid of that problem. Hope this helps some people.

Cool, thanks for the update!
One of those days when i have some free time I'll mess around with the box again. For now I got the Tronsmart Draco (2nd one cause the first one was a dud i think) which is working perfectly (3 days now)

[vkk]

Is it only for stock firmware?
When I try unpacking both wasser 2.0.5 and 2.0.4 I'm getting "Unpacking of Android image unsuccessful ... exiting."

Edit
Same with chameleon, I set the permissions to read/write and execute on both the script and the images.

Tried with lubuntu on vm and linux mint native from external HD

[no_spam_for_me]

Is it only for stock firmware?
When I try unpacking both wasser 2.0.5 and 2.0.4 I'm getting "Unpacking of Android image unsuccessful ... exiting."

Edit
Same with chameleon, I set the permissions to read/write and execute on both the script and the images.

If you read the thread you will find http://www.freaktab.com/showthread.php?20229-Running-Android-or-Linux-from-an-SD-card-on-a-RK3288-device-An-easy-way-to-dual-boot&p=265538&viewfull=1#post265538

EDIT
also check if you use 32 or 64 bit...

[vkk]

If you read the thread you will find http://www.freaktab.com/showthread.php?20229-Running-Android-or-Linux-from-an-SD-card-on-a-RK3288-device-An-easy-way-to-dual-boot&p=265538&viewfull=1#post265538

EDIT
also check if you use 32 or 64 bit...

Ah thanks!

I just searched for unsuccesful in the thread and didnt find anything.
64bit, I did everything you and linuxium said and it finally worked.

Thank you guys!

Now I'll check if there's a performance increase with the evo

[no_spam_for_me]

I tested the NAND (8GB) at Linux

Inspired by your eMMC/NAND performance test (https://plus.google.com/+IanMORRISON/posts/MicuuyJdbak) I had done the same at my UBOX with 8GB chip...

iozone
                                                    random   random
   kB  reclen    write  rewrite    read    reread     read    write
51200       4     2802     2241     7863     7669     5166     2031
51200     512    11321     7389    34326    34687    34114     7489
51200   16384    [B]13594    12551[/B]    41565    42211    42215    13925
 
su
1.  First I set the governor to 'performance'
echo performance > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
2.  For the write test I use the command 
dd if=/dev/zero of=speedtest bs=1M count=1000 oflag=direct conv=fdatasync
3.  For the read test I use 
dd of=/dev/null if=speedtest bs=1M count=1000 iflag=direct
 
write  3 times
  6.5 / 6.5 / 6.5
read  3 times
  42.5 / 42.6 / 42.9

especially the write/rewrite are not really nice so because of that the dd writes are also not really nice...
:

and the EVO

:

dd of=/dev/null if=speedtest bs=1M count=1000 iflag=direct
1000+0 records in
1000+0 records out
1048576000 bytes (1.0 GB) copied, 46.5529 s, [B]22.5 MB/s[/B]
dd if=/dev/zero of=speedtest bs=1M count=1000 oflag=direct conv=fdatasync
1000+0 records in
1000+0 records out
1048576000 bytes (1.0 GB) copied, 123 s, [B]8.5 MB/s[/B]

:

                                                              random    random
              kB  reclen    write  rewrite    read    reread    read     write
           51200       4     [B]3451     3426    10541    10572    10514     3520[/B]
           51200     512    [B]15129    15763[/B]    21890    21967    21963 [B]   15670[/B]
           51200   16384    [B]15946    16250[/B]    22505    22547    22547[B]    16349[/B]

:

Because of the limit of the microSD-reader (max read ~22MB/s) it will me slower at read (sequential) but it is faster at the writes, at the randoms and at the small blocks...

[vkk]

Yeah but I figured the random is more important for system performance.
Anyway I got excited too soon, it didnt flash anything on the sdcard, it just goes with the flashing really fast and only creates the partitions.

wat@huh:~/Desktop/New$ cp and and-debug
wat@huh:~/Desktop/New$ sed -i 's?2> /dev/null??' and-debug
wat@huh:~/Desktop/New$ sudo ./and-debug was.img
./and-debug: Is your SD card loaded as '/dev/sdc' (y/n)? n
./and-debug: Do you want to use a different device? y
./and-debug: Enter new device name? /dev/sdb
./and-debug: Is your SD card loaded as '/dev/sdb' (y/n)? y
./and-debug: Unmounting partitions on '/dev/sdb' ... done.
./and-debug: Unpacking Android image 'was.img' ... done.
./and-debug: Unpacking Android boot image ... done.
./and-debug: Formatting SD card '/dev/sdb' ... done.
./and-debug: Flashing bootloader 'sdboot_rk3288.img' to '/dev/sdb' ... done.
./and-debug: Updating partition table on '/dev/sdb' ... done.
./and-debug: Calculating partition sizes for '/dev/sdb' ... done.
./and-debug: Creating 'cache' partition as '/dev/sdb1' with size of 128 MB ...done.
./and-debug: Making 'ext4' file system for 'cache' partition on '/dev/sdb1' ... done.
./and-debug: Creating 'metadata' partition as '/dev/sdb2' with size of 4 MB ... done.
./and-debug: Making 'ext4' file system for 'metadata' partition on '/dev/sdb2' ... done.
./and-debug: Creating 'system' partition as '/dev/sdb3' with size of 768 MB ... done.
./and-debug: Making 'ext4' file system for 'system' partition on '/dev/sdb3' ... done.
./and-debug: Creating 'data' partition as '/dev/sdb4' using rest of space on '/dev/sdb' ... done.
./and-debug: Making 'ext4' file system for 'data' partition on '/dev/sdb4' ... done.
./and-debug: Updating Android boot source ... grep: res: Is a directory
grep: sbin: Is a directory
grep: res: Is a directory
grep: sbin: Is a directory
done.
./and-debug: Rebuilding Android boot image ... 4059 blocks
done.
./and-debug: Creating 'parameter.img' from 'parameter' ... done.
./and-debug: Flashing 'parameter.img' to '/dev/sdb' ... done.
./and-debug: Flashing boot 'boot.img' to '/dev/sdb ... done.
./and-debug: Flashing kernel 'kernel' to '/dev/sdb ... done.
./and-debug: Flashing resource 'resource' to '/dev/sdb ... done.
./and-debug: Flashing system 'system.img' to '/dev/sdb3' ... done.
./and-debug: Removing unpacked Android image ... done.
./and-debug: Flushing buffers for '/dev/sdb' ... done.
./and-debug: Android SD card created on '/dev/sdb'.

Tried wasser, cameleon and stock 111k.
I think its because I'm using the laptops card reader since the usb reader doesnt recognize the microsd.

Edit: gdisk is installed

[hueb_s]

If you don't know what device file your sdcard is, you just shouldn't do this! Do you know what a syslog is?

[no_spam_for_me]

Yeah but I figured the random is more important for system performance.
:

YOU find it out? hmmmm

http://www.freaktab.com/showthread.php?21974-Microsd-as-emmc

:
I think its because I'm using the laptops card reader since the usb reader doesnt recognize the microsd.
:

I don't know whitch VM you use (VWware, VMBox,...) and also I don't know if it wil be handled as /dev/sd* or /dev/mmcblk*
After plug in a dmesg could helps a lot...

[vkk]

If you don't know what device file your sdcard is, you just shouldn't do this! Do you know what a syslog is?

I do know which one is the sdcard, dont know how to do\check syslog.

YOU find it out? hmmmm

http://www.freaktab.com/showthread.php?21974-Microsd-as-emmc

Didnt get you

dmesg[/I] could helps a lot...

I tried with linux mint running natively from extrenal HDD, and from VMWARE lubuntu.

This is from native mint
dmesg before - https://www.dropbox.com/s/su50k2xy70...mesg2.txt?dl=0
dmesg after - https://www.dropbox.com/s/1mwcstu2wp...dmesg.txt?dl=0

and

sdc      8:32   1  14.9G  0 disk 
└─sdc1   8:33   1  14.9G  0 part /media/huh/ADF8-FB0A

sdc      8:32   1  14.9G  0 disk 
├─sdc1   8:33   1   128M  0 part /media/huh/cf6b03dd-f3c3-4a27-a862-10b4bf12df10
├─sdc2   8:34   1     4M  0 part /media/huh/6b8ceaea-c7d6-4f1f-acdb-6f212deae637
├─sdc3   8:35   1   768M  0 part 
└─sdc4   8:36   1     2G  0 part /media/huh/829ebeb0-1ae1-44eb-8a3c-52051bb34c4b

When I try to turn the box on I see a frozen boot animation.
Box is fine because it booted linux from sdcard when created with windows.

[no_spam_for_me]

Your after seems to be the before
and your before seems to be the after...

Anyway, but what had you done after the before?

That's the delta at the demesg2.txt (the real after)

[ 1187.659545] [UFW BLOCK] IN=wlan0 OUT= MAC=7c:e9:d3:17:88:ad:84:94:8c:62:97:42:08:00 SRC=192.168.0.1 DST=224.0.0.1 LEN=36 TOS=0x00 PREC=0x00 TTL=1 ID=0 DF PROTO=2 
[ 1312.832684] [UFW BLOCK] IN=wlan0 OUT= MAC=7c:e9:d3:17:88:ad:84:94:8c:62:97:42:08:00 SRC=192.168.0.1 DST=224.0.0.1 LEN=36 TOS=0x00 PREC=0x00 TTL=1 ID=0 DF PROTO=2 
[ 1438.016411] [UFW BLOCK] IN=wlan0 OUT= MAC=7c:e9:d3:17:88:ad:84:94:8c:62:97:42:08:00 SRC=192.168.0.1 DST=224.0.0.1 LEN=36 TOS=0x00 PREC=0x00 TTL=1 ID=0 DF PROTO=2 
[ 1504.773386] usb 1-1.4: new high-speed USB device number 12 using ehci-pci
[ 1504.867467] usb 1-1.4: New USB device found, idVendor=058f, idProduct=6366
[ 1504.867472] usb 1-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 1504.867474] usb 1-1.4: Product: Mass Storage Device
[ 1504.867476] usb 1-1.4: Manufacturer: Generic
[ 1504.867478] usb 1-1.4: SerialNumber: 058F63666433
[ 1504.867904] usb-storage 1-1.4:1.0: USB Mass Storage device detected
[ 1504.868364] scsi13 : usb-storage 1-1.4:1.0
[ 1505.995404] scsi 13:0:0:0: Direct-Access     Multiple Card  Reader     1.00 PQ: 0 ANSI: 0
[ 1505.995829] sd 13:0:0:0: Attached scsi generic sg3 type 0
[ 1506.374135] sd 13:0:0:0: [sdc] Attached SCSI removable disk
[ 1507.906217] usb 1-1.4: USB disconnect, device number 12
[ 1534.756725] usb 1-1.4: new high-speed USB device number 13 using ehci-pci
[ 1534.850811] usb 1-1.4: New USB device found, idVendor=058f, idProduct=6366
[ 1534.850815] usb 1-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 1534.850818] usb 1-1.4: Product: Mass Storage Device
[ 1534.850819] usb 1-1.4: Manufacturer: Generic
[ 1534.850821] usb 1-1.4: SerialNumber: 058F63666433
[ 1534.851240] usb-storage 1-1.4:1.0: USB Mass Storage device detected
[ 1534.851553] scsi14 : usb-storage 1-1.4:1.0
[ 1535.978670] scsi 14:0:0:0: Direct-Access     Multiple Card  Reader     1.00 PQ: 0 ANSI: 0
[ 1535.979261] sd 14:0:0:0: Attached scsi generic sg3 type 0
[ 1536.662825] sd 14:0:0:0: [sdc] 31291392 512-byte logical blocks: (16.0 GB/14.9 GiB)
[ 1536.663863] sd 14:0:0:0: [sdc] Write Protect is off
[ 1536.663874] sd 14:0:0:0: [sdc] Mode Sense: 03 00 00 00
[ 1536.664979] sd 14:0:0:0: [sdc] No Caching mode page found
[ 1536.664986] sd 14:0:0:0: [sdc] Assuming drive cache: write through
[ 1536.669235] sd 14:0:0:0: [sdc] No Caching mode page found
[ 1536.669265] sd 14:0:0:0: [sdc] Assuming drive cache: write through
[ 1536.679136]  sdc: sdc1 sdc2 sdc3 sdc4
[ 1536.683607] sd 14:0:0:0: [sdc] No Caching mode page found
[ 1536.683615] sd 14:0:0:0: [sdc] Assuming drive cache: write through
[ 1536.683622] sd 14:0:0:0: [sdc] Attached SCSI removable disk
[ 1539.042267] EXT4-fs (loop0): mounted filesystem with ordered data mode. Opts: (null)
[ 1539.066593] EXT4-fs (sdc2): mounted filesystem with ordered data mode. Opts: (null)
[ 1539.072195] EXT4-fs (sdc4): mounted filesystem with ordered data mode. Opts: (null)
[ 1539.083285] EXT4-fs (sdc1): mounted filesystem with ordered data mode. Opts: (null)
[ 1563.198288] [UFW BLOCK] IN=wlan0 OUT= MAC=7c:e9:d3:17:88:ad:84:94:8c:62:97:42:08:00 SRC=192.168.0.1 DST=224.0.0.1 LEN=36 TOS=0x00 PREC=0x00 TTL=1 ID=0 DF PROTO=2 
[ 1585.539426] [UFW BLOCK] IN=wlan0 OUT= MAC=7c:e9:d3:17:88:ad:84:94:8c:62:97:42:08:00 SRC=83.7.114.33 DST=192.168.0.16 LEN=58 TOS=0x00 PREC=0x00 TTL=48 ID=0 DF PROTO=UDP SPT=51515 DPT=30555 LEN=38 
[ 1588.562181] [UFW BLOCK] IN=wlan0 OUT= MAC=7c:e9:d3:17:88:ad:84:94:8c:62:97:42:08:00 SRC=83.7.114.33 DST=192.168.0.16 LEN=58 TOS=0x00 PREC=0x00 TTL=48 ID=0 DF PROTO=UDP SPT=51515 DPT=30555 LEN=38 
[ 1688.333276] [UFW BLOCK] IN=wlan0 OUT= MAC=7c:e9:d3:17:88:ad:84:94:8c:62:97:42:08:00 SRC=192.168.0.1 DST=224.0.0.1 LEN=36 TOS=0x00 PREC=0x00 TTL=1 ID=0 DF PROTO=2 
[ 1813.465125] [UFW BLOCK] IN=wlan0 OUT= MAC=7c:e9:d3:17:88:ad:84:94:8c:62:97:42:08:00 SRC=192.168.0.1 DST=224.0.0.1 LEN=36 TOS=0x00 PREC=0x00 TTL=1 ID=0 DF PROTO=2 
[ 1938.610481] [UFW BLOCK] IN=wlan0 OUT= MAC=7c:e9:d3:17:88:ad:84:94:8c:62:97:42:08:00 SRC=192.168.0.1 DST=224.0.0.1 LEN=36 TOS=0x00 PREC=0x00 TTL=1 ID=0 DF PROTO=2 
[ 2035.301973] usb 1-1.4: USB disconnect, device number 13
[ 2039.600450] usb 1-1.4: new high-speed USB device number 14 using ehci-pci
[ 2039.694786] usb 1-1.4: New USB device found, idVendor=058f, idProduct=6366
[ 2039.694798] usb 1-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 2039.694804] usb 1-1.4: Product: Mass Storage Device
[ 2039.694809] usb 1-1.4: Manufacturer: Generic
[ 2039.694814] usb 1-1.4: SerialNumber: 058F63666433
[ 2039.695572] usb-storage 1-1.4:1.0: USB Mass Storage device detected
[ 2039.696357] scsi15 : usb-storage 1-1.4:1.0
[ 2040.826828] scsi 15:0:0:0: Direct-Access     Multiple Card  Reader     1.00 PQ: 0 ANSI: 0
[ 2040.827554] sd 15:0:0:0: Attached scsi generic sg3 type 0
[ 2041.518307] sd 15:0:0:0: [sdc] 31291392 512-byte logical blocks: (16.0 GB/14.9 GiB)
[ 2041.519385] sd 15:0:0:0: [sdc] Write Protect is off
[ 2041.519396] sd 15:0:0:0: [sdc] Mode Sense: 03 00 00 00
[ 2041.520492] sd 15:0:0:0: [sdc] No Caching mode page found
[ 2041.520500] sd 15:0:0:0: [sdc] Assuming drive cache: write through
[ 2041.524622] sd 15:0:0:0: [sdc] No Caching mode page found
[ 2041.524631] sd 15:0:0:0: [sdc] Assuming drive cache: write through
[ 2041.535827]  sdc: sdc1
[ 2041.539568] sd 15:0:0:0: [sdc] No Caching mode page found
[ 2041.539580] sd 15:0:0:0: [sdc] Assuming drive cache: write through
[ 2041.539588] sd 15:0:0:0: [sdc] Attached SCSI removable disk

[vkk]

"Before" should be when the card is fat32 one partition and "after" is after I tried to flash the rom on the microsd, it shows all the partitions but they are empty.
In the terminal it shows "flashing" for a second and them done without writing anything.

Maybe I messed the dmesgs up?

[no_spam_for_me]

hmmm, I wondering why I see during this process 3 times

[ 1504.773386] usb 1-1.4: new high-speed USB device number 12 using ehci-pci

as 12, 13, 14
and also

[ 2039.695572] usb-storage 1-1.4:1.0: USB Mass Storage device detected
[ 2039.696357] scsi13 : usb-storage 1-1.4:1.0
[ 2040.826828] scsi 13:0:0:0: Direct-Access     Multiple Card  Reader     1.00 PQ: 0 ANSI: 0

as 13, 14 and 15...

maybe because of changing the partition table???

Also I see

[ 1536.679136]  sdc: sdc1 sdc2 sdc3 sdc4

and later

[ 2041.535827]  sdc: sdc1

Also why

[ 1539.042267] EXT4-fs ([B]loop0[/B]): mounted filesystem with ordered data mode. Opts: (null)

?

[vkk]

I think USB mass storage is external HD, I have an NTFS partition on it as well and it shows on linux as usb mass storage.

[COLOR=#333333][ 1536.679136]  sdc: sdc1 sdc2 sdc3 sdc4[/COLOR]

Because of partitions?

The rest I have no idea as I know close to nothing about linux.

I think it has to do with the card reader, maybe it will work with usb.

Edit: just tried usb stick and its the same

Edit2: Scratch that tried again and it work with old usb stick.

Guess I'll have to buy a new card reader

[grant2258]

It's not your card reader disable the auto mount in mint I posted earlier in this thread how and how to do it. dd gets confused and writes to the loop back mount not sure why but it is the problem. Also make sure to update cpio package because the default one has problems. Test all the binary as well in the tools directory I think it's tools from memory just run and check for errors.