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

Root [AT&T] Did I just brick my new LG G2 ?

I don't believe adb will work while in fastboot mode, not sure. I'm taking those words literally and thinking only fastboot commands would work here. So I'd want to try fastboot devices command instead.

You should be able to use a mac, yes. I just don't know the exact command nomenclature with a Mac but as long as you know how to fastboot flash img files with it, then fine.
 
I really appreciate all your help, but I gotta tell you - I know exactly squat about fastboot. I assume it has something to do with my phone?

Just kidding....I know it has to do with my phone. But that's literally the extent of my fastboot knowledge. I'm googling now in a separate tab, but any continued guidance will be much appreciated.
 
adt2 said:
I really appreciate all your help, but I gotta tell you - I know exactly squat about fastboot. I assume it has something to do with my phone?

Just kidding....I know it has to do with my phone. But that's literally the extent of my fastboot knowledge. I'm googling now in a separate tab, but any continued guidance will be much appreciated.
Click to expand...

Fastboot is similar to adb. If you know one, you virtually know the other. If you installed the Android SDK and the associated tools/platform tools that comes with that, then you have both adb and fastboot with that.

What we do is download a series of .img files to your PC or Mac. Since the phone is already in fastboot mode by default right now, you can then use the command line/terminal on your PC to flash the phone with said .img files thereby restoring the phone to a state where download mode becomes available.
 
Ok so I'm not positive if that is ok or not. Normally, there'd be some other indentifiers there. So try this:

fastboot reboot

Does it reboot the phone? It'll go back into the fastboot mode but interested to see if it reboots in the process. That would verify that we're running fastboot commands and they're being received.
 
iowabowtech said:
Ok so I'm not positive if that is ok or not. Normally, there'd be some other indentifiers there. So try this:

fastboot reboot

Does it reboot the phone? It'll go back into the fastboot mode but interested to see if it reboots in the process. That would verify that we're running fastboot commands and they're being received.
Click to expand...

Yep, that reboots the phone. All I get is the same five lines of text, but it definitely rebooted. Went black, got LG logo, back to white text. Yay?
 
Yes, that's a yay. :D

What you're gonna want to do is go back up the page here on this very thread and revisit those partitions I linked earlier. (the 10_d partitions). From that list, you'll need to download the following to your computer:

aboot.img
boot.img
laf.img
rpm.img
sbl1.img
tz.img
dbi.img

You can ignore the rest, just need those 7. I'll work up the rest of instructs momentarily.

Edit for anyone reading this after the fact. You should only need aboot and laf to restore download mode (and possibly boot if you had a failed Autorec flash). Make sure they are from a matching software version. (i.e. aboot.img from 10_d and laf.img from 10_d, etc). If flashing aboot and laf (and boot if applicable) don't give you download mode, then flash all the listed partitions and cross your fingers.
 
Ok so I have a question for you. You're using the Mac right? When you entered that fastboot command, are you issuing that from a certain directory/folder? Or are you just able to issue that from any directory and it works? I see references to Mac installs where one must issue adb/fastboot commands from the same directory in which the adb/fastboot utilities are housed. I'm not sure if there's a way to make that global on a mac and if so, if that's what you've done somehow? Bottom line...I want to make sure we issue the command set from the correct directory.
 
As a rep of this site, I MUST take this opportunity to invoke the typical disclaimer...you can back out of this if you want. You're willing to assume all risk blah blah blah.

I have NOT done this procedure myself but I HAVE seen this done and it has worked to restore download mode to the LG G2. So if you're cool with all that...

...here's what we do. I would just as soon house those 7 images in a folder so they're all in one confined spot. Probably not necessary but I feel better about it. Maybe create a folder on your desktop and call it android. Once done, place the 7 .img files into that folder. Then fire up terminal and cd to that android folder.

Just to be sure, we're still a go, issue the fastboot devices command first from that locale. If it shows up as before, we're ready. Very important to maintain a constant connection with the phone to Mac from here forward. Next issue these commands, waiting for each to complete before starting the next:

fastboot flash aboot aboot.img
fastboot flash boot boot.img
fastboot flash laf laf.img
fastboot flash recovery recovery.img
fastboot flash rpm rpm.img
fastboot flash sbl1 sbl1.img
fastboot flash tz tz.img

Once all the flashes are complete, go ahead and disconnect the usb cable from the phone and long press the power button. If it reboots, then long press the power button again until the phone is completely off.

Once it's off, try now to enter download mode and see if you have it. If all went well, you should.
 
Okay, all the flashing went well (I think). Turned phone off, booted into download mode and got a very pretty screen saying something about updating. Then got an error in the middle of a black window, then a blank screen, then the LG logo with the pulsing turquoise LED. That's been on-screen now for a couple of minutes with no change or other activity.

EDIT: The fastboot devices command no longer produces any result, but the adb devices command gives me a serial number and "offline". Just FYI.
 
iowabowtech said:
So it doesn't show download mode like the pic I posted several posts up? Was kind of expecting that to be honest?
Click to expand...

Okay, I waited for the LG logo to disappear and it never happened, so I turned it off and re-did the download mode thing, and this time I go the download mode graphic like in your image above. Phone is now on a "Firmware Update" screen with a non-moving 0% progress indicator. Also says "rooted" at the bottom. Yay, or not?
 
adt2 said:
Okay, I waited for the LG logo to disappear and it never happened, so I turned it off and re-did the download mode thing, and this time I go the download mode graphic like in your image above. Phone is now on a "Firmware Update" screen with a non-moving 0% progress indicator. Also says "rooted" at the bottom. Yay, or not?
Click to expand...

That be a woot. :D

That is precisely how it's supposed to look. Hang tight while I write up the final leg of instructs to your soon to be booting, stock phone.
 
You'll need Windows for this last part.

I want to start by saying a huge thanks to the gents over at freenode IRC, channel lg-g2 for the following links and instructs. Those guys have been clutch support for this phone. :)

Start here:
Restore Stock G2 Firmware - Pastebin.com

Download the LG Flash Tools. Note the rest of the instructs on that page to download and replace the "megalock dll" with the one linked there. Do that as instructed.

Next get the ATT varian't .dll and .tot file here and download to your PC:
Listing of Stock_Firmware

(note that the .tot is housed within that zip that's listed. So d/l and extract to reveal the .tot file)

Though the original page has the basic instucts, here's the pictoral guide to help you along:
imgur: the simple image sharer

Final note:
One user here, recently reported that they got a dll error when starting all this and we believe it came from the megalock dll. I think I'd try the aforementioned megalock dll first but if you experience that same problem, see the following thread for an alternate megalock dll file and swap it with that one instead. Note the last several posts in this thread to see the link(s):

http://androidforums.com/sprint-lg-g2-all-things-root/838706-lg-g2-brick.html
 
Me and the laptop battery are both dying, so I'm going to table this (hopefully) final part until tomorrow morning. Thank you again for all your help. I'll update here after doing these last steps and let you know where things stand.
 
You've been a trooper man and you are through the worst of it. In fact, you've hit about every snag there is to hit and made it through. Many people have done this last part to restore their phone to stock, myself included. So you're in the home stretch with the light at the end of the tunnel shining brightly.

Looking forward to hearing how it goes.
 
I am back in business! Process linked above was relatively quick and painless, and I am now back to the "Let's set up your new AT&T phone!" screen. Android version is 4.2.2, software version is D80010o.

Now I need to decide whether/how to do all this again. Maybe I can live with LG & AT&T's crapware after all...

Again, I can't thank you enough for all your help.
 
By way of comparison, I just returned my Cyanogenmod 11 Nexus 5 to stock. Took about 5 minutes total, including the download, and required exactly one command be typed in.

For me personally, Nexus 5 > LG G2. I'll keep the G2, because I got a great deal on it, but I think I'll go back to the N5 as my daily driver (although CM11 wasn't great).
 
Brian706 said:
Dirty Unicorns!

http://androidforums.com/showthread.php?t=807957
Click to expand...

Strangely ive never tried DU.
Strange because i chat to their dev Alex Cruz on g+.
Its maybe because i dont like AOKP.
A buddy of mine put Liquid Smooth on his new G2 and likes it so have a look at that too :thumbup:
I think all these issues will be ironed out. I see the G2 as the nexus5's big brother and if money was no object id own one now :)

EDIT sorry brian i just realised your link was for the nexus 5 :)
For hammerhead i recommend carbon or validus
 
You must log in or register to reply here.
Back
Top Bottom