Database Users

if adb devices does not list device, can device be powered down immediately?

have tried to figure out how to turn off aria when connecting the usb and adb devices does not list device. reboot is the next step (volume up and power) and device always reboots and it seems impossible to hold down volume and power and get back into HBOOT / RECOVERY
question is, is it possible to reboot directly into HBOOT ?

Cancel the loop, reboot the phone, and send "adb reboot bootloader" from the prompt, when the HTC Quietly Brilliant screen appears.

seboj said:
Cancel the loop, reboot the phone, and send "adb reboot bootloader" from the prompt, when the HTC Quietly Brilliant screen appears.
Click to expand...
Click to collapse
how can I send *any* adb commands when I am unable to see device?

Can you see the phone in adb when it is powered on normally for use? If you can then when the HTC Quietly brilliant screen comes up your computer should be able to connect to the phone through adb. If it does not then you will want to uninstall HTC Sync and re-install it.. ( if you are running Window) make sure you have no anti-virus or malware scanners running/active as those create havoc causing HTC Sync to not install correctly and the drivers necessary for Windows to see the phone properly to not get installed.

Yes, I can see when normally connected but that was not my original question.
I do not have HTC Sync installed, only SDK USB drivers.
Repeat of my original question:
"..how to turn off aria when connecting the usb and adb devices does not list device. reboot is the next step.."
The reason I ask this, is that as I sit on the REBOOT screen and LOOP is running in background, if adb devices does not see phone, when I press power it will automatically reboot and power up all the way to main menu where I have to (again) do a total power shutdown in order to see HBOOT and RECOVERY.
I am trying to get faster to HBOOT and RECOVERY since adb devices is not listing device.
Is that clear now?

Your question was already answered in post 2. Use adb reboot bootloader at the quietly brilliant screen.

hi2u2 said:
Your question was already answered in post 2. Use adb reboot bootloader at the quietly brilliant screen.
Click to expand...
Click to collapse
wonderful. if only it worked, which it does not since adb (anything) does not work since adb (any command) does not see device

xdafly said:
wonderful. if only it worked, which it does not since adb (anything) does not work since adb (any command) does not see device
Click to expand...
Click to collapse
Have you actually tried though?
If you can see your phone in adb devices when it is loaded into Android, then you should be able to send the adb reboot bootloader after you reboot from recovery. The fact that the phone doesn't list during the loop is irrelevant. Once you've rebooted the phone from recovery, and the phone displays the Quietly Brilliant logo, then it has loaded enough to be recognized by the computer, and the adb command will work, and instantly reboot the phone into the hboot screen.
If the command doesn't work, double check to make sure your command prompt is in the right directory with all the right files, try installing Sync, and / or try reinstalling your driver.

[Q] ADB Way into recovery, bootloop

Okay so I flashed a rom and im stuck in a bootloop, but I cant get into recovery to restore a nandroid. My power button receded so as soon as I put in a battery it immediately turns on. But if i go into bootloader, not the power button nor the volume keys will work. So I cant get into recovery that way. Is there any other way like with adb in bootloader? Or am i screwed lol.
Thanks in advance for help, I could really use it.

adb reboot bootloader
adb reboot recovery
It should be obvious what they do. Bootloader won't do you much good without a power button.
Sent from my HTC Glacier using XDA App

estallings15 said:
adb reboot bootloader
adb reboot recovery
It should be obvious what they do. Bootloader won't do you much good without a power button.
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
I tried running adb in the bootloader but it wont connect to my phone. What exactly should I be typing to connect it? Its plugged in with a usb cord. Sorry, obviously im a huge newb

perhac89 said:
I tried running adb in the bootloader but it wont connect to my phone. What exactly should I be typing to connect it? Its plugged in with a usb cord. Sorry, obviously im a huge newb
Click to expand...
Click to collapse
if you are in bootloader mode, make sure the phone says FASTBOOT USB somewhere on the screen when connected to the computer.
then type
Code:
fastboot reboot (whatever it is you want to reboot to)
adb only works in recovery or android itself.

saranhai said:
if you are in bootloader mode, make sure the phone says FASTBOOT USB somewhere on the screen when connected to the computer.
then type
Code:
fastboot reboot (whatever it is you want to reboot to)
adb only works in recovery or android itself.
Click to expand...
Click to collapse
Then only thing Im getting is Hboot Usb Plug, not Fastboot Usb
Edit: Okay now I have Fastboot USB showing, but cmd doesnt recognize fastboot, nor will it connect to my device

Just boot the phone in the regular way.
While it boots, in bootanimation or even a bit before that, execute "adb reboot recovery".

Jack_R1 said:
Just boot the phone in the regular way.
While it boots, in bootanimation or even a bit before that, execute "adb reboot recovery".
Click to expand...
Click to collapse
All Im getting when I do this is error device not found

Bump.
I can't get it back into fastboot usb either, I think the power button fixed for a second before and selected fastboot.

Do you have a warranty on this phone?
If not, you may want to open it where you can access the power button more easily.
Before you do that though, get it caught in a bootloop and try adb reboot recovery. Reboot and try again at a different point. It should work eventually. Persistence might pay off.
Sent from my HTC Glacier using XDA App

perhac89 said:
All Im getting when I do this is error device not found
Click to expand...
Click to collapse
Since you're in the bootloop, your device is connecting and disconnecting. See when it connects (easily recognized Windows "USB device connected" sound), then execute "adb reboot recovery" until the command catches or the phone reboots. Attempt several times.
If it won't work - open the phone and fix the button.

Recovery mode, device not detected by Windows

ok, trying to follow the instructions to sideload the OTA update to kitkat here:
http://www.androidcentral.com/how-manually-update-your-nexus-tablet-kitkat
However, I am running into a problem with the recovery mode. it isn't seen by my PC. So adb cannot find my device to let me sideload the OTA.
adb sees my tablet when it is running normally, though. I was able to reboot into recovery using adb. It just lost the connection as soon as I was rebooted in recovery.
Does anyone know how to make windows see my tablet while it is in recovery mode?
Thanks,

brandonyoung said:
ok, trying to follow the instructions to sideload the OTA update to kitkat here:
http://www.androidcentral.com/how-manually-update-your-nexus-tablet-kitkat
However, I am running into a problem with the recovery mode. it isn't seen by my PC. So adb cannot find my device to let me sideload the OTA.
adb sees my tablet when it is running normally, though. I was able to reboot into recovery using adb. It just lost the connection as soon as I was rebooted in recovery.
Does anyone know how to make windows see my tablet while it is in recovery mode?
Thanks,
Click to expand...
Click to collapse
You need to pull up the recovery menu by clicking the power button and then clicking the volume up button and then letting go of both of them. then click the button that says something along the lines of sideloading an update via adb and then you're set to send the adb command. Be wary, however, I seemed to somehow brick my N10 earlier by doing this. I finally got it up and running (by what I'm calling luck) but it wasn't a fun hour.

sparkplugDev said:
You need to pull up the recovery menu by clicking the power button and then clicking the volume up button and then letting go of both of them. then click the button that says something along the lines of sideloading an update via adb and then you're set to send the adb command. Be wary, however, I seemed to somehow brick my N10 earlier by doing this. I finally got it up and running (by what I'm calling luck) but it wasn't a fun hour.
Click to expand...
Click to collapse
I can get to recovery, no problem there. I can select the option to sideload via adb. the problem is in Windows. Once my tablet is in recovery, the tablet is no longer seen by Windows, so the adb sideload command fails because it doesn't see the tablet is connected anymore,

brandonyoung said:
I can get to recovery, no problem there. I can select the option to sideload via adb. the problem is in Windows. Once my tablet is in recovery, the tablet is no longer seen by Windows, so the adb sideload command fails because it doesn't see the tablet is connected anymore,
Click to expand...
Click to collapse
I've heard that unplugging the device from the PC until you're in recovery mode might help. I would also suggest, if that doesn't work, to install the ADB drivers again once you're in recovery mode.

Go to device manager and you will probably see "Nexus 10" listed with no drivers installed.
Right click it an select properties, then Driver. Click Update Driver.
Select the browse option, then let me pick option, then click "Have Disk" and point it to the folder sdk\extras\google\usb_driver from the Android SDK you installed.
Then select the Android ADB driver.

garysargent said:
Go to device manager and you will probably see "Nexus 10" listed with no drivers installed.
Right click it an select properties, then Driver. Click Update Driver.
Select the browse option, then let me pick option, then click "Have Disk" and point it to the folder sdk\extras\google\usb_driver from the Android SDK you installed.
Then select the Android ADB driver.
Click to expand...
Click to collapse
When it is running, and usb debugging is enabled, it shows up under Android Phone as Android Composite ADB Interface.
I turn USB debugging off, and it shows up under Portable Devices as Nexus 10
I boot into the bootloader and it shows under Android Phone as Android Bootloader Interface.
but It doesn't show at all when I am in recovery

How are you connecting your N10 to your Windows machine? Are you using good USB cable? Are you using USB2 or USB3 port? Is the port attached to mobo directly, or is it on the case?
Some claim there can be issues with poor USB cables, using USB3 instead of USB2, or using port not directly on the mobo, so if you're doing any of those, I'd suggest trying a switch.
Also, I'm confused, has USB debugging on or off when you go into Recovery?

mevensen said:
How are you connecting your N10 to your Windows machine? Are you using good USB cable? Are you using USB2 or USB3 port? Is the port attached to mobo directly, or is it on the case?
Some claim there can be issues with poor USB cables, using USB3 instead of USB2, or using port not directly on the mobo, so if you're doing any of those, I'd suggest trying a switch.
Also, I'm confused, has USB debugging on or off when you go into Recovery?
Click to expand...
Click to collapse
I am connecting with a USB cable. I don't know if it is "good' or not, but it works with the tablet in all other modes. I was able to use adb to transfer files, reboot, etc. I was able to use fastboot to flash Chainfire's autoroot, and to flash the factory images.
I was using a USB2 port directly on my laptop, but I just tried the USB3 port and it didn't change anything.
Plugging it into my USB hub, and my hub did not detect that it was plugged in either while it was in recovery mode. It was detected when I rebooted back into the system.
USB debugging is on when I enter recovery. I used "adb reboot recovery" to reboot my tablet into the recovery mode

garysargent said:
Go to device manager and you will probably see "Nexus 10" listed with no drivers installed.
Right click it an select properties, then Driver. Click Update Driver.
Select the browse option, then let me pick option, then click "Have Disk" and point it to the folder sdk\extras\google\usb_driver from the Android SDK you installed.
Then select the Android ADB driver.
Click to expand...
Click to collapse
Thank you !!!!!!!!!

my lenovo a6000 shot no display but detecting n device manager.
it occured due to flash flash.rec.
please help me.

adb working with device booted, but not in bootloader

adb works fine when the devices is powered on, but once I reboot into the bootloader, it no longer recognizes the device. I am trying to sideload an OTA
I have tried to update to the latest USB drivers, but in Windows 10 I constantly get the error message "The folder you specified doesn't contain a compatible software driver for your device. If the folder contains a driver, make sure it is designed to work with Windows for x64-based systems".
Any advice?

scdavis0 said:
adb works fine when the devices is powered on, but once I reboot into the bootloader, it no longer recognizes the device. I am trying to sideload an OTA
I have tried to update to the latest USB drivers, but in Windows 10 I constantly get the error message "The folder you specified doesn't contain a compatible software driver for your device. If the folder contains a driver, make sure it is designed to work with Windows for x64-based systems".
Any advice?
Click to expand...
Click to collapse
Well... You can't use ADB in bootloader. Only fastboot commands work here.
While in bootloader, use volume up/down till you see "recovery mode". Press power button and you'll reboot to recovery.
Check this guide to sideload the ota:
https://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
2nd post...

Sorry I should say it also does not work on the prompt where I am supposed to type in the sideload command. I get a no devices found error.
Again it works fine when the phone is booted into the OS.

scdavis0 said:
Sorry I should say it also does not work on the prompt where I am supposed to type in the sideload command. I get a no devices found error.
Again it works fine when the phone is booted into the OS.
Click to expand...
Click to collapse
When entering recovery, are you sure you pressed power button + tapped volume up to see the recovery menu? And from there scrolled down and selected: apply update from ADB? Only from here your phone will be recognized...
Well, if you already did it, i'm not sure how the phone would not be recognized if it does when powered up... Maybe someone else already encountered the issue...

5.1 said:
When entering recovery, are you sure you pressed power button + tapped volume up to see the recovery menu? And from there scrolled down and selected: apply update from ADB? Only from here your phone will be recognized...
Well, if you already did it, i'm not sure how the phone would not be recognized if it does when powered up... Maybe someone else already encountered the issue...
Click to expand...
Click to collapse
Yes this is in fact what I am doing. I receive a device not found error, even though adb works with the device booted into the OS.
In fact, I can do:
adb reboot recovery
Then when recovery comes up:
adb devices
and list of devices attached is blank

I figured this out. I had to unplug and plug back in the phone once I got to the sideload step.

I had this exact issue with Nvidia shield TV. I had old or corrupt adb/fastboot. I redownloaded and set up my environment from scratch, adb worked and fastboot worked

Stuck at twrp loading screen, no other boot options is working.

hi!
So i've messed up my phone. I was formatting my data and as twrp was stuck for 15 minutes at done i forced rebooted my phone. after that i can only boot into twrp (not even edl mode) no matter which button combos i use. But the thing is, twrp is stuck at the loading screen. the phone is recognized in adb but it is recognized in recovery and trying to use the command "adb reboot edl" doesn't work, nothing happens.
What can i do? I was thinking about using some commands where the phone is recognized in adb as in recovery but i have no idea what to do.

senny22 said:
hi!
So i've messed up my phone. I was formatting my data and as twrp was stuck for 15 minutes at done i forced rebooted my phone. after that i can only boot into twrp (not even edl mode) no matter which button combos i use. But the thing is, twrp is stuck at the loading screen. the phone is recognized in adb but it is recognized in recovery and trying to use the command "adb reboot edl" doesn't work, nothing happens.
What can i do? I was thinking about using some commands where the phone is recognized in adb as in recovery but i have no idea what to do.
Click to expand...
Click to collapse
both volume buttons + plug the wire doesn't work?

senny22 said:
hi!
So i've messed up my phone. I was formatting my data and as twrp was stuck for 15 minutes at done i forced rebooted my phone. after that i can only boot into twrp (not even edl mode) no matter which button combos i use. But the thing is, twrp is stuck at the loading screen. the phone is recognized in adb but it is recognized in recovery and trying to use the command "adb reboot edl" doesn't work, nothing happens.
What can i do? I was thinking about using some commands where the phone is recognized in adb as in recovery but i have no idea what to do.
Click to expand...
Click to collapse
I have exactly the same problem, could you solve it? I'm very worried about my phone

ale0796 said:
I have exactly the same problem, could you solve it? I'm very worried about my phone
Click to expand...
Click to collapse
Hi! When I held both volume buttons and the power I dunno in what mode I was in but while my phone was on this mode and plugged in to my PC it was recognized in device manager as ADB something (I don't remember). I was shocked when I saw that my PC would recognize the phone because no LEDs was lit (not even the red LED you get in edl mode) and also my phone would start instantly with pressing the power button, (in edl it takes about 10 to restart the phone). Anyway so I tried zadig, Qualcomm drivers and even a different pc but it would still connect as ADB something. Lastly I disabled automatic driver updates in windows and installed the qualcomm axon 7 firmware driver (Google it). After that I rebooted and my phone was now recognized as "qualcomm hs loader" something and so I could use Miflash to flash a stock firmware. Miflash would work right away though but after maybe 15 tries and lots of reboots it then worked for some reason I don't know. After that I had a stock recovery back and it was all going smooth again from there.

senny22 said:
Hi! When I held both volume buttons and the power I dunno in what mode I was in but while my phone was on this mode and plugged in to my PC it was recognized in device manager as ADB something (I don't remember). I was shocked when I saw that my PC would recognize the phone because no LEDs was lit (not even the red LED you get in edl mode) and also my phone would start instantly with pressing the power button, (in edl it takes about 10 to restart the phone). Anyway so I tried zadig, Qualcomm drivers and even a different pc but it would still connect as ADB something. Lastly I disabled automatic driver updates in windows and installed the qualcomm axon 7 firmware driver (Google it). After that I rebooted and my phone was now recognized as "qualcomm hs loader" something and so I could use Miflash to flash a stock firmware. Miflash would work right away though but after maybe 15 tries and lots of reboots it then worked for some reason I don't know. After that I had a stock recovery back and it was all going smooth again from there.
Click to expand...
Click to collapse
THANK YOU SO MUCH, after 30 more attempts, I get the xiaomi miflash flashed my device, the last thing I tried was to disconnect the phone, keep the power button for 10 seconds and then connect it. The device was recognized as "Qualcomm HS-USB QDLoader 9008" download this rom https://build.nethunter.com/misc/axon7/A2017U_B15-NEW_FULL_EDL.zip unzip it and select the folder with miflash and flash it. Miflash did not send me the "can not get hello package" message anymore. I really appreciate it a lot, without your message I would probably have kept my phone in a box and forget it. I hope all people can read this comment and solve this problem. THANK YOU

ale0796 said:
THANK YOU SO MUCH, after 30 more attempts, I get the xiaomi miflash flashed my device, the last thing I tried was to disconnect the phone, keep the power button for 10 seconds and then connect it. The device was recognized as "Qualcomm HS-USB QDLoader 9008" download this rom https://build.nethunter.com/misc/axon7/A2017U_B15-NEW_FULL_EDL.zip unzip it and select the folder with miflash and flash it. Miflash did not send me the "can not get hello package" message anymore. I really appreciate it a lot, without your message I would probably have kept my phone in a box and forget it. I hope all people can read this comment and solve this problem. THANK YOU
Click to expand...
Click to collapse
Really glad I could help