I recently employed the use of adb get-state and decided to know further about it. Running adb inter alia shows:

adb get-state                - prints: offline | bootloader | device

I intend to know under what circumstance(s) would that command return bootloader.

As of now I'm aware of these outputs:

  • device: booted into Android OS, debugging enabled and authorized
  • recovery: booted into recovery environment
  • sideload: during side-loading
  • unauthorized: booted into Android OS, debugging enabled but not authorized yet
  • offline: wireless device not in reach. (There may be other reasons.)
  • unknown: When adbd not detected at other side. At least that's what I understand of it. Occurs in case of debugging being disabled or device not plugged in.

I'm yet to know about the following two outputs:

  • host
  • bootloader

I found all those outputs here with no added explanation.

Before you ask,

  • yes, I've already ran that command when my Nexus 6 was booted into bootloader mode and I received unknown as output;
  • it is mere curiosity with nothing that it would solve in particular as of now.
  • If I may dare a guess, I'll say that the bootloader string can be outputted only if you find a way to start adbd after booting into the bootloader. This guess is based on the fact that, by issuing adb get-state from a Windows machine to a device booted into Android, I got unknown. Only by manually launching adbd on the Android with start adbd, was I able to have my Windows machine's adb outputting device. – Death Mask Salesman May 13 '16 at 8:15
  • @DeathMaskSalesman I don't think I'm following you. Consider addressing these points: 1) Did you verify on the device's screen that the device was indeed in bootloader mode? Which device did you use? 2) How were you able to start adbd at all? If you are talking about adb shell start adbd then it is technically impossible thing. – Firelord May 13 '16 at 9:14
  • The device output was obtained with the Android device booted into... Android. The main OS. Now, let's come to the two points: 1) Samsung devices' bootloader mode is the famed Odin mode, obtained by issuing adb reboot bootloader. My device is a Samsung Galaxy S4 Mini (GT-I9195, or serranoltexx); 2) As said in the prologue, starting adbd seems to be possible only from recovery or the OS itself. Launching it from the bootloader is one of my many crazy theories, but adb does not recognize a phone if in bootloader mode. – Death Mask Salesman May 13 '16 at 9:21

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.