Kernels and boot.img - HTC Sensation

Is it ok to flash a different boot.img from another kernel. Let's say im running sebastian, is it ok to flash boot.img from faux? My wifi is still not turning on and im really desperate.

Yes, but typically the kernels will unpack the boot.img and repack it with their kernel while keeping the ramdisk intact. They will also flash their own matching drivers so as not to break wifi/BT.

Related

Working kernel based on toast's source?

Has anybody on here been able to compile/boot their own evo kernel? I have been able to
compile a kernel just fine but given the limitations of fastboot on our spl i cannot test the
image using "fastboot flash zimage zImage". I have tried packing the kernel into a boot
image then signing and flashing rom. This got me stuck at the 1st boot screen. I have also
tried to unpack and repack the stock boot image without making any edits and that fails at
the first boot screen as well. So I believe there is definately something different to the
procedure of flashing or creating boot images.
So does anybody have any advice? maybe a fix? If anyone is able to boot a custom kernel please send me a pm!
haven't had a chance to test out the kernel ... i know in flipz supersonic .6 rooted ROM a kernel is flashed in the update.zip file. not sure what kernel this is since the OTA update from .1 to .6 the boot.img didnt change, md5sum the same. i didnt compare the md5sum of the boot.img hes using to the RUU boot.img .
i know the froyo ROM on here flashes a boot.img, which i think remember reading was compiled from toast's kernel source. i'd imagine mainly with a modified init.rc ...
hope that helps a bit and gives you some motivation its possible although the two examples i've given are from toast and flipz who both appear to be ahead of the curve!
once the htc kernel source hits i plan on kernel compiling ...

flash boot.img

im running miui and would like to use the newest cm7 kernel. how do i flash the boot.img to my phone without replacing the boot.img in mui rom and reflashing the rom?
speedfreak228 said:
im running miui and would like to use the newest cm7 kernel. how do i flash the boot.img to my phone without replacing the boot.img in mui rom and reflashing the rom?
Click to expand...
Click to collapse
i'm not sure those two are compatible...
but if you want to give it a shot, heimdall the kernel.
i had no success doing this, and cant seem to OC the Miui Kernel past 1.4 stably - so post here if you get it going Speed....
speedfreak228 said:
im running miui and would like to use the newest cm7 kernel. how do i flash the boot.img to my phone without replacing the boot.img in mui rom and reflashing the rom?
Click to expand...
Click to collapse
which MIUI ROM are you running? can you share it? im interest in MIUI, but can't fine a ROM.....
speedfreak228 said:
im running miui and would like to use the newest cm7 kernel. how do i flash the boot.img to my phone without replacing the boot.img in mui rom and reflashing the rom?
Click to expand...
Click to collapse
You can heimdall it just like you can heimdall the zImage for kernels for Samsung-derived ROMs. Not sure if you can use SGS Kernel Flasher - haven't tried that.
When the phone is in download mode:
Code:
heimdall flash --kernel boot.img
I can't help you as far as Heimdall installations in Windows - I'm a Linux user.
Kernel Flasher Did Not work.......Bootlooped my phone in a never ending Voodoo lagfix install boot up.

[Q] Regarding flashing boot.img between 2 ROMs.

Hello, my device is currently running LeeDroid's ROM and I was looking to test out other ROMs for fun. One example is TrickDroid. I noticed that each thread provides a boot.img to be flashed in fastboot. Must I do that before flashing each ROM and after backing up and wiping? Thank you!
If both ROMs are on the same base then no, you shouldnt have to flash each time..
Newer bases require newer boot.imgs,
The worst thing that could happen is the ROM wont boot, To fix that, Just flash the boot.img
I would love to thank you but I reached my max Thanks for today. I will come back tomorrow
If you get a bootlop, you should erase the cache or just flash the boot.img as said above

Do I have to flash the boot img file every time I flash a rom?

Just as the title states...Do anyone know if you have to flash the boot.img file separately every time I flash a custom rom or is it with certain roms only?
plmiller0905 said:
Just as the title states...Do anyone know if you have to flash the boot.img file separately every time I flash a custom rom or is it with certain roms only?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1954060
http://forum.xda-developers.com/showthread.php?t=1955303
plmiller0905 said:
Just as the title states...Do anyone know if you have to flash the boot.img file separately every time I flash a custom rom or is it with certain roms only?
Click to expand...
Click to collapse
as mentioned in other threads.. if you are flashing similar ROMs ( having same kernel ).. there is no need to flash boot.img separately. But say if you wanna switch from sense to aosp you must do that as they have different kernels.
Again if you are just upgrading from older version to newer version of same ROM and if there are no kernel changes no need to flash it
To clarify, flashing the boot image from fastboot is only necessary if you are on hboot 1.14 b(coming from AT&T firmware 2.20). Previous hboot versions, the kernel is flashed automatically when you flash the ROM.

[Q] switch between custom kernels

Hi. ATM I use elemental x and I've read to switch to another kernel I have to reflash the whole ROM. what's the problem with just flashing the boot.img to get back to stock kernel and then flash another custom kernel?
maroc84 said:
Hi. ATM I use elemental x and I've read to switch to another kernel I have to reflash the whole ROM. what's the problem with just flashing the boot.img to get back to stock kernel and then flash another custom kernel?
Click to expand...
Click to collapse
nothing, it should work fine
Sent from my Nexus 5 using XDA Free mobile app
maroc84 said:
Hi. ATM I use elemental x and I've read to switch to another kernel I have to reflash the whole ROM. what's the problem with just flashing the boot.img to get back to stock kernel and then flash another custom kernel?
Click to expand...
Click to collapse
As jd1639 said... Yes, flashing the stock boot.img should be just fine.
Probably easier though, you can also just dirty flash the ROM that your currently running on your N5 without wiping anything and then while still in recovery, just flash the custom kernel that you want to switch too and done.
maroc84 said:
Hi. ATM I use elemental x and I've read to switch to another kernel I have to reflash the whole ROM. what's the problem with just flashing the boot.img to get back to stock kernel and then flash another custom kernel?
Click to expand...
Click to collapse
As far as I know, just flashing the stock boot.img is usually fine, but if you take a look at franco's thread, the process to uninstall includes flashing system.img as well, since a couple of system files are modified. I don't think elementalx does though, so what you suggested will work ok.
simonarturo said:
As far as I know, just flashing the stock boot.img is usually fine, but if you take a look at franco's thread, the process to uninstall includes flashing system.img as well, since a couple of system files are modified. I don't think elementalx does though, so what you suggested will work ok.
Click to expand...
Click to collapse
Very true... Some kernels do modify the system and that's why I find it easier to just dirty flash the ROM that I'm currently using, since it wipes the system partition and then you don't run into issues.
Thank you.
So I'll better dirty flash to avoid unnecessary problems with a new kernel.
All user data should be save with a dirty flash, am I right?
maroc84 said:
Thank you.
So I'll better dirty flash to avoid unnecessary problems with a new kernel.
All user data should be save with a dirty flash, am I right?
Click to expand...
Click to collapse
Yeap.. Nothing will be erased.
What about if I am on stock? Should flashing the flash-base.sh (from factory image) have the same effect like a dirty flash of a custom recovery with a zip of a custom Rom? So all use data be save.
maroc84 said:
What about if I am on stock? Should flashing the flash-base.sh (from factory image) have the same effect like a dirty flash of a custom recovery with a zip of a custom Rom? So all use data be save.
Click to expand...
Click to collapse
If you mean the flash-all.bat, it will erase all data! Just flash the /system and /boot images and then flash the custom kernel..
Or, you can dirty flash the stock 4.4.4 rom and then flash the custom kernel.
Edit: no. I mean the batch as I named it. It's not flash-all. But I think it only flashes radio and bootloader.
Side fact: *.bat = Windows DOS and *.sh = Linux shell
maroc84 said:
Edit: no. I mean the batch as I named it. It's not flash-all. But I think it only flashes radio and bootloader.
Side fact: *.bat = Windows DOS and *.sh = Linux shell
Click to expand...
Click to collapse
No need to flash radio as well. Flashing boot.img and system.img will do the job is you're on stock and you're guaranteed to not lose your data. I think that will only happen if you flash userdata.img
Just flash the rooted stock zip ROM.
Sent from my Nexus 5 using Tapatalk

Categories

Resources