Database Info

I am about to downgrade my P40 Pro and I have some questions

Hello,
Lurker here. I want to downgrade my Huawei P40 Pro to a lower firmware to install GMS. For what is worth, I did some digging around to find out what would be the most safe way to do it and this is what I came up (did).
Firmware: I saw a lot of people have problems with their phones rebooting because of a wrong firmware version. I wanted to download my own off of MT-Team's database, but I noticed, that I cant seem to find my exact firmware. To be more precise, I'm not just looking at my area code, but also at the exact same build number: C432E8R5P2. I can't seem to find this exact build on MT-Team's database, so went somewhere else. I already bought a firmware from this site (I cant post links so I will just add a photo).
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
The firmware build number is exactly the same as mine (C432E8R5P2), not the mention that all the other info of the model and everything seems to check out. With what I bought, I would be downgrading to EMUI version 10.1.0.114.
Questions:
1. When choosing the right firmware, is its important that the whole build number matches? If so, have I chosen the right firmware? Do any of you know the vendor, is the software safe?
2. If the downgrade is successful, is its still possible to install GMS with an EMUI version 10.1.0.114?
Downgrade process: I am planning to wipe my phone clean before the whole process, buy an OTG cable and downgrade from an USB drive, because the whole process through HiSuite seems to have more risk, depending on the programs version, or am I wrong?
Questions:
3. Is it safer to downgrade from an USB drive via OTG cable, in comparison to HiSuite?
4. If the downgrade is not successful with the OTG cable/USB drive, what version of HiSuite should I use to downgrade the phone?
5. If my phone soft-bricks, are the any methods to fix it?
Thanks in advance

Anyone help?

compare it with more site
Cosim15 said:
Anyone help?
Click to expand...
Click to collapse
Try to check the comparison with other pages so you can see the various information.

Hope this helps someone.
I successfully downgraded my Huawei P40 Pro.
Some details:
I could not go through with my initial plan, as the phone did not recognize the firmware, so I had to find another way.
I found my firmware (C432E8R5P2) via MT Firmware finder (PC), to version 10.1.0.131 with my exact firmware version (C432E8R5P2). Its number 409481 in the firmware finder, if this helps anyone. IMEI number also checked it out available for install.
I used HiSuite proxy and HiSuite 10.0.0.510 (because the newer versions did not let me connect to the proxy).
Wiped the whole phone clean + cache wipe.
Downgraded successfully and at the very end of it (once the downgrade is complete, it says it will now restart), restarted the phone to enter recovery (before it could restart into OS) - wipe the phone clean again + cache wipe.
Once booted, I did not get ANY errors, it was like a new phone. Used Googlefier to install GMS, it works.
Had NO problems with the phone, it let me update back to 10.1.0.176 (C432E8R5P2) and GMS is still working perfectly. No issues with the update, no use of HiSuite to update or anything.
10/10.
Hope this helps someone who has the exact firmware version as mine. I did not risk anything but the EXACT number as a whole. Worked the whole day to get this done.
Cheers

Cosim15 said:
Hope this helps someone.
I successfully downgraded my Huawei P40 Pro.
Some details:
I could not go through with my initial plan, as the phone did not recognize the firmware, so I had to find another way.
I found my firmware (C432E8R5P2) via MT Firmware finder (PC), to version 10.1.0.131 with my exact firmware version (C432E8R5P2). Its number 409481 in the firmware finder, if this helps anyone. IMEI number also checked it out available for install.
I used HiSuite proxy and HiSuite 10.0.0.510 (because the newer versions did not let me connect to the proxy).
Wiped the whole phone clean + cache wipe.
Downgraded successfully and at the very end of it (once the downgrade is complete, it says it will now restart), restarted the phone to enter recovery (before it could restart into OS) - wipe the phone clean again + cache wipe.
Once booted, I did not get ANY errors, it was like a new phone. Used Googlefier to install GMS, it works.
Had NO problems with the phone, it let me update back to 10.1.0.176 (C432E8R5P2) and GMS is still working perfectly. No issues with the update, no use of HiSuite to update or anything.
10/10.
Hope this helps someone who has the exact firmware version as mine. I did not risk anything but the EXACT number as a whole. Worked the whole day to get this done.
Cheers
Click to expand...
Click to collapse
Hi I would like to know how to know its version on MT Firmware finder (PC) because there is a lot of version for my case I am looking for the 10.1.0.131 (C432E8R6P1) currently I am on 10.1.0.176 (C432E8R6P1) how to know the correct version to download and how to downgrade thank you

Cosim15 said:
Hello,
Lurker here. I want to downgrade my Huawei P40 Pro to a lower firmware to install GMS. For what is worth, I did some digging around to find out what would be the most safe way to do it and this is what I came up (did).
Firmware: I saw a lot of people have problems with their phones rebooting because of a wrong firmware version. I wanted to download my own off of MT-Team's database, but I noticed, that I cant seem to find my exact firmware. To be more precise, I'm not just looking at my area code, but also at the exact same build number: C432E8R5P2. I can't seem to find this exact build on MT-Team's database, so went somewhere else. I already bought a firmware from this site (I cant post links so I will just add a photo).
The firmware build number is exactly the same as mine (C432E8R5P2), not the mention that all the other info of the model and everything seems to check out. With what I bought, I would be downgrading to EMUI version 10.1.0.114.
Questions:
1. When choosing the right firmware, is its important that the whole build number matches? If so, have I chosen the right firmware? Do any of you know the vendor, is the software safe?
2. If the downgrade is successful, is its still possible to install GMS with an EMUI version 10.1.0.114?
Downgrade process: I am planning to wipe my phone clean before the whole process, buy an OTG cable and downgrade from an USB drive, because the whole process through HiSuite seems to have more risk, depending on the programs version, or am I wrong?
Questions:
3. Is it safer to downgrade from an USB drive via OTG cable, in comparison to HiSuite?
4. If the downgrade is not successful with the OTG cable/USB drive, what version of HiSuite should I use to downgrade the phone?
5. If my phone soft-bricks, are the any methods to fix it?
Thanks in advance
Click to expand...
Click to collapse
-------------- here you will find the solution https://forum.xda-developers.com/android/apps-games/googlefier-install-gms-huawei-honor-t4180485

samlis said:
Hi I would like to know how to know its version on MT Firmware finder (PC) because there is a lot of version for my case I am looking for the 10.1.0.131 (C432E8R6P1) currently I am on 10.1.0.176 (C432E8R6P1) how to know the correct version to download and how to downgrade thank you
Click to expand...
Click to collapse
Did you get this resolved?

Cosim15 said:
Hope this helps someone.
I successfully downgraded my Huawei P40 Pro.
Some details:
I could not go through with my initial plan, as the phone did not recognize the firmware, so I had to find another way.
I found my firmware (C432E8R5P2) via MT Firmware finder (PC), to version 10.1.0.131 with my exact firmware version (C432E8R5P2). Its number 409481 in the firmware finder, if this helps anyone. IMEI number also checked it out available for install.
I used HiSuite proxy and HiSuite 10.0.0.510 (because the newer versions did not let me connect to the proxy).
Wiped the whole phone clean + cache wipe.
Downgraded successfully and at the very end of it (once the downgrade is complete, it says it will now restart), restarted the phone to enter recovery (before it could restart into OS) - wipe the phone clean again + cache wipe.
Once booted, I did not get ANY errors, it was like a new phone. Used Googlefier to install GMS, it works.
Had NO problems with the phone, it let me update back to 10.1.0.176 (C432E8R5P2) and GMS is still working perfectly. No issues with the update, no use of HiSuite to update or anything.
10/10.
Hope this helps someone who has the exact firmware version as mine. I did not risk anything but the EXACT number as a whole. Worked the whole day to get this done.
Cheers
Click to expand...
Click to collapse
I am having difficulty navigating through the MT Firmware finder. Please help. I have your exact model/firmware.

femabod said:
I am having difficulty navigating through the MT Firmware finder. Please help. I have your exact model/firmware.
Click to expand...
Click to collapse
That older method doesnt work anymore. See my thread ( in my signature, from computer) for the new methods.

Question Touchscreen doesn't work after update to LE2113_11.C.47 [SOLVED]

I'm looking for a captain who could help me find solution. Like "EtherealRemnant" in his post, Im not able to get OOS 12 work on my OP9.
EtherealRemnant post:
https://forum.xda-developers.com/t/...p9-stock-oos-11-2-2-2aa.4275727/post-86854951
Like "everyone" I've something messed up with TWRP boot and ended up with MSM tool. Cause I have LE2113 I have to use India MSM for 9Pro.
Then I use downgrade package to get stock OOS on my OP9, then use oficial way to update OOS, till highest A11. But whenever I use update to LE2113_11.C.47 it ended up with frozen/not working touch screen. Not just in OS but also in TWRP and stock recovery. I´ve tried also connect USB mouse, but with no successs.
My question, is there a way how to update to OOS (A12) without get freezed touchscreen?
EDIT:
Whole problem was in usage of wrong MSM (INDIAN OP9pro, EU OP9pro). So if you want to recover yours OP9 (EU) LE2113, you have to use MSM tool from allenjthomsen (Thank you!).
More abotu this tool here

I was able to get my device back to stock software by modding the MSM Tool for global but then I gave it to someone else to try to help them and it didn't work. I have sent a PM to the person who mods these images for some help.
Have you tried using the full install zip for BA using the system updater? I didn't actually try that before I messed around with the MSM Tool. Put this in the root of your storage and go to updater and do the local upgrade.
https://otafsg-cost-az.coloros.com/OnePlus9_EEA/OnePlus9Oxygen_22.E.13_GLO_0130_2111112104/patch/amazone2/GLO/OnePlus9Oxygen/OnePlus9Oxygen_22.E.13_GLO_0130_2111112104/OnePlus9Oxygen_22.E.13_OTA_0130_all_2111112104_f4acbf.zip
It seems like what is happening is even after you get it back to stock software, there is a flag somewhere that's designating the device as an Indian 9 Pro. Once I got the modified global MSM Tool I made to flash my phone, the problem stopped because my phone was fully global again and I've been back on OOS 12 C.48 since Saturday evening (for better or worse, OOS 12 has a lot of issues but I don't want to risk another brick for awhile, especially since I'm not sure that the mod I made actually worked and it wasn't just some freak coincidence that let me flash back).

Thank you for your reply, the link you've send is downloading:
OnePlus9Oxygen_22.E.13_OTA_0130_all_2111112104_f4acbf.zip
I've presume that is for Global version, or is for EU version also?
EDIT:
Last try was:
MSM - OnePlus_9_Pro_EU_OxygenOS_11.2.2.2
Then update to:
OnePlus 9 Oxygen OS 11.2.10.10.LE25BA (EU)
- OnePlus9Oxygen_22.E.13_OTA_0130_all_2111112104_f4acbf.zip
Then, two options:
Oxygen updater -> C.47 ->Touchscreen death
OTA update -> OxygenOS 12.0 (C.48) (EU)
- OnePlus9Oxygen_22.E.11_OTA_0110_all_2107082125_downgrade_09b1a0a810824761.zip ->Touchscreen death
Im starting to be little bit despered, where is the problem. I've tried lost of combination but still no luck...

AtreyC said:
Thank you for your reply, the link you've send is downloading:
OnePlus9Oxygen_22.E.13_OTA_0130_all_2111112104_f4acbf.zip
I've presume that is for Global version, or is for EU version also?
EDIT:
Last try was:
MSM - OnePlus_9_Pro_EU_OxygenOS_11.2.2.2
Then update to:
OnePlus 9 Oxygen OS 11.2.10.10.LE25BA (EU)
- OnePlus9Oxygen_22.E.13_OTA_0130_all_2111112104_f4acbf.zip
Then, two options:
Oxygen updater -> C.47 ->Touchscreen death
OTA update -> OxygenOS 12.0 (C.48) (EU)
- OnePlus9Oxygen_22.E.11_OTA_0110_all_2107082125_downgrade_09b1a0a810824761.zip ->Touchscreen death
Im starting to be little bit despered, where is the problem. I've tried lost of combination but still no luck...
Click to expand...
Click to collapse
The same thing happened to me 2 days before and the conclusion was to use stock Android 11 or any custom ROM.

AtreyC said:
Thank you for your reply, the link you've send is downloading:
OnePlus9Oxygen_22.E.13_OTA_0130_all_2111112104_f4acbf.zip
I've presume that is for Global version, or is for EU version also?
EDIT:
Last try was:
MSM - OnePlus_9_Pro_EU_OxygenOS_11.2.2.2
Then update to:
OnePlus 9 Oxygen OS 11.2.10.10.LE25BA (EU)
- OnePlus9Oxygen_22.E.13_OTA_0130_all_2111112104_f4acbf.zip
Then, two options:
Oxygen updater -> C.47 ->Touchscreen death
OTA update -> OxygenOS 12.0 (C.48) (EU)
- OnePlus9Oxygen_22.E.11_OTA_0110_all_2107082125_downgrade_09b1a0a810824761.zip ->Touchscreen death
Im starting to be little bit despered, where is the problem. I've tried lost of combination but still no luck...
Click to expand...
Click to collapse
The link I sent you is the full stock EU image.

AtreyC said:
I'm looking for a captain who could help me find solution. Like "EtherealRemnant" in his post, Im not able to get OOS 12 work on my OP9.
EtherealRemnant post:
https://forum.xda-developers.com/t/...p9-stock-oos-11-2-2-2aa.4275727/post-86854951
Like "everyone" I've something messed up with TWRP boot and ended up with MSM tool. Cause I have LE2113 I have to use India MSM for 9Pro.
Then I use downgrade package to get stock OOS on my OP9, then use oficial way to update OOS, till highest A11. But whenever I use update to LE2113_11.C.47 it ended up with frozen/not working touch screen. Not just in OS but also in TWRP and stock recovery. I´ve tried also connect USB mouse, but with no successs.
My question, is there a way how to update to OOS (A12) without get freezed touchscreen?
Click to expand...
Click to collapse
Did you unlock the bootloader before you upgraded, the frozen non working touchscreen only happened when I upgraded with an unlocked bootloader. If you havent already try to MSM back to stock and then upgrade to OOS12 before you unlock the bootloader

jshinn1 said:
Did you unlock the bootloader before you upgraded, the frozen non working touchscreen only happened when I upgraded with an unlocked bootloader. If you havent already try to MSM back to stock and then upgrade to OOS12 before you unlock the bootloader
Click to expand...
Click to collapse
The broken touchscreen happened to me with a locked bootloader too. I know this because I was on 11.2.10.10 after spending hours figuring out how to get it back on full global firmware and I made the conscious decision not to mess with a custom ROM anymore after updating to 11.2.10.10 before I chose to use the OTA to upgrade to C.48 so I didn't unlock the bootloader. Then I ended up having to do the MSM again when my touchscreen didn't work.

EtherealRemnant said:
The broken touchscreen happened to me with a locked bootloader too. I know this because I was on 11.2.10.10 after spending hours figuring out how to get it back on full global firmware and I made the conscious decision not to mess with a custom ROM anymore after updating to 11.2.10.10 before I chose to use the OTA to upgrade to C.48 so I didn't unlock the bootloader. Then I ended up having to do the MSM again when my touchscreen didn't work.
Click to expand...
Click to collapse
Hmmm Im definitely no expert but if that doesn't work then hopefully somebody else can chime in with a solution.

jshinn1 said:
Hmmm Im definitely no expert but if that doesn't work then hopefully somebody else can chime in with a solution.
Click to expand...
Click to collapse
The only thing that worked for me was getting back to the stock global firmware with the MSM Tool. I modded the MSM Tool to do this since I was stuck on the India 9 Pro software and it worked for whatever reason but I had someone else try it and it didn't work for them and asking someone who knows about the MSM Tool, my fix shouldn't have worked for me either, so I took it down so as not to mislead anyone. As you can see though, OOS 12 is running fine.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

@jshinn1 When I install MSM for OP9pro on my OP9, I've unlock bootloader to install downgrade for OP9 via TWRP. Then I try to update via OTAs, downloaded from Oxygen updater, or xda sources. Result is still same, death touch after install Android 12 update.
I've also tried swaping slots (A,B) in TWRP during install, no result.
So far only MSM capable unbrick my OP9 was Indian 9Pro and EU 9Pro. But in the end same result death touch.

I was able to fix it by modifying the settings.xml in the T-Mobile msm, I haven't had anyone else try but it's worked multiple times on my own. I can provide the link if anyone is interested. It's for the OP9 T-Mobile but I can easily change it to global if needed.

Sound promising, can you change it not to Global, but to EU (2113)?

Okay I will try it on my device and if all looks good report back with a download link.

XxBigBuckxX said:
I was able to fix it by modifying the settings.xml in the T-Mobile msm, I haven't had anyone else try but it's worked multiple times on my own. I can provide the link if anyone is interested. It's for the OP9 T-Mobile but I can easily change it to global if needed.
Click to expand...
Click to collapse
Can I ask how you did this? I modified the settings.xml on the global ROM to IN and it flashed mine that was stuck as an Indian 9 Pro but then failed params when I gave it to someone else and I haven't wanted to risk being stuck on IN firmware again to troubleshoot it. In my case all I did was change the Desc from O2 to IN and that did it but I gave it to someone with a T-Mobile device also flashed with Indian 9 Pro software and it didn't work... Figured it must be a fluke that it worked for me.

Problem SOLVED, see my edit in first post. Thank you all for participation.

AtreyC said:
Problem SOLVED, see my edit in first post. Thank you all for participation.
Click to expand...
Click to collapse
Glad you figured it out

Question Poco X3 Pro stuck on MIUI 12.5 and can't update

Hi all,
i've just bought a Poco X3 Pro from Amazon and i was playing with it in order to decide if i'll keep it or not. The first thing that i wanted to do, was to update to the MIUI 13 to check if it was slower on that software, but the phone doesn't see any update and it is stuck at MIUI 12.5 (Global 12.5.5.0 RJUEUXM which seems to be the EEA/EU version). I've tried to search for update, i've tried to change the region, to enable "Receive updates before" but nothing changed.
I've tried also to download the update to use the "Choose package" option but it doesn't accept anything that i give to him. This is a first for me.
Is there anything else that i can try to do instead of unlocking the bootloader to use miflash? Just because i don't want to wait the 168 hourse of the process.
Thanks in advance!

nope, for me you need to unlock the bootloader to install any custom roms miui/aosp that's the only way i think.

Z4buz4 said:
Hi all,
i've just bought a Poco X3 Pro from Amazon and i was playing with it in order to decide if i'll keep it or not. The first thing that i wanted to do, was to update to the MIUI 13 to check if it was slower on that software, but the phone doesn't see any update and it is stuck at MIUI 12.5 (Global 12.5.5.0 RJUEUXM which seems to be the EEA/EU version). I've tried to search for update, i've tried to change the region, to enable "Receive updates before" but nothing changed.
I've tried also to download the update to use the "Choose package" option but it doesn't accept anything that i give to him. This is a first for me.
Is there anything else that i can try to do instead of unlocking the bootloader to use miflash? Just because i don't want to wait the 168 hourse of the process.
Thanks in advance!
Click to expand...
Click to collapse
Try to use XiaoMiTool V2, it should update your phone to latest stock rom without needing to unlock bootloader.

The 13.0.2 (stable beta) EEA Rom was pulled as far as I know, but the predecessor 13.0.1 has never been available via OTA since then. It will probably only be possible again with the next update to bring a 12.5.5 EEA device to MIUI 13 via OTA.

thorin0815 said:
The 13.0.2 (stable beta) EEA Rom was pulled as far as I know, but the predecessor 13.0.1 has never been available via OTA since then. It will probably only be possible again with the next update to bring a 12.5.5 EEA device to MIUI 13 via OTA.
Click to expand...
Click to collapse
So what i am experiencing should be normal because i've got the EEA version?
Popletenec said:
Try to use XiaoMiTool V2, it should update your phone to latest stock rom without needing to unlock bootloader.
Click to expand...
Click to collapse
Never used it before, i'll search for it. Thanks!

At least I've read of some cases in a German forum, so I assume that's why it's not updated for you either.

I have the same problem. Got an X3 Pro off Ebay. Came with a Euro charger in the box but ROM shows as MIUI 12.5.5.0 Global version in the settings section on the phone.
Tried to use XiaoMiTool v2 but that detects the ROM as EEA.
So I am stuck not knowing what to do.
I want to stay bootloader locked, for now any way, so I am really frustrated.

gandalf_grey91 said:
I have the same problem. Got an X3 Pro off Ebay. Came with a Euro charger in the box but ROM shows as MIUI 12.5.5.0 Global version in the settings section on the phone.
Tried to use XiaoMiTool v2 but that detects the ROM as EEA.
So I am stuck not knowing what to do.
I want to stay bootloader locked, for now any way, so I am really frustrated.
Click to expand...
Click to collapse
EEA/EU versions are also Global ones, but with EU law restrictions and they are named Global as well. Check the underlined part in your phone, does it have EU in it as well?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

I've tried with XiaoMiTools v2. It sees as the last possible update for the EEA the 12.5.5.0 update and it's unable to install the MIUI 13 EEA that i've previously downloaded. It doesn't neither allow me to install the global one, asking for the unlock of the bootloader which i'm still waiting.

There are two types of update files. One for the recovery, the other for fastboot. Are you sure you downloaded the right one for the Xiaomi tools?
Here you can download both types for 13.0.1:
https://xiaomifirmwareupdater.com/archive/miui/vayu/
For 13.0.2 I only saw the update for the recovery, but I've only scanned it for some seconds.

thorin0815 said:
EEA/EU versions are also Global ones, but with EU law restrictions and they are named Global as well. Check the underlined part in your phone, does it have EU in it as well?
View attachment 5661291
Click to expand...
Click to collapse
Yep, shows RJUEUXM.
BTW, what sort of EU law restrictions are we talking about?

The restrictions refer to Poco/Xiaomi and not to us users. User privacy is protected by EU laws. Well, at least in theory. ;-)

LOL
Many thanks for explaining.
Sounds good, in theory.

thorin0815 said:
There are two types of update files. One for the recovery, the other for fastboot. Are you sure you downloaded the right one for the Xiaomi tools?
Here you can download both types for 13.0.1:
https://xiaomifirmwareupdater.com/archive/miui/vayu/
For 13.0.2 I only saw the update for the recovery, but I've only scanned it for some seconds.
Click to expand...
Click to collapse
You're right, i'm an idiot :'D I've tried to use the recovery one with XiaomiMiTools. I'll try with the fastboot one and i'll update you about if it works.
Thanks!

Am in the UK and have received the 13.0.1 update via OTA about a week ago.

Hmm, have the same problem with my Poco X3 Pro. Bought it as new back then and updated MIUI whenever possible. Now I am stuck at 12.5.5.0 global and cannot update. Even downloading the latest update again (like suggested by Xiaomi support) does not work - it downloads but just doesn't install.
If I try to install that download manually with stock Updater app it says that the downloaded update (which was downloaded by that app itself BTW) cannot be veryfied. So I am completely locked to 12.5.5.0 it seems.
Since I do not want to root the phone nor apply a custom recovery or so - is there any other possibility to finally update to latest MIUI?

You all can't wait to flash even buggier MIUI 13, because... why?! Does Poco give out rewards for having the latest build? For what reason do you NEED it so much?

Personally I'd like to stay uptodate, especially for Android and Security Patches. Being stuck at 12.5.5.0 left me with Android 11 (at least this was shown) and very old security patches. If there es an easy and convenient way to get those updates in w/o hazzling around with root, custom recovery, several tools and PC - I am in, just point me to it.
I finally managed to update. After my 12.5.5.0 was unable to update itself with the last version it downloaded itself (which for me was a clear bug and hence another reason to move on) I downloaded latest official global stable MIUI13 for Poco X3 Pro and installed it with the system updater app. Worked flawlessly.

I have the same problem, but with MIUI 13.0.1.0, clearly there are several new updates for EEA after it, but it doesnt see any OTA, a manual download just installs the same version, and any new official stabel non beta packages it outrigth refuses to install in the manual updater u can unlock in the upodater app.
Oddly for the official stable versions i got off the update tracker from this forum, clearly labelled as non beta, the updater errors tellign me its a version for beta testers so i cannot install it.

Hi all i tried the same since morning and did not want to lose all my business or mobile banking apps ...
The easiest way to upgrade my MIUI was to switch Region from Germany to UK.
I imediatley got the OTA Option for MIUI 13. Maybe later will try to switch to India
So no need for FASTBOOT or wiping your data!

How To Guide [ TB-Q706F ] Pad Pro 12.6 Bypass Lenovo's region lock. ROW <==> ZUI easy

If you replaced the ZUI with the global and you see a black screen on startup with a warning about the incompatibility of software and hardware - that's your case
Look my video:
It also will works the other way around, except that the ZUI firmware is not yet in the public access.
Hex-editor HxD: https://mh-nexus.de/en/downloads.php?product=HxD20
QPST (QFil inside) : https://qpsttool.com/qpst-tool-v2-7-496

Contents of file frpinfo.bin:
Spoiler: Look:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
1. Country code
2. Serial number
3. Model name
4. OS fingerprint
5. Hardware components. For example, 8SSP69A6P it is: https://www.ebay.com/itm/255389221369
Region lock code:
02 for Chinese ZUI.
01 for Rest Of World (ROW)
You need to change only code, no more.
Good luck.

Great OTA? widevine L1? Anyone else tried this?

OTA working, Widevine L1 not tested, must be working.
Two my forum-mates already switched from ZUI to Global (me too).
When ZUI firmware will be in public access, we will able switch from ROW to ZUI.

May you have fpinfo.bin for stock TB-J716F?

No, I haven't. You can try to fix your own fpinfo.
Or you can compare 2 fpinfo.bin - from ZUI and from ROW and try to find this bite

f1tm0t said:
No, I haven't. You can try to fix your own fpinfo.
Or you can compare 2 fpinfo.bin - from ZUI and from ROW and try to find this bite
Click to expand...
Click to collapse
thien.nm2905 said:
May you have fpinfo.bin for stock TB-J716F?
Click to expand...
Click to collapse
I have J716F and erased all data using QFIL, my mistake. I tried fix my fpinfo.bin partition and match with stock j706f. Still cannot fix the widevine L1. I managed to restore serial number only by fixing the fpinfo.bin.
I have a good news, I was able to fix rotation for GSI on J716F, auto rotation, brightness and etc. Still cannot spoof the widevine. I am using Crdroid 8.6 android 12.

Nice work. Any chance you could check widevine via an app?
ZUI hasn't had an update in ages!

gunalarix8 said:
I have J716F and erased all data using QFIL, my mistake. I tried fix my fpinfo.bin partition and match with stock j706f. Still cannot fix the widevine L1. I managed to restore serial number only by fixing the fpinfo.bin.
I have a good news, I was able to fix rotation for GSI on J716F, auto rotation, brightness and etc. Still cannot spoof the widevine. I am using Crdroid 8.6 android 12.
Click to expand...
Click to collapse
How is this running, is it stable, any issues? I wouldn't mind trying another ROM and don't need winevine.
EDIT
Just noticed that you have fixed the rotation & brightness issues on GSI ROMs, would you mind posting the fix (or a link). Thx

Anyone else tried this yet?

So what is the procedure, first flash ROW to get black screen and message and then change region? Or first change region and then flash ROW?

hello i am a little confused, can he make my pro 12.6Can I change to an international system, I would like to try it if I can.

Mondaywalk said:
Great OTA? widevine L1? Anyone else tried this?
Click to expand...
Click to collapse
I used this method after soft bricking my P12 pro after latest Row OTA update (thanks Lenovo). After updating my frpinfo file, now i'm using latest Row version wihout any issues, DRM info shows Widevine L1 but didn't tested yet since i'm still reconfiguring my tablet, i'll update this later. I can't say anything about OTAs since i'm on latest version.
EDIT: i wrote more details about what i did here: https://forum.xda-developers.com/t/xiaoxin-pad-pro-12-6-tb-q706f-questions.4418463/post-87697465
EDIT 2: just checked, Widevine L1 on Netflix app (althought i'm feeling like the image is a bit grainy, not just on netflix, but on all streaming apps, maybe a android 12 issue!?).
Keep in mind i've used Lenovo's RSA Row Rom Image.

erzketis said:
So what is the procedure, first flash ROW to get black screen and message and then change region? Or first change region and then flash ROW?
Click to expand...
Click to collapse
After changing the region code to 01 (ROW), I downloaded the ROM using Lenovo Rescue and Smart Assistant (LMSA) and flashed it using QFIL. Now I'm on the global version based on android 12L instead of ZUI.

nourtirga said:
After changing the region code to 01 (ROW), I downloaded the ROM using Lenovo Rescue and Smart Assistant (LMSA) and flashed it using QFIL. Now I'm on the global version based on android 12L instead of ZUI.
Click to expand...
Click to collapse
Looks like either way is fine, since i flashed first then changed the code.

Hexcz said:
Looks like either way is fine, since i flashed first then changed the code.
Click to expand...
Click to collapse
But does that mean the tablet now is not a chinese version anymore and it will receive and install Global OTA without any issues?!

nourtirga said:
But does that mean the tablet now is not a chinese version anymore and it will receive and install Global OTA without any issues?!
Click to expand...
Click to collapse
Technically yes, but you'll know you purchased the chinese version xD. And yes, after doing that you can flash the global rom, but i can't assure about OTAs since i'm on latest one and didn't received any OTAs yet, but i guess it will receive OTAs without any issues.

Hexcz said:
Technically yes, but you'll know you purchased the chinese version xD. And yes, after doing that you can flash the global rom, but i can't assure about OTAs since i'm on latest one and didn't received any OTAs yet, but i guess it will receive OTAs without any issues.
Click to expand...
Click to collapse
Even if it didn't receive any OTA updates, I am okay with being able to flash the global ROM using QFIL. Once a new version is release I will flash it manually.
But I don't see any difference now with the global version since we flashed the original firmware without any modifications.
I hope I'm not wrong.

nourtirga said:
Even if it didn't receive any OTA updates, I am okay with being able to flash the global ROM using QFIL. Once a new version is release I will flash it manually.
But I don't see any difference now with the global version since we flashed the original firmware without any modifications.
I hope I'm not wrong.
Click to expand...
Click to collapse
You can use Lenovo's Rescue Smart Assistant to flash the latest global rom. I'd suggest to use Qfil only to check the region code.

Hexcz said:
You can use Lenovo's Rescue Smart Assistant to flash the latest global rom. I'd suggest to use Qfil only to check the region code.
Click to expand...
Click to collapse
I already flashed the ROW version. I'm just asking for the upcoming updates. should I consider it now like Tab P12 Pro or there is still something that might cause not receiving & installing OTA updates.

Official AOSP for Huawei (stanford) - LeaOS-PHH (android 13 version)

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
​LeaOS is a project which based on AOSP with trebledroid patches.
This build includes settings parameters for Huawei STF as well as several evolutions:
Offline charging
AGPS Supl20
SafetyNet
GCam for kirin
Installation
Download system file : "LeaOS-A13-20230224-iceows-stf.img.xz" (without google apps) or "LeaOS-A13-20230224-iceows-google-stf.img.xz" (google apps version)
Extract img file
Flash system image : fastboot flash system <drag system.img here>
Boot into recovery: power + vol+ while NOT connected to pc
Factory reset
Reboot to System and setup with android assistant
Enjoy !!!
Source Code:
https://github.com/Iceows
ROM OS Version: Android 13.0
ROM Kernel: Stock kernel
ROM Firmware Required: EMUI 9.1
Based On: Google AOSP + TrebleDroid patches
Support Group
Channel update

reserved

drm/widevine.zip patches for ab is not needed to flash?

I didn't have time to look if it was necessary. The patch is only needed if the version of emui9 you are using has a preavs partition. You can see it if you capture a logcat log with adb. If so I would make a drm patch with the correct version of the drm files for stf-l09

I have finally had the chance to fully implement it, and I'm here to give you the feedback!
Generally speaking, it can be considered a stable build and can be used on your main device. However, there's always room for improvement and the following areas should be revised:
1- The included "Android System WebView" is too old to work, rendering synchronizing with Google accounts impossible. The workaround is easy, however, as the updated versions can be downloaded from the Play store. The same applies to: "Phone", "Contacts", "Messaging" and "Browser" apps.
2- The "Search" box in the Home screen is impossible to remove.
3- The "Navigation bar inverse" option in "Phh Treble Settings -> Misc features" doesn't work, even after re-selecting navbar mode, as specified.
4- The "Adaptive Brightness" option results in more brightness than needed, where it has to be manually lowered. The cause might be related to incorrect readings from the phone's sensors, on the software side.
5- Not a problem, but rather a suggestion: More customizations in general, and in the "Status bar" specifically, can make the ROM more appealing.
Additionally, the instructions above for flashing the ROM are good enough, but it's worth adding that the bootloader of the target phone has to be unlocked first The instructions to achieve that are likely included in the "Honor 9 Guides, News, & Discussion" forum.
Keep up the great work

Barrytoo said:
I have finally had the chance to fully implement it, and I'm here to give you the feedback!
Generally speaking, it can be considered a stable build and can be used on your main device. However, there's always room for improvement and the following areas should be revised:
1- The included "Android System WebView" is too old to work, rendering synchronizing with Google accounts impossible. The workaround is easy, however, as the updated versions can be downloaded from the Play store. The same applies to: "Phone", "Contacts", "Messaging" and "Browser" apps.
2- The "Search" box in the Home screen is impossible to remove.
3- The "Navigation bar inverse" option in "Phh Treble Settings -> Misc features" doesn't work, even after re-selecting navbar mode, as specified.
4- The "Adaptive Brightness" option results in more brightness than needed, where it has to be manually lowered. The cause might be related to incorrect readings from the phone's sensors, on the software side.
5- Not a problem, but rather a suggestion: More customizations in general, and in the "Status bar" specifically, can make the ROM more appealing.
Additionally, the instructions above for flashing the ROM are good enough, but it's worth adding that the bootloader of the target phone has to be unlocked first The instructions to achieve that are likely included in the "Honor 9 Guides, News, & Discussion" forum.
Keep up the great work
Click to expand...
Click to collapse
[UPDATED GUIDE] [BOOTLOADER UNLOCK] Huawei p8 lite 2017 (pra-lx1)
This guide is the only one made and tested personally by me, I am not responsible for malfunctions or any damage to the device, carefully read every single step and everything will be successful [ATTENTION]: Before proceeding, save all your...
forum.xda-developers.com
This guide worked for me on the huawei p8 lite 2017, and i was looking around because i also have a honor 9, and dc unlocker have support for honor 9 apparently.
I'll be trying the same method of the p8 guide on honor 9 to see if it works. If i remember i'll comeback to give feedback on this

Barrytoo said:
I have finally had the chance to fully implement it, and I'm here to give you the feedback!
Generally speaking, it can be considered a stable build and can be used on your main device. However, there's always room for improvement and the following areas should be revised:
1- The included "Android System WebView" is too old to work, rendering synchronizing with Google accounts impossible. The workaround is easy, however, as the updated versions can be downloaded from the Play store. The same applies to: "Phone", "Contacts", "Messaging" and "Browser" apps.
2- The "Search" box in the Home screen is impossible to remove.
3- The "Navigation bar inverse" option in "Phh Treble Settings -> Misc features" doesn't work, even after re-selecting navbar mode, as specified.
4- The "Adaptive Brightness" option results in more brightness than needed, where it has to be manually lowered. The cause might be related to incorrect readings from the phone's sensors, on the software side.
5- Not a problem, but rather a suggestion: More customizations in general, and in the "Status bar" specifically, can make the ROM more appealing.
Additionally, the instructions above for flashing the ROM are good enough, but it's worth adding that the bootloader of the target phone has to be unlocked first The instructions to achieve that are likely included in the "Honor 9 Guides, News, & Discussion" forum.
Keep up the great work
Click to expand...
Click to collapse
For customisation and remove search bar, just change the launcher

AltairFR said:
For customisation and remove search bar, just change the launcher
Click to expand...
Click to collapse
Yep, that's what I did.
However, the small downside to that is the extra memory usage. Besides that, no launcher really bests the baked-in one in smoothness, but again, that's minor.

neves2k said:
[UPDATED GUIDE] [BOOTLOADER UNLOCK] Huawei p8 lite 2017 (pra-lx1)
This guide is the only one made and tested personally by me, I am not responsible for malfunctions or any damage to the device, carefully read every single step and everything will be successful [ATTENTION]: Before proceeding, save all your...
forum.xda-developers.com
This guide worked for me on the huawei p8 lite 2017, and i was looking around because i also have a honor 9, and dc unlocker have support for honor 9 apparently.
I'll be trying the same method of the p8 guide on honor 9 to see if it works. If i remember i'll comeback to give feedback on this
Click to expand...
Click to collapse
Sadly I still didn't managed to do it... I can't downgrade from android 9 to 8 :/ In the past i had that option, but now it's just gone...
I tried dload method with SDCard, but it fails every time. I guess that dload method only works to upgrade and not to downgrade?
If you have some tips to help me downgrade it let me know please

Hello AltairFR,
I've got a Honor 9 in quite good state, and I wanted to upgrade it to most current version before using it (I'm no real geek, set up and then "never touch a running system" is rather me).
I started with unlocking bootloader with DC-unlocker, successfully.
I installed and used adb and fastboot utils.
Then I attempted to install TWRP according to this manual https://romprovider.com/honor-9-dev-support/
As far as I understand, the trick consists of two parts, 1) proper version of TWRP (not easy to find one for Honor 9!), and 2) patched kernel to avoid restore of stock recovery, so TWRP persists.
Unfortunately I failed. After I performed all the steps, the phone got to a bootloop (booted, restarted, booted, restarted, ...)
That version of TWRP never started, it just showed the logo and hung. Patched kernel was no success either because
stock recovery is back. The only way I can resurrect TWRP is to perform factory reset in stock recovery. Then next start is TWRP, and afterwards again just bootloop and stock recovery.
Then I found and installed a working version of TWRP here https://forum.xda-developers.com/t/twrp-ish-twrp-3-2-1-for-honor-9-running-gsi-8-1-roms.3818442/
Then I attempted Android 10 according to https://theupgradeguide.com/install-android-10-on-honor-9-aosp-gsi-treble-rom-how-to-guide/
This was most successful attempt so far, except it was only installed w/o GApps and Antroid reported "There is an internal problem in your device. Please contact your manufacturer." <- not really useable.
Then I tried your Android 13 build. I installed it the way you recommend (fastboot). I got "Invalid sparse file format at header magi" and something about "device reported max upload size of" about 400MB. Nevertheless, it completed kind of successfully. But this Android never started up. It's starting and then reboots. Both with GApps and without.
I assumed the reason could be that patched Kernel I installed at the beginning. I inspected my versions with "Multi-Tool for Huawei and Honor" and found Firmware version = STF-L09 8.0.0.368(C432) Your prerequisites are
ROM Kernel: Stock kernel​ROM Firmware Required: EMUI 9.1​My EMUI is not reported by "Multi-Tool" at all, although in the video guide it's shown. (Perhaps because I don't have any EMUI at all anymore. As far as I understood, it's a Huawei version of "look-and-feel" on Android).
So now my question, how did you manage to get EMUI 9.1 ?
I searched for stock firmware to restore my phone to at least original state. I found https://huaweistockrom.com/honor-9-stf-l09 which refers to EMUI 9.1 in file name Huawei_Honor_9_STF-L09_9.1.0.210_C43 ... .0.0_R3_EMUI9.1.0_05014NMA_Dload.zip
But the free download site is not available, and it's a bit risky to go for paid one without knowing the archive file contains what it sais.
Hence my question, how did you manage to get your EMUI 9.1 ? My pretty much last hope is, if I get to that version of stock software then your Android 13 build hopefully installs successfully too.
Thank you in advance.

Hello. I think you've complicated yourself. The procedure is much simpler, you just need to flash the right twrp and then install LeaOS. I look on my stf the version of emui that I have. I will answer you later

k0a1a said:
Hello AltairFR,
I've got a Honor 9 in quite good state, and I wanted to upgrade it to most current version before using it (I'm no real geek, set up and then "never touch a running system" is rather me).
I started with unlocking bootloader with DC-unlocker, successfully.
I installed and used adb and fastboot utils.
Then I attempted to install TWRP according to this manual https://romprovider.com/honor-9-dev-support/
As far as I understand, the trick consists of two parts, 1) proper version of TWRP (not easy to find one for Honor 9!), and 2) patched kernel to avoid restore of stock recovery, so TWRP persists.
Unfortunately I failed. After I performed all the steps, the phone got to a bootloop (booted, restarted, booted, restarted, ...)
That version of TWRP never started, it just showed the logo and hung. Patched kernel was no success either because
stock recovery is back. The only way I can resurrect TWRP is to perform factory reset in stock recovery. Then next start is TWRP, and afterwards again just bootloop and stock recovery.
Then I found and installed a working version of TWRP here https://forum.xda-developers.com/t/twrp-ish-twrp-3-2-1-for-honor-9-running-gsi-8-1-roms.3818442/
Then I attempted Android 10 according to https://theupgradeguide.com/install-android-10-on-honor-9-aosp-gsi-treble-rom-how-to-guide/
This was most successful attempt so far, except it was only installed w/o GApps and Antroid reported "There is an internal problem in your device. Please contact your manufacturer." <- not really useable.
Then I tried your Android 13 build. I installed it the way you recommend (fastboot). I got "Invalid sparse file format at header magi" and something about "device reported max upload size of" about 400MB. Nevertheless, it completed kind of successfully. But this Android never started up. It's starting and then reboots. Both with GApps and without.
I assumed the reason could be that patched Kernel I installed at the beginning. I inspected my versions with "Multi-Tool for Huawei and Honor" and found Firmware version = STF-L09 8.0.0.368(C432) Your prerequisites are
ROM Kernel: Stock kernel​ROM Firmware Required: EMUI 9.1​My EMUI is not reported by "Multi-Tool" at all, although in the video guide it's shown. (Perhaps because I don't have any EMUI at all anymore. As far as I understood, it's a Huawei version of "look-and-feel" on Android).
So now my question, how did you manage to get EMUI 9.1 ?
I searched for stock firmware to restore my phone to at least original state. I found https://huaweistockrom.com/honor-9-stf-l09 which refers to EMUI 9.1 in file name Huawei_Honor_9_STF-L09_9.1.0.210_C43 ... .0.0_R3_EMUI9.1.0_05014NMA_Dload.zip
But the free download site is not available, and it's a bit risky to go for paid one without knowing the archive file contains what it sais.
Hence my question, how did you manage to get your EMUI 9.1 ? My pretty much last hope is, if I get to that version of stock software then your Android 13 build hopefully installs successfully too.
Thank you in advance.
Click to expand...
Click to collapse
Can you give me an explanation of how did you managed to unlock the bootloader of our honor 9 please?
For the stock ROM you can find it here for free https://androidhost.ru/

neves2k said:
Can you give me an explanation of how did you managed to unlock the bootloader of our honor 9 please?
Click to expand...
Click to collapse
Here is the way https://romprovider.com/unlock-bootloader-huawei/
I paid 4.31 EUR (4 credits).
> For the stock ROM you can find it here for free https://androidhost.ru/
Thank you, I found the site in the meantime. The latest version there is C432B130 while mine is B368. (Is it the reason why patched Kernel B366 silently failed to install?..)

k0a1a said:
Here is the way https://romprovider.com/unlock-bootloader-huawei/
I paid 4.31 EUR (4 credits).
> For the stock ROM you can find it here for free https://androidhost.ru/
Thank you, I found the site in the meantime. The latest version there is C432B130 while mine is B368. (Is it the reason why patched Kernel B366 silently failed to install?..)
Click to expand...
Click to collapse
For TWRP I will use this twrp :
altairfr-huawei - Browse /TWRP-Recovery at SourceForge.net
sourceforge.net
For stock ROM download a old EMUI 9.1 ROM and update it with hisuite or stock system huawei OTA. Don't flash kernel

AltairFR said:
For TWRP I will use this twrp
Click to expand...
Click to collapse
It worked, thank you.
> For stock ROM download a old EMUI 9.1 ROM and update it with hisuite or stock system huawei OTA. Don't flash kernel
I'm too far away from HiSuite yet.
I managed to start installation of stock firmware from SD card. "Installing EMUI" after 5% progress breaks with "Software install failed, reboot system now" :-/
In TWRP file manager I see a couple of directories were created on SD card [perhaps by installation routine, who else] with "android" in their names, and a couple of files. Just a couple of, not more.

k0a1a said:
It worked, thank you.
> For stock ROM download a old EMUI 9.1 ROM and update it with hisuite or stock system huawei OTA. Don't flash kernel
I'm too far away from HiSuite yet.
I managed to start installation of stock firmware from SD card. "Installing EMUI" after 5% progress breaks with "Software install failed, reboot system now" :-/
Click to expand...
Click to collapse
Do you have tried sevice repair firmware for stf-l09 ?.
You have a post here
Firmware Huawei Honor 9 STF-L09 - Stock service full rom
Update Instructions: Normal update dload/update.app [Main firmware file] Copy required vendor pack Example : [/dload/venrod/update_****_hw_eu.app] after rename the file in update.app Update dload/update.app [Required vendor file] Manually reset...
forum.xda-developers.com

AltairFR said:
Do you have tried sevice repair firmware for stf-l09 ?.
Click to expand...
Click to collapse
Yes I downloaded this one, a .rar achive with dload directory inside:
Service repair firmware [ Скачать / Download ]​File: STF-L09 C432B130 Belgium Germany France Netherlands Portugal Switzerland Spain Italy Austria Bosnia and Herzegovina Poland Denmark Finland Czech Lithuania Romania Serbia Slovenia Hungary Android 7.0 EMUI 5.1​Model: STF-L09​Build Number: C432B130​Vendor: [ hw/eu ]​Country: [ Belgium Germany France Netherlands Portugal Switzerland Spain Italy Austria Bosnia and Herzegovina Poland Denmark Finland Czech Lithuania Romania Serbia Slovenia Hungary ]​

Dis is nice. How bout RROS?

electronic_dream said:
Dis is nice. How bout RROS?
Click to expand...
Click to collapse
Btw have a question about device. I have bootloader unlocked years ago now, i had code but lost in a virus attack. Found that potato method that worked for honor 8. My question is if i flash those service firmwares to oreo or pie bootloader will relock? In 8 it did. Is there any way to flash oreo and pie roms without having to flash firmwares? If the only way is test point to get unlock code i'll do that when battery will die or smth like that.

electronic_dream said:
Btw have a question about device. I have bootloader unlocked years ago now, i had code but lost in a virus attack. Found that potato method that worked for honor 8. My question is if i flash those service firmwares to oreo or pie bootloader will relock? In 8 it did. Is there any way to flash oreo and pie roms without having to flash firmwares? If the only way is test point to get unlock code i'll do that when battery will die or smth like that.
Click to expand...
Click to collapse
And another. I've seen out there harmonyos firmware. That's only chinese? And after flashing that is possible go android again and have twrp etc.?