Develop Bugs

Epic 4g Not recognized on Windows 7 64 bit

I'm from the Evo 4G section of xda and just bought an Epic 4G from a friend to play around with. I've rooted and fully customized my Evo 4G and my uncle's Samsung Infuse. So I am not new to the rooting side of these phones. However, I just can't seem to get this to work no matter how hard I try.
Ok so I have done Google searches and sifted through the various "fixes" here on xda....I cannot, no matter what I do, get my epic 4g to be recognized on my Windows 7 64 bit.
I've downloaded and installed about 3 or 4 different USB driver files. I've gone through 2 different cables. I've uninstalled and even updated drivers via Windows. And I've installed and updated Kies. I bought the phone from a friend of mine who had done a full system restore before he gave it to me. So if there were any system issues they should be gone. When I plug in one of the cables the phone shows that the USB cable is connected and I have USB debugging on. But my computer shows "Uknown Device." Does anyone have any suggestions for me please?
I've included screenshots of what my computer shows me. Any help, or reference literature that I may have overlooked, that you guys can provide would be extremely helpful.

There's a few reasons this could be happening. You may want to try different USB ports on your computer or connecting through a USB hub. Also, make sure you're using the official Samsung drivers (you can search for them on XDA).
Otherwise, go to the dialer on the phone and punch in ##8778# and under USB make sure PDA is checked instead of modem. Hope that helps.

I too could never get win7x64 to work but had no problem on other pc running win7x86. I wasted hours trying. Uninstalled everything, removed all references in registry, used usbdevview, device manager, different usb ports, win update, and on and on and on. Gave up since I had other computer and it just worked 1st try. Please pm me if u find the solution. Would still like it to work on 64 bit. My thought is the 64 bit driver, but I hear others are working. :-O
Sent from my SPH-D700 using XDA App

BillyBob3 said:
I too could never get win7x64 to work but had no problem on other pc running win7x86. I wasted hours trying. Uninstalled everything, removed all references in registry, used usbdevview, device manager, different usb ports, win update, and on and on and on. Gave up since I had other computer and it just worked 1st try. Please pm me if u find the solution. Would still like it to work on 64 bit. My thought is the 64 bit driver, but I hear others are working. :-O
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
Mine works fine on my 64bit Laptop. I had to update drivers once though since going to GB leak broke it. On my desktop it will only work if connected in the rear USB port.
Sent from my SPH-D700 using XDA App

I've used atleast 3 different computers with 64 bit windows 7, I never did anything special except for download the drivers from samsungs website...

I don't know what it is because I couldn't get the computer to recognize my phone on my uncle's laptop (which runs Vista 32). It kept giving me the same "Unknown Device" message when I went to look at the drivers.

Concordium said:
I don't know what it is because I couldn't get the computer to recognize my phone on my uncle's laptop (which runs Vista 32). It kept giving me the same "Unknown Device" message when I went to look at the drivers.
Click to expand...
Click to collapse
Where it says unknown device double click on that then go to update driver then browse to location of unzipped samsung drivers.
Sent from my SPH-D700 using xda premium

Welcome to the Epic 4g xda section! It just so happens I was looking for Windows 7 64-bit drivers earlier today.
Here's where I found them: http://forum.xda-developers.com/showthread.php?t=798067
Then scroll down to the section "2.3 – ROOTING" and you'll find the listed drivers there.

jdawg101 said:
Welcome to the Epic 4g xda section! It just so happens I was looking for Windows 7 64-bit drivers earlier today.
Here's where I found them: http://forum.xda-developers.com/showthread.php?t=798067
Then scroll down to the section "2.3 – ROOTING" and you'll find the listed drivers there.
Click to expand...
Click to collapse
That post and those drivers are old...
Go here and get the drivers from Samsung:
http://www.samsung.com/us/support/downloads/SPH-D700ZKASPR
AFAIK, that package should install the correct drivers for the OS.
GL
=]

I install 32 and 64 bit drivers for the i9000
Sent from my SPH-D700 using Tapatalk

I have literally the same problem, phone was reconized and connected fine when i was running xp 32 bit, installed windows 7 64 bit and nothing i do will work. Was your problem ever resolved?

All i can say is try extracting the drivers thru 7zip
then extract the files it gives you
then u should see like a folder and then copy and paste the
folder in the c: program files
and then go back to device manager and then actually manaually search for
drivers and that should work cuz it worked for me im using Windows 8

unfortunately that is one of the exact ways I tried to do it, thanks for the input tho. Just incase I over looked something searching for the driver manually, what sub category should my phone be under in device manager? thx

For those having trouble getting the drivers installed in Win7(x64/x86).
A workaround could be to use WUBI (Ubuntu's windows based installer that adds an option to boot to Ubuntu, while allowing it [Ubuntu] to be uninstalled from windows like a "normal" program).
Install WUBI, boot to Ubuntu, problem solved!
If the point of installing the drivers it to get Odin working...
The WUBI workaround would still work, you would just replace Odin with Heimdall (which is 100x better/more stable than Odin anyway).
I realise this is a lot to do for resolving a driver install problem, but... Heimdall pwns Odin anyway.
GL
;]

apugslovesxda said:
unfortunately that is one of the exact ways I tried to do it, thanks for the input tho. Just incase I over looked something searching for the driver manually, what sub category should my phone be under in device manager? thx
Click to expand...
Click to collapse
It will show up under USB.
Sent from my SAMSUNG-SGH-I717 using xda premium

kennyglass123 said:
It will show up under USB.
Sent from my SAMSUNG-SGH-I717 using xda premium
Click to expand...
Click to collapse
and if your in download mode when you hook your phone up
it will show up under modem it wil not show until you connect your phone

Ok I had to do the following inorder for it to work on my windows 7 x64 bit
I download the samsung epic 4g driver samsung_mobile_driver_v1.3.800.0.msi
I then used 7zip to extract the file
I then used the msi file and installed it
I then used 7 zip and extracted the samsung_mobile_driver_v1.3.800.0.msi file to a directory
I then DISABLE ALL INTERNET ACCESS ON THE LAPTOP BY TURNING OFF WIFI AND OR PULLING THE LAN CABLE OUT THE PC.
I then plug the phone into the pc usb slot
let the pc find the drivers
if it does not find them point to the extracted directory you did above and it will be good.
now do ##8778# and place the bottom into pda and if it cant find drivers point it to the extracted directory.
now turn phone off and go into download mode 1 key and power button and let windows find the drivers

jmuru said:
There's a few reasons this could be happening. You may want to try different USB ports on your computer or connecting through a USB hub. Also, make sure you're using the official Samsung drivers (you can search for them on XDA).
Otherwise, go to the dialer on the phone and punch in ##8778# and under USB make sure PDA is checked instead of modem. Hope that helps.
Click to expand...
Click to collapse
Oh... my... god. I spent hours today trying to figure out how to get this phone I picked up to show me its sd card as a drive. Everyone on the internet seemed to be saying it was the lack of the right drivers, though they all disagreed on what the right drivers were. I tried so many different drivers, no luck.
That above, that I quoted: all it took. Why would it possibly be misconfigured out of the box in such a weird, impossible-to-locate way? Jeez.
(Anyway, I know I'm bumping a super old thread with this first post, but I felt compelled not just to thank this person for restoring my sanity, but also to bump up this thread's relevance for future googlers going as crazy as I was going.)

Win7 64bit pc does not Recognize A100 tab

I have previously have installed drivers for 3 android devices and never had a problem except now. Neither my pc or my laptop (both win7 64bit) can recognize it. I've tried changing ports (could not change cables because I do not have an extra micro usb cable), I have installed and uninstalled several times on both computers. I've even tried to see if it ewas a compatibility issue with the 64 bit sytem but when I went into setup.exe properties there was not a compatibility tab. I bought this refurbished from Walmart so Acer no longer covers it under warranty. I did buy a 2 year extended warranty that I can use as a last resort.
Is the micro usb cable suppose to seat flat against the body of the Acer a100 or can you see a portion of the metal part of the plug? Also, should I be able to wiggle the usb plug back and forth. Any assistance with this would certainly make my day. I have been working with this for 2 days now.

I'm assuming you installed the driver downloaded from Acer? My laptop is also 64-bit and it recognizes just fine after installing the driver. Yes, you can still see some metal part of the usb plug and it does wiggle, at least it does on mine.
Sent from my Nexus S using xda premium

[email protected] said:
I'm assuming you installed the driver downloaded from Acer? My laptop is also 64-bit and it recognizes just fine after installing the driver. Yes, you can still see some metal part of the usb plug and it does wiggle, at least it does on mine.
Sent from my Nexus S using xda premium
Click to expand...
Click to collapse
Yes, I did download from Acer. I finally went back and reviewed the paper work that came with Tab and found that the company that refurbished for Walmart has a 90 day warranty. I have emailed there warranty support service, hopefully I will hear something from them tomorrow. The only thing I have not tried is a different usb cable which I will pick up tomorrow at good old Radio Shack. If that does not fix the problem then the problem must be in the Tab. I have installed drivers for 3 other android device on the same pc's and never had a problem. Tomorrow is going to be a busy day for me. Dealing with this issue, going to the dentist and I am suppose to get the new Vizio Co-Star so I will be setting that up and then learning how to operate it and seeing what its potential is.

[email protected] said:
I'm assuming you installed the driver downloaded from Acer? My laptop is also 64-bit and it recognizes just fine after installing the driver. Yes, you can still see some metal part of the usb plug and it does wiggle, at least it does on mine.
Sent from my Nexus S using xda premium
Click to expand...
Click to collapse
Would it be possible to install clockworkmod and root and install the rom over wifi? I not sure how to do it but, I am sure there is someone that has done this before.

lartomar2002 said:
Would it be possible to install clockworkmod and root and install the rom over wifi? I not sure how to do it but, I am sure there is someone that has done this before.
Click to expand...
Click to collapse
Only if you have adb over network, which stock doesn't have, so no you can't do that, has to be USB.
Tapatalked from my Galaxy S II.

pio_masaki said:
Only if you have adb over network, which stock doesn't have, so no you can't do that, has to be USB.
Tapatalked from my Galaxy S II.
Click to expand...
Click to collapse
Da*n, Oh well, back to the drawing board.

lartomar2002 said:
I have previously have installed drivers for 3 android devices and never had a problem except now. Neither my pc or my laptop (both win7 64bit) can recognize it. I've tried changing ports (could not change cables because I do not have an extra micro usb cable), I have installed and uninstalled several times on both computers. I've even tried to see if it ewas a compatibility issue with the 64 bit sytem but when I went into setup.exe properties there was not a compatibility tab. I bought this refurbished from Walmart so Acer no longer covers it under warranty. I did buy a 2 year extended warranty that I can use as a last resort.
Is the micro usb cable suppose to seat flat against the body of the Acer a100 or can you see a portion of the metal part of the plug? Also, should I be able to wiggle the usb plug back and forth. Any assistance with this would certainly make my day. I have been working with this for 2 days now.
Click to expand...
Click to collapse
I also have this problem with two Computers,Windows 7 64 Bit and Windows 8 Consumers Preview 64 Bit. Many Hours Lost trying but still unable to find a fix. It has to be a Security Issue possibly with an Exploit in the USB Driver Software. My Resolution was to Break Out the Old Trusty Dell XP Laptop. Copy and Pasted the Same Downloaded Files to a USB Drive and used them on the XP Laptop and in Less then 5 Minutes Successful Root !

Izzyb914 said:
I also have this problem with two Computers,Windows 7 64 Bit and Windows 8 Consumers Preview 64 Bit. Many Hours Lost trying but still unable to find a fix. It has to be a Security Issue possibly with an Exploit in the USB Driver Software. My Resolution was to Break Out the Old Trusty Dell XP Laptop. Copy and Pasted the Same Downloaded Files to a USB Drive and used them on the XP Laptop and in Less then 5 Minutes Successful Root !
Click to expand...
Click to collapse
I was at Radio Shack and bought a cable for $20.00, what a rip-off I could have gotten the same cable for $4.95 from Monoprice. Anyways that was the problem and now the pc sees the device.

You can download an Ubuntu Live CD for free, and boot from it without needing to reformat / repartition your hard disk. In other words you don't need to install it, just reboot run the commands you need, take the disc out, boot back to windows and done.
I put together this package that simply includes adb and fastboot, it will install them automatically and allow you to run them with ease.
Download here:
android-cmdline-tools.zip
Instructions:
Boot into your Live Ubuntu CD (or other distro)
Download the above package
Open your terminal emulator (i.e. Gnome Terminal, Konsole, Terminator, etc) do the following:
Code:
cd /tmp && unzip ~/Downloads/android_cmdline_tools.zip
*If you downloaded to a different location you need to correct the path, I used ~/Downloads as it is the typical download location on linux for Chrome and Firefox.
After the file is unzipped you should have the android-cmdline-tools directory in /tmp/android-cmdline-tools
Now lets install adb and fastboot:
Code:
cd android-cmdline-tools && sudo bash ./install-linux.sh
(may request your password if you are on a live cd then it shouldn't, however if it does leave it blank, otherwise you should type your users password)
This will prompt you to make sure you wish to install. Enter Y to install, any other key to abort
If this succeeds, you will now have adb and fastboot ready to run on your device
On linux you shouldn't need any special drivers for these tools to work with the A100 so this package is a small convenient download that is quick to install and use the tools, and should come in handy for usage via Live CD/DVD to access your A100 or most other android devices through adb/fastboot
Good luck and hope this helps!

linuxsociety said:
One quick solution would be to grab an Ubuntu Live CD download and reboot your computer into the Live installation, download the adb and fastboot files for linux. You usually can get them in packages aimed at flashing recovery so you don't have to download the entire Android SDK. Ubuntu shouldn't have a problem seeing your A100 without the need for any drivers or modifying any .ini files. This is an alternative, so that you don't have to wipe your Win7 install. just keep a Live CD for linux laying around, they usually come in handy!!
Actually now that I am thinking of it I'll just make a package named A100-cmdline-tools.zip that contains both adb and fastboot for both windows and linux. Maybe it will come in handy for some of you guys
Click to expand...
Click to collapse
Bought another micro usb cable and that fixed the problem. But I am going to use your suggestion and burn a Live CD to have around. Thanks

lartomar2002 said:
Bought another micro usb cable and that fixed the problem. But I am going to use your suggestion and burn a Live CD to have around. Thanks
Click to expand...
Click to collapse
edited that post, made a Linux android-cmdline-tools.zip package that includes both adb and fastboot and will install them for you. May be a handy .zip file to keep laying around for your PC, small size and easy for a quick download too if your on Live CD. I also have the Windows adb.exe and fastboot.exe files as well as the required .dll's in the zip, I just haven't made an installer for windows (yet - will be install-windows.sh) .

linuxsociety said:
edited that post, made a Linux android-cmdline-tools.zip package that includes both adb and fastboot and will install them for you. May be a handy .zip file to keep laying around for your PC, small size and easy for a quick download too if your on Live CD. I also have the Windows adb.exe and fastboot.exe files as well as the required .dll's in the zip, I just haven't made an installer for windows (yet - will be install-windows.sh) .
Click to expand...
Click to collapse
Where do I d/l from?

lartomar2002 said:
Where do I d/l from?
Click to expand...
Click to collapse
where it says download here, and then provides the link or I'll just provide it in this msg too: http://beta.androidfilehost.com/?fid=9390062577138008179

linuxsociety said:
where it says download here, and then provides the link or I'll just provide it in this msg too: http://beta.androidfilehost.com/?fid=9390062577138008179
Click to expand...
Click to collapse
Duh! Sometimes I can be so dense.

Windows 8.1 Fastboot

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

[Q] Nexus 7 not recognized as MTP on Win7

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!...

Windows 10: Unknown USB Device (Device Descriptor Request Failed)

Hi everyone!
I'm trying to get my Nexus 7 2013 to work with Windows 10.
However, when I plug it in I get an error saying that the device is not recognized. It doesn't even show up properly at Device Manager.
I can not update or change the driver. It's driving me kind of insane. There's no OS on my tablet so I need a direct USB connection to send files.
Has anyone worked out a fix for this issue?

Nexus device drivers for windows 10
Did you download the google device drivers for Nexus devices? Just do a search for Nexus Device Drivers in your search engine.
Is your bootloader unlocked and do you have a custom rom installed? This will allow you to accomplish both tasks with a single click. http://forum.xda-developers.com/showthread.php?t=1766475
Hope this helps.
Do not forget to give thanks if it works.
gn
ev1lchris said:
Hi everyone!
I'm trying to get my Nexus 7 2013 to work with Windows 10.
However, when I plug it in I get an error saying that the device is not recognized. It doesn't even show up properly at Device Manager.
I can not update or change the driver. It's driving me kind of insane. There's no OS on my tablet so I need a direct USB connection to send files.
Has anyone worked out a fix for this issue?
Click to expand...
Click to collapse

georgenazar said:
Did you download the google device drivers for Nexus devices? Just do a search for Nexus Device Drivers in your search engine.
Is your bootloader unlocked and do you have a custom rom installed? This will allow you to accomplish both tasks with a single click. http://forum.xda-developers.com/showthread.php?t=1766475
Hope this helps.
Do not forget to give thanks if it works.
gn
Click to expand...
Click to collapse
Yes, I did. I also downloaded them from Skipsofts Toolkit. For some reason Windows does not want to use them.
Sent from my P01M using Tapatalk

If u click on the link in my first reply it will take u to a different toolkit specifically for Nexus devices.
Are you using a USB 2 or USB 3 port? I used to have problems when I used a USB 3 port.
I know this is obvious but I thought I should mention it, did u uninstall the ADB drivers and re-install the google nexus drivers?
Good luck again.
gn
ev1lchris said:
Yes, I did. I also downloaded them from Skipsofts Toolkit. For some reason Windows does not want to use them.
Sent from my P01M using Tapatalk
Click to expand...
Click to collapse

Wugs Toolkit did not work.
I'm going to try a Windows 7 USB flash drive. Hopefully it's more of a Windows 10 driver thing than USB 3.0.

Windows 7 didn't work. Going to try Ubuntu Live USB.
This is really getting on my nerves.
Is there an adapter I can get that will change USB3 to USB2?

Tried the whole Linux thing. Didn't work. My Zenfone however works like a charm.
I give up.
Rest in Peace Nexus 7 2013

ev1lchris said:
I give up.
Click to expand...
Click to collapse
Hold on, "only the white light at the bottom turns on" - is it still the case?
If no, please post VID/PID descriptor from Device Manager in Windows or 'lsusb' in Linux.
If yes, no point of struggling with USB as it will be either:
VID_05C6&PID_9008
VID_0000&PID_0000
and there is nothing you can do with it anyway.
The white light at the bottom, in this context, usually indicates a faulty battery and no recharge can fix it. I remember that you posted a few times about decreased SOT, which eventually leads to completely dead battery. You can confirm it if you disconnect the charger, take the N7's back off and measure voltage between the battery plug's pin #1 and #6. If it is below 1V, then there is no doubt the battery is faulty. Some try to 'kick start' it but it is a waste of time, just replace it.

My battery is fine. It's new and holds a charge.
The problem is neither Windows or Linux want to recognize it to push files to it.
At least I can watch the pretty Google boot sequence.

Is it possible I damaged something when replacing the battery?

ev1lchris said:
Is it possible I damaged something when replacing the battery?
Click to expand...
Click to collapse
No.
While reading about this problem on three threads already I noticed that you only try to connect to TWRP on ADB/MTP, which may be damaged for some reason. Let's try a completely different USB connection protocol:
boot the Nexus in fastboot mode (when off press power+vol.dn)
connect it to your PC
on PC run: fastboot getvar all
You can run the fastboot app from Windows or Linux...
on Windows install NRT and run it from "C:\Program Files (x86)\WugFresh Development\Nexus Root Toolkit\data" folder
or run it without installation from live Linux
If you are successful in getting normal output from "fastboot getvar all", proceed to OS reflash.
If not, post USB VID/PID while in fastboot connection.

Thanks, I'll try this. However, Windows can not detect the Nexus 7 even when in the Bootloader.

ev1lchris said:
Thanks, I'll try this. However, Windows can not detect the Nexus 7 even when in the Bootloader.
Click to expand...
Click to collapse
No worries, but I still need the USB descriptor of a failed connection in fastboot/bootloader mode...
on Windows, run UsbTreeView and post 'File - Save full report'
on Linux post the output of 'lsusb'
Well, perhaps something isn't right after the battery replacement after all
The wide silver ribbon cable which goes across the battery, connects USB data lines from the daughterboard to motherboard and it might be partially disconnected. Please try to re-seat and re-lock it on both ends.
:highfive:

k23m said:
No worries, but I still need the USB descriptor of a failed connection in fastboot/bootloader mode...
on Windows, run UsbTreeView and post 'File - Save full report'
on Linux post the output of 'lsusb'
Well, perhaps something isn't right after the battery replacement after all
The wide silver ribbon cable which goes across the battery, connects USB data lines from the daughterboard to motherboard and it might be partially disconnected. Please try to re-seat and re-lock it on both ends.
:highfive:
Click to expand...
Click to collapse
I think I may have accidentally damaged the silver ribbon when installing the battery. Some of the ends are messed up.
As for the VID and PID I took a screenshot. I can still run USB tree.

ev1lchris said:
I think I may have accidentally damaged the silver ribbon when installing the battery. Some of the ends are messed up.
As for the VID and PID I took a screenshot. I can still run USB tree.
Click to expand...
Click to collapse
No need, I see VID_0000 which indicates a hardware issue. If the cable can not be fixed, here is another one, but please check this video before replacement.
Cheers
:good:

When taking out the cable the first time I think I damaged some of the connectors.
Should be an easy fix.

k23m said:
No need, I see VID_0000 which indicates a hardware issue. If the cable can not be fixed, here is another one, but please check this video before replacement.
Cheers
:good:
Click to expand...
Click to collapse
Good news: The cable is installed, the PC can detect the Nexus 7, the Stock seems to have installed successfully.
BAD NEWS: THE TOUCHSCREEN IS NOT WORKING
What is going on? I hope this is a software issue?

ev1lchris said:
Good news: The cable is installed, the PC can detect the Nexus 7, the Stock seems to have installed successfully.
BAD NEWS: THE TOUCHSCREEN IS NOT WORKING
What is going on? I hope this is a software issue?
Click to expand...
Click to collapse
Good and bad news
Run TWRP3 and check if touchscreen works there.
If not, I think we're not done with the cable yet as it also connects touch to the motherboard.

I've watched some YouTube. I've deciphered that the wide cable is data and the narrow one touchscreen.
I've tried unplugging and plugging both. No luck there. I notice the tablet heats up sometimes too.
When installing I noticed a small plume of smoke. I hope nothing happened.
When it boots into the OS there is a crossed out square on the upper right hand corner now.
Any suggestions?

I put in the cable I kind of damaged back into the Nexus 7. Now it gets detected and the touchscreen works. I have no clue what happened here but it seems fixed.
THANK YOU ALL VERY MUCH FOR YOUR HELP. Much appreciation and love to the XDA community!