I've managed to build Froyo with the CM vendor tree for vision(ie: Desire Z/G2).
The build worked (ive used the same tree to build for a wildfire and desire as well with no issues) - pulled a couple of files (librpc.so and the libcamera libs) from the desire out/ directory.
I'm using dsixda's kitchen to cook then roms, when i push the rom to the phone and attempt to flash it, it fails with "assert failed: write_raw_image("/tmp/boot.img", "boot")" (Status 7)
i am able to flash CM6.1.1.1 and CM7.0.3 with no worries - if i use the boot.img from CM6.1.1 the rom will flash, but then goes a bit special once the rom boots.
I assumed the cm 6.1.1 rom would have the same boot.img as my built CM 6.1.1 vendor + android 2.2.1 - but i'm gravely mistaken
obviously my issue is building the boot.img from the source tree - can anyone give me some hints as to where i should look?
issue resolved - was a kitchen problem
changing the offending lines in updater-script to:
Code:
package_extract_file("boot.img", "/dev/block/mmcblk0p22");
seems to have fixed the issue.
Related
Been using st0kes' thread (http://forum.xda-developers.com/showthread.php?t=709105) and have checked out the AOSP tree, and build a ROM from it that boots on my phone, however....
How do I get the build to stop including things like the recovery image (rather than deleing the folder from the final zip)?
How do I get the build to include additional repo's, such as superuser?
I attempted to follow the guide myself, but when it comes to the command :
source build/envsetup.sh
I just get a "Bash: file not found"
But i don't know anything about the recovery...have you tried the cyanogen wiki?
Josh.
sounds like you're not in the correct folder..
Anyway, in answer to my original question... I found some useful posts on http://howto.ccroms.net/:
http://howto.ccroms.net/android_project/build/mod/recovery
http://howto.ccroms.net/android_project/build/mod/busybox
and
http://howto.ccroms.net/android_project/build/mod/root
I've got Superuser.apk / bash / busybox included, and my compile box is running with the changes from the /recovery howto now (Thank God for 24 core boxes, it compiles a full otapackage in ~10-15 minutes!)
Android 4.1.2 Compiled from Source of Quarx repo
+ Linaro as mentioned on quarx github
1.If you new with custom roms look here :
http://forum.xda-developers.com/showthread.php?t=1216982
In German :
http://www.android-hilfe.de/custom-...-wechselt-bzw-updatet-man-ein-custom-rom.html
info for quarx JB 2ndboot build for defy here
http://forum.xda-developers.com/wiki/Motorola_Defy/JB_status
Spezial thanks to Quarx2k,Walter79,Kayant,Skeevey433,Moqua......
Who made many things possible on Defy
Requirements :
Rooted Defy , all models, installed
ClockworkMod Recovery
Install :
Flash zip through recovery like every nightly
Reboot
Notes:
Rom reboot maybe once after installation
Enable usb-debugging for a short time if akku is allways 100%
Google apps can be found here :
http://goo.im/gapps/
For better battery and prevent ringtone bug replace zram.img and ramdisc.img in system/bootmenue/2nd-boot
with files contained in download Folder , using root explorer or flash the kernel-b773d4b651-without-666db01d50+ ramdisk_from18_11_2012 .zip in custom recovery after installing the rom.
(Should work on all newer CM10 2nd-boot roms)
Remember , all you do is on your risk
Files can be found here:
http://db.tt/zliqMTdy
MB525 red lense
Why waste your time having to update this when anyone can compile it through my guide or just use quarx's builds
There is no point posting this expect if you are adding some things or features like linaro which wskelly has done.... Or maybe you like doing extra work for no reason .
ok , i need a guide for linaro
companions
i appreciate the tips
happy new year
grateful
Yesterday I donwloaded CF_FIRE kernel (http://forum.xda-developers.com/showthread.php?t=2263720) for my WFS 2012. After compilation with default config using arm-eabi-4.4.3 and packing into boot.img using abootimg tool kernel doesn't boot. Inmediately after booting it from fastboot phone restarts. Phone is S-OFF. Image unpacking and re-packing works well, I made some modifications to ramdisk, also precompiled kernels are working. WTF?
SOLVED
Problem solved, i made mistake in kernel base address in config file.
Hi all,
I have downloaded the sources for cm 12.1, I have already build many ROMs for htc m7, m8 and some others. Cyanogen have not released the source for htc m9 yet, however you and find a github repo with all the neccesary parts for building you himaul ROM over a CM_12.1 source. It is called Hima-Dev
I have cloned all necessary parts for building it and I have placed them into the right place. Bellow I attach a listh of what I downloaded.
The kernel
Then the common vendor propietary folder
And finally the device specific folder along with its common folder for device.
Before building I run the ./extract-files script in order to get all propietary libraries, apps and files. Then I start a building for "himaul" and everythhing works very ok. (breakfast himaul && brunch himaul)
The problem comes after install the new ROM. It raises many exceptions during boot screen. Bellow I attach some of the log messages I get.
Code:
java.lang.UnsatisfiedLinkError: dlopen failed: cannot locate symbol "__htclog_init_mask" referenced by "libtime_genoff.so"...
java.lang.NullPointerException: Attempt to invoke interface method 'void android.app.IActivityManager.handleApplicationCrash(android.os.IBinder, android.app.ApplicationErrorReport$CrashInfo)' on a null object reference
My question is. Should I wait for cyanogen in order to get a stable source or is there any workout for solving this? :good:
I don't know what's the issue with my setup or kernel tree (Alberto97's git) that I'm getting these errors all the time when I try to compile any rom
1) rmnetctl library conflict. There's always this error in all roms and states that "shared libraries is already defined" in rmnetctl folder in device tree hence stopping the build at the begenning. I got past the issue by deleting the rmnetctl folder in device tree but is it the right way to do it?
2) Sepolicy error. Even after I delete above folder, the build stopped after it reaches about 34%, I don't know what it's called but I'm getting this error every time I try to compile any rom. This time while building aosp extended https://hastebin.com/yomepicili.sql
I'm a noob so pardon any lack of knowledge. I am trying to learn to compile here. Also, I'm using oreo-mr1 branch device tree and kernel and oreo-mr1-addison branch for vendor.