Sorry, i have meant: release 2021.04.25 and it is there.Is your RQ2A.210405.005 a different version of crDroid from another maintainer? On Eremiteins download site there is no version from 2021.04.05. If yes, you should make a clean flash. Depending gapps, I always used the vanilla-roms and flashed gapps after that because you can mostly choose the package size and do not have to install every google app.
I just double checked and I think I'm having the same issue as you now. I was able to reboot to TWRP 3.5.2_9-0 with no issue, even after installing A12 rom but before creating a PIN code to unlock. But after doing that, now TWRP just bootloops. So it does appear that the encryption in A12 causes this version of TWRP to not be bootable. Darn. So anyway, word of warning to anyone flashing A12, be sure to flash Magisk in TWRP before you set a PIN code during initial setup (that's when the data partition is officially encrypted).So that means after flashing A12 rom you are able to boot into TWRP the normal way?
As you are on CrDroid, you can simply flash a newer version over the older one from within TWRP and after that Magisk again, without erasing data etc. All to both slots. If you use a bgz version now you should dirty flash the same. If you want to change to bvz version without Google apps I think it will be better to do a clean flash.
I figured it out. While the TWRP screen was bootlooping, I used a USB cable and ADB command "adb reboot bootloader" to get into bootloader mode. Then the only thing I found that would kick me out of the recovery bootloop was to select "Boot to FBMI" which I am not sure what that is, but it did actually boot system finally. Whew, I was afraid I would have to use the firehoses to start all the way back at international again.Edit: Well now I am stuck in TWRP bootloop it seems. I tried using 'adb reboot system' and 'adb reboot bootloader' then selecting Start, but it always boots into TWRP. Any idea how I can force it to boot into System again?
That's a legit concern for some people. I used to use TWRP all the time, but these days I don't take backups or flash much anymore. As long as I have Magisk working, I can use SwiftBackup for 99% of what I need. This being mostly just an eReader and Youtube device for me, at any rate.
Not yet, but I can only imagine how laggy it would be. I'm on A12 PixelExperience right now, and planning to roll back to the previous ROM because the UI is just too unresponsive in comparison.Has someone tested with one of the A13-roms?
Thank you for reply. I'll try again.Hm, is your bootloader unlocked? If not, please follow the modification guide in post 1. I recommend to do it with chinese rom 20200522. After unlocking you should be able to flash the modified global rom. If your bootloader is already unlocked, I don't know any advice now, but search this thread for "corrupt", I remember there were some posts depending this issue years ago.
Thanks. I'll try)Afaik no. You can try to flash a 3.7.0 TWRP for similar SDM660 devices (Xiaomi Mi Pad 4, Redmi Note 7 etc.), there are some official versions at the TWRP site. But due to different drivers in the kernel or other differences it is possible that some parts of the X Neo don't work after that (e.g. wifi). But please give it a try and report here.