Frequently Asked Questions

DedSec Project is a phone-first Termux toolkit and website ecosystem for learning, organizing scripts, checking links/files, exploring OSINT awareness, and solving Android/Termux workflow problems in a legal and responsible way.

The project was created by dedsec1121fk and is maintained around the public website, GitHub repository, guides, support pages, and sponsor-only extras.

No. It is designed for people who want to learn Termux and solve real digital problems from an Android phone. Beginners should start from the Installation Guide, then Learn About The Tools, then Assistance.

Most of the project is built for no-root Android usage through Termux. If a tool ever needs a special permission, it should explain it before use.

Start from the main page, open Guide For Installation, read Learn About The Tools, then use Assistance when you hit a specific Termux or DedSec problem.

Assistance replaced the old assistant chat. It is a set of standalone SEO-friendly help pages for Termux setup, storage permission, Python modules, pip errors, GitHub clone, unzip, updates, and broken installs.

Project questions stay here. Technical Termux troubleshooting moved to Assistance so each problem has its own focused page that users and search engines can understand better.

Use the Store for direct chat support, setup help, repair help, custom scripts, ButSystem re-branding, and other services. Use Contact & Credits for available contact options.

No. The project should be used for learning, privacy awareness, authorized testing, diagnostics, and personal workflow improvement. Do not use any tool against systems or accounts you do not own or have permission to test.

Open Learn About The Tools. That page explains the tools and helps you decide what to run before you touch Termux commands.

ButSystem.py is presented as an exclusive DedSec Project offer with its own page. Open the ButSystem page to understand the concept, access model, and related services.

Yes. The website supports English and Greek with a language switcher, and new Assistance pages include both English and Greek text.

Sponsors-only tools are extra scripts or resources available through the project’s sponsor tiers when access is active. The Store and sponsor links explain the current access paths.

The Store contains direct chat support, setup help, repair help, custom scripts, ButSystem re-branding, portfolio/CV website services, and sponsor-related options.

Send a clear screenshot of the error, the command you ran, the folder shown by pwd, and what you expected to happen. This makes support faster.

No. The FAQ and Assistance guides are free self-help. Paid support is for users who want someone to handle the issue directly or explain the fix personally.

Use a current official Termux release from F-Droid or the project’s official GitHub releases. The old Google Play build is outdated and can cause repository or package problems.

Most DedSec Project scripts and the Smartphone Academy are designed for normal, non-rooted Android devices. Features that depend on protected Android areas, raw wireless interfaces or system-level modification may be unavailable without root.

Common causes are an outdated Termux build, unfinished package upgrades, unsupported CPU wheels, low storage, broken repositories or a dependency that needs compilation. Use Assistance and include the complete error, Android version, architecture and command you ran.

Yes for many scripts, lessons and local utilities. Large AI models, media processing, heavy scans and multiple servers can be slow or run out of memory. Start with lightweight options and keep free storage available.

Many launchers check for common packages and Python modules, but not every Android, repository or compiler problem can be solved automatically. Read each prompt before accepting changes and keep a backup of personal modifications.

Downloaded local scripts, documentation and many Academy exercises can work offline. Features that query websites, APIs, repositories, maps, weather, public records or remote services require a connection.

Settings.py is the central launcher and configuration experience for the DedSec Project. It helps users browse available scripts, choose interface options and start tools from one place.

Developer Base groups phone-first utilities for files, coding, project structure, local websites, notes and development workflows inside Termux.

File Type Checker helps inspect the real type of a file instead of trusting only its extension. File Converter provides guided conversion workflows where supported. Always preserve originals before converting.

It prepares common development packages and a practical coding environment in Termux. Exact availability still depends on Android version, CPU architecture and upstream package support.

They support defensive learning, local diagnostics, link checks, QR creation, footprint awareness and authorized network observation. They are not permission to scan or interfere with systems you do not own.

It is a high-risk training category demonstrating how social engineering and browser permission requests can expose data. Use it only in controlled demonstrations with explicit informed consent. Never deploy deceptive pages against real people.

The Games section contains local terminal and browser experiments such as Pet Friends, Tamagotchi, Terminal Arcade and other interactive projects. They demonstrate scripting, state, menus and creative coding on Android.

ButSystem.py is an exclusive local-first communication and social platform experiment with chats, groups, stories, profiles, files, security controls and temporary sharing links. Read its dedicated page before installing or resetting it.

The website teaches the theory and gives structured instructions. Practical work runs locally through Termux and the included Smartphone-Academy.py companion, which prepares safe workspaces and records progress on the device.

Progress is stored locally under ~/.dedsec-smartphone-academy in the Termux home directory. It is not tied to a website account and is not uploaded automatically.

The companion creates separate training folders with supplied samples. A lesson may ask you to inspect your own phone settings, but it should clearly say so. Never point destructive commands at shared storage or personal folders.

No universal procedure is safe for every model. The Academy teaches model verification, documentation research, backups, risk assessment, dry runs and rollback planning. Follow the exact manufacturer or ROM maintainer guide for your exact model and region.

Many downloaded theory pages and local labs work offline. Research lessons, official-source verification, package installation and update checks require temporary internet access.

Run python Smartphone-Academy.py status to view progress, then open the existing workspace under ~/.dedsec-smartphone-academy/workspaces. Do not use --force unless you have backed up the current work.

Yes. Hours are estimates for active setup, testing, verification and documentation. Device speed, experience, troubleshooting and the depth of your evidence can change the real duration.

The site may use Google Tag Manager and analytics for visits, clicks, device information and approximate region-level statistics, as explained in the Privacy Policy. The local Academy progress file is separate and stays on the device.

The public project should be reviewed like any other source code. Do not enter secrets into scripts you have not inspected. Network-enabled tools should state why they connect, and you should test them with non-sensitive samples first.

Only with explicit informed consent in a controlled training environment. Deception, credential collection, camera or microphone capture and location collection without authorization can be illegal and harmful.

Not automatically, especially for security tools, local servers or obfuscated samples, but warnings must not be ignored. Inspect the source, permissions, network behavior and files changed before deciding whether to run it.

Their rights, access to legal counsel, presumption of innocence and due process should be respected. Public discussion should rely on verified records and must not obstruct investigations, threaten people or assume guilt from headlines.

The main website is ded-sec.space. The backup at ded-sec.online is intended for continuity if the main domain or hosting path becomes unavailable. Repository-aware builds keep their domain and path rules separate.

The main website repository is dedsec1121fk/dedsec1121fk.github.io. The sal-scar/ded-sec repository is the backup mirror, while dedsec1121fk/test is used to review changes before production.

Follow the Update guide in Assistance or the repository README. Back up changed settings, personal data and custom scripts before pulling or replacing files, because project updates may change filenames or structure.

It can if you replace the full project folder. Keep personal changes in a separate branch or backup, compare changes with Git and merge intentionally instead of copying blindly.

Use the project’s Contact page or the relevant GitHub repository issue tracker. Include the exact script, commit or version, Android version, Termux source, architecture, complete command and complete error output with secrets removed.

Yes. Small focused pull requests are easier to review. Explain what changed, how it was tested in Termux, which files are affected and any safety or compatibility limitations.

GitHub project pages run below /, while the main and backup domains run at the root. The repository-aware build rewrites internal paths, canonical URLs, CNAME and indexing files for the selected target.