I messed up something on my phone so that it only boots up in bootloader mode. According to the phone, flashing mode is enabled and it recognizes that a USB cable is attached.
The computer makes the sound that something attached when I connect the phone. However, running "adb devices" shows no connection and the fastboot command says "waiting for any device". The phone is essentially bricked if I can't get it recognized by the computer. Please help!
The third computer I tried, worked! Thanks.
Related
I am using fastboot with the "Google USB Driver package, revision 4" from the Android SDK. The device is detected just fine when I am booted into fastboot but nothing is ever listed when I run "fastboot devices" from the command line.
I have tried this with my "Android Dev Phone 1" (I got it from ebay!) and my unlocked/rooted Droid Incredible. Both devices do have USB debugging enabled. Adb works just fine when the devices is booted up.
With the dev phone when I boot holding back/off I get the message "serial0". When I connect it to the computer it changes to "fastboot", as expected.
Any suggestions?
Anyone?
waiting device
I have similar problem here. Fastboot cant seem to detect any device plugged to usb. Tried installing all drivers from LG setup, got sdk and ran cmd promt, cd directory, then typed fastboot erase recovery. It just waits for the device. Is there anyone familiar with this prblem. Hope someone can help. THanks!
So I turned on USB debugging and made sure the RSA key fingerprint was remembered on my phone. I connected my phone to my PC with the HTC drivers installed and ran "adb devices" to make sure that my PC and phone are communicating with each other, and the device is online. I do "adb reboot", and the phone reboots, but then my phone appears offline to my PC. I've looked around for an hour and cannot seem to find the root of this issue...
I've found toggling USB debugging will make the PC recognize the device again, but then I have issues when it comes to try to S-Off the device. I think this is the main cause of the problem.
It appears when weaksauce re-roots after boot, adb no longer recognizes my device. Any fixes?
Hey all.
I'm real sorry if this is out there somewhere--which I'm sure it is.
I had no luck using the search feature.
My PC (win 8.1) will not recognize the phone when connected in fastboot mode. I have the drivers installed and will work/connect when powered on. In fastboot it DOES show that the USB is obviously connected but, again, PC doesn't pick it up or says there was a "problem" with this device....
I am trying to the the TWRP recovery installed.
In addition, why is it when stock "recovery" is selected is shows the android with the statement "no command" and does nothing?!
Thanks for any and all help and/or links
I'm hoping someone can help me out here. I've rooted phones before and didn't have any trouble previously. I just bought a used Pixel 3 on eBay with the plan to root using Magisk. The only problem is I can't get the device to be recognized at all on my PC. I've tried all the usual things like different USB ports, different cables, cleaning out the port, etc. I have the latest drivers installed and I have a Pixel XL that is recognized by my PC immediately so I know I have the correct drivers installed. Pixel 3 does not show up in Device Manager at all. I have USB debugging enabled on the device, but it never prompts me to Allow USB debugging when I connect the Pixel 3 to my PC.
Now, here's the weird part. I know the cable is working fine because I use the same cable and plug it into my Mac. The Pixel 3 is recognized immediately and I'm prompted to enable USB debugging. ADB then works just fine on my Mac. 'adb devices' shows my phone. But I then try to use 'adb reboot bootloader' and my phone reboots to the bootloader as it should. At this point my phone says it's in FastBoot Mode, but the device isn't recognized using 'sudo fastboot devices' and if I try 'sudo fastboot flashing unlock' it just sits there saying 'waiting for any device'. I've also tried putting it into FastBoot mode manually by using the Power and Volume Down key, but run into the same issue with it not being recognized while in FastBoot mode.
Could the previous owner have done something to the bootloader to cause the device to not be recognized in FastBoot mode? And is there any way to fix it? Why would the phone be recognized on my Mac without issue, but using the same cable and multiple different ports on my PC, it never gets recognized?
Any help would be very much appreciated here as I'm at a loss as to what I can do and fear I just spent money on an expensive paperweight.
I tested the cable I'm using with my Pixel XL and it's immediately recognized by my PC and the notification for USB debugging shows on the phone, so I know the cable is working out. No device ever shows in the device manager when I have my Pixel 3 connected though. I've even uninstalled the drivers while my Pixel XL is connected to hopefully put Windows into a driverless state hoping my Pixel 3 would then show up as an unrecognized device, but no device. I can't get it to show up at all in Windows for some reason and it's not recognized while in fastboot mode on my Mac. Fastboot mode information all seems to match what a Pixel 3 should look like as well, so I don't think the previous owner installed the wrong software causing device id mismatch. Anyone have any other suggestions for what I can try?
My phone "POCO x2" has somehow got "bricked" and Now when i try to get it unbricked it does not connects to my pc . Phone is in "fastboot" mode but when I connect's that through cable I can not even see it in "device manager" in "Android" or in "Other devices" please help anyone
Beonder said:
My phone "POCO x2" has somehow got "bricked" and Now when i try to get it unbricked it does not connects to my pc . Phone is in "fastboot" mode but when I connect's that through cable I can not even see it in "device manager" in "Android" or in "Other devices" please help anyone
Click to expand...
Click to collapse
Open device manager and verify whether or not it is loading the proper driver. The correct driver should be something like "Android Bootloader Interface". You may need to download and manually install the full set of drivers for your device manufacturer. After installing the driver's, you may need to manually select the bootloader interface driver.