After Root.
Install on your phone.

RECOMMENDED / ROOT → BAR → SYSTEM INSTALLER

The native installation route after Root

AutoRoot v4 documents unsigned BAR installation after its Root notification, plus local Root helpers and a package format. This app follows that native package approach. “Recommended” is this project’s guidance for the checked environment, not BlackBerry certification or proof that every Root method works. AutoRoot author’s documentation.

Computer-free daily use is established separately from computer-free first installation. Q20 and Passport installation evidence includes commands sent over trusted Root SSH to the phone’s installer; it does not establish a complete phone-only first-install flow.

01 / FIRST INSTALL

Choose your installation route

Root means system administrator access. A Root marker, working SSH, a terminal icon and the ability to install a BAR are separate requirements. Confirm any first-use system installation or storage permission prompts normally on the phone.

Advanced: AutoRoot v4 terminal bootstrap

Not rooted? Start with desktop preparation.

Installation needs final SUD success and the matching installed version. A 120-second timeout or completed message is insufficient; keep an unknown task for inspection.

02 / BACK UP, ENABLE, CHECK

After installation, follow four steps

This describes the candidate workflow. Keep your SIM, number and system dialer; your carrier's plan still applies. The SIM needs VoLTE provisioning and normal LTE data service.

1. Check the phone and choose a backup location

   Open the app and confirm the model, OS, current SIM and check results. Choose an SD card or internal storage. Originals are saved and read back for verification before changes are allowed.

2. Choose “Activate VoLTE” and wait for the current task

   Read and confirm the operation. Submitted work continues in the phone's background; closing the app does not cancel it. Reopening queries the same task. Do not reinstall.

3. Restart normally when prompted

   Restart from the power menu and unlock. Wait for the system Root success notification, then open the app once. Do not repeatedly tap an unresponsive icon; the waiting page cannot run if the OS refuses launch. Checks run automatically inside the app. Passport network policy changes may require another restart.

4. Test outgoing calls, incoming calls, audio and LTE yourself

   Call out with the system dialer, then receive a call from another phone. Keep each connected for at least two minutes, then make one more outgoing call. Confirm audio in both directions and LTE / 4G throughout, then record the result. The app does not dial for you; IMS registration alone does not establish working calls.

A call record applies only to the current SIM, boot and payload version. Power off before changing SIMs. Recheck after a SIM change, restart or version change. Test SMS, number display and long standby separately too.

03 / KEEP THE ORIGINALS

Where should backups go?

SD card: prefer an available separate copy

A mounted card that passes write and readback checks can hold original backups. Keep it inserted until installation finishes. Afterward, keep another copy elsewhere if possible.

Internal storage: usable, but still on the same phone

Internal storage is available without an SD card. It helps local restoration but does not protect against loss of the phone, storage failure or files becoming inaccessible when the OS cannot start. You can export to an SD card later.

Use the exact export location shown in the app

Internal exports are under /accounts/1000/shared/documents/BB10-VoLTE/; SD card exports are under /accounts/1000/removable/sdcard/BB10-VoLTE/. Each task has its own subdirectory. Keep original backups and receipts. A redacted diagnostic report cannot replace original backups.

04 / UPDATES & RESTORATION

Update, disable or restore

Payload updates and app BAR upgrades are separate

The app's update check and offline ZIP import update runtime components and adaptation payloads. The publisher's signature is verified. If an online check fails, use a trusted offline package from the corresponding release. Bundled installation payloads and offline packages need no online download; registration and calls still require the carrier network.

Upgrading the interface app itself uses a new BAR with the same application identity. Follow the Release requirements, replace it through an existing installation entry point and verify the actual app version. A completed ZIP update does not mean the BAR was upgraded.

Finish restoration before removing the app

Use disable and restore, rollback or full uninstall from management. Restart normally and continue the same task when prompted. Uninstall can require staged restarts; removed files do not prove restoration has been verified. Deleting the home-screen icon alone does not restore service configuration or remove Root.

If a task is interrupted, files are unknown or backups conflict, keep the original task and files. Recheck or export a report first. Restoration requires ownership and verification evidence; repeated installation is not a way to overwrite unknown state.

Mobile and the new desktop manager use management protocol 2. Old r14 / r15 / r16 desktop clients cannot fully manage the new payload; use a newer manager matching the phone service protocol. If an older client is rejected, upgrade it and follow the release's disable, restore and normal-restart adoption steps.

05 / EVIDENCE & DEVICE SCOPE

Mobile app checks, by device

Checked on 2 November 2026, Asia/Shanghai. The latest UI build and the phone-only first-install experience need their own acceptance. An earlier isolated Passport wake/restart was accepted by the owner; its underlying cause is not claimed fixed. Long-term stability remains separate.

The historical scope is OS 10.3.3.3216 on Q10 SQN100-3, Q20 / Classic SQC100-2 and Passport SQW100-4. The nine model/carrier voice combinations recorded on r7 / r8 remain documented. r14 SMS validation covers Q20 with Unicom and Passport with Mobile; it does not extend to other SMS combinations.

Each new mobile build needs its own checks for installation, app-to-Root access, BAR upgrades, small and large screens, and restoration; the results above belong to their recorded v12/r18 combinations. Recognizing a model, compiling successfully or seeing an icon cannot establish those results.

Other Q10 / Classic variants can inspect the separate experimental route. Native hashes, ABI, SIM, network and restoration checks still apply; startup is manual and autostart stays off. SQC100-4 and other unvalidated variants are not listed as supported. Unknown devices can export a partial compatibility report. There is no control to ignore failed checks.

Read historical structured acceptance records · Read the detailed call checklist