Hi,
I am trying to port cyanogenmod 13.0 to the Lenovo K3 note.
I have two problems that I have not been able to solve despite googling and searching this forum. Any answers would be appreciated.
Problem 1)
Build terminates close to very end at this line:
Code:
Installing recovery patch to system partition
Warning: could not find RECOVERY/RAMDISK/etc/recovery.fstab
Warning: could not find SYSTEM/build.prop in <built-in function zip>
using prebuilt recovery.img from BOOTABLE_IMAGES...
using prebuilt boot.img from BOOTABLE_IMAGES...
cp: cannot stat ‘$OUT/target/product/aio_otfp/ota_temp/SYSTEM/bin/install-recovery.sh’: No such file or directory
build/core/Makefile:1074: recipe for target '$OUT/target/product/aio_otfp/system/bin/install-recovery.sh' failed
make: *** [$OUT/target/product/aio_otfp/system/bin/install-recovery.sh] Error 1
build/core/Makefile contains the lines
Code:
$(hide) cp $(ota_temp_root)/SYSTEM/bin/install-recovery.sh $(TARGET_OUT)/bin/install-recovery.sh
$(hide) cp $(ota_temp_root)/SYSTEM/recovery-from-boot.p $(TARGET_OUT)/recovery-from-boot.p
however the file install-recovery.sh is missing. In fact the whole $(ota_temp_root)/SYSTEM/bin/ directory is empty.
Has anyone encountered this error before, or have thoughts on a solution?
Problem 2)
If I remove the line entirely from the makefile (i.e. skip install-recovery.sh) the build completes successfully. The $OUT directory contains the files recovery.img, boot.img, system.img, userdata.img, and so forth. I can flash the recovery.img to my recovery partition, and all is well booting into it. However, there is no .zip file for flashing the system as a whole.
I have tried various combinations of make otapackage, make bacon, etc., but none of these seem to work (possibly they were features in previous versions of CM). Is there a different target I should use, or a flag that I need to change in the device tree?
Many thanks for everyone's help!
Related
Hello there,
I am trying to build a custom ROM for Samsung P3113 based on AOKP source on the jb branch. I was able to make "unofficial" release using "brunch aokp_p3113". However, when I attempted to make a distribution release, the "make -j4 dist" failed. The following are the commands I used:
. build/envsetup.sh
lunch aokp_p3113-userdebug
make -j4 dist
I got the following error messages:
device/moto/stingray/recovery/recovery_ui.cpp:22:20: fatal error: device.h: No such file or directory compilation terminated.
make: *** [out/target/product/p3113/obj/STATIC_LIBRARIES/librecovery_ui_stingray_intermediates/recovery_ui.o] Error 1
Can someone help? By the way, I don't need to build OTA package.
Found root cause
Found the root cause -
All the three header files needed by recovery_ui.cpp are missing. To workaround, I excluded the stingray recovery from the make, and the problem solved.
Hopefully, someone in the AOKP team will add the missing files to repository.
Hello.
I've got a Lenovo S6000 which I've extracted the boot.img from and used mkvendor.sh to generate the device tree.
The problem is such that because of the ridiculous amount of space left for the recovery and boot image, I can't compile a recovery image using:
Code:
$ make recoveryimage -j8
I've tried appending 'CFLAGS=-Os' (optimising for size) after running make clobber, but to no avail.
The exact output of the make command is as follows:
Code:
/home/george/CyanogenMod/out/target/product/s6000/boot.img maxsize=3514368 blocksize=135168 total=5062656 reserve=270336
error: /home/george/CyanogenMod/out/target/product/s6000/boot.img too large (5062656 > [3784704 - 270336])
build/core/Makefile:562: recipe for target '/home/george/CyanogenMod/out/target/product/s6000/boot.img' failed
make: *** [/home/george/CyanogenMod/out/target/product/s6000/boot.img] Error 1
make: *** Deleting file '/home/george/CyanogenMod/out/target/product/s6000/boot.img'
make: *** Waiting for unfinished jobs....
Is there an alternative recovery which is smaller than CWM which I could use? Or a work around?
Before you ask, yes, I am using a prebuilt kernel extracted from the device - I understand that that partly to blame. The source code is available but doesn't compile well (missing headers, syntax errors and annoying inline function errors to name a few).
I'm trying to build a stand alone Android kernel and i want to write loadable kernel module, but when i build my module.c file, i have this error
Code:
error: smd_private.h: No such file or directory
search at google told me that i should change
Code:
<smd_private.h>
into
Code:
"smd_private.h"
in arch/arm/mach-msm/smd_init_dt.c file . but i dont have this file in my kernel folder !!!, so i download this file,but the error still exist!! Can you help me?
[Q]
any help?
Hi! I'm trying to build the CypherOS ROM based on Android 6.0 for my Xiaomi Redmi Note 3, using CyanogenMod sources. The build seemed to be running just fine until it stopped at this bit near the end:
Code:
putting script in etc/install-recovery.sh
cp: cannot stat '/home/nsood/cypher/out/target/product/kenzo/ota_temp/SYSTEM/bin/install-recovery.sh': No such file or directory
build/core/Makefile:1077: recipe for target '/home/nsood/cypher/out/target/product/kenzo/system/bin/install-recovery.sh' failed
make: *** [/home/nsood/cypher/out/target/product/kenzo/system/bin/install-recovery.sh] Error 1
make: Leaving directory '/home/nsood/cypher'
It seems to be copying some install-recovery.sh from a temporary folder to the permanent one, but fails because there's no install-recovery.sh in system/bin there.
Some digging showed it is present in system/etc though:
Code:
$ find | grep install-recovery.sh
./out/target/product/kenzo/ota_temp/SYSTEM/etc/install-recovery.sh
Where is this file supposed to be? How do I point it to the right location? Anything I can do to fix this?
This is an error in your fstab.
Check you BoardConfig for the definition of TARGET_RECOVERY_FSTAB.
This defined file is the file that makes brunch bail out.
Unfortunately I do not know exactly what causes it, so you need to play around.
P.S.: The error in fstab is probably that either the mount for /boot or for /recovery is missing.
Hi @NSDCars5
How did you solve this...
I'm getting the same error when'm building for UMI Z
First time I'm building Android ,and building for a new device
If I copy install-recovery.sh from etc/ to bin/ the build continues... but there has to be a reason for it to end up in etc?
Go into build/core/make file.mk and somewhere near line 1057 you'll see a
(hide)(ota)"something blahblahblah" install-recovery.sh
Comment it out with a #
Hi guys i'm having a problem with Kitchen 0.224 on opening a system.img of Android MM 6.0.1.
when i start the process of creating a working folder and when the process is done i get the following message:
Compiling simg2img ...
In file included from sparse_crc32.c:46:0:
ext4_utils.h:29:23: fatal error: sys/types.h: No such file or directory
compilation terminated.
gcc: error: sparse_crc32.o: No such file or directory
rm: cannot remove '*.o': No such file or directory
Error: simg2img not successfully compiled!
to be specific i'm running kitchen on linux mint 18.2,followed all the steps to get kitchen working.
Phone Asus ZenFone 2 Z00L MarshMallow.img ROM .
any idea on what is wrong ?? how do i get to work and modify that ROM?
any lil help is appreciated
oh and before someone wonder and even ask yes i am a beginner on those stuff