If the device you're using does use a recovery ramdisk you can try booting the new version temporarily from fastboot and see if your internal storage shows up. See the how-to install custom recovery thread in the Q&A section of the forum.
You probably can still root, but you have to add the banking app to the deny list in Magisk and hide Magisk Manager under a different package name. Both settings are in the Magisk Manager app. You may also need the SafetyNetFix from KDrag0n. You can Google that. Doing this makes Samsung Pay work for example, which generally doesn't if you're rooted.
Thanks for your answer. I had looked for it and found the unofficial file and installation commands, and there was also a note to install to the vendor partition. The installation command was fastboot flash vendor_boot twrp xxxx.img What I notice now is that ab was not given to the command. I will try it and report back.
Installing a Custom Recovery
All custom recoveries come in the format of an IMG file (some are released as a flashable ZIP, like OrangeFox, but there's still an IMG inside). However, installation method will differ, depending on where the recovery ramdisk resides on your device specifically. Failing to install the custom...xiaomi.eu
Since the only MIUI 14 .EU ROM available is a fastboot ROM for Xaga, that is all that is officially supported right now. You CANNOT update your device via recovery yet.
BUT, If you bothered to look in the Q&A section, there is a Xaga vendor boot partition recovery available (which is about a month old now and barely downloaded, and doesn't list the android version supported as it should, so you should consider it completely untested).
Instructions to flash it are also in the same thread...
Okay, I tested this a few days ago and the themes didn't work. Tried again, everything is back to normal. Mist have been something on the server side.
I changed to dark mode, thanks. I am now on 3,5 screen on time. Battery is down to 30 something percent. The screen is eating the most energy which is not surprising. Could set it to a lower resolution and refresh rate but who does that
. I'm just curious if this screen on time, probably around 5 hours is normal (after all the phone is more than a year old).
Your screen is still using ALOT of power. For example on my F3 on this charge it has been active 21hrs 22min, 3hrs 32min screen on time since I didn't use the phone that much yesterday, and my screen power use is 400mah. Are you using auto brightness? I would definitely try turning down the refresh rate on your phone and see if it helps. You can always switch it back if it doesn't.I changed to dark mode, thanks. I am now on 3,5 screen on time. Battery is down to 30 something percent. The screen is eating the most energy which is not surprising. Could set it to a lower resolution and refresh rate but who does that
What the hell is "odinx"? If you're using an outdated release from TWRP.me, then that's your problem... It was built for Android 11...
Great, yes , I am using auto brightness. Will deactivate that and see if that makes a difference. After that I will try the 60hz suggestion and see if I can get it down to your numbers. Thanks for the suggestions!
Auto brightness usually is fine, but maybe it's keeping your screen too bright for some reason. I thought maybe you had it set to full brightness all the time or something based on the power consumption.
Ah, okay. No, full brightness is a bit too bright for me. Auto brightness is now off, let's see what happens. Now I know that the screen should use less energy so thanks..
never tried renaming the magisk package, everything else... no luck. not even using second space,
A lot of apps check for the presence of magisk manager. If it's not hidden, then many apps will assume you're rooted just based on the known package name being installed, hence the renaming/hiding feature for the package name. It was the same way with Screen2Auto. Google initially was banning based on package name alone before moving on to more sophisticated detection techniques.
Looks like you have some kind of corruption in your keystore. It's clearly a low-level issue, a clean flash might help, but I don't have any other ideas.
No idea. Your keymaster fails with internal error code -1000 (KM_ERROR_UNKNOWN_ERROR) and public error code 10 (ERROR_KEYMINT_FAILURE).
Updating, most likely yes, don't know if TWRP will be able to decrypt data once Android 13 is booted for the first time.
Update to the latest - I see this changelog on TWRP:
We found that it's missing FM radio functionality so we had to rebuild, now we're hearing that it's stuck on boot logo, so... no idea for now.
