hello, i have problem fastboot mode, it detect my phone but in device manager not Identify the device. only show (!Android)
but in adb it detect when turn on devices. i want unlockbootloader to install custom rom
MOD can close this thread. done by install driver Android device to Android bootloader interface (windows 10 pro)
Related
One N7, strictly stock, is recognised in Win 7 and in fastboot mode i.e no issue.
The other N 7 is root and unlock.
Under Win 7 home premium:
All of a sudden it is not recognised and device manager shows Android composite adb interface
but the windows driver is missing ( when I plug it Win 7 is not showing that a driver is installing).
There is no mention of N 7, not even a yellow exclamation point, let alone no mention of portable devices.
In adb mode the N 7 is recognised. Bootloader is accessible but fastboot devices does not show the N 7.
I cannot access CWM recovery 6.0.1.0 neither through bootloader nor from Rom manager.
This N 7 has stock JB 4.1.2 (JZ054K). I have installed SuperSU, Rootkeeper and Rom Manager.
Under Win 7 professional it is recognised, it shows in device manager and in adb but not in fastboot mode after going in bootloader mode, and still cannot access recovery mode (waiting for device if I try to do that).
I need help to solve this issue. Thank you
I prefer not to use a toolkit.
Hi,
Despite my best efforts device manager still shows yellow at Android compesite device..
In ADB SHELL MODE it won't list the device on ADB DEVICES Command.
Can someone help me with the right USB / fastboot drivers for Mi A1 for Windows 10 Pro
Managed to get the fastboot working.
vu2pmc said:
Hi,
Despite my best efforts device manager still shows yellow at Android compesite device..
In ADB SHELL MODE it won't list the device on ADB DEVICES Command.
Can someone help me with the right USB / fastboot drivers for Mi A1 for Windows 10 Pro
Click to expand...
Click to collapse
https://forum.xda-developers.com/showthread.php?t=2588979
Compatibility mode, run as admin, you can also try with another source of adb files, because I had issues with the one from magisk manager.
Not working for me
After installing pie update now my phone is not recognised as ADB or fast boot mode
All drivers are properly installed
In device manager ,ADB and FASTBOOT is shown (device is connected )
ADB works correctly when device is on
But it doesn't when it is in recovery or download mode
Use minimal adb last version. Then open it and cmd.exe open by run administration. I think it will be work properly.
Device LG G6
Model : G600LR30c
I was thinking of installing a custom os which requires TWRP recovery installed in the device which recuires the device to be bootloader unlocked. But when I use the command "adb reboot bootloader" in minimal adb the device never goes to boot menu, instead it simply restarts and then if I put the command "fastboot oem device-id", it never shows the id and keeps showing "waiting for a device" instead. Please help me resolve this.
P.S: I also tried to access boot menu using key combo. but in vain
If you can put the phone in Fastboot mode during powerup or restart, it's a Windows issue if it don't work. Windows must recognize the device via PnP and install a different set of drivers each time the usb mode changes. If it don't work when the phone is already in Fastboot mode, try different drivers.
I once had two sets installed, that from the device manufacturer and that ripped from the Google SDK(on XDA). This way all usb modes worked, but Windows couldn't perform the Reboot Fastboot/Recovery commands fom ADB like is the case here and the Windows software had, suitable drivers installed, to be able to access the phone if it was already set to Fastboot/Download etc mode.
That was a TI OMAP based LG L9 under Win7. Starting with Windows 8.1, Fastboot was no longer working at all, you could only perform disaster recovery via D/L mode with a stock image and then root the thing with a one-click rooter to be able to install a recovery from Android etc etc, but that was due to the no longer supported TI SoC. But Qualcomm also tends to completely abandon older SoCs.
I'm dumbfounded. I have unlocked bootloaders and rooted for years. Just got my OP8P.
I also have a new Microsoft Surface Pro with Windows 10.
I installed ADB, installed Fastboot.
Unlocked developer options and turned on USB Debugging and Developer Unlock.
Windows device manager shows ADB INTERFACE for the my device in device manager.
I can open can open Power Shell and/or the CMD prompt. I've done both.
I can type adb devices in the command prompt and I CAN see my device.
I can reboot it fastboot from the CMD prompt so I KNOW Wndows sees my phone.
BUT ONCE I'M IN FASTBOOT, the problem starts.
Fastboot does NOT see my device. Commands return the words "Waiting for Device..."
I BELIEVE the issue is with the drivers. When I boot into Fastboot, my device location changes in Device Manager from USB>ADB Interface to Portable Devices>Android.
The Android Device icon has a yellow triangle with an exclamation mark. It's says the driver for this device is not installed. But everything was working fine and the drivers were fine while the device was powered up normally.
If I try to manually install the driver it fails and says "cannot update drivers for your Android".
What heck is going on? What did I do wrong?
I've uninstall and reinstalled the drivers direct from Oneplus. I've uninstall and reinstalled the drivers direct from Google. 'I ve uninstall and reinstalled the drivers direct from Windows.
Why can't device and drivers be recognized in Fastboot. And why can't I update the drivers for the "Android" device?