dimanche 12 août 2012

MELE_android_4.0_vision 1.1 flash failure on Windows 7, bad PhoenixCard version!

In the previous post (New Mele A1000/A2000 ICS Android 4.0.4 firmware released) I announced a new firmware.
Seems that it fails to be flashed with PhoenixCard 3.0.3 on Windows 7 (thanks to JP for pointing it out, see the old post comments)
On mele.cn forum: http://bbs.mele.cn/showtopic.aspx?topicid=751&page=end someone has the same issue.
I never noticed this since I flashed from a Windows XP virtual machine.
The solution is to upgrade to PhoenixCard 3.0.6 on Windows 7, or run the tool on Windows XP.

I made a video from a Mele A2000 flash failure process. I got that when I was tweaking my firmware (missing DISKFS file):
Mele A1000/A2000  flash failure

Flash success sequence, for reference: Mele A1000/A2000 flash success.

17 commentaires:

  1. I've tested the Supercharger V6 with this release and works fine (http://forum.xda-developers.com/showthread.php?p=16635544#post16635544), and the AllwinnerMod (on the google play store) just to change the DPI (if you connect the mele to a big screen 120DPI is the best). I've applied the audiofix from the lundman site too, but it didn't work. I need to change the audio to software processing on MX Player (to hear mkv audio).

  2. Hi JP,
    please try this patch:
    Should work without software processing(referenced in this thread: http://bbs.mele.cn/showtopic.aspx?topicid=759&postid=2540#2540)

  3. I'll try it later.
    I'm thinking of recompile the kernel, I need some modules that are not found on the mele kernel.
    I guess I'll try the amery sources (https://github.com/amery/), hope it works. Do you know if there are some recommended ".config" to start?
    Thank you :)

  4. I successfully recompiled the kernel using this site :
    There is a specific configuration for mele A1000
    I used the linaro toolchain: https://launchpad.net/linaro-toolchain-binaries/+download
    But never tried to run it... yet :)

    1. I'll try this weekend, hope it works :)

  5. Hey Thierry,
    Look at this: http://bbs.mele.cn/showtopic-802.aspx (for all the audio problems)
    I've compiled the android kernel without problems, but it's a pain to update the running kernel and I don't have the debug cable to know whats happening, I know that is easy to build one, but I'm not on the mood.
    Maybe I'll try to update the kernel later.
    The next steps:
    1. Dump the kernel partition from nand
    2. Separate kernel from ramfs
    3. Build a new nand partition with the updated kernel
    4. write the partition and debug

  6. Have you managed to
    a) overclock the mele? (CM9 / AOKP on Mele 4.0 V1.0 OCs to 1.5Ghz, 4.0 V1.1 OCs to 1.1Ghz, can't find why)
    b) Set something to run automatically on startup? My edits to the .rc files just get reverted

    1. a) http://www.cnx-software.com/2012/05/06/editing-allwinner-a10-board-configuration-files-script-bin/

      b) If you use android download the SManager and open your script with that.

  7. Hey Thierry
    In the end, I didn't replaced the current running kernel, it's just a waste of time, what I did was:
    Download the last amery kernel from github (android 3.0 v2)
    make menuconfig ->
    - I've selected the extra modules that I needed
    - Changed the version of the kernel from 3.0.39 to 3.0.8+ (I know it's ugly, but who cares) so the modules compiled has "vermagic = 3.0.8+" (if vermagic != 3.0.8+ the modules cannot be inserted via insmod obvioulsy).
    - I've used the same toolchain that the guy at mele used: Codesourcery arm-none-linux-gnueabi and all it's working ok.

    1. Hi JP,
      Glad to see you finally made it work.
      Well, the internal kernel driver APIs change quite often and your compiled driver could lead to a kernel oops. Let's say that if it works 1 time, it works everytime :-)

      I will try to run the kernel I compiled for my mele device, should be easier to debug with the serial line.

    2. Yeah, I need the serial line badly, but I was checking the kernel messages with all the new compiled modules and all worked fine so far.
      Well, my experience tells me that if you have a 3.0 kernel, and you use a 3.0.X kernel to build a module for it, it should work without problems, even I've checked some "best practices" to port kernel modules for different kernels that says the same thing.
      If you need help just ask. :)

    3. Indeed, I need help :)
      What method did you use to modify and write your own kernel?
      This one: http://lundman.net/wiki/index.php/MeLe_A2000#Android_Kernel ?
      Seems that something misses in my modified nand image.
      When I compare the original nandc dump image and the modified image, I see a -rom1fs- section that disapeared.
      I got the u-boot interactive command line to get some boot information:

      boot_normal=nand read 40007800 boot;boota 40007800
      boot_recovery=nand read 40007800 recovery;boota 40007800
      bootcmd=run setargs boot_normal
      setargs=setenv bootargs console=${console} root=${nand_root} init=${init} loglevel=${loglevel} mac_addr=${mac}

    4. Remember that if you dump the nand partition you must "divide" it: the kernel section from the ramfs section using the split_bootimg.pl

    5. ahh I forgot, just use the amery kernel, the android 3.0 V2 sources.

    6. Hey Thierry do you have some kind of messenger client?

    7. Ce commentaire a été supprimé par l'auteur.

    8. you can contact me at brandoclio [}}@}}] gmail [}}dot}}] com

      (remove the extra characters)