Anybody interested in AOSP ICS for Locked Bootloader?

SpaceCaker

Senior Member
Mar 26, 2011
13,545
10,901
0
netherlands
www.youtube.com
My problems with sources (every codes)
For example PolisBlood 4.2
I succesfully upload mango files to my server
This files: https://github.com/kovacslaszlo13/android_device_semc_mango
Code:
[email protected]:~/pbjb4.2$ . build/envsetup.sh
including device/generic/armv7-a-neon/vendorsetup.sh
including device/generic/armv7-a/vendorsetup.sh
including device/generic/mips/vendorsetup.sh
including device/generic/x86/vendorsetup.sh
including device/semc/coconut/vendorsetup.sh
including device/semc/haida/vendorsetup.sh
including device/semc/mango/vendorsetup.sh
including sdk/bash_completion/adb.bash
[email protected]:~/pbjb4.2$
Now i try to start:
Code:
[email protected]:~/pbjb4.2$ lunch

You're building on Linux

Lunch menu... pick a combo:
     1. full-eng
     2. full_x86-eng
     3. vbox_x86-eng
     4. full_mips-eng
     5. mini_armv7a_neon-userdebug
     6. mini_armv7a-userdebug
     7. mini_mips-userdebug
     8. mini_x86-userdebug
     9. full_coconut-userdebug
     10. full_haida-eng
     11. cm_mango-eng

Which would you like? [full-eng]
And when i try to choose cm_mango-eng
Code:
Which would you like? [full-eng] 11
build/core/product_config.mk:223: *** Cannot locate config makefile for product "cm_mango".  Stop.

** Don't have a product spec for: 'cm_mango'
** Do you have the right repo manifest?

[email protected]:~/pbjb4.2$
So whats the problem?

This problems are in AOSP ICS/JB 4.1 and PolishBlood 4.2 too
do brunch cm_mango-userdebug instead

Sent from my S500 using xda app-developers app
 
  • Like
Reactions: leslie_smith

Diatosta

Member
Feb 4, 2012
9
0
0
So, is this dead? I really wanted AOSP, and as my LWW is locked bootloader, this was my only chance, cause I don't like other roms at all (too much rom control and stuff, just give me default please) :p