Database Users

[RELEASE] One-Click UnBrick updated 10july11

Try One-Click UnBrick... If that doesn't work:
Try "3 button combo".. If that doesn't work:
Try a "301k Factory Mode jig"... If that doesn't work:
Try UnBrickable Mod http://forum.xda-developers.com/showthread.php?t=1236273 (if available on your platform)
If you require additional help, send me a private message, we can work something out.
Background
I've been working on stopping the bricking problem on our phones for a while now.
Ever tried JTAG unbrick recovery?--superhuman soldering skills no longer required for JTAG
Developing methods to recover bricks without JTAG - I keep this updated with current information as it develops.
ALL JIG VALUES here! --this will give you some resistor values to try
Altered water damage indicators --um... just in case you lick your battery and need warranty replacement
The Galaxy S Hack Pack--A compilation of resources for Galaxy S Phones.
I wanted to write some software which will help the user to understand what they are doing.. So I began the Heimdall One-Click project. http://code.google.com/p/heimdall-one-click/ Heimdall One-Click is not yet finished, but the Unbrick is complete. Heimdall One-Click is based on binaries from another Open-Source project, called Heimdall by XDA member Benjamin Dobell.
About One-Click UnBrick
This Software:
Will work on all Samsung devices which use Odin3
Is a single, portable executable
Is the first one-click anything for our devices on Linux
Works on Mac
Works on Windows
Is open source
Is programmed in Java
Deploys and installs Heimdall for your OS
Is super easy to use.... Only one button!
Demonstration video:
Image captured on Ubuntu 11.04:
{
"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"
}
This software is completely safe. It is a part of my Heimdall One-Click project. I wanted to release this to work out any cross-platform difficulties which may be encountered before I release Heimdall One-Click.
Instructions
1. Copy OneClick.jar to your Desktop-- or any other folder on your computer, It won't work on a network share.
2. Double click. -- As long as you have Java installed On Linux and Mac you are up and running.
For some versions of Windows as a work around to UAC (User Access Control, the annoying popups), a executable called "OneClickLoader.exe" has been deployed to the same folder as OneClick.jar. It is important that you do not rename OneClick.jar until after runnning OneClickLoader.exe
3. right click OneClickLoader.exe and select "Run as Administrator" -- Setup should be run-of-the-mill.
Fate-Silver said:
It works with all softbricked condition basically.
Stuck in a boot loop?
Is it still able to boot into CWM(Recovery Mode) or Download Mode.
If it's still able to go back into Download Mode, you don't need this software.
Just turn your Captivate into the Download Mode and flash back to STOCK Eclair or Froyo using Odin 1 Click or whatever similar.
Click to expand...
Click to collapse
Problems and Comments
If you would like to comment on something post here on XDA
If you're unsure of something, post here on XDA
If you have a show-stopping bug, please use this form: http://code.google.com/p/heimdall-one-click/issues/entry
This is a list of all bugs reported: http://code.google.com/p/heimdall-o...+Priority+Milestone+Owner+Summary&cells=tiles
I am very interested in feedback. If you would like to test this, just put your phone into download mode and click the unsoft brick button. It will simply reboot your phone. It will not flash any firmware and it does not have the capability to do anything except release the locks which prevent a phone from booting if they are present.
Click Here to Download One-Click UnBrick 10July11 from GoogleCode
You will need Java installed on your computer: Do you have java?
Disclaimer: All materials presented are for informational purposes. This content is not an authorization, advertisement, nor a suggestion to flash your phone with custom firmware. In no event shall I be held liable for any direct, indirect, incidental, spcial, exemplary, or concequential damages, including but not limited to loss of data, business interruption or damage to equipment. This information is released AS-IS with no written or express warranty or liability.

Linux users, mark this file as executable:
Code:
chmod +x OneClick.jar
All platforms: Double Click to run, OR, right click and open with Java, OR from command line:
Code:
java -jar OneClick.jar
Releases
-Version1.0 3July11 initial release
-Version1.b 4July11 fixes windows 7 & Vista UAC. Thanks to Roddreick for windows UAC workaround binary.
-Version1.IIX 5july11 fixes Winodws 7 and Vista. Adds countdown to non-imperative notifications. Adds real-time monitoring to determine if dependencies are actually required on Windows, rather then blindly installing. Since windows is such a PITA, this was alot of work. This version will work if you have Java installed and OneClick.jar on your computer (no network shares) on Windows XP, Windows Vista, Windows 7, Mac OS X Snow Leopard, and all Debian based Linux distributions including Ubuntu and Mint.
-Version 1.SVNR33 9july11 Much smaller package size, decreased by 5 megs. Fixes browser launching on Linux/mac. Decreases logging level to 1. Adds Log to temp folder at level 4. Adds optional donations to Heimdall or One-Click. Adds Windows Problem Resolution Center.
-Version 1.FINAL 10July11 Fixed UAC issues, File may now be renamed on Windows, Left launcher as alternate method, added linux asthetics, fixed driver link
Major Operating Systems requiring testing
Mac OS-X Leopard
Mac OS-X Snow Leopard
Mac OS-X Lion
Linux Ubuntu 32
Linux Ubuntu 64
Linux Mint
Linux Debian
Windows XP
Windows Vista
Windows 7
note: If you are having problems with drivers, This is caused by an invalid USB Device ID in the ROM installed on the phone.
If you'd like to contribute to the next version
Testing on your platform is as simple as putting your phone into download mode and clicking the button. It will simply reboot the phone if the phone is not bricked.
Grab the code from the SVN: checkout http://heimdall-one-click.googlecode.com/svn/trunk/
You can modify the code with NetBeans: http://netbeans.org/downloads/
If you come up with a positive change, I'll add you to the SVN as a contributor or a committer to ensure you get credit for your work.
I'm always looking to make a new version. Please give feedback.

wow this looks neat...i will definitely fire it up next time i brick my epic! great job AdamOutler!
edit: tested and it did kick my epic out of download mode in windows
if the command above gives you issues on windows 7 then do the following:
click the start button
goto programs>accessories>
right click on 'command prompt' and select run as administrator
cd to your download folder (ie: cd c:\downloads\oneclick\)
then type 'java -jar OneClick.jar'
you should only have to do all of that the first time so drivers for heimdall can be installed correctly
AdamOutler is working a better solution for the windows crowd

Awesome will try it out went nesesary!

Gotta check this out it's probably gonna have to wait til tomorrow looks cool
Sent from my phone on vacation

Nice work man! Hope I don't have to try it out anytime soon, but I really appreciate the effort you've put into this and all your other projects.

A definite must-have, thanks for this!

awesome this makes me less stressed out when flashing! thanks!will use when necessary!

just as a heads up, not every environment will play nice with the "doube click to run" as the file is stored now on google code. if you're on linux, simply either chmod +x the file or do "java -jar ./OneClick.jar" to run it (assuming java is in your path). seems ubuntu (and derivatives, I guess) assume the jar file wants to be opened with archive manager by default, so set it to run with java beforehand (launched with sun java 6, didn't try openjdk)
add to that the application doesn't seem to reliably recognize heimdall 1.0.1 CLI... attempting to run it returns a blank version string but after updating to 1.0.2b it recognized it fine. not world-ending, but just something I thought you should be aware of.
I'm a bit more interested in your heimdall one-click attempts though, as I'd like to see something like that implemented for 2.2 (since not every captivate can go back to JF6 it seems)... I've been pointing people at the leaked JI6 odin one-click for now, as it contains all the necessary files and is usable on every device.
edit: looking a bit more over heimdall's implementation, does this simply run the "heimdall close-pc-screen" command in an easy to use GUI?

Kaik541 said:
just as a heads up, not every environment will play nice with the "doube click to run" as the file is stored now on google code. if you're on linux, simply either chmod +x the file or do "java -jar ./OneClick.jar" to run it (assuming java is in your path). seems ubuntu (and derivatives, I guess) assume the jar file wants to be opened with archive manager by default, so set it to run with java beforehand (launched with sun java 6, didn't try openjdk)
add to that the application doesn't seem to reliably recognize heimdall 1.0.1 CLI... attempting to run it returns a blank version string but after updating to 1.0.2b it recognized it fine. not world-ending, but just something I thought you should be aware of.
I'm a bit more interested in your heimdall one-click attempts though, as I'd like to see something like that implemented for 2.2 (since not every captivate can go back to JF6 it seems)... I've been pointing people at the leaked JI6 odin one-click for now, as it contains all the necessary files and is usable on every device.
Click to expand...
Click to collapse
True... I'll add that to the first post.
Heimdall one-click is operational. I'm working the kinks out of it with the one-click unbrick first. I've sucessfully flashed my phone on all three platforms using heimdall one-click. I don't feel comfortable releasing something like that without thorough testing. This is basically testing for my one-click platform.

can you do a write up on how to brick your phone, and the many ways to it.

Awesome work. Very good and very useful tool, Adam!

Stev3-o said:
can you do a write up on how to brick your phone, and the many ways to it.
Click to expand...
Click to collapse
Sure.. too easy.
Soft bricks:
Flash improper firmware which the system recognizes as improper
Prematurely terminate transfer
Flash with a bad cable
Hard Bricks:
Flash improper bootloaders
Flash mismatched versions of proper bootloaders
Flash bootloaders with a bad cable

AdamOutler said:
Sure.. too easy.
Soft bricks:
Flash improper firmware which the system recognizes as improper
Prematurely terminate transfer
Flash with a bad cable
Hard Bricks:
Flash improper bootloaders
Flash mismatched versions of proper bootloaders
Flash bootloaders with a bad cable
Click to expand...
Click to collapse
Quick question: Does the Odin 1-click flash the primary bootloader? I think I may have hardbricked my cappy tonight. I went from cognition beta 1 (2.3.3) with new bootloaders and one-clicked to 2.1 the phone made it to rfs and then froze. Now it will do nothing. You think I killed it? Thanks.

Coldskiesfullofblue said:
Quick question: Does the Odin 1-click flash the primary bootloader? I think I may have hardbricked my cappy tonight. I went from cognition beta 1 (2.3.3) with new bootloaders and one-clicked to 2.1 the phone made it to rfs and then froze. Now it will do nothing. You think I killed it? Thanks.
Click to expand...
Click to collapse
that's a question for Q&A.
You'd need to check it out with UART for any answers.

So if I read the op and the links right there still isn't a non jtag solution for hard bricks? I asked toys becuase it seemed that with refering to the herr bricks and what causes them as well that you have found a work around... I probably just misunderstand it though.
SIGNATURE : Life is like a box of captivates, you never know if your gps will work

AdamOutler said:
Sure.. too easy.
Hard Bricks:
Flash improper bootloaders
Flash mismatched versions of proper bootloaders
Flash bootloaders with a bad cable
Click to expand...
Click to collapse
Can this software fix the hard bricks? If yes.. too good, many thanks. You made the life less stressfull.

Haven't had to use it and hopefully never will but thank you Sir!

bigbyte.me said:
Can this software fix the hard bricks? If yes.. too good, many thanks. You made the life less stressfull.
Click to expand...
Click to collapse
NO. Hard Bircks are mainly because of wrong Bootloaders, if that the phone is unable to boot, so can't access it. If its HardBricked my guess is only Samsung can unbrickit. BTW new GB bootloaders are un-brickables. They now has the hability to re-download a ROM on Phone<---->PC Screen.

thanks, you are genius, huge help!

[Tool][Windows Only][Root] Android Reverse Tethering 3.19

Android Reverse Tethering for windows users.
Tethering is the ability to surf on your pc using the 3g of your phone
Reverse tethering is the opposite : surf on your phone using the ADSL of your PC. No Wifi or 3G connection required.
==>Troubleshooting (FAQ) <==
Since a lot of users don't read the full article before asking for help, I will start by this section !
Not yet compatible with Android 5. Work on progress. Don't ask me when it will be available
Android 4.3 and upper : You must install the Connectivity hack (see Connectivity hack section) before connect .
Android 4.3 and upper : You must connect your phone/tablet to a working wifi or 3g once after each boot before using reverse tethering !!!
This work only for rooted users and with Windows. Don't ask for linux or for some fruit operating systems !!!
The tool is not compatible with "CrossBreeder" , "adaway" or other tools that change the host file (removing localhost)
Tethering and reverse tethering (this tool) are not compatible at the same time, it's then not possible to turn your android phone as a wifi hotspot.
If your device is not listed in the "select a device" dropdow list:
Ensure Usb debugging is enabled. See "Before starting the tool" section
The ADB subsystem is sometimes not working properly. Click the "Kill ADB" button (on Tools)
Your device is perhaps not installed properly. See your device manufacturer. You can download a generic driver from google here : http://developer.android.com/sdk/win-usb.html.
Windows can detect your device as a "Media Transfer Protocol" (MTP) or "Picture Transfer Protocol" (PTP). When you connect the usb cable, you can receive an "Usb" notification. Click the notification to change this parameter. If one don't work, take the another one...
Click refresh or restart the tool to detect your device.
If the connection shutdown often, try another usb cable
Proxies problems :
Corporte proxy. The windows application is not able to traverse proxies.
The good news is that you can use some applications like FreeCap , sockscap and proxifier.
You must start the androidTool from one of these launchers, giving proxy adress and port.
Thanks "edgd1er" for the information.
Android 3G proxy. Even if 3g is desactivated, your provider (APN) proxy may still be used by applications.
The windows tool is not able to communicate with your provider proxy.
Note that only a few providers include a proxy. You must remove it manually.
The tool will give you informations on how to do it when detected.
Installation :
Unpack the zip file. This zip files contains the windows part, ADB and the android APK.
Before starting the tool :
You must install drivers for your device.
If you don't find drivers for your phone/tablet, check the Universal Naked Driver
Other interesting tool to install Adb and drivers (32/64) : [TOOL] ADB, Fastboot and Drivers - 15 seconds ADB Installer .
Some screenshots are availables in this thread to install the driver.
Ensure you have debugging enabled on your phone :
Settings > Applications > Development > USB Debugging > Turn On
Ensure you have root access AND SuperUser application installed.
Change the superuser settings (Menu -> Preferences -> Notifications part) :
Uncheck "Notifications" label to display "Do not show notification when an app is granted Su Permissions"
{
"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"
}
AndroidTool
The AndroidTool.exe is the windows part
The low level communication tool (ADB) is included in the zip file.
AndroidTool will try to find ADB in c:\android-sdk-windows\platform-tools\adb.exe
If not found he will use the provided one.
The first time you use the program :
If you want to use another version of ADB, clik "config" and in the first tab enter the path to the ADB
Select the DNS server to use in the right list. On complex system, some dns can be detected.
Start reverse tethering
Just click “Connect”.
If it's the first time you use the program, This will install the latest android package and the dependencies (busybox and redsocks).
The SuperUser process may ask you to allow “Usb tunnel”
If the android process crash after receiving superuser rights, close the windows program and start again.
The android interface (first tab) will show connections forwarded to windows.
Others tabs are just for debugging. Send the log on this thread in case of problem.
Start your browser
Google chrome will complain that no connection is available. Don’t care. That work.
Firefox , opera and dolphin don’t have problem with that !!!
The current version of the application can’t forward low level ICMP packet (PING).
From Android Os point of vue, there is no internet connection.
Command line prompt :
The windows tool is a "One click" application. Just click the "Connect" button.
But you can add parameters to directly connect when the program start.
Here are the supported commands : Device:xxxx (where xxxx is the device id), Connect, Disconnect, KillAdb, LogToClipboard, Show, Hide, Quit
Parameter sample : Device:123465789 Connect Hide
Create a second shortcut with Disconnect Quit parameters to stop connection and close the application.
Connectivity hack :
This will install some low level program to install a "fake" Wifi for browsers and google play market.
Don't worry, I didn't brick my phone and tablet during the development.
The Xposed framework author and me are not responsible for anything you do with your phone/tablet/rice cooker.
This work for android 4.X, but an experimental version of the Xposed framework for Gingerbread made by liudongmiao can be found here: http://forum.xda-developers.com/showthread.php?p=44034334#post44034334 (no support from my side)
On the windows program, go to tools tab and click "install hack"
Launch the Xposed Installer (you just installed) on your android and click on "Install/Update"
Go to the module tab and check the HackConnectivityService (see screenshot below)
Reboot the phone
Done!
This work for market but also for some other programs (some games,skype,hangouts...)
For older android 2.x or 3.x version :
The application want to have an active 3G or Wifi network interface.
Some market applications are tagged "Wifi" only.
To get around this problem, you can activate the 3G BEFORE starting reverse tethering,all the data will goes to the usb.
Tips : You can connect to some wifi hotspot not protected by a key.
It's only when you want to surf that the hotspot ask you a user/password.
But, at this point, we have an 'active' connection. Market download should work after starting reverse tethering.
Not fully working application but work if you install the HackConnectivityService on android 4.x:
Market download
Spotify
Skype. (not checked yet)
If someone know another one, post a reply !
History :
Version 3.19
Added some rights for sdcard access.
New windows icons.
Version 3.18
Fixed Xposed HackConnectivityService module. You must click "install hack" to update it
Small bug fix.
Version 3.17
Updated Xposed framework installer 2.4.1
Small bug fix.
For Linux ,Mac OS X , I recommand this guide (from @phamthanhnam ) : http://forum.xda-developers.com/showthread.php?t=2287494 .
This required entering a lot of manual commands on both android and the PC each time you want to connect (reserved to power "geek" users).
This work also for windows, but much more complicated, compared to this "One click" connect tool. I let user chose the solution he want...
I will not respond to email or private message. If you want support, post a reply on this forum.
Do you like this program ? Want to make a donation ? Send any amount to my paypal account (click the donate button on left)
Please read FAQ on top of the page before asking for help.
Older versions were removed (416611 downloads)

capslock66 said:
Unpack the zip file. This zip files contains the windows part, ADB and the android APK.
You MUST uninstall previous version. If you don’t find it, run a dos command prompt on the installation folder and enter this command : Adb uninstall service.tracetool
Ensure you have debugging enabled on your phone :
Settings > Applications > Development > USB Debugging > Turn On
Run the windows program : AndroidTool.exe
The first time you use the program, click on “Show Android interface”. This will install the package and the dependencies (busybox and redsocks).
The SuperUser process may ask you to allow “Usb tunnel”
To start tethering click “Connect”.
Again, The SuperUser process may ask you to allow “Usb tunnel”
If the android process crash after receiving superuser rights, close the windows program and start again. (It’s a beta)
The android interface will show connections forwarded to windows.
Start your browser
Google chrome will complain that no connection is available. Don’t care. That work.
Firefox , opera and dolphin don’t have problem with that !!!
The current version of the application can’t forward low level ICMP packet (PING).
From Android Os point of vue, there is no internet connection.
Market :
The search market work, but due to the same connection problem, it’s not possible to download. I hope Google will fix the market.
Click to expand...
Click to collapse
I was looking to get some internet access on alpha build of ics for galaxy tab... Hope this works..will try and let you know..thanks for the good work...
Sent from my GT-P1000 using XDA App

Great work. Tested this and it works pretty well (on HTC Aria CM7).

do you mean we need to connect the tablet to the PC using the USB cable then we can use reverse thethering thingy ?

Wouldn't the PC app like Connectify Me do this thing without all this?
☞★sent from drajax's Galaxy SL!!! *♂ツ

Wow thanks a million!, i hope we can download apps as well but i'll settle for apks for now, <3
---------- Post added at 08:14 PM ---------- Previous post was at 07:55 PM ----------
drajax said:
Wouldn't the PC app like Connectify Me do this thing without all this?
☞★sent from drajax's Galaxy SL!!! *♂ツ
Click to expand...
Click to collapse
it would, but this program uses a USB cable, connectify uses WiFi, so for us who don't have wifi routers or connectify we can use this

Galaxy S II (GT-I9100) on CyanogenMod 7.1, using SiyahKernel 2.2b6, doesn't work. Using Windows 7 x86, with correct drivers installed. Can't get past the step of clicking 'Show Android Interface'. Clicks, but nothing happens. No devices are listed within the program.

screamworks said:
Galaxy S II (GT-I9100) on CyanogenMod 7.1, using SiyahKernel 2.2b6, doesn't work. Using Windows 7 x86, with correct drivers installed. Can't get past the step of clicking 'Show Android Interface'. Clicks, but nothing happens. No devices are listed within the program.
Click to expand...
Click to collapse
If the device is not listed, it's not a problem related with reverse tethering. It's a driver or installation problem !

ldloh2 said:
do you mean we need to connect the tablet to the PC using the USB cable then we can use reverse thethering thingy ?
Click to expand...
Click to collapse
Yes, you just need to install the windows program then click connect.
It's a beta, market is not able to download.

capslock66 said:
If the device is not listed, it's not a problem related with reverse tethering. It's a driver or installation problem !
Click to expand...
Click to collapse
Elaborate? On your post it says:
Tested under:
Acer Iconia A500 (Taboonay 2.1)
Galaxy S (Cyanogen 7)
Galaxy S II
HTC Aria (CM7)
Click to expand...
Click to collapse
The device is listed. And I've got all appropriate drivers for my device installed?

Inspire 4G CM7, works
As a side note, I had ADB running when I started it & it didnt work. Killed all ADB sessions & relaunched, after that it worked like a charm.

screamworks said:
Elaborate? On your post it says:
The device is listed. And I've got all appropriate drivers for my device installed?
Click to expand...
Click to collapse
Did you enabled USB Debugging ?
Run a dos command prompt then enter this command :
Code:
cd\instfolder
adb devices
instfolder is the folder where you unzipped ReverseTethering.zip
Ensure you have adb.exe in that folder
You should see :
Code:
List of devices attached
xxxxxxxxxxx device
If not, try to re-install driver or test on another PC.

combustiblemonkey said:
As a side note, I had ADB running when I started it & it didnt work. Killed all ADB sessions & relaunched, after that it worked like a charm.
Click to expand...
Click to collapse
Better is to configure the application to use the already installed ADB program on your computer :
button config -> ADB sheet -> update path -> button save
Then restart the tool.

Working on Nexus S with MIUI. Opera browser and Market both work.
I was hoping to use it to avoid using my data while playing games or when installing games with huge downloads after installing, but that doesn't seem to be the case yet. I see I can add ports for forwarding, but how can I tell what port a game uses?

This was something i was waiting but i could not use the internet from pc.
I have SGS1, 2.3.6. I dont get any error messages. Clicking connect makes it connect but status column always not connected.
Im on company network. Which IP i will use? Which port i will use?

Kolero said:
I was hoping to use it to avoid using my data while playing games or when installing games with huge downloads after installing, but that doesn't seem to be the case yet. I see I can add ports for forwarding, but how can I tell what port a game uses?
Click to expand...
Click to collapse
Next version will detect automatically ports.
But it's still not possible do download from Market

yken said:
This was something i was waiting but i could not use the internet from pc.
I have SGS1, 2.3.6. I dont get any error messages. Clicking connect makes it connect but status column always not connected.
Im on company network. Which IP i will use? Which port i will use?
Click to expand...
Click to collapse
Beta 2 (+- 15 decembre) will be more stable. With automatic port detection.

serves to moto defy?

Why not just use virtual router on your pc?

Works like a charm on My Ideos X5 U8800.. Thx!

[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

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

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