Database Develop

Camera CM9

Hello everyone,
I am trying to get the camera work on CM9 but it doens't work! so if anyone can help me that would be Great and one last question can we use the camera drivers from the official TAB 7.7 ICS firmware?
using also this: http://forum.xda-developers.com/showthread.php?t=1651530
EDIT:
First fix doesn't work
EDIT:
Trying to do the kernel work now!
EDIT:
There is no boot.img file in the official samsung rom! (4.0.4)

Decompile the 7.7 kernel, find the driver for the camera, pull that section of code, recompile the cm9 kernel with the new driver.

FlanFlinger said:
Decompile the 7.7 kernel, find the driver for the camera, pull that section of code, recompile the cm9 kernel with the new driver.
Click to expand...
Click to collapse
Downloading 7.7 Firmware now after that i will decompile kernel and find the driver for the camera i will pull that to the cm9 kernel and recompile it wish me luck! PS Where to find the kernel in the Boot.img Or am i wrong?

You've got the source code for ICS on the 7.7 ?

FlanFlinger said:
You've got the source code for ICS on the 7.7 ?
Click to expand...
Click to collapse
No can you give me?

Yeah sure, here you go

FlanFlinger said:
Yeah sure, here you go
Click to expand...
Click to collapse
You don't know what you are saying man! im just trying something and you do this
I will never come back on this thread again (Galaxy Tab 8.9)
You guys are just Crazy To say im having ADHD you don't know what that means i think so im the calmest person here now

No need for that language
But lets just clear a few things up shall we......
You are going to reverse engineer (as you have no source code) about 6mb of data from the 7.7 kernel, find all the relevant parts that drive the camera and then use that to recompile the CM9 kernel to get the camera working.....
This is you whose only dev experience is taking a few apps out of a stock rom, repacking it, releasing it WITH NO CHANGELOG and then shortly after deleting the contents of your release post.

FlanFlinger said:
No need for that language
But lets just clear a few things up shall we......
You are going to reverse engineer (as you have no source code) about 6mb of data from the 7.7 kernel, find all the relevant parts that drive the camera and then use that to recompile the CM9 kernel to get the camera working.....
This is you whose only dev experience is taking a few apps out of a stock rom, repacking it, releasing it WITH NO CHANGELOG and then shortly after deleting the contents of your release post.
Click to expand...
Click to collapse
Im now busy with Porting Bindroid rom from galaxy tab 10.1 section i have permission from him is that also not good or can i do that?

safariking said:
Im now busy with Porting Bindroid rom from galaxy tab 10.1 section i have permission from him is that also not good or can i do that?
Click to expand...
Click to collapse
What I've just put in bold is what's really important. Sure, as long as you're willing to fix bugs the community reports because ports usually contain bugs since they are mostly not using native code.

nirogu325 said:
What I've just put in bold is what's really important. Sure, as long as you're willing to fix bugs the community reports because ports usually contain bugs since they are mostly not using native code.
Click to expand...
Click to collapse
Off coarse i will do that

I just wanna save you the trouble since it's not doable, especially not by you. Stop trying and wait for an official 8.9 ICS, only then we would be able to get the camera working.

[Q][DEV] Kexec in new safestrap 2.10 how can we use it?

Hi, guys.
I'm trying to figure out how I can integrate it, basically, for stock safe-system at least.
I downloaded some ready-to-go droid bionic cm9 with kexec integrated, didn't understand the idea of devtree(probably it's patched). Should we compile kexec for ourself with modules? where can I read about it?
Thanks,
Oleg

Might want to check out the Eternity Project website. Kholk seems to be based there and I know he did a lot of the early work on this exploit.
Droid 4 - AOKP K1L0

I read there a little, but if hashcode can comment kexec thing, would be nice.
I saw that it tries to boot kernel when you start safe system, but still need some examples.

http://files.rombot.org/ROMs/maserati/kexec/ try this

tobby88 said:
http://files.rombot.org/ROMs/maserati/kexec/ try this
Click to expand...
Click to collapse
you're quick, downloaded already

So anyone flashed the kexec CM9 build yet? I probably won't get a chance to until this evening.
Droid 4 - AOKP K1L0

kwyrt said:
So anyone flashed the kexec CM9 build yet? I probably won't get a chance to until this evening.
Droid 4 - AOKP K1L0
Click to expand...
Click to collapse
flashed, works fine. But I can't figure out why kexec doesn't boot in my motorola ics based rom
the one good thing I want to say for now - both CPU cores are working fine.

olegfusion said:
flashed, works fine. But I can't figure out why kexec doesn't boot in my motorola ics based rom
the one good thing I want to say for now - both CPU cores are working fine.
Click to expand...
Click to collapse
Sorry for my noobish question, but I have no idea what Kexec is or what it can do.
Would someone mind giving a quick summary?
Thanks!
-Nolam

Nolam20 said:
Sorry for my noobish question, but I have no idea what Kexec is or what it can do.
Would someone mind giving a quick summary?
Thanks!
-Nolam
Click to expand...
Click to collapse
Kexec is the future for D4 ROMs. It is an exploit that allows the flashing of custom built kernels. No more trying to build ROMs around Moto's stock kernel.
Droid 4 - AOKP K1L0

tobby88 said:
http://files.rombot.org/ROMs/maserati/kexec/ try this
Click to expand...
Click to collapse
flashed and working well
edit -- ut oh, spoke too soon. "Can't connect to camera"
hmmm.

mattvirus said:
flashed and working well
edit -- ut oh, spoke too soon. "Can't connect to camera"
hmmm.
Click to expand...
Click to collapse
I think I saw via hashcode's twitter that the camera is the main problem area on the kexec builds.
Droid 4 - AOKP K1L0

Also having quite a difficult time getting gapps to flash. Pulled the 0429 build from goo-im and flashed multiple times but it's never present in the apps list. never seen this before hmmmmm
edit -- got it this (3rd) time, very strange but oh well.

Can anybody try to boot kexec kernel in the eclipse or my rom?
Tried to replace kernel modules, added kexec folder, no luck with booting.
Need to do something with ramdisk, I tried some changes, got cycle reboot after kexec load. Will continue

Continue the thread here:
http://rombot.org/forums/index.php?/topic/1851-rom-nightlies-cm9ics-unofficial-kexec-builds/

[ Guide / Script ] Auto-Porter

WINDOWS
Note: Tested on Windows 8
1) 7-Zip
2) Winmerge
3) Notepad++
4) Java SE Development Kit
5) Place on your Desktop in a folder.
This script comes with instructions for each step, It is the MIUI auto-porter modified for general use with CM10 based roms.
It will say a bunch of stuff about MIUI on the splash-screen at the start, Ignore it.
Any Rom that uses CM10 as a base can be ported to this device using this script.
Download: Auto-porter

I know It's not a new rom update but I figured you folks would like it better, to test it out go to AvatarRoms site or some other CM10 based rom and try your hand at porting!
Some roms will have TW framework or other things like this and that must be taken care of manually, so for more complex ports you will need a good understanding of how to port and diff and xml editing and so on; but for very basic things or to create a quick port to assess what kind of potential work would need to be done, how compatible your device is with a base; this is a good place to start.

Hello
We can port any rom based on CM10 with this ? Like Paranoid Rom ??

Fekajo said:
Hello
We can port any rom based on CM10 with this ? Like Paranoid Rom ??
Click to expand...
Click to collapse
Try to and it wll prob work

I have already tried this with CM10 epinter for base and Paranoid for AT&T One X because they are the same architecture and screen size ( 1280*720 )
But they don't start, i see the log but i don't understand anything ^^'
I retry and i give you feedback
Thanks for your work

im trying that right now the cm10 and pana will tell you if it works its 2.70 so dont think it has pie but hey whatever

Fekajo said:
I have already tried this with CM10 epinter for base and Paranoid for AT&T One X because they are the same architecture and screen size ( 1280*720 )
But they don't start, i see the log but i don't understand anything ^^'
I retry and i give you feedback
Thanks for your work
Click to expand...
Click to collapse
Sometimes the foreign rom is just not compatible as a base, you will see results as you experiment and find which phones are most 'similar' to yours

If anyone has successfully ported a rom with auto-porter that boots and is somewhat functional or functional, then please post and share the details here. I personally do not know how to port a rom, or make a rom etc., But I am willing to learn how to use the auto-porter in this thread if someone is willing to point me in the right direction. Like which base to use, and what modifications need to be done and so on...

the tmobile s3 is based from the same chipset, should try there to see

Will this work with CM10.1 ROMs? Looking into porting AOKP 4.2 the easy way

Ban-Hammer said:
Will this work with CM10.1 ROMs? Looking into porting AOKP 4.2 the easy way
Click to expand...
Click to collapse
Hmmm, Perhaps but most likely not, I haven't tried any CM10.1 roms in this fashion

Tquetski said:
Hmmm, Perhaps but most likely not, I haven't tried any CM10.1 roms in this fashion
Click to expand...
Click to collapse
Alright. I can wait patiently for Hashcode
Sent from my XT926 using Tapatalk 2

Can you do a CM9 version ?

radnou974 said:
Can you do a CM9 version ?
Click to expand...
Click to collapse
Uh....

radnou974 said:
Can you do a CM9 version ?
Click to expand...
Click to collapse
It might work with CM9, worth a try.
May I ask why CM9? CM7 is much more stable on these phones.
Sent from my XT926 using Tapatalk 2

Dam i can't get miui up and running. I know it's kernal related but I'm not even getting a home screen. Smh.
Sent from my Razr HD using Tapatalk 2

[ROM/MOD][WIP]CM for locked BL

Hello guys
First, big fat disclamier:
THIS IS NOT WORKING. Please don't try this for fun, only if you're willing to put in some time to help me get this fixed.
@djolivier and @letama worked out a way to get CM10 running on Xperia S with locked bootloader, loosely based on the work @atis112 did for Xperia U.
For the past couple of days I've been trying to port it to our beloved T.
It does sort of boot but there is nothing on screen. Logcat is working however and so is adb shell (though no su) so we have some way of debugging.
At the moment there is a working recovery (CWM 6.0.4.6 for locked BL by @davidmarco), enter it by pressing vol+ when the led is blue (it will turn green, then red). Here you will have an su shell and you can get dmesg and /proc/last_kmsg.
Please read the thread by djolivier to get an idea of how it works. In the last couple of pages you will find everything I have tried so far and some insightful answers from letama.
So the main thing now is to hunt down which are the libs/drivers we need.
I will try to get some more info into this thread asap but first I wanted to get it up so those of you who think they can help can get going.
Download
cm10_lb_mint_b12.zip - 188.72 MB
This includes the .489 stock kernel, which is probably the best for compatibility.
XDA:DevDB Information
CyanogenMod for Locked Bootloader, a ROM for the Sony Xperia T
Contributors
TiMiN8R, letama, djolivier
ROM OS Version: 4.1.x Jelly Bean
ROM Kernel: Linux 3.4.x
Based On: CyanogenMod
Version Information
Status: Alpha
Created 2014-01-08
Last Updated 2014-01-08

Reserved

I think someone starting this off is a great idea, when i have some free time i'll try to offer you some help mate.
But need to get up to speed with it all from djolivier's thread before anything else. But i'm happy to offer some help when i can, if that be testing, or general de-bugging.

This is awesome.keep up Timn8r
Sent from my LT30p using XDA Premium 4 mobile app

How about asking letama for help? He was the one getting this to work on Xperia S..
By the way, really appreciate you doing this.. Was already waiting for someone to try this on our devices!
When it boots up I will try to flash the 30p to 25i patch and see if it works!
Sent from my LT25i using xda app-developers app

WhiteNeo said:
How about asking letama for help? He was the one getting this to work on Xperia S..
By the way, really appreciate you doing this.. Was already waiting for someone to try this on our devices!
When it boots up I will try to flash the 30p to 25i patch and see if it works!
Sent from my LT25i using xda app-developers app
Click to expand...
Click to collapse
Letama already helped me a lot over in the other thread, getting it up to this point. But now we need to find some very device specific stuff, that's best left to the people who actually have the device to test and debug. My time is limited this week and I don't have a need for this since mine is unlocked, it's just for the sport, so I figured, let's get some other people in on the action
Sent from my Xperia T using XDA Premium 4 mobile app

now im not too sure of this so i maybe completely wrong so please correct me if i am but im sure i read somewhere that the CM kernel drivers and STOCK kernel drivers differ in some way or another ..... again i repeat im not certain on this but if this is the case then certain things in the rom may need redirecting to the STOCK drivers rather than CM drivers as they done exist? ..... if i am right i wouldn't have a clue where to start to be honest but obviously you cant change the drivers in the kernel because then it wouldn't work on LB ..... perhaps ask rimmer for some help or advice as he ported MIUI to stock?

oddeceed said:
now im not too sure of this so i maybe completely wrong so please correct me if i am but im sure i read somewhere that the CM kernel drivers and STOCK kernel drivers differ in some way or another ..... again i repeat im not certain on this but if this is the case then certain things in the rom may need redirecting to the STOCK drivers rather than CM drivers as they done exist? ..... if i am right i wouldn't have a clue where to start to be honest but obviously you cant change the drivers in the kernel because then it wouldn't work on LB ..... perhaps ask rimmer for some help or advice as he ported MIUI to stock?
Click to expand...
Click to collapse
Yes that's just about right. We cannot change the drivers in the kernel but what we can do, and what I've been trying to do, is trying to match the drivers in the rom with the kernel, i.e. swapping out CM drivers for drivers from the stock .489 firmware. But there are quite a lot, that's why we need more people trying, testing, debugging. We could go another way, namely build new CM from source to match the kernel but that's beyond me I'm afraid.
letama said:
There is no easy way to solve that I'm afraid. You can try to play with dlls (check this for a list), but it has big chances to fail. The proper way to do that is to get fxp repo, patch hal to match stock kernel and recompile cm.
Click to expand...
Click to collapse
If @Rimmer1966 wants to help he is welcome of course.

TiMiN8R said:
... there are quite a lot, that's why we need more people trying, testing, debugging. We could go another way, namely build new CM from source to match the kernel but that's beyond me I'm afraid.
Click to expand...
Click to collapse
i know less than you and stuck on windows 8.1 which makes it even harder for me to do anything to help .... i hope that this can get up and running ..... providing you can get screen and touch working its more than enough proof of concept of what can be achieved and if enough different devices get going this way then maybe just maybe teams like CM will revert back from thier custom kernel (which i dont like) and start using stock kernels in builds (we can all dream right?)

Any updates on this? I can help as a beta tester or help with building on my pc.

masterjet said:
Any updates on this? I can help as a beta tester or help with building on my pc.
Click to expand...
Click to collapse
Not much going on on my end. I've been running on the leaked stock 4.3 for the last few days. I did have a little go on using the kernel from that rom to boot CM10.2 but I've not made much progress, seems that SELinux is throwing a spanner in the works.
If anyone wants to have a go, here's what you can do. Get the stock .489 here.
We should try swapping out .so in /system/lib/hw one at a time. You can do this by booting to CWM, mount /system and adb push, chmod 0644 the file and reboot. Get a logcat, reboot to CWM and get dmesg and last_kmsg
Code:
adb logcat > logcat
adb shell cat /proc/last_kmsg > last_kmsg
adb shell dmesg > dmesg
Lather, rinse, repeat. It is a slow and tedious process, so the more the merrier
TiMiN8R said:
I replaced hwcomposer.msm8960.so, that seems yo have fixed it. Also tried a couple of others that didn't work: gralloc.msm8960.so (can't start), copybit.msm8960.so (brought back the camera probs). Still no screen.
Most prominent spam now is
Code:
smd_pkt_open: DATA5_CNTL open failed -19
I also noticed this in logcat
Code:
I/clearpad_fwloader( 681): hanlde_arg: option = [default]
I/clearpad_fwloader( 681): hanlde_arg: saved.module_id = [0x32]
E/clearpad_fwloader( 681): read_sysfs: Unable to open /sys/devices/virtual/input/mice/name
E/clearpad_fwloader( 681): read_sysfs: Unable to open fwfamily
That is the touchscreen. There is indeed no /sys/devices/virtual/input/mice/name. I'm not sure if it is related to the no video issue but it's a problem nonetheless.
Click to expand...
Click to collapse

Thread is dead? No updates, no progress?

masterjet said:
Thread is dead? No updates, no progress?
Click to expand...
Click to collapse
Seems a bit of a dead end. Our stock kernel just seems to be to different from the stock kernel.
No-one else seems to want to pitch in and try some stuff out.
Might have another go with 4.3 when the official Sony's finally out.

it might be a stupid idea but why dont we swap out every .so file from the miui rom witch works with the stock kernel?

like i mentioned before
Why don't we try to do what they did with the moto defy/bravo and run a 2nd init. http://www.google.com/url?sa=t&sour...9ICIDA&usg=AFQjCNHMzrlHTlHC4EjfkhTkZxavJbEJow

lordyka said:
it might be a stupid idea but why dont we swap out every .so file from the miui rom witch works with the stock kernel?
Click to expand...
Click to collapse
If you had read the other thread, you would have known that I've already tried a lot of .so's from stock firmware but nog all of them work. This is the hard part, finding the ones that work.
jewkhok said:
Why don't we try to do what they did with the moto defy/bravo and run a 2nd init. http://www.google.com/url?sa=t&sour...9ICIDA&usg=AFQjCNHMzrlHTlHC4EjfkhTkZxavJbEJow
Click to expand...
Click to collapse
Well the first part, the hijacking, is exactly what does mod is doing. With regards to the 2nd-init program, I'm not sure that init itself is the problem. The "only" problem we have is finding drivers/libs that are compatible with both CM and stock kernel. But I could be off though. If someone wants to build us a 2nd-init go right ahead

Wow just came back to the T forums to see how things were going and I see this! Hopefully Tim can port it I'm sure he can
Sent from my XT1058 using Tapatalk

I honestly don't think 2nd init would make a big difference, as TiMiN8R has already stated, the problems are the drivers. You can now either ask FXP to use drivers from the Sony 4.3 Stock kernel or do it yourself...
Good luck on this, you'll surely make it.
Gesendet von meinem Xperia S mit Tapatalk

got the source codes?
I'm thinking about doing the same with Z1, wouldn't mind take a look at your work

If you asked me: here are the sources.
Gesendet von meinem Xperia S mit Tapatalk

Lollipop for the Optimus 2x

Welcome to the official thread for the Lollipop roms for our Optimus 2x
As to start, this thread is exclusively for the developers who are interessted/working on on the Lollipop ports for our Optimus 2x
We had alredy some build like the OmniRom , CM12 and even ParanoidAndroid.
This thread is exclusively for discussions for the developers and for the testers to test the new made roms so I will update the links as the roms get made. So I am only posting here the links of the latest version, to get the versions from the past you wil need to browse throught this thread
Update 05/6/2016
Gucky did it again! New build for CyanogenMod 12.1 is up, and now with fixed camera! When I get the full list of working features and bugs, I will upload it here. Thank you Gucky for your massive help and contribution to this community. This device is very old after all, and you still find the time to tinker on it. No words really. Respect!
CM12.1 : https://sourceforge.net/projects/lg...cm-12.1-20160531-UNOFFICIAL-p990.zip/download
WARNING the Rom is still not stable, but we are close!
ParanoidAndroid: https://s.basketbuild.com/devs/Puri/p990/AOSPA(lollipop)
Take in mind that all these roms are unstable besides the CM12 rom,but it still has some major bugs which we as a group will fix.
As in all of this, stay tuned for updates

Good job my friend

Thank you very much. I'm downloading right now. It would be useful, if you could upload your (Lokal) Manifest, too. So we are able to re- build the rom with the necessary changes.
Looking forward!
Credits goes to you!

um
gucky01 said:
Thank you very much. I'm downloading right now. It would be useful, if you could upload your (Lokal) Manifest, too. So we are able to re- build the rom with the necessary changes.
Looking forward!
Credits goes to you!
Click to expand...
Click to collapse
um.......*noob mode activated.....BOOP * what you mean with manifest? lol

Could you please share your sources.
TheMysteryouse said:
Hello everyone.As you might know me from some threads where i comment some stuff.Anyways, since Lollipop was announced i was obssesed with it and my wish was that i would be the first one to make the version availble for our device.
Well i kinda did it....KINDA of course but we need some help if we wanna make it work.I call ALL of the developers for our device to work together to make it work.We are so close to get it fully booting.I made it boot to the animation and now where the help comes in use.We need some developers who can enable ADB on our device in the bootanimation.TO be honest i dont really know anything about sources and that stuff but i know some things.With the help of @tonyp and @timduru which I am the most thankfull of that gave me hope to make this.So here we go!
WARNING!!!
ONLY FOR DEVELOPERS
No one should download and flash this rom because you will get stuck in the bootanimation and will need to install previouse rom again and install everything over...blah blah blah.
Also the link to the rom is here ----> https://www.dropbox.com/s/fwhg08ux7qhtgsh/5.0 test.zip?dl=0
So if someone gets it working, please pm me in the progress. Cheers
Click to expand...
Click to collapse

TheMysteryouse said:
um.......*noob mode activated.....BOOP * what you mean with manifest? lol
Click to expand...
Click to collapse
a little help.
http://wiki.cyanogenmod.org/w/Doc:_Using_manifests

Oh
Hugo-PT said:
a little help.
http://wiki.cyanogenmod.org/w/Doc:_Using_manifests
Click to expand...
Click to collapse
Well to be honest, i dont really know how to share the menifest because i didn't use much the source. I was porting the Cm11 tonyp's rom and the rom from timduru, so i dont really know how to share the manifest lol

TheMysteryouse said:
Well to be honest, i dont really know how to share the menifest because i didn't use much the source. I was porting the Cm11 tonyp's rom and the rom from timduru, so i dont really know how to share the manifest lol
Click to expand...
Click to collapse
Did you change some files in the zips or did you build a new rom in the way Raum described, my friend?
http://forum.xda-developers.com/nexus-4/general/guide-cm11-how-to-build-cyanogenmod-11-t2515305

nope
gucky01 said:
Did you change some files in the zips or did you build a new rom in the way Raum described, my friend?
http://forum.xda-developers.com/nexus-4/general/guide-cm11-how-to-build-cyanogenmod-11-t2515305
Click to expand...
Click to collapse
nope, didn't touch anything other than the updater script i think and the build prop because i wanted fully stock experience

I can be your tester my phone got a battery problem so im having fun with flashing roms

I will try to exchange the updater script from my build with yours.
Lets see if I can flash mine.
And your your problem: I think there are one or more patches that we maybe need, witch timduru wont need because of the tegra3 hardware. (maybe some patch for our old egl hardware)

DJNoXD said:
I will try to exchange the updater script from my build with yours.
Lets see if I can flash mine.
And your your problem: I think there are one or more patches that we maybe need, witch timduru wont need because of the tegra3 hardware. (maybe some patch for our old egl hardware)
Click to expand...
Click to collapse
Well, it might be that he used KatKiss from timduru for the TF101 which has a Tegra 2, but still our phone uses the Tegra 2 AP20H, while the TF101 uses Tegra 2 T20. Small difference in the chipset, but still a difference. Easiest would be to port from the Galaxy R or Captivate Glide, but they too struggle with Lollipop over in their forum. Anyway, TheMysteryouse used timduru's AOSP rom, so maybe it would be easier building the whole thing from the demo CM12 sources available.

nonono
DJNoXD said:
I will try to exchange the updater script from my build with yours.
Lets see if I can flash mine.
And your your problem: I think there are one or more patches that we maybe need, witch timduru wont need because of the tegra3 hardware. (maybe some patch for our old egl hardware)
Click to expand...
Click to collapse
Nope, this rom has NOTHING to do with the tegra 3 rom.I used the rom for TF101 tablet which is tegra 2 but had a cmall chipset difference.So yeah I am still trying to do some things like searching the framework sources from tony to see if he has a code in the build.prop which directly enables ADB from the boot, but cant really find it.Anyways try your best and so the others.Cheers

Hi guys, after some testings I could get booting to finish. There are some errors left. But I will work further this evening and upload the rom afterwards. Think this will remain a test build for some time, till Tony or DJ can fix the errors.
Stay tuned!

Any video or screenshot? xD
Sorry for nob request, but working well or not, its great to our comunity
p.s. if need tester in future, you, TheMysteryouse or DJNoXD.
Im ready for

...WoW!...That´s Good News...Thank You for All of You, Guy´s...

gucky01 said:
Hi guys, after some testings I could get booting to finish. There are some errors left. But I will work further this evening and upload the rom afterwards. Think this will remain a test build for some time, till Tony or DJ can fix the errors.
Stay tuned!
Click to expand...
Click to collapse
Awesome news buddy! Lollipop on first power dual core android device! Switch to 1+ One as a primary phone for some reason but I will continue to follow and supporto you!

That is great!!! ))))))))

Ok. I have to go one step back. The rom is not ready for the testers and I'm too tired to test more. For those, who want to repeat my steps or want to finish...
I replaced the files in Mystery's rom with my own Kitkat ones. The first half, than the second. Now I could get it to finish the booting process. This steps I went on and on. So I could reduce the problem to the framework-files in "system". If you replace all of them, it boots up with some error messages.
I think we have to reduce the 40 files inside more and more to find the reason for the bootloop.
All the best to you,my friends!

Damm this is great a device from 2010 receives android L. 4years later. If I can borrow the old optimus 2x from my father then I could also look into the problems if it's not booting yet then. Till then continue your work.