Related
I have a big problem !!! I had on my phone root s-off ROM Shooter Beats 1,7 and I flashed CWM 4.0.1.-shooteru via fastboot.
BUT when I was in fastboot USB I was thinking that I will try to have root with s-on on the screen on HBOOT. So I used command that I read in unroot section.
fastboot oem fastboot oem writesecureflag 3 and then reboot bootloader and my pfone is off and I cannot turn it on and dont know what to do :-( I am scared
you need to s-off your device again.using cmd
yes, I know, but I cannot turn on the phone.. I cannot do anything
Bricked
Sent from my HTC EVO 3D X515m using XDA App
There is nothing else to do?? :-(
What about warranty? If I cannot get to my phone, HTC cannot know if it doesnt work because of root, right? Do I have a chance?
What about a simple RUU? Just to try, and may it gives you s-on back and hboot and Kernel, so you maybe can boot into fastboot loader
Sent from my HTC EVO 3D X515m using XDA App
I cannot turn my phone on, I cannot go to bootloader, I cannot do anything. But when there is battery there is little red light on and when I remove battery it goes off. It is not blinking it is just permanent weak red colour (it is hardly to see).
When I connect Evo 3D to laptop, there is a sound that something is through USB connected, but the drivers are not regognized (in system there is only something QHUSB_DLOAD)
I was trying cmd and fastboot reboot and it is waiting for device
I was trying adb restart and nothing..
when I try RUU, it cannot find my device
Castellano2 said:
I cannot turn my phone on, I cannot go to bootloader, I cannot do anything. But when there is battery there is little red light on and when I remove battery it goes off. It is not blinking it is just permanent weak red colour (it is hardly to see).
When I connect Evo 3D to laptop, there is a sound that something is through USB connected, but the drivers are not regognized (in system there is only something QHUSB_DLOAD)
I was trying cmd and fastboot reboot and it is waiting for device
I was trying adb restart and nothing..
when I try RUU, it cannot find my device
Click to expand...
Click to collapse
try to use a RUU
If all fails send it back to HTC and say it stopped working overnight
Sent from my HTC EVO 3D X515m using XDA App
Did you have recovery? If you do, the problem you ran into might be an easy one.
1. Plug your phone to a power source (Long press the power button for few seconds and see if the light is on)
2. If the light is on, press the camera button (may be few times if first time doesn't work) and wait.
3. The first two steps should have already taken you into the boot screen. If it doesn't, then sorry.
thre3aces said:
If all fails send it back to HTC and say it stopped working overnight
Sent from my HTC EVO 3D X515m using XDA App
Click to expand...
Click to collapse
Try to push camera, volume up+down and power Buttonand hold it down for a few seconds and see if the phone boots. Then plug in charger and charge it. So you can see if the battery was dead!
Thank you guys for advices but
1, I tried use RUU and as I said it doesnt find my device (there are not drivers anymore)
2, volume plus camera button and so on.. this problem I solved many times.. it was problem with CWM 5.0.2. but I have there 4.0.1. which has no battery bug.
My phone doesnt work and cannot go on.
I googled little bit and find out that people with Desire HD had the same issue and they sent it to service and got new phone. I hope it will be the same I love my phone so muuuuuuch..
I think the problem is that I would need to get drivers for my mobile to get sdk ready.. but :/
Questions or Problems Should Not Be Posted in the Development Forum
Please Post in the Correct Forums
Moving to Q&A
Castellano2 said:
Thank you guys for advices but
1, I tried use RUU and as I said it doesnt find my device (there are not drivers anymore)
2, volume plus camera button and so on.. this problem I solved many times.. it was problem with CWM 5.0.2. but I have there 4.0.1. which has no battery bug.
My phone doesnt work and cannot go on.
I googled little bit and find out that people with Desire HD had the same issue and they sent it to service and got new phone. I hope it will be the same I love my phone so muuuuuuch..
I think the problem is that I would need to get drivers for my mobile to get sdk ready.. but :/
Click to expand...
Click to collapse
bricked...there are a few reports here that did the same procedure and bricked it too.
I really cant understand why people play with those things although they have no idea of what they are risking.
..i mean, you could have been very proud that you got a device which csn achieve s-off. Thousands still dteaming of it.
Why the hell you wanted to went back to son and root?
If you would read through the forums you should have nitice, that you cant flash custom kernels easily - just with flash img gui. And flashing radios is
Is completly not possible with son.
Son makes life so much more painful.
And you still did it...sry tried it
Sent from my HTC EVO 3D X515m using xda premium
j4n87 said:
bricked...there are a few reports here that did the same procedure and bricked it too.
I really cant understand why people play with those things although they have no idea of what they are risking.
..i mean, you could have been very proud that you got a device which csn achieve s-off. Thousands still dteaming of it.
Why the hell you wanted to went back to son and root?
If you would read through the forums you should have nitice, that you cant flash custom kernels easily - just with flash img gui. And flashing radios is
Is completly not possible with son.
Son makes life so much more painful.
And you still did it...sry tried it
Sent from my HTC EVO 3D X515m using xda premium
Click to expand...
Click to collapse
I know, I read through forum and find out that problem with QHUSB_DLOAD is always dead end. You cannot understand why people do that? I read a lot of topic where people have written that I tried to unroot their phone because of warranty and in finally step - whitesecure flag 3 - it bricked. They do it exactly how it was in "manual", so they have just bad luck.
I want to have s-on because my cable conector was wrong and I was afraid when I won´t connect my phone to computer, I cannot remove root and my quarantee will finished.. But I didnt flash stock Rom because I want to give it on sd card and when my usb cable won´t work, I could just reflash to stock ROM from my backup..
Right now my phone is in service..
Hello everyone,
I seem to be facing a singular issue, but I imagine it is much my fault, and just wanted a confirmation from those more experienced with the device...
I bought an Incredible 4G from eBay, that already had the a copy of Avatar on it, I believe almost the latest update. So when I confirmed the device worked after charging the battery, I flashed the latest copy of Avatar and the JB Gapps, and everything seemed hunkydory.
So, after that, I put in my old SIM, deactivated as I was using a non-4g device, and put it in the Incredible 4G. I started the activation process on the phone, following prompts to reboot the phone (Note: I did not know about CM10.1's issue regarding activation at the time, so one of the possible problems.)
After seemingly failing to activate after the first reboot, I "tried again" and it went down for another reboot. And it stayed down. Completely. I cannot get the phone to start, after charging the battery separately, cannot get into bootloader, nothing. I get QHSUSB_DLOAD when plugged into a computer using USB, but that's it.
A few notes: first time I started up, the screen went to recovery. I didn't think that was an issue; I factory reset from there, and rebooted into Avatar. Second issue: I used ROM updater on the phone to download and install the recovery, as I imagined that there was an automatic checksum done in the process (perhaps it was imagined?), and so when it went to flash, it had some issue, which didn't seem like a problem with the download, and I went through flashing it normally through recovery. Sorry I can't provide more details on that, but everything seemed to work all right after rebooting.
Finally, and this may be irrelevant, I put a 64GB SDXC card in the phone, I had already realized that it could not natively support exFAT, and so left the card in the device until the next time I could boot to recovery to partition it, and went through the activation process with the card inserted and not recognized.
So, I imagine that I have a hard brick, but can't tell if it's completely my fault, because it bricked in a peculiar fashion, at least from what I can tell, as no one seems to have encountered a similar issue after searching for the last 5 days.
If there's any hope for recovery, I would really appreciate some help regarding the device. I'm willing to provide some more info if necessary, and I'd like to find out sooner rather than later if it's a lost cause.
Thanks for any help you guys can give. XDA devs are awesome.
Quite the predicament. Just to clarify, have you tried the following?
1) Remove that super-big MicroSD
2) Remove SIM
3) Remove battery and wait a few minutes; also press the power button while phone is off
4) Only re-inserting the battery, hold vol-down and then hold power until screen comes on (then release power but keep holding vol-down)
I have tried them all; no SIM or SD card has been in there since the issue started. I hadn't tried pushing the power button while the battery was out, but it doesn't seem to change anything. So far, no reaction whatsoever even when holding power + vol down for a few minutes.
ChiqOmar said:
I have tried them all; no SIM or SD card has been in there since the issue started. I hadn't tried pushing the power button while the battery was out, but it doesn't seem to change anything. So far, no reaction whatsoever even when holding power + vol down for a few minutes.
Click to expand...
Click to collapse
Looks like you have a very hard to solve brick, I would like to help, have you tried using fastboot, I mean connected to pc and on that screen issue a fastboot command, also upload a picture of it please since this is new kind of brick, also I found this, our device is supported,
http://unlimited.io/qhsusbdload.htm
Sent from my ADR6410LVW using xda app-developers app
jose51197 said:
Looks like you have a very hard to solve brick, I would like to help, have you tried using fastboot, I mean connected to pc and on that screen issue a fastboot command, also upload a picture of it please since this is new kind of brick, also I found this, our device is supported,
http://unlimited.io/qhsusbdload.htm
Sent from my ADR6410LVW using xda app-developers app
Click to expand...
Click to collapse
You can't do fastboot if you can't reach the bootloader, and I've been assured the unlimited.io tool will not help for DLOAD resulting from non-racun related procedures.
Reading forum posts about QHSUSB_DLOAD suggest either jtag is necessary (which might not be worth it considering the phone can be purchased for $150 on ebay) or some strange strokes of luck after letting the phone sit for a bit. ChiqOmar, sorry I don't have great advice; do all the reading you can about QHSUSB_DLOAD mode.
jose51197 said:
Looks like you have a very hard to solve brick, I would like to help, have you tried using fastboot, I mean connected to pc and on that screen issue a fastboot command, also upload a picture of it please since this is new kind of brick, also I found this, our device is supported,
http://unlimited.io/qhsusbdload.htm
Sent from my ADR6410LVW using xda app-developers app
Click to expand...
Click to collapse
yes sounds like he is stuck in QSHUSB_DLOAD mode, but i don't know if the resolutiion on unlimited.io will help him or not.they say it's not supported for other reasons other than from running their exploit. it might work though.
mdmower said:
You can't do fastboot if you can't reach the bootloader, and I've been assured the unlimited.io tool will not help for DLOAD resulting from non-racun related procedures.
Reading forum posts about QHSUSB_DLOAD suggest either jtag is necessary (which might not be worth it considering the phone can be purchased for $150 on ebay) or some strange strokes of luck after letting the phone sit for a bit. ChiqOmar, sorry I don't have great advice; do all the reading you can about QHSUSB_DLOAD mode.
Click to expand...
Click to collapse
Maybe port HTC unbricking project to our device, and try to help him using it, since he can't do nothing about it right now, ChiqOmar, you ok with testing it ?, btw download ubuntu connect phone and see if the partitions get mounted, btw looks like you need to flash hboot from that mode, that's all then ruu, I have all the tools to do it if you want to
Sent from my ADR6410LVW using xda app-developers app
mdmower said:
You can't do fastboot if you can't reach the bootloader, and I've been assured the unlimited.io tool will not help for DLOAD resulting from non-racun related procedures.
Reading forum posts about QHSUSB_DLOAD suggest either jtag is necessary (which might not be worth it considering the phone can be purchased for $150 on ebay) or some strange strokes of luck after letting the phone sit for a bit. ChiqOmar, sorry I don't have great advice; do all the reading you can about QHSUSB_DLOAD mode.
Click to expand...
Click to collapse
i was able to bring my rezound back after a hard brick with a hex edited hboot that went bad with this tool but ported for rezound. its worth a try?
Thanks for the help everyone. Yes, although it states quite clearly that the Unlimited.io tool is only meant for devices bricked using their tool, I tried it anyway; obviously, nothing changed.
Though JTAG sounds interesting, I have no idea how to get started with that...nor do I really know if I want to travel down that route just now.
The HTC Unbricking Project sounds promising, but also no idea how to get started as it has not been ported for our device. The partitions don't get mounted in Ubuntu, as I connected it to the computer to use the Unlimited.io tool.
Finally, regarding the nature of the brick itself, I really wish I could pinpoint the issue better to help others if a similar issue happens in the future.
I am actually waiting on a battery, (ordered before I got the phone) and so will try that to see if anything changes.
Thanks again everyone. I've got a feeling I might have to write this one off pretty soon.
ChiqOmar said:
Hello everyone,
I seem to be facing a singular issue, but I imagine it is much my fault, and just wanted a confirmation from those more experienced with the device...
I bought an Incredible 4G from eBay, that already had the a copy of Avatar on it, I believe almost the latest update. So when I confirmed the device worked after charging the battery, I flashed the latest copy of Avatar and the JB Gapps, and everything seemed hunkydory.
So, after that, I put in my old SIM, deactivated as I was using a non-4g device, and put it in the Incredible 4G. I started the activation process on the phone, following prompts to reboot the phone (Note: I did not know about CM10.1's issue regarding activation at the time, so one of the possible problems.)
After seemingly failing to activate after the first reboot, I "tried again" and it went down for another reboot. And it stayed down. Completely. I cannot get the phone to start, after charging the battery separately, cannot get into bootloader, nothing. I get QHSUSB_DLOAD when plugged into a computer using USB, but that's it.
A few notes: first time I started up, the screen went to recovery. I didn't think that was an issue; I factory reset from there, and rebooted into Avatar. Second issue: I used ROM updater on the phone to download and install the recovery, as I imagined that there was an automatic checksum done in the process (perhaps it was imagined?), and so when it went to flash, it had some issue, which didn't seem like a problem with the download, and I went through flashing it normally through recovery. Sorry I can't provide more details on that, but everything seemed to work all right after rebooting.
Finally, and this may be irrelevant, I put a 64GB SDXC card in the phone, I had already realized that it could not natively support exFAT, and so left the card in the device until the next time I could boot to recovery to partition it, and went through the activation process with the card inserted and not recognized.
So, I imagine that I have a hard brick, but can't tell if it's completely my fault, because it bricked in a peculiar fashion, at least from what I can tell, as no one seems to have encountered a similar issue after searching for the last 5 days.
If there's any hope for recovery, I would really appreciate some help regarding the device. I'm willing to provide some more info if necessary, and I'd like to find out sooner rather than later if it's a lost cause.
Thanks for any help you guys can give. XDA devs are awesome.
Click to expand...
Click to collapse
Just got same issue, though for me I installed avatar rom, then rebooted at some point, but instead it hard bricked, can't charge pull battery out/in boot back up removed sim sd card didn't help me either. Any progress yet, or help?
Ill try to get a working htc unbriking Project soon for you guys to try, both please use ubuntu and have a working USB cable, I'm gonna try to reinstall hboot, also have teamviewr installed, also please tell me if you guys are supercid, also no usb 3.0 cable or port please
Sent from my ADR6410LVW using xda app-developers app
Some Information
jose51197 said:
Ill try to get a working htc unbriking Project soon for you guys to try, both please use ubuntu and have a working USB cable, I'm gonna try to reinstall hboot, also have teamviewr installed, also please tell me if you guys are supercid, also no usb 3.0 cable or port please
Sent from my ADR6410LVW using xda app-developers app
Click to expand...
Click to collapse
I'm on Ubuntu 13.04 64 Bit, I have a usb cable, Anker Battery Expert separate battery charger. And my Phone is S-OFF DirtyRacun Currently still hard bricked (Not by the Racun though) don't have any 3.0's, i have a onn usb cable and the stock, I also have a Ubuntu 12.04.2 LTS 32 Bit Live DVD. Battery Charging using a battery pack charger. Won't charge through USB
OldNut5 said:
I'm on Ubuntu 13.04 64 Bit, I have a usb cable, Anker Battery Expert separate battery charger. And my Phone is S-OFF DirtyRacun Currently still hard bricked (Not by the Racun though) don't have any 3.0's, i have a onn usb cable and the stock, I also have a Ubuntu 12.04.2 LTS 32 Bit Live DVD.
Click to expand...
Click to collapse
pm me with gtalk email and ill see what i can do, also install teamviewr
OldNut5 said:
I'm on Ubuntu 13.04 64 Bit, I have a usb cable, Anker Battery Expert separate battery charger. And my Phone is S-OFF DirtyRacun Currently still hard bricked (Not by the Racun though) don't have any 3.0's, i have a onn usb cable and the stock, I also have a Ubuntu 12.04.2 LTS 32 Bit Live DVD. Battery Charging using a battery pack charger. Won't charge through USB
Click to expand...
Click to collapse
I lost my first Dinc 4G LTE after I installed CM10.1, was working great for a while and just blinked off, never to recover. No charge light, no response to power button. I also had an aftermarket battery (Hyperion), but it would get so hot charging I replaced it with an OEM HTC battery. I think that damaged the phone.
Since I work with analog electronics, I assume something in the power path physically burned out. I never tried to talk to it via USB, but just cabling it to a computer generates no response.
I went back to the Stock RUU.zip from the unlimited.io site to get the firmware update. During the update it just sort of died. Now I can't get it to charge or get into the bootloader. Help! Please!:crying:
Hello friends and thanks for reading. Glad to finally be a part of one of the most highly respectable, trustworthy, and knowledgeable development sites on the Internet. Not an ass kisser, just feel that if you've used a website to fix or mod ALOT of different things that you didn't know how to fully do on your own, and you also learned how and why, you should express some appreciation. I've searched and searched but I'm pretty sure this is one of the more rare bricks. Not one of those did u hold volume down and OMG theres the hboot menu threads lol. So here goes...
Modification Procedure:
JuopunutBear S-Off
Hboot 1.50.5050
Radio 1.09.00.0706
Recovery TWRP v2.2.0
Angry Bean Rom CM 10.1 build 06.07.13
Joe Blow Hacks
Computer rig:
Ubuntu 12.04 x32 & Windows 8 x32 dual boot
Asus A8AE-LE
Amd Athlon 64 3500+
2gb Pc3200
Tools / Testing Equipment:
- 2 identical model Evo's
Model: PG86100
- 2 identical batteries (all working)
- Both phones have had the same exact procedure done
- The other Evo that went through the procedure is still working fine and I use it as my main phone
What it Does / Doesn't do:
- Cant get to hboot
- Cant get to recovery
- With battery in and usb charger plugged in, and not hitting any buttons including power, there is a solid red light that would indicate normal charging. I don't believe it is because the other Evo, after letting the bad one supposedly charge the battery, says the battery is low
- With the usb charger unplugged and a known charged battery placed in the phone and me hitting power once, it vibrates once and the home, menu, back and search light up. Screen shows absolutely nothing. holding volume up down and power in this state makes the phone vibrate once and all the lights go out. Then after a second adb sees it again as device offline
- When I boot using either Windows or Ubuntu, the command “adb devices” shows the serial and offline
- When I boot the working Evo using either Windows or Ubuntu, the command “adb devices” shows the serial and device (as it should)
- Adb and fastboot run fine with the working Evo
- Adb is about useless on the dead Evo. Every command = error device offline
Things I tried that failed:
- Volume up + power it vibrates once and the home, menu, back and search light up
- Volume down + power the phone doesn't boot (can't access hboot)
- Charger in the phone first with no battery. Then I held volume up and down and inserted the battery. Phone just goes back to the solid red light and gets hot. Screen shows absolutely nothing
(yes I took my time do to the fact that most problems occur do to a lack of patience and user error :silly:
- Ruu (no fastboot)
- ./brickdetect.sh Device can't be detected. Check connections
I usually got this type of thing in the bag but this time I'm just not getting anywhere. Any and all input would be greatly appreciated. Is there something not right here in this Evo setup that I'm not seeing or in your opinion do u think that the working Evo is in “harms way”? I keep wondering...Thanks
What happened to the phone before it got into its current state? Did this happen while you were doing the S-off procedure?
Sent from my Evo 3D CDMA using xda premium
The Fer-Shiz-Nizzle said:
What happened to the phone before it got into its current state? Did this happen while you were doing the S-off procedure?
Sent from my Evo 3D CDMA using xda premium
Click to expand...
Click to collapse
No thats the thing. I did both Evo procedures at the same time. Same files and everything. S-off went great for both phones. The phone was being used as a dlna client. Right before it "bricked", it was watching The Walking Dead. Would you consider this to be a brick, as i don't want to be misleading people. Theres a lotta posts that throw around bricked and hard bricked like there the same when there not...
Noxus001 said:
No thats the thing. I did both Evo procedures at the same time. Same files and everything. S-off went great for both phones. The phone was being used as a dlna client. Right before it "bricked", it was watching The Walking Dead. Would you consider this to be a brick, as i don't want to be misleading people. Theres a lotta posts that throw around bricked and hard bricked like there the same when there not...
Click to expand...
Click to collapse
I mean ya i know it's bricked lol but should it be defined as hard bricked?...
Is it getting hot around cameras while it's on charger?
If it is your motherboard died
Yes it is. Installed a a known good board inside the dead evo and I'm currently using it to post.
Sent from my Evo V 4G using xda premium
Noxus001 said:
Yes it is. Installed a a known good board inside the dead evo and I'm currently using it to post.
Sent from my Evo V 4G using xda premium
Click to expand...
Click to collapse
So it's all fine now?
Yes all is well. Thanks for all the help
Sent from my Evo V 4G using xda premium
Just a coincidence that the board died?
Noxus001 said:
Yes it is. Installed a a known good board inside the dead evo and I'm currently using it to post.
Sent from my Evo V 4G using xda premium
Click to expand...
Click to collapse
Hi everyone.
So, what do you guys think happened here? Did the motherboard just happen to die, or was its demise hastened by modifying the phone?
Good to read that you solved your problem, though. So, where did you get a replacement board, just off one of the usual sell yours buy someone else's type sites?
Ok so last night I transferred some files with otg cable. Unmounted and then went to put it on charger and it does not recognize the charger. It did charge after I powered it down. But when the phone is on it doesn't recognize anything plugged into the usb port. Anyone have any suggestions? And if not how do I run a ruu or something to get back to stock for warranty without a connection to pc?
Sent from my HTC One using Tapatalk 4
Quick update. I am on 3.09.401.1 firmware and a 2.24.401.8 based rom. Not sure if that has anything to do with it but it will charge in recovery mode but not booted up. So seems like a firmware/software issue. Is there any way to flash firmware without using usb to pc? Because it won't recognize the usb at all.
Sent from my HTC One using Tapatalk 4
Clselfridge said:
Quick update. I am on 3.09.401.1 firmware and a 2.24.401.8 based rom. Not sure if that has anything to do with it but it will charge in recovery mode but not booted up. So seems like a firmware/software issue. Is there any way to flash firmware without using usb to pc? Because it won't recognize the usb at all.
Sent from my HTC One using Tapatalk 4
Click to expand...
Click to collapse
Weird problem. Not sure if it will work but you can try "flashify" from the play store to flash firmware, etc without usb. Keep us posted on your results.
Also see if you can access it through bootloader. You might be able to RUU. Alternatively, factory reset and install ROM in recovery. Or try side adb in recovery..
Clselfridge said:
Ok so last night I transferred some files with otg cable. Unmounted and then went to put it on charger and it does not recognize the charger. It did charge after I powered it down. But when the phone is on it doesn't recognize anything plugged into the usb port. Anyone have any suggestions? And if not how do I run a ruu or something to get back to stock for warranty without a connection to pc?
Sent from my HTC One using Tapatalk 4
Click to expand...
Click to collapse
I'm currently using the same firmware ROM base combination as you with no issues. Are you using the charger that came with your phone, have you replaced the usb cable to make sure it isn't faulty?
Sent from my HTC One using xda app-developers app
suntzu said:
Weird problem. Not sure if it will work but you can try "flashify" from the play store to flash firmware, etc without usb. Keep us posted on your results.
Also see if you can access it through bootloader. You might be able to RUU. Alternatively, factory reset and install ROM in recovery. Or try side adb in recovery..
Click to expand...
Click to collapse
I am going to look into flashify. That sounds interesting. I have tried getting the thing to pick up the usb in hboot. But no luck so far.
igglesphilsfan said:
I'm currently using the same firmware ROM base combination as you with no issues. Are you using the charger that came with your phone, have you replaced the usb cable to make sure it isn't faulty?
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
I have tried three different HTC branded charger/cable combinations. With no luck while booted up. I charged to 100% while shut off.
I have been running this combo for a week or something. Ever since the firmware hit the forums. And had no issues until two nights ago when this first started giving me grief... so I don't know what has caused it.
I also posted this over in the international forums and there's a guy over there with the same issue.
Sent from my HTC One using Tapatalk 4
well i am downloading a stock backup and i have a stock recovery not sure how to get them both to work... because i have to flash the stock rom with twrp and then how do i get the stock recovery flashed with a stock rom.... i will figure it out. anyway my plan is to try to take an ota and have that change the firmware and then i will know if i have a hardware issue or a software issue.
Lol. Now I'm not sure what to do. I reverted back to stock rom and recovery and then realized the touch drivers I have aren't compatible.... But I am booted up and plugged into the pc and it is charging but not coming up on the pc as a device. I don't know if debug mode is on because I am stuck at the first setup screen... Ahh I can't seem to catch a break here...
Sent from Tapatalk
Clselfridge said:
Lol. Now I'm not sure what to do. I reverted back to stock rom and recovery and then realized the touch drivers I have aren't compatible.... But I am booted up and plugged into the pc and it is charging but not coming up on the pc as a device. I don't know if debug mode is on because I am stuck at the first setup screen... Ahh I can't seem to catch a break here...
Sent from Tapatalk
Click to expand...
Click to collapse
Ruu back to stock AT&T and start over.
scrosler said:
Ruu back to stock AT&T and start over.
Click to expand...
Click to collapse
That's what I am trying to do... However I can't get the pc or the phone to recognize the connection. I have been messing with this thing and getting nowhere for so long I feel like I'm just banging my head agains a wall...
Sent from Tapatalk
Clselfridge said:
That's what I am trying to do... However I can't get the pc or the phone to recognize the connection. I have been messing with this thing and getting nowhere for so long I feel like I'm just banging my head agains a wall...
Sent from Tapatalk
Click to expand...
Click to collapse
...have you tried booting into safe mode and then see if it is recognized? Just a shot in the dark. :fingers-crossed:
igglesphilsfan said:
...have you tried booting into safe mode and then see if it is recognized? Just a shot in the dark. :fingers-crossed:
Click to expand...
Click to collapse
How do I get into safe mode?
Sent from Tapatalk
Press the power button until the power options open. Tap and hold POWER OFF on the screen and the phone should ask if you'd like to boot into safe mode but if your touch panel is not working for you this is not going to work.
Sent from my HTC One using xda app-developers app
igglesphilsfan said:
Press the power button until the power options open. Tap and hold POWER OFF on the screen and the phone should ask if you'd like to boot into safe mode but if your touch panel is not working for you this is not going to work.
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Correct. I have totally screwed myself I think. I think I basically at this current time have a fairly lightweight brick that lights up. I have no touch capabilities at all and nothing recognized when plugged into PC. I have tried plugging into a windows 8 and also a Ubuntu machine with no dice in fast boot or adb....
Sent from Tapatalk
I dont think it is prob with some ROM. I used HTC One with stock rom (official stock by HTC) and after three months my phone stopped charging and also stop USB connection. I googled it and it was universal prob and also HTC knows about that.
See this http://forum.xda-developers.com/showthread.php?t=2417377
Phone acted very strange. Details are in above link. And also there are 2 or 3 threads more like this.
sandeep.mjs said:
I dont think it is prob with some ROM. I used HTC One with stock rom (official stock by HTC) and after three months my phone stopped charging and also stop USB connection. I googled it and it was universal prob and also HTC knows about that.
See this http://forum.xda-developers.com/showthread.php?t=2417377
Phone acted very strange. Details are in above link. And also there are 2 or 3 threads more like this.
Click to expand...
Click to collapse
Did you end up getting it resolved and if so how?
I don't think AT&T will look kindly on me for having it unlocked and s-off and for having a rom/firmware mismatch...
Sent from Tapatalk
Clselfridge said:
Did you end up getting it resolved and if so how?
I don't think AT&T will look kindly on me for having it unlocked and s-off and for having a rom/firmware mismatch...
Sent from Tapatalk
Click to expand...
Click to collapse
Unless the OTA adapter screwed up the USB connector pins for data but not power, then you should be able to recover. However like stated there has been a few reports of failed USB connectors.
Does there seem like there is any damage to the usb pins in the connector on the phone?
Did you make sure to have the HTC device drivers installed on your PC before trying ADB. Do you have a Windows 7 PC to try?
crushalot said:
Unless the OTA adapter screwed up the USB connector pins for data but not power, then you should be able to recover. However like stated there has been a few reports of failed USB connectors.
Does there seem like there is any damage to the usb pins in the connector on the phone?
Did you make sure to have the HTC device drivers installed on your PC before trying ADB. Do you have a Windows 7 PC to try?
Click to expand...
Click to collapse
So far I have tried on win8 winxp and Ubuntu.on the windows pcs the drivers were definitely installed. No dice on any of them. I am thinking the connector must be messed up. I can't see anything obvious looking at it but the fact that on three pcs one of them running Linux didn't find the phone but will charge it is pretty definitive. I don't have the money to pay for repairs due to having "tampered" with the phone(even though it doesn't say that) it is an AT&T phone with s-off and unlocked and a 1.55 hboot and has a inverted splash screen. Pretty obvious...
Sent from Tapatalk
Clselfridge said:
So far I have tried on win8 winxp and Ubuntu.on the windows pcs the drivers were definitely installed. No dice on any of them. I am thinking the connector must be messed up. I can't see anything obvious looking at it but the fact that on three pcs one of them running Linux didn't find the phone but will charge it is pretty definitive. I don't have the money to pay for repairs due to having "tampered" with the phone(even though it doesn't say that) it is an AT&T phone with s-off and unlocked and a 1.55 hboot and has a inverted splash screen. Pretty obvious...
Sent from Tapatalk
Click to expand...
Click to collapse
If you boot the phone into the bootloader without the cable attached it should come up and say fastboot. When you attach the USB cable does the display on the phone change to fastboot USB or stay only fastboot?
crushalot said:
If you boot the phone into the bootloader without the cable attached it should come up and say fastboot. When you attach the USB cable does the display on the phone change to fastboot USB or stay only fastboot?
Click to expand...
Click to collapse
Only fastboot. Never changes.
Sent from Tapatalk
Clselfridge said:
Only fastboot. Never changes.
Sent from Tapatalk
Click to expand...
Click to collapse
Yep, then it seems the pinouts on the USB connector have been damaged. Bummer.
On the plus side consider this: AT&T will probably still give you device exchange without charging you a fee. First, they mostly don't care about users modding their phones. Secondly there are so many exchange requests coming into them for the One, that all the defective units will just be sent back to HTC directly by AT&T and at that point HTC is not going to bother to go back to AT&T and say listen this list of devices were modified. If they did, that would create a backlog on work for AT&T to match the records to owners and then contacting them and trying to prove that the user did this so far removed from the exchange that it doesn't make business sense to them.
I have seen AT&T users report that they have sent in devices that were extremely modified and obvious, but AT&T proceeded with the exchange anyway because they would rather keep you as a happy customer than spending time trying to prove what you did was the only cause of the failure. Users have even sent back total bricks that they created by doing something stupid and AT&T still replaced the device without question.
When you modded the phone, that basically ended AT&T's obligation to help you with any service/software related issues, but the modding did not void the hardware warranty and it seems your device has a hardware issue that was unlikely caused by the software modifications.
The key in your case would be to do the defective device exchange via phone/mail and not via the walk in device service center.
If you don't want to do this because of the possible risk of flagging by them, then I may be willing to buy your bricked device if you are not going to do anything with it. PM if interested.
Made the mistake of bricking my Att HTC ONE M7. Ive tried everything to revive this damn thing, did loads of research to see if anyone came up with a solution with no luck.
I was restoring my backup phone (Galaxy S2) to convert my mom to an android and get her away from that pile of **** iPhone. I downloaded a philz recovery from the xda app on my ONE for the S2 (which is something I've always had a rule against for this reason).
To make a Long story longer I, for some reason, thought it was for my ONE. Flashed it in recovery (TWRP) "Failed" then I realized what i did. But it failed, I then flashed a bootanimation. "Success"..
Restarted my device but it never came back on. No lights, screen, or response from any combination of buttons.
I guess the recovery flash ,even though it failed, was the nail in the coffin. I just can't believe it died that easy even though it let me flash a bootanimation. Not paying attention just cost me a lot of money and loads of pride.
It shows up qhsusb_dload in device manager. I e-mailed HTC and I'm gonna try a warranty claim. Also talked to someone about Jtag.
If anyone wants to attempt a solution Im game.. I will keep this post up to date with what run around HTC gives if I go that route. If anyone cares...
"IF IT AIN'T BROKE, FIX IT UNTIL IT IS...
HTC ONE Rooted, Unlocked,
Tampered Just a Tad,
Maximus HD 4.4 KitKat
Died an Honorable Death.. due to
Lapse in judgement, temporary
Mental Retardation..
Sent using my HTC One XL backup, fill in,
The ONE I can always count on...
Are you able toqccess fastboot or TWRP?
Sent from my HTC One using xda app-developers app
No, cant access anything.. black screen. No response.
Sent from my HTC One X using xda app-developers app
Update:: HTC told me to do this combination of buttons that I haven't read anywhere else. It didn't work for me but it might be a solution for others experiencing the dead black screen issue.
•Charge the device for at least 10 minutes
•With the device truly OFF while still being plugged into the wall outlet, push in and hold volume up and volume down AND power button, for 2 minutes.
•Let go. Device will boot up, and battery/charging logic are re-calibrated.
Sent from my HTC One X
https://www.youtube.com/watch?v=db5f3If-2Jw&feature=youtube_gdata_player
Idk if this I'll worth... Wish you the best. Reading more in dept about your problem, you are in a touth position
Sent from my HTC One using xda app-developers app
Sending my phone in for Jtag via Mobile Tech Videos. I've only heard good things (on average) gonna send it off Monday and we shall see...
Sent from my old faithful HTC One X
I am also stuck
i am also stucked QHSUSB DLOAD really worried please help if any body is having solution
Does your charge led come on when it's plugged into the wall? Do any lights at all work?
Sent from my HTC One_M7
rasoolakhter said:
i am also stucked QHSUSB DLOAD really worried please help if any body is having solution
Click to expand...
Click to collapse
Their is a fix now .. I did mine today
QHSUSB_DLOAD Fix
This will fix devices which were bricked due to firmware incompatibility. This can be caused with the way HTC handles the firmware updates in it's m7's OTAs. If you've been flashing from a 3.x firmware to a 5.x firmware via OTA, or manually, you most likely have a device stuck in QHSUSB_DLOAD. This tool is for you
http://forum.xda-developers.com/showthread.php?t=2770684
Prerequisites
the appropriate package for the device
a supported bricked device
a usb cable
fastboot
distro utils: md5sum, strings, tail, grep, unzip ( all included in most linux distros)
some basic linux experience
root access on a linux machine
patience
DISCLAIMER: We do NOT guarantee that this method will work for you, or that it is flawless. We are also not responsible if your phone is completely dead after the procedure, or your house burns down because your phone exploded. You are doing this in YOUR OWN RISK.
Instructions
Boot the linux box and download the appropriate package for the device.
Remove the sim card from the phone. Do not connect yet
Extract the package in your working directory
Open up a terminal and cd to that directory
Run revive.sh as root and connect the device
Code:
sudo ./revive.sh
The procedure is automated. At the end of the unbrick process, you will need to charge the device fully and then flash one of the full firmwares bundled, as pointed from the script. This is crucial to ensure device stability.
Click to expand...
Click to collapse
The problem with mine is that after I bricked it I sent it to be jtaged. When I got it back it wouldn't unlock to any network. No matter what it asks me for an unlock code.
Maybe I can run this on my phone and restore the emmc that cross checks the modem.???
What harm could it do
Sent from my HTC One
cannonofcourse said:
The problem with mine is that after I bricked it I sent it to be jtaged. When I got it back it wouldn't unlock to any network. No matter what it asks me for an unlock code.
Maybe I can run this on my phone and restore the emmc that cross checks the modem.???
What harm could it do
Sent from my HTC One
Click to expand...
Click to collapse
where did u send?
How much was it ?
I sent it to mobile tech videos... I heard good stuff about them but don't send it to them if you want your phone to work again. I don't remember what it cost me but I wish I would have waited for this unbrick method. The jtag process fried my modem or part of my motherboard. Try the unbrick method. People have had a lot of luck with that.
HTC ONE M-7
cannonofcourse said:
I sent it to mobile tech videos... I heard good stuff about them but don't send it to them if you want your phone to work again. I don't remember what it cost me but I wish I would have waited for this unbrick method. The jtag process fried my modem or part of my motherboard. Try the unbrick method. People have had a lot of luck with that.
HTC ONE M-7
Click to expand...
Click to collapse
i tried that method but after the command i get a message error that my device isn't found