Related
Hello all. Im new to this particular forum. I own a Galaxy Nexus, but I am unlocking/rooting my buddies One S for him. I have gone through the loops already; unlocked the bootloader, rooted, and installed custom recovery (CWM) with no issues. I was pleasantly surprised to find out that it was a snap compared to his previous HTC Legend. Nightmare.
Anyway, forgive me if this has in fact been answered as I have been searching. After a custom ROM is flashed you still have to flash a boot img via fastboot? I attempted to install CM10 yesterday and get stuck at the HTC boot screen?? Luckily I made a nandroid of the stock ROM and easily reverted. Where do I find the appropriate boot img? Is it just the img that is found in the unpacked ROM? Couldn't find anything pertaining to this in the ROM write up. I know with my Nexus you flash the ROM via recovery and that is it. Strange that you need to also flash the boot img following the ROM flash.
Any help is appreciated.
brunswick000 said:
Hello all. Im new to this particular forum. I own a Galaxy Nexus, but I am unlocking/rooting my buddies One S for him. I have gone through the loops already; unlocked the bootloader, rooted, and installed custom recovery (CWM) with no issues. I was pleasantly surprised to find out that it was a snap compared to his previous HTC Legend. Nightmare.
Anyway, forgive me if this has in fact been answered as I have been searching. After a custom ROM is flashed you still have to flash a boot img via fastboot? I attempted to install CM10 yesterday and get stuck at the HTC boot screen?? Luckily I made a nandroid of the stock ROM and easily reverted. Where do I find the appropriate boot img? Is it just the img that is found in the unpacked ROM? Couldn't find anything pertaining to this in the ROM write up. I know with my Nexus you flash the ROM via recovery and that is it. Strange that you need to also flash the boot img following the ROM flash.
Any help is appreciated.
Click to expand...
Click to collapse
Hello there, since you installed cwm recovery, you have to flash the boot.img via fastboot, if you have the twrp recovery you may not need to flash it via fastboot, it does it for you if you have an hboot under 1.14 but if its over that hboot your going to have to flash the boot.img for any Rom via fastboot. It still wouldn't hurt to flash the boot.img via fastboot but that's just me, well I hope I helped you and if I did then good, and if you wanna know more just ask...
If I helped then just press the thanks button
Sent from my One S
leohdz148 said:
Hello there, since you installed cwm recovery, you have to flash the boot.img via fastboot, if you have the twrp recovery you may not need to flash it via fastboot, it does it for you if you have an hboot under 1.14 but if its over that hboot your going to have to flash the boot.img for any Rom via fastboot. It still wouldn't hurt to flash the boot.img via fastboot but that's just me, well I hope I helped you and if I did then good, and if you wanna know more just ask...
If I helped then just press the thanks button
Sent from my One S
Click to expand...
Click to collapse
Got it to work. Thank you. :good:
brunswick000 said:
Got it to work. Thank you. :good:
Click to expand...
Click to collapse
Hi,
I was using CM10 and now I want to revert back to my previously used stock ROM. However after restoring I'm still unable to boot (I'm using ClockworkMod Touch). Do I need to flash the stock boot.img too? Where I can find it?
Thanks in advance!
TnTonly said:
Hi,
I was using CM10 and now I want to revert back to my previously used stock ROM. However after restoring I'm still unable to boot (I'm using ClockworkMod Touch). Do I need to flash the stock boot.img too? Where I can find it?
Thanks in advance!
Click to expand...
Click to collapse
Its in the rom.zip just extract it. Also look for Flash Image Gui in apps section as enables you too flash a boot.img direct from your phone whilst booted in a rom and will even extract the files for you from the new rom.zip!
Edit: Link to Flash Image Gui - http://forum.xda-developers.com/showthread.php?t=1954121
shadowch31 said:
Its in the rom.zip just extract it. Also look for Flash Image Gui in apps section as enables you too flash a boot.img direct from your phone whilst booted in a rom and will even extract the files for you from the new rom.zip!
Edit: Link to Flash Image Gui - http://forum.xda-developers.com/showthread.php?t=1954121
Click to expand...
Click to collapse
I can't find the zip file for stock HTC ROM
Anyway, I found the boot.img in the nandroid backup folder and it's all good now.
Thank you for the link! ^_^
I would also switch to TWRP. Seems to have less issues, if any, for most folks
Get it thru Goo Manager from PlayStore--
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.
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
I made the mistake of running a cm10 rom on my htc one s that didnt work on i so now i can only access TWRP and my phones bootloader from my One S so I'm trying to find my phone's stock RUU but there are so many out there! Can anyone tell me how to find one? Or another way to get into my phone using another ROM? My phone is rooted with Twrp recovery, Unlocked bootloader obviously and S-on. All my phone does is show the htc bootscreen and then go black but I can still enter bootloader and the TWRP menu and I can connect it to my computer fine. Any help would be VERY greatly appreciated!
IsaacDroid said:
I made the mistake of running a cm10 rom on my htc one s that didnt work on i so now i can only access TWRP and my phones bootloader from my One S so I'm trying to find my phone's stock RUU but there are so many out there! Can anyone tell me how to find one? Or another way to get into my phone using another ROM? My phone is rooted with Twrp recovery, Unlocked bootloader obviously and S-on. All my phone does is show the htc bootscreen and then go black but I can still enter bootloader and the TWRP menu and I can connect it to my computer fine. Any help would be VERY greatly appreciated!
Click to expand...
Click to collapse
Don't give up. I had the same issue with my telus One S. I think I fixed it by falshing boot image separately and after flashing CM10. I believe this happens if the phone is rooted but is in S-ON mode, whatever that means. I remember it really gave me a hard time and as I was going to give up i flashed the boot image and it worked. You have to do it through a command window on your PC. There should be an all-in-one tool in this forum somewhere to simplify the steps a bit. Good luck!
Thanks!
new_convert said:
Don't give up. I had the same issue with my telus One S. I think I fixed it by falshing boot image separately and after flashing CM10. I believe this happens if the phone is rooted but is in S-ON mode, whatever that means. I remember it really gave me a hard time and as I was going to give up i flashed the boot image and it worked. You have to do it through a command window on your PC. There should be an all-in-one tool in this forum somewhere to simplify the steps a bit. Good luck!
Click to expand...
Click to collapse
Thank you very much! Could you tell me what boot image you flashed and maybe how to get it and also how you flashed it? Thank you so much for the response!
IsaacDroid said:
Thank you very much! Could you tell me what boot image you flashed and maybe how to get it and also how you flashed it? Thank you so much for the response!
Click to expand...
Click to collapse
It is in the zip file that you download to flash, i.e. your new ROM. So when you download CM10, open the zip file. BOOT.IMG will be there. Extract it and flash it to your phone. I believe everything was in One_S_All-In-One_Kit_v3.4. Look it up in the forum and it has all the tools you need. I admit that it was a pain and nothing was straight forward. I always root my android devices and install new ROMs. But HTC One S was particularly tricky.
Good luck!
Hello there! Fellow HTC One S user here! Don't give up on CM10! It's way better than stock on your one S! What you need to remember is that HBoot versions higher than 1.09 can't flash the boot while installing the rom, so you need to do that after flashing a rom! The boot for your version is going to be included in the rom's zip file. Look for the boot.img file located in the zip file's root. Every rom should have this. Place this boot.img file in the kernel folder of the One S all in one kit and flash it. You should be good to after that!
Don't hesitate to ask for more help if needed!
Simon
seoman81 said:
Hello there! Fellow HTC One S user here! Don't give up on CM10! It's way better than stock on your one S! What you need to remember is that HBoot versions higher than 1.09 can't flash the boot while installing the rom, so you need to do that after flashing a rom! The boot for your version is going to be included in the rom's zip file. Look for the boot.img file located in the zip file's root. Every rom should have this. Place this boot.img file in the kernel folder of the One S all in one kit and flash it. You should be good to after that!
Don't hesitate to ask for more help if needed!
Simon
Click to expand...
Click to collapse
When I try to flash a ROM through fastboot it sends it fine but then it says: FAILED (remote: not allowed), and I tried pushing the ROM with adb but when I tried to put it on the sdcard, it said permission denied, do you know why? I am S-ON, would that be a problem? Thanks!
Hey guys,
Tonight I went to install cleanrom on my Verizon HTC One M8. I made a nandroid backup as I always do before flashing a new ROM and then proceeded to flash the new ROM. That went great but then I did something I wouldn't normally do I wiped my data just because I wanted a fresh start and all of my important stuff was backed up online. But when I went to boot I'm stuck on the HTC logo. I have an OTG cable so I proceeded to put the ROM on a flash drive and flash it. Same problem. So I put my old ROM ViperOne 2.4 on the flash drive and flashed it. Now I instantly boot into fastboot. This all seems really strange to me but I'm sure its caused by me stupidly formatting data. I need a bigger flash drive to install the original nandroid backup I found online so I will get one today and post my results. I'm almost positive that will fix my problem but I know there might be an HTC guru out there that knows exactly what my problem is and it may be more then what I'm thinking. Sorry this is scattered ive been messing with my phone all night and kinda tired now. Any help is greatly appreciated and thank you in advance for taking time to help me with this issue. And if I missed anything let me know and I will be sure to post it.
Edit
Sorry I completely forgot to add that I put my nandroid backup on my flash drive but when I went to use it it did not work. I believe this is because I did not have a big enough flash drive so it did not completely back up. LOL! Tonight was not my night.
radiowavedev said:
Hey guys,
Tonight I went to install cleanrom on my Verizon HTC One M8. I made a nandroid backup as I always do before flashing a new ROM and then proceeded to flash the new ROM. That went great but then I did something I wouldn't normally do I wiped my data just because I wanted a fresh start and all of my important stuff was backed up online. But when I went to boot I'm stuck on the HTC logo. I have an OTG cable so I proceeded to put the ROM on a flash drive and flash it. Same problem. So I put my old ROM ViperOne 2.4 on the flash drive and flashed it. Now I instantly boot into fastboot. This all seems really strange to me but I'm sure its caused by me stupidly formatting data. I need a bigger flash drive to install the original nandroid backup I found online so I will get one today and post my results. I'm almost positive that will fix my problem but I know there might be an HTC guru out there that knows exactly what my problem is and it may be more then what I'm thinking. Sorry this is scattered ive been messing with my phone all night and kinda tired now. Any help is greatly appreciated and thank you in advance for taking time to help me with this issue. And if I missed anything let me know and I will be sure to post it.
Click to expand...
Click to collapse
Did you flash newest "firmware" as well? The 2.xx.xxx.x ROM's need newest firmware to boot correctly. (Radio, hboot). Old hboot would cause it to hang at boot.
When I flash ROMs in TWRP I go into advanced and check data, dalvik cache, system, and data every time, never had an issue.
andybones said:
When I flash ROMs in TWRP I go into advanced and check data, dalvik cache, system, and data every time, never had an issue.
Click to expand...
Click to collapse
+1
andybones said:
When I flash ROMs in TWRP I go into advanced and check data, dalvik cache, system, and data every time, never had an issue.
Click to expand...
Click to collapse
That is why this was so strange to me. The hboot firmware sounds promising though.
bigblueshock said:
Did you flash newest "firmware" as well? The 2.xx.xxx.x ROM's need newest firmware to boot correctly. (Radio, hboot). Old hboot would cause it to hang at boot.
Click to expand...
Click to collapse
Thank you for the response. I never even knew it was necessary to flash hboot. I've flashed a couple of ROMs before and never flashed hboot. I will try this tonight. Is this just as simple as flashing a zip? And I pick the newest available version?
radiowavedev said:
Thank you for the response. I never even knew it was necessary to flash hboot. I've flashed a couple of ROMs before and never flashed hboot. I will try this tonight. Is this just as simple as flashing a zip? And I pick the newest available version?
Click to expand...
Click to collapse
not just hboot my friend.
the whole firmware.
if you were to take the OTA you would get this firmware installed.
since we are S-OFF and we don't want to take the OTA, as it's MUCH easier to just fastboot the firmware.zip once someone takes the OTA and pulls all the needed files..
here is the thread you want - here
here is a direct copy and paste from the thread full credit to the OP
"4.4.3 DOWNLOADS BELOW no boot or recovery included in this (what this means is that you won't have to re-flash a custom recovery after the firmware, they removed it to make things easier on us.)
https://www.androidfilehost.com/?fid=23622183712470028
CREDIT TO dottat as he posted it 1st so no need for me too well just use his. Be sure to thank him if you see if around.
Flash via fastboot or Sd card method. Flash at your own risk.
directions for flashing firmware via fastboot an radios below.
Place the zip in your fastboot/adb directory on your computer.
Put the device in fastboot mode
(Volume down and power until menu appears, select fastboot using power button)
Connect the device to the computer
Enter the following commands from terminal/command prompt in the fastboot directory, one at a time:
fastboot oem rebootRUU (this puts the device in RUU mode)
fastboot flash zip firmware.zip (rename file to firmware.zip)
It will say that the update did not finish, to flush again, so repeat the above step:
fastboot flash zip firmware.zip
Then fastboot reboot-bootloader��
FYI on my m8 i did not need to be reflushed on 1.55 but on the new update it did.
credit for these directions also come from santod "
andybones said:
not just hboot my friend.
the whole firmware.
if you were to take the OTA you would get this firmware installed.
since we are S-OFF and we don't want to take the OTA, as it's MUCH easier to just fastboot the firmware.zip once someone takes the OTA and pulls all the needed files..
here is the thread you want - here
here is a direct copy and paste from the thread full credit to the OP
"4.4.3 DOWNLOADS BELOW no boot or recovery included in this (what this means is that you won't have to re-flash a custom recovery after the firmware, they removed it to make things easier on us.)
https://www.androidfilehost.com/?fid=23622183712470028
CREDIT TO dottat as he posted it 1st so no need for me too well just use his. Be sure to thank him if you see if around.
Flash via fastboot or Sd card method. Flash at your own risk.
directions for flashing firmware via fastboot an radios below.
Place the zip in your fastboot/adb directory on your computer.
Put the device in fastboot mode
(Volume down and power until menu appears, select fastboot using power button)
Connect the device to the computer
Enter the following commands from terminal/command prompt in the fastboot directory, one at a time:
fastboot oem rebootRUU (this puts the device in RUU mode)
fastboot flash zip firmware.zip (rename file to firmware.zip)
It will say that the update did not finish, to flush again, so repeat the above step:
fastboot flash zip firmware.zip
Then fastboot reboot-bootloader��
FYI on my m8 i did not need to be reflushed on 1.55 but on the new update it did.
credit for these directions also come from santod "
Click to expand...
Click to collapse
Thank you for all of the useful information I will give this a shot tonight.
radiowavedev said:
Thank you for all of the useful information I will give this a shot tonight.
Click to expand...
Click to collapse
Quite welcome, be sure to go into the thread I posted and thank them, it's all their words, I simply copy and pasted it for you.
andybones said:
Quite welcome, be sure to go into the thread I posted and thank them, it's all their words, I simply copy and pasted it for you.
Click to expand...
Click to collapse
Yeah I'm quite used to the ways of XDA but honestly had no idea about hboot. And I definitely will be thanking them. I'm now home and will test it out. I'll post my results afterwards.
andybones said:
Quite welcome, be sure to go into the thread I posted and thank them, it's all their words, I simply copy and pasted it for you.
Click to expand...
Click to collapse
Okay so I downloaded m8.443.firmware.zip does this have to be flashed via fastboot? And once I flash it should I flash my custom rom cleanrom 2.0 rc and that should be it for my issue?
radiowavedev said:
Okay so I downloaded m8.443.firmware.zip does this have to be flashed via fastboot? And once I flash it should I flash my custom rom cleanrom 2.0 rc and that should be it for my issue?
Click to expand...
Click to collapse
well in bootloader/fastboot yes.. but you DO NOT run the fastboot command..
this is exactly what you do
1) the file you downloaded, m8.443.firmware.zip - rename this to firmware.zip
2) adb reboot bootloader (or however you get there)
3) fastboot oem rebootRUU - this is the important part you will be brought to a black screen with a gray HTC logo IIRC, run the next command - the green bar may stop 3/4 of the way this is because you when you run the last command it will finish it.
4) fastboot flash zip firmware.zip
5) fastboot reboot-bootloader
Im sorry this might be stupid but what do you mean by not running fastboot command? And you say reboot-bootloader shouldn't I do reboot-recovery and flash my custom rom after factory resetting of course. Sorry im just trying to make sure im thorough. I would think messing up hboot would permanently brick my phone.
andybones said:
well in bootloader/fastboot yes.. but you DO NOT run the fastboot command..
this is exactly what you do
1) the file you downloaded, m8.443.firmware.zip - rename this to firmware.zip
2) adb reboot bootloader (or however you get there)
3) fastboot oem rebootRUU - this is the important part you will be brought to a black screen with a gray HTC logo IIRC, run the next command - the green bar may stop 3/4 of the way this is because you when you run the last command it will finish it.
4) fastboot flash zip firmware.zip
5) fastboot reboot-bootloader
Click to expand...
Click to collapse
Would it just be easier to use a nandroid backup?
I figure in the meantime ill fill you in on everything I know about my phone. I was previously running the newest version of ViperOne which was 2.5.0 This problem came up after flashing cleanrom 2.0 RC. I am S-off and unlocked of course and I am running CWM-based Recovery v6.0.4.8 and my hboot stats are as follows:
***UNLOCKED***
M8_WLV PVT SHIP S-OFF
CID-VZW__001
HBOOT-3.16.0.0000
RADIO-0.89.20.0321
OpenDSP-v38.2.2-00542-M8974.0311
OS-1.55.605.2
eMMC-boot 2048MB
I have searched the forums looking for anything related to my issue and cant seem to come up with anything. I have come across a few people with the same issues as me but there questions go unanswered which makes me very nervous... I do believe it is related to my hboot firmware but I cant seem to find a thorough explanation of hboot. Sorry I am a former Motorola guy. This HTC stuff is really mixing it up for me. LOL!
I really appreciate all of the help you have given me and am grateful that you are hanging in with my HTC stupidity and phobia of bricking this 700 dollar piece of aluminum and magnesium.
radiowavedev said:
I figure in the meantime ill fill you in on everything I know about my phone. I was previously running the newest version of ViperOne which was 2.5.0 This problem came up after flashing cleanrom 2.0 RC. I am S-off and unlocked of course and I am running CWM-based Recovery v6.0.4.8 and my hboot stats are as follows:
***UNLOCKED***
M8_WLV PVT SHIP S-OFF
CID-VZW__001
HBOOT-3.16.0.0000
RADIO-0.89.20.0321
OpenDSP-v38.2.2-00542-M8974.0311
OS-1.55.605.2
eMMC-boot 2048MB
I have searched the forums looking for anything related to my issue and cant seem to come up with anything. I have come across a few people with the same issues as me but there questions go unanswered which makes me very nervous... I do believe it is related to my hboot firmware but I cant seem to find a thorough explanation of hboot. Sorry I am a former Motorola guy. This HTC stuff is really mixing it up for me. LOL!
I really appreciate all of the help you have given me and am grateful that you are hanging in with my HTC stupidity and phobia of bricking this 700 dollar piece of aluminum and magnesium.
Click to expand...
Click to collapse
Separate the terminology "ROM" and "Firmware" for a moment. Firmware should/will never change regardless of what ROM's you flash. Think of firmware as a computers BIOS, And ROM as your computers operating system.
First, turn your phone off. Second, hold volume down + power button and do NOT let go of volume down until you're in the boot loader screen. Step 3) switch the boot loader into fast boot within that screen(Fast boot or fast boot USB may come up by default it will be highlighted in red). If you're plugged up to your computer via USB, it should automatically say "Fastboot USB". Then you can execute the commands in the command prompt andybones was talking about.
Did i loose you anywhere?
You could just nandroid back to your previous ROM... but that defeats the purpose. You'll never be able to go to a newer Sense ROM without the firmware upgrade anyway. You might as well get it done because it may improve your network signal, boot times, etc. Usually only benefits you,
After you upgrade firmware, it will say hboot 3.18.0000, Radio: 1.09.20.0702,
radiowavedev said:
Would it just be easier to use a nandroid backup?
Click to expand...
Click to collapse
I didn't just waste my time to write you up a STEP BY STEP FOOL proof guide.
I am not doing this for my benefit...
You made a thread.
You asked for help.
I gave detailed, if you mess up you didn't follow them exactly..
Why would you have me give you exact directions to fix your phone, then ask about a nandroid?
NO. If it were that simple my friend, don't you think I would have let you known this?
I'm sorry if this comes off rude, but I went out of my way to give you exact detailed instructions and you blow them off.
Why make a thread and then not take the advice from a Recognized Contributor to this site!?
I hope you can understand how frustrating this is.
I don't do this because it's fun for me to help get your phone fixed, I do it because you asked for help, and I like to help, but when my help goes un-heard and blown off - I walk away. - Best of luck my friend.
I am still going to help because that's the kind of guy I am..
Run the RUU since you are S-OFF if nothing else works.
You are a SOFT-brick. Very easy to fix.
Andybones, I totally understand. I wasnt trying to be rude im just confused and trying to come up with ideas. I understand it was dumb to mention the nandroid now. I hope you can accept my sincerest apology. I appreciate everything you have done for me and understand if you dont want to help me any longer. Like I said it was not my intention to be rude but I see how it can look like that. I just dont know what im doing.
Hi there, I believe I may have been in the same position as you at some point. What actually is happening is that you are trying to flash a new ROM (4.4.3 I believe) with the old hboot. The ROM should still boot but it will take up to 20min.
How to fix this:
1. Boot into boot loader, (manually or adb)
2. Choose fastboot
3. Connect to USB
4. Open command prompt
5. Fastboot devices
6. fastboot oem rebootRUU
7. You should see a black screen with a dark HTC logo.
8. fastboot flash zip (nameofzip).zip
9. When it finishes type fastboot reboot-bootloader (hyphen required)
10. You just flashed the new firmware but it has no os. You now need to flash a ROM or restore a nandroid backup.
Sent from my HTC One M8 GPE converted using XDA Premium mobile app