Porting Andoid on A1200 MING

[biggerstone]

Hi,All:
i have downloaded a boot_usb tools from Revision 2367: /trunk/src/host/boot_usb. i make it successfuly under my Ubuntu 8.10
(Header file verison: /usr/src/linux-headers-2.6.27.7). My make file include is : INC ?= /home/administrator/andorid/linux-2.6.24/include.
If not setting this path, make error and output: asm-arm/setup.h:No such file or directory.

According with the guideline of "http://www.motorolafans.com/forums/android-os/21887-porting-andoid-a1200-ming.html", when i upload zImage-a1200 file to
Motorola Ming A1200 by usb_boot. An error occures:
administrator@ubuntu:~/boot_usb-0.2.0$ ./boot_usb zImage-a1200
Serching for EZX phone: E2/A1200/E6/A910 found.
FAILED: claim usb interface 1 of device: could not claim interface 0: Operation not permitted
administrator@ubuntu:~/boot_usb-0.2.0$
administrator@ubuntu:~/boot_usb-0.2.0$ pwd
/home/administrator/boot_usb-0.2.0

I add a item to /etc/udev/rules.d/45-libmtp8.rules according by "http://ubuntuforums.org/showthread.php?t=346840", but the problem still exist.

If anybody can tell me why???

[sabrod]

Good: with this bootusb, and a new kernel, you'll have a stable configuration.
Note that now, you almost need only ONE kernel for ALL the EZX devices, this is why you NEED a machid for newers kernels.

You probably need to sudo or be root...

Then because of a bug in pxa driver in linux, you need either to disable udc on your kernel or to use gen-blob (genblob initialise correctly udc before to launch the kernel)

You forgot the machine id, you can continue like this, but this way only work for "old" kernels...
After 2.6.25, the machid has to be specified. There is a far better support, amount of hardware supported on the actual kernel, you may prefer using it....

so:
Genblob has also to be launched with a special machid with bootusb:"0".

sudo ./bootusb genblob 0

This will enter the second stage bootloader, before to press enter, press the desired key on the phone :

-----------[vol+] go to genblob usb mode (let you do another bootusb, this time the phone will work perfect)
for ex., knowing A1200's machid is 1742.

sudo ./bootusb zImage 1742 "root=/dev/nfs nfsroot=192.168.0.200:/PATH/TO/YOUR/NFSROOT/EXPORT/ rootdelay=5 ip=192.168.0.202:192.168.0.200:192.168.0.200:255.255.255.0"

this is in case you prefer the rootfs on nfs. (note that the CMDLINE is quoted "").
the IP param. is : ip=<client-ip>:<server-ip>:<gw-ip>:<netmask>:<hostname>:<device>:<autoconf>
i didn't used the 3 lasts ---------------------------------------------------\__________________________/

----------[vol -] need an sd card, and will draw a boot menu. (you put the necessary in /boot/ in a first partition of sd formatted fat16 or 32)

----------[nothing] will boot the default kernel, maybe, if it exist.


See:
linuxtree/Documentation/nfsroot.txt
Dual boot - OpenEZX (for the more actual/functionnal _genblob_ way to go)
http://people.openezx.org/wyrm/gen-blob/README Complement to the link above.
http://www.motorolafans.com/forums/a...tml#post168526 (don't forget my posts )
Working bootusb, zImage to test are on Index of /gmzhuo you may prefer using them as they are tested...

[m_kawale]

plz tell how to do this in e6...
plz....

[sabrod]

m_kawale: I want you to read the 2nd line in the message i just post!!
it's exactly the same on E6, except you need to find the e6 machid from there:
http://www.arm.linux.org.uk/develope...s/download.php
Note that it's been said maybe 3 or 4 times in 7 pages.....

[biggerstone]

To sabrod:
my output looks like this:
administrator@ubuntu:~/boot_usb-0.2.0$ ./boot_usb zImage-a1200
Serching for EZX phone: E2/A1200/E6/A910 found.
FAILED: claim usb interface 1 of device: could not claim interface 0: Operation not permitted


Should i install a A1200 usb driver under my Host (ubuntu 8.10 ) when i connect A1200 to host via USB? I am a newer, i do't know if i must to do this.

[biggerstone]

Thanks sabrod, i can upload zImage file to my A1200.
administrator@ubuntu:~/boot_usb-0.2.0$ sudo ./boot_usb zImage-a1200
Serching for EZX phone: E2/A1200/E6/A910 found.
Sending mach id code 867: 100% OK
Uploading kernel: 100% OK
Calling the kernel...
DONE

But i have another problem. I can't telnet to my A1200. the result show following:
administrator@ubuntu:~/boot_usb-0.2.0$ telnet telnet 192.168.1.2
telnet: could not resolve telnet/192.168.1.2: Servname not supported for ai_socktype

After finished upload, my A1200 screen outpu something like this:
[I]usb 1-3: new full speed usb device using px027x-ohci and address 5
usb 1-3: device not accepting address 5, error -62
rpcbind: server 192.168.1.1 not responding, time out
Root-NFS: unable to get nfsd port number from server, using default
Looking up port of 100005/1 on 192.168.1.1
rpcbind: server 192.168.1.1 not responding ,time out
Root-NFS: Unable to get mountd port number from server, using default
mount: server returned error -5 while mounting /root/andoid_nfs
VFS: Unable to moubnt root fs via NFS, trying floppy.
VFS: Cannot open root device "nfs" or unknow-block(2,0)
Please append a correct "root=" boot option; here are the avaible paritions:
b300 243712 mmvblk0 driver:mmcblkb301 243660 mmcblkop1
Kernel panic -not syncing: VFS: unable to mount root fs on unknown-block(2,0)[/I]

I am sure that the path /home/android_nfs is correct by comman ls -l.

administrator@ubuntu:/home$ ls -l
total 24
drwxr-xr-x 42 administrator administrator 4096 2008-12-11 09:44 administrator
drwxr-xr-x 3 root root 4096 2008-12-11 09:35 android_nfs
drwx------ 2 root root 16384 2008-12-03 10:47 lost+found
administrator@ubuntu:/home$

POST: i make my Android Root NFS just as the first message of this post(See androidezx' post). should i modify my host IP address(it's 192.168.1.7)??

Why don't i get this output in my A1200 screen:
mount: server returned error -5 while mounting /root/andoid_nfs

Hopes your help,3x!

[biggerstone]

Hi all:
Could you help me? maybe i don't describe my problem clearly.
My target divice type is : A1200e(Not A1200). when i try another CMD with "boot_usb <kernel> [machid] [cmdline]" , My A1200E outputs nothing but some dot.
administrator@ubuntu:~/boot_usb-0.2.0$ sudo ./boot_usb zImage-a1200 1742 "root=dev/nfs nfsroot=192.168.1.7:/home/andriod_nfs rootdelay=5 ip=192.168.1.2:192.168.1.7:255.255.255.0"
Serching for EZX phone: E2/A1200/E6/A910 found.
Sending mach id code 1742: 100% OK
Uploading kernel: 100% OK
Calling the kernel...
DONE

If i change machid from 1742 to 876, there are something output in A1200e Screen.This string is :
...
rpcbind: server 192.168.1.1 not responding, time out
Root-NFS: unable to get nfsd port number from server, using default
Looking up port of 100005/1 on 192.168.1.1
rpcbind: server 192.168.1.1 not responding ,time out
Root-NFS: Unable to get mountd port number from server, using default
mount: server returned error -5 while mounting /root/andoid_nfs
VFS: Unable to moubnt root fs via NFS, trying floppy.
VFS: Cannot open root device "nfs" or unknow-block(2,0)
Please append a correct "root=" boot option; here are the avaible paritions:
b300 243712 mmvblk0 driver:mmcblkb301 243660 mmcblkop1
Kernel panic -not syncing: VFS: unable to mount root fs on unknown-block(2,0) //Stop here

Why does A1200E behave different with different [machid]????

[Konig]

m_kawale, take this as a warning. You are unnecessarily spamming the board. All information about the project is here on as is basis. I'm sure if there were 2-3 more like you, the developers will definitely not come back here. Please, in the interest of all here, either take the time to read and understand everything, or do not attempt it at all as it may be too advanced for you, and you run the risk of screwing up everything.

[sabrod]

I belive you did, but just to be sure, you type "bootusb genblob 0" BEFORE bootusbing zImage 1742 <"CMDLINE params"> , right?

Afaik Openezx don't take care of the hardware revision, it's basicly the same phones, and functionnalities.
Only when you compile a custom kernel, you may want some modules you don't find elsewhere or for testing some drivers instead of the defaults one.

A1200's machine id is known to be 1742 so this is the safer and only one to use. (if you don't want to burn your device...but in fact it's hard to say because i really don't know what kernel are you trying to boot.)
please do a uname -a once you have a shell prompt and tell us what's the kernel you are trying to use.
cat /proc/config.gz >/tmp/config.gz cannot hurt too, not sure if it works but may help you to understand how this kernel works (it's the kernel config file, that was used for compiling it).

For your probs: I'd tell you to try some changes (and maybe test with GmZhuo's bootusb...):

sudo ./boot_usb zImage-a1200 1742 "root=dev/nfs nfsroot=192.168.1.7:/home/andriod_nfs rootdelay=5 ip=192.168.1.2:192.168.1.7:255.255.255.0"
--Your ip setup lacks a gateway.
--it's /dev/nfs
Maybe this can help solving the prob:
sudo ./boot_usb zImage-a1200 1742 "root=/dev/nfs nfsroot=192.168.1.7:/home/andriod_nfs rootdelay=5 ip=192.168.1.2:192.168.1.7:192.168.1.7:255.255.255.0"

If you follow the wiki page "rootfs on nfs" you'll see the most importants CMDLINE params. Not ip.
Because ip is usually setup by default (192.168.0.202) you can always overides defaults with the CMDLINE, but be sure there is no conflicts with the others networks setups on this box (192.168.1.7 should be only for usb0, not for the ethernet router... ).
If you don't specify IP, then the default one will be used.
So you'll have to set up your box's interface (f.ex. :"usb0") to 192.168.0.200 so it will be able to see your phone (it would be at 192.168.0.202)

Ah, in the first logs you give I see "unable to mount /root/android_nfs" , the path there shouldn't differ from the path you have in your Box... you tell the rootfs was unpacked in /home/android_nfs ...

And for telnet, maybe android use ssh?? I don't know, but anyway, you'll be able to telnet/ssh only when the rootfs will be find and running... just "ping" for now

[sabrod]

I think, maybe your kernel doesn't support machid or something is wrong with the command line , if you cannot overide the defaults params, you can try to setup your box with the default IP and export path...
Maybe it will let you have a first try.
Note that i'm writing an updated 'getting started' page in openezx's wiki, that may help you too.
In the future, you should use a more recent kernel than yours...
Because, correct me if i'm wrong, you should be using android-ezx's kernel?
Most of the tips i gave you are for booting actuals kernels, not really 2.6.25 or older ones. These kernels differs a lot from the actuals.
And actuals are the most up-to-dates, and functionnals. (bluetooth, FM radio, calls, some camera's sensors, etc... are only recently supported)