Database Info

[Q] HTC ONE X Briked fastboot FAILED unknown error

Hi:
The problem is the next: My HOX was bricked, the LCD display never turns on, i always have a blank screen. My firmware is 3.14.707.2 and i try to use the RUU for my CID_044 to unbrick my device like the user mr.dj26: http://forum.xda-developers.com/showthread.php?t=1859339&page=2. But after i put the unclock code (hdev) to flash the boot.img and recovery.img, my device is totally bricked.
I always have blank screen, but the device can restart and light the bottom buttons, but is like not have any rom. The device is only recognized for my windows when i put the device in bootloader, and when i use fastboot devices, he recognize the device, but when i try to flash any file use getvar command and others, he always say me: FAILED (command write failed (Unknown error)).
Before have this problem, i had blank screen but could hear the sound of the ROM starting and access to the device using adb and fastboot. Using the RUU always say that the battery still under 30%, i put 4 hours to charge and always the led is red. Connect the device after that and always have the same ERRORS. I drain the battery reboting a lot of times and after that i charge the device. After a 2 or 3 three hours the led turns green, but when i reconnect the device i have the same ERRORS.
My HOX is totally bricked or i could do something else to recover the fastboot and ADB connection to flash the ROM using RUU?
PS: I attach pictures of the fastboot errors and the device manager screens of my pc.

Do you have a dual-core S4 or a quad-code Tegra? Because you ran a RUU for the Tegra version but that is a firmware for the HD2.

You're in the wrong forum andres:
andresg13 said:
Recently i bought a HTC ONE X international version (CID: HTC_044 Asia WWE)
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=37427756#post37427756

iElvis said:
Do you have a dual-core S4 or a quad-code Tegra? Because you ran a RUU for the Tegra version but that is a firmware for the HD2.
Click to expand...
Click to collapse
I have a HTC ONE X international version Asian WWE (CID_044). I think that is a quad core Tegra and my firmware really is the 3.14.707.24. The problem is that i cant flash boot, recovery or use a RUU. I want to know another way to access to my device or know if its completely bricked.

Rob S. said:
You're in the wrong forum andres:
http://forum.xda-developers.com/showthread.php?p=37427756#post37427756
Click to expand...
Click to collapse
Sorry Rob. I put in this place causei really don't have experience in this forum and i cant reply in another threads cause i have to make 10 post or something like that. I really need help to solve my HOX problem.

andresg13 said:
Sorry Rob. I put in this place causei really don't have experience in this forum and i cant reply in another threads cause i have to make 10 post or something like that. I really need help to solve my HOX problem.
Click to expand...
Click to collapse
This is the forum for the One XL, you have the International One X. They are 2 completely different phones. You need to stick to the forums in the link below.
http://forum.xda-developers.com/forumdisplay.php?f=1533

pside15 said:
This is the forum for the One XL, you have the International One X. They are 2 completely different phones. You need to stick to the forums in the link below.
http://forum.xda-developers.com/forumdisplay.php?f=1533
Click to expand...
Click to collapse
Thanks.
I repost in the next link http://forum.xda-developers.com/showthread.php?p=37475112#post37475112. How can i delete the post?

andresg13 said:
Thanks.
I repost in the next link http://forum.xda-developers.com/showthread.php?p=37475112#post37475112. How can i delete the post?
Click to expand...
Click to collapse
Even though you're in the wrong forum, based on your cmd prompt screenshot im pretty sure your fastboot commands are not in the correct path... try dropping your .img inside your adb/fastboot folder, right click on the adb/fastboot folder and choose "open command prompt here"
Dunno what problems your facing, but that'll at least get your recovery on there and boot.img... dunno if it'll fix your black screen.........
Sent from my evita using Tapatalk 2

Op created new thread in the correct forum.
Thread close

[Q] HTC one x at&t QHSUSB_DLOAD mode, will not start.

I have a htc x AT & T one that will not start, I have looked in several forums and have not found the solution, I need help?
1. When the phone is connected to the mains or red light.
2. At precionar the power button for several seguntos the buttons below gives no flash and no response.
3. When I connect the phone to a PC with Windows only recognizes QHSUSB_DLOAD no response from phone.
This happened after installing RUU 3.18.502.6.
have any solution for my case?

This has happened to a few people. Were you rooted with SuperCID? It's not clear what the cause is, but your phone is bricked.
It's possible the jet tool might be able to unbrick it. There is also a service called jtag that will cost around $75.

You sir, are screwed. QHSUSB_DLOAD means the phone is most likely bricked.
Did you have SuperCID? You should have read this: http://forum.xda-developers.com/showthread.php?t=2181929

You can try the unbrick evita thread. You'll need a Linux boot disk. If you can't pull up the emmc partitions then you're SOL. Which is most likely the case but doesn't hurt to check right?
If you manage to restore your phone be sure to s-off before trying to ruu again.
Sent from my HTC One X using xda app-developers app

Please help me!
Hi, im only 14 years old, from argentina. I bricked my phone a month ago by flashing ICJ into HTC One X evita, and i spent like 160 dollars to repair it by jtag as here in argentina the jtag service did not work. Today i was also updating to RUU 3.18.502.6 through the RUU downloaded from HTC site and as it finished a message appeared saying it completed succesfully. But when i tried to boot it it wont turn on nor charge, and my PC detected as QHUSB_DLOAD my heart freezed as they are the same symptoms as last time. I would like to know please any solution to this, and also, will jtag service work this time or this case is like the one that happened to me before. Please any answer would be great. Thank You!

Nicobesso said:
Hi, im only 14 years old, from argentina. I bricked my phone a month ago by flashing ICJ into HTC One X evita, and i spent like 160 dollars to repair it by jtag as here in argentina the jtag service did not work. Today i was also updating to RUU 3.18.502.6 through the RUU downloaded from HTC site and as it finished a message appeared saying it completed succesfully. But when i tried to boot it it wont turn on nor charge, and my PC detected as QHUSB_DLOAD my heart freezed as they are the same symptoms as last time. I would like to know please any solution to this, and also, will jtag service work this time or this case is like the one that happened to me before. Please any answer would be great. Thank You!
Click to expand...
Click to collapse
This site works for some of the bricks... Didn't work for mine...
http://unlimited.io/qhsusbdload.htm

I tried this method but it did not work ... I'm still looking for a solution.

FarBeyond said:
This site works for some of the bricks... Didn't work for mine...
http://unlimited.io/qhsusbdload.htm
Click to expand...
Click to collapse
Maybe you, and others,need to learn to read again... Sorry to be rude, but that website clearly states at the top, "THIS METHOD WILL NOT WORK FOR DEVICES BRICKED BY FLASHING ROMS OR ANY OTHER SOURCE".
Also, PblClear.zip wipes the primary bootloader partition. Not the greatest idea...
Sent from my HTC One X using xda premium

Ok
Myrder said:
Maybe you, and others,need to learn to read again... Sorry to be rude, but that website clearly states at the top, "THIS METHOD WILL NOT WORK FOR DEVICES BRICKED BY FLASHING ROMS OR ANY OTHER SOURCE".
Also, PblClear.zip wipes the primary bootloader partition. Not the greatest idea...
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Yes i know, but as there is a lot of people like you with experience, maybe someone can help me.

http://forum.xda-developers.com/showthread.php?p=39545425
This is a discussion we were having about installing QHSUSB_DLOAD drivers and repairing them via usb.Might have useful links on it for you to do some investigation.
Sent from my HTC One X using xda premium

[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"

[Q] lost. cannot turn on or boot to anything

hey guys, i would really appreciate if someone has a minute to help me, cause i am lost in terminology and forums, and am working too much these days so cannot really read thousands of posts right now, and your experience could probably help.
so i installed rom manager , did i dont know what, went to work, my phone went battery dead, came back home, plugged it, but it wont recharge, nor go to boot loader, nor but normally, the light flashes randomly here and there when unplugging or pressing pwr button.
when connected to pc, the pc bips ta ta ta, or ti da, or ta di, but phone doesnt show anywhere, but the pc runs the device driver installation.
any clues?
it is an htc one x from rogers canada
thank you!

salissimo said:
hey guys, i would really appreciate if someone has a minute to help me, cause i am lost in terminology and forums, and am working too much these days so cannot really read thousands of posts right now, and your experience could probably help.
so i installed rom manager , did i dont know what, went to work, my phone went battery dead, came back home, plugged it, but it wont recharge, nor go to boot loader, nor but normally, the light flashes randomly here and there when unplugging or pressing pwr button.
when connected to pc, the pc bips ta ta ta, or ti da, or ta di, but phone doesnt show anywhere, but the pc runs the device driver installation.
any clues?
it is an htc one x from rogers canada
thank you!
Click to expand...
Click to collapse
Thanks for starting your own thread.
Screen stays black, power button stays black, can't get HTC screen or reovery up? If that's the case, it's bricked. You can try the Unbricking thread, you'll need a linux boot disk if you don't run linux and some time and patience. I'll brb to post helpful links.
Create bootable linux USB: http://forum.xda-developers.com/showthread.php?t=2223669&highlight=boot*+linux+usb
Unbrick thread: http://forum.xda-developers.com/showthread.php?t=1966850 If you make it past step 3 you may be able to save it. Otherwise, needs Jtag or warranty repair.
Good luck.

Did you flash anything with ROM Manager? I'm not sure it's supported for the One XL, but that could have changed. In the early days, a lot of people bricked because it was flashing things for the quad-core phone, which uses a different partition layout.
Was it functioning correctly, but then the battery went dead and it never revived? That sounds like the power management bug. Some people, unfortunately, have had their phones just die like this, like it just decides the battery is dead and won't recharge. If that's the case, you're due for a warranty replacement.

thanks.
i thought opening new threads with similar topics was considered kinda spamming, thats why i posted there. sorry.
ihave googled jtag but it is still unclear what that would be...
uhh, linux tralalaaaa a long night in front of me ha?
can you please explain in a few words?
thanks
exad said:
Thanks for starting your own thread.
Screen stays black, power button stays black, can't get HTC screen or reovery up? If that's the case, it's bricked. You can try the Unbricking thread, you'll need a linux boot disk if you don't run linux and some time and patience. I'll brb to post helpful links.
Create bootable linux USB: http://forum.xda-developers.com/showthread.php?t=2223669&highlight=boot*+linux+usb
Unbrick thread: http://forum.xda-developers.com/showthread.php?t=1966850 If you make it past step 3 you may be able to save it. Otherwise, needs Jtag or warranty repair.
Good luck.
Click to expand...
Click to collapse

well, the problem is it dint let me to do a lot of things trhough rom manager because it wasnt the premium version but it did let me change a bootable setting and i do not remember which. the phone after that worket normally. but my stupid self forgot i have changed that in rom manager, went to work, my battery emptied during the day and the phone went off. when i plugged it when i came home it would not charge or turn on. so my guess is it is trying to boot something i set up but doesnt have enough power to finish it and cannot recharge further because it is stuck in that booting... if I understood anything about this things in these few hours i was trying to be smart and jerked off around the phone
i guess i deserve it
thanks
iElvis said:
Did you flash anything with ROM Manager? I'm not sure it's supported for the One XL, but that could have changed. In the early days, a lot of people bricked because it was flashing things for the quad-core phone, which uses a different partition layout.
Was it functioning correctly, but then the battery went dead and it never revived? That sounds like the power management bug. Some people, unfortunately, have had their phones just die like this, like it just decides the battery is dead and won't recharge. If that's the case, you're due for a warranty replacement.
Click to expand...
Click to collapse

Charge it overnight and see if it turns on at all afterwards.
Sent from my One X using xda app-developers app

Delete.
Sent from my HTC One X using xda premium

salissimo said:
i thought opening new threads with similar topics was considered kinda spamming, thats why i posted there. sorry.
Click to expand...
Click to collapse
There's bit of etiquette involved. If the thread is "mature" in the sense that the OP's issue has been resolved, or multiple discussion threads have evolved, then popping in with a related question is fine. It's just not polite to pop in on the second page of someone else's query when people are still trying to help him, unless you have the identical problem.
salissimo said:
well, the problem is it dint let me to do a lot of things trhough rom manager because it wasnt the premium version but it did let me change a bootable setting and i do not remember which. the phone after that worket normally. but my stupid self forgot i have changed that in rom manager, went to work, my battery emptied during the day and the phone went off. when i plugged it when i came home it would not charge or turn on. so my guess is it is trying to boot something i set up but doesnt have enough power to finish it and cannot recharge further because it is stuck in that booting... if I understood anything about this things in these few hours i was trying to be smart and jerked off around the phone
Click to expand...
Click to collapse
It's possible, but sounds unlikely. I don't think that just changing some setting would stop it from at least powering on. ROM Manager would have had to overwrite something critical that would prevent the CPU from even finding hboot. Had you merely messed up some boot setting, you should still be able to get the boot screen, which would then start looping.
Plug your phone into your PC and see what pops up in Device Manager. I expect you'll get QHUSB_DLOAD, which means you're bricked.

guyz. what about this line?
quote
rerequisites: Ubuntu 12.04 or higher. 32/64 bit
unbrick package: http://dl.dropbox.com/u/40181085/unbrick_evita.zip
A null p4: included in the unbrick package.. you will need to hex edit your IMEI into this file. the offset is 0x21c, it's after 11111111, which is the SuperCID
end quote
what does it mean an null p4 ? is it a file? i have a file called killp4 in the unbrick evita folder i downloaded. should i type my imei into it and save it? where in the file? any specific syntax? thanks!
salissimo said:
thanks.
i thought opening new threads with similar topics was considered kinda spamming, thats why i posted there. sorry.
ihave googled jtag but it is still unclear what that would be...
uhh, linux tralalaaaa a long night in front of me ha?
can you please explain in a few words?
thanks
Click to expand...
Click to collapse

salissimo said:
guyz. what about this line?
quote
rerequisites: Ubuntu 12.04 or higher. 32/64 bit
unbrick package: http://dl.dropbox.com/u/40181085/unbrick_evita.zip
A null p4: included in the unbrick package.. you will need to hex edit your IMEI into this file. the offset is 0x21c, it's after 11111111, which is the SuperCID
end quote
what does it mean an null p4 ? is it a file? i have a file called killp4 in the unbrick evita folder i downloaded. should i type my imei into it and save it? where in the file? any specific syntax? thanks!
Click to expand...
Click to collapse
I've never used that unbrick tool but I'm assuming you would need to be able to get to the bootloader to get it to work. Correct me if I'm wrong.
Sent from my HTC One X using xda app-developers app

salissimo said:
guyz. what about this line?
quote
rerequisites: Ubuntu 12.04 or higher. 32/64 bit
unbrick package: http://dl.dropbox.com/u/40181085/unbrick_evita.zip
A null p4: included in the unbrick package.. you will need to hex edit your IMEI into this file. the offset is 0x21c, it's after 11111111, which is the SuperCID
end quote
what does it mean an null p4 ? is it a file? i have a file called killp4 in the unbrick evita folder i downloaded. should i type my imei into it and save it? where in the file? any specific syntax? thanks!
Click to expand...
Click to collapse
bakp4 is the null p4
I think killp4 is the same but I used bakp4 when i did it.

can you please try to answer my question? do i have to edit the file? which file? what and where to write in? can i skipo this step maybe?
thanks
exad said:
bakp4 is the null p4
I think killp4 is the same but I used bakp4 when i did it.
Click to expand...
Click to collapse

salissimo said:
can you please try to answer my question? do i have to edit the file? which file? what and where to write in? can i skipo this step maybe?
thanks
Click to expand...
Click to collapse
Hex edit your imei into bakp4 You cannot skip any steps. Did step 3 bring up your emmc partitions? if not you can't move any further. It's a full brick.

thanks,
i think i got ack something like sda1 sda2 sda3 so i am still hoping.
i have just opened my phone to find out there is no imei code printed anywhere in it.
so i am digging through my **** to find that little sticker which i think no longer exists.
heh, am i lucky.
is there an imei printed somwhere within the phone to your knowledge?
thanks a lot man
exad said:
Hex edit your imei into bakp4 You cannot skip any steps. Did step 3 bring up your emmc partitions? if not you can't move any further. It's a full brick.
Click to expand...
Click to collapse

salissimo said:
thanks,
i think i got ack something like sda1 sda2 sda3 so i am still hoping.
i have just opened my phone to find out there is no imei code printed anywhere in it.
so i am digging through my **** to find that little sticker which i think no longer exists.
heh, am i lucky.
is there an imei printed somwhere within the phone to your knowledge?
thanks a lot man
Click to expand...
Click to collapse
Needs to be the same amount of partitions as shown in the picture.. I think it's 32? if I'm not mistaken. If not, then you cannot recover.
no, it's not printed on the phone anywhere. It's in the Hboot or in the box the phone came with. that's it.

If you got it from AT&T, contact them and ask for bit. Whenever they activate a phone, we store it in the system and keeps track of what phone the customer is using.
Sent from my Carbon-ize Evita using xda-developers app

in the screenshot there are dev/sda dev/sda1 dev/sda2 dev/sda3 dev/sda5 dev/sda6
i have dev/sda dev/sda1 dev/sda2 dev/sda3 i think
but i havent done that with imei when i tried
so no chance ha?
what if i dont find the imei?
thank you!
exad said:
Needs to be the same amount of partitions as shown in the picture.. I think it's 32? if I'm not mistaken. If not, then you cannot recover.
no, it's not printed on the phone anywhere. It's in the Hboot or in the box the phone came with. that's it.
Click to expand...
Click to collapse

do you think mz phone is still under warranty considering it was tampered, and i cracked it open?
thanks!
salissimo said:
in the screenshot there are dev/sda dev/sda1 dev/sda2 dev/sda3 dev/sda5 dev/sda6
i have dev/sda dev/sda1 dev/sda2 dev/sda3 i think
but i havent done that with imei when i tried
so no chance ha?
what if i dont find the imei?
thank you!
Click to expand...
Click to collapse

I doubt AT&T can tell you unlocked it. They'll assume it's a power issue like Telus did for me. HTC may or may not warrant it. Mixed results from xda members
Sent from my One X using xda app-developers app

It should be in the EFS nv_data.bin. folder.
Sent from my HTC One X using xda premium

[Q] HOX is dead Please HELP!

Hi, i updated my htc one x at&t through HTC Manager with RUU Stock Rom. Everything was going fine and i don't know wth happen!!! Now my HOX wont power on after upgrade!! If i plug it to computer this one recognize the phone but htc sync manager doesn´t. PLease help me if you need more info please ask for it!! thank you very much!

Have you tried flashing stock?
Sent from that one guy with the cool phone
If I helped you hit that Thanks button!

ayo234 said:
Have you tried flashing stock?
Sent from that one guy with the cool phone
If I helped you hit that Thanks button!
Click to expand...
Click to collapse
how can i do that? i can't get into bootloader or recovery to do it! thanks for your reply

Were you son or soff? Stock or rooted?
Sent from my HTC One XL using xda app-developers app

exactly same problem here... I think this is a brick.... soft or hard i cant tell. I am trying to use a home made jig still no progress, may be i connected it badly.
Still got faith b4 opening this beast/beauty... I'll post if any advance...

There's no such thing as a soft brick, it's either bricked or it's not.
Sent from my Evita

Thanx got that timmaaa....
Exad mine was at
S-ON
ROOTED
SuperCID

Qnatz said:
Thanx got that timmaaa....
Exad mine was at
S-ON
ROOTED
SuperCID
Click to expand...
Click to collapse
Sorry to say this but your bricked
Running RUU while S-ON = Brick.

yap.... that's the beauty...
on a pc when flashing cmos there are
jumpers/pins if connected they wipe cmos
is this similar with the htc one x board..... maybe it would work.
has anyone done this....

Kinotsu said:
Sorry to say this but your bricked
Running RUU while S-ON = Brick.
Click to expand...
Click to collapse
Hi, i'm
S-ON
Rooted (but i unroot before installing stock rom) and,
SuperCID
HBOOT 1.14
I really don't understand. Am i in the same situation? why do this happen to a phone? there must be a way to solve this kind of problems. I downloaded the stock rom (.exe file) from htc webpage at at&t htc one x update tutorial. why if htx is letting someone downloading it the phone can get bricked? thank you for your answers

germanjo said:
Hi, i'm
S-ON
Rooted (but i unroot before installing stock rom) and,
SuperCID
HBOOT 1.14
I really don't understand. Am i in the same situation? why do this happen to a phone? there must be a way to solve this kind of problems. I downloaded the stock rom (.exe file) from htc webpage at at&t htc one x update tutorial. why if htx is letting someone downloading it the phone can get bricked? thank you for your answers
Click to expand...
Click to collapse
I unfortunately had the same issue, The SuperCID & S-ON come into play. You would want to do the JTAG revival, your only hope. Your SuperCID indicates the modification done, which primarily causes this.

humdingor said:
I unfortunately had the same issue, The SuperCID & S-ON come into play. You would want to do the JTAG revival, your only hope. Your SuperCID indicates the modification done, which primarily causes this.
Click to expand...
Click to collapse
Would you recomend riff jtag? i know it is very expensive but i will look for some one in my city who has it. Any other idea of how to solve it? any idea if i can build jtag on my own. i'm good with electronics so i think i can do it if i get the circuit diagram. thank you

To be honest you'd be better off getting someone who knows what they're doing to do it for you. HTC have nothing to do with the RUU bricking phones, it's nit a fault with the RUU. It's because it looks for certain criteria wharf it runs and if you don't have those criteria it goes bad. It's up to the users to educate themselves about what happens when they've modified their phones.
Sent from my Evita

germanjo said:
Hi, i'm
S-ON
Rooted (but i unroot before installing stock rom) and,
SuperCID
HBOOT 1.14
I really don't understand. Am i in the same situation? why do this happen to a phone? there must be a way to solve this kind of problems. I downloaded the stock rom (.exe file) from htc webpage at at&t htc one x update tutorial. why if htx is letting someone downloading it the phone can get bricked? thank you for your answers
Click to expand...
Click to collapse
The brick is due to SuperCID, which is a mod/hack that you did. HTC is not responsible for that. RUU with SuperCID typically shouldn't result in a brick. But on the other hand, you should always do thorough research before applying any stock updates (RUU or OTA) to a modded phone.
If there was a way to come back form this short of JTAG, it hasn't been found yet. And its been worked on by some knowledgeable and skilled folks here.

germanjo said:
Would you recomend riff jtag? i know it is very expensive but i will look for some one in my city who has it. Any other idea of how to solve it? any idea if i can build jtag on my own. i'm good with electronics so i think i can do it if i get the circuit diagram. thank you
Click to expand...
Click to collapse
I've messed up my phone twice & was rescued through JTAG by MobileVideotech. The service is good, although the AT&T ROM that they loaded kept my phone rebooting frequently. However, I have seen that issue ever since I came on custom ROMs. You can give it a try if you wish.