Does ADB work with locked bootloader? - LG G7 ThinQ Questions & Answers

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?

Related

How can I unlock bootloader on my HTC Desire 526 G dual sim? Help

I tried four times to unlock bootloader on this device with pc, but all times I FAILED.
I tried change USB port.
I tried this:
Open cmd with admin permission
" CD AppData\Local\Android\android-sdk\platform-tools"
"adb devices" (Now pc recognize me)
"adb reboot bootloader" (My phone reboot in bootloader mode showing the message "=> FASTBOOT Mode"
now I Type "fastboot devices" and my device isn't showed
HELP ME PLEASE!!!!
Hey There,
You should have fastboot devices on ur PC then put your device into fastboot mode , open command prompt from fastboot folder (after you have installed fastboot) and type this command
fastboot devices
(ABCDEFGHI fastboot) you should see your phone
then type
fastboot oem unlock#
a option will come on your phone use the volume keys
after typing this command it shows vol up for unlock bootloader and vol down for do not unlock bootloader . but when i press vol up key it shows unlock failed (((
I am having a hard time getting the he bootloader to unlock are there any chance there is a website that has a simple software one click any were
Leonardo.Silvagni said:
I tried four times to unlock bootloader on this device with pc, but all times I FAILED.
I tried change USB port.
I tried this:
Open cmd with admin permission
" CD AppData\Local\Android\android-sdk\platform-tools"
"adb devices" (Now pc recognize me)
"adb reboot bootloader" (My phone reboot in bootloader mode showing the message "=> FASTBOOT Mode"
now I Type "fastboot devices" and my device isn't showed
HELP ME PLEASE!!!!
Click to expand...
Click to collapse
Here you can find unlocking tools and steps for htc 526g dual sim
http://4pda.ru/forum/index.php?showtopic=699986&st=140#entry47210746
Dont forget to press thanks:good:

fastboot never start after update to android 6

Hy
I had an unlocked bootloader phone. Yesterday I flashed the new Android 6, Europe version from the Huawei blog forum, no beta, on my Huawei GX8. I used the method, dload on SD card, Phone off an the press Volume down+volume up+Power button.The flashing was normaly.
Now the phone starts normaly but I can´t start fastboot. When the phone is off and i press Vol down + Power the phone start the android system and the Huawei logo is coming not the fastboot Modus. I can see my phone and the order under Windows but i can not control my phone with the fastboot command. (example: fastboot device. the answere ist searching devices, but it comes no resolution) I loaded the last version of Fastboot, but the problem is the same.
Please can you help me. What can i do? Many thanks for your help!
Should be connect the charger cable to the phone.
charger or computer
excuse me for bad english
No i use a data cable, debugging is on. I can copy data from my phone to PC or from PC to phone, but fastboot does not found my device.
bertl237 said:
No i use a data cable, debugging is on. I can copy data from my phone to PC or from PC to phone, but fastboot does not found my device.
Click to expand...
Click to collapse
And when you use adb to reboot to bootloader, what happen? Do you have "Minimal adb and fastboot tool" installed?
krispin said:
And when you use adb to reboot to bootloader, what happen? Do you have "Minimal adb and fastboot tool" installed?
Click to expand...
Click to collapse
Sorry for my question, what´s the differents about adb and fastboot tool? I have install the last version of minimal adb and the fastboot tool, also the Windows driver for the phone. Debugging is on. I try to connect my phone about the fastboot terminal. When i try to set the phone into the bootloader mod with the fastboot terminal and the equivalent command, fastboot say´s "searching phone". My phone does not react.
bertl237 said:
Sorry for my question, what´s the differents about adb and fastboot tool? I have install the last version of minimal adb and the fastboot tool, also the Windows driver for the phone. Debugging is on. I try to connect my phone about the fastboot terminal. When i try to set the phone into the bootloader mod with the fastboot terminal and the equivalent command, fastboot say´s "searching phone". My phone does not react.
Click to expand...
Click to collapse
So, you connect your phone, open minimal adb and fastboot too, run "adb devices", you see device id? If yes, run "adb reboot bootloader" . Phone shoult reboot to fastboot mode. Then run "fastboot devices" to see if it is connected properely.
i did it, like you described, but i see not my device id. Only the note "seach device"
Is it possible that TWRP is defect on my device? Is TWRP necessary for fastboot or only for root?
bertl237 said:
i did it, like you described, but i see not my device id. Only the note "seach device"
Is it possible that TWRP is defect on my device? Is TWRP necessary for fastboot or only for root?
Click to expand...
Click to collapse
No, you should be able to use adb and fastboot with stock recovery.
After first adb command you shoult approve authorization on your phone.
Here is screenshot from minimal adb...
Phone must be in MTP mode.
And here is phone in fastboot
Many thanks for your help, now I m in my bootloader.
2 problems i had.
1. My daemon was not started correctly, i have not seen my device.
2. I used the wrong command. I started with fastboot, not with the command adb device. I tap „fastboot reboot-bootloader“,but the correct command is “adb reboot-bootlader“
Now i have seen my phone is unlocked, i hope i can root my android 6.
bertl237 said:
Many thanks for your help, now I m in my bootloader.
2 problems i had.
1. My daemon was not started correctly, i have not seen my device.
2. I used the wrong command. I started with fastboot, not with the command adb device. I tap „fastboot reboot-bootloader“,but the correct command is “adb reboot-bootlader“
Now i have seen my phone is unlocked, i hope i can root my android 6.
Click to expand...
Click to collapse
Just reboot to fastboot and flash surdu-petru version of TWRP recovery 3.0.2 with command "fastboot flash recovery xxxxx.img". And than reboot to recovery and flash supersu zip.

adb reboot bootloader - device not found

I've installed ADB/Fastboot/USB Drivers from http://forum.xda-developers.com/showthread.php?t=2588979 (tried both 1.3 and 1.4.2 versions.
Booted my SW3 into Fastboot (whitescreen, with fastboot written on it) - attached to the PC, Device shows up as SAMSUNG Android Phone > Android ADB Interface
Ran CMD as an Administrator.
Typed, adb reboot bootloader.... Error: device '<null>' not found.
Typed adb devices... not listed.
Okay, so using a driver stripper (and windows program uninstaller), removed all Samsung phone USB drivers, KIES and existing ADB drivers. Re-ran the top tool to re-install everything. Repeated process, still showing up as SAMSUNG Android Phone > Android ADB Interface. Still not detected.
No idea at all what's going on here. I've tried cleaning the drivers multiple times. Other USB ports (2.0 & 3.0). Tried manually updating the driver to Google Inc. driver variants (9.0-11.0)
Really appreciate any help here.
if you're into bootloader you have to type fastboot devices , adb only works outside fastboot in system mode
woschirmer said:
if you're into bootloader you have to type fastboot devices , adb only works outside fastboot in system mode
Click to expand...
Click to collapse
Mind if I pick your brain on that point. I'm used to ADB on a smartphone, I really expected this to be similar but there's clearly some catches.
I don't think I'm into bootloader yet because the command 'adb reboot bootloader, or adb reboot-bootloader' doesn't do anything other than throw the error mentioned above.
However, typing fastboot devices gives me.
14442D38F870562 fastboot
But this doesn't allow me to process to run through the other ADB commands I need to complete. 'adb devices' still lists nothing.
In short, I'm trying to downgrade my SW3 to LCA32, as required to turn on the NFC functionality https://github.com/pimpimmi/LibreAlarm/wiki/How-to-install-NFC-on-Sony-Smartwatch-3
It's to assist in enhancing a medical device that uses NFC.
Sideburnt said:
Mind if I pick your brain on that point. I'm used to ADB on a smartphone, I really expected this to be similar but there's clearly some catches.
I don't think I'm into bootloader yet because the command 'adb reboot bootloader, or adb reboot-bootloader' doesn't do anything other than throw the error mentioned above.
However, typing fastboot devices gives me.
14442D38F870562 fastboot
But this doesn't allow me to process to run through the other ADB commands I need to complete. 'adb devices' still lists nothing.
In short, I'm trying to downgrade my SW3 to LCA32, as required to turn on the NFC functionality https://github.com/pimpimmi/LibreAlarm/wiki/How-to-install-NFC-on-Sony-Smartwatch-3
It's to assist in enhancing a medical device that uses NFC.
Click to expand...
Click to collapse
Okay progress, I see what you mean now adb reboot bootloader doesn't work. But fastboot reboot bootloader does. This is allowing me to move through the necessary TWRP and img steps. Thanks.

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?

ADB/Fastboot Access denied

So I've decided to root and customize my Z2 Force and want to unlock the bootloader to get TWRP installed. All device side settings are correct (USB Debug, OEM unlock etc.) in developer mode. ADB commands are working fine as I can see my SN when using ADB Devices command. I then reboot to the bootloader through ADB (adb reboot bootloader) and it works fine and my Z2 boots into the bootloader. Then I try to get the unlock code (fastboot oem unlock) and I get a message after trying to run the command: access denied. I started my CMD window using run as admin - no help. Installed ADB all over again with new generic drivers and moto drivers - no help.
I don't understand why I'm getting this message. I've unlocked and rooted all my phones over the years but they've all been HTC. Never messed with a moto phone like this before. I bought this phone directly through moto and it's suppose to be a carrier unlocked version. Anyone think this is a permalocked bootloader version - MODEL:XT1789-04 TYPE:M29E2
Any help is appreciated.

Categories

Resources