Are there any guides that show the user how to create a rom from scratch? I've seen multiple guides on creating a rom but they do so using the kitchen. I would prefer something that shows how to make a rom without a crutch.
please help
HydrogenPeroxide said:
Are there any guides that show the user how to create a rom from scratch? I've seen multiple guides on creating a rom but they do so using the kitchen. I would prefer something that shows how to make a rom without a crutch.
Click to expand...
Click to collapse
I would say the best way to make a ROM from scratch is to compile it from source. If your interested in learning how to compile a ROM from source I would recommend taking a look at this guide to building Jelly Bean from source, as well as Google's offcial documentation on building Android from source. Additionally this guide on Zip Based ROM tweaking is a good guide to take a look at. Let me know if you still have any questions .
HydrogenPeroxide said:
Are there any guides that show the user how to create a rom from scratch? I've seen multiple guides on creating a rom but they do so using the kitchen. I would prefer something that shows how to make a rom without a crutch.
Click to expand...
Click to collapse
Normally all device forums have tutorials on how to compile ROM from source(if someone has already compiled it).
If no development has yet started for your phone then you you need to create the device tree which is tough. Otherwise just google . There are lots of tutorials lying on xda.
shimp208 said:
I would say the best way to make a ROM from scratch is to compile it from source. If your interested in learning how to compile a ROM from source I would recommend taking a look at this guide to building Jelly Bean from source, as well as Google's offcial documentation on building Android from source. Additionally this guide on Zip Based ROM tweaking is a good guide to take a look at. Let me know if you still have any questions .
Click to expand...
Click to collapse
Thanks, I didn't even know there was an official guide
I'm wanting an AOSP ROM on my s5 g901f but there is no support at all. Could someone point me in the right direction? I'd like to have a go and have looked up porting but I don't think that is the way to go. If somebody could give me the steps what I need to do for this modal I will research.
Could I use the cm for note 4 as it has similar specs, ie
805, 420 etc. Or s5 g900 as a base ROM? Or would I need to build from scratch?
There is only one custom ROM for g901f and that's touchwiz so somebody please help before I go insane. Touchwiz really is that bad
Up for this. Really interested especially for us who has not so good programming skills
mikey187lfc said:
I'm wanting an AOSP ROM on my s5 g901f but there is no support at all. Could someone point me in the right direction? I'd like to have a go and have looked up porting but I don't think that is the way to go. If somebody could give me the steps what I need to do for this modal I will research.
Could I use the cm for note 4 as it has similar specs, ie
805, 420 etc. Or s5 g900 as a base ROM? Or would I need to build from scratch?
There is only one custom ROM for g901f and that's touchwiz so somebody please help before I go insane. Touchwiz really is that bad
Click to expand...
Click to collapse
Let's see if I can point you in the right direction! Because of the differences in specs between your S5 Plus and the regular S5 you can't use that to port ROM's. For the Note 4 idea, since you only have a Touchwiz ROM as your base (The one from your S5 Plus) it won't work properly for the port ROM (CM12 Note 4). I would recommend looking at compiling CM12 for your device, which I would recommend taking a look at this guide here. Let me know if you have any questions be happy to help you out.
Related
Is there such a guide/tutorial/description?
I am interested in porting ROMs to the G1. I am a total beginner, and I could not find anything useful (except the automatic porting of dsixda's kitchen, what is great btw, but I want to learn how to do it by hand, etc).
Could please someone tell me how to do this, what to copy from original ROM for things to work, etc?
Thank you very much!
It's going to vary from ROM to ROM, depending on what device you are porting from and whether it's Sense/AOSP/etc.
You can get some ideas from a couple of my posts though.
http://forum.xda-developers.com/showthread.php?t=723319
http://forum.xda-developers.com/showthread.php?t=815265
Porting is not generally that hard to do... It's getting everything to work right that's a pain.
Also, look at vendor trees for your device. That will give you a good idea about which proprietary files (drivers, etc.) that need to be replaced.
gnarlyc said:
It's going to vary from ROM to ROM, depending on what device you are porting from and whether it's Sense/AOSP/etc.
You can get some ideas from a couple of my posts though.
http://forum.xda-developers.com/showthread.php?t=723319
http://forum.xda-developers.com/showthread.php?t=815265
Porting is not generally that hard to do... It's getting everything to work right that's a pain.
Also, look at vendor trees for your device. That will give you a good idea about which proprietary files (drivers, etc.) that need to be replaced.
Click to expand...
Click to collapse
This is really great, thanks Gnarlyc... been searching all over for tutorials/etc. I was able to port an N1 ROM to the EVO (using dsixda's kitchen); however sensors + radios failed to work after boot-up; probably missed a couple files/libs. Will look these links for tips. Thanks!
gnarlyc said:
It's going to vary from ROM to ROM, depending on what device you are porting from and whether it's Sense/AOSP/etc.
You can get some ideas from a couple of my posts though.
http://forum.xda-developers.com/showthread.php?t=723319
http://forum.xda-developers.com/showthread.php?t=815265
Porting is not generally that hard to do... It's getting everything to work right that's a pain.
Also, look at vendor trees for your device. That will give you a good idea about which proprietary files (drivers, etc.) that need to be replaced.
Click to expand...
Click to collapse
really nice, finaly a topic where i found more infos than just "use the kitchen and change kernel"
other questions :
how do you know you needed to replace some string values by other ? simply open the original rom for you device and compare, or simply guessing the name ???
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.
can anyone help me to learn a bit more than android!
I heared about compile form source and biuld form source...And I can't understand what diferences between compile from source and port! can U explain easily?
for example should I want to bring superOxygen Rom in my x10 , should I port it with cm as base or compile form source?!
thx
for short:
porting means you are making rom to your device from another device, you will be just moving libs, editing ramdisk, etc.
compiling from source means you make a complete rom from scratch including programming own drivers, libs in some situations.
If source is avaiable fot superOxygen then you can try compiling it yourself, but editing, or adding your drivers is necessary, and anyway its harder than porting, but gives better result in fact because you can program everything to make it work and you aren't dependant on binary files like in porting.
When porting, hardware should be close to one you have in your X10, because most things will not work when processor differs, wifi modules, gsm etc. You take files from any X10 rom and replace ones that are with same name in another rom (oxygen here).
Thanks very much man!
I took your advices...it was good advices but what is your idea about this:
If I port Superoxygen from Nexus1 for my x10 and (use stable AOSP as base) , then can I say I make a superOxygen Rom?
compiling from source is how much difficult?! I'm 17...! , I have a link that teach compile from source... Is it need some Knowledges that is impossible for me?!
heh, im 17 too and I don't have much knowledge, but looking on pcfighter(a gt540 developer) im impressed, hes 17 too and does a great job, so it depends on time spent and interests
when you port oxygen, you can just say that you ported and not made it. credits go to the maker and you for just making it work on x10
I'm looking now how to compile for gt540 but can't find any idea how to make it strict for gt540 compiling from source tutorials are mostly for nexus s and nexus 4g because most of are just remade of what you can find on official android developer page and its easier. For unsupported device its even harder, you have to work with what you already have and add it first to sources then ... more things to do. I'm beginner with that too, just pulled sources yesterday and looking how to make it work :] so don't expect so much help in this way :]. Just telling you overall how this looks
For compiling you need to know Java and C programing language.
Sent from my Xoom using Tapatalk
@mesaj! do you know c and gava programing languge?! ofcourse I worked c++ a little...
Thanks now I also know what the difference is.
In easy terminology. Compiling a ROM is building a ROM from the source code so it means you are building a ROM from the ground up. Porting a ROM to your phones means to take a ROM built for another phone and to get it working on yours. That's the simplest way to think of it. I have in my signature a guide for compiling a ROM. Oh and I'm newly 18
私のEVO 3Dから送信される。
Thanks for this thread
Thanks now I also know what the difference is.
Click to expand...
Click to collapse
Thanks for this thread
Click to expand...
Click to collapse
just press the thanks button if you like this thread
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.
Hello everyone.
Im new here.
I just want to ask something.
When porting roms can my base ROM and my port ROM have different android version?
Looking forward to having responses
P/s: sorry for bad engrisk )
XdaNeko said:
Hello everyone.
Im new here.
I just want to ask something.
When porting roms can my base ROM and my port ROM have different android version?
Looking forward to having responses
P/s: sorry for bad engrisk )
Click to expand...
Click to collapse
It has been a looong time since I knew about those things but if I remember your base ROM should have that same Android version as your port ROM.
And if you want an advice, please consider building a ROM from source. Troubleshooting is hell with ported ROMs. Building ROM is scary because it has commands that you don't know yet, but it's way more easy than porting. Trust me.
Here is a guide on how to build ROM from source :
https://forum.xda-developers.com/chef-central/android/guide-android-rom-development-t2814763
@XdaNeko
It's NOT the version of Android what does matter. If that would be the case then an upgrade via OTA never would be possible.
A Stock ROM always at 100% matches phone's hardware ( CPU, GPU, RAM, storage memory, etc.pp ) - it's built by OEM's / Carrier's R&D department, the guys who know best of.
Whereas a Custom ROM necessarily does NOT because it gets built by 3rd-party companies/programmers associations - who think they can do it better, but don't always have the specific Android device at hand.