Yes, I know it's A11 firmware, but there was something with the "newer" ones that didn't work, whereas this one is perfect (on X3).V220.127.116.11 ?
Do you know, it is android 11 firmware ?
I have an experience with crdroid on poco f3. If you will use firmware which is not recomended by crDroid author, always something will be wrong. Use only version recomended by developer !!!!
Unlocked bootloader? TWRP installed? Then good to go. Follow the instructions at the start of the thread.Hi guys.
I have a Poco X3 NFC with xiaomi.eu 12.5.8.
Is necessary to flash a stock rom before flash crDroid?
Yes. I have both but I see some post with other users saying that they have to install an specific version of the stock rom.Unlocked bootloader? TWRP installed? Then good to go. Follow the instructions at the start of the thread.
Recovery & fastboot. First needs... recovery, second is totally clean (bigger one) and it needs MIUI flash or something . Oh, if you use MIUI flash unheck 'lock bootloader ' lower right corner
MB_CC_Manx,Official MIUI instalation file exist with 2 different version, flashable image and full image (I do not remember correct names). If you installed xiaomi.eu the smaller version, it is like other custom roms and you can install other. If it was full version , better to install original MIUI because customs base and use parts of it from original partitions. We do not know if xiaomi.eu changed anything ...( and I do not know if they distribute full version or not.)
Solved by resetting network settingsOK, so my mobile service enabled VoLTE. Now I cannot send or receive SMS unless I select 3G as preferred network type (instead of LTE). Slower, but works... for now - until they disable 3G support altogether.
So, Q: how to disable VoLTE while leaving LTE preference?
I tried *#*#4636#*#* to get this:
View attachment 5876815
but can't change VoLTE toggle
I'm experiencing something similar, namely this issue:Anyone experiencing lot of drain from Google play services? On mine it says 18hrs total runtime since yesterday
9.3 is here:
- Initial crDroid 9.3 release
- Updated to March 2023 security patches (android-13.0.0_r35)
- Implemented Android 13 QPR2
- Full source rework (some stuff got added, some got removed)
- Patches for leica cam added
- Because of the new security patch, leica cam is broken though
- Lots of other improvements and fixes
Not if you're 'encrypted'.Safe to dirtyflash?
Thanks, what group is that?Not if you're 'encrypted'.
That's not true, you can dirty flash even if you are encryptedNot if you're 'encrypted'.
Why does Release 'Notes' say:... not true, you can dirty flash even if you are encrypted
I can only say that t I just did yesterday an OTA upgrade, and it was most obviously dirty, because afterwards everything was still there as usual.Why does Release 'Notes' say:
• CLEAN FLASH IS MANDATORY IF YOU ARE ENCRYPTED
See post #1816 screenshot.
The dev would be the best person to comment on all the above and the 'MANDATORY' thing, I guess..... did yesterday an OTA upgrade, and.... everything was still there as usual.... not sure if a manual dirty upgrade from recovery would be any different..... 9.1 -> 9.2 did require clean flash because of a change in the encryption system, but I don't see from the changelog why 9.2 -> 9.3 should be an issue.
Probably because of this changelog entry:Hey all, we got a new update (check telegram).
It says "clean flash mandatory"
Anyone tried dirty flash?
I am on the update before that!
You're right - it shouldn't be offered as an OTA update. I've always said that custom ROM devs should add "WIPE" or something similar in the ROM filename, so that users that don't read the changelog aren't left with a brick. Being stuck with an unbootable phone with official firmware isn't acceptable to users, so why should it be acceptable to custom ROM users? I know it's necessary, but just give people a warning.It does say "clan flash mandatory"? I tried it via OTA, when it was suggested as an install with no warning whatsoever.
I then tried the OTA and it rebooted directly into recovery, with the error "init_user0_failed". A subsequent dirty flash didn't help either and I had to reinstall the previous version. Luckily this worked.
But if it requires a clean flash, then it shouldn't be offered as an OTA.
Yes, exactly, stable - not experimental. It should be obvious that proprietary blobs from the device manufacturer are more solid than oss ones, even if they're older...You want a stable rom or not?
You want a stable rom or not?Probably because of this changelog entry:
"Reverted to MIUI 14.0.1 blobs".
Don't you just love it when the maintainer flips back and forth between incompatible sources
*** Disclaimer I am not responsible for any damage you made to your device You have been warned