Related
Okay, I did some searching and I didn't really find what I needed in my circumstance. I've read the threads about unrooting my thunderbolt buy my situation is a bit more specific than the generic unrooting procedures that I've seen.
So, through some weird circumstances my thunerbolt's screen doesnt turn on anymore. It ended up being dropped about a foot and the screen just died on me. there is no physical damage to the phone (i.e. the screen isn't cracked or bleeding). I already talked to Verizon reps about it, and I might be able to turn it in for warranty replacement. (If not, I'll just have to use my upgrae ). but to turn it for warranty I will obviously have to remove root. I haven't flashed anything to my phone for about 3 or 4 months so I know I didn't kill the screen by messing something up.
Here's the catch:
-my screen is dead so i cant really see what im doing on the phone.
-for some reason my computer cant recognize my phone. it keeps telling me that "the USB evice has malfunctioned".
-my SD card still reads in my card reader on my PC.
So basically I don't really have any idea how i could possibly go about unrooting my phone. Any ideas or suggestion are welcome. Maybe a donation to the contributors that help me? If not I will sadly have to leave the realm of the thunderbolt and I will use my upgrade If needed. (I would much rather keep my Thunderbolt than have to upgrade to like the nexus or something...I dont like them....)
Thanks in advanced
Buy the thundebolt restore app from the market
Sent from my ADR6400L using XDA App
donnyp1 said:
Buy the thundebolt restore app from the market
Sent from my ADR6400L using XDA App
Click to expand...
Click to collapse
Okay, but how can I use it with out a working screen?
thanks
That i dont know. But if the screen isnt working, why unroot?
Sent from my ADR6400L using XDA App
so that i can turn it in for a warranty claim
If it were me, I'd try the warranty route. If the screen/phone? wont turn on, how can someone tell if rooted? Worst case, you'd have to use your upgrade like you said. Hope you get it figured out, good luck
Tapatalkn with my Thunderbolt
Classicmm said:
If it were me, I'd try the warranty route. If the screen/phone? wont turn on, how can someone tell if rooted? Worst case, you'd have to use your upgrade like you said. Hope you get it figured out, good luck
Tapatalkn with my Thunderbolt
Click to expand...
Click to collapse
Exactly
Sent from my ADR6400L using XDA App
Can't they like hook it up to their computer or something like that and find that the phone is rooted?
Maybe, but didn't you say your PC doesn't recognize phone anymore? From what I've read, don't quote me on this, Big Red does not really do an in depth check before sending out for repair. Check for root, sure they do but again no screen/power, who knows then. Repair people could prolly care less. Again, nothing in stone here, just stuff I picked reading here n there.
Tapatalkn with my Thunderbolt
Yeah. I went into the store and they shipped me a new warranty replacement phone. Although they did this, I'm still a bit apprehensive about sending it back while it's still rooted. So my original request still stands: I would like to know of a possible way to unroot it.
Thanks
Please help read!!
So my HTC amaze died on me about 2 days ago I was listening to my music in my car connected through Bluetooth then a cop passed by and everything shut off haha coincidence haha anyway went home had no service like absolutely nothing thought nothing of it and went to sleep, next morning still nothing and ever since now its dead. Called HTC they said most likely its T-Mobile not the phone but they sent me a replacement back cover (which is cool) because the antennas are on the back anyway I know this isn't the problem because even without the back cover you can still get signal. So I took phone to T-Mobile put new sim tested and nothing so now I know its the phone not T-Mobile. Anyway my question is how can I prepare to send back to T-Mobile I have relocked phone put stock recovery and put leaked ics Rom. So is that bad that it sais relocked and bad if I'm using leaked ics rom I know its voids warrenty when it sais relocked but my software and phone everything works perfect its just the signal so will they fix it? And when I send in could I send phone with a eBay bought battery not HTC one so they could send me a new battery or should I send only HTC battery, phone, and back cover. And also is there any fix for this so I don't have to send in? Please help thanks
You can install official ruu and that will update and install your hboot to locked, which is what tells them if it's locked or relocked. If you don't know how to do this you need to read. Also I've been hearing that ever since s off became available they are considering as voiding warranty not sure if this has taken effect yet or if it matters but just to be sure if your s off read the section that tells you how to s on.
Now before you send have you tried toggling airplane mode on and off ? Still no signal? Flash the official ruu usually fixes these issues. If still no signal then I suggest you send it in.
Sent from my HTC_Amaze_4G using xda premium
fcpelayo said:
You can install official ruu and that will update and install your hboot to locked, which is what tells them if it's locked or relocked. If you don't know how to do this you need to read. Also I've been hearing that ever since s off became available they are considering as voiding warranty not sure if this has taken effect yet or if it matters but just to be sure if your s off read the section that tells you how to s on.
Now before you send have you tried toggling airplane mode on and off ? Still no signal? Flash the official ruu usually fixes these issues. If still no signal then I suggest you send it in.
Sent from my HTC_Amaze_4G using xda premium
Click to expand...
Click to collapse
It's still gonna say relocked, the only way he can get it back to "locked", is if he s-off's the device, once s-off is successful, it automatically puts it as locked all over again, he can leave it as lock, restore a stock ruu, then using, use the command: fastboot writesecureflag 3, that will s-on the device along with everything else being complete stock.
Hmm ya I know how to ruu wich I did but I ruu the ics leak and now everything's stock accept that it sais relocked and want to know if that's gonna be a problem for warrenty when I send it in? It shouldnt since its not software problem? And ya hear how to s off just don't want to try wire trick and all that. And yep tryed turning off and on airplane mode turning off radio taking T-Mobile to change sim cards have original stock Rom tryed *#*#4636#*#* all those tricks but nothing.
Sent from my HTC_Amaze_4G using xda app-developers app
Dark Nightmare said:
It's still gonna say relocked, the only way he can get it back to "locked", is if he s-off's the device, once s-off is successful, it automatically puts it as locked all over again, he can leave it as lock, restore a stock ruu, then using, use the command: fastboot writesecureflag 3, that will s-on the device along with everything else being complete stock.
Click to expand...
Click to collapse
Yeah I wasn't sure if he was s off or not but thanks for correcting me.
cast2brian said:
Hmm ya I know how to ruu wich I did but I ruu the ics leak and now everything's stock accept that it sais relocked and want to know if that's gonna be a problem for warrenty when I send it in? It shouldnt since its not software problem? And ya hear how to s off just don't want to try wire trick and all that. And yep tryed turning off and on airplane mode turning off radio taking T-Mobile to change sim cards have original stock Rom tryed *#*#4636#*#* all those tricks but nothing.
Sent from my HTC_Amaze_4G using xda app-developers app
Click to expand...
Click to collapse
When you chose to unlock boatloader you voided your warranty. So by saying relocked it tells them you unlocked it. You need to do what dark nightmare says or you run the risk of not warranting your phone. Luckily for me I "lost" my phone so I couldn't send it in.
Sent from my HTC_Amaze_4G using xda premium
fcpelayo said:
Yeah I wasn't sure if he was s off or not but thanks for correcting me.
When you chose to unlock boatloader you voided your warranty. So by saying relocked it tells them you unlocked it. You need to do what dark nightmare says or you run the risk of not warranting your phone. Luckily for me I "lost" my phone so I couldn't send it in.
Sent from my HTC_Amaze_4G using xda premium
Click to expand...
Click to collapse
Just trying to help you get that under your hat, no offense meant.
Aw man well hope HTC is cool about it since its not a software problem but just gotta hope for the best!! Ha argh sucks I bought this on craigslist a couple months back for $300 ha I have pre paid
Sent from my HTC_Amaze_4G using xda app-developers app
Aw man well hope HTC is cool about it since its not a software problem but just gotta hope for the best!! Ha argh sucks I bought this on craigslist a couple months back for $300 ha I have pre paid <br />
<br />
Sent from my HTC_Amaze_4G using xda app-developers app
Click to expand...
Click to collapse
I've never heard of a warranty exchange get denied for this phone... even rooted. Most issues with this device are hw issues... u will be fine
Sent from my HTC One S using Tapatalk 2
aw glacierguy thanks for the positive attitude! hope everything goes good for my phone!
So update for everyone i called HTC back and told them to cancel my back cover replacement for the Amaze because i know this is not the reason why i have no bars! because without that cover i still had bars and i know the amaze has some more antennas inside the device. Anyway i told them that i want to send the phone in for repairs so now everything set up and just have to send the phone on its way :crying: hope its a hardware issue and they can fix it. In the mean time got kinda intresting email from HTC saying
"After we receive the device, we will diagnose it and if there are any damages that fall outside of the limited warranty, we will contact you with a quotation to repair. If you choose not to repair, a service fee of up to $35 dollars will be charged and the device will be returned unrepaired."
Yes kinda scared me but hope i don't have to pay anything for this repair so everyone wish me luck and ill let you guys know how everything goes.
Sucks im probably not gonna have my phone for about a month
Just asking, but even if you managed to get the phone completely back to stock and say "Locked" isn't HTC able to tell if you've unlocked the bootloader via their unlock process on the website?
I was under the impression that the entire reason for the HTC unlock process (getting the key from the phone, etc) was so that they would have a database of phones that have had their bootloader unlocked? I'm kind of new to this but that was my impression.
ericdjobs said:
Just asking, but even if you managed to get the phone completely back to stock and say "Locked" isn't HTC able to tell if you've unlocked the bootloader via their unlock process on the website?
I was under the impression that the entire reason for the HTC unlock process (getting the key from the phone, etc) was so that they would have a database of phones that have had their bootloader unlocked? I'm kind of new to this but that was my impression.
Click to expand...
Click to collapse
I think they do have a database, yes, but that only tells them that you requested the file, they can't know you YOU used the file, can they? Huh? Nope, if they knew you used the file, that sir would be invasion of privacy, then they'd be paying for more than just a simple device replacement with the lawsuits that would be hitting them from every mobile device owner using their product.
So once it says "Locked", they can't say you voided your warranty, then they'd have to prove it.
Yes what darknightmare said you could get token but maybe last second decided not to do it haha anywho sending it saying relocked hope they fix hardware issue if not maybe gotta spend money?
Dark Nightmare said:
I think they do have a database, yes, but that only tells them that you requested the file, they can't know you YOU used the file, can they? Huh? Nope, if they knew you used the file, that sir would be invasion of privacy, then they'd be paying for more than just a simple device replacement with the lawsuits that would be hitting them from every mobile device owner using their product.
So once it says "Locked", they can't say you voided your warranty, then they'd have to prove it.
Click to expand...
Click to collapse
They don't need a database. There is no way I know of to get a "locked" phone once it has been unlocked. It will say "relocked". So HTC knows it has had an unlocked bootloader. That doesn't necessarily negate the warranty so far as HTC is concerned. I've read that they have fixed what are obviously hardware problems. But they won't fix anything that a ROM screwed up unless you pay.
The wildcard is T-Mobile. They may or may not be picky about these sort of things.
Ya for sure lets see what htc sais shipped out today through ups htc should get it thursday hope ups loses or breaks my packagae have 300 dollar insurance ha but yep anyone know of any prices for this fix?
stevedebi said:
They don't need a database. There is no way I know of to get a "locked" phone once it has been unlocked. It will say "relocked". So HTC knows it has had an unlocked bootloader. That doesn't necessarily negate the warranty so far as HTC is concerned. I've read that they have fixed what are obviously hardware problems. But they won't fix anything that a ROM screwed up unless you pay.
The wildcard is T-Mobile. They may or may not be picky about these sort of things.
Click to expand...
Click to collapse
Sir, when I say there is a way to get a "locked" bootloader, please don't argue with me unless you can prove my theories wrong, , I have tested and proven everything I speak of, I don't just say something because I want to.
Edit: For the record, once it says "relocked" you have voided your warranty, if you read the agreement on HTC website when unlocking your bootloader and the message on the device when unlocking, it clearly states by unlocking your bootloader you are voiding your warranty.
Dark Nightmare said:
Sir, when I say there is a way to get a "locked" bootloader, please don't argue with me unless you can prove my theories wrong, , I have tested and proven everything I speak of, I don't just say something because I want to.
Edit: For the record, once it says "relocked" you have voided your warranty, if you read the agreement on HTC website when unlocking your bootloader and the message on the device when unlocking, it clearly states by unlocking your bootloader you are voiding your warranty.
Click to expand...
Click to collapse
100% on what Dark Nightmare said, i followed the procedure on the forums on how to completely restore to stock. i was s-off etc.. after it was all said and done, my phone was locked and ready to rock. I sent it back after my replacement arrived and all was good.
Just read through General, Q&A and Dev section, Trust me the answer is there. It's ALWAYS there. I used the GB juopunutbear S-off tool instead of the ICS tool cause i am retarded and didn't take my time and got stuck because of it. I did 2-3 minutes of using the search button and i was fixed in a second!
First of all! Yes Dark Nightmare is correct he knows his stuff you can put it back to locked anywho i would first like to say thank you for all the replys to this post. First post and didnt think my question would be answered but it was and its a great community we got here, i may be new member, but ive always been on xda reading up and hacking all my phones i have went from metro pcs huawei ascend, tmobile my touch 4g and now htc amaze all rooted and custom roms also have done droid and sidekick 4g. The thing is i do have experience and learned alot. Main thing is its an honor to have Dark nightmare and glacierguy here i feel like you guys are famous! ha have seen you guys in different sections and you guys know your stuff so thanks!
p.s everyone that posted i hit thanks
Sent from a Galaxy Nexus?
That's why when dknmare comes in I don't argue with him instead I take it and learn.
Sent from my HTC_Amaze_4G using xda premium
Dark Nightmare said:
Sir, when I say there is a way to get a "locked" bootloader, please don't argue with me unless you can prove my theories wrong, , I have tested and proven everything I speak of, I don't just say something because I want to.
Edit: For the record, once it says "relocked" you have voided your warranty, if you read the agreement on HTC website when unlocking your bootloader and the message on the device when unlocking, it clearly states by unlocking your bootloader you are voiding your warranty.
Click to expand...
Click to collapse
I think my post may not have been clear. Of course you can lock the bootloader; that is how one installs the original ROM. But I was under the impression that it then says ”relocked” if you have previously unlocked the device. That warning from HTC have me a lot of pause when I read it! But I think what I read said ”may” void your warranty. But I was reading fast...
Sent from my HTC View somewhere in LALA land
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:
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
I was given a htc DNA and it's been one headache after another. It had a cracked digitizer, s-off, eng hboot, unlocked boot loader and a custom recovery installed on it when it was given to me. Trying to make a long story short, I ended up having to replace the board with the sim card reader on it and immediately after putting the new board in the cameras quit working along with the speakers and microphone. I was able to get all but the cameras working, but then I bricked it, and here is how. I was attempting to return back to stock, relocked the boot loader, was attempting to use a ruu which wasn't working, so I decided to unlock my boot loader again. The story ends with me attempting the unlock with ez-unlock, and when I did it said successful and I was able to keep using the phone as normal, but after turning the phone off it wouldnt turn back on, and the only sign of life comes when I plug it into my computer. As soon as i connect it to my computer, htc sync manager opens up but says no phone connected, device manager will show the phone as my htc and android 1.0.. I've experienced similar signs of life from an htc vivid, but it's issues were due to a bad battery, so I am hoping for the best but expecting this to end with jtag. Can anybody help me out please, it would be great to not require jtag services, but it would be better yet if I could gain a better understanding of at least what went wrong. Thank you
TELE-FLASH said:
I was given a htc DNA and it's been one headache after another. It had a cracked digitizer, s-off, eng hboot, unlocked boot loader and a custom recovery installed on it when it was given to me. Trying to make a long story short, I ended up having to replace the board with the sim card reader on it and immediately after putting the new board in the cameras quit working along with the speakers and microphone. I was able to get all but the cameras working, but then I bricked it, and here is how. I was attempting to return back to stock, relocked the boot loader, was attempting to use a ruu which wasn't working, so I decided to unlock my boot loader again. The story ends with me attempting the unlock with ez-unlock, and when I did it said successful and I was able to keep using the phone as normal, but after turning the phone off it wouldnt turn back on, and the only sign of life comes when I plug it into my computer. As soon as i connect it to my computer, htc sync manager opens up but says no phone connected, device manager will show the phone as my htc and android 1.0.. I've experienced similar signs of life from an htc vivid, but it's issues were due to a bad battery, so I am hoping for the best but expecting this to end with jtag. Can anybody help me out please, it would be great to not require jtag services, but it would be better yet if I could gain a better understanding of at least what went wrong. Thank you
Click to expand...
Click to collapse
You can't boot into anything? Not even bootloader mode?
.torrented said:
You can't boot into anything? Not even bootloader mode?
Click to expand...
Click to collapse
Sadly no, I can't get it to boot at all. I also need to mention that the lights don't come on when it's plugged in either. I'm thrown for a loop by it all because my computers will still react to it if I hook it up to them with usb, but that's about all they will do. Why would sync manager open up when I plug it in, but then state that there is no device connected.
Ive seen where people have said to leave phone charging for 24 hours without trying to turn it on and it worked. I've also seen people run a calibration test on the battery but I forgot how to do it.
Sent from my HTC6435LVW using XDA Premium 4 mobile app
EZ-Unlock is an unsupported method by the DNA hardware. It will always cause a hard-brick. Which you have done. I did this to myself at one point, too. I tried EZ-Unlock and it hard-bricked my DNA. Call Verizon. Tell them that it just randomly started doing this. Don't mention root or anything. They'll replace it for free. That's what I did.
Sorry about that bud. Try to do some more research before modding your phone next time.
TELE-FLASH said:
Sadly no, I can't get it to boot at all. I also need to mention that the lights don't come on when it's plugged in either. I'm thrown for a loop by it all because my computers will still react to it if I hook it up to them with usb, but that's about all they will do. Why would sync manager open up when I plug it in, but then state that there is no device connected.
Click to expand...
Click to collapse
Oh I see.
ryanguy426 said:
EZ-Unlock is an unsupported method by the DNA hardware. It will always cause a hard-brick. Which you have done. I did this to myself at one point, too. I tried EZ-Unlock and it hard-bricked my DNA. Call Verizon. Tell them that it just randomly started doing this. Don't mention root or anything. They'll replace it for free. That's what I did.
Sorry about that bud. Try to do some more research before modding your phone next time.
Click to expand...
Click to collapse
Or, he could so kindly ask Zarboz to jtag it for him and fix it possibly. I'm not saying he will jtag it but he does jtag work, so if you want to know more you should pm him about it.
Yeah I forgot Z could JTAG it... Thanks for posting that. I am sure that he will be more than happy to JTAG it for him.
Sent from my HTC Droid DNA using XDA Premium 4 mobile app
Can you get into the bootloader by holding power+volume down for any amount of time?
Have you let it sit on the charger over night?
Hold power down for at least 20 seconds to a minute?
Sent from my HTC Droid DNA using XDA Premium 4 mobile app
.torrented said:
Oh I see.
Or, he could so kindly ask Zarboz to jtag it for him and fix it possibly. I'm not saying he will jtag it but he does jtag work, so if you want to know more you should pm him about it.
Click to expand...
Click to collapse
Well thank you for your feedback, and assistance. I owe most everything I know about phones to XDA and it's members! Regarding my situation with the DNA, yup sure enough it is bricked. I figured it was, but have had similar reactions from a bad battery in the past, so.. Regarding the process of unlocking the boot loader, this is the first time I've ever directly seen anything regarding the cid. Not sure if maybe it has been part of the process in ways that I was unaware of in the past with other phones or if this is more device specific, but either way would anybody possibly know where I could find more in depth information regarding this and if there is anybody who is knowledgeable with this that wouldn't mind helping somebody out?
sorry for the run on sentences lol
oh, and thank you for the referral to Zarboz, I will definitely be getting in touch with him.