You may want to look into the Jewel Evita Toolkit, as there's still some chance you may be able to recover, and worst case scenario, you're still bricked, so it's worth a stab.
I offer free JTAG to users with a 300 post count or who are vouched for by a senior members
In this case I would help out only asking that you please give something back to the community
If its a onexl Qualcomm chip I can service the unit
Sent from my SCH-R970 using xda premium
Hi Zarboz I have a at&t htc one x with damage by flash a ruu. with the Riff Box everything says ok but it still does not turn on. What could it be?
sorry for the english i'm from mexico
Does the unit show as qh_usbdload?
Sent from my HTC6435LVW using XDA Premium 4 mobile app
Can you post screenshot of what it shows if there is numbers or just qh dload
Sent from my HTC6435LVW using XDA Premium 4 mobile app
It hasn't been unbricked if it's still showing that.
Sent from my Evita
Did you ever fix yours?Oh, before I send to the guy my phone didnt even was recognized. After he returned to me it started happening. Maybe he didn't use Riff Box JTAG properly?
Ok, so I tried flashing cyanogenmod on my phone and ended up with what i believe to be a hard brick... I'll go through what I did, and I guess if there is any way to reverse this and return it to working condition, I would greatly appreciate this information. First, I used the exploit found in the all-in-one kit so that the bootloader could be unlocked officially by HTC. After getting my bootloader unlocked via the file sent to me by HTC, I flashed my cwm via fastboot. Everything seemed to be working fine at this point; the phone would boot into both the rom and the cwm. I rebooted the phone and flashed the boot image found in the cm rom I was flashing on my phone. I rebooted once again, erased the cache and dalvik, and then attempted to flash the rom. It was unsuccessful the first time due to failed asserts. I had previously been able to simply edit the build.prop file and remove the asserts on other android devices to correct this problem, so I attempted to do this. I tried again to flash the rom, which began installing, and then resulted in the phone turning off. I am sure that this has everything to do with my editing of the file, but I am just wondering why it did not work this time, and if there is a way to correct this without expensive hardware. Any feedback is greatly appreciated.
Ok, so I tried flashing cyanogenmod on my phone and ended up with what i believe to be a hard brick... I'll go through what I did, and I guess if there is any way to reverse this and return it to working condition, I would greatly appreciate this information. First, I used the exploit found in the all-in-one kit so that the bootloader could be unlocked officially by HTC. After getting my bootloader unlocked via the file sent to me by HTC, I flashed my cwm via fastboot. Everything seemed to be working fine at this point; the phone would boot into both the rom and the cwm. I rebooted the phone and flashed the boot image found in the cm rom I was flashing on my phone. I rebooted once again, erased the cache and dalvik, and then attempted to flash the rom. It was unsuccessful the first time due to failed asserts. I had previously been able to simply edit the build.prop file and remove the asserts on other android devices to correct this problem, so I attempted to do this. I tried again to flash the rom, which began installing, and then resulted in the phone turning off. I am sure that this has everything to do with my editing of the file, but I am just wondering why it did not work this time, and if there is a way to correct this without expensive hardware. Any feedback is greatly appreciated.
I downloaded the latest, most stable rom directly from the cyanogenmod website, and no, I can't access fastboot or recovery.