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
Related
Please take the time to read this:I flashed and installed SkyRaider a couple days ago and I noticed when I connected to my PC that my PC started recognizing it as HTC Phone (or something of the like). This apparently really screwed up my drivers on my computer because I installed iKReaM and now I can't even get into disk drive mode...it doesn't ask what connection type I want anymore and my computer just says "USB Device Not Recognized". I tried uninstalling the HTC Driver Installer but that didn't do anything either. This is not good as I ran into the same problem when trying to root my friends Samsung Fascinate and never go the problem fixed. Anyways...my phone worked perfect before and SkyRaider evidently messed it up pretty good...to say I am pissed is an understatement. If you need any more info please let me know.
Please link me to the newest HTC Drivers as well, it would be much appreciated.
If no one can help I will have to do a clean install of windows 7, which is not an enjoyable experience
https://market.android.com/details?id=com.dooblou.WiFiFileExplorer&hl=en
You will have to buy the pro version to push files. That would be your easy solution.
You can always use recovery to get into usb mode as well.
Stratejaket said:
https://market.android.com/details?id=com.dooblou.WiFiFileExplorer&hl=en
You will have to buy the pro version to push files. That would be your easy solution.
You can always use recovery to get into usb mode as well.
Click to expand...
Click to collapse
I can't get into recovery anymore using usb mode, computer doesn't recognize the device so no way to use it...and I would use the Wifi app instead of using a usb cable? I see what you mean by easy but I don't wanna avoid the problem...I have a brand new $1600 Alienware so I would like to have it fixed lol...if need be I may just have to do a clean install
I know this isn't your actual problem but just for the record, AirDroid lets you control your phone and push files to it with a web browser and wifi for free.
(I tried linking it but I guess I haven't made enough posts to include links yet, easy to find by searching the Market tho)
You might check under Settings/ Connect to PC to make sure the Ask Me option is turned on.
Sent from my ADR6400L using Tapatalk
When you plug your phone into your computer does the phone start to charge?
If so restart the computer and plug the phone into a different usb port. Check device manager and see if you have it listed in your usb devices, or you have an ! over a usb. Most of the time this ends up being an issue with the computer it is being hooked to, not the phone. The computer isn't launching the driver correctly to show the phone that it is connected to a computer, and not just a wall outlet.
Even when I've had this issue, which is random I have still been able to use recovery usb to manage it. Make sure when your in recovery you mount the sdcard before enabling the usb.
Hey guys. I'm trying to root my m8 by using the toolkit. Well, I try to get the Token ID but adb fails since it can't find any devices. I've uninstalled the drivers, re installed, tried different sources, everything and I just can't get it to be recognized by ADB.
Anybody have any ideas? I'm running Win8x64
Regards
Smith
I'm having the same problem
smithisize said:
Hey guys. I'm trying to root my m8 by using the toolkit. Well, I try to get the Token ID but adb fails since it can't find any devices. I've uninstalled the drivers, re installed, tried different sources, everything and I just can't get it to be recognized by ADB.
Anybody have any ideas? I'm running Win8x64
Regards
Smith
Click to expand...
Click to collapse
Make sure your SDK is up to date, and that you are opening the command prompt from the proper location. Also make sure that USB debugging is enabled in developer options on the device.
I've had the same issue. I did all of the above and even tried on a Mac and adb still hasn't recognized my phone. Im on win 7x64. Still researching for an answer.
I'm not sure if this will hold true for everyone, but what worked for me was to updat the adp.exe and dlls. Then after I did that, ran the get token script from the toolbox, open the phone to the home screen, and accept the connection request from the computer.
I ended up having to just start the process over again on a different computer, but it worked, so I'm happy lol.
Regards
Smith
You can also try disabling USB Debugging and re-enabling it while the USB is connected. Works for me so far
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?
Calling all A95X MAX owners!
Has anyone successfully connected this TV box to a PC in order to send ADB commands?
I installed the S905X2 USB drivers that come with the S905X2_USB_Burning_Tool. With USB debugging on, I put the A95X MAX into bootloader and connected it to my PC with a male-to-male type-a USB cable, but there was no reaction in the PC's device manager, where you'd expect to see the Android USB driver appear when a connection is made. (I did get power throught the cable, for when I unplugged the power to the A95X MAX it remained on with the USB cable plugged in.)
Is there something I don't know about or has no-one here tried to connect the box to a PC via USB?
It would be useful to send ADB & fastboot commands to this TV box.
I feel your pain
doktorspin said:
Calling all A95X MAX owners!
I also have tried to connect via usb to the a95x max us and MANY other amlogic manufactured tv boxes without success.
You would think some expert person from this forum would respond to this issue once and for all... GRRRR....but noooooooo, no such expert person seems to want to answer the bell here or in any other related tech forum I have gone to. Is it possible no one on the planet knows the answer to this?
Attempting tech support at both gearbox and geekbuying websites, places where one typically purchases such tv boxes have yielded nonsensical/completely useless/incompetent answers so no point going there for any such related support.
Anyway. From what have been able to observe, the burning tool driver shown as "libusb-win32 usb devices" known strangely as the "world cup" driver, "only works for the burning process app as far as the box being recognized by the burning tool app via a USB connection but it seems it has nothing to do with the device being recognized by the ADB.EXE PC side app when using the USB connection.
For that you need an "android composite ADB interface driver". Unfortunately, none of the google or Microsoft or any "universal" ADB USB drivers I have tried, seem to work for these amlogic tv boxes which throws you back to having to go to the amlogic manufacturer to download their drivers from there.
Although this makes almost too much sense, you won't find any downloadable drivers at their site, "amlogicdot com, so we all are back to step one...GRRRRR.
So, until a forum expert from this xda-developers site finally decides to help with this issue....if in fact that will ever happen, we are all pretty much stuck in the mud here as far as the needed USB connection. Until that happens, here is a work around I developed which will let you communicate with these boxes without the need for any USB drivers as long as such amlogic boxes come rooted.
The TCPIP wireless or wired connection trick:
What many folks don't know is that if the box is unrooted you will ALWAYS need to have an initial USB connection before one can switch over to a tcpip connection ("ADB tcpip 5555" command after you have FIRST established a USB connection), but if the box is rooted you do NOT have to have an initial successful USB connection!!!
The secret is to switch over to tcpip at the Android device FIRST by using one of many apps on the android device that activates this such as "WIFI ADB" or "ADB WIFI reborn" app etc. Don't bother with the ones that say no root or any other app that says you need to connect a USB cable first since that defeats the whole point of this post right?...smile.
The app typically will give the IP address of your device along with the command needed on the PC side such as "ADB connect 192.168.1.3:5555" (the device IP address along with its port number ) which allows you to connect your PC to the android device via tcpip WITHOUT ever connecting to any USB cable and having to worry about non functioning USB drivers.
In closing, although I think I have provided a life saver solution for those that cannot get the USB connection to work to still be able to connect to their android device regardless of a non-working USB connection, there are cases where windows apps relying on ADB won't work even with a rooted device because these developers at program entry, STUBBORNLY just look for a USB connection instead of looking and USING A-N-Y valid and working connection as should be the case regardless if it’s thru USB or tcpip.
If any other forum member can help us figure out how to force these win apps to use ANY available valid working connection and not just a usb connection this post would then have a COMPLETE solution to this issue.
Hopefully the explained tcpip work around in this post can help those stuck with a non-working usb connection.
Cheers Ed Ray;
Click to expand...
Click to collapse
Ed,
Thanks for your response. I've been trying another approach to deal with my basic problem of being able to flash a system image (a ROM) onto the A95X MAX. It mainly involved trying to get TWRP running and get it to flash the image. That seemed to be unsurmountable. So now I'm looking into the possibility of putting the system image into a zip file with a little glue and using stock recovery to flash it from the SD card.
In the process I found instructions as to how to get ADB up & running over ethernet here:
https://stackoverflow.com/questions/2604727/how-can-i-connect-to-android-with-adb-over-tcp
Sounds like it should work, but I'm drained on this system into a zip file thing.
Cheers.
Good Morning Ladies and Gents;
I am working with an LG G4 H811 (T-Mobile) on 20v (MM 6.0), which I would like to root. I have unlocked the bootloader, which is confirmed every time I start the phone. I then tried to root using LGUP, but the phone wasn't recognized, so I did an error recovery reinstall in LG Bridge, thinking a fresh software install would re-align things.
Now, whenever I connect the phone to the computer, I get a pop-up window on the phone saying "USB Connection - Allow this computer to access your phone data?" CANCEL/ALLOW and the phone does not show up on the PC screen or in Device Drivers until I tap "ALLOW". Therefore, it is not recognized by any software without tapping ALLOW.
More than an inconvenience, this effectively prevents me from any mods on the phone, because I need to shut off the phone and disconnect from the USB port, then reconnect with Volume UP pressed to get to download, and in download mode I have no access to ALLOW the USB connection, so neither ADB nor FastBoot recognize any devices, and the phone is not included in Device Manager.
Of course, the bootloader is unlocked, Developer Options enabled, OEM Unlock on, USB Debugging on. I am using an original LG USB cable. I have tried 4 different computers and three different sets of drivers. I've tried older drivers on older and newer computers, and vice-versa, for every combination available. Each time, I plug in the phone after a fresh computer install and let it install it's own drivers. Two of the computers are Windows 7, two are Windows 10. I've tried connecting in MTP mode and PTP mode, with no difference. I've removed the SD card in case it was affecting things, and done a factory reset on the phone. Auto Play options have been set on the PC to "Do Nothing". I've searched the internet and this forum without results.
Basically, I've spent two days on this before asking for help. Has anyone else had this experience and solved it with something other than drivers? I think I've just about run out of ideas! Thanks.
I don't root however it's probably Developer options>usb default settings>usb tethering
Try connecting directly from Disk Management on the PC. Use the scan for new drives option if it's not visible.
Thanks buddy, appreciate you trying to help out.
Tethering is a way to allow a device connected to your phone to use the phone's data connections. In the tethering instructions:
"You may not be able to access the data files stored in the phone's memory, such as pictures, music etc, or transfer such files between your phone and your PC when USB tethering is on"
However, its worth a try - so I set up tethering, unplugged the phone and plugged it in again - the same Cancel/Allow screen came up, and no device in DM until I tapped Allow.
I then opened Disk Management and plugged in the phone. I still get the Cancel/Allow screen, and rescanning devices didn't show anything new, because the phone is not in the Device Manager until I tap Allow.
The key here is finding out why the phone or computer do not store the "Allow" command. Normally, the phone will show this screen the first time you plug it into a computer, and when you tap Allow, it will store that someplace such that the phone and computer are recognized as safe devices. You should never have to see the permission screen again. My challenge is that I don't know where that permission is stored - is it on the phone, the computer, attached to the driver? Don't know. And I don't know why it's not being saved. If I had those answers, I could probably edit the registry (or whatever) to make this a permanent attachment.
Thanks!
You're welcome.
Maybe debug mode?
Try turning off Developer options.
Obviously there is a way, sorry but I never had to use that function.
Try some Google searches which is how I usually find answers and/or by just playing with it
Well, I wouldn't be able to communicate via ADB with Developer Options off. And I spent two days searching the internet before coming here, and all I found was people updating their drivers, which is why I tried so many combinations of Windows versions and drivers versions.
I'm actually kind of surprised that this seems to be such a unique problem, I was hoping someone would notice the post who had actually had a similar problem and fixed it. But I do appreciate you trying to help!
Sorry I can't help, but I never choose to root.
It's time sucking black holes like this that I deliberately want to avoid.
At least you didn't brick it...
ha ha... you got that exactly right! Every time I do this I end up spending DAYS trying to get up to date on everything that has changed since my last phone!
Well, I appreciate you taking time to try to help.