Porting Andoid on A1200 MING

[m_kawale]

plz can u post screen short for how to mod e6 wit android...
plz...
i m dieing to use it...

[sabrod]

+1 android-ezx should also have made a video of his console when he was creating the patchs, and i'd like to see this linux tools compiling too.
(to see if it's true that linux can be used for that)

[biggerstone]

Hi, sabrod:
Thank you for your help.

//////For your probs: I'd tell you to try some changes (and maybe test with GmZhuo's bootusb...):
answer:
i haver download "GmZhuo's bootusb" and "zImage-20081206" , but an failed occoured:
root@ubuntu:/home/administrator/boot_usb-0.2.0# sudo ./boot_usbgm zImage-20081206
Serching for EZX phone: E2/A1200/E6/A910 found.
Sending mach id code 867: 100% OK
Uploading kernel: 100% OK
Uploading params: FAILED: params upload failed
root@ubuntu:/home/administrator/boot_usb-0.2.0# sudo ./boot_usbgm zImage-20081206 1742 "root=/dev/nfs nfsroot=192.168.1.1:/home/android_nfs rootdelay=5 ip=192.168.1.2:192.168.1.1:192.168.1.1:255.255.255.0"
Serching for EZX phone: E2/A1200/E6/A910 found.
Sending mach id code 1742: 100% OK
Uploading kernel: 100% OK
Uploading params: FAILED: params upload failed
root@ubuntu:/home/administrator/boot_usb-0.2.0#

/////please do a uname -a once you have a shell prompt and tell us what's the kernel you are trying to use.
Answer:
my host linux version is:
root@ubuntu:/home/administrator/boot_usb-0.2.0# uname -a
Linux ubuntu 2.6.27-7-generic #1 SMP Fri Oct 24 06:42:44 UTC 2008 i686 GNU/Linux
root@ubuntu:/home/administrator/boot_usb-0.2.0#

My target(Motorola A1200e) kernel and Root NFS is maked according to this post(linux-2.6.24)

The followings is my infomation collected.
(1) I have configured my PC' USB network according to the link "http://wiki.openezx.org/Rootfs_on_NFS".
root@ubuntu:/home/administrator/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
root@ubuntu:/home/administrator/boot_usb-0.2.0# ifup usb0
ifup: interface usb0 already configured
root@ubuntu:/home/administrator/boot_usb-0.2.0#
root@ubuntu:/home/administrator/boot_usb-0.2.0# ifconfig
eth0 Link encap:Ethernet HWaddr 00:1f:c6:1b:43:77
inet addr:192.168.1.7 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::21f:c6ff:fe1b:4377/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:338 errors:0 dropped:0 overruns:0 frame:0
TX packets:67 errors:0 dropped:0 overruns:0 carrier:1
collisions:0 txqueuelen:1000
RX bytes:35841 (35.8 KB) TX bytes:0 (0.0 B)
Memory:dffc0000-e0000000

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:174 errors:0 dropped:0 overruns:0 frame:0
TX packets:174 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:12808 (12.8 KB) TX bytes:12808 (12.8 KB)

usb0 Link encap:Ethernet HWaddr 9e:d8:dc:08:31:2b
inet addr:192.168.1.1 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::9cd8:dcff:fe08:312b/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:9 errors:0 dropped:0 overruns:0 frame:0
TX packets:25 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:252 (252.0 B) TX bytes:3848 (3.8 KB)

root@ubuntu:/home/administrator/boot_usb-0.2.0#

(2) I have make my /home/android_nfs export correctly. See my host' terminal:
root@ubuntu:/home/administrator/boot_usb-0.2.0# showmount -e
Export list for ubuntu:
/home/android_nfs (everyone)

[sabrod]

Well, you still not requiring help the right way... You need to take care of your setup, and precise only the necessary specific openezx details that stops your progress.
But ok, now i believe i can maybe help you...and let you try the stuff.

I don't see what's wrong for the first error:PARAM UPLOAD FAILED. (the machid 867 sound weird!!)
Except maybe if you could precise if when you launched bootusb in genblob in usb mode, or in original bootloader flash mode. So I believe you made something wrong and cannot help you more without other details.

please add for example:

With genblob 'usb ready':
./boot_usbgm zImage-20081206

Wich command cannot work properly because a recent kernel need a machid... But it would be, at least, good to know it's not a trivial error you may did, that cause the kernel panic. (like forget to launch genblob before trying a 2008 kernel).

As i said, newer kernels (pxa-udc driver prob) can't work without the necessary reset of the usb port , wich isn't done by the original bootloader, but by genblob, note that this is not true for older kernel that bug "appeared" in Openezx-2.6.26. Well before the driver used was different.

Well uname -a of your box is good to know, as you probably have an uptodate ubuntu , but i was thinking of your phone's kernel.

This one, 2.6.24, (if i understood correctly) should work without any care ("bootusb zImage2.6.24" that's all and otherwise it will not work!), because it don't have the same pxa-udc driver as mainline linux, but it's anthic history...

Ok, for your export, it's maybe working, the network is the problem:
usbnet and ethernet MUST have different addresses ranges ...
You have to either disconnect eth or reconfigure it's IP' range...
You have 192.168.1.Y for eth0 and usb0 you must change one of them to 192.168.X.Y where X differ from 1 and with X and Y between 0 and 255.
X determine the range, i hope to be clear.
if you can't overide the kernel commandline, you have to change your box's config to suit the kernel. (the same for nfs export: maybe it's "/root/android_nfs" . (i went and read the patch, wahoo!!)

IP is always changeable in userspace, later, but if userspace depends on network (nfsroot).... it isn't easy

See: http://wiki.openezx.org/Getting_Started
there is also an outdated document that can maybe help you for trying this old 2.6.24 kernel.

Good luck, you're near from your goal!

[Konig]

i didnt ask u not to disturb me! i asked u not to disturb the developers!!!
Trust me, if u were on another elite forum, im pretty sure you would have been banned for repeatedly asking the same thing! besides, read the pdf file in the first post and follow whats written there!

[biggerstone]

sabrod,

Firstly, thanks for your patience and advices.
Now i can ping 192.168.1.2 OK(192.168.1.2 is my A1200e' IP Address), my host usb networking's IP is 192.168.1.1.

But i still can't telent to 192.168.1.2. Any problem for my procedure of setting USBNET?

///////////////////////See here
root@ubuntu:/home/administrator/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
root@ubuntu:/home/administrator/boot_usb-0.2.0# ifconfig
eth0 Link encap:Ethernet HWaddr 00:1f:c6:1b:43:77
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:1
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
Memory:dffc0000-e0000000
lo:.................

usb0 Link encap:Ethernet HWaddr 9e:d8:dc:08:31:2b
inet addr:192.168.1.1 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::9cd8:dcff:fe08:312b/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:9 errors:0 dropped:0 overruns:0 frame:0
TX packets:25 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:252 (252.0 B) TX bytes:3848 (3.8 KB)

root@ubuntu:/home/administrator/boot_usb-0.2.0# ping 192.168.1.2
PING 192.168.1.2 (192.168.1.2) 56(84) bytes of data.
64 bytes from 192.168.1.2: icmp_seq=1 ttl=64 time=1.22 ms
64 bytes from 192.168.1.2: icmp_seq=2 ttl=64 time=1.28 ms
64 bytes from 192.168.1.2: icmp_seq=3 ttl=64 time=1.29 ms
64 bytes from 192.168.1.2: icmp_seq=4 ttl=64 time=1.31 ms
64 bytes from 192.168.1.2: icmp_seq=5 ttl=64 time=1.32 ms
64 bytes from 192.168.1.2: icmp_seq=6 ttl=64 time=1.33 ms
64 bytes from 192.168.1.2: icmp_seq=7 ttl=64 time=1.34 ms
64 bytes from 192.168.1.2: icmp_seq=8 ttl=64 time=1.36 ms
^C
--- 192.168.1.2 ping statistics ---
8 packets transmitted, 8 received, 0% packet loss, time 7028ms
rtt min/avg/max/mdev = 1.227/1.311/1.362/0.039 ms
root@ubuntu:/home/administrator/boot_usb-0.2.0# ssh 192.168.1.2
ssh: connect to host 192.168.1.2 port 22: Connection refused
root@ubuntu:/home/administrator/boot_usb-0.2.0# telnet 192.168.1.2
Trying 192.168.1.2...
telnet: Unable to connect to remote host: Connection refused

I have searched some links, such as:
https://lists.gnumonks.org/pipermail...st/001419.html
https://lists.gnumonks.org/pipermail...il/001913.html

but how to fix it ??No one describes it clearly.

[biggerstone]

Well, you still not requiring help the right way... You need to take care of your setup, and precise only the necessary specific openezx details that stops your progress.
But ok, now i believe i can maybe help you...and let you try the stuff.

I don't see what's wrong for the first error:PARAM UPLOAD FAILED. (the machid 867 sound weird!!)
Except maybe if you could precise if when you launched bootusb in genblob in usb mode, or in original bootloader flash mode. So I believe you made something wrong and cannot help you more without other details.

please add for example:

With genblob 'usb ready':
./boot_usbgm zImage-20081206

Wich command cannot work properly because a recent kernel need a machid... But it would be, at least, good to know it's not a trivial error you may did, that cause the kernel panic. (like forget to launch genblob before trying a 2008 kernel).

i didn't forget to launch genblob before trying 2 2008 kernel. before i upload zImage, i launch genblob,but failed so i give up.
root@ubuntu:/home/administrator/boot_usb-0.2.0# sudo ./boot_usbgm genblob
Serching for EZX phone: E2/A1200/E6/A910 found.
Sending mach id code 867: 100% OK
Uploading kernel: Segmenttation fault. //stop here

As i said, newer kernels (pxa-udc driver prob) can't work without the necessary reset of the usb port , wich isn't done by the original bootloader, but by genblob, note that this is not true for older kernel that bug "appeared" in Openezx-2.6.26. Well before the driver used was different.

Well uname -a of your box is good to know, as you probably have an uptodate ubuntu , but i was thinking of your phone's kernel.

This one, 2.6.24, (if i understood correctly) should work without any care ("bootusb zImage2.6.24" that's all and otherwise it will not work!), because it don't have the same pxa-udc driver as mainline linux, but it's anthic history...
i am sure my target kernel is 2.6.24. I make it according by the PDF of "Android Porting Guideline for A1200
by androidezx@gmail.com 2008.08.05". Nothing modified.

Ok, for your export, it's maybe working, the network is the problem:
usbnet and ethernet MUST have different addresses ranges ...
You have to either disconnect eth or reconfigure it's IP' range...
I have my eth0 disconnected, and i have configured the usb0 ip address (192.168.1.1) in the file /etc/network/interfaces.
And now the usb0 is up and i can ping 192.168.1.2 OK.

You have 192.168.1.Y for eth0 and usb0 you must change one of them to 192.168.X.Y where X differ from 1 and with X and Y between 0 and 255.
X determine the range, i hope to be clear.
if you can't overide the kernel commandline, you have to change your box's config to suit the kernel. (the same for nfs export: maybe it's "/root/android_nfs" . (i went and read the patch, wahoo!!)
Just as the attach file of the first page of this discussion, my android-config-nfs.patch have the line:
CONFIG_ARM=y
CONFIG_SYS_SUPPORTS_APM_EMULATION=y
@@ -236,7 +236,7 @@
#
CONFIG_ZBOOT_ROM_TEXT=0x0
CONFIG_ZBOOT_ROM_BSS=0x0
-CONFIG_CMDLINE="console=tty1 root=/dev/mmcblk0p2 rootfstype=ext2 rootdelay=1 ip=192.168.0.202:192.168.0.200:192.168.0.200:255.255.255.0 debug mem=32M@0xA0000000 mem=16M@0xAC000000"
+CONFIG_CMDLINE="root=/dev/nfs nfsroot=192.168.1.1:/root/android_nfs rw ip=192.168.1.2:192.168.1.1:192.168.1.1:255.255.255.0:ezx:usb0ff mem=32M@0xA0000000 mem=16M@0xAC000000"
# CONFIG_XIP_KERNEL is not set
CONFIG_KEXEC=y
IP is always changeable in userspace, later, but if userspace depends on network (nfsroot).... it isn't easy

See: Getting Started - OpenEZX
there is also an outdated document that can maybe help you for trying this old 2.6.24 kernel.

Good luck, you're near from your goal!

Thanks for your encourage!
Now I can see usb0 device in linux host and ping 192.168.1.2 (I config A1200 ip to 192.168.1.2 and linux host is 192.168.1.1). But when I telnet 192.168.1.2, there is the below error:
root@ubuntu:/home/administrator/boot_usb-0.2.0# ssh 192.168.1.2
ssh: connect to host 192.168.1.2 port 22: Connection refusedroot@ubuntu:/home/administrator/boot_usb-0.2.0# telnet 192.168.1.2
Trying 192.168.1.2...
telnet: Unable to connect to remote host: Connection refused
I suspect whether telnetd service is not running or telnet port 22 is disabled. Could you give some advise?

[Konig]

i thought telnet port was always 23

[sabrod]

use sudo!!
genblob command is ./boot_usb gen-blob 0
0 the machid needed for genblob.
Ah you find the patch... so you work on a rootfs on nfs?
If, yes network is good and ssh and telnet should work.
try sudo or su!!!
Few and lasts hints:
-use nmap 192.168.1.2 to see open ports (don't ask about how to install nmap, please)
-Or maybe sudo ssh-keygen then copy /root/.ssh/*.pub to phones same places (root & users .ssh folders) for each users (you never know) and then rename the fiel to "authorized_keys". (basis of ssh )
Note that openEZX developpers already had solved for YEARS problems that exists on this kernel : use git source code depositories (sound, bluetooth, phone-calls, fm radio...).
I could help, it seems i only prevented you to read some tutos and howtos, for now, consider learning session, I'm tired, i'm not a F1 key... Nothing specifics to android or nothing that isn't in openezx's wiki was asked. I helped finding basic bugs, ok... for a short time...
But you don't seem to be very curious, at the end... You cannot use the androidezx's work like that, and finish, without learning and really work, to port android in one day...
i had to point you repeatedly the same probs and lacks of infos...please!
To port android to a1200, you may want to try a NEW kernel built by you, based on androidezx's patchset.
see PM.

[sabrod]

i thought telnet port was always 23

Me too!
At least this is the 23 i always used.