Hey guys,
I have been looking for solutions for 3days now and can't find it.
My phone is showing under device manager both when its on, and when in adb mode without exclamation mark.
I had SDK 24.4.1 installed, installed everything needed (I think) (Platforms, usb drivers,..)
Flashtool drivers installed, it shows device in fastboot devices but not in adb devices..
When I open CMD in admin mode, I cd to the platform tools folder and do 'Adb devices' It does not show.
I tried Adb kill-server not working, daemon starts succesfull but nothing shows under adb devices.
Also tried a different pc, same outcome.
Running windows 10
I hope its something really stupid I'm forgetting..
UPDATE: Solved! After installing the good SDK, I just had to shut down computer, pull out the plug, take out the battery and wait a while.. Restart and now its showing! Thanks anyway guys Root here I come
You power on device with unlocked screen?
Your phone should just be on with screen unlocked like normal if trying to use adb.
Installed android Studios and it appeared I had sdk for android 6.1 and 6.0 but not for 5.1 wich I am running? I deleted both and installed the 5.1 one.. reinstalled sdk with usb drivers etc.. now I am getting this;
server version (32) doesn't match this client (36); killing...
Error; could not instal 'smartsocket' listener: Cannot bind to 127.0.0.1;5037
could not read ok from ADB server
*failed to start daemon*
error: cannot connect to daemon
I tried starting adb while device not connected, gives me the same ****.
Tried with mobile on, screen unlocked stays the same.
read that step 2a http://forum.xda-developers.com/z5-compact/general/flashtool-how-to-flash-sony-xperia-z5-t3425367
and try this http://forum.xda-developers.com/showthread.php?t=2588979
Rooted. Can I update the phone to latest android now? or only trough flashing costum roms?
Yes, you can.
You can read this forum not only ask
HELLO,
I have been trying to upgrade my Acer liquid e700/e39 from 4.4.2 kitkat to lollipop, so i have been trying to install philz touch recovery to my mac, which is running mac sierra.However whenever i get to the point that says 'this requires a working adb on your pc and a root shell on your mtk devices click ok, then it say's please wait a moment, then it says 'please connect your phone via usb, whenever i connect the phone and click okay it says "sorry adb root shell isn't working.But i enabled adb root on my phone via king root,and usb debugging is also enabled.I also followed some tutorials about installing adb and fastboot on mac x, and ran some commands via the terminal, but i still keep on getting 'sorry adb root shell isn't working with a yellow exclamation, and it then asks if i want to download some mtk tools which takes me to pdanet.I set up pdanet on the mac and on the phone from the instructions, but still nothing works.help!
thanks.
I want to unlock my cousin's tab who recently passed away and no one knows the passcode so after some googling i found that you can do it via ADB.
(https://forum.xda-developers.com/showthread.php?t=2620456)
The device successfully connects with my pc but when I execute "adb devices" it shows;
.......................... unauthorized
and running adb shell shows;
This adbd's $ADB_VENDOR_KEYS is not set; try 'adb kill-server' if that seems wrong.
Otherwise check for a confirmation dialog on your device.
With the device locked Im unable to authorize my computer so I decided to search something for that too and found this article where it tells u to pull keys from another device and push it into your locked one while in recovery mode and this is where Im stuck. Whenever Im in recovery mode, adb devices shows nothing so if someone of you could help me would be awesome.
Hope someone can help me I am becoming confused. I have downloaded adb tools from this site. and I am trying to follow the instructions step by step. I have a Doogee X5 max pro. android phone
It is set up in USB debugging mode! When I type adb devices" ,running command from within the folder as per instructions!" a deamon launches but does not see the phone?
I run same from command prompt from start menu .nothing happens. just return me to platform tools.
The instructions says the tool may open in a shell. but does not elaborate what to do within a shell.
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)