[GUIDE][XP] Working Fastboot Drivers for Windows 8.1 x64 - Sony Xperia P, U, Sola, Go
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.
Related
[Q] Archos 80 G9 and Usb Driver problem
Goodmornig everyone..! I just bought an Archos 80 G9 Turbo 16GB and I cannot connect it with my computer that runs Windows 7 64bit When I plug it, it is detected as an Unknown Device (error code 43) and nothing is mounted.. (but tablet is in "slow charge") In an old Win XP computer is working good, this made me think it's not completely tablet's fault.. here what I've tried, deeply searching on internet: -Downloaded ADB android Drivers (in Archos site, on internet, various sources), forced installation of them, problem come out: Drivers are not for a 64 bit Os -Uninstalled Kies, LG Pc suite and rebooted after every change..nothing changed -Unactivate and reactivate after reboot Windows Media Player 12..no change -Changed Usb Mode in tablet from MTP to PTP.. nothing changed -Installed a lot of USB apps in Google Play and tried changing values..no change -Upgraded tablet from GingerBread to ICS, deeply wiped and restored several times, and in every configuration, I allways had same results.. -Changed USB cable, several of them tested..and guess?? Nothing..eheh -Tried shouting at it, tried kissing and asking for his forgiveness..but nothing I'm stuck on Stock! i cannot upgrade it with XDA custom, I can only connect to pc via FTP server....! Any Clues?!?! Thank You to all!
1. To root and to enable SDE menu you need only adb driver 2. You can transfer archos.ext4.update files using FTP from pc to tablet 3. Recovery for flashing firmware update or custom kernel creates ramdisk which is seen as standard usb storage device- "just works"
You need to give full access (Everybody) to the folder where Android SDK is installed in Program Files (x86) and through Android SDK Manager select the second item "Android SDK Platfrom-tools for download. This worked for me on Windows 7 Ultimate.
Ooops overread something... forget it!!! Have you checked for the correct MTP driver package... Regards, scholbert
gen_scheisskopf said: 1. To root and to enable SDE menu you need only adb driver 2. You can transfer archos.ext4.update files using FTP from pc to tablet 3. Recovery for flashing firmware update or custom kernel creates ramdisk which is seen as standard usb storage device- "just works" Click to expand... Click to collapse Only is an huge word, I have tried several dof them, and no one is working, no one is accepted by windows (it tells me they are not designed for the device or they are not for an x64 OS) Strange thing, it accepted me usb drivers for Samsung Mobile, it installed them.. but not ADB from android... obviously, Samsung ones where not working with it.. xcen3x said: You need to give full access (Everybody) to the folder where Android SDK is installed in Program Files (x86) and through Android SDK Manager select the second item "Android SDK Platfrom-tools for download. This worked for me on Windows 7 Ultimate. Click to expand... Click to collapse Installed drivers and quite everything with Android SDK, but nothing changed, even forcing these drivers... tried with access tweek, but.. nothing.. scholbert said: Ooops overread something... forget it!!! Have you checked for the correct MTP driver package... Regards, scholbert Click to expand... Click to collapse Dowloaded and istalled a few from windows... the problem is, if it would be an MTP problem, I should not have it in PTP mode... I suppose... EDIT: tried disabling Integrity Checks for non signed drivers with these string in cmd: bcdedit.exe -set loadoptions DDISABLE_INTEGRITY_CHECKS bcdedit.exe -set TESTSIGNING ON nothing changed
indyjones83 said: Only is an huge word, I have tried several dof them, and no one is working, no one is accepted by windows (it tells me they are not designed for the device or they are not for an x64 OS) Strange thing, it accepted me usb drivers for Samsung Mobile, it installed them.. but not ADB from android... obviously, Samsung ones where not working with it.. Installed drivers and quite everything with Android SDK, but nothing changed, even forcing these drivers... tried with access tweek, but.. nothing.. Click to expand... Click to collapse For Gen9 you need Archos modified driver
gen_scheisskopf said: For Gen9 you need Archos modified driver Click to expand... Click to collapse These are the first one I tried.. From their site.. Not working.. Thankyou! I wrote them in Contact and support in that site, copying and pasting the same I wrote here, they answered me, two days later.. Excited in what solution they could give me,from the heights of their knowledge, I suddenly opened and the answers was: Please write the email in English. Are they kidding me? This makes me suppose they have not even tried in reading it.. Well.. 1000 thanks for you and you support..! Sent from my Optimus 2X using XDA
Second reply from Archos, this time they read it, but only first few lines.. their reply is: "We invite you to connect the device to a 32 bits system and then to check if the Archos is seen by the pc." Already done, and it's working with that (WIN XP) Did you try to install manually the MTP driver from the device manager of the PC ? YES. any new clue from here? Thankyou!
Try this Sent from my ARCHOS 80G9 using XDA
1 thing, when you are plugging into your PC, are you plugging it into the main hub (rear of PC), or a front port? I had a devil of a job getting mine to recognise the driver, in the it turned out it really needs to be plugged into the rear port, it may have been a conflict on my PC, but worth a shot.
pittnuma said: 1 thing, when you are plugging into your PC, are you plugging it into the main hub (rear of PC), or a front port? I had a devil of a job getting mine to recognise the driver, in the it turned out it really needs to be plugged into the rear port, it may have been a conflict on my PC, but worth a shot. Click to expand... Click to collapse Yes, tried to connect it in every usb my laptop has, even tried in disconnecting every usb device and turned off the pc. After that I took off battery for a few minutes and started again.. no change... ERROR 43...! In the old win xp pc I use front usb I installed 10 years ago, and works..! ADB USB drivers from archos site are not recognized, it's not possible to manually select them.. I was able to select an old symbian driver I have in an old backup directory, but not that one... any clue?
indyjones83 said: Yes, tried to connect it in every usb my laptop has, even tried in disconnecting every usb device and turned off the pc. After that I took off battery for a few minutes and started again.. no change... ERROR 43...! In the old win xp pc I use front usb I installed 10 years ago, and works..! ADB USB drivers from archos site are not recognized, it's not possible to manually select them.. I was able to select an old symbian driver I have in an old backup directory, but not that one... any clue? Click to expand... Click to collapse Did you try the link in my previous post? I'm running win7 64 bit and it worked for me! Maybe just try adding the file in your USERPROFILE directory first! Sent from my HTC Sensation using XDA
bobjbain said: Did you try the link in my previous post? I'm running win7 64 bit and it worked for me! Maybe just try adding the file in your USERPROFILE directory first! Sent from my HTC Sensation using XDA Click to expand... Click to collapse Yes, that one and a modified one.. the problem is, it remains as an "Unknown Device" (error 43). I tried now to move that driver you suggested me in USERPROFILE (c:\USERS\"myname" and c:\USERS\"myname"\.android) is this you mean? and same error: can't find in directory any compatible driver for the device. make sure it's done for a x64 system... It seams to me device is not recognized at all.. not PTP or MTP or USB DEBUG.... but it works with win xp...! I tried again..! Another doubt I have is: when I plug it to the wall charger I found on the box, it goes on "Slow Charge".. is it normal? why not fast charge or Normal? may be an hint?
indyjones83 said: Yes, that one and a modified one.. the problem is, it remains as an "Unknown Device" (error 43). I tried now to move that driver you suggested me in USERPROFILE (c:\USERS\"myname" and c:\USERS\"myname"\.android) is this you mean? and same error: can't find in directory any compatible driver for the device. make sure it's done for a x64 system... It seams to me device is not recognized at all.. not PTP or MTP or USB DEBUG.... but it works with win xp...! I tried again..! Another doubt I have is: when I plug it to the wall charger I found on the box, it goes on "Slow Charge".. is it normal? why not fast charge or Normal? may be an hint? Click to expand... Click to collapse OK try this :- Download the naked universal drivers attached to this post and unzip somwhere!! (got this from the Sensation forum, would say thanks but I can't remember who posted them). Attache your G9 then go into device manager. Now find your badly installed driver and uninstall it. Keep doing this until all drivers are uninstalled. Now unplug and reattach G9, let windows do it's thing. You will still have a excalamation next to "Android Drivers" at this point. Right click on the driver in device manager and "Update Driver Software", then click "Browse My Computer....", now click on "Let Me Pick from a list...", then click the "Have Disk" button. Browse to the folder where you extracted the Universal Naked Drivers and select the andorid_winxusb.inf file. If you get unsigned warnings click on the "trust me" or whatever it says. Driver should now be installed. The adb_usb.ini file is really for if you use adb, if you do it need to go in c:\users\you\.android directory (create the directory if it doesn't exist). You can test adb connectivity by using "adb devices" from the command line. Hope this helps
indyjones83 said: Another doubt I have is: when I plug it to the wall charger I found on the box, it goes on "Slow Charge".. is it normal? why not fast charge or Normal? may be an hint? Click to expand... Click to collapse I think this is probably because your USB cable only has 2 internal cables, not 4. IIRC, the outside 2 are USB and data chat and the inside 2 are for 5v power. If your G9 detects the cable doesn't have the two middle connections then it will do a slow charge regardless. Are you using the cable you got with the G9??
bobjbain said: I think this is probably because your USB cable only has 2 internal cables, not 4. IIRC, the outside 2 are USB and data chat and the inside 2 are for 5v power. If your G9 detects the cable doesn't have the two middle connections then it will do a slow charge regardless. Are you using the cable you got with the G9?? Click to expand... Click to collapse Yes, I'm using the cable i got with the g9.. I could have a dual cable (the one they give to you with an external hdd), but it's mini usb, not micro... bobjbain said: OK try this :- Download the naked universal drivers attached to this post and unzip somwhere!! (got this from the Sensation forum, would say thanks but I can't remember who posted them). Attache your G9 then go into device manager. Now find your badly installed driver and uninstall it. Keep doing this until all drivers are uninstalled. Click to expand... Click to collapse And this is the problem.. I don't have any driver to uninstall, as if my device is an "Unknown Device" no service, no adb no mpt recognized.. only an "unknown device".. even with new drivers, the only driver it lets me install are Samsung drivers.. but obiously doesn't work! I now tried in installing it as this samsung, just to have something to uninstall... bobjbain said: Now unplug and reattach G9, let windows do it's thing. You will still have a excalamation next to "Android Drivers" at this point. Right click on the driver in device manager and "Update Driver Software", then click "Browse My Computer....", now click on "Let Me Pick from a list...", then click the "Have Disk" button. Browse to the folder where you extracted the Universal Naked Drivers and select the andorid_winxusb.inf file. If you get unsigned warnings click on the "trust me" or whatever it says. Driver should now be installed. The adb_usb.ini file is really for if you use adb, if you do it need to go in c:\users\you\.android directory (create the directory if it doesn't exist). You can test adb connectivity by using "adb devices" from the command line. Hope this helps Click to expand... Click to collapse You are really amazing, archos is not caring at all.. Before I tried your firs suggestion in USERDEVICE and for a minute it found my device as Error 10 and not Error 43 (unknown device)... and that's the only moment my pc saw the tablet... Thankyou!!
indyjones83 said: Yes, tried to connect it in every usb my laptop has, even tried in disconnecting every usb device and turned off the pc. After that I took off battery for a few minutes and started again.. no change... ERROR 43...! In the old win xp pc I use front usb I installed 10 years ago, and works..! ADB USB drivers from archos site are not recognized, it's not possible to manually select them.. I was able to select an old symbian driver I have in an old backup directory, but not that one... any clue? Click to expand... Click to collapse I too have run across this problem--AFTER woprking for 6 months with it under ADB just fine. Not just my work computer, home devices as well. Did you ever get this fixed?
One way to get Windows 7 to detect your Fascinate after flashing a new ROM like AOKP
Ok hopefully this helps someone. After flashing the amazing AOKP ROM (literally best ROM I've ever flashed...Holy stable batman) I noticed that on Win7 x86 or x64 that USB file transfer to/from SD card worked fine...as did Odin but Windows could not find a driver for my phone anymore. This creeped me out because this meant adb would not be able to connect. Running the adb devices command would not show anything. I tried 3 different Win 7 machines and a WinXP machine all of them used to work but now they didn't I read the FAQ, I goggle searched xda and droid forums and tried everything, cables, switching USB ports, phone settings, dev settings, new usb drivers but, I could no longer get adb to connect. So I started looking closely at the Samsung USB drivers I have on my machines which worked fine on stock ROMs, and a few other custom ROMs (not blaming AOKP no disrespect) and I found that the hardware id for my device changed and the device string wasn't referenced in any of the USB drivers files. So I forced the correct driver to install and it worked! So if that is all you need to know cool, if you some of you need the steps here they are: I'm assuming you already have Samsung USB drivers and adb from the SDK installed (if not there's tons of info on this site to get both) I'm also assuming you installed the USB drivers so they are in the default location, if you extracted a zip file or something you will need the path to the USB drivers Last assumption... I tried 3 different versions of Samsung USB drivers and for each one the ssadadb2.inf that has the ADB driver was in the USB Drivers\16_Shrewsbury folder...If you don't find it there do a search in the USB Drivers folder and reference that location for step 13 Click Start button, then right-click Computer, then click Manage Click Device Manager Expand Other devices, you should see SCH-I500 with the yellow exclaimation point Right-click it then click Update Driver Software Click Browse my computer for driver software Click Let me pick from a list of drivers Scroll up, highlight Show All Devices, click Next Click Have Disk Click Browse Browse to C:\Program Files\SAMSUNG\USB Drivers\16_Shrewsbury Double-click ssadadb2.inf, click Open, Click OK Highlight SAMSUNG Android Composite ADB Interface, click Next You will get an "Update Driver Warning" saying cannot verify compatibility with your hardware, click Yes You should see Windows has successfully updated your driver software, click Close Back in device manager under ADB Interface you should see the driver name you just added....the entry under Other devices should be gone Connect your data USB cable (not a charging only cable...if you can't tell the difference just be sure you used this cable for data before) Open a cmd prompt (start>run>cmd enter if you didn't know) browse to where you installed adb and type "adb devices" You should see your device and a serial number again....back in business Like I said no disrespect to AOKP I rock my B31 (soon to be 32) Pink Unicorn proudly This hopefully applies to anyone who had a hardware id change from any ROM.
Successfully install ADB drivers
I did some research on xda to find working solution, and finally use this method below. 1. enable USB debugging. 2. plug in your Tablet. 3. let windows install "null" driver. 4. go to Control Panel -> driver Manager. 5. find SGPT12 -> right click -> update driver. 6. browse my computer for driver software -> let me pick... 7. choose Google, Inc and "Android sooner Single ABD Interface" -> install it anyway. 8. done.
mingkee said: I did some research on xda to find working solution, and finally use this method below. 1. enable USB debugging. 2. plug in your Tablet. 3. let windows install "null" driver. 4. go to Control Panel -> driver Manager. 5. find SGPT12 -> right click -> update driver. 6. browse my computer for driver software -> let me pick... 7. choose Google, Inc and "Android sooner Single ABD Interface" -> install it anyway. 8. done. Click to expand... Click to collapse rooted or not?
Windows XP? Vista? 7? 8?
jiggykilla said: rooted or not? Click to expand... Click to collapse Since it is installed on PC (Win 7), rooted or not does not matter, but you must have Android ADB installed on your PC. BTW, I don't realize there's no Q&A section.
[ADB/FB/APX Driver] Universal Naked Driver 0.72 (We dont need no stinking HTC Sync)
Universal Naked Driver 0.72 ** HTC One Added (HTC phones are pretty much future proof with my driver) ** Google Nexus 4 Added ** Google Nexus 10 Added ** Google Nexus Q Added ** Google Nexus S Added 32 & 64 Bit Windows 8 / 7 / Vista / XP - Attached to this post! MD5: 30D25BC073F010CA01178CD6E2C5E4FA I am happy to release my Universal Naked Driver. This is to allow ADB, Fastboot & APX interfaces to work without installing any package much less multiples packages for users with multiple devices. Yes you can just install them and uninstall right away but why bother? I was annoyed that I couldnt use my Transformer Prime and Galaxy Nexus without having versions and packages trip over each other. My previous post for the Sensation & Galaxy Nexus was helpful so I thought I would bring to XDA the newest Android driver available from source (which they call 4.0) and make it start talking. Warning: Uninstall any previous driver package's you may have installed and also manually remove drivers by attaching your phone and going to Windows device manager and right click the entry for your phone and select "Uninstall" on the next prompt make sure to select "Delete the driver software for this device" then hit OK and reboot before installing these drivers Code: Google Nexus Devices ADB & Fastboot Samsung Devices ADB & Fastboot Asus Devices ADB, Fastboot & APX HTC Devices ADB & Fastboot Code: [B]Windows 8 Instructions[/B] How to Disable Driver Signature Enforcement in Windows 8: From the Metro Start Screen, open Settings (move your mouse to the bottom-right-corner of the screen and wait for the pop-out bar to appear, then click the Gear icon). Click ‘More PC Settings’. Click ‘General’. Scroll down, and click ‘Restart now’ under ‘Advanced startup’. Wait a bit. Click ‘Troubleshoot’. Click ‘Advanced Options’ Click ‘Windows Startup Settings’ Click Restart. Enjoy!
Just FYI, you don't need HTC Sync to get the drivers, you can download the drivers by themselves.
designgears said: Just FYI, you don't need HTC Sync to get the drivers, you can download the drivers by themselves. Click to expand... Click to collapse Ah they may have changed this but this will still work with all your devices and tablets.
Thanks for making this but after about 30 min of research you can learn how to modify the google ini file to work with ANY android ran device as long at it doesn't have a proprietary connection interface. Once you plug in the phone just go to device manager and properties. Find the hardware ID and Vendor ID and plug them into the generic google.ini setup and label it with your phone. Then you can just install google drivers to run your interface. I work with linux too and its even EASIER to create generic google drivers you just need vendor id and port.
I've installed this driver and I still have the MTP device problem. My phone connects as an android tablet and I can't mount my storage card. Pls help
Can't unlock bootloader in Pocophone F1
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: