hard brick in Nexus 5X - Nexus 5X Q&A, Help & Troubleshooting

Hi I'm new on the forum and I have a Nexus 5X H790 32GB but get's hard bricked, the phone had the bootlop problem and in a attempt to bring back to life the phone die, the pc doesn't recognize it and I can't get into bootloader, so if anyone can help will be really great, thanks

Related

QHSUSB_DLOAD after replacing a faulty battery.

A couple of months ago my battery started dying, it couldn't hold a charge and had swelled up quite a bit. Before I replaced the battery I rebooted the phone into recovery and tried to recover it to a previous state, I think this is were something when wrong. So I'm stuck here wondering if there's any way to restore my G2 to a working state, I noticed there's a way to recover from QHSUSB_DLOAD on other HTC devices but I doubt the procedure would work on this model.
If that is the only mode you can get into then phone is a brick. I've been trying to get the devas in charge of the unbricking project to make something work for the g2/dz in this scenario but no love. Sorry
maybe if you can find out exactly where you care from and what you did to get in this situation I may* be able to help
Sent from my Nexus 7 using xda premium

Nexus 5x кирпич

Hello , help please , I accidentally put the firmware on the 5th nexus 5x . Now he does not turn vrrbshe , no matter what does not respond , you can restore it as something ?? Replacing the board is quite expensive , and money to replace it I have not. Would be very grateful . Phone 4g 16gb

Nexus 5x problems after screen replace

Hi all
Got the girlfriends sons nexus 5x a new screen and have replaces it but the trouble is that it will turn off and on and will not let us use lg uppercut to re flash the bugger.
Thanks in advance

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.

My Nexus 5x got the bootloop yesterday, can't fix it by myself.

Hello
My Nexus 5x 16 GB (LG H791 ) got the bootloop, i need to fix my phone !
Soo yesterday was a very hot day.
I ran around a bit outside and took a lot of pictures. But it was very hot outside. Whenever I take pictures, HDR has to be rendered first, it consumes a lot of power and I can imagine that the Nexus 5x gets hot. When I put it in my pocket, it still worked. After I got it out again, the screen was completely black and it could not boot anymore. It was just black, nothing worked.
Later, I went home to look at the Nexus 5x.
I looked at whether it was possible to get into fastmode, dloadmode and recoverymode, but the screen remained black.
I've fixed other cell phones before, but with the Nexus 5x, I still have some little hopes.
I opened the nexus and cleaned it completely with 100% alcohol. Every corner and every connector.
After cleaning I switched it on again and suddenly it started again.
But it only showed the colorful google animation and it restarted after a short time and it repeated itself endlessly.
From there I noticed that it is the well-known bootloop problem.
I knew before that it will eventually come to this problem, so I unlocked my OEM (Bootloader) about 1 year ago :good: !
So I googled and there seem to be some fixes !?
First of all, I tried THIS and it didn't help
I tried also from this solution the TWRP recovery. Jeah i got in to the TWRP recovery and installed the EX4_10_5X.zip, but with some errors. The Nexus is still repeating... BUT!! The google logo animation was stuck, no animation!
Soo I googled more and more and saw a new solution!
THIS! So i did all 4 stepts expect step 1, because it's already unlocked.
JEAH! My Nexus 5x seems to be ok again ! After I set everything up, the Nexus 5x has frozen and crashed ! Man damn!! I was sooo happy..
Then i tried to flash the latest factory image from https://developers.google.com/android/images?hl=en#bullhead
I ran the "flash-all.bat", got no problems the first time, but the Nexus is still bootlooping :/
So i flashed it again with a factory image from 8.1.0 (OPM1.171019.011, Dec 2017).
But this time the Nexus has freezed and turned off!
It restarted by itself, but there was no Google logo anymore. It restarted each time after the message came that the Nexus is unlocked.
If I go into fast mode, it freezes after a short time, it is not possible to flash an image on it, because after a "fastboot reboot-bootloader" command, the Nexus just stops responding, so I have to disconnect the battery.
If I reconnect the battery immediately, the screen will still be black.
So I always have to wait 3 minutes until I can connect the battery again. This is exactly as with a USB-C cable.
I got one time a crash or greenscreen !
I saw a thread about (BLOD).
I downloaded the latest fix files. After i got really quick into the fastboot mode, i flashed this two things and jeah i got my google logo back, but it still freezes and it won't turn on, only if I reconnect the battery after some minutes.
Now my problems:
No Google logo (Rare)
It stays off after it freezes
It's hard and randomly that I get into the recovery mode with TWRP. If I make it, the nexus freezes again
I can not flash an image because the screen stays black every time I restart
I can't fix it, i need your help ! Pls
Community ? Can you help me ?
@MrClean24, I'd say goodbye: even if you succeed to make it run with sleeping cores, it's slow and wont be stable.
rp158 said:
@MrClean24, I'd say goodbye: even if you succeed to make it run with sleeping cores, it's slow and wont be stable.
Click to expand...
Click to collapse
Man damn, it don't wan't to give it up
@MrClean24, a new mainboard?
rp158 said:
@MrClean24, a new mainboard?
Click to expand...
Click to collapse
That was my first idea, but i don't wan't to use any money for this phone
If it can't be fixed, then i will buy a Pixel 3a phone.
@MrClean24, good idea (I'm not favouring bin generally, but you wont fix damaged hardware by software plasters durably)
Jeah its a hardware problem :/ I think mine can't be fixed anymore, but thanks
Join the club
My old n5x is death with that problem
My old Nexus 4 have the same problem too
2 Nexus deaths ??
in 2018 I bought a pixel 2 xl and is a great machine
manfio said:
Join the club
My old n5x is death with that problem
My old Nexus 4 have the same problem too
2 Nexus deaths ?
in 2018 I bought a pixel 2 xl and is a great machine
Click to expand...
Click to collapse
Can't wait 4 my pixel 3a

Categories

Resources