Hi, I just bought an LG G2 D802 20B Model a couple days ago, yesterday I wanted to downgrade to 4.2.2 and I ended up bricking the phone.
The phone is non rooted, doesn't have any custom recovery, and not recognized by adb even though i installed all the drivers ( koush drivers, PdaNet, Lg drivers ...)
At first I flashed with .kdz file and it ended in bootloop, I tried to factory reset but it doesnt have any effects with the stock recovery it only shows the green android bot and blue progress bar and then restart in 3 seconds and reboots to lg logo and start looping.. After a restart the download mode didn't work anymore it showed me fastboot error, I searched for the tutorial that actually worked and I flashed with .tot method but there is still bootloop and the download mode is stuck at the image attached. The phone is not recognized by neither windows or ubuntu therefore I can't use adb to fix the partitions.
Can any body provide me with a solution? The phone is still new and it will be a shame if its transformed to a brick in 3 days :crying:
Hey..hmm i think thats how download mode it is...so did you tried to flash again a firmware?
raulx222 said:
Hey..hmm i think thats how download mode it is...so did you tried to flash again a firmware?
Click to expand...
Click to collapse
Actually the picture attached is stuck and it doesnt change , and the pc can't recognize the phone so I cant flash it with another firmware
BUMP! please help!!
This isn't download mode.
here
only aboot, boot, laf..
bender_007 said:
This isn't download mode.
here
only aboot, boot, laf..
Click to expand...
Click to collapse
Thanks for your reply, however the phone is not recognized on windows neither on ubuntu therefore this tutorial can't help ...
I am in the exact same situation.
Mine is a D802 32GB Hong Kong model. I stupidly ran AutoRec which soft-bricked my phone. Managed to get Download Mode working, then flashed 20C and 20B which bootlooped. Then I attempted to flash 10B, which got me into this exact state:
Download Mode not working (only shows "Download Mode", does not go to firmware recovery screen, not detected in Win/Linux)
Factory reset (Power + Vol Down) can go to factory reset screen, after factory reset, still bootloop.
Once in a while, I also get the Android icon which then disappears after a few seconds and goes to LG logo again.
If I plug the phone in and do a factory reset, Windows detects the LGE AndroidNet modem, and Linux will detect cdc_acm USB Abstract Control Model driver. Flash Tool and LG Mobile Support seems to detect the phone and attempt to flash, but the phone restarts after a short while.
I have no idea what else to do
Hi,
I tried to install Grola Rom on my phone and unfortunately I think that I may have flashed the ROM for the D802 (I tried to find a faster DL than the FShare link).
My phone is now stuck in Fastboot Mode. I've tried every method to try to get my phone back into regular working condition, but my laptop does not recognize my phone. No matter which driver I install, it shows up as Android in device manager and ADB devices and Fastboot devices shows up nothing.
I was able to get it to boot into download mode for about two seconds before it boots itself back into download mode immediately.
I've tried accessing recovery and download mode, but nothing works.
How would I either get back to recovery or at the very least back to download mode so I can go back to stock?
Thanks,
mjoecarroll
Edit: When I boot up it just says Fastboot Started.
When I plug it in, it says:
--reset--
--portchange--
--reset--
--portchange--
Same problem did you fix it?
Hey guys, I have a VS980 that was wrongly flashed with the wrong variant of CloudyG2 3.3, causing it to boot to Fastboot mode only. I used guides available on these forums that said I needed to flash the laf.img partition back to the phone to get it out of Fastboot mode but it now went back to Fastboot mode with a greyish-black screen, it did not even show the LG logo. I know it went to Fastboot mode because running the the "fastboot devices" command returned the phone identity. I then used SRKtook 2.1 to fix the Recovery, and this led to the phone going into QHSUSB 9006 mode. I then used the same SRKtool 2.1 to fix the QHSUSB 9006 issue. The tool successfully completed the process and even prompted me to flash the stock firmware, which I did using LGFlashTool 1.8, and one of the available TOT files (V26A). The flashing process completed successfully with a PASS. The phone powered on okay but with the same greyish-black screen as from before. I know the flashing process completed successfully because the the phone charges okay, the touchscreen works (even with the greyish-black screen I can unlock the screen, I can press the Home, Recents, and Back virtual buttons), and calls made to the SIM card inside the phone will ring). The PC recognizes the phone in MTP mode with Device Manager reporting it as being an LGE MTP Android Device, sometimes as a LG VS980 4G. My issues are these:
- What is it with the greyish-black screen? Anything I can do to rectify it? By the way it is not an LCD issue because I have repeatedly swapped screens from my other LS980 to the VS980 and from the VS980 to the LS980. On the LS980 both LCDs work perfectly.
- I can't get into Recovery mode. All the normal Volume Down+Power combo does is power on the phone. What can I do?
- I can't get into Fastboot mode. What can I do?
I am in the process of downloading every VS980 stock firmware I can find (10B, 11A, 26A, 39A, 24A, 27A). I will flash each to the phone, hopefully there'll be one that will fix my phone.
Hello guys.
It's a Huawei Ascend Xt2. It had TWRP installed with bootloader unlocked.
Since I wanted to have stock rom with no root, so I erased eveything, relocked the bootroom and now the phone just shows Huawei logo when booting and then enters Recovery mode on it's own. If I press Vol - and Power enters Fastboot&rescue mode.
Both Mac and PC recognizes the device as MSM8937_32(with recovery mode) and Google(Fastboot&rescue mode).
Tried installing ADB drivers no luck (waiting for device), tried with huawei drivers no luck.
I have the stock rom downloaded. I'm not able to flash anything on this device.
Is it possible to install from MicroSD?
Windows detects the device as mentioned. I think maybe it's recognizing the device as a different device or wrong driver but not sure what else to do.
Thank you for your suggestions.
PD> In FASTBOOT&RESCUE MODE.... phone says:
PHONE Relocked
FRP Unlock.
Thanks
vinhidalgo said:
Hello guys.
It's a Huawei Ascend Xt2. It had TWRP installed with bootloader unlocked.
Since I wanted to have stock rom with no root, so I erased eveything, relocked the bootroom and now the phone just shows Huawei logo when booting and then enters Recovery mode on it's own. If I press Vol - and Power enters Fastboot&rescue mode.
Both Mac and PC recognizes the device as MSM8937_32(with recovery mode) and Google(Fastboot&rescue mode).
Tried installing ADB drivers no luck (waiting for device), tried with huawei drivers no luck.
I have the stock rom downloaded. I'm not able to flash anything on this device.
Is it possible to install from MicroSD?
Windows detects the device as mentioned. I think maybe it's recognizing the device as a different device or wrong driver but not sure what else to do.
Thank you for your suggestions.
PD> In FASTBOOT&RESCUE MODE.... phone says:
PHONE Relocked
FRP Unlock.
Thanks
Click to expand...
Click to collapse
download this > https://easy-firmware.com/home/browse/category/id/25781/
use 7zip to extract it on your pc until you get the dload folder that contains the update.app
copy dload to your ext_sdcard.
follow instructions found in the zip of check mine here > https://forum.xda-developers.com/showpost.php?p=76902495&postcount=86
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?