jeudi 9 août 2012

Mele A2000 custom firmware failure... fixed!

Indeed, the sole issue was the missing "DISKFS_000000000" file in image.cfg.

In a10_flash_kitchen_v2, here is the complete diff with the original file:

diff -uN files/image.cfg.orig files/image.cfg
--- files/image.cfg.orig 2012-02-15 13:15:08.000000000 +0100
+++ files/image.cfg 2012-08-09 13:33:47.264226709 +0200
@@ -58,17 +58,18 @@

     {filename = INPUT_DIR .. "_output\\bootfs.fex",           maintype = ITEM_ROOTFSFAT16, subtype = "BOOTLOADER_00000",},
     {filename = INPUT_DIR .. "_extract\\RFSFAT16_ENVIROMENT_00000.fex",           maintype = ITEM_ROOTFSFAT16, subtype = "ENVIROMENT_00000",},
+    {filename = INPUT_DIR .. "_extract\\RFSFAT16_DISKFS_000000000.fex",           maintype = ITEM_ROOTFSFAT16, subtype = "DISKFS_000000000",},
     {filename = INPUT_DIR .. "_input\\root.fex",   maintype = ITEM_ROOTFSFAT16, subtype = "BOOT_00000000000",},
     {filename = INPUT_DIR .. "_input\\system.fex", maintype = ITEM_ROOTFSFAT16, subtype = "SYSTEM_000000000",},
     {filename = INPUT_DIR .. "_input\\recovery.fex",   maintype = ITEM_ROOTFSFAT16, subtype = "RECOVERY_0000000",},
-    {filename = INPUT_DIR .. "_extract\\RFSFAT16_OEM_000000000000.fex", maintype = ITEM_ROOTFSFAT16, subtype = "OEM_000000000000",},
+;    {filename = INPUT_DIR .. "_extract\\RFSFAT16_OEM_000000000000.fex", maintype = ITEM_ROOTFSFAT16, subtype = "OEM_000000000000",},

     {filename = INPUT_DIR .. "_output\\vboot.fex", maintype = ITEM_ROOTFSFAT16, subtype = "VBOOTLOADER_0000",},
     {filename = INPUT_DIR .. "_extract\\RFSFAT16_VENVIROMENT_0000.fex",           maintype = ITEM_ROOTFSFAT16, subtype = "VENVIROMENT_0000",},
     {filename = INPUT_DIR .. "_output\\vroot.fex", maintype = ITEM_ROOTFSFAT16, subtype = "VBOOT_0000000000",},
     {filename = INPUT_DIR .. "_output\\vsystem.fex", maintype = ITEM_ROOTFSFAT16, subtype = "VSYSTEMFS_000000",},
     {filename = INPUT_DIR .. "_output\\vrecovery.fex", maintype = ITEM_ROOTFSFAT16, subtype = "VRECOVERYFS_0000",},
-    {filename = INPUT_DIR .. "_extract\\RFSFAT16_VOEM_00000000000.fex", maintype = ITEM_ROOTFSFAT16, subtype = "VOEM_00000000000",},
+;    {filename = INPUT_DIR .. "_extract\\RFSFAT16_VOEM_00000000000.fex", maintype = ITEM_ROOTFSFAT16, subtype = "VOEM_00000000000",},

     {filename = INPUT_DIR .. "_extract\\BOOT    _BOOT0_0000000000.fex",             maintype = ITEM_BOOT,   subtype = "BOOT0_0000000000",},
     {filename = INPUT_DIR .. "_extract\\BOOT    _BOOT1_0000000000.fex",             maintype = ITEM_BOOT,   subtype = "BOOT1_0000000000",},

Now the flash process succeeds, and the Mele HTPC boots succefully.
And I can begin to hack this box!
The sole thing that bothers me is the SDCard flash process that is still under Windows (using PhoenixCard), this is the only operation I need to perform under Windows.

My intention is to keep Android on this box. No linux distribution can boot as fast as Android, and Android is linux, why changing something that works?
Furthermore, it is possible to run linux commands on top of an Android OS (using the "chroot" trick), so my armedslack distribution will be able to run concurrently on this box.

To be continued...

5 commentaires:

  1. At this point do you get your Android working?
    can you modify the kernel and get it to boot? I seriously need the xpad module working (under Devices -> Input -> Joystick)
    Thanks

    RépondreSupprimer
    Réponses
    1. http://forum.xda-developers.com/showthread.php?t=1838478

      There's something that I've been working on without good results

      Supprimer
    2. The modified firmware works, but I did not touch the kernel itself. Since the kernel shipped within the firmware version is 3.0.8 and the "amery" version is 3.0.36 (currently), you cannot just compile a module with amery version and try to load on the mele version. You need to replace the whole thing.
      "JP" is trying to compile and run a new kernel (see the comments of http://tmerle.blogspot.fr/2012/08/meleandroid40vision-11-flash-failure-on.html), but this can be a hard task to have a working version of the kernel (missing options lead to recompile the kernel, revert to the stock firmware to get back to a stable version, ...)

      Supprimer
  2. hi i am also a developer i have downloaded the source for android ics for mele a1000 and compiled got the image and burned that image through phoenix in sd-_card but image is not working. I have tried with other lichee also but it dint came.PLEASE GIVE ME THE EXACT SOURCE AND STEPS FOR MAKING ANDROID FOR MELE A1000.I NEED SERIOUS HELP U CAN MAIL ME FOR THIS MAIL ID ALSO venkat.raghavvarma@gmail.com

    RépondreSupprimer
    Réponses
    1. I compiled once Android CM10.1 for Mele, based on this forum thread (see "ugers"'s posts):
      http://www.slatedroid.com/topic/40980-42-for-allwinner/
      Follow this (look at the README file):
      https://github.com/ugers/android_device_907

      But I did not get any further than running it, and seeing that it was far from useable (no HW acceleration, bad Ethernet setup, ...).
      I think a better start is to get CM9 (with HW acceleration):
      http://forum.xda-developers.com/showthread.php?t=1760929
      Use same method as ugers, but with christian_troy repository.

      All my customizations (further posts) are based on a Mele compiled firmware, I never recompile Android.

      Supprimer