JCloud J Calendar JVault J Busters Phone apps App Store Phone page
Phone… JCloud…

Phones

Health, last connection, and everything stored on this PC. Plug in for a USB backup, trigger one over the internet, Find My J, or copy a phone onto a new one.

Loading phones…

Link a phone to JCloud

  1. USB (best for full backup): plug in a data cable. If the phone asks, tap Allow. USB debugging can stay on — then Backup.
  2. Wi‑Fi: every app talks through JCloud. Encrypted slices wait, retry, and shrink if the signal drops — same send/save/receive path for photos, apps, and notes.

Loading pair link…

Open JCloud Open JVault

Backups
On this PC
Vault

JCloud

This PC is the cloud for your phones. Each phone has its own folder. Plug in USB, or open the phone link on Home.

Checking…

USB backup copies the whole phone under the active device. Offload only frees space in the folders listed in Settings — it will never wipe the entire phone.

Devices

Name each phone. JCloud tracks storage used on this PC and the latest backup per device. Plug in a phone and tap Use for backups (or bind its adb serial) so the right folder is used.

Loading devices…
Settings (schedule, folders)
Wireless sync (token)

Token (send as header X-JCloud-Token). All apps use JCloud Link — AES-256-GCM slices that resume and shrink on a weak signal:

Over Tailscale Funnel the phone can hit this Phones app and upload files without USB. USB/adb backup is still the simplest full pull of Photos/Download/etc.

Vault for this device

Offload moves folders to this PC and deletes them on the phone. Phone app: install JCloud from the App Store, then open the phone link on Home (it pastes this PC’s URL + token). Mobile page: /jcloud-app

Loading…

Backups for this device

Loading…

Phone apps

J Maps, calendar, notes, and the phone catalog live on this tab. Plug in over USB to install. J Store is USB-only once; other apps can update over Wi‑Fi.

Full App Store Design an App

Recorder

Voice or type. Saves into J Notes on this PC so Jill and the Notes phone app can read it.

J Maps · Hey Jarvis

The phone app is J Maps in the catalog. Hey Jarvis here can add calendar events and send ideas to J Notes.

J Calendar

Each phone user has their own calendar. New events are sole (private) unless you share them. Paste dumps and Hey Jarvis live in the full app.

Open J Calendar
Loading…

J Notes

Shared notes for the Notes phone app, the recorder, and J Maps ideas.

Loading…

On the phone

Clip, Jarvis, Jill, JNotes, JCloud, J Store, J Maps, JGames, JDesk, JVault, J Calendar. Plug USB in to install.

Checking phone…
CL
Clip
Clip info lives on the mini PC — floor, orders, workers
JA
Jarvis
Fast local chat — this PC, cellular or any Wi‑Fi
JI
Jill
Ask Jill on the mini PC — texts, mail, desk
JN
JNotes
Notes synced to this PC — Jill can read & write
JC
JCloud
Backup · Find My · Status · Share · Instant PIN
JS
J Store
Apps · E/OS comfort pack · Link
JM
J Maps
Hey Jarvis notes, ideas, and calendar on this Phones PC
JG
JGames
Retro arcade — play live with people on this PC
JD
JDesk
Use this PC from your phone — screen + touch
JV
JVault
Full-screen vault door · walk-in unlock
JC
J Calendar
Per-user calendar · sole by default · share · paste dumps · Hey Jarvis
Publish / add app

Standalone apps

Jarvis, Clip, and Jill work on house Wi‑Fi and cellular through this PC’s public HTTPS. Clip and Jill still run on the mini PC. Standalone apps ship all UI inside the APK and run offline on the phone.

  • Notes — offline notepad (com.chris.notes) in the App Store when built.
  • Template: phone-tools/apps/StandaloneNotes (and copy for new apps — leave Capacitor server.url empty so assets stay local).
  • Rule of thumb: if it must work on a plane with no PC, build it standalone and put the APK in the store.

Drivers Windows needs

USB IDModeWhat you need
VID_18D1&PID_4E11 / 4EE1ADB / AndroidGoogle USB / Android ADB Interface — adb devices
VID_18D1&PID_D00DFastboot / bootloaderWinUSB with Google GUID — fastboot devices

What failed on this PC (and the fix)

  • Stock Google android_winusb.inf does not list FP6 fastboot PID_D00D → yellow Android in Device Manager.
  • Zadig installs WinUSB but often with the wrong DeviceInterfaceGUID → device looks OK, fastboot hangs on “waiting for any device”.
  • GUID can reset every time the phone re-enters fastboot → re-run the fix.

Correct Google fastboot GUID:

{F72FE0D4-CBCB-407d-8814-9ED673D0DD6B}

Phone in bootloader, then run elevated:

~/Desktop/Phones/phone-tools/fix-fastboot-guid.bat

Or PowerShell (Admin):

powershell -ExecutionPolicy Bypass -File ~/Desktop/Phones/phone-tools/fix-fastboot-guid.ps1

Troubleshooting

SymptomLikely causeFix
adb shows unauthorized RSA prompt not accepted Unlock phone → Allow USB debugging (Always allow)
adb devices empty Cable / driver / not in Android Data cable, another port, enable USB debugging
Bootloader menu but fastboot devices empty Missing or wrong WinUSB GUID Device Manager → Android VID_18D1&PID_D00D → run fix-fastboot-guid
fastboot OKAY but still locked On-phone confirm not done Select Unlock bootloader / Unlock critical with Vol Up + Power
Keeps restarting after unlock Wipe / first boot chaos Force off → Vol Down+Power → stay on menu → finish unlock_critical / flash
/usr/bin/env: bash: No such file Git Bash shebang bash ./flash_FP6_factory.sh
Critical unlock check fails unlock_critical not confirmed Repeat unlock_critical; fastboot oem device-info must show critical unlocked: true
Phone on welcome setup mid-process Wipe reboot Skip setup; get USB debugging or force bootloader — flashing will wipe again

Instructions for Jarvis (agent)

  1. Work from ~/Desktop/Phones/phone-tools/platform-tools.
  2. Check adb devices and PnP VID_18D1. If unauthorized → tell user to tap Allow.
  3. adb reboot bootloader. Poll for PID_D00D. If fastboot empty but Android USB present → run elevated fix-fastboot-guid.ps1, then retry.
  4. Unlock / unlock_critical only with clear “confirm on phone” prompts. Expect wipes and temporary disconnects.
  5. Flash with Git Bash: bash ./flash_FP6_factory.sh from C:\flash\fp6-eos (or re-extract zip). Log output. Wait for EXIT 0.
  6. Tell user first /e/OS boot can take 5–10 minutes. Do not relock unless asked + SPL checked.
  7. Update this page / JARVIS-PHONE.md if a new gotcha appears on the next phone.

Full runbook: /phone-tools/JARVIS-PHONE.md

Progress checklist (next phone)

Full command reference

Platform Tools

cd ~/Desktop/Phones/phone-tools/platform-tools
.\adb.exe devices
.\adb.exe reboot bootloader
.\fastboot.exe devices

Unlock (wipes)

.\fastboot.exe flashing unlock
# On phone: Unlock the bootloader → Vol Up → Power

.\fastboot.exe flashing unlock_critical
# On phone: confirm again

.\fastboot.exe oem device-info
# Need: Device unlocked: true  AND  Device critical unlocked: true

Verify ROM

cd C:\Users\Chris\Desktop\JA\phone-tools
Get-FileHash .\IMG-e-4.2-a16-20260815662938-official-FP6.zip -Algorithm SHA256
# Expect: 8C651B810A0280E0621C07058094ACBEF88C3524D2EA0C7FB99FD634EC03818C

Flash (Git Bash)

cd /c/flash/fp6-eos
# or: tar extract zip to that folder first
export PATH="/c/flash/fp6-eos/bin-msys:$PATH"
bash ./flash_FP6_factory.sh

Anti-rollback

Note stock SPL before unlock. /e/OS rollback ≈ 5th of its SPL month. Only relock if /e/OS rollback ≥ previous stock SPL. Prefer leave unlocked.