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...

[Q] MTP XP Driver

I attempted to search for this issue, and while there are many similar issues, I haven't actually seen a resolution for 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"
}
I need the MTP driver for Windows XP. I've gotten the other 2 drivers up & running, but not the MTP. Anyone able to provide a link for a working MTP driver for my Nexus 7?

I guess you have to install Windows Media Player (this is only possible with a genuine Windows).
Personally I use AirDroid to transfer files. ( https://play.google.com/store/apps/details?id=com.sand.airdroid )

goebish said:
I guess you have to install Windows Media Player (this is only possible with a genuine Windows).
Personally I use AirDroid to transfer files. ( https://play.google.com/store/apps/details?id=com.sand.airdroid )
Click to expand...
Click to collapse
I already have Media Player 11 on there. No go.
AirDroid isn't an option as we only have WiFi at work on our outside LAN and our computers are all behind the firewall.

i had this issue recently.
do you have USB debugging turned on? if so, turn it off.

mrhomiec said:
i had this issue recently.
do you have USB debugging turned on? if so, turn it off.
Click to expand...
Click to collapse
Yeah. No luck.

@mrhomiec
Yes, I turn USB debugging off and try re-installing the driver again and it is working fine now. Many thanks.:good:

After ages trying to root my Nexus 7 and repeatedly un/re-installing of drivers using various 'toolkits' and then finally succeeding, I was upset to see this problem in Device Manager.
Seeing mrhomiec's excellent solution in the first thread I looked at was a great relief. Many thanks!

Media Transfer Protocol Porting Kit
I know this is super old but just in case anyone searched this for help, You might try downloading the Media Transfer Protocol Porting Kit
Heard this works. If you Google search "Microsoft MTP" it will be the first result. I can't post links so that's the best I can give you guys.

twista4004 said:
I know this is super old but just in case anyone searched this for help, You might try downloading the Media Transfer Protocol Porting Kit
Heard this works. If you Google search "Microsoft MTP" it will be the first result. I can't post links so that's the best I can give you guys.
Click to expand...
Click to collapse
It helped. Even if the posts are old, there's always someone looking for a solution. Thanks!

MTP working with XP
Here is what I had to do to get MTP working with XP SP3:
1: Download and install MTPPK12
2: Download and intall Media Player 11
3: Connect the N7 to the PC via the USB cable and set USB to MTP instead of "Camera".
4: Open "Settings" and turn off "USB debugging".
5pen "Device Manager" on the PC and look for "Android Device". If you find and entry for an "ADB" device, uninstall the driver. Unplug the N7 and plug it back in. The PC should now find a device titled "Nexus 7" and install the driver. Open "My Computer" and "Nexus 7" should now be listed and ready to transfer files.

A little something to get USB-Debugging working
Hey guys,
for those who want to use their precious Android with enabled USB-debugging at a Win XP system:
1. get some drivers that work fine without enabled debugging (for HTC disciples: http://forum.xda-developers.com/showthread.php?t=2191279 ) and install them.
2. switch your device to usb-debugging and look up the exact hardware-ID @ your device manager (device manager -> android device -> details -> hardware ID) - keep that window open for you'll need the exact key
3. Search the installed drivers (for me it was C:\Programme\HTC\HTC Driver\Driver Files\XP_x86) and edit the 'androidusb.inf'.
4. In the file, look for the 'Device Section' and scroll way down to the 'For XP and later' section. Here you copy the first entry and paste in your hardwareID.
For me, I took:
%USB\VID_0BB4&PID_0C01&MI_01.DeviceDescRelease%=HTCAND32.Dev, USB\VID_0BB4&PID_0C01&MI_01
Click to expand...
Click to collapse
and changed it to:
%USB\VID_18D1&PID_2D02&MI_01.DeviceDescRelease%=HTCAND32.Dev, USB\VID_18D1&PID_2D02&MI_01
Click to expand...
Click to collapse
5. Next scroll down until you find the '[Strings]' section. Here you do the same thing as before:
Copy the first entry and edit it according to your hardwareID.
For me, I took:
USB\VID_0BB4&PID_0C01.DeviceDescRelease="My HTC"
Click to expand...
Click to collapse
and changed it to:
USB\VID_18D1&PID_2D02.DeviceDescRelease="My HTC ONE"
Click to expand...
Click to collapse
(you are free to name it what ever you want )
Next you'll need to scroll down until the patten changes from
USB\VID_0BB4&PID_0C01.DeviceDescRelease="My HTC"
Click to expand...
Click to collapse
to
USB\VID_0BB4&PID_0C01&MI_01.DeviceDescRelease="My HTC"
Click to expand...
Click to collapse
here you'll need to copy the first entry again and edit it to match your needs. Just copy the device name you have entered before.
6. Finally you can install the drivers manually via your device manager. Just choose your pimped androidusb.inf as driver and you should be able to work with your android phone at usb-debugging (for example for MyPhoneExplorer).
Of cause I am not responsible if you wreck your Win XP / your drivers so don't overdo it. If you don't know what you are doing, do it like the Beatles and 'let it be'

doomhendi said:
Hey guys,
for those who want to use their precious Android with enabled USB-debugging at a Win XP system:
1. get some drivers that work fine without enabled debugging (for HTC disciples: http://forum.xda-developers.com/showthread.php?t=2191279 ) and install them.
2. switch your device to usb-debugging and look up the exact hardware-ID @ your device manager (device manager -> android device -> details -> hardware ID) - keep that window open for you'll need the exact key
3. Search the installed drivers (for me it was C:\Programme\HTC\HTC Driver\Driver Files\XP_x86) and edit the 'androidusb.inf'.
4. In the file, look for the 'Device Section' and scroll way down to the 'For XP and later' section. Here you copy the first entry and paste in your hardwareID.
For me, I took:
and changed it to:
5. Next scroll down until you find the '[Strings]' section. Here you do the same thing as before:
Copy the first entry and edit it according to your hardwareID.
For me, I took:
and changed it to:
(you are free to name it what ever you want )
Next you'll need to scroll down until the patten changes from to
here you'll need to copy the first entry again and edit it to match your needs. Just copy the device name you have entered before.
6. Finally you can install the drivers manually via your device manager. Just choose your pimped androidusb.inf as driver and you should be able to work with your android phone at usb-debugging (for example for MyPhoneExplorer).
Of cause I am not responsible if you wreck your Win XP / your drivers so don't overdo it. If you don't know what you are doing, do it like the Beatles and 'let it be'
Click to expand...
Click to collapse
The method in the prior post works fine and is much easier.

lewmur said:
The method in the prior post works fine and is much easier.
Click to expand...
Click to collapse
The method in the prior post works for the MTP device, which doesn't include the adb-interface for every power-user / dev tools and apps, dude
Plus I don't like to flood my system with .. sweet, useful and light-weight progs like MP11 /10 :laugh:
greetz

doomhendi said:
The method in the prior post works for the MTP device, which doesn't include the adb-interface for every power-user / dev tools and apps, dude
Plus I don't like to flood my system with .. sweet, useful and light-weight progs like MP11 /10 :laugh:
greetz
Click to expand...
Click to collapse
The question was how to connect MTP, not ADB. BTW, I'm 74 yrs old and find the appelation "dude" quite offensive.

lewmur said:
The question was how to connect MTP, not ADB. BTW, I'm 74 yrs old and find the appelation "dude" quite offensive.
Click to expand...
Click to collapse
MTP and ADB come hand in hand so if anyone wants to use the ADB-interface, he or she can do so by following this little tutorial and don't even need to spam their system with unnecessary bloatware.. sorry, but I don't see the problem you've got with that ?
And I'm very sorry, I don't understand the problem you've got with a useful tutorial but that doesn't mean that I've got any problem with you oO
So, no offense

doomhendi said:
MTP and ADB come hand in hand so if anyone wants to use the ADB-interface, he or she can do so by following this little tutorial and don't even need to spam their system with unnecessary bloatware.. sorry, but I don't see the problem you've got with that ?
And I'm very sorry, I don't understand the problem you've got with a useful tutorial but that doesn't mean that I've got any problem with you oO
So, no offense
Click to expand...
Click to collapse
My problem is that most people searching a thread like this aren't going to read every post. They go to the "last page" to see what the latest solution is. Your post was on the last page by itself and I was concerned that noobs reading it would think it was "the best" solution. I wanted to point out that the post previous to yours actually had an easier solution. And, IMO, Media Center takes a miniscule amount of disk space compared to what the vast majority of people have available.

lewmur said:
My problem is that most people searching a thread like this aren't going to read every post. They go to the "last page" to see what the latest solution is. Your post was on the last page by itself and I was concerned that noobs reading it would think it was "the best" solution. I wanted to point out that the post previous to yours actually had an easier solution. And, IMO, Media Center takes a miniscule amount of disk space compared to what the vast majority of people have available.
Click to expand...
Click to collapse
Well I have found this thread because I was looking for a solution for the MTP / ADB-problem and thought that other users might find this missing information useful. Your problem with my post would mean that you disagree any discussion or even better solutions to problems (threats) as soon as you posted your solution .. which truly isn't the way a community works.
And sorry, but I won't discuss the cancer-like spreading of MS products to any system with you in this threat. It's not as simple as disk space.
I suggest we now stop bloating up this topic, unless you've got more useful information concerning the problem.

doomhendi said:
Well I have found this thread because I was looking for a solution for the MTP / ADB-problem and thought that other users might find this missing information useful. Your problem with my post would mean that you disagree any discussion or even better solutions to problems (threats) as soon as you posted your solution .. which truly isn't the way a community works.
And sorry, but I won't discuss the cancer-like spreading of MS products to any system with you in this threat. It's not as simple as disk space.
I suggest we now stop bloating up this topic, unless you've got more useful information concerning the problem.
Click to expand...
Click to collapse
I didn't imply that your solution wouldn't work or wasn't valuable info. I merely referred readers back to the previous post so that they would realize they had a CHOICE!!!

lewmur said:
I didn't imply that your solution wouldn't work or wasn't valuable info. I merely referred readers back to the previous post so that they would realize they had a CHOICE!!!
Click to expand...
Click to collapse
.. If they want a truly working USB-interface, they don't have one :laugh:
But you get a 'thanks-click' from me for you intentions

worked like magic!
I followed each step exactly and the magic worked! I can now access my HTC internal storage and SD Card contents from Windows XP.!
Many many thanks!
lewmur said:
Here is what I had to do to get MTP working with XP SP3:
1: Download and install MTPPK12
2: Download and intall Media Player 11
3: Connect the N7 to the PC via the USB cable and set USB to MTP instead of "Camera".
4: Open "Settings" and turn off "USB debugging".
5pen "Device Manager" on the PC and look for "Android Device". If you find and entry for an "ADB" device, uninstall the driver. Unplug the N7 and plug it back in. The PC should now find a device titled "Nexus 7" and install the driver. Open "My Computer" and "Nexus 7" should now be listed and ready to transfer files.
Click to expand...
Click to collapse

Clockworkmod Tether on Windows 8

Trying to install clockworkmod tether on windows 8 laptop but is failing saying tapinstall.exe failed. Eventvwr shows error 1722. Any help would be appreciated.

ixiduffixi said:
Trying to install clockworkmod tether on windows 8 laptop but is failing saying tapinstall.exe failed. Eventvwr shows error 1722. Any help would be appreciated.
Click to expand...
Click to collapse
You must shut off windows 8 driver signing security. It installed fine after i did this.
Click Advanced Startup Under The General Heading Under More PC Settings
After Reboot Click Troubleshoot Advanced Options, Advanced System Setting
After Reboot Type Number To Disable Driver Signing Security
Then Load Up windows 8 then install. This time it will ask you weather or not to install the drivers.

JSmith549 said:
You must shut off windows 8 driver signing security. It installed fine after i did this.
Click Advanced Startup Under The General Heading Under More PC Settings
After Reboot Click Troubleshoot Advanced Options, Advanced System Setting
After Reboot Type Number To Disable Driver Signing Security
Then Load Up windows 8 then install. This time it will ask you weather or not to install the drivers.
Click to expand...
Click to collapse
I will try this once I get home. If this works you, my friend, are my hero.

Thank you for this, solved my problem as well!

JSmith549 said:
You must shut off windows 8 driver signing security. It installed fine after i did this.
Click Advanced Startup Under The General Heading Under More PC Settings
After Reboot Click Troubleshoot Advanced Options, Advanced System Setting
After Reboot Type Number To Disable Driver Signing Security
Then Load Up windows 8 then install. This time it will ask you weather or not to install the drivers.
Click to expand...
Click to collapse
Looks like it changed a little with 8.1. Now its located in:
Setting > Change PC Settings > Update and Recovery > Under Advanced Click Restart Now

JSmith549 said:
You must shut off windows 8 driver signing security. It installed fine after i did this.
Click Advanced Startup Under The General Heading Under More PC Settings
After Reboot Click Troubleshoot Advanced Options, Advanced System Setting
After Reboot Type Number To Disable Driver Signing Security
Then Load Up windows 8 then install. This time it will ask you weather or not to install the drivers.
Click to expand...
Click to collapse
Thank you - mine also worked!!!! :good: ur my :angel:

Is Samsung ADB Driver ALSO Not Digitally Signed In Windows 8.1?
crsmith6196 said:
Thank you - mine also worked!!!! :good: ur my :angel:
Click to expand...
Click to collapse
Your solution allowed Tether to install for me. Do I need to do the same thing for the Samsung ADB drivers?
73 DE N4RPS
Rob

I can get Tether installed on both my Windows 8 Laptop and my Galaxy Nexus device (running 4.3, no root) and I used to be able to use Tether with no issue about one year ago. Now, however, when trying to initiate Tether, this is what I'm presented with:
Starting Tether...
C:\Program Files (x86)\ClockworkMod\Tether\node-tuntap
Opening tun device.
Opening tun device: null
Waiting for interface to get ready... (forker, waiting 5 seconds)
Waiting for interface to get ready... (postSetup, waiting 5 seconds)
Forking worker.
Tun/tap device IP: 10.0.0.1
Reading tun/tap device...
Opening tun device.
adb binary path: "C:\Program Files (x86)\ClockworkMod\Tether\win32\adb.exe"
Checking phone status...
tun worker initialized.
Listening on tether port...
0A3C31D90400C017 New device found.
0A3C31D90400C017 Connecting to device.
0A3C31D90400C017 Checking if package is installed.
Error listing pacakges. Assuming Tether.apk is already installed.
0A3C31D90400C017 Setting up adb port forwarding to port 30002.
0A3C31D90400C017 adb port forwarding results:
{ '0':
{ [Error: Command failed: error: device offline
] killed: false, code: 1, signal: null },
'1': '',
'2': 'error: device offline\r\n' }
0A3C31D90400C017 Error forwarding:
{ [Error: Command failed: error: device offline
] killed: false, code: 1, signal: null }
0A3C31D90400C017 Creating relay for device.
0A3C31D90400C017 Tether error:
{ '0':
{ [Error: connect ECONNREFUSED]
code: 'ECONNREFUSED',
errno: 'ECONNREFUSED',
syscall: 'connect' } }
cleaing up relay connection
0A3C31D90400C017 Tether connection closed.
cleaing up relay connection
0A3C31D90400C017 Tether connection closed.
This is just repeated infinitely until I manually stop Tether on my computer.
Since this is the only thread that comes up when searching for Tether issues on Windows 8 machines I could find, is there anyone who can help me figure out how to get this back to working order?

miguelshihto said:
I can get Tether installed on both my Windows 8 Laptop and my Galaxy Nexus device (running 4.3, no root) and I used to be able to use Tether with no issue about one year ago. Now, however, when trying to initiate Tether, this is what I'm presented with:
Starting Tether...
C:\Program Files (x86)\ClockworkMod\Tether\node-tuntap
Opening tun device.
Opening tun device: null
Waiting for interface to get ready... (forker, waiting 5 seconds)
Waiting for interface to get ready... (postSetup, waiting 5 seconds)
Forking worker.
...........
This is just repeated infinitely until I manually stop Tether on my computer.
Since this is the only thread that comes up when searching for Tether issues on Windows 8 machines I could find, is there anyone who can help me figure out how to get this back to working order?
Click to expand...
Click to collapse
I'm getting the same thing - no luck with it so far.
Anyone who's figured this out - it'd be much appreciated if you can help!

Surface Pro 3
So i just bot a surface pro 3 and i was trying to instal clockworks tethering system and it wants me to download .net frameworks version 2.0, but when i try to download it, it says i already have it. I could relay use some help!

bit late...
javiertrevino73 said:
So i just bot a surface pro 3 and i was trying to instal clockworks tethering system and it wants me to download .net frameworks version 2.0, but when i try to download it, it says i already have it. I could relay use some help!
Click to expand...
Click to collapse
.NET Framework 2.0 is not installed on Windows 8 by default.
To install it, go to Control Panel – Programs – Turn Windows features on or off – Check ‘Microsoft .NET Framework 3.5.1′ – OK.
Note, that .NET Framework 2.0 is included into version 3.5.
Source: wishmesh.com/2011/09/net-framework-2-0-is-not-installed-on-windows-8-developer-preview-by-default

I just bumped up from windows 7 to 10 and when I go to use my tether all I get is this C:\Program Files (x86)\ClockworkMod\Tether when I push start. I haven't read any issuse regaruding tether and windows 10 I doubt I am the the first, does anyone here have any idea what is going on?

Durteedee said:
I just bumped up from windows 7 to 10 and when I go to use my tether all I get is this C:\Program Files (x86)\ClockworkMod\Tether when I push start. I haven't read any issuse regaruding tether and windows 10 I doubt I am the the first, does anyone here have any idea what is going on?
Click to expand...
Click to collapse
I'm also having this same issue so compatibility appears to be broken in Windows 10.

Durteedee said:
I just bumped up from windows 7 to 10 and when I go to use my tether all I get is this C:\Program Files (x86)\ClockworkMod\Tether when I push start. I haven't read any issuse regaruding tether and windows 10 I doubt I am the the first, does anyone here have any idea what is going on?
Click to expand...
Click to collapse
I'm having the same problem myself, I just reported it to the developer so hopefully there will be a fix before too long.

Temp fix at least.
XTCrefugee said:
I'm having the same problem myself, I just reported it to the developer so hopefully there will be a fix before too long.
Click to expand...
Click to collapse
Not too sure, I'm no developer, but I believe there may be issues with the adb drivers. I installed PdaNet+ (same type of app.) and it specifically says Win10 compatible. I allowed it to overwrite the adb drivers with the driver's it determined to be correct and the PdaNet+ app works and tethers to my laptop. I am unfortunately in an area right now with only 2G service so I will not be messing around with it too much tonight but maybe tomorrow I can see if it is going to be a replacement or maybe the new drivers will work with the CM Tether software.

Well i hope they can get too or soon. I dont think its my adb drivers

sprint users
pdanet+ is blocked by sprint.
masqman said:
Not too sure, I'm no developer, but I believe there may be issues with the adb drivers. I installed PdaNet+ (same type of app.) and it specifically says Win10 compatible. I allowed it to overwrite the adb drivers with the driver's it determined to be correct and the PdaNet+ app works and tethers to my laptop. I am unfortunately in an area right now with only 2G service so I will not be messing around with it too much tonight but maybe tomorrow I can see if it is going to be a replacement or maybe the new drivers will work with the CM Tether software.
Click to expand...
Click to collapse

Its *not* usb drivers...
...because
adb devices
and
adb shell ps
...work just fine (after authorising).
Justin C thinks its changes to .Net on the ClockWorkMod forum (I can't post a link unfortunately).
Specifically I think the exe is failing to create the virtual network device (TAP) which then gets passed to run.bat
run.bat should then open up the windows firewall but it just fails with very little output when given no TAP index.
So it could also be driver related. I tried briefly adding some third party Windows 10 TAP driver but to no avail.

[APP][TOOL] ADB-Over-WiFi-Helper

Free for XDA members and as a thank you for all the information, tools and roms XDA Developers has provided over the years here is something I created that makes it easy to connect adb over tcpip to multiple Android devices. Get rid of the wires!
One click to switch adb on all usb connected devices to tcpip.
One click to switch adb on all tcpip connected device back to usb.
Auto discovery of the devices listening on tcpip.
The application consists of two parts. "Helper.jar" to run on the pc and "Helper.apk" for the device.
View attachment 2455389Helper.jar
- Installs the Helper.apk on the device.
- Attempts to switch adb on the device to use tcpip.
- Sends broadcast messages to look for devices on the network.
- Initiates an adb connection over tcp to any ip that responds to the broadcast.
- Provides a button to switch all usb devices to tcpip.
- Provides a button to switch all tcpip devices to usb which also uninstalls the helper.apk file, leaving no "junk" on the device.
{
"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"
}
On the device, Helper.apk
- Turns on WiFi if not already on.
- Checks and shows if the adb port was indeed opened.
- Listens and responds to udp broadcasts from Helper.jar.
Some android devices will work without root but if you get a red message from the helper on the device, you will need to root it to enable adb in tcpip mode. The rooted method to set adb to use tcpip is used in case the device is rooted.
If you like the tool and want to contribute, please feel free to buy the app on the Play store. The attachment contains exactly the same files for free.
Feedback is welcome and I hope someone finds this useful!
Adrian
UPDATE!!
A new tool I am calling "ADB Master" that includes all functionality of ADB-Over-WiFi-Helper plus a lot more is now also available for free to XDA users.
Get the new ADB Master here: http://forum.xda-developers.com/showthread.php?t=2707556
It is highly recommended to use the new download rather than the file attached to this post!

Thanks for this. Much appreciated. :good:

If you need an icon or Banner created let me know.
Nice work!

so now if i broke my USB port i can lock bootloader with this?Yes?
Nexus 4

ADB over wireless
I think this will be a very useful application for anybody requiring to make changes when on the road, or away from one's main computer.
Running ADB over WiFi should be a great addition to anybody's 'tool kit', I for one, look forward to making use of this application.
Many thanks for bringing this to all of us at XDA.
Thank you!

this apps is awesome make adb over wifi easier

Nice
extremewing said:
Free for XDA members and as a thank you for all the information, tools and roms XDA Developers has provided over the years here is something I created that makes it easy to connect adb over tcpip to multiple Android devices. Get rid of the wires!
One click to switch adb on all usb connected devices to tcpip.
One click to switch adb on all tcpip connected device back to usb.
Auto discovery of the devices listening on tcpip.
The application consists of two parts. "Helper.jar" to run on the pc and "Helper.apk" for the device.
View attachment 2455389Helper.jar
- Installs the Helper.apk on the device.
- Attempts to switch adb on the device to use tcpip.
- Sends broadcast messages to look for devices on the network.
- Initiates an adb connection over tcp to any ip that responds to the broadcast.
- Provides a button to switch all usb devices to tcpip.
- Provides a button to switch all tcpip devices to usb which also uninstalls the helper.apk file, leaving no "junk" on the device.
View attachment 2455388On the device, Helper.apk
- Checks and shows if the adb port was indeed opened
- Listens and responds to udp broadcasts from Helper.jar.
Some android devices will work without root but if you get a red message from the helper on the device, you will need to root it to enable adb in tcpip mode. The rooted method to set adb to use tcpip is used in case the device is rooted.
If you like the tool and want to contribute, please feel free to buy the app on the Play store. The attachment contains exactly the same files for free.
Feedback is welcome and I hope someone finds this useful!
Adrian
Click to expand...
Click to collapse
Nice tool Bro :good:

Thank you for the Christmas gift. I'm on HTC DNA and I am rooted but I get the red port closed message about root required.
No request for root occurs in supersu from this app.

rayjr13 said:
Thank you for the Christmas gift. I'm on HTC DNA and I am rooted but I get the red port closed message about root required.
No request for root occurs in supersu from this app.
Click to expand...
Click to collapse
Same issue here, on my rooted Xperia J. No entry regarding this apk's request for root is found in Super-SU's logs, whatsoever.

Wow, thanks for all the comments!
The helper on the device does not use or need su and ONLY does the following:
1) Checks if the adb tcp port was indeed opened on the device (by creating a tcp connection attempt to it)
2) Listens and then responds to a udp broadcast from the java app.
In future, it could do more.
All the work is done over the USB cable (or WiFi to switch back) using adb from the java app.
In essence, the java app executes the following abd commands to each device (both the "rooted" and non rooted methods are attempted each time):
To turn ON tcpip mode:
adb -s <devicename> tcpip 5555
adb -s <devicename> shell su -c 'setprop service.adb.tcp.port 5555'
To turn OFF tcpip mode:
adb -s <devicename> usb
adb -s <devicename> shell su -c 'setprop service.adb.tcp.port -1'
Please explain a bit more what is happening when the red message appears?
Is the device connected over USB and appearing in the left hand list on the java app?
Perhaps post the output from the java app when you press Switch to WiFi.

darkmatthew said:
so now if i broke my USB port i can lock bootloader with this?Yes?
Nexus 4
Click to expand...
Click to collapse
This app needs you to be able to first connect the USB and is intended to make it easier to work with lots of devices at the same time. For a rooted device without USB / damaged USB, any ADB to WiFi switching app on the play store should work to get adb onto WiFi and then, yes, you should be able to execute your required adb commands.

Thank you in advance for this very important tool!
extremewing said:
This app needs you to be able to first connect the USB and is intended to make it easier to work with lots of devices at the same time. For a rooted device without USB / damaged USB, any ADB to WiFi switching app on the play store should work to get adb onto WiFi and then, yes, you should be able to execute your required adb commands.
Click to expand...
Click to collapse
I have a HTC One, 4.3 Sense 5.5, ( 3.62.771.3 ), and need to reset it back to stock. My USB port doesn't function when the phone is on.
(Works OK in fastboot mode) - and I need to be S-off, then S-on again (locked, remove tampared via revone, moonshine,
or rumrunner) but all those require USB adb. and I can't do that.
So I'll try this and let you know how it goes.

spereree said:
I have a HTC One, 4.3 Sense 5.5, ( 3.62.771.3 ), and need to reset it back to stock. My USB port doesn't function when the phone is on.
(Works OK in fastboot mode) - and I need to be S-off, then S-on again (locked, remove tampared via revone, moonshine,
or rumrunner) but all those require USB adb. and I can't do that.
So I'll try this and let you know how it goes.
Click to expand...
Click to collapse
Please note, this app also requires USB ADB to start off.

Tried it...
extremewing said:
Please note, this app also requires USB ADB to start off.
Click to expand...
Click to collapse
OK, so I've tried it, and it seems like it can only pick up an ongoing ADB WiFi connection but I'm sure I'm doing something wrong.
Remember; I can't use USB debugging coz my usb doesn't work when the phone is on. so USB debugging is off, and there is no point using it. I'm using this as an alternative to restore back 100%.
(1) I pushed the apk file to the phone, using "WiFi File explorer pro"
(2) I installed it using "APK installer"
(3) Ran Helper.jar
(4) Opened an already installed WiFi ADB app on my phone, and established a connection (granted SU first)
(5) ran your app, "ADB over wifi helper" - it picked up the connection (showed green, " ... listening on port 5555 ... ", etc)
Back to the Helper.jar, all it does is saying "Searching - Hello to 255.255.255.255" "Timeout"
I was assuming it would have automatically connected it for me (say running a command like "adb connect ip.address:5555" )
or am I getting this wrong?
I kept the path to my android sdk
****Also, I used the mini sdk (It's quite popular, so I'm assuming most users will have this) and I'm missing the "platform-tools" folder. I just have fastboot and adb,exe and some dll files. So, can you provide a link we could get the required "platform-tools" folder alone? (zipped) ****
However, when I connect manually via command prompt, "adb connect ip.address:5555" the Helper.jar automatically detects it, and the option to Switch devices to USB appears (which I will not use, personally)
But the "Searching" cycle still continues.
Also, what is the use of the large text entry form below the "Searching" indication?
Again, thanks for this tool!!!
P.S. imagine a user trying to do what is said in this thread, but doesn't have a functioning USB port to use adb with, and has to result with your app (alongside another WiFi adb app) - This will fill the gap! as in ANYONE can recover / flash roms, etc, even if you have a broken USB port!!!

spereree said:
Back to the Helper.jar, all it does is saying "Searching - Hello to 255.255.255.255" "Timeout"
I was assuming it would have automatically connected it for me (say running a command like "adb connect ip.address:5555" )
or am I getting this wrong?
Click to expand...
Click to collapse
This is not wrong. After the helper.apk was running on the device, and showing you the port was open, the jar app should be able to discover it. Are both the pc and device connected to the same wifi access point, and that access point allows the two to talk? I assume so based on your later comments. What OS version?
spereree said:
I kept the path to my android sdk
****Also, I used the mini sdk (It's quite popular, so I'm assuming most users will have this) and I'm missing the "platform-tools" folder. I just have fastboot and adb,exe and some dll files. So, can you provide a link we could get the required "platform-tools" folder alone? (zipped) ****
Click to expand...
Click to collapse
Just point the app to the folder containing the adb executable.
spereree said:
However, when I connect manually via command prompt, "adb connect ip.address:5555" the Helper.jar automatically detects it, and the option to Switch devices to USB appears (which I will not use, personally)
But the "Searching" cycle still continues.
Click to expand...
Click to collapse
Searching will always continue. Something is either blocking the udp broadcast or the device is not allowing helper.apk to get them.
spereree said:
Also, what is the use of the large text entry form below the "Searching" indication?
Click to expand...
Click to collapse
That is a log of what the app is doing

extremewing said:
Are both the pc and device connected to the same wifi access point, and that access point allows the two to talk? I assume so based on your later comments. What OS version?
Click to expand...
Click to collapse
I'm on Windows 8.1 x64
and both devices are on the same network (I'm using my PC as the hotspot via a program called connectify. I'm using a USB 3G dongle for internet.
Just point the app to the folder containing the adb executable.
Click to expand...
Click to collapse
So that means I've done that OK...
Searching will always continue. Something is either blocking the udp broadcast or the device is not allowing helper.apk to get them.
Click to expand...
Click to collapse
I believe that might be the problem, but I don't see where that issue comes from...
Also as an addition, When I connect adb over WiFi on my phone, and I list all devices, I see my phone (as an IP address) but with "unauthorized" next to it (please search on the this issue for more info)... This was a brick wall I hit, when I was trying to get my phone 100% to stock, to send it to repairs for my USB issue... MEaning I can't run any shell commands, etc... via ADB... I was hopping this app could find a way around that?

spereree said:
I'm on Windows 8.1 x64
and both devices are on the same network (I'm using my PC as the hotspot via a program called connectify. I'm using a USB 3G dongle for internet.
So that means I've done that OK...
I believe that might be the problem, but I don't see where that issue comes from...
Also as an addition, When I connect adb over WiFi on my phone, and I list all devices, I see my phone (as an IP address) but with "unauthorized" next to it (please search on the this issue for more info)... This was a brick wall I hit, when I was trying to get my phone 100% to stock, to send it to repairs for my USB issue... MEaning I can't run any shell commands, etc... via ADB... I was hopping this app could find a way around that?
Click to expand...
Click to collapse
You have more than one thing going on here.
1) The program you mentioned "connectify" *may* be blocking the broadcast for discovery to work.
2) The "unauthorized" message is due to an out of date adb on the pc. You should upgrade to the latest version in order to connect to newer android devices. Note that you would also need to accept a permission prompt on the android screen.
3) I am also thinking you need to enable USB debugging for anything to work properly when executing adb commands (even over wifi with a faulty usb port).
4) If you get it back to stock, you may want to see if the USB issue you have is fixed.
5) You may also actually use fastboot to flash it back to stock?

Hi, Thanks for the reply.
I'll try all the options and get back to you.
extremewing said:
4) If you get it back to stock, you may want to see if the USB issue you have is fixed.
5) You may also actually use fastboot to flash it back to stock?
Click to expand...
Click to collapse
As for getting back to stock, I would also love to remove the tampered and "unlocked"
warnings from the top, so that I can take it back to repairs under warranty.
So actually ADB over WiFi need to work flawlessly as if I connected the USB cable,
This is so that when rumrunner is run on the device, no problems should be encountered.
Even after multiple reboots (hence, this application should load ASAP when Android booted.)

This tool is so awsome.
Saved alot of time here.
Tyvm

New version out soon
Since there are nearly 1000 downloads, I was going to bring out a new version I've been working on and I wanted some feedback or thoughts about what you would like to see.
The new version at the moment will give you these new features in the JAR app:
- Improved: device lists that will allow you to multi-select devices to perform actions on
- New: list of all apps on all devices (replaces the "console" at the bottom)
- New: Install an APK from your PC onto all selected devices
- New: One click uninstall of multiple apps on all selected devices
- New: One click enable / disable of multiple apps on all selected devices
Is there anything else one would want to do on all devices?

[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.