Database Users

Unable to Connect N7 via USB to PC

First some background:
Playing around with some ROMs, I loaded up MIUI. I wanted to see what all the fuss was about. While installing from ROM Manager, the subsequent boot into CWM started my backup and installed the ROM. During the process CWM notified me the install was attempting to overwrite the recovery partition. I inadvertently said yes, one of the bad things about touch recovery...fat fingers.
Result:
CWM was blown away. MIUI failed to install Google Apps.
I connect the N7 up to my PC. It is not detected. No ADB available, however I can use wireless ADB so I installed ROM manager and reflashed CWM. This was were the fun began. Everything on my internal storage got nuked during the install and attempted recovery. I had to format internal storage.
No biggie, I have backups on my laptop through WUGFresh Root Kit. I will restore back to stock and start over.
Problem:
No computer I connect the N7 to detects it, regardless of USB connection method nor OS on the PC (Ubuntu, Win 7, Mint). I still have wireless ADB but that doesn't help with fastboot.
Current Status:
Currently I am running AOKP, after flashing multiple ROMs and Recovery between TWRP (current) and CWM. Also I have done many factory resets, cache cleaning, etc.
My diagnosis:
I think my boot, recovery or bootloader partition is borked due to the fat finger in CWM while installing MIUI. The added bonus...without being able to connect the N7 to any PC, I can't get into recovery unless I get lucky (1 out of 10 tries I get lucky and can get into recovery). I can get into recovery as long as I can boot into a ROM and do any common method to reboot recovery.
Question:
Now my question, does anyone have any ideas what I can do to get the USB connection working again to allow ADB/Fastboot connections?
Additional info/Review:
I have a GNex that I can ADB/Fastboot into without issue.
I have tried multiple different cables to connect to PC/Laptops.
As mentioned, I have tried multiple PCs to attempt a connection running everything from Windows 7 to variations of Linux (Mint and Ubuntu)
All the cables work fine with GNex, excluding one cable I deemed trashworthy.
I am fairly certain that the micro-USB port is fine, I can charge without issue even connected to a PC. OTG cable works perfectly fine.
I did something saying a port was open from the N7 that cause USB connection to fail. I forget what I did to find that message or what program I was using. I think I was trying to do a adb usb command from the command line on the N7.
USB Debugging is enabled.

More info:
No errors in logcat when connecting N7 to PC.

Try to do complete wipe & flash stock . My desktop has never detected the n7 but the fastboot works. I was able to flash stock using wugs toolkit.
Sent from my GT-I9300 using Tapatalk 2

That is the problem, I can't get any PC to recognize the n7 is connected. therefore, wugs root tool kit wont work. it uses fastboot and adb. without the drivers loaded and the device detected, I can't use wugs. this happens even on machines I have never plugged the n7 into.
If I could find a flashable zip of stock, that might do the trick.
I am wondering if I can use the otg cable and connect from my phone with adb? I don't think I can run fastboot commands from the phone though.
Sent from my Nexus 7 using Tapatalk 2

Doubt you could. Have you tried booting into bootloader then changing the usb port on the and also try reinstalling the drivers. When in bootloader try locating your device in device manager.
Good luck
Sent from my GT-I9300 using Tapatalk 2

panjaby said:
Doubt you could. Have you tried booting into bootloader then changing the usb port on the and also try reinstalling the drivers. When in bootloader try locating your device in device manager.
Good luck
Sent from my GT-I9300 using Tapatalk 2
Click to expand...
Click to collapse
even in boot manager, the device does not show in device manager on windows and it can't be seen on Linux either when looking for attached devices.
With my old viewsonic gtab I use to verify there was a device connected from command line, that doesn't work either. I'll post that command later today, just for reference.
Sent from my Nexus 7 using Tapatalk 2

OK, I have verified the problem is on the tablet side. I can connect my OTG cable to the tablet and mount my GNex allowing me to perform adb commands sent to the phone. I can not mount my tablet to the phone reversing the cable.
N7 ---> OTG ---> USB ---> GNex (works)
GNex ---> OTG ---> USB ---> N7 (fails, phone does not recognize the tablet being connected. I verified I could connect to a USB stick without issue.)
I think this narrows it down to MTP/PTP being disabled somewhere. Since it affects fastboot as well, I am assuming something in boot or bootloader. I ruled out recovery due to recovery working correctly when I can get to it.
Any ideas?

[Q] Unable to access NTP on Mac

I have a Nexus 7 (2012) that I am trying to get to connect to a mac so that I can transfer some files and a backup, but it does not seem to be a normal problem. I can use fastboot just fine, and have verified this with -fastboot reboot. When I connect my N7 to the computer while it is turned on and on the home screen, it begins to charge, show the status bar 'usb debugging', but does not actually connect with MTP using Android file transfer or otherwise. I have tried different cords, reinstalling Android file transfer, usb ports, and a Windows 7 laptop with drivers from Wugs toolkit installed, but still nothing. I am running a stock rooted 4.3 JWR66Y with unlocked bootloader and TWRP 2.6.3, and have even opened it up to make sure that the micro-usb is not loose; It isn't. If someone could help me with this that would be greatly appreciated, and if I left out some information please tell me
Thanks
P.S Just checked before posting and I apparently have stock recovery back on.

[Q] HELP with recovery, no usb access to nexus 7, not detecting with official cable.

Ok so long story short, i have a nexus 7 2012 which a rooted and installed cyanogen mod.
I was using it as a car install and works perfect, i'm using an otg cable to mount usb sticks, triggering soft shutdown and powering the nexus etc. So usb seems to be working fine.
Basically i removed the tablet it to modify the bootloader to turn on automatically with ac power applied, if the battery runs out i have to manually power on with button, but now i'm running into a problem.
Ever since taking the tablet out and trying to connect over usb, none of my computers detect the tablet.
I've tried different operating systems, drivers, cables etc etc.
Also changed from mtp to ptp in storage and also turned on usb debugging mode. If i connect an otg cable the nexus see's the otg and i can mount usb's etc.
So i thought i might try recover the nexus back to factory, maybe there was an issue with the rom corrupted etc, I've downloaded the original 4.2.2 firmware which is currently installed.
Booted into recovery and tried re-installing the 4.2.2 zip, it keeps aborting. A guy in work tried to use sideloader and connect via adb. no luck.
I'm not very familiar with the android platform so i've no other ideas what to do and other idea's how to recover now.
The guy i work with mentioned using a usb jig, would that be the way to go or can anyone else suggest some else that might help.
Thanks

Before you updated when was the last time you connected your N7 to your computer?
When you connect your N7 to your computer does it act like it is charging? Have you tried more than one computer? I had a similar problem with mine last year & sent it in 3 times. Asus replaced both the USB port board & the main board on different occassions. I suspect your mainboard might be faulty.

Does adb see the device

jadesse said:
Before you updated when was the last time you connected your N7 to your computer?
When you connect your N7 to your computer does it act like it is charging? Have you tried more than one computer? I had a similar problem with mine last year & sent it in 3 times. Asus replaced both the USB port board & the main board on different occassions. I suspect your mainboard might be faulty.
Click to expand...
Click to collapse
I last connected the nexus to the laptop a few monts back to load some music onto it, didn't have a problem. It's only been connected to a computer maybe 3 times. once to root/rom it then another few times to load music etc.
I can't see why the usb board maybe faulty as i can read data from a usb key when the otg cable is connected.
It's a strange one. You could be right, i might try pick up a broken nexus and swap some parts. Usb board etc.

crusrod said:
Does adb see the device
Click to expand...
Click to collapse
Yes adb is shown in device manager, but it's not recognizing the nexus, comes up with an error 10 , cannot start. etc etc

foster182 said:
Yes adb is shown in device manager, but it's not recognizing the nexus, comes up with an error 10 , cannot start. etc etc
Click to expand...
Click to collapse
I am having this same problem on my (unrooted) HTC One after attempting to "convert" it from an AT&T to a Google Play Edition device with the procedure described here.
As part of the procedure, I attempted to flash the stock Google Play Edition ROM using fastboot commands, but I got an error message. The instructions say to just try the flash again, but the phone no longer connects properly via USB (error 10) while in bootloader mode. While in bootloader mode, the phone indicates there is some sort of problem (a line showing the OS version is highlighted in red), and attempting to enter recovery mode does nothing but display a phone with a big red X in it. The phone seems to operate fine and responds to ADB commands when the phone is fully booted, albeit with the old OS (not Google Play Edition) still in place.
Any Android device could theoretically get in this state. We're sort of "paralyzed", because everything we want to do to regain control of the bootloader and fix the situation seems to require issuing fastboot commands from a computer connected to the phone while it's in bootloader mode. Yet entering recovery mode or getting a computer to connect to it via USB no longer seems possible.
I wonder if there's another way to issue fastboot commands without relying on the USB connection to a computer?

USB Device not recognized on Windows

I have a dilemma. This morning my usb was working fine but I needed to get back to stock and unrooted. I flashed the system.img from the NDR90X factory image and wiped my data (not userdata however because I didn't want to lose everything) the phone booted up just fine and operates fine, other then it doesn't mount on my pc anymore. fastboot and adb do not work for me either. I tried mounting on both windows and linux, I tried using another computer, and I have tried mounting through the recovery. none of these have worked. I cant try going back to complete stock because fastboot is not recognizing the device either. the phone still charges fine with no problems. But I still am getting the feeling that maybe the usb port has malfunction. I was hoping that maybe someone could help me with this problem and reaching a solution. I don't know if I can contact google about this problem because my device cannot be returned to completely stock.
I forgot to mention that after flashing the stock system.img I also flashed TWRP, and since then I am back on a custom rom to see if maybe that would fix my problem. However it still persists.
I have uploaded a picture showing what error message I am getting on windows.

Reinstall the USB drivers

hd-renegade said:
Reinstall the USB drivers
Click to expand...
Click to collapse
Turns out it was the USB that doesn't work. When I got home I tried another USB that I have and it works fine.
Sent from my AOSP on angler using Tapatalk

Nexus 6p stuck in twrp with no os and no connection to pc

i made the boneheaded mistake of deleting everything off my phone in twrp (3.2.1-0) and ive had little success in trying to recover it.
1. my pc will not recognize it when its plugged in, this was also an issue when it had an os on it. ive tried to install the google usb drivers as well as the hisuite drivers with no success
2. i bought a usb otg adapter so i could possibly push the new os through there but when ever i try i get 0mb when trying to select the storage in the mount section of twrp. ive also tried reformatting the usb multiple times but that didnt work either.
3. there is no connectivity while in fastboot as well as adb
I'm caught in a tight situation and don't have the means to buy a new phone if anyone could help me out i would greatly appreciate it

shpadza said:
i made the boneheaded mistake of deleting everything off my phone in twrp (3.2.1-0) and ive had little success in trying to recover it.
1. my pc will not recognize it when its plugged in, this was also an issue when it had an os on it. ive tried to install the google usb drivers as well as the hisuite drivers with no success
2. i bought a usb otg adapter so i could possibly push the new os through there but when ever i try i get 0mb when trying to select the storage in the mount section of twrp. ive also tried reformatting the usb multiple times but that didnt work either.
3. there is no connectivity while in fastboot as well as adb
I'm caught in a tight situation and don't have the means to buy a new phone if anyone could help me out i would greatly appreciate it
Click to expand...
Click to collapse
Powerdown your phone and boot to bootloader by pressing powerkey and holding vol- then connect to your computer you should see the Nexus 6p on your pc and. from your computer download any rom of your like,gapps,root optional and copy it to your internal storage. Then just flash.

Gearswar said:
Powerdown your phone and boot to bootloader by pressing powerkey and holding vol- then connect to your computer you should see the Nexus 6p on your pc and. from your computer download any rom of your like,gapps,root optional and copy it to your internal storage. Then just flash.
Click to expand...
Click to collapse
that doesnt work either. i have all of the appropriate drivers and still nothing.

That could be your pc. Try a different port or even better another pc.