throwaway96

Debugging apps (inspect)

Inspectability

Developer mode apps (those installed in /media/developer) are inspectable by default. Other apps (e.g., from the LG Content Store) are not inspectable by default, but you can add "inspectable": true to their appinfo.json to enable it. Debugging system apps (i.e., those in /usr/palm/applications) may require a special flag.

Ports

The developer mode app debugger listens on port 9998.

System service and system app debugging uses ports 5885 and 9999, respectively. However, debugging for these is not normally enabled.

Inspecting an app

throwaway96

Introduction

The DPF720 is a digital picture frame with "Digital Decor" branding. It is based on an MStar MSPD21D SoC. The example I obtained did not come in the original box, but I believe I received all important components. Here is an (open box?) Amazon listing for it. This eBay listing (archive) seems to show the box.

Conventions

Unless otherwise noted: left/right are when viewing the assembled device from the front (i.e., looking at the screen); top/bottom of the board refers to its orientation when the device is assembled and upright.

Label

Contents

The label on the bottom refers to the device as "7 In. Ultra Slim Digital Picture Frame". The first few lines under that are:

smx-smx

<?php
function kilo($n){ return $n * 1024; }
function mega($n){ return kilo($n) * 1024; }

function to_cmdline(array $cmd){
	return implode(' ', array_map('escapeshellarg', $cmd));
}

function make_pipe(array ...$cmds){
	$cmdlines = array_map('to_cmdline', $cmds);

throwaway96

HostDiag

The Host Diagnostics (HostDiag) screen shows various system information. It has been present on LG TVs since long before webOS. While it generally isn't very useful, it could come in handy in certain situations.

Opening

In general, to open HostDiag you must highlight "Channel Tuning" in the menu and press the "1" button 5 times. The menu can be opened with the menu button on the remote, but the steps after that vary a bit across webOS versions. Note that

webOS 6

smx-smx

diff --git a/ext/ffi/ffi.c b/ext/ffi/ffi.c
index 9be5ac3405..81ac091750 100644
--- a/ext/ffi/ffi.c
+++ b/ext/ffi/ffi.c
@@ -922,9 +922,11 @@ static void zend_ffi_callback_hash_dtor(zval *zv) /* {{{ */
 }
 /* }}} */
 
-static void zend_ffi_callback_trampoline(ffi_cif* cif, void* ret, void** args, void* data) /* {{{ */
-{

throwaway96

#!/bin/sh

# Directory to store overlays in (one directory structure is created per overlay configured down below)
OVERLAY_BASE=/var/lib/webosbrew/customca

overlay() {
        set -e
        overlay_id="$(echo $1 | sed 's;/;__;g')"
        unset TARGET SOURCE FSTYPE OPTIONS
        eval $(findmnt -P $1)

throwaway96

This is a collection of a few of my smaller webOS scripts.

License: AGPL v3 or later

throwaway96

#!/bin/sh

# by throwaway96
# licensed under AGPLv3+
# https://gist.github.com/throwaway96/bb31a17562eec4d8325020dee8c7e6b5

cert=/home/root/something.crt
name=lol_hax
file="${name}.pem"
tmp="/tmp/tempcert.pem.${$}"

throwaway96

WTA backdoor/vulnerability

Overview

There is a vulnerability/backdoor in webOS 5+ that allows you to easily run arbitrary commands as root during the boot process. The easiest way to exploit it simply involves putting a file on a USB drive and having it connected to your TV while it boots. There are two other methods that are more complex and require additional exploits.

throwaway96

Fixing a Microsoft SQL Server LocalDB trigger error

This is a note on how I fixed a relatively minor issue with Microsoft SQL Server Express LocalDB. The solution was a bit difficult to find. Therefore I'm writing this in the hope that it will be found by other people who have the same problem and Google the error message text. This is based on a StackOverflow answer by Yennefer. I've added a bit more detail and an alternative way to delete the triggers. I'm leaving out most of my mistakes, several dead ends, etc.

I'm certainly no expert on anything in this document. I'm just sharing what worked for me.

The error

When I opened Microsoft's Volume Activation Management Tool (VAMT) and tried to connect to my LocalDB instance as usual, I got this error: