Hey!
I just got a bricked N5X from my friend. It doesn't show any sighs of life (download mode, recovery, etc.) except lovely Qualcomm HS-USB QDLoader 9008 when I connect phone to the PC.
I searched a lot of post across the Internet and there are couple of ways to (at least try to) fix ix, but I miss files to do that. BoardDiag doesn't support this chip and even if I want to try I cannot find .tot files for 5x.
So is there any way to fix it? To get img files needed or something else?
Thanks in advance!
Unfortunately, my Nexus 5X just got bricked as well. It was working fine until all of a sudden, it rebooted while using Google Maps & Bluetooth to stream the navigation and music. Then it got stuck on the Google boot screen and since then, it would not boot. I was able to get it to start in bootloader mode and recovery mode a few times. I was even able to clear cache once but that was it. Now, I can only get it to start in bootloader after pressing and holding the power + vol.down button for at least 20 secs.
I tried plugging into my computer and it shows the Qualcomm HS- USB QDLoader 9008 (COM5) under Ports (COM & LPT).
What can I do to recover from this?
If you are able to go to the download mode, then maybe you can try LGUP to flash original image. You can more info on other xda forums
konker said:
Unfortunately, my Nexus 5X just got bricked as well. It was working fine until all of a sudden, it rebooted while using Google Maps & Bluetooth to stream the navigation and music. Then it got stuck on the Google boot screen and since then, it would not boot. I was able to get it to start in bootloader mode and recovery mode a few times. I was even able to clear cache once but that was it. Now, I can only get it to start in bootloader after pressing and holding the power + vol.down button for at least 20 secs.
I tried plugging into my computer and it shows the Qualcomm HS- USB QDLoader 9008 (COM5) under Ports (COM & LPT).
What can I do to recover from this?
Click to expand...
Click to collapse
hardware issue, google and LG are apparently aware of this. Mine just crapped out and Im one month out of warrunty so I was able to get google to do a one time replacement. Thought who knows how long that one will last.
My Nexus 5X just crapped out about 5 minutes ago. I was using Chrome and it froze, so I held the power key. It is stuck in a boot loop. If I VolDn+Power I get the menu to go to go into recovery, but it doesn't succeed. Tonight when I get home if there's anything to try via ADB I'd appreciate a link, but I figure it's the hardware problem. Bootloader Version BHZ11h. I'm out of warranty but have an extended one from my credit card company.
Same here...I am really frustrated about that!Another bricked nexus out of nowhere..!!Don't know what to do!
Since i still have warranty is it better to go to the place i bought to ''fix'' it as they said or send an email to google if they can replace it..?
what do you think? is there any way to save our data?
My Nexus 5x froze up without warning earlier this week while listening to spotify and playing ingress.
I managed to reboot it but the same thing happened again so I booted it up in recovery mode and did a factory reset. Now the phone is dead other then the LED flashing red while connected to the charger.
I contacted the reseller and i'm gonna ship it of today to be repaired i hope.. unless the repairshop claim it's been water damaged or some other "#ยค"#%.
Here's another Nexus 5X bricked: it frozes playing War wings.
Sent in warranty to LG repair center they changed the mobo and sent me back in 4 weeks: how many time could work now?
link: https://pan.baidu.com/s/1TmQ9jmdAym2NYt_YGyt2Cg pin : g5cg
this rom test at my phone nexus 5 use firehose 8974 , no firehose 8994 ,your must find 8994
Related
Hi , today when using the camera app to record a video it got hanged and went off, restarted and put the code mobile went off again and never came on , just 3 months old mobile .
Stock android
when connected to windows PC, sounds comes , that device is connected and shows up in the device manger as qualcomm hs usb qdloader 9008 . ( no led , or screen on mobile )
power button long press or the volume and power does not work too .
whats the best option , show it to the service center/RMA ???
julesbgoes said:
Hi , today when using the camera app to record a video it got hanged and went off, restarted and put the code mobile went off again and never came on , just 3 months old mobile .
Stock android
when connected to windows PC, sounds comes , that device is connected and shows up in the device manger as qualcomm hs usb qdloader 9008 . ( no led , or screen on mobile )
power button long press or the volume and power does not work too .
whats the best option , show it to the service center/RMA ???
Click to expand...
Click to collapse
Try holding the power button for about 10 seconds waiting for a reboot. Once it reboots turn it off and use the "Option 2" from this guide, only when you get to step 6 of this "Option 2", DON'T do a "wipe data/factory reset" just yet, and do a wipe cache only and reboot. See if this will get your device behaving again.
https://support.google.com/nexus/answer/4596836?hl=en
And also do the above while you've removed your sim card.
Sent from my Nexus 5X using XDA-Developers mobile app
julesbgoes said:
Hi , today when using the camera app to record a video it got hanged and went off, restarted and put the code mobile went off again and never came on , just 3 months old mobile .
Stock android
when connected to windows PC, sounds comes , that device is connected and shows up in the device manger as qualcomm hs usb qdloader 9008 . ( no led , or screen on mobile )
power button long press or the volume and power does not work too .
whats the best option , show it to the service center/RMA ???
Click to expand...
Click to collapse
There's a reasonable chance your EMMC storage started dying.
If you have bootloader unlocked try flashing factory image.
If not, see if you can boot into recovery, then try flashing the full OTA (not the partial/differential OTA) using adb sideload.
If that doesn't work, there is a thread about recovering from qualcomm hs usb but that is from a bad flash, not a corrupt EMMC.
Most likely you'll need to RMA the unit, but those are some things you could try.
I removed the SIM card , now if i hold the buttons , i just get red light flashing nothing else
julesbgoes said:
I removed the SIM card , now if i hold the buttons , i just get red light flashing nothing else
Click to expand...
Click to collapse
RMA .
julesbgoes said:
I removed the SIM card , now if i hold the buttons , i just get red light flashing nothing else
Click to expand...
Click to collapse
Dead battery signal. It probably won't even charge anymore. Contact Google Nexus support and document all the troubleshooting steps you've done so they don't ask you repeat all this. They should ship you a new one and ask you to send the faulty one back.
Best of luck.
Sent from my Nexus 5X using XDA-Developers mobile app
Thanks for the replies , i got the mobile from amazon , so it has to be repaired by LG and they said the board is gone and all the data , i dont trust them because most Indians don't do software stuff.
The board is not in stock and will take more then 10-15 days .
Would have i avoid warranty if i had tried the qualcomm hs usb qdloader 9008 boot loader stuff ?
julesbgoes said:
Would have i avoid warranty if i had tried the qualcomm hs usb qdloader 9008 boot loader stuff ?
Click to expand...
Click to collapse
If you got the qualcomm loader via bad flash, I think the TOT file could have helped.
In your case, probably it wouldn't have helped, though given a 15 day wait, probably 3 week turnaround, it would have been worth a shot.
I wouldn't feel bad you didn't try it though, most likely would have been a waste of time as TOT file won't cure failing EMMC, which is the most likely explanation for what you described.
So, the other day my phone started acting weird. It randomly restarted, then worked another hour or so, and then started shutting down almost immediately after booting. I was running a Nexus 5X with rooted stock Android 7.0.0 (SuperSU root) and ElementalX kernel. It had been running this for a few months without any issues. I can't think of anything I did to trigger this. I didn't run any updates, I haven't flashed anything since I installed ElementalX couple months ago.
After a lot of troubleshooting (at first I could still get into the bootloader and recovery, but when I did, TWRP didn't recognize any partitions? I was unable to access the file system in TWRP), it finally got so bad that my phone is no longer recognized by my laptop other than "QHSUSB_BULK" device in the Device Manager (Windows 10 x64). Completely black screen, no response, no LED when plugging in adapter. One time I managed to get into the bootloader (randomly, no idea what triggered it) and I managed to put stock 7.1.1 on it, but soon after the installation of that, the exact same thing happened: random reboots, progressively getting worse to in the end: no recovery, no bootloader, only recognized as "QHSUSB_BULK". So I was back to the lowest point.
I read about a "hidden second bootloader" on the 5X, that would be accessable through Power+Both Volume keys, but that doesn't work at all for me (tried it for up to 1 minute of pressing).
After hours of searching (I probably read all the 5X + other phones's topics here that have this issue..), I came here: www.droidsavvy.com/unbrick-qualcomm-mobiles/
I followed those steps precisely, got my laptop to recognize the phone as 'Qualcomm HS-USB QDLoader 9008' by installing the Qualcomm drivers with driver signature verification turned off, but I just couldn't get the QFIL program to flash anything to my phone. It threw a "Download Fail:Sahara FailSahara Fail" saying it couldn't send the Flashing program to my phone. I tried several things here: attempted to power off the phone, then hold Volume up+plug in USB --> flash straight away, different driver/software versions, different laptop, but all to no avail.
I have no real way of telling whether the phone is on or off (it seems impossible to actually turn it off - if I hold power for 30 or so secs I do hear the USB disconnect-connect sound from my laptop, but the device is still shown as "QHSUSB_BULK" so it won't actually turn off properly).
My current hypothesis: it's a hardware fault (eMMC?) and as I'm still within warranty I can send it in for repair/replacement.
Perhaps there is a very slight chance that someone has also encountered this, and it's still a software problem which can be helped by me in some way?
Thanks in advance!
Its probably some part of the motherboard that is faulty. Take it into a repair center. Get it replaced.
Hey guys...
so i managed to connect my almost dead Pixel XL, to the PC
and its now know as QUALCOMM HS-USB at Device Manager...
the question is...
how to proceed now?
i found lots of guides to OnePlus, but cant find any to install Android Stock Rom...
any tips will be appreciatted!!!!!
tasty_boy said:
Hey guys...
so i managed to connect my almost dead Pixel XL, to the PC
and its now know as QUALCOMM HS-USB at Device Manager...
the question is...
how to proceed now?
i found lots of guides to OnePlus, but cant find any to install Android Stock Rom...
any tips will be appreciatted!!!!!
Click to expand...
Click to collapse
Just went through the same problem with my Pixel Xl.
To fix it i hold down the Volume Down + Power button until the phone boots in to the bootloader.
From there I just flashed the factory IMG.
Best of luck
hey my friend, i was thinking about It, but i have no screen...
how can i know that the phone booted in bootloader?
already tried...but the phone didnt connected to the computer...for sure wasnt in bootloader
Well it can be a hardware failure, but since i had the exact same problem with the black screen and my phone also showed up as QUALCOMM HS-USB 9008, i doubt it is a hardware failure. I can only suggest solutions that might work.
-Try holding in all the buttons for 14 seconds.
-Connect phone to the computer, then run "fastboot devices", if the phone is recognized(shows up in the list), flash factory img.
-Connect phone to the computer, then run "ADB devices", If the phone is recognized "ADB reboot bootloader". Then proceed as when you flash factory img.
Did you come from Android O btw ?
HALV0RS3N said:
Well it can be a hardware failure, but since i had the exact same problem with the black screen and my phone also showed up as QUALCOMM HS-USB 9008, i doubt it is a hardware failure. I can only suggest solutions that might work.
-Try holding in all the buttons for 14 seconds.
-Connect phone to the computer, then run "fastboot devices", if the phone is recognized(shows up in the list), flash factory img.
-Connect phone to the computer, then run "ADB devices", If the phone is recognized "ADB reboot bootloader". Then proceed as when you flash factory img.
Did you come from Android O btw ?
Click to expand...
Click to collapse
everything was fine with Nougat, then i received Android O update and it happened
i was browsing the web and listening to some music, then it rebooted itself and didnt come back again!
tasty_boy said:
everything was fine with Nougat, then i received Android O update and it happened
i was browsing the web and listening to some music, then it rebooted itself and didnt come back again!
Click to expand...
Click to collapse
Trie "Vol Up+Vol Down+Power for 30 sec"
I am sure you have already tried all the combinations in the world.
I would return it to google.
Best of luck.
tasty_boy said:
everything was fine with Nougat, then i received Android O update and it happened
i was browsing the web and listening to some music, then it rebooted itself and didnt come back again!
Click to expand...
Click to collapse
Hey man, have the same problem with my pixel. Did you fix it?
I had that issue to with mine. Ended up getting a RMA
Hi guys,
I am not sure what exactly happened. I was sitting around and listening to some music when my old Nexus 5X suddenly rebooted and stayed blank.
First guess - Battery. But that turned out to be quite wrong as I had charged it over night. Tried to get into fastboot mode or recovery mode; After the logo showing up and my beloved "This device isn't trusted" sign the screen went completely blank and that was the last sign of life. As it's got an USB port, I hooked the device up to a computer, found it to identify as "Qualcomm HS-USB QDLoader 9008".
Some research showed me that this is some kind of download mode, in terms of 'nothing works anymore' and you'd have to get your hands really dirty here to get at least somewhere.
So my educated guess would be bad memory or some corrupted filesystem and I'd have to reinitialize the phone to be able to fastboot or anything.
Tools already looked at:
LGUP - No joy; Device not found as this one requires something like a basic recovery mode which seems to be broken here
boarddiag - I was able to read from the memory using 'download' using a tot file I found somewhere online.
QPST - Found some prog_emmc_firehose_8992_lite_lge.mbn file, but I lack the patch and raw program files
Any ideas out there getting that bugger alive again?
Cheers
Rei
This is not a sign of download mode, your device hardbricked. As you have the firehose (I don't know if should work this) I found from another thread there the other files for QPST. I didn't tried that because this was released after I send my 5x to service (yes, for second time) due to hardbrick . https://drive.google.com/file/d/0B5EP5AzZNQxPcE52QWw2VloteUU/view
T-Mobile S8+ [G955U] -- Factory reset resulted in complete wipe & no longer boots up.
I have a Samsung galaxy S8 plus (T-Mobile) [SM-G955U]
Current Firmware:
G955USQU4CRE9
I'm using windows 7 to attempt to repair my phone.
My problem is as follows...
A few weeks ago my phone started giving me the dreaded:
"Unauthorized actions have been detected..."
error code and sending my phone to restart.
This has happened to me in the past on other phones so i thought, ok. restart and it should be fine. However, this kept happening... the next day and on the 3rd day it happened about 3 times in a row. At this point I was cautious and backed up all my files, turned on USB debugging and shut off my wifi & data.
I then proceeded to do a factory reset from the settings. Once it restarted I got a weird error stating something like no such recovery file could be found. When I saw this I knew I messed up because I didn't first take a backup of my system & recovery...
I got a hold of T-Mobile who walked me through their reset steps, none of which worked. They had me contact Samsung and I did but to no avail. Simply stated they mentioned they could fix it if I had warranty, if not I would have to pay for repair.
Either way I sent all information to Samsung and they have not gotten back to me even though they mentioned we'd hear back in 48 hours. (it's been about a week) I've tried to reach out since then but I haven't had a lot of time to sit on the phone with their elevator music...
Ever since then I've tried everything from Samsung Smart Switch to re-flashing through Odin with no luck.
I've tried all of the reset options...
Hard reset
Soft reset
Wipe cache (recovery mode)
Wipe and factory reset (recovery mode)
Simulated battery pull
etc., etc., etc.
Nothing works. Odin flashes correctly (i get "PASS") and the phone turns off but does not turn back on.
I've tried several tricks to get it to turn back on but it won't go past the boot screen (Samsung Galaxy S8+ screen)
I've flashed, re-flashed, wiped, reset, etc.
Now smartswitch doesn't even work on it because it does not recognize the device...
When i connect my phone now it just shows up as the qualcomm chip. I get "Qualcomm HS-USB QDLoader 9008" under devices...
ADB only works when it's in download mode or recovery mode but it doesn't recognize the device either...
Another problem is the increased time it takes to get into the boot menus (download or recovery).
Sometimes when I haven't touched my phone for a whole day I can get into download mode within 10 seconds or less but the more I try it and especially if I successfully flash stock software, the next time booting into recovery or download mode can take up to 5 minutes (holding the button combination). Recovery mode is worse.. even after 24 hours without touching the phone it will come up maybe in 3 minutes but has taken as long as 7 minutes... my fingers are in pain.
Essentially, even after successfully flashing my phone will not boot. and when i hold vol_down + power i can sometimes get the boot screen but it won't go past that.
Also, None of the above boot options work if my phone isn't connected to power--these options only work when it's plugged in. If my phone is not plugged in it will not vibrate, light up, boot up, or do anything other than behave as a paperweight.
I believed it may have been a charging issue so i left it plugged in overnight and even went to download mode and plugged it in for a few hours but that doesn't affect it at all. Even if i'm in download or recovery mode it'll turn off right when i unplug the device.
I'm trying to get it to the best buy that's approved for samsung repair but when I called they said they wouldn't repair it anyways because i didn't buy it there... -_-
Please let me know if I need to provide any other information. I'm trying to get an image of the recovery screen so you can see the error it gives me... Something about no file found. This is increasingly difficult though because some times it takes too long to get into these modes and I leave it alone and come back to it later.
Has this happened to anyone else? Can someone provide some sort of advice or a method to fix this?
thanks in advance.
Can you download the Qualcomm HS-USB QDLoader 9008 driver, and then see if you can fastboot oem-unlock and see if it unlocks your bootloader