• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root Build CyanogenMod7 from source | Development area

Obviously, Gentoo doesn't have apt-get, so can you paste the command you used to grab all the build-deps? I haven't used Gentoo in years, so I don't know if I can really help.

From what I can see, V8 (and/or libv8) didn't build correctly and when the compile goes to execute it, it fails...

Code:
E/v8      (32060):
E/v8      (32060): #
E/v8      (32060): # Fatal error in v8::Context::New()
E/v8      (32060): #
E/v8      (32060): Error initializing V8
E/v8      (32060):
E/v8      (32060): #
E/v8      (32060):

I installed with the following -

Code:
sudo emerge -1n git gnupg flex bison gperf libsdl esound wxGTK squashfs-tools zip curl ncurses zlib sun-jdk pngcrush schedtool

Some of the package names are slightly different, but they should all install the required libraries and headers that CM expects.

V8 is Google's Java interpreter, right?
 
I haven't gotten to it either, but I believe if you just extract the mtblobs.tar.gz into:

~/android/system/vendor/motorola/triumph/

Then comment out the first part of the extract-files.sh script where all the lines begin with 'adb pull', then what's left would be that script, simple and less chance of missing anything or introducing problems.


So just take out "abd pull" lines... what about
Code:
(cat << EOF) | sed s/__DEVICE__/$DEVICE/g | sed s/__VENDOR__/$VENDOR/g > ../../../vendor/$VENDOR/$DEVICE/$DEVICE-vendor-blobs.mk
 
So just take out "abd pull" from every line (that has it in the beginning) and we should be good? For example...

From:
Code:
adb pull /system/bin/hci_qcomm_init  ../../../vendor/$VENDOR/$DEVICE/proprietary

To:
Code:
/system/bin/hci_qcomm_init  ../../../vendor/$VENDOR/$DEVICE/proprietary

no you want to comment it out by putting a "#" at the beggining of every line...

like this:
Code:
adb pull /system/bin/hci_qcomm_init  ../../../vendor/$VENDOR/$DEVICE/proprietary

to:
Code:
#adb pull /system/bin/hci_qcomm_init  ../../../vendor/$VENDOR/$DEVICE/proprietary

then that will tell the script to skip those lines.
 
So just take out "abd pull" from every line (that has it in the beginning) and we should be good? For example...

From:
Code:
adb pull /system/bin/hci_qcomm_init  ../../../vendor/$VENDOR/$DEVICE/proprietary
To:
Code:
/system/bin/hci_qcomm_init  ../../../vendor/$VENDOR/$DEVICE/proprietary

Run this -

Code:
mkdir -p ~/android/system/vendor/motorola/triumph
tar xvzf /path/to/mtblobs.tar.gz ~/android/system/vendor/motorola/triumph

You can then run the extract-files.sh script without worry. The adb lines will fail, but everything else will be in place and you can continue. If you want to, remove every line starting with "adb pull" to avoid even calling adb.
 
So if I run "extract-files.sh" and it doesn't show anything (after you press enter), then it is good?!

Better yet, can someone just send me a copy of the extract-files.sh? I added a # to every line that started with adb pull...

Edit: Seems to be working. I am now building ICS. Hopefully.
 
So if I run "extract-files.sh" and it doesn't show anything (after you press enter), then it is good?!

Better yet, can someone just send me a copy of the extract-files.sh? I added a # to every line that started with adb pull...

dont worry you did it right. mine didnt show anything when i ran it either, but everything still worked for me :D
 
Just curious, in order to pull the ICS source is the only thing you need to change:

repo init -u git://github.com/ikarosdev/android.git -b gingerbread


to:
repo init -u git://github.com/ikarosdev/android.git -b ics

(and of course using the ICS proprietary files agentc13 posted a link to so you can build)

Also, is the ICS repo up to date (i.e. up to the point Isaac got to in his Road to ICS on the Triumph thread)? I remember Isaac saying that he would update this thread when he got the ICS code in order, just wondering what sort of state it's in.
 
Just curious, in order to pull the ICS source is the only thing you need to change:

repo init -u git://github.com/ikarosdev/android.git -b gingerbread


to:
repo init -u git://github.com/ikarosdev/android.git -b ics

(and of course using the ICS proprietary files agentc13 posted a link to so you can build)

Also, is the ICS repo up to date (i.e. up to the point Isaac got to in his Road to ICS on the Triumph thread)? I remember Isaac saying that he would update this thread when he got the ICS code in order, just wondering what sort of state it's in.

http://androidforums.com/triumph-al...ussion-building-ics-source-isaacs-github.html

My Github news feed: https://github.com/ikarosdev.atom
 
Just curious, in order to pull the ICS source is the only thing you need to change:

repo init -u git://github.com/ikarosdev/android.git -b gingerbread


to:
repo init -u git://github.com/ikarosdev/android.git -b ics

(and of course using the ICS proprietary files agentc13 posted a link to so you can build)

Also, is the ICS repo up to date (i.e. up to the point Isaac got to in his Road to ICS on the Triumph thread)? I remember Isaac saying that he would update this thread when he got the ICS code in order, just wondering what sort of state it's in.

This is the thread for ICS building:

http://androidforums.com/triumph-al...ussion-building-ics-source-isaacs-github.html

Also the proprietary files posted earlier is THE only proprietary files for the MT, they came from Froyo, works in GB, and will hopefully be used in ICS too (if we don't get some sort of update from Motorola or a clone of the MT).

Also I believe as someone mentioned in the other thread, the posted blobs is missing a libaudio.so file somewhere too.
 
My repo freezes at around "android_device_samsung_crespo" for some reason. Can I escape out and restart from that point?

*edit* I think I got it. I just opened another window in terminal and retype repo sync -j16. It seems to restart where it left off on its own.

-Mike
 
My repo freezes at around "android_device_samsung_crespo" for some reason. Can I escape out and restart from that point?

-Mike

You should be able to do this:

Code:
killall -9 repo && killall -9 python

then do the repo sync again. It would pick up where you were.
 
You should be able to do this:

Code:
killall -9 repo && killall -9 python
then do the repo sync again. It would pick up where you were.

Ok. I'm getting frustrated with the repo. I did what you suggested, worked fine. I restarted the repo and here is where it hangs again and again (5 or 6 times in a row):

Code:
mike@gator-ubuntu:~/android/system$ repo sync -j16
fatal: Not a git repository: '/home/mike/android/system/.repo/projects/bootable/recovery.git'
Fetching projects:   8% (26/314)  fatal: Not a git repository: '/home/mike/android/system/.repo/projects/device/htc/supersonic.git'
Fetching projects:  98% (308/314)  fatal: Not a git repository: '/home/mike/android/system/.repo/projects/bootable/recovery.git'
fatal: Not a git repository: '/home/mike/android/system/.repo/projects/device/htc/supersonic.git'
error: Cannot fetch CyanogenMod/android_bootable_recovery
error: Cannot fetch CyanogenMod/android_device_htc_supersonic

Not sure if it's the git's end or on mine. It has taken quite a while to get to this point, but I feel like there is something going on on their end preventing me from completing this.
 
You are doing this for CM7, not ICS right?

You may need to start over. I had a similar issue and deleted all the files I had repo'ed and started that part from scratch.
 
Ok. I'm getting frustrated with the repo. I did what you suggested, worked fine. I restarted the repo and here is where it hangs again and again (5 or 6 times in a row):

Code:
mike@gator-ubuntu:~/android/system$ repo sync -j16
fatal: Not a git repository: '/home/mike/android/system/.repo/projects/bootable/recovery.git'
Fetching projects:   8% (26/314)  fatal: Not a git repository: '/home/mike/android/system/.repo/projects/device/htc/supersonic.git'
Fetching projects:  98% (308/314)  fatal: Not a git repository: '/home/mike/android/system/.repo/projects/bootable/recovery.git'
fatal: Not a git repository: '/home/mike/android/system/.repo/projects/device/htc/supersonic.git'
error: Cannot fetch CyanogenMod/android_bootable_recovery
error: Cannot fetch CyanogenMod/android_device_htc_supersonic
Not sure if it's the git's end or on mine. It has taken quite a while to get to this point, but I feel like there is something going on on their end preventing me from completing this.

The -j16 switch isn't required, but it speeds things up in the case of a high speed repo. Run again with
Code:
repo sync
and see if it completes. It will be slower, but I haven't had any issues running repo single-threaded.
 
I have usually done
HTML:
repo sync -j4
It didn't seem much slower to me, and I didn't have issues doing it this way. When I used -j16 I had issues.
 
I have usually done
HTML:
repo sync -j4
It didn't seem much slower to me, and I didn't have issues doing it this way. When I used -j16 I had issues.

I'll try j4 and see. Yes, I am only running the repo for gingerbread.

As suggested, I deleted everything and redid all steps. I an syncing on -j4 and it seems to be working much better.
 
Ok guys, I got the repo sync completed. I now, apparently have an issue with either my device, or ADB. ADB spits back this response:
Code:
mike@gator-ubuntu:~$ adb devices
List of devices attached 
????????????    no permissions
I know that it's connected properly, USB debugging is enabled, and working, server is started, and lsusb command states that it is connected. I remember editing a file a while ago to build directly to a device. I think that may be the problem. I had to edit the file to see the device specifically. I just can't remember what the file was. :(

I'm off to bed. I'll deal with this tomorrow after work. Thanks for the help so far.

-Mike
 
Ok guys, I got the repo sync completed. I now, apparently have an issue with either my device, or ADB. ADB spits back this response:
Code:
mike@gator-ubuntu:~$ adb devices
List of devices attached 
????????????    no permissions
I know that it's connected properly, USB debugging is enabled, and working, server is started, and lsusb command states that it is connected. I remember editing a file a while ago to build directly to a device. I think that may be the problem. I had to edit the file to see the device specifically. I just can't remember what the file was. :(

I'm off to bed. I'll deal with this tomorrow after work. Thanks for the help so far.

-Mike

You have to start the server with superuser permissions. Something like:
sudo adb start-server

It's been a while since I've done it, but I remember running into the same issue.
 
Ok guys, I got the repo sync completed. I now, apparently have an issue with either my device, or ADB. ADB spits back this response:
Code:
mike@gator-ubuntu:~$ adb devices
List of devices attached 
????????????    no permissions
I know that it's connected properly, USB debugging is enabled, and working, server is started, and lsusb command states that it is connected. I remember editing a file a while ago to build directly to a device. I think that may be the problem. I had to edit the file to see the device specifically. I just can't remember what the file was. :(

I'm off to bed. I'll deal with this tomorrow after work. Thanks for the help so far.

-Mike


I had the same issue....
here man check this out... it should be of some help to you! :D

ADB: "no permissions" (Linux Mint 9) [SOLVED] - xda-developers
 
I had the same issue....
Thanks for all the help fellas... I will try to do that when I get home. It seems weird though, I never had to do that before to communicate via ADB... I may have had to do something like that to pull files from another device before, if memory serves. It's not serving so well this morning, as I am a little fried from last nights frustration. However, I did get the repo!
 
Thanks for all the help fellas... I will try to do that when I get home. It seems weird though, I never had to do that before to communicate via ADB... I may have had to do something like that to pull files from another device before, if memory serves. It's not serving so well this morning, as I am a little fried from last nights frustration. However, I did get the repo!


Yeah just do what it says in that link. I did and it worked perfect after that!
 
Yeah just do what it says in that link. I did and it worked perfect after that!

You guys rock! I went in as Root. Got the needed files via ADB and now I am building a ROM.

This should be the "most current" iteration correct? I mean, if it builds correctly, it should work as a fully functioning ROM right?

I've tried the Wifi tether on the current available iteration of CM7 for Triumph on XDA. Wifi tether works, but it is a bit shaky at times. Has it been updated on any other builds? Is this build based on that?

Thanks for all the help guys.(sorry for the birage of questions)
-Mike

*edit* Ok, I screwed up... Just read a few posts up that I "pulled" the files from the wrong ROM. I used the CM7 build that I am currently running. I will need to re-do the build with the updated files that I downloaded. I will also edit the scripts as recommended here also... No ticky, No laundry!
 
You guys rock! I went in as Root. Got the needed files via ADB and now I am building a ROM.

This should be the "most current" iteration correct? I mean, if it builds correctly, it should work as a fully functioning ROM right?

I've tried the Wifi tether on the current available iteration of CM7 for Triumph on XDA. Wifi tether works, but it is a bit shaky at times. Has it been updated on any other builds? Is this build based on that?

Thanks for all the help guys.(sorry for the birage of questions)
-Mike

*edit* Ok, I screwed up... Just read a few posts up that I "pulled" the files from the wrong ROM. I used the CM7 build that I am currently running. I will need to re-do the build with the updated files that I downloaded. I will also edit the scripts as recommended here also... No ticky, No laundry!

nahh you shouldnt have to redo anything. just put the stock rom on your phone then repull the files, or grab the motorola blobs that agentc posted further up on this thread and put them where there supposed to go :D
 
nahh you shouldnt have to redo anything. just put the stock rom on your phone then repull the files, or grab the motorola blobs that agentc posted further up on this thread and put them where there supposed to go :D

That's exactly what I did Ziggy (the second option). Thanks man. I would like to include the ADW launcher in my build. Can I build it separatly and add it in after the zip file is built?

I started my build, but I'm gonna hit the sack. I got a long few days ahead of me. I'll check in the AM to see what happens. I am getting kinda excited, like it's Christmas already. Happy holidays guys.
 
Back
Top Bottom