• 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

mantera said:
are you guys sure you pulled the proprietary files? Like b_randon said, some of those files are the proprietary ones. Did you guys made sure that adb saw your phones before running the extractfiles.sh script?

And of course, you need to have debugging turned on on your phone.
Click to expand...

Yes i pulled all of them no errors.
Im just gonna delete everything and resync
 
shane@shane-TA990FXE:~$ mkdir -p ~/android/system && mkdir -p ~/bin
shane@shane-TA990FXE:~$ cd ~/android/system
shane@shane-TA990FXE:~/android/system$ repo init -u git://github.com/ikarosdev/android.git -b gingerbrea
repo initialized in /home/shane/android
Your Name [Shane]:
Your Email [blah blah blah]:

Your identity is: Shane <blah blah blah>
is this correct [y/N]? y

repo initialized in /home/shane/android


shane@shane-TA990FXE:~/android/system$ repo sync -j16
Fetching projects: 100% (315/315), done.
Checking out files: 100% (145/145), done.g out files: 43% (63/145)
Checking out files: 100% (4679/4679), done. out files: 37% (1738/4679)
Checking out files: 100% (10012/10012), done.ut files: 19% (1960/10012)
Checking out files: 100% (12550/12550), done.ut files: 16% (2089/12550)
Checking out files: 100% (518/518), done.ng out files: 48% (250/518)
Checking out files: 100% (142/142), done.ng out files: 2% (3/142)
Checking out files: 100% (10462/10462), done.ut files: 0% (18/10462)
Syncing work tree: 100% (314/314), done.

shane@shane-TA990FXE:~/android/system$ cd ~/android/system/device/motorola/triumph
bash: cd: /home/shane/android/system/device/motorola/triumph: No such file or directory
shane@shane-TA990FXE:~/android/system$ cd
shane@shane-TA990FXE:~$ cd ~/android/system/device/motorola/triumph
bash: cd: /home/shane/android/system/device/motorola/triumph: No such file or directory

Thats where im at no such directory.

If i delete the system everything works. i am building now
example
cd ~/android/device/motorola/triumph
 
konspiracy said:
shane@shane-TA990FXE:~$ mkdir -p ~/android/system && mkdir -p ~/bin
shane@shane-TA990FXE:~$ cd ~/android/system
shane@shane-TA990FXE:~/android/system$ repo init -u git://github.com/ikarosdev/android.git -b gingerbrea
repo initialized in /home/shane/android
Click to expand...

Yeah, that's because you initialized your repo in the ~/android/ directory. See where in your quote it says:

repo initialized in /home/shane/android

Also, I'm assuming that your copy and paste just missed the last letter "d" in gingerbread in this line, right?

Code: 
shane@shane-TA990FXE:~/android/system$ repo init -u git://github.com/ikarosdev/android.git -b gingerbrea
 
mantera said:
Yeah, that's because you initialized your repo in the ~/android/ directory. See where in your quote it says:

repo initialized in /home/shane/android

Also, I'm assuming that your copy and paste just missed the last letter "d" in gingerbread in this line, right?

Code: 
shane@shane-TA990FXE:~/android/system$ repo init -u git://github.com/ikarosdev/android.git -b gingerbrea
Click to expand...
Your correct. thank you.
it finally built cleanly.
 
I'm setting up my FedoraCore14 system, from your instructions.

I've changed package names for installation via YUM, and installed the JRE1.6 on my platform. Once I have a functional system I'll post a summary of changes for FC users.
One thing I can share is that I regretted adding Android 2.3.3 and 2.2 environments to my AndroidSDK, as "Real3D by LGE" took forever to download (twice)!:o

Currently I have a problem that has not been posted yet. I think I know the answer, but I'm surprised nobody else has bumped into this issue yet.

When I ran the "extract-files.sh" script it failed to find a number of files. My guess is that this needs to be run when you have a stock ROM flashed on the phone. I'm running cm-7.1.0-TG-B0.8 + TheOCv1.5 kernel. The "extract-files.sh" script yielded the following errors, after which my compile fails to find target ".../thermald".

Here is the output from my extract.


android_env> sh ./extract-files.sh
320 KB/s (28764 bytes in 0.087s)
635 KB/s (64080 bytes in 0.098s)
260 KB/s (23284 bytes in 0.087s)
115 KB/s (9664 bytes in 0.081s)
1161 KB/s (61756 bytes in 0.051s)
360 KB/s (32256 bytes in 0.087s)
380 KB/s (18052 bytes in 0.046s)
248 KB/s (22288 bytes in 0.087s)
67 KB/s (5632 bytes in 0.081s)
remote object '/system/bin/thermald' does not exist
250 KB/s (22508 bytes in 0.087s)
177 KB/s (15040 bytes in 0.082s)
170 KB/s (14240 bytes in 0.081s)
169 KB/s (14188 bytes in 0.081s)
178 KB/s (15148 bytes in 0.082s)
62 KB/s (5180 bytes in 0.081s)
397 KB/s (18548 bytes in 0.045s)
93 KB/s (7764 bytes in 0.081s)
251 KB/s (22312 bytes in 0.086s)
293 KB/s (26372 bytes in 0.087s)
294 KB/s (26388 bytes in 0.087s)
300 KB/s (26376 bytes in 0.085s)
247 KB/s (22172 bytes in 0.087s)
338 KB/s (30364 bytes in 0.087s)
247 KB/s (22172 bytes in 0.087s)
294 KB/s (26400 bytes in 0.087s)
65 KB/s (5476 bytes in 0.081s)
376 KB/s (18140 bytes in 0.047s)
167 KB/s (13984 bytes in 0.081s)
167 KB/s (14176 bytes in 0.082s)
169 KB/s (14176 bytes in 0.081s)
64 KB/s (5424 bytes in 0.082s)
191 KB/s (15952 bytes in 0.081s)
115 KB/s (9676 bytes in 0.081s)
114 KB/s (9676 bytes in 0.082s)
1437 KB/s (101484 bytes in 0.068s)
68 KB/s (5708 bytes in 0.081s)
247 KB/s (22164 bytes in 0.087s)
374 KB/s (18040 bytes in 0.047s)
116 KB/s (9708 bytes in 0.081s)
614 KB/s (62096 bytes in 0.098s)
127 KB/s (10640 bytes in 0.081s)
341 KB/s (30564 bytes in 0.087s)
634 KB/s (63460 bytes in 0.097s)
292 KB/s (26256 bytes in 0.087s)
162 KB/s (13740 bytes in 0.082s)
161 KB/s (13664 bytes in 0.082s)
1021 KB/s (114792 bytes in 0.109s)
1623 KB/s (233708 bytes in 0.140s)
1384 KB/s (175104 bytes in 0.123s)
2852 KB/s (580140 bytes in 0.198s)
110 KB/s (9260 bytes in 0.081s)
remote object '/system/lib/libaudioeq.so' does not exist
984 KB/s (59064 bytes in 0.058s)
1255 KB/s (79784 bytes in 0.062s)
1327 KB/s (166904 bytes in 0.122s)
3425 KB/s (1887044 bytes in 0.537s)
1538 KB/s (210620 bytes in 0.133s)
718 KB/s (38476 bytes in 0.052s)
428 KB/s (20096 bytes in 0.045s)
remote object '/system/lib/hw/gralloc.msm7k.so' does not exist
remote object '/system/lib/libOmxEvrcEnc.so' does not exist
remote object '/system/lib/libOmxAacDec.so' does not exist
remote object '/system/lib/libOmxQcelp13Dec.so' does not exist
remote object '/system/lib/libOmxAmrEnc.so' does not exist
remote object '/system/lib/libOmxAdpcmDec.so' does not exist
remote object '/system/lib/libOmxEvrcDec.so' does not exist
remote object '/system/lib/libOmxAmrDec.so' does not exist
remote object '/system/lib/libOmxAmrwbDec.so' does not exist
remote object '/system/lib/libOmxWmaDec.so' does not exist
remote object '/system/lib/libOmxQcelp13Enc.so' does not exist
remote object '/system/lib/libOmxMp3Dec.so' does not exist
remote object '/system/lib/libOmxAmrRtpDec.so' does not exist
remote object '/system/lib/libOmxAacEnc.so' does not exist
remote object '/system/lib/libmm-adspsvc.so' does not exist
remote object '/system/lib/libomx_aacdec_sharedlibrary.so' does not exist
remote object '/system/lib/libomx_amrdec_sharedlibrary.so' does not exist
remote object '/system/lib/libomx_amrenc_sharedlibrary.so' does not exist
remote object '/system/lib/libomx_avcdec_sharedlibrary.so' does not exist
remote object '/system/lib/libomx_m4vdec_sharedlibrary.so' does not exist
remote object '/system/lib/libomx_mp3dec_sharedlibrary.so' does not exist
remote object '/system/lib/libomx_sharedlibrary.so' does not exist
165 KB/s (13984 bytes in 0.082s)
401 KB/s (36028 bytes in 0.087s)
4728 KB/s (1116992 bytes in 0.230s)
336 KB/s (30112 bytes in 0.087s)
59 KB/s (4944 bytes in 0.081s)
3510 KB/s (1116992 bytes in 0.310s)
3095 KB/s (1136272 bytes in 0.358s)
246 KB/s (22156 bytes in 0.087s)
932 KB/s (97128 bytes in 0.101s)
1108 KB/s (129136 bytes in 0.113s)
301 KB/s (27048 bytes in 0.087s)
332 KB/s (29876 bytes in 0.087s)
59 KB/s (5012 bytes in 0.081s)
157 KB/s (13340 bytes in 0.082s)
1863 KB/s (218676 bytes in 0.114s)
781 KB/s (83296 bytes in 0.104s)
612 KB/s (62568 bytes in 0.099s)
980 KB/s (58560 bytes in 0.058s)
820 KB/s (87136 bytes in 0.103s)
626 KB/s (62664 bytes in 0.097s)
441 KB/s (41956 bytes in 0.092s)
378 KB/s (34012 bytes in 0.087s)
1382 KB/s (98480 bytes in 0.069s)
110 KB/s (9264 bytes in 0.081s)
322 KB/s (28972 bytes in 0.087s)
108 KB/s (9176 bytes in 0.082s)
291 KB/s (26240 bytes in 0.087s)
111 KB/s (9304 bytes in 0.081s)
1022 KB/s (61352 bytes in 0.058s)
360 KB/s (32364 bytes in 0.087s)
951 KB/s (97128 bytes in 0.099s)
661 KB/s (66764 bytes in 0.098s)
369 KB/s (17520 bytes in 0.046s)
111 KB/s (9272 bytes in 0.081s)
370 KB/s (18116 bytes in 0.047s)
61 KB/s (5140 bytes in 0.081s)
android_env>
Click to expand...

:confused: I suspect I need to flash back to the OEM ROM, but didn't want to go through the hassle if it's really something else. I'm not sure I "need" all of the missing files, but at this point I know I need the one.

:cool: I sent a donation this morning (before sleeping through my compile). I appreciate all your hard work, now more than just a "thank" click.
 
RedAnt said:
:confused: I suspect I need to flash back to the OEM ROM, but didn't want to go through the hassle if it's really something else. I'm not sure I "need" all of the missing files, but at this point I know I need the one.
Click to expand...

As others have said here & in other places, the extract-files.sh only works when in Froyo (kind of a pain if you ask me). If I ever get it to work, I'd try to package it all up and just post them somewhere so people don't have to go through these hassles just to build (if someone does it before me, that'd be even better :) There may even be updated blobs out there somewhere on the interwebs instead of always grabbing the old Froyo ones from the phone.
 
I just restored my 2.2 stock ROM and extracted the files. I am not sure exactly where they got put. I think it would be /username/android/system/vendor/motorola/triumph. If that is correct, I can probably put them on github or make a zip to download for them. If someone who knows a bit better tells me if I am right (or if I am wrong and the appropriate directory), I can make sure they are available without having to flash 2.2 to pull them.
 
Whyzor said:
As others have said here & in other places, the extract-files.sh only works when in Froyo (kind of a pain if you ask me). If I ever get it to work, I'd try to package it all up and just post them somewhere so people don't have to go through these hassles just to build (if someone does it before me, that'd be even better :) There may even be updated blobs out there somewhere on the interwebs instead of always grabbing the old Froyo ones from the phone.
Click to expand...

Sorry, I reviewed the entire thread last night a number of times and never noticed any reference to having to use the stock OEM ROM.

Do I need to rerun Part III "get-rommanager" with the OEM ROM too?
 
RedAnt said:
Sorry, I reviewed the entire thread last night a number of times and never noticed any reference to having to use the stock OEM ROM.

Do I need to rerun Part III "get-rommanager" with the OEM ROM too?
Click to expand...
This post is where we started talking about needing them from stock (at least the latest time it was mentioned). You don't need your phone to be connected for the rommanager part, although I redid that part after re pulling the files from the stock ROM. Just to be safe, it probably wasn't necessary.
 
agentc13 said:
I just restored my 2.2 stock ROM and extracted the files. I am not sure exactly where they got put. I think it would be /username/android/system/vendor/motorola/triumph. If that is correct, I can probably put them on github or make a zip to download for them. If someone who knows a bit better tells me if I am right (or if I am wrong and the appropriate directory), I can make sure they are available without having to flash 2.2 to pull them.
Click to expand...

If you examine the ~/android/system/device/motorola/triumph/extract-files.sh script, the first half does adb pull from a device and puts them in "../../../vendor/$VENDOR/$DEVICE/proprietary". Then the 2nd half copies them to various directories. If we have a packaged zip or tar.gz file to replace the adb pull into proprietary/ dir, then a 2nd-half only extract-files.sh script can be made to just take it from the pkg-extracted paths.

So the short answer is, package up "~/android/system/vendor/motorola/triumph/proprietary/", that path doesn't exist on my machine.
 
Whyzor said:
If you examine the ~/android/system/device/motorola/triumph/extract-files.sh script, the first half does adb pull from a device and puts them in "../../../vendor/$VENDOR/$DEVICE/proprietary". Then the 2nd half copies them to various directories. If we have a packaged zip or tar.gz file to replace the adb pull into proprietary/ dir, then a 2nd-half only extract-files.sh script can be made to just take it from the pkg-extracted paths.
Click to expand...
OK, I will look at that when I get a chance. I am not on my laptop to check it out right now. I am sure I can get the files posted, but I suck at scripting/programming so someone else will have to mess with that part.
 
Thanks for the help!

I just finished a nandroid backup (cm7) and restore (OEM). It's amazing how loud that Virgin Mobil boot sound is, and what my phone looked like 5 weeks ago when I switched over to CM7.

The extract worked perfectly from OEM ROM. Now starting my phone restore, as well as my compile.
 
alright so I just finished compiling a build with an updated frameworks base, I guess I can customize it a little.
 
b_randon14 said:
If I get a chance tonight I will set it up to where it pits the files where it needs to be and sets everything up with a script!
Click to expand...

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.
 
I swear, just trying to get Ubuntu on my Parallels VM is already a challenge. LOL (It is using 3.0 kernel, something that Parallels 6 doesn't support.

Is it possible to build CM7 with the new drivers and new fixes that have been "discovered"?
 
Sorry for the dumb question, but am I correct in assuming that this can only be done on Linux, not on Windows?
 
minus5252 said:
Sorry for the dumb question, but am I correct in assuming that this can only be done on Linux, not on Windows?
Click to expand...
Correct. Although you could try a linux virtual machine on windows PC. I had issues building correctly when doing that and just set up my laptop to dual boot. (It has been years since I dual booted linux on something, lol)
 
Whyzor said:
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.
Click to expand...

Yeah I was going to modify his script(but make it a new one that people can download with the blobs and have it copy from where you extract them at the the vendor folders then set everything up.
 
target Executable: wpa_cli (out/target/product/triumph/obj/EXECUTABLES/wpa_cli_intermediates/LINKED/wpa_cli)
target Executable: ip-up-vpn (out/target/product/triumph/obj/EXECUTABLES/ip-up-vpn_intermediates/LINKED/ip-up-vpn)
Copying: out/target/common/obj/JAVA_LIBRARIES/sqlite-jdbc_intermediates/classes-jarjar.jar
target SharedLib: librpc (out/target/product/triumph/obj/SHARED_LIBRARIES/librpc_intermediates/LINKED/librpc.so)
target SharedLib: gralloc.default (out/target/product/triumph/obj/SHARED_LIBRARIES/gralloc.default_intermediates/LINKED/gralloc.default.so)
target Strip: lights.triumph (out/target/product/triumph/obj/lib/lights.triumph.so)
target SharedLib: liboverlay (out/target/product/triumph/obj/SHARED_LIBRARIES/liboverlay_intermediates/LINKED/liboverlay.so)
target SharedLib: sensors.goldfish (out/target/product/triumph/obj/SHARED_LIBRARIES/sensors.goldfish_intermediates/LINKED/sensors.goldfish.so)
target SharedLib: libacc (out/target/product/triumph/obj/SHARED_LIBRARIES/libacc_intermediates/LINKED/libacc.so)
Install: out/target/product/triumph/system/lib/libc_malloc_debug_leak.so
Install: out/target/product/triumph/system/lib/libc_malloc_debug_qemu.so
Install: out/target/product/triumph/system/lib/libthread_db.so
target Generated: libv8 <= out/host/linux-x86/bin/mksnapshot
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):
make: *** [out/target/product/triumph/obj/STATIC_LIBRARIES/libv8_intermediates/snapshot.cc] Aborted
make: *** Waiting for unfinished jobs....
target SharedLib: libcyanogen-dsp (out/target/product/triumph/obj/SHARED_LIBRARIES/libcyanogen-dsp_intermediates/LINKED/libcyanogen-dsp.so)
Click to expand...

What's going on? I'm compiling on Gentoo, so I might be missing a required lib.
 
hamfactorial said:
This is CM7, following the directions from the OP. This happens after "brunch triumph"
Click to expand...

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):
 
You must log in or register to reply here.
Back
Top Bottom