Develop Bugs

[Q] Please help, stuck im ''Fasboot mode started''

Guys, I'm completely lost.
I rooted my phone, and tryed to use TWRP recovery.
Installed Android Studio Setup Wizzard, openned command window and typed ''adb shell'', ''su''...
But when I tried entering recovery mode to go into TWRP, my phone just got Stuck.
It says: ''Fastboot mode started''
''reset''
''portchange''
''reset''
''portchange''
then i decided to remove the usb cable from the phone and it said more things, now it says ''Fastboot: processing commands''
Even tried to remove the battery but nothing works.
I am a noob when it comes to Roms and flashing this and that, and I know i made a mistake by doing this. Could you guys send me a solution for this? Just want my phone back.
I'm using the LG G3 D855.

If it doesnt start normally into Android OS your phones a goner
Take it into your local service center and tell them the problem occurred while you were trying to apply the Lollipop OTA

D851 T-Mobile G3

Hoping someone can help me here.
My wife has a G3 that started acting up back in September or so. It would randomly turn off and reboot, usually while not even touching it. Did some looking around and found that the Facebook Messenger app could cause some instability. Removed the app, all was good for a couple of weeks before it started again. This time, we backed everything up, did a factory reset, all was good for about a week. Reboots started again so I did a hard reset from Recovery. Booted up, everything was good again for about a week again before the reboots started up. The wife ended up giving up on it and went back to her Galaxy S3.
I've been messing around with it today. Phone has been stuck in a boot loop at the LG logo. Battery is fully charged. I followed some guides and downloaded the V10c stock firmware TOT file, dated June 20th, 2014 and LGD851_20140611_LGFLASHv160.dll and loaded them up into LGFlashTool v1.8.1. Installed fresh LG drivers on my Win7 PC, followed the flashing instructions to the letter using a USB 2.0 port (as I read somewhere that 3.0 ports have caused issues on some devices). Everything flashes 100%, flash tool reads complete, phone shows a big 3 on the screen with a blue background. Unplug and reboot the device and it's right back to a boot loop at the LG logo.
Now at one point, during the flashing process, it would boot into LG MiniOS 3.1 and I was able to choose an option (chose Normal Boot) and it would go back into the boot loop. Also, I connected it to my Ubuntu machine just to see what would happen and I received an error "Unable to mount LGE Android Phone. Unable to open MTP device", which makes sense. However, the phone itself would get to the T-Mobile logo and briefly jump into the initial setup of the phone before jumping back to the LG logo and starting over again. Connecting back to my Win7 machine, it just boot loops unless I have the flash tool running. Not having USB connected, it just boot loops.
I'm at a loss here. I can usually muddle my way through these kind of things but this one has me completely stumped. Ordinarily, I wouldn't worry much about this but she's wanting to get a new phone through T-Mobile's JUMP program and we can't do that if the phone won't even boot.
Any help would be appreciated.

Valorendk said:
Hoping someone can help me here.
My wife has a G3 that started acting up back in September or so. It would randomly turn off and reboot, usually while not even touching it. Did some looking around and found that the Facebook Messenger app could cause some instability. Removed the app, all was good for a couple of weeks before it started again. This time, we backed everything up, did a factory reset, all was good for about a week. Reboots started again so I did a hard reset from Recovery. Booted up, everything was good again for about a week again before the reboots started up. The wife ended up giving up on it and went back to her Galaxy S3.
I've been messing around with it today. Phone has been stuck in a boot loop at the LG logo. Battery is fully charged. I followed some guides and downloaded the V10c stock firmware TOT file, dated June 20th, 2014 and LGD851_20140611_LGFLASHv160.dll and loaded them up into LGFlashTool v1.8.1. Installed fresh LG drivers on my Win7 PC, followed the flashing instructions to the letter using a USB 2.0 port (as I read somewhere that 3.0 ports have caused issues on some devices). Everything flashes 100%, flash tool reads complete, phone shows a big 3 on the screen with a blue background. Unplug and reboot the device and it's right back to a boot loop at the LG logo.
Now at one point, during the flashing process, it would boot into LG MiniOS 3.1 and I was able to choose an option (chose Normal Boot) and it would go back into the boot loop. Also, I connected it to my Ubuntu machine just to see what would happen and I received an error "Unable to mount LGE Android Phone. Unable to open MTP device", which makes sense. However, the phone itself would get to the T-Mobile logo and briefly jump into the initial setup of the phone before jumping back to the LG logo and starting over again. Connecting back to my Win7 machine, it just boot loops unless I have the flash tool running. Not having USB connected, it just boot loops.
I'm at a loss here. I can usually muddle my way through these kind of things but this one has me completely stumped. Ordinarily, I wouldn't worry much about this but she's wanting to get a new phone through T-Mobile's JUMP program and we can't do that if the phone won't even boot.
Any help would be appreciated.
Click to expand...
Click to collapse
Good afternoon, my recommendation is that flashes with lg flash tool 2015. All you need is your phone updated driver installed on your pc. Further, you need to download the KDZ (firmware of your stock rom) corresponding to your model. Look at the XDA thread as do or YouTube. If you need more help, you can consult here.

cesarandres_8911 said:
Good afternoon, my recommendation is that flashes with lg flash tool 2015. All you need is your phone updated driver installed on your pc. Further, you need to download the KDZ (firmware of your stock rom) corresponding to your model. Look at the XDA thread as do or YouTube. If you need more help, you can consult here.
Click to expand...
Click to collapse
IIRC, he's talking about going back to the latest stock firmware available from LG and flashing with with @quangnhut123's flash tool.

Thanks for both of your help on this. I actually had given up on the phone for a while. The last time I flashed, it was allowing me to get into the first time setup but wouldn't let me complete setup before rebooting. So I ordered a new battery and everything is working like it's brand new. Thanks again!

LG G4 H815 Euro - Troubles flashing stock ROM

Hello to all of you,
Thanks in advance for any help you can provide.
I bought second hand a LG G4 H815 with CyanogenMod 14 already installed on it.
Everything was fine until I installed my Ebanking apps, that would not function with an unlocked bootloader. I needed to return to a clean factory safe state...
It was the second time I flashed a rom in my whole life, the first one was a Galaxy S plus years ago.
I followed all the instructions for the KDZ flash in this tutorial but I stumbled upon a "Upgrade stopped due to error" in LG flash tool.
I retried 3 or 4 times but with no luck. I verified that the ROM was correct for my model and it was. European and all...
I tried LGUP but my phone is unknown ( at least it's detected)...
I read some posts and told myself "I probably have messed up something, let's try it again with a fresh thing"... I clicked on the factory reset button and carried on.
There the phone booted on TWRP (That i didn't know existed before this). As I explored the menus with a TWRP google search on the computer, I began to realize that the factory reset was maybe a bad thing to do with a custom rom. I tried to reboot but I always end up booting on TWRP.
I re-tried to flash in download mode, but with always the "Upgrade stopped due to error".
I also tried to flash directly from TWRP a stock rom. Didn't work.
I was beginning to lose it and tried to flash the CM14 version I had before, juste to have a working phone again, but even this didn't work... I'm stuck with a TWRP phone
I need some help there...

FamousCarpet said:
Hello to all of you,
Thanks in advance for any help you can provide.
I bought second hand a LG G4 H815 with CyanogenMod 14 already installed on it.
Everything was fine until I installed my Ebanking apps, that would not function with an unlocked bootloader. I needed to return to a clean factory safe state...
It was the second time I flashed a rom in my whole life, the first one was a Galaxy S plus years ago.
I followed all the instructions for the KDZ flash in this tutorial but I stumbled upon a "Upgrade stopped due to error" in LG flash tool.
I retried 3 or 4 times but with no luck. I verified that the ROM was correct for my model and it was. European and all...
I tried LGUP but my phone is unknown ( at least it's detected)...
I read some posts and told myself "I probably have messed up something, let's try it again with a fresh thing"... I clicked on the factory reset button and carried on.
There the phone booted on TWRP (That i didn't know existed before this). As I explored the menus with a TWRP google search on the computer, I began to realize that the factory reset was maybe a bad thing to do with a custom rom. I tried to reboot but I always end up booting on TWRP.
I re-tried to flash in download mode, but with always the "Upgrade stopped due to error".
I also tried to flash directly from TWRP a stock rom. Didn't work.
I was beginning to lose it and tried to flash the CM14 version I had before, juste to have a working phone again, but even this didn't work... I'm stuck with a TWRP phone
I need some help there...
Click to expand...
Click to collapse
uninstall any drive for g4 from pc and reinstall again and lgup. now reboot phone to download mode when lgup is open first check upgrade opsion and when open kdz check refurbish opsion and start. good luck

Thank you for your answer
Still no luck
Uninstalled drivers
Rebooted PC
Reinstalled the drivers
Still unknown device

The best way to flash stock image is to use official LG Bridge app. Download it, turn off your phone, connect it to PC while holding volume up button - phone will go into download mode. Then there is option for software restore in LG Bridge but i won't tell u where exactly. If it won't work i would try on another PC. If it won't work maybe you would be able to flash stock image trough send_command but i won't help you with it.

FamousCarpet said:
Thank you for your answer
Still no luck
Uninstalled drivers
Rebooted PC
Reinstalled the drivers
Still unknown device
Click to expand...
Click to collapse
open lgup torn off the phone press volume up insert usb cable wait to see download mode on phone release up button and see if everything go fine

Thank you a lot Avantu, the LG Bridge did the trick! I now have a factory rom!

I Bricked and Unbricked my day one V30 in one night (How to not be completly screwed)

I picked up my UK V30 H930 yesterday all fine and saw that LG have unlocked the bootloader on my model so I went ahead and tried it along with trying the alpha TWRP build
So I thought id write about what went wrong and how I recovered from it.
I made the mistake of letting the phone auto update to 10v software verion before I did this. As I had 10f on before when I bought the phone.
I went to load in all the software needed to unlock the bootloader and proceeded to do so but in my haste of the user data being wiped taking a longer then I thought it would I unpluged the phone to try "fastboot flash unlock unlock.bin" again . No such luck already unlocked. It booted back in fine so I thought everything was ok but that was the moment I thought could have caused my entire night to be ruined.
I thought with the bootloader saying it was unlock it was now fine to flash TWRP on now so went to do that and discovered it would no longer boot into the rom anymore coming up with the LG V30 Logo and just staying put. Thought it must be my 10v software version messing it up. Ok ill try to flash a 10f stock kdz. After about an hour or so of 'Finding my feet' with the phones boot methods for download mode, Fastboot and recovery I found that twrp was being strange with mounting the phone tried otherways eventually got the phone talking to the pc by using uppercut with LGUP and having the phone in download mode and the port com channel in device mananger set to com 41. After about 4 tries of flashing KDZ's to the phone it would just come with a "erasing" circle and proceed to get stuck on boot logo again so I messed about with .dlls and tried to other methods. Still nothing.
Now I tried LG Bridge's "Update error recovery" and I was actually talking to the phone for the 1st time so i let it do its thing which took well over an hour to download the kdz file. "Fine just work please". it got to the updating stage at 5% and froze and the phone being in download mode hadnt done a thing. I tried again but still nothing. Eventually now at 6am and having been up all night I went to give up but I manged to get it on to fastboot mode and by chance came across "flashing lock_bootloader" tried and it and it locked tthe bootloader back up (this thing of LG saying it cannot be undone must be rubbish?) now before I tried anything I rebooted the phone . IT BOOTED! onto the fresh 10v KDZ i had installed on it but before anything I wanted to see if it would now run with a unlocked bootloader on its own with no TWRP installed. It works! Now i just need a method of rooting but im now ready at least.
Hope this helps anyone with simular troubles.

Also had some trouble yesterday after trying out some Magisk modules.
On reboot it sometimes got stuck in the LG V30 screen, and sometimes even the bootanimation came up, but it didnt finish the boot lol
Only installed and adblock btw, and tried the Xposed module. Uninstalled that again btw. Now only using Adblock.
Phone also seems to need Power + Vol- to force shutdown for me, not only Power like other phones. Also didnt manage to find a way to boot into recovery when the phone is off, only found a way to get into the factory reset screen ?
sadly i dont have a working sdcard currently (my 3 year old 128GB one is read only for some reason, atleast changes dont get applied), so ill wait for a new one to mess around more ^^
Also working on a LOS14.1 build atm (it compiled, but didnt adapt all parts of thr device tree yet, and no idea if i have all vendor files lol)

SGCMarkus said:
Also had some trouble yesterday after trying out some Magisk modules.
On reboot it sometimes got stuck in the LG V30 screen, and sometimes even the bootanimation came up, but it didnt finish the boot lol
Only installed and adblock btw, and tried the Xposed module. Uninstalled that again btw. Now only using Adblock.
Phone also seems to need Power + Vol- to force shutdown for me, not only Power like other phones. Also didnt manage to find a way to boot into recovery when the phone is off, only found a way to get into the factory reset screen
sadly i dont have a working sdcard currently (my 3 year old 128GB one is read only for some reason, atleast changes dont get applied), so ill wait for a new one to mess around more ^^
Also working on a LOS14.1 build atm (it compiled, but didnt adapt all parts of thr device tree yet, and no idea if i have all vendor files lol)
Click to expand...
Click to collapse
Ive just managed to get 10f on so ill retry flashing twrp now.
Are you sure your sdcard doesnt have a little read/write switch on it . Im sure i remember so of them used to have one.

Dreamxtreme said:
Ive just managed to get 10f on so ill retry flashing twrp now.
Are you sure your sdcard doesnt have a little read/write switch on it . Im sure i remember so of them used to have one.
Click to expand...
Click to collapse
nope, doesnt have one. Neither windows nor Linux fail at writing on it, or when deleting files, but as soon as I re-insert the SDCard all changes are reversed. Formatting doesnt work anymore, unknown error. Tried that in Windows, Linux and in the Phone (Androids formatting crashed, TWRPs produced an error after it timed out)

I have hit a wall

Hello everyone, Merry Christmas!
Although I say that, I bring not so merry news. My OnePlus 7T is bricked and after trying everything I don't know where to go from here. Currently I am stuck at the:
The current image (boot/recovery) has been destroyed​phase of things and all I can do is boot into fastboot, that is it.
How did this all start? All I did was just update the phone to Android 12 with the official OTA update from OnePlus, big mistake. Worst update ever; my adaptive brightness went haywire, the brightness gets stuck at max, I couldn't receive calls, data was completely unresponsive, and the list goes on. So before the obvious downgrade method, I try a few things first:
Cycle airplane mode on/off
Reset network settings
Reset ANR
These worked for a minute on my data then right back to the same issue.
Wipe cache partition... Oh wait I had to find out the hard way Android 12 removed this option....
Wipe the phone
That fixed nothing.
Ok time to downgrade, but this is where things got tricky and I realized that maybe all my issues stemmed from me getting the wrong update from OnePlus? Although I found this out too late.
See my phone model is HD1907 which I already knew at the back of my head, but when it mattered to remember the most, I didn't catch what happened. After my update to A12, my model number changed to HD1901 which is the Indian version, and when I saw it didn't think anything of it at the time but then after all my problems it came back to me, my phone has always HD1907 so maybe this is a compatibility issue.
Anyway since I was going to downgrade anyway I thought to myself, 'since I already wiped everything, maybe I can use this opportunity to try out a ROM for A12 and see if it is just this ****ty OOS causing all these issues,' and so I did. First thing I did was unlock the bootloader, and try get TWRP on my phone. That all went fine, I booted into TWRP, flashed my zip for TWRP, then proceeded to try to boot into the OS... and the rest is history because that is as far as I got. Apparently my boot.img is destroyed and I can't boot back into TWRP anymore either, all I can do is get to fastboot.
So then I tried MSM, it won't detect my phone.... So then I tried flashing my Stock ROM through fastboot, apparently I'm missing a partition and it won't write to a critical partition either....
So where do I go from here...?

Hello I was in the exact same boat as you today same phone, same update issues, same no recovery mode, no os to boot into only greeted with fastboot mode. I have resolved it and I'm back on oos 11 good as new. I did use the msm tool it is tricky for sure at first. A critical step is installing the qualcomm drivers and then rebooting your pc. Get them here
https://androiddatahost.com/nbyn6. Be sure to reboot. It's late and I just got this thing back into working shape so I don't want to write a lot a right now. It's been a few days since this post so... If you are still stuck I will be glad to help out let me know. There is hope!

Canbeit said:
Hello I was in the exact same boat as you today same phone, same update issues, same no recovery mode, no os to boot into only greeted with fastboot mode. I have resolved it and I'm back on oos 11 good as new. I did use the msm tool it is tricky for sure at first. A critical step is installing the qualcomm drivers and then rebooting your pc. Get them here
https://androiddatahost.com/nbyn6. Be sure to reboot. It's late and I just got this thing back into working shape so I don't want to write a lot a right now. It's been a few days since this post so... If you are still stuck I will be glad to help out let me know. There is hope!
Click to expand...
Click to collapse
I too had all the symptoms after an update to OOS12, including progressively losing any semblance of booting. not even recovery and the drivers found elsewhere didn't work, and had a different name when installed and would never get detected in the MsmDownloadTool. After installing this one and rebooting, it finally detects it and installs the image of EDL mode.