MMY India: moving to a new phone
Moving MMY to a new phone in India is a reinstall, not a copy. Android does not carry the app's data across on its own, the version code decides whether the new file is an update, and the one-time code goes to whichever SIM you type in. Do the SIM first, then the file, then the login.
Order of work
Reinstall, in the right order
- Finish the number port, or move the physical SIM, before you install. The OTP has to reach the new handset. A port that is still pending will send the code to the old network, and you will wait on a phone that cannot receive it. Dual-SIM notes are on the OTP page.
- Check the new phone against the file. Android 7.0 or newer, arm64-v8a. A new phone in current Indian retail almost always clears both, and "almost" is not a check. Read About phone, as the device page describes, especially if the "new" phone is a refurbished handset.
- Download the channel file again. Do not copy the APK off the old phone over Bluetooth or a file-share app unless you then check the byte count. A forwarded file is how a truncated copy starts its second life. The finished file is 20,954,528 bytes.
- Install, open once on Wi-Fi, and let the first launch fetch its assets. That fetch is part of the move. A metered pack on the new SIM should not be the path for it if you can avoid it. See the network page.
- Sign in with the same number you used before, and type the SMS code yourself. The app cannot read it.
Uninstall on the old phone after the new one is signed in, not before, if you still have the old handset. Keeping both for a day costs nothing and gives you a fallback if the new install fails the byte check. Once the new phone works, remove the app from the old one so a household member does not inherit a logged-in session. Shared-phone hygiene is on the age page.
Version code
Version name 2.2.5, version code 225
The file this site records carries version name 2.2.5 and version code 225, package com.mmyuionn.opp02. Android treats the version code as the update integer. If the old phone already has this package at code 225, installing the same file again is a reinstall of the same build, not an upgrade. If a later file appears with a higher code, Android will accept it over this package only when the signing key matches. A lower code will be refused with "app not installed".
The other measured file, mmy.apk at 21,049,457 bytes, uses package com.Mymuqiueb.ineb. Same label, same version name, different app. Installing it on the new phone does not bring over a session from com.mmyuionn.opp02, and installing both gives you two icons. Pick the channel file, which is the one the button on this site opens, and do not "complete" the move by adding the second package.
Nothing in a file dump transfers a balance. This site did not measure accounts, deposits or withdrawals. If the old phone held a balance, the only route is the account itself, recovered by the number and the code, on a server this site does not operate. Copying app data with a backup tool is not a method this site can vouch for, and it is a good way to restore a half-written cache that then fails the first launch.
The new SIM
OTP on the new SIM
Type the number that owns the account, which should now be on the new SIM. A new prepaid SIM with a new number is a new identity as far as an SMS gate is concerned. Using it because the port is slow creates a second account, and this site has no way to merge two accounts. Wait for the port.
New SIMs in India can take a little while before SMS works even when data already works. Prove SMS with a message from another phone before you request the code. Check DND on the new SIM too. A freshly ported number keeps the DND preference that belonged to it, and a strict filter can drop the first code. The messages app's spam tab is the first place to look.
READ_SMS is still absent on the new phone. You type the code. Nobody at a shop counter should type it for you, and you should not read it aloud. A registration done by the person who sold you the handset is an account you do not control.
After the move
What does not come across
Local settings, a declined notification prompt, and cached assets do not come across. On Android 13 and newer the new phone will ask for POST_NOTIFICATIONS again. Decline it if this handset is ever shared. The state you are standing in did not change because the phone did. If you moved cities as well as handsets, re-read the states page and check a current source for the new state before you deposit. Payment rails remain not confirmed by this site on either phone.