How to make Galaxy S4 work with Pioneer radio. Switching selinux to permissive

A year ago, I became the proud owner of the Pioneer SPH-DA100 AppRadio 2


radio tape recorder . I bought the radio tape recorder initially to connect a smartphone, because I wanted to implement a navigator with traffic jams, play music from a phone, etc. But the main goal of course is Yandex.Navigator. At that time, I was the proud owner of the Samsung Galaxy S3 I9300. Of course, the supplied pioneer software immediately went to the trash and an excellent ARLiberator product was found . This program smartly allows you to control the phone from the radio, displaying a full screen phone. ScreenStandby was added to it in order to prevent the phone from discharging. To this was added the mhl adapter from the Samsung Galaxy S4.


It is very important to use the original adapter, Chinese adapters immediately begin to crash, snow and green the screen. Initially, I wanted to use Samsung’s wireless AllShare Cast Dongle:


After lengthy tests, it turned out that if you open the navigator and turn on the music at the same time, the connection starts to fail and the songs stutter every 10-15 seconds. Well, for the work of Arliberator, you need Root. All this bunch worked perfectly and pleased me until a week ago I broke my phone on the corner of the tiled floor. It was decided to switch to the Galaxy S4.

1. It was bought and flashed with the latest Samsung firmware based on android 4.4.2.
2. Received Root.

But nothing worked. Arliberator did not connect to the machine, and could not pass the built-in performance tests. In particular, the test “Creating a virtual device” failed. After a long search, it turned out that in the new Android, the status of SELinux was changed from a more free Permissive to a strict Enforcing, which, in turn, there are still restrictions with root. The setenforce 0 command did not help switch SELinux. Samsung also snapped their KNOX protection system. All this was a definite plus for ordinary users, bringing Android in security closer to iOS, but it did not satisfy my goals. After long searches and attempts, an algorithm was developed to get rid of this scourge. You can perform the described actions further at your own risk. The author of the article is not responsible for turning your phone into a brick.

Yes, and another point: the very first firmware of something non-original causes the KNOX counter to fire, which cannot be reset at this time in any way. The operation of the counter, of course, causes the nullification of the Samsung warranty.


1. The stock firmware with the cut out KNOX and the added Root (available on was flashed through ODIN 3.07 in the PDA field. Do not forget about all the wipes, including factory reset.

To switch SELinux, the only working way for me was to update the modified kernel.

2. You need to flash CWM Recovery. The usual ROM Manager can not do here, because it does not work on the I9500:

a) Download recovery_version_.img from .
b) Rename the downloaded file to recovery.img
c) Pack it in a tar image using TAR_MD5_PACKAGER (also on 7Zip did not help here.
d) Flash through ODIN in the PDA field.

3. Install the Omega Files program and download the modified stock kernel for the I9500 using it. The kernel is assembled from Samsung sources, at least the developer says so.

4. Flash downloaded archive via CWM without unpacking. Again, not forgetting about wipes.

As a result, almost stock firmware was obtained with root and SELinux status - permissive.

The bundle ARLiberator + ScreenStandby was complemented by the excellent Car Dashboard program , which replaces the Launcher for the duration of the connection and is convenient for poking while driving in the radio.

The algorithm I described is certainly concise, but each of these actions is chewed on many resources, but I have not found such a combination anywhere. I hope this information will be useful to those who are going to use this radio, as well as for those who have the desire to switch SELinux mode on the new Samsung.

A small addition about the counter:
Perhaps with the word counter I could be misleading. In fact, the counter was before. In the I9500, this is already a flag that switches to 1 with unofficial intervention. Now KNOX software is responsible for this, which is present not only in rom but also in the bootloader, and as far as is known, it does not allow downgrading the bootloader at the hardware level.

Also popular now: