Database Info

[Need Help] I need to install Oreo (EMUI 8.0) Stock ROM in Mate 9 using TWRP 3.2.1-0

Hi folks. Sorry if this topic has been covered before. I really tried to find threads with a solution but I wasn't able to get specific answers. Kindly help me out.
This is the current status of my Huawei Mate 9 - MHA-l29
My Huawei Mate 9, MHA- L29 is working okay, aside from a few bugs I noticed after upgrading to Oreo (EMUI 8.0) using TWRP last year (a previous version)
I am running Android 8.0 Oreo. The version reads System 8.0.0.42(00YC) when I check in the "About Phone Section". When I check this version using HiSuite, it tells me that is the official one.
I have unlocked the bootloader FRP...basically everything is unlocked.
I have installed TWRP version 3.2.1-0
I suspect I may have accidentally wiped out the recovery for my device, so if I tried to do a factory reset, it may not work. That is why I wanted to just do a fresh installation of STOCK ROM for Oreo.
Now this is what I need help to do.
I wanted to do a fresh installation of the stock ROM for Oreo (8.0) for my Mate 9 device. I figure stock ROM will be more stable and it will be the official one anyway.
The reason I want to do a fresh install is because I noticed the current version has a few bugs that kept recurring whenever I did a factory reset (issues with themes, calendar, etc).
I wanted to know if I can use TWRP 3.2.1 (currently installed) to do an installation of Oreo stock ROM for my mate 9 using maybe the SD Card. I saw somewhere that I can simply copy the files to the SD card and then use TWRP 3.2.1-0 to do an installation.
If the above is possible, what do I need to do?
If it is not possible to use TWRP 3.2.1, what can I do instead so that I install a new stock ROM without bricking the phone? Please assist.
Thank you in advance for your time and help.

Mat3guy said:
Hi folks. Sorry if this topic has been covered before. I really tried to find threads with a solution but I wasn't able to get specific answers. Kindly help me out.
This is the current status of my Huawei Mate 9 - MHA-l29
My Huawei Mate 9, MHA- L29 is working okay, aside from a few bugs I noticed after upgrading to Oreo (EMUI 8.0) using TWRP last year (a previous version)
I have unlocked the bootloader FRP...basically everything is unlocked.
I suspect I may have accidentally wiped out the recovery for my device, so if I tried to do a factory reset, it may not work. That is why I wanted to just do a fresh installation of STOCK ROM for Oreo.
Now this is what I need help to do.
I wanted to do a fresh installation of the stock ROM for Oreo (8.0) for my Mate 9 device. I figure stock ROM will be more stable and it will be the official one anyway.
The reason I want to do a fresh install is because I noticed the current version has a few bugs that kept recurring whenever I did a factory reset (issues with themes, calendar, etc).
I wanted to know if I can use TWRP 3.2.1 (currently installed) to do an installation of Oreo stock ROM for my mate 9 using maybe the SD Card. I saw somewhere that I can simply copy the files to the SD card and then use TWRP 3.2.1-0 to do an installation.
If the above is possible, what do I need to do?
If it is not possible to use TWRP 3.2.1, what can I do instead so that I install a new stock ROM without bricking the phone? Please assist.
Thank you in advance for your time and help.
Click to expand...
Click to collapse
https://forum.xda-developers.com/honor-9/development/tool-flash-official-firmware-recovery-t3769279
Check out that tool. I've used it myself, works well.

Havoc Pie downgrade to Havoc Oreo doesnt work

Hey guys. Iam trying 1 week to get Havoc Oreo.
I used this https://forums.oneplus.com/threads/oxygenos-9-0-ota-for-the-oneplus-6.909533/ to get base Oreo Rom on my OP6. This works.
But when i want to flash Havoc Oreo (Havoc-OS-20180904-enchilada-Official.zip) via TWRP (twrp-installer-enchilada-3.2.2-0.zip only this Version works for me) i get a loop in fastboot.
Can someone help me pls?
My instruction:
1. Flash downgrade
2. Go fastboot, boot TWRP
3. Flash TWRP via ADB SIDELOAD
4. Restart to recovery
5. Flash Havoc Oreo via ADB SIDELOAD
6. Restart
7. Bootloop Fastboot mode
thanks for any help.

RockstarLover said:
Hey guys. Iam trying 1 week to get Havoc Oreo.
I used this https://forums.oneplus.com/threads/oxygenos-9-0-ota-for-the-oneplus-6.909533/ to get base Oreo Rom on my OP6. This works.
But when i want to flash Havoc Oreo (Havoc-OS-20180904-enchilada-Official.zip) via TWRP (twrp-installer-enchilada-3.2.2-0.zip only this Version works for me) i get a loop in fastboot.
Can someone help me pls?
My instruction:
1. Flash downgrade
2. Go fastboot, boot TWRP
3. Flash TWRP via ADB SIDELOAD
4. Restart to recovery
5. Flash Havoc Oreo via ADB SIDELOAD
6. Restart
7. Bootloop Fastboot mode
thanks for any help.
Click to expand...
Click to collapse
OK, so I am not sure what exists in the OnePlus forums but lets start with:
1. You are aware there are two sets of partitions on this device correct? If not, please read here: https://forum.xda-developers.com/oneplus-6/how-to/guide-noobs-guide-to-b-partitions-op6-t3816123
2. What are you running now?
3. You need to update your TWRP to blu_spark but I am not sure if the latest (v9.91) works with Oreo... I know that v9.86 works with Oreo for sure. Read and download from here: https://forum.xda-developers.com/oneplus-6/development/kernel-t3800965
4. Get the appropriate OOS zip file from this thread: https://forum.xda-developers.com/oneplus-6/how-to/oneplus-6-mirrors-official-oxygen-os-t3792244
Specifically OOS 5.1.11: https://www.androidfilehost.com/?fid=1322778262903980680
The basic steps should be like this (all assumes you have and unlocked bootloader):
1. If you are running OOS 5.1.11, reboot to fastboot
2. Boot blu_spark TWRP.img - fastboot boot twrp.xxx.img
3. Flash OOS 5.1.11
4. Flash blu_spark TWRP.zip to get it on both slots
5. Reboot to RECOVERY
6. Flash OOS 5.1.11
7. Flash blu_spark TWRP.zip
8. Factory reset in TWRP
9. Flash Havoc Oreo zip
10. Flash blu_spark TWRP.zip
11. Reboot to RECOVERY
12. Flash GApps
13. Flash Magisk (optional if you want root)
14. Flash no-verity if you plan to run unencrypted. (optional)
My advice is to READ READ READ before going forward with anything. The A/B partition layout is far from the traditional days of a single partition layout with a recovery partition. Educate yourself or risk bricking your device and opening up a whole different set of problems.

i do this by step by step but now iam bricked. after all it want restart but it glows only the blue led

RockstarLover said:
i do this by step by step but now iam bricked. after all it want restart but it glows only the blue led
Click to expand...
Click to collapse
It does sound like you READ READ READ before proceeding... My steps were not intended as a step-by-step guide, which is why I said the steps "should look like this". You didn't answer any of my questions, so I have no idea where you started from or where things went wrong to get you into this state...
Can you get into fastboot mode?
If so, try this thread first: https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665
The fastboot restore method will ONLY work if you know which OOS you were running before you got bricked...
If you can't restore from fastboot images, try this thread: https://forum.xda-developers.com/oneplus-6/how-to/tool-msmdownloadtool-v4-0-international-t3798892
I cannot stress enough, you MUST read all the steps and understand what you are doing before doing anything. If you have any questions, ASK before proceeding... Good luck.

thank u for ur help. i used the second method because the first didnt worked and now iam unbricked.
1. You are aware there are two sets of partitions on this device correct?
Click to expand...
Click to collapse
I know it
2. What are you running now?
Click to expand...
Click to collapse
Now iam running Oxygen OS 5.1.5 Android 8.1.0 and Device State is locked
Is this normal that in fastboot shows this bootloader and baseband empty ?
productname - xxx
variant -sdm ufs
bootloader version -
baseband version -
serialnumber - xxxxxxx
secure boot - yes
I want to try again to get havoc oreo. i will w8 for ur response.

RockstarLover said:
thank u for ur help. i used the second method because the first didnt worked and now iam unbricked.
I know it
Now iam running Oxygen OS 5.1.5 Android 8.1.0 and Device State is locked
Is this normal that in fastboot shows this bootloader and baseband empty ?
productname - xxx
variant -sdm ufs
bootloader version -
baseband version -
serialnumber - xxxxxxx
secure boot - yes
I want to try again to get havoc oreo. i will w8 for ur response.
Click to expand...
Click to collapse
You are back up and running, good work! Congrats!
When you say the device is 'locked', you mean the bootloader is locked again? It shows 'Locked' in fastboot? Obviously you need to unlock the bootloader again before proceeding if this is the case...
And 'Yes', it is normal for 'bootloader version' and 'baseband' to be blank. It shows the same on my device anyway, and I can flash custom ROMs with no issues, and everything works.
At this point, you should be able to follow the steps in my post, making sure you first unlock the bootloader (which will wipe all of your data). You might want to format data (not just wipe as well) to start fresh. I would also confirm that there are no issues running Havoc Oreo with encryption (I'd recommend asking the question in the Havoc OnePlus telegram channel, https://t.me/havoconeplus). After people ask to "Why are you running Oreo?!?!", you just might get an answer... I dumped being encrypted after about a week of having this device because it made moving between ROMs more difficult.
In step 14, I mention the no-verity file to remove force encryption. I have attached it to this post. Again, you may want to have /data encrypted (necessity, personal preference etc.) so this isn't mandatory but I found it made flashing different ROM's much easier (personal preference really).

do u know where u find the havoc oreo rom now ? they changed their download directory. and the overview is confusing me.

RockstarLover said:
do u know where u find the havoc oreo rom now ? they changed their download directory. and the overview is confusing me.
Click to expand...
Click to collapse
Looks like they removed Oreo builds, you might be out of luck. Check out XenonHD 8.1 thread if your set on running Oreo, was updated to Dec. Security patch.

hey brother. i have good news. i just want download again havoc oreo cause i deleted the old zip. i had thought maybe the oreo havoc zip was faulty. now i restored it with a restore tool. i tried again and now it works.
IAM ON HAVOC OREO . It starts but now i got a message.
"Android System
A vendor image mismatch has been detected. Typically this means your vendor image is out of date.Please ensure your vendor image matches OPM1.171019.011."
what is this now

RockstarLover said:
hey brother. i have good news. i just want download again havoc oreo cause i deleted the old zip. i had thought maybe the oreo havoc zip was faulty. now i restored it with a restore tool. i tried again and now it works.
IAM ON HAVOC OREO . It starts but now i got a message.
"Android System
A vendor image mismatch has been detected. Typically this means your vendor image is out of date.Please ensure your vendor image matches OPM1.171019.011."
what is this now
Click to expand...
Click to collapse
Did you flash OOS 5.1.11 on both slots? I know you said you were on OOS 5.1.5 when you did the MSM tool restore.
Unsure if the Havoc build you are running requires a certain FW. Usually the devs update the blobs on customer ROMs based on the latest releases of OOS. In this case, 5.1.11 was the last version of OOS Oreo.

i was on 5.1.5 and flashed 5.1.11 on both slots and then i flashed havoc rom

RockstarLover said:
i was on 5.1.5 and flashed 5.1.11 on both slots and then i flashed havoc rom
Click to expand...
Click to collapse
I'd recommend just going to Pie. I haven't run Havoc in over a month but the latest AEX is solid and battery life is excellent. The Pie ROMs have stabilized significantly in the last month.

i just flashed the latest havoc rom now. Really really thanks brother. ur a good boy.
have a good year

Android 11 Red Magic Rom [FLASHGUIDE]

Hello again!
I saw a post where leipnacht provides a link to the public beta of Android R. (I let you here a drive link to download it faster).
I flashed it and it's working properly on my device. There is some bugs, but the most part of the things works without problems (Personally, I didn't face any bug itself (only a low noise with the vibration by the moment), but there are some comments in the page of bbs nubia about some problems with other things.
The previous conditions from where I update to Android R Red Magic Rom were using a GSI in the Android 10 chinese version of the rom. So, the steps I followed are:
1. In the recovery, wipe data, cache and dalvik. Also, format data.
2. Flash in the Android 10 TWRP the Android R rom.
3. Flash this NikGapps Package , Magisk Debug and DFE (Encrypt disabler in order to be able decrypt data in the recovery). I also flashed Permissive_5 but I think there is no need to do it.
4. Boot and enjoy.
I will attach all the files and some screenshots for those who want to take a see to the rom. Personally, I feel no changes in this version, but, as always, the performance is great and it runs really smooth. It's a beta version, so I hope more changes in the future.
P.D. In order to get safetynet passing, I used HideProps Config magisk module. There is no big issues with it, and everything is fixable
P.d.2. This rom has antiroll-back active, so if you want to go back to previous version, you will have to use the unbrick tool

Perseo99 said:
Hello again!
I saw a post where leipnacht provides a link to the public beta of Android R. (I let you here a drive link to download it faster).
I flashed it and it's working properly on my device. There is some bugs, but the most part of the things works without problems (Personally, I didn't face any bug itself (only a low noise with the vibration by the moment), but there are some comments in the page of bbs nubia about some problems with other things.
The previous conditions from where I update to Android R Red Magic Rom were using a GSI in the Android 10 chinese version of the rom. So, the steps I followed are:
1. In the recovery, wipe data, cache and dalvik. Also, format data.
2. Flash in the Android 10 TWRP the Android R rom.
3. Flash this NikGapps Package , Magisk Debug and DFE (Encrypt disabler in order to be able decrypt data in the recovery). I also flashed Permissive_5 but I think there is no need to do it.
4. Boot and enjoy.
I will attach all the files and some screenshots for those who want to take a see to the rom. Personally, I feel no changes in this version, but, as always, the performance is great and it runs really smooth. It's a beta version, so I hope more changes in the future.
P.D. In order to get safetynet passing, I used HideProps Config magisk module. There is no big issues with it, and everything is fixable
P.d.2. This rom has antiroll-back active, so if you want to go back to previous version, you will have to use the unbrick tool
Click to expand...
Click to collapse
Thanks for the update.
I have been planning to upgrade my Red Magic 3 to Android 10 (CN rom) for quite a while now. And its good to know A11 beta has arrived too.
Have you tried fps games on this device like pubg mobile, cod etc? Do they work properly ?
Also, I haven't even unlocked bootloader on my device. Can you proivde a better guide, to completely switch from global rom (stock) to A11 (beta) or A10 CN rom (stable).
Need links / guide for following items -
- Unlock bootloader
- Link of working twrp and steps to flash (should I change recovery after installing this beta?)
- Gapps and Magisk link (As I can't run this device without Google services).
It will be a huge help for me to get started.
Take your time with it (no rush).
Thanks in advance!!!

nalin_s3 said:
Thanks for the update.
I have been planning to upgrade my Red Magic 3 to Android 10 (CN rom) for quite a while now. And its good to know A11 beta has arrived too.
Have you tried fps games on this device like pubg mobile, cod etc? Do they work properly ?
Also, I haven't even unlocked bootloader on my device. Can you proivde a better guide, to completely switch from global rom (stock) to A11 (beta) or A10 CN rom (stable).
Need links / guide for following items -
- Unlock bootloader
- Link of working twrp and steps to flash (should I change recovery after installing this beta?)
- Gapps and Magisk link (As I can't run this device without Google services).
It will be a huge help for me to get started.
Take your time with it (no rush).
Thanks in advance!!!
Click to expand...
Click to collapse
Hey!
No problem at all. I let you here two guides to migrate to the cn rom and even a gsi
Be careful and aware about what you are going to do, It's not specially difficult but you have to get ready all the files and tools in case of brick or bootloops.
Enjoy the flashing!

Perseo99 said:
Hey!
No problem at all. I let you here two guides to migrate to the cn rom and even a gsi
Be careful and aware about what you are going to do, It's not specially difficult but you have to get ready all the files and tools in case of brick or bootloops.
Enjoy the flashing!
Click to expand...
Click to collapse
Thanks for the links. I am planning to update to stable A10 version for now.
I have few questions it be a huge help you could clear some of my doubts -
1. After unlocking bootloader I have to install TWRP (for gapps to run). So should I install TWRP after flashing CN rom ? or before ?
I am asking this because I read in some guides that only CN rom is custom recovery capable.
2. If you have run A10 stables before, does OTA updates require to be installed via TWRP only ?
Will I loose Gapps and Root access if I updated the ota directly from settings? And will every rom flash with TWRP clear my installed apps ?
Thanks in advance for helping!!. ??

nalin_s3 said:
Thanks for the links. I am planning to update to stable A10 version for now.
I have few questions it be a huge help you could clear some of my doubts -
1. After unlocking bootloader I have to install TWRP (for gapps to run). So should I install TWRP after flashing CN rom ? or before ?
I am asking this because I read in some guides that only CN rom is custom recovery capable.
2. If you have run A10 stables before, does OTA updates require to be installed via TWRP only ?
Will I loose Gapps and Root access if I updated the ota directly from settings? And will every rom flash with TWRP clear my installed apps ?
Thanks in advance for helping!!. ?
Click to expand...
Click to collapse
Well, I will go in order:
1. You have to flash first in the stock recovery the Android 10 CN rom and then flash the custom recovery. There is no twrp avaible for global rom. Once in the custom recovery, you can flash Gapps and Magisk (in android 10 there is no need of DFE file, the recovery is able to decrypt data properly.
2. You don't need to get worried about OTAs, there is no a constant software update work by nubia for this device, but in case of update, you would flash the rom from the offcial page, with magisk and gapps again and be sure you keep the custom recovery.

Perseo99 said:
Hello again!
I saw a post where leipnacht provides a link to the public beta of Android R. (I let you here a drive link to download it faster).
I flashed it and it's working properly on my device. There is some bugs, but the most part of the things works without problems (Personally, I didn't face any bug itself (only a low noise with the vibration by the moment), but there are some comments in the page of bbs nubia about some problems with other things.
The previous conditions from where I update to Android R Red Magic Rom were using a GSI in the Android 10 chinese version of the rom. So, the steps I followed are:
1. In the recovery, wipe data, cache and dalvik. Also, format data.
2. Flash in the Android 10 TWRP the Android R rom.
3. Flash this NikGapps Package , Magisk Debug and DFE (Encrypt disabler in order to be able decrypt data in the recovery). I also flashed Permissive_5 but I think there is no need to do it.
4. Boot and enjoy.
I will attach all the files and some screenshots for those who want to take a see to the rom. Personally, I feel no changes in this version, but, as always, the performance is great and it runs really smooth. It's a beta version, so I hope more changes in the future.
P.D. In order to get safetynet passing, I used HideProps Config magisk module. There is no big issues with it, and everything is fixable
P.d.2. This rom has antiroll-back active, so if you want to go back to previous version, you will have to use the unbrick tool
Click to expand...
Click to collapse
Can you check your pm??

There's no problem in flashing but take note there's no going back i mean you cant downgrade it anymore using unbric tool even if you flash rom using cmd it will not work my rm3s now is bricked theres no tool or method that can fix it right now. Unless someone make a new unbrick tool

jepoyxxv said:
There's no problem in flashing but take note there's no going back i mean you cant downgrade it anymore using unbric tool even if you flash rom using cmd it will not work my rm3s now is bricked theres no tool or method that can fix it right now. Unless someone make a new unbrick tool
Click to expand...
Click to collapse
I already went to 11 and flash to 3.11

But how did you flash android 10 3.11 in rm3s no matter what tool i use i cant fix my rm3s from being bricked by flashing android 11 beta can you tell me what did you do did you flash it manually in command prompt please help me

jepoyxxv said:
But how did you flash android 10 3.11 in rm3s no matter what tool i use i cant fix my rm3s from being bricked by flashing android 11 beta can you tell me what did you do did you flash it manually in command prompt please help me
Click to expand...
Click to collapse
If you are in 11 beta and want to downgrade..just simple flash global version and again flash 3.11 done

What did you use to flash global rom lastweek i successfully installed android 11 beta and use unbrick tool to go back to global but i got bricked. And i cant fix it anymore.

jepoyxxv said:
What did you use to flash global rom lastweek i successfully installed android 11 beta and use unbrick tool to go back to global but i got bricked. And i cant fix it anymore.
Click to expand...
Click to collapse
I just flash global from otg and tham again 3.11

walkwitmeinhel said:
I just flash global from otg and tham again 3.11
Click to expand...
Click to collapse
Could you please tell me where to download the 3.11 rom. I am not aware that this rom exists. Is this a CN or global rom? Thanks for your reply.

[email protected] said:
Could you please tell me where to download the 3.11 rom. I am not aware that this rom exists. Is this a CN or global rom? Thanks for your reply.
Click to expand...
Click to collapse
http://ui.nubia.cn/rom/detail/64

Oh! Didn't expect that. I just post this for Red Magic 3 device users. I don't know how RM3S actually works. Have you tried the unbrick tool from chinese version? Or just flashing the global rom from recovery is enough?

Wait is there a chinese unbrick tool cn. version for red magic can you provide me a link.. unbrick tool 3/3s.global by jerry is not working anymore if you got brick by android 11 beta rom...

jepoyxxv said:
Wait is there a chinese unbrick tool cn. version for red magic can you provide me a link.. unbrick tool 3/3s.global by jerry is not working anymore if you got brick by android 11 beta rom...
Click to expand...
Click to collapse
Let's see. Here is a link for Red Magic 3S unbrick tool. Download the non-eu ones.
If you have a Red Magic 3 with Red Magic 3s software, I will provide you the link to the other unbrick tool.
Also, you can try flashing the global rom from the stock recovery included in the package of the A11 rom that you have download.

Thanks for replying my bro.. my device is rm3s i already use rm3 and rm3s unbrick tool.. downloading fire hose programmer and image was successfully but.. my phone is still corrupted... And one thingg i dont have twrp install in my rm3s thats why its hard for me to fix it.. can you please guide or teach me how to flash stock recovery using global rom i know how to use cmd and adb

jepoyxxv said:
Wait is there a chinese unbrick tool cn. version for red magic can you provide me a link.. unbrick tool 3/3s.global by jerry is not working anymore if you got brick by android 11 beta rom...
Click to expand...
Click to collapse
So then, It's not a problem of the unbrick tool, that is actually working properly. The thing is that you didn't know how to do a correct process to migrate from cm rom to global...
The first thing you should do is reboot the phone into fastboot mode (power+vol. Down). Then, connect the phone to the PC and type the next commands in the cmd:
Code:
fastboot devices
in order to see if your device is being recognized
Code:
fastboot oem nubia_unlock NUBIA_NX629J
to unlock the bootloader
Code:
fastboot flashing unlock
in order to make your phone able to boot with a modified software. In the moment you will enter this command, you will see a screen advising you about your data (it'll be erased once you accept to unlock flashing).
After that, you can reboot your phone, that will show you an screen advising you that the bootloader is open. Accept and continue without problems.
Tell me if you have been able to make your phone boot.

Perseo99 said:
Well, I will go in order:
1. You have to flash first in the stock recovery the Android 10 CN rom and then flash the custom recovery. There is no twrp avaible for global rom. Once in the custom recovery, you can flash Gapps and Magisk (in android 10 there is no need of DFE file, the recovery is able to decrypt data properly.
2. You don't need to get worried about OTAs, there is no a constant software update work by nubia for this device, but in case of update, you would flash the rom from the offcial page, with magisk and gapps again and be sure you keep the custom recovery.
Click to expand...
Click to collapse
Required in CN A10 + twrp A10, or maybe from CN A9 + twrp A9 to be able to flash

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?

Can't install Pixel Experience Custom Android 12

I have been struggling to install Pixel Experience Android 12 on my Poxo X3 NFC.
I had PE Android 11 before. When I tried to flash Android 12 I get following error
assert failed: update_dynamic_partition(package_extract_file("dynamic_partition_op_list"))
Updater process ended with ERROR: 1
Error installing zip file ...
What I tried
1, Install latest firmware
2. Format Data
3. Wipe data, dalvik, cache
3. Sideloading Custom Rom
Can someone help me to revive my device please?
Thanks a lot

Hello, on my wife's X3NFC I had to flash the latest Full ROM (12.5.7) via Fastboot.
Then I was able to install the lA12 PE. I don't know why I had to do this, but it worked.
She didn't like A12 PE and now A11 PE is running again on her Phone
Maybe (I heard about that) it works too, if you only flash the super.img from latest Fastboot-Image via Recovery.

SmartJuwel said:
Hello, on my wife's X3NFC I had to flash the latest Full ROM (12.5.7) via Fastboot.
Then I was able to install the lA12 PE. I don't know why I had to do this, but it worked.
She didn't like A12 PE and now A11 PE is running again on her Phone
Maybe (I heard about that) it works too, if you only flash the super.img from latest Fastboot-Image via Recovery.
Click to expand...
Click to collapse
I installed MIUI fastboot rom. Then I tried to flash PE A12 rom without any issues. But after successful completion, phone reboots to bootloader (Fastboot). Can you tell me what I am doing wrong?
Can you please give me steps to install PE after you've installed MIUI fastboot rom?

1st installed latest MIUI via MiFlash
Booting successful into MIUI
Flashing TWRP in Fastboot-Mode
Booting into TWRP, install ROM, wipe Caches and format data.
Reboot Phone

i'm in this very predicament. Still on PE11 Plus Edition and can't flash PE12 giving me the very same ERROR. Can someone pls post the sure way to get this done properly? Links to roms that must be flashed first would be very appreciated...

Snakeatermgs said:
i'm in this very predicament. Still on PE11 Plus Edition and can't flash PE12 giving me the very same ERROR. Can someone pls post the sure way to get this done properly? Links to roms that must be flashed first would be very appreciated...
Click to expand...
Click to collapse
SmartJewel (Post above you) told you how to do it