From what I understand, and please correct me if I'm wrong, but boot.img is your kernel correct?
Is there a way to get the boot.img off my present device and use it with other ROMS, like flash one through CWM and flash a custom boot.img through fastboot? Also, are all CDMA kernels compatible with CDMA ROMs? Like, could I use a CM7 kernel with a CM9 ROM and have it work properly (or as well as it does on CM7?)
kalaker said:
From what I understand, and please correct me if I'm wrong, but boot.img is your kernel correct?
Is there a way to get the boot.img off my present device and use it with other ROMS, like flash one through CWM and flash a custom boot.img through fastboot? Also, are all CDMA kernels compatible with CDMA ROMs? Like, could I use a CM7 kernel with a CM9 ROM and have it work properly (or as well as it does on CM7?)
Click to expand...
Click to collapse
you can flash directly the kernal.zip no need to flash the whole boot.img (we have kernal in zip files given by the devs GSM) but if you need you can backup your current thing in cwm (you will have your boot.img there ) and then flash a new boot.img from fastboot
Code:
fastboot flash boot boot.img
and if it isnt working you can copy the old boot.img from /sdcard/clockworkmod/backup/(the folder in which the backup is taken the name is mostly the date )2012-03-22-12-45/boot.img
and everything will be normal.. its never a bad thing to do trial and eroor and revert back to normal
---------- Post added at 12:47 PM ---------- Previous post was at 12:46 PM ----------
kalaker said:
From what I understand, and please correct me if I'm wrong, but boot.img is your kernel correct?
Is there a way to get the boot.img off my present device and use it with other ROMS, like flash one through CWM and flash a custom boot.img through fastboot? Also, are all CDMA kernels compatible with CDMA ROMs? Like, could I use a CM7 kernel with a CM9 ROM and have it work properly (or as well as it does on CM7?)
Click to expand...
Click to collapse
you can check this out http://forum.xda-developers.com/showthread.php?t=1556983
Related
So I flashed few custom ROMs in a past few days. But every custom ROM requires me to flash boot.img. if I don't flash boot.img, my wifi will error or in other case, my phone won't even boot into homescreen.
I don't mind to do so (flashing boot.img after flash new custom ROM), but is there anyway to switch between custom ROMs without flashing boot.img? Is it caused by my device is S-ON? Cus my previous phone didn't require me to flash boot.img. I tried to backup two custom ROMs and restore in in CWM but I still need to flash boot.img. why can't I just backup 3 custom ROMs in CWM and restore it anytime as I want wothout flash boot.img?
Thanks
"Better late than never, but never late is better"
-Drake
yes unless the rom creator told not to fo that
i. don't think anyone will ever say that
dont just say thanks hit thanks if i helped
a true lfc supporter
and a former symbian lover
sent from my awesome HTC One V running rc 2.0 by CKPV5 -using xda premium
SUPPORT THE SOFTWARE DEVELOPER'S IF YOU LIKE THE GAME / APP BUY IT
JalmiNyondong1933 said:
So I flashed few custom ROMs in a past few days. But every custom ROM requires me to flash boot.img. if I don't flash boot.img, my wifi will error or in other case, my phone won't even boot into homescreen.
I don't mind to do so (flashing boot.img after flash new custom ROM), but is there anyway to switch between custom ROMs without flashing boot.img? Is it caused by my device is S-ON? Cus my previous phone didn't require me to flash boot.img. I tried to backup two custom ROMs and restore in in CWM but I still need to flash boot.img. why can't I just backup 3 custom ROMs in CWM and restore it anytime as I want wothout flash boot.img?
Thanks
"Better late than never, but never late is better"
-Drake
Click to expand...
Click to collapse
Ya.. because of s-on, the kernel cannot be installed during the ROM installation. You can switch between ROMs without flashing boot.img only when those custom ROMs are using a stock kernel.
ckpv5 said:
Ya.. because of s-on, the kernel cannot be installed during the ROM installation. You can switch between ROMs without flashing boot.img only when those custom ROMs are using a stock kernel.
Click to expand...
Click to collapse
Oh. I see. This is really depressing. I really like your ROM but also love Modaco Vanilla ICS ROM. Is there any way to use stock kernel on both ROM? (Just for my personal use, not for published)
Sent from my HTC One V using xda premium
Let me tell you a little secret.. hehe...
1. grab yourself 7-zip (http://www.7-zip.org)
2. decide which rom's boot.img that you want to make a default for all your downloaded custom roms (which based on htc ruu).
3. let say you decide MoDaCo's rom boot.img
4. Open the MoDaCo's rom with 7-zip, browse to system/lib/modules; extract the modules folder with its content.
5. For all custom's rom, replace the modules with the one from MoDaCo.
6. You can flash any custom's rom without a need to flash a boot.img provided you already flash the boot.img from MoDaCo's rom earlier.
So only one time flash the boot.img, the next custom rom, you don't need to.(because you already replace the modules). When you make any nandroid backup of a custom rom, restoring the nandroid, you don't need to reflash the boot.img.
So this works for most custom roms that we have in One V Dev forum at the moment (not much of them too), I can say it should be 99% works. Give it a try.
ckpv5 said:
Let me tell you a little secret.. hehe...
1. grab yourself 7-zip (http://www.7-zip.org)
2. decide which rom's boot.img that you want to make a default for all your downloaded custom roms (which based on htc ruu).
3. let say you decide MoDaCo's rom boot.img
4. Open the MoDaCo's rom with 7-zip, browse to system/lib/modules; extract the modules folder with its content.
5. For all custom's rom, replace the modules with the one from MoDaCo.
6. You can flash any custom's rom without a need to flash a boot.img provided you already flash the boot.img from MoDaCo's rom earlier.
So only one time flash the boot.img, the next custom rom, you don't need to.(because you already replace the modules). When you make any nandroid backup of a custom rom, restoring the nandroid, you don't need to reflash the boot.img.
So this works for most custom roms that we have in One V Dev forum at the moment (not much of them too), I can say it should be 99% works. Give it a try.
Click to expand...
Click to collapse
Sure, sounds promising. I'll give it a try. Thanks
EDIT: It works. :good:
Sent from my HTC One V using xda premium
ckpv5 said:
Let me tell you a little secret.. hehe...
1. grab yourself 7-zip (http://www.7-zip.org)
2. decide which rom's boot.img that you want to make a default for all your downloaded custom roms (which based on htc ruu).
3. let say you decide MoDaCo's rom boot.img
4. Open the MoDaCo's rom with 7-zip, browse to system/lib/modules; extract the modules folder with its content.
5. For all custom's rom, replace the modules with the one from MoDaCo.
6. You can flash any custom's rom without a need to flash a boot.img provided you already flash the boot.img from MoDaCo's rom earlier.
So only one time flash the boot.img, the next custom rom, you don't need to.(because you already replace the modules). When you make any nandroid backup of a custom rom, restoring the nandroid, you don't need to reflash the boot.img.
So this works for most custom roms that we have in One V Dev forum at the moment (not much of them too), I can say it should be 99% works. Give it a try.
Click to expand...
Click to collapse
this is awesome secret... :good::good::good::good:
will try it today..... :angel:
thanks for sharing
Hey guys, i am trying to flash a kernel on my phone (bricked kernel) i came from 3 different roms and i always get the same problem. After i flash the rom and enter into it and make sure everything works, I go back to fastboot to flash the boot.img of the kernel and then proceed to flashing the kernel module in revcovery. Everything goes well but once I restart my phone just wont proceed pass the htc logo
I am running hboot verson 1.36 as that is the highest i can go with a CID_044 and running CWM 5.8.4.0 Is there something i should be doing or am doing wrong? Please help and thanks
Are you on a JB rom ? If you are, you can't use those kernels. They are for ICS roms only
Mr.Hofs i right like always but if you are on a ics rom you still need to repack your boot.img. You can do that by using nibble.cc. First step is to take the source boot.img and that can be found in rom.zip and you select it when you are on nibble.cc by clicking on source img. Then you need kernels boot.img and that comes with the kernel download in the kernel.zip. When it is all ready they will upload and repack and you will download repackee boot.img. Hope it helps and good luck
Sent from my HTC One X using xda app-developers app
Haha thanks, and i had a similar case a while back and i adviced him to use the 0.6 or 0.5 bricked kernel because I saw some reports in the bricked thread about not booting. It worked for him.
And are you using the right bricked kernel on the right rom. There is one kernel for the aosp roms and there is one for the sense roms
I don't know if i understand (bad english). With repacked kernel will it work? Same case, CM10, 1.36 hboot and CWM 5.8.4.0.
hey guys thanks for all your help i got it to work on an ICS rom but not on a JB rom which is a real bummer cause i really like the JB roms so i guess i just skip flashing kernels and stick with stock Thank you all for your help i really appreciate it
In fact there are no custom kernels for JB yet at all, HTC has to release the source code for it .... but they haven't done that yet ! Till then stock is all we have
How did you get back to the default kernel after flash bricked kernel?
There are 2 ways to go back to the stock kernel
1 ; flash the boot.img from the rom you are using and flash the modules that can be found in the rom.zip
2 ; flash the boot.img from the rom you are using and reflash the rom without a full wipe ( only cache & dalvik cache )
These methods are the ones i know, maybe there is a tool somwhere ... but i don't use tools
Mr Hofs said:
In fact there are no custom kernels for JB yet at all, HTC has to release the source code for it .... but they haven't done that yet ! Till then stock is all we have
Click to expand...
Click to collapse
I just want to make sure I understand...If I currently have Stock JB running on my HOX I cannot use a custom ROM because the source has not been released? I am asking because Ive gone through all the "standard steps" needed to unlock, root, backup, and flash CM10, but I cannot get past the boot screen.
angrymanhands said:
I just want to make sure I understand...If I currently have Stock JB running on my HOX I cannot use a custom ROM because the source has not been released? I am asking because Ive gone through all the "standard steps" needed to unlock, root, backup, and flash CM10, but I cannot get past the boot screen.
Click to expand...
Click to collapse
No custom kernels are not possible. And i mean by that, that there is no sweep to wake functions or other big tweaks like undervolting. Custom roms are no problem ! And to your not booting question : CM10 on a JB hboot needs a modified kernel !
http://db.tt/uDdWaAtH
You need this one ! Then it will boot
Mr Hofs said:
No custom kernels are not possible. And i mean by that, that there is no sweep to wake functions or other big tweaks like undervolting. Custom roms are no problem ! And to your not booting question : CM10 on a JB hboot needs a modified kernel !
http://db.tt/uDdWaAtH
You need this one ! Then it will boot
Click to expand...
Click to collapse
Wow, thanks! I'll check it out as soon as Dropbox let's me download it. It says your account has too much traffic and to check back later.
Sent from my HTC One X using xda premium
---------- Post added at 06:33 PM ---------- Previous post was at 05:38 PM ----------
also i have another few questions. Is the boot.img you are inking to different than the one packaged with the CN10 rom? If I want to go back to my stock nandroid backup do I need to flash the stock boot.img, or will the restoring of the backup take care of that for me? if i do need the boot.img from the stock rom, how do I get that.
angrymanhands said:
Wow, thanks! I'll check it out as soon as Dropbox let's me download it. It says your account has too much traffic and to check back later.
Sent from my HTC One X using xda premium
---------- Post added at 06:33 PM ---------- Previous post was at 05:38 PM ----------
also i have another few questions. Is the boot.img you are inking to different than the one packaged with the CN10 rom? If I want to go back to my stock nandroid backup do I need to flash the stock boot.img, or will the restoring of the backup take care of that for me? if i do need the boot.img from the stock rom, how do I get that.
Click to expand...
Click to collapse
Yeah I got a mail that my links are suspended !!!
But yes its a different boot.img, and if you want to restore the nandroid backup you also need to flash the boot.img from the nandroid backup ! Its located inside the backup folder
Here it is, the CM10 boot for usage with higher hboot versions.
Thanks everyone. One more question... I see the stock boot image in the backup, but it has a different file extension. Do I have to convert it, or do I just rename it to boot.img? Right now it's named boot.emmc.win
Sent from my HTC One X using xda premium
Just flash it like this:
fastboot flash boot boot.emmc.win
Thank you so much for the info.
Sent from my HTC One X using xda premium
If the nandroid backup is done with CWM the kernel will be named boot.img, and when the nandroid backup is done with TWRP recovery its named like the file you have ! :thumbup:
Awh yeah! It worked! You guys are awesome, thank you for your help!!
Sent from my PG41200 using xda premium
OK, another question. I have s-off, I was under the impression that I would not have to manually flash boot images. So I guess my question is why do I have to manually flash the boot images?
Sent from my PG41200 using xda premium
Newbie here, my Dhd is s-on, ive been flashing and custom rom and kernels to it via cwm and as always i have to flash the boot.img both rom/kernel to fully installed it. Now I want to update my kernel to the newest pacharx release for better battery. but It doesnt have the boot.img which im use to flashing.. when i extract here is what i get:
zImage
unpackbootimg
modclean.sh
mkbootimg.sh
mkbootimg
dd
how do i install this kernel?
i tried flashing the zImage but it doesnt work... please help
You do not extract anything from that zip, just flash it whole from the recovery as you would any boot.img
Sent from my Desire HD using xda app-developers app
ilans93 said:
You do not extract anything from that zip, just flash it whole from the recovery as you would any boot.img
Sent from my Desire HD using xda app-developers app
Click to expand...
Click to collapse
i've already done that but since im on s-on i cant flash the rom via cwm, it needs to be in fastboot... i used to flash kernel with boot.img files on it,but now im just lost with this kernel i want to flash because i cant find the boot.img..
anythingbutipod said:
i've already done that but since im on s-on i cant flash the rom via cwm, it needs to be in fastboot... i used to flash kernel with boot.img files on it,but now im just lost with this kernel i want to flash because i cant find the boot.img..
Click to expand...
Click to collapse
That IS a kernel, not a ROM. Just flash it via fastboot then... You can also do it via ADB if you know how to, if not, use the search bar
ilans93 said:
That IS a kernel, not a ROM. Just flash it via fastboot then... You can also do it via ADB if you know how to, if not, use the search bar
Click to expand...
Click to collapse
I know how to.flash via fastboot and abd, my question is what file should i flash since theres no boot.img file in the kernel... Sorry newbie here
anythingbutipod said:
I know how to.flash via fastboot and abd, my question is what file should i flash since theres no boot.img file in the kernel... Sorry newbie here
Click to expand...
Click to collapse
According what I've read in other posts you can't flash a raw kernel.zip with s-on.
It has also been pointed out that a boot.IMG is Rom specific, so they most likely wouldn't be interchangeable between different roms
Sent from my HTC Desire HD using xda app-developers app
anythingbutipod said:
I know how to.flash via fastboot and abd, my question is what file should i flash since theres no boot.img file in the kernel... Sorry newbie here
Click to expand...
Click to collapse
boot.img is a kernel so don't search for a boot.img in a kernel.zip - it's the same thing only not compressed. ranger4740 is correct. You shouldn't use boot.img from one ROM and put it on another, but that's not what you asked for... As for the fact that you can't flash a kernel.zip with S-ON, I didn't know about that so I can't help you there... Sorry :/ Try asking your question in the kernel thread...
ilans93 said:
boot.img is a kernel so don't search for a boot.img in a kernel.zip - it's the same thing only not compressed. ranger4740 is correct. You shouldn't use boot.img from one ROM and put it on another, but that's not what you asked for... As for the fact that you can't flash a kernel.zip with S-ON, I didn't know about that so I can't help you there... Sorry :/ Try asking your question in the kernel thread...
Click to expand...
Click to collapse
Ok, i also tried to do some research and read some forums, seems my only way to s-off my dhd, which i will be researching next... Thanks:fingers-crossed:
My desired rom has already updated with the kernel that i wanted flash ,so my battery life is now great, although there a bug in battery charging where in it notifies late yet it charges the phone batt. (not that big if a deal for me). Also i created an aroma zip file to install all system update on my phone since the original update flashes the kernel... Thanks for the replies "learn a lot from all those researches i made" :victory:
I started making my ROM with Android Kitchen and I dumped system folder from ftf file.
But I cannot find META-INF and boot.img to use for ROM.
I tried using MIUI v4 META-INF and boot.img but I get status 6 error while installing ROM. By Kitchen's FAQ it means something is up with update-script. So, I need to find stock boot.img for latest ICS Arc S firmware and associated META-INF with update-script.
I searched for those files for more than 8 hours, still can't find them.
I hope if anyone posts them that I could be able to normally install ROM without a problem.
Thank you in forward.
Err, there is no stock boot.img. All stock kernels are provided in the stock firmware packages also known as FTF files.
Depending on what you need it for, you can download the source code(, make the modifications) and compile it yourself.
Hmmm, how am I going to make custom ROM without boot.img if it is needed(or is it?).
I can't get any other custom kernel because I want to make ROM for locked bootloader phone.
Do you know what should I do to complete ROM if i can't have stock boot.img?
A_B_E_D said:
Hmmm, how am I going to make custom ROM without boot.img if it is needed(or is it?).
I can't get any other custom kernel because I want to make ROM for locked bootloader phone.
Do you know what should I do to complete ROM if i can't have stock boot.img?
Click to expand...
Click to collapse
For roms built on stock Rom, u shouldnt have any kernel inside the flashable zip
Sent from my LT18i
Sahaab said:
For roms built on stock Rom, u shouldnt have any kernel inside the flashable zip
Sent from my LT18i
Click to expand...
Click to collapse
Yeah, that's what I though after someguyfromhell wrote a post and I made a new zip without boot.img and deleted write_raw_image line from update-script.
Right now I am searching for solution to other problem(some folders and files are not showing up on my sdcard while viewing it in Windows, so I have no space to drop ROM in there, will try when I fix this).
Thank you both for replies, will try to fix this soon.
A_B_E_D said:
Hmmm, how am I going to make custom ROM without boot.img if it is needed(or is it?).
I can't get any other custom kernel because I want to make ROM for locked bootloader phone.
Do you know what should I do to complete ROM if i can't have stock boot.img?
Click to expand...
Click to collapse
If you are going to do a ROM for locked bootloaders, then there is no boot.img needed at all. Locked bootloader means stock kernel, means no boot.img.
Also, it is not needed. Some ROM developers supply their own kernels together with the ROM, however it is not a requirement.
Is there an way to port a gsm rom (jb like sphlong or omega) to cdma? I tried Curtis's guide by i found myself stuck and it wouldn't boot properly. What i got stuck on was the boot.img part of it. Here's the guide
http://forum.xda-developers.com/showthread.php?t=2362137
Can someone possibly explain how to get the boot.img to work, i cant understand what its saying
Dbzavatar said:
Is there an way to port a gsm rom (jb like sphlong or omega) to cdma? I tried Curtis's guide by i found myself stuck and it wouldn't boot properly. What i got stuck on was the boot.img part of it. Here's the guide
http://forum.xda-developers.com/showthread.php?t=2362137
Can someone possibly explain how to get the boot.img to work, i cant understand what its saying
Click to expand...
Click to collapse
use the boot image from your base ROM.
If you're S-ON use fastboot to flash it.
MameTozhio said:
use the boot image from your base ROM.
If you're S-ON use fastboot to flash it.
Click to expand...
Click to collapse
One more thing, the modules from the base ROM's boot.img has to be added to the GSM rom, right?
Yes add the modules from the base rom boot img. Be sure the boot img you use is from a compatible and same version cdma rom. In other words,if the rom you are converting is 4.1+ use a cdma boot.img that is meant for 4.1+ roms. If the rom is 4.0,use a cdma 4.0 based boot.img along with its modules. Be aware that some roms just do not respond as expected even if you make these changes. It is trial and error finding roms that will convert as expected.
Thanks!!
Curtis1973 said:
Yes add the modules from the base rom boot img. Be sure the boot img you use is from a compatible and same version cdma rom. In other words,if the rom you are converting is 4.1+ use a cdma boot.img that is meant for 4.1+ roms. If the rom is 4.0,use a cdma 4.0 based boot.img along with its modules. Be aware that some roms just do not respond as expected even if you make these changes. It is trial and error finding roms that will convert as expected.
Click to expand...
Click to collapse
I tried to redo the conversion with the sphlonge rom and while flashing, i got
assert failed: getprop('ro.product,device")
does this mean i cant flash it since its primou?
Dbzavatar said:
I tried to redo the conversion with the sphlonge rom and while flashing, i got
assert failed: getprop('ro.product,device")
does this mean i cant flash it since its primou?
Click to expand...
Click to collapse
change the line in updater-script to primoc