Develop Bugs

[Q] Stuck in a boot loop with HTC diagnostic area (dead volume down rocker)

Hey guys
I'm running MrGarak's fantastic MIUI rom however I've found that the kernel is booting my phone into that white HTC diagnostic screen by default. Unfortunately my volume down button is dead and so I can't navigate the menu; the only way I can boot my phone at the moment is to boot it connected via USB as that makes it boot to Recovery and I can reboot from there.
Any ideas? I think this and another rom I tried both used LordMUE's kernel, could that be the reason the boot preferences don't default to just booting the OS?
Any help and/or pointers would be greatly appreciated

So you can access bootloader and recovery!
So just flash another kernel. What's your problem?
Put a zip on your SD (with a SD reader or ADB pull), then go in recovery, navigate with the 4 keys under the screen (or vol+ and power)... and flash.
What is strange for me is that it seems to happen sudenly... so how do ou know it's the kernel. Anyway...

I have clockwork recovery, and can navigate it using the soft keys (home menu etc). You should also he able to use the vol up key to get to the bottom of the list, (depending on the recovery you're using I suppose)
Sent from my Desire HD using Tapatalk

_david_94 said:
I have clockwork recovery, and can navigate it using the soft keys (home menu etc). You should also he able to use the vol up key to get to the bottom of the list, (depending on the recovery you're using I suppose)
Sent from my Desire HD using Tapatalk
Click to expand...
Click to collapse
Unfortunately it boots into the white HTC area (dunno what it's called). The one where you can see if your phone is S-OFF or not.
Also, I'm not sure what is to blame... but I've only just recently noticed that my phone cold boots this way so I assumed it was a recent rom that I applied. Will test this theory later.

Sounds to me like your volume down button is stuck in.
Definitely not a ROM issue, as it has nothing to do with the bootloader.
Sent from The App that Time Forgot.

Hey, i had this issue like a month ago. You can check my previous threads. It's hardware I'm 100% sure. Basically if you're in warranty you need to flash the stock rom with S-On so you can get a new phone. You can get it to boot but it's really a pain. You have to play with the volume up when first turning on your phone. It took me about an hour. Then when it boots you'll be in a "Safe Mode" (no clue whats limited all seemed fine to me). Then do your backup if you wish.
Also note: Flashing the S-On rom is a PAIN, took me about 2-3 hours of rebooting, holding vol up, tapping vol up, to get it to boot right, but with patients you'll get it to go.
Good luck to ya.

xtremedelta said:
Hey, i had this issue like a month ago. You can check my previous threads. It's hardware I'm 100% sure. Basically if you're in warranty you need to flash the stock rom with S-On so you can get a new phone. You can get it to boot but it's really a pain. You have to play with the volume up when first turning on your phone. It took me about an hour. Then when it boots you'll be in a "Safe Mode" (no clue whats limited all seemed fine to me). Then do your backup if you wish.
Also note: Flashing the S-On rom is a PAIN, took me about 2-3 hours of rebooting, holding vol up, tapping vol up, to get it to boot right, but with patients you'll get it to go.
Good luck to ya.
Click to expand...
Click to collapse
Ah, I'm definitely beyond warranty. The thought of vol+down being stuck down makes a lot of sense!
I'll just take it to one of the dodgy Asian repair shops, if it's a hardware issue I'm sure they'll know what to do.
Cheers for your help everyone!

[Q] Booting phone without the power button

Hey guys, back with a new problem.
So the wife has been having issues with her power button for a while now, and its getting to the point where it is pretty much intolerable. Last time she killed her battery it took almost a half hour of button mashing to get her phone to boot back up, and I'm worried that next time she kills the battery, I wont be able to get it to boot again.
Does anyone know a way to boot the G2/Desire Z without a working power button (other than disassembling the phone and shorting the contacts in the power button)?
Her contract is up next month, but I'm sure she'll drop it, kill the battery, or have to do a battery pull between now and then, so any help is appreciated!

I'm not sure but I think I had my g2 powered down and pluged it into my laptop and it booted.
Sent from my G2 running the random rom of the day.

like the above mentioned, there was a flaw in one of the clockwork recoveries (can't recall the version off hand) that when the phone was powered off and you plugged it in it would automaticaly turn on. for you this wouldn't be a flaw so search the forum for someone complaining about this and just install that recovery. of course you will have to be rooted first if you aren't already
Sent from my HTC Vision using xda premium

I had that booting issue with the Clockwork Mod touch recovery for our phones. Guess it can be helpful in this situation. This is the thread with recovery info and this is how to flash recovery.
Not sure if the files linked to in our recovery thread still work but here is link to CWM-Touch 5.8.1.0

Couldn't she do adb reboot or no?

Chancee said:
Couldn't she do adb reboot or no?
Click to expand...
Click to collapse
not if the phone is powered off already. need to be on to use adb
Sent from my HTC Vision using xda premium

In Mimistry ROM you can wake and unlock your phone by pressing a trackball.

andriens said:
In Mimistry ROM you can wake and unlock your phone by pressing a trackball.
Click to expand...
Click to collapse
Firstly, I think you mean Andromadus Mimicry, not mimistry
Secondly, trackpad wake/unlock is a feature in most custom roms.
Thirdly, wake is completely different to booting, which is what the question was about. A (maybe somewhat vague) analogy would be, you've lost the ignition key for your car, and you're trying to start the engine by shifting to first gear.
demkantor said:
like the above mentioned, there was a flaw in one of the clockwork recoveries (can't recall the version off hand) that when the phone was powered off and you plugged it in it would automaticaly turn on. for you this wouldn't be a flaw so search the forum for someone complaining about this and just install that recovery. of course you will have to be rooted first if you aren't already
Click to expand...
Click to collapse
I think the version you're looking for is Clockworkmod 3.0.0.5, which should be available in the Rom Manager app (under flash older/other recovery). can't find a working link for the img itself.
-Nipqer

[Q] Hard brick

Woke up this morning and my N7 wouldn't turn on. Plugged it in and the charging indicator came up showing at nearly full charge. Holding the power button then turned it on. Went away for an hour or two, came back and it was off. When I turned it back on it was stuck on the X screen. Forcing a reboot with power+vol just led to the tablet turning off. And now I just plugged it into my computer and QHSUSB_DLOAD came up.
Just got the damn thing a couple days ago and it was 100% stock. Any ideas as to what may have caused this?

Just unplugged it and it turned on but is again stuck on the X. Is QHSUSB_DLOAD no longer indicative of a hard brick?

I'm a newbie here, but let's try.
If you can get to the X one, then I think it's not brick yet.
Maybe your should try to press pwer button and volume down to get to fastboot. You press this combination when your Nexus is turned off.

opticaldh said:
I'm a newbie here, but let's try.
If you can get to the X one, then I think it's not brick yet.
Maybe your should try to press pwer button and volume down to get to fastboot. You press this combination when your Nexus is turned off.
Click to expand...
Click to collapse
once I turn it off the whole cycle starts over again. It's sporadically deciding whether or not it wants to boot but I'll keep trying to get into fastboot

herculesgs said:
Woke up this morning and my N7 wouldn't turn on. Plugged it in and the charging indicator came up showing at nearly full charge. Holding the power button then turned it on. Went away for an hour or two, came back and it was off. When I turned it back on it was stuck on the X screen. Forcing a reboot with power+vol just led to the tablet turning off. And now I just plugged it into my computer and QHSUSB_DLOAD came up.
Just got the damn thing a couple days ago and it was 100% stock. Any ideas as to what may have caused this?
Click to expand...
Click to collapse
In doing a little googling it looks to be possibly caused by the update. If you look up the error, you will see a common problem where HTC bricked a bunch of different phones when they pushed an ota a while back. I would say just return it and get a new one . You could do some research and try it yourself. Are you able to get into your bootloader ( vol+ and Vol - when you trun it on)?

uprightbass360 said:
In doing a little googling it looks to be possibly caused by the update. If you look up the error, you will see a common problem where HTC bricked a bunch of different phones when they pushed an ota a while back. I would say just return it and get a new one . You could do some research and try it yourself. Are you able to get into your bootloader ( vol+ and Vol - when you trun it on)?
Click to expand...
Click to collapse
I was able to get into it this morning and I wiped my cache. The next time it decides to turn on/I can get it into the bootloader I'll try a factory reset

herculesgs said:
I was able to get into it this morning and I wiped my cache. The next time it decides to turn on/I can get it into the bootloader I'll try a factory reset
Click to expand...
Click to collapse
Well something got corrupted, but if its booting its not hard bricked (that's good news). Luckily for you as well the aosp images are up so if you want to do a restore you can snag your images, and just do a fastboot install. I hope this isn't indicative of another problem with the device itself, I still maintain that you should probably exchange your device for a new one if you did indeed do nothing to the device. It would be a shame if the same problem happened again because of a faulty component.

uprightbass360 said:
Well something got corrupted, but if its booting its not hard bricked (that's good news). Luckily for you as well the aosp images are up so if you want to do a restore you can snag your images, and just do a fastboot install. I hope this isn't indicative of another problem with the device itself, I still maintain that you should probably exchange your device for a new one if you did indeed do nothing to the device. It would be a shame if the same problem happened again because of a faulty component.
Click to expand...
Click to collapse
Yeah, I most likely will. It'll boot to the X probably once every 25 tries so there's something weird going on and it's probably safer just to return it then find a fix and have it happen again.

herculesgs said:
Yeah, I most likely will. It'll boot to the X probably once every 25 tries so there's something weird going on and it's probably safer just to return it then find a fix and have it happen again.
Click to expand...
Click to collapse
Just out of curiosity, where did you purchase it from? Does the seller recognize a lemon as returnable, would you possibly have to tell them you just didn't like it?

uprightbass360 said:
Just out of curiosity, where did you purchase it from? Does the seller recognize a lemon as returnable, would you possibly have to tell them you just didn't like it?
Click to expand...
Click to collapse
Wally world. afaik they're pretty lax on returns

update
Got into the bootloader and did a factory reset. Everything seems to be working again now

herculesgs said:
Got into the bootloader and did a factory reset. Everything seems to be working again now
Click to expand...
Click to collapse
Awesome! Love a happy ending.

Mine was like that all day. I am unlocked and rooted but stock ROM. Damn thing was on an x all day. I was finally able to get to TWRP and flashed my latest backup. No ideas what happened or why.
Sent from my Nexus 7 using xda app-developers app

AnarchoXen said:
Mine was like that all day. I am unlocked and rooted but stock ROM. Damn thing was on an x all day. I was finally able to get to TWRP and flashed my latest backup. No ideas what happened or why.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Mine is just stuck on Google...... I got into fastboot and flashes stock image but it still will not get past google. I can not boot it to recovery or anything other than fastboot.

What happens when you do vol down and power to try and get into the bootloader? Nothing at all?
Sent from my Nexus 7 using xda app-developers app

kd5dmg said:
Mine is just stuck on Google...... I got into fastboot and flashes stock image but it still will not get past google. I can not boot it to recovery or anything other than fastboot.
Click to expand...
Click to collapse
Follow hercules advice. Vol Down + Power to get to bootloader. Then you should be able to get to recovery. Let us know.
Sent from my Nexus 7 using Tapatalk 4

kd5dmg said:
Mine is just stuck on Google...... I got into fastboot and flashes stock image but it still will not get past google. I can not boot it to recovery or anything other than fastboot.
Click to expand...
Click to collapse
Stuck at Google means /system is corrupted or erased (fastboot to restore system.img)
Stuck at X means something wrong with userdata/cache (factory restore from recovery)
Won't start at all with USB identifying as QHSUSB_DLOAD means either bootloader corrupted or raw partitions corrupted
I suggest you reflash again.

[Q] HTC Inspire 4G bricked help!

Hi there, I have a HTC Inspire 4G phone that is not working anddont know what to do, Actually I have knowledge in samsungs only, (download mode recovery etc) but this phone does not turn on at all, after pressing the power button there is a little red led at the left and turns on and thats it, pressing power and vol - doesnt do anything,
When I plugged it in the computer after 5 mins around the computer recognizes an "android phone" or "my htc" nothing else happens.
when I leave the phone alone, suddently it turns on vibrating constantyl and shows a white screen with a HTC green logo but nothing else happens
:silly: this is crazy right? , please help

Dc-18 said:
Hi there, I have a HTC Inspire 4G phone that is not working anddont know what to do, Actually I have knowledge in samsungs only, (download mode recovery etc) but this phone does not turn on at all, after pressing the power button there is a little red led at the left and turns on and thats it, pressing power and vol - doesnt do anything,
When I plugged it in the computer after 5 mins around the computer recognizes an "android phone" or "my htc" nothing else happens.
when I leave the phone alone, suddently it turns on vibrating constantyl and shows a white screen with a HTC green logo but nothing else happens
:silly: this is crazy right? , please help
Click to expand...
Click to collapse
What happened before this?
Did someone try doing something like down grading?
Your symptoms sound like someone tried to flash a froyo ruu on a device that had gingerbread on it which means your bootloader is possibly messed.
Sent from my GT-I9505 using xda app-developerfs app

some time ago was rooted, a friend of mine tried to format it, he selected all the delete options, and then it did not continue to boot

Dc-18 said:
some time ago was rooted, a friend of mine tried to format it, he selected all the delete options, and then it did not continue to boot
Click to expand...
Click to collapse
I haven't the slightest what you're trying to say here.

bananagranola said:
I haven't the slightest what you're trying to say here.
Click to expand...
Click to collapse
the 1 post is the original and current problem..

Is your bootloader unlocked? Is it S-Off? Did you flash a custom ROM? Did you wipe /system? What exactly did you do to get it into that state?

bananagranola said:
Is your bootloader unlocked? Is it S-Off? Did you flash a custom ROM? Did you wipe /system? What exactly did you do to get it into that state?
Click to expand...
Click to collapse
Im not really sure if the bootloader is unlocked since I didnt use this phone before, but pressing power button + vol- doesnt do anything, my friend who is the owner said that the phone was rooted he wiped everything in the system options, after that the phone did not start anymore and got the problems mentioned before

He might of formated something for the phone to boot up properly, tryed flashing ruu or ADB(ANDROID DEVICE BRIDGE)
Sent from my Desire HD using XDA Premium HD app

JustPlayingHard said:
He might of formated something for the phone to boot up properly, tryed flashing ruu or ADB(ANDROID DEVICE BRIDGE)
Sent from my Desire HD using XDA Premium HD app
Click to expand...
Click to collapse
That may work, is there any thread to see how to do this? Thanks for your help guys

Dc-18 said:
pressing power button + vol- doesnt do anything
Click to expand...
Click to collapse
Did you do that when the phone was off?

bananagranola said:
Did you do that when the phone was off?
Click to expand...
Click to collapse
Yep, removed the battery and tried but doesn't do anything

Dc-18 said:
Yep, removed the battery and tried but doesn't do anything
Click to expand...
Click to collapse
Wait, you tried that when the battery wasn't in the phone?

bananagranola said:
Wait, you tried that when the battery wasn't in the phone?
Click to expand...
Click to collapse
Nup, of course when the battery was on the phone, what I meant is I removed the battery and insert it again and tried but didn't work

Dc-18 said:
Nup, of course when the battery was on the phone, what I meant is I removed the battery and insert it again and tried but didn't work
Click to expand...
Click to collapse
It didn't turn on? What did it do?

bananagranola said:
It didn't turn on? What did it do?
Click to expand...
Click to collapse
Nothing at all

Flashing and bootloop

Hello!
I'm planning to upgrade from a LG G4 to this awesome phone (I hope this is a good desicion??!) and this would be my first HTC phone then after some Samsung and LG devices.
So I have a question: When I'm flashing something on my LG G4, something goes wrong and a bootloop appears, then I can simply remove the battery, put it in again, boot to recovery, flash again and all is fine.
But what could I do if something like this appeared on the 10 due to non-removeable battery?
Thanks in advance!

Holding down the power button and the volume down button allows you to reboot the phone. I've had several HTC phones that work this way, and I've never had an issue with being able to reboot the phone this way.
Sent from my HTC 10

Magnum_Enforcer said:
Holding down the power button and the volume down button allows you to reboot the phone. I've had several HTC phones that work this way, and I've never had an issue with being able to reboot the phone this way.
Sent from my HTC 10
Click to expand...
Click to collapse
That means this works even when the phone is bootlooping? Well that's good to know, thank you!

RogerF81 said:
That means this works even when the phone is bootlooping? Well that's good to know, thank you!
Click to expand...
Click to collapse
Yep, even when it's boot looping.
Sent from my HTC 10

Magnum_Enforcer said:
Yep, even when it's boot looping.
Sent from my HTC 10
Click to expand...
Click to collapse
Thanks! Is it still worth getting the 10? I mean considering the development? )Will there be some stable CM/AOSP based Roms?)

RogerF81 said:
Thanks! Is it still worth getting the 10? I mean considering the development? )Will there be some stable CM/AOSP based Roms?)
Click to expand...
Click to collapse
Most definitely[emoji106]
Sent from my HTC 10

Magnum_Enforcer said:
Most definitely[emoji106]
Sent from my HTC 10
Click to expand...
Click to collapse
Sounds promising:good: Looking forward for expanding developing and getting this phone :fingers-crossed:

RogerF81 said:
When I'm flashing something on my LG G4, something goes wrong and a bootloop appears, then I can simply remove the battery, put it in again, boot to recovery, flash again and all is fine.
But what could I do if something like this appeared on the 10 due to non-removeable battery?
Click to expand...
Click to collapse
I've been in this situation already. Holding power+vol-dn for a long time will cause the keys to blink and then it will reboot.
Putting the RUU's zip on the external SD card will give you the option to factory flash it to out-of-the-box state on power-up. This is a wonderful thing.
I was in a bootloop once for a custom ROM gone sour and again when running the RUU.exe BSODded due to memory failure on the PC (talk about bad timing...heh...no pun intended), leaving the phone in a coma.
The US Unlocked/Dev version has the RUUs available on htc's site.

Magnum_Enforcer said:
Holding down the power button and the volume down button allows you to reboot the phone. I've had several HTC phones that work this way, and I've never had an issue with being able to reboot the phone this way.
Sent from my HTC 10
Click to expand...
Click to collapse
Power + vol up with M8 to force a reboot. I've found power + vol up and down works with the 10.