How to use every bluetooth CAT dongle with RepeaterBook – now without root!

Last time I showed you how you can use any bluetooth CAT dongle with RepeaterBook. This time I show you how to do the same but without the need to get root access. Everything is the same except how we get to that file and get it back to the device.

Prerequisites

  • You have ADB (Android Debug Bridge) installed
  • You have a USB cable for your phone
  • You have enabled ADB debugging for your phone (if not: just google it)
  • You have Android Backup Extractor on you Computer Get it HERE.

Extracting the file

First of all we need to get the file com.zbm2.repeaterbook_preferences.xml from the device.
To do that we just type in a command line: adb backup -noapk com.zbm2.repeaterbook

Confirm to backup on your device. You mustn’t use a password in order to follow my tutorial.

You will find a file called backup.ab in your current folder. We need to get a backup.tar file out of it.
Now we type: java -jar abe.jar unpack ~/backup.ab backup.tar

After that you will find a file called backup.tar. You will find the file we are looking for under the subfolder apps. Open the file and edit it as I explained in an earlier post. Save it and update the .tar archive. The exact way depends on the Software you use. Try googling it if you have now idea.

Getting the changed file to the device

First we need to get a new .ab file from the .tar file. To accomplish that we type: java -jar abe.jar pack backup.tar backup-new.ab 

Restore the file to your device: adb restore backup-new.ab

 

Just confirm that you want to restore. That’s it.

 

If you have difficulties following these steps: Write a comment and wait. A will write it in a more clean way the next days.

Just the usual note: I take NO responsibility if you are a not capable of using your brain and/or your computer and then damage something. Following this tutorial could kill cat babies if used wrong and without caution.

How to use every bluetooth CAT dongle with RepeaterBook

By default RepeaterBook only works with CAT dongles that have a specific MAC address. I bought a cheap dongle from ebay, but the Android App RepeaterBook didn’t recognize it. So I decided to look into the apps files. I found a file containing settings of the app. There I could set the MAC address:

<?xml version=’1.0′ encoding=’utf-8′ standalone=’yes’ ?>
<map>
<boolean name=”PREF_DISPLAY_5GHz” value=”false” />
<boolean name=”PREF_DISPLAY_APCO25″ value=”false” />
<boolean name=”PREF_DISPLAY_WIDE_VER2″ value=”false” />
<string name=”PREF_DISPLAY”>1</string>
<string name=”PREF_LAST_MAC_ADDRESS”>20:16:05:19:36:33</string>
<boolean name=”PREF_DISPLAY_2M” value=”true” />
<boolean name=”PREF_DISPLAY_23CM” value=”false” />
<string name=”PREF_MILE_KILOMETRE”>km</string>
<boolean name=”PREF_ENABLE_AUTOCONNECT” value=”true” />
<boolean name=”PREF_DISPLAY_TV” value=”false” />
<string name=”PREF_MANUAL_LOCATION”>JO41BN</string>
<boolean name=”PREF_DISPLAY_1_25m” value=”false” />
<boolean name=”PREF_DISPLAY_6M” value=”false” />
<boolean name=”PREF_DISPLAY_33CM” value=”false” />
<boolean name=”PREF_DISPLAY_DMR” value=”true” />
<boolean name=”PREF_DISPLAY_10M” value=”true” />
<boolean name=”PREF_DISPLAY_ECHOLINK” value=”false” />
<boolean name=”PREF_DISPLAY_ANALOG” value=”true” />
<boolean name=”PREF_DISPLAY_ALLSTAR” value=”false” />
<string name=”PREF_MAX_DISTANCE_VER2″>500</string>
<boolean name=”PREF_DISPLAY_DSTAR” value=”false” />
<string name=”PREF_SORT_BY_VER3″>35</string>
<boolean name=”PREF_ENABLE_SCREENON” value=”false” />
<boolean name=”PREF_DISPLAY_WIRES” value=”false” />
<boolean name=”PREF_DISPLAY_24GHz” value=”false” />
<boolean name=”PREF_DISPLAY_4M” value=”false” />
<string name=”PREF_BLUECAT_RADIO”>1</string>
<boolean name=”PREF_DISPLAY_IRLP” value=”false” />
<boolean name=”PREF_DISPLAY_YSF_VER2″ value=”false” />
<boolean name=”PREF_DISPLAY_13CM” value=”false” />
<boolean name=”PREF_DISPLAY_WIRES_X” value=”false” />
<boolean name=”PREF_DISPLAY_70CM” value=”true” />
<boolean name=”PREF_DISPLAY_9CM” value=”false” />
<boolean name=”PREF_DISPLAY_10GHz” value=”false” />
<boolean name=”PREF_AUTO_LOCATION” value=”false” />
</map>

As you can see, <string name=”PREF_LAST_MAC_ADDRESS”>20:16:05:19:36:33</string> contains the MAC address. Just get the MAC address of your devices using apps like “Bluetooth Viewer LITE” and put it into the file. You need root access to edit that file. The file is located under: /data/data/com.zbm2.repeaterbook/shared_prefs/com.zbm2.repeaterbook_preferences.xml

Now I can finally set my FT-857D’s frequency using my smartphone. 😀

How to automatically remove all EXIF information from photos inside a folder

I just found a few photos I’d like to use on the Internet and I wanted to remove all the EXIF information from it.

EXIF information contains the camera used and some of the settings and even where you made the photo on cameras with GPS.

I didn’t want to remove it from every single photo, so I made a script for it:


#!/bin/bash
#This script deletes all EXIF information from any .JPG or .jpg photo in a folder. It is needed to install ImageMagick to use the mogrify command.
#NOTE: YOUR EXIF WILL BE LOST! DO A BACKUP IF YOU NEED IT!
# This program comes with absolutely no warranty, to the extent permitted by applicable law.
cd ~/YOUR_PICTURE_FOLDER/
clear
echo Now locating pictures and deleting EXIF information
find ./*/ -name '*.JPG' | xargs mogrify -strip
clear
echo step 1 of 4 done...
find ./*/ -name '*.JPG~' | xargs rm
clear
echo step 2 of 4...
find ./*/ -name '*.jpg' | xargs mogrify -strip
clear
echo step 3 of 4...
find ./*/ -name '*.jpg~' | xargs rm
clear
echo step 4 of 4...
#The above lines containing 'rm' remove the .JPG~ or .jpg~ files, which you get when you close the program before finishing. Just run it again to get rid of them.
echo 'We are done! You can now use your photos on the Internet! Press any key to continue.. :)'
read -n 1
echo
exit

This simple script needs the program ImageMagick installed to have the mogrify command available.

Use it at your own risk.

New model of the Raspberry Pi available!

Hi there,

the Raspberry Pi foundation has just announced the new Model Raspberry Pi 2 B+

What’s new?

  • A 900MHz quad-core ARM Cortex-A7 CPU (~6x performance)
  • 1GB LPDDR2 SDRAM (2x memory)
  • Complete compatibility with Raspberry Pi 1

This new device will be compatible to Windows 10 and this will be a free version of Windows, but I still prefer Raspbian. I think you can’t do all the same with Windows… There are already so many tutorials for Linux… I think that won’t come for Windows.

Source: Raspberry Pi Foundation http://www.raspberrypi.org/raspberry-pi-2-on-sale/

Hamnet over VPN with OpenWRT-Router

ENGLISH VERSION BELOW

Ich wollte unbedingt ins Hamnet. Komfortabel per WLAN mit all meinen Geräten. Also habe ich meinen Router mit OpenWRT so eingerichtet, dass er sich mit dem VPN verbindet. Denn eine HF-Verbindung habe ich leider nicht.

Allerdings gibt es dabei noch ein paar Sachen zu beachten.

Ich werde jetzt nicht auf das einrichten einer VPN-Verbindung eingehen, sondern nur darauf, was speziell für das Hamnet notwendig ist. Für das einrichten einer VPN-Verbindung gibt es genug Anleitungen. (Aber ppp-mod-pptp muss installiert sein.)

Nachdem das VPN eingerichtet wurde, muss erst einmal die Firewall Zone geändert werden. Stelle sie z.b. auf “HamnetVPN”. Dazu gibst du bei unspecified -or- create: einfach “HamnetVPN” ein. Danach muss in der Config-Datei /etc/config/network die Zeile option auth 'pap' hinzugefügt werden, denn die Verbindung wird unverschlüsselt aufgebaut. OpenWRT versucht standarmäßig das verschlüsselte CHAP zu nutzen. Am einfachsten kann die Datei mit nano editiert werden. Falls noch nicht installiert, wird das mit opkg update gefolgt von opkg install nano getan.

Die Firewall-Zone "HamnetVPN".
Die Firewall-Zone “HamnetVPN”.

Die Datei öffnen wir nun mit nano /etc/config/network und fügen die Zeile hinzu. Danach sollte unser Eintrag so aussehen:

 

config interface ‘hamnet’
option proto ‘pptp’
option server ‘ruhrlink.dyndns.org’
option password ‘q<$djre9sk#)2zTB’
option auth ‘pap’
option username ‘dc7ia’
option defaultroute ‘0’

Natürlich ist das Passwort nicht echt! 😉

(Die Reihenfolge der Optionen ist egal.)

Wir speicern mit Strg+O und schließen mit Strg+X.

Anschließend müssen wir die Datei /etc/ppp/options.pptp editieren. Dort fügen wir nomppe hinzu. Die Datei sieht dann so ähnlich wie diese aus:

noipdefault
noauth
nobsdcomp
nodeflate
idle 0
# mppe required,no40,no56,stateless
maxfail 0
refuse-chap
nomppe

Die Zeile, welche mit mppe beginnt, muss wie oben mit dem # auskommentiert werden. Dann speichern wir und starten den Router neu. Jetzt müsste man unter Interfaces sehen, dass das VPN eine 44.*-IP-Adresse bekommen hat:

Das Hamnet-VPN ist erfolgreich verbunden.
Das Hamnet-VPN ist erfolgreich verbunden.

Anschließend muss noch die statische Route gesetzt werden:

Die statische Route unter OpenWRT eingerichtet für das 44.0.0.0/8 Netz.
Die statische Route unter OpenWRT eingerichtet für das 44.0.0.0/8 Netz.

Diese statische Route bewirkt, dass die Pakete fürs Hamnet auch dahin kommen, und nicht ins Internet geschickt werden. Dies machen wir unter Network -> Static Routes.

Jetzt sollte dein Router dir das Hamnet über WLAN und LAN zur Verfügung stellen. 🙂

Denke aber daran, dass du deine VPN vor unbefugter Nutzung schützen musst. Dein WLAN sollte verschlüsselt sein.

Vielen Dank an Florian, DF2ET. Er hat mir gut geholfen. So doll, dass es nun funktioniert. 🙂

ENGLISH

(Hint: Ask for the VPN vpn@ruhrlink.org )

I really wanted to use Hamnet. Comfortable via Wi-Fi with all my devices. So I have set up my router with OpenWRT so that it connects to the VPN automatically. I can’t use RF because I don’t see the repeater.

However, there’s still a few things to note.

I will not go into detail how to set up a VPN connection, but only to what is specifically required for the Hamnet. For setting up a VPN connection there is enough instructions online. (But make sure you have ppp-mod-pptp muss installed.)

After the VPN was set up once the firewall zone needs to be changed. For example, set it to “HamnetVPN”. Just type in field unspecified -or- create: the name of the firewall zone, for example “HamnetVPN”. Then you have to change the Config-file /etc/config/network and add line option auth 'pap', because we neeed an unencrypted connection. OpenWRT tries to use encrypted CHAP as default. The easiest way to edit this file is to use nano. If not installed yet that can be done with opkg update and opkg install nano.

The firewall zone & quot; & quot ;. HamnetVPN The code firewall zone “HamnetVPN”.

We open the file using nano /etc/config/network and add the line. Then our entry should look like this:

 config interface ‘Hamnet’
option proto ‘pptp’
server option ‘ruhrlink.dyndns.org’
option password ‘q<$djre9sk#)2zTB’
auth option ‘pap’
option username ‘dc7ia’
option default route ‘0’

Of course is it not my real password! 😉

(The order of options does not matter.)

We save with Ctrl + O and end with Ctrl + X .

Then we need to edit the file /etc/ppp/options.pptp . There we add nomppe . The file will look something like this:

noipdefault
noauth
nobsdcomp
nodeflate
idle 0
# Mppe required, no40, no56, stateless
maxfail 0
refuse-chap
nomppe

The line beginning with mppe must be commented out as above with the # . Then we save and restart the router. Now would you see at menu point "interfaces" that the VPN has a 44.* IP address.

 

The Hamnet -VPN is connected successfully. The code Hamnet VPN is connected successfully.

 

The static route must be set:

The code static route set up under OpenWRT for the 44.0.0.0/8 network.

 

This static route causes packets for Hamnet also to get to, and not be sent to the Internet. We do this under Network – & gt; Static Routes.

Now your router you should give you Hamnet access via WLAN and LAN. 🙂

But remember that you need to protect your VPN from unauthorized use. Your WLAN should be encrypted.

Thanks to Florian, DF2ET. He helped me well. So great that it works now. 🙂