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

edwill · #21 (**permalink**) 10-29-2010, 01:42 AM

OK Ive tried everything I can think of. It begins to compile and at the last minuet I get this:

Outputting files to /home/edouble/android/output/sdcard
mv: cannot move `modules-2.6.27.46-01203-g4e5852fb.tar.gz' to `/home/edouble/android/output/sdcard': No such file or directory
Start compiling tinboot/xip for rhod210.....
/home/edouble/android/tinboot-linux-msm/tinboot/tinboot2.S: Assembler messages:
/home/edouble/android/tinboot-linux-msm/tinboot/tinboot2.S:115: Error: file not found: kernel/zImage
/home/edouble/android/tinboot-linux-msm/tinboot/tinboot2.S:117: Error: file not found: kernel/initrd.gz
/home/edouble/android/prebuilt/linux-x86/toolchain/arm-eabi-4.4.0/bin/arm-eabi-objcopy: 'tinboot.o': No such file
mv: cannot stat `tinbootxip': No such file or directory
rm: cannot remove `tinboot.o': No such file or directory
Inserting tinboot into payload
fullbuild.sh: 122: wine: not found
mv: cannot stat `os.nb.payload.NEW': No such file or directory
Inserting blank imgfs into payload
fullbuild.sh: 125: wine: not found
Creating os.nb portion of nbh
fullbuild.sh: 127: cannot open OS-new.nb.payload: No such file
Creating NBH
fullbuild.sh: 129: wine: not found
rm: cannot remove `OS-new.nb.payload': No such file or directory
rm: cannot remove `OS-new.nb': No such file or directory
mv: cannot stat `/home/edouble/android/tinboot-linux-msm/ruu_signed.NBH': No such file or directory
zip warning: name not matched: output

zip error: Nothing to do! (try: zip -r 20101029-2.6.27.46-01203-g4e5852fb.zip . -i output)
cd: 146: can't cd to android/tinboot-linux-msm/tinboot
rm: cannot remove `*.NBH': No such file or directory
cd: 148: can't cd to sdcard
rm: cannot remove `*.tar.gz': No such file or directory
edouble@ubuntu:~/android/tinboot-linux-msm/tinboot$

What am I missing. I followed the instructions to the letter. Im thinking this has something to do with where the compiler puts the .NHB file but Im not sure. Plz help.... Thanks....

**natemcnutty** · #22 (**permalink**) 10-29-2010, 02:14 AM

Quote:

Originally Posted by edwill

OK Ive tried everything I can think of. It begins to compile and at the last minuet I get this:

Outputting files to /home/edouble/android/output/sdcard
mv: cannot move `modules-2.6.27.46-01203-g4e5852fb.tar.gz' to `/home/edouble/android/output/sdcard': No such file or directory
Start compiling tinboot/xip for rhod210.....
/home/edouble/android/tinboot-linux-msm/tinboot/tinboot2.S: Assembler messages:
/home/edouble/android/tinboot-linux-msm/tinboot/tinboot2.S:115: Error: file not found: kernel/zImage
/home/edouble/android/tinboot-linux-msm/tinboot/tinboot2.S:117: Error: file not found: kernel/initrd.gz
/home/edouble/android/prebuilt/linux-x86/toolchain/arm-eabi-4.4.0/bin/arm-eabi-objcopy: 'tinboot.o': No such file
mv: cannot stat `tinbootxip': No such file or directory
rm: cannot remove `tinboot.o': No such file or directory
Inserting tinboot into payload
fullbuild.sh: 122: wine: not found
mv: cannot stat `os.nb.payload.NEW': No such file or directory
Inserting blank imgfs into payload
fullbuild.sh: 125: wine: not found
Creating os.nb portion of nbh
fullbuild.sh: 127: cannot open OS-new.nb.payload: No such file
Creating NBH
fullbuild.sh: 129: wine: not found
rm: cannot remove `OS-new.nb.payload': No such file or directory
rm: cannot remove `OS-new.nb': No such file or directory
mv: cannot stat `/home/edouble/android/tinboot-linux-msm/ruu_signed.NBH': No such file or directory
zip warning: name not matched: output

zip error: Nothing to do! (try: zip -r 20101029-2.6.27.46-01203-g4e5852fb.zip . -i output)
cd: 146: can't cd to android/tinboot-linux-msm/tinboot
rm: cannot remove `*.NBH': No such file or directory
cd: 148: can't cd to sdcard
rm: cannot remove `*.tar.gz': No such file or directory
edouble@ubuntu:~/android/tinboot-linux-msm/tinboot$

What am I missing. I followed the instructions to the letter. Im thinking this has something to do with where the compiler puts the .NHB file but Im not sure. Plz help.... Thanks....

So, two things. First, you still need to install wine. Just do a sudo apt-get install wine. Second, I need to fix a tiny bit in the script. I changed it up for people who didn't put the android folder in their home directory and forgot to fix the relative path on tinboot.

Edit: OK, pretty sure I found the issue with the XIP part. Once you get wine installed, I think you'll be all set

pts69666 · #23 (**permalink**) 10-29-2010, 09:07 AM

Quote:

Originally Posted by edwill

OK Ive tried everything I can think of. It begins to compile and at the last minuet I get this:

`/home/edouble/android/output/sdcard': No such file or directory

What am I missing. I followed the instructions to the letter. Im thinking this has something to do with where the compiler puts the .NHB file but Im not sure. Plz help.... Thanks....

one thing not in the instructions that is needed is a:

mkdir /home/edouble/android/output/sdcard

also as natemcnutty said, you still need to install wine =D

**Lmiller1708** · #24 (**permalink**) 10-29-2010, 10:58 AM

Quote:

Originally Posted by pts69666

one thing not in the instructions that is needed is a:

mkdir /home/edouble/android/output/sdcard

also as natemcnutty said, you still need to install wine =D

There are a couple of folders that need to be made. One pointed above, and the XIP folder. You already created it but it was made in the android folder and not the tinboot-linux-msm like it should be.

Then the code will work great! Thanks again!

Code:

if [ ! -d "$TINBOOT/xip" ] ; then
mkdir $TINBOOT/xip
fi
if [ ! -d "$OUTPUT_PATH" ] ; then
mkdir $OUTPUT_PATH
mkdir $OUTPUT_PATH/sdcard
fi

edwill · #25 (**permalink**) 10-29-2010, 12:46 PM

OK, installed wine and added the extra folders. I did start over to make sure everything was done correctly. I get to the end as before but this time I get:

Outputting files to /home/edouble/android/output/sdcard
Start compiling tinboot/xip for rhod210.....
mv: cannot move `tinbootxip' to `xip/rhod210': No such file or directory
Inserting tinboot into payload
mv: cannot stat `os.nb.payload.NEW': No such file or directory
Inserting blank imgfs into payload
Creating os.nb portion of nbh
Creating NBH
updating: output/ (stored 0%)
updating: output/sdcard/ (stored 0%)
updating: output/sdcard/modules-2.6.27.46-01204-ga0bebc2.tar.gz (deflated 1%)
updating: output/ruu_signed.NBH (deflated 11%)

The compiler stops there and then gives me the command prompt. I really feel like a noob but I really want to try this out. What am I missing?

pts69666 · #26 (**permalink**) 10-29-2010, 12:55 PM

Quote:

Originally Posted by edwill

OK, installed wine and added the extra folders. I did start over to make sure everything was done correctly.

I will try running the script with rhod210 when I get home if this isn't resolved. I myself ran it as rhod400, so I will see what different results I get when I run it as your model.

Edit:

Try finding this part of the code in the script:

Code:

$TOOLCHAIN_PATH-objcopy tinboot.o -O binary tinbootxip
mv tinbootxip xip/$1

and changing it to

Code:

$TOOLCHAIN_PATH-objcopy tinboot.o -O binary tinbootxip
mkdir xip/$1
mv tinbootxip xip/$1

that should clear up the first error, unless it cannot find tinbootxip. if thats the case, i will have to look at it more when i get home

Code:

mv: cannot move `tinbootxip' to `xip/rhod210': No such file or directory

as far as the

Code:

mv: cannot stat `os.nb.payload.NEW': No such file or directory

i will have to wait until i get home to look at. that'll be like 3 hours or so.

**[ACL]** · #27 (**permalink**) 10-29-2010, 01:03 PM

ahh man .. hope you dont brick yourself . i corrupted my phone already once and wozzer ended up needing a new phone. Just gotta be careful.

**Lmiller1708** · #28 (**permalink**) 10-29-2010, 01:20 PM

Quote:

Originally Posted by edwill

OK, installed wine and added the extra folders. I did start over to make sure everything was done correctly. I get to the end as before but this time I get:

Outputting files to /home/edouble/android/output/sdcard
Start compiling tinboot/xip for rhod210.....
mv: cannot move `tinbootxip' to `xip/rhod210': No such file or directory
Inserting tinboot into payload
mv: cannot stat `os.nb.payload.NEW': No such file or directory
Inserting blank imgfs into payload
Creating os.nb portion of nbh
Creating NBH
updating: output/ (stored 0%)
updating: output/sdcard/ (stored 0%)
updating: output/sdcard/modules-2.6.27.46-01204-ga0bebc2.tar.gz (deflated 1%)
updating: output/ruu_signed.NBH (deflated 11%)

The compiler stops there and then gives me the command prompt. I really feel like a noob but I really want to try this out. What am I missing?

Add the lines of code to the script from my post above this and it should work out just fine.

**natemcnutty** · #29 (**permalink**) 10-29-2010, 04:12 PM

Quote:

Originally Posted by Lmiller1708

There are a couple of folders that need to be made. One pointed above, and the XIP folder. You already created it but it was made in the android folder and not the tinboot-linux-msm like it should be.

Then the code will work great! Thanks again!

Code:

if [ ! -d "$TINBOOT/xip" ] ; then
mkdir $TINBOOT/xip
fi
if [ ! -d "$OUTPUT_PATH" ] ; then
mkdir $OUTPUT_PATH
mkdir $OUTPUT_PATH/sdcard
fi

Thanks. Yeah, all of the problems are because I removed the relative references. I always run my script from the tinboot directory, and my script was grabbing the pwd. I had this:

if [ ! -d "$TINBOOT/xip" ] ; then
mkdir xip
fi

instead of

if [ ! -d "$TINBOOT/xip" ] ; then
mkdir $TINBOOT/xip
fi

That should be fixed now. Also, I missed the fact that the buildxip.sh script in tinboot actually has if -a instead of if -d which will fail the build as well

**natemcnutty** · #30 (**permalink**) 10-29-2010, 05:01 PM

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