[Sprint HTC EVO 4G LTE] AsinX:
Hope this helps guys

http://xdaforums.com/showpost.php?p=28020178&postcount=36

Start with a pure sdk system dump and deodex it - or use one of the dumps floating around here that are pre deodexed

you need to basically merge it with your latest ics build - I used my last compile of cm9 as a base but needless to say the closer the base is to aosp the better. You'll want to keep as much of the sdk pristine as possible basically just add in the things you need that are device specific such as:

any platform named hw libs from /system/lib/hw

your egl files from /system/lib/egl

your modules from system/lib/modules

wifi, bluetooth, and gps related files from /system/etc

you also will need your idc and keymap files and all the other device specific items out of /system/usr folders so your input methods will work - no idc files means no touch screen

the above error looks like a framework and lib are not getting along. Make sure the frameworks and all of the root /libs are sdk originals you can copy libs over to your sdk port that are not included however just don't overwrite any

make sure you properly modifiy the build.prop to match your device

copy busybox to the working folder into /system/bin and /system/xbin make sure every binary is executable! symlink /system/bin/busybox to /system/bin/sh and replace the sdk version of toolbox bin with the ics version

in ramdisk retain your device.init.rc but replace everything else with what comes in the sdk ramdisk - download the sdk properly and extract the ramdisk as cpio.gz extract it and use it as a base only adding the device specific .rcs that you need. If init.rc needs a few changes make them but as a rule you can usually just use your device.init.rc and keep the master clean. Be sure that init.traces.rc is in your ramdisk it's a new file for jellybean and it gives a crapload of errors when it's not there.

try not to load any wifi modules for initial tests - theres some changes that are screwing mine up if I set my modules to load on boot- it prevents a full boot haha

and this is from: http://xdaforums.com/showthread.php?t=1737736

To those PMing me asking about porting info: Don't expect there to be a simple cut and paste way to port. If you have no experience with porting or don't at least have an understanding of how android is structured, then I would advise you to read up before attempting this. I can provide targeted help if you have a specific issue, but I won't port it for you, and please don't be offended if I suggest you go do some reading.

If you still think you can do this, then here's a checklist of the major things you should look at to get it booting:

•boot.img - Grab mine or any other jellybean boot.img, and pull the entire init.rc and init.traces.rc, and package it up with a cm9 boot.img

•/system/lib/modules + /system/lib/hw - Modules must be brought across from a cm9 rom, and unless your device runs the same chipset as the base you're using (tegra for the n7, omap for the gn), you'll probably need to put all of the hw libs into there too

•/system/etc/firmware + /system/vendor - You'll most probably need to pull both of these dirs into the rom

•/system/lib/egl - You'll want all of the egl libs and egl.conf

•Various /system/etc files - There's usually some configs, firmware, and other stuff in here

•/system/lib - There's tons of files in here, a lot of which you'll need to bring over, and a lot of which you'll need to leave alone. Best advice I can give you is to find an open source cm9 tree for your device and check the proprietary-files.txt file