Develop Bugs

Flash boot.img

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

HTC One V boot loops

So I was craving vanilla android on my HTC One V (CDMA, primoc) so I unlocked the boot loader, rooted it and installed TWRP. I tried AOKP first, but I ended up in what was basically a boot loop (it would boot up into the setup/startup but within about 30 seconds to a minute it would reboot). After digging around a bit I found some information indicating that only AOSP ROMs would work on my phone, I think because I had taken all the OTA updates before installing the ROM. So I tried some AOSP ROMs, but virtually all of them do the same thing. I have been able to get the CodefireX ROM working, but MMS doesn't seem to work with it (I can send texts but don't recieve them). I'd love to be able to install CM9 or 10 but I can't seem to find any AOSP ROMs (other than CFX) that don't put me in a boot loop. Any help would be greatly appreciated!!!

Flash kernel mate
Sent from my One V using xda premium

cybervibin said:
Flash kernel mate
Sent from my One V using xda premium
Click to expand...
Click to collapse
I always flash the boot.img from the ROM zip, that is flashing the kernel isn't it?

The following have support for the PrimoC OTA update:
-RhythmicROM
-x3reme Sense v5
-I have also gotten PACman to work using the CFX kernel (flash the ROM but use the boot.img from CFX)
-demi_fiend is working on a ROM and kernel that is basically a stock ROM (at least that's how I understand it). The kernel is available, but the ROM hasn't been uploaded yet.

Sounds like you have what I had yesterday. Had you already allowed any over-the-air updates?
If so, check out this thread: http://forum.xda-developers.com/showthread.php?t=2018518
Option #2 worked nicely for me.

still fash them sepreately,
for sense based go for titanium
and aosp based fgo for hell boy

cybervibin said:
still fash them sepreately,
for sense based go for titanium
and aosp based fgo for hell boy
Click to expand...
Click to collapse
Please read the op. The poster has a primoc.

Ya I had actually already tried option #2 over there but got this error...
Hboot Version is older!
Update Fail!
Press <POWER> to reboot
Click to expand...
Click to collapse
From what I understand from the responses I got on that thread my main ver was updated with the OTA and the RUU they are using only supports the one previous to it.
The following have support for the PrimoC OTA update:
-RhythmicROM
-x3reme Sense v5
-I have also gotten PACman to work using the CFX kernel (flash the ROM but use the boot.img from CFX)
Click to expand...
Click to collapse
Thanks for the info! I'll give those a try.

tallnproud said:
The following have support for the PrimoC OTA update:
-RhythmicROM
-x3reme Sense v5
-I have also gotten PACman to work using the CFX kernel (flash the ROM but use the boot.img from CFX)
-demi_fiend is working on a ROM and kernel that is basically a stock ROM (at least that's how I understand it). The kernel is available, but the ROM hasn't been uploaded yet.
Click to expand...
Click to collapse
Well RhythmicROM is giving me the same issue as all the others. I might try flashing demi_fiend's kernel and see if that helps...
*EDIT* So I just realized it might be important to mention that every time I do a factory reset with TWRP it fails and says sd-ext can't be wiped. I've been able to wipe everything else though, and was able to get CFX working so I assumed that wasn't the problem.

my bad sorry

Where to download stock boot.img and META-INF for Arc S?

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.

[Q] [urgent] Help needed

so i got into this problem i sucessfully unlocked the bootloader using htc offficial method flashed the twrp recovery wiped everything as coming from stock rom
downloaded the slimbeam rom and the g apps and flashed it but the problem is after the htc boot screen i am getting this kind of message in red lines and then it get stuck at that i tried several other roms also still the same problem any solutions where i got wrong??

On your PC, take the rom you're flashing and unzip it with 7zip, get the boot.img file over to where your fastboot is, then in fastboot USB mode, issue this command -
fastboot flash boot boot.img
Be sure that you're only using a rom for your phone.

EarlyMon said:
On your PC, take the rom you're flashing and unzip it with 7zip, get the boot.img file over to where your fastboot is, then in fastboot USB mode, issue this command -
fastboot flash boot boot.img
Be sure that you're only using a rom for your phone.
Click to expand...
Click to collapse
thanks for the reply man
and so i have to extract the rom and flash the boot image from it through flash boot and then flash the rom right?
so do i have to do this process for flashing all types of rom or this is one time only process

ankitxperia said:
thanks for the reply man
and so i have to extract the rom and flash the boot image from it through flash boot and then flash the rom right?
so do i have to do this process for flashing all types of rom or this is one time only process
Click to expand...
Click to collapse
You're unlocked with HTCdev.com but encrypted signature security is still there - aka s-on.
You'll need to do this with every rom flash, unless it includes an s-on kernel installer.
And if one does, those don't work 100% of the time, not the dev's fault.
This is pretty much the standard procedure for all s-on HTCs.
You can skip it if your flashing a similar rom and you're sure it has the exact same kernel as the previous one.
But you'll probably spend more time figuring that out each time than just doing the procedure.
I think most people do the rom first, then the boot.img - I think that you want to go with that.

Thanks man really appreciated the reply
Btw can you suggest stable cm rom kernel combo and
also do I have to flash the boot. Img from the rom I downloaded?
I would be great if you provide stable cm rom :thumbup::thumbup:
Send from my nexus 7 still on jb

Sorry, I own other HTC models and you have to go with one for your phone.
And yeah, you want to flash the boot.img from each rom you download and try.
The boot.img contains the kernel - that ties the hardware to the rest of the rom.
They have to match up.

So we I am also trying to flash ligux rom so we need to flash the rom and gapps in the recovery and then flash the hell boy kernel through flash boot via cmd right?
Send from my nexus 7 still on jb
Send from my nexus 7 still on jb

ankitxperia said:
So we I am also trying to flash ligux rom so we need to flash the rom and gapps in the recovery and then flash the hell boy kernel through flash boot via cmd right?
Send from my nexus 7 still on jb
Send from my nexus 7 still on jb
Click to expand...
Click to collapse
If that kernel and rom combo are compatible, yes, that's it exactly for an s-on HTC.

ankitxperia said:
thanks for the reply man
and so i have to extract the rom and flash the boot image from it through flash boot and then flash the rom right?
so do i have to do this process for flashing all types of rom or this is one time only process
Click to expand...
Click to collapse
Everything is here: http://forum.xda-developers.com/showthread.php?t=1996665

bratusm said:
Everything is here: http://forum.xda-developers.com/showthread.php?t=1996665
Click to expand...
Click to collapse
Thank you! I'm on the app and didn't have time to find it.
Go there, do that.

Why Did a Factory Reset clear Sprint's Network/Cell Data

Whatever info the Sprint techs put into your device in order for it to get service from their network, that information was cleared when I wiped /data/ and /cache/.
Shouldn't that information be saved somewhere safer?
I am now unable to get service. What do?

RUU recovery fixed it.
But will custom ROMs still not be able to get service? Find out soon!

blksith0 said:
RUU recovery fixed it.
But will custom ROMs still not be able to get service? Find out soon!
Click to expand...
Click to collapse
I'm sure you're all eagerly awaiting the results of that test ^
It turns out that NO the custom ROM wiped whatever info allows the phone to place calls, and no updates/actiavtions would fix it. So gg. Don't buy an M9.

blksith0 said:
I'm sure you're all eagerly awaiting the results of that test ^
It turns out that NO the custom ROM wiped whatever info allows the phone to place calls, and no updates/actiavtions would fix it. So gg. Don't buy an M9.
Click to expand...
Click to collapse
That's not correct. As mentioned several times here on xda the boot.img of 3.35.x firmware-based roms is not compatible with 3.y firmware versions where y is not the same as 35. If you're trying to use a non-sense-based custom rom (e.g. CM) you need to flash thicklizard's mono kernel. For sense-based roms you need to re-flash the stock boot.img of your currently installed firmware. After that you can use the chosen rom without problems.
Sent from my HTC One M9 using XDA Labs

So I should first find out what boot.img that ViperROM 5.3.0 uses, and then I should flash that that same boot.img version to my M9?
Do you need S-OFF for changing boot.img?

blksith0 said:
So I should first find out what boot.img that ViperROM 5.3.0 uses, and then I should flash that that same boot.img version to my M9?
Do you need S-OFF for changing boot.img?
Click to expand...
Click to collapse
No and no. Viper is using a boot.img for 3.35.x. You need the boot.img of your stock firmware. You could for example back up the stock boot.img with TWRP before you delete your stock rom and restore it after you flashed the viper rom. However, since the latest viper version is based on an HTC 10 port you still might face issues. Viper 4.3 on the other hand should be working fine since it's based on the HTC One M9. I'd suggest you to ask in the viper thread whether additional steps are needed for getting viper 5.3 to work on your phone.
Edit @blksith0: Sorry, I totally forgot that the viper rom has a special aroma installer with several options for the different branded M9 versions when I wrote this post. Although you might not be using the device on the sprint network you still need to choose the optimisations for sprint. Those options are made for being able to support the different firmware versions and not for the carrier you're actually using. Because of this flashing the stock boot.img shouldn't be needed in case of the viper rom.
Sent from my HTC One M9 using XDA Labs