Hi guys,
i hope anyone has a solution for me here.
So i have this weired case where the phone shows up in ADB but not in fast boot in the windows device manager when using the Recovery/Fastboot mode.
I already tested 3 different PCs and multiple cables. I as well got lucky and a friend of mine got a note 9 as well. With this the Fastboot and ADB show so it shouldn´t be a driver issue.
Can anyone help me with this problem because i would have wanted to get TWRP on this phone.
...I think it's ok when it shows up in ADB. Did you hear the windows connection sound on the PC when you plug in the device?
You need to install the driver.
Without it, the phone is only detected in adb:
http://bigota.d.miui.com/tools/xiaomi_usb_driver.rar
Don't forget to disable Driver Digital Signature enforcing in Win10.
kalehrl said:
You need to install the driver.
Without it, the phone is only detected in adb:
http://bigota.d.miui.com/tools/xiaomi_usb_driver.rar
Don't forget to disable Driver Digital Signature enforcing in Win10.
Click to expand...
Click to collapse
As I wrote before, I got 2x the same Phone on hand one gets recognized and all by windows and shows up with the correct device driver in fastboot. The other phone doesn't show a thing, windows isn't even recognizing that it got connected in fastboot.
Strange is that the phone that doesn't get recognized in fastboot mode does get recognized in edl and adb mode.
So in the end I am looking for an information if this could be fixed or if the main board is some kind of damaged.
opg2000 said:
...I think it's ok when it shows up in ADB. Did you hear the windows connection sound on the PC when you plug in the device?
Click to expand...
Click to collapse
No sadly not, with the second device I could hear it connect and show correctly. The problem phone shows in adb and edl but not fastboot
Knoppersd said:
As I wrote before, I got 2x the same Phone on hand one gets recognized and all by windows and shows up with the correct device driver in fastboot. The other phone doesn't show a thing, windows isn't even recognizing that it got connected in fastboot.
Strange is that the phone that doesn't get recognized in fastboot mode does get recognized in edl and adb mode.
So in the end I am looking for an information if this could be fixed or if the main board is some kind of damaged.
Click to expand...
Click to collapse
I got the same issue but by installing the above driver and changing the new type-C cable.... helped me and solved my problem......
Knoppersd said:
Hi guys,
i hope anyone has a solution for me here.
So i have this weired case where the phone shows up in ADB but not in fast boot in the windows device manager when using the Recovery/Fastboot mode.
I already tested 3 different PCs and multiple cables. I as well got lucky and a friend of mine got a note 9 as well. With this the Fastboot and ADB show so it shouldn´t be a driver issue.
Can anyone help me with this problem because i would have wanted to get TWRP on this phone.
Click to expand...
Click to collapse
have yu got the solution of this because I am also facing the same issue.
No sorry, the phone is still dead and i moved on from it.
kalehrl said:
You need to install the driver.
Without it, the phone is only detected in adb:
http://bigota.d.miui.com/tools/xiaomi_usb_driver.rar
Don't forget to disable Driver Digital Signature enforcing in Win10.
Click to expand...
Click to collapse
Managed to connect my Redmi Note 9 (merlin) to Fastboot with my Windows PC and install stock ROM with MiFlash thanks to this driver.
To install the driver i did:
1. Download driver from link above (ignored Firefox's warning of potential risk).
2. Unpack the rar file.
Now we must disable Windows Driver Signature for the driver to install correctly. It will only be disabled during a single boot and the automatically revert to active and secure again after reboot.
3. Restart Windows while holding the "Shift" key through Start Menu -> Power ->Restart.
4. The blue Windows Advanced Boot menu should appear. Select: "Troubleshoot" -> "Advanced Options" -> "Startup Settings" -> "Restart"
5. Computer will restart to the Startup Settings Menu. Press number "7" key on your keyboard to select "Disable driver signature enforcement". Windows then will boot to Desktop.
6. Search and open "Device Manger" on Windows menu.
7. Under "Other devices" right click "Android" (for me it appeared with a caution sign because of the default driver error) and then "Update driver".
8. Browse my computer for Drivers -> "Let me pick from a list..." -> Select "ADB Interface" (not sure if it is important which type of device is selected) -> "Have Disk".
9. Browse the downloaded driver folder that was unpacked on step 2 and select "android_winusb.inf" (this is the Windows driver).
10. On the Windows Security prompt select "Install this driver anyway".
From here on Fastboot mode should be recognized by the PC and you can install a ROM using MiFlash or following any other guide to install via Fastboot in this forum.
Related
hey guys this is the new thread as the previous thread can not be monitored now as the owner of that thread @Ivan93tm don't have xperia go anymore
so here i start
requirements
Download and install JDK tools form Java here.
Download SDK android from this site.
usb_driver.zip - 8.68 MB
for installing the new sdk in windows 8
extract the sdk to a convenient place
run sdk manager and download Extras file "google usb drivers".
if sdk manager don't run then follow these steps
open sdk/tools/android.bat with your favorite editor.
find this code
set java_exe=
call lib\find_java.bat
if not defined java_exe goto :EOF
then replace this with
set java_exe="D:\Program Files\Java\jdk1.7.0_07\bin\java.exe" (make sure you give your java.exe file path)
save android.bat then run android.bat as administrator and you are done your sdk will run.
now follow the steps
go to settings in windows 8 then go to general then in advanced setup click restart now.
then go to troubleshoot --> Advanced option --> Startup settings --> Restart.
then you will get a window with some options choose number 7. Disable Driver Signature Enforcement.
or you can do it through cmd lines.
open cmd as administrative.
type "bcdedit /set testsigning on" and restart PC
and when bellow steps are done then at the end type this type "bcdedit /set testsigning off" in cmd and restart PC
power off you phone.
go to control panel --> system and Security --> System --> Device manager.
now connect your phone in fastboot mode i.e connecting to usb while holding the volume + button
USE USB 2.0 ONLY.
now S1 fast boot device is appear click fastly on it and update driver.
now when phone turn in normal mode unplag phone (keep open update driver windows).
select driver from folder
then select "chose manualy from a list of driver in computer".
browse from disk and select "android_winusb.inf" from "...\android-sdk\extras\google\usb_driver" and select "android bootloader interface.
before click next plug again the phone in fastboot mode.
click next and your done.
EDIT :
For WINDOWS 8.1
just update your windows from store
or download from here
credits to @Ivan93tm
One had success with different method:
http://forum.xda-developers.com/showthread.php?p=45550695#post45550695
ChikeD said:
One had success with different method:
http://forum.xda-developers.com/showthread.php?p=45550695#post45550695
Click to expand...
Click to collapse
he used flashtool but flashtool doesn't work for all including me i tried installing driver using flashtool in bot win7 and win8 but failed and finally i choose this method
garvitdelhi said:
he used flashtool but flashtool doesn't work for all including me i tried installing driver using flashtool in bot win7 and win8 but failed and finally i choose this method
Click to expand...
Click to collapse
Didn't work for him either before he followed the procedure.
ChikeD said:
Didn't work for him either before he followed the procedure.
Click to expand...
Click to collapse
ok cool but i have the driver right now i am going to try that method on another pc if it gives success then i am going to add that method also using his permission
garvitdelhi said:
ok cool but i have the driver right now i am going to try that method on another pc if it gives success then i am going to add that method also using his permission
Click to expand...
Click to collapse
I don't think he is the one posted if first, ask him where he found it.
I can't install because "S1 fast boot device" doesn't show up. The only thing that show up in Device Manager for me is "Unknown USB Device (Device Failed Enumeration). Does anyone know what this means?
registradus said:
I can't install because "S1 fast boot device" doesn't show up. The only thing that show up in Device Manager for me is "Unknown USB Device (Device Failed Enumeration). Does anyone know what this means?
Click to expand...
Click to collapse
Are you connecting your phone in fastboot mode .. ? and are you using usb 2.0 port
garvitdelhi said:
Are you connecting your phone in fastboot mode .. ? and are you using usb 2.0 port
Click to expand...
Click to collapse
Yeah I've tried everything. Connects fine normally.
tried
different USB ports, 2.0 and 3.0
enabling USB debugging mode
uninstalling drivers
Light on phone turns green, but then just goes into charging mode.
I'm on Windows 8 64
registradus said:
Yeah I've tried everything. Connects fine normally.
tried
different USB ports, 2.0 and 3.0
enabling USB debugging mode
uninstalling drivers
Light on phone turns green, but then just goes into charging mode.
I'm on Windows 8 64
Click to expand...
Click to collapse
green...??? it must be voilet or blue while pluging in your phone your phone must be switched off and then connect to usb whole pressing the volume up key not down
garvitdelhi said:
green...??? it must be voilet or blue while pluging in your phone your phone must be switched off and then connect to usb whole pressing the volume up key not down
Click to expand...
Click to collapse
Really? I've got Xperia U, PC Companion tells me to press volume down...
---------- Post added at 05:45 AM ---------- Previous post was at 05:35 AM ----------
garvitdelhi said:
green...??? it must be voilet or blue while pluging in your phone your phone must be switched off and then connect to usb whole pressing the volume up key not down
Click to expand...
Click to collapse
Tried holdin volume up instead, light goes blue, but still get "USB device not recognised"
green is for flashmode and voilet is for fastboot mode and try with volume up button pcc uses flashmode so it tells you to put with volume down and did your phone is detected by pcc if not try installing pcc again and then disable windows verification and then try again
Tried holdin volume up instead said:
Expriece the same bug (
anyone can help me, Everything is installed. PC Companion, Drivers, Flashtool
Click to expand...
Click to collapse
wellwits said:
Expriece the same bug (
anyone can help me, Everything is installed. PC Companion, Drivers, Flashtool
Click to expand...
Click to collapse
Have you tried what the OP says?
Try installing the drivers from flashtool with the steps in this post?
Good day is this woking on wndows 8.1 too ??
On my Windows 8.1 64-bit at step 8 it doesn't recognize it as S1 fastboot device.
When I select android_winusb.inf and click OK, it says the folder specified doesn't contain a compatible driver for my device, make sure it is designed to work with Windows x64-based systems.
So I can't. ;(
2Radon said:
On my Windows 8.1 64-bit at step 8 it doesn't recognize it as S1 fastboot device.
When I select android_winusb.inf and click OK, it says the folder specified doesn't contain a compatible driver for my device, make sure it is designed to work with Windows x64-based systems.
So I can't. ;(
Click to expand...
Click to collapse
same problem with my windows 8.1 64bit
Ok So i must sty on win 8
not working
im on win 8.1 & not worked for me
now in win Xp not working too
i think flash ic is damaged
usb not recognized in win xp in flash & fastboot mod :crying: :crying:
same problem here. device manager displays unknwon device and wont accept the .inf - file...
Hi my neo l not connecting in fastboot mode. I have updated all drivers but when i connect phone in fastboot mode a popup shows unrecognised usb device. Aldo not showing anything when i typed" fastboot devices " in cmd.
Mani-saini said:
Hi my neo l not connecting in fastboot mode. I have updated all drivers but when i connect phone in fastboot mode a popup shows unrecognised usb device. Aldo not showing anything when i typed" fastboot devices " in cmd.
Click to expand...
Click to collapse
Hello friend, try to connect to another USB port on your computer, if it does not work disconnect any USB devices you may have connected and try again, if still don't work is because drivers are not installed, try re-install them again, what windows version are you using, if it is Windows 8 there is special procedure how to install fastboot drivers,
Good luck
Yeah first make sure you see it in the Device Manager on Windows.
galarpo said:
Hello friend, try to connect to another USB port on your computer, if it does not work disconnect any USB devices you may have connected and try again, if still don't work is because drivers are not installed, try re-install them again, what windows version are you using, if it is Windows 8 there is special procedure how to install fastboot drivers,
Good luck
Click to expand...
Click to collapse
I have instaled all fastboot drivers. Also changed the cable.and in device manager it showing unknown device.
I am using windows 8 .which method for installing drivers???
how to
Mani-saini said:
I have instaled all fastboot drivers. Also changed the cable.and in device manager it showing unknown device.
I am using windows 8 .which method for installing drivers???
Click to expand...
Click to collapse
1- Hold SHIFT and restart you computer, always holding SHIFT or run this "shutdown /r /o"
2- You should be now on "Advanced Startup options", select "Troubleshoot" --->"Advanced Options"--->"Startup settings"--->"restart"
3- Next select option 7
4- plug your phone to computer in fastboot mode and install flashtool drivers, remenber to say yes on the windows appearing during installation, after everything is installed, restart your computer and problem solved.
Dear All,
I have been struggling to install fastboot drivers on Windows 10 for my Phone (D6503) for almost a month now.
I tried many of the options suggested here like disabling Driver signature enforcement, using the drivers they suggested, etc etc but nothing has worked yet.
Sony Flashtool only recognizes ADB and not Fastboot.
Request for your inputs on this.
Thank you!
Are you using latest version of flashtool? I had this problem with the old version and then I installed drivers by disabling driver signature enforcement. Now it works fine.
AlanDS said:
Are you using latest version of flashtool? I had this problem with the old version and then I installed drivers by disabling driver signature enforcement. Now it works fine.
Click to expand...
Click to collapse
I did try that, and it installs successfully (even with the old version) but FlashTool does not recognize the device in Fastboot when I do a "Check Drivers" in tool and cmd prompt as well. Am I missing something here?
What is the Device Manager entry for Z2 Fastboot mode ? (For ADB, I get sa111 or so)
Thanks!
http://i.imgur.com/Ccx8xgm.png
http://i.imgur.com/RGK54dH.png
Any inputs on this issue will be greatly appreciated!
Are you holding volume down as you plug in the usb cable?
mmceorange said:
Are you holding volume down as you plug in the usb cable?
Click to expand...
Click to collapse
Yup.
It was a noob error on my part. I thought it will show both ADB and Fastboot devices simultaneously.
Now the Device Manager shows 'Sony Fastboot Device' upon connecting it in Fastboot mode. Hopefully I can now root it without any more problems.
Thanks!
pai.pradeep said:
Dear All,
I have been struggling to install fastboot drivers on Windows 10 for my Phone (D6503) for almost a month now.
I tried many of the options suggested here like disabling Driver signature enforcement, using the drivers they suggested, etc etc but nothing has worked yet.
Sony Flashtool only recognizes ADB and not Fastboot.
Request for your inputs on this.
Thank you!
Click to expand...
Click to collapse
Walkthrough
Hold down either SHIFT key while tapping or clicking on Restart, available from any Power icon.
Tip: Power icons are available throughout Windows 10 and Windows 8 as well as from the sign-in/lock screen.
Note: This method does not seem to work with the on-screen keyboard. You'll need to have a physical keyboard connected to your computer or device to open the Advanced Startup Options menu this way.
Wait while the Advanced Startup Options menu opens.
-troubleshoot
-advanced options
-startup settings
-(press 7) disable driver signature enforcement
Wait for the opening of the windows
download and install z2 drivers
Search forum [Drivers] FlashTool Xperia Driver Pack (v1.5)
hacimax said:
Walkthrough
Hold down either SHIFT key while tapping or clicking on Restart, available from any Power icon.
Tip: Power icons are available throughout Windows 10 and Windows 8 as well as from the sign-in/lock screen.
Note: This method does not seem to work with the on-screen keyboard. You'll need to have a physical keyboard connected to your computer or device to open the Advanced Startup Options menu this way.
Wait while the Advanced Startup Options menu opens.
-troubleshoot
-advanced options
-startup settings
-(press 7) disable driver signature enforcement
Wait for the opening of the windows
download and install z2 drivers
Search forum [Drivers] FlashTool Xperia Driver Pack (v1.5)
Click to expand...
Click to collapse
Thanks, managed to do install it
pai.pradeep said:
Yup.
It was a noob error on my part. I thought it will show both ADB and Fastboot devices simultaneously.
Now the Device Manager shows 'Sony Fastboot Device' upon connecting it in Fastboot mode. Hopefully I can now root it without any more problems.
Thanks!
Click to expand...
Click to collapse
Heh, we're all a noob at some point
btw, another similar bug is when you use FlashTools "Fastboot Restart" option, or Fastboot boot into recovery.
Sometimes your Device get's stuck!
You see the blue LED on the device but your device won't be seen by the computer.
Only way to solve this error is by using another USB port on the computer.
Does anyone still have this file available to download? [Drivers] FlashTool Xperia Driver Pack (v1.5) Seems DoomLords links are no longer valid. Thank you in advance
my mi a3 is not recognized when in fastboot mode by the computer
I had this problem just some couple of hours ago and what you have to do (or at least it solved this in my end) is go to Manage Devices, scroll to TP-Link Android Phone, expand it and right click Android Bootloader Interface and uninstall without deleting the driver, then refresh for hardware changes and it will install the driver again and fastboot will work this time.
Jhon_Locke said:
I had this problem just some couple of hours ago and what you have to do (or at least it solved this in my end) is go to Manage Devices, scroll to TP-Link Android Phone, expand it and right click Android Bootloader Interface and uninstall without deleting the driver, then refresh for hardware changes and it will install the driver again and fastboot will work this time.
Click to expand...
Click to collapse
I'm facing this same issue. Please can you tell me where I can see Manage Devices on my computer? I'm using Windows 10.
I had the same issue. I tried all the methods that i researched. Even tried virtual machines running Windows 7 and Linux but same thing happens. I thought it was a Windows 10 issue. Til 1 day i tried to use a different cable, and DAMN! that fixed it.
same here, recognized as adb device but not recognized by fastboot.
I'm using Linux and fastboot work well.
The problem is that with lsusb no device is displayed, so I think it's a bootloader issue, is the bootloader environment corrupted? is there other setting to enable other then enable usb debug and enable OEM unlock?
Go to device manager right klik on android device and update the driver automatic.thats all.
U had the same problem and i solved with this.
Probably you don't have installed correctly fastboot drivers
Barbiox Dogg said:
I'm facing this same issue. Please can you tell me where I can see Manage Devices on my computer? I'm using Windows 10
Click to expand...
Click to collapse
im late but if u still need to know then hold down windows and x, a list should come up and then click device manager from there
deniloo said:
my mi a3 is not recognized when in fastboot mode by the computer
Click to expand...
Click to collapse
Just Update the device driver probably be showing under others in Device manager.
Visit this site to get the driver for your device. https://www.getdroidtips.com/download-latest-xiaomi-usb-drivers/
Dears,
How has this issue just "disable driver signature enforcement"
Search youtube on this and follow instruction
Say thanks if it help please,
Hi,
My Nord 2 have latest update DN2103_11_A.17, and I wanted to enable VoLTE.
My computer can't detect my phone in ADB when in recovery mode, it detects only when just powered on normaly and connected.
I have latest Android plateform tools installed on computer.
Any Idea of what's wrong ?
Thanks
Adb drivers and permissions.
Try in Linux, easier
I have exactly the same problem on my OneNeplus Nord 2. I installed the MediaTek_Preloader_USB_VCOM_Drivers drivers in auto mode and even in manual mode under Windows 10. When I type adb reboot recovery the smartphone reboots in recovery mode even if it tells me seems strange see photo (sorry very small text...) but then no other orders are accepted. Same problem in bootloader mode. So I can't unlock the bootloader. Any help is welcome...
Hey I had the same issue with fastboot device not showing up. Fastboot with other devices on my PC had never been an issue.
This Fixed it for me:
Open "Device Manager" from the Windows start menu.
Your device should be listed there as "Android Device" (with a yellow indication for missing driver)
Right click the device and select "Update Driver".
Click Browse my computer for drivers.
Click Let me pick from a list of available drivers on my computer.
From the list select "Android Bootloader Interface". It is possible that you need to deselect the "Show compatible hardware" button.
Good luck.
cukierkas said:
Adb drivers and permissions.
Try in Linux, easier
Click to expand...
Click to collapse
Hi, thanks I'll try. Any specific driver for Linux?
I've read that adb in recovery mode doesn't work since A.14 update, and I'm on A.17. Anyone Can confirm that?