Database Develop

Need some help setting up my SP

I have bought a new SP, and gave my last one to my wife, so I have a chance to start fresh.
I can't stand the bloating on the phone, and would like a light, fast lollipop ROM on it that still lets me use Sony's photo apps if possible. This one seems right for me (http://forum.xda-developers.com/xperia-sp/development/rom-cyanogenmod-12-1-sabermod-t3219230).
The problem I am experiencing is that when I go to various builds, I am having trouble understanding the instructions, and how to do what they are asking. I understand that I need to break the bootloader first, and then do something after that, and then install drivers, etc.. but I feel like a bit of an idiot because I just don't get it.
The instructions for one that I was thinking of putting on reads as follows :
* place the phone in fastboot mode, and flash the boot.img from the latest build: sudo fastboot flash boot boot.img
* enter Cyanogen Recovery
* flash the TWRP zip you downloaded via Cyanogen Recovery.
* shutdown and reboot into TWRP recovery.
* wipe/format /system /data /cache /dalvik.
* flash latest available build, and flash gapps.
* reboot and you're done.
Questions
- How do I flash the boot.img from the latest build? What is boot.img? What does "sudo fastboot flash boot boot.img " mean?
- How do I enter Cyanogen Recovery? What is it? Where do I get it?
- How do I flash the TWRP zip?
I could go on. I really need a step by step guide, or some systematic way to educate myself.
Can you suggest a ROM with a step by step guide, or one with a youtube video showing how it is done (walkthrough) or similar?

http://forum.xda-developers.com/showthread.php?t=2888579
Use this Guide to understand about Custom ROMs, Bootloaders, Flashing ROMs, Kernel and Recovery. Specific to Xperia SP.
Take your time to read, if didn't understand something, search for it on Google, you'll understand things
There are many more generic device Guides, but this Guide is Specifically for our Device.
Once you read the guide, then you'll understand the Instructions given in any ROM thread.
Sent from my Q1010i using Tapatalk

make backup of drm partition, unlock bootloader then start flashing roms

installing Magisk on Xiaomi A2 fails

First I unlocked the boot loader, although I doubt that’s needed for installing Magisk:
A2/Android (Oreo 8.1): Enabled developer options, enabled unlocking of boot loader, enabled debugging via USB.
PC/Linux: $ adb reboot bootloader
A2 boots into boot loader.
PC/Linux: $ fastboot oem unlock
Then I tried installing Magisk:
A2/Android: Re-enabled developer options, enabled debugging via USB, disabled automatic system updates (just in case, for later).
PC/Linux: $ adb reboot recovery
A2/Android: On the dialog asking for permission to allow USB debugging, selected to always allow from this computer and hit OK.
A2 displays screen with lying robot, saying No command. I held power, pressed volume-up once, released power.
A2 boots into recovery.
A2/Recovery: Selected Apply update from ADB.
PC/Linux:
$ adb sideload Magisk-v16.0.zip
Total xfer: 1.01x
A2/Recovery: Error message failed to verify whole-file signature
PC/Linux: Checked the zip file. It can be unzipped just fine, so it’s OK.
What else can I try?
PS: I do have detailed screen shots of the critical steps, but I don’t find an option to upload them to the forum.

You can't sideload the Magisk zip on a stock recovery. If you don't have a custom recovery installed you'll have to patch the boot image first with the Manager and then flash the patched image manually with fastboot. Check the installation instructions in the release thread.

Didgeridoohan said:
You can't sideload the Magisk zip on a stock recovery.
Click to expand...
Click to collapse
Thanks!
If you don't have a custom recovery installed you'll have to patch the boot image first with the Manager and then flash the patched image manually with fastboot. Check the installation instructions in the release thread.
Click to expand...
Click to collapse
Tried that, but did something extremely stupid in the process, knowing full on that this could cause an issue (I assumed things are easy to fix in case something goes wrong):
I did not run any system updates, leaving the Android 8.1 ROM at V9.6.5.0. (no problem so far)
I downloaded V9.6.10.0 of the ROM, and had Magisk patch the included boot.img to create patched_boot.img (still no problem)
I flashed patched_boot.img onto my A2. Now the device did not boot anymore. It hung at the loader animation showing a horizontal bar with varying colors.
To get the A2 to boot again, I obtained V9.6.9.0 of the ROM, I flashed the included boot.img, and I cleared the cache. Unfortunately, while the device boots into Android now, I cannot enable WLAN. It simply doesn’t work. Again, no surprise: V9.6.9.0 ≠ V9.6.5.0
Not being able to find the V9.6.5.0 ROM, I got the idea to update the half broken A2 to the latest ROM, i.e. V9.6.10.0. But how, without WLAN? Well, I found out that it is possible to use the WLAN connection of another Android device via Bluetooth. This is what I used, and I had to be very patient – it’s dog slow. Anyhow, I waited, and the installer started to do its job. The download succeeded, but the installation failed.
Phew, for now I’m out of options, and I’ve a non functioning device.
In another thread on the XDA Forums, I did find an unofficial dump of V9.6.5.0. But 1. I’m hesitant to install from unofficial dumps, and 2. the dump does not include a boot.img. Instead it includes one big payload.bin. Don’t know what to make out of that.
The alternative could be to install either V9.6.10.O or V9.6.9.O manually, possibly by flashing each partition image individually from fastboot. I don’t know, however, if that is a great idea.
PS: Sorry about the confusion with all those numbers.

Oh man... Flashing an update manually (each partition should work fine) is probably a good idea at this point.

Didgeridoohan said:
Oh man... Flashing an update manually (each partition should work fine) is probably a good idea at this point.
Click to expand...
Click to collapse
Went ahead with that. In fact, included in the full ROM archive are scripts for doing the update, sorted by an increasing number of steps performed:
flash_all_except_data.sh
flash_all.sh
flash_all_lock.sh
flash_all_lock_crc.sh
The last one also flashes CRC check sums into crclist and sparsecrclist. Included is a script to generate these check sums form the image files: flash_gen_crc_list.py
Here’s how I got back to a system that boots up fine:
PC/Linux: $ tar xfz jasmine_global_images_V9.6.10.0.ODIMIFE_20180731.0000.00_8.1_2aeda83301.tgz
PC/Linux: $ cd jasmine_global_images_V9.6.10.0.ODIMIFE_8.1
PC/Linux: $ fastboot flashing unlock
(reboot)
PC/Linux: $ fastboot flashing unlock_critical
(possibly reboot again)
PC/Linux: $ ./flash_all_lock_crc.sh
(went through smoothly, flashing CRC possibly not necessary)
Following this success, I did another attempt at installing Magisk:
PC/Linux: $ cp ../patched_boot.img images/boot.img
(created with Magisk Manager from the V9.6.10.0 boot.img)
PC/Linux: $ python2.7 flash_gen_crc_list.py
(thought it’s a good idea, but doesn’t help – see below)
PC/Linux: $ fastboot flashing unlock
(reboot)
PC/Linux: $ fastboot flashing unlock_critical
(possibly reboot again)
PC/Linux: $ ./flash_all_lock_crc.sh
(went through smoothly, flashing CRC possibly not necessary)
Unfortunately, upon reboot I get:
Code:
<!>
Your device is corrupt. It can’t be trusted
and will not boot
Visit this link on another device:
g.co/ABH
Eventually the device doesn’t show the message anymore, instead hanging permanently at a androidone logo.
Not locking the boot loader after flashing solves the issue, but: For security reasons, I don’t want to use a device with an unlocked boot loader!
Any idea?

Uh-oh! Now it seems like I eclipsed my previous stupidity.
In the Android developer settings, I disabled OEM unlocking. Then I rebooted the device, locked the boot loader: fastboot oem lock This was still possible.
As result, I get the aforementioned error message:
Code:
<!>
Your device is corrupt. It can’t be trusted
and will not boot
Visit this link on another device:
g.co/ABH
But now I cannot unlock the device anymore. fastboot oem unlock gives: FAILED (remote: Flashing Unlock is not allowed)
Bricked for good, right? :crying:

Oh... I saw your first message about getting things working (post #5), but I didn't have time to answer (work, work, work).
Now I wished I would have had the time, since I would have posted that you should never lock your bootloader on a modded device. The risk of something going wrong and not being able to unlock the bootloader again is too great...
If you're lucky there's still some kind of hack available that you can use, but you'd have to take that in your device's forum, where they know the device best.
That sucks... I hope you get things sorted. Good luck.

Didgeridoohan said:
Now I wished I would have had the time, […]
Click to expand...
Click to collapse
Don’t worry. I like to take systems to their limit.
[…] since I would have posted that you should never lock your bootloader on a modded device.
Click to expand...
Click to collapse
For security reasons, I don’t like the idea of leaving the boot loader open. While I understand that – due to encryption – it’s not possible to access my data, I assume it would be feasible to modify boot.img to install a rootkit in a few minutes. Just the thought of this being possible makes me uncomfortable and not trust the device for productivity use.
I wonder if I would also get the your device is corrupt message with Lineage installed.
If you're lucky there's still some kind of hack available
Click to expand...
Click to collapse
Yes, I’m betting on that, or perhaps the Xiaomi Mi Flash Tool can be used. (looking for an official download location)

feklee said:
I wonder if I would also get the your device is corrupt message with Lineage installed.
Click to expand...
Click to collapse
Did you preserve dm-verity when you patched the boot image? That sounds like dm-verity complaining...

Didgeridoohan said:
Did you preserve dm-verity when you patched the boot image? That sounds like dm-verity complaining...
Click to expand...
Click to collapse
No:
I’m almost certain that I did not enable dm-verity.
The device is corrupt message appears right after the reboot following ./flash_all_lock.sh or ./flash_all_lock_crc.sh, i.e. without any setup by Magisk Manager, and dm-verity is disabled by default.
BTW I got around to trying Xiaomi Mi Flash Tool, but it’s useless: It seems to be simply an ugly GUI for the fastboot commands. It cannot flash a device in locked state. In the end I was able to revive the device by opening it and using the test point method. Phew, gotta be more careful the next time…

How to check if MIUI flashed by MiFlash is legit?

Hi, yesterday I unlocked bootloader in my phone and flashed a custom ROM but I decided that I want to go back to stock and have locked bootloader. I downloaded MiFlash tool and 10.0.3.0 image from here: http//)c(.)mi(.)com/oc/miuidownload/detail?guide=2
First thing that struck me was that the tool isn't signed, the producer is unknown in the UAC popup. The ROM was suspicious as well, its MD5 hash (only part of it) was in the filename, which is just stupid. I decided that I want to use this tool and flash the ROM anyway. I connected my phone (which was in fastboot mode) to USB 3.0 port in my PC and ran the tool. It got up to flashing system image, but then I got an error "Failed system flash". I noticed that the bootloader got locked, but the MiFlash Unlock tool told me that the device is already unlocked. I tried to boot to TWRP but, well, the bootloader was locked. I thought I hard bricked my phone, but then I decided to connect it to USB 2.0 port. To my surprise, the whole flashing progress was successful and I got no errors. It was suspicious for me, I thought that the first error was on purpose, to replace boot image to allow installation of rogue ROMs with locked bootloader. I know it's kinda paranoic, but I don't trust these Chinese tools at all. Also, I compared old boot image (backed up with TWRP) with new one, and their hashes were different. When the phone booted, I successfully updated MIUI to version 11.0.4.0 (it's the latest MIUI available in Poland), so it seems for me that it's legit. I'm attaching some screenshots from settings: https//)imgur(.)com/a/894o9qU. So, what's the best way to determine if the system is 100% legit and I'm not running some fake ROM with hidden malware?

knur2172 said:
Hi, yesterday I unlocked bootloader in my phone and flashed a custom ROM but I decided that I want to go back to stock and have locked bootloader. I downloaded MiFlash tool and 10.0.3.0 image from here: http//)c(.)mi(.)com/oc/miuidownload/detail?guide=2
First thing that struck me was that the tool isn't signed, the producer is unknown in the UAC popup. The ROM was suspicious as well, its MD5 hash (only part of it) was in the filename, which is just stupid. I decided that I want to use this tool and flash the ROM anyway. I connected my phone (which was in fastboot mode) to USB 3.0 port in my PC and ran the tool. It got up to flashing system image, but then I got an error "Failed system flash". I noticed that the bootloader got locked, but the MiFlash Unlock tool told me that the device is already unlocked. I tried to boot to TWRP but, well, the bootloader was locked. I thought I hard bricked my phone, but then I decided to connect it to USB 2.0 port. To my surprise, the whole flashing progress was successful and I got no errors. It was suspicious for me, I thought that the first error was on purpose, to replace boot image to allow installation of rogue ROMs with locked bootloader. I know it's kinda paranoic, but I don't trust these Chinese tools at all. Also, I compared old boot image (backed up with TWRP) with new one, and their hashes were different. When the phone booted, I successfully updated MIUI to version 11.0.4.0 (it's the latest MIUI available in Poland), so it seems for me that it's legit. I'm attaching some screenshots from settings: https//)imgur(.)com/a/894o9qU. So, what's the best way to determine if the system is 100% legit and I'm not running some fake ROM with hidden malware?
Click to expand...
Click to collapse
That site is the official MIUI forums and the list of fastboot ROMs listed in that page are the official ROMs. As far as I know, that page is the only official page that has fastboot ROM links.
A boot partition backup from TWRP will not give the same hash, it copies the data from the boot partition into a new .img file, it does not do a bit perfect copy of the partition.

Robbo.5000 said:
That site is the official MIUI forums and the list of fastboot ROMs listed in that page are the official ROMs. As far as I know, that page is the only official page that has fastboot ROM links.
A boot partition backup from TWRP will not give the same hash, it copies the data from the boot partition into a new .img file, it does not do a bit perfect copy of the partition.
Click to expand...
Click to collapse
Thank you for your response! So it seems that I've done everything properly and there's no need to worry about anything

Someone please Help!....Bootloop after flashing magisk patched boot image

Device:Vivo 1802
Android version: 8.1
Magisk version name:canary build
Magisk version code:25101
ANDROID - Google Drive
drive.google.com
this folder contains
1. stock image
2. patched boot image
3. magisk log
4. cat /proc/mount
the stock boot.img being used is correct one cause it fixed bootloop upon flashing
Can't obtain boot log as it requires custom kernal
Someone please help

Kernal log has been included in same folder...
someone please help

someone please help
i have same device
with the issue

I forgot one important rule. Do not update magisk if it works. Stable channel or not. Got the same stuck on line 137 of uninstaller.sh in the latest version tried v23 the version I installed. When I reboot black screen heptic feedback goes crazy and blue notification led stays on. I am trying to uninstall the version from twrp. So after all these years it's still not stable.

it never was really working for me!

SwapScout said:
it never was really working for me!
Click to expand...
Click to collapse
It did work for me but I guess my device it too old for the new version. I hoped for backwards compatibility but it does not exist at all when you install the update you will simply automatically brick your device. I now used 15.3 just a little outdated facepalm, I need a new rom but too busy and lazy right now.. I had to manually flash back original boot.img from the firmware and run the uninstall script a few times. Never the less to say that it works horribly at least that is my experience.. But if it works, it does work good.
So if you guys wonder how to fix it.. First get the version you installed from here
Releases · topjohnwu/Magisk
The Magic Mask for Android. Contribute to topjohnwu/Magisk development by creating an account on GitHub.
github.com
If the extension is *.apk rename it to zip call it uninstall_25.zip or whatever boot the phone in fastboot and load TWRP image (from here https://twrp.me/Devices/). Make sure to use the correct TWRP version too, I've noticed that the normal non ROW version corrupts boot.img in the patching process even if it says in the console successfully installed, without errors!.. It has something to do with the firmware on your phone I guess? Idk but give it a try and keep a copy of your original boot.img and back-ups in general before you attempt to mess with Magisk and Xposed. I use a old dev dummy phone for this a older one it runs non offical firms and magisk with xposed. It's buggy and not stable but it's a old phone perfect to play with and mess up.
Put it in the ADB and fastboot bin folder for your device (fist download the correct adb & fastboot)
Run
Code:
@echo off
%~d0
CD "%~d0%~p0"
@echo off
title Fastboot TWRP ..
adb reboot bootloader
fastboot boot twrp.img
echo booting TWRP
pause >nul
Login if full device encryption etc.
Install select the uninstall zip (magisk version you installed) for example uninstall_25.zip
If that does not work (in my case)
Grab original boot.img from OEM firmware or firmware version you are running and flash it.
Code:
fastboot flash boot boot.img
I did try to fix SELinux context(in TWRP) but I don't advice you to do so because it warns you it can break the system even futher. Try this as last option.

NiTrOwow said:
It did work for me but I guess my device it too old for the new version. I hoped for backwards compatibility but it does not exist at all when you install the update you will simply automatically brick your device. I now used 15.3 just a little outdated facepalm, I need a new rom but too busy and lazy right now.. I had to manually flash back original boot.img from the firmware and run the uninstall script a few times. Never the less to say that it works horribly at least that is my experience.. But if it works, it does work good.
So if you guys wonder how to fix it.. First get the version you installed from here
Releases · topjohnwu/Magisk
The Magic Mask for Android. Contribute to topjohnwu/Magisk development by creating an account on GitHub.
github.com
If the extension is *.apk rename it to zip call it uninstall_25.zip or whatever boot the phone in fastboot and load TWRP image (from here https://twrp.me/Devices/). Make sure to use the correct TWRP version too, I've noticed that the normal non ROW version corrupts boot.img in the patching process even if it says in the console successfully installed, without errors!.. It has something to do with the firmware on your phone I guess? Idk but give it a try and keep a copy of your original boot.img and back-ups in general before you attempt to mess with Magisk and Xposed. I use a old dev dummy phone for this a older one it runs non offical firms and magisk with xposed. It's buggy and not stable but it's a old phone perfect to play with and mess up.
Put it in the ADB and fastboot bin folder for your device (fist download the correct adb & fastboot)
Run
Code:
@echo off
%~d0
CD "%~d0%~p0"
@echo off
title Fastboot TWRP ..
adb reboot bootloader
fastboot boot twrp.img
echo booting TWRP
pause >nul
Login if full device encryption etc.
Install select the uninstall zip (magisk version you installed) for example uninstall_25.zip
If that does not work (in my case)
Grab original boot.img from OEM firmware or firmware version you are running and flash it.
Code:
fastboot flash boot boot.img
I did try to fix SELinux context(in TWRP) but I don't advice you to do so because it warns you it can break the system even futher. Try this as last option.
Click to expand...
Click to collapse
my phone neither have custom recovery available 🥹….
and I cant build one….as it requires stock recovery.img if I am not wrong …….

Swapmema6be said:
my phone neither have custom recovery available 🥹….
and I cant build one….as it requires stock recovery.img if I am not wrong …….
Click to expand...
Click to collapse
It should be possible to load the uninstaller zip with the stock recovery if the bootloader is unlocked and if the stock recovery doesn't check signature verification if it will you will need to sign the zip with the keys in order to pass it. It's always best to get a phone with all these packages available if not, you're fed up with what you have stock garbage..
For your Vivo Y83 it seems there is no custom recovery image around, I could not find it. Meaning you will have to manually side-load it by using the "Install Update" option in the recovery. Again I hope for you that it does not check for signature verification, it probably will and then well. You're out of luck doing the repair and you will have to reflash a fresh new rom. You can try to build it if you have the original recovery.img but that requires more effort. If the phone even worth all the effort? I think there is a reason why they left out support. There are better devices on the market even older ones and newer ones. Look on kimovil, Idk not a fan of mediatek SoC devices.

I don
NiTrOwow said:
It should be possible to load the uninstaller zip with the stock recovery if the bootloader is unlocked and if the stock recovery doesn't check signature verification if it will you will need to sign the zip with the keys in order to pass it. It's always best to get a phone with all these packages available if not, you're fed up with what you have stock garbage..
For your Vivo Y83 it seems there is no custom recovery image around, I could not find it. Meaning you will have to manually side-load it by using the "Install Update" option in the recovery. Again I hope for you that it does not check for signature verification, it probably will and then well. You're out of luck doing the repair and you will have to reflash a fresh new rom. You can try to build it if you have the original recovery.img but that requires more effort. If the phone even worth all the effort? I think there is a reason why they left out support. There are better devices on the market even older ones and newer ones. Look on kimovil, Idk not a fan of mediatek SoC devices.
Click to expand...
Click to collapse
t really need that fix Bootloop…. I can fix Bootloop by flashing original boot.img…..thing is I want to root🥹

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!