Warning: This will delete all your data. You'll also see a large warning every time you turn on the device (attached), this disappears in less than a second.
Turn on developer mode
Turn on OEM unlock and USB debugging
Install LG drivers
Windows: http://tool.lime.gdms.lge.com/dn/downloader.dev?fileKey=UW00120120425
Mac: http://tool.lime.gdms.lge.com/dn/downloader.dev?fileKey=UW00320110909
Type adb devices and authorize your computer on the phone
Type adb reboot bootloader
Type fastboot devices and make sure your phone shows up
Type fastboot oem unlock
Type fastboot getvar all
Should say (bootloader) unlocked:yes
Type fastboot reboot
What's the purpose for an Unlock bootloader?
bhagiratha said:
What's the purpose for an Unlock bootloader?
Click to expand...
Click to collapse
It's the first step to rooting. If you plan to root, wiping your data now may be preferable.
bhagiratha said:
What's the purpose for an Unlock bootloader?
Click to expand...
Click to collapse
At this point, nothing. It's a prelude to rooting.
When I type in fastboot oem unlock, I get < waiting for any device >
And it waits, forever. (well, ok, like 15 minutes until I get impatient and pull the battery)
I'm on windows 10, installed the drivers from this post. When I check the device manage, the phone is listed as Android Bootloader Interface. I try updating the drivers by pointing it to the LG drivers folder, it says drivers are up to date. I've got ADB and OEM unlock both enabled in developer options. I've tried the phone on different USB ports, the cable works fine when the phone is booted normally, I've tried launching minimal adb&fastboot as admin and regular. What am I missing/doing wrong?
heldc said:
When I type in fastboot oem unlock, I get < waiting for any device >
And it waits, forever. (well, ok, like 15 minutes until I get impatient and pull the battery)
I'm on windows 10, installed the drivers from this post. When I check the device manage, the phone is listed as Android Bootloader Interface. I try updating the drivers by pointing it to the LG drivers folder, it says drivers are up to date. I've got ADB and OEM unlock both enabled in developer options. I've tried the phone on different USB ports, the cable works fine when the phone is booted normally, I've tried launching minimal adb&fastboot as admin and regular. What am I missing/doing wrong?
Click to expand...
Click to collapse
Try fastboot devices and reinserting the usb cable. Doesn't make sense that adb sees it but fastboot does not unless it's a different driver. I think fastboot driver differs actually so do that driver too.
Ubuntu
heldc said:
When I type in fastboot oem unlock, I get < waiting for any device >
And it waits, forever. (well, ok, like 15 minutes until I get impatient and pull the battery)
I'm on windows 10, installed the drivers from this post. When I check the device manage, the phone is listed as Android Bootloader Interface. I try updating the drivers by pointing it to the LG drivers folder, it says drivers are up to date. I've got ADB and OEM unlock both enabled in developer options. I've tried the phone on different USB ports, the cable works fine when the phone is booted normally, I've tried launching minimal adb&fastboot as admin and regular. What am I missing/doing wrong?
Click to expand...
Click to collapse
You can also load Ubuntu on a flash drive and boot your computer from the flash drive. Then run the commands.
https://www.ubuntu.com/
Cheers
heldc said:
When I type in fastboot oem unlock, I get < waiting for any device >
And it waits, forever. (well, ok, like 15 minutes until I get impatient and pull the battery)
I'm on windows 10, installed the drivers from this post. When I check the device manage, the phone is listed as Android Bootloader Interface. I try updating the drivers by pointing it to the LG drivers folder, it says drivers are up to date. I've got ADB and OEM unlock both enabled in developer options. I've tried the phone on different USB ports, the cable works fine when the phone is booted normally, I've tried launching minimal adb&fastboot as admin and regular. What am I missing/doing wrong?
Click to expand...
Click to collapse
First be on your c:\
Type in adb devices
If your phones serial comes up type in..
Adb reboot bootloader
Then
Fastboot oem unlock
ADB reboot bootloader boots straight into the OS on AT&T v20 :crying:
cordell12 said:
ADB reboot bootloader boots straight into the OS on AT&T v20 :crying:
Click to expand...
Click to collapse
Do you guys have the oem unlock option at least?
Also what helped me was downloading android studio with the sdk.. It installs android drivers which were necessary for me at least to get past the waiting for device message, windows located the drivers on my c drive and boom... Unlocked Bootloader.. Just saying
Sent from my LG-H918 using XDA-Developers mobile app
wing_addict_usa said:
Do you guys have the oem unlock option at least?
Click to expand...
Click to collapse
yup, even warns us that certain things won't work if we enable it. adb works just fine too
cordell12 said:
yup, even warns us that certain things won't work if we enable it. adb works just fine too
Click to expand...
Click to collapse
Yeah I am really curious if there may still be a way to unlock the bootloader with out AT&T variant. I wish I kept my phone on the Download Mode when I had gotten into it because I wanted to see if by any chance that might actually get fastboot to read the phone..
I'm curious if there's anyone with a T-Mobile variant that has their bootloader unlocked and wants to view their debug logs (specifically last_log/last_kmsg). As I was looking through mine and tried to boot into bootloader these lines were the only things I saw that might have interested me at all. I'm just curious on what the values are on their phone.
Code:
last_log
[ 0.711419] ro.boot.flash.locked=1
[ 0.711784] ro.bootloader=unknown
[ 0.711817] ro.oem_unlock_supported=1
last_kmsg
<6>[ 1.077087 / 01-01 00:00:01.069][3] [70] SW3800_Authentication [vendor code: 1]
<6>[ 1.077120 / 01-01 00:00:01.069][3] [110] set_dload_mode: download_mode:0
wing_addict_usa said:
It's the first step to rooting. If you plan to root, wiping your data now may be preferable.
Click to expand...
Click to collapse
It's quite possible the process of rooting will wipe the phone anyway.
twistedvip said:
Yeah I am really curious if there may still be a way to unlock the bootloader with out AT&T variant. I wish I kept my phone on the Download Mode when I had gotten into it because I wanted to see if by any chance that might actually get fastboot to read the phone..
I'm curious if there's anyone with a T-Mobile variant that has their bootloader unlocked and wants to view their debug logs (specifically last_log/last_kmsg). As I was looking through mine and tried to boot into bootloader these lines were the only things I saw that might have interested me at all. I'm just curious on what the values are on their phone.
Click to expand...
Click to collapse
power device off, hold volume up and keep it down and plug in USB cord while it's connected to PC. I tried fastboot from download mode though. the logs do look interesting, wonder what a T-MOBILE device says
Double0EK said:
First be on your c:\
Type in adb devices
If your phones serial comes up type in..
Adb reboot bootloader
Then
Fastboot oem unlock
Click to expand...
Click to collapse
Yup, I did that. And then I get an error. Well, not an error, just a lack of response. fastboot devices returns nothing. I'm currently downloading the full sdk, on the theory that perhaps it's a problem with the installation of 'minimal adb and fastboot' I have.
---------- Post added at 08:07 PM ---------- Previous post was at 07:36 PM ----------
manufan721 said:
Also what helped me was downloading android studio with the sdk.. It installs android drivers which were necessary for me at least to get past the waiting for device message, windows located the drivers on my c drive and boom... Unlocked Bootloader.. Just saying
Sent from my LG-H918 using XDA-Developers mobile app
Click to expand...
Click to collapse
Did you do anything specific after installing Android Studio to get it to install the drivers? Cos I've installed Android Studio, but am still having the same problem-fastboot devices returns nothing, and fastboot oem unlock hangs on <waiting for device>. I went into device manager and had it search the entire C: for drivers for the android bootloader interface, and it gave the same 'already up to date drivers' message as before I installed Android Studio.
EDIT- Even after installing the Google usb driver, no luck. Giving up for the weekend.
I'm a newbie, may I know have to fastboot from download mode?
having same issue just hangs at Fastboot oem unlock if anybody can help thanks in advance
twistedvip said:
Yeah I am really curious if there may still be a way to unlock the bootloader with out AT&T variant. I wish I kept my phone on the Download Mode when I had gotten into it because I wanted to see if by any chance that might actually get fastboot to read the phone..
I'm curious if there's anyone with a T-Mobile variant that has their bootloader unlocked and wants to view their debug logs (specifically last_log/last_kmsg). As I was looking through mine and tried to boot into bootloader these lines were the only things I saw that might have interested me at all. I'm just curious on what the values are on their phone.
Code:
last_log
[ 0.711419] ro.boot.flash.locked=1
[ 0.711784] ro.bootloader=unknown
[ 0.711817] ro.oem_unlock_supported=1
last_kmsg
<6>[ 1.077087 / 01-01 00:00:01.069][3] [70] SW3800_Authentication [vendor code: 1]
<6>[ 1.077120 / 01-01 00:00:01.069][3] [110] set_dload_mode: download_mode:0
Click to expand...
Click to collapse
[ 0.711817] ro.oem_unlock_supported=1 1=YES
did some digging into last_kmsg while trying to boot into bootloader (AT&T device) and found a reason it may not be allowing it.
http://forum.xda-developers.com/showthread.php?t=2708466
Its a start :good:
of course we need root in order to dd anything
LG issued a new driver update for the v20. Driver version is 4.1.1+. You can get the driver from the website.
Related
hello,
I'm hoping someone here can help me sort out my current problem.
I've been trying to root so I can install the latest ICS port, but having problems at the Fastboot screen.
I apologize in advance if some of the references/names I'm using are incorrect.
So, I had originally unlocked my Nexus S sometime early this year. When I restart the phone, the "unlocked" lock picture shows up under the "Google" words, and when I go into fastboot mode, the Lock State is Unlocked.
I'm running 2.3.6 right now on the Tmobile version of the phone.
When the phone is on (not in fastboot mode), I can execute ADB commands and the device is recognized. As soon as I go into fastboot it isn't.
I'm running 64bit Win 7, and I have gone through the various threads that have listed this issue, and installed PDA Net drivers and still there is no solution.
In Fastboot mode, while connected to computer under device manager, it shows up under Universal Serial Bus Controllers as an Unknown Device... I'm unable to update any drivers for it, and even when I try to manually update the drivers by going to the PDANet drivers it does not allow it.
When the phone is on in regular mode in device manager it shows up as Android Phone and within that it has a listing called Android Composite ADB Interface.
As mentioned above, when phone on in regular mode everything is detected.
I installed clockwork app from market, assuming that the phone was "rooted" based on the "unlock state" in fastboot mode, but it immediately says that phone needs to be rooted because it was unable to find SuperUser file etc etc.
I've spent the better part of a few days trying to figure this out by checking all sorts of links, but I haven't found a solution. The main issue is that the phone is not being recognized when in fastboot mode when connected by USB. And I'm unable to install the proper drivers for fastboot mode.
Hopefully this makes sense, and someone can provide some insight.
Thanks in advance!
I'm not positive about this but couldn't you adb push the su binary and apk? I don't own the Nexus but I would think since its unlocked you could just push the files. If this would work I would think it's just a temporary solution to allow superuser permission. As I understand it, fastboot is the preferred method for the Nexus.
Sent from my PG06100 using Tapatalk
Did you try a fastboot command like fastboot devices?
Don't know if this applies to you but I had a similar sounding problem when trying to root my Nexus S where everytime I booted into fastboot mode I had an error message at the bottom of the screen saying something like 'fastboot status-fail Invalid command' and so I couldn't use any fastboot functions.
To get around it I used this one-click root . For some reason I got an error message halfway through for whatever reason and it wouldn't complete the root for me but it booted me into fastboot without receiving the error message and then once I was in I went and rooted manually.
The CWM is out of date on that site though (possibly the super-user zip too) so I replaced them with the latest versions and popped it in my dropbox for you, if you wanna try it out.
http://dl.dropbox.com/u/47770734/One-Click-Nexus-S.zip
Edit: just had a little look through the bat script and the initial commands that got me into fastboot properly is (with your phone in debugging mode):
adb start-server
adb reboot bootloader
Click to expand...
Click to collapse
So you could try that first if you wanna go through manually.
Know that you can't run adb command while in fastboot mode. Boot into your CWM and then you can start an adb shell and you'll be able to push all the files you want and execute all the commands you need.
Fastboot mode is for running fastboot indeed. Try 'fastboot devices' while you're in the bootloader and see if devices pop up. If not, you really have to figure out your drivers issue. Maybe remove the device completely from your PC (including driver files) and reinstall it using the PDAnet drivers.
Greetz
I have a Nexus 5, returned to factory specifications (many times) with backup & restore inhibited. I am trying the “very simple” process of unlocking it, without any success. My problem is repeated many times on the web, Fastboot does not work, but ADB does.
I run the following command:
C:\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>adb devices
List of devices attached
0315c2d60935c160 device
Then I run the following command:
C:\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>fastboot devices
C:\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>
ADB sees the phone; Fastboot does not.
The solution is well documented on the web: Install new drivers. I have been installing drivers from just about everywhere for the last week without success. With the phone connected, I get this from Device Manager:
Computer
Android Device
Android Composite ADB Interface
The driver information is as follows:
Driver Provider: Google, Inc.
Driver Date: 7/9/2013
Driver Version: 8.0.0.0
Driver Signer: Google, Inc.
Driver Details:
Driver Files:
C:\Windows\System32\Drivers\Winsub.sys (File Version 6.2.9200.16384(Win8_rtm.120725-1247))
C:\Windows\System32\WdfcoInstaller01009.dll(File Version 1.9.7600.16385 (Win7_rtm.090713-1255)
C:\Windows\System32\WinUSBCoInstaller2.dll (File Version 6.1.7600.16385 (win7_rtm.090713-1255))
I am running a Dell XPS-17 I7 laptop with Windows 8 (not 8.1) 64 bit
If I could find a way to unlock without using Fastboot, that would probably be a good solution, but I can’t. And I have absolutely no success at getting Fastboot to work.
I do notice that the Device Manager lists Android Composite ADB interface (ADB works) but noting about a Fastboot interface. Does that mean anything?
Please help I am at my wit’s end.
For what it is worth, I did read all the tutorials here, and the only thing I could figure out was if I have the right drivers everything works fine. I also reviewed the posts here, including "Diagnosing USB Driver and ADB issues in Windows," which discusses ADB (which I have no problem with)
this article helped me out a bunch. http://blog.dantup.com/2012/10/fixing-adb-device-not-found-with-nexus-7-in-recovery-mode/
you'll have to edit the "android_winusb.inf" with the correct hardware id.
in Device Manager make sure you go to "Android Device" > "Android Composite ADB Interface" go to Properties. on the Details tab and then click on the drop down box and select "hardware ids" you might see 2 ids there. i believe the one you'll need is the bottom one. if you only have one. thats fine too.
so, read the article. grab your hardware id and edit your driver. see if it works. you may have to reboot after you edit the driver. hope this works for you.
krdu said:
I have a Nexus 5, returned to factory specifications (many times) with backup & restore inhibited. I am trying the “very simple” process of unlocking it, without any success. My problem is repeated many times on the web, Fastboot does not work, but ADB does.
I run the following command:
C:\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>adb devices
List of devices attached
0315c2d60935c160 device
Then I run the following command:
C:\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>fastboot devices
C:\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>
ADB sees the phone; Fastboot does not.
Click to expand...
Click to collapse
OK, please don't be offended, but I have to ask a really dumb question. You aren't running the "fastboot devices" command while in recovery, right? I read the above twice and didn't see where you booted into bootloader after running the "adb devices" command. Unless I'm missing something, fastboot won't find any devices unless you are in the bootloader.
Sounds like you need to boot your phone into fastboot mode. Power off the phone and hold volume down and hit the power button.
Then the fastboot devices command should work and you should be able to unlock the boot-loader then. Unlocking the boot-loader will wipe your phone just so you know.
erikivy said:
OK, please don't be offended, but I have to ask a really dumb question. You aren't running the "fastboot devices" command while in recovery, right? I read the above twice and didn't see where you booted into bootloader after running the "adb devices" command. Unless I'm missing something, fastboot won't find any devices unless you are in the bootloader.
Click to expand...
Click to collapse
Actually, the answer to that question is "Yes, and no." I was not aware that Fastboot only worked in the bootloader, but I could never get it to work there either. However, when I copied the previously posted listings I was not in the bootloader, I was in normal booted mode.
I then went and tried it in the bootloader, to copy listings to post, and here's what I got!
C:\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>adb devices (In normal Mode)
List of devices attached
0315c2d60935c160 device
C:\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>adb reboot bootloader (rebooted to Bootloader)
C:\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>adb devices
List of devices attached
C:\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>fastboot devices
0315c2d60935c160 fastboot
C:\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>fastboot oem unlock
...
OKAY [ 41.215s]
finished. total time: 41.215s
C:\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>
As you can see it unlocked the phone but I have absolutely no clue why it unlocked this time and never did before. I hope to God I never have to unlock it again.
Also, it appears that in the bootloader, ADT is NOT working but Fastboot is! (now)
You realize that the two command line interfaces (ADB and fastboot) don't work in the same state, right? ADB is for use in recovery and while booted, whereas fastboot only works in bootloader. It sounds to me like everything is working exactly as it should.
I'm no expert or anything, but I always assumed that they were two different ways to interact with your device while it is in different states. If I'm mistaken, someone please correct me.
krdu said:
Actually, the answer to that question is "Yes, and no." I was not aware that Fastboot only worked in the bootloader, but I could never get it to work there either. However, when I copied the previously posted listings I was not in the bootloader, I was in normal booted mode.
I then went and tried it in the bootloader, to copy listings to post, and here's what I got!
C:\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>adb devices (In normal Mode)
List of devices attached
0315c2d60935c160 device
C:\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>adb reboot bootloader (rebooted to Bootloader)
C:\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>adb devices
List of devices attached
C:\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>fastboot devices
0315c2d60935c160 fastboot
C:\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>fastboot oem unlock
...
OKAY [ 41.215s]
finished. total time: 41.215s
C:\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>
As you can see it unlocked the phone but I have absolutely no clue why it unlocked this time and never did before. I hope to God I never have to unlock it again.
Also, it appears that in the bootloader, ADT is NOT working but Fastboot is! (now)
Click to expand...
Click to collapse
ADB is used in android and the recovery.
Fastboot is used only in the bootloader.
Hi
My phone is international NXT-L29
I was on Ephemeral B180 rom but i decided to upgrade it to get emui 4.1
I flashed back stock b180 rom, and after I flashed stock b321 rom
ROM works great but i would like to get root and twrp back again, but everytime I try to go through fastboot i get this screen on picture.
I logged into my dc unlocker again and followed the procedures (manufacture mode, unlocking,...) and dc unloccker tool informs that the phone was unlocked...but no, when I do adb reboot bootloader i still get the same message on the picture.
I saw other suggestions here on XDA, i confirm oem unlock is activated on developer options...i made factory reset and then "vol+- power" (with or without phone connected to PC) but i dont't get any option to unlock bootloader. I always arrive to a menu saying that the phone is looking for upgrade and tries until 5% is reached... (if I keep waiting it does not fisplat error message, only waits and waits and after a while it reboots normally (i don't have any dload folder either on phone or sd card)
Any suggestion to solve this is highly appreciated
many thanks
Try to get ur unlock code from huawei website maybe this can help.
Did you run the bootloader unlock command with your unlock code again?
Ephemera said:
Did you run the bootloader unlock command with your unlock code again?
Click to expand...
Click to collapse
the only command my phone accept is adb reboot bootloader
Then i get the screen of picture that I posted, which says that it is a cold reboot (?)
Whem I reach this point it doens not respond to anything else taht I type on Command line (I type fastboot oem unlock (and the code) but on pc screen i read 'ewaiting device' and nothing happens on phone
gm007 said:
Try to get ur unlock code from huawei website maybe this can help.
Click to expand...
Click to collapse
I retrived my code from DC Unlocker (it has an option to read bootload code) but the problem is thar when I get de Fastboot&Rescue Mode the phone does not react to any command i can type on PC
Can I replace the stock boot.img that comes inside the UPDATE.APP file byone decrypted boot image of same rom?
If that would be possible then flashing this "modified" UPDATE.APP would solve the problem?
Many Thanks
pasil.pt said:
I retrived my code from DC Unlocker (it has an option to read bootload code) but the problem is thar when I get de Fastboot&Rescue Mode the phone does not react to any command i can type on PC
Click to expand...
Click to collapse
Hi pasil.pt,
try to update the fastboot mode driver
http://forum.xda-developers.com/showpost.php?p=69382774&postcount=202
grofock said:
Hi pasil.pt,
try to update the fastboot mode driver
http://forum.xda-developers.com/showpost.php?p=69382774&postcount=202
Click to expand...
Click to collapse
I don't see any kedacom usb device folder...
Check if the device isnfound by the computer. Restart in fastboot mode then on your computer type "fastboot devices" you should get a device and its serial. If you're not getting anything its a driver issue.
Ephemera said:
Check if the device isnfound by the computer. Restart in fastboot mode then on your computer type "fastboot devices" you should get a device and its serial. If you're not getting anything its a driver issue.
Click to expand...
Click to collapse
I did not try the command fastboot devices, but as per the new picture attached when I run adb devices the computer finds my phone
the problem is, then, when next i run 'adb reboot bootloader'...the device goes into fastboot&rescue mode and the device is not recognized by computer anymore
pasil.pt said:
I did not try the command fastboot devices, but as per the new picture attached when I run adb devices the computer finds my phone
the problem is, then, when next i run 'adb reboot bootloader'...the device goes into fastboot&rescue mode and the device is not recognized by computer anymore
Click to expand...
Click to collapse
Open control panel when your phone is in this state (it's fastboot mode) and you should see the folder I talked about.
It seems drivers issue, i hate windows 10
Try different usb port,and try to remove the drivers and install them again.
Make sure no usb device connected to any other ports.
grofock said:
Open control panel when your phone is in this state (it's fastboot mode) and you should see the folder I talked about.
Click to expand...
Click to collapse
YES!!!!!!
many thanks to you. grofock, and to ephemera, and XDA
At last i got it done. (Huawei are so tricky compared to samsung...but at least they do not explode
gm007 said:
It seems drivers issue, i hate windows 10
Try different usb port,and try to remove the drivers and install them again.
Make sure no usb device connected to any other ports.
Click to expand...
Click to collapse
You were probably right because i recently changed PC and aeverytime w10 upgrades I pray...
Have the the same problem, but didn't find the solution. Try different laptops and different cables. Windows can't recognise my Mate 8 L29 after B320 update cause of the wrong descriptor.
timasan said:
Have the the same problem, but didn't find the solution. Try different laptops and different cables. Windows can't recognise my Mate 8 L29 after B320 update cause of the wrong descriptor.
Click to expand...
Click to collapse
try grofock's hints about control panel and Device manager on windows....
pasil.pt said:
try grofock's hints about control panel and Device manager on windows....
Click to expand...
Click to collapse
I try it on four different PCs and still error 43 "wrong descriptor".
timasan said:
I try it on four different PCs and still error 43 "wrong descriptor".
Click to expand...
Click to collapse
Maybe explain more what you did,what are you trying to do and which tools you used.
gm007 said:
Maybe explain more what you did,what are you trying to do and which tools you used.
Click to expand...
Click to collapse
I'm trying to install drivers for Mate 8. I did it on different PC with Win 10 and 7. With different cables. Try to change or delete drivers for USB hub and etc. In fastboot mode and normal with usb debug and w/o.
timasan said:
I'm trying to install drivers for Mate 8. I did it on different PC with Win 10 and 7. With different cables. Try to change or delete drivers for USB hub and etc. In fastboot mode and normal with usb debug and w/o.
Click to expand...
Click to collapse
Did you install hisuite it has all the drivers and make sure to enable allow hisuite to use hdb in phone settings under security.
So I'm seeing a ton of posts of folks not able to get fastboot to see their devices. I've done some tinkering around and found a set of drivers that work fine for both ADB and Fastboot. (Attached)
Uninstall any ADB drivers you have on your system. Easiest way is to plug your phone in, go into device manager, right click your phone and select uninstall and check the box that says to remove the driver as well.
Then download this package, extract, simply run install.exe as admin. Don't panic, it doesn't do anything visual.
Now plug your phone in and see if adb works, you may need to authorize the computer again on the phone so make sure it's unlocked.
Reboot into bootloader and check if fastboot sees the phone by using
Code:
fastboot devices
If not then go back into device manager and right click on your phone, select update driver, let me select one from a list and you should see "Fastboot interface (Google USB ID)". Select this one.
Check fastboot without unplugging with the same command. Check and see if you can send commands to the phone by using for instance,
Code:
fastboot getvar unlocked
If the command fails, simply plug the phone into a different USB port and the same Google driver should install again and you should be able to send commands to the phone. Alternatively, you can reboot the phone by tapping the battery out and starting it all over again.
Now she chooches.
Lemme know if you're still having problems.
bless up ??
Does this work for sprint variant?
im having problems...damn it i don't get this
---------- Post added at 03:19 PM ---------- Previous post was at 02:42 PM ----------
any help please?
Verizon variant here,
I cannot seem to get this dang V20 in the right mode
(I've seen a bootloader or two in my day):highfive::laugh::silly:
I have used the adb command (several times)
Code:
adb reboot bootloader
to get it into bootloader mode, alas it is to no avail since all the command does is send the phone into "Restart" mode; nor can I get fastboot to recognize it when it is in, what I believe to be , the bootloader for said LG V20 of the
Verizon persuasion!
Suggestions?
You need fastboot, not bootloader... To get it, turn off your phone, plug your LG cable into the computer, ( but not the phone yet) hold the volume down key for 5 seconds then plug it into your cable, do not release the button till your phone boots. It should boot into fastboot... Provided you have turned on USB debugging in developer settings (turn on oem unlock while you are in there too. (this is the way on the tmo V20 at least... If that doesn't work, I would use the dirty Santa guide
Sent from my LG-H918 using Tapatalk
Not sure how I finally got it working for my Verizon variant as I tried like four or five different ways, but someone should definitely make a video.. Perhaps I will since I think visuals are a good aid to go along with written instructions..
Thanks bro works
Very easy
With my t mobile v20
My phone shows as connected in adb devices. I can also get it to reboot bootloader, but once im there.. I cant issue any commands such as fastboot oem device-id. It gives me the dreaded waitng for any device.
can't manage to make this work for H990DS, i don't get the usual authorization window to the computer, only get the window to choose which USB mode (battery charge, file transfer, so on...) I'm trying to get adb to work to activate agressive Doze on Greenify app, any help?
Thanks
Vexamus said:
So I'm seeing a ton of posts of folks not able to get fastboot to see their devices. I've done some tinkering around and found a set of drivers that work fine for both ADB and Fastboot. (Attached)
Uninstall any ADB drivers you have on your system. Easiest way is to plug your phone in, go into device manager, right click your phone and select uninstall and check the box that says to remove the driver as well.
Then download this package, extract, simply run install.exe as admin. Don't panic, it doesn't do anything visual.
Now plug your phone in and see if adb works, you may need to authorize the computer again on the phone so make sure it's unlocked.
Reboot into bootloader and check if fastboot sees the phone by using
Code:
fastboot devices
If not then go back into device manager and right click on your phone, select update driver, let me select one from a list and you should see "Fastboot interface (Google USB ID)". Select this one.
Check fastboot without unplugging with the same command. Check and see if you can send commands to the phone by using for instance,
Code:
fastboot getvar unlocked
If the command fails, simply plug the phone into a different USB port and the same Google driver should install again and you should be able to send commands to the phone. Alternatively, you can reboot the phone by tapping the battery out and starting it all over again.
Now she chooches.
Lemme know if you're still having problems.
Click to expand...
Click to collapse
Perfect and Easy!!!! :good:
thx..ur ma angel
I can't find my phone in Device Manager.
this is great and works like a charm! thanks!
Thanks!
Just as the title says; I have the unlock token and I've tried everything I can think of to flash it and nothing's worked. I have OEM unlocking enabled, the phone is permanently carrier unlocked, USB debugging is enabled, I've made sure to download a new version of Platform Tools, I've moved the .bin file to the same directory as Platform Tools, the phone comes up in ADB and fastboot when I check, it just won't write and I can't figure out why... usually it just hangs at sending 'cust-unlock' etc. but never progresses past that. Can anyone help me figure this out?
EDIT: Resolved! Me being dumb, not realized I'd only tried USB 2.0 ports; using a 3.2 port did the trick instantly.
Have you tried other fastboot commands like - "fasboot reboot bootloader" to ensure your fastboot is working properly and the correct drivers are installed?
FoxyDrew said:
Have you tried other fastboot commands like - "fasboot reboot bootloader" to ensure your fastboot is working properly and the correct drivers are installed?
Click to expand...
Click to collapse
Yea, that's what's baffling; I can jump back and forth between adb and bootloader/fastboot pretty easily but I just can't send the unlock token. I have seen a couple weird errors though, like if I'm in bootloader and do 'fastboot OEM unlock' and it fails (since I can't get the token to flash) and afterward I try 'fastboot devices' sometimes fastboot crashes to the 'press any key to reboot' screen.
Could this just be an outdated driver issue? I thought they were up to date...
Have u try using other cable or even try on different PC?
hendavi said:
Have u try using other cable or even try on different PC?
Click to expand...
Click to collapse
I've tried multiple USB ports and the original cable as well as others; I've confirmed commands like 'ADB reboot bootloader' and 'fastboot reboot bootloader' work and I've even updated the ADB/fastboot drivers just in case... still nothing. I haven't tried a different PC yet but I suppose that's next
No matter what I try, this is what I get every time I try it from the bootloader. I've tried from bootloaderd/recovery, but it fails there too saying something like 'writing not allowed' or something... I have OEM unlock turned on and it's carrier unlocked, so I have no clue what's stopping this from working.
What's really weird is I actually got this to work once before on this same device, but had to reset the phone back to stock T-Mobile branded software using the MSM tool; the first time around, I was able to enter the unlock token and just unlock it like normal (fastboot OEM unlock). Now that I've reset the phone and I'm trying again, it just won't work... really perplexed on this one.
UPDATE
I had to pull up an image of my mobo's io panel because I couldn't remember and couldn't see which ports were which; once I moved the cable to a USB 3.2 port, it worked... I guess I'd only been trying it on USB 2.0s before so it didn't work.
Thanks for your help!
I had same issue on my OnePlus 8 TMobile. Have to disable driver signatures. This shows you how. Yes, the link is for a diff phone, but just follow the disable driver signatures part of it and it will then show up in fastboot
https://forum.xda-developers.com/t/...owing-up-in-fastboot-mode-windows-10.4194491/
EDIT: False alarm. I was sent an unlock code for an older device I have instead of the one I just bought. Should've double checked it first.