Database Info

Qhsusb_dload

Just tried to install CWM using Recovery Mangaer APP. Now it wont boot and i get QHSUSB_DLOAD in device manager. Am i fubar'd or is this brick recoverable? TIA

probably just need to get someone to dump the recovery partition and flash it with odin

designgears said:
probably just need to get someone to dump the recovery partition and flash it with odin
Click to expand...
Click to collapse
Any suggestions on where to start? at least i'm glad it happened to me instead of they guy i recommended it to. He was looking for a way to install CWM without a computer.. I don't need anymore enemies :angel:

designgears said:
probably just need to get someone to dump the recovery partition and flash it with odin
Click to expand...
Click to collapse
any idea where i can fond the drivers for 64bit win 7?

got the drivers installed. have the mmcblk0p22.img. Whats next? lol

Have you tried to RUU? Since the drivers are installed.
Sent from my HTC One X using Tapatalk 2

kleeman7 said:
Have you tried to RUU? Since the drivers are installed.
Sent from my HTC One X using Tapatalk 2
Click to expand...
Click to collapse
no but i will. thanks.
Hunting Odin download now.

kleeman7 said:
Have you tried to RUU? Since the drivers are installed.
Sent from my HTC One X using Tapatalk 2
Click to expand...
Click to collapse
ruu doesn't see it

QHUSB_DLOAD mode usually means you bricked hard and unless you have some software that the rest of us mere mortals don't, you will need to warranty it.

looks like odin is for Samsung devices?
anyone have any ideas? Device manager now reads:
Qualcomm HS-USB QDloader 9008 (com 7)

Hunt3r.j2 said:
QHUSB_DLOAD mode usually means you bricked hard and unless you have some software that the rest of us mere mortals don't, you will need to warranty it.
Click to expand...
Click to collapse
Qualcomm tools people have been looking for? I saw a post somewhere here at XDA and the OP was talking about some Qualcom tool kit. The'yve also been talking about some qualcom tools in the s-off thread.. Same thing??

nugzo said:
Qualcomm tools people have been looking for? I saw a post somewhere here at XDA and the OP was talking about some Qualcom tool kit. The'yve also been talking about some qualcom tools in the s-off thread.. Same thing??
Click to expand...
Click to collapse
I dunno, but it was talked about in the Sensation Unbricking Project, it isn't easy to recover at all, and for most it's a lost cause....

Hunt3r.j2 said:
I dunno, but it was talked about in the Sensation Unbricking Project, it isn't easy to recover at all, and for most it's a lost cause....
Click to expand...
Click to collapse
Thank you. The only tools i could find was revskills. Dont know if that's what i need or not. 90% of that is over my head.

nugzo said:
looks like odin is for Samsung devices?
anyone have any ideas? Device manager now reads:
Qualcomm HS-USB QDloader 9008 (com 7)
Click to expand...
Click to collapse
Yes Odin is Samsung. Get in touch with the s-off guys they have been playing around with download mode and may be able to help.
Borrowed this maybe it throwing you into recovery may help, also they said fastboot flash works, maybe flash twrp from fastboot.
beaups said:
I tried the pg1fs. sig check failure. As a matter of fact doing "fastboot flash aksldjflkadsfjdlsk pg1fs.img" causes the same error, so something is in the img that causes sig check or any flash attempt except recovery is sig checked. Fastbook oem refurbish puts out a lot of interesting text, then reboots into recovery and looks for something (doesn't say what).on sd card (I tried copying IMG's to internal and external sd, no luck). Interesting thing about refurb command is it seems particularly "excited" about the fact that we have super CID - run it yourself and see, no harm is done (data, etc.). one recovery boots you can screw around with volume and power keys to see the text.
Click to expand...
Click to collapse
Sent from my HTC One X using Tapatalk 2

Just thought I'd mention this to the op, I saw the thread where you were trying to help someone else flash a recovery without a pc with all the best intentions and ended up bricking. It broke my heart...lol sounds mushy I know, but really. Best of luck getting it fixed up man.
Sent from my HTC One X using Tapatalk 2

anyone find solution?

initialz said:
anyone find solution?
Click to expand...
Click to collapse
Thanks for the three month necro, but once again, go to the S-OFF thread...

what version was the last ruu you ran before it bricked..

You are probably SOL.
Sent from my One X using xda app-developers app

When you turn your phone on the first (idk) seconds your in emmc mode which you can dd the hboot partition in to fix your phone. Read it a while back in the S-Off thread, seems like it worked.
Edit: Rewrote whole thing, remembered how
Sent from my HTC One XL using xda premium

Tip/warning rom manager recovery for htc one x (gsm)

I am creating this post as a tip and warning to everyone with an at&t htc one x (mostly noobs for help). If you have rom manager on your phone do not use it to flash the new recovery listed for the htc one x (gsm). I've been messing with android since 2009, but me seeing a new recovery for the one x with (gsm) next to it thought hey finally got an official clockwork recovery for our phones!!!!! Well i was wrong. Its for the international versions only not ours. The partition it writes the recovery to is on our bootloader partition, and flashing it will kill your phone. I flashed it, kept it on for hours but as soon as i rebooted the phone it turned off and would not turn on or charge. You'll pretty much be screwed and have to get a new phone unless you know how to run linux and ask for help fixing it which is harder than you think. Again do not flash the htc one x (gsm) recovery in rom manager!!!!!
Hope this helps some of you before hand and not after.
If this post isn't necessary i am sorry and please close it.

Nobody should ever use ROM Manager for anything, EVER.
Sorry for your loss.

Why would you flash a recovery for a different device and expect it to work?
When ROM manger is supported on your device its a great tool, like on the sgs2. If its not officilially supported on your device, don't mess with it.
Sent from my Nexus 7 using xda premium

nooomoto said:
Why would you flash a recovery for a different device and expect it to work?
When ROM manger is supported on your device its a great tool, like on the sgs2. If its not officilially supported on your device, don't mess with it.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
it was new on there at the time and with gsm next to i i figured it was for ours, anyway point is if i knew it wasnt for my phone i wouldnt have flashed it.

rob219 said:
it was new on there at the time and with gsm next to i i figured it was for ours, anyway point is if i knew it wasnt for my phone i wouldnt have flashed it.
Click to expand...
Click to collapse
in fact, it is not really that hard to fix. Just re-lock the phone via fastboot. then run RUU package from AT&T
It should set every thing back to original.
if your phone is not respond RUU, try reboot on RUU via fastboot.
By the way, The only recovery that works now is TWRP
Use this one only

sugeraddict said:
in fact, it is not really that hard to fix. Just re-lock the phone via fastboot. then run RUU package from AT&T
It should set every thing back to original.
if your phone is not respond RUU, try reboot on RUU via fastboot.
By the way, The only recovery that works now is TWRP
Use this one only
Click to expand...
Click to collapse
The ruu has to access the boot loader to verify your version. If you end up flashing a device and it writes certain partitions of your boot loader (ICJ).... Well your left with a permabrick, until someone finds a way to JTAG the One X(AT&T). I've heard that its already been done, but the person who has performed it has kept the pinout secret.
I'm not entirely sure which partitions your ROM manager has wrote to, if you can find that out you might be able to fix it... Depending on which ones have been written too.
Sent from my One X using xda app-developers app

Zombie thread alert!

Like many of us have said before. We are not the one x. We are the one XL.
Sent from my One X using xda app-developers app

_MetalHead_ said:
Nobody should ever use ROM Manager for anything, EVER.
Sorry for your loss.
Click to expand...
Click to collapse
Sorry, but I disagree!
I've had more problem locating backup files and restoring when in TWRP, than ROM manager!
Mike

MaverickCoast said:
Sorry, but I disagree!
I've had more problem locating backup files and restoring when in TWRP, than ROM manager!
Mike
Click to expand...
Click to collapse
You must be doing something wrong then. You don't even need to locate backups with TWRP, they're found automatically. Anyway, was it really necessary to revive an 18 month old thread just to say that?
Sent from my Evita

[Q] I may have just hardbricked my One X... o.O

I was installing a rom on my Rogers One X.
I can't post the link, but it is the "IceColdJelly AOKP ROM" posted recently on onexroot.com
EDIT: Found it on XDA. yes, it is for the international version
The instructions say:
To install, reboot into recovery, do data wipe/factory reset, install ROM, install Gapps, then extract boot.img from ROM zip file and flash with fastboot.
Click to expand...
Click to collapse
I did everything except for the last step, but then I accidentally rebooted the phone. Now my phone seems to be completely dead. I can't boot to the bootloader, I can't do anything. Even the charging light does not come on when I plug it into my PC.
When I plug it in to my PC it shows up as "Qualcomm QHSUSB_HBOOT" in the Windows device manager, but does not show up in adb, or fastboot.
Am I screwed??

Karvin said:
I was installing a rom on my Rogers One X.
I can't post the link, but it is the "IceColdJelly AOKP ROM" posted recently on onexroot.com
The instructions say:
I did everything except for the last step, but then I accidentally rebooted the phone. Now my phone seems to be completely dead. I can't boot to the bootloader, I can't do anything. Even the charging light does not come on when I plug it into my PC.
When I plug it in to my PC it shows up as "Qualcomm QHSUSB_HBOOT" in the Windows device manager, but does not show up in adb, or fastboot.
Am I screwed??
Click to expand...
Click to collapse
From the top of my head remembering front the HTC inspire that sounds like a lord clockan Rom...and I know he doesn't dev for us..now you successfully flashed a Rom for the tegra one x.... Which is bad..you might of hard bricked it

Karvin said:
I was installing a rom on my Rogers One X.
I can't post the link, but it is the "IceColdJelly AOKP ROM" posted recently on onexroot.com
The instructions say:
I did everything except for the last step, but then I accidentally rebooted the phone. Now my phone seems to be completely dead. I can't boot to the bootloader, I can't do anything. Even the charging light does not come on when I plug it into my PC.
When I plug it in to my PC it shows up as "Qualcomm QHSUSB_HBOOT" in the Windows device manager, but does not show up in adb, or fastboot.
Am I screwed??
Click to expand...
Click to collapse
Cannot stress this enough, do not flash anything that isn't posted in the dev sections of this forum...I believe IceColdJelly is for the international (Tegra 3) One X and you may have overwritten your boot sector and recovery. If you can't get the charging light to come on then you are most likely out of luck.

Karvin said:
I was installing a rom on my Rogers One X.
I can't post the link, but it is the "IceColdJelly AOKP ROM" posted recently on onexroot.com
The instructions say:
I did everything except for the last step, but then I accidentally rebooted the phone. Now my phone seems to be completely dead. I can't boot to the bootloader, I can't do anything. Even the charging light does not come on when I plug it into my PC.
When I plug it in to my PC it shows up as "Qualcomm QHSUSB_HBOOT" in the Windows device manager, but does not show up in adb, or fastboot.
Am I screwed??
Click to expand...
Click to collapse
Daaaaaaammmmn. Tssk tssk RESEARCH B4 flashing a ROM!. Ur phone prolly fried if it don't turn on for shiz like these fellas mention. Always be careful man don't just go all exited n flash a tegra rom :/
Sent from my HTC One XL using xda app-developers app

stnguyen09 said:
Cannot stress this enough, do not flash anything that isn't posted in the dev sections of this forum...I believe IceColdJelly is for the international (Tegra 3) One X and you may have overwritten your boot sector and recovery. If you can't get the charging light to come on then you are most likely out of luck.
Click to expand...
Click to collapse
But I have the Rogers One X, which I think is Telstra right?
Anyway, I found the rom's page on XDA:
http://forum.xda-developers.com/showthread.php?t=1796340
It is posted in the "HTC One X" forum, so that's not the Telstra version then, right?

Nevermind, I was mixed up about the versions. Yes, the rom is for the wrong version of the One X.
Thanks for the replies guys.
I was searching around and found this:
http://forum.xda-developers.com/showpost.php?p=30572793&postcount=12
just found out the one x international recovery flashes on the partition that on our phones is the boot loader partition. could be fixed inside of linux, but i didnt get into how.
Click to expand...
Click to collapse
Might be possible to fix in Linux? I've heard that using the linux-only tools, it is possible to write to a partition even when the bootloader is broken. Anybody ever heard of this?

Karvin said:
Nevermind, I was mixed up about the versions. Yes, the rom is for the wrong version of the One X.
Thanks for the replies guys.
I was searching around and found this:
http://forum.xda-developers.com/showpost.php?p=30572793&postcount=12
Might be possible to fix in Linux? I've heard that using the linux-only tools, it is possible to write to a partition even when the bootloader is broken. Anybody ever heard of this?
Click to expand...
Click to collapse
It overwrit your hboot I think....there was a post I think I saw u have to do something very quickly and restore your boot partitions...but I have no idea ..sorry

Another one bites the dust...

I'll buy it from u

Karvin said:
But I have the Rogers One X, which I think is Telstra right?
Click to expand...
Click to collapse
Rogers is Rogers, Telstra is Telstra. Telstra is an Australian carrier.
Seems like the OP had a fundamental lack of basic understanding of what they were even looking at when flashing ROMs, which is of course a no-no.

Tough crowd lol
I am well aware of the difference between my hoc and the international version. I got mixed up by the "Telstra" thing. I thought it was the same as the rogers/at&t version.
Sent from my X10i using xda app-developers app

Karvin said:
Tough crowd lol
I am well aware of the difference between my hoc and the international version. I got mixed up by the "Telstra" thing. I thought it was the same as the rogers/at&t version.
Click to expand...
Click to collapse
They are essentially the same. Rogers or Telstra makes no difference, they are both the Snapdragon S4 version of the One X/XL. ROMs are interchangeable. How did this have anything to do with flashing a ROM for the international version?
My main point of my previous post, if you are mixed up, confused, etc. about any aspect of what you are doing when flashing ROMs or doing other mods, STOP, DO NOT PROCEED. Figure it out before proceeding, as you see what the consequence of not doing so is . . . a sexy looking paperweight.

redpoint73 said:
They are essentially the same. Rogers or Telstra makes no difference, they are both the Snapdragon S4 version of the One X/XL. ROMs are interchangeable. How did this have anything to do with flashing a ROM for the international version?
My main point of my previous post, if you are mixed up, confused, etc. about any aspect of what you are doing when flashing ROMs or doing other mods, STOP, DO NOT PROCEED. Figure it out before proceeding, as you see what the consequence of not doing so is . . . a sexy looking paperweight.
Click to expand...
Click to collapse
Yes, obviously it was completely my bad... I'm not trying to blame anyone else.
This is has become a pointless discussion...

Phone won't boot after rom flash?

I got my one x last week and rooted it a few days ago via the all in one method found here ( http://forum.xda-developers.com/showthread.php?t=1952426 ) and everything worked including superuser. After a few days of use I decided to try the icecoldjelly aokp rom found here ( http://onexroot.com/one-x-roms/icecoldjelly-aokp-rom-for-rooted-one-x-android-4-1-2/ ). The rom flash said successfull and so did the gaps zip. Then when I pressed reboot the phone never cam back on. I tired living it charging overnight in case it lost charge (even though it showed almost full before I flashed). I'm not sure but I think I may be out luck?
Is there anything I can try to get this thing to boot up?

Ezence01 said:
I got my one x last week and rooted it a few days ago via the all in one method found here ( http://forum.xda-developers.com/showthread.php?t=1952426 ) and everything worked including superuser. After a few days of use I decided to try the icecoldjelly aokp rom found here ( http://onexroot.com/one-x-roms/icecoldjelly-aokp-rom-for-rooted-one-x-android-4-1-2/ ). The rom flash said successfull and so did the gaps zip. Then when I pressed reboot the phone never cam back on. I tired living it charging overnight in case it lost charge (even though it showed almost full before I flashed). I'm not sure but I think I may be out luck?
Is there anything I can try to get this thing to boot up?
Click to expand...
Click to collapse
You flashed an international ROM, you now probably have an expensive paperweight. Sorry, please read the stickies next time
You may be able to dd a partition 4 to your phone if someone dumps one for you, and if you know how/someone is willing to help.
First go try this http://unlimited.io./qhsusbdload.htm

I hate seeing all these hard bricked phones I'm sorry but yeah u shoulda read:/

absolutelygrim said:
You flashed an international ROM, you now probably have an expensive paperweight. Sorry, please read the stickies next time
You may be able to dd a partition 4 to your phone if someone dumps one for you, and if you know how/someone is willing to help.
First go try this http://unlimited.io./qhsusbdload.htm
Click to expand...
Click to collapse
I figured as much. For some reason I mistook the international rom for the att one
If I tried to exchange it, would att be able to notice this?
I'll try your link first, thank you.

Ezence01 said:
I figured as much. For some reason I mistook the international rom for the att one
If I tried to exchange it, would att be able to notice this?
I'll try your link first, thank you.
Click to expand...
Click to collapse
Umm, yes they will notice it. Just don't run over it with your car and make an insurance claim :\
If you can install Ubuntu 12.04 and teamviewer i'd be willing to try and help you

absolutelygrim said:
Umm, yes they will notice it. Just don't run over it with your car and make an insurance claim :\
If you can install Ubuntu 12.04 and teamviewer i'd be willing to try and help you
Click to expand...
Click to collapse
lol, no definitely not insurance claim. I'm in the process now, I'll update with results. Thanks for the advice and help.

Ezence01 said:
lol, no definitely not insurance claim. I'm in the process now, I'll update with results. Thanks for the advice and help.
Click to expand...
Click to collapse
If it doesn't work and you still want help send me a PM

man that icecoldjelly rom is doing some damage....:crying:

Crappyvate said:
man that icecoldjelly rom is doing some damage....:crying:
Click to expand...
Click to collapse
Yea it is. But I think I have an idea that will help everyone.. Not that they will read the OP if I start a thread :beer:

absolutelygrim said:
Yea it is. But I think I have an idea that will help everyone.. Not that they will read the OP if I start a thread :beer:
Click to expand...
Click to collapse
don't tell me you want to start a tutorial on dd'ing to restore the partition that was overwritten by icecoldjelly that would be opening a big can of worms ? although maybe not since they are already bricked

Crappyvate said:
don't tell me you want to start a tutorial on dd'ing to restore the partition that was overwritten by icecoldjelly that would be opening a big can of worms ? although maybe not since they are already bricked
Click to expand...
Click to collapse
I will try that if I can't fix it.
They are already bricked so it won't hurt any more than it is right now
If I can fix this guy's phone, then i'll consider starting a tutorial.
I'm going to document everything as I do it, and make it noob proof. IF it works. BIG FAT IF

absolutelygrim said:
I will try that if I can't fix it.
They are already bricked so it won't hurt any more than it is right now
If I can fix this guy's phone, then i'll consider starting a tutorial.
I'm going to document everything as I do it, and make it noob proof. IF it works. BIG FAT IF
Click to expand...
Click to collapse
got a backup of my mmcblk0p4 if you want

Crappyvate said:
got a backup of my mmcblk0p4 if you want
Click to expand...
Click to collapse
Throw it to me

absolutelygrim said:
Throw it to me
Click to expand...
Click to collapse
just remove the .txt

Crappyvate said:
just remove the .txt
Click to expand...
Click to collapse
Right now we are trying to time it right and get his phone into emmc mode.. one that's done, I think we should have this problem fixed.
Windows recognizes it as QHSUSB_DLOAD (so its still alive), but when he holds down power, no lights flash, making this hard to time
---------- Post added 28th October 2012 at 12:22 AM ---------- Previous post was 27th October 2012 at 11:52 PM ----------
Crappyvate said:
just remove the .txt
Click to expand...
Click to collapse
Is your mmcblk0p4 from 2.20? I don't know if that would matter.
I think it's because we are using Ubuntu 12.10 and not 12.04, will report back eventually..

12.10 is not happening, if it's successful on 12.04, even just the unbrick method, I'm not concerned about the downgrade anymore, this could be good news for our little international rom lovers
Will try 12.04 sometime today
Sent from my HTC One XL using xda-developers app

absolutelygrim said:
12.10 is not happening, if it's successful on 12.04, even just the unbrick method, I'm not concerned about the downgrade anymore, this could be good news for our little international rom lovers
Will try 12.04 sometime today
Sent from my HTC One XL using xda-developers app
Click to expand...
Click to collapse
sorry i was out...no partition is from 1.85 or maybe even 1.73 don't remember,
any luck ?? have you tried to talk to beaups or 18th.abn ?

Unbricking has been a real pain in the butt using ubuntu, we found it to much easier and more successful using tinycore from a bootable USB. I don't know why, but it's been proven on several devices so try that. Also, p4 holds the device imei and cid, when it gets corrupted in may be causing the soft brick because p12 is dependent on its information since it also displays the device imei and phone info, so do p12, make sure your using a signed image and do p4, which can be any p4, the imei will just have to be repaired afterward. It will spring to life, I promise you
Sent from my HTC One XL using Tapatalk 2

Crappyvate said:
sorry i was out...no partition is from 1.85 or maybe even 1.73 don't remember,
any luck ?? have you tried to talk to beaups or 18th.abn ?
Click to expand...
Click to collapse
18th.abn said:
Unbricking has been a real pain in the butt using ubuntu, we found it to much easier and more successful using tinycore from a bootable USB. I don't know why, but it's been proven on several devices so try that. Also, p4 holds the device imei and cid, when it gets corrupted in may be causing the soft brick because p12 is dependent on its information since it also displays the device imei and phone info, so do p12, make sure your using a signed image and do p4, which can be any p4, the imei will just have to be repaired afterward. It will spring to life, I promise you
Sent from my HTC One XL using Tapatalk 2
Click to expand...
Click to collapse
@crappy, nah we had to stop for the night cause I had to get up early and get senior pictures taken.
I had him install Ubuntu 12.04 rather than use a LiveCD, so we'll try it again later today.
@18th
We got to the point where it starts writing p4, but hangs and continuously sends the Reset, I posted in the thread over at the evo LTE forum asking about it, holding the power button for 30+ seconds as suggested prints an error cannot reset device
I am using mmcblk0p4 from crappy, and your hboot from dropbox.

On the hox, you only need to hold down the power button for about 10-12 seconds so 30 may be too long and sending a time out to the emmc recover tool
Sent from my HTC One XL using Tapatalk 2

[DRIVERS] [UnBrick hoxl project start] QHSUSB_DLOAD

Okay so if you are like me and have installed the OTA Update or ran the 3.18 ruu with an S-On Device chances are You are currently hard bricked which in most cases leaves 4 options, Option 1. Try to get a replacement through the carrier or Manufacturer Option 2. Send it off for a repair or Option 3 try and fix it yourself. Option 4 Toss the device and look elsewhere.
I Personally am going with Option 3 and am attempting to figure out a working Unbrick Method that does not require a RIFF box so with that said i will be working in this thread in an effort to get an unbrick project working. Feel free to add your knowledge, input, and advice in the proceeding posts below.
Please Note if you are using Windows 8 you will need to disable driver signature enforcement, while there are many ways to do this by far the easiest way is to open an Elevated Command Prompt and enter
Code:
bcdedit /set {globalsettings} advancedoptions true
when you restart your Computer choose option 7. To Disable Advanced Boot Options Enter
Code:
bcdedit /set {globalsettings} advancedoptions false

I suggest that you try reading here. I hard bricked my device before while trying to downgrade my HBOOT version from 1.14 to 1.09.
http://forum.xda-developers.com/showthread.php?t=2156231
To sum it up, he could still access his bootloader, but couldn't flash anything. By accessing rebootRUU, he managed to place his phone into a brick mode which allowed Linux to recognize and write to the boot partition. To enter that sort of brick mode, he flashed an UNSIGNED HBOOT file, which would have been fine since he was S-ON. BUT, once he sent in the command for S-ON, the device saw the UNSIGNED HBOOT and rebricked. He was then able to re-write the P4 file, which contains all your device information (IMEI, CID etc.). Then flash in the recovery, access the recovery, and flash your ROM.
I don't know how different that hard brick is from yours, but it worked for me. Can you access your bootloader btw?

d3thstalker said:
I suggest that you try reading here. I hard bricked my device before while trying to downgrade my HBOOT version from 1.14 to 1.09.
http://forum.xda-developers.com/showthread.php?t=2156231
To sum it up, he could still access his bootloader, but couldn't flash anything. By accessing rebootRUU, he managed to place his phone into a brick mode which allowed Linux to recognize and write to the boot partition. To enter that sort of brick mode, he flashed an UNSIGNED HBOOT file, which would have been fine since he was S-ON. BUT, once he sent in the command for S-ON, the device saw the UNSIGNED HBOOT and rebricked. He was then able to re-write the P4 file, which contains all your device information (IMEI, CID etc.). Then flash in the recovery, access the recovery, and flash your ROM.
I don't know how different that hard brick is from yours, but it worked for me. Can you access your bootloader btw?
Click to expand...
Click to collapse
no my device is literally hard bricked, no bootloader/hboot no os no recognition on pc other than qhsusb_dload i remember working on the same issue with the htc shooter on sprint so im trying the method we used to recover our device after intentionally bricking it which requires linux but in any case im almost there im currently trying to track down the ENG hboot for the evita atm

FragmentedLogik said:
im currently trying to track down the ENG hboot for the evita atm
Click to expand...
Click to collapse
If you find one, let Leamstears know. He has a thread posted somewhere asking for it.
Also, you might search for unbrick evita in general section. There was a thread started awhile back by my buddy.
Sent from my HTC One X using xda premium

i have you made any progress ??? my htc one s is hard briked too

https://www.dropbox.com/sh/a1n5s4r61wfh7qr/gkgxmKXwka/Evita soff partitions
Maybe this will help.
Sent from my One X using xda premium

I am not sure if this is helpful at all, but I was looking into methods used to unbrick other HTC devices and found this thread: http://forum.xda-developers.com/showthread.php?t=1522351 I am not sure what all I would need to change to get it to work for our phone. if you have any thoughts I would be more than willing to look at it.

PUfelix85 said:
I am not sure if this is helpful at all, but I was looking into methods used to unbrick other HTC devices and found this thread: http://forum.xda-developers.com/showthread.php?t=1522351 I am not sure what all I would need to change to get it to work for our phone. if you have any thoughts I would be more than willing to look at it.
Click to expand...
Click to collapse
I'm not sure it will really help. The first part is to run brickdetect.sh. That script appears to try to enumerate the partitions. I tried to enumerate my partitions using the manual steps in mirgantrophy's unbrick evita thread to no success before I sent my device off for JTAG. You could always try to run the brickdetect.sh script and see though. It doesn't do anything to your phone. It just searches dmesg (a Linux log) for the partitions being detected when you attach the bricked phone via USB. Don't run the rest of it though. ;-P

I'd like see a method to fix emmc of an htc inspire 4g(htc ace). Can any of our methods be transposed for other htc devices?

do you think this would work on a samsung device? i flashed a skyrocket rom for my S2 and it was sposed to be fine but it decided not to be. or at least work on a project for samsung devices.... dont leave us hanging

Trozzul said:
do you think this would work on a samsung device? i flashed a skyrocket rom for my S2 and it was sposed to be fine but it decided not to be. or at least work on a project for samsung devices.... dont leave us hanging
Click to expand...
Click to collapse
I definitely would not try this on any device other than the device it's intended for. Completely different chipsets.
Sent from my Evita

my htc one x does not start and charge the battery
try installing an edited rom
then restart the phone now will not start

gato06 said:
my htc one x does not start and charge the battery
try installing an edited rom
then restart the phone now will not start
Click to expand...
Click to collapse
Do you have One X (Endeavor) or One XL (Evita)?
Sent from my Evita

timmaaa said:
Do you have One X (Endeavor) or One XL (Evita)?
Sent from my Evita
Click to expand...
Click to collapse
One X at&t

gato06 said:
One X at&t
Click to expand...
Click to collapse
What ROM did you flash?
Sent from my Evita

timmaaa said:
What ROM did you flash?
Sent from my Evita
Click to expand...
Click to collapse
I try with this rom
http://forum.xda-developers.com/showthread.php?t=2174855

gato06 said:
I try with this rom
http://forum.xda-developers.com/showthread.php?t=2174855
Click to expand...
Click to collapse
Well you've bricked your phone. That ROM is not for our phone.
Sent from my Evita

How unbrick :'( You have idea?

You can either get a jtag repair or send it to HTC to have the motherboard replaced. Jtag is the cheaper option. When you get it back, make sure you stay within our forum and only flash software intended for our device.
Sent from my Evita

ran the 3.18 ruu with an S-On Device
Click to expand...
Click to collapse
i never thought run RUU with s-on device will brick it. Will it be more correct to say "run RUU on device with s-on & supper cid will brick you device"