Windows 7 x64
Galaxy Nexus i515, BROKEN SCREEN, USB DEBUGGING WAS NOT TURNED ON. The phone is completely stock I just turned it on and used it until I broke my screen. Screen lock is on.
I have been trying to access my phone, using Fastboot, to wipe it before I send it in for warranty. I can not seem to do this at all. It seems that I can not install the drivers because I have not enabled USB debugging. Is this true? I have been following this guide : http://www.teamandroid.com/2012/07/30/how-to-set-up-adb-fastboot-with-android-sdk/2/ When i go to manually install the drivers, from SDK, I get, "The folder you specified does not contain a compatible software driver for your device. If the folder contains a driver, make sure that it is designed to work with Windows for x6-based systems." I then tried the driver from Samsung and got the same response.
So then I hold VOL+ _ VOL- and Power and tried to install the drivers for Fastboot with the same outcome as above. Also when I boot in Fastboot mode the drivers that are installed make my phone a modem. The driver is called, "SAMSUNG Mobile USB Modem." I can not get this to change.
So to summarize I can not get the ADB Drivers to install, because I do not have USB Debugging enabled, that in return will not allow me to install Fastboot Drivers because when I plug the phone in the computer sees it as a Modem.
Any suggestions? I am just trying to erase the info on my phone I have given up all hope of recovering any data.
Thanks,
qualm
USB debugging drivers/interface have nothing to do with fastboot drivers/interface. What's a screen lock?
a manta wrote this.
beekay201 said:
USB debugging drivers/interface have nothing to do with fastboot drivers/interface. What's a screen lock?
a manta wrote this.
Click to expand...
Click to collapse
I meant a screen pattern lock. When you wake up the screen you have to connect the dots in a certain pattern before your screen unlocks and you can use the phone.
As far as, USB debugging drivers/interface having nothing to do with fastboot drivers/interface, then what am I doing wrong? I can not get my computer to see my phone as an android device.
_qualm_ said:
I meant a screen pattern lock. When you wake up the screen you have to connect the dots in a certain pattern before your screen unlocks and you can use the phone.
As far as, USB debugging drivers/interface having nothing to do with fastboot drivers/interface, then what am I doing wrong? I can not get my computer to see my phone as an android device.
Click to expand...
Click to collapse
I know what a screen pattern lock is.
Uninstall all drivers, reboot pc.
Assuming device is off: press power+vol up+vol down, until you feel the vibration. Wait 2 secs or so. Device will be in fastboot mode.
Read this thread, i say again, READ this thread, obviously start with the first post! - http://forum.xda-developers.com/showthread.php?t=1812959
Thanks for the link. I read it and followed instructions for installing the drivers. Here is what I did:
1.Uninstalled all drivers
2.Rebooted my PC
3.Downloaded these Drivers, as suggested: http://forum.xda-developers.com/showthread.php?t=1379875
4.Followed these instructions, on how to install the driver without windows trying to find one automatically: http://forum.xda-developers.com/showpost.php?p=29044502&postcount=735
Everything seemed to go well under the Device Manager, when I plug my phone in in fastboot mode, it shows Android Phone -> Samsung Android Interface. This is way better than what I had before, when it was showing up as a Modem. Now when I try to use fastboot.exe and I type "fastboot devices" nothing shows up. I reset the computer and replugged in my device, in fastboot, and the same thing nothing shows up in fastboot.
Thanks for you help.
Did you miss the part about having to feed windows the same driver again, when connecting the device for the first time, in FASTBOOT MODE?
a maguro wrote this.
beekay201 said:
Did you miss the part about having to feed windows the same driver again, when connecting the device for the first time, in FASTBOOT MODE?
a maguro wrote this.
Click to expand...
Click to collapse
Not sure if I understand what your asking.
I followed all of the steps here: http://forum.xda-developers.com/showpost.php?p=29044502&postcount=735 I connected the phone booted normally and let windows find a driver so that the driver reads Portable Devices -> Galaxy Nexus. Then I unplugged the Nexus and booted it in fastboot mode and plugged it in. Next I followed the directions to install the Universal_Naked_Driver, in fastboot mode. I can not install the driver for ADB because I can not enable USB Debugging with my broken screen.
Thanks Again.
Why is it so difficult for people to understand that USB debugging has nothing to do with anything outside the booted OS?
Sent from my Galaxy Nexus
W8 a sec, do you even have your bootloader unlocked???
You said you're running stock, so that should have been my first question, because to unlock your bootloader through the usual way, you need to confirm a dialog on the device... which in your case, doesn't have a working screen.
_qualm_ said:
Not sure if I understand what your asking.
I followed all of the steps here: http://forum.xda-developers.com/showpost.php?p=29044502&postcount=735 I connected the phone booted normally and let windows find a driver so that the driver reads Portable Devices -> Galaxy Nexus. Then I unplugged the Nexus and booted it in fastboot mode and plugged it in. Next I followed the directions to install the Universal_Naked_Driver, in fastboot mode. I can not install the driver for ADB because I can not enable USB Debugging with my broken screen.
Thanks Again.
Click to expand...
Click to collapse
....
Lets see:
That post shows how it's done, correctly. (I think, from what i've read)
pay attention to part 3)
3)
NOTE:
- The method described here can be used to install the "Samsung Galaxy Nexus ADB Interface" driver as well as the "Samsung Galaxy Nexus Bootloader Interface" driver.
- Differences between the two procedures. One is done with the phone booted up normally and "USB Debugging" is enabled, and the other is done when the phone is in fastboot. I will cover the "USB Debugging" part here.
Click to expand...
Click to collapse
then...
We will now install the two drivers that efrant talked about in his post.
A) (FOR ADB - WHEN RUNNING ANDROID OS):
Enable USB debugging on your device
- Goto Settings > Developer Options > Check "USB Debugging"
- Connect device, manually update driver to Naked driver by 1wayjohny, done. On 4.2 and above, you'll need to confirm that you accept the host's (your pc) RSA key.
B) (FOR FASTBOOT - WHEN RUNNING FASTBOOT MODE)
boot into fastboot mode - power off phone and hold vol up + vol down + power
Click to expand...
Click to collapse
Both for A) and B), you need to do the "Update drivers manually" part!
Right now, your only option is B), that is to use fastboot to either:
- Flash stock images.
- To get your data back, boot a custom recovery (which won't require the RSA key confirmation for ADB) from fastboot, then use ADB to pull your /sdcard/ or whatever.
Pirateghost said:
Why is it so difficult for people to understand that USB debugging has nothing to do with anything outside the booted OS?
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
I am learning this ^. I am having trouble getting my computer to see my phone, in fastboot mode. All of the instructions that I have read start with installing drivers for ADB, which requires the phone to be USB debugging mode, and then the drivers for fastboot. So I thought my trouble was, since I can not install the drivers for ADB, and that I was having trouble with all of my drivers, that it was probably the fact that my phone can not be put into USB debugging mode. I now realize that USB debugging has nothing to do with fastboot, as fastboot is before the OS is booted. I am still just having trouble with my fastboot driver and seeing my phone with fastboot.exe.
beekay201 said:
W8 a sec, do you even have your bootloader unlocked???
Both for A) and B), you need to do the "Update drivers manually" part!
Right now, your only option is B), that is to use fastboot to either:
- Flash stock images.
- To get your data back, boot a custom recovery (which won't require the RSA key confirmation for ADB) from fastboot, then use ADB to pull your /sdcard/ or whatever.
Click to expand...
Click to collapse
No my bootloader is not unlocked. Is this the reason that my phone is not detected by fastboot.exe? Do I need to unlock my bootloader?
I have been trying option B, as I know this is my only option. I have been doing the "Update drivers manually" part I even tried on another PC with windows 7, to no avail. What ever I seem to do I can not see my device in fastboot.exe.
_qualm_ said:
No my bootloader is not unlocked. Is this the reason that my phone is not detected by fastboot.exe? Do I need to unlock my bootloader?
I have been trying option B, as I know this is my only option. I have been doing the "Update drivers manually" part I even tried on another PC with windows 7, to no avail. What ever I seem to do I can not see my device in fastboot.exe.
Click to expand...
Click to collapse
No. Fastboot should be able to see your device if the proper drivers are installed. Fastboot is REQUIRED to unlock the bootloader
Sent from my Galaxy Nexus
Pirateghost said:
No. Fastboot should be able to see your device if the proper drivers are installed. Fastboot is REQUIRED to unlock the bootloader
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
If you used odin to flash something, that will unlock the bootloader. Flashing a section of edited param using OMAP flash will also unlock the bootloader.
Beamed from my Maguro.
I also have the same problem with my galaxy C5.
_qualm_ said:
No my bootloader is not unlocked. Is this the reason that my phone is not detected by fastboot.exe? Do I need to unlock my bootloader?
I have been trying option B, as I know this is my only option. I have been doing the "Update drivers manually" part I even tried on another PC with windows 7, to no avail. What ever I seem to do I can not see my device in fastboot.exe.
Click to expand...
Click to collapse
My galaxy C5 is also not recognized as a bootloader interface while in fastboot mode, after installing all the drivers correctly. Samsung usb driver v1.5.63.0 makes the changes i think, and it makes it as a modem instead of bootloader. maybe the solution is i have to manually update the driver of that modem into bootloader, right click on the modem in device manager and change it's driver into bootloader of your phone, maybe it works. I will try it this way.
Let me know if this solution has worked for someone.
Thanks
Soft bricked(?) my phone. I've got no ROM installed and No ROM/backup on my SD card.my laptop doesnt detect my phone even after re-installing USB device driver (error MTP USB device).
Now I want to use ADB Sideload to push a ROM into my SD card in recovery.
Unfortunately it seems like USB Debugging isn't turned on, it can't find my device.
Is there anyway to turn it on in recovery/ TWRP? any other way to bring back to life?
blinkjona said:
Soft bricked(?) my phone. I've got no ROM installed and No ROM/backup on my SD card.my laptop doesnt detect my phone even after re-installing USB device driver (error MTP USB device).
Now I want to use ADB Sideload to push a ROM into my SD card in recovery.
Unfortunately it seems like USB Debugging isn't turned on, it can't find my device.
Is there anyway to turn it on in recovery/ TWRP? any other way to bring back to life?
Click to expand...
Click to collapse
Maybe fastboot. Try this to keep your data: http://forum.xda-developers.com/showthread.php?t=2377307
Sent from my Galaxy Nexus using XDA Premium HD app
mrgnex said:
Maybe fastboot. Try this to keep your data: http://forum.xda-developers.com/showthread.php?t=2377307
Click to expand...
Click to collapse
Thanks, problem is USB debugging is not enabled :crying:
I think your problem is incorrect drivers, uninstall your current driver and install this
blinkjona said:
Thanks, problem is USB debugging is not enabled :crying:
Click to expand...
Click to collapse
fastboot has nothing to do with ADB.
thanks a bunch
there's a return to stock thread in general. use that.
I have an HTC One M8 by T-Mobile, running the latest firmware, unlocked, rooted and on Android 5.0 Lollipop with the stock recovery. (I put the stock recovery back on because I had no need for the custom at the time and charging would bring me through the recovery and be real annoying).
I had no problem doing all of this but now (a few weeks later) I need to get the custom recovery back on in order to flash a new ROM.
Problem is, I'm connecting my phone to my computer and I can't get ADB to connect, HTC Sync Manager shows there's no device connected and windows explorer only shows a new CD Drive connected and mounted on (F that doesn't work and does not act as a storage platform for my phone.
What I have tried:
Disabling USB Debugging
Restarting Phone
Re-enabling USB Debugging
Un-installing HTC Sync Manager
Force installing "androidusb.INF"
uninstalling HTC Sync Manager, unplugging phone, disabling usb debugging, turning off phone and then going back through again, installing, plugging in turning on and enabling.
Really puzzled here, need to connect to ADB to flash custom recovery to go back to my stock ROM.
Try using the generic Android MTP drivers in Device manager. Of course you could also check all the basics as well.
Try a different port or a different cable. Try to kill the adb server and restart it. Can also try revoking the USB permissions and accepting again when prompted on the device.
Though you don't really need adb to flash the recovery, it needs to work in Fastboot mode. ADB will only work in a running OS or in a recovery, fastboot of course from fastboot mode, which is what you'll need in order to flash the recovery. You won't need USB debugging enabled for it either.
Try some of the stuff above, especially if maybe it's a cable or port issue.
I realize you may find a solution before even considering the option below ⬇
http://forum.xda-developers.com/showthread.php?t=2965030
If you have an extra rooted device and get the cable coming you will never have to worry about troubleshooting drivers again considering after an ruu or a conversion you will go through the possible issues of drivers more than once
I've changed my CID,MID,flashed recovery with this method.
Being S-OFF I've not needed to try an ruu through ruu mode but would guarantee it will do the job
I flashed a custom rom and now my PC does not recognize my phone. I can't transfer files or fastboot to the phone from the PC.
I wanted to go back to stock, but when I went to flash-all, it stalls at waiting for device.
Not sure what happened, any help solving this would be appreciated.
It's not the drivers in the PC, it's something that happened within the phone.
Gordietm said:
I flashed a custom rom and now my PC does not recognize my phone. I can't transfer files or fastboot to the phone from the PC.
I wanted to go back to stock, but when I went to flash-all, it stalls at waiting for device.
Not sure what happened, any help solving this would be appreciated.
It's not the drivers in the PC, it's something that happened within the phone.
Click to expand...
Click to collapse
Deleted
Gordietm said:
I flashed a custom rom and now my PC does not recognize my phone. I can't transfer files or fastboot to the phone from the PC.
I wanted to go back to stock, but when I went to flash-all, it stalls at waiting for device. Not sure what happened, any help solving this would be appreciated. It's not the drivers in the PC, it's something that happened within the phone.
Click to expand...
Click to collapse
You should also try a different A-C cable. Do you still have a custom recovery or stock? If so you can use adb to push/pull files to the phone and try "update via adb". Have you done a full factory reset?
It's not the cable, I've a few different ones. I can't use adb, because the PC doesn't recognize that Mr phone is connected.
Gordietm said:
It's not the cable, I've a few different ones. I can't use adb, because the PC doesn't recognize that Mr phone is connected.
Click to expand...
Click to collapse
Have you enabled usb debugging , reinstalled the Google usb drivers, is the adb folder all right (maybe re-downlaod an re-install).
gee2012 said:
Have you enabled usb debugging , reinstalled the Google usb drivers, is the adb folder all right (maybe re-downlaod an re-install).
Click to expand...
Click to collapse
I have enabled USB debugging, the adb floder is fine. I still have to try updating the drivers, haven't done that yet. Thanks
Gordietm said:
I have enabled USB debugging, the adb floder is fine. I still have to try updating the drivers, haven't done that yet. Thanks
Click to expand...
Click to collapse
Turns out that restating the PC did the trick.
Everything works now. Thanks for the help.
Fixed- ran the 15 second ADB and fastboot installer
I updated to the latest verion of windows and now ADB and fastboot do not recognize device. I dowloded the phone drivers updated to a current version of ADB and fastboot from google. I have have developer options on and USB debugging. I also tried on another computer and same issue. I'm not getting the pop-up that says allow this computer to use USB debugging which I think might be the problem. Any ideas?
jdh10475 said:
Fixed- ran the 15 second ADB and fastboot installer
I updated to the latest verion of windows and now ADB and fastboot do not recognize device. I dowloded the phone drivers updated to a current version of ADB and fastboot from google. I have have developer options on and USB debugging. I also tried on another computer and same issue. I'm not getting the pop-up that says allow this computer to use USB debugging which I think might be the problem. Any ideas?
Click to expand...
Click to collapse
Might be a little overkill here but unplug your phone from your pc, uninstall moto drivers, reboot, reinstall moto drivers and reboot. Meanwhile in developer settings in your phone, revoke usb debugging authorization and turn usb debugging off.
Once all that is done replug your phone let the drivers install, then toggle usb debugging back on. Hopefully it'll reinstall a fresh adb driver and prompt for authorization.