Hi All,
I recently bought an xoom wifi model mz604 uk/eu spec with android 3.2 upon first boot/update. Took a while to connect to a pc running xp pro sp3... after reading many comments on the importance of enabling usb debugging, this bugger will only identify itself clearly (as a media device) with usb debugging off... I intend to root the device after a while due to the missing usb / udisk mount point within the stock file system.
In short, will the omission of debugging cause complications when flashing a revised rom, or will it be no problem after unlocking and reverting back to stock, pre flashing?
I have some experience with android 1.6 to 2.3, but this 3 to ics looks like a potential pain in the butt!
Cheers & Thanks for sharing any of your experiences on this,
Bob
Ps I will install windows 7 if there isn't a comfortable work around, I just like xp pro because it's lighter than the others...
I sorted it. After the vague motorola driver software completed its own background update, hrs later! why? I was able to manually choose the driver through show all devices / motorola. Now i get a different icon via my computer depending on whether usb debugging is on or off...
My friend busted the screen on her razr, and we were trying to get her photos off of it with my laptop, but windows explorer wont recognize any of the files on it. anybody know of some third party software that might help? Unfortunately, she wasnt using an sd card, so all the photos are on the phones internal storage. The phone is unrooted and my computer is running windows 7
Try turning usb debugging on.
Sent from my PACMAN MATRIX HD MAXX
For me personally MTP always worked better and more stable under Linux than under W7. Try downloading a ubuntu live cd (has to be ubuntu 13.04) and try connect to the phone with the live system. 13.04 supports MTP natively, so it should be as easy as plug & play.
Just a thought: have you installed the motorola sw with the drivers before trying to connect to the phone?
izzy spun said:
My friend busted the screen on her razr, and we were trying to get her photos off of it with my laptop, but windows explorer wont recognize any of the files on it. anybody know of some third party software that might help? Unfortunately, she wasnt using an sd card, so all the photos are on the phones internal storage. The phone is unrooted and my computer is running windows 7
Click to expand...
Click to collapse
maybe a silly question, but did she have the cloud sync turned on? They might be safe & sound & waiting for you.
Hello
:crying:
I got my N5 today, and like my wife's N7 and my N10, NONE of them will show up on windows explorer (windows 8.1)
I can unlock, root, install custom recovery, all good, but as far as actually SEEING my device on the computer so I can drag and drop stuff, well, I literally have been spending almost a day trying to sort that out and have not got any closer at all. It is really pathetic.
I've changed the windows Unsigned drivers thing (though the drivers must be ok if I can do all that other rooting etc)
But yet when I uninstall the drivers to try installing them again, win8 says "Android ADB Interface. The third party INF does not contain digital signature information"
But I'm pretty sure that when I reinstall them AGAIN, I will still nto be able to see any of my Nexus devices on Windows explorer... despite them showing up in the Windows Notification under USB, and they are mounted there... I can UNmount them!
Something is way off kilter here, its with 3/3 devices, perhaps win8.1 is completly Android unfriendly, or?
Advice/help MUCH appreciated for someone who is going nuts here.
tx
Mark.
Did you turn MTP off to install the drivers to make sure ADB is working correctly? If so, did you check it to turn it back on? I am having no issues with Windows 8.1.
Same in Windows 7, I can't see my mates N5 on my Windows 7 machine but it's fine on his (he got the generic drivers from Windows update whereas I had mine from the Google SDK so that might be something to do with it?...)
It's just hit-or-miss. It's not Windows 8.
My work computer got a fresh image about 2 months ago. I've plugged other Android devices in, but haven't plugged in a Nexus device (or one that utilizes MTP the same way). I plugged in the N5 when I got it, and it worked flawlessly. My gaming PC at home has the Android SDK installed and it worked perfectly there. My HTPC does not have the Android SDK installed and nothing shows up in My Computer at all.
It's a weird android thing.
Hello guys,
lowandbehold said:
Did you turn MTP off to install the drivers to make sure ADB is working correctly? If so, did you check it to turn it back on? I am having no issues with Windows 8.1.
Click to expand...
Click to collapse
I did turn it iff to ADB but do not see where I would turn it back on, but that may be it with my N5...
EddyOS said:
Same in Windows 7, I can't see my mates N5 on my Windows 7 machine but it's fine on his (he got the generic drivers from Windows update whereas I had mine from the Google SDK so that might be something to do with it?...)
Click to expand...
Click to collapse
I really dont know. I have 4 PC's in the house, and sometimes my old dell laptop (also 8.1) seems to be the most reliably connect-able.
hotleadsingerguy said:
It's just hit-or-miss. It's not Windows 8.
My work computer got a fresh image about 2 months ago. I've plugged other Android devices in, but haven't plugged in a Nexus device (or one that utilizes MTP the same way). I plugged in the N5 when I got it, and it worked flawlessly. My gaming PC at home has the Android SDK installed and it worked perfectly there. My HTPC does not have the Android SDK installed and nothing shows up in My Computer at all.
It's a weird android thing.
Click to expand...
Click to collapse
There has to be a physical reason for it (unless we are to consider the metaphysical - past lives, re-incarnation of gadgets, Steve Jobs curses and stuff...) and it does amaze me that it still seems so hit and miss. When I first got onto android a few years back, you just plugged your phone into USB, ANY ONE ON ANY COMPUTER and whammo, you'd get both Ext SD adn Int SD mounted... reliably. I'm sure that was causing security and stability issues so all manufacturers seem to have snuffed that out.
so that MTP toggle is at settings > Storage > settings in storage
but it makes no difference still not vis in WinExplorer
Cheers
Mark.
Settings/Storage then hit the advanced menu button on the top right to enter "USB computer connection" and make sure MTP is checked.
lowandbehold said:
Settings/Storage then hit the advanced menu button on the top right to enter "USB computer connection" and make sure MTP is checked.
Click to expand...
Click to collapse
Tx mate, yeah I tried but alas, makes no diffs...
Thanks, but sadly this is a really abysmal part of android... and used to be a major + of the platform.
Mark.
fredphoesh said:
Tx mate, yeah I tried but alas, makes no diffs...
Thanks, but sadly this is a really abysmal part of android... and used to be a major + of the platform.
Mark.
Click to expand...
Click to collapse
I had this problem extensively, when trying to Root my Nexus, I went through uninstalling and re-installing drivers repeatedly, it was obnoxious, but i did end up getting it to work, so don't necessarily give up. I am running Win 8.1 though, eventually i had to go through Wug's Root Kit, and into the advanced driver installation settings, and install the raw drivers. (By booting windows into disabling secure driver certs.) Once i did that it gave me significantly more access, also try toggling your camera one on, the PTM or something, and switching back and forth with MTP.
ZeroAlphawolf said:
I had this problem extensively, when trying to Root my Nexus, I went through uninstalling and re-installing drivers repeatedly, it was obnoxious, but i did end up getting it to work, so don't necessarily give up. I am running Win 8.1 though, eventually i had to go through Wug's Root Kit, and into the advanced driver installation settings, and install the raw drivers. (By booting windows into disabling secure driver certs.) Once i did that it gave me significantly more access, also try toggling your camera one on, the PTM or something, and switching back and forth with MTP.
Click to expand...
Click to collapse
I must say, I did leave that part out of my replies. I too installed the raw drivers using Wugs toolkit. Maybe that is the x-factor.
Enable USB debugging in developer options.
Sent from my Nexus 7 using Tapatalk
Nexus Root Toolkit includes a variety of USB drivers you can try, as well as a few utilities to help you diagnose and fix android driver problems. That's where I would start. You don't need to use it to root or anything (unless you want to) but the driver utilities in the toolkit have fixed a number of problems I've had with android drivers over the years. I currently have my nexus 5 / 7 / galaxy working fine on two computers with windows 8.1
Not really the same at all but I had a hard time getting my S3 to be recognized on my computer at work running XP.
In the end the problem was the generic USB drivers that were installed had to be manually removed; even the official Samsung drivers wouldn't overwrite them. After a bit of digging and prodding I got it to work.
My Nexus was recognized without issue on my Win 8 machine.
You'll have to try a variety of different drivers to get it to show up properly. My N4 and Note 3 had no issues showing up, but the N5 wouldn't. I had to uninstall all the old drivers and started with brand new Google drivers to get the N5 to show up. Now it's there.
This happens to me every single time with a new device so I know exactly what to do now. It's not a driver issue, it's a problem with windows 8 and how it searches for drivers.
If you have the Android SDK installed properly just open up device manager > right click on android device > Update driver software > browse my computer > Let me pick from a list of device drivers on my computer > select the google adb driver from here.
Another problem I had was remembering to accept the ADB on my phones end, I never had to do that with my HTC one, so when going through rooting the raw drivers were likely unnecessary, I just hadn't noticed the primly on my phone when the first drivers I installed worked.
Hello guys, thanks for the various responses...
ZeroAlphawolf said:
Wug's Root Kit, and into the advanced driver installation settings, and install the raw drivers
--------also try toggling your camera one on, the PTM or something, and switching back and forth with MTP.
Click to expand...
Click to collapse
lowandbehold said:
I too installed the raw drivers using Wugs toolkit. Maybe that is the x-factor.
Click to expand...
Click to collapse
I did initially install the raw drivers as they sounded like they would be best... will try the camera toggle and MTP toggle
rabidfurball said:
I currently have my nexus 5 / 7 / galaxy working fine on two computers with windows 8.1
Click to expand...
Click to collapse
Encouraging!!! I know from my SGS3 and 4 and some generic chinese tablets ive had that the driver installation can be a major PITA but eventually you do the same thing for the 5th time, and it works, with no (seemingly) logical reason.
Stories said:
I had to uninstall all the old drivers and started with brand new Google drivers to get the N5 to show up. Now it's there.
Click to expand...
Click to collapse
I did a fresh install of windows 8.1 just yesterday... so it was pretty clean!
KiNG OMaR said:
It's not a driver issue, it's a problem with windows 8 and how it searches for drivers. If you have the Android SDK installed properly just open up device manager > right click on android device > Update driver software > browse my computer > Let me pick from a list of device drivers on my computer > select the google adb driver from here.
Click to expand...
Click to collapse
Yeah, i have tried that and it says I have the best drivers already installed. Oddly I can use Nexus Root Toolkit fine, so there has to be something right about the drivers... just not the part that shows up on a computer.
I'm convinced there HAS to be some scientific way of doing this, its such a common problem, it would be great to really figure it out. The problem is, one has to try 100 things before it works, so it becomes almost impossible to know which actions to attribute as the solution!
tx again,
Mark.
a solution - possibly useful...
Hello guys
Following Wugfresh's instructions to the T...
I tried drivers Option 1, (Universal) and the result was exactly as with the Raw (Option 4) drivers... So I uninstalled the drivers, ran ran USBDeview and uninstalled 7 devices like "Google Nexus ADB Interface" and "USB Composite device" and "Nexus 10".
Then tried Option 2.
The installation did not go exactly according to Wugfresh visual guide, so I cant be certain, but I do know that installingPDANET drivers only work if you select MTP, otherwise it will not find the tablet/phone.
After the instalation, the app called PDANET installed on computer, not on my tablet. My PC showed a pop up notification when tablet USB debugging is turned on, but again, it was not visible in windows explorer.
I then was going to try Option 4 again, and Uninstalled drivers in device manager WHILE I STILL HAD THE TABLET STILL PLUGGED IN, so I am guessing though PDANET uninstalled, the drivers remained (which I think is what Wugfresh's process would have done if it had run according to plan. I ran USBDeview and uninstalled the same 7 devices.
Then
Plugged tablet back in to attempt Raw drivers, but all of a sudden, the device was recognised and for the first time visible fully in Internet Explorer!
So basically it seemed to be the PDANET drivers that worked, though I have no idea if that would have worked had I tried these drivers in the first place.
I hope that helps someone!
Cheers
Mark.
OP, are you running W8.1 64 bits or 32 bits ??
I had my Sony Viao running W8 64 bits & hated it, downgraded to W7 64 bits and it's very happy getting along with Nexus 7 - going to play with N5 later on. Good old Dell Latitude is running W7 32 bits and it's my main machine to unlock, root & flash and so far so good - yet, I was reading about someone running Vista and had issues with the usb drivers.
I have 2 fully licensed W8 safely tucked away and the way it's looking, I might never get out of W7 - let alone then upgrading to 8.1 for free - getting reminders from $S a few things already.
Most of the time, the mess are caused by conflicting drivers installed & loaded - I keep a clean & lean desktop to do these bench work, and even though it is a PITA, starting clean with minimal programs (and apps) installed is often a good start - turn off antivirus & firewall, especially if connectivity is not needed - enabled access only if it is required and/or necessary.
I've also noticed that on my Nexus 4 I can only access adb in PTP mode, doesn't work at all with MTP enabled.
Hello guys
Letitride said:
OP, are you running W8.1 64 bits or 32 bits ??
Most of the time, the mess are caused by conflicting drivers installed & loaded
Click to expand...
Click to collapse
64 on the two PC's in the same room, HTPC's and laptop are 32 I think, but I have not tried them. I did a fresh Win 8.1 install on Tuesday and had no drivers from any devices other than the ones I manually installed with Wug.
KiNG OMaR said:
I've also noticed that on my Nexus 4 I can only access adb in PTP mode, doesn't work at all with MTP enabled.
Click to expand...
Click to collapse
Yeah, well try the PDANET (worked for me, though was my last resort as I don't like to install stuff that is a/ meant for something else, b/has some software I dont need that comes with it... but I did manage to keep the drivers and UNinstall PDANET software by keeping the tablet plugged in when I uninstalled PDANET... try it.
tx
Mark.
Cant turn on usb debugging after system update even when its plugged into the pc it wont turn on.. i can still transfer files from phone to pc and pc to phone im not sure whats going on here. Theres no bug reports either and you cant verify apps over usb..
haro25 said:
Cant turn on usb debugging after system update even when its plugged into the pc it wont turn on.. i can still transfer files from phone to pc and pc to phone im not sure whats going on here. Theres no bug reports either and you cant verify apps over usb..
Click to expand...
Click to collapse
Do a factory reset ?
That didnt work it hasnt worked since day of the system update and that was on a fresh install of the rom before this one.. i think thats just how the system update is...
https://youtu.be/fqFvuZoFwF4
I made this video showing settings and dev settings in the boost mobile j7 after system update... kinda give people a better look at whats going on. I posted it to the public on Facebook so hopefully it gets out to the right people..
Heres a screen recorder that works without root..
https://play.google.com/store/apps/details?id=com.hecorat.screenrecorder.free
What Is USB Debugging Mode On Android? [MakeUseOf Explains]
Written by Joel Lee
January 11, 2013
Ads by Google
usb debuggingIf you use an Android phone and you’ve searched forums for solutions to problems, you’ve probably heard the term “USB Debugging” every once in a while. You may even have seen it while looking through your phone’s settings. It sounds like a high-tech option, but it really isn’t; it’s quite simple and useful.
One beauty of Android is that it has a lot of built-in features, many of which are advanced. If you want to supercharge your phone with mods and whatnot, you can; if you want to use it just as it was out of the box, you can ignore the advanced stuff. USB Debugging is a feature that all users can benefit from, though, so you should know what it does and when to use it.
What Is USB Debugging Mode?
USB Debugging Mode is a mode that can be enabled in Android after connecting the device directly to a computer with a USB cable. The primary function of this mode is to facilitate a connection between an Android device and a computer with Android SDK (software development kit). As the name might suggest, Android SDK is a software suite that’s designed to aid in the development of Android apps.
Ever wondered how a programmer creates apps on the Android? They definitely don’t code them straight on the phone device! That would be nightmarish at best. Instead, they utilize the environment of the Android SDK to code apps on a computer, use USB Debugging Mode to transfer those apps to a device for testing.
usb debugging
But, again, here’s the takeaway: USB Debugging Mode establishes a direct connection between an Android device and a computer and readies it for deeper-level actions. That’s the important part.
In some versions of Android, the USB Debugging Mode feature may be called Developer Mode. With such a name, it can be easy (and reasonable) to think that you’ll never need to deal with this aspect of Android if you never plan on developing anything. That’s not exactly true.
Why Is USB Debugging Mode Important?
USB Debugging grants you a level of access to your device. This level of access is important when you need system-level clearance, such as when coding a new app. However, there are a few non-development-related benefits from this new level of access that can give you much more freedom of control over your device.
For example, with Android SDK, you gain direct access to your phone through your computer and that allows you to do things you normally couldn’t, like snag instant screenshots of your device or run terminal commands with ADB. These terminal commands can help you restore a bricked phone–a useful tool for any adventurous Android owner. Without it, you’d have to get a replacement phone.
android usb debugging
USB Debugging is also necessary if you ever want to root your Android device. Before an app like One-Click Root can dig into your system and deliver the exploit that roots the device, USB Debugging is necessary to allow that function in the first place.
Yes, the original intention for USB Debugging Mode was only meant for developers who needed to copy data between their computers and Android devices, to install apps on the phone without notifications, and to read log data off the phone. But even if you aren’t a developer, you’ll probably run into a few apps that require USB Debugging Mode to function properly, so this mode does affect you and you should know about it.
Start searching dialer codes for Samsung devices and do be careful on what you do in those service menus.
-sent from this device using this app.
Just tried that and cant get any codes to work in the dialer or in the apps.. and one says im missing su so i dont know im about to just flash back to the older firmware Security is nice and all but damn they killed it.
I found the problem it was samsung knox if you activate it or use my knox app it disables your dev settings so i ripped knox out of my phone now i have usb debugging..
So. I have spent about an hour searching now, and cant seem to find anyone else who is having this problem (which seems peculiar to me...) but anyways, ive got my girlfriends stock, non-rooted big ol mama jama of a clone for the p8+ (or max, maybe?) and when i connect it to my microsoft surface 3 running windows 10, it doesn't recognize it AT ALL. I have usb debugging turned on the device, and on my computer i turned off the check for digitally signed drivers, I have the latest version of android studio installed, with adb, fastboot, the whole shebang, I have downloaded several drivers, up to (but not limited to)pdanet and the ultimate driver mtk kit that is usually found alongside the skipsoft anddroid toolkit. I cant seem to figurer this beyotch out, it will charge the device but literally nothing more. neither the device nor the computer can tell the other one exists.
any tips?
HiSuite installed?
NOPE! thank yoy kind sir, lets see whsat she does