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
Related
I boot my Acer Iconia Tab A200 into fastboot mode (robot lying down and RED exclamation mark over it). I plug it into my Windows 7 (64bit) desktop computer with SDK installed, and from the directory with fastboot.exe I type FASTBOOT DEVICES but the device is not being seen, it just goes back to the prompt, like the command executed but didn't do anything. I assume this is because the drivers aren't installed. But I don't know how to install the "adb drivers". How is this done?
Go to Acer support page, you'll get the drivers there.
This device will not fully boot. It gets stuck at an "encryption unsuccessful" message. I'm trying to flash a rom image from my desktop computer using fastboot, but when my tablet is in fastboot mode, my desktop computer won't recognize it. ie adb devices command doesn't show that there is any device connected, and I think it's because the drivers aren't installed. I think those Acer drivers only work if the tablet can be fully booted.
Installed the Google USB Drivers from the SDK Manager already. Don't know what's wrong.
Alright I figured out how to get fastboot to interface with my Android tablet. The problem was that I wasn't getting the tablet into fastboot mode to recieve commands.
But now it's working. However, I'm trying to unlock the bootloader and it gives me an errors that says:
SetUnlockedMode: Error occured while unlock the device ...
Fastboot: Failed to set unlock mode
I have to unlock the bootloader before I flash an image to the tablet, right ?
Yep, surely.
So, I was messing some things up in safestrap and I decided I want to do a fresh start on my phone. So I went to the wipe section and wiped everything.. Now as I can tell, I have no /system folder, no OS, nothing. I can access bootloader. After intense reading and searching, I managed to connect my phone via adb, adb devices command shows the ID of my phone in a sideload state. Sideloading a rom never worked, tried many of them, at best I got an error about getprop file missing - tried to modify the updater-script using an editor after instructions but still nothing. My main issue is that while adb works fine, drivers are 100% fine, upon entering phone into fastboot mode, it disconnects and there is nowhere to be found under device manager. If I could get it to work in fastboot I could then use RSD lite to flash a stock rom. Also, the only command that works from adb is the # adb sideload filename, anything else returns error:closed. Even tried #adb usb #adb remount and so on. Is my phone a garbage at this point?
forgot to say also, tried to connect via fastboot under windows 7 sp1 / xp sp3 / ubuntu 14.04 .
bump
bump..
When I got my m7 I tried to s-off but nothing worked. I eventually figured out that ADB won't work. I am rooted, running IC 3.06 (KK 4.42, Sense 6) and would love to upgrade to insertcoin 6.05 but I'm afraid to do it without ADB to fall back on. Anyone know how to fix this?
I have tried to run many s-off programs from three different PCs running Windows 7 and updated Linux Mint DE, Ubuntu 14.04 with original cable and other good quality ones. I can communicate with the phone with fastboot and can copy and paste to the phone perfectly in every OS. But when I try to ADB reboot or any other command, I get "device not found" .
pete2bec2 said:
When I got my m7 I tried to s-off but nothing worked. I eventually figured out that ADB won't work. I am rooted, running IC 3.06 (KK 4.42, Sense 6) and would love to upgrade to insertcoin 6.05 but I'm afraid to do it without ADB to fall back on. Anyone know how to fix this?
I have tried to run many s-off programs from three different PCs running Windows 7 and updated Linux Mint DE, Ubuntu 14.04 with original cable and other good quality ones. I can communicate with the phone with fastboot and can copy and paste to the phone perfectly in every OS. But when I try to ADB reboot or any other command, I get "device not found" .
Click to expand...
Click to collapse
ADB only works in Android OS with USB debugging enabled or in a custom recovery. If the phone is showing FASTBOOT USB then ADB will not work!
I was in Android with USB debugging enabled, on a PC with drivers. I could copy and paste files between phone and PC. But if I typed ADB devices in a terminal window, I got devices not found. I didn't get unknown command, so it saw the correct path. No matter what command I typed, I got device not found.
pete2bec2 said:
I was in Android with USB debugging enabled, on a PC with drivers. I could copy and paste files between phone and PC. But if I typed ADB devices in a terminal window, I got devices not found. I didn't get unknown command, so it saw the correct path. No matter what command I typed, I got device not found.
Click to expand...
Click to collapse
Have you updated your ADB/Fastboot files or update the drivers?
Hello folks,
Yesterday, i wasn't able to unlock my phone and wifi was switched off for some reason so I couldn't use my google credentials or google device manager to unlock it. for some reason the device stopped responding to my lock pattern ...
So I thought I would try to use adb to at least turn the wifi on and then I can use google device manager to unlock it and reset the pattern.
THe problem is, every time I try to install the asus adb drivers I get this message in the driver install screen:
"
The software for this device is installed, but it may not work correctly
The device won't start: code 10
"
in the device manager, the "asus adb interface" has a yellow triangle with an exclamation mark on it.
I tried it on 2 different PCs with windows 10 as well as a windows 7 VM ... but every time I get the same message at the install screen.
ofcourse due to this, whenever I type "adb shell" or "adb devices" I get nothing...
Has any one faced this issue before with the asus adb drivers? any solutions you can think of?
The phone itself is rooted using towel root, every thing else is basically its stock rom.
Thank you and appreciate your help!
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)