fastboot devices
fastboot flash boot boot.img
fastboot flash vbmeta vbmeta.img
fastboot flash recovery recovery.img
fastboot reboot
OK, that’s what I’d tried and it didn’t work. So, does this mean my only option is to completely reinstall the Android 11 firmware?
Thank you all once again @Xxpsilon @aibd & @nanabanaman 
very much appreciated
Yes, because all my other rescue attempts (like yours) have failed. By the way: crDroid 10.5 with MinMicroG works perfectly on my “willow”.
1 Like
I got this error message after running the .bat file:
fastboot getvar product 2>&1 | findstr /r /c:"^product: *willow" || echo Missmatching image and device
Have I missed a step somewhere?
In that step, I took boot.img from the ZIP file with the installation image that is offered for download and flashed the boot.img file manually using fastboot flash boot ./boot.img because I couldn’t boot into the /e/ recovery to flash the entire zip file using adb sideload since the 1.21 recovery had been replaced with the possibly broken 2.0 /e/ recovery. But I don’t think what I did there contributed anything to solving the issue, I was just trying random things at that point, in fact, it may have done more harm than good.
As I described, I ultimately got it working by first flashing the /e/ recovery for version 1.21 and after that I was able to get into recovery by doing fastboot reboot recovery. Once I was in recovery, I could see the error message about the cache partition.
Willow / ginkgo
My memory is that Lineage / /e/OS managed to “combine” the two devices but Xiaomi released them as individual models.
Retail Branding,Marketing Name,Device,Model
Redmi,Redmi Note 8T,willow,Redmi Note 8T
Xiaomi,Redmi Note 8,ginkgo,Redmi Note 8
If you let a .bat file work for you, you cannot overlook any steps because you cannot intervene directly in the process.
Missmatching image and device strongly suggests that you do not have a Redmi Note 8T (willow) in operation, but a Redmi Note 8 (gingko).
To check, please enter in fastboot mode:
fastboot devices #Check whether the device is detected and recognized by the computer
fastboot getvar product #get product name
What is the response?
That’s exactly how it is.
That’s why there are two stock firmware versions,
but still only one CustomROM version
- Latest dev ginkgo (willow)
/e/OS R builds to be stopped
With Google stopping security patches and LOS also dropping support for A11 …
As much as I like /e/ OS, with what happened recently I would like to use another ROM.
… but again the system only booted into
fastboot mode.
Hey,
a belated thank you to everyone who helped me with this. I lost my data and moved to crDroid in the end (via the official Redmi ROM as advised above). So, I was able to get my phone working again for my trip - big, BIG thanks!
Has anyone been able to get /e/ 2.1 working on the Gingko/Willow yet?
Cheers