Search results

Do you mean the updater says 'no updates' or the OTA file has gone walkies, or something else? Am assuming you are device is curtana and you are indeed running xiaomi.eu modded build (not official mi.coms curtana EU release)

What? Why?

1. Is this a proximity sensor thing? I thought it was just floating notifications, try disabling that for the phone app (you can also tap the name/number of the 'short version' to get the full screen layout) 2. Settings - Apps - System App Settings - Call Settings - Incoming Call Settings -...

Unsure as I don't know what part of the boot process is hanging and I rarely reboot. I'm have a feeling it's before the handover to recovery/rom - have you noticed the same freezes when trying to get to recovery or only when booting the system?

Pretty sure this is a bug in the stock rom (Kernel? Bootloader? Not sure what's actually responsible for the hang) The device will freeze at the first splash - the one with the open padlock for unlocked bootloaders - for a matter of minutes. Most people don't bother and just reboot. It seems to...

Can I squeeze any more details out of you on this?

Thanks, I'd combed the wiki previously but always good to refresh! So I suppose the fact it's just recovery environments suffering from this the fault lies in their decryption routine. The fact fastboot boot is a stable workaround still boggles me, but I think that's far enough down this...

If I understand things correctly (I'd give myself odds around 60%) the reason we format data is because this removes the encryption scheme so a new one can be created. This is why wipe is not enough. So I would imagine the partition is built and encrypted using the (keymaster?) scheme supplied...

So the bug is either in formatting the partition, or when trying to read it. The first post has a confusing warning about decryption during format. If the bug lies there then we're going to need to format using the new recovery to be fully clear of the issue. Hopefully I've explained my...

So does that mean 11.1.1 will decrypt partitions formatted on older / different builds? Or that it's fixed when partitions are formatted with 11.1.1+?

Turns out this is a known problem, it's described in the OF10 build notes & the OF wiki says

Can you explain why there are so many warnings for twrp 3.5x?

Can you explain the problem with twrp? Is it that formatting /data doesn't remove the encryption like it should?

The problem is you are using a recovery based on A10 sources to try to decrypt a A11 rom (note the 10 at the end of the filename) I'm using the April 20 build of pitchblack recovery by dungphp Link and have no issues decrypting

I used PBRP-miatoll-3.1.0-20210420-1027-UNOFFICIAL.zip by dungphp to update and it worked without issue. The ROM is only available as a full OTA (as opposed to the o a patch ota) but you don't need to do anything with your /data partition, although I'd imagine you'd need to at least wipe it if...

There should be an option to view the logs if you click the gear icon in the top right. You should also update your copy of the unlock tool - Download v5.5.224.24

This may be a question for the xiaomitool developer, looks like this is a unofficial tool and shouldn't be confused with MiFlash which is the official Windows tool for updating via fastboot

Do you actually have a system_ext partition to mount? Looks like it's a new partition introduced in Android 11. Not sure why the assert failed but passed using an older version of twrp though

Dungphp has made a Thread over at xda for his recoveries, changelogs should appear here.

I'm still pretty hazy on all the changes android 10 brought but my understanding is that fastboot cannot see the sub-partitions and can only work on /super as a whole. I'm unsure if recovery gets any further along the boot process to be able make sense of things or if it's in the same boat...