Run ...
. build/envsetup.sh
lunch
make bacon

Those are not errors envsetup is a script to load variables and methods called by the build system into the memory (enviroment). Think of it as getting into a car.

Then we customized the environment for your device with lunch or brunch (brunch is a customized version of lunch both are initialized in envsetup.sh). Think of lunch as checking the mirrors and adjusting the seat. ( brunch actually starts the build)

Now we are ready to build make otapackage or make bacon. This is where the actual compiling begins or to keep the analogy going like starting the car and driving off. (bacon is a cm customized version of otapackage)

 

Ok. Looks like I've got another issue.

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

When I do this running non-root I get a permission denied error at the end.

 

You setup something while logged in as root and now thatvu are regular user you don't have permission to access.

In non phone Linux root should almost never be used.

I think you can run sudo chown -r ~/android $USERNAME:$USERNAME

them try again

 

Ok looks like that solved it. As for the above code, turns out I needed to add "LOCAL_MODULE_TAGS := optional" above grub stage 1, gurb pre stage 2 and stage 2.

Now I'm getting:

<br />
find: `out/target/common/docs/gen': No such file or directory<br />
find: `out/target/common/docs/gen': No such file or directory<br />
find: `out/target/common/docs/gen': No such file or directory<br />
find: `out/target/common/docs/gen': No such file or directory<br />
find: `out/target/common/docs/gen': No such file or directory<br />
make: *** No rule to make target `bacon'.  Stop.<br />

 

if bacon is unavailable use otapackage

 

It worked but the recovery.img was too big. I fear with all my messing around I may have messed up something. I'll go though the whole process again and see what happens.

 

I assume you are trying to build a recovery.img... cd to your device dir and you'll see a BoardConfig.mk. Make sure you have the correct BOOTIMAGE size

<br />
TARGET_BOOTLOADER_BOARD_NAME := mecha<br />
<br />
# Use stock libril for now<br />
TARGET_PROVIDES_LIBRIL := vendor/htc/mecha/proprietary/libril.so<br />
BOARD_MOBILEDATA_INTERFACE_NAME := "rmnet_sdio0"<br />
BOARD_HAS_EXTRA_SYS_PROPS := true<br />
USE_IPV6_ROUTE := true<br />
<br />
# Additional Camera hacks for mecha<br />
#BOARD_HAVE_HTC_FFC := true<br />
#BOARD_USE_REVERSE_FFC := true<br />
<br />
# Hack for improper scaling.<br />
BOARD_OVERLAY_MINIFICATION_LIMIT := 2<br />
BOARD_USES_GENLOCK := true<br />
TARGET_FORCE_CPU_UPLOAD := true<br />
BOARD_VENDOR_QCOM_GPS_LOC_API_HARDWARE := mecha<br />
BOARD_VENDOR_QCOM_GPS_LOC_API_AMSS_VERSION := 50000<br />
<br />
BOARD_SYSTEMIMAGE_PARTITION_SIZE := 585101312<br />
BOARD_USERDATAIMAGE_PARTITION_SIZE := 1232072704<br />
BOARD_BOOTIMAGE_PARTITION_SIZE := 4194304 <-- Most Important!!!<br />
BOARD_FLASH_BLOCK_SIZE := 262144<br />

Once thats done to build do

<br />
. build/envsetup.sh && full_deviceName-eng && make -j* recoveryimage<br />

Replace the * with how many processors you have.

 

Looks like doing this:

<br />
. build/envsetup.sh && full_deviceName-eng && make -j* recoveryimage<br />

gives me this:

<br />
kyocera_milano-eng: command not found<br />

Also I'm wondering, do I have to change

<br />
BOARD_FLASH_BLOCK_SIZE :=<br />

Right now it's set at 131072 is that default or does the build get that automatically?
When I do a cat /proc/mtd I get 00040000 as my block size....I think. According to one forum I read the erasesize is the block size.

 

I'm a dummy and forgot the "lunch" command. Kind of important. It would be

<br />
. build/envsetup.sh && lunch full_milano-eng && make -j<*how many procs you have> recoveryimage<br />

Paste what you get from cat /proc/mtd and I'll see if I can help you more.

 

Ok....

<br />
# export PATH=/data/local/bin:$PATH<br />
# cat proc/mtd<br />
dev:    size  erasesize  name<br />
mtd0: 00600000 00040000 "boot"<br />
mtd1: 08e00000 00040000 "system"<br />
mtd2: 02780000 00040000 "fota"<br />
mtd3: 00100000 00040000 "pltable"<br />
mtd4: 00100000 00040000 "splash"<br />
mtd5: 00600000 00040000 "recovery"<br />
mtd6: 09640000 00040000 "userdata"<br />
mtd7: 06f00000 00040000 "cache"<br />
#<br />

 

I'd use 0x00600000. The proper way would be to convert it to Hex though

 

I took a moment to re-read this thread, I am getting the sense you are not just building CyanogenMod for the first time but are trying to builld it for a non-supported device. I.E make the first CyanogenMod rom for it. Is that what you are trying to?

Basically what is it that you are trying to accomplish here?

 

Yes. That is what I am trying to accomplish. It is for my Kyocera Milano which is an non-supported phone.

 

Ah, this will be the first in a long line of errors. You are about to become an expert in GoogleFu.

 

I compiled and the recovery image booted. Only it looks like someone took the smudge tool to the main menu. I'll post a picture if you want to take a look.

 

Sure.

 

Allright:

It's funny. Everything otherwise works fine. The nav buttons and menu navigation work fine.

 

Did you use the correct boot.img or does the phone even use one?

 

Yes I did. I extracted one from the phone and that's the one I used.

 

I had issues with the "make otatools" command where it was creating my unpackbootimg. I had to build it on its own and move it to my /bin dir or my platform-tools dir.

It doesnt seem that its dealing with your boot.img correctly. Just a thought to go over the steps again and see if it spouts any errors that you didn't see.