• 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

No prob. Hopefully it works better for you this time around.

I actually used the 7-zip app in Windows to combine the files initially so that should work for you too. If I remember correctly, you just have to:

1. Open the 7-zip app
2. Open the primary archive file from within the 7-zip program. (file #1 in this case)
3. Right-click in the 7-zip window, and the combine option should be available.
4. Select the combine option and it should prompt to create a new 7zip file with the contents of all the 7zip files.

Note: As with the linux instructions, all 7zip files should be in the same folder. If you open the primary 7zip file, the 7-zip program should find the remaining files automatically when combining.
 
meh, the only issue i had with building the kernel source code was with a couple drivers, the zimage builds fine though. it's the drivers that wont build for me. also, for some reason mine wouldnt boot, like i said before... Still trying to find a fix.
 
JBrd400 said:
No prob. Hopefully it works better for you this time around.

I actually used the 7-zip app in Windows to combine the files initially so that should work for you too. If I remember correctly, you just have to:

1. Open the 7-zip app
2. Open the primary archive file from within the 7-zip program. (file #1 in this case)
3. Right-click in the 7-zip window, and the combine option should be available.
4. Select the combine option and it should prompt to create a new 7zip file with the contents of all the 7zip files.

Note: As with the linux instructions, all 7zip files should be in the same folder. If you open the primary 7zip file, the 7-zip program should find the remaining files automatically when combining.
Click to expand...

I think I used winrar to unzip in windows and that's where I got the errors, i'll try 7zip and see if the file it says is missing is there, and but isn't a file with the ". o" extension an output from the compiler?
 
I just used the archive manager in linux to unzip the .7z files then once i got all the .zip files I unzipped them again to get the single tar file, then unzipped it one last time to get the final kernel src.. not sure if that broke it or not
 
Downthemachine - You could be right. I have very little programming experience so I can't say for sure. That said, the fact that you don't have the full kernel folder could still be your problem. It may be missing the component that creates that particular output file.

Snake - It doesn't sound like you combined the 7zip files before extracting. I would try combining them as mentioned previously and see where that gets you.
 
Well here's what I found on my windows laptop, it tries to overwrite some files when extracting the tar, because windows sees capitals and lower case letters the same, so I extracted it twice, one with yes to all, one with no to all. I'll copy it all over to the linux computer when I get home, including the tar file, also I will extract that. So I'll have three kernel folders, and I'll do a compare to see the differences

Edit:
You know I think I had troubles on linux extracting the 7zip files so I extracted the whole thing in windows xp, flipped it to a usb and went from there.
 
Why couldn't zte just use winrar to begin with to split the files instead of doing this insane method :confused: it makes no sense.. lol
 
Snake X said:
Why couldn't zte just use winrar to begin with to split the files instead of doing this insane method :confused: it makes no sense.. lol
Click to expand...

For real!
Or better yet, why couldn't they just use github? I :D
 
You might copying the combined 7zip file to linux and extract the kernel folder from there too. I don't remember how I did that part specifically, but I don't think I saw anything about overwriting files.
 
The real question is why did they split these files at all? Pretty much everyone's got broadband internet now so why make smaller downloads?
 
Overwriting was in windows, Linux I'm pretty sure two files can have the same name, cause its case sensitive
And windows is not
 
Well once downthemachine compares the results and comes with something to conclude what the correct method to unzip the source, I'm just going to wait for that to happen so I can be sure that its correct.. lol it seems like unzipping is a problem of its own now
 
Right, was just suggesting you copy the file output by 7-zip to Linux and doing the final extraction from there so as to prevent the overwriting. (which may or may not screw up the source files)
 
Amazing how complicated the simplest thing could be. Lol (not the build, the darn zips)

I'll be done with work in an hour, and I'll post my results a little after
 
I don't quite think that will work.. But you can try and let us know! I have a funny feeling that zte used some proprietary method in linux to split those files
 
It's not proprietary. It shows what compression was used right in the file names. N860-kernel.7z.001.zip

Nice utility tookah! Wish I knew about that one earlier...
 
Oh I thought it was done through some method that might have been only doable by the linux os or something and you had to do it a certain way, I didn't know
 
Untar with linux, and built completed with toolchain 4.4.0! Yay! Is it bootable? No clue
 
I did all mine on ubuntu so it compiled fine after i figured out how to combine them, problem is the source is screwed up. Either that or we need the stock kernels offset for the padding
 
shinru2004 said:
I did all mine on ubuntu so it compiled fine after i figured out how to combine them, problem is the source is screwed up. Either that or we need the stock kernels offset for the padding
Click to expand...

Offset? I'm still learning all this, also it compiled with 4.4.3 now
 
Well, I was hoping someone else would respond as I don't really know what it is technically. I think it has to do with where kernel data is stored in memory, but I'm still learning this stuff too.

From a practical standpoint, you need to find the kernel offset (aka base) address as it should be specified in the kernel. (not necessary if you're using stock .config) It should also be specifed when running the mkbootimg command to repack boot.img. You can find the base address by looking at a given kernel's .config file. Do a search for "CONFIG_PHYS_OFFSET" and you should find it. You should also be able to find the offset value specified in the kernel source. You need to find the defconfig file for the Warp in the ./arch/arm/configs folder. Also be sure to look for the CONFIG_CMDLINE value in the kernel's .config file as it is important as well.

You might check out the various tutorials on extracting and repacking boot.img. Here's 1 to get you started. They don't all mention the --base parameter for mkbootimg, but that's where you specify the kernel offset. There's also a --pagesize parameter that isn't mentioned much either.

HOWTO: Unpack, Edit, and Re-Pack Boot Images - Android Wiki
 
You must log in or register to reply here.
Back
Top Bottom