Database Develop

Cyanogen Mod?

I did a search here and didn't see any info on this...
Now that ROMs are being rolled out, will we be seeing a Cyanogen Mod? I ran it on my G1, Mytouch Slide, G2, and need some Cyanogen loving for my D3...
Is he waiting for the unlocked bootloader?

Code3VW said:
I did a search here and didn't see any info on this...
Now that ROMs are being rolled out, will we be seeing a Cyanogen Mod? I ran it on my G1, Mytouch Slide, G2, and need some Cyanogen loving for my D3...
Is he waiting for the unlocked bootloader?
Click to expand...
Click to collapse
Apparently they're working on it
http://www.youtube.com/watch?v=FrzPSLIJyiQ&feature=player_embedded

Be patient. CyanogenMod is a source built ROM, it's compiled from source and the source code is a mix of AOSP from Google/Android and the CyanogenMod Team's own programming. Hashcode has been working very hard on getting the source ported so that it will compile and run on the Droid 3. He's also working on making it work in a "sandbox" area so as not to affect the stock ROM (easy to switch back and forth between the two).
All the current ROMs for the Droid 3 are modified stock ROMs. Some theme changes, app deletions/additions, a few build.prop edits, etc...

tcrews said:
Be patient. CyanogenMod is a source built ROM, it's compiled from source and the source code is a mix of AOSP from Google/Android and the CyanogenMod Team's own programming. Hashcode has been working very hard on getting the source ported so that it will compile and run on the Droid 3. He's also working on making it work in a "sandbox" area so as not to affect the stock ROM (easy to switch back and forth between the two).
All the current ROMs for the Droid 3 are modified stock ROMs. Some theme changes, app deletions/additions, a few build.prop edits, etc...
Click to expand...
Click to collapse
I am not that well versed on CyanoGen... I started off with a D2, and the flexribbon broke before I was able to see the dawn of custom kernels. Is cyanogen truly a custom kernel? If so, I assume we're trying to hijack the boot process to load dual kernels?

librarat said:
I am not that well versed on CyanoGen... I started off with a D2, and the flexribbon broke before I was able to see the dawn of custom kernels. Is cyanogen truly a custom kernel? If so, I assume we're trying to hijack the boot process to load dual kernels?
Click to expand...
Click to collapse
CyanogenMod on locked bootloaders hijacks the init process and runs on top of the stock kernel. No kernel replacement on locked bootloader phones.

Yyup, that's what I thought.
Also, according to Hashcode0f, well be seeing a CM7 beta in the very, very near future. He's going to be writing a dossier up on it shortly.
Source: his twitter feed.
Sent from my DROID3 using XDA App

Downloading!

Even though it has a bootloader, that doesn't mean the development cannot take place. Why not develop now so when the bootloader gets unlocked, you will already have a pretty descent ROM to flash on!

http://hash-of-codes.blogspot.com/
CM7 Alpha release here... read carefully, radio still doesn't work.

Androidsims said:
http://hash-of-codes.blogspot.com/
CM7 Alpha release here... read carefully, radio still doesn't work.
Click to expand...
Click to collapse
Technically the radio works (3G data), but the phone app crashes due to an audio codec issue I'm looking at.
But be careful anyway.

Hashcode said:
Technically the radio works (3G data), but the phone app crashes due to an audio codec issue I'm looking at.
But be careful anyway.
Click to expand...
Click to collapse
****, that's functional in my book. Who calls people nowadays?
Sent from my DROID3 using xda premium

mothman57 said:
Even though it has a bootloader, that doesn't mean the development cannot take place. Why not develop now so when the bootloader gets unlocked, you will already have a pretty descent ROM to flash on!
Click to expand...
Click to collapse
Honestly, I don't believe the bootloader will ever be unlocked. It will have to be unlocked by Motorola and I just do not believe that they ever will.
So developing ROMs (from source) will require using the 2nd-init process CM7 is using to boot the "new" OS on top of the stock kernel. Kernel will remain stock.......

Did you forget who bought motorola? Google! And google supports devs. Like all the unlocked nexus phones! It will be released sooner or later! Have hopes!
Sent from my DROID3 using XDA App

mothman57 said:
Did you forget who bought motorola? Google! And google supports devs. Like all the unlocked nexus phones! It will be released sooner or later! Have hopes!
Sent from my DROID3 using XDA App
Click to expand...
Click to collapse
If the acquisition passes through (which likely won't be soon).. word is Google bought them more for patents than for anything else. If we're lucky, Google might make sure future phones are unlocked. However I highly doubt Google will do anything about phones already released.

Plus Moto said they would release an update to unlock the bootloaders where carrier approved. The other variations of the droid 3 may get unlocked, but I doubt big red will give their approval for unlocking the droid 3.

Find devs for 2nd boot cm10 romw

i had a motorola defy with locked bootloader. There were no hope for updates and for custom roms. Till dev (quarx) did it. Now defy has jelly bean (cm10). Lets search for devs and make a donation app, so they can buy our phone add develop one great rom.

Great idea, but do we have enough people? No one will buy the phone if we can donate only ~100€

well, not to develop ROM, but better to sacrifice their/his phone to try unlocking bootloader..
http://www.lg.com/global/support/opensource/opensource-detail.jsp?detailCustomerModelCode=LGP880
we've now source code, i think it'll help us

reas0n said:
well, not to develop ROM, but better to sacrifice their/his phone to try unlocking bootloader..
http://www.lg.com/global/support/opensource/opensource-detail.jsp?detailCustomerModelCode=LGP880
we've now source code, i think it'll help us
Click to expand...
Click to collapse
Yes it will...well at least for a custom kernel i think. Still, drivers have to come from Nvidia. And everyone knows about their reputation when it comes providing open source codes and such.

ukramch said:
i had a motorola defy with locked bootloader. There were no hope for updates and for custom roms. Till dev (quarx) did it. Now defy has jelly bean (cm10). Lets search for devs and make a donation app, so they can buy our phone add develop one great rom.
Click to expand...
Click to collapse
incorrect, i made the Sense custom for Defy way before even CM9 was invented, but correct 2nd-init was working already then and no none really spend much investigating how to use it early on, but that was probably 1yr+ ago.

Dexter_nlb said:
incorrect, i made the Sense custom for Defy way before even CM9 was invented, but correct 2nd-init was working already then and no none really spend much investigating how to use it early on, but that was probably 1yr+ ago.
Click to expand...
Click to collapse
Quarx was the first one who figured it out, how to 2nd boot the cm7 rom on defy. maybe he could give some tips for devs in our comminity.
PS: i can remember your rom

hietsu said:
Great idea, but do we have enough people? No one will buy the phone if we can donate only ~100€]
what do you think, how large is our community approximately?
Click to expand...
Click to collapse

ukramch said:
hietsu said:
Great idea, but do we have enough people? No one will buy the phone if we can donate only ~100€]
what do you think, how large is our community approximately?
Click to expand...
Click to collapse
We're definitely not that big. I'd say theres no more than 15-20 that uses this phone and that would be interested in develpment advancement
Click to expand...
Click to collapse

ukramch said:
Quarx was the first one who figured it out, how to 2nd boot the cm7 rom on defy. maybe he could give some tips for devs in our comminity.
PS: i can remember your rom
Click to expand...
Click to collapse
i did mine in feb.2011 , Quarx did his first post of cm7 in april 2011, i do not know if that helps your memory. (i did check all his post on the topic) . I strongely believe i was utilizing 2ndinit on defy on a customrom, and i was introducing it here on o4x for now.
but to stay on topic, no one seems to have faith in a CM10 for O4X here, i tried to port, but that never went well, and compiling only helps so far as the ril driver is documented by LG here.
but the rest should be straight forward, since we share chipset with OneX which got quite far now.
btw,
i did post my CM10 rom as nandroid backup using 2nd init , so your request is already existing on o4x, just not with a phone functionality.

Dexter_nlb said:
i did mine in feb.2011 , Quarx did his first post of cm7 in april 2011, i do not know if that helps your memory. (i did check all his post on the topic) . I strongely believe i was utilizing 2ndinit on defy on a customrom, and i was introducing it here on o4x for now.
but to stay on topic, no one seems to have faith in a CM10 for O4X here, i tried to port, but that never went well, and compiling only helps so far as the ril driver is documented by LG here.
but the rest should be straight forward, since we share chipset with OneX which got quite far now.
btw,
i did post my CM10 rom as nandroid backup using 2nd init , so your request is already existing on o4x, just not with a phone functionality.
Click to expand...
Click to collapse
Sorry, i had my defy since may 2011. then you are right. at the beginning there were also phone functionality problems, we shouldn't loose faith

babymatteo said:
Yes it will...well at least for a custom kernel i think. Still, drivers have to come from Nvidia. And everyone knows about their reputation when it comes providing open source codes and such.
Click to expand...
Click to collapse
I have downloaded the file and it is .zip file .. It has two files that are kernel and platform files >> Good news
Now, I can see all the files for our O4X and everything is clear . We can make modification for it and install it by CWM
I hope you guys all the best with development . The kernel file has the drivers for our O4X
Best regards,
---------- Post added at 11:16 AM ---------- Previous post was at 11:05 AM ----------
Please, look at the information of tegra 3 and open your eyes as much as you can at the official website
http://www.nvidia.co.uk/object/tegra-3-uk.html
Maybe you need it sooner or later ..
Best regards,

IMHO
As long as the kernel is not signed u cant really use it. i dont remember anyone using 2nd init on milestone for a custom kernel.
they actually just adapted CM for the old kernels wich is a lot of work i think... And that could be done for our 4xHD as well the problem is
actually that u need the devs for it.
And i think no dev really wants 2 work on a standart phone unless he has it and really wants to keep it and mod on it.

cm/pa building/discussion & plans.

hello all, I've just picked up a razr i as a temp standin while my xperia Z is away under warranty repair.
(it was cheap enough to keep too play with afterwards)
is there any reason why no-one has started on CM /PA yet? I've looked through all the posts and can't see anything remotely like a real custom rom..
I'm happy to start working on this (will probably leave it till my Z is back in use though), but would like to get a decent team together to work on it, rather than do it on my own, which is what I've done in the past for a few devices and burnt myself out!
if you're interested then let me know
DO NOT POST
Code:
+1
and me
or
let me beta test !
I want people with a more technical bent than a lot of the users on here to get involved.
for those people, is there anything I'm missing that would stop us building for this?
we have kernel source, and omars kernel looks fairly decent basepoint looking at his git, and some source from motorola that looks sloppily put together.
we can flash with fastboot, and even using blobs it doesn't look too arduous to get at least a 4.1 based build going, so am I missing something?
I'm pretty open on how I work, but I don't tolerate people demanding stuff, or expecting perfection, this will be a W.I.P for a very long time (especially if done on my own).

As far as i know, the problem is on intel processor libs... That's what i've read somewhere around here

Aosp and cm build with some modifications. The phone boots, but in a boot loop on my build. Haven't solved that and will not solve it I think. I have some skills in building, modifying and debugging, but not enough... To get it working. Give it a shot, we can help everyone to get past some certane problems we already solved.
Sent from my GT-P5110 using XDA Premium HD app

Hazou said:
Aosp and cm build with some modifications. The phone boots, but in a boot loop on my build. Haven't solved that and will not solve it I think. I have some skills in building, modifying and debugging, but not enough... To get it working. Give it a shot, we can help everyone to get past some certane problems we already solved.
Sent from my GT-P5110 using XDA Premium HD app
Click to expand...
Click to collapse
do you have a record of what you've already done (other than the github obviously)?
I couldn't find anything searching ..

anerik said:
As far as i know, the problem is on intel processor libs... That's what i've read somewhere around here
Click to expand...
Click to collapse
fards said:
hello all, I've just picked up a razr i as a temp standin while my xperia Z is away under warranty repair.
(it was cheap enough to keep too play with afterwards)
is there any reason why no-one has started on CM /PA yet? I've looked through all the posts and can't see anything remotely like a real custom rom..
I'm happy to start working on this (will probably leave it till my Z is back in use though), but would like to get a decent team together to work on it, rather than do it on my own, which is what I've done in the past for a few devices and burnt myself out!
if you're interested then let me know
DO NOT POST
Code:
+1
and me
or
let me beta test !
I want people with a more technical bent than a lot of the users on here to get involved.
for those people, is there anything I'm missing that would stop us building for this?
we have kernel source, and omars kernel looks fairly decent basepoint looking at his git, and some source from motorola that looks sloppily put together.
we can flash with fastboot, and even using blobs it doesn't look too arduous to get at least a 4.1 based build going, so am I missing something?
I'm pretty open on how I work, but I don't tolerate people demanding stuff, or expecting perfection, this will be a W.I.P for a very long time (especially if done on my own).
Click to expand...
Click to collapse
hello the problem is that no source AOSP (Cyanogen or AOKP) have x86 libraries and formats, visit www.androidx86.org
if you need a beta tester let me know
The app also must be compatible with x86

The problem I faced was that at the moment of booting it kept restarting netd -- which is odd seeing how the Kernel iptables/ipchains and net configuration is the same on Motorola's one. [info]
I even tried adding and compiling extra modules on the Kernel without much luck -- and it was not the typical ramdisk *.rc files fix here.

Hmm I presumed that with the amount of x86 development boards about there would be a load more work on bringing cm across.
I'll start to have a look at it in depth in the next couple of weeks.
Sent from my XT890 using Tapatalk 4 Beta

On my github I got some work and fixes. Not all of them though. Someone's aren't uploaded yet
Sent from my XT890 using xda app-developers app

Is it easyer to make miui v5?
RAZR i xt890 Tapatalk 2

choppertriker said:
Is it easyer to make miui v5?
RAZR i xt890 Tapatalk 2
Click to expand...
Click to collapse
Harder cause it's not only based on cm10 it's alto different port

For MiUi 4.0 there was the possibility to make a stock based Miui Rom,
There even was one for our Razr i, even though it wasn't very popular.
Is this possibility gone with v5 or is there any other reason not to?
greetings

Killigrew said:
For MiUi 4.0 there was the possibility to make a stock based Miui Rom,
There even was one for our Razr i, even though it wasn't very popular.
Is this possibility gone with v5 or is there any other reason not to?
greetings
Click to expand...
Click to collapse
v4 is different, cause all the porting guides are adapted for it, plus there's miuiv4.1 for razr which is easily portable i guess, but v5 is a whole different matter cause it's based on cm

I will be very happy if anyone port miui 4.1 for our razr, i used it before, on my old phone
If anybody dev could do it i think many ppl will be happy as i.
Wysyłane z mojego XT890 za pomocą Tapatalk 2

Oh yes! Please port miui to razr i. :thumbup:
RAZR i xt890 Tapatalk 2

Personally I will never touch muios with a bargepole
Sent from my GT-N8010 using Tapatalk HD

A real cm or pa build would be awesome! I hope you guys make my dreams come true

Any news fards?
Enviado desde mi XT890 usando Tapatalk 4 Beta

Nope sorry, not yet. been trying to get an aosp build booting from the Motorola code, but it's not happening with that yet. never mind any further progress
Sent from my C6603 using Tapatalk 4 Beta

fards said:
Nope sorry, not yet. been trying to get an aosp build booting from the Motorola code, but it's not happening with that yet. never mind any further progress
Sent from my C6603 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Dont worry bro, i have all my hope that one day we gonna have cm or pa
Enviado desde mi XT890 usando Tapatalk 4 Beta

I got Intel's AOSP Android (4.1.2) to build and then made some binary blob overlays on top. It show the Motorola animation logo on the Phone and then it starts flickering -- I have yet to plug adb to it, but I need to go to sleep soon.
Experimental File, adb enabled at boot: RazRi_AOSP_A001.zip [Flashes boot animation, this is using Motorola's *.prop files, which shouldn't be]
Experimental File, adb enabled at boot: RazRi_AOSP_A002.zip [Have not tried this one, this has safe cflags and default build.prop]
Source: https://github.com/oxavelar/android_device_motorola_intel_smi
Q: Anyone with two phones who knows what to experiment with? I put the instructions to build on the github readme at the moment.

C6903 - CyanogenMod 11 for Locked Bootloaders - Help needed!

Hello guys, I'm acquiring some info about how to build the CM11 to Honami with locked bootloader.
 @Olivier already did it to Xperia S and @letama said to me that MAYBE we can do the same to Z1.
I'm not a dev at all, but for sure I have some skill (I hope!).
So, I have to ask first, did anyone already tried it? Worked? Didn't work?
If anyone is willing to help, please, let me know.
---
Current status:
Repo sync

Impossible workout kexec, and that does not look promising. Is in the original development section.
Sent from my C6903 using XDA Premium 4 mobile app

gregbradley said:
Impossible workout kexec, and that does not look promising. Is in the original development section.
Sent from my C6903 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I will have a look into it, thanks to point it out!

gregbradley said:
Impossible workout kexec, and that does not look promising. Is in the original development section.
Click to expand...
Click to collapse
Well, this solution doesn't use kexec. It basically hijack stock firmware android boot to boot the alternate firmware but it's using stock kernel, that's why it can work with locked bootloaders. The only requirement is that cm or aosp should run on stock kernel and doesn't require a modified kernel. As you have kitkat on your device, there is a good chance that it does.

But it doesn't, that's why it does not work and a modified ramdisk (Hence modified kernel, hence unlocked bootloader) is needed
Hence kexec is needed, but that seems like a lost hope on Xperia Z devices

Nothink is imposible i hope

No, nothing is impossible, but there has to be enough effort spent on it.
Personally I don't think there will be as most devs got bootloaders which can be unlocked...hence they do not need kexec
In future its always preferable to check this before purchase

mabe don't need to unlock bootloader but workaround this - mabe multiboot or kexec will be more developed because more phone will released with LB and this is their new policy :/
gregbradley said:
No, nothing is impossible, but there has to be enough effort spent on it.
Personally I don't think there will be as most devs got bootloaders which can be unlocked...hence they do not need kexec
In future its always preferable to check this before purchase
Click to expand...
Click to collapse

gregbradley said:
But it doesn't, that's why it does not work and a modified ramdisk (Hence modified kernel, hence unlocked bootloader) is needed
Click to expand...
Click to collapse
Ramdisk is not a problem... When I say kernel, I mean zImage, not zImage+ramdisk: we extract cyanogen ramdisk in the boot hijack.
Kernel drivers combined to Android hal is what I meant and could cause problem depending on how Cyanogen was developed and how Cyanogen kernel source code is far from stock one. That's why we're usually stuck on Cyanogen with the same Android version.
Another solution is to hack Cyanogen code to support stock zImage. It's not for the faint of the heart, but it could be the only solution.

Greg's absolutely right, if your bootloader unlock allowed status is no or you're unwilling to unlock it then i'm afraid you're out of luck, i'm not saying it's impossible that just isn't true, but again as Greg's said this more than likely isn't going to happen as it would take some talented folk a lot of time to accomplish it, with the Z2 having been released and the vast majority of people able to unlock their bootloaders there is little call for someone to have a crack at it.
in all fairness though, the rom's that are available for locked bootloaders are pretty damn good and the launchers that you can install these days gives a near perfect android experience, you'll only be missing things like Halo and custom kernels along with a few mods and such that only appear to be available for cm based roms and the like.

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.