[project]Port android to meizu M8

Its not an usb its an serial ttlconverter.
i checked the wirings to the chip, and shorting tx and rx pins right on the max232 echos back to terminal, so the chip should get the signals. I think its a problem with power or sth. Can i get the echo even if the chip has no power? (i dont have power from serial, i used the 3v from m8 pin to power the max232)

my co worker (which is electric engeneer) is working outside today so i cant ask him to have a look at my board if i made any error. But soldring a pre build board is normal not a great thing

if you mean for jtag pins, take a look in the jtag topic, i posted a very clever and easy way to secure the connection between jtag cable and pinout by using some plexi in the form of the battery...
(shame still no one answered on to it!!!)

I used a clear plastic in shape of the sim card, but i think using one shaped like the battery sounds better because its bigger and easier to handle. i will build such a thing this evening. For connection i will push needles through the plastic, this should be eneugh.

Another problem is, we cant write right into the nand. I saw a ilustration from samsung.
Here

Because of bad block management and stuff this should be done by the bootloader who is capable of manage this. So the way to go would be using eboot and dnw to start the image. if my serial port is damaged, i think i need to dump eboot and modofy it so it starts download everytime without user interaction, or use uboot (its easer to modify cause i can get the source of this)...

i wrote an email to meizu what it would cost to get it fixed... i just hope the damn serial port stil worx...

beeing honest,
it is to long ago that i used serial ttl, these days i only use usb ttl.
But i keep myself to it that you will need to power 232 chip with the vcc from m8 like you say. If you have a power reading on multimeter when connected to wire coming from m8 (1.0~3.3voltage for vcc and tx) it should power the serial chip. (so really - really double check this voltage readings on m8 side)

Can i get the echo even if the chip has no power

no : (

soldring a pre build board is normal not a great thi

normally not, that is if you soldered well and did not screw the leadings on pcb by overheating (like i did this weekend with mine )

a clear plastic in shape of the sim card

that is also a fine solution, but i think that way is harder to secure the connection between pins and m8 pcb, but i am sure you will keep us posted on how it worked out;-)

we cant write right into the nand

what?
you mean movinand i think?

uboot (its easer to modify cause i can get the source of this)

yes, i allready contacted bill with a request if he has the source or patches for m8 to be included in the source.
Then we could add wince boot support to it and flash this to your m8 instead of eboot. (beeing honest this is what i mostlikely will be doing in the future with mine, since i want to be running mer and android)

wrote an email to meizu

let us hope!

@ loonix, great !
i was interested if you liked yours, it could be that i will be ordering the same ttl is why i wanted to know :-)
Keep us informed ;-)

a co worker testes my ttl converter... it works...
so i need to have a look @ home if my serial port worx and maybe i need another 3v power supply.

I will try this right when im @ home this evening and then i will see if m8 serial ports still worx.

No i dont sayd movinand. have a look at the pdf i linked, the last page shows how to upgrade firmware through jtag

I found stock CE rom use a magic jump in the first 4 byte of nb0, too.
and I complete graphic menu display / serial check codes done this afternoon.
I will calculate distance and jump to my loader, then get a serial selectable xip after a short sleep.

So that is good but also not good news.

about jtag, ive read the pdf, but i am sceptic about it since bill (and a friend of banxian) claimed he flashed it over with jtag in the past.
It was posted somewhere in this topic.

found stock CE rom use a magic jump in the first 4 byte of nb0, too.
and I complete graphic menu display / serial check codes done this afternoon.
I will calculate distance and jump to my loader, then get a serial selectable xip after a short sleep.

cool!

We can surly write a bootloader. thats why nand maufactures guarantee that the first few block are error free.
To write to the whole nand you need to do a error block scan first, and this isnt done by jtag dirct. So you jtag a loader which loades the rest and can do this error block check.
Thta how i understood it

re-reading says to me indeed the same,
but to be sure we will need to wait until someone tries a full dump.

It is also possible that this full dump is not possible with normal jtag but with the higher end jtag devices.
Now Banxian has a jlink i thought, if he would manage to find some time between android compiling and his normal life, maybe he could try the dump?

edit; even then - you proved in the passed that bios fw loads a ce kernel that mounts directly after eboot. rewriting uboot to load this kernel and then updating eboot and others will still remain a solution...

Its not the dump problem its the write problem. Without checking for error blocks i cant write to any adress, because i dont know where error blocks are.

I see a way in first see if serial works. if it does i will just use dnw tool and eboot and we will be fine again. But if serial port is damaged i need to bring the bootloader in usb download mode on another way, maybe through dumping it, patcing it an reprogram it so it enters download mode everytime.

But thats alls speculation i will see when im @ home what i can do

ow sorry i made a typo, it was writing i ment indeed.

I complete graphic menu display

btw banxian, if you have screens, feel free to share ;-)
and good night for now!

alls speculation i will see when im @ home

i am curious, but will see ;-)

Originally Posted by evow04

btw banxian, if you have screens, feel free to share ;-)
and good night for now!

yes, that would be great....

aaah, i can't wait :D

okay dunno what this means...
i connected m8 so serial port, powerd on an some shit came trhough the line. nothing i could read.
i was disabpointed, but then i tried to echo something through my ttl and this echo isnt correct @ 115200. I get the correct echr (eg send r get r) on every baudrate < 19200 (every baudrate < 115200 @ terraterm) above this i get shit.
@ 115200 by r get an y and @ 38200 i get an = for n r...
tried this @ two different pcs.

i think if the echo in 115200 doesnt work, i cant read the phones messages. so i need first to correct this

if you echo you ttl, do you get the right value even in 115200?? If yes, i think some contact on my board may be soldred bad dunno... seems any shit of the universe centres @ my phone lol

Originally Posted by raangu

aaah, i can't wait :D

r3wdy, some bad and some good news;
normally using ttl debug you have only 1 working setting.
That is the one setup by the host you are targeting.
On M8 this means during eboot on baudrate 115200bps (other settings default) But that is with default factory state.
Since you screwed abit with removing blocks this setting could be completly different. so like any hacker does playing around with settings should provide you with fully readable characters.
If you get stuff like

Code:

||||@@#"##|`µ

this means you are using a wrong setting, but if you get this reading it means there is a connection.
If i understand well you were going to power ttl from another source, are you sure you used exactly 3.3volt?

Oww and in the past my m8 provide 1 character that rolls continously on HT when something was not correctly connected, just saying, you never know..

seems any shit of the universe centres @ my phone

i dondt hink that any of the settings in m8 has changed because bootloader workx. this would been damaged too if blocks in this area were damaged.

I know i get a connection, i can see linux boot in terminal, i can identify the charaters (for example, the uncompress linux and then some dots) i see this sequence but i cant read anything (Instead of "Uncrompressing linux.........." i get '432ß09adsc444444444444444'. i can clearly identify those '4' as the '.' from this message
when linux is booted, and press a button on my m8 there is a gpio message, i can see this coming too, right when i press the button. I see the msg coming, i just cant read it
So because of the timing and the order of the "shitstuff"§ i see that it conformes to that what is displayed on my screen.
Just the terminal doesnt show any readly stuff.
And, everytime i start m8 i get exactly the same "shit" so i know what ever comes to my terminal its alsway the same. thats a good sign :D

But as said, when i shorten rx/tx of my ttl converter and set baudrate to 115200, i also dont get the right echo, so why should the m8 msgs @ the same baudrate be right

So i have hope that it worx. the next i need is a ttl converter which converts @ 115200 right, then i maybe able to read the bootmsgs and then i think i will be able to send to the m8.

I tried all speeds from 2400 to 115200 nothing works readable. but for 2400 to 57xxx this is normal

dualboot menu worked with serial cable.
I press A for Android, C for MMobile (CE).

One hint:
When I select MeizuOS in select menu, it have a extra detection on power button, if power button been hold with in one second, CE boot up, else return to sleep. I think it may designed for prevent miss operation in power off mode.
that make I must to use Power for shortcut of CE menu, or user will get confused why they must push this key after touch.

@banxian,
if there was a photo showing the dualboot menu, that would be fantastic


Great thanks to you guys!

Originally Posted by r3wDy

thats a good sign :D

it is, but can you confirm how you were powering your ttl?

When i am @home tonight i will check if i can get some new life out of my ttl that i broke, if so i will pm you: i could send it through the postal service ...
(but beeing scared it wont arrive like your plug still did not arrive :s)

btw made any progress with jtag dumps?

dualboot menu worked with serial cable.

great! you are doing well it seems.
I think Meizu should contact you for helping within their development!
So in the initial boot system you made, you launch both the xip.bin from movinand or ? and can i find the source on your git?

I was thinking to write Meizu an e-mail with a new request for supporting us in the porting project, but no idea if it would have any succes.
Did they by any chance contacted you Banxian?
Cause to have all drivers correctly working their help could be welcome.

(but beeing scared it wont arrive like your plug still did not arrive :s)

Oh thats my fault, the second one i havt send till now. Just too much to do with my m8... the first one i think will never arrive... dunno where it is :/ I promise to send it these days.

I have a 3V adapter but mesured it hat slightly more than 3v (3.6 or so)

Another nice thing: i cant load my m8 battery anymore. I tried with ttl ujntil the battery got emtpy, and pluging the phone into the ac adapter doesnt loaded it. I tried the whole night. This morning i startet linux with battery inside, pwerd off, and it seemed to load again, but im not sure, i had to go to work. As i say, everything that can go worng goes wrong right now :/

So with the dualboot thing down, whats the status on Android drivers, last i heard was that a few worked, but what about the others?

copy 2.6.28 kernel drivers/mmc/core to 2.6.27 will get well effect for movenand.it will be found each boot!

okay ttl works @ 115200 but now m8 battrie is fucked up cant charge it. Need to buy a new one
im going to build usb/(serial cable now so i can use it without battery

okay false alert battery worx, adapter seems to be defect