Jump to content

Recommended Posts

Guest sto1911
Posted

Dear Members,

I have the 2.2 source downloaded from ZTE for ZTE V880 (a.k.a. ZTE Blade/Orange San Francisco).

I want to compile this but I have no information on how to do this and what other steps I have to take to build my very own working ROM.

Can anyone help me?

Posted
Dear Members,

I have the 2.2 source downloaded from ZTE for ZTE V880 (a.k.a. ZTE Blade/Orange San Francisco).

I want to compile this but I have no information on how to do this and what other steps I have to take to build my very own working ROM.

Can anyone help me?

Start by setting your machine up as described here.... http://source.android.com/source/download.html

Posted
Start by setting your machine up as described here.... http://source.android.com/source/download.html

That is a good start, but is outdated. I tried it, and as instructed, used java 1.5, then when I tried a 'make' it told me that I need 1.6 :D Also the OS needs to be on 64 bits, I had an Ubuntu 10.10 on 32 bits, and again, when running make, it told me that it needs 64 bits.

Also they say Mac Snow Leopard is not supported but I think it is (will try it soon, in a virtual machine the building takes like forever).

Found better info Googling around.

Once I manage, will provide step by step instructions.

Guest sto1911
Posted

Thank you all for your answers. This process seems to be veeery long and I have already faced problems with the prerequisites :D We will see if this is leading anywhere...

Guest Sebastian404
Posted (edited)

There are a number of guides already on how to build the kernel, and as you have spotted the most involved part is having the pre-requisites.

Be-aware the ZTE 2.1 Kernel source as supplied from their website wont compile without some modifications, check the existing Kernel threads for that

Edited by Sebastian404

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.