Back to the overviewInstall OkcarOS on
jactivelte
Installing a custom recovery using
Install OkcarOS on
Samsung Galaxy S4 Active
jactivelte
WARNING: The provided instructions are for OkcarOS 18.1. These will only work if you follow every section and step precisely.
Do not continue after something fails!
Do not continue after something fails!
Basic requirements
- Read through the instructions at least once before actually following them, so as to avoid any problems due to any missed steps!
- Make sure your computer has
adb
andfastboot
. Setup instructions can be found here. - Enable USB debugging on your device.
- Make sure that your model is actually listed in the “Supported models” section here (exact match required!)
- Boot your device with the stock OS at least once and check every functionality.
WARNING: Make sure that you can send and receive SMS and place and receive calls (also via WiFi and LTE, if available), otherwise it won’t work on OkcarOS either! Additionally, some devices require that VoLTE/VoWiFi be utilized once on stock to provision IMS.
- LineageOS is provided as-is with no warranty. While we attempt to verify everything works you are installing this at your own risk!
Important Information
NOTE: The following instructions require a machine running Windows 10 build 17063 or newer.
Samsung devices come with a unique boot mode called “Download mode”, which is very similar to “Fastboot mode” on some devices with unlocked bootloaders. Odin is a Samsung-made tool for interfacing with Download mode on Samsung devices. The preferred method of installing a custom recovery is through Download Mode – rooting the stock firmware is neither necessary nor required.
Installing a custom recovery using Odin
NOTE: If this device’s install instructions already had you download Odin/Enable OEM Unlocking earlier in the installation process, you can skip the steps for enabling OEM Unlock, as well as for downloading and extracting the drivers and Odin.
- Download Lineage Recovery. Simply download the latest recovery file, named
recovery.img
- Open a Command Prompt in the folder where the file was downloaded, and TAR the file by running
tar --format=ustar -cvf recovery.tar recovery.img
.Tip: Make sure to not accidentally name the filerecovery.img.img
when file name extensions are hidden.Tip: You can open a command prompt in any folder by right-clicking on empty space while holding Shift and selecting “Open Command Prompt here” or “Open PowerShell window here” from the context menu.Important: Other recoveries may not work for installation or updates. We strongly recommend to use the one linked above! - Power off the device, and boot it into download mode:
- With the device powered off, hold Home + Volume Down + Power.
- Now, click the button that the onscreen instructions correlate to “Continue”, and insert the USB cable into the device.
- Download and install the necessary drivers.
- Download the newest Samsung drivers from here. You will need to create a Samsung account and login to download them.
- Install
SAMSUNG_USB_Driver_for_Mobile_Phones.exe
.
- Download this version of Odin.
- Extract “Odin_3.13.1.zip”.
- Run
Odin3 v3.13.1
found in the newly extracted “Odin_3.13.1” folder. - Check in the top left of the Odin window that you see a valid device, it will show up as something like
COM0
.Tip: TheCOM
port, or the number succeedingCOM
, may be any valid number. - In the left side of the Odin window, you will see an “Options” tab, click it, and then un-check the “Auto Reboot” option.
- Check the box labeled next to the button labeled “AP”, and then click the “AP” button.
- In the menu that pops up, select the newly downloaded (or built) custom recovery
.tar
or.tar.md5
.
Tip: The filename may vary depending on your device, and the version of your custom recovery. - In the menu that pops up, select the newly downloaded (or built) custom recovery
- Click “Start”. A transfer bar will appear on the device showing the recovery image being flashed.
NOTE: The device will continue to display
Downloading... Do not turn off target!!
even after the process is complete. - Unplug the USB cable from your device.
- Manually reboot into recovery, this may require pulling the device’s battery out and putting it back in, or if you have a non-removable battery, press the Volume Down + Power buttons for 8~10 seconds until the screen turns black & release the buttons immediately when it does, then boot to recovery:
- With the device powered off, hold Home + Volume Up + Power. Let go of Power immediately when the phone vibrates, but keep holding the two other keys.
NOTE: Be sure to reboot into recovery immediately after installing the custom recovery. If you don’t the custom recovery will be overwritten on boot.NOTE: If your recovery does not show the OkcarOS logo , you accidentally booted into the wrong recovery. Please start at the top of this section!
Installing OkcarOS from recovery
- Download the OkcarOS installation package that you would like to install or build the package yourself.
- (Optionally): If you want to install Google Apps add-on package (use the
arm
architecture), you can download it from here.
- (Optionally): If you want to install Google Apps add-on package (use the
- If you are not in recovery, reboot into recovery:
- With the device powered off, hold Home + Volume Up + Power. Let go of Power immediately when the phone vibrates, but keep holding the two other keys.
- Now tap Factory Reset, then Format data / factory reset and continue with the formatting process. This will remove encryption and delete all files stored in the internal storage, as well as format your cache partition (if you have one).
- Return to the main menu.
- Sideload the OkcarOS
.zip
package but do not reboot before you read/followed the rest of the instructions!- On the device, select “Apply Update”, then “Apply from ADB” to begin sideload.
- On the host machine, sideload the package using:
adb -d sideload filename.zip
.Tip: Normally, adb will reportTotal xfer: 1.00x
, but in some cases, even if the process succeeds the output will stop at 47% and reportadb: failed to read command: Success
. In some cases it will reportadb: failed to read command: No error
oradb: failed to read command: Undefined error: 0
which is also fine.
Installing Add-Ons
NOTE: If you don’t want to install any add-on (such as Google Apps), you can skip this whole section!
NOTE: Add-ons aren’t signed with OkcarOS’s official key, and therefore when they are sideloaded, Lineage Recovery will present a screen that says
Signature verification failed
, this is expected, please click Continue
.WARNING: If you want the Google Apps add-on on your device, you must follow this step before booting into OkcarOS for the first time!
- Click
Apply Update
, thenApply from ADB
, thenadb -d sideload filename.zip
for all desired packages in sequence.
All set!
Once you have installed everything successfully, you can now reboot your device into the OS for the first time!
- Click the back arrow in the top left of the screen, then “Reboot system now”.
NOTE:
The first boot usually takes no longer than 15 minutes, depending on the device.
If it takes longer, you may have missed a step, otherwise feel free to get assistance.
Get assistance
After you’ve double checked that you followed the steps precisely, didn’t skip any and still have questions or got stuck, feel free to ask on our subreddit or in #OkcarOS on Libera.Chat.