After updating my Nexus 7 to 4.2.2 I could not connect to PC via USB using MyPhoneExplorer. WiFi connect was still okay.
I just found the answer at
http://www.fjsoft.at/forum/viewtopic.php?t=19015
Basically, the answer is:
"In order to make MyPhoneExplorer compatible with Android 4.2.2 over USB you need the latest version of ADB (1.0.31 or higher). See http://forum.xda-developers.com/showthread.php?t=2144709 for details, there you'll also find a link to the latest ADB version. If you prefer you can of course download the latest Android SDK from Google's servers). Older versions of ADB do not trigger the confirmation request introduced with Android 4.2.2, therefore MyPhoneExplorer can't establish an ADB connection over USB.
Simply copy the three files adb.exe, AdbWinApi.dll und AdbWinUsbApi.dll to MyPhoneExplerer's DLL folder (usually "C:\Program Files\MyPhoneExplorer\DLL" (backup the existing files prior to copying the new ones)."
Click to expand...
Click to collapse
was just searching for a solution to this problem on my nexus 4. Thanks a ton, it's working great now
thanks a lot. you saved my day.
If you re download MPE although it is the same software version they have now included the latest android ADB in the package
Sent from my GT-I9505
Related
Hello XDA Community.
I'm attempting to install the new RC of CyanogenMod-6 for the Hero CDMA. I'm currently running the stock 2.1 version of Android. I've been following the guides that were referred to in the thread (I tried posting the urls but new users can't do so to prevent spam).
I've successfully rooted my phone and now I'm trying to do a Nandroid backup. I'm running Windows 7 32-bit and have hit a road block with ADB not recognizing my device. I followed the guide put together by Nephron to install the Android SDK. I've spent several hours going through threads and doing google searches looking for the solution. I have debugging turned on and I don't mount my SD drive when I plug the USB cord in. I've used USBDeview as some have suggested to delete current HTC drivers and then reinstall - no luck.
Here is a screen shot of what happens when I plug in my Hero:
See attached - "failedinstall.jpg"
Then I'll go to device manager to manually install the driver (it never allows me to manually select upon connection for some reason):
See attached "devicemgr.png"
And then this is the message I get when I point it to the "right" folder with the drivers:
See attached - "unabletoinstall.png"
So, on the Android SDK site I noticed this message:
"The USB driver for Windows provides support for the following Android-powered devices:
T-Mobile G1* / ADP1
T-Mobile myTouch 3G* / Google Ion
Verizon Droid*
Nexus One
* Or similar hardware on other carriers
Any additional devices will require Windows drivers provided by the hardware manufacturer.
^So is all of this HTC's fault? I've downloaded a couple of different .zip folders from different threads claiming that these drivers would work. But none of them have yet to do the trick for me.
I'm new at this so I have a few other questions as well:
Most guides I've read about how to do a Nandroid backup always recommend flashing a ROM b/f doing a backup. But I want to backup my current stock rom and settings before I flash. Wouldn't I want to create a recovery image before installing any other ROMs? Perhaps I'm misunderstanding some requirements?
Referring again to the thread on the CyanogenMod RC, can someone help me understand step #3? How do I know if it is necessary to update my radio? What implications does this have? I tried looking for info about this on the wiki and I couldn't find anything comprehensive enough to answer my question.
I'd appreciate any guidance!
Before you modify anything you will want to boot into recovery, assuming you flashed one, by holding down Home and turning the phone phone back on(power button). But since you don't have adb working then you probably haven't. You can still do this using terminal on your phone.
Download terminal emulator from market and then download a revoery image (AmonRa 1.6.2 or Darch's 1.7xx) and then mount your sdcard to the computer and transfer the recovery to the root of the sdcard. Open up terminal emulator and type in
Code:
su
cd /sdcard
flash_image recovery recovery-RA-heroc-v1.6.2.img(type the exact file name of the recovery you are using)
reboot recovery
If you had factory 2.1 on your phone then you have the latest radio. The radio can be flashed just like any ROM, but make sure that the radio is not for GSM phones as this will destroy your phone.
Instructions from Android Developers and ADB, Fastboot, and Nandroid for Noob
Download the latest Android SDK.
Unzip to C:\AndroidSDK
Right-click on (My) Computer, and select Properties
Go to Advanced settings
XP: Click the Advanced tab
Vista/7: Click Advanced system settings on the left
Click the Environment Variables button
double-click on Path (under System Variables)
Add the full path to the tools/ directory:
C:\AndroidSDK\tools\
(make sure a semicolon ( separates this new path from all the others)
Latest windows sdk version appears to need: "C:\AndroidSDK\android-sdk-windows\tools", install location may change with further updates..
Run C:\AndroidSDK\SDK Setup.exe
If you get an error about not having Java SDK installed but you do, add the path to 'bin' within your Java installation location to the Path environmental variable as described above before the sdk entry you just made. (eg add "C:\Program Files\Java\jdk1.6.0_20\bin;") This is likely to only be necessary where the 64 bit Java SDK is installed (obviously) on a 64 bit machine.
If it gives you an error about http go to settings and click on "Force http//....."
Unselect all options except for the USB driver
If you can't get the setup to work, download the USB-DRIVERS folder - HERE (Windows XP/Vista/Windows 7)
On your phone, click Settings > Applications > Development and make sure USB Debugging is on.
Plug your phone into your computer via USB cable (it needs to be on). It should say installing drivers if using Windows.
After it installs the drivers, goto the Start menu and type cmd into the search bar (Vista or higher) or click Run then type in cmd (XP) to open the command prompt.
Type the following into the command prompt window:
adb devices
You should see a serial number pop up, it’s the serial number of your phone. This means you are all set. If you do NOT see a serial number, then we need to reinstall the drivers.
Download USBDeview
While the phone is still plugged in, open USBDeview and sort by manufacturer. Find all the HTC/Android drivers and uninstall them all. (Windows Vista requires program to be run as an administrator, otherwise files won't uninstall.)
Once all have been uninstalled, unplug the phone from the USB cable and plug it back in.
The correct drivers should reinstall automatically (check the drivers as they are installing, one should say ADB Device driver).
To check, go to Devices in your Start menu then click on the “Android Phone”. Click on the Hardware tab, and check the list of drivers for ADB Interface under Type.
Done! Now you can use ADB to alter your phone from your computer.
If all else fails try installing HTC Sync software-- http://member.america.htc.com/download/Driver/HTC Hero (Sprint)/HTC_Sync_2.0.40.exe and then removing the drivers for it and then trying to install the android sdk drivers
Or you can dual boot with Linux and all you will need to do is download and unzip android sdk and edit 2 files and everything will work.
WOW>>>>>no that is way to confusing. the best thing to do is install vmware workstation. Then do a virtual WINDOWS XP MODE. from there you will be able to install the drivers and such in order to get the phone to be seen.
the version of htc sync i used for all my computers including win 7 was 2.0.33
if you want it then just pm me and I will get it to you
they don't offer it for a download anymore
this version corrected all my driver issues
I hope this post can be of use to someone. My workplace is running Lotus Notes (sigh) and IBM recently released an update to their Traveler server which supports Activesync sychronizaton of mail, contacts, calendar and directory on Android, Iphone, etc.
The only problem is AT&T blocks Sideloading. Yes a simple root can fix the issue but that is not a true solution for every Captivate for our users. I figured out a relatively easy method of getting around this limitation.
First you need the following:
Rooted Captivate (to obtain the .apk files necessary) Only needed once, I would upload the necessary files but IBM won't like that very much.
Computer with Captivate drivers and Android SDK
The Lotus Traveler setup requires two installs which makes the process more tricky than simply doing an adb install lotusinstaller.apk, so we need a few more steps.
1. On your PC download the Lotusinstaller.apk file from your traveler server and copy it to you sdk\tools folder.
2. Plug your rooted Captivate phone into you computer with debugging mode on and use adb to issue the following command "adb install lotusinstaller.apk"
3. Open the installer application on your phone and enter the required server and authentication information for your system and click next. (this will create the server setting on the phone and download the lotustraveler.apk file to your rooted phone.) I can't remember the exact location so simply do an adb shell then "su" to gain super user rights and then do a find -name LotusTraveler.apk (or *.apk and find the lotustraveler.apk)
4. copy this file to your computer. One easy way would be to adb pull LotusTraveler.apk c:\location of sdk\tools\
Now that you have both the lotusinstaller.apk and lotustraveler.apk you will not need the rooted captivate for future phone setups.
5. Now to setup a stock Captivate. Enable usb debugging
6. adb install lotusinstaller.apk
7. launch the installer and enter the appropriate settings on the phone and click next. It will attempt to download the lotustraveler.apk and then give you an error about not being able to install applications that aren't from the market. Ignore that and close the installer.
8. now issues abd install lotustraveler.apk on your pc
You're done. The installer setup the initial server settings and the lotustraveler did the rest.
To setup more phones begin from step 5 from now on
***Disclaimer***
I wrote this up simply from memory so I'm sorry if this is not 100% accurate with the commands etc.
you could user the The Android Central Sideload Wonder Machine to put .apk's on the device and not need to root.
Just a thought.
jetski said:
you could user the The Android Central Sideload Wonder Machine to put .apk's on the device and not need to root.
Just a thought.
Click to expand...
Click to collapse
thats exactly my first thought.
jetski said:
you could user the The Android Central Sideload Wonder Machine to put .apk's on the device and not need to root.
Just a thought.
Click to expand...
Click to collapse
Or just side load through ADB in a command window in windows. "adb install filename.apk" done.
Sent from my SGH-I897
Clienterror said:
Or just side load through ADB in a command window in windows. "adb install filename.apk" done.
Sent from my SGH-I897
Click to expand...
Click to collapse
I'll try the wonder machine first. thanks for that tip.
Your suggestion won't work as stated in my walkthrough. The initial apk downloads another apk to your phone somewhere in the system directory. Once you have both apk files it's a simple "adb install lotusinstaller.apk" then "adb install Lotustraveler.apk"
wonder machine causes the issue of not being able to install the second apk file as stated in my last post. It can replace adb install after you have both apk files on your computer.
I need to get the second file to install it on my non-rooted phone.
Does anyone know the location of the download on the phone so it can be pulled via adb?
Ziuck said:
I need to get the second file to install it on my non-rooted phone.
Does anyone know the location of the download on the phone so it can be pulled via adb?
Click to expand...
Click to collapse
just do
find -name LotusTraveler.apk
it will show you where the apk is located
Im learning android dev n java. When i had official v20a, it was shown in eclipse online when i ran my apps for testing.
But since i installed cm 10.1 (april 29 updated), it shows my phone but offline n i cant test my apps
Sometimes it show up as online but most of the times it show my phone offline. When it is offline i tried following things but it does not show online even after them...
Tried unplug n plug my phone again
Tried restarting my phone
Tried restarting eclipse
But no hope. :banghead:
Can anyone solve this prob? I need it very much to test my apps.
Thanks in advance...
Sent from my LG-P880 using xda premium
Hi , try this:
1)Run eclipse : windows -> sdk manager . Close eclipse (not the sdk manager) and upgrade your sdk to 4.2.2 and perform all the updates that the sdk manager find.
2)Run eclipse : it will report some problem and advice you to check for updates : do it and upgrade. If eclipse doesn't report any error you can perform the check via help->check for updates.
3)Restart eclipse and you are ok
Zeph90 said:
Hi , try this:
1)Run eclipse : windows -> sdk manager . Close eclipse (not the sdk manager) and upgrade your sdk to 4.2.2 and perform all the updates that the sdk manager find.
2)Run eclipse : it will report some problem and advice you to check for updates : do it and upgrade. If eclipse doesn't report any error you can perform the check via help->check for updates.
3)Restart eclipse and you are ok
Click to expand...
Click to collapse
i already have 4.2.2 installed fully. and i said my phone sometimes is detected as online, but most of times it is offline
one more thing to mention.
my phone is also shown offline in adb, when i put this command in adb
adb devices [ENTER]
********** offline
it shows my phone's serial and then says it's offline, wtf?
the problem is in adb. In android 4.2.2 there is a debug usb protection .If you use the sdk 4.2.2 when you connect for the first time your device in usb debug, a popup on your screen device will ask you if that computer is trusted.
A lot of people have reported issues with this.. i've resolved easily with the upgrade of the sdk.
However there is a topic somewhere in xda with adb and fastboot drivers that work properly with 4.2.2 devices
this solved my problem.
i was studying this issue on many forums and blogs, and came to stack overflow. and found this answer.
go to your adb command prompt on pc and enter these commands one by one.
adb kill-server
set ADB_TRACE=all
adb nodaemon server
after that restart your pc,
Done!
now everytime i connect my phone with adb, it is online
Note: i don't know what these commands are doing, but it just solved my problem. the problem came out because of wrong path to sdk or something. and these commands do it magically lol, thats what i know.
Has anyone got MyPhoneExplorer to work with a Cyanogenmod 10.1 based ROM ?
I've only just got around to rooting my Incredible S, and haven't had chance to look into it much but it seems like you need to update the adb drivers that MyPhoneExplorer uses to make it incompatible?
Anyone had any luck with this?
invosoft said:
Has anyone got MyPhoneExplorer to work with a Cyanogenmod 10.1 based ROM ?
I've only just got around to rooting my Incredible S, and haven't had chance to look into it much but it seems like you need to update the adb drivers that MyPhoneExplorer uses to make it incompatible?
Anyone had any luck with this?
Click to expand...
Click to collapse
Hello.
I'm using CYM 10.1-20130526-UNOFFICIAL-i9300
Temasek RC2.6.1
Build Number cm_i9300-userdebug 4.2.2 JDQ39E.
MyPhoneExplorer latest release on Win7 x64 and Outlook 2010 and i can not synch it with phone.
Driver ver 2.9.103.812.
Will try with another Drivers.
Let me know if you found solution.
Carambolero said:
Hello.
I'm using CYM 10.1-20130526-UNOFFICIAL-i9300
Temasek RC2.6.1
Build Number cm_i9300-userdebug 4.2.2 JDQ39E.
MyPhoneExplorer latest release on Win7 x64 and Outlook 2010 and i can not synch it with phone.
Driver ver 2.9.103.812.
Will try with another Drivers.
Let me know if you found solution.
Click to expand...
Click to collapse
Yes, I did find a solution in the end but I've forgotten exactly what I did now, sorry! Try this though (taken from the MyPhoneexplorer forums) :
1. Download Google's latest Android SDK: 32-bit or 64-bit.
2. Unpack the SDK or - if you have Windows Vista, 7 or 8 - simply open the ZIP file.
3. Inside the SDK locate and open the folder sdk -> platform-tools.
4. Locate the files adb.exe, AdbWinApi.dll and AdbWinUsbApi.dll.
5. Open MyPhoneExplorer's DLL folder, which usually is C:\Program Files\MyPhoneExplorer\DLL (on 32-bit systems) or C:\Program Files (x86)\MyPhoneExplorer\DLL (on 64-bit systems).
6. Backup the files adb.exe, AdbWinApi.dll and AdbWinUsbApi.dll which reside in MyPhoneExplorer's DLL folder by copying them to a safe location on your hard disk.
7. Copy the files adb.exe, AdbWinApi.dll and AdbWinUsbApi.dll from the SDK folder to MyPhoneExplorer's DLL folder; these files will then replace the old files. Notice: Windows might ask you to enter the administrator password to perform this step.
8. Close all open folders and start MyPhoneExplorer.
9. Connect your Android phone or tablet to one of your computer's USB ports.
10. In MyPhoneExplorer choose File -> Connect.
11. On your Android smartphone or tablet confirm that your computer is allowed to establish a USB connection.
I am running the latest nightly of omnirom and I am developing and testing an app to be published to Google Play, I cannot test the app over adb however because I cannot get adb to connect. Upon connecting my device to my computer, the drivers fail to install.
USB Debugging is enabled
adb devices returns empty
adb over network disabled
media file transfer disabled
Version: 4.4.4-20140730-n801x-NIGHTLY
Kernel Versoin: 3.0.64-OMNI-gbd32646
Any help is greatly appreciated!
Have you installed the sammy drivers?
XxPixX said:
Have you installed the sammy drivers?
Click to expand...
Click to collapse
I have the official drivers for my tablet installed but it is still not recognized over ADB, I also installed the samsung usb drivers with no luck.
In general, most AOSP-derived firmwares use Google's drivers.
I'll check my N8013 this weekend, but I have had no ADB issues in the past. That said, I run Linux which is FAR less finicky than Windows is as far as ADB is concerned.