Related
Don't use this rom due to random bootloop .
Hi all here the latest aokp milestone rc2 based on the latest unoficial cm9 rom BY Erwin.P
It's aokp milestone 6. version 4.0.4
Enjoy the aokp rom
The defauct lanchet is nova i think is the fastest but you can always use apex lancher or other ics one.
Detail:
Ics interface.Cm9 theme chooser, aokp setting and more will come.
What need to be fix :
Aokp stock live wallaper .But it's all and all cm9 bug.
Download:
https://docs.google.com/open?id=0B-5I_FmNMNolX0JpdEVFX2NIZG8
WARNING:
Before to install you have to delete 77tweaks in System/etc /init d
Credit:
Erwin.p
Aokp developer for wildfire.
Cyanogenmod team
can't download
Hello Pator57,
First I want to express my intentions with this post: I'm VERY glad that you have started to work on these ROM ports, and I'm only willing to help ya so that you can contribute more and more for the wildfire.
For me, a ROM presenting shouldn't be done in this way. First , lets start with the thread name-you should specify what actually is in this thread, is it a port/mod/build-from-source/etc, not only 'aokp update' for example, you should specify a date/version of the specific ROM , so that the users can keep an eye on the ROM since its almost certain that it will have some bugs , that should be fixed in new versions.
Later, in the thread its good not only to explain how and what you did it, but to put screen-shots/videos. To give details about the features,the ROM base and from where did you ported it, about the performance and some glitches. Plus that don't forget to include some disclaimer, so that you are not taking any responsibility for bricked phones, earthquakes or anything else. There can always be someone to point at you and claim that you bricked his precious phone. Detailed credits are also good to write, but you have made it so its OK.
Moreover,the actual zip of the ROM. Its not cool to name it 'aokp.zip' or 'miuiv4.zip'. I again think that including date/version is good, because when you make 3-4 different zips with bug fixes for example, personally i love to store more than a one version of the ROM I use and with these names it wouldn't be practical.
Of course one can rename it himself , or try the ROM to find out whats in,but(I think) these small suggestion would make you look more professional and reliable, just the way a developer/porter should look. This will give me personally convince in you, and that the things you do wont harm my phone. I hope noone will feel offended in any way. My intention as I said is only to help you, so that we can have one more ROM "producer" here. All what I wrote are personal views on how the things are done around here, its your choice whether to follow them!
Vency77 said:
Hello Pator57,
First I want to express my intentions with this post: I'm VERY glad that you have started to work on these ROM ports, and I'm only willing to help ya so that you can contribute more and more for the wildfire.
For me, a ROM presenting shouldn't be done in this way. First , lets start with the thread name-you should specify what actually is in this thread, is it a port/mod/build-from-source/etc, not only 'aokp update' for example, you should specify a date/version of the specific ROM , so that the users can keep an eye on the ROM since its almost certain that it will have some bugs , that should be fixed in new versions.
Later, in the thread its good not only to explain how and what you did it, but to put screen-shots/videos. To give details about the features,the ROM base and from where did you ported it, about the performance and some glitches. Plus that don't forget to include some disclaimer, so that you are not taking any responsibility for bricked phones, earthquakes or anything else. There can always be someone to point at you and claim that you bricked his precious phone. Detailed credits are also good to write, but you have made it so its OK.
Moreover,the actual zip of the ROM. Its not cool to name it 'aokp.zip' or 'miuiv4.zip'. I again think that including date/version is good, because when you make 3-4 different zips with bug fixes for example, personally i love to store more than a one version of the ROM I use and with these names it wouldn't be practical.
Of course one can rename it himself , or try the ROM to find out whats in,but(I think) these small suggestion would make you look more professional and reliable, just the way a developer/porter should look. This will give me personally convince in you, and that the things you do wont harm my phone. I hope noone will feel offended in any way. My intention as I said is only to help you, so that we can have one more ROM "producer" here. All what I wrote are personal views on how the things are done around here, its your choice whether to follow them!
Click to expand...
Click to collapse
It's the same port as tamahal port but based on the latest cm9 09/20 rom.But exept that and some tweaks it's exactly the same rom.
Sent from my HTC Wildfire using xda premium
ROM dont work, enter pin code and always boot screen
Fulfen said:
ROM dont work, enter pin code and always boot screen
Click to expand...
Click to collapse
Ho too bad.Flash this fix and it should work now.
OT: dafuq, what is this updater-script for a simple build.prop replace
Vency77 said:
OT: dafuq, what is this updater-script for a simple build.prop replace
Click to expand...
Click to collapse
Yea i change it but before i have testing the rom without the build prop change and all was working well.So come back to the stock build prop of cm9.IF it still doesn't work i will try again a new port this week end
now just htc logo... so still fail
Strange it was working well for me..But do you make an factory reset, wipe data, wipe dalvik cache,wipe cache partition before flashing ?
Ok but if the rom still doesn't work i will deleted the thread.
Sent from my HTC Wildfire using xda premium
I'm going to backup my current CM9 setup and try this out? What device did you port from?
Sent from my Wildfire using Tapatalk 2
It's not an port it's an uptate of the other aokp rom by thathanmal66.
Sent from my HTC Wildfire using xda premium
im biting my tongue here lol
R.V.3 (MokeeOs)
Pator57 said:
Strange it was working well for me..But do you make an factory reset, wipe data, wipe dalvik cache,wipe cache partition before flashing ?
Ok but if the rom still doesn't work i will deleted the thread.
Sent from my HTC Wildfire using xda premium
Click to expand...
Click to collapse
yes i have wildfire for 2 years i know how to flash rom, i did all those things.
Looks like i am having some great fun here
Sent from Hell!!
Pator57 said:
It's not an port it's an uptate of the other aokp rom by thathanmal66.
Sent from my HTC Wildfire using xda premium
Click to expand...
Click to collapse
I'm sure it shouldn't be called like this,because its a whole-ROM zip , and you tell that we should wipe everything when installing it,but whatever.Since its an 'update' of tathanhlam66's ROM , why do you make a whole new thread and not just continue what tathanhlam66 started ?
EDIT: Plus that , you have not edited both threads as I suggested you, which is making them BOTH look just funny. If you are not serious , and constantly state 'This is an update...blqblq', they will continue to look funny and futile!
and i hope you got permission to post and uptate his work?
R.V.3 (MokeeOs)
slymobi said:
and i hope you got permission to post and uptate his work?
R.V.3 (MokeeOs)
Click to expand...
Click to collapse
...and to play scrabble with his name
As on the MIUI thread, is it possible to provide some more details on that? Screenshots, bug list?
It's quite tricky to flash a ROM without knowing the results..
There are no bug but if im wrong tell me like my miui port.But it report to doesn't boot so i will try to make it boot next weekend.And i don't need to ask permision aokp it's like miui it's an open software and no need screenshoot the rom it's an ics rom but only with some aokp option tweaks
Sent from my HTC Wildfire using xda premium
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
reported it to be deleted.
wait till tomorrow for my new personal build
Will complete it later on.
Will complete it later on.
wuut?
This is yours CM7 or based on CM7 bieltv?
Alucard1989pl said:
This is yours CM7 or based on CM7 bieltv?
Click to expand...
Click to collapse
Yep my cm7 built from source
The device trees are by biel which I am working on.
downloading .... report in half an hour ...!
EDIT: Sbrick too, trying with hell lock now...
Phone has soft brick by kernel in your cm7 rom . . . system data and cache must be formated to ext4?
Alucard1989pl said:
Phone has soft brick by kernel in your cm7 rom . . . system data and cache must be formated to ext4?
Click to expand...
Click to collapse
use hells fusion from the other thread..
I already use hells fusion kernel but when i installed your cm7 my phone stuck on splash screen and led for 1 sec turn on.
Alucard1989pl said:
I already use hells fusion kernel but when i installed your cm7 my phone stuck on splash screen and led for 1 sec turn on.
Click to expand...
Click to collapse
logcat? its really weird cuz it worked for someone else..
what instructions did u use?
prototype-U said:
use hells fusion from the other thread..
Click to expand...
Click to collapse
Please include your kernel in this thread to make it clearer
You have to use this updater-script for flash cm7. If you don't use this one, the phone will get bricked. http://pastebin.com/htJ8NYTs
For use this updater-script you have to put in the first root of the zip two files: bmlunlock and busybox.
Remember to add the boot.img of hells fusion kernel at second post!
P.S. OP I think that you have to give credits to biel!
Soft Brick. Tried with hell lock flashable zip, softbrick with flashlight with 2 seconds. Now tried with the kernel you provided, stuck on the SGAi bootlogo. Any solution? You said it worked on someone else's device... How did he install? From stock or another rom?
EDIT: Now will try with the updater script you said, @Lopicl.00 . What attachment are you talking about?
mathm2013 said:
Soft Brick. Tried with hell lock flashable zip, softbrick with flashlight with 2 seconds. Now tried with the kernel you provided, stuck on the SGAi bootlogo. Any solution? You said it worked on someone else's device... How did he install? From stock or another rom?
Click to expand...
Click to collapse
Follow my post!
bricked the device while trying to install this rom, i had the kernel from your threat
Angryace said:
bricked the device while trying to install this rom, i had the kernel from your threat
Click to expand...
Click to collapse
Threat is something that puts you in danger
Well, I don't know which is the point of this thread. You are building my sources. You are making my ROM. Why create another thread? You don't have the device, me neither, but I started that project from 0. Why instead of making your CM7 you don't help us? Why don't you make a pull request? Do we need to talk with testers, which are the same for the both of us, to just test the same ROM!? If we want to have something big, we should focus on one CM and not building various CM7. I don't know which is the point of this, and I don't know what were you thinking. In your github there is 0 changes on my device tree. I committed all my changes during the last month and you used my work to build your own, and then it seems that your ROM is better than mine, because I don't release mid-done ROM's. I want to give the best expierence to all the users.
Also, I committed all the changes to help people understand on what I'm working. Many users asked me if I was really working on it, as I did not commit anything to github, but I was. And what happens if I commit? other users use my work to build their ROM's? I think that's not the way to go.
And what about a simple credit to the real author of this ROM? as your signature says: Send me device tree and I'll build the ROM. Why? To be more famous using other people's work? I don't get the point of anything here...
Oh, btw, where are the permissions to do that?
Thanks, Biel.
bieltv.3 said:
Well, I don't know which is the point of this thread. You are building my sources. You are making my ROM. Why create another thread? You don't have the device, me neither, but I started that project from 0. Why instead of making your CM7 you don't help us? Why don't you make a pull request? Do we need to talk with testers, which are the same for the both of us, to just test the same ROM!? If we want to have something big, we should focus on one CM and not building various CM7. I don't know which is the point of this, and I don't know what were you thinking. In your github there is 0 changes on my device tree. I committed all my changes during the last month and you used my work to build your own, and then it seems that your ROM is better than mine, because I don't release mid-done ROM's. I want to give the best expierence to all the users.
Also, I committed all the changes to help people understand on what I'm working. Many users asked me if I was really working on it, as I did not commit anything to github, but I was. And what happens if I commit? other users use my work to build their ROM's? I think that's not the way to go.
And what about a simple credit to the real author of this ROM? as your signature says: Send me device tree and I'll build the ROM. Why? To be more famous using other people's work? I don't get the point of anything here...
Click to expand...
Click to collapse
Ok I am also starting the device tree from scratch. Is that alright?
I will suspend the current build and post a new one tomorrow which will based on my device trees.
About credits? I didnt even complete writing this thread..
About changes thing? I have made changes at my end which are not committed becuz I dont wanna put untested changes on github.
Sorry If I offended someone but I had no real intentions of doing that..
and btw.. I mean somehting else from my sign.. I want to help other device owners to get new roms to their device. Though it contradicts to this build.
i successflly ported it i will upload the rom 15hours from now
but people should help me get the rom booting becasue it is stucked at boot logo im new at roms please cooperate ill give full credits to people who helps :angel::angel:
THANK YOU!!! That's amazing!!
it will never gonna work
diffrent hardware
no compatible kernel
its not a port yet, since its not booting m8 :/
Verstuurd van mijn SM-G900F
safariking said:
it will never gonna work
diffrent hardware
no compatible kernel
Click to expand...
Click to collapse
You never know, it could.
hey
i dont know thats why im asking for help
i will upload this yet
i will upload this but i need to ask permission from gr8nole cause im using his nolekat for base rom
Congrats on getting a stock ROM partially working! Safariking, I think you should support this newbie and not just say it won't work. How did you think we got custom ROMs?
aaronjasper49 said:
i successflly ported it i will upload the rom 15hours from now
but people should help me get the rom booting becasue it is stucked at boot logo im new at roms please cooperate ill give full credits to people who helps :angel::angel:
Click to expand...
Click to collapse
Well my advice is get use to logcats(google troubleshooting them, maybe even research a few ported manifactured roms to different devices and kernel porting will also be a big part of a build like this) , if you can get it to a working state these areas will be where most of the problems will be show whats conflicting, But without a kernel built/ported for the rom and hardware confliction issues your gonna have issues logcat may not be able to solve. Its not impossible but its far from easy porting from a different manifactured device but it does happen, htc roms have been brought to samsung for a few devices tho very few if any ever 100% function and it can be very time consuming for even a pro builder. would be nice for a custom factory rom from another branded device on our device!. I i wish you luck and will keep my fingers crossed and will check it out once its posted :good:
Lincoln99 said:
You never know, it could.
Click to expand...
Click to collapse
I do know, it won't
Different screens, different SOCs, different everything. There is no way to get fully working. Ever.
LoopingCreeper said:
Congrats on getting a stock ROM partially working! Safariking, I think you should support this newbie and not just say it won't work. How did you think we got custom ROMs?
Click to expand...
Click to collapse
You are talking about 2 completely different things here. Our custom Roms are stock based with some modifications. These are no ports.
Sent from my SM-T210 using XDA Premium 4 mobile app
Mm... I see what you mean.
Still, we could get a Nexus 7-like Lollipop ROM when Cyanogen releases CyanogenMod12. Or 13. Cannot remember.. :silly:
btw using a Touchwiz based rom to port a AOSP rom is completely useless that will never ever boot.
if you port something do it from a similair device with the same hardware and uif you port aosp you need a aosp base! if you port a touchwiz based rom use a touchwiz based rom Easy!
Mate not to crush your dream or effort but what the other devs are tell you if true including my self. Educated your self more, all the tutorials and guides regarding porting, building custom rom and more can be find on xda.
As for Lollipop we would have to wait till a compatible / similar device has it before it can be ported.
On that note hope that clear up some stuff for you and understand things better.
So the galaxy tab 2 has official support from cyanogenmod which I think it will be getting cm 12 which the device hardware and specs are not much different someone can port that over to our tab 3.
Or if the tab 4 gets official Samsung android l update you devs can port it to our tab 3??
aaronjasper49 said:
i successflly ported it i will upload the rom 15hours from now
but people should help me get the rom booting becasue it is stucked at boot logo im new at roms please cooperate ill give full credits to people who helps :angel::angel:
Click to expand...
Click to collapse
Did you replace the nexus 7 libs with the tab 3 7.0 libs? Found in /system/lib
DevMyAndroid said:
Did you replace the nexus 7 libs with the tab 3 7.0 libs? Found in /system/lib
Click to expand...
Click to collapse
i forgot but i will look at the rom if i did
and i wont flash it because i dont have a data cable to reflash the stock rom i will probably start working on december
aaronjasper49 said:
i forgot but i will look at the rom if i did
and i wont flash it because i dont have a data cable to reflash the stock rom i will probably start working on december
Click to expand...
Click to collapse
Upload the rom so i can check/replace the lib files
The only ROM that varies from stock is gr8nole's CM11 ROM. All other are touchwiz
If we had a stable CM ROM i feel this device would be very smooth and probably run some high end games smoothly
DevMyAndroid said:
Upload the rom so i can check/replace the lib files
Click to expand...
Click to collapse
ok i will edit this if can upload it
i dont think you need Gr8noles permission. just credit him in op for base rom.
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.