Installed Fission 2.2.2 and I cannot get my phone to be recognized for ADB in any mode. I ensured I have the latest drivers. I can browse my SD Card contents on my PC and stuff, but the ADB Interface fails to install when I plug it into my PC.
zehkaiser said:
Installed Fission 2.2.2 and I cannot get my phone to be recognized for ADB in any mode. I ensured I have the latest drivers. I can browse my SD Card contents on my PC and stuff, but the ADB Interface fails to install when I plug it into my PC.
Click to expand...
Click to collapse
not sure if it is the same,
but a few times i couldn't get adb to work, the fun thing is then a "cd drive" was also mounted in pc mode... (using linux)
anyway, try the following:
got to: Settings -> Applications -> Development
uncheck (if it is) USB debugging
check USB debugging
replug usb (might not be necessary)
Just checked and mine worked fine in charge only mode.
Related
I've had ADB working successfully in the past, but now nothing is listed after an "adb devices" command, and a "device not found" error for other commands. I was on Royal Ginger 2, and just updated to the latest CM7 nightly - then wanted to use ADB to tweak a few things and found out something was wrong. What else do I need to do to get adb to recognize my device?
I haven't changed anything on my laptop, which is Win7 64bit, and I've updated everything in SDK Manager. Device Manager on the laptop shows T-Mobile myTouch4g USB Device under Disk drives on the Device Manager, and I believe I have the latest mt4g drivers installed. I'm connecting via USB with debugging turned on, and without turning on USB storage.
Any ideas?
I was finally able to get adb to recognize my device again. FYI, I tried a few different things, but I think what finally got it working was tweaking the *.inf file in the usb_driver folder in SDK, the uninstalling/reinstalling the drivers - as outlined here:
http://forum.xda-developers.com/archive/index.php/t-881324.html
Last night I finally decided to use Wugs Nexus Root Toolkit to unlock the bootloader, root the device, flash CWM recovery and installed SlimBean ROM. It was somewhat of a pain to get adb to work at first, it had me uninstall drivers off my PC. Now when connecting my tablet to my PC, PC is not letting me view the internal SD card, nothing comes up. I've tried connecting it to another Windows 7 PC, same issue. Wondering if its something with the ROM, anyone else had this problem? What's the solution.
Uninstall USB ADB Driver
I had the same problem. What ended up working was re-connecting the tablets via USB to my Windows 7 machine. Open up Device Manager and find Nexus 7, right-click on it and select Uninstall (this removes the ADB drivers that were used to root, etc). Then disconnect the USB cable and reconnect it. Then it should automatically reinstall the USB drivers for MTP access. Hope that helps.
That's actually what I had to do to get Root Toolbox to work....or so it said.. I'm surprised though, if I hook it up to another PC why that PC wouldn't automatically try to install the driver.. If I have it with USB debugging off, it doesn't show in the display manager, if I enable USB debugging it does. Tried uninstall, disconnect, reconnect USB cable, same issue.
Check your USB Connection settings for MTP yet?
Thank you. Didn't know where that was at first. Went to settings:storage:menu icon:USB connection settings: checked MTP. now my PC is detecting the N7.
My Win10 Insider Preview machine did not recognize the phone. Nothing happened when I connected the phone and I could not access storage of the phone.
Below is the solution for it:
Go to Control Panel - Device Manager - LeMobile Android Device (could be under a different name. Choose the one that is your phone) - Update Driver - Manually Install a Driver - Let me pick a list of available drivers on my computer - MTP USB .
4K2K said:
My Win10 Insider Preview machine did not recognize the phone. Nothing happened when I connected the phone and I could not access storage of the phone.
Below is the solution for it:
Go to Control Panel - Device Manager - LeMobile Android Device (could be under a different name. Choose the one that is your phone) - Update Driver - Manually Install a Driver - Let me pick a list of available drivers on my computer - MTP USB .
Click to expand...
Click to collapse
Uhm ... when you connected the phone to computer you changed the mode on phone from USB charging to MTP mode ?
In my Win10 x64 build 14392.447 not problem to see the phone in MTP mode after changing mode on phone.
Alternative solution is to use KDE Connect app over Wifi. Bonus is that once set up, it is possible to push files from the phone to the PC without any interaction on the PC side - e.g. useful if the PC doubles as a file server.
losteagle said:
Uhm ... when you connected the phone to computer you changed the mode on phone from USB charging to MTP mode ?
In my Win10 x64 build 14392.447 not problem to see the phone in MTP mode after changing mode on phone.
Click to expand...
Click to collapse
Both of my home & works computer (Win10 14959) failed to detect it as MTP or PTP drive. Might have been due to those having previous phone's drivers.
But I faced same problem with fresh out of the box Win8 laptop.
No issue with the MTP, however I can't seem to get adb to work. list of devices attached is showing empty.
ksj0823 said:
No issue with the MTP, however I can't seem to get adb to work. list of devices attached is showing empty.
Click to expand...
Click to collapse
I had the same issue, i reinstalled minimal ADB and removed the drivers from my pc, rebooted my pc. Plugged the phone into a different USB port and voilá ADB could see it
Citroon said:
I had the same issue, i reinstalled minimal ADB and removed the drivers from my pc, rebooted my pc. Plugged the phone into a different USB port and voilá ADB could see it
Click to expand...
Click to collapse
Wanted to add my voice here too that I did the same - I had to clean up previous drivers I had installed over time for varios phones and different ADB versions like the one from clockworkmod - once I cleaned that out and installed google drivers from SDK PTP worked and I was able to do Helium restores
I had issue on my Win10 PC, but I found that after I disabled USB debugging, it would work as MTP/PTP, but not for ADB of course. So apparently, I have to toggle USB debugging ON/OFF to switch back and forth from MTP and ADB.
Small pain in the butt.
Solution.
I had the same issue. Drove me NUTS for about an hour. In the end, simply unchecked the USB DEBUGING in developer settings. This will make it pop up immediately.
Update:
I clearly should have read the post above mine first.
The popup to allow USB debugging from my computer doesn't popup when I connect my Oneplus 5 to my computer, and thus ADB devices comes back empty. This is only happening for my PC on stock Rom. When I tried installing another Rom, the popup to allow USB debug option comes and the phone is getting detected in my PC. Even on stock Rom, in another PC popup to allow usb debug option comes, only in my PC stock Rom it is not getting detected. Not sure whats and wheres the issue(PC or Phone)?!
I I've rooted my phone before and it was working fine previously and it stopped being detect after OB10 . I looked online too and tried options like restarting, turning debugging off and on, revoke USB authorization etc...... nothing works Please HELP!!!!
swapnilshah said:
The popup to allow USB debugging from my computer doesn't popup when I connect my Oneplus 5 to my computer, and thus ADB devices comes back empty. This is only happening for my PC on stock Rom. When I tried installing another Rom, the popup to allow USB debug option comes and the phone is getting detected in my PC. Even on stock Rom, in another PC popup to allow usb debug option comes, only in my PC stock Rom it is not getting detected. Not sure whats and wheres the issue(PC or Phone)?!
I I've rooted my phone before and it was working fine previously and it stopped being detect after OB10 . I looked online too and tried options like restarting, turning debugging off and on, revoke USB authorization etc...... nothing works Please HELP!!!!
Click to expand...
Click to collapse
If you have a folder named '.android' in your User Directory, delete it and then try again. If this doesn't work uninstall your current ADB software and reinstall the Platform Tools package:
https://developer.android.com/studio/releases/platform-tools
I've had this once or twice and that always did the job.
Dirk said:
If you have a folder named '.android' in your User Directory, delete it and then try again. If this doesn't work uninstall your current ADB software and reinstall the Platform Tools package:
https://developer.android.com/studio/releases/platform-tools
I've had this once or twice and that always did the job.
Click to expand...
Click to collapse
Thanks will try that and update you...
Dirk said:
If you have a folder named '.android' in your User Directory, delete it and then try again. If this doesn't work uninstall your current ADB software and reinstall the Platform Tools package:
https://developer.android.com/studio/releases/platform-tools
I've had this once or twice and that always did the job.
Click to expand...
Click to collapse
I tried deleting .android folder in user directory and also reinstalled the platform tools package.... but still it is not showing the device in adb devices command.
swapnilshah said:
I tried deleting .android folder in user directory and also reinstalled the platform tools package.... but still it is not showing the device in adb devices command.
Click to expand...
Click to collapse
On the Stock ROM, where you are having the trouble, does your PC see the phone when you connect it. i.e does it show up as a device in Explorer and Device Manager? When you enable MTP can you transfer files?
As it's only a problem on the OOS ROM, i wonder if it's a Driver issue. When you installed the Platform Tools, did you install the Google USB Drivers?
Also have a look here. There may be some useful information:
https://stackoverflow.com/search?q=adb+doesn't+see+my+device+on+pc
try to use a different cable. it works for me
i had a same problem like you
had the same problem on my phone (manually added the adb public key to get access), only got fixed by factory reset. the popup just didnt show no matter what, even though adb worked.
Hi !
After a three months of not using my Nook Glowlight Plus (not rooted, it's standard), i turned it on, and tried to connect it to my Windows 10 PC.
Nothing appeared as USB Drive as expected. In fact, there's no device in the Device Manager list.
I tried in two other PCs with Windows 10, and in a fourth one with Windows 7, and the same behaviour.
I went to update the firmware, and it completed the process. Also, in About Menu i see:
Model: BNRV10
App Version: 52.0.78 / 5.2.4.27
After this, i tried to connect it again in the PCs, and same behaviour, no USB drive.
I called B&N, and the operator told me to load the update.zip file and complete the update, but i tried to explain her if i'm not seeing any USB drive, it will be very difficult.
After researching some internet, i discovered if i press in the Nook icon in the About Menu, i can enter in a kind of System Settings Menu, and i checked in the Android Development Settings, the USB Debugging option is enabled.
But the question is... I don't want to root it, i just want the Nook to be seen by Windows...
Any suggestion, please?
Thanks!
Just using the "USB Debugging" is not the same as rooting.
You're not necessarily modifying any of the system.
In fact, I would recommend against using the "USB drive" style interface.
You would need to install ADB on your desktop.
Then you could just:
Code:
C:\>adb push update.zip /sdcard
Renate NST said:
You would need to install ADB on your desktop.
Then you could just:
Code:
C:\>adb push update.zip /sdcard
Click to expand...
Click to collapse
Thanks a lot! I will try that! Thanks!