I was wondering if anyone could point me in the direction of some information on porting from one version of android to a higher version. Preferably from 1.6 Donut to 2.2 Froyo or 2.3 Gingerbread. Is this even possible?
Also, could anyone tell me what phone I could use that is similar to the Behold II (SGH-t939)? Is the Behold II in the cyanogen repo? If it is, anyone know it's codename?
I have a build environment set up for cyanogenmod, and I followed this guide. I have got to the gpg import and was wondering if the gpg block is device specific somehow or if it is universal.
Tying in to my first question, is whether there is any way I could get the proprietary files and kernel information out of a rom file instead of off the phone. I have a custom rom installed on the phone that isn't working 100% but I don't really want to put the oem rom back on. Unless I absolutely have to.
Also, once I do actually get the proprietary information and kernel stuff, how exactly do I incorporate all that into a new build?
Sorry, I am just starting to learn about android development and need some guidance. Any help would be greatly appreciated.
Thanks
Basically, I'm trying to port this rom to the Samsung Vibrant. I am using the latest Cyanogen Mod nightly as the base rom and following the tutorials for porting roms to other devices. I just want to make sure that I have properly checked everything, since I'd rather not test the rom on my device without community help. I've checked to make sure that the resolutions are similar, etc. My question is, is there anything I'm missing or anything that I should fix?
Accidentally double posted: Can a mod delete this thread?
So, anyone willing to answer this question for me?
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.
I have been searching for stock roms for porting but I cant find any. All the stock roms have firmware + tool due to which I cant port it. I cant find any folders and other materials required for porting. Someone plz post the download link to stock rom so that I can port roms. Thank you