Develop Bugs

[Q] ADB recognizes device but not in recovery

Hi! I want to update my girlfriend's GNex by pushing update via recovery. I have adb working and recognizing device when it's turned on (with debugging mode). But when I go to recovery (adb reboot recovery), I can't get my device recognized again - "adb devices" shows nothing. I figured it can't be problem with drivers (since the device is recognized when turned on?), I must be doing something else wrong? But I have no idea where to look.
Sorry for the (probably) common question, but all I've found (using search) is adb not recognizing devices at all. I've been only using "fastboot" commands so far, and I never had problems with recognizing.

Joplisan said:
Hi! I want to update my girlfriend's GNex by pushing update via recovery. I have adb working and recognizing device when it's turned on (with debugging mode). But when I go to recovery (adb reboot recovery), I can't get my device recognized again - "adb devices" shows nothing. I figured it can't be problem with drivers (since the device is recognized when turned on?), I must be doing something else wrong? But I have no idea where to look.
Sorry for the (probably) common question, but all I've found (using search) is adb not recognizing devices at all. I've been only using "fastboot" commands so far, and I never had problems with recognizing.
Click to expand...
Click to collapse
what recovery are you using? in twrp, in advanced menu, theres a adb sideload option.

The problem is that her phone is locked, everything is stock. The only option is adb sideload (as far as I know). Any suggestions? I really don't have a clue.
Sent from my Galaxy Nexus using my thumbs.

Stock recovery does not offer the ADB interface, so adb commands will not work. You need to flash a custom recovery such as CWM or TWRP.

Ahhh, I didn't know that. I guess I have to wait for the ota, then, since I can't flash or use custom recovery. Thank you for your help!
Sent from my Galaxy Nexus using my thumbs.

Actually you can use adb commands in stock recovery - this works on build number JRN84D and newer only (JRN84D corresponds to 4.1, the first Jelly Bean build).
1) Reboot your device into the stock recovery (i.e., the screen with the Android on its back with the "!");
2) Access the stock recovery menu by pressing power and volume up;
3) Select "Apply update from ADB";
4) Download the correct update for your build and place it in the same directory as your ADB binary;
5) Open a command prompt in the same directory as your ADB binary;
6) Type adb devices to make sure that your device is recognized;
7) Type adb sideload name-of-file.zip
8) Reboot. Done.
Click to expand...
Click to collapse
This is from Method 4 in http://forum.xda-developers.com/showthread.php?t=1419170
Hope this helped

[Q] How do you access fastboot?

Hey everyone, so about a week ago I decided to flash the wrong rom (not intentionally) on my phone. I used the LGflashtool. Now I cannot access download mode at all and when i turn it on all it does is stay on the LG logo. When I turn on the phone and i hold up the volume up button it starts up fastboot and looks like this
[40690] Fastboot Mode Started
[40780]---reset--
[40780]---portcharge---
[40990] fastboot: processing commands
but when i try to run the command "adb devices" in the command prompt (C:\Users\chris\AppData\Local\Android\sdk\platform-tools (folder path)) it does not show my device at all. Also when i try to run the command "adb reboot" it says "Error: device not found"
Is there a way for my computer to see my device?
Thanks in advance

Returning to Stock, fastboot doesn't seem to exist.

I am trying to return to stock on my T-Mobile HTC One M8 using the nandroid backups thread that @ckpv5 put up here. I need to get all the information using "fastboot getvar all", but fastboot devices doesn't list anything. My device is listed when I type in "adb devices". USB debugging is enabled. When I type in "adb reboot fastboot", my device just restarts. When I type "adb reboot bootloader", it brings me to the bootloader. I choose reboot fastboot, but fastboot devices still doesn't list anything.
My adb and fastboot drivers are from the "Minimal ADB and Fastboot" thread here.
What is the issue?
Update 1: I re-installed the HTC drivers that come with HTC Sync Manager and it has worked so far.
I GOT IT TO WORK. THANKS ANYWAYS!

Does ADB work with locked bootloader?

I have a LG G7 (LM-G710EM) with locked bootloader (stock version: V10h). I can easily enter fastboot mode. When I send the command "fastboot devices" (from a command window running ADB) it returns a list with the serial number of my device. So, it seems to work. But if I run the command "ADB devices" then I receive an empty list.
I don't want to unlock the bootloader. I just want to send specific commands required by some app to work properly without the need to be root. For example BetterBatteryStats requires the ADB command "adb -d shell pm grant com.asksven.betterbatterystats android.permission.DUMP".
I did already in my Moto G5+ with stock 7.0 (locked bootloader) and it worked. Is it possible to do the same in my LG G7 without unlocking the bootloader?

I just ran into a similar issue when giving BBS permissions. The solution that worked for me on my Verizon G7 was to select the USB connection notification then go to Photo Transfer mode. Right after that I got the authorization request on the phone to grant debugging permission to my computer. After that adb devices showed the phone. Hopefully that same tip helps.

ADB doesn't work in fastboot mode.

LameMonster82 said:
ADB doesn't work in fastboot mode.
Click to expand...
Click to collapse
at the end I discovered what was wrong. to enter ADB commands there is no need to enter fastboot mode, just connect the phone (already switched on) to the PC and accept the connection from that PC. Then opening a CMD window, it's enough to type the command "adb devices" and the serial number of the phone appears, telling that the phone is ready to accept adb commands. uhff!!

LG G7 ThinQ ADB devices - nothing appears, no matter what I try (all of the above and some other stuff!) I can only assume that Sprint have had this thing so locked up, even ADB can't help! Any ideas?

In fastboot mode, message "OTG NOT MOUNTED, File NOT FOUND"

I have used the SDK tools trying to root my M9.
Activated developper mode, OEM unlocking end usb debugging.
In bootloader mode I can use the command line "adb devices" and it list in terminal a number for the device.
If I do the same in fastboot mode ("adb devices" at command line) then it doesn't show any device number and keeps searching.
When in fastboot mode I got the following message:
SD MOUNTED
OTG NOT MOUNTED
File NOT FOUND
Can somebody help me to solve this issue pls!!

mgbeek68 said:
I have used the SDK tools trying to root my M9.
Activated developper mode, OEM unlocking end usb debugging.
In bootloader mode I can use the command line "adb devices" and it list in terminal a number for the device.
If I do the same in fastboot mode ("adb devices" at command line) then it doesn't show any device number and keeps searching.
When in fastboot mode I got the following message:
SD MOUNTED
OTG NOT MOUNTED
File NOT FOUND
Can somebody help me to solve this issue pls!!
Click to expand...
Click to collapse
Why don't you just install twrp using fastboot then flash magisk?