Yeah, I’ve run into a similar situation—those older zkLogin-based Sui wallets (like from Suiet or Ethos pre-merger) can be tricky now that the Slush transition happened. Basically, since zkLogin wallets are tied to your OAuth identity provider (like Google), and don’t use seed phrases, recovering them outside the original dApp context needs a few extra steps.

Here’s what I’ve learned and what might help:

First, the key thing is: your account still exists on-chain, but you need to reconstruct the exact zkLogin session parameters (like the OAuth token, JWT, salt, and address seed) to be able to sign transactions again. Since Slush and most new wallets don’t support re-importing old zkLogin accounts directly (yet), you can’t just "add" that wallet like a seed phrase-based one.

But here’s a practical way forward:

• Try logging in via the original app you used (like Suiet or Ethos) if it still supports zkLogin with your Google account. Some still maintain legacy support.
• If that fails, you may need to wait for Slush or a new zkLogin-compatible tool to release a recovery bridge or migration path. There’s been talk of tools that let you connect with Google, re-generate the ephemeral keys, and access the funds again—but they’re not widely available yet.
• You can also check https://sui.io/zklogin or Sui Discord for the latest updates on zkLogin recovery or support.

If you do regain access temporarily, your best move is to transfer the assets out to a new wallet (like a seed phrase–based one on Suiet, Martian, or Slush) so you’re not locked out again if the zkLogin auth method breaks down completely.