Hi everybody,
since my Sensation is on its last legs, I wanted to try building a ROM myself. I've never tried anything of the sort, but given all the resources we have, it shouldn't be impossible for a power user, given the right tutorials? At least, the building part. Making it work perfectly is another thing... But I wanted to at least try. Cyanogenmod 12.1 is a bit too heavy for me, and Slimkat was just perfect.
I've looked everywhere for tutorials on how to build a custom rom for a specific device but I've only found stuff from 2011 that uses android kitchen (deprecated)... Can anybody give me a few pointers?
I thought I could use Slim's Github and maybe have ivanich's device tree as a base?
Related
I am building an aosp ROM for the galaxy player 5.0 as an independent study at my school. I have the stock kernel for it that I extracted out of an odin image and I was wondering, do I have to build aosp around the kernel because I heard aosp kernels aren't good with the drivers and I need every function to work. I have found many tutorials for aosp and I am not going to use Googles since I can't understand that as much as other ones on the internet. Can someone enlighten me on the subject so I'm not going to fail, its due by january and I am still on the fence about whether I can do this. I just need some guidance and not to have somebody do it for me.
So im trying to get everything up and running on my computer so I can build us all a pure vanilla 4.2 rom. I have been following a guide to setting everything up on Ubuntu 10.04 to build 4.2 roms, my only problem is finding our device tree. I am a bit unsure if I can just use CM's d2vzw device tree or if I need to find another one.
If it does needs to be a different device tree I have found one, https://github.com/Joelz9614/android_device_samsung_d2vzw , but yet again I dont know if it would be better to use CM's device tree or this one. For the time being I am going to use this one until someone chimes in and lets me know which one would be best to use, or if there is another I dont know about that I need to use to build 4.2 .
Thanks in advance guys
So, Since the Cyanogenmod source is so big (I heard that it has 19GB), people like us who have gay as slow internet have no chance of even trying to cook a ROM for our unsupported devices.
Since I can't download the whole CM source and I see awesome ROM's out there, I Ported one ROM called Cyanfox (which was made for Samsung S2 i9100) to Samsung Infuse 4G using Beanstalk ROM as a base. I followed a guide which asks me to replace some folders and edit some files. It was walking fine. Then came an update to both the ROMs, Thinking that cince it is a update, it will have the updated apps and source, I tried porting them again but this time Beanstalk updated ROM as a base cause a bootloop while the Beanstalk old ROM works fine as a Base ROM.
Now what I don't get is, why is Beanstalk new ROM not working as a base? (Since the new Beanstalk ROM will have updated Source, I want to use that ROM as my base.)
And the second question is, what files does actually matter when you are Porting or cooking an Android ROM? (I mean like windows works on all kind of PC's all it needs is the drivers right? The drivers actually matter on windows)
And the 3rd question is can I update the source files somehow without downloading the whole 19GB CM source and if possible how?
The 4rth is, I heard from somewhere that boot.img is the file which separates the phones? Then why can't we just port ROM's by replacing boot.img since these two phone's are from the same vendor and it has likely specs. (Which is not possible I think)
I am really really a newbie to this thingies, I just wanted to clear out these things. Sorry for my noobness.
Thanks!
Hello everyone! I am a little new to this, so please take it easy on me. I have actually never created my own Android ROM via the AOSP, but I have opened up Zip files for ROMs other developers have created and have been able to do basics.
I recently bought this device: MPie G7 (gearbest . com/cell-phones/pp_76182.html)
As you can all tell, it is not exactly a very popular phone. So, finding source code for this phone's ROM is basically, impossible. I have also been unable to find the manufactures website address either (anyone have any ideas?).
Anyway, here are my very noob questions. I am obviously planning on hitting base with the AOSP code, but with Lollipop. This poses a new problem to me, because I cannot find the source code, how am I supposed ot create a kernel specific ROM? This thing runs on a MTK, most precisely: MTK6582. It came with Android 4.4.2 (KitKat).
I am also worried about one small other thing, which is the gestures. If my phone is on standby, screen is off, I can do gestures on the off screen to do certain things. Similar to the OnePlus One. But, I am worried I will not be able to do that if I build my own ROM from source.
Anyone have suggestions? Or can possibly help? Thank you very much. All your help is appreciated!
By
omarquazi said:
Hello everyone! I am a little new to this, so please take it easy on me. I have actually never created my own Android ROM via the AOSP, but I have opened up Zip files for ROMs other developers have created and have been able to do basics.
I recently bought this device: MPie G7 (gearbest . com/cell-phones/pp_76182.html)
As you can all tell, it is not exactly a very popular phone. So, finding source code for this phone's ROM is basically, impossible. I have also been unable to find the manufactures website address either (anyone have any ideas?).
Anyway, here are my very noob questions. I am obviously planning on hitting base with the AOSP code, but with Lollipop. This poses a new problem to me, because I cannot find the source code, how am I supposed ot create a kernel specific ROM? This thing runs on a MTK, most precisely: MTK6582. It came with Android 4.4.2 (KitKat).
I am also worried about one small other thing, which is the gestures. If my phone is on standby, screen is off, I can do gestures on the off screen to do certain things. Similar to the OnePlus One. But, I am worried I will not be able to do that if I build my own ROM from source.
Anyone have suggestions? Or can possibly help? Thank you very much. All your help is appreciated!
Click to expand...
Click to collapse
Why don't you list down some of the specifications of your phone and compare them with other mediatek devices!!!
That way if u have the stock ROM of the phone then u can port ROMs from another mediatek device like xolo q700i which has a dedicated thread!!! xolo q700i has many different number of ROMs !!! That way by zip based theming and porting you might be successful in at least creating a ROM for yourself which u can use as a base for different roms!!!
The way I see it if you don't have source or downloadable ROM from your OEM, you have two options:
- like @thecoolster said you could try flashing ROMs from similar devices, and hope you don't end up stuck with a soft brick.
- or, likely your device can be easily rooted (in the settings perhaps?) if it isn't already. Then you can make nandroid to give yourself a stock ROM to cook.
Actually porting your ROM from a developer device tree and AOSP or CM is hard if you are only a hobbyist cook.
Even with a cooked ROM, you'd need a recovery that lets you flash it or you'd have to use SP flashtool and make your own config files for the flash.
Hi guys, i am new to android and everything and i have an intention to build a CM based ROM for Hammerhead and i really looking forward on help. I need beta testers and a dev who can help me out, cuz so far iḿ following the rom building guide by this guy called jackeagle, and honestly sometimes it just makes no sense at all so I appreciate any help, don't judge me by any reason.
If you want to build CM rom use CM instructions (there are on cm wiki page). If you want your customizations you need github, fork cm source and modify it.
After it you need to modify local_manifest to use your source, not CM to build rom and voila, everything should work fine.
I know what i'm saying, i've built CM roms for D802, WT19i and some other devices.