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.
Lemme get some things out of the way.. I am a noob. I have searched. I have read some of the results from the search. I am overwhelmed by the 20+ pages of results (lol). I am not 100% sure this is the correct forum for this (not sure where else would be ).. I believe this is one of those things where I need help based on my situation.. Ok, so here I go.
I wish to start porting ICS to my phone. That's my goal. I have general understanding of how linux works, but I do not know much about the android specifics of how they work, or what needs to be modified for this to work. I do not plan to use the kitchen tool as I wish to learn this the hard way. I believe this will help me become more understanding in what I am doing. However, at this point I don't and that's why I'm here. My phone model is irrelevant almost because its prepaid and usually the communities don't even recognize their existence.. at least that's how I feel about it. But I digress. My phone is the zte warp by boost mobile and I am here to learn hopefully the things that will get me started on porting ICS to this phone. I right now believe that the best thing for me to learn is how the android related files work because as it is, I only looked at guides on how linux works and I understand most of it. I'm not sure that's the best thing that will help me port ics, but I'm certain it is important.
Please help me figure out where I should start in learning how to port ICS to my phone basically.
Thanks XDA
anyone? I am quite serious about wanting to do and go into this but I have yet one thread that anyone's ever replied to.. (or post iirc) which puts a damper on me
Snake X said:
Lemme get some things out of the way.. I am a noob. I have searched. I have read some of the results from the search. I am overwhelmed by the 20+ pages of results (lol). I am not 100% sure this is the correct forum for this (not sure where else would be ).. I believe this is one of those things where I need help based on my situation.. Ok, so here I go.
I wish to start porting ICS to my phone. That's my goal. I have general understanding of how linux works, but I do not know much about the android specifics of how they work, or what needs to be modified for this to work. I do not plan to use the kitchen tool as I wish to learn this the hard way. I believe this will help me become more understanding in what I am doing. However, at this point I don't and that's why I'm here. My phone model is irrelevant almost because its prepaid and usually the communities don't even recognize their existence.. at least that's how I feel about it. But I digress. My phone is the zte warp by boost mobile and I am here to learn hopefully the things that will get me started on porting ICS to this phone. I right now believe that the best thing for me to learn is how the android related files work because as it is, I only looked at guides on how linux works and I understand most of it. I'm not sure that's the best thing that will help me port ics, but I'm certain it is important.
Please help me figure out where I should start in learning how to port ICS to my phone basically.
Thanks XDA
Click to expand...
Click to collapse
From my limited knowledge, I think it is a huge task undertaking, you can download Android source code from Google, the hard part will be the device driver development and porting for Linux kernel (and maybe portion of Android). If you are lucky, you can use the existing phone bootloader (or you have to port one). Understanding the inner of the phone (different chip set may need different device driver) will be another challenging task.
by the device driver development, you mean all the libs that go into the phone? Couldn't I just copy/paste the pre-existing libs that are already made for the phone? Also the phone im working with is a bit strange really.. noone has been able to compile the kernel from its source and get it to boot yet.. when it was compiled the zImage was different than that of the stock one.
And yeah, I have downloaded the aosp source.. I just need to know where to start at and the processes involved really
Snake X said:
by the device driver development, you mean all the libs that go into the phone? Couldn't I just copy/paste the pre-existing libs that are already made for the phone? Also the phone im working with is a bit strange really.. noone has been able to compile the kernel from its source and get it to boot yet.. when it was compiled the zImage was different than that of the stock one.
And yeah, I have downloaded the aosp source.. I just need to know where to start at and the processes involved really
Click to expand...
Click to collapse
To answer you question no the drivers and lib files are different for aosp based rooms then they are for the stock OEM from. The first step will be to get a working kernel. Without anything you do will be pointless
I'm somewhat interested in the same thing, and from what I've gathered, you'll need to do these things to begin ROM development:
1. Read every page on the AOSP site and grab a copy of the AOSP source. It probably wouldn't hurt to read the regular Android developer wiki as well.
2. Learn about Linux driver development:
http://lwn.net/Kernel/LDD3/ (this is apparently considered THE BOOK on Linux driver development)
http://www.freesoftwaremagazine.com/articles/drivers_linux
3. Learn pretty much every detail about your phone and its hardware, especially when it comes to how ROMs are installed on it. For example, my phone (the Droid X2) has a locked bootloader, so 2nd init has to be used to boot new ROMs, and this makes it so that we cannot update the kernel.
You can usually find this sort of information on your phone manufacturer's website. Sometimes they even post the source code to their phone's drivers, which is helpful.
4. Look at other ROMs (preferably for your phone) and see how they work. The source code is freely available for most popular ROMs.
For example: CyanogenMod keeps their source code in a public git repository: https://github.com/cyanogenmod
5. Get to work on porting!
I would highly recommend starting with something smaller, however, just as a start. One good jumping-off point is probably this guide: http://forum.xda-developers.com/showthread.php?t=1272270
If any part of this was wrong, or if I left something out, somebody feel free to correct me, I'm still a noob.
Thank you so much for your direction, however,, android kitchen.. im not sure about that because isnt that only ment for htc devices? My phone is made by zte
what device do you even have?
if it's stuck officialy on 2.1 or 2.2 there's no hope that if you even port it that it'll work
its the zte warp from boost mobile (prepaid). Btw if I compile an aosp ics launcher and put that on my phone whats the chances of that working?
edit: it uses 2.3.5
Well Sebastian responded on android forums, apparently zte is very bad at version control with their kernel sources. So when they complete one project, they use the same source for the next project, and what they release could be for anything. Apparently the blade source had the same issues, it took him a while to get them to correct the source
Sent from my N860 using Tapatalk
Yeah I noticed that there were ppl saying there were things similar but I'm not sure what will work or what won't.. guess its time to start a petition on zte to release the source code lol
edit: seems like zte's bein a bad company and violated the GNU GPL license for not providing a complete source code.. I compiled an email and sent it to someone who can proof read it and send it to the right person for this kinda thing.. danggit zte
First a short question. What is the device configuration.(For example:https://github.com/TeamICS/android_device_htc_heroc) Which information does it contain? I don't think it's the whole Rom, but they update it, change stuff and so on?
Now my actual question:
I want to port a Kernel+System on an unsupported device.
Where do I have to start. Is there a difference between building it from source or port one from a similar device? Is one solution slower, more complicated or anything? There are many tutorials for porting, just bundle a system with a working kernel, but what to do if I want to have the Kernel also?
How do I extract the Device Proprietary Files without an github of the device?
Links, short explanation of the steps or anything else would be helpful.
I am sorry if this post seems to be ill informed, but I am searching and searching and can't find really helpful information..
chaoskoch said:
First a short question. What is the device configuration.(For example:https://github.com/TeamICS/android_device_htc_heroc) Which information does it contain? I don't think it's the whole Rom, but they update it, change stuff and so on?
Now my actual question:
I want to port a Kernel+System on an unsupported device.
Where do I have to start. Is there a difference between building it from source or port one from a similar device? Is one solution slower, more complicated or anything? There are many tutorials for porting, just bundle a system with a working kernel, but what to do if I want to have the Kernel also?
How do I extract the Device Proprietary Files without an github of the device?
Links, short explanation of the steps or anything else would be helpful.
I am sorry if this post seems to be ill informed, but I am searching and searching and can't find really helpful information..
Click to expand...
Click to collapse
First off what device do you have?
This link might be helpful
How to Port Android to Another Device
Now in regard to your questions i'll do my best to answer them best I can. The device configuration think of it as a fingerprint every fingerprint is unique (Although some a very similar), basically when building from source is tells the build what device you want the version of android your compiling to run on. They update and change the device configuration to reflect changes in the different versions of Android (Going from Gingerbread to ICS for example). Porting Kernels is not easy if you don't know C, things about embedded systems, basic Linux knowledge, among other skills but take a look at Guidance regarding Kernel porting, and what do you mean by port system? Here is a basic place to start for kernels AOSP Building Kernels and Building Your First Kernel. Yes their is a difference between porting a kernel and building from source, porting implies taking a kernel from device A and porting it to device B, while building from source means your building directly for device A. Porting in your case is probably going to be harder then building from source. If you want to have the kernel also again you have to modify it to run on the device you are porting it too. To extract proprietary files you have to hook your device up to your computer, turn on usb debugging, and using ADB run these commands:
Code:
cd ~/android/system/device/motorola/sholes/ # Replace Motorola and Sholes with your vendor such as HTC, Samsung, etc. and your device codename
Then run:
Code:
./extract-files.sh
Look at this guide for more info Compiling ICS from Source. Hope this helps you in some way :good:.
So I'll start by saying, if you read any of the current porting guides, it's basically impossible to build CM for a device unless you already have it running on the device... So that's not very helpful.
I am working on porting CM10 to the Ouya, I have the build environment set up fine, I can build a perfectly working CWM recovery from source for it, but when I build CM10 it doesn't boot, nothing even shows up on the screen. I am pretty sure this is due to some missing proprietary blobs from the Ouya, but since no one has made a proprietary-files.txt for it yet, I'm left in the unenviable postion of having to do it myself. I have no problem with doing it, I simply don't know how. I tried using the file from the tf700t source (because the hardware is the most similar) but got no better result. Now I've spent 2 days searching fourms, google, etc. to find a guide to create a proprietary-files.txt, but all I can find is a mess of sites telling you how to use an existing one...
Can anyone help me with this, or am I out of luck? Alternatively, does anyone know an IRC channel I could find an expert in? Fattire and Dalingrin come to mind for their work on the nook color and HP touchpad. If they could make those devices work they should be able to help me fix the ouya with no trouble...
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