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

Root I may have bricked my lg g2. any help would be hugely appreciated!

D

dwreck9

Lurker
I have an lg g2 (d801-tmobile) that I had successfully rooted and installed cyanogenmod on it alone with twrp and had a full backup. However, I attempted to install a new rom (official android 5.0 for the lg g2) however I did not wipe anything before flashing the new rom zip. It attempts to boot but stays stuck at the tmobile screen forever. I have attempted to hard reset it with button combination (volume down and power button) and it allows me to "factory reset" but it doesn't boot to recovery, instead it enters fastboot mode. Also when I attempt to enter download mode it shows the download mode screen for about a second but then goes into fastboot mode also. I cannot get my computer to recognize it at all and I'm completely stuck. If anyone has suggestions or any help of any kind it would be greatly appreciated.

thank you so much,

--Derek
 
The cleanest and most sure way to recoup from fastboot mode is to fastboot flash the necessary partitions to restore download mode. My recommendation is aboot, boot, dbi, laf, rpm, sbl1, and tz which you can find here:

http://downloads.codefi.re/autoprime/LG/LG_G2/D801BK/Stock_Firmware

I'd go with the 20a partitions since they're newer.

fastboot devices
fastboot reboot (optional, but will verify the presence of working fastboot connection)

fastboot flash aboot aboot.img
fastboot flash boot boot.img
etc
etc

Once all 7 partitions have been flashed, exit cmd/terminal and unplug phone from pc. Long press power for NO LESS than 15 seconds to power down phone entirely then release power button. Now use the usual button press to enter download mode which should be present at this time. Then proceed to restore stock via kdz/tot.
 
iowabowtech said:
The cleanest and most sure way to recoup from fastboot mode is to fastboot flash the necessary partitions to restore download mode. My recommendation is aboot, boot, dbi, laf, rpm, sbl1, and tz which you can find here:

http://downloads.codefi.re/autoprime/LG/LG_G2/D801BK/Stock_Firmware

I'd go with the 20a partitions since they're newer.

fastboot devices
fastboot reboot (optional, but will verify the presence of working fastboot connection)

fastboot flash aboot aboot.img
fastboot flash boot boot.img
etc
etc

Once all 7 partitions have been flashed, exit cmd/terminal and unplug phone from pc. Long press power for NO LESS than 15 seconds to power down phone entirely then release power button. Now use the usual button press to enter download mode which should be present at this time. Then proceed to restore stock via kdz/tot.
Click to expand...

thank you so much for your help. is there any way I can trouble you to elaborate on how to flash these to my device? I understand the commands but I am unable to get my computer to detect my g2 whatsoever. there is not any sign of it in device manager. I have what I believe are the drivers necessary (lg g2 d801 drivers, adb, and fastboot drivers) but I still have no signs of my phone in the device manager.

again thanks so much and I really appreciate your help.
 
dwreck9 said:
thank you so much for your help. is there any way I can trouble you to elaborate on how to flash these to my device? I understand the commands but I am unable to get my computer to detect my g2 whatsoever. there is not any sign of it in device manager. I have what I believe are the drivers necessary (lg g2 d801 drivers, adb, and fastboot drivers) but I still have no signs of my phone in the device manager.

again thanks so much and I really appreciate your help.
Click to expand...

You'll want the latest version you can find of the LG United Drivers. Google should get you set up there, it's mainly for general usb recognition and for download mode which you'll need later.

For the fastboot portion though, the best and most reproducible method I've found is to download PDAnet to your machine. The download itself comes packaged with fastboot drivers so theoretically, you don't even have to launch the application once downloaded. The drivers should live on your machine after the simple act of downloading it. I would probably not have your phone plugged in at that time. Once the program is on your machine go ahead and plug in the phone while in fastboot mode, with any luck the drivers will auto apply at that time. If not, try rebooting the PC next while leaving the phone plugged in and in fastboot mode the entire duration of the reboot. As Windows boots up, recognizes the plugged device it should search for local applicable drivers and apply. Look in device manager...you want to see a device titled "adb interface" or similar wording. That's a positive ID for either adb or in this case, fastboot mode.

If you don't already have the sdk set up, use our forum's mini sdk package. Unzip to the root of your "C" drive. You should then have a folder called sdk-tools on the root of C with some stuff relating to adb/fastboot inside. Now open command prompt and enter command:

cd c:\sdk-tools

Once at that directory, you can begin to issue the commands listed in the previous post. Be sure to place the 7 .img's inside the sdk-tools folder before issuing the fastboot flash commands as you'll effectively be writing those images from the sdk-tools folder through the usb cable and onto the eMMc of the device, if you will ;)

Side note: when downloading the 7 img's, be sure to left click on each one to download. Do not right click and "save as" because that will accidentally save the URL link and cause major issues. Double check that the file size you've downloaded for each matches the posted file size to lessen potential for a partial download.
 
iowabowtech said:
You'll want the latest version you can find of the LG United Drivers. Google should get you set up there, it's mainly for general usb recognition and for download mode which you'll need later.

For the fastboot portion though, the best and most reproducible method I've found is to download PDAnet to your machine. The download itself comes packaged with fastboot drivers so theoretically, you don't even have to launch the application once downloaded. The drivers should live on your machine after the simple act of downloading it. I would probably not have your phone plugged in at that time. Once the program is on your machine go ahead and plug in the phone while in fastboot mode, with any luck the drivers will auto apply at that time. If not, try rebooting the PC next while leaving the phone plugged in and in fastboot mode the entire duration of the reboot. As Windows boots up, recognizes the plugged device it should search for local applicable drivers and apply. Look in device manager...you want to see a device titled "adb interface" or similar wording. That's a positive ID for either adb or in this case, fastboot mode.

If you don't already have the sdk set up, use our forum's mini sdk package. Unzip to the root of your "C" drive. You should then have a folder called sdk-tools on the root of C with some stuff relating to adb/fastboot inside. Now open command prompt and enter command:

cd c:\sdk-tools

Once at that directory, you can begin to issue the commands listed in the previous post. Be sure to place the 7 .img's inside the sdk-tools folder before issuing the fastboot flash commands as you'll effectively be writing those images from the sdk-tools folder through the usb cable and onto the eMMc of the device, if you will ;)

Side note: when downloading the 7 img's, be sure to left click on each one to download. Do not right click and "save as" because that will accidentally save the URL link and cause major issues. Double check that the file size you've downloaded for each matches the posted file size to lessen potential for a partial download.
Click to expand...
I can't explain how appreciative I am for the help. The reason that my computer wasn't recognizing the phone was that my usb cable wasn't the official lg one. As soon as i used the original one it began downloading all the necessary drivers etc... right now I have entered download mode and it is doing a firmware update. Im assuming this should take a while? it is currently at 0% (been running for probably 5 minutes) would that be normal?

again thanks so much! You truly are a lifesaver!
 
dwreck9 said:
I can't explain how appreciative I am for the help. The reason that my computer wasn't recognizing the phone was that my usb cable wasn't the official lg one. As soon as i used the original one it began downloading all the necessary drivers etc... right now I have entered download mode and it is doing a firmware update. Im assuming this should take a while? it is currently at 0% (been running for probably 5 minutes) would that be normal?

again thanks so much! You truly are a lifesaver!
Click to expand...

Download mode is just an interface. You must use proprietary lg software to flash stock firmware to the phone while actively in download mode. For the G2 there is a kdz flash tool and a tot flash tool. If you choose to use the tot method, that same download link I provided earlier for the partitions also has a tot (its zipped, simply unzip to reveal the raw tot) and a lg flash dll specific to the d801 variant. Those are the 2 target files which are used in the tot method. You can read all about how to use either method here:
http://forum.xda-developers.com/showthread.php?t=2432476

I'm not sure about kdz availability for the d801, the OP of that thread has a repository. Don't worry if the firmware is old, even JB age. You can simply OTA your way forward once the phone has been restored to any previous firmware. Ask if questions. Oh, and if you opt to use the kdz method, choose the "cse" flash option in the kdz flash tool. It ensures a full scale reset of the device back to a new in the box state which would be a wise choice considering where you're coming from.
 
Hey. Is it fixed? Because if I see this right you came from jb bootloader and possibly jb kernel and basoeband to lollipop kernel and didn't have suitable bootloader and baseband.
 
iowabowtech said:
Download mode is just an interface. You must use proprietary lg software to flash stock firmware to the phone while actively in download mode. For the G2 there is a kdz flash tool and a tot flash tool. If you choose to use the tot method, that same download link I provided earlier for the partitions also has a tot (its zipped, simply unzip to reveal the raw tot) and a lg flash dll specific to the d801 variant. Those are the 2 target files which are used in the tot method. You can read all about how to use either method here:
http://forum.xda-developers.com/showthread.php?t=2432476

I'm not sure about kdz availability for the d801, the OP of that thread has a repository. Don't worry if the firmware is old, even JB age. You can simply OTA your way forward once the phone has been restored to any previous firmware. Ask if questions. Oh, and if you opt to use the kdz method, choose the "cse" flash option in the kdz flash tool. It ensures a full scale reset of the device back to a new in the box state which would be a wise choice considering where you're coming from.
Click to expand...
I fell asleep yesterday while it was updating but I can happily say that I am up and running! I'm unbelievably thrilled for this. Thank you so very much iowabowtech! You're a lifesave! How can I donate to you? Through paypal or something? I was ready to pay a repair guy to do it but he wasn't able to.
 
bender_007 said:
Hey. Is it fixed? Because if I see this right you came from jb bootloader and possibly jb kernel and basoeband to lollipop kernel and didn't have suitable bootloader and baseband.
Click to expand...
I am officially fixed thanks to iowabowtech. I flashed the lg stock lollipop rom without wiping my data and partitions and the steps above got me back to stock recovery and rom. It worked like a charm. super easy with the details above.

wish you luck
 
I'm glad you fixed it. Note that the service guys can't know all unbricking techniques but rather connect to boxes and click the magic buttons so it's the best to ask on forums :)
 
What exactly were the commands? I read this whole thing a few times and I don't see what commands to enter into command prompt. Do I just randomly type the names of those 7 files if I'm having the same issue? I can actually get into my phone's OS if that makes a difference, it's just when I try to reboot into recovery mode that I get stuck on fastboot. It's not terribly important, it's my wife's old phone, she has the G3 now. But having built computers for the lat 20 years or so rooting phones was one thing I never tried so this was supposed to be my practice run. Not great so far....

I have busybox installed, as well as flashify, quickboot, supersu, and twrp. I'm not sure if any of those can get me out of this but it was either flashify or twrp that got me into this when I clicked the wrong thing. I flashed something, it said success, I thought great, rebooted and was like "not great". Stuck on fastboot there when I reboot to recovery. But again, I CAN get into the phone if I reboot normally.
 
lordraiden said:
What exactly were the commands? I read this whole thing a few times and I don't see what commands to enter into command prompt. Do I just randomly type the names of those 7 files if I'm having the same issue? I can actually get into my phone's OS if that makes a difference, it's just when I try to reboot into recovery mode that I get stuck on fastboot. It's not terribly important, it's my wife's old phone, she has the G3 now. But having built computers for the lat 20 years or so rooting phones was one thing I never tried so this was supposed to be my practice run. Not great so far....

I have busybox installed, as well as flashify, quickboot, supersu, and twrp. I'm not sure if any of those can get me out of this but it was either flashify or twrp that got me into this when I clicked the wrong thing. I flashed something, it said success, I thought great, rebooted and was like "not great". Stuck on fastboot there when I reboot to recovery. But again, I CAN get into the phone if I reboot normally.
Click to expand...

You should be able to fastboot flash a compatible twrp recovery.img from fastboot mode if that is your only issue. What firmware does the phone currently have on it and how did you root? Also, do you know which version of twrp you tried to flash with flashify?
 
iowabowtech said:
You should be able to fastboot flash a compatible twrp recovery.img from fastboot mode if that is your only issue. What firmware does the phone currently have on it and how did you root? Also, do you know which version of twrp you tried to flash with flashify?
Click to expand...

Fastbood mode doesn't do anything but sit there on that black screen saying fastboot. I rooted using the instructions for it on the highonandroid website. The rooting process seemed fairly simple. But there were also step by step instructions on how to do everything. When you fastboot flash the recovery image I don't exactly know how to do that. Image files on windows are easy to use, you can extract them or just mount them using something like Daemon tools then run them like cds in the virtual drive. I'm not sure how to do image files on Android. The android version on the phone is 5.0.2 and the Kernel is 3.4.0

Twrp is 7.5.1.3 and Flashify is 1.9.1
 
lordraiden said:
The android version on the phone is 5.0.2 and the Kernel is 3.4.0
Click to expand...

That is the crux of your problem. Unfortunately, when you're on Lollipop on this device, you can't just flash TWRP without some significant workarounds. You can root, as you did successfully, but working around the bootloader takes more effort. Fortunately, @bender_007 has been maintaining an automated tool for this:
http://androidforums.com/threads/lg-g2-autorec-twrp-on-lollipop-stock-rooted.917299/

However, I'm not sure if you'll run into issues with that or not since you've attempted a flash to recovery already and you're rooted. Ideally you'd want to use his tool from a stock state. Bender may be able to provide some more insight on that.

If it turns out you can't use the tool, there are other options but it'd be nice to get his take on this first, then formulate the easiest path of travel from there. I pinged him so let's give a bit and see if he opines on your situation.
 
This is why I never toyed with Android before :( It's odd because I've been using Linux on and off for years playing with various distros, especially Backtrack and Kali, but this stuff is Greek to me on the phone. It's probably just lack of practice. I'm embarrassed to say my first computer was a TSR-80. lol
 
lordraiden said:
This is why I never toyed with Android before :( It's odd because I've been using Linux on and off for years playing with various distros, especially Backtrack and Kali, but this stuff is Greek to me on the phone. It's probably just lack of practice. I'm embarrassed to say my first computer was a TSR-80. lol
Click to expand...

Mine was an Apple IIe so I'm not judging bro. :D

And this phone is one of the worst to deal with regardless of linux eperience tho that will help you a great deal moving forward. We've had 2 bootloader workarounds and they are firmware dependent. Not just firmware, but specific partitions of said firmware. You pretty much have to be mired in the workings of this device on a daily basis to know what's up in that regard.

We'll get it fixed no problem. I just want to take the least amount of steps as possible and I'm sure Bender has dealt with many people in various states when using his tool. So we chill and hopefully save you some work in the long run. :)
 
Hello. Yes you are fine as long you are on stock(or stock based rom). It will change the partition layout no matter what. So if it's lollipop(not aosp) you are fine.
 
I may play around with hers in a day or so, but we just bought a car in New Jersey yesterday that died on the way home to CT so we've been focusing on that stuff. I did try to root my Galaxy Note 3 (Tmobile) tonight and I tried CWM and twrp and couldn't get either one to work. CWM there doesn't even seem to be a consensus which file is supposed to work for my phone. My phone is the 900t but the file listed for my phone is 900s and I kept getting some error message. So I went to them CWM website and they have two files, one regular andone touch. The touch one doesn't work at all. The regular one seemed to install with Odin, but when I booted to recovery mode it gave me some message about nonandroid recovery not working or some such. The other times before that it would just boot right into the stock recovery. I set Odin not to auto-restart, I tried the battery pull method, could not get into CWM. TWRP I can't get to work on my note 3 at all for some reason. But maybe it's a sign to wait till I have the Note 5 when it comes out before I screw with the Note 3. My biggest issue is the crap that loads with Android. I don't need a rom, I just want to disable everything like I do with windows via startup, services, and the registry. And the task killers unrooted are useless since the apps just restart a few seconds later. I have an 8400mah battery that winds up dead in about 5-7 hours of heavy use. It should last a lot longer. I also have two of the regular 3200mah batteries and the stock back for them, so I always have enough power when I go out but I'd be able to do a lot more if I can stop the bloatware, or even delete it.
 
dwreck9 said:
I have an lg g2 (d801-tmobile) that I had successfully rooted and installed cyanogenmod on it alone with twrp and had a full backup. However, I attempted to install a new rom (official android 5.0 for the lg g2) however I did not wipe anything before flashing the new rom zip. It attempts to boot but stays stuck at the tmobile screen forever. I have attempted to hard reset it with button combination (volume down and power button) and it allows me to "factory reset" but it doesn't boot to recovery, instead it enters fastboot mode. Also when I attempt to enter download mode it shows the download mode screen for about a second but then goes into fastboot mode also. I cannot get my computer to recognize it at all and I'm completely stuck. If anyone has suggestions or any help of any kind it would be greatly appreciated.

thank you so much,

--Derek
Click to expand...
Glad you got your phone working again and I'm wondering if you can help me out. I have a D801 rooted running stock and I'm trying to flash Cyanogen with TWRP but every time I try, it fails. How did you do it?
 

Attachments

  • IMG_20150707_180508.jpg
    IMG_20150707_180508.jpg
    382.6 KB · Views: 117
I'm using T-Mobile LG G2 d801. I'm rooted using kingroot, but after the phone was rooted with kingroot I replaced it with SuperSuMe App now that I'm rooted why can't I use AutoRec or any other trwp recoveries? Need help..
 
You must log in or register to reply here.
Back
Top Bottom