Database Info

bootloops and wifi doesn't turn on

i had the latest COS12 stock rom (rooted)
few days ago my battery ran out and after charging, the device got into bootloop.
i tried the onplus fix (https://forums.oneplus.net/threads/fix-stuck-at-boot-logo-boot-loop-random-reboot.160199/) which indeed fixed my bootloop and flashed KTU84Q (4.4.4), however, my wifi doesn't turn on now:
https://youtu.be/xchjcNl3pPk
i've tried clean flash again (with lolipop i get bootloop again)
i've also tried flashing color os (kitkat) and also no wifi
so far my problem seems to be:
on lolipop - bootloop
on kitkat - no wifi
any one has any idea?

matanp said:
i had the latest COS12 stock rom (rooted)
few days ago my battery ran out and after charging, the device got into bootloop.
i tried the onplus fix (https://forums.oneplus.net/threads/fix-stuck-at-boot-logo-boot-loop-random-reboot.160199/) which indeed fixed my bootloop and flashed KTU84Q (4.4.4), however, my wifi doesn't turn on now:
https://youtu.be/xchjcNl3pPk
i've tried clean flash again (with lolipop i get bootloop again)
i've also tried flashing color os (kitkat) and also no wifi
so far my problem seems to be:
on lolipop - bootloop
on kitkat - no wifi
any one has any idea?
Click to expand...
Click to collapse
A few questions:
What method are you using to switch between KK and LP? Fastboot (flashing stock images) or recovery?
If it's recovery, are you flashing the correct firmware/modem?
Are you still able to see your baseband and IMEI in About Phone?
IF you haven't flashed the stock images with fastboot that's the first thing you should try. I have detailed instructions in my guide here:
http://forum.xda-developers.com/showthread.php?t=2839471

first, thanks for your reply
second:
at first i did a clean flash from fastboot like this: https://forums.oneplus.net/threads/tutorial-flashing-a-factory-image-from-scratch.142870/
i also tried the oneplus one fix for bootloops that also use fastboot from here: https://forums.oneplus.net/threads/fix-stuck-at-boot-logo-boot-loop-random-reboot.160199/
later, i tried flashing from recovery, also the colorOS rom
the common for all is LP = bootloop \ KK = no wifi
when i'm on KK the phone works got, getting calls in and out
when i've flashed from recovery i've flashed only one zip file. didn't flash firmware nor modem

matanp said:
first, thanks for your reply
second:
at first i did a clean flash from fastboot like this: https://forums.oneplus.net/threads/tutorial-flashing-a-factory-image-from-scratch.142870/
i also tried the oneplus one fix for bootloops that also use fastboot from here: https://forums.oneplus.net/threads/fix-stuck-at-boot-logo-boot-loop-random-reboot.160199/
later, i tried flashing from recovery, also the colorOS rom
the common for all is LP = bootloop \ KK = no wifi
when i'm on KK the phone works got, getting calls in and out
when i've flashed from recovery i've flashed only one zip file. didn't flash firmware nor modem
Click to expand...
Click to collapse
Have you flashed the latest Lollipop build with fastboot as outlined in my guide?

not with your guide but with the guide in the link in my last post
also i don't remember seeing a userdata 64GB file in the lolipop image i had

matanp said:
not with your guide but with the guide in the link in my last post
also i don't remember seeing a userdata 64GB file in the lolipop image i had
Click to expand...
Click to collapse
That's because the LP images don't usually contain it, but the ones I link to do.

i'll try and report
thanks

i just got a message from oneplus support:
Hi Matan,
Thank you for reaching out. Sorry for the inconvenience that has caused to you. Rest assured that we will be providing you solutions in solving the issue.
You can also try to flash the device to the latest Oxygen OS, it is designed to fix common bugs that causes the issue.
To install OxygenOS on your OnePlus One, you need to flash the device. You may follow the guidance here:
https://forums.oneplus.net/threads/oxygenos-is-here-installation-guide.289398/
Please also note that since OxygenOS is a product from OnePlus therefore it is currently only available for OnePlus One.
Please don't hesitate to contact us for any update and feedback.
Thank you and have a good day.
Regards,
Jefflee
Click to expand...
Click to collapse
can i flash oxyOS (to check if it solve the problem) and after that flash your COS12 img with the fastboot commands or is there anything else i should know about?

flashed the latest COS12 version with your guide and i still have bootloops

Having this exact problem.... No wifi in CM11 and when updating tot CM12 getting boot looped.
Found a solution to your problem?

It's because of the modem files.. When u downgrade or upgrade from/to lollipop/kitkat u must flash the appropriate files!! Pm me if u want more info
Sent from my A0001 using Tapatalk

yes, i've open a ticket with oneplus one and their tech guy installed oxygenOS and it works well

Firmware type, 3rd party seller

Hi guys, I just got my Mi4c and I was wondering what mods can I do with it (install sMIUI). I am pretty scared about all this bootloader locking thing, and I am very unceirtan about firmware that came with the device. It was purchased in Hong Kong, and details are as follows:
Android version: 5.1.1 LMY47V
MIUI version: MIUI 7.0.4.0(LXKCNCI) Stable
Is it safe to flash, or will it lock BL?
Many thanks in advance

voolandis said:
Hi guys, I just got my Mi4c and I was wondering what mods can I do with it (install sMIUI). I am pretty scared about all this bootloader locking thing, and I am very unceirtan about firmware that came with the device. It was purchased in Hong Kong, and details are as follows:
Android version: 5.1.1 LMY47V
MIUI version: MIUI 7.0.4.0(LXKCNCI) Stable
Is it safe to flash, or will it lock BL?
Many thanks in advance
Click to expand...
Click to collapse
sMiui will not lock your bootloader, it's safe...
Just flash TWRP and you're ready..

ice-it said:
sMiui will not lock your bootloader, it's safe...
Just flash TWRP and you're ready..
Click to expand...
Click to collapse
Do you know if this is already custom firmware or official one. I don't see too many of chinese apps on it, just the Mi & MIUI ones...

voolandis said:
Do you know if this is already custom firmware or official one. I don't see too many of chinese apps on it, just the Mi & MIUI ones...
Click to expand...
Click to collapse
From build number it seems legit, but it's an old build...

ice-it said:
From build number it seems legit, but it's an old build...
Click to expand...
Click to collapse
Strange.
I've checked: I have locked bootloader and no custom recovery, but I have root.
What are my next steps for flashing?

voolandis said:
Strange.
I've checked: I have locked bootloader and no custom recovery, but I have root.
What are my next steps for flashing?
Click to expand...
Click to collapse
Read this discussion and follow the steps http://forum.xda-developers.com/mi-4c/general/mi4c-flash-twrps-recovery-cms-row-t3307801
When you have TWRP up and running you can flash whatever you want...
But it's very strange that you have a locked bl with an old China stable ROM...

ice-it said:
Read this discussion and follow the steps http://forum.xda-developers.com/mi-4c/general/mi4c-flash-twrps-recovery-cms-row-t3307801
When you have TWRP up and running you can flash whatever you want...
But it's very strange that you have a locked bl with an old China stable ROM...
Click to expand...
Click to collapse
Allright, just to clarify: bootloader wasn't locked after all. I managed to flash TWRP and gain root again after brick. Fastboot stable 7.1.6.0 ROM flashed via MiFlash, than run a .bat script for TWRP and flashed SuperSU.zip.

[FAQ][Anti-Rollback] All your questions are answered here.

Hi all.
So, as we know with recent MIUI update Xiaomi screwed our whyred. And this gave birth to many questions which is like a struggle for many users to find all those answers. So, I tried to answer all your questions. If you think your question isn't included please feel free to ask.
Q1: What is this "Anti-Rollback" thing?
A: Its a security measure that Google brought with the release of Android Oreo. It makes sure that your data is secure even when phone is stolen or if any attacker tries to downgrade the software and wants to gain control over your data.
Q2: How is this harmful to my device?
A: Well, as a security measure it should never give you a hard-brick. When someone tries to downgrade, it should display a warning and get turned off but there's difference between how things should work and how Xiaomi does. As Google has stated, "Anti-Rollback" should get automatically turn off when the user unlocks the bootloader but in case of MIUI even unlocked users are getting hard-bricks. Hopefully the developers of MIUI should push an update soon and if they don't, our beloved devs will find a way for sure
Q4: So, what now? Will Xiaomi solve this issue?
A: We do not know. But our beloved developers in the XDA-Forum will find a way for sure
Q5: How to know if my device is affected by it?
A: Run fastboot command :
Code:
fastboot getvar anti
The displayed output : 3 shall mean you're fine while 4 shall mean you're in the Anti-Rollback squad.
Q6: I'm in the Anti-Rollback squad what now?
A: Don't worry you can still flash custom recovery and roam around custom ROMs but avoid flashing any firmware or any MIUI ROM which is older than what you're using now otherwise you'll brick your device.
Q7: Which MIUI builds include "Anti-Rollback"?
A: All the MIUI builds which are released after Stable MIUI V9.5.17.0 and Beta MIUI V8.7.5 include "Anti-Rollback". And yes the Chinese versions are affected as well.
Q8: Do MIUI Stable V9.5.17.0 and Beta V8.7.5 have "Anti-Rollback" enabled?
A: NO. If you're on either of these builds you are safe to downgrade and use any older version.
Q9: How to flash custom recovery and custom ROMs on "Anti-Rollback" enabled devices?
A: On "Anti-Rollback" enabled ROMs you cann't flash custom recovery permanently. You'll have to boot into recovery first by running fastboot command:
Code:
fastboot boot xyz.img
(where xyz is name of your recovery file). Once you're booted into the custom recovery, copy the recovery image file in the internal storage and flash that recovery from recovery itself. Now you've successfully flashed custom recovery and you're good to go with custom ROMs. WARNING: Avoid flashing any firmware.
Q10: Can I migrate from Stable to Beta and vice-versa?
A: You can install Beta from Stable, make sure you flash latest Beta build same is the case with Stable. If you're on anti-4 firmware, whether its Beta or Stable you can switch to any anti-4 MIUI ROM Beta or Stable but remember you must flash latest version available while switching. (anti-4 means "Anti-Rollback" enabled firmware)
Q11: Can I unlock bootloader and flash custom ROMs on an "Anti-Rollback" enabled device?
A: Yes. Again to flash custom ROMs and recovery refer to Q9.
Q12Can I flash "Anti-Rollback" enabled ROM via TWRP?
AWell, in some cases it did work, just flash lazy flasher zip file after flashing MIUI ROM via TWRP. But while switching to MIUI from AOSP based ROMs on an "Anti-Rollback " enabled device I recommend you to go with fastboot method to avoid chances of brick.
For active discussion join whyred telegram group: https://t.me/redminote5proofficial
Hit thanks if helped.

Saabu said:
Q9: How to flash custom recovery and custom ROMs on "Anti-Rollback" enabled devices?
A: On "Anti-Rollback" enabled ROMs you cann't flash custom recovery permanently. You'll have to boot into recovery first
by running fastboot command:
Code:
fastboot boot xyz.img
(where xyz is name of your recovery file). Once
you're booted into the custom recovery, copy the recovery image file in the internal storage and flash that recovery
from recovery itself. Now you've successfully flashed custom recovery and you're good to go with custom ROMs.
WARNING: Avoid flashing any firmware.
Click to expand...
Click to collapse
Thanks for the above, but I believe that #9 is true. All MIUI roms regardless of version and anti roll back protection willl reflash the default MIUI recovery when you boot the OS. The only way to get it to stay is by flashing a custom ROM after TWRP, or by obtaining root and removing the "/system/bin/install-recovery.sh" file. If you're on anti-rollback you won't even be able to flash the recovery - you'll get an anti-rollback protection error.

This only concerns the "Xiaomi Redmi Note 5"?

For the Fastboot Command : fastboot getvar anti , I have : Anti:1 .. What does means ?
When you says "avoid flashing any firmware or any MIUI ROM which is older than what you're using now." , So Imagine if I have MIUI 10 Official with Android 8.1 and I Would like to flash like Xiaomi.eu or Lineage OS with Android 8.0 , The phone will brick ?
If I want to Flash Mod with TWRP Flashable Zip , the phone will brick or not ?
Thanks for your FAQ !

For me when i type fastboot devices it shows my device number but when i type this command fastboot getvar anti it shows nothing please help and im using Redmi note 5 vince version and miui version is 9.6.2.0 global stable.

kunal bro said:
For me when i type fastboot devices it shows my device number but when i type this command fastboot getvar anti it shows nothing please help and im using Redmi note 5 vince version and miui version is 9.6.2.0 global stable.
Click to expand...
Click to collapse
You answered yourself... It is ONLY for Redmi Note 5 (Pro) aka whyred! You are even in wrong device forum!

One doubt..... I am on AOSP right now. If I flash global beta 8.7.12 in twrp and then flash lazyflasher, will my twrp be removed !! Will I be able to go back to AOSP ?? @Saabu

DEBASISH said:
One doubt..... I am on AOSP right now. If I flash global beta 8.7.12 in twrp and then flash lazyflasher, will my twrp be removed !! Will I be able to go back to AOSP ?? @Saabu
Click to expand...
Click to collapse
After you flash a ROM that has Anti-Rollback enabled, you can still switch to AOSP anytime as I discussed in Q9. And yes, flashing lazy flasher simultaneously after MIUI will keep your TWRP.
Happy flashing

Saabu said:
Q5: How to know if my device is affected by it?
A: Run fastboot command :
Code:
fastboot getvar anti
The displayed output : 3 shall mean you're fine while 4 shall mean you're in the Anti-Rollback squad.
Click to expand...
Click to collapse
Hi, @Saabu,
Many thanks for the clarification.
However to enter the code through the fastboot, it has to be with the equipment turned off in fastboot mode, right?
Best regards,
Jorge

Jorge Moreira said:
Hi, @Saabu,
Many thanks for the clarification.
However to enter the code through the fastboot, it has to be with the equipment turned off in fastboot mode, right?
Best regards,
Jorge
Click to expand...
Click to collapse
Ofc.
Fastboot commands work only in fastboot mode?

Saabu said:
Ofc.
Fastboot commands work only in fastboot mode
Click to expand...
Click to collapse
It was a silly question, I know ...
Just to confirm....
Thanks,

I am a little concern about all this anti rollback matter...
well, the point is i am in xiaomi.eu rom, 8.6.28 (miui 10). I have checked the "anti" variable via the "fastboot getvar anti", and return 3.
Now, I would like to downgrade to miui 9 via twrp, and since I have "the 3 value" I understand that I can downgrade without any trouble, rigth?
However, I have found this https://xiaomi.eu/community/threads/antiroll-back.44975/
Here a guy have tried somehing similar and...briked phone.
What do I do now? Flash? i stay in a rom version that i dont like?
Thanks for your answers

nolohedecidido1 said:
I am a little concern about all this anti rollback matter...
well, the point is i am in xiaomi.eu rom, 8.6.28 (miui 10). I have checked the "anti" variable via the "fastboot getvar anti", and return 3.
Now, I would like to downgrade to miui 9 via twrp, and since I have "the 3 value" I understand that I can downgrade without any trouble, rigth?
However, I have found this https://xiaomi.eu/community/threads/antiroll-back.44975/
Here a guy have tried somehing similar and...briked phone.
What do I do now? Flash? i stay in a rom version that i dont like?
Thanks for your answers
Click to expand...
Click to collapse
You can flash any MIUI 9 with anti 3 via TWRP. Dont flash the ROMs with anti 4 via TWRP. Last MIUI ROMs with anti-3 were: Stable MIUI V9.5.17.0 and Beta MIUI V8.7.5.

Saabu said:
Hi all.
So, as we know with recent MIUI update Xiaomi screwed our whyred. And this gave birth to many questions which is like a struggle for many users to find all those answers. So, I tried to answer all your questions. If you think your question isn't included please feel free to ask.
Q1: What is this "Anti-Rollback" thing?
A: Its a security measure that Google brought with the release of Android Oreo. It makes sure that your data is secure even when phone is stolen or if any attacker tries to downgrade the software and wants to gain control over your data.
Q2: How is this harmful to my device?
A: Well, as a security measure it should never give you a hard-brick. When someone tries to downgrade, it should display a warning and get turned off but there's difference between how things should work and how Xiaomi does. As Google has stated, "Anti-Rollback" should automatically turn off when the user unlocks the bootloader but in case of MIUI even unlocked users are getting hard-bricks. Hopefully the developers of MIUI should push an update soon and if they don't, our beloved devs will find a way for sure
Q4: So, what now? Will Xiaomi solve this issue?
A: We do not know. But our beloved developers in the XDA-Forum will find a way for sure
Q5: How to know if my device is affected by it?
A: Run fastboot command : The displayed output : 3 shall mean you're fine while 4 shall mean you're in the Anti-Rollback squad.
Q6: I'm in the Anti-Rollback squad what now?
A: Don't worry you can still flash custom recovery and roam around custom ROMs but avoid flashing any firmware or any MIUI ROM which is older than what you're using now. Remember you cann't flash MIUI Stable over Beta otherwise you'll brick your device.
Q7: Which MIUI builds include "Anti-Rollback"?
A: All the MIUI builds which are released after Stable MIUI V9.5.17.0 and Beta MIUI V8.7.5 include "Anti-Rollback". And yes the Chinese versions are affected as well.
Q8: Do MIUI Stable V9.5.17.0 and Beta V8.7.5 have "Anti-Rollback" enabled?
A: NO. If you're on either of these builds you are safe to downgrade and use any older version.
Q9: How to flash custom recovery and custom ROMs on "Anti-Rollback" enabled devices?
A: On "Anti-Rollback" enabled ROMs you cann't flash custom recovery permanently. You'll have to boot into recovery first by running fastboot command: (where xyz is name of your recovery file). Once you're booted into the custom recovery, copy the recovery image file in the internal storage and flash that recovery from recovery itself. Now you've successfully flashed custom recovery and you're good to go with custom ROMs. WARNING: Avoid flashing any firmware.
Q10: Can I migrate from Stable to Beta and vice-versa?
A: You can install Beta from Stable and make sure you flash latest Beta build but installing Stable over Beta isn't possible yet.
Q11: Can I unlock bootloader and flash custom ROMs on an "Anti-Rollback" enabled device?
A: Yes. Again to flash custom ROMs and recovery refer to Q9.
For active discussion join whyred telegram group: https://t.me/redminote5proofficial
Hit thanks if helped.
Click to expand...
Click to collapse
Deleted

i have a question for my understanding. for example i want to install LOS 15.1. Where do i know if LOS uses ARB 3 or 4 ?

TM147 said:
i have a question for my understanding. for example i want to install LOS 15.1. Where do i know if LOS uses ARB 3 or 4 ?
Click to expand...
Click to collapse
When updating to LOS/AOSP based rom, its installer does not include firmware update. So you gonna have the same anti value after flashing it. Btw, check their official thread, they have clear installation instructions now.

what about my warranty if my phone is bricked?
will they do for free of cost
as my phone got bricked today 3 months old phone

If I delete firmware update folder in any rom ( with ARB4 ,ARB4,any older ROM) and flashing that will brick my phone ?

hargitomi said:
When updating to LOS/AOSP based rom, its installer does not include firmware update. So you gonna have the same anti value after flashing it. Btw, check their official thread, they have clear installation instructions now.
Click to expand...
Click to collapse
Thanks. but now i have some more question. Sorry this ARB Think is
Which official thread did you mean ? I found the official installation guide but i can't read anythink about devices with ARB4
... sorry can't post the link to LOS
Another thing that makes me thoughtful is Q2 in the beginning. "As Google has stated, "Anti-Rollback" should automatically turn off when the user unlocks the bootloader but in case of MIUI even unlocked users are getting hard-bricks."
So unlocking the bootloader is essential for flashing a custom recovery. What can/ must i do if i have a ARB4 Device to install TWRP ? On the TWRP side i can't read anything about this problem
.. sory can't post the link to TWRP
So please help me because i don't want to brick my device

iam on 8.7.5 with unlocked bootloader can i flash custom roms like los and rr rom by using twrp

Flash Q roms from OOS 10.0.4 BA

Hello I want to install a Android 10 ROM but I just can't do it. I've followed instructions and tried to install crdroid, Paranoid and Pixel Experience. Everything result as a never ending boot animation or "no command" screen.
The logcat spam me with
Code:
[email protected]::IVendorF ingerprintExtensions/default
ServiceManagement: getService: Trying again for [email protected]::IVendorF ingerprintExtensions/default...
I've followed those instructions
From last OOS, reboot to fastboot, boot TWRP, flash last OOS and TWRP, reboot, do the same, reboot, format Data, reboot, flash the ROM and TWRP, reboot.
I've may added some extra reboot to be sure but it should work fine.
What did I do wrong, is this because I come from a BA version and not AA ? or 10.0.4 instead of 10.0.3 ?
I need ppl to tell me if they were able to flash a ROM coming from 10.0.4 BA please.
Thx for your support

Please someone, don't tell me I'm the only one having a European firmware...

I can confirm this too when i use EU vendor (GM1913).
I just use MSM to convert the device to International (after backing up EVERYTHING).
Using MSM->Unlocking bootloader again->Installing AOSP

Svid said:
I can confirm this too when i use EU vendor (GM1913).
I just use MSM to convert the device to International (after backing up EVERYTHING).
Using MSM->Unlocking bootloader again->Installing AOSP
Click to expand...
Click to collapse
Thx it worked
I put the link for MSM tool here to complete your answer
https://forum.xda-developers.com/oneplus-7-pro/how-to/msm-tool-guac-t3934691

Why did you not just falsh the international version in twrp instead of the eu version and then flash a custom rom of your choice. No need for the msm tool.

hallo dare said:
Why did you not just falsh the international version in twrp instead of the eu version and then flash a custom rom of your choice. No need for the msm tool.
Click to expand...
Click to collapse
because you can't flash GM21AA stable on a GM21BA based rom (error 7)

Svid said:
because you can't flash GM21AA stable on a GM21BA based rom (error 7)
Click to expand...
Click to collapse
I did previously. No issues. Not sure if it's possible on latest version, but it did work

2nd attempt to upgrade to 12.2.4.0 from 12.0.4.0 failed and resulting in storage wipe

Hi,
I would like to know if anybody encountered this. This is my second time encountering this issue. I was on 12.0.4 and received a notification to perform update to 12.4.0. After downloading and rebooting, my twrp launched and after a few seconds instead of flashing, it went to the main menu page. After that, the phone just goes to fastboot mode and refused to boot. My phone has been rooted with magisk. Much appreciated for experts inputs.
The only way for me to boot my phone is to do a clean flash using mi flash tool and fallback to the old version...
Thank you.

spicediablo said:
Hi,
I would like to know if anybody encountered this. This is my second time encountering this issue. I was on 12.0.4 and received a notification to perform update to 12.4.0. After downloading and rebooting, my twrp launched and after a few seconds instead of flashing, it went to the main menu page. After that, the phone just goes to fastboot mode and refused to boot. My phone has been rooted with magisk. Much appreciated for experts inputs.
The only way for me to boot my phone is to do a clean flash using mi flash tool and fallback to the old version...
Thank you.
Click to expand...
Click to collapse
V12.0.4.0.QJKMIXM is a android 10 stable rom and V12.2.4.0.RJKMIXM is a android 11 stable beta rom which has many bugs.
V12.2.4.0.RJKEUXM is a stable rom that you can flash with miflash(but EEA not global).

After successfully going to v12.2.4.0, now I am finding that my current TWRP 3.4.1b unable to decrypt the phone thus not able to root it. I guess I have to fall back to 12.0.4.0 to be safe... I was tempted to go to 12.2.4.0 due to android 11 but looks like it's too problematic now due to beta. I was actually wondering why beta was pushed to me.
NOSS8 said:
V12.0.4.0.QJKMIXM is a android 10 stable rom and V12.2.4.0.RJKMIXM is a android 11 stable beta rom which has many bugs.
V12.2.4.0.RJKEUXM is a stable rom that you can flash with miflash(but EEA not global).
Click to expand...
Click to collapse

"I was actually wondering why beta was pushed to me "
You are not the only one, many users have reported this problem to XDA and c.mi.com
Try xiaomi.eu_multi_HMK30Pro_V12.2.2.0.RJKCNXM_v12-11 better than stock and on android 11.

spicediablo said:
After successfully going to v12.2.4.0, now I am finding that my current TWRP 3.4.1b unable to decrypt the phone thus not able to root it. I guess I have to fall back to 12.0.4.0 to be safe... I was tempted to go to 12.2.4.0 due to android 11 but looks like it's too problematic now due to beta. I was actually wondering why beta was pushed to me.
Click to expand...
Click to collapse
Now it is a stable rom https://xiaomifirmwareupdater.com/miui/lmi/stable/V12.2.4.0.RJKMIXM/
seems to be the same

Try flashing stock recovery before performing ota update. Flashing ota via twrp cause /storage inaccessible for me.

Thanks, so you updated with stock recovery without issues but are you able to flash twrp with the updated rom?
kopter36 said:
Try flashing stock recovery before performing ota update. Flashing ota via twrp cause /storage inaccessible for me.
Click to expand...
Click to collapse

NOSS8 said:
"I was actually wondering why beta was pushed to me "
You are not the only one, many users have reported this problem to XDA and c.mi.com
Try xiaomi.eu_multi_HMK30Pro_V12.2.2.0.RJKCNXM_v12-11 better than stock and on android 11.
Click to expand...
Click to collapse
Is that the most stable android 10 based on miui? I'm thinking about downgrading to many android 11 bugs on 12.2.4.0 global

Latin_lion_ said:
Is that the most stable android 10 based on miui? I'm thinking about downgrading to many android 11 bugs on 12.2.4.0 global
Click to expand...
Click to collapse
This is not a stock ROM and it is a android 11.

spicediablo said:
Thanks, so you updated with stock recovery without issues but are you able to flash twrp with the updated rom?
Click to expand...
Click to collapse
Yes i am able to successfully flashed twrp via fastboot afterward and directly proceed to root using magisk.
Everything works as usual, except, for me atleast, twrp now require pattern-type (3x3 dot) as password for decryption. Pin or character doesnt works.

Deleted.

To solve update problem you need to Rollback to stable stock rom, I used this:
Code:
lmi_global_images_V12.2.4.0.RJKMIXM_20201228.0000.00_11.0_global
extracted it.
then used mi flash from this toolkit:
Code:
mi-globe.com_Xiaomi_MiFlash_Pro_EN_5.3.1104.39.exe
sorry, but I cant provide links to downloads.

Moribus said:
To solve update problem you need to Rollback to stable stock rom, I used this:
Code:
lmi_global_images_V12.2.4.0.RJKMIXM_20201228.0000.00_11.0_global
extracted it.
then used mi flash from this toolkit:
Code:
mi-globe.com_Xiaomi_MiFlash_Pro_EN_5.3.1104.39.exe
sorry, but I cant provide links to downloads.
Click to expand...
Click to collapse
This is nothing new. With the bootloader unlock you can flash any version of stock rom with miflash.

kopter36 said:
Yes i am able to successfully flashed twrp via fastboot afterward and directly proceed to root using magisk.
Everything works as usual, except, for me atleast, twrp now require pattern-type (3x3 dot) as password for decryption. Pin or character doesnt works.
Click to expand...
Click to collapse
Successfully updated to 12.2.4.0. However, my nova launcher has been 'uninstalled' after this upgrade and I am unable to reinstall it with install fail error coming up. I am installing from apk. Anybody has this issue?