Database Users

[Q] N4 won't boot, isn't recognized by any computer (adb, fastboot, etc.)

A couple of weeks ago my N4 decided that it didn't want connect to my computer. I tried windows xp, 7, and osx. I tried 5 different usb cables that worked with other android phones just fine. I tried all usb ports on said computers. I've uninstalled and re-installed all drivers, using all the known methods. Then I noticed that I was getting terrible battery life. Like 5% gone in 20 minutes with all radios turned off and leaving it in my pocket. I was on the latest verison of PA with the latest verion of franco.kernel and I've had no previous problems with my phone.
So I thought maybe I did something to it like a bad flash, so i downloaded a stock 4.2.2 zip and flashed it (with gapps). The problem persisted. So I proceeded to wipe the phone in cwm in an act of desperation, and lo and behole I was then stuck with the same problem as before, but this time with no working os to boot to, and no way of connecting it to fastboot or adb in order to put any files on the sdcard/ flash it back to stock. I am, however, still able to boot into cwm and the bootloader. Then, thinking it might be a problem with the usb daughter board as whenever I tried to plug my phone into a computer it gave me this:"windows has stopped this device because it has reported problems. (code 43)", I ordered a replacement. Replacement came, I swapped them out, and absolutely nothing has changed. I tried uninstalling/deleting drivers and re-installing them just to make sure, but same results as before. Also, the N4 DOES charge when plugged into a power source like normal.
So the way I see it, I can either keep trying to replace parts, or one of you wonderful people know some crazy fix to my problem. If not, then I could go the other way, and attempt to brick the N4 even further in order to get it replaced (I.e. it's not possible to see whether or not it's unlocked/has a custom recovery). Also, I can enter "download mode" by holding down the volume buttons and connecting a usb cable, but windows still doesn't recognize the device.

usb not working

Hey guys I tried to connect my nexus 7 to my Windows 7 laptop but nothing popped up it just showed as charging on my n7 I've tried update the drivers and different cables and different laptops too but it's all the same, even fastboot doesn't show up or mtp in twrp, any ideas how to fix this guys?

Anyone got any idea how to fix this problem?

Hey,
Have you tried enabling USB debugging in Settings > Developer Options?

Fobos531 said:
Hey,
Have you tried enabling USB debugging in Settings > Developer Options?
Click to expand...
Click to collapse
Cheers mate but yep I tried that and nothing changed

I'm in the same boat. Had this problem for a long while, almost had my guarantee expire so I had it fixed. Not sure what caused it, or what fixed it. But couple of weeks later I was transfering some files through the now working USB port and accidently touched the cable - the device lost connection mid-transfer and since then I was unable to use the USB to transfer files, or connect the device to anything but the charger..
Along comes the 5.1 OTA which I decide to install and mid-install there was an error and the device soft-bricked - I can't boot it, it shows the Android robot with a red traingle and exclamation mark and 'No command.' written under it, at which point it reboots after a couple of minutes.
I can access recovery and fastboot mode and excecuted a factory reset but to no avail. Does anyone know how to fix the USB so that I can reflash stock and make my device work again?
Also, any ideas if one could bypass the use of the USB port in fixing the softbrick would also be helpful.

Armeddy said:
I'm in the same boat. Had this problem for a long while, almost had my guarantee expire so I had it fixed. Not sure what caused it, or what fixed it. But couple of weeks later I was transfering some files through the now working USB port and accidently touched the cable - the device lost connection mid-transfer and since then I was unable to use the USB to transfer files, or connect the device to anything but the charger..
Along comes the 5.1 OTA which I decide to install and mid-install there was an error and the device soft-bricked - I can't boot it, it shows the Android robot with a red traingle and exclamation mark and 'No command.' written under it, at which point it reboots after a couple of minutes.
I can access recovery and fastboot mode and excecuted a factory reset but to no avail. Does anyone know how to fix the USB so that I can reflash stock and make my device work again?
Also, any ideas if one could bypass the use of the USB port in fixing the softbrick would also be helpful.
Click to expand...
Click to collapse
Do you twrp installed mate?

No, I do not.

Google Nexus 4 Does not show up as USB device but charging OK.

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.

Android boot loop on Samsung Galaxy Grand Neo (i9060)

Hey!
New to XDA but a complete fan of the help and guides you guys provide.
So, I acquired an i9060 smartphone and successfully installed CM 11 without the help of my laptop since the usb cable through Odin never worked for me (driver issues on Win10?).
Unfortunately, my phone entered an Android boot loop. And now with a lot of attempt I can't even enter CWM or even charge my smart phone, as it always reboots while trying to charge the battery (it's always drained) or gets stuck during logo before accessing CWM.
I tried to install Samsung drivers, Kies, ABD, Odin to restore the firmware but... nothing seems to recognise this Samsung device. Does anyone had the same problems I'm having now? Any suggestions?

You might try another USB cable, USB port, or even another computer. Without Odin, you're not going to be able to fix this since recovery is no longer available.

es0tericcha0s said:
You might try another USB cable, USB port, or even another computer. Without Odin, you're not going to be able to fix this since recovery is no longer available.
Click to expand...
Click to collapse
Tried on 3 laptops but the problem persists. Never thought of changing my usb cable though. I'll give it a shot
Btw, is there anyway to use an external SD card to force a factory reset?

n1ur0 said:
Hey!
New to XDA but a complete fan of the help and guides you guys provide.
So, I acquired an i9060 smartphone and successfully installed CM 11 without the help of my laptop since the usb cable through Odin never worked for me (driver issues on Win10?).
Unfortunately, my phone entered an Android boot loop. And now with a lot of attempt I can't even enter CWM or even charge my smart phone, as it always reboots while trying to charge the battery (it's always drained) or gets stuck during logo before accessing CWM.
I tried to install Samsung drivers, Kies, ABD, Odin to restore the firmware but... nothing seems to recognise this Samsung device. Does anyone had the same problems I'm having now? Any suggestions?
Click to expand...
Click to collapse
Have you considered the possibility that your power button is sticking? Not the part that you touch but the hardware switch behind it?
Do you have USB debugging enabled?
Are you using the stock cable or at least a USB cable with the same number of pins/pinouts?

USB C charging issue

So after getting around to installing the July security patch a couple days ago USB C charging stopped working on my Nexus 6P. If I use a USB A to USB C cable it will charge, but not if I use USB C to USB C. This persisted over multiple cable and chargers.
I tried to wipe the cache but had a problem getting into recovery - I could get to the boot loader but when i select Recovery i get a 'No Command' error screen. (eventually i found out i could power and volume up from this screen to get recovery, but the wipe cache didn't fix anything.)
Then I installed Oreo hoping that would take care of the issue but no luck. Any thoughts? Anybody else get this from the security patch?
Google support has not been particularly helpful.

Hi, i just started getting this issue today. I installed android O yesterday. My original charger which is C to C wont work but C to A will work fine. I've also had my 6p not recognized by my pc. It only charges when i plug it in. Tried different cables, different computers, but I think it might by my charging port. Google support tried, they didn't know what was going on.
But I'm stuck without a custom recovery right now and have lost root access. But phone is working fine. Messed up during flashing, didnt flash custom recovery thinking twrp would be intact but nope. And I cant use ADB to reflash anything cause my stupid 6p wont get recognized by my pc. haha

sonysingh1983 said:
Hi, i just started getting this issue today. I installed android O yesterday. My original charger which is C to C wont work but C to A will work fine. I've also had my 6p not recognized by my pc. It only charges when i plug it in. Tried different cables, different computers, but I think it might by my charging port. Google support tried, they didn't know what was going on.
But I'm stuck without a custom recovery right now and have lost root access. But phone is working fine. Messed up during flashing, didnt flash custom recovery thinking twrp would be intact but nope. And I cant use ADB to reflash anything cause my stupid 6p wont get recognized by my pc. haha
Click to expand...
Click to collapse
haha. use bootloader mode and fastboot flash the TWRP you overwrote when you flashed over recovery. ADB only works in Recovery, but fastboot works in bootloader mode which previously said you can access.