• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!

[FIX] Windows 8.1 Fastboot/Flashmode/ADB for Sony and Samsung devices

Search This thread

janek2012

Member
Jul 21, 2012
9
87
As you all may now, Microsoft pushed the new driver stack in Windows 8.1 so ALL (not only USB 3.0) devices must provide a BOS descriptor. Sony ADB and Fastboot doesn't, so Windows fails to enumerate the device which is reported in Device Manager as error code 43.
This also may help if you have a USB drive or mouse and it stopped working after you upgraded from Windows 8 to Windows 8.1.

Microsoft said that the fix will come in February but for people who don't want to wait I prepaired a dirty solution:
Microsoft published the update.

proof - see attachment.

THE PROBLEM IS NOW FIXED BY THIS UPDATE: http://support.microsoft.com/kb/2917929 - USE IT INSTEAD OF MY FIX!

Here is my old (dirty) solution:
HTML:
#include <std_disclaimer.h>
/*
 * Your warranty is now void.
 *
 * I am not responsible for bricked devices, dead SD cards,
 * thermonuclear war, or you getting fired because the alarm app failed. Please
 * do some research if you have any concerns about features included in this ROM
 * before flashing it! YOU are choosing to make these modifications, and if
 * you point the finger at me for messing up your device, I will laugh at you.
 */

I repeat this is a REALLY DIRTY solution that may harm your system, personal data, hardware and/or cat.
Here are the steps:
0. Have a Linux or Windows LiveCD just in case something goes wrong
1. Download and extract files from attachment
2. Navigate to the folder corresponding to your system version (x86 = 32-bit, x64 = 64 bit)
3. Right-click franken-usb.bat and click "Run as Administrator"
5. Wait for it to finish and reboot the system. If everything went fine, you will boot your system successfully
6. Install ADB/Fastboot drivers just like on Windows 8
7. Connect your phone in Fastboot mode to your USB 2.0 port and check if it works
8. Enjoy and wait for official fix

How does it work:
It's not any kind of magic - it just replaces Windows 8.1's usbhub.sys and usbport.sys with Windows 8's ones.
Old files don't check for BOS descriptor so Fastboot can work.

Script updated - it should now actually copy the files but please double check if files were copied to C:\Windows\system32\Drivers!


Hope it helps you!

Regards!
 

Attachments

  • proof.png
    proof.png
    64.4 KB · Views: 44,792
  • USB.zip
    687 KB · Views: 97,369
Last edited:

sandeep101

Senior Member
Jun 19, 2010
147
21
!! success !!

thank u bro , working great on win 8.1 pro 64 bit , fastbooted sony xperia LWW and flashed kernel like before ! :laugh:
just need to copy files manually though but that was so easy .:victory:
 

hhamzah49

Senior Member
Mar 3, 2013
245
31
Den Haag
Looks like it works reading those comments! Gonna try it tomorrow!

Sent from my LT30p using xda app-developers app

EDIT:

doesnt work for me! It now doesnt show the driver blabla it shows s1 fastboot. And the phone doesnt stay in fastboot

EDIT 2:
nevermind fixed it with installing drivers via flashtool.

Thankyou my hero!
 
Last edited:
  • Like
Reactions: cmureza

Steph310

Senior Member
Jul 3, 2012
1,519
1,434
Cahors
I only needed to replace manually files, but yes! Now it works perfectly on Win8.1 x64 on USB2.0 computer!
My problem finally solved, thanks to you janek2012! :good:
 
Last edited:

rwells

Senior Member
May 18, 2013
51
6
Honolulu
Finally Success!!

You are on the top of my "Good Guys" list!! After manually copying the two files, fastboot is now working on my Win 8.1 x64 USB 2 computer. Nothing else worked. I tried editing the registry, updated USB drivers, replaced with universal drivers, intel drivers and nothing worked except your solution.

Many thanks.
 

psyke83

Inactive Recognized Developer
Mar 29, 2011
1,267
3,959
janek2012,

Many thanks for this workaround - it saved me having to wait for Microsoft's fix to perform the update to Windows 8.1. I would recommend that you update your archive with a more reliable "restore" script, or at least update your initial post with the information. Rather than moving the .bak files back into place, it makes much better sense to utilise Windows Resource Protection/sfc. These two commands will repair the two files:

Code:
sfc /scanfile=%systemroot%\system32\Drivers\usbhub.sys
sfc /scanfile=%systemroot%\system32\Drivers\usbport.sys

If the integrity violations are not repaired correctly, future hotfixes/updates from Microsoft that contain updated USB drivers (including the specific fix for this issue) may fail to install.
 

brightblue

Member
Jan 31, 2014
5
1
Thanks SO MUCH for this!!!!
I had tried everything and only your solution works!!!


Did not work for me, now left with no functional usb ports. How do I restore the .bak files?
Just navigate to \windows\system32\drivers, and move the current usbhub.sys and usbport.sys (should be v6.2.9200.16384)
and then rename
usbhub.sys.bak to usbhub.sys and
usbport.sys.bak to usbport.sys
(should be v6.3.9600.16384)

Then reboot.
 
Last edited:
  • Like
Reactions: n70shan

MatteFugger

Member
Feb 6, 2011
14
1
Cork
Worked without any problems (had to manually coppy the files to the system32\driver folder )
sorry, but can't hit the Thanks-Button more than one time :)

Using HDH with HBoot: 0.85.0024
Win8.1 (Install from scratch - no update installation) 64Bit
intel 4th Gen

ADB was working with no problem from very begining but the Fastboot I got just working after this nice and easy tutorial/fix

Thanks a tonne
 

Top Liked Posts

  • There are no posts matching your filters.
  • 80
    As you all may now, Microsoft pushed the new driver stack in Windows 8.1 so ALL (not only USB 3.0) devices must provide a BOS descriptor. Sony ADB and Fastboot doesn't, so Windows fails to enumerate the device which is reported in Device Manager as error code 43.
    This also may help if you have a USB drive or mouse and it stopped working after you upgraded from Windows 8 to Windows 8.1.

    Microsoft said that the fix will come in February but for people who don't want to wait I prepaired a dirty solution:
    Microsoft published the update.

    proof - see attachment.

    THE PROBLEM IS NOW FIXED BY THIS UPDATE: http://support.microsoft.com/kb/2917929 - USE IT INSTEAD OF MY FIX!

    Here is my old (dirty) solution:
    HTML:
    #include <std_disclaimer.h>
    /*
     * Your warranty is now void.
     *
     * I am not responsible for bricked devices, dead SD cards,
     * thermonuclear war, or you getting fired because the alarm app failed. Please
     * do some research if you have any concerns about features included in this ROM
     * before flashing it! YOU are choosing to make these modifications, and if
     * you point the finger at me for messing up your device, I will laugh at you.
     */

    I repeat this is a REALLY DIRTY solution that may harm your system, personal data, hardware and/or cat.
    Here are the steps:
    0. Have a Linux or Windows LiveCD just in case something goes wrong
    1. Download and extract files from attachment
    2. Navigate to the folder corresponding to your system version (x86 = 32-bit, x64 = 64 bit)
    3. Right-click franken-usb.bat and click "Run as Administrator"
    5. Wait for it to finish and reboot the system. If everything went fine, you will boot your system successfully
    6. Install ADB/Fastboot drivers just like on Windows 8
    7. Connect your phone in Fastboot mode to your USB 2.0 port and check if it works
    8. Enjoy and wait for official fix

    How does it work:
    It's not any kind of magic - it just replaces Windows 8.1's usbhub.sys and usbport.sys with Windows 8's ones.
    Old files don't check for BOS descriptor so Fastboot can work.

    Script updated - it should now actually copy the files but please double check if files were copied to C:\Windows\system32\Drivers!


    Hope it helps you!

    Regards!
    5
    Windows 8.1 "A request for the USB BOS descriptor failed" - SOLVED !

    OMFG ! I managed to solve this using a NEW METHOD !!! :D:D
    :good: NO DRIVER ALTERATION REQUIRE !
    :good: NO NEED to download MS bull**** non-working installer fix whatsoever !
    :good: ONLY administrative privileges are required as it involves EASY registry editing.
    To apply the workaround for a specific device, add a REG_DWORD value named SkipBOSDescriptorQuery that has a value of 1 to the following registry subkey:

    HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\usbflags\vvvvpppprrrr

    (where vvvv is the device's Vendor ID, pppp is the device's Product ID, and rrrr is the device's Revision number. You can get the VID/PID/REV numbers from the device manager's details tab. This number is encoded in the HardwareIDs of the device)
    1. Click Start, click Run, type regedit in the Open box, and then click OK .
    2. Locate and then click the following subkey in the registry:
      HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\UsbFlags
    3. On the Edit menu, point to New, and then click Key.
    4. Type the name of the new key in the following form: vvvvpppprrrr
      where
      vvvv is a 4-digit hexadecimal number that identifies the vendor (idDevice from the USB Deviceescriptor),
      pppp is a 4-digit hexadecimal number that identifies the product (idVendor from the USB Device Descriptor)
      rrrr is a 4-digit binary-coded decimal number that contains the revision number of the device (bcdDevice from the USB Device Descriptor).
    5. On the Edit menu, point to New, and then click DWORD (32-bit) Value. ( Do that inside that "vvvvpppprrrr" folder !)
    6. Type SkipBOSDescriptorQuery for the name of the DWORD Value, and then press ENTER.
    7. Right-click SkipBOSDescriptorQuery, and then click Modify.
    8. In the Value data box, type 1 , and then click OK.
    9. Exit Registry Editor. Then, Unplug and re-plug the device for the workaround to take effect.
    SOURCE HERE

    In my case, I had already that "VVVVPPPPRRRR" folder so I jumped to step #5.

    I attach an image from my own computer - so it will be easy to understand what is the "VVVVPPPPRRRR" using window's Device Manager.
    attachment.php
    4
    @janek2012

    Please update your OP to let people know that the hotfix only applies to Sony Xperia devices. You should link to Microsoft's USB Core Blog - Microsoft engineers have asked users to submit USB traces in order for specific devices that are affected by this bug to receive an official fix in future. This is really inconvenient, but people need to know. It's here: http://blogs.msdn.com/b/usbcoreblog...8-0-but-fail-on-windows-8-1-with-code-43.aspx

    You are my hero
    i love you dude :D
    even microsoft fix didn't work
    but your dirty fix did work :p
    using motorola fire xt311
    thanks :p

    Same deal - submit your trace to Microsoft (with the original 8.1 USB drivers) if you ever want to see this fixed in future.
    3
    Today my Win 8.1 64bit install updates from microsoft, and fastboot/flashmod work without this fix
    2
    windows 10

    I installed win10 yesterday and facing this problem.