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.
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]
Hi guys,
So my lg g3 was running on cyanogen 13.0 and then i updated to one nightly which was not so good (freezing all the time).. i tried to rollback but somehow I ended up with my phone bricked..
I cannot go into twrp, i just see the fastboot console. I am able to execute some commands from my computer but even tough i installed the device drivers from lg's website i cannot get the phone recognised by the adb.
it's weird because i can execute fastboot reboot, but i cannot execute fastboot pull /media.
Can someone please point me to a solution in order to recover my data and be able to go into recovery mode.
Thanks in advance.
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
A little background info...
I bought a used Nexus 5x and received it running the stock rom with the bootloader unlocked. Not sure if the device was properly unrooted and returned to stock. It was running 7.1.2 out of the box. Also, I took the latest security update a few days ago, before attempting to root. I wanted to do some homework on the device before attempting root. It's been a while since I rooted a device. And wanted to refresh my memory.
When I began the process, I was having trouble getting my windows 7 PC (64) to recognize the device via adb. I did a little reading and found out my driver's needed to be updated. After I updated them the device could now be recognized in adb (yes, I did remember to enable USB debugging). Verified working by returning serial number after typing the adb devices command. So I was confident I could no proceed with flashing TWRP via fastboot.
The problem...
So now that I verified adb working and talking to my device I then typed adb reboot bootloader to access the bootloader (cause I honestly didn't want to disconnect the device and have to press buttons). The device successfully booted into the bootloader. My next step was to type fastboot devices in the command line but this is where the problem I'm having is. The device is not recognized. So I unplugged the device from the PC, opened a new command window in the platform-tools folder where fastboot resides, rebooted the device back into the bootloader, reconnected the device to the PC and attempted the fastboot devices command again and nothing, no device. I execute the command fastboot flash recovery TWRP.xx.xxxx.img and the command window says waiting for device or something like that. I am not sure what steps to take next. I've never had a problem getting a PC to recognize a device in bootloader mode before. I am pretty sure my environments are set up correctly. Is it something with the device? Is there a way to correct this? I'm really lost as to what to do here. I cannot root because I cannot flash custom recovery because I cannot get my PC to recognize the device in fastboot. Please, any help is appreciated. I'm stumped.
Update.
Resolved. Used a different pc with a fresh adb environment. Worked on the first try to flash twrp and super su.
ADB command not recognized
Hi there, i'm facing a similar problem. My 5x went into bootloop. It was on stock. After going through XDA posts, I was preparing to flash stock rom once again to see if that works. So I installed in my Windows 10 - SDK tools / platform. We I used command for ADB the command prompt say device listed, but does not come up with serial number. But when fastboot command is given, it returns with a serial number.
My question is what went wrong? My PC also dose not shows 5x in the explorer, despite installing drivers.
I would also like to know how to enable USB debugging when your phone is bricked?
Looking forward to any suggestions.....thanks upfront....
Hello everyone.
Yesterday I bricked my Xiaomi Redmi Note 8 Pro, and today I managed to unbrick it without requiring anything special (no need for a Authorized Service Account).
I use Linux, so the scripts inside the Stock ROM end with the .sh file extension. If you're using Windows, use the .bat files.
Phone:
Xiaomi Redmi Note 8 Pro 128GB - Begonia (with NFC).
Bricked state:
Constant boot loop;
No access to bootloader;
No access to system;
Access to fastboot.
Phone requirement:
You must be able to load fastboot mode.
PC requirements:
1. You'll need adb tools (SDK Platform-Tools) to communicate with your phone. Official link is below;
2. Download and unpack the Stock ROM linked below.
Instructions:
1. You need to make sure your phone has some power in it;
2. Unpack the Stock Rom and enter its folder (begonia_global_images_V10.4.2.0.PGGMIXM_20191024.0000.00_9.0_global);
3. Put your phone into fastboot mode (Key Combo: Hold the Power button + Volume Down button until the fastboot logo appears);
4. Connect your phone to your PC;
5. Run the flash_all.* scripts according to your operating system:
5.1. Linux: "./flash_all.sh";
5.2. Windows (untested; I'm not using Windows): Run "flash_all.bat" (How to Run a BAT File on Windows);
6. Wait something between 5min to 10min. It's quite fast, and the flashing process is verbose enough.
7. Profit.
F.A.Q.:
1. How did you find this?
Well, none of the unbrick methods in the forum were working, except for the Authorised Service Account one which I didn' t test. I desperately wanted to unbrick my phone by myself, and I thought that it couldn't get worse (it could with a completely blank screen, but I got away with it).
2. Where did you get the Stock ROM from?
I can't remember. It likely was from a xda forum post but I'm unsure. If I can find the original post containing the Stock ROM I used I'll write it here.
3. Which Miui and Android version did you have prior to the brick?
MIUI Global 11.x + Android 9.
4. Which Miui and Android version does the Stock ROM you installed have?
MIUI Global 10.4.2 + Android 9.
5. Can I install any Stock ROM?
As long as it's compatible with your phone version, yes. I recommend not installing a Android 10 Stock ROM because of this: https://forum.xda-developers.com/showpost.php?p=82743011&postcount=3
6. What if can't enter fastboot mode (phone screen in dead blank)?
You won't be able to unbrick your phone using this method. It is worth trying to enter fastboot mode even though your phone has a dead screen, because fastboot might be working anyway (you'll have to test this yourself, as in trying to load fastboot with a blank screen). Read the next question.
7. How can I test if fastboot mode is working?
"adb devices" returns nothing;
"fastboot devices" returns your device (proof it works). Since "fastboot devices" finds your device, you can run the appropriate scripts.
8. What about your Mi Unlock Status before and after the brick?
Before: Unlocked.
After: Unlocked (I thought it would lock the bootloader again, but it didn't).
9. My phone is bricked and I don't know how much battery my phone has left. What should I do?
You should let it turn off due to 0% battery and charge it fully. I do not recommend you flash like I did, without knowing how much battery I had (yes, I took my chances there). As far as I know, any phone in fastboot mode does not charge its battery.
10. Why is fastboot working in your case?
I don't know. I suspect flashing the preloader and the lk from this OP Redmi Note 8 Pro - The Megathread helped, but it's just a hunch.
11. Will you attempt to flash a Custom ROM again?
After taking a break, yes.
12. Is this phone now unbrickable?
As long as fastboot mode works, perhaps. More feedback is required.
Files:
SDK Platform-Tools (adb/fastboot): https://developer.android.com/studio/releases/platform-tools
Stock ROM used: http://bigota.d.miui.com/V10.4.2.0.PGGMIXM/begonia_global_images_V10.4.2.0.PGGMIXM_20191024.0000.00_9.0_global_270117fdb2.tgz
Feedback:
Due to my job I'm currently very short on time during the week to follow this thread, so it would be immensely helpful to have your feedback on this procedure.
Feedback from people who's phones are bricked with blank screens would be very appreciated, specifically if they can enter fastboot mode without any visual cues from their phones. If any bricked state allows fastboot mode, it seems this phone is easily unbrickable.
Thanks:
strongst for his understanding and in reopening this thread.
Compass.
Thread open again
strongst
Forum Moderator
Hi there,
Is there anyway to fix the hardbrick without the authorized account?? If not how can i find someone to do this for me?
andrewff2 said:
Hi there,
Is there anyway to fix the hardbrick without the authorized account?? If not how can i find someone to do this for me?
Click to expand...
Click to collapse
Yes, if you can access fastboot mode in your phone like I mentioned above. If hardbrick means loss of access to fastboot mode/recovery/system/basically everything, you'll need to find some other unbrick method.
If fastboot mode is working for you, you can unbrick your device by yourself with nothing else than the fastboot command and the Stock ROM. No need for any extra tools/programs.
inb4: The fastboot command is in the SDK Platform-Tools package I linked in the OP.
Compass.
Compass Linux said:
Yes, if you can access fastboot mode in your phone like I mentioned above. If hardbrick means loss of access to fastboot mode/recovery/system/basically everything, you'll need to find some other unbrick method.
If fastboot mode is working for you, you can unbrick your device by yourself with nothing else than the fastboot command and the Stock ROM. No need for any extra tools/programs.
inb4: The fastboot command is in the SDK Platform-Tools package I linked in the OP.
Compass.
Click to expand...
Click to collapse
Yeah i tried this method but fastboot cannot even detect device
andrewff2 said:
Yeah i tried this method but fastboot cannot even detect device
Click to expand...
Click to collapse
That's a shame.
It's worth trying different USB ports, cables etc.
I usually enter fastboot mode first and only then I connect the phone to my PC.
Then "./fastboot devices" and my phone is listed.
Compass.
Compass Linux said:
Yes, if you can access fastboot mode in your phone like I mentioned above. If hardbrick means loss of access to fastboot mode/recovery/system/basically everything, you'll need to find some other unbrick method.
If fastboot mode is working for you, you can unbrick your device by yourself with nothing else than the fastboot command and the Stock ROM. No need for any extra tools/programs.
inb4: The fastboot command is in the SDK Platform-Tools package I linked in the OP.
Compass.
Click to expand...
Click to collapse
Yeah i tried this method but fastboot cannot even detect device in windows appear com5 in Windows but fastboot do nothing just white led that blinks
andrewff2 said:
Yeah i tried this method but fastboot cannot even detect device in windows appear com5 in Windows but fastboot do nothing just white led that blinks
Click to expand...
Click to collapse
I can't give support in this area, but do you have the proper Windows drivers installed?
If you do and it still doesn't work, try a different computer. If you can use a Linux machine somehow it's worth trying. With Linux I didn't need to install anything besides the SDK Platform-Tools package to communicate with my phone.
I think you can unbrick your phone, because fastboot mode is loading (if it's loading it should reply to fastboot commands).
Compass.
Compass Linux said:
I can't give support in this area, but do you have the proper Windows drivers installed?
If you do and it still doesn't work, try a different computer. If you can use a Linux machine somehow it's worth trying. With Linux I didn't need to install anything besides the SDK Platform-Tools package to communicate with my phone.
I think you can unbrick your phone, because fastboot mode is loading (if it's loading it should reply to fastboot commands).
Compass.
Click to expand...
Click to collapse
Thanks for the help man but no the only thing is the white led that sometimes blink nothing more no vibration no sound no screen nothing.....
I'm trying to find someone who can help me with this but no one responds... sad
andrewff2 said:
Thanks for the help man but no the only thing is the white led that sometimes blink nothing more no vibration no sound no screen nothing.....
I'm trying to find someone who can help me with this but no one responds... sad
Click to expand...
Click to collapse
It seems the only solution for you is this (for now): [GUIDE] [begonia] UNBRICK - stuck on DA mode / Authorised Service Account required
Which you've probably read already.
I think you either do that or wait to see if another unbrick method appears.
Compass.
I have the same problem as yours and tried your solution but after i run flash_all.bat it just opens and closes in a split-second and i have no idea whether it works or not. Should I wait a couple of minutes or just try again?
advan93 said:
I have the same problem as yours and tried your solution but after i run flash_all.bat it just opens and closes in a split-second and i have no idea whether it works or not. Should I wait a couple of minutes or just try again?
Click to expand...
Click to collapse
That's not normal.
What you should see are various files being flashed along with their progress meter.
I'm assuming you're double clicking the .bat file. Instead of doing that, open a CMD Prompt and use that instead.
Compass.