Database Info

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 Having issues after Converting OnePlus 9 5G LE2117 to Global

Hi everyome,
I have a OnePlus 9 5G LL2117. I have used the MSM Global tool about 3 weeks ago to convert it to GLobal (LE2115) Oxygen OS & ran Oxygen OS 12 fine w/ no issues.
I did a soft reset last night and when my phone restarted I saw it said it had No Sim/network detected and emerngecy calls only. I tried the MSM converstion tool again & it does restore the phone to OxygeOS 11 but the phone model is still LE2117. Even the softare updates say they are for LE2115.
What should I do?
See the attached phtoos below. I really would appreciate some help in this matter. The phone works fine for the moment.
{
"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"
}
Before, the device was just fine and it showed in the about section as LE2115.
Now after using the MSM tool : https://forum.xda-developers.com/t/...r-other-firmware.4277169/page-3#post-85143501
Now, when I go to software update it prompts me to install to something meant for LE2115. I already did install an Oxygen OS 11 update meant for LE2115 and I'm still able to use it on Verizon
If, I do install this update as I tried once before. I'm out of luck as the SIM is disabled and cell service will NOT WORK.
This was never an issue when the phone was originally converted to global 3 weeks ago & I even installed the C.61 update & worked fine on Verizon.
What do I do?
Thanks so much

You've completely converted. Of course your gonna get updates for the global unit. Not 100% sure maybe someone else can chime in but you need to back-pedal. Get back to where you were. I'd try using your correct version of msm tool. Not global version. Use T-Mobile

Yeah but then how come last time my model was showing as LE2115? and I was able to update to Android 12 fine?

luckychukiye said:
Yeah but then how come last time my model was showing as LE2115? and I was able to update to Android 12 fine?
Click to expand...
Click to collapse
You didn't update without issues so that's null and void.

Alright. What should I do? Keep it on this & try to update later? Oxygen OS updater does seem to detect the phone can be updated. .
Thanks for the confirmation of it being converted to Global

There shouldn't be any issues with your device running global firmware as the hardware is largely the same. You would be the first one I will have heard of that can't run global software. Are you saying that since your MSM you actually tried updating to C.61 and lost the radio again or are you just assuming that you will? I would go through the update process and if you lose the radio, factory reset, and see if it's just something that's happening with the update causing problems because there is no reason it should be breaking.

When I last did the MSM tool conversion 2 weeks ago it update to Oxygen OS 12 & I updated to C.61 right before I did that accidentally soft reset. It was working fine.
After I did the MSM tool conversation a day ago again and tried to update to C.64 I lost cell radio.
I just got this OnePlus 9 in December/January and even back then I had issues updating to Oxygen OS 12 but was told to wait by OnePlus themselves. What do you think?
As you said my phone is in global so it should run fine? Maybe wait and try again later? Should I do it via Software Update or Oxygen OS updater?

It makes no sense that you would lose radio updating to OOS12, I've never heard of anyone else losing it. There are lots of these T-Mobile converted to global devices out there because they were able to be gotten so cheaply from T-Mobile so if it was a real issue, it would be reported a lot more. Also, the update to C.61 is incremental right now, so you can also just choose to take C.48 and wait.

Yeah. For C.48 though. Should I update to it via Oxygen OS Updater from the Play Store or Software update? Right now it prompts me to do this i software update.
Also, updating to 12 one thing I didn't like is the notifications and extra bundles apps 11 d didn't have

Also, is it normal for my device to still say LE2117 on the about page?

Verizon/Visible on OxygenOS 12?
I installed the C.44 update hoping all of the "No Service" issues of the initial release would have been fixed, but I still could not connect to the Verizon network. After 2 hours of chatting with an online rep at Visible (Verizon's MVMO) she...
forum.xda-developers.com
Like this user

EtherealRemnant said:
It makes no sense that you would lose radio updating to OOS12, I've never heard of anyone else losing it. There are lots of these T-Mobile converted to global devices out there because they were able to be gotten so cheaply from T-Mobile so if it was a real issue, it would be reported a lot more. Also, the update to C.61 is incremental right now, so you can also just choose to take C.48 and wait.
Click to expand...
Click to collapse
Also, oddly when I did convert the phone back to the TMObile version before converting to Global. It had no signal or anything despite saying the phone is network unlocked. Why is this?

Quite frankly I am stumped as to what your issue could be. If you're having it on stock software too, it's likely hardware.

I had the same issue converting. I found that flashing this fixed it for me:
[TMO] OOS/COS DATA FIX
TO CLARIFY THIS IS A ROOT ONLY FIX After gaining root install given module. Data is now retained. Even after reboot(s). No empty slot or waiting. Issue is TMO variant is showing muli sim. So props were added to make it like a conversion to single...
forum.xda-developers.com
You would need to be rooted though, as this is a magisk module. Maybe if we can get a tweaked stock rom with the sysprop updated, we wouldnt need to root.

Thanks
How would I go about doing this from where I am now? since I'm on OS 11. What would I need to do to flash this?

I wonder why it worked fine before

Try this MSM. It's modded to flash full global 11.2.10.10 to T-Mobile variants. The modded MSM Tool you used seems to be leaving traces that make the phone think it's dual SIM in OOS12, same thing that happens with the India firmware on global units. I modded this one myself and it's untouched stock global 11.2.10.10 that was just modded to target TMO instead of O2.
3.57 GB file on MEGA
mega.nz
As global units aren't dual SIM either, full global firmware should not have the dual SIM bug. If this doesn't work, that module seems to be your only choice.

Also., what if I go the custom rom route?
Would I need to do anything with Magisk ? There are roms that have full Verizon support

luckychukiye said:
Also., what if I go the custom rom route?
Would I need to do anything with Magisk ? There are roms that have full Verizon support
Click to expand...
Click to collapse
Not in my experience, no. It's an OOS bug. I got it with Indian firmware and with ColorOS.

Yeah. Again this phone was working fine so I don't think I need to do any of that stuff. The phone is working right now as I'm typing this.
What rom are you using and on what network? V Verizon as well?
I even called OnePlus and they confirmed people were complaining about Verizon SIM not working on their OnePlus phoens and told me it was a software bug

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.

Untouched Poco F2 Pro (SJKEUXM) Unknown baseband after latest update (13.0.8.0 SJKEUXM)

Hello,
I dunno if this thread is still active but I have the EU variant Poco F2 Pro and this has been untouched since 2020(no I regret not unlocking the bootloader). And just last week, (I think) after receiving the latest patch update, I suddenly lost my baseband. Hence I now have no signal. I have raken my ohone to a technician for consultation and checkup and he was the one who noticed the "unknown baseband", Suffice to say my IMEI is also gone. He told me that rhe only way to solve this is to reflash OS. Unfortunately, my bootloader is still locked because I said this is still untouched (I regret it now).
So I did some research and came across this DFT Pro Tool for mobile maintenance which works on multiple brands and claims it can fix the IMEI/baseband issue even with bootloader locked. PROBLEM IS, you have to buy it for $70 and for something you'll gonna be using just once, that is a huge sum.
Now I have sent Fredback to Poco about this and requested for a rollback update (idk if they reply to such cases) just to see if the current update is the issue. I have also tried redownloading and reflashing the full latest firmware via the update menu but it did not solve anything.
The last thing on my mind is to reflash an older version (maybe 13.0.5.0, 4.0, or 3.0) via recovery but I know xiaomi and Poco implemented an anti rollback feature (which I now think is kinda selfish and stupid of them).
I also have this crazy idea of extracting the baseband zip from a previous version of the rom, renaming it 'update.zip" and flashing but I doubt that it's as simple as that.
Anyone encountered a similar issue?
{
"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"
}

ichigo_kurosaki said:
Hello,
I dunno if this thread is still active but I have the EU variant Poco F2 Pro and this has been untouched since 2020(no I regret not unlocking the bootloader). And just last week, (I think) after receiving the latest patch update, I suddenly lost my baseband. Hence I now have no signal. I have raken my ohone to a technician for consultation and checkup and he was the one who noticed the "unknown baseband", Suffice to say my IMEI is also gone. He told me that rhe only way to solve this is to reflash OS. Unfortunately, my bootloader is still locked because I said this is still untouched (I regret it now).
Click to expand...
Click to collapse
V13.0.8.0.SJKEUXM is a stable beta, and yes Xiaomi is updating with Beta versions on the stable channel and this is nothing new, many like you have found themselves with bricked phones.
At first tried with https://www.xiaomitool.com/V2/ if no result reposted.

Will it work even with locked bootloader? Thanks for the reply anyway.

ichigo_kurosaki said:
Will it work even with locked bootloader? Thanks for the reply anyway.
Click to expand...
Click to collapse
First try to reinstall the same version with the OTA.

NOSS8 said:
First try to reinstall the same version with the OTA.
Click to expand...
Click to collapse
Already did that. Tried the ota and the full rom (download full package).

ichigo_kurosaki said:
Already did that. Tried the ota and the full rom (download full package).
Click to expand...
Click to collapse
So;use https://www.xiaomitool.com/V2/,select bricked device.(Not 100% guaranteed that it will work)

NOSS8 said:
So;use https://www.xiaomitool.com/V2/,select bricked device.(Not 100% guaranteed that it will work)
Click to expand...
Click to collapse
Yes you are right. This method is not guaranteed. I tried to trick the tool into thinking my Poco F2 Pro was bricked. I got as far as to the firmware selwction for my device (there was IMI and IMI-new) but I thinkini represents redmi k30 pro because when i tried to proceed it was searching for china rom (when in fact I have F2 eu variant). Idk what imi new is. Maybe that is my device/global and eu f2. But when i tried to proceed i get this error i was lucky to cime uo upon doing google search.

Try with the same rom or update.
This tool is able to detect the rom.

NOSS8 said:
Try with the same rom or update.
This tool is able to detect the rom.
Click to expand...
Click to collapse
So i gotta use "my device is working" then "i want to mod ot" then select my rom file?

ichigo_kurosaki said:
So i gotta use "my device is working" then "i want to mod ot" then select my rom file?
Click to expand...
Click to collapse
try what is possible.

NOSS8 said:
try what is possible.
Click to expand...
Click to collapse
Almost succeeded. Lol. I went in to Mi Assistant in recovery so just to make the device appear in pcsuite mode. All was qell .a rom was found for my device. Almost done flashing then $hit happens and i was booted back (thankfully) to my current system.

NOSS8 said:
try what is possible.
Click to expand...
Click to collapse
Almost succeeded. Lol. I went in to Mi Assistant in recovery so just to make the device appear in pcsuite mode. All was qell .a rom was found for my device. Almost done flashing then $hit happens and i was booted back (thankfully) to my current

Hi, i have the global version (POCO F2 PRO) in the last month i had this problem. I dont know the reason, never did something whith software , only one day the phone freezen and when i do the reboot los this information. You have good news?? pd: sorry for my english no is my principal lenguage

Hello..
Please any solution yet? I also have Poco f2 pro global with same issue (bootloader is locked).. and currently the phone is not recognised by any pc(only charging) all settings are okay. The phone is not even reading USB otg flash storage again.

Question Can't update to MIUI 14

Hello. So I'm trying to update my phone from MIUI 13.0.4 to 14.0.1. I click on choose update package and then choose the zip file and this error appears: "Can't flash this stable ROM" Any idea on how to fix this?
{
"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 have no idea, but same issue on my wife's X3 Pro. Mine got 13 then 14 through OTA, hers was stuck on 12.5 saying no update. I managed to force 13, but still says no update, and same error message with 14 if I try to manually install it, so if you find the solution, i'm interested please!

Hello. So I've been trying for days to download MIUI 14 but it seems I have no luck. Tried clicking "Download latest package" and this error shows up: "Wait a minute or two and try again". Tried installing from "Choose update package", chose the EU package then "Can't flash this stable ROM", tried the global package and then "Couldn't verify update package. Update via USB instead". So my phone is stuck on 13.0.4.0? I was trying to avoid fastboot but it seems I'm doomed to use it. Anyone have any idea about this?

lidistat67 said:
Hello. So I'm trying to update my phone from MIUI 13.0.4 to 14.0.1. I click on choose update package and then choose the zip file and this error appears: "Can't flash this stable ROM" Any idea on how to fix this?
Click to expand...
Click to collapse
13.0.4 missing the following to know the version?

I have the same, but my EEA model does not want to update past 13.0.1, installing any newer MIUI 13 roms give me the error that its only for Beta testing ( eventhough they are labelled as stable releases not Beta) and the 14 gives the same error yours does.

-MB- said:
I have the same, but my EEA model does not want to update past 13.0.1, installing any newer MIUI 13 roms give me the error that its only for Beta testing ( eventhough they are labelled as stable releases not Beta) and the 14 gives the same error yours does.
Click to expand...
Click to collapse
POCO X3 Pro EEAStable BetaRecoveryV13.0.2.0.SJUEUXM12.03.3 GB2022-05-11
POCO X3 Pro EEAStableFastbootV13.0.3.0.SJUEUXM12.05.4 GB2022-07-09
Try to change region (Belgium for example) and reboot then activate Wifi and try to update or downloaded the rom and tried to update via the updater.(V13.0.3.0.SJUEUXM).

NOSS8 said:
POCO X3 Pro EEAStable BetaRecoveryV13.0.2.0.SJUEUXM12.03.3 GB2022-05-11
POCO X3 Pro EEAStableFastbootV13.0.3.0.SJUEUXM12.05.4 GB2022-07-09
Try to change region (Belgium for example) and reboot then activate Wifi and try to update or downloaded the rom and tried to update via the updater.(V13.0.3.0.SJUEUXM).
Click to expand...
Click to collapse
CHangign region didn't help. But for some reason i found an incremental update file for 13.0.3.0 that was smaller then the full rom, and it does seem to install now.

-MB- said:
CHangign region didn't help. But for some reason i found an incremental update file for 13.0.3.0 that was smaller then the full rom, and it does seem to install now.
Click to expand...
Click to collapse
All is here:
Xiaomi Firmware Updater
The ultimate script that provides firmware packages for Xiaomi devices.
xiaomifirmwareupdater.com

NOSS8 said:
All is here:
Xiaomi Firmware Updater
The ultimate script that provides firmware packages for Xiaomi devices.
xiaomifirmwareupdater.com
Click to expand...
Click to collapse
Yes, I got that incremental update from there. Seems its the only type the updater here accepts as install file. I am on 13.0.3.0 now. Tried the full roms of .4 and 6, and those still give the same error, so I guess if a firmware has no incremental update file on that site, I cant use it.,

-MB- said:
Yes, I got that incremental update from there. Seems its the only type the updater here accepts as install file. I am on 13.0.3.0 now. Tried the full roms of .4 and 6, and those still give the same error, so I guess if a firmware has no incremental update file on that site, I cant use it.,
Click to expand...
Click to collapse
The radical solution is to unlock the bootloader, flash the rom you want and relock the bootloader.
Or to use a Xiaomi EU rom.

Having a similar issue. I have the same version and I've downloaded the ZIP file to update to it, but I just receive an error saying invalid path. Any ideas on how to fix this?
Apparently moving it out of downloads seems to have fixed it lol, but I get a can't verify message. I have a feeling you could potentially get round this, since I noticed that even with an update package, it required network access. Perhaps it's phoning home in some way?

i find the answer,,eaa last framware version is 13.0.6.0
and we have stuck in 13.0.4.0
u must install miui downloader then download 13.0.6.0 stable and
isntall it
and miui 14 ota update comes for you,

metttti said:
i find the answer,,eaa last framware version is 13.0.6.0
and we have stuck in 13.0.4.0
u must install miui downloader then download 13.0.6.0 stable and
isntall it
and miui 14 ota update comes for you,
Click to expand...
Click to collapse
Yeah, I don't have that firmware installed
Don't know why it would be required just to update

i can confirm, advice from metttti works!thank you metttti, you are genius
I was stuck on 13.0.1., paradox- two same phones poco x3 pro, my phone easy on 14.0.2, wife phone stuck on 13.0.1. downloaded 13.0.6 with miui downloader, after reboot, immediately appear update for 14.0.2.

kody33 said:
i can confirm, advice from metttti works!thank you metttti, you are genius
I was stuck on 13.0.1., paradox- two same phones poco x3 pro, my phone easy on 14.0.2, wife phone stuck on 13.0.1. downloaded 13.0.6 with miui downloader, after reboot, immediately appear update for 14.0.2.
Click to expand...
Click to collapse
Forgot to reply that it worked for me too
not entirely satisfied with MIUI 14 though