[project]Port android to meizu M8

they do teamwork I think, and they don't flash the firmware by mzupdate (power+button), so they can't release a such one.
I think the video is real, because somebody from meizu tell me some wires connected to M8 in that video.

maybe bill is a meizu employer and he would lose his job ? *gg*

And i totaly agree. We should keep the Meizu updater intact if we dont have anything better that allows us to return to the original OS or to fix a broken installation.
So, Bill cant give us the 'finished product' but i hope the guide will help a lot =)

Originally Posted by Loonix

We should keep the Meizu updater intact

jup!

way1:
only M8TinyLoader injected into stock xip, both kernel/modules/rootfs/initramfs place on nand (with image or native file).
this may fit to normal user.

for dualboot from eboot this is the best option,
but i would change the idea if we would have jtag one day:
use the bootloader to define what to load,
so replace eboot with uboot, eboot can be backed-up first and any interested user can reflash if jtag is accesible
since building a jtag-cable cost maybe a 5-10 euro.
to continu:
booting a bin from movinand instead of nor is more interesting cause then you can create dualboot again..

http://www.gpswang.cn/bbs/viewthread...1&page=1&extra=

This product can update to dualbootmenu by normal way.
I want do like this update by xip.bin, but no idea to do yet.

Originally Posted by bill

http://www.gpswang.cn/bbs/viewthread...1&page=1&extra=

This product can update to dualbootmenu by normal way.
I want do like this update by xip.bin, but no idea to do yet.

this is the next things I would like to do.
you can have a look at MPack/M8TinyLoader Source in gitorious.
MPack - Gitorious
M8TinyLoader - Gitorious


I complie M8TinyLoader with visual studio to get a static PE without any library depency, then use LiteXipBuilder tools in MPack to convert it to flat memory layout then compress it to xip.

next version of loader/mpack will support inject code into a stock xip.bin (need a hardcore relocator/section drop algr), or a separate xip.bin which use gap space below eboot.
surely M8's eboot can be updated by MPack, but It's dangerous to end user so I disabled it by default.
I had send a special xip.bin which replace eboot to employer of Meizu, after a flash, his phone get to stone quickly. he can't press power+music anymore.

@bill:
do you have any suggestion to connect jtag pins on M8 with JLink?
I wanna use a mirrored thick PCB and place two stripe conductive rubber to contact with M8.

www.mobi28.com/m8/m8_jtag.asp

You can reference this page.

i think the solution with nk.exe which contains reals nk.exe and kernel is best for dualboot...
And i know it can be done.
Maybe we could just add our code int the space between 80000000 and 801000000 as banxian metioned. There is space and if we dont get it too big this must be possible. And maybe then we dont need any relocations becaue we wouldnt need to move the other data.
Therefore we would need the asm gpio codes to access the buttons. But i think they can be reversed

Before now anyone jumps on jtag i will stay and fight with android
Tried yesterday to get g_ether usb networking to run to use nfsroot which would be very very good for development, bet i wasnt succesfull.
Dunno why i need to stduy drivers kernelkonfig and bootlogs to find it.

Originally Posted by r3wDy

i think the solution with nk.exe which contains reals nk.exe and kernel is best for dualboot...
And i know it can be done.

I'll use a legacy solution. add a copy memory entry that target at end of main area (chain01) storage space, this can be done by MPack, and do a jump from OEP of original nk.exe (nk.exe must store as uncompressed in nb0), this makes less modify on nk.exe. two weeks ago I added nk.exe auto hack to modify it's ROMHDR retrieve code, I think it's safe.
surely I will test if shadowNk can recongize a startup point to copymemory entry.

There is space and if we dont get it too big this must be possible.

I'd like to place it and end of eboot (80003000 + phycsize in ROMHDR).

www.mobi28.com/m8/m8_jtag.asp

You can reference this page.

sorry, my problem is hwo to connect a wire to M8, a welded M8 should lost warranty I think. tape lots of pins always get circuit in poor contact, I shoud use my finger to hold it in debugging but I had a serious cough till last month I think it will kill me soon.

I find what he uploaded.




1. M8_eboot_Bootloader.rar,740KB,下载 0 次,MEIZU M8 WinCE Eboot Bootloader s3c6410
2. MEIZU_M8_Android_port_guide.zip,75KB,下载 0 次,meizu M8 Android s3c6410 移植指南,先移植内核，再移植andorid
3. SD-WLAN-BT-8688-FC8-MMC-10.38.2.p00-26609.P23_B1.t,4633KB,下载 0 次,marvell 8688 wifi Linux 驱动源代码
4. 6410_Android_SP_Installation_Manual_v0.2.rar,436KB,下载 0 次,三星s3c6410 Android移植文档，android篇
5. [Linux]_Installation_Manual_for_U-Boot_v2.8.rar,1328KB,下载 0 次,三星s3c6410 Android移植文档，uboot
6. m8_u-boot-1.3.4-sscr_onenand.tar.gz,11787KB,下载 0 次,m8 s3c6410 linux android启动的uboot
7. android_modify_ramdisk.img.rar,1KB,下载 0 次,浅析如何在android上生成我们自己的ramdisk.img启动系统文件
8. kernel_write_file.rar,1KB,下载 0 次,之前以为在内核中不能创建文件,其实不是这样子的,只要文件系统跑起来之后就可以像在用户空间一样操作 文件.
9. android_busybox.rar,5KB,下载 0 次,替换android默认的busybox,支持tab补全
10. M8_Android_portting_guide.rar,68KB,下载 0 次,M8 Android 移植指南,先移植内核，再移植andorid
11. u-boot-1.3.4_onenand090812.tar.gz,8096KB,下载 0 次,s3c6410支持Onenand启动的uboot
12. kino2.rar,221KB,下载 66 次,mplayer基于qtopia的播放界面.可在PDA,moto Linux手机上运行

m8 kernel source download:

1,if you want to boot from onenand flash,just "make zImage" is OK.
2,if you want to boot from nfs,remove select: "make menuconfig"--->General setup --->[] Initial RAM filesystem and RAM disk (initramfs/initrd) support,
then "make zImage" is OK.

www.mobi28.com/m8/m8_kernel.asp

m8 kernel download sorce
1,if you want to boot from onenand flash,just "make zImage" is OK.
2,if you want to boot from nfs,remove select: "make menuconfig"--->General setup --->[] Initial RAM filesystem and RAM disk (initramfs/initrd) support,
then "make zImage" is OK.

The only bad thing is that we worked so hard to see that most of ot was already done :P

But i must say, for start from scratch as we did, we did very succesfull :D

There are very very many thing to do yet.
This just finished a base kernel.
Now,because phone not work yet, need a dualbootmenu to boot return CE when you want phone function.

we knew this.
it was clear that runnung android makes no phone, maybe just a nice looking pda.
But this are things on which we can concentrate now, that we have a runing android build....
I remeber that the modem brings up status message when booting windows ce.. need to look what kind of modem this is then we can see further

about ril driver, I think you can use osdesigner to build a M8 CEROM n get phone work, then merge same patch to linux. maybe easiler because we can analyst phone componets change in stock firmware.

Originally Posted by r3wDy

we knew this.
it was clear that runnung android makes no phone, maybe just a nice looking pda.
But this are things on which we can concentrate now, that we have a runing android build....
I remeber that the modem brings up status message when booting windows ce.. need to look what kind of modem this is then we can see further

analyst usage of at command is enough I think. use IIC/etc to get hardware version, and read differnt serial for incoming call, send at command to dial.

Its a Hayes compatible modem @ com7 and 9 but i dont know what happens if i would send may ATD 0179xxxxxxx.
this would bring the modem do dail a number, but the audio must be connected to the speaker and mic and i dont know if this goes automagicly because the modem is wired to them or if the driver needs to do this.

One can see the AT commands sended to the modem by looking in Mux7_10.dll from meizu os.

But wait
I think about gsm modem drivers and dont even have adroid running. Hopefully this will change this evening so we can concrentrate on dualboot. And then we can concentrate on missing drivers.

But how do we organize android in the phone? if we want to keep it windows comaptible it would be no good to format the memory yffs2. so we should mount the flash through mtd swith vfat to stay windows comptaible. maybe create a android partition of about 200mb or so to bring a rootfilesystem in there

Guys,
there is so much to respond on, so i am not going to do it :P

@bill
if i would reflash nand with the uboot you uploaded, place kernel in nand
i would be able to get in a basic working android kernel?

About the jtag : is this normal jtag, ice jtag, other...?
Cause just found out that my old jtag cable is dead so i want to buy a new one with usb support :-) But then i will need to be sure what one i need..
(or maybe i will build one but have no parallel port anymore except on my old 80386 pc but that does not support the jtag tools i guess :P)

If i can acces jtag flash with the standard samsung tools i could backup my eboot and get started with a git for QI (better then uboot) and use the modified QI to provide a dualboot system to android and wince..
(i think for now this is more interesting to begin with, then we can keep on using the m8 with stock XIP that loads from /disk, and /disk we could repartition in lets say 1Gib for wince, 1Gib for linux, and the rest for storage of mp3, movies,..)


edit :
QI homepage
QI summary
QI GIT : git://git.openmoko.org/git/qi.git
Source for smartq qi dualboot system i am going to request asap...

edit:is it ok if we open-up a new topic [HowTo] Jtag connection
this to avoid that this topic gets evenmore couded?

[QUOTE=evow04;103606]Guys,
there is so much to respond on, so i am not going to do it :P

@bill
if i would reflash nand with the uboot you uploaded, place kernel in nand
i would be able to get in a basic working android kernel?

Yes,you can