Database Users

LG G2 Hard Bricked

So I wiped the system partition on my LG G2/D800 (mostly out of stupidity) and now I'm stuck in the boot loop.
Symptoms are following:
1. Stuck in the boot loop
2. Will not go into download or recovery mode
3. When turning on the LG logo appears and disappears repeatedly
4. Device is not detected when plugged into the USB
5. Factory reset using VolDown+Power doesn't do anything
I've tried most of the ideas I've been able to find on the forum, but it looks like I'm stuck mostly because I cannot enter download mode and the phone is not detected in any way when plugged into the USB (no many partitions or anything).
Will be grateful for any ideas how to get out of it?

meseer said:
So I wiped the system partition on my LG G2/D800 (mostly out of stupidity) and now I'm stuck in the boot loop.
Symptoms are following:
1. Stuck in the boot loop
2. Will not go into download or recovery mode
3. When turning on the LG logo appears and disappears repeatedly
4. Device is not detected when plugged into the USB
5. Factory reset using VolDown+Power doesn't do anything
I've tried most of the ideas I've been able to find on the forum, but it looks like I'm stuck mostly because I cannot enter download mode and the phone is not detected in any way when plugged into the USB (no many partitions or anything).
Will be grateful for any ideas how to get out of it?
Click to expand...
Click to collapse
so vol up and then plug usb, does not take you to download mode?
if not try using srk tools.. if that doesnt work i think you need to short circuit your motherboard.
http://forum.xda-developers.com/lg-g2/general/lg-g2-unbrickable-fix-real-hard-brick-t2904404
and to go back to stock d800 variant..you said you have..
http://forum.xda-developers.com/showpost.php?p=65643825&postcount=4

raptorddd said:
so vol up and then plug usb, does not take you to download mode?
if not try using srk tools.. if that doesnt work i think you need to short circuit your motherboard.
http://forum.xda-developers.com/lg-g2/general/lg-g2-unbrickable-fix-real-hard-brick-t2904404
and to go back to stock d800 variant..you said you have..
http://forum.xda-developers.com/showpost.php?p=65643825&postcount=4
Click to expand...
Click to collapse
Indeed I cannot enter download mode with vol up then plug usb.
Good news is that I was able to enter qhsusb mode by short circuiting the moterboard. I used srktools to unbrick in qhsusb mode, however it didn't work. The linked guide recommends to flash only laf.img, aboot.img and boot.img. I don't really understand how flashing more can hurt. I also don't completely understand why flashing these should help. After all, I messed only with the system partition. I'll try to follow the guide more closely, but I'm thinking that a better idea would be to flash system partition in a qhsusb mode. I just need to figure out where to get system.img from.

meseer said:
Indeed I cannot enter download mode with vol up then plug usb.
Good news is that I was able to enter qhsusb mode by short circuiting the moterboard. I used srktools to unbrick in qhsusb mode, however it didn't work. The linked guide recommends to flash only laf.img, aboot.img and boot.img. I don't really understand how flashing more can hurt. I also don't completely understand why flashing these should help. After all, I messed only with the system partition. I'll try to follow the guide more closely, but I'm thinking that a better idea would be to flash system partition in a qhsusb mode. I just need to figure out where to get system.img from.
Click to expand...
Click to collapse
So now I can consistently get into ghsusb mode by short curcuiting the motherboard, and I can flash img files with dd. I flashed every partition from the stock FW which was on my phone. Now when hold vol up and plug in usb, I'm ending up in a stock recovery. However, I still cannot enter download mode and the phone still suffers from boot loop if I choose to reboot the phone.

meseer said:
Indeed I cannot enter download mode with vol up then plug usb.
Good news is that I was able to enter qhsusb mode by short circuiting the moterboard. I used srktools to unbrick in qhsusb mode, however it didn't work. The linked guide recommends to flash only laf.img, aboot.img and boot.img. I don't really understand how flashing more can hurt. I also don't completely understand why flashing these should help. After all, I messed only with the system partition. I'll try to follow the guide more closely, but I'm thinking that a better idea would be to flash system partition in a qhsusb mode. I just need to figure out where to get system.img from.
Click to expand...
Click to collapse
am not so sure about laf and rest of stuff.
i know tha once i had the qhusb mode all i had to do is enter download and flash TOT using flash tools.

lg g2 vs980 wont turn on or charge or regconized by pc
i have a probleme with my lg g2 vs980 . when i try to install tho cyanogenmod rom . at firt i intall it and it shows that no sim card. i tried to reintall it again so i have install again the the custom recovery and when i tryien to press the volum downd and power but the phone turned of and evrything is black . i tried to turn it on or charge it but but it didn't . i tried to connect it to pc it didn't get regconized. when i turn it on the phone vibrate but not turned on .plz help me

Bourakhma said:
i have a probleme with my lg g2 vs980 . when i try to install tho cyanogenmod rom . at firt i intall it and it shows that no sim card. i tried to reintall it again so i have install again the the custom recovery and when i tryien to press the volum downd and power but the phone turned of and evrything is black . i tried to turn it on or charge it but but it didn't . i tried to connect it to pc it didn't get regconized. when i turn it on the phone vibrate but not turned on .plz help me
Click to expand...
Click to collapse
go back to stock
you can try the srk tools 2.1 and see if you can get nuke download.
or read here
http://forum.xda-developers.com/lg-g2/general/lg-g2-unbrickable-fix-real-hard-brick-t2904404

Brick Jiayu S3 MTK 6752 ( TWRP Recovery flash failed )

Hello XDA fourm.
i have Jiayu S3 and i tried to flash a TWRP recovery into the phone .
i download flashiy from app store and download TWRP recovery and hitted the flash button .
after i click reboot the phone stuck on boot loop and cant go into recovery mode, which it did before i tried to flash TWRP recovery .
PC doesn't Reconsize the phone, and cant do anything with it .
Please help

edenb2 said:
Hello XDA fourm.
i have Jiayu S3 and i tried to flash a TWRP recovery into the phone .
i download flashiy from app store and download TWRP recovery and hitted the flash button .
after i click reboot the phone stuck on boot loop and cant go into recovery mode, which it did before i tried to flash TWRP recovery .
PC doesn't Reconsize the phone, and cant do anything with it .
Please help
Click to expand...
Click to collapse
what you mean pc doesnt recognize? you mean mtp?
have you tried spflash tool on pc? phone should be detected on spflash tool , be sure to install mtk drivers.

Do you think your USB port on phone worked before this? If it was dead, change the little daughter board with the USB port.
If it worked: Get a flashable TWRP version for spflash tool, go to spflash tool, check only "recovery," click download, then plug in the USB wire to the phone. You can try holding up arrow or down arrow whilst plugging in the USB port to the phone. This Mediatek phone is awesome because it is really unbrickable. I had to be WAY more careful in following directions with my old HTC phones. I've had flashes fail on the Jiayu and it's always able to be recovered.

Stuck in a boot loop and can't access recovery mode

So I flashed a custom rom and it required a specific TWRP recovery. But after installing the custom rom I had to install another TWRP recovery otherwise it wouldn't boot into OS (this recovery was probably unsupported and thus my phone was forced to boot into OS)
So every time I wanted to boot into recovery mode I had to use an app like flashify and flash the first recovery to boot into recovery mode. And after finishing I had to flash the "unsupported" recovery again in order to boot into OS.
Now with the "unsupported" recovery, I installed Xposed and some modules and then restarted the device. And..........boom! The phone is stuck in a boot loop! And I can't even boot into recovery mode.
Now here's the other nightmares I'm getting:
1. Cant use ADB to flash a new recovery because my device is "unauthorized" and in order to fix that I need to go to developers option which is not possible (because of boot loop)
2. Uninstall Xposed: button combinations aren't working and I cant go to recovery mode to flash the uninstaller zip
3. vol up + vol down + power button doesn't open recovery because the recovery is "unsupported"
4. Can't even boot to fastboot mode by holding vol down + power. It tries to boot into OS and starts boot looping
5. Can't use sp flash tool to flash stock rom or recovery because whenever I connect the phone to PC, the phone tries to boot into OS and....you guessed it starts boot looping.
Now I'm out of ideas and really depressed. If anyone can help me out with this I'll be grateful forever.
My device is: Lenovo k4 note
Chipset: MediaTek MT6753
Currently on this recovery: https://androidfilehost.com/?fid=673368273298981920
Got this recovery from here (recovery2): https://forum.xda-developers.com/k4-note/development/unofficial-resurrection-remix-5-8-2-t3570195
Thanks!

Update: The problem is solved after flashing stock rom via sp flash tool

Can you please help me im havifng the same problem
scarecow47 said:
Update: The problem is solved after flashing stock rom via sp flash tool
Click to expand...
Click to collapse
I think the pc cant dtect my device same problem bro after installing new rom it keeps on rebooting after the lenovo logo. Cant also access the recovery mode. Please help me

Bro I'm not an expert. Someone from XDA discord server helped me with this. And I actually forgot the exact thing I did to be honest. I downloaded the sp flash tool on pc and downloaded the stock rom. Then flashed it to the phone. You have to connect your device via USB before. For a detailed guide you can search on YouTube with something like "how to flash stock rom via sp flash tool"
Or ask in the discord server. They will surely help you.

How did you flash that? Can you please explain step by step

Check this link: https://firmwarefile.com/lenovo-k4-note-a7010a48
You can download the stock rom from here. And there is also a tutorial on how to flash it. I followed it. Hope that helps!

scarecow47 said:
Check this link: https://firmwarefile.com/lenovo-k4-note-a7010a48
You can download the stock rom from here. And there is also a tutorial on how to flash it. I followed it. Hope that helps!
Click to expand...
Click to collapse
Thanks, the problem is my phone is struck on the Lenovo logo, it's not turning off but my computer deducted it as Lenovo device

If ADB can detect your device then you can just flash a new recovery and you should be fine. But as I said I'm not an expert so I'd suggest you to ask for help on the XDA discord server. That's where I got help from.

Did anyone found the solution?
Thanks

Can any one find the solution of that problem , because my lenovo k4 note also stuck on boot looping logo... and vibrate like bootup time

MiFlash - 'cannot receive hello packet' in EDL Mode. No Fasboot

Hi all,
what happens until here?
A week ago i have bricked my Axon 7 (2017G). Complete dead, only red LED flashing. Search the Forum and found the instructions to disassemble the phone, shorten the Service Point and set the device into edl mode. Great, Works. Flashing the full EDL Rom via MiFlash and phone boots into Android. But then i was realizing that i have flashed the wrong linked Rom. ZTE_A2017V2.0.0B13. At this time i was not Aware that i Need 2017G Rom. Phone works, but wrong Rom.
When i tried to flash anew rom i get from miflash the message 'cannot receive hello packet. try to reset...'
I'm using Win10, several USB Ports and several MiFlash versions. When i Press Power + Vol Down i get into FTM Mode. When i press Power + Vol Up i come into 'Revoery Mode?'. Ist in Chinese.
Message from Fastboot:
'Your device Software cant be checked for corruption. Please lock the bootloader'.
What can id do, any Idea?
Regards

nukem007 said:
Hi all,
what happens until here?
A week ago i have bricked my Axon 7 (2017G). Complete dead, only red LED flashing. Search the Forum and found the instructions to disassemble the phone, shorten the Service Point and set the device into edl mode. Great, Works. Flashing the full EDL Rom via MiFlash and phone boots into Android. But then i was realizing that i have flashed the wrong linked Rom. ZTE_A2017V2.0.0B13. At this time i was not Aware that i Need 2017G Rom. Phone works, but wrong Rom.
When i tried to flash anew rom i get from miflash the message 'cannot receive hello packet. try to reset...'
I'm using Win10, several USB Ports and several MiFlash versions. When i Press Power + Vol Down i get into FTM Mode. When i press Power + Vol Up i come into 'Revoery Mode?'. Ist in Chinese.
Message from Fastboot:
'Your device Software cant be checked for corruption. Please lock the bootloader'.
What can id do, any Idea?
Regards
Click to expand...
Click to collapse
disassemble again, force EDL and flash the corresponding rom

bornlivedie said:
disassemble again, force EDL and flash the corresponding rom
Click to expand...
Click to collapse
Already done, same Story. I've disassemble again and tryed like the first time. But MiFlash says no hello package. Laptop was meanwhile rebooted to ensure that no Background processes are blocking MiFlash.
I can also force EDL Mode by 'adb reboot edl'. The Axon is then shown as 'Qualcomm HS-USB QD Loader 9008)' in the device manager. Or is there a difference?

nukem007 said:
Already done, same Story. I've disassemble again and tryed like the first time. But MiFlash says no hello package. Laptop was meanwhile rebooted to ensure that no Background processes are blocking MiFlash
Click to expand...
Click to collapse
In Windows 10, does the device manager detect the phone as Qualcomm 9008 inside the ports section? It is the way Windows detects a phone in EDL mode. You may have also some driver issue in Windows. If it is detected as BULK then you only need to install the latest Qualcomm drivers. You can find the details in this guide.

nukem007 said:
Already done, same Story. I've disassemble again and tryed like the first time. But MiFlash says no hello package. Laptop was meanwhile rebooted to ensure that no Background processes are blocking MiFlash.
I can also force EDL Mode by 'adb reboot edl'. The Axon is then shown as 'Qualcomm HS-USB QD Loader 9008)' in the device manager. Or is there a difference?
Click to expand...
Click to collapse
I had the no hello package message in Win10 with a A2017U, for me the solution was to setup to run MiFlash in Administrator mode (look for the check box under the compatibility tab), and then replugin the USB cable and restart EDL fresh.
There seem to be all kinds of cases of this occurring for various phones on the internet with various solutions, but this one worked for me this time.
It seems to be a YMMV thing.
BTW if you have an unlocked bootloader flashing the Recovery with the suitable version of Nfound's TWRP Exclusive allows a choice of rebooting into EDL(9800).
This makes getting back into EDL relatively convenient.

nukem007 said:
Hi all,
what happens until here?
A week ago i have bricked my Axon 7 (2017G). Complete dead, only red LED flashing. Search the Forum and found the instructions to disassemble the phone, shorten the Service Point and set the device into edl mode. Great, Works. Flashing the full EDL Rom via MiFlash and phone boots into Android. But then i was realizing that i have flashed the wrong linked Rom. ZTE_A2017V2.0.0B13. At this time i was not Aware that i Need 2017G Rom. Phone works, but wrong Rom.
When i tried to flash anew rom i get from miflash the message 'cannot receive hello packet. try to reset...'
I'm using Win10, several USB Ports and several MiFlash versions. When i Press Power + Vol Down i get into FTM Mode. When i press Power + Vol Up i come into 'Revoery Mode?'. Ist in Chinese.
Message from Fastboot:
'Your device Software cant be checked for corruption. Please lock the bootloader'.
What can id do, any Idea?
Regards
Click to expand...
Click to collapse
I have now used the Axon7Toolkit with Option 11 (Restore to stock) and after this flashed the 2017G with MiFlash. And it works. Don't know why.
But the Topic with the Bootloader is still open. So I'm not able to root and istall TWRP:
Message from Fastboot:
'Your device Software cant be checked for corruption. Please lock the bootloader'.

nukem007 said:
Already done, same Story. I've disassemble again and tryed like the first time. But MiFlash says no hello package. Laptop was meanwhile rebooted to ensure that no Background processes are blocking MiFlash.
I can also force EDL Mode by 'adb reboot edl'. The Axon is then shown as 'Qualcomm HS-USB QD Loader 9008)' in the device manager. Or is there a difference?
Click to expand...
Click to collapse
that's a bad connection, you must have let go of the contact too son
make sure it gets detected in your pc, hold it a couple of seconds more and then let go

Use the ADB command "adb reboot edl" instead as its the most sure fire way to ensure you are actually in EDL mode. The button combination method sometimes doesn't work as I've experienced this myself on more than one occasion.

I have the same issue. I cant flash using MiFlash. My phone stuck on black screen and no LED flash. This is what i tried to do:
1: I unlocked bootloader using MiFlash and fastboot.
2: Installed TWRP recovery.
3: Tried to install custom ROM and it installed but phone was not booting to system and it always went to fastboot mod.
4: Then i again lock the boatloader using fastboot oem lock.
5: Just after that the phone went to black screen and no LED and adb devices dont show phone listed and fastboot not working.
6: Tried Vol up and power for a minute but no LED and no logo just black screen. Tried Vol down and power plus vol up/down and power for a minute but nothing.
7: If i connect phone with PC its appearing in Device Manager as Qualcom HS-USB QDLoader 9008 (COM10)
8: adb and fastboot dont detect it. MiFlash detets but not flashing and gives No hello packet received error.
Anybody can help? Should i try flashing stock rom using MyFlash if it works for some reason? Other files are not flashing like recovery or unlock etc.

> 4: Then i again lock the boatloader using fastboot oem lock.
This is the fatal step that bricked your phone in EDL mode. Reason: To relock bootloader, your phone must be full stock first:
stock ROM, stock recovery. But you was with TWRP = custom recovery!
Fortunately, the Axon 7 is "unbrickable". And your phone is still in EDL mode, this is not the worst brick status (DFU mode).
Note: if ever your were in DFU mode, there is still DFU tool to unbrick your phone (search appropriate topic in forum).
To unbrick in EDL mode, try to EDL flash entire stock ROM corresponding to your model (A2017, A217U or A2017G), Nougat recommanded (not Oreo: not supported by many tools; not Marshmallow: too old).
Recommended tool to flash:
Axon 7 EDL tool (it has link to full stock ROM for different models)
https://forum.xda-developers.com/axon-7/development/axon-7-edl-tool-flash-backup-restore-t3750759
Note: I never get "No hello packet received error" when using Axon 7 EDL tool. Miflash is not necessary nor recommended for me (overkill, various versions).
Some advices:
- always launch Windows Device manager and monitor it to check phone connection status (COM HD-USB QDLoader 9008, or DFU, or Android device).
- try using latest stable Qualcomm HD-USB QDLoader Driver, if possible signed version. E.g. version 2.1.1.2.
- of course charge the phone fully if possible before flashing.
- check and use good USB connection cable.
- you may need to set Windows in "test mode" first (disable driver signing) to avoid "No hello packet received error"
https://answers.microsoft.com/en-us...est-mode/27b555ca-852a-44c7-b42f-c84b8eec06f2

I have a really similar issue. After updating to Oreo ROM B03, I tried to enter EDL to flash twrp (but I didn't get to this).
I couldn't boot to bootloader using the recovery options (the system was just normally starting). I tried with vol+, vol- and power at one time. After the red led blinks I released all buttons. I guess I got to EDL, but I can't quit it now.
The QDLoader 9008 (driver version is exactly 2.1.1.2) is visible COM4, but I can't do nothing with it. Same error with Miflash, Axon 7 EDL tool stopped on "Loading the programmer". I tried all combinations vol+, vol-, power to boot to the system again, but without luck. Black screen and no reaction.
After night, when I hold power the red led blinks and that's all. When I connect cable to laptop the red led starts blinking, no QDLoader 9008 visible now.
Anyone has an idea what to can I do?

I have the same issue. I cant flash using MiFlash. My phone stuck on black screen and no LED flash. This is what i tried to do:
1: I unlocked bootloader using MiFlash and fastboot.
2: Installed TWRP recovery.
3: Tried to install custom ROM and it installed but phone was not booting to system and it always went to fastboot mod.
4: Then i again lock the boatloader using fastboot oem lock.
5: Just after that the phone went to black screen and no LED and adb devices dont show phone listed and fastboot not working.
6: Tried Vol up and power for a minute but no LED and no logo just black screen. Tried Vol down and power plus vol up/down and power for a minute but nothing.
7: If i connect phone with PC its appearing in Device Manager as Qualcom HS-USB QDLoader 9008 (COM10)
8: adb and fastboot dont detect it. MiFlash detets but not flashing and gives No hello packet received error.
Anybody can help? Should i try flashing stock rom using MyFlash if it works for some reason? Other files are not flashing like recovery or unlock etc.
Click to expand...
Click to collapse
Hi,
same issue here. Using the Axon7_EDL_Tool doesn't work for me: While flashing A2017G_B03_OREO_FULL_EDL via "Flash FULL EDL" it stops with the output: Loading the programmer: prog_ufs_firehose_8996_ddr.elf
Does someone know the solution?

same thing happening today, anyone found the solution yet?

A2017G Bricked Oreo

Can't seem to get any interaction with the buttons, but it is seen in windows as Qualcome HS-USB QDLoader 9008 (COM3).
How i got here.
used a update.zip to go to oreo b3
using the EDL tool i backed up the OREO (A2017B03) recovery
using the EDL tool i flashed oki's trwp and rebooted
nothing...
Tried flashing EDL packages with the EDL tool and MIFlash.
> EDL tool hangs on `loading the programmer`
> MiFlash "cannot retrieve hello packet" , "try to reset status" ,"write time out maybe device was disconnected"
Tried other USB2 and USB3 slots
Tried other USBC cables
prediction, it seems i have broken EDL mode as the device is in the state but does not do anything after that.
device does not boot or reboot into edl. stuck in this state

dalebaxter01 said:
Can't seem to get any interaction with the buttons, but it is seen in windows as Qualcome HS-USB QDLoader 9008 (COM3).
How i got here.
used a update.zip to go to oreo b3
using the EDL tool i backed up the OREO (A2017B03) recovery
using the EDL tool i flashed oki's trwp and rebooted
nothing...
Tried flashing EDL packages with the EDL tool and MIFlash.
> EDL tool hangs on `loading the programmer`
> MiFlash "cannot retrieve hello packet" , "try to reset status" ,"write time out maybe device was disconnected"
Tried other USB2 and USB3 slots
Tried other USBC cables
prediction, it seems i have broken EDL mode as the device is in the state but does not do anything after that.
device does not boot or reboot into edl. stuck in this state
Click to expand...
Click to collapse
Why do you backup the recovery? its already included in the zip file,just grab it.And OKIs twrp does not support stock oreo.
If you can boot in twrp,do it and flash a twrp for oreo from nfound and wipe everything

Predatorhaze said:
Why do you backup the recovery? its already included in the zip file,just grab it.And OKIs twrp does not support stock oreo.
If you can boot in twrp,do it and flash a twrp for oreo from nfound and wipe everything
Click to expand...
Click to collapse
i backed up the stock recovery just incase i was going to go back to it, but seeing what has happened it seems like even tho i flashed a custom recovery and didn't boot into it i am just plain stuck in a EDL state. i can't boot into recovery or fastboot as i'm seemingly stuck in EDL

dalebaxter01 said:
i backed up the stock recovery just incase i was going to go back to it, but seeing what has happened it seems like even tho i flashed a custom recovery and didn't boot into it i am just plain stuck in a EDL state. i can't boot into recovery or fastboot as i'm seemingly stuck in EDL
Click to expand...
Click to collapse
i was stuck in edl sometime ago too because i was flashing edl firmware and my laptop shutdown because empty battery.Can you enter FTM mode? hold vol down + power button.
If yes do it.Now close axon7toolkit EDL TOOL.After that open axon7toolkit and follow instructions.It will boot in edl again and try to flash firmware

Predatorhaze said:
i was stuck in edl sometime ago too because i was flashing edl firmware and my laptop shutdown because empty battery.Can you enter FTM mode? hold vol down + power button.
If yes do it.Now close axon7toolkit EDL TOOL.After that open axon7toolkit and follow instructions.It will boot in edl again and try to flash firmware
Click to expand...
Click to collapse
holding for 2 min unplugged and another 2 min plugged and nothing

FIXED
- Waited for battery to drop to 0% and the EDL loop was ended
- plugged into PC and used the buttom combo
- EDL'd ZTE Oreo Rom

dalebaxter01 said:
FIXED
- Waited for battery to drop to 0% and the EDL loop was ended
- plugged into PC and used the buttom combo
- EDL'd ZTE Oreo Rom
Click to expand...
Click to collapse
Refreshing subject because same **** happened to me
My question is how long did you wait to empty the battery? I was about 57% when phone stucked in EDL... does it drains battery when being dead-like?

yarecco said:
Refreshing subject because same **** happened to me
My question is how long did you wait to empty the battery? I was about 57% when phone stucked in EDL... does it drains battery when being dead-like?
Click to expand...
Click to collapse
I don't have my Axon 7 on me, but I would give it about a day or 2 for it to die out on its own because its standby time can be insane if you have a custom kernel.