Related
Hi guys.
My dad's phone is suddenly stuck in Fastboot mode, possibly bricked.
Warranty will cover it but unfortunately he has lots of pictures which was not backed up.
When started and connected to my PC the phone is stuck saying:
Fastboot mode started
EDIT: the phone was stock, not rooted.
-- reset--
-- portchange--
Windows detects it as "Android" Under Other devices in Device Manager.
I've tried to update the driver, downloading two different LG G3 drivers but this doesn't work.
Is there any way to backup data on the phone before handing it in?
Cheers
Simply, you need to do;
1- Install proper drivers for fastboot
2- Boot (not flash) a TWRP image for your device via fastboot
3- Install proper drivers for ADB
4- Simply type "adb pull /data/media" from command line
Warning: Do not try to copy files via MTP.
If you want to help from TeamViewer, just send an e-mail to here: [email protected]
Hello!
I attempted to modify some system files (overwriting mine with LG v10 ones supplied in this thread: http://forum.xda-developers.com/g4/themes-apps/help-bringing-lg-v10s-camera-to-g4-t3223371) and my device ended up not going past the first boot screen (where the "Bootloader unlocked!" message appears).
Some facts:
- I have the H815 variant
- I have tried the drivers that come with LG Bridge and some others found on this forum.
- I have (officially) unlocked my bootloader, voiding my warranty
- The device gets stuck on the first boot screen (the one with text "Bootloader unlocked!"), led starts pulsing blue a second later.
- Logcat from boot is located at: pasteb in.com/64RZ3SgJ
- I have TWRP, but the press combination ( vol-down + power-button key, release for 1 sec, press them again) to boot into it doesn't work.
- I had Android 6.0 installed using the zip flashing method from recovery - with root.
- It does get past the first boot screen when I connect the micro-usb cable and it figures it has enough juice to turn on itself, but doesn't get past the boot animation then.
- I can access Download mode
- I tried flashing H81520A_00.kdz with LG Flash Tool 2014 (both normal and CSE mode), but it says: "Required info cannot be found. Contact the system administrator". Device doesn't react.
- I tried flashing older Europe Open H81510D.kdz with LG Flash Tool 2014, but it says: "Upgrade stopped due to an error." and wants me to try again (which didn't help). This message comes after a few seconds of attempting an upgrade to which my phone actually reacts - some text changes in download mode log box.
- (I did use LG Flash Tool 2014 in CDMA - DIAG mode)
- I tried using LG Update Recovery tool in LG Bridge. A similar error appeared making me retry the process, which doesn't work as well.
- Running any fastboot command yields in message: "< waiting for device >"
Please provide me with assistance as I've found other people with similar errors as well (even though their devices aren't bricked yet)
Edit 1: I discovered I had a short time window of ADB access after booting. I used the command "adb reboot recovery" and got into recovery mode. Will try to reflash system files.
Edit 2: Problem solved. Android booted up normally after reflashing the files. Gosh this was nerve-racking. Somebody should make a tutorial out of this.
Edit 3:
I was asked to write a more clear procedure, so here's my attempt. It is better than nothing. Again I suggest someone try to write a better explanation and verify that it works on other devices as well.
1. Have adb installed on your computer
2. Have the necessary drivers installed on your computer. I think I used these: http://tool.xcdn.gdms.lge.com/dn/downloader.dev?fileKey=UW00120120425
3. Have your phone turned completely off.
4. Test if adb works from the console, using the following command: "adb version"; if it doesn't google for how to add adb to system environment path.
5. Connect the computer and the device using a micro-usb cable. The device should detect that it is being charged and turn itself on, thinking that it has enough battery to do so. If it doesn't, do so yourself.
6. While the device is booting, you have (at least I had) a short time period while your device listens for commands. In console type the following command: "adb reboot recovery" (try this from immediately after the device starts booting until it works, if it doesn't try again). This should reboot your into recovery mode.
7. If you do not have system flashables on your device, google how to sideload zip files. Get them here: http://forum.xda-developers.com/g4/development/stock-h815-20a-stock-images-kdz-t3232282. Flash them (I flashed all, just in case, but system might be enough).
8. After flashing, you (if coming from any other rom) should clear data and cache as well.
9. Reboot the device and it should be working.
with flashtool impossible to rollback . and impossible to flash kdz 6.0... a lot of people with this issue
Somehow I managed to make adb recognize the device and provide me with logcat access. I posted the contents on pastebin: pasteb in.com/64RZ3SgJ
Edit: Problem solved. Description in 1st post.
gregor.eesmaa said:
Somehow I managed to make adb recognize the device and provide me with logcat access. I posted the contents on pastebin: pasteb in.com/64RZ3SgJ
Edit: Problem solved. Description in 1st post.
Click to expand...
Click to collapse
Could you write clear, detailed procedure ...
well thank you
---------- Post added at 09:05 PM ---------- Previous post was at 09:01 PM ----------
I have the same problem, I do not know how to go back
rotoko said:
Could you write clear, detailed procedure ...
well thank you
---------- Post added at 09:05 PM ---------- Previous post was at 09:01 PM ----------
I have the same problem, I do not know how to go back
Click to expand...
Click to collapse
There you go. Can't do any better as I am not an expert in how Android precisely works at this level.
have followed what you ahd done i.e try adb reboot recovery and can net get adb to find device
will try again later as not very well learned in android
uk h815
leegreggs said:
have followed what you ahd done i.e try adb reboot recovery and can net get adb to find device
will try again later as not very well learned in android
uk h815
Click to expand...
Click to collapse
Perhaps you should try running the command: "adb devices" to see whether it has connected until it has (just run it multiple times). Otherwise, are you experiencing same symptoms as me? Did you also overwrite the system with V10 files? I'm thinking that the time window was caused by the system attempting to read some media profiles while starting all the other processes behind.
gregor.eesmaa said:
Perhaps you should try running the command: "adb devices" to see whether it has connected until it has (just run it multiple times). Otherwise, are you experiencing same symptoms as me? Did you also overwrite the system with V10 files? I'm thinking that the time window was caused by the system attempting to read some media profiles while starting all the other processes behind.
Click to expand...
Click to collapse
No I've decided to go back to my LG g2 till either flashtool gets updated or till a tot & dll comes out
gregor.eesmaa said:
Hello!
I attempted to modify some system files (overwriting mine with LG v10 ones supplied in this thread: http://forum.xda-developers.com/g4/themes-apps/help-bringing-lg-v10s-camera-to-g4-t3223371) and my device ended up not going past the first boot screen (where the "Bootloader unlocked!" message appears).
Some facts:
- I have the H815 variant
- I have tried the drivers that come with LG Bridge and some others found on this forum.
- I have (officially) unlocked my bootloader, voiding my warranty
- The device gets stuck on the first boot screen (the one with text "Bootloader unlocked!"), led starts pulsing blue a second later.
- Logcat from boot is located at: pasteb in.com/64RZ3SgJ
- I have TWRP, but the press combination ( vol-down + power-button key, release for 1 sec, press them again) to boot into it doesn't work.
- I had Android 6.0 installed using the zip flashing method from recovery - with root.
- It does get past the first boot screen when I connect the micro-usb cable and it figures it has enough juice to turn on itself, but doesn't get past the boot animation then.
- I can access Download mode
- I tried flashing H81520A_00.kdz with LG Flash Tool 2014 (both normal and CSE mode), but it says: "Required info cannot be found. Contact the system administrator". Device doesn't react.
- I tried flashing older Europe Open H81510D.kdz with LG Flash Tool 2014, but it says: "Upgrade stopped due to an error." and wants me to try again (which didn't help). This message comes after a few seconds of attempting an upgrade to which my phone actually reacts - some text changes in download mode log box.
- (I did use LG Flash Tool 2014 in CDMA - DIAG mode)
- I tried using LG Update Recovery tool in LG Bridge. A similar error appeared making me retry the process, which doesn't work as well.
- Running any fastboot command yields in message: "< waiting for device >"
Please provide me with assistance as I've found other people with similar errors as well (even though their devices aren't bricked yet)
Edit 1: I discovered I had a short time window of ADB access after booting. I used the command "adb reboot recovery" and got into recovery mode. Will try to reflash system files.
Edit 2: Problem solved. Android booted up normally after reflashing the files. Gosh this was nerve-racking. Somebody should make a tutorial out of this.
Edit 3:
I was asked to write a more clear procedure, so here's my attempt. It is better than nothing. Again I suggest someone try to write a better explanation and verify that it works on other devices as well.
1. Have adb installed on your computer
2. Have the necessary drivers installed on your computer. I think I used these: http://tool.xcdn.gdms.lge.com/dn/downloader.dev?fileKey=UW00120120425
3. Have your phone turned completely off.
4. Test if adb works from the console, using the following command: "adb version"; if it doesn't google for how to add adb to system environment path.
5. Connect the computer and the device using a micro-usb cable. The device should detect that it is being charged and turn itself on, thinking that it has enough battery to do so. If it doesn't, do so yourself.
6. While the device is booting, you have (at least I had) a short time period while your device listens for commands. In console type the following command: "adb reboot recovery" (try this from immediately after the device starts booting until it works, if it doesn't try again). This should reboot your into recovery mode.
7. If you do not have system flashables on your device, google how to sideload zip files. Get them here: http://forum.xda-developers.com/g4/development/stock-h815-20a-stock-images-kdz-t3232282. Flash them (I flashed all, just in case, but system might be enough).
8. After flashing, you (if coming from any other rom) should clear data and cache as well.
9. Reboot the device and it should be working.
Click to expand...
Click to collapse
:crying::crying: i forget to enable usb debugging, now my pc can not connect to phone under downloadmode. And i can not use adb to let it reboot bootloader.
I think my dev is bricked for good. I used twrp and was not careful and wiped system. Now I cannot get into fastboot anymore and recovery does not work. It never shows up on USB. If I enter recovery, select yes to delete, it does nothing, just reboots with LG logo..
rav0r said:
I think my dev is bricked for good. I used twrp and was not careful and wiped system. Now I cannot get into fastboot anymore and recovery does not work. It never shows up on USB. If I enter recovery, select yes to delete, it does nothing, just reboots with LG logo..
Click to expand...
Click to collapse
I'm having the same problem. I wiped the device ready to install a new Rom and TWRP crashed. No adb or fastboot and it only loads onto the LG flash screen. There must be a way to do it as it's software problem, not hardware problem. How do they get the software onto the handset when first made, that's what I need I feel.
AndHD2 said:
I'm having the same problem. I wiped the device ready to install a new Rom and TWRP crashed. No adb or fastboot and it only loads onto the LG flash screen. There must be a way to do it as it's software problem, not hardware problem. How do they get the software onto the handset when first made, that's what I need I feel.
Click to expand...
Click to collapse
Same here, only a software issue. I cannot boot to download mode, and my device is locked.
Sometimes it might have happened to you that you have erased your download mode while doing some fun with adb commands and enjoying android development with starter knowledge. In this process you unfortunately destroyed your download mode.
Now you want to go back to stock but your download mode is not appearing only a fastboot mode opening saying some very tensed and confusing things to understands. This is the situation where you are totally messed up and out of mind. Don't know what to do. Tried whole of internet and can't find a solution. Now method is working and you want a fix. Then this thread is gonna help you a lot. You will be very happy to read instructions here cause they are easy and also phone saving too. These instructions can even save your amount to be given to a repairing shop.
So a lot of introduction is done, let's proceed to the process. First of all read disclaimer to avoid any misunderstandings of future.
Code:
Your warranty is void now. I am not responsible for any mistake and wrong thing happens to your device. Always try if you have a good knowledge of that.
These steps are not an official LG and therefore not endorsed by LG Electronics in any way. As such, this is a 'try-at-your-own-risk' approach. Please make sure to back up your important files when trying this for the first time. I take no responsibility for any undue outcomes resulting from the use of these steps and instructions. And all the best for step.
Things you Need:
1: LG united mobile drivers here. (Skip you have already)
2: adb & Fastboot drivers from here. (To do flashing commands). Minimal Edition.
3: Make sure "USB debugging" is on for you LG G3 device. If not sure check here.
4: laf.img for your device . (Download mode image). Most important thing
Download it from here according to your device variant like as d850, d855 or etc.
Select your variant > Stock partitions > 10D > laf.img ( I prefer 10d laf.img you are welcome to try other ).
5: LG G3 device in fastboot mode by connecting to PC while phone is powered off pressing volume up(+) button.
6: And the most important thing a computer. (I tried it on Windows 10 but will work on 7,8 and others too.
Steps:
1: Install LG united mobile drivers.
2: Install "adb and fastboot mode" drivers. Copy "laf.img" to the directory where you installed them and run "MAF32.exe"
Mine is "C:\Program Files (x86)\Minimal ADB and Fastboot"
3: Connect your LG G3 device while in fastboot mode.(Make sure drivers are installed).
4: Check if connection is right by doing this command
Code:
fastboot devices
5: If you done right your device might appear. (Sometimes as a question mark too)
6: To flash download mode. Execute these commands in sequence.(Make sure "laf.img" is copied to that folder where you installed the adb and fastboot drivers and is named as "laf.img").
Code:
fastboot erase laf
fastboot flash laf laf.img
fastboot reboot
7: Pull battery of your device and reboot into download mode again if flashing is successful. Download mode might appear as original. If not then you might have not listened to instructions. (If still stuck ask in comments).
If i helped you anyhow press "Thanks"
All the best with process.
Credits:
Autoprime for the stock partitions.
shimp208 for minimal ADB and fastboot drivers.
And all others who gave some ideas, drivers and tools for that method to work.
in adb commands appears waiting for device along time and no thing happened ..... plz
dksoni411 said:
Sometimes it might have happened to you that you have erased your download mode while doing some fun with adb commands and enjoying android development with starter knowledge. In this process you unfortunately destroyed your download mode.
Now you want to go back to stock but your download mode is not appearing only a fastboot mode opening saying some very tensed and confusing things to understands. This is the situation where you are totally messed up and out of mind. Don't know what to do. Tried whole of internet and can't find a solution. Now method is working and you want a fix. Then this thread is gonna help you a lot. You will be very happy to read instructions here cause they are easy and also phone saving too. These instructions can even save your amount to be given to a repairing shop.
So a lot of introduction is done, let's proceed to the process. First of all read disclaimer to avoid any misunderstandings of future.
Code:
Your warranty is void now. I am not responsible for any mistake and wrong thing happens to your device. Always try if you have a good knowledge of that.
These steps are not an official LG and therefore not endorsed by LG Electronics in any way. As such, this is a 'try-at-your-own-risk' approach. Please make sure to back up your important files when trying this for the first time. I take no responsibility for any undue outcomes resulting from the use of these steps and instructions. And all the best for step.
Things you Need:
1: LG united mobile drivers here. (Skip you have already)
2: adb & Fastboot drivers from here. (To do flashing commands). Minimal Edition.
3: Make sure "USB debugging" is on for you LG G3 device. If not sure check here.
4: laf.img for your device . (Download mode image). Most important thing
Download it from here according to your device variant like as d850, d855 or etc.
Select your variant > Stock partitions > 10D > laf.img ( I prefer 10d laf.img you are welcome to try other ).
5: LG G3 device in fastboot mode by connecting to PC while phone is powered off pressing volume up(+) button.
6: And the most important thing a computer. (I tried it on Windows 10 but will work on 7,8 and others too.
Steps:
1: Install LG united mobile drivers.
2: Install "adb and fastboot mode" drivers. Copy "laf.img" to the directory where you installed them and run "MAF32.exe"
Mine is "C:\Program Files (x86)\Minimal ADB and Fastboot"
3: Connect your LG G3 device while in fastboot mode.(Make sure drivers are installed).
4: Check if connection is right by doing this command
Code:
fastboot devices
5: If you done right your device might appear. (Sometimes as a question mark too)
6: To flash download mode. Execute these commands in sequence.(Make sure "laf.img" is copied to that folder where you installed the adb and fastboot drivers and is named as "laf.img").
Code:
fastboot erase laf
fastboot flash laf laf.img
fastboot reboot
7: Pull battery of your device and reboot into download mode again if flashing is successful. Download mode might appear as original. If not then you might have not listened to instructions. (If still stuck ask in comments).
If i helped you anyhow press "Thanks"
All the best with process.
Credits:
Autoprime for the stock partitions.
shimp208 for minimal ADB and fastboot drivers.
And all others who gave some ideas, drivers and tools for that method to work.
Click to expand...
Click to collapse
mero_enriqi said:
Click to expand...
Click to collapse
That can happen because
1: USB debugging is off on your device
2: Drivers are not installed properly
Proper fixes
1: Turn on usb debugging.
2: Install driver again or try the procedure on some other computer
(If you can get a computer running Windows 7 32-bit that would be a good choice)
im stuck at firmware update. every time i restart my phone theres no download mode and directly go to firmware update. how can i back download mode? i cant open my phone to on the debug setting
Fastboot doesnt work
Hi there
I hardbricked my phone while reinstalling stock rom when my laptop crashed. Afterwards adb and download mode wouldn't start, only thing now is fastboot.
I tried your solution, but it doesn't seems to be working. The device is showing in CMD (fastboot devices) but further commands arent accepted, they show up at the G3 screen, but afterwards nothing happens. What can i do (I really don't want to try the "short-circut - Qualcom" method).
Drivers and so on are properly installed
Thanks in advance
Can't get to download mode!
I did everything as instructed and the flashing was successful...
But whenever I want to go to download mode, it just shows download mode icon and then goes straight to fastboot!
How can I fix this?
Lg G3 D851 10c here, trying this method after trying to flash magisk and got stuck with Fast boot mode. its been stuck on "erasing 'laf' ..." for a very very long time.
thanx..............work perfect lg d851 10c
Hi, Dev /..
Mine is lg ge d851 10f
What Shoud i flash to install recovery and boot into recovery to flash roms. kindly help me ASAP...:fingers-crossed:
hi mine is d85110f . which laf.img shoud i flash kindly help
booting to download mode
in adb type
PHP:
adb reboot bootloader
this should get you to download mode......
if you try
PHP:
adb reboot fastboot
or VOL UP+USB
you cannot enter download mode
if you are on a custom rom.
The phone will just reboot.
However
PHP:
adb reboot bootloader
seems to do the trick.
Also I am on LG G3 D858HK with mokee rom 7.1
and this works for me.
twrp working but unable to mount storage.
download mode showing but its not detect.
fastboot mode not working
tried everything change file system etc
Hi, I got my LG G3 to work on Lineage but now I would like to flash back to stock using the LG Flash Tools. This doesn't work. Seemingly the reason is that the device doesn't show up as Android Device in the Windows device manager. Can anyone give me a hint on how to proceed?
Cheers
Does "fastboot devices" recognize your phone. If yes.. then maybe you can download the stock file and run the relevant fastboot commands. I have a moto e phone which was not getting recognized by windows and https://forum.xda-developers.com/showthread.php?t=2759495 (step 3) worked for me. I am not aware of the exact commands for LG G3.
Regrettably no. Only thing that happens is that the USB-Storage mounts with an "image" and a "verinfo" folder.
Hi,
Here is fix for those, who have problem with bootloop on 5X with locked bootloader and OEM unlock disabled.
This tutorial works for Beta Android O bootloop too.
You will need:
ADB + drivers installed: https://forum.xda-developers.com/showthread.php?t=2588979
Nexus toolkit: DL.- http://www.wugfresh.com/nrt/
STOCK image archive, older than you have now - https://developers.google.com/android/images#bullhead
Latest OTA image archive : https://developers.google.com/android/ota#bullhead
-------------------
Extract stock image (NOT OTA)
install Nexus toolkit and restart your phone in Bootloader mode
connect phone to pc.
In nexus toolkit click on : advanced utilities > launch
look at: fastboot flash
screen: https://postimg.org/image/kkk9h92oz/
click on all buttons and flash all partition files from extracted archive - except recovery ,userdata and cache.
Copy downloaded OTA ROM archive in ADB folder.
reboot in recovery
now select apply update from adb.
open ADB
flash latest OTA package via command : adb sideload <packagename>.zip
I hope, this tutorial is useful for you, if yes, please hit thanks button.
And sorry for my english.
GREAT!!! Saved my phone. Thank you very much!
I've run into the issue by running the Factory reset from the Settings on my Nexus 5x and ran into this bootloop, is there a way to get this fixed if I didn't have USB debugging on? As I was just plain Factory reseting my phone.
I am getting this error when trying to sideload OTA via adb command
adb server version (32) doesn't match this client (39); killing...
* daemon started successfully *
falling back to older sideload method...
terminate called after throwing an instance of 'std::bad_alloc'
what(): std::bad_alloc
Nevermind I was doing it wrong. It is fixed now. Thanks for the guide.
Ins1d3r said:
I've run into the issue by running the Factory reset from the Settings on my Nexus 5x and ran into this bootloop, is there a way to get this fixed if I didn't have USB debugging on? As I was just plain Factory reseting my phone.
Click to expand...
Click to collapse
You not need usb debugging enabled in system.
Communication with pc is working in fastboot and recovery.
Redmi Note 3 - Tapatalk
any idea how to do it in mac?
What do you mean with: "Copy downloaded OTA ROM archive in ADB folder."
Just sideloading doesn't work.
ADB cant find my 5x...
Thank you OP for this i am need of help and it appears your solution has found me. Im on holiday atm and my nexus 5x just got the dreaded bootloop! Alll i see is the spinning colors for android logo after pin code is inputted.
Im very anxious to backup my photos of my son and family, so want to ask is this method safe? I dont want to risk losing data.. i can get into recovery mode and my phone is boot locked and not rooted, so can someone also tell me if adb backup will allow me to backup my pictures and video reliably? I will do a full backup and then try and flash the OTA.
serving: 'bullhead.zip' (~47%) * failed to read command: No error , what im doing wrong ?
ok succeed after dozen attempts , phone booted to main desktop work for like 5 mins and then frozen , looks like it went back to bootlooping ;(
Hi guys, same situation, since yesterday I could boot with a bit of effort (like waiting 15 minutes of bootloop) but now the 5x doesn't boot at all and so neither in recovery. My phone is locked and never modded so I will send in warranty when I will be back home ( 10 days). So now I would like to fix it to use it at least in this week, but how can I do if I can't boot in recovery?
I can just boot in the bootloader so use fastboot command...if I unlock the bootloader I will get the little lock in the bottom part of the screen, when I will lock it to send it to LG will it disappear?
How exactly is this toolkit's fastboot flashing supposed to work if you have a locked bootloader?
How is using this toolkit any different from running the "flash-all.bat" that's included with factory images?
This did nothing at least in my case.
I get the feeling that the flash operations are failing and the toolkit just disregards this.
Cannot enter recovery
I completed the first step in fastboot but when i try to enter recovery it goes to bootloop again....what should i do?
Nope, not working. Rebooting again and again. Issue not resolved. Please help!
Hi I need help,
what do i choose when i click 'system' tab?
[/QUOTE]
rockhardy said:
I am getting this error when trying to sideload OTA via adb command
adb server version (32) doesn't match this client (39); killing...
* daemon started successfully *
falling back to older sideload method...
terminate called after throwing an instance of 'std::bad_alloc'
what(): std::bad_alloc
Nevermind I was doing it wrong. It is fixed now. Thanks for the guide.
Click to expand...
Click to collapse
Hi,
I'm having the same problem.
Cannot enter recovery since the device just stays in bootloop, and I get the same message error if I try to sideload.
What were you doing wrong and how did you fixed it?
Tks
jcfortunato said:
Hi,
I'm having the same problem.
Cannot enter recovery since the device just stays in bootloop, and I get the same message error if I try to sideload.
What were you doing wrong and how did you fixed it?
Tks
Click to expand...
Click to collapse
It's been a while since I tried it. But as far as I remember it was due to phone not being in recovery mode. I hold the power button until the phone screen went off. And while holding the power button I instantly pressed volume down button to bring back the fastboot mode and then recovery mode.
i'm sorry but i don't see my latest build (currently running on 7.1.2)
i've tried using 'any build', it said that i have to choose one of the build listed :/
thank you
-----
edit
found them!
but it says that my OTA is out ouf date
I downloaded the latest one though (August)
where did I go wrong? :/
Anyone still doing this ha? I've just run into this issue with my wife's phone, and there are things on there she needs..
The ones with issue with the big cores causing bootloops, use this guide to unlock device then proceed with following guide
https://forum.xda-developers.com/showthread.php?t=3641199
Sent from my Nexus 5X using Tapatalk
Hello, I've done all the procedure until reboot recovery, but I've didn't find the button for select apply update from adb in NRT.