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
Related
Essentially What's wrong:
My phone is stuck in a boot loop, computers won't recognize the usb connection, and my sd card won't mount. My SD card is, however, recognizable if I plug it directly to my computer using an adapter.
What Happened:
I rooted my phone using CWM and Odin in order to remove bloatware and enable tethering. After enabling tethering, my computer stopped recognizing my phone. I tried everything to fix it including factory resetting my phone, formatting cache, data, system, and sd card all under the CWM boot menu (hold volup+home+power). Soon afterwards, my phone got stuck in a boot loop. On startup, it hangs on the white "Samsung" logo. While trying to fix the issue, I noticed that my sd card won't mount.
What I've tried:
I've tried this method, but it requires that I either have usb access or access to my phone. I've tried reinstalling the Samsung driver fifteen times. I've tried formatting the SD card in my computer. I've tried using different computers. I've tried using different usb cords. I've tried clearing the registry on my computer, I've tried scouring Google and these forums for a solution. Maybe I'm blind and missed something.
What I'm trying to do:
The way I see it, I need to figure out a way to flash the stock rom back to my phone. In order to do this, I need to get my usb to recognize. If I can do this, the rest is easy. Does anyone has any ideas on what can be done?
Cerei said:
Essentially What's wrong:
My phone is stuck in a boot loop, computers won't recognize the usb connection, and my sd card won't mount. My SD card is, however, recognizable if I plug it directly to my computer using an adapter.
What Happened:
I rooted my phone using CWM and Odin in order to remove bloatware and enable tethering. After enabling tethering, my computer stopped recognizing my phone. I tried everything to fix it including factory resetting my phone, formatting cache, data, system, and sd card all under the CWM boot menu (hold volup+home+power). Soon afterwards, my phone got stuck in a boot loop. On startup, it hangs on the white "Samsung" logo. While trying to fix the issue, I noticed that my sd card won't mount.
What I've tried:
I've tried this method, but it requires that I either have usb access or access to my phone. I've tried reinstalling the Samsung driver fifteen times. I've tried formatting the SD card in my computer. I've tried using different computers. I've tried using different usb cords. I've tried clearing the registry on my computer, I've tried scouring Google and these forums for a solution. Maybe I'm blind and missed something.
What I'm trying to do:
The way I see it, I need to figure out a way to flash the stock rom back to my phone. In order to do this, I need to get my usb to recognize. If I can do this, the rest is easy. Does anyone has any ideas on what can be done?
Click to expand...
Click to collapse
The phone not connecting: I have had this issue before. If you go into the device manager on the computer and show all devices, you can remove all the samsung usb drivers and the root usb drivers from the computer. Reboot the computer and leave the phone unplugged. it will reinstall the main drivers. reboot the phone and hold the buttons to enter recovery, it should still work even while stuck on samsung logo. connect the phone to pc and it should reinstall the drivers and connect properly.
mromblad said:
The phone not connecting: I have had this issue before. If you go into the device manager on the computer and show all devices, you can remove all the samsung usb drivers and the root usb drivers from the computer. Reboot the computer and leave the phone unplugged. it will reinstall the main drivers. reboot the phone and hold the buttons to enter recovery, it should still work even while stuck on samsung logo. connect the phone to pc and it should reinstall the drivers and connect properly.
Click to expand...
Click to collapse
Do you remember at all the name of the drivers that need to be uninstalled? When I plug in my Droid Charge, the computer attempts to install the drivers but it always fails. Under device manager I will then see "unknown deviced" labeled with a yellow exclamation mark. I uninstall that, then plug the phone back in but the same error occurs.
If there are other drivers that I need to uninstall, then I don't know what they're called. None of the devices in the manager say anything referring to samsung.
Cerei said:
Do you remember at all the name of the drivers that need to be uninstalled? When I plug in my Droid Charge, the computer attempts to install the drivers but it always fails. Under device manager I will then see "unknown deviced" labeled with a yellow exclamation mark. I uninstall that, then plug the phone back in but the same error occurs.
If there are other drivers that I need to uninstall, then I don't know what they're called. None of the devices in the manager say anything referring to samsung.
Click to expand...
Click to collapse
go to device manager and choose: view >> show hidden devices
then under the usb drivers look for and uninstall the SAMSUNG if any and uninstall the : Generic USB Hub if any, and uninstall USB Root Hub if any, and reboot computer.
THANK YOU
How don't know how I managed to miss this when trying to fix this over the past week+, but it worked. Getting rid of those root usb devices got my computer to recognize my phone, then I was able to easily use Odin to boot it back to the stock rom. Thank you so much. Crazy how such a simple solution can be the answer.
mromblad said:
go to device manager and choose: view >> show hidden devices
then under the usb drivers look for and uninstall the SAMSUNG if any and uninstall the : Generic USB Hub if any, and uninstall USB Root Hub if any, and reboot computer.
Click to expand...
Click to collapse
Hello. im having the same problem and need help. I find 2 root hubs in the drivers and uninstall them and restart computer, but it installs again the 2 root hubs after restarting computer i press (+ and poverbutton on my galaxy s plus) and then press menu button to go to the settings.. then i plug it in but it still dont recognizes the g disk.. after i reboot the phone it just shows for a little while but i cant acces it... please some advice... THANKS!"
hannu123 said:
Hello. im having the same problem and need help. I find 2 root hubs in the drivers and uninstall them and restart computer, but it installs again the 2 root hubs after restarting computer i press (+ and poverbutton on my galaxy s plus) and then press menu button to go to the settings.. then i plug it in but it still dont recognizes the g disk.. after i reboot the phone it just shows for a little while but i cant acces it... please some advice... THANKS!"
Click to expand...
Click to collapse
hi there,
i am havin the same problem. i just wanted to know if you managed to get a solution? i am desperate. please assist.
Hi there
I'm having same problem with celkon a20. It strucks on erasing data not connecting to PC....please reply me
mromblad said:
The phone not connecting: I have had this issue before. If you go into the device manager on the computer and show all devices, you can remove all the samsung usb drivers and the root usb drivers from the computer. Reboot the computer and leave the phone unplugged. it will reinstall the main drivers. reboot the phone and hold the buttons to enter recovery, it should still work even while stuck on samsung logo. connect the phone to pc and it should reinstall the drivers and connect properly.
Click to expand...
Click to collapse
Hello, have tried uninstalling the USB drivers but Windows 10 re-installs these drivers upon restart. My Samsung SM-N750 is still not detected on via USB, and therefore cannot proceed with Odin firmware flash. Do you have any other suggestions? Many thanks.
I'm wondering if anyone has run into this problem before?
I'm trying to unlock the bootloader on my friend's Photon Q, I downloaded the SDK and installed the Motorola drivers. But when I put his phone into Fastboot mode, the "fastboot oem get_unlock_data" command does not work and CMD just says waiting for devices.
Yes I'm shift+right clicking on the platform-tools folder in the SDK to run the Command Prompt and I did download the correct Fastboot file. The command "adb devices" shows nothing when his phone is plugged in, but it shows my own phone (A Motorola Droid Bionic) when it's plugged into the USB cable. RSD Lite also recognizes both phones when powered on or in Fastboot mode.
I have no idea what to do at this point, we just need to get that unlock data to plug into the Moto site. Would it be possible to use someone else's unlock key or is each one randomized individually for the device? Or would that even work because my computer can't do the command for the unlock data, so maybe it couldn't push the unlock key onto the phone?
quick thought: did you enable usb debugging on the device?
edit: i guess that wouldn't make any difference in fastboot mode...
anyway, yeah, i'm pretty sure each device has it's own unique code. it's odd that fastboot recognizes the device, but the command isn't working. i bet you will get it somehow tho. a similar thing actually does happen to me sometimes, and in my case, it is because my usb ports are going bad and the computer loses connection with the phone.
Man nobody has anything eh? That's a crying shame. I tried using a different computer and went through the same course and still nothing.
I did try USB debugging on and off on both machines, didn't change a thing.
In order for the drivers (and therefore adb) to pick up the phone, I needed usb debugging *and* the phone not to be in charge only mode. Maybe that will help?
If not, when you reboot to fastboot and connect the cable, look at the devices installing list (if win 7) or device manager, and confirm the pc sees the fastboot device. If not you may need to reinstall the driver. Strange I know, but I needed to after getting my unlock data, holding off on unlocking due to the warranty voiding note, then trying again a couple days later where it wouldn't recognize. Seems to be finicky drivers to match a finicky device. But I do love this keyboard lol...
Sent from my XT897 using Tapatalk 2
We've only ever tried it in MTP mode and USB debugging enabled. This is day three of plugging it in and pulling it out and still no go. This is a royal pain, that is for sure.
Download Motorola Device Manager from the website, install, plug in phone. Place the phone into mass storage mode WITHOUT debugging enabled, then other modes, then back into bootloader mode then into fastboot mode. This will install EVERY driver, I didn't see that as one of the things tried.
Once you are in those modes, Android ADB device driver will install.
Hope that helps...
Sent from my XT897 using xda premium
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.
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!