CRYA Docs
Guides for users, creators, and reviewers.
Learn how to build, diagnose, export, submit, buy, and troubleshoot CRYA packs without needing to understand the systems behind CRYA.
Help center
Browse by task, not by internal module
The docs follow the support-center shape users expect: setup, builder, files, package reports, store, accounts, community, and support.
Server limits, demo import, theme package, cache, permissions, and rollback checks.
Image sets, ZIP imports, timing, loops, visual fit, export choices, and package handoff.
desc.txt, frame folders, dimensions, file names, Samsung notes, and safe repair paths.
Submissions, ownership notes, preview evidence, compatibility labels, badges, and review expectations.
Premium, clean exports, store packs, refunds, grants, entitlement evidence, and app-safe purchase paths.
Telegram topics, AI help, moderation-safe support, group rules, status commands, and privacy boundaries.
Learning paths
Start with the outcome, then pick the article
CRYA docs should feel like a guided product manual: users pick what they are trying to do, then get the safest next step.
Start from artwork, frames, or a ZIP and learn what a valid boot package needs.
Read Package Doctor results, desc.txt notes, frame warnings, and preview mismatches.
Use safe fixes, backups, and recovery-first guidance before touching install paths.
Prepare preview media, creator credit, compatibility labels, and Store submission evidence.
Use support evidence, status checks, legal routes, and account/billing privacy rules when stuck.
Article standard
Every guide should answer the same practical questions
Docs become more useful when every article gives users context, evidence, safety notes, and a clear next step.
What this guide helps the user do and who it is for.
What evidence or files to collect before starting.
What safety, root, billing, privacy, or Store boundary applies.
What to do next if the result fails or needs support.
| Package Doctor | Reports, desc.txt, folder shape, dimensions, frame order, file names, and repair language. |
|---|---|
| QMG export | Samsung context, boot/shutdown media paths, compatibility limits, and recovery-first notes. |
| Store submissions | Ownership, previews, compatibility labels, quality score, creator credit, and review outcomes. |
| Billing and Premium | Premium, clean export credits, future Store packs, refunds, grants, and entitlement evidence. |
| Support evidence | Package report, screenshots, device/build context, account privacy, and escalation lane. |
| Root safety | Backups, risky actions, user consent, system paths, and what CRYA will not promise. |
Core guides
Start with the documents users actually need
These docs connect the app, Boot Store, support, billing, and safety language into one readable help center.
desc.txt, frame folders, dimensions, repair notes, and support handoff.
ReadQMG ExportSamsung-aware export guidanceBoot/shutdown paths, model context, recovery notes, and compatibility limits.
ReadStore SubmissionsCreator review checklistPreviews, ownership, compatibility, access labels, and moderation evidence.
ReadBillingPremium and clean exportsSubscription access, clean export credits, paid packs, refunds, and private evidence.
ReadSupport EvidenceAsk for help oncePackage reports, device context, screenshots, private account routes, and status checks.
ReadRoot SafetyRecovery-first guidanceBackups, root/system risk, modules, firmware context, and responsible reporting.
ReadPopular guides
The first articles CRYA should publish
These are the high-value documents users will need before launch.
Create from a still image or ZIP source and understand the preview/export loop.
Understand resolution, fps, part folders, loop lines, and common parser mistakes.
Prepare screenshots, ownership notes, compatibility labels, and review metadata.
Backups, module choices, install risk, and what to collect before asking support.