Redmi Note 8T (Ginkgo) stuck in fastboot mode after eOS 2.1 update (from 1.21)

Yes, this phone has been a bit unlucky with respect to /e/. First we had broken builds for maybe half a year and hence were locked out of security updates, then one update sent Bliss Launcher into a crash loop for a month or two for me, making it temporarily unusable, and now this 2.0 update.

I think the issue is just that the development team doesn’t have a phone of this model to test on. I guess community devices will get more stable as the project grows.

I went back to 1.21 for now by first flashing the old recovery and then the old version, plus a few other things. This allowed me to keep all data. I detailed the process in this post. Backups are still highly recommended of course.

I did the flashing from Linux (Mint) since it’s way too annoying to deal with Windows and trying to get it to recognize drivers and such. If you run into too much trouble on Windows, a live version of your favorite Linux distribution that you can boot from a USB thumbdrive would probably suffice.