Mobile device not working 8.1 FIX - Microsoft Surface

Quick fix for your mobile device not working in Surface 8.1 preview ( mine Samsung Galaxy S2) just go to settings>change pc settings>update & recovery>recovery>refresh. Just wait until it finishes and plug in your device and voilĂ .
Tried and tested on cameras and several mobile phones.
Not my hard work as found this on MS forums - thanks AlphaPapa ?

1964ad said:
Quick fix for your mobile device not working in Surface 8.1 preview ( mine Samsung Galaxy S2) just go to settings>change pc settings>update & recovery>recovery>refresh. Just wait until it finishes and plug in your device and voilĂ .
Tried and tested on cameras and several mobile phones.
Not my hard work as found this on MS forums - thanks AlphaPapa ?
Click to expand...
Click to collapse
When I try to do this, I get a message about the proper files not being on my device, and it won't use the 8.0 recovery USB and files I have on there.

purple.epod said:
When I try to do this, I get a message about the proper files not being on my device, and it won't use the 8.0 recovery USB and files I have on there.
Click to expand...
Click to collapse
I am having the same problem, has anyone figured it out?

Related

how to avoid usb not recognized in download mode

hi, after a year of trying custom roms i learned that the most suitable rom is the stock rom after uninstalling bloatware and system apps u dont use
and i learned that the reason that message usb not recognized appers after connecting ur phone to pc in doanload mode is that you are runnig a windows other than windows 7.
download mode works only on windows 7 ( with experience )
so , to be sure , i advice to install samsung kies from official site , install it and make sure to check install mobile drivers and then restart pc
ahmedteling said:
hi, after a year of trying custom roms i learned that the most suitable rom is the stock rom after uninstalling bloatware and system apps u dont use
and i learned that the reason that message usb not recognized appers after connecting ur phone to pc in doanload mode is that you are runnig a windows other than windows 7.
download mode works only on windows 7 ( with experience )
so , to be sure , i advice to install samsung kies from official site , install it and make sure to check install mobile drivers and then restart pc
Click to expand...
Click to collapse
You do realize none of this is true?
In MY experience, Download mode works with every windows! I have personally tried XP, 7, 8 and 8.1. Sir, you'r argument is false and invalid... Reported...
Reason for reporting: Post contains non-useful and false information that is misleading and simply wrong and might end up being harmful as Kies is not only incompatible with legacy devices but also known to be harmful, proved by a large number of devices being soft bricked, thank you.
AXAz0r said:
You do realize none of this is true?
In MY experience, Download mode works with every windows! I have personally tried XP, 7, 8 and 8.1. Sir, you'r argument is false and invalid... Reported...
Reason for reporting: Post contains non-useful and false information that is misleading and simply wrong and might end up being harmful as Kies is not only incompatible with legacy devices but also known to be harmful, proved by a large number of devices being soft bricked, thank you.
Click to expand...
Click to collapse
i have win 8 i raped the internet to make download works but no luck , till last week i tryed with my sister win7 laptop and it works
ahmedteling said:
i have win 8 i raped the internet to make download works but no luck , till last week i tryed with my sister win7 laptop and it works
Click to expand...
Click to collapse
See proof screenshots in attachments.
Fun fact. I didn't download Kies, i didn't download any drivers, i didn't use any tricks. All i did is this:
1. Run ODIN 4.42
2. Boot in Download Mode
3. Plug in USB
Oh! Right! Also, you might want to enable automatic updates in your system... you know, so windows can automatically install the drivers?
And thats it...
galaxy fit did not shows on windows 8.1
u can see the screen short
sudhanshu2099 said:
u can see the screen short
Click to expand...
Click to collapse
install samsung usb mobile driver download from google
i solved the problem by using windows 7 , i were using windows 8
Sent from my Lenovo A516 using Tapatalk

[Q] All of a sudden no USB or adb/fastboot detction

Hi folks,
wasn't really sure where to post this thread as my phone doesn't have a separate section and since this is more of a general issue rather than one related to a specific phone model, thought I'd try my luck here.
Anyways onto the problem - was gifted a Micromax A092 a few days back. Worked fine until last night when Windows stopped detecting it. When this issue first cropped up, a few times of disconnecting & reconnecting the USB cable got the phone working again but after I plugged in another phone to transfer data and reconnected mine, the issue became permanent and continues to persist.The phone charges when connected to the wall but doesn't charge nor does it get detected when plugged into the PC.
Now when I pull the USB cable and stick it into a different port on the PC, for a second or two, the "connected in charging mode" message appears in the pull down menu and Windows detects phone memory/storage briefly before both disappear. I haven't had the opportunity to plug it into a different machine to check whether its being detected but I can assure you that the USB cable isn't the issue as every other phone in the house works with all the cables I have been using ( 3 to be precise - 2 Micromax and a Sony cable).
Another strange thing I think I should mention in the hope that it could lead to a resolution is that ever since this issue started, none of the phones are being detected by fastboot/adb and don't appear in Device Manager under Android Device as Android ADB Interface. Just two days back, I flashed an Xperia M with fastboot but now the phone doesn't show up under Android Devices, just as Sony 0104 or something. Same with a Galaxy Star Pro. I have reinstalled Android SDK, usb drivers, fastboot/adb but no dice. Opening up the command prompt in the adb/fastboot folder and typing fastboot devices doesn't list any of these phones either.
So can someone please help me in determining whether this is a software or a hardware issue? Any suggestions are welcome and truly appreciated. Thanks.
If you updated your Windows to Windows 8.1 than have following problem:
Since Windows 8.1 MS expects a USB BOS descriptor - USB 2.0/3.0
see htthttp://blogs.msdn.com/b/usbcoreblog/archive/2013/11/26/why-does-my-usb-device-work-on-windows-8-0-but-fail-on-windows-8-1-with-code-43.aspx
There is a dirty solution which works on updated Windows 8.1 update 1:
http://forum.xda-developers.com/showthread.php?t=2598155
Maybe you need a reboot.
fanmile said:
If you updated your Windows to Windows 8.1 than have following problem:
Since Windows 8.1 MS expects a USB BOS descriptor - USB 2.0/3.0
see htthttp://blogs.msdn.com/b/usbcoreblog/archive/2013/11/26/why-does-my-usb-device-work-on-windows-8-0-but-fail-on-windows-8-1-with-code-43.aspx
There is a dirty solution which works on updated Windows 8.1 update 1:
http://forum.xda-developers.com/showthread.php?t=2598155
Maybe you need a reboot.
Click to expand...
Click to collapse
Thanks for the reply
No I haven't updated Windows. Mine's a standalone Win 8.1 installation that's been running for a good few months now.
Like I said, w/o any rhyme or reason, it stopped working in the middle of the night and so did fastboot/adb. I remember typing fastboot devices and having the phone detected just prior to Windows acting up and in following time period, I don't remember installing any software or applying any Windows updates. This issue basically just came out of nowhere.
I'll take a look at the links but will it work for someone who was already using 8.1?
XenolithicYardZone said:
I'll take a look at the links but will it work for someone who was already using 8.1?
Click to expand...
Click to collapse
These work arounds are only for Windows 8.1. The MS Patch should work, if you have not the latest patches. I have the latest patches installed and I cannot install the patch. I need the dirty solution for my old samsungs galaxy models and HTC One X with cyanogenmod 11 - M8.
At the moment I have no further ideas to help you.
fanmile said:
These work arounds are only for Windows 8.1. The MS Patch should work, if you have not the latest patches. I have the latest patches installed and I cannot install the patch. I need the dirty solution for my old samsungs galaxy models and HTC One X with cyanogenmod 11 - M8.
At the moment I have no further ideas to help you.
Click to expand...
Click to collapse
No worries man....guess what? On a whim, I plugged it back in and voila...there was detection. I have no idea how it started working but I have been at it all day and something probably did the trick though I have no clue what it was which is annoying me because if this were to happen again, I would be back to square one.
Ah I see...I did download the patch you had linked to but before I could get around to installing it, this thing started working again. Anyways good to know it won't work with the latest updates as I installed the latest Windows update just this morning myself.
Although now my phone's being detected, the fastboot problem still persists. Neither my phone or any other phones I have access to are detected via fastboot. They all show up under Device Manager as Android ADB Interface but are not recognized by fastboot. Its really irritating me because only 2 days back I flashed the Xperia M on the same damn OS but no dice now. I applied the Windows update hoping it would fix this issue but no luck so far. No software installations, no Window's tweaking...nothing. Hell I haven't even rebooted the PC in the last few days until this started happening. Strange. More research....yay
If you happen to recollect or come across any other workarounds, please do let me know.
use this driver worked for me
download these driver this is only driver fault
d-h.st/ZUh
copy link and download lenovo.zip and in device manager select android and use update driver option to install driver and its done try it works for me
get drivers from
micromax official website

[Q] Computer won't recognize S6

Hi,
The title pretty much sums it all, it won't connect at all. Driver or no driver, oem cable or not and stock rom or not. Can't even ADB in...
But ! It does work on my laptop (without drivers), so it's not a faulty device.
Anyone have any idea ?
*Edit: Both my laptop and desktop computers are running Win 8.1
dw4 said:
Hi,
The title pretty much sums it all, it won't connect at all. Driver or no driver, oem cable or not and stock rom or not. Can't even ADB in...
But ! It does work on my laptop (without drivers), so it's not a faulty device.
Anyone have any idea ?
*Edit: Both my laptop and desktop computers are running Win 8.1
Click to expand...
Click to collapse
It's the fingerprint security blocking access to the S6's data, you have to unlock screen on the S6 and your Windows will see the drive
vegetaleb said:
It's the fingerprint security blocking access to the S6's data, you have to unlock screen on the S6 and your Windows will see the drive
Click to expand...
Click to collapse
Thanks mate, but i already tried with screen unlocked. It might be a little more serious than that.
Remove all samsung drivers from control panel, then re install.
blud7 said:
Remove all samsung drivers from control panel, then re install.
Click to expand...
Click to collapse
Thanks again bro, but i already tried that.
SmartSwitch for PC has a RE-install device drivers option.
try running that.
kimkara said:
SmartSwitch for PC has a RE-install device drivers option.
try running that.
Click to expand...
Click to collapse
Okayyyyyyyy, i figured it out... So i was trying your method, installing SmartSwitch, and it wouldn't install because i didn't have the "Media Feature Pack". Because i'am running Windows 8.1 N on my desktop pc.
So i installed that media bull**** pack and then !!!! Miracle, it worked ! Didn't even need smartswitch. And if you are asking yourselves why is it working on my laptop, well the answer is very simple. My laptop is running a standard version of Windows 8.1... It actually make perfect sense the S6 only connects in PTP or MTP, which are both multimedia "modes". And i still can't adb into the device, must be coming from somethings else !
Anyway thanks to everyone for your help !
dw4 said:
Okayyyyyyyy, i figured it out... So i was trying your method, installing SmartSwitch, and it wouldn't install because i didn't have the "Media Feature Pack". Because i'am running Windows 8.1 N on my desktop pc.
So i installed that media bull**** pack and then !!!! Miracle, it worked ! Didn't even need smartswitch. And if you are asking yourselves why is it working on my laptop, well the answer is very simple. My laptop is running a standard version of Windows 8.1... It actually make perfect sense the S6 only connects in PTP or MTP, which are both multimedia "modes". And i still can't adb into the device, must be coming from somethings else !
Anyway thanks to everyone for your help !
Click to expand...
Click to collapse
good to know, glad you got it working.

s6 not connecting to windows

Hi all, I have been having a problem for the longest time now. My s6 refuses to connect to any pc. My first laptop had windows 7 on it and the s6 would successfully connect to it. That laptop is no more and i upgraded to a new one with win 10 installed on it. This laptop along with 2 others windows 7 completely refuses to connect to my phone. I think i have tried every "solution" but nothing works. My phone is rooted with a custom rom and the fast charge also refuses to work. I need to be able to connect to windows so i can reinstall the original firmware for a warranty exchange. Yes, i have all sumsung drivers installed, i have the original cable (and more), i tried smart switch, it still doesn't work. Any tips will be greatly appreciated. Thank you
Go to: Settings -> About Phone -> Tap on the build number 7 times to enable Developer Options -> Go to Developer Options and enable USB-Debugging
Now try connecting it to your PC
renolz said:
Go to: Settings -> About Phone -> Tap on the build number 7 times to enable Developer Options -> Go to Developer Options and enable USB-Debugging
Now try connecting it to your PC
Click to expand...
Click to collapse
Thank you for the response, however i have tried that multiple times with no luck
Ayoodannyx said:
Thank you for the response, however i have tried that multiple times with no luck
Click to expand...
Click to collapse
bump
same thing here. Not sure why but my phone doesnt come out the usb notification thing when i plug it into my laptop
austinjklim said:
same thing here. Not sure why but my phone doesnt come out the usb notification thing when i plug it into my laptop
Click to expand...
Click to collapse
bump..
can someone please help me sort this out? I have tried numerous methods to get the phone to connect, all of which has been unsuccessful. Everyone knows the struggle of not being able to connect to windows.. thanks in advance.
The problem could be the USB port on the phone. Or the data / charging cable may be faulty.
Try download Shortcut master lite from playstore, run secret code explorer in it, then code 0808, and set AP and MTP+ADB to see phone as disk in windows, this helped me, hope it will help you.

Question Fastboot not working in Windows 11 [Resolved]

Hello!
I cant get my Windows 11 virtual machine to detect my Xiaomi 12 when its in Fastboot mode. Does any one happen to have any ideas to solve this?
It shows up as 'Android' in device manager. I've also attempted to install a drivers manually and none of them seem to be acceptable. Weirdly, my Xiaomi 12 is recognised when its in regular, usb transfer mode and the MiUnlockTool by Francesco Tescari even recognises it then too. For context, debugging mode and enable bootloader settings have been enabled in MIU 13.
Any help would be greatly appreciated. Thanks
eshlad said:
Hello!
I cant get my Windows 11 virtual machine to detect my Xiaomi 12 when its in Fastboot mode. Does any one happen to have any ideas to solve this?
It shows up as 'Android' in device manager. I've also attempted to install a drivers manually and none of them seem to be acceptable. Weirdly, my Xiaomi 12 is recognised when its in regular, usb transfer mode and the MiUnlockTool by Francesco Tescari even recognises it then too. For context, debugging mode and enable bootloader settings have been enabled in MIU 13.
Any help would be greatly appreciated. Thanks
Click to expand...
Click to collapse
First thing to do is install this device drivers https://androidmtk.com/download-xiaomi-usb-drivers , then reboot and try to reconnect your device. This may fix our problem.
WhiteCoffeeCat said:
First thing to do is install this device drivers https://androidmtk.com/download-xiaomi-usb-drivers , then reboot and try to reconnect your device. This may fix our problem.
Click to expand...
Click to collapse
Thanks for the suggestion! I will attempt these. Fingers crossed
I have previously attempted to install adb driver but had some trouble. When installing using Device Manager, the locate .inf dialog refuses to accept my selection. I dont seem to be any error. When attempting to do so via the folder (and sub folders) it says no drivers found. Perhaps i'm doing this totally wrong?
Thanks again for your suggestion @WhiteCoffeeCat .
I've attempted to install the drivers. The Qualcomm worked fine but I've been unable to install the ADB driver. I've tried to bypass driver signatures and ect and even that didnt work.
So as of now, when my Xiaomi is in fastboot mode, it shows up as 'Android' in device manager.
eshlad said:
Thanks again for your suggestion @WhiteCoffeeCat .
I've attempted to install the drivers. The Qualcomm worked fine but I've been unable to install the ADB driver. I've tried to bypass driver signatures and ect and even that didnt work.
So as of now, when my Xiaomi is in fastboot mode, it shows up as 'Android' in device manager.
Click to expand...
Click to collapse
Put Windows into testing mode before installing drivers in Miflash, adb.. Run cmd prompt as admin and type bcdedit -set TESTSIGNING ON or bcdedit -set TESTSIGNING OFF for disabling testing mode.
Thanks @Stefke93 ! I gave that a try but still had the same outcome as before.
That said, I did find a way to resolve the problem i had....So i was able to install the ADB drivers in Device manager, I added a legacy hardware, selected Universal Serial Bus Function devices, and from their i found ADB usb driver. After that, it started to work fine.
Thanks everyone for the help. Got there in the end... I guess due to my back luck so far i was due a win... i didnt have to wait to unlock, i could do so immediately.
eshlad said:
Thanks @Stefke93 ! I gave that a try but still had the same outcome as before.
That said, I did find a way to resolve the problem i had....So i was able to install the ADB drivers in Device manager, I added a legacy hardware, selected Universal Serial Bus Function devices, and from their i found ADB usb driver. After that, it started to work fine.
Thanks everyone for the help. Got there in the end... I guess due to my back luck so far i was due a win... i didnt have to wait to unlock, i could do so immediately.
Click to expand...
Click to collapse
how?
goila said:
how?
Click to expand...
Click to collapse
Hello, the same thing happened to me yesterday, I'll explain: you connect your Xiaomi 12 in fastboot mode, you right click on My PC and select manage, device manager, select the android device and right click, update driver, search for driver in my PC, choose drivers available on my PC, show all devices, use disk and look for the folder where you have saved the file that I am attaching (android_winusb), select Android ADB Interface and click Next, Done.
jholfran3 said:
Hello, the same thing happened to me yesterday, I'll explain: you connect your Xiaomi 12 in fastboot mode, you right click on My PC and select manage, device manager, select the android device and right click, update driver, search for driver in my PC, choose drivers available on my PC, show all devices, use disk and look for the folder where you have saved the file that I am attaching (android_winusb), select Android ADB Interface and click Next, Done.
Click to expand...
Click to collapse
Thanks, but that doesn't help, otherwise I've already done it. I had m1 mac and with parallel desktop only the possibility to install win 11.. win 11 sucks.. I installed win10 on an intel mac in parallel and that solved my problem
eshlad said:
Thanks @Stefke93 ! I gave that a try but still had the same outcome as before.
That said, I did find a way to resolve the problem i had....So i was able to install the ADB drivers in Device manager, I added a legacy hardware, selected Universal Serial Bus Function devices, and from their i found ADB usb driver. After that, it started to work fine.
Thanks everyone for the help. Got there in the end... I guess due to my back luck so far i was due a win... i didnt have to wait to unlock, i could do so immediately.
Click to expand...
Click to collapse
Bro plz help me.
I'm also using Windows 11 in Desktop parallels 18 in Mac m1.
I'm facing the same issue.
Can't install the android bootloader interface.
After clicking ok butter after selection of fastboot driver location, nothing happens!
Seeking ur help.
Please
ItsmeeVishal said:
Bro plz help me.
I'm also using Windows 11 in Desktop parallels 18 in Mac m1.
I'm facing the same issue.
Can't install the android bootloader interface.
After clicking ok butter after selection of fastboot driver location, nothing happens!
Seeking ur help.
Please
Click to expand...
Click to collapse
Have you tried to disable driver signature enforcement in windows 11.
istampal said:
Have you tried to disable driver signature enforcement in windows 11.
Click to expand...
Click to collapse
Yeah, i tried it.
Nothing happened.
ItsmeeVishal said:
Yeah, i tried it.
Nothing happened.
Click to expand...
Click to collapse
Hey,
So I had so many issues installing the drivers to allow my VM to detect my phone in fastboot mode.
This is what worked for me (quote below). I swear I attempted this a number of times with different cables and it eventually worked. Mine seemed to work with an apple usb C cable instead othe official xiaomi cable with a usb c converter for the m1 mac.
eshlad said:
That said, I did find a way to resolve the problem i had....So i was able to install the ADB drivers in Device manager, I added a legacy hardware, selected Universal Serial Bus Function devices, and from their i found ADB usb driver. After that, it started to work fine.
Click to expand...
Click to collapse
eshlad said:
Hey,
So I had so many issues installing the drivers to allow my VM to detect my phone in fastboot mode.
This is what worked for me (quote below). I swear I attempted this a number of times with different cables and it eventually worked. Mine seemed to work with an apple usb C cable instead othe official xiaomi cable with a usb c converter for the m1 mac.
Click to expand...
Click to collapse
What VM were u using?
I'm using parallels Desktop 18
eshlad said:
Hey,
So I had so many issues installing the drivers to allow my VM to detect my phone in fastboot mode.
This is what worked for me (quote below). I swear I attempted this a number of times with different cables and it eventually worked. Mine seemed to work with an apple usb C cable instead othe official xiaomi cable with a usb c converter for the m1 mac.
Click to expand...
Click to collapse
I tried to do what u said but don't know what to do next.
Plz see the attached video video and tell me what wrong I'm doing.
After clicking on legacy hardware, what are other steps......
And, thank you so much for reply!
eshlad said:
Hello!
I cant get my Windows 11 virtual machine to detect my Xiaomi 12 when its in Fastboot mode. Does any one happen to have any ideas to solve this?
It shows up as 'Android' in device manager. I've also attempted to install a drivers manually and none of them seem to be acceptable. Weirdly, my Xiaomi 12 is recognised when its in regular, usb transfer mode and the MiUnlockTool by Francesco Tescari even recognises it then too. For context, debugging mode and enable bootloader settings have been enabled in MIU 13.
Any help would be greatly appreciated. Thanks
Click to expand...
Click to collapse
Hello.
I got that same problem, solved by connecting a multiport usb on my computer, then connecting my device MI12TPro on that multiport... then everything went better
Titek said:
Hello.
I got that same problem, solved by connecting a multiport usb on my computer, then connecting my device MI12TPro on that multiport... then everything went better
Click to expand...
Click to collapse
Hi Tek,
I have had many issues with windows and fastboot,
some cables would work with some of the ports and then not.
My pc has 12 usb ports, yet it was still hit and miss whether fastboot would work on my Poco F3.
I tried your tip and after using a cheapy Targus 4 port usb adaptor, my "FASTBOOT PROBLEMS ARE NOW SOLVED"
now what am i going to do with my 7 surplus USB-C Cables
Many thanks for your TIP

Categories

Resources