Jump to content

Recommended Posts

Guest Frankish
Posted

Is there a guide for someone who has never done this before? I'm familiar with Ubuntu if that helps? I want to know the specifics for if i wanted to build tom g's blade kernel from source. Any help is mucho appreciated. Links, full walkthrough or fiery rage :(

Oh and i looked at the CM wiki but it says it's out of date now.

Guest Frankish
Posted

Thanks for the reply. I hope the 1.5ghz of ram isn't a strict requirement :( I'm glad you replied hec as i see you doing a lot around here.

Guest t0mm13b
Posted
Thanks for the reply. I hope the 1.5ghz of ram isn't a strict requirement :( I'm glad you replied hec as i see you doing a lot around here.

Have a look here which I blogged about compiling your own kernel....hope this helps :(

Guest hecatae
Posted
Have a look here which I blogged about compiling your own kernel....hope this helps :(

@t0mm13b, your instruction were the most helpful I've followed, though they did need a bit of editing to get what I needed working

Guest t0mm13b
Posted
@t0mm13b, your instruction were the most helpful I've followed, though they did need a bit of editing to get what I needed working

Ahh that's grand.... feel free to point out anything that I may have missed... :(

Guest hecatae
Posted
Ahh that's grand.... feel free to point out anything that I may have missed... :(

boot.img-ramdisk.cpio.gz > I found needs to be boot.img-ramdisk.gz on all instructions

and if you want to use the existing kernel to build the boot.img instead of zImage use boot.img-kernel

Guest ahngau
Posted

Sigh... That seems so hard for us mere mortals.

While you guys are at it, would you be so kind to see if it is possible to add call recording to CM7?

One of the great things about the blade is the call recording feature on Froyo but it seems like the CM devs don't want it in their rom. I have tried to push the phone.apk from FLB's 2.2 rom to CM7 but it seems like there are some missing methods in com.android.internal.telephony.

Guest t0mm13b
Posted
boot.img-ramdisk.cpio.gz > I found needs to be boot.img-ramdisk.gz on all instructions

and if you want to use the existing kernel to build the boot.img instead of zImage use boot.img-kernel

Thanks hecatae for the heads up :(

The tutorial was based on the Paul's Modaco Custom ROM, hence the minor differences... the mileage will vary between ROMS... unless there's a standard naming convention used that I am not aware of?

Guest Frankish
Posted

I'm currently stumbling at even just setting up git... :(

I have Java and Python sorted. I'll take another look when i first get home. Thanks for the help so far guys.

Guest hecatae
Posted
Thanks hecatae for the heads up :(

The tutorial was based on the Paul's Modaco Custom ROM, hence the minor differences... the mileage will vary between ROMS... unless there's a standard naming convention used that I am not aware of?

every boot.img I've split so far using split_bootimage.pl names one part boot.img-kernel and the other boot.img-ramdisk.gz

to decompress the boot.img-ramdisk.gz I have to add .cpio so it becomes boot.img-ramdisk.cpio.gz and then follow this http://discuz-android.blogspot.com/2008/01...ramdiskimg.html

Guest css771
Posted

Thanks for the guide guys. I did try to build from tom's sources using the instructions on the cyanogenmod wiki. And I did get an img file. But it wouldn't boot on my phone. So I'll try later with the guides here. Thanks a lot :(

ps, did anyone already build tom's new kernel on cm7? How's the battery looking now?

Guest Frankish
Posted
Thanks for the guide guys. I did try to build from tom's sources using the instructions on the cyanogenmod wiki. And I did get an img file. But it wouldn't boot on my phone. So I'll try later with the guides here. Thanks a lot :(

ps, did anyone already build tom's new kernel on cm7? How's the battery looking now?

I put a request in the cm7 thread for this, it would be nice to get just the updated boot.img so i don't need to reflash.

Guest hecatae
Posted
I'm currently stumbling at even just setting up git... :(

I have Java and Python sorted. I'll take another look when i first get home. Thanks for the help so far guys.

fonix232 has written a good guide here for setting up the sdk and adb http://android.modaco.com/content/zte-blad...e/#entry1558122

and fonix232 wrote a very simple guide here for setting up cyanogenmod source http://android.modaco.com/content/zte-blad...g-cyanogenmod7/

I follow it up to

repo sync -j16

and then I know I've got most tools needed

Guest Frankish
Posted

Great stuff. Keep the information coming. The more i have here the less questions i have to ask and can attempt to dive in. I dont have a real reason for wanting to do this i just wan to learn. I suppose i'll be able to get the latest boot.img for cm7 :(

Guest The-One
Posted

Download the arm toolchain from the android repo, git clone the kernel source used in cm7 export the path to the toolchain and make.

Guest jt_mcg
Posted (edited)

I used this tut on cynaogen's wiki, but substituting directory names and Tom's git and that has gotten me compiled kernels, but I seem to be missing something in the config stage, because after I remake the boot.img I never get usb storage/mounting/debugging to work.

tomm13b's blog post has been very informative too and I'm going to retry using his steps with hecatae's edits if necessary when I have a chance later on.

Thanks everyone for always providing information and help to get people like me to this stage even!

Edit: Also, fonix's building cm7 and then the wiki's for building were also great for getting the environment setup.

Edited by jt_mcg
Guest css771
Posted

ok I was finally successful in getting the new kernel to compile and flashed nightly 12 using the new kernel. However now, adb is not working. It says no devices found. Was there perhaps some a patch/ drivers for adb that I needed to add while compiling the kernel?

Guest hecatae
Posted (edited)
ok I was finally successful in getting the new kernel to compile and flashed nightly 12 using the new kernel. However now, adb is not working. It says no devices found. Was there perhaps some a patch/ drivers for adb that I needed to add while compiling the kernel?

t0mm13b's blog is missing -cmdline

mkbootimg –base 0x2A00000 -cmdline 'androidboot.hardware=blade console=ttyMSM2,115200 g_android.product_id=0x1354' –kernel zImage –ramdisk boot.img-ramdisk.cpio.gz -o boot.img

ran into the same problem on the honeycomb port, ended up with no ADB due to that line missing

-cmdline 'androidboot.hardware=blade console=ttyMSM2,115200 g_android.product_id=0x1354'

Edited by hecatae
Guest Frankish
Posted

I think i'm out of my depth here guys i'm giving up i think. :(

Guest hecatae
Posted
I think i'm out of my depth here guys i'm giving up i think. :(

how far have you got?

Guest jt_mcg
Posted (edited)

I still have no adb and am unable to mount usb!

I'm not sure what to do!

Am I missing something in the .config? is their a module I need to add in somewhere?

is it the aforementioned -cmdline? and where does it go! I see nothing in lsusb either so I'm assuming so...

myconfig.txt

Edited by jt_mcg
Guest css771
Posted (edited)
t0mm13b's blog is missing -cmdline

ran into the same problem on the honeycomb port, ended up with no ADB due to that line missing

-cmdline 'androidboot.hardware=blade console=ttyMSM2,115200 g_android.product_id=0x1354'

Thanks for that :( adb is working now :) The only thing left to do now is hope for better battery life I guess :(

Edited by css771
Guest jt_mcg
Posted
I think i'm out of my depth here guys i'm giving up i think. :(

If I can get close, you can surely build a kernel!!

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.