How To Compile Your Own Kernels, Modules, Tinboot (NAND boot), and More for Beginners

[Lmiller1708]

Originally Posted by oisact

I'm using the following script to automatically generate the proper module tarball name so I don't have to rename it manually:

# Generate module name. Assumes lib/modules contains one subdir with the target name
cd $MODULES_PATH/lib/modules
MODNAME=$(ls -d */)
MODNAME=modules-${MODNAME%/}.tar.gz

Just thought you might want to incorporate it in your build script to save the manual work.

This works too:

 KER_VER="$(cat $KERNEL_PATH/include/config/kernel.release)"

Aslo we don't use .tgz anymore. Only Haret does.

[oisact]

Does tinboot pertain to haret too, or only NAND? I'm building haret at the moment, and doing so under OSX (so no wine), so basically this is all just a big experiment at this point. If I can get a patent build environment set up then I'll see about contributing as I have time. I'm readying another iPhone game for release, plus my regular work projects on top of that, so I don't have a whole lot of spare time.

[Lmiller1708]

Originally Posted by oisact

Does tinboot pertain to haret too, or only NAND? I'm building haret at the moment, and doing so under OSX (so no wine), so basically this is all just a big experiment at this point. If I can get a patent build environment set up then I'll see about contributing as I have time. I'm readying another iPhone game for release, plus my regular work projects on top of that, so I don't have a whole lot of spare time.

Tinboot is only for NAND. Haret does not even need the NBH. And you do need to have the tgz... Sorry I thought you were doing this for NAND. Haret is different.

[MassStash]

woooooaaaahhhhh, thats weird... waitin for a lil more info on how things are going with new method to try that out....

[Lmiller1708]

Originally Posted by MassStash

woooooaaaahhhhh, thats weird... waitin for a lil more info on how things are going with new method to try that out....

Follow my directions and give it a try.

[natemcnutty]

Thanks to dadaR6 for helping me out. There were a few things wrong in the OP that he noticed. I removed the part about squashfs-tools using apt-get because that was wrong, and I changed the link for the rootfs build script since it was pointing to the old location.

I'm playing with my own autobuild right now, and hopefully I'll have a fully automated script to set up the entire dev environment for those who would rather run a simple shell script instead of walking through the whole first post.

[cmajewsk]

You state the folder structure should be:

Since the modules are now applied through androidupdate.tgz, you will need to make a directory structure in ~/android to look like this:

~/android
|--- androidupdate
|--- data
|--- system
|--- lib
|--- modules

Does that mean they are on the root of '/android'? Because you go on to note," put under /androidupdate/system/lib/modules". So are they inside each other like .android/andriodupdate/data/system...etc..? Plus I seem to already have a 'modules' folder under '/android'.

Also does it matter where you extract squashfs tools? Cause when I ran MAKE I received the following output:

cmajewski@cmlan-linux:~/squashfs3.4$ cd ~/squashfs3.4/squashfs-tools
cmajewski@cmlan-linux:~/squashfs3.4/squashfs-tools$ make
cc -I. -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_GNU_SOURCE -O2 -c -o mksquashfs.o mksquashfs.c
mksquashfs.c:39: fatal error: zlib.h: No such file or directory
compilation terminated.
make: *** [mksquashfs.o] Error 1

Any suggestions?

Thanks for all your help on this, you've done an amazing job!

[natemcnutty]

Originally Posted by cmajewsk

You state the folder structure should be:

Since the modules are now applied through androidupdate.tgz, you will need to make a directory structure in ~/android to look like this:

~/android
|--- androidupdate
|--- data
|--- system
|--- lib
|--- modules

Does that mean they are on the root of '/android'? Because you go on to note," put under /androidupdate/system/lib/modules". So are they inside each other like .android/andriodupdate/data/system...etc..? Plus I seem to already have a 'modules' folder under '/android'.

Also does it matter where you extract squashfs tools? Cause when I ran MAKE I received the following output:

cmajewski@cmlan-linux:~/squashfs3.4$ cd ~/squashfs3.4/squashfs-tools
cmajewski@cmlan-linux:~/squashfs3.4/squashfs-tools$ make
cc -I. -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_GNU_SOURCE -O2 -c -o mksquashfs.o mksquashfs.c
mksquashfs.c:39: fatal error: zlib.h: No such file or directory
compilation terminated.
make: *** [mksquashfs.o] Error 1

Any suggestions?

Thanks for all your help on this, you've done an amazing job!

Blah, stupid formatting issue on that. It should be showing more like a tree. I'll see if I can fix that.

As for the squashfs tools, I haven't had time to fix up my new VM, but I'll get more details on this when I do. Right now, I'm trying to get my phone unlocked again as I locked it in an attempt to get USB functioning again like LMiller did. Unfortunately, it did not work for me, and I'm now stuck on VZW's crappy stock ROM...

[manekineko]

Directions were great, thanks Nate!

For some reason building the kernel with the Google prebuild tools resulted in non-booting for me. Didn't even show the black screen before freeze on Haret.

Switched to CodeSourcery on emwe's advice that that's what most of the devs are using, and now all is well and booting. Might add a note into the first post that if using CodeSourcery, you just need to change the make line to point correctly to arm-none-eabi-gcc (full path is ~/CodeSourcery/Sourcery_G++_Lite/bin/arm-none-eabi-gcc for me when I installed the package from CodeSourcery rather than the one from your first post).

For some reason my build differs from the autobuild in size still, but hey, at least it's booting.

[Lmiller1708]

Wirelessly posted (TP2: Mozilla/5.0 (Linux; U; Android 2.2.1; en-us; pcdadr6350 Build/FRG83D) AppleWebKit/533.1 (KHTML, like Gecko) Version/4.0 Mobile Safari/533.1)

Originally Posted by manekineko

Directions were great, thanks Nate!

For some reason building the kernel with the Google prebuild tools resulted in non-booting for me. Didn't even show the black screen before freeze on Haret.

Switched to CodeSourcery on emwe's advice that that's what most of the devs are using, and now all is well and booting. Might add a note into the first post that if using CodeSourcery, you just need to change the make line to point correctly to arm-none-eabi-gcc (full path is ~/CodeSourcery/Sourcery_G++_Lite/bin/arm-none-eabi-gcc for me when I installed the package from CodeSourcery rather than the one from your first post).

For some reason my build differs from the autobuild in size still, but hey, at least it's booting.

Cool! Good job. Now we can have another helper...

I'm guessing you aren't using LK and that is why the size diff. Maybe send me a pm and I can help you out some more to get on the same page as us.