I got myself a second hand oneplus 7 pro gm1913, coming from a oneplus 5t. it's running the the latest OOS fully stock but widevine l3. Can someone help me on how to fix this. I've been reading up but i am out of the loop. This MSM tool seems to be a way to fix it. Flash back to 9 to hopefully get back widevine l1 and then update to 10 and to 11. Where can i get this msm tool or do i need to root to get back L1. I have no idea where to begin. It's all changed compared to the 5T. I feel like a total newbie again
UnwindingThree8 said:
I got myself a second hand oneplus 7 pro gm1913, coming from a oneplus 5t. it's running the the latest OOS fully stock but widevine l3. Can someone help me on how to fix this. I've been reading up but i am out of the loop. This MSM tool seems to be a way to fix it. Flash back to 9 to hopefully get back widevine l1 and then update to 10 and to 11. Where can i get this msm tool or do i need to root to get back L1. I have no idea where to begin. It's all changed compared to the 5T. I feel like a total newbie again
Click to expand...
Click to collapse
You will only get L1 Widevine after update from OS9 to OS10, on OS 9 you want get it. Charge your phone, download drivers and MSM Tool from de link below, follow the tutorial. After you flash MSM tool in EDL mode, you will get OS 9, set up your phone and you will receive an OS 10 OTA update, update and after check if you have L1 Widevine certificate, if so, continue and you will receive a new OTA update to OS 11 last build. You don't need to root to get back L1. MSM toll will wipe your full data and relock the bootloader.
I have the same model and used this tutorial and this MSM tool for 3 times, go ahead!
Here it is:
[MSM Tool] Guac for All
To everyone who donated, I love y'all. This took a really long time to get lol but it's straight from support and I did not make any modifications to it; I hope it helps a lot of people. The revision is listed in the archive, I believe it's...
forum.xda-developers.com
If you have problems with Qualcomm drivers!
Qualcomm HS-USB QDLoader 9008 Drivers: Download and Installation Guide
Download Qualcomm HS-USB QDLoader 9008 drivers for communicating with your Android device in Emergency Download (EDL) mode. Learn how to install these drivers on any Windows 11/10/8.1/8/7 computer.
www.thecustomdroid.com
UnwindingThree8 said:
I got myself a second hand oneplus 7 pro gm1913, coming from a oneplus 5t. it's running the the latest OOS fully stock but widevine l3. Can someone help me on how to fix this. I've been reading up but i am out of the loop. This MSM tool seems to be a way to fix it. Flash back to 9 to hopefully get back widevine l1 and then update to 10 and to 11. Where can i get this msm tool or do i need to root to get back L1. I have no idea where to begin. It's all changed compared to the 5T. I feel like a total newbie again
Click to expand...
Click to collapse
Did you fixed the issue with MSM tool?
I fix this issue by flashing via MSM Tool using latest android 10 of OOS, then from that, you can just upgrade to android 11 as usual. As a matter of fact, I still manage to have widevine l1 even after opening the bootloader. But I went to install crdroid 8.6 and that messes up the widevine again. Well, atleast I know exactly how to fix it.
This thread must move to Q&A Forum.
madhuranand007 said:
This thread must move to Q&A Forum.
Click to expand...
Click to collapse
Spoiler: Thread moved
{
"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"
}
Just report a thread when it needs maintenance
Hello,
Do you guys think EU, NA, IN firmwares aren't equal when it comes to DRM restrictions/restoration ?
I'm talking with a USA guy who can restore DRM L1 with MSM (he uses NA firmwares) on a A12.1 custom rom
Doing the same process with the same firmware but EU builds won't restore widevine L1..
What a mess
Your feedbacks are highly appreciated
ps : quote me so i won't miss your answer
Neil_Armstrong_ said:
Hello,
Do you guys think EU, NA, IN firmwares aren't equal when it comes to DRM restrictions/restoration ?
I'm talking with a USA guy who can restore DRM L1 with MSM (he uses NA firmwares) on a A12.1 custom rom
Doing the same process with the same firmware but EU builds won't restore widevine L1..
What a mess
Your feedbacks are highly appreciated
Click to expand...
Click to collapse
I don't think they are equal. I have a IN version OP7Pro and I had widevine l3 issues. I flashed OOS 10 through MSM tool and updated with system update and it didn't do anything. I am still on L3. That means things are different.
luarpc said:
You will only get L1 Widevine after update from OS9 to OS10, on OS 9 you want get it. Charge your phone, download drivers and MSM Tool from de link below, follow the tutorial. After you flash MSM tool in EDL mode, you will get OS 9, set up your phone and you will receive an OS 10 OTA update, update and after check if you have L1 Widevine certificate, if so, continue and you will receive a new OTA update to OS 11 last build. You don't need to root to get back L1. MSM toll will wipe your full data and relock the bootloader.
I have the same model and used this tutorial and this MSM tool for 3 times, go ahead!
Here it is:
[MSM Tool] Guac for All
To everyone who donated, I love y'all. This took a really long time to get lol but it's straight from support and I did not make any modifications to it; I hope it helps a lot of people. The revision is listed in the archive, I believe it's...
forum.xda-developers.com
Click to expand...
Click to collapse
Hi bud, followed these steps and followed the steps of flashing MSM on the link attached and updated through to OoS10 and still at L3. Using GM1913 (EU OP7 Pro). any suggestions?
Mister_T_97 said:
Hi bud, followed these steps and followed the steps of flashing MSM on the link attached and updated through to OoS10 and still at L3. Using GM1913 (EU OP7 Pro). any suggestions?
Click to expand...
Click to collapse
It worked with me. I'm using a Custom ROM now with L1. Try to update to last build OOS 11.9. Check if you have L1. There are people who get L1 flashing Magisk. If not try to flash OOS 11 on 2 slots, a and b.
Mister_T_97 said:
Hi bud, followed these steps and followed the steps of flashing MSM on the link attached and updated through to OoS10 and still at L3. Using GM1913 (EU OP7 Pro). any suggestions?
Click to expand...
Click to collapse
Try this too if doesn't work the other way.
Steps to go enable Widevine L1.
• Flash OOS 11 stable. eg.11.0.5.1
• Flash Magisk then enable Zygisk + denylist.(in denylist you should select show system apps in three-dot menu,then search gms, select com.google.android.gms and .gms.unstable)or use Magisk v23.0 for test purpose.
• Reboot.
• Verify if you have L1 working using app like DRM info.
• Local upgrafe OOS 11 stable (preferably same build).
• Reboot.
• Verify if you have L1 working using app like DRM info.
Note: you only need to do this once
Related
Hi!
Today i successfully bricked my OP9 to the point where the global MSM tool couldn't recognize it anymore.
I tried everything, from different MSM tools to this thread. Nothing.
Then, Deus ex Machina, @flameteam recommended me to try Indian/EU version of MSM tool for OP9 Pro with Lite Firehose...
...It worked.
It makes no sense, but it worked for me. Try it. Good luck, and thanks a million again @flameteam !!
Enjoy it I struggled for a week. The result is ridiculous but successful
_MartyMan_ said:
Hi!
Today i successfully bricked my OP9 to the point where the global MSM tool couldn't recognize it anymore.
I tried everything, from different MSM tools to this thread. Nothing.
Then, Deus ex Machina, @flameteam recommended me to try Indian/EU version of MSM tool for OP9 Pro with Lite Firehose...
...It worked.
It makes no sense, but it worked for me. Try it. Good luck, and thanks a million again @flameteam !!
Click to expand...
Click to collapse
Yes !! thanks @flameteam. My Oneplus 9 EU was really super hard bricked (turned to the "dark side") with no display whatsoever. I went for the EU package and the phone came back to life !!
This was the only way as some other download tool dedicated for the Oneplus 9 didn't work. Gave me "Sahara error. (with Windows 7, 10, different USB cables etc)
And , yes as strange as it sounds my Oneplus 9 now runs the OP9 Pro firmware ?!?!.
But this gave me the chance to install the stock OTA for Oneplus 9. It seems to work.
The question is if a full stock OTA OP9 actually cleaned out any trace of the previous Pro version ?
Big Update. my phone is coming back and free again )i think) No warranty, just wild QoL issues with the 9, it seems.
Im still very happy to get it back .
{
"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"
}
Yo i love you bro.....seriously you are the fkkkng mannnn omg
josc002 said:
Yes !! thanks @flameteam. My Oneplus 9 EU was really super hard bricked (turned to the "dark side") with no display whatsoever. I went for the EU package and the phone came back to life !!
This was the only way as some other download tool dedicated for the Oneplus 9 didn't work. Gave me "Sahara error. (with Windows 7, 10, different USB cables etc)
And , yes as strange as it sounds my Oneplus 9 now runs the OP9 Pro firmware ?!?!.
But this gave me the chance to install the stock OTA for Oneplus 9. It seems to work.
The question is if a full stock OTA OP9 actually cleaned out any trace of the previous Pro version ?
Click to expand...
Click to collapse
yes cleaning msm tool
The Indian version of MSM was able to restore my phone, but now I cant install any OTAs without bricking it. How did you get it back to a Global rom after the MSM retore?
I was finally able to unbrick by using this method after days of troubleshooting, but now how in the hell do I get the OnePlus 9 firmware back onto it? I've downloaded different (full zip) ota's, moved to root storage, and when I go to system settings --> local upgrade, the updates do not show up there. I tried flashing via TWRP and I believe it booted to inactive slot (where update was applied) and bootlooped. Eventually it booted back into slot A with OP9Pro firmware. I thought maybe I could use global msm tool for OP9 but the thread that says "UPDATED" downloads and then fails to open. So far only msm tool I have gotten to work for my phone was for the Indian OP9Pro variant.
_MartyMan_ said:
Hi!
Today i successfully bricked my OP9 to the point where the global MSM tool couldn't recognize it anymore.
I tried everything, from different MSM tools to this thread. Nothing.
Then, Deus ex Machina, @flameteam recommended me to try Indian/EU version of MSM tool for OP9 Pro with Lite Firehose...
...It worked.
It makes no sense, but it worked for me. Try it. Good luck, and thanks a million again @flameteam !!
Click to expand...
Click to collapse
you still bricked foooo??? adb reboot edl launch msm tool in thank me lataaaa
Hallelujah!!!! IT WORKED!!!!!!!!! I've been bricked for a month!!
The question now is how do i get back to global? Any ideas?
Anyone???
YES
Got back to global. Took me a day to figure it out. Enable OEM Unlock and USB debugging. I flashed temp TWRP, installed the OS Zip file from OnePlus support site. Rebooted into recovery, formatted and wiped system. Booted into global. This installation is in SLOT B. Slot A will still have horrible Indian Rom (only horrible because it shouldn't be installed on my Global Unlocked Phone, no disrespect to my Indian brothers.) Note when logging in for the first time let global do its OTA update before you do anything else, especially before you reboot. The Indian version is installed in slot A. REBOOT after OTA installed. Don't reboot before OTA does its thing. This will ensure Slot A has a clean installation. I made the mistake of rebooting before the OTA and I could not do anything with slot A. Relock the bootloader, it will wipe and you will boot into a pristine Global OS 11.2.8.8 Rom.
lrod55 said:
I was finally able to unbrick by using this method after days of troubleshooting, but now how in the hell do I get the OnePlus 9 firmware back onto it? I've downloaded different (full zip) ota's, moved to root storage, and when I go to system settings --> local upgrade, the updates do not show up there. I tried flashing via TWRP and I believe it booted to inactive slot (where update was applied) and bootlooped. Eventually it booted back into slot A with OP9Pro firmware. I thought maybe I could use global msm tool for OP9 but the thread that says "UPDATED" downloads and then fails to open. So far only msm tool I have gotten to work for my phone was for the Indian OP9Pro variant.
Click to expand...
Click to collapse
See above. I figured it out.
Ok. this worked for me... I was able to save my LE2110 from being hard bricked. THANK YOU.
Now, has anyone been able to go back to the non-Pro software?
If so, how did you do it?
zborn said:
Ok. this worked for me... I was able to save my LE2110 from being hard bricked. THANK YOU.
Now, has anyone been able to go back to the non-Pro software?
If so, how did you do it?
Click to expand...
Click to collapse
See my response above.
ctonylee1965 said:
See my response above.
Click to expand...
Click to collapse
That didn't work for me. I just MSMed back to 9 firmware
lrod55 said:
I was finally able to unbrick by using this method after days of troubleshooting, but now how in the hell do I get the OnePlus 9 firmware back onto it? I've downloaded different (full zip) ota's, moved to root storage, and when I go to system settings --> local upgrade, the updates do not show up there. I tried flashing via TWRP and I believe it booted to inactive slot (where update was applied) and bootlooped. Eventually it booted back into slot A with OP9Pro firmware. I thought maybe I could use global msm tool for OP9 but the thread that says "UPDATED" downloads and then fails to open. So far only msm tool I have gotten to work for my phone was for the Indian OP9Pro variant.
Click to expand...
Click to collapse
I hard bricked my oneplus 9 first time and was panicking. Luckily I found this thread and your answer. You guys saved me hours and days of fixing this, most important of all, I can't tell me wife that I trashed a $800 phone after bought it a couple days ago. I was able to get my phone back into EU version using the MSM tool, lost my IMEI # and sim card won't work, So I was able to switch back to global after following your instruction. Thank you.
_MartyMan_ said:
Hi!
Today i successfully bricked my OP9 to the point where the global MSM tool couldn't recognize it anymore.
I tried everything, from different MSM tools to this thread. Nothing.
Then, Deus ex Machina, @flameteam recommended me to try Indian/EU version of MSM tool for OP9 Pro with Lite Firehose...
...It worked.
It makes no sense, but it worked for me. Try it. Good luck, and thanks a million again @flameteam !!
Click to expand...
Click to collapse
How did you do it? I am trying this method, but MSM tool gives me this error:
Hello i received one(tb-j716f) unlocked with a globaoe fw without ota's and i flashed the cn one and took the boot.ipg and patched it with pagisk for root and when flashing it via fastboot the device reboots to fastboot everytipe 1nd had to reflash the fw via edl , i did flashed vbmeta img with the known command o disable verification but no success same thing again. Can anyone plz tell me how to root that crap , it was intended to root use only and took over xiaomi pad pro just because the xiaomi needs 7 days of waiting before unlocking , plz help guys .thx so much i can buy a couple beers for the helper
i think you should write your question separately, and have some pictures of step by steps , so i can help you find the root cause and solutions
luizkun said:
i think you should write your question separately, and have some pictures of step by steps , so i can help you find the root cause and solutions
Click to expand...
Click to collapse
I tried to root it patching the boot.img but it wont boot after that and goes straight to fastboot , i used same bootfile on the device
I rooted it successfully , for those who want it just pm me
Pm me
Why don't you directly post the method here? The philosophy of this forum does not work like that.
bouyhy01 said:
Pm me
Click to expand...
Click to collapse
pmed
The method is described here on the Chinese forum. Keeping things like this for yourself and asking money doesn't help the community much...
MOD EDIT: Quote deleted since post deleted.
You seem like a very trustworthy and mature person, don't expect anyone to help you with this attitude.
Also you should read the forum rules before posting.
zxcv88 said:
The method is described here on the Chinese forum. Keeping things like this for yourself and asking money doesn't help the community much...
Click to expand...
Click to collapse
I had a look at that website through google translate, however it's a bit unclear..
I've got an unlocked Pad Pro 2021 TB-J716F on 12.5.126, which as far I could make out is the correct firmware for rooting.
Do you know the actual steps required for rooting?
Thanks
tinybilbo said:
I had a look at that website through google translate, however it's a bit unclear..
I've got an unlocked Pad Pro 2021 TB-J716F on 12.5.126, which as far I could make out is the correct firmware for rooting.
Do you know the actual steps required for rooting?
Thanks
Click to expand...
Click to collapse
I haven't tried it because I flashed original firmware and relocked my bootloader. Maybe someone else has tried and is willing to share the info.
zxcv88 said:
I haven't tried it because I flashed original firmware and relocked my bootloader. Maybe someone else has tried and is willing to share the info.
Click to expand...
Click to collapse
No worries! Thanks anyway.
If anyone has managed it, would they mind just listing the process.
@bouyhy01
As @sakun-ice requested, please share your knowledge publicly. Sharing is at the heart of XDA. Please do not ask users to contact you via PM for sharing the rooting steps.
Just a quick update for those wishing to root a TB-J716f
I had a "global" ZUI_12.5.126 with play store pre-installed. I was forced to update since Magisk wouldn't install properly.
So I updated to the latest firmware I could find... ZUI_13.0.346
Update (and relock bootloader to use OTA updates)
1) Grabbed my DeviceID by typing ####2222# into the search bar in Settings.
2) Then went to
https://www.zui.com/iunlock
and input the DeviceID to get the bootloader unlock image.
ZUI_12.6.211 (OPST)
3) Flashed TB-J716F_CN_OPEN_USER_Q00209.3_R_ZUI_12.6.211_ST_210730_qpst.zip via qfil. Used Tropaion's Guide (thanks).
Install Stock ROM - Xiaoxin Pad Pro 2021 [TB-J716F]
How to install Stock ROM - Xiaoxin Pad Pro 2021 [TB-J716F] I tried installing a GSI-ROM on this tablet, which basically worked except for three/four bugs I coulnd't solve. So I tried to restore the Stock ROM in the meantime and will share my...
forum.xda-developers.com
4) Locked bootloader using Tropaion's guide (thanks again ).
Lock+Unlock Bootloader - Xiaoxin Pad Pro 2021 [TB-J716F]
How To Lock and Unlock Bootloader - Xioaxin Pad Pro 2021 - TB-J716F Since I found out that the Tablet supports Project Treble I'm trying to get a GSI-ROM running on it. Currently with many trial and error I got LiR-ROM to boot. The first step is...
forum.xda-developers.com
ZUI_12.6.238 (OTA)
5) Put TB-J716F_CN_OPEN_USER_Q00209.3_R_ZUI_12.6.211_ST_210730_to_TB-J716F_CN_OPEN_USER_Q00209.3_R_ZUI_12.6.238_ST_210824.zip into the root of the tablet and renamed it update.zip.
6) Used system update to update to ZUI_12.5.238.
ZUI_13.0.346 (OTA)
7) Put TB-J716F_CN_OPEN_USER_Q00209.3_R_ZUI_12.6.238_ST_210824_to_TB-J716F_CN_OPEN_USER_Q00209.3_R_ZUI_13.0.346_ST_211108.zip into the root of the tablet and renamed it update.zip.
8) Used system update to update to ZUI_13.0.346.
Root
1) Extracted boot.img from firmware ZUI_13.0.346 (use this guide)
Extract Android OTA Payload.bin File using Payload Dumper Tool
Learn how to dump and extract Android OTA Payload.bin file to get the boot.img (for rooting with Magisk), vendor.img, and other other partition images.
www.thecustomdroid.com
2) Installed latest Magisk and patched the extracted (transferred from PC) boot.img.
3) Transferred the magisk_patched.img from Pad to the PC.
4) Unlocked bootloader using Tropaion's guide.
Lock+Unlock Bootloader - Xiaoxin Pad Pro 2021 [TB-J716F]
How To Lock and Unlock Bootloader - Xioaxin Pad Pro 2021 - TB-J716F Since I found out that the Tablet supports Project Treble I'm trying to get a GSI-ROM running on it. Currently with many trial and error I got LiR-ROM to boot. The first step is...
forum.xda-developers.com
5) Rebooted into fastboot and flashed the modified boot.img (from the PC) fastboot flash boot magisk_patched.img
Hope that helps anyone else who might want to do the same...
tinybilbo said:
Just a quick update for those wishing to root a TB-J716f
I had a "global" ZUI_12.5.126 with play store pre-installed. I was forced to update since Magisk wouldn't install properly.
So I updated to the latest firmware I could find... ZUI_13.0.346
Update (and relock bootloader to use OTA updates)
1) Grabbed my DeviceID by typing ####2222# into the search bar in Settings.
2) Then went to
https://www.zui.com/iunlock
and input the DeviceID to get the bootloader unlock image.
ZUI_12.6.211 (OPST)
3) Flashed TB-J716F_CN_OPEN_USER_Q00209.3_R_ZUI_12.6.211_ST_210730_qpst.zip via qfil. Used Tropaion's Guide (thanks).
Install Stock ROM - Xiaoxin Pad Pro 2021 [TB-J716F]
How to install Stock ROM - Xiaoxin Pad Pro 2021 [TB-J716F] I tried installing a GSI-ROM on this tablet, which basically worked except for three/four bugs I coulnd't solve. So I tried to restore the Stock ROM in the meantime and will share my...
forum.xda-developers.com
4) Locked bootloader using Tropaion's guide (thanks again ).
Lock+Unlock Bootloader - Xiaoxin Pad Pro 2021 [TB-J716F]
How To Lock and Unlock Bootloader - Xioaxin Pad Pro 2021 - TB-J716F Since I found out that the Tablet supports Project Treble I'm trying to get a GSI-ROM running on it. Currently with many trial and error I got LiR-ROM to boot. The first step is...
forum.xda-developers.com
ZUI_12.6.238 (OTA)
5) Put TB-J716F_CN_OPEN_USER_Q00209.3_R_ZUI_12.6.211_ST_210730_to_TB-J716F_CN_OPEN_USER_Q00209.3_R_ZUI_12.6.238_ST_210824.zip into the root of the tablet and renamed it update.zip.
6) Used system update to update to ZUI_12.5.238.
ZUI_13.0.346 (OTA)
7) Put TB-J716F_CN_OPEN_USER_Q00209.3_R_ZUI_12.6.238_ST_210824_to_TB-J716F_CN_OPEN_USER_Q00209.3_R_ZUI_13.0.346_ST_211108.zip into the root of the tablet and renamed it update.zip.
8) Used system update to update to ZUI_13.0.346.
Root
1) Extracted boot.img from firmware ZUI_13.0.346 (use this guide)
Extract Android OTA Payload.bin File using Payload Dumper Tool
Learn how to dump and extract Android OTA Payload.bin file to get the boot.img (for rooting with Magisk), vendor.img, and other other partition images.
www.thecustomdroid.com
2) Installed latest Magisk and patched the extracted (transferred from PC) boot.img.
3) Transferred the magisk_patched.img from Pad to the PC.
4) Unlocked bootloader using Tropaion's guide.
Lock+Unlock Bootloader - Xiaoxin Pad Pro 2021 [TB-J716F]
How To Lock and Unlock Bootloader - Xioaxin Pad Pro 2021 - TB-J716F Since I found out that the Tablet supports Project Treble I'm trying to get a GSI-ROM running on it. Currently with many trial and error I got LiR-ROM to boot. The first step is...
forum.xda-developers.com
5) Rebooted into fastboot and flashed the modified boot.img (from the PC) fastboot flash boot magisk_patched.img
Hope that helps anyone else who might want to do the same...
Click to expand...
Click to collapse
This is great! I will definitely try this when I have time. Also because I don't care much for widevine anymore because I found a better alternative to Netflix.
I wonder how did you get the ZUI_13.0.346 update because it doesn't show up on my tablets OTA.
zxcv88 said:
This is great! I will definitely try this when I have time. Also because I don't care much for widevine anymore because I found a better alternative to Netflix.
I wonder how did you get the ZUI_13.0.346 update because it doesn't show up on my tablets OTA.
Click to expand...
Click to collapse
I found it in a WeChat folder link, in the post you linked (post #08). So thanks for that .
It was headache getting signed up for the a Chinese forum...! But perseverance and google translate helped!
{
"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 don't use Netflix or Amazon either.... KODI is my friend....
tinybilbo said:
I found it in a WeChat folder link, in the post you linked (post #08). So thanks for that .
It was headache getting signed up for the a Chinese forum...! But perseverance and google translate helped!
View attachment 5460559
I don't use Netflix or Amazon either.... KODI is my friend....
Click to expand...
Click to collapse
I tried to sign up for that forum too but wasn't able to get through the phone verification... Would you mind sharing the download link here cause I'm not able to find it.
Thanks!
EDIT: I reuploaded the update here.
Big thanks to @tinybilbo for sharing!
zxcv88 said:
I tried to sign up for that forum too but wasn't able to get through the phone verification... Would you mind sharing the download link here cause I'm not able to find it.
Thanks!
EDIT: I reuploaded the update here.
Big thanks to @tinybilbo for sharing!
Click to expand...
Click to collapse
No worries, enjoy the update... (btw I was also stumped by the phone verification for that site, however I managed to get a temporary Chinese SMS number via a random site that I googled!)
Just remember you need to come from firmware ZUI_12.6.238 with a locked bootloader for this to work.
(I have the other updates required if you need them, just DM me).
Okay so I just tried this and it worked perfectly!
Also as a little bonus I managed to pass safetynet while unlocked and rooted lol. Although widevine is still L3.
Thanks a lot @tinybilbo for the guide. You should make a how to topic so others can easily find it as well.
zxcv88 said:
Okay so I just tried this and it worked perfectly!
Also as a little bonus I managed to pass safetynet while unlocked and rooted lol. Although widevine is still L3.
Thanks a lot @tinybilbo for the guide. You should make a how to topic so others can easily find it as well.
Click to expand...
Click to collapse
Glad to hear you got rooted!
What did you do in order to pass safetynet? (that was next on my list!)
thx
This was a Untested MSM .OPS file for the EU Variant use at your own risk.
This was tested by @lockmunk and verified to be working for the EU varient of the device check post 4 if you want to see proof.
This will fail verification when pressing verify because the msm tools used was originally global msm,i just swapped the ops files so it could be flashed.
This was made using the files linked here : https://forum.xda-developers.com/t/...oneplus-9-le2113-with-msm-tool.4320461/page-2
ANY AND ALL DAMAGE DONE TO YOUR DEVICE AFTER THIS IS NOT MY RESPONSIBILITY.....
I take no responsibility for you hardbricking your device or it becoming nonworking after this......
This is OxygenOS_11.2.7.7.LE25BA firmware as shown in the screenshot in post #4
https://www.mediafire.com/file/gyv5gza7t4ibn7j/OnePlus_9_EU_lemonade_22_E.10_210609.zip/file
PREREQUISITES
MUST HAVE QUALCOMM DRIVER'S INSTALLED (FOR EDL TO WORK!!)
CLICK LINK DOWNLOAD MSM TOOL
UNZIP
CLICK ON MSM TOOL
RUN AS OTHER!!
REBOOT TO EDL.
(POWER OFF)
HOLD BOTH VOLUME UP AND DOWN CONNECT TO PC
WHEN YOU SEE CONNECTED CLICK START AND LET IT RUN DEVICE WILL REBOOT ONCE & DONE!!!
wow this is nice. can someone test it?
dear @allenjthomsen a
Found that MD5 checksum failed
{
"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"
}
ok I risk myself to tried it out.
and the results is...it REALLY WORKS!!
below is my settings in MSM and about phone
lockmunk said:
dear @allenjthomsen a
Found that MD5 checksum failed
View attachment 5479725
Click to expand...
Click to collapse
It will fail md5 verification because msm tools in this file were originally global i just swapped the ops file.
lockmunk said:
ok I risk myself to tried it out.
and the results is...it REALLY WORKS!!
below is my settings in MSM and about phone
Click to expand...
Click to collapse
this is good im glad it was able to restore your phone to EU
My model is le2110 and a bit afraid of bricking. Anyone tested on 2110?
azizolmez said:
My model is le2110 and a bit afraid of bricking. Anyone tested on 2110?
Click to expand...
Click to collapse
LE2110 is CN and normally comes with Colour OS unless converted to IN firmware. LE2113 is EU. LE2115 is NA/Global.
This info was taken from OP9 community forum.
allenjthomsen said:
LE2110 is CN and normally comes with Colour OS unless converted to IN firmware. LE2113 is EU. LE2115 is NA/Global.
This info was taken from OP9 community forum.
Click to expand...
Click to collapse
Converted oos11 then flashed havoc. Now I want to go back to stock.
Thanks you a lot for making this. Sorry cause i m asking but, can it be done with last 11.2.10.10 too? Thanks xDD
azizolmez said:
Converted oos11 then flashed havoc. Now I want to go back to stock.
Click to expand...
Click to collapse
you can use it with no problem, i have LE2110 too, but i live in Europe. Until now i was using GLOBAL MSM to get OOS and flashing Europe by local update.
Sheldd said:
Thanks you a lot for making this. Sorry cause i m asking but, can it be done with last 11.2.10.10 too? Thanks xDD
Click to expand...
Click to collapse
I'm not sure thats possible unless the msm files could be found like the ones provided in the thread that i linked, best i can say for now is just use the provided msm i made and update via settings to latest firmware.
Sheldd said:
Thanks you a lot for making this. Sorry cause i m asking but, can it be done with last 11.2.10.10 too? Thanks xDD
Click to expand...
Click to collapse
When I try this files, I also on this version. Should be no problem. Then now I updated to 11.2.10.10 without any problem.
allenjthomsen said:
This was a Untested MSM .OPS file for the EU Variant use at your own risk.
This was tested by @lockmunk and verified to be working for the EU varient of the device check post 4 if you want to see proof.
This will fail verification when pressing verify because the msm tools used was originally global msm,i just swapped the ops files so it could be flashed.
This was made using the files linked here : https://forum.xda-developers.com/t/...oneplus-9-le2113-with-msm-tool.4320461/page-2
ANY AND ALL DAMAGE DONE TO YOUR DEVICE AFTER THIS IS NOT MY RESPONSIBILITY.....
I take no responsibility for you hardbricking your device or it becoming nonworking after this......
This is OxygenOS_11.2.7.7.LE25BA firmware as shown in the screenshot in post #4
OnePlus_9_EU_lemonade_22_E.10_210609.zip
drive.google.com
PREREQUISITES
MUST HAVE QUALCOMM DRIVER'S INSTALLED (FOR EDL TO WORK!!)
CLICK LINK DOWNLOAD MSM TOOL
UNZIP
CLICK ON MSM TOOL
RUN AS OTHER!!
REBOOT TO EDL.
(POWER OFF)
HOLD BOTH VOLUME UP AND DOWN CONNECT TO PC
WHEN YOU SEE CONNECTED CLICK START AND LET IT RUN DEVICE WILL REBOOT ONCE & DONE!!!
Click to expand...
Click to collapse
Work fine on my OnePlus 9, thank you for saving my phone
I flashed with MSM Tool to my LE2110 but Model Number doesn't change
isson said:
I flashed with MSM Tool to my LE2110 but Model Number doesn't change
Click to expand...
Click to collapse
based on my experience with OP devices the model number will not change on your device even if you flash a different msm.
isson said:
I flashed with MSM Tool to my LE2110 but Model Number doesn't change
Click to expand...
Click to collapse
The model number wont change by flashing a diferent region rom. Only if you flash the weirdo OOS12 update you will see LE2115 xDD
I flashed with MSM Tool to my LE2110 works very well , but im unchecked all
the model name remain the same too, but no problem finally we have a tool to re-alive our op9
thanks boss
Would this work with the T-Mobile op9? I went that whole India 9pro direction and now my phone can't use the fingerprint sensor or proximity sensor. Any feedback would be great thanks.
I have one question, since supported LTE frequencies is a software limitation, flashing the EU version when we come from global rom change something one le2110 model?
akboy7015 said:
I have one question, since supported LTE frequencies is a software limitation, flashing the EU version when we come from global rom change something one le2110 model?
Click to expand...
Click to collapse
no changement, no change name model remain all perfect as a new model
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
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.