[Q] Problems with kernel flashing - HTC One X

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

Related

[Q] Flash boot.img before restoring Nandroid?

Stupid question:
did i have to flash the right boot.img when i restore a rom via nandroid?
lets say, i have a sense rom installed, but want to restore the cyanogen rom.
did i have to flash any boot.img before i restore a backup?
i guess not. correct me if im wrong
Yes, of course you do. You can't write to the boot partition from recovery (without s-off), which is why you have to flash the boot.img via fastboot when you flash a ROM. So when you're restoring a backup from recovery it's still not able to write to the boot partition, so you'll have to flash the boot.img from your backup yourself.
where do you get the boot.img from? is it in the nandroid backup file, if so where? Thanks!
ps sorry for bringing up an old thread.
In the .zip file of the Rom you want to restore.
Sent from my HTC One X using xda premium
where do i get it for a nandroid backup of stock rom?
vans88 said:
where do i get it for a nandroid backup of stock rom?
Click to expand...
Click to collapse
depending what version you want. there is a thread in development by Tryce.. he had all the stock recoveries from 1.26 and onwards and all the boot.imgs for all stock rom versions.
here is the link i was talking about
http://forum.xda-developers.com/showthread.php?t=1616741
Thanks Goku80! That thread did the trick!
vans88 said:
Thanks Goku80! That thread did the trick!
Click to expand...
Click to collapse
no worries buddy. Glad to help
pls help about galaxy y duos gt-s6102
Goku80 said:
no worries buddy. Glad to help
Click to expand...
Click to collapse
I flash by odin but downloading mode in phone not cout --> only zero so long. (use kies is same)
Now my phone is error flashing boot, i want to flash by odin or kies but i can't
Pls help me!!!!
windows112009 said:
I flash by odin but downloading mode in phone not cout --> only zero so long. (use kies is same)
Now my phone is error flashing boot, i want to flash by odin or kies but i can't
Pls help me!!!!
Click to expand...
Click to collapse
this is the HTC One X Forum mate
Thanks to all the info of boot.img really help this guy over here.
i wanted to restore the backup of stock rom and couldnĀ“t do it
once again thanks
SandmanPT said:
Thanks to all the info of boot.img really help this guy over here.
i wanted to restore the backup of stock rom and couldnĀ“t do it
once again thanks
Click to expand...
Click to collapse
U should flash the same boot.img as it was when u made the nandroid, for example, yesterday I was with venon and franco s kernel, made a nandroid, flashed another rom and boot.img. then used my nandroid of venon, restored nandroid and flashed franco s kernel boot.img.
LET THEM TALK, ALOUD!! HTC ONE X, THE ONLY ONE. VIPERX + FRANCO KERNEL r12

[Q] Do I have to flash boot.img every time I flash a new Custom Rom?

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

Questions for clever people

[FONT="Century Gothic"
Hey, just wondering if anyone can answer a few questions for me. Total newbie here and i'm just currently learning before i take action. I'm slowly getting there
I'm currently on 1.28 (Android 4.0.3) if i were to flash a custom 4.0.4 (2.05) rom would i be able to return to my current state via nandroid?
How do you 'uninstall kernel mods'?
Why can i return to 1.28 from a custom rom, but not from an OTA
Thank you for your time if you answer.
I'll be thanking ANYONE who answers
thankssss
][/FONT]
smidgeox said:
[FONT="Century Gothic"
Hey, just wondering if anyone can answer a few questions for me. Total newbie here and i'm just currently learning before i take action. I'm slowly getting there
I'm currently on 1.28 (Android 4.0.3) if i were to flash a custom 4.0.4 (2.05) rom would i be able to return to my current state via nandroid?
How do you 'uninstall kernel mods'?
Why can i return to 1.28 from a custom rom, but not from an OTA
Thank you for your time if you answer.
I'll be thanking ANYONE who answers
thankssss
][/FONT]
Click to expand...
Click to collapse
Make the back up before you install anything and you can restore it fine..
Restore will wipe out any mods you have installed but to just remove a kernel you need stock modules to flash and also the boot.IMG.
You will need to flash the boot.IMG in the backup folder from your pc in fastboot as the device is s-on and as a result boot.IMG cannot by flash from CWM this needs to be done.for every ROM you try.
Sent from my HTC One X using xda app-developers app
Thanks for your answer. Really grateful. Where would I find these stock modules and I thought the boot.img includes the kernel so wouldn't flashing the stock boot.img get rid of the mods?
X
smidgeox said:
Thanks for your answer. Really grateful. Where would I find these stock modules and I thought the boot.img includes the kernel so wouldn't flashing the stock boot.img get rid of the mods?
X
Click to expand...
Click to collapse
say you flash ARHD and then you flash boot.img stock one...there is a thread dedicated to repacking. there you can find the stock modules for that rom...same goes with the other custom kernels. GuyAdams has all repacked boot.imgs with modules there
and no flashing boot.img does not get rid off any mods

How to retrieve current/stock boot.img

Hi guys!
Noob here. Searched through other threads but all i found is making CWM backups as well as flashing the kernel (boot.img)
Would like to know if there is a way to get the currently running boot.img?
I'm on a stock rom, unlocked booloader and rooted. Reason I need this is for easy/quick switching to stock.
I used a boot.img that was posted here on one of the threads but it seems to be for a different region (though it still worked as i was running the correct recovery file plus I had to do all the steps again). In case i have to go back to stock again this would be a faster way i think.
make a nandroid backup of ur stock rom
ul get yourself a stock kernel
or else get ur ruu available and extract urslf
Sent from my One V
paarthdesai said:
make a nandroid backup of ur stock rom
ul get yourself a stock kernel
or else get ur ruu available and extract urslf
Sent from my One V
Click to expand...
Click to collapse
Hahaha. I'm such a noob I didn't realize it's also backing up boot.img
Many thanks, paarthdesai!

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

Categories

Resources