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

**Lmiller1708** · #31 (**permalink**) 10-29-2010, 05:45 PM

Quote:

Originally Posted by natemcnutty

OK, if you could, please try creating a new fullbuild.sh based on the updates I just made. I made sure that all pathing is correct regardless of where you launch the script from, and as long as you specify the locations of your sources in the beginning, it will work perfectly.

I tested moving my sources around, tested the new script, and compiling was still successful

Worked like a charm! Great job!

**natemcnutty** · #32 (**permalink**) 10-30-2010, 01:24 AM

Quote:

Originally Posted by Lmiller1708

Worked like a charm! Great job!

Awesome. Now that we've got this working, I'll start going through some of the significant files that you might want to modify. Early tomorrow I'll try to add more to the second post about the tinboot2.S file and init for rootfs. There's a few simple modifications you can do to change things for your liking, and hopefully I'll learn a few new things in the process

edwill · #33 (**permalink**) 10-30-2010, 10:05 AM

I have to let it go at this point. Followed the instructions to the letter. I have gone through the compiler multiple times and I get nothing. Just for FYI this is the final output from the compiler:

Quote:

Outputting modules to /home/edouble/android/output/sdcard
Start compiling tinboot/xip for rhod210.....
Inserting tinboot into payload
Inserting blank imgfs into payload
Creating os.nb portion of nbh
Creating NBH
updating: output/ (stored 0%)
updating: output/ruu_signed.NBH (deflated 10%)
updating: output/sdcard/ (stored 0%)
updating: output/sdcard/modules-2.6.27.46-01205-gf696d55.tar.gz (deflated 1%)

Thing is the referring files are empty. I know im doing something wrong so Im going to let it go. I will try the prebuilt NHB play with that. Keep up the work guys....

**Lmiller1708** · #34 (**permalink**) 10-30-2010, 10:55 AM

Quote:

Originally Posted by edwill

I have to let it go at this point. Followed the instructions to the letter. I have gone through the compiler multiple times and I get nothing. Just for FYI this is the final output from the compiler:

Thing is the referring files are empty. I know im doing something wrong so Im going to let it go. I will try the prebuilt NHB play with that. Keep up the work guys....

Check in your Android folder for a zip file. Or if you made a Dropbox folder check in there.
Everything looks fine from what you have showed.

Good luck!

**natemcnutty** · #35 (**permalink**) 10-30-2010, 03:19 PM

Quote:

Originally Posted by Lmiller1708

Check in your Android folder for a zip file. Or if you made a Dropbox folder check in there.
Everything looks fine from what you have showed.

Good luck!

Yeah, I'll put an echo at the end of the script to say where it is moving the files to. I love getting a chance to make this a little more user friendly

Edit: Script has been updated

Also fixed an issue where the sdcard folder may not have been created if you already had the output folder but not the sdcard folder.

pts69666 · #36 (**permalink**) 10-30-2010, 09:46 PM

what happens if you replace the blank filesystem with the rootfs.img? im going to experiment with this =P i guess there would be code in the kernel to not look for that file then... hmm...we shall play around and see what happens...

edit:
haha, thats a stupid idea... the initrd will still look for the rootfs on the SD card... hmm... i wonder if tinboot needs to be modded in any way for it to put the rootfs on the nand...

coolsilver · #37 (**permalink**) 11-02-2010, 12:03 AM

I would assume you would need to merge the rootfs into the nbh file with tinboot. How it would be addressed I am unsure. Then you need to worry about the system.ext2 and data.img. I am sure someone that does custom android roms for other phones can give an idea how to cook this.

pts69666 · #38 (**permalink**) 11-02-2010, 12:51 AM

Quote:

Originally Posted by coolsilver

I would assume you would need to merge the rootfs into the nbh file with tinboot. How it would be addressed I am unsure. Then you need to worry about the system.ext2 and data.img. I am sure someone that does custom android roms for other phones can give an idea how to cook this.

right, but on the other phones, the bootloader that is already on the phone allocates all that already. that is something they don't have to worry about. and if i'm not mistaken, rootfs.img would mount to the "/" directory and the data.img would mount to the "/data/" directory. idk where system.ext2 would mount...

but anyway, it might have to be different partitions on the nand. I think that when the NHB gets written to the nand, the .img/.bin file gets written as a pseudo-partition. just have to get the phone to know its there xD

**natemcnutty** · #39 (**permalink**) 11-02-2010, 12:52 AM

Quote:

Originally Posted by coolsilver

I would assume you would need to merge the rootfs into the nbh file with tinboot. How it would be addressed I am unsure. Then you need to worry about the system.ext2 and data.img. I am sure someone that does custom android roms for other phones can give an idea how to cook this.

Yeah, it's more of the changes to initrd and other components that rely on rootfs that I'm curious about. I know how to use yang to add it to the NBH, it's actually referencing it that I don't know how to do

pts69666 · #40 (**permalink**) 11-07-2010, 01:17 PM

Quote:

Originally Posted by natemcnutty

Yeah, it's more of the changes to initrd and other components that rely on rootfs that I'm curious about. I know how to use yang to add it to the NBH, it's actually referencing it that I don't know how to do

How did the Vogue Devs do it? It seems that they are the reference for any other device because it was the first. =P