Hello everyone,
I have an un-rooted and unlocked boot-loader Nexus S 4G that currently only charges by USB cable and multiple computers do not acknowledged that the device is plugged in. I've tried multiple usb cables, and have been working on this issue for the past couple of days. It seems to be that the USB port may be partially working, since it still can charge, but I'm unable to run any fastboot or adb commands. It currently runs the Android 4.0.4 (IMM76D) factory image. I do not have clockworkmod recovery installed and I believe the original recovery may have not been correctly flashed as it shows an Android with an exclamation point when I try to enter into recovery from fastboot.
My questions:
1. Is it possible to root this device by using terminal emulator and copying the files needed through dropbox/wifi? Is there an ICS 4.0.4 exploit that may work? (I can also install SSHDroid)
2. Is there a way to run a script from within Android that will automatically run fastboot commands while in fastboot mode?
3. Is there a possible fix for the usb port for it to be recognized?
Thank you for your help!
Related
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.
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
trying to install lineage and i cant even make it past fasboot device when in fastboot. im using a laptop that only has usb 3 ports has someone figured out how to do it from usb 3 ports?
If your device is running Android 11 or above version, then you may try out the new Wireless Debugging Feature to execute ADB & Fastboot Commands wirelessly.