Related
tried to upgrade my XDA to 2003 microsoft, i reset the phone, and now its just dead,i can't even boot to bootloader, PLEASE HELP!!!!!!!!!!!!
Have you used the reset hole under the headphone socket. Push once then push once more after 60 seconds.?
yes tried that,follow your instructions and all that happened was the internal lights came on,and thats it,even tried the bootloader again and still nothing,i can't even use active sync to flast the rom again.please help its doing my head in now.
dead xda
Do you mean an XDA 2? Because I've just done the same thing. And am (or have been)tearing my hair out too.
Then having got it into boot loader mode (which is tricky) and then cradled it I tried getting active sync 4 to find it but it couldn't. In despair I did bootload mode again and cradled it (grey screen says 'USB' now) and ran (and I can't encourage you to do this of course since it is illegal probably) a beta of mobile 2005. Now this found the mobile! And it's ...at 98% installed.
Watch this space...
dead xda
and no (karma comes home) it doesn't work: get a message 'device authentification failure consult the product maufacurer..."
Damn
its an XAD 1 AND CAN'T EVEN GET THE BOOTLOADER UP ANYMORE!!!!!!!!!!!!!!!!!!!HELP
PLAN B
O.K
(it's worth saying this all started because my pc crashed during an upgrade to the legitimate 2003 final rom for XDA 11. )
I couldn't get this installation to restart (I think because I expected active sync to say, 'yes, found the device' before re-installing - and it doesn't seem to need to do this. Or maybe not. Perhaps I'd just stuffed up getting it n boot loader mode? Who knows. Anyhow. Having another go at putting the legit rom upgrade on now. Fingers crossed & much praying.
dead?
I suspect that for you (and possibly for me also - the jury is still out on my machine) we may need to say hello to our local phone shop in the morning. But that's not the end of the world - tho' it'll probably cost a few £.
undead
Note to self: have a look at other massively helpful forums on this site before doing dumb stuff! There are smart and well-informed people who have all the answers. (notably RAGO in the "stuck in o2 Splash screen forum")
Yippee
(I send apologies for posting all this in what I now realise is totally the wrong forum. (Newbie!)
Adios!
I had just the same problems,
I removed the battery & Sim
I held in the power button and reset button at the same time
but kept them both pressed for 1 min!
I Put the battery & sim back and it all seemed to reset.
Fluke?
not to sure yet but i had no problems
after.
Mac.
So I was playing with the loons kitchen and got called away for a bit...I left my phone plugged in and the kitchen on the desktop (groan now)...my kids wanting to get on the pc did something...not sure what, but my husband says he walked by and said that the ruu was up...I thought ah crap...so I grabbed my phone and saw it was stuck on the splash screen. I rebooted, nothing, splash screen only. I tried getting into bootloader, finally got the message to "restore factory defaults press send" which I did...still, it won't go past the splash screen. I tried the directions found in the "force a bootload" thread...nada. It WILL NOT read as plugged in, and I cannot get it to flash to ANY rom, not button's not the official Tmo, none...PLEASE PLEASE help!!!!!
Thanks in advance.
akashastrega said:
So I was playing with the loons kitchen and got called away for a bit...I left my phone plugged in and the kitchen on the desktop (groan now)...my kids wanting to get on the pc did something...not sure what, but my husband says he walked by and said that the ruu was up...I thought ah crap...so I grabbed my phone and saw it was stuck on the splash screen. I rebooted, nothing, splash screen only. I tried getting into bootloader, finally got the message to "restore factory defaults press send" which I did...still, it won't go past the splash screen. I tried the directions found in the "force a bootload" thread...nada. It WILL NOT read as plugged in, and I cannot get it to flash to ANY rom, not button's not the official Tmo, none...PLEASE PLEASE help!!!!!
Thanks in advance.
Click to expand...
Click to collapse
Just compose yourself for a sec while we ascertain whether it is an actual brick or not. We need to determine two things:
Can you safely assume that your battery has sufficient charge to try a few things? We dont want a completely flat battery to make matters worse.
Only if you have plenty of battery left. Tell us what happens when you enter bootloader mode by holding down camera button and pressing the soft reset hole with the stylus. If your able to get into the tricolour screen then you should be fine.
peter petrelli said:
Just compose yourself for a sec while we ascertain whether it is an actual brick or not. We need to determine two things:
Can you safely assume that your battery has sufficient charge to try a few things? We dont want a completely flat battery to make matters worse.
Only if you have plenty of battery left. Tell us what happens when you enter bootloader mode by holding down camera button and pressing the soft reset hole with the stylus. If your able to get into the tricolour screen then you should be fine.
Click to expand...
Click to collapse
I had at least 80 percent battery. I cannot get into the tri-color screen. Tried holding camera and soft reset, tried comm, camera, power, tried talking sweet to it...it just goes to splash screen each time. HELP!!!
This is a G3 wiza200 IPL/SPL 2.26 and it IS unlocked.
Thanks in advance
If your trying to get into bootloader mode, the device shouldnt boot like normal up to splashscreen. If your getting this far then theoretically the bootloader shuold be fine. I'm going to explain the process in simple terms. I'm not treating you like a child I just want to clarify then we can move on to trying other methods.
1.hold down camera button
2.press little hole on side with stylus
3.release camera button.
Your device should reboot to bootloader mode. Then next thing you see should be the three coloured screen.
peter petrelli said:
If your trying to get into bootloader mode, the device shouldnt boot like normal up to splashscreen. If your getting this far then theoretically the bootloader shuold be fine. I'm going to explain the process in simple terms. I'm not treating you like a child I just want to clarify then we can move on to trying other methods.
1.hold down camera button
2.press little hole on side with stylus
3.release camera button.
Your device should reboot to bootloader mode. Then next thing you see should be the three coloured screen.
Click to expand...
Click to collapse
Yeah, I know...in theory it SHOULD, it's not, hence the freaking out. I am attempting to charge it on the main plug, but it begins to charge then dies. I did have a loose usb port, which I thought got fixed, as my phone charged fine last night, and sync'd fine today. I'm not a pro, but not a noob either...so I am getting frustrated because trying the things I do know, aren't producing the results they should.
**The splash screen is one I made, independent of an OS...after any rom change, I flash my custom splash screen...it has always worked...however, it is making me think that it is the ONLY thing on the MDA, and any signs of a rom were somehow killed by my kids flashing the phone with a very incomplete kitchen rom.**
I will try again. Any help that can be offered would be MUCH appreciated.
PS---I LOVE Heroes!!
When plugged into either usb or main plug, does either light (green/orange) stay on? If not then this symptom combined with a general loose fitting of the usb/main plug would indicate a malfunctioning loose usb socket. The thing is though, even with a loose socket you should still be able to enter bootloader mode. This puzzles me.
Other rescue options include sd-card method, but if you dont have one already, a non-functioning usb will prevent you from composing one because you need communication between the pc and your device.
peter petrelli said:
When plugged into either usb or main plug, does either light (green/orange) stay on? If not then this symptom combined with a general loose fitting of the usb/main plug would indicate a malfunctioning loose usb socket. The thing is though, even with a loose socket you should still be able to enter bootloader mode. This puzzles me.
Other rescue options include sd-card method, but if you dont have one already, a non-functioning usb will prevent you from composing one because you need communication between the pc and your device.
Click to expand...
Click to collapse
I can get brief and random orange lights (my phone was not 100% but at least 80% when I first began)...it takes a lot of sweet talking though to get it to connect to charge. I tried a backup battery as well. Pushing the camera and soft reset either produces my custom splash, or nothing at all (no boot whatsoever). I am truly stumped.
EDIT
I am not aware of the SD card method. I do have an SD, but if I need a special program, I do not have it.
The fact that no light remains on when you connect usb or mains plug makes me think that the usb socket is loose again. In which case I'm doubtful that you can flash via bootloader mode.
The fact that you cant get into bootoader mode suggests that it was somehow corrupted when the flashing process was interrupted. This could be unrecoverable.
From here I'd suggest you investigate the sd card method. I've never relied on this method so this is uncharted territory for both of us.
Read this thread here and here. I think we're running out of options...
Semi success, I got into the quad colored boot (white bottom)...but cannot get it to recognize the usb. I am getting an error message about an unrecognized device, so I will try to fix active sync first...any suggestions for me now that I am at least in a bootloader screen
thats awesome.that means you do in fact have a bootloader still.
You need it to display USB in the little corner. When your in bootloader mode try removing and inserting the USB cable, we need it to show USB in the corner. Without this, you cannot flash.
peter petrelli said:
thats awesome.that means you do in fact have a bootloader still.
You need it to display USB in the little corner. When your in bootloader mode try removing and inserting the USB cable, we need it to show USB in the corner. Without this, you cannot flash.
Click to expand...
Click to collapse
it shows usb in the corner, however it is not producing any charging light, nor does my pc recognize the usb. So...I don't know if this will matter, but as I said...I have the RGB + white bootscreen with usb in the corner...is there still a chance????
yes there is a slim chance.
this will improve your chances by a small margin. Remove the memory card, kill wcescomm.exe in task manager on your pc, turn off any firewall/AV.
Now this is the hard part. I dont own a G3 device so I'm not sure what rom to flash that would save your device. I'd suggest you get the latest rom from the company that shipped your device eg Dopod, Tmobile, Imate etc. If you have a rom that you use in times like this to rescue your device then flash it now.
Good Luck
peter petrelli said:
yes there is a slim chance.
this will improve your chances by a small margin. Remove the memory card, kill wcescomm.exe in task manager on your pc, turn off any firewall/AV.
Now this is the hard part. I dont own a G3 device so I'm not sure what rom to flash that would save your device. I'd suggest you get the latest rom from the company that shipped your device eg Dopod, Tmobile, Imate etc. If you have a rom that you use in times like this to rescue your device then flash it now.
Good Luck
Click to expand...
Click to collapse
wcescomm.exe is NOT showing in Task Mgr...I will try to flash anyway. I killed the firewall and the sd had been removed already. Any other suggestions??
EDIT
ruu error 260 update error
It cannot connect, please check to make sure it is cradled blah blah blah
Thats ok. I forgot that the previous flashing attempts would have killed it off anyway.
So I get ruu error 260
I have rebooted my pc, deleted any connections in active sync (leaving only guest)...
UgggH
It is NOT recognizing the usb
the usb port is as tight today as it was last night after my hubby repaired it...I'm backed to stumped
EDIT**
I had to reboot MDA, now I have lost the little corner usb...but I still have the quad bootscreen
This is progress at least, 1 hour ago we didnt even have bootloader mode. Perhaps you could try flashing another rom, but I think if error 260 keeps appearing then something is wrong with the USB socket.
somehow i lost bootloader again...
this is driving me insane!!!
am trying again, will update momentarily.
************EDIT*****************
Finally got it back into bootloader, but it will not read the usb. keep getting that stupid error message that it doesn't recognize the device, and if I try to flash it with a stock rom, I get error 260.
I have closed the wcescomm.exe
I have killed my firewall
I have rebooted my phone, my pc...everything a few times
I have deleted any connections in active sync
I have unticked allow usb in active sync
WHAT AM I MISSING???
The usb port on the phone does not feel loose again...could it have got fried somehow? I feel as if I can get the damned usb to be recognized, I can save my precious MDA.
Please...any other suggestions, brainstorms, whatever???
THANK YOU
I had a little problem with theloons kitchen doing the same thing to me last week where it would give me the 260 error. I'll upload a ROM flashing file for you to try. Probably the best thing to do right now would be to take the nk.nbf file from an official ROM and stick it in this file and then run the RUU in it. After that you should be ok again to try your luck at cooking with theloons kitchen again although you may want to wait 'til the kids are at school or something before you try it.
When in bootloader mode there's no charging circuit so you won't get any lights on top. The only way to see if USB is working is by watching that same word (USB) at the bottom of the screen.
Check the SD card method which was what saved me once from the 'freezing in splash-screen' problem: http://forum.xda-developers.com/showthread.php?t=276963
good luck
mestrini said:
When in bootloader mode there's no charging circuit so you won't get any lights on top. The only way to see if USB is working is by watching that same word (USB) at the bottom of the screen.
Check the SD card method which was what saved me once from the 'freezing in splash-screen' problem: http://forum.xda-developers.com/showthread.php?t=276963
good luck
Click to expand...
Click to collapse
absolutely right while in bootloader mode it wont charge,but to charge or verify status of usb connectivity,while in bootloader mode push power off button,it'll go in sleep mode but lights will show charging if usb cable is charging
usb cable might be charging but mini usb port of the phone has many connectors I think 9 connectors,I'm not sure,may be the connector for making connectivity relation with phone and pc is damaged.
try with another usb cable if possible,if the connectivity with usb is established than method in the link provided by 'mestrini' is a good option,good luck
It had been going so well, until 9 months later...today. This morning I noticed my battery low (12%), and I thought I'd charge it when I got to work. However it never made it to work - when I went to charge it the back light was on and it was frozen. Thought nothing of it, plugged in the charger, hit the reset button and... nothing. So battery out, back in - press the power light and all I get is the solid green light, no screen, no activity, nothing.
The charging light isn't on either when it is charging, yet the battery shows good charge (tried it on a friends). I'm guessing it's dead, any other takers? I'll ring Vodafone tomorrow, but I'm running with a Duty rom. Hopefully as it looks terminal it should be ok, fingers crossed??
Same thing happened to me just now. WTF? I didn't even do anything. Just totally dead with green light only on. I've tried everything. Pull battery, connect USB, charger, took out SIM, took out memory card, even tried with another new battery, nothing at all. and I just got this phone as replacement last week.
You are stuck in OEMSBL. I can help, but it will be later or tomorrow.
Tell me your ROM, SPL Version, Radio Version, & device model number as well as typey, i.e. Tilt, TYTNII, etc...
HMMMM seems we have a new problem here
Hi Guys
Guess this is now new problem with tytn ii had my phone repaired a couple of weeks ago. technician said something about 3 bad block in the CE was responsible for the TRI color boot screen i used to get.
He said that he formated the phone and reloaded all "firmware".
Prior to sending it in i had Confused Stu Vista Mobile 1.3 running on the phone. Also had OLIPRO 1.0 as the sspl
Tried Frankenkaiser but the phone will not complete step 7 keeps showing that it is an unknown USB device, once i replug the USB cable.
Loaded all the Qualicom Drivers for the Phone as well.
GSLEO3 you and JockeyW are "GOD'S" when it comes to these issues.
Please grace me with your knowledge.
Running Confused Stu Vista Mobile 1.3
Radio 1.65.14.06
wolffie02 said:
Tried Frankenkaiser but the phone will not complete step 7 keeps showing that it is an unknown USB device, once i replug the USB cable.
Loaded all the Qualicom Drivers for the Phone as well.
Click to expand...
Click to collapse
why did you even try frankenkaiser? you only need to use it if you have no SPL (and only if you have the radio from hell).
anyway, to everyone in this thread... if the device still causes the PC to load the qualcomm drivers, when plugged in, then you can recover it, though usually need to use another program as frankenkaiser is currently only compiled for specific radio versions.
Sorta Dead with solid green light
I am in the same boat ... I mistakenly flashed a non-Kaiser radio ( 1.65.28.25 ) and then thought I was reading a Kaiser page about ho to fix it and I ran a `2a`. Ooops on me.
I cannot get tricolor bootloader ... tried hard-reset ( two soft keys and reset ), and Camera-reset, but nothing is working.
What does work:
-bong when connected to PC
-mtty connects - but no `CMD>` prompt.
-able to issue `setboot` - and get back "ARM9BootMode:1".
I've read all the posts and it seems like without the bootloader, I am stuck.
This is an ATT Tilt/8925.
Any and ALL suggestions much appreciated.
seems i have such a problem
the kaiser shows only solid green led. nothing else
doesnt enter tricolor
when i plug it to usb, device manager shows first Qualcomm device and then finds several new devices such as Data Interface
device is AT&T Tilt 8925, original rom version, radio and spl are unknown
who can help me?
cmonex said:
anyway, to everyone in this thread... if the device still causes the PC to load the qualcomm drivers, when plugged in, then you can recover it, though usually need to use another program
Click to expand...
Click to collapse
what program?
i currently have a htc touch pro -mighty rom(sprint) and a while ago i once screwed the Touch Screen Digitizer so i bought another one. i just bought a used hero and the screen looks like it is in excellent condition, although i cannot swipe anything on the screen (had a user name and password lock when i got it and so i wiped it) after wiping at the very end i watched as it flashed a message really fast something about screen locked. when i see windows or whatever it is i push menu twice and it appears to unlock the phone as power save mode is all that i can see otherwise so now since i can see the icons but cannot touch anything only the buttons work, my question , is the screen broken? i click the talk button and i get a "sorry , the process android.process.acore has stopped unexpectedly.please try again." i was going to try and install Aloysius 1.0 v2 to see if the talk would work then although it seems alot more difficult to install a custom rom then the touch pro. i tried to find a Android Rooting in 1-click (limited time only… until it gets patched) to no avail
thank for any help
Try re-running the official RUU via your PC. See this thread to download it (scroll down to post #2 for the RUU): http://forum.xda-developers.com/showthread.php?t=694572
Don't worry about following all those rooting steps in the first long post #1. Just scroll down to post #2 and download the .5 RUU file, then run it from your PC with the phone plugged into USB.
It will completely wipe the phone and revert it back to factory stock settings. If your touch screen is still broken/messed up after this, then yes there's something wrong with the screen and you should take the phone back or replace it or whatever.
take it into sprint. hell you may even luck out and get an evo or epic out of it. i hear they are trying to push those phones on customers.
sorry i did not mention that i bought it at a swap meet for $30 and the phone seemed locked and said too many password attempts and the touch never worked , so i wiped it. i noticed on the side of the screen by the voulme controls , looks like some tweeker tried to maybe bull the battery out and did not know how to open the back.lol and tried to pry in that area a kinda bent the shiny piece slightly below the - vol button and cracked that chrome plated piece that seems to be inbetween the screen and the back case. i will still try the RUU and check it out, i never did try to replace the digitizer on the touch since the walkthrough seemed too detailed. i wounder about the hero.
trying to reset using RUU although says, error 170 usb i tried to install HTC sync can cant connect with it either. i dont understand how to properly install the drivers i suppose.
any advise
Does it just have the white HTC screen. And you can use all hard buttons but nothing else???
If so its because your phone was rooted and then someone did a factory reset. It happened to mine. Its a way of them locking you out of your phone after rooting.. I ran the ruu back to 2.1 and then rerooted it.
Try this RUU..
http://www.4shared.com/file/2uQunBaV/RUU_Hero_C_Sprint_2276515_R_si.html
Also you just download the htc sync here..
http://www.htc.com/us/support/hero-sprint/downloads/
Jus10o said:
Does it just have the white HTC screen. And you can use all hard buttons but nothing else???
http://www.htc.com/us/support/hero-sprint/downloads/
Click to expand...
Click to collapse
no the OS seems to be functioning fine , except for everytime i push send it get the "sorry! the process android.process.acore has stopped unexpectedly. please try again"
so i tried to power up holding on to vol + and doing the RUU as well as having the phone as normal as can be and running RUU and i get
error(170) usb connection error
rom update utility cannot connect to your phone.
i installed the file HTC_Sync_2.0.40.exe and ran RUU_Hero_C_Sprint_2.27.651.5_R_signed_release.exe when told powered the phone and clicked next and always get the 170usb error. i still am guessing that the drivers are not installed properly as when i plug in the phone i dont hear the normal usb sound made by the pc. also i never noted that i dont have the offical usb sync cable i have 2 of them , one is shape the same as the area to insert it on the hero, it is the htc touch pro cable . and the other usb cable is the basic one that works for alot of stuff that it fits into, except for motorola`s cell phones to charge them.lol
heeeeeelp
Bringing back more old threads
I am having this exact problem with an HTC Hero. I started before it had ever been rooted. I have rooted, loaded custom roms, wiped everything, ran two diff RUUs, and replaced the digitizer.
If I boot the phone to the HBoot, at the top of the screen it says TOUCH PANEL-fail.
Wondering if it is hardware or software at this point. I had it working earlier today somehow after doing a full wipe, but when i reactivated the phone and started dialing a number to test it it froze up. Rebooted and it was back to the same problem.
Hi everybody,
a friend of mine got his HTC One (black) yesterday and rooted it. He flashed a proper custom ROM on it which I and another one of my work buddy use as well without any issues (InsertCoin). No further flashes done, no other custom kernels, no S-Off, no SuperCID. Just unlocked Bootloader and custom ROM.
He let the device run dry yesterday evening so it shut off itself automatically. He put it on his charger, the phone turned on, he did some surfing and installing apps from the market and set up his alarm. The phone charged over night and he was also able to switch off the alarm this morning.
He got ready for work, got into his car and wanted to switch on the screen on the one for some good tunes. But the screen stayed black.
When I arrived at work, he was a little upset and panicked a little. I thought I was able to recover the device.
After plugging it in to my work computer, the device manager just shows a unknown device called "QHSUSB_DLOAD" so I went to google and looked it up..
Weird thing is: QHSUSB_DLOAD wasnt seen yet on the HTC One (M7) as far as I can see it and it was pretty bad on the HTC One S. It means "Qualcom High Speed USB Download Mode" and on the One S as well as on the Nexus 4 this devices showed up after the bootloader got damaged or the device got stuck in that mode for good.
When plugging the device in (USB / Wall charger) the charging LED doesnt turn on at all, the capacitive buttons dont start to blink while holding down the power button as well.
This thing seems to be gone for good.
But aint it the way that we dont even have any access to the bootloader if its not an official update from HTC? Signature check and stuff? Since the device was rooted, no OTA updates were able to arrive at all. He told me that he didnt try to flash anything after we flashed the custom ROM.
Any advice on that?
Did you even try booting the device first thru hboot/bootloader or holding the power button to force a restart? If you did try connecting the device while on QHSUSB_DLOAD and execute a compatible RUU on your PC. RUU uses android's download mode to flash the ROM so it should be repaired by an RUU.
Already tried, no luck. Tells me the device has not been found.
I am sorry to hear that, man, but from the looks of it your friend now has a paperweight. I'd take it to an HTC service center and hear what they have to say regarding this; of course it will no longer be covered under warranty, but maybe they can fix it for you for a price or something.
Are you sure RUU can't find the phone? If it can't then I guess only a JTAG box can fix it so either send it to HTC for repair or have someone who knows JTAG fix it.
Try4Ce said:
Already tried, no luck. Tells me the device has not been found.
Click to expand...
Click to collapse
I saw this issue on my friend's GS3 once. It was hard bricked and there was no way to recover from what I read (at least on the GS3). I know I saw a thread somewhere here in this forum about the same issue and someone linked to a Sensation thread where there was a way to fix it but I'm not sure if it would apply to the One
Same problem - but the phone magically fixed itself!
I had the exact same problem with my HTC One as described in OP...
My alarm went off in the morning and I set off for work, my battery was low but I thought that I would just charge it when I got to work. I was playing a game (Dungelot) whilst waiting for my bus and was receiving pop up messages about low battery. When it got to 4% left I decided that I would finish the level then close the game down, but as I was just about to finish, the phone went blank...I assumed that I had naturally used up all the battery life and although peeved that I had probably lost my progress in the game, wasn't too bothered.
I got to work and plugged my phone in to charge on my computer. The computer wanted to search for QHSUSB_DLOAD drivers but I thought this must be what it does when my phone isn't switched on and it finds the device. I cancelled the search prompt and tried to switch my phone on...nothing happened.
I tried for the rest of the day, trying to force shut down the bricked phone by holding power in for 30 secs, trying to power into boot mode etc...everything! But the phone would not switch on and the only response I got from it was a little orange LED every now and again and the QHSUSB_DLOAD prompt.
After googling the prompt - I found myself here and REALLY began to sh*t my pants! I've only had the phone less than a month and felt I was tech-savvy enough to flash my phone with a new ROM (Android Revolution HD) to try and get rid of some of the bloatware. I had flashed a new ROM successfully a coupld of weeks before and everything had been fine up that point.
I went home depressed but throught i'd try to plug my phone into a proper mains charger rather than my work's old USB cable (that came with my previous HTC Desire Z) I was going to try a long night of searching the net to try and find a way where I could at least recover the photo's, Zoe's and vids of my new born son but had such a headache that I gave up and went for an early night.
I was woken unexpectedly the next morning by my phone alarm going off! I stopped the alarm and the home just went to Home screen as normal! I don't know how or why these events happened...whether it was the flashed ROM, the game I was playing, the battery running out before the phone could shut down properly, the old USB cable in my work not charging but detecting the device or a combination of all of those, but so far, the phone jumped back into life with the alarm after being charged in the mains all night!
Thought i'd share as it may just help someone else out there who encounters this!
Some phones have miraculously come back from QHSUSB_DLOAD with no explanation of why. Other than that it usually means a hard brick. You can send it to HTC, they will charge you and replace the main board, from what I've heard.
Sent from my HTC One using XDA Premium 4 mobile app
---------- Post added at 08:20 PM ---------- Previous post was at 08:20 PM ----------
Also, its not unheard of. I've seen it happen a few times in these forums.
Sent from my HTC One using XDA Premium 4 mobile app
I wonder if having your alarm set saved you. This phone will actually power itself on so as not to miss an alarm.
Sent from my HTC One using xda app-developers app
lampel said:
I wonder if having your alarm set saved you. This phone will actually power itself on so as not to miss an alarm.
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Hi Try4Ce,
I am facing the same issue. If your friend's phone is fixed, can you share with me how the fix happened?
Many thanks in advance.
Krishna Menon.
same here
Any idea how to fix it?
Delingerb said:
Any idea how to fix it?
Click to expand...
Click to collapse
Jtag or send it to HTC is the only way.
Sent from my HTC One using Tapatalk
My Solution
Had the same Problem.
My Solution was to Download "HTC One (M7) Toolkit" and force Fastboot.
Pushed Power and Volume Down until Screen was Flashing.
Took about 2 minutes and the Phone was rebooting.
I have no idea what was happening. I have no idea if this helps or works for others. But its worth trying.
Sorry for my bad english.
Try4Ce said:
Any advice on that?
Click to expand...
Click to collapse
CoryTallman said:
Some phones have miraculously come back from QHSUSB_DLOAD with no explanation of why. Other than that it usually means a hard brick. You can send it to HTC, they will charge you and replace the main board, from what I've heard.
Click to expand...
Click to collapse
bkmenon said:
Hi Try4Ce,
I am facing the same issue. If your friend's phone is fixed, can you share with me how the fix happened?
Many thanks in advance.
Krishna Menon.
Click to expand...
Click to collapse
Delingerb said:
Any idea how to fix it?
Click to expand...
Click to collapse
This is some kind of mode that is enabled when you hold power on button when the device battery is completely drained. i.e. when you try to turn device on it will not boot up (Special I was connected to usb cable via PC to charge my phone NEXUS 4 when I get into this mode). I saw a similar mode where nvflash commands are executed something like APX(can't recall correctly) with Tegra 4 device (that time also I was connected with a usb cable and charging the tablet when it was completely drained!). A simple solution to quit this issue is DO not Panic and let the device get a little charge. After that boot normally with the power button. In case if it didn't try other modes to enter such as recovery or fastboot reboot commands if your device is getting recognised..
QHSUSB DLOAD means its a hard bricked phone, No amount of messing about with it will fix it, Send it to a service centre, it will probable have to have the motherboard replaced..Sorry
My device entered in QHSUSB_DLOAD mode after the 4.4 ota was installed and 30 minutes later, I was able to turn up the phone. It restarted itself like 5 times and then it was normal. Miracle..
danielr18 said:
My device entered in QHSUSB_DLOAD mode after the 4.4 ota was installed and 30 minutes later, I was able to turn up the phone. It restarted itself like 5 times and then it was normal. Miracle..
Click to expand...
Click to collapse
What do you mean by "force"? What did you do exactly?
My device wouldn't do anything, and it was in QHSUSB_DLOAD . But when I later pushed the power button for a minute, it worked.
danielr18 said:
My device wouldn't do anything, and it was in QHSUSB_DLOAD . But when I later pushed the power button for a minute, it worked.
Click to expand...
Click to collapse
mine spent the night carrying on waking took the charger and the green light for continued access, tried to turn it on but could not. After reading your response, I tried to hold the power button for longer. After 15 seconds the phone rang and the light came on, everything works perfect so far
Today while I was updating firmware phone gone to QHSUSB_DLOAD mode.
I am guessing it's end of road. :crying: