Hey guys I created this to show progress on porting AOKP from the S3 and get some collaboration from devs. If any devs want to help please chime in. I can send my zip file of my attempted port. So far though I am going to need a ported kernel, the one in my zip is just our stock N7100 kernel. I don't have the note ii so I have no way to test it, and I only feel comfortable having devs test because I am not at the point of releasing anything, and have not yet asked permission to use other dev's work. Basically once this is booting and stable I am going to get permission and I will post it up in the Dev section.
Hi
Can anybody port this Rom from the nexus 5? To D802
Its based on pure4.4 aosp sources by google.
http://forum.xda-developers.com/showthread.php?t=2512139
I'm not very good at development but I can help in some way or the other.
Thanks
Mate,
I'm sure developers are working on the port as we speak. Just need to have some patience
I've been trying to build 4.4 from source at the moment using the CM device tree for our phone. I literally know nothing about building so it's been an interesting experience hitting a lot of errors that I'm sure are simple to overcome. But I'm sure the Devs are hard at work on some awesome stuff for our G2's
Good day everybody!
I created this thread here so that people cuold handle with this argument, Porting ROMs!
In particular I also wanted to ask help about a project I wanted to start by myself.
I'm new about porting full ROMs but I followed dozen of guides and got in touch with it!
I recently saw the new "Hydrogen OS" ROM for One Plus One and totally went in love with it! My project was to port this ROM to the Samsung S4.
Being my first time I'm not quite sure, so I wanted to know if someone could give me an hand or some tips!
Following guides I would like to port "Hydrogen OS" to my Samsung S4 i9505 using as base
ROM a version of CM12 5.0.2!
Is it possible? Will it boot or are they incompatible?
Can someone help me with This project?
I am looking for any dev's out there willing to help me build my own ROM. I have building just pure AOSP for awhile now for the Nexus 5 and now for the Nexus 6P. I am looking for help with things like adding SuperSU and adding features found in other ROM's out there. I have some knowledge (not much though) of using github and gerrit to cherry pick stuff, but I have a lot of trouble when it comes to fixing build errors. If anyone out there has the time and would be willing to help it would greatly appreciated. You can either reply here or feel free to PM me.
Hey folks,
I know most people have already given up on this phone because it didn't sell well and doesn't have much support. But like the rest of us still browsing this forum, I still have my M9 and still believe it can be improved. I am currently working on a project to build a clean AOSP rom (without any kinky modifications, just a nice stock rom built directly from the AOSP sources.)
I've never undergone such a project, and I've been reading a lot about the steps necessary to realize this goal. I've been following Sony's excellent AOSP building guide so far. I have the android sources downloaded, all I'm missing are the proprietary files (from the device itself, most likely) and the ability to set up the proper device trees/manifests. I was planning to use the Cyanogenmod device tree because a lot of work has gone into it and, given that my M9 is currently running one of the CM13 nightlies, is pretty stable and works with new device firmwares. I know there is already a guide on the Cyanogenmod wiki for building CM for the M9, but I am not building CM at all, I want to build a 100% stock AOSP rom.
Can anybody help me proceed from here? I've downloaded the https://github.com/CyanogenMod/android_device_htc_hima-common tree and put it into device/htc/himaul but I'm not sure where to go from here. The extract-files.sh script does not work (because there is no CM helper script). Does anyone have any experience with this sort of thing?
Thank you very much in advance. I hope this will help everyone as I know many people have been looking for a non-CM AOSP rom for this phone (some do not agree with CM design philosophies). I definitely plan to share this rom and write a guide to help other projects when this is figured out.
I look forward to hearing back,
vivremetrique
Hi, I have no idea on doing roms, but you could help be your tester ...
whatever you need, talk me
---------- Post added at 10:22 PM ---------- Previous post was at 10:19 PM ----------
It would be good to make a ROM Nougat if possible
AOSP 100% and cyanogenmod device tree are totally different
I don't know what does it take to have a full aosp working rom, but I'm sure that CM code has nothing to do with it.
anyway, with the right work it shouldn't be so hard since m9 shares hardware with nexus 6p...
Frug01 said:
[/COLOR]It would be good to make a ROM Nougat if possible
Click to expand...
Click to collapse
Yes, the sources I will be building from will be Nougat sources (7.1 experimental sources). Thank you for offering to test once this is done.
throcker said:
AOSP 100% and cyanogenmod device tree are totally different
I don't know what does it take to have a full aosp working rom, but I'm sure that CM code has nothing to do with it.
anyway, with the right work it shouldn't be so hard since m9 shares hardware with nexus 6p...
Click to expand...
Click to collapse
I mean the operating system will be 100% AOSP, but obviously since this is not a Nexus/Pixel device the device tree will not be included in AOSP... The device tree/proprietary files have nothing to do with the actual user experience, they are simply needed for support of the hardware/stock kernel if desired/camera or wireless firmware. I don't see the sense is rewriting these from scratch given the time and effort already put into them by CM devs/those in the Cyanogenmod threads in this forum.
It would be great if some of you could help gather helpers for this project. It seems that properly setting up the device and getting ready to build the rom are all that is missing, so I'm hoping this goes relatively quickly.
So I believe I've made some progress. I downloaded the htc vendor files, the htc msm8994 kernel files, the hima-common tree, and the himaul tree. There is still something missing, because running the "lunch" command warns that it cannot locate the config makefile.
I found references to cm in cm.mk in device/htc/himaul/cm.mk but I don't know what to replace them with and I don't want to download the whole CM source tree as well.
Can anyone shed some light on this issue?
I can't help you, but that is a very good idea! Hope you can solve this issue.
Nice project, I would love to see AOSP Nougat on our M9! I'm not a dev who could help you with the building process, but maybe the dev of the CM14 port for M8 could give you an advice. Good luck!
I think you are underestimating the efford and skills it needs. Even with official Kernel Source released it took some really effort to make for example the camera work. If you don't know hot to setup a device tree for an existing rom, then I feel the skills required exceeding the ones you have. I don't want to offend you, but maybe it's better to take a step back an learn how to add this to an AOSP Marshmallow rom, instead of thinking about porting it to Nougat. If it would be that easy, wouldn't a ready to use Nougat Version of any other popular Rom for the m9 be out already?
Any telegram group of One M9???
Enviado desde mi HTC_M9u mediante Tapatalk
Adromir said:
I think you are underestimating the efford and skills it needs. Even with official Kernel Source released it took some really effort to make for example the camera work. If you don't know hot to setup a device tree for an existing rom, then I feel the skills required exceeding the ones you have. I don't want to offend you, but maybe it's better to take a step back an learn how to add this to an AOSP Marshmallow rom, instead of thinking about porting it to Nougat. If it would be that easy, wouldn't a ready to use Nougat Version of any other popular Rom for the m9 be out already?
Click to expand...
Click to collapse
That effort would.not be wasted. Once the solution to the camera problem is solved, it's solved for all versions, not just Marshmallow. We can reuse the kernel source and firmware blobs in N. I reckon that we don't have a rom because nobody is working on it.
If it would be that easy, why isnt there an official (or even inofficial) cm 14 for m9 out, as it already got an official cm 13? If everything you needed would be to just switch everything else to cm 14 and reuse the mm kernel source and blobs?
Adromir said:
If it would be that easy, why isnt there an official (or even inofficial) cm 14 for m9 out, as it already got an official cm 13? If everything you needed would be to just switch everything else to cm 14 and reuse the mm kernel source and blobs?
Click to expand...
Click to collapse
Because there is almost zero demand for one. People in the CM13 thread are actively discouraged from even mentioning CM14. How can we develop the ROM if we don't have anybody working on it?
Given CM's automated device tree preparation system, I doubt it would take more than a simple source tree update to Nougat to start compiling a 7.x ROM (whether it works perfectly or not, it would be a start).
Well then I would say, a way to start might be to try compile a booting cm 14 for the m9. Last time I looked there has been at least a device tree prepared for cm 14. I guess that would be the easiest way to test, if you might be succesfull with it
Any news @vivremetrique ? Or did you drop the project?
While it is possible to build cm14.1 for the M9, I was unable to make it see the sim card after days of trying. something in libril or possibly the firmware I have makes it not work.
Trainwr3ck said:
While it is possible to build cm14.1 for the M9, I was unable to make it see the sim card after days of trying. something in libril or possibly the firmware I have makes it not work.
Click to expand...
Click to collapse
If it is the same Problem I had with a CM13 based rom, then the build.prop is missing some Values to detect network. I took them from a working one and put them in the BoardConfig by hand
can't help, but my hopes are so high for this one!