Hello, I hope that this topic can be opened here, if not please move it or let me know and I will delete it.
In adb I am getting the error "failed to check server version: protocol fault (couldn't read status): No error" and I cannot see my device when I use the command "adb devices". Moreover, it seems like my phone is not letting me authorize my laptop for USB debugging despite trying different options to getting it to work. I have tried different trouble shooting methods that I have found online, but nothing has worked so far. If anyone has any ideas, it would be greatly appreciated.
I am using a POCO F2 Pro that has had its bootloader unlocked and I am running Xiaomi.eu version 12.0.4 (stable) and using a Windows 10 machine to connect with my phone. I did not have much problems with the flashing off TWRP, using ADB commands, or flashing the ROM when I did all of these things last month.
Now, however, I have been having some problems. I believe it started when I tries to update the System FW a few days ago in the phone instead of flashing it manually. Because it was the stable version, and because the option existed in my system settings, I thought that I would be able to update it without going through those steps. The update downloaded and I got the correct file, but when I hit install, I did not get the new FW, despite the phone rebooting. I've been having problems with adb since this time, I believe.
Try restarting adb server:
Code:
adb -d kill-server
adb -d start-server
Try re-enabling USB debug stuff in Dev Options too.
Saratoga79 said:
Try restarting adb server:
Code:
adb -d kill-server
adb -d start-server
Try re-enabling USB debug stuff in Dev Options too.
Click to expand...
Click to collapse
Hello, thanks for your reply. I tried that yesterday, but I gave it another try today. This was the error that I received when I ran the command in Powershell:
Program 'adb' failed to run: No application is associated with the specified file for this operationAt line:1 char:1
+ adb -d kill-server
+ ~~~~~~~~~~~~~~~~~~.
At line:1 char:1
+ adb -d kill-server
+ ~~~~~~~~~~~~~~~~~~
+ CategoryInfo : ResourceUnavailable: ) [], ApplicationFailedException
+ FullyQualifiedErrorId : NativeCommandFailed
When I ran the command in Command Prompt, I got the error "failed to read response from server".
Trying to start the server also lead to an error "protocol fault (couldn't read status): No error
---------
Part of my issues may be coming from the fact that I no longer get the authorize USB debugging on my phone, even after I have revoked the authorizations. I've tried different ports, different USB cables, and even factory resetting my phone, to no luck.
Try using the latest platform tools from Google.
batuken said:
Try using the latest platform tools from Google.
Click to expand...
Click to collapse
From what I know, I am using the latest SDK platform tools. I initially downloaded from that site either in late July or early August, and yesterday I deleted the old files and re-installed them from the website. Is there an additional step that I might have missed in removing the old files from my computer?
Additionally, the .android folder in my user profile is now empty (no adb_key file(s) inside).
Related
ok so i downloaded the SDK and the windows drivers. i downgraded the phone to rc29 and have just enabled adb on the phone using the command <enter>setprop persist.service.adb.enable 1<enter> and <enter>telnetd<enter>. i opened up CMD in windows and changed the directory where i needed and tried to run adb and it gave me this error: "* daemon not running. starting it now *
* daemon started successfully *
error: device not found"
why did it give me this error? and alo im stuck at the part where im supposed to "copy a busybox binary" using adb push. i dont know exactly what im supposed to do to do that step. i am a noob at this stuff so please be kind and use noob terms and steps.
Thanks
PS: i did connect the phone to the pc with the data cable and the add new hardware thing popped up and i installed the drivers like i was supposed to. it said something about they were installed correctly but may not be working properly, whatever that means.
Try this....
Unplug the phone.
Reboot the computer.
When fully rebooted, plug the phone back in and see what the computer does.
Did it say, "Found new hardware" or some such message?
Did it say that it couldn't find a driver?
Okay - after the OTA updates, I'm now having the same problem! Ouch!
Plugging in, running DOS Command...
c:\> adb devices
Reports that there are no devices attached!
BUG!!!!!!!!!!!!!!!
Trying to do some push/pull and do the new lag fix to no avail. After adb devices, the phone shows up as attached, but after adb remount I get "remount failed: No such file or directory" I'm not able to execute a push or pull command, and therefore I'm not able to run the lag fix.
I have USB Debugging selected, and I was able to delete the bloatware via adb shell, but none of the other commands go through for me...
Which version of Windows are you running?
Windows 7 64 bit
Still haven't found a fix to this, so I'll post up what I'm inputting and what I'm getting in return.
Here is the code I use to get into ADB and then attempt a remount:
Code:
cd C:\android-sdk-windows
cd tools
adb remount
remount failed: No such file or directory
When I try to push and/or pull, I get this:
Code:
adb push ./smoothcalendar.apk /system/app
failed to copy './smoothcalendar.apk' to '/system/app/smoothcalendar.apk': Permission denied
I've tried adb kill-server, then adb remount with the same issues.
currently experiencing the same problem...
Do you have BusyBox Installer installed on your phone? I believe you have to have it installed in order to use Android SDK.
I've got Busybox 1.17.1 on mine.
I'm wondering, is this a problem at the computer level or at the phone level? I know the Vibrant had some issues with push/pull, but I see some stuff here in the dev thread (lagfixes, sideloader stuff) that if I run from my computer attempt push/pull commands that fail and therefore the thing I'm running (lagfix most recently) doesn't actually work and I'm stuck with a slower phone.
If its a phone issues, I can just exchange it under warranty, since I'm out of my 30 days. But I'm hoping it's not as I'd like to keep this one that other than this has worked great for me.
When I first starting using ADB, I was connecting my phone like when I was using Windows Explorer to muck around on it. I had mounted the usb connection in the notification window. I kept getting errors when I tried to push/pull. I reconnected once and forgot to mount the usb connection and everything worked perfectly. Make sure the usb debugging is check marked in Applications in settings. Try to do the push/pull without using remount command and don't click on the USB connected notification option when you plug it in. I'm really new at this linux stuff so I could be wrong. I'm just trying to share my experience in hopes that maybe you're doing the same things I was doing before I stumbled onto the right way to do it.
Hmm, odd, I've tried that very method many times before, to no avail.
I try it just now, and having no problems with push or pull. Works for me! Thanks!
Upgraded to ICS 4.0.4 following Jim's instruction. Got stuck on the rooting step. In windows, the driver could be installed without USB debug turned on. And I can see the phone is mounted. Only when I turned on usb debugging, the driver couldn't not be installed properly and rooting script would freeze at damon started (something like that)
Tried it under Mac too. The phone can't even be recognized. Tried factory reset/reinstall newest driver/reboot millions of times, it just didn't help. The phone still can be seen using adb devices command. But I got the following errors while running the rooting script:
Unable to chmod /data/local/12m/debugfs^M: No such file or directory
Unable to chmod /data/local/12m/su^M: No such file or directory
Unable to chmod /data/local/12m/cmds^M: No such file or directory
failed on '/data/local/12m/batch' - No such file or directory
...
I can still log on to my phone by adb -s command and it turned out I don't have permission to write or list all the phone folders including data. No wonder. There is noway of changing the permission with chmod either since sudo does not work.
I came very close to fxz back to 2.3.6 because of the frustration, but still wanted to give it a final shot. Does anyone have any idea how to get my phone rooted in this case?
Questions should be posted in Q&A (Questions & Answers) Section.
I assume you're running the script as Administrator? Also, I'm not sure what you're getting at with the drivers not being able to install if the phone is in debugging mode. It has nothing to do with the phone, you just download the latest drivers and install to your PC, then enable debugging on the phone, connect via USB, and run the script as Administrator...
Sent from my fingers to your peepers
Hi!
Please help me...
My Infocus M210 is rooted and I've edited the build.prop from a build prop editor to speed up internet data connection but the editor goes wild and changes everything written on the build.prop then forced my phone to shut down and when I start my phone, it stuck at boot loop.
I've already wipe data/factory reset on its built-in Android system recovery <3e>.
but I think its the worst thing that I've done.
Coz I thougt it disabled debugging and removed root permission from my device.
I've used Apply update from ADB.
I tried to sideload stockrom.zip but when its completed sending on my phone, then says "installation aborted" I've tried different ROMs but same result.
I have also tried shell commands:
adb pull /system/build.prop
adb -d -e -s <serialNumber> shell am start options -D
but all shell commands doesn't work and says "error:closed"
So then I've tried Fastboot mode
but my devices wasn't found
so I have followed some threads and watched youtube tutorials:
So I removed drivers via "usbdeview"
Then installed Fastboot device/ Fastboot interface drivers manually.
but I almost tried all drivers from official to many google drivers
but still my device wasn't found in cmd
says "waiting for device"
Now I'm thinking if there are some tricks to fix adb "error:closed"
or try different computers for fastboot
I already used my Windows 7 64-bit from my friend
and Windows XP 32-bit from my friend
Please Help me... :crying:
Hello,
Welcome to XDA.
Try posting your question in the forum linked below.
http://forum.xda-developers.com/android/help
The experts there may be able to help. Good luck.
I accepted the forced OS upgrade over the weekend (I think it was for Pie) on my Samsung Note 8. Upon restart, it is no longer accepting my encryption password and I can't get to my home screen. Yes, I know my password, and yes I'm freaking out (so any help would be appreciated!). I would like to not wipe the data off my phone.
So far he's what I've tried on my own:
Restarting/rebooting the device
Samsung Sync to try and back up
Find my mobile (both the android version and samsung version) to try and back up the device. No dice.
Load to bootloader (but device not recognized)
I'm down to three tries before the Factory Reset Protection (FRP) kicks in. (any way to extend number of tries is a separate, but equally important question.)
I finally started brushing up on adb and ran "adb devices". Server starts and it recognizes the device (whew!) but it's "unauthorized" which I assume it has to do with my encryption. Again, I have no access to the settings menu in order to enable USB debugging, so going into the GUI is not possible.
I also tried this:
[email protected]:~# adb backup -apk -shared -all -f ~/android/backup.ab
adb: unable to connect for backup: device unauthorized.
This adb server's $ADB_VENDOR_KEYS is not set
Try 'adb kill-server' if that seems wrong.
Otherwise check for a confirmation dialog on your device.
[email protected]:~# adb kill-server
[email protected]:~# adb start-server
* daemon not running; starting now at tcp:5037
* daemon started successfully
[email protected]:~# adb backup -apk -shared -all -f ~/android/backup.ab
adb: unable to connect for backup: device unauthorized.
This adb server's $ADB_VENDOR_KEYS is not set
Try 'adb kill-server' if that seems wrong.
Otherwise check for a confirmation dialog on your device.
Again, the fact that ADB is recognizing the device is a good sign in my opinion, just need to get past that so I can backup and pull the data off my phone. If there are any how-to's or steps that show what I can do to fix my actual problem and get my phone back to the way it was on Saturday, that would be AWESOME.
I haven't tried rebooting without the SIM inserted or wiping cache partition from the reset screen, but I'm willing to try that if anyone thinks that'll do it.
Please help.