Hello,
i tried to update my Nexus 5 to 5.1 by using adb sideload.
First i installed the driver which did not work, i removed them and used an another and the device was recognized after that on windows.
So I started the sideload and it stopped at about 60% and the USB Connection was lost. I can not see the device in the device manager and if i use my linux computer i can not see any new entry if i use 'dmesg'. I used an another USB cable to check if this is broken. I tried to format the cache and it now still boots to the recovery mode.
Can it be that the USB driver in the N5 is broken now?
I wanted to prevent a factory reset, but i dont think that a FR will help here if i can not connect even in the recovery mode
Any suggestions?
Thank you!
wwwiesel said:
Hello,
i tried to update my Nexus 5 to 5.1 by using adb sideload.
First i installed the driver which did not work, i removed them and used an another and the device was recognized after that on windows.
So I started the sideload and it stopped at about 60% and the USB Connection was lost. I can not see the device in the device manager and if i use my linux computer i can not see any new entry if i use 'dmesg'. I used an another USB cable to check if this is broken. I tried to format the cache and it now still boots to the recovery mode.
Can it be that the USB driver in the N5 is broken now?
I wanted to prevent a factory reset, but i dont think that a FR will help here if i can not connect even in the recovery mode
Any suggestions?
Thank you!
Click to expand...
Click to collapse
Hmmm, intermittent ADB occured before attempted sideload falure.
Boot to bootloader and see if you can
fastboot devices
If you can detect the device in fastboot, but still cant ABD, then maybe take a look here http://forum.xda-developers.com/showpost.php?p=59420668&postcount=322
After looking there, if you are absolutely certain that it is not a driver issue, you might be looking at a hardware failure of the charging port.
https://www.youtube.com/watch?v=qqCEXEmcj4Y
If it were me, I'd replace the port and re-attempt ADB sideload.
Related
I have a T-Mobile Nexus S that has a bootloop. Its my friends so I dont know what he did to it. I can get to the bootloader but when I connect it to my computer it won't recognize it. I thought of a driver problem but i can't get past the bootloop to enable usb debugging. It also won't show up in device manager. The phone's usb port works. It will still charge. I just need to get rid of the bootloop. Any help would be greatly appreciated. Thanks!
MAGnum_21 said:
I have a T-Mobile Nexus S that has a bootloop. Its my friends so I dont know what he did to it. I can get to the bootloader but when I connect it to my computer it won't recognize it. I thought of a driver problem but i can't get past the bootloop to enable usb debugging. It also won't show up in device manager. The phone's usb port works. It will still charge. I just need to get rid of the bootloop. Any help would be greatly appreciated. Thanks!
Click to expand...
Click to collapse
If it has a custom recovery, boot into it and wipe data/factory reset.
If it does not, flash a custom recovery. These forums are chockful on guides how to root, flash stuff and fix bootloops.
I looked up how to install recoveries but when i plug in my nexus to my computer it is not recognized. At the bottom of the bootloader screen it says "USB Control Init" and then "USB Control Init End". I do have the proper drivers installed. Is there a fix for this?
Are you sure that you have the correct drivers installed, though?
It's known that people who use Windows have a lot of success with the PDAnet drivers (you can search around here for those), rather then with the standard USB drivers the Google SDK provides.
Greetz
Did you try to run "fastboot devices" in command prompt while it's at fastboot mode and plugged into the PC? What do you see as the result? The guides on XDA should help, but you may also head over to nexusshacks_dot_com for more references.
Sent from my Nexus S using XDA App
With pdanet it requires me to plug in my phone with usb debugging turned on to get the drivers with i cant do because of the bootloop. and when i go into command prompt it says "waiting for device" and won't recognize it. Thanks for the help
Hi Guys,
I've had a few problems with my N5 recently...
If I plug my N5 into my PC via the stock USB cable and boot into the Bootloader (PWR+VOLDN) then it will allow me to flash the original N5 firmware, located here: https://developers.google.com/android/nexus/images, this would indicate to me that there is no issue with the actual devices ability to transfer files via USB connection... Right?
No!
For some strange reason my phone will allow me to push a full factory image to it and will also process any Fastboot commands that are sent to it but as soon as you boot into something like TWRP and try to control the phone's ADB functionality it will not find the device at all! The new MTP option in TWRP 2.8 will allow my computer to see my phone's MTP connection for about 1 second and then will immediately disconnect, the same happens when trying to connect to MTP from within Android too.
USB debugging doesn't show that it is connected when my phone is plugged into my PC and Windows makes the 'device connected' sound and then straight after makes the 'device disconnected' sound...
Any ideas? I am certain that this is an issue with my handset's hardware or software rather than any of the computers or cables... I have tried 3 different cables (including the stock cable) and also three different computers (Windows 8.1 @ Work, Mac OS X @ Work and my own personal PC running Windows 8.1 & Ubuntu @ Home)... All OSs and all computers run into exactly the same issue, device connects briefly and then disconnects.
I have troubleshooted issues relating to the driver. This is not the issue... Device Manager cannot even see the hardware after the disconnect.
Thanks for any help in advance,
Lewis
Also:
-Android does not detect that the USB is charging the device unless the device is booted with the cable attached (if it's not attached before the 'Google' screen then it can't see the USB input at all, within android or TWRP, of course...).
Having the exact same problem. Did you find a solution?
EvilBetty said:
Having the exact same problem. Did you find a solution?
Click to expand...
Click to collapse
It's most likely a driver issue.
Elluel said:
It's most likely a driver issue.
Click to expand...
Click to collapse
Not a driver issue.
3 different Nexus 5s, 5 different workstations. Other two Nexi are fine on all 5 PC's.
1 PC used for ADB forensics, 2 used for ADB development work, one known working for ROM'ing / rooting.
Phone has been factory reset, factory ROM'd from Fastboot. Connects fine on Fastboot. Will not connect on ADB / MTP.
On a fresh PC / phone reboot, the PC will detect the phone for just a second and then it will not reconnect until process is completed.
-EB
What's your adb version?
Went on for about 2 weeks, then suddenly went away on its own. I have no idea what the problem was or the solution. Sorry.
i have a nexus 5 which has stock ROM and blu spark kernel . i locked the bootloader while on the same kernel and again unlocked it . . the phone is bootlooping into twrp and the google logo . in twrp it says unable to mount data . i can access twrp . . i am unable to flash anything . it says unable to mount data/ . please the attachment
All I see is a google logo, not rebooting just staying on the screen. I am pretty sure I deleted the operating system, but I can't seem to get in recovery. What lead up to this was me not being able to connect the device to windows over usb, nothing in device manager, I couldn't even get adb to connect even through twrp sideload. But now I think I caused a whole new issue. I'm just trying to get back to stock rooted lol. Advise?
Edit: unpluged battery and replugged it in, got into recovery now, still having issues connecting so I can flash a rom.
Edit: I have the google usb driver installed from the android sdk. I still can't see my device in windows device manager nor I can't see it through adb. still searching around for a solution.
Edit: I found my old rom still on the device so I was able to install that to actually use the device. I still can't seem to connect to the pc in any way though. I have usb debugging checked drivers installed. Windows just doesn't seem to think a device is there.
s101999 said:
All I see is a google logo, not rebooting just staying on the screen. I am pretty sure I deleted the operating system, but I can't seem to get in recovery. What lead up to this was me not being able to connect the device to windows over usb, nothing in device manager, I couldn't even get adb to connect even through twrp sideload. But now I think I caused a whole new issue. I'm just trying to get back to stock rooted lol. Advise?
Edit: unpluged battery and replugged it in, got into recovery now, still having issues connecting so I can flash a rom.
Edit: I have the google usb driver installed from the android sdk. I still can't see my device in windows device manager nor I can't see it through adb. still searching around for a solution.
Edit: I found my old rom still on the device so I was able to install that to actually use the device. I still can't seem to connect to the pc in any way though. I have usb debugging checked drivers installed. Windows just doesn't seem to think a device is there.
Click to expand...
Click to collapse
Try toggling MTP and/or PHP in USB options.
Your device might show up as an adb device in Device Manager.
Edit:
Some more info here:
http://forum.xda-developers.com/showpost.php?p=57205550&postcount=146
Use a different usb port, different cords, or even a different computer, until you get a pc to recognize the phone.
I had this. It was because not all USB leads have data. Even some that do are wired different. Use the original or HTC work fine with N5 as I've both brands
howard bamber said:
I had this. It was because not all USB leads have data. Even some that do are wired different. Use the original or HTC work fine with N5 as I've both brands
Click to expand...
Click to collapse
Well on my 4th cable, what do you know it works just fine. Feel a little silly but thanks everyone.
I tried to access my phone's internal storage but the phone doesn't show in My Computer. The Portable Device in Device manager says MTP USB device and it has the yellow triangle on it. The Samsung driver is the Android Composite ADB Interface with no triangle. I have debugging on but the MTP device driver always fails whether debugging is on or not. I used Koush's drivers found here on XDA but same old thing. The Portable Device used to show up as A0001 and /or One but now it doesn't and I don't understand how that happened. Can someone enlighten me and perhaps solve this problem? It's been very frustrating as I just spent 13 hours trying to get my phone working (Thanks Heisenberg for fixing) and now another 6 trying to figure this out. Please HELP if you can. Thanks!
kristorm said:
I tried to access my phone's internal storage but the phone doesn't show in My Computer. The Portable Device in Device manager says MTP USB device and it has the yellow triangle on it. The Samsung driver is the Android Composite ADB Interface with no triangle. I have debugging on but the MTP device driver always fails whether debugging is on or not. I used Koush's drivers found here on XDA but same old thing. The Portable Device used to show up as A0001 and /or One but now it doesn't and I don't understand how that happened. Can someone enlighten me and perhaps solve this problem? It's been very frustrating as I just spent 13 hours trying to get my phone working (Thanks Heisenberg for fixing) and now another 6 trying to figure this out. Please HELP if you can. Thanks!
Click to expand...
Click to collapse
Even I had faced this problem on Windows 8. I had installed drivers 4-5 odd times. But later I just flashed CM11S zip via recovery and enabled USB Debugging Mode and it finally got recognized on my laptop.
I was facing many issues with all lollipop ROMs. Hence I reverted back and now everything is working fine.
I, too am using CM11s as Lollipop has too many bugs for me at this time. Maybe I'll try re-flashing CM and see what happens. Thanks for the reply
My question is: How can one flash from recovery when the file that needs to be flashed cannot be sent to the phone because it's not recognized by the computer?
Nevermind...I figured it out and flashed 11S successfully! Everything shows up now on computer. WOOT!
Dear all,
Please Help me. My One plus one is on CM12 official rom (rooted). Problem is when I connect my phone to computer and use ADB it is detected (adb devices: number & devices detected) but when in fastboot (fastboot devices : nothing is detected) I check in my device manager (yellow triangle on android ) My problem is why CAN it be detected when my phone is on but NOT during fastboot.
Necessary checks done : USB debugging, Universal driver, SDK installed, USB driver reinstalled again, tried changing usb ports on computer, tried on 2 laptops)
I am helpless, tried checking on forums can not find the answer.
CalvinVeez said:
Dear all,
Please Help me. My One plus one is on CM12 official rom (rooted). Problem is when I connect my phone to computer and use ADB it is detected (adb devices: number & devices detected) but when in fastboot (fastboot devices : nothing is detected) I check in my device manager (yellow triangle on android ) My problem is why CAN it be detected when my phone is on but NOT during fastboot.
Necessary checks done : USB debugging, Universal driver, SDK installed, USB driver reinstalled again, tried changing usb ports on computer, tried on 2 laptops)
I am helpless, tried checking on forums can not find the answer.
Click to expand...
Click to collapse
Have test to fastboot commands?
In fastboot be unplugged
Write
fastboot reboot
for test
Will answer wait for device
Plug device to test
My pc also does not recognise but work fine
with commands
geowolf1000 said:
Have test to fastboot commands?
In fastboot be unplugged
Write
fastboot reboot
for test
Will answer wait for device
Plug device to test
My pc also does not recognise but work fine
with commands
Click to expand...
Click to collapse
Tried adb reboot bootloader then phone boots into fastboot mode but from here..
is total no connection. Tried checking fastboot devices (nothing), fastboot reboot (waiting)
then i tried as u said unplug & plug in (not recognize) from here adb cannot be written anymore. (no more commands can be typed). Tried others like down loading Pdanet ,force install driver..Nothing works. Thinking ,did I corupt the bootloader while I was rooting it last time.?
I think if something was wrong with bootloader you could not either boot .
Do you use antivirus to pc?
Try without antivirus
What happening the false is from computer
Mine is reverse issue. When in fastboot mode, pc recognizes OPO, but when OPO is normally connected to pc, adb is not working. Its charging and can transfer data through USB, but OPO is not recognized through adb commands. Device Manager too recognizes my OPO only when it is in fastboot mode and not when normally connected via USB for data transfer.
I have a software, through which I can REVERSE TETHER my PC's internet to my mobile via USB. Because my OPO is not recognized via USB in normal mode, I can't do that. Any idea, what's wrong with my OPO.
(I have installed Android SDK and google usb drivers, for my OPO to work in fastboot. I have rooted. My pc runs on win7)
mrsureshisha said:
Mine is reverse issue. When in fastboot mode, pc recognizes OPO, but when OPO is normally connected to pc, adb is not working. Its charging and can transfer data through USB, but OPO is not recognized through adb commands. Device Manager too recognizes my OPO only when it is in fastboot mode and not when normally connected via USB for data transfer.
I have a software, through which I can REVERSE TETHER my PC's internet to my mobile via USB. Because my OPO is not recognized via USB in normal mode, I can't do that. Any idea, what's wrong with my OPO.
(I have installed Android SDK and google usb drivers, for my OPO to work in fastboot. I have rooted. My pc runs on win7)
Click to expand...
Click to collapse
Install pdanet+ for win