Related
sorry if this clutters up the forum for a bit, i promise to delete it when it dies.
i've recently started using adb when i flashed over to 5.0.2h. i followed the instructions in the tutorial and was able to use adb. 2 nights ago, i began doing more complicated commands (for me) and tried to push a .apk into /system/app.
i wasn't immediately successful but i eventually got it in there and decided to reboot my phone. after this reboot, however, i lost the use of adb. i tried upgrading to the usb drivers haykuro posted, uninstalling them and re-trying the old one, rebooting the computer, rebooting my phone and none of it works. i've since wiped my phone and flashed it with the latest h build from haykuro (thanks haykuro!) but that didn't work either. now i'm trying to see if the 1.5 sdk will work.
i was wondering if anyone would have an idea about what i should do next. should i reinstall adb? try it on another computer? another cable? it's not the worst loss in the world, my phone is fine and my usb cable still works in the conventional way. i even checked to see if i somehow lost root and i was able to get su on the terminal emulator. but i still want the use of adb for nandroid, if nothing else.
thanks in advance!
I had the same problem after flashing to the G rom. I couldn't get ADB to work but fastboot recognized my phone and I was able to flash back to my backup. First time I did a complete wipe before flashing, second time, no wipe, made no difference in either case for me
When you plug Dream into your computer, does it show up in the Device Manager list? What is the entry? Hopefully it says HTC Dream Composite ADB Interface
I just had the same problem, I had to update the driver and it is working fine now.
Which driver did you use? I downloaded the one on the saphire port project page, but couldn't find a way to install it. When I open device manager, there is no ADB interface listed.
zer0day said:
Which driver did you use? I downloaded the one on the saphire port project page, but couldn't find a way to install it. When I open device manager, there is no ADB interface listed.
Click to expand...
Click to collapse
Give me a few minutes I will find you a link for it.
jordanjf86 said:
Give me a few minutes I will find you a link for it.
Click to expand...
Click to collapse
Here it is. http://dl.google.com/android/android_usb_windows.zip after downloading this when you go to update your driver in device manager make sure to use this. Hopefully this will help it worked for me.
jashsu said:
When you plug Dream into your computer, does it show up in the Device Manager list? What is the entry? Hopefully it says HTC Dream Composite ADB Interface
Click to expand...
Click to collapse
yes, that's what it comes up as. and i've tried the usb drivers from haykuro's page and they didn't work before and after rebooting my computer.
i'm on vista and it wont accept the updated drivers. it downloads the standard removable memory drivers and wont let me update to anything else. anybody have any ideas
just installed the 1.5 apk and adb and it works again. for people running haykuro builds, i would suggest trying this if you have adb problems. just intall the 1.5 sdk as normal, copy adb.exe and AdbWinApi.dll into \system32 and you should be good.
unless requested i will delete this thread in two days. thanks everyone!
Hmm... i tried that and its still not working ):
Ive tried like 10 different USB drivers from various sites including this one, downloaded the 1.5 SDK and installed it, wen through several reboots and it always says either that the driver is for the wrong platform, the most up to date one is ALREADY installed (HTC Bootloader), or that Windows couldn't find any drivers.
Under ADB Interface in device manager is "%USB\VID_0BB4&PID0FFF.DeviceDescRelease%"
did you try and update the driver through the device manager? i've heard that it's the only way to update it for some people.
I had already Posted & Solved This Issue here : http://forum.xda-developers.com/showthread.php?t=493703
Go Check It, It ll work for sure....
90% of the time the problem is with the drivers etc. Use this tutorial to fix that : http://goo.gl/OS3Vi
If you still encounter the problem then you can use ADBwireless available at google play to wirelessly connect your device to the computer
Hope it helps :highfive:
Hi
I actually replying about the bible quote you have mentioned? you into theology?
Hello ppls.
I've read some similar threads about this problem, tried some solutions, didn't worked and they didin't really had my situation.
So lets begin. My phone isn't recognized by my computer of anysort. When i plug the device i get this error: Windows has stopped this device because it has reported problems. (Code 43) .Tried solutions for the error with no succes.
I run Windows 7 64 bit,4gb Ram, Intel Quad Core 2,2 Ghz. I downloaded the drivers for the device from samsung, bummer when i manually try to update the drivers and set the path to where the drivers are it says The device is already up to date,even with online search.
What i've tried so far:
1. Tried in normal condition with KIES. Debugging off.
2. Debuggind on. Same
3. Different PC with windows 7 32 bits, same error, same solutions that don't work
4. Updating .Net framework
5. Installing a program that automaticly detects drivers. It didnt even see it.
6. Checking the cable for corrosion or anything else faulty. Cleaned it even.
7. Yelling are the stupid phone !!
Thank you.
rahbert said:
Hello ppls.
I've read some similar threads about this problem, tried some solutions, didn't worked and they didin't really had my situation.
So lets begin. My phone isn't recognized by my computer of anysort. When i plug the device i get this error: Windows has stopped this device because it has reported problems. (Code 43) .Tried solutions for the error with no succes.
I run Windows 7 64 bit,4gb Ram, Intel Quad Core 2,2 Ghz. I downloaded the drivers for the device from samsung, bummer when i manually try to update the drivers and set the path to where the drivers are it says The device is already up to date,even with online search.
What i've tried so far:
1. Tried in normal condition with KIES. Debugging off.
2. Debuggind on. Same
3. Different PC with windows 7 32 bits, same error, same solutions that don't work
4. Updating .Net framework
5. Installing a program that automaticly detects drivers. It didnt even see it.
6. Checking the cable for corrosion or anything else faulty. Cleaned it even.
7. Yelling are the stupid phone !!
Thank you.
Click to expand...
Click to collapse
Have you tried with a different USB cable?
No because i connected succesfully my friends galaxy fit with it, so the cable is not the problem.
thry manualy installing galaxy s drivers on pc?
Uninstall and reinstall the drivers.
Try different drivers.
Make sure you're using a Samsung wrong with the Samsung drivers.
Use a different PC.
Keep trying!
I gave up...I tried everything.Spent hours of searching forums and applying solution, nothing works... Tried On 3 different pc's. 1 with win 7 64bit, and the rest win 7 32 bit. I can't manually install the drivers either. Says there are already up to date when i set a location for the drivers to detect...I can't even use it as mass storage.
rahbert said:
I gave up...I tried everything.Spent hours of searching forums and applying solution, nothing works... Tried On 3 different pc's. 1 with win 7 64bit, and the rest win 7 32 bit. I can't manually install the drivers either. Says there are already up to date when i set a location for the drivers to detect...I can't even use it as mass storage.
Click to expand...
Click to collapse
To try using different drivers you would need to uninstall the current driver.
And just to be sure, you didn't flash to CM7/MIUI recently, not realizing Samsung drivers won't recognize your phone anymore, right? Nexus S drivers for those ROMs.
Its on the original ROM i think. Recently bought it second hand, 1 year old.
I couldn't find different drivers...except 32 bit and 64bit, but they all are the same version. Maybe post a link or something. Mine are 1.4.4.
Firmware version: 2.3.3
Baseband version i9000XXJVO
Kernel Version: 2.6.35.7-i9000xwjvh - CL184813 [email protected] #Dark_core_2.4 Mon May 16 15:02:38 EEST 2011
Build Number: DarkyRom JVH v10.1
SOLVED. The problem was from the ROM Darky 10.2. I went to a service did a resoft donno how they do it, installed me the original gingerbread 2.3.4 and now works like a charm!
rahbert said:
SOLVED. The problem was from the ROM Darky 10.2. I went to a service did a resoft donno how they do it, installed me the original gingerbread 2.3.4 and now works like a charm!
Click to expand...
Click to collapse
Just for future reference, this site is filled with tutorials on how to do just that. In fact, that is what this site is all about—new ROMs, new ideas, and how to get them onto your device. Look around next time.
upichie said:
Just for future reference, this site is filled with tutorials on how to do just that. In fact, that is what this site is all about—new ROMs, new ideas, and how to get them onto your device. Look around next time.
Click to expand...
Click to collapse
Dude i'm not the kinda of guy that doesn't research first. Like i mentioned i tried everything i found with no effect. The thing is, the problem reappeared after a day, with the new rom. Took it back to the service, said its a virus from some apps i installed...Is it possible? Thing is, it worked even after i restored all my apps.
I couldn't change the rom either because neither Odin or Heimdall saw my phone, if that is what you reffered to. If you know how to resoft a phone without the pc recognizing it (not even as a composite USB device in download mode or debugmode) and just Showing in Odin or Heimdall "Unknown Device" and failed at installing ClockworkMod, be my guest and redirect me to the tutorial, or tell me how to do it.
Thx
rahbert said:
Dude i'm not the kinda of guy that doesn't research first. Like i mentioned i tried everything i found with no effect. The thing is, the problem reappeared after a day, with the new rom. Took it back to the service, said its a virus from some apps i installed...Is it possible? Thing is, it worked even after i restored all my apps.
I couldn't change the rom either because neither Odin or Heimdall saw my phone, if that is what you reffered to. If you know how to resoft a phone without the pc recognizing it (not even as a composite USB device in download mode or debugmode) and just Showing in Odin or Heimdall "Unknown Device" and failed at installing ClockworkMod, be my guest and redirect me to the tutorial, or tell me how to do it.
Thx
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1347899
upichie said:
http://forum.xda-developers.com/showthread.php?t=1347899
Click to expand...
Click to collapse
How can i use Mobile Odin if i can't root it?
Anyway the problem has been identified as the driver behind the usb slot of the phone, At least that what the guy at the service said...for the moment i'm waiting. I'll keep you posted.
rahbert said:
How can i use Mobile Odin if i can't root it?
Anyway the problem has been identified as the driver behind the usb slot of the phone, At least that what the guy at the service said...for the moment i'm waiting. I'll keep you posted.
Click to expand...
Click to collapse
Throw it against the wall then. You ask us for help, disregard all of it, and then update us on what the service desk told you. If you will only listen to them, then don't ask us, kay? Appreciated.
Hi, there.
Actully, the rahbert's question is not bad. How can i use Mobile Odin if i can't root the device?
Or, how can I root without PC? Is it possible? I have exactly the same problem:
Nexus S (I9020), ICS 4.0.4(stock). When I plug the device: the error is reported(Code 43).
Should I try wipe data/factory reset? I really don't want to do this, because there is another good question: How can I fully backup my data(Titanium and so on) without root access? Can you suggest me something? Thanks.
Herman76 said:
Have you tried with a different USB cable?
Click to expand...
Click to collapse
Changing the USB cable worked for me. Thanks!!
my samsung galaxy s is not recognized by my computer no matter what i do!
don't know why, i've done some research, no results.
i've installed Kies, which i assume already installs the drivers, but when i connect, the computer shows no sign of connection (it says that i need to update drivers in device manager??) i tried different USB ports, toggled USB debugging on/off, NOTHING WORKS
the reason i want my computer to recognize the galaxy is because i want to update it to android 2.3.5 via odin. but when i enter download mode, the computer doesn't recognize it. when i'm in the system, the computer STILL doesn't recognize it...???
please somebody help, it's rooted, running a different MIUI version (not the ones in xda dev section), i'm not sure where i got it from, but it's called an ENG_MIUI?
CM7 (and subsequently MIUI) is built from the Nexus S source code, so find the proprer drivers for it. "CM7 drivers" should be a sufficient google search. Also, Kies sometimes interferes while using the other drivers. If you run into any problems, uninstall Kies.
Okaham said:
my samsung galaxy s is not recognized by my computer no matter what i do!
don't know why, i've done some research, no results.
i've installed Kies, which i assume already installs the drivers, but when i connect, the computer shows no sign of connection (it says that i need to update drivers in device manager??) i tried different USB ports, toggled USB debugging on/off, NOTHING WORKS
the reason i want my computer to recognize the galaxy is because i want to update it to android 2.3.5 via odin. but when i enter download mode, the computer doesn't recognize it. when i'm in the system, the computer STILL doesn't recognize it...???
please somebody help, it's rooted, running a different MIUI version (not the ones in xda dev section), i'm not sure where i got it from, but it's called an ENG_MIUI?
Click to expand...
Click to collapse
To get your phone recognized you need nexus s drivers. But that won't help you get it recognized by kies.
You need stock firmware on your phone to get it updated through kies.
Sent from my GT-I9000 using xda premium
I have same problem previously. But it solved after I do this: while Kies open, select Tools then press Install driver.
thanks guys, but how would i go about doing that? the directions i found don't make any sense?
ndemin said:
I have same problem previously. But it solved after I do this: while Kies open, select Tools then press Install driver.
Click to expand...
Click to collapse
Just to clarify, this won't help you. Samsung uses Samsung drivers. Since you do not currently have Samsung firmware on your phone, this won't do you any good. As previously stated by two very informative posters, you will need the Nexus S drivers to recognize your phone.
And, also as previously stated by just an absolutely wonderfully helpful poster, if you do a simple google search you'll find exactly what you need. Try either Nexus S Driver, CM7 Driver, Nexus S CM7 Driver, or really anything else similar. You could also check the CM7 Wiki, as I'm sure there would be a link for them there. And finally, if you simply search XDA Developers, I'm sure you'd find plenty of posts with what you need.
Hopefully that helps.
thanks
now my computer can see it when it's in android, but why does it STILL not see my Galaxy S in download mode???
do i need another set of drivers? (it said driver not found)
BTW THANKS GUYS!!! sorry if i'm being annoying
hello??
anybody??
Well did you install the Nexus S drivers yet?
upichie said:
Well did you install the Nexus S drivers yet?
Click to expand...
Click to collapse
yes, the nexus s drivers are installed, but i STILL can't connect through download mode...
try different computer, install samsung driver then connect your phone
still doesn't work???
Well, it seems to be a driver issue!
Try these (32-bit windows) but make sure that you are having a fresh win7 installed just in any case that your reg got corrupted with drivers (Ime ).
Still not working,then try on another pc..!
---------- Post added at 07:12 AM ---------- Previous post was at 07:06 AM ----------
upichie said:
Just to clarify, this won't help you. Samsung uses Samsung drivers. Since you do not currently have Samsung firmware on your phone, this won't do you any good. As previously stated by two very informative posters, you will need the Nexus S drivers to recognize your phone.
And, also as previously stated by just an absolutely wonderfully helpful poster, if you do a simple google search you'll find exactly what you need. Try either Nexus S Driver, CM7 Driver, Nexus S CM7 Driver, or really anything else similar. You could also check the CM7 Wiki, as I'm sure there would be a link for them there. And finally, if you simply search XDA Developers, I'm sure you'd find plenty of posts with what you need.
Hopefully that helps.
Click to expand...
Click to collapse
Well, CM7 drivers won't help SGS to get recognized on PC on DLD mode, you need another set of drivers and not those Nexus S's. I had the above ones installed on my PC (Google's your Best friend ) .
I had to install the drivers manually,
Right click on computer, click manage -> device something -> find your device in the list, select to update driver, search manually and enter the path to your android sdk and search.
Worked like a charm to me
Sent from my GT-I9000 using XDA App
pzayx said:
I had to install the drivers manually,
Right click on computer, click manage -> device something -> find your device in the list, select to update driver, search manually and enter the path to your android sdk and search.
Worked like a charm to me
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
computer could see device in download mode?
hi
i had same problem, but computer recognize the device as "unknown device"
in all modes, developed, storage etc...
i am close to think thats is problem of internal usb driver of the rom
want to downgrade from de device, whitout usb, but i dont know how do it, because i am not root, and its no possible in 2.3.4 whituot usb.
thanks
I had a lot of similar issues with my I9000, too.
Tried everything on ROM and driver side also on different computers.
Finally it turned out that my Micro USB connector was corroded.
I have around 30 people in our company that have the same phone, and 5 of them had similar issues. I guess it's a common problem with this device.
I took a toothpick and cleaned the contact of the connector by sliding it up and down for a couple of million times. This also did the trick for my colleagues.
I think it's at least worth to try it.
Good luck
i try to clean the contact, but still cant connect to the computer.
I wonder if a method of degrading the system with a signed rom from the recovery, without using the USB cable or ODIN.
i have a same problem. Any new solution?
snbmf said:
i have a same problem. Any new solution?
Click to expand...
Click to collapse
use this guide
Check this out! Links to useful Guides and " Banned " Documentaries
Hello all, first time poster, but I have been lurking for a few days absorbing what I can. I just recently got my first Android phone, the Droid Turbo. So far I love it. I am trying to use the awesome Debloater tool I found elsewhere, but I have a problem. When ever I connect my Droid Turbo to a computer in my house (desktop or laptop), I get an error in device manager. Neither the standard Google ADB driver, or the Universal ADB drivers seem to be working. I am not stupid when it comes to computers, but am I missing something? I have uninstalled, restarted and reinstalled both drivers a few times, I even tried using the SDK to install Google's drivers as well. USB debugging is turned on. I can't seem to find any USB drivers for the Droid Turbo at the Motorola site listed with Google. The phone is new, running 4.4.4 KitKat. I am running Windows 7 x64 on my PC, a fairly fresh install. I'm really at a loss to figure out what is going on, any help or a point in the right direction would be greatly appreciated . I have already searched most of the relevant information and videos on this sight, but perhaps I missed something.
Please keep up the good work! My phone is just begging for a root/unlocked bootloader with a clean Android install, But I will settle for no bloatware for now.
I was going to include a screenshot of what I see with my phone plugged in, but I don't have enough posts yet. None of the options of "Update Driver" result in it working, its as if it sees my Droid Turbo there, but I just don't have correct the drivers for it, and I cant find the right ones.
Install drivers from motorola and select driver manualy, dont work with Windows XP
matheus_sc said:
Install drivers from motorola and select driver manualy, dont work with Windows XP
Click to expand...
Click to collapse
at this link:
Motorola Device Manger/USB drivers.
https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481
Awesome!
Awesome! That link is what I was missing. Thanks a lot to both of you!
Hello, I just received my Nexus 6 but I have a problem which also was also a problem on my old note 2. It won't recognize the drivers or install them. I did some test, it connected and instantly updated the drivers on another machine, so it's not the cable or the phone(A windows 7 machine), and it also works with my windows 10 tablet.
I also removed digital signature requirement for installing them, doesn't seem to work. I literally have no clue and did my research for about 1 hour to no avail. I must have done something way long in the past on windows 8.1 to flash my note and that ****ed up somewhere in windows, but I have absolutely no clue here.
Worst comes to worst, I'll just reformat, as this was an "upgrade" from windows 8.1.
Couldn't this be linked to motherboard drivers possibly?
Edit : http://puu.sh/jVpz1/38c5e640f8.jpg I tried manually to uninstall/reinstall, to no avail.
Lyper said:
Hello, I just received my Nexus 6 but I have a problem which also was also a problem on my old note 2. It won't recognize the drivers or install them. I did some test, it connected and instantly updated the drivers on another machine, so it's not the cable or the phone(A windows 7 machine), and it also works with my windows 10 tablet.
I also removed digital signature requirement for installing them, doesn't seem to work. I literally have no clue and did my research for about 1 hour to no avail. I must have done something way long in the past on windows 8.1 to flash my note and that ****ed up somewhere in windows, but I have absolutely no clue here.
Worst comes to worst, I'll just reformat, as this was an "upgrade" from windows 8.1.
Couldn't this be linked to motherboard drivers possibly?
Edit : http://puu.sh/jVpz1/38c5e640f8.jpg I tried manually to uninstall/reinstall, to no avail.
Click to expand...
Click to collapse
Delete all your android drivers, and try this:
http://forum.xda-developers.com/showthread.php?t=2588979
I removed 4 adb drivers and many samsung ones, installed with administrator settings the linked content, then it tried to install the nexus 6 via the default windows updated. Seemed to work, get the sound for connection, but no option to transfer my stuff. I tried uninstalling the drivers and re-installing, still nothing.
http://puu.sh/jVt0q/57fb6bf8d3.png
No more ideas?
Lyper said:
No more ideas?
Click to expand...
Click to collapse
Been a long time since I did it. Have to download the google driver. Then go to device manager where you delete the Android driver. Right click and will ask for where to get the driver. Pick local to search PC for driver and install from there. That the best I remember off top of my head. On mine is Asus driver. I deleted it and then searched PC for the Google driver.
prdog1 said:
Been a long time since I did it. Have to download the google driver. Then go to device manager where you delete the Android driver. Right click and will ask for where to get the driver. Pick local to search PC for driver and install from there. That the best I remember off top of my head. On mine is Asus driver. I deleted it and then searched PC for the Google driver.
Click to expand...
Click to collapse
Yeah well I did that multiple times, which didn't work. I really don't feel like reformatting, ho boy, but I really gotta get this going. Thanks for the suggestion!
Try switching ports.
Sent from my Nexus 6 using Tapatalk
I tried switching ports.
Ok so the list of things I tried : Manually removing any drivers that had to do with android/usb phone, I reinstalled the drivers for my motherboard, I fixed every system inconsistency with ccleaner, removed android studio. I had also manually removed any prior detection fo the nexus 6 in the device manager. It will once again pop up the "driver install" from windows, complete, but be impossible to manually update via device manager as it doesn't recognize my device.
I'm also using the default cable from my nexus 6, and tried others. Is there anything else to do? Otherwise reformatting tonight. Thanks everyone for the support.
Hello, sorry to keep bumping this thread. I just reformat... and the problem still persists. I have no clue what to do anymore, I literally tried everything I could possibly think of.
Anyone got any ideas? To state again, I'm running windows 10 x64.
http://puu.sh/k0qiv/a4802d7e43.png
I just found that when I used the "reset pc" function of Windows, I still have remnants of adb. What am I supposed to do here? Any ideas how to remove them fully? Could that be the problem?
Nevermind, I did a total complete reformat now, still doesn't work. I'm literally out of ideas now.
Should I contact my motherboard manufacturer (MSI) ?
not sure what to tell you, but definitely samsung drivers and motorola drivers do not play well together very often
Lyper said:
http://puu.sh/k0qiv/a4802d7e43.png
I just found that when I used the "reset pc" function of Windows, I still have remnants of adb. What am I supposed to do here? Any ideas how to remove them fully? Could that be the problem?
Click to expand...
Click to collapse
Not sure what you lost. I did an upgrade from 8.1 to 10. All my SDK, Java, adb/fastboot, Path Variables, ect remained intact. Depending on Make and Model of PC there have been a lot of drivers missing or needing updates. The PC should see the phone regardless of adb/fastboot status. It has to be a driver on PC side. The OS supports it. It should show as an Android device even if it doesn't say Nexus 6. Nexus 6 shows the Google Driver is good.
prdog1 said:
Not sure what you lost. I did an upgrade from 8.1 to 10. All my SDK, Java, adb/fastboot, Path Variables, ect remained intact. Depending on Make and Model of PC there have been a lot of drivers missing or needing updates. The PC should see the phone regardless of adb/fastboot status. It has to be a driver on PC side. The OS supports it. It should show as an Android device even if it doesn't say Nexus 6. Nexus 6 shows the Google Driver is good.
Click to expand...
Click to collapse
Can this be the problem?
http://www.msi.com/support/mb/P67AC43_B3.html#down-driver&Win10 64
There doesn't seem to be any drivers for windows 10, I tried installing the windows 8 ones, but that didn't work.
Lyper said:
Can this be the problem?
http://www.msi.com/support/mb/P67AC43_B3.html#down-driver&Win10 64
There doesn't seem to be any drivers for windows 10, I tried installing the windows 8 ones, but that didn't work.
Click to expand...
Click to collapse
Have you tried a Windows update since the original boot. On my son's AZUS the touchpad driver was bad. It had changed driver to a Generic. Deleted that driver and ran Windows update and it found the new driver. Worth a shot. Hard to tell what to do. I couldn't see any differences after the Win 10 upgrade. Didn't even effect my dual boot Linux. My friend just lost lost the drive sync to his Linux setup.
---------- Post added at 11:40 AM ---------- Previous post was at 11:38 AM ----------
Just an update, I cannot believe I found the problem while I kept digging.
Get this.
It was because I had Windows 10 N version. I am not ****ing kidding. Somehow the windows bloatware makes it so I'm unable to install phone drivers. It seems to be a recurrent problem because my friend has another phone and it did the same to him. How the **** is this a thing? Like, how could microsoft let such a **** up go by and there hasn't been a big controversy? Am I missing something?
I feel like the cheaper version of an OS gimping the user by removing such basic function as installing phone drivers is insane. But then you can fix it by installing the media pack for your respective OS, but you have to know that.
I'll leave this up if anyone ever searches for these terms.
Lyper said:
Just an update, I cannot believe I found the problem while I kept digging.
Get this.
It was because I had Windows 10 N version. I am not ****ing kidding. Somehow the windows bloatware makes it so I'm unable to install phone drivers. It seems to be a recurrent problem because my friend has another phone and it did the same to him. How the **** is this a thing? Like, how could microsoft let such a **** up go by and there hasn't been a big controversy? Am I missing something?
I feel like the cheaper version of an OS gimping the user by removing such basic function as installing phone drivers is insane. But then you can fix it by installing the media pack for your respective OS, but you have to know that.
I'll leave this up if anyone ever searches for these terms.
Click to expand...
Click to collapse
Can you tell where can I find the media pack for windows 10?
Thanks.