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
Related
Good morning
I tried updating the rom on my htc sensation and to do so i usualy have to flash the boot.img aswell to get rid of the infinite startup screen
but my device doesnt work anymore when im in the bootloader in fastboot mode on windows i get a message usb device malfunctioned
i know the usb works as when im booted up in my (previous rom) i can still send data from my pc to my phone over the usb cable
any ideas?
regards
frayful said:
Good morning
I tried updating the rom on my htc sensation and to do so i usualy have to flash the boot.img aswell to get rid of the infinite startup screen
but my device doesnt work anymore when im in the bootloader in fastboot mode on windows i get a message usb device malfunctioned
i know the usb works as when im booted up in my (previous rom) i can still send data from my pc to my phone over the usb cable
any ideas?
regards
Click to expand...
Click to collapse
Might be a driver issue. Can you try a different USB port?
Sent from my HTC Desire S using Tapatalk
Heya i tried different usb ports tried different cables and tried it on 2 other laptops aswell all gave the error usb device not recognized, device malfunctioned after like 10 seconds after being connected
regards
Which Windows do you have?
tested on 3 windows 8.1 pc's
frayful said:
tested on 3 windows 8.1 pc's
Click to expand...
Click to collapse
maybe you are facing now connectivity issues with w8
write in the search box "how to set up adb/fastboot in windows 8"
check some threads and see if you have any success
HTC One S4
Alright, I've looked into this for quite a bit. There's 3 things I've found:
- Change charging cable (done)
- Install HTC Sync (done)
- The USB connector port on the phone could be broken (hope not)
Anything else I can look into?
- Rom is ViperOneS JB
I believe I've tried ADB devices, I haven't really done any sort of ROM changing so I've forgotten much of this, but I believe ADB devices doesn't show any available devices.
EDIT: Another thing to add is that the PC recognises the phone when in CWM but doesn't mount the device such that I can access the files.
EDIT 2: I tried Fastboot USB, only comes up as Fastboot AC :/
Another thing: I charge my phone using a dodgy eBay USB cable, I didn't use this for connecting to the PC but whenever I plug in the charger the phone says to unlock in order to access files on the PC (as it would if my PC detected the phone).
Sorry to sound desperate but I need a response, fast!
Uninstal htc sync.
Instal latest HTC drivers & adb.
PS
Windows 8.1 have a problem with driver.
It says the device connected to the PC has "malfunctioned". I deleted HTC Sync, haven't updated ADB cos I can't remember the link.
Installed latest adb, no avail.
http://forum.xda-developers.com/showthread.php?t=2217396
http://dottech.org/21534/how-to-ins...ows-computer-for-use-with-your-android-phone/
I already have those.
Anyone at all know anything?
Bump :/
It does say unlock to access phone storage on computer and then when I do, nothing happens.
I have the same issue, and I've tried to access my One S from multiple computers (different usb ports, 2.0, hub, et.c., Windows, OSX, Linux) and nothing seems to do the trick. I'm completely locked out from switch recovery (TWRP installed but can't be accessed, possibly due to old 1.13 hboot).
Sorry not to be able to offer any help, just that I doubt it'll be fixed in your case by switching computers/os/ports et.c. since I've tried most of that already, and I must've been through 10-12 different usb cables by now.
Just about ready to ditch this phone.
Flash the original recovery.
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.
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.
Afternoon all,
Have been out of the rom'ing scene for a while...
I have a number of devices (Galaxy Tab 2 10.1 and Nexus 7 2012, to be exact), that I want to flash a new ROM onto (the Tab's stuck in a boot loop, the N7's due for Dirty Unicorns Nougat Rom).
All pretty straight forward - I've done it in the past - BUT...
Can I get Windows 10 to even *see* new hardware's been connected, let alone recognize it?
Can I fook
To confirm, I plug the USB between the PC and the device, and all that shows this is connected is that the device realises it's being charged, no "ding ding" from Windows, no USB confirmation from the device...
Both devices have USB Debugging enabled.
Have tried different USB cables
Have tried different USB ports
Have tried - many! - different USB drivers, including that from both Asus and Google's own dev kit.
Have ADB installed, "adb devices" shows no devices (blank).
The thing that's really pi**ing me off is that this is such a basic thing to be stuck by, I really cant figure out what I'm missing!
Any help appreciated gents...
cy80rg said:
Afternoon all,
Have been out of the rom'ing scene for a while...
I have a number of devices (Galaxy Tab 2 10.1 and Nexus 7 2012, to be exact), that I want to flash a new ROM onto (the Tab's stuck in a boot loop, the N7's due for Dirty Unicorns Nougat Rom).
All pretty straight forward - I've done it in the past - BUT...
Can I get Windows 10 to even *see* new hardware's been connected, let alone recognize it?
Can I fook
To confirm, I plug the USB between the PC and the device, and all that shows this is connected is that the device realises it's being charged, no "ding ding" from Windows, no USB confirmation from the device...
Both devices have USB Debugging enabled.
Have tried different USB cables
Have tried different USB ports
Have tried - many! - different USB drivers, including that from both Asus and Google's own dev kit.
Have ADB installed, "adb devices" shows no devices (blank).
The thing that's really pi**ing me off is that this is such a basic thing to be stuck by, I really cant figure out what I'm missing!
Any help appreciated gents...
Click to expand...
Click to collapse
Windows 10 is very buggy. Download lobit Drive Booster to see if you are missing any driver for your pc. Your pc is probably missing some drivers for the motherborad or outdated. If this does not work, clean install windows 10. Let windows 10 install all the drivers for you while it is installing. Best method. Good internet connection required.
its damn easy,the problem lies in Windows,just boot into repairmodus/system recovery its the blue menu for troubleshooting,there u choose Startup Setting and there u choose number 7,thats for disabling the digital driver signature checking,after the reboot all is fine,boot note u must do it everytime new after reboot.
please next ask and post in right section,thanx.
Nvidia USB driver (ADB and Fastboot) is the only one that works for me
https://developer.nvidia.com/shield-open-source