I want commands of msys on widows7 for fastboot android phone from normal mode (without switch off phone). Please, post available commands for fastboot android phone in normal mode or any alternative.
I have tried "adb reboot -bootloader" but it's not working.
thanks
amar.
http://forum.xda-developers.com/showthread.php?t=2472970
Only thread I found in my quick search that was well, my problem.
After accidentally hitting Factory Reset, I managed to lose all USB connectivity functionality.
I CAN boot into bootloader.
I CAN boot into recovery.
ADB - no response.
Fastboot - no response.
Connecting my computer USB cable to my phone in the bootloader screen doesn't even change to "Fastboot USB" anymore.
I have Windows 8 on my desktop and I just tried connecting it to my buddys laptop to see if that would change, and no luck.
Fastboot pulls zero devices in command prompt, and adb (obviously) doesn't either.
Mounting SD/USB in Recovery does nothing and isn't detected by either pc's.
Any ideas?
Windows 8 64-bit
TWRP Recovery - 2.6.3.0
HTC BMP USB Driver 1.0.5375
HTC Driver Installer 4.5.0.001
Android Debug Bridge 1.0.31
SuperCID
TKTAB911 said:
http://forum.xda-developers.com/showthread.php?t=2472970
Only thread I found in my quick search that was well, my problem.
After accidentally hitting Factory Reset, I managed to lose all USB connectivity functionality.
I CAN boot into bootloader.
I CAN boot into recovery.
ADB - no response.
Fastboot - no response.
Connecting my computer USB cable to my phone in the bootloader screen doesn't even change to "Fastboot USB" anymore.
I have Windows 8 on my desktop and I just tried connecting it to my buddys laptop to see if that would change, and no luck.
Fastboot pulls zero devices in command prompt, and adb (obviously) doesn't either.
Mounting SD/USB in Recovery does nothing and isn't detected by either pc's.
Any ideas?
Windows 8 64-bit
TWRP Recovery - 2.6.3.0
HTC BMP USB Driver 1.0.5375
HTC Driver Installer 4.5.0.001
Android Debug Bridge 1.0.31
SuperCID
Click to expand...
Click to collapse
What recovery/
Sent from my HTC One XL using XDA Premium 4 mobile app
im trying to enter fastboot from bootloader but every time i select it, it just reloads the bootloader. everything else works fine.
the bootloader IS fastboot mode.
Well when I run fastboot protocol nothing happens
strker45 said:
Well when I run fastboot protocol nothing happens
Click to expand...
Click to collapse
Get into Bootloader. (I use ADB command: ADB Reboot Bootloader)
Use the volume down button to select "Fastboot Protocol."
It is deceptive as the screen on your Shield won't change.
Use your fastboot commands now. See if that works.
You need to make sure your fastboot and adb drivers are installed and recognized.
Also need fastboot on your pc of course. Good luck.
Once again, the bootloader is fastboot on your tablet, if you are on that screen then you can use fastboot if the above conditions are met.
Same symptom here.
When Android is loaded, Win10 finds it as both MTP and USB debugging device. adb is reporting back. All well.
However, when shield is in fastboot mode, fastboot finds nothing.
In my case reason was driver:
when connected in fastboot mode, win10 wants to install an
Android Device -Android Bootloader Interface
=> you see this in device manager
To satisfy Win10, download NVIDIA USB driver from here
https://developer.nvidia.com/shield-open-source
hence point the driver install in Win10 device manager to the driver download/extract location
Reconnect your shield.
In my case this worked.
Hope this helps
vrmuhr said:
To satisfy Win10, download NVIDIA USB driver from here
https://developer.nvidia.com/shield-open-source
hence point the driver install in Win10 device manager to the driver download/extract location
Click to expand...
Click to collapse
Thank you, worked very well for me.
Hi,
I'm trying to boot a twrp image on my Motorola One Vision without flashing it or rooting the phone.
I've unlocked the boot loader and enabled developer options and set USB to debugging. When I connect the phone to the computer and use ./adb devices it is detected fine. When I disconnect, reboot and enable fastboot and when the menu is up connect it to the computer again it will not detect the phone. ./adb devices give no output and ./fastboot boot /PATH/TO/IMAGE.FILE just gives the output "waiting for device". I've tried from both my windows partition and Linux Debian with the same result. Cables are fine as I can use adb to pull files and such- It's basically in the fastboot menu that it doesn't seeem to respond.
The phone is running Android 10 Kane 4.14. I've tried twrp 3.4 but I don't think the image is the issue since it won't respond to commands in fastboot.
Does anyone have any suggestions for troubleshooting this? Any and all help is appreciated.
Kind regards
Magnus
Cardinal_Vice said:
Hi,
I'm trying to boot a twrp image on my Motorola One Vision without flashing it or rooting the phone.
I've unlocked the boot loader and enabled developer options and set USB to debugging. When I connect the phone to the computer and use ./adb devices it is detected fine. When I disconnect, reboot and enable fastboot and when the menu is up connect it to the computer again it will not detect the phone. ./adb devices give no output and ./fastboot boot /PATH/TO/IMAGE.FILE just gives the output "waiting for device". I've tried from both my windows partition and Linux Debian with the same result. Cables are fine as I can use adb to pull files and such- It's basically in the fastboot menu that it doesn't seeem to respond.
The phone is running Android 10 Kane 4.14. I've tried twrp 3.4 but I don't think the image is the issue since it won't respond to commands in fastboot.
Does anyone have any suggestions for troubleshooting this? Any and all help is appreciated.
Kind regards
Magnus
Click to expand...
Click to collapse
If ur phone is detected by adb don't disconnect and hit adb reboot bootloader, it worked for me than when ur in bootloader type:
fastboot flash vbmeta vbmeta_patch.img
fastboot erase userdata
fastboot erase cache (not necessary)
and boot to recovery
I have access to fastboot and EDL mode. Does this mean that I can also access the mode that will show the phone after the adb devices command?
If device gets booted into FASTBOOT or EDL mode then it can't additionally get accessed via ADB: this can only get achieved when device got booted into RECOVERY mode.
To clarify:
ADB ( short for Android Debug Bridge ) deals - as its name implies - with a device's Android OS.
FASTBOOT deals - as its name implies - with device's bootloader, if that isn't bricked.
EDL ( short for Emergency Download Mode ) - specific to devices with a Qualcomm Snapdragon chipset - deals with the device itself, is used if bootloader is bricked.
Thank you for your quick help. Is it possible to access adb during bootloop?
I entered something called recovery mode, but the computer doesn't recognize that any device has been connected - adb devices doesn't see anything either.
On one of the pages I read this information:
Spoiler
Ed Reynolds says:
December 2, 2018 at 4:31 am
Unfortunately, there really is no “recovery” per set, yet. There is a mode where one can factory reset the phone which can be reached using the hardware buttons. However, from there, you cannot do anything other than reboot to a simpler form of phone. There are no options to go into bootloader or Fastboot mode. ADB won’t get you there. Sometimes, using ADB, you can boot into a simple android recovery with no command! There you remain until hard booting back it back into full functionality. Developer is apparently working on it
Reply
Deepak Gupta says:
December 2, 2018 at 4:38 am
Hi Ed Reynolds,
Thanks for sharing your knowledge. We appreciate your efforts. Yes, stock recovery doesn’t offer many options. One has to install a custom recovery like TWRP to get over this problem and to maximize productivity.
Reply
Ed Reynolds says:
December 8, 2018 at 7:48 pm
That is correct. but, in order to install a custom recovery, one must be able to get into bootloader, in some way. Either through physical buttons or through the ADB tool. forget about using the physical buttons – they get you to the recovery that you mention, but cannot get you into Fastboot (bootloader) mode. If you use the ADB tools while in this particular recovery mode, and try to reboot into bootloader mode from there, it boots back into the system. So, using that route, you cannot ever get to a place where you can install TWRP or anything else, for that matter – including applying an unlocking code if one were available. Next, if you try to get into recovery mode using the ADB tools (not the physical buttons, you do arrive at a more “conventional” recovery — with the picture of the little Android symbol, etc. However, there are no commands to use to get into Fastboot or bootloader mode. I have had this problem before and sometimes, using the physical buttons, you can reveal commands at this stage. However, even here, no combination of physical buttons reveals any commands. Then, as a last ditch effort, you use the ADB tools to boot into bootloader mode, you return to the system! The result is, again, you cannot install any sort of custom recovery because there is no internal or external way to flash it. If you have overcome this problem, please share! It is very frustrating! Thanks. Ed
Does this mean that I will need to flash custom recovery to gain access via adb during bootloop?
Android's Recovery is nothing else than a minimalistic working Android OS, comparable to Windows Recovery Environment ( WinRE ), so it's accessible via ADB.
A Custom Recovery ( like TWRP ) isn't needed at all, because such a only is an UI version operable by touches.
So if Windows don't see device when is in recovery mode (but recognize correctly when is in fastboot mode), there is a problem with drivers?
I want to access to adb pull for backup. Device is rooted with unlocked bootloader and allowed USB debugging and no PIN password, but bootlooped after trying to restart after uninstalling YouTube app
OMG
when in Recovery mode then you've to connect device via USB-cable with computer and you can launch adb pull command on computer.
When I in recevery mode, computer not recognize it - adb commands not working, device manager don't see any device. When I on fastboot or EDL, computer recognize phone, commands working and device manager shows device on list
Then obviously USB Debugging didn't get enabled in Android's Developer Options.
Robert997 said:
When I in recevery mode, computer not recognize it - adb commands not working, device manager don't see any device. When I on fastboot or EDL, computer recognize phone, commands working and device manager shows device on list
Click to expand...
Click to collapse
As the other user said, USB Debugging is not enabled or proper drivers are not installed. The drivers for fastboot and adb are different. Search for correct drivers, disable driver signing in Windows and install the drivers.