If I enable USB debugging on my Verizon Galaxy Nexus and connect the phone to my Windows 8 machine, the PC crashes.
Has anyone else successfully connected to a win8 pc while in debug mode?
I have problems like this on my win8 too.
Windows 8, while it is in RTM mode, there is still a lot of work to be done on it. I would not recommend upgrading your desktop or notebook, unless you have a touch screen. Win8 is awful in my opinion, with some cool features.
Alehbye
Alehbye said:
Windows 8, while it is in RTM mode, there is still a lot of work to be done on it. I would not recommend upgrading your desktop or notebook, unless you have a touch screen. Win8 is awful in my opinion, with some cool features.
Alehbye
Click to expand...
Click to collapse
Sadly as an IT admin I don't have the luxury of "Skipping" OS's and must learn them whether I like them or not. I will test this out and get back to you OP.
Thanks. I don't mean for this to turn into the pros/cons of win8, I was curious if others had seen the same behavior.
The system looks like it tries searching for a compatible driver and crashes with a "Bad_Pool_Header" error.
For me windows 8 installed the correct drivers by itself all i had to do is enable it in device manager
Both of my Dell workstations crashed, but my Lenovo ThinkPad didn't. Appears to be hardware/driver related. I'll keep digging.
I also have the same problem and error. Any solutions?
had that problem only once, now it works fine
Sent via Tapatalk 2 from my GNex running CM10
vijaykd said:
I also have the same problem and error. Any solutions?
Click to expand...
Click to collapse
I resolved the blue screens by installing Samsung Kies which installs the USB drivers for the Galaxy Nexus. Afterwards Windows 8 (Pro RTM 64bit) correctly installs all drivers when using USB Debugging mode, no more blue screens.
tripmckay said:
I resolved the blue screens by installing Samsung Kies which installs the USB drivers for the Galaxy Nexus. Afterwards Windows 8 (Pro RTM 64bit) correctly installs all drivers when using USB Debugging mode, no more blue screens.
Click to expand...
Click to collapse
That seems to have fixed it! I even uninstalled the Samsung Kies software (but kept the drivers) and everything is working smoothly.
Thanks again.
Related
This is intended for people which run KIES and device is not seen, neither the message "connecting..." appear on KIES, and MTP application does not start on Samsung galaxy.
If you moved com.android.* and com.sec.android.* into some path which is not /data/data you may have this problem. At least this is what happend to me, after I moved file back MTP start and Kies recognize the device.
never moved anything it simply does not work on Windows 7 32bit.
no magic helped ... no formating internal sd nor anything else ... i've read whole fracking day on the web how to deal with this issue and none of the solution worked.
SGS GT-i9000 ECLAIR.XFJM3 rooted
disabling launcherpro fixed it for me.
im told other launchers cause issues too
Eh, really, problems on Win 7 32bit? Haha that's so strange because it works almost flawlessly on Windows 7 64bit. Perhaps the first time there's better support for 64bit than 32bit.
Yes, you MUST run TWlauncher (standard launcher in Touchwiz) and if you got Windows 7, you might wanna download some third party drivers.
I'm on Windows 7 64bit and I downloaded the win7 x64 samsung galaxy s drivers form softpedia.
well the mtp driver doesnt install on my 64 bit computer.
It works on windows 7 32 and 64 bit just fine
No third party drivers and no magic. It's all down to individual system config otherwise it would be the same for everybody.
Incidentally, there is an update out for Kies taking it to version 1.5.1.10074_45
g0c said:
never moved anything it simply does not work on Windows 7 32bit.
no magic helped ... no formating internal sd nor anything else ... i've read whole fracking day on the web how to deal with this issue and none of the solution worked.
SGS GT-i9000 ECLAIR.XFJM3 rooted
Click to expand...
Click to collapse
have you googled for FileSearcherforKiesFix and tried that? the only thing that fixed it for me.
Strange. Kies works fine on my both computers: Win7 x64 and WinXP. Had some issues before, but new Kies works without any issues.
hello all,
i got the gt-i9000 like 2 months back the kies s/w was workin fine for the first few days now the app itself fails to lauch even if the fone is not connected.
I have uninstalled and reinstalled kies s/w like a million times.
The installation is always successful but when i click on the kies icon to start the program nuthin happens :s
Please help.
Oh yeah i am running Win7 32bit legit.
BronzedDroid said:
Eh, really, problems on Win 7 32bit? Haha that's so strange because it works almost flawlessly on Windows 7 64bit. Perhaps the first time there's better support for 64bit than 32bit.
Click to expand...
Click to collapse
Works fine for W7 32bit flawlessly to. Also for me on 2.2 it works under launcher pro as well, added bonus of not having to use home switcher (or the like) every time I connect the phone
rocketpaul said:
well the mtp driver doesnt install on my 64 bit computer.
Click to expand...
Click to collapse
It works fine on my copy of Windows 7 64bit, but I have to switch to touchwiz, and go to driver recovery in the kies menu.
I use XP at home and at work.
From home with JP6 and Kies 1.5.3.10093_82 I can connect fine using a cheap USB cable and with phone having Samsung Kies as default running LauncherPro.
At work Kies cannot connect to the phone... it just says connecting, please wait.... all the time, its wierd...
I guess I have to remove all the USB hubs on the work computer.... Will install Windows 7 Pro 64 bit at work soon so... maybe ill just wait until then...
Kies not working with LauncherPro. You have to create a shortcut to MTP Application, when you connected the phone and selected Kies need to start with this shortcut.
This is the only way to connect Kies with LauncherPro.
Somewhere I read about this, LaucherPro not recognised like TW.
Hope this helps.
The only way I have ever ever gotten kies was following these steps:
1. Completely close kies
2. Connect your phone
3. Open up device manager, find I9000 (should be under portable devices), right-click and disable (if device manager lags after you click disable then unplug the phone)
4. Replugin the phone and wait for it to say connected on the phone's screen
5. Re-enable I9000 in device manager
6. Fire up Kies and it should connect
These steps have worked every time for me
ps: I'm on Windows 7 x64
http://arvindgaba.com/computer/sams...o-install-for-samsung-galaxy-s-kies-resolved/
Not tested but seems to be approved
I'm on linux so i never used kies. Jusi odin all the way and i have nothing to complain about
This issue has become rediculous. Samsung fail so much with this usb ****. I run Win 7 32 bit and kies previously worked and even when it occassionally wouldn't I used odin.
Now unfortunately the phone just isn't recognised even after various driver and spftware reinstallations and registry deletions etc... etc... etc....
I have win8 professional, this does not come with Media center which supports MTP devices out of the box.
So after fresh install, My phone is not recignized by the computer anymore.
Installed drivers numerous times etc.
no go.
My laptop has Win8 premium edition which has media center.
phone connects and shows up as MTP no problem.
I will try installing SDK and see that would make any changes
update: installed samsung drivers and now it's working.
leegoon84 said:
I have win8 professional, this does not come with Media center which supports MTP devices out of the box.
So after fresh install, My phone is not recignized by the computer anymore.
Installed drivers numerous times etc.
no go.
My laptop has Win8 premium edition which has media center.
phone connects and shows up as MTP no problem.
I will try installing SDK and see that would make any changes
update: installed samsung drivers and now it's working.
Click to expand...
Click to collapse
i cant get mine to recognize either even after installing and re installing the drivers!!
I'm on a fresh install of Windows 8.1
Here's what I did.
1. Installed HTC Sync Manager
2. Installed Minimal ADB and Fastboot
3. ADB works fine, boot into bootloader.
4. Windows shows Unknown USB Device (Device Failed Enumeration) in Device Manager
Running fastboot devices returns nothing
I can connect my phone to view files, I can ADB on my phone, the only thing I cannot do is fastboot. Why is this happening and how can I fix it?
kinglime said:
I'm on a fresh install of Windows 8.1
Here's what I did.
1. Installed HTC Sync Manager
2. Installed Minimal ADB and Fastboot
3. ADB works fine, boot into bootloader.
4. Windows shows Unknown USB Device (Device Failed Enumeration) in Device Manager
Running fastboot devices returns nothing
I can connect my phone to view files, I can ADB on my phone, the only thing I cannot do is fastboot. Why is this happening and how can I fix it?
Click to expand...
Click to collapse
I just experienced the exact same issue following the same steps on my laptop also running 8.1
Fastboot doesn't work w 8.1. No workaround. You need another OS.
Sent from my HTC6500LVW using xda app-developers app
gzbrambila said:
Fastboot doesn't work w 8.1. No workaround. You need another OS.
Sent from my HTC6500LVW using xda app-developers app
Click to expand...
Click to collapse
Uh no. I have it working perfectly fine on my Surface Pro. It has both USB 3.0 and Windows 8.1. I'm not sure exactly how I got it to work but its possible.
megaorange1 said:
Uh no. I have it working perfectly fine on my Surface Pro. It has both USB 3.0 and Windows 8.1. I'm not sure exactly how I got it to work but its possible.
Click to expand...
Click to collapse
From all of my research, you're the first person I've heard of having it working. Any specific drivers used? I'm very curious (currently, I have to use a backup machine to push TWRP updates to my VZW One)
Same thing here. 8.1 broke fastboot. Is this a Microsoft problem specifically because if it is I seriously doubt they will be in a hurry to patch it.
Sent from my HTC One using Tapatalk
I have found out something based on the VMware experience. Can somebody try it out and report back???
I feel that the fastboot problem in windows 8.1 is related to the USB port.
For those people that having problem, are you guys using USB 2.0??? If yes do you have USB 3.0 port in your computer??? The real problem maybe is that fastboot only works with USB 3.0 but not USB 2.0 in windows 8.1...
I tried both USB types, and half a dozen drivers and workarounds, and nothing.
I don't believe the dude above got it working. He is probably thinking Win 8, not 8.1. I have it working on 8.
Flash Image GUI will probably do everything you need to do in fastboot without the need for a computer. I just threw 8.1 on one of my extra PC's, I'll see if I can get the drivers going. I feel like this was answered in another thread though, I think it is in the rumrunner thread...
Just another reason why 8 is bad
cgskook said:
Just another reason why 8 is bad
Click to expand...
Click to collapse
fastboot was working on windows 8 and adb !!!
so the update win 8.1 have change sometihng but the question is what
and i try different drivers (from google,intelandroiddrv) and noting work
why have micro change something with drivers pffffff
kaverorzi said:
yep,definitely not working on Win8.1x64
Rooted a couple weeks ago on Win8x64, no issues.
Only noticed this issue today after I couldn't flash a different splash screen for my NuSenseOne.
Click to expand...
Click to collapse
I don't have the link on hand but there is a driver update to support 8.1 I have it working fine.
Sent from my HTC6500LVW using Tapatalk
i just used http://www.droid-now.com/2013/10/fix-working-fastboot-drivers-windows-8-1-x64/ and fastboot works on a 3.0 port on 8.1
I've just had this problem last week, and now got a solution...
Hi guys,
For anyone interested, due to something DreamerTKM said - I tried both USB 2 & USB 3 sockets on my Dell L701X laptop and both failed:
ERROR: Unknown USB Device (Device Failed Enumeration)
I did a clean install of Win 8.1 Pro and it still failed...
Anyway, I was using Windows 8.1 Pro default drivers for my system when this issue came up last week - default as in Microsoft's own out of the box drivers (drivers on the install DVD and Windows Updates) for my CPU chipset, USB chipset, etc... - my entire system (except for my nVidia graphic card!)
My laptop is now a few years old and my official "Dell" CPU chipset drivers are not compatible with Win 8.1, so I need to rely on Microsoft for these, but my USB 3 originally had Dell supplied "Renesas USB 3" drivers which I hadn't installed or even thought about installing as my USB 3 socket worked - and worked well...
...anyway, after installing the original Renesas USB 3 drivers the fastboot commands work once plugged into a USB 3 socket! USB 2 still wouldn't work though, but now my Win 8.1 laptop can do fastboot commands through a USB 3 socket.
I understand not everyone will have a Dell L701X laptop but the moral here is before blaming Microsoft and their Windows 8.1 O/S (which is truly awesome), try installing the correct drivers first!
DreamerTKM - thank you for putting me on the correct path with this!
Hopefully this post may help some of you!
solution
guyz if u r working on win8.1 just plug it in ur usb 3.0 then it will wrk...if u put in usb 2.0 it wont!
No changes. I have read a few topics that it barely works with Win 8.1, so I will have to try it somewhere esle with Windows 7, then I'll be coming back to tell what's up.
wex28 said:
No changes. I have read a few topics that it barely works with Win 8.1, so I will have to try it somewhere esle with Windows 7, then I'll be coming back to tell what's up.
Click to expand...
Click to collapse
Full fastboot and ADB support is available in windows 8.
Watch the first video: http://forum.xda-developers.com/showthread.php?t=2703585
I have been using fastboot and adb with no problems on Windows 8.1 since January. But the issue is much more than simply using a different USB port. Here is the tutorial I used. http://www.droid-now.com/2013/10/fix-working-fastboot-drivers-windows-8-1-x64/ Certain security features of 8.1 need to be bypassed to install the modified drivers. Also see this guide: http://forums.team-nocturnal.com/index.php/topic/1362-how-to-adb-fastboot-in-windows-xp-7-81/ I used this just for ADB, but it looks like he's updated his guide for fastboot as well. Hope this information helps.
morrowa2 said:
I have been using fastboot and adb with no problems on Windows 8.1 since January. But the issue is much more than simply using a different USB port. Here is the tutorial I used. http://www.droid-now.com/2013/10/fix-working-fastboot-drivers-windows-8-1-x64/ Certain security features of 8.1 need to be bypassed to install the modified drivers. Also see this guide: http://forums.team-nocturnal.com/index.php/topic/1362-how-to-adb-fastboot-in-windows-xp-7-81/ I used this just for ADB, but it looks like he's updated his guide for fastboot as well. Hope this information helps.
Click to expand...
Click to collapse
Also, there is this: http://forum.xda-developers.com/showthread.php?t=2703585
I've been trying to play with some of the ROM's of Pokemon games recently and i've been using the Pokemon ROM editor to edit the games ROM's. This was before i rooted my nexus 7. Be aware that I haven't flashed any other ROM's or played with any kernels or device mechanics yet and the device was still connecting as MTP before I had rooted and for a while after i had rooted. I can connect it as PTP, but that's not useful when you need to take the whole .nds file for a game off your device. I'm not quite sure what's causing it, but I can tell you what i've already tried so far.
I've reinstalled the ADB drivers and every single part of my Nexus 7 from both PC's that I plugged it into, then enabled MTP and reconnected them, but Windows gives me a driver not found error and so ends the driver solution. I've connected it to more than one PC, one of which had not had the device connected to it ever before, yet it still it didn't appear. (Both PCs are running windows 7), so that means it's either Windows 7 doesn't like Google and wants to screw them by not showing their devices (which is unlikely) or the nexus 7 is just being derpy (which is likely). I've tried different cables, but i assume the cable is alright seeing as it can charge and connect as PTP.
I'm not really sure where else to go from here and i kinda need to edit that ROM soon as my Electabuzz needs to evolve and I need to change his evolution conditions so he evolves at level 56 instead of by trade. There's a random piece of info for you. Also, if i get any solutions that require software downloads, please link to the software or files. I'm pretty new to android tinkering and I don't know all of the terms yet.
EDIT: I don't understand this anymore. At first, PTP was working, now i tried it on a laptop, It didn't work, then i tried it on the PC again and now both PTP and MTP are suddenly working again...
Why does android continue to just fix itself automatically? This is the third time!
SassMaster said:
EDIT: I don't understand this anymore. At first, PTP was working, now i tried it on a laptop, It didn't work, then i tried it on the PC again and now both PTP and MTP are suddenly working again...
Why does android continue to just fix itself automatically? This is the third time!
Click to expand...
Click to collapse
Sounds to me like you have a driver or cable/usb port issue. One of these two links might be useful. Installing a USB driver and [FIX] MTP with USB debugging. Sometimes you might need to go into the device manager and uninstall the driver AND driver software then do a fresh install of the driver. You might want to do a reboot of the computer after uninstalling the driver. I've been lucky and never had problems but my brother had problems and we basically just had to uninstall and reinstall the driver.
SassMaster said:
Why does android continue to just fix itself automatically? This is the third time!
Click to expand...
Click to collapse
To add to what was said above you will need to disables driver security enforcement in order to install the drivers. This will put your computer in test mode and allow you to install non signed drivers. You will also need to manually install the drivers in device manager. I assume you already tried settings > storage > click three dots in the upper right hand side of the screen > click USB connection > select MTP.
Sent from my Nexus 7 Flo running CM 11 4.4.2 with ElementalX Kernel using XDA Premium 4 mobile app
LinearEquation said:
To add to what was said above you will need to disables driver security enforcement in order to install the drivers. This will put your computer in test mode and allow you to install non signed drivers. You will also need to manually install the drivers in device manager. I assume you already tried settings > storage > click three dots in the upper right hand side of the screen > click USB connection > select MTP.
Sent from my Nexus 7 Flo running CM 11 4.4.2 with ElementalX Kernel using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Absolutely right! I also forgot to mention that I have my Windows 7 desktop and laptop both set to Not automatically install drivers which I think makes it easier, at least for me.
You're all wrong! MTP is one big witchery!! It has a mind of its own! It's going to work when you don't need and expect it! It's going to fail when you need and expect it! MTP comes from Microsoft, the house of dark witchcraft and wizardry that gave birth to ugly and sad things like Kin and its misscarried brother Kin 2, Windows Vista and a cursed, evil, dark and lonely soul called Zune! The legend and tales of Gates tell that on Judgement Day, Zune will enslave his very own strain just to take revenge on humanity! Fear the day of revenge! Fear the day of Zune!...
Hi friends, I follow you every day and I love you!
I have a very big problem with my Note 10.1 2014 edition, that I can't solve. When I connect it to the computer (I tried 5 computers with different windows versions) it only charge the battery, but it's not recognised by kies or Odin. In Windows 8.1 it is shown as "unrecognised usb driver", in windows 7 too and it isn't seen at all in windows xp. I tried reinstalling kies, factory reset the tab, but without success. What can I do? I'm thinking about sending it in assistance.
Thank you and excuse me for my bad English!
Rick080194 said:
Hi friends, I follow you every day and I love you!
I have a very big problem with my Note 10.1 2014 edition, that I can't solve. When I connect it to the computer (I tried 5 computers with different windows versions) it only charge the battery, but it's not recognised by kies or Odin. In Windows 8.1 it is shown as "unrecognised usb driver", in windows 7 too and it isn't seen at all in windows xp. I tried reinstalling kies, factory reset the tab, but without success. What can I do? I'm thinking about sending it in assistance.
Thank you and excuse me for my bad English!
Click to expand...
Click to collapse
When you plug in the tablet does it ask you (on the tablet screen) if you want to connect as a media device or charge only? Check your developer settings that you don't have debug mode set.
No, it doesnt ask anything...
Rick080194 said:
No, it doesnt ask anything...
Click to expand...
Click to collapse
Have you confirmed that you are NOT in USB debug mode?
Also make sure drivers are installed on computer. Sometimes it can take a few minutes to install drivers. When I first put mine on computer at work I had to manually install driver's.
mikep2323 said:
Also make sure drivers are installed on computer. Sometimes it can take a few minutes to install drivers. When I first put mine on computer at work I had to manually install driver's.
Click to expand...
Click to collapse
Yes, i reinstalled drivers through kies application, but nothing
I have the same issue. I have been searching for a fix. I want to root but PC will not recognize it or pop up with anything, tablet only charges nothing else up on tablet. I have search and searched but nothing. I am also running windows 8.1.
*****
I have now tried a 2nd PC using all USB plugs. Installed Kies nothing, uninstalled and installed only driver still nothing. Clicked version 6 times on build number to get Developer options. I enabled USB debugging.
I am starting to get upset, I just want to Root for a few functions. It shouldn't be this difficult.
Anyone have any thoughts? It could be a simple thing we are over looking.
Change cable
Also try rebooting your PC .
My laptop stops finding USB devices after about 2 weeks.
Solved
I solved selling the tablet for 430$!
For those who are still having the problem, this solution worked for me on Windows 7.
I installed the first "Download" Link from here.
http://forum.xda-developers.com/showthread.php?t=961956