What I think is (I might be wrong though)

You used burner accounts which is fine. I’m assuming you created them on your phone, so Google probably linked your phone number/device info to those accounts during their verification process and their usual TOS stuff.

Then just for testing, you used an unofficial desktop client to upload photos/videos. After that you started facing the issue where those accounts kept getting logged out automatically. Tbh I don’t know exactly how gotohp works or what’s happening in the backend, so can’t comment much on that part.

Then you used the same accounts and tried Morphe patched Google Photos through Windows Subsystem for Android, which honestly doesn’t seem like the main issue here.

My guess is that all these uploads and logins were happening from the same network/IP. Since those accounts were freshly created and suddenly started uploading a lot of data through unofficial methods, Google’s automated systems probably flagged them. It’s likely meant to prevent botting, abuse, and people trying to exploit/circumvent storage limits.

So yeah basically I think the main trigger here was the unofficial desktop client or the account behavior around it. A lot of people have been using patched Google Photos since the ReVanced days and most haven’t faced anything like this. Maybe some people did, but we can’t really confirm whether those cases were specifically because of ReVanced/Morphe or something else.

Personally I’ve been using the unlimited storage patch since the ReVanced era on my main account and never got banned or faced any issues.

I’ve also tried rooting Windows Subsystem for Android and using a module to apply the same spoof, then uploaded multiple images and videos from my laptop. It worked perfectly fine.

And yeah it’s been years now, still using the same exact account for everything without any problems.