Related
I went to flash some things...and now it's stuck in the qualcomm download mode? How the hell do I get out of it??
You can't, you're screwed
I had this on my old Sensation, it stands for Qualcomm High Speed USB
Basically what's happened is your phone has lost the drivers for the chip set and needs them re-installed, as far as I'm aware, no-one has managed to find a way to do it.
Hope its still under warranty mate, I think its the only way you'll get it sorted
Sent from my GT-I9100 using xda premium
redrumsilence said:
You can't, you're screwed
I had this on my old Sensation, it stands for Qualcomm High Speed USB
Basically what's happened is your phone has lost the drivers for the chip set and needs them re-installed, as far as I'm aware, no-one has managed to find a way to do it.
Hope its still under warranty mate, I think its the only way you'll get it sorted
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
You're kidding, right? Well I installed the drivers for that, and it's now recognized by my computer, but there's nothing I can do? At all?
What exactly did you do to cause this?
Sent from my HTC One X using Tapatalk 2
random1204 said:
You're kidding, right? Well I installed the drivers for that, and it's now recognized by my computer, but there's nothing I can do? At all?
Click to expand...
Click to collapse
When it happened to me, I found the QHSUSB drivers and installed them, my computer recognised my Sensation, but nothing else.
I scoured XDA, Google, all sorts, I couldn't find anything, I just sent mine in under insurance and got a new one
Sent from my GT-I9100 using xda premium
Your not screwed. Pmed
Sent from my HTC One X using xda premium
Galaxy s3 Tmobile in same state
18th.abn said:
Your not screwed. Pmed
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Hey do you have any info on this mode? I would love to have some kind of info as to a course of action, even though this is for a different model...
18th.abn said:
Your not screwed. Pmed
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
i to am stuck in this mode. i flashed clockwork recovery (gsm) on my at&t one x thinking it was for our phone since it wasnt there the last time i checked. after i did a reboot the phone never came back on.
rob219 said:
i to am stuck in this mode. i flashed clockwork recovery (gsm) on my at&t one x thinking it was for our phone since it wasnt there the last time i checked. after i did a reboot the phone never came back on.
Click to expand...
Click to collapse
Is it completely dead and unresponsive? Just flashing the wrong recovery shouldn't kill your phone. I've done it myself a couple of times by accident, and fixing it was just a matter of flashing the right one.
Sounds like you actually flashed the wrong rom. Doing that can kill your bootloader, which will put you in QHSUSB mode. There is a way out that's been discussed, but I can't find it at the moment. It involves pushing a new hboot onto your phone and I believe requires Linux.
iElvis said:
Is it completely dead and unresponsive? Just flashing the wrong recovery shouldn't kill your phone. I've done it myself a couple of times by accident, and fixing it was just a matter of flashing the right one.
Sounds like you actually flashed the wrong rom. Doing that can kill your bootloader, which will put you in QHSUSB mode. There is a way out that's been discussed, but I can't find it at the moment. It involves pushing a new hboot onto your phone and I believe requires Linux.
Click to expand...
Click to collapse
it wasnt a rom. it was definetly the clockwork recovery in rom manager. it said gsm next to htc one x and its a new one so i was stupid enough to flash it. i did a reboot and it was dead. i already talk to at&t about it and there sending me a new one.
rob219 said:
it wasnt a rom. it was definetly the clockwork recovery in rom manager. it said gsm next to htc one x and its a new one so i was stupid enough to flash it. i did a reboot and it was dead. i already talk to at&t about it and there sending me a new one.
Click to expand...
Click to collapse
That's interesting, because I did (almost) the same thing. When I first unlocked my HOX, I installed ROM Manager and accidentally flashed the Samsung GSII recovery. I was able to fix it just by going back to bootloader and adb flashing the correct version.
iElvis said:
That's interesting, because I did (almost) the same thing. When I first unlocked my HOX, I installed ROM Manager and accidentally flashed the Samsung GSII recovery. I was able to fix it just by going back to bootloader and adb flashing the correct version.
Click to expand...
Click to collapse
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.
I had the same problem with the QHSUSB Download it turns out my phone had a really drained battery so how I managed to fix it was had it plugged into my computer and let the lights flash until i got a solid amber light. after about 15 minutes, I turned it on and it worked fine!
on my tablet i pressed for a really long time the power button and then it started up
it enters almos allways in qualcomm download mode when the battery is depleated.
you revived a dead thread to say something about your tablet?
I'm going to go revive some too now
Sent from my HTC One XL using Tapatalk 2
DvineLord said:
you revived a dead thread to say something about your tablet?
Click to expand...
Click to collapse
Someone can find my reply useful, compared to you and the other troll that did not say anything useful.
Same situation for me .. i flashed TWRP, backedup my rom, flashed a new rom and reboot. black screen, no light, unresponsive .. this same message shows up on my windows machine "QHUSB_LOAD no driver found"
atombone said:
Same situation for me .. i flashed TWRP, backedup my rom, flashed a new rom and reboot. black screen, no light, unresponsive .. this same message shows up on my windows machine "QHUSB_LOAD no driver found"
Click to expand...
Click to collapse
I'm guessing you flashed an international ROM on your One XL. That will do it.
iElvis said:
I'm guessing you flashed an international ROM on your One XL. That will do it.
Click to expand...
Click to collapse
Its a One X (ATT) but your probably right. I downloaded it from ONEXROOT.com. just strange to me that because i flashed a rom it screws the bootloader. ugh... sucks
I recently got the One X because I became to impatient for the One X+.
After flashing cm10 on it I decided to try and flash back to stock to see if i could return it to ATT because i was within 14 days.
I accidentally bricked my phone by deleting my system from the recovery and now I cant boot into recovery.
It turns on but goes as far as the "HTC quietly brilliant 'this build is for development purposes...'" screen and stops.
I can turn the phone off and on but it gets stuck at this screen.
I've tried button combos to get into recovery and I've tried adb and the one x tool kit.
I've also tried the recovery from the RUU OTA update but no dice.
Any way to fix this?
Ectosock said:
I recently got the One X because I became to impatient for the One X+.
After flashing cm10 on it I decided to try and flash back to stock to see if i could return it to ATT because i was within 14 days.
I accidentally bricked my phone by deleting my system from the recovery and now I cant boot into recovery.
It turns on but goes as far as the "HTC quietly brilliant 'this build is for development purposes...'" screen and stops.
I can turn the phone off and on but it gets stuck at this screen.
I've tried button combos to get into recovery and I've tried adb and the one x tool kit.
I've also tried the recovery from the RUU OTA update but no dice.
Any way to fix this?
Click to expand...
Click to collapse
Which ruu were you using?
Did you relock your boot loader before running ruu?
Sent from my One X using xda app-developers app
Myrder said:
Which ruu were you using?
Did you relock your boot loader before running ruu?
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
I used "htc_one_x_RUU_2.20.502.7_att_us_08022012" to revert back to stock because i was originally on 2.20.
I did not relock my boot loader before running RUU.
Ectosock said:
I used "htc_one_x_RUU_2.20.502.7_att_us_08022012" to revert back to stock because i was originally on 2.20.
I did not relock my boot loader before running RUU.
Click to expand...
Click to collapse
There is your problem.
Fastboot oem lock
Type that into your fastboot cmd window to ruu
Sent from my One X using xda app-developers app
Myrder said:
There is your problem.
Fastboot oem lock
Type that into your fastboot cmd window to ruu
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
still no dice
error: device not found or < waiting for device >
One thing though is the phone shows up in my device manager as Android but is an unknown and does not have the drivers.
I have the usb drivers, and android SDK installed so I dont know what drivers it is missing.
Okay I can get into the bootloader but im still getting no ADB connection
[EDIT]
from the bootloader i went into fastboot USB and relocked the bootloader
RUU is running!
Ectosock said:
Okay I can get into the bootloader but im still getting no ADB connection
[EDIT]
from the bootloader i went into fastboot USB and relocked the bootloader
RUU is running!
Click to expand...
Click to collapse
Glad you're back up and running.
I wonder if att will even take back his phone because of the relocked status, why do you want the one x + so much? You just said you couldn't wait so you tampered with it and changed your mind, but I mean the one x + is only a second faster.. you can just overclock HTC one x anyways. But I'm glad you phone is back.
Keep the Xl.
WR
Sent from my HTC One X
WhatTheAndroid? said:
I wonder if att will even take back his phone because of the relocked status, why do you want the one x + so much? You just said you couldn't wait so you tampered with it and changed your mind, but I mean the one x + is only a second faster.. you can just overclock HTC one x anyways. But I'm glad you phone is back.
Click to expand...
Click to collapse
WarRaven said:
Keep the Xl.
WR
Sent from my HTC One X
Click to expand...
Click to collapse
64gb plus better battery is enough for me to switch.
Also can the store employees actually tell if it was bootloader tampered? The last time I traded in my stock flashed Samsung Captivate for return all they did was a factory reset and took it back.
Though, better battery life is questionable.
WR
Sent from my HTC One X
They can just go into fastboot if they wanted to and just deny your return. I doubt they will do that. Although it would suck if the phone malfunctions on the next person and he returns it back to att and I guess that would be suspicious but I think your fine. I guess more space is nice on a phone but I don't think I have used that much space on my laptop haha, mabye 50 gigs of bloatware and some music and some fps games. I was just wondering why the switch. Oh and did the ruu go as planned? Oh and also if you decide to get insurance for your phone you should think about squaretrade...they protect against a lot..drops spills..and if you factory reset to stock Rom they will fix it even though you may have rooted..and they will pay you the no commitment price if they can't fix it.(drops,spills,etc)
Here in Los Angeles and surrounding cities the ATT reps are now trained to get into the boot loader to check for a tampered and unlocked device. A few months ago they were not but many devices have come back where someone screwed it up and returned it.
WhatTheAndroid? said:
They can just go into fastboot if they wanted to and just deny your return. I doubt they will do that. Although it would suck if the phone malfunctions on the next person and he returns it back to att and I guess that would be suspicious but I think your fine. I guess more space is nice on a phone but I don't think I have used that much space on my laptop haha, mabye 50 gigs of bloatware and some music and some fps games. I was just wondering why the switch. Oh and did the ruu go as planned? Oh and also if you decide to get insurance for your phone you should think about squaretrade...they protect against a lot..drops spills..and if you factory reset to stock Rom they will fix it even though you may have rooted..and they will pay you the no commitment price if they can't fix it.(drops,spills,etc)
Click to expand...
Click to collapse
The RUU worked perfectly and I returned it with no hassle; they didn't even factory reset it in front of me.
I now have the One X+ and I'm glad i switched. It runs so well I don't think I'll need a custom rom for a while.
I've been using Hassoon2000's All in one toolkit. I successfully unlocked the boot loader. I was going to install Cyanogenmod 10. I copied the boot.img into the kernals folder for the AIO toolkit. I flashed that and that's where it went south. My phone continuously rebooted at the HTC bootup screen.
After some reading I have "relocked" the bootloader. I attempted to flash what I thought was the stock RUU. I can get into fast boot, but not the recovery. ( I was using the TWRP recovery that came with the tool kit). If I try to choose factory reset, it acts like it's flashing my phone (gray screen with a progress bar, but then goes back into fastboot after about 30sec.)
Am I SOL? I'm willing to compensate via pay pal if we get this thing going. If not, I did find a site call JTag brick repair.
When you flashed the kernel, did you install the actual Rom? If your phone can turn on, its not bricked. Which ruu did you download? Why isn't it working?
Sent from my HTC One XL using xda app-developers app
area51avenger said:
When you flashed the kernel, did you install the actual Rom? If your phone can turn on, its not bricked. Which ruu did you download? Why isn't it working?
Sent from my HTC One XL using xda app-developers app
Click to expand...
Click to collapse
I found an ruu after some googling. I perhaps didn't get the right one. No I didn't install the rom after I flashed the kernel. I flashed the kernel first, then I was going to boot into the recovery to install the rom. The phone just hung at the HTC screen before going into recovery. In red letters it says: This build is for development purposes only... etc"
Did you hold volume down and power at the same time to boot into recovery? Also make sure you get the right ruu. Which carrier are you on and what firmware were you before you flashed? The ruu is an exe you run from your desktop while your phone is in fastboot
Sent from my HTC One XL using xda app-developers app
Here's where I'm currently at. I have the bootload unlocked again through the toolkit. I also have the TWRP installed. I CAN get into TWRP.
I have AT&T, I'll do some searching on trying to find an RUU.
Hboot-1.14.0002
Radio-0.19as.32.09.11_2
openDSP-v29.1.0.45.0622
Awesome. Now mount USB storage in twrp and plug it in to your computer. If windows asks you to format. Say yes and format fat32. Copy the cm10.zip file to your sd card. Install from twrp. You may have to flash the boot.img again in fastboot.
Sent from my HTC One XL using xda app-developers app
I get an E:Error in sdcard/cm10.zip (Status 7)
Error flashing zip
Updating partition details...
I did do a factory reset and wipe cache.
Is it the right cm10 for HTC evita
omario8484 said:
Is it the right cm10 for HTC evita
Click to expand...
Click to collapse
I'm doing endevarou. I have the HTC One X, not the XL.
You have the one xl if you have the dual core att evita. if you have the quad core international one x then it's the endeavor.
Sent from my HTC One XL
deathbyenduser said:
I'm doing endevarou. I have the HTC One X, not the XL.
Click to expand...
Click to collapse
If so, then you are in the wrong forum, and if you used the toolkit from this forum, it also explains why you are stuck in the state you are. This forum is for the Evita. Are you sure you have the quad core Tegra3 version? What carrier is your phone from?
Also, if you can get into hboot, you are nowhere near bricked. Any type of power on (even just hboot) is not that hard to recover from. The only real brick is if the screen doesn't come on at all, and no charge LED when plugged to charger. Even then, the phone can sometimes be unbricked in Linux.
redpoint73 said:
If so, then you are in the wrong forum, and if you used the toolkit from this forum, it also explains why you are stuck in the state you are. This forum is for the Evita. Are you sure you have the quad core Tegra3 version? What carrier is your phone from?
Also, if you can get into hboot, you are nowhere near bricked. Any type of power on (even just hboot) is not that hard to recover from. The only real brick is if the screen doesn't come on at all, and no charge LED when plugged to charger. Even then, the phone can sometimes be unbricked in Linux.
Click to expand...
Click to collapse
Okay. I have the One XL for LTE. I was thinking the XL meant the bigger HTC One X that was out.
deathbyenduser said:
I'm doing endevarou. I have the HTC One X, not the XL.
Click to expand...
Click to collapse
deathbyenduser said:
Okay. I have the One XL for LTE. I was thinking the XL meant the bigger HTC One X that was out.
Click to expand...
Click to collapse
Really?! You my friend should not be flashing, rooting, unlocking bootloaders until you know the process and you can do it without reading how to do so. Learn how to swim before you jump into the deep end.
This is my third my root. I had the OG Motorola Droid and HTC Sensation with Tmobile. Now this One X LTE.
I can see why you said that though. I made an honest mistake. Looking back at the HTC models what I meant to say for some stupid reason I thought the HTC One X + (new one for att) was actually the HTC One XL. So I confused myself, flashed the wrong kernel. Luckily with some confirmation from you guys I'm back on the road. My phone is working.
My phone is working with CM10. I just need to get a compatible version of Gapps on. I'll be sending someone beer money. :victory:
deathbyenduser said:
This is my third my root. I had the OG Motorola Droid and HTC Sensation with Tmobile. Now this One X LTE.
I can see why you said that though. I made an honest mistake. Looking back at the HTC models what I meant to say for some stupid reason I thought the HTC One X + (new one for att) was actually the HTC One XL. So I confused myself, flashed the wrong kernel. Luckily with some confirmation from you guys I'm back on the road. My phone is working.
My phone is working with CM10. I just need to get a compatible version of Gapps on. I'll be sending someone beer money. :victory:
Click to expand...
Click to collapse
Great to hear.
You are very lucky you didn't do it the other way around (flash an endeavor rom on an evita device), as you would be the proud owner of a very expensive paperweight.
HTC can get stuffed for naming 3 different phones almost exactly the same One X/ One XL (or AT&T One X) / One X+. It is a minefield for people new to the phone.
Regardless of how many phones you've rooted, its pretty clear that you didn't do the enough reading to know the difference between the X, XL, and X+, and to know what you own. As already mentioned, you're lucky you didn't brick.
Only flash things from our forum, and you'll be safe: http://forum.xda-developers.com/forumdisplay.php?f=1538
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
Ladies and Gents,
I made sure I chose the correct RUU based on my CID (CWS__001)
I relocked my phone and attempted to install "RUU_EVITA_UL_JB_45_S_Cingular_US_3.18.502.6_Radio_ 0.24p.32.09.06_10.130.32.34_release_signed.exe". After the RUU finished my phone seems to be hard bricked.
Won't Boot.
No power lights.
I knew this could happen when flashing an international version. AFTER getting owned I also found this post http://forum.xda-developers.com/showthread.php?t=2181929. Which was blatantly in the beginning of the forum. Has anyone found a fix for this issue, or is my only option JTAG repair?
Thanks,
Ryan
ryan9316 said:
Ladies and Gents,
I made sure I chose the correct RUU based on my CID (CWS__001)
I relocked my phone and attempted to install "RUU_EVITA_UL_JB_45_S_Cingular_US_3.18.502.6_Radio_ 0.24p.32.09.06_10.130.32.34_release_signed.exe". After the RUU finished my phone seems to be hard bricked.
Won't Boot.
No power lights.
I knew this could happen when flashing an international version. AFTER getting owned I also found this post http://forum.xda-developers.com/showthread.php?t=2181929. Which was blatantly in the beginning of the forum. Has anyone found a fix for this issue, or is my only option JTAG repair?
Thanks,
Ryan
Click to expand...
Click to collapse
You could take your phone back and tell them it won't boot etc.
If you can't get it to boot neither can they, so no-one will know it's been unlocked/rooted.
Some people will say this is fraudulent, but hey, if you can live with yourself who cares what anyone else thinks?
Pft I returned mine to Telus when the same thing happened to me. The way I see it, it was HTC's RUU that bricked my phone, not me. Like you, I did not have supercid and was S-ON.
You could try the unbrick Evita thread. If you make it past step 3 you can save your phone.
You'll need to boot to Linux.
Sent from my One X using xda app-developers app
exad said:
Pft I returned mine to Telus when the same thing happened to me. The way I see it, it was HTC's RUU that bricked my phone, not me. Like you, I did not have supercid and was S-ON.
You could try the unbrick Evita thread. If you make it past step 3 you can save your phone.
You'll need to boot to Linux.
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
I saw this and will give it a try, thank you for the advice!
ryan9316 said:
I saw this and will give it a try, thank you for the advice!
Click to expand...
Click to collapse
I bricked my phone trying to install elementalx and phone wouldn't boot at all and no lights. sent it in for jtag and they told me emmc controller was unresponsive and sent it back to me. looks like I may have to trash the phone... or make a few bucks on ebay.
mkalbarc said:
I bricked my phone trying to install elementalx and phone wouldn't boot at all and no lights. sent it in for jtag and they told me emmc controller was unresponsive and sent it back to me. looks like I may have to trash the phone... or make a few bucks on ebay.
Click to expand...
Click to collapse
Did they refund you? I was going to send it into mobiletechvideos for JTAG. I don't see the phones selling for more than 100$ on ebay.
ryan9316 said:
Did they refund you? I was going to send it into mobiletechvideos for JTAG. I don't see the phones selling for more than 100$ on ebay.
Click to expand...
Click to collapse
If the emmc controller isn't responding, it's worth even less than that.
Sent from my One X using xda app-developers app
ryan9316 said:
Did they refund you? I was going to send it into mobiletechvideos for JTAG. I don't see the phones selling for more than 100$ on ebay.
Click to expand...
Click to collapse
they did refund. minus the cost of shipping and something else, however. it was worth a try though... All I know though is I will never touch an elemental kernel again... not worth it that's for sure...
mkalbarc said:
they did refund. minus the cost of shipping and something else, however. it was worth a try though... All I know though is I will never touch an elemental kernel again... not worth it that's for sure...
Click to expand...
Click to collapse
Just curious about your situation. Did the kernel flash successfully and then just not boot? What ROM were you flashing it over? Tons of people, myself included, have flashed that kernel without issue so I'm interested in what exactly happened.
pside15 said:
Just curious about your situation. Did the kernel flash successfully and then just not boot? What ROM were you flashing it over? Tons of people, myself included, have flashed that kernel without issue so I'm interested in what exactly happened.
Click to expand...
Click to collapse
Sure, I too have used their kernels and have never had an issue until this time. So I started to install the kernel and it froze at I believe 60%? Then it sat... It said the flash could take awhile so to just wait so I did... For 2 hours. I knew something wasn't right because no elemental flash has taken my phone longer than a few minutes before this one so without thinking i'd hurt anything I held the buttons to hard power off the phone. After it shut off it's been completely dead since. No charge lights, no sign of any life at all other then the QHSUSB_DLOAD under device manager when plugged into my PC. the rom that I had flashed was the latest cleanrom. super bummed but i'll get over it. the worst part about this was I had pics of my kids that I had not backed up that are now lost.
mkalbarc said:
Sure, I too have used their kernels and have never had an issue until this time. So I started to install the kernel and it froze at I believe 60%? Then it sat... It said the flash could take awhile so to just wait so I did... For 2 hours. I knew something wasn't right because no elemental flash has taken my phone longer than a few minutes before this one so without thinking i'd hurt anything I held the buttons to hard power off the phone. After it shut off it's been completely dead since. No charge lights, no sign of any life at all other then the QHSUSB_DLOAD under device manager when plugged into my PC. super bummed but i'll get over it. the worst part about this was I had pics of my kids that I had not backed up that are now lost.
Click to expand...
Click to collapse
That does suck about the pictures. That would upset me more than the phone as well. I went and looked at the thread after I saw your post and saw a couple of other bricks aside from yours in the last couple of hundred posts. Very unfortunate that flashing a kernel bricked it. I try to stay away from anything that uses the Aroma Installer unless there are no other options, not saying that was the problem, but I've had numerous issues with it previously. After seeing multiple bricks from a basic kernel flash I'm going to definitely be more cautious about what I flash from now on. I'd be totally screwed if I bricked this phone. Anyway, hope you end up with something better out of this, like the HTC One.
pside15 said:
That does suck about the pictures. That would upset me more than the phone as well. I went and looked at the thread after I saw your post and saw a couple of other bricks aside from yours in the last couple of hundred posts. Very unfortunate that flashing a kernel bricked it. I try to stay away from anything that uses the Aroma Installer unless there are no other options, not saying that was the problem, but I've had numerous issues with it previously. After seeing multiple bricks from a basic kernel flash I'm going to definitely be more cautious about what I flash from now on. I'd be totally screwed if I bricked this phone. Anyway, hope you end up with something better out of this, like the HTC One.
Click to expand...
Click to collapse
Funny thing about the One... I was thinking about getting it but after this issue I will never look at another phone that doesn't have a removable sd card...
I think a key thing to note here is that you are flashing software that has been altered by someone you don't know and you can never be sure that things will work out. There's huge risks associated with rooting/unlocking your phone. If there wasn't HTC would warrant your phone regardless of what you do.
If you don't have an answer to the question "What will I do when I brick my phone?" don't root. Whenever modding anything, consoles, phones, set top boxes, I always assume that I will render it unusable. If that doesn't sit well with me, I don't modify it. That should be the general rule of thumb to follow.
Sent from my One X using xda app-developers app
3 words: Dropbox Camera Upload.
exad said:
I think a key thing to note here is that you are flashing software that has been altered by someone you don't know and you can never be sure that things will work out. There's huge risks associated with rooting/unlocking your phone. If there wasn't HTC would warrant your phone regardless of what you do.
If you don't have an answer to the question "What will I do when I brick my phone?" don't root. Whenever modding anything, consoles, phones, set top boxes, I always assume that I will render it unusable. If that doesn't sit well with me, I don't modify it. That should be the general rule of thumb to follow.
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
Very well said... I always get a little nervous when screwing with a new $500+ device.
Sent from my HTC One X using xda app-developers app
iElvis said:
3 words: Dropbox Camera Upload.
Click to expand...
Click to collapse
Thank you for the advice! I will remember that with my next phone.
I just use g+ to instantly upload my photos. Unlimited space is hard to argue with
Sent from my One X using xda app-developers app
phone not able to boot
guys please help me out I flashed stock root JB ROM after that my device wont boot just white screen with HTC logo. The phone boots into recovery but I wiped the sd card SD card mount error is being returned.
Clockworkmod recovery v6.0.3.1 S off
anuj.sherawat said:
guys please help me out I flashed stock root JB ROM after that my device wont boot just white screen with HTC logo. The phone boots into recovery but I wiped the sd card SD card mount error is being returned.
Clockworkmod recovery v6.0.3.1 S off
Click to expand...
Click to collapse
Install twrp 2.3.3.1 and reformat sd card with a pc. Move Rom to sd and reflash. And also what hboot? I know you said s-off bit did you fastboot the boot.img and see is that helped?
Sent from my HTC One X using xda app-developers app
31ken31 said:
Install twrp 2.3.3.1 and reformat sd card with a pc. Move Rom to sd and reflash. And also what hboot? I know you said s-off bit did you fastboot the boot.img and see is that helped?
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
thanks first of all I was on CMW, formatted the drive as computer prompted, lost the data but was able to flash the ROM and fastboot the boot image to phone.
Now only one problem the phone restarts and then goes to boot loop everytime I have to fastboot the boot image file.
DO I need to change the recovery and is there any way to by pass the fastboot process? Sorry for noob question