Dualscan™ Share
Overview
Save USB folders to GitHub, GitLab or Bitbucket and transfer pinned backups, with integrity and original app/layout protection.
Dualscan™ Share moves files between user-selected USB folders and pinned Git or public AWS S3 snapshots, preserving relative paths and verifying content. Start with the official Dualscan OS image or restore a prepared .dualscan project. MAKE OR RESTORE A USB IMAGE Pin a public GitHub commit, resolve Git LFS pointers to actual binaries, and transfer its tracked structure directly into your selected USB root. No repository-folder or ZIP wrapper is added. Transfers stream with bounded memory, check hashes and sizes, and read destination files back before verified completion. The official image requires BACKUP_SHA256.json; supported manifests must validate when present. Read-only preflight checks collisions before you authorize missing-file creation. Different existing files block writing. Share never formats a drive or automatically replaces conflicting files. Progress, pause/resume, cancellation, local checkpoint recovery and separate evidence reports are included in the main transfer workspace. Smart Switch readiness appears only for eligible plans after full verification; it does not certify restoration on a phone. DISCOVER BACKUPS AND INSTALLERS Discover nested package folders without hardcoded drive names, device IDs or timestamps. Source Backup is excluded. Select a package and snapshot; each Smart Switch snapshot requires both SmartSwitchBackupInf.bk and APKFILE/AppList.bk. Loose APKs are identified from their actual Android package metadata, including renamed files. Detected versionName/versionCode and pinned official release hash/size checks have separate results. Diamond Player 1.4.3 / build 12 is recognized correctly. Older builds, incorrect packages, checksum mismatches and scan/permission errors have distinct statuses. Encrypted Smart Switch payload presence remains independent and is labelled version unverified. No APK is executed and no encrypted app version is inferred. SAVE A VERIFIED DERIVATIVE Save USB folders to a new branch in an existing GitHub, GitLab.com or Bitbucket Cloud repository using a session-only access token. Ordinary folders can be saved as clearly labelled generic snapshots. Review destination, file totals, any empty-repository initialization, LFS changes and storage-host permissions before publication. Existing branches are never force-pushed. Remote Git identities are checked; LFS server object confirmation is distinguished from a full binary redownload. A Smart Switch derivative must preserve every original tracked file and app from the pinned official Dualscan OS reference. Added snapshots remain separate under SmartSwitchBackup2; both markers are required. Missing or changed originals and invalid additions block publication. Original launcher bytes are preserved; physical folder order, icon coordinates and successful device restoration are not certified. Restores put SmartSwitchBackup2 and the original OEM structure directly at the selected root. CREATE AND SHARE .DUALSCAN PROJECTS After analyzing a public GitHub source, open .dualscan · Git / AWS S3 and choose Export current pinned Git plan. A successful verified S3 backup downloads its matching .dualscan project automatically. These files hold source identities and integrity metadata; binary payloads remain in Git/LFS or S3. New files use binary TypelockerProject2 authenticated AES-256-GCM protection with a shared app key. The key is recoverable from client software; use an optional private passphrase for confidential project metadata. Legacy files remain readable. Import rechecks source identities and the original reference before collision-safe restore. Public S3 backup accepts only a verified complete Dualscan SSS dataset. Use your existing bucket and scoped credentials, review a new random DUALSCAN-OS folder, and explicitly authorize public access to all files and the project descriptor. Every object passes anonymous SHA-256/size read-back. Share does not change bucket policies, ACLs or Block Public Access settings. Protect personal additions using Smart Switch encryption before upload; project-file protection does not encrypt public payloads. Interrupted uploads may leave partial objects and charges. Scoped setup examples are provided. HELP AND PRIVACY Open Settings & help for the instruction manual, including USB-to-GitHub and USB-to-S3 project creation: https://dualscan.cloud/share/manual.html Requests go directly to the chosen provider or approved storage endpoint. Tokens and AWS keys remain in page memory and are excluded from project exports, checkpoints and reports. There are no ads, analytics, publisher-operated transfer servers or automatic report uploads. Desktop Chrome 132+ with File System Access is required. Choose the USB root and check free space yourself; a browser cannot identify USB-C hardware or preserve full filesystem timestamps, ownership and ACLs. This is file transfer, not a certified forensic disk acquisition. Keep the workspace open while operating. Separate macOS and Windows downloads and documentation are available at https://dualscan.cloud/share/. They are not included in the Chrome package. Samsung and Smart Switch names describe compatible backup data and do not imply sponsorship or certification.
0 out of 5No ratings
Details
- Version1.3.2
- UpdatedOctober 29, 2026
- Offered byDualscan.cloud Dualscan LLC
- Size278KiB
- LanguagesEnglish
- Developer
Email
50e3f9@gmail.com - Non-traderThis developer has not identified itself as a trader. For consumers in the European Union, please note that consumer rights do not apply to contracts between you and this developer.
Privacy
Dualscan™ Share has disclosed the following information regarding the collection and usage of your data. More detailed information can be found in the developer's privacy policy.
Dualscan™ Share handles the following:
This developer declares that your data is
- Not being sold to third parties, outside of the approved use cases
- Not being used or transferred for purposes that are unrelated to the item's core functionality
- Not being used or transferred to determine creditworthiness or for lending purposes
Support
For help with questions, suggestions, or problems, visit the developer's support site