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?
Related
Hello All,
Basically, while Nexus is on it does not charge or even recognize a charge from anything, and it also does not recognize when plugged in via USB to my PC.
This occurred a week ago, noticeably a few days after installing MultiROM for testing. I thought MultiROM may have been the cause so went entirely back to stock ROM but still not working.
Couple things that I have noticed... When using MultiROM my drivers are no longer recognized as they should, but instead as Andriod bootloader. I had uninstalled and reinstalled new drivers to allow the flash and correction to Stock, which did work, but now nothing even remotely similar to my Nexus is showing up in my Devices. I have double checked with multiple cords, still no luck... I will say that I have not Enabled USB Debugging because I cannot. Every time I attempt to enable USB Debugging, the Nexus freezes up and reboots... I'm thinking this is the root cause of the issue or there is a fluke bad pin issue in my internals of the Nexus...
It seems that I cannot work in fastboot or adp mode as the USB is not recognized...
I've searched for several days for hours at a time for more info on this, but no luck! Any thoughts and help would be helpful!
Thanks!
DTTD said:
Hello All,
Basically, while Nexus is on it does not charge or even recognize a charge from anything, and it also does not recognize when plugged in via USB to my PC.
This occurred a week ago, noticeably a few days after installing MultiROM for testing. I thought MultiROM may have been the cause so went entirely back to stock ROM but still not working.
Couple things that I have noticed... When using MultiROM my drivers are no longer recognized as they should, but instead as Andriod bootloader. I had uninstalled and reinstalled new drivers to allow the flash and correction to Stock, which did work, but now nothing even remotely similar to my Nexus is showing up in my Devices. I have double checked with multiple cords, still no luck... I will say that I have not Enabled USB Debugging because I cannot. Every time I attempt to enable USB Debugging, the Nexus freezes up and reboots... I'm thinking this is the root cause of the issue or there is a fluke bad pin issue in my internals of the Nexus...
It seems that I cannot work in fastboot or adp mode as the USB is not recognized...
I've searched for several days for hours at a time for more info on this, but no luck! Any thoughts and help would be helpful!
Thanks!
Click to expand...
Click to collapse
Try doing a factory reset first, then see if USB debugging works.
If it won't work, could you try downloading a normal recovery on your device and installing without fastboot and adb connection with computer (I think that is possible, not sure). Is download, boot into recovery and flash like a ROM. Sorry if that's all wrong, I did Google but found nothing, yet I'm sure I did that to install a newer version of twrp???
Also, if you have root, could you try using adb over WiFi, this should work the same, although there is no fastboot.
Good luck!
Fallon9111 said:
Try doing a factory reset first, then see if USB debugging works.
If it won't work, could you try downloading a normal recovery on your device and installing without fastboot and adb connection with computer (I think that is possible, not sure). Is download, boot into recovery and flash like a ROM. Sorry if that's all wrong, I did Google but found nothing, yet I'm sure I did that to install a newer version of twrp???
Also, if you have root, could you try using adb over WiFi, this should work the same, although there is no fastboot.
Good luck!
Click to expand...
Click to collapse
Thanks for providing more information on this. I have done a Factory Reset via Settings and also via Recovery, but still not available.
I think I'm making progress with adb via Ubuntu over USB, but USB Debugging still gives the Epic crash and still will not charge while On, which is more just annoying than anything else.
Asus/Google Support are saying it is a physical pin issue, but that doesn't explain why USB Debugging is failing. Does anyone know where the USB files are contained? I'm wondering if I've messed up at the Kernel level. Any thoughts?
About my Nexus - More Info
I forgot that I should provide more information about what I'm running:
Phone: Nexus 7
Android Version: 4.2.2
Kernel version: 3.1.10-g05b777c
Build number: JDQ39
Prior to issue also had:
Recovery: TWRP
ROM: Stock JDQ39
MultiROM: Yes
UPDATE
So after more work on my Ubuntu we have found more information and seem to have narrowed down the issue! :fingers-crossed:
I have been able to flash via Fastboot just fine, which has thus allowed me to get TWRP installed and now I'm back rooted. I still cannot adb via USB though. We've double checked with multiple Nexus 7's of the same type, which allow command: adb devices and their devices will show, while it does not for my device. (Side note: my version of Ubuntu does not "see" the adb command in its pwd so... But tests have been done on other machines and worked...)
So after sifting down to adb issues, we found that in /data/property I'm missing persist.sys.root_access and persist.sys.usb.config ... But creation of persist.sys.usb.config didn't do anything...
I had a rooted 4.3 stock image on my N10. Got the notification about the downloaded update for 4.4
It did the update through TWRP (which was weird to me) and finished, restarts and gets stuck on the boot loading screen.
So I went into recovery, and cleared cache, no luck, then complete factory reset, no luck, then I added "System" to that wipe, not knowing what it was an now there is no OS installed.
I installed the Nexus 10 Toolkit (Unified Toolkit) and install the USB drivers, but my computer is not seeing my device..
Help?
As long as you can get to the bootloader, you can reflash a stock image. Easiest way is with wugfresh nexus root toolkit. It will walk you through the driver installation and the various image downloads.
That did not work.
The computer is not seeing my device. Drivers are installed, not seeing it, it's in the proper Boot mode.
I followed the mode that said I didn't need debugging enabled, still nothing.
bmancell said:
I followed the mode that said I didn't need debugging enabled, still nothing.
Click to expand...
Click to collapse
I would recommend uninstalling the USB drivers you installed with the toolkit and manually installing the Google USB drivers attached to this post. After you have installed the USB drivers I would recommend manually booting into your devices bootloader by simultaneously holding down the power button + volume up button + volume down button. Once you are in bootloader mode I would recommend download this Android 4.4 KitKat Factory Image and flashing it to your device in order to restore things to a working order. Let me know if you still have questions I'll be happy to help you out.
And want explain to me how I copy that file to my device when the computer can't see it?
bmancell said:
And want explain to me how I copy that file to my device when the computer can't see it?
Click to expand...
Click to collapse
Check out my previous post and see if those steps will allow your computer to see your device, and let me know how that goes for you.
Ok, I unziped the folder, got the tablet in bootloader mode, which I already said I tried, nothing.
Weird thing, I plugged the tablet into my other computer, it makes the noise for Windows 8.1 that you hear when you plug a USB device in, but there is no notifcation, nothing in device manager, nothing. Just the sound .
bmancell said:
Weird thing, I plugged the tablet into my other computer, it makes the noise for Windows 8.1 that you hear when you plug a USB device in, but there is no notification, nothing in device manager, nothing. Just the sound .
Click to expand...
Click to collapse
I just want to re-state everything to make sure anyone can understand.
This was a Nexus 10 rooted 4.3 Stock. I got the 4.4 update, it finished without issues, but got the boot loop issue.
I cleared cache, factory reset and eventually the system without luck, which left the tablet without an OS (bootloader or recovery only options).
My systems can not detect the tablet, I have installed, re-installed, tried two different toolkits and no luck.
I can't believe it's an actual brick that can't be fixed? Anyone?
Its definitely NOT your tablet. I had similar issues when rooting a Kindle and it was an issue with the PC's USB drivers. If you search the forums for USB / ADB drivers you will find a detailed discussion on how to delete existing drivers (its a process) and update new drivers.
sojthumper said:
Its definitely NOT your tablet. I had similar issues when rooting a Kindle and it was an issue with the PC's USB drivers. If you search the forums for USB / ADB drivers you will find a detailed discussion on how to delete existing drivers (its a process) and update new drivers.
Click to expand...
Click to collapse
Did you read? I have installed/reinstalled the drivers 3 times.
bmancell said:
Did you read? I have installed/reinstalled the drivers 3 times.
Click to expand...
Click to collapse
I also tried a third computer, and another cable. It will charge from a computer, nothing else.
I went through the same experience; it *was* the drivers. If you're using the wugfresh toolkit, it gives at least three options for driver installation. In my case only the drivers from pdanet worked. I've had similar issues in the past with my N7; in that case only the pdanet drivers worked on one computer, and only the Koush drivers worked on a different computer -- both Win 7 by the way; I have no idea why.
I did have to go through the whole procedure described in the toolkit to manually unistall old drivers and manually remove references to the device before reinstalling the driver.
You can get into TWRP, correct? Do you have a USB-OTG cable? You could download a ROM, put it on a flash drive then install it directly from the USB drive. There should be some flashable stock roms, or if you have an old Nandroid backup on your computer (always a good idea to have) you could restore it.
Sent from my Nexus 7 using xda app-developers app
gc84245 said:
You can get into TWRP, correct? Do you have a USB-OTG cable? You could download a ROM, put it on a flash drive then install it directly from the USB drive. There should be some flashable stock roms, or if you have an old Nandroid backup on your computer (always a good idea to have) you could restore it.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Don't know what a USB-OTG cable is, and not sure how you'd connect a flash drive, but...
I tried one more computer, this time it was a computer with Windows 7 one it. Detected the tablet right away.
So, why the heck does Windows 8 (8.1 to be exact) not allow my tablet to be seen (im sure with the OS on, and booted in, it will)./
tjupille said:
I went through the same experience; it *was* the drivers. If you're using the wugfresh toolkit, it gives at least three options for driver installation. In my case only the drivers from pdanet worked. I've had similar issues in the past with my N7; in that case only the pdanet drivers worked on one computer, and only the Koush drivers worked on a different computer -- both Win 7 by the way; I have no idea why.
I did have to go through the whole procedure described in the toolkit to manually unistall old drivers and manually remove references to the device before reinstalling the driver.
Click to expand...
Click to collapse
This must be why my Windows 8 machines don't work, but I dont remember seeing other driver options, only the one, will keep in mind in the future.
Sounds like the problem is solved, but I highly recommend getting a USB-OTG cable anyways. Go to Amazon and search for "USB-OTG". You can connect flash drives and external hard drives to your tablet. I got mine for $2.
Sent from my Nexus 7 using xda app-developers app
... and is no longer recognized when connected to a computer via USB, meaning I can't return to stock to get ready for the Lollipop OTA.
Got a rooted Nexus 4 running the latest PA beta.
What happens when connecting to PC:
- On two different Windows machines: systray popup saying "USB device not recognized. The last USB device you connected to this computer malfunctioned etc.". In device manager it says "Unknown USB device (device descriptor request failed)"
- On elementary OS, based on Ubuntu 12.04: nothing, besides charging.
No USB debugging connection notification on the Nexus 4 either when plugging in.
What I've tried (USB debugging enabled, all relevant drivers installed):
- Settings > Storage > USB computer connection > check Camera PTP (used to be required in order to get an RSA key prompt when connecting to a computer, now it does nothing)
- Flashing latest stable CM to see if PA was to blame. Made no difference.
- Uninstalling device through device manager in Windows and reconnecting. No effect. Driver update doesn't work either, finds nothing.
- Using Wugfresh's Nexus toolkit to see if that worked, but that obviously doesn't work either when the device isn't recognized, same with the Universal Nexus Linux Toolkit on Linux.
- Scouring the net for solutions and coming up with nothing
I have flashed factory images before on this phone without problems. Should I consider it a hardware failure by now, or is this a known issue with a fix?
Try a new wire, different usb port on computer, finally look into cleaning your charging port on the phone/replacing it.
DrFredPhD said:
Try a new wire, different usb port on computer, finally look into cleaning your charging port on the phone/replacing it.
Click to expand...
Click to collapse
Tried three different cables, every port on two laptops, no joy - my girlfriend's phone connects normally.
Wouldn't replace the charging port, then I'd just get a new phone since it's a 2 years old Nexus 4. If only there was a way to flash the factory image using only TWRP.
bimsebasse said:
Tried three different cables, every port on two laptops, no joy - my girlfriend's phone connects normally.
Wouldn't replace the charging port, then I'd just get a new phone since it's a 2 years old Nexus 4. If only there was a way to flash the factory image using only TWRP.
Click to expand...
Click to collapse
Flash this in twrp http://forum.xda-developers.com/showthread.php?p=47476426
Sent from my Nexus 5 using XDA Free mobile app
Thanks jd1639, that seemed to be exactly what I was looking for -
- but then I had an extremely blonde moment and formatted everything in TWRP, wiping the ROM I was gonna flash in the process, on a device where USB file transfer doesn't work anymore
My phone is now a paper weight.
Have you tried the file manager in twrp yet? I've found it connects when nothing else will...
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?
I need some help guys.
My Nexus 7 all of a sudden stopped sending data through usb OTG and i tried to erase cache through TRWP but ended up deleting the OS. Now I am stuck with a device with no OS. I cannot mount the USB for my computer to recognise it so that I can restore it. I tried ADB sideload but it doesnt load and gets stuck on starting...
If I click on Mount, I cannot click on the USB-OTG box. My computer does have the correct drivers for the USB as it used to work on it before but since the OTG stopped responding to data I am now stuck and cannot push a restore image to the device.
Any help would really be appreciated.
Many thanks.
I've tried almost everything I can think off. I tried different OTG cables, different computers. None of the computers even detect a device as plugged in. Whether I boot into bootloader or recovery I just cannot get the PC to even acknowledge the fact that something is plugged in. As a result I am just not able to flash it at all. I tried NRT with the soft-brick option but that fails too because it says no adb connectivity.
any help please?