Database Info

Huawei MediaPad M3 Lite 10 Custom ROM and Custom Recovery [TWRP]

{
"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"
}
​
This thread is for the MediaPad M3 Lite 10 LTE - Tablet from Huawei.
In my case, I´m looking for a C-ROM and C-Recov (e.a. RR, Mokee, TWRP) for the
Huawei MediaPad M3 Lite 10 LTE (BAH-L09) with Android 7.0 and EMUI 5.1
Since it´s quite new on the market it´s atm hard to find anything bout a C-ROM or even a C-recovery.
discoveries
advises
questions
tipps / tricks
productive discussions
solutions
are much appreciated.
Detailed device Informations:
​
​

Nobody knows any thread about this tablet??

Still searching for a root-solution.
So it's possible to read out the firmware with Infinity Box CM2 but haven't found a working "Non-dongle"-version (Loader).
Some days, there will be a root solution.
It just takes time and will be posted in here.

essayn said:
Still searching for a root-solution.
So it's possible to read out the firmware with Infinity Box CM2 but haven't found a working "Non-dongle"-version (Loader).
Some days, there will be a root solution.
It just takes time and will be posted in here.
Click to expand...
Click to collapse
If you need some help and i can do something, tell me

skymota said:
If you need some help and i can do something, tell me
Click to expand...
Click to collapse
I much appreciate the offer but what could u do if u haven´t the device or do u own it ?
Since my CM2-Infinity-box doesn´t work (usually I work with Miracle Box but it´s not compatible ...well the Tablet has to be rooted to read the firmware..), and literally tried all rooting-apps and progs, this device is really stubborn!

I own this device, thats what i told you

skymota said:
I own this device, thats what i told you
Click to expand...
Click to collapse
Very well. ?
Actually, just the stock-recovery is needed to finally start to compile it. Have u been able to extract the recovery or maybe the whole ROM ? ?

essayn said:
Very well.
Actually, just the stock-recovery is needed to finally start to compile it. Have u been able to extract the recovery or maybe the whole ROM ? ?
Click to expand...
Click to collapse
search and read a lot about this but i cant...

skymota said:
search and read a lot about this but i cant...
Click to expand...
Click to collapse
Well, to bad but I guessed so, since this device is atm not rootable. :/
I tried every single Flash-Box like MB, Infinity, Aladdin, Falcon etc pp.. any Rooting-App (APK & PC- based), almost a dozen flash-tools like ADT, AOS-flasher, Ultimate Backup-tool etc...and several command prompts via ADB&Fastboot.
Really Nothing helped to get a nandroid- or even a dumb ROM. From which I could extract the stock recovery.
Nevermind, I will try alil more with Holo- & Heliumbackup, which surely wont work but who knows, rite ??
I'm patient and as soon as I've found a solution I'll share it here immediately.
As any other user is welcome to do so, too.

I´ve managed to extract the stock-recovery via an OTA-update which came from Firmware Finder from Team MT.
U ´ll find the recovery on G-Drive. The "oldRECOVERY.img" is the extracted stock-recovery from the original BAH-L09C100B018 firmware!
So, since I´ve updated the Tablet, the only "RECOVERY.img"-named file is from the newest firmware which is L09C100B021!
If u wanna update to ...021, via the Firmware Finder-App, u need
The App
Time
Be aside your tablet
and watch this video before u start
May read this thread aswell
​

I bought the BAH-W09 model last week, anyone here unlocked bootloader on the lite 10 yet?

jenkins-1984 said:
I bought the BAH-W09 model last week, anyone here unlocked bootloader on the lite 10 yet?
Click to expand...
Click to collapse
Yup, unlocked the BL from day 1. It´s the same procedure for all HUAWEI devices.
Just go here, login or register, confirm the unlocking agreement and put all device infos into the blank fields.
U´ll immediatley get an unlock code, which u have to enter via fastboot command prompts (recommended):
fastboot devices
fastboot oem unlock-go 1234567890123456 <- (this number is an example, u´ll have to put ur code there instead)
fastboot reboot
From now on an unlocked bootloader message will appear every time u start ur device. Just press power shortly to boot then. (It´s also written in the text aswell)
P.S.
Before u try to unlock: Don´t forget to enable USB-debugging in the Engineertool (tap 7 times on "build" in the settings-menue) and "allow OEM unlocking".

essayn said:
Yup, unlocked the BL from day 1. It´s the same procedure for all HUAWEI devices.
Just go here, login or register, confirm the unlocking agreement and put all device infos into the blank fields.
U´ll immediatley get an unlock code, which u have to enter via fastboot command prompts (recommended):
fastboot devices
fastboot oem unlock-go 1234567890123456<- (this number is an example, u´ll have to put ur code there instead)
fastboot reboot
From now on an unlocked bootloader message will appear every time u start ur device. Just press power shortly to boot then. (It´s also written in the text aswell)
P.S.
Before u try to unlock: Don´t forget to enable USB-debugging in the Engineertool (tap 7 times on "build" in the settings-menue) and "allow OEM unlocking".
Click to expand...
Click to collapse
Ok cheers, I looked on the emui site and was nothing under their tablet menu only phones on the unlock bootloader page, on Nexus you just enable usb-debugging and click the OEM unlock in settings and fastboot flashing unlock in terminal. Sony uses a custom tool and HTC via their website I had a few phones in the past and built roms etc this my first Huawei device apart from my Nexus 6p Huawei help build with Google. I take it this device no official forum atm only the Kirin version.

Ya, HUAWEI has a quite faire unlock policy.
Important: There's an unlock bug sometimes. Be sure to have the Original firmware on ur device. (No updated ROM)
Have fun.

essayn said:
Ya, HUAWEI has a quite faire unlock policy.
Important: There's an unlock bug sometimes. Be sure to have the Original firmware on ur device. (No updated ROM)
Have fun.
Click to expand...
Click to collapse
It's on latest official that came with device, I take it there is no twrp or anything out for this device ATM?

Just check a view posts above. I've described how to get the newest FW.
So if the factory ROM-version is installed, unlock the BL and after then update ur ROM. Jfi.
BTW_
Atm there's no custom recovery available for the M3 Lite Versions. U have to compile it by urself or make a request on Hovatek.com

essayn said:
Just check a view posts above. I've described how to get the newest FW.
So if the factory ROM-version is installed, unlock the BL and after then update ur ROM. Jfi.
BTW_
Atm there's no custom recovery available for the M3 Lite Versions. U have to compile it by urself or make a request on Hovatek.com
Click to expand...
Click to collapse
I'm not bothered about updating the firmware ATM more so custom recovery but will look into it after my holiday.

I have requested official forum for this device and looks to be accepted so hopefully get some development going for this device soon...

There seems to be no way to retrieve the unlock code for Wifi-only tablets from the official Huawei site, as it demands the IMEI which is obviously missing.
I have contacted Huawei support with the product ID and serial number of my M3 Lite 10. One day later I have received the unlock code. I think that having been polite has helped
.

Storage question
Hello,
First of all: sorry, if the question is 'noobish', but as a matter of fact I am noob as far as android is concerned
I just bought this tablet for my son (LTE version), and I was quite surprised to find out that I can't move the installed applications to SD card.
Are there any hints and tips on how to take advantage of the big SD card, so my son's game data would not have to be stored in the internal memory?
The only default option is to change the memory from internal to SD, after the tablet restarts. But I assume it uses then only the SD card, and I am looking for a solution I remember from Samsung phone, where I could choose certain apps to move from internal memory to SD.
Another question, just by the way, is following: when I install an apk file from the SD card, during the installation process every few seconds I get a pop-up saying the application is not responding (although the installation is in progress). Any way to disable those annoying pop-ups?
I'd appreciate any feedback

Lenovo Smart Tab P10 TB-X705F aka ZA440169US

So what do you folks think of the new Lenovo Smart Tab P10? I just ordered one because my LG G Pad 8.3 v500 is very long in the tooth and I finally just got tired of waiting for a good spec tablet with plenty of storage and memory to show up. It only has a midrange Snapdragon 450, but the storage a memory make up for that.
https://www.lenovo.com/us/en/smart-tab/
I was looking for a owners manual to read and found this. Looks like replacing the battery in the future won't be too bad. I'll cross my fingers and hope that the bootloader is unlockable.
https://download.lenovo.com/consumer/mobiles_pub/tab_p10_hmm_en_201812.pdf
https://fccid.io/O57TBX705F/User-Manual/User-Manual-R1-pdf-4117204.pdf
Open Source Code
TB-X705F (Wi-Fi)
https://support.lenovo.com/us/en/downloads/DS506312
TB-X705L (LTE)
https://support.lenovo.com/us/en/downloads/DS506313
Stock Roms
TB-X705F (Wi-Fi)
Lenovo TB-X705F_USER_S000017_20180831_Q00020_ROW Factory ROM [androidhost.ru].zip
TB-X705L (LTE)
Lenovo TB-X705L_USER_S000023_20180921_Q00020_ROW Factory ROM [androidhost.ru].zip

I received my Lenovo Smart Tab P10 (TB-X705F) a few weeks ago. It's a nice tablet with good features. The only thing I'm struggling with is unlocking the bootloader. The developer options have the "Allow OEM unlocking" setting and I've enabled it, but no unlock commands are recognized when in fastboot mode. The error is "FAILED (Unknown command)". I've tried "fastboot oem unlock", "fastboot oem unlock-go", "fastboot flashing unlock" etc.

I hope Amazon didn't force Lenovo to lock down the bootloader because it has Alexa poopoo installed. I figure there will be a Chinese exploit for this and the LTE version eventually.
I couldn't stand Alexa and disabled it. I'm looking forward to TWRP so I can make a backup, root and install Adaway.

Same here....
Hey guys, I got the same issue, all unlock commands are unknown. Has anybody got a fix yet?

I had no problem with the bootloader, Tb-x704v. Install most recent https://devsjournal.com/download-minimal-adb-fastboot-tool.html it solved some of my issues.

I bought one a few weeks ago... No dock though. Seems ok, their os is pretty slim though, can't wait for some development.

it is project treble supported but still no lineage 16.1 (pie)? for lenovo tab P10 TB-X705L

Hi, you should be able to unlock bootloader with this command:
fastboot oem enable-unlock-once

TWRP
I installed the TWRP Builder app, but it couldn't extract the recovery image and build.prop file because I don't have root. Do you think that a TWRP recovery can be made from the older firmware in my first post? It has a recovery.img file, but couldn't find a build.prop file.
{
"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"
}

How do we get this device in to it's only device thread? When you search for it through "my device" in the xda app it doesn't come back with a correct result. Maybe it will also get more community development by doing that.

Any hope lineage 16.1 for lenovo tab P10

Hello all,
Any developments on this device. What are the chances of getting rid of the echo features and make it a Google assistant instead?

Can anybody share the alexa show mode apk? I'm downloading the firmware but it is taking ages

Any one been able to install the Google Now Launcher in this tablet? The Play Store message says that it's incompatible with this tablet.
Thanks for any assistance!

Did anybody try to unlock the bootloader in Linux?
I successfully rooted Z3 Play in Linux while it didn't work in Windows
Can anybody find full ROM in lollinet (where I can find Moto/Lenovo ROM)?

I've tried installing the stock images that are posted and keep getting a signature error using the recovery. I noticed that the image doesn't have a system.img but rather system_1.img-system_32.img. Is there a way to package the system files to install the new system? Having an issue with the OTA and it keeps wanting to install the PRN rather than the ROW image. Any thoughts?

Anyone successfully root this as of yet? Not seeing any TWRP for it or an approach.

I today received an update to Android 9 on my tablet. Was kind of surprised. Anyone else can confirm?
Update contains new "Le Tab UI".

so there is no way to root this tablet?

gforums said:
I today received an update to Android 9 on my tablet. Was kind of surprised. Anyone else can confirm?
Update contains new "Le Tab UI".
Click to expand...
Click to collapse
Confirmed. I'm at Android 9 after an OTA update.
Chaser
---------- Post added at 08:27 PM ---------- Previous post was at 07:58 PM ----------
ZHIONZY said:
so there is no way to root this tablet?
Click to expand...
Click to collapse
My tablet is rooted. I found a root solution a little while back, but I haven't posted it yet because it's not very user-friendly. Basically it requires that you do a fresh install of Oreo and it gets bricked on an OTA update. If you're interested in getting it rooted like that then send me a private message. If there's enough interest I'll create a root thread. I consider myself quite capable with Android but not a full expert. I'm really hurting without custom recovery and without a fastboot OEM unlock that works longer than once. That temporary unlock command successfully allows me to swap out the bootloader image but upon reboot it doesn't like the new image as it asks for a password that must be part of the bootloader security because it won't accept any passwords that I have set. Perhaps with a root thread we could all contribute to getting this working. I have two of P10s now so I'm able to test on my spare, but I don't have unlimited time to devote to this.
I know that a lot of people would be excited to get root on this device. I assure you sure you that it is possible. However, I don't want to start a thread with a solution that will force people to do a fresh install of Oreo and possibly lose data. And of course there's the problem with the OTA update which will brick the device. Of course everyone understands that they modify their device at their own risk, but I consider my root solution still a bit dirty and I was hoping at least to get it to accept OTA updates before I wrote up a root guide. I really think that if we could get a permanent bootloader unlock instead of a temporary unlock that we could get past this problem. And if somebody is out there that could make a TWRP image for this device, I think we would be golden as we could do a standard magisk root install via custom recovery.
Chaser

Widevine and MSM help

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

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

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.