Somehow I managed to get my PC to only recognize ROMaster ADB drivers only; but it doesn't work properly with ADB commands on my computer. I would like to revert it back to only detecting "normal" adb devices.
I believe I had install ROMaster Setup previously for data recovery purposes but have it uninstalled since. Can someone guide me in the proper direction ?
I have tried to reinstall ROMaster Setup and uninstall it. Run Ccleaner and clean up the registry, uninstall and reinstall Google SDK (USB Drivers).
I have tried to manually select driver to install but only two ROMaster selection appears.
Using Windows XP.
Thank you in advance.
What phone?
I have tried this with my Nexus 4 and several other Samsung devices.
Weird. And you can't manually load the driver in the Device Manager? Like so:
http://www.teamandroid.com/2012/07/30/how-to-set-up-adb-fastboot-with-android-sdk/3/
I just downloaded the application to see where they store the drivers and it should be located here:
C:\Program Files (x86)\DriverToolkit
So, plug in the phone, let it load those drivers, then go to Device Manager and uninstall it from there, then go and delete that folder and reboot, then try again.
Related
Hello,
Been trying to get droid explorer and adb to reconize my tilt2. Here is run down of what i have done.
on an up to date windows xp box
installed latest pdanet for android
installed latest droid explorer
connected my tilt2, it installed the adb driver but wont install the 2 cdc asm drivers
run droid explorer and it doesn't reconize the phone. i have the phone in debug mode and notification does come up.
on the android side i am running
frx 5
wistilt2 test kernel
highlandsun ril driver
btw, tried to run the busybox installer and it says it cant gain root access.. i thought all these builds have it by default or am i missing a step or two. I have superuser installed.
portreeve
All you need is the XDA device to install. The other two, CDC etc are not needed.
Is the adb service running? See if adb.exe is in task manager. You only need pda.net for the drivers, the software will mess with adb itself. So make sure their software is not running.
What do you mean busybox installer? For Titanium Backup or...?
You don't need SuperUser, that is an app that is more for security - if something asks for SU, it'll let you allow it thru the app. Yes, all our HaRET builds are rooted.
portreeve said:
Hello,
Been trying to get droid explorer and adb to reconize my tilt2. Here is run down of what i have done.
on an up to date windows xp box
installed latest pdanet for android
installed latest droid explorer
connected my tilt2, it installed the adb driver but wont install the 2 cdc asm drivers
run droid explorer and it doesn't reconize the phone. i have the phone in debug mode and notification does come up.
on the android side i am running
frx 5
wistilt2 test kernel
highlandsun ril driver
btw, tried to run the busybox installer and it says it cant gain root access.. i thought all these builds have it by default or am i missing a step or two. I have superuser installed.
portreeve
Click to expand...
Click to collapse
I didn't have a problem, My drivers installed automatically for me, but I'm using Win7.
You don't have to have pdanet or superuser for DroidExplorer to work.
Goto your device manager and see what device is listed under ADB interface. My Rhod300 shows up as a HTC DREAM.
arrrghhh said:
All you need is the XDA device to install. The other two, CDC etc are not needed.
Is the adb service running? See if adb.exe is in task manager. You only need pda.net for the drivers, the software will mess with adb itself. So make sure their software is not running.
What do you mean busybox installer? For Titanium Backup or...?
You don't need SuperUser, that is an app that is more for security - if something asks for SU, it'll let you allow it thru the app. Yes, all our HaRET builds are rooted.
Click to expand...
Click to collapse
Sorry arrrghhh, I had the window sitting open, and thought I had hit submit... lol
i was able to install on a windows 7 box and it picked up the drivers but when opening up droid explorer it still shows no devices found. any other advice?
portreeve said:
i was able to install on a windows 7 box and it picked up the drivers but when opening up droid explorer it still shows no devices found. any other advice?
Click to expand...
Click to collapse
Did you try mine? Remove pda.net, once you have the drivers no software is required from them.
Plus, you might also try the good ole reboot, and ensure that adb.exe is running in the task list.
All things I suggested previously...
yes, i've done the suggestion. It shows its connected. Under device manager there is an android phone, under that there is android adb interface but nothing under that. I don't know what else to do. Is there something i am missing on the android side?
and adb is running in taskmanager.
portreeve said:
and adb is running in taskmanager.
Click to expand...
Click to collapse
portreeve said:
yes, i've done the suggestion. It shows its connected. Under device manager there is an android phone, under that there is android adb interface but nothing under that. I don't know what else to do. Is there something i am missing on the android side?
Click to expand...
Click to collapse
and you've rebooted?
I'm out of ideas, I've installed adb on tons of computers, win7 xp etc and all work flawlessly. It is a pretty advanced debugging tool, it's not very easy to install or use...
yes and i have rebooted twice now. still the same thing.
Boot android on phone.
Plug phone in.
Run Windows update.
Check device manager to make sure everything has drivers installed.
Run DroidExplorer
phone will show up as 00000000 in DroidExplorer
Reinstall DroidExplorer if problem persists.
Oh and there should be a device or driver in device manager called XDA, if memory serves me correctly.
Had the same problem about a month ago... downloaded PdaNet from the Marketplace here and it established the connection so I could use the USB to my phone. I didn't have to run it or buy it though .. just install it.
I have a Gtablet in which I was able to install and use NVFlash. I used the recommended driver for this process and it works perfectly. Now here is my new problem / challenge. I am trying to learn SDK ADB. As parts of the procedures, I have to install the Google USB driver to have the device recognized as an android device (Or something in that line as per the instructions). Here are the problems:
1.) My Gtab show on the device manager as a storage device and a portable device with the same drive letter as the storage device
2.) I'vr tried removing the NVflash USB driver, but it does not uninstall. Every time I re-connect the device it re-install the driver and goes back to problem 1.)
3.) I used (USBdeview) to try and remove the device and the driver from my win 7 x64 but it just don't uninstall or stop the decive or anything.
4.) I tried updating the driver of the gtab (As in problem 1.)) and it says that the current driver is the most appropriate for the device. And goes back to problem 1.)
In other words..... I am tied up with the NVFlash driver (Tegra I beleive, which is the one described on the NVFlash How to). I am trying to SDK ADB, but it will not allow me to connect cause the Gtab is not recognized as an Android device, but as a storage device or nvidia tegra when in APX mode (I beleive it called).
which step am I missing or doing wrong?
Thanks in advance
Please excuse my lack of technical lingo.....
Did you read the sticky message: adb for your gtab (windows) in the general section?
I had the same problem, except I'm using windows XP. The storage device is not the driver to uninstall. Device manager never showed me any other drivers relating to the gTab.
Using USBDeview I was able to see a different driver (can remember was it was called exactly), uninstalled then reinstalled using the usb driver I downloaded from google and everything was fine.
Hello;
This was my first time installing a Rom. I was fed up with my phone responding slowly and in time jams.
1-The first thing I did was install cwm recovery v6.0.2.7.
2-Then use the S3 tool kit available in xda to make a backup of all except system apps and internal storage data and it was stored in a .bak file. So that games and other apps keep their info as it is a hassle to start from the beginning.
3-Installed CM 10.1 nightly used in the instructions provided here.
All is okay up to here.
4-Tried to restore apps and app data through S3 tool kit but it won't display the data in the phone. I did enable the usb debugging on the cm10.1 (by pressing 7 times on the build name to enable the developers option and enabling usb debugging). I had the same problem when trying to do the backup in step 2, but it connected through the adb mode. This problem is that when ever I connect a device via usb windows installs the driver so every time I connect my phone windows installs the drivers.
5- When step 4 did not work I tried to restore using Holo Backup but no use no able to connect through to adb mode.
I can access the phone storage but I believe the appropriate drivers are not running when using the restore programs even though they are installed.
So the questions are:
1- Is there a way to fix the connection to be able to use S3 unified tool kit or if any one has dealt with the same problem?
2- Is there a way to restore the .bak file via cwm recovery?
3-For future use; An app or program that can be stored in the phone to avoid the use of a PC. The app or program would back-up contacts, sms text, apps and app data into the virtual sd or cloud to avoid deletion when "wipe data/ factory reset" after installing a rom.
I look forward to your replies.
Thank you.
What drivers do you have? Have you tried Universal Naked Driver? That's the only way I could get adb to work on mine when running CyanogenMod
wststreet said:
What drivers do you have? Have you tried Universal Naked Driver? That's the only way I could get adb to work on mine when running CyanogenMod
Click to expand...
Click to collapse
The image below shows the Drivers I currently have.
I used to have a lot more but a majority of them were copies of the same driver.
I had 2 other Samsung drivers but I also deleted them. According to an article that stated a fix to the problem is to uninstall all usb drivers except mouse and keyboard and reinstall the usb drivers of the device desired, but no success.
sub-80 said:
The image below shows the Drivers I currently have.
I used to have a lot more but a majority of them were copies of the same driver.
I had 2 other Samsung drivers but I also deleted them. According to an article that stated a fix to the problem is to uninstall all usb drivers except mouse and keyboard and reinstall the usb drivers of the device desired, but no success.
Click to expand...
Click to collapse
I tried to install the universal naked driver but no success. I followed the instruction went into the device manager and under the samsung android phone was the samsung android ADB interface which I uninstalled and checked the delete part. The pc requested to restart which I forgot to turn off the the internet which resulted in the driver being installed once it restarted. Tried a second and third time with no internet but when I uninstall and check the delete marker the pc does not ask to reboot. And if I try to update the driver with VND it notifies me that it is up to date.
Any solutions?
sub-80 said:
I tried to install the universal naked driver but no success. I followed the instruction went into the device manager and under the samsung android phone was the samsung android ADB interface which I uninstalled and checked the delete part. The pc requested to restart which I forgot to turn off the the internet which resulted in the driver being installed once it restarted. Tried a second and third time with no internet but when I uninstall and check the delete marker the pc does not ask to reboot. And if I try to update the driver with VND it notifies me that it is up to date.
Any solutions?
Click to expand...
Click to collapse
Tried ADB wifi but no success the pc says that there are no adb devices.
Also tried PDANet+ to install the drivers but software does not see the s3.
s there a way to restore the .bak file via cwm recovery
tried changing the file name by removing the .bak
jje
JJEgan said:
s there a way to restore the .bak file via cwm recovery
tried changing the file name by removing the .bak
jje
Click to expand...
Click to collapse
removed the .bak extension and placed it in the download folder of my virtual sd folder and pressed restore on cwm but nothing happened.
Could be because the backup is password protected?
Also tried to restore the file via titanium backup through the extract simple adb with and without the extension but only says analyzing file and remains that way for hours.
Hi
Wondering how to set my new z5 in ptp mode, so i can use helium to transfer my userdata from games to new phone.
Im looking for that answer too, just bought z5c.
Hi, I just did a Helium Backup yesterday, you don't actually need the ptp connection. Go into the device manager and right click on "ADB device" (it has a yellow triangle icon on it) and reinstall driver from your pc, choosing "ADB interface". Then disconnect the device from the computer, close helium on the computer and reopen, then reconnect. The connection will establish. That was my experience, YMMV but fiddling a bit can help. I hope you succeed
The steps I did to enable PTP mode so I can use adb:
- plug the phone into the PC USD and install normal drivers
- install Helium backup app on the phone. Run Enable PTP from Helium. It will not work, but will pop an ADB unknown driver in your computers Device Manager
- Download Sony ADB drivers: http://developer.sonymobile.com/downloads/drivers/xperia-z5-compact-e5803-and-e5823-driver/ and then unzip
- in device manager, right click on ADB Device, Select update driver, select Search Location and point to the drivers unzipped in the step above. Make sure you include Search Subfolders. The driver will be detected and you can install it.
- In helium app, enable PTP
After this I could use ADB!
After doing this, my phone rebooted and then could not be seen by Windows. So there are no recognizable drivers for windows? Sony PC Companion re-install did not reinstate the drivers.
Anyone know how to fix?
Hi
Just got my A3. I'm unable to connect with adb to restore my backup. I enabled Dev options and USB debugging and when plugged into USB I get P notification icon and USB debugging connected message in notification. However
adb devices
shows nothing is connected. I notice there is no pop up asking if I want to authorize this computer which is iirc normally what happens.
adb can see my blu g6 phone so that's working. When I connect the A3 as a storage device, with no USB debugging, I can transfer files ok, so USB is working. I have a fresh Android studio install which should have the right sdk. I tried
adb connect <ipaddress>
and got "no connection could be made because target machine actively refused it" I did not refuse, because nothing popped up.
Have rebooted both phone and PC (windows 7)
Any idea what's going on? Thanks
Sent from my G6 using Tapatalk
Follow up: okay I figured out I need to install adb driver because A3 shows up in yellow in device manager. But I can't find a driver that works. I googled xiaomi A3 adb driver and downloaded like five of them from different sites and none worked. When I point windows to the folder where I extracted the driver it says could not find driver for your device.
I'm going nuts. Can someone point to a working driver for Windows 7?
Sent from my G6 using Tapatalk
These always worked for me. If they are not automatically installed for the device, follow the instructions in the video.
https://forum.xda-developers.com/showthread.php?t=2588979
Thanks. I figured out where I went wrong.
Instead of using the "browser file on my computer" and point it to where the driver is, I have to choose "let me select from a list" then "all devices", then select the Android composite adb driver. At least this works on Windows 7.
---
So I restored my back up, I got the pop up to confirm restore my data, and it seemed to run through the restore and took a while, but nothing changed. None of my app data was restored. All apps are still in newly installed state.
It did restore the data in SD storage, so my download folder etc got restored, which I could've done just copying to and from my PC.
What I really want is all the app data restored so I don't have to log back into all the different services and do all the settings again.
I did the back up with
adb backup -all -apk -shared -f allbackup.ab
Shouldn't that have worked?
Sent from my G6 using Tapatalk
From what I remember adb restore does not install *.apk back. It only writes back system and data files. So if you wanna all the app data restored - reinstall all apps manually before and then do adb restore.
On Windows you can sort of semi-automate that process in command prompt:
for %f in (C:\<your pak folder location>\*.apk) do adb install "%f"
Make sure though apk don't have spaces in their names or adb will complain.
qwertysmerty said:
From what I remember adb restore does not install *.apk back. It only writes back system and data files. So if you wanna all the app data restored - reinstall all apps manually before and then do adb restore.
On Windows you can sort of semi-automate that process in command prompt:
for %f in (C:\<your pak folder location>\*.apk) do adb install "%f"
Make sure though apk don't have spaces in their names or adb will complain.
Click to expand...
Click to collapse
I looked at adb logcat and there were a bunch of errors. Looks like it did try to restore app data but failed. Google back up already installed the apks back (except for the ones I side loaded) so that wasn't the problem. It's the app data (settings, etc) that I was hoping to get back
Oh well I just spent an hour setting my apps up again. I hear Google has already deprecated adb backup. Android needs a good non root desktop back up solution, not the cloud backup where you're at the mercy of Google and the individual apps to decide what get backed up.