Content moved. Go here: http://forum.xda-developers.com/showthread.php?t=3231109
Thank you
thank you for sharing this
md5= 550a231310527ce322f6c0e3c0c0596c
thanks for this post, urm can you do jelly bean 4.2.2 for me :good:
are you sure this is full source? because i think full source comes around 15 or 20 gb. This is merely 3.2 gb.
falconnoob said:
are you sure this is full source? because i think full source comes around 15 or 20 gb. This is merely 3.2 gb.
Click to expand...
Click to collapse
Yaa bro... this is the full cm12 source... Highly compressed... I have my friends who have been using this... I myself am using this bro! If u extract the file... U get around 15GB...
kirito9 said:
thanks for this post, urm can you do jelly bean 4.2.2 for me :good:
Click to expand...
Click to collapse
4.2.2? Yaa sure... I had my friend uploaded it before... Here you go:
http://www.androidfilehost.com/?fid=23060877490004404
Link updated @kirito9 bro! Please copy-paste in browser...
This is the cm10.1 source.. (Android 4.2.2)
Born to be a coder said:
thank you for sharing this
Click to expand...
Click to collapse
Anytime Aman!
Please Dont Post on the Q/A thread.. I wont look at it... Post here and press the thanks button!
Awsome
You are really awsome can u do a favour to me
can you provide me the llvm and stlport folder compressed of cm11 source present in cm11/external/....
Please
Thanks again @regalstreak :laugh:
---------- Post added at 10:52 AM ---------- Previous post was at 10:48 AM ----------
4.2.2? Yaa sure... I had my friend uploaded it before... Here you go:
Download
This is the cm10.1 source.. (Android 4.2.2)
WORKING NOW THANKS :good: :laugh:
regalstreak said:
Yaa bro... this is the full cm12 source... Highly compressed... I have my friends who have been using this... I myself am using this bro! If u extract the file... U get around 15GB...
Click to expand...
Click to collapse
can you upload the compressed .repo folder too so that we can update it?i mean repo synced later on? and also is it cm12.1 or cm12?
falconnoob said:
can you upload the compressed .repo folder too so that we can update it?i mean repo synced later on? and also is it cm12.1 or cm12?
Click to expand...
Click to collapse
It is cm12... Not 12.1 as it is still in development stages and unstable. Of the .repo folder... Ill see... Ill compress it and see.. If size is less than 5gb.. Ill upload it... Ill update u guys on this till thursday..
P.S. Im happy dad bought me a new laptop! Lenovo z50-70.. The i7 model...
Help
Brother i need serious help im trying to get my proprietary files via .sh and it says cannot create directory permission denied and says adbd cannot run tried adbd insecure (it disables usb debugging in my case)
HOW TO FIX
the ss of error is attached plz help
sandeep.sethi said:
Brother i need serious help im trying to get my proprietary files via .sh and it says cannot create directory permission denied and says adbd cannot run tried adbd insecure (it disables usb debugging in my case)
HOW TO FIX
the ss of error is attached plz help
Click to expand...
Click to collapse
try
Code:
cd (your directory before the cm12 source)
chmod -R 777 cm12
chmod -R a+x cm12
No success
regalstreak said:
try
Code:
cd (your directory before the cm12 source)
chmod -R 777 cm12
chmod -R a+x cm12
Click to expand...
Click to collapse
It is showing same error.
Actually you can update to cm12.1 using a cm12 repo. Repo is basically a collection of git object, uploading this would serve no purpose, .repo folder is needed.
Sent from my Moto G using XDA Free mobile app
i have fixed propreitory files but now it shows this error
http://pastebin.com/Ux2Fia5h
got error.. need assistance.
regalstreak said:
Hey Guys! I have found many people like me with low bandwidth are not able to sync the cyanogenmod source. So here I present to you. Cyanogenmod 12 Source (Android 5.0.2) as of 29/03/2015! The original source size including the .repo folder is 29 GB. In the .repo folder, there are temporary files. So I have not included the .repo folder as you dont need it to compile. The size of source without .repo folder is 14 GB. And it is highly compressed to only 3.2 GB! This has purely done by me. So. Here you go:
You Cannot Update the sources as they do not have the .repo folder!
Cyanogenmod 12
DOWNLOAD
FAQ
Q1> Is this really Cyanogenmod 12 source?
Ans: Yeah! I have compressed it! and it is real Cyanogenmod 12 source.
Q2> How To Extract Source?
Ans:
Open Terminal
Download 7zip if not done before (sudo apt-get install p7z-full)
Now cd to the drive where you have downloaded the sources
7z x *.7z
Now you have extracted the source
Q3> Will you upload the .repo folder?
Ans:Sorry Guys. I cannot. The highly compressed size ofthe .repo folder is 10GB which makes it worthless to upload as you would not download because of low bandwidth. I also cant upload because of low bandwidth. More over, you cannot update to cm12.1 with the repo folder. You can just update the minor changes committed by the cyanogenmod maintainers. So, In short, Im not uploading. Sorry forthe inconvenience.
You cannot extract source with GUI on the Archive Extractor. So, Try the method I mentioned
Q3> The size is 2 GB or 3.2 GB? I saw the size 2 GB on Androidfilehost!
Ans: The size is 3.2 GB. I had kept the laptop whole night for uploading. So maybe it did not show the correct size there!
Please press the "Thanks Button" if I helped you and quote me if you have a problem!
Click to expand...
Click to collapse
got this error when ran make -j4 otatools.
Checking build tools versions...
************************************************************
You are attempting to build with the incorrect version
of java.
Your version is: Picked up JAVA_TOOL_OPTIONS: -javaagent:/usr/share/java/jayatanaag.jar java version "1.7.0_79" OpenJDK Runtime Environment (IcedTea 2.5.6) (7u79-2.5.6-0ubuntu1.15.04.1) OpenJDK 64-Bit Server VM (build 24.79-b02, mixed mode).
The required version is: "1.7.x"
Please follow the machine setup instructions at
https://source.android.com/source/initializing.html
************************************************************
build/core/main.mk:171: *** stop. Stop.
need help...
thanks..
I was trying to build for s duos 2
butt this error came after 3 hours
almamun512 said:
I was trying to build for s duos 2
butt this error came after 3 hours
Click to expand...
Click to collapse
Please reattach the picture.
jackey31 said:
got this error when ran make -j4 otatools.
Checking build tools versions...
************************************************************
You are attempting to build with the incorrect version
of java.
Your version is: Picked up JAVA_TOOL_OPTIONS: -javaagent:/usr/share/java/jayatanaag.jar java version "1.7.0_79" OpenJDK Runtime Environment (IcedTea 2.5.6) (7u79-2.5.6-0ubuntu1.15.04.1) OpenJDK 64-Bit Server VM (build 24.79-b02, mixed mode).
The required version is: "1.7.x"
Please follow the machine setup instructions at
https://source.android.com/source/initializing.html
************************************************************
build/core/main.mk:171: *** stop. Stop.
Install the correct java version bro...
need help...
thanks..
Click to expand...
Click to collapse
regalstreak said:
Please reattach the picture.
Click to expand...
Click to collapse
These are the screenshots ........................
bro can u upload cm11 sources ?? i have it but when i try to generate boot.img recovery files .. it alwasy gave me error of .. "unpackbootimg is not found"
i have tryd make -j4 otatools but still error occured ..
i will be very thankfull to you if u find me a fix for it else upload cm11 source as highly compressed as u did with cm12
almamun512 said:
These are the screenshots ........................
Click to expand...
Click to collapse
your build tree has problems... correct it... source is correct
Related
Requirements :
OS linux Ubuntu 12.04 32bits
2Gb RAM with 3Gb swap or above
Processor dual core or above
120Gb Harddisk or above
Fast internet connection ( i have no this )
First download this file
Installer SDK and Build packages by squadzone modified for me
you will get installerBuildRomGalmin.sh , run this file via Terminal on Ubuntu!
Code:
chmod a+x ~/installerBuildpackages.sh
installerBuildpackages.sh
Create the Directories
You will need to set up some directories in your build environment.
To create them:
mkdir -p ~/bin
mkdir -p ~/android/system
Install the Repository
Enter the following to download make executable the "repo" binary:
curl https://dl-ssl.google.com/dl/googlesource/git-repo/repo > ~/bin/repo
chmod a+x ~/bin/repo
NOTE: You may need to reboot for these changes to take effect.
Now enter the following to initialize the repository:
cd ~/android/system/
repo init -u git://github.com/CyanogenMod/android.git -b gingerbread
repo sync -j16
Device repo !
clone its
choose branch master
put on device tree or replace totoro folder on device tree
(/device/samsung/totoro)
Vender folder clone its
pu on vendor folder !
(/vendor/samsung/totoro)
Download RomManager
NOTE: This only needs to be done when an update to RomManager is released. If you are-up-to date, you may skip to Building CyanogenMod.
Download RomManager which is needed by the build:
~/android/system/vendor/cyanogen/get-rommanager
Configure Build & Compile
Now, the environment must be configured to build and the ROM compiled, from code, for the Galaxys2.
. build/envsetup.sh && brunch totoro
Notes :
based on tutorial for galaxy mini by squadzone
the device repo created for me ( add credits if you use its )
sorry bad english !
changelog :
1.0
-initial tutorial for cm7 galaxy y ( may need some modifications! )
reserved for more updates if necessary !
Thanks for this buddy :good:
OFF : Any news about CM9 ?
wow.. reserved sir whitexp.. long time no post? D
I WIIL TRY IT BOR
By SOMKLL
But this Cyanogen has the same bugs,right?
whitexp what about cm9 ? when will u continue xD
and great guide
This message is COPYRIGHTED to me and stolen from:My post
Cyanogen 7/9 only get developed again when the gpu driver become released
Awesome tutorial sir...
Just one question...if we still have GPU restrictions while compiling CM7/9/10, then what is the use of the tutorial? Is there any update I should be aware of?
I'm not at all disrespecting OP's efforts...I respect him...he is doing commendable job for this device..hat's off! this question is just out of curiosity!
everyone needs brodcom drivers,without it nothing is possible.
PREMOLIKES said:
everyone needs brodcom drivers,without it nothing is possible.
Click to expand...
Click to collapse
Well it's still possible to boot it, so yeah. It's a handy tutorial, LEARN to appreciate guys! That's the reason why SGY devs are leaving, 1 by 1, because of you people that whine! Thank them for the effort!
PREMOLIKES said:
everyone needs brodcom drivers,without it nothing is possible.
Click to expand...
Click to collapse
Without this kind of tutorial and with gpu drivers will you make cm7 for sgy????
Awesome tutorial sir!!
Tutotial is good.no doubt.I said drivers are a stumbling block.
PREMOLIKES said:
Tutotial is good.no doubt.I said drivers are a stumbling block.
Click to expand...
Click to collapse
Drivers will be here soon! I am gettin ready already!
Sent from my GT-S5360 using XDA
Mohamed.Anwar said:
Thanks for this buddy :good:
OFF : Any news about CM9 ?
Click to expand...
Click to collapse
what gaming rom r using
Exellent tut buddy.:thumbup::thumbup:
sent while doin' some burnouts
hell_lock said:
Drivers will be here soon! I am gettin ready already!
Sent from my GT-S5360 using XDA
Click to expand...
Click to collapse
really?
broadcom will release their drivers or are you just joking around because i just installed windows again on my pc ...
cosminx13 said:
really?
broadcom will release their drivers or are you just joking around because i just installed windows again on my pc ...
Click to expand...
Click to collapse
A suggestion from me.you can use both os like dualboot.for info about this try google
MANY GREEEEETZ!!!
Hello guys i'm here with my first guide of how to build cyanmobile from source for galaxy fit ......
As you all might know cyanmobile went opensource thanks to squadzone now we can compile it from source with our own modifiactions.....
Requirements
1)Linux machine (recommended 64bit and ubuntu) with atleast 50gb free space
2)Common sense of how to use google and fix errors
3)Basic knowledge of git and its commands
4)A possibilty of bricking your fit
5)A fast and stable internet connection
now lets get started
Assuming we have linux installed
installing required build packages
from terminal
HTML:
sudo apt-get install git-core gnupg flex bison gperf libsdl1.2-dev libesd0-dev libwxgtk2.6-dev squashfs-tools build-essential zip curl libncurses5-dev zlib1g-dev sun-java6-jdk pngcrush schedtool
Note:- All the packages are important dont skip any of them
now making the directories to download the source
HTML:
mkdir -p ~/bin
mkdir -p ~/android/system
here mkdir stands for make directory
~ refers to your home folder (incase if you are a beginner)
Next
making the repo command executable
copy paste this terminal
HTML:
curl https://dl-ssl.google.com/dl/googlesource/git-repo/repo > ~/bin/repo
chmod a+x ~/bin/repo
Reboot your system after executing this
This defines the repo command or the repo command usable on your machine
chmod is giving permissions to the folder a+x is the permissions given don't go deep into this.
Next
Downloading the source
i will be referring execute to copy pasting in the terminal
HTML:
repo init -u git://github.com/CyanMobile/android_cyanmobile.git -b gingerbread
now
repo sync
alternatives
repo sync -jx
here x can be anything depends on your internet speed ther will x number of simultaneous download if you use the arguement
like if you use
repo sync -j4
There will 4 downloads going on simulatneously
Next after the source has been downloaded you will find someting like this...
syncing working tree 100
now you have the source downloaded
Preparing the build environment
install java jdk6 or jdk 5 using this tutorial
http://codingforme.wordpress.com/2012/05/14/installing-oracle-java-jdk-6-or-7-on-ubuntu-12-04/
Install the android sdk following this tutorial
http://www.howtoforge.com/setting-up-an-android-app-build-environment-with-eclipse-android-sdk-phonegap-ubuntu-11.04
not testsed on jdk 7 so better use 6 or 5
fix its path using "export PATH=$PATH:"ur sdk path""
ur sdk path depends on where you install it
install adb using this guide
http://forum.xda-developers.com/showthread.php?t=921169
Connect your phone with usb debugging enabled and execute this
preferable do this when you are on a cm based rom ..
HTML:
adb devices
if you see something like this its working for you
HTML:
List of devices attached
S5670efac482b device
now go to device > samsung > beni execute extract-files.sh as root use sudo and drag that to terminal and hit enter
now cd into the root of your source folder
HTML:
cd ~/android/system
then
HTML:
source buid/envsetup.sh
HTML:
lunch
you will see all the build properties something like this
HTML:
PLATFORM_VERSION_CODENAME=REL
PLATFORM_VERSION=2.3.8
TARGET_PRODUCT=cyanogen_beni
TARGET_BUILD_VARIANT=eng
TARGET_SIMULATOR=false
TARGET_BUILD_TYPE=release
TARGET_BUILD_APPS=
TARGET_ARCH=arm
TARGET_ARCH_VARIANT=armv6-vfp
HOST_ARCH=x86
HOST_OS=linux
HOST_BUILD_TYPE=release
BUILD_ID=GINGERBREAD
now type make -jx otapackage
x depends on your hardware more it is faster the build
you will find the built one in out/samsung/beni /cm--xxx.zip
Flash it and enjoy
credits
wilfredcool007
vishwanthptl
sakindia123
yajnab
ravi h basawa
adit_pat
squadzone
google
xda
without these guys it wouldnt be possible pree thanks for them plz
1 st reserved
Thumbs up
Nice guide ajay :good:
Its same as the building of cyanogenmod. But to continue this thread u have to first build a copy too for promoting this and the errors while building , so start repo syncing. I am syncing the jelleybean now.
Best of luck for this thread
yajnab said:
Its same as the building of cyanogenmod. But to continue this thread u have to first build a copy too for promoting this and the errors while building , so start repo syncing. I am syncing the jelleybean now.
Best of luck for this thread
Click to expand...
Click to collapse
i am too doing a list of common errors encountered and will update the op
speed_bot said:
i am too doing a list of common errors encountered and will update the op
Click to expand...
Click to collapse
I'm on a low bandwidth. Can u please make a highly compressed .uha or Uharc compression package of the cyanmobile so that i can also help u in building this. not having the cm7 sources too. It cn be a grat sart for making a more modified cyanombile than squadzone.
yajnab said:
I'm on a low bandwidth. Can u please make a highly compressed .uha or Uharc compression package of the cyanmobile so that i can also help u in building this. not having the cm7 sources too. It cn be a grat sart for making a more modified cyanombile than squadzone.
Click to expand...
Click to collapse
dude do this remove all devices and sync only beni and tass the source is small and use aosps prebuilt the download is only 3gb bro...and can plz upload the prebuilt directory for me i will upload frameworks and devices by tmrw for you..........plz i need the prebuilt directory
You rock man, keep up the good work.. thank you..
praveen_kalasa said:
You rock man, keep up the good work.. thank you..
Click to expand...
Click to collapse
thanks bro..
Nice Work
Very useful Guide for Begineers. Keep this thread updated
RishabhAd said:
Very useful Guide for Begineers. Keep this thread updated
Click to expand...
Click to collapse
but only few people responded to it so what can i update with
??
hi.i am trying to build from your how to...will report ...thank you for this...
desalesouche said:
hi.i am trying to build from your how to...will report ...thank you for this...
Click to expand...
Click to collapse
im already compiling for your device
How to build cyanmobile x from source for p500?
thanks
x-dira said:
How to build cyanmobile x from source for p500?
thanks
Click to expand...
Click to collapse
just choose p500 during lunch
building for huawei u8800pro and u8860
hi can i build with 3.0.87 kernel?
or should i use a 2.6.35 one?
can we build only gingerbread or is there possibility to build 4.2.2?
thank you
Nice guide :thumbup:
I'll try it for GalaxyW
desalesouche said:
hi can i build with 3.0.87 kernel?
or should i use a 2.6.35 one?
can we build only gingerbread or is there possibility to build 4.2.2?
thank you
Click to expand...
Click to collapse
u need kernel 2.6 for gb 3.x supports only ics and above.android 4.2.2 is buildable provided u have all drivers and other binaries
K_TECH said:
Nice guide :thumbup:
I'll try it for GalaxyW
Click to expand...
Click to collapse
dude this guide is for galaxy fit but u can build it for w or any device by using the tress specific for that device.
Bump
I wanna try to port this ROM to the LG e739, but I have no idea what to do at this point. I downloaded the sources, but the device tree I have from cm7.2 is just plain, it lacks everything else the other devices have and to be honest I'm overwhelmed. Any help is greatly appreciated
This thread will be kept for troubleshooting issues with CM build by @KINGbabasula
Please report any bugs found in this thread and keep the Original thread clean.
Link to the thread will be posted here when build will be published
Do not ask for ETA.
Rom will be ready when it's ready !!!
ptothej said:
Hi all
I'm working on CM buil for our beloved i9105P a skullface has stopped the development for our device.
I've started to work on one with a big help from Skullface and a tons of tutorials found.
The thing is when it comes to compiling the build o got an error
No rule to make a target `/home/przemo/Source/out/target/product/i9105P/kernel', wymaganego przez `/home/przemo/Source/out/target/product/i9105P/boot.img'. Stop.
Folder structure is set up as follows
kernel is in folder /home/przemo/Source/kernel/samsung/i9105P
and device files from github are in the folder home/przemo/Source/kernel/samsung/i9105P.
What i'm doing wrong ??
Any help appreciated
Click to expand...
Click to collapse
Try putting the kernel zImage in /home/przemo/Source/out/target/product/i9105P/kernel... and renaming it to "kernel"
panda00 said:
Try putting the kernel zImage in /home/przemo/Source/out/target/product/i9105P/kernel... and renaming it to "kernel"
Click to expand...
Click to collapse
But the out folder is being created when compiling CM build
ptothej said:
But the out folder is being created when compiling CM build
Click to expand...
Click to collapse
Oh sorry, I meant /home/przemo/Source/kernel/samsung/i9105P/kernel - put the zImage inside and rename it to "kernel".
Copied the wrong line
EDIT: Oops wait a second!
Will work on it tomorrow, to much computer screen for today
Wysyłane z mojego GT-I9105P za pomocą Tapatalk 2
Ok so kernel issue is done, was a typo in boardconfig file LOL.
Now ther issues
Import includes file: /home/przemo/Source/out/target/product/i9105P/obj/STATIC_LIBRARIES/libvpx_intermediates/import_includes
Import includes file: /home/przemo/Source/out/target/product/i9105P/obj/STATIC_LIBRARIES/libstagefright_mpeg2ts_intermediates/import_includes
Import includes file: /home/przemo/Source/out/target/product/i9105P/obj/STATIC_LIBRARIES/libstagefright_httplive_intermediates/import_includes
Import includes file: /home/przemo/Source/out/target/product/i9105P/obj/STATIC_LIBRARIES/libstagefright_id3_intermediates/import_includes
Import includes file: /home/przemo/Source/out/target/product/i9105P/obj/STATIC_LIBRARIES/libFLAC_intermediates/import_includes
Import includes file: /home/przemo/Source/out/target/product/i9105P/obj/STATIC_LIBRARIES/libopensles_helper_intermediates/import_includes
Import includes file: /home/przemo/Source/out/target/product/i9105P/obj/STATIC_LIBRARIES/libOpenSLESUT_intermediates/import_includes
Export includes file: frameworks/ex/variablespeed/jni/Android.mk -- /home/przemo/Source/out/target/product/i9105P/obj/SHARED_LIBRARIES/libvariablespeed_intermediates/export_includes
Notice file: frameworks/av/media/libstagefright/NOTICE -- /home/przemo/Source/out/target/product/i9105P/obj/NOTICE_FILES/src//system/lib/libstagefright.so.txt
Notice file: frameworks/av/media/libstagefright/colorconversion/NOTICE -- /home/przemo/Source/out/target/product/i9105P/obj/NOTICE_FILES/src//system/lib/libstagefright_color_conversion.a.txt
Notice file: frameworks/av/media/libstagefright/codecs/mp3dec/NOTICE -- /home/przemo/Source/out/target/product/i9105P/obj/NOTICE_FILES/src//system/lib/libstagefright_mp3dec.a.txt
Notice file: frameworks/av/media/libstagefright/codecs/aacenc/NOTICE -- /home/przemo/Source/out/target/product/i9105P/obj/NOTICE_FILES/src//system/lib/libstagefright_aacenc.a.txt
Notice file: frameworks/av/media/libstagefright/matroska/NOTICE -- /home/przemo/Source/out/target/product/i9105P/obj/NOTICE_FILES/src//system/lib/libstagefright_matroska.a.txt
Notice file: frameworks/av/media/libstagefright/timedtext/NOTICE -- /home/przemo/Source/out/target/product/i9105P/obj/NOTICE_FILES/src//system/lib/libstagefright_timedtext.a.txt
Notice file: external/libvpx/NOTICE -- /home/przemo/Source/out/target/product/i9105P/obj/NOTICE_FILES/src//system/lib/libvpx.a.txt
Notice file: frameworks/av/media/libstagefright/mpeg2ts/NOTICE -- /home/przemo/Source/out/target/product/i9105P/obj/NOTICE_FILES/src//system/lib/libstagefright_mpeg2ts.a.txt
Notice file: frameworks/av/media/libstagefright/httplive/NOTICE -- /home/przemo/Source/out/target/product/i9105P/obj/NOTICE_FILES/src//system/lib/libstagefright_httplive.a.txt
Notice file: frameworks/av/media/libstagefright/id3/NOTICE -- /home/przemo/Source/out/target/product/i9105P/obj/NOTICE_FILES/src//system/lib/libstagefright_id3.a.txt
Notice file: external/flac/libFLAC/NOTICE -- /home/przemo/Source/out/target/product/i9105P/obj/NOTICE_FILES/src//system/lib/libFLAC.a.txt
Notice file: frameworks/av/drm/libdrmframework/NOTICE -- /home/przemo/Source/out/target/product/i9105P/obj/NOTICE_FILES/src//system/lib/libdrmframework.so.txt
Notice file: frameworks/av/drm/common/NOTICE -- /home/przemo/Source/out/target/product/i9105P/obj/NOTICE_FILES/src//system/lib/libdrmframeworkcommon.a.txt
Notice file: frameworks/av/media/libstagefright/omx/NOTICE -- /home/przemo/Source/out/target/product/i9105P/obj/NOTICE_FILES/src//system/lib/libstagefright_omx.so.txt
make: *** Brak reguł do zrobienia obiektu `vendor/samsung/i9105P/proprietary/lib/libvorbisidec.so', wymaganego przez `/home/przemo/Source/out/target/product/i9105P/system/lib/libvorbisidec.so'. Stop.
make: *** Oczekiwanie na niezakończone zadania....
Notice file: frameworks/av/media/libstagefright/yuv/NOTICE -- /home/przemo/Source/out/target/product/i9105P/obj/NOTICE_FILES/src//system/lib/libstagefright_yuv.so.txt
Any Ideas ?
Please ignore previous post got it sorted, had to copy lib and etc folders to vendor folder.
Still few issue to resolve, but getting closer
ptothej said:
Please ignore previous post got it sorted, had to copy lib and etc folders to vendor folder.
Still few issue to resolve, but getting closer
Click to expand...
Click to collapse
I m going to try cm10.1 soon
Bt I think I will wait for ur build.. good luck .
ptothej said:
Please ignore previous post got it sorted, had to copy lib and etc folders to vendor folder.
Still few issue to resolve, but getting closer
Click to expand...
Click to collapse
BTW question. Is it with OC Or what ?
warface123 said:
BTW question. Is it with OC Or what ?
Click to expand...
Click to collapse
It's Stock CM so to speak
warface123 said:
BTW question. Is it with OC Or what ?
Click to expand...
Click to collapse
He's basically got to go with stock CM kernel with no changes to the source as to achieve official CM status somewhere along the road.
Sent from my GT-I9105P
panda00 said:
He's basically got to go with stock CM kernel with no changes to the source as to achieve official CM status somewhere along the road.
Sent from my GT-I9105P
Click to expand...
Click to collapse
As there is no custom kernel at the moment, neither do i have time or knowledge to compile custom kernel.
I've decided to compile GM build based on Skullface project.
As Panda00 said it's a long road ahead.
Sorry to interrupt but I try to follow CM build and have some questions:
- Basically we use(d) http://wiki.cyanogenmod.org/w/Doc:_porting_intro as guideline?
- Device configuration is already done -> skullface's github? Is this one for I9105P or also for I9105?
- Can the stock samsung kernel be used with CM or has it to be kernel source from Samsung Open Source?
- As for kernel source I saw different things till now: skullface imported GT-I9105_SWA but for GT-I9105P we need GT-I9105P_JB?
- There are also GT-I9105_CIS and GT-I9105_MEA available at Samsung Open Source. Are those regional stuff or what's the meaning of CIS and MEA? Does it matter which to choose?
- Next step would be trying to build CM (if Samsung stock kernel can be used it would be easier to build CM instead of using kernel source I assume)?
s2+user said:
Sorry to interrupt but I try to follow CM build and have some questions:
- Basically we use(d) http://wiki.cyanogenmod.org/w/Doc:_porting_intro as guideline?
- Device configuration is already done -> skullface's github? Is this one for I9105P or also for I9105?
- Can the stock samsung kernel be used with CM or has it to be kernel source from Samsung Open Source?
- As for kernel source I saw different things till now: skullface imported GT-I9105_SWA but for GT-I9105P we need GT-I9105P_JB?
- There are also GT-I9105_CIS and GT-I9105_MEA available at Samsung Open Source. Are those regional stuff or what's the meaning of CIS and MEA? Does it matter which to choose?
- Next step would be trying to build CM (if Samsung stock kernel can be used it would be easier to build CM instead of using kernel source I assume)?
Click to expand...
Click to collapse
You have a lot of questions. LOL.
Skullface's work is based on I9105P source , but he just misnamed it.
The stock boot.img cannot be used, you have to modify it (just a little bit) to work with CM. If you're using Skullface's work then that was done for you already.
I know that MEA is Middle East and Africa.. so yes they're regions.
Sent from my GT-I9105P
Kernel seems to have been built sucessfully :victory: but I didn't include pawitp's changes yet
Now I'm waiting for the rest to finish :fingers-crossed:
Build has finished but no zip file inside out directory
Update: forget my problem, found out what was missing :victory:
s2+user said:
Build has finished but no zip file inside out directory
Update: forget my problem, found out what was missing :victory:
Click to expand...
Click to collapse
Well done, now i can stop working on mine CM, no point having 2 same builds.
Wysyłane z mojego GT-I9105P za pomocą Tapatalk 2
ptothej said:
Well done, now i can stop working on mine CM, no point having 2 same builds.
Wysyłane z mojego GT-I9105P za pomocą Tapatalk 2
Click to expand...
Click to collapse
Well you 2 could always collaborate; work together.
Sent from my GT-I9105P
panda00 said:
Well you 2 could always collaborate; work together.
Sent from my GT-I9105P
Click to expand...
Click to collapse
Could do
Well after all we need developers for everything else cause I'm no developer
I only wanted to try building CM and there is so much stuff that I want to know about the whole process of porting and building. But after all it's a little beginning :highfive:
This is a PURE AOSP ROM build guide. I have opted not to post an actual AOSP ROM based on 6.0.0 due to the fact I just dont care for it much. The instructions are up to date as of 10/21/2015
Deprecated-> This thread is about learning to build your own ROM following the instructions in post #2. The ROM posted in this thread is for example output. Feel free to download and use the ROMS @GROGG88 and I build! Feel free to try and build your own. We will try to help!
Quick Change Log
10/21 - Updated guide to reflect Android version 6.0.0_r1. No ROM for download (at this time).
1/17 - Updated build with official 5.0.2 Binaries. Fixed Browser "Settings" crash.
12/19 - Updated my Flo builds to Android 5.0.2_r1
12/9 - Updated my Flo build. Will not be doing a Deb Build any more.
12/2 @GROGG88 has updated his builds. I have not! I will update tomorrow. I did however get thefactory stock rooted ROM up HERE!
11/18 - @GROGG88 and I have joined forces to create two ROMS! I will be creating PURE AOSP ROMS and he will be creating Modified ROMS with many useful features! Each ROM can als be user built because all commits are shared in post #2!!!
11/15 - B8 - Updated the 5.0.0_r6. Deb is only using preview binaries due to lack of final binary files.
11/14 - B7 - Updated the 5.0.0_r5. Deb is only using preview binaries due to lack of final binary files.
11/10 - B6 - File system install instead of block install, Added Google Location Services to framework, Fixed a root issue that couple DEB users were having
11/9 - B5 - Changed wallpaper again. Fixed stock recovery at source level (Thanks to @Gnome and @GROGG88)
11/8 - B4 - Changed wallpaper to android 5 Wallpaper, fixed reverting to stock recovery (No need for save-recovery.zip), pre-rooted boot.img (No need for extra boot.img!)
11/7 - B3 - Removed it. Bad files. Reverted back to Build 2.
11/5 - B2 -- Fixed MTP bug that google has left in every version of AOSP, made ROM recovery flashable and added 2 zips to the OP
11/4 - B1 - Update to 5.0.0_r2. PC install via fastboot
Additional Downloads
Root by @Chainfire HERE!
Gapps for Lollipop HERE! There may be others so shop around!
Stericson's Busybox in flashable zip format is attached! Thanks to @Stericson for the binaries!
@GROGG88's Special Builds are HERE!
MOD EDIT: Link removed as domain has expired. Thread closed until new links can be installed
Please hit Thanks! It just as easy as hitting Download!
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Ubuntu 14.04 Set up and Build Guide
Updated 11/05/2014
Feel free to ask any questions about the build process. Do not ask questions about Ubuntu!
This guide assumes the following
Have Ubuntu 14.04 setup, fully operation, and up to date. Hard Machine or Virtual, makes no difference. Must meet the minimum specs for compiling. Info from Google HERE
Understand terminal command line entry as this is all command line processors.
You are not here to ask for help with Linux, only the Android build process!
Add Java
Code:
sudo apt-get install openjdk-7-jdk
Add Build tools (Adds the required packages at the time of this posting)
Code:
sudo apt-get install git gnupg flex bison gperf build-essential \
zip curl libc6-dev libncurses5-dev:i386 x11proto-core-dev \
libx11-dev:i386 libreadline6-dev:i386 libgl1-mesa-glx:i386 \
libgl1-mesa-dev g++-multilib mingw32 tofrodos \
python-markdown libxml2-utils xsltproc zlib1g-dev:i386
Add Repo command (Syncs Google Repository with your local machine)
Code:
mkdir ~/bin && curl http://commondatastorage.googleapis.com/git-repo-downloads/repo > ~/bin/repo && chmod a+x ~/bin/repo
Add bin folder to path for repo command (After you do this close Terminal and re-open to institute changes (easy way))
Code:
sudo gedit .bashrc
export PATH=~/bin:$PATH <-(add to end of bashrc)
Identify Yourself to the Repo (One day you may make commits so think about that when choosing your info!)
Code:
git config --global user.email "[email protected]"
git config --global user.name "yourpreferredusername"
Synch Repo (Download source... Sit back and grab a pop and a sandwich...)
Code:
mkdir ~/AOSP
cd ~/AOSP
repo init -u https://android.googlesource.com/platform/manifest -b android-6.0.0_r1
repo sync
Note: I use AOSP as my directory name. You can use what you want. You could use "aosp" or "Source" or "android" or "whateveryoulike"
Install proprietary binaries (Needed for things like GPS and Bluetooth, they are not Open Source like android) (Install proprietary binaries from here in the root of AOSP folder (or whatever you called yours))
Code:
[url]https://developers.google.com/android/nexus/drivers[/url]
Run envsetup.sh
Code:
source build/envsetup.sh
Choose Device
Code:
lunch
Build it!
Code:
make -j8 otapackage
See Build Notes and ramblings from me in post #3!
Notes
The ROM build will be a PURE AOSP ROM with no Gapps at all. See links in post #1 to PA Gapps for a good set of Google Apps!
The ROM will also have terminal level SU. So becareful! In other words its fully rooted and could be open to vulnerabilities. Flash your favorite Superuser Package if you need it. I dont. I recommend SuperSU by @Chainfire HERE. Download the flashable zip and flash after you flash ROM.
make -j8 is the number of worker threads that the make command will use to build. To me 8 is a safe number for an i7 processors. For an i5 Processor I would use -j4. I have experimented with a multitude of different values and it seems to me that the number of logical cores is also the best number to use with the make command.
Google recommends between -j24 and -j32 (to me that is excessive and causes my machine to error out every once in a while). Keep in mind the higher you push the more load the CPU will undertake. If your O/C'ing real hard you better have some nice cooling! I had to cut back OC on my 4770k from 4.65 to 4.4 with a Corsair H60 cooler just so it wouldn't over heat. When in doubt start low.
My i7 machine clocked at 4.4 and 16 gigs of RAM on a Samsung 840 Pro 256 Gig SSD take about 38 minutes to build the entire ROM.
With a 50 Meg download link it took maybe 30 to 45 minutes to sync the repo.
Changes from Source
Check out @GROGG88 patches HERE!
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Mindrocket said:
Right on Scott! Can't wait to give it a spin.
---------- Post added at 07:37 PM ---------- Previous post was at 07:15 PM ----------
Security settings crashes says"unfortunately settings has stopped" .
Click to expand...
Click to collapse
I think its the same error some other folks are facing. Rascarlo and a few others would release their AOSP builds but it appears this blocks them from releasing. Read this over on a few pages on a few ROMs in this neighborhood.
whoamanwtf said:
I have faith in you making it work
Click to expand...
Click to collapse
Can anyone post a snippet of logcat during the crash? Particular the actually error itself.
Place it in the
Code:
box if you can.
If not I get out of work in a few hours and can look then...
mjwhirly said:
Nice to see you venturing into new projects. Most people start with CM since its not to hard to compile, but you did it the opposite way which will make all the difference in the end
Sent from my LG-D800 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
IMHO: If you dont start with the basics you will end in a mess
got to try this as your clean rom works well iam sure this one will be great also
keep up the great work to you and who helps you.
Where would i start to try baking my own cake .. i use archlinux what programs needed to do a build
rocksyjj said:
got to try this as your clean rom works well iam sure this one will be great also
keep up the great work to you and who helps you.
Where would i start to try baking my own cake .. i use archlinux what programs needed to do a build
Click to expand...
Click to collapse
Never used archlinux but I used Ubunutu 13.04
Here is where I started: http://forum.xda-developers.com/showthread.php?t=2224142
(I hate nano so used gedit of course. )
But at the last two shell commands i didint use the AOKP tree I used the AOSP base so you want to look here for that: http://source.android.com/source/downloading.html
Then follow the instructions from that page on forward until you have yourself a ROM :highfive:
Also pay attention to the blurb about proprietary binaries
Obtaining proprietary binaries
The Android Open-Source Project can't be used from pure source code only, and requires additional hardware-related proprietary libraries to run, specifically for hardware graphics acceleration.
Official binaries for the supported devices can be downloaded from Google's Nexus driver page, which add access to additional hardware capabilities with non-Open-Source code.
When building the master branch for a device, the binaries for the most recent numbered release or with the most recent date are the ones that should be used.
Click to expand...
Click to collapse
There is a link for the Nexus binaries in that blurb. Make sure you install them before building and you are good.
Alright then...
Build 20131008.010041 up!
Changes
Re-synced repo for 2013/10/08
Fixed Settings -> Security F/C
Changed SU to SuperSU
Also can I have some people rate the thread 5 stars... The Nexus 7 FHD troll is at it again. He is going around rating my threads, and others, 1 star.
Any help with that would be appreciated. Damn trolls, lol!
scrosler said:
Alright then...
Build 20131008.010041 up!
Changes
Re-synced repo for 2013/10/08
Fixed Settings -> Security F/C
Changed SU to SuperSU
Also can I have some people rate the thread 5 stars... The Nexus 7 FHD troll is at it again. He is going around rating my threads, and others, 1 star.
Any help with that would be appreciated. Damn trolls, lol!
Click to expand...
Click to collapse
You fixed the security settings fc! Mind sharing how you managed to fix that?
Sent from my Nexus 7 using Tapatalk 4
scrosler said:
Also pay attention to the blurb about proprietary binaries
There is a link for the Nexus binaries in that blurb. Make sure you install them before building and you are good.
Click to expand...
Click to collapse
Where is the link to download the Nexus binaries btw? I didn't see a proprietary binaries blurb in the above 2 links.
Thanks.
vibranze said:
Where is the link to download the Nexus binaries btw? I didn't see a proprietary binaries blurb in the above 2 links.
Thanks.
Click to expand...
Click to collapse
Its under the actual "Building for devices" page...
http://source.android.com/source/building-devices.html
Wich leads to...
https://developers.google.com/android/nexus/drivers
scrosler said:
Alright then...
Build 20131008.010041 up!
Changes
Re-synced repo for 2013/10/08
Fixed Settings -> Security F/C
Changed SU to SuperSU
Also can I have some people rate the thread 5 stars... The Nexus 7 FHD troll is at it again. He is going around rating my threads, and others, 1 star.
Any help with that would be appreciated. Damn trolls, lol!
Click to expand...
Click to collapse
Hi Scott. Where is the download link for this one? I think a few folks would love to know the fix for the security fc since last I read it was blocking their update as well. Definitely want to try the aosp one.
Sent from my Nexus 7 using XDA Premium 4 mobile app
scrosler said:
Its under the actual "Building for devices" page...
http://source.android.com/source/building-devices.html
Wich leads to...
https://developers.google.com/android/nexus/drivers
Click to expand...
Click to collapse
hi scott,
could you please share the sources you build from? and specifically how you fixed the Security settings FC?
thanks.
vibranze said:
Thanks Scotts, appreciated your fast response. :good:
Click to expand...
Click to collapse
Your welcome!
mpmilestogo said:
Hi Scott. Where is the download link for this one? I think a few folks would love to know the fix for the security fc since last I read it was blocking their update as well. Definitely want to try the aosp one.
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Its in the OP. Post 1. I just changed the link. Happy downloading!
TheDarkDefender said:
hi scott,
could you please share the sources you build from? and specifically how you fixed the Security settings FC?
thanks.
Click to expand...
Click to collapse
The source is the AOSP tree and it can be found here: http://source.android.com/source/downloading.html (thats all I am using).
Fixing the Settings F/C was creative... had to Google to get the answer, lol
Here is what I found...
CM 10.2 initially had this issue as its based from AOSP like this rom (SOURCE). They did not explain a fix... Also, note this is a less than one week old issue. So I continued on with Google... (Google is a son of a ***** when you need it )
Then found this thread on XDA from the Nexus 4 about an update to 4.2.2 HERE! This started to make sense as they posted a fix for the N4. HOWEVER that fix was not applicable to our N7.2 because we did not have the keymaster files on the vendor partition!!!
So test flashed the Google stock ROM /system/vendor/firmware/keymaster/* files into this AOSP ROM. VIOLA! It worked and solved the problem.
Now I will admit I am not sure why these files are not in the AOSP source tree as I am still learning... If you can shed more light then please do! But I do know that it fixed the issue. Was not seemingly prevalent before October 2nd (or maybe it was but thats when it was reported on CM10.2) and moving those files into the ROM base resolved (granted they are not in the same spot as the N4).
Please feel free to share anything you know in this thread.
scrosler said:
Your welcome!
Its in the OP. Post 1. I just changed the link. Happy downloading!
Click to expand...
Click to collapse
Thanks Scott. I think I found something rather strange with my tablet with just about any of the AOSP builds. I found this on another as well. It seems whenever I enable locations in chrome or chrome beta the tablet soft resets immediately. If I turn off location reporting, nothing happens but I get no location updates. I decided to restore things using the factory images. For the umpteen thousandth time, thanks to the Android team for providing the safety net!
Gonna try again later today and see if this issue persists after resetting the device to the factory image and reflashing the AOSP build.
mpmilestogo said:
Thanks Scott. I think I found something rather strange with my tablet with just about any of the AOSP builds. I found this on another as well. It seems whenever I enable locations in chrome or chrome beta the tablet soft resets immediately. If I turn off location reporting, nothing happens but I get no location updates. I decided to restore things using the factory images. For the umpteen thousandth time, thanks to the Android team for providing the safety net!
Gonna try again later today and see if this issue persists after resetting the device to the factory image and reflashing the AOSP build.
Click to expand...
Click to collapse
No this very possible depending on the GAPPS used. I think this is more a GAPPS issue then a ROM issue. I cant say for sure but I might have time to look later.
If someone else knows then do tell.
However I dont much care for Chrome on mobile (love it on PC) so I use AOSP and it runs well. But have not tested location.
Im sure a fix can be found with enough effort.
scrosler said:
No this very possible depending on the GAPPS used. I think this is more a GAPPS issue then a ROM issue. I cant say for sure but I might have time to look later.
If someone else knows then do tell.
However I dont much care for Chrome on mobile (love it on PC) so I use AOSP and it runs well. But have not tested location.
Im sure a fix can be found with enough effort.
Click to expand...
Click to collapse
Interesting. I've tried the BANKS minimal GAPPS core and photosphere as well as the goo.im gapps in clean flashes of other aosp based ROMs but still had the same issue. Perhaps I'll try the PA gapps next since they seem to have everything in them. Gonna give the whole thing a try a bit later today as well. I'm lucky enough to have two Nexus 7 tablets so one has your latest CleanROM on it which I love! The other seems to have descended into flashing heaven or the other place .
Any help appreciate on the issue though. I'd love to run AOSP on the second tablet since one of them is destined for my daughter when she realizes she wants one.
scrosler said:
The source is the AOSP tree and it can be found here: http://source.android.com/source/downloading.html (thats all I am using).
Fixing the Settings F/C was creative... had to Google to get the answer, lol
Here is what I found...
CM 10.2 initially had this issue as its based from AOSP like this rom (SOURCE). They did not explain a fix... Also, note this is a less than one week old issue. So I continued on with Google... (Google is a son of a ***** when you need it )
Then found this thread on XDA from the Nexus 4 about an update to 4.2.2 HERE! This started to make sense as they posted a fix for the N4. HOWEVER that fix was not applicable to our N7.2 because we did not have the keymaster files on the vendor partition!!!
So test flashed the Google stock ROM /system/vendor/firmware/keymaster/* files into this AOSP ROM. VIOLA! It worked and solved the problem.
Now I will admit I am not sure why these files are not in the AOSP source tree as I am still learning... If you can shed more light then please do! But I do know that it fixed the issue. Was not seemingly prevalent before October 2nd (or maybe it was but thats when it was reported on CM10.2) and moving those files into the ROM base resolved (granted they are not in the same spot as the N4).
Please feel free to share anything you know in this thread.
Click to expand...
Click to collapse
Thank you very much. Did you figure out the commit in the CM repo that actually solved this issue?
Also, what do you mean by So test flashed the Google stock ROM /system/vendor/firmware/keymaster/* files into this AOSP ROM ? Could you elaborate please?
I'd be happy to share anything I get to know about this. Been researching about this too. Thanks.
first off all i dont know where to start such thread so moderate can move it to whatever place they thought of
now i had some good news and not some good news
good news is i had found complete mtk sources and compiled rom out of it succesfully
and not so good news is
sources are of 4.1.2 and im new to this so i need developers help
i'm posting the steps that i had followed for compiling
DOWNLOAD
1. download and install ubuntu if not installed already
2. download sources http://pan.baidu.com/wap/link?uk=2869617224&shareid=4195729301&third=0
3. download jdk-6u29-linux-x64.bin (this worked for me)
SETTING UP MACHINE
1. open terminal and type
2.
Code:
sudo apt-get install flex bison gperf build-essential curl zlib1g-dev g++-multilib g++-4.4-multilib libc6-dev-i386 lib32ncurses5-dev ia32-libs x11proto-core-dev libx11-dev lib32readline5-dev lib32z1-dev wine mingw32 tofrodos libxml2-utils
3. after it finishes installation of required pakages type
Code:
cd /usr/bin
sudo mv gcc gcc.bak
sudo ln -s gcc-4.4 gcc
sudo mv g++ g++.bak
sudo ln -s g++-4.4 g++
4. now setup java change to directory where jdk-6u29-linux-x64.bin resides and extract using
Code:
./jdk-6u29-linux-x64.bin
cammand in terminal
make sure permission of jdk-6u29-linux-x64.bin is executable
5. type following in terminal
Code:
gedit ~/.bashrc
and following lines to bashrc in gedit
Code:
#java Settings
export JAVA_HOME=~/toolchain/jdk1.6.0_29
export JRE_HOME=JAVA_HOME/jre
export CLASSPATH=$JAVA_HOME/lib:$JRE_HOME/lib:$CLASSPATH
export PATH=$JAVA_HOME/bin:$JRE_HOME/bin:$PATH
make sure to setup up path correctly in my case java is exracted in toolchain folder yours may differ
6 type follwing in terminal
Code:
sudo mv /bin/sh /bin/sh.bak
sudo ln -s /bin/bash /bin/sh
BUILDING ROM
1. extract sources( in my case in alps folder at home)
2. open mbldenv.sh in root directory of extracted folder and edit java path as done before
3. open terminal emulator
and type
Code:
./mk -h for all commands
and type
Code:
./mk -o=TARGET_BUILD_VARIANT=user mbk77_tb_jb n
(for a complete new build of mbk77_tb_jb project)
###########################################################
now i request all developers to colabrate and make kitkat possible
im trying my bit but new to all this and mtk sources are complete mess
if you got any problem or error im here to help to best of my possibilities
screenshot of out folder and generated build.prop is attached
and dont ask me to upload anything as my net speed is slow it takes 7 days to download sources
Great Initiative Buddy
All the best :good:
got all imgs compiled without any errors ??
Sent from my XOLO A700 using Tapatalk
AnoopKumar said:
got all imgs compiled without any errors ??
Sent from my XOLO A700 using Tapatalk
Click to expand...
Click to collapse
Yes buddy no error sources are complete but a big mess too
Sent from my NeXus using xda app-developers app
I don'y have the device but my neighbour has since i can't use his phone all day i can just help by making device tree for CM11 and try and add patches which were made for MT6589
I an not sure if this can work the only thing is @bindassdost you sync the sources and try we can make a organisation on Github and submit the patches
GuneetAtwal said:
I don'y have the device but my neighbour has since i can't use his phone all day i can just help by making device tree for CM11 and try and add patches which were made for MT6589
I an not sure if this can work the only thing is @bindassdost you sync the sources and try we can make a organisation on Github and submit the patches
Click to expand...
Click to collapse
brother i cant sync sources my net is slow (256kbps) only it took me 7 days to download 2.7gb compressed souorces i dont know how long it will take to sync 9gb sources to github thats why i wrote everything that i did so that someone with good speed do the task
thats the reson i cant procede further as cm sources are also huge arround 10gb but i can help if someone else do this
bindassdost said:
brother i cant sync sources my net is slow (256kbps) only it took me 7 days to download 2.7gb compressed souorces i dont know how long it will take to sync 9gb sources to github thats why i wrote everything that i did so that someone with good speed do the task
thats the reson i cant procede further as cm sources are also huge arround 10gb but i can help if someone else do this
Click to expand...
Click to collapse
GuneetAtwal said:
I don'y have the device but my neighbour has since i can't use his phone all day i can just help by making device tree for CM11 and try and add patches which were made for MT6589
I an not sure if this can work the only thing is @bindassdost you sync the sources and try we can make a organisation on Github and submit the patches
Click to expand...
Click to collapse
i can help u with that i have downloaded the synced sources..and will upload if the phone boots up...
i am just thing of how to build it as it is not supported...
just help me with that and the recovery which will reqire selinux..
,[email protected]
also i have cloned the kernal sources of your bindassboost..is it ok..i did not have any other souces of kernal..
well my cm 11 sorce downloading is complete around 13.54 gb..
plus my net speed is 2 mbps..
Avenger4droid said:
i can help u with that i have downloaded the synced sources..and will upload if the phone boots up...
i am just thing of how to build it as it is not supported...
just help me with that and the recovery which will reqire selinux..
,[email protected]
also i have cloned the kernal sources of your bindassboost..is it ok..i did not have any other souces of kernal..
well my cm 11 sorce downloading is complete around 13.54 gb..
plus my net speed is 2 mbps..
Click to expand...
Click to collapse
First try the build output coming from these sources as they will be 4.1.2 so you don't require any special Recovery for now so try that
GuneetAtwal said:
First try the build output coming from these sources as they will be 4.1.2 so you don't require any special Recovery for now so try that
Click to expand...
Click to collapse
i havent made the output file yet...
cause i dont know..
i have cloned the sources ....but i m confused how to build ???
is there a folder called "protect" in "source/mediatek/"
Sent from my XOLO A700 using Tapatalk
probably yes...cause i had one when i downloaded the sources...
also is there a vender folder in mediatek...???
So now Can WE Expect Kitkat For CAnvas2 ... Don't know When Micromax Gonna Release It .. @bindassdost
I think these are MT8377 sources :/
Can't work on it without a device to test.
Sent from my C2105 using Tapatalk
varun.chitre15 said:
Can't work on it without a device to test.
Sent from my C2105 using Tapatalk
Click to expand...
Click to collapse
Hi sir, its good to see you back.....:victory:if you are sure(i mean undertaking cm development) we shall start a fundraiser thread if you wish to have a device
varun.chitre15 said:
Can't work on it without a device to test.
Sent from my C2105 using Tapatalk
Click to expand...
Click to collapse
Nice See You varun.chitre15 Buddy........
hello sir..
varun.chitre15 said:
Can't work on it without a device to test.
Sent from my C2105 using Tapatalk
Click to expand...
Click to collapse
thank you sir for returning sir...i am very grateful to you...
i have downloaded cm 11 sources and also made the evironment for developing...
all i need is ur help to compile it as i dont have complete device trees..and kernal sources...
also i have not made cm for unsupported device..
your help is very important and gratefull to me..
regards
Avenger4droid
Avenger4droid said:
thank you sir for returning sir...i am very grateful to you...
i have downloaded cm 11 sources and also made the evironment for developing...
all i need is ur help to compile it as i dont have complete device trees..and kernal sources...
also i have not made cm for unsupported device..
your help is very important and gratefull to me..
regards
Avenger4droid
Click to expand...
Click to collapse
tHATS fANTASTIC bROTHER... =
bindassdost said:
(...)
good news is i had found complete mtk sources and compiled rom out of it succesfully
(...)
Click to expand...
Click to collapse
Hi
You do know that those sources aren't for MT6577 ?
They are for MT8377, a Tablet SoC , and there are a lot of diffs between MT6577 and MT8377 (mainly GPU; max RES; etc, etc )
So, just imagine the mess it would be, by working on some sources that aren't exaclly for your SoC.
Even with full sources for MT6589, the CM Builds required alot of work, and the build status are still WIP. And with a lot of things to be fixed...
B.Regards
Check these sources
mxrootrom.blogspot.in/2014/02/mediatek-mtk-kernel-source-code-leaked.html?m=1
Sent from my MICROMAX CANVAS 2 using XDA Premium 4 mobile app