0
samsung-q70t-tizen-root
Getting persistent debloat on my Samsung Q70T TV
- Root exploit
- Alpha
- High brick risk
This project hasn't been claimed by its maintainer yet, so its details come from the community. Is it yours? Claim it
Before you start
- How hard is it?
- HardUses the command line or developer tools.
- What you need
- Nothing beyond the device, as far as the project says.
- Can it break my device?
- Could leave your device unusable.
- Can I undo it?
- The project doesn't say. Assume you can't.
Get itOpens github.com
Did it work for you?
Did samsung-q70t-tizen-root work on your Samsung Q70T?
No reports yet.
One-tap reports from owners. Bricked reports are checked before they count.
Compatibility
Devices: Samsung Q70T.
No compatibility information yet.
Getting started
From the project's README ("Starting on a different model"):
- Inventory the device: firmware string, kernel, runtime dirs, capscan.sh, read-only vs writable partitions, what is in /etc/profile.d.
- Confirm the foothold and what uid it gives you.
- Decide which root path the device class supports: /usr/bin/dotnet with capsysadmin → archive-root may apply; no dotnet host, launcher plugins only → managed code runs capless (see 07); a world-writable DMA device → physical-memory route.
- Get the firmware container, decrypt via the TEE, recover the kernel, derive addresses for that build.
- For persistence, look for a boot path that sources or executes something on a writable partition, and verify it runs as root.
- Test every claim on the device; write down the firmware string next to every address.
Risk and recovery
- Brick risk
- High
- Requires opening the device
- No
Credits, license and support
- License
- MIT