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
Related
Guys as the title tells, can someone experienced enough create a sticky thread for listing all the custom roms and kernels that are available for our galaxy s2?
And also regularly updating it when new roms are released. It will be much helpful.
As i dont have enough time regularly im not in a position to do that.
It hasn't happened yet for a good reason - there's still a debate about what can be defined as a custom ROM and what can't.
See the first post in the "Android development" section. Passions run high there.
I find it relatively easy to look at the headlines rom XXX v1.2 .
Any list is going to be meaningless unless it had a full and active update of the actual improvements on that version .
Some roms are not going to fit into any pattern particular Kitchen roms with multiple builds.
jje
hello everyone i am fairly new to the world of android ive only had 2 android phones the first was a samsung transform which i rooted and had everything done to it that was possible but recently traded it for an echo and to my dismay cannot root it so i am gonna try and build my own custom rom just dont know how to do it ive been looking online for guides but it seems like everyone i found only works with htc? if someone could please guide me in the right path on finding guides on building roms that would be awsome i am curious to learn this whole process thanx
This probably isnt the right place for your post, a section called Android Development for your specific phone would be a great place to start a thread.
As for the question though, there generally speaking are no guides for building roms. Most people will start small, with mods or themes, then slowly grow into full roms. Although based on your post, your phone cannot be rooted, so how are you expecting to install the rom without root?
Hi, I would like to learn how to build a vanilla AOSP ROM with ubuntu.
Is the first time for me, so I need a complete guide. :angel:
thanks
Or someone can compile it for me... Pure Aosp without any tweak or mod...
And of course future update of aosp.
There are several guides, no this isn't a LMGTFY link, but it is a Google link. The first two are good guides.
Point being, you may need to refer to more than one guide until you have your build environment set up properly, and all the other variables in place. Might take you some time before you've built successfully, but it's a worthwhile experience.
Edit: obviously the links above point to some 4.2.1 resources, you can work your way around that with additional Google Ninja stuff. Seriously, go for it, it's fun.
No one is going to write you a personalized step-by-step guide on how to do it you need to read up and learn to do it yourself.
Start here:
http://source.android.com/
This section will tell you how to set up you pc to run it
http://source.android.com/source/building.html
As an example here is a guide to setting up an AOSP build environment, yes its for another device but it will give you an idea of what is involved in setting it up.
http://androidforums.com/optimus-m-all-things-root/619804-guide-building-aosp-more.html
HI all , i lunched this thread after weeks of googling and usless search for a new stock or custom rom to update my phone (samsung sgh-i857 doubletime) it's a dual screen phone with querty built-in keyboard it's from at&t and it is stuck on android 2.2.2, i'm very sad that they and after years from lunching it didn't back it up with a single soft update -_- ... and i know that there are users who bought this phone like me and seek help.. i know that it's not this easy but if you are a devloper help us by creating a custom rom for it ....if you are a user of this phone please support this thread by commenting so we can get an update for it :good: ps: i attached informations for it's cpu
Hello good sir, I like you am a noobish Doubletime user who is struggling to update it to Gingerbread. So far I have been somewhat able to use the Cyanogenmod source code and I have built a CWM Recovery for the device but that seems to have hard bricked it... I ordered a new one off ebay for $15 and I'm ready to start cooking. You have my support!
Just an update.
I have a plan I have on how to get this runnin.
1. Port CWM to the DoubleTime through Cyanogemod 6.
2. Get a working version of Cyanogenmod 6 working on the DoubleTime to hopefully free up some space.
3. Find if Gingerbread can run on Froyos kernel.
From there I'll either be building a GingerBread compatable kernel or Cyanogenmod 7 depending on compatability. Any advice or help would be very appreciated.
Being new to ROM building I'm a little lost and hesitant on flashing things but here's what I know so far.
The DoubleTime uses a Qualcomm MSM7230 same as the HTC Vision. I forked it's Github respiratory and I'll be using it as a base as recommended by the Cyanogenmod porting guide.
The partitions sizes (as a accurately as I can estimate them) are:
/cache=21.05MB
/data=176.65MB
/system=194.38MB
I may need to know the recovery partition size but I'm not sure how to find that out.
I have the recovery.img and the boot.img as well as the zImage. So as soon as the repo sync is done I'll be on my way.
I'm back again today with somewhat mixed news, I can find most of the partitions and their names (I've learned a lot today) but I can not seem to find the boot, recovery or ramdisk partitions. I'm already boggled by the what seems to be unconventional naming setup for partitions. Put all of my "notes" in a text docement in the attachments section. Any help with this is very appertiated. I can type and post anything into the ADB shell you need me too.
I'm beginning to feel like I'm talking to myself, I probably am...
Upon reading forum rules and such it has come to my attension that this is the wrong forum for this kind of thread, So I have made a new thread in the Miscellaneous Android Developement Forum that will hopefully be more useful at getting more proffesional and opinionated help.
http://forum.xda-developers.com/showthread.php?t=2651728
Hey there,
INTRO:
I'm a relatively new member to XDA and the Android Community as well. The Moto G (2014) is my first Android phone since ever. I was using iPhones (4,4S,5,5S), iPads and Mac and have Jailbroken and Developed Tweaks, Apps etc for iOS.
Now that I got my hands on this amazing device, I would love to contribute to the Community by developing and porting ROMs for the Moto G 2014.
WHAT? WHY?:
So if it isnt too much trouble could someone post a device-specific instructions, checklist and downloads to setup a development environment for Moto G (2014). I'm a pretty fast learner so any crude form of instructions would suffice. With the right heading and instructions I'm sure that I can contribute to this community.
PAST CONTRIBUTIONS:
If you're curious about what I've preciously done, just Google "Krishna Sagar iPhone" and you'll see. I've developed apps, Jailbreak tweaks and I've even been mentioned and credited by CNET.com for discovering the first solid evidence about 4G in the iPhone 5. (Before it was announced or released. Yea!! )
So any help at all is appreciated! You know.. Help Me to Help You!
Regards
Krishna Sagar
http://www.krishna.bz
PS: I've searched XDA and found some tutorials but I'm looking for some device specific instructions and downloads such as Device Tree, Kernal, ROM sources etc.. and crude up-to-date instructions on how to setup a Build-Environment. Thanks
Reserved by OP:
Once I get a working set of instruction and successfully setup my Dev Environment, I will post concise step-by-step instructions on how I set it up so that others can use it as a reference.
Okay....i just learned these things past month.
So tell me where you reached so that i can guide you.
N.K.V. said:
Okay....i just learned these things past month.
So tell me where you reached so that i can guide you.
Click to expand...
Click to collapse
I am at the very beginning... From the start would be great. Like i said.. I dont want a lengthy tutorial.. I'll find the instructions myself
For eg: just say setup Android Kitchen instead of walking me through the installation setup.
I just need a crude checklist to begin. I've doing some searxhing of my own.. But like i said, i need a bit more devicr specific approach!
Device specific approach would start once you have downloaded the repo.
Till then.... Approach for all the devices would be same.
Que: You are talking about building the rom from source right??
Or you just want to modify the stock rom!?
N.K.V. said:
Device specific approach would start once you have downloaded the repo.
Till then.... Approach for all the devices would be same.
Que: You are talking about building the rom from source right??
Or you just want to modify the stock rom!?
Click to expand...
Click to collapse
Havent decided really.. Might start by porting ROMs initially.. then gradually work on my own ROM
Thanks btw for your help
KrishnaSagar said:
Havent decided really.. Might start by porting ROMs initially.. then gradually work on my own ROM
Thanks btw for your help
Click to expand...
Click to collapse
And where can I download these device repos?
For Porting ROMs : Usually ports are done from working Cyanogen build or AOSP build, which we doesn't have yet. But, k2wl and shawn are main developers working towards that. Once we get those fully working then only you will be able to port another roms.
Regarding Device Repo: It's required to build rom from source, not for porting one.
repo is a "Source Code" file, which is approx 25-30 GB in size.