I have no experience compiling roms. I really like this rom and would like to use it on my phone. Is there a template, guide or something that can make porting this rom to my ZU GPE easy?
Also I've looked at some guides on how to port any rom to any device and on the lollipop build for the AICP builds there is no longer the folder for system with all the folders, instead there is a .dat file that holds all of that and I have no idea how to extract it.
It's easiest if @alia5 still has the source adapted for the Xperia - if so, he can just make a few changes to the GPe device tree and build it.
It is possible to port from Xperia to GPe, as shown by blueether here, but I don't know if it works well. I'd go for building it from source.
There's a good guide for building here, but you'll need to make some changes to the device trees for them to work with AICP. If alia5 is busy, I can probably do it for you, if you'd prefer.
Triflot said:
It's easiest if @alia5 still has the source adapted for the Xperia - if so, he can just make a few changes to the GPe device tree and build it.
It is possible to port from Xperia to GPe, as shown by blueether here, but I don't know if it works well. I'd go for building it from source.
There's a good guide for building here, but you'll need to make some changes to the device trees for them to work with AICP. If alia5 is busy, I can probably do it for you, if you'd prefer.
Click to expand...
Click to collapse
Thanks so much! It's funny you mentioned the thread @blueether created. I used the the AICP port @alia5 made and just flashed the togari2gpe mod and it worked so that's what i'm using now I see that the team for AICP have started development for Lollipop and have put out some nightly builds for other devices. I wanted to try to learn how to port the Lollipop to my GPE. I saw this guide http://anythingsyouneed.blogspot.com/2014/06/how-to-port-custom-rom-rom-porting.html and downloaded the CM12 rom for the GPE to use as my base and the nexus 5 AICP rom to use as the port but when I extracted both roms the system apps, framework, etc were in the form of .dat file. I searched to see how to extract the .dat files and I came up with nothing. So I guess in order to port the AICP(Lollipop) rom I would need to build it from source.....right? Also I would need to make some changes to the device tree to work with AICP?
Crickette said:
Thanks so much! It's funny you mentioned the thread @blueether created. I used the the AICP port @alia5 made and just flashed the togari2gpe mod and it worked so that's what i'm using now I see that the team for AICP have started development for Lollipop and have put out some nightly builds for other devices. I wanted to try to learn how to port the Lollipop to my GPE. I saw this guide http://anythingsyouneed.blogspot.com/2014/06/how-to-port-custom-rom-rom-porting.html and downloaded the CM12 rom for the GPE to use as my base and the nexus 5 AICP rom to use as the port but when I extracted both roms the system apps, framework, etc were in the form of .dat file. I searched to see how to extract the .dat files and I came up with nothing. So I guess in order to port the AICP(Lollipop) rom I would need to build it from source.....right? Also I would need to make some changes to the device tree to work with AICP?
Click to expand...
Click to collapse
I'm glad that that tool worked, I wrote that before I had access to a GPe.
Building for source is the best bet. Do they have a togari tree for lollipop? if they do build that and see if you can get it built without any errors then get the device/sony/togari and device/sony/togari_gpe from cm11 or 12 and compare to the aicp folder and work from there. If you want a hand with anything shoot me a pm or hangouts request
Crickette said:
Thanks so much! It's funny you mentioned the thread @blueether created. I used the the AICP port @alia5 made and just flashed the togari2gpe mod and it worked so that's what i'm using now I see that the team for AICP have started development for Lollipop and have put out some nightly builds for other devices. I wanted to try to learn how to port the Lollipop to my GPE. I saw this guide http://anythingsyouneed.blogspot.com/2014/06/how-to-port-custom-rom-rom-porting.html and downloaded the CM12 rom for the GPE to use as my base and the nexus 5 AICP rom to use as the port but when I extracted both roms the system apps, framework, etc were in the form of .dat file. I searched to see how to extract the .dat files and I came up with nothing. So I guess in order to port the AICP(Lollipop) rom I would need to build it from source.....right? Also I would need to make some changes to the device tree to work with AICP?
Click to expand...
Click to collapse
Glad that it worked!
Into lollipop i will look sooner or later, just a matter of time (pretty busy atm)
I don't have access to a gpe, but i can take a look wheni'll look at lollipop
Thanks so much guys for the help!! I greatly appreciate it I will try it myself and see what I can come up with. You guys are awesome! @alia5 @blueether @Triflot
Related
I'm trying to port this ROM from this git to the Desire HD. I have ported a ROM before by replacing certain system files but this seems to be a lot more advanced. I am currently here but that is only half of what I need to do. Could anyone give me some advice or a place to begin?
cruzin_cruzing said:
I'm trying to port this ROM from this git to the Desire HD. I have ported a ROM before by replacing certain system files but this seems to be a lot more advanced. I am currently here but that is only half of what I need to do. Could anyone give me some advice or a place to begin?
Click to expand...
Click to collapse
You have to add a source for building for your device. Look in my signature for gingerbread compilation and go the bottom of the guide. Just change names of directories as needed. It is easier to port a ROM that is already compiled. Look in the supported device forums of that ROM and port one.
Hey guys!
My device (the HTC One X for AT&T) currently has a CM9 and AOKP port. I really wanted to get started with developing though. I wanted to create a full AOSP ROM (directly from Google) just to learn the process and get my hands dirty with ROM development (I've already done quite a few mod packs and a kernel).
We have an open sourced CM9 device tree available. I've tried using that device tree for building the AOSP ROM but of course, it has errors because the AOSP source isn't CM9...
So what I'm asking is how can I use this CM9 device tree with a pure AOSP ROM? Like, how exactly do I edit the CM9 device tree so that it creates an AOSP ROM? I'm aware its no easy task, but if someone could point me in the right direction it would be greatly appreciated. I'm a noob when it comes to ROM development, I've never made one before haha I have compiled ROMs before, I maintain the AOKP nightlies for the HP Touchpad.
If someone could help me make this device tree work it would be awesome. Thanks!
P.S. Here is the tree in case someone wanted to look at it: https://github.com/vmagro/android_device_htc_evita
Delete cm.mk
Edit vendorsetup.sh (remove "cm_").
That is all you need to do, I believe.
Like you know, sync the AOSP source, include your device folder amd build.
Sent from my Galaxy Nexus using Tapatalk 2
mDroidd said:
Delete cm.mk
Edit vendorsetup.sh (remove "cm_").
That is all you need to do, I believe.
Like you know, sync the AOSP source, include your device folder amd build.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
I found this thread and this is exactly what I'm doing. Would you be interested in answering my questions in exchange for a nice donation? I haven't had much luck getting help and being a single parent of three toddlers I really need to maximize my free time to work on this.
You also would have to delete any offending overlays from CM that are present within your device repo. As you compile you may run into errors which you could work through.
私のEVO 3Dから送信される。
dastin1015 said:
You also would have to delete any offending overlays from CM that are present within your device repo. As you compile you may run into errors which you could work through.
私のEVO 3Dから送信される。
Click to expand...
Click to collapse
Removing overlays doesnt work here. Have many issues regarding the kernel.
hey
Good luck
rohan32 said:
Hey guys!
My device (the HTC One X for AT&T) currently has a CM9 and AOKP port. I really wanted to get started with developing though. I wanted to create a full AOSP ROM (directly from Google) just to learn the process and get my hands dirty with ROM development (I've already done quite a few mod packs and a kernel).
We have an open sourced CM9 device tree available. I've tried using that device tree for building the AOSP ROM but of course, it has errors because the AOSP source isn't CM9...
So what I'm asking is how can I use this CM9 device tree with a pure AOSP ROM? Like, how exactly do I edit the CM9 device tree so that it creates an AOSP ROM? I'm aware its no easy task, but if someone could point me in the right direction it would be greatly appreciated. I'm a noob when it comes to ROM development, I've never made one before haha I have compiled ROMs before, I maintain the AOKP nightlies for the HP Touchpad.
If someone could help me make this device tree work it would be awesome. Thanks!
P.S. Here is the tree in case someone wanted to look at it: https://github.com/vmagro/android_device_htc_evita
Click to expand...
Click to collapse
Were you able to port aosp device tree from cm.Please tell me how ?
So I am trying to build AOSP 5.0 for Redmi 1s. I downloaded the AOSP source. I also downloaded the device tree and vendor tree from github. Now what changes I have to make to build AOSP????
You need to edit the make files, edit .sh and vendor.
I used this answer to get my AOSP running on my G2 using CM sources. It's not very hard to manage this because CM is not quite different in these aspect, but you need to know some stuff about programming and solve the errors. Good luck.
GalaticStryder said:
You need to edit the make files, edit .sh and vendor.
I used this answer to get my AOSP running on my G2 using CM sources. It's not very hard to manage this because CM is not quite different in these aspect, but you need to know some stuff about programming and solve the errors. Good luck.
Click to expand...
Click to collapse
Can you explain...cause I can't understand that post
There are Lott's of threads for porting for Rom's to any device..
But most of describes to use same android versions for base and port...
But i want try porting CM12 for Galaxy Core...
I am not a developer but still want to use Cm12 on my device .. So instead of asking some one i would love to port it by myself:thumbup:
hareshsangar said:
There are Lott's of threads for porting for Rom's to any device..
But most of describes to use same android versions for base and port...
But i want try porting CM12 for Galaxy Core...
I am not a developer but still want to use Cm12 on my device .. So instead of asking some one i would love to port it by myself:thumbup:
Click to expand...
Click to collapse
That is hard to do without a background in building from source and knowing some coding and kernel stuff. You don't have lollipop yet on that device so it will be even harded. You can't just copy some files. You need a device tree and modify the kernel and then build cm12 from source.
Thanks for taking time .. But i would if i can port CM11 at least
hareshsangar said:
Thanks for taking time .. But i would if i can port CM11 at least
Click to expand...
Click to collapse
Well I don't know about your device (it's basically the same for all Qcom device, I don't know about MTK). Porting by copying files is less reliable then building from source (well it's way easier). It's very very hard to solve bugs when copying files and if the base has bugs the port might be even more buggy.
I have been working on Cyanogenmod 12.1 for the LG G Stylo (codenamed LG G4 Stylus). We've gotten to the point where enough bugs are fixed where we can look at the possibility of porting new ROMs to the Stylo. Several roms are in progress, mainly AICP and XenonHD. I was looking at the possibility of taking up porting CarbonROM.
My approach that I currently have in mind is to sync the CarbonROM sources, along with all the dependencies, vendor files, kernel, and device tree from CM and resolve the errors from lunch and make from there. Is that approach on the right track? What other modifications do I need to make before starting?
Thanks in advance!
Sent from my LG-H631 using Tapatalk
Might take a look here http://forum.xda-developers.com/showthread.php?t=1798056
I'm no developer, but this thread will show you kernel and ROM building from source.