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?
Related
Just ran into a problem which took me some time to solve. Thought I would share it to save other people some frustration.
After an adb reboot the i5800 got stuck in "modem" mode. i.e. android booted fine but gave a modem and a serial port over usb rather than adb. Reboots did not solve the problem.
The solution is to enter recovery screen:
reboot recovery
OR
press proper buttons to get into recovery mode
And then perform a reboot from there
Is this the same as *#7284# and selecting "PDA" on UART and USB, or just on USB? Or is this a completely separate thing?
miki.antena said:
Is this the same as *#7284# and selecting "PDA" on UART and USB, or just on USB? Or is this a completely separate thing?
Click to expand...
Click to collapse
Thanks so much for this!!!! After helping hack a friends build.prop to enable Apparatus compatibility in the Market, I found USB wasn't working properly anymore. Resetting changes in the phone didn't help (I had to do this via the phone terminal) although I at least managed to buy Apparatus before the sale ended.
After initially getting confused due to a lack of drivers and the occasional 'nH' showing up devices without drivers which made me think something was borked, I worked out from the VID & PID it was just the lack of drivers making (well I'm not sure why it did the 'nH' sometimes it got serial something instead), once I installed the drivers all was fine.
Except still mass storage wasn't showing and the Samsung connect manager didn't show up on my phone when I connected USB, nor did ADB work at all. In fact, it didn't even show up in the phone menu as debugging mode if I didn't start phone with it connected (or something like that). Funnily enough when I did get it the debugging to show up I did get the USB mass storage to show up in the phone, but it didn't help (it just unmounted the card which I think is all it ever does).
Anyway after a bit more fooling around I eventuall came across http://forum.xda-developers.com/showthread.php?t=1215103 and the stuff about modem and mkasick's post which sounded a lot like it could be my problem. The code for that Samsung phone didn't work so I searched for the 5800 and came across this giving me the right code. Sure enough UART (but not USB) was set to modem instead of PDA. I was unsure whether that was wrong but changed it anyway and yep that fixed it!
I still have no idea what went wrong. I had thought may be the phone didn't like me rebooting via ADB but I've now done that several times. In fact most of the stuff except install a superuser update has been more or less repeated. I guess it was just some strange rare occurence that it somehow got changed. I did have to reconnect the USB while working the first time, not sure why but ADB lost connection then I found couldn't connect. Perhaps that's somehow related. Now that I know what to do, it's trivial but very annoying when I didn't. I still don't get why Samsung decided to make the connect manager (my phone doesn't have that) only to have some hidden option where it can be set to modem or USB.
Partially because of this, I never got to get Tilestorm HD become compatible in time for the sale although my friend wasn't so interested in that. (Eventually I worked out using the THC Tattoo modded market which reports a fake resolution enables it. Well, I also modified the build.prop but I don't know if that was necessary. I wasn't able to do it solely by the build.prop. But it was way too late by then to buy Tilestorm HD cheap.)
Nil Einne said:
I still have no idea what went wrong. I had thought may be the phone didn't like me rebooting via ADB but I've now done that several times.
Click to expand...
Click to collapse
This may sound like crazy idea, but is your USB port/connector clean?
(The USB port allows for dozens of different phone functions when using very specific resistance between data pins.)
i bought a LG D802 32gb last night as i was using a 16 gb before i wanted to flash cloudy g3.. so i tried to install custome recovery twrp...
now i am in fast boot mode..
it says :
[880]fastboot mode started
[910]udc_start()
when i attach usb cable
[1100]-reset-
[1110]-portchange-
[1120]-reset-
[1130]-portchange-
[1140]-fastboot: processing commands
i tried holding volume + and and attaching the usb cable but no luck ... so now i have NO RECOVERY, NO DOWNLOAD MODE, AND MY WINDOWS PICKING UP MY PHONE AS "USB MODEM PHONE ADB PORT"
please help
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?
... 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...
Hi i have a nexus 7 (2012) everything was working fine until android 5. The device was slow and almost unusable. Then the 5.0.2 update came out and guess what? I updated it and now my laptop wont recognize the device so i tried a different cable and nothing. I plugged the nexus 7 in my second computer and nothing not even the sound that means you plugged something in the usb port. So i went to my brothers house and tried his computer.... the same... nothing. We plugged his nexus 7 (2012) 5.0.2 wich is the exact same device as mine and it works so we thought that it was the usb connector on the device and we switched my connector with his....NOTHING happens. computer wont recognize the device, no sound, no pop-up, no ADB detection. Does anyone have the same problem or a solution on how to downgrade 5.0.2 back to 4.4 without usb cable?
Thank you
Did you tried out to start n7 into fastboot mode and recovery mode?
Is usb not available also there?
fastboot and recovery mode also has no USB. absolutely nothing happens. when i connect the device it charges but the lightning icon does not appear on the battery in the status bar. and its not the usb port on the N7 i changed it.
?????????????????
Same here
I have the same Problem - a N7 GSM with 5.0.2 and no communication via USB.
I have tried different computers with Win7 and Ubuntu14.10. As well as differnt cables. (And all combinations of that work with my HTC M7, by the way)
Under Linux, not even lsusb shows the device, or dmesg shows any connection to a usb device.
To be completly honest, I did not give much love to my N7, I have been using it hardly. But when I did, I have been flashing some differnt Roms and testing different bootloaders so this might be some kind of my fault.
i updated to 5,1 and still the same problem so i assume its hardware related. but i know it is not the USB connector because i tried it on my brothers N7. and it works
Mine is quirky, comp recognizes it and can order boot but sideload and push to device don't work. Its odd.
Got myself a google LG Nexus 4.
Connecting via USB - 2 different cables, 2 computers, 3 different operating systems (archlinux, debian, windows vista ) - i get nothing (*).
the phone does not acknowledge that it is connected to a computer, but it charges ok.
the computers do not recognize the phone in any way, not even in dmesg (or device manager in windows).
i have tried changing options inside the phone (debugging on/off, mtp/ptp...), even a full factory reset, and going into recovery and wiping cache/dalvik cache. - nothing.
wiggling the cable and such does not help.
i even replaced the usb connector, no change whatsoever.
so something tells me that it is not a hardware problem.
the phone has been upgraded to android 5.0 (before i became the owner).
my endless searches show that nobody knows what's going on, it might be hardware fatigue, it might be related to the upgrade to 5.x, it might be a firmware problem...
any helpful pointers, including downgrading & softbricking the system would be helpful (i just want to install ubuntu phone onto it).
(*) my other android phone connects ok with both cables, to all machines and operating systems.
With the phone in fastboot or recovery mode, is it recognized?
The fact that the usb port has been changed could indicate a problem with the motherboard connector.
Go into device manager with your phone connected and uninstall the drivers. Then install "universal adb driver"(google it it's from Koush) with your phone NOT connected.
audit13 said:
With the phone in fastboot or recovery mode, is it recognized?
Click to expand...
Click to collapse
i tried adb, the device list is empty.
booting into recovery, replugging the usb cable, i still get nothing. it's like there's nothing to communicate to, both from the computer's and the phone's point of view.
i will have to play with fastboot (i gather it works only while the phone is booted into recovery?), but i doubt it'll change anything.
The fact that the usb port has been changed could indicate a problem with the motherboard connector.
Click to expand...
Click to collapse
do you mean the connector from the usb port, that flat cable snap-on thingy (far right on this image)?
is it realistic to try to fix that?
PS:
meanwhile the battery drained completely and i had a "Red light of death" which i managed to fix like this. i think it will take a while to recharge properly.
Adb commands will work with the phone booted into the rom. Use fastboot commands with the phone in fastboot mode.
Yes, the flat part at the it her end of the USB cable is what connects to the motherboard and is not worth fixing if that is causing the charging problem.
With a red LED, just connect it to a 2.0 amp charger using the original charging cable and let it charge for a few hours.
thanks again.
next thing i realized that the volume rocker isn't working (anymore?).
so i can't boot into recovery.
i don't know how, but once i managed to get into recovery, but couldn't make any choices in there.
anyhow, that sort of cinches it: i'm done with this phone. project failed.
(nevermind, it was a cheap ebay shot)
ubuntu phone will have to wait.