Develop Bugs

[Q] Flashing Stock Recovery ROM?

How can I flash the Stock Recovery ROM for my Desire Z?
Basically, I want to remove what ClockWorkMod did. Even when I turned Fast Boot off, turned off the phone, it wouldn't, and will startup ClockWorkMod instead. That said, I can't boot into HBOOT at all since wanting to go into HBOOT means I'm required to turn the phone off completely first.
I'm also having trouble finding my shipped ROM (1.34.707.5), and from the other threads I read, it seemed like a bad idea to grab other DZ ROMs and try flashing it.
Can anyone help/guide me with this? Thanks!
Edit: Prior to this, I was trying to overclock my DZ using this guide for noobs http: //androidforums.com/desire-z-all-things-root/233729-ultimate-guide-rooting-overclocking-your-bell-desire-z-newb-friendly.html. I followed every step, inclusive of the backup.
Kudos to Blue1k for the guide and gtrab for the amazing overclock script

Code:
adb reboot bootloader
will get you into fastboot usb.

Hm,fastboot at settings menu deactivated.
Turned phone off,then holding trackpad down and turning phone
on works for me!

Thanks keinengel for the tip!
@Ganli I can't turn phone off using the menu (and with Fast Boot turned off). I tried removing the battery and I got into HBOOT successfully.
That said, I didn't like the way ClockWorkMod disabled my turning off phone (I do appreciate the backup features it provided). Is there anyway I could restore the original recovery back?

n3ph said:
That said, I didn't like the way ClockWorkMod disabled my turning off phone (I do appreciate the backup features it provided). Is there anyway I could restore the original recovery back?
Click to expand...
Click to collapse
There's a known issue with ClockworkMod where, when you have your phone turned off and you plug in the charger, it automatically then starts up in Clockwork. Is this what you're seeing ? Because if not, that sounds very odd (Clockwork disabling turning off your phone ).
You can flash a new recovery from fastboot, if you have the eng hboot installed. I presume you can take the recovery.img file from one of the stock ROMs, then do "fastboot flash recovery recovery.img".

steviewevie said:
There's a known issue with ClockworkMod where, when you have your phone turned off and you plug in the charger, it automatically then starts up in Clockwork. Is this what you're seeing ? Because if not, that sounds very odd (Clockwork disabling turning off your phone ).
You can flash a new recovery from fastboot, if you have the eng hboot installed. I presume you can take the recovery.img file from one of the stock ROMs, then do "fastboot flash recovery recovery.img".
Click to expand...
Click to collapse
Bingo. It turned off completely when I non-fast boot powered it down without the charger plugged in!
I would like to flash the original recovery like what you mentioned. I am afraid of hardware incompatibilities as mine has a different software version than the ones I've seen here. I wonder if I could use them. (By the way, I haven't seen any recovery.img around, only PC10IMGs)

n3ph said:
I would like to flash the original recovery like what you mentioned. I am afraid of hardware incompatibilities as mine has a different software version than the ones I've seen here. I wonder if I could use them. (By the way, I haven't seen any recovery.img around, only PC10IMGs)
Click to expand...
Click to collapse
The PC10IMG is a zip file containing various stuff to make up a ROM, mainly these are partition images. One of them is recovery.img. So you can get recovery.img from one of those ROM images.
What ROM are you running exactly ?

Stock ROM. Probably one of the Asian version.
Baseband
12.28b.60.140eU_26.03.02.02_M
Kernel
2.6.32.21-gd2764ed
[email protected] #1
Tue Oct 26 16:04:03 CST 2010
Build number
1.34.707.5 CL273326 release-keys
Software
1.34.707.5
I haven't seen any ROM with this version on XDA yet. I saw about the RUU in other threads. Will I be able to select flashing only the recovery from RUU? Or is it a full flash only?

n3ph said:
I haven't seen any ROM with this version on XDA yet. I saw about the RUU in other threads. Will I be able to select flashing only the recovery from RUU? Or is it a full flash only?
Click to expand...
Click to collapse
I have never tried the RUU. At a complete guess I would think it is only a full flash.
You can run the RUU then leave it at the first screen, then open up another window and find where Windows has put the temp files it has extracted from the RUU. Amongst those will be the ROM image, which you can open up (it's a zip file) and find the "recovery.img" file, which you can flash via fastboot if you have the eng hboot installed.

Understood. One more question, my HBOOT is stock. Not sure if this is different from "eng hboot" By Fastboot, you meant this program http: //forum.xda-developers.com/showthread.php?t=463627 right?

Im confused here and just thinking out loud for myself but maybe to provoke some logic here --
without clockworkmod you are unable to flash any roms. you must have clockworkmod to tinker with your phone. no clockworkmod = unroot, or semi root psuedo root whatever.
the only way people can flash stuff is with clockworkmod. its the only recovery available at this time.
if i am missing something or being redundant, my sincere regards.
??

n3ph said:
Understood. One more question, my HBOOT is stock. Not sure if this is different from "eng hboot" By Fastboot, you meant this program http: //forum.xda-developers.com/showthread.php?t=463627 right?
Click to expand...
Click to collapse
You can tell which hboot you have if you shut down the phone (fully, not HTC's confusingly-named "fast boot" mode, which is a sleep state) and then hold Volume down and then hold Power till it turns on.
If it says "SHIP" on the first line, it is the stock hboot. The engineering hboot says "ENG". The eng hboot gives you more options.
No need to install that program, if you go through the steps in my adb guide to setup adb via the SDK, you will have fastboot too.

androidcues said:
without clockworkmod you are unable to flash any roms. you must have clockworkmod to tinker with your phone. no clockworkmod = unroot, or semi root psuedo root whatever.
the only way people can flash stuff is with clockworkmod. its the only recovery available at this time.
Click to expand...
Click to collapse
Yes, the only recovery options we have at the moment are stock recovery or ClockworkMod recovery (installed from ROM Manager). Maybe we will get some more custom recoveries in the future, who knows ?
But you don't need ClockworkMod to flash a ROM. You can flash stock ROMs on a stock phone, though only ones designed specifically for your sub-model of phone (e.g. European ROMs if it's a European phone, T-Mobile ROMs if it's a G2, etc, etc).
If you get S-OFF then you can flash custom ROMs to your phone, or stock ROMs from a different stock Vision (e.g. flashing a stock European ROM onto an Asian DZ).
ClockworkMod is very very useful for letting you do a full backup (nandroid backup) of your ROM.
You can also flash other ways, e.g. flashing from your SD card via hboot, or if you have the eng hboot installed then you can use the fastboot mode/utility to flash too.

thank you i stand corrected.

Thanks for the help. After researching more on what you said, I have a better idea on the flashing process =)
I'll try to reserch more while waiting for a compatible ROM for my phone before trying anything again (in case I brick it)

n3ph said:
Thanks for the help. After researching more on what you said, I have a better idea on the flashing process =)
I'll try to reserch more while waiting for a compatible ROM for my phone before trying anything again (in case I brick it)
Click to expand...
Click to collapse
I'd like to know if anyone was able to make a copy of the stock ROM or has found the RUU for this specific version.

[Q] Help! Boot Loop, Hboot/HB USB working, partition update fail.

Really hoping I can revive this incredible.
Got the phone in attempt to fix it, it's in a constant state of 'boot-loop syndrome'..
Can't go into recovery.. can't factory data reset.. all I get is the
....*vibrate*, white HTC incredible screen....*vibrate off*, etc. etc. etc.
The only thing that is working is hboot (as well as hboot usb when plugged into a pc).
But that's as far as I can get.. anything else I attempt to load from the hboot/bootloader it goes into a constant boot loop spasm.
The incredible is currently S-ON
Hboot- 0.92.0000
Radio-2.15.10.07.07
I've tried numerous PB31IMG stock files in attempt to recover the system.
The system/sd card detect the files just fine and attempt to load them.
The PB31IMG at pvillcomp ( http://pvillecomp.com/?page_id=22 ) didn't work, too old
This one, however, does work (only one so far I've found that does)
http://dinc.does-it.net/Stock_Images/4.08.605.2/PB31IMG.zip
But while going through the installation process it fails at Radio_**
all other variables within the file (bootloader, system, recovery, etc) complete successfully.
Once all the components of the zip file are installed, it gives the message
partition update fail!
Update fail!
Click to expand...
Click to collapse
Am stuck at this point, hoping for assistance.. if anyone knows any possible solutions or what the issue could be, please help!
Thank you.

echoedge said:
But while going through the installation process it fails at Radio_**
.
Click to expand...
Click to collapse
That sounds scary. I've heard that a failed radio flash is the only way to permenantly brick one of these phones.
Here's what I would try:
1. Update HBOOT to the latest, from here:
http://dinc.does-it.net/Hboots/Hboot_1.07/
2. Unlock the bootloader using htcdev (see cmlusco's or scotty's guides)
3. Flash a custom recovery using fastboot (I've used CWM and TWRP)
IF you can get all that to complete successfully, and can boot into recovery, you should then be able to get root adb access to the system. This will give you some more options, such as flashing an older RUU (again, see cmlusco's and scotty's guides for downgrading), and just maybe you'll be able to find something that works.

musical_chairs said:
That sounds scary. I've heard that a failed radio flash is the only way to permenantly brick one of these phones.
Here's what I would try:
1. Update HBOOT to the latest, from here:
http://dinc.does-it.net/Hboots/Hboot_1.07/
2. Unlock the bootloader using htcdev (see cmlusco's or scotty's guides)
3. Flash a custom recovery using fastboot (I've used CWM and TWRP)
IF you can get all that to complete successfully, and can boot into recovery, you should then be able to get root adb access to the system. This will give you some more options, such as flashing an older RUU (again, see cmlusco's and scotty's guides for downgrading), and just maybe you'll be able to find something that works.
Click to expand...
Click to collapse
Thanks for the website, was looking for something like that
Anywho, tried to flash it in the bootloader, it seems to find it a file for which is proper but does not give me any option to update it.
It just says "looking for PB31IMG... then finds it, says checking PB31IMG...", then the prompt goes away.
I'm quite limited when it comes to knowledge on this stuff, but anyone think if I decompile the stock ruu (~180mb) PB31IMG.zip, and flashboot each part of the update separately it may work?

Need help with soft-bricked M8, have made progress on my own but need help.

I have a soft-bricked HTC One M8, It happened when I was attempting to return the phone to stock android with stock kernel and stock recovery while relocking the bootloader, none of that is really important though what happened is I had a bad flash and the phone got put into a bootloader loop with no OS. It still had an Unlocked bootloader with S-Off. Once it was in a bootloader loop I was able to download a custom recovery via fastboot commands, the phone can now go into TWRP but it will only boot version 2.7.0.0 - earlier versions don't boot at all and newer versions will boot but are non-responsive/have no display.
Once in TWRP 2.7.0.0 I use push command from adb to load a stock android RUU zip into my MicroSD, I attempt to flash it via TWRP 2.7.0.0 but get a failed response. I have cleared everything and TWRP 2.7.0.0 is having trouble mounting /data/. I tried using using push command through adb to put a newer version of TWRP on my MicroSD so that TWRP could flash it but TWRP was unable to do so. Any version of Clockwork Mod has been unsuccessful to boot.
Essentially TWRP 2.7.0.0 can't flash anything or mount anything for me, I believe I need either a newer version or a different recovery, but no other recovery or twrp version seems to be able to boot correctly.
Any tips, advice, or general help would be extremely appreciated. I try to help myself before asking others and I don't know what else I can do, I have searched the forums for every relevant thread possible and tried many many things to get this to work with no success. Thank you for reading.

Gitnerd said:
I have a soft-bricked HTC One M8, It happened when I was attempting to return the phone to stock android with stock kernel and stock recovery while relocking the bootloader, none of that is really important though what happened is I had a bad flash and the phone got put into a bootloader loop with no OS. It still had an Unlocked bootloader with S-Off. Once it was in a bootloader loop I was able to download a custom recovery via fastboot commands, the phone can now go into TWRP but it will only boot version 2.7.0.0 - earlier versions don't boot at all and newer versions will boot but are non-responsive/have no display.
Once in TWRP 2.7.0.0 I use push command from adb to load a stock android RUU zip into my MicroSD, I attempt to flash it via TWRP 2.7.0.0 but get a failed response. I have cleared everything and TWRP 2.7.0.0 is having trouble mounting /data/. I tried using using push command through adb to put a newer version of TWRP on my MicroSD so that TWRP could flash it but TWRP was unable to do so. Any version of Clockwork Mod has been unsuccessful to boot.
Essentially TWRP 2.7.0.0 can't flash anything or mount anything for me, I believe I need either a newer version or a different recovery, but no other recovery or twrp version seems to be able to boot correctly.
Any tips, advice, or general help would be extremely appreciated. I try to help myself before asking others and I don't know what else I can do, I have searched the forums for every relevant thread possible and tried many many things to get this to work with no success. Thank you for reading.
Click to expand...
Click to collapse
If you ask me
since i have s-off I would just change my mid and cid to dev edition then flash dev end ruu.

Gitnerd said:
I have a soft-bricked HTC One M8, It happened when I was attempting to return the phone to stock android with stock kernel and stock recovery while relocking the bootloader, none of that is really important though what happened is I had a bad flash and the phone got put into a bootloader loop with no OS. It still had an Unlocked bootloader with S-Off. Once it was in a bootloader loop I was able to download a custom recovery via fastboot commands, the phone can now go into TWRP but it will only boot version 2.7.0.0 - earlier versions don't boot at all and newer versions will boot but are non-responsive/have no display.
Once in TWRP 2.7.0.0 I use push command from adb to load a stock android RUU zip into my MicroSD, I attempt to flash it via TWRP 2.7.0.0 but get a failed response. I have cleared everything and TWRP 2.7.0.0 is having trouble mounting /data/. I tried using using push command through adb to put a newer version of TWRP on my MicroSD so that TWRP could flash it but TWRP was unable to do so. Any version of Clockwork Mod has been unsuccessful to boot.
Essentially TWRP 2.7.0.0 can't flash anything or mount anything for me, I believe I need either a newer version or a different recovery, but no other recovery or twrp version seems to be able to boot correctly.
Any tips, advice, or general help would be extremely appreciated. I try to help myself before asking others and I don't know what else I can do, I have searched the forums for every relevant thread possible and tried many many things to get this to work with no success. Thank you for reading.
Click to expand...
Click to collapse
That's not how to flash an RUU.zip
This is how it is done.
Make sure that your extSD is formatted to FAT32 first. It won't work otherwise.
After the format, rename the zip to 0P6BIMG.zip (that's a zero, not the letter) and place it onto the root of your card.
Boot into bootloader (Turn off you phone, then boot it up while holding power + vol down) and select hboot if it doesn't do that automatically.
Follow the prompts (vol up to flash ~ power to reboot)
That's it. Super easy.
Make sure to delete the renamed file from your extSD, otherwise every time you boot to hboot, it'll try to update again.

xunholyx said:
That's not how to flash an RUU.zip
This is how it is done.
Make sure that your extSD is formatted to FAT32 first. It won't work otherwise.
After the format, rename the zip to 0P6BIMG.zip (that's a zero, not the letter) and place it onto the root of your card.
Boot into bootloader (Turn off you phone, then boot it up while holding power + vol down) and select hboot if it doesn't do that automatically.
Follow the prompts (vol up to flash ~ power to reboot)
That's it. Super easy.
Make sure to delete the renamed file from your extSD, otherwise every time you boot to hboot, it'll try to update again.
Click to expand...
Click to collapse
Hello, thank you for your reply, I was traveling for holidays and have been working on the phone for the past couple of days and have run into alot of trouble doing what you say here, any help would be greatly appreciated I'm at the end of my rope with this phone. I got the 0P6BIMG.zip RUU and loaded it onto my Fat.32 formatted SD Card , I loaded the card into the phone and followed the fastboot options to flash, it recognized the RUU and attempted to flash it but said the model ID was incorrect. I opened up the zip and sure enough the android-info.txt file in the RUU does not list my model number and I cannot put my model number into it because it is an htc encrypted zip that will not let me change the file properties of the archive. I thought about trying to put the HTC into developer kernel so that my model ID would line up with that of the RUU info file but I did something (don't know what I did) and now fastboot won't even recognize the device (fastboot devices command shows nothing when phone is in fastboot USB mode).
My mid is 0P6B20000
My cid is VZW_001

Gitnerd said:
Hello, thank you for your reply, I was traveling for holidays and have been working on the phone for the past couple of days and have run into alot of trouble doing what you say here, any help would be greatly appreciated I'm at the end of my rope with this phone. I got the 0P6BIMG.zip RUU and loaded it onto my Fat.32 formatted SD Card , I loaded the card into the phone and followed the fastboot options to flash, it recognized the RUU and attempted to flash it but said the model ID was incorrect. I opened up the zip and sure enough the android-info.txt file in the RUU does not list my model number and I cannot put my model number into it because it is an htc encrypted zip that will not let me change the file properties of the archive. I thought about trying to put the HTC into developer kernel so that my model ID would line up with that of the RUU info file but I did something (don't know what I did) and now fastboot won't even recognize the device (fastboot devices command shows nothing when phone is in fastboot USB mode).
My mid is 0P6B20000
My cid is VZW_001
Click to expand...
Click to collapse
You need to use this RUU.zip
It is for the Verizon model

xunholyx said:
You need to use this RUU.zip
It is for the Verizon model
Click to expand...
Click to collapse
My goodness, I looked for this RUU everywhere, I would type in my mid and cid into google, I checked the One m8 archive of RUU's in that XDA thread, I couldn't find it. I don't know how you did, but you just saved my phone! Im booted into Android 4.4.2, receiving texts and everything. I'll figure out if I'm safe to update android later, I'm just so happy to have a working phone again. I gave you a thanks but do you have a contribution link or anything I could give to? You have helped me out tremendously.

Gitnerd said:
My goodness, I looked for this RUU everywhere, I would type in my mid and cid into google, I checked the One m8 archive of RUU's in that XDA thread, I couldn't find it. I don't know how you did, but you just saved my phone! Im booted into Android 4.4.2, receiving texts and everything. I'll figure out if I'm safe to update android later, I'm just so happy to have a working phone again. I gave you a thanks but do you have a contribution link or anything I could give to? You have helped me out tremendously.
Click to expand...
Click to collapse
I gave you an old RUU link. Sorry.
You can get the 5.0.1 RUU.zip from here if you want to update. It would be good to do it now, since running the RUU wipes your device, and yours is already wiped.
I've sent a PM with a donation link.
Thank you!

[Brick phone] help needed

I have flashed many phones before my G4 and this is the first time I'm having to ask for help.
The firmware installed was AICP CM13, then the screen went green with a DemiGod message. I held the vol down button to reboot and it came back up. After a few restarts and green screens i figured I needed to reflash the firmware. I booted into Recovery and while wiping the device to flash a new firmware, TWRP crashed. After leaving it for half hour or so, I took the battery out to enter into TWRP so I can flash the new firmware. TWRP is no there to be seen. I hold down the vol down and power button, releasing power for second or two and choose to go into recovery. Every time the phone just gets stuck on the LG screen displaying "Bootloader state :Bootlader unlocked!".
In short, I have no firmware, the device has been wiped and TWRP doesn't seem to be working.
I have tried to flash a KDZ file (H81520A_00.kdz) using the flash guide here. This comes back as unsuccessful saying "connection to server failed". As shown below.
View attachment 3605673
The method to flash an .img file using cmd on the pc includes moving the 4gb .img file to the parent folder of the phone storage. I can't get to move any files whatsoever to my device so figured this method would not work.
Seems if I can somehow flash TWRP, then I should be able to install a new firmware.
Any help much appreciated.

Hi, Can you get an ADB connection to your phone, or get your phone into bootloader somehow. From there you could try 'fastboot boot recovery.img'?
If so, then from within TWRP you can flash twrp recovery so the recovery is then sorted. Then you could flash click here (the full version). This will then allow LG UP to find a connection. From there if you really wanted to can flash any KDZ as a proper reset. Hope it works buddy!!

rav101 said:
Hi, Can you get an ADB connection to your phone, or get your phone into bootloader somehow. From there you could try 'fastboot boot recovery.img'?
If so, then from within TWRP you can flash twrp recovery so the recovery is then sorted. Then you could flash click here (the full version). This will then allow LG UP to find a connection. From there if you really wanted to can flash any KDZ as a proper reset. Hope it works buddy!!
Click to expand...
Click to collapse
I can get into recovery but I am unsure as to how I could try 'fastboot boot recovery.img'. Would that be the same as flashing an img when the root method first came out?

AndHD2 said:
I can get into recovery but I am unsure as to how I could try 'fastboot boot recovery.img'. Would that be the same as flashing an img when the root method first came out?
Click to expand...
Click to collapse
Just to make sure you know. TWRP is your recovery. Your last message said you did not have TWRP?
When I first rooted my phone (and subsequently when I install a .kdz), I have to go into the bootloader and install TWRP. I personally do this by using the above command "fastboot boot recovery.img" with the recovery.img being placed on my computer in the same location as my adb installation. This command only boots up TWRP but does not flash it. I then flash twrp by having a copy of it on my external sd card. Within twrp you can select to flash zip, or there is an option to flash an image. I use this to flash twrp (from twrp... its a little inception like but it works). Once you have twrp up and running, you can install a rom. If you want to do flash a .kdz, I have found you need to be on a stock based rom in the first place hence why i referenced the v20a full system zip.
Hope that made sense.
Regards,
Ravi

It is late here and with me being tired I said recovery instead of download. I can boot into download mode but when I try to boot into recovery then it just goes straight to the LG splash screen and it will either remain in that screen or the green Demigod screen would come up.
I'm off to sleep and away from my laptop as I have to be up in 5 hours. Luckily I still have my Note 4 so at least I'm not without a phone in the morning. I will try the steps what you have suggested just as soon as I get back from work.
Many thanks

rav101 said:
Just to make sure you know. TWRP is your recovery. Your last message said you did not have TWRP?
When I first rooted my phone (and subsequently when I install a .kdz), I have to go into the bootloader and install TWRP. I personally do this by using the above command "fastboot boot recovery.img" with the recovery.img being placed on my computer in the same location as my adb installation. This command only boots up TWRP but does not flash it. I then flash twrp by having a copy of it on my external sd card. Within twrp you can select to flash zip, or there is an option to flash an image. I use this to flash twrp (from twrp... its a little inception like but it works). Once you have twrp up and running, you can install a rom. If you want to do flash a .kdz, I have found you need to be on a stock based rom in the first place hence why i referenced the v20a full system zip.
Hope that made sense.
Regards,
Ravi
Click to expand...
Click to collapse
I have finally got chance to sit down and have a go at performing the procedure listed above. I downloaded the adb and fastboot installation as outline here. It is the minimum to what this thread says I will need for my device. I moved the recovery.img to the installation location which were in Windows/programs files (x86)/Minimal adb and fastboot. I launched the program and typed in 'fastboot boot recovery.img'. I tried this in download mode, charging mode (phone off) and while on the LG flash screen where TWRP didnt load but in all cases I have had no response at all.
If someone can help the much appreciated.

AndHD2 said:
I have finally got chance to sit down and have a go at performing the procedure listed above. I downloaded the adb and fastboot installation as outline here. It is the minimum to what this thread says I will need for my device. I moved the recovery.img to the installation location which were in Windows/programs files (x86)/Minimal adb and fastboot. I launched the program and typed in 'fastboot boot recovery.img'. I tried this in download mode, charging mode (phone off) and while on the LG flash screen where TWRP didnt load but in all cases I have had no response at all.
If someone can help the much appreciated.
Click to expand...
Click to collapse
Hi @AndHD2, I'm sorry but I can't think of anything else

rav101 said:
Hi @AndHD2, I'm sorry but I can't think of anything else
Click to expand...
Click to collapse
I had another demigod type screen but this was grey and not green with less detail. However it did say it were a kernel error.
Is the handset still under warrenty with the bootloader unlocked. I have a feeling its not

Stuck in Bootloader, cant boot recovery. Help save my phone.

So I was flashing a new rom (ICE Rom) for my htc m9. I flashed it without wiping the data and the process was successful without any errors. When i tried to reboot the phone it took me to the bootloader. All i could do was switch between recovery, bootloader and download mode. I tried to reflash the rom but the recovery kept restarting as soon as i press the button to flash, as if it was crashing. I thought, maybe if i update the recovery i could flash the zip. I tried to update recovery from bootloader but i couldn't since my device is S-ON. So being me, a gigantic wannabe android dev, went to the RUU and flashed the recovery img. And now when I try to access the recovery it gives me an error, "Failed to boot to recovery mode". I also believe that i might have accidentally deleted the OS, but I am not sure about that. Really need HELP. PLEASE.
Summary:
HTC M9
Unlocked
S-ON
Cant access recovery
Can access RUU, Bootloader, Download mode.
-------------------------------------------------------
Edit: I flashed the oldest possible twrp recovery image and was able to access the recovery after that. Only need to find a way to fix the other problem.

What is your firmware version? If you tried to install a Marshmallow based ROM without upgrading the firmware, that might explain your symptoms.

computerslayer said:
What is your firmware version? If you tried to install a Marshmallow based ROM without upgrading the firmware, that might explain your symptoms.
Click to expand...
Click to collapse
I am not sure about the firmware version but I flashed a updated version of my previous rom, and now i can boot normally. Not sure what the issue was. Both the roms are marshmallow. Any ideas what the problem could have been?

Yea. Messed up boot and recovery cache versions, as well as maybe a broken recovery partition.
You messaged me in private saying you had the same issue as the other dude. If that was the case, he has a bad NAND chip pretty sure.
For now, I doubt that is the case on your phone. However, should you end up with a broken recovery that wasn't flashed fully or was and then went to sh!t later, that could be an indicator for a bad NAND too. Could. It can also be a number of other things like just bad flashing practice, bad flashing hardware (cable, ports, drivers, incompatible controller chips...) etc.
If I were you, I would see that I get my hands on a good, current RUU and run that.
Either as zip, which I would flash by using an SDCard, or by exe, which I would run on my PC with the phone connected and working drivers. The drivers are most safely obtained by installing HTC Sync Manager from here: http://www.htc.com/us/software/htc-sync-manager/.
US RUU's you will find here: http://www.htc.com/us/support/rom-downloads.html
For any other RUU, non-US, you will need to dig through XDA, Google Search, known sites such as AFH, Androidruu.com, ir-files....
The RUU would even out all partitions and get them into a reliable stock state. Then you could reflash TWRP afterwards and then a ROM. Viper preferably. Because that is my Team and I helped you

nukerdude50 said:
I am not sure about the firmware version but I flashed a updated version of my previous rom, and now i can boot normally. Not sure what the issue was. Both the roms are marshmallow. Any ideas what the problem could have been?
Click to expand...
Click to collapse
Bad flash, double check md5 and filesizes.
Beamed in by telepathy.