yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] antawnm26:
Samsung site is down...Can someone point me in the right direction so I can Odin I535VRBMF1
[Verizon Samsung Galaxy S III] buhohitr:
EDIT:

Try this one http://www.androidfilehost.com/?fid=23134718111254196
[Verizon Samsung Galaxy S III] antawnm26:
thanks..will this update my bootloader/modem? I can flash this with twrp?
[Verizon Samsung Galaxy S III] buhohitr:
Deleted....sorry I was on another thread and thinking confused. If you want to flash back to stock factory file give me a second see if I can find the tar file for you.
[Verizon Samsung Galaxy S III] antawnm26:
yes thats what i am looking for the stock rom..but this link is way to small for that and also, I opened it up and it didnt have the tar file in there..Im assuming this link was like a firmware update instead...
[Verizon Samsung Galaxy S III] buhohitr:
OK, here is the full firmware, unzip then flash with ODIN. This included rom/bootloader/modem/kernel(everything). This will bring back to factory stock rom.

http://www.androidfilehost.com/?fid=23134718111254196
[Verizon Samsung Galaxy S III] antawnm26:
thanks.thats what i needed....is it recommended that you update the baseband with this?http://xdaforums.com/showthread.php?t=1788313&highlight=vrbmf1
[Verizon Samsung Galaxy S III] buhohitr:
If you already have strong signal and no issue with data drop, then you don't need to upgrade, otherwise yes you could upgrade and possible it may cure your poor signal...hopefully. In my case, this new radio did nothing to my phone signal.
[Click General] chongbos:
miss u all！！

miss Kalim!!

miss cn.froyo！！
[G2 Q&A, Help & Troubleshooting] ddarvish:
tried 3 or 4 different AOSP roms including vanir and cm and on all of them i can get the play store to work. some google services (gmail, google+) work while others dont (store, hangouts). what am i doing wrong. i have done full wipes between the different rom installs.. when i go back to stock LG rom with/ root the play store works fine
[G2 Q&A, Help & Troubleshooting] truckroot:
Sounds like a gapps issue. I use PA mini and have zero issues.

Sent from my Nexus 7
[G2 Q&A, Help & Troubleshooting] ddarvish:
some of these roms come with gapps included. and i tried 2 other gapps. anyhow i did find a solution. I went into settings and apps manager and i cleared data on all google play services, google play store, google framework, google account settings and low and behold it now work.. i must note that my LTE/ WIFI/cell reception still stay white and never turn blue (indicating connected to g-services) but at least they all work..
[Sprint HTC EVO 4G LTE] Link420able:
These 2 roms by team nocturnal (correct me if i'm wrong) are simply amazing. When our phone finally receives android 4.3 with possible sense 5.5, will these roms get updated to 4.3 as well? I will have this phone for over a year to come as I am just a poor teenager who stumbled upon rooting and the android developement world with an LG Optimus S, and upgraded to the Evo 4G LTE in may of 2013.

Will major developers like NIN and sinistertensei still be developing for our phone?

apologizes if this is a dumb question. Just never know when a developer will move on.
[Sprint HTC EVO 4G LTE] lreyes:
Well we all know amazing roms don't always come from xda. Why don't you ask them personal via Private message. We don't even have sense 5 from HTC and most people doubt we'll see it from them. (As a OTA)
[Sprint HTC EVO 4G LTE] Link420able:
HTC has broken their promise's before, but with the update planned to go into sprint testing in mid january, It's very likely we will see it.

You do make a good point however, I just typed this on the go earlier.
[Sprint HTC EVO 4G LTE] Moscow Desire:
Thread closure

As previously stated by another member, there's really no point in discussing matters like this, when the ROM's are not hosted on XDA.

It's better to post your questions on the Developers own websites. Just Google them. They're pretty easy to find.

So with that said, it's better off to close this thread.

Cheers

MD
[Android Q&A, Help & Troubleshooting] spaboleo:
No one? :confused::angel:
[Android General] janek2012:
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:

#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!
[Android General] wabicek:
So far it works (both adb and fastboot) on my computer. But it was necessary to copy these files manually.

Thank you! :good:
[Android General] sandeep101:
!! 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:
[Android General] heatledger:
thanks! working perfectly 8.1 64bit

you're my hero
[Android General] hhamzah49:
Looks like it works reading those comments! Gonna try it tomorrow!

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!
[Android General] Leon:
Works on me too! Thanks!
[Android General] MatteXperiaU:
awesome!! you are my hero!!!!:good:
[Android General] drmidoo:
works on windows 8.1 x64 usb 2.0

thanks :D great fix :D
[Android General] Steph310:
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:
[Android General] gonzal86:
Yea me too replaced manualy, but all works fine. At last phone connect in fastboot and flash :D

Dobra robota [MENTION=414431]janek[/MENTION] :D
[Android General] mido_fedo:
yes working good with replace manually files

thanks bro :)
[Android General] rwells:
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.
[Android General] psyke83:
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:

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.
[Android General] n.vk1305:
thnakyou so much man.....wasted my whole day for this,now i got fastboot usb.. :) :)
[Android General] Art2Fly:
Did not work for me, now left with no functional usb ports. How do I restore the .bak files?
[Android General] brightblue:
Thanks SO MUCH for this!!!!

I had tried everything and only your solution works!!!

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.
[Android General] MatteFugger:
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
[Android General] DeadMan2k:
Today my Win 8.1 64bit install updates from microsoft, and fastboot/flashmod work without this fix
[Android General] Abhinav Valecha:
just copy the two files in this zip and manually replace them with the one in system {to open drivers, just press windows+r and type drivers and press enter}

ALWAYS HAVE A BACKUP
[Android General] luxm4n:
Yes! :)

Just Install FlashTool Driver :D
[Android General] janek2012:
Yes, Microsoft finally published the hotfix for this issue.

Check http://support.microsoft.com/kb/2917929 .
[Android General] kirE_2o1o:
Was struggeling with fastboot now for around 2hours with my HTC One.

The microsoft fix alone didn't change my problem, but additionally replacing the USB 3.0 drivers from Microsoft with those from the manufacturer himself (in my case Renesas) did.
[Android General] janek2012:
Good to hear you got this working but keep in mind that using USB3.0 ports for such purposes is not recommended. You should use USB 2.0 for any flashing operations.
[Android General] Captain_Throwback:
Thanks for this. I already had the Microsoft update installed on my Computer, but fastboot still wasn't working. Your files fixed it. Thanks again!
[Android General] Mazzen.kh:
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
[Android General] psyke83:
[MENTION=4753858]janek2012[/MENTION]

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

Same deal - submit your trace to Microsoft (with the original 8.1 USB drivers) if you ever want to see this fixed in future.
[Android General] codingtent:
ADB working without modifications on windows 8.1 with ASUS device

It may interest you to know that ADB is working without any driver modifications on windows 8.1 with an ASUS device.

as at 18 march 2014.

i didnt have the device when i first upgraded to windows 8.1, so i dont know if this success is due to recent upgrades.

but its fine now.
[Android General] Ron173:
Mate awesome work!

Fixed my HTC issue after hours of muckin around with drivers n Microsoft this n that.

I did have to install manually too, but the 'dirty fix' (dunno whats dirty about it) certainly worked.

Would click thanks meter but for some reason they are not highlighted on this pc, I'm logged in obviously as posting, so dunno, maybe another win 8 bug!

cheers
[Android General] garzie2000:
You literally saved me from trashing my current Windows 8.1 set up
[Android General] jass619:
Thanks! Was waiting for a fix for a long time.... Now time to try kitkat on my arc s... (^_-)
[Android General] Kevincorella:
Thank you a lot, I almost got crazy and install win7 jaja
[Android General] Jammed_Death:
i downloaded the ms fix, tried to install it and system says it was installed but i have the same issue :/
[Android General] Captain_Throwback:
http://xdaforums.com/showthread.php?p=50525263
[Android General] DS-1:
I installed MS patch, but I can't fastboot/flashmode drivers.

So I used this script (I still had to manually move both .sys file) and after tried again to install drivers.

I always got this:
[Android General] Raddub:
Many thanks !!

well.. I had some issues at first (for example, my mouse & keyboard weren't recognised), but then I copied manually the files in your zip in system32/drivers folder.. and, finally my samsung i5500 was recognised in download mode!! :victory:

I searched for this problem for 2 months.. so, thank you a lot !! :good:
[Android General] XeNNz:
Thank you!!!!!!!! 999times. IT WORKED. But manually cuz with the script my keyboard and mouse was down xD.
[Android General] Roman91:
Thanks!!! This way all works well (but with manual procedure ..the script does not work)
[Android General] MrMariusz:
Thanks a million times, Janek.

Actually, the Windows update didn't resolve the issue.

But manually replacing the files from the USB zip file did.
[Android General] Captain_Throwback:
Has anyone gone and provided feedback to MS so they can actually FIX this problem? If everyone keeps using this workaround, it'll never actually get fixed.
[Android General] KEV500:
You are the best..Thank you, uninstalling Windows 7 dual boot on my Ultrabook:good::laugh:
[Android General] alexander7567:
Had this problem on my Windows 8.1 and it said the Microsoft fix was already installed... So I did it via your method and after a reboot it worked instantly.... Thanks!
[Android General] amir-456:
:(

Not worked for me!!

And i have no usb functionality now!!!

How can fix it?

My keyboard&mouse not working and i stock in start menu.

Plz help :((
[Android General] javvadi:
Need Original Windows 8.1 64bit usbhub.sys and usbport.sys files

The solution was excellent for flashboot and it worked for me. I forgot to take a backup of the usbhub.sys and usbport.sys files and after a reboot my USB Mouse & Keyboard not working. For now I'm using other keyboard & mouse with Connectivity - PS2. If you have Windows 8.1 64bit usbhub.sys and usbport.sys files please attach them

Thanks in advance

Javvadi
[Android General] domg73:
just use the command:

sfc /scannow

from an elevated command prompt... the original usb drivers will be restored.
[Android General] robisrobis:
thank you for fix

i have win 8.1 update 1

but without your fix i cant flash firmware on my prestigio PMP5101c

again i must say thank you very much
[Android General] Captain_Throwback:
http://xdaforums.com/showthread.php?p=50525263

If no one ever submits the info to Microsoft, it'll NEVER get fixed for other devices.
[Android General] paarthdesai:
the microsoft update says this is not for me....i have 8.1 pro .. i am soo tired with this **** now
[Android General] kostelo:
The fixed worked like a charm on HTC Desire (Bravo). At last a working solution. Thanks alot.
[Android General] Vitormellorj:
Yesssssss!!!!! Very nice! Thank you, I've tried for several days. Only the files copied and pasted the x64 folder in the directory: C :/ windows> system32> drivers. It worked perfectly. Thank you again.:laugh:
[Android General] jainanshal:
Now this worked!!!

[MENTION=4753858]janek2012[/MENTION]

You are the man...!! Of all other s**t circulating all over the internet, this is the only thing that works. It would have saved me a lot of time, energy & frustration if idiotic google gave me this result directly.

I tried the Microsoft way first, but stupid thing said that it is not for my system.. i don't know why when every eligibility criterion was satisfied :confused:

Anyways, I manually copied the 2 dll files because the script for some reason didn't work. Rebooted & voila... :victory:
[Android General] fredrick255:
The referenced stand alone windows update refuses to install for me on Win 8.1 x64 Pro.

I noticed there was an optional update rollup available that mentioned a BOS descriptor fix but doesn't seem to resolve the issue for me. For drivers, I'm using the ones in the HTC Driver folder the came with either HTC Sync or the Sync Manager.

update rollup: http://support.microsoft.com/kb/2967917/en-us

bos descriptor: http://support.microsoft.com/kb/2973456/en-us
[Android General] ivkom:
Excellent! Now one of my smart-phone (htc desire 601 dual sim) work fine with usb2. Thanx!
[Android General] nb2385:
works great

Went through a lot of different google results before I found this. Worked perfectly, microsoft update said my system wasn't compatible. Thanks so much for the fix. :)
[Android General] DevRocks123:
WORKS !!!

after trying various patches and almost every possible method of restoring adb drivers, i was dissapointed that none work for my HTC One V primou, then i found ur quick and easy fix and OMG!!!!! after applying it, my fastboot runs like a charm.!!!.....thank you bro, even the official update didn't fix it and the fix you provided works excellently...i owe u one bro.....thanks again......!!!!!!!!:laugh::good::D
[Android General] cool-face:
Yea, i cant install update, dirty method works! Tested on windows 8.1 x64 and HTC Desire HD
[Android General] gps3dx:
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.

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.

[IMG="VVVVPPPPRRRR - How to obtain"]http://xdaforums.com/attachment.php?attachmentid=2941854&stc=1&d=1411058255[/IMG]
[Android General] siropchik:
work well

It works!!

Thank you very much!:victory:
[Android General] DreamerTKM:
Thanks for the new workaround solution. But I have to say that this solution is very subjective to devices. Example like HTC and Sony which already reported to microsoft or the manufacturer itself came out some workaround on the drivers side can successfully work with this solution.

But for me, I'm using Samsung Galaxy S Plus, the main problem is windows read the VID, PID, REV as 0000,0000,0000 instead of 04E8 (Samsung), XXXX, XXXX so even the registry value is set, but the USB drivers still failed to point the address correctly.

So, I will stick to original workaround with windows 8 drivers until I changed my phone.

Thanks again.
[Android General] gps3dx:
Are you sure you've installed the right drivers ?

My solution suppose to help those who have HW that is OK & SW(drivers) that was installed as needed ( using the special restart method & enforcing the driver signature off ). :o

I can advise you to uninstall the driver completely from the device manager to get windows to install the default driver that it "Think" it should have.

( or to give you "unknown device" of some sort ) that way you may get the right VID&PID&REV details.

Be sure to install the right driver after that

WHILE enforcing the driver signature off

.

There are many sources for Samsung adb driver.

P.S - I got SII i9100 and didn't had any problem at all on the same win 8.1 that had problem with my HTC fastboot driver. :cowboy:
[Android General] gandolf007:
tanx alt but my problem don't fixed

i have USB 3.0 ports om my labtop (win 8.1 x64) and your solution not worked for me !! and don't installed Windows8.1-KB2917929-x64.msi !! say error :the update is not applicable to your computer

what should i do ?

pls help
[Android General] Galactus:
This worked wonders mate. In my case the VVVVPPPPRRRR folder was already set too. Cheers bud, I'd thank you 10 times if I could lol :good:
[Android General] kchaisu:
Thanks, changing usbport.sys and usbhub.sys files manually works for me on Win 8.1 Pro x64 bit on Acer Aspire 1810T with HTC Desire S, kitkat ROM. However, establishing new folder in HKEY does not work.

PS. I do not have ADB Interface and HTC Bootloader path as shown under My PC Name. I have Android device and My HTC path instead. Thanks.
[Android General] barondebxl:
How do u copy the 2 files and where?
[Android General] JovieBrett:
How am I supppsed to do this? My keyboard is not functioning, I cannot even boot to BIOS and safe mode because of my keyboard being unable to function :'(
[Android General] aleixsr:
Great this worked for me with HTC Desire S & Windows 8.1
[Android General] nice&easy:
Thanks for the solution, very helpful... I had to manually replace the files on the driver’s folder and reboot w8, then worked like a charm (for me, using usb 2.0 ports)
[Android General] lewonsky:
it seems u need to delete the backup files after replacing them.

not sure why but it seems to work on both my win 8.1 and 10 after doing this
[Android General] queser.info:
microsoft

the fix from microsoft don't work for me
[Android General] rienkandroid:
Can't install the Windows8.1-KB2917929-x64.msi !! say error :the update is not applicable to your computer

So your 'really dirty, dirty' fix still isn't obsolete. It worked for me. Thanx
[Android General] Gizmo0001:
solutions for ADB working on windows 8.1 i.e. solving the usb enumeration issue

to answer your questions regarding KB2917929: this fix will only help a few people out there using sony phones (see http://blogs.msdn.com/b/usbcoreblog...8-0-but-fail-on-windows-8-1-with-code-43.aspx).

So if you get the hint "this fix is unapplicable" / "das Update ist nicht für Ihren Computer geeignet" please use the secondbest option as described in http://xdaforums.com/showthread.php?p=55830683#post55830683.

If this still fails then go back to the "dirty fix" but mind that you use "sfc" to repair your usb drivers once Windows Updates or other USB devices fail (see http://xdaforums.com/showpost.php?p=50028102&postcount=13).
[Android General] 2girls1cup:
Warning about these methods

its recommended to immediately copy the original files back to your pc once you do whatever you need to do to your htc. Otherwise once you accept and windows updates, you will be stuck with non functioning usb ports as in my case.
[Android General] OnlinerUserBD:
Thankyou very much, it's worked on windows 8.1 (x86), htc desire bravo great job! (y)

firstly, I followed your updated 1st method, its failed to support at my windows 8.1 but when reversed to old dirty method just worked on my htc desire bravo (gsm) after searching around internet lots of methods and wasting more then 10 hours. I am happy now:)
[Android General] Ark-kun:
Those instructions are wrong. The registry value type should be BINARY with value 01 00 00 00 instead of DWORD.