Database Info

General [Download] P11(TB-J606) Android 11 Global ROM

Android 11 Global ROM
WIFI:
https://rsdsecure-cloud.motorola.com/download/TB-J606F_S320029_210923_ROW.zip
LTE:
https://rsdsecure-cloud.motorola.com/download/TB-J606L_S320030_210923_ROW.zip
{
"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"
}

@qwer1335 I've changed the prefix of your thread from "Development" to "General" as the thread didn't qualify for the first one. Please review the sticked guidances of the responsible moderators' team prior to your next posting and do not change the prefix back! Thanks for your cooperation.
Regards
Oswald Boelcke
Senior Moderator

Updated with LMSA with no issues, only be warned that everything is deleted and you start from scratch. I had my bootloader unlocked, this was kept. But I am unable to root it as I did with Android 10. Patching boot.img with Magisk and I get bootloop to fastboot after flashing it. Only way to continue as of now was to flash the boot.img that came with the new firmware.

Hallux_ said:
Updated with LMSA with no issues, only be warned that everything is deleted and you start from scratch. I had my bootloader unlocked, this was kept. But I am unable to root it as I did with Android 10. Patching boot.img with Magisk and I get bootloop to fastboot after flashing it. Only way to continue as of now was to flash the boot.img that came with the new firmware.
Click to expand...
Click to collapse
So may I ask if you bought your 606f from China or abroad?
Since mine is a Chinese one, everytime I flash 0805/0906 it ends with *system and hardware not compatible* error. (the same both BL locked and unlocked)
I wonder if this new ROW rom fixes this issue.
Thanks.

i tried but the link doesn't work
EDIT: i tried from rescue and smartaassistant, and i found the update

asukav said:
So may I ask if you bought your 606f from China or abroad?
Since mine is a Chinese one, everytime I flash 0805/0906 it ends with *system and hardware not compatible* error. (the same both BL locked and unlocked)
I wonder if this new ROW rom fixes this issue.
Thanks.
Click to expand...
Click to collapse
I have the global version.

Hallux_ said:
I have the global version.
Click to expand...
Click to collapse
Then that's not a problem.
Can you guide me how to unpack the img files? I tried several but none of those works correctly.
I just want to do some research on what kind of restrictions lenovo does to the rom files.
Thank you.

asukav said:
Then that's not a problem.
Can you guide me how to unpack the img files? I tried several but none of those works correctly.
I just want to do some research on what kind of restrictions lenovo does to the rom files.
Thank you.
Click to expand...
Click to collapse
Sorry, I am not sure if it is what you are looking for, but I downloaded the new ROM with LMSA and I do have all the IMG files in the download directory. I do not know if you can do the same not having the exact same tablet model.

asukav said:
So may I ask if you bought your 606f from China or abroad?
Since mine is a Chinese one, everytime I flash 0805/0906 it ends with *system and hardware not compatible* error. (the same both BL locked and unlocked)
I wonder if this new ROW rom fixes this issue.
Thanks.
Click to expand...
Click to collapse
i recently install this rom but have "system and hardware not compatible, can you intsall android 11 on chinese lenovo p11 tablet?

famicom9x said:
i recently install this rom but have "system and hardware not compatible, can you intsall android 11 on chinese lenovo p11 tablet?
Click to expand...
Click to collapse
Still a "NO". It's the same: "system and hardware not compatible".
So I flash back to 0520.
I do hope I could spare some time to unpack those imgs to have a check on some specific files next week.
Just be busy all the time with my work...
Engineers from Lenovo China give me no useful answers. I think I can only count on myself.

I tried update to 210923 via LMSA, but not boot.
Then I tried again with qpst 2.7.496, it boot up and get a minor update to 0925.
Still lost serial number.

Que??

Have a new ROM in https://mirrors.lolinet.com/firmware/lenovo/Tab_P11/TB-J606F/TB-J606F_S320109_211207_ROW.zip but after i flash with QPST 2.7.496 still "system and hardware not compatible". Need someone fix it.

tnt1212 said:
Have a new ROM in https://mirrors.lolinet.com/firmware/lenovo/Tab_P11/TB-J606F/TB-J606F_S320109_211207_ROW.zip but after i flash with QPST 2.7.496 still "system and hardware not compatible". Need someone fix it.
Click to expand...
Click to collapse
It's because your device is Region locked. Within this XDA there is a forum on how to region unlock ur device. You have to use QCN file to change it.
Mine won't update because of region lock and now it's working perfectly

Hey guys, do you know if we still have widevine L1 after updating this ROM with locked bootloader?

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

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!

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.