I'm very interested in doing some ROM development, though I'm quite the beginner. I know my way around Java and can hold up against some C, and I've also done some apps. I have a few questions though before I get started.
After I run make on the AOSP, how can I test my build with the emulator and my device (Eris)?
Will using the build on my Eris work, provided there are no build problems?
How could I base a ROM I make off of an existing ROM? (For example, KaosFroyo)
What is the difference between cooking a ROM, and running make on the AOSP?
I think thats about it for now. Thanks for taking a look!
Chiggins said:
I'm very interested in doing some ROM development, though I'm quite the beginner. I know my way around Java and can hold up against some C, and I've also done some apps. I have a few questions though before I get started.
After I run make on the AOSP, how can I test my build with the emulator and my device (Eris)?
Will using the build on my Eris work, provided there are no build problems?
How could I base a ROM I make off of an existing ROM? (For example, KaosFroyo)
What is the difference between cooking a ROM, and running make on the AOSP?
I think thats about it for now. Thanks for taking a look!
Click to expand...
Click to collapse
1) I'll answer the Eris part, since I have done that more than once... You need to zip up the following:
a) /system folder from 'out/target/product/generic (or desirec if you used a vendor tree)
b) a /META-INF/com/google/android folder structure with a working update-script
c) a boot.img with an Eris kernel and appropriate init.* scripts in the ramdiskThen sign the resulting zip. There's your base ROM. You can also just throw that into dsixda's kitchen.
2) Yes. Define 'work'. You'll need an Eris kernel, Eris specific drivers in the right place, and the correct settings in the init.* scripts and build.prop. It also helps to have a wlan.ko in /system/lib/modules that is compiled against the kernel that you are using.
3) If you take an existing Eris ROM and use it as a base, you're golden. The Eris specific stuff is already there. At that point, you can theme, add/remove apps/etc. Give credit where credit is due though. Personally, I recommend that you start with a stock ROM or AOSP, but that's me.
4) Well, I suppose it depends on who you ask... Some devs don't really like the 'cook' moniker. It sort of implies that you are just taking parts from everywhere else and making something tasty instead of coming up with something new. Compiling AOSP is not really coming up with something new, but at least you started 'from scratch'.
Even if you don't want to use a kitchen, I recommend that you download dsixda's and my Android Builder to look at the scripts. You can learn a lot by looking at those.
Related
hey guys im a beginner and have no clue on how to build a rom for hd2, but would like to build one. can someone please help?1?
post your question regarding cooking in chef general..
dloopy said:
hey guys im a beginner and have no clue on how to build a rom for hd2, but would like to build one. can someone please help?1?
Click to expand...
Click to collapse
It will involve a lot of reading, i believe Dutty provides a kitchen in his roms so thats a start.
heres a great starter, lots of info about the kitchen structure in post 1, great starter guide in post 2
http://forum.xda-developers.com/showthread.php?t=628948
There's a lot involved when it comes to building a fast, stable, well-working ROM.
To get you started, I would recommend you download Ervius's Visual Kitchen based on Bepe's latest tools from HERE.
Second, download the latest stock ROM for your specific device. Mine is the T-Mobile HD2 so the stock ROM for that was where I started.
Extract the RUU_LEO_......exe using WinRAR. It can be found HERE. The free version will serve you well. Now open the Kitchen executable and use the option on the left to "extract" or dump the stock ROM that you just extracted from the exe. This will create the Kitchen for you. Or rather.. It will create a solid base foundation in which you can begin your modifications.
Before you'll be able to re-cook the ROM however, you will have to "recmod" the NTFConfig.dll module in Notification Enhancement. Failure to do this will result in a non-booting ROM. Don't ask why... I just know that this has to be done.
Once you do all of this, rebuild the ROM as stock and flash it to your phone(YOU MUST HAVE HARDSPL FIRST!!!!). If all goes well and the ROM boots, runs, and works like you expect a stock ROM to work, then you're free to start making all the changes you want.
TIP>> NEVER delete any package just because you are now using an updated version. Always keep the original just in case something doesn't work and always remember, keep 2 save files. One that you know for a fact will work if you re-cook and one that you experiment with.
As you get more comfortable with cooking ROMS, then you'll be able to update the SYS/XIP components more easily and so I suggest you stay away from that right off the get go. Get a good solid ROM first then play with those "extras".
One last thing - Familiarize yourself with the initflashfiles.dat file(open it with notepad) located in \OEM\"Device name"\0409\OEM_Lang_0409(I used 0409 as an example as this is WWE - you can use whatever language you like). This file controls all files and directories. Trust me, if you don't understand what I mean by that then open the file and you will.
If you have any other questions I'm sure there are many other chefs here who can offer you help and assistance.
Finally, be persistent! Don't let a buggy or non-booting ROM get you down. It can always be fixed! Just have confidence in your "techy side" and have patience. Know that the more you do it, the better at it you will get.
Good luck and happy building!!!
on rom building
[ ive been told that you can take a standard custom rom of your choice and just load the hd2 drivers to it is this true and where can i find the drivers to check what folder would i locate the
regards
---------- Post added at 12:14 PM ---------- Previous post was at 11:59 AM ----------
ross07 said:
[ ive been told that you can take a standard custom rom of your choice and just load the hd2 drivers to it is this true and where can i find the drivers to check what folder would i locate the
regards
Click to expand...
Click to collapse
or any standard drivers of what ever phone etc
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 ???
Okay, I am a noob. Glad to be on XDA, but a noob nonetheless.
I know the basic in's and out's of flashing, backing up ROMs, etc.
Well, I want to learn how to start writing my own custom ROMs.
I have (at least I think) most of the necessary software, SDK Tools, Microsoft Basic and C++ 2010. But I don't have anything but basic knowledge of code. Anybody willing to help a noob out and get me kick-started in making ROMs and coding in general?
The only device I have to work with is a PC and my HTC DInc. It's been a great phone
I'd much appreciate the help.
Thanks in advance,
TheSmashippy
The kernel is in C
Android is mostly java (if its open source = Cyanogenmod).
But most Roms just and and replace apps. Maybe add some themes and stuff. Have a modded kernel for OC and stuff. And thats mostly it.
Smasher816 said:
The kernel is in C
Android is mostly java (if its open source = Cyanogenmod).
But most Roms just and and replace apps. Maybe add some themes and stuff. Have a modded kernel for OC and stuff. And thats mostly it.
Click to expand...
Click to collapse
Well, see I don't really get most of that. I don't understand the differences between C and C++ and Basic, I know they're separate languages, but I don't really notice any differences.
And I have never flashed a new kernel before, just new ROMs I'm actually pretty sure I still have the Stock DInc kernel, unless a few of the ROMs I've flashed came with kernels specifically for them... Not really sure how kernels effect the ROM :/ Like I said, noob. Hard.
Well, until you have flashing down, then I would stick there. Once you do it a few times, it is no big deal. The first time might have you on the edge of your seat.
thesmashippy said:
Not really sure how kernels affect the ROM :/.
Click to expand...
Click to collapse
The Kernel has a major effect on the rom. Changing a kernel can make a rom much better or far worst. Kernels allow many customizations in the rom like overclocking. Here's an example of this: Kernel A may allow your device to be overclocked to 1.2Ghz and Kernel B may allow your device to be overclocked to 1.9Ghz. See here: http://en.wikipedia.org/wiki/Kernel_(computing) . It's basically the same in Android.
Theonew said:
The Kernel has a major effect on the rom. Changing a kernel can make a rom much better or far worst. Kernels allow many customizations in the rom like overclocking. Here's an example of this: Kernel A may allow your device to be overclocked to 1.2Ghz and Kernel B may allow your device to be overclocked to 1.9Ghz. See here: "could not quote this url due to noobiness" . It's basically the same in Android.
Click to expand...
Click to collapse
Thanks for the description man that really specified it for me.
Ok, learning a bit at a time is good Anyone want to take me under their wing and teach me about writing code and creating my own ROMs?
The first thing I want to say is that my English is not really good. I hope you understand my questions.
I have an idea for a new Android rom, but I'm faced with a dilemma. I want to have as much as possible supported devices, so I also can just build a launcher apk which can be installed through Google Play. In this way all mobile devices with the minimal platform version can use it. The biggest problem is that I don't only want a replacement for the application launcher but also the notification drawer and everything else. Is it possible to replace them also? I don't think so, so I think I'll work on a custom rom.
The next problem is which base rom I would use if I really build a custom rom. It's most likely to use AOSP as base because it's clean. The question is which version of AOSP: Gingerbread, Ice Cream Sandwich, or the newest version Jelly Bean. You would probably say Jelly Bean because this is the newest version. The problem is the phone support. Gingerbread is supported on most phones. If I build ICS or JB the phones which are supported by Cyanogenmod are easy to support, because I can use their device files. The only problem is that my phone, the Samsung Galaxy Gio is not officially supported and the unofficial port is not really stable. I don't think it's a big problem to use this device files and just wait till the developer makes it more stable, but I don't know for sure.
The last thing I want to know is if it's really that simple to support multiple devices. If I read tutorials about porting existing roms to your device they all say you just have to add your device files to the source and compile it. But they never say something about the kernel. Most devices need another kernel because their hardware is different isn't it? Please explain me how this works.
I'm sorry about this hazy story, but please help me before I make wrong choices. Thanks on purpose.
Wietse
WietsedeVries said:
The biggest problem is that I don't only want a replacement for the application launcher but also the notification drawer and everything else. Is it possible to replace them also? I don't think so, so I think I'll work on a custom rom.
Click to expand...
Click to collapse
These changes you are talking about can be done. They are system changes so not supported by the android app installer.
Eg: Your notification drawer, status bar are part of SystemUI.apk. The source for this is can be found in the AOSP source code under android/frameworks/base/...
You can make your modifications, compile it into an apk and then make a flashable zip to replace the current one (or push it via a rooted adb console).
or you can compile the entire source code into a flashable zip (eg CM7,9 etc..) and use it a replacement ROM with your modifications.
This is the line between an application under the android runtime and the android runtime itself.
these files, under framework are part of the OS. so to provide a customized version of the operating itself is what people like to call ROMs.
Now ROMs (like any OS) are device dependant. Windows has the code to run in a lot of different hardware configs, but android aims to be small. It should have only the minimum required code to efficiently run itself on a device.
Thats the kernel. The kernel communicates with the hardware and so the rest of the hardware can happily talk to a working kernel and expect the hardware to function as advertised. Kernel is a simple program which goes into the RAM on system start and sits there directing the operation of the phone.
Kernel devs work on making sure the hardware and the android runtime work perfectly together. Now, in this imperfect world, not all sources are open, even though they should be. and therein the issue lies.
If you want to compile android from source and make sure it works on your phone, first you need to make sure you have the kernel with all the changes(patches) to it made by the vendor (chap who made the phone and bullied you into buying it) to get it working on your hardware.
If you dont have that, you have to do it yourself. Or wait for someone else to do it.
once you can compile android and get it working on your phone with all the itty bitty hardware working A-OK.. then you can browse through the source, make changes as per your individual requirements and compile it into a ROM.
see the changes to the OS are separate from the changes to the kernel. The kernel changes are for hardware-software interaction so they are phone SPECIFIC.
but changes to your custom android OS (ROM) can be "cherry-picked" from other ROM/gerrit/AOSP/CM/AOKP sources and put inside your own source tree to get included in your build.
so if you have all the device / kernel stuff from a working android distribution, you can take the source of another android distribution and swap the device stuff into it and see if it works.
hope this helps.
wingie6200 said:
These changes you are talking about can be done. They are system changes so not supported by the android app installer.
Eg: Your notification drawer, status bar are part of SystemUI.apk. The source for this is can be found in the AOSP source code under android/frameworks/base/...
You can make your modifications, compile it into an apk and then make a flashable zip to replace the current one (or push it via a rooted adb console).
or you can compile the entire source code into a flashable zip (eg CM7,9 etc..) and use it a replacement ROM with your modifications.
This is the line between an application under the android runtime and the android runtime itself.
these files, under framework are part of the OS. so to provide a customized version of the operating itself is what people like to call ROMs.
Now ROMs (like any OS) are device dependant. Windows has the code to run in a lot of different hardware configs, but android aims to be small. It should have only the minimum required code to efficiently run itself on a device.
Thats the kernel. The kernel communicates with the hardware and so the rest of the hardware can happily talk to a working kernel and expect the hardware to function as advertised. Kernel is a simple program which goes into the RAM on system start and sits there directing the operation of the phone.
Kernel devs work on making sure the hardware and the android runtime work perfectly together. Now, in this imperfect world, not all sources are open, even though they should be. and therein the issue lies.
If you want to compile android from source and make sure it works on your phone, first you need to make sure you have the kernel with all the changes(patches) to it made by the vendor (chap who made the phone and bullied you into buying it) to get it working on your hardware.
If you dont have that, you have to do it yourself. Or wait for someone else to do it.
once you can compile android and get it working on your phone with all the itty bitty hardware working A-OK.. then you can browse through the source, make changes as per your individual requirements and compile it into a ROM.
see the changes to the OS are separate from the changes to the kernel. The kernel changes are for hardware-software interaction so they are phone SPECIFIC.
but changes to your custom android OS (ROM) can be "cherry-picked" from other ROM/gerrit/AOSP/CM/AOKP sources and put inside your own source tree to get included in your build.
so if you have all the device / kernel stuff from a working android distribution, you can take the source of another android distribution and swap the device stuff into it and see if it works.
hope this helps.
Click to expand...
Click to collapse
Thank you very very much for your explanation! It's a pity it's impossible to hit multiple times "Thanks".
I think I'm going to make a modified SystemUI.apk but you didn't tell the application launcher is also in this file. Did you just forget this or is this stored in another file/folder? And the lock screen? And I want also to replace the boot animation if it's possible.
If I take the source files of the SystemUI.apk of AOSP ICS, does this work on every phone running ICS? Included CM, AOKP and other (smaller) custom roms? And my last question: Since SystemUI.apk a apk file is, is it possible to edit these files through Eclipse and build it in Eclipse? Or do I get errors?
//Edit:
Still another question: How much work is it to, as example, port a modified Gingerbread SystemUI.apk to ICS? (Or vice versa)
WietsedeVries said:
Thank you very very much for your explanation! It's a pity it's impossible to hit multiple times "Thanks".
I think I'm going to make a modified SystemUI.apk but you didn't tell the application launcher is also in this file. Did you just forget this or is this stored in another file/folder? And the lock screen? And I want also to replace the boot animation if it's possible.
If I take the source files of the SystemUI.apk of AOSP ICS, does this work on every phone running ICS? Included CM, AOKP and other (smaller) custom roms? And my last question: Since SystemUI.apk a apk file is, is it possible to edit these files through Eclipse and build it in Eclipse? Or do I get errors?
//Edit:
Still another question: How much work is it to, as example, port a modified Gingerbread SystemUI.apk to ICS? (Or vice versa)
Click to expand...
Click to collapse
Only way is through exchanging the png files since porting the whole .apk is impossible.
Sent from my Jelly Beaned Ace
Thanks for the answer. And do you also know the answers of the other questions?
Sent from my GT-S5660 using xda app-developers app
WietsedeVries said:
If I take the source files of the SystemUI.apk of AOSP ICS, does this work on every phone running ICS? Included CM, AOKP and other (smaller) custom roms? And my last question: Since SystemUI.apk a apk file is, is it possible to edit these files through Eclipse and build it in Eclipse? Or do I get errors?
//Edit:
Still another question: How much work is it to, as example, port a modified Gingerbread SystemUI.apk to ICS? (Or vice versa)
Click to expand...
Click to collapse
There are two roads you can go now - one is use apktool to *decompile* apk the apk file that you've taken from your phone, it doesnt convert the app to java source code but java bytecode in .smali files (like an assembly version of the source) but you will have access to the resource files (xml, images etc..) so you can replace them and create some new themes.
http://forum.xda-developers.com/showthread.php?t=1814441
http://forum.xda-developers.com/showthread.php?t=1760133
And no - a GB systemUI.apk will *NOT* work on ICS. It is very probable that any changes you make through any of these methods can brick you phone. So make sure you have CWM and a nandroid backup.
If you want to add/edit functionality within the source code of systemUI.apk, you need to learn how to compile Android from Source. i would suggest getting hold of the CyanogenMod source tree for your device and playing around with it.
Ginger bread is CM7 and ICS is CM9.
http://forum.xda-developers.com/showthread.php?t=1552090
once you have the full source tree, you'll find a folder called android/frameworks/base/core/...something../systemui/..
this will contain the javasource code for your application. Here you can edit stuff to your hearts content!
Note that this cannot be compiled standalone by eclipse. The Android build system must be used to compile this (cuz its a system app).
a nice resource i used when i was doing the same thing :laugh:
http://iserveandroid.blogspot.in/2011/01/how-to-implement-your-own-status-bar.html
cheers and have fun.
hey guys, just wondering how difficult it would be to do this and keep the finger print scanner. i (with no android developing experience) tried following a few tuts to try and port a 4.3 rom with little success, i managed to get it to start installing in cwm then to give a permission failure or something similar so yeah just a quick question
+1
Sent from my SM-N900V using Tapatalk
hectorz321 said:
hey guys, just wondering how difficult it would be to do this and keep the finger print scanner. i (with no android developing experience) tried following a few tuts to try and port a 4.3 rom with little success, i managed to get it to start installing in cwm then to give a permission failure or something similar so yeah just a quick question
Click to expand...
Click to collapse
Permission failure? Noob here too
I am guessing the ROM you tried to port checks for the Model number of the phone before flashing. What ROM did you try to port to and if you could post the instructions here we will make this the porting thread
Given that HTC One has all the custom ROM's and kernels we need devs or someone like us who can follow instructions to start doing it. I am sure we will get help from one another and end up with custom ROM's for the MAX.
I was also thinking of doing this but just to start with i don't want to look at the fingerprint scanner and may be later we could get it working.
I am certain most people would be willing to not have a working fingerprint scanner, as a trade off for a few custom roms/kernels...
Well to start you need to make sure your Meta-Inf directory is one from the Max, you should be porting from something with the same board as well which would give you less headaches in the long run. The One would be a good starting port since they use the same boards (msm8960 Snapdragon 600) The updater script in Meta-Inf needs to be pointing to the correct device. For example and this is just an example in the beginning of the updater script which is really the instructions for flashing the rom in recovery shouldn't say something like "get prop blah blah m7vzw" the m7 being the model # should be t6vzw if you were using a Verizon device etc etc.. All mount points need to be exactly what the Max's mount points are otherwise it will never flash.. The original One mount points aren't the same as the One Max. Also the kernel from the Max is a must, plus in system/lib you need the modules as well as hardware. In system/bin you need vold, vold is device specific. In system/etc you need vold.fstab again device specific stuff. The you need the hardware directory, which is touch capacitive buttons and LED's and what not. Those may be the same as the One since they are laid out the same.. The audio should most likely be the same but you would need to remove all the Beats Audio crap from system/etc since the One Max isn't a beats device.. GSM to GSM may be an easy port, CDMA to CDMA may be a little more difficult. Although they use libril-qc-qmi-1.so I think it is, that may be a typo but that's something like what the lib path will point to, the code may be slightly different in telephony for CDMA LTE devices. That would be found in framework.jar if applicable framework2.jar..
I could most likely easily get a port done, I'm just very limited to time.. Some of the tutorials out there are very generic and would kind of work well if you have 2 very identical devices with minor changes and manufactured around the same time small example would be like the HTC Desire and the HTC Thunderbolt.. That's a pretty straight forward port with some minor audio tweaks since sound image in system/etc is different and that as well are devices that would require a RIL hack as stated above with framework.jar... That right there would be strictly smali/baksmali hacking which I have some knowledge with but by no means a master of it lol... That is unless we had source for certain things but that isn't likely by no means... If anyone is interested in getting to work I'm more then willing I just sometimes have a hectic schedule... There is more to porting then just a few quick changes if you want a clean solid daily driver port... I started to port MIUI V5 just haven't really had much of a chance to test it. I have 3 MIUI ports built all slightly altered to eventually test different hacks..
The reason I chose MIUI V5 to port is because a good deal of HTC MIUI ROMs are based heavily on Sense.. Not many of them are AOSP based anymore which to me is kind of a shame.... The Chinese must have gotten tired of so many ports popping up with a lot of broken stuff because they all use to be AOSP based and to get them ported required a ton smali hacks and now when you decompile an actual source built official chinese MIUI rom and you diff out lets say services.jar from CM and services.jar from MIUI for every line of code like cdmareceiver.smali in CM in MIUI it's i.smali then cdmareceiver$1.smali in CM in MIUI it's 23.smali.... Those aren't actual lines those are just examples but they made it damn near impossible to properly diff stuff out.. You'd literally have to go through thousands and thousands upon thousands of lines to figure out which matches what and then make the changes you feel like need to be made and then hope you didn't break something in the process.... It sucks lol...
So yeah most of the HTC devices are now MIUI converted Sense based builds and I'm hoping are a little easier to port with less changes!! But I guess we'll see?!?!
Like I said, anyone wanting to work with me I will be more then glad to lend my knowledge of Android! I need someone to get me motivated again. I really miss working on Android and building stuff porting stuff whatever.. It's just fun! Plus we desperately need some form of a custom Android really really bad.... All of us do... I mean I'm Verizon, but Sprint, the International crew, all of us....
Lets pool all of our knowledge together and do some work!!! To all reading this if you are down contact me in this thread or PM me and lets get busy!
Murrda said:
Well to start you need to make sure your Meta-Inf directory is one from the Max, you should be porting from something with the same board as well which would give you less headaches in the long run. The One would be a good starting port since they use the same boards (msm8960 Snapdragon 600) The updater script in Meta-Inf needs to be pointing to the correct device. For example and this is just an example in the beginning of the updater script which is really the instructions for flashing the rom in recovery shouldn't say something like "get prop blah blah m7vzw" the m7 being the model # should be t6vzw if you were using a Verizon device etc etc.. All mount points need to be exactly what the Max's mount points are otherwise it will never flash.. The original One mount points aren't the same as the One Max. Also the kernel from the Max is a must, plus in system/lib you need the modules as well as hardware. In system/bin you need vold, vold is device specific. In system/etc you need vold.fstab again device specific stuff. The you need the hardware directory, which is touch capacitive buttons and LED's and what not. Those may be the same as the One since they are laid out the same.. The audio should most likely be the same but you would need to remove all the Beats Audio crap from system/etc since the One Max isn't a beats device.. GSM to GSM may be an easy port, CDMA to CDMA may be a little more difficult. Although they use libril-qc-qmi-1.so I think it is, that may be a typo but that's something like what the lib path will point to, the code may be slightly different in telephony for CDMA LTE devices. That would be found in framework.jar if applicable framework2.jar..
I could most likely easily get a port done, I'm just very limited to time.. Some of the tutorials out there are very generic and would kind of work well if you have 2 very identical devices with minor changes and manufactured around the same time small example would be like the HTC Desire and the HTC Thunderbolt.. That's a pretty straight forward port with some minor audio tweaks since sound image in system/etc is different and that as well are devices that would require a RIL hack as stated above with framework.jar... That right there would be strictly smali/baksmali hacking which I have some knowledge with but by no means a master of it lol... That is unless we had source for certain things but that isn't likely by no means... If anyone is interested in getting to work I'm more then willing I just sometimes have a hectic schedule... There is more to porting then just a few quick changes if you want a clean solid daily driver port... I started to port MIUI V5 just haven't really had much of a chance to test it. I have 3 MIUI ports built all slightly altered to eventually test different hacks..
The reason I chose MIUI V5 to port is because a good deal of HTC MIUI ROMs are based heavily on Sense.. Not many of them are AOSP based anymore which to me is kind of a shame.... The Chinese must have gotten tired of so many ports popping up with a lot of broken stuff because they all use to be AOSP based and to get them ported required a ton smali hacks and now when you decompile an actual source built official chinese MIUI rom and you diff out lets say services.jar from CM and services.jar from MIUI for every line of code like cdmareceiver.smali in CM in MIUI it's i.smali then cdmareceiver$1.smali in CM in MIUI it's 23.smali.... Those aren't actual lines those are just examples but they made it damn near impossible to properly diff stuff out.. You'd literally have to go through thousands and thousands upon thousands of lines to figure out which matches what and then make the changes you feel like need to be made and then hope you didn't break something in the process.... It sucks lol...
So yeah most of the HTC devices are now MIUI converted Sense based builds and I'm hoping are a little easier to port with less changes!! But I guess we'll see?!?!
Like I said, anyone wanting to work with me I will be more then glad to lend my knowledge of Android! I need someone to get me motivated again. I really miss working on Android and building stuff porting stuff whatever.. It's just fun! Plus we desperately need some form of a custom Android really really bad.... All of us do... I mean I'm Verizon, but Sprint, the International crew, all of us....
Lets pool all of our knowledge together and do some work!!! To all reading this if you are down contact me in this thread or PM me and lets get busy!
Click to expand...
Click to collapse
this was exciting to read, best of luck
I am going to get Ubuntu installed today and then Android Kitchen here i come!
pradeepvizz said:
I am going to get Ubuntu installed today and then Android Kitchen here i come!
Click to expand...
Click to collapse
You can always use Cygwin on windows. there is a how to cook a rom tutorial in the General Android Dev forum.
DeadPhoenix said:
You can always use Cygwin on windows. there is a how to cook a rom tutorial in the General Android Dev forum.
Click to expand...
Click to collapse
Thanks, i just installed it via virtual box without disturbing my system.
Just got android kitchen up and running, on prting sides of things got further this time, into aroma installes but error 7 which suggested earlyer is to do with mount points, if anyone could happen to help with theese it would be fab ))
Ok this is good start, i am proud of us here
I have got Android Kitchen running on my Ubuntu via virtual box.
I tried to set my working folder and tried tried to import my TWRP stock ROM backup. It seems like Android kitchen will require a CWM backup and TWRP does not seems to work.
With the TWRP backup i got this error
NON-YAFFS/NON-TAR FILE FORMAT DETECTED IN ROM
Click to expand...
Click to collapse
So i have just restored stock ROM on my phone, flashed CWM and now backing up my Stock ROM to COOK ANDROID
@[email protected] did you miss this thread just kidding, I know you have got a hectic schedule.
Again i am extremely happy to see ppl starting to develop ROM's!
Thanks for your encouragement @Murrda
No problem.. I'm home from work already and I'm off for the next 3 days so I'm actually going to get back to working on some ports. Anyone need a hand with anything as far as questions or setting up Linux or a dev environment please feel free to hit me up!
pradeepvizz said:
Ok this is good start, i am proud of us here
I have got Android Kitchen running on my Ubuntu via virtual box.
I tried to set my working folder and tried tried to import my TWRP stock ROM backup. It seems like Android kitchen will require a CWM backup and TWRP does not seems to work.
With the TWRP backup i got this error
So i have just restored stock ROM on my phone, flashed CWM and now backing up my Stock ROM to COOK ANDROID
@[email protected] did you miss this thread just kidding, I know you have got a hectic schedule.
Again i am extremely happy to see ppl starting to develop ROM's!
Thanks for your encouragement @Murrda
Click to expand...
Click to collapse
Murrda said:
No problem.. I'm home from work already and I'm off for the next 3 days so I'm actually going to get back to working on some ports. Anyone need a hand with anything as far as questions or setting up Linux or a dev environment please feel free to hit me up!
Click to expand...
Click to collapse
heyy i could use some help doing this part in android kitchen. straight from android kitchens page but i can't seem to get the recovery.fstab out anyway! im on t6ul verson of the max by the way thanks
/HIDE (sorry dont know how to get this to work (forum noob here too)
Create a file under the kitchen's /tools/edify_defs folder, with the name being the same as the value of ro.product.device (found in your device's /system/build.prop file).
If the stock ROM images for your device contain the recovery.img file, extract its files from the kitchen menu: Advanced --> Tools for boot image --> Extract from boot.img/recovery.img in any folder. Then, open up its ramdisk folder, and look for /system/etc/recovery.fstab or /etc/recovery.fstab or similar FSTAB file location. Open this file to find the mount points.
See the template file in the edify_defs folder to see how to set the mount points inside the file you created. Look at the other files in that folder for examples on how to do it.
managed to flash something and get mounting things sorted ))), getting an interesting navy green screen when booting now, will let you know on further developments. its a vanilla android rom i tried insertcoin-m7-google-edition_5.0-1 to be exact
hectorz321 said:
managed to flash something and get mounting things sorted ))), getting an interesting navy green screen when booting now, will let you know on further developments. its a vanilla android rom i tried insertcoin-m7-google-edition_5.0-1 to be exact
Click to expand...
Click to collapse
Good start mate! awesome!
update, getting a boot logo now which is great but im in a bootloop and have no idea where to start, iv been looking on trying to get logcat and such running but no success yet. Any advise anyone?
hectorz321 said:
update, getting a boot logo now which is great but im in a bootloop and have no idea where to start, iv been looking on trying to get logcat and such running but no success yet. Any advise anyone?
Click to expand...
Click to collapse
Which guide are you following? i just cooked a ROM today first time. I made the stock ROM for the T6UL.
---------- Post added at 08:34 PM ---------- Previous post was at 08:34 PM ----------
ooo, Merry Christmas everyone
Yeah I've been trying to port gpe over to the max but I think I need the gpe kernel ported too.. I used the Max Sense kernel for it and I get a bootloop or frozen boot logo after install with no hope of getting a logcat. I didn't move the Max sense update-binary but don't think that would be an issue, both since Its gpe and I'm using aroma..
Sent from my HTC One using XDA Premium 4 mobile app
HolyAngel said:
Yeah I've been trying to port gpe over to the max but I think I need the gpe kernel ported too.. I used the Max Sense kernel for it and I get a bootloop or frozen boot logo after install with no hope of getting a logcat. I didn't move the Max sense update-binary but don't think that would be an issue, both since Its gpe and I'm using aroma..
Sent from my HTC One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Got to exactly the same point as you, reading several tutorials online i came across this interesting line "To port Sense you have to unpack the boot.img of your base rom and edit the init.rc to change the bootclasspath and match it with the port one" which is what iv done but also got stuck in a bootloop, looking at the two kernels are are a few differences in them. I think that might be they key.
hectorz321 said:
Got to exactly the same point as you, reading several tutorials online i came across this interesting line "To port Sense you have to unpack the boot.img of your base rom and edit the init.rc to change the bootclasspath and match it with the port one" which is what iv done but also got stuck in a bootloop, looking at the two kernels are are a few differences in them. I think that might be they key.
Click to expand...
Click to collapse
Yeah, i know for the kernel, without being able to mess with the zimage, the sense max kernel lacks the init.environ.rc from gpe, the fstab file is different(at least file extension), and there's a few things that point to sense files or folders that don't exist on gpe. Currently there is no released source for the max yet :'( so unless someone knows how to do it manually and hasn't shared HOW to do so, I just have to wait.. Hopefully it won't be too long.
Sent from my HTC One using XDA Premium 4 mobile app