• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root [Boost Mobile] kernel source code won't build

So was stock 0x080000000? Or something like that? Man this stuff is way confusing. I unpacked and split the kernal out of a nandroid boot.img. I haven't tried to repack it with the one I made yet. I'm still trying to figure this stuff out.
 
Yeah, it's abstract stuff no doubt. Stock should be 0x00200000, but you should verify for yourself just to better understand the process. ;)
 
Ya man, i'm completely lost, and I found the offset. But that page completely confused me.
 
Yeah, it's one of those things where the more you know, the more you realize you don't know. Not something you learn overnight. Don't feel bad though...I'm pretty lost on the vast majority of the kernel settings too. You *really* have to know android and your device's hardware when making changes in there. (and that's not even counting creating your own custom modules, etc.) I have a lot of respect for true devs...

Anyway, that .config file is just a list of all the kernel settings. Make menuconfig is essentially the same thing, just in a graphical version.

Edit: Here's another link. It covers the whole porting process, but there are parts that you may find useful with regard to extracting and repacking the kernel & boot.img.

http://www.freeyourandroid.com/guide/porting-android
 
here try this when you make the boot.img i think this is why it wouldn't boot before

./mkbootimg --cmdline 'console=ttyMSM1,115200' --kernel zImage --ramdisk ramdisk-new.gz --base 0x00200000 --pagesize 4096 -o boot.img

i was able to unpack and repack the stock boot.img using the above command and it booted right up
it has to be the source because i cannot get the kernel to boot period no matter what i do, i don't believe the modules are keeping it from starting but i will make an update.zip and flash the kernel and the modules together and see what happens
 
So I'll try to pack the kernel tonight, and literally fell asleep reading about boot imgs, headers, offsets, lol. But I also tried to build the cm kernal, didn't make it far at all, and that was with a stock config. I honestly wanted to see if the process would be the same, the and it's not. For the most part the sources are exactly the same, the but the cm kernal has a good 20 - 30 files that are different, when compared, these files just look like older versions. But I'll keep digging
 
Yeah, I pretty much use the same command line as shinru. I just specify the boot.img-kernel file instead of zImage. Not sure if it matters, but I was also able to unpack/repack the stock kernel and it worked. Haven't had much luck with others, but I'm more concerned with the CM7 boot/partition issue at this point.

Don't think I've messed with CM7 kernels yet, but you might try using a different toolchain and see what happens. 4.4.0 and 4.4.3 seem to be the most popular.
 
Code: 
MIME-Version: 1.0
Received: by 10.220.3.143 with HTTP; Fri, 23 Mar 2012 09:05:31 -0700 (PDT)
Date: Fri, 23 Mar 2012 12:05:31 -0400
Delivered-To: shinru2004@gmail.com
Message-ID: <CAFuO_Hzy06KSYZA=f4v2RxRb5hVjAU0t-DYUDFfcfM3FDKe-DA@mail.gmail.com>
Subject: ZTE Warp kernel source code
From: michael miller <shinru2004@gmail.com>
To: support@zte.com.cn
Content-Type: multipart/alternative; boundary=047d7b34355aac902604bbeb31e2

--047d7b34355aac902604bbeb31e2
Content-Type: text/plain; charset=ISO-8859-1

Hello,

First of all let me start by saying I'm really enjoying my ZTE Warp. but
the reason i have contacted you is because i am concerned about the kernel
source code for the Warp, I as well as 4 other people have tried to build
the source code. After some trial and error we have been able to get to
source code to compile with the 4.4.0 tool-chain as well as the
4.4.3 tool-chain. Even though we have been able to get it to compile we
still cannot get the kernel to boot our phones, Mainly i was wondering if
there might be something wrong with the Kernel source code. We have had
veterans try compiling the source and they can't even get it to boot, if
you could please let me know if there is anything wrong with the source or
maybe re-post a newer version if you could. It would be greatly
appreciated, and would help us in bringing more new possibilities to this
device as well as popularity

Waiting to get a reply
 
That's what ive been wondering since ive seen the video tutorial on how to build an android kernel from src
 
Koush's any kernel wont work on our phone unless we change out the update-binary and edit the updater-script to mount our ext4 partitions correctly. that file came out way before ext4 appeared on android. it mounts a normal MTD partition, let me edit it and then anyone who wants to try it can do so. but first check out Hoarks boot.img packer its made for the warp
 
Ok im downloading the ZTE Fury N850 Source code, there's a good chance they are exactly the same, Hardware specs are identical. Only Difference is the screen resolution which shouldn't be a problem with the default warp config added

The N850 Source Code Contains the Arthur Defconfig for the warp so chance are the source will work on our phones
 
couldn't get the fury source to build for the warp, so i retried the warp source compiled and installed

never mind it was some kinda fluke and the kernel didn't flash for some reason ........
 
Snake X said:
I wouldnt go *too* experimental with kernels.. one messup and no more cwm!
Click to expand...

The kernel shouldnt hurt the cwm install, every kernel i have tried cwm always works, they should be on seperate blocks

Sent from my N860 using Tapatalk 2 Beta-2
 
I guess.. just if you mess it up *too* badly though there's a risk it won't even boot into that part at all
 
Time to find some cheap used warps for testing :D I had one I got from a guy on the forums, but then my wife's phone crapped out, so she snagged it from me :banghead:
 
so has noone been able to successfully compile the kernel by source yet? Does the kernel used in cm7 count?
 
You must log in or register to reply here.
Back
Top Bottom