I want to know if I can enable USB Debugging thru ADB while Evo is in Fastboot USB. I am locked out as I do not know the security pin. Any thoughts? My plan was to root it then use abd shell -d SQLITE3 commands. However I may not be able to root it as bootloader is locked and I do not wish to wipe data, I was looking to temp root thru ADB commands. If anyone may chime in on any of these elements, i would be grateful. I would love to learn how to root using ADB only!
Have Honda Accord X 2019 Have 8 inch for based on android 6.0.1 Find how on USB debugging find how on adb mode. Now have problem: when I enter "adb devices" the command on the computer. I get a response device number and that the device is not authorized. I would have to confirm on the device usb debug but I think that Honda blocked. I try in Ubuntu Insert key files from your phones that passed authorization. nothing helps. please tell me what else can be done. you can simulate the situation on any phone just by request do not confirm usb debug and try to do something after the command "adb devices".
vikdr said:
Have Honda Accord X 2019 Have 8 inch for based on android 6.0.1 Find how on USB debugging find how on adb mode. Now have problem: when I enter "adb devices" the command on the computer. I get a response device number and that the device is not authorized. I would have to confirm on the device usb debug but I think that Honda blocked. I try in Ubuntu Insert key files from your phones that passed authorization. nothing helps. please tell me what else can be done. you can simulate the situation on any phone just by request do not confirm usb debug and try to do something after the command "adb devices".
Click to expand...
Click to collapse
Try this:
1. Go to the developer options on the phone and click "Revoke USB debugging authorization" if option is present
2. Disconnect device
3. Delete folder %USERPROFILE/.android
4. Re-start ADB server
Code:
adb kill-server
adb start-server
5. Re-connect device
Code:
adb devices
I do this dont help. "unauthorized". You can verify this in your phone just dont confirm usb debuging when ask.
vikdr said:
You can verify this in your phone just dont confirm usb debuging when ask.
Click to expand...
Click to collapse
That your problem, you have to confirm when you connect your device, also make sure u use the latest version of adb, it can be downloaded here: https://developer.android.com/studio/releases/platform-tools
Problem i cant confirm on phone. Need use adb without confirm on phone
Re-create RSA keys
Code:
adb kill-server
adb keygen %USERPROFILE%\.android\keys\adbkey.pub
Thanks. But dont help
vikdr said:
Thanks. But dont help
Click to expand...
Click to collapse
Hi!
How did you solve the problem?
Hi. No
Hi, I have a Xiaomi phone with the 3 buttons apparently broken.
I'm trying the adb commands to power up the phone, but unfortunately I don't have the adb enabled on the device (infact when I try to use the command "adb reboot" the system gives me the message "device unautorized").
do anyone knows how to use the adb commands to enable the adb on the phone to power up again?
thank you very much (I'm so depreeeeessed)
ADB ( read: ADB daemon ) is part of Android OS.. Thus it should be obvious when Android isn't running you can't run any ADB command where it doesn't matter whether USB debugging got enabled or not.
I'm looking for a ways on how to enter DIAG Mode.
( for Qualcomm Product Support Tools )
I tried following method to enter DIAG Mode.
Using ADB mode.
Connect turned on device to PC via USB-cable and enter these commands in device terminal.
adb shell
su
setprop sys.usb.config diag,adb
But no response.
:victory: Self-resolved.
I reinstall stock ROM(curtana_V12.0.1.0.QJWMIXM) by MiFlash.
Then I tried ADB method.
I could set Diag mode.
On custom ROM, I could not.
marlinzukz2 said:
:victory: Self-resolved.
I reinstall stock ROM(curtana_V12.0.1.0.QJWMIXM) by MiFlash.
Then I tried ADB method.
I could set Diag mode.
On custom ROM, I could not.
Click to expand...
Click to collapse
Hi, are you trying to unlock additional LTE bands or enable some LTE+ CA configurations?
I just got a new F(x)tec Pro-1X and I want to root it. I'm following the instructions to use Magisk from the F(x)tec team which involves 1) installing Magisk, 2) connecting adb and authorizing, 3) adb pushing the Pro-1X boot.img, 4) Running Magisk and patching the boot.img, and 5) downloading the patched .img.
Then I run "adb reboot bootloader" which leads me to a screen where I can choose Recovery mode and then I get to an Android screen that says "No command". I believe it's here that I'm supposed to run "fastboot flash boot magisk_patched-25200_HsxJg.img"; however, when I run "adb devices", I get unauthorized, and trying to run fastboot anyway fails:
$ adb devices
List of devices attached
8ce396c8 unauthorized
$ fastboot flash boot magisk_patched-25200_HsxJg.img
< waiting for any device >
I found elsewhere that from this screen, I can hold the power button and press the volume up key and then release both and I see the Android recovery screen. Then I scroll down to Enter fastboot and press power to enter that and I see fastbootd, but I get the same "waiting for any device" output if I try the fastboot flash command here.
If I go back to recovery mode, and instead go to Apply update from ADB, I then see the following from adb devices, but I still can't run fastboot flash:
$ adb devices
List of devices attached
8ce396c8 sideload
I'm running the latest Android Studio and platform-tools on a Lenovo X270 running Fedora 37 and Linux kernel 6.0.17. I'm connecting using a USB-2 port without a hub and tried multiple USBC cords.
A commenter on the F(x)tec forums said that he could never get his Lenovo X250 to work and he had to buy a Raspberry Pi 3 model B.
Are there any alternatives or diagnostics I can run to help solve this "unauthorized" error?
Did you enable usb debugging in the developer options and validate the box after connecting with a USB cable?
ze7zez said:
Did you enable usb debugging in the developer options and validate the box after connecting with a USB cable?
Click to expand...
Click to collapse
Yes. That was required for steps 2-4 for pushing and pulling the image. When I did that, I had to authorize my laptop on my phone. There's no such dialog during recovery mode. Is there some way to pre-authorize recovery mode with my laptop, or otherwise disable this authorization?
Option below USB debugging, which is: Revoke USB debugging authorizations.
or
read this:
ADB Android Device Unauthorized
Since I reinstalled Eclipse (simply deleted and downloaded it again) I can't debug my applications on Samsung Galaxy i9001 (with CyanogenMod - Android 4.4.2). It worked fine before reinstallation.
stackoverflow.com
ze7zez said:
Option below USB debugging, which is: Revoke USB debugging authorizations.
or
read this:
ADB Android Device Unauthorized
Since I reinstalled Eclipse (simply deleted and downloaded it again) I can't debug my applications on Samsung Galaxy i9001 (with CyanogenMod - Android 4.4.2). It worked fine before reinstallation.
stackoverflow.com
Click to expand...
Click to collapse
Thanks, but none of that worked. My problem is authorizing during recovery mode, not during normal operations. It seems what I really need is to either modify /data/misc/adb/adb_keys on the device, or run adb disable-verity, or set ro.adb.secure=0, but I don't have permissions to do any of those.
It's interesting that another F(x)tec user says this works with a Raspberry Pi, and also says it does not work with his Lenovo X250 running Linux, which is similar to my laptop. This suggests there's some sort of limitation or additional security related to the Linux kernel 6.0.17 and/or Fedora, but I can't find what that is or how to diagnose it. I don't have SELinux running on my laptop.
Good day,
I'm use adb tools from my fedora 37
Your issue is related to how you call adb.
Try this:
adb kill-server
sudo adb start-server
sudo adb devices
The same game with fastboot tools
Its works perfect with selinux on
Regards
MoHuToP said:
Good day,
I'm use adb tools from my fedora 37
Your issue is related to how you call adb.
Try this:
adb kill-server
sudo adb start-server
sudo adb devices
The same game with fastboot tools
Its works perfect with selinux on
Regards
Click to expand...
Click to collapse
Doesn't work:
$ adb kill-server
$ sudo -i
# adb start-server
* daemon not running; starting now at tcp:5037
* daemon started successfully
# adb devices
List of devices attached
8ce396c8 device
# adb reboot bootloader
... Wait for recovery mode "no command" screen ...
# adb devices
List of devices attached
8ce396c8 unauthorized
# fastboot flash boot magisk_patched-25200_HsxJg.img
< waiting for any device >
For reference, attached are pictures of all the places where I try the commands and they fail.
I bought a Raspberry Pi 3 B and microSD, installed Raspbian, installed adb and fastboot, connected to phone (normal boot), authorized the Pi, ran adb reboot bootloader, entered recovery mode, phone goes to "No command" screen, but then I get a popup on my Raspberry Pi desktop that says:
Unable to open MTP device "001,013"
Clicked OK and ran adb devices, and I'm back to the "unauthorized" status and adb and fastboot don't work. Tried this in the Raspberry Pi as both a normal user and root (with adb kill-server in between).
Tried with another USB C cable and got a similar error, although it ended with "001,016".
Any ideas?
Resolved by running fastboot on the START screen! (And worked through my X270)