SOLVED: Issue fixed by using an USB 2.0 Port, don't use USB 3.0, it has some issues.
I've searched everywhere for a fix and still have not been able to make this work, this are the steps I have taken:
> I've created an MI Account with "Sync" and "Find Device" options enabled
> Enabled "OEM unlocking", "USB debugging", "USB debugging (Security settings)" on Developer options
> I've added my account and device on "MI Unlock status"
> Downloaded & installed ADB Driver, Mi PC Suite and Qualcomm Driver following the steps on this website:
Flashxiaomi website pokcophone f1 usb driver (can't type link here)
(After Android ADB Interface is installed it says that it might not work correctly and the device can not be started (Code 10) as shown on one of the pictures of the guide above)
> Downloaded MIUI Unlock software via the official website zip file named "miflash_unlock-en-4.5.514.47"
> Moved MIUI Unlock file to C:
> Ran as admin "MiUsbDriver" from the previous downloaded folder in order to install drivers
> Turn off my device and set it into fastboot mode
> Devices Manager > Android Phone > Android Bootloader Interface > driver tab proprieties show driver provider is "Xiaomi Technology, Inc.", driver date is "11/3/2016", and driver version is "16.0.0.0".
> Installed android_winusb.inf on MIUI Unlock | driver | win10 folder
> Ran as admin "miflash_unlock" and at this point my phone disconnects from my PC, phone shows "Press key to shutdown" on screen and by clicking the settings option on the MIUI application it tells me to click the button to install the drive
Other informations:
My pc is using intel, not AMD
What can I do?
Try unlock with windows 7 and usb port 2.0
tiennhu89 said:
Try unlock with windows 7 and usb port 2.0
Click to expand...
Click to collapse
That might be the issue, I'm on windows 10 and usb port 3.0, ill give it a try
Edit: It worked with usb 2.0 port!
Thanks, issue solved.
eldesaro123 said:
That might be the issue, I'm on windows 10 and usb port 3.0, ill give it a try
Edit: It worked with usb 2.0 port!
Thanks, issue solved.
Click to expand...
Click to collapse
Congratulations. :highfive:
Related
This is a working fix for the Xperia P Flashmode/Fastboot on Windows 8.1.
Disclaimer: I'm not the original author of this fix. Use it at your own risk.
All credit goes to Samyak Ranjan over at Droid Now. LINK
Note: Please double check in Device Manager if you have Intel eXtensible Host Controller under the Universal Serial Bus Controllers. It's listed as Intel(R) USB 3.0 eXtensible Host Controller.
Note 2: You will need to have a USB 3.0 and a USB 2.0 ports for this to work. USB 3.0 for the fix and the 2.0 to install the S1Fastboot Driver.
Here are the steps:
1. Install the XP default drivers included in the Flashtool. It's in the FLASHTOOL\DRIVERS folder in wherever you installed it.
2. Download the attachment I have included in this post. It's the official Intel Drivers for USB 3.0 Driver: Intel® USB 3.0 eXtensible Host Controller Driver for Intel® 7 Series/C216 Chipset Family. I've already included the modded files that works for Windows 8 and 8.1.
3. Disable Signing Reinforcement in Windows. Hit WINDOWS + C, go to SETTINGS ---> PC Settings ---> Click the Search button ---> Type in "advanced startup options ---> Click "Change advanced startup options" ---> Click the button that says "Restart".
4. After it reboots, choose Troubleshoot ---> Advanced options ---> Startup settings ---> Click Restart ---> Hit 7 on your keyboard (Disable driver signature enforcement). Your computer will Reboot again, log in as normal.
5. Open Device Manager.
6. Go to Universal Serial busses at the end and double click “Intel USB 3.0 eXtensible controller”. Click on Drivers in the New window which opens.You should see that the Drivers are provided by Microsoft.
7. Now click “Update Driver” and then select “Browse my computer for driver software”. Next choose “Let me pick from a list of device drivers on my computer” and select “Have Disk”.
8. In the Window that pops up titled “Install From Disk” choose “Browse” and navigate to the location where we replace the attachment.
("...\Intel(R)_USB_3.0_eXtensible_Host_Controller_Driver\Driver_Installer\Drivers\Win7\x64\") Select iusb3xhc.inf and click ok.
9. Ignore all warnings and install the drivers. After installing, Reboot the computer with the same procedure as Step 3 & 4.
Note: At this stage any devices you have connected to USB 3.0 hub will cease function. So fair warning. They will be fixed after you finish.
10. On opening the device manager, you should see an Unknown device. If you already had one before, you need to cross-check every unknown device to find the one we need. Double click each such device and go to the 3rd tab “Details”. Find the Value “VID_8086″. If you only have one listed unknow device it's that one even if it does not have "VID_8086".
11. After finding the correct device, choose “Update Driver” then click “Browse my computer”, Windows will ask you to identify the type of device, scroll down and select “Universal Serial Bus Devices”.
12. Click next, choose “Have Disk”, “Browse” and select the modified iusb3hub.inf that we placed in the same folder earlier. Ignore all warnings and install the drivers.
13. Restart the computer normally and look at the driver tab for the “Intel(R) USB 3.0 eXtensible Host Controller” and the “Intel(R) USB 3.0 Root Hub” to confirm that you are now running the Intel drivers instead of the Microsoft ones.
___________________________________________________________________________________________________________________
Now plug in your XP while holding down, the S1Boot Fastboot Driver should now install. I've double checked it via Sony Update Service and Flashtool 64. Both now register my XP.
EDIT: If the file is corrupted, here's the Mediafire link. Click!
kyzn said:
This is a working fix for the Xperia P Flashmode/Fastboot on Windows 8.1.
Disclaimer: I'm not the original author of this fix. Use it at your own risk.
All credit goes to Samyak Ranjan over at Droid Now. LINK
Note: Please double check in Device Manager if you have Intel eXtensible Host Controller under the Universal Serial Bus Controllers. It's listed as Intel(R) USB 3.0 eXtensible Host Controller
Here are the steps:
1. Install the XP default drivers included in the Flashtool. It's in the FLASHTOOL\DRIVERS folder in wherever you installed it.
2. Download the attachment I have included in this post. It's the official Intel Drivers for USB 3.0 Driver: Intel® USB 3.0 eXtensible Host Controller Driver for Intel® 7 Series/C216 Chipset Family. I've already included the modded files that works for Windows 8 and 8.1.
3. Disable Signing Reinforcement in Windows. Hit WINDOWS + C, go to SETTINGS ---> PC Settings ---> Click the Search button ---> Type in "advanced startup options ---> Click "Change advanced startup options" ---> Click the button that says "Restart".
4. After it reboots, choose Troubleshoot ---> Advanced options ---> Startup settings ---> Click Restart ---> Hit 7 on your keyboard (Disable driver signature enforcement). Your computer will Reboot again, log in as normal.
5. Open Device Manager.
6. Go to Universal Serial busses at the end and double click “Intel USB 3.0 eXtensible controller”. Click on Drivers in the New window which opens.You should see that the Drivers are provided by Microsoft.
7. Now click “Update Driver” and then select “Browse my computer for driver software”. Next choose “Let me pick from a list of device drivers on my computer” and select “Have Disk”.
8. In the Window that pops up titled “Install From Disk” choose “Browse” and navigate to the location where we replace the attachment.
("...\Intel(R)_USB_3.0_eXtensible_Host_Controller_Driver\Driver_Installer\Drivers\Win7\x64\") Select iusb3xhc.inf and click ok.
9. Ignore all warnings and install the drivers. After installing, Reboot the computer with the same procedure as Step 3 & 4.
Note: At this stage any devices you have connected to USB 3.0 hub will cease function. So fair warning. They will be fixed after you finish.
10. On opening the device manager, you should see an Unknown device. If you already had one before, you need to cross-check every unknown device to find the one we need. Double click each such device and go to the 3rd tab “Details”. Find the Value “VID_8086″. If you only have one listed unknow device it's that one even if it does not have "VID_8086".
11. After finding the correct device, choose “Update Driver” then click “Browse my computer”, Windows will ask you to identify the type of device, scroll down and select “Universal Serial Bus Devices”.
12. Click next, choose “Have Disk”, “Browse” and select the modified iusb3hub.inf that we placed in the same folder earlier. Ignore all warnings and install the drivers.
13. Restart the computer normally and look at the driver tab for the “Intel(R) USB 3.0 eXtensible Host Controller” and the “Intel(R) USB 3.0 Root Hub” to confirm that you are now running the Intel drivers instead of the Microsoft ones.
___________________________________________________________________________________________________________________
Now plug in your XP while holding down, the S1Boot Fastboot Driver should now install. I've double checked it via Sony Update Service and Flashtool 64. Both now register my XP.
Click to expand...
Click to collapse
can u provide for usb 2.0 because my phone dosent connect in usb 2.0 also and also after i connect my phone it dosent show up as S1Boot Fastboot instead it show that "driver enumeration failed".
What if I only have USB 2.0 on my computer?
Just disable driver signing as per instructions above nothing special for USB 2.0 I have covered windows 8 drivers many times on this forum I also asked for it to be sticky but no1 will make it so every1 on windows 8/8.1 will have the same problem
Sent from my Xperia Go using xda app-developers app
can you re-upload the drivers its corrupted, thanks
nagarjuna93 said:
can u provide for usb 2.0 because my phone dosent connect in usb 2.0 also and also after i connect my phone it dosent show up as S1Boot Fastboot instead it show that "driver enumeration failed".
Click to expand...
Click to collapse
nanoleet said:
What if I only have USB 2.0 on my computer?
Click to expand...
Click to collapse
Sorry, but currently the fix I found was for UBS 3.0 only. Did you already try the other fixes here in XDA? Some of them worked for USB 2.0.
In my case it was a combination of this fix, and installing the S1Fastboot driver via USB 2.0.
nosmaster said:
Just disable driver signing as per instructions above nothing special for USB 2.0 I have covered windows 8 drivers many times on this forum I also asked for it to be sticky but no1 will make it so every1 on windows 8/8.1 will have the same problem
Sent from my Xperia Go using xda app-developers app
Click to expand...
Click to collapse
That did not work for me. ADB drivers installed but not the Fastboot, so I thought I'd share the way that did.
hrashdan said:
can you re-upload the drivers its corrupted, thanks
Click to expand...
Click to collapse
Done.
Work for me!!! Thanks
Only USB 3.0, right?
Sent from my Xperia Sola using xda premium
manudo said:
Only USB 3.0, right?
Sent from my Xperia Sola using xda premium
Click to expand...
Click to collapse
Yes.
Installing the hub driver causes BSOD with MEMORY_MANAGEMENT error
Device: surface pro 1
For those with intel 8/c220 usb series you may have a look to
http://plugable.com/2012/12/01/windo...#comment-19066
Andrew (thanks) submitted there, in his comment, modified drivers in December 2013 for the Intel 8&7/c series
Be sure to use the right one because it could be a big mess (my experience)
see my post here (i tried to use 7c series drivers given in that link above,and 8 series one with the trick given a the begining by the initial writer
) big mess, only the Andrew modified ones for my 8Cseries worked :
http://forum.xda-developers.com/showthread.php?p=49426792
bountygiver said:
Installing the hub driver causes BSOD with MEMORY_MANAGEMENT error
Device: surface pro 1
Click to expand...
Click to collapse
Those are the modded drivers specifically made to support Intel 7 USB 3.0 ports. Do you even have the specific hardware those drivers were made for?
Thanks.. was trying to flash my old pro after a long time and tried everything.. this was the only thing that worked..
This worked for me on Windows 8.1 x64.
However, I had originally "Renesas eXtensible Host Controller" installed in my device manager so I downloaded the latest Renesas USB 3.0 drivers in stead of the Intel drivers but it worked perfectly afterwards!
after installing the driver all my usb devices stopped working. i cannot use my mouse and keyboard and cannot login to windows... ay help how i could fix it?
molnartibor said:
after installing the driver all my usb devices stopped working. i cannot use my mouse and keyboard and cannot login to windows... ay help how i could fix it?
Click to expand...
Click to collapse
go to your Bios USB settings and disable xHCI, that worked for me & I was able to do a system restore
Any info of working fastboot driver for Windows 10? Those posted in OP not accepted.
I'm new to CyanogenMod & It needs new driver for ADB connection!!???
I already have HTC_Driver_4.1.0.001 installed on my windows7 & works good with other previous ROMs.
I've checked ADB via usb on developer setting. How can I find or have a driver for "ADB connection" Windows couldn't find it automatically.
Thanks
kam5iz said:
I'm new to CyanogenMod & It needs new driver for ADB connection!!???
I already have HTC_Driver_4.1.0.001 installed on my windows7 & works good with other previous ROMs.
I've checked ADB via usb on developer setting. How can I find or have a driver for "ADB connection" Windows couldn't find it automatically.
Thanks
Click to expand...
Click to collapse
For me. Go into Device Manager and find the unconfigured device and manually assign the driver to it.
EDIT: Which you may need to get the android sdk and download the usb driver and manually assign it with those.
I have not managed to connect to my Redmi Note 4 (Android 6.0 MRA58K, MIUI Global 8.1 | Stable) via adb from my Windows 7 computer.
With my old SGN4 this was never a problem but I am a noob on the RN4.
I have Android Studio (with adb) installed, then
I connect my mobile via USB cable
I select on the mobile "Use USB for: Transfer files (MTP)", USB debugging is enabled and I can see the phone in the Windows explorer
then I open a command prompt and run adb but "nothing happens":
c:\Progs\Android\sdk\platform-tools>
c:\Progs\Android\sdk\platform-tools>adb.exe logcat
- waiting for device -
^C
c:\Progs\Android\sdk\platform-tools>adb devices
List of devices attached
c:\Progs\Android\sdk\platform-tools>
What am I missing???
Check drivers on control panel, it is correct?
dromaczek said:
Check drivers on control panel, it is correct?
Click to expand...
Click to collapse
Not sure I can post an image: i.imgur.com/UFAi5ez.png
In the Windows Device Manager there are two interesting entries:
Other devices
--- MTP [has an exclamation mark]
Portable devices
-- Redmi Note 4 [looks fine]
Is the "Transfer files (MTP) mode correct"?
Does the phone need to be rooted?
Gollob said:
Not sure I can post an image: i.imgur.com/UFAi5ez.png
In the Windows Device Manager there are two interesting entries:
Other devices
--- MTP [has an exclamation mark]
Portable devices
-- Redmi Note 4 [looks fine]
Is the "Transfer files (MTP) mode correct"?
Does the phone need to be rooted?
Click to expand...
Click to collapse
You have wrong adb driver (choose manually other from control panel)
dromaczek said:
You have wrong adb driver (choose manually other from control panel)
Click to expand...
Click to collapse
The driver was indeed the issue, thanks for that.
This is what I did:
[1] xiaomifirmware.com/downloads/download-xiaomi-redmi-note-4-drivers-utilites
[2] Download: latest_usb_driver_windows.zip
[3] also downloaded ADB Installer v1.4.3: adb-setup-1.4.3.zip from the same page (not sure if this was necessary)
[4] Control Panel, Device Manager: installed the driver (Android ADB Interface)
Now I have this Android ADB Interface under the heading SAMSUNG Android Phone, not sure if this is a problem
at some point later on as it is obviously a Xiaomi Android Phone that I have. [see: i.imgur.com/yvIyIjt.png]
When running adb devices I got the device ID and unauthorized at first and after approving USB access on the
handset it showed the device ID and authorized and I can issue commands like abd logcat.
Gollob said:
The driver was indeed the issue, thanks for that.
This is what I did:
[1] xiaomifirmware.com/downloads/download-xiaomi-redmi-note-4-drivers-utilites
[2] Download: latest_usb_driver_windows.zip
[3] also downloaded ADB Installer v1.4.3: adb-setup-1.4.3.zip from the same page (not sure if this was necessary)
[4] Control Panel, Device Manager: installed the driver (Android ADB Interface)
Now I have this Android ADB Interface under the heading SAMSUNG Android Phone, not sure if this is a problem
at some point later on as it is obviously a Xiaomi Android Phone that I have. [see: i.imgur.com/yvIyIjt.png]
When running adb devices I got the device ID and unauthorized at first and after approving USB access on the
handset it showed the device ID and authorized and I can issue commands like abd logcat.
Click to expand...
Click to collapse
You must authorized access and check all ADB options on xiaomi rom to use for example adb density command etc (and log on mi acount)
[Solved] Xiaomi Redmi Note 4 : Connection with ADB
Hi,
As we all know Xiaomi works on its own MIUI, So when you want to connect to adb that is developer mode you need to connect as MIDI,
Enable MIDI
Step 1: Goto settings > Additional Settings > Developer options
Step 2:In developer option, Enable developer options,
Step 3: In same menu go down in side Networking and from the SELECT USB CONFIGURATION, select MIDI
Now check adb devices on your command prompt you can see your Xiaomi is connected.
Happy Coding
Does your phone show up on the terminal with adb devices command when in recovery? Can be stock recovery too.
Also, in fastboot, use fastboot commands
i.e. fastboot devices instead of adb devices
One more thing, go to device manager and manually install a legacy driver and browse to adb and choose Android Bootloader Interface (ABI) look into it, it's possible.
That should do it. Tell me if it helps.
Sorry I don't know how to quote stuff and format commands.
dromaczek said:
Check drivers on control panel, it is correct?
Click to expand...
Click to collapse
hello brother, I'm facing the same issue while unlocking the bootloader.
I think these is prob with the drivers.. pps help me out
Hi! I have a new Xiaomi Redmi 4X and want to use it for app development with Android studio. I enabled the developer options, usb debugging, installing apps over usb and usb debugging (security settings) on the phone. When I connect the device to Windows 7, I see a device called "ADB Interface" in the device manager which is missing a driver. The hardware id of this device is "USB\VID_2717&PID_FF48&REV_0318&MI_01".
I already tried the following things:
The Minimal ADB and Fastboot package from XDA developers (https://forum.xda-developers.com/showthread.php?t=2317790 --> https://www.androidfilehost.com/?fid=745425885120698566)
Xiaomi Mi Flash Tool (http://en.miui.com/thread-345974-1-1.html --> http://api.bbs.miui.com/url/MiFlash)
The Google USB driver that can be downloaded in the Android SDK manager
ADB Driver Lite and Platform-tools (adb/fastboot) for Redmi 4X (https://xiaomifirmware.com/downl ... ols-redmi-4x-prime/ --> https://xiaomifirmware.com/download/3718/)
Xiaomi Redmi 4X driver For Normal Connecting (https://gsmusbdriver.com/xiaomi-redmi-4x --> http://gsmusbdriver.com/driver/8597/)
None of these worked. The Xiaomi Mi Flash Tool only contained unsigned drivers which I could not install. For the rest of these packages, Windows could not find any matching drivers in them. I then selected several drivers from these packages manually and installed them despite Windows warning me that this might not work. The drivers did install, but then Android studio would complain with the message: "Installation failed with message Failed to establish session."
Where do I find a working driver for the "ADB Interface" of the Redmi 4X?
Any help appreciated!
Thanks!
Ok, I was able to solve this myself. The error in Android Studio when trying to install apks on the Redmi 4X was not caused by the ADB Interface driver, but by "wrong" settings on the Redmi 4X. I followed the directions in this thread to solve this:
en.miui.com/thread-410773-1-1.html (1st answer, by hackhert)
I'll quote the answer here:
Go to Settings -> Permissions -> Install via USB: Uncheck your App if it's listed.
Go to Settings -> Additional Settings -> Privacy: Check the Unknown Sources option.
Go to Settings -> Additional Settings -> Developer options: Check the Install via USB option.
Go to Settings -> Additional Settings -> Developer options:Enable view attribute inspection
Finally Go to Settings -> Additional Settings -> Developer options:Turn off MIUI optimization.
And then restart your device and whoooaaaa it will work i guaranteee..
NOTE - Signin in to MI account is required to enable Install via USB option.
Click to expand...
Click to collapse
The ADB driver I used is the one that can be downloaded in the Android SDK manager:
SDK Manager -> SDK Tools -> Install "Google USB Driver"
Go to Windows Device Manager, find "ADB Interface" -> update driver -> select manually -> select from list -> all devices -> select folder "C:\Users\Username\AppData\Local\Android\sdk\extras\google\usb_driver" -> select "Android ADB Interface"
Windows will warn you that this driver might not work, install it anyway
Device manager will show "Android ADB Interface" in the category "SAMSUNG Android Phone"
Thank you, this solution works perfectly for me too. Find this two days after looking around and tried thousands things.
Hahaha.... !
By doing this step :-Go to Windows Device Manager, find "ADB Interface" -> update driver -> select manually -> select from list -> all devices -> select folder "C:\Users\Username\AppData\Local\Android\sdk\extra s\google\usb_driver" -> select "Android ADB Interface"
It gives message "windows was unable to install your ADB interface" while I am giving right path.
Simple way for installing adb drivers for redmi note 4 and others
1) Download & install MiFlash Tool to your pc
2) Connect your phone to pc , automatic driver install will start , wait till it fails. (Skip driver searching on microsoft database wich is "Windows Update")
3) Open Device Manager and find there "Other devices" >> "ADB Interface" , double-click on that and hit "Update Driver"
in the window just apeared.
4) Hit "Browse my computer for driver software"
5) Hit "Let me pick from a list of device of device drivers on my computer"
6) With "Show all devices" highlighted hit "Next"
7)Then hit "Have disk" button
8) "Browse" to "C:\XiaoMi\XiaoMiFlash\Source\ThirdParty\Google\Driver" and "Open" there "android_winusb.inf" and hit "OK" and press "Next" with "Android ADB Interface" highlighted.
9) It will prompt you that windows cannot verify driver sources, just hit "Yes"
10)hit "Install that driver anyway"
Thats all , for most users of windows 7 this should work. Some of you may face some troubles on 64-bit Windows versions because of unsigned drivers. Google how to solve this on your OS. Guide was created on 64-bit Windows 7 Professional it may differ a bit for other windows users but you got the point where to find the original driver.
Driver ids used in guide:
USB\VID_2717&PID_FF48&REV_0318&MI_01
USB\VID_2717&PID_FF48&MI_01
P.S. Also mi flash tool has adb and fastboot executables in "C:\XiaoMi\XiaoMiFlash\Source\ThirdParty\Google\Android"
i hope you will find this useful. Cheers !
I already tried the following things:
The Minimal ADB and Fastboot package from XDA developers (https://forum.xda-developers.com/sho....php?t=2317790 --> https://www.androidfilehost.com/?fid=745425885120698566)
Xiaomi Mi Flash Tool (http://en.miui.com/thread-345974-1-1.html --> http://api.bbs.miui.com/url/MiFlash)
The Google USB driver that can be downloaded in the Android SDK manager
ADB Driver Lite and Platform-tools (adb/fastboot) for Redmi 4X (https://xiaomifirmware.com/downl ... ols-redmi-4x-prime/ --> https://xiaomifirmware.com/download/3718/)
Click to expand...
Click to collapse
I tried all of that too and the ONLY drivers that work is the one that comes on the MiFlash unlock tool.
Open Device Manager. Go "Other devices" >> "ADB Interface" , double-click on that and hit "Update Driver" and manually go to the MiFlash tool folder. There's one inside that name Driver
Voila
Now you phone will be listed when you type "adb devices" on a cmd windows
So i've been wiping my phone and erased my OS so it doesn't boot up properly and i'm stuck at the logo.
I've been trying around with different drivers yet Windows doesn't let me access my phone via pc
i can enter the twrp menu. I have been searching for a few hours but havent found anything that made it work again.
What can i do/use to make my pc recognize my phone and install a new os? :/
Search Google for your 'device name' and 'unbrick'
Do you have USB with OTG? Might help
Sent from my MI 6 using Tapatalk
Thanks for the advice, i tried said way before using FlashOne but had trouble installing the correct drivers
It seems to be working for now, at least its currently flashing
Heyyo, sometimes windows forgets how to set up the driver. I have no idea if it's something to do with TWRP, device tree or kernel but yeah it's an odd one... My guess is it might be kernel as it doesn't include the USB OTG fix for the Le Max 2 that a recent LOS 14.1 LeEco MSM8996 kernel update brought which is what TWRP uses for device and kernel.
Hopefully on the next TWRP version it will include it.
Device Manager > select unknown device driver > update driver > let me choose > (Standard MTP Device) > USB MTP Device > apply and so fourth
Otherwise? You can use this command with adb to get the files onto your device
adb push NameOfFile.zip /sdcard
That will put the files onto the sdcard folder of your phone as it is only the MTP driver that Windows sometimes fails to set up where as the ADB driver for Android is universal.