Develop Bugs

[GUIDE] [E980] Fix soft bricks. Flash back to stock using LGFLashTools

I realized there aren't any guides [in English] around here to help rooted folks that soft bricked their LG PRO to restore it back to factory settings. This should be useful if you got your phone stuck on the AT&T or the LG logo. Especially now that we don't have an unlocked bootloader or a recovery to reocver our soft brick.
Anyway, to start, a little disclaimer: I hold no responsibility if this method renders your phone completely useless, or burns and makes some nice fireworks. I'm simply writing this to document the process that worked for me. Use at your own discretion.
Dislcimaer 2: this method will wipe out your internal sdcard, apps data, everything! It'll restore the phone back to the way you got it from AT&T. Might even lose your cell unlock status (not verified). so keep these unlock codes handy just in case.
Note to linux users like myself: get your a** on windows or run it from a VM. VirtualBox with Win7 works fine.
Steps:
Download
1. LGFlashTools v1.5. Anything less won't work. Mirror: HERE
2. DLL file for LGE980
3. Drivers
4. The stock image file
Thanks to IOMonster for hosting these biga** files.
Install
1. Install the LG drivers downloaded above.
2. Install LGFlashTools v1.5 (but don't run it)
3. Extract the DLL and the TOT files from above and put them in a nice tidy directory
Drivers initialization
1. Put the phone into download mode. (Turn off device, keep pressing volume down while plugging in the micro usb cable. If this doesn't work, try holding both volume keys instead)
2. Let the phone initialize and install the drivers. Once done, in Device manager, you should see the LG phone listed under COM ports (something along these lines).
3. Find that LG entry in Device Manager, click on Properties, Advanced and then change the COM port to COM41 and close/save.
4. Unplug your phone! Important step.
LGFlashTools
To get this tool to work, you'll need to do a few tricks.
1. Set the computer's date to some time in July 2012 or before.
2. Disconnect the internet
3. Find a serial number or register key from somewhere on the web (a google search for lgflashtools serial will yield some results). Can't help you here and please don't share any keys in this thread or get us in trouble.
4. Execute the LGFlashTools. It should ask you for a key, put it in. Now you should see a dialog where you can load the DLL file and the TOT files that you extracted earlier. Put them both in here. Click ok
Flashing
5. There is a yellow arrow on the top left. Click on it to initialize the process. Once done, it should say "ready/finished" or whatever.
6. Put the phone in download mode again, and plug it into the USB port. LG FLash Tools should start flashing it automatically. When it's done, it'll automatically reboot into your stock AT&T rom and all of your data and internal sdcard files are gone.
Profit

Thanks again Mac !

MrNa5ty said:
Thanks again Mac !
Click to expand...
Click to collapse
sure thing I'm probably going to refer to it myself someday.

madmack said:
sure thing I'm probably going to refer to it myself someday.
Click to expand...
Click to collapse
Thanks .... great info!!!!!

Nice. Hopefully they sticky this.

Welp, just bricked the phone again but was able to flash the tot... very simple and quick lol ur the man mac

this worked perfectly fine for me. i 1st tried it on w8 but after plugging in the e980 and letting the drivers and such install, it did not show up under com in the device manager. in fact, there was no com section. it did show up under devices and printers and i tried and could not find a com setting there. i went ahead and tried to flash but since i could not change to the proper port, the flash tool never found my e980.
so instead i just did it all on a w7 box, the device was listed under com, and i went along with the flashing.
thank you.

Think this will fix the bricks that are happening when they try to mess around with the bootloader?
Sent from my LG-E980 using Tapatalk 4 Beta

jprosek said:
Think this will fix the bricks that are happening when they try to mess around with the bootloader?
Sent from my LG-E980 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Nope. Mess with the bootloader and you'll risk losing download mode.

nvm

This needs to be stickied!!!
Sent from my LG-E980 using xda app-developers app

My friend just bricked his and the wi9ed the system. I can get ir into download mode for him but thats it. I tried recovery mode but trying to do that or boot regularly it just shows lg the an android with the spinning symbol on it the lg again then lg 2 more times and just stays there. Can this be fixed with only download mode? Again I plugged it in and im not sure its being seen by the computer.

Make sure you have the drivers installed and use pc suite to get back the firmware

rob219 said:
My friend just bricked his and the wi9ed the system. I can get ir into download mode for him but thats it. I tried recovery mode but trying to do that or boot regularly it just shows lg the an android with the spinning symbol on it the lg again then lg 2 more times and just stays there. Can this be fixed with only download mode? Again I plugged it in and im not sure its being seen by the computer.
Click to expand...
Click to collapse
it doesn't hurt to try. I'll bet it will because I was left with something similar and this method got me back on stock.

smaybe said:
Make sure you have the drivers installed and use pc suite to get back the firmware
Click to expand...
Click to collapse
Pc suite? Do you mean lg flash tools? I downloaded it but it wants me to log in to use it. I havent found a log in for it yet.

Download lg pc suite it have lg flash tool in it
Then you search a little in menus for firmware urgence recovery something like that and if it don't work try update in the same menu
And if all of that didn't work I'll find you a link to flash a kdz

Deleted

I seem to have an issue with my E980, i cant get data my apn directory is empty and cant seem to add an apn it will just not save! anyone else have this issue or know what i can do? thanks!

Reboots to recovery only
Ok, I flashed the recovery in this post using the dd method http://forum.xda-developers.com/showpost.php?p=43460298&postcount=208
The value pack was trying to download on my phone and instead of cancel, I pressed install. Now the phone only boots into that recovery. I have everything from the op downloaded, but instead of download mode it only boots into the recovery, any ideas?
When it boots up, It says the following for a couple of seconds:
Code:
Secure booting error
Cause: Device Unlock, so boot success!!
Edit: Got it into download mode by holding down both volume keys and plugging into usb. Thanks!!

apascual89 said:
Ok, I flashed the recovery in this post using the dd method http://forum.xda-developers.com/showpost.php?p=43460298&postcount=208
The value pack was trying to download on my phone and instead of cancel, I pressed install. Now the phone only boots into that recovery. I have everything from the op downloaded, but instead of download mode it only boots into the recovery, any ideas?
When it boots up, It says the following for a couple of seconds:
Code:
Secure booting error
Cause: Device Unlock, so boot success!!
Edit: Got it into download mode by holding down both volume keys and plugging into usb. Thanks!!
Click to expand...
Click to collapse
I'm glad you got it resolved! I just edited the OP with this information.

Hard Bricked my device, can someone help?

I have been trying to get this thing upgraded to 5.0 for a day and half now, and i just flashed it for like the 10th time with lg flash tool to try to take it to stock. The rom i flashed that bricked the device I found in this thead: http://forum.xda-developers.com/show....php?t=2698267
All of a sudden it won't turn on, won't respond to adb or enter recovery with the volume down + power combo.
All i can see in device manager is qhsusb with an exclamation point. I struggled to update this and once i finally did, the device still isn't recognized by the computer in any lg programs like mobile support tool or flash tool or by adb and wont turn on what can/should i do at this point??

jazir said:
All of a sudden it won't turn on, won't respond to adb or enter recovery with the volume down + power combo.
Click to expand...
Click to collapse
So it won't enter download mode either? You didn't mention that one... If it does enter download mode you have several options, however based upon what you posted I'm guessing download mode is also not available?

muiriddin said:
So it won't enter download mode either? You didn't mention that one... If it does enter download mode you have several options, however based upon what you posted I'm guessing download mode is also not available?
Click to expand...
Click to collapse
I managed to find out that the phone is in something called bulk mode and even found a tool that gets lg phones out of bulk mode. The program located in this thread here: http://forum.xda-developers.com/lg-g2/general/fix-unbrick-lg-g2-stuck-qualcomm-hs-usb-t2933830.
It has my chipset in it(The APQ8064) and can connect with the phone. It passes the first two tests (AP, and EMMC) and fails the SDRAM test. If i can figure how to fix the last test and make it succeed, the tablet won't be bricked anymore. Any ideas?

jazir said:
I managed to find out that the phone is in something called bulk mode and even found a tool that gets lg phones out of bulk mode. The program located in this thread here: http://forum.xda-developers.com/lg-g2/general/fix-unbrick-lg-g2-stuck-qualcomm-hs-usb-t2933830.
It has my chipset in it(The APQ8064) and can connect with the phone. It passes the first two tests (AP, and EMMC) and fails the SDRAM test. If i can figure how to fix the last test and make it succeed, the tablet won't be bricked anymore. Any ideas?
Click to expand...
Click to collapse
Had a quick look at that bulk mode thing. It seems to refer to a TOT file.
That TOT file seems to be in this thread http://forum.xda-developers.com/showthread.php?t=2692505 and is still downloadable it seems. (https://drive.google.com/file/d/0B34qnFE3O_HbX2t6elg5UXZFNEk/edit)
Looking further at that unbrick thread it seems that SDRAM is checked in step 4 . Where do you get stuck?

lukesan said:
Had a quick look at that bulk mode thing. It seems to refer to a TOT file.
That TOT file seems to be in this thread http://forum.xda-developers.com/showthread.php?t=2692505 and is still downloadable it seems. (https://drive.google.com/file/d/0B34qnFE3O_HbX2t6elg5UXZFNEk/edit)
Looking further at that unbrick thread it seems that SDRAM is checked in step 4 . Where do you get stuck?
Click to expand...
Click to collapse
Well my phone doesn't work with that program anymore. After running into the sdram error for so long i ended up scanning that thread and running across QPST, which is the qualcomm manufacturer tool for flashing phones/tablets with Qualcomm. , which placed my phone into download mode for QPST.
I believe i can fix it using the process listed here: http://forum.xda-developers.com/nexus-4/general/wip-unbricking-nexus-4-using-qpst-t2208289
However i need the correct hex and mbn files, which are generated from the 4.4.2 tot file for my gpad. The annoying part is this has to be done in linux. The guide i found of how to make the correct files is here: http://forum.xda-developers.com/nexus-4/general/wip-unbricking-nexus-4-using-qpst-t2208289 ,
Except i don't know how to work linux and that is just a little too complicated for me. If you have linux and can attempt to help me build the correct files that would be great. Unless i can somehow run a loopback mount command on windows like it mentions, i'm stuck

Bricked Swift

Hello Everyone!
I recently tried to root my wileyfox swift but failed miserably. I did the following when fastbooting the recovery image -> fastboot flash system ****.img.
However, i realized my mistake too late, and now my phone is all messed up!
The phone doesnt show anything when i try to start it and i cant access fastboot again, to undo my mistake. My device manager recognizes my phone when its plugged in to my computer but i cant access any files.
Am i screwed or is there any solution to this?
Thanks in advance!!

Try to access the bootloader with the hardware button combo first (volume down + power / volume up + power). If you get into recovery, you will be able to get to the bootloader with adb or a menu entry. Depends on what recovery you have installed for the latter.
In case you have no access to the bootloader (proper soft brick), go for the QFIL method. Avoid using it unless there is no other option.
Here is the thread:
http://forum.xda-developers.com/wileyfox-swift/general/how-to-set-device-tampered-to-false-t3276317

Cant access bootloader.
However, tried your second option and it went well until i got "SaharaDownload fail" at the last step, and now my computer doesnt recognize the phone in device manager. It does not show anywhere that my phone is connected.

narmista said:
Cant access bootloader.
However, tried your second option and it went well until i got "SaharaDownload fail" at the last step, and now my computer doesnt recognize the phone in device manager. It does not show anywhere that my phone is connected.
Click to expand...
Click to collapse
Does the phone give any indication of being connected? Notification light, starting the display, etc?
If yes, make sure the phone is in the correct mode and check the drivers - some of the other forum members mentioned this and the gymnastics around the battery. This would be on my to-do list. The device might come up on the device manager as different one, so monitor the manager for any changes once you connect the device.
If you happen to have Windows 7 device laying at you house, you can try with it (if only not to worry about compatibility and sporadic Win10 behaviour).
It will be a good idea to check the turkish website for General Mobile 4G (one of the Android one derivatives of the hardware) where some people have faced similar problems using the same tool.

narmista said:
Cant access bootloader.
However, tried your second option and it went well until i got "SaharaDownload fail" at the last step, and now my computer doesnt recognize the phone in device manager. It does not show anywhere that my phone is connected.
Click to expand...
Click to collapse
If you need my help via TeamViewer then WhatsApp me at +27799261595 or pm me

Finally got my phone back on the device manager! However, I still get sahara error when trying the back to false method.
imgur.com/a/FsSX0
*It says no port available since i removed the phone*

My XIAOMI MI A2 went to 0% and now it has a bootloop android one

I was playing normally the phone discharged turned off, and when I connect it only shows the android one screen over and over, the led that shows that it's charging doesn't turns on, I have nothing weird installed, didn't even knew about fastboot or roms, or anything like that until 15 minutes ago, so the fastboot options are not and cannot be activated, does it have a solution? do I just let it be connected for a few hours and try again, or what, i'm a noob on this matters so I don't know what to do. Thanks

maybe try holding vol down and power for 10 or more seconds. it should vibrate. it reboots and shows fastboot icon, you can flash stock rom again, let us know

loop4444 said:
maybe try holding vol down and power for 10 or more seconds. it should vibrate. it reboots and shows fastboot icon, you can flash stock rom again, let us know
Click to expand...
Click to collapse
The fastboot screen shows, but I can't do anything, and if I connect it to my PC after watching somethings like going to CMD and trying some commands the console doesn't even recognize those commands, maybe I have to install something for it to read it? I don't know, if this helps in anyway, I appreciate it.

M4N4GM said:
The fastboot screen shows, but I can't do anything, and if I connect it to my PC after watching somethings like going to CMD and trying some commands the console doesn't even recognize those commands, maybe I have to install something for it to read it? I don't know, if this helps in anyway, I appreciate it.
Click to expand...
Click to collapse
connect phone in fastboot mode and flash stock rom trough MiFlash, but remember to take backup of internal memory. I'll release all except external sd.

pawelik said:
connect phone in fastboot mode and flash stock rom trough MiFlash, but remember to take backup of internal memory. I'll release all except external sd.
Click to expand...
Click to collapse
Can you do the backup even if the phone can't start? does de MiFlash has that option? and thanks i'll try

M4N4GM said:
Can you do the backup even if the phone can't start? does de MiFlash has that option? and thanks i'll try
Click to expand...
Click to collapse
It seems that you didn´t enable USB debugging before, maybe? Did you solve it?

SubwayChamp said:
It seems that you didn´t enable USB debugging before, maybe? Did you solve it?
Click to expand...
Click to collapse
No I didn't enable the USB debugging, and no I haven't been able to do it, the mi flash program needs extra installations but always sends an error message and closes, I really don't know how to do this kind of things, I tried with a program called MiFlash Unlock, but it needs a Xiaomi account connected with the number and I don't have one, I really don't know what to do from here, plus I've read that I need the rom to install and don't know where can I find it and which one is the one that I need to install.
Once again thanks and if someone can help me further than this is appreciated

M4N4GM said:
No I didn't enable the USB debugging, and no I haven't been able to do it, the mi flash program needs extra installations but always sends an error message and closes, I really don't know how to do this kind of things, I tried with a program called MiFlash Unlock, but it needs a Xiaomi account connected with the number and I don't have one, I really don't know what to do from here, plus I've read that I need the rom to install and don't know where can I find it and which one is the one that I need to install.
Once again thanks and if someone can help me further than this is appreciated
Click to expand...
Click to collapse
Anyway you can't do many things although you should have enabled USB debugging atleast you decided to unlock device but fastboot is (almost) useless for device with locked boatloader.
The first thing I do no matter I don't think to root or modify my device is enabling USB debugging just to have more options to recover from an eventual brick.
Now try to do the next before to go to the other option; try to enter to recovery from device off, using volume up + power for some seconds then format/factory reset and let us know what happened.

SubwayChamp said:
Anyway you can't do many things although you should have enabled USB debugging atleast you decided to unlock device but fastboot is (almost) useless for device with locked boatloader.
The first thing I do no matter I don't think to root or modify my device is enabling USB debugging just to have more options to recover from an eventual brick.
Now try to do the next before to go to the other option; try to enter to recovery from device off, using volume up + power for some seconds then format/factory reset and let us know what happened.
Click to expand...
Click to collapse
That option didn't work, volume up + power just tried to start the phone

M4N4GM said:
That option didn't work, volume up + power just tried to start the phone
Click to expand...
Click to collapse
Ok, I supposed it, some partitions get corrupted while device fails to reboot.
Your last solution is using EDL mode, you will find many tutorials on YouTube to put device in this mode using test point method, then flashing the official stock rom through MiFlash tool.
To take in account MiFlash tool doesn´t work while in fastboot mode on devices with locked bootloaders so you have to use it in EDL (Emergency DownLoad) mode, no other workaround known on that. (for this model)
As reference I´ll put the basis of the links that you need to take a look in:
- Test Point method:
https://www.google.com/url?sa=t&rct...=XzknDcBovWw&usg=AOvVaw3gCAHutdqhO0Ukszyz-XJ-
- Drivers for unbrick qualcomm devices:
https://gsmusbdrivers.com/download/qualcomm-hs-usb-qdloader-9008-driver-64-bit-windows/
- Xiaomi Flash Tool:
https://xiaomiflashtool.com/download/xiaomi-flash-tool-20181115
- Fastboot images, you can use the latest:
https://forum.xda-developers.com/mi-a2-lite/how-to/fastboot-xiaomi-mi-a2-fastboot-images-t3824871

SubwayChamp said:
Ok, I supposed it, some partitions get corrupted while device fails to reboot.
Your last solution is using EDL mode, you will find many tutorials on YouTube to put device in this mode using test point method, then flashing the official stock rom through MiFlash tool.
To take in account MiFlash tool doesn´t work while in fastboot mode on devices with locked bootloaders so you have to use it in EDL (Emergency DownLoad) mode, no other workaround known on that. (for this model)
As reference I´ll put the basis of the links that you need to take a look in:
- Test Point method:
https://www.google.com/url?sa=t&rct...=XzknDcBovWw&usg=AOvVaw3gCAHutdqhO0Ukszyz-XJ-
- Drivers for unbrick qualcomm devices:
https://gsmusbdrivers.com/download/qualcomm-hs-usb-qdloader-9008-driver-64-bit-windows/
- Xiaomi Flash Tool:
https://xiaomiflashtool.com/download/xiaomi-flash-tool-20181115
- Fastboot images, you can use the latest:
https://forum.xda-developers.com/mi-a2-lite/how-to/fastboot-xiaomi-mi-a2-fastboot-images-t3824871
Click to expand...
Click to collapse
Thanks i'll try if it works

SubwayChamp said:
Ok, I supposed it, some partitions get corrupted while device fails to reboot.
Your last solution is using EDL mode, you will find many tutorials on YouTube to put device in this mode using test point method, then flashing the official stock rom through MiFlash tool.
To take in account MiFlash tool doesn´t work while in fastboot mode on devices with locked bootloaders so you have to use it in EDL (Emergency DownLoad) mode, no other workaround known on that. (for this model)
As reference I´ll put the basis of the links that you need to take a look in:
- Test Point method:
https://www.google.com/url?sa=t&rct...=XzknDcBovWw&usg=AOvVaw3gCAHutdqhO0Ukszyz-XJ-
- Drivers for unbrick qualcomm devices:
https://gsmusbdrivers.com/download/qualcomm-hs-usb-qdloader-9008-driver-64-bit-windows/
- Xiaomi Flash Tool:
https://xiaomiflashtool.com/download/xiaomi-flash-tool-20181115
- Fastboot images, you can use the latest:
https://forum.xda-developers.com/mi-a2-lite/how-to/fastboot-xiaomi-mi-a2-fastboot-images-t3824871
Click to expand...
Click to collapse
You should try the official and safer fastboot image.
http://c.mi.com/oc/miuidownload/detail?device=1700353

Little Hill said:
You should try the official and safer fastboot image.
http://c.mi.com/oc/miuidownload/detail?device=1700353
Click to expand...
Click to collapse
Wrongly quoted.

Question No valid operation system could be found on G10

Hello There
Just tried to reset the phone from a colleague(forgot his pattern and didnt use his G10 since december 21) and stuck with TFM tool on no command.
Tried every combination with power and volume up but couldn't go further.
With luck after one night of trying the fastboot command on CMD finally found the phone.
First command I tried was fastboot reboot fastboot(found the command somewhere here G10 forum).
The device now wont start in fastboot and start immediately with the AndroidOne logo and afterwards a big red explanation mark with the message:
No Valid operating system could be found.
The device will not boot.
Appreciate any help
Thank you!
Pete

Hey Pete,
I know it's a little late, but I'll put this here just in case you or anyone else needs it later. I got the same error after reset and fixed it by changing the active boot slot.
boot to fastboot
from command prompt/terminal: fastboot getvar current-slot
command will return something like:
current-slot: a
Finished. Total time: 0.002s
In this case you would want to change slot to 'b'
fastboot --set-active=b (if the above says 'current-slot: b', then use --set-active=a here)
fastboot reboot
Then go get a drink or something, this reboot is going to be SLOW.

Dear Experts,
I am having the same error as Pete explained in the beginning, the real problem is I can't get into recovery/fastboot mode by trying different key combinations found in the internet. When I try the combination/ connects usb to PC it shows the error and restart everytime. Even tried to flash stock rom using sp tool but it's not detecting in PC either. Tried a heap of MTK drivers. Tried Test point method. None of these seems to work. Could any super humans among you help me please.
Model - Nokia G10, TA-1334
Thanks in advance..

After a week's research, found the solution and brought back my phone from death. The problem was not the drivers. it was me. Tried the test point method in wrong way, need to set the connection from test point to GND first and then only connect to PC. Also make sure there is at least one program awaiting to be connected (Eg. MTK Client/ MTK Bypass tool).
1. Disable the secure boot.
2. Use SP tool to flash the ROM (Trust me there will be errors. Lots of errors, but it can be sorted with some deep google search).
3. Make sure the test point connected to GND all the time while flashing.
You can do it. Finally, my problem shrinked to the invalid IMEI. will sort it out.

eb60700 said:
After a week's research, found the solution and brought back my phone from death. The problem was not the drivers. it was me. Tried the test point method in wrong way, need to set the connection from test point to GND first and then only connect to PC. Also make sure there is at least one program awaiting to be connected (Eg. MTK Client/ MTK Bypass tool).
1. Disable the secure boot.
2. Use SP tool to flash the ROM (Trust me there will be errors. Lots of errors, but it can be sorted with some deep google search).
3. Make sure the test point connected to GND all the time while flashing.
You can do it. Finally, my problem shrinked to the invalid IMEI. will sort it out.
Click to expand...
Click to collapse
I have the same problem. The phone restarts and I can't put it in fastboot. Could you solve it?

Andrey10 said:
I have the same problem. The phone restarts and I can't put it in fastboot. Could you solve it?
Click to expand...
Click to collapse
You should have back up the firmware before doing anything.
Please try to get the phone in fastboot mode.

I did not make the backup. The combination of buttons to get the phone in fastboot mode does not work for me. All it does is reboot.

Andrey10 said:
I did not make the backup. The combination of buttons to get the phone in fastboot mode does not work for me. All it does is reboot.
Click to expand...
Click to collapse
Have you used SP Flash Tool to reset the device?

eb60700 said:
After a week's research, found the solution and brought back my phone from death. The problem was not the drivers. it was me. Tried the test point method in wrong way, need to set the connection from test point to GND first and then only connect to PC. Also make sure there is at least one program awaiting to be connected (Eg. MTK Client/ MTK Bypass tool).
1. Disable the secure boot.
2. Use SP tool to flash the ROM (Trust me there will be errors. Lots of errors, but it can be sorted with some deep google search).
3. Make sure the test point connected to GND all the time while flashing.
You can do it. Finally, my problem shrinked to the invalid IMEI. will sort it out.
Click to expand...
Click to collapse
hello friend. Did you manage to fix the IMEI by any chance? I have a device that has an invalid IMEI and Serial Number.
I managed to fix the IMEI problem