Hi i'm new to the att htc one x, just rooted, and installed twrp... then flash cleanrom5. I also noticed clean has a kernel, i did not see an install guide, but i've installed kernels before on my captivate. So what i'm wondering if it's as easy as....
1. place kernel on phone storage
2. reboot into recovery
3. install kernel from recovery
4. reboot
If there anything i am missing or if i am completely off could someone please help me out with this?
Thank you :good:
If you are on the 1.14 hboot (rooted on 2.20 firmware) you can't flash kernels from recovery. You have to do it using fastboot.
redpoint73 said:
If you are on the 1.14 hboot (rooted on 2.20 firmware) you can't flash kernels from recovery. You have to do it using fastboot.
Click to expand...
Click to collapse
Would you mind walking me through that process?
Unless this makes any difference "CleanROM V is based on the latest Asian 2.29 RUU which is Android 4.0.4, Sense 4.1 and is ODEXED!"
not sure if that means i am on 2.29 rooted.
cannon19932006 said:
Would you mind walking me through that process?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1957193
http://forum.xda-developers.com/showpost.php?p=33493959&postcount=2
Sent from my HTC One XL
absolutelygrim said:
http://forum.xda-developers.com/showthread.php?t=1957193
http://forum.xda-developers.com/showpost.php?p=33493959&postcount=2
Sent from my HTC One XL
Click to expand...
Click to collapse
I don't see anything about flashing kernels in that thread.
cannon19932006 said:
I don't see anything about flashing kernels in that thread.
Click to expand...
Click to collapse
the boot.img has the kernel in it, it has to be flashed from fastboot.
heres the kernel. dl.dropbox.com/u/31360541/CleanKERNEL/CleanKERNEL 1.1 - HOX.zip
flash the boot.img from fastboot, then flash the zip from recovery. fastboot flash method http://forum.xda-developers.com/showpost.php?p=33493959&postcount=2
edit: btw, what exploit did you use to achieve root? Was it the x-factor exploit?
cannon19932006 said:
Unless this makes any difference "CleanROM V is based on the latest Asian 2.29 RUU which is Android 4.0.4, Sense 4.1 and is ODEXED!"
not sure if that means i am on 2.29 rooted.
Click to expand...
Click to collapse
Not the firmware you are on now. The firmware you originally achieved root on. More importantly, what version is your hboot (go to hboot, and the version number is listed)?
If your phone was purchased with 2.20 firmware, and you rooted using the new X-factor exploit method, you have the 1.14 hboot.
Hboot 1.14 plugged the hole by which flashing kernels from recovery was possible. So it can only be done by fastboot.
redpoint73 said:
Not the firmware you are on now. The firmware you originally achieved root on. More importantly, what version is your hboot (go to hboot, and the version number is listed)?
If your phone was purchased with 2.20 firmware, and you rooted using the new X-factor exploit method, you have the 1.14 hboot.
Hboot 1.14 plugged the hole by which flashing kernels from recovery was possible. So it can only be done by fastboot.
Click to expand...
Click to collapse
i used x-factor yes, and yes it's 1.14, thank you both for the help.
cannon19932006 said:
i used x-factor yes, and yes it's 1.14, thank you both for the help.
Click to expand...
Click to collapse
Ok, since you used x-factor, make sure to flash your boot.img before flashing the ROM
Same with a kernel. Flash boot.img then the kernel zip
absolutelygrim said:
Ok, since you used x-factor, make sure to flash your boot.img before flashing the ROM
Same with a kernel. Flash boot.img then the kernel zip
Click to expand...
Click to collapse
I already flashed the rom, just not the kernel, i don't remember flashing the boot.img, just following the instructions on the rom's page here
http://forum.xda-developers.com/showthread.php?t=1655011
"Must have twrp Recovery installed with unlocked bootloader! CWM Recovery will cause serious issues!!!
Copy ROM to storage
Reboot to Recovery
Wipe data / Factory Reset in Recovery!
Install ROM and Aroma installer will start.
Choose Options
Let install complete
Reboot to System"
That's how i flashed this rom anyway.
That's funny your in schertz, i live like 5 miles from there in Universal city lol.
cannon19932006 said:
I already flashed the rom, just not the kernel, i don't remember flashing the boot.img, just following the instructions on the rom's page here
http://forum.xda-developers.com/showthread.php?t=1655011
"Must have twrp Recovery installed with unlocked bootloader! CWM Recovery will cause serious issues!!!
Copy ROM to storage
Reboot to Recovery
Wipe data / Factory Reset in Recovery!
Install ROM and Aroma installer will start.
Choose Options
Let install complete
Reboot to System"
That's how i flashed this rom anyway.
That's funny your in schertz, i live like 5 miles from there in Universal city lol.
Click to expand...
Click to collapse
Well, If cleanROM is using the same Kernel as stock, then you got lucky. If they use the same kernel, no need to flash boot.img.
If they are different kernels and you dont flash boot.img, you are now in a bootloop
lol Universal City
not bad
Sorry for so many questions lol, just making sure i do this right.
okay so basically i want to download the kernel and the fastboot drivers posted in your post.
Extract the fastboot drivers, and then unzip the kernel, taking the boot.img from it and placing it into the fastboot directory that i just unzipped.
I then want to boot my phone into hboot and select fastboot
open the command prompt and take it to where the fastboot.exe is.
then type fastboot flash boot boot.img into the command prompt
After all this is done i want to go into recovery and flash the zip of the kernel?
Is that all right?
cannon19932006 said:
Sorry for so many questions lol, just making sure i do this right.
okay so basically i want to download the kernel and the fastboot drivers posted in your post.
Extract the fastboot drivers, and then unzip the kernel, taking the boot.img from it and placing it into the fastboot directory that i just unzipped.
I then want to boot my phone into hboot and select fastboot
open the command prompt and take it to where the fastboot.exe is.
then type fastboot flash boot boot.img into the command prompt
After all this is done i want to go into recovery and flash the zip of the kernel?
Is that all right?
Click to expand...
Click to collapse
Yeap. Don't "extract" the zip, just drag the boot.img out of the zip
absolutelygrim said:
Yeap. Don't "extract" the zip, just drag the boot.img out of the zip
Click to expand...
Click to collapse
Success, THANKS!
absolutelygrim said:
the boot.img has the kernel in it, it has to be flashed from fastboot.
heres the kernel. dl.dropbox.com/u/31360541/CleanKERNEL/CleanKERNEL 1.1 - HOX.zip
flash the boot.img from fastboot, then flash the zip from recovery.
Click to expand...
Click to collapse
Why do you say to flash the boot.img and then zip if boot.img has the kernel in it?
Thank you. R
cimenta said:
Why do you say to flash the boot.img and then zip if boot.img has the kernel in it?
Thank you. R
Click to expand...
Click to collapse
Because the new hboot makes it to where you cant flash kernels through recovery. only fasboot
So why the second flash if the boot.img was flashed via fastboot?
I am just lost in these. Could you recommend any reading except this forum for me to get more understanding? So I don't do anything to my phone?
cimenta said:
So why the second flash if the boot.img was flashed via fastboot?
I am just lost in these. Could you recommend any reading except this forum for me to get more understanding? So I don't do anything to my phone?
Click to expand...
Click to collapse
It wasn't.
boot.img can't be flashed from recovery, it skips it.
Thats why you flash boot.img from fastboot then the ROM from recovery
http://forum.xda-developers.com/showthread.php?t=1963896
absolutelygrim said:
It wasn't.
boot.img can't be flashed from recovery, it skips it.
Thats why you flash boot.img from fastboot then the ROM from recovery
http://forum.xda-developers.com/showthread.php?t=1963896
Click to expand...
Click to collapse
So although ROM zip file contains boot.img when flashing boot.img won't be flashed? That's why we need to flash is separately? Is it important to flash it before flashing ROM?
Thank you.R
I'm also, learning as I go. From reading and multiple failed attempts at flashing ROMs and kernels, I have found the correct way with 1.14 Hboot.
-dl the rom/kernel
-extract only the boot.img file
- save both .zip and boot to your desired folder.
-go into recovery and mount sd card to pc
-transfer .zip file to your phones sd card
-get back into fastboot on your phone
-transfer boot.img to fastboot folder
-from fastboot cmd prompt(if you have win7, open your folder with fastboot in it hold shift+right click and open cmd)
-type "fastboot boot boot.img" without quotes
-go back into recovery and clean cache/delvik
-then install .zip that you copied to the sd card
You should be good to go from there.
If I have left anything out, please feel free to correct.
Sent from my HTC One X using xda app-developers app
Related
After unlock, root install recovery, by following
http://www.htconeforum.com/forum/htc-one-s-hacks/385-how-unlock-root-htc-one-s.html
then I put miui.2.8.24 from official website:
http://www.miui.com/extra.php?mod=download/rom&fid=160
after reboot, install miui, then reboot, the screen stays on the boot picture of miui, never changes, I guess that failed, and too bad, I didn't notice there is back up function in recovery, so I didn't notice,
what I have is: fast boot still talks to the phone, but seems can't mount the phone as a drive, so I can't load other ROMs to try it out.
then I try to follow this one:
http://www.htconeforum.com/forum/ht...c-one-s-back-100-stock-relocked.html#post2817
to restore the stock rom, there was any luck, after long time trying, RUU just failed. what should I do now?
I already relock it, can I still unlock it? if so, is there anywhere I can find stock img, and use fast boot to flash the stock img? is that possible?
Thanks.
Did you fastboot the boot.img of say ROM you're flashing?
If using CWM you need to fastboot the boot.img, just extract the boot.img from the ROM
Using fastboot
Code:
fastboot flash boot boot.img
baseballfanz said:
Did you fastboot the boot.img of say ROM you're flashing?
If using CWM you need to fastboot the boot.img, just extract the boot.img from the ROM
Using fastboot
Code:
fastboot flash boot boot.img
Click to expand...
Click to collapse
first of all, thanks for reply,
no, but i did try to flash another boot.img, and wasn't any luck, so each rom has its own boot.img?
Ummm.......Yeah. It should be in the zip of rom you flashed.
T-MobileUS HTC One S running Stock Rooted 2.21.
fmedrano1977 said:
Ummm.......Yeah. It should be in the zip of rom you flashed.
T-MobileUS HTC One S running Stock Rooted 2.21.
Click to expand...
Click to collapse
thanks, I will try it tonight. by the way, after you rooted, you get better battery performance while running stock rom?
hi guys
when i was flashing roms before i had to manually flash boot.img in fastboot since i didnt have twrp
but i noticed the kernel is the same date as the rom i just flashed today (cm10)
do the new CWMs flash the boot.img ?
You need to fastboot because there is no s off
Sent from my HTC One S using xda premium
qwerty warrior said:
hi guys
when i was flashing roms before i had to manually flash boot.img in fastboot since i didnt have twrp
but i noticed the kernel is the same date as the rom i just flashed today (cm10)
do the new CWMs flash the boot.img ?
Click to expand...
Click to collapse
CWM has always been able to flash boot.img with the ROM if you fastboot booted into CWM, like so: (provided the clockwork-recovery-version-blabla.img file is in your current dir ofc)
Code:
fastboot boot clockwork-recovery-version-blabla.img
Maybe CWM can flash the boot.img on certain Hboot versions, what is yours?
Ooh is there a new CWM version for ville?
frdd said:
CWM has always been able to flash boot.img with the ROM if you fastboot booted into CWM, like so: (provided the clockwork-recovery-version-blabla.img file is in your current dir ofc)
Code:
fastboot boot clockwork-recovery-version-blabla.img
Maybe CWM can flash the boot.img on certain Hboot versions, what is yours?
Ooh is there a new CWM version for ville?
Click to expand...
Click to collapse
from what i read only TWRP had the ability to flash boot.img without going into fastboot and using ADB
but when i went into rom manager it said new clockworkmod 5.8.3.1 so i updated
and noticed the new kernel after a normal rom update in recover (CWM)
qwerty warrior said:
from what i read only TWRP had the ability to flash boot.img without going into fastboot and using ADB
but when i went into rom manager it said new clockworkmod 5.8.3.1 so i updated
and noticed the new kernel after a normal rom update in recover (CWM)
Click to expand...
Click to collapse
Na CWM can do it if booted the way i described. Kind of defeats the purpose though as you still need to have a computer hooked up, might as well fastboot flash the boot image. 5.8.3.1 is a couple of months old. But check which Hboot version you have, that might explain why it works for you. You can also check your kernel version with ADB by the way, like so:
HTML:
adb shell uname -a
Hey guys!! I was thinking about flashing the Blackout Beast Mode 3 to my phone thats runnig viper xl. I just wanted to make sure there're compatible and I also want to know if I have any problems how I would go about getting the stock kernel back. Thanks for your answers as always.
Nevermind I found the answer. No it will not work. Moderaters feel free to delete thread.
ImagioX1 said:
Nevermind I found the answer. No it will not work. Moderaters feel free to delete thread.
Click to expand...
Click to collapse
Yea it will. Flash the camera fix and it should work fine
Of course it wil bro. Flash that shiz and be amazed. I'm running viper 2.1, beastmode at a consistent 1.89 GHz, and this thing is on fire. You won't be disappointed
sent from my venom injected, blazingly fast as f#&k OneXL via xda premium
Just a note I have had some overheating at times and a lot of slowdown without ocing...Although the slowing down I have a feeling is because of my execcive undervolting which did make my battery awesome though
I run performance. And overvolted :sly:
sent from my venom injected, blazingly fast as f#&k OneXL via xda premium
Where would I find the camera fix cause I can't do without a camera? I have read several post in the beastmode thread but haven't seen a camera fix.
ImagioX1 said:
Where would I find the camera fix cause I can't do without a camera? I have read several post in the beastmode thread but haven't seen a camera fix.
Click to expand...
Click to collapse
cam fix
absolutelygrim said:
cam fix
Click to expand...
Click to collapse
I found it just before you posted, but thanks anyway. I think i'm going to give up on flashing the kernel though. I thought it could be done through recovery but with 2.20 you must flash through fastboot. I don't even know the commands for flashing or all the steps involved-i'm new at this stuff. Don't want to brick my five hundred dollar phone thats only a month old and don't even have a warranty.
ImagioX1 said:
I found it just before you posted, but thanks anyway. I think i'm going to give up on flashing the kernel though. I thought it could be done through recovery but with 2.20 you must flash through fastboot. I don't even know the commands for flashing or all the steps involved-i'm new at this stuff. Don't want to brick my five hundred dollar phone thats only a month old and don't even have a warranty.
Click to expand...
Click to collapse
You can't brick your phone by flashing a kernel.
If you really want to flash the kernel, do this:
1. Install the SDK (fastboot and adb) and drivers as per the root threads that currently exist
2. Flash BeastMode Kernel
3. While still in Recovery, open a Command Prompt (in Administrator mode) on your laptop
4. Switch to the folder where "adb.exe" and "fastboot.exe" are located
5. type "adb pull /tmp/boot.img"
6. If it fails, the drivers aren't installed properly or you're not in the right folder
7. Reboot your phone to Bootloader by typing "adb reboot bootloader"
8. Run "fastboot flash boot boot.img"
9. Reboot your phone
Make sure you also flash the cam fix.
Phone bootloops.
Will not work on my phone. Successfully pulled the boot.img after flashing in recovery. Then I flashed the boot.img that I pulled in fastboot. Then I reboot the phone and wind up in a bootloop. I then have to reflash the boot.img from viper to get the phone to start.
ImagioX1 said:
Wound up with a boot loop flashing the boot.img on page 166. I'm running Mac to do the fastboot commands and for some reason I cannot pull the boot.img after flashing the kernel.
Click to expand...
Click to collapse
Just drag and drop the boot.IMG out of the zip and put it in the same.directory as fasboot
Sent from my HTC One XL using xda-developers app
absolutelygrim said:
Just drag and drop the boot.IMG out of the zip and put it in the same.directory as fasboot
Sent from my HTC One XL using xda-developers app
Click to expand...
Click to collapse
I edited my post after you posted that. I have sucessfully pulled the boot.img after installing beastmode. It is in the same directory as fastboot and it sucessfully flashes. It just bootloops after that.
Anyone have any ideas what the problem might be?
ImagioX1 said:
Anyone have any ideas what the problem might be?
Click to expand...
Click to collapse
Let's try this again
1.) Wipe System
2.) Factory Reset
3.) Flash boot.img from ViperXL (from fastboot)
4.) Flash ViperXL (from recovery)
5.) Boot your phone
6.) reboot into fastboot
7.) flash kernel boot.img on page 166 (from fastboot)
8.) flash kernel zip (from recovery)
After flashing the kernel, your camera will NOT work. You will need to flash the camera fix. I don't know if you have to flash that from fastboot or recovery on 1.14.
cam fix
absolutelygrim said:
Let's try this again
1.) Wipe System
2.) Factory Reset
3.) Flash boot.img from ViperXL (from fastboot)
4.) Flash ViperXL (from recovery)
5.) Boot your phone
6.) reboot into fastboot
7.) flash kernel boot.img on page 166 (from fastboot)
8.) flash kernel zip (from recovery)
After flashing the kernel, your camera will NOT work. You will need to flash the camera fix. I don't know if you have to flash that from fastboot or recovery on 1.14.
cam fix
Click to expand...
Click to collapse
Ok. Will try.
I still get a boot loop. If my phone can't handle 2.1 ghz would that be the cause of the bootloop?
ImagioX1 said:
I still get a boot loop.
Click to expand...
Click to collapse
oh 2.20 firmware..
try the same thing but without the last step
I don't know what they did, if they flashed the boot.img and rebooted, or if they flashed the zip with it
absolutelygrim said:
oh 2.20 firmware..
try the same thing but without the last step
I don't know what they did, if they flashed the boot.img and rebooted, or if they flashed the zip with it
Click to expand...
Click to collapse
Ill try that, but TURGE on the previous page of this thread said flash both.
It is often stated that it is necessary to manually flash boot.img via fastboot AFTER installing a xxrom.zip in recovery.
Is this really necessary?
If you take a look in the file updater-script, which belongs to every xxrom.zip, you find that boot.img is flashed as last action in the update procedure (seen e.g. in the latest CM10-nightly). So I guess that it is not necessary to additionally flash it afterwards using fastboot.
Am I right?
1aladdin1 said:
It is often stated that it is necessary to manually flash boot.img via fastboot AFTER installing a xxrom.zip in recovery.
Is this really necessary?
If you take a look in the file updater-script, which belongs to every xxrom.zip, you find that boot.img is flashed as last action in the update procedure (seen e.g. in the latest CM10-nightly). So I guess that it is not necessary to additionally flash it afterwards using fastboot.
Am I right?
Click to expand...
Click to collapse
You are wrong and right lol. If your Hboot is 1.09 or lower TWRP can flash the boot.img but if you higher you have to fastboot or use Flash Image GUI app. And always a good idea to flash boot.img just in case it has changed but thats more for AOSP roms.
Darknites said:
You are wrong and right lol. If your Hboot is 1.09 or lower TWRP can flash the boot.img but if you higher you have to fastboot or use Flash Image GUI app. And always a good idea to flash boot.img just in case it has changed but thats more for AOSP roms.
Click to expand...
Click to collapse
I have Hboot 1.13 - so I need to "fastboot flash boot boot.img"
Unfortunately there is no error message showing that flashing the boot-partition during xxrom.zip-Installation in TWRP-recovery has failed.
I suppose that there is no particular order between installing the xxrom.zip and flashing boot-partition. Am I right?
1aladdin1 said:
I have Hboot 1.13 - so I need to "fastboot flash boot boot.img"
Unfortunately there is no error message showing that flashing the boot-partition during xxrom.zip-Installation in TWRP-recovery has failed.
I suppose that there is no particular order between installing the xxrom.zip and flashing boot-partition. Am I right?
Click to expand...
Click to collapse
I use to fastboot first then rom but now I just use Flash Image GUI. TWRP wont say its failed for some reason but it can if you remove the boot.img but thats nothing to worry about.
there is a method how to downgrade hboot:
http://forum.xda-developers.com/showthread.php?t=1990043&highlight=downgrade+unbrick
it's a little bit tricky and requires some linux knowledge, but it takes you down to hboot 1.06
I can't find any guides about how to install a different (but compatible) kernel, zipped, on a S-ON device. I know I need the kernel to be in .img form and not .zip. Can anyone lead me to a guide, or give me some advices on how do I actually do it?
So you want .zip or .img?
At title it says ''Zip not .img'' And later it says ''to be in .img form and not .zip''
Anyways, with the .img one; you need to find a correct boot.img, then follow this;
http://forum.xda-developers.com/showthread.php?t=1631861
Scroll down, find the ''Extra 1: Flashing "boot.img"''
If this is what you're looking for..
Someone smarter should correct me if I was wrong.
each kernel in development section comes with zip format
There's a mess in my head right now and I can't explain exactly what I want. I apologize.
I have a S-ON HTC Sensation, that means when I want to install a new rom I need to enter bootloader and fastboot the boot.img. Then enter Recovery and flash the rom in zip form.
What if I want to install a new Kernel (a compatible one, as i said) but which is in zip form as the rom. How do I get the boot.img out of it so I can flash the zip afterwards? Because I understand that zipping it normally without any boot.img might get me some errors.
rareshutzu said:
There's a mess in my head right now and I can't explain exactly what I want. I apologize.
I have a S-ON HTC Sensation, that means when I want to install a new rom I need to enter bootloader and fastboot the boot.img. Then enter Recovery and flash the rom in zip form.
What if I want to install a new Kernel (a compatible one, as i said) but which is in zip form as the rom. How do I get the boot.img out of it so I can flash the zip afterwards? Because I understand that zipping it normally without any boot.img might get me some errors.
Click to expand...
Click to collapse
i think i know what are you talking about
do you have 4ext recovery installed?
if not then install 4ext and before flashing any rom or even a kernel enable smartflash from it
you just avoid the step for flashing the boot.img manually
with smartflash feature you don't need to flash any boot.img
rzr86 said:
i think i know what are you talking about
do you have 4ext recovery installed?
if not then install 4ext and before flashing any rom or even a kernel enable smartflash from it
you just avoid the step for flashing the boot.img manually
with smartflash feature you don't need to flash any boot.img
Click to expand...
Click to collapse
Great. That's exactly what I wanted. To not flash boot.img anymore. I'll try and let you know
rareshutzu said:
Great. That's exactly what I wanted. To not flash boot.img anymore. I'll try and let you know
Click to expand...
Click to collapse
FYi, Boot.img comes with every kernel. Open the zip on your pc look around and extract it.
JAM THAT THANKS BUTTON.
Happy to help.