Database Users

Kernel Source DROID Incredible by HTC (Verizon) – GB MR - 2.6.35 WITH COMPILING GUIDE

Hey all, I guess if your here its because you want to build your own kernel from the HTC GB Kernel source for the HTC Droid Incredible. So that's what we're gonna do.
First things first. I have to send out a huge thanks to a few guys that helped me out along the way.
jdkoreclipse - Your the best man. Thanks for getting me compiling.
wdfowty - Always good on the code.
ohheyitslou - Standing by while a blabbered on with stupid questions.
conap - The original god of kernels.
Koush - Thanks for the anykernel updater.
Note: The method I descripe below is what worked for me to get this thing to build and boot. Additional packages may be required. Ie; JDK, Android SDK, Python, git and the 32bit libs (if your on a x64 machine). I do assume that you have them and have your computer set up for development. I also assume that you are fully aware that any damage caused to your devices from YOU following this guide is held at your own responsibility.
Click to expand...
Click to collapse
First things first, lets make sure you are on a linux distro. At the time of this writing, I was using Ubuntu 11.10 x64. Note: 64x is highly suggested. My computer is a dual core amd machine with 4GB of ram. I have a 250GB HHD.
Next lets download some things that we will need for your kernel.
The kernel source of course:
DROID Incredible by HTC (Verizon) – GB MR - 2.6.35 kernel source code
This is the correct size and MD5:
88.8 MB (93,175,808 bytes) 67c01623ff73415a99e5f8cd1d8ef11a
You will also want the CM Toolchain. This is what compiles your kernel.
Open a terminal window and type:
Code:
git clone git://github.com/CyanogenMod/android_prebuilt.git prebuilt
And finally, the anykernel_updater.zip for packaging and flashing your kernel: anykernel_updater.zip
Have these things downloaded? Great! Lets continue.
Next we need to create a new build directory to build your kernel in. For this tut, we will make this in your Home dir.
Open a terminal window and type:
Code:
cd ~
mkdir android
cd android
mkdir kernel
Easy huh?
Next grab your HTC Droid Incredible kernel source archive and just open it with archive manager. We don't need to do any untarring here.
You'll want to drag that 395.2MB folder inside called 'incrediblec-2.6.35-gb-mr' to that kernel directory you created.
Next, grab the CM toolchain archive and open it the same way. Yup just drag that folder thats inside there out and put right in your 'android' folder.
So lets review real quick before we continue:
Inside your Home directory you now have a folder called: android
Inside that android folder you have two folders. One called: kernel and the other called: android_prebuilt or prebuilt.
Inside the kernel folder you have your kernel source folder: incrediblec-2.6.35-gb-mr
Is this correct? Good.
Now, lets open a new terminal window and move to your kernel source folder:
Code:
cd '/home/yourusername/android/kernel/incrediblec-2.6.35-gb-mr'
Now we will compile the source. Note: This is a basic kernel source compiling guide. Our focus is to simply compile the source. Nothing more.
In the terminal window type:
Code:
make incrediblec_defconfig
make -j4 ARCH=arm CROSS_COMPILE=/home/yourusername/android_prebuilt/linux-x86/toolchain/arm-eabi-4.4.3/bin/arm-eabi-
Note I used j4. This is because I am using a dual core box to develop on. I think now days most boxes are usually dual core or quad core?
Your kernel should now be compiling. This process could run average between 5min-1hr. My laptop (which is beast) did it in about 2 minutes. But then again I'm running a full install of 'buntu x64 with everything updated and ready to rock.
Anyways after the compiler finishes building it will tell you where to locate your kernel and wifi driver. Yes the wifi driver is included!
The kernel should be at: /home/yourusername/android/kernel/incrediblec-2.6.35-gb-mr/arch/arm/boot/ for those that don't know it is called 'zimage'. Just drag that out to your Desktop.
Now go grab your wifi driver. Its located at: /home/yourusername/android/kernel/incrediblec-2.6.35-gb-mr/drivers/net/wireless/bcm4329_204/ It will be called bcm4329.ko. Again drag that out to your desktop.
Now you can close everything thats open. Grab that anykernel_flasher.zip you downloaded earlier and open it up with archive manager. Don't extract it, just open it.
Navigate to system/lib/module/ and drag your bcm4329.ko right into it.
Next back up all the way to the root of the anykernel_flasher.zip and then open the kernel folder. Yup just drag and drop your zimage right in there. Close the archive manager window.
CONGRATS!!! You just compiled your first kernel from source!
Now you can rename the zip to whatever is easiest for you to remember. Common practice says the date and time should be in the name. Like mine from today is called: 2.6.35.13-stang-kernel-1830-110111.zip.
Now go test your kernel. Just put it on your sd card and flash it through recovery. The anykernel_updater.zip will handle the wiping for you so you shouldn't have to worry about wiping boot, dalvik-cache or cache. You can still wipe those things if you would like.
Once the flash is complete, just hit reboot device and wait for your phone to boot up. It took mine about 5 minutes to fully boot up.
Well, I hope yall enjoyed this guide. I wanted to keep it simple. I am not a kernel god or anything but let me tell ya, I went through a lot to try to learn how to do this. So if you run into any trouble, I'll try to help you out if I can.
Have fun guys!

now what​..........

Nice. Good job.
Sent from my ADR6300 using Tapatalk

Way to help us out with a good easy to follow guide stang thanks
sent from my sexy Slcd Droid Incredible. not dinc or D-inc that just sounds stupid.

tiny4579 said:
Nice. Good job.
Sent from my ADR6300 using Tapatalk
Click to expand...
Click to collapse
Thanks Tiny. Now we need to get some more customs going
evilstewie23 said:
Way to help us out with a good easy to follow guide stang thanks
sent from my sexy Slcd Droid Incredible. not dinc or D-inc that just sounds stupid.
Click to expand...
Click to collapse
Thanks stew, You know how much this means to me.

Beast Mode! Very nice guide sir, I'm sure some of the more serious members will get hella use out of this. I have been (sort of) following your progress on twitter, so glad to see that you finally got it figured out. Nice work.

00McD00 said:
Beast Mode! Very nice guide sir, I'm sure some of the more serious members will get hella use out of this. I have been (sort of) following your progress on twitter, so glad to see that you finally got it figured out. Nice work.
Click to expand...
Click to collapse
Thanks Mc. I'm just happy to have learned this much atleast. I'm even more happy to share what I've learned. That's the important part.

wildstang83 said:
Thanks Mc. I'm just happy to have learned this much atleast. I'm even more happy to share what I've learned. That's the important part.
Click to expand...
Click to collapse
Definitely, I have always felt the same way. Sharing is caring lol

That's the stuff, Wildstang. Glad you're back.
Sent from my Prime_XL Incredible via Tapatalk

very nice. Im going to give a this a go and see what i can some up with. does this require a sense rom or a aosp rom?

dirtsky said:
very nice. Im going to give a this a go and see what i can some up with. does this require a sense rom or a aosp rom?
Click to expand...
Click to collapse
This compiles a sense kernel.

tcberg2010 said:
This compiles a sense kernel.
Click to expand...
Click to collapse
Well Sh*t. Oh well ill still give it a go I guess.

tcberg2010 said:
This compiles a sense kernel.
Click to expand...
Click to collapse
these instructions will work fine for aosp. You just have to download that kernel source instead. The compile process is the same.
Sent from my ADR6300 using Tapatalk

Ill have to get the kernel source and see what I can do.
Sent from my Incredibly awesome Droid Incredible.

Thanks for adding this howto, wildstang -
I really appreciate it. I just for the first time in a year+ went from my old rooted inc to this home-brewed self-compiled (I added cifs & tun built into the kernel) and installed it. I'd just tried the insensitive ROM as well and this helped things quite a lot due to cifs & tun. I also set the clock to a not-very-aggressive 1075000 which works fine on my inc.
Much appreciated and good guide.
edit: I forgot to mention that in general and here as well, you can 'brand' your kernel so you're sure you've really installed it and it is running on your phone by checking the firmware revs in about-phone. To do that, just edit Makefile and I think it is called Extra (under Version) which is as it is set to .13, so I set that in my case to .13-cifs-tun-cust, and it shows on my phone. It is useful in case you forget to zip the file up or something.
Hashi

HTC Desire V porting with Sense 4.0a. Anyone?

Hi guys,
I've just came across this new device for the Chinese market and here are the specs: http://www.gsmarena.com/htc_desire_v-4805.php
It has almost the same hardware as our old N1, above all NOTE that it has the same Adreno200 for graphics :good:
For now I have downloaded a European RUU (RUU_PRIMO_DS_ICS_40A_HTC_Europe_1.59.401.1_Radio_1.05.34D.25_20.20.30.22U_release_263747_signed) for this Desire V (codenamed Primo?), and I have extracted the system.img.
Now to extract the content of that image I have to play with a Linux environment..
I've tried with unyaffs.exe but this image won't extract with that utility. I think the only solution is to "mount -o loop system.img" or something like that.
Do you think it's possible to do something?
Please remember that I'm only a cooker, with some (a little) experience, but with NO Java knowledge..

Iperzampem0 said:
Hi guys,
I've just came across this new device for the Chinese market and here are the specs: http://www.gsmarena.com/htc_desire_v-4805.php
It has almost the same hardware as our old N1, above all NOTE that it has the same Adreno200 for graphics :good:
For now I have downloaded a European RUU (RUU_PRIMO_DS_ICS_40A_HTC_Europe_1.59.401.1_Radio_1.05.34D.25_20.20.30.22U_release_263747_signed) for this Desire V (codenamed Primo?), and I have extracted the system.img.
Now to extract the content of that image I have to play with a Linux environment..
I've tried with unyaffs.exe but this image won't extract with that utility. I think the only solution is to "mount -o loop system.img" or something like that.
Do you think it's possible to do something?
Please remember that I'm only a cooker, with some (a little) experience, but with NO Java knowledge..
Click to expand...
Click to collapse
I'm up for that. I think if a lot of devs work together we can do it. I dunno about java experience
Sent from my HTC Desire using xda app-developers app

**** Shaky. He stopped all his job =(
But good idea and good luck
I can be your tester if you want of course
Sent from my Nexus One using Tapatalk 2

Iperzampem0 said:
Hi guys,
I've just came across this new device for the Chinese market and here are the specs: http://www.gsmarena.com/htc_desire_v-4805.php
It has almost the same hardware as our old N1, above all NOTE that it has the same Adreno200 for graphics :good:
For now I have downloaded a European RUU (RUU_PRIMO_DS_ICS_40A_HTC_Europe_1.59.401.1_Radio_1.05.34D.25_20.20.30.22U_release_263747_signed) for this Desire V (codenamed Primo?), and I have extracted the system.img.
Now to extract the content of that image I have to play with a Linux environment..
I've tried with unyaffs.exe but this image won't extract with that utility. I think the only solution is to "mount -o loop system.img" or something like that.
Do you think it's possible to do something?
Please remember that I'm only a cooker, with some (a little) experience, but with NO Java knowledge..
Click to expand...
Click to collapse
can you please upload the system.img file somewhere? (or post the link to the original RUU_PRIMO_DS_ICS_40A_HTC_Europe_1.59.401.1_Radio_1.05.34D.25_20.20.30.22U_release_263747_signed file )

Here you go. It's ruu
http://hotfile.com/dl/158782968/55e3eb6/
Do we need 3.0 kernel ?
Sent from my Nexus One using Tapatalk 2

thanks..
i think shaky's Sense 4.0 alpha rom was based on Desire V dump.. dont know if it is worth the effort to start all over again...

Wait. It was based from One V rom. Not desire V
Sent from my Nexus One using Tapatalk 2

I agree with xeloni. Shaky was using the One V rom dump, which has the Adreno205 gpu!
The great thing of having a device with at least the same GPU is that we can have the right GPU files/drivers and maybe have a complete full gpu rendering. Obviously we gonna have to build a 3.0 kernel and proper cpu drivers...

Cmon dbasabe ! !
And shaky has almost finished thé kernel but he stopped all :/
After Imperzampemo, in this rom delete all useless appartement. Some ringtones. Fast and Light sense
Sent from my Nexus One using Tapatalk 2

i managed to extract system.img, it is 800mb after uncompressing...
one more thing, i couldn't extract the secure boot image. anyone know how to extract that?

xeloni said:
Cmon dbasabe ! !
And shaky has almost finished thé kernel but he stopped all :/
After Imperzampemo, in this rom delete all useless appartement. Some ringtones. Fast and Light sense
Sent from my Nexus One using Tapatalk 2
Click to expand...
Click to collapse
Shaky has not stopped . He continues in silence and won't post on xda again. You better be following him on Twitter.
Also, dbasabe has left a long time ago
Sent from my HTC Desire using xda app-developers app

fake_japanese_guy said:
i managed to extract system.img, it is 800mb after uncompressing...
one more thing, i couldn't extract the secure boot image. anyone know how to extract that?
Click to expand...
Click to collapse
OK, but now the main thing is to extract all the content from system.img!
About boot_signed.img don't know yet.
Anyway I still have to install Linux on my pc, so I'm stuck as of now..

race55 said:
Shaky has not stopped . He continues in silence and won't post on xda again. You better be following him on Twitter.
Also, dbasabe has left a long time ago
Sent from my HTC Desire using xda app-developers app
Click to expand...
Click to collapse
I'm following him on twitter
If someone wants to add me look in m'y signature
Sent from my Nexus One using Tapatalk 2

Iperzampem0 said:
OK, but now the main thing is to extract all the content from system.img!
About boot_signed.img don't know yet.
Anyway I still have to install Linux on my pc, so I'm stuck as of now..
Click to expand...
Click to collapse
Virtual box
Sent from my Nexus One using Tapatalk 2

xeloni said:
I'm following him on twitter
If someone wants to add me look in m'y signature
Sent from my Nexus One using Tapatalk 2
Click to expand...
Click to collapse
Does shaky have his twitter account protected?
Didn't realise he had quit xda until I read this. Another dev loss; reminds me of Medroid / Samuaz.
Sent from my Nexus One using xda app-developers app

xeloni said:
Virtual box
Sent from my Nexus One using Tapatalk 2
Click to expand...
Click to collapse
Yea, I'm using that but it's really slow and I have problems... wtf! I hate Linux.

cpm said:
Does shaky have his twitter account protected?
Didn't realise he had quit xda until I read this. Another dev loss; reminds me of Medroid / Samuaz.
Sent from my Nexus One using xda app-developers app
Click to expand...
Click to collapse
No itsnt protected
Sent from my Nexus One using Tapatalk 2

i managed to extract boot_secure.img also.. it had 256bytes of some security key on the beginning.. i had to tail it and then extract.
any way, after extracting, the system.img is more than 600mb.. we need to reduce it to less than 200mb to install to nexus one...
meanwhile im trying to boot with the kernel from the dump.. as of now, its not working.. kernel panic..

fake_japanese_guy said:
i managed to extract boot_secure.img also.. it had 256bytes of some security key on the beginning.. i had to tail it and then extract.
any way, after extracting, the system.img is more than 600mb.. we need to reduce it to less than 200mb to install to nexus one...
meanwhile im trying to boot with the kernel from the dump.. as of now, its not working.. kernel panic..
Click to expand...
Click to collapse
Try to boot with the kernel included in shaky rom
Sent from my Nexus One using Tapatalk 2

ill try that. but before that, need to find some applications to remove the the dump so that i can reduce the /system size to less than 200mb...

[Ubuntu Touch] Porting the Ubuntu Touch Developer Preview to GT-N7000

This is the port of Ubuntu Phone to the Samsung Galaxy Note GT-N7000
What works:
Wifi (fixed on 18-07)
GSM (only mobile connection)
Webbrowsing
Taking photos (fixed)
If you haveing trouble with GSM give it time to connect. If its still not working check this : https://plus.google.com/100264483712374857174/posts/3o1tjYo9Ghx
CREDITS
thanks to chasmodo for
manifest additions
camera driver
runtime intermediates files
thanks to Gerrett for
the hint to remove the GalaxyNoteSettings from build
fixing the wifi issue
The short way:
Download, push to sdcard, reboot to recovery, do a backup, do a full wipe and flash(keep the order of the files)
quantal-preinstalled-phablet-armhf.zip
Ubuntu n7000 nightly build
The long way:
Here is the official Canonical's Porting Guide
here we have the cm nightlies from wich we take the binaries for the base system.
Now, I will set up my building system how described in the Guide (Since I've already a working Ubuntu 13.04 x64 PreAlpha installation, I'll use that as base)
Seting up the development environment
What is not in the guide:
Code:
sudo apt-add-repository ppa:phablet-team/tools
sudo apt-get update
sudo apt-get install phablet-tools
sudo apt-get install bzr
sudo apt-get remove openjdk-7-jdk
sudo apt-get install openjdk-6-jdk
So, on the console
(if there are german speaking people following, this is how you can kill the waiting time http://www.youtube.com/watch?v=S_poaB9jLAc and http://www.youtube.com/watch?v=eMim3OV2cQE and http://www.youtube.com/watch?v=1-jbeV_kpaU have fun)
Code:
mkdir -p UbuntuTouch/GT-N7000 #at a location with 20 gigs of free space(yes, its a lot :D )
cd UbuntuTouch/GT-N7000
git config --global user.email "[email protected]" #needs this only once for
git config --global user.name "Your Name"
phablet-dev-bootstrap ./ #this will take a while, it will download all sources except the kernel if I understood right
Edit .repo/manifest.xml and add following at the same xml level where the other project tags are.
(First search for, maybe they are already in that file)
Code:
then again on console:
Code:
repo sync
Code:
adb devices #just a short check to see if the connection is working, if it's in the list, go further, if not check whats the problem
. build/envsetup.sh
brunch cm_n7000-userdebug #if everything is ok, this will take a while
put the zip you get in the output onto your sdcard, download saucy-preinstalled-phablet-armhf.zip
reboot your n7000 into recovery mode, backup and flash first the preinstalled and then the build.
Have fun

Sounds good...keep us updated
Thanks

I have the required changes ready in the files incase someone is interested
was waiting for beerbong but he seems busy... times like these u wish u werent building remotely ^^
maybe utacka or chas(with his new pc) can help..

AW: [Ubuntu Touch] Porting the Ubuntu Touch Developer Preview to GT-N700
So what does that mean toxic? Do u already ported it? ??

no I'll try it this weekend

Re: [Ubuntu Touch] Porting the Ubuntu Touch Developer Preview to GT-N700
You don't have to use cm, you can use AOSP.
You can even use Samsungs kernel source (I haven't bothered building the latest so no idea how good it is our not) and the binary blobs from the latest stock build.
I'm building it for one of my tablets at the mo from AOSP, using an old but working kernel.
Sent from my GT-N7000 using Tapatalk 2

fards said:
You don't have to use cm, you can use AOSP.
You can even use Samsungs kernel source (I haven't bothered building the latest so no idea how good it is our not) and the binary blobs from the latest stock build.
I'm building it for one of my tablets at the mo from AOSP, using an old but working kernel.
Sent from my GT-N7000 using Tapatalk 2
Click to expand...
Click to collapse
First of all I'll use what the guide suggests. Playing games comes after.

Re: [Ubuntu Touch] Porting the Ubuntu Touch Developer Preview to GT-N700
fards said:
You don't have to use cm, you can use AOSP.
You can even use Samsungs kernel source (I haven't bothered building the latest so no idea how good it is our not) and the binary blobs from the latest stock build.
I'm building it for one of my tablets at the mo from AOSP, using an old but working kernel.
Sent from my GT-N7000 using Tapatalk 2
Click to expand...
Click to collapse
For a device such as ours, don't think deviating from CM is a good idea
Sent from my GT-N7000 using xda premium

Re: [Ubuntu Touch] Porting the Ubuntu Touch Developer Preview to GT-N700
I was reading over the guide and would have to say there is a lot of set up involved
Sent from my GT-N7000 using XDA Premium HD app

Good luck man! Subscribed to the thread! i hope you'll make it!

Sorry, missed coming back to this thread.
For SUID changes, the mentioned file is found at -
device/samsung/galaxys2-common/rootdir/fstab.smdk4210
The Brightness settings dont need to be changed as those changes are already present I think.

AW: [Ubuntu Touch] Porting the Ubuntu Touch Developer Preview to GT-N700
Yeah,seems to be server problems, i'm syncing since yesterday, but now i can the see the end
Edit: Seems like to many people are syncing now .. cant sync anything atm ..
Gesendet von meinem GT-N7000 mit Tapatalk 2

hey,
i saw this previews for the mako, i dont know if this will help you guys to port it for the N7000, afaik they can simply be flashed in recovery :cyclops:
http://cdimage.ubuntu.com/ubuntu-touch-preview/quantal/mwc-demo/

T1663R said:
hey,
i saw this previews for the mako, i dont know if this will help you guys to port it for the N7000, afaik they can simply be flashed in recovery :cyclops:
http://cdimage.ubuntu.com/ubuntu-touch-preview/quantal/mwc-demo/
Click to expand...
Click to collapse
they are for galaxy nexus, nexus 4, 7 and 10.

Yep, having sync troubles at this end as well. Must be lots of us trying to make this work. Good to know the GT-N7000 is so popular? Keep getting "fatal: The remote end hung up unexpectedly".

Re: [Ubuntu Touch] Porting the Ubuntu Touch Developer Preview to GT-N700
Can we please get a dedicated section for ubuntu on the note mods?
Sent from my GT-N7000 using xda premium

Ok so i've been afk most weekend. How's it going? Any luck getting ubunutu on our notes?

This way I'll never have to change my device. You guys always keep bringing new stuff to it
Thanks a lot to all the amazing work all the devs around here are doing. Love you all

AW: [Ubuntu Touch] Porting the Ubuntu Touch Developer Preview to GT-N700
Repo is synced .. and all stuff done from ubuntus guide. But get build error. Will look at it tomorrow. Anyone got it to build?
Edit: okay, it only wants to build the note settings, needs to be removed from makefile.
Will now build overnight an hope its rdy in the morning
Gesendet von meinem GT-N7000 mit Tapatalk 2

fards said:
You don't have to use cm, you can use AOSP.
You can even use Samsungs kernel source (I haven't bothered building the latest so no idea how good it is our not) and the binary blobs from the latest stock build.
I'm building it for one of my tablets at the mo from AOSP, using an old but working kernel.
Sent from my GT-N7000 using Tapatalk 2
Click to expand...
Click to collapse
Forgive my offtopic, i'm interested of using Samsung sources for Galaxy SII i9100, instead of cyanogenmod 10.1, that isn't properly good for this device. can you tells me more about that?

Porting ROMs

How does one port ROMs to another phone? I'm looking to try and port Xylon to the Find 5.
Sent from my X909 using xda app-developers app

it's really not that difficult. just have to adjust some overlays, change some stuff in vendor and maybe grab the camera from CM if the changes haven't been made to that ROM.

if you are building from source:
Find the 4.2.2 source code of the ROM you want to port
Get the manifest.
Add the CM10.1 device/kernel tree and proprietary libs in the .repo/local_manifest/roomservice.xml
sync all the repos
(do whatever the source might need you to set up: EG paranoid android, need you to setup your device properly in vendor/pa/* files)
compile. Fix any problems(maybe missing files, etc)
you could try a non-4.2.2-based ROM to port, but you'll run into more incompatibility issues to fix

mbh87 said:
it's really not that difficult. just have to adjust some overlays, change some stuff in vendor and maybe grab the camera from CM if the changes haven't been made to that ROM.
Click to expand...
Click to collapse
So would you say just use this
http://forum.xda-developers.com/showthread.php?t=2232773
And the CM10 for our Oppo?
Sent from my X909 using xda app-developers app

newbcake said:
So would you say just use this
http://forum.xda-developers.com/showthread.php?t=2232773
And the CM10 for our Oppo?
Sent from my X909 using xda app-developers app
Click to expand...
Click to collapse
No, build from source since it's available.

mbh87 said:
No, build from source since it's available.
Click to expand...
Click to collapse
You mean Oppo's source or AOSP from Google? I presume AOSP
Sent from my X909 using xda app-developers app

assuming this is the one you want to port (it is using 4.2.2, so hopefully it'll be easier)
read their README: https://github.com/XYAOSP/buildscripts
use repo and checkout this manifest
https://github.com/XYAOSP/platform_manifest/blob/jb4.2/default.xml
use repo and sync all the repos
then see how I get the device specific files here? do the same https://git.ngvincent.com/projects/oppo-x909-cm10/wiki/Build#Get-device-specific-sources-and-build
then follow whatever instructions needed to build. if it uses CM based building (which i think they do here, then do
. build/envsetup.sh && brunch
select the find5 entry (if it;s not there, then do lunch, select find5, mka)
wait for it to fail. read error message. fix error message. repeat last 3 steps .. Google is your friend... learn to love google
---------------------------------------
you should try building CM10.1 first. there will hopefully be no errors, and you learn how to use brunch/lunch/breakfast / etc
https://git.ngvincent.com/projects/oppo-x909-cm10/wiki/Build

paperWastage said:
assuming this is the one you want to port (it is using 4.2.2, so hopefully it'll be easier)
read their README: https://github.com/XYAOSP/buildscripts
use repo and checkout this manifest
https://github.com/XYAOSP/platform_manifest/blob/jb4.2/default.xml
use repo and sync all the repos
then see how I get the device specific files here? do the same https://git.ngvincent.com/projects/oppo-x909-cm10/wiki/Build#Get-device-specific-sources-and-build
then follow whatever instructions needed to build. if it uses CM based building (which i think they do here, then do
. build/envsetup.sh && brunch
select the find5 entry (if it;s not there, then do lunch, select find5, mka)
wait for it to fail. read error message. fix error message. repeat last 3 steps .. Google is your friend... learn to love google
---------------------------------------
you should try building CM10.1 first. there will hopefully be no errors, and you learn how to use brunch/lunch/breakfast / etc
https://git.ngvincent.com/projects/oppo-x909-cm10/wiki/Build
Click to expand...
Click to collapse
Is there something wrong with the Xylon repo? I keep getting this:
Code:
Cannot fetch htc-msm8960/[some path here]

newbcake said:
Is there something wrong with the Xylon repo? I keep getting this:
Code:
Cannot fetch htc-msm8960/[some path here]
Click to expand...
Click to collapse
use google and your own intuition to help you (this is why you should build the Cm10.1 ROM first.... the knowledge you gain will help you)
most likely either github is down, or the path referencing it is invalid, or something......
but the question is, do we need htc-msm8960? most likely no, since the oppo kernel is self contained
^^^ all this comes from experience.... seriously, go build cm10.1 for the find 5 first

paperWastage said:
use google and your own intuition to help you (this is why you should build the Cm10.1 ROM first.... the knowledge you gain will help you)
most likely either github is down, or the path referencing it is invalid, or something......
but the question is, do we need htc-msm8960? most likely no, since the oppo kernel is self contained
^^^ all this comes from experience.... seriously, go build cm10.1 for the find 5 first
Click to expand...
Click to collapse
we probably dont need it, but a lot of ROMs make you download ALL their devices and corresponding files.

Well, I removed the HTC lines from manifest.xml (maybe not a good idea?) but anyway, it finished syncing after.

mbh87 said:
we probably dont need it, but a lot of ROMs make you download ALL their devices and corresponding files.
Click to expand...
Click to collapse
yeah... it's a problem with a simple fix.... if the error was something like "packages_mms_app", then it's a more serious problem.....
does removing that repo mask a larger problem? that's why I'm pushing for OP to start small first by building CM10.1, and learn the environment (instead of posting every single problem he encounters here, and asks for help)
I've only started playing with android source code in March/early april... and these are things that I've learned/picked up since then.

paperWastage said:
yeah... it's a problem with a simple fix.... if the error was something like "packages_mms_app", then it's a more serious problem.....
does removing that repo mask a larger problem? that's why I'm pushing for OP to start small first by building CM10.1, and learn the environment (instead of posting every single problem he encounters here, and asks for help)
I've only started playing with android source code in March/early april... and these are things that I've learned/picked up since then.
Click to expand...
Click to collapse
Understood. I'm syncing up the Cm10 now. Thanks!
Is is best to do this all on Linux, Mac, or Windows?

It isn't possible to do it on windows so one of the other two.

mbh87 said:
It isn't possible to do it on windows so one of the other two.
Click to expand...
Click to collapse
Cool thanks. I just "finished" my compile on my Mac 10.7.8 but there was something about gcc422 not found. I have the latest XCode installed along with Dev tools. So can anyone help cause I didn't see anything with a Google.
I presume a clean Ubuntu is preferred
Sent from my X909 using xda app-developers app

newbcake said:
Cool thanks. I just "finished" my compile on my Mac 10.7.8 but there was something about gcc422 not found. I have the latest XCode installed along with Dev tools. So can anyone help cause I didn't see anything with a Google.
I presume a clean Ubuntu is preferred
Sent from my X909 using xda app-developers app
Click to expand...
Click to collapse
it's preferable
even on ubuntu, you still have to get specific packages: need oracle version of jdk, not openjdk, need to remove some incompatible stuff
heres a guide for ubuntu 12.10
https://git.ngvincent.com/projects/oppo-x909-cm10/wiki/Android-setup

paperWastage said:
it's preferable
even on ubuntu, you still have to get specific packages: need oracle version of jdk, not openjdk, need to remove some incompatible stuff
heres a guide for ubuntu 12.10
https://git.ngvincent.com/projects/oppo-x909-cm10/wiki/Android-setup
Click to expand...
Click to collapse
I tried compiling CM10, and am even having problems with that. Google did not seem to help for this. Here is what I did:
I did the mka, then mka otapackage, and NOTHING is appearing. No zips at all.
Code:
hardware/qcom/media/mm-video/vidc/vdec/src/omx_vdec.cpp:9925:138: warning: format '%d' expects argument of type 'int', but argument 5 has type 'OMX_U32 {aka long unsigned int}' [-Wformat]
make: *** wait: No child processes. Stop.
That is the last fine before it gives me control of terminal again.

newbcake said:
I tried compiling CM10, and am even having problems with that. Google did not seem to help for this. Here is what I did:
I did the mka, then mka otapackage, and NOTHING is appearing. No zips at all.
Code:
hardware/qcom/media/mm-video/vidc/vdec/src/omx_vdec.cpp:9925:138: warning: format '%d' expects argument of type 'int', but argument 5 has type 'OMX_U32 {aka long unsigned int}' [-Wformat]
make: *** wait: No child processes. Stop.
That is the last fine before it gives me control of terminal again.
Click to expand...
Click to collapse
a few tips
typically, compilers only stop when there's an error, not warnings (unless you set flags like -Werror )
compiling is parallelized.... let's say you have a quad core, you can compile 4 projects simultaneously... when you have an error on the first make file, it stops.... but the other 3 projects will continue compiling and outputting logs until they're done (then the scheduler sees the first make file has an error, doesn't execute any more make builds and halts), so the last log file/line might not be showing you the error
For CM10.1, find5 is official now... you can just use brunch instead of breakfast/lunch & mka

paperWastage said:
a few tips
typically, compilers only stop when there's an error, not warnings (unless you set flags like -Werror )
compiling is parallelized.... let's say you have a quad core, you can compile 4 projects simultaneously... when you have an error on the first make file, it stops.... but the other 3 projects will continue compiling and outputting logs until they're done (then the scheduler sees the first make file has an error, doesn't execute any more make builds and halts), so the last log file might not be showing you the error
For CM10.1, find5 is official now... you can just use brunch instead of breakfast & mka
Click to expand...
Click to collapse
In essence, I scour the log for errors?
I just presumed as CM10 already existed on the Oppo Find 5, it would be an error-free compile.

newbcake said:
In essence, I scour the log for errors?
I just presumed as CM10 already existed on the Oppo Find 5, it would be an error-free compile.
Click to expand...
Click to collapse
you could source the log for errors
or just run the compile script again and again.... the scheduler will continue building other packages, but it'll come to a point where it can't build anything else without that broken package.... and hence, the error in the log will be obvious(since everything else is already built, no logs from them)
it should be an error-free compile, but sometimes things could happen (a small tweak in package/A gives some problems when compiling with package/B)
I would say, most likely there's some build package incompatibility in your system.

[SOURCES] Elife E7 - Discovery Elite Kernel Sources

Here is the kernel source for:
General Mobile Discovery Elite
Gionee Elife E7
These two devices using the same kernel source. You should use the defconfig from your own device to compile and use it with shared source.
Source link: http://www.burakgon.com/kernel-sources-for-general-mobile-discovery-elite-and-gionee-elife-e7-is-here/
Have fun while modifying!
XDA:DevDB Information
Gionee Elife E7 - General Mobile Discovery Elite Kernel Sources, a Kernel for the GiONEE Elife E7
Contributors
burakgon
Kernel Special Features:
Version Information
Status: Stable
Current Stable Version: 1
Stable Release Date: 2014-04-01
Created 2014-04-01
Last Updated 2014-04-05

Thanks a lot burakgon. I knew you were the real deal! Can you please post your ROM as well which is used in discovery mobile? And your flash tools which you promised to release as well?

[OFF TOPIC]
@burakgon Sir i Need General Mobile Discovery Kernel Source... You Made ATOM ROM Having ATOM Kernel For General Mobile Discovery Which Means You Have its Kernel Sources... i Tried Kernel Sources Released By FLY For its Fly-IQ4410 But Those Sources Are Not Complete Lots Of Drivers Are Missing And There is No Hope From Other Rebranded Devices... its An Humble Request Sir
Sorry To Disturb You Here...

Thank You very very much
let my exams complete
i will port cm

if you can provide device tree it will be awesome

yasirmujtaba said:
if you can provide device tree it will be awesome
Click to expand...
Click to collapse
I will try

Hi guys.
I am looking forward to support this awesome device. I got the source later i do the recovery and all stuff. Can anyone provide me stock boot.img and recovery.img.

icoolguy1995 said:
Hi guys.
I am looking forward to support this awesome device. I got the source later i do the recovery and all stuff. Can anyone provide me stock boot.img and recovery.img.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2706689

burakgon said:
I will try
Click to expand...
Click to collapse
hey burakgon did you got correct sources from gionee
i heard you were talking to gionee support for problems with kernel sources
pls reply

the sources that have been posted here might be correct but they (gionee) use a different (non standard) mkbootimg to pack it. that leads to issues. simply put, take their boot image or recovery, unpack it, without making any changes, repack it. the new file will be smaller in size. and device wont boot up if you flash them.

Ravikirancg said:
the sources that have been posted here might be correct but they (gionee) use a different (non standard) mkbootimg to pack it. that leads to issues. simply put, take their boot image or recovery, unpack it, without making any changes, repack it. the new file will be smaller in size. and device wont boot up if you flash them.
Click to expand...
Click to collapse
Ive tried upacking boot.img from my device replaced the zImage which i compiled from sources and again repacked it with the same ramdisk and flashed..The black screen appears. heard that sometimes the smaller size of ramdisk can be the culprit..

GTARaja said:
Ive tried upacking boot.img from my device replaced the zImage which i compiled from sources and again repacked it with the same ramdisk and flashed..The black screen appears. heard that sometimes the smaller size of ramdisk can be the culprit..
Click to expand...
Click to collapse
not exactly the size of ramdisk but the offset. we need a custom mkbootimg binary. need to edit mkbootimg.c and then re run make recoverytools. try unmkbootimg.

Ravikirancg said:
not exactly the size of ramdisk but the offset. we need a custom mkbootimg binary. need to edit mkbootimg.c and then re run make recoverytools. try unmkbootimg.
Click to expand...
Click to collapse
ive tried with different offsets from xperia z1 n nexus 5 didnt work.....not tried editing mkbootimg.c...ill try it later...btw can u compile it once for us if u have some spare time

Ravikirancg said:
the sources that have been posted here might be correct but they (gionee) use a different (non standard) mkbootimg to pack it. that leads to issues. simply put, take their boot image or recovery, unpack it, without making any changes, repack it. the new file will be smaller in size. and device wont boot up if you flash them.
Click to expand...
Click to collapse
afaik if gionee uses a custom mkbootimg wouldn't they have provided the custom tool to general mobile. if so burakgon could have provided us with same. I at least request him to provide us with general mobile firmware so as to test the theory that they might have made small hardware changes
in general elite.

GTARaja said:
ive tried with different offsets from xperia z1 n nexus 5 didnt work.....not tried editing mkbootimg.c...ill try it later...btw can u compile it once for us if u have some spare time
Click to expand...
Click to collapse
surely.. here you go https://www.dropbox.com/s/e62wf141ahcqy7j/mkbootimg
when you repack, keep base address as 0x0.
dhirajranger said:
afaik if gionee uses a custom mkbootimg wouldn't they have provided the custom tool to general mobile. if so burakgon could have provided us with same. I at least request him to provide us with general mobile firmware so as to test the theory that they might have made small hardware changes
in general elite.
Click to expand...
Click to collapse
well, I dont know much about Gionee to assume that it would have given the binary. afaik, it didnt even release the kernel sources.. let alone explain these. then again, I hope Gionee is dev friendly and helps us out. but I can assure you of one thing. Gionee does not use the standard methods. It surely has a messed up software on the device. it took me a week to get adb working properly on the terminal. Hell, I still cant get it to boot into fastboot mode..
P.S., It seems they use some signature for signing the recovery. I just unpacked the recovery and repacked it using mkbootimg. Its initial size was about 11mb. the newer one barely had a size of 8.7mb.
P.P.S., If some one is in touch with Gionee or get in touch with them, please pm..

Ravikirancg said:
surely.. here you go https://www.dropbox.com/s/e62wf141ahcqy7j/mkbootimg
when you repack, keep base address as 0x0.
well, I dont know much about Gionee to assume that it would have given the binary. afaik, it didnt even release the kernel sources.. let alone explain these. then again, I hope Gionee is dev friendly and helps us out. but I can assure you of one thing. Gionee does not use the standard methods. It surely has a messed up software on the device. it took me a week to get adb working properly on the terminal. Hell, I still cant get it to boot into fastboot mode..
P.S., It seems they use some signature for signing the recovery. I just unpacked the recovery and repacked it using mkbootimg. Its initial size was about 11mb. the newer one barely had a size of 8.7mb.
P.P.S., If some one is in touch with Gionee or get in touch with them, please pm..
Click to expand...
Click to collapse
Missing dt.img??
Sent from my ST25i using Tapatalk

AnoopKumar said:
Missing dt.img??
Sent from my ST25i using Tapatalk
Click to expand...
Click to collapse
ah! googled that up.. interesting.. the mkbootimg xperia ZU guys use syncs up with the one I built.. I will test that out..

They use some dtb.img.......
Have a look at dtb.img method
Sent from my Discovery Elite using XDA Premium 4 mobile app

This source is not good may be missing display driver.. Only giving black screen after booting.
Sent from my ST25i using Tapatalk
---------- Post added at 12:40 PM ---------- Previous post was at 12:38 PM ----------
Ravikirancg said:
ah! googled that up.. interesting.. the mkbootimg xperia ZU guys use syncs up with the one I built.. I will test that out..
Click to expand...
Click to collapse
You need to generate dt.img for for your complied zImage
Sent from my ST25i using Tapatalk

AnoopKumar said:
This source is not good may be missing display driver.. Only giving black screen after booting.
Sent from my ST25i using Tapatalk
---------- Post added at 12:40 PM ---------- Previous post was at 12:38 PM ----------
You need to generate dt.img for for your complied zImage
Sent from my ST25i using Tapatalk
Click to expand...
Click to collapse
yes I did that.. and as you mentioned, I get a white screen.. actually, my kernel itself didnt compile.. but I had some dts files and built a dt.img out of it.. if you built a stock kernel, mind sharinng your dt.img?