Is that really nessessary? I used the a/b rom like before.5. Flash GSI slot-a only ROMs in TWRP
Did you flash it to both slots or only a? I can adjust the steps before I edit the guide. Any feedback is welcome.Is that really nessessary? I used the a/b rom like before.
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.Sorry, i have meant: release 2021.04.25 and it is there.
So how can i make a dirty flash to keep my apps? Any way for this?
Just flash .img files in slot A/B in fastboot? CrimsonKnight13 i would also need your help.
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.fawkesyeah I'm still at A11 and I think I will not update to A12 due to the difficulties TWRP still has with A12 up to version 3.62 even with not encrypted partitions. Some days ago version 3.70 was released with encryption support for A12, but this won't help us at the moment.
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?