Develop Bugs

[Q] Bricked Desire Z

Hi
I've got Desire Z with latest Visionary rom. Everything worked fine till today. My som played Angry Birds and suddenly phone turned off... I was unable to turn it on - pull & put back battery doesn't work. When I connect charger - nothing, unable to boot, black screen, charging led not working. I connected DZ via usb to my notebook - it found QHSUSB_DLOAD device and nothing more. I read somewhere at xda, that it could be burned motherboard. Any ideas to bring it back to work ?
Greetings - Tom

Hi,
yesterday my phone went to restart. Unfortunately it shows only black screen with phone with red triangle than I pull and put back battery and try to start again. I got only logo htc and nothing more. Than I tried restart phone more times and now it not response to power button. I get only black screen. If I connect tel to pc it found device QHSUSB_DLOAD.
Interesting is that i played Angry Birds few hours before scrash.

Me have same problem with DZ....

SEmp91 said:
Me have same problem with DZ....
Click to expand...
Click to collapse
what playing angry birds and then phone shut off? if you would like more help please give more details
Sent from my HTC Vision using xda premium

I bought this phone yesterday and it was already broken. Phone dont start and if I plugged them to PC it defined as QHSUSB_DLOAD device.
Previous owner said that phone was finally broken (from died memory chip to QHSUSB_DLOAD mode) when it lying on the table with battery.

fried emmc is a prdoblem with certain chips on these phones. do you knoew if it rooted? boot into bootloader (hold volume down while powering on) and write down everything on that screen
Sent from my HTC Vision using xda premium

In QHSUSB_DLOAD mode phone cant boot into bootloader, unfortunately..
I ask previous owner about root, will see what he says
There people solved same problem with sensation but no solution for DZ granted

Phone is s-on without root

unfortunetly if you can access bootloader or recovery there is nothing that can be done other than jtag.
Sent from my HTC Vision using xda premium

bootloader and recovery has no available currently. I know that a long ago..
Do you know how repair via jtag or via qhsusb_dload mode?

SEmp91 said:
bootloader and recovery has no available currently. I know that a long ago..
Do you know how repair via jtag or via qhsusb_dload mode?
Click to expand...
Click to collapse
as far as I know no one has made a way to unbrick with the qhsusb_dload for the vision, I only looked into that project once when I got a doubleshot for my girlfriend, just to see what its all about. I believe there are only a limited number of devices that dexter (I think that's his name) support, the vision not being one of them. also this will only help under certain circumstance. if you have a fried emmc than you can't read or write to it and I don't believe even jtag would help. but not having access to bootloader or recovery just makes it nearlly imposible do anything.
now there are people who have the knowhow and equipment to jtag the vision, and they probably charge in the $50 range. this *may* get you access to your bootloader and then of course a full stock rom/radio/spl/etc would be forced to you phone but again without knowing what caused the brick it is hard to say
Sent from my HTC Vision using xda premium

Thanks.
May i ask dumb question? bootloader is stay in emmc? or another storage?
For example, desire s with died emmc setup to boot from microSD and it works!
I see no problem with replacement emmc but boot from sd is easier if bootloader alive, of course
And jtag-board with soft is so high price..

yeah the bootloader partition is in the emmc, if that is just borked (not a fried emmc) jtag will fix it. you can't boot from sd because you have nothing working, cathedral (I think that's who it was) discovered how to boot off sd in these situations, and yes that works with the g2/dz as well, but even then you need a somewhat working recovery
jtag is probably about the same as a new logic board, maybe a little cheaper. but if you can't find someone to do it for like 20~30 bucks then buy a new motherboard for like 60~80. or learn how to do jtag yourself, the equipment is rather cheap (sometimes can make your own cable) and the software I believe is free. someday I plan to learn myself (got a couple dead g1s lying around) but for now I'm no help in that regard
Sent from my HTC Vision using xda premium

if bootloader hold in emmc.. so i really want to know what is written in cpu-memory)

I believe all partitions are held in the emmc, the cpu is just like the command center and decides what to do and when to do it.
Sent from my HTC Vision using xda premium

above CPU exists another flash-drive but i dont know anything about data located in this storage.

sorry I couldn't tell you, haven't looked it to this much but to my understanding is that all partitions are held in the emmc. I guess its possible that the larger system parition is located in a seperate nand but I don't think so. I'm sure a little googling will turn up a breakdown of all compenents on the logic board if your interested and where memory is alocated
Sent from my HTC Vision using xda premium

Replacing emmc solved problem

Hey glad to hear! Did you replace the whole board or just the chip?
Sent from my SGH-T839 using Tapatalk 2

Juct a chip оfcourse)

Unresponsive phone - Dead?

Bit of a strange one.....
Phone was fine last night, replied to a text, checked my phone 10 minutes later and its not working, doesn't seem to be responding to the power button so was a little confused, no captive feedback, no lights or sounds. Battery was showing 62% prior.
It hasn't worked since.
Tried:
- Holding down the power to restart the phone.
- Holding down power and vol - to get into the bootloader
- Charged it for 10 hours (doesn't even indicate the LED)
- Tried connecting to a PC (and PC doesn't recognise it at all - again no LED)
The phone is an international one x. It is rooted and has been fine since August on root. Wasn't being used excessively or any stress that you would expect to cause a failure. Wasn't dropped or anything.
I'm stumped, had a search on here and can't find anything. So before i put an insurance claim in, does anyone have any suggestions? Battery failure? Motherboard failure?
Cheers

Try connecting your phone to your pc, see what Windows recognises it as
Sent from my faster than SGS3 HOX.

XxVcVxX said:
Try connecting your phone to your pc, see what Windows recognises it as
Sent from my faster than SGS3 HOX.
Click to expand...
Click to collapse
It doesn't recognise it as anything and the led is not appearing on the phone.
Thanks

Phone is stuck in apx mode or something, you'll have to send it back for repair. I just did it 2 days ago, It's really worring because I'm seeing a lot of these cases but nobody has reported back to say what htc has done about it. I hope I don't get charged for it.

Maximus78 said:
Phone is stuck in apx mode or something, you'll have to send it back for repair. I just did it 4 days ago, It's really worring because I'm seeing a lot of these cases but nobody has reported back to say what htc has done about it. I hope I don't get charged for it.
Click to expand...
Click to collapse
Is that likely to be software related? As Im giving a HTC rep a hard time on the Chat and he has stipulated the following (which i am tasking him about as i believe he is in accurate)
'Should our engineers find any physical damage, wear and tear, illegal software, illegal repair attempts or your warranty has expired, the repair will be chargeable and we will send you a quote via email.'
Well that covers every single warranty claim does it not?

Used to have this problem with my sensation xe,connect to pc and 're boot your bootloader,can't remember the exact commands.
Worth a try ..
Sent from my HTC One X using xda app-developers app

Phone is dead send it to HTC ,they will repair it under warranty,HTC won't know anything because phone is DEAD

atrako1973 said:
Phone is dead send it to HTC ,they will repair it under warranty,HTC won't know anything because phone is DEAD
Click to expand...
Click to collapse
How do i know its 100% dead, can they do anything i can't? Also they can tell from my IMEI its rooted and will blame that as a way to avoid a warranty claim.

markb63 said:
Used to have this problem with my sensation xe,connect to pc and 're boot your bootloader,can't remember the exact commands.
Worth a try ..
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
I have tried various ABD reboot commands (to my brief knowledge) and its non existent as far as a PC is concerned

vis-tec said:
I have tried various ABD reboot commands (to my brief knowledge) and its non existent as far as a PC is concerned
Click to expand...
Click to collapse
Mine wasn't non existent to my pc. When I connected it via usb my pc made a sound but not like the normal one and then windows said it couldn't install the drivers. So each time I connected it a strange exclamation mark was showing where normally it would show usb connected.
There is no wear and tear and not opened it but if they mean illegal software as in custom rom then I'm F***ed. So I'm not sure how they'll respond. Got a msg from three uk today saying they've received my device and are assessing it now. So that was two days of sending it in, not bad.
Think I might open a thread when I get it back letting everyone know the final outcome since I haven't seen anyone reporting on what similar experience they've had.

vis-tec said:
How do i know its 100% dead, can they do anything i can't? Also they can tell from my IMEI its rooted and will blame that as a way to avoid a warranty claim.
Click to expand...
Click to collapse
Again HTC has no chance in hell to know whatever happened to your phone ,they will change the motherboard ,end of story,please send it to HTC ,call them ,tell them phone is not respoding to anything,don't mention root or anything like that,they will arange pick-up ,HTC one x still has 16 months warranty, send it don't be a chicken

even mines stuck in apx mode..i also have given the phone to service centre...curiously all the post about apx mode have occured after they upgraded to jb.

kartiyk said:
even mines stuck in apx mode..i also have given the phone to service centre...curiously all the post about apx mode have occured after they upgraded to jb.
Click to expand...
Click to collapse
I never upgraded to JB so that debunks that myth, H3G_001 cid. I started experiencing massive lock-ups and force closures before it stopped responding (apx-mode). I have sent it in for repair now.

Maximus78 said:
I never upgraded to JB so that debunks that myth, H3G_001 cid. I started experiencing massive lock-ups and force closures before it stopped responding (apx-mode). I have sent it in for repair now.
Click to expand...
Click to collapse
right then~ even i faced lot off errors just before it went dead....unfortunately i thought it to be a rom issue,but learnt my fate a few hours later !

Don't believe mine was an APX issue. Didnt get the 'APX Scfreen' that many describe or any kind of recognition from a PC either on the PC or the phone.
Phone was collected 2 hours ago. Will advise when i hear from them. If not i will put an insurance claim in through my phone insurance.

vis-tec said:
Don't believe mine was an APX issue. Didnt get the 'APX Scfreen' that many describe or any kind of recognition from a PC either on the PC or the phone.
Phone was collected 2 hours ago. Will advise when i hear from them. If not i will put an insurance claim in through my phone insurance.
Click to expand...
Click to collapse
apx screen doesnt show up in our phones. when you connect the device through usb it will show up as drivers not avaialable or so.and apx will be shown in device manager window

I have same problem with my One X. Phone is now in service and I wait to see what will be with my phone. I also have many problems with some apps, IGO stop to work, Google maps also and when I try to open quadrant standard my phone turn off display and died :crying: .
I am from Europa (Serbia) I bought brand new phone from a guy who brought it from Singapore (don´t have warranty). Phone is CID - 044 and Asia_WWE. My friend have phone service and yesterday he try everything and nothing, today will try with something what he called "BOX"

This is getting scary because the exact same thing is happening to many of us now and around the same time. I accepted a quote from three uk yesterday of £76 to repair it. The three service centre chap said due to illegal software they were not able to flash it. I am very saddened that I won't be able to flash from now on.

Maximus78 said:
This is getting scary because the exact same thing is happening to many of us now and around the same time. I accepted a quote from three uk yesterday of £76 to repair it. The three service centre chap said due to illegal software they were not able to flash it. I am very saddened that I won't be able to flash from now on.
Click to expand...
Click to collapse
If Three UK supplied your phone, you shouldn't have to pay. Consumer protection laws.

BenPope said:
If Three UK supplied your phone, you shouldn't have to pay. Consumer protection laws.
Click to expand...
Click to collapse
But they knew I'd put illegal software on it. I'm sure they just connected it to their pc got a nod from htc and that sorted that problem out. 76 quid please for looking at it.

HTC One M8 bricked

My HTC One M8 got bricked while updating to android 4.4.4 (eye experience). According to futuretel, the warranty is only active for three months without a receipt. I tried locating a reliable phone repair shop in Toronto and its been a nightmare. HTC has the worst customer service I have ever experienced. The phone still contains my data. Any tips or advice would be greatly appreciated.
please note: the power button is broken

khanvict786 said:
My HTC One M8 got bricked while updating to android 4.4.4 (eye experience). According to futuretel, the warranty is only active for three months without a receipt. I tried locating a reliable phone repair shop in Toronto and its been a nightmare. HTC has the worst customer service I have ever experienced. The phone still contains my data. Any tips or advice would be greatly appreciated.
please note: the power button is broken
Click to expand...
Click to collapse
Well I guessed you bought an old phone
Sent from my HTC One_M8 using XDA Free mobile app

danger12345 said:
Well I guessed you bought an old phone
the phone was sealed but I misplaced the receipt while moving
Click to expand...
Click to collapse

khanvict786 said:
danger12345 said:
Well I guessed you bought an old phone
the phone was sealed but I misplaced the receipt while moving
Click to expand...
Click to collapse
Bricked how? Like, it won't turn on at all? I've seen a lot of people on this site say "hard bricked" when it is something that can be fixed with some guidance.
Does it turn on?
Click to expand...
Click to collapse

There's a lesson here, always keep your receipts. Also if it was broken already then you should have had it replaced. Unless you caused the damage then they won't replace it regardless because you could be the reason why it bricked

superchilpil said:
There's a lesson here, always keep your receipts. Also if it was broken already then you should have had it replaced. Unless you caused the damage then they won't replace it regardless because you could be the reason why it bricked
Click to expand...
Click to collapse
He has two posts, which doesn't really tell his experience with rooting and "bricks", but is usually a good indication. I have a feeling he can fix it with some help.
I could be wrong though. No answer on the "will your phone turn on?" yet.
EDIT: no power button. not bricked. hardware issue. should read the whole post instead of having another sip of beer.

xunholyx said:
khanvict786 said:
Bricked how? Like, it won't turn on at all? I've seen a lot of people on this site say "hard bricked" when it is something that can be fixed with some guidance.
Does it turn on?
Click to expand...
Click to collapse
No, the phone won't turn on. However, my computer picks up the device (connects then disconnects). I'm heading to a repair shop just now.
Click to expand...
Click to collapse

khanvict786 said:
xunholyx said:
No, the phone won't turn on. However, my computer picks up the device (connects then disconnects). I'm heading to a repair shop just now.
Click to expand...
Click to collapse
I bet it's not bricked. Did you try to boot into recovery using the toolkit?
Click to expand...
Click to collapse

superchilpil said:
There's a lesson here, always keep your receipts. Also if it was broken already then you should have had it replaced. Unless you caused the damage then they won't replace it regardless because you could be the reason why it bricked
Click to expand...
Click to collapse
Learnt the hard way. The phone was working perfectly fine except for the power button. After the update, the phone was stuck in a boot loop between update symbol and low battery. I pulled out the sd card and now its just showing a flashing red light. I am going to get the power button fixed just now and get the technician to diagnose any other issues.

Did you happen to buy the device with a credit card? This almost always will suffice as a proof of purchase or receipt.
If your phone was in a loop when the battery died, its not bricked.

update
The phone shows up as QUALCOMM HS-USB QDLoader 9008 (com 3)
I'm planning on buying another phone (not HTC)

khanvict786 said:
The phone shows up as QUALCOMM HS-USB QDLoader 9008 (com 3)
I'm planning on buying another phone (not HTC)
Click to expand...
Click to collapse
Its technically bricked but there are tools that you could use to fix it, but I doubt you want to take that much effort in fixing it.
So what was the point of this thread? You obviously don't want to fix it. So you just wanted to whine about it? Good luck on your next phone, don't brick that one too.

Pretty sure my m8 is bricked
Hey i sort of hi-jacked this thread , however it relates to my matter. I tried to convert my HTC into google play edition, I s -off, unlocked the boot loader and rooted it. Now for the fun part I went to flash a google m8 rom and BAM boot loaader came up with tampered and not only that the rom didn't work and now the htc boot screen (the white one) has a lock on the bottom and i can't do anything. I can access TWRP and have flashed other roms to it but it keeps denying them and going to the same htc boot screen with that lock symbol. Anyone please help I just got this phone and feel like I should never gotten myself mixed in this modding business lol . Thanks for anyone that can help me resolve this.

superchilpil said:
Its technically bricked but there are tools that you could use to fix it, but I doubt you want to take that much effort in fixing it.
So what was the point of this thread? You obviously don't want to fix it. So you just wanted to whine about it? Good luck on your next phone, don't brick that one too.
Click to expand...
Click to collapse
The only viable solution I came across is JTAG. Can you please share those tools? Phones shouldn't be bricking when updating on stock

Really...really bricked OnePlus 3

Hi guys, I would like to share my experience with a bricked OP3, I own my OP3 about 3 months ago, currently I'm running 3.5.3 CB, and zero problems with the device until now.
My younger brother has his OP3 about two months ago, and I don't know what's he thinking but he flashed a CM12 on his OP 3. Really I don't understand why a person could do that, however he really screw the phone. Never return from death.
I've tried all guides and possible solutions for the brick, there is no bootloader, no recovery, no vibration, no anything. The phone is really dead.
The device it's recognized by the pc after installing qualcomm drivers and after pressing power +volume up buttons, like qualcomm 9008, and it gets recognized by the unbrick took (msm download tool v3.0).
And when I start the tool it start to flash anything goes apparently well, green successful message. But phones continue as a expensive brick.
When I plugged the phone like it should be, pressing only volume up and connecting cable it gets correctly recognized like qualcomm 9008, and by the tool, but when I hit start, it give me that saharra communication failed message.
But when I unplugged and connect again and hit power + volume up, gets recognized again but I doesn't have that Sahara error and even its flashed with the tool, but phone continue to be dead.
I've disassembled the phone to see if I can see some simple trouble in the hardware maybe, I tested changing parts with my phone to see if the trouble is in some charging or display or anything like that, but all parts are working well.
Even I've put my motherboard on the dead phone and it works perfectly.
I can give up to leave this phone dead like that but I've tried anything possible so I'm planning selling spare parts.
In my country I don't have any SAT or any place like that to repair the phone.

dannytgt said:
Hi guys, I would like to share my experience with a bricked OP3, I own my OP3 about 3 months ago, currently I'm running 3.5.3 CB, and zero problems with the device until now.
My younger brother has his OP3 about two months ago, and I don't know what's he thinking but he flashed a CM12 on his OP 3. Really I don't understand why a person could do that, however he really screw the phone. Never return from death.
I've tried all guides and possible solutions for the brick, there is no bootloader, no recovery, no vibration, no anything. The phone is really dead.
The device it's recognized by the pc after installing qualcomm drivers and after pressing power +volume up buttons, like qualcomm 9008, and it gets recognized by the unbrick took (msm download tool v3.0).
And when I start the tool it start to flash anything goes apparently well, green successful message. But phones continue as a expensive brick.
When I plugged the phone like it should be, pressing only volume up and connecting cable it gets correctly recognized like qualcomm 9008, and by the tool, but when I hit start, it give me that saharra communication failed message.
But when I unplugged and connect again and hit power + volume up, gets recognized again but I doesn't have that Sahara error and even its flashed with the tool, but phone continue to be dead.
I've disassembled the phone to see if I can see some simple trouble in the hardware maybe, I tested changing parts with my phone to see if the trouble is in some charging or display or anything like that, but all parts are working well.
Even I've put my motherboard on the dead phone and it works perfectly.
I can give up to leave this phone dead like that but I've tried anything possible so I'm planning selling spare parts.
In my country I don't have any SAT or any place like that to repair the phone.
Click to expand...
Click to collapse
Damn that sucks. He probably flashed the wrong rom or something else. You should contact oneplus and see if they can do something about it cuz i reckon your brother's phone still has warranty.

dannytgt said:
Hi guys, I would like to share my experience with a bricked OP3, I own my OP3 about 3 months ago, currently I'm running 3.5.3 CB, and zero problems with the device until now.
My younger brother has his OP3 about two months ago, and I don't know what's he thinking but he flashed a CM12 on his OP 3. Really I don't understand why a person could do that, however he really screw the phone. Never return from death.
I've tried all guides and possible solutions for the brick, there is no bootloader, no recovery, no vibration, no anything. The phone is really dead.
The device it's recognized by the pc after installing qualcomm drivers and after pressing power +volume up buttons, like qualcomm 9008, and it gets recognized by the unbrick took (msm download tool v3.0).
And when I start the tool it start to flash anything goes apparently well, green successful message. But phones continue as a expensive brick.
When I plugged the phone like it should be, pressing only volume up and connecting cable it gets correctly recognized like qualcomm 9008, and by the tool, but when I hit start, it give me that saharra communication failed message.
But when I unplugged and connect again and hit power + volume up, gets recognized again but I doesn't have that Sahara error and even its flashed with the tool, but phone continue to be dead.
I've disassembled the phone to see if I can see some simple trouble in the hardware maybe, I tested changing parts with my phone to see if the trouble is in some charging or display or anything like that, but all parts are working well.
Even I've put my motherboard on the dead phone and it works perfectly.
I can give up to leave this phone dead like that but I've tried anything possible so I'm planning selling spare parts.
In my country I don't have any SAT or any place like that to repair the phone.
Click to expand...
Click to collapse
Really sorry To hear it?? BUT CM12 rom??? ? where he find it....?? if you hard bricked phone.. go to a expart devs shop.. he may be solved your problem

If your phone will not power on oneplus service center person are also not able to check how your phone will dead i think so you can claim the warranty.

CM 12 roms developed for One Plus 2,I don't really now why in the hell he do that, but he did it: https://forums.oneplus.net/threads/cyanogenmod-os-12-1-yog4pas1n0-update-25-08-15.349531/
What do you mean with expert dev shop?
Anyway I didn't think I will find some like that shop, I'm in Buenos Aires, Argentina, and maybe 99% of the cellphones technician didn't know anything about Oneplus 3,that's the reason why I've disassembled by miself.

dannytgt said:
CM 12 roms developed for One Plus 2,I don't really now why in the hell he do that, but he did it: https://forums.oneplus.net/threads/cyanogenmod-os-12-1-yog4pas1n0-update-25-08-15.349531/
What do you mean with expert dev shop?
Anyway I didn't think I will find some like that shop, I'm in Buenos Aires, Argentina, and maybe 99% of the cellphones technician didn't know anything about Oneplus 3,that's the reason why I've disassembled by miself.
Click to expand...
Click to collapse
No wonder why it got bricked xD. You should see if you still have the warranty for your brothers phone. Contact oneplus and see if they can replace the phone.

I contact oneplus and they say me I wanna contact my seller to review warranty, but I bought on "Mercado libre" some trading online place like ebay.
So we are in a really bad situation.

dannytgt said:
I contact oneplus and they say me I wanna contact my seller to review warranty, but I bought on "Mercado libre" some trading online place like ebay.
So we are in a really bad situation.
Click to expand...
Click to collapse
Well ****. Can't you contact the seller that you bought it from? Also your brother should be careful next time he flashes a rom. We all make mistakes, sometimes ppl have to learn it the hard way.

Yes this will be the first phone since 2005 year when I started to flash custom roms on samsung omnia i900, thats really dead, I bring from the death a lot of bricked phones. But this phone is really dead so I think I will start sparing parts, maybe we can recover some of the money invested on the device.

Nexus 5X hard bricked. Is there definitely no way to fix it?

I have a Nexus 5X (running Oreo 8.0 rooted) which was working fine until yesterday. The phone was responding very slowly so I decided to power it off. After that the phone will not power on at all. When I connect it to PC via USB, it shows up as "QHSUSB_BULK" in device manager. I have read online that this means the phone is hard bricked. I bought the phone in June 2016 and the warranty only lasts a year so I can't RMA it. What should I do? I really liked the 5X and nothing out there really compares to it.

@gwynlordofcinder: sad for you. But why you ask the same question as 20 others before? Try freezer and/or oven to get back the mainboard-connections. If successfull, you can save your data or go on with a kernel-profile which makes the big core sleep. Use search for details.

gwynlordofcinder said:
I have a Nexus 5X (running Oreo 8.0 rooted) which was working fine until yesterday. The phone was responding very slowly so I decided to power it off. After that the phone will not power on at all. When I connect it to PC via USB, it shows up as "QHSUSB_BULK" in device manager. I have read online that this means the phone is hard bricked. I bought the phone in June 2016 and the warranty only lasts a year so I can't RMA it. What should I do? I really liked the 5X and nothing out there really compares to it.
Click to expand...
Click to collapse
They have extended the warranty to 18 months, or someone said 24 months, since there is a hardware issue with the 5X.

Most likely fixable, but with the need of special files.
Search up on QD Loader 9008 on this subforum and read through it.
i'm on the hunt to find a fix for it, hopefully i'll make it. gonna share my findings asap!

Voicebox said:
They have extended the warranty to 18 months, or someone said 24 months, since there is a hardware issue with the 5X.
Click to expand...
Click to collapse
There is no extended warranty in the UK, which is where I purchased the phone.

gwynlordofcinder said:
There is no extended warranty in the UK, which is where I purchased the phone.
Click to expand...
Click to collapse
Since this happened from normal usage and not from you installing a custom ROM or updating the bootloader, or something like that, I think you have the bootloop problem. I normally think of a hard brick being the result of flashing say the incorrect bootloader, or a corrupt file, etc. which can then hopefully be undone by software means to get the right software back on there.
If you have the bootloop, it is a hardware problem. The fact that the phone doesn't bootloop does not mean you don't have the hardware problem. Boot looping was just the most common way to identify it, but many, like mine would just either never even start booting, or would start, then go black.
If you don't figure out any software way to do anything, then try to look for bootloop fixes. Searching for that might get you further. But with a hardware problem, everything except the fix for disabling the big cores (in XDA threads), is temporary unless you are lucky.
Assuming you have a hardware issue, here's some steps to maybe try. I was able to get the rescue fix installed on my phone after using a hair dryer on the motherboard. But that didn't fix anything since my problem was hardware. But if your OTA update was maybe slightly corrupted, maybe it'll help.
https://productforums.google.com/forum/#!topic/nexus/G_0s70PzK_s
To jump right to trying a rescue OTA, go here:
https://productforums.google.com/forum/?utm_medium=email&utm_source=footer#!topic/nexus/hdrNONCCoNE
If it doesn't react enough to do anything from a computer, you may have to resort to putting it in the freezer for a while first. Which may give a short period where it'll boot and you can maybe adjust the settings so you can try one of the XDA fixes that disable the big cores.
One fix that disables the big cores:
https://forum.xda-developers.com/nexus-5x/general/untested-nexus-5x-bootloop-death-fix-t3641199
Example video of heat gunning the motherboard. He did hair dryer, but then did it again with a heat gun. That's in a separate video of his. By using a heat gun, I was able to get it to where I could pull my data off and it even acted normal for 9 hours. Then rebooted and then eventually ended up bootlooping. The fix to disable the big cores was not around back then, so I never have tried it, and ended up getting the 5X replaced by Google.
https://www.youtube.com/watch?v=SD25mdrgAys
Different walk through:
https://www.youtube.com/watch?v=6HlqfB7VD1E

Voicebox said:
which can then hopefully be undone by software means to get the right software back on there.
Example video of heat gunning the motherboard. He did hair dryer, but then did it again with a heat gun. That's in a separate video of his. By using a heat gun, I was able to get it to where I could pull my data off and it even acted normal for 9 hours. Then rebooted and then eventually ended up bootlooping. The fix to disable the big cores was not around back then, so I never have tried it, and ended up getting the 5X replaced by Google.
https://www.youtube.com/watch?v=SD25mdrgAys
Different walk through:
https://www.youtube.com/watch?v=6HlqfB7VD1E
Click to expand...
Click to collapse
except that the files needed for unbricking corrupt bootloaders/eMMCs' are so hard to find it's incredible.
bought a used 5X that "suddenly died in a pocket", now that you mention all of this, i might try doing the hardware fixes and then apply the big core disabling and hopefully get my phone to work.
the phone did get serviced though, so they might've installed bad firmware since the phone is in QDLoader & in EDL mode (PC recognizes the phone, while fastboot/adb/LGUP doesn't)

gwynlordofcinder said:
I have a Nexus 5X (running Oreo 8.0 rooted) which was working fine until yesterday. The phone was responding very slowly so I decided to power it off. After that the phone will not power on at all. When I connect it to PC via USB, it shows up as "QHSUSB_BULK" in device manager. I have read online that this means the phone is hard bricked. I bought the phone in June 2016 and the warranty only lasts a year so I can't RMA it. What should I do? I really liked the 5X and nothing out there really compares to it.
Click to expand...
Click to collapse
Can you update driver "QHSUSB_BULK" in device manager by choose driver manually . I have problem like this in Inew V3 (Chaina Phone) and can fix by choose driver manually.