• 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

I'll give it a whirl.

Edit: Ok so building as is with your updated experimental branches in android_hardware_libhardware, android_hardware_msm7k, android_frameworks_base AND android_device_motorola_triumph. The first attempt, got this:

Code:
Checking build tools versions...
build/core/base_rules.mk:78: *** Module name: gralloc.triumph
build/core/base_rules.mk:79: *** Makefile location: device/motorola/triumph/libgralloc-qsd8k
build/core/base_rules.mk:80: * 
build/core/base_rules.mk:81: * Each module must use a LOCAL_MODULE_TAGS in its
build/core/base_rules.mk:82: * Android.mk. Possible tags declared by a module:
build/core/base_rules.mk:83: * 
build/core/base_rules.mk:84: *     optional, debug, eng, tests, samples
build/core/base_rules.mk:85: * 
build/core/base_rules.mk:86: * If the module is expected to be in all builds
build/core/base_rules.mk:87: * of a product, then it should use the
build/core/base_rules.mk:88: * "optional" tag: 
build/core/base_rules.mk:89: * 
build/core/base_rules.mk:90: *    Add "LOCAL_MODULE_TAGS := optional" in the
build/core/base_rules.mk:91: *    Android.mk for the affected module, and add
build/core/base_rules.mk:92: *    the LOCAL_MODULE value for that component
build/core/base_rules.mk:93: *    into the PRODUCT_PACKAGES section of product
build/core/base_rules.mk:94: *    makefile(s) where it's necessary, if
build/core/base_rules.mk:95: *    appropriate.
build/core/base_rules.mk:96: * 
build/core/base_rules.mk:97: * If the component should be in EVERY build of ALL
build/core/base_rules.mk:98: * products, then add its LOCAL_MODULE value to the
build/core/base_rules.mk:99: * PRODUCT_PACKAGES section of
build/core/base_rules.mk:100: * build/target/product/core.mk
build/core/base_rules.mk:101: * 
build/core/base_rules.mk:102: *** user tag detected on new module - user tags are only supported on legacy modules.  Stop.
I then added the missing LOCAL_MODULE_TAGS := optional to Android.mk in device/motorola/triumph/libgralloc-qsd8k.

The 2nd attempt after adding the line got this:

[C++] host C: libpng <= external/libpng/pnggccrd.c host C: libpng <= external/libpng/ - Pastebin.com

Damn it. Alright, I'll try and fix that issue too. Good catch on the missing module tags in the local gralloc, I'll fix that up too. I think we're getting closer to getting it to build though.
 
You never answered the other guys post so im going to take it you have to pull the proprietary files from the stock rom?
I noticed pulling from cm7 and there seems to be some libraries missing.
 
I'm getting errors on this step:
Code:
whyzor@ubuntu:~/android/system$ repo init -u git://github.com/ikarosdev/android.git -b gingerbread
Traceback (most recent call last):
  File "/home/whyzor/bin/repo", line 690, in <module>
    main(sys.argv[1:])
  File "/home/whyzor/bin/repo", line 657, in main
    _Init(args)
  File "/home/whyzor/bin/repo", line 189, in _Init
    _CheckGitVersion()
  File "/home/whyzor/bin/repo", line 214, in _CheckGitVersion
    proc = subprocess.Popen(cmd, stdout=subprocess.PIPE)
  File "/usr/lib/python2.7/subprocess.py", line 679, in __init__
    errread, errwrite)
  File "/usr/lib/python2.7/subprocess.py", line 1239, in _execute_child
    raise child_exception
OSError: [Errno 2] No such file or directory
 
I'm getting errors on this step:
Code:
whyzor@ubuntu:~/android/system$ repo init -u git://github.com/ikarosdev/android.git -b gingerbread
Traceback (most recent call last):
  File "/home/whyzor/bin/repo", line 690, in <module>
    main(sys.argv[1:])
  File "/home/whyzor/bin/repo", line 657, in main
    _Init(args)
  File "/home/whyzor/bin/repo", line 189, in _Init
    _CheckGitVersion()
  File "/home/whyzor/bin/repo", line 214, in _CheckGitVersion
    proc = subprocess.Popen(cmd, stdout=subprocess.PIPE)
  File "/usr/lib/python2.7/subprocess.py", line 679, in __init__
    errread, errwrite)
  File "/usr/lib/python2.7/subprocess.py", line 1239, in _execute_child
    raise child_exception
OSError: [Errno 2] No such file or directory

Looks like you didn't install git. Did you install all the build deps?
 
I'm getting errors on this step:
Code:
whyzor@ubuntu:~/android/system$ repo init -u git://github.com/ikarosdev/android.git -b gingerbread
Traceback (most recent call last):
  File "/home/whyzor/bin/repo", line 690, in <module>
    main(sys.argv[1:])
  File "/home/whyzor/bin/repo", line 657, in main
    _Init(args)
  File "/home/whyzor/bin/repo", line 189, in _Init
    _CheckGitVersion()
  File "/home/whyzor/bin/repo", line 214, in _CheckGitVersion
    proc = subprocess.Popen(cmd, stdout=subprocess.PIPE)
  File "/usr/lib/python2.7/subprocess.py", line 679, in __init__
    errread, errwrite)
  File "/usr/lib/python2.7/subprocess.py", line 1239, in _execute_child
    raise child_exception
OSError: [Errno 2] No such file or directory

You don't have the correct repo installed. Look at this post 102 from earlier in the thread:

http://androidforums.com/triumph-al...d7-source-development-area-3.html#post3453116
 
Ok, I figured out my problem above, I skipped the 32bit & 64bit section & only got the 64bit section first time around. But now it's having trouble connecting to github.com/ikarosdev/android.git it seems.

Code:
whyzor@ubuntu:~/android/system$ repo init -u git://github.com/ikarosdev/android.git -b gingerbread
gpg: keyring `/home/whyzor/.repoconfig/gnupg/secring.gpg' created
gpg: keyring `/home/whyzor/.repoconfig/gnupg/pubring.gpg' created
gpg: /home/whyzor/.repoconfig/gnupg/trustdb.gpg: trustdb created
gpg: key 920F5C65: public key "Repo Maintainer <repo@android.kernel.org>" imported
gpg: Total number processed: 1
gpg:               imported: 1

Get https://android.googlesource.com/tools/repo
remote: Counting objects: 1462, done
remote: Finding sources: 100% (80/80)
remote: Total 1462 (delta 952), reused 1462 (delta 952)
Receiving objects: 100% (1462/1462), 437.79 KiB | 654 KiB/s, done.
Resolving deltas: 100% (952/952), done.
From https://android.googlesource.com/tools/repo
 * [new branch]      maint      -> origin/maint
 * [new branch]      master     -> origin/master
 * [new branch]      stable     -> origin/stable
 * [new tag]         v1.0       -> v1.0
 * [new tag]         v1.0.1     -> v1.0.1
 * [new tag]         v1.0.2     -> v1.0.2
 * [new tag]         v1.0.3     -> v1.0.3
 * [new tag]         v1.0.4     -> v1.0.4
 * [new tag]         v1.0.5     -> v1.0.5
 * [new tag]         v1.0.6     -> v1.0.6
 * [new tag]         v1.0.7     -> v1.0.7
 * [new tag]         v1.0.8     -> v1.0.8
 * [new tag]         v1.0.9     -> v1.0.9
 * [new tag]         v1.1       -> v1.1
 * [new tag]         v1.2       -> v1.2
 * [new tag]         v1.3       -> v1.3
 * [new tag]         v1.3.1     -> v1.3.1
 * [new tag]         v1.3.2     -> v1.3.2
 * [new tag]         v1.4       -> v1.4
 * [new tag]         v1.4.1     -> v1.4.1
 * [new tag]         v1.4.2     -> v1.4.2
 * [new tag]         v1.4.3     -> v1.4.3
 * [new tag]         v1.4.4     -> v1.4.4
 * [new tag]         v1.5       -> v1.5
 * [new tag]         v1.5.1     -> v1.5.1
 * [new tag]         v1.6       -> v1.6
 * [new tag]         v1.6.1     -> v1.6.1
 * [new tag]         v1.6.10    -> v1.6.10
 * [new tag]         v1.6.10.1  -> v1.6.10.1
 * [new tag]         v1.6.10.2  -> v1.6.10.2
 * [new tag]         v1.6.2     -> v1.6.2
 * [new tag]         v1.6.3     -> v1.6.3
 * [new tag]         v1.6.4     -> v1.6.4
 * [new tag]         v1.6.5     -> v1.6.5
 * [new tag]         v1.6.6     -> v1.6.6
 * [new tag]         v1.6.7     -> v1.6.7
 * [new tag]         v1.6.7.1   -> v1.6.7.1
 * [new tag]         v1.6.7.2   -> v1.6.7.2
 * [new tag]         v1.6.7.3   -> v1.6.7.3
 * [new tag]         v1.6.7.4   -> v1.6.7.4
 * [new tag]         v1.6.7.5   -> v1.6.7.5
 * [new tag]         v1.6.8     -> v1.6.8
 * [new tag]         v1.6.8.1   -> v1.6.8.1
 * [new tag]         v1.6.8.10  -> v1.6.8.10
 * [new tag]         v1.6.8.11  -> v1.6.8.11
 * [new tag]         v1.6.8.2   -> v1.6.8.2
 * [new tag]         v1.6.8.3   -> v1.6.8.3
 * [new tag]         v1.6.8.4   -> v1.6.8.4
 * [new tag]         v1.6.8.5   -> v1.6.8.5
 * [new tag]         v1.6.8.6   -> v1.6.8.6
 * [new tag]         v1.6.8.7   -> v1.6.8.7
 * [new tag]         v1.6.8.8   -> v1.6.8.8
 * [new tag]         v1.6.8.9   -> v1.6.8.9
 * [new tag]         v1.6.9     -> v1.6.9
 * [new tag]         v1.6.9.1   -> v1.6.9.1
 * [new tag]         v1.6.9.2   -> v1.6.9.2
 * [new tag]         v1.6.9.3   -> v1.6.9.3
 * [new tag]         v1.6.9.4   -> v1.6.9.4
 * [new tag]         v1.6.9.5   -> v1.6.9.5
 * [new tag]         v1.6.9.6   -> v1.6.9.6
 * [new tag]         v1.6.9.7   -> v1.6.9.7
 * [new tag]         v1.6.9.8   -> v1.6.9.8
 * [new tag]         v1.7       -> v1.7
 * [new tag]         v1.7.1     -> v1.7.1
 * [new tag]         v1.7.2     -> v1.7.2
 * [new tag]         v1.7.3     -> v1.7.3
 * [new tag]         v1.7.3.1   -> v1.7.3.1
 * [new tag]         v1.7.4     -> v1.7.4
 * [new tag]         v1.7.4.1   -> v1.7.4.1
 * [new tag]         v1.7.4.2   -> v1.7.4.2
 * [new tag]         v1.7.4.3   -> v1.7.4.3
 * [new tag]         v1.7.5     -> v1.7.5
 * [new tag]         v1.7.6     -> v1.7.6
 * [new tag]         v1.7.6.1   -> v1.7.6.1
 * [new tag]         v1.7.7     -> v1.7.7
 * [new tag]         v1.7.7.1   -> v1.7.7.1
 * [new tag]         v1.7.7.2   -> v1.7.7.2
 * [new tag]         v1.7.7.3   -> v1.7.7.3
 * [new tag]         v1.7.7.4   -> v1.7.7.4
 * [new tag]         v1.7.7.5   -> v1.7.7.5
 * [new tag]         v1.7.7.6   -> v1.7.7.6
 * [new tag]         v1.7.8     -> v1.7.8
 * [new tag]         v1.7.8.1   -> v1.7.8.1
Get git://github.com/ikarosdev/android.git
github.com[0: 207.97.227.239]: errno=Connection refused
fatal: unable to connect a socket (Connection refused)
github.com[0: 207.97.227.239]: errno=Connection refused
fatal: unable to connect a socket (Connection refused)
fatal: cannot obtain manifest git://github.com/ikarosdev/android.git
Is there an easier way to get the proprietary blobs? I have Ubuntu running in a VMware environment, and don't think it can grab the files from my phone without jumping through a lot of hoops. Either way it seems that konspiracy mentioned that it's missing a few files to build anyway. Can someone just zip them up and post them?
 
Ok, I figured out my problem above, I skipped the 32bit & 64bit section & only got the 64bit section first time around. But now it's having trouble connecting to github.com/ikarosdev/android.git it seems.

Code:
whyzor@ubuntu:~/android/system$ repo init -u git://github.com/ikarosdev/android.git -b gingerbread
gpg: keyring `/home/whyzor/.repoconfig/gnupg/secring.gpg' created
gpg: keyring `/home/whyzor/.repoconfig/gnupg/pubring.gpg' created
gpg: /home/whyzor/.repoconfig/gnupg/trustdb.gpg: trustdb created
gpg: key 920F5C65: public key "Repo Maintainer <repo@android.kernel.org>" imported
gpg: Total number processed: 1
gpg:               imported: 1
 
Get https://android.googlesource.com/tools/repo
remote: Counting objects: 1462, done
remote: Finding sources: 100% (80/80)
remote: Total 1462 (delta 952), reused 1462 (delta 952)
Receiving objects: 100% (1462/1462), 437.79 KiB | 654 KiB/s, done.
Resolving deltas: 100% (952/952), done.
From https://android.googlesource.com/tools/repo
 * [new branch]      maint      -> origin/maint
 * [new branch]      master     -> origin/master
 * [new branch]      stable     -> origin/stable
 * [new tag]         v1.0       -> v1.0
 * [new tag]         v1.0.1     -> v1.0.1
 * [new tag]         v1.0.2     -> v1.0.2
 * [new tag]         v1.0.3     -> v1.0.3
 * [new tag]         v1.0.4     -> v1.0.4
 * [new tag]         v1.0.5     -> v1.0.5
 * [new tag]         v1.0.6     -> v1.0.6
 * [new tag]         v1.0.7     -> v1.0.7
 * [new tag]         v1.0.8     -> v1.0.8
 * [new tag]         v1.0.9     -> v1.0.9
 * [new tag]         v1.1       -> v1.1
 * [new tag]         v1.2       -> v1.2
 * [new tag]         v1.3       -> v1.3
 * [new tag]         v1.3.1     -> v1.3.1
 * [new tag]         v1.3.2     -> v1.3.2
 * [new tag]         v1.4       -> v1.4
 * [new tag]         v1.4.1     -> v1.4.1
 * [new tag]         v1.4.2     -> v1.4.2
 * [new tag]         v1.4.3     -> v1.4.3
 * [new tag]         v1.4.4     -> v1.4.4
 * [new tag]         v1.5       -> v1.5
 * [new tag]         v1.5.1     -> v1.5.1
 * [new tag]         v1.6       -> v1.6
 * [new tag]         v1.6.1     -> v1.6.1
 * [new tag]         v1.6.10    -> v1.6.10
 * [new tag]         v1.6.10.1  -> v1.6.10.1
 * [new tag]         v1.6.10.2  -> v1.6.10.2
 * [new tag]         v1.6.2     -> v1.6.2
 * [new tag]         v1.6.3     -> v1.6.3
 * [new tag]         v1.6.4     -> v1.6.4
 * [new tag]         v1.6.5     -> v1.6.5
 * [new tag]         v1.6.6     -> v1.6.6
 * [new tag]         v1.6.7     -> v1.6.7
 * [new tag]         v1.6.7.1   -> v1.6.7.1
 * [new tag]         v1.6.7.2   -> v1.6.7.2
 * [new tag]         v1.6.7.3   -> v1.6.7.3
 * [new tag]         v1.6.7.4   -> v1.6.7.4
 * [new tag]         v1.6.7.5   -> v1.6.7.5
 * [new tag]         v1.6.8     -> v1.6.8
 * [new tag]         v1.6.8.1   -> v1.6.8.1
 * [new tag]         v1.6.8.10  -> v1.6.8.10
 * [new tag]         v1.6.8.11  -> v1.6.8.11
 * [new tag]         v1.6.8.2   -> v1.6.8.2
 * [new tag]         v1.6.8.3   -> v1.6.8.3
 * [new tag]         v1.6.8.4   -> v1.6.8.4
 * [new tag]         v1.6.8.5   -> v1.6.8.5
 * [new tag]         v1.6.8.6   -> v1.6.8.6
 * [new tag]         v1.6.8.7   -> v1.6.8.7
 * [new tag]         v1.6.8.8   -> v1.6.8.8
 * [new tag]         v1.6.8.9   -> v1.6.8.9
 * [new tag]         v1.6.9     -> v1.6.9
 * [new tag]         v1.6.9.1   -> v1.6.9.1
 * [new tag]         v1.6.9.2   -> v1.6.9.2
 * [new tag]         v1.6.9.3   -> v1.6.9.3
 * [new tag]         v1.6.9.4   -> v1.6.9.4
 * [new tag]         v1.6.9.5   -> v1.6.9.5
 * [new tag]         v1.6.9.6   -> v1.6.9.6
 * [new tag]         v1.6.9.7   -> v1.6.9.7
 * [new tag]         v1.6.9.8   -> v1.6.9.8
 * [new tag]         v1.7       -> v1.7
 * [new tag]         v1.7.1     -> v1.7.1
 * [new tag]         v1.7.2     -> v1.7.2
 * [new tag]         v1.7.3     -> v1.7.3
 * [new tag]         v1.7.3.1   -> v1.7.3.1
 * [new tag]         v1.7.4     -> v1.7.4
 * [new tag]         v1.7.4.1   -> v1.7.4.1
 * [new tag]         v1.7.4.2   -> v1.7.4.2
 * [new tag]         v1.7.4.3   -> v1.7.4.3
 * [new tag]         v1.7.5     -> v1.7.5
 * [new tag]         v1.7.6     -> v1.7.6
 * [new tag]         v1.7.6.1   -> v1.7.6.1
 * [new tag]         v1.7.7     -> v1.7.7
 * [new tag]         v1.7.7.1   -> v1.7.7.1
 * [new tag]         v1.7.7.2   -> v1.7.7.2
 * [new tag]         v1.7.7.3   -> v1.7.7.3
 * [new tag]         v1.7.7.4   -> v1.7.7.4
 * [new tag]         v1.7.7.5   -> v1.7.7.5
 * [new tag]         v1.7.7.6   -> v1.7.7.6
 * [new tag]         v1.7.8     -> v1.7.8
 * [new tag]         v1.7.8.1   -> v1.7.8.1
Get git://github.com/ikarosdev/android.git
github.com[0: 207.97.227.239]: errno=Connection refused
fatal: unable to connect a socket (Connection refused)
github.com[0: 207.97.227.239]: errno=Connection refused
fatal: unable to connect a socket (Connection refused)
fatal: cannot obtain manifest git://github.com/ikarosdev/android.git
Is there an easier way to get the proprietary blobs? I have Ubuntu running in a VMware environment, and don't think it can grab the files from my phone without jumping through a lot of hoops. Either way it seems that konspiracy mentioned that it's missing a few files to build anyway. Can someone just zip them up and post them?

You need to be running the stock Froyo ROM to get all of the files. CM7 or MIUI won't work. That's what Konspiracy was talking about when he said he couldn't get all of the files.

As for connecting your phone to the vmware environment, it will definitely work. After you plug in your phone (with the usb debugging enabled on the phone), on the VMWare Server Home page (start --> all programs --> vmware --> vmware server --> vmware server home page) for your virtual machine, you just need to enable the Foxconn USB device from the USB Controller dropdown at the top of the Home page when you have your virtual machine selected. That will stop Windows from accessing the phone and enable it for the Virtual Machine.
 
You need to be running the stock Froyo ROM to get all of the files. CM7 or MIUI won't work. That's what Konspiracy was talking about when he said he couldn't get all of the files.

As for connecting your phone to the vmware environment, it will definitely work. After you plug in your phone (with the usb debugging enabled on the phone), on the VMWare Server Home page (start --> all programs --> vmware --> vmware server --> vmware server home page) for your virtual machine, you just need to enable the Foxconn USB device from the USB Controller dropdown at the top of the Home page when you have your virtual machine selected. That will stop Windows from accessing the phone and enable it for the Virtual Machine.

I'm running VMWare Player 4.0.1 (free vs paid for server), so don't have those exact settings, but it *SHOULD* pass through USB devices, will have to try this after I get my home computer setup (It doesn't have VMware or Ubuntu yet). My connection problems may be due to firewalls at work, tried pointing to tickerguy's github with same results.

Would it be possible to just store the Motorola blobs on github? The developers for the Optimus V/S/T/M have this for each of their line of devices. I know technically they're not part of open source, but we can't see the code anyway. It's not like there's a lucrative market for it either. It would help get new developers/builders running quicker.
 
If we could get one repo of all the files that would be great. If I had more experience with repo I would but It seems like we have to take things from here or there.
 
Ahh it's nice to see more builders springing up here :). I just redownloaded the CM7 source today. I'm gonna start by building me a custom recovery and then work on a CM7 ROM after I get bROM v1.1 out!!
 
So both times I have tried this It stops after this:
Code:
Fetching projects:  99% (311/314)  Receiving objects:   4% (856/19451), 61.91 Miremote: Total 19451 (delta 10796), reused 18950 (delta 10295)
Receiving objects: 100% (19451/19451), 1.80 GiB | 1.18 MiB/s, done.
Resolving deltas: 100% (10796/10796), done.
From git://github.com/CyanogenMod/android_prebuilt
 * [new branch]      gingerbread -> github/gingerbread
 * [new branch]      gingerbread-release -> github/gingerbread-release
 * [new branch]      ics        -> github/ics
 * [new tag]         cm-7.1.0   -> cm-7.1.0
Is there something I missed? I have been following the instructions to a T.
 
So both times I have tried this It stops after this:
Code:
Fetching projects:  99% (311/314)  Receiving objects:   4% (856/19451), 61.91 Miremote: Total 19451 (delta 10796), reused 18950 (delta 10295)
Receiving objects: 100% (19451/19451), 1.80 GiB | 1.18 MiB/s, done.
Resolving deltas: 100% (10796/10796), done.
From git://github.com/CyanogenMod/android_prebuilt
 * [new branch]      gingerbread -> github/gingerbread
 * [new branch]      gingerbread-release -> github/gingerbread-release
 * [new branch]      ics        -> github/ics
 * [new tag]         cm-7.1.0   -> cm-7.1.0
Is there something I missed? I have been following the instructions to a T.

No, you didn't do anything wrong. For whatever reason, sometimes it stops syncing and just sits. It's some kind of remote connection error (without ever giving you an error). When it occurs, just press ctrl+z and then type:

Code:
killall -9 repo && killall -9 python
and run the "repo sync" command again.
 
So I did a compare with Tickerguy's 10/2 build that he just uploaded and my build from your github and there's a whole bunch of stuff different... Seems that the build on github was updated to the latest cm7 (2.3.7) compared to the 2.3.5 in Tickerguy's 10/2 build.
1.jpg

Why are you doing a comparison to such an older build (10/2)? That last one was released 11/19.

The reason why your build is 2.3.7 is because CM7 upstream is 2.3.7. The device folder (a.k.a my Github stuff) is only the configurations to build CM7 specifically for the Triumph.
 
Why are you doing a comparison to such an older build (10/2)? That last one was released 11/19.

The reason why your build is 2.3.7 is because CM7 upstream is 2.3.7. The device folder (a.k.a my Github stuff) is only the configurations to build CM7 specifically for the Triumph.

Pretty sure that is a spam post. They talked about something similar in the guide forums, I reported it for the mods to take care of. The spammers copy some other post and add broken pic links for a site or something like that.

Also, thanks for the explanation. Too bad it happens after it's been downloading forever. :(
 
Pretty sure that is a spam post. They talked about something similar in the guide forums, I reported it for the mods to take care of. The spammers copy some other post and add broken pic links for a site or something like that.

Also, thanks for the explanation. Too bad it happens after it's been downloading forever. :(

Running repo sync after that issue will just pick back up where it left off. If you were 99% done, it'll just start back up there.
 
Okay so I'm pulling proprietary files from the device(I had had it working before last tiime I tried to build before, so I now ADB works on my Ubuntu install) but now everytime I execute extract-files.sh I get this error:

Code:
error: insufficient permissions for device
This shows up a bunch(One for everytime it's supposed to pull a file in the sh script. Don't know what is going on!!

EDIT**:After further inspection whenever I do a ADB devices to list the devices connected, I gives me a device of a bunch of questions marks and it says no permission out from it!! I don't know what I have messed up here lol!

Code:
????????????    no permissions
 
Okay so I'm pulling proprietary files from the device(I had had it working before last tiime I tried to build before, so I now ADB works on my Ubuntu install) but now everytime I execute extract-files.sh I get this error:

Code:
error: insufficient permissions for device
This shows up a bunch(One for everytime it's supposed to pull a file in the sh script. Don't know what is going on!!

EDIT**:After further inspection whenever I do a ADB devices to list the devices connected, I gives me a device of a bunch of questions marks and it says no permission out from it!! I don't know what I have messed up here lol!

Code:
????????????    no permissions

here man check this out... it should be of some help to you! :D

ADB: "no permissions" (Linux Mint 9) [SOLVED] - xda-developers
 
Gettinf this error when trying to build the recovery image. It seems like maybe this device is missing from the CM7 source at the moment?

Code:
build/core/product_config.mk:194: *** _nic.PRODUCTS.[[vendor/cyanogen/products/cyanogen_cooper.mk]]: "device/samsung/cooper/device_cooper.mk" does not exist.  Stop.

I believe I am missing some of the device repositories for some of these devices. I have been commenting out those porduct make files under /vendor/cyanogen/products and everytime I get another error for another device that I don't have a /device/<devie name> folder for. I dont know why I am missing these files!! I synced just before I started doing this!!
 
Gettinf this error when trying to build the recovery image. It seems like maybe this device is missing from the CM7 source at the moment?

Code:
build/core/product_config.mk:194: *** _nic.PRODUCTS.[[vendor/cyanogen/products/cyanogen_cooper.mk]]: "[B]device/samsung/cooper/device_cooper.mk[/B]" does not exist.  Stop.
I believe I am missing some of the device repositories for some of these devices. I have been commenting out those porduct make files under /vendor/cyanogen/products and everytime I get another error for another device that I don't have a /device/<devie name> folder for. I dont know why I am missing these files!! I synced just before I started doing this!!

Code:
"[B]device/samsung/cooper/device_cooper.mk[/B]"

It's complaining that the device makefile for the Samsung Cooper is missing. This shouldn't be the case as the Cooper was added to the manifest on October 30, 2011. My GB manifest is current with upstream's. https://github.com/ikarosdev/android/commits/gingerbread

Are you sure all the device configs were pulled correctly?
 
Well actually I used tickerguy's git repository so his manifest may not be up to date :S I didn't think about that lol!

But yeah I'm gonna see if I can work around it!
 
Back
Top Bottom