Fixed the duplicated chats issue (WazzapMigrator 10.4.1)
Update to my previous post: the duplicated chats issue is now resolved.
After opening a ticket with WazzapMigrator support, they confirmed the problem and released the 10.4.1 version.
The fix
WazzapMigrator 10.4.1 addresses the root cause of the duplicated chats and the “new account” error.
What changed in 10.4.1:
-
Fixes the identity conflict that left my number linked to two different accounts on WhatsApp’s servers.
-
Requires a fresh migration from scratch (no way to patch an existing installation).
How I applied the fix
-
Downloaded WazzapMigrator 10.4.1 (APK provided by their support).
-
Used the same
ChatStorage.sqliteandMedia.zipfiles from the first migration. -
Uninstalled WhatsApp and cleared its data.
-
Ran the migration again with the new version (~1 hour).
-
Reinstalled WhatsApp from Aurora Store (with Google account, not anonymous).
-
Restored the history using the same Airplane Mode trick to force local backup reading.
-
Verified that I can now send messages from any old chat without duplication.
Result
-
Full history:
Restored. -
Duplicated chats:
Eliminated. -
Sending messages:
Working. -
Recent messages (from the last 7 days until I solved the problem):
Lost (accepted as trade-off for the fix).
The error “This phone number is connected to a new WhatsApp account” no longer appears.
Consider that:
-
The official WhatsApp transfer method does not work on /e/OS.
-
WazzapMigrator works, but you need the latest version (10.4.1 or newer) to avoid the duplicated chats issue.
-
The fix requires a fresh migration. You can’t patch an existing installation.
-
Use Aurora Store with your Google account, not in anonymous mode.
-
If you see the “new account” message, it means you need the updated version.
Thanks to the WazzapMigrator team for identifying the issue and releasing the fix.