[ISDNRaiser]

Hello,I`m new here and a new owner of an Eken M001. I bought it on ebay and received it today. A fast test seems good, it starts up and worked. Then we have to go and I turned it off with a long press on the powerbutton. He asked me to disable the phone module. I agreed and since them only get a black screen...

I`ve tried to flash a new room (stands here in the forum), but only get the fellowing errormessage:--> Erase File-System partition Fail! Exit!Maybe the kernel don`t support this NAND FlashThis error comes with original Eken M001 1.7.4 firmware...Now my quest is: Is it broken (then flashmemory)? Hope you can help me.With kind regardsISDNRaiser

 

[hellrazaa]

no its not broken its the sd card format... make sure you format it at 32kilobytes in the dropdown menu in windows.....sometime certain cards dont format right and it makes the firmware update not go through...that happened to me before

 

[ISDNRaiser]

thank you for the quick answer. But it doesn`t help. I formated a 4gb sd card to fat32 32kb, copied the files on it and the same error came. Is there another hint for me? I`m very unhappy with this situation. Thanks to all who can help. If the eken is broken, is there anybody who can repair it? I will pay for it, if it will work after it...

 

[Lupo1st]

Better use a SD Card with less Gigs - max. 2 GB - the others are most likely SDHC Cards - which might not work proper on flashing

 

[ISDNRaiser]

This still doesn`t work... everytime the same error...

also with 1gb and a 2gb card... oh man... this is disgusting... thanks for your help... but i think, i have a brick by now...

 

[tarpez]

download and install wince-rom then maybe the android rom will go.

 

[Kiddy]

I have the same issue. Anyone have a solution? Black screen on boot and this issue when i try to flash:"Erase File-System partition Fail! Exit!Maybe the kernel don`t support this NAND Flash"

 

[mammlouk]

It has nothing to do with the SDCard. I posted in the relax thread and then realized I wished I hadn't, because I don't want to clutter it up, so here is something to try.This is part of update.sh; lines 35 - 51. It tries to run the command

flash_eraseall /dev/mtd9

This is to completely wipe the system partition before copying any files. If the command doesn't exit with a status of 0 (Means no problems) then you get the message you are receiving. What you could do instead is comment out that section of code and go down to line 65 to add the following code (below 65 and above the "fi" in 66)

pointY=$(($pointY + $height))string="Now Exiting since we haven't cleared the partition...."echo $stringgui-echo $pointX $pointY "$string"exit 0

Now when you run the flash you it will skip the formatting the nand partition and just try to mount it. You will either get an message about it failing to mount or one about it working followed by the message above. The reason for exiting is because it's not a good idea to continue on with writing a bunch of files over the partition without erasing it first. If it comes back and says it can mount the partition let me know and I can tell you what to put in to manually erase all files before copying in the new ones from the rom. If it fails to mount then there is a problem with your unit's NAND and the only solution would be to replace it.

 

[Kiddy]

flash_eraseall /dev/mtd9[/CODE]This is to completely wipe the system partition before copying any files. If the command doesn't exit with a status of 0 (Means no problems) then you get the message you are receiving. What you could do instead is comment out that section of code and go down to line 65 to add the following code (below 65 and above the "fi" in 66)

pointY=$(($pointY + $height))string="Now Exiting since we haven't cleared the partition...."echo $stringgui-echo $pointX $pointY "$string"exit 0

Now when you run the flash you it will skip the formatting the nand partition and just try to mount it. You will either get an message about it failing to mount or one about it working followed by the message above. The reason for exiting is because it's not a good idea to continue on with writing a bunch of files over the partition without erasing it first. If it comes back and says it can mount the partition let me know and I can tell you what to put in to manually erase all files before copying in the new ones from the rom. If it fails to mount then there is a problem with your unit's NAND and the only solution would be to replace it.

Testing now, will let you know the result.I get:"Mount file-system partition OKNow Exiting since we haven't cleared the partition...."How should i continue to manually erase nand??

 

[mammlouk]

O.k. that's good, it means that your nand is mountable, but for some reason flash_eraseall isn't completing successfully. What you can do is keep the flash_erase code and the accompanying verification cases commented out, delete the code I had you add between lines 65 and 66, then add the following starting on line 67 (after "fi").

pointY=$(($pointY + $height))string="--> Erase File-System ......"echo $stringgui-echo $pointX $pointY "$string"rm -rf /mnt/mtdif [ $? -ne 0 ] ; then	string="Erase File-System Fail! Exit!"echo $stringgui-echo $pointX $pointY "$string"exit 0else	string="Erase File-System OK!echo $stringgui-echo $pointX $pointY "$string"fi

The bbcode is adding some extra line breaks, so makse sure you don't have any after the "then" or the "else". It also changed my greater than symbol in the first string line to ">", so make sure you fix that too. That should hopefully get the flash to complete for you.

 

[Kiddy]

pointY=$(($pointY + $height))string="--> Erase File-System ......"echo $stringgui-echo $pointX $pointY "$string"rm -rf /mnt/mtdif [ $? -ne 0 ] ; then string="Erase File-System Fail! Exit!"echo $stringgui-echo $pointX $pointY "$string"exit 0else string="Erase File-System OK!echo $stringgui-echo $pointX $pointY "$string"fi[/CODE]The bbcode is adding some extra line breaks, so makse sure you don't have any after the "then" or the "else". It also changed my greater than symbol in the first string line to ">", so make sure you fix that too. That should hopefully get the flash to complete for you.

Will try now! ... will come back with resultI say that your bbcode was changed by forum.My device now says:"Mount file-system partition OKErase File-system Fail! Exit""Doesnt sound good, Is it maybe possible to flash without erase ?

 

[mammlouk]

Hmm.. try changing the code to

rm -rf /mnt/mtd/*

and reflashing

 

[Kiddy]

Hmm.. try changing the code to

rm -rf /mnt/mtd/*

and reflashing

Crap, same fail"Mount file-system partition OKErase File-system Fail! Exit""Maybe flash without erase?! Is that possible?

 

[mammlouk]

You can try it. Just remove the code I had you add and leave the initial flash_eraseall stuff commented out.

 

[Kiddy]

You can try it. Just remove the code I had you add and leave the initial flash_eraseall stuff commented out.

Will try as last option. Do you have more tips on how to erase partition? Scary, i got this after flashing Relax 1.9.9....

 

[Kiddy]

I still have this error to erase partition. However i could boot up the device today after i didnt touch the device for 6hours :-o but after playing with it for 3minutes it freeze and could not boot up again (black screen).Is this maybe caused by Relax OC kernel ?Seems like if you let the device rest for a few hours then you can boot up. "hard shutdown" does not seem to work that well (maybe led is off but i guess device is still on). I'll try to drain the battery and retest.Please tell if you have seen this behaviour or have a solution. Thanks

 

[Kiddy]

What a piece of s*** I finally found a solution!This issues was probably couse by flashing the Relax OC ROM 530mhz!I turned off the device and didnt touch it for 2hours. Then i could successfully flash Original 1.9.1 and now flashed Mercury M002 without problems.I've treid 4reboots without problems so hopefully my device works fine now.Thanks for your help mammlouk

 

[mammlouk]

Glad to hear you got it running again. The kernel is fairly stable for most people, but overclocking is still extremelynew to these tablets and it seems there are many mixed experiences for how how some people can safely overclock their units. When you flashed the 1.9.1 and mercury roms were you able to do it without modifying the update script, or did you still have to bypass the partition format?

 

[Kiddy]

[quote name='mammlouk;62214]Glad to hear you got it running again. The kernel is fairly stable for most people' date=' but overclocking is still extremelynew to these tablets and it seems there are many mixed experiences for how how some people can safely overclock their units. When you flashed the 1.9.1 and mercury roms were you able to do it without modifying the update script, or did you still have to bypass the partition format?[/QUOTE'] I flashed it without changing anything in the script. So erase partition was fine after letting device be turned off for a few hours

 

[mammlouk]

Very interesting. I wonder if maybe the overclock was causing the whole SoC to get too hot and affecting the NAND.