[Q] Fastboot driver not recognised - G4 Q&A, Help & Troubleshooting

Hello.
I'm trying to unlock the phones bootloader (I have the H815 EUR version).
The problem is that after I boot into recovery both my PC's don't recognize the fastboot driver (Windows 8 and Windows 7), both are showing the device only as "Android".
I installed the LG drivers "LGUnitedMobileDriver_S52MAN314AP22_ML_WHQL_Ver_3.14.1".
Any ideas?
Thanks in advance

twinkle2K said:
Hello.
I'm trying to unlock the phones bootloader (I have the H815 EUR version).
The problem is that after I boot into recovery both my PC's don't recognize the fastboot driver (Windows 8 and Windows 7), both are showing the device only as "Android".
I installed the LG drivers "LGUnitedMobileDriver_S52MAN314AP22_ML_WHQL_Ver_3.14.1".
Any ideas?
Thanks in advance
Click to expand...
Click to collapse
Did you ever get help with this or figure it out?

Related

[Q] Help with ADB....Question

I am trying to get ADB to work so I can do the unlock bootloader. ADB recognizes my phone while booted up with usb debugging enabled, but when I reboot to fastboot, it does not recognize it.
I've tried different drivers, uninstalling and reinstalling.... no luck.....
Is there anyone that is knowledgeable in this area to assist me? Is there any kind of IRC channel available to get real-time answers?
Please help,
Thanks,
Bob
i am in the same boat. Using windows 7(64 bit). Cannot get the phone recognized in boot loader mode.
diablonyc2 said:
i am in the same boat. Using windows 7(64 bit). Cannot get the phone recognized in boot loader mode.
Click to expand...
Click to collapse
Yeah, im on 7 64 bit also..... i've tried disabling digital driver thing at bootup...
device manager see its just fine.... I can access it with adb while the phone is booted up.... as soon as I reboot to fastboot screen the phone cannot be seen by adb devices..... still shows up just fine with no ! in device manager....
... is there anyway to push a stock image and load a factory stock image from the stock recovery? says it needs to be in /cache folder.... i tried pushing a stock image there but it tells me access is denied.... i tried enabling root.... says root not available on production builds..... im lost....
I just tried it on my xp machine and it worked just fine..... weird.. something with 7 64 bit? i tried pda net drivers, samsung, samsung naked 1.7.... all said they were working fine....
adb is for android or recovery
fastboot is for bootloader
adb won't recognise the device when it's in fastboot mode.
Try:
Code:
fastboot devices
And you don't need adb to unlock the bootloader, the command is:
Code:
fastboot oem unlock
So not entirely sure why you're chasing adb...
I am in the same boat, what happens for me is that fastboot doesnt even recognize the device. So all in all I can't oem unlock my device.
Using win7 64bit
j1mmyg88 said:
I am in the same boat, what happens for me is that fastboot doesnt even recognize the device. So all in all I can't oem unlock my device.
Using win7 64bit
Click to expand...
Click to collapse
The usual recommendation (and what worked for me) is to install PDANet first, just for the drivers. Then fastboot will see your device. You can remove PDANet afterwards and the drivers will remain.
copkay said:
The usual recommendation (and what worked for me) is to install PDANet first, just for the drivers. Then fastboot will see your device. You can remove PDANet afterwards and the drivers will remain.
Click to expand...
Click to collapse
fyi - this is what I did, with 64 bit windows 7 - the driver install didn't complete 'til I actually connected the GN in fastboot mode, then win7 installed the driver and I was able to run fastboot successfully.

No fastboot devices but can use adb devices.

Hey, I am having trouble pushing TWRP onto my op3 via fastboot. I managed to unlock my bootloader successfully but after that, I know cannot flash TWRP. When I type in "adb devices" It returns a string, however "fastboot devices" does nothing. I've uninstalled and re-installed oneplus usb, fastboot and adb drivers countless time and even reset my PC twice. Any ideas? This is really frustrating as I was on TWRP fine before I had to RMA my op3 where they put it back to stock. Any ideas? Thanks
I have the same problem ADB works but Fastboot not.... I have all drivers correct installed..
Rom: OOS 3.2.7
PC: Windows 10
Gesendet von meinem ONEPLUS A3003 mit Tapatalk
ELoTRIX said:
I have the same problem ADB works but Fastboot not.... I have all drivers correct installed..
Rom: OOS 3.2.7
PC: Windows 10
Gesendet von meinem ONEPLUS A3003 mit Tapatalk
Click to expand...
Click to collapse
Yeah me too, same ROM and PC OS. Very strange
CallumL701 said:
Yeah me too, same ROM and PC OS. Very strange
Click to expand...
Click to collapse
Got the same problem too, after unlocking the bootloader the fastboot devices cannot find anything
Tested several drivers and even another laptop :/
Rom: OOS 3.2.7
PC: Windows 10
But phone starts ok in OOS system?
If, yes, download TWRP 3.0.2.1 original & TWRP 3.0.2.1-19 modified. Put them in phone sd card. Download FLashify from Play store and flash recovery .img. Then go recovery to test if it works.
One of those will work.
inflames19 said:
Got the same problem too, after unlocking the bootloader the fastboot devices cannot find anything
Tested several drivers and even another laptop :/
Rom: OOS 3.2.7
PC: Windows 10
Click to expand...
Click to collapse
CallumL701 said:
Yeah me too, same ROM and PC OS. Very strange
Click to expand...
Click to collapse
I've solved that problem by installing Windows 7 on a Virtual Machine the phone Was recognized and has installed the drivers by itself. And fastboot was working
I don't know why fastboot is not working on Windows 10....
Thanks for the different solutions, I'll try it for myself.
But I'm still wondering why the unlock worked because there it used fastboot too
1
me too its says : Witting for devices !!!
Rom: OOS 3.2.7
PC: Windows 10
CallumL701 said:
Hey, I am having trouble pushing TWRP onto my op3 via fastboot. I managed to unlock my bootloader successfully but after that, I know cannot flash TWRP. When I type in "adb devices" It returns a string, however "fastboot devices" does nothing. I've uninstalled and re-installed oneplus usb, fastboot and adb drivers countless time and even reset my PC twice. Any ideas? This is really frustrating as I was on TWRP fine before I had to RMA my op3 where they put it back to stock. Any ideas? Thanks
Click to expand...
Click to collapse
Had the same issue, here's what fixed it for me:
(On Windows 10)
1 - Plug your device while on and install the OP3 drivers that appear as a removable disk, I reinstalled them also, so no harm in doing that again.
2 - Run admin command prompt from wherever you have your adb and fastboot
3 - get your device into fastboot/bootloader mode "adb reboot bootloader"
4 - press windows key + X and go to device manager, look for the Android device with exclamation mark
5 - right click on Android Device > update driver software > browse my computer... > let me pick... > look for Android and then select Android Fastboot Interface if memory serves me right.
And that's it. Fastboot should be recognized now. That's what worked for me when windows recognized adb but not fastboot, hope it helps out.
Remember to hit the thanks button if I helped you out.
1
rpsgrayfox said:
Had the same issue, here's what fixed it for me:
(On Windows 10)
1 - Plug your device while on and install the OP3 drivers that appear as a removable disk, I reinstalled them also, so no harm in doing that again.
2 - Run admin command prompt from wherever you have your adb and fastboot
3 - get your device into fastboot/bootloader mode "adb reboot bootloader"
4 - press windows key + X and go to device manager, look for the Android device with exclamation mark
5 - right click on Android Device > update driver software > browse my computer... > let me pick... > look for Android and then select Android Fastboot Interface if memory serves me right.
And that's it. Fastboot should be recognized now. That's what worked for me when windows recognized adb but not fastboot, hope it helps out.
Remember to hit the thanks button if I helped you out.
Click to expand...
Click to collapse
I've done everything U said but when it on the Bootloader it says waiting for device
Thank you to try solve the problem
Since there are a lot of people complaining I think the problem is bigger than we think :/ My OP3 nor OPO are seen
CallumL701 said:
Hey, I am having trouble pushing TWRP onto my op3 via fastboot. I managed to unlock my bootloader successfully but after that, I know cannot flash TWRP. When I type in "adb devices" It returns a string, however "fastboot devices" does nothing. I've uninstalled and re-installed oneplus usb, fastboot and adb drivers countless time and even reset my PC twice. Any ideas? This is really frustrating as I was on TWRP fine before I had to RMA my op3 where they put it back to stock. Any ideas? Thanks
Click to expand...
Click to collapse
Sir Mohd said:
I've done everything U said but when it on the Bootloader it says waiting for device
Thank you to try solve the problem
Click to expand...
Click to collapse
I'm sorry to hear it didn't work, I'd try to reinstall adb and fastboot then using Minimal Adb and Fastboot found in this thread http://forum.xda-developers.com/showthread.php?t=2317790
ELoTRIX said:
I've solved that problem by installing Windows 7 on a Virtual Machine the phone Was recognized and has installed the drivers by itself. And fastboot was working
I don't know why fastboot is not working on Windows 10....
Click to expand...
Click to collapse
Please tell us how you did That ,
Ty.
Sir Mohd said:
Please tell us how you did That ,
Ty.
Click to expand...
Click to collapse
I have just installed on my Windows 10, a Virtual Machine (VMware) with Windows 7 installed all driver oneplus 3 and adb+fastboot and it works
I have the same issue. Got my OP3 yesterday and have been trying in vain to get my Windows 10 install to recognise the phone in fastboot mode, but to no avail. I am unable to unlock my bootloader.
I think the problem is with Windows 10. My laptop did an update yesterday, I think that's the problem.
Got some news for you:
I was so frustrated that I decided to install Windows 7 over my Windows 10 and have a try.
Well what should I say: everything worked on the first try, without any problems with the original driver which comes with the op3 when you plugin the phone.
Hope I could help
It appears to be an issue with Windows 10 drivers. I have used an ancient install of Xubuntu on an older EeePC in order to unlock the bootloader and flash TWRP and SuperSU. I've still had no luck getting fastboot to be recognised on Windows 10, though on Xubuntu, it is recognised instantly with no issues.
inflames19 said:
Got some news for you:
I was so frustrated that I decided to install Windows 7 over my Windows 10 and have a try.
Well what should I say: everything worked on the first try, without any problems with the original driver which comes with the op3 when you plugin the phone.
Hope I could help
Click to expand...
Click to collapse
I'v Windows 7 Can you explain how ? and what the required files ?
Thank u
Sir Mohd said:
I'v Windows 7 Can you explain how ? and what the required files ?
Thank u
Click to expand...
Click to collapse
I'm not at my pc atm but I'll try my best:
If you plugin your op3 there will be a cd mounted with the setup for the driver.
I just installed this driver with the setup.exe (on a complete new instance of Windows 7).
After the installer was finished, I opened cmd.exe and could use adb and fastboot.

Uncloking bootloader on h815

Hello team,
I've been trying to unlock the bootloader of my device for the last couple of days. I have tried installing the drivers from LG suite, couple of drivers from the forum and google as well.
When i try to type in the command line oem device-ID i get "waiting for device"
According to the internet this is an issue with the drivers.
Can anyone suggest suitable ADB drivers ?
gogobaba said:
Hello team,
I've been trying to unlock the bootloader of my device for the last couple of days. I have tried installing the drivers from LG suite, couple of drivers from the forum and google as well.
When i try to type in the command line oem device-ID i get "waiting for device"
According to the internet this is an issue with the drivers.
Can anyone suggest suitable ADB drivers ?
Click to expand...
Click to collapse
did you select usb debuggin in developers options.?
when you go iinto fastboot did you allow phone to acces adb in phone screen?
Yes to both of your questions. I'm using windows 10 x64 with the latest drivers for my laptop

Hardbricked/Softbricked Zenfone 2 ZE551ML/Z00AD?

Hello!
After replacing mainboard in my Zenfone 2, I'm not able to flash anything through fastboot, beacuse adb can't regonize phone-Getting Windows 10 Error- Windows Can't regonize USB. Before, I unlocked bootlader and installed MM bootloader. I have installed Asus Usb drivers, Google Usb driver and Intel Android Usb driver. Help me please I love my Zenfone,but I did something wrong. :crying:
Yanun said:
Hello!
After replacing mainboard in my Zenfone 2, I'm not able to flash anything through fastboot, beacuse adb can't regonize phone-Getting Windows 10 Error- Windows Can't regonize USB. Before, I unlocked bootlader and installed MM bootloader. I have installed Asus Usb drivers, Google Usb driver and Intel Android Usb driver. Help me please I love my Zenfone,but I did something wrong. :crying:
Click to expand...
Click to collapse
try uninstalling and reinstalling drivers. what does it shows in device manager when you connect phone to pc?
In device manager it shows error with port.
Reinstalled drivers. Still nothing. http://imgur com/a/ezps8

Redmi Note 8T drivers for Windows 7

I'm trying to connect my Note 8T to my windows 7 to use software such as mpcsuite, tool-all-in-one and others.
I'm struggling to do it, Windows won't recognise it. I've tried all the drivers I've found in this forum and also googling, but no luck. When I connect the phone it does configure some device automatically, but there's always one missing that I cannot find drivers for: TRINKET-IDP _SN:XXXXX
The thing is that if I go into fast boot, then Windows will find the phone just fine and I can for example run the MiFlash Unlock app, but not when the phone is in any other state.
I haven't tried other versions of Windows as I have no other.
any suggestion what I'm missing here?
thanks!
johnsecada said:
I'm trying to connect my Note 8T to my windows 7 to use software such as mpcsuite, tool-all-in-one and others.
I'm struggling to do it, Windows won't recognise it. I've tried all the drivers I've found in this forum and also googling, but no luck. When I connect the phone it does configure some device automatically, but there's always one missing that I cannot find drivers for: TRINKET-IDP _SN:XXXXX
The thing is that if I go into fast boot, then Windows will find the phone just fine and I can for example run the MiFlash Unlock app, but not when the phone is in any other state.
I haven't tried other versions of Windows as I have no other.
any suggestion what I'm missing here?
thanks!
Click to expand...
Click to collapse
download minimal ADB and Fastboot and turn on usb debugging from developer options. Also accept the popup on screen when you connect phone to PC after this
I have the same problem, have you succeeded ?
Thank you
I have the same issue with my Note 8T
i had the same problem with my note8. try to google around 1 hour. & that's the ones topic about it. unfortunately it has no answer poor me
johnsecada said:
I'm trying to connect my Note 8T to my windows 7 to use software such as mpcsuite, tool-all-in-one and others.
I'm struggling to do it, Windows won't recognise it. I've tried all the drivers I've found in this forum and also googling, but no luck. When I connect the phone it does configure some device automatically, but there's always one missing that I cannot find drivers for: TRINKET-IDP _SN:XXXXX
The thing is that if I go into fast boot, then Windows will find the phone just fine and I can for example run the MiFlash Unlock app, but not when the phone is in any other state.
I haven't tried other versions of Windows as I have no other.
any suggestion what I'm missing here?
thanks!
Click to expand...
Click to collapse
Try downloading the Xiaomi unlocking tool, I didn't have problems with drivers, but I saw a messages about downloading drivers and "Driver already installed" for my phone within the application log.
Give that a try!
But problem with Note 8. I don't remember when it started, but on crDroid 6 it definitely worked.
After that I notice in device manager what it determinate as some SAMSUNG Adb Device with Clock World driver. I had ADB Universal Driver installed, after uninstalled everything start work fine.
I have a similar problem with note 8t too. I have Windows 10 x64 and when i put the phone on fastboot mode and plug on the pc nothing happens, nothing shows on the device manager. When the phone is in normal mode the pc recognizes it normally. I want to unlock the bootloader to change the rom to the global version, but neither Mi unlock tool or Mi flash tool recognizes it. Any tips from anybody?
scarlos89 said:
I have a similar problem with note 8t too. I have Windows 10 x64 and when i put the phone on fastboot mode and plug on the pc nothing happens, nothing shows on the device manager. When the phone is in normal mode the pc recognizes it normally. I want to unlock the bootloader to change the rom to the global version, but neither Mi unlock tool or Mi flash tool recognizes it. Any tips from anybody?
Click to expand...
Click to collapse
Use W7
W10 always have problems with some driver signature
loopypalm said:
Use W7
W10 always have problems with some driver signature
Click to expand...
Click to collapse
Thank you very much. I've installed W7 and the pc recognized the cel on fastboot mode. Mi unlock recognize it too, but now i have a message to wait 149 hours to unlock the bootloader. Just have to wait now or have some way to skip this?
Again, thank you very much.
scarlos89 said:
Thank you very much. I've installed W7 and the pc recognized the cel on fastboot mode. Mi unlock recognize it too, but now i have a message to wait 149 hours to unlock the bootloader. Just have to wait now or have some way to skip this?
Again, thank you very much.
Click to expand...
Click to collapse
you have to wait

Categories

Resources