Database Develop

Only boots to twrp

I tried to flash lineage iOS after wiping my resurrection ROM doing factory wipe and system data cache internal everything so I would start clean. When I flashed it said error 7 boot loader was out of date need to be updated. Tried to update my ROM but resurrection Remix has never done one update for my SMT713 . Re-flashed my twrp recovery backup with success but now will not boot into system. Will only boot to recovery. How do I fix this problem of not being able to boot into my system?

Same here...

Two solutions, either reflash TWRP with Odin or open up the terminal in TWRP and run the following:
dd if=/dev/zero of=/dev/block/platform/7824900.sdhci/by-name/misc count=1 bs=32
Then reboot
info from Reddit thread

Bmj09bj said:
I tried to flash lineage iOS after wiping my resurrection ROM doing factory wipe and system data cache internal everything so I would start clean. When I flashed it said error 7 boot loader was out of date need to be updated. Tried to update my ROM but resurrection Remix has never done one update for my SMT713 . Re-flashed my twrp recovery backup with success but now will not boot into system. Will only boot to recovery. How do I fix this problem of not being able to boot into my system?
Click to expand...
Click to collapse
CrashHouse said:
Same here...
Click to expand...
Click to collapse
Lineage OS requires boot loader NRD90M.T813XXU2BQD1 for versions from 4/26/17 forward. You can find the info in the thread at this link - https://forum.xda-developers.com/tab-s2/orig-development/rom-lineageos-14-1-t3543920/page34. Read post #338. You also need TWRP 3.1.0-1 flash Nougat updates. I suggest you read this thread thoroughly before doing anything. It has a lot of info on how to do the upgrades properly. https://forum.xda-developers.com/tab-s2/general/t813-nougat-official-update-t3592597
You can get by with just the boot loader files found here - https://drive.google.com/file/d/0B3i4Cdm8QYlLck5LU2dIRng2S2c/view.
Read, read, read before doing anything and you can't go wrong.

Thnx

Everything you said is good and true, but not really helpful for the immediate issue in the thread. The reboot recovery loop is acknowledged by the TRWP thread OP as a known bug along with the reflashing of recovery as a fix.

Psiuyo said:
Everything you said is good and true, but not really helpful for the immediate issue in the thread. The reboot recovery loop is acknowledged by the TRWP thread OP as a known bug along with the reflashing of recovery as a fix.
Click to expand...
Click to collapse
It is helpful if it keeps him from making the same dumb mistake. The problem all began when he flashed the latest Lineage without having the proper version bootloader. Although in my initial post I used the numbers for the T813, it is JUST AS APPLICABLE for the T713. Reflashing TWRP as a fix doesn't do squat for him if he tries to flash Lineage again without updating his bootloader or if he uses the wrong version TWRP. Just sayin'.

Need help with Me176c, fastboot.... 123# screen

My Asus memo pad 7 is stuck on fastboot.... 123# screen. I've tried temporary recovery and had success installation with lineage-14.1 but nothing changed. Please help. Thanks.

Did you have Lollipop installed before?
Also, do I understand it correctly that you're able to get into the temp recovery session?

Yes lollipop was installed and rooted long time ago, after the issue I decided to put it away. I did loads after that though, so I don't think lollipop is still there.
It was first at boot screen, got this fastboot... 123# after I flashed a fastboot image. Flashed loads of recoveries, systems and boot images before and after the fastboot issue.
Hope this helps you understand the state it's in. Thanks for replying.

MJMJ7 said:
Yes lollipop was installed and rooted long time ago, after the issue I decided to put it away. I did loads after that though, so I don't think lollipop is still there.
It was first at boot screen, got this fastboot... 123# after I flashed a fastboot image. Flashed loads of recoveries, systems and boot images before and after the fastboot issue.
Hope this helps you understand the state it's in. Thanks for replying.
Click to expand...
Click to collapse
If the tablet boots into the screen with the 3 fastboot lines you are in DNX mode, which means you've likely messed up your bootloader. To restore the bootloader, follow the steps outlined in https://forum.xda-developers.com/showpost.php?p=73672837&postcount=5
If everything works, you should get to a second Fastboot screen with NORMAL BOOT etc. From there you can either start the temporary TWRP recovery session (see https://forum.xda-developers.com/showpost.php?p=73673438&postcount=7) to flash the Lollipop package you've downloaded earlier (UL-K013-WW-12.10.1.36-user.zip) or flash LineageOS.
If you want to flash LineageOS you need to unlock your bootloader. Download https://www.androidfilehost.com/?fid=312978532265362065, take the ESP.img from the ZIP and download https://github.com/me176c-dev/devic...recovery-3.1.1-20171119-UNOFFICIAL-me176c.img. Then run:
Code:
fastboot flash ESP ESP.img
fastboot flash recovery twrp-recovery-3.1.1-20171119-UNOFFICIAL-me176c.img
Power off your device, then press Volume Down + Power. Intel logo should show up, and ask if you want to go into recovery or fastboot. Go into recovery using Volume Down. Do a Factory reset again (it's under Wipe), then flash https://github.com/me176c-dev/devic...ge-14.1-20171119-UNOFFICIAL-me176c-signed.zip (e.g. put it on your external SD).

I will try these steps and update you. Thank you very much.

O yes! It worked. Tablet is now back in operation on lineageos. Going and get Gapps now. Thanks a lot lambdadroid

I believe my work on this tablet is not complete as I can't install Gapps. Installation failing every time. So I tried to reinstall lineage as this was installed before when I was trying all sorts to fix it.
Then when I followed the procedures you sent me, it booted into lineage after I unlocked the bootloader and installed twrp. So the system still had lineage from my fastboot installation attempts. What I can install now is the original version (ul k013 ww-12.10.1.36-user) and that works but I don't want this.
Any help on getting lineage to complete the installation? as it gets to the end with a little to go hut just never finishes (left this overnight)
Thanks.

lambdadroid said:
If the tablet boots into the screen with the 3 fastboot lines you are in DNX mode, which means you've likely messed up your bootloader. To restore the bootloader, follow the steps outlined in https://forum.xda-developers.com/showpost.php?p=73672837&postcount=5
If everything works, you should get to a second Fastboot screen with NORMAL BOOT etc. From there you can either start the temporary TWRP recovery session (see https://forum.xda-developers.com/showpost.php?p=73673438&postcount=7) to flash the Lollipop package you've downloaded earlier (UL-K013-WW-12.10.1.36-user.zip) or flash LineageOS.
If you want to flash LineageOS you need to unlock your bootloader. Download https://www.androidfilehost.com/?fid=312978532265362065, take the ESP.img from the ZIP and download https://github.com/me176c-dev/devic...recovery-3.1.1-20171119-UNOFFICIAL-me176c.img. Then run:
Code:
fastboot flash ESP ESP.img
fastboot flash recovery twrp-recovery-3.1.1-20171119-UNOFFICIAL-me176c.img
Power off your device, then press Volume Down + Power. Intel logo should show up, and ask if you want to go into recovery or fastboot. Go into recovery using Volume Down. Do a Factory reset again (it's under Wipe), then flash https://github.com/me176c-dev/devic...ge-14.1-20171119-UNOFFICIAL-me176c-signed.zip (e.g. put it on your external SD).
Click to expand...
Click to collapse
I believe my work on this tablet is not complete as I can't install Gapps. Installation failing every time. So I tried to reinstall lineage as this was installed before when I was trying all sorts to fix it.
Then when I followed the procedures you sent me, it booted into lineage after I unlocked the bootloader and installed twrp. So the system still had lineage from my fastboot installation attempts. What I can install now is the original version (ul k013 ww-12.10.1.36-user) and that works but I don't want this.
Any help on getting lineage to complete the installation? as it gets to the end with a little to go hut just never finishes (left this overnight)
Thanks.

MJMJ7 said:
I believe my work on this tablet is not complete as I can't install Gapps. Installation failing every time. So I tried to reinstall lineage as this was installed before when I was trying all sorts to fix it.
Then when I followed the procedures you sent me, it booted into lineage after I unlocked the bootloader and installed twrp. So the system still had lineage from my fastboot installation attempts. What I can install now is the original version (ul k013 ww-12.10.1.36-user) and that works but I don't want this.
Any help on getting lineage to complete the installation? as it gets to the end with a little to go hut just never finishes (left this overnight)
Thanks.
Click to expand...
Click to collapse
No need to reply twice.
Please clarify: What exactly is failing? The LineageOS ZIP or the OpenGApps ZIP? Do you get an error during installation or does it never finish the boot after installation?
Things you can try: Check TWRP log for errors (usually marked red if you click the bottom right button in TWRP). Try a factory reset in TWRP.

lambdadroid said:
No need to reply twice.
Please clarify: What exactly is failing? The LineageOS ZIP or the OpenGApps ZIP? Do you get an error during installation or does it never finish the boot after installation?
Things you can try: Check TWRP log for errors (usually marked red if you click the bottom right button in TWRP). Try a factory reset in TWRP.
Click to expand...
Click to collapse
Just thought you wouldn't be notified if I don't quote.
The gapps file is giving an error and failing, the lineageOS just stalls and never complete the installation.
I will try again now.....

patching system image unconditionally....
This is going on and on, about 10% left to complete but it never does. LineageOS installation.
Updater process ended with ERROR: 1
Error installing zip file '/external_sd/0-System zips/
Asus Memo pad 7 K013/gapps 7.1.zip'
And that's what I'm getting from the gapps installation.
Installation failed.

Got the Gapps to install, had to choose x86 version. Still no improvement from lineage.

MJMJ7 said:
patching system image unconditionally....
This is going on and on, about 10% left to complete but it never does. LineageOS installation.
Updater process ended with ERROR: 1
Error installing zip file '/external_sd/0-System zips/
Asus Memo pad 7 K013/gapps 7.1.zip'
And that's what I'm getting from the gapps installation.
Installation failed.
Click to expand...
Click to collapse
Maybe the file wasn't downloaded/copied properly. Enable ZIP file signature verification in the TWRP settings and flash the LineageOS package again. Does it print "Zip signature verified successfully"?

lambdadroid said:
Maybe the file wasn't downloaded/copied properly. Enable ZIP file signature verification in the TWRP settings and flash the LineageOS package again. Does it print "Zip signature verified successfully"?
Click to expand...
Click to collapse
Did it again with another copy and enabled the verification and all came out successfully. Thanks for your help.:good:

Decryption unsuccessful, the password you entered is correct, but...

After installing Nitrogen OS and gapps, I have restarted the phone and the following message appears:
Decryption unsuccessful, the password you entered is correct, but unfortunately your data is corrupt. To resume using your phone, you need to perform a factory reset. When you set up your phone after the reset, you'll have opportunity to restore any data that was backep up to your Google Account
I have formatted all the partitions, I have repaired them, I have reinstalled the operating system again and the same thing keeps appearing ...
TWRP is updated.
Help me! Thank's!

Jonny6921 said:
After installing Nitrogen OS and gapps, I have restarted the phone and the following message appears:
Decryption unsuccessful, the password you entered is correct, but unfortunately your data is corrupt. To resume using your phone, you need to perform a factory reset. When you set up your phone after the reset, you'll have opportunity to restore any data that was backep up to your Google Account
I have formatted all the partitions, I have repaired them, I have reinstalled the operating system again and the same thing keeps appearing ...
TWRP is updated.
Help me! Thank's!
Click to expand...
Click to collapse
Perhaps you should say which version of NitrogenOS you're using. Also asking in Nitrogen's thread has a higher chance of answers for your question.

I wonder if you think wipe is the same as format. That is not always the case. You need a real format of the data partition.

runekock said:
I wonder if you think wipe is the same as format. That is not always the case. You need a real format of the data partition.
Click to expand...
Click to collapse
Additionally TWRP's format function is broken.

Try "fastboot format userdata" if TWRP isn't properly formatting.

Elektroschmock said:
Additionally TWRP's format function is broken.
Click to expand...
Click to collapse
Can you elaborate on this?
I usually try to erase and format in fastboot anyway. But fastboot throws a can't format raw partition or something like that.

format (not wipe) data or use oreo builds
i've already done it
upgrade your twrp if it keeps failing, i'm using the latest release

Can someone help here? I followed all of the necessary steps to install LineageOS 16 on the Nexus 6 using TWRP and I am having this problem. I am not supremely skilled when it comes to these things, but I did it very carefully and made sure to read the instructions many times and go step by step as indicated. I was really looking forward to injecting new life into my N6, but now I basically have a brick.

Flaco05 said:
Can someone help here? I followed all of the necessary steps to install LineageOS 16 on the Nexus 6 using TWRP and I am having this problem. I am not supremely skilled when it comes to these things, but I did it very carefully and made sure to read the instructions many times and go step by step as indicated. I was really looking forward to injecting new life into my N6, but now I basically have a brick.
Click to expand...
Click to collapse
Without explaining what the problem is, it is hard to help you. Since you are using TWRP, you should have backup to restore.

Thank you for replying. I have the exact problem described by OP. And yes, I have a backup, so technically not bricked, you are right. Just very disappointed that following the flashing instructions let to this problem. Thank you again.

With great respect, I doubt that you actually followed the instructions as closely as you think. Unless your N6 has a hardware problem, the instructions will be correct - and I say this not knowing which instructions you followed, but any bad instructions are generally corrected pretty quickly.
To recap (and anyone please correct or amend anything for accuracy - I'll write this from memory):
- download TWRP 3.3.1 from https://twrp.me/motorola/motorolanexus6.html
- flash it in Bootloader - fastboot flash recovery twrp.img
- while you're there, format data - fastboot format userdata (you can also do this in TWRP, but as Elektroschmock says that TWRP formatting isn't perfect...)
- boot into recovery
- wipe everything - all partitions
- transfer your ROM & Gapps - and Magisk if you want root - to your device (recovery allows a direct connection to your PC)
- flash ROM, Gapps, Magisk
- reboot
- report back
Edit: One more thing just in case. If you get a "can't mount system" message, go back to TWRP main screen, Mount, and ensure that the "system read-only" checkbox is unchecked.

Hi, that is exactly what I did! I have repeated the process with LineageOS 15.1 (and the matching GApps) and it worked. Might this be an encryption problem related to LinerageOS 16? And thank you for responding.
Incidentally, what GApps package is the one most recommend? I used Open GApps Stock, but some of the Google Apps are acting up.

I use Opengapps Pico Arm (not Arm64).
All I can say is that I've installed LineageOS 16 on 2 N5s, 2 N4s and a Lenovo 8" tablet, all with no problems at all. Your problem is not device-specific, since the original query was not for an N6, and I myself know about this "corrupt" problem because I suffered from it myself a year or so ago on my own N6. The procedure I specified has always worked 100% for me every time.

Looking at the LineageOS 16 thread, there is a specific TWRP linked, and MindTheGapps is also linked which is different than openGapps.
If you haven't decrypted by FORMATING user data (not wiping), that may also be a problem.

Thanks, ktmom. The format was part of my instructions, and Flaco05 says he did exactly that. Normally I don't use fastboot to format - I just rely on TWRP and it's worked fine.
I've always used the standard Opengapps Pico and TWRP 3.3.1, no special versions, and they have always worked flawlessly - never any problems. Still, since Flaco05 is having problems, I guess he has nothing to lose by trying the recommended versions...

Thank you all. I will try some of these things tomorrow. I love this community!

dahawthorne said:
With great respect, I doubt that you actually followed the instructions as closely as you think. Unless your N6 has a hardware problem, the instructions will be correct - and I say this not knowing which instructions you followed, but any bad instructions are generally corrected pretty quickly.
To recap (and anyone please correct or amend anything for accuracy - I'll write this from memory):
- download TWRP 3.3.1 from https://twrp.me/motorola/motorolanexus6.html
- flash it in Bootloader - fastboot flash recovery twrp.img
- while you're there, format data - fastboot format userdata (you can also do this in TWRP, but as Elektroschmock says that TWRP formatting isn't perfect...)
- boot into recovery
- wipe everything - all partitions
- transfer your ROM & Gapps - and Magisk if you want root - to your device (recovery allows a direct connection to your PC)
- flash ROM, Gapps, Magisk
- reboot
- report back
Edit: One more thing just in case. If you get a "can't mount system" message, go back to TWRP main screen, Mount, and ensure that the "system read-only" checkbox is unchecked.
Click to expand...
Click to collapse
OK, I did all this, but have been stuck at the Google screen upon reboot for 30 minutes. Is this bad news, or this normal?

No, definitely not normal. A new ROM takes longer to boot but it's generally ten minutes maximum.
Have you tried flashing only the ROM & Gapps, without Magisk? Once you boot successfully you can then flash Magisk later. Try starting again from the top and see if that works.
(P.S. In a slow quiet thread, as this one is at the moment, there's no need to copy the entire post to which you're replying... )
Edit: No, sorry, not from the top. TWRP will still be there after formatting & wiping, so start at the third (format data) part.

Thank you. There is still some kind of a problem. After I finish flashing ROM and Gapps using the instructions, and then reboot (after wiping cache/davlik, right?), I get the Lineage OS logo in motion, and then finally boots into recovery (not system) again. Not sure what to do. Maybe try a different build? I am currently using the latest LineageOS 16 nightly.

Strange. Maybe try LineageOS 15.1?
I enjoy playing with bleeding-edge software, but when you can't get it to work at all then it sort of ruins the fun. A lot of people seem to prefer the stability of 15.1. Personally I never see much difference between even major versions. Maybe I'm just a bit unobservant...

How to reset firmware

so i've tried a few roms, and couldn't get gpay working. im going to try a few things mentioned in other threads, but before i start that. i want to properly/fully reset my phone to the stock, to hopefully make sure i don't mess anything up in the future.
my first issue was installing twrp, i tried to `fastboot flash` the recovery, but nothing worked until i followed these steps: https://www.getdroidtips.com/download-and-install-twrp-recovery-for-redmi-k20-pro-latest/
im worried about what might be in the misc.bin in that zip. cuz i couldn't reboot into twrp recovery until i flashed that. does anyone know what that is? i think i just want to flash/reset? everything on my phone back to miui, make sure i update to the latest firmware etc. but, tbh, i find navigating xda difficult and can't seem to find the official firmware anywhere, or steps on how to reset the phone...
thanks for any help

Um, i think ur in the wrong category

thejacer87 said:
my first issue was installing twrp, i tried to `fastboot flash` the recovery, but nothing worked until i followed these steps ...
im worried about what might be in the misc.bin in that zip. cuz i couldn't reboot into twrp recovery until i flashed that. does anyone know what that is?
Click to expand...
Click to collapse
The misc.bin file is basically just a script that tells the Device to directly boot into TWRP, because Xiaomi Devices / MIUI are configured to overwrite TWRP after a reboot. If you still feel uncomfortable having to flash the misc file, try "fastboot *BOOT* TWRP.img" instead of "fastboot *FLASH* TWRP.img".
If you wish to keep MIUI installed instead of an Custom ROM make sure to flash Magisk, as it patches the DM-Verity stuff that causes the Device to either get stuck in a Bootloop or replace TWRP with the Stock Recovery.
If you're planning to run an Custom ROM like LineageOS, AOSiP etc. you don't have to flash Magisk as long as your Device isn't encrypted. Rebooting from TWRP to System without flashing Magisk on an encrypted Device will encrypt your Data Partition and you'll have to format Data to be able to access the Internal Storage again. (Flashing Magisk in that case will prevent your Device from encrypting all your Data again after an ROM Flash.)

Fatal_Scythe said:
The misc.bin file is basically just a script that tells the Device to directly boot into TWRP, because Xiaomi Devices / MIUI are configured to overwrite TWRP after a reboot. If you still feel uncomfortable having to flash the misc file, try "fastboot *BOOT* TWRP.img" instead of "fastboot *FLASH* TWRP.img".
If you wish to keep MIUI installed instead of an Custom ROM make sure to flash Magisk, as it patches the DM-Verity stuff that causes the Device to either get stuck in a Bootloop or replace TWRP with the Stock Recovery.
If you're planning to run an Custom ROM like LineageOS, AOSiP etc. you don't have to flash Magisk as long as your Device isn't encrypted. Rebooting from TWRP to System without flashing Magisk on an encrypted Device will encrypt your Data Partition and you'll have to format Data to be able to access the Internal Storage again. (Flashing Magisk in that case will prevent your Device from encrypting all your Data again after an ROM Flash.)
Click to expand...
Click to collapse
k thanks for the info. what's the difference b/w the boot v flash for twrp?
is the misc.bin from that link i posted safe then? where did it come from? is there a thread here where files like that are posted/talked about?
i definitely plan to stick with either lineage or Pixel experience. i just want to get google pay going. so i think my next attempt will be to relflash magisk and look into that sql fix everyone mentions

thejacer87 said:
so i've tried a few roms, and couldn't get gpay working. im going to try a few things mentioned in other threads, but before i start that. i want to properly/fully reset my phone to the stock, to hopefully make sure i don't mess anything up in the future.
my first issue was installing twrp, i tried to `fastboot flash` the recovery, but nothing worked until i followed these steps: https://www.getdroidtips.com/download-and-install-twrp-recovery-for-redmi-k20-pro-latest/
im worried about what might be in the misc.bin in that zip. cuz i couldn't reboot into twrp recovery until i flashed that. does anyone know what that is? i think i just want to flash/reset? everything on my phone back to miui, make sure i update to the latest firmware etc. but, tbh, i find navigating xda difficult and can't seem to find the official firmware anywhere, or steps on how to reset the phone...
thanks for any help
Click to expand...
Click to collapse
If you're planning to go back to stock MIUI and locked bootloader, I highly recommend using Mi Flash and flashing the original fastboot MIUI ROM which can be found here https://www.xda-developers.com/download-miui-11-xiaomi-redmi-note-7-pro-poco-f1/amp/. All you gotta to do is extract the ROM file which is .tgz to any folder, and in Mi Flash select that folder click on "clean all and lock" in the bottom right corner, and click flash. This should theoretically make your device "out of the box".
Keep in mind that this method requires a PC with all ADB and fastboot drivers, they can be downloaded from here https://forum.xda-developers.com/showthread.php?t=2588979 .

thejacer87 said:
k thanks for the info. what's the difference b/w the boot v flash for twrp?
is the misc.bin from that link i posted safe then? where did it come from? is there a thread here where files like that are posted/talked about?
i definitely plan to stick with either lineage or Pixel experience. i just want to get google pay going. so i think my next attempt will be to relflash magisk and look into that sql fix everyone mentions
Click to expand...
Click to collapse
BOOT will just let the Device temporarily boot into the Recovery (without making changes to the Recovery Partition) FLASH will write the Recovery Image to the Recovery Partition so you can boot to it whenever you want / need to.
I don't know if there's any kind of threads where certain files are talked about sorry, but I could be wrong though.
I don't know much about G Pay, I was gonna try it too but my Bank doesn't support it. I've seen quite a few people reporting success in getting it to work / making payments with it in local stores with the mentioned SQL Fix so if you're lucky it'll work for you too

Fatal_Scythe said:
BOOT will just let the Device temporarily boot into the Recovery (without making changes to the Recovery Partition) FLASH will write the Recovery Image to the Recovery Partition so you can boot to it whenever you want / need to.
I don't know if there's any kind of threads where certain files are talked about sorry, but I could be wrong though.
I don't know much about G Pay, I was gonna try it too but my Bank doesn't support it. I've seen quite a few people reporting success in getting it to work / making payments with it in local stores with the mentioned SQL Fix so if you're lucky it'll work for you too
Click to expand...
Click to collapse
just got gpay to work with the sql fix. thanks for the help

Question Stuck in Bootloop any help?

After the Jan update to crdroid 9 I have been completely unable to load twrp back onto my phone. I have never had any problems with this before, but now after trying for the third time I am stuck in my third bootloop. I have tried 'install current twrp' 'install to ramdisk' and used two different versions of twrp the result is always the same, stuck in fastboot. So first question - is there a way to get out of the bootloop without having to do a third factory reset because they are doing my head in? Second question - is there a way to get twrp installed any more on this rom? I tried changing slots but it makes no difference. Because it is stuck in fastboot I can 'fastboot boot twrp' to do any flashing/wiping that may be necessary, but so far I have only been able to get the phone back with a factory reset. Any help appreciated.

viking777 said:
After the Jan update to crdroid 9 I have been completely unable to load twrp back onto my phone. I have never had any problems with this before, but now after trying for the third time I am stuck in my third bootloop. I have tried 'install current twrp' 'install to ramdisk' and used two different versions of twrp the result is always the same, stuck in fastboot. So first question - is there a way to get out of the bootloop without having to do a third factory reset because they are doing my head in? Second question - is there a way to get twrp installed any more on this rom? I tried changing slots but it makes no difference. Because it is stuck in fastboot I can 'fastboot boot twrp' to do any flashing/wiping that may be necessary, but so far I have only been able to get the phone back with a factory reset. Any help appreciated.
Click to expand...
Click to collapse
I should first try to reflash the firmware for your device. That's something to try first.

Just flash other ROM and wipe data. If doesn't help, flash firmware for your device like @minionguy said.

Update - I got back to a working system without a factory reset by fastbooting twrp going to restore and restoring the boot partition only from my latest twrp backup, so that answers Q1. As for Q2 (how to get twrp installed I still don't know how to do that).
Thanks for the replies btw. I think if that is the only way to install twrp I will have to live without it for now. I know I am not the only one with this problem there have been other reports elsewhere. Somebody suggested sideloading, but I can't find a zip file for the twrp version I am using ( twrp-3.7.0_12-0-spes-A12-dblenk9) and this is the only version I have found that works properly since it successfully decrypts data whereas the other versions I have used don't even bother to try, making them useless.

viking777 said:
Update - I got back to a working system without a factory reset by fastbooting twrp going to restore and restoring the boot partition only from my latest twrp backup, so that answers Q1. As for Q2 (how to get twrp installed I still don't know how to do that).
Thanks for the replies btw. I think if that is the only way to install twrp I will have to live without it for now. I know I am not the only one with this problem there have been other reports elsewhere. Somebody suggested sideloading, but I can't find a zip file for the twrp version I am using ( twrp-3.7.0_12-0-spes-A12-dblenk9) and this is the only version I have found that works properly since it successfully decrypts data whereas the other versions I have used don't even bother to try, making them useless.
Click to expand...
Click to collapse
This is where I borked it myself, and with sideloading. Apparently, the semi-permanent instructions for TWRP on spes should work using twrp-3.7.0.img (96mb) and NOT twrp-3.7.0-12.1-06.11.22.img (128mb), as the latter is the JabiYeff version and is "unable to flash MIUI ROMs due to dynamic partitioning error" as of November 2022. I assume your dblenk9 version is 128mb? You have a link for it? Googling gives only this thread and a couple of Russian sites 4pda.to. I just stayed on the stock crDroid recovery; did the same on my RN10P after this same ROM.
Flash crd9.1 on spes using instructions by LolFlasherNoob with the full MIUI ROM flashed first.

Sheist! said:
This is where I borked it myself, and with sideloading. Apparently, the semi-permanent instructions for TWRP on spes should work using twrp-3.7.0.img (96mb) and NOT twrp-3.7.0-12.1-06.11.22.img (128mb), as the latter is the JabiYeff version and is "unable to flash MIUI ROMs due to dynamic partitioning error" as of November 2022. I assume your dblenk9 version is 128mb? You have a link for it? Googling gives only this thread and a couple of Russian sites 4pda.to. I just stayed on the stock crDroid recovery; did the same on my RN10P after this same ROM.
Flash crd9.1 on spes using instructions by LolFlasherNoob with the full MIUI ROM flashed first.
Click to expand...
Click to collapse
@Sheist!
Thanks for the reply.
Re the dblenk9 twrp, it definitely came from this site somewhere but I can't find the link any more either, nor on the wider internet. The version I use is 96mb and it has worked very well up until the Jan update. Like yourself, I will stay on crdroid recovery for now, but I will attach the dblenk9 twrp version to this post in case you or anyone else is interested. You can still use it for 'fastboot boot twrp' and it does decrypt data so you are not left with 0mb on internal storage like the others I have tried.
NB To anyone who happens across this post whilst looking for twrp versions, If you are on the Jan ota do not try to install this, only fastboot it - unless you enjoy bootloops!

It probably doesn't matter much now, but I managed to find the original post that linked to the dblenk9 twrp this is it:
Any one have OrangeFox Recovery for Redmi Note 11 (spes)?
I am looking for OrangeFox Recovery for RN 11 (spes). Couldn't find anywhere. Anybody build it?
forum.xda-developers.com
It shows how good the search is on this forum because I wasn't even looking for it!