I was just using my phone normally, then it hung and wouldn't restart normally. Bootloader and fastboot is accessible, but attempting to boot into system or recovery just puts me in a black screen. Connecting it to a computer via USB in that state gives me a "Qualcomm HS-USB QDLoader 9008 (COM3)" device, which from what I read, indicates that my device is superbricked.
My phone:
Nexus 5X LGH791 32GB
Bootloader version: BHZ10i
Build version: MDA89E
Device is unlocked and rooted
Have not flashed anything new in at least a month
What I've tried:
1) fastboot boot twrp-3.0.2-0-bullhead.img:
Note: Each session does not last more than 10-15 seconds, even if I don't do anything and leave it at the password entry. The phone then goes into the same black screen state.
Phone boots into TWRP, but upon trying to decrypt the filesystem, i see "Failed to mount system/cache" messages.
2) Using LGUP (http://forum.xda-developers.com/nexus-5x/help/req-help-to-unbrick-t3251740):
LGUP detects and communicates with the phone fine, but the phone hangs midway while doing the update (goes into the same black screen state). It always hangs at about 15-21% progress, at the "system" step.
3) fastboot flash from factory image
All the flashing succeeds, but the phone still cannot boot normally.
My own conclusion:
There's some storage hardware issue, and all my data is lost. I would just like to check if I have exhausted all my options, though. Even if the phone can't be saved, is there anything I can do to retrieve the data in the phone?
Your conclusion is probably correct.
Sometimes EMMC errors eventually work themselves out enough to boot if you attempt enough times for the bad areas to get remapped, but often the damage is too catastrophic to remap.
You are going to need to RMA your device regardless because you can't trust a phone that has that severe of EMMC problem even if you eventually got it to boot again.
Related
Phone hardbricked after following "[Solved] Secure Boot Error" thread. What do I do?
I followed the one click root method, which worked out well. After that, I installed su, flashify, and twrp. I then tried installing a custom rom, but upon booting into recovery mode, I received the Secure Boot Error text. It wasn't too big of a deal since I could still take out the battery, put it back in, and boot normally.
But, after seeing this thread:
http://forum.xda-developers.com/lg-g3/help/help-secure-boot-error-trying-to-boot-t3054977
and how simple the instructions were, I proceeded to give it a shot. I entered in the 4 commands, powered off my phone, and attempted to boot into recovery mode. But unlike before when I booted into recovery mode, nothing appeared. No lg logo, backlight power, nothing. It's acting as it would if nothing was powering it. Now I'm stuck with a bricked phone, and sincerely need some advice on where to proceed next. Could someone help me?
Oh, btw, when I plug the phone the computer, I do "the device was successfully installed" message. The phone appears in device manager, under Ports as LGE AndroidNet USB Serial Port or as LG AndroidNet Phone under devices and printers. It doesn't appear under This PC at all.
probably one of the core system partitions has a version mismatch which is the reason why your phone isnt turning on because the partition wasnt written correctly
you need to kick it into Qualcomm USB HS Loader 9008 by shorting out the testpoint, other than that your phone is gone
Hello,
I seem to have really messed up my G3 and after days of research I have not been able to get anywhere with it. I've read posts of people having similar issues, but their solutions do not seem to work for me.
What I tried to do is flash the ROM, starting with TWRP. After installing TWRP and rebooting I was getting the "no command" message on the screen. I believe (this was days ago), I used ADB to remove laf and reboot the phone (for some reason I could not back it up). The phone rebooted in fastboot and it has been downhill from there.
No download mode. When normally started the phone just hangs on the LG logo. Vol- and power gets me to the "Factory data reset", but if I do that, it flashes "erasing" for a second and it goes back to the LG logo screen.
I can get to fastboot, however, any command that I enter in CMD or Linux terminal just shows up on the phone's screen and it does not do anything. Fastboot devices shows the device as "????????" in Linux and as "?" in Windows. I have tried multiple drivers for Windows.
I tried BoardDiag (3 or 4 different versions running as admin) and shorting the pins, but any time I try to run the checks, I get an error - "No response from device" or "Device was not found in dload trying flash programmer"
I also tried SmartBootDiag, but once it detects the phone, it does its checks and it disconnects the device, without giving me an option to flash anything. Looking at the logs, it does not find any anti-rollback issues.
Any suggestions would be greatly appreciated as I am not sure what else to try.......
Thank you.
Anyone??
I have a non-rooted VS986 (probably 26A).
Recently I ran out the battery and the phone died. When I charged it and turned it back on, it stayed stuck at the Verizon boot screen.
I hadn't really changed anything recently, and I did not take the most recent OTA (27C) so this just seems like a random hardware failure.
I can boot into Recovery, but if I choose "Safe Mode" or "USB Debug Mode" the phone just hangs at the Verizon Screen.
I tried to Wipe Cache and restart, but it just hangs at the Verizon screen.
I *can* boot into Download mode.
I would really like to back up the internal SD card--photos, settings etc. if possible.
Is there anything I can do at this point just to get an ADB prompt or something that might allow me to perform a backup (even if limited)?
Sounds like a motherboard failure. You could try booting into download mode and using adb to pull your files but you'll have to know the exact path to their location. And to do that you would have had to have USB debugging activated.
If that doesn't work then your SOL. Time to use your insurance or warranty if it's still good.
Dear Nexus 5X users,
I would like to share my success story to booting up the bootlooped Nexus 5X. My phone was bootloader locked when the bootloop happened. After searching threads for hours, I found out I had to unlocked the bootloader. And the only way to do that is to go to the developer's option and change the OEM bootloader setting. But, it seems impossible to do that when I am having the bootlooping.
From one of the thread, I saw that one person used a hair dryer to heat up his phone, then the phone booted up normally. So, I also tried to heat up my phone. Following is how I did that. It only took ~10 minutes.
I put my phone on top of my electric radiator. The phone has a cover, so it kinda helps not to burn my phone. After 5 min later, I turned on my phone. It rebooted 2-3 times, then magically it booted up normally. So, I quickly activated developer's option and switch on the OEM bootloader unlock option.
Now, I just installed TWRP and one of the 4core kernel. It is booting normally. I hope this is helpful for someone who is in my position.
If this is not an appropriate new thread, or there is a better thread I can post to, let me know.
Man, I am in a somewhat similar situation. Was running PureNexus ROM, when suddenly got BLOD. In my desperation, I wiped data clean as soon as it booted into TWRP after a million tries. Now device won't go beyond Google logo, and the bootloader (fastboot) mode is not being detected in PC
I tried all driver installation methods, but the culprit is incorrect device ID being shown to my PC - USB\VID_0000&PID_0002\5&ECB7860&0&9 (unknown usb device - device descriptor request failed)
What do I do? I can heat up the phone but will have to continue doing it till the first boot after data wipe finishes, which can be like 10-15mins, which sounds risky.
UPDATE:
My situation was peculiar, because I had wiped the /data partition when the device was already bootlooping (managed to boot into TWRP after cooling the phone and wiped /data in my infinite wisdom). After that, I was still stuck in BLOD, except one change - PC was no longer recognizing the device in fastboot (see the hardware ID I mentioned above).
How it fixed it:
Removed the case, and heated up my phone with a hair dryer for 5min
Booted it up, it was stuck on Google logo for a fairly long time before bootlooping, as compared to earlier. My guess - it was trying to load system files, which wasn't happening when the phone wasn't heated up.
Now I booted into bootloader and PC was able to recognize the device in fastboot mode.
Finally I was able to flash the moded boot.img files to disable bigger cores and my 5X is back to being my daily driver.
So Here are the steps
1. My bootloader got unlocked.
2. I Installed factory preloader and lk images.
3. Rebooted to Fasboot and flashed TWRP 3.3.1-0924 by wzsx150 (the only Android 9 recovery that didn't get removed immediately after flashing and rebooting for 1st time to get to recovery).
4. Formatted Data, Closed AVB 2.0 and Signed TWRP.
5. Rebooted to Fastboot and flashed stock EEA Android 9 (11.0.3.0) from Global (11.0.6.0) and reflashed factory preloader and lk.
6. Rebooted to recovery, Formatted Data, Closed AVB 2.0 and Signed TWRP.
7. Using ADB sideload from Twrp Installed EEA Android 10 (11.0.2.0).
8. Rebooted into fastboot Installed Updated TWRP-3.3.1-1210 (by wzsx150).
9. Rebooted into fastboot and flashed misc.bin from same zip (according to bat file inside it should get flashed after recovery but I forgot.)
10. BRICKED. Booted to Redmi logo for 3 seconds and rebooted infinitely.
This type of brick in 4pda.ru according to google translate can be mitigated by letting battery drain and then enter DA download mode using SP Flash Tool.
I've Used the tool several time so I thought Okay no big deal.
So This is what I tried:
11. Pressed download button
12. Connected USB Cable to phone.
13. Device pauses a second (Probably for SP Flash Tool to respond) then doesn't enter DA (Unlike previous times) and screen brighten for a second or two but then turns off and repeats this process forever.
I've been using Drivers provided by Microsoft Update Catalogue but tried all the drivers on 'MTK Usb Driver v1.0.8' and 'Mediatek_Driver_Auto_Installer_1.1352.00' after disabling Driver Signature Enforcement. but even though drivers are installed they don't get loaded and after force installing them in add legacy drivers they are their but have yellow triangles and their Location lists as 'Unknown' and status as 'This device cannot start. (Code 10)'. Tried Removing them after adding them as a site suggested but that didn't work either.
I learned the hard way to never mismatch partitions with this phone. I thought having the factory preloader and lk1/2 would protect me but no.
When you say brick, do you mean you have a completely black screen with only the notification LED turning on when you plug it in?
Grab a bootable Linux image and use that on a USB stick to eliminate the driver issue you're having. Interface is identical
wang1chung said:
I learned the hard way to never mismatch partitions with this phone. I thought having the factory preloader and lk1/2 would protect me but no.
When you say brick, do you mean you have a completely black screen with only the notification LED turning on when you plug it in?
Grab a bootable Linux image and use that on a USB stick to eliminate the driver issue you're having. Interface is identical
Click to expand...
Click to collapse
So I tried Ubuntu. Problem isn't from Drivers. It's because my Windows or linux didn't ever got a chance to enter fastboot so they can load preload drivers properly.
In Windows, Mediatek USB Port is the only driver that get loaded, and that for only an instant then it disappears in Device Manager.
In Linux according to this Tutorial everything is fine but SP Flash Tool gives me a " ERROR : STATUS_ERR (-1073676287) , MSP ERROE CODE : 0x00. "
Based on this chinese site I should find my Vendor Id and Product Id specific to my system (or is it my chipset?) and then change some files but how do I get linux to recognize mediatek usb device first when It needs to enter fastboot for that to happen.
Is there any way to manually add it?
EDIT: So After some reading I realized that I have to get my phone to fastboot first to get the drivers recognized. In windows as far as I know there is no way for manually adding 'Location' to Drivers. what about Linux?
I think you're talking about a soft-brick and I'm talking about a hard-brick. If you can get to fastboot, it's a soft-brick.
Hold the volume down and power buttons simultaneously for 1min and see if your screen changes.
Don't worry about the Linux drivers, if your phone is in the correct mode, it'll work.
I don't think it's a Soft-Brick (unless Hard-Brick means even the display not turning up at all), Holding them for a minute with battery charged doesn't do anything. As soon as it boots back up it starts getting caught in Booting until Redmi logo and staying there for 2-3 seconds then reboots. I tried to hold Volume Down + Power for 3 minutes while caught in this bootloop but no fastboot. I'll retry when battery discharges again. first without usb cable attached then with.
Thanks for taking time to work this through with me. Nowadays with all service centers being closed it's really a nightmare to have something you need on internal storage and not being able to access it. First thing I'll do after this is to buy a 128GB SD card to store the important stuff.
By the way should I just use the Live Ubuntu or Install it to see if the problem is from being a live image.
When I hard bricked my phone, I didn't have anything but that white led when I plugged it in. If you have the redmi logo, should mean there is hope. I've only ever entered DA mode when I had a hard brick.
This might be one of those situations where letting the battery drop to 0% would allow you to access fastboot. MiFlash only works in fastboot and DA mode I believe. What happens when you hold volume up and power for a minute while plugged in to your computer? Run "ADB devices" to start the adb service first
I doubt it would make a difference live to installed, but it's your call if you have the time.
With Phone in Bootloop mode Holding Either Vl+ and Power or Vl- and Power doesn't make a difference.
With Phone Off and USB detached It's the same.
With USB attached Vol+ and Power for over 3 Mins result in Device Manger listing 'Mediatek USB Port' for as long as display remains 'dark but bright' (for 2-3 seconds then shuts down and turns itself back on). removing it when phone suddenly shuts down. when USB is detached phone remains shutdown.
With USB attached Vol- and Power for over 3 Mins result in Phone's Display Brightening for 5 seconds no device listing in Device Manager nor entering fastboot or being recognized by adb or fastboot (set on a permanent re-checking by a cmd script). then phone shuts itself down and back on.
LED situation:
With Vol+ and Power with USB attached LED when phone is Off is Fullbright. When Display Brightens It turns off.
With Vol- and Power with USB attached LED when Phone is Off Blinks Once Fullbright and then remains Semi-bright whether phone is on until shutdown and the Blinks Fullbright again.
I Live in Iran and with sanctions there is no way to pay anyone overseas. Unless they're willing to risk accepting cryptocurrencies from an Iranian , my only chance if I can't work it out is to wait till unofficial service centers here open.
Your phone only being detected for 5 seconds is supposed to happen. It checks for a signal from so flash and if it doesn't see it, drops off.
I'm not sure paying someone to remotely flash your phone will work if SP Flash isn't even trying or detecting your phone. With mine, it would detect and try to flash (red bar sitting at 100%) before throwing an error.
Try letting your battery die, if that doesn't work, maybe the test point mod will work. Otherwise, I think your only option is a service center.