Database Users

Lg g2 Boot loops

I am not sure if I can post this solution in this thread as I am not a developer and merely sharing my experience, It seems several people are having issues with bootloops after installing att update or for some other reason, my post deals with helping only a certain issue. You should be able to boot into recovery by any means in order to use my solution.
The problem I had was I was trying to flash a new Rom and copied Rom and gapps into my phone( of course I was rooted and had recovery flashed) and then out of curiosity I wiped everything in advanced wipe in twrp so now I have no Rom to boot into or no file to flash and either download mode would not work, I was p******g in my shorts as I my phone was only a week old and its dead that's what I at least thought. And after spending the whole night no solution was found in xda website and neither did Google help any, now the solution. now u should compare this to ur problem and find where u stand. I installed pdanet on my pc as stock lg drivers don't seem to help pc recognize my phone in recovery mode, then I plugged my phone to pc while phone is still in recovery mode and then opened pdanet in pc and installed lg drivers through it and then adb was able to see my device(until now I was trying adb sideload and it wasn't working) so when adb was able to see my device, I used sideload in twrp and pushed Rom from pc to phone using sideload commands and my phone was back and I am the happiest man in the world. So in short
1. This method works only for people who can boot into twrp recovery but not into phone.
2. Have ur desired roms and gapps ready 3. Make sure u have a working adb in ur pc and if not install minimal adb and fastboot application only onto ur desktop for easy access, and copy ur desired Rom and gapps into that folder and rename them to 1.zip and 2.zip for easy reference and easy adb commands.
4. Download and install pdanet on your pc. Power on ur device into recovery and plug it into your pc. Start adb from the folder u installed on your desktop(hold shift and right click within the folder(minimal adb and fastboot) and click on start command here option, command opens up and it will show in which folder ur in and then type adb devices and if everything is right your phone in sideload mode should show up as adb sideload and if not (this is where the problem is) run pdanet and install lg drivers through it and then unplug exit sideload and restart sideload in ur phone and plug it back to pc and ur pdanet will notify u have connected ur lg phone. Then run adb again and type adb devices and it will show up as adb sideload and now (you should search how to use sideload as I don't remember those commands) and push Rom into (the ones u renamed for easy access and reboot and all should be all. Sorry for the lengthy post but I typed this solution into several posts individually and so decided to put it up as sticky and if anyone feels to remove part of or all the post I have no problem, just wanted to do my help to others with similar problem.
Sent from my LG-D800 using xda app-developers app

lingarajug said:
I am not sure if I can post this solution in this thread as I am not a developer and merely sharing my experience, It seems several people are having issues with bootloops after installing att update or for some other reason, my post deals with helping only a certain issue. You should be able to boot into recovery by any means in order to use my solution.
The problem I had was I was trying to flash a new Rom and copied Rom and gapps into my phone( of course I was rooted and had recovery flashed) and then out of curiosity I wiped everything in advanced wipe in twrp so now I have no Rom to boot into or no file to flash and either download mode would not work, I was p******g in my shorts as I my phone was only a week old and its dead that's what I at least thought. And after spending the whole night no solution was found in xda website and neither did Google help any, now the solution. now u should compare this to ur problem and find where u stand. I installed pdanet on my pc as stock lg drivers don't seem to help pc recognize my phone in recovery mode, then I plugged my phone to pc while phone is still in recovery mode and then opened pdanet in pc and installed lg drivers through it and then adb was able to see my device(until now I was trying adb sideload and it wasn't working) so when adb was able to see my device, I used sideload in twrp and pushed Rom from pc to phone using sideload commands and my phone was back and I am the happiest man in the world. So in short
1. This method works only for people who can boot into twrp recovery but not into phone.
2. Have ur desired roms and gapps ready 3. Make sure u have a working adb in ur pc and if not install minimal adb and fastboot application only onto ur desktop for easy access, and copy ur desired Rom and gapps into that folder and rename them to 1.zip and 2.zip for easy reference and easy adb commands.
4. Download and install pdanet on your pc. Power on ur device into recovery and plug it into your pc. Start adb from the folder u installed on your desktop(hold shift and right click within the folder(minimal adb and fastboot) and click on start command here option, command opens up and it will show in which folder ur in and then type adb devices and if everything is right your phone in sideload mode should show up as adb sideload and if not (this is where the problem is) run pdanet and install lg drivers through it and then unplug exit sideload and restart sideload in ur phone and plug it back to pc and ur pdanet will notify u have connected ur lg phone. Then run adb again and type adb devices and it will show up as adb sideload and now (you should search how to use sideload as I don't remember those commands) and push Rom into (the ones u renamed for easy access and reboot and all should be all. Sorry for the lengthy post but I typed this solution into several posts individually and so decided to put it up as sticky and if anyone feels to remove part of or all the post I have no problem, just wanted to do my help to others with similar problem.
Sent from my LG-D800 using xda app-developers app
Click to expand...
Click to collapse
I have more or less the same issue. Was with StockMod for D802 and received an official OTA and accepted and installed it. Now I'm stuck in bootloop. Unlike you, I can go into recovery (CWM not TWRP) BUT I can't seem to go into fastboot mode. When I hold the Volume Up and connect the phone through cable to my laptop, the phone boots but goes automatically into recovery mode. Did system wipe as well (which I shouldn't have) and at that point my phone has no OS to boot into so I used ADB to transfer CM 10.2 and GAPPS to my phone hoping that if I do it like I'm flashing a custom rom will help but unfortunately it didn't. I'm still stuck in bootloop and can't go into fastboot. help please...:crying:

Try a stock Rom and see if it helps.
Sent from my LG-D800 using xda app-developers app

[Q] Big issue with my Sprint LG G2 after I cleared the system

So I deleted everything in my phone, including the Rom I wanted to flash (smart, right?) and all I have is TWRP Recovery mode and Download Mode. When I put my phone into any mode, my PC does not recognize it and I therefor cannot fix it... I've tried it on three computers with downloading and updating the drivers. The first time it works after installing and updating the drivers, but when I put it in the second time it does not work. I need to unplug my phone in download mode while doing the LG program, and the computer won't recognize or find my phone. All help is greatly appreciated and thanks to repliers in advance
Day 2 of not having a phone: I can't do this xD I need to fix it somehow, if anyone can help me please do

Boot to recovery and start adb sideload mode. Then from your computer just adb sideload rom.zip
If your phone doesnt install the drivers once in sideload mode then manually search for the adb bridge driver from the android sdk and install it.

x714x said:
Boot to recovery and start adb sideload mode. Then from your computer just adb sideload rom.zip
If your phone doesnt install the drivers once in sideload mode then manually search for the adb bridge driver from the android sdk and install it.
Click to expand...
Click to collapse
Tried that and it would say "device not found." and other error codes. One time I was able to load my device onto the computer and after it completed the CM 11 transfer it stopped. I may have to order an OTG cable or something...

[Q] hours for searching for nothing help plz!

I ****ed up my phone today I did full wipe (formatted internal storage too, so i can't flash any rom in recovery because there is nothing) and now i've been searching hours someone who can help me? In TWRP i can't mount anything to my pc (i do not know why?) AND adb says me "devices not found" or something like that so can't push any zip-file to my phone via adb sideload. Is there any way to reapir my phone? can someone help me? Thanks alot!

There was a bug in a bunch of recent twrp releases that causes adb to not work in recovery. Patched versions have been made, try finding one for your device.
Added:
If you can't find a patched version, flash cwm or philz recovery with fastboot, adb is working on both of those. You just need a rrcovery image and do
"fastboot flash recovery <recovery-file>.img"
In fastboot mode.

let's try it out!
nvan7891 said:
There was a bug in a bunch of recent twrp releases that causes adb to not work in recovery. Patched versions have been made, try finding one for your device.
Click to expand...
Click to collapse
So u mean i need to flash new recovery version? how i can do it when my adb isn't workin? thanks!

alkkade said:
I ****ed up my phone today I did full wipe (formatted internal storage too, so i can't flash any rom in recovery because there is nothing) and now i've been searching hours someone who can help me? In TWRP i can't mount anything to my pc (i do not know why?) AND adb says me "devices not found" or something like that so can't push any zip-file to my phone via adb sideload. Is there any way to reapir my phone? can someone help me? Thanks alot!
Click to expand...
Click to collapse
i dont know how to fix your problem but i know how u can change the devices not found
install on your computer pdanet driver.
p.s.
i ****ed up my phone as well today i publish a post i will be thankfull if look on my problem.thanks.

alkkade said:
So u mean i need to flash new recovery version? how i can do it when my adb isn't workin? thanks!
Click to expand...
Click to collapse
See the edit to my first response. Fastboot is done in fastboot mode, not recovery, so you should be good. You just need the basic .img file of cwm or philz recovery.

If you are on win 7 try this:
http://adbdriver.com/downloads/
(Adb driver installer)
Run it when you turn adb sideload on in G2 and connect it to PC.
If it fails you still can go buy somewhere USB OTG cable (few bucks) and flash ROM from usb stick like me.

It appears that accessing fastboot pn the lg g2 is not so simple. Sorta like samsung phone deal, where a manufacturer download is used instead. From what I gather, recovery might need to be wiped to access fastboot, which you could do from terminal in twrp, but thats risky. Apparently, a lot of people have gotten stuck in fastboot mode. Best bet would be to reflash stock firmware through lg download mode. Also see this thread for a method to return to stock firmware:
http://forum.xda-developers.com/showthread.php?t=2432476
Once you are back to stock, just reroot and flash revovery, etc.

downloadmode should still work. go back to any kdz for your version
also source and versions post next time

[Q] [BRICK][TWRP] LG G2 D-802 bricked & not seen from PC

Hi there, this is a big trouble.
My LG G2 (16GB, european format, I bought it in Italy) always work perfectly. I didn't mod anything til yesterday, just rooted and added superuser, and worked fine. I have the original stock firmware and original Android 4.4.0 Kit Kat.
Then yesterday I wanted to install the XCam, so before I install the TWRP recovery. Disaster: black, total black. From that moment, G2 doesn't work. And didn't go to recovery or download.
One of the last moves I did before the disaster: TWRP installing asked me the format of my mobile, "AT&T" or "international", and I chose the second one.
Anyway, after some attempts, I was succesful in restore a few modes. I followed this guide:
http://forum.xda-developers.com/showthread.php?t=2451696
With Ubuntu on the terminal of my friend, I followed the guide and now this is the current situation:
1) When I try to press power, it stucks at the logo
2) If I press power & vol -, appears the logo, then press these again and I go in sort of Hard Factory Reset, but it's not really true, cause I press 3 times power and I go in TWRP recovery
3) If i press vol + while I'm plugging mobile to PC, appears the "download mode" screen on mobile. But PC doesn't see it
(see the photos I attached)
Now my real problem is how to install and restore the original stock firmware. All this trouble happened not because of OTA or a mod, but just cause of installing a TWRP in bad way.
In the guide I linked above, it suggests to write some command strings in recovery but that doesn't work for me, I guess cause I don't have an OTA.
So I don't know how to insert a file to restore my firmware, because I don't have in my memory and, as you know, G2 doesn't have external memory.
I tried connecting a usb pen drive but doesn't see it in recovery.
I tried connecting in download mode to PC, using LG Flash Mobile and more, but doesn't work cause my PC seems unable to see the mobile.
I followed this guide hoping to modify the hosts file:
http://forum.xda-developers.com/showthread.php?p=44710061#post44710061
But didn't work. Also, I can't activate usb debug cause I can't enter in my mobile.
What can I do? Suggestions?

kiapsita said:
Hi there, this is a big trouble.
My LG G2 (16GB, european format, I bought it in Italy) always work perfectly. I didn't mod anything til yesterday, just rooted and added superuser, and worked fine. I have the original stock firmware and original Android 4.4.0 Kit Kat.
Then yesterday I wanted to install the XCam, so before I install the TWRP recovery. Disaster: black, total black. From that moment, G2 doesn't work. And didn't go to recovery or download.
One of the last moves I did before the disaster: TWRP installing asked me the format of my mobile, "AT&T" or "international", and I chose the second one.
Anyway, after some attempts, I was succesful in restore a few modes. I followed this guide:
http://forum.xda-developers.com/showthread.php?t=2451696
With Ubuntu on the terminal of my friend, I followed the guide and now this is the current situation:
1) When I try to press power, it stucks at the logo
2) If I press power & vol -, appears the logo, then press these again and I go in sort of Hard Factory Reset, but it's not really true, cause I press 3 times power and I go in TWRP recovery
3) If i press vol + while I'm plugging mobile to PC, appears the "download mode" screen on mobile. But PC doesn't see it
(see the photos I attached)
Now my real problem is how to install and restore the original stock firmware. All this trouble happened not because of OTA or a mod, but just cause of installing a TWRP in bad way.
In the guide I linked above, it suggests to write some command strings in recovery but that doesn't work for me, I guess cause I don't have an OTA.
So I don't know how to insert a file to restore my firmware, because I don't have in my memory and, as you know, G2 doesn't have external memory.
I tried connecting a usb pen drive but doesn't see it in recovery.
I tried connecting in download mode to PC, using LG Flash Mobile and more, but doesn't work cause my PC seems unable to see the mobile.
I followed this guide hoping to modify the hosts file:
http://forum.xda-developers.com/showthread.php?p=44710061#post44710061
But didn't work. Also, I can't activate usb debug cause I can't enter in my mobile.
What can I do? Suggestions?
Click to expand...
Click to collapse
Help, please

borrow or buy a mini usb otg stick, put the flashable stock rom on it (for your variant), connect it to the device, enter twrp, install the rom zip from usb otg...
see in twrp under "mount" if it shows you "usb/otg" (don't know which twrp version you have so i assume it's the older 2.7.x.x one)
you can also search the xda on how to sideload a rom zip from a computer to a bricked or formatted device (i personally have mini usb otg stick so i never used sideloading)
good luck

You haven't attached any images of the download mode.
Downloade mode is:
1. power off your lg g2
2. hold volume up AND connect g2 to pc
Now..if there is an actual download mode with arrows then it's ok. If you see the blue circles only then you have to fix it.
This would be the next step then...
btw LG flash tool

571
bender_007 said:
Now..if there is an actual download mode with arrows then it's ok. If you see the blue circles only then you have to fix it.
Click to expand...
Click to collapse
I'm afraid it's the second one... It's the same of this one:

kiapsita said:
I'm afraid it's the second one... It's the same of this one:
Click to expand...
Click to collapse
There is a way to fix it?
I already tried the tutorial with LG Flash Tool, but PC doesn't see my device

Install vmware and download slax. Install slax inside vmware. Connect it to PC and attach the qualcomm device. Then there is another tutorial for unbricking. Seek my posts inside

bender_007 said:
Install vmware and download slax. Install slax inside vmware. Connect it to PC and attach the qualcomm device. Then there is another tutorial for unbricking. Seek my posts inside
Click to expand...
Click to collapse
"Connect it to PC and attach the qualcolmm device"? What you mean? Just that I plug my device to PC?

kiapsita said:
"Connect it to PC and attach the qualcolmm device"? What you mean? Just that I plug my device to PC?
Click to expand...
Click to collapse
Which tutorial you mean?

http://forum.xda-developers.com/showthread.php?t=2582142
---------- Post added at 05:19 PM ---------- Previous post was at 05:18 PM ----------
Use vmware and slax. Flash aboot, boot, laf. No other files.

sea mniteen
bender_007 said:
http://forum.xda-developers.com/showthread.php?t=2582142
---------- Post added at 05:19 PM ---------- Previous post was at 05:18 PM ----------
Use vmware and slax. Flash aboot, boot, laf. No other files.
Click to expand...
Click to collapse
I don't have Ubuntu, are you sure I can do that with Windows PC - and with no damage?
I already follow this tutorial (the first link in my first post). Now my computer can't see the device. Are you sure I can do this procedure anyway?

bender_007 said:
Use vmware and slax. Flash aboot, boot, laf. No other files.
Click to expand...
Click to collapse
And where do I get aboot, boot and laf?

Help! I need to restore download mode -now is in blue circles!

From your kdz, use kdz extractor.

bender_007 said:
From your kdz, use kdz extractor.
Click to expand...
Click to collapse
I'm sincerely worried to damage my PC with VmWare and Slax. Can't I use Ubuntu?

You can use ubuntu. Neither of these will damage your pc

Should I also overwrite the openrecovery file with an updated TWRP recovery, in order to support USB OTG ?

Can't find kdz extractor, anyway

I have the same problem and i have try all the aboves the only way to unbrick it i think is only via adb because i have adb acces
sorry for my english, thanks advance.

refresh! same problem any help? : d

Help with Rooting SM-G900h

Hey guys, so first of all, consider me a noob with everything related to samsung devices, i used to root xperia devices, but now wanna try rooting my sm-g900h but i have a few questions about the process and a few possibilites from you savvy lot.
Pre-requisites :
- device has usb debugging mode on
- has unlocked bootloader
- computer has device drivers
//Do i need anything else ?
Questions :
1. I would like to install a custom recovery too (idk how that works using the odin program), so after having installed said recovery would i be able to root my device using it ? (flashing the needed rom and the CF rooting module ?)
2. When i try flashing android 4.4 on my device, odin seems to get stuck at the "initialisation" step every time. (as i've said, i'm new to odin and such) After reading around, a few tips were said about removing the battery before going into flashmode then putting it in once odin detects it but still to no avail. What am i doing wrong while flashing the custom rom ?
Any help would be greatly appreciated,
Thanks.

Go to the below link for rooting
http://forum.xda-developers.com/showthread.php?t=2696537
Got to the below link to download custom recovery (TWRP)
https://dl.twrp.me/klte/
Instructions to flash recovery
Download the tar file
Put phone in download mode
open odin select AP or PDA depending on the odin version
Select the Tar file
Click start
Satsana said:
Hey guys, so first of all, consider me a noob with everything related to samsung devices, i used to root xperia devices, but now wanna try rooting my sm-g900h but i have a few questions about the process and a few possibilites from you savvy lot.
Pre-requisites :
- device has usb debugging mode on
- has unlocked bootloader
- computer has device drivers
//Do i need anything else ?
Questions :
1. I would like to install a custom recovery too (idk how that works using the odin program), so after having installed said recovery would i be able to root my device using it ? (flashing the needed rom and the CF rooting module ?)
2. When i try flashing android 4.4 on my device, odin seems to get stuck at the "initialisation" step every time. (as i've said, i'm new to odin and such) After reading around, a few tips were said about removing the battery before going into flashmode then putting it in once odin detects it but still to no avail. What am i doing wrong while flashing the custom rom ?
Any help would be greatly appreciated,
Thanks.
Click to expand...
Click to collapse

androidtweaker1 said:
Go to the below link for rooting
http://forum.xda-developers.com/showthread.php?t=2696537
Got to the below link to download custom recovery (TWRP)
https://dl.twrp.me/klte/
Click to expand...
Click to collapse
Ok so first things first, i finally managed to root my phone, (my knox counter tripped, =1 now) but i think it soft-bricked my phone since i found myself in a bootloop.
After trying to access the recovery (volume up + home + power buttons) nothing happened, so tried flashing a new recovery, following the link u provided, but i still cannot seem to be able to get into the recovery.
Am i doing something wrong ?
Thx a lot for your help

Try this
1) Flash stock firmware using odin
2) Flash recovery from the my previous post
3) Root using odin using file from this link. It your model specific file. I had given root file for KLTE model previously may be that's causing the bootloop.
Satsana said:
Ok so first things first, i finally managed to root my phone, (my knox counter tripped, =1 now) but i think it soft-bricked my phone since i found myself in a bootloop.
After trying to access the recovery (volume up + home + power buttons) nothing happened, so tried flashing a new recovery, following the link u provided, but i still cannot seem to be able to get into the recovery.
Am i doing something wrong ?
Thx a lot for your help
Click to expand...
Click to collapse

androidtweaker1 said:
Try this
1) Flash stock firmware using odin
2) Flash recovery from the my previous post
3) Root using odin using file from this link. It your model specific file. I had given root file for KLTE model previously may be that's causing the bootloop.
Click to expand...
Click to collapse
Well finally managed to familiarize myself with odin (from a noobs perspective of course hehe) But yeah that's what i've done, then flashed cwm recovery, cause that's actually the only one that didn't cause a bootloop in my case.. and rooted it again via the chain fire's method all over again =3.
Thank you guys very very much for your help and for your precious time,
Helped me quite the bit ;3

Great! :highfive:
Satsana said:
Well finally managed to familiarize myself with odin (from a noobs perspective of course hehe) But yeah that's what i've done, then flashed cwm recovery, cause that's actually the only one that didn't cause a bootloop in my case.. and rooted it again via the chain fire's method all over again =3.
Thank you guys very very much for your help and for your precious time,
Helped me quite the bit ;3
Click to expand...
Click to collapse

androidtweaker1 said:
Great! :highfive:
Click to expand...
Click to collapse
If i may ask one last question that isn't related to this thread, it would be how would i be able to access the phone via adb (i already have everything installed for it of course ) without the phone being turned on
On my old sony phone we had this fastboot mode for example so we could use the fastboot command interface =o.
In the case of samsung devices there seems to be only the odin mode/recovery options and i can't detect the phone from odin mode and via the recovery it's detected [using the "update from adb" option] but using this, the options are quite limited (i can only use the command : adb sideload <module_to_flash> =/)
[in my case i would like to do a nandroid backup through adb but i need to be able to first detect my phone (and without having the phone booted on the system)]
Thanks a bunch though, for everything

You can do a nandroid backup using CWM
Satsana said:
If i may ask one last question that isn't related to this thread, it would be how would i be able to access the phone via adb (i already have everything installed for it of course ) without the phone being turned on
On my old sony phone we had this fastboot mode for example so we could use the fastboot command interface =o.
In the case of samsung devices there seems to be only the odin mode/recovery options and i can't detect the phone from odin mode and via the recovery it's detected [using the "update from adb" option] but using this, the options are quite limited (i can only use the command : adb sideload <module_to_flash> =/)
[in my case i would like to do a nandroid backup through adb but i need to be able to first detect my phone (and without having the phone booted on the system)]
Thanks a bunch though, for everything
Click to expand...
Click to collapse

androidtweaker1 said:
You can do a nandroid backup using CWM
Click to expand...
Click to collapse
Tried doing one using cwm right now, 5GB and still not enough space =O have to do it all over again =.='
But isn't there any way to access phone via adb without it being turned on ? =o

If you want ADB access do the below.
Ensure you have the USB drivers installed
Go to settings>about phone>build number>tap build number 7 times
Go back to settings>developer options>select usb debugging
Now connect phone to PC> there will be a prompt displayed on your phone select okay
ADB drivers will be installed. Thats it
Now you have ADB access
You can take a backup even when the phone is turned on via ADB
Satsana said:
Tried doing one using cwm right now, 5GB and still not enough space =O have to do it all over again =.='
But isn't there any way to access phone via adb without it being turned on ? =o
Click to expand...
Click to collapse

androidtweaker1 said:
If you want ADB access do the below.
Ensure you have the USB drivers installed
Go to settings>about phone>build number>tap build number 7 times
Go back to settings>developer options>select usb debugging
Now connect phone to PC> there will be a prompt displayed on your phone select okay
ADB drivers will be installed. Thats it
Now you have ADB access
You can take a backup even when the phone is turned on via ADB
Click to expand...
Click to collapse
So if somehow i softbrick my phone there won't be any possible way to use adb ? =o

You can have ADB access if you put your phone in recovery mode (power+volume up+home button) even if the phone is soft bricked. But USB debugging should be enabled.
Satsana said:
So if somehow i softbrick my phone there won't be any possible way to use adb ? =o
Click to expand...
Click to collapse

androidtweaker1 said:
You can have ADB access if you put your phone in recovery mode (power+volume up+home button) even if the phone is soft bricked. But USB debugging should be enabled.
Click to expand...
Click to collapse
Thx a bunch ;3 again