[AT&T Samsung Galaxy S II Skyrocket SGH-I727] wantowan2:
Wow, thanks dude.

I started over again about an hour ago. Just in case I effed with something last night and don't rmember. (was late) .....and I'm getting productive output! Still, not too optomistic but , progress...

The part of the tut that I am not getting forsure is the end. To me, there should be some sort of manifest directing to an "out" of some sort. Once that is done, I still need a way to make this thing flashable...? lol The tut says that is "out of scope" lol

Edit:

For example, this is what happens when it finishes and I have to gether the various things..

~/android/device/kernel/msm8660-common$ mkdir ../cyanogenmod_skyrocket_output
mkdir: cannot create directory `../cyanogenmod_skyrocket_output': File exists
:~/android/device/kernel/msm8660-common$ cp arch/arm/boot/zImage ../cyanogenmod_skyrocket_output/zImage
cp: accessing `../cyanogenmod_skyrocket_output/zImage': Not a directory
:~/android/device/kernel/msm8660-common$ find . -name "*.ko" -exec cp {} ../cyanogenmod_skyrocket_output \;
:~/android/device/kernel/msm8660-common$ cp arch/arm/boot/ zImage ../cyanogenmod_skyrocket_output/ zImage
cp: target `zImage' is not a directory
:~/android/device/kernel/msm8660-common$ find . -name "*.ko" -exec cp {} ../cyanogenmod_skyrocket_output \;
:~/android/device/kernel/msm8660-common$ cp arch/arm/boot/zImage ../cyanogenmod_skyrocket_output/zImage
cp: accessing `../cyanogenmod_skyrocket_output/zImage': Not a directory
:~/android/device/kernel/msm8660-common$

And when I try to nav to the location manually, there is no "zimage" there. However, I did find, (this is weird) a file not only a folder called "cyanogenmod_skyrocket_output" as type"object code (application/x-object)" and 113.3 kB. I tried to open it and it took forever. When it did, it was all machine language. I suspect that this is infact the zImage named "cyanogenmod_skyrocket_output" for some reason....

Edit: I went ahead and built the moduals cuz ..... I dunno and couldn't collect the as stated in the tut so I went and weeded them out manually. I wonder if this is all of them ?

~/android/device/kernel/msm8660-common$ make modules
CHK include/linux/version.h
CHK include/generated/utsrelease.h
make[1]: `include/generated/mach-types.h' is up to date.
CALL scripts/checksyscalls.sh
Building modules, stage 2.
MODPOST 20 modules
CC arch/arm/mach-msm/dal_remotetest.mod.o
LD [M] arch/arm/mach-msm/dal_remotetest.ko
CC arch/arm/mach-msm/dma_test.mod.o
LD [M] arch/arm/mach-msm/dma_test.ko
CC arch/arm/mach-msm/msm-buspm-dev.mod.o
LD [M] arch/arm/mach-msm/msm-buspm-dev.ko
CC arch/arm/perfmon/ksapi.mod.o
LD [M] arch/arm/perfmon/ksapi.ko
CC crypto/ansi_cprng.mod.o
LD [M] crypto/ansi_cprng.ko
CC drivers/crypto/msm/qce.mod.o
LD [M] drivers/crypto/msm/qce.ko
CC drivers/crypto/msm/qcedev.mod.o
LD [M] drivers/crypto/msm/qcedev.ko
CC drivers/crypto/msm/qcrypto.mod.o
LD [M] drivers/crypto/msm/qcrypto.ko
CC drivers/input/evbug.mod.o
LD [M] drivers/input/evbug.ko
CC drivers/media/video/gspca/gspca_main.mod.o
LD [M] drivers/media/video/gspca/gspca_main.ko
CC drivers/misc/msm_tsif.mod.o
LD [M] drivers/misc/msm_tsif.ko
CC drivers/misc/tsif_chrdev.mod.o
LD [M] drivers/misc/tsif_chrdev.ko
CC drivers/misc/vibetonz/vibrator.mod.o
LD [M] drivers/misc/vibetonz/vibrator.ko
CC drivers/mmc/card/mmc_test.mod.o
LD [M] drivers/mmc/card/mmc_test.ko
CC drivers/net/wireless/bcmdhd_samsung/dhd.mod.o
LD [M] drivers/net/wireless/bcmdhd_samsung/dhd.ko
CC drivers/scsi/scsi_wait_scan.mod.o
LD [M] drivers/scsi/scsi_wait_scan.ko
CC drivers/spi/spidev.mod.o
LD [M] drivers/spi/spidev.ko
CC drivers/video/backlight/lcd.mod.o
LD [M] drivers/video/backlight/lcd.ko
CC net/sched/cls_flow.mod.o
LD [M] net/sched/cls_flow.ko
CC net/sched/sch_dsmark.mod.o
LD [M] net/sched/sch_dsmark.ko

Just the "LD [M] * .ko" ones

One more thing about the "thewadegeek" tut. If I'm not mistakend, isn't a zImage really a *.tar.zImage? Meaning that this would be odin?