[MIDCF43] 4.3'' PC Tablet (Low Cost)

[bin]

Salut,

Je ne trouve pas beaucoup d'info sur cette petite tablet lowcost (produit publicitaire ~40$), voici donc une petite inspection materiel et logiciel avant de me lancer sur la modification de la ROM

HARDWARE

Chips:

- CPU : F20

- RAM : SAMSUNG KGA08U0E

- NAND : Elixir 1208

- Wifi : Realtek RTL8180

- ? : AXP193

SOFTWARE

ADB device

./adb devices
List of devices attached
20080411	device

Cpu info

# cat /proc/cpuinfo
Processor	: ARM926EJ-S rev 5 (v5l)
BogoMIPS	: 650.43
Features	: swp half thumb fastmult edsp java
CPU implementer	: 0x41
CPU architecture: 5TEJ
CPU variant	: 0x0
CPU part	: 0x926
CPU revision	: 5

Hardware	: sun3i
Revision	: 0000
Serial		: 0000000000000000

Mem info

# cat /proc/meminfo
MemTotal:		 166440 kB
MemFree:		   24704 kB
Buffers:			1484 kB
Cached:			72128 kB
SwapCached:			0 kB
Active:			64772 kB
Inactive:		  63664 kB
Active(anon):	  54860 kB
Inactive(anon):	  260 kB
Active(file):	   9912 kB
Inactive(file):	63404 kB
Unevictable:		   0 kB
Mlocked:			   0 kB
HighTotal:			 0 kB
HighFree:			  0 kB
LowTotal:		 166440 kB
LowFree:		   24704 kB
SwapTotal:			 0 kB
SwapFree:			  0 kB
Dirty:				 4 kB
Writeback:			 0 kB
AnonPages:		 54840 kB
Mapped:			28656 kB
Shmem:			   296 kB
Slab:			   4868 kB
SReclaimable:	   1848 kB
SUnreclaim:		 3020 kB
KernelStack:		1840 kB
PageTables:		 3696 kB
NFS_Unstable:		  0 kB
Bounce:				0 kB
WritebackTmp:		  0 kB
CommitLimit:	   83220 kB
Committed_AS:	 702572 kB
VmallocTotal:	 122880 kB
VmallocUsed:	   30228 kB
VmallocChunk:	  82948 kB

Ls / (Root)

./adb shell
# ls -l
-rwxr-xr-x mount	mount	   98264 2012-02-22 01:20 init
drwxr-xr-x root	 root			  2012-05-03 14:38 sys
drwx------ root	 root			  2012-02-22 01:20 lost+found
lrwxrwxrwx root	 root			  2010-01-01 00:00 cache -> /data/root-cache
-rw-r--r-- mount	mount		 118 2012-02-22 01:20 default.prop
-rw-r--r-- mount	mount		1677 2012-02-22 01:20 init.goldfish.rc
-rw-r--r-- mount	mount		 288 2012-02-22 01:20 ueventd.goldfish.rc
lrwxrwxrwx root	 root			  2010-01-01 00:00 vendor -> /system/vendor
drwxrwxr-x root	 system			2010-01-01 00:00 mnt
-rwxr--r-- mount	mount	  522240 2012-02-22 01:20 initlogo.rle
drwxr-xr-x mount	mount			 2012-02-22 01:20 drivers
dr-xr-xr-x root	 root			  1970-01-01 01:00 proc
lrwxrwxrwx root	 root			  2010-01-01 00:00 d -> /sys/kernel/debug
dr-x------ root	 root			  2010-01-01 00:00 config
drwxr-xr-x mount	mount			 2012-02-22 01:20 sbin
-rw-rw-rw- root	 root		37681 2012-05-02 23:16 sdcard
lrwxrwxrwx root	 root			  2010-01-01 00:00 etc -> /system/etc
drwxr-xr-x mount	mount			 2012-02-22 01:20 sun3i_conf
drwxr-xr-x root	 root			  2010-01-01 00:00 acct
-rw-r--r-- mount	mount		3868 2012-02-22 01:20 ueventd.rc
drwxr-xr-x mount	mount			 2012-02-22 01:20 system
drwxr-xr-x root	 root			  2012-05-03 14:38 dev
-rwxr--r-- mount	mount	   16035 2012-02-22 01:20 init.rc
drwxrwx--x system   system			2012-05-03 03:54 data

Ls /dev

# ls -l /dev
crw------- root	 root	   7, 135 2012-05-03 14:38 vcsa7
crw------- root	 root	   7,   7 2012-05-03 14:38 vcs7
drwxr-xr-x system   system			2012-05-03 14:38 cpuctl
crw------- root	 root	 247,   0 2012-05-03 14:38 ace_dev
crw------- root	 root	 150,   0 2012-05-03 14:38 cedar_dev
crw-rw---- system   audio	249,   1 2012-05-03 14:38 pmem_adsp
crw-rw---- system   graphics 250,   0 2012-05-03 14:38 pmem
drwxr-xr-x root	 root			  2012-05-03 14:41 block
crwxrwxrwx root	 root	 251,   0 2012-05-03 14:38 g2d
crwxrwxrwx system   system   252,   0 2012-05-03 14:38 disp
crw------- root	 root	  10,  50 2012-05-03 14:38 network_throughput
crw------- root	 root	  10,  51 2012-05-03 14:38 network_latency
crw------- root	 root	  10,  52 2012-05-03 14:38 cpu_dma_latency
drwxr-xr-x root	 root			  2012-05-03 14:38 log
crw-rw-rw- root	 root	  10,  57 2012-05-03 14:38 binder
crw------- root	 root	  10, 236 2012-05-03 14:38 device-mapper
crw-rw-r-- system   radio	 10,  58 2012-05-03 14:38 alarm
crw-rw---- system   bluetooth  10, 223 2012-05-03 14:38 uinput
crw-rw---- adb	  adb	   10,  59 2012-05-03 14:38 android_adb_enable
crw-rw---- adb	  adb	   10,  60 2012-05-03 14:38 android_adb
crw------- root	 root	  10,  61 2012-05-03 14:38 tv_connected
crw------- root	 root	  10,  62 2012-05-03 14:38 cuse
crw------- root	 root	  10, 229 2012-05-03 14:38 fuse
crw-rw-rw- root	 root	  10,  63 2012-05-03 14:38 ashmem
crw-rw-rw- root	 root	 267,   0 2012-05-03 14:38 pm
crw------- root	 root	   7, 129 2012-05-03 14:38 vcsa1
crw------- root	 root	   7,   1 2012-05-03 14:38 vcs1
crw------- root	 root	   7, 128 2012-05-03 14:38 vcsa
crw------- root	 root	   7,   0 2012-05-03 14:38 vcs
crw-rw-rw- root	 root	   5,   2 2012-05-03 15:24 ptmx
crw------- root	 root	   4,  63 2012-05-03 14:38 tty63
crw------- root	 root	   4,  62 2012-05-03 14:38 tty62
crw------- root	 root	   4,  61 2012-05-03 14:38 tty61
crw------- root	 root	   4,  60 2012-05-03 14:38 tty60
crw------- root	 root	   4,  59 2012-05-03 14:38 tty59
crw------- root	 root	   4,  58 2012-05-03 14:38 tty58
crw------- root	 root	   4,  57 2012-05-03 14:38 tty57
crw------- root	 root	   4,  56 2012-05-03 14:38 tty56
crw------- root	 root	   4,  55 2012-05-03 14:38 tty55
crw------- root	 root	   4,  54 2012-05-03 14:38 tty54
crw------- root	 root	   4,  53 2012-05-03 14:38 tty53
crw------- root	 root	   4,  52 2012-05-03 14:38 tty52
crw------- root	 root	   4,  51 2012-05-03 14:38 tty51
crw------- root	 root	   4,  50 2012-05-03 14:38 tty50
crw------- root	 root	   4,  49 2012-05-03 14:38 tty49
crw------- root	 root	   4,  48 2012-05-03 14:38 tty48
crw------- root	 root	   4,  47 2012-05-03 14:38 tty47
crw------- root	 root	   4,  46 2012-05-03 14:38 tty46
crw------- root	 root	   4,  45 2012-05-03 14:38 tty45
crw------- root	 root	   4,  44 2012-05-03 14:38 tty44
crw------- root	 root	   4,  43 2012-05-03 14:38 tty43
crw------- root	 root	   4,  42 2012-05-03 14:38 tty42
crw------- root	 root	   4,  41 2012-05-03 14:38 tty41
crw------- root	 root	   4,  40 2012-05-03 14:38 tty40
crw------- root	 root	   4,  39 2012-05-03 14:38 tty39
crw------- root	 root	   4,  38 2012-05-03 14:38 tty38
crw------- root	 root	   4,  37 2012-05-03 14:38 tty37
crw------- root	 root	   4,  36 2012-05-03 14:38 tty36
crw------- root	 root	   4,  35 2012-05-03 14:38 tty35
crw------- root	 root	   4,  34 2012-05-03 14:38 tty34
crw------- root	 root	   4,  33 2012-05-03 14:38 tty33
crw------- root	 root	   4,  32 2012-05-03 14:38 tty32
crw------- root	 root	   4,  31 2012-05-03 14:38 tty31
crw------- root	 root	   4,  30 2012-05-03 14:38 tty30
crw------- root	 root	   4,  29 2012-05-03 14:38 tty29
crw------- root	 root	   4,  28 2012-05-03 14:38 tty28
crw------- root	 root	   4,  27 2012-05-03 14:38 tty27
crw------- root	 root	   4,  26 2012-05-03 14:38 tty26
crw------- root	 root	   4,  25 2012-05-03 14:38 tty25
crw------- root	 root	   4,  24 2012-05-03 14:38 tty24
crw------- root	 root	   4,  23 2012-05-03 14:38 tty23
crw------- root	 root	   4,  22 2012-05-03 14:38 tty22
crw------- root	 root	   4,  21 2012-05-03 14:38 tty21
crw------- root	 root	   4,  20 2012-05-03 14:38 tty20
crw------- root	 root	   4,  19 2012-05-03 14:38 tty19
crw------- root	 root	   4,  18 2012-05-03 14:38 tty18
crw------- root	 root	   4,  17 2012-05-03 14:38 tty17
crw------- root	 root	   4,  16 2012-05-03 14:38 tty16
crw------- root	 root	   4,  15 2012-05-03 14:38 tty15
crw------- root	 root	   4,  14 2012-05-03 14:38 tty14
crw------- root	 root	   4,  13 2012-05-03 14:38 tty13
crw------- root	 root	   4,  12 2012-05-03 14:38 tty12
crw------- root	 root	   4,  11 2012-05-03 14:38 tty11
crw------- root	 root	   4,  10 2012-05-03 14:38 tty10
crw------- root	 root	   4,   9 2012-05-03 14:38 tty9
crw------- root	 root	   4,   8 2012-05-03 14:38 tty8
crw------- root	 root	   4,   7 2012-05-03 14:38 tty7
crw------- root	 root	   4,   6 2012-05-03 14:38 tty6
crw------- root	 root	   4,   5 2012-05-03 14:38 tty5
crw------- root	 root	   4,   4 2012-05-03 14:38 tty4
crw------- root	 root	   4,   3 2012-05-03 14:38 tty3
crw------- root	 root	   4,   2 2012-05-03 14:38 tty2
crw------- root	 root	   4,   1 2012-05-03 14:38 tty1
crw-rw---- root	 system	 4,   0 2012-05-03 14:38 tty0
crw------- root	 root	   5,   1 2012-05-03 14:38 console
crw-rw-rw- root	 root	   5,   0 2012-05-03 14:38 tty
crw------- root	 root	   1,  11 2012-05-03 14:38 kmsg
crw-rw-rw- root	 root	   1,   9 2012-05-03 14:38 urandom
crw-rw-rw- root	 root	   1,   8 2012-05-03 14:38 random
crw-rw-rw- root	 root	   1,   7 2012-05-03 14:38 full
crw-rw-rw- root	 root	   1,   5 2012-05-03 14:38 zero
crw-rw-rw- root	 root	   1,   3 2012-05-03 14:38 null
crw------- root	 root	   1,   2 2012-05-03 14:38 kmem
crw------- root	 root	   1,   1 2012-05-03 14:38 mem
drwxr-xr-x root	 root			  2012-05-03 14:38 snd
crw------- root	 root	  89,   1 2012-05-03 14:38 i2c-1
drwxr-xr-x root	 root			  2012-05-03 14:38 input
crw------- root	 root	  89,   0 2012-05-03 14:38 i2c-0
crw------- root	 root	 254,   0 2012-05-03 14:38 rtc0
drwxr-xr-x root	 root			  2012-05-03 14:38 bus
crw------- root	 root	   4,  64 2012-05-03 14:38 ttyS0
drwxr-xr-x root	 root			  2012-05-03 14:38 graphics
crw-rw-rw- root	 root	 253,   0 2012-05-03 14:38 de
drwxr-xr-x root	 root			  2012-05-03 14:38 socket
drwxr-xr-x root	 root			  1970-01-01 01:00 pts

Ls /dev/block

# ls -l /dev/block
brw------- root	 root	 179,   1 2012-05-03 14:41 mmcblk0p1
drwxr-xr-x root	 root			  2012-05-03 14:41 platform
brw------- root	 root	 179,   0 2012-05-03 14:41 mmcblk0
drwxr-xr-x root	 root			  2012-05-03 14:41 vold
brw------- root	 root	   9,   0 2012-05-03 14:38 md0
brw------- root	 root	  93,  32 2012-05-03 14:38 nande
brw------- root	 root	  93,  24 2012-05-03 14:38 nandd
brw------- root	 root	  93,  16 2012-05-03 14:38 nandc
brw------- root	 root	  93,   8 2012-05-03 14:38 nandb
brw------- root	 root	  93,   0 2012-05-03 14:38 nanda
brw------- root	 root	   7,   7 2012-05-03 14:38 loop7
brw------- root	 root	   7,   6 2012-05-03 14:38 loop6
brw------- root	 root	   7,   5 2012-05-03 14:38 loop5
brw------- root	 root	   7,   4 2012-05-03 14:38 loop4
brw------- root	 root	   7,   3 2012-05-03 14:38 loop3
brw------- root	 root	   7,   2 2012-05-03 14:38 loop2
brw------- root	 root	   7,   1 2012-05-03 14:38 loop1
brw------- root	 root	   7,   0 2012-05-03 14:38 loop0
brw------- root	 root	   1,   0 2012-05-03 14:38 ram0

Partitions

# cat /proc/partitions
major minor  #blocks  name

 93		0	  16384 nanda
 93		8	  16384 nandb
 93	   16	 262144 nandc
 93	   24	 524288 nandd
 93	   32	1145856 nande
179		0	1921024 mmcblk0
179		1	1916922 mmcblk0p1

Mounts

# cat /proc/mounts
rootfs / rootfs rw 0 0
/dev/root / ext3 rw,relatime,barrier=1,nodelalloc,data=ordered 0 0
devtmpfs /dev devtmpfs rw,relatime,size=83152k,nr_inodes=20788,mode=755 0 0
tmpfs /dev tmpfs rw,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
/dev/block/nandc /system ext4 rw,noatime,barrier=1,data=ordered 0 0
/dev/block/nandd /data ext4 rw,noatime,barrier=1,data=ordered 0 0
/dev/block/vold/93:32 /mnt/sdcard vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0000,dmask=0000,allow_utime=0022,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/93:32 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0000,dmask=0000,allow_utime=0022,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
tmpfs /mnt/sdcard/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0
/dev/block/vold/179:1 /mnt/extern_sd vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0000,dmask=0000,allow_utime=0022,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/179:1 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0000,dmask=0000,allow_utime=0022,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
tmpfs /mnt/extern_sd/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0

ADB user

echo "test" > zzzz.txt
...
lrwxrwxrwx root	 root			  2010-01-01 00:00 etc -> /system/etc
-rw-rw-rw- root	 root			5 2012-05-03 16:43 zzzz.txt
drwxr-xr-x mount	mount			 2012-02-22 01:20 sun3i_conf
...

Df

# df
Filesystem			 Size   Used   Free   Blksize
/					   14M	 8M	 5M   1024
/					   14M	 8M	 5M   1024
/dev					81M	44K	81M   4096
/dev					81M	44K	81M   4096
/mnt/asec			   81M	 0K	81M   4096
/mnt/obb				81M	 0K	81M   4096
/system				241M	80M   161M   1024
/data				  467M	47M   419M   1024
/mnt/extern_sd		   1G   128K	 1G   32768
/mnt/secure/asec		 1G	24K	 1G   4096
/mnt/sdcard			  1G	24K	 1G   4096
/mnt/secure/asec		 1G	24K	 1G   4096

LIENS

F20 datasheet : http://wenku.baidu.c...eae009ed23.html

Alibaba : http://gri.en.alibaba.com/product/510423703-209961836/BOXCHIP_F20_5_inch_android_2_2_tablet_pc.html

OVERVIEW

Bon tout à l'air déja "open bar", toutes les partitions sont en r/w, pratique...l'utilisateur ABD est root... bref rien a faire :)

LEs partitions sont identifiées, je vais dumper les ROM et vous tiens au courant

C'est ma seconde tablet android, je me demande si cette petite tablet a un 'Restore Mode' et quelles sont les combinaisons de touches pour y accéder...

J'ai essayé les trucs évidents mais rien...une idée ?

Bin

Modifié 3 mai 2012 par bin

[bin]

Voici la procédure des dumps des partitions system et data reussie et quelques hypothèses sur les autres partitions avec tentative de montage

NAND DUMPS

NANDA : /dev/block/nanda (fat16)

# dd if=/dev/block/nanda of=/mnt/extern_sd/nanda.dump
32768+0 records in
32768+0 records out
16777216 bytes transferred in 3.970 secs (4225998 bytes/sec)
# ./adb pull /mnt/extern_sd/nanda.dump

Comme je ne sais pas ce que c'est que cette partition, un petit coup d'oeil avec un editeur hexa pour voir si je peux la monter...

C'est un systéme de fichier en FAT16, On va donc tester de la monter en vfat...

# mkdir vnanda
# mount -o loop -t vfat nanda.dump vnanda
# tree vnanda
vnanda
├── app_demo.axf
├── boot.ini
├── drv_de.drv
├── drv_demo.drv
├── drv_nand.drv
├── drv_sd.drv
├── linux
│   ├── ??
│   │   ├── android
│   │   └── android.bmp
│   ├── ???
│   │   ├── android
│   │   └── android.bmp
│   ├── ???2
│   │   ├── android
│   │   ├── android.bmp
│   │   └── opening24.bmp
│   ├── android
│   ├── android.bmp
│   ├── bImage
│   ├── epuda1
│   │   ├── android
│   │   └── android.bmp
│   ├── epuda2
│   │   ├── android
│   │   ├── android24.bmp
│   │   └── android.bmp
│   ├── linux.ini
│   ├── params
│   └── youduo
│	   ├── android
│	   └── TELE System 32.bmp
├── magic.bin
└── wpower.drv
7 directories, 27 files
# umount vnanda

Il semble que ce soit la partition de boot, je verais apres avoir essayé de monter toutes les partitions...

NANDB : /dev/block/nandb (???)

# dd if=/dev/block/nandb of=/mnt/extern_sd/nandb.dump
32768+0 records in
32768+0 records out
16777216 bytes transferred in 4.260 secs (3938313 bytes/sec)
# ./adb pull /mnt/extern_sd/nandb.dump

Le contenu de la partition nandb est assez disparate

Cela ne m'apprend rien sur la nature de la partition

SYSTEM : /system => /dev/block/nandc (ext4)

# dd if=/dev/block/nandc of=/mnt/extern_sd/system.dump
524288+0 records in
524288+0 records out
268435456 bytes transferred in 76.130 secs (3526014 bytes/sec)
# adb pull /mnt/extern_sd/system.dump
# mkdir vsystem
# mount -o loop -t ext4 system.dump vsystem
# ls -l vsystem
total 32
drwxr-xr-x 2 1009 1009  1024 févr. 22 02:20 app
drwxr-xr-x 2 1009 1009  5120 févr. 22 02:20 bin
-rwxr--r-- 1 1009 1009  1426 févr. 22 02:20 build.prop
drwxr-xr-x 8 1009 1009  1024 févr. 22 02:20 etc
drwxr-xr-x 2 1009 1009  1024 févr. 22 02:20 fonts
drwxr-xr-x 2 1009 1009  1024 févr. 22 02:20 framework
drwxr-xr-x 6 1009 1009  4096 févr. 22 02:20 lib
drwx------ 2 root root 12288 févr. 22 02:20 lost+found
drwxr-xr-x 3 1009 1009  1024 févr. 22 02:20 media
drwxr-xr-x 2 1009 1009  1024 févr. 22 02:20 preinstall
drwxr-xr-x 2 1009 1009  1024 févr. 22 02:20 sun3i_conf
drwxr-xr-x 7 1009 1009  1024 févr. 22 02:20 usr
drwxr-xr-x 2 1009 1009  1024 févr. 22 02:20 xbin
# umount vsystem

DATA : /data => /dev/block/nandd (ext4)

# dd if=/dev/block/nandd of=/mnt/extern_sd/data.dump
1048576+0 records in
1048576+0 records out
536870912 bytes transferred in 155.700 secs (3448111 bytes/sec)
# adb pull /mnt/extern_sd/data.dump
# mkdir vdata
# mount -o loop -t ext4 data.dump vdata
# ls -l vdata
total 32
drwxrwxr-x  2 romain romain  1024 mai	3 02:49 anr
drwxrwxrwx  2   1009   1009  1024 mai	3  2012 app
drwxrwx--x  2 romain romain  1024 janv.  1  2010 app-private
drwx------  4 romain romain  1024 janv.  1  2010 backup
drwxrwxrwx  2 root   root	1024 janv.  1  2010 camera
drwxrwx--x  2 romain romain  4096 mai	3  2012 dalvik-cache
drwxrwx--x 41 romain romain  3072 mai	3  2012 data
drwxr-x---  2 root	 1007  1024 janv.  1  2010 dontpanic
drwxrwx--x  3   2000   2000  1024 janv.  1  2010 local
drwxrwx---  2 root   root   12288 févr. 22 02:21 lost+found
drwxrwx--t 11 romain   9998  1024 janv.  1  2010 misc
-rw-------  1 romain romain   111 avril 26 21:19 pointercal
drwx------  2 root   root	1024 mai	3 01:23 property
drwxrwx---  3 romain   2001  1024 janv.  1  2010 root-cache
drwx------  3 romain romain  1024 janv.  1  2010 secure
drwxrwxr-x  7 romain romain  1024 mai	3  2012 system
-rw-rw-rw-  1 root   root	   0 janv.  1  2010 system.notfirstrun
# umount vdata

NANDE : /dev/block/nande (fat32)

# dd if=/dev/block/nande of=/mnt/extern_sd/nande.dump
2291712+0 records in
2291712+0 records out
1173356544 bytes transferred in 372.140 secs (3152997 bytes/sec)
# ./adb pull /mnt/extern_sd/nande.dump

Un coup d'oeil sur le fichier,

nous indique que c'est une partition en FAT32

# mount -o loop -t vfat nande.dump vnande
# tree vnande
vnande
├── DCIM
│   └── 100ANDRO
├── download
└── LOST.DIR

4 directories, 0 files
#umount vnande

Il semble que ce soit le systéme de fichier original qui est present sur cette partition.

Je continus mes investigations, si quelqu'un a un tuyaux pour passer la tablette en mode recovery, faite le moi savoir ?

Bin

Modifié 3 mai 2012 par bin

[bin]

Salut,

Bon je suis toujours en train d'essayer d'identifier les partitions et surtout d'essayer de comprendre la procédure de boot de la tablette. Je commence a me rendre compte que la tablette basée sur le F20 est très proche des tablettes basées sur le A10 "allwinner". J'ai donc trouvé la procédure pour mettre la tablette en bootloader avec les outils specifiques.

PARTITIONS MAP

Je peux commencer dresser une carte, mais la partition de boot me pose problème, je n'arrive pas à identifier le bootloader. Il y'a des fichiers qui semble inutilisé sur la nanda ce qui ne facilite pas le reverse.

Nand Map (temporaire) :

nanda : BOOT : Partition de boot + noyau linux (la partition est sale)

nandb : UNUSED : Semble non utilisée (certains fichiers de boot y font reference en root=)

nandc : SYSTEM : Montée sur /system

nandd : DATA : Montée sur /data

nande : FS : / (Aussi montée sur /mnt/sdcard)

ALLWINNER

Ce fabrquant fournis entre autre le fameux A10, les architectures sont relativement proche, on trouve un peu d'info sur ce processeur, et surtout il existe un fork "allwinner" officiel du kernel linux pour cette famille.

A10

F20

AllWinner Technologie : http://www.allwinnertech.com

Il existe un outils "LiveSuit" qui permet de flasher la NAND des processeurs allwinner en mode bootloader

Download LiveSuitPack_version_1.09_20111101 (with english language):

http://www.tablettedroid.com/?wpdmact=process&did=MTUzLmhvdGxpbms=

RESTORE OU BOOTLOADER ?

Je confirme qu'il n'y a pas de mode "restore" sur cette petite tablette, par contre il est possible de passer le tablette en mode bootloader et grave a l'outils "LiveSuit" de flasher la NAND.

J'ai effectué l'installation (windows only) sur un Win7 (avec les driver usb dédié), la tablette semble être détectée, je n'ai pas encore tester de flasher.

Pour passer la tablette en mode bootloader :

1 - La tablette doit être eteinte

2 - Maintenez appuyé la touche "Volume +"

3 - Brancher le cable USB au PC

4 - Et tout de suite après appuyez 5 fois très vite sur le bouton "power"

5 - La tablette semble rester éteinte, mais Windows détecte un device inconnus, indiquer les pilotes LiveSuit et zooo...

6 - Une fois les bidouilles terminées, sortez votre trombone et faite un hard reset en le glissant dans le trou a coté du bouton "power".

Je cherche donc a bien identifier la mecanique du bootloader avant de flasher quoi que ce soit, je cherche aussi a créer un fichier image unique pour utiliser déja sous LiveSuit avant de reflechir a un update.zip

Bin

Modifié 4 mai 2012 par bin

[Looping08]

Salut

J'allais poster pour dire que je venais de recevoir cette petite tablette POLAROID ... !!! en cadeau pour avoir commandé des fournitures de bureau, cool pour moi qui découvre le monde Android :D

Mon 1er réflexe a été de vouloir télécharger quelques Apps que j'ai sur ma Galaxy Tab 10.1 en 3.2 mais ... NON pas comme ça que ça marche :(

Donc ma question est moins technique que celle de bin (bien choisi le pseudo :P )

Comment faire pour télécharger des Apps sans accès à Google Play ?

je rappelle que je suis un vrai de vrai newbie et que je suis en apprentissage, donc je découvre Android 2.3 après 3.2 de ma tab

merci de votre indulgence ^_^

A bientôt

Looping ;)

[bin]

Salut Looping,

Oops je n'avais pas vu ton post hier...Bienvenu, et cool d'avoir un deuxieme utilisateur de ces petits bidules...

:) je dois commander mes fournitures aussi chez JPG :)...

Si je trouve un gAppMarker.apk je te tiens au courant....

Regarde aussi dans "télécharger" sur la tablet puis clique sur le bouton menu...

Si non, J'ai encore du mal a comprendre la sequence de boot du F20, la partition semble comporter un vieux relicat du A10, je ne sais pas si les fichiers tons véritablement utilisé...

pas de boot.axf... serais ce le app_demo.axf le bootloader ?

# mkdir vnanda
# mount -o loop -t vfat nanda.dump vnanda
# tree vnanda
vnanda
├── boot.ini						  : Normaly used by boot.afx no ? (see content)
├── magic.bin						 : Normaly used by boot.afx no ? (see content)
├── app_demo.axf					  : Used by ? (ELF, Linker & Thumb Macro Assembler RVCT2.2 [build 349])
├── drv_de.drv						: Used by ? (ELF, Linker & Thumb Macro Assembler RVCT2.2 [build 349])
├── drv_demo.drv					  : Used by ? (ELF, Linker & Thumb Macro Assembler RVCT2.2 [build 349])
├── drv_nand.drv					  : Used by ? (ELF, Linker & Thumb Macro Assembler RVCT2.2 [build 349])
├── drv_sd.drv						: Used by ? (ELF, Linker & Thumb Macro Assembler RVCT2.2 [build 349])
├── wpower.drv						: Used by ? (ELF, Linker & Thumb Macro Assembler RVCT2.2 [build 349])
└── linux
├── bImage						: Linux Kernel (5.9 Mo)
├── linux.ini					 : Memory mapping ? (see content)
├── params						: Kernel cmdline ? (see content)
│
├── android					   : Splash Polaroid
├── android.bmp				   : Bmp Polaroid
├── ??
│   ├── android				   : Splash Android
│   └── android.bmp			   : Bmp Android
├── ???
│   ├── android				   : Splash Polaroid
│   └── android.bmp			   : Bmp Polaroid
├── ???2
│   ├── android				   : Splash Difrnce
│   ├── android.bmp			   : Bmp Difrnce
│   └── opening24.bmp			 : Bmp Difrnce
├── epuda1
│   ├── android				   : Splash MemUp
│   └── android.bmp			   : Bmp MemUp
├── epuda2
│   ├── android				   : Splash ACL
│   ├── android24.bmp			 : Bmp ACL
│   └── android.bmp			   : Bmp ACL
└── youduo
	   ├── android				: Splash Tele System
	   └── TELE System 32.bmp	 : Bmp Tele System
7 directories, 27 files

boot.ini

[system]
start_os_name = linux
timeout	   = -1
display_device= 0

[linux]

magic.bin

a1sp9maKde37ee6c-6dc4-4d74-86f0-db32116efb53e0e40ccf-7a66-406b-88c3-415b4a62a8f7777622ab-6bd0-464f-9da5-4cc203e855ea8ce5671f-e8b5-442e-9300-2ee6836c538aabf5f481-c961-4895-8245-631f74851d0c2bbb4229-55a8-4929-a165-3f406f0ee441ab5d09a9-c4dc-44bb-a175-cfb7c978a062329ea51e-1ddc-44ff-ac09-9ef7b64e0c52a712e47d-13f7-4490-9fea-bdcd587b8a4a5ed4d4e6-0ba3-45c5-a778-3232a42d4d960a9b7466-d7b3-4087-b8ff-c51763b852a50cd78bb6-a6d5-43a8-8661-fb91abd346433e8a86ee-711e-49c1-ad54-b59dd01fe513e22b0d8b-647f-4417-a115-9806c5d64eec

linux.ini

[segment]
img_name = c:\linux\bImage
img_size = 0x2000000
img_base = 0x80008000

[segment]
img_name = c:\linux\params
img_size = 0x100
img_base = 0x83008000

[segment]
img_name = c:\linux\android
img_size = 0x200000
img_base = 0x88200000


[script_info]
script_base = 0x83000000
script_size = 0x8000

[logo_info]
logo_name = c:\linux\android.bmp
logo_address = 0x88000000
logo_show = 1

params

console=ttyS0,115200 root=/dev/nandb rw init=/init;

Modifié 5 mai 2012 par bin

[Nicolasdes]

Comment faire pour télécharger des Apps sans accès à Google Play ?

Salut, je crée un autre sujet ( https://forum.frandroid.com/topic/102557-tablette-polaroid-43/ ) sur la tablette pour éviter de "polluer" celui de développement à bin. Je suis dans le même cas que toi.

Et bonne chance bin, je crois que tu es un des seuls à faire des recherches dessus !

Modifié 5 mai 2012 par Nicolasdes

[bin]

Salut Nicolasdes et Looping,

Cool de trouver des possésseurs de ces gadgets lowcost...

Si vous avez des tuyaux, n'hésitez pas :)...

Bin

[bin]

Salut,

Après avoir écumé le net sur tous ce qui touche au F20, allwinner, boxchip, socship, etc...Je n'ai pas trouvé de véritable réponse concernant la mécanique de boot du F20, du coup, j'ai commencé a passer la carte électronique au peigne fin et j'ai trouvé un port série (RS232) au niveau TTL.

UN PORT SÉRIE ACCESSIBLE

Dans le répertoire /dev on a bien un device (block) /dev/ttyS0, un petit test de transmission m'a permis de valider que c’était bien un port série.

# cat truc.txt > /dev/ttyS0

Les Niveaux électriques de la tablette et du PC sont différent (Tablette: TTL [0,5V] ; PC: [-12,12V] ), il faut quelques composants entre les deux pour faire cette adaptation. Ne branchez pas la tablette directement au PC dans l'état. Je n'ai pas eu le temps monter un petit max232 pour adapter le signal et voir ce qui sort de ce port.

Le truc intéressant, c'est que immédiatement après l'allumage une trame est émise par la tablette puis ensuite celle ci semble relativement bavarde durant le boot et même après...

ATTENTION : Vous pouvez endommager irrémédiablement vous ou votre matériel et/ou annuler votre garantie avec ce genre de bidouille, vous êtes seul responsable des problèmes que vous pourrez occasionner...

IMPORTANT:

Il faut que capot ferme sans forcer et surtout sans tordre la dalle, si non la tablette démarre mais la dalle tactile ne fonctionne pas, il y'a des composants sur la nappe, il ne doivent pas être compressé, j'ai été obligé d'enlever le scotch bleu que j'avais mis, il est vrai, un peu à l'arrache....

Pas facile de choper une trame avec l'appareil photo...avec une petite vidéo ce sera plus pratique pour faire des hypothèses...

Voici donc une hypothèse de ce que l'on peut s'attendre à recevoir sur le port série...

0:10 - Allumage, première trame émise immédiatement (Est le prompt du bootloader ?)

0:11 - Affichage logo polaroid

0:13 - Longue trame ~2sec (Est ce noyau linux ?)

0:17 - Courte trame

0:18 - Courte trame

0:23 - Courte trame

0:38 - Affichage logo android

0:54 - Courte trame (Est ce init ?)

0:55 - Courte trame

Etc....

Dès que possible je monte le max232 pour répondre a toutes ces questions, j'éspère surtout avoir des infos sur le bootloader...

Et si quelqu'un qui passe par là, sait a quelle moment le noyau linux est réellement chargée...

Est ce que le chargement ce fait avant ou pendant le splash Android avec la bar de progression ?

(j'ai l'impression que le noyau fini d'etre chargé et est lancé au moment du splash Android, il démarre précisément a 0:38, avant j'éspère que c'est le bootloader qui est bavard...)

Bin

Modifié 6 mai 2012 par bin

[bin]

Salut,

Après avoir bricolé un petit adaptateur RS232 un peu root, j'ai le plaisir de vous livrer un bootlog complet de du F20.

SETUP

Je n'ai pas de Max233 sous la main (la version 3.3V du Max232) donc j'ai fais ça à l'arrache avec un 2N2222A (en inverseur) une résistance de 2.2K sur la base et une de 1K en rappel sur le collecteur. Mon convertisseur USB/RS232 choppe le transitoire donc 5 V d'alim suffisent...c'est de l'expérimental :P

VIDEO

Une petite vidéo pour valider le timing du bootlog

BOXCHIP F20 BOOTLOG

HELLO! BOOT0 is starting!
initializing SDRAM OK.
Succeed in opening nand flash.
Succeed in reading Boot1 file head.
The size of Boot1 is 0x00030000.
The file stored in 0X00000000 of block 2 is perfect.
Check is correct.
Ready to disable icache.
Succeed in loading Boot1.
Jump to Boot1.
begin to init file system
bat vol = 3951
1
mount successfully.



[MSG]: BootMain start  
0  
The all optional count is 1  
only one os to boot  
WRN:L412(BootOS\BootOS.c):test for multi os boot with display  
WRN:L243(Common\ui\display_interface\display_interface.c):ERR: LCD not open  
WRN:L60(..\OSAL_Cache.c):Length is ZERO!  
start address = 0x80008000  
jump to  
[	0.000000] timer_set_mode: periodic
[	0.000000] Console: colour dummy device 80x30
[	0.220000] bio: create slab <bio-0> at 0
[	0.510000] request fb success!
[	0.520000] [uART]debug disable!
[	0.560000] The 0 disk name = BOOTFS, class name = DISK, disk size = 32768
[	0.570000] The 1 disk name = LROOTFS, class name = DISK, disk size = 32768
[	0.570000] The 2 disk name = LSYSTEMFS, class name = DISK, disk size = 524288
[	0.580000] The 3 disk name = LDATAFS, class name = DISK, disk size = 1048576
[	0.590000] The 4 disk name = UDISK, class name = DISK, disk size = 0
[	0.600000] The 4 disk size = 2291712
[	0.600000] part total count = 5
[	0.690000] ------ pmem ioremap cached -------
[	0.700000] CONFIG_USB_SW_SUN3I_USB0_OTG
[	0.700000] [sw_hcd0]: usb host driver initialize........
[	0.710000] [sw_hcd0]: [usb host]: usb_vbase	= 0xf1c13000
[	0.720000] [sw_hcd0]: [usb host]: sram_vbase   = 0xf1c00000
[	0.720000] [sw_hcd0]: [sw_hcd_host0]: close_usb_clock_ex
[	0.730000] [sw_hcd0]: [sw_hcd_host0]: open_usb_clock
[	0.770000] [sw_hcd0]: usbc_init_state = 1
[	0.770000] [sw_hcd0]: platform is usb host
[	0.770000] [sw_hcd0]: sw_hcd_host0: ConfigData=0xde (UTMI-8, dyn FIFOs, bulk combine, bulk split, HB-ISO Rx (X), HB-ISO Tx (X), SoftConn)
[	0.790000] [sw_hcd0]: sw_hcd_host0: hw_ep 0shared, max 64
[	0.790000] [sw_hcd0]: sw_hcd_host0: hw_ep 1tx, max 512
[	0.800000] [sw_hcd0]: sw_hcd_host0: hw_ep 1rx, max 512
[	0.810000] [sw_hcd0]: sw_hcd_host0: hw_ep 2tx, max 512
[	0.810000] [sw_hcd0]: sw_hcd_host0: hw_ep 2rx, max 512
[	0.820000] [sw_hcd0]: sw_hcd_host0: hw_ep 3tx, max 512
[	0.820000] [sw_hcd0]: sw_hcd_host0: hw_ep 3rx, max 512
[	0.830000] [sw_hcd0]: sw_hcd_host0: hw_ep 4tx, max 512
[	0.840000] [sw_hcd0]: sw_hcd_host0: hw_ep 4rx, max 512
[	0.840000] [sw_hcd0]: sw_hcd_host0: hw_ep 5tx, max 512
[	0.850000] [sw_hcd0]: sw_hcd_host0: hw_ep 5rx, max 512
[	0.850000] [sw_hcd0]: sw_hcd_init_controller: sw_hcd_host0: USB Host mode controller at f1c13000 using PIO, IRQ 38
[	0.870000] WRN:L271(drivers/usb/sun3i_usb/hcd/core/sw_hcd_core.c):ERR: hcd is not enable
[	0.880000] [sw_hcd0]: sw_usb_host0_disable start
[	0.880000] -------sw_hcd0_soft_disconnect---------
[	0.880000] [sw_hcd0]: INFO : USB VBus power OFF
[	0.880000] WRN:L370(drivers/usb/sun3i_usb/hcd/core/sw_hcd_core.c):ERR: hcd is not enable
[	0.890000] [sw_hcd0]: [sw_hcd_host0]: close_usb_clock
[	0.900000] [sw_hcd0]: sw_usb_host0_disable end
[	0.900000] [sw_hcd1]: usb host driver initialize........
[	0.910000] [sw_hcd1]: [usb host]: usb_vbase	= 0xf1c14000
[	0.920000] [sw_hcd1]: [usb host]: sram_vbase   = 0xf1c00000
[	0.920000] [sw_hcd1]: open_usb_clock
[	0.970000] [sw_hcd1]: usbc_init_state = 0
[	0.970000] [sw_hcd1]: platform is usb host
[	0.970000] [sw_hcd1]: sw_hcd_host1: ConfigData=0xde (UTMI-8, dyn FIFOs, bulk combine, bulk split, HB-ISO Rx (X), HB-ISO Tx (X), SoftConn)
[	0.990000] [sw_hcd1]: sw_hcd_host1: hw_ep 0shared, max 64
[	0.990000] [sw_hcd1]: sw_hcd_host1: hw_ep 1tx, max 512
[	1.000000] [sw_hcd1]: sw_hcd_host1: hw_ep 1rx, max 512
[	1.010000] [sw_hcd1]: sw_hcd_host1: hw_ep 2tx, max 512
[	1.010000] [sw_hcd1]: sw_hcd_host1: hw_ep 2rx, max 512
[	1.020000] [sw_hcd1]: sw_hcd_host1: hw_ep 3tx, max 512
[	1.020000] [sw_hcd1]: sw_hcd_host1: hw_ep 3rx, max 512
[	1.030000] [sw_hcd1]: sw_hcd_init_controller: sw_hcd_host1: USB Host mode controller at f1c14000 using PIO, IRQ 39
[	1.040000] [sw_hcd1]: INFO : USB VBus power ON
[	1.050000] sw_usb_disable_hcd1 start, clk_is_open = 1
[	1.060000] sw_hcd_stop: sw_hcd disabled
[	1.060000] [sw_hcd1]: INFO : USB VBus power OFF
[	1.060000] [sw_hcd1]: close_usb_clock
[	1.060000] -------sw_hcd1_soft_disconnect---------
[	1.070000] sw_usb_disable_hcd1 end
[	1.070000] [sw_hcd2]: usb host driver initialize........
[	1.080000] [sw_hcd2]: [usb host]: usb_vbase	= 0xf1c1e000
[	1.080000] [sw_hcd2]: [usb host]: sram_vbase   = 0xf1c00000
[	1.090000] [sw_hcd2]: open_usb_clock
[	1.130000] [sw_hcd2]: open_usb_clock, clk_is_open = 1
[	1.130000] [sw_hcd2]: usbc_init_state = 1
[	1.140000] [sw_hcd2]: platform is usb host
[	1.140000] [sw_hcd2]: sw_hcd_host2: ConfigData=0xde (UTMI-8, dyn FIFOs, bulk combine, bulk split, HB-ISO Rx (X), HB-ISO Tx (X), SoftConn)
[	1.150000] [sw_hcd2]: sw_hcd_host2: hw_ep 0shared, max 64
[	1.160000] [sw_hcd2]: sw_hcd_host2: hw_ep 1tx, max 512
[	1.170000] [sw_hcd2]: sw_hcd_host2: hw_ep 1rx, max 512
[	1.170000] [sw_hcd2]: sw_hcd_host2: hw_ep 2tx, max 512
[	1.180000] [sw_hcd2]: sw_hcd_host2: hw_ep 2rx, max 512
[	1.180000] [sw_hcd2]: sw_hcd_host2: hw_ep 3tx, max 512
[	1.190000] [sw_hcd2]: sw_hcd_host2: hw_ep 3rx, max 512
[	1.200000] [sw_hcd2]: sw_hcd_init_controller: sw_hcd_host2: USB Host mode controller at f1c1e000 using PIO, IRQ 40
[	1.210000] [sw_hcd2]: INFO : USB VBus power ON
[	1.210000]  
[	1.210000] ------------IRQ SESSION_REQ-------------
[	1.210000]  
[	1.210000] [sw_hcd2]: INFO : USB VBus power ON
[	1.220000] [sw_udc]: udc_init: version 20080411
[	1.230000] [sw_udc]: [sw_usb_udc]: binding gadget driver 'android_usb'
[	1.230000] [sw_udc]: alloc request: ep(0xc059db70, ep0, 64), req(0xcf92f120)
[	1.240000] WRN:L2369(drivers/usb/sun3i_usb/udc/sw_udc.c):ERR: usb device is not active
[	1.250000] Gadget Android: controller 'sw_usb_udc' not recognized
[	1.260000] WRN:L2369(drivers/usb/sun3i_usb/udc/sw_udc.c):ERR: usb device is not active
[	1.270000] [sw_udc]: CONFIG_USB_GADGET_DUALSPEED
[	1.270000] [sw_udc]: usbd_start_work
[	1.280000] [sw_udc]: alloc request: ep(0xc059dc70, ep4-bulk, 512), req(0xcf969e60)
[	1.290000] [sw_udc]: alloc request: ep(0xc059dc30, ep3-bulk, 512), req(0xcf969e20)
[	1.300000] [sw_udc]: alloc request: ep(0xc059dc30, ep3-bulk, 512), req(0xcf969de0)
[	1.310000] [sw_udc]: alloc request: ep(0xc059dc30, ep3-bulk, 512), req(0xcf969da0)
[	1.310000] [sw_udc]: alloc request: ep(0xc059dc30, ep3-bulk, 512), req(0xcf969d60)
[	1.330000] IR Initial OK
[	1.330000] [sun3i-ts:inf] sun3its_init is invoked.
[	1.340000] [sun3i-ts:inf] sun3i tp probe initial
[	1.340000] [sun3i-ts:inf]  
[	1.350000] [sun3i-ts:inf] sun3i tp inital ok
[	1.350000] sun3i RTC
[	1.350000] f20_rtc_probe tmp_data = 16385
[	1.370000] -----[cedar_dev] set ve clock -> 0x3040c019
[	1.370000]  
[	1.370000] ------------IRQ CONNECT-------------
[	1.370000]  
[	1.490000] [mmc]: awsmc controller unsing config sdc0 0, sdc1 0, sdc2 1, sdc3 0
[	1.500000] [mmc]: awsmc.2: pdev->name: awsmc, pdev->id: 00000002
[	1.510000] [mmc]: smc 2, source = video_pll0, src_clk = 297000000, mclk 99000000,  
[	1.510000] [mmc]: MMC Driver init host 2
[	1.520000] [mmc]: awsmc.2: Initialisation Done.
[	1.620000] m1 Audio successfully loaded..
[	1.620000] registered taskstats version 1
[	1.630000] incomplete xfer (32
[	1.630000] incomplete xfer (32
[	1.640000] incomplete xfer (32
[	1.640000] incomplete xfer (32
[	1.650000] incomplete xfer (32
[	1.650000] incomplete xfer (32
[	1.650000] incomplete xfer (32
[	1.660000] incomplete xfer (32
[	1.660000] incomplete xfer (32
[	1.660000] incomplete xfer (32
[	1.670000] incomplete xfer (32
[	1.670000] incomplete xfer (32
[	1.680000] incomplete xfer (32
[	1.680000] incomplete xfer (32
[	1.680000] incomplete xfer (32
[	1.690000] incomplete xfer (32
[	1.690000] incomplete xfer (32
[	1.690000] incomplete xfer (32
[	1.700000] [sw_hcd]: reset port.  
[	1.700000] incomplete xfer (32
[	1.710000] incomplete xfer (32
[	1.710000] incomplete xfer (32
[	1.710000] incomplete xfer (32
[	1.720000] incomplete xfer (32
[	1.720000] incomplete xfer (32
[	1.720000] incomplete xfer (32
[	1.730000] incomplete xfer (32
[	1.730000] incomplete xfer (32
[	1.730000] incomplete xfer (32
[	1.740000] incomplete xfer (32
[	1.740000] incomplete xfer (32
[	1.750000] incomplete xfer (32
[	1.750000] incomplete xfer (32
[	1.750000] incomplete xfer (32
[	1.760000] [sw_hcd]: reset port stopped.
[	1.760000] csr1: 0x2
[	1.760000] csr2: 0x0
[	1.770000] spurious?
[	1.770000] incomplete xfer (32
[	1.770000] incomplete xfer (32
[	1.780000] incomplete xfer (32
[	1.780000] incomplete xfer (32
[	1.780000] incomplete xfer (32
[	1.790000] incomplete xfer (32
[	1.790000] incomplete xfer (32
[	1.800000] incomplete xfer (32
[	1.800000] incomplete xfer (32
[	1.800000] incomplete xfer (32
[	1.810000] incomplete xfer (32
[	1.810000] incomplete xfer (32
[	1.810000] incomplete xfer (32
[	1.820000] incomplete xfer (32
[	1.820000] incomplete xfer (32
[	1.830000] incomplete xfer (32
[	1.830000] incomplete xfer (32
[	1.830000] incomplete xfer (32
[	1.840000] [sw_hcd]: reset port.  
[	1.840000] incomplete xfer (32
[	1.840000] incomplete xfer (32
[	1.850000] f20_rtc_gettime
[	1.850000] read time 2010-1-1 20:49:25
[	1.860000] EXT2-fs (nandb): error: couldn't mount because of unsupported optional features (244)
[	1.900000] [sw_hcd]: reset port stopped.
[	1.900000] csr1: 0x2
[	1.900000] csr2: 0x0
[	1.960000] [sw_hcd]: sw_hcd_h_disable, epnum = 0
[	1.960000] [sw_hcd]: sw_hcd_h_disable, epnum = 0
[	1.990000] EXT4-fs (nandb): warning: maximal mount count reached, running e2fsck is recommended
[	2.010000] VFS: Mounted root (ext3 filesystem) on device 93:8.
[	2.040000] init: /init.rc: 244: invalid option 'root'
[	2.040000] init: /init.rc: 244: invalid option 'root'
[	2.340000] invalid bits_per_pixel :0 in var_to_fb
[	2.380000] invalid bits_per_pixel :0 in var_to_fb
[	2.520000] EXT4-fs (nandd): warning: maximal mount count reached, running e2fsck is recommended
[	2.550000] init: not file /data/wipe_me
[	2.650000] EXT4-fs (nandc): warning: maximal mount count reached, running e2fsck is recommended
[	2.940000] EXT4-fs (nandd): warning: maximal mount count reached, running e2fsck is recommended
[	3.050000] init (1): /proc/1/oom_adj is deprecated, please use /proc/1/oom_score_adj instead.
[	3.060000] init: cannot find '/system/bin/memsicd', disabling 'memsicd'
[	6.060000] [DISP]open
[	7.760000] JBD2: Disabling barriers on nandb-8, not supported by device
[	8.070000] JBD2: Disabling barriers on nandd-8, not supported by device
[	8.070000] JBD2: Disabling barriers on nandc-8, not supported by device
[   36.310000] [DISP]open
[   36.450000] [DISP]open
[   36.870000] [DISP]open
[   38.150000] [sun3i-ts:dbg] suspend off
[   38.720000] usb_wifi_host = 2
[   38.730000] sw_usb_enable_hcd2 start, clk_is_open = 1
[   38.730000] WRN:L1552(drivers/usb/sun3i_usb/hcd/hcd2/sw_hcd2.c):ERR: sw_usb_enable_hcd2, usb clock is open, can't open again
[   38.750000]  
[   38.750000] rtw driver version=v3.1.2330.20110808
[   38.750000] register rtw_netdev_ops to netdev_ops
[   38.760000] CHIP TYPE: RTL8188C_8192C
[   38.760000]  
[   38.760000] usb_endpoint_descriptor(0):
[   38.770000] bLength=7
[   38.770000] bDescriptorType=5
[   38.780000] bEndpointAddress=81
[   38.780000] wMaxPacketSize=200
[   38.780000] bInterval=0
[   38.790000] RT_usb_endpoint_is_bulk_in = 1
[   38.790000]  
[   38.790000] usb_endpoint_descriptor(1):
[   38.800000] bLength=7
[   38.800000] bDescriptorType=5
[   38.800000] bEndpointAddress=2
[   38.800000] wMaxPacketSize=200
[   38.810000] bInterval=0
[   38.810000] RT_usb_endpoint_is_bulk_out = 2
[   38.820000]  
[   38.820000] usb_endpoint_descriptor(2):
[   38.820000] bLength=7
[   38.820000] bDescriptorType=5
[   38.830000] bEndpointAddress=3
[   38.830000] wMaxPacketSize=200
[   38.830000] bInterval=0
[   38.840000] RT_usb_endpoint_is_bulk_out = 3
[   38.840000]  
[   38.840000] usb_endpoint_descriptor(3):
[   38.850000] bLength=7
[   38.850000] bDescriptorType=5
[   38.850000] bEndpointAddress=84
[   38.860000] wMaxPacketSize=40
[   38.860000] bInterval=1
[   38.860000] RT_usb_endpoint_is_int_in = 4, Interval = 1
[   38.870000] nr_endpoint=4, in_num=2, out_num=2
[   38.870000]  
[   38.880000] USB_SPEED_HIGH
[   39.000000] Chip Version ID: VERSION_NORMAL_TSMC_CHIP_88C.
[   39.000000] RF_Type is 3!!
[   39.020000] EEPROM type is E-FUSE
[   39.020000] ====> ReadAdapterInfo8192C
[   39.030000] Boot from EFUSE, Autoload OK !
[   39.530000] i2c-1, xfer timeout
[   39.530000] Assertion failed! drivers/hwmon/mxc_mma7660.c,85,mma7660_read_xyz,result>=0
[   39.720000] EEPROMVID = 0x0bda
[   39.720000] EEPROMPID = 0x8176
[   39.730000] EEPROMCustomerID : 0x00
[   39.730000] EEPROMSubCustomerID: 0x00
[   39.730000] RT_CustomerID: 0x00
[   39.740000] _ReadMACAddress MAC Address from EFUSE = 00:13:ef:51:30:7b
[   39.750000] EEPROMRegulatory = 0x0
[   39.750000] _ReadBoardType(0)
[   39.750000] BT Coexistance = disable
[   39.760000] RT_ChannelPlan: 0x02
[   39.760000] _ReadPSSetting...bHWPwrPindetect(0)-bHWPowerdown(0) ,bSupportRemoteWakeup(0)
[   39.770000] ### PS params=>  power_mgnt(0),usbss_enable(0) ###
[   39.780000] ### AntDivCfg(0)
[   39.780000] readAdapterInfo_8192CU(): REPLACEMENT = 1
[   39.780000] <==== ReadAdapterInfo8192C in 760 ms
[   39.840000] rtw_macaddr_cfg MAC Address  = 00:13:ef:51:30:7b
[   39.840000] MAC Address from pnetdev->dev_addr= 00:13:ef:51:30:7b
[   39.870000] bDriverStopped:1, bSurpriseRemoved:0, bup:0, hw_init_completed:0
[   39.980000] +871x_drv - drv_open, bup=0
[   40.410000]  ===> FirmwareDownload91C() fw:Rtl819XFwImageArray_TSMC
[   40.410000] fw_ver=v75, fw_subver=0, sig=0x88c0
[   40.610000] fw download ok!
[   40.620000] Set RF Chip ID to RF_6052 and RF type to 1T1R.
[   41.360000] IQK:Start!!!
[   41.430000] Path A IQK Success!!
[   41.440000] Path A IQK Success!!
[   41.440000] IQK: final_candidate is 0
[   41.450000] IQK: RegE94=100 RegE9C=e RegEA4=fe RegEAC=2 RegEB4=0 RegEBC=0 RegEC4=0 RegECC=0
[   41.450000]  Path A IQ Calibration Success !
[   41.680000] pdmpriv->TxPowerTrackControl = 1
[   41.700000] MAC Address from REG_MACID = 00:13:ef:51:30:7b
[   41.700000] MAC Address = 00:13:ef:51:30:7b
[   41.700000] -871x_drv - drv_open, bup=1
[   42.360000] [rtw_wx_set_pmkid] IW_PMKSA_FLUSH!
[   42.360000] set_mode = IW_MODE_INFRA
[   42.380000] [rtw_wx_set_pmkid] IW_PMKSA_FLUSH!
[   44.060000] survey done event(11)
[   44.110000] set_mode = IW_MODE_INFRA
[   44.110000] wpa_set_auth_algs, AUTH_ALG_SHARED_KEY and  AUTH_ALG_OPEN_SYSTEM [value:0x3]
[   44.140000] wpa_set_encryption, crypt.alg = WEP
[   44.140000] (1)wep_key_idx=0
[   44.140000] wep, set_tx=1
[   44.140000] ==> rtw_set_key algorithm(5),keyid(0),key_mask(1)
[   44.140000] =>rtw_wx_set_essid
[   44.140000] ssid=subway, len=6
[   44.140000] new candidate: subway(00:0f:66:90:9b:f1) rssi:-65
[   44.140000] rtw_select_and_join_from_scanned_queue: candidate: subway(00:0f:66:90:9b:f1)
[   44.140000] <=rtw_wx_set_essid
[   44.140000] link to new AP
[   44.320000] link to Broadcom AP
[   44.340000] OnAuthClient
[   44.340000] OnAssocRsp
[   44.340000] report_join_res(5)
[   44.350000] HW_VAR_BASIC_RATE: BrateCfg(0x15d)
[   44.380000] HTOnAssocRsp
[   44.390000] update raid entry, mask=0x40000fff, arg=0x80
[   44.470000] rtl8192c_set_FwJoinBssReport_cmd mstatus(1)
[   44.480000] SetFwRsvdPagePkt
[   44.480000] Set RSVD page location to Fw.
[   44.480000] =>mlmeext_joinbss_event_callback
[   45.700000] rtl8192c_dm_RF_Saving(): RF_Normal
[   47.750000] rtl8192c_dm_RF_Saving(): RF_Save
[   51.720000] rtw_set_pid set pid[2]=207

SHUTDOWN:

[   95.450000] [sun3i-ts:dbg] [suspend_store]change before TPCTRL =0x200681
[   95.460000] [sun3i-ts:dbg] [suspend_store]change before TP_INT_CTRL=0xb0000723
[   95.470000] [sun3i-ts:dbg] suspend on
[   96.970000] [mmc]: awsmc.2: ShutDown.
[   97.010000] mmc_remove_host cf975800
[   97.060000] unregister_pm_notifier
[   97.060000] mmc_stop_host
[   97.070000] device_del
[   97.070000] led_trigger_unregister_simple
[   97.070000] [sw_hcd2]: close_usb_clock
[   97.080000] [sw_hcd1]: close_usb_clock
[   97.080000] WRN:L164(drivers/usb/sun3i_usb/hcd/hcd1/sw_hcd1.c):ERR: clock handle is null, sie_clk(0xc05876bc), phy_clk(0xc0587338), open(0)
[   97.090000] [sw_hcd0]: [sw_hcd_host0]: close_usb_clock
[   97.490000] Power down.

Kernel

# cat /proc/version
Linux version 2.6.36.4 (M10-Android-Team@Linux) (gcc version 4.3.3 (Sourcery G++ Lite 2009q1-203) ) #22 Sat Jan 14 09:39:23 CST 2012

J’espère que l'analyse de ce log me permettra d'avancer sur la mécanique de boot de ce satané F20 mais on peut déjà imaginé un tas de petite applications d'automatisme ou robotique légères avec Android comme contrôleur pour 40 dollars....

Modifié 6 mai 2012 par bin

[godeke-m]

Ah ah ma patronne ma demander hier ce que cela valais ^^ je lui ai dis d'oublier :P (480/272 WTF !!!! )

on as plutot commander le robot de cuisine XD

[matzpx8709]

Hi bin,

sorry for not writing francais. I have a similar device which is called (german) Touchlet pmt43-wifi.

It seems to be exactly the same, but i cannot flash it, because the menu key doesn't work.

Could you please give me the nand[a-e] - Images of the 4.3 Android ?

[bin]

Hallo Matzpx8709,

Thanks a lot for this good information, you get right, it's the same, this going to extend my search.

I dont get the nand[a-e] for 4.3 (ICS) yet, this is that why i play with the bootloader before bricking it, i let you know if i found someting for 4.3. For you key combinaison, did you try the last versions of "LiveSuit" (1.7 at least for F20). Be sur you use the LiveSuit USB driver. (i upload here if needed http://binbones.com/...20_LiveSuit.rar)

1/ Be sur the device is off

2/ Press and keep Vol+

3/ Connect USB (first time he ask to select LiveSuit driver)

4/ Try to press quicly 10 times power

5/ LiveSuite react, you can probably flash with....

An other thanks

Bin

Salut Matzpx8709,

Merci pour l'info, c'est le même modèle.

Je n'ai pas les partion nand[a-e] pour ICS 4.3, c'est pour ca que je fais quelques essais sur le bootloader avant de bricker le device. Pour la combinaison de touche, vérifis que LiveSuit est bien a jour (1.7 pour F20) et assure toi que le driver USB utiisé est bien le driver LiveSuit

(je l'ai uploadé ici si besoin http://www.binbones....20_LiveSuit.rar)

1/ Le device doit être eteint

2/ Presser et laisser appuyé Vol+

3/ Connect USB (La première fois vous devez intaller driver LiveSuit)

4/ Presser power 10 fois rapidement

5/ LiveSuite reagit, tu pourra peut etre flasher....

Encore merci

Bin

Modifié 9 mai 2012 par bin

[matzpx8709]

Hello bin,

many thanks for your driver, i will try that.

what i found out so far is, that you can have many sections in the boot.ini in the nanda-Partition:

mine looks as follows:

[

system]
start_os_name = linux
timeout	   = 5
display_device= 0

[linux]

[matz]

with this section matz, you can have a directory /boot/matz parallel to /boot/linux,

In this section matz, you have to have a "matz.ini" instead of a "linux.ini".

When you have, for example a [polaroid] section, you have a polaroid.ini

when you press power for 2 secs, then release power

then press vol+ 1 time, you select boot section matz,,

by pressing again vol+ 1 time, you select boot section linux.

by pressing shortly again polwer, you start the selected boot section.

by this way, you dont have to brick something. (the youda and all other dirs in linux arent needed, there are only alternative logos for boot in it. mine in section matz is internet.

i am reporting my experiences here again when i am further.

many thanks until here.

------------------------------

Hello bin again,

i tried your package on my tablet.

with your description of the keys, it worked now, that the driver installed.

But flashing isn't possible, because of an error, which is undeclared :-))

it is a messagebox with caption lifesuit and symbol "!" and message "" (blank)

------------------

when i am using livesuite 1.09 (from above link),

i am getting this message readable and it says "no device needs upgrade".

Modifié 11 mai 2012 par matzpx8709

[bin]

Hello matzpx8709 again,

what i found out so far is, that you can have many sections in the boot.ini in the nanda-Partition:

mine looks as follows:

...

with this section matz, you can have a directory /boot/matz parallel to /boot/linux,

Good information sir, can you tell me if you get boot.axf or app_demo.axf as stage 2 bootloader on nanda partition ?

Traduction : Matzpx8709 nous montre la nanda du pmt43, je lui demande quel fichier de bootloader est present sur la nanda

when you press power for 2 secs, then release power

then press vol+ 1 time, you select boot section matz,,

by pressing again vol+ 1 time, you select boot section linux.

by pressing shortly again polwer, you start the selected boot section.

Gooooood.....many thanks for this information, i heard about this but this indicate you get a real "boot.axf" not strange "app_demo.afx" as bootloader, did you confirm ?

Traduction : La procédure indiqué par Matzpx8709 permet de sélection un noyau au boot, je lui demande donc si il possède un boot.axf ou l'etrange app_demo.axf comme bootloader

i tried your package on my tablet.

with your description of the keys, it worked now, that the driver installed.

Good news

Traduction: La version de livesuit semble fonctionner

i am getting this message readable and it says "no device needs upgrade".

Wich firmware did you try ? this probably because it's not the good rom/device i read sometime.

Traduction: Son premier essais de flashage a echoué avec le message "Aucun periphérique n'a besoin d'être mis à jour", je lui demande avec quelle rom il a essayé

Many thanks matzpx8709 for you return and informations

I let you know too...

Bin

[matzpx8709]

Hi bin,

it is not boot.axf, it is app_demo.axf.

if you make (with linux) a strings app_demo.axf, you can see some keywords for the boot.ini.

and i tried both firwares, the one for android 4.0.3 and also for android 2.3 (Version 2.5).

as far as i saw in your tree of the nand, it is exactly identical.

also the `uname -a` is exactly the same.

another hint: i copied init to matz, hexedited the string "init.rc" to "matz.rc" and could experiment with it.

i tried to boot from sdcard, but this seems not to be working.

i tried to remount root on sdcard shortly after boot, but it seems that udev has to be run for creating the dev entries for sdcard (dev/mmcblk0p1)

if you could copy the nands from your android 2.3, i could investigate possible differences.

especially your nanda is of greater interest for me.

thank you so far ..

please come back ...

[bin]

Salut,

Pour ceux que ça intéresse, voici les dumps des partitions d'origine de la Polaroid MIDCF43 Android 2.3

ORIGINAL POLAROID MIDCF43 ANDROID 2.3 (F20 BOXCHIP) :

NANDA - BOOT (Fat16) - b67d9fb7fc5aaf3d0f358359b0288928 - 16,8 Mo

http://www.binbones.com/tablet/midcf43/dumps/stock/nanda.dump

NANDB -ROOTFS (Ext2) - a689dc51763072e7cf1af52f4c59ac7e - 16,8 Mo

http://www.binbones.com/tablet/midcf43/dumps/stock/nandb.dump

NANDC - SYSTEM (Ext4) - ab6a407a72d6fa0335a96a9370cbacbd - 268,4 Mo

http://www.binbones.com/tablet/midcf43/dumps/stock/nandc.dump

NANDD - DATA (Ext4) - cd3eb54f15d84632f5e1104105b3f9c0 - 536,9 Mo

NANDE - SDCARD (Fat32) - 082703878efad148092c854cde4bd984 nande.dump 1,2 Go

Bin

Modifié 9 mai 2012 par bin

[matzpx8709]

hi bin, hi all,

i can boot the polaroid kernel.

it differs in size 4 bytes and is not binary equal.

the serial number in my kernel is 59 while in polaroid kernel it is 22, also the dates differ.

my kernel version is:

Linux version 2.6.36.4 (M10-Android-Team@Linux) (gcc version 4.3.3 (Sourcery G++ Lite 2009q1-203) ) #59 Thu Nov 17 16:49:13 CST 2011

the polaroid kernel isnt able to boot from sdcard also.

because my device is registering also on linux with Bus 007 Device 002: ID 1f3a:efe8, i

will try lifesuite on another machine with a different windows (mine was win7 starter on a netbook).

Modifié 10 mai 2012 par matzpx8709

[matzpx8709]

hi all, hi bin,

its sad, i am not able to update to 4.0.3 with my device. neither the 1.07 nor the 1.09 neither in win7 nor in win xp does work.

but the other image with the android 2.3 is also not flashable on my device.

does someone know, who vendor id 1f3a is ?

in win xp i always get the message "no device available".

my last idea is, if i would get your roms of the 4.0.3, i could write them raw onto the device, but this is very dangerous, because they are mounted. (possibly remount ro, don't know if this works).

the filesizes of the drivers/bootprogram in the boot partition (nanda) are the same as in my "touchlet pmt43-wifi".

Modifié 10 mai 2012 par matzpx8709

[bin]

Hello Matzpx,

I think we break the "forum moderation rules" with english language, i 'm going to ask moderator for derogation but i think we may go to an english forum or wiki if you want...i follow you and stay here for french return....

its sad,...

It's a bad day for me too, i brick my own app_demo.afx say : "No OS to Boot !" i see on RS232 :)

I try to create a bootable mmc, not successfully but interested results

1 - I can show different number int app_demo.axf boot with keys combinaisons

2 - i think my card begin to boot and arm crash immediatly (opcode/sramaddr must me not valid)

(i need to investigate more)

... i am not able to update to 4.0.3 with my device. neither the 1.07 nor the 1.09 neither in win7 nor in win xp does work.

but the other image with the android 2.3 is also not flashable on my device.

...

in win xp i always get the message "no device available".

I try different ROM with same results XP&7, but i think this is a ROM/device "ID" probleme, what do you think about ?

does someone know, who vendor id 1f3a is ?

i think this is a AllWinner corp id or the "usb chip subset" supplier...i dont know

my last idea is, if i would get your roms of the 4.0.3, i could write them raw onto the device, but this is very dangerous, because they are mounted. (possibly remount ro, don't know if this works).

hum...I think the bootable mmc is a more safer way you always can recover...

the filesizes of the drivers/bootprogram in the boot partition (nanda) are the same as in my "touchlet pmt43-wifi".

Ok, can you publish your nanda ?

SYSRQ EMBEDDED

If you got a serial port, you can send a command to linux kernel with sysrq

(Change log level, show-registers, etc...) here is the help show by kernel

[   48.720000] SysRq : HELP : loglevel(0-9) reBoot Crash terminate-all-tasks(E) memory-full-oom-kill(F) kill-all-tasks(I) thaw-filesystems(J) saK show-memory-usage(M) nice-all-RT-tasks(N) powerOff show-registers(P) show-all-timers(Q) unRaw Sync show-task-states(T) Unmount show-blocked-tasks(W)

BOOTABLE F20 MMC : FIRST TRY

I try to create a simple binboot.S with theoricaly send "H" to UART0.

I use the A10 register map (from uboot and leechee), this will probably the probleme, i will disam the app_demo.afx to confirm the UART base addr.

1 - Fake bootloader

start:
ldr 	r0, =uartaddr
mov 	r1, #72
strb 	r1, [r0]


done: 	b 	done

uartaddr:
.word 0x01c28000

I build with

arm-none-eabi-as binboot.S -o  binboot.o

Remap with, (get this baseaddr from app_demo.afx disasm but it can be an other probleme)

arm-none-eabi-ld -Ttext=0x82800000 -o binboot.elf binboot.o

I got only executable code

arm-none-eabi-objcopy -O binary binboot.elf binboot.bin

2 - Create a All Winner mmc special binary

I found this https://github.com/hipboi/mksunxiboot

(and just discover https://github.com/amery/mksunxiboot)

This as the allwinner mmc header, i see the "jump address" in header, i need to investigate here

mksunxiboot binboot.bin binboot-mmc.bin

3 - Put it into mmc

sudo dd if=binboot-mmc.bin of=/dev/sdb bs=1024 seek=8
sync

4 - Result

A: When i put a standard mmc, app_demo.axf start and say "No OS found !" on serial port

B: When i put the custom mmc, dont see anything, app_demo.afx is not started, nothing on serial port

I thin F20 try to start by uggly code and crash and/or reboot indefinetly...sometime when i unplug the mmc, it restart immediatly and start app_demo.afx...

I need to enforce my ugly bootloader with good mapping and good serial uart register and be sure allwinner header jump is ok

I try to boot directly the app_demo.afx on cf, but nothing append, i think F20 search a Boot0 on mmc not a Boot1(app_demo.afx)

BUILD.PROP

In system/build.prop i can see this

# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=GRH55
ro.build.display.id=roller1.35_20120112.1353
ro.build.version.incremental=eng.kiming.20120106.115351
ro.build.version.sdk=9
ro.build.version.codename=REL
ro.build.version.release=2.3
ro.build.date=Fri Jan  6 11:55:59 CST 2012
ro.build.date.utc=1325822159
ro.build.type=eng
ro.build.user=kiming
ro.build.host=inet
ro.build.tags=test-keys
ro.product.model=sun3i
ro.product.brand=allwinners
ro.product.name=sun3i
ro.product.device=sun3i
ro.product.board=sun3i
ro.product.cpu.abi=armeabi
ro.product.manufacturer=unknown
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=exDroid
# ro.build.product is obsolete; use ro.product.device
ro.build.product=sun3i
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=roller1.35_release-sun3i-eng 2.3 GRH55 eng.kiming.20120106.115351 test-keys
ro.build.fingerprint=allwinners/sun3i/sun3i:2.3/GRH55/eng.kiming.20120106.115351:eng/test-keys
# end build properties
# system.prop for sun3i board
# This overrides settings in the products/generic/system.prop file

#add for 480*272 lcd panel
ro.sf.lcd_density=120	

rild.libpath=/system/lib/libreference-ril.so
rild.libargs=-d /dev/ttyS0

#
# ADDITIONAL_BUILD_PROPERTIES
#
ro.kernel.android.checkjni=1
ro.setupwizard.mode=OPTIONAL
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt

Whait is on you PMT-43 device /system/build.prop ?

Bin

Modifié 11 mai 2012 par bin

[matzpx8709]

hi bin,

if we are breaking rules of this board in writing english, lets go to an english forum. but maybe moderator is friendly.

my french is only two years in school, so i cannot write in french.

mai je aime la france. :-))))

i dont think, booting directly from mmc is possible.

eventually the way could be u-boot, wich can load kernel images and have a root on mmc.

have a look at github.com, there is a spain programmer called Alejandro Amery(amery), which is working on allwinner a10:

https://github.com/amery

there is also a kernel which contains allwinner sun3i (F20) code, but it isn't compilable, because of missing dma.c-routines.

he also worked on u-boot and sun4i (a10).

maybe that could help.

# begin build properties

# autogenerated by buildinfo.sh

ro.build.id=GRH55

ro.build.display.id=roller1.35_ruifu

ro.build.version.incremental=eng.inet_paul.20111114.105335

ro.build.version.sdk=9

ro.build.version.codename=REL

ro.build.version.release=2.3

ro.build.date=Mon Nov 14 10:57:13 CST 2011

ro.build.date.utc=1321239433

ro.build.type=eng

ro.build.user=inet_paul

ro.build.host=InetSoftware

ro.build.tags=test-keys

ro.product.model=PX-8709

ro.product.brand=allwinners

ro.product.name=sun3i

ro.product.device=sun3i

ro.product.board=sun3i

ro.product.cpu.abi=armeabi

ro.product.manufacturer=unknown

ro.product.locale.language=de

ro.product.locale.region=DE

ro.wifi.channels=

ro.board.platform=exDroid

# ro.build.product is obsolete; use ro.product.device

ro.build.product=sun3i

# Do not try to parse ro.build.description or .fingerprint

ro.build.description=roller1.35_release-sun3i-eng 2.3 GRH55 eng.inet_paul.20111114.105335 test-keys

ro.build.fingerprint=allwinners/sun3i/sun3i:2.3/GRH55/eng.inet_paul.20111114.105335:eng/test-keys

# end build properties

# system.prop for sun3i board

# This overrides settings in the products/generic/system.prop file

#add for 480*272 lcd panel

ro.sf.lcd_density=120

rild.libpath=/system/lib/libreference-ril.so

rild.libargs=-d /dev/ttyS0

#

# ADDITIONAL_BUILD_PROPERTIES

#

ro.kernel.android.checkjni=1

ro.setupwizard.mode=OPTIONAL

net.bt.name=Android

dalvik.vm.stack-trace-file=/data/anr/traces.txt

Modifié 11 mai 2012 par matzpx8709

[bin]

Hello matzpx809,

mai je aime la france. :-))))

:) i ask moderator, i wait repsonse...

i dont think, booting directly from mmc is possible.

Ho sorry, i'm not very clear...i dont want to boot linux directly inplace of boot0, i just want to inject a small piece of code witch send a 'H' char by serial port, this is a proof of concept, if i receive the H on my serial terminal, bingo ! it's possible to boot what we want and i will go to compile the rigth u-boot parameters....

How did you explain the boot behavior with a aw-tagged-mmc oppsit standard mmc ?

have a look at github.com, there is a spain programmer called Alejandro Amery(amery), which is working on allwinner a10:

https://github.com/amery

Yes there is a more recent for on github (that can compile well) and there is a lot of "all winner" things on git hub

there is also a kernel which contains allwinner sun3i (F20) code, but it isn't compilable, because of missing dma.c-routines.

he also worked on u-boot and sun4i (a10).

I dont find anything on "sun3i" only "sunxi" or "sun4i" and the same for u-boot, so...or i probably lost something ?

(F20 mem & reg must differt a lot from A10....)

Edit : suni (sc8600), le sunii (sc9800), sun3i (f20), sun4i (a10)

I you got the membase addr of boot0 and UART register for sun3i, let me know

Bin

Modifié 11 mai 2012 par bin

[matzpx8709]

hi bin, hi all,

seems that i am a litle stupid: in amery's git linux-allwinner there is a branch 2.6.36-474.....

i will try that and give you a result back.

[RELENA]

Bonjour,

J'ai cet appareil en ma possession cependant, je n'arrive pas à installer Googleplay pour télécharger des applications. Cet appareil n'est pas dans la liste de Googleplay.

Est-ce que quelqu'un connaîtrait une astuce pour arriver à télécharger par Googleplay quand même.

Merci d'avance.

Cordialement.

[Nicolasdes]

Pour le moment, c'est impossible. Mais tu peux utiliser androidPIT (https://forum.frandroid.com/topic/102557-tablette-polaroid-43/)

[matzpx8709]

Hello all,

i fond a chinese tool to unpack the img files of VX610W......rar, be careful, this is definitly not the right kernel nor boot for our device.

i tried the kernel out of V2.0.5 and this kernel does not boot.

Also, there is a boot.axf instead our app_demo.axf !.

i am maybe coming back with better news, we try some other channels.

i dont find anything on "sun3i" only "sunxi" or "sun4i" and the same for u-boot, so...or i probably lost something ?

(F20 mem & reg must differt a lot from A10....)

Edit : suni (sc8600), le sunii (sc9800), sun3i (f20), sun4i (a10)

I you got the membase addr of boot0 and UART register for sun3i, let me know

Bin

i meant _kernel_ sources, not _uboot_-sources with f20.

i did not find any f20(=sun3i) inserts in u-boot too. (like you did not).

But conceptually, u-boot is in my oppinion the right way.

other tablets do this also.