Moving Panda Master to a New Phone Without Losing Your Account
How to transfer Panda Master to a new phone: what lives on the server, what to do before you retire the old device, and the mistakes that cause lost access.
Getting a new phone should be the easy part. You restore a backup, sign back into a handful of apps, and carry on. Then you reach the apps that did not come from an app store, and the automatic restore that handled everything else simply passes over them.
Panda Master is one of those. It will not appear in your restored app list, it will not be pulled down from the cloud, and the version you had on your old handset does not migrate itself. None of that means your account is at risk — but it does mean the move requires a few deliberate steps rather than none at all.
The good news is that the thing people actually worry about, losing their balance, is not really in play. Your account lives on the operator's servers. The app on your phone is a window onto it, not the account itself. Understanding that distinction takes most of the anxiety out of the process.
This guide covers what transfers automatically, what does not, the order to do things in, and the mistakes that turn a fifteen-minute job into a support ticket.
What actually lives where
Before touching anything, it helps to be clear about which side of the line each thing sits on.
On the server, and therefore safe: your username, your password, your credit balance, your transaction history, your game progress, and any bonuses currently attached to your account. None of this is stored on your handset in any meaningful sense, and none of it is affected by what you do to the app.
On your device, and therefore lost when the device goes: the installed app itself, your saved login if you had the app remember it, in-app display settings such as sound and graphics preferences, and any cached assets. All of these are trivially replaceable.
This is why the advice you will see repeated — that uninstalling does not delete your credits — is accurate. It is also why the one genuinely dangerous mistake is losing access to your login details, because those are the only key to the part that matters.
Before you retire the old phone
Do these things while you still have the working device in your hand. Every one of them is far harder afterwards.
Confirm you know your username and password
Not “the app logs me in automatically.” Actually know them. Open the app, sign out, and sign back in manually. If you cannot, you have discovered a problem at the only point where it is still easy to solve.
Many people have used the same installation for a year without ever typing their password. The app remembered it, so they never had to. That is exactly the situation that turns a phone upgrade into a recovery request.
Write the details down somewhere durable
A password manager is best. A note in an encrypted notes app is fine. A screenshot in your camera roll is not great but is better than nothing. What does not work is relying on memory for something you have not typed in months.
Record the username exactly as it appears, including any capitalisation or numbers. Usernames on these platforms are often assigned rather than chosen, and a single transposed digit will block you.
Note who your agent is
Accounts are opened and supported through an individual agent. If you need help during the move, that agent is who you contact — not a general support address. Save their contact details outside the messaging app if that app is also tied to the phone you are replacing.
People forget this one constantly. They change phones, lose their message history, and then have no way to reach the one person who can help them.
Note where you originally got the app
You will need to download it again, and you want it from the same place. Getting the new install from a different source is the most common cause of the signature errors that make an app refuse to install, and more importantly it is how modified builds end up on people's devices.
Check your balance and take a screenshot
Not because it is going to change, but because having a record of the figure and the date removes any ambiguity if a question comes up later. It costs you five seconds.
Setting up on the new phone
With the preparation done, the move itself is short.
- Finish the standard phone setup first. Complete your system restore, connect to Wi-Fi, and install pending OS updates before you start. Trying to install anything mid-restore, on a device still pulling down gigabytes in the background, is asking for a truncated download.
- Confirm you have enough free storage. A new phone restoring a large backup can be surprisingly full. You want at least a gigabyte free.
- Get the download link from your original source. Ask your agent, or use the distributor page you used the first time.
- Enable install permission for your browser. On Android this is under Settings → Apps → Special app access → Install unknown apps. On a brand-new device this will always be off.
- Download on stable Wi-Fi and leave the screen on. Do not switch apps until the download completes.
- Install, open, and sign in with your existing details. Do not create a new account.
Point six deserves emphasis. If the app presents a sign-up option first, look for the sign-in option instead. Creating a second account does not merge with your first, does not carry your balance, and produces a genuinely awkward cleanup involving your agent. It is the single most consequential mistake in this whole process, and it happens because the sign-up button is usually the more prominent one.
iPhone to Android, or the other way
Switching platforms adds nothing to the account side — your login works identically on either — but it does change the installation method.
The Android route uses an APK file, installed through your browser with install permission granted. The iOS route works differently, typically through a configuration profile or a web-app installation, and the exact steps depend on how your distributor has set it up.
If you are changing platform, tell your agent before you start. The link you were given for one platform will not work on the other, and the instructions differ enough that guessing wastes time.
Expect small cosmetic differences between the two versions. Layout, animation smoothness, and where certain controls sit can vary. Your account, balance and history are identical because they are not platform-specific.
Using both phones for a while
People often keep the old handset running for a week or two during the changeover. That is fine, with one caveat worth knowing.
Most operators of this kind do not permit the same account to be actively signed in on two devices at once. What typically happens is that signing in on the new device silently signs the old one out. That is normal behaviour, not an error, and not a sign that anything is wrong with your account.
What you should not do is treat the two installations as independent. Do not try to run a session on both simultaneously, and do not assume a balance shown on the old device is current after you have played on the new one. If something looks inconsistent, close both, wait a moment, and open one.
Wiping the old phone properly
Once the new device is working, the old one needs handling before it is sold, traded in, or handed to a family member.
Sign out of the app explicitly rather than just deleting it. Deleting an app does not always clear a stored session token, and a signed-in session on a device you no longer control is exactly the thing you do not want.
Then do a full factory reset from system settings. Do not rely on manually deleting apps and files. A factory reset is the only reliable way to clear stored credentials, cached data and saved sessions across everything on the device, not just this one app.
If the phone is going to someone in your family, this still applies. The point is not distrust; it is that a device with a live session on it is a liability regardless of who is holding it.
When the new install will not sign in
If you have installed successfully but the login is rejected, work through these in order before contacting anyone.
Check the username character by character. Assigned usernames often mix letters and digits in ways that invite mistakes — a zero read as the letter O, a one read as a lowercase L. Compare it against what you wrote down.
Watch for autocorrect. Mobile keyboards will happily capitalise the first letter of a username field or insert a trailing space after a paste. Both will fail a login silently. Turn off autocorrect for the field if you can, and check for a space at the end.
Confirm you are on the current version. An outdated build can fail to authenticate against updated servers. If your old phone had not updated in a long time and you installed from a saved file rather than a fresh link, you may be running something the server no longer accepts.
Try a different network. Switch from Wi-Fi to mobile data, or the reverse. Some networks interfere with connections to servers outside their usual expectations, and this produces login failures that look like wrong-password errors.
If all four come back clean, contact your agent. Give them your username, the device and OS version, where you downloaded from, and the exact error text. That is enough for them to act on immediately rather than asking three rounds of clarifying questions.
The mistakes that actually cause problems
Across everything above, four errors account for nearly all the genuine difficulty:
- Wiping the old phone before confirming the new one works. Keep the old device intact and functional until you have successfully signed in on the new one. Not until you have installed it — until you have signed in.
- Not knowing the password. Everything else on this page is a minor inconvenience. This one is the difference between a fifteen-minute task and a recovery process that depends entirely on your agent's records.
- Creating a second account. Look for sign in, not sign up.
- Downloading from wherever came up first. Use the source you originally used. A search result under time pressure is how modified builds get installed.
A short checklist
If you want the whole thing in one place:
- On the old phone: sign out and back in to confirm you know your credentials.
- Write down username, password, agent contact, and download source.
- Screenshot your balance.
- On the new phone: finish setup, update the OS, confirm free storage.
- Get the link from your original source. Enable install permission.
- Download on Wi-Fi with the screen on. Install.
- Sign in — not sign up — with your existing details.
- Confirm your balance matches the screenshot.
- Only then: sign out on the old phone and factory reset it.
Done in that order, the move is uneventful. The steps that feel like overcaution — testing your password before you need it, keeping the old device until the new one is proven — are the ones that make it uneventful.
Frequently asked questions
Do I lose my balance when I switch phones?
No. Your username, password, balance, transaction history and bonuses are all held on the operator's servers. The app on your handset is only a window onto that account. What you lose with the old device is the installed app and any saved login, both of which are easily replaced.
What should I do before wiping my old phone?
Sign out and sign back in on the old device to prove you actually know your username and password, write both down somewhere durable, save your agent's contact details outside any app tied to that phone, note where you originally downloaded the app, and screenshot your balance. Keep the old phone working until you have successfully signed in on the new one.
Can I move between iPhone and Android?
Yes. Your account works identically on either platform because it is server-side. Only the installation method changes: Android uses an APK file with install permission granted, while iOS typically uses a configuration profile or web-app install. Tell your agent before you switch so you get the right link.
Can I use Panda Master on two phones at once?
Generally not simultaneously. Signing in on a new device usually signs the old one out automatically, which is normal behaviour rather than an error. During a changeover, use one device at a time and do not treat a balance shown on the old handset as current.
My new install will not accept my login. What now?
Check the username character by character for digits misread as letters, watch for autocorrect capitalising the field or adding a trailing space, confirm you installed a current build rather than an old saved file, and try switching between Wi-Fi and mobile data. If all four are clean, contact your agent with your username, device model, download source and the exact error text.