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.
Related
Okay so I'm currently downloading this 'Opensource_Update4.zip' file from Opensource, which I assume is the Official Kernel?
Just a few quick questions that I'd appreciate your help with guys:
1. Am I correct in what I just said above?
2. If so, do I just flash the file through ODIN?
3. Will this wipe my phone back to factory settings?
4. Will this affect my device being rooted?
Thanks in advance
New_World_Order said:
1. Am I correct in what I just said above?
Click to expand...
Click to collapse
No.
New_World_Order said:
2. If so, do I just flash the file through ODIN?
Click to expand...
Click to collapse
Again: no.
New_World_Order said:
3. Will this wipe my phone back to factory settings?
Click to expand...
Click to collapse
You will not be able to flash this, as it's not a flashable kernel, but SOURCE CODE.
So many wrong things in just one post
VAXXi said:
No.
Again: no.
You will not be able to flash this, as it's not a flashable kernel, but SOURCE CODE.
So many wrong things in just one post
Click to expand...
Click to collapse
Woaaaaaah I need a huge slap.
Would you be so kind as to explain please? :$
Sent from my GT-I9100 using XDA
Not really, as it's quite long
But the tl;dr version is: what Samsung published today is the source code (human readable code) for the ICS kernel. The ICS kernel is the "core" of the system, if you want. By compiling the source code, you obtain the machine code (specifically one zImage file) which runs on your device.
They are forced to publish the sources due to GPL requirements, but they're not very helpful in doing this. Inside the source code, there's still binary code (device drivers, etc) which cannot be published due to various agreements with the hardware manufacturers. Having this source code, even incomplete as it is, allows developers to see how the binary code is treated; this way, they can improve their code or even develop open-source replacements for the closed binary part of the kernel.
VAXXi said:
Not really, as it's quite long
But the tl;dr version is: what Samsung published today is the source code (human readable code) for the ICS kernel. The ICS kernel is the "core" of the system, if you want. By compiling the source code, you obtain the machine code (specifically one zImage file) which runs on your device.
They are forced to publish the sources due to GPL requirements, but they're not very helpful in doing this. Inside the source code, there's still binary code (device drivers, etc) which cannot be published due to various agreements with the hardware manufacturers. Having this source code, even incomplete as it is, allows developers to see how the binary code is treated; this way, they can improve their code or even develop open-source replacements for the closed binary part of the kernel.
Click to expand...
Click to collapse
Hahahaa okay thanks...
I think I'll just leave it alone! :')
Sent from my GT-I9100 using XDA
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
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 ?
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
Complete Source for the MediaTek MT6589 is available at Sony Open Source Archives
I have confirmed that it is full and shows only warnings while building and builds without errors.
What Next?The config?
It is the full source for the Xperia C. :good:
dev0xteam said:
Complete Source for the MediaTek MT6589 is available at Sony Open Source Archives
I have confirmed that it is full and shows only warnings while building and builds without errors.
What Next?The config?
Click to expand...
Click to collapse
I believe the config file is device dependent so will be different for a116......
still if anyone takes up the project of building it for a116 he has to modify the config :fingers-crossed:
here is kernel source of mmx canvas HD aka fly iq451
https://disk.yandex.ru/public/?hash=VJjzmkQPL8/elQ2+VKi89/k0nd//iBWRDiIhNZOCrzg=&locale=ru
Dj_Ignatius said:
here is kernel source of mmx canvas HD aka fly iq451
https://disk.yandex.ru/public/?hash=VJjzmkQPL8/elQ2+VKi89/k0nd//iBWRDiIhNZOCrzg=&locale=ru
Click to expand...
Click to collapse
Is it complete?
dev0xteam said:
Is it complete?
Click to expand...
Click to collapse
i think yes..
Ok. The sony source is not fully complete but.enough to build a kernel. Still there is some problem in config or something else which is not allowing the kernel to compile..
Sent from my A116 using xda app-developers app
As many people have pointed out, this isn't full source. There has yet to be a "release" of FULL source yet. There are a lot of kernel stuff around, but kernel isn't a problem at this time because mediatek and its vendors are fairly good about upgrading kernel. What I and many others want is the missing Android build end of the source. Even Sony didn't release this piece. There is a list of whats missing in the sauce. They have a script that packages the stuff that will build only a kernel and it pulls out the MediaTek crap. look in
Code:
16.0.A.0.36/mediatek/build/android
to see what i mean. its just a basic skeleton but no actual android stuff. CD into tools and you'll see the script
Code:
filter.py
has a list of all the sources they wont release. So when people say stuff like "FULL SOURCE FOR MEDIATEK" look into it first. AFAIK MediaTek has never released this source to anyone but its partners. IE: sony, zte, cubot, etc. Sony may have released the most complete source, they havent released all of it. And i dont think anyone ever will. I've sent MediaTek countless emails and have never recieved a response. Anyway this source is a good start if someone wants to look into overclock(which i dont believe is possible at this time with the source we have) but again i havent looked at it yet. but i digress.
konnorrigby said:
As many people have pointed out, this isn't full source. There has yet to be a "release" of FULL source yet. There are a lot of kernel stuff around, but kernel isn't a problem at this time because mediatek and its vendors are fairly good about upgrading kernel. What I and many others want is the missing Android build end of the source. Even Sony didn't release this piece. There is a list of whats missing in the sauce. They have a script that packages the stuff that will build only a kernel and it pulls out the MediaTek crap. look in
Code:
16.0.A.0.36/mediatek/build/android
to see what i mean. its just a basic skeleton but no actual android stuff. CD into tools and you'll see the script
Code:
filter.py
has a list of all the sources they wont release. So when people say stuff like "FULL SOURCE FOR MEDIATEK" look into it first. AFAIK MediaTek has never released this source to anyone but its partners. IE: sony, zte, cubot, etc. Sony may have released the most complete source, they havent released all of it. And i dont think anyone ever will. I've sent MediaTek countless emails and have never recieved a response. Anyway this source is a good start if someone wants to look into overclock(which i dont believe is possible at this time with the source we have) but again i havent looked at it yet. but i digress.
Click to expand...
Click to collapse
A general question :- i previously had mmx a75 which of course didn't had the sources but overclocking through mtkcpu from playstore was achieved..!! So why our device can't be overclocked using the same app..??
Sent from my A116 using xda premium
Hopefully this means we get cyanogen based ROMs soon
Sent from my Canvas HD running X-flare V2 ROM
axis.meister said:
Hopefully this means we get cyanogen based ROMs soon
Sent from my Canvas HD running X-flare V2 ROM
Click to expand...
Click to collapse
Did you read the thread?
Sent from my Evo 3D CDMA using XDA Premium 4 mobile app
konnorrigby said:
Did you read the thread?
Sent from my Evo 3D CDMA using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Read the OP and got my hopes high. Read your post now and ...
lets hope Mediatek actually releases full sources in the future.
konnorrigby said:
As many people have pointed out, this isn't full source. There has yet to be a "release" of FULL source yet. There are a lot of kernel stuff around, but kernel isn't a problem at this time because mediatek and its vendors are fairly good about upgrading kernel. What I and many others want is the missing Android build end of the source. Even Sony didn't release this piece. There is a list of whats missing in the sauce. They have a script that packages the stuff that will build only a kernel and it pulls out the MediaTek crap. look in
Code:
16.0.A.0.36/mediatek/build/android
to see what i mean. its just a basic skeleton but no actual android stuff. CD into tools and you'll see the script
Code:
filter.py
has a list of all the sources they wont release. So when people say stuff like "FULL SOURCE FOR MEDIATEK" look into it first. AFAIK MediaTek has never released this source to anyone but its partners. IE: sony, zte, cubot, etc. Sony may have released the most complete source, they havent released all of it. And i dont think anyone ever will. I've sent MediaTek countless emails and have never recieved a response. Anyway this source is a good start if someone wants to look into overclock(which i dont believe is possible at this time with the source we have) but again i havent looked at it yet. but i digress.
Click to expand...
Click to collapse
http://www.hacktohell.org/2013/07/mediatek-mt6589-complete-source.html#.Ui5G3sanojp
can this be the full source? i am not a dev so idk anything about it there is a link in the link i gave u maybe u can see it and tell us
so any good news about custom kernel?
Is this enough to build a custom kernel atleast?
Sent from my Micromax A116 using Tapatalk