I just got my new phone and have rooted it (i did have CM7 on it but im on stock atm again.)
What my problem is whenever i load any custom kernel, wi fi just breaks.
Ill go to wireless settings, click the check box, then it just says 'error'
anyone heard of this?
bringonblink said:
I just got my new phone and have rooted it (i did have CM7 on it but im on stock atm again.)
What my problem is whenever i load any custom kernel, wi fi just breaks.
Ill go to wireless settings, click the check box, then it just says 'error'
anyone heard of this?
Click to expand...
Click to collapse
When you load the kernel are you flashing the zimage manually or using a packaged update.zip that includes the wifi module for that kernel?
all im doing is using flashboot to flash the .img.
no idea how to flash it properly, could use your help
bringonblink said:
all im doing is using flashboot to flash the .img.
no idea how to flash it properly, could use your help
Click to expand...
Click to collapse
Are you building the kernel and boot image yourself or pulling them from somewhere?
I just downloaded netarchys 1.2.4 cfs, and extracted the .img and fastbooted it onto the phone.
What i think you're saying is that this is not the correct method to flash the kernel because the other folders are not being put on to the phone (hence broken wi fi)
If thats the case just need help to flash the kernel properly
bringonblink said:
I just downloaded netarchys 1.2.4 cfs, and extracted the .img and fastbooted it onto the phone.
What i think you're saying is that this is not the correct method to flash the kernel because the other folders are not being put on to the phone (hence broken wi fi)
If thats the case just need help to flash the kernel properly
Click to expand...
Click to collapse
Ah, indeed
So, that zip is meant to be applied via a custom recovery (CWM). It will flash not only the boot image, but also copy the newly build kernel modules, create a custom /etc/init.d and install busybox.
By flashing just the boot image you are missing the rebuilt modules and the custom init.d (which mounts /data with noauto_da_alloc, etc and sets windowsmgr.max_events_per_sec=72 for better scolling performance. As a result of not having the rebuilt kernel modules when the network module tries to load (bcm4329.ko) the version number won't match the kernel and it will fail to load. If you check dmesg you'll see it complaining
Flash this via a custom recovery and you should be fine (just place the entire zip on your device and then chose it from CWM).
right, thanks that clears that up.
however, i have another problem now!
Basically i flashed the netarchy kernel, realized i had no wifi, did a factory reset thinking ill get back to stock, however im stuck with this netarchy kernel AND ive lost CWM.
3G is being a pain and not downloading properly etc.
Is there any way for me to reset and just flash CM7 and Netarchy 1.2.4
im outta ideas :/ thanks for the help!
bringonblink said:
right, thanks that clears that up.
however, i have another problem now!
Basically i flashed the netarchy kernel, realized i had no wifi, did a factory reset thinking ill get back to stock, however im stuck with this netarchy kernel AND ive lost CWM.
3G is being a pain and not downloading properly etc.
Is there any way for me to reset and just flash CM7 and Netarchy 1.2.4
im outta ideas :/ thanks for the help!
Click to expand...
Click to collapse
When you reboot on a stock rom there is a script that checks recovery and if it is not stock it will reflash the stock recovery. This is an easy fix though. If you want to stay on stock you can flash CWM through fastboot, flash the SU binary and then rename/delete the script (/etc/install-recovery.sh or something like that).
If you want to just flash CM7 then just download the full zip and place it on the phone. Flash CWM through fastboot, boot into recovery and flash CM7 as desired (RC or nightlies). Then go ahead and apply the appropriate netarchy kernel - there's a separate version for CM IIRC. Make sure you do a full wipe before you flash CM7.
Ok so im downloading rom manager onto my phone, downloading CM7 on pc, then will transfer to phone (whole zip right?) then i just reboot in recovery, wipe and flash CM7, and THEN start on the kernel lol
Ok thanks ill keep ya updated really appreciate it
edit
Thanks a lot booted and rooted running CM7 and Netarchy
Related
I want to overclock the NS without having to replace the rom. Would this be possible? Are there additional risk associated with overclocking without replacing the ROM?
Thanks in advance!
Yes you can. All you need is root and clockwork recovery. Then download Netarchy's kernel. I know for sure that his kernel works on stock rom since he said so himself. I don't know about Trinity kernel though.
I run stock and I've tried both the trinity stock kernel and netarchy cfs kernel OC @ 1.2ghz. Personally I've had better results on the netarchy kernel.
Sent from my Nexus S
Can I put the stock kernel if I don't like the netarchy kernel? Because I use Bluetooth and wifi always and i just wanted to get a little bit more of my NS!
Make a nandroid backup of the stock rom then flash the kernel. I use netarchy every day and am usually on wifi with my bt earpiece in.
Sent from my Darkginger CM7 Google Nexus S!
I'm having a hard time finding how to flash the kernel (found a lot about how to flash the ROM though).
Would someone link me a FAQ or list some quick instructions on how to go about it?
I have ROM manager installed already (woot!)
Thanks again!
catchsomezz said:
I'm having a hard time finding how to flash the kernel (found a lot about how to flash the ROM though).
Would someone link me a FAQ or list some quick instructions on how to go about it?
I have ROM manager installed already (woot!)
Thanks again!
Click to expand...
Click to collapse
same thing as flashing a ROM.
just make sure if you're flashing a kernel over stock.. make sure its the kernel built for the "stock" rom and not a kernel for CM7 or Bionix etc
catchsomezz said:
I'm having a hard time finding how to flash the kernel (found a lot about how to flash the ROM though).
Would someone link me a FAQ or list some quick instructions on how to go about it?
I have ROM manager installed already (woot!)
Thanks again!
Click to expand...
Click to collapse
Assuming the kernel you want is clockwork compatible, put the zip file of it in your sdcard.
Boot to clockwork recovery either via ROM Mgr (if you're rooted) or via fastboot if you're not.
In Clockwork, find the menu option to install a update/file/zip from sdcard. Select that option, then navigate with the volume keys to the zip file for the kernel. Select it by pushing the power button. Select and answer yes for the are you sure warning. Wait for it to give you a update applied successfully message.
Navigate up to where you can select reboot, and reboot.
You should be on your new kernel.
I WOULD ALWAYS RUN A NAND BACKUP FROM CLOCKWORK BEFORE MESSING WITH THIS STUFF. And ideally, I would keep a copy of that backup on my laptop or dropbox account, not just my sdcard on the phone.
Thanks for all your (very quick) help!
I'm currently running Netarchy's 1.2.2 BFS @ 1.3 and it definitely feels a big snappier with loading some programs
I put today the netarchy kernel 1.2.2 and i have one question...
Where is the VooDoo Improvements? I didn't find the application!
For me the kernel is stable and wifi works even when bluetooth is disabled!
Hi guys,
I'd like to downgrade from Android 3.2 (build HTJ85B) to Android 3.0.1 (build HWI69), since this was the last version that allowed me to flash a new kernel without getting stuck at the Motorola logo. The Xoom is rooted, using the rootboot.img floating around here. Is it just a matter of flashing the stock boot, system, recovery, and userdata images back onto the Xoom? Or is there more to it than that? This will effectively unroot the phone too, correct, since it will be wiped clean? Thanks in advance for any help!
mattberman said:
Hi guys,
I'd like to downgrade from Android 3.2 (build HTJ85B) to Android 3.0.1 (build HWI69), since this was the last version that allowed me to flash a new kernel without getting stuck at the Motorola logo. The Xoom is rooted, using the rootboot.img floating around here. Is it just a matter of flashing the stock boot, system, recovery, and userdata images back onto the Xoom? Or is there more to it than that? This will effectively unroot the phone too, correct, since it will be wiped clean? Thanks in advance for any help!
Click to expand...
Click to collapse
Look, there's obviously something else going on with your Xoom that is not related to the Honeycomb version you have updated to. My suggestion is to very logically figure out what may have happened to get you stuck so we can get you unstuck.
Of course, if you go to the Moto Dev site you can download the stock images for your Xoom model (be careful to choose the correct model) and flash them through fastboot.
Don't relock.
You can reroot at HC3.01 or you can OTA update to 3.1/3.2 as desired and then root.
It's all up to you.
I know there's something else wrong, but for the life of me I cannot figure out what it is. I've tried different kernels (stock, Tiamat, different branches of each), but whenever I try to build and flash a new kernel, I get stuck at the Motorola logo, and have to reboot and reflash the older rootboot.img from these forums. I tried different mkbootimg offsets (it should be 0xe19f8000 for the Xoom I believe, correct?) and different ramdisks, but still the same problem. Unless there is some other special step I missed for building Xoom kernels, I'm out of ideas, and I know I had better luck building and flashing kernels on Android 3.0.1, so this is sort of my final fallback method.
These are the steps I took to get where I am:
1. Upgrade Android 3.2 OTA (build HTJ85B) for US WiFi Xoom (which is my model)
2. Unlock Xoom via fastboot
3. Copy su files over for root access
4. Build 2.6.36.3 kernel from source tree (many different branches, etc like mentioned above)
5. Extract ramdisk and combine with zImage kernel output using mkbootimg (tried both no offset and offset=0xe19f8000, which I found after digging around on the Xoom)
6. Flash new boot image via fastboot and reboot. This is when I get stuck a Motorola logo..
Any advice?
mattberman said:
I know there's something else wrong, but for the life of me I cannot figure out what it is. I've tried different kernels (stock, Tiamat, different branches of each), but whenever I try to build and flash a new kernel, I get stuck at the Motorola logo, and have to reboot and reflash the older rootboot.img from these forums. I tried different mkbootimg offsets (it should be 0xe19f8000 for the Xoom I believe, correct?) and different ramdisks, but still the same problem. Unless there is some other special step I missed for building Xoom kernels, I'm out of ideas, and I know I had better luck building and flashing kernels on Android 3.0.1, so this is sort of my final fallback method.
These are the steps I took to get where I am:
1. Upgrade Android 3.2 OTA (build HTJ85B) for US WiFi Xoom (which is my model)
2. Unlock Xoom via fastboot
3. Copy su files over for root access
4. Build 2.6.36.3 kernel from source tree (many different branches, etc like mentioned above)
5. Extract ramdisk and combine with zImage kernel output using mkbootimg (tried both no offset and offset=0xe19f8000, which I found after digging around on the Xoom)
6. Flash new boot image via fastboot and reboot. This is when I get stuck a Motorola logo..
Any advice?
Click to expand...
Click to collapse
Quick question: are you using CWM Recovery to flash the zip files, and if so what version of recovery do you have installed?
The version which works best for the Xoom is v3.2.0.0 R4c. However if you "updated" through Rom Manager to v4.0.0.X, that version is incompatible with the external sdcard and if you are trying to flash from your internal sdcard, it will seem like it's working but will not work, will just hang or revert to previous state. So maybe I'm really off base...you seem to know a lot...but I've seen similar problems caused by that bad recovery version.
I'm not using CWM at all, since I still don't have an SD card to use (I'm waiting on an order from a few weeks back). So that is probably not the issue. I hope to test using CWM after my card arrives, maybe that will fix the issue, but I doubt it.
Edit: Also, just to clarify, I'm not flashing any zip files, just the boot image .img files.
mattberman said:
I'm not using CWM at all, since I still don't have an SD card to use (I'm waiting on an order from a few weeks back). So that is probably not the issue. I hope to test using CWM after my card arrives, maybe that will fix the issue, but I doubt it.
Edit: Also, just to clarify, I'm not flashing any zip files, just the boot image .img files.
Click to expand...
Click to collapse
So you are decomposing the zip files and flashing image files through fastboot? Because you know you can't flash zip files through fastboot.
mattberman said:
Hi guys,
I'd like to downgrade from Android 3.2 (build HTJ85B) to Android 3.0.1 (build HWI69), since this was the last version that allowed me to flash a new kernel without getting stuck at the Motorola logo. The Xoom is rooted, using the rootboot.img floating around here. Is it just a matter of flashing the stock boot, system, recovery, and userdata images back onto the Xoom? Or is there more to it than that? This will effectively unroot the phone too, correct, since it will be wiped clean? Thanks in advance for any help!
Click to expand...
Click to collapse
Worst logic EVAR
mattberman said:
I'm not using CWM at all, since I still don't have an SD card to use (I'm waiting on an order from a few weeks back). So that is probably not the issue. I hope to test using CWM after my card arrives, maybe that will fix the issue, but I doubt it.
Edit: Also, just to clarify, I'm not flashing any zip files, just the boot image .img files.
Click to expand...
Click to collapse
Annnnd here is the problem....flash in a custom image would be a good start to fixing ur trouble. Search solarnz custom clockwork recovery image and flash through fastboot
rockhumper said:
Annnnd here is the problem....flash in a custom image would be a good start to fixing ur trouble. Search solarnz custom clockwork recovery image and flash through fastboot
Click to expand...
Click to collapse
He doesn't have his microsd card yet. But might as well get ready.
okantomi said:
So you are decomposing the zip files and flashing image files through fastboot? Because you know you can't flash zip files through fastboot.
Click to expand...
Click to collapse
Sorry if I was unclear, I am not using any zip files anywhere in the flashing process, except when dealing with the ramdisk. I've done this many times before with other devices, I'm not completely new to the process.
rockhumper said:
Worst logic EVAR
Click to expand...
Click to collapse
How is that bad logic? If something isn't working as it should, go back to the last stable point when it did.
rockhumper said:
Annnnd here is the problem....flash in a custom image would be a good start to fixing ur trouble. Search solarnz custom clockwork recovery image and flash through fastboot
Click to expand...
Click to collapse
I could try this but how would that help? Do I need a custom recovery image to flash a new kernel? It won't work with stock? I'll give it a shot, thanks for the input. Okantomi, he's talking about the recovery .img file (flashed via fastboot), and not the .zip via CWM (I think).
Just get a 2gb or 4gb sd card, or borrow one from a phone, it's pretty simple...
To go back just grab the stock images from my sticky. Fastboot flash them, wipe cache and start over.
Sent from my PG86100 using Tapatalk
Hi All
Finally plucked up the courage to register and ask a question after lurking for the good part of 2 years.
I've an i9020A and have flashed CyanogenMod 9 v4.0.3 v1.0 which is great, however I wanted to try Steve Garon's kernel which just wont take.
I reboot into Recovery, wipe Dalvik Cache a couple of times, install Steve's kernel which apparently flashes no problem.
I reboot and get the optimising Android applications screen then check my kernel under settings.
It is still the original KalimochoAz kernel and I cannot turn on my wireless.
Now this has happened previously when trying to also update my kernel under CDTDroid's AndroidMe 1.2 which I could only fix by restoring back to 1.1.
Any idea on what may be wrong here guys?
Appreciation in advance.
Lally
Have you tried just flashing again? A bad flash often results in wifi not working and may be the cause of the about page showing the old kernel. Remember to wipe dalvik cache again, too.
Thanks for the reply Harbb, do you mean a re flash of the Kernel or ROM? If Kernel then yeah I have done, same scenario. I'll also try a re download of the Kernel to see if that improves anything but this is much akin to me trying to update from Speedy3 to Speedy4 under AndroidMe 1.2 which was unsuccessful.
Just the kernel, as you've already tried. Just remember to do a NANDroid backup (CWM --> backup & restore --> backup) when you have a stable, working ROM. Can save you alot of trouble if you don't have a relatively recent one.
Also, are you using CWM 5.0.2.0? And could it be that your phone isn't particularly happy about the 1100mhz OC with Steve Garon's kernel?
I'd suggest updating CWM recovery to the latest version.
Sent from my Nexus S using xda premium
Cheers for the help guys.
Yes, using 5.0.2.0, but something is not right cause I just tried to flash CWR again from within Rom Manager (4.8.1.3) and it gets to around 95% and the app gives 'Rom Manager is not responding.
Looks like I'll have to try a complete wipe and reflash.
Will report back the results.
Forget rom manager all together.
Download the recovery you want to use.
Flash it via fastboot
flash kernel.
I'd do what albundy said - flash a new recovery through fastboot and make sure the bootloader is unlocked (vol. up + power --> bootloader: unlocked)
Ok, downloaded CM9 1.1, redownloaded Steves kernel, reinstalled recovery from fastboot.
Wiped and formatted everything twice then installed from scratch.
So far everything is good, still getting errors on Superuser, but installing again via recovery seems to fix that issue.
Cheers chaps.
Good to know Lally, happy you got it sorted out.
Cheers Harbb, the test will be when I want to change the kernel again I suppose, one complete wipe and install a day is enough
Hi,
I have managed to put on a kernel that's not working. Is there a way to revert back to the original kernel? I do have a nandroid backup, but re-installing that didn't put on the old kernel.
I am using Liquidsmooth ROM. Any help would be appreciated.
Thanks.
if you can boot into the rom use flashimagegui, if not do the normal fastboot the boot.img then do it again with flashimagegui to get the modules.
what kernel did you try to flash? the only kernel that will work with new liquidsmooth is cm10.1_vz-oc-linaro.3.zip. it contains modules, if you aren't s-off then you need to flash boot.img in fastboot then flash again in recovery for the modules.
DvineLord said:
if you can boot into the rom use flashimagegui, if not do the normal fastboot the boot.img then do it again with flashimagegui to get the modules.
what kernel did you try to flash? the only kernel that will work with new liquidsmooth is cm10.1_vz-oc-linaro.3.zip. it contains modules, if you aren't s-off then you need to flash boot.img in fastboot then flash again in recovery for the modules.
Click to expand...
Click to collapse
I did exactly that, presuming that it was working... But I have been facing issues. The phone restarts every once in a while and I have managed to get to this condition after multiple wipes and restoring a backup. Anyways I don't know what the issue is I was just wondering how to revert back to the original kernel.
im running Liquid-JB-v2.1-RC2-evita.zip and cm10.1_vz-oc-linaro.3.zip. there seem to be some general issues with the rom that present as basically glitching and gets worse overtime atleast for me. im pretty sure it isnt related to the kernel. but to revert kernel just load the liquidsmooth zip into flashimagegui and itll pull the needed files, let it wipe cache and dalvik then reboot.
DvineLord said:
im running Liquid-JB-v2.1-RC2-evita.zip and cm10.1_vz-oc-linaro.3.zip. there seem to be some general issues with the rom that present as basically glitching and gets worse overtime atleast for me. im pretty sure it isnt related to the kernel. but to revert kernel just load the liquidsmooth zip into flashimagegui and itll pull the needed files, let it wipe cache and dalvik then reboot.
Click to expand...
Click to collapse
I do not have s-off does the flashimagegui works even without it?
strommer666 said:
I do not have s-off does the flashimagegui works even without it?
Click to expand...
Click to collapse
yes, Flash Image GUI
you should also s-off your phone it will make life ALOT easier and the process is simple take like 2 minutes.
DvineLord said:
yes, Flash Image GUI
you should also s-off your phone it will make life ALOT easier and the process is simple take like 2 minutes.
Click to expand...
Click to collapse
Thanks I'll make sure I do that..
also new stable build of liquidsmooth just got released. you should flash it. imma flash it with a clean full wipe. but you should s-off first so you dont have to flash boot.img separately every rom.
DvineLord said:
also new stable build of liquidsmooth just got released. you should flash it. imma flash it with a clean full wipe. but you should s-off first so you dont have to flash boot.img separately every rom.
Click to expand...
Click to collapse
Ya, I saw the new version wanted to try that which is why I wanted to got to the old kernel version. I had tried installing it with the linaro kernel but it gets stuck on the boot screen.
Update: - I installed the flash gui image, then extracted and installed the kernel , factory reset the phone, then installed the latest liquid smooth build. But it is still not going ahead of the boot animation.
Update 3 :- Got the old kernel back. Did a restore. Working fine now . But still for some reason I cannot install the new ROM yet.
strommer666 said:
Ya, I saw the new version wanted to try that which is why I wanted to got to the old kernel version. I had tried installing it with the linaro kernel but it gets stuck on the boot screen.
Update: - I installed the flash gui image, then extracted and installed the kernel , factory reset the phone, then installed the latest liquid smooth build. But it is still not going ahead of the boot animation.
Update 3 :- Got the old kernel back. Did a restore. Working fine now . But still for some reason I cannot install the new ROM yet.
Click to expand...
Click to collapse
you need everything. you don't need to extract the kernel. just load the whole zip file.
DvineLord said:
you need everything. you don't need to extract the kernel. just load the whole zip file.
Click to expand...
Click to collapse
I did load the full file and the flash gui image extracted the kernel. The thing is I have the kernel now, but still I can't seem to be able to install the new version of the LiquidSmooth build. I am doing a nandroid backup of this thing and try installing it again.
well new liquidsmooth is nice, im using cwm now as recovery since ive had tons of issues with twrp since version 2.2.2.0
hi,
so as i can not post in the android development subforum i'll have to try it here..
I have: HOS with TWRP 2.4.4.0 (goo manager) with HBOOT 2.15 (S-ON) running PAC-man ROM 22.1 (the newest update)
also i have bubba v4 installed and everything was working really perfectly. (s2w and some kernel tuner settings)
yesterday i played a bit with UI settings, nothing that i thought would stop my device from booting..
today i woke up, the battery was empty so i plugged in, turned on and left, after a while i came back and it was still at the boot
animation (PAC is loading...).
now i have tried to reflash bubba, PAC (cache+dalvik wipe) and the boot.img via fastboot. still it is stuck on that loading screen.
now i'd really like to use this rom with the bubba kernel.
any clues how i could get it out of this boot cycle?
thanks
-t.
2.4.4.0 is kinda crap in certain things. Flashing roms is one of them. Please use 2.3.3.0 as this will work.
why do you think that twrp version is the problem?
flashing this rom with 2.4.4 has worked well, so flashing over the same ROM with it shouldn't be problem...?
when flashing or wiping everything seems to work normally.
also, i am not sure how to downgrade twrp!?
best,
-t.
edit: okay i found out, fastboot flash recovery .. should work. i'll let you know if it works afterwards *fingers crossed*
edit2: reflashing the ROM it takes much longer (maybe thats good?) i just hope it finishes at some point...
edit3: okay, so re-flashing with twrp 2.3.3.0 did'nt work either, it is still stuck at the "PAC loading..." stage
(yes, i flashed the boot.img too)
any more clues?
finally i had this phone set up just the way i wanted, it was perfect and then this. why couldn't it just keep working
makes me sad, i want to use my phone damnit
okay, so i flashed and wiped and flashed and wiped a few times, system, cache, dalvik whatever, suddenly it started working... i also flashed some different kernels (as i thought some bubba stuff might still be there)
soo IDK what it was but now it works again, thank god..
maybe its worth mentioning that i flashed an older PAC rom (v22.0.1_20130324-230044) though i am not sure if that was the problem...
Sorry, I was off for some time from this forum.
If your bootloader version is > 1.09 you'll have to flash the kernel separately due to some restrictions in the higher bootloader versions.
If e.g. you flashed boot.img only from the 'bubba.zip' you're missing some of the modules needed for working coming with that flashable zip. Just have a look inside the zip file and you'll see some different content besides the boot.img. So you need to flash the complete zip file (to get the modules) and separately again the boot.img (to get the kernel itself).
The point about 2.4.4.0 / 2.5.0.0 is, that some installer scripts for some roms don't work as they should.
:good:
Hey,
Thanks, yeah but the thing is I installed Bubba right I think. Even manually copying the modules and setting the permissions...
and it has been working. Does the system lose modules when the permissions are not exactly right? I remember leaving the exec permission on for the modules because I was lazy
Well nevermind I guess I learned something from this little action that cost me most of my precious Saturday...
Also I now tried flashing twisted 3 and bulletproof kernel neither of them worked for pac rom, maybe someone could explain to me which kernel works for which rom? I thought they are completely interchangeable as long as they are compatible to the hardware..
And how do boot images work? I thought if you flash a boot image it overrides the old one, but flashing a Rom and then only installing a boot image from some kernel doesn't end with booting the rom (that's how I tried to repair it in the first place )
Well, appreciate the help.
Best,
#t.
Sent from my One S using xda app-developers app harhar
Bulletproof is for sense
HTC_One_S | S-OFF | ViperOneS_2.2.0 | Black-Blue_Sense_Theme | ElementalX_4.2
Aha okay, I thought sense is like any app running ontop of any kernel...alright.
Sent from my One S using xda app-developers app
tehtomi said:
Hey,
Thanks, yeah but the thing is I installed Bubba right I think. Even manually copying the modules and setting the permissions...
and it has been working. Does the system lose modules when the permissions are not exactly right? I remember leaving the exec permission on for the modules because I was lazy
Click to expand...
Click to collapse
Usually the installer script should set the right permissions already. Nah, modules shouldn't go lost this way ( system/lib/modules/*.ko).
tehtomi said:
And how do boot images work? I thought if you flash a boot image it overrides the old one, but flashing a Rom and then only installing a boot image from some kernel doesn't end with booting the rom (that's how I tried to repair it in the first place )
Click to expand...
Click to collapse
In short: boot.img = kernel
It's stored in an own partition (block) on the phone, That's why you have to use 'fastboot flash boot boot.img'. Same for radio: 'fastboot flash radio radio.img' and so on. The bootloader will load them first from this block. But search Google if you'd like to know more. lol
Usually there is a boot.img file in any rom.zip that can be extracted and flashed also it's supposed to be flashed with the rest of rom.zip in one go. Blame htc for their bootloaders which prevent you from this. That's why we talk about htc's half assed bootloader unlock.
To come to an end: There are sense based roms, AOSP and AOKP based roms. Whereas AOSP and AOKP based kernels could be interchangeable, sense based kernels are only compatible to htcs sense UI. That's why you can't mix them up with all the roms out there. Sense is deeply integrated into kernel.