Is there a good tutorial on how to compile CM10 (or any CM) for an unsupported device? In particular, I have a MIONE_PLUS phone manufactured by XiaoMi, which is not officially supported by CM. I'd like to experiment with creating a CM10 port to my device.
I've synced the CM10 repo, but I'm confused about what the next step should be. In terms of proprietary binary files / configuration files, how do I know what files are necessary? And how do I compile CM10 with an existing Linux kernel grabbed from my stock ROM?
Any advice is appreciated. Thanks!
first you need to get the propietary files for MI-one (wish i dubt that miui give it to the comunity).
blackwing182 said:
first you need to get the propietary files for MI-one (wish i dubt that miui give it to the comunity).
Click to expand...
Click to collapse
Will a general target, say, mini_armv7a, work?
Dominator008 said:
Will a general target, say, mini_armv7a, work?
Click to expand...
Click to collapse
As long as you find a phone from the same board type should be pretty easy getting boot.
Sent from my Galaxy Nexus using xda premium
lithid-cm said:
As long as you find a phone from the same board type should be pretty easy getting boot.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
MI-ONE is msm8660 so he can look to similar boards like HTC sensation , Samsung galaxy s2 T989 ( Hercules) , ATT samsung Skyrocket as an example
Related
Hi guys,
I went to check for the HTC DX source code on htcdev.com, and saw there were around 31 sources, but they're are all CRC's...
Could anyone please explain to me, what is a CRC? I tried googling it, but it didn't really help.
Sent from my HTC Desire X using xda premium
kernel source
Lloir said:
kernel source
Click to expand...
Click to collapse
I have been reading up on making roms, mostly about AOSP and CM, since they have best info and tutorials and such. But at some point, they both say to port to a new device you need to have the proprietary files (non open source device-specific software) to be able to build a working rom, using ./extract-files.sh or ./proprietary-files.sh.
From what I've read, identifying these files is mostly educated (not my case, lol) guessing, trial and error,... But I was wondering : is this CRC source code what they are talking about and would there be a way to get all the necessary proprietary files from it ?
infernal77 said:
I have been reading up on making roms, mostly about AOSP and CM, since they have best info and tutorials and such. But at some point, they both say to port to a new device you need to have the proprietary files (non open source device-specific software) to be able to build a working rom, using ./extract-files.sh or ./proprietary-files.sh.
From what I've read, identifying these files is mostly educated (not my case, lol) guessing, trial and error,... But I was wondering : is this CRC source code what they are talking about and would there be a way to get all the necessary proprietary files from it ?
Click to expand...
Click to collapse
Search for vendor protou github.
Google it. You'll find proprietary files.
Regards
Sent from my Desire using xda app-developers app
Yasir Javed Ansari said:
Search for vendor protou github.
Google it. You'll find proprietary files.
Regards
Sent from my Desire using xda app-developers app
Click to expand...
Click to collapse
Thanks, Yasir, I know lli0r made a device and vendor tree, but he said the vendor tree might be incomplete. He tried to make us a CM9 but hasn't got the device itself. I also read you can extract the files from a running device, but for that you need extract-files.sh or proprietary-files.sh, which isn't in there. I'm sure I can google and find one of those files from another device and try to run them on mine, but they're probably device-specific as well. And there isn't one of those files in lli0r's github. I checked that I'm sorry, I am ompletely new to Android, let alone building roms, but I love to just experiment a bit
Btw, when are you getting your Desire X ?
I tried to build android from source (nexus target) following google's instructions and this operation was succesfull. Now I would like to know which variations I have to do for targeting galaxy s3. I saw that in cyanogenmod they added some script to do this thing but to see them I think that I should download all their source code + android source code again.
I even tried to search some tutorial to build the rom and I found only methods that make use of already built material, like the ones with kitchen.
XDA Developers forum Android Hacking and Chef Central may be of more use .
jje
I think you need s3's proprietary binaries to make this work.
More information
http://source.android.com/source/building-devices.html
Sent from my GT-I9300 using xda premium
qtwrk said:
I think you need s3's proprietary binaries to make this work.
More information
http://source.android.com/source/building-devices.html
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
Supposing that I got the binaries, then there is the problem that I can't use the lunch command specifying the GT-I9300 device.
This script is for if you are compiling android from source and want to convert one tree to another name. For instance, we have been using a modified mako tree so if you wanted to start compiling for the Optimus G you would download the mako tree and modify it to our device. That would normally mean you need to replace all instances of the word mako with geeb or whatever you want to call it. and also rename some files as well. this script does it all for you.
just put it in the device tree directory and run it and it will prompt you for the rest.
it will ask you about the current device name and the new device name. the current device name should be the name of the device you are switching from and the new device name should be whatever you want to rename it to. both should be just one word like mako or skyrocket or geeb or geeb_att_us (underscores are OK).
Download -------> name-changer.py
Click to expand...
Click to collapse
Click to expand...
Click to collapse
the script requires python to run (it works in python 2.5....not sure about python3)
just run (in the device tree directory):
Code:
./name-changer.py
please let me know if you have any suggestions or bugs. thanks
So if I'm reading this correctly, you would be able to have the sources for say paranoid android, then you put this in there and it would edit the sources to work for our phone?
Or am I way over thinking this?
Sent from my Nexus 4 using Tapatalk 2
MrZim4 said:
So if I'm reading this correctly, you would be able to have the sources for say paranoid android, then you put this in there and it would edit the sources to work for our phone?
Or am I way over thinking this?
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
This is for the device source.... Not android source. Its for converting one tree to another phone. I just made it because I tend to do this manually all the time so I just wanted to automate the process.
Sent from my LG-E970 using xda app-developers app
Please can a mood Luck thread till further notice.
Thank you
LaputaCake said:
Hello who wants to help me build cm10.1 and cm10 for you guys as ive found one for £45 need a device tree and testers
Click to expand...
Click to collapse
I can help you testing your builds
HTC Desire X || Android 4.1.2 || mySENSEdx5 RC3.0
I will help testing too if I have time
I will help to with the testing.
LaputaCake said:
Hello who wants to help me build cm10.1 and cm10 for you guys as ive found one for £45 need a device tree and testers
Click to expand...
Click to collapse
You can find everything here : http://forum.xda-developers.com/showthread.php?t=2437255 .
Good luck.
Yeah. I can hlep with testing as well; when you provide your sources, I can assist in building too, when I have some time left (now there is hardly any, but it will be a bit better after christmas, I hope)
trying to repo sync and getting this even using protou project init:
repo init -u git://github.com/ProtouProject/android.git -b cm-10.1
but get this:
Code:
fatal: '../CyanogenMod/android_abi_cpp.git' does not appear to be a git repository
fatal: Could not read from remote repository.
Please make sure you have the correct access rights
and the repository exists.
error: Cannot fetch CyanogenMod/android_abi_cpp
I think this one is source for cm 10.2 only, if I'm not mistaken. For cm 10.1 or 10, there are only sources by atis112 (please correct me if I'm wrong).
Sent from my HTC Desire X using XDA Premium 4 mobile app
dansou901 said:
I think this one is source for cm 10.2 only, if I'm not mistaken. For cm 10.1 or 10, there are only sources by atis112 (please correct me if I'm wrong).
Sent from my HTC Desire X using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Its alright i fixed by rebuilding envireoemtndfvbisduvbsdnzvh. just repo syncing now
LaputaCake said:
Its alright i fixed by rebuilding envireoemtndfvbisduvbsdnzvh. just repo syncing now
Click to expand...
Click to collapse
Ill be using this device tree
https://github.com/ProtouProject/android_device_htc_protou/tree/cm-10.1
Yeah,that is the device tree we are using.
Not sure how did you get to Protou Project github,we only use common from there.
Everything else is on Protoype-U github.
EDIT : Also if you need help with compiling tell me,i can setup a virtual ubuntu and do some work.
I can't dual boot it now because i need a whole partition for my school project.
nightwalkerkg said:
Yeah,that is the device tree we are using.
Not sure how did you get to Protou Project github,we only use common from there.
Everything else is on Protoype-U github.
EDIT : Also if you need help with compiling tell me,i can setup a virtual ubuntu and do some work.
I can't dual boot it now because i need a whole partition for my school project.
Click to expand...
Click to collapse
Does anyone have sim unlocking method working (Not paid)
Also how bigga hard drive do you have as ive only got 78.1g for ubuntu and 69.97gigs for windows
That should do for building cm if you're not building for more devices.
Sent from my HTC Desire X using XDA Premium 4 mobile app
I can help with compiling as well . Got about 200GB free disk space on Ubuntu lying around , waiting to be useful xD
Will setup & sync everything tomorrow though , right now I'm a little busy .
I can also help with testing , logcatting etc .
LaputaCake said:
Does anyone have sim unlocking method working (Not paid)
Also how bigga hard drive do you have as ive only got 78.1g for ubuntu and 69.97gigs for windows
Click to expand...
Click to collapse
Tried DesireC method... Not working, I was looking at it the other day and couldn't really find anything useful. Happy to see you Hear on The Dx subforum
dansou901 said:
That should do for building cm if you're not building for more devices.
Sent from my HTC Desire X using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Im building cm10.2 for my phone aswell better cut down on windows but i got nice 500gb external hdd
And due to S-ON there is no free sim unlocking method for now. But there are several paid methods which should work.
Sent from my HTC Desire X using XDA Premium 4 mobile app
dansou901 said:
And due to S-ON there is no free sim unlocking method for now. But there are several paid methods which should work.
Sent from my HTC Desire X using XDA Premium 4 mobile app
Click to expand...
Click to collapse
ill have to get unlocked or vodafone
LaputaCake said:
ill have to get unlocked or vodafone
Click to expand...
Click to collapse
anyone know anywhere to get one?
Is it really important to get the phone unlocked ?
You can just get a new sim card and run it,if you don't wont this phone to be your primary phone that is.
I had made a thread about creating a custom ROM for Android over here: http://forum.xda-developers.com/general/xda-assist/building-custom-android-rom-t3526514#post70277383 and Art Vanderlay suggested I post here, so here it is.
I own the BLU Energy X 2, and I am in need of the Device Tree and Vendor Blobs for the phone to create a custom ROM based off of CyanogenMod. My device currently has CyanogenMod on it, however it's an unofficial port for the BLU Studio Selfie. I am not sure how the dev of that ROM got these files, however the Infinix Hot 2 is a "clone" of that device, so he may have just ported it from there, or it may have not even needed porting at all Anyways, for me to create a custom ROM based off of CyanogenMod, I need the Device Tree and Vendor Blobs. I do have the ProjectConfig file if that helps.
These files are usually somewhere on GitHub, but due to the development community for BLU devices in general being almost non-existant, these files are nowhere to be found. So, how can I get these files for my device to start building a custom ROM? Thanks
If you need any other information, please reply.
Device Specs:
BLU Energy X 2
Model #: E050U
Android Version: 5.1 Lollipop
Kernel Version: 3.10.74+
Chipset: MT6580
Use Device and Vendor trees from similar devices, change names and other stuff like your device in the configs...
I'm noobie too, but this is how people make it for MTK devices
Audriuskins said:
Use Device and Vendor trees from similar devices, change names and other stuff like your device in the configs...
I'm noobie too, but this is how people make it for MTK devices
Click to expand...
Click to collapse
Ok, thanks, I'll look for some similar devices. Will any similar MTK device work? What needs to be similar? OS versions? Chipset? Kernel version?
What do I need to look for?
Thanks
NateDev473 said:
Ok, thanks, I'll look for some similar devices. Will any similar MTK device work? What needs to be similar? OS versions? Chipset? Kernel version?
What do I need to look for?
Thanks
Click to expand...
Click to collapse
Must be on the same chipset from my experience, Kernel and OS doesn't matter.
Audriuskins said:
Must be on the same chipset from my experience, Kernel and OS doesn't matter.
Click to expand...
Click to collapse
So all I need to do is find a device with similar specs, and same chipset that has device tree and vendor blobs already created? And then I just modify it to fit my specific device?
NateDev473 said:
So all I need to do is find a device with similar specs, and same chipset that has device tree and vendor blobs already created? And then I just modify it to fit my specific device?
Click to expand...
Click to collapse
Something like that, you should look up :
http://forum.xda-developers.com/showthread.php?t=2274332
Audriuskins said:
Something like that, you should look up :
http://forum.xda-developers.com/showthread.php?t=2274332
Click to expand...
Click to collapse
Do the devices need to be officially CM supported, to get the device tree and vendor blobs? Because I found a couple of devices like the ZenFone Go that has an unofficial version of CM, but I can't find the device tree for that device.
These come from the oem. While the directions posted sometimes work it is dirty hacking at best and never stable. This is why developers stay away from mtk devices and they are really only used in cheap devices.
NateDev473 said:
Do the devices need to be officially CM supported, to get the device tree and vendor blobs? Because I found a couple of devices like the ZenFone Go that has an unofficial version of CM, but I can't find the device tree for that device.
Click to expand...
Click to collapse
Search on Github
Audriuskins said:
Search on Github
Click to expand...
Click to collapse
Ok, so I've discovered that the Infinix Hot 2 has mostly the same specs as my device, and that it's basically a clone of the Studio Selfie, which is the device that I used to unofficially port CyanogenMod to my device, so that's a good sign. Anyways, CyanogenMod was built for the Infinix Hot 2 from source, and they provided links to GitHub. It does say though that the Infinix Hot 2 is Android One. Is that a big problem?
Thanks
NateDev473 said:
Ok, so I've discovered that the Infinix Hot 2 has mostly the same specs as my device, and that it's basically a clone of the Studio Selfie, which is the device that I used to unofficially port CyanogenMod to my device, so that's a good sign. Anyways, CyanogenMod was built for the Infinix Hot 2 from source, and they provided links to GitHub. It does say though that the Infinix Hot 2 is Android One. Is that a big problem?
Thanks
Click to expand...
Click to collapse
No idea x)
I guess you can try xd
Audriuskins said:
No idea x)
I guess you can try xd
Click to expand...
Click to collapse
Ok, thanks
Audriuskins said:
No idea x)
I guess you can try xd
Click to expand...
Click to collapse
I found this on GitHub, is that what I am looking for in terms of the vendor files and stuff like that? http://imgur.com/a/KUcxC
NateDev473 said:
I found this on GitHub, is that what I am looking for in terms of the vendor files and stuff like that? http://imgur.com/a/KUcxC
Click to expand...
Click to collapse
Clone whole tree, rename everything to yours.
In device tree check if configs are like your device
Audriuskins said:
Clone whole tree, rename everything to yours.
In device tree check if configs are like your device
Click to expand...
Click to collapse
Ok, I will. If some of the configs are different for my device, I can just replace the values with the ones that work for my device right? Also in that other device's lib volder, they have a lot less stuff then my stock ROM lib folder, is that fine?
NateDev473 said:
Ok, I will. If some of the configs are different for my device, I can just replace the values with the ones that work for my device right? Also in that other device's lib volder, they have a lot less stuff then my stock ROM lib folder, is that fine?
Click to expand...
Click to collapse
I can't help you very much, because I'm new in MTK development ://
Audriuskins said:
I can't help you very much, because I'm new in MTK development ://
Click to expand...
Click to collapse
Would it be possible to then just upload my own files? Because on my phone I have all those files that are there for the other device. That would be better, I think, because they would be specific to my phone... If you don't know it's fine
NateDev473 said:
Would it be possible to then just upload my own files? Because on my phone I have all those files that are there for the other device. That would be better, I think, because they would be specific to my phone... If you don't know it's fine
Click to expand...
Click to collapse
I dont know