bug: Mount (root) install does not work

[sankarru]

Bug description

bug: mount install without gmscore not work as the revanced manager works,there still original app remains and i want to manually move the patched app to the original yt app location to make it work ,hope u fix it.

Version of Morphe (Manager) and the app you are patching

Latest but dont no about version due to frequent updates

Morphe logs

Nil

Acknowledgements

• I have checked all open and closed bug reports and this is not a duplicate.
• I have chosen an appropriate title.
• All requested information has been provided properly.
• The bug only affects using Morphe (Manager)

[LisoUseInAIKyrios]

Did you change the installer to Mount (root)?

Do that if you haven't. And don't use expert mode. It will automatically pick the correct patches and give instructions specific to root.

https://github.com/MorpheApp/morphe-documentation/blob/main/docs/morphe-resources/questions.md#25-how-do-i-patch-morphe-with-root

[ij-israfil]

same problem.

[sankarru]

This problem i also faced in urv manager but not in revenced manager by inotia

[eramax]

same problem, i have to use revenced manager to make root mount

[eramax]

The logs
03_03-13-30-41_139.log

[LisoUseInAIKyrios]

Exception doesn't give any good feedback:

1772541192.486 10451 11587 11587 E Morphe Install: Mount install failed
1772541192.486 10451 11587 11587 E Morphe Install: java.io.IOException: Exception thrown on remote process
1772541192.486 10451 11587 11587 E Morphe Install: 	at com.topjohnwu.superuser.internal.IOResult.checkException(Unknown Source:13)
1772541192.486 10451 11587 11587 E Morphe Install: 	at com.topjohnwu.superuser.internal.RemoteFile.newOutputStream$1(Unknown Source:18)
1772541192.486 10451 11587 11587 E Morphe Install: 	at app.morphe.manager.domain.installer.RootInstaller$install$2.invokeSuspend(Unknown Source:401)
1772541192.486 10451 11587 11587 E Morphe Install: 	at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(Unknown Source:11)
1772541192.486 10451 11587 11587 E Morphe Install: 	at kotlinx.coroutines.UndispatchedCoroutine.afterResume(Unknown Source:26)

[LisoUseInAIKyrios]

What root kit are you using?

[ij-israfil]

I am using magisk v30.7

[LisoUseInAIKyrios]

Some users said they had to disable root permissions in magisk app and start patching, then while patching was running they granted root permission again before patching finishes

[eramax]

What root kit are you using?

kernelSU next with android 16 qpr2

[eramax]

Use Claude

Bug Report — Mount Install Fails After Successful Patching

Device: Realme RMX3301
Android Version: 16 (API 36)
Morphe Manager Version: v1.11.0-dev.1
Patches Bundle: v1.16.1-dev.2 (61 patches)
Target App: YouTube v20.40.45 (169 MB)

---

Description

After the patching process completes successfully, the installation step fails consistently with a Mount install failed error. The patched output APK (~93 MB) appears to be generated correctly, but the installer is unable to locate the file at the expected path during the mount install phase.

---

Error Log (Key Excerpts)

E RootInstaller Mount install failed
java.io.IOException: Exception thrown on remote process
Caused by: android.system.ErrnoException: open failed: ENOENT (No such file or directory)
    at app.morphe.manager.domain.installer.RootInstaller

Additionally, during the signing phase, the following exception was observed (non-fatal but potentially related):

Asn1DecodingException: Failed to instantiate SubjectPublicKeyInfo
NoSuchMethodException: com.android.apksig.internal.x509.SubjectPublicKeyInfo.<init>

---

Analysis

The ENOENT error indicates that the installer process is attempting to access the output APK at:

/data/user/0/app.morphe.manager/app/ui/ephemeral/installer/output.apk

but the file does not exist at that path at the time of installation. This is likely caused by one of the following:

1. The patched APK is written to a temporary path that gets cleaned up before the RootInstaller attempts to mount/install it, possibly due to a race condition or premature cleanup between the patcher process and the installer process.
2. The Asn1DecodingException during signing may be causing the signing step to silently fail or produce a corrupted/incomplete output file, which then gets rejected or auto-deleted.
3. The patcher runs in a separate process (app.morphe.managerPatcher via RuntimeInit), and the IPC handoff of the output file path to the main installer process may be broken on Android 16 / API 36 due to stricter SELinux policies (several avc denied entries are present in the log for untrusted_app context).

---

Steps to Reproduce

1. Open Morphe Manager v1.11.0-dev.1
2. Select YouTube APK (v20.40.45, standard APK — not APKM bundle)
3. Apply all 61 patches from the official Morphe Patches bundle v1.16.1-dev.2
4. Let the patching complete → observe "Mount install failed" error

---

Expected Behavior

The patched APK should be installed successfully after the patching step completes.

Actual Behavior

Installation fails with ENOENT — the output file is not found at the expected path, despite patching appearing to complete successfully.

---

Additional Notes

• KernelSU is active and app.morphe.manager has SuperUser access granted.
• The issue occurs twice in the log (two consecutive install attempts both fail with the same error).
• Multiple avc denied SELinux entries are present, specifically for untrusted_app trying to read odsign and build_attestation props — this may be relevant on Android 16.
• RAM at the time of patching: 2.03 GB available / 6.92 GB total — unlikely to be a memory issue.

---

[LisoUseInAIKyrios]

Please try uninstalling and use 1.10.0

Do not update Manager if it prompts you.

https://github.com/MorpheApp/morphe-manager/releases/tag/v1.10.0

[eramax]

Issue Summary

Your Morphe Manager patcher is crashing with an ART Runtime memory allocation error (SIGABRT exit code 134) despite the increased RAM.

Key Findings:

Device Status:

• Device: Realme GT2 Pro (RMX3301)
• OS: Infinity-X v3.7 (Android 16 API 36)
• Versions: (Manager v1.10.0, Patches v1.16.0)
• Target App: YouTube v20.40.45 (169 MB)
• Kernel: 5.10.246-gki

The Problem:
The error message says: Check failed: regionspacememmap.IsValid - No region space mem map

This means the patcher process cannot allocate contiguous low-memory space for the ART heap, even though system RAM is increased. This is a memory fragmentation issue, not a total RAM shortage.

Memory Attempts:

1. First attempt: 1536 MB - Failed
2. Retry: 1408 MB - Failed
3. Second retry: Failed

Why It's Happening:

When patching YouTube (169MB+ APK with 61 patches), the isolated patcher process needs a specific memory layout. The increased RAM helps, but fragmentation prevents allocating the needed contiguous block.

This second log reveals a different and more critical root cause than the first log. Here's the complete issue report:

---

Summary

The patching pipeline fails consistently in two compounding stages: (1) the patcher subprocess crashes with an Out-Of-Memory SIGABRT on the first attempt, then restarts with a higher memory limit; (2) the signing step on the second attempt fails silently with an Asn1DecodingException, yet the process reports success anyway — producing a partially-signed or improperly-signed APK. The installer then fails to open the output file, resulting in ENOENT.

---

Detailed Failure Chain

Stage 1 — Patcher Process OOM Crash (First Attempt, PID 29011)

The first patcher subprocess crashes with a fatal SIGABRT during ART Heap initialization:

E app.morphe.managerPatcher  Failed to allocate pages for alloc space 
  "main space region space" of size 2048MB with message 
  "Failed anonymous mmap(0x0, 2147745792, 0x3, 0x22, -1, 0)": Out of memory.

F app.morphe.managerPatcher  runtime.cc:714  
  Abort message: 'Check failed: regionspace->mem_map_.IsValid() 
  No region space mem map'

F libc  Fatal signal 6 (SIGABRT), code -1 (SI_QUEUE) 
  in tid 29011 (managerPatcher), pid 29011 (managerPatcher)

The process exits with code 134 (128 + SIGABRT). The manager then automatically retries with the fallback limit:

I Morphe Manager  Process finished with exit code 134
I Morphe Manager  Process memory limit failed, retrying with 896

Stage 2 — APK Signing Failure During Second Attempt (PID 29018)

The second attempt completes patching successfully, saves the patched APK, then begins signing. The signing step throws an exception twice (for V2 and V3 signature schemes) while encoding the public key:

I System.out  Caught a exception encoding the public key 
  com.android.apksig.internal.asn1.Asn1DecodingException: 
  Failed to instantiate com.android.apksig.internal.x509.SubjectPublicKeyInfo

W System.err  Caused by: java.lang.NoSuchMethodException: 
  com.android.apksig.internal.x509.SubjectPublicKeyInfo.<init>
    at com.android.apksig.internal.asn1.Asn1BerParser.parseSequence(SourceFile:11)
    at com.android.apksig.internal.apk.ApkSigningBlockUtils.encodePublicKey(Unknown Source:45)
    at com.android.apksig.internal.apk.v2.V2SchemeSigner.generateSignerBlock(...)
    at com.android.apksig.internal.apk.v3.V3SchemeSigner.generateSignerBlock(...)
    at com.android.apksig.ApkSigner.sign(Unknown Source:2543)
    at app.morphe.manager.domain.manager.KeystoreManager.sign$2.invokeSuspend(...)

Despite this exception, the manager does not abort and reports:

I Morphe Patcher  Patching succeeded output=...installer/output.apk size=180075565 elapsed=123913ms

Stage 3 — Mount Install Fails (ENOENT)

When RootInstaller attempts to open the output APK via libsu's FileSystemService, it fails with:

E Morphe Install  Mount install failed
  java.io.IOException: Exception thrown on remote process
  Caused by: android.system.ErrnoException: open failed: ENOENT (No such file or directory)
    at libcore.io.Linux.openNative(Native Method)
    at com.topjohnwu.superuser.internal.FileSystemService.openWriteStream(...)
    at app.morphe.manager.domain.installer.RootInstaller.install$2.invokeSuspend(...)

The install fails twice (at ~T+21s and ~T+24s after signing completes), indicating a retry loop that also fails.

---

Root Cause Analysis

The signing exception (NoSuchMethodException on SubjectPublicKeyInfo.<init>) is the core bug. The apksig library is using reflection to instantiate an internal ASN.1 class. On Android 16 (API 36), stricter hidden API restrictions or changes in the internal class constructor signature cause this reflection call to fail. The exception is caught and swallowed internally, but the signing block for both V2 and V3 schemes is not properly generated, resulting in an APK that either:

• Has a malformed/missing signature block and gets rejected or auto-deleted by the system before RootInstaller can access it, or
• Is written to a path that the FileSystemService running in the root shell context cannot resolve (possible path mapping issue between user-space app context and root shell context).

The OOM crash in Stage 1 is a secondary contributing factor — the memory retry mechanism works correctly, but it adds complexity to the flow and may affect the state passed to the signing stage.

---

Steps to Reproduce

1. Open Morphe Manager v1.11.0-dev.1 on a device running Android 16 (API 36)
2. Select YouTube APK v20.40.45 (standard single APK, 169 MB)
3. Initiate patching with all 61 patches from bundle v1.16.1-dev.2
4. Observe: patcher crashes on first attempt (OOM/SIGABRT), retries automatically
5. Second attempt completes → signing throws Asn1DecodingException (caught silently)
6. Install step fails with ENOENT — reproducible 100% of the time

---

Expected Behavior

• The signing step should either succeed or explicitly fail with a user-visible error if it cannot sign the APK.
• The install step should never be attempted with a corrupted or unsigned APK.

Actual Behavior

• The signing exception is silently swallowed, patching is falsely reported as successful.
• The installer then fails with ENOENT trying to open an inaccessible or non-existent output file.

---

Additional Technical Notes

• Build fingerprint: realme/RMX3301/RED8AC:L1/15/AP3A.240617.008/S.1e1fd2e-39b2-5caf:user/release-keys
• ROM: Infinity-X v3.7
• Root: KernelSU (active, SuperUser access granted to app.morphe.manager)
• The Asn1DecodingException hits both V2SchemeSigner and V3SchemeSigner — meaning the APK is entirely unsigned
• The OOM crash requesting 2048 MB mmap on a device with only ~2 GB available RAM is expected to fail; the retry at 896 MB succeeds, suggesting the initial memory limit heuristic may be too aggressive on lower-RAM devices
• Multiple avc denied SELinux entries are present throughout for odsign and build_attestation props — consistent with Android 16 tightened policy

---

[wchill]

ENOENT and the signing error are unrelated. The signing error actually appears to be benign, as we have seen it during testing but the finished apk installs just fine on non rooted devices.

The initial OOM failure is expected and is not a concern.

More analysis needed to see what the issue is here.