Database Develop

[INT/Bell][CWM]Auto Ram Fixer for unlocked bootloader

Hi,
This is a small CWM zip to add the [email protected] line to your existing boot and recovery partitions to fix the ram issue with the international unlocked bootloader. If the second mem is already there it does nothing.
The point of this is you can have a regular recovery flashed and fix the ram issue without wondering what tegra part you have, it preserves your serial number as well. More useful with stock boot images than custom ones that already have this done.
To use:
Flash with a CWM recovery supporting edify scripting. That means you have an unlocked recovery basically.The program inside the zip can be used on it's own to list the cmdlines already in your phone, or to set them to something else.
As cmdline, it lists, as setcmdline it sets the entire thing, as addcmdline it adds on to the end of the existing cmdline.​Cheers!

Great! Looks like our bell friends are having good development as well.
Sent from my MB860 using XDA Premium App

NF, cheers bro I really appreciate the work from you.
Sent from my MB860 using XDA Premium App

So would i need to flash this once and then any ROM I install will have fixed RAM, or do I need to flash this after every installation?

IUH1991 said:
So would i need to flash this once and then any ROM I install will have fixed RAM, or do I need to flash this after every installation?
Click to expand...
Click to collapse
You can just keep it handy on your sdcard and use when needed, it depends on the "rom" you flash, it may or may not have a ram fix solution built in.
Cheers!

J-Roc said:
NF, cheers bro I really appreciate the work from you.
Sent from my MB860 using XDA Premium App
Click to expand...
Click to collapse
You're welcome.
Cheers!

NFHimself said:
You can just keep it handy on your sdcard and use when needed, it depends on the "rom" you flash, it may or may not have a ram fix solution built in.
Cheers!
Click to expand...
Click to collapse
It depends on the Kernel the Rom has within it, nothing else.
Furthermore, no offense. But this is kinda useless now. Did you not know we have unified Kernel's? If someone made a Rom without a unified kernel, they can basically shove that Rom.
I do not see a point in this at all. I guess maybe for testing old Roms.....

NFHimself said:
You can just keep it handy on your sdcard and use when needed, it depends on the "rom" you flash, it may or may not have a ram fix solution built in.
Cheers!
Click to expand...
Click to collapse
So solid man, keep up the good work!

nexxusty said:
It depends on the Kernel the Rom has within it, nothing else.
Furthermore, no offense. But this is kinda useless now. Did you not know we have unified Kernel's? If someone made a Rom without a unified kernel, they can basically shove that Rom.
I do not see a point in this at all. I guess maybe for testing old Roms.....
Click to expand...
Click to collapse
Hi,
I addressed this already in the OP. It's more for use with stock kernels.
Can you compile the motorola kernel source (pick one) and get a binary exact match for the stock Bell kernel?
No offense to the guys working on kernel's here, but I am not really compelled by the added features/bug fixes, and am concerned more about stability, especially when the source seems to be ATT based. Which is fine if you are running an ATT framework "rom/theme" I guess, even better if you have an ATT phone.
Cheers!

NFHimself said:
Hi,
This is a small CWM zip to add the [email protected] line to your existing boot and recovery partitions to fix the ram issue with the international unlocked bootloader. If the second mem is already there it does nothing.
The point of this is you can have a regular recovery flashed and fix the ram issue without wondering what tegra part you have, it preserves your serial number as well. More useful with stock boot images than custom ones that already have this done.
To use:
Flash with a CWM recovery supporting edify scripting. That means you have an unlocked recovery basically.The program inside the zip can be used on it's own to list the cmdlines already in your phone, or to set them to something else.
As cmdline, it lists, as setcmdline it sets the entire thing, as addcmdline it adds on to the end of the existing cmdline.​Cheers!
Click to expand...
Click to collapse
Hi is this fix for when i flash IHOP and get ram problem it fix that or its universal for every kernel (Gb froyo ROMs etc) ?

so does this mean it is actually possible to download more ram??

xateeq said:
Hi is this fix for when i flash IHOP and get ram problem it fix that or its universal for every kernel (Gb froyo ROMs etc) ?
Click to expand...
Click to collapse
Yes, what you said.
Cheers!

geishroy said:
so does this mean it is actually possible to download more ram??
Click to expand...
Click to collapse
Uhm, what?
Cheers!

geishroy said:
so does this mean it is actually possible to download more ram??
Click to expand...
Click to collapse
Download more RAM? Umm...did you even read this before you posted it? or do you know absolutely nothing about what RAM is?

geishroy said:
so does this mean it is actually possible to download more ram??
Click to expand...
Click to collapse
So many people don't understand what Ram actually is *sigh*
You're not the first, I see it EVERYWHERE, google it up!

Thanks a lot, because i was having ram issue with eternity project kernel, and your patch solve it !
Sent from my MB860 using XDA App

dnsdenis said:
Thanks a lot, because i was having ram issue with eternity project kernel, and your patch solve it !
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
Glad it worked out!
Cheers!

System Ram lists 816 total, so I should be in the clear or should I apply it anyways? Is there not a gig of ram on this thing or is some gpu/frame buffer dedicated?

drolgnir said:
System Ram lists 816 total, so I should be in the clear or should I apply it anyways? Is there not a gig of ram on this thing or is some gpu/frame buffer dedicated?
Click to expand...
Click to collapse
You are in the clear.
Cheers!

So, if I understand this correctly, when I flash this it will auto-fix any ROM, kernel or custom recovery that I install?

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.

[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

Can I take cm10.1's 07/07 kernel and flash it via CWM?

I heard that cm10.1's 07/07 kernel has no whitescreens. I am using a newer version of cm10.1 . Can I flash 07/07 kernel on its own via CWM? If yes, how can I make it flashable? Thanks in advance.

G i said:
I heard that cm10.1's 07/07 kernel has no whitescreens. I am using a newer version of cm10.1 . Can I flash 07/07 kernel on its own via CWM? If yes, how can I make it flashable? Thanks in advance.
Click to expand...
Click to collapse
here is the flashable kernel

ahmedadd said:
here is the flashable kernel
Click to expand...
Click to collapse
Dayyyum. That was fast. Thank you so much buddy. Any idea why Wifi isn't working?
EDIT: I turned off Wifi optomization, but still I can't enable wifi. Can you tell me the process to flash the kernel over my ROM? Maybe i did something wrong.

G i said:
Dayyyum. That was fast. Thank you so much buddy. Any idea why Wifi isn't working?
EDIT: I turned off Wifi optomization, but still I can't enable wifi. Can you tell me the process to flash the kernel over my ROM? Maybe i did something wrong.
Click to expand...
Click to collapse
no you did not make any wrongs to use 7-7 kernel the wi-fi wont work at all.

ahmedadd said:
no you did not make any wrongs to use 7-7 kernel the wi-fi wont work at all.
Click to expand...
Click to collapse
ffs this phone. everytime something's broken. at first the whitescreens, then the sdcard mount problem, now wifi is disabled...god pls!

you flash an old kernel/ramdisk and wonder why Wi-Fi isn't working... it's just...

TheWhisp said:
you flash an old kernel/ramdisk and wonder why Wi-Fi isn't working... it's just...
Click to expand...
Click to collapse
I mean, there should be a stable ROM with everything working. Maybe not the latest release but it would be stable. I know all ROMs are stable for your phone since you don't have WS or mount problem, but there's no rom for my phone that won't malfunction.

I am not your employee if you haven't noticed yet.

TheWhisp said:
I am not your employee if you haven't noticed yet.
Click to expand...
Click to collapse
Holy **** dude, your attitude. Everybody in this forum loves you cuz you're the only developer this ****ty phone has but you keep acting like a douche, throwing a tandrum to whoever dares to mention WS or sd card mount problem or even something that has been stated before. We are noobs, we're trying to learn, this place's like a school to us. XDA ain't your own business, we're members of XDA as well. Did I even ask you to do something for me? Did I even post to your github or anything like this? No, cuz I know that douchebags like you better leave 'em alone.

but there's no rom for my phone that won't malfunction.
Click to expand...
Click to collapse
Sorry, but you have clearly misunderstood the whole point of XDA. Most of the developers here (including me) do this as a hobby. I make this ROM for myself and then I share with anyone else. I am not going to do something, in this case fix bugs I have never experienced nor can reproduce, just because something is not working on your device. Douches are people who constantly spam and whine about things. Use GB and be happy.

TheWhisp said:
Sorry, but you have clearly misunderstood the whole point of XDA. Most of the developers here (including me) do this as a hobby. I make this ROM for myself and then I share with anyone else. I am not going to do something, in this case fix bugs I have never experienced nor can reproduce, just because something is not working on your device. Douches are people who constantly spam and whine about things. Use GB and be happy.
Click to expand...
Click to collapse
Ok kiddo

You know, you should really take a chill pill....TheWisp is trying to do something for free here..i don't think you really understand the "free" part...myself, i couldn't spare the time to learn to develop for Android, much less fix bugs and try to create a stable rom without up-to-date blobs ( which by the way is really harder than simply porting cm to a certain device which already has jb or a variation of it)...if you really want something 100% stable go for stock (tough good luck with random crashes)..if you want something 97% stable go for cm10 or cm10.1 (i find 30/06/2013 cm10.1 to be one of the smoothest and stable of all the cm10.1 builds), and if you want something 95% stable go for cm11(the one i have right now)...you should really stop complaining, and instead of being part of the problem, start learning to develop and be a part of the solution (if developing is for you). Peace!

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.