[Q] ICS on a similar phone - Hero CDMA Q&A, Help & Troubleshooting

Please forgive me for posting on your forum but I gave googled my problem with no success and the developers for ICS on the Hero have made progress with compiling ICS so I thought I'd ask my question here.
I have successfully compiled ICS 4.0.3 for the ARMv6 using the TeamICS patches here:
hxxps://github.com/TeamICS/ICS_Fixes
(sorry....can't post outside links yet!)
And other relevant pataches like:
hxxp://r.cyanogenmod.com/#change,10532
My phone is the Samsung Intercept with the S3C6410 processor similar to the processor in the Hero. The Intercept ROMs don't use .img files to flash the /system partition so I compiled ICS with: make -j4 otapackage to get a zip.
My dev box is Ubuntu 10.04 LTS and everything is installed EXACTLY like the AOSP website says it should be here:
hxxp://source.android.com/source/initializing.html
I flash the zip using CM recovery and boot and this error is killing me:
Warning PackageParser Exception reading AndroidManifest.xml in /system/framework/framework-res.apk
Warning PackageParser java.lang.SecurityException: /system/framework/framework-res.apk failed verification of META-INF/CERT.SF
Warning PackageParser Exception reading AndroidManifest.xml in /system/app/PicoTts.apk
Warning PackageParser java.lang.SecurityException: /system/app/PicoTts.apk failed verification of META-INF/CERT.SF
No apk will load because they fail verification. The list of failed APK's is long in logcat. I even went into the Java source code to hack out the verification code with no success. If any Devs have seen this or know why this is happening I would be grateful for a hint. Thanks.
UPDATE: I flashed the Hero ICS zip to my phone(with a few modifications to prevent a phone brick!) to see if the problem was with my compile or something else and I got the same errors. This must mean that there is something about the way Android checks APK signatures that I don't understand.
More information:
If I run jarsigner -verify -certs framework-res.apk I get "jar verified".
I have a theory about certs being bad at runtime:
In logcat there are entries saying that bouncycastle classes can't be preloaded and I'm guessing that bouncycastle has something to do with cryptographic keys so maybe PackageParser can't use the crypto classes and bombs.

jaybob413 would definitely be the guy to ask, or even mattcrystal. see if they have time to pm back and forth, and even post this in a dev/wip/rom thread in the intercept forums. exciting what these old phones can do, and i hope you go far with your port.

whoshotjr2006 said:
jaybob413 would definitely be the guy to ask, or even mattcrystal. see if they have time to pm back and forth, and even post this in a dev/wip/rom thread in the intercept forums. exciting what these old phones can do, and i hope you go far with your port.
Click to expand...
Click to collapse
Thanks for the tip...I have sent a message on github to mattcrystal so maybe he will respond if he has time.

bads3ctor said:
Please forgive me for posting on your forum but I gave googled my problem with no success and the developers for ICS on the Hero have made progress with compiling ICS so I thought I'd ask my question here.
I have successfully compiled ICS 4.0.3 for the ARMv6 using the TeamICS patches here:
hxxps://github.com/TeamICS/ICS_Fixes
(sorry....can't post outside links yet!)
And other relevant pataches like:
hxxp://r.cyanogenmod.com/#change,10532
My phone is the Samsung Intercept with the S3C6410 processor similar to the processor in the Hero. The Intercept ROMs don't use .img files to flash the /system partition so I compiled ICS with: make -j4 otapackage to get a zip.
My dev box is Ubuntu 10.04 LTS and everything is installed EXACTLY like the AOSP website says it should be here:
hxxp://source.android.com/source/initializing.html
I flash the zip using CM recovery and boot and this error is killing me:
Warning PackageParser Exception reading AndroidManifest.xml in /system/framework/framework-res.apk
Warning PackageParser java.lang.SecurityException: /system/framework/framework-res.apk failed verification of META-INF/CERT.SF
Warning PackageParser Exception reading AndroidManifest.xml in /system/app/PicoTts.apk
Warning PackageParser java.lang.SecurityException: /system/app/PicoTts.apk failed verification of META-INF/CERT.SF
No apk will load because they fail verification. The list of failed APK's is long in logcat. I even went into the Java source code to hack out the verification code with no success. If any Devs have seen this or know why this is happening I would be grateful for a hint. Thanks.
UPDATE: I flashed the Hero ICS zip to my phone(with a few modifications to prevent a phone brick!) to see if the problem was with my compile or something else and I got the same errors. This must mean that there is something about the way Android checks APK signatures that I don't understand.
More information:
If I run jarsigner -verify -certs framework-res.apk I get "jar verified".
I have a theory about certs being bad at runtime:
In logcat there are entries saying that bouncycastle classes can't be preloaded and I'm guessing that bouncycastle has something to do with cryptographic keys so maybe PackageParser can't use the crypto classes and bombs.
Click to expand...
Click to collapse
Sorry sir. I personally do not have enough time to look at your problem. I'm pretty busy with Zero Hero at the moment and ICS development is always on going.
When compiling from source the very last thing the complier does is run Google's signapk before finishing the zip. One reason I never got it to work was I was running 32 bit Ubuntu. Jaybob noticed I needed to be running 64 bit to properly compile and after that I'm able to flash my own builds from source. My guess is this is where you might be failing. ICS is a much bigger than gingerbread and tons of changes that are hard to overcome.
Sent from my HTC Zero Hero Sense 3.5

MattCrystal said:
Sorry sir. I personally do not have enough time to look at your problem. I'm pretty busy with Zero Hero at the moment and ICS development is always on going.
When compiling from source the very last thing the complier does is run Google's signapk before finishing the zip. One reason I never got it to work was I was running 32 bit Ubuntu. Jaybob noticed I needed to be running 64 bit to properly compile and after that I'm able to flash my own builds from source. My guess is this is where you might be failing. ICS is a much bigger than gingerbread and tons of changes that are hard to overcome.
Sent from my HTC Zero Hero Sense 3.5
Click to expand...
Click to collapse
Thanks for posting. ICS on the Samsung Intercept is up and running.

Do me a favor and click thanks perhaps and your welcome
Sent from my HTX Zero Hero Sense 3.5

no wip/dev thread on the intercept forums yet? that would be awesome, i a know a few with intercepts that would love to see ics on their phones. op you should think about making it happen, at least posting a guide/howto.

Related

[Q] A few AOSP compile questions

I am trying to compile a clean AOSP ROM for my O2X, there is a few things I am having trouble with.
1. What is the significance of overriding the build prop with the following:
Code:
PRODUCT_BUILD_PROP_OVERRIDES += PRODUCT_NAME=lge_star BUILD_ID=FRG83G BUILD_DISPLAY_ID=GRJ22 BUILD_FINGERPRINT=lge/lge_star/p990/p990:2.2.2/FRG83G/lgp990-V10b.2ED2ADCFFC:user/release-keys PRIVATE_BUILD_DESC="star-user 2.2.2 FRG83G 2ED2ADCFFC release-keys"
Clearly its used for something, else CM7 wouldn't be doing it.
2. When I try to boot the compiled system (using either CM or EternityProject kernel), it simply stops at the LG logo, no logcat, no dmsg, nothing and after a while it reboots. What could I be missing?
I am using the init.rc from the CM7 p990 source, do I need some extra modules for it to boot? (I have added busybox and bash)
Tips on how I could debug the issue would be appreciated (any additional logs?).
I've managed to get froyo building and running from source (I used the nvidia branch and merged 2.2.2 myself)
I just used the stock LG kernel though
Got almost everything but gave up because it was a huge pain in the ass
You dont really need those
Are you trying to create the device tree yourself?
fallout0 said:
I've managed to get froyo building and running from source (I used the nvidia branch and merged 2.2.2 myself)
I just used the stock LG kernel though
Got almost everything but gave up because it was a huge pain in the ass
You dont really need those
Are you trying to create the device tree yourself?
Click to expand...
Click to collapse
Yea I am trying to create a device tree that will make AOSP compile and run. Its compiling just fine and it uses bits from the CyanogenMod device tree. The problem is that it wont run, it gives me no logcat output at all.
Here is the p990.mk:
http://pastebin.com/SxUZZDau
The boardconfig and proprietaries are identical to CM7. (Merged star-common and p990 configs since I have no use for p999)
Try using the stock kernel + init.rc - that is just use the boot image from modaco for now
You should be able to adb shell into it and check dmesg to see what's going on
fallout0 said:
Try using the stock kernel + init.rc - that is just use the boot image from modaco for now
You should be able to adb shell into it and check dmesg to see what's going on
Click to expand...
Click to collapse
Same problem, no dmsg or logcat.
Im gonna start from scratch now
About your first question (and sb correct me if I'm wrong), its just for market stuff to show up on the device, whilst making About>System display GRJ22 etc. etc.
L10nH34Rt said:
About your first question (and sb correct me if I'm wrong), its just for market stuff to show up on the device, whilst making About>System display GRJ22 etc. etc.
Click to expand...
Click to collapse
That would make it rather useless
KernelCrap said:
Same problem, no dmsg or logcat.
Im gonna start from scratch now
Click to expand...
Click to collapse
Also you HAVE to check out the code from nvidia because the tegra2 has a bug in the CPU and their code base has a work around for it if you don't the dynamic linker doesn't work and you'll find every executable will segfault ( when you flash your system image from recovery try and go into system/bin and run. /ls for example)
In the board configuration you'll notice a HAVE_TRGRA something or rather line
check out bionic that's where that fix is applied
fallout0 said:
Also you HAVE to check out the code from nvidia because the tegra2 has a bug in the CPU and their code base has a work around for it if you don't the dynamic linker doesn't work and you'll find every executable will segfault ( when you flash your system image from recovery try and go into system/bin and run. /ls for example)
In the board configuration you'll notice a HAVE_TRGRA something or rather line
check out bionic that's where that fix is applied
Click to expand...
Click to collapse
Im gonna try to build using the 2.3.3 gingerbread-tegra source from nvidia
EDIT: Same problem, when running something i get "Segmentation fault". I am using the gingerbread-tegra source from nvidia :S
I have the following in BoardConfig.mk:
TARGET_HAVE_TEGRA_ERRATA_657451 := true
Busybox is working fine though :/
Shouldn't the source from nvidia allow me to execute the compiled binaries without giving segmentation fault?
The funny thing is that busybox is working, and I can access dmesg through busybox.
KernelCrap said:
That would make it rather useless
Click to expand...
Click to collapse
It wouldn't if you couldn't access the market now would it?
L10nH34Rt said:
It wouldn't if you couldn't access the market now would it?
Click to expand...
Click to collapse
I'd rather have it boot atm.
Still same problem even though I have moved to the gingerbread-tegra source
IMHO its a wasted effort. You'll have trouble getting camera/hdmi etc.etc to work... Just clone CM repo and cherry-pick from there.
L10nH34Rt said:
IMHO its a wasted effort. You'll have trouble getting camera/hdmi etc.etc to work... Just clone CM repo and cherry-pick from there.
Click to expand...
Click to collapse
For starters I don't care about camera or hdmi, I want a clean AOSP rom - CM is great, but it includes too many extra features for my taste.
Are you sure you checked out the tegra branch from nvidia? gingerbread-tegra?
I could only get froyo to boot myself - gingerbread would crash inside surfaceflinger with the froyo graphics libraries. I think the cygonenmod guys had access to leaked gingerbread libraries.
Hi guys, where i can find sources from nvidia ? I only found the kernel git...
Thank's
fallout0 said:
Are you sure you checked out the tegra branch from nvidia? gingerbread-tegra?
I could only get froyo to boot myself - gingerbread would crash inside surfaceflinger with the froyo graphics libraries. I think the cygonenmod guys had access to leaked gingerbread libraries.
Click to expand...
Click to collapse
I am sure and I am using the leaked libraries too. Anything else i can try?
Sent from my Optimus 2X using XDA App
If all the executables are seg faulting then you won't even get to logcat and the shell won't run unfortunately.
Try this...
find all the blocks of code in the source that have the #ifdef HAVE_TEGRA..ERRATA
and remove them
That way you'll definitely know that its compiling that section of the code. That has to work
fallout0 said:
If all the executables are seg faulting then you won't even get to logcat and the shell won't run unfortunately.
Try this...
find all the blocks of code in the source that have the #ifdef HAVE_TEGRA..ERRATA
and remove them
That way you'll definitely know that its compiling that section of the code. That has to work
Click to expand...
Click to collapse
Will try that once I get home later today
I commented it out the following places:
Code:
./bionic/libc/Android.mk:497: ifeq ($(TARGET_HAVE_TEGRA_ERRATA_657451),true)
./bionic/linker/Android.mk:46:ifeq ($(TARGET_HAVE_TEGRA_ERRATA_657451),true)
Still not booting, now the error is (from logcat):
Code:
exec '/system/bin/sh' failed: No such file or directory (2)
But /system/bin/sh does exists, with the following permissions (also tried with chmod 777):
Code:
-rwxr-xr-x 1 root shell 82840 sh
If I do adb shell when in recovery and executes the binary files, they all seg fault (except for busybox) :/
Here is my BoardConfig.mk:
http://pastebin.com/ZsmJp0v1

Linux ON droid not IN android question????

Ok, this goes out to any and all DEVs out there. We all know by now that we (some people not me) can run linux within android using the loop mounts, vnc viewer, etc... Now how about REPLACING android with a linux distro like debian or maybe even what these guys use http://openpandora.org/ ..... its linux based and has an arm CPU.. Any way I'm talking about flashing over android wiping the internal sorage and installing linux on it or even using the boot loader to flash over android???, of course this is getting rid of any 3g connection and phone usage. I understand that, I am talking about giving our RETIRED droid 1s a use. I wanna see my D1 run a linux distro in full hardware mode NO MORE ANDROID. now dont get me wrong I love android as much as the next guy, but why now flash something else to it???
Another link I found, this is for windows mobile but hey, similar idea.
http://wing-linux.sourceforge.net/trac/wiki/FAQ
P.S. I AM NOT A DEV JUST AN IDIOT WITH AN IDEA!! my ignorance is NOT bliss and I would love to know if this is even possible. I'm willing to help ANY WAY I CAN. lol
THANKS!!!
I don't think it's possible. Because of the locked bootloader we're forced to use Motorola's bug-ridden Kernel and as Android's Kernel is a heavily modified Linux Kernel it most likely won't run an ordinary Linux distro.
But I'm no expert either
Milestone is locked, Droid is not ...
Maybe this will help (if you don't know german, you can use Google Translate):
http://www.android-hilfe.de/anleitu...debian-chroot-mit-lxde-auf-dem-milestone.html
Thanks for the replies. Again the USA Droid 1 is nit locked or at least has been completely unlokcked. I've read a million "run debian on android" posts... I don't need to know German to see that the post above is the same thing. Like I said before I have NO INTEREST IN RUNNING LINUX ON ANDROID. I want TO REPLACE android completely with Linux to make a device like the openpandora handheld from my first link.
Any one up to the challenge????
Thanks again!
Really, no one??
I've been running Debian on my Droid booting from the SD card for a while, more recently trying Arch Linux after realizing that anything optimized for ARMv7, VFPv3, NEON, or Thumb-2 (I'm not sure which unfortunately) won't boot because of a page fault or something. Ubuntu, MeeGo, and Angstrom just kernel panic and don't give any useful information even at the highest debugging level. I'm back to using an ARMv5te Arch Linux build (http://archlinuxarm.org) although I could just as well use Debian. I really wish Ubuntu worked for multitouch.
Well, I got the touchscreen calibrated! I forgot that my screen rotation hack only rotated the framebuffer It's stuck in portrait for now. I decided to use mtev (MeeGo's multitouch X11 input driver) after being fed up with evdev's aversion to being rotated, but now that I'm back to the stock portrait rotation evdev should work fine.
If you want instructions, either PM me or wait until I post a full guide and/or my patched kernel tree. It's not super difficult, but it's a lot of command line use and compiling.
What works:
*CPU and SD card (obviously )
*Touchscreen (single touch/portrait only for now)
What needs work:
*Keyboard mapping is wrong, the number keys and symbols don't work. I need to figure out how Android handles Alt. I had to patch the GPIO keyboard driver because the keyboard worked in the console but not in X11, which expects EV_SYN.
*Sound is OSS only, but there is no mixer device, so aumix is useless and there's no volume control or sound output.
*I haven't tried the SGX driver, so I can't comment on hardware acceleration yet.
*Battery charging relies on battd, which is a proprietary Android binary from Motorola. It might run on Debian with "ls -s / /system" and the creation of the socket it expects (init.sholes.rc I believe), but I'm not getting my hopes up.
Untested:
*WiFi (needs firmware, but should work)
*Bluetooth
*Calls/data
*Sensors (although the accelerometer and compass seem to be recognized by evdev)
I'll upload my kernel, either as patches or on GitHub (or binaries if there's enough demand) once I get around to fixing the keyboard issue. Fingers crossed that I don't get carried away cleaning up the kernel, or worse yet, give up...
This is incredible news! I'm so glad to hear it. Of course you are running in hardware mode? Not through android? If so I'm super exited about this! I love arch Linux, I run it on all my computers and I understand it more than any other distro I've tried. I would love to give it a shot, though I'm not that great at compiling I think it will be worth it.
As I said before I am in no way a dev or even a Linux pro, but I can get by and if theres any way I can help this project become "complete" I'm willing to learn what ever is necessary to do so.
Also were u able to get an x server running? Possibly a DE? That would be crazy awesome.
Thanks a million, looking foreword to work with you and make this happen!
For anyone who's interested, I put together a quick package containing my kernel patches, configuration notes, and an automated kernel build script.
It's pretty self-explanatory aside from the installation of the root filesystem, which I leave up to your imagination
As I've probably repeated several times now, I've run Debian and Arch Linux natively on my Droid with my patched kernel (no chroot or VNC "hack"). With enough determination, it's possible to run practically anything on it - personally, I'm determined to get Ubuntu on it.
WOOT... insta-fail for me LOL you have it set up to work in specific directories? I thought i placed everything right but I guess not.. I got an error on the first line of output lol
Welcome to gTan64\'s lazy Droid kernel compiler\!
build.sh: line 5: [: missing `]'
build.sh: line 5: -z: command not found
build.sh: line 5: -z: command not found
Entering $WORK
Applying patches
build.sh: line 16: /*.patch: No such file or directory
mv: cannot stat `/arch/arm/boot/compressed': No such file or directory
cp: cannot stat `/compressed': No such file or directory
Setting up build
cp: cannot stat `/GNUmakefile': No such file or directory
cp: cannot stat `/sholes_config': No such file or directory
FIXME! No numeral or symbol input until someone finds a third-level
modifier key to use instead of AltGr for the keyboard.
cp $MISC/defkeymap.map $K_SRC/drivers/char
Building kernel!
make: *** No targets specified and no makefile found. Stop.
Kernel build done!
You have done something amazing, I'm just to stupid to figure it out my self. XD
I can understand why you would want ubuntu with all its pre-setup glory and support for nearly all hardware but dont you think its a little heavy for this hardware? lol I doubt you would try to use the Unity UI but I doubt that alone would even fit in ram LOL you could just use the ubuntu packages and drivers with debian maybe?
THANKS AGAIN!!!!
That's what happens when I don't test my own scripts
I was thinking too much about making it easy. Just try applying my patches to your tree manually.
Code:
cd kernel_src
patch -p1 <../patches/first.diff
patch -p1 <../patches/next.diff #and so on...
#Obviously, substitute the paths of the actual patches ;)
#Finally, copy sholes_config to .config and invoke 'make'.
It's actually much simpler than my script makes it, and you don't need my convoluted folder setup.
UM lol I cant find any patch files? are they in the ZIP? or do I have to obtain them elsewhere?
I can tell this is gonna be a hell of a project LOL
THANKS!!!
"Duh" moment - I used the .diff file extension instead of .patch
I'm such a scatterbrain... Remind me not to release anything before testing
EDIT: Strike that, reverse it. They're .patch files.
I AM BLIND lol I found them... BUT.. when I try to patch. terminal just seems to lock up... I press enter, the curser moves to the next line but it doesnt do anything. lol how long should 1 patch take?? its been about 10 minutes and I leave it be for now
EDIT:
LOL i forgot the "<" in the command OOPS but I'm not seeing any .config file or folder in the source to copy the sholes_config too. yes I have show hidden files on.. PS unfortatly usinf Fedora 15 gnome 2...... (on server so I can work on this anywhere through vnc )
THANKS
When I said "copy sholes_config to .config", that's literally what I meant. .config is the Linux kernel build configuration file, not a folder.
'cp /path/to/sholes_config .config' from your kernel tree should do it.
Oh, I forgot to mention that you need an ARM cross-compiler/toolchain. I use the gcc-arm-linux-gnueabi package in Ubuntu, but I don't know what the Arch equivalent is off the top of my head.
The "GNUmakefile" is just a convenience, it exports "ARCH=arm CROSS_COMPILE=arm-linux-gnueabi-" before calling the actual makefile. If you don't have an ARM cross compiler in your path, it won't build at all. If you do, modify CROSS_COMPILE to point to it - on some systems it's called arm-unknown-linux-gnueabi, etc. etc.
Let me know if you get anywhere before it errors out.
OK I put the config file in the kernel_src but unfortainatly I'm using Fedora 15 XP I installed arm-gp2x-linux-gcc which is the fedora arm gcc I guess... lol so wha would I edit in the .config to make it point to arm-gp2x-linux-gcc. Its not my first attempt to compile an android kernel but I've never been succesfull LOLOL
thanks
I'm pretty sure that toolchain won't work - the GP2X was ARMv5 IIRC, so unless it's a newer build of GCC (4.3 or higher) and you're absolutely sure it supports the ARM EABI and the ability to generate ARMv7 instructions (which is unlikely if it's pre-4.1), I would recommend a newer toolchain.
CodeSourcery makes a pretty solid one: https://sourcery.mentor.com/sgpp/lite/arm/portal/release1803
If you end up using it, you can change the second line in GNUmakefile to "CROSS_COMPILE=arm-none-linux-gnueabi-". Don't worry about changing .config.
Well I DLed the linux/GNU installer and it gave me "arm-2011.03-41-arm-none-linux-gnueabi.bin" LOL
so I was thinking would it just be easier to just use my lappy with crunchbang (debian based) so I can follow ur instructions with deb / apt-get LOL fedora is a ***** and it dont have what I need... I cant find an arm v7 cross compiler for it
thanks
.bin files are the Linux equivalent of Windows EXE installers. Run it like this:
Code:
#cd /path/to/installer.bin
./installer.bin
#substitute the actual name, of course.
It needs root permissions if you want to install it to /usr/local (sudo ./installer.bin or su -c 'sh installer.bin'). You can also install it to /usr, but that will make it more tedious to uninstall later. If you decide to install it in your home folder - say ~/toolchain - you don't need root permissions, but you will need to add ~/toolchain/bin to your path:
Code:
export PATH=$PATH:$HOME/toolchain/bin
To be honest, I prefer Ubuntu to Fedora/OpenSUSE/$RPM_distro, so if you have access to a Debian or Ubuntu system, using that would make my life easier
Omg duh... the "non_Linux" part of the name true me off lol i'll start doing this on my laptop it's deb based crunchbang. I prefer anything over rpm distros too but it was a quick painless install on my server XP thanks ill try this when I get home
Sent from my DROIDX using XDA App

[Q] nOOb: export apk from Eclipse IDE?

So, I've been doing some Android development tutorials, as I have almost no experience in any sort of coding. I'm working in Ubuntu 11.10 with android-sdk-linux, Eclipse IDE, & java version 1.6
Things are going ok, but...
I tried to export a signed apk of my application project from Eclipse yesterday, and when I try to install it on my D3 I get this error:
HTML:
Error Parsing Package
What am I doing wrong?
thanks in advance...
lunacie said:
So, I've been doing some Android development tutorials, as I have almost no experience in any sort of coding. I'm working in Ubuntu 11.10 with android-sdk-linux, Eclipse IDE, & java version 1.6
Things are going ok, but...
I tried to export a signed apk of my application project from Eclipse yesterday, and when I try to install it on my D3 I get this error:
HTML:
Error Parsing Package
What am I doing wrong?
thanks in advance...
Click to expand...
Click to collapse
Sorry bro, I have no idea. You might get more help Android Development and Hacking or more specifically Android Software Development which is a subforum of the first link. Sorry I personally can't help you out more than that, wish I could.
If your device is recognized as a development device, you should be able to just hit the 'Run' button and it should compile your app, install it to the device and automatically launch it. Your device needs to have USB debugging turned on and you need to have the ADB driver installed (need to get it from Motorola if this is a Moto device, it won't install automatically like the rest of the storage drivers).
My Droid3 shows up as ???????? in adb. I was exporting a signed apk to install because I can't get the device to recognize. Am I missing a configuration of some kind? I'm guessing there's some kind of vendor code or something that I need for ADB to work properly with my phone?
tnx
EDIT: think I figured it out. it's the udev rules, looks like i'm on the right track....
EDIT 2: Got it! Thanks for the heads up.

Need Help Recompiling Kernel

Howdy Folks,
I've been working on porting some ROMS to our device from the Sensation forum and I'm getting closer. I am currently using cygwin in Windows 7 64-bit so that I am able to use dxdia's kitchen. I have been able to successfully decompile both boot.img from the Base (U.S. Stock Vivid) and Port (Elegancia Pegasus) but when I need to recompile, I get the error "Compiling mkbootfs ... Error: mkbootfs not successfully compiled!"
I don't know how to proceed at this point in time. After I get the boot.img working, I'll need to start working on the AROMA script so you might not hear from me for a few weeks (due to work and school). I've been following the guide from http://forum.xda-developers.com/showthread.php?t=2245786. If anyone has experience with using dxdia's kitchen or has a different tool that I can use in Windows, that would be great. I want to keep the development for this phone going until a pick up the Nexus 5 (whenever that may be).
-Apatche

[Q] Help building CM for Nook HD+

I've been running CM on my HD+ for the last few months and it's been great. I'm working on making some modifications to the VM and to the kernel and it requires building CM from source. I've already done this with several other devices and have had only minor problems. I'm following the instructions and it can't build. I get the following error:
Code:
============================================
PLATFORM_VERSION_CODENAME=REL
PLATFORM_VERSION=4.3.1
CM_VERSION=10.2-20140120-UNOFFICIAL-ovation
TARGET_PRODUCT=cm_ovation
TARGET_BUILD_VARIANT=userdebug
TARGET_BUILD_TYPE=release
TARGET_BUILD_APPS=
TARGET_ARCH=arm
TARGET_ARCH_VARIANT=armv7-a-neon
TARGET_CPU_VARIANT=cortex-a9
HOST_ARCH=x86
HOST_OS=linux
HOST_OS_EXTRA=Linux-3.7.10-1.16-desktop-x86_64-with-SuSE-12.3-x86_64
HOST_BUILD_TYPE=release
BUILD_ID=JLS36I
OUT_DIR=/home/david/Android/system/out
============================================
make: *** /.config: Is a directory. Stop.
I've searched and haven't found a solution but It seems like I'm missing a manifest or something. I'm wondering if this is missing from 10.2 and I should just try building 11 or if there's a way I can build from source.
Thanks to anyone who can help!
No experience building CM but it looks like maybe /.config instead of ./config got invoked?
Sent from HD+ MAG2GA CM 11 from SD
Did you follow this guide? -> http://wiki.cyanogenmod.org/w/Build_for_ovation (repo init for cm11 instead if cm11 is desired)
Its probably just an error that you made. I don't remember seeing it before.
Edit it doesn't like /.config. That much is obvious. So try to rename or move it or fix your problem to avoid it. (if its ~/.config be careful as that is an important dir.)
There is a .config in /out during building process which is the kernel defconfig file. There is also ~/.config. And that's all I know about that. Look around for .config or google your error with "/.config;" removed and see how the "make: *** is a directory. stop" plain version helps you.
I followed the guide in the wiki but it's a no go. I removed and resynced just in case something didn't pull correctly (wouldn't be the first time). I'm grepping the makefiles for .config to try and narrow down the problem but it doesn't seem to be helping. I've compared the structures of the Galaxy Nexus and the Nook build trees and I don't see any huge differences.
<edit>
Found a bunch of config files but no .config, now I'm even more confused.
ddpruitt said:
I followed the guide in the wiki but it's a no go. I removed and resynced just in case something didn't pull correctly (wouldn't be the first time). I'm grepping the makefiles for .config to try and narrow down the problem but it doesn't seem to be helping. I've compared the structures of the Galaxy Nexus and the Nook build trees and I don't see any huge differences.
<edit>
Found a bunch of config files but no .config, now I'm even more confused.
Click to expand...
Click to collapse
It shouldn't be in what you received with the guide as your getting the device repo, but how you did it or something that is not configured correctly on your os.
Its a bit confusing but the error says what it wants and that's the key.
Edit: Tried to get my build to do the same but no go. Out of ideas for you. Sorry
Some other thoughts based on testing:
You get the correct manifest, etc. with the git and repo sync so again its not with what your getting. That all will build it without that weird error.
If there's no .config file in android/system/out/target/product/ovation/obj/KERNEL_OBJ/ then its because it didn't do enough to put one there yet. That shouldn't be the issue as it will rename a .config dir and continue or if it can't then have a different error.
Did you try make clean or make clobber and try building again?
sandsofmyst said:
It shouldn't be in what you received with the guide as your getting the device repo, but how you did it or something that is not configured correctly on your os.
Its a bit confusing but the error says what it wants and that's the key.
Edit: Tried to get my build to do the same but no go. Out of ideas for you. Sorry
Click to expand...
Click to collapse
I had someone else try it on an Ubuntu machine and it has the same issue. I'll try to get the verygreen repos instead of the official CM ones see if that helps
Duplicated! ...
You have a .config directory in /
Exactly as the error says as I get the same error only by creating one there. Or I should say the exact same error line and no building.
sandsofmyst said:
Duplicated! ...
You have a .config directory in /
Exactly as the error says as I get the same error only by creating one there. Or I should say the exact same error line and no building.
Click to expand...
Click to collapse
You're an absolute genius. For some reason I did have a /.config directory, I never even though of looking in the root directories. Must be some strange KDE issue. I deleted it and build kicked off and it's rolling fine now.

Categories

Resources