[Touch CDMA Android Development] wondercow:
Hi l1q1d, thanks for making atools. I'm not having much luck getting it to modify kernels for the Vogue, though. I have tried using it several times with older versions (1.0.4, 1.0.6) and not gotten it to work but never wrote in. I tried it today with the new 1.1.1 version and still couldn't get it to work correctly, and I figured I wasn't helping anyone by not posting. So, here is my story from today. I think atools isn't setting the paths correctly for the Vogue because even though I am telling it to install to nand, it seems to want to make .img files anyways.

So, I really wanted to try one of the experimental kernels from the Kaiser thread, so I downloaded KAISIMG.NBH from post 63 in that thread even though I am on Vogue. I loaded the file in atools, changed the device to Vogue, and left all other settings alone. Which is to say, it was set to 240x320 resolution, Froyo, system on nand p2, data on nand p3. I flashed to my phone, a bunch of text scrolled by, and it ended with this:

/init: line 334: mount_opt: not found
sh: 0 unknown operand
Found boot parameter for system
system on nand partition
mount: mounting /dev/block/mtdblock2 on /system failed: no such device or address
Found boot parameter for data
data on nand partition
/data failed: No such device or address
Install module for this kernel
apply modules/androidupdate.tgz
Failed
from sourceforge

At this point, I rebooted, held volume up when the screen told me to, and got to the boot menu. I clicked "install system" and watched it create a .img file on my fat32 SD card, so I took the card out, deleted the .img file, and tried again.

The second time, I went back to atools and changed the install locations from nand p2/p3 to "auto". I figured maybe if the boot menu would give me a choice, I could make this work. So, I saved and flashed the kernel. This time the screen stopped at:

bio too big device loop1 (2 > 0)
EXT2-fs: unable to read superblock
The superblock could not be read or does not describe a correct ext2 filesystem. If the device is valid and it really contains an ext2 filesystem (and not swap or ufs or something else), then the superblock is corrupt, and you might try running e2fsck with an alternate superblock: e2fsck -b 8193 <device>

e2fsck:
mount: mounting /dev/block/loop1 on /system failed: Invalid argument
Failed
Failed to mount /system

So, I reboot and hold volume up. I don't have a choice of where to install my system and data (normally I get a little menu where I can pick system on nand, system on ext2 SD, system on .img SD, etc.). I try installing system anyways hoping the default is nand, but it creates another .img file, which I delete from the SD card using my computer.

Ok, so maybe all this problem was because I was using an experimental kernel designed for the Kaiser, a totally different device than what I have. I can accept this, so time to go back to a real Vogue kernel. I close and re-open Atools and click the web button to download the kernel directly. It downloads the whole thing and fills in device Vogue, screen 240x320, Froyo, nand, development 2.6.32, system on nand p2, data on nand p3. Sounds perfect, so I create the file and flash. No luck:

sh: 2: unknown operand
Found boot parameter for system
system on nand partition
mount: mounting /dev/block/mtdblock2 on /system failed: No such device or address
Found boot parameter for data
data on nand partition
mount: mounting /dev/block/mtdblock3 on /data failed: No such device or address
Failed
Install module for this kernel

And it sits there with a blinking _ sign. So, granted, there is no reason for me to be using Atools at this point because I haven't changed any settings from the stock .NBH file from the git (I only did this last step for troubleshooting purposes). I download the latest Vogue .nhb from kernel-release on the git, flash it to my phone, and it works like a charm. In the volume-up boot menu, I have the option to set my install wherever I would like, and it installs to nand correctly.

Sorry for the long post, but I hope this is helpful. I suspect that Atools is not mapping the install location correctly for the Vogue and is forcing the .img option instead of flashing directly to Nand.