• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root PC Can't interface with Tablet

DimBulb

Android Enthusiast
Dec 31, 2012
350
105
Minnesota
This is different from any other thread, because my Nexus 7 ... IS rooted, has been found and opened with the PC for 9 months or so.

The problem, is that I had a hard-drive failure. The C Drive died and so good old WinXP needed to be reinsatlled on a new 360 GB hard-drive.

That's all been set up. I was able to get the drivers to my rooted phone, pulled off the phone, so the phone, it's sdcard and all are accesable by PC, that part's good now.

I've been trying Wuggs, Nexus Root Tool, (repeatedly) and the ADB drivers, are installed, and show as Nexus 7, in device manager, ... than the fun start's. Of course settings/developer options/debugging is turned on.

This tablet, isn't being opened or found as a usb device and given a drive letter, at all. (accept in device manager) so ...?

Deleted the drivers and reinstalled them, the tool kit, can't confirm they are installed all the way or correctly.

I have tried other USB port's, shortened the cord, minimal running programs on the PC tried the other drivers PdaNet, etc.

I've booted into recovery with the USB cord plugged in, (with device manager on my screen) so I could see any changes, it seems to correctly identify the found tablet and act's as if it's all set up.

Nothing's working though.

I want a "connect to PC" window, and the choice to connect as MTP (media device), or install driver given, but that's not possible when the USB cable is plugged in.

What should I do? What have I forgotten, (or never learned) about these driver installations?

Thanks.
 
Hmm, DimBulb (great username, btw :)), looks like you've hit all the obvious things...

Have you grabbed the USB drivers from here?:

ASUSTeK Computer Inc. -Support- Drivers and Download Nexus 7

Change the OS: dropdown to "Android" and then expand the "+ USB (1)" section (click on the plus sign), then choose the "Global" download link (its the middle one) to download the "usb_driver_r06_windows.zip" file.

You could also try booting-up Linux from a CD or USB drive and see if you get access from there--since Linux plays much nicer with USB connectivity than Windows, it might prove / rule-out a hardware connectivity issue and/or point towards the Windows drivers as the issue.

Also, one last thing you've probably already tried: I often (always?) have to make sure I'm past the unlock screen in order for my USB disk connectivity to work (this is a long shot but didn't want to omit ideas).

Best of luck!

:)
 
  • Like
Reactions: DimBulb
Upvote 0
Mr scary Sir, I'm awed you would reply. Your fame is legend.

With your excellent instructions to find them, I got those usb drivers. I upgraded, the drivers in device manager (with those), they were seen, and accepted.

No change unfortunately, device isn't showing up in "my computer" as a usb device for storage or another drive letter.
Booted into recovery, the PC saw and accepted a new device, loaded the drivers there, and in device manager, the drivers/device, under Android phone were see as Galaxie instead of Google Nexus 7 (as loaded from WuggsTool... but on rebooting the tablet, that didn't provide the access from PC to Tablet, and they are again seen as Android/Google Nexus7.

Is there a need to un-root, and re-root do you think? I'm on CyanogenMod 10.1 grouper 4.2.2JDQ39

Oh, and the un-lock screen, on the tablet, I take it? I don't use that feature, so checking see it wasn't on, or in use. Is that what you meant?

Thanks.
 
  • Like
Reactions: scary alien
Upvote 0
One last note, than I need to leave. From the pull down, the option: "connected as a media device can be opened, doing that, found the option to change to a camera (PTP).
Default, Media device (MTP)
Or opptionally, Camera (PTP)

Setting it as Camera, gave, in my computer, a usb device/drive letter/camera icon,
and in device manager, a "new" imaging device, and names it as Nexus 7.

Here's screen shot's, of both. As far as gaining access, in Camera, it did, but extremely limited, and showed a couple of pix taken long ago.

The ADB interface, isn't interfacing, beyond whats been described. This behavior seems so much like the "close but no cigar" that lot's of us ran into with TETHERING, after the OTA update onto our phones of B11 J.B.

Just weird!
 

Attachments

  • ScreeShotNexus7NotSeen.jpg
    ScreeShotNexus7NotSeen.jpg
    214.7 KB · Views: 72
  • ScreeShotNexus7AsCamera.jpg
    ScreeShotNexus7AsCamera.jpg
    215.1 KB · Views: 83
  • Like
Reactions: scary alien
Upvote 0
LOL, DimBulb, you are too kind, my friend :).

Yeah, if you don't have a lockscreen, then no worries about that (we had a discussion on the GNex area about being able to access the internal storage for that when the lockscreen was still up, but I guess that either doesn't apply here or isn't an issue).

So I am just a little confused on one point: are you able to see and do things in Wug's Toolkit when booted in recovery? That would be the using adb USB driver mode by the way...

Now, I'll admit I am not a USB guru of any sort--I fumble and stumble my way around, LOL ;) :) :p, but here's a few notes for us to compare (in no real order):

1. There's an adb mode for the USB drivers (i.e., different from fastboot mode)

2. There's a fastboot mode for the USB drivers (i.e., different from adb mode)

3. You could also try mskip's [Google Nexus 7 TOOLKIT V5.0.0] Drivers, Backup, Unlock, Root, Recovery, Flash + MORE utility (look for the section labled "1. INSTALLING ADB/FASTBOOT DRIVERS" for details) for the USB drivers.

I've never used it, but mskip knows his stuff and this is very similar to Wug's Toolkit. I also don't really know if installing the adb and fastboot drivers get you the USB drivers you need for a normal Android boot and file transfer (but I would have guessed so).

4. I've read USB instructions say before that you need to uninstall all of the other USB drivers you have before installing the new one. I've actually never done this since it seems a bit overkill to me, but I'm guessing it might help in your case since it's possible that your PC is getting confused about how to properly communicate with your N7...:dontknow:

5. My Device Manager screen shows "SAMSUNG Android Phone" with "Google Nexus 7 ADB Interface" underneath it... I'm not really sure why is says SAMSUNG since it's an Asus device but I also don't remember exactly which USB drivers I've installed for the N7 :thinking:.

6. In the drop-down notification's "Connected as a media device" pulldown ("Touch for other USB options."), I only have Media device (MTP) checked (Camera (PTP) is un-checked).

Just thought I'd throw the above out there for you...maybe something will ring a bell or will help...

Lemme know how else I can help! :)
 
  • Like
Reactions: DimBulb
Upvote 0
Scary, (your not at all frightening, only helpful, unlike most "other" aliens I've known).

"are you able to see and do things in Wug's Toolkit when booted in recovery?" No,.. have been told no ADB device is present.

"1. There's an adb mode for the USB drivers (i.e., different from fastboot mode)" I don't know what that means.

"2. There's a fastboot mode for the USB drivers (i.e., different from adb mode)" I don't know what that means, either. :eek:

As far as removing the drivers, I've been doing that, (with Wuggs), and also in Windows, device manager, (un-install). Tried a number of time's to "plant" the drivers by re-installing, but with un-installing between.

I've been using the widget that comes with RomToolbox Pro, and it's got a fast-boot, that can peal paint, it's so quick, but it's just re-booting, ... very quickly.

"3. You could also try mskip's [Google Nexus 7 TOOLKIT V5.0.0] Drivers, Backup, Unlock, Root, Recovery, Flash + MORE utility (look for the section labled "1. INSTALLING ADB/FASTBOOT DRIVERS" for details) for the USB drivers. Oddly I'd stumbled onto that very site and was lifting what I could about the drivers, before I asked for help here.

I'll go back to mskip's and re-read and then try his toolkit. Maybe that can make the difference.

Thanks so much for giving over your time to all these suggestions, and the much needed support.



 
  • Like
Reactions: scary alien
Upvote 0
:)

Regarding the adb and fastboot stuff--I was just pointing-out that the USB drivers (or the protocols that the USB connections need via the drivers) are different for both adb mode and in fastboot mode. adb is available to you in both a custom recovery (like ClockworkMod or TWRP, etc.) and in "normal" (regular) Android when USB debugging is enabled and permission is given (via the prompt you get when you first connect). fastboot (or bootloader) mode is only used and needed for the fastboot utility when the device is sitting at the bootloader screen.

~ ~ ~

Do you have a CD or DVD burner and can you boot your PC from that? We could try burning a Linux distro to a disc and I could lead you through seeing if Linux has any issues... I ran into a really cool little thing (a small, 47MB Linux image) by SuperR last week that is pretty stripped-down but should at least help us rule-out some things.

Let me know if you want to try that...
 
  • Like
Reactions: DimBulb
Upvote 0
SuperR sure get's around. I remember reading some of that thread, and he's been helpful recently with the tethering problems after the OTA to the phone.

Yes I can boot from DVD. I've never used Linux, but can see where your going with that, I'll go find that thread of SuperR's, (unless you have it handy to link to).

Since I just ran GoogleNexus 7 Toolkit, and it loaded the drivers, and has acted exactly as the other methods so far, (drivers, but no Windows/Android interfacing), I'm open to trying the boot into Linux.

This is such an unusual, problem, it seems so simple to solve, yet over and over something is out of whack and I want to know what it is. Windows? It's XP, Service pack 3, I've upgraded the network framework to version 4 ,for another piece of software that called for it. Other than that, this is identical to the OS the tablet and phone have always embraced.

Thanks Scary.
 
  • Like
Reactions: scary alien
Upvote 0
SuperR sure get's around. I remember reading some of that thread, and he's been helpful recently with the tethering problems after the OTA to the phone.

Yes I can boot from DVD. I've never used Linux, but can see where your going with that, I'll go find that thread of SuperR's, (unless you have it handy to link to).

Since I just ran GoogleNexus 7 Toolkit, and it loaded the drivers, and has acted exactly as the other methods so far, (drivers, but no Windows/Android interfacing), I'm open to trying the boot into Linux.

This is such an unusual, problem, it seems so simple to solve, yet over and over something is out of whack and I want to know what it is. Windows? It's XP, Service pack 3, I've upgraded the network framework to version 4 ,for another piece of software that called for it. Other than that, this is identical to the OS the tablet and phone have always embraced.

Thanks Scary.

Yeah, SuperR's pretty sharp, eh? :thumbup: (I'm still working on something for him--LOL, related to USB issues, too :p).

Here's the link: http://androidforums.com/warp-sequent-all-things-root/747022-tool-warp2-cwm-recovery-flasher.html

We obviously don't want to use any of the programs or options on there--we just want to use the Linux install to launch a Terminal session and do this:

$ sudo adb devices
$ sudo adb shell ls -al /sdcard
$ sudo adb shell ls -al /sdcard/*

(I think the root password is just "root").

I can walk you through things if you need...I might have to grab my laptop to boot it up again, too, if you need.

If this get's too hairy and you have time, we can Gtalk via scary.alien@gmail.com.

:)
 
  • Like
Reactions: DimBulb
Upvote 0
I am downloading and will have it in a minute, I'm so glad you anticipated me.
Newbie to Linux means I'm sweating already. You make it easy. Would I be using the drivers previously downloaded from your first reply? And, it's going to take me a while to re-familiarize myself with ISO, and then do this, so may be some while.

"We obviously don't want to use any of the programs or options on there--we just want to use the Linux install to launch a Terminal session and do this:
Quote:
$ sudo adb devices
$ sudo adb shell ls -al /sdcard
$ sudo adb shell ls -al /sdcard/*"

I'll say thanks now to you, and also on SuperR's thread ...
http://androidforums.com/warp-sequent-all-things-root/747022-tool-warp2-cwm-recovery-flasher.html
 
  • Like
Reactions: scary alien
Upvote 0
Oh, you won't need any drivers at all for Linux...in fact, you should be able to view the files on your N7 from a file browser on the Linux install (I don't know if that utility was included in SuperR's setup, though).

I just figured if we could get adb access working from the same PC, albeit with a different O/S, then that would confirm that it's an issue with the USB drivers under Windows.

I'm gonna boot up the same thing as you...gotta grab my laptop...
 
  • Like
Reactions: DimBulb
Upvote 0
Ugh...don't know how to or think we can use a file browser in Linux to browse the N7's SD card's filesystem (I'm guessing that's what the MTP for/with Windows does :dontknow: :p).

No matter, if you can boot-up the .iso file, plug in your N7 to a USB port, and get it to respond to the "adb devices" or an "adb ls -al /sdcard/*" command, then we know that USB access to your N7 does indeed work...
 
  • Like
Reactions: DimBulb
Upvote 0
If you can boot-up the .iso file, plug in your N7 to a USB port, and get it to respond to the "adb devices" or an "adb ls -al /sdcard/*" command, then we know that USB access to your N7 does indeed work...

I just burned the disc, glad you were reading my mind again, (scary alien indeed), as being plugged in with the tablet, when booting seemed smart, but could blow up the computer AND the Nexus for all I know.

Give me a minute here ...
 
  • Like
Reactions: scary alien
Upvote 0
Wow, what an experience. That was worth the price of admission. I simply didn't expect the operating system, to take over, my monitor and computer. One bug, (and it's mine), my screen resolution is set at 1152x864 pixels, so the screen was dominated by the message, yet I worked around that while getting familiar with the OS.

Down to the actual value of this neat tool from SuperR. It worked flawlessly to run the commands you gave me Scary, and ran through the process finding and installing drivers, and giving the (on his back android) fast boot screen, to show who was in charge. It was working in both worlds, the PC and the android for sure.

Unfortunately, on reboot, the PC is still not connecting with my tablet.

Earlier I made a nandroid back up with the thought, that it might be necessary to load a factory image and un-root to make the changes from scratch so WinXP can think it's the boss, and "allow" itself to "actually" use these drivers that have been installed. After that, I can always reload the grouper I'm on now.

I'm very gratefull to have gotten so much of your help Scary, and actually done something so cool as to flash Linux on my Windows computer, MAN that really was a rush.

Thanks.
 
Upvote 0
I've been nail biting reading this thread. :eek:

MTP - Microsoft's mass transport protocol and the source of many headaches.

I don't have this tablet but fwiw, I often just use an FTP server app (free in the Play Store) on my phone, and then follow instructions to access storage from the browser via wifi.

Slower, not perfect, works in a pinch for lots of MTP problems.

Probably I'm not really helping, I just wanted to hang and say good on ya to the both of you. :)
 
Upvote 0
Yeah, I am very excited about SuperR's Linux flashing tool--it's got a lot of future potential for many devices--many kudos and thanks to him for sharing that and his knowledge about it!

Booting from a Linux CD is pretty cool, eh? :) I didn't really expect anything to "stick" afterwards since it's really OS-dependent and only last while you were booted-up in Linux--so, that does indeed tell us that Windows and/or the USB drivers you're having to muck with is the issue.

Not sure where to go from here...things should be working from Windows...can you get hold of another PC or laptop and try to install the USB drivers there and see if that gives you access? Again, that's just narrowing-down and ruling-out (or confirming) where the issue might be...

Happy to help however I can! :)

I know how frustrating this must be and the nature of the back-and-forth of forum posts is nice, but inherently slower ;) :).
 
  • Like
Reactions: DimBulb
Upvote 0
I've been nail biting reading this thread. :eek:

MTP - Microsoft's mass transport protocol and the source of many headaches.

I don't have this tablet but fwiw, I often just use an FTP server app (free in the Play Store) on my phone, and then follow instructions to access storage from the browser via wifi.

Slower, not perfect, works in a pinch for lots of MTP problems.

Probably I'm not really helping, I just wanted to hang and say good on ya to the both of you. :)

LOL, EM--honestly, I was thinking about you when MTP and Linux came-up ;) :).

Thank you for looking in on us and let us know any other thoughts you might have! :)

I'm scratching my head here at this point :p.
 
  • Like
Reactions: EarlyMon
Upvote 0
Thanks for the comments, I was using the FTP that bolt's on to Firefox this morning, to access a friends site. I'll have to look into the version for Android.

I'm turning now to the setting(s) that must be not "turned on yet" in this new WinXP install. Years can go by and I don't dig around in the guts of Windows like I used to.

I'm convinced it's a simple thing, something overlooked, or not-yet-added, or an update, that hasn't been applied, so Window's XP will get a clue, and interface with Nexus. Just for giggles, I've just plugged both into USB, for the first time....

And I see that the device manager creates a "portable devise" to interface with the Phone for instance, (only when the phone is plugged in), while not with the tablet. Plugged in the phone and tablet become "Android phone" and under that, the actual device is named ... i ZTE ADB interface Or Nexus 7ADB Interface .

Well this has been fun.

Much appreciate your words.

Thanks.
 

Attachments

  • BothAndroidsAtOnce.jpg
    BothAndroidsAtOnce.jpg
    75.5 KB · Views: 130
Upvote 0
MTP isn't built in to WinXP. Sorry if this is a duplicate but just in case - http://answers.microsoft.com/en-us/...ndows-xp/fa19dfda-aae2-4ea1-b959-fe175a3ebb59

It didn't get built in to Ubuntu until 13.04 (I think).

FTP server is easy. Install, launch, follow instructions and say what it says into your browser on your PC, no add-ons required.

This one doesn't suck - "Ftp Server"

https://play.google.com/store/apps/details?id=com.theolivetree.ftpserver

If you're really lucky, AirDroid may work for what you need over wifi.

MTP is the bane of my existence. :rofl:

Best luck, that's about all I know. :eek:
 
Upvote 0
can you get hold of another PC or laptop and try to install the USB drivers there and see if that gives you access? Again, that's just narrowing-down and ruling-out (or confirming) where the issue might be..

That's a good idea!

And at the same time, the question comes to mind, has anyone else ever had this (backward) problem before?

I mean, it's always about the attempt to root, to install etc. to go from the PC to that phone or tablet and change the android to your liking.

But that's not what's happening here. The tablet WAS interfacing, windows XP was compliantly hooking up, ... nothings changed with the tablet, it's the PC that's got the hick-ups, the Tablet is rooted, and I can go into root with a number of the apps installed.

I've entertained these devices long enough.
Now I think I'll let myself BE entertained by a large screen machine, and watch a movie.

I'll take some time here to say thanks again. :)
 
  • Like
Reactions: scary alien
Upvote 0
MTP isn't built in to WinXP. Sorry if this is a duplicate but just in case - How do I install the MTP drivers for Windows XP? - Microsoft Community

:eek:


I'm finding this very helpful the link I followed to get the MTP drivers, and then the idea led me on a google look-up, and found this thread, with an interestingly similar problem, and kind-of odd solution.

http://forum.xda-developers.com/showthread.php?p=32260564

I seems they found success, by turning OFF, debugging during driver installation.

I'll be trying several other things, and will get back.

Thank you.
 
Upvote 0
Upvote 0
Question: Was the N7 plugged into the PC when it crashed?

Reason being, is when I first got a flash drive, I was running Win XP. I powered down the PC, then unplugged my USB stick and went home. Next day got to work and powered the PC on, wouldn't recognize the Drive. I tried to change the drive letter, everything. No Go.

I figured out eventually, that I needed to power down the PC, and plug the drive in while it was powered down, then boot the PC up. Once I did that, it recognized the drive.

Not sure if this is related to your issue, or even if my story helped in any way. I tried, and hopefully it helps. :)
 
Upvote 0

BEST TECH IN 2023

We've been tracking upcoming products and ranking the best tech since 2007. Thanks for trusting our opinion: we get rewarded through affiliate links that earn us a commission and we invite you to learn more about us.

Smartphones