[Kernel Source] ToAsTcfh-Eclair-2.6.27 {Updated- Apr30, 2010} Murder-Kernel

[5tr4t4]

I suspect the new boot.img was not created with the correct hero base address, 0x19200000 (tip from Lox):

mkbootimg --kernel boot.img-kernel --ramdisk ramdisk-boot --cmdline "no_console_suspend=1 console=null" -o newBoot.img --base 0x19200000

I have a working update.zip now using aosp2.1-darchstar, just testing. I'm attaching my boot.img with the correct base address. It should work with whatever ROM you have.

I double-checked my kernel build, I enabled:

MSM Hardware 3D Register Driver
2. Android 2.0+ (Eclair) (MSM_HW3D)

...this was the only difference in the config that I could find, so I can only assume this is the 3D stuff. If so, the boot.img above is correct. Let me know if if works for others.

 

[wtphoto]

no I ended up nandroiding back to fresh, and im in the process of clean flashing flipz 2.1. I'll post the results of the flash_image when the rom loads.
But weird it wouldnt work.
And it wouldn't flash in recovery mode because it couldnt find the sdcard dir

im in the same exact boat nandroid just got done

 

[5tr4t4]

your zip needs to be signed and it wont let me sign it because batch process fails?

Sorry to confuse, I just zipped it up assuming the forum would allow me to attach an ".img" file. This should be unzipped BEFORE moving over to the sdcard. Then from the adb shell:

flash_image boot boot.img

 

[5tr4t4]

Actually it made with those exact commands including the base address...

Hmm, not sure. I got stuck at the boot too until I replacked the boot.img with the --base command. Go figure

 

[Avalaunchmods]

Sorry to confuse, I just zipped it up assuming the forum would allow me to attach an ".img" file. This should be unzipped BEFORE moving over to the sdcard. Then from the adb shell:

flash_image boot boot.img

ooo ok i was under the impression you incorporated the image file into an update.zip file for nandroid.

but no biggy now i am the boat that cant find the boot image so ill try while connected to recovery and we will see what happens

 

[regaw_leinad]

i had something like that happen once before but no fastboot or anything. just a dead phone. fixed it with RUU

anyways were you able to flash the image?

I literally wiped and flashed the ROM again... and still a no go on the flash_image... I've tried everything... couldn't be my sdcard..? it works perfectly for everything else..

 

[gators0223]

Hmm, not sure. I got stuck at the boot too until I replacked the boot.img with the --base command. Go figure

Huh...I don't know. But I'm sure it was in there the first time. I compiled my first kernel last night following the tutorial here on xda exactly so I'm not sure what happened.

Anyway, in case anyone is interested, I made an update.zip for the one I posted earlier. It is working for me on Flipz 2.1. I have not tested any other rom with it. (this IS an update.zip you can flash through recovery)

Again, do this at your own risk. It worked for me though...

 

[regaw_leinad]

Huh...I don't know. But I'm sure it was in there the first time. I compiled my first kernel last night following the tutorial here on xda exactly so I'm not sure what happened.

Anyway, in case anyone is interested, I made an update.zip for the one I posted earlier. It is working for me on Flipz 2.1. I have not tested any other rom with it. (this IS an update.zip you can flash through recovery)

Again, do this at your own risk. It worked for me though...

ok tryin it out. hopefully I'll have better luck this time

 

[Avalaunchmods]

I literally wiped and flashed the ROM again... and still a no go on the flash_image... I've tried everything... couldn't be my sdcard..? it works perfectly for everything else..

lol man you are getting some crazy issues. if i were you just wipe completely. restore nandroid flipz2.1 the go to page 3 and follow the guide he posted word for word including the push. i finally just got it to work.

DO IT ALL IN RECOVERY THROUGH CMD PROMPT INCLUDING THE PUSH ADB

it works and this is an incredible rom now multitouch FTW

 

[wtphoto]

Huh...I don't know. But I'm sure it was in there the first time. I compiled my first kernel last night following the tutorial here on xda exactly so I'm not sure what happened.

Anyway, in case anyone is interested, I made an update.zip for the one I posted earlier. It is working for me on Flipz 2.1. I have not tested any other rom with it. (this IS an update.zip you can flash through recovery)

Again, do this at your own risk. It worked for me though...

man you are a pimp and a half right now thanks much it worked great.

 

[regaw_leinad]

OK the update.zip worked lol
don't know why I was having so many problems lol
I'll try the whole method again tomorrow... when I'm actually awake

AND WOWOWOWOWOW Multitouch is great!

 

[Tikerz]

I double-checked my kernel build, I enabled:

MSM Hardware 3D Register Driver
2. Android 2.0+ (Eclair) (MSM_HW3D)

...this was the only difference in the config that I could find, so I can only assume this is the 3D stuff. If so, the boot.img above is correct. Let me know if if works for others.

I just flashed it to AOSP 2.1 and it booted, but there's really no speed improvement that I could tell. Like you said earlier, Gallery is still really slow.

 

[Avalaunchmods]

OK the update.zip worked lol
don't know why I was having so many problems lol
I'll try the whole method again tomorrow... when I'm actually awake

AND WOWOWOWOWOW Multitouch is great!

good to hear man

i cant run neocore thought which is a bummer but im sure we will see much much more stuff come out tom. i believe ima crash too. thanks alot to the guy who posted the img file and everybodys work/help tonight.

 

[kniteshift]

I wish I could make it easier, but if you just can't wait for someone to make an update.zip, here is the new boot image and wireless module. Sadly, you will have to install them yourself. Its not hard to do though.

Basically, here goes:
Do nandroid backup...always!

# adb push newBoot.img /sdcard/newBoot.img
# adb shell
# cat /dev/zero > /dev/mtd/mtd2 (you may get an error here. don't worry about it)
# flash_image boot /sdcard/newBoot.img
# reboot

*Steps courtesy of cteneck's how-to

Then to get wifi working you have to

# adb push wlan.ko /system/lib/modules/wlan.ko

Note: This is for the boot.img in the 2.1 build only. I have not tested it with other ROMs, only the leaked 2.1 by flipzmode

Can't post links, but just remove the space:
t3chi3. net/hero/other/newBoot.img
t3chi3 .net/hero/other/wlan.ko

This worked for me, but please don't yell at me if it doesn't for you...

How did you get into the command prompt? :O

 

[gators0223]

good to hear man

i cant run neocore thought which is a bummer but im sure we will see much much more stuff come out tom. i believe ima crash too. thanks alot to the guy who posted the img file and everybodys work/help tonight.

Interesting. I just downloaded neocore and it worked fine for me. I didn't get as high as maejrep though. Only 23.3 instead of his 29.9. (edit: disabling sound and killing Jbed got me to 27.5!)

 

[gators0223]

How did you get into the command prompt? :O

From your shell you are in currently (either cmd on windows or a linux-type shell), type "adb shell" and you should be good to go assuming you have the android sdk tools directory in your path.

I posted an update.zip a few posts back that is the exact same thing as these instructions just easier. Thats probably the best way to go instead of typing in the commands. Less messy

 

[kniteshift]

Great, just saw it thanks!

 

[5tr4t4]

I just flashed it to AOSP 2.1 and it booted, but there's really no speed improvement that I could tell. Like you said earlier, Gallery is still really slow.

I noticed. I get multi-touch, but the Gallery (and Live wallpapers) are still dog slow for me.

 

[kniteshift]

weird i don't seem to get multi touch to work

 

[gators0223]

weird i don't seem to get multi touch to work

Out of curiosity, what does it say under Kernel version in Settings->About?