Database Develop

How do you switch out Kernels?

I found a rom that uses 10mb ram ack and i would like to switch out for Cyanogens Kernel... How would i go about doing this?

just switch from other ROM
you would take the boot.img and the wlan.ko from another ROM or cyanogen build then you would put them into the ROM you have with the memory hack and replace the old ones with the new ones. after that sign the the update.zip and flash my freind

flash_image boot /sdcard/boot.img
(replace /sdcard/boot.img with whatever you called it and where you saved it)

ralle.gade said:
you would take the boot.img and the wlan.ko from another ROM or cyanogen build then you would put them into the ROM you have with the memory hack and replace the old ones with the new ones. after that sign the the update.zip and flash my freind
Click to expand...
Click to collapse
I tried both these methods and I get stuck at the G1 screen
I tried switching to a Cyanogen Kernel

SD/MemCard Nu-Incubus26Jc's FroYo 2.2 RLS10 7/13/2010

This is being released for TESTING PURPOSES ONLY. This is not intended to be a full release.
This is an SD Card release ONLY, if you want to flash the entire phone, visit the original thread. Beyond that, the build is 100% unchanged from the 7/10/2010 release of Incubus26Jc's Super FroYo 2.2 [Deodexed] [RLS10] - this is not the all languages release, just the standard RLS10 as downloadable from here.
All original information is in Incubus' original thread: http://forum.xda-developers.com/showthread.php?t=712310
I may just be being impatient, but this froze up on me a couple of times right after completing setup and beginning sync. Still, I have been able to fully install, boot the phone through HaRET, get text messages, and a little more. I've barely had much time to test this, but it's a step above your traditional proof of concept, so try it out!
Note, this release is not intended to either show up Incubus26Jc, nor claim his work as my own. I simply made the conversion and RAR'd it up. I'm sure Incubus26Jc chooses not to make an SDCard version available for his own reases and possibly doesn't want his name associated for whatever reason, I didn't clear this release in advance, and if requested, I will delete the thread.
>>>Direct Download Nu-Incubus Super FroYo 2.2 RLS10SD<<<

NuAngel said:
I actually bought a few pieces of software to do the conversion, but I figured a few bucks was worth it for something fun like this. Although, if anybody would like to donate a few bucks to the cause, PM me and I can get you my paypal address.
Click to expand...
Click to collapse
What exactly did you "convert"? And what software did you need? From first glance it just looks like you just threw the tar in with all the sdcard files found in other builds. The extracted tar and tgz are the same size... and you said that it's 100% the same thing... so why do we need a separate thread for this? Just ask Incubus if he could add the andboot files in a separate download in the original thread...

Well, in most basic terms all I did was convert the TGZ to a TAR, then grabbed the necessary HaRET files - but after this many releases, Incubus has intentionally had no SDCard version of his releases, so I just thought I'd toss this one out there for those like me who were interested in trying his latest release, but don't want to completely make the switch to Android and just like running it through WinMo.
NuAngel

NuAngel said:
Well, I'll just say the most basic thing I did was convert the TGZ to a TAR, then grabbed the necessary HaRET files - but after this many releases, Incubus has intentionally had no SDCard version of his releases, so I just thought I'd toss this one out there for those like me who were interested in trying his latest release, but don't want to completely make the switch to Android and just like running it through WinMo.
NuAngel
Click to expand...
Click to collapse
I read a post a while back by dzo on incubus' thread that in order to boot the TGZ from HaRet, you need to modify something in the default.txt (add a couple of lines in the cmd). Thanks for this though...

egzthunder1 said:
I read a post a while back by dzo on incubus' thread that in order to boot the TGZ from HaRet, you need to modify something in the default.txt (add a couple of lines in the cmd). Thanks for this though...
Click to expand...
Click to collapse
I am using Androidinstall.tgz files. Just install it to the SD card using the norootfs method that has been used for a while. His builds aren't anti-SD card from what I can tell...

Thanks for the kind words, EGZ. Wasn't trying to take any attention away from Incubus at all, I just wanted to tinker with it, myself, which was why I released it! I don't really intend to keep up with future releases, unless people actually want me to continue.
And the reason I had to spend money is because I don't currently have a single Linux machine in my place, and WinRAR doesn't make TAR files.
NuAngel

Do I understand this correctly?
Are you basically just wanting to install the Incubus FroYo build on the SD card? I was unsure about the exact method to do this as well. Here are the steps I followed to make it happen.
I think I did something similar to what you are doing here, except the convert the tgz to tar. All I did was take the tgz file and rename the extension to tar. No zipped or rar file program needed. Then I grabbed the basic haret files from Myn's eclair along with the updated zImage file. I threw it all in the andboot dir on the SD card. Everything installed just fine. Is this what you are trying to accomplish?

Vivafutbol - yup, pretty much the same process - I just never expected renaming the TGZ to TAR to work - they're similar fromats, but not identical... surprised it worked!
Still, if anyone is interested in checking it out, they can download it from the link above, no need to do any work.
NuAngel

NuAngel said:
And the reason I had to spend money is because I don't currently have a single Linux machine in my place, and WinRAR doesn't make TAR files.
NuAngel
Click to expand...
Click to collapse
There is no need to spend money for what you did. TGZ is just a gzipped TAR file and many freeware archivers can extract TAR from TGZ - like 7-Zip http://www.7-zip.org/ ..
Also, HaRET can handle TGZ..

NuAngel said:
And the reason I had to spend money is because I don't currently have a single Linux machine in my place, and WinRAR doesn't make TAR files.
NuAngel
Click to expand...
Click to collapse
Just out of curiosity, what program did you have to purchase that does this?

milanche said:
There is no need to spend money for what you did. TGZ is just a gzipped TAR file and many freeware archivers can extract TAR from TGZ - like 7-Zip http://www.7-zip.org/ ..
Also, HaRET can handle TGZ..
Click to expand...
Click to collapse
Doesn't HaRET just boot the zImage? Then in the kernel is where you would activate the system image like in the old days, or the adroidinstall.tar or tgz?

Forget I tried.

Oh, and 7-Zip will extract TGZ's - but the TGZ had folders in it, not another TAR file - thus getting those folders back in to a TAR required another piece of software - 7Zip doesn't create tar files.
It's okay, it was like $10. I didn't expect this to become the focal point of the ROM. Jesus.

NuAngel said:
Forget I tried.
Click to expand...
Click to collapse
It's great that you tried. You won't get the experience unless you do try.
The only problem I have with all of this is that you indirectly asked if people would donate to you. You couldve done a little research and found out that you didnt need to spend any money.
I'm not trying to attack you, you just couldve went about it differently. Asked Incubus if he could host it in the original thread (and at least given you credit), or if he would mind if you opened a new thread. I'm not speaking for him but I'm sure he would'nt have mind.
Again, I think it's great that you tried this on your own. We need more people like that in this community.

NuAngel said:
Oh, and 7-Zip will extract TGZ's - but the TGZ had folders in it, not another TAR file - thus getting those folders back in to a TAR required another piece of software - 7Zip doesn't create tar files.
It's okay, it was like $10. I didn't expect this to become the focal point of the ROM. Jesus.
Click to expand...
Click to collapse
I did it manually as well, and I didn't even rename the .tgz to .tar
I admit I had to hunt around for some files, so this does help, thank you

Its not my rom either. Its dzo's rom. I just done a few things to it. The reason i never put up sd install files in the roms is because of all the problems people usually have until they flash nand and all is better. I can put the haret files on the OP if you would like. No harm done buddy.

I saw your windows rom but haven't tried it yet because i'm still using nfsfan. Apreciate someone new taking an interest in vogue. Also I did flash froyo to my sd card but did have to read quite a bit. I am sure I would have appreciated being spoon fed. Thanks.

Since the last few posts have been pretty positive, one thing I might work on is slapping in an updated zImage file, since I did use a slightly olde one to try and boost stability (those who know my Windows Mobile ROM know that's my central focus).
NuAngel

NuAngel said:
Since the last few posts have been pretty positive, one thing I might work on is slapping in an updated zImage file, since I did use a slightly olde one to try and boost stability (those who know my Windows Mobile ROM know that's my central focus).
NuAngel
Click to expand...
Click to collapse
Also, the initrd.gz is very old (Maybe before the .tgz support was implemented). Try using THIS ONE (taken from HERE) with the tgz to see if it works.

I hope you did not take my post on the negative side. At the very least this thread has created some good conversation about how these files actually work together. I did have to search around for a while to get an understanding of which files should be used.
I personally like the SD version of the builds, because I don't have the guts to wipe out the windows install and risk breaking this great little device.

Understanding zimage/.nbh

Sorry for the newbie question.
When people refer to the zimage or .nbh, I don't really understand what that means. All I've done is downloaded the latest haret and used that to install Incubus' Froyo. Everything works fine (except the camera!). So what does zimage or .nbh have to do with anything?

Its the Kernel or in other words the operation System.
The zimage is for the haret method and the nbh is to flash android over windows.
So you only need the one for your prefered method.
incubus,cyanogen,freshfroyo.. are the builds that are set on this kernel (its like windows and the programms set upon dos(^^yeah old windows ;D ))
Heres a good guide if you think about flashing:http://forum.xda-developers.com/showthread.php?t=636024
The newest zimage and nbh can be found in incubus thread, he has a link there in the start post. ( here: http://it029000.massey.ac.nz/vogue/files/?C=M;O=D)
This is how i got it, hope its not wrong ;D

dertester123 said:
Its the Kernel or in other words the operation System.
The zimage is for the haret method and the nbh is to flash android over windows.
So you only need the one for your prefered method.
incubus,cyanogen,freshfroyo.. are the builds that are set on this kernel (its like windows and the programms set upon dos(^^yeah old windows ;D ))
Heres a good guide if you think about flashing:http://forum.xda-developers.com/showthread.php?t=636024
The newest zimage and nbh can be found in incubus thread, he has a link there in the start post. ( here: http://it029000.massey.ac.nz/vogue/files/?C=M;O=D)
This is how i got it, hope its not wrong ;D
Click to expand...
Click to collapse
That's a little more clear, thank you. But I still don't quite get it. Does haret already include a zimage? I've downloaded the latest haret and incubus froyo and installed on SD card, works great, but I've never installed/downloaded a zimage. Is this something that I need to bother with?

joelshort said:
That's a little more clear, thank you. But I still don't quite get it. Does haret already include a zimage? I've downloaded the latest haret and incubus froyo and installed on SD card, works great, but I've never installed/downloaded a zimage. Is this something that I need to bother with?
Click to expand...
Click to collapse
Depending on who/where you download haret from, it may or may not include all the files needed to boot. The "package" that has to be in place for haret to work is
Code:
SDCard\andboot\haret.exe (executable that reboots phone to Linux environment from WinMo)
SDCard\andboot\zImage (compressed Linux image with support for our hardware that Android runs in)
SDCard\andboot\initrd.gz (don't know)
SDCard\andboot\default.txt/startup.txt (rules Haret follows/info given to zImage when loading)
zImage and initrd.gz are updated from time to time providing a more stable environment or new features to emulate Android on.

Lintegras said:
Depending on who/where you download haret from, it may or may not include all the files needed to boot. The "package" that has to be in place for haret to work is
Code:
SDCard\andboot\haret.exe (executable that reboots phone to Linux environment from WinMo)
SDCard\andboot\zImage (compressed Linux image with support for our hardware that Android runs in)
SDCard\andboot\initrd.gz (don't know)
SDCard\andboot\default.txt/startup.txt (rules Haret follows/info given to zImage when loading)
zImage and initrd.gz are updated from time to time providing a more stable environment or new features to emulate Android on.
Click to expand...
Click to collapse
Thanks! That's much more clear, and I get it now.

joelshort said:
Thanks! That's much more clear, and I get it now.
Click to expand...
Click to collapse
Any other questions, feel free to read, search, and ask if you can't find it anywhere.

[Guide]How to Port roms to your mobile

This guide will help you in porting ROM's to different devices. Although it my not work 100% of the time, it should you show the steps involved in porting a ROM but also which files are important to a device's functionality.
Some handy tools to have before starting:
- The Android SDK, this contains ADB logcat which is a hugely important tool in ROM development. It lets us know what is perhaps causing an app to F/C or a ROM to bootloop. See our guide on how to set this up HERE
- Notepad++ , very useful for altering scripts.
- Patience, getting ports to boot can sometimes take a lot of effort and time but hopefully this guide will show you the quickest and easiest way to get your ported ROM booting.
Okay first decide which ROM you would like to port, don't port HDPI ROM's to MDPI devices or vice versa it just won't work.And it's best to start with the easy and simple ports to get some experience behind you before you go off porting Sense 3.0 to your X10.
Let's get started...
Porting is fairly easy and requires only some folders, files and a boot.img to be replaced.
Now because this is a universal guide I can only tell you how to get the basic hardware working on your port. AOSP ROMs are fairly easy to figure out so you won't have much trouble figuring out what needs replacing. Manufacturer specific ROMs such as Sense 3.0 ROMs are bit more difficult to figure out but the basic skills you will be taught here can be applied in principle to those ROMs.
1. First off lets start with the biggie, the kernel. Those of you familiar with linux will know how important the kernel is a to system, I won't go into detail here but if your kernel isn't specific to your device then your ROM won't boot. The kernel is contained within the boot.img of your ROM's zip (or zImage if it's a Samsung). During flashing it is unpacked and wrote to the system.
To replace the kernel we need to decompile it and no this isn't as easy as opening it winzip. The best way to do this is using Linux; we can use a combination of both perl scripts and terminal commands.
In order for us too see the kernel files contained within the boot.img, we need to first unpack it and this will extract the kernel binary and the ramdisk. What you need at this point is the split_bootimg.zip. This contains a perl script which will extract both files and display the boot.img header, the kernel command line and the board name (if specified).
An example of the output would be:
Page size: 2048 (0x00000800)
Kernel size: 1388548 (0x00153004)
Ramdisk size: 141518 (0x000228ce)
Second size: 0 (0x00000000)
Board name:
Command line: no_console_suspend=1
So how to use this perl script you ask? Well...
First open a terminal and cd to the directory which contains the perl scripts you just downloaded. Next, type this command: "perl split_bootimg.pl boot.img" and that will extract the kernel to your current directory.
Now, we need to extract the ramdisk, the ramdisk has been unpacked from the boot.img and is sitting your current directory with the file name "boot.img-ramdisk.gz", at the moment this still isn't useful to us so we need to un-gzip and then un-cpio it.
So for that we need the Linux terminal. So again from the terminal or using the same terminal enter these commands:
mkdir ramdisk < Creates a directory where we can store the ramdisk
cd ramdisk < Changes our current directory to that of the ramdisk
gzip -dc ../boot.img-ramdisk.gz | cpio -i < Will un-gzip and un-cpio ramdisk
Okay so now we can see all the ramdisk files:
./init.devicename.rc
./default.prop
./proc
./dev
./init.rc
./init
./sys
./init.goldfish.rc
./sbin
./sbin/adbd
./system
./data
So what's important here is the "init.devicename.rc" and "unvented.device.rc". This is the target devices .rc files contained within the ramdisk, now all we have to do here is rename this .rc file to that of the device you are porting to, e.g: "init.trout.rc" > "init.hero.rc"
Some devices ramdisk differ and may not contain "unvented.device.rc" so if this is case for you,then begin by renaming the init.device.rc to your model id and leave it at that. If you get problems well.. that's what the live support is for.
The other file which may be of use to us here is "init.rc", this contains all the system wide kernel properties which we can change to our liking but we'll leave as it is for now.
So now we've edited the ramdisk, we need to change the kernel so that the one the ROM uses is actually specific to our device, when we used the split_bootimg perl script it also unpacked the kernel and that is also in our current directory with the filename "boot.img-kernel".
Easiest way to replace the kernel is to take a kernel update zip for your device, un-zip it and rename the zImage file to "boot.img-kernel" and copy and replace the file of the same name in your directory.
Okay, now that's all done, we need to pack this back up into something that android can understand when it's being flashed. So we need to make a new boot.img from the files we have in our current directory.
First, we need to pack the ramdisk back up into it's original state, so again we need to use the Linux terminal. The command that will do this is this:
find . | cpio -o -H newc | gzip > ../newramdisk.cpio.gz
Remember the ../ is the path to the directory of your ramdisk, remember to remove anything that won't be used by the kernel as cpio will include EVERYTHING in the working directory.
Okay now that the ramdisk is back in it's original format we need to repack the kernel and ramdisk into the boot.img.
So back into the terminal we go and this time we're going to use the "repack-bootimg" perl script (as if that wasn't obvious enough). The command you will ise here is esentially the same to the one we used to split it, so:
"perl repack-bootimg.pl ../path to kernel ../path to ramdisk directory ../path to outfile"
And the boot.img is complete!
So if we look back to the ROM we are porting we can see that we need to put the boot.img into the root of the zip, this will hold true for almost every Android ROM. Next we need to replace some of the files which allow the hardware and keys to work. This is the easy part.
Go into the root of the zip and follow this path to the kernel modules; "/system/lib/modules" Delete all the files you find here.
Now take the kernel modules which came along with the kernel you added to the boot.img and copy them there. Next follow this path to the propietary hardware files;
"/system/lib/hw" Delete all the files you find here.
Again this as simple as taking the files from a ROM meant for your device and copying them into this directory. So what we've done there is added the kernel modules that we can set symlinks to in the updater-script and contain the modules needed for things like WiFi, bluetooth etc. The "/hw" directory as you can see contains the files which control the sensors and lights such as GPS and the accelerometer.
Next, we can look at making sure the hard and soft keys work, the files which contain the layout of your device keys can be found in;
"/system/usr/keylayout" and "/system/usr/keychars"
Touch only those 2 directories.
Delete all the files in here and copy the ones from your device (following the same directory) here.
Okay now to finish off we need to copy over the mount point information for your device and the WiFi drivers.
Follow this path; "/system/etc" and delete only these files and directories.
- vold.fstab
- /wifi
- /ppp
Now follow the same path in a ROM for your device and copy over these files.
Okay we're done!
Before flashing take a look and some guides which show you how to write updater-scripts, incase you need to create important symbolic links.
Happy Porting!
**mod edit** credits to JieeHD from the VillainROM team for this guide! original thread here: http://www.freeyourandroid.com/guide/porting-android

reserved for future......

Hey,how did i help in this?
PS:i m thinking of buying this phone.....is it any good?

i have both the galaxy sl and spice mi 410 i copied from your thread so had to give you credit even though you are not the original poster
spice mi 410 competely outshines galaxy sl so much so that i hardly use sl hooked to this at i.6ghz its lightning fast great plays any game hardly random reboots though average camera galaxy sl better
side note :if you could build succh a nice rom with sl god knows what good you can do with mi 410 please buy it haha
cranium rocks

oh cool............i had forgotten about that thread
2nd hand for 9999 only.................

Hey that's my tutorial... Hope it helps someone....
Sent from my SAMSUNG-SGH-I777 using xda premium

rdannar said:
Hey that's my tutorial... Hope it helps someone....
Sent from my SAMSUNG-SGH-I777 using xda premium
Click to expand...
Click to collapse
than credit to you i am just sharing with everyone "hope it helps someone"

Thank you!!! Will try too port a gt-I9100 rom to a gt-I9100G.
Hope it will be easy with this guide.

Dear Preyesh1.... Could you add the credit to the creator of this guide or at least you mention the url source because I've seen this guide just exactly as in this thread somewhere in the internet.
Except if this guide is pure of yours.
Just to remind...
Edited: Never mind... The creator has been here after all...

I have some questions:
so this means you can take the U9000 android 2.2.2 kernel and merge with ICS?
or does this only works with kernel coming from a GB build to another GB build?

It will help me cause I'm gonna use it soon
Sent from my Triumph using XDA

ziggy46 said:
It will help me cause I'm gonna use it soon
Sent from my Triumph using XDA
Click to expand...
Click to collapse
Hey are you going to port your rom to your device this will be great...!!

I wanna try this great tutorial
Sent from my Droid using Tapatalk

Nice plagiarism.
I mean look at that OP. You've selected the entire article, hit copy, hit new post here, hit paste then hit submit. That's plagiarism of the laziest kind you could have at the very least put some effort in, formatted the text, used code blocks etc.
My word.
edit:
preyesh1 said:
See our guide on how to set this up HERE
Click to expand...
Click to collapse
Hahahahaha.

[Q] init untracked pid xxxx exited

So this is a pretty familiar problem:
init untracked pid xxxx exited
I places xxxx, because the error doesn't stay at the same number: it goes from 100 all the up to 500, that's when I pull the battery from the phone in order to stop the loop
I am getting this error when I am trying to port IceCreamBread v1.1 from the HTC Wildfire thread, http://forum.xda-developers.com/showthread.php?t=1336611. But I always stumble upon this problem. The rom is posted in the downloadlink:
http://dl.dropbox.com/u/8992815/xda/androidinstall.tar
I am also unable to get information from logcat, since the error occurs before the bootlogo appears (out of my personal experience I noticed that ddms isn't able to detect my phone, before I am able to see the bootscreen).
I have also used the init.rc from the IceCreamBread v1.1, which I extracted from the boot.img of this build with dsixda's kitchen, but still I have no luck.
In a whim I even extracted the zImage from the IceCreamBread v1.1 build to try to boot this rom, but then, as expected, the phone just reboots right after initialize haret.
So what can I do know? I am able to boot the Official cyanogenmod build for the HTC Wildfire when I perform this method, but with this rom booting results in the aforementioned error

I don't have HTC VOGUE/Kaiser! I edit ROMs for JetDroid! So I can not help really much and also I read this post quickly....
"untracked pid xxxx exited" coming because some files is not working maybe you need to change boot.img to other boot.img! I cant unpack/repack boot.img so I can not help with that... JetDroid is using zImage and sometimes some ROMs will not work with zImage which is for ex: CM6... so then it needs other zImage, so try to use HTC Wildfire boot.img if it have it but try to edit it for your device... then check the init.rc and edit it for your device... add the files what it needs to work, etc.
If you replacing one file and it gets the untracked pid xxxx exited, then you need to add the original file back and then maybe works.......
EDIT: it works for me but init.rc needs editing!
init: cannot find setupmodem.sh, leds, etc...
EDIT2: when I use your edited ROM and then sysinit.rc what I renamed to init.rc and added other files to EXT3 on JetDroid then I see odd text and then it's booting and android boot logo stocks many times... so one or more files is not working! ? and it is 2.3.7 ROM! it's just edited to look a like ICS? maybe it is better to edit HTC Vogue/kaiser GB 2.3 ROM and make it look a like ICS ROM?...

Is there some guide you have found or followed to be a succesfull porter or was it just trail and error for you?
**In your post you adviced to use the boot.img of the device which I was porting, but for example when I use the zImage of the HTC wildfire for my device it simply doesn't boot Haret, but just reboots. So how am I able to edit the zImage: What set-up/programs are you using (I am using windows 7)...
The rom I actually want to port is the HTC Hero's Team-ICS rom, but I stumble upon so many problems. And I really am new to porting roms..... It's in this thread:
http://forum.xda-developers.com/showthread.php?t=1362062
And this is the boot.img from this rom (I managed to extract it with dsixda's kitchen).
http://dl.dropbox.com/u/8992815/xda/BOOT-EXTRACTED.zip
Fact is that I copy all the, in my eyes appropriate, files from Scoot's gingerbread build, but when I copy these files I am always stuck at the aforementioned init errors. I copy the following files:
http://dl.dropbox.com/u/8992815/xda/porting/Copy/paste.zip
When I copy these files into the original Hero ICS build, in order to get it working on the kaiser, I get that BLOODY init: untracked pid xxxx exited error. The link to the file:
http://dl.dropbox.com/u/8992815/xda/Team ICS 20 dec 4.0.1/androidinstall.tar

hom.hom said:
Is there some guide you have found or followed to be a succesfull porter or was it just trail and error for you?
**In your post you adviced to use the boot.img of the device which I was porting, but for example when I use the zImage of the HTC wildfire for my device it simply doesn't boot Haret, but just reboots. So how am I able to edit the zImage: What set-up/programs are you using (I am using windows 7)...
The rom I actually want to port is the HTC Hero's Team-ICS rom, but I stumble upon so many problems. And I really am new to porting roms..... It's in this thread:
http://forum.xda-developers.com/showthread.php?t=1362062
And this is the boot.img from this rom (I managed to extract it with dsixda's kitchen).
http://dl.dropbox.com/u/8992815/xda/BOOT-EXTRACTED.zip
Fact is that I copy all the, in my eyes appropriate, files from Scoot's gingerbread build, but when I copy these files I am always stuck at the aforementioned init errors. I copy the following files:
http://dl.dropbox.com/u/8992815/xda/porting/Copy/paste.zip
When I copy these files into the original Hero ICS build, in order to get it working on the kaiser, I get that BLOODY init: untracked pid xxxx exited error. The link to the file:
http://dl.dropbox.com/u/8992815/xda/Team ICS 20 dec 4.0.1/androidinstall.tar
Click to expand...
Click to collapse
OK!
I can not edit Android files so I don't really know how can edit zImage...
zImage: on Linux Ubuntu can be edited somehow with terminal and on Windows you need to use Microsoft Visual C+/C++ or something like that and then you need source files!

I tried to run your rom from first post but without success. One by one I eliminated init errors by changing files from my working 2.3.7 port, however, at the end i get bootloop with many another errors in logcat... Be honest, at this point I gave up and did not want to waste more time on it.
Using this "copy-paste" port method I had more luck with htc tattoo roms than wildfire
About porting ICS. If I can trust people trying to port AOSP ICS to my second phone(LG) - without recomplilaton kernel and drivers we don't have chance to get this working on kaiser. Too many differences...

MaRekRM said:
About porting ICS. If I can trust people trying to port AOSP ICS to my second phone(LG) - without recomplilaton kernel and drivers we don't have chance to get this working on kaiser. Too many differences...
Click to expand...
Click to collapse
I concur, there are way too many differences to cope with.
I say this from experience from trying to port the Wildfire's Honeyfire build about 8 months ago (buried in a thread somewhere around here).
Best I achieved is exactly the same point you're at now, with untracked PID errors, even after editing initrd and adding the proper drivers for the Vogue to the build.

Has anyone had any luck with this?
What I'm now getting for errors has to do with files being signed (I suppose, have no way to read output).
I get names of modules scrolling across the screen, almost as if the modules in the install don't match the signatures in the kernel modules.

I have personally come to a point where I am stopped, because of my lack of knowledge. So I think that I can't be a great help to you: I am sorry!.
But I think the best thing you can do know, is post the build you got now in an experimental thread (now it is a bit buried under the other posts in this thread). It may attract the attention of a developer with more knowledge, a developer of the same level as DZO.