• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root [International] Please help! LG G2 bricked. Tried everything!

There is nothing at all in device manager. I have looked in all of the different parts of it whilst unplugging and plugging it back in again.

I held the power off button for 30 seconds and then tried to get into recovery. This takes me back to flashboot. I did the same but got into download mode.

I only ever get as far as the screen shot I put on before. It doesn't get into the 'proper' download mode that has the usb symbol and the arrows on.

Thanks
 
Its only one download mode 2 things to ask or maybe 3 . do u have a factory USB cable aka lge USB cable. Next how many USB ports do you have on your PC /laptop. Last do you have another PC/laptop you can use that is up to date with vista or windows 8.
 
There is nothing at all in device manager. I have looked in all of the different parts of it whilst unplugging and plugging it back in again.

I held the power off button for 30 seconds and then tried to get into recovery. This takes me back to flashboot. I did the same but got into download mode.

I only ever get as far as the screen shot I put on before. It doesn't get into the 'proper' download mode that has the usb symbol and the arrows on.

Thanks

Ok, I finally see what you're saying now. I've heard of this before but couldn't remember the details. I had to consort with a gent in IRC to get to the bottom of it. Long story short, we need to fastboot flash a few partitions as I mentioned in my first post here.

So there's a couple options. If you'd rather try getting some help in IRC, you can go that route for faster instructs. If so, go here:

freenode Web IRC (qwebirc)

nickname: whatever you want it to be
channel: #lg-g2

If you want to do it here or there, you'll first need to have some version of the Android sdk on your machine in order to issue fastboot commands. If you don't have that, you can use our mini-sdk which is easier.
 
You may need a special driver for adb/fastboot usage also. From all reports I've seen, it appears Koush's universal adb driver works fine for that:

Koush

Note: if your device shows up as "galaxy nexus" after applying the driver file, don't worry about it. It's a known side effect and doesn't make any difference in function.
 
OK I have installed that as well. Nothing has come up though, should it? What do I do next?
Thanks, I really appreciate this by the way!
 
You'll note in EarlyMon's post about the mini-sdk, the part about updating the path to create an environmental variable. You'll also have to refer to the OP as he states there. If you have that done, you can then open up a command prompt in windows, and while the phone is connected to the pc in "fastboot mode", go ahead and issue the command (from windows cmd)...fastboot devices.
 
Last edited:
Think I already know the answer to this but just in case...issue the command fastboot reboot. If the phone reboots, great. If not (which I kinda doubt), then we'll have to work on some things.
 
Hi, it reboots fine. But then I ran fastboot devices and it did the same again.
Thanks

Hmm, ok great. I'm kinda surprised it worked in that state but happy to hear that. If the fastboot reboot command caused a reboot, then we should be good to proceed.

Ok so now use that link I posted a few posts up. In the folder 10b_EUR_16G Partitions, download the following:

sbl1.img (please note that's typed as... sb, the letter "l", then the number "1".)
aboot.img
rpm.img
boot.img
laf.img
tz.img

NOTE: for the ones that start with a number (like 5-rpm.img), rename those so they are instead exactly like the list I just gave above. In other words, just ditch the numbers from the filename.

To be honest, I believe that list to be overkill but I'd rather be sure we get what we need. Now, take each of those img files and place them into your sdk-tools folder. Just drop them all right in there with the stuff that came there by default.

I noticed you were issuing your commands from that directory so let's continue doing it just like that from here on.

Once you get that done, post back.
 
edit to add: you don't want any of those .img files still zipped. Be sure that you placed the actual .img files into the sdk-tools folder.

Ok, so now's the time when I need to do the usual disclaimer...you accept all risk, etc etc. If you want to roll the dice on a return instead, go that route. I've been involved in this process before with the G2, and it went just fine but anytime we flash partitions, there is some risk.

Ok so if you're still reading, I'll take that as though you want to move forward. Let's start with trying to flash only what I think you absolutely need to keep risk at the lowest possible level.

So from your same C:\sdk-tools directory, again run the fastboot devices command as before, just to make sure its showing the fastboot connection. Even if it's showing the question mark as before, that's fine. Then, run the following two commands, letting the first finish before moving to the second (please double check spelling before hitting enter key):

fastboot flash aboot aboot.img
fastboot flash laf laf.img


If all goes well there, finish it off with a fastboot reboot command. The phone should reboot as before.

Do not expect a booting, working phone right now. That's ok and to be expected. Instead, our goal here is to fix the download mode issue you were having. So now, go back into download mode and if all went well, you should have two new things happening:

1.) the device is being recognized in windows device manager
2.) you should see the download mode picture (with the blue dots), but then it should move past that and into the screen with the "usb symbol and arrows" as you put it.

If that is the case, you should then be able to move forward with reflashing the stock firmware as you were originally trying to do.

Let us know if all goes well up to this point.
 
Hi, Thanks for that. At the moment it is stuck on the LG logo. Should I just wait?


If you already did the above instructs, just go ahead and long press the power button until the phone shuts down entirely (hold for like 30 seconds if need be).

Then, use the usual method to press and hold volume up while connecting to the USB cable/PC in order to get into download mode. That's when you should notice the differences for the positive.
 
Yes! We are in download mode :-) Thank you so much. I may need you again tomorrow when I attempt the next stage but hopefully I will be able to do it.

Thanks so much.:)

No problem, you are past the worst of it now. We'll be here if you need further assistance. :)

Whatever happens tho, please let us know how it turned out if you would please.
 
Also, you probably already know this, but on your D802, please be mindful to flash the EUR 16 GB firmware. On the D802 in particular, the internal storage size is a determining factor.
 
Hi again, it's getting stuck at 49% with the below:

18:38:39 : MODEL DLL Event : (100, 3146241)
18:38:39 : Step : TYPE_WPARAM_UPGRADE_ERROR
18:38:39 : CleanModelDll() : Free Model.dll
18:38:39 : _DetachDLL Call
18:38:44 : _DetachDLL Call End
18:38:44 : Page_Error
 
There are multiple methods and software tools to flash stock firmware. I only done this with the LG Flash Tools software. What software and instructs are you using? I don't know how to interpret what you posted.
 
Before I have to go to work, I'm going to post the method I'm most familiar with. If you strike out with whatever method you're using, you can refer to this if desired.

Use these instructs.

On line 2, where it says to d/l your tot and dll file, don't use that link. Instead use THIS link which should look familiar to you since that's where you also got the partition img's from earlier. This time though, you'll want to download the file called BIN_LGD802AT-00-V10b-EUR-XX-SEP-07-2013-16G, and the dll file at the very bottom. Inside that large zip file is the .tot for your device. Yes, it's an older one but using that tot and the listed bin will bring you to original stock. As long as you receive OTA updates at your location, you can just accept OTA's when you're done with this and you'll end up back on the latest firmware.

On the original instructs page I linked, it mentions swapping out the megalock dll file in the Flash Tools software package. If you do that and you end up with any megalock errors when attempting the flash, here is an alternate megalock dll to swap out instead:

Alternate megalock dll (only use if needed)

So to review...download LG Flash Tools software, the tot and dll for your phone, then follow the instructs as posted in the link. Note the pictoral that's also available there to help you along the way.

I have heard that some of the altnernative methods to flash stock on LG phones don't work as well on the G2 because of its huge rom size. For some reason that seems to mess with them. I've seen very few issues reported with the LG Flash Tools method however. So good luck if you need this.

source and thanks: autoprime of the xda forums, freenode IRC and team Codefire. If there were others involved in the writeup and file storage solution, thanks to all.
 
Hi, When I install the LG Flash Tool I get the attached. And then it asks me for a user name and password.
Thanks
 

Attachments

  • 1.jpg
    1.jpg
    8.9 KB · Views: 83
Hi, When I install the LG Flash Tool I get the attached. And then it asks me for a user name and password.
Thanks

Never seen that. Make sure the Flash Tools version you downloaded was 1.8.1.1023. There are older versions out there that will not behave in the same way you need.

Also, did you replace the megalock.dll as per the instructs? If not, that could be the reason. If you did already replace it, try the alternate megalock dll I posted instead and then try to re-run the tool.

Lastly, I can't remember all what drivers you have installed, but if you don't have the LG United Mobile driver installed, that could be an issue as well. Link for that here:

Directory Listing of //Xda/LG Software/Drivers/

I think it may be available on the LG website as well.

Make sure you are in download mode too and change the COM port as instructed. It needs to detect the phone in that state.
 
Back
Top Bottom