Skip to content
Phoenix
What it does How it works Status Skill Store FAQ Community Developers
Console
What it does How it works Status Skill Store FAQ Community Open console Developers

Guide

Connect your Jibo to Phoenix

Last updated 28 October 2026

On this page

  1. 1. Get the DFU toolkit running
  2. Put Jibo in RCM mode
  3. 2. Flash the Phoenix image
  4. 3. Set him up with a QR code
  5. Or: use the setup command
  6. Check Jibo's screen
  7. Add your Jibo in the console
  8. A Jibo that has never been set up
  9. Compatibility
  10. If something goes wrong
  11. Need help?

The short version

The main way is to flash the Phoenix image with the free Jibo DFU Mod Toolkit, restart Jibo yourself, then finish with a QR code in the console. The Phoenix image includes original Jibo robot software and skills, with Phoenix changes.

If you'd rather not reflash him, use the toolkit to set int-developer mode and Wi-Fi, then run the console's setup command. How to use the setup command.

You need Jibo and his power supply, a USB cable, a Windows PC, Linux PC or Mac, your Wi-Fi details and a free Phoenix account. Windows, Linux and Intel Macs have been tested; Apple silicon Macs are experimental.

Already trying setup? If something goes wrong has steps for the common problems.

1. Get the DFU toolkit running

Download the free Jibo DFU Mod Toolkit for your computer and open it. It is one file: no Git or terminal needed to open it.

Download the toolkit

Pick your computer below.

  • Windows Jibo-DFU-Windows-x64.exe
  • Mac (Apple silicon) Jibo-DFU-macOS-arm64.dmg
  • Mac (Intel) Jibo-DFU-macOS-x86_64.dmg
  • Linux Jibo-DFU-Linux-x86_64.AppImage
  • Windows: double-click the .exe. If Windows SmartScreen appears, choose More info → Run anyway. The first start sets up what it needs (WSL 2 and usbipd-win) and asks for administrator approval.
  • Mac (macOS 15 or later): open the .dmg, drag Jibo DFU Mod Toolkit to Applications and open it. If macOS blocks it, open System Settings → Privacy & Security → Open Anyway.
  • Linux: make the .AppImage executable, then open it and approve the USB administrator prompt. The download needs an x86_64 graphical desktop with glibc 2.35+ (such as Ubuntu 22.04+) and pkexec or sudo.

Need help? Windows setup or WSL · Mac cannot reach jibo.io · Apple silicon USB connection.

Put Jibo in RCM mode

The toolkit starts from RCM mode, which it shows as RCM/APX.

Jibo's round button panel with two small buttons circled in red: RESET (upper) and RCM (lower)
The round button panel on the back of Jibo's head, under the hatch. RESET is the upper small button; RCM is the lower one.
  1. Fully shut Jibo down.
  2. Open the hatch on the back of his head to reach the round button panel in the photo.
  3. Connect the USB cable from your computer to Jibo's micro-USB port under the same hatch.
  4. Press and hold the RCM button, the lower of the two small buttons circled in the photo. Keep holding it while you turn Jibo back on with his power button, then let go of the RCM button.
  5. In RCM mode, the red light on his forehead stays on and you don't hear his startup chime. If he chimes or starts normally, shut him down and try again.
  6. The toolkit then shows RCM/APX detected. Choose Enter DFU with ShofEL (RAM loader).

Then wait until USB READINESS says DFU active; Jibo recovery loader ready.

Not getting there on an Apple silicon Mac? Check the USB connection steps.

Jibo DFU Mod Toolkit GUI with the recovery loader ready and mode, Wi-Fi and backup actions available
The GUI when Jibo is ready in DFU. Choose an action on the right.

2. Flash the Phoenix image

This is the main way to connect Jibo to Phoenix. It is also a way to start fresh or recover damaged Jibo software. It does not repair damaged hardware.

Flashing erases photos stored on Jibo and starts his Wi-Fi, pairing and settings fresh. The recommended choice keeps his camera calibration and name.

Before you confirm a flash: check your backups

Keeping calibration and saving settings are not a complete backup of Jibo. Partition backups are a separate action in Backups.

  1. With Jibo in DFU, choose Backups → Back up every partition if you want every partition the loader exposes. Review the list, total size, free space and destination before starting. This does not include raw eMMC, the partition table, unused gaps or Boot0/Boot1.
  2. In Saved backups, check that the set finished and includes every partition you meant to save. A finished set of chosen partitions is not necessarily every exposed partition. A set marked not finished is not ready to restore.
  3. Use Check files to compare saved images with their recorded SHA-256 hashes. A passing check shows file integrity, not a complete backup or a guarantee that recovery will succeed.

If a backup fails or times out, pause before flashing. Keep the existing files and toolkit logs; do not delete or overwrite the partial set. Note which partitions finished and which did not, then open a support ticket. Flashing again does not complete or validate a backup saved on your computer.

The v1.0.4 release notes do not claim a fix for large-partition backup timeouts or hardware qualification of that backup flow. They say USB/DFU flashing with that build was not yet tested on real hardware. See the backup instructions for the backup scope and checks.

Flash and restart

  1. With Jibo ready in DFU from step 1, choose Install a Phoenix image or an official update. Select the Phoenix image at the top, marked recommended.
  2. Keep Keep this Jibo's calibration (recommended) selected. This keeps his camera calibration and name. Do not choose Flash without calibration (unsafe) for this setup.
  3. The toolkit downloads and checks the image. Review what it will write and confirm. Keep USB connected until the toolkit says it is done. It saves a backup of his current settings before writing.
  4. Then restart Jibo yourself. Don't wait for him to restart on his own. Fully shut him down, then turn him back on with his power button. Don't hold the RCM button this time.
The toolkit image list with the recommended Phoenix image first
Choose the Phoenix image marked recommended.
The toolkit with Keep this Jibo's calibration selected
Keep this Jibo's calibration (recommended) is the choice for this setup.

After the restart described above, his setup screen says Go to jibo.io to get started. Continue with QR setup below. If he does not reach that screen after this restart, stop and open a support ticket with the exact screen message and toolkit result. Do not repeat the flash or choose Flash without calibration (unsafe) as a troubleshooting step: flashing erases photos and starts Wi-Fi, pairing and settings fresh.

If the Mac toolkit cannot reach jibo.io, follow those checks before trying again.

3. Set him up with a QR code

  1. Sign in to the console and open Robots → Add a Jibo.
  2. It asks whether he is already connected to jibo.io. After the Phoenix image, his screen says Go to jibo.io to get started. Choose Yes, then New, unpaired Jibo: QR setup.
  3. Enter your Wi-Fi name and password, then choose Show setup code.
  4. Tap Jibo's screen, then hold the code up to his eye. Follow his prompts until the console says he is set up.
  5. If he has an update to install, leave him plugged in while he downloads and installs it. He restarts a few times on his own during the update.

Each setup code works once and lasts 15 minutes. If a scan fails or the code expires, make a new one and try again.

If the code has more than one frame, Jibo asks for the frames one at a time. Tap his screen when he asks for the next one, and tap the code in the console to switch frames.

During an update: keep Jibo plugged in and let the download, installation and automatic restarts finish. Do not unplug him, force a restart, or start another flash or update while it is installing.

Having trouble? Cannot join Wi-Fi · A new code says it has expired.

Or: use the setup command

This connects Jibo without reflashing him. First use the toolkit and RCM steps above to get him ready in DFU. He needs int-developer mode and Wi-Fi so the command can reach him over SSH.

If Jibo cannot join the network, start with the Wi-Fi checks.

Set int-developer mode and Wi-Fi

In the GUI:

  1. Choose Set mode and configure Wi-Fi, then select int-developer.
  2. Enter your Wi-Fi name and password.
  3. Keep Show Wi-Fi status and IP on the boot screen checked. It is on by default for developer-mode setup and lets you read Jibo's IP from his screen.

If Jibo already has your Wi-Fi saved, More tools and local images → Set robot mode → int-developer is enough to change his mode, but it does not add the boot-screen status. Use the combined setup above to add it.

Review and confirm the change, keep USB connected until the toolkit reports it verified, then restart Jibo yourself: fully shut him down and turn him back on with his power button, without holding RCM. He should boot in int-developer mode and join your Wi-Fi.

The toolkit saves a backup of his settings before it writes. Its Backups menu can also back up every partition or chosen ones, restore them, and list the backups saved on your computer. Backing up and restoring need Jibo in DFU.

Check Jibo's screen

The Wi-Fi/IP line appears on the boot screen only in developer or int-developer mode with Show Wi-Fi status and IP on the boot screen enabled. Here is what each message means:

On Jibo's screenWhat it means and what to do
Wi-Fi: checking... Jibo is starting up and checking Wi-Fi. Wait for the status to update.
Wi-Fi: connected to <network name> · IP <address> Wi-Fi is connected and Jibo has an IP address. This is the IP address the Robots → Add a Jibo command asks for.
Wi-Fi: connected, waiting for address Jibo has joined the network, but the router has not given him an IP address yet. Wait a minute; if it stays here, check the router and its DHCP settings.
Wi-Fi: not connected Jibo is not connected to Wi-Fi. Check the network name and password, and make sure he is within range of the router. Re-run Set mode and configure Wi-Fi or More tools and local images → Add or update a Wi-Fi network with the correct name and password, then restart him. More Wi-Fi checks.
Wi-Fi: status unavailable The Wi-Fi status could not be read. Restart Jibo once; if it still appears, open a support ticket in #help on the Phoenix Discord.

If the line is missing, check the mode and enable the option in Set mode and configure Wi-Fi, then restart. To remove it, choose More tools and local images → Remove boot-screen Wi-Fi/IP status, then restart Jibo. Unchecking the GUI checkbox leaves the current setting unchanged; it does not remove an installed status line.

Before running the setup command: follow the toolkit's current boot-screen status safety note. It calls for removing this optional line before a services update. Write down Jibo's IP address, put him back in DFU, choose More tools and local images → Remove boot-screen Wi-Fi/IP status, then restart him yourself without holding RCM. This removes the status line, not his mode or saved Wi-Fi. If you need help, open a support ticket in #help on the Phoenix Discord before continuing.

Add your Jibo in the console

  1. Sign in to the console and open Robots → Add a Jibo.
  2. If he has not been connected to Phoenix, choose No or I'm not sure, then Check and prepare this Jibo.
  3. Choose Windows or macOS / Linux and copy the command the console makes for your account. On Windows, paste it into PowerShell or Command Prompt; it runs in WSL. On a Mac or Linux PC, paste it into a terminal. Use a computer on the same network as Jibo.
  4. When the command asks for Jibo's IP address, use the one on his boot screen. Review what it will change and confirm.

If Jibo was set up before, the command links him to your account and he downloads and installs his update. If he is new or reset, he restarts into his setup screen; then finish with a QR code. Leave him plugged in during his update and automatic restarts.

The command's account code is private and works once. Opening its console page again replaces it. Take the command from your own console, not from a screenshot or someone else's message.

A Jibo that has never been set up

Phoenix supports a brand-new Jibo, one still sealed in his box, or one that was factory reset. The simplest route is the Phoenix image, then QR setup. You do not need the original phone app.

Look at his setup screen. Go to jibo.io to get started means he is already connected to Phoenix. If you just flashed the Phoenix image, go straight to QR setup. If you are unsure whether he is still paired, use Check and prepare this Jibo in the console to check his existing identity; that command needs int-developer mode and Wi-Fi.

Go to the Jibo app on your phone to get started means he is not connected to Phoenix yet. Start with step 1, or follow the setup-command route if you would rather not reflash him.

Compatibility

Any stock Jibo that has never been modified is supported with 100% certainty. Paskooter has personally tested every stock software version and all stock files.

If your robot was previously changed by another mod system, it will most likely work with no changes, but that cannot be guaranteed: there is no way to foresee changes someone else made. If it doesn't work, open a support ticket in #help on the Phoenix Discord. Paskooter is happy to help.

If something goes wrong

Start with what you see. If these steps do not help, open a support ticket in #help on the Phoenix Discord with the Details for support listed below. Keep Wi-Fi names and passwords, setup commands, account codes, QR codes, account details and other personal or network information private; crop or redact them from screenshots and review logs before sharing.

  • Jibo cannot join Wi-Fi
  • A new QR code says it has expired
  • The toolkit needs Windows setup or WSL
  • The Mac toolkit cannot reach jibo.io
  • An Apple silicon Mac cannot connect over USB

“Can't connect to Wi-Fi network”

What you see: Jibo scans the code, then cannot join your Wi-Fi.

  1. Keep Jibo within range of the router. Check the Wi-Fi name and password, including capitals, punctuation and spaces. For a phone hotspot, use the network name shown in its hotspot settings.
  2. For QR setup, enter those details and choose Show setup code again; the old code still has the old details. For the setup-command route, correct the saved Wi-Fi with the toolkit, then restart as that step describes.

Details for support: the exact message, router or hotspot model, whether you used QR setup or the setup command, and which steps you tried. Do not send your Wi-Fi name or password.

“QR code has expired” straight after scanning

What you see: Jibo rejects a code you just made. The message alone is not enough to tell why setup did not finish. Check the setup screen and Wi-Fi details below before assuming the code is too old.

  1. Check his setup screen. Go to jibo.io to get started means he is already connected to Phoenix. If it still says Go to the Jibo app on your phone to get started, connect him first with the Phoenix image or the setup command; the command needs int-developer mode and Wi-Fi.
  2. If the console offers Make a new code, choose it. Otherwise, reopen QR setup, check your Wi-Fi details and choose Show setup code.
  3. Scan the new code promptly. Setup codes work once and normally last 15 minutes. If there are several frames, follow the frame-by-frame steps; do not reuse an old screenshot.
  4. If another fresh code is rejected immediately, stop repeating setup and open a support ticket in #help on the Phoenix Discord. Do not reset or reflash Jibo just for this message.

Details for support: which setup route you used, the time and time zone, how long after making the code you scanned it, the number of frames, and the exact messages on Jibo and in the console. Do not attach the QR code.

The Windows toolkit will not open, or asks for WSL

What you see: setup asks for Linux/WSL or USB support, or stops before the toolkit opens.

  1. Use the Windows .exe download, not the source ZIP or run-gui.cmd. The toolkit needs WSL 2, WSLg and usbipd-win; it is not a WSL-free app.
  2. Follow its setup prompts and the Windows administrator prompt for an installation you approved. Keep the computer online. Save your work and restart Windows if requested, then open the same .exe again.
  3. If an older download stopped at Checking Windows and WSL or said WSL is not installed, download the current .exe (v1.0.4 or later) and open it. When setup offers to install Windows' Linux support, choose Install and approve the Windows administrator prompt. When it asks, restart Windows yourself and open the same .exe again. If it still stops, open a support ticket with the ticket button in #help on the Phoenix Discord.
  4. If setup stops, use Copy details and Open log folder. If those buttons are not shown, take a screenshot or photo of the error. Do not switch to the source ZIP or run-gui.cmd as a workaround.

Details for support: the copied setup summary or error screenshot, Windows version, toolkit version and the step where it stopped. Review it before sharing; leave out passwords and Wi-Fi settings.

The Mac toolkit says “Can't reach jibo.io”

What you see: the toolkit cannot get the Phoenix image list. This message alone does not tell us why.

  1. On that same Mac, open jibo.io in a browser. If it also fails, check the Mac's internet connection and try again when the site is reachable.
  2. If the browser works, close the image list and reopen Install a Phoenix image or an official update. If it still fails, send the details below rather than bypassing certificate or image checks.
  3. Check that you used the download for your Mac's chip. The downloadable app needs macOS 15 or later; for an older Mac, follow the source-version instructions.

Details for support: Mac model and chip, macOS and toolkit versions, the full error message, when it happened (with time zone), and whether jibo.io opened in that Mac's browser.

An Apple silicon Mac cannot connect to Jibo over USB

What you see: the toolkit does not show RCM/APX detected, or never reaches DFU active; Jibo recovery loader ready. Apple silicon USB operation is still experimental.

  1. Use the Apple silicon download. If running from source, use a native Terminal session, not Rosetta, as the Mac instructions describe.
  2. With no transfer running, check the USB cable and try a direct connection rather than a hub. Follow the RCM steps, then choose Refresh USB. Do not unplug USB during a transfer.
  3. If it still cannot reach DFU, stop before flashing and open a support ticket in #help on the Phoenix Discord. A Windows or Linux PC, or an Intel Mac, is another option.

Details for support: Mac model and chip, macOS and toolkit versions, the USB cable/adapter/hub used, the exact USB readiness message, and whether Jibo showed the red forehead light without a startup chime.

Need help?

Open a support ticket in #help on the Phoenix Discord. Use the channel's Open a support ticket button. Include what Jibo shows and which step you reached. Keep passwords and account codes private.

For toolkit details, read the toolkit README.

Phoenix is an independent project, not affiliated with Jibo, Inc. Changing your robot's software carries some risk; it is your hardware and your decision. See Privacy and Terms before starting.

Find your people.

Jibo stories, setup help, and project updates in Phoenix's own Discord community.

Join Phoenix Discord

Phoenix is independent, with no affiliation to, or endorsement by, Jibo, Inc., its successors or any current rights holder. "Jibo" identifies the hardware this software is compatible with.

Free to use. Provided as is, with no warranty of any kind. Home Developers Terms Security