Hello everyone, I'm using Redmi Note 3 and I have tried rooting it several times.
I have unlocked the bootloader. I have also installed the adb drivers.
When I connect phone in fastboot mode and write 'fastboot devices' in cmd it doesn't return anything. But when I connect when its on, adb devices returns the device code.
Please help.
Same, happens to mine too. Used to work with a previous install of windows, but now, nope.
Had this issue too.
Try going to Device Manager and check to see if Kedacom USB Device shows up. Under which, Android Bootloader Interface should be present. Install minimalist ADB and fastboot and right click Android Bootloader Interface. Click Update Driver Software, browse computer, and then click the option to list driver files already present on your drive. It should pull up a fastboot driver that's an older version than the one you currently have. Install that and fastboot will work again.
Doesn't work
Can you please link the files for download when we're updating the driver software.
Related
Hello,
I have just bought a oneplus 7t Pro
I would like to root it but first I need to unlock it.
But impossible to get it detected in fastboot while it works with adb (it finds my device).
I have installed the driver from the attached "cd" repertory, nevertheless the devices manager shows an "android" device which is not correctly installed.
I tried to install the driver manually by slecting it in the oneplus folder in program files, but it says that the driver "OnePlus android bootloader interface" cannot be installed as the hash file is missing.
anyone can help?
Thanks
get the fastboot driver from google. easy to find, then unzip it and select it when installing drivers for oneplus fastboot in device manager.
so yea get either the google fastboot driver or the OEM drivers found there too
DeeZZ_NuuZZ said:
get the fastboot driver from google. easy to find, then unzip it and select it when installing drivers for oneplus fastboot in device manager.
so yea get either the google fastboot driver or the OEM drivers found there too
Click to expand...
Click to collapse
Hello,
This what I tried and it worked! Using generic driver instead of ... weird. Anyway now everything is fine.
Thanks.
I have the following devices installed ( I enabled show hidden devices ) .
Although my phone still wont be recognized after a qualcomm crash dump
I am on an older macbook pro running High Sierra. the phone I'm using is a Blu G5 running android 9. I have the developer options unlocked and oem unlocked and usb debugging checked. When i open my terminal i type cd and drag and drop the platform tools folder into the terminal window changing the directory to the folder containing the adb and fastboot files. I can use adb commands such as adb devices and get the serial number and it says devices. So far so good. Then i reboot the phone into the bootloader manually or using command adb reboot bootloader and the phone goes into fastboot mode. I know because it says it on top of the screen in white letters. Then i run into the problem fastboot commands don't work. If I type in fastboot devices nothing but a new command line shows up. When i type in any other command like fastboot device or fastboot oem unlock it says "waiting for any devices." I wait and wait but nothing happens. I have looked on the internet for a solution but all i find is that the driver may not deinstalled properly. I have tried manually installing fastboot driver and used sdk manager to install the fastboot driver and I have tried it using the terminal in android studio but no matter what when i try useing fastboot commands i get the "waiting for any device" message. Does any have a solution or could anyone recommend and forum for android development on MacOSX?
@DimDreams
Seems the Fastboot driver is invalid.
jwoegerbauer said:
@DimDreams
Seems the Fastboot driver is invalid.
Click to expand...
Click to collapse
I have literally tried like 10 different sdk tool downloads just platform tool download basically every thing i can find. By chance would you or anyone out there have a working driver for MacOSX 10.13.6? or link a guide that can help me figure this out. I have made a little progress with a forum on xda about fastboot on macs but i still just keep getting the waiting for any device message.
@DimDreams
May also be that the Fastboot Android mode is not available on the phone in question.
I've had similar issues before and noticed that fastboot mode works better via USB 2.0 than USB 3.0. Maybe check which port you're using and switch. ADB seems to work well either way, however. Hope that helped.
I just had this problem as well and I found this, what worked for me is first boot your phone into bootloader mode with
Code:
adb reboot bootloader
. While in the bootloader fastboot worked for me. Hope this helps someone!
Once I reboot to bootloader and connect to PC, the command "fastboot devices" does not recognize the device, so when I try to unlock it. it says "waiting for device". I've enabled both OEM unlocking and USB debugging.
The phone shows "fastboot_unlock_verify ok"
"The device is in fastboot mode which is only for debug Android devices. if you want to exit fastboot mode, please long press volume up nad power buttons simultaneously. "
EDIT: Solved it by using the correct platform-tools
I have the same problem. I actually thought that I installed the right sdk platform tools. Can you upload the platform tools that work for you?
Thank you
7tyjupiter said:
I have the same problem. I actually thought that I installed the right sdk platform tools. Can you upload the platform tools that work for you?
Thank you
Click to expand...
Click to collapse
I used the ones from here - https://www.getdroidtips.com/download-adb/#How-to-Install-Android-SDK-and-Platform-Tools
Solved.
I downloaded the platform tools 30.0.5 and reinstall it. Then i reinstall the adb bootloader driver right at the moment when the Nord2 is in the fastboot mode.
cheers
I have no developer options for reboot, bootloader, recovery.
platform tools 30.0.5, where?
Try after reboot into bootloader "fastboot devices". Is the Nord 2 recognized?
For me the correct command was "fastboot flashing unlock".
Hier is the link for the Platform tools 30.0.5
adb - platform tools v30.0.5.zip | by abdyasar for Utilities
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
I'm having the same issue. I can't get my Nord 2 show up with "fastboot devices". Sent my phone into the bootloader with "adb reboot bootloader" no problem.
I have used the 30.0.5 platform tools as well as the 31.0.3. Installed Oneplus USB drivers and also tried the universal r13 android drivers (Reinstalled the bootloader drivers while in bootloader mode). Also tried Snoop05s 1.43 adb installer. All to no avail. Just can't get my device to show up in the bootloader.
In Phone settings bootloader is open and USB debugging is on.
Edit: I made it work. Used regular CMD and not powershell and it showed up.
F4t16u3 said:
I'm having the same issue. I can't get my Nord 2 show up with "fastboot devices". Sent my phone into the bootloader with "adb reboot bootloader" no problem.
I have used the 30.0.5 platform tools as well as the 31.0.3. Installed Oneplus USB drivers and also tried the universal r13 android drivers (Reinstalled the bootloader drivers while in bootloader mode). Also tried Snoop05s 1.43 adb installer. All to no avail. Just can't get my device to show up in the bootloader.
In Phone settings bootloader is open and USB debugging is on.
Edit: I made it work. Used regular CMD and not powershell and it showed up.
Click to expand...
Click to collapse
Mine does not show up.... -.-
I've been trying to unlock the bootloader in my phone (OnePlus7T Pro).
I can't see my phone when booted into fasboot mode or recovery mode (I can see the phone while normally working).
The command: fastboot devices shows no device. The same with adb devices command.
I think I need a proper driver for the device. I've already tried UniversalAdbDriverSetup.msi, but with no success.
I use PC with Ryzen processor and Win10.
Could you suggest a solution, please?
The UniversalAdbDriverSetup you referred to is not of any use. You instead have to install the Android USB Driver suitable to your phone:
Download OnePlus USB Driver for Windows (Latest Driver)
Download the latest and original OnePlus USB Driver to connect your OnePlus Smartphone to the Windows Computer quickly and easily.
androidmtk.com
kamien8 said:
I use PC with Ryzen processor and Win10.
Could you suggest a solution, please?
Click to expand...
Click to collapse
This might help...
[FIX] Fastboot issues on Ryzen based PCs
AMD has been known for it's notorious fastboot issues in the custom ROM community, especially with Xiaomi devices. I was trying to unlock the bootloader of my Redmi Note 5 Pro the other day and I encountered with an issue where Mi Unlock Tool...
forum.xda-developers.com
Thanks for information.
I can see the device when it is up and running. Still nothing when it is in FB mode, however I can see the Widnows sound of a connected device.
jwoegerbauer said:
The UniversalAdbDriverSetup you referred to is not of any use. You instead have to install the Android USB Driver suitable to your phone:
Download OnePlus USB Driver for Windows (Latest Driver)
Download the latest and original OnePlus USB Driver to connect your OnePlus Smartphone to the Windows Computer quickly and easily.
androidmtk.com
Click to expand...
Click to collapse
I uninstalled the previous drivers and installed the right one from the link. I also have used your version of adb and fastboot.
CXZa said:
This might help...
[FIX] Fastboot issues on Ryzen based PCs
AMD has been known for it's notorious fastboot issues in the custom ROM community, especially with Xiaomi devices. I was trying to unlock the bootloader of my Redmi Note 5 Pro the other day and I encountered with an issue where Mi Unlock Tool...
forum.xda-developers.com
Click to expand...
Click to collapse
Yes, I've heard about the fix. Run it, but still nothing happened.
Maybe I have to find somebody with Intel processor.
Because your phone's Android is version 10 try this
Code:
adb reboot fastboot
fastboot reboot fastboot
fastboot devices
....
jwoegerbauer said:
Because your phone's Android is version 10 try this
Code:
adb reboot fastboot
fastboot reboot fastboot
fastboot devices
....
Click to expand...
Click to collapse
Hi, I'm half way.
I checked on Intel proc, and I can see bootloaded phone in fastboot. ADB still can't see the device.
I was trying to re-install drivers, but no changes.
Unfortunately I need working ADB as I have to sideload an image.
I've since years a laptop powered by AMD Ryzen 5 in use: Fastboot always works like a hell. Hence I'm pretty sure that it doesn't matter whether Fastboot is run on an Intel or AMD powered computer.
If ADB isn't working as expected my guess is that "USB debugging" didn't get enabled on phone and phone didn't get re-booted afterwards.
USB debugging is enabled. When the phone is started normally, ADB works fine (for example I can use adb reboot bootloader command)
I thought, maybe there is a mess with the drivers in the device. Can it cause the issue?
So to confirm, this is the only one drivers package I need to run OnePlus (7T Pro) in bootloader and use fastboot and adb commands?
OnePlus 7T Pro USB Driver for Windows
Download the latest OnePlus 7T Pro Driver for Windows Computer. You can use the latest OnePlus Driver to connect OnePlus Device to the Computer.
oneplusdriver.com
Command
Code:
adb reboot bootloader
since Android 10 is incorrect: I've already told you this in a previous post.
jwoegerbauer said:
Command
Code:
adb reboot bootloader
since Android 10 is incorrect: I've already told you this in a previous post.
Click to expand...
Click to collapse
Yes, you're right.
adb reboot bootloader command works. Once I am in bootloader I still can connect phone via adb but fastboot doesn't work. That was my question, if the highlightet drivers are the only one I need.
Is it possible, that there is something wrong with the phone?
If ADB successfully connects to phone then your phone isn't booted into its bootloader, but into Android OS.
Hey all, I just got a G90 Pro that I want to put a ROM on, but something is up with the fastboot. I have the drivers installed according to what I found online, but when I go to fastboot there is no response from the cmd inputs. Nothing even shows up when I check fastboot devices. Has anyone had luck with these phones? I can't even unlock the bootloader!
If not already done yet, install the suitable BLUE USB Driver for Android:
Download BLU USB Driver for Windows (Latest Driver)
Download the latest and original BLU USB Driver to connect any BLU Smartphone and Tablets to the Windows Computer quickly.
androidmtk.com
jwoegerbauer said:
If not already done yet, install the suitable BLUE USB Driver for Android:
Download BLU USB Driver for Windows (Latest Driver)
Download the latest and original BLU USB Driver to connect any BLU Smartphone and Tablets to the Windows Computer quickly.
androidmtk.com
Click to expand...
Click to collapse
I have done this, but did it again just to be sure, and device manager recognizes the G90 Pro under USB devices, and ADB finds it, but when I do the 'adb reboot bootloader' the fastboot mode text is on the bottom, yet fastboot commands don't do anything, not even 'fastboot devices'.
Edit: Fastboot devices is recognized in fastbootd, but not regular fastboot, yet the other commands don't work.
In your case fastboot is located in Android's user-space, hence you run this command sequence
Code:
adb devices
adb reboot fastboot
fastboot reboot fastboot
fastboot <YOUR-COMMAND-HERE>
fastboot reboot
jwoegerbauer said:
In your case fastboot is located in Android's user-space, hence you run this command sequence
Code:
adb devices
adb reboot fastboot
fastboot reboot fastboot
fastboot <YOUR-COMMAND-HERE>
fastboot reboot
Click to expand...
Click to collapse
Fastboot reboot fastboot just brings up the fastboot command list. Assuming it's expecting me to try reboot bootloader.
That's really weird because your phone is running Android 10.
My info in settings definitely confirms that. Nothing seems to be working as expected though.
jwoegerbauer said:
That's really weird because your phone is running Android 10.
Click to expand...
Click to collapse
Is there any other possible solution? I still can't get fastboot commands to work after rebooting to fastboot mode from fastbootd.