Hi All
I am trying to get a CM6 Kernel to build for my HTC Desire. I have tried almost all of the suggestions found on these forums with very little success. At the moment I can compile KO's using the kernel sources (and a little magic version manipulation) and loading those ko's into the phone seems to work just fine. However, when I try to load the zImage into the phone, I get nothing out, adb logcat has no output. I am pretty sure my packager works (I am using published scripts to extract a kernel image from the pre-compiled nightly and I can repackage the pre-compiled kernel without any issues).
The conclusion I have come to is that although I have extracted .config from the nightly build along with the other files obtained from the phone with the extraction script, I cannot compile a new kernel that works.
REQUEST: Does anyone have a link to the scripts cyanogenmod is using to kick off the nightly builds for each of the phone types? Since they seem to be able to build an image that runs on my phone, I should be able to do the same thing using a sub set of their scripts.
I'm relatively new to the developing scene, and I was looking to get my start with compiling a CM10 ROM. I compiled it just fine, no issues, and I'm currently running that on my phone. Then I decided to try to compile 10.1. I was able to do it the same way as the 10 ROM, except just selecting a different Repo and extracting the proprietary files from a 10.1 ROM instead of 10. So I compile the ROM, flash it, and No communication with the SIM card. No number, no IMEI, no Network status, NOTHING. I flash back to my CM10 build, and it works just fine. I delete the 10.1 repo and redownload it, rebuilt the ROM, same problem! Anybody able to help me here?
I have exactly the same problem. I build 10.1 once with the files pulles from my phone and one with the propertary files from a repository. I also build it on two different maschines and tested it on 3 different devices.
Any hint?
I don't agree with this being here, more of a Q/A section post really...
Try again now, after this it should work:
https://github.com/CyanogenMod/andr...mmit/b703b0121d0356753834fd99ce38736a35f342ca
To know if that's going to fix your issue, see if you are missing /system/lib/libril.so in your rom.
Kindly discuss your issue here - http://tinyurl.com/7habffm
You'll get some good info/knowledge with many users sharing their experience.
Since development for the Sidekick 4G has stopped I decided to try and port the CM11 M10 snapshot from the Galaxy S 4G using this guide. I used the Galaxy S 4G as port ROM since most of the specs are the same as the SK4G. The base ROM I used is ayoteddy"s KJ2 Deodexed & rooted ROM. I followed the guide and flashed the ROM I made but the phone didn't boot. It stays stuck at the tmobile startup screen and then bootloops. I took a logcat and see a lot of errors but idk how to correct them. I tried uploading the ROMs I used and the one I created but it only let me upload the logcat.
Hey,
Its awesome to see some more effort in this phone but when porting a ROM one of the main prerequisites is the base being the same android version.
So to port cm11 over you would need a kitkat kernel and ROM for the sk4g already.
What would be real helpful is to get the gingerbread kernel fully functional then any GB ROM could be ported fairly easily.
Or start with a kitkat kernel but both require a bit of work. If you want to take it on a can link a bunch of guides that may help
Thanks for that info. I don't have experience coding but I would like to be able to learn how to cook and port roms so I would really appreciate some guides. As I understand it, since there is no KitKat ROM available for the sk4g I would first need to make my own KitKat kernel and ROM before I would be able to port cm11? And how long do you think it would take to learn everything needed to be able to port and cook roms?
Hey,
On mobile right now so can't post a bunch of links but xda is filled with them
The best place to start would be http://www.xda-university.com
And be sure to check out the forum links as well!
For a quick set of links see the seventh post in this thread
http://forum.xda-developers.com/showthread.php?t=2348266
For a different device but those are all great places to start learning to develop for android
Keep me posted on your progress!
Took me a while to find some useful guides since I was searching with the term "port" and not "build/compile from source" since that is essentially what I'm doing. I used wiki.cyanogenmod.org/w/Doc:_porting_intro and wiki.cyanogenmod.org/w/Build_for_galaxysmtd (can't post links yet). I forked the galaxys4g repo and modified the files to be suited for the sidekick4g. Now I'm onto the building step, a couple of things already broke and I managed to fix them, but I ran into this error and haven't been able to fix it.
brunch sidekick4"ebtables is disabled on this build"
find: `src': No such file or directory
build/core/base_rules.mk:134: *** system/extras/ext4_utils: MODULE.TARGET.EXECUTABLES.setup_fs already defined by device/samsung/sidekick4g. Stop.
I researched the MODULE.TARGET.EXECUTABLES.setup_fs already defined by device/samsung/sidekick4g issue and suggestions were to delete the setup_fs file within device/samsung/sidekick4g folder. However the setup_fs file wasn't in there, I did find a setup_fs.c file and deleted that one. Then I proceeded to try the build again and ran into the same error. Another suggestion was to use grep -R setup_fs *. This command pointed to these files,
Android.mk:LOCAL_SRC_FILES := setup_fs.c
Android.mk:LOCAL_MODULE := setup_fs
Android.mk~:LOCAL_SRC_FILES := setup_fs.c
Android.mk~:LOCAL_MODULE := setup_fs
initramfs/init.herring.rc:service setup_fs /system/bin/setup_fs /dev/block/platform/s3c-sdhci.0/by-name/userdata
sidekick4g.mk: setup_fs
But I don't know what exactly I'm supposed to delete. The device repo is located at github.com/SK4G/android_device_samsung_sidekick4g.git It is a pre-build attempt version before I made suggested changes to the local repo. I tried "git push origin master", the command went through and said everything is up to date but the remote repo still wasn't changed so I haven't been able to update it.
What are you using for the device tree? The relay is a completely different device and none of the drivers would work, did you at least pull blobs and proprietary files from a sk4g?
There is a ton of setup to be done in order to build from source, you can use the cm11 source but need to make a specific device tree for the sidekick to get a working build, not to mention a ton of kernel work will be needed
For the device tree I forked the galaxys4g repo (not the galaxy s relay 4g) and then modified the files to build the sidekick4g specific device tree. When pulling the blobs and proprietary files the guide said " Your device should already be running a build of CyanogenMod for the branch you wish to build for the extract-files.sh script to function properly". Not sure if that's relevant to the errors but I was still able to pull the blobs towards the correct ~/android/system/vendor/samsung directory. As far as the kernel I downloaded the stock kernel from the samsung source website and then put it in the kernel/samsung/sidekick4g directory. The guide said that the kernel and kernel modules would be built automatically as long as I made appropritate changes to the BoardConfig.mk and I did so. I have done every step in the guide and now I'm into building but I can't get past the previously mentioned error. Should I delete the whole part of the files mentioned by the grep -R setup_fs * command or just the red part or is there another solution?
Well the blobs that were pulled and the kernel that was used was for froyo, that won't work for kitkat without a weeks worth of modification
Also the s4 is even more different than the relay and would be much harder to use anything from there
What you need at this point is to create your own device tree on github and add this to your local manifest, then the hard part is to adapt the sk4g kernel into something that will work with kitkat, once this steps are complete you can build and then fix the errors that come up, fixing any errors at this point won't help much as the files used are incompatible from the start
I should have been more specific, I used the T-Mobile Galaxy S 4G which is one the first galaxy phones. It has the same hummingbird chipset, architecture, ram/rom size, resolution, and both originally ran froyo. The guide states that the cm buildbots build a compatible kernel for me. I didn't just fork the galaxys4g repo and leave it as is. I went through the files and substituted anything that was galaxys4g device specific to fit the sidekick4g.
No problem, should have read more clearly, yes the galaxy s is very similar minus the keyboard but you can look at the work that was done to get a GB ROM booting here
http://forum.xda-developers.com/showthread.php?t=2323617
This was done on the exhibit, another very similar phone,
Even after the kernel was adapted the keyboard never worked, you check the link to his github to see what was put into it to work
The kernel built by the bot won't adapt it to work between different versions of android so you need to build this manually first then you can use it, but even then there will be a lot to do in order to get the keyboard working
Now I'm beginning to understand what you have been trying to tell me. It was hard to grasp at fist because I never really looked into building a kernel since I usually just use the stock kernel or the cm built in kernel on my devices. Now I shall redirect my efforts into building a kernel
Hi I just wanted to know if you're still building port for the sidekick 4G I still have mine and I would like to use if you have kitkat to work. I miss my sidekick 4G
Sent from my Nexus 6 using XDA Free mobile app
This is a script that should last a while when it comes to compatibility. It helps guide you through setting up a build environment to build an AOSP rom from source. I'll create a few more that help for compiling from some other ROM repos (think PA, CM, AOKP, that kind of thing) but for now this is what I've got. I'm working on a second that can set up the source for compiling, choose a device to compile for (and hopefully be able to download stuff like prebuilts and other stuff as well and downloading proprietary blobs) actual devices, compile them, copy the zip to an out folder, and in some cases even directly sideload it. Enjoy!
Oh yeah, you need Ubuntu/derivative other than mint 14.04 or later (64 bit version ONLY) and over 60gb of free space.
This guide currently downloads source for android 5.0.
Has anyone tried this? Did it help?
I'm trying to build AOSP from source, I've got my repo's setup just fine, but I'm unable to find the device tree or vendor files anywhere, or how to obtain anything. The only other thread I found had a single response saying to just build CM instead, which is exactly what I am trying to avoid. My main goal is to get Slim6 ported properly and that's all in AOSP base.
there is an aosp build already, check that thread