Take back
your Samsung TV.

Help me reduce optional tracking, advertising and unwanted smart features on a Samsung TV I own. First inventory my existing setup; if changes or backups already exist, preserve them and do not reapply them blindly.

My model: [PASTE MODEL CODE]
My software version: [PASTE FULL S/W VERSION]

Start read-only. Find this computer’s local network IP and explain how I can enable Developer Mode. Ask for the TV’s IP only if you cannot identify the intended TV safely. Do not act on any other device.

Throughout this task, preserve HDMI, picture, sound, Home/settings, remote controls, networking, Bluetooth, accessibility and my other streaming apps. Leave SmartThings, Ambient Mode, firmware updates and app updates unchanged. Install no background service or scheduled job on my computer. Never expose serial numbers, credentials, account data or private signing keys.

Explain compatibility gaps and retain working recovery instructions. Do not promise a speed improvement or claim every tracking path is eliminated.

Find this computer’s current local IP address for Samsung’s Host PC IP field. Do not give me the public internet IP or assume an address from an earlier session.

I will open Apps → App Settings, IMMEDIATELY press 123 to open the number input, enter 12345 → Done as fast as possible, then enable Developer Mode, enter that computer IP and power-cycle the TV. Once I confirm that is done, connect using Samsung’s official SDB tool. If SDB is missing, download the minimal appropriate package from the official Tizen source and verify it runs. Do not install a computer background service.

Read the TV model, Developer Mode state and authorized Host PC IP. Confirm they match my intended TV and computer. A reachable network port alone is not a successful developer session.

Review the current source and documentation at https://github.com/chris-ritsen/samsung-tv-root and any applicable AGENTS.md instructions. Assess the archive-launcher route for my exact TV. Do not assume compatibility from the Tizen version, and do not substitute another model’s kernel exploit.

Inventory the developer capabilities, installed .NET runtime and required file capabilities first. If the prerequisites match, try the least invasive temporary-root test. I authorize that test on my TV. Explain that archive-root probe performs root acquisition, not just read-only inspection.

Require authenticated UID/EUID 0, checked system files unchanged and successful session cleanup before calling it successful. Do not alter /etc/passwd or Samsung’s verification key on disk, flash firmware, unlock secure boot or remount protected partitions.

Back up and reversibly disable Bixby, its wake-word engine and related voice helpers, plus identified ACR/content-analysis app components on this TV.

Read https://github.com/jss8649/quiet-tizen and its applicable instructions as a reference, not a universal profile. Discover my installed app IDs, executable paths, database schema, service definitions and dependencies. Do not apply another model’s cleanup list wholesale.

Before changes, create a fresh consistent SQLite .backup, verify integrity and retain copies on both the TV and computer. Save actual preference values/types, service states and marker states. Prepare guarded, field-specific rollback first; never overwrite the first backup or restore an old database wholesale.

Where supported, set only the selected app entries to app_disable=true, app_onboot=false and app_autorestart=false. Inspect and disable the relevant voice preferences, including voice_activated, wakeupless_status, voice_recog_enable and prelaunch_mode where present. Use stop markers only when the exact negated ConditionPathExists is confirmed in this TV’s service definition.

Read back changes and check live processes. Stop only identified target processes. Tell me if anything restarts. Let root cleanup finish before asking for a reboot.

In a separate backed-up phase, reversibly disable Alexa-specific entries on this TV. Preserve all other features and previous changes.

Inventory actual installed app IDs, executable paths, service definitions/dependencies and running processes. Look for the Amazon Alexa app, Samsung alexa-client, alexa-fullscreen-app and wakeup-engine-alexa, but do not assume those are the only IDs or that every TV has all four.

Create a fresh consistent SQLite .backup, verify integrity and save original metadata and relevant service/preference/marker states on both TV and computer. Prepare guarded field-specific rollback before mutation. Do not overwrite previous backups or delete executable files.

Where supported, set only verified Alexa-specific app entries to app_disable=true, app_onboot=false, app_autorestart=false. If an Alexa service exists, inspect its definition before choosing a reversible stop mechanism. Do not disable generic text-to-speech or accessibility services based on their names.

Stop only positively identified target processes. Read back every selected field, check database integrity and report any processes that remain or restart. Let root cleanup finish before asking me to power-cycle, then verify persistence after reboot. Do not install a computer service or a TV startup app in this phase.

Audit this TV for remaining microphone listeners and voice-capture paths. My goal is to disable optional microphone listening, including wake-word detection, hands-free/far-field recognition, Bixby and Alexa. Also assess remote-button push-to-talk input and other microphone-using apps. Do not assume that turning off wake words disables every microphone path.

Begin read-only. Identify the exact model/firmware and the actual installed app IDs, executable paths, service definitions, dependencies and relevant preference values. Where access permits, inspect audio-input/capture-device use and map each client to its app or service. Distinguish microphone capture from speaker playback, text-to-speech, HDMI content recognition and a service listening on a network port. A name, loaded library or open socket is not proof of microphone recording; absence from a single process listing is not proof that listening is impossible.

Review candidates such as Samsung farfieldvoice, ondevice-voice, Bixby/Alexa wakeup engines, voice-app, voice-client and any live bwake or voice-interaction process. Treat names as leads only. Determine their actual role and dependencies before selecting them. Do not kill a process solely by its name or disable shared audio services.

Before each reversible change, make a fresh consistent SQLite .backup, verify it, save original metadata, preference types/values and service/marker states on both devices, and prepare guarded field-specific rollback. Preserve earlier backups and completed phases. If I rely on accessibility or voice-dependent apps, explain the specific tradeoff before disabling shared components.

Disable only verified optional microphone/voice targets using supported app flags, actual preferences and verified vendor stop conditions. Retain executable files. Do not alter firmware, update settings, HDMI, speakers, sound output, Bluetooth audio, networking, Home/settings, streaming apps, screen readers or text-to-speech services merely because their names include voice or audio. Install no computer background service.

Check this exact model’s official documentation for a physical microphone switch and explain what it controls; do not invent a switch location or claim it also disconnects a remote’s microphone. For undocumented remote push-to-talk paths, report the limit instead of claiming complete hardware isolation.

After changes, read back fields and preferences, check service/process states and microphone-capture clients where observable, and document any auto-restarts or inspection restrictions. After root cleanup, guide me through cold-boot and standby/wake checks. Report verified disabled features separately from unverified audio paths. Do not claim the TV can no longer listen unless the available evidence supports that claim.

In a separate backed-up phase, disable the installed components corresponding to Samsung Analytics and identified optional usage reporting; Targeted Ad Service; AdAgent and CoBA AdAgent; PISA and its control service; PromotionApp and its companion service; ADPlayer components; and Samsung TV Plus, its standalone app, deeplinker and background provider. Turn off TV Plus auto-start using the actual preference where present.

Inspect db/menu/autorun_tv_plus. Before changing it, save its actual type and value on both TV and computer and prepare a guarded inverse operation. If it exists as a boolean, set it to false using the matching preference interface and read it back. If its type differs, inspect the supported representation before changing it. If absent, do not create it: report that this firmware has no such preference and use only verified TV Plus app boot flags and provider controls. Preserve unrelated auto-start settings.

Identify exact IDs and paths from this TV. Snapshot the registry and preserve original settings, service states and marker states on both TV and computer. Prepare guarded field-specific rollback before applying anything. Prefer disabling to deleting files.

Verify any vendor-defined stop-file conditions before using them. Preserve everything outside this selected scope, including SmartThings, Ambient Mode, other streaming apps and all update settings. Check registry integrity, read back every selected field and check live service/process states. Report any automatic restarts instead of claiming everything has stopped.

The TV has completed a full power-cycle. Reconnect and perform a read-only verification of every previous phase.

Confirm this is a new boot. Read the selected registry fields, voice preferences, TV Plus auto-start, persistent stop markers, service states and relevant running processes. Check database integrity. If SDB is stale, refresh the local SDB connection without changing the TV’s configuration.

Report four categories clearly: settings that survived reboot, services/processes confirmed stopped, components that restarted, and behavior that remains untested. Do not equate disabled registry entries with stopped processes. Do not make additional changes during this verification.

Inspect contents-recognition-service.service and the process named media-analytics. Verify their executable paths, owning units and dependencies on this TV.

If they are the identified optional recognition/analytics components, back up their definitions and original states, prepare rollback and stop/block them reversibly. Inspect whether persistent controls are actually writable and loaded by systemd. Do not assume /opt/usr/share/systemd/system is a unit search path merely because it contains stop-marker files.

If only runtime masks are supported, use those and explicitly say they clear at reboot. Do not modify firmware or protected partitions to force persistence. Verify service states and actual processes afterwards, including any dependent service affected. Make no additional feature changes.

In another separately backed-up phase, disable Samsung Health and its fitness/workout helpers, Gaming Hub background helpers, and context-aware suggestions/content-grab helpers.

Identify Samsung Health’s installed UI, service and fitness/workout helpers by their actual executable paths, manifests and dependencies. Names such as samsunghealth-service-tv or com.samsung.tv.health-mde-* are discovery leads, not a universal list. Confirm ownership and purpose before selecting each entry. Disable these components reversibly; do not delete app files or shared platform services.

Discover exact installed IDs and dependencies, create a fresh consistent SQLite .backup, verify integrity and retain it on TV and computer. Save original field values, preference types/values, service states and marker states on both devices. Prepare guarded, field-specific rollback before mutation; never overwrite the first backup or restore an old database wholesale.

Where supported, set only the verified selected entries to app_disable=true, app_onboot=false and app_autorestart=false. Inspect the actual Samsung Health service definitions and use a stop marker only when the exact negated ConditionPathExists is confirmed. Stop only identified target processes. Verify database integrity and read back every selected field. Change only these features. Keep SmartThings, Ambient Mode, accessibility, picture, sound, HDMI, networking, Home/settings and my streaming apps intact.

Read back all selected changes and inspect processes. If Health or Gaming Hub relaunches in the current session, say so. After root cleanup, guide me through a cold-boot verification rather than claiming persistence from the saved flags alone.