I am using the options you provided while creating my new boot image. " ./mkbootimg --kernel zImage --ramdisk newramdisk.cpio.gz *--base 0x30000000 --pagesize 4096* -o newtestboot.img "
Also, a slight typo in the make instructions export PATH=$PATH:/home/<uname>/mydroid/prebuilt/linux-x86/toolchain/arm-eabi-4.4.3/bin/ make ARCH=arm clean make ARCH=arm *CROSS_COMPILE=arm-eabi-* herring_defconfig make -j4 ARCH=arm CROSS_COMPILE=arm-eabi- On Wed, Mar 30, 2011 at 2:26 PM, Steve Modica <mod...@small-tree.com> wrote: > Did someone modify fastboot to not require the special options anymore? I > didn't think what you did would work. > > On Mar 30, 2011, at 2:04 PM, k b wrote: > > Finally managed to boot using my new kernel. The problem was with the > bootloader version I was using. Did the following to get it to work : > > 1. My Nexus S phone was still on 2.3.0. Updated it manually to 2.3.3 > (update.zip). Used Clockwork Mod Recovery to wipe dalvik cache, userdata and > cache partition because was facing the same boot loop of crashes. > > 2. Got latest kernel code and built : > git clone git://android.git.kernel.org/kernel/samsung.git > export > PATH=$PATH:/home/<uname>/mydroid/prebuilt/linux-x86/toolchain/arm-eabi-4.4.3/bn/ > make ARCH=arm clean > make ARCH=arm herring_defconfig > make -j4 ARCH=arm CROSS_COMPILE=arm-eabi- > > 3. Split the boot.img from update.zip and created new ramdisk img > ./split_bootimg.pl boot.img > mkdir ramdisk > cd ramdisk > gzip -dc ../boot.img-ramdisk.gz | cpio -i > find . | cpio -o -H newc | gzip > ../newramdisk.cpio.gz > > 4. Create new boot img using built zImage and newramdisk.cpio.gz > ./mkbootimg --kernel zImage --ramdisk newramdisk.cpio.gz --base > 0x30000000 --pagesize 4096 -o newtestboot.img > (if it hangs in the boot screen, wipe dalvik cache etc.) > > 5. To test : > fastboot boot newtestboot.img > To flash : > fastboot flash boot newtestboot.img > > > @Steve : Thanks for your help. > @Ian : Hope this helps. > > > On Tue, Mar 29, 2011 at 5:58 PM, Steve Modica <mod...@small-tree.com>wrote: > >> >> >>> I have exactly the same problem and as you can see from my post >>> (http://groups.google.com/group/android-kernel/browse_thread/thread/ >>> 6719c09c108b977a) I used the CROSS_COMPILE stuff when I built. Steve, >>> have you done this successfully? What exactly did you do? >>> >> >> I do the following: >> go into gingerbread tree >> source build/envsetup.sh >> cd into kernel/samsung >> make ARCH=arm CROSS_COMPILE=arm-eabi- menuconfig >> make ARCH=arm CROSS_COMPILE=arm-eabi- >> >> go to <root>/out/target/product/crespo >> fastboot -b 0x30000000 -n 4096 flash:raw boot ./zImage ./ramdisk.img >> >> I have a feeling you're missing the -b and -n parameters. >> >> -- >> Steve Modica >> CTO - Small Tree Communications >> www.small-tree.com >> phone: 651-209-6509 ext 301 >> mobile: 651-261-3201 >> >> >> >> >> >> >> >> -- >> unsubscribe: android-kernel+unsubscr...@googlegroups.com >> website: http://groups.google.com/group/android-kernel >> > > > -- > unsubscribe: android-kernel+unsubscr...@googlegroups.com > website: http://groups.google.com/group/android-kernel > > > -- > Steve Modica > CTO - Small Tree Communications > www.small-tree.com > phone: 651-209-6509 ext 301 > mobile: 651-261-3201 > > > > > > > -- > unsubscribe: android-kernel+unsubscr...@googlegroups.com > website: http://groups.google.com/group/android-kernel > -- unsubscribe: android-kernel+unsubscr...@googlegroups.com website: http://groups.google.com/group/android-kernel
