Database Info

[S-Off] and Device Offline for PJ831000

This was answered a little bit in the S-Off thread and I would like to post it for everyone that has the PJ8310000 device and they are running into device "offline" when using adb devices. This is for Windows 8 only. I had the same problem in OSX, but I believe the solution is the same. I cannot post in the thread in the developer section yet, that is why this is here.
First, if you can't see your device in your device manager, make sure you have the latest HTC Device drivers installed or install the latest version of HTC Sync. This is very important for Windows 8.
Second, you will need to download and install the latest Android SDK. Just "Download From Other Platforms" and choose the appropriate SDK installation. You will need to run the SDK Manager.exe to install the latest tools. Note: ADB and Fastboot have been moved from the "tools" folder to "platform-tools".
Make sure your phone is in debugging mode by going into the Developer Options and choosing "Android debugging."
Find your SDK installation and make sure you are under "platform-tools" folder. You can ctrl-shift-right click on that folder to open a command prompt at that folder location. Saves you time.
Type in the command prompt:
Code:
adb devices
Your device should be listed and probably says Offline. This is normal. Take a look at your phone, you should get a prompt on your phone asking you if you trust the device that is trying to connect to it (this should be your computer). Allow it.
Type in the command prompt:
Code:
adb devices
This time, your device should be listed with the word "device" instead of offline.
To restart the daemon, type the following separately:
Code:
adb kill-server
adb start-server
This is the best I can do for everyone and it solved my problems with no further issues. I am not an expert and this is the only solution that has worked for me.

Thanks, this worked for me.

I did this in Windows 7 SP1 no problem. All I had to so was get the latest Android SDK and replace all the adb/fastboot files I already had and it worked no problems.
If you get permission denied when doing the last "adb shell" command, get adbd insecure from the forums here and run debugging mode insecurely from there.
Sent from my One X using xda app-developers app

Desertman123 said:
If you get permission denied when doing the last "adb shell" command, get adbd insecure from the forums here and run debugging mode insecurely from there.
Click to expand...
Click to collapse
I had this problem because SU was only allowing apps in CM10.1 (4.2.1). I found the solution by enabling the Dev Options via multiple clicks on the Build number until dev options was enabled, then changed Root access to Apps adn ADB.
FYI for anyone else that gets lost like I was.

ok so i can s-off now?

yes get some, 9 steps to s0ff

Ponarona said:
ok so i can s-off now?
Click to expand...
Click to collapse
Yes, you can use the HTC One XL link in the S-Off thread with no issues. I made this to help people with Win8 and trying to get their phones to appear properly in their device manager and to list it under adb devices.

If you get device offline, my issue, I was running android 4.2.2 but had an outdated adb. Just update adb if you still have problems

I know this is exceedingly random, but if you run a mac and can't see your device in adb, and in the past you tried sharing your phone internet with your mac via usb try running this:
sudo kextunload /System/Library/Extensions/EasyTetherUSBEthernet.kext
./adb kill-server
I need to do that before every adb session.
I'd be amazed someone actually has those conditions, but hey, it might help someone.
Sent from my HTC One X using xda app-developers app

ATTN: Backup your boot0 block today

ATTENTION: PUBLIC SERVICE ANNOUNCEMENT
It has come to my attention that under certain circumstances when the Kindle HD's get stuck in a bootloader bootloop the information on the "boot0" block of the internal storage can be ERASED and RESET.
This partition is special and contains ALL of your device's hardware specific information:
- Wifi MAC address + Encoded Secret for registering w/ Amazon services
- BT MAC address
- Serial #
etc
FOR BACKING UP THIS PARTITION:
Code:
adb shell su -c "dd if=/dev/block/mmcblk0boot0 of=/sdcard/boot0block.img"
adb pull /sdcard/boot0block.img
Place the "boot0block.img" file with the other files that you backed up in the original instructions for safe keeping.
FOR RESTORING THIS PARTITION:
(do not do this unless you are absolutely SURE that your boot0 block got wiped out -- hopefully you never need to)
This is done via adb from your PC while the device is in TWRP recovery or in the Android OS (not fastboot):
Code:
cd <your safekeeping files>
adb push boot0block /sdcard/boot0block.img
adb shell "echo 0 > /sys/block/mmcblk0boot0/force_ro; dd if=/sdcard/boot0block.img of=/dev/block/mmcblk0boot0;"
THIS FILE IS UNIQUE TO YOUR DEVICE AND CANNOT BE REPLACED OR REBUILT FROM ANOTHER DEVICE. DO NOT SHARE IT WITH ANYONE AS IT CONTAINS INFORMATION ABOUT YOUR DEVICE USED BY AMAZON DURING REGISTRATION.

very interesting Hashcode,thanks for the information :good:

Odd, I can't seem to find the file after I pulled it with ADB.
EDIT: I didn't even assign the command an output location to begin with. LOL.

Thanks for the info.
How can I access KFHD via ADB if CM10.1 installed.
I can't see my device in device manager only as a media storage or sth like that.
Should I remove KFHD adb driver and install the google driver?
Or just using the hidden trick in cm10.1?
"Enable Developer options in your phone (Settings > About phone and tap Build Number until you are a developer (about 7 times)
Set root access for APPS and ADB in: Settings > Developer Options > Root Access
Enable Android debugging at the same page (Developer Options). Enable ADB over network if you need.
Check if your Settings > Security > Unknown Sources is checked. you will need it to install over ADB."
Yeah...it helped

esox_hu said:
Thanks for the info.
How can I access KFHD via ADB if CM10.1 installed.
I can't see my device in device manager only as a media storage or sth like that.
Should I remove KFHD adb driver and install the google driver?
Or just using the hidden trick in cm10.1?
"Enable Developer options in your phone (Settings > About phone and tap Build Number until you are a developer (about 7 times)
Set root access for APPS and ADB in: Settings > Developer Options > Root Access
Enable Android debugging at the same page (Developer Options). Enable ADB over network if you need.
Check if your Settings > Security > Unknown Sources is checked. you will need it to install over ADB."
Yeah...it helped
Click to expand...
Click to collapse
Just turn on ADB debugging on the tablet, and plug it into the computer. On the computer, open command prompt, use the command "adb devices" to see if your ADB is working.
Other than that, I don't know what happened in your post.

Ok i really can't figure this one out, I used adb many times while testing KFFAide tool so I am 100% sure my adb drivers are installed correctly, But since i switched to cm10.1 (Thanks hashcode) ADB cannot recognize my device anymore, I have enabled ADB on my KFHD and when i connect it to my pc a small notification appears "Android debugging enabled" but when i use "adb devices" command nothing shows up!
Can anyone help me with this i'm completely lost here!

AmrBanawan said:
Ok i really can't figure this one out, I used adb many times while testing KFFAide tool so I am 100% sure my adb drivers are installed correctly, But since i switched to cm10.1 (Thanks hashcode) ADB cannot recognize my device anymore, I have enabled ADB on my KFHD and when i connect it to my pc a small notification appears "Android debugging enabled" but when i use "adb devices" command nothing shows up!
Can anyone help me with this i'm completely lost here!
Click to expand...
Click to collapse
Leave the device plugged in, go to Developer Setting and uncheck ADB debugging, then check it again. You should see a prompt, select OK for both.

seokhun said:
Leave the device plugged in, go to Developer Setting and uncheck ADB debugging, then check it again. You should see a prompt, select OK for both.
Click to expand...
Click to collapse
Ok thanks i tried but to no avail

AmrBanawan said:
Ok thanks i tried but to no avail
Click to expand...
Click to collapse
Yeah I actually have the same problem too now

Thanks for the heads up hash, got it on a usb stick now
---------- Post added at 11:41 PM ---------- Previous post was at 11:39 PM ----------
Protomartyr said:
Yeah I actually have the same problem too now
Click to expand...
Click to collapse
I had to manually check android debugging and usb debugging notify and it worked just fine.... make sure adb over network is not checked

Protomartyr said:
Yeah I actually have the same problem too now
Click to expand...
Click to collapse
AmrBanawan said:
Ok thanks i tried but to no avail
Click to expand...
Click to collapse
Why don't you guys try this, go into CMD while connected with the device (ADB debugging on), and type "adb devices" to start the daemon, then try the commands. Other than that, I don't know what else to do.

seokhun said:
Why don't you guys try this, go into CMD while connected with the device (ADB debugging on), and type "adb devices" to start the daemon, then try the commands. Other than that, I don't know what else to do.
Click to expand...
Click to collapse
Nope. Just get "List of Devices Attached" but no serial number. Checked device manager and it's showing up as a portable device. Probably will reinstall them and see if that solves it.
On a side note:
if we ran these commands in terminal emulator on the device, would that be sufficient?

Protomartyr said:
Nope. Just get "List of Devices Attached" but no serial number. Checked device manager and it's showing up as a portable device. Probably will reinstall them and see if that solves it.
On a side note:
if we ran these commands in terminal emulator on the device, would that be sufficient?
Click to expand...
Click to collapse
Yes
run the first command then pull it manually
But we need to know what's going on, i will need adb sometime soon when prokennexusa releases the next version of KFFAide

AmrBanawan said:
Yes
run the first command then pull it manually
But we need to know what's going on, i will need adb sometime soon when prokennexusa releases the next version of KFFAide
Click to expand...
Click to collapse
you can always open up your device manager and manually apply the adb drivers to your kindle

How do we know the boot0 partition is erased?
Sent from a Kindle Fire HD running CM10.1 using Tapatalk 2

had same probs on cm10 getting the files no matter what i tried.in windows 7 and xp it wouldnt install normal driver so i could see kindle as a drive so flashed an amazon zip and pc recognizes it without any problems and now have the files needed

dugoy13 said:
How do we know the boot0 partition is erased?
Sent from a Kindle Fire HD running CM10.1 using Tapatalk 2
Click to expand...
Click to collapse
Normally you would notice WiFi doesn't work under any circumstances same for BT. And when on Amazon's software it won't let you register.
Sent from my Amazon Kindle Fire HD using Tapatalk 2

I can't get ADB to find it either, think i'll revert back to stock to get the file then go back to CM - I notice though on CM turning USB Debugging on doesn't change anything in device manager, it still stays connected as a media device or camera, depending on which you have ticked in storage setting *shrugs*
Thank you Hashcode

PaulJCW said:
I can't get ADB to find it either, think i'll revert back to stock to get the file then go back to CM - I notice though on CM turning USB Debugging on doesn't change anything in device manager, it still stays connected as a media device or camera, depending on which you have ticked in storage setting *shrugs*
Thank you Hashcode
Click to expand...
Click to collapse
No don't, just type the command hashcode provided in terminal emulator and you'll find the backup in your sdcard, just copy it to your pc like normal!

You can do it from the terminal without typing ADB. that may be why people are confused. Start with hashcodes command but start with "su -c" in the terminal.
Sent from my Nexus S 4G using xda app-developers app

[Q] ADB command hang out

Hi All,
I am a newbie here. I issue following "adb shell getprop" adb command to retrieve device properties. This just hang out no output printed on the terminal or no prompt appears.
I then kill it at send "adb shell getprop ro.build.version.release" but it also just hang out.
I am working on ubuntu12.04. adb devices list one device which is connected.
Please help, how can I read device properties from adb (such as OS, model, manufacturer etc..)
My device is not rooted.
Many thanks!
IUA

Unlocked bootloader

I have my Samsung note 3, and it will never be unlocked. So i was thinking about moving to this. Is the Verizon edition unlocked for custom roms?
Sent from my SM-N900V using XDA Free mobile app

scoreboard said:
I have my Samsung note 3, and it will never be unlocked. So i was thinking about moving to this. Is the Verizon edition unlocked for custom roms?
Sent from my SM-N900V using XDA Free mobile app
Click to expand...
Click to collapse
It doesn't come unlocked, but you can unlock it. That's why are a lot of us are on this phone. I had an S5 ordered, but decided against it, when I saw there wasn't any progress being made on it. I cancelled my order, bought my M8, and haven't looked back. Give me an unlocked bootloader, or give me death.

You can S-OFF (which unlocks bootloader) & root it immediately after getting it.
I came from a locked Galaxy S4 and have to say this phone is snappier than an iPhone & as unlockable as a door thats compatible with all keys ;D. Love love loveeee this phone and highly recommend it! Go for it!
I unlocked mine the moment I got home with it, no OTA update required as some people have said to do before unlocking it & as far as I've seen no ones had an actual "Oh no! They made it impossible to unlock like Sammysung!" moment.

Ive tried a for the last two days to root my htc m8..but i can not get it to work...tried htc unclock tried setting up adb...but the first gives me an mid error and the second does not recognize my phone...i did install the newest update before i tried to s-off....any help would be great...

Frausbite77 said:
Ive tried a for the last two days to root my htc m8..but i can not get it to work...tried htc unclock tried setting up adb...but the first gives me an mid error and the second does not recognize my phone...i did install the newest update before i tried to s-off....any help would be great...
Click to expand...
Click to collapse
Have u tried the weak sauce app for root then fire water to s-off?
Sent from my Insanely powered M8 using Tapatalk

holla420 said:
Have u tried the weak sauce app for root then fire water to s-off?
Sent from my Insanely powered M8 using Tapatalk
Click to expand...
Click to collapse
I set up adb using the method from root junky. but my computer won't recognize my device. I must have tried it like 50 times, so i tried the htcdev unlock method...my computer recognizes by device but after i copy the token i get the mid 160 error.

Frausbite77 said:
I set up adb using the method from root junky. but my computer won't recognize my device. I must have tried it like 50 times, so i tried the htcdev unlock method...my computer recognizes by device but after i copy the token i get the mid 160 error.
Click to expand...
Click to collapse
U must not being in the right directory
Sent from my Insanely powered M8 using Tapatalk

Frausbite77 said:
I set up adb using the method from root junky. but my computer won't recognize my device. I must have tried it like 50 times, so i tried the htcdev unlock method...my computer recognizes by device but after i copy the token i get the mid 160 error.
Click to expand...
Click to collapse
What that guy above me said, if you using Windows make sure you right click+shift in the platform tools directly then see if it shows up with adb devices, if not check your drivers.

Frausbite77 said:
Ive tried a for the last two days to root my htc m8..but i can not get it to work...tried htc unclock tried setting up adb...but the first gives me an mid error and the second does not recognize my phone...i did install the newest update before i tried to s-off....any help would be great...
Click to expand...
Click to collapse
HTCDEV unlock doesn't work for the Verizon variant. To s-off just follow this step by step guide:
http://forum.xda-developers.com/showthread.php?t=2708628
PRO TIPS: Let's say that your adb and fastboot files are located in C:\Program Files\Android. Add this directory to your system path by pressing the Windows key and typing "environment". After a few letters you'll see an option called "Edit the System Environment Variables". Click on this option. The system properties windows will open to the Advanced tab. Click the Environment Variables button. In the System Variables field you'll see a variable called Path. Click on it and choose edit. In the variable value field you'll see a list of paths separated by semi colons. We want to add the path of your adb and fastboot files to the system Path variable so that adb and fastboot commands can be executed anywhere. For the example location I used above you would add the following to the end of the list:
;C:\Program Files\Android
To test, open a command prompt and type "adb". This should launch adb with no parameters. Now you can use adb and fastboot commands anywhere. When you download the firewater script file, you can just leave it in the Downloads directory. If you use Chrome you could click the arrow next to the file and choose "show in folder". Then shift+right click an empty portion of the Downloads directory window and choose "open command window here" (you can also shift+right click on folders icons to accomplish this). Should be easy to s-off now.
NOTES:
*Once adb is setup issue the command "adb devices" to ensure your phone is recognized. The first time you will get a popup on your phone asking if you want to allow the PC adb access. Make sure you check "always allow".
*Before you issue the "su" command wait about 30 seconds to allow WeakSauce to root the phone after reboot. If you get an error saying "su not found" it's because WeakSauce has not yet rooted the phone. Wait 10 seconds and try again.
*When you issue the "su" command wake your phone's display and look for a SuperSu request. Allow it obviously.
*It's possible that the process may fail. If it does just try again. If it keeps failing try a different USB 2.0 port. Also make sure you're using the best USB cable that you have. The one that came with the phone should work.

Doc Ames said:
HTCDEV unlock doesn't work for the Verizon variant. To s-off just follow this step by step guide:
http://forum.xda-developers.com/showthread.php?t=2708628
PRO TIPS: Let's say that your adb and fastboot files are located in C:\Program Files\Android. Add this directory to your system path by pressing the Windows key and typing "environment". After a few letters you'll see an option called "Edit the System Environment Variables". Click on this option. The system properties windows will open to the Advanced tab. Click the Environment Variables button. In the System Variables field you'll see a variable called Path. Click on it and choose edit. In the variable value field you'll see a list of paths separated by semi colons. We want to add the path of your adb and fastboot files to the system Path variable so that adb and fastboot commands can be executed anywhere. For the example location I used above you would add the following to the end of the list:
;C:\Program Files\Android
To test, open a command prompt and type "adb". This should launch adb with no parameters. Now you can use adb and fastboot commands anywhere. When you download the firewater script file, you can just leave it in the Downloads directory. If you use Chrome you could click the arrow next to the file and choose "show in folder". Then shift+right click an empty portion of the Downloads directory window and choose "open command window here" (you can also shift+right click on folders icons to accomplish this). Should be easy to s-off now.
NOTES:
*Once adb is setup issue the command "adb devices" to ensure your phone is recognized. The first time you will get a popup on your phone asking if you want to allow the PC adb access. Make sure you check "always allow".
*Before you issue the "su" command wait about 30 seconds to allow WeakSauce to root the phone after reboot. If you get an error saying "su not found" it's because WeakSauce has not yet rooted the phone. Wait 10 seconds and try again.
*When you issue the "su" command wake your phone's display and look for a SuperSu request. Allow it obviously.
*It's possible that the process may fail. If it does just try again. If it keeps failing try a different USB 2.0 port. Also make sure you're using the best USB cable that you have. The one that came with the phone should work.
Click to expand...
Click to collapse
Thank you for letting me know about the HTC Dev...I have a mac and set up ADB...it shows my phone off line...i get the message that says allow this computer and check always...i run adb devices and now it just returns blank...i reinstall drivers which is htc sync but the problem persists....

Frausbite77 said:
Thank you for letting me know about the HTC Dev...I have a mac and set up ADB...it shows my phone off line...i get the message that says allow this computer and check always...i run adb devices and now it just returns blank...i reinstall drivers which is htc sync but the problem persists....
Click to expand...
Click to collapse
Try 'adb kill-server' then issue 'adb start-server' then try 'adb devices'. If that doesn't work, try a different USB port. If still no joy try a different USB cable. If that doesn't work try restarting the Mac, restarting the phone, spinning around in an office chair three times, and blowing into a Nintendo cartridge. If that doesn't work I don't know what else to suggest besides trying it on a different computer or maybe in Windows. I've never had an issue with ADB so if somebody else has any ideas for Frausbite77 please chime in.
Edit: I googled this Mac ADB guide. I don't know if it really matters, but it says to have ADB/fastboot in the /usr/bin directory. Check it out. There's a script file and when run it installs the Android SDK tools to the appropriate folder. Also check the comments. Somebody else has probably had the same problem as you:
http://htc-one.wonderhowto.com/how-...-mac-os-x-send-commands-your-htc-one-0151178/
Edit 2: After reading a user's comment that the script was broken I looked at the script and it was, in fact, broken. I fixed it. Follow the guide but use this zip instead:

Doc Ames said:
Try 'adb kill-server' then issue 'adb start-server' then try 'adb devices'. If that doesn't work, try a different USB port. If still no joy try a different USB cable. If that doesn't work try restarting the Mac, restarting the phone, spinning around in an office chair three times, and blowing into a Nintendo cartridge. If that doesn't work I don't know what else to suggest besides trying it on a different computer or maybe in Windows. I've never had an issue with ADB so if somebody else has any ideas for Frausbite77 please chime in.
Edit: I googled this Mac ADB guide. I don't know if it really matters, but it says to have ADB/fastboot in the /usr/bin directory. Check it out. There's a script file and when run it installs the Android SDK tools to the appropriate folder. Also check the comments. Somebody else has probably had the same problem as you:
http://htc-one.wonderhowto.com/how-...-mac-os-x-send-commands-your-htc-one-0151178/
Edit 2: After reading a user's comment that the script was broken I looked at the script and it was, in fact, broken. I fixed it. Follow the guide but use this zip instead:
Click to expand...
Click to collapse
Ok, well so I never got adb to show my device on line....but when i typed ./adb reboot, the device actually responds to the commands...taking a risk i went ahead and pushed the firewater files and the process worked. I was able to unlock my device and install twrp...so i figured out that for and to work i have to type in ./ before i type in any commands...i don't if i messed something up along the way or what...but in the end i have gotten i was able to root and get s off....maybe i got lucky lol...thanks so much for the help!!

Frausbite77 said:
Ok, well so I never got adb to show my device on line....but when i typed ./adb reboot, the device actually responds to the commands...taking a risk i went ahead and pushed the firewater files and the process worked. I was able to unlock my device and install twrp...so i figured out that for and to work i have to type in ./ before i type in any commands...i don't if i messed something up along the way or what...but in the end i have gotten i was able to root and get s off....maybe i got lucky lol...thanks so much for the help!!
Click to expand...
Click to collapse
That's the proper command line for using Adb on a Mac. It won't work without using ./ before the command.
Sent from my HTC6525LVW using Tapatalk

Frausbite77 said:
Ok, well so I never got adb to show my device on line....but when i typed ./adb reboot, the device actually responds to the commands...taking a risk i went ahead and pushed the firewater files and the process worked. I was able to unlock my device and install twrp...so i figured out that for and to work i have to type in ./ before i type in any commands...i don't if i messed something up along the way or what...but in the end i have gotten i was able to root and get s off....maybe i got lucky lol...thanks so much for the help!!
Click to expand...
Click to collapse
My bad. I should have mentioned that to execute a file in a Unix-like operating system you need to enter the full or relative path if it's not in your $Path environment variable. That's why you needed to add a './' before the command. The './' indicates that the file is in the current directory. That's probably why that guide recommended putting adb and fastboot in /usr/bin. If you want to fix it so that adb and fastboot commands can be run from anywhere open a terminal, change to the directory where adb and fastboot are located, and issue the following commands:
sudo mv adb /usr/bin
sudo mv fastboot /usr/bin
That will move adb and fastboot into /usr/bin which is in your $Path so you can issue the commands anywhere without using './'. I'm glad you got your M8 s-offed and recovery installed. If you're looking into custom ROMs, I can personally recommend ViperOne as a great stock option and LiquidSmooth as an AOSP option. Try em' out. Now that you have recovery you can just restore a backup if you don't like your current ROM.

Doc Ames said:
My bad. I should have mentioned that to execute a file in a Unix-like operating system you need to enter the full or relative path if it's not in your $Path environment variable. That's why you needed to add a './' before the command. The './' indicates that the file is in the current directory. That's probably why that guide recommended putting adb and fastboot in /usr/bin. If you want to fix it so that adb and fastboot commands can be run from anywhere open a terminal, change to the directory where adb and fastboot are located, and issue the following commands:
sudo mv adb /usr/bin
sudo mv fastboot /usr/bin
That will move adb and fastboot into /usr/bin which is in your $Path so you can issue the commands anywhere without using './'. I'm glad you got your M8 s-offed and recovery installed. If you're looking into custom ROMs, I can personally recommend ViperOne as a great stock option and LiquidSmooth as an AOSP option. Try em' out. Now that you have recovery you can just restore a backup if you don't like your current ROM.
Click to expand...
Click to collapse
Thanks for the advice...actually i was just going to ask about some roms...just flashed viper rom and gonna give it a go...thanks for all the help...

Frausbite77 said:
Thanks for the advice...actually i was just going to ask about some roms...just flashed viper rom and gonna give it a go...thanks for all the help...
Click to expand...
Click to collapse
You'll love it. A couple thing to note though. For some reason the 1.6 download doesn't actually contain the 1.6 OTA so you'll want to go to 'About phone' and update to 1.6. Also I believe that ViperOne defaults to power saver mode. You can change this by using the toggle in the notification drawer. If you want to add power saver and extreme power saver to the settings menu follow this guide:
http://forum.xda-developers.com/showthread.php?t=2710946

Doc Ames said:
You'll love it. A couple thing to note though. For some reason the 1.6 download doesn't actually contain the 1.6 OTA so you'll want to go to 'About phone' and update to 1.6. Also I believe that ViperOne defaults to power saver mode. You can change this by using the toggle in the notification drawer. If you want to add power saver and extreme power saver to the settings menu follow this guide:
http://forum.xda-developers.com/showthread.php?t=2710946
Click to expand...
Click to collapse
wow, man viper rom is insane, thanks for the update heads up...i wouldn't have even thought to do that...guess i have tons of reading to catch up on...thanks...

Having Problems using ADB after a reboot

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).