Search results

Yeah... If you don't manage to get into EDL I wouldn't know what to do. Heck, I wouldn't even know what to do if I was unable to get into Fastboot apart from hiring one of those shady EDL services on Telegram. Oh, the glory of fastboot ROMs. Now I know why I stayed off them until recovery ROMs...

If you're super new to fastboot, non-recovery ROMs as you probably are I'd recommend the super-safe update procedure I posted here. Follow all steps to the letter. https://xiaomi.eu/community/threads/22-12-19-21.67684/page-2#post-678781

Sounds like a configuration issue rather than a ROM issue. Have you checked WhatsApp's permissions? Especially for contacts and that it's set to Always, not just while using the app or the default "return blank messages".

You were fully charged? You could try charging for a while and trying to turn the phone on again. You can check what happens when you keep the power button pressed for a long time (like 30 seconds) unless you tried already. "No way to go back to fastboot mode" means the hold volume down and...

No such problem on my Redmi K40 Pro+. I like to live dangerously so I just tried it out (after backing up data ;) ). Might be a USB connection issue. Just try flashing again using a different port on your computer and maybe a different cable. It doesn't matter that the previous partitions were...

I don't have a good answer to that. I have broken fastboot ROMs before - seemingly randomly, that's the danger of fastboot ROMs and why I refused to switch to my new phone for almost a year until recovery ROMs became available which actually have some sort of error checking. :P Usually you...

You can restore data only. Be mindful though that the data partition might be the problem here and if you have to not restore it then it's basically like a clean flash.

Yes. OK, if it literally doesn't boot after essentially the first and quite automated step then you'll probably have no other option than a clean install. You could maybe try wiping cache/dalvik via TWRP first and see if this helps but after that there's not much else you can do. You could back...

The recovery always gets overwritten when installing via fastboot and using the provided scripts. You could try another dirty flash but this time follow my update procedure that tries minimizing risk and seems to have worked for quite a few people between the last two weeklies including me...

Yes. Choose the appropriate script, not the first install and if you want to mitigate the risk of anything going wrong you can follow my "super conservative and cautious installation guide" here: https://xiaomi.eu/community/threads/22-12-19-21.67684/post-678781

I'd try wiping cache/dalvik via recovery (e.g. from TWRP) but apart from that I can't think of any. If you have bootloops or other problems try dirty flashing again and see if this helps. If it doesn't, the next step would be to back up your data (both the partition and separately the storage...

Try reflashing and following the super-safe steps outlined in my post above. Do not skip anything even if it seems silly or redundant. I read from your signature that you are on a Rooted Xiaomi 12 Pro? Did the crashes start after or before rooting on the new version?

Again, just cause it worked somehow for you doesn't mean that it's the correct procedure. In fact it's completely wrong and nobody should be following that or reporting bugs after doing so. ;) Also, if you're on Xiaomi 12X, Psyche TWRP is available for you. You cannot update the ROM through it...

You cannot reuse a patched boot.img from another ROM version, LOL! It's a miracle if it worked ever and it's for sure not a problem with the ROM. You always reflash/repatch Magisk after each update. I prefer the TWRP installation method but to each one their own.

In which way and which app are they not working? Are you rooted? Asking because my Redmi K40 Pro+ is at least in the same family of devices and payments work fine via Google Pay/Google Wallet, even with root but I had to jump through additional hoops for that.

Successful (dirty) flash of the ROM, TWRP and Magisk on my Redmi K40 Pro+. Coming from the previous MIUI 14 Dev ROM. I'll repost the steps I followed since they seemed to help a few people in previous version's thread. Merry Christmas to everyone (who is celebrating it)! My SUPER conservative...

A few users including me had good results by following the steps I posted here. Follow them to the letter except using twrp-3.7.0_12-v6.5_A12-venus-skkk.img instead of the recovery for haydn. >> INSTRUCTIONS HERE <<

You can select what you backup in TWRP. To keep your app settings and the previous OS etc. select Data and Super. Boot is also generally a good idea. And then obviously backup everything you have in storage by just connecting your phone and transferring whatever is there when it pops up after...

You won't lose any data if you use the correct update script from the extracted ROM directory. Booting into TWRP, flashing it and installing Magisk has nothing to do with losing your data. Of course uninstalling Magisk will result in you having to reconfigure that to an extent. Even if you...

Yeah, delete everything Magisk-related, rename Magisk-v25.2.apk to Magisk-v25.2.zip and flash from TWRP. That's the way I did it and how a guy who had similar problems whom I helped via DMs did as well.