Database Info

[Q] Bootloop after rebooting

Well I've been having this problem for a while, my phone goes into a bootloop whenever I restart it. It shows the white HTC screen, goes black, then the white HTC screen...over and over again.
The only way I have found to get it to boot up normally is when I connect a USB cable to it
But if I remove the cable and reboot, I get the same problem again.
Any ideas? Has anyone had this happen before??

That may be a Hardware issue. They easiest way I can think of is to RUU back to Stock, and Reformat the SD Card. If it still does it, then it may be a Hardware related issue.

CNexus said:
Well I've been having this problem for a while, my phone goes into a bootloop whenever I restart it. It shows the white HTC screen, goes black, then the white HTC screen...over and over again.
The only way I have found to get it to boot up normally is when I connect a USB cable to it
But if I remove the cable and reboot, I get the same problem again.
Any ideas? Has anyone had this happen before??
Click to expand...
Click to collapse
I've had that happen a couple times but it was because it was something I did/flashed, I agree with prboy, ruu back and format memory card (save your stuff to the computer first)- I've forgotten to save first a couple times

prboy1969 said:
That may be a Hardware issue. They easiest way I can think of is to RUU back to Stock, and Reformat the SD Card. If it still does it, then it may be a Hardware related issue.
Click to expand...
Click to collapse
I'll definitely try that, I don't know if this shed anymore light on it but my sdcard doesn't mount through my phone anymore either...happened around the same time as the restarting thing
But I'll tr and see what happens, if not I'll just take it in to sprint, I know it can't be something I flashed, I've been on stock for a while because of my utility
Sent from my PG06100 using xda premium

I would start by Formatting the SD Card. Then if that doesn't resolve issue. Format the SD Card again, and then RUU. If at that point the issue is still present, it's time to take it in to Sprint. Out of curiosity, are you using a custom Kernel ? Reason I ask is that I've run across something slightly similar after Flashing an Experimental Kernel Dirty. Meaning I did not wipe Cache, or Dalvik before Flashing. Mind you this was a very long time ago, in my HERO days. But I seem to remember it acting sort of like the symptoms you described.

prboy1969 said:
I would start by Formatting the SD Card. Then if that doesn't resolve issue. Format the SD Card again, and then RUU. If at that point the issue is still present, it's time to take it in to Sprint. Out of curiosity, are you using a custom Kernel ? Reason I ask is that I've run across something slightly similar after Flashing an Experimental Kernel Dirty. Meaning I did not wipe Cache, or Dalvik before Flashing. Mind you this was a very long time ago, in my HERO days. But I seem to remember it acting sort of like the symptoms you described.
Click to expand...
Click to collapse
Nope, no custom anything. 100% stock 2.2 with temproot, but since I can't reboot its really permroot lol
Sent from my PG06100 using xda premium

Then I would defiantly try what I stated above. See if it can resolve the issue.

prboy1969 said:
Then I would defiantly try what I stated above. See if it can resolve the issue.
Click to expand...
Click to collapse
Will do
Sent from my PG06100 using xda premium

Getting the same issues. I've tried ruu through both the exe and pg06 img. Tried factory reset with no luck, in the stock recovery ive wiped everything with no luck also. It's read by fastboot and i can issue commands, flashing through fastboot just gives me a sig verification failure. I've tried every method i've found and none have worked. Happened after downgrading to 2.2. I got temproot and went to permroot to go into this. I used htcdev to unlock the bootloader and it was successful. I cant access my sdcard since flashing the 2.2 ruu reverted it to stock and i cant get into the system to disk drive it. It boots for about 3 seconds then reboots. If any of the mmcblk... commands were mistyped or something was done wrong, how would i go about checking or fixing them if thats even possible? Any help or leads would be amazing.
SPEEDY XF SHIP S-ON
HBOOT-0.93.0001
RADIO-1.07.00.1129
eMMC-boot

KiDxNinja said:
Getting the same issues. I've tried ruu through both the exe and pg06 img. Tried factory reset with no luck, in the stock recovery ive wiped everything with no luck also. It's read by fastboot and i can issue commands, flashing through fastboot just gives me a sig verification failure. I've tried every method i've found and none have worked. Happened after downgrading to 2.2. I got temproot and went to permroot to go into this. I used htcdev to unlock the bootloader and it was successful. I cant access my sdcard since flashing the 2.2 ruu reverted it to stock and i cant get into the system to disk drive it. It boots for about 3 seconds then reboots. If any of the mmcblk... commands were mistyped or something was done wrong, how would i go about checking or fixing them if thats even possible? Any help or leads would be amazing.
SPEEDY XF SHIP S-ON
HBOOT-0.93.0001
RADIO-1.07.00.1129
eMMC-boot
Click to expand...
Click to collapse
So at this point your just trying to run the RUU ? Or do you still want to achieve Root ?

prboy1969 said:
So at this point your just trying to run the RUU ? Or do you still want to achieve Root ?
Click to expand...
Click to collapse
I had temp root and in between gaining perm root this happened. Root does me no good if I'm boot looped and can't even adb. I'm trying to get the phone to boot. Or read through adb. I can't fast boot any of the partitions either so I'm basically stuck in limbo

KiDxNinja said:
I had temp root and in between gaining perm root this happened. Root does me no good if I'm boot looped and can't even adb. I'm trying to get the phone to boot. Or read through adb. I can't fast boot any of the partitions either so I'm basically stuck in limbo
Click to expand...
Click to collapse
Have you tried booting it up while connected to a USB cord? That works for me because my phone will otherwise go into a bootloop whenever I restart it
Sent from my PG06100 using xda premium

KiDxNinja said:
I had temp root and in between gaining perm root this happened. Root does me no good if I'm boot looped and can't even adb. I'm trying to get the phone to boot. Or read through adb. I can't fast boot any of the partitions either so I'm basically stuck in limbo
Click to expand...
Click to collapse
Are you trying the PG06IMG , or the RUU.exe ? Have you tried doing the 2.2 RUU.exe through Fastboot ?

prboy1969 said:
Are you trying the PG06IMG , or the RUU.exe ? Have you tried doing the 2.2 RUU.exe through Fastboot ?
Click to expand...
Click to collapse
Yes and Yes, read my first post -_-

KiDxNinja said:
Yes and Yes, read my first post -_-
Click to expand...
Click to collapse
Must have missed that somehow. My bad . But on to the issue at hand. I'm wondering if maybe your SD Card went wonky. I would remove the SD Card, format it. Load the PG06IMG back onto the Card, reinstall. Then try to flash it. Of course backup your card to the PC first.
TEAM MiK
MikROMs Since 3/13/11

prboy1969 said:
Must have missed that somehow. My bad . But on to the issue at hand. I'm wondering if maybe your SD Card went wonky. I would remove the SD Card, format it. Load the PG06IMG back onto the Card, reinstall. Then try to flash it. Of course backup your card to the PC first.
TEAM MiK
MikROMs Since 3/13/11
Click to expand...
Click to collapse
Tried this with same result. flashing through hboot works for the 2.2 ruu, but im still stuck in the bootloop.
I also tried flashing a custom recovery via hboot, but the pgo6img loads then doesnt ask me if i want to update or not. I have literally no idea where to go or what to check.

KiDxNinja said:
Tried this with same result. flashing through hboot works for the 2.2 ruu, but im still stuck in the bootloop.
I also tried flashing a custom recovery via hboot, but the pgo6img loads then doesnt ask me if i want to update or not. I have literally no idea where to go or what to check.
Click to expand...
Click to collapse
Its not pgo6img. Its PG06IMG.zip. its a zero before the 6 not the letter "o". Idk if capitalized letters matter or not but I always capitalize all the letters
Sent from my EVO using Tapatalk 2

YoungCorruptionV2.0 said:
Its not pgo6img. Its PG06IMG.zip. its a zero before the 6 not the letter "o". Idk if capitalized letters matter or not but I always capitalize all the letters
Sent from my EVO using Tapatalk 2
Click to expand...
Click to collapse
I was just about to say that, if the name of the file isn't correct, the bootloader won't pick it up.

Yeah i know, i was just too lazy to type it out. I know what im doing as far as general modding and flashing, and I actually managed to fix it. I'm not positive how but I used the unroot back to stock guide for the stock locked bootloader. After flashing it through hboot I tried the 2.3.4 RUU. Still bootlooped but I was at stock with locked bootloader. I then used htcdev to reunlock the bootloader and I was then able to flash partitions through fastboot. I flashed cwm and was able to adb through it. I basically just reran through the rooting phase and gained temproot. From here I redid the steps to engineer hboot and finally received s-off. After this it booted normally. I might be leaving steps out but if anyone needs specifics, just pm me and maybe I can figure it out again for you.
Sent from my PG06100 using Tapatalk 2

help with boot loop loop loop
hi
someone can help whit phone?
in summer i restart phone and it stuck in loop htc logo in white over and over agen
till batrtery go down and nothing happen when trying to charg only led was flashing
no to long ago i plug to charger ad phone torn back on, sd card was out
I turn it off put sd card back on phone turn back on, try to software update one and second time it go back to loop agen=[
rand battery down agen and it does not torn back on, to hboot
well it does if i play whit it holding power bottom volume down longer time
speed xe ship s-on
hboot-0.99.0001
radio-1.08.01.0111
emmc-boot
can some one give me step by step instruction?

[Q] Where to Access Hasoon2000 S-Off Tool?

I've spent hours searching for how to S-Off my device. I've been running CM 9 and then 10, but it seems like my problem with 10.1 is S-on.
Most searches come to someone recommending Hasoon2000s S-Off tool, and linking to the original thread at: http://forum.xda-developers.com/showthread.php?t=1696373&highlight=s+off
The problem is that the link in that original thread to download the S-Off Tool is no longer there. I've looked through Hasoon2000s other downloads, and while there is the all-in-one toolkit 2.0, there doesn't seem to be a way to do S-Off in that kit.
I'll probably settle for JuopunutBear's solution, but since everywhere I go people are swearing by Hasoon2000s, (and I used the all-in-one toolkit with great success), does anyone have any new direction to track down a downloadable version of the S-Off tool, or a way to access it, or is JuopunutBear's all that is left for some reason? I haven't found any posts saying why Hasoon2000's has been pulled?
Thanks!

If I were you I would stay away from toolkits altogether. Not because they are bad, only because you learn absolutely nothing from using them and usually come bomb the threads when **** hits the fan.
The wire trick is a fun little task to handle though so everything should be okay that way.
Sent from my Nexus 4 using Tapatalk 2

Toolkit
ArachnydZ28 said:
I've spent hours searching for how to S-Off my device. I've been running CM 9 and then 10, but it seems like my problem with 10.1 is S-on.
Most searches come to someone recommending Hasoon2000s S-Off tool, and linking to the original thread at: http://forum.xda-developers.com/showthread.php?t=1696373&highlight=s+off
The problem is that the link in that original thread to download the S-Off Tool is no longer there. I've looked through Hasoon2000s other downloads, and while there is the all-in-one toolkit 2.0, there doesn't seem to be a way to do S-Off in that kit.
I'll probably settle for JuopunutBear's solution, but since everywhere I go people are swearing by Hasoon2000s, (and I used the all-in-one toolkit with great success), does anyone have any new direction to track down a downloadable version of the S-Off tool, or a way to access it, or is JuopunutBear's all that is left for some reason? I haven't found any posts saying why Hasoon2000's has been pulled?
Thanks!
Click to expand...
Click to collapse
His toolkit is still there, just browse around a bit... or go here... http://d-h.st/users/hasoon2000/?fld_id=2818#files

acwest said:
His toolkit is still there, just browse around a bit... or go here...
Click to expand...
Click to collapse
Thanks for your help I appreciate it- That was the same place linked to above.
Thats his toolkit 2.0 which I used to unlock my phone, but it doesn't give the phone S-Off (or atleast I couldnt find a way to do it in the toolkit)
His S-Off toolkit can't be found anymore on the otherhand, and I've searched in depth. I've been trying for at least 6-8 hours to get S-Off. Now I have a semi-bricked phone. Every path I go down is a dead end and its driving me nuts!
I was going to try the wire trick, but it requires stock rom. I had backed up the stock rom but it won't load. I downloaded 2 PD15IMG.zip files but neither of them will load, recovery says "Bad" when I try to run the .zip files. Did a little research. I think I need to do it via fastboot for the PD15IMG.zip files. Trying to figure that out now. Warnings seem pretty dire about trying to do it on a non-stock rom
This is getting above my head but I'm working my best to figure it out. Worst comes to worse I'll just have to order a new phone! I hate to be the novice that ends up being a PITA, as I've dealt with them plenty on the car forums I'm active on. I'd like to apologize up front for being "that guy".

Whats your situation now, do you have a recovery? What does it all say on your bootloader screen? Write that all down here
Sent from my Nexus 7 using xda premium

demkantor said:
Whats your situation now, do you have a recovery? What does it all say on your bootloader screen? Write that all down here
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
unlocked
Doubleshot PVT Ship S-On RL
Hboot- 1.45.0013
Microp-0353
eMMC-Boot
Nov 21 2011, 20:20:47
I do have recovery and hboot. Stock backup won't load though even though the file is there in recovery.
Thanks!

And what if you were to try and flash another rom, like miktouch, through recovery?
Sent from my MyTouch 4G Slide using xda premium

demkantor said:
And what if you were to try and flash another rom, like miktouch, through recovery?
Sent from my MyTouch 4G Slide using xda premium
Click to expand...
Click to collapse
I was able to reflash a version of CM10 I was using for a while and that works, but I can't find a stock one that will work. I've tried multiple, and they all give me "bad" error and don't finish the install.
I was going to try a different version of CM10, 10.1, or go to a stable release of 9. If none of those worked, I'd be happier with stock. None of the ones I've tried will work, but I'm assuming thats because I'm S-On, but since I can't find hasoon2000s S-Off tool everyone was raving about, and the wire trick requires stock ROM based on what the directions say, I find myself in a pickle.
The CM10 version I have can't do some basic things I need for work- like sync with my bluetooth in the car or not randomly freeze up during the day without me knowing it sending all my calls to voicemail. I tried versions of the others that other people are using (like silverL's 10.1 and the CM-listed stable CM9) and neither would load.
Do I have a different issue? AKA are other people with S-On able to load those Roms? I can try miktouch too.
---
Also trying to load via fastboot and I'm getting this error:
"Whoops: didn't find expected signature
read_central_directory_entry_failed
error: failed to access zipdata in [Whole bunch of non-english characters taking up a few lines]"
----
Update: Just to clarify, when I try to install a stock rom it gives me "Can't open [filename] (bad)
However, when I try to install the CM's, it installs fine and says "Install from sdcard complete" they just won't load when I restart my phone, except for the original version of CM10. (for example, in all the 10.1s I've tried I get "Unfortunately, the process com.android.phone has stopped" but the intro page will load. I figured that came down to an S-On issue when I tried to troubleshoot.

Any rom that is based off stock (like miktouch) should work to do the wire trick. I would check md5sums of the roms that won't flash to make sure they aren't corrupt at all. Also some say the latest twrp (and maybe other recoveries) won't flash some roms, so may need to change that as well
Sent from my MyTouch 4G Slide using xda premium

demkantor said:
Any rom that is based off stock (like miktouch) should work to do the wire trick. I would check md5sums of the roms that won't flash to make sure they aren't corrupt at all. Also some say the latest twrp (and maybe other recoveries) won't flash some roms, so may need to change that as well
Sent from my MyTouch 4G Slide using xda premium
Click to expand...
Click to collapse
Great, thanks!
I'll give miktouch a shot to see if I can use it for the wire trick. I'll let you know if it works.

ArachnydZ28 said:
Great, thanks!
I'll give miktouch a shot to see if I can use it for the wire trick. I'll let you know if it works.
Click to expand...
Click to collapse
negative.
miktouch would go through the install process, and end at the Tmobile mytouch 4g slide screen forever. I know on one install it took a long time to "load" the first time so I left it on this screen for about 15 minutes to no avail. Let me know if there is any chance of it taking longer than that. Reinstalls were the same story.
I got CM9.1 to install by installing it twice on top of itself (not sure why that fixes it) but it was a tiny bit buggy.
Is there any chance this could be bootloader related or recovery related? I can try to reload those too. grrr...

Its possible but if your bootloader can boot up one ROM it should be able to boot another. For this phone the only reason I have seen to change bootloaders is to unlock all the fastboot options. Flashing a new bootloader would reformat your partitions which may be the cause of your issue. Make sure you do a full wipe from recovery or fastboot -w or use a superwipe script, hell I tend to do all three between flashes but I'm kinda ocd when it comes to this, I hate debugging issues caused by residual effect from old data left after a dirty flash
But it may be worth it to flash a new recovery, not sure what you are using now but sometimes one will work when another doesn't, this would probably be my next step
Sent from my Nexus 7 using xda premium

demkantor said:
Its possible but if your bootloader can boot up one ROM it should be able to boot another. For this phone the only reason I have seen to change bootloaders is to unlock all the fastboot options. Flashing a new bootloader would reformat your partitions which may be the cause of your issue. Make sure you do a full wipe from recovery or fastboot -w or use a superwipe script, hell I tend to do all three between flashes but I'm kinda ocd when it comes to this, I hate debugging issues caused by residual effect from old data left after a dirty flash
But it may be worth it to flash a new recovery, not sure what you are using now but sometimes one will work when another doesn't, this would probably be my next step
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
I'm running CWM 5.5.0.4
I'll try to reload it or another version (I'm seeing some issues people have with 5504)
Thanks!

ArachnydZ28 said:
I'm running CWM 5.5.0.4
I'll try to reload it or another version (I'm seeing some issues people have with 5504)
Thanks!
Click to expand...
Click to collapse
You should try CWM 5.0.2.7. Also, since you are S-On you should extract the boot.img from Miktouch and flash it from fastboot, separately from the ROM. Since you have been on an ICS/Jellybean rom, I have to believe your original boot.img was replaced at some point. This is the only way to get back the Gingerbread boot.img. I am not savvy enough to know if this file is the bootloader or the kernel, but this process should get you back to stock-enough to do the wire trick.
Sent from my SGH-T699 using xda app-developers app

It's the kernel.....the boot.img file, I mean. The bootloader is that mostly white screen you see with "Hboot" at the top that will have "S-On" or "S-Off" after the word Radio. Good response.:good:

ArachnydZ28 said:
Thanks for your help I appreciate it- That was the same place linked to above.
Thats his toolkit 2.0 which I used to unlock my phone, but it doesn't give the phone S-Off (or atleast I couldnt find a way to do it in the toolkit)
His S-Off toolkit can't be found anymore on the otherhand, and I've searched in depth. I've been trying for at least 6-8 hours to get S-Off. Now I have a semi-bricked phone. Every path I go down is a dead end and its driving me nuts!
I was going to try the wire trick, but it requires stock rom. I had backed up the stock rom but it won't load. I downloaded 2 PD15IMG.zip files but neither of them will load, recovery says "Bad" when I try to run the .zip files. Did a little research. I think I need to do it via fastboot for the PD15IMG.zip files. Trying to figure that out now. Warnings seem pretty dire about trying to do it on a non-stock rom
This is getting above my head but I'm working my best to figure it out. Worst comes to worse I'll just have to order a new phone! I hate to be the novice that ends up being a PITA, as I've dealt with them plenty on the car forums I'm active on. I'd like to apologize up front for being "that guy".
Click to expand...
Click to collapse
Load the pd15img.zip on your sd card and boot to your bootloader. It should detect the file on your card and ask if you want to flash it. Just follow the directiins it gives you
Edit: actually should be pd59img not 15
Sent from my SGH-T889 using Tapatalk 2

[Q] AT&T HTC One X Soft Brick. Tried everything I could find. Suggestions?

So my AT&T HTC One X is bootloader unlocked, super CID and was rooted. I installed a copy of Viper XL 4.2.0 that had issues with the radio turning off so I thought I'd try Maximus HD. I flashed the boot.img and went to install the rom only to find that the rom was for the international version of the HTC One X only (this was conveniently overlooked in the thread). I backed out of installation, went to restore with my TWRP backup and it had been deleted. I reinstalled the Viper XL rom and my phone booted up to the HTC developers screen (red text) and went black. This now happens every time I try to boot the phone up.
I have access to fastboot and clockwork recovery. I can't get ADB to work as I don't have access to enable USB debugging. I have flashed a few roms since with their respective boot.img to no avail. The phone still just boots to the HTC screen and blacks out.
I don't have S-off and, from my research, I can't get it without ADB so I can't RUU and return to stock without bricking (apparently). I've been at this for about a month and this soft brick is starting to look a whole lot like a hard brick.
Any suggestions, or am I out of business?
Thanks in advance!

roycedavies said:
So my AT&T HTC One X is bootloader unlocked, super CID and was rooted. I installed a copy of Viper XL 4.2.0 that had issues with the radio turning off so I thought I'd try Maximus HD. I flashed the boot.img and went to install the rom only to find that the rom was for the international version of the HTC One X only (this was conveniently overlooked in the thread). I backed out of installation, went to restore with my TWRP backup and it had been deleted. I reinstalled the Viper XL rom and my phone booted up to the HTC developers screen (red text) and went black. This now happens every time I try to boot the phone up.
I have access to fastboot and clockwork recovery. I can't get ADB to work as I don't have access to enable USB debugging. I have flashed a few roms since with their respective boot.img to no avail. The phone still just boots to the HTC screen and blacks out.
I don't have S-off and, from my research, I can't get it without ADB so I can't RUU and return to stock without bricking (apparently). I've been at this for about a month and this soft brick is starting to look a whole lot like a hard brick.
Any suggestions, or am I out of business?
Thanks in advance!
Click to expand...
Click to collapse
Not sure if I can help you much but I did notice an important clue by what you said. It looks like you flashed the boot.img before flashing the Rom. This is backwards. You are supposed to flash the Rom first and then the boot.img. If you are not S-Off this will indeed cause problems. If you are still able and have the files on the phone, try flashing in that order and see if that clears it up. Oh and P.S. I'm sure you already are kicking yourself but yes, stick to Roms made for our phone in this forum.
Just noticed something else:
you said you had access to fastboot? Connect the phone and open a CMD prompt, navigate to your ADB/Fastboot folder (Where ever you keep your adb/fastboot tools) and then type "fastboot devices" to see if your computer is talking to your phone. If it is, you said you can flash Viper. you will just need to unzip the Viper zip and get the boot.img. Put that file in your ADB/Fastboot folder. open a CMD prompt again and navigate once again to you ADB/Fastboot folder, then type "fastboot flash boot boot.img and that should get you back on the road.
This is assuming you have a folder with the required ADB/Fastboot resources (if you don't I recommend you learn how) and knowledge on how to navigate to that folder with DOS commands.

roycedavies said:
So my AT&T HTC One X is bootloader unlocked, super CID and was rooted. I installed a copy of Viper XL 4.2.0 that had issues with the radio turning off so I thought I'd try Maximus HD. I flashed the boot.img and went to install the rom only to find that the rom was for the international version of the HTC One X only (this was conveniently overlooked in the thread). I backed out of installation, went to restore with my TWRP backup and it had been deleted. I reinstalled the Viper XL rom and my phone booted up to the HTC developers screen (red text) and went black. This now happens every time I try to boot the phone up.
I have access to fastboot and clockwork recovery. I can't get ADB to work as I don't have access to enable USB debugging. I have flashed a few roms since with their respective boot.img to no avail. The phone still just boots to the HTC screen and blacks out.
I don't have S-off and, from my research, I can't get it without ADB so I can't RUU and return to stock without bricking (apparently). I've been at this for about a month and this soft brick is starting to look a whole lot like a hard brick.
Any suggestions, or am I out of business?
Thanks in advance!
Click to expand...
Click to collapse
You said you flashed the boot.img from Maximus before flashing the ROM (which is ok, the previous member is incorrect in saying that it must be afterwards, it can be either), but did you flash the boot.img from the Viper XL ROM when you flashed that? If not your phone is trying to boot Viper while the Maximus boot.img is still installed, obviously this won't work.
One thing. The fact that Maximus ROM is only for the Endeavoru wasn't "conveniently overlooked" as you sarcastically put it. You were in the wrong forum. The ROM itself is in the Endeavoru forum and you have the Evita so you shouldn't be in the Endeavoru forum in the first place. The ROM is in the correct forum, it doesn't need to be labelled "Endeavoru only" because the user should be aware of which device they have and be aware of which forum they are in. The fact that you're bouncing around both forums is a bit of a worry. You have no reason to be in that forum.
Our forum is here:
http://forum.xda-developers.com/forumdisplay.php?f=1538
Our two development sections are here:
http://forum.xda-developers.com/forumdisplay.php?f=1541
http://forum.xda-developers.com/forumdisplay.php?f=1726
Stay within our device forum, you don't ever need to be anywhere else. You're pretty lucky you haven't actually bricked your phone by flashing that ROM. By the way, there's no such thing as a soft brick. A brick is when your phone will not power on at all. It's either bricked or it isn't.
Sent from my Evita

timmaaa said:
You said you flashed the boot.img from Maximus before flashing the ROM (which is ok, the previous member is incorrect in saying that it must be afterwards, it can be either), but did you flash the boot.img from the Viper XL ROM when you flashed that? If not your phone is trying to boot Viper while the Maximus boot.img is still installed, obviously this won't work.
One thing. The fact that Maximus ROM is only for the Endeavoru wasn't "conveniently overlooked" as you sarcastically put it. You were in the wrong forum. The ROM itself is in the Endeavoru forum and you have the Evita so you shouldn't be in the Endeavoru forum in the first place. The ROM is in the correct forum, it doesn't need to be labelled "Endeavoru only" because the user should be aware of which device they have and be aware of which forum they are in. The fact that you're bouncing around both forums is a bit of a worry. You have no reason to be in that forum.
Our forum is here:
http://forum.xda-developers.com/forumdisplay.php?f=1538
Our two development sections are here:
http://forum.xda-developers.com/forumdisplay.php?f=1541
http://forum.xda-developers.com/forumdisplay.php?f=1726
Stay within our device forum, you don't ever need to be anywhere else. You're pretty lucky you haven't actually bricked your phone by flashing that ROM. By the way, there's no such thing as a soft brick. A brick is when your phone will not power on at all. It's either bricked or it isn't.
Click to expand...
Click to collapse
Thanks for the reply. I believe the reason I'm not bricked is because I backed out of the installation of Maximus HD during the setup screen progression. The actual ROM was never flashed. However, I have flashed the boot.img and ROMs for Viper, Xylon, and Cyanogenmod with no success. The result is the same every time (HTC screen, then black). I extract the boot.img from each of the roms, flash it, and then flash the ROM. The ROM I flash is a copy of the the original with the boot.img still inside. Perhaps I should be removing the boot.img if I am going to flash it separately in fastboot? And I realize that the threads are specific for certain phones now. It's all kind of a mess to get into at first.

I understanding that it can be a bit confusing at first, especially with the phones betting similarly named. But you know now so you shouldn't have this problem again. I believe you will probably need to run an RUU to get out of this mess, but I'll need to see your bootloader details first, just the first five lines.
Sent from my Evita

Madcat8686 said:
Not sure if I can help you much but I did notice an important clue by what you said. It looks like you flashed the boot.img before flashing the Rom. This is backwards. You are supposed to flash the Rom first and then the boot.img. If you are not S-Off this will indeed cause problems. If you are still able and have the files on the phone, try flashing in that order and see if that clears it up. Oh and P.S. I'm sure you already are kicking yourself but yes, stick to Roms made for our phone in this forum.
Just noticed something else:
you said you had access to fastboot? Connect the phone and open a CMD prompt, navigate to your ADB/Fastboot folder (Where ever you keep your adb/fastboot tools) and then type "fastboot devices" to see if your computer is talking to your phone. If it is, you said you can flash Viper. you will just need to unzip the Viper zip and get the boot.img. Put that file in your ADB/Fastboot folder. open a CMD prompt again and navigate once again to you ADB/Fastboot folder, then type "fastboot flash boot boot.img and that should get you back on the road.
This is assuming you have a folder with the required ADB/Fastboot resources (if you don't I recommend you learn how) and knowledge on how to navigate to that folder with DOS commands.
Click to expand...
Click to collapse
Dude, you are a golden-freaking genius. Your suggestion to flash the boot.img second did the trick! I'm currently running Uxylon! Hopefully things continue to work. Thank you, thank you, thank you.

Oh, that's great. Usually it shouldn't matter which order you flash in, but at least it got you out of trouble this time.
Sent from my Evita

roycedavies said:
Dude, you are a golden-freaking genius. Your suggestion to flash the boot.img second did the trick! I'm currently running Uxylon! Hopefully things continue to work. Thank you, thank you, thank you.
Click to expand...
Click to collapse
Actually I can't take credit for this. Timmaaa pointed out something I didn't know. You can flash them in either order (mind blown!) I've only see it one way. I learn a ton every day. @timmaaa pointed out you had the Maximus boot.img loaded. I think you just flashed over it and now you have the correct boot.img for the Rom you are running. Glad everything worked out for you and I learned something in the process too. Cheers!

Madcat8686 said:
Actually I can't take credit for this. Timmaaa pointed out something I didn't know. You can flash them in either order (mind blown!) I've only see it one way. I learn a ton every day. @timmaaa pointed out you had the Maximus boot.img loaded. I think you just flashed over it and now you have the correct boot.img for the Rom you are running. Glad everything worked out for you and I learned something in the process too. Cheers!
Click to expand...
Click to collapse
Hey, you should take the credit, I believe flashing it afterwards was what got his phone booted :thumbup:
Sent from my Evita

Madcat8686 said:
Actually I can't take credit for this. Timmaaa pointed out something I didn't know. You can flash them in either order (mind blown!) I've only see it one way. I learn a ton every day. @timmaaa pointed out you had the Maximus boot.img loaded. I think you just flashed over it and now you have the correct boot.img for the Rom you are running. Glad everything worked out for you and I learned something in the process too. Cheers!
Click to expand...
Click to collapse
thanks again for your help and this might be a total shot in the dark but I am still having the boot to black issue after installing uxylon. the room is running well enough (4g won't turn on but one problem at a time) but every time I turn the phone off or rent I have to get into fastboot and flash the boot.img to get the phone on again. is that normal? the only other ROM I have ever had working is viper but I haven't seen any indication that having to use fastboot to turn the phone on every time is normal. is there a way to fix this possibly?

timmaaa said:
I understanding that it can be a bit confusing at first, especially with the phones betting similarly named. But you know now so you shouldn't have this problem again. I believe you will probably need to run an RUU to get out of this mess, but I'll need to see your bootloader details first, just the first five lines.
Sent from my Evita
Click to expand...
Click to collapse
Thanks for the reply! I will get the bootloader info ASAP bit don't I need to be s-of in order to RUU? from what I've read, if you don't have unlocked bootloader, root access, and s-off, you'll end up bricking your phone with RUU. I'd really like to do it but I have tried to get s-off to no avail.

No, that isn't normal at all, there's definitely something screwy there. I think you're gonna need to run an RUU, so you'll need to get s-off. Try this:
Http://Rumrunner.us
Sent from my Evita

roycedavies said:
thanks again for your help and this might be a total shot in the dark but I am still having the boot to black issue after installing uxylon. the room is running well enough (4g won't turn on but one problem at a time) but every time I turn the phone off or rent I have to get into fastboot and flash the boot.img to get the phone on again. is that normal? the only other ROM I have ever had working is viper but I haven't seen any indication that having to use fastboot to turn the phone on every time is normal. is there a way to fix this possibly?
Click to expand...
Click to collapse
Definitely not normal. A few recommendations:
1. Back up all your stuff, wipe everything except the SD card, Flash a fresh copy of the Rom, Flash the boot.img (you really should consider S-Off), Wipe the cache and DALVIK cache one more time, boot up the system.
2. Same as above except choose another Rom. There are plenty to choose from. The 4.4 Roms are getting a lot better now that the new Kernel fix got rid of the boot loops/reboots.
Sorry about the delay, it's been a heavy week at work. Hope things work out for you.

I don't think flashing another ROM is going to fix the problem at hand. There's very possibly something much deeper wrong here, which a ROM flash won't fix. I honestly think it's better to run an RUU which will bring everything back to the way it's meant to be and the user can start with a blank slate.
Sent from my One XL using XDA Premium 4 mobile app

timmaaa said:
No, that isn't normal at all, there's definitely something screwy there. I think you're gonna need to run an RUU, so you'll need to get s-off. Try this:
Http://Rumrunner.us
Sent from my Evita
Click to expand...
Click to collapse
Sometimes is pays to see if there is a page 2 to the thread...Sorry about that! lol
---------- Post added at 08:48 PM ---------- Previous post was at 08:45 PM ----------
timmaaa said:
I don't think flashing another ROM is going to fix the problem at hand. There's very possibly something much deeper wrong here, which a ROM flash won't fix. I honestly think it's better to run an RUU which will bring everything back to the way it's meant to be and the user can start with a blank slate.
Sent from my One XL using XDA Premium 4 mobile app
Click to expand...
Click to collapse
You have no idea how much I have vicariously learned from your posts. Thanks Timmaa! I keep thinking if more of these folks would go ahead and get S-Off they would have waaaaaaaaaay less issues.

Flashing another ROM could be worth a try, but the fact that the boot.img seems to be disappearing whenever the screen is off suggest something has gone wrong at a lower level.
I'm glad to help, I'm still learning something new just about every day too from XDA.
Sent from my One XL using XDA Premium 4 mobile app

timmaaa said:
Flashing another ROM could be worth a try, but the fact that the boot.img seems to be disappearing whenever the screen is off suggest something has gone wrong at a lower level.
I'm glad to help, I'm still learning something new just about every day too from XDA.
Sent from my One XL using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I totally agree now because after rereading the post, there is a radio issue in addition to the boot issue. Is it possible that the Endeverou boot.img messed something up?

Yeah, that's exactly what I'm thinking. An RUU will hopefully fix that right up.
Sent from my Evita.

timmaaa said:
No, that isn't normal at all, there's definitely something screwy there. I think you're gonna need to run an RUU, so you'll need to get s-off. Try this:
Http://Rumrunner.us
Sent from my Evita
Click to expand...
Click to collapse
That sounds like a good plan. (I'm really appreciating all your input by the way! Thanks so much!) One question though, upon checking out the rumrunner website, there isn't specific mention of the HTC One X Evita. Call me paranoid, but after what I've been through I want to make 100% sure I'm compatible before moving forward. Have you or anyone used this specific method for S-Off on the One X Evita?

For the Evita you use the universal HTC method. I've created a thread for it if you want to make sure it's worked for other Evita owners.
http://forum.xda-developers.com/showthread.php?t=2540232
Sent from my Evita.

[SOLVED] Flashing light, no screen...Help appreciated!

Hi All!
Recently i flashed TWRP and Cynogenmod 10.2.1 stable to my HTC Telestra One XL (evita)
I unlocked boot-loader
I successfully rooted
But I shut down once, and when i tried to boot, it got stuck in a boot-loop
Upon many retries, it suddenly wont turn on
when I charge it it only has a flashing red light but it wont even turn on, no screen not buttons; nothing!
And if I plug it in to my PC, the pc keeps sounding the USB Connected sound multiple times over a short period of 30 seconds to 2 minutes and then it gives off multiple shaky beeps
I hope this is enough info to let anyone help out!
Thank You in Advance
EDIT:
when connected to a pc it shows drivers is ready to use but tries to install QHUSB_DLOAD but fails and latest RUU does not detect
Thx again

What is the exact full filename of the ROM zip that you flashed? When a device is showing up as QHSUSB_DLOAD in Windows it usually means it's bricked.
Sent from my Evita

timmaaa said:
What is the exact full filename of the ROM zip that you flashed? When a device is showing up as QHSUSB_DLOAD in Windows it usually means it's bricked.
Sent from my Evita
Click to expand...
Click to collapse
Just found out:
a friend of mine tried to flash a file named "cm-10.0.0-evita" and it gave off a message saying that this phone is not rooted or missing supersu/ something along those lines
before that he wiped sd card (whole thing)...
and then it went off from there
NOTE: its a phone with mess with, but still want to fix even though its just a side phone we barely use....help appreciated

So does it power on at all?
Sent from my Evita

timmaaa said:
So does it power on at all?
Sent from my Evita
Click to expand...
Click to collapse
nope
when plugged in it only has a red LED that flashes once every once in a while and thats it
pc recognises it but wants to install qhusb_dload (as mentioned) and it just sais no driver found
i am researching and i found something called a "RIFF Box" but unsure if its worth it, plus i dont know where to jtag it (if its possible at all)
PS: hi from sydney!

Al-Dazzlez said:
Just found out:
a friend of mine tried to flash a file named "cm-10.0.0-evita" and it gave off a message saying that this phone is not rooted or missing supersu/ something along those lines
before that he wiped sd card (whole thing)...
and then it went off from there
NOTE: its a phone with mess with, but still want to fix even though its just a side phone we barely use....help appreciated
Click to expand...
Click to collapse
How did he try to flash it -_- these vague responses make it very hard to help. Bottom line is you can try pressing and holding power until the light goes off and then power and volume down to get the bootloader up, if that doesn't work you can try the evita jet tool to try to unbrick it. Bricks such as yours are not recoverable 9 times out of 10.

It looks like your only option is to get a jtag repair done. I wouldn't bother trying to do it yourself unless you're a fully experienced electronic engineer or the like. I'm not sure how many jtag repairers there are in Australia but I'm guessing Google should be able to reveal that information. Howdy from Melbourne.
Sent from my Evita

Hi from Canada!... I just wanted to be part of the greetings.. :laugh:

exad said:
How did he try to flash it -_- these vague responses make it very hard to help. Bottom line is you can try pressing and holding power until the light goes off and then power and volume down to get the bootloader up, if that doesn't work you can try the evita jet tool to try to unbrick it. Bricks such as yours are not recoverable 9 times out of 10.
Click to expand...
Click to collapse
he placed the cyanogen mod on the phones sd card, then he wiped sd card, after that he used the install function on twrp it gave him a message that his phone is not rooted and if he would like to root it, he accepted, then it rebooted into twrp, and he tried again to install, same message appeared and then he gave up and shut it down...(sorry for vague terms, please bear with me, still trying to learn the ropes of talking on this forum)

I gotta say, this is all very odd :/ How did he install anything if he wiped the SD card after copying it over? :/ hmmmm In any case, you CAN try he jet tool as per my last post before getting a jtag. You'll need a linux install or Bootable USB stick/CD/DVD though.

My guess is that the only thing he installed was SuperSU. That'd be why it booted straight back into TWRP.
Sent from my Evita

timmaaa said:
It looks like your only option is to get a jtag repair done. I wouldn't bother trying to do it yourself unless you're a fully experienced electronic engineer or the like. I'm not sure how many jtag repairers there are in Australia but I'm guessing Google should be able to reveal that information. Howdy from Melbourne.
Sent from my Evita
Click to expand...
Click to collapse
i researched..nothing..just some videos of people who do it (jtag)in the US and US only......
but still asking 'round the shops wont hurt i guess:laugh:
ill keep ya posted about using that tool you mentioned!
and exad; SUP!
and yeah.. it sounds weird to me too but i mainly play around with stuff like the galaxy series samsung's so the htc stuff is still new...and i have to admit...i am hating it so far.... but still experience cant hurt :laugh:

Hi guys!
im back
I JTAG'd the phone overseas, and it came back, surely enough, working, but now another problem arises,
the guy apparently unlocked the bootloader, S-Off, and installed CM with android 4.3.1. the phone boots, everything is well, but for times from 10 seconds to minutes of usage it just turns off, the Hboot shows
***tampered***
***relocked***
any idea wth is wrong with it now?
it does not reboot from power menu, and does not do anything really since I cant keep it on for more than a few minutes at most. I cannot keep it on long enough to unlock the bootlaoder anymore, and I cannot boot into TWRP (as the guy told me he put it on)
da hell do I Do now? any help appreciated

Try an RUU, any Evita RUU is fine if you have s-off.
Sent from my Evita

timmaaa said:
Try an RUU, any Evita RUU is fine if you have s-off.
Sent from my Evita
Click to expand...
Click to collapse
Thank you, tried but it did not pick up, but:
UPDATE:
I booted into teamwin, and flashed a CM11snapshot (latest one) everything seems fine so far (after 20 million dalvik and cache and factory restores) but now i am waiting for the problem to arise again, if not, ill have one problem left to fix....the back button does not work....
and now how the hell do i use an RUU on a custom frimware, ? (used it once on this phone but using a stock rom)
thanks again for your time timmaaa, seriously appreciated

Al-Dazzlez said:
Thank you, tried but it did not pick up, but:
UPDATE:
I booted into teamwin, and flashed a CM11snapshot (latest one) everything seems fine so far (after 20 million dalvik and cache and factory restores) but now i am waiting for the problem to arise again, if not, ill have one problem left to fix....the back button does not work....
and now how the hell do i use an RUU on a custom frimware, ? (used it once on this phone but using a stock rom)
thanks again for your time timmaaa, seriously appreciated
Click to expand...
Click to collapse
There's only one way to run an RUU, and that's to connect your phone and initiate the program in Windows. You're s-off so all security checks are disabled.
Sent from my Evita

timmaaa said:
There's only one way to run an RUU, and that's to connect your phone and initiate the program in Windows. You're s-off so all security checks are disabled.
Sent from my Evita
Click to expand...
Click to collapse
I Just ran one, Unlocked bootloader, on Cm11 snapshot after re-root and all that crap done, should be alright now

[Q] Cannot soff, devunlock or anything else

Hi guys!
First of all thank you for reading.
I'm probably in my 3rd day lurking around every possible forum and thread looking for an answer to my similar problem but have yet to find one.
I used to have a sensation xe but I kinda smashed the digitizer to bits. before that the was battery swollen and the back case pretty damaged (it survived a 120 kph gps reading of an rc car before going end over end across a parking lot). Meanwhile I got an Htc One, which is superb and I kinda forgot about the old gal.
A few days back I found a guy selling a sensation for spares (the mobo was fried on his) so I just bought that (for 20 euros) and figured all I needed to to was a mobo transplant and then have a nice almost new sensation.
But obviously the digitizer is not calibrated. I found the forum with the tutorial on that but it requires super CID and Soff. Cannot do either of them.
Since the mobo has been replaced the devunlock didn't work. Cannot, for the love of me succeed with the junopunutbear soff with the wire trick. Tried it on a ubuntu live cd, all goes well up until the wire trick. On a side note, I design and build 3d printers for a living, I might be a noob in the android department but that's about it. Even tried an automatic timed relay to do the two wire taps and still nothing. Obviously, it's not working on windows, I found the kgs1992 tool which requires a version of controlbear for windows which I cannot find (found one but it doesn't recognise it when I put it in the tools folder).
tl;dr
Cannot devunlock, cannot soff, nothing. Could I possibly try changing the IMEI so that i can maybe just maybe devunlock it first? I tried putting the mobo back in the old phone, still powered up but didn't recognize the token. I'm pretty much stuck right now.
Any help would be highly appreciated and if you read the whole thing, kudos to you for standing my chatter !

i sent you a pm
also you can follow this guide which avoids wire trick
http://forum.xda-developers.com/showthread.php?t=2751187

rzr86 said:
i sent you a pm
also you can follow this guide which avoids wire trick
http://forum.xda-developers.com/showthread.php?t=2751187
Click to expand...
Click to collapse
Hi mate!
Thank you so much for your reply!
Unfortunately, rumrunnes told me to f myself lol, an error about not finding an unsecure kernel I guess, too frustrated to remember what the error was after finally finding a piece of software which seemed to do something.
Will try with the link you sent me and will come back with results!

elktw said:
Hi mate!
Thank you so much for your reply!
Unfortunately, rumrunnes told me to f myself lol, an error about not finding an unsecure kernel I guess, too frustrated to remember what the error was after finally finding a piece of software which seemed to do something.
Will try with the link you sent me and will come back with results!
Click to expand...
Click to collapse
did it tell you to be rooted first?

rzr86 said:
did it tell you to be rooted first?
Click to expand...
Click to collapse
That it did, but I was under the assumption (well all the guides I read) that you need to be devunlocked in order to root it. which I can't do. Am I missing something or is this a vicious circle ?

elktw said:
That it did, but I was under the assumption (well all the guides I read) that you need to be devunlocked in order to root it. which I can't do. Am I missing something or is this a vicious circle ?
Click to expand...
Click to collapse
just use the temproot.bat file from juopunutbear thread
then run rumrunner again
it is mentioning also in rumrunner thread

Stuck on confirm Unlock bootloader
Ok, my phone got really messed up with TWRP format bug.
Since then, I have tried RUU, different recoveries and finally got stuck with Relocked, S-ON, no ROM, no ADB on my Sensation.
When i try to unlock via Unlock_code.bit i used earlier i am able to send it via fastboot to phone where it prompts me for a choice Yes/No.
And here is funny part.
I can select No with my power button which reboots my phone and shows white screen with bootloader after it since there is nothing on it.
But, when i press Volume up and select Yes option and Power button to confirm it, nothing happens. Actually it freezes phone and i have nothing else left to do except pulling out battery and booting to bootloader.
Since it is some kind of alive, I'm sure there is some way to revive it but I guess I'm kinda not seeing right steps to unlock it, s-off again, and custom recovery and wait for twrp team or shantur to find a sollution to fix corrupted partitions.
Can you help me with unlocking?
What logs do you need?

culler said:
Ok, my phone got really messed up with TWRP format bug.
Since then, I have tried RUU, different recoveries and finally got stuck with Relocked, S-ON, no ROM, no ADB on my Sensation.
When i try to unlock via Unlock_code.bit i used earlier i am able to send it via fastboot to phone where it prompts me for a choice Yes/No.
And here is funny part.
I can select No with my power button which reboots my phone and shows white screen with bootloader after it since there is nothing on it.
But, when i press Volume up and select Yes option and Power button to confirm it, nothing happens. Actually it freezes phone and i have nothing else left to do except pulling out battery and booting to bootloader.
Since it is some kind of alive, I'm sure there is some way to revive it but I guess I'm kinda not seeing right steps to unlock it, s-off again, and custom recovery and wait for twrp team or shantur to find a sollution to fix corrupted partitions.
Can you help me with unlocking?
What logs do you need?
Click to expand...
Click to collapse
Well, i can certainly try and tell you what I did. Basically listen to the wonderful advice of @rzr86. Assuming you have tried many tools, you probably have the temproot utility. I just used that and Rumrunners, no wire trick no nothing, those were pretty straightforward and I finally managed to soff and supercid it. Afterwards I just installed 4ext recovery and was finally able to install whatever custom rom I wanted.
My problem however is now a different one. Cannot calibrate the touchscreen using the 58diag file. I'm using cgmod11 and if I run the calibration file, it gets stuck in bootloader. Standard RUU and it does nothing at all for the touchscreen. I'm pretty much stuck and out of ideas.
Aaaanyway, try rumrunners with temproot and get back to me with the results !

elktw said:
Well, i can certainly try and tell you what I did. Basically listen to the wonderful advice of @rzr86. Assuming you have tried many tools, you probably have the temproot utility. I just used that and Rumrunners, no wire trick no nothing, those were pretty straightforward and I finally managed to soff and supercid it. Afterwards I just installed 4ext recovery and was finally able to install whatever custom rom I wanted.
My problem however is now a different one. Cannot calibrate the touchscreen using the 58diag file. I'm using cgmod11 and if I run the calibration file, it gets stuck in bootloader. Standard RUU and it does nothing at all for the touchscreen. I'm pretty much stuck and out of ideas.
Aaaanyway, try rumrunners with temproot and get back to me with the results !
Click to expand...
Click to collapse
Did you had access to rom and adb to run Rumrunners utility? I have only access to bootloader and when i try to run it it hangs waiting for ADB.
Also, I'm stuck on unlock bootloader screen so probably have corrupted memory because I can't unlock it. :/

culler said:
Did you had access to rom and adb to run Rumrunners utility? I have only access to bootloader and when i try to run it it hangs waiting for ADB.
Also, I'm stuck on unlock bootloader screen so probably have corrupted memory because I can't unlock it. :/
Click to expand...
Click to collapse
do you have adb/fastboot installed?
did you enable usb debugging mode from settings?
use usb 2.0 ports not 3.0
also what windows OS do you have?

rzr86 said:
do you have adb/fastboot installed?
did you enable usb debugging mode from settings?
use usb 2.0 ports not 3.0
also what windows OS do you have?
Click to expand...
Click to collapse
I'm on Windows 8.1 64-bit, but also tried Windows 7 32-bit and Ubuntu 13.04 both 32 and 64bit.
I also tried both USB2.0 and USB3.0 ports.
Like i said, I cant enable USB debugging mode in settings since i don't have ROM now, device is empty, except bootloader without recovery and I can't find way to install since I'm Relocked and S-on.

culler said:
I'm on Windows 8.1 64-bit, but also tried Windows 7 32-bit and Ubuntu 13.04 both 32 and 64bit.
I also tried both USB2.0 and USB3.0 ports.
Like i said, I cant enable USB debugging mode in settings since i don't have ROM now, device is empty, except bootloader without recovery and I can't find way to install since I'm Relocked and S-on.
Click to expand...
Click to collapse
S-OFF requires a working rom so you can't use S-OFF method
with windows 8.1 you will face connectivity issues
type in search box how to set up adb/fastboot in windows 8 but the point is that you don't have enabled usb debugging mode
so i am not sure if you will have any success
by the way what version of TWRP did you flash?
the latest? (2.7.0)

I was using TWRP 2.7.0.0 which corrupted my partitions so i tried various recoveries to fix the situation without success.
So I tried to RUU and it also failed.
Somewhere along the way of trying to revive my phone, i used fastboot oem lock and now i somehow have S-ON device which is RELOCKED and I have no custom recovery. I can't even access HTC recovery now.
When i try fastboot flash unlocktoken Unlock_code.bin from HTCDev it prompts me with screen to choose YES to unlock or NO to unlock.
When i choose YES with Volume button and press Power button to confirm, device freezes and stays like that forever, or until I remove battery.
Selecting no reboots device and brings me back to bootloader.
*** RELOCKED ***
*** Security Warning ***
PYRAMID PVT SHIP S-ON RL
HBOOT-1.29.0000
RADIO-11.24A.3504.31_M
OpenADSP-v05.6.0.2226.00.0418
eMMC-boot
Mar 2 2012,18:14:34

culler said:
I was using TWRP 2.7.0.0 which corrupted my partitions so i tried various recoveries to fix the situation without success.
So I tried to RUU and it also failed.
Somewhere along the way of trying to revive my phone, i used fastboot oem lock and now i somehow have S-ON device which is RELOCKED and I have no custom recovery. I can't even access HTC recovery now.
When i try fastboot flash unlocktoken Unlock_code.bin from HTCDev it prompts me with screen to choose YES to unlock or NO to unlock.
When i choose YES with Volume button and press Power button to confirm, device freezes and stays like that forever, or until I remove battery.
Selecting no reboots device and brings me back to bootloader.
*** RELOCKED ***
*** Security Warning ***
PYRAMID PVT SHIP S-ON RL
HBOOT-1.29.0000
RADIO-11.24A.3504.31_M
OpenADSP-v05.6.0.2226.00.0418
eMMC-boot
Mar 2 2012,18:14:34
Click to expand...
Click to collapse
i thibk you are stuck mate unfortunately
did you try unbricking project or jtag method?

rzr86 said:
i thibk you are stuck mate unfortunately
did you try unbricking project or jtag method?
Click to expand...
Click to collapse
I tried unbricking project but it hangs on start with connecting to device or waiting for device.
As I understood, it needs to access ADB which i cant succeed.
I dont have JTAG equipment so it goes to some service to see if they could repair it.
It's such a great device, i don't want to lose it so soon