Database Users

BackTrack 5 Security Distro on Thunderbolt

First, if you don't know what backtrack is, or what its used for I'd recommend the Ubuntu on Thunderbolt thread found here:
http://forum.xda-developers.com/showthread.php?t=1104983
He's done a lot of great work and its more refined.
Big thanks to anantshri, he's responsible for the .img and install.
{
"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"
}
Installations instructions:
Update your busybox (system/xbin) to the following version for chroot
Busybox http://db.tt/S9ERQvK
thanks twistedumbrella
Click to expand...
Click to collapse
download:
Terminal emulator-- I recommend Android Terminal Emulator by Jack Palevich
VNC Viewer-- e.g. android-vnc-viewer (free)
I also recommend 'Hacker's Keyboard'
Download the following three files and extract them with 7Zip.
======== FILE DOWNLOAD LINK================
DROPBOX links Bitlied for download count track
Alternate link from personal server.
Please do not create mirror : just want to keep a count on download's
PART 1 : Download Link : http://bit.ly/p1BT5
PART 2 : Download Link : http://bit.ly/BT5p2
PART 3 : Download Link : http://bit.ly/BT5p3
bt7z.001: http://www.mediafire.com/?x9cgxzdx84vc6uj
bt7z.002: http://www.mediafire.com/?xaoidipkg1o7vgo
bt7z.003: http://www.mediafire.com/?po3nznbxgvdipur
MD5 Sum : Thanks to DooMLorD
558ecb1f0e5feb1da86526df8761e6cc bt.7z.001
247842fd0d3ebb39454f76f4704d1537 bt.7z.002
f74d2f744434a7182b13287d9f8165e7 bt.7z.003
thanks anantshri
Click to expand...
Click to collapse
Once you have all the files downloaded, extract to a folder named 'bt'. You should see the following in the folder:
bt
bt.img
installbt.sh
startbt
stopbt
Copy the bt folder to your sdcard (file size~3.25GB)
Open up your Terminal emulator on your phone and cd to /sdcard/bt
type in the following
su
sh installbt.sh
If everything installed correctly you can proceed with the following
startbt --starts the backtrack service
stopbt --stops bt
bt --gives you backtrack command line
To access the gui
type ui in the bt shell to start the vncserver
killui stops it
your vnc server default login settings are going to be as follows
Address: 127.0.0.1 or localhost
Port: 5901
Password: 12345678
Additionally, you can use a workstation vnc viewer to log into bt via adb. Type the following into adb:
adb forward tcp:5901 tcp:5901
Ensure you have started the ui in your bt shell, then start your vnc client on your workstation. Connect to 127.0.0.1:5901 (or localhost:5901) and put in the 12345678 as the password.
You need to start the bt service every time you reboot with startbt, and need to reinstall bt when you flash a new rom (sh installbt.sh).
I'll continue to update this post with confirmations of what works and things we need to fix.
Optimization/tweaks:
type 'pico ~/bin/ui' in your bt shell, then adjust the resolution to 800x480
Working/Broken:
The big glaring omission is enabling monitor mode on the wireless adapter. What we need to make this happen is a stand alone installation (dual boot with android) and wireless chipset driver support. This is very unlikely to happen, especially when it runs with a relative degree of functionality in the android VM.
There are still many things that BackTrack can do, I encourage everyone to update their apt source.list and download the pieces they found missing, as well as to utilize the tools available-- this is still a very powerful toolkit.

dude this is legit. backtrack on linux is the ****.
i used to crack people's wireless with that ****, and do penetration tests all the time.
funny thing is im sonic wall certified lol. security my ass.

Samsuck said:
dude this is legit. backtrack on linux is the ****.
i used to crack people's wireless with that ****, and do penetration tests all the time.
funny thing is im sonic wall certified lol. security my ass.
Click to expand...
Click to collapse
is that section of backtrack functional though to actually get that use out of it? OP mentioned its not 100%.

Well played. BackTrack was our "secret weapon" when I worked in the tech field. Thanks.

I will be super excited if packet injection ever works.

If anyone is having issues extracting, you only need to use 7zip on the first file. This will extract all the files you need.
Ill be making some x server tweaks and compiling a list of functioning apps/hardware, will update the op.
Right now, wifi and 3g are working for data; I still need to test bt, but it should work. Ettercap fails when scanning for hosts, as do many other apps. Still a work in progress.
Sent from my ADR6400L using XDA App

this is sweet! i got it up and running in 20 minutes including extracting the files. i tried to install a few different versions of chrome and they all said wrong architecture. Im assuming this is an ARM issue because its not emulating x86 or x64 its just running on ARM. im curious if this will cause a problem for any other software that checks the processor, i didnt have time to check

Ok so, everything worked great until after "startbt". That works but once I go to start the ui, I get "Chroot: applet not found". Anyone know what I'm doing wrong?

can someone check if wireless card can be put in promiscuous mode? aka. capturing packages intended for someone else

kr0n1c said:
Ok so, everything worked great until after "startbt". That works but once I go to start the ui, I get "Chroot: applet not found". Anyone know what I'm doing wrong?
Click to expand...
Click to collapse
Did you update busybox?

cuguy said:
can someone check if wireless card can be put in promiscuous mode? aka. capturing packages intended for someone else
Click to expand...
Click to collapse
So I don't have an exact answer for you but I tried to run Aircrack-ng&Co and all I got was command not found.

I'm looking into that today, will also post a way to vnc in via adb, will make testing much easier.
Just got married, the honeydo lists have already started.. been juggling my time.
Sent from my ADR6400L using XDA App

Ke1evraTi said:
Did you update busybox?
Click to expand...
Click to collapse
I updated Busybox but still get the same error. To update BB, all I had to do was copy busybox.txt to /system/xbin correct?

i get to the command line fine, when I type ui I get command not found

Take away the .txt and overwrite the existing busybox in xbin. The browser appended .txt when you saved it and it should not be there.
For the ui, make sure you type bt first, so that you start the bt process. You should see [email protected]# or something similar instead of the usual #
Sent from my ADR6400L using XDA App

Gr8gorilla said:
i get to the command line fine, when I type ui I get command not found
Click to expand...
Click to collapse
Also, make sure you are su when you run startbt and bt

I actually fixed it by starting the command line and using vi to edit the /usr/bin/startvnc file, changed the resolution then exported the USER=root, I then used the command startvnc and it worked fine. Ui however did not work at all.

Gr8gorilla said:
I actually fixed it by starting the command line and using vi to edit the /usr/bin/startvnc file, changed the resolution then exported the USER=root, I then used the command startvnc and it worked fine. Ui however did not work at all.
Click to expand...
Click to collapse
Glad you got it worked out.
Additional way to connect to bt in op. Using adb should make troubleshooting much easier. Testing bt and promiscuous now
Additionally, you can use a workstation vnc viewer to log into bt via adb. Type the following into adb:
adb forward tcp:5901 tcp:5901
Ensure you have started the ui in your bt shell, then start your vnc client on your workstation. Connect to 127.0.0.1:5901 (or localhost:5901) and put in the 12345678 as the password.
Click to expand...
Click to collapse
Optimization/tweaks:
type 'pico ~/bin/ui' in your bt shell, then adjust the resolution to 800x480
Click to expand...
Click to collapse

Updated OP, we can't enable monitor mode on the wireless chipset, its running on a VM and there isn't driver support for it. This limits our ability to some extent, but there are still many useful tools in bt

this is DISGUSTING!!!
can't wait to try this out in the morning after work, MAJOR PROPS!

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

Android Accessibility Settings?

Hello - I'm trying to set up remote access of my android head unit to monitor system vitals remotely.
I have an Xtrons head unit (MCU Version: T8.3. 19-94-14-E06101-190118) and am struggling to get any remote access Apps to function fully. Apparently, I need to enable a setting on the accessibility setting, but I can't find these?
Nearly all apps (Team Viewer, etc) allow the connection and allow me to move a mouse around the screen however non allow me to 'click' remotely. The App AnyDesk has been the most helpful with their development team providing access to a universal plugin that will supposedly enable the functionality, however it requires access to the device's accessibility settings. Does anyone know how to access this?
The below post raised a simial question but remained unanswered: https://forum.xda-developers.com/an...essibility-settings-lost-android-8-1-t3906920
Android Version:
8.1.0
MCU Version:
T8.3. 19-94-14-E06101-190118
System Version:
V9.3.1_20181128.105007_HC2-FD
https://www.dropbox.com/s/znppnvmt1jc5pha/IMG_4652.PNG?dl=0
{
"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"
}

dale_oxford said:
Hello - I'm trying to set up remote access of my android head unit to monitor system vitals remotely.
I have an Xtrons head unit (MCU Version: T8.3. 19-94-14-E06101-190118) and am struggling to get any remote access Apps to function fully. Apparently, I need to enable a setting on the accessibility setting, but I can't find these?
Nearly all apps (Team Viewer, etc) allow the connection and allow me to move a mouse around the screen however non allow me to 'click' remotely. The App AnyDesk has been the most helpful with their development team providing access to a universal plugin that will supposedly enable the functionality, however it requires access to the device's accessibility settings. Does anyone know how to access this?
The below post raised a simial question but remained unanswered: https://forum.xda-developers.com/an...essibility-settings-lost-android-8-1-t3906920
Android Version:
8.1.0
MCU Version:
T8.3. 19-94-14-E06101-190118
System Version:
V9.3.1_20181128.105007_HC2-FD
https://www.dropbox.com/s/znppnvmt1jc5pha/IMG_4652.PNG?dl=0
Click to expand...
Click to collapse
I have been given the following advice from Xtrons (the device reseller), as they say, the model is now discontinued and won't forward on any support inquiries to the manufacturer.
"After entering "adbon "in the factory set and opening ADB, you can apply on the machine by yourself directly."
Does this mean "adbon" is the password to access the factory settings, or are they saying that I need to set up an ADB connection to the HU via a computer?
Many thanks

dale_oxford said:
I have been given the following advice from Xtrons (the device reseller), as they say, the model is now discontinued and won't forward on any support inquiries to the manufacturer.
"After entering "adbon "in the factory set and opening ADB, you can apply on the machine by yourself directly."
Does this mean "adbon" is the password to access the factory settings, or are they saying that I need to set up an ADB connection to the HU via a computer?
Many thanks
Click to expand...
Click to collapse
ADBON is the password for the factory settings, to get ADB activated... but this does not allow you to edit the accessibility settings, because the entry is hidden by manufacture.
With activating ADB on your device you are able to run console commands on your PC via ADB on your unit.
Code:
adb shell settings put secure enabled_accessibility_services [package name/service name]
You can try the app "Accessibility Settings Shortcut" app from play store. But I guess you have to activate it after each reboot.
If your unit is rooted you also can use Tasker with Secure Settings app to get this done on each boot.

rigattoni said:
ADBON is the password for the factory settings, to get ADB activated... but this does not allow you to edit the accessibility settings, because the entry is hidden by manufacture.
With activating ADB on your device you are able to run console commands on your PC via ADB on your unit.
Code:
adb shell settings put secure enabled_accessibility_services [package name/service name]
You can try the app "Accessibility Settings Shortcut" app from play store. But I guess you have to activate it after each reboot.
If your unit is rooted you also can use Tasker with Secure Settings app to get this done on each boot.
Click to expand...
Click to collapse
Hello Rigattoni,
Thank you so much for this advice. I’ve installed a number of ‘Accessibility Settings Shortcut’ apps from the PlayStore as some seemed incompatible. This has allowed me to many system changes but hasn’t solved the problem.
Do you know what specific setting the AnyDesk plugin is asking to be modified? I’ve looked through all of the settings I can but can’t see what it would need? I would very much prefer that I don’t have to ADB the device as I am MAC only and have no experience in performing this task.
Where would the AnyDesk Control Setting be within the accessibility settings?
Below are a few photos which might help:
1 - MCU Version.
2 - What the application requires to run (prompt).
3 - Application error (on opening).
https://i.ibb.co/mNwC1pP/IMG-4665.jpg
https://i.ibb.co/gSYjRcL/IMG-4652.jpg
https://i.ibb.co/C66FCY2/IMG-4653.jpg
On a separate note, I found in the setting that I could run my HU as a higher resolution and now it looks a lot better!

@dale_oxford,
Sorry I don´t use this AnyDesk application, so no advice possible from my side.
ADB is available for MAC too... so if you want to get this fixed....
Assuming the setting is persisted, you just need to do it once.
Laptop and unit just need to be in the same WiFi network and ADB available on your laptop.
Setup instructions --> https://www.xda-developers.com/install-adb-windows-macos-linux/

rigattoni said:
@dale_oxford,
Sorry I don´t use this AnyDesk application, so no advice possible from my side.
ADB is available for MAC too... so if you want to get this fixed....
Assuming the setting is persisted, you just need to do it once.
Laptop and unit just need to be in the same WiFi network and ADB available on your laptop.
Setup instructions --> https://www.xda-developers.com/install-adb-windows-macos-linux/
Click to expand...
Click to collapse
Thank you.
I appreciate that you may have no experience with the particular App, but I too have limited experience with Android. I hoped that with your experience you may have a gut feeling as to what the dialogue box was advising?
I’ve read though this tutorial and wanted to check something before proceeding:
1. Will a USB to USB cable work ok as both devices (laptop and the HU) only have female connections? Hopefully this will work without additional software?
2. In the code that you provided, where can I find the specifics which you listed as options? What is the “package name/ service name”? adb shell settings put secure enabled_accessibility_services [package name/service name]
Can you please direct to me some of the commands which would be applicable in solving this problem maybe?
Many thanks,
Dale

dale_oxford said:
Thank you.
I appreciate that you may have no experience with the particular App, but I too have limited experience with Android. I hoped that with your experience you may have a gut feeling as to what the dialogue box was advising?
I’ve read though this tutorial and wanted to check something before proceeding:
1. Will a USB to USB cable work ok as both devices (laptop and the HU) only have female connections? Hopefully this will work without additional software?
2. In the code that you provided, where can I find the specifics which you listed as options? What is the “package name/ service name”? adb shell settings put secure enabled_accessibility_services [package name/service name]
Can you please direct to me some of the commands which would be applicable in solving this problem maybe?
Many thanks,
Dale
Click to expand...
Click to collapse
Dale,
you need to use WiFi for it.
Get the unit to exact the point with the error message.
Open the Commandline Box in the ADB folder and type:
Code:
ADB connect 192.***.***.*** (put in the IP-Address of your unit instead)
ADB shell
top
You will get some output in the CMD.
press the "q" on your keyboard to quit the refresh of the CMD.
Post a screenshot of the CMD in here.
Hopefully we can find the name of the needed accessibility.
If we found the name you just connect again both (laptop and unit) to the same WiFi, open again the CMD on your laptop and use the following commands:
Code:
ADB connect 192.***.***.*** (put in the IP-Address of your unit instead)
adb shell settings put secure enabled_accessibility_services [package name/service name] <-- The package name of the app without brackets.
exit
exit

rigattoni said:
Dale,
you need to use WiFi for it.
Get the unit to exact the point with the error message.
Open the Commandline Box in the ADB folder and type:
Code:
ADB connect 192.***.***.*** (put in the IP-Address of your unit instead)
ADB shell
top
You will get some output in the CMD.
press the "q" on your keyboard to quit the refresh of the CMD.
Post a screenshot of the CMD in here.
Hopefully we can find the name of the needed accessibility.
If we found the name you just connect again both (laptop and unit) to the same WiFi, open again the CMD on your laptop and use the following commands:
Code:
ADB connect 192.***.***.*** (put in the IP-Address of your unit instead)
adb shell settings put secure enabled_accessibility_services [package name/service name] <-- The package name of the app without brackets.
exit
exit
Click to expand...
Click to collapse
Hi - Thanks for this this looks great. I haven’t been able to try this yet as I’ve been away from my car.
in the meantime I’ve done a little research into this and my understanding was that I would still need to initially do a USB connection in order to activate the ADB mode. Please have a look at the attached tutorial:
https://futurestud.io/tutorials/how-to-debug-your-android-app-over-wifi-without-root
Are you saying that I can connect via Wi-Fi without having to use a USB cable in the first instance or will I still need to do this? If so with a USB male to male cable work given that both my computer and the android headset have female connectors?

dale_oxford said:
Hi - Thanks for this this looks great. I haven’t been able to try this yet as I’ve been away from my car.
in the meantime I’ve done a little research into this and my understanding was that I would still need to initially do a USB connection in order to activate the ADB mode. Please have a look at the attached tutorial:
https://futurestud.io/tutorials/how-to-debug-your-android-app-over-wifi-without-root
Are you saying that I can connect via Wi-Fi without having to use a USB cable in the first instance or will I still need to do this? If so with a USB male to male cable work given that both my computer and the android headset have female connectors?
Click to expand...
Click to collapse
Once again...
You are not able to use a female/female USB cable to get connected to your unit as there is not real OTG available on the unit.
You need to use WiFi as I wrote.
It works exactly the same way.

ADB : Missing popup debugging authorization permission

Hello !
I bought this radio head unit on AliExpress (it's the D version) : https://fr.aliexpress.com/item/1005002212221194.html?spm=a2g0o.productlist.0.0.f7057521b4ZITh&algo_pvid=d9ce368e-ff00-495f-a529-2a731b4c08e1&algo_exp_id=d9ce368e-ff00-495f-a529-2a731b4c08e1-3&pdp_ext_f=%7B%22sku_id%22%3A%2212000019285936076%22%7D&pdp_npi=2%40dis%21XPF%2122714.0%219313.0%21%21%215390.0%21%21%402103250d16614764984578815e1966%2112000019285936076%21sea&curPageLogUid=tE6VyZxSAnJY
Device Name : ums512_1h10_Natv
Build Number : QP1A.190711.020 release-keys
I developed an app for it and I need to debug this app with ADB.
How do I proceed ?
For now, I activated the developper mode and the FileTransfer mode in default USB settings then I connected a male-to-male cable to the 2 USB ports but the device does not pop up the debugging authorization permission.
Thanks for your help !

Kapoe said:
Hello !
I bought this radio head unit on AliExpress (it's the D version) : https://fr.aliexpress.com/item/1005002212221194.html?spm=a2g0o.productlist.0.0.f7057521b4ZITh&algo_pvid=d9ce368e-ff00-495f-a529-2a731b4c08e1&algo_exp_id=d9ce368e-ff00-495f-a529-2a731b4c08e1-3&pdp_ext_f=%7B%22sku_id%22%3A%2212000019285936076%22%7D&pdp_npi=2%40dis%21XPF%2122714.0%219313.0%21%21%215390.0%21%21%402103250d16614764984578815e1966%2112000019285936076%21sea&curPageLogUid=tE6VyZxSAnJY
Device Name : ums512_1h10_Natv
Build Number : QP1A.190711.020 release-keys
I developed an app for it and I need to debug this app with ADB.
How do I proceed ?
For now, I activated the developper mode and the FileTransfer mode in default USB settings then I connected a male-to-male cable to the 2 USB ports but the device does not pop up the debugging authorization permission.
Thanks for your help !
Click to expand...
Click to collapse
I think you are using your unit at a power supply on bench?
May be a solution to use ADB with WiFi to connect to the unit. This is what I use... and on top I use SCRCPY to see the screen on my laptop.
Just give it a try and connect to the unit with the IP of the unit, instead trying to use the USB cable which is mostly not registered.

Hi,
thank you for your reply !
I'm not using the unit on bench but directly in the car, but I can connect it to home wifi
The device address on wifi is 192.168.88.105.
So, I used this command :
$ adb connect 192.168.88.105:5555
cannot connect to 192.168.88.105:5555: Aucune connexion n’a pu être établie car l’ordinateur cible l’a expressément refusée. (10061)
The result is "connection refused" with error code 10061.
Any idea to fix this ?

Kapoe said:
Hi,
thank you for your reply !
I'm not using the unit on bench but directly in the car, but I can connect it to home wifi
The device address on wifi is 192.168.88.105.
So, I used this command :
$ adb connect 192.168.88.105:5555
cannot connect to 192.168.88.105:5555: Aucune connexion n’a pu être établie car l’ordinateur cible l’a expressément refusée. (10061)
The result is "connection refused" with error code 10061.
Any idea to fix this ?
Click to expand...
Click to collapse
Did you activate "Open Net ADB" in the developer settings?
On the other side... May be you first need to activate ADB in your device. See this posting: https://forum.xda-developers.com/t/how-to-adb-when-head-unit-has-usb-a-sockets.3879769/post-83181523
You really need to use Terminal Emulator on your head unit. Other emus may not work.
What app are you developing?
Edit: If you are connected to the home WiFi and you have a good battery charger added to the car battery, then you can use SCRCPY sitting on your sofa... I don´t want to miss this tool...

rigattoni said:
Did you activate "Open Net ADB" in the developer settings?
On the other side... May be you first need to activate ADB in your device. See this posting: https://forum.xda-developers.com/t/how-to-adb-when-head-unit-has-usb-a-sockets.3879769/post-83181523
You really need to use Terminal Emulator on your head unit. Other emus may not work.
What app are you developing?
Edit: If you are connected to the home WiFi and you have a good battery charger added to the car battery, then you can use SCRCPY sitting on your sofa... I don´t want to miss this tool...
Click to expand...
Click to collapse
I didn't found "Open Net ADB" in the developer settings...
But I activated ADB as you indicates, and it's better :
$ adb connect 192.168.88.105:5555
failed to authenticate to 192.168.88.105:5555
I tried to copy my adb.pub in /data/misc/adb/adb_keys but I need root access...
I installed apk like OneClickRoot, KingRoot, Kingo Root with no success in rooting

Kapoe said:
I didn't found "Open Net ADB" in the developer settings...
But I activated ADB as you indicates, and it's better :
$ adb connect 192.168.88.105:5555
failed to authenticate to 192.168.88.105:5555
I tried to copy my adb.pub in /data/misc/adb/adb_keys but I need root access...
I installed apk like OneClickRoot, KingRoot, Kingo Root with no success in rooting
Click to expand...
Click to collapse
Did you use ADB on a Windows-PC?
$ adb looks like a terminal thing....
Code:
C:\ADB\scrcpy-win64-v1.19>adb connect 192.168.178.41
* daemon not running; starting now at tcp:5037
* daemon started successfully
connected to 192.168.178.41:5555
BTW... for getting root, you may give a screenshot from "About tablet" or similar, which shows the MCU and firmware you are using,

Kapoe said:
I didn't found "Open Net ADB" in the developer settings...
But I activated ADB as you indicates, and it's better :
$ adb connect 192.168.88.105:5555
failed to authenticate to 192.168.88.105:5555
I tried to copy my adb.pub in /data/misc/adb/adb_keys but I need root access...
I installed apk like OneClickRoot, KingRoot, Kingo Root with no success in rooting
Click to expand...
Click to collapse
From Android 4.2, every ADB device needs to be authorized for a computer to connect. This is done for security. So when a USB is connected a prompt comes asking to authorize the device when USB debugging is set. But does not happen for WIFI ADB.
So the workaround is to connect the device by USB, accepting the machine always. Then when the Wireless ADB is tried, it should work.

rigattoni said:
Did you use ADB on a Windows-PC?
Click to expand...
Click to collapse
Yes, and the "failed to authenticate" message is because, as TorstenH said, my ADB device is not authorized for my computer.
TorstenH said:
From Android 4.2, every ADB device needs to be authorized for a computer to connect. This is done for security. So when a USB is connected a prompt comes asking to authorize the device when USB debugging is set. But does not happen for WIFI ADB.
So the workaround is to connect the device by USB, accepting the machine always. Then when the Wireless ADB is tried, it should work.
Click to expand...
Click to collapse
That's the problem...
In my first message I explained I activated the developper mode and the FileTransfer mode in default USB settings then I connected a male-to-male "data cable" to each 2 USB ports but the device does not pop up the debugging authorization permission.
That's why I tried to copy the adb.pub file from my computer to my device but unsuccessfully due to root rights needed.
I search how to root my device but I found nothing...
{
"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"
}

Kapoe said:
Yes, and the "failed to authenticate" message is because, as TorstenH said, my ADB device is not authorized for my computer.
That's the problem...
In my first message I explained I activated the developper mode and the FileTransfer mode in default USB settings then I connected a male-to-male "data cable" to each 2 USB ports but the device does not pop up the debugging authorization permission.
That's why I tried to copy the adb.pub file from my computer to my device but unsuccessfully due to root rights needed.
I search how to root my device but I found nothing...
Click to expand...
Click to collapse
You could try to enable USB debugging after! you connected your PC. That helped on some smartphone FWs.
And here are some more approaches you could try:
Can't authorise android device in USB debugging mode
I am trying to use a Samsung Galaxy S6 Edge for debugging an android app. I've downloaded and installed the Samsung USB driver but when the device appears in android studio it says the device is
android.stackexchange.com

There is already another thread regarding ADB with these TS10 units.
Seems that they did not find a reliable solution.
TS10 ADB offline
Hi all. I´m trying to get ADB to work with my TS10/Topway-style headunit. Since I can´t put the unit in device mode I can´t connect a USB cable to it. I´ve managed to start ADB listening over WiFi using the internal ADB Shell hidden in the...
forum.xda-developers.com
Even rooting the device is nearly impossible. Search for TS10 root and you find a lot of threads for that.
Not the best unit to work on.

I finally solved my problem by rooting my device and setting manually /data/misc/adb/adb_keys
Thank you for your support !

Kapoe said:
I finally solved my problem by rooting my device and setting manually /data/misc/adb/adb_keys
Thank you for your support !
Click to expand...
Click to collapse
Maybe you can describe how you did this to help other users.

BE CAREFUL ! USE AT OWN RISK !
Firmware update used to root my device :
https://disk.yandex.ru/d/rIBtRseJuNvbTg --> TS10 / TS10.1.2_20220507.095321_THEME1-Rooted.zip