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.

Stuck unlocking my Atrix.

I'm currently attempting to root my atrix but I've come across a problem that I can't seem to be able to solve through googling or otherwise.
I'm using the tutorial stickied on the Atrix homepage labelled [HOWTO MAY16].
I got as far as step 8 and my phone passed the sbf flash using RSD lite but continuing on with the process to step 13 where it is asking me to type "fastboot oem unlock" into cmd I get an error message telling me that cmd is waiting for my device but nothing seems to happen.
I've tried reinstalling drivers (64 bit), restarting computer, restarting phone, trying different leads/usb sockets with no change to my result.
The exact thing that I'm doing with cmd is to navigate to the platform-tools folder, open adb, open flashboot and then attempt fastboot oem unlock.
Additional information:
UK Orange Atrix 4G running 3.4.4
using IHOP sbf file
running windows 7 64-bit, using the 64-bit drivers.

Do you have access to win 7 or xp? Win 8 is really new and possibly that could be the problem. Worth a shot.

pre4speed said:
Do you have access to win 7 or xp? Win 8 is really new and possibly that could be the problem. Worth a shot.
Click to expand...
Click to collapse
Ops, typo. I'm running Windows 7 64-bit. I'll edit my post when xda allows me to.

Unlock
Enter the bootloader program by powering off the phone, Hold the volume down key and the power at the same time. The phone will be in the bootloader program when it powers up, use the volume down key to scroll through bootloader menu options. the second option will be fastboot program. Select the fastboot option with the volume up key, this will enter the fastboot mode of operation. Connect the phone to the PC via USB cable. Enter the directory where the fastboot program resides on the PC. Type the Fastboot oem unlock command. If sucessful a message will display on PC retuned by the phone. Reboot phone and unlocked will display in the upper left corner of the phones display. Continue to follow the original post, flash recovery, root phone, flash custom ROM. Happy Flashing, Enjoy! :fingers-crossed:

fdaconta said:
Enter the bootloader program by powering off the phone, Hold the volume down key and the power at the same time. The phone will be in the bootloader program when it powers up, use the volume down key to scroll through bootloader menu options. the second option will be fastboot program. Select the fastboot option with the volume up key, this will enter the fastboot mode of operation. Connect the phone to the PC via USB cable. Enter the directory where the fastboot program resides on the PC. Type the Fastboot oem unlock command. If sucessful a message will display on PC retuned by the phone. Reboot phone and unlocked will display in the upper left corner of the phones display. Continue to follow the original post, flash recovery, root phone, flash custom ROM. Happy Flashing, Enjoy! :fingers-crossed:
Click to expand...
Click to collapse
I just gave it another try and it gets stuck after I type fast boot oem unlock. I definitely have the right directory but I still get stuck here. Cmd just tells me it's waiting for my device and stops there. I think it's a driver issue after a bit of googling but the official drivers aren't working. This socks.

I had a similar problem with my device not showing up. There wasn't really a big fix for it but I just waited longer before trying to execute the command. I'm not sure if you're experiencing the same thing I did but when it couldn't detect my device it just hadn't been recognized by the computer yet. Make sure your drivers are working (connect usb and select every option on the pull down menu and are sure the device gets installed). After that do the same thing as before for fastboot but make sure you securely plug it in and wait for the computer to detect your phone before you move forward
Sent from my MB860 using xda app-developers app

[Q] Cant access bootloader

Hi,
I ran into a problem with my Nexus 4, the plan was to unlock the bootloader using my mac and fastboot. (used this as information but didn't follow it step by step, youtube.com/watch?v=fHZJ2f6JLw0)
I turned off the phone and went into the bootloader with volume down + power button. From here i used "fastboot devices" to secure that i was able to communicate with the phone. My device showed up together with an error message saying "ERROR: could not get pipe properties nexus 4".
Before doing any more i wanted to understand what this message meant so I searched the web without any success. I booted up my android, turned on usb debugging and used "adb devices". This time only my devices showed up and no error messages. I used the "adb reboot boatloader" to access the bootloader once again.
I still had the same error message with "flashboot devices" as before.
From here i didn't do anything more, I may have disconnected the usb from the computer while the terminal window was open and the phone in bootloader but without running any command from fastboot.
So I didn't run "fastboot oem unlock" or anything else.
I turned off the phone and tried to access the bootloader one more time with the volume down + power button. It didn't respond to this any more and nothing happened, the device just stayed turn off.
I turned on the phone and tried to use adb to access the bootloader but now when running the "adb devices" it just responds "-bash: adb: command not found".
I have tried to restore the phone thru the android setting meny without any success. The phone is working fine without any problem except i cant access the bootloader or use adb.
So I desperately need help from you guys. :crying:
Have any of you heard of this problem before?
Regards Rasmus

I have to change my statement.
Actually I succeeded rooting and installing CWM recovery using a win7 computer together with Nexus4 toolkit.
The issue i have right now is that i can't start the device into bootloader using volume and power buttons.
To access bootloader i have to go thru the toolkit and this can be an issue in case i flash a bad rom or kernel and can access android usb debugging.
Is it possible to restore the bootloader?

rallanand said:
The issue i have right now is that i can't start the device into bootloader using volume and power buttons.
Click to expand...
Click to collapse
Are you holding the down volume and pressing the power button?

What OS is the computer that you are using? If you have reset the device, make sure that USB debugging is checked again. I know it sounds dumb, but a lot of times it's the simplest things we forget. Once you factory reset your device, it resets everything.
If you are on Windows 7, make sure you are starting the command prompt from the same location your adb is installed. If you are on Ubuntu or another Linux distro, please let me know which one. This seems like it should be an easy fix for you, but a little more info is needed. Thanks!

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.

nexus 6p not showing on device manager

Hi, my 6p will not show up on my PC. Have tried installing drivers, different PC, different cable but nothing works.
I recently upgraded to android O. I extracted the files from system image and flashed boot image, vendor image, and system. But now when I try to go into recovery it says no command and I lost root access but my bootloader is unlocked. I never flashed the recovery thinking TWRP would stay intact but I guess I was wrong. Normally I would just use ADB and fix it but hence my problem. Is there any way to root without PC or any way I can fix my situation?

Having the same exact issue here, hope someone has a way to fix it.

sonysingh1983 said:
Hi, my 6p will not show up on my PC. Have tried installing drivers, different PC, different cable but nothing works.
I recently upgraded to android O. I extracted the files from system image and flashed boot image, vendor image, and system. But now when I try to go into recovery it says no command and I lost root access but my bootloader is unlocked. I never flashed the recovery thinking TWRP would stay intact but I guess I was wrong. Normally I would just use ADB and fix it but hence my problem. Is there any way to root without PC or any way I can fix my situation?
Click to expand...
Click to collapse
So your phone will boot into the OS, or not? If so, make sure USB debugging is set to "on" in Developer Settings. Can you put your device in fastboot mode by holding down the volume down button before hitting the power button? The "no command" means you are in (stock) recovery. You then have to hold the power button down while using the volume buttons to navigate. Power button is confirm. Get your phone into bootloader mode and use ADB to flash TWRP again. @meoshe

v12xke said:
So your phone will boot into the OS, or not? If so, make sure USB debugging is set to "on" in Developer Settings. Can you put your device in fastboot mode by holding down the volume down button before hitting the power button? The "no command" means you are in (stock) recovery. You then have to hold the power button down while using the volume buttons to navigate. Power button is confirm. Get your phone into bootloader mode and use ADB to flash TWRP again. @meoshe
Click to expand...
Click to collapse
Yes phone is working fine. Debugging is on. Can't use ADB phone does not get recognized by PC, only charges. Dint even get the pull down notification once I connect usb. Tried changing connection to mtp in developer options also. Nada. Nothing works to fix it. I'm thinking my charging port might have something wrong with it I don't know. I'm stuck not having root atm.

sonysingh1983 said:
Yes phone is working fine. Debugging is on. Can't use ADB phone does not get recognized by PC, only charges. Dint even get the pull down notification once I connect usb. Tried changing connection to mtp in developer options also. Nada. Nothing works to fix it. I'm thinking my charging port might have something wrong with it I don't know. I'm stuck not having root atm.
Click to expand...
Click to collapse
Gotcha. What about the other points? Entering bootloader mode from a powered off state, and that you are in Recovery mode (no command), and navigating thru it with the power+volume buttons?

v12xke said:
Gotcha. What about the other points? Entering bootloader mode from a powered off state, and that you are in Recovery mode (no command), and navigating thru it with the power+volume buttons?
Click to expand...
Click to collapse
Yes that works. Thank you. But still can't root phone and can't flash TWRP. Was looking at a root APK but not sure if they will work with O. If I could root then I could install TWRP thru it's app but I need root for that.

You can't root the phone until you have a working custom recovery. Focus on either fastboot flashing or fastboot booting TWRP.img

v12xke said:
You can't root the phone until you have a working custom recovery. Focus on either fastboot flashing or fastboot booting TWRP.img
Click to expand...
Click to collapse
How do I go about fastboot booting TWRP image?
I can get into bootloader from phone but I can't use a PC.

I did read your OP, but this sounds like a driver issue. There are two drivers that need to be installed first the USB and then fastboot. Since you can boot the device and use it, maybe you should try NRT by Wugfresh to install, test and confirm the drivers are properly installed. Booting or flashing TWRP is just a different command. Instead of fastboot flash recovery twrp.img, you use fastboot boot recovery recovery.img. The NRT toolkit can also either boot or flash a recovery image.
EDIT: Also try "Revoking ADB debugging" and re-enabling @sonysingh1983

sonysingh1983 said:
Yes phone is working fine. Debugging is on. Can't use ADB phone does not get recognized by PC, only charges. Dint even get the pull down notification once I connect usb. Tried changing connection to mtp in developer options also. Nada. Nothing works to fix it. I'm thinking my charging port might have something wrong with it I don't know. I'm stuck not having root atm.
Click to expand...
Click to collapse
Hi, just tried the mtp setting in developer options. Didn't get it the first time but now am able to access internal storage. I have plug sound app from play installed and I get a notification sound when plugging and unplugging. First try there was no sound when changing from charging to mtp. Ok after repeating it. Hope that helps.

Just as a follow up I got my win10 pc to recognize my O flashed nexus. I booted into bootloader after I had updated my sdk and drivers through android studio. It recognized the phone but nothing was happening. I rebooted into the os and the access allow prompt popped up on the phone and adb was able to see it under listed devices.