I have to reboot after connecting cable every time when i need to use disk drive or adb option on my phone without reboot it's not working & after reboot it works fine any solution?
Using European Stock Rom & tried too many roms same problem with every rom.
Related
Hey guys,
I just flashed RemICS ROM v1.7 in my phone. Everything is working fine but there's a one problem MY PHONE WON'T CONNECT TO MY PC
Before flashing the ROM I was on stock 2.3.6 DDLF2. I used these instruction to root my phone: http://forum.xda-developers.com/showpost.php?p=30336871&postcount=8
After rooting my device I had some problem with USB CONNECTION but then i just restarted my PC and it started working. But after flashing RemICS the phone won't connect to my pc. There is even no notification in my status bar like it came before. When I connect my phone to my laptop via USB cable there is no change in my phone it just starts charging.
I really love this ROM but I can't have it with this bug please help guys.
(ALSO ONE MORE THING: WHEN I FLASHED THIS ROM THERE WAS NO MUSIC PLAYER APP!! THIS IS STRANGE RIGHT? I THINK THERE MUST BE SOME WRONG WITH MY ZIP FILE. WILL RE-FLASHING WITH A NEW ZIP FILE SOLVE THIS TWO PROBLEMS?)
Has anyone tried the stock 4.3 flashable from tr1gg3r84 on an AT&T one mini? I'm unable to get my computer to detect the phone once its installed. (USB Device Unrecognized) However fastboot and recovery modes still allow my PC to see the phone.
I've restored my stock TWRP I made before attempting anything and it also doesn't allow the device to show up via MTP as it previously did
fuzzmania said:
Has anyone tried the stock 4.3 flashable from tr1gg3r84 on an AT&T one mini? I'm unable to get my computer to detect the phone once its installed. (USB Device Unrecognized) However fastboot and recovery modes still allow my PC to see the phone.
I've restored my stock TWRP I made before attempting anything and it also doesn't allow the device to show up via MTP as it previously did
Click to expand...
Click to collapse
So I've solved my own problem. Using the USB Cable that CAME WITH THE PHONE works. However the cable for my nexus 4 does not, despite it working perfectly fine for months
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
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.
Hello
Few days back I installed CynogenMod on My phone. Everything worked fine for few days and when suddenly I tried changing the APN settings yesterday and it wasn't happening. Then I needed to transfer some files on my phone again it didn't recognize it.
The pc drivers are all fine.
It is just charging and not showing any usb options.
adb is also not recognizing the device.
Tried different USB cables and USB ports? Tried booting TWRP and mounting partitions?
I removed Cynogenmod and there is no os installed. Now adb is not recognizing the device.
When i connect the device to the computer the connection sound comes, but nothing is visible in device manager or in explorer.
can anyone please help?
imgur dot com/a/Y5jGE
No need for adb, use fastboot commands to flash a factory image or use wugfresh nrt.
Try deleting drivers and reinstalling.