If you do not want to or can't update your Electrum (since it's not too old, seed_version 32 by v4.0.2 ~ 4.0.7)
Restoring it from seed should do the trick, you'll lose your contacts and labels if you have those, though.

This what the developers or at least the author of electrum's official documentation say about that matter:
https://electrum.readthedocs.io/en/latest/seedphrase.html#motivation

In short, yes "it's better" for them but not in a "roll your own" way because BIP39 was just new before they implemented v2.0 electrum seed.

You're welcome.
You can get back here or in the Bitcoin Technical Support board if you can't find any support in your local board.

You've sent a transaction so it must be in your "change address" instead of the address where the funds are from.

If you want to import the whole BTC wallet, not just the address, you can import the "seed phrase" (12/24-words) instead of a single private key.
Select "legacy" or "P2PKH" if the wallet prompted you to select script/address type.
That's if the wallet where you're importing supports BIP39 seed.

From Jaxx to which wallet?
What type of bitcoin address are you trying to import (starts with what letter/number)?

Because almost all wallets do not automatically import/sweep from all the possible script types.

:-\ "uncheck" means "remove the check" in the box.
If it's now unchecked, the value (2GB) that you're seeing is now grayed-out, it won't be used because pruning is now disabled and you cannot edit it.
If it's checked, pruning is still enabled.

You can also post a thread in your local board to speed things up, there, users post at your local timezone so they can reply as soon as you post.
Plus you can use your native language there.
Local Boards: https://bitcointalk.org/index.php#5 | Use Other languages/locations if your language doesn't have a local board.

I shouldn't have used the word "version".
I mean, the "release version" apk's may be different than the uploaded binaries in the Playstore.
If those are different, it might fail to install-over the currently installed old version.

I don't have an old Android jellybean device to test but, you can check which version will work from the downloads archive page of Electrum:
Link: https://download.electrum.org/

The lowest version that can connect to servers is version 3.3.4, download the file "Electrum-3.3.4.0-release.apk" and install it to your phone.
Problem is, the version in the website may be different than what they've released in Playstore so you might encounter errors during installation.

I see, so the main disk doesn't have enough space for the blockchain that's why pruning is enabled.

You can use your 'disk D' as the data directory then disable pruning in Bitcoin-qt's setting:

• Open Bitcoin Core (bitcoin-qt) and open the settings: "Settings->Options..."
• Click "Open Configuration File" below and 'bitcoin.conf' will open using your notepad.
• Type/Paste: datadir=D:\Bitcoin into that text file, save it, then close it.
• Lastly, uncheck "Prune block storage to" to disable pruning (I have already told you this when you're just starting the sync process).

Restart Bitcoin core to reload the config file and it will sync from scratch after that.
That's all you need for now, wait until it's fully synced, then you can always use importprivkey to your 'blank wallet' if you found more keys.

If those are hashed with MD5, then you wont be able to reverse them easily since it's not reversible.
MD5 is broken so you may be able to bruteforce or exploit the vulnerabilities but that's a job for experts in that field.

If those are HEX, do the same procedure that you did to the previous four keys in the OP to encode them into WIF.
Then import it to your "blank wallet" using the steps I've mentioned in my previous post.

Make sure Bitcoin Core's prune setting is disabled so you can rescan after it's fully synced or you'll just waste your internet bandwidth and time.

There, you can find "Error:" and "Warning:" lines of text that will tell the reason why your Bitcoin Core is stuck at 89%.

Additional info: Windows10 may not be able to open a ".log" file directly as text so, select a text editor (like notepad) when it prompts you.
The debug log will be saved in the data directory, if you're not using the default - %appdata%/bitcoin, you should look in your custom bitcoin data directory.

Hmmm... unfortunately, I don't know how the old bitcoin.com worked and I have no idea about an old "China site" where you bought the bitcoins.
Armory is another Bitcoin client that only uses Bitcoin Core to download and verify the blockchain, here's its board if you want to know more about it: /index.php?board=97.0

It's complicated alright  :-X
Anyways, if those "four keys" are the same ones you've imported to Bitcoin Core, then let it sync so it can find the coins.
Bitcoin core is capable of checking all outputs of different script types derived from the private key.
If Bitcoin Core has fully synced and it has no balance, enter rescanblockchain command for the last time to make sure that it's really empty.

Other than that, I have no further response.

It means that your blockchain is set to be "pruned", it can't use rescan because it doesn't have the older blocks because 'pruning' will delete the older blocks after the set size was reached.

I don't know if it will be able to scan for balances (from the succeeding blocks) of your newly created wallet's imported keys because I haven't experienced that scenario.
If you have enough disk space for the blockchain and other data (about 400GB+), you can consider disabling pruning in "Settings->Options...->Prune block storage to".
Then restart the sync process.

Plus you need the whole blockchain in case you'll need to import other possible keys from your backup in case those four aren't private keys.

The order isn't important, the important part is to use the rescan flag only in the last key.

That's because the start parameter you added to bitcoin-qt wont be used by bitcoind or you're using it with default start parameters.
You mentioned that you've used the GUI to set the custom data directory.

Anyway, to make a global default, add datadir=YOUR_SSD_DATA_DIR to your "bitcoin.conf" file in the default data directory.
If you don't have a bitcoin.conf file there, create one.

Default bitcoin datadir: https://en.bitcoin.it/wiki/Data_directory#Default_Location

To change server:
Click the green circle icon at the lower-righthand side of Electrum,
Untick "Select server automatically", then right-click on a server of your choice and select "Use as server".

But if it's already green, changing the server wont be needed.

It's been two days but have you let Electrum open for a while and did not closed it right after checking the balance?
Because it needs time to download the blockchain headers.

If nothing checks-out: I highly suspect that you're looking at a different wallet file, if no, restored a different seed.

No, I mean select the second choice "Make Blank Wallet" not 'blank wallet name', you should put a wallet name or 'Create' button wont be clickable.

After creating the wallet, go to console (Window->Console). Select the blank wallet in the "Wallet:" drop-down menu.
Then type the commands, one at a time;
For the first three:
For the fourth key:
Change "Your_Private_Key" into those encoded WIF private keys.

Electrum needs the blockchain headers to function which it doesn't have initially.
So if it's the first time Electrum is used, it will have to download the said file which is about 55mb in size so you'll have to wait for it to be completed in the background.

But if about 10 minutes have passed, your internet is "good" and the Electrum's connection status is 'Green' (lower-right circle),
then the imported WIF keys are really empty (at least for P2PKH outputs).

It barely reached the year when compressed public key was introduced to Bitcoin client,
If it's before April 2012, you shouldn't be looking for compressed addresses because it's not available in the client at that time.

You may have to search for P2PK outputs as well, which doesn't have an address but the public key itself.
IDK any other client that support it aside from Bitcoin Core; if you want, you can import those keys to Bitcoin Core but it will require you to download and verify the blockchain before you can check for balance.
Your transactions are quite early so you'll likely see the transactions earlier in the sync process if it has any balance.

Import command (do right after creating a "Blank Wallet"): https://bitcoincore.org/en/doc/0.21.0/rpc/wallet/importprivkey/
Use "false" rescan flag for the first three, then "true" to the last one.

You can now import those to a wallet of your choice, or my suggested client: Electrum.
If you use Electrum, let the wallet open for a few minutes for it to sync (blockchain headers - 55mb file).
If there's no balance, those may not be private keys or those are for compressed public keys, in that case, use the tool in the post above.

One by one; pasting them all will produce invalid result.
The result should be similar to the WIF (Wallet Import Format) displayed in the linked thread above, it should start with '5'.

A wallet can import/export multiple private keys, you may have exported those 4.

Yes, if those are private keys, the next step to be able to import those to a wallet is to convert them into WIF (base58check).
The easiest way is to use a converter tool.

This one should work (brainwalletx.github.io/#converter) but must be used in an offline environment and downloaded & run from source.
To convert the keys, go to "Converter" tab, copy your PrvKey (HEX) into the "Source Text", then select "B58Check" in the 'Convert To' tabs.
The result should be the private key in WIF format, depending on the age of those keys, you may or not need to convert them into compressed WIF.

Then import those keys to a wallet, I'd suggest Electrum (electrum.org).
Here's the steps to verify Electrum (recommended before using it): https://bitcoinelectrum.com/how-to-verify-your-electrum-download/
Here's the steps for importing keys: https://bitcoinelectrum.com/importing-your-private-keys-into-electrum/

Note: Do not share the private keys.