[project]Port android to meizu M8

what i don't understand is, when upgrade mode works why jtag eboot ?

Skoddi, at the moment r3wdy his upgrade mode is fuck** up.
so he is stuck with a semi working kernel and con not reverse.

So one option is through serial eboot menu, other one is by reflashing everything with the use of jtag.
Jtag has the advantage that you can experiment a lot more, if it is bricked you can reverse it back to original.

hope it makes it clear :-)

yeah i know but he wrote that his upgrade mode works so this is the point i dont understand ^^

no theupgrade mode wont start because the image in nand flash is destroyed. yaffs2 tried to "fix" tis fiesystem. WWe need to place android on movinand by aking 2 paritions there, and then check the init script of android so it ounts the right system and data partition. we can (should) use yaffs2 in this two paritions. I will do this when im t home this evening, and then i will too see why this dan plug has not yet arrived @ evow... maybe its lost. i love the post, i will send another one this evening

ok, thx ^^

i hope the jtag will work and you can finish the android boot

send your plug with a brick. it will get fast arrive.

Hi r3wdy,
how is/was Munich this time of the year?

about the plug, i will wait some longer on the postal services cause it seems that it will still take some time before ive got my m8 back
I will keep you posted ;-)

send your plug with a brick. it will get fast arrive

I am curious about the tric you will be using to restore your m8.
Hopefully it wont be any pain in the ass!

btw, your picture with booting the kernel seems to be removed from the internet

I gave a plug today to as firend of mine and he will try to solder 10 cables to it for me i hope he can do this so i could try dnw to restore my phone... right now im using a 6230 and it sux like hell :D

lol:-)
keep us posted !

Got two perfectly soldred cabels. each with 10 wires onnit.
But now my fucking ttl chip is fucked...........

grrrr

http://www.weebls-stuff.com/toons/Amazing+Horse/

Just build a converter and got nothing...
im thinking if i fucked up the serial port by doing something wrong.
If this happend i have only the jtag way left... but i dondt know, my ttl converter got fucked up yesterday night and im not the electonric engeneer to build a new one...

Im frustraded now...
I think i will buy one but this will take weeks to arrive and i want to do something...

Darn!
Seems you have all the luck at the moment ='(

Maybe you can buy a 'generic' cable with a TTL adapter in it and convert it to the 10pin USB plug?
Like suggested in this thread:
>>>How To Make China Phone Flash Cable<<<

But that is more like an addendum for this MeizuMe thread:
Howto: Serial Debug Connection

I get a working busybox that can accept serial input (by gettty) and have framebuffer console at sametime.

I used nfsroot on aesop rootfs yesterday, it failed after a android splash animation.
and I take two days to check all platform codes from google, my repo lose response lots of time.
I would like to make a failed animation as same as nfs, and store it in root.ext3.img so people can easiler for a easy test.

ok, chroot worked.
a please insert charge plug system raise up now.

Android firmware for Meizu M8.
Preview version r1, build with M8TinyLoader LiteXipBuilder(MPack) linux-2.6.27-m8-bill rootfs-aesop-20091011.
TODO: a dual boot xip.bin package in next week.

download mdroid_cuptools_r2_fixed.rar from here:
http://www.rayfile.com/en/files/cfe6...-0014221b798a/


separate package for people who can't download from rayfile or don't like rayfile download tools (raysource)
r2 fixed kernel in xip.bin format:
http://sourceforge.net/projects/rejacker/files/MPack/mdroid_cuptools_r2_xip_fixed.zip/download
r2 rootfs in mdroid.img format:
http://sourceforge.net/projects/rejacker/files/MPack/mdroid_cuptools_r2_rootfs.zip/download

update: replace link with zip version, I forget add tar before bz2 but can't access forum in these hours.
I added partition dection scripts to fix problem for some newer M8 which have different disk to me.
if you get yaffs hint and waiting at uclibc login, please try this fix.
boot in to upgrade mode, replace with fixed xip.bin and upgrade.

Kernel in xip.bin contains loader and busybox with Linux kernel.
After busybox get launched, he will try to find mdroid.img from your M8 disk.
The mdroid.img is an ext3 image that works like norflash in other mobile.
Your all changes make in android will write in this file only.
And OneNand driver is also disabled in this build.
It makes your M8 won't get such a cuptools (sadness in Chinese) like r3wDy.



Install:
Extract all files from downloaded archive first, then reset you M8 to flash mode (power + play button), copy xip.bin and mdroid.img to same place like you upgrade firmware.
It works as same as a normal firmware upgrade, so don't forgot backup your call history and mms.
when you pressed upgrade button, after some seconds your M8 stick will reappear in your computer. I suggest you overwrite xip with a stock MeizuOs xip.bin, this cheat make you can quickly roll it back when you need a phone, without a working usb connection.

Warning:
phone will not work. if you have important call, please flash in night or insert sim card to other handset.

Hint:
Keep your battery case opened or remove battery to use USB power supply.
This makes your can quickly soft reset when system halts.
you can copy files to M8 in upgrade mode.

Uninstall:
Flashing with a stock firmware. Remove mdroid.img from your disk. That’s all.

the xip.bin contains kernel bootloader for eboot and kernel.
the rootfs.img contains all files needs run android.

you can build your self rootfs like this:

create ext3 on a image file:

Code:

dd if=/dev/zero of=rootfs.img bs=1M count=100
/sbin/mkfs.ext3 rootfs.img

copy files into image we ceated you may need root account to mount / cp.

Code:

mkdir mountedext3
mount -o loop rootfs.img mountedext3
cp -r aesoproot/* mountedext3/
umount mountedext3

Fix a bug:
in file: gpio_keys.c
from
input_event(input, type, button->code, !!state);
to
input_event(input, type, button->code, !state);

after fixed,the key will normal.

when I press volume key, volume increse to max forever (may be a up -> down seq).
it's in meizum8_button.c in your config.
and touchscreen driver seems corrupt when key clicked.

there should a widget for softkeys but not this time.
I can go to make dualboot now, and study build platform later.

Originally Posted by banxian

when I press volume key, volume increse to max forever (may be a up -> down seq).
it's in meizum8_button.c in your config.
and touchscreen driver seems corrupt when key clicked.
.

yes,you just need Fix this bug in file meizum8_button.c
to
input_event(input, type, button->code, !state);

or the other better right way to fix:
in arch\arm\plat-s3c64xx\devs.c change:

static struct gpio_keys_button meizu_m8_button_table[] = {
{KEY_BACK, GPIO_MEIZU_KEY_HOME , 1, "Home button" , EV_KEY, 0, 20},
{KEY_MENU, GPIO_MEIZU_KEY_PLAY, 1, "Play button" , EV_KEY, 0, 20},
{KEY_VOLUMEUP, GPIO_MEIZU_KEY_VOL_UP, 1, "Volume up" , EV_KEY, 0, 20},
{KEY_VOLUMEDOWN, GPIO_MEIZU_KEY_VOL_DOWN, 1, "Volume down", EV_KEY, 0, 20},
{KEY_END, GPIO_MEIZU_KEY_POWER, 1, "power", EV_KEY, 1, 20}
};

@bill:
did your kernel have some fix on sd interface or mmc detecing?
it's not written in porting guild.
I noticed some delay changed, some debug printk add in init.
In my tests aesop kernel and stock linux 2.9.32 just can't find mmcblk0 on M8.

Originally Posted by banxian

@bill:
did your kernel have some fix on sd interface or mmc detecing?
it's not written in porting guild.
I noticed some delay changed, some debug printk add in init.
In my tests aesop kernel and stock linux 2.9.32 just can't find mmcblk0 on M8.

sorry, no fix on sd interface or mmc detecing yet.

Somebody can upload mdroid_cuptools_r1.rar on rapidshare or megaupload? because i can't download on rayfile...