Is there a tutorial around anywhere to show you how to create a custom rom for the nexus s 4g? Is there a website or a section on this website with all the mods you can add to the nexus s 4g? Is there a way to make a mega rom with every mod and every customization possible?
To be honest...I have not seen a Guide to create new ROMs, but I have seen some for theming:
http://forum.xda-developers.com/showthread.php?t=916814
http://www.xda-developers.com/android/guide-on-how-to-make-basic-theming-changes-to-roms/
It can get you started
I do believe Codename Android's website may be able to help you.. not too sure, but check it out, developers tutorials at the top..
http://codenameandroid.com/
I found this one also. It can get you started (this was for Xperia X10 but compiling and getting ready is the same for all):
http://forum.xda-developers.com/showthread.php?t=1503093
hello everyone, a few cats at android fourms "aka phandroid' have put our minds together in hopes of building some stock 4.1.2 roms
its really only me and a few other devs doing this. the list will go in order but only with links. as i see no point in copying and repasting everything here.
theses mods are stock 4.1.2 based only and will not work on aosp
this is for sgh-t599n "aka exhibit"
this is the link to the (w.i.p) aosp style rom
http://androidforums.com/galaxy-exhibit-all-things-root/859889-rom-aosp-touchwiz-sgh-t559n.html
this is the mod to 11 color ink effect
this will enable ink effect for sgh-t599n found on the note,note 2,s3, and various other roms
http://androidforums.com/galaxy-exhibit-all-things-root/859678-mod-4-1-2-stock-ink-effect.html
this is my guide on how to port ink effect to your rom
http://androidforums.com/galaxy-exhibit-all-things-root/859780-guide-how-port-ink-effect-easy-way.html
g-rom by gturn (go and thank this man with out this i wouldnt have been able to start)(this is based off of number2)
http://androidforums.com/galaxy-exhibit-all-things-root/839864-gt-rom-v-1-0-a.html
number2 rom by Ldrafta
'http://androidforums.com/galaxy-exhibit-all-things-root/833691-rom-numbertwo-v1-0-md4-tw_4-1-2-a.html"
disabled-sig check (look for it at this post)
http://androidforums.com/galaxy-exhibit-all-things-root/859889-rom-aosp-touchwiz-sgh-t559n.html#post6652724
i will update this forum with more mods/roms/themes as they come.
ill say this now DO NOT! i will say it again DO NOT ASK FOR HELP HERE
i will just simply ignore you, you must go to the correct thread thats listed above here for help
also mods if this isnt the right place to put this then please move it to the right place. i figure it was a general discussion so to put it here
Since previous development thread was closed, I've been getting a lot of pms. Everyone thanks for the kind words and for offering me help. Thumbs up for this great community.
The reason I didn't post the link was because my laptop or my upload server let me down. At least that is what I saw when I woke up.
No big deal, thought I would upload it upcoming weekend. But as we all might know, today oos 2.2.1 was released. My custom oos was based on 2.2.x, so I was thinking to rebuild this rom again based on the latest software. Meaning it will take a couple of weeks before it will be ready.
So far this briefing. If you have questions regarding this rom, for now please ask in this thread.
Link to original thread:
COSX
To the features, just add the viper4android... And try to make the files app show the root directory too.
I feel you should post ur 2.2.1 build directly when its ready..take your time and i do support what u stand for!! and if possible add network speed indicator
Since there was no answer to this on the original thread, what do you mean by theme support? Layers?
I'll be patiently waiting for your release
But, for playing purpose, are there any guide somewhere to create a moded rom from a stock rom ?
I've been looking but all i could find was from 2012
I don't think it's as simple a remove/add apks from the rom zip :cyclops:
Request
Please donot remove the stock oos camera which has manual focus iso exposure .... __/\__ please
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!
Hello,
Just wondering if there's any development/developers still active on this device?
I've been toying with the idea of some mods and feature ports to stock. Unfortunately, I am limited to what I can do currently. (mainly repo builds because I don't have an appropriate computer. however, apk editing and porting is possible.)
I'd like to breathe some new life into this great device. So if anyone is active please let me know.
You might find some help here depending on what you want to do https://t.me/EssentialPH1DEV