Frameo photo frame: ADB stuck on “unauthorized”
Why adb devices shows a Frameo frame as unauthorized, and what owners did about it.
Why does adb devices show my Frameo frame as “unauthorized”?
Having no SystemUI (no status or navigation bar) is common on these frames, and SystemUI may also be present but deliberately disabled. Then the ADB authorization prompt has nowhere to appear.
What should I try first?
On a Runxion 10.1" Frameo frame, turning Frameo's ADB Access off and on again with the USB cable plugged in brought up the authorize prompt. This is reported for that frame only.
Source: Wes Bos, photo-frame-dashboard: device table (Runxion row)
Which frames are known to stay unauthorized?
The repo lists the Pastigio / SOMY ZC002 10.1" (Frameo), the Pastigio FRAME157 15" (Frameo; owners wrote the host key to userdata adb_keys from Loader after a verified backup), the Uhale 102KZ (prompt hidden behind the Uhale kiosk) and the Uhale SI006. Frames sold under the same name can have different boards, so match the About screen, not the brand.
Sources: Wes Bos, photo-frame-dashboard: device table; Wes Bos, photo-frame-dashboard: device index intro
What if the prompt never appears?
Adding your computer's public key straight into /data/misc/adb/adb_keys, matching the ownership, mode and SELinux context of the adb_keys file already on the frame, authorizes ADB without a prompt and without touching the boot image or any binary. This was seen on the Uhale SI006 and the SOMY ZC002.
Related build: the project page