Database Users

How to cook ROM for Galaxy S

Can someone explain me how to cook a Galaxy S' ROM?
I'm pretty good with computer, and i have a lot of time, if someone can help me i'm sure that i will work hard on it.
Thanks for any help!

Iacopo91 said:
Can someone explain me how to cook a Galaxy S' ROM?
I'm pretty good with computer, and i have a lot of time, if someone can help me i'm sure that i will work hard on it.
Thanks for any help!
Click to expand...
Click to collapse
if it would be that easy, everybody would do it
what do you mean by "good with computers"? do you know how to write code (C/C++)? are you yet experienced with running linux? have you ever compiled a kernel before? do you want to make a source-(AOSP)-rom (then you can get the source here: http://source.android.com/ and here: http://opensource.samsung.com/) or do you want to just theme and customize a stock firmware?
i think there are already some tutorials around which will help you in the beginning. just google for them!
i haven't done custom rom development myself but i would really like to get some (clean) aosp goodness on this phone. i am experienced with linux (use it since 6 years as primary os) and i can code c/c++/asm. so if you are in fact serious and able to go all the way. i would appreciate to help!

jodue said:
if it would be that easy, everybody would do it
what do you mean by "good with computers"? do you know how to write code (C/C++)? are you yet experienced with running linux? have you ever compiled a kernel before? do you want to make a source-(AOSP)-rom (then you can get the source here: http://source.android.com/ and here: http://opensource.samsung.com/) or do you want to just theme and customize a stock firmware?
i think there are already some tutorials around which will help you in the beginning. just google for them!
i haven't done custom rom development myself but i would really like to get some (clean) aosp goodness on this phone. i am experienced with linux (use it since 6 years as primary os) and i can code c/c++/asm. so if you are in fact serious and able to go all the way. i would appreciate to help!
Click to expand...
Click to collapse
I'm pretty able to develop with Eclipse, so android sdk. Linux quite good, i prefer to use windows, but i know linux is necessary. First of all i'd like to know how to customize GALAXY fw and then i'll study how to compile a kernel, no one during my life helps me, and it's difficult for me because i'm not good with english and all tutorials are in english!
I'll try to work on it! Thank you

Can someone explain me how to cook a Galaxy S Froyo ROM with AOSP as the base and samsung drivers?

Could someone please explain to me how to flash the Korean firmware onto the European phone? Really need the native "record call" feature

I saw some instructions posted here
http://forum.androidcentral.com/hacking/40130-100-stock-captivate-rom-aosp-source.html

It's not difficult if you're comfortable with linux, shell scripts, custom kernels, and cross compiling.
Basically that's pretty much all it needs, Android systems are very similiar to a running linux system.
Boot off a bootloader (usually closed sourced) into kernel and initrd, then init loads the drivers, system and configs, after which is pretty much to your taste and likings.
Source code of android, samsung kernel source, are available online, google is your friend.

[DEV] AOSP Gingerbread ROM thoughts - NOT A ROM THREAD

I've been pondering this for a while. This thread serves as a thinking ground until the official AOSP Gingerbread Sources are released.
As a HD2 Android community, once Gingerbread is up on it's git source, why doesn't one brave soul go ahead and download the source, and build it so it's completely stock (aka generic) with no mods, just directly from the source, and then release it as a "ROM Starter", meaning that devs that are wanting to sink their teeth into a working Gingerbread base can download that ROM, add their own sprinkle of seasoning (custom apps and the like) and bake it even more.
The person who baked the original ROM would be thanked and all that jazz. This would save a lot of time and effort having to download compilers, and all that stuff just to make a HD2 Gingerbread ROM.
In other words, make a ROM base that we can do our own spin-offs on it for example, you might see:
m-deejay NitrousBread
darkstone SpicyGingerBread
...etc.
Which are based on the generic ROM that the brave soul compiled. I'm sure they'll be famous as well
So yeah, that's my two cents. Your opinions?

Yes I agree. I was thinking we should have a base ROM just like in Nexus S, without any mods or tweaks and etc. A Plain vanilla stock Android 2.3 Gingerbread ROM. Then from there devs are welcomed to make changes and etc.

waiting system dump from Nexus S

MDJ ROMS Rules
m-deejay said:
waiting system dump from Nexus S
Click to expand...
Click to collapse
mdj I know, you would be the one to do it. Keep up the good work.

[p1010] Compatiable Custom Rom for p1010

Hi Guys,
Can somebody point out what are the compatiable Custom ROM for p1010...
I am looking for best custom ROMS ..
Cheers!!!!!

Well, just the CleamROM,
Motafoca said that will port cyanogenmod 9, but this will take a time.

samcortez said:
Well, just the CleamROM,
Motafoca said that will port cyanogenmod 9, but this will take a time.
Click to expand...
Click to collapse
This is correct. CleanROM is the only "non-stock" ROM available for the 1010 and technically is not a "Custom" ROM. It is based upon a "Stock" Gingerbread firmware with some "bloat" removed and some theme's added. Also, Scott from Scottroms (the developer of CleanRom) I believe has sold his Galaxy Tab and will not be providing future updates.
Motafoca is indeed working on a CyanogenMod (CM) build for the P1010 but to my knowledge he is the ONLY developer doing so. Let's all wish him luck and support him in his journey because once he is successful it will open the door to other developers.
FYI, I have created an in-depth thread specifically for the GT-P1010 that can be viewed HERE.
I will be updating that thread and adding the details above to it. My hope is that we can all discuss our "forgotten" P1010's in that thread so as to be able to find all the information more easily.

I'm one of the testers of motafoca. And well, actually, we are trying to ort cyanogenmod 7.2, but the zip doesnt works, p1010 is a little complicate. And motafoca is working on 4 devices at same time. Soo its hard. I think that in march we finish with cyanogenmod 7.2 (note: the biggest problem is do a flashable rom of cyanogenmod, after that, is just pick the drivers of gingerbread from the source)

Thanks Guys for that information...

[Q] which AOSP 5.0 ROM for building yourself?

I am NOT a developer!
I am a Systems Administrator, and I have built a 4.2 before using ubuntu 14.04, with a SGS2 i9100.
I have attempted in the past to ask for a device tree so I could build my own pure AOSP, and no one was able to help me.
SO, I now have my hands on a S4, and I want to put 5.0 on it.
I can create the build environment. either the windows version or the ubuntu version.
What I would like to know is which ROM would provide me a bit of instructions on how to use and build their ROM.
I'm looking for a ROM as close to AOSP as possible.
Preferably without any CyanogenMod builds, but I hightly doubt that is possible.
Seems everyone is using them for some reason.
I've been going to the ROM's section and I see no instructions on how to BUILD the rom.
Sure, I see their Github, but no info in what environment its been build in.
Can someone assist in helping find a ROM, so I can contribute to this community once I get the feel for it?
thank you!

You can try building cm to understand the basis, then move to aosp

Need help wrapping my head around building AOSP for HTC One M9

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!