Is there a simple way of finding all proprietary/vendor files for porting CM or other AOSP based ROMs?
My phone is running Android 5.1 and I wanted to port CM12.1 to it but having trouble finding these proprietary files, similar devices use different files and I can't seem to understand how people who ported ROMs for them found their list of files for proprietary-blobs.txt
Related
Hey Guys,
My Android lacks development, the only ROMs availible are just apk mods and build.prop edits. I am planning to build CM or some other AOSP-based ROM for my Phone. I found the source code for Qualcomm phones at CodeAurora: https://www.codeaurora.org/xwiki/bin/QAEP/WebHome
My Android runs 2.3.5 and the ro.product.board is msm7627a.
The problem is, there are 2 Gingerbreads for my msm7627a... "gingerbread" and "gingerbread_chocolate". And if I select one of them, I am presented with tons of other options.
I have built software from source in Ubuntu but something tells me that Android is completely different. Can somebody please point me in the right direction? After I find my device's source code, how will I use it to port CM?
And Mainly, which one is my Android's?
Note: I have attached the build.prop of my Rooted Stock ROM.
Hi
Short and sweet, I am busy getting into ROM development, and as exercise to get a better grasp on what is going on, I mostly dabbled with AOSP until yesterday. I am in the process of porting Cyanogenmod 10.2 to Galaxy S2 (i9100).
While going through the CM instructions, there was a segment on how to extract "proprietary blobs" from CM running on the device in question. This is required as part of the build for hardware specific reasons they did not give too much details about.
I just have one query. Has anyone tried to, or know if it is possible to do this blob extraction from ROMs other than CyanogenMod?
That's all folks.
Ok so I have built cm11 for my device (galaxys s 4g), and ported cm11 from another device to (aries -> galaxy s 4g). CM11 has too much going on IMO and I just want pure aosp on my device, the problem is that there are no (recent) aosp roms for my device, or any similar devices.
So how do I port my device to a different flavor of android when there are no roms of that flavor?
What have I tried?
So far I have setup the aosp 4.4 repo to a different folder than my cm11 repo (the build environment files should be the same right?)
I tried using the manifest from the cm11 rom and buidling with aosp,that didnt work it didnt even finish compiling =(.
I browsed the aosp source for other devices by the same manufacturer, but everything looked completely different from what I am used to.
The most helpful guide in this direction sofar has been cyanogenmods guide but it has left me with more questions than answers.
What [I think] I need to know
Custom recovery - aosp doent seem to include a recovery, the cm guide says to start with the recovery. So i need to know if I need to add a custom recovery to aosp, or if i can install aosp roms from twrp without breaking it.
Binaries - It is safe to use the binaries used in CM11 for aosp/any other flavor, or are the binaries flavor specific? (im thinking they are safe to use, but not entirely sure).
Device files - what files should be safe to use for any flavor?
Kernel - Cm builds the kernel when you compile the rom (or so it says), does aosp build the kernel when you build the rom, or do I have to build the kernel separately? Is it safe to say use a CM11 kernel with an aosp rom?
There are Lott's of threads for porting for Rom's to any device..
But most of describes to use same android versions for base and port...
But i want try porting CM12 for Galaxy Core...
I am not a developer but still want to use Cm12 on my device .. So instead of asking some one i would love to port it by myself:thumbup:
hareshsangar said:
There are Lott's of threads for porting for Rom's to any device..
But most of describes to use same android versions for base and port...
But i want try porting CM12 for Galaxy Core...
I am not a developer but still want to use Cm12 on my device .. So instead of asking some one i would love to port it by myself:thumbup:
Click to expand...
Click to collapse
That is hard to do without a background in building from source and knowing some coding and kernel stuff. You don't have lollipop yet on that device so it will be even harded. You can't just copy some files. You need a device tree and modify the kernel and then build cm12 from source.
Thanks for taking time .. But i would if i can port CM11 at least
hareshsangar said:
Thanks for taking time .. But i would if i can port CM11 at least
Click to expand...
Click to collapse
Well I don't know about your device (it's basically the same for all Qcom device, I don't know about MTK). Porting by copying files is less reliable then building from source (well it's way easier). It's very very hard to solve bugs when copying files and if the base has bugs the port might be even more buggy.
Hello,
I'm new to Android modding and I already read many guides, tutorials, etc. But every time people build a new ROM they don't use the AOSP but the CM source. So I like to build a clean, not modified ROM from the AOSP sources but when I tried the first time, I didn't know what I need to do because Google's guide only tells about how to build the ROM for a Nexus device and not for mine (I'm using the Motorola Moto G 2014 as primary device).
So first of all, is it possible to build the AOSP for my device or do I have to make any modifications in sources (or it is for one person just not possible to port the AOSP to my device) ?
If it is possible, what do I have to do? Is there any guide or tutorial how to build the AOSP for a non Google phone in general?
Thanks for responses
firefligher