Hi everyone
Since i updated firmware from .42 to .62 via flashtool, i've got a weird behaviour when i plug my phone in Flash mode.
It's recognized as S1 boot download with a yellow triangle thingy, i installed usb flash drivers, now it's with SEMC Flash Device as hardware, then after 30s-1min it reboots and turns to SEMC HSUSB Device, a mass storage entity.
Can you help me fix this so i can access fastboot?
I reverted back to .42 via wotan, erase all drivers with usbdeview, plug it back, nothing works. I surely did something wrong but i can't spot it.
Tried on another pc, same behavior. Something's missing/corrupt in the phone.
i have a similiar problem, i cant access fastboot, message waiting for device, in device manager i cant install the driver cause it tells me not found.
Any Idea?
I was having strange problems when trying to install the drivers on a windows 7 PC. i had to install GordansGate drivers but it still didnt work. I ended up installing PDAnet or something and it installed all the correct drivers for me and using the latest version of flashtool i can do everything from there (flashtool, fastboot, adb)
i tried so much, but it wont recognize the driver -.- dont know what to do, every time when i try it with device manager->S1BootFastboot->install driver it tells me that my drivers directory are not the right drivers -.-
install this and run through the setup carefully and follow each step. this fixed my driver (not recognizing device) problems on my desktop
http://junefabrics.com/android/download.php
hope this solves your problems because i was going mad with mine for ages
ok solved my problem by installing flashtool and the flashtool drivers. now everything works fine
Hey! I have the same problem on my Mini.
When connecting, Device manager says "S1boot ..." and the icon has yellow triangle, but then it changes to "SEMC Flash Device"
Fastboot gives "<waiting for device>"
What Flashtool version have you had when you installed it's drivers?
Did you add that .inf file from SE site?
Theonewithideas said:
Hey! I have the same problem on my Mini.
When connecting, Device manager says "S1boot ..." and the icon has yellow triangle, but then it changes to "SEMC Flash Device"
Fastboot gives "<waiting for device>"
What Flashtool version have you had when you installed it's drivers?
Did you add that .inf file from SE site?
Click to expand...
Click to collapse
i have the same problem
francois90 said:
i have the same problem
Click to expand...
Click to collapse
Try switching the USB cable and USB port
Theonewithideas said:
Try switching the USB cable and USB port
still nothing ... if u can give me more instructions i'd appreciate it , ty
Click to expand...
Click to collapse
Related
hey.
i followed the guide for rooting my galaxy nexus.
driver installation was alright, and then i switched to fastboot mode (green android) and then the device manager didn't recognize my gn (unknown device).
tried uninstalling and then reinstalling, tried "updating" it with various rar files i found on this forum and ofcourse i tries pdanet.
none of them worked. it was always unknown device.
then i had no choice and i removed the battery to boot it normal.
suggestions? thnaks
After installation, plug in your phone, look at your system tray for the USB icon, click it. It should show a status of installing more drivers. This can take awhile, and for a lot of people it seems to fail the last step, Android 1.0 drivers. Open control panel, system, device manager. Look for a yellow error icon. Click that, choose to install drivers manually and locally. Then select 'choose from list', find Samsung.
That should get you back on track
Sent from my Galaxy Nexus Bugless Beast 4.0.3 lte +franco#5
Were you able to unlock the bootloader? If you didn't do this, don't go installing any driver... be very careful. If you install the wrong driver in device manager, you'll screw it up. I installed the wrong driver on my main computer and I couldn't get the device manager to even recognize the phone :| I couldn't locate the right driver either because once I installed the driver, it renamed it. It was a huge pain and the only way I got this to work was by using a different PC with the correct drivers.
I have found this to be the best instructions for unlocking the bootloader. Most importantly, it includes directions on how to gain access to adb on your phone properly. Take your time and follow the instructions exactly...
Dutchy18 said:
hey.
i followed the guide for rooting my galaxy nexus.
driver installation was alright, and then i switched to fastboot mode (green android) and then the device manager didn't recognize my gn (unknown device).
tried uninstalling and then reinstalling, tried "updating" it with various rar files i found on this forum and ofcourse i tries pdanet.
none of them worked. it was always unknown device.
then i had no choice and i removed the battery to boot it normal.
suggestions? thnaks
Click to expand...
Click to collapse
I had the same issue, install pdanet and your phone will be recognized when in fastboot
Sent from my Galaxy Nexus using xda premium
i followed one of the main guides on this forum.
it says to install the pdanet drivers and then boot to fastmode via the volume buttons.
once i got into fastboot, the device was unrecognizable.
when i was still in normal boot, the device was recognized and it was all right. and yeah i turned usb debugging on.
how can i unlock the bootloader without installing drivers?
thanks
Dutchy18 said:
i followed one of the main guides on this forum.
it says to install the pdanet drivers and then boot to fastmode via the volume buttons.
once i got into fastboot, the device was unrecognizable.
when i was still in normal boot, the device was recognized and it was all right. and yeah i turned usb debugging on.
how can i unlock the bootloader without installing drivers?
thanks
Click to expand...
Click to collapse
silly question, but after booting to fastboot, you are using the fastboot.exe, and not adb? if you type "fastboot devices" does anything show up?
no, nothing shows up.
and thats clearly because the driver is not installed correctly.. i see a yellow sign in device manager.
what am i doing wrong? only thing i was different from the guide is that instead of typing adb reboot bootloader, i got into fastboot by pressing the volume buttons.
Dutchy18 said:
no, nothing shows up.
and thats clearly because the driver is not installed correctly.. i see a yellow sign in device manager.
what am i doing wrong? only thing i was different from the guide is that instead of typing adb reboot bootloader, i got into fastboot by pressing the volume buttons.
Click to expand...
Click to collapse
click open that yellow unrecognized device...manually choose drivers (don't do auto), and select from the list, you'll see samsung, choose the driver
that should install android 1.0...alot of people have gotten this error.
edit: another thing to keep in mind is, after installing the drivers, and fixing the device in device manager, it can still take a little bit to initialize. in your system tray there should be a usb icon, open that to see when the drivers are done
I am in the same boat. I tried for hours on 2 different Windows 7 laptops (both 64bit). I am trying to get Yakju from one of the derivitives (without unlocking the device).
Steps taken:
- Dloaded Samsung USB driver 1.4.6 & Installed: Did not recongnize in explorer or Odin (even Odin did not show a thing)
- Dladed PDA Net A302x64: Did not recognize in explorer or Odin.
Both times the GN is in Device/Printers and listed as having Android 1.0 driver. I try to manually update, but cannot seem to find driver in list (as it just has Android 1.0 driver listed). Any suggestions?
i didnt even see the "Android 1.0".. just "unknown device" all along..
i also tried on a different computer.. same issue.
about manually installing the driver.. i tried pointing him to a manual driver package i got from this forum.. it said its the same driver..
when im searching for "samsung" on the list, i dont see a relevant driver.
Well, i've saw someone else on here who was having driver issues, who also had installed both samsung & pda drivers...
uninstall both.
fresh install ONLY the naked drivers directly off samsungs website (http://www.samsung.com/us/support/downloads/verizon-wireless/SCH-I515MSAVZW -- if you're verizon, if not, you can search there). Do the install. Plug the phone in, it will start to install its usual crap. this is the long part. then, it will fail like you saw before. in device manager, you'll see the unrecognized device. Open, it will ask you to find drivers, choose "Browse", "Let Me Pick From a List", "Samsung", and then pick the driver with the date 11/25/2011
check to see if there are any other unrecognized devices in device manager, just to be sure you got em all. at this point, plugging in your phone should show the USB connected icon in the system tray. do you see this? If you click it does it say "Eject MTP"?
my laptop does not recognize my phone in either flashmode or fastboot mode, i tried sing pc companion and flashtool drivers but it does not fix the problem. maybe im doing something wrong, can you guys help me in step by step?
Phone: Xperia Arc S
Version: 4.0.4
Build: 4.1.B.0.587
Computer
OS: Windows 8 (64bit)
http://forum.xda-developers.com/showthread.php?t=2044804
still not working for me
Do you see any error, installing the drivers? What was the the status in the flashtool?
Cibhin said:
Do you see any error, installing the drivers? What was the the status in the flashtool?
Click to expand...
Click to collapse
there's no error in installing the drivers, the status is "device not found"
Phone [Q] my laptop doesn't recognize my phone (flash mode & fastboot mode)
Try this:
(1) Go to device manager
(2) Plug phone in and look for any changes in your list of devices (maybe under other devices) should have a yellow box with exclamation mark
(3) Once found right click then click browse my computer for driver software (point to the folder where drivers are)
(4) Install from there make sure driver signature is off like instructions above :good:
Use this ( View attachment driver_androidusb.zip )... It will work for Arc S and Other
click Thanks if I Help
still not working...
here is the device status...
This device cannot start. (Code 10)
A request for the USB BOS descriptor failed.
try to uninstall any Android Emulator programs you have
Check also if both ends of the usb cable are properly connected and intact to phone and laptop.
Install Android SDK, open it, install all drivers with it. That should do the thing, if I remember correctly.
Sent from LT18i with custom firmware by myself.
Someguyfromhell said:
Install Android SDK, open it, install all drivers with it. That should do the thing, if I remember correctly.
Sent from LT18i with custom firmware by myself.
Click to expand...
Click to collapse
how do you install the drivers using android sdk?
If it's possible for you and not too painstaking, try and format your system, and then do a fresh install. Worked for me when I had a similar problem in the past.
MarcSinger said:
If it's possible for you and not too painstaking, try and format your system, and then do a fresh install. Worked for me when I had a similar problem in the past.
Click to expand...
Click to collapse
i think ill do that, i have tried almost everything but nothing works
so what now? working?
My laptop will not recognize flash mode.
Its not driver problem its keep usb not recognizing.
Hi! I'vs just bought a new computer and I have to migrate from my desktop PC to the new laptop. The problem comes after restart the PC. I've installed the Android SDK, the PCCompanion, the Gordon's Gate drivers and the fastboot drivers from flashtool, as on my desktop computer with the advanced reinstall to avoid the prohibition to install unsigned drivers. The problem comes here because with my PC I could flash kernels at this point, but, in my new laptop appears another unknow device called Sony Fastboot Interface inside Android Device in the Device Manager. Any ideas?
No one?
What happens when you try to install the drivers ?
Is it in any way colides with flashing and so on ?
IF not then don't worry.
When I finish, appears another unknow device (Android Bootloader Interface) and if I try to flash a kernel, the console gives me waiting for device
I recall installing few drivers.
1 Regular usb
2 Fastboot mode drivers
3 Flashtool drivers
Try googling "xperia fastboot drivers" and download any you can find, i remember downloading some from sony's official webiste.
Here:
http://developer.sonymobile.com/downloads/drivers/fastboot-driver/
Connect the device in normal mode and fastboot mode and manually select the path to the drivers.
I ended up doing it in windows safe mode, because my pc kept freezing.
GL
Have you tried using flashtool for kernel flash?
Sent from my Xperia X10 using xda premium
Which OS are you using?
Hello guys, i recently in past change cca 8 times flashed fw, kernel and rom, but yesterday i want to flash so i flashed firmware without problems, but when i wanted fastboot (Search button + USB to phone) led turns blue but flashtool gives me this Device connected in flash mode. So i try reinstall drivers, but still same
ERROR - Drivers need to be installed for connected device.
ERROR - You can find them in the drivers folder of Flashtool.
INFO - Device connected in flash mode
ERROR - This action can only be done in fastboot mode
INFO - Device Status: NOT FOUND
ERROR - This action can only be done in fastboot mode. Please help me
ExisteRcz said:
Hello guys, i recently in past change cca 8 times flashed fw, kernel and rom, but yesterday i want to flash so i flashed firmware without problems, but when i wanted fastboot (Search button + USB to phone) led turns blue but flashtool gives me this Device connected in flash mode. So i try reinstall drivers, but still same
ERROR - Drivers need to be installed for connected device.
ERROR - You can find them in the drivers folder of Flashtool.
INFO - Device connected in flash mode
ERROR - This action can only be done in fastboot mode
INFO - Device Status: NOT FOUND
ERROR - This action can only be done in fastboot mode. Please help me
Click to expand...
Click to collapse
if drivers are not installed properly.. Start Windows 7 or 8 or 8.1 in "Disabled Driver Sginature Mode" (Google this if you don't know how)
if you think drivers are installed correctly.. then do one think cuz I also face the same issue.. Don't connect the Device and then try to FLash by the electric signal..
first select the firmware .. click ok.. then let the software tell u.. to connect the Device.. do that and it should work !! let us know.
Drivers are "SEMC Flash Device" for "S1Boot Fastboot". And when i try to load kernel first when device is disabled it gives me this.
02/013/2015 12:13:21 - INFO - Device disconnected
02/013/2015 12:13:33 - ERROR - This action can only be done in fastboot mode
02/013/2015 12:13:41 - ERROR - This action can only be done in fastboot mode
02/013/2015 12:13:49 - INFO - Device connected in flash mode
02/013/2015 12:13:56 - ERROR - This action can only be done in fastboot mode
and i dont know how to flash via electric signal
Emma software from Sony works well for recovery my phone to original ROM and Kernel.
Maybe "back" button is stuck. Can you boot into android (doesn't matter is it custom rom or official firmware)
Also, try different usb port or different usb cable
Untill you found a solution you can flash custom kernels in .ftf format (you can flash them in flash mode)
Sent from my R800i using XDA Free mobile app
Bakisha said:
Maybe "back" button is stuck. Can you boot into android (doesn't matter is it custom rom or official firmware)
Also, try different usb port or different usb cable
Untill you found a solution you can flash custom kernels in .ftf format (you can flash them in flash mode)
Sent from my R800i using XDA Free mobile app
Click to expand...
Click to collapse
I dont think the "back" button is stucked. Cuz when i power off phone and holding back button and connect it gives me Green LED and when Search button its gives me Blue LED. Problem is not in phone but in Flashtool. If I have flash mode on phone devices shows me "S1Boot Flashmode" when fastboot "S1Boot Fastboot". I tryied all usb ports on my PC and 4 USB Cables (1 Original from XPlay and 3 others from different samsung phones) and Yea I can boot into android, and i tryied flash custom kernels in .ftf format but its always brick my phone and I must use Emma software for Revive the phone . Sorry my english is very bad
ExisteRcz said:
I dont think the "back" button is stucked. Cuz when i power off phone and holding back button and connect it gives me Green LED and when Search button its gives me Blue LED. Problem is not in phone but in Flashtool. If I have flash mode on phone devices shows me "S1Boot Flashmode" when fastboot "S1Boot Fastboot". I tryied all usb ports on my PC and 4 USB Cables (1 Original from XPlay and 3 others from different samsung phones) and Yea I can boot into android, and i tryied flash custom kernels in .ftf format but its always brick my phone and I must use Emma software for Revive the phone . Sorry my english is very bad
Click to expand...
Click to collapse
Yeah, it looks like phone is ok
Try to uninsatll all related drivers from PC (go to device manager, righ-click on driver, then "uninstall"). Do it when for all 3 modes (flash, normal and fastboot mode)
Then disconnect and connect phone again.
Or choose to manually install drivers for
Or reinstall flashtool
Bakisha said:
Yeah, it looks like phone is ok
Try to uninsatll all related drivers from PC (go to device manager, righ-click on driver, then "uninstall"). Do it when for all 3 modes (flash, normal and fastboot mode)
Then disconnect and connect phone again.
Or choose to manually install drivers for
Or reinstall flashtool
Click to expand...
Click to collapse
I tryied these so many times. I downloaded and tested 13 differents drivers but it has no effect still Flash mode . and i reinstalled flashtool too. I dont know what can be wrong.
ExisteRcz said:
Hello guys, i recently in past change cca 8 times flashed fw, kernel and rom, but yesterday i want to flash so i flashed firmware without problems, but when i wanted fastboot (Search button + USB to phone) led turns blue but flashtool gives me this Device connected in flash mode. So i try reinstall drivers, but still same
ERROR - Drivers need to be installed for connected device.
ERROR - You can find them in the drivers folder of Flashtool.
INFO - Device connected in flash mode
ERROR - This action can only be done in fastboot mode
INFO - Device Status: NOT FOUND
ERROR - This action can only be done in fastboot mode. Please help me
Click to expand...
Click to collapse
ExisteRcz said:
I tryied these so many times. I downloaded and tested 13 differents drivers but it has no effect still Flash mode . and i reinstalled flashtool too. I dont know what can be wrong.
Click to expand...
Click to collapse
im using flashtool 0.9.10.1 and all seems fine.. try that
saqibkhan said:
im using flashtool 0.9.10.1 and all seems fine.. try that
Click to expand...
Click to collapse
Okay I downloaded uninstalled my flashtool, then uninstalled drivers, installed flashtool 0.9.10.1, then drivers from C:/Flashtool/drivers and installed just Xperia PLAY and fastboot drivers, then i connect device in fastboot (Blue LED) and it says "08/045/2015 11:45:32 - ERROR - Drivers need to be installed for connected device.
08/045/2015 11:45:32 - ERROR - You can find them in the drivers folder of Flashtool.
" but i installed them, so i installed them manualy i searched for them somewhere, from 3 drivers i selected Android Bootloader Interface but everytime it install Android ADB Interface so problem is in drivers i think.
ExisteRcz said:
Okay I downloaded uninstalled my flashtool, then uninstalled drivers, installed flashtool 0.9.10.1, then drivers from C:/Flashtool/drivers and installed just Xperia PLAY and fastboot drivers, then i connect device in fastboot (Blue LED) and it says "08/045/2015 11:45:32 - ERROR - Drivers need to be installed for connected device.
08/045/2015 11:45:32 - ERROR - You can find them in the drivers folder of Flashtool.
" but i installed them, so i installed them manualy i searched for them somewhere, from 3 drivers i selected Android Bootloader Interface but everytime it install Android ADB Interface so problem is in drivers i think.
Click to expand...
Click to collapse
if you are using Windows 8 or 8.1 .. try going into "Disable Signature mode for Drivers" in advanced startup and then try installing the Drivers !!
btw I install ADB drivers from the ADB package.. that is in the folder Fastboot and ADB Package\Drivers\google-usb_driver
try this.. but install in the mode I told u above.. uninstall the previous devices.. and when it Says Confirm Uninstall theirs a small box below that telling u "delete Drivers" and Uninstall.. tick that.
When I enter bootloader to try and flash twrp.... I get the message "waiting for device"
Trying to flash TWRP
can anyone help?
ADB recognizes the device...as soon as I reboot into the bootloader.... it disconnects
Anyone?
no one?
bigd19888 said:
When I enter bootloader to try and flash twrp.... I get the message "waiting for device"
Trying to flash TWRP
can anyone help?
ADB recognizes the device...as soon as I reboot into the bootloader.... it disconnects
Click to expand...
Click to collapse
If you want helpful responses you have to be more specific. Assuming you have the fastboot files installed on your PC/laptop ... What LG G4 model? What software version? Bootloader Unlocked? etc.
Assuming you have installed on your PC/laptop LGMobileDriver_WHQL_Ver_4.2.0 available for download from the LG US site as the Windows driver can create issues, have you tried downloading and installing the "Official" TWRP app and installing that way?
Suggest if you are still having problems, you head over to: https://forum.xda-developers.com/g4/development/recovery-twrp-3-touch-recovery-t3442424
Read the OP thoroughly and post any issues you're having there.
sdembiske said:
If you want helpful responses you have to be more specific. Assuming you have the fastboot files installed on your PC/laptop ... What LG G4 model? What software version? Bootloader Unlocked? etc.
Assuming you have installed on your PC/laptop LGMobileDriver_WHQL_Ver_4.2.0 available for download from the LG US site as the Windows driver can create issues, have you tried downloading and installing the "Official" TWRP app and installing that way?
Suggest if you are still having problems, you head over to: https://forum.xda-developers.com/g4/development/recovery-twrp-3-touch-recovery-t3442424
Read the OP thoroughly and post any issues you're having there.
Click to expand...
Click to collapse
I have minimal adb and fastboot installed
device is h811 20v
bootloader is already unlocked
and yes I'm using LGMobileDriver_WHQL_Ver_4.2.0
sdembiske said:
If you want helpful responses you have to be more specific. Assuming you have the fastboot files installed on your PC/laptop ... What LG G4 model? What software version? Bootloader Unlocked? etc.
Assuming you have installed on your PC/laptop LGMobileDriver_WHQL_Ver_4.2.0 available for download from the LG US site as the Windows driver can create issues, have you tried downloading and installing the "Official" TWRP app and installing that way?
Suggest if you are still having problems, you head over to: https://forum.xda-developers.com/g4/development/recovery-twrp-3-touch-recovery-t3442424
Read the OP thoroughly and post any issues you're having there.
Click to expand...
Click to collapse
I have the right files, when I get into adb reboot into bootloader
it no longer recognizes the device. I cannot flash twrp
After reboot into bootloader, open your "windows device manager" and see if windows detects your device properly.
RuedasLocas said:
After reboot into bootloader, open your "windows device manager" and see if windows detects your device properly.
Click to expand...
Click to collapse
seems like a driver problem, need to keep removing and reinstalling in device manager for it to recognize my phone
I'm using the right driver...so I don't know what the problem is
quite annoying
windows xp I never have a problem with adb and fastboot.....windows 7 and up. ALWAYS
bigd19888 said:
seems like a driver problem, need to keep removing and reinstalling in device manager for it to recognize my phone
I'm using the right driver...so I don't know what the problem is
quite annoying
windows xp I never have a problem with adb and fastboot.....windows 7 and up. ALWAYS
Click to expand...
Click to collapse
Don't allow Windows 10 to update your drivers - you can set that up in Windows. Google it for the how-to.
bigd19888 said:
I have the right files, when I get into adb reboot into bootloader
it no longer recognizes the device. I cannot flash twrp
Click to expand...
Click to collapse
bigd19888 said:
seems like a driver problem, need to keep removing and reinstalling in device manager for it to recognize my phone
I'm using the right driver...so I don't know what the problem is
quite annoying
windows xp I never have a problem with adb and fastboot.....windows 7 and up. ALWAYS
Click to expand...
Click to collapse
The device type changes depending on "how" its connected. Windows can "see" it as a ADB device, MODEM, etc...
With the phone connected, uninstall all device related on windows device manager, refresh the device manager for it to detect the phone as it should be (as you need it to be detected).
Sometimes its needed a manual device driver install. Happens some times to me, unfortunately I don't remember exactly how I do it because the issues (when it happens) are kind of random, so, I need to "understand" what is going wrong and fix it.
Just to tell you that is nothing unfixable on the procedure, you just need to have patience and find out how windows is supposed to detect your device.
If you don't find out by yourself, tomorrow (Monday), I'll try to see on mine how it should be detected in fastboot mode and tell you. Today its already late for me...
Good luck
RuedasLocas said:
The device type changes depending on "how" its connected. Windows can "see" it as a ADB device, MODEM, etc...
With the phone connected, uninstall all device related on windows device manager, refresh the device manager for it to detect the phone as it should be (as you need it to be detected).
Sometimes its needed a manual device driver install. Happens some times to me, unfortunately I don't remember exactly how I do it because the issues (when it happens) are kind of random, so, I need to "understand" what is going wrong and fix it.
Just to tell you that is nothing unfixable on the procedure, you just need to have patience and find out how windows is supposed to detect your device.
If you don't find out by yourself, tomorrow (Monday), I'll try to see on mine how it should be detected in fastboot mode and tell you. Today its already late for me...
Good luck
Click to expand...
Click to collapse
everytime I boot into the bootloader the driver stops working.. when I boot the phone normally windows doesn't recognize my phone. it is unknown, so I remove the driver, reinstall it., get into bootloader and same issue persists "waiting on device:" I think the lg driver keeps crashing or it is windows issue
will try again tomorrow
bigd19888 said:
everytime I boot into the bootloader the driver stops working.. when I boot the phone normally windows doesn't recognize my phone. it is unknown, so I remove the driver, reinstall it., get into bootloader and same issue persists "waiting on device:" I think the lg driver keeps crashing or it is windows issue
will try again tomorrow
Click to expand...
Click to collapse
Your device should be seen as "LGE Android Phone" (if your lg drivers are good).
Now gonna be tricky because my OS is in Portuguese, I don''t know exactly the path name in English... use your imagination
Connect the device on a USB 2 Port !!!
In windows device manager, select "update driver", "search software on the computer", "allow to choose from a list of avalable drivers". unmark the "compatible hardware" and find on the list the needed drivers. If the "LGE" drivers don't work, try to download Universal ADB Drivers, maybe it works.
bigd19888 said:
everytime I boot into the bootloader the driver stops working.. when I boot the phone normally windows doesn't recognize my phone. it is unknown, so I remove the driver, reinstall it., get into bootloader and same issue persists "waiting on device:" I think the lg driver keeps crashing or it is windows issue
will try again tomorrow
Click to expand...
Click to collapse
I'm thinking it could be a corrupted LG driver. Download another from the LG US site, ONLY. Uninstall the one you have installed now, reboot and install the newly downloaded one. Then connect your phone and see if it is recognized and shown correctly in Windows Device Manager. Also, in adb type lsusb and see if the phone is listed in the output.
bigd19888 said:
everytime I boot into the bootloader the driver stops working.. when I boot the phone normally windows doesn't recognize my phone. it is unknown, so I remove the driver, reinstall it., get into bootloader and same issue persists "waiting on device:" I think the lg driver keeps crashing or it is windows issue
will try again tomorrow
Click to expand...
Click to collapse
Boss, no need to struggle with this ADB anymore.. there is a tool called FWUL which was created for people who have driver issues... Check it out here:
https://forum.xda-developers.com/an.../live-iso-adb-fastboot-driver-issues-t3526755
:good: