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
Related
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!
This is for my brother's phone...
He tried 3 different computers, downloaded the latest samsung USB drivers on all 3, tried any and all USB ports on each computer. It is not recognized at all. The phone charges and that's about it. He's even tried a few different USB cables.
He's on CM 10.2 now and needs to go back to stock to upgrade to a new phone.
I had him try flashing a stock-rooted ROM from recovery, and it will not work. I don't know what error he gets off-hand, but he says that it gets denied.
Help please!
bryank930 said:
This is for my brother's phone...
He tried 3 different computers, downloaded the latest samsung USB drivers on all 3, tried any and all USB ports on each computer. It is not recognized at all. The phone charges and that's about it. He's even tried a few different USB cables.
He's on CM 10.2 now and needs to go back to stock to upgrade to a new phone.
I had him try flashing a stock-rooted ROM from recovery, and it will not work. I don't know what error he gets off-hand, but he says that it gets denied.
Help please!
Click to expand...
Click to collapse
Not sure about stock but I can give you something to try under CM 10.2.. Go into Settings -> Storage -> (Click three dot menu in upper right) -> USB Computer Connection -> Make sure Media Device (MTP) is checked.
He was able to get it back to stock with mobile odin. Now USB works. Weird.
Thanks!
He was able to get it back to stock with mobile odin. Now USB works. Weird.
Thanks!
Hi Guys,,, I got Tf300Tg....I just updated it to new firmware ww 10.6.310..Now there is Stock recovery,,,,Bootloader is showing "Unlocked Device".
Now problem is that USB is not working even i have purchased the new cable,,,but my pc is not detecting my Asus TF300tg. However charging is ok.
Now i need to root it,,obviously rooting requires TWRP and specially USB pc link......
Is there any way to Install TWRP Without PC support?????????????????
jaffer707 said:
Hi Guys,,, I got Tf300Tg....I just updated it to new firmware ww 10.6.310..Now there is Stock recovery,,,,Bootloader is showing "Unlocked Device".
Now problem is that USB is not working even i have purchased the new cable,,,but my pc is not detecting my Asus TF300tg. However charging is ok.
Now i need to root it,,obviously rooting requires TWRP and specially USB pc link......
Is there any way to Install TWRP Without PC support?????????????????
Click to expand...
Click to collapse
If you root with motochopper you can use Terminal Emulator app on the tablet to install TWRP. You can also try installing the Universal Naked Drivers for ADB and fastboot to connect with your computer.
Well I am aware of all these methods but problem is in My tablet's USB/Charging slot, may there is some pin damaged that is why USB in not detecting,,,,Even i have every thing in my PC like Universal naked Drivers,,,Android SDK,,Motochopper Etc, Not only This couple of Months ago I have "unbricked" my Asus TF300tg using Fastboot Commands and Flashed New Blob,,,,, Everything was working well now i have decided to Root it but TWRP was replaced by the Stock Recovery....That is why is asked whether there is any way to root it through any App or WIFI...
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.