升级android到tiny6410上失败

硬件为tiny6410，MLC Nand,我更新wince6和linux都能成功启动，然而更新android2.3.2却失败了，之前成功过。现象如下

Linux version 2.6.36-FriendlyARM (root@jensen) (gcc version 4.5.1 (ctng-1.8.1-FA
) ) #2 PREEMPT Fri Mar 25 12:28:26 HKT 2011
Kernel command line: root=ubi0:FriendlyARM-root ubi.mtd=2 rootfstype=ubifs  init
=/linuxrc console=ttySAC0,115200 androidboot.console=s3c2410_serial0
Creating 3 MTD partitions on "NAND 2GiB 3,3V 8-bit":
0x000000000000-0x000000400000 : "Bootloader"
0x000000400000-0x000000c00000 : "Kernel"
0x000000c00000-0x000080000000 : "File System"
UBI: attaching mtd2 to ubi0
UBI: physical eraseblock size:   1048576 bytes (1024 KiB)
UBI: logical eraseblock size:    1032192 bytes
UBI: smallest flash I/O unit:    8192
UBI: VID header offset:          8192 (aligned 8192)
UBI: data offset:                16384
UBI error: compare_lebs: unsupported on-flash UBI format

UBI error: ubi_init: cannot attach mtd2
PPP generic driver version 2.4.2

VFP support v0.3: implementor 41 architecture 1 part 20 variant b rev 5
one_wire_status: 4
s3c-rtc s3c64xx-rtc: setting system clock to 2000-02-22 21:32:01 UTC (951255121)

Freeing init memory: 1396K
UBIFS error (pid 752): ubifs_get_sb: cannot open "ubi0:FriendlyARM-root", error
-19
mount: mounting ubi0:FriendlyARM-root on /r failed: No such device
1Wire touchscreen OK
/init: line 103: can't open /r/dev/console: no such file
Kernel panic - not syncing: Attempted to kill init!
[<c016a9a4>] (unwind_backtrace+0x0/0xe4) from [<c04c31f8>] (panic+0x68/0x194)
[<c04c31f8>] (panic+0x68/0x194) from [<c01827e4>] (do_exit+0x68/0x664)
[<c01827e4>] (do_exit+0x68/0x664) from [<c018310c>] (do_group_exit+0xb0/0xe4)
[<c018310c>] (do_group_exit+0xb0/0xe4) from [<c0183150>] (sys_exit_group+0x10/0x
18)
[<c0183150>] (sys_exit_group+0x10/0x18) from [<c0165e60>] (ret_fast_syscall+0x0/
0x30)
one_wire_status: 2
Rebooting in 5 seconds..

出现上面这些错误，我认为应低格化nand flash可能会解决，但我进入uboot中，不支持format nand。请问如何解决上面这些问题？都是按照手册操作的，如下是

#This line cannot be removed. by FriendlyARM(www.arm9.net)

CheckOneButton=No
Action=install
OS= Android

VerifyNandWrite=No

StatusType = Beeper| LED

#################### Linux #####################
Linux-BootLoader = Linux/u-boot_nand-ram256.bin
Linux-Kernel = Linux/zImage_n43
Linux-CommandLine = root=ubi0:FriendlyARM-root ubi.mtd=2 rootfstype=ubifs  init=/linuxrc console=ttySAC0,115200
Linux-RootFs-InstallImage = Linux/rootfs_qtopia_qt4-mlc2.ubi
Linux-RootFs-RunImage = Linux/rootfs_qtopia_qt4.ext3

################### WindowsCE6 #################
WindowsCE6-Bootloader= WindowsCE6\NBOOT_N43-RAM256.nb0
WindowsCE6-BootLogo = WindowsCE6\bootlogo.bmp
WindowsCE6-InstallImage = WindowsCE6\NK_n43-i.bin
WindowsCE6-RunImage = WindowsCE6\NK_n43-i.bin

################### Android ####################
Android-BootLoader = Android/u-boot_nand-ram256.bin
Android-Kernel = Android/azImage_n43
Android-CommandLine = root=ubi0:FriendlyARM-root ubi.mtd=2 rootfstype=ubifs  init=/linuxrc console=ttySAC0,115200 androidboot.console=s3c2410_serial0
Android-RootFs-InstallImage = Android/rootfs_android-mlc2.ubi
Android-RootFs-RunImage = Android/rootfs_android.ext3

你烧的内核是3.25的，还不支持MLC2
请下载新版本的软件试试。

我使用网上的5月20号的rootfs_android.ubi ，出现一样的现象
Uncompressing Linux... done, booting the kernel.
Initializing cgroup subsys cpu
Linux version 2.6.36-FriendlyARM (root@tzs-i7pc.friendlyarm) (gcc version 4.5.1
(ctng-1.8.1-FA) ) #1 PREEMPT Wed May 18 21:05:10 CST 2011
CPU: ARMv6-compatible processor [410fb766] revision 6 (ARMv7), cr=00c5387f
CPU: VIPT nonaliasing data cache, VIPT nonaliasing instruction cache

NAND device: Manufacturer ID: 0xec, Chip ID: 0xd5 (Samsung NAND 2GiB 3,3V 8-bit)

Creating 3 MTD partitions on "NAND 2GiB 3,3V 8-bit":
0x000000000000-0x000000400000 : "Bootloader"
0x000000400000-0x000000c00000 : "Kernel"
0x000000c00000-0x000080000000 : "File System"
UBI: attaching mtd2 to ubi0
UBI: physical eraseblock size:   1048576 bytes (1024 KiB)
UBI: logical eraseblock size:    1032192 bytes
UBI: smallest flash I/O unit:    8192
UBI: VID header offset:          8192 (aligned 8192)
UBI: data offset:                16384
UBI error: validate_ec_hdr: bad VID header offset 512, expected 8192
UBI error: validate_ec_hdr: bad EC header
UBI error: ubi_io_read_ec_hdr: validation failed for PEB 0
UBI error: ubi_init: cannot attach mtd2
PPP generic driver version 2.4.2

要使用 tiny6410光盘上的 rootfs_android-mlc2.ubi

mindee说的使用5月20号的试下，但5月20号的没有rootfs_android-mlc2.ubi这个文件。
我用光盘提供的rootfs_android-mlc2.ubi文件，也是出现这个错误。

我觉得需要低格nand才行，用linux使用ubifs也是可以的