Jump to content


Photo

Building CyanogenMod7

* * * * - 3 votes

  • This topic is locked This topic is locked
143 replies to this topic

#21
Pierg75

Pierg75

    Newbie

  • Members
  • Pip
  • 16 posts
  • Devices:Orange San Francisco

Is that a typo or are there really 2 forms reg_code and regcode?

It's easy enough to fix, either fix the type if that's causing the issue or check that extract_files.sh/unzip_files grab it from your phone/rom or remove it from the copy steps - I'd try the first option since it may well be needed, I think it tells the wifi driver which region you are in and there fore what wifi frequencies can legally be used.


Actually yesterday night I got it working changing the name in reg_code (or regcode I don't remember now).
Anyway I got a update.zip but, after flash it, the phone went into a reboot loop.

Later I'll probably give it another try.

  • 0

#22
thecoming

thecoming

    Newbie

  • Members
  • Pip
  • 31 posts
Nice one, ill try this out on my linux mint later!

  • 0
Posted Image

#23
punkmilitia

punkmilitia

    Regular

  • Members
  • PipPip
  • 127 posts
  • Location:South England
  • Devices:San Francisco
  • Twitter:@shaunhoare
Fixed thanks to fonix. :P

Edited by punkmilitia, 09 February 2011 - 02:46 PM.

  • 0
http://shaunsdomain.tk
if any of my posts help you, why not look into getting a GG simcard? free UNLIMITED internet, unlimited texts and 250mins a month for just a £10 topup, by signing up for a sim with the sim pic below we both get £5 free! :DPosted Image

#24
paulgdp

paulgdp

    Newbie

  • Members
  • Pip
  • 7 posts
  • Gender:Male
  • Location:France
  • Devices:ZTE-Blade OLED (Bouygue)
Hi,
I post here my experience while building this rom. I hope that some informations will help people to build the rom, but in the end my final rom doesn't work (the phone keeps rebooting in clockmodwork)

First I describe you my building environment :
I'm using Debian Sid 32 bits for my day to day work, but for my first try compiling cyanogenmod, I wanted to follow as close as possible the tuto so I created a ubuntu 10.10 64bits chroot.
You can do this with theses commands under any linux distributions (You just need to have deboostrap installed) with a 64bits linux kernel (so you can do this on a 32bits user space system with a 64bit kernel).
All the commands are done in root
# mkdir ubuntu
# debootstrap --arch=amd64 --variant=buildd --verbose maverick ubuntu
# mount procfs -t proc ubuntu/proc/
# mount sysfs -t sysfs ubuntu/sys/
# mount -o bind /dev ubuntu/dev/
# mount -o bind /dev/pts/ ubuntu/dev/pts/
# chroot ubuntu

Then, I followed the instructions of the tutorial, but I just want to add that you must add the partner repository BEFORE installing the packages to have sun-java6 installed.

Everything worked except for the extract-file part.

I had the same problem as Pierg75 and dannejo (I use JJ9 which must miss some files), so I used unzip-file.sh to extract the file from some zipped rom. (BTW the script has some typo problem, I give you a corrected one on my ftp).
I tried to extract the file from differents roms (cyanogen_blade-ota-cm7-beta2.zip, r0.2_update_de-crossed_blade_signed.zip, flb-froyo-blade-r8a.zip and Japanese_Jellyfish_RLS9.zip) but none of them had all the required files...
So I've done a mix of all of them using this priority: cyanogen_blade-ota-cm7-beta2.zip > r0.2_update_de-crossed_blade_signed.zip > flb-froyo-blade-r8a.zip > Japanese_Jellyfish_RLS9.zip.
I also give you the resulted directory containing all the proprietary files on my ftp.

And then I successfully compiled the rom (which is also on the ftp), then flashed it on my phone (I formated /boot /system /data and /cache), but it doesn't work.

The phone stay 1 minute on the ZTE blade splash screen and then reboot on clockworkmod recovery..

Here are all the files I was speaking about: http://paulgrandperr...ree.fr/android/

Do you have any ideas why the rom is not booting?

And btw thanks to everyone involved in custom rom development for the zte!

  • 0

#25
Pierg75

Pierg75

    Newbie

  • Members
  • Pip
  • 16 posts
  • Devices:Orange San Francisco

And then I successfully compiled the rom (which is also on the ftp), then flashed it on my phone (I formated /boot /system /data and /cache), but it doesn't work.
The phone stay 1 minute on the ZTE blade splash screen and then reboot on clockworkmod recovery..
Do you have any ideas why the rom is not booting?


I have the same problem.
Installed the new rom, stays for some secs on the green android screen and them reboot into recovery mode.
I used a clean (not really :P ) debian 64bit machine to build the image without setting up a temp ubuntu installation.

  • 0

#26
paulgdp

paulgdp

    Newbie

  • Members
  • Pip
  • 7 posts
  • Gender:Male
  • Location:France
  • Devices:ZTE-Blade OLED (Bouygue)

I have the same problem.
Installed the new rom, stays for some secs on the green android screen and them reboot into recovery mode.
I used a clean (not really :P ) debian 64bit machine to build the image without setting up a temp ubuntu installation.


Then I suppose that this problem must be related to the recent git commits made on TomG's sources..
It's also probably why the beta3 hasn't already been released.

  • 0

#27
whatcolour

whatcolour

    Enthusiast

  • MoDaCo Silver
  • PipPipPip
  • 234 posts

Hi,
I post here my experience while building this rom. I hope that some informations will help people to build the rom, but in the end my final rom doesn't work (the phone keeps rebooting in clockmodwork)

First I describe you my building environment :
I'm using Debian Sid 32 bits for my day to day work, but for my first try compiling cyanogenmod, I wanted to follow as close as possible the tuto so I created a ubuntu 10.10 64bits chroot.
You can do this with theses commands under any linux distributions (You just need to have deboostrap installed) with a 64bits linux kernel (so you can do this on a 32bits user space system with a 64bit kernel).
All the commands are done in root
# mkdir ubuntu
# debootstrap --arch=amd64 --variant=buildd --verbose maverick ubuntu
# mount procfs -t proc ubuntu/proc/
# mount sysfs -t sysfs ubuntu/sys/
# mount -o bind /dev ubuntu/dev/
# mount -o bind /dev/pts/ ubuntu/dev/pts/
# chroot ubuntu

Then, I followed the instructions of the tutorial, but I just want to add that you must add the partner repository BEFORE installing the packages to have sun-java6 installed.

Everything worked except for the extract-file part.

I had the same problem as Pierg75 and dannejo (I use JJ9 which must miss some files), so I used unzip-file.sh to extract the file from some zipped rom. (BTW the script has some typo problem, I give you a corrected one on my ftp).
I tried to extract the file from differents roms (cyanogen_blade-ota-cm7-beta2.zip, r0.2_update_de-crossed_blade_signed.zip, flb-froyo-blade-r8a.zip and Japanese_Jellyfish_RLS9.zip) but none of them had all the required files...
So I've done a mix of all of them using this priority: cyanogen_blade-ota-cm7-beta2.zip > r0.2_update_de-crossed_blade_signed.zip > flb-froyo-blade-r8a.zip > Japanese_Jellyfish_RLS9.zip.
I also give you the resulted directory containing all the proprietary files on my ftp.

And then I successfully compiled the rom (which is also on the ftp), then flashed it on my phone (I formated /boot /system /data and /cache), but it doesn't work.

The phone stay 1 minute on the ZTE blade splash screen and then reboot on clockworkmod recovery..

Here are all the files I was speaking about: http://paulgrandperr...ree.fr/android/

Do you have any ideas why the rom is not booting?

And btw thanks to everyone involved in custom rom development for the zte!


Similar procedure and same result, i.e., keep rebooting into recovery.

  • 0

#28
rjm2k

rjm2k

    Hardcore

  • Members
  • PipPipPipPipPipPip
  • 1,096 posts
I'm surprised that unzip_file and extract_files don't share the same code with suitable switch for zip vs adb, seems daft and error prone having to do everything twice.

  • 0

#29
fonix232

fonix232

    Addict

  • Members
  • PipPipPipPipPip
  • 942 posts
  • Location:Hungary, Debrecen
  • Devices:ZTE Blade [TFT 512RAM]
  • Twitter:@fonix232

I'm surprised that unzip_file and extract_files don't share the same code with suitable switch for zip vs adb, seems daft and error prone having to do everything twice.


It is the usual CM-stuff, every phone what's in and has two ways of getting the files has both files :P

  • 0
If you like my work, invite me for a drink or two!

Also, take a look at my Blade-dedicated site too! fonix232.co.cc

#30
metzench

metzench

    Regular

  • MoDaCo Silver
  • PipPip
  • 78 posts
1. Thanks TomG for the great work so far.

2. Would be nice to know from which rom exactly TomG pulled the necessary files. Then we all could pull them from the same source were it is known to work or not? Anyone knows something about that?

3. My build succeeded, didn´t install it yet, but i think it wont work either as your others. What i think is strange, TomGs image is 84MB mine update-cm-nightly-signed.zip is only 61MB and there is a zte-blade-ota-eng.metzench.zip that is 64MB. How come the size differs that much? Must be a problem somewhere.....

Regards,
Christian

  • 0

#31
rjm2k

rjm2k

    Hardcore

  • Members
  • PipPipPipPipPipPip
  • 1,096 posts

2. Would be nice to know from which rom exactly TomG pulled the necessary files. Then we all could pull them from the same source were it is known to work or not? Anyone knows something about that?


you don't need to know, simply use Toms latest release to extract from. if you need extra files in addition to that then extract them manually, add them to the copy script, build your rom then add them to extract and away you go next time.

  • 0

#32
metzench

metzench

    Regular

  • MoDaCo Silver
  • PipPip
  • 78 posts

you don't need to know, simply use Toms latest release to extract from. if you need extra files in addition to that then extract them manually, add them to the copy script, build your rom then add them to extract and away you go next time.


Did you already try to extract them from his latest image with unzip_files yourself?

Regards, Christian

  • 0

#33
hecatae

hecatae

    Hardcore

  • Moderator Team
  • PipPipPipPipPipPip
  • 3,205 posts
  • Gender:Male
  • Location:northampton
  • Devices:Samsung i9305
  • Twitter:@meritez

1. Thanks TomG for the great work so far.

2. Would be nice to know from which rom exactly TomG pulled the necessary files. Then we all could pull them from the same source were it is known to work or not? Anyone knows something about that?

3. My build succeeded, didn´t install it yet, but i think it wont work either as your others. What i think is strange, TomGs image is 84MB mine update-cm-nightly-signed.zip is only 61MB and there is a zte-blade-ota-eng.metzench.zip that is 64MB. How come the size differs that much? Must be a problem somewhere.....

Regards,
Christian


have you extracted them both and found any folders are a bigger size?

20mb is quite a lot, is anything missing from the build process?

  • 0

#34
ThrashMan

ThrashMan

    Diehard

  • MoDaCo Silver
  • PipPipPipPip
  • 464 posts
  • Gender:Male
  • Location:Miserable old git!
  • Devices:ZTE Blade [UK 512MB TFT]

At the moment i think it's pretty much a free for all still, hopefully once/if this becomes an official cyanogen build it will come under more control with access and code reviews for others to add to.


Sweet....quite excited about this project (in a sad geeky kind of way).
Will happily join in when things come under some sort of control.

  • 0

#35
thecoming

thecoming

    Newbie

  • Members
  • Pip
  • 31 posts
sbscj88@linuxmint ~ $ cd device/zte/blade
bash: cd: device/zte/blade: No such file or directory

im getting this error, i cant seem to get my phone to start the usb so i can activate the debug mode. anyone know how to fix this?

  • 0
Posted Image

#36
rjm2k

rjm2k

    Hardcore

  • Members
  • PipPipPipPipPipPip
  • 1,096 posts

sbscj88@linuxmint ~ $ cd device/zte/blade
bash: cd: device/zte/blade: No such file or directory

im getting this error, i cant seem to get my phone to start the usb so i can activate the debug mode. anyone know how to fix this?

surely it should be something like cd cm6/device/zte/blade

  • 0

#37
metzench

metzench

    Regular

  • MoDaCo Silver
  • PipPip
  • 78 posts

have you extracted them both and found any folders are a bigger size?

20mb is quite a lot, is anything missing from the build process?


Well despite the fact that the recovery directory is missing ( isnt this a full image only update to an already installed cm7? How to build the whole image? ), tha app directory is missing 20MB, like adw launcher and other apps that are there in TomG´s image.

How do we build an full image for CM?

Regards,
Christian

  • 0

#38
rjm2k

rjm2k

    Hardcore

  • Members
  • PipPipPipPipPipPip
  • 1,096 posts

Well despite the fact that the recovery directory is missing ( isnt this a full image only update to an already installed cm7? How to build the whole image? ), tha app directory is missing 20MB, like adw launcher and other apps that are there in TomG´s image.

How do we build an full image for CM?

Regards,
Christian


Tom probably added those manually to the vendor/zte directory which isn't included in github, maybe he will eventually provide a sctipt like CM do for google apps and rom manager

  • 0

#39
thecoming

thecoming

    Newbie

  • Members
  • Pip
  • 31 posts

surely it should be something like cd cm6/device/zte/blade


Have you tried this? ill give it a go later and see what i can do. i would like to build the latest version and help add to the git

  • 0
Posted Image

#40
rjm2k

rjm2k

    Hardcore

  • Members
  • PipPipPipPipPipPip
  • 1,096 posts

Have you tried this? ill give it a go later and see what i can do. i would like to build the latest version and help add to the git


Well, it all depends on where you got the code to when you used git. If it's not in your home dir then cd device/zte/blade will not work!

  • 0




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users