When my watch connects to any PC via cradle, it's never detected. On Windows, I get a USB device malfunction. On Linux, it's not even detected. Via Bluetooth, it's unauthorised. So I can't even do basic file transfers to my watch. Anyone have a clue what I can do to get this working?
jrk190 said:
When my watch connects to any PC via cradle, it's never detected. On Windows, I get a USB device malfunction. On Linux, it's not even detected. Via Bluetooth, it's unauthorised. So I can't even do basic file transfers to my watch. Anyone have a clue what I can do to get this working?
Click to expand...
Click to collapse
I don't mean to insult, but do you have usb debugging enabled under the developer options and bluetooth debugging enable in the watch + app? If so, you might try an FDR on your watch (unpair with phone). I used a MacBook Pro when I unlocked the bootloader on my g watch thinking I was going to try Asteroid OS. I had just re-rooted my 6P using the Mac so I knew ADB/Fastboot was working on the computer. It wouldn't work initially and I knew the unlocking process was going to reset the watch either way. After the FDR everything started working again and I was able to unlock the bootloader. Don't know why but that helped me. Good luck.
Alexandgut said:
I don't mean to insult, but do you have usb debugging enabled under the developer options and bluetooth debugging enable in the watch + app? If so, you might try an FDR on your watch (unpair with phone). I used a MacBook Pro when I unlocked the bootloader on my g watch thinking I was going to try Asteroid OS. I had just re-rooted my 6P using the Mac so I knew ADB/Fastboot was working on the computer. It wouldn't work initially and I knew the unlocking process was going to reset the watch either way. After the FDR everything started working again and I was able to unlock the bootloader. Don't know why but that helped me. Good luck.
Click to expand...
Click to collapse
You're perfectly fine, no insult taken.
Debugging is enabled on the watch with Bluetooth as well, debugging is enabled on the phone and in the companion app. I get an authorization error and never get promoted for key on the watch, and when plugged in I get a USB descriptor error. I tried using another dock, another USB cable, and another port, and had no luck. I factory reset several times but I just redid it, so I'll give it another go and see if I can get it to work.
jrk190 said:
You're perfectly fine, no insult taken.
Debugging is enabled on the watch with Bluetooth as well, debugging is enabled on the phone and in the companion app. I get an authorization error and never get promoted for key on the watch, and when plugged in I get a USB descriptor error. I tried using another dock, another USB cable, and another port, and had no luck. I factory reset several times but I just redid it, so I'll give it another go and see if I can get it to work.
Click to expand...
Click to collapse
I had this issue for the longest time, try copying your adb_keys.pub from the ./android folder (I know it's C:/Users/yourusername/.android on Windows, and I believe it's ~./android on macOS/OSX, but I don't have a Mac to verify) on your computer to /data/misc/adb/adb_keys on the watch. You may need to either be rooted or have TWRP, I can't remember for sure because I was already rooted when adb had stopped working for me
zack4200 said:
I had this issue for the longest time, try copying your adb_keys.pub from the ./android folder (I know it's C:/Users/yourusername/.android on Windows, and I believe it's ~./android on macOS/OSX, but I don't have a Mac to verify) on your computer to /data/misc/adb/adb_keys on the watch. You may need to either be rooted or have TWRP, I can't remember for sure because I was already rooted when adb had stopped working for me
Click to expand...
Click to collapse
Well I have TWRP, but the watch isn't detected for mtp even connected to the PC...
jrk190 said:
Well I have TWRP, but the watch isn't detected for mtp even connected to the PC...
Click to expand...
Click to collapse
Have you tried to delete and update the drivers for the watch?
Related
anyone have a 64-bit adb driver for the slide
Where is the 32 bit? I plugged my phone into my PC last night when I got home, and it couldn't use the driver I recently downloaded that I was using for the G1... Or do i have to manually update the driver again using the same driver INF file I used for the G1?
fermunky said:
Where is the 32 bit? I plugged my phone into my PC last night when I got home, and it couldn't use the driver I recently downloaded that I was using for the G1... Or do i have to manually update the driver again using the same driver INF file I used for the G1?
Click to expand...
Click to collapse
it took a few days after nexus release to get a proper driver so im thinking we will be waiting a day or 2.
I used the 64bit driver for the Dream and my Vista64 had no trouble connecting to my Slide in ADB.
Thanks Fordude on Android Fourums!!!
1. Used USBDeview to uninstall all of the HTC drivers/ports
2. Unplugged HTC from PC
3. Installed PDANet software for Android (free).
4. When prompted, plugged in slide
5. After successful report of drivers being installed and program, accessed adb just fine!
Click to expand...
Click to collapse
Worked great for me on win7/64. SDK and Android Browser both work, still need root though
Also tried to use Apps2sd update zip, needs to be signed for this phone if anyone would be willing.
apps2sd--http://paulw.hardmilk.com/downloads/r1-a2sd-desire-dalvik-fresh-signed.zip
and the instructions for ADB were found here
http://androidforums.com/t-mobile-mytouch-slide/90832-adb-drivers.html
I'll have to give this a try. I remember using PDANet a while back and it worked, so probably will work again. Thanks
awesome i got it working now thanks
Strange, I'm still getting an error on mine. When I plug mine in, it tries to install the drivers, and then the windows driver install box tells me that the device is not configured correctly. And yes I have USB debugging turned on.
chrisinaz said:
Strange, I'm still getting an error on mine. When I plug mine in, it tries to install the drivers, and then the windows driver install box tells me that the device is not configured correctly. And yes I have USB debugging turned on.
Click to expand...
Click to collapse
On this phone, I had to change the default connection mode to Charge Only, and then also make sure Debug mode was enabled. It kept automatically turning into a mass storage device even though debug was enabled at the same time. Also, use USBDeview, it will find all your HTC/MyTouch/ADB/Android drivers installed. Remove them, unplug phone, reinstall PDANet, and you're golden.
the HTC Sync update for the phone was released for the phone. it should contain the necessary and appropriate drivers.
fermunky said:
On this phone, I had to change the default connection mode to Charge Only, and then also make sure Debug mode was enabled. It kept automatically turning into a mass storage device even though debug was enabled at the same time. Also, use USBDeview, it will find all your HTC/MyTouch/ADB/Android drivers installed. Remove them, unplug phone, reinstall PDANet, and you're golden.
Click to expand...
Click to collapse
I've done all the steps in the proper order. Removed everything. However, my phone was defaulting to the USB Mass Storage mode, so I tried it again in Charge Only and it still fails.
I also couldn't find anything on HTC's website that pertains to poetik517's post. But I'll keep looking.
Thanks anyways guys, it's not that big of a deal for me to just wait.
http://member.america.htc.com/download/Driver/T-Mobile_myTouch_Slide/HTCSync2.0.35.exe
poetik517 said:
http://member.america.htc.com/download/Driver/T-Mobile_myTouch_Slide/HTCSync2.0.35.exe
Click to expand...
Click to collapse
Got it. For some reason Chrome had me Cached outside of the US, so it wasn't showing up for me.
For everyone's reference, make sure your selected country is US or just go here:
http://www.htc.com/us/support
chrisinaz said:
I've done all the steps in the proper order. Removed everything. However, my phone was defaulting to the USB Mass Storage mode, so I tried it again in Charge Only and it still fails.
I also couldn't find anything on HTC's website that pertains to poetik517's post. But I'll keep looking.
Thanks anyways guys, it's not that big of a deal for me to just wait.
Click to expand...
Click to collapse
You'll want to remove the driver again via USBDeview. THEN make sure Charge only is selected, reinstall PDANet, and then plug in phone. If it still doesn't work, you are doing something wrong, trust me.
Ok, so I found a few older threads on this, but no tips in them seem to work in my case. I can't seem to get my S4 to see the PC/USB connection and prompt to select Media Device or the like. The USB icon never even appears in the notification bar. The PC recognizes connection (USB tone sounds) and shows device ready to use, but phone never gives the option. Doesn't seem to matter if USB Debugging is checked or not, or anything else that I can find so far. Here's the things I can generally eliminate:
2 different USB cables worked on wife's S4 on two different PCs. Neither cable or PC worked with my S4
Tried reinstalling Samsung USB drivers just to be sure
Cold booted phone
Tried unchecking and re-checking USB debugging (also tried with it unchecked)
So when we take in working fine on wife's S4, I'd generally guess that we can eliminate cable and PC from the potential problem list. Phone is currently on stock rom, but rooted. Outside of that and freezing VZ Support, Knox, and VZ Tones, no other modifications to the OS. At this point, I'm pretty stumped. Any suggestions on other steps to try?
The problem is your USB settings in the hidden dialers. Look for tutorials on how to enable them, and once found, type *#0808#, and a list of usb otions will come up. Pick any with MTP and they'll work again.
Worked perfect. Thanks muchly!
aidankiller4 said:
The problem is your USB settings in the hidden dialers. Look for tutorials on how to enable them, and once found, type *#0808#, and a list of usb otions will come up. Pick any with MTP and they'll work again.
Click to expand...
Click to collapse
Not to threadjack, but...
On a related issue, win update tried to update my samsung ADP, etc drivers and failed. Ever since, I cannot connect to the PC. The PC doesn't even notice that the phone is connected. I tried the above fix to no avail (it is set to MTP) I uninstalled and reinstalled kies, tried troubleshooting the usb connection, ect...
Please help.
Im_Gumby said:
On a related issue, win update tried to update my samsung ADP, etc drivers and failed. Ever since, I cannot connect to the PC. The PC doesn't even notice that the phone is connected. I tried the above fix to no avail (it is set to MTP) I uninstalled and reinstalled kies, tried troubleshooting the usb connection, ect...
Please help.
Click to expand...
Click to collapse
Try installing/reinstalling Kies, it comes bundled with all the samsung drivers you'll need
Tried that. Twice. To no avail.
But it is no longer a problem. I installed eclipse rom and it now works again.
Who knows what went wrong...
And now it's not working again. Reinstalled (dirty) the ROM without any change. Thoughts?
So my Nexus 4 had a faceoff with the driveway yesterday and the touch screen is dead. The phone seems to work fine otherwise. I was hoping to access my phone via USB to get a few files and read an unread SMS message. The problem is that for me to use any adb shell commands or USB debugging tools or anything, I need to be able to click on the authentication popup on the phone, which of course I cannot do. Is there any way to get around this? The device is rooted, and clockworkmod is installed, if that helps. USB debugging is also enabled. It's just the authentication I cant do. I'm also not afraid of command lines. I'll give anything a try.
The only idea I've found so far is maybe a USB OTG mouse, but I'd rather do it today from my computer than wait for an adapter to arrive in the mail. Any other suggestions?
Thanks
So... now that I think with hindsight, I did something pretty stupid, and I'm going to need some help, since I have no idea what to do.
I have a Nexus 9 tablet, and I never liked it. The OS is just so slow and laggy, and it overheats, and it has many other problems. Quite a couple of times, I installed custom ROM's and so on, and I never had a problem. Let me explain what I did now.
Around a month ago, while looking on the internet, I heard this thing that if I install the original software, but with no encryption, it would work better. It sounded cool at the time, so I downloaded the Nexus Root Toolkit, and did it.
Everything went well. But then I heard about a custom ROM that was apparently working even better, Dirty Unicorns, so using the same toolkit, I installed it. For the first time, my Nexus 9 actually worked the way it is supposed to work, but the custom ROM still had its problems, it crashed from time to time. I was thinking about possibly returning or selling the tablet, so that's why using the Toolkit, I reinstalled the original software. But, if I went all the steps, and also locked the OEM, my device then showed a flag saying that it was a development device, while booting up. So, after messing around with the settings of the Toolkit a little, I decided to reinstall the software, but leave the bootloader unlocked.
But after some time, I reinstalled my Windows, and I also reinstalled the Toolkit. But that's when I started to have problems. My tablet wouldn't connect to my laptop anymore. I used the toolkit and uninstalled drivers, reinstalling others quite a couple of times, and that's where I think that I messed something up. I managed to eventually connect my tablet, and I rooted it, after rooting it, I connected it again. But adb wasn't working for some reason. A little annoyed, I simply copy pasted the zip file of CM13 into my tablet's internal storage, and I rebooted it to the recovery, TWRP. But the recovery failed to flash it, saying something about an Error 7.
Now that I think about it, I was stupid, since after that, I performed a complete factory reset, resetting my TWRP backup too. I tried to connect it again, nothing. It didn't connect at all. I plug it in, my computer doesn't even recognize that something is plugged in. No Nexus 9, no Android Device, no anything. I booted it in fastboot mode, and it worked, my computer recognized it, and after I downloaded a ROM zip file again, I tried to connect the tablet back and flash it manually, but nothing. It didn't recognize anything anymore.
I tried to reinstall the drivers countless times. I deleted what I had, reinstalled it, nothing. I uninstalled and reinstalled the Toolkit. But strangely, now, even if I know that I installed the Google USB drivers, and the ADB drivers, as I even installed Android SDK, if I use USB Deview, it doesn't show me any of them. I can't see any Google or ADB drivers, although I tried installing them multiple times. So now, I'm stuck with a tablet with TWRP and no OS, which I can't connect to my PC, and I can't use ADB or fastboot.
Is it something from my laptop? I can't check to see if it will connect to another PC right now, so I don't know for sure. Is there any way to delete all the traces from my (failed) attempts at reinstalling the drivers, and to install them again properly? Or is it something from the tablet itself? I don't have an OS, so I can't enable USB debugging.
So, shortly, I have no idea what's happening. And I'm quite obviously a noob in all of these. Can anyone help me? Please?
If you boot into the bootloader and from a command prompt type fastboot devices you don't get anything?
Sent from my Nexus 9 using XDA-Developers mobile app
I still couldn't get ADB to work, but I managed to work out fastboot. It may be something from my USB cable, it works perfectly.
I flashed the original software back, and I'll go to check my cable, although I feel kinda stupid that I didn't think about that in the first place.
Thanks for the help anyway.
If fastboot is working and bootloader is unlocked, you can still install a factory image.
Depending of your device download for wifi Version:
https://dl.google.com/dl/android/aosp/volantis-mob30p-factory-2cb57a1b.tgz
If you habe the LTE variant:
https://dl.google.com/dl/android/aosp/volantisg-mob30p-factory-ae9ce05a.tgz
Extract the files and put them into the same directory link fastboot and execute the flash-all.bat
WARNING: Any data will be erased!!! Also TWRP
Now it should boot up with stock firmware.
If you want your device decrypted install twrp. format the internal storage and flash the pure nexus rom which i can highly recommend and is decrypted by default. Dont forget do flash gapps
my issue is same
what if someone USB- debug is not enabled , is there any possibility to do that , i have a device nexus 9 , rooted it it went into bootloop then i factory reset it , and now my adb is not communicating , if there is any options?
rohanzakie said:
what if someone USB- debug is not enabled , is there any possibility to do that , i have a device nexus 9 , rooted it it went into bootloop then i factory reset it , and now my adb is not communicating , if there is any options?
Click to expand...
Click to collapse
Use fastboot, not adb.
what if fastboot isn't working, either?
uberSkeptic said:
what if fastboot isn't working, either?
Click to expand...
Click to collapse
Is the tablet in fastboot mode?
madbat99 said:
Is the tablet in fastboot mode?
Click to expand...
Click to collapse
Yup. I can boot into the bootloader, and from there (or from TWRP) into fastboot, but no computer I've connected it to (and I've tried many) will recognize it. Doesn't show up in Device Manger or lsusb, doesn't show up from either "adb devices" or "fastboot list devices" (the latter just hangs there saying "Waiting for any device"). The USB on the tablet itself is fine, and I even replaced the USB daughter-board just to be safe.
uberSkeptic said:
Yup. I can boot into the bootloader, and from there (or from TWRP) into fastboot, but no computer I've connected it to (and I've tried many) will recognize it. Doesn't show up in Device Manger or lsusb, doesn't show up from either "adb devices" or "fastboot list devices" (the latter just hangs there saying "Waiting for any device"). The USB on the tablet itself is fine, and I even replaced the USB daughter-board just to be safe.
Click to expand...
Click to collapse
Hi, uberSkeptic...
Just a quick thought... Have you tried a different USB cable?
Rgrds,
Ged.
Edit & Additional...
The command is not fastboot list devices... it's fastboot devices
One last point... Ensure your Nexus 9 is definitely booted into fastboot mode and not just HBOOT (the bootloader). Take a look at the two screenshots below - your Nexus 9 should look like the screenshot on the right, the one with my green explanatory text.
Apologies for the poor image quality; there's no way of taking a screenshot in the bootloader, so I had to take photographs instead.
Hope this helps and good luck.
Thanks for the advice and going so far as to photograph the hboot/fastboot screens, but unfortunately I have indeed tried multiple USB cables, including the OEM's and I've definitely successfully gotten the tablet into fastboot but it doesn't show on the computer with either fastboot command (devices or devices list).
uberSkeptic said:
Thanks for the advice and going so far as to photograph the hboot/fastboot screens, but unfortunately I have indeed tried multiple USB cables, including the OEM's and I've definitely successfully gotten the tablet into fastboot but it doesn't show on the computer with either fastboot command (devices or devices list).
Click to expand...
Click to collapse
I'm out of ideas then.
One of my first thoughts was possible Windows driver problems, but as you mentioned you'd tried it on several different computers, that didn't seem to be a likely cause of the problem - I mean, you'd expect at least one of 'em to work! Maybe somebody else can help with a solution.
GedBlake said:
I'm out of ideas then.
One of my first thoughts was possible Windows driver problems, but as you mentioned you'd tried it on several different computers, that didn't seem to be a likely cause of the problem - I mean, you'd expect at least one of 'em to work! Maybe somebody else can help with a solution.
Click to expand...
Click to collapse
Sadly, me too. I even tried using a flash drive with a micro-USB connector on it, which I used to use to do nandroid backups, but now TWRP doesn't even "notice" that the USB drive is there (or any USB drive connected via an OTG cable).
Too bad, too - the tablet is otherwise in great condition and even has a custom-painted backplate (long story).
Thanks for trying to help, though!
uberSkeptic said:
...The USB on the tablet itself is fine, and I even replaced the USB daughter-board just to be safe.
Click to expand...
Click to collapse
Mmm...
uberSkeptic said:
...I even tried using a flash drive with a micro-USB connector on it, which I used to use to do nandroid backups, but now TWRP doesn't even "notice" that the USB drive is there (or any USB drive connected via an OTG cable).
Click to expand...
Click to collapse
Mmm... (scratches head, raises eyebrow quizzically)...
If I was Hercule Poirot and this was a murder case, and with all the suspects gathered in one room, prior to revealing a brilliant deduction... I'd be casting very dark glances in the direction of your Nexus 9's USB port right now as the likely culprit here.
Think about it. Different computers. Different USB cables. An OTG cable... And none of them work. What's the one thing they all have in common?
Answer: The USB port on the Nexus 9 itself, and where you've replaced the USB daughter-board.
Maybe, possibly, that replacement don't go so well. Maybe there's some unknown problem with it. I can't comment too much on this, 'cos it outside the scope of my knowledge - I'm a software guy; circuit boards and dismantling devices to fix 'em isn't something I'm comfortable with. I always think I'm going to damage something or rip a wire out somewhere, so I bow to your superior knowledge in this area, as I may be talking complete cobblers here. It certainly wouldn't be the first time.
Anyway... Sorry I wasn't able to help find a working solution for you. If anything occurs to me that might help, I'll be sure to let you know.
Rgrds,
Ged.
I would be suspect if the replacement as well if it weren't for the fact that I did it only AFTER the other symptoms/problems appeared. Hence the replacement (which is known good because the battery charges no problem). There cables and everything inside the tablet tests just fine... It feels like the firmware for USB is somehow corrupt or something.
Thanks for all the advice, though. ?
So I can't believe I didn't think of this before, but when I run "dmesg" from the terminal app included w/ TWRP, I see that there a TON of errors, mostly referencing problems accessing the recovery image. I could screenshot it, if anyone at all might be able to tell me a little more specifically what the dmesg log is trying to tell me...
So I have been trying to root my Moto G Power 2021 all day. I have been following the guide to using Magisk the non-twrp way, and I keep hitting the same snag over and over again. So far, I have successfully unlocked the bootloader, downloaded and installed the latest Magisk apk (Magisk25.2.apk) form the github page, and downloaded and installed the official Rescue and Smart Assistance (LMSA) on my computer. The problem that I am having is that whenever I plug my phone into my computer while I have RSA open, it asks me to authorize the computer to use it, but nothing opens on my phone to give me that option.
Before I am asked, yes I have Developer tools unlocked, the OEM is unlocked already (As I said above), and I have made sure that USB Debugging was allowed.
Please, tell me where I'm going wrong with this if anywhere?
The only other information I can think to add is that my phone IS running Android 11, but I'm unsure if that matters as I have seen other guides that explain how to root on Android 11.
Thanks in advance for any information that can be given!
First thing: Have you installed the specific Motorola USB Drivers on your PC?
Link: https://motorola-global-portal.cust...can-i-download-the-usb-drivers-for-my-device?
sdembiske said:
First thing: Have you installed the specific Motorola USB Drivers on your PC?
Link: https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481/~/where-can-i-download-the-usb-drivers-for-my-device?
Click to expand...
Click to collapse
Yes I did. I also tried uninstalling and reinstalling it when you linked it in case I didn't have it installed correctly, and that still did not work.
The below image is what I keep getting when I attempt to connect to RSA with my phone, and nothing at all like that shows up on my phone to verify.
Had you previously authorized the phone on that PC, i.e., using adb, etc? If so, you may not have to authorize it again. Have you actually tried to do anything with RSA or just wondered why the authorization notification doesn't show on your phone? Does the USB debugging pop-up show in the status bar on your phone when you're connected? If so, you're connected and were already authorized.
Other than that, your antivirus/firewall software may be blocking the connection and you'll have to allow the app to connect to the phone there. May also want to check that your USB cord isn't the issue by trying another one with data capabilities.
Please see the N.B. in my signature below.
Thanks! I'll give that a shot and update when I've got a chance. I don't believe it's the USB cable since it's the cable that came with the phone, so I'll try the antivirus/firewall software side of things first.
Small edit:
I forgot to actually answer your question before. No, I hadn't already authorized this computer, as this is actually a pretty new computer (Only a few months old at this point). The USB debugging shows up at the top of my phone yes, but RSA won't do anything unless I authorize it, which gives me conflicting impressions that the phone seems to think it's verified the computer, but the computer and program don't see the verification.
sdembiske said:
Had you previously authorized the phone on that PC, i.e., using adb, etc? If so, you may not have to authorize it again. Have you actually tried to do anything with RSA or just wondered why the authorization notification doesn't show on your phone? Does the USB debugging pop-up show in the status bar on your phone when you're connected? If so, you're connected and were already authorized.
Other than that, your antivirus/firewall software may be blocking the connection and you'll have to allow the app to connect to the phone there. May also want to check that your USB cord isn't the issue by trying another one with data capabilities.
Please see the N.B. in my signature below.
Click to expand...
Click to collapse
Thank you! That worked! I was able to get it sorted out, AND following the root guide, I was able to get my phone rooted too! Thank you very much again!
@Cloud557 How did you unlock bootloader? I have cricket moto g power 2021 but I checked with Motorola and apparently this model cannot be unlocked? Thanks