[project]Port android to meizu M8

Originally Posted by r3wDy

This evening i will clone the android branch from thier server compile it and will build a nfsroot with this. This evening i should have android up and running on m8 to see how the develpment continues.

ooh, that would have been too good
but good luck for further development

Ooh F*** it's the final goal??! After that we can run Android???

run android doesnt mean to use it...
bill already said that there is stlil no modem driver so no phone functionality will be avaliable at start. I dont know how it is with wlan and stuff....
Therefore we do dialboot at first while we develop further

Does this android created could be used on the new M8 SE version? Since beginning of Oct, the M8 SE version replace the old version.
Bill may have some idea about this SE version?

there are notmuch changes between m8 and m8se especially not in cpu/memory hardware so im pretty sure android would run just as good as on normal m8

indeed the most hardware should be still the same (except audio),
and same hack (xip mod) would be possible to use on SE.
Only serial debug and Jtag will need to be checked..

Btw R3wdy,
if you manage to run some kernels,
please spoil us with some more pictures!
Would love to see them!

with the paragon partition tools you can resize

You mean this ? and if so, You did it while using the bootcd or..?
Ow and did you notice if movinand was already been partitioned in 2 by factory or not?


btw
bad news; it could be that i wont receive a replacement meizu m8 since my reseller can not place his hands on the replacement i need .. bit pissed since the project finally gets somewhere.

yes this is what i used.
And mhn i saw only one partitiion on the movinand but this was 7,6 GB ansd not 8. now its 7,2 and 400mb ext2

Iwil spoil pix wenn android boots from rootnfs i will try this now

argh its all shit :D i have no dedicated linux machine and a ubuntu live cd has no nfs server so i need to install linux first...

i love this progress :D my first page i load in my browser every day is this thread...


alpha next week ? and can we test ist ? :D

Originally Posted by r3wDy

argh its all shit :D i have no dedicated linux machine and a ubuntu live cd has no nfs server so i need to install linux first...

R3wdy,
like i mentionned:
try dualboot with ubuntu and a bootloader like easyBCD
( saves the mess on MBR , howto link )
or try wubi his saves you time and removes easily afterwards!

wil spoil pix

woooeehoee!

7,6 GB ansd not 8

now that is logic since gb is a marketing trick and GiB is for all linux nerds like me, but i hoped it would show a hidden partition (still think it is there)

i love this progress :D my first page i load in my browser every day is this thread...

So that is why this topic has about 50.000 hits ?
lol

I repaired my multicable (serial+usb) right now. I think it can allow me use serial + nfs at same time.

VMWare can connect to real network, you do not need a phys installation.

in my tests, bill's kernel can build in to xip with litexipbuilder and startup, just like our aesop_M8 one.

atag memory configuation seems overwrited by hard code in both kernel.

our aesop based kernel will get a pointer dereference panic in onenand partition parsing.

It's not important now, yes I am going to write a lite touch screen position retrieve for bare M8TinyLoader, instead full driver in kernel, and detect which menu user clicked.

I just booted android (ife tried :D) over nfsroot, and the first parts of android wanted to start, but the movinand wasnt correct configured so i failed.

One problem now:
i cant reflash my m8 anymore back to meizu os because my upgrade mode got destroyed.

++ShadowNK()
ShadowNK : _ReadImage() ERROR...

Mhn what to do now??
luckyliy i have a working nfsroot so i could try to build a script (maybe with dd??) to write a new image to the device.

anyway i must flash the upgradesystem trhough rootnfs back to the device. Any idea how to do this? or can i reflash this through the samsung jtag cable?
Any ideas how to get my m8 back to work, because i cant do further development without upgrade system...

what a bad news!
how you get mzupdate broken?
by a kernel startup, or stone maker?

... mzupdate parts/partition on onenand (in other device use nor flash for xip) seems get corrupted.

A cheap LPT jtag cable can do this work but I can't confirm.

Android mounts mtdblock4 as system. mtdblock4 seems to be the upgradesystem patition or something
And it tried to mount it yffs2 but this is fat or somethig to i just killed the image

The only thing i think to get my m8 back is to write an init.rd script on the machine with nfsroot and use dd to write an binary image of the upgradesystem.
Following the logs android tried ti initialize its system on mtdblock4 which then seems to be just this partitiion

i tried to execute dd to dump parts of mtdblock4 but it dont know how exactly to do this, nor i really know the name if this device.
i tried dd if=/dev/mtdblock4 of=/test bs 1024
or
dd if=/mtdblock4 of=/test bs 1024

but nothing happens. this could be because my nfs system is mounted readonly...
so i tried
mout -o remount,rw /
to get it rw and then did touch test
but nothing happens....-

So i will try to build a jtag cable :/

Now i have a phone which boots an android kernel and wants to start it over nfsroot, but cant do this and cant get back to meizu os.

So any ideas how to geht the upgrade system back on the phone would be appriciated :D

Originally Posted by r3wDy

One problem now:
i cant reflash my m8 anymore back to meizu os because my upgrade mode got destroyed.
Mhn what to do now??

Can you press power + play button to enter the update interface.
If can, you can copy the xip.bin file from nfsrootfs: "cp nfs/xip.bin nfs/sdcard",then update by normal way.

I think it's impossible because update interaced is a running CE,
first of all he get his mzupdate corrupted.
and can't emulate in your kernel.

may be he want to use a "free" partition in kernel building but get mzupdate fucked.

quite right banxian.
I cant enter mzupdate.
as said it seems to me that mtdblock4 got destroyed by the yaffs2 FS driver and now the checksums arnt correct and it wont boot anymore.
What i now try to do is to remount the nfsroot writable and do a dd of this partition. then i will see if there are fragments of mzupdate innit. If i can find some there i can flash it back with dd i think.
or someone here from the forums makes a nfsroot and does a dd dump from his mtdblock4 and i write this intomy phone.

Another way i think i could go wuld be trhough jtag.
Can i flash with jtag to a defined adress in nand or can i just write form top?
If i cant flash it direkt to its location i could flash uboot, copy xip.bin fro biospack in ram and let it execute. it then will flash mzboot and mzupdate again.

Ill try :/ hope t get my phone back

r3wdy that is terrible news!
Hope you can fix it asap!

Can you press power + play button to enter the update interface.
If can, you can copy the xip.bin file from nfsrootfs: "cp nfs/xip.bin nfs/sdcard",then update by normal way.

lets hope it does the trick!

But i still did not understand what happened;
you mounted nor instead of movinand and trashed the upgrade system?

If you press the upgrade keys, do you notice "enter upgrade.." onscreen and get an error through debug cable that it can not find the data to proceed with..?

I hate to say it , but i was already a bit affraid this could happen one day.
Therefor it could be interesting to make backups of all data through jtag so everything can be flashed back to original...
@banxian(or bill), you have jtag?
could you try and dump those files, it could help r3wdy!

edit,
another way around:
patch a uboot to load wince from movinand?
(maybe we have this way the dualboot system)

[U-Boot] [PATCH] Add WinCE image load/boot cmd
[U-Boot-Users] U-Boot WinCE booting support?

the android startup script mounts a device called mtd@system and this was the problem. this mtd@system seems to bemtdblock4 and there is the updater i think.
So yaffs treid to "fix" the filesystem @ mounttime and this killed my image.

So
@banxian,bill
Anyone who could boot a linux kernel and do a diskdump of mtdblock4 and up is somwhere to me? i wil try to dd it into the system...

Originally Posted by r3wDy

the android startup script mounts a device called mtd@system and this was the problem. this mtd@system seems to bemtdblock4 and there is the updater i think.
So yaffs treid to "fix" the filesystem @ mounttime and this killed my image.

So
@banxian,bill
Anyone who could boot a linux kernel and do a diskdump of mtdblock4 and up is somwhere to me? i wil try to dd it into the system...

Hi,r3wDy
Pleae try this way:
http://www.mobi28.com/m8/M8_DNW_tools.asp

step by step:
1,power off M8.
2,connect USB line and serial line to M8.
3,Press space key enter eboot mode in serial console.
4,press u key
5,open DNW tools,if connect success,it will display [USB:OK]
6, select "USB port" --> "UBoot" ,select the xip.bin file download to M8.
7,if faile,try again 1-6.

@bill
see my reply in url=http://www.meizume.com/modding-development/9371-how-serial-debug-connection.html
, follow evow04's instruction, as he montioned, I can write UART2 but can't read.
so press enter takes no effect.
I need rework my serial cable to get right RX pin (maybe 7/8), then ask r3wDy to make a new one.