This presumes that you can get adb/fastboot to work and it just won't recognize your device.
Not originally written by me...made some adjustments though
- connect your Dell in(volume up and power held) fastboot(ignore if only want adb) and change manually drivers one of the method:
go into device manager(type devmgmt.msc into command prompt)> double click dell streak device > update driver >browse my computer for driver software >Let me pick from list >Android phone >Android Bootloader Interface or android adb interface.
-reboot to fastboot with volume up and power held and type fastboot devices on cmd
-or type adb devices in command prompt and your device should show.
Good luck.
Hey Guys any1 knows the fastboot commands for booting Device into recovery Mode and checking connected Devices?
Help would be nice, need to know
Thx Advanced
Function: Check connection and get basic information about devices connected to the computer.
"adb devices"
"fastboot devices" - This is essentially the same command as adb devices above. However, it works in the bootloader, which ADB does not.
Function: Reboot your phone into recovery mode.
"adb reboot recovery"
Obviously without the speech marks.
Hello,
despite presumably doing everything correctly, Tool spews this error when I'm trying to relock the BL by using "fastboot oem asus-lock" command:
FAILED (remote: 'Command not supported in default implementation')
1. I have connected the phone to the side port.
2. Tool folder is directly in C:\ directory.
3. ADB binaries are installed correctly.
4. Phone is in fastboot mode and detected, but the tool cannot detect correctly which phone it is and asks me to choose the model manually, but ROG 3 is not on the list, so I chose ROG Phone 2. Does it matter? If so, what do I do? I also set priviledges for Tool-all-in-one systemwide, does it matter?
Also, should I use the command line in Advanced Options of the tool, or should I rightclick the folder and summon the command line from there? Please help, I don't have any more ideas! Thank you!
use the side usb port (the top black one, not the bottom orange one) and try the command again through FB
Thank you for fast response!
I'm constantly using the sideport, and the command still fails with the message above.
What I can add is that EVERY fastboot process fails with the SAME message, so it's not just relocking that is the problem, but it seems that every fastboot command cannot be executed on my ROG Phone 3 (aside from fastboot devices, which correctly shows my device as connected).
Which suggests to me that something is wrong with my setup. Anybody has any idea?
When I try to relock my rog phone 3 I do the list devices command and it shows my device, I then reboot into fastboot
and type command fastboot oem asus-lock and all it says is <waiting for device> how can I relock bootloader???????? If there was an apk to unlock it shouldnt there be an apk to relock it?
You need install fastboot drivers on your pc, so device manager will see your phone
When I open PowerShell and run the command "fastboot devices" my phone isn't getting detected. My phone is connected to my PC, I've installed platform tools & adb as well as the correct ROM. I'm pretty new to rooting so I'm not sure what's going on. I don't have a SIM Card so that might be the issue, but I'm trying to find a root guide that doesn't require sim.
What I've installed;
Latest USB Driver (MTP USB Device)
Latest ADB/Fastboot from android.com/studio/releases/platform-tools
Installed Fastboot ROM MIUI V13.0.6.0.SKDMIXM Stable from https://xiaomirom.com/en/rom/xiaomi.../#download-xiaomi-11t-pro-stable-fastboot-rom
Device Specs:
- MIUI Global 13.0.6 Stable (SKDMIXM)
- Android ver. 12 SKQ1.211006.001
Following this guide to root and have been following step by step up to 3:12:
WhalePC said:
When I open PowerShell and run the command "fastboot devices" my phone isn't getting detected. My phone is connected to my PC, I've installed platform tools & adb as well as the correct ROM. Not sure what's going on.
Following this guide to root and have been following step by step up to 3:12:
Click to expand...
Click to collapse
Maybe you summarized the command in your statement but with power shell the command is "./fastboot devices"
Do you see the device icon in the taskbar?
NOSS8 said:
Maybe you summarized the command in your statement but with power shell the command is "./fastboot devices"
Do you see the device icon in the taskbar?
Click to expand...
Click to collapse
Yeah i see the icon on my taskbar. Just tried running it via "./fastboot devices" and no devices show up. I haven't unlocked the bootloader yet (haven't enabled Mi Unlock status) yet is that maybe the issue? If so, is there a way to root without the need of a sim card?
WhalePC said:
Yeah i see the icon on my taskbar. Just tried running it via "./fastboot devices" and no devices show up. I haven't unlocked the bootloader yet (haven't enabled Mi Unlock status) yet is that maybe the issue? If so, is there a way to root without the need of a sim card?
Click to expand...
Click to collapse
You generally shouldn't need a SIM card to use ADB or fastboot commands.
Are you sure you have the correct drivers installed? Does the device appear under adb devices when in Android?
V0latyle said:
You generally shouldn't need a SIM card to use ADB or fastboot commands.
Are you sure you have the correct drivers installed? Does the device appear under adb devices when in Android?
Click to expand...
Click to collapse
How do i check that I have the correct drivers installed? I ran adb devices and it showed my device 3d37ace2 device was connected.
EDIT: Here's how I enter into fastboot and excute commands;
- Plug in phone into PC and wait for icon to show up on taskbar
- Open Powershell in platform-tools folder
- Power off phone and enter fastboot (hold down power button+vol down)
- Once Fastboot text shows up on my phone I run the command "fastboot devices" in powershell
WhalePC said:
How do i check that I have the correct drivers installed? I ran adb devices and it showed my device 3d37ace2 device was connected.
EDIT: Here's how I enter into fastboot and excute commands;
- Plug in phone into PC and wait for icon to show up on taskbar
- Open Powershell in platform-tools folder
- Power off phone and enter fastboot (hold down power button+vol down)
- Once Fastboot text shows up on my phone I run the command "fastboot devices" in powershell
Click to expand...
Click to collapse
This looks like a good place to start. It's possible you have a generic ADB driver installed and may need a device specific one.
V0latyle said:
This looks like a good place to start. It's possible you have a generic ADB driver installed and may need a device specific one.
Click to expand...
Click to collapse
Just reinstalled the latest ADB/Fastboot from https://androidmtk.com/download-15-seconds-adb-installer and still have the same issue. I also installed Xiaomi AB/Fastboot Tools to check if it can identify my device and it does.
Running adb shell in cmd prompt outputs:
Code:
C:\Users\Whale>adb shell
* daemon not running; starting now at tcp:5037
* daemon started successfully
vili:/ $
But once it's in fastboot it responds with:
Code:
C:\Users\Whale>adb shell
adb.exe: no devices/emulators found
Same for Powershell:
Code:
PS C:\Users\Whale\Downloads\11t pro\platform-tools> adb devices
List of devices attached
3d37ace2 device
PS C:\Users\Whale\Downloads\11t pro\platform-tools> fastboot devices
PS C:\Users\Whale\Downloads\11t pro\platform-tools> ./fastboot devices
PS C:\Users\Whale\Downloads\11t pro\platform-tools> adb devices
List of devices attached
PS C:\Users\Whale\Downloads\11t pro\platform-tools> fastboot devices
PS C:\Users\Whale\Downloads\11t pro\platform-tools> ./fastboot devices
Currently, when my phone is turned on (not in fastboot), my device is detected as 3d37ace2 (codename: vili), but as soon as it goes to Fastboot, it no longer can detect the device.
WhalePC said:
Just reinstalled the latest ADB/Fastboot from https://androidmtk.com/download-15-seconds-adb-installer and still have the same issue. I also installed Xiaomi AB/Fastboot Tools to check if it can identify my device and it does.
Running adb shell in cmd prompt outputs:
Code:
C:\Users\Whale>adb shell
* daemon not running; starting now at tcp:5037
* daemon started successfully
vili:/ $
But once it's in fastboot it responds with:
Code:
C:\Users\Whale>adb shell
adb.exe: no devices/emulators found
Same for Powershell:
Code:
PS C:\Users\Whale\Downloads\11t pro\platform-tools> adb devices
List of devices attached
3d37ace2 device
PS C:\Users\Whale\Downloads\11t pro\platform-tools> fastboot devices
PS C:\Users\Whale\Downloads\11t pro\platform-tools> ./fastboot devices
PS C:\Users\Whale\Downloads\11t pro\platform-tools> adb devices
List of devices attached
PS C:\Users\Whale\Downloads\11t pro\platform-tools> fastboot devices
PS C:\Users\Whale\Downloads\11t pro\platform-tools> ./fastboot devices
Currently, when my phone is turned on (not in fastboot), my device is detected as 3d37ace2 (codename: vili), but as soon as it goes to Fastboot, it no longer can detect the device.
Click to expand...
Click to collapse
ADB commands won't work in fastboot and vice versa. When your device is in Android or recovery, you can use ADB commands, but when it's in bootloader mode, you have to use fastboot commands. ADB shell won't do anything for you in fastboot because there's no kernel running, much less a shell.
Since your device isn't appearing under fastboot devices it's most likely a driver issue. You need two separate drivers; the ADB driver is not device specific, but the bootloader driver is.
Case in point: This is what appears when my Pixel 5 is connected while booted into Android:
When I reboot to bootloader, this is what I see:
So, this is what I suggest:
Reboot to bootloader, connect to your PC, and look at Device Manager to see if anything comes up as unrecognized. Make sure it's the right device by unplugging the USB cable; it should disappear. You'll then need to update the driver, and point it to the the Xiaomi driver folder.
V0latyle said:
ADB commands won't work in fastboot and vice versa. When your device is in Android or recovery, you can use ADB commands, but when it's in bootloader mode, you have to use fastboot commands. ADB shell won't do anything for you in fastboot because there's no kernel running, much less a shell.
Since your device isn't appearing under fastboot devices it's most likely a driver issue. You need two separate drivers; the ADB driver is not device specific, but the bootloader driver is.
Case in point: This is what appears when my Pixel 5 is connected while booted into Android:
View attachment 5731657
When I reboot to bootloader, this is what I see:
View attachment 5731663
So, this is what I suggest:
Reboot to bootloader, connect to your PC, and look at Device Manager to see if anything comes up as unrecognized. Make sure it's the right device by unplugging the USB cable; it should disappear. You'll then need to update the driver, and point it to the the Xiaomi driver folder.
Click to expand...
Click to collapse
Thanks fam, was able to solve it by installing a different driver from this video:
.
Now I'm getting an error:
Code:
PS C:\Users\Whale\Downloads\11t pro\platform-tools> fastboot flash boot magisk_patched.img
Sending 'boot_a' (196608 KB) OKAY [ 4.210s]
Writing 'boot_a' FAILED (remote: 'Flashing is not allowed in Lock State')
fastboot: error: Command failed
which I assume means I need to unlock my bootloader via Mi Unlock status?
WhalePC said:
Thanks fam, was able to solve it by installing a different driver from this video:
.
Now I'm getting an error:
Code:
PS C:\Users\Whale\Downloads\11t pro\platform-tools> fastboot flash boot magisk_patched.img
Sending 'boot_a' (196608 KB) OKAY [ 4.210s]
Writing 'boot_a' FAILED (remote: 'Flashing is not allowed in Lock State')
fastboot: error: Command failed
which I assume means I need to unlock my bootloader via Mi Unlock status?
Click to expand...
Click to collapse
Yep. I don't know how it works on Xiaomi devices but try fastboot flashing unlock
Unlocking your bootloader will wipe data, so if you need to back anything up, do that first.
Enter in FASTBOOT MODE: press Power+Volume down button for 4-5 sec in the same time,the phone reboot, at the vibration release the power button.Now plug in the phone to the PC.
Having the bootloader locked does not prevent seeing the device in Fastboot mode.(***Not useful at the moment)
To root you must first unlock the bootloader.(***your bootloader is locked)(FAILED (remote: 'Flashing is not allowed in Lock State')
Unlock the bootloader
You must have a Xiaomi account and a valid sim.
Procedure:
https://new.c.mi.com/global/post/101245
https://en.miui.com/unlock/index.html
Why look for tutorials on You tube'Sometimes good, sometimes fake) while on XDA(Always good )in the How to section of your device these tutorials exist and specify that the bootloader must be unlocked.
https://forum.xda-developers.com/t/root-xiaomi-11t-pro.4441213/
https://forum.xda-developers.com/t/...structions-for-xiaomi-11t-pro-global.4362515/
check debugging via USB option.
WhalePC said:
When I open PowerShell and run the command "fastboot devices" my phone isn't getting detected. My phone is connected to my PC, I've installed platform tools & adb as well as the correct ROM. I'm pretty new to rooting so I'm not sure what's going on. I don't have a SIM Card so that might be the issue, but I'm trying to find a root guide that doesn't require sim.
What I've installed;
Latest USB Driver (MTP USB Device)
Latest ADB/Fastboot from android.com/studio/releases/platform-tools
Installed Fastboot ROM MIUI V13.0.6.0.SKDMIXM Stable from https://xiaomirom.com/en/rom/xiaomi.../#download-xiaomi-11t-pro-stable-fastboot-rom
Device Specs:
- MIUI Global 13.0.6 Stable (SKDMIXM)
- Android ver. 12 SKQ1.211006.001
Following this guide to root and have been following step by step up to 3:12:
Click to expand...
Click to collapse
You will need to manually configure fastboot drivers.
hi folks I am trying to unlock the bootloader on a Motorola E4 plus running 7.1.1 but I'm having a lot of trouble. Firstly when I boot the device into bootloader mode by pressing and holding the power and volume down buttons and plug it into my windows 10 pc it says 'transfer mode: cable not connected'. I have tried different cables and usb ports but the issue persists. Moreover, when I try to get the unlock data using the 'fastboot oem get_unlock_data' command it says '(remote: 'unknown command')'. Oddly however adb works and the phone is shown when I type 'fastboot devices'.
So far I've tried:
using my mac
factory resetting the phone
wiping the system cache
ensuring security is set to none on the phone
different usb cables
different usb ports
installing the android SDK and running the cmd window from it
minimal adb and fast boot
platform tools based adb
restarting the computer
installing motorola's own drivers
ensuring oem unlocking and usb debigging are turned on in developer options
ensuring the MTP driver is installed and updating the driver in device manager
restarting the phone
I would be grateful for any help anybody could please offer. Thanks all!