Database Users

[GUIDE] Getting ADB Setup; An Idiots' proof guide on getting ADB working for Rooting!

[GUIDE] Getting ADB Setup; An Idiots' proof guide on getting ADB working for Rooting! v1.2
Hey XDAers. Getting ADB setup and working is an essential part to rooting your Android device and helps layout the foundations to better understanding the language and using it in this environment. While not going into extreme detail, this is just a quick guide or overview on the first part of rooting; Getting ADB setup and working.
** Make sure your Transformer is not currently connected to your PC yet. We will be installing device drivers first (Step 7) and modify a setting on your tablet first before connecting to your PC (Step 8).
Step 1 :
Download and install the Android SDK.
You can download the SDK from the Google Developer's website. I have linked for you the download page and a direct link to the installer (Note: the direct link may change in the future with future versions, I will try stay on top of this and change the link)
http://developer.android.com/sdk/index.html
http://dl.google.com/android/installer_r10-windows.exe
*New Version : http://dl.google.com/android/installer_r11-windows.exe
You may or may not be prompted to install the latest version of Java if you haven't done so already, install it, and you may or may not have to reboot your computer.
Step 2 :
Once the install is complete, navigate to the directory in which you installed the SDK and launch the SDK Manager executable. It may or may not ask you to download and install the Java JDK, do so if you haven't already.
*When I run the android SDK installer it tells me I don't have the java JDK installed, even though I've installed it already*
Answer :
It says that but disregard it. If you've installed it, it should be fine. When it gets to the part that says its not installed and won't let you go any further simply click back then click forward again and it should allow you to go ahead.
Thanks Crimton!
Click to expand...
Click to collapse
Step 3:
Once the SDK Manager is launched, it will look something similar to the window below.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
You will want to do something along the lines of update all or install all. This way it will download all the latest packages and you willhave the latest SDK tools installed.
Once that is complete, you can exit out of the SDK Manager.
Step 4:
Open up a command prompt window. You can do so by holding the WinKey+R, a run window will appear, type CMD, and hit enter.
Step 6:
Within the Command Prompt window, navigate to the Android SDK folder\platform tools folder (Command Prompt command : CD foldername\foldername\foldername\etc)
Step 7:
Now install the ASUS Sync software if you haven't loaded it previously. http://www.asus.com/Eee/Eee_Pad/Eee_Pad_Transformer_TF101/#download. Just select your operating system, hit download, then install.
Why are we installing the ASUS Sync software you ask?
Well mainly because it has USB drivers that will help your PC operating system detect and display your ASUS Transformer. Without the drivers, ADB wouldn't be able to detect your device most likely!
*For other android devices, you will need similar software from that manufacture. HTC Sync for HTC devices as an example.
Click to expand...
Click to collapse
Step 8:
Enable USB Debugging on your android device / Transformer.
Go to Transformer Tablet, go to settings -> applications->Development, turn on USB Debugging.
Step 9:
Connect the USB cable from your android device / Transformer to the PC. It will begin to automatically install drivers, let it do so and complete. May ask to reboot machine.
Step 10:
Once that is done, go back to the command prompt. Run ‘ADB Devices’
You should see something like above, indicating it detected the transformer, if not, run the following ‘adb kill-server’, ‘adb start-server’, ‘adb devices’
Ok, if you are seeing something like the screenshot above then success, you have successfully gotten ADB up and working! Congratulations! That wasn't too hard now was it? You can now follow one of the root guides and follow the directions and you should be on your way to a fully rooted device. Cheers!
-------
Troubleshooting:
In the event you complete the steps above but your computer either will not recogonize the Transformer in Windows as a device, or ADB will not see it please try the following to see if this will fix it for you. You only need to try these if the above steps aren't working for you, but most people, they work fine.
Try uninstalling the ASUS Sync software, and reloading it.
After reinstalling the ASUS Sync software, restart your PC
Make sure your Transformer tablet is in USB Debugging Mode, and connect the USB Cable
You should see a Win7 prompt that says installing drivers. If you do not, try connecting to a different USB port, I've had to do this once on an older PC of mine.
In ADB be sure to kill server and start server and then see if you can see the device
Now, if you are still not seeing it installing drivers, or its not showing up as a device on My Computer, or ADB is still not seeing it, try download and install these ASUS Windows USB Drivers, these may do the trick : http://hotfile.com/dl/118226479/2f89b99/ASUS_Android_USB_drivers_for_Windows.zip.html
-------
Notes:
-If you want another guide on something else, let me know, and I will see what I can do.
-Yes this has been posted a million times I know, but I thought this might help out those few people that don't feel like looking around. Plus, it has nice color illustrations. Who doesn't like picture books?
-------
Credits
Crimton for Java JDK workaround when not showing as installed
sourworm for new link to SDK installer

Nice job. Added to ultimate thread. Probably a good idea to attach the pics in your post to the XDA forums, so they are saved in future, as a lot that are hosted on other sites die after too many people view them.

stuntdouble said:
Nice job. Added to ultimate thread. Probably a good idea to attach the pics in your post to the XDA forums, so they are saved in future, as a lot that are hosted on other sites die after too many people view them.
Click to expand...
Click to collapse
Will do when I get home, thanks for the tip.

Ill add this to the FAQ

One of these days I hope to get ADB set up in Ubuntu 10.10.....
HTC Vision; Rooted, Booted and Scooted.

I'm not a complete noob, but I'm stuck on step 1!!
When I run the android SDK installer it tells me I don't have the java JDK installed, even though I've installed it already....
http://download.oracle.com/auth/otn-pub/java/jdk/6u25-b06/jdk-6u25-windows-i586.exe
OH! It's working now.... Never mind.

RedMist said:
I'm not a complete noob, but I'm stuck on step 1!!
When I run the android SDK installer it tells me I don't have the java JDK installed, even though I've installed it already....
http://download.oracle.com/auth/otn-pub/java/jdk/6u25-b06/jdk-6u25-windows-i586.exe
OH! It's working now.... Never mind.
Click to expand...
Click to collapse
Glad you got it resolved, I will edit the guide and make note about java installation.

Daughain said:
One of these days I hope to get ADB set up in Ubuntu 10.10.....
HTC Vision; Rooted, Booted and Scooted.
Click to expand...
Click to collapse
[GUIDE] Lazyman's installation guide to ADB on Ubuntu 10.10
http://forum.xda-developers.com/showthread.php?p=11823740#post11823740

neilkarunatilaka said:
[GUIDE] Lazyman's installation guide to ADB on Ubuntu 10.10
http://forum.xda-developers.com/showthread.php?p=11823740#post11823740
Click to expand...
Click to collapse
at a glance, even that thread makes it look like more trouble than it is. but good info

RedMist said:
I'm not a complete noob, but I'm stuck on step 1!!
When I run the android SDK installer it tells me I don't have the java JDK installed, even though I've installed it already....
http://download.oracle.com/auth/otn-pub/java/jdk/6u25-b06/jdk-6u25-windows-i586.exe
OH! It's working now.... Never mind.
Click to expand...
Click to collapse
How did you fix it? I've been struggling with this same issue for at least a month now.

n25philly said:
How did you fix it? I've been struggling with this same issue for at least a month now.
Click to expand...
Click to collapse
It says that but disregard it. If you've installed it, it should be fine. When it gets to the part that says its not installed and won't let you go any further simply click back then click forward again and it should allow you to go ahead. At least that's how I remember it.
Sent from my ADR6400L using Tapatalk

Crimton said:
It says that but disregard it. If you've installed it, it should be fine. When it gets to the part that says its not installed and won't let you go any further simply click back then click forward again and it should allow you to go ahead. At least that's how I remember it.
Sent from my ADR6400L using Tapatalk
Click to expand...
Click to collapse
lol, simple solutions are good. Just wish it didn't take me a month to find that one out.

Very simple and easy to follow. Thanks OP.

I download Asus sync for window 7 64bits but when I run asus, it doesn't detect my device and of course ADB devices didn't show up any device. Something I missed? Please?

randy_c said:
I download Asus sync for window 7 64bits but when I run asus, it doesn't detect my device and of course ADB devices didn't show up any device. Something I missed? Please?
Click to expand...
Click to collapse
Sorry to hear that. Off the top of my head, I'm not sure what could be causing this. But here are a couple things you can try. And please let us know what happens next.
Try uninstalling the ASUS Sync software, and reloading it.
After reinstalling the ASUS Sync software, restart your PC
Make sure your Transformer tablet is in USB Debugging Mode, and connect the USB Cable
You should see a Win7 prompt that says installing drivers. If you do not, try connecting to a different USB port, I've had to do this once on an older PC of mine.
In ADB be sure to kill server and start server and then see if you can see the device
Now, if you are still not seeing it installing drivers, or its not showing up as a device on My Computer, or ADB is still not seeing it, try download and install these ASUS Windows USB Drivers, these may do the trick : http://hotfile.com/dl/118226479/2f89b99/ASUS_Android_USB_drivers_for_Windows.zip.html

I have a few questions. This is the first real time I'm using ADB.
So I have tried everything you listed above and I can get it to sync on occasion, but I cannot get it to read my device in the command prompt. I type this "D:\android-sdk-windows\tools>adb devices" and it says "The device is not ready." Why is it not finding it even with it syncing at that moment?
Also, do you type "D:\android-sdk-windows\tools>" every time you run something? If so, is there a way to get that to show up beforehand every time instead of having to type it? Thanks again for your help!

andrew53517 said:
I have a few questions. This is the first real time I'm using ADB.
So I have tried everything you listed above and I can get it to sync on occasion, but I cannot get it to read my device in the command prompt. I type this "D:\android-sdk-windows\tools>adb devices" and it says "The device is not ready." Why is it not finding it even with it syncing at that moment?
Also, do you type "D:\android-sdk-windows\tools>" every time you run something? If so, is there a way to get that to show up beforehand every time instead of having to type it? Thanks again for your help!
Click to expand...
Click to collapse
1) First thing you can try is the famous 'adb kill-server' 'adb start-server' commands and see if that will get it going. Also 'adb usb' will restart the daemon listening on USB, so maybe that could make it usable. If not, make sure the ASUS Sync app is not running, and perhaps see if there are any running services/apps on your Transformer that could be causing the conflict. Download System Panel Lite from Market and tell it to end all apps, then try again (make sure USB Debugging is enabled)
If you tried all of that, and still no dice, make sure no USB Drives or Memory Cards are connected, then connect the Transformer (w/ USB Debugging), go to Device Manager, uninstall the USB drivers for the device if you can find it or it may show up as a USB Mass Storage device under USB Controllers, then disconnect the Transformer, reconnect the Transformer, it should reinstall the drivers for the Transformer since you already have ASUS Sync installed, then retry.
If again still no dice, try using the ASUS USB Windows Drivers and going to Device Manager and updating the drivers with those you downloaded (download the correct ones for your particular operating system, and then try again.
Now, if this still doesn't work, let me know, and I'll try think of something else. Maybe someone else has had this issue and come up with a workaround or solution, but I'm drawing a blank currently. I'll sleep on it and see if I can think of anything else
2) You don't have to type that up all the time. What you can do is navigate the platform tools folder (or whatever folder has the adb files), then if on Win 7, hold shift and right click on the folder (Platform Tools for example), and you will see an Open Command Prompt here. Hit that, and it will already be in that root folder. But in general, in a command prompt window, once you have navigate to the specified folder, you will be in that folder, so you will only need to type ADB 'command' if that makes sense.
[/LIST]

I think I might have figured it out, if this is it. So I downloaded the drivers but I don't think they ever installed. Don't laugh lol, how do you install them? There isn't a .exe file or anything to install them.. I just see files and notes. Do I put it somewhere or what do I do with the 3 files and readme file?
I think that might fix my problem...I hope.. Thanks again for your help. Much appreciated!
EDIT: I think I got the drivers and it still can't find it. :/ I think I'm going to take a break on rooting for a few. ADB is a pain! lol. I might just wait for an easier method or just not root it. We'll see. Thanks again.

andrew53517 said:
I think I might have figured it out, if this is it. So I downloaded the drivers but I don't think they ever installed. Don't laugh lol, how do you install them? There isn't a .exe file or anything to install them.. I just see files and notes. Do I put it somewhere or what do I do with the 3 files and readme file?
I think that might fix my problem...I hope.. Thanks again for your help. Much appreciated!
EDIT: I think I got the drivers and it still can't find it. :/ I think I'm going to take a break on rooting for a few. ADB is a pain! lol. I might just wait for an easier method or just not root it. We'll see. Thanks again.
Click to expand...
Click to collapse
If you get a chance, try this on a Windows XP or Windows 7 machine that you haven't connected the Transformer too yet, and follow the guide exactly, and I'm pretty sure it will work without a problem I'm just thinking something has happened when it loaded up the drivers for you initially and that is why you are having the issues, or some background process on either Windows or the Transformer is making the device seem "busy", thus giving you the not ready error, as this process has worked for many many other users.

I was just thinking about it. Maybe I can try that on my downstairs computer. Ill give it a shot Sunday night and see how it goes...ill let you know...

[GUIDE] How to install Universal Naked Drivers

I have seen many questions asking how to install universal naked drivers. Last week I received (loan) a windows computer and had the same issues. I decided to provide the info to help others.
Note: These drivers do work properly for the TF300T even though they may not state that exactly. Also if your tablet identifies as a TF201 it will still work properly.
Note: If you are on windows 8 and having problems please see the bottom of this post #1 for help! This info was provided by prototype7 please give him a thanks.
First some info. Windows thinks it should make the choices about drivers and is designed to keep us from choosing something that might cause problems. We need to maintain control through the process if we are to succeed.
Here are the choices I had to use to change my drivers and a link to the drivers.
windows-start - in search type device manager and return
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
right click on the entry you wish to change the driver for
Update Driver Software
Browse my computer for driver software
Let me pick from a list of device drivers on my computer
Have Disk
Browse
choose the universal naked drivers directory
click on the proper inf file
windows says drivers not signed; install anyway
Windows 8
Note: The following info was kindly provided by prototype7. Please give him a thanks.
Originally Posted by prototype7
I was trying to install these using this guide on Windows 8, but was running into a problem with the drivers not being signed, so here's the solution:
Hit Start+X, select Command Prompt (Admin)
Type "shutdown -o -r -t 0" (without quotes) and hit enter
You'll get a screen with some options on it after a few seconds
Click Troubleshoot
Advanced Options
Windows Startup Settings
Restart
You'll get a menu of options to choose from
Press the number on your keyboard for "Disable driver signature enforcement"
Now you can follow the guide without any issues, reboot again after the drivers are installed and you'll be good to go.
Click to expand...
Click to collapse
using this method you don't have to uninstall your current driver
if you deviate at any step windows will refuse to allow this change
Good Luck!

Re: How to install Universal Naked Drivers
Thanks for this thread which is really good and useful :good:
Good stuff
Sent from my N7 3G with DroiDevs premium between sky and earth.

And this thread is now stickied
MD

philos64 said:
Thanks for this thread which is really good and useful :good:
Good stuff
Sent from my N7 3G with DroiDevs premium between sky and earth.
Click to expand...
Click to collapse
Thanks for the kind words. I have wanted to post this for sometime but didn't have windows to prove the method.

Moscow Desire said:
And this thread is now stickied
MD
Click to expand...
Click to collapse
Thank you!
I just hope it can help some others getting their drivers installed and working.

Hi,
first thanks for the thread (i believe it will help a lot of people)
I followed all the steps, but it still doesn't work...
I did a lot of research but i have not found the solution... When i use fastboot, it still "<waiting for device>".
Anyone have the same probleme ?
Thanks for the help.
EDIT: Fine it's my fault, the cmd line have to be with -i 0x0B05 option, without it, it doesn't work.

Manox7 said:
Hi,
first thanks for the thread (i believe it will help a lot of people)
I followed all the steps, but it still doesn't work...
I did a lot of research but i have not found the solution... When i use fastboot, it still "<waiting for device>".
Anyone have the same probleme ?
Thanks for the help.
EDIT: Fine it's my fault, the cmd line have to be with -i 0x0B05 option, without it, it doesn't work.
Click to expand...
Click to collapse
Thanks!
I don't know why some tablets require the tablet designation and others don't. For that reason we suggest everyone use them. It is a code assigned by google that designates the manufacture of the unit. On linux we have to declare them to avoid a permissions error but we don't have to add drivers.
I'm glad you got everything sorted.

I was trying to install these using this guide on Windows 8, but was running into a problem with the drivers not being signed, so here's the solution:
Hit Start+X, select Command Prompt (Admin)
Type "shutdown -o -r -t 0" (without quotes) and hit enter
You'll get a screen with some options on it after a few seconds
Click Troubleshoot
Advanced Options
Windows Startup Settings
Restart
You'll get a menu of options to choose from
Press the number on your keyboard for "Disable driver signature enforcement"
Now you can follow the guide without any issues, reboot again after the drivers are installed and you'll be good to go.

prototype7 said:
I was trying to install these using this guide on Windows 8, but was running into a problem with the drivers not being signed, so here's the solution:
Hit Start+X, select Command Prompt (Admin)
Type "shutdown -o -r -t 0" (without quotes) and hit enter
You'll get a screen with some options on it after a few seconds
Click Troubleshoot
Advanced Options
Windows Startup Settings
Restart
You'll get a menu of options to choose from
Press the number on your keyboard for "Disable driver signature enforcement"
Now you can follow the guide without any issues, reboot again after the drivers are installed and you'll be good to go.
Click to expand...
Click to collapse
Thanks for the update info. If it is ok I'd like to quote your information in the first post for others who are on windows 8.

tobdaryl said:
Thanks for the update info. If it is ok I'd like to quote your information in the first post for others who are on windows 8.
Click to expand...
Click to collapse
Go ahead, it would make it easier to see. Glad I could help.

prototype7 said:
Go ahead, it would make it easier to see. Glad I could help.
Click to expand...
Click to collapse
Thanks again, I'll put in the first post for others.

Windows for x64
tobdaryl said:
Thanks again, I'll put in the first post for others.
Click to expand...
Click to collapse
Hello. I am having problems getting ADB to open. I did everything you mentioned hoping that these new drivers would work, but at the end I got a message window with "Select Device" saying;
"The folder you specified doesn't contain a compatible software driver for your device. If the folder contains a driver, make sure it is designed to work with Windows for x64-based systems.
I am using a Droid Razr Maxx with CM 10 installed on Android version 4.2.2. I have tried everything to get ADB to open and nothing seems to work.
Thank you in advance for your time

nathanielhall929 said:
Hello. I am having problems getting ADB to open. I did everything you mentioned hoping that these new drivers would work, but at the end I got a message window with "Select Device" saying;
"The folder you specified doesn't contain a compatible software driver for your device. If the folder contains a driver, make sure it is designed to work with Windows for x64-based systems.
I am using a Droid Razr Maxx with CM 10 installed on Android version 4.2.2. I have tried everything to get ADB to open and nothing seems to work.
Thank you in advance for your time
Click to expand...
Click to collapse
You have to actually select the file not just the directory. By only selecting the directory you give windows a choice. If windows has a choice it will always refuse to install.
Point windows to the android_winusb.inf file and it should install properly.

file selected still not working
tobdaryl said:
You have to actually select the file not just the directory. By only selecting the directory you give windows a choice. If windows has a choice it will always refuse to install.
Point windows to the android_winusb.inf file and it should install properly.
Click to expand...
Click to collapse
I have tried multiple times to select the file android_winusb file there is no .inf next to it but the file type is setup information

nathanielhall929 said:
I have tried multiple times to select the file android_winusb file there is no .inf next to it but the file type is setup information
Click to expand...
Click to collapse
That should be the proper file. In folder options there is probably a check in "Hide Known File Types". This will keep you from seeing certain extensions. Windows uses the inf extension for setup information.
Try the other inf file android_apxusb.inf and see if that will install. If you have already then I am lost.
Are you on windows 8? If so please see the topic Windows 8 at the bottom of the first post.

Still nothing
tobdaryl said:
That should be the proper file. In folder options there is probably a check in "Hide Known File Types". This will keep you from seeing certain extensions. Windows uses the inf extension for setup information.
Try the other inf file android_apxusb.inf and see if that will install. If you have already then I am lost.
Are you on windows 8? If so please see the topic Windows 8 at the bottom of the first post.
Click to expand...
Click to collapse
I have tried to select the android_apxusb file and I get the same message.
I am on Windows 7 x64
Also can you help me get a reply to this post: http://forum.xda-developers.com/showthread.php?t=2257005
I posted it a while ago and no one has answered me. Maybe you can help me with this post.

nathanielhall929 said:
I have tried to select the android_apxusb file and I get the same message.
I am on Windows 7 x64
Also can you help me get a reply to this post: http://forum.xda-developers.com/showthread.php?t=2257005
I posted it a while ago and no one has answered me. Maybe you can help me with this post.
Click to expand...
Click to collapse
I'll do some research and reply on the other thread. Adb is working if you get your serial number with adb devices, adb kill-server, etc.
In windows drivers have to be installed to get anything from your tablet with adb. Drivers are not needed for Linux and Mac but are required for windows.
Before I forget to mention later you need to run cmd as administrator in windows to use adb but since you fail with a terminal on the unit it may be a structure issue with the command.

how do I start ADB?
tobdaryl said:
I'll do some research and reply on the other thread. Adb is working if you get your serial number with adb devices, adb kill-server, etc.
In windows drivers have to be installed to get anything from your tablet with adb. Drivers are not needed for Linux and Mac but are required for windows.
Before I forget to mention later you need to run cmd as administrator in windows to use adb but since you fail with a terminal on the unit it may be a structure issue with the command.
Click to expand...
Click to collapse
I changed the path to C: Android-SDK platform tools and when I ran cmd as an administrator all I typed was adb. Am I missing something here? I also tried adb.exe

nathanielhall929 said:
I changed the path to C: Android-SDK platform tools and when I ran cmd as an administrator all I typed was adb. Am I missing something here? I also tried adb.exe
Click to expand...
Click to collapse
Check the thread you wished me to help with as I think I have already posted the resolution there.

tobdaryl said:
I'll do some research and reply on the other thread. Adb is working if you get your serial number with adb devices, adb kill-server, etc.
In windows drivers have to be installed to get anything from your tablet with adb. Drivers are not needed for Linux and Mac but are required for windows.
Before I forget to mention later you need to run cmd as administrator in windows to use adb but since you fail with a terminal on the unit it may be a structure issue with the command.
Click to expand...
Click to collapse
Thanks for ur great job
I have tf300t with replaced logicboard. -it was bricked
My os win8 64bit
I tried universal naked driver ..but no way
is their any reasons with the last bricked in this case...??
Sorry for the poor english

Fixing MTP/Debugging not reading your Nexus device...

Ok peeps... I've flustered myself over this issue for a while, and noticed in a couple other threads that others are having this issue as well, so I'm posting what I hope to be a "cure all" for devices not reading in Windows as MTP devices. This should work in any and every Google Nexus devices, with the one exception being the actual Galaxy Nexus (model SCH-I515) because it's driver is distributed by solely by Samsung.
A little background:
For a long while, I had my device all nice and set up, ready to use and work with as I so pleased, and then it seemed like there was a driver update, and from then on out, I couldn't get my device (in this case, the Nexus 7 Grouper) to be read by Windows as anything other than a PTP (camera) device... I looked high and low over the internet (including this site) for a fix to my problem, a number of offerings to look over, and seemingly only one of them worked. So... Here I am to share it with you all, so hopefully you don't have to fight with it (anymore) like I did...
Just a quick FYI, this worked for me using BOTH Windows Vista (64 bit) and Windows 7 (64 bit), and really should be pretty much universal for all versions of Windows (but don't quote me on that, I'm not saying it with 100% confidence)
Now, a lot of the pages that I came across in my search suggested that you have to uninstall this or that, reboot a half dozen times, and really, more work than it actually took, so I'm going to offer up the way that worked for me, and did so simply. I'm not saying that pages like TheByteSmasher's or sfhub's version for the 2013 N7 model didn't work, simply that they took more steps than what actually worked for me with less hassle. That all being said, let's get to fixing the issue at hand...
I suggest that on your computer that you have a display of your computer's drives (start menu, then selecting/entering the "computer" option)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
in the background while you're doing all of this. Visually, it serves as an aid for what you may or may not have to do. If at any time your device shows up in your computer's devices in MTP mode, you should already be fine. If not, please continue.
On your device:
Begin by plugging your device into your computer using a data-compatible USB cord (most stock cords that come with your device are).
If your computer starts trying to install device drivers, let it take it's course, and see if your device is working "as is" with USB Debugging.
Note that every time you switch debugging on or off, or switching between MTP and PTP, your computer could/might install drivers for each mode. Let this finish before making another selection.
Open the Settings app.
Choose Storage.
Touch the Menu icon button, and then choose the command USB Computer Connection. (Might be up in the corner somewhere, in a pulldown menu... Mine had 3 dots set up like a colon if that helps ya get the image)
There should be two options; MTP and PTP.
Ensure that there’s a check mark by the Media Device (MTP) option.
Back out of the Storage tab, and go into Developer Options.
If Developer options is not available to you, go to "About phone/tablet/device", and where your build number is listed, tap that section 7 times. After about the 4th time of you tapping it, it'll toast you a little notification that just says "continue tapping for developer mode"​
Once you're in Developers Options, go to the Debugging area, and select enabling of USB Debugging.
On your computer:
Get into your device manager. This can be done a number of ways, some of which depend on which version of Windows you're on... I personally use the WindowsIcon+PauseButton shortcut feature, but if you need directions on this;
Clicking the Start button > click Control Panel > System and Security > under System, clicking Device Manager.* Administrator permission might be required depending on settings and your user account of your computer. Another way to do this, again depending on which version of Windows you have, could be done by opening the Start button, and in the search feature typing in "device manager"
Once in device manager, it'll display all devices connected to your computer. If you're unsure as to which connects to your device, simply pay attention to the device manager while you unplug your device (it'll refresh) and then plug your device back in (another refresh will happen). Chances are, it'll be either a collapsable tab called "Android device/phone/tablet" or it'll be in your "Portable Devices" collapsable tab. (It could also be in USB controller/devices, for whatever reason) Whichever one it is for you, expand that tab and it'll show something like "Android Composite ADB Bootloader Interface" or some variation of those words. This is good, we know that your computer is reading that your device is connected, even if it's not (presently) allowing MTP.
Double-click the Android Composite ADB Bootloader Interface submenu item, and it'll pull up the properties of it, giving you 3 tabs to select from. Go to the "Driver" tab, and read what version of driver it says you have installed.
Taking a step away from that for a minute, download the latest Google USB Driver zip and save it into a directory where you can easily find it... Download folder or desktop work fine, whichever you're more comfortable with.
BTW, if for whatever reason the link above doesn't work, you can go directly to the Google USB driver page and download it from there, but the first link takes you directly to the latest download zip file itself...
Once you have the file downloaded, extract it into a folder using a program like WinRAR or other zip file utilities.
NOTE: The next step is not mandatory, but I suggest it for users who are knowledgeable enough to know that there are files, folders, and other such things on your computer are not meant to be messed with, and if you do so, you could mess up your computer. What I'm doing will not mess up your computer AT ALL, but if you decide to mess with other things in folders we're going to access, then YOU can mess it up. You've been notified, I'm not going to take responsability for your actions, because if all you do is follow my directions, NOTHING bad will happen. If you're uncomfortable with messing with system folders/files, just skip to the step beyond this... This one is done purely for cosmetic and easily accessible reference reasons only.... That being said, go into your computer's driver's folder, which will usually be found at C:\Windows\System32\drivers. From there, create a new folder and call it "Android", and then go into it. Take the files that you extracted in the previous step, and move them all to here. After moving them all into the android folder, remember the location you're at in Windows, you'll be using it in the next step...
Whether or not you did the previous step, it's important that you know where the files you extracted are now placed. Going back to the device manager program, in the tab "driver", you'll see where it says "Update Driver". Click that.
A prompt will come up asking if you want to "search (online) automaticly for updated driver software" or to "browse your computer for driver software". You have already downloaded the latest driver, and honestly the automatic search often finds a driver that's useless or doesn't work right, so you'd select to browse your computer... If you moved the files into the drivers folder done a couple steps back, provided you haven't named your computer or placed the files on another drive than your C:/ drive, your location for what you're looking for should be C:\Windows\System32\drivers\Android\latest_usb_driver_windows\usb_driver. Feel free to copy and paste that upon your need, and place it directly into the "search for driver software in this location" box.. Hitting "Next" should bring you to the next step (below). If you didn't move the files (or they're in a different directory, or for whatever reason the above didn't work for you), then you're going to have to point your computer to where you placed the extracted files... And this kinda gets "iffy", as in "if the computer sees what you've done" or you actually have to "hold it's hand" to recognize what you've done. In other words, at this state of implementing the files, you computer really hasn't recognized them (the driver files) existing on your computer. So, chances are, you're going to have to do some hand-holding, which is fine, because atleast this way, we know we're all doing it in a way that both you and your computer aren't having to guess....From here what you'll need to do is select "Let me pick from a list of drivers on my computer" and upon doing so, UN-ticking the "show compatible hardware" check-box. You should see now a couple of selection boxes listed as Manufacturer and Model. Do NEITHER of these. Instead, click the "Have Disk" option, and a "Install from disk" menu will pop up. From there, go into "Browse..." and point your computer to wherever you placed the extracted files, opening all the folders until you come to a file called android_winusb.inf, and selecting it. This will guarantee that your computer is grabbing and using the exact file you're wanting it to, the correct driver update installation.​
After selecting the "android_winusb.inf" file and hitting Open/OK, it'll bring you back to where you un-ticked the "show compatible hardware" option earlier, with it now being re-ticked (which is fine). There might be a few listings as to which you can choose from there under the "model" tab, and any of those should work for you. You have to CLICK which one you want until a popup appears. I just chose the one with the longest name, figured it served the most purposes... :laugh:
Anyways, your driver will start installing... You'll likely hit a warning message that says something to the extent of "this driver cannot be verified"... Shoot right through that and allow it, and your device will finish installing the driver... If your sound is on, you'll notice a new device connection sound... Check back in the contents of your computer connections, and you should see your "new" device listed there. If not, sometimes a restart might be required.
Congrats, your device is now seen by Windows:
If this helped you, I'd love a thanks!

reserved....

TToTT said:
... download the ... driver ... from there...
Click to expand...
Click to collapse
User 1wayjonny has also made his offering of what he calls "Naked Drivers" which offers more "Universal" android coverage than just Nexus devices, though I haven't tested/used them myself. Procedure would be the same as above, just pointing to his drivers instead. His post can be found here.

I'm having an issue where I can connect to my 64 bit Win 7 laptop in debug mode, but I'm not able to connect in the MTP mode with debug turned off. I expected to be able to mount the device storage in either mode.
Is that correct? If so, any ideas? I do notice I can't seem to get the MTP driver to stay in device manager.
Rick

C5Longhorn said:
I'm having an issue where I can connect to my 64 bit Win 7 laptop in debug mode, but I'm not able to connect in the MTP mode with debug turned off. I expected to be able to mount the device storage in either mode.
Is that correct? If so, any ideas? I do notice I can't seem to get the MTP driver to stay in device manager.
Rick
Click to expand...
Click to collapse
Try not only removing, but actually deleting the driver you're on while your device isn't connected, and after doing so, reconnect the device with the newest drivers installed on your computer. For some reason, Windows has been known to trick itself into either allowing or not allowing things to work simply because of this. As for why you're able to connect in MTP in debugging mode and not when you've got debugging turned off goes, part of the entire reason for debugging mode is for compatibility. It certainly doesn't harm either your computer or device in one vs the other (debugging on or off), so as long as you have one that does work, there's no need for the other, or to have a "problem" with not having the other. If you're just OCD about fixing things like this though, there's always trying what I suggested to begin with.... (first sentence)

Thanks for the response. I'm going to give your suggestion a try because I am OCD about this kind of thing. It's nice to know I've got it working, but bugging me that I can't get it working all the time.
Rick

Actually, deleting the drivers seems to have done the trick. I'm going to watch it over the next few days, but thanks again for the tip.
Rick

C5Longhorn said:
Actually, deleting the drivers seems to have done the trick. I'm going to watch it over the next few days, but thanks again for the tip.
Rick
Click to expand...
Click to collapse
Happy to have been of some help. :good:

bro there is no latest_usb_dri ver_windows type folder in this downloaded zip.pls help me

[Q] SGS5 Not recognized by PC!

Whenever I connect my phone to my computer via USB, it says "USB Device not recognized". I look in my device manager and I see 4 devices come up called "Bluetooth Peripheral Device" show up under "Other devices", yet they got yellow warning symbols next to them.
My phone connects to my PC via Bluetooth fine, but the USB just wont work! I've searched the web but most things are outdated or just don't work...
I think this is due to using an OTG cable, making my phone act as the host device whenever I plug it in?
Extra detail:
-PC is running Windows 7 ultimate x64
-Samsung Galaxy S5 is on Android 5.0, but didn't work on previous versions either
-I use the samsung cable, but have also tried one other cable.
-Tried plugging it into another computer, does the exact same thing.

Install Samsung drivers / KIES3

*Detection* said:
Install Samsung drivers / KIES3
Click to expand...
Click to collapse
Already tried those, made no difference unfortunately

CheeseJuggernaut said:
Whenever I connect my phone to my computer via USB, it says "USB Device not recognized". I look in my device manager and I see 4 devices come up called "Bluetooth Peripheral Device" show up under "Other devices", yet they got yellow warning symbols next to them.
.
Click to expand...
Click to collapse
Have a look at this post I put up for someone with a similar problem to you, see if it helps, you need to use the USB cable that came with the phone, others will work but a lot don't work properly
Post

ag4751 said:
Have a look at this post I put up for someone with a similar problem to you, see if it helps, you need to use the USB cable that came with the phone, others will work but a lot don't work properly
Post
Click to expand...
Click to collapse
Thank you for the great help, I think that this is what needs to be done to fix it. There is still one problem though.
I have tried this before, but I ran into a problem where it would do this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
As you can see, it wont let me use the driver, saying that there is a "code 10" and that the driver wont start. I think that if I can get through this error, my phone will finally connect

CheeseJuggernaut said:
As you can see, it wont let me use the driver, saying that there is a "code 10" and that the driver wont start. I think that if I can get through this error, my phone will finally connect
Click to expand...
Click to collapse
Try these options,
1. Control Panel > Devices & Printers then plug in your phone and you should get an Unknown Device appear, right click on it and select Troubleshoot and run that process to see if that sorts out the problem.
2. Start your computer in safe mode then try installing the driver manually that way, then reboot your PC normally.
Registry solution if you want to try it as long as you understand Windows Registry
1. Go to the Registry Editor click Start > Run > and type in regedit then hit Enter
2. Expand the folder location HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Contro l\Class\
3. Find EEC5AD98-8080-425f-922A-DABF3DE3F69A in the folder list and click on it, this should say Portable Devices in the right window
4. See if it contains a value called UpperFilters if so delete it
5. Before you delete it though make a backup of the EEC5AD98-8080-425f-922A-DABF3DE3F69A folder, right click on it and Export to a folder just in case you need to restore it.
6. To restore the key if you need to just go to the folder where you exported it to and click on it to install

ag4751 said:
Try these options,
1. Control Panel > Devices & Printers then plug in your phone and you should get an Unknown Device appear, right click on it and select Troubleshoot and run that process to see if that sorts out the problem.
2. Start your computer in safe mode then try installing the driver manually that way, then reboot your PC normally.
Registry solution if you want to try it as long as you understand Windows Registry
1. Go to the Registry Editor click Start > Run > and type in regedit then hit Enter
2. Expand the folder location HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Contro l\Class\
3. Find EEC5AD98-8080-425f-922A-DABF3DE3F69A in the folder list and click on it, this should say Portable Devices in the right window
4. See if it contains a value called UpperFilters if so delete it
5. Before you delete it though make a backup of the EEC5AD98-8080-425f-922A-DABF3DE3F69A folder, right click on it and Export to a folder just in case you need to restore it.
6. To restore the key if you need to just go to the folder where you exported it to and click on it to install
Click to expand...
Click to collapse
Sorry for the late reply, ive been busy.
There is no UpperFilters value, and unfortunately the troubleshoot didnt resolve the problem.

CheeseJuggernaut said:
Sorry for the late reply, ive been busy.
There is no UpperFilters value, and unfortunately the troubleshoot didnt resolve the problem.
Click to expand...
Click to collapse
You are having a problem with this aren't you.
If you have Kies installed uninstall it also plug in your phone and find it in the list of USB Devices, then right click select properties and uninstall the driver, unplug the phone and reboot your PC.
Once rebooted Temporarily turn off any firewalls and Anti Virus scanners and try the below
Install Kies 3, start Kies and check for updates, if there are any updates then install them.
Restart Kies 3 after any update, once its running plug in your phone and let the drivers install
If its worked properly Kies will see it, if not then check the USB devices and try to install the driver manually again
Don't forget to use the USB cable that came with the phone

ag4751 said:
You are having a problem with this aren't you.
If you have Kies installed uninstall it also plug in your phone and find it in the list of USB Devices, then right click select properties and uninstall the driver, unplug the phone and reboot your PC.
Once rebooted Temporarily turn off any firewalls and Anti Virus scanners and try the below
Install Kies 3, start Kies and check for updates, if there are any updates then install them.
Restart Kies 3 after any update, once its running plug in your phone and let the drivers install
If its worked properly Kies will see it, if not then check the USB devices and try to install the driver manually again
Don't forget to use the USB cable that came with the phone
Click to expand...
Click to collapse
Unfortunately this hasnt worked. As always I plug my phone in (while unlocked) and nothing happens exept for the notification on my desktop about a usb device not recognised

CheeseJuggernaut said:
Unfortunately this hasnt worked. As always I plug my phone in (while unlocked) and nothing happens exept for the notification on my desktop about a usb device not recognised
Click to expand...
Click to collapse
I have run out of suggestions, your PC is just being difficult, I tried googling the problem but nothing really helpful there, but I did find this Link and a few people said it sorted it for them, have a look the solution for them was the links in post 18

ag4751 said:
I have run out of suggestions, your PC is just being difficult, I tried googling the problem but nothing really helpful there, but I did find this Link and a few people said it sorted it for them, have a look the solution for them was the links in post 18
Click to expand...
Click to collapse
Thanks for trying! I think im gonna go get my phone port checked out at the phone shop. Thanks again!

CheeseJuggernaut said:
Thanks for trying! I think im gonna go get my phone port checked out at the phone shop. Thanks again!
Click to expand...
Click to collapse
Are you using the OEM cable?

Rapunzl said:
Are you using the OEM cable?
Click to expand...
Click to collapse
Yes, and ive tried other cables. Its a problem that is most probably hardware though

CheeseJuggernaut said:
Thanks for trying! I think im gonna go get my phone port checked out at the phone shop. Thanks again!
Click to expand...
Click to collapse
Take the original USB cable as well so they can try another one against yours just in case it a faulty cable

[GUID] Enable Remote SIM Access Protocol (rSAP) on the OnePlus One, using QPST

This guid shows two things:
1. How to enable QPST and USB diag mode.
2. How to enable rSAP.
Please notice, I'm not responsible for any damage in hard- and software of your devices, if you are following this guid. You do all on your own risk.
Click to expand...
Click to collapse
For this guid your device have to be rooted.
In the newer versions of OnePlus' CyanogenMod diag mode is disabled in kernal. Therefore you have to flash an earlier ROM. In this step download Calkulin's Stock Rooted XNPH44S ROM and store zip to your device.
Go to recovery and make a full backup. This is really necessary to preserve the state of your phone.
Wipe Dalvik Cache, System, Data and Cache. ATTENSION: This will delete all your settings, apps and app data!
Install XNPH44S ROM
After rebooting system go to Settings -> About Device -> tab ten times on Build-Number to unlock developer settings. Than go to Developer settings and make sure USB debugging is enabled.
Download the package, containing driver and QPST
Connect your device to USB, go to Settings -> Storage -> USB computer connection and deselect both MTP and PTP.
For Win8 and Win10: restart with deactivated driver signature check.
Open ADB (Android SDK) and type following commands:
Code:
adb shell
Code:
su
Code:
setprop sys.usb.config diag,adb
Go to Windows Device Manager and open Other Devices node. There are two entries of our device "A0001". Klick right on the first one and choose Update driver software -> Browse my computer... -> Let me pick from a list... -> Show all devices -> Have disk -> Browse...
Browse to folder Driver in downloaded package, than open Win x64 or Win x86 corresponding to your system, select *.inf file and apply.
After seccessful installation there is a Modems node in Device Manager, containing node HTC USB Modem. Right click and go to Properties. In top of the Modem tab page is the information about used COM-port. Remember that COM<number>.
Go to QPST folder in downloaded package and execute setup.exe to install QPST.
Open QPST Configuration from windows Start menu, go to Ports tab page and click on Add New Port.... Type (the remembered) COM<number> to the "Port:" text box and OPO to the "Port Label:" text box. Than click on OK.
Active Phones tab page should now look like this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Now you can use QPST.
Open EFS Explorer from windows Start menu. It may take a moment to read data from your device.
On left side you can see a folder tree like in file explorer. Navigate to /nv/item_files/modem/qmi/uim
Click right on right side and than Copy Item File from PC. Browse to EFS Entry folder of downloaded package and choose file sap_security_restrictions.
Close all windows and reboot your device. If you want, you can repeat the steps 10, 16 and 17 to verify success.
Boot to recovery and restore your backup.
Now go to Google Play and download app Bluetooth SIM Access Install and app Bluetooth SIM Access (Trial)
Open Install app and click on Install system files. The phone have to reboot after installation. If you want to verify successful installation, open app again, the desintall button have to be enabled now.
Enable your Bluetooth
Open Bluetooth SIM Access (Trial) app go to Settings -> Check SIM Access. If there no errors and several entries with green check marks, than rSAP is working now.
Files:
Package (On Mega click on 'download in browser')
ROM (On Mega click on 'download in browser')
Acknowledgement:
Thank you devilsshadow, for your tutorial, which showed me how to setup QPST.
Thank you Calkulin, for your ROM, which makes it possible to use QPST.
Special thanks goes to Martin , for developing his great apps and making our phones better.

Great! Thanks a lot!
Finally got my OPO working with my VW premium bluetooth car system

EFS Explorer crashes with a Runtime error upon opening sap_security _restrictions file.
Win 10 64Bit.
Edit:
Got it to work with the Frankenstein modem from here:http://forum.xda-developers.com/oneplus-one/general/firmware-modem-oneplus-one-lollipop-t3300907
Looks like it does not work with the newer modems, i was using bacon_firmware_update_2016_1-25_.4.0.1.c7-00011.zip

Hi, do you have further informatiom about the crash? Exact error message?
Did you try windows compatibility mode?
I used win 8.1 x64. Sorry I don't have win 10 to test it.

I used Win 10 Pro 64bit, and had no problems using the software.

Thank you very much for the precise description! I linked it from android-rsap
With my newly acquired OPO I first could not install the diag drivers. The USB id seems to have changed from VID_05C6&PID_6765&MI_00 to PID_676C. After changing that in the inf file the installation worked and I could run QPST.

Great. Thanks a lot.
Can i flash after enabling rSAP CM13, or will it disable rSAP again?
Thank you.

I'm wondering about this myself.
I was running jgcaap CM13 before I did enable RSAP. Took a backup of everything in TWRP first. And restored everything except EFS after (thought that if I flashed EFS I would loose rsap again, but I'm not sure). Everything is working fine btw

fitzpete said:
EFS Explorer crashes with a Runtime error upon opening sap_security _restrictions file.
Win 10 64Bit.
Click to expand...
Click to collapse
This seems to happen with more recent baseband versions. They require the "Factory Test Mode" (ftm_mode) to be set to allow changes. ftm_mode is NV item 453. It can be modified with the QXDM tool.
Now the value of ftm_mode is cached inside the baseband software. Currently I don't know a better solution than to reboot the phone. Sadly in some phones (OnePlus 2) the value doesn't survive the reboot.

Mugen_Civic said:
Great. Thanks a lot.
Can i flash after enabling rSAP CM13, or will it disable rSAP again?
Thank you.
Click to expand...
Click to collapse
Yesterday I do enable RSAP, wow I am really happy about that.
What happens when do a full wipe for flash and install an clean ROM? Is RSAP deactivated again?
Gesendet von meinem A0001 mit Tapatalk

hums87 said:
What happens when do a full wipe for flash and install an clean ROM? Is RSAP deactivated again?
Click to expand...
Click to collapse
No. RSAP will stay enabled.

Hi many thanks for this guide but all link are dead ! can you reupload them ?
thanks

Thanks for the hint. I will reupload it soon and give an announcement.

mamath53 said:
Hi many thanks for this guide but all link are dead ! can you reupload them ?
thanks
Click to expand...
Click to collapse
I reuploaded the files to other hoster.

Could someone tell me what this is good for?

Flatric said:
Could someone tell me what this is good for?
Click to expand...
Click to collapse
RSAP (remote SIM access protocol) is a communication standard for free speeking systems. Eg. Volkswagen concern uses it in its cars. The SIM of your phone is cloned per bluetooth to your cars build in mobile phone module. The radio functions (calling/SMS) are disabled on your phone while connection and executed by your car. That is good for battery, electro smog in your car and connectivity.
But it have drawbacks too. No internet connection on phone while connection. This problem is solved in newer cars by providing a wifi hotspot, which uses the internet contract of your SIM.

Hi
If I open Bluetooth SIM Access (Trial) app, there is no "Check SIM access" option.
Did I do something wrong?

r0tati0n said:
Hi
If I open Bluetooth SIM Access (Trial) app, there is no "Check SIM access" option.
Did I do something wrong?
Click to expand...
Click to collapse
Hi, I think the check has moved to the installer app. See section 3.

Thanks
Altough I couldnt find anything in there too...
In the installer app I get 3 check marks:
System Files installed, Connect to Socket, Connect to SIM, all green.
Does that mean I have RSAP?
Do I need anything else?
Can I uninstall the app and keep RSAP?

r0tati0n said:
Thanks
Altough I couldnt find anything in there too...
In the installer app I get 3 check marks:
System Files installed, Connect to Socket, Connect to SIM, all green.
Does that mean I have RSAP?
Do I need anything else?
Can I uninstall the app and keep RSAP?
Click to expand...
Click to collapse
I think so. Test it with your car. Thats the reason why the trial app exists. But you have to know that the trial app swaps numbers in contact, therefore it is not good for all day use.
I haven't uninstalled the installer app. In this app you can see updates for the system files. But the updates are seldom and if the installed version works for you, I think it's no problem to uninstall it.