UP Manager

💊 Universal Patch Manager Universal Patch Manager (UPM) is an Android manager for patching apps with ReVanced, Morphe, and Reseam in one place. Built from ReVanced Manager, UPM expands the full patching workflow with third-party patch bundles, multiple patcher runtimes, saved apps and patch profiles, batch and automatic repatching, flexible APK sources, advanced installers, and standalone APK utilities.

UPM supports the ReVanced, Morphe, and Reseam patch ecosystems, rooted and non-rooted workflows, local and remote patch bundle sources, split APK handling, downloader integrations, signature and keystore tools, detailed patching diagnostics, backups, storage controls, and extensive UI customization.

💪 Features

UPM covers the full patching lifecycle, from choosing an APK source and patch bundle to patching, installing, saving, repatching, automating updates, and managing the files and tools around those workflows.

For runtime behavior, memory limits, and troubleshooting, see the patching runtime guide.

Patch Bundles & Patcher Runtimes ReVanced, Morphe, and Reseam in one manager: Use ReVanced .rvp, Morphe .mpp, and Reseam .reseam patch bundles from the same app. Third-party patch bundles: Add compatible local or remote patch bundles, including repository and release-based sources. Bundle discovery: Browse the Patch Bundle Registry catalog in UPM, search it, inspect supported apps and patches, and import bundles directly. Remote updates: Check, download, and background-update remote bundles with progress, stable/pre-release channel handling, per-bundle update controls, and force-redownload support. Full changelog history: View cached patch bundle changelog history with configurable loading and storage limits, plus release links when available. Bundle organization: Rename imported bundles, reorder them, preserve metadata and timestamps, and export/import bundle configurations. Built-in runtimes: Morphe and Reseam patching runtimes are bundled with UPM. Morphe supports JVM or ART execution; Reseam uses its native Android runtime. ReVanced v21 runtime plugin: Add the supported ReVanced v21 runtime plugin from a local APK or GitHub source and manage its trust, update channel, installed version, and stored plugin files. ReVanced v22 runtime plugin: Add the ReVanced v22 plugin with the same trust and update controls as v21. Both JVM and ART execution are supported. Patch Selection, Profiles & Patching Flexible patch selection: Select/deselect all patches globally or per bundle, undo/redo changes, filter new patches, inspect option values, and switch between bundle recommendations and other supported versions. Patch confirmation: Review selected bundles, patches, options, and relevant configuration before patching. Patch profiles: Save patch selections, option values, target versions, a reusable APK/split source, installer choice, signature workflow, auto-install behavior, and one-tap patching preferences. Single and batch patching: Patch one app or build a multi-app queue with per-app configuration, reordering, cancellation, detailed progress/results, and install-all actions. Automatic repatching: Periodically repatch opted-in saved apps when their patch bundles change, with configurable intervals, charging requirements, notifications, and optional Shizuku/Shevery installation. Repatch source retention: Keep the original APK or split archive used for a saved app so future manual, batch, and automatic repatches can reuse it without asking for the source again. Split APK preparation: Patch .apkm, .apks, .xapk, and compatible split archives with selectable modules and cleanup filters for unused languages, densities, and native libraries. Install-target-aware patches: Morphe patch availability can adapt to Standard or Root Mount patching, including required/unavailable patches and optional GmsCore handling. Signature metadata workflow: Optionally clone signature metadata from the original signed input into the final patched APK and remember that choice for saved apps, profiles, batch jobs, and automatic repatching. Signing control: Use the manager keystore, import compatible keystores, or skip patched APK signing where supported. Detailed patcher diagnostics: View elapsed time, app/runtime/device information, selected patches, split/native-library state, and expandable patcher steps and sub-steps. Live resource monitoring: Optional memory, CPU, and storage I/O graphs are available during patching, with compact layouts and peak/current readings. Patcher logs: Export detailed logs with app, device, runtime, selected patch, split, and failure information.

APK Sources, Downloaders & Saved

Apps

Multiple APK sources: Start from installed apps, local storage, manager-downloaded APKs, downloader plugins, supported helper apps, or split archives depending on the workflow. Downloader plugins: Install, update, configure, trust/revoke, and remove compatible downloader plugins directly in UPM. APK download helper apps: Use supported standalone helper apps as APK sources, with helper discovery, signer trust, GitHub source management, and install/update controls. Download cache management: Keep multiple downloaded APKs, export or delete individual entries, and optionally retain only the newest download for each app. Saved patched apps: Keep patched APKs in the Apps tab for later install/export/repatch workflows and inspect the patches, bundles, and related metadata used to create them. Saved app organization: Search and reorder saved apps, manage update badges, and control whether patched apps are automatically saved. Installation & Root Workflows Central installer manager: Configure primary and fallback installers and choose installers per install or patching result, saved app, patch profile, or tool workflow. Multiple install methods: Use the Android system installer, Shizuku/Shevery/Sui, supported custom installers, rooted installation, or Root Mount where compatible. Google Play attribution: Supported system, Shizuku/Shevery, and rooted install modes can record Google Play Store as the installation source. Root Mount: Mount compatible patched APKs over installed stock apps with stock-source checks, split-input compatibility, post-patch routing, and install-target-aware patch selection. Root recovery: Track mounted apps across reboots, repair broken mounts, recover stock sources where possible, and export diagnostics when a mount needs attention. Installation controls: Cancel in-progress installs, handle signature conflicts with clearer recovery options, and automatically install successful patch results when configured.

Tools & System Utilities

Split APK merger: Merge .xapk, .apkm, .apks, and compatible ZIP archives into a single APK with selectable split filters, signing, install/save actions, progress sub-steps, and live resource monitoring. Split installer: Install compatible split packages directly without first merging them into a single APK. APK signer: Sign APKs with the manager's signing configuration from a standalone tool. Signature metadata injector & cloner: Inspect sources and clone/inject legacy signature metadata into APK or split targets with selectable signing/output behavior. Keystore creator: Generate new signing keystores in supported formats with configurable credentials and long-lived certificates. Keystore converter: Convert supported keystore formats directly in the app. Custom YouTube assets: Build custom adaptive icons and header assets with positioning, color, preset, and export controls. LSPosed module management: Optional rooted tab for adding, updating, installing, and organizing user-added LSPosed-compatible modules from GitHub or local storage. Storage, Backups & File Management Storage dashboard: Inspect UPM storage usage across caches, patch bundles, runtime/downloader plugin files, saved APKs, repatch inputs, patch-profile inputs, signing files, LSPosed modules, backgrounds, and other app data. Targeted cleanup: Clear individual storage areas, clear recreatable caches, or configure scheduled automatic cache cleanup. Settings and data export/import: Back up and restore manager settings and supported UPM configuration data, including patch-related preferences and organization state. Signing-file handling: Import/export compatible keystores while keeping signing material out of Android cloud backups. Custom file picker: Favorite paths, remember folders per workflow, persist sorting/search preferences, show hidden files, and use Android document providers where supported.

Appearance, Navigation & Search

Theme customization: Choose theme/accent colors with presets, HEX input, and live previews, plus monochrome and pure-black options where supported. Custom backgrounds: Import a background image, adjust its transparency, and keep a private app copy so it remains available if the original moves. Navigation controls: Configure tab visibility/labels, swipe navigation behavior, action layouts, and other interaction preferences. Search throughout UPM: Search settings with jump-to highlighting and search the Apps, Patch Bundles, Patch Profiles, discovery, patch selection, and file-picker workflows. Patch-selection layouts: Use standard or more compact/minimal patch selection views and keep relevant filters/presets across sessions.

Updates, Notifications & Advanced

Controls Manager updates: Check for new UPM releases, preview changelogs in-app, and receive update notifications. Patch bundle notifications: Get grouped update alerts and background download progress for bundle updates, including manual and automatic delivery modes. Metered-network controls: Decide whether manager and patch bundle update checks/downloads may run on metered connections. Developer options: Advanced controls remain directly accessible for patcher behavior, process/runtime settings, logging, memory handling, notification behavior, and diagnostics. External automation: When external batch actions are enabled, automation apps can request batch patching, while launcher shortcuts can trigger update/repatch workflows.

Localization Device language support: Follow the device language when a supported translation is available, with English fallback behavior. Selectable app languages: English, German, Spanish, French, Chinese (Simplified), Indonesian, Hindi, Gujarati, Portuguese (Brazil), Vietnamese, Korean, Japanese, Russian, Turkish, and Ukrainian. In-app switching: Change languages from Settings with a restart prompt when needed.

💊 Android manager for ReVanced, Morphe, and Reseam with third-party patch bundles, batch and automatic repatching, advanced installers, APK tools, and deep customization.

💊 Universal Patch Manager Universal Patch Manager (UPM) is an Android manager for patching apps with ReVanced, Morphe, and Reseam in one place. Built from ReVanced Manager, UPM expands the full patching workflow with third-party patch bundles, multiple patcher runtimes, saved apps and patch profiles, batch and automatic repatching, flexible APK sources, advanced installers, and standalone APK utilities.

UPM supports the ReVanced, Morphe, and Reseam patch ecosystems, rooted and non-rooted workflows, local and remote patch bundle sources, split APK handling, downloader integrations, signature and keystore tools, detailed patching diagnostics, backups, storage controls, and extensive UI customization.

💪 Features UPM covers the full patching lifecycle, from choosing an APK source and patch bundle to patching, installing, saving, repatching, automating updates, and managing the files and tools around those workflows.

For runtime behavior, memory limits, and troubleshooting, see the patching runtime guide.

Patch Bundles & Patcher Runtimes ReVanced, Morphe, and Reseam in one manager: Use ReVanced .rvp, Morphe .mpp, and Reseam .reseam patch bundles from the same app. Third-party patch bundles: Add compatible local or remote patch bundles, including repository and release-based sources. Bundle discovery: Browse the Patch Bundle Registry catalog in UPM, search it, inspect supported apps and patches, and import bundles directly. Remote updates: Check, download, and background-update remote bundles with progress, stable/pre-release channel handling, per-bundle update controls, and force-redownload support. Full changelog history: View cached patch bundle changelog history with configurable loading and storage limits, plus release links when available. Bundle organization: Rename imported bundles, reorder them, preserve metadata and timestamps, and export/import bundle configurations. Built-in runtimes: Morphe and Reseam patching runtimes are bundled with UPM. Morphe supports JVM or ART execution; Reseam uses its native Android runtime. ReVanced v21 runtime plugin: Add the supported ReVanced v21 runtime plugin from a local APK or GitHub source and manage its trust, update channel, installed version, and stored plugin files. ReVanced v22 runtime plugin: Add the ReVanced v22 plugin with the same trust and update controls as v21. Both JVM and ART execution are supported. Patch Selection, Profiles & Patching Flexible patch selection: Select/deselect all patches globally or per bundle, undo/redo changes, filter new patches, inspect option values, and switch between bundle recommendations and other supported versions. Patch confirmation: Review selected bundles, patches, options, and relevant configuration before patching. Patch profiles: Save patch selections, option values, target versions, a reusable APK/split source, installer choice, signature workflow, auto-install behavior, and one-tap patching preferences. Single and batch patching: Patch one app or build a multi-app queue with per-app configuration, reordering, cancellation, detailed progress/results, and install-all actions. Automatic repatching: Periodically repatch opted-in saved apps when their patch bundles change, with configurable intervals, charging requirements, notifications, and optional Shizuku/Shevery installation. Repatch source retention: Keep the original APK or split archive used for a saved app so future manual, batch, and automatic repatches can reuse it without asking for the source again. Split APK preparation: Patch .apkm, .apks, .xapk, and compatible split archives with selectable modules and cleanup filters for unused languages, densities, and native libraries. Install-target-aware patches: Morphe patch availability can adapt to Standard or Root Mount patching, including required/unavailable patches and optional GmsCore handling. Signature metadata workflow: Optionally clone signature metadata from the original signed input into the final patched APK and remember that choice for saved apps, profiles, batch jobs, and automatic repatching. Signing control: Use the manager keystore, import compatible keystores, or skip patched APK signing where supported. Detailed patcher diagnostics: View elapsed time, app/runtime/device information, selected patches, split/native-library state, and expandable patcher steps and sub-steps. Live resource monitoring: Optional memory, CPU, and storage I/O graphs are available during patching, with compact layouts and peak/current readings. Patcher logs: Export detailed logs with app, device, runtime, selected patch, split, and failure information.

APK Sources, Downloaders & Saved

Apps Multiple APK sources: Start from installed apps, local storage, manager-downloaded APKs, downloader plugins, supported helper apps, or split archives depending on the workflow. Downloader plugins: Install, update, configure, trust/revoke, and remove compatible downloader plugins directly in UPM. APK download helper apps: Use supported standalone helper apps as APK sources, with helper discovery, signer trust, GitHub source management, and install/update controls. Download cache management: Keep multiple downloaded APKs, export or delete individual entries, and optionally retain only the newest download for each app. Saved patched apps: Keep patched APKs in the Apps tab for later install/export/repatch workflows and inspect the patches, bundles, and related metadata used to create them. Saved app organization: Search and reorder saved apps, manage update badges, and control whether patched apps are automatically saved. Installation & Root Workflows Central installer manager: Configure primary and fallback installers and choose installers per install or patching result, saved app, patch profile, or tool workflow. Multiple install methods: Use the Android system installer, Shizuku/Shevery/Sui, supported custom installers, rooted installation, or Root Mount where compatible. Google Play attribution: Supported system, Shizuku/Shevery, and rooted install modes can record Google Play Store as the installation source. Root Mount: Mount compatible patched APKs over installed stock apps with stock-source checks, split-input compatibility, post-patch routing, and install-target-aware patch selection. Root recovery: Track mounted apps across reboots, repair broken mounts, recover stock sources where possible, and export diagnostics when a mount needs attention. Installation controls: Cancel in-progress installs, handle signature conflicts with clearer recovery options, and automatically install successful patch results when configured. Tools & System Utilities Split APK merger: Merge .xapk, .apkm, .apks, and compatible ZIP archives into a single APK with selectable split filters, signing, install/save actions, progress sub-steps, and live resource monitoring. Split installer: Install compatible split packages directly without first merging them into a single APK. APK signer: Sign APKs with the manager's signing configuration from a standalone tool. Signature metadata injector & cloner: Inspect sources and clone/inject legacy signature metadata into APK or split targets with selectable signing/output behavior. Keystore creator: Generate new signing keystores in supported formats with configurable credentials and long-lived certificates. Keystore converter: Convert supported keystore formats directly in the app. Custom YouTube assets: Build custom adaptive icons and header assets with positioning, color, preset, and export controls. LSPosed module management: Optional rooted tab for adding, updating, installing, and organizing user-added LSPosed-compatible modules from GitHub or local storage. Storage, Backups & File Management Storage dashboard: Inspect UPM storage usage across caches, patch bundles, runtime/downloader plugin files, saved APKs, repatch inputs, patch-profile inputs, signing files, LSPosed modules, backgrounds, and other app data. Targeted cleanup: Clear individual storage areas, clear recreatable caches, or configure scheduled automatic cache cleanup. Settings and data export/import: Back up and restore manager settings and supported UPM configuration data, including patch-related preferences and organization state. Signing-file handling: Import/export compatible keystores while keeping signing material out of Android cloud backups. Custom file picker: Favorite paths, remember folders per workflow, persist sorting/search preferences, show hidden files, and use Android document providers where supported. Appearance, Navigation & Search Theme customization: Choose theme/accent colors with presets, HEX input, and live previews, plus monochrome and pure-black options where supported. Custom backgrounds: Import a background image, adjust its transparency, and keep a private app copy so it remains available if the original moves. Navigation controls: Configure tab visibility/labels, swipe navigation behavior, action layouts, and other interaction preferences. Search throughout UPM: Search settings with jump-to highlighting and search the Apps, Patch Bundles, Patch Profiles, discovery, patch selection, and file-picker workflows. Patch-selection layouts: Use standard or more compact/minimal patch selection views and keep relevant filters/presets across sessions. Updates, Notifications & Advanced Controls Manager updates: Check for new UPM releases, preview changelogs in-app, and receive update notifications. Patch bundle notifications: Get grouped update alerts and background download progress for bundle updates, including manual and automatic delivery modes. Metered-network controls: Decide whether manager and patch bundle update checks/downloads may run on metered connections. Developer options: Advanced controls remain directly accessible for patcher behavior, process/runtime settings, logging, memory handling, notification behavior, and diagnostics. External automation: When external batch actions are enabled, automation apps can request batch patching, while launcher shortcuts can trigger update/repatch workflows.

Localization Device language support: Follow the device language when a supported translation is available, with English fallback behavior. Selectable app languages: English, German, Spanish, French, Chinese (Simplified), Indonesian, Hindi, Gujarati, Portuguese (Brazil), Vietnamese, Korean, Japanese, Russian, Turkish, and Ukrainian. In-app switching: Change languages from Settings with a restart prompt when needed.

🔽 Download

You can download the most recent version of Universal Patch Manager from GitHub releases.

UP Manager uses the package app.universal.patch.manager and installs separately from the former URV app. Before switching, export your data from the old app using Settings > Export & Import > Export everything, then import that backup into UP Manager. Export and import your signing keystore separately on the same settings page so your patched apps keep the same signing key. Keep the old app installed until you have verified the imported data and key.

Existing URV JSON exports can be imported directly without renaming the files: Import everything, manager settings, patch bundles, patch profiles, and patch selections all retain their existing formats. UPM migrates the former manager API setting and manager-hosted plugin source URLs, and recognizes the old runtime package identities in imported settings. User-entered names, package names, options, and signing credentials are preserved.

Export/import the signing keystore separately; JSON backups do not include its key material. Files stored privately by URV and Android file-access grants do not move with a JSON backup. Reselect custom backgrounds, local bundle files, APK inputs, or option files if Android no longer grants access to them.

The embedded JVM uses OpenJDK 25 with compact object headers in 64-bit processes and OpenJDK 17 on 32-bit ARM. This configuration follows Morphe Manager PR #1302. Reseam continues to run in its isolated ART worker.

Runtime plugins must be built for UPM: app.universal.patch.manager.revanced.v21.runtime and app.universal.patch.manager.revanced.v22.runtime. The bundled Reseam runtime uses app.universal.patch.manager.reseam.runtime, and Morphe uses app.universal.patch.manager.morphe.runtime.

📋 Patch Bundles

UPM starts with no patch bundles installed. Add bundles through discovery or import.

UPM can add compatible ReVanced (.rvp), Morphe (.mpp), and Reseam (.reseam) patch bundles from local files, supported remote URLs, repository/release sources, and the in-app discovery catalog. ReVanced v21 and v22 bundles require their respective runtime plugins. Morphe and Reseam are included by default.

The Patch Bundle Registry maintains a searchable catalog of community patch sources. Visit its patch browsing site to explore bundles, patch lists, supported apps, release versions, and changelogs, and copy remote bundle URLs for import into UPM.

The same registry powers UPM's in-app patch bundle discovery, where you can search the catalog, inspect compatible apps and patches, and import supported bundles directly.

🔌 Supported Downloader Plugins

UPM supports compatible downloader plugins and standalone APK download helper apps as reusable APK sources. They can be installed or imported from supported GitHub repository, release, or APK asset URLs, managed from Downloader settings, and used directly in patching and tool workflows.

The ReVanced Manager Downloaders repository provides compatible downloader plugins for sources such as APKMirror, APKPure, and APKCombo. UPM also supports standalone APK download helper apps, such as Helper For Morphe.

⭐ Star History

Star History Chart

⚖️ License

Universal Patch Manager is licensed under the GPLv3 license. Please see the license file for more information. tl;dr you may copy, distribute and modify Universal Patch Manager as long as you track changes/dates in source files. Any modifications to Universal Patch Manager must also be made available under the GPL, along with build & install instructions.