Trying to unlock bootloader, upon opening command prompt via minimal adb fastboot, after entering "fastboot flashing unlock" instead of completeing the process, I'm getting a "waiting for any device" message instead.
I'm unsure if this newly discovered usb 3.1 port on my pc is even the right port for this usbc cable, as I've never used it before now.
Windows recognizes it as MTP usb , but I can't access anything, it's empty when I open it. So I don't know if it's the wrong port, and maybe I actually need to buy a USB to usbc cable from Google (tried the one that came with my V30, got same message) or if it's something else I'm missing.
breacherman said:
Trying to unlock bootloader, upon opening command prompt via minimal adb fastboot, after entering "fastboot flashing unlock" instead of completeing the process, I'm getting a "waiting for any device" message instead.
I'm unsure if this newly discovered usb 3.1 port on my pc is even the right port for this usbc cable, as I've never used it before now.
Windows recognizes it as MTP usb , but I can't access anything, it's empty when I open it. So I don't know if it's the wrong port, and maybe I actually need to buy a USB to usbc cable from Google (tried the one that came with my V30, got same message) or if it's something else I'm missi
Click to expand...
Click to collapse
just go to device manager in your windows pc where u see unknown device then you have to search for the driver of your phone and just manually select driver for your device i just faced same issue but after that it preety works but it can persists with other phone connection
[email protected] said:
just go to device manager in your windows pc where u see unknown device then you have to search for the driver of your phone and just manually select driver for your device i just faced same issue but after that it preety works but it can persists with other phone connection
Click to expand...
Click to collapse
hey thanks, that worked. Considering I've only had 3 rooted phones in the last maybe 8 years, I tend to forget those prerequisites
Related
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
Hi guys, i'm getting this problem and cant connect to pc and i think i've tried it all.
when i connect my phone to the PC, it stars charging but my pc doesn't recognize the device, and my phone doesn't show the notification to make it file transfer.
Could it be a computer issue?
it seems not, i've uninstalled and installed drivers (ADB and Fastboot, oneplus drivers, google drivers) and the problem persist, and even try it on another computer and its the same, the phone does not appear even on Device Manager.
Could it be the Cable?
I don't think so, i'm using the original oneplus cable, it use to work really well before, and i have even connect other phone with the same cable and the other phone is recognize by the computer, so it''s not a cable issue... but I still when to a Tech-store and try other USB-C cables with their computer but my issue still persist (phone isn't recognize, just charge).
Could it be a phone software issue?
Maybe? but i discover this issue 3 weeks ago and a i was on EVOX rom and i thought it would be solved flashing another rom, and i CLEAN FLASH Resurrection Remix Rom, but then the problem was still there!
cant connect even on FASTBOOT MODE...
BTW, before installing RR, i Installed OOS 10.3.4, and still my computer doesnt recognize the phone, YES i have enabled developer options and USB debugging is enabled, and USB PREFERENCES to File transfer, but its not helping me, the "usb for" option its all grayed out and cant change that.
Right now i'm stuck on a RR build without Gapps, and i lost ROOT and RECOVERY, and as you may think, i cant install any of them because i cant connect to my pc, so i'm in a pretty difficult situation here hehe, could you please help me out?
This helped me. Hope it works for you too
I can't paste the link but search "how to get your Android device to show up in file explorer" by how to geek.
Didn't work
xnruaa said:
I can't paste the link but search "how to get your Android device to show up in file explorer" by how to geek.
Click to expand...
Click to collapse
Thanks for your reply, but this didn't work because my device isn't shown on device & printers, or anywhere as far as i checked...
PROBLEM SOLVED.
I think this is the silliest solution I've ever seen, it was just DUST, i clean my USB-C PORT (with a mask xD) and then pluggin, AND VOILA, it worked!!! so keep your ports clean everyone
adb devices command works perfectly but when I'm in bootloader, computer does not recognize my phone. fastboot devices returns nothing. device manager show Android with a triangle under "Other Devices".
1. Tried updating the driver and manually choosing it as Android ADB Interface or Android Bootloader Interface with no luck.
2. Tried uninstalling/reinstalling the USB drivers and adb still works normal but fastboot still won't recognize my phone.
3. Tried revoking USB debugging and reallowing debug from my phone. Still same issue.
4. Tried using original Oneplus USB C-C cable, Pixel USB C-C cable, USB A-C cable, generic USB C-C cable (Oneplus was still not recognized on fastboot but Pixel was recognized so it is not the cable/PC)
4. Tried reformatting my PC. Doing a clean install on everything and still same issue.
My last resort is this thread. I would really like to unlock my Oneplus 8T bootloader and root but for some reason, fastboot does not recognize my phone. I just hooked up my Pixel phone after reformatting my PC and adb/fastboot worked normally like it should.
grimlust said:
adb devices command works perfectly but when I'm in bootloader, computer does not recognize my phone. fastboot devices returns nothing. device manager show Android with a triangle under "Other Devices".
1. Tried updating the driver and manually choosing it as Android ADB Interface or Android Bootloader Interface with no luck.
2. Tried uninstalling/reinstalling the USB drivers and adb still works normal but fastboot still won't recognize my phone.
3. Tried revoking USB debugging and reallowing debug from my phone. Still same issue.
4. Tried using original Oneplus USB C-C cable, Pixel USB C-C cable, USB A-C cable, generic USB C-C cable (Oneplus was still not recognized on fastboot but Pixel was recognized so it is not the cable/PC)
4. Tried reformatting my PC. Doing a clean install on everything and still same issue.
My last resort is this thread. I would really like to unlock my Oneplus 8T bootloader and root but for some reason, fastboot does not recognize my phone. I just hooked up my Pixel phone after reformatting my PC and adb/fastboot worked normally like it should.
Click to expand...
Click to collapse
try this https://forum.xda-developers.com/oneplus-8t/how-to/guide-fastbootd-to-recognized-computers-t4192449
---------- Post added at 01:00 PM ---------- Previous post was at 12:58 PM ----------
You can also try installing the oneplus drivers in the oneplus drive that pops up when you plug in your phone
Edit: Scratch that. I guess the 8T doesn't come with a driver partition. Try this https://oneplususbdrivers.com/oneplus-8t-usb-driver-download/
Install Universal ADB Drivers first and then boot Oneplus 8T to fastboot mode, repair oneplus device driver to "ClockworkMod Android ADB Interface" on Windows, you can use fastboot command for unlock bootloader now.
Universal ADB Drivers https://adb.clockworkmod.com/
I had the worst bloody time getting fastboot drivers installed for my 8T (KB2007, T-Mo).
I ended up having to find the device id for my device and manually patch and resign Google's USB drivers to get it working. If you can handle reading batch files and stuff, clone the repositories at https://github.com/fawazahmed0/Latest-adb-fastboot-installer-for-windows and https://github.com/fawazahmed0/windows-unsigned-driver-installer.
grimlust said:
adb devices command works perfectly but when I'm in bootloader, computer does not recognize my phone. fastboot devices returns nothing. device manager show Android with a triangle under "Other Devices".
1. Tried updating the driver and manually choosing it as Android ADB Interface or Android Bootloader Interface with no luck.
2. Tried uninstalling/reinstalling the USB drivers and adb still works normal but fastboot still won't recognize my phone.
3. Tried revoking USB debugging and reallowing debug from my phone. Still same issue.
4. Tried using original Oneplus USB C-C cable, Pixel USB C-C cable, USB A-C cable, generic USB C-C cable (Oneplus was still not recognized on fastboot but Pixel was recognized so it is not the cable/PC)
4. Tried reformatting my PC. Doing a clean install on everything and still same issue.
My last resort is this thread. I would really like to unlock my Oneplus 8T bootloader and root but for some reason, fastboot does not recognize my phone. I just hooked up my Pixel phone after reformatting my PC and adb/fastboot worked normally like it should.
Click to expand...
Click to collapse
Hi Grimlust i am in this exact scenario is it your device problem solved. If it has done can you walk me through the steps you went through to get that result. Please its my last chance to revive my one plus 8T
savio97 said:
Hi Grimlust i am in this exact scenario is it your device problem solved. If it has done can you walk me through the steps you went through to get that result. Please its my last chance to revive my one plus 8T
Click to expand...
Click to collapse
don't know if you still need it but today i was as desperate as you were and this helped me
How to Install Google's Android Bootloader Interface Drivers
In this comprehensive guide, we will show you how to download and install the Google's Android Bootloader Interface Drivers on your PC.
www.droidwin.com
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?
I am trying to unlock Redmi note 6 pro but facing issue in fastboot. whenever I try 'fastboot devices' command, on 1st query it shows ID but on 2nd time query it shows '????????". when this happen, on phone screen messege appears as " press any key to shutdowd". pls check the attached image and tell me the solution. Have tried uninstall/reinstall driver, updated phone through phone's updater but nothing helps. phone always kicks out from fastboot mode. due to this problem mi unlock tool never detect my phone.
@Narrry84
Change USB port, change USB cable, install Android USB Driver matching your needs if not already done yet
jwoegerbauer said:
@Narrry84
Change USB port, change USB cable, install Android USB Driver matching your needs if not already done yet
Click to expand...
Click to collapse
Have done already these steps. will try changing PC tomorrow..