Whenever i boot to the bootloader, then plug phone into computer, it doesn't change to fastboot usb mode
Are you using the usb cable that came with the phone?
If you plug in the phone first, can you adb reboot to bootloader?
Is usb debugging enabled in developer options?
If USB debugging is on in your settings than wile in hboot just volume up or down to reboot fastboot.
It's done that for me and that's what I did
Usb debugging has no effect in the boot loader.
Can't you just select fastboot from the boot loader menu?
ashyx said:
Usb debugging has no effect in the boot loader.
Click to expand...
Click to collapse
I was actually just reading on another post, USB Debugging is needed for adb, but not fastboot.
Never really thought about it that much, I had assumed like jball that you need USB Debugging for both adb and fastboot.
redpoint73 said:
I was actually just reading on another post, USB Debugging is needed for adb, but not fastboot.
Never really thought about it that much, I had assumed like jball that you need USB Debugging for both adb and fastboot.
Click to expand...
Click to collapse
Usb debugging has no effect outside of the os. Adb can be used in recovery regardless of usb debugging.
ashyx said:
Usb debugging has no effect outside of the os. Adb can be used in recovery regardless of usb debugging.
Click to expand...
Click to collapse
Well look at that. For some reason, I thought you can use adb in bootloader, but I just tried it and it didn't work. And like you said, only in OS and recovery; and whether USB debugging is selected or not does not affect adb use in recovery. Fastboot likewise doesn't need USB debugging; and phone obviously needs to be in fastboot mode.
We are all learning on XDA
Related
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
I wanted to update my ROM, so I downloaded the newest version of Hason2000's Toolkit and was ready to flash the boot.img.
I plug my phone in; both my phone and computer recognizes the connection. I notice that USB Debugging is required so I enable it.
Problem? The computer stop recognizing my phone, the phone sees the connection just fine.
I tried updating the drivers (several times), I tried installing the driver on another computer, no go. Turning off the USB Debugging fixes the problem, but then I can't flash the kernel.
My ROM is IceColdJelly 2.5.1 (old I know), any ideas? :crying:
Metaception said:
I wanted to update my ROM, so I downloaded the newest version of Hason2000's Toolkit and was ready to flash the boot.img.
I plug my phone in; both my phone and computer recognizes the connection. I notice that USB Debugging is required so I enable it.
Problem? The computer stop recognizing my phone, the phone sees the connection just fine.
I tried updating the drivers (several times), I tried installing the driver on another computer, no go. Turning off the USB Debugging fixes the problem, but then I can't flash the kernel.
My ROM is IceColdJelly 2.5.1 (old I know), any ideas? :crying:
Click to expand...
Click to collapse
You should be in fastboot to flash a boot.img.
USB debugging has no effect on fastboot.
Tigerlight said:
You should be in fastboot to flash a boot.img.
USB debugging has no effect on fastboot.
Click to expand...
Click to collapse
Hason2000's All-In-One Toolkit needs USB Debugging to work, it appears to just automate the fastboot commands so I assumed doing it manually would be the same.
I guess I will try it after I DL the files needed, but I still don't understand why USB Debugging stops my computer from seeing the phone.
Metaception said:
Hason2000's All-In-One Toolkit needs USB Debugging to work, it appears to just automate the fastboot commands so I assumed doing it manually would be the same.
I guess I will try it after I DL the files needed, but I still don't understand why USB Debugging stops my computer from seeing the phone.
Click to expand...
Click to collapse
Yes the toolkit uses ADB to automate the reboot into fastboot mode.
And my understanding is that enabling USB Debugging changes the drivers required so that you can access the ADB interface.
I rooted and installed my first ROM using the toolkit, idk y it's different now.
I will try to flash via fastboot and then ask in the toolkit thread as well since these driver are the ones that the came with the toolkit.
EDIT: Whhhhooaa, did it! Cheers for fastboot
Metaception said:
Hason2000's All-In-One Toolkit needs USB Debugging to work, it appears to just automate the fastboot commands so I assumed doing it manually would be the same.
I guess I will try it after I DL the files needed, but I still don't understand why USB Debugging stops my computer from seeing the phone.
Click to expand...
Click to collapse
If you want adb usb drivers, i prefer to install moborobo from Moborobo.com.
Start application,
Plug your device with usb debugging on.
and it will do the work.
I already enabled OEM Unlock and USB Debugging in Developer options.
then I connected my LG G4 H811 to PC and confirmed MTP.
adb devices just shows:
List of devices attached
If I select USB charge instead of MTP, the adb devices shows:
List of devices attached:
LGH811***** offline
Looks like MTP mode adb cannot connect to H811 at all.
Does anyone know the reason? Really need to unlock bootloader and then root my phone.
Thanks
eruisi said:
I already enabled OEM Unlock and USB Debugging in Developer options.
then I connected my LG G4 H811 to PC and confirmed MTP.
adb devices just shows:
List of devices attached
If I select USB charge instead of MTP, the adb devices shows:
List of devices attached:
LGH811***** offline
Looks like MTP mode adb cannot connect to H811 at all.
Does anyone know the reason? Really need to unlock bootloader and then root my phone.
Thanks
Click to expand...
Click to collapse
its beacause your mobile's Debugging didnt alowed that usb connection. when u type 'adb device' there should be a popup on your device asking to connect to pc. choose Allow. it will be online hen.
Thanks for the reply!
But there is no popup on the phone when I type "adb devices". The only popup I see is when I connect PC and phone with USB, a popup on phone asks me "Allow this computer to access your phone data?" I choose "Yes"
Any help will be much appreciated.
eruisi said:
Thanks for the reply!
But there is no popup on the phone when I type "adb devices". The only popup I see is when I connect PC and phone with USB, a popup on phone asks me "Allow this computer to access your phone data?" I choose "Yes"
Any help will be much appreciated.
Click to expand...
Click to collapse
You need to enable USB debugging in developers options.
Sent from my LG-D801 using Tapatalk
bxlegend said:
You need to enable USB debugging in developers options.
Sent from my LG-D801 using Tapatalk
Click to expand...
Click to collapse
I enabled OEM unlock and USB debugging both in Developer options.
eruisi said:
I enabled OEM unlock and USB debugging both in Developer options.
Click to expand...
Click to collapse
If all the checks boxes are ticked, try revoking USB debugging authorizations. Connect your device as MTP (try PTP as well) and try to adb devices again and see if you get the pop up on your phone. Last option would be to boot into recovery via button combo and reboot into the bootloader from there.
Sent from my LG-D801 using Tapatalk
I tried all of your suggestions, none of them work.
PTP/USB charging mode, adb devices shows:
List of devices attached:
LGH811***** offline
MTP shown no device attached...
I did get into download mode (bootloader mode I think) - screen says Firmware Update, do not unplug the USB connection until the process is complete
Then I tried to run fastboot oem unlock, it stucks at
< waiting for device >
and there is no change on phone screen.
Any other ideas? I really need to root my H811. Appreciate any suggestions!
Change to PTP mode.
Gesendet von meinem LG-H815 mit Tapatalk
It sounds like your usb drivers ars not properly installed. I would try uninstalling and then reinstall. Did you happen to install LG Bridge?
Sent from my LG-H811 using Tapatalk
eruisi said:
I tried all of your suggestions, none of them work.
PTP/USB charging mode, adb devices shows:
List of devices attached:
LGH811***** offline
MTP shown no device attached...
I did get into download mode (bootloader mode I think) - screen says Firmware Update, do not unplug the USB connection until the process is complete
Then I tried to run fastboot oem unlock, it stucks at
< waiting for device >
and there is no change on phone screen.
Any other ideas? I really need to root my H811. Appreciate any suggestions!
Click to expand...
Click to collapse
Download mode is not the recovery. If you have TWRP installed as your recovery, power your phone off completely and disconnect it from the computer. Then press and hold volume down and power. Keep holding and when you see the LG screen, release only the power button and press and hold it quickly again (you should still be holding volume down). This'll take you to the factory reset screen, select yes twice and you should be taken to twrp. REMEMBER, ONLY DO THIS IF YOU HAVE TWRP INSTALLED!
Sent from my LG-D801 using Tapatalk
I dont have TWRP installed
The phone is in initial state from factory and has been upgraded to MM 20O
eruisi said:
I dont have TWRP installed
The phone is in initial state from factory and has been upgraded to MM 20O
Click to expand...
Click to collapse
Ohh...follow the op in this thread.
Sent from my LG-D801 using Tapatalk
I followed all steps in the thread you list. I am stuck at "adb devices" where I didn't see my phone is listed if I connect with MTP mode. For USB charge or PTP, I see devices but it is offline.
With this problem, I cannot get my phone reboot into bootloader mode and run oem unlock/twrp.
eruisi said:
I followed all steps in the thread you list. I am stuck at "adb devices" where I didn't see my phone is listed if I connect with MTP mode. For USB charge or PTP, I see devices but it is offline.
With this problem, I cannot get my phone reboot into bootloader mode and run oem unlock/twrp.
Click to expand...
Click to collapse
Did you tried revoking the usb auth?
http://forum.xda-developers.com/g4/development/unlock-bootloader-h811-20o-t3459285/post68630578
Do you receive a popup afterwards when connecting the usb cable?
PTP or usb charge should be fine.
What OS are you running?
.
I am using Window10 on my PC.
I made a tiny progress: I installed LG Bridge software and it updated LG driver on my PC. Now when I connect phone to PC with USB (of course I choose "ALLOW" for popup USB Connection Allow this computer to accept your phone data?). Now I see devices under MTP mode but it is still offline so I cannot boot it into bootloader mode. There is no popup when I run adb devices.
I tried revoke USB auth a couple of time, no luck
Finally I made it work!
The reason is adb I was using is too old
I changed to 1.0.31 then it works w/o any issue.
Thanks for the help all the way! I really appreciate your patience.
eruisi said:
Finally I made it work!
The reason is adb I was using is too old
I changed to 1.0.31 then it works w/o any issue.
Thanks for the help all the way! I really appreciate your patience.
Click to expand...
Click to collapse
flash tt36 uss enterprise rom ots fast.
http://forum.xda-developers.com/tmobile-g4/development/t-mobile-lg-g4-h-811-mm-20o-tt10-uss-t3411769
I am having a different problem, i get to all these step but when I type fastboot oem unlock it gets stuck at waiting for device no matter how long i let it sit. I know there is no problem with adb because it shows the device with the serial number, I just can't unlock the boot loader
eruisi said:
Finally I made it work!
The reason is adb I was using is too old
I changed to 1.0.31 then it works w/o any issue.
Thanks for the help all the way! I really appreciate your patience.
Click to expand...
Click to collapse
OP @eruisi
Dont you know that this doesn't belong to the Android Development section?
Please be sensible and post in the right section and create threads only when it is actually required.
By using SEARCH and PM to other members...many things get solved with less and accurate results
Thread moved
Hi,
My phone is soft bricked, stuck in charging icon, but it responds to adb and fastboot. I tried unlocking and flash from fastboot - no luck.
USB debugging is not enabled in the device, maybe that is preventing it from flashing.
Any help, please.
Thanks,
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.