Again and again? You seem to have a serious memory loss

You've already asked this same question 3 times already, two threads and one reply:
1 (reply): Re: Bitcoin wallet
2 (thread): Bitcoin wallet
3 (thread): Wallet reader

The last one have the most accurate replies to this question including answers your "XY problem".

Since you phone is rooted, you must make a complete backup of mycelium including the data files using a reputable "full backup software" (eg. but not recommended: Titanium Backup)

I've tried it, yes mycelium just shows the message "syncing please wait" when I click "Export account keys".

But it worked after I force close mycelium in the "settings->apps", closed all data/WiFi connections (and/or enable Airplane mode).
Then I launched mycelium while offline, it allowed me to export the master private keys (xprv/yprv/zrpv).

If it didn't worked at your end, try clearing the cache as well but NOT the data.

Maybe that's because the site database wasn't yet updated to the latest blocks where your transactions are included.
As I've said, there's a note below the page that states the last analysed height.

If it's option 1, it will only generate three UTXO to virgin wallet that isn't much of an issue.

When wallet A sends all of its balance to "virgin wallet", the transaction already consolidates all of its inputs. So as wallet B and C.
Just watch out for the fee rate if there are too many inputs.

1. What backup? If it's the seed phrase, you're going to be fine as long every word is correct. If it's Google/cloud backup, the wallet files aren't covered by it.

2. You can select the "account": from m/49'/0'/0'/0 ; use m/49'/0'/1'/0 for the next account, m/49'/0'/2'/0 for the third and so forth.

You can import the seed to electrum (electrum.org) by clicking "option->BIP39" on the enter seed window
and from there, specify the correct derivation path below the address type selection.

You shouldn't mess up with the path though as your main issue is "synchronization" and it has nothing to do with the derivation path.

---

-Edit-
It's better not to uninstall the wallet in case if there are recoverable data from it.
Have you tried installing the old version apk (if you have a backup) to your other phone and restore the seed there?

Depending on the number of available UTXOs.

If you have a ton of available inputs from those three "donator" wallets, option 1 may be a good choice.
On the other hand, if you only have one to three UTXO or more but for the same address,
creating dump file is better since you can import their private keys to the new wallet without too much hassle.

The implications that you wanna hear for option 2 is: the keys will be leaked and if your system is monitored, you might lose your funds.
At least export / import them while offline or in an "air-gap" PC.

If you decided to import make sure to add 'false' to the RPC command: eg. importprivkey "label" false except for the last one.
So your wallet wouldn't proceed to 'rescan' on every import.
Personally, I'd choose option 1.

Walletexplorer is automatic in terms of address linking,
When you pasted an address, it will show which wallet it belongs and you can check all of the wallet's addresses by clicking "show wallet addresses".

It automatically include an address to a specific wallet if the address was used together as an input with one of that wallet's address.
Just take note of the latest block update below the page, most of the time, it's delayed.

When checking for compatibility, look at the miner's algorithm.
Antminer Z11 is for "Equihash" algo while ETC (Ethereum Classic) is "EtHash", so it isn't compatible.

If you're targeting Ethereum/Ethereum Classic for ASIC mining, it's a bad choice IMO.
They are known to fork whenever there's an "ASIC risk"; if they fork after you bought your ASICs, you'll end up mining another coin.

This is new to me, I though it will add '0' in front of 007d7 to be valid because it's odd-digit; instead, it resulted to 'G....'

---

If you want to put a random value, it should be 20 byte HEX or 40 (1-0, a-f) characters.

It isn't required.
You can undo (disable) it by restoring the seed, but creating a new standard electrum wallet and sending all of your balance to that wallet is better.

Take note that that fee includes the service payment the next 20 transactions that you will make,
means that you won't be charged for the next and consecutive transactions.

BTW, to confirm that it's 2FA fee, double-click the transaction date from the history and see if that output is highlighted in blue.

Turns out it isn't a problem with my or your connection, and seems to be a delay that exceeded the default timeout.
There's nothing to configure in my PC/network since I'm positive that it's relatively fast.
If you can't directly browse to https://electrum.org/version, it could be a different issue.

Following the issue (#5899), SomberNight have given a simple command to execute in the console.
There's no reply since then.

You can try that and if you like, contribute your results.

The one that you should contact is Paxful not Poloniex as it's where your USDT is.

The major problem however is they have a previous post about not recovering wrongly sent coins, specifically BCH sent to BTC;
Here's the post: https://twitter.com/raypaxful/status/988624672529858560

Your issue is similar but you should contact their support anyway.

Breathe in and relax, then take your time to read the contents of this thread.

Most of the information are already posted here, it's up to Abra if they will give you an honest answer, hopefully the correct derivation path.
Or wait for @Heisenberg_Hunter's test if he can guess the correct path as he had successfully reproduced your issue.

You can post the address here but not the seed.

It's either they are lying or the customer support wasn't aware that getting the private key of your BSV address can restore the same address to a Bitcoin client/wallet,
All you need to do is to restore the seed phrase to other BSV wallet and export the address prv keys to a bitcoin wallet.
BTW, either of the two addresses don't have any transaction from the two chains
What's the exact address where you've sent your BTC?

Point these out or quote this (and provide a link to this thread):
Abra claims that their wallet is "non-custodial", then it should possible to restore the address to a different client that supports the backup [13word(-1) BIP39 seed].
You just need to know which "derivaton path" Abra is using for Bitcoin SV to restore your BSV address(es) to other wallets.

If you know the derivation path (something like: m'/0'/0), it's easy.
Too bad, every reddit thread that I've found about this issue ended up with non-recovered funds.

Then there's a high chance of recovering your funds. It's a legacy address and importing its private key to Electrum wont be troublesome.
Now, contact their support regarding those info above because they said that they have a custom derivation path in order to get that private key from your seed.

If it's really a non-custodial wallet, then there's a way to recover the funds,
Again, does your Abra's BTC address starts with '3'?

To confirm the info from DdmrDdmr's reddit link, ask them (Abra's Customer Support) these:

• The derivation path for your Bitcoin SV [BSV] account.
• If the 13-word seed is BIP39.

Just do not share the seed here, those info are enough to be able to recover your Bitcoins.

The address is not the wallet, you have just created a "watch-only imported wallet" by putting the Bitcoin address in Electrum.
You won't be able to do anything using that but monitor your funds.

---

Does your Abra's BTC address starts with '3'?

P.S: I was going to try the app to check every derivation path but it's asking for too much information including name, email and mobile number to create a supposed "non-custodial wallet".
Just contact their support to give you the best advice.

These aren't necessary, in fact #1 will even make it seem disconnected until you've re-downloaded the headers.

Try to disable your firewall and/or AV temporary to see if its blocking your connection.

If disabling the firewall worked, create an exception for Electrum, then enable your firewall.
If disabling the AV worked, create an exception as well.

I was using Cloudflare's DNS prior, then changed to Google's, restarted the router and the issue still persists.
Based from other's replies, I think this is an issue with my and OP's ISP, router, PC or other network setting; not Electrum.

@StrongCore I'll post it here if I found the issue.

Me or the OP? Me, I've tried it and it prompted to download the version file.
I forgot to mention it here but I have included it in issue #5899. The details are in the link I provided.