So, my lg g5 h850eu one day started turning on and off when finally show screen like this
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
.
So i downloaded minimal adb and fastbooot and typed "fastboot reboot". After this commend phone turned off and never displayed anything. In device manager show qualcomm hs-usb QDLoader 9008 (com3) and in minimal shows error: no devices/emulators found. I wanted use lgup to flash stock firmware but shows no handset connected.
What can i do in this situation?
Unfortunately, this isn't possible to fix this in my experience since the firehose and required program and rawprogram0.xml files do not work with the G5. The only solution is to replace the motherboard.
najak223 said:
So, my lg g5 h850eu one day started turning on and off when finally show screen like this
.
So i downloaded minimal adb and fastbooot and typed "fastboot reboot". After this commend phone turned off and never displayed anything. In device manager show qualcomm hs-usb QDLoader 9008 (com3) and in minimal shows error: no devices/emulators found. I wanted use lgup to flash stock firmware but shows no handset connected.
What can i do in this situation?
Click to expand...
Click to collapse
The same thing happened to me yesterday. First the stock camera started to hang, clearing data solved that, but at night it began to restart until the "fastboot" escreen appeared. Then I removed the battery, put the reserve one (a new one) and it never gave again a life signal...:crying:
Related
Hello and thanks for readingSo, i will to explain my situation:
The phone is stucked in edl.
The phone was runing miui 9.5.
The device manager see the 9008 qloader.
Mi flash tool see the device.
The led blink in red.
No mi logo.
No fastboot.
No vibration.
No unlock bootlader.
Here comes the errors:When i try to flash this fastboot room in the mi flash tool, i get the following error: Ping target failed.
Here screen shoot and log.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
View attachment log.rar
When i try with QFIL 2.0.0.3 i get this error (Device is not in firehose mode):
Aditional info:
I try with a couple of roms, devolper and stable.
I am triying to flash from windows 10 64 bit (driver enforce are disabled).
I tryed with deep flash cable (cortocircuit green and white)
When i try with older mi flash tool (2015), i get stuck in send nop comand.
I install and re-install drivers several times (qualcom).
I follow many guides, but most are to enter in edl mode, and then they can flash with no problems.
Here is a screenshot of the device manager:
The mi flash tool stuck few seconds in this, "ping target via firehose" before it ends in error:
Conclusion and what I think is the problemI think there is a soft problem with the emmc and the prog_emmc_firehose_8976_ddr.mbn, that does not let communicate the cellphone and the mi flash tool properly.
Other can be that the emmc went only read.
If is that the problem, is there any soft solution??
I would apreciate any help.
---------------------------------------------------------------------------------------------------------------------------------------------------------------
If you got here, thank you very much and sorry for my basic english.
Hi all,
So I'm with EE in the UK, which is the only network to refuse to update the Mate 20 Pro until at least April. I tried to update using this method here which has had some success on the EE forums: https://forum.xda-developers.com/mate-20-pro/how-to/android-emui-10-lya-l29-c432-dload-t4015241
I formatted my USB, plugged it in my the adapter, and it verified and installed the files in the dload folder:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
However, upon loading now I get stuck at the "Your device is booting" with the option of either powering off, holding power down to enter eRecovery etc. I tried to restore via eRecovery but get a failed error after connecting to any WiFi. I tried to connect to HiSuite but it says the device is not supported.
Fastboot says "PHONE locked, FRP Unlock" so I don't know if I can do anything to restore it.
My best idea is to be able to reflash an original EE image via the USB method again - does anyone know how I can do this? Or is the device permanently bricked?
Thanks
Matt
EDIT: I should point out the error has occurred because I flashed LYA-L29 instead of the LYA-L09 that I am on...
I can connect via ADB/fastboot if that helps...
MattKneale said:
I can connect via ADB/fastboot if that helps...
Click to expand...
Click to collapse
Put the files in the adb/fastboot folder, enable "usb dubugging, open cmd as admin and navigate to the adb folder then type "adb reboot bootloader" then "fastboot flashing unlock" then on your phone press "unlock the bootloader" then after quickly setting up the phone go straight to settings and enable developer mode and usb debugging again then on the pc type "adb reboot bootloader" and finally type "flash-all" wait patiently for the flashing to end.
Good luck !
Good day. The phone LG G3 VS985WK worked, but the Internet distribution via the SIM card of another operator was not available. I used a program SALT FWUL loaded from a USB flash (Live USB) drive to remove AntiRollBack. Through the inoperability of the Internet distribution, I also deleted the system partitions using the program SALT FWUL loaded from a USB flash (Live USB). After that, the program SALT FWUL does not detect the device, recovery does not start and no Download Mode. Moved the phone to Qualcomm HS-USB QDLoader 9008. When restoring the phone with the program BoardDiag (AP Check), an error appears "No response from the device. Check PMIC first and if stiil boot problem, replace AP". If you choose settings AP Check+EMMC Test or PMIC ON, then "Device was not found in dload trying flash programmer". Settings B2 (MSM8974AC) or G2 (MSM8974) and versions BoardDiag 2.99a or BoardDiag 3.99c do not affect, the error is the same.The program https://www.androidbrick.com/unbrick-recover-your-dead-lg-g3-g2-all-variants/ restores the phone, but only one port LGE AndroidNet USB Serial Port and one modem LGE AndroidNet USB Modem appears. I use Windows 7 SP1 Ultimate x64. Please help me recover the phone. I understand Russian and English.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Buy a new phone m8. VS985 are cheap.
Hello,
I hope someone can offer an idea of how to solve issue I'm facing atm.
I have FZ-X1 phone and it's came simlocked from Japan.
I want to run "fastboot oem clearsimlock 0".
I'm trying to communicate to it using fastboot but the problem I have is that once I boot the phone into its stock bootloader, my PC cannot see connected phone in Device Manager:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Once phone is fully booted into UI, I can see it recognised running command "adb devices":
I tried both latest Google and original Panasonic ADB drivers available for download. I use Windows 7 x32 version - it shouldn't have issue with drivers signature, right?
Have no clue how to overcome this obstacle. Any ideas or suggestions are very appreciated.
Thanks!
Remove the Google USB driver and the Panasonic ADB driver: All you have to do is to install the proper OEM USB driver suitable for your device:
Download Qualcomm HS-USB QDloader 9008 driver for Windows - 32-bit / 64-bit
You can now download Qualcomm QDLoader HS-USB Driver of 32-bit & 64-bit Installer. We have put up the entire installation process for you.
www.getdroidtips.com
Thank you for your reply! I tried that - unfortunately the phone still not detected by Windows 7 once connected to PC.
Hello!
I got my mom's phone because it got stuck on the boot screen (honor Powered by android). She was out in the cold for a while, and when she tried to use her smartphone, it had shut down. As she tried to restart it, it got stuck on the boot screen. So she gave it to me hoping to at least get some important data back. I fixed some bricked phones in the past, but this one seems impossible to fix.
I got fastboot working, but the recovery doesn't seem to start no matter how I press PWR and Vol+. Also fastboot reboot recovery gets me no further than a reboot to the boot screen. Since the FRP is locked, I can't flash a recovery image.
The fastboot screen suggest to open HiSuite. But on my Mac it does require HDB to be active. However the windows version aknowledges that a device can do something via fastboot.
But my win10 machine is unable to properly recognize the usb device. Installing USB drivers seems not to help, even manual install in the device manager fails with driver signature disabled. Also a registry fix from this website seems not to help. In the end, I can't get fastboot to work in the commandline nor HiSuite.
At this point I'm out of Ideas. As it stands now, the only way to recover the data is by unsoldering the eMMC .
There are ways to unlock the bootloader, but as far as I know, it requires wiping the storage.
I'm not sure what happened to the phone outside, but it's really strange that there is no recovery available.
Does anyone have ideas on how to proceed?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}