Can anybody help with my really 'bricked' LG-F800L? - LG V20 Questions & Answers

I modified aboot.img,then flash into my phone,now it no response wether press any key to startup.
Now,it's really bricked!can not into download、recovery、fastboot mode.
now I can into 9008 qdloader mode.

Related

Blackscreen / Qualcomm HS-USB QDLloader 9008

Hey guys,
finally i bricked my phone...
After a failed flash to TWRP recovery and a failed unbrick with fastboot, the phone won't start. Blackscreen. Only in device manager it show's "Qualcomm HS-USB QDLoader 9008". Is there any chance to unbrick or should i get a new mainboard?
PS: Sorry for my bad english, im from Germany
Thank you in advance
JaDa
@JaDaKiZz welcome to the party - read this http://www.reddit.com/r/lgg2/comments/2p5xei/the_lg_g2_is_unbrickable_a_story_of_death_and/ and let me know if you need any help. The MOST IMPORTANT thing you need to do is figure out the right KDZ for your phone.
Use http://csmg.lgmobile.com:9002/csmg/b2c/client/auth_model_check2.jsp?esn=xxxxxxxxxxxxxxx
replace xxxxxxxxxxxxxxx with your IMEI
Hey sandys,
the BoardDiag start but abort the test.
Linux don't show my G2 in devices. What can I do?
JaDa
Same thing happened to my phone. Thats what it shows in windows and isnt picked up by ubuntu. When I tried to use the lg tool to recovery it fails and says phone isnt in dload mode trying flash programmer. Dont have the money currently for @tungkick and dont see any other way.

New method to unstuck on EDL mode with Qualcomm HS-USB Diagnostics 900E

Well, today, I flash a wrong firmware on my RN3 pro RR 5.8.3, unlock unofficially and get brick. No fastboot, No recovery, long press power button only brought splash screen for a second then screen goes black again. When stick to PC only red led blinking, on Device manager show Qualcomm HS-USB Diagnostics 900E so no Miflash.
Okay after a whole morning, I found this method here http://en.miui.com/forum.php?mod=viewthread&tid=266598&highlight=900e.. I tried method 3 from that thread because the other are just unreadable. So here is the step:
1. Plug the phone to PC - Red led blinking
2. Hold both 3 button: Volume up, Volume Down, Power button for around 10s. Phone vibrate and show the Linux Penguin Icon (Qualcom mode)
3. Check in Device manager/Port , it show other (unfortunately not the 9008 as in the thread). I check with Miflash Phone is recognize but i Cant flash any thing
4. SO i tried using this method here (step 4 ) https://forum.xda-developers.com/showpost.php?p=69613342&postcount=3 and get into EDL mode with 9008 port. Voila!
Optional
5. Then I flash this TWRP and unlock officially from here https://forum.xda-developers.com/redmi-note-3/how-to/unlock-unofficially-install-zcx-twrp-t3586778 and the beast is up again ! :highfive:
So i post this here to help anyone stuck in EDL mode and dont have a DFC or dont want to use test point method.
hope this help .
Thanks for sharing.
I already have deep flash cable (btw I made it myself, it is easy) and I have used it some times... But it is good if u don't have the cable!!
Regards!
Thanks a lot for this small post, it saved me from throwing this phone out of the window.
I could update MIUI using fastboot EDL, weirdely enough you cannot update official MIUI without unlocking the bootloader... WTF xiaomi
Saved my ass man thank you i got a real headache from all the failed attempts but u did the job.
my Redmi 4 no response. wat I do now.
when I connect usb cable to phone to pc it's show direct edl mode or Qualcomm Snapdragon 9008 is connected in port .
so what happened it?
wat I do now pls help me.

Chinese Axon 7 is not seen in ADB or MiFlash..Bricked??

After installing twrp on my chinese axon 7 latest B16 I rebooted accidentally and now my phone gets stuck on the the ZTE logo.
I cant enter recovery as when I press volume up + power, it reboots a couple of times with the zte logo and nothing else.
Also when entering EDL mode the only thing my PC is showing in device manager is "Handset Diagnostic Interface(DFU) (COM6)". Before it was showing as "Qualcomm HS-USB QDLoader 9008" but no more, even after multiple reboots and installing the qualcomm drivers again.
Before when running "adb devices" in the CLI I would see my device but now nothing. and running adb reboot edl shows error: no devices/emulators found.
Also tried MiFlash but when I hit refresh I dont even see COM in the list, its just blank.
Does anyone have any suggestions?
as I tried the below guide but get stuck as my device is never picked up by ADB or MiFlash
https://forum.xda-developers.com/axon-7/development/edl-emergency-dl-mode-twrp-unlock-t3553514
cozzysa said:
After installing twrp on my chinese axon 7 latest B16 I rebooted accidentally and now my phone gets stuck on the the ZTE logo.
I cant enter recovery as when I press volume up + power, it reboots a couple of times with the zte logo and nothing else.
Also when entering EDL mode the only thing my PC is showing in device manager is "Handset Diagnostic Interface(DFU) (COM6)". Before it was showing as "Qualcomm HS-USB QDLoader 9008" but no more, even after multiple reboots and installing the qualcomm drivers again.
Before when running "adb devices" in the CLI I would see my device but now nothing. and running adb reboot edl shows error: no devices/emulators found.
Also tried MiFlash but when I hit refresh I dont even see COM in the list, its just blank.
Does anyone have any suggestions?
as I tried the below guide but get stuck as my device is never picked up by ADB or MiFlash
https://forum.xda-developers.com/axon-7/development/edl-emergency-dl-mode-twrp-unlock-t3553514
Click to expand...
Click to collapse
Yeah, DFU brick. You basically need to follow the 4th category brick repair guide. Good luck
Choose an username... said:
Yeah, DFU brick. You basically need to follow the 4th category brick repair guide. Good luck
Click to expand...
Click to collapse
wow damn..I found this guide: https://forum.xda-developers.com/axon-7/how-to/a2017-4th-category-brick-repair-manual-t3585898
But I see it involves me opening the device which I am trying to avoid as a last resort.
I just sent the seller from Ali-express to see if they will replace it.
Never actually told them that I was tinkering with it.
Fingers crossed on the reply, will update the thread once I receive a reply.
cozzysa said:
wow damn..I found this guide: https://forum.xda-developers.com/axon-7/how-to/a2017-4th-category-brick-repair-manual-t3585898
But I see it involves me opening the device which I am trying to avoid as a last resort.
I just sent the seller from Ali-express to see if they will replace it.
Never actually told them that I was tinkering with it.
Fingers crossed on the reply, will update the thread once I receive a reply.
Click to expand...
Click to collapse
well that's the other way lol
I had to follow the guide, and it fixed my phone, so be assured that you can fix it if they send it back
It seems I got really luck as putting my phone in Factory test mode made device manager finally show "Qualcomm HS-USB QDLoader 9008" which I was then led MiFlash in detecting it.
I was then able to flash Stock B13 and from there unlock the bootloader, flash twrp and root.
cozzysa said:
It seems I got really luck as putting my phone in Factory test mode made device manager finally show "Qualcomm HS-USB QDLoader 9008" which I was then led MiFlash in detecting it.
I was then able to flash Stock B13 and from there unlock the bootloader, flash twrp and root.
Click to expand...
Click to collapse
Usually you can't enter Factory Test Mode when on a DFU brick. The known procedure to do that is to discharge the phone, then put it into FTM somehow and then using ADB to get to EDL. It's really weird that you've been able to pull that off that way
Could you tell us how you got into FTM? Just by vol down and power? It would be a nice addition to the brick guide, before attempting to take the phone apart
Yeah, it was just by power + volume down.

XT1768 Hard Brick NEED HELP

I tried to install TWRP recovery and then flashing something without first doing a factory reset and now my phone won't turn on. I get nothing on the display when holding the power button or power + Vol. Down. Device Manager detects the phone only as "Qualcomm HS-USB QDLoader 9008".
I've read about flashing with EMMC but I get an error message that says "Open rawprogram.xml fail!". I don't know where to find a rawprogram.xml. I have the stock rom and have flashed it before myself through ADB fastboot commands but I don't know what to di in this situation. Please help!
skotseno said:
I tried to install TWRP recovery and then flashing something without first doing a factory reset and now my phone won't turn on. I get nothing on the display when holding the power button or power + Vol. Down. Device Manager detects the phone only as "Qualcomm HS-USB QDLoader 9008".
I've read about flashing with EMMC but I get an error message that says "Open rawprogram.xml fail!". I don't know where to find a rawprogram.xml. I have the stock rom and have flashed it before myself through ADB fastboot commands but I don't know what to di in this situation. Please help!
Click to expand...
Click to collapse
You bricked it. Many others have done the same thing to theirs by flashing the wrong firmware.
skotseno said:
I tried to install TWRP recovery and then flashing something without first doing a factory reset and now my phone won't turn on. I get nothing on the display when holding the power button or power + Vol. Down. Device Manager detects the phone only as "Qualcomm HS-USB QDLoader 9008".
I've read about flashing with EMMC but I get an error message that says "Open rawprogram.xml fail!". I don't know where to find a rawprogram.xml. I have the stock rom and have flashed it before myself through ADB fastboot commands but I don't know what to di in this situation. Please help!
Click to expand...
Click to collapse
I think you can just use a blankflash file. I even used the one for 1767 one on my 1768 when I bricked mine by accident (had the exact same symptoms as you, no bootloader, nothing). Got it form here: https://forum.kingfirmware.com/thread-4419.html

[SOLVED!] Hard Bricked 6T Help Pls

Hi internet,
I obviously need help. I accidently bricked my 6T again and it seems to be permenant. I tried to used the MSMdownloadtool but the tool can't detect the device. And the device is in a Qualcomm CrashDump Mode. It shows Attempted to kill init! exit code=0x0000000b do_exit. I got to go but is there a way to fix this.
You must post in Q/A not here
Tapatalké depuis mon OnePlus 6T Havoc OS avec FP !
What were u exactly trying to do while this happened ?
Extreme_Ninja2099 said:
Hi internet,
I obviously need help. I accidently bricked my 6T again and it seems to be permenant. I tried to used the MSMdownloadtool but the tool can't detect the device. And the device is in a Qualcomm CrashDump Mode. It shows Attempted to kill init! exit code=0x0000000b do_exit. I got to go but is there a way to fix this.
Click to expand...
Click to collapse
You can restore you device using fastboot rom. Search for oos 6t fastboot rom.. There are guides for installation.
P.S. It will give a whole bunch of error in the cmd during installation but don't interrupt the process as your device will be restored in the end
Use Mnm tool to fix your phone. It can fix hard brick devices and guidance is there how to use .
PS: this is not right place post next time post on Q/A section.
Hold all the buttons down till it shuts off, almost a full minute. Then get it to boot to fastboot, power off. Then start up msm, then while phone is unplugged and off, hold both vol buttons for a 4 count, then plug it in. Msm will day connected, hit start. Let it finish and reboot. that's all
Qualcomm crashdump is not the same as download mode, and will not work with MSM. You still need to put your device manually into download mode.
parker.stephens said:
Qualcomm crashdump is not the same as download mode, and will not work with MSM. You still need to put your device manually into download mode.
Click to expand...
Click to collapse
Hold down every button till it shuts off, then force reboot to bootloader, then select power off to make sure it's off. Then do as I instructed above to fix it. Sometimes u can just run a fastboot rom to fix it, or boot twrp and flash a rom. I do this multiple times a day sometimes.
fullofhell said:
Hold all the buttons down till it shuts off, almost a full minute. Then get it to boot to fastboot, power off. Then start up msm, then while phone is unplugged and off, hold both vol buttons for a 4 count, then plug it in. Msm will day connected, hit start. Let it finish and reboot. that's all
Click to expand...
Click to collapse
Thanks everyone who replied. The whole thing started when I tried to update my TWRP the wrong way and I got nothing better to do. I was on 3.2.3-1 and the newest on the website (TWRP) was 3.2.3-2, but I flashed the image instead, into vendor. This got me into the Qualcomm CrashDump Mode and it kept on rebooting to it as well. There was no way that I was be able to use the MSMDownload tool to recover my 6T as the tool couldn't detect my device as it was connected as Qualcomm HS-USB Diagnostics 900E not Qualcomm HS-USB QDloader 9008.
I pressed all the buttons and got into FASTBOOT mode! Then I booted TWRP, luckily all my stuff isn't corrupted and I did a Nandroid backup beforehand as well. So, I just restored my Nandroid backup and voila I got my 6T back. Thanks again everyone
Extreme_Ninja2099 said:
Thanks everyone who replied. The whole thing started when I tried to update my TWRP the wrong way and I got nothing better to do. I was on 3.2.3-1 and the newest on the website (TWRP) was 3.2.3-2, but I flashed the image instead, into vendor. This got me into the Qualcomm CrashDump Mode and it kept on rebooting to it as well. There was no way that I was be able to use the MSMDownload tool to recover my 6T as the tool couldn't detect my device as it was connected as Qualcomm HS-USB Diagnostics 900E not Qualcomm HS-USB QDloader 9008.
I pressed all the buttons and got into FASTBOOT mode! Then I booted TWRP, luckily all my stuff isn't corrupted and I did a Nandroid backup beforehand as well. So, I just restored my Nandroid backup and voila I got my 6T back. Thanks again everyone
Click to expand...
Click to collapse
Everybody, it's called the MSMDownload Tool. It cannot be used in Fastboot Mode or Qualcomm CrashDump Mode, it can only be used in EDL Mode (Emergency Download Mode).
I have onplus 6t international i reset my device now its stuck on fastboot mode locked i cant enable oem unlocked in devlopers because my 6t is stuck on fastboot what to do please help
CaptionNixx said:
I have onplus 6t international i reset my device now its stuck on fastboot mode locked i cant enable oem unlocked in devlopers because my 6t is stuck on fastboot what to do please help
Click to expand...
Click to collapse
Power off use msm. Done.
fullofhell said:
Power off use msm. Done.
Click to expand...
Click to collapse
I did that but its shows conected when i press start its work for 5s then its shows N/A in connection area
CaptionNixx said:
I did that but its shows conected when i press start its work for 5s then its shows N/A in connection area
Click to expand...
Click to collapse
If your using windows search for device manager to see what your device is being detected as. Try and reboot if your device isn't Qualcomm HS-USB QDloader 9008. Once it shows that try and update the driver, but you'll need to be a admin. Have you installed Oneplus USB Drivers?
Extreme_Ninja2099 said:
If your using windows search for device manager to see what your device is being detected as. Try and reboot if your device isn't Qualcomm HS-USB QDloader 9008. Once it shows that try and update the driver, but you'll need to be a admin. Have you installed Oneplus USB Drivers?
Click to expand...
Click to collapse
Yes i did that and driver is fully installed Qualcomm HS-USB QDloader 9008 and there is No yallow sigh in driver
Try closing the MSMDownload tool and opening it again. This happened to me when I used MSMDownload Tool and restarting made my device connected
Extreme_Ninja2099 said:
Try closing the MSMDownload tool and opening it again. This happened to me when I used MSMDownload Tool and restarting made my device connected
Click to expand...
Click to collapse
Thanks brother its done
Help I can not get in to fastboot mode. Im stuck in Crashdump mode. Even when i power off the phone holding powerbutton down for a while it will powerup again and the unlocked bootloader warning window with "press power key to pause boot" will not react to any presses.
Also booting and holding down power+down will result in the same and go to crashdump mode.
What do I do
Voldemort13 said:
Help I can not get in to fastboot mode. Im stuck in Crashdump mode. Even when i power off the phone holding powerbutton down for a while it will powerup again and the unlocked bootloader warning window with "press power key to pause boot" will not react to any presses.
Also booting and holding down power+down will result in the same and go to crashdump mode.
What do I do
Click to expand...
Click to collapse
did yoy got any solution

Categories

Resources