OEM Brand Asset Customization & Upload Guide by Robustel

OEM Brand Asset Customization & Upload Guide

Overview

A Robustel gateway device can support custom OEM branding when the Web UI must use approved customer brand assets. This guide provides step-by-step instructions on how to safely upload brand asset files from a Windows local drive (C:) to the device's /app/oem directory for custom branding configuration. The key conclusion is that the required filenames and destination path must remain exact for the customized assets to load.

1. Connect to the Device

Use a terminal tool (e.g., PowerShell, CMD, Xshell) to connect via SSH, or use an SFTP client (e.g., WinSCP, FileZilla).Check if the directory exists:

  • Troubleshooting Note: If an SSH key conflict error occurs during connection, run:
            ssh-keygen -R 192.168.0.1    

2. Verify and Create the Target Directory

Run the following commands in the device terminal to ensure the target directory exists.

  • Check if the directory exists:
      ls -ld /app/oem

(If the system returns "No such file or directory", the folder does not exist.)

  • Create the directory (if missing):
      sudo mkdir -p /app/oem

3. Copy OEM Brand Assets (Upload from Local C: Drive)

Assuming your files are located at C:\OEM_Files\ on your local PC, the device IP address is 192.168.1.100, and your username is root (or custom sudo user).

Execute the command in your local computer's terminal (NOT inside the SSH session). Note the path formatting: Windows paths use backslashes \ or double forward slashes //, while remote Linux paths use forward slashes /.

Command Example (Batch Upload All Files):

scp C:\OEM_Files\logo_login.png C:\OEM_Files\logo_index.png C:\OEM_Files\favicon.ico C:\OEM_Files\style.js C:\OEM_Files\copyright.js sudoeg@192.168.1.100:/app/oem/

💡 Tips:

  • Replace sudoeg with your actual username (create a sudo account in the ROS Pro system if needed).
    • If the user sudoeg encounters permission issues, grant permission on the device:
sudo chown -R sudoeg:sudoeg /app/oem/
  • Replace 192.168.1.100 with your device's actual IP address.
  • Replace C:\OEM_Files with your local folder path.
  • When prompted, enter your device login password to initiate the transfer.

Method B: Using WinSCP (Graphical User Interface)

If you prefer a GUI tool over the command line:

  1. Open WinSCP and log in using the device's IP, username, and password.
  2. Navigate to C:\OEM_Files\ in the left panel (Local PC).
  3. Navigate to /app/oem/ in the right panel (Remote Device).
  4. Select all 5 required files from the left panel and drag them into the right panel.

Required File Checklist (All Required):

  • logo_login.png — Custom login page logo (400 × 90 px)
  • logo_index.png — Custom top-left header logo for the homepage (180 × 47 px)
  • favicon.ico — Custom browser tab icon (48 × 48 px)
  • style.js — Custom styling script (can be copied from default system /www directory)
  • copyright.js — Custom copyright script (can be copied from default system /www directory)

How to Obtain Default style.js and copyright.js Files

  1. Locate the files on the device:
      find /www/ -name style.js
      find /www/ -name copyright.js

  1. Copy the files to the /app/oem directory:
      cp /www/path/to/style.js /app/oem/
      cp /www/path/to/copyright.js /app/oem/

4. Reboot the Device

After uploading all files, execute a reboot command in the device's SSH terminal to apply changes.

  • Reboot Command:
reboot

(or sudo reboot, depending on user privileges)


Conclusion

A Robustel gateway device is correctly configured for custom OEM branding when the uploaded assets appear in the Web UI after reboot and browser-cache refresh. This confirms that the files were transferred to the supported OEM directory without altering system files.

⚠️ Important Notes

  1. Do Not Modify System Files: Only copy the required new files into /app/oem/DO NOT delete or modify any existing system files.
  2. Exact File Names Required: File names must match the checklist exactly (case-sensitive). Incorrectly named files will not be recognized by the system.
  3. Verification: After rebooting, clear your browser cache and access the WebUI to confirm that the new logos and copyright information are displayed correctly.

Revision

Date

Author

Notes

v.1.0

2026/08/01

Bill Chen

Initial Release