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.
Related
i can only access the white screen when i chose bootloader>recovery i get the /!\ sign.
i installed the USB driver and i was able to use only the "fastboot" commends. adb commend didn't work. when i type fastboot devices i get the serial no. of the device.
when i use the adb devices commend i get: "List of devices attached" and an empty line.
is it possible to fix this phone? thanx in advance.
Asilns said:
i can only access the white screen when i chose bootloader>recovery i get the /!\ sign.
i installed the USB driver and i was able to use only the "fastboot" commends. adb commend didn't work. when i type fastboot devices i get the serial no. of the device.
when i use the adb devices commend i get: "List of devices attached" and an empty line.
is it possible to fix this phone? thanx in advance.
Click to expand...
Click to collapse
adb only works within android since it's a debugger if I'm not mistaken. Try using fastboot to flash the system images of the stock rom back to their respective partitions. (ie. fastboot flash system system.img; fastboot flash boot boot.img; etc.)
You must be unlocked for that to work however.
problem solved
after almost 10 hours of research the solution was really easy.
1.download "recovery-RA-nexus-v1.6.2.img" and fastboot it using this commend:
fastboot-windows flash recovery recovery-RA-nexus-v1.6.2.img
2.flash a rom from SD card and everything should work fine
Hi,
I unlocked my motorola moto g2 dual sim, installed "Minimal ADB and Fastboot" and see the Android Device Motorola ADB Interface in the device Manager, activated USB Debugging and run the fastboot mode.
Now when I enter "adb devices" in my cmd.exe, I am getting always
"List of devides attaced " but noting followed.
When I write "adb recoot bootloader" I am getting
"error: device '(null)' not fount"
On my handy display I see
"Device is UNLOCKED. Status Code: 3
Transfer Mode: USB Connected
Cursor: "Normal Powerup"
...
USB connected"
How can I install twrp and unlook my motorola, if I can't reach the fastboot mode?!
When I start my handy normally, I get the serial if I put "adb devices" in the cmd window.
Can anybody give me a tipp?!
Have you tried flashing the recovery through fastboot? It looks like it is connected to me. Try flashing recovery. If it doesn't work, then try installing Moto drivers.
Sent from my Moto G 2014 using Tapatalk
Hello all
Please is it possible to install stock ROM or stock OTA update without ADB commands?
Some other way for install?
Because my watch blocking ADB authorization!!!
Simply not show confirmation ADB dialog window
I tryed everything around ADB and nothing
I´m on stock recovery for info...
Thank you very much for help :good:
Have a nice day for all
Somebody help me?
Thank you very much
https://forum.xda-developers.com/zenwatch-3/how-to/guide-how-to-revert-to-android-wear-1-5-t3635196
No adb commands required. To enter fastboot press and hold Upper button+ Center button on turned off watch.
Here you can find more useful info https://forum.xda-developers.com/zenwatch-3/how-to/guide-reboot-recovery-fastboot-unlock-t3546743
djdarkrider said:
https://forum.xda-developers.com/zenwatch-3/how-to/guide-how-to-revert-to-android-wear-1-5-t3635196
No adb commands required. To enter fastboot press and hold Upper button+ Center button on turned off watch.
Here you can find more useful info https://forum.xda-developers.com/zenwatch-3/how-to/guide-reboot-recovery-fastboot-unlock-t3546743
Click to expand...
Click to collapse
Thank you for reply but in both links are adb commands...
those are fastboot commands. You don't need adb popup on watch to use them.
djdarkrider said:
those are fastboot commands. You don't need adb popup on watch to use them.
Click to expand...
Click to collapse
I can't use adb commands because my device is unauthorized for adb commands
I can't authorize my watch because not showing pop up window for allow adb.
Note: all my other Android devices works fine for adb commands and authorization...
This mean that problem is in the watch...
Hoffmanns said:
I can't use adb commands because my device is unauthorized for adb commands
I can't authorize my watch because not showing pop up window for allow adb.
Note: all my other Android devices works fine for adb commands and authorization...
This mean that problem is in the watch...
Click to expand...
Click to collapse
I get it.
Those commands are typed in adb command line, when your watch are in FASTBOOT mode. There will be no authorization for fastboot mode. Turn your watch off, then press and hold power+upper buttons, until you are in fastboot mode(it will be written on watch screen). Then connect watch to pc and type "fastboot devices" in adb window.
Just try it. NO AUTHORIZATION REQUIRED
djdarkrider said:
I get it.
Those commands are typed in adb command line, when your watch are in FASTBOOT mode. There will be no authorization for fastboot mode. Turn your watch off, then press and hold power+upper buttons, until you are in fastboot mode(it will be written on watch screen). Then connect watch to pc and type "fastboot devices" in adb window.
Just try it. NO AUTHORIZATION REQUIRED
Click to expand...
Click to collapse
God bless you :laugh::good:
It's working :laugh:
I tryed many many things but not this
Thank you very much for your help and time :good::good::good:
Someone please.help...
tott2003 said:
Someone please.help...
Click to expand...
Click to collapse
1. Connect the USB cable from the side of the phone and make sure that developer mode and USB debugging is activated.
2. Connect your phone to the PC, make sure it's connected in data transfer mode.
3. Go to adb.exe and fastboot.exe folder, hold shift and right click to open CMD or PowerShell from there. If you open PowerShell use .\ before the command, if you are using CMD just type the command without it.
4. Type in CMD: "adb devices" without parenthesis, you should see your device serial number.
5. Type then in CMD: "adb reboot bootloader" without parenthesis, you will go to fastboot mode or the "Green Start Screen" after the phone boots.
6. Type "fastboot devices" you should see you device serial number. which means you can run fastboot commands without any issues.
P.S I am using PowerShell instead of CMD, so the pictures show the commands with .\ in the beginning.
Rashad83 said:
1. Connect the USB cable from the side of the phone and make sure that developer mode and USB debugging is activated.
2. Connect your phone to the PC, make sure it's connected in data transfer mode.
3. Go to adb.exe and fastboot.exe folder, hold shift and right click to open CMD or PowerShell from there. If you open PowerShell use . before the command, if you are using CMD just type the command without it.
4. Type in CMD: "adb devices" without parenthesis, you should see your device serial number.
5. Type then in CMD: "adb reboot bootloader" without parenthesis, you will go to fastboot mode or the "Green Start Screen" after the phone boots.
6. Type "fastboot devices" you should see you device serial number. which means you can run fastboot commands without any issues.
P.S I am using PowerShell instead of CMD, so the pictures show the commands with . in the beginning.
Click to expand...
Click to collapse
Cheers mate ?
Rashad83 said:
1. Connect the USB cable from the side of the phone and make sure that developer mode and USB debugging is activated.
2. Connect your phone to the PC, make sure it's connected in data transfer mode.
3. Go to adb.exe and fastboot.exe folder, hold shift and right click to open CMD or PowerShell from there. If you open PowerShell use .\ before the command, if you are using CMD just type the command without it.
4. Type in CMD: "adb devices" without parenthesis, you should see your device serial number.
5. Type then in CMD: "adb reboot bootloader" without parenthesis, you will go to fastboot mode or the "Green Start Screen" after the phone boots.
6. Type "fastboot devices" you should see you device serial number. which means you can run fastboot commands without any issues.
P.S I am using PowerShell instead of CMD, so the pictures show the commands with .\ in the beginning.
Click to expand...
Click to collapse
HOLY. ****ING. ****.
I have spent the past two days trying to figure this out. Not *one* other person on the internet, so much as I have seen, has mentioned using the side port. Seriously, you just made my day. Thank you so much! :good:
Created a new topic, disregard
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.