Database Info

[Q] HTC Sensation Continuous Bootloop

Unlocked
Pyramid PVT Ship S-ON RL
HBOOT-1.27.0000
eMMc-boot
I installed the new viper 1.41 rom and then tried to flash one of the kernals. It said it was all done but then now I'm stuck in a continuous bootloop.
I can boot into recovery and have tried to flash another rom already but it stays in bootloop, also tried flashing different kernal and still doesn't work.
Tried to start from the beginning using cmd etc (adb etc) but cmd can't find a device when using the command adb devices.
What should I do? Please help !!1

mattyon9 said:
Unlocked
Pyramid PVT Ship S-ON RL
HBOOT-1.27.0000
eMMc-boot
I installed the new viper 1.41 rom and then tried to flash one of the kernals. It said it was all done but then now I'm stuck in a continuous bootloop.
I can boot into recovery and have tried to flash another rom already but it stays in bootloop, also tried flashing different kernal and still doesn't work.
Tried to start from the beginning using cmd etc (adb etc) but cmd can't find a device when using the command adb devices.
What should I do? Please help !!1
Click to expand...
Click to collapse
Hi,
Do you have 4EXT recovery installed?
If so ,enable smartflash.

malybru said:
Hi,
Do you have 4EXT recovery installed?
If so ,enable smartflash.
Click to expand...
Click to collapse
"Download 4EXT recovery (1.0.0.5!)" I have this on installed and smartflash is already enabled via recovery.

mattyon9 said:
"Download 4EXT recovery (1.0.0.5!)" I have this on installed and smartflash is already enabled via recovery.
Click to expand...
Click to collapse
Hi,
Unless you have it permanently enabled,you must enable it just before you flash anything.

malybru said:
Hi,
Unless you have it permanently enabled,you must enable it just before you flash anything.
Click to expand...
Click to collapse
Again I've already set smartflash before every flashing of roms. Just this time I'm stuck in a bootloop and can't do nothing about it?

mattyon9 said:
Again I've already set smartflash before every flashing of roms. Just this time I'm stuck in a bootloop and can't do nothing about it?
Click to expand...
Click to collapse
Hi,
Have you got a nandroid you can restore?

malybru said:
Hi,
Have you got a nandroid you can restore?
Click to expand...
Click to collapse
Unfortunately not

Also stuck in the same boat
Hi!
I too am stuck in a bootloop trying to flash CM10.
The problem is I thought I needed CWM to flash the firmware and am now stuck with the CM10 logo when I try and reboot the phone.
Doing more reading 4ext seems to be required to fully wipe the phone rather than CWM
I've found PG58IMG.zip which is recognised when I boot into recovery, but not apparently installed. Perhaps not surprisingly CWM won't install the zip.
Does anyone have any ideas what I can do to the installation?
Thanks
Kevin

mattyon9 said:
Unfortunately not
Click to expand...
Click to collapse
Hi,
You might therefore consider a RUU
Look HERE
---------- Post added at 06:43 PM ---------- Previous post was at 06:39 PM ----------
StockportGerbil said:
Hi!
I too am stuck in a bootloop trying to flash CM10.
The problem is I thought I needed CWM to flash the firmware and am now stuck with the CM10 logo when I try and reboot the phone.
Doing more reading 4ext seems to be required to fully wipe the phone rather than CWM
I've found PG58IMG.zip which is recognised when I boot into recovery, but not apparently installed. Perhaps not surprisingly CWM won't install the zip.
Does anyone have any ideas what I can do to the installation?
Thanks
Kevin
Click to expand...
Click to collapse
Hi,
Firmware is not dependent on a particular recovery.
4 EXT is a better choice ,because it gives you more options.
What PG58IMG.zip were you trying to flash?
S-on/off?
hboot?
radio?
ROM?
Kernel?
etc
etc
etc
More information is required...

Getting past the bootloop
After my plea for help yesterday regarding the bootloop after I had tried to update my HTC Sensation, I eventually found the answer to my problem. Also the response I had yesterday raised some questions which I note at the end
.
Firstly I was trying to update my stock firmware HTC Sensation to CM10; the build I was using was the AOKP / Kang build by bruce2728 dated 16th November as that seemed to be being actively maintained and the functionality I required was reportedly working fine. I read the rather cursory instructions and given I’ve updated several Android tablets before I thought this will be easy. FAIL!
I’ll document elsewhere the process I followed, however the problem I had was when I tried to apply the CM10 image using CWM. It seemed to write successfully but when I came to reboot the phone it was stuck in a boot loop with the cyanogenmod logo stuck on the screen until I pulled the battery out. I couldn’t install 4ext using the play store app as I’d trashed the android installation.
I eventually replace CWM with 4ext by downloading the correct recovery image to my PC (from the third post of http://forum.xda-developers.com/showthread.php?t=1666401, note that the recovery image is different for different phones and possibly operator.)
I then started the phone in bootloader (noting the phone was S-ON), plugged in the USB connection and pressed the power button, so fastboot was selected and then Fastboot usb was displayed on the phone.
From a command prompt on the PC after changing to the directory where I had placed fastboot and adb I typed “fastboot recovery recovery.img” and this replaced CWM with 4ext.
After rebooting the phone and getting back into the bootloader, I selected recovery. This time 4ext started. Before writing the new Android image I wiped user data and (I think it was in tools once you scrolled to the bottom) selected “enable 4ext superflash” before flashing the ROM and Google Apps and then successfully rebooting the phone. For reference the phone took less than 5 minutes to start up.
I now think my problem was trying to flash the ROM with S-ON and not using 4-ext superflash. Oh well
Following on from the response from malybru (Thanks)
Does writing a new rom change the radio? I’d understood it remained the same unless you made special efforts to change it and you were likely to wipe out the phone?
Thanks again
Kevin

maybe i am wrong but radio can be changed only when you are flashing different firmware and to do that you have to be S-OFF

StockportGerbil said:
After my plea for help yesterday regarding the bootloop after I had tried to update my HTC Sensation, I eventually found the answer to my problem. Also the response I had yesterday raised some questions which I note at the end
.
Firstly I was trying to update my stock firmware HTC Sensation to CM10; the build I was using was the AOKP / Kang build by bruce2728 dated 16th November as that seemed to be being actively maintained and the functionality I required was reportedly working fine. I read the rather cursory instructions and given I’ve updated several Android tablets before I thought this will be easy. FAIL!
I’ll document elsewhere the process I followed, however the problem I had was when I tried to apply the CM10 image using CWM. It seemed to write successfully but when I came to reboot the phone it was stuck in a boot loop with the cyanogenmod logo stuck on the screen until I pulled the battery out. I couldn’t install 4ext using the play store app as I’d trashed the android installation.
I eventually replace CWM with 4ext by downloading the correct recovery image to my PC (from the third post of http://forum.xda-developers.com/showthread.php?t=1666401, note that the recovery image is different for different phones and possibly operator.)
I then started the phone in bootloader (noting the phone was S-ON), plugged in the USB connection and pressed the power button, so fastboot was selected and then Fastboot usb was displayed on the phone.
From a command prompt on the PC after changing to the directory where I had placed fastboot and adb I typed “fastboot recovery recovery.img” and this replaced CWM with 4ext.
After rebooting the phone and getting back into the bootloader, I selected recovery. This time 4ext started. Before writing the new Android image I wiped user data and (I think it was in tools once you scrolled to the bottom) selected “enable 4ext superflash” before flashing the ROM and Google Apps and then successfully rebooting the phone. For reference the phone took less than 5 minutes to start up.
I now think my problem was trying to flash the ROM with S-ON and not using 4-ext superflash. Oh well
Following on from the response from malybru (Thanks)
Does writing a new rom change the radio? I’d understood it remained the same unless you made special efforts to change it and you were likely to wipe out the phone?
Thanks again
Kevin
Click to expand...
Click to collapse
Hi,
Flashing a ROM does NOT change the radio.
In fact,you cannot change the radio or firmware if you are s-on.
"Smartflash" is what I would have suggested if you had 4 EXT recovery and s-on.
It is all well documented HERE

malybru said:
Hi,
Flashing a ROM does NOT change the radio.
In fact,you cannot change the radio or firmware if you are s-on.
"Smartflash" is what I would have suggested if you had 4 EXT recovery and s-on.
It is all well documented HERE
Click to expand...
Click to collapse
Hi!
I think I read everything except that guide yesterday - thanks it is interesting.
Regards
Kevin

New to One S and need some help

Hi,
Normally, I try to troubleshoot things myself without bothering others, but I'm in need of help this time. The tricky part is, I just bought this HTC One S from a stranger, so I don't have its complete history. With that said, here's what I need help with. The phone came with Pacman installed (v18.0.0). But, I would like to install this ROM: http://forum.xda-developers.com/showthread.php?t=2082451
It's basically a stock ICS ROM (the lite version mentioned with stuff removed). In attempt to do this myself, I found this post on here:
Yes the only other solution for you involves rooting. It is possible to go back to ICS by rooting your phone, going through a bootloader downgrade, hexediting a particular partition, then running an older compatible RUU... Its all possible, but requires some time to understand and do. And definately requires a few wipes of phone data in the mean time (which can be backed up through titanium and custom recoveries).
Only need to do that if you want to downgrade hboot. All you have to do is root and flash a rom, I have JB radio and hboot and run ICS Trickdroid 8.1.0.
So, I put the ICS ROM in the internal sdcard, did the usual wiping stuff (I've owned several HTC phones, so this part I know how), then installed the ROM. Unfortunately, it didn't work. When I rebooted the phone, it got stuck in boot loop. It would go to HTC logo screen with the development purpose only warning and just keep turning off and on. Fortunately, I was able to get back into recovery and restored it to Pacman. So, apparently, you can't just flash any ICS ROM over JB setup... Can someone help me figure out what I need to do to install that modified stock ROM please? I very much appreciate your help. My One S is S4 from T-Mobile.
Thank you,
GT

Did you flash boot.img?
Sent from my HTC VLE_U using xda app-developers app

thats weird.. if you wipe cache, dalvik, factory reset and system.. it should be fine.
which recovery do you have? cwm or twrp? flashing the rom after wiping everything i stated before, and then flashing boot.img depending on your hboot [btw, go to bootloader and see what it says for hboot. if it is higher than 1.13, you need to fastboot boot.img.

dr_rick13 said:
thats weird.. if you wipe cache, dalvik, factory reset and system.. it should be fine.
which recovery do you have? cwm or twrp? flashing the rom after wiping everything i stated before, and then flashing boot.img depending on your hboot [btw, go to bootloader and see what it says for hboot. if it is higher than 1.13, you need to fastboot boot.img.
Click to expand...
Click to collapse
Thank you for tending to my thread. The recovery installed is CWM 5.8.3.1
Here's what it says on fastboot:
Tampered
Unlocked
VLE PVT SHIP S-On RL
HBOOT-1.14.0004
RADIO-1.08ts.50.02.16
OpenDSP-v29.1.0.45.0622
eMMC-boot
Please let me know what exactly I need to do in step by step or point me to a thread that contains the steps. Thank you so much.

goldentequila said:
Thank you for tending to my thread. The recovery installed is CWM 5.8.3.1
Here's what it says on fastboot:
Tampered
Unlocked
VLE PVT SHIP S-On RL
HBOOT-1.14.0004
RADIO-1.08ts.50.02.16
OpenDSP-v29.1.0.45.0622
eMMC-boot
Please let me know what exactly I need to do in step by step or point me to a thread that contains the steps. Thank you so much.
Click to expand...
Click to collapse
no prob, i HIGHLY suggest you flash TWRP recovery.. it's a loot better.
2. are you trying to install a TMOUS ROM?
3. since your hboot is higher than 1.13, you will need to fastboot boot.img [let me know if you know how to do that]
4. also since your hboot is higher than 1.13, you will need to flash some partitions or else your WiFi won't work.
Let me know if you need help doing any of the above, but start out with installing TWRP first.

dr_rick13 said:
no prob, i HIGHLY suggest you flash TWRP recovery.. it's a loot better.
2. are you trying to install a TMOUS ROM?
3. since your hboot is higher than 1.13, you will need to fastboot boot.img [let me know if you know how to do that]
4. also since your hboot is higher than 1.13, you will need to flash some partitions or else your WiFi won't work.
Let me know if you need help doing any of the above, but start out with installing TWRP first.
Click to expand...
Click to collapse
Thank you for such a prompt reply. Here are some of my answers.
2. Yes, the ROM I want to install is this one: http://forum.xda-developers.com/showthread.php?t=2082451
It's the light version mentioned in that first post.
3. I just read up on this page: http://forum.xda-developers.com/showthread.php?t=1752270
I think I got the idea, but just to double check, is this what I need to do after every time I install a custom ROM?
4. The partition files exist on the phone already, and I read some, so I have a basic understanding of it. But, the developer of the ROM I want to install says it is not necessary with that ROM, so hopefully that's true.
I am amazed by how different everything is from a HTC phone to another HTC phone even when they seem so similar!
A quick question. Does EXT4 exist for HTC One S? I used to use that for HTC Sensation and loved it. I'm guessing no, but I thought I'd ask.
So, to sum it up, is this what I need to do?
1. Flash TWRP recovery (please tell me how to find the right version for S4. all in one toolkit doesn't work on my phone).
2. Wipe everything and install the ROM
3. Flash boot.img
4. If wifi is not working, try the partition files
Please let me know if I got this right. Thank you,

goldentequila said:
Thank you for such a prompt reply. Here are some of my answers.
2. Yes, the ROM I want to install is this one: http://forum.xda-developers.com/showthread.php?t=2082451
It's the light version mentioned in that first post.
3. I just read up on this page: http://forum.xda-developers.com/showthread.php?t=1752270
I think I got the idea, but just to double check, is this what I need to do after every time I install a custom ROM?
4. The partition files exist on the phone already, and I read some, so I have a basic understanding of it. But, the developer of the ROM I want to install says it is not necessary with that ROM, so hopefully that's true.
I am amazed by how different everything is from a HTC phone to another HTC phone even when they seem so similar!
A quick question. Does EXT4 exist for HTC One S? I used to use that for HTC Sensation and loved it. I'm guessing no, but I thought I'd ask.
So, to sum it up, is this what I need to do?
1. Flash TWRP recovery (please tell me how to find the right version for S4. all in one toolkit doesn't work on my phone).
2. Wipe everything and install the ROM
3. Flash boot.img
4. If wifi is not working, try the partition files
Please let me know if I got this right. Thank you,
Click to expand...
Click to collapse
If the Toolkit can't see your phone then you might need to install the drivers that come with it for it to work.

goldentequila said:
Thank you for such a prompt reply. Here are some of my answers.
2. Yes, the ROM I want to install is this one: http://forum.xda-developers.com/showthread.php?t=2082451
It's the light version mentioned in that first post.
3. I just read up on this page: http://forum.xda-developers.com/showthread.php?t=1752270
I think I got the idea, but just to double check, is this what I need to do after every time I install a custom ROM?
4. The partition files exist on the phone already, and I read some, so I have a basic understanding of it. But, the developer of the ROM I want to install says it is not necessary with that ROM, so hopefully that's true.
I am amazed by how different everything is from a HTC phone to another HTC phone even when they seem so similar!
A quick question. Does EXT4 exist for HTC One S? I used to use that for HTC Sensation and loved it. I'm guessing no, but I thought I'd ask.
So, to sum it up, is this what I need to do?
1. Flash TWRP recovery (please tell me how to find the right version for S4. all in one toolkit doesn't work on my phone).
2. Wipe everything and install the ROM
3. Flash boot.img
4. If wifi is not working, try the partition files
Please let me know if I got this right. Thank you,
Click to expand...
Click to collapse
3. Yes, since your hboot is higher than 1.13, you will need to fastboot boot.img everytime you flash a ROM, unless you want to downgrade?
3.5: like Darknites said, you will need to install drivers for your the One S if you haven't already. You can download HTC Sync, and they'll install automatically [this is needed for being able to fastboot the boot.img]
4. They do exist, but everytime you wipe before flashing a ROM, they also get deleted, but try using the ROM without flashing the partition files and see if it works, if not then flash the partition files.
5. Yes, I'm pretty sure EXT4 exists with the One S, but am not 100% sure, maybe someone else can confirm this?
Lastly, here is where you download TWRP:
http://teamw.in/project/twrp2/100
scroll down and download the link for the S4 VARIANT, but you need to have drivers installed before doing this. and you will need to fastboot the recovery, since the download is an image: to do so, go into cmd, type cd c:\ (whatever your fastboot folder is called) and enter
then, type: fastboot flash [name of recovery, which is the name of the file you downloaded).img. Should take about 2 seconds to flash.
BTW, here are the drivers:
http://d-h.st/users/Inferi0r/?fld_id=2736#files

dr_rick13 said:
3. Yes, since your hboot is higher than 1.13, you will need to fastboot boot.img everytime you flash a ROM, unless you want to downgrade?
3.5: like Darknites said, you will need to install drivers for your the One S if you haven't already. You can download HTC Sync, and they'll install automatically [this is needed for being able to fastboot the boot.img]
4. They do exist, but everytime you wipe before flashing a ROM, they also get deleted, but try using the ROM without flashing the partition files and see if it works, if not then flash the partition files.
5. Yes, I'm pretty sure EXT4 exists with the One S, but am not 100% sure, maybe someone else can confirm this?
Lastly, here is where you download TWRP:
http://teamw.in/project/twrp2/100
scroll down and download the link for the S4 VARIANT, but you need to have drivers installed before doing this. and you will need to fastboot the recovery, since the download is an image: to do so, go into cmd, type cd c:\ (whatever your fastboot folder is called) and enter
then, type: fastboot flash [name of recovery, which is the name of the file you downloaded).img. Should take about 2 seconds to flash.
BTW, here are the drivers:
http://d-h.st/users/Inferi0r/?fld_id=2736#files
Click to expand...
Click to collapse
Ya 4EXT is coming soon.

dr_rick13 said:
3. Yes, since your hboot is higher than 1.13, you will need to fastboot boot.img everytime you flash a ROM, unless you want to downgrade?
3.5: like Darknites said, you will need to install drivers for your the One S if you haven't already. You can download HTC Sync, and they'll install automatically [this is needed for being able to fastboot the boot.img]
4. They do exist, but everytime you wipe before flashing a ROM, they also get deleted, but try using the ROM without flashing the partition files and see if it works, if not then flash the partition files.
5. Yes, I'm pretty sure EXT4 exists with the One S, but am not 100% sure, maybe someone else can confirm this?
Lastly, here is where you download TWRP:
http://teamw.in/project/twrp2/100
scroll down and download the link for the S4 VARIANT, but you need to have drivers installed before doing this. and you will need to fastboot the recovery, since the download is an image: to do so, go into cmd, type cd c:\ (whatever your fastboot folder is called) and enter
then, type: fastboot flash [name of recovery, which is the name of the file you downloaded).img. Should take about 2 seconds to flash.
BTW, here are the drivers:
http://d-h.st/users/Inferi0r/?fld_id=2736#files
Click to expand...
Click to collapse
Thank you so much. Yes, I tried installing the drivers using the toolkit's function, but I haven't tried HTC Sync option. Maybe that'll work better. I think I know what I need to do now. Thanks a bunch!

goldentequila said:
Thank you so much. Yes, I tried installing the drivers using the toolkit's function, but I haven't tried HTC Sync option. Maybe that'll work better. I think I know what I need to do now. Thanks a bunch!
Click to expand...
Click to collapse
Also try rebooting the computer if its still not working.

goldentequila said:
Thank you so much. Yes, I tried installing the drivers using the toolkit's function, but I haven't tried HTC Sync option. Maybe that'll work better. I think I know what I need to do now. Thanks a bunch!
Click to expand...
Click to collapse
Thank you, dr_rick13 and other kind members who responded to my call for help.
I was able to troubleshoot this, and now my phone's working the way I wanted it. Just one correction on dr_rick13's instruction:
then, type: fastboot flash [name of recovery, which is the name of the file you downloaded).img. Should take about 2 seconds to flash
recovery is missing in that line, so it should be fastboot flash recovery [name of recovery, which is the name of the file you downloaded).img
I know it was just a typo or forgot to write it, but I wanted to point this out in case some other user finds this thread and follows that instruction.
All in all, thanks for everything! You guys rock!
GT

goldentequila said:
Thank you, dr_rick13 and other kind members who responded to my call for help.
I was able to troubleshoot this, and now my phone's working the way I wanted it. Just one correction on dr_rick13's instruction:
then, type: fastboot flash [name of recovery, which is the name of the file you downloaded).img. Should take about 2 seconds to flash
recovery is missing in that line, so it should be fastboot flash recovery [name of recovery, which is the name of the file you downloaded).img
I know it was just a typo or forgot to write it, but I wanted to point this out in case some other user finds this thread and follows that instruction.
All in all, thanks for everything! You guys rock!
GT
Click to expand...
Click to collapse
oops, it was late last night when I wrote that.. my bad
Sent from my HTC One S using xda premium

I'm new here too. I understand that you need to flash the boot.img with that hboot, but why? And will it ever be fixed?
I've owned and rooted many a phones and never had to do that. Just curious why it's like that, and if it will be fixed. It's just easier to not be that way. Again, I'm new here, just trying to understand
Sent from my HTC Glacier using Tapatalk 2

pnut22r said:
I'm new here too. I understand that you need to flash the boot.img with that hboot, but why? And will it ever be fixed?
I've owned and rooted many a phones and never had to do that. Just curious why it's like that, and if it will be fixed. It's just easier to not be that way. Again, I'm new here, just trying to understand
Sent from my HTC Glacier using Tapatalk 2
Click to expand...
Click to collapse
we do not have S-OFF yet, so until we do.. people with hboots 1.13+ will need to flash boot.img. But HTC still hasn't said anything about when we will get S-OFF or if we will get it.

pnut22r said:
I'm new here too. I understand that you need to flash the boot.img with that hboot, but why? And will it ever be fixed?
I've owned and rooted many a phones and never had to do that. Just curious why it's like that, and if it will be fixed. It's just easier to not be that way. Again, I'm new here, just trying to understand
Sent from my HTC Glacier using Tapatalk 2
Click to expand...
Click to collapse
Its just the way HTC wants us to do it and maybe they feel it be better for us but mostly them. There is a way round it but you have to downgrade the Hboot.

Darknites said:
Its just the way HTC wants us to do it and maybe they feel it be better for us but mostly them. There is a way round it but you have to downgrade the Hboot.
Click to expand...
Click to collapse
Thanks. Is there any downside to downgrading the hboot? Why don't people do that instead?
When I had the Amaze, the recovery 4ext had "smart flash" which did this same thing because it was s-on
Sent from my HTC Glacier using Tapatalk 2

pnut22r said:
Thanks. Is there any downside to downgrading the hboot? Why don't people do that instead?
When I had the Amaze, the recovery 4ext had "smart flash" which did this same thing because it was s-on
Sent from my HTC Glacier using Tapatalk 2
Click to expand...
Click to collapse
Because of Linux and the fact you brick it to do it too. We meant to be getting 4ext but don't know when.

Darknites said:
Because of Linux and the fact you brick it to do it too. We meant to be getting 4ext but don't know when.
Click to expand...
Click to collapse
Thanks
http://forum.xda-developers.com/showthread.php?p=33233125
This seems like out would make things so much easier. I'm not always around a pc when wanting to flash things. If I use this, I should be able to flash away.
But what about resorting nandroids. This doesn't work with that. Hmmm
Just trying to wrap my mind around it
Sent from my HTC Glacier using Tapatalk 2

pnut22r said:
Thanks
http://forum.xda-developers.com/showthread.php?p=33233125
This seems like out would make things so much easier. I'm not always around a pc when wanting to flash things. If I use this, I should be able to flash away.
But what about resorting nandroids. This doesn't work with that. Hmmm
Just trying to wrap my mind around it
Sent from my HTC Glacier using Tapatalk 2
Click to expand...
Click to collapse
Yep very good app I did use it in till I downgraded.

Deleted /system, help!

Hi guys,
My cousin from America came to visit yesterday, and he asked me if I could install CyanogenMod on his phone. It's an HTC One X from AT&T. So I set his CID to 111111, unlocked his bootloader with HTCDev, flashed TWRP 2.5.0.0 and then I rooted his phone. Afterwords, I did a backup via TWRP Recovery.
I looked for the CyanogenMod for this device and the stable build was cm-10.0.0-evita. I transfered it to the phone's TWRP folder, booted recovery and tried to install it but failed, the error message was: assert failed: getprop("ro.bootloader") == 2.1....and some more numbers and stuff
Stupid as I was, I thought "It's probably the stock ROM interfering with the installation, and I can always restore my backup" so I erased a couple of things from the phone: Dalvik Cache, Cache, Data, sdcard and System. Left Android Secure alone because I didn't know what it was or what it does.
Then it hit me. I formatted Data, my backup was gone! And so was the ROM I wanted to flash!
What do I do now? I don't have any operating system installed and can't boot into android! All I can do is boot into Recovery and Bootloader.
Here's what bootloader says:
*** TAMPERED ***
*** UNLOCKED ***
EVITA PVT SHIP S-ON RL
HBOOT-1.09.000
RADIO-0.16.32.09.01_3
OpenDSP-v25.1.0.32.0405
eMMC-boot
Apr 2 2012, 21:08:24
My recovery is: TWRP 2.5.0.0
Any ideas?

It's ok, no need to panic
Download ROM to PC. Make doubly sure it's for this device, I think the error you experienced the first time was because you tried to flash an International One X ROM. Only get your ROMs from here, or here.
Boot into recovery.
Connect the phone to the PC.
Mount your sd/internal storage from your TWRP menu.
Copy ROM from PC to phone.
Wipe cache/dalvik/factory reset/system.
Flash ROM.
Reboot.
Enjoy.
Sent from my Evita

Alright, no problem, the error you got in TWRP was because you needed to have HBOOT 2.14 or above to install CM10.1 because of the kernel it uses. Never wipe /sdcard because it won't do you any good. Now, what you're gonna wanna do is, mount USB Storage in TWRP (under mount menu) when it's connected to your PC, download a ROM (not CM10.1 for now, we'll get to that soon enough) and make sure it's for this phone, drag and drop it to your phone from the PC, and flash it. Once you do that, if you still want to get CM10.1, we can help you with that too.
Edit: @timmaaa he won't be able to use CM10.1 because he's on hboot 1.09.

Your main problem, is that you are deleting/formatting things without having any clue what they are. This is an invitation for disaster. Your backups are deleted because your deleted the SD card, not because you deleted /data or /system.
/system = current ROM
/data = user data (phone storage), formatting is the same as factory reset
The only things that really need to be deleted when flashing a new ROM is /data (factory reset) and cache. Formatting /system is not necessary, as flashing a new ROM does this by default before installing the new ROM.
Connect the phone to your computer, mount USB in TWRP, and move the new ROM zip to the SD card, and flash from TWRP.
Its also a good idea to copy a backup to your computer or Dropbox. But that is probably not something that will help you at the moment. Just a bit of advice moving forward.

While in twrp, plug into your pc then go to mounts > mount usb storage. Then put whatever Rom on there. Make sure you get the right Rom for this device.
EDIT:
Oh wow just realized I was beat by like 3 people before I hit post lol
Sent from my HTC One X using xda premium

dragancla said:
Hi guys,
My cousin from America came to visit yesterday, and he asked me if I could install CyanogenMod on his phone. It's an HTC One X from AT&T. So I set his CID to 111111, unlocked his bootloader with HTCDev, flashed TWRP 2.5.0.0 and then I rooted his phone. Afterwords, I did a backup via TWRP Recovery.
I looked for the CyanogenMod for this device and the stable build was cm-10.0.0-evita. I transfered it to the phone's TWRP folder, booted recovery and tried to install it but failed, the error message was: assert failed: getprop("ro.bootloader") == 2.1....and some more numbers and stuff
Stupid as I was, I thought "It's probably the stock ROM interfering with the installation, and I can always restore my backup" so I erased a couple of things from the phone: Dalvik Cache, Cache, Data, sdcard and System. Left Android Secure alone because I didn't know what it was or what it does.
Then it hit me. I formatted Data, my backup was gone! And so was the ROM I wanted to flash!
What do I do now? I don't have any operating system installed and can't boot into android! All I can do is boot into Recovery and Bootloader.
Here's what bootloader says:
*** TAMPERED ***
*** UNLOCKED ***
EVITA PVT SHIP S-ON RL
HBOOT-1.09.000
RADIO-0.16.32.09.01_3
OpenDSP-v25.1.0.32.0405
eMMC-boot
Apr 2 2012, 21:08:24
My recovery is: TWRP 2.5.0.0
Any ideas?
Click to expand...
Click to collapse
First off flash twrp 2.3.3.1 or 2.6 all others have issues.
Then mount usb storage from twrp
Copy Rom to sd card
Wipe cache and dalvik
If you're not s-off depending on hboot version the boot image will need to be flashed via fastboot.
Boot into rom.
Good luck.
Edit: just saw your on 1.09 no need to flash boot image first.
Sent from my HTC One XL using xda premium

Oh by the way, TWRP 2.5 is known to have issues, so try using TWRP 2.3.3.1 instead.
You'll need to change recovery versions before doing any of the steps I mentioned above.
Sent from my Evita

timmaaa said:
Oh by the way, TWRP 2.5 is known to have issues, so try using TWRP 2.3.3.1 instead.
You'll need to change recovery versions before doing any of the steps I mentioned above.
Click to expand...
Click to collapse
TWRP 2.6 has been recently released, and appears to have resolved the issues with 2.5. But yeah, 2.5 and 2.4 are known to cause some serious problems (many ROMs will fail to flash).

Lol. All together now.
Sent from my Evita
---------- Post added at 12:37 AM ---------- Previous post was at 12:31 AM ----------
redpoint73 said:
TWRP 2.6 has been recently released, and appears to have resolved the issues with 2.5. But yeah, 2.5 and 2.4 are known to cause some serious problems (many ROMs will fail to flash).
Click to expand...
Click to collapse
Yeah I've heard it's working well, I'm gonna give it a spin hopefully in the next few days. I just thought it'd be best to suggest something we know for sure is solid for right now.
Sent from my Evita

Wow, thanks for the quick responses!
First of all, I can't mount SD card from TWRP. I can mount cache, data and System, but the checkbox nextto sdcard can't be clicked, stays unchecked. I can mount USB Storage but my computer says it needs to format the drive to use it, and I'm using Windows not Linux.
Secondly, whenever i try to flash openrecovery-twrp-2.3.1.0-evita.img with adb fastboot it says "The filename, directory name, or volume syntax is incorrect".
What do I do? :S

Also, after I've done this, what ROM do you suggest I download to flash, given my bootloader and situation?

dragancla said:
Wow, thanks for the quick responses!
First of all, I can't mount SD card from TWRP. I can mount cache, data and System, but the checkbox nextto sdcard can't be clicked, stays unchecked. I can mount USB Storage but my computer says it needs to format the drive to use it, and I'm using Windows not Linux.
Secondly, whenever i try to flash openrecovery-twrp-2.3.1.0-evita.img with adb fastboot it says "The filename, directory name, or volume syntax is incorrect".
What do I do? :S
Click to expand...
Click to collapse
You must have done a factory reset from bootloader, which has corrupted your storage. So, mount usb storage then format it using Windows to fat32 format.
The error you're encountering while trying to flash recovery is most likely because you're giving adb incorrect or mistyped command. To make it easier on yourself, rename the recovery zip file on your pc to something simple like "twrp.img" then issue the following command exactly:
fastboot flash recovery twrp.img
Sent from my Evita

dragancla said:
First of all, I can't mount SD card from TWRP. I can mount cache, data and System, but the checkbox nextto sdcard can't be clicked, stays unchecked.
Click to expand...
Click to collapse
You didn't do a factory reset from bootloader did you?

RollTribe said:
You didn't do a factory reset from bootloader did you?
Click to expand...
Click to collapse
Looks like he did. Instructions given above.
Sent from my Evita
---------- Post added at 12:53 AM ---------- Previous post was at 12:52 AM ----------
dragancla said:
Also, after I've done this, what ROM do you suggest I download to flash, given my bootloader and situation?
Click to expand...
Click to collapse
You can flash pretty much any Sense ROM, and most aosp ROMs (just not the ones with the 3.4 kernel).
Sent from my Evita

RollTribe said:
You didn't do a factory reset from bootloader did you?
Click to expand...
Click to collapse
I did :S Thought it would help...
timmaaa said:
You must have done a factory reset from bootloader, which has corrupted your storage. So, mount usb storage then format it using Windows to fat32 format.
The error you're encountering while trying to flash recovery is most likely because you're giving adb incorrect or mistyped command. To make it easier on yourself, rename the recovery zip file on your pc to something simple like "twrp.img" then issue the following command exactly:
fastboot flash recovery twrp.img
Sent from my Evita
Click to expand...
Click to collapse
Thanks, it worked! I can mount sdcard now!
What's the next step?

dragancla said:
I did :S Thought it would help...
Yeah, never do that...
Thanks, it worked! I can mount sdcard now!
What's the next step?
Click to expand...
Click to collapse
Now you can flash any ROM you want as long as it isn't AOSP with 3.4 kernel. Unless you really want the 3.4 ROM, but then you'd first have to s-off and then run the RUU to 3.18.

The next step after what? What exactly have you achieved so far?
Sent from my Evita

RollTribe said:
Now you can flash any ROM you want as long as it isn't AOSP with 3.4 kernel. Unless you really want the 3.4 ROM, but then you'd first have to s-off and then run the RUU to 3.18.
Click to expand...
Click to collapse
Would this work? http://forum.xda-developers.com/showthread.php?t=2230754
Or can you link me any ROM that would work for me, please?

dragancla said:
Would this work? http://forum.xda-developers.com/showthread.php?t=2230754
Or can you link me any ROM that would work for me, please?
Click to expand...
Click to collapse
Yeah, that would work. It's a little outdated, but it should work just fine.

timmaaa said:
The next step after what? What exactly have you achieved so far?
Sent from my Evita
Click to expand...
Click to collapse
Well, I can now access the sdcard/internal storage on my PC when I connect the cable in TWRP Recovery. I just need a ROM.

Screen went blank after flashing boot.img

Meaning to install CyanogenMod I followed CyanogenMod wiki instructions (can't post link here)
Only that I have TWRP instead of CWM.
When I got to installing "CyanogenMod from recovery" I got a message saying that the pushing had failed because permissions did not allow it.
So I tried a solution they suggested for a similar message which did not work, and then I read the note at the bottom that says the kernel should be flashed via fastboot, I flashed it but now it's just blank (I guess because it has an alien kernel and the rest is the same)
I dont have a copy of my previous boot.img

Not enough information provided, please provide the following:
-Your bootloader details
-Your current TWRP version
-The exact filename of the ROM zip you flashed
-Is the phone powering on at all
Sent from my Evita

timmaaa said:
Not enough information provided, please provide the following:
-Your bootloader details HBOOT 2.15.0000 S-OFF
-Your current TWRP version 2.6.3
-The exact filename of the ROM zip you flashedcm-10.2.1-evita.zip I tried to flash it but couldnt do it on adb only flash the boot.img
-Is the phone powering on at all yes it is, it goes through the start screen and when it would show the icons it's just black with the backlight on
Sent from my Evita
Click to expand...
Click to collapse
Answers

What do you mean you couldn't do it on adb? Do what on adb? You don't use adb to flash a ROM.
Sent from my Evita

timmaaa said:
What do you mean you couldn't do it on adb? Do what on adb? You don't use adb to flash a ROM.
Sent from my Evita
Click to expand...
Click to collapse
I mean to push the rom on the root of the sdcard: look at the instructions I followed:
Place the CyanogenMod rom .zip file on the root of the SD card using adb:
Transfer your file(s): adb push YOURROMZIP.zip /sdcard/
If you boot directly to recovery and have an internal sdcard, you may need to run adb shell mount /sdcard or mount data through the recovery menu before transferring.
If you see "error: device not found" there is likely a driver issue on the PC.
If you see "error: insufficient permissions for device", try "adb kill-server" and then run "adb devices" to see if the device is attached.
On some devices, the zip file can be copied to the device using standard USB Mass Storage or MTP support. Boot the device normally and transfer the file to it.
Optional: Place any supplemental packages (e.g. Google Apps[1] or kernel) .zip file(s) on the root of the SD card.
Boot to recovery mode on the device by holding With the device powered down, hold the Volume Down and Power buttons until HBOOT appears, then release the buttons. Navigate using the volume keys and select RECOVERY using the Power key..
Once the device boots into the ClockworkMod Recovery, use the physical volume buttons to move up and down. On most devices, the power button is used to confirm your selection, although for some devices the power button is used as a "back" button to go up one level, in which case the home button is used to confirm the selection.
Optional/Recommended: Select backup and restore to create a backup of the current installation on the device. If this option is missing, it's likely because the stock ROM has overwritten your custom recovery on boot.
Select the option to wipe data/factory reset.
Select install zip from sdcard.
Select choose zip from sdcard.
Select the CyanogenMod file you placed on the sdcard. You will then need to then confirm that you do wish to flash this file.
Optional: Install any additional packages you wish using the same method.
Once the installation has finished, return back to the main menu, and select the reboot system now option. The device should now boot into CyanogenMod.
Click to expand...
Click to collapse
And the note I mentioned:
Note:
This device, if unlocked with HTC Dev Unlock, MUST have its kernel flashed via fastboot! Extract the boot.img from the rom zip and flash using fastboot flash boot boot.img
Click to expand...
Click to collapse

dvdmrn said:
I mean to push the rom on the root of the sdcard: look at the instructions I followed:
Click to expand...
Click to collapse
So you never actually flashed the ROM but you flashed the boot.img from the ROM zip anyway? No wonder it isn't working, you've flashed an incompatible boot.img onto whatever ROM you previously had installed (which is still installed by the way because flashing a boot.img does not flash a ROM).
All you needed to do was mount your sd card using TWRP (menu/mount/mount usb storage) and copy the ROM zip across, then install it. You have s-off so you don't ever need to flash the boot.img separately.
I really think you need to do some research, it seems you lack even a basic understanding of what you're doing. You don't know what a boot.img is or what it does or how or why you would need to flash it. You don't seem to know how to use your custom recovery. You don't seem to know how to install a ROM.
A lack of knowledge is almost always what leads to somebody bricking their phone, which I'm sure you don't want to happen. Do yourself a favour and spend the next couple of days reading up so you have a better understanding of modified devices. A great place to start would be my Evita FAQ thread and my How-To Guide For Beginners thread, you'll find both in my signature.
Sent from my Evita
---------- Post added at 06:17 AM ---------- Previous post was at 06:14 AM ----------
dvdmrn said:
And the note I mentioned:
Click to expand...
Click to collapse
I'm not sure where you found that note but it isn't entirely correct. Only Evitas with s-on and a hboot greater than 1.09 need to flash the boot.img via fastboot.
Sent from my Evita

timmaaa said:
So you never actually flashed the ROM but you flashed the boot.img from the ROM zip anyway? No wonder it isn't working, you've flashed an incompatible boot.img onto whatever ROM you previously had installed (which is still installed by the way because flashing a boot.img does not flash a ROM).
All you needed to do was mount your sd card using TWRP (menu/mount/mount usb storage) and copy the ROM zip across, then install it. You have s-off so you don't ever need to flash the boot.img separately.
I really think you need to do some research, it seems you lack even a basic understanding of what you're doing. You don't know what a boot.img is or what it does or how or why you would need to flash it. You don't seem to know how to use your custom recovery. You don't seem to know how to install a ROM.
A lack of knowledge is almost always what leads to somebody bricking their phone, which I'm sure you don't want to happen. Do yourself a favour and spend the next couple of days reading up so you have a better understanding of modified devices. A great place to start would be my Evita FAQ thread and my How-To Guide For Beginners thread, you'll find both in my signature.
Sent from my Evita
---------- Post added at 06:17 AM ---------- Previous post was at 06:14 AM ----------
I'm not sure where you found that note but it isn't entirely correct. Only Evitas with s-on and a hboot greater than 1.09 need to flash the boot.img via fastboot.
Sent from my Evita
Click to expand...
Click to collapse
This is where it's from
wiki cyanogenmod org / w / Install_CM_for_evita
I'm sorry for having hurried and done that but I couldn't flash the ROM and there were no more instructions, I've been reading for the last months, and even though I thought replacing the kernel could not be the best idea, it was the only idea I could get from those instructions and I thought maybe the kernel would have to be moved first for some reason. Anyway, thank you very much for your patience, I have to do it today because I have to travel and at&t limitations on the network -since it forces 4G- won't allow me to use my current carrier. I tried just moving the ROM by mounting and it worked. Thanks man

[Q] I Soft Bricked my HTC One M8

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