Database Info

[TOOL] Lx Multi Tool v1.3.2 [WIN/LIN/MAC][Unlock/Recovery/Stock/Kernel/More]

{
"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"
}
It has LINUX/UNIX and MAC support!
​
Due to the fact that there is another tool for Android called Android Multi Tools, I decided to rename this one to Lx Multi Tool, future releases will go under this name.
Features: ​Fastboot
- Unlock/Lock Bootloader
- Flash Recovery Menu (you can choose and add recoveries) - TWRP 2.8.7.2 Included
- Flash any partition (Flashing submenu)
- Flash full Stock images (you can choose and add images)
- Erase partitions (you can choose which of the partitions)
- Reboot (you can choose again...)
Adb
- Sideload .zip files (you can choose and add .zip files) - SuperSU v2.65 (Systemless!) included
- Backup (you can choose the name and place for your backup)
- Restore (you can choose your backup)
- Version (it just shows the version of your adb binaries) - platform-tools 23.1 included
- Logs (DMESG and Logcat)
- Screenshots (you can directly take screenshots to your PC with no Root)
- Reboot (lots of choices)
Others
- Refresh and delete files/folders from menus (Right click or key F5 and Del)
- Open tool folders from the menus (to add your own kernel/stock image/recovery/sideload zip files)
- Tab key support for easier keyboard navigation
- Tool-tips for all buttons
- Check for updates
- Link to xda-thread (here)
​
Download links: ​Windows x86|x64 - Linux x64 - MAC x64
All released versions can be found here.
​
[ROOT] Use SuperSU 2.62 or higher from here systemless for 6.0.1 and above.​
Known bugs/limitations: ​ - For partition Flashing, it is recommended(mandatory?) to do a reboot-bootloader if you want to flash multiple partitions one after the other. (according to the Google flashing scripts) (Implemented in 1.2.1)
- For return to stock, the tool will be stuck after your phone successfully boots, you need to reboot to fastboot again in order to flash the Radio and finish the full return to stock. (Fixed in 1.2.0)​
Changelog: ​
Check the changelog for each release here.
​
Tutorials/FAQ: ​
Q: How do I get in bootloader/fastboot mode?
Turn off the phone and turn it on by using Volume down + Power key.
Q: How do I check for updates in your tool?
Follow the instructions in the screen below.
Q: Where can I find the device driver to install it for windows?
Click here, download the driver and run the setup.
Q: How do I root my stock phone?
- Unlock bootloader.
- Flash recovery.
- Use SuperSU 2.62 systemless or higher from here.
(Usually the latest version upon tool release is included in the Sideload folder of the tool, you can either sideload it or copy it to recovery and flash it manually)
Q: I get an error "Cannot open file" on MAC, what should I do?
Open the terminal, go to your application path and paste this command:
Code:
chmod +x LxMultiTool.app/contents/macos/*
Q: What do I need to do in order to be in Fastboot or in ADB mode.
Fastboot mode will be detected only while being in bootloader.
ADB mode will be detected from Recovery (custom) and actual ROM with USB debugging active.
Refresh button needs to be used in order to check for what mode you are in.
Q: Are there any other software that I need to install in order to run this tool?
On Windows and MAC everything is bundled, so nothing needs to be installed, just run.
On Linux you need to install from your package manager libQt5Core, libQt5Widgets, libQt5Gui, libQt5Network.
If it's not enough, use ldd LxMultiTool in terminal to find out what you're missing from your environment.
Q: I have an yellow/orange/red text screen during boot, what's that?
When you unlock you usually get the Orange screen and it's normal, but if you really want to know what's this about, give a reading to this.
Q: Hey, my device is not detected, why?
On windows, you need to manually install the USB drivers, they are not included and probably they won't be included in this tool.
Also, make sure you click the connection Refresh button after connecting the device to your PC.
Q: What do i need to do in order to install a custom ROM?
1. Unlock Bootloader.
2. Flash a custom recovery of your choice.
3. Flash an insecure kernel (boot).
4. Flash custom ROM with no problems via recovery.
All those things are found and can be done via this tool.
Q: Hi, i just downloaded this tool, how do i use it?
First, extract the folder somewhere.
After that, run LxMultiTool.exe on windows by double clicking it, LxMultiTool on linux and the same on mac.
Q: Do I need android-sdk installed or something else?
No! This tool uses it's own supplied binaries for adb and fastboot, if you have android-sdk installed it will be ignored anyways.
This tool is fully portable and stand-alone.
Q: I get an error while trying to unlock the bootloader -> FAILED(remote: oem unlock is not allowed), what now?
Starting with Android 5.0, you need to enable Bootloader Unlocking from the developer settings, in order to do that, follow these steps:
- Enable Developer options
- Enable USB Debugging
- Look for the ‘OEM Unlock’ Option and toggle it.
Q: How do I use the return to stock feature?
First download the latest package from here, then extract the contents (there is an archive in the archive) untill you get the a folder like angler-mda89d
that contains the images, that folder needs to be copied in the /Data/StockPackages folder in order to be visible.
Easier steps -> Get your device in bootloader -> Start the tool -> Hit refresh -> go to Stock -> hit open folder -> copy the extracted folder with the name angler-xxxxxx in there, hit F5 or Right-click + Refresh -> you should see the folder in there like in the following screenshot. Thanks @ursa08 for the screenie.
Q: How do I enable Developer options?
- Launch the Settings
- Scroll Down and Tap on About Phone(or About Device)
- Locate the Build Number Section
- Tap on the Build Number Option 7 Times
- Go Back to the Main Settings Page
- Scroll Down and Tap on Developer Options
Q: Hi, i just bought a phone what should i do now?
Well, you firstly need to unlock your bootloader...
Q: What is logcat?
Well, you can pretty much use google for that answer, but to put it short, is that thingy that tells you what is happening behind the scenes of your phone.
It is usually used for debugging and entertaiment(?).
When you report an error/bug to somebody, it will be a blessing to provide a logcat (logfile)!
Q: What is a Custom Recovery and why do i need one?
A custom recovery is that thingy that let's you flash .zip files, use your logic and you wil get it why you need one.
Q:There are others guides/tutorials out there, should i check them instead of this?
If you manage to get things done using this one, no, otherwise yes, note that some could be outdated...
Q:What is sideload and how do I use it?
Sideload is a function from adb that let's you flash a zip file while in recovery directly from your PC.
Please note that you need to be in sideload mode on your recovery before doing this.
To enter sideload mode, in TWRP go to Advanced -> ADB Sideload -> Swipe to sideload​
Sources: ​The official and original repository can be found here.​
Bug reports/Feature requests: ​If you have any bug, or you consider a feature to be a must-have, please use the issue functionality on github for more traceability here.​
Licensing: ​Please note that this tool is open source and released under GPL v3 licence which can be read here.
Make sure you understand at least the short version of the license that's provided in the tool before using it or before contributing/forking and other related stuff.​
Tech and stuff: ​Some additional marketing for stuff used in this tool
Qt - An awesome cross-platform IDE
Vmware - For letting me test this tool on all platforms (Linux and MAC).
Icons8 - A nice platform for good-looking FREE icons. (Big thanks!)
UnixUtils - For the sed utility for Windows.
AndroidFileHost - For the awesome file-management platform for developers.​
Donations: ​Even though this tool is provided free of charge, full open-source, donations are very welcome to support the future development of this tool and to buy me a beer while coding future improvements on it.
This section will also include the hall of fame for donors, as well as on the github repository.
Special thanks for donations:
- @john7760
​
Disclaimer:​I will not be responsible for smashed screens, bricked phones or any other things that you can accuse me of, i've done this tool to help people, use it at your own risk and consider giving a THANKS if you use it and like it.​Please consider leaving some feedback, what to improve, what could be done better, what annoys you, it really helps me improve the tool.
Also, to avoid useless threads on general, Q&A or useless posts, please read the FAQ section upside, it's like a Mini-Guide!

Thanks!
I think there will be more people. Need to run a better window.
Windows7 64bit, part of the code.
Now, I have a simple editing of it.Make it look good.:laugh::laugh:
Download link:
https://mega.nz/#!nQBiDL7J!aDd9BhKtRw2tuYrpD7fImUXMn_Hl-qmUzwqKY13bYTc

Getting an error
FAILED(remote: oem unlock is not allowed)

Skies/SANKE said:
Thanks!
I think there will be more people. Need to run a better window.
Windows7 64bit, part of the code.
Now, I have a simple editing of it.Make it look good.:laugh::laugh:
Download link:
https://mega.nz/#!nQBiDL7J!aDd9BhKtRw2tuYrpD7fImUXMn_Hl-qmUzwqKY13bYTc
Click to expand...
Click to collapse
Well, I've looked at your edit and I don't understand what looks better than mine... It might be subjective though...
Pikezer1337 said:
Getting an error
FAILED(remote: oem unlock is not allowed)
Click to expand...
Click to collapse
Will investigate this problem and I hope I will get a solution fast
Edit: The information from this link might help with your problem.

I am running Arch Linux.
My shell is ZSH.
I downloaded and extracted, and ran zsh (filename).
I wanted to go with option 1 and got this
Code:
[= LG Nexus 5X - Multi Tool v0.1 - Linux =]
[1] Unlock bootloader. (via fastboot)
[2] Relock your bootloader. (via fastboot)
[3] Flash Recovery menu. (via fastboot)
[4] Backup and restore. (via adb)
[5] Recovery sideload. (via adb)
[r] Reboot menu.
[l] Logging menu.
[q] Quit.
Select your option:
1
menu:23: command not found: bootloader
127 [email protected] ~/Android/5XMultiTool.v0.1 % :(
any ideas?

paOol said:
I am running Arch Linux.
My shell is ZSH.
I downloaded and extracted, and ran zsh (filename).
I wanted to go with option 1 and got this
Code:
[= LG Nexus 5X - Multi Tool v0.1 - Linux =]
[1] Unlock bootloader. (via fastboot)
[2] Relock your bootloader. (via fastboot)
[3] Flash Recovery menu. (via fastboot)
[4] Backup and restore. (via adb)
[5] Recovery sideload. (via adb)
[r] Reboot menu.
[l] Logging menu.
[q] Quit.
Select your option:
1
menu:23: command not found: bootloader
127 [email protected] ~/Android/5XMultiTool.v0.1 % :(
any ideas?
Click to expand...
Click to collapse
The problem should be fixed in the V0.2, the Linux and MAC versions are not tested before posting, so bugs could still be around there...

added to index

Hi all, imusing linux and just tried to unlock my 5X. it worked but my question is, it is normal that it formated automatically?
after reboot, i have to start all over again with my account and setup.

Yes it's normal

Thanks mate, I'm new with nexus devices. One last thing, do I have to locked again or its OK leave it like that since on every reboot its showing me that I'm unlock. Sorry and thanks
Sent from my Nexus 5X using Tapatalk

You can leave it like that as long as you can deal with that message on every boot. If you lock it, you would have to unlock (and wipe) again if you ever want to flash anything again. Personally, unless you want to stick with the stock ROM OTAs, I'd leave it unlocked.

Would you confirm your Tools Re-Lock feature works with Custom Recovery (TWRP) without bricking device?

Born<ICs said:
Would you confirm your Tools Re-Lock feature works with Custom Recovery (TWRP) without bricking device?
Click to expand...
Click to collapse
Usually, locking your device does not brick anything, if everything works fine before locking, everything will work fine after locking, you are only limited after locking.

Lexmazter said:
Usually, locking your device does not brick anything, if everything works fine before locking, everything will work fine after locking, you are only limited after locking.
Click to expand...
Click to collapse
.
Would you mind answering the question?
With custom recovery, TWRP, installed and unlocked what happens when you use your Tool to go back to Lock?
Have you tested?
Thanks

Born<ICs said:
.
Would you mind answering the question?
With custom recovery, TWRP, installed and unlocked what happens when you use your Tool to go back to Lock?
Have you tested?
Thanks
Click to expand...
Click to collapse
To be honest I never locked my bootloader, didn't found a reason to, so I didn't tested.
But technically speaking, the only thing that happens is that you cannot flash other custom recoveries (fastboot stuff basically) without unlocking again and wiping all the stuff on your device.

OK, thank you. ReLocking to flash factory image was what I was thinking. I read doing so can lead to bootloop. Just trying to make note of things to avoid doing.
Cheers

You can lock and unlock your bootloader as much as your heart desires without consequence

skulldreamz said:
You can lock and unlock your bootloader as much as your heart desires without consequence
Click to expand...
Click to collapse
Well, wiping your data partition can be a pretty big consequence...
-edit-
You used to be able to use BootUnlocker for Nexus Devices to lock and unlock the bootloader from within the OS, but it looks like that's a no-go on the 5X...

I'm new to the nexus devices, but if I unlock the bootloader and root, will I loose both if I take an OTA update?

owenrg said:
I'm new to the nexus devices, but if I unlock the bootloader and root, will I loose both if I take an OTA update?
Click to expand...
Click to collapse
You will definitely lose root. I don't know about the bootloader since I've never taken an OTA, but I would guess that, unless there are bootloader changes in the update, your bootloader would stay unlocked. And to my knowledge the bootloaders are pretty much never updated for incremental OTAs.

Unbrick Honor 9 STF-L09 (NOT FREE, HCU and DC-Phoenix required)

Introduction
THIS METHOD IS NOT FREE. I HAVE NO IDEA HOW TO DO THIS FOR FREE, EXCEPT MAYBE WITH THIS : https://forum.dc-unlocker.com/forum/modems-and-phones/huawei/162196-free-hcu-license-offer
Oh my god. I just come out of 3 days of trying to get this to work, non-stop. I feel the need to write this guide so people in the exact same configuration as me won't have to go through what I did.
Yes there are many tutorials about unbricking your Honor 9, but few are very detailed, and I couldn't make them to work for my european STF-L09. Plus, very few of them have a solution for updating to the very latest version (9.1.0 as the time of writing). So here we go.
The device I did this with, and the situation I was in.
There are so many variants of the Honor 9, and I've tried tutorials that weren't the same model as me, they just wouldn't work.
Honor 9 STF-L09, Europe version, Kirin960.
Previous installed ROM before brick was Oreo (the Pie update I tried to make bricked the phone), but I think you can do that on any previous version.
After the brick, I had a completely dead Honor 9 : no reaction at all, whether I plugged it in or tried any buttons combination.
What you need
- The correct Drivers
- A HCU Client Timed License, which is 19 EUR for 72h, and is going to give you access to the main software we need, DC-Phoenix.
- The correct .dgtks Repair File
- The correct ROM file to flash
- HiSuite
- Tools to open the back of your phone
- A metal object to connect the testpoints (anything will do : tweezers, copper cable, paperclip, sim-tool...)
- Read these two tutorials from www.dc-unlocker.com :
https://www.dc-unlocker.com/dc-phoenix-flash-repair-tutorial
https://www.dc-unlocker.com/flash-bricked-huawei-phones-in-huawei-1-mode
Step 1 - Connect the testpoints
Then open the back of your phone to reveal the testpoints that you can see on the image below (thanks to the user 4r44444 for the picture).
Then, open the Device Manager on Windows, and reveal the COM and LPT Ports (so you can see if you failed at connecting the testpoints or not).
You don't need to connect the two testpoints shown in the picture : you only need to connect the bottom one with anything else that's metal inside the phone.
It will take you some trial and error but eventually, your Device Manager should refresh and show you an unknown device called "SER".
Step 2 - Install the drivers
First, install the latest version of HiSuite to get the basic drivers. Make sure to close it completely (taskbar) and disable the fact that it opens itself when you plug your phone, or it might screw things up.
Then, install the two drivers that are on both dc-unlocker.com tutorials I've linked above.
https://files.dc-unlocker.com/share.html?v=share/984CE114852148B5B9A9CDD918BEC235
https://files.dc-unlocker.com/share.html?v=share/18B15B9D02C945A79B1967234CECB423
The first one "Huawei_Android_phone_drivers.rar" was not useful for me, but the second one, "Huawei drivers testpoint.rar", is to make your COM port recognizable instead of this unknown "SER" in device manager.
In Device Manager, right click on "SER", "Update driver", and locate the extracted folder on your computer.
This is all you need I think, but I installed so many random drivers (which I would not recommend) that I'm not even sure anymore.
Step 3 - Repair the phone with DC-Phoenix
Following "Method 3" from this link, but with some differences : https://www.dc-unlocker.com/dc-phoenix-flash-repair-tutorial
As I said, this method is not free. You can buy credits to make DC-Phoenix work for 72 hours (you need 15 of them for that I think), but since we need HCU, you're better off buying a timed license which gives access to DC-Phoenix.
Open DC-Phoenix, and click on the "Download files" button on top. There, search for the file "STF-Full-Repair-NV-included-Board-A051-7.0.0_r1.dgtks" and download it, it's the Repair File.
https://get-file.org/search#q|STF-Full-Repair-NV-included-Board-A051-7.0.0_r1|1
With your phone connected via testpoints (it has to appear in the Device Manager in the COM Ports, and I recommend changing the COM Port to 1 (right click, Port settings, advanced,...)), go to the "Update OEMINFO" tab, and check "Use BOOTLOADER". There, choose "Kirin960_T2_A7.0_V4" (maybe it's a different one for you, but for me only this one worked).
Then check "Update OEMINFO and unlock Huawei ID", and choose "STF-L09". Click Update, and this should run without errors. If it doesn't recognize your device, that means that it's not turned off and connected via testpoints.
Once that is done, your device may show a sign of life by booting into fastboot mode (or sometimes not). Anyway, you can go directly to the "Update Firmware" tab, and in the "Update file" field, choose the file "STF-Full-Repair-NV-included-Board-A051-7.0.0_r1", check "Rescue Revovery" and "Old slow algo", and click "Update".
After completion, your phone should be able to boot (after a very long press) into a chinese test ROM.
Step 4 - Repair the phone infos with DCU
Follow this tutorial : http://hcu-client.com/huawei-phone-repair-as-empty-board/
Don't forget to change your phone to Manufactured mode (as explained) so you can read your phone info.
In the Step 4, they let you choose between Repair UMTS or CDMA tab, I chose CDMA because I think the phone has a MEID.
Then, when they tell you that you just have to click on "Repair as empty board" to make everything fill in automatically, for me this was complete bs : only my IMEIs were added.
So what you have to do is fill your original SN, WiFi and BT MAC adresses, and so on. But since your phone is bricked and you probably dumped the box that states the SN, you're outta luck like me. It seems like it's illegal to change a MAC or SN number, so I can't recommend it, but I personally just chose random numbers (that have the same number of digits).
For model I entered "STF-L09", for vendor "hw", and for country "eu". Don't check "Erase restricted ver.", since it's only for Qualcomm CPUs. Click on Repair.
Once this is done, your phone should be resetting, and able to boot in the same ROM as before, except in english.
Step 5 - Upgrade to the latest Android 9.1.0
Normally you'd have to do this step with DC-Phoenix : just flash one of their Full Stock Roms they have on their file database (click Download Files on DC-Phoenix, and search for "STF-L09").
You can try that (don't forget that you have to be in fastboot mode (Vol down + plug USB) to install), but it really didn't work for me, and even if it did, I don't know how you'd update after it, because your phone probably won't receive OTAs.
So the solution I found was this one : https://www.reddit.com/r/Huawei/comments/az4bl7/finally_managed_to_update_my_mate10_pro_to_pie/
First, uninstall your latest version of HiSuite to be able to follow this tutorial and install the old version.
Then, the file I chose in Firmware Finder was this one :
STF-L09 9.0.1.175(C432E2R1P5)
STF-L09C432E2R1P5B175 (9.0.1.175)
STF-L09C432E2R1P5T8B175 (9.0.1.175)
I chose the "full" version, which gave me this link :
http://update.dbankcdn.com/TDS/data/files/p3/s15/G3757/g1699/v260353/f1/full/update.zip
After following this tutorial, your phone should boot normally. You can then installs OTAs to update to 9.1.0. I'd recommend resetting the phone after this last step, to have a clean install.
If it doesn't work for you, you can also try this method : https://www.getdroidtips.com/full-guide-install-stock-firmware-huawei-smartphone/
I'll try to answer as many questions as fast as possible (since the Timed License is quite stressful), so feel free to ask !

Does the HCU Client unblock the network after doing the full repair?

Hello , Is this solution still works for honor 9 ?
I can't find stock rom on official website also.

[UPDATED GUIDE] [BOOTLOADER UNLOCK] Huawei p8 lite 2017 (pra-lx1)

This guide is the only one made and tested personally by me, I am not responsible for malfunctions or any damage to the device, carefully read every single step and everything will be successful
{
"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"
}
[ATTENTION]: Before proceeding, save all your data on your computer and REMOVE ANY KIND OF UNLOCKING (sequence, pin, fingerprint etc ..); remove the sim and the microSD; get a microSD, at least 3/4 giga, where you can upload the files necessary for the procedure.
[NECESSARY CONDITIONS]: Starting from emui 8; have the cell phone charged to 100%; bootloader unlocked and the only procedure I know and working is the one I propose in the guide, the code is obtained by paying 4 €/$, THERE ARE NO FREE ALTERNATIVES.
[PREREQUISITES]: Download -> HiSuite , Dc-Unlocker
At this point we create a folder on the desktop and we will call it ANDROID1O to have a reference point and we will extract the folder contained in the dc-unlocker archive. Once the folder has been extracted, install adb and fastboot in order. At this point we can also install HiSuite.
[PROCEDURE]
[DOWNGRADE] In
order for dc-unlocker to read the bootloader code it is necessary to go back to an older version of android, so let's proceed as follows:
(1) We connect the mobile phone to the computer and start HiSuite, in some cases it will start automatically, and we follow the procedure that will be shown to us to enable debugging. If you have followed everything correctly HiSuite will read your device without problems.
(2) Remaining on HiSuite, click on the UPDATE SYSTEM item, a window will appear, at this point we can press on PREVIOUS VERSION (now I don't remember the precise wording) and we can start the downgrade. It will take a while.
(3) At the end of the downgrade we can start the mobile phone by skipping and ignoring the various configurations by putting the language in Italian as a matter of practicality, let's move on to the next step
[GET BOOTLOADER CODE]
(1) We go to the system settings ---> information ----> we do many taps until the message "now you are a developer" appears ----> we go back ----> developer options and activate usb debugging.
(2) Let's go to HiSuite and in the settings located at the top right we remove the check mark under "Start when it connects to the device" and close it.
(3) We buy the credits to read the bootloader code from https://www.dc-unlocker.com/buy in this way:
- We select the payment method
- We leave "new user account"
- We enter a username that we like it
- We enter an e-mail address to which we can easily access, here we will be sent the credentials to be able to access dc-ulocker
- We enter 4 in the credits box and then type on confirm
- If everything went well, the screen will appear with the credentials and you will receive a copy on the email
(We now have the necessary credits to be able to read the unlock code)
(4) Let's go back to the folder created on the desktop and start dc-unlocker and clicking on the SERVER item we enter the credentials obtained on the site
(5) At this point in the drop-down at the top left we look for the item HUAWEI PHONES
(6) A guide will appear that in any case I will report here:
- In the call keypad type the following combination * # * # 2846579 # * # *
- Press on MANUFACTURE MODE
(7) We can connect the mobile phone and press on the magnifying glass we see on dc-unlocker and if we have done everything correctly the program it will detect our mobile phone
(8) When the phone has been recognized we go to the UNLOCKING section and press on READ BOOTLOADER CODE, if we have done everything correctly we will get a code that we will enter somewhere so as not to lose it, we will need it later
(I leave you the video dc-unlocker official guide on how to unlock bootloader if you have any doubts ---> Help
(9) We disconnect the mobile phone from the computer
(10) After writing down the bootloader code we can close dc-unlocker, connect the mobile phone to a wifi network and search for system updates to return to the latest version of android and therefore to emui8,
if no updates appear, we try to force them by going to settings, wifi, press and hold on the wifi to which we are connected, modify, check advanced options, press on proxy, manual,
in proxy hostname we write localhost and in the port we write 8080 , we press on connect and if we return to the updates item it should find the most recent version. At this point we can update the mobile phone to the most recent version.
[BOOTLOADER UNLOCK]
(1) After returning to the most recent version of android we turn on the mobile phone
(2) We go to the system settings ---> information ----> do many taps until the message "you are now a developer "----> go back ----> developer options and activate the usb debug and the active voice unlock manufacturer
(3) We connect the mobile phone to the computer, press on transfer files, go back to the developer settings and activate the debug , at this point the mobile will ask us to give permissions to our computer and we confirm
(4) Let's go back to the desktop and at the top right click on file, open windows powershell, open windows poweshell as administrator and click on yes
(5) We type the command "adb devices" (write it without quotes), we wait for the end of the 'execution of the command and type again the command "adb devices" (without quotes)
and so we will see a number that corresponds to our mobile phone
(6) We give the command "adb reboot bootloader" (without quotes) and we send
(7) The mobile phone will start in a white screen with an android, the important thing is that two written in red appear with the words PHONE Unlocked and FRP Unlock
(8) From the Widows poweshell screen opened previously we give the command "fastboot oem unlock CODICEBOOTLOADER" (without quotation marks) (CODICEBOOTLOADER refers to the code obtained with Dc-Unlocker) and press on
enter (9) On the cellualre a warning will appear, press once the volume up key and then the power key to confirm the unlocking of the bootloader
(10) When the procedure is finished, it will take very little time, we give the command "fastboot reboot" (without quotes) and when the mobile phone screen it will go black we unplug it
(11) The cellualre will restart a couple of times with a white and other yellow writing, let it go, it will be returned to the factory settings and we will just have to skip all the configuration procedures but set the language in Italian
Finally the bootloader is unlocked!

Here's a free way https://github.com/SkyEmie/huawei-honor-unlock-bootloader

JanoRasho13 said:
Here's a free way https://github.com/SkyEmie/huawei-honor-unlock-bootloader
Click to expand...
Click to collapse
You try this?

pitrazzu said:
You try this?
Click to expand...
Click to collapse
I didn't, but a friend of mine with p20 lite succeeded unlocking!

JanoRasho13 said:
I didn't, but a friend of mine with p20 lite succeeded unlocking!
Click to expand...
Click to collapse
Knowing this sooner I would do it with this tool. Anyway good to knoe but I don't think I would stay with Huawei brand due to their anti-community mods policy.

DunoCZ said:
Knowing this sooner I would do it with this tool. Anyway good to knoe but I don't think I would stay with Huawei brand due to their anti-community mods policy.
Click to expand...
Click to collapse
Yes, absolutelly. Why you prevent me to mod my phone if the phone is mine?

Here is a free alternative to DC-UNLOCKER
I've unlocked the bootloader and installed TWRP on my wife's phone (emui 8 up to date dec 2020)
Here is the program : Potato NV
Follow these instructions : PotatoNV - wiki
To find where the testpoint is located search for pralx1 STF testpoint on your favourite internet search engine.
PS : By the way, the understanding of how it works goes way beyond my technical skills...

Junkilito said:
Here is a free alternative to DC-UNLOCKER
I've unlocked the bootloader and installed TWRP on my wife's phone (emui 8 up to date dec 2020)
Here is the program : Potato NV
Follow these instructions : PotatoNV - wiki
To find where the testpoint is located search for pralx1 STF testpoint on your favourite internet search engine.
PS : By the way, the understanding of how it works goes way beyond my technical skills...
Click to expand...
Click to collapse
And that means I no longer need to downgrade?

gabefufezan said:
And that means I no longer need to downgrade?
Click to expand...
Click to collapse
I didn't need to downgrade. I've just downgraded after the unlock via dload in order to install Android 11 Rom.

JanoRasho13 said:
Here's a free way https://github.com/SkyEmie/huawei-honor-unlock-bootloader
Click to expand...
Click to collapse
I want to try this way. Did it work for you guys?

This is supossed to happen, right?

gabefufezan said:
View attachment 5273573This is supossed to happen, right?
Click to expand...
Click to collapse
It's almost impossible to find it randomly. There are too many combinations...
If you read the issue section of this git, you'll see it by yourself.

Junkilito said:
It's almost impossible to find it randomly. There are too many combinations...
If you read the issue section of this git, you'll see it by yourself.
Click to expand...
Click to collapse
So that means the tool is unefficient?

gabefufezan said:
So that means the tool is unefficient?
Click to expand...
Click to collapse
I think so.

gabefufezan said:
So that means the tool is unefficient?
Click to expand...
Click to collapse
I tried but It didn't work. Unfortunately I had an aplhanumeric code despite that my device was european, and this made impossible the task to find the code ( it would take millions of years to do a minimum percentage of combinations ).
I found it using PotatoNV, it adds the difficult part to disassemble the phone but it is very efficient.

gabefufezan said:
View attachment 5273573This is supossed to happen, right?
Click to expand...
Click to collapse
It is not supposed to happen this way. You have to see something like "fastboot error: wrong password", so you're probably missing some permissions.
Anyway unless you have a numeric code there is virtually zero chance to find it in that way.
In my case I ran the script and in ~4 hours it tried all the numeric codes supposed to fit with my imei, but with no success. Later I discovered that my code was alphanumeric.

Hi everyone, I've just obtained te bootloader code, but now I'm stuck on EMUI 5.0.3, there are no updates available.
I tried forcing it but nothing changes..

On my P8 Lite 2017, I've tried the PotatoNV method which is, in fact, very easy (the most difficult part was to open the back cover, but with an opening tool it's easier) and no need to downgrade. For me the SkyEmie method was just a waste of time.

pitrazzu said:
(10) After writing down the bootloader code we can close dc-unlocker, connect the mobile phone to a wifi network and search for system updates to return to the latest version of android and therefore to emui8,
if no updates appear, we try to force them by going to settings, wifi, press and hold on the wifi to which we are connected, modify, check advanced options, press on proxy, manual,
in proxy hostname we write localhost and in the port we write 8080 , we press on connect and if we return to the updates item it should find the most recent version. At this point we can update the mobile phone to the most recent version.
Click to expand...
Click to collapse
Hello, i'm stuck at this step, i'm back at EMUI 5.0.3 and when i check for update it tells me "no updates"

Worked for me (PRA-LX1) !!
So easy, except from potatoNV (didn't try back panel is broken, as a result I cannot open my phone) all other free solutions have not worked for me.

How To Guide [TB-J706F] [ROM] ZUI 12.6 Offline easy install

Hello TB-J706F (aka XiaoXin Pad Pro) users !
Latest ZUI ROM cannot be found in the file repositories and on the Lenovo support site. However, you can download the initial version of ZUI for our tablet and update to the latest ZUI 12.6, getting 4 updates. However, in fact, we only need two of them. I kindly saved them for you and included in my superpack along with the necessary software.
Link: https://cloud.mail.ru/public/DHTp/9dm4g5e13
Second link: https://drive.google.com/file/d/1ELq8YIU1FRL_4OX5RSWba9m2korSRDxD
The archive contains all necessary soft:
Spoiler
{
"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"
}
Adb & fastboot, lenovo USB drivers, flasher QPRST and detailed instructions (English) in pictures how to install QPRST and flash the initial ZUI - All-in-One. There are two updates in the folder OTA:
1update.zip - updates ZUI to v. 12.5 (first A 11 version);
2update.zip - updates ZUI 12.5 to 12.6 latest at this moment.
ZUI first ROM can be downloaded from here: https://mirrors.lolinet.com/firmware/lenovo/Tab_P11_Pro/TB-J706F/ - TB-J706F_CN_WIFI_USER_Q00018.0_Q_ZUI_12.0.335_ST_201103_qpst.zip
Attention !!! The first thing you must do is to make sure that your parameter in NV item 6858 is 01 or 00, otherwise the ZUI A11 will not boot (A10 can). How to do this, look guide: https://forum.xda-developers.com/t/check-region-unlock-p11-tb-j606f-l-n.4356451/ That guide advises also change country code, I have CN (China), it can be changed after first ZUI flashing, code ####6030# in Settings -- Search bar on top.
=== Manual ===​1. According to the pdf guide, flash the downloaded ZUI ROM. Boot, minimal offline initial settings, and you can see Desktop screen. If you need change region code to CN - go to Settings, insert ####6030#, маке choise from one point CN or PRC (People Republic China). This will reboot and clear the user's data (factory reset). Now you need to go to settings, become a developer, enable USB debugging. Also you need set right data (day, month and year).
2. On PC: unpack Adb Tools in folder, place 1update.zip & 2update.zip inside adb tools folder. Run the Command Prompt, check connect to device and command the tablet:
adb reboot recovery
In tablet's recovery select Apply update from ADB and on PC run command adb sideload 1update.zip. Wait for update process completion, then reboot into the system, patiently wait for the booting to complete. Now you have ZUI 12.5 on tablet.
3. Repeat the previous step using 2update.zip - adb sideload 2update.zip. Wait for completion, then reboot into the system.
Now you have latest ZUI 12.6 !
The ZUI looks much prettier, more comfortable and sleeker than the poor global firmware, and has more features.
P.S. The video shows the firmware process of changing NV item 6858 in the hex editor to install the ZUI, only for the younger version of the tablet. The process is the same for the P11 Pro.
Spoiler: Korean language
​

Thank you for this!
May I request for the update files? The link you provided is not working. Thanks!

o97601 said:
Thank you for this!
May I request for the update files? The link you provided is not working. Thanks!
Click to expand...
Click to collapse
Hi ! Checked it moment ago, link working: https://cloud.mail.ru/public/DHTp/9dm4g5e13
Spoiler

d1m-ON said:
Hi ! Checked it moment ago, link working: https://cloud.mail.ru/public/DHTp/9dm4g5e13
Spoiler
View attachment 5484189
Click to expand...
Click to collapse
Thank you but I think my location is not letting me to download the file. I have a problem though. I was trying to change the region code but the QFIL is not letting me to backup my QCN. I can't click the button. On the other hand, when I am using the NV Read and Writer, my phone is not communicating to it. Any help?

I don't think you should do it, it's too complicated for you. You can't even download my file via VPN and connect the tablet properly
Another link: https://drive.google.com/file/d/1ELq8YIU1FRL_4OX5RSWba9m2korSRDxD
P.S. You need flash ZUI from lolinet first, and second is connect tablet in DIAG mode, then backup .qcn and restore edited .qcn

I'm done backing up the QCN. But unfortunately, I cant find the hex code that it requires. I cut my chase and just stay with 12.5 for the mean time. Thank you!

After updating I get this screen and I can't do anything else.
Yes, I followed the instructions to the letter

Just flashed again to the original ROM.

d1m-ON said:
Hello TB-J706F (aka XiaoXin Pad Pro) users !
Latest ZUI ROM cannot be found in the file repositories and on the Lenovo support site. However, you can download the initial version of ZUI for our tablet and update to the latest ZUI 12.6, getting 4 updates. However, in fact, we only need two of them. I kindly saved them for you and included in my superpack along with the necessary software.
Link: https://cloud.mail.ru/public/DHTp/9dm4g5e13
Second link: https://drive.google.com/file/d/1ELq8YIU1FRL_4OX5RSWba9m2korSRDxD
The archive contains all necessary soft:
Spoiler
View attachment 5480323
Adb & fastboot, lenovo USB drivers, flasher QPRST and detailed instructions (English) in pictures how to install QPRST and flash the initial ZUI - All-in-One. There are two updates in the folder OTA:
1update.zip - updates ZUI to v. 12.5 (first A 11 version);
2update.zip - updates ZUI 12.5 to 12.6 latest at this moment.
ZUI first ROM can be downloaded from here: https://mirrors.lolinet.com/firmware/lenovo/Tab_P11_Pro/TB-J706F/ - TB-J706F_CN_WIFI_USER_Q00018.0_Q_ZUI_12.0.335_ST_201103_qpst.zip
Attention !!! The first thing you must do is to make sure that your parameter in NV item 6858 is 01 or 00, otherwise the ZUI A11 will not boot (A10 can). How to do this, look guide: https://forum.xda-developers.com/t/check-region-unlock-p11-tb-j606f-l-n.4356451/ That guide advises also change country code, I have CN (China), it can be changed after first ZUI flashing, code ####6030# in Settings -- Search bar on top.
=== Manual ===​1. According to the pdf guide, flash the downloaded ZUI ROM. Boot, minimal offline initial settings, and you can see Desktop screen. If you need change region code to CN - go to Settings, insert ####6030#, маке choise from one point CN or PRC (People Republic China). This will reboot and clear the user's data (factory reset). Now you need to go to settings, become a developer, enable USB debugging. Also you need set right data (day, month and year).
2. On PC: unpack Adb Tools in folder, place 1update.zip & 2update.zip inside adb tools folder. Run the Command Prompt, check connect to device and command the tablet:
adb reboot recovery
In tablet's recovery select Apply update from ADB and on PC run command adb sideload 1update.zip. Wait for update process completion, then reboot into the system, patiently wait for the booting to complete. Now you have ZUI 12.5 on tablet.
3. Repeat the previous step using 2update.zip - adb sideload 2update.zip. Wait for completion, then reboot into the system.
Now you have latest ZUI 12.6 !
The ZUI looks much prettier, more comfortable and sleeker than the poor global firmware, and has more features.
​
Click to expand...
Click to collapse
can i flash from row to zui 12.6?

Finally! Thank you!

datntien said:
can i flash from row to zui 12.6?
Click to expand...
Click to collapse
Yes! Just follow the tutorial

o97601 said:
Finally! Thank you!
Click to expand...
Click to collapse
Congrats! You are great!

datntien said:
can i flash from row to zui 12.6?
Click to expand...
Click to collapse
Sure, no problems.
Video added:
Spoiler: Korean language

d1m-ON said:
Congrats! You are great!
Click to expand...
Click to collapse
May I know where did you get the files in OTA? I am searching if there is already an update for zui 13.

o97601 said:
May I know where did you get the files in OTA? I am searching if there is already an update for zui 13.
Click to expand...
Click to collapse
I have been getting updates to my tablet via Wi-Fi and after downloading (before installing) I save the update file to the microSD. The update files arrive on the device in the .Zuiota folder (hidden folder).

Thanks for the guide. I have succeed and now I am running ZUI 12.6. I did the updates OTA instead using adb. I setted the internal country code to 00, I had ROW rom before and the code was 02. I used GFil and was straightforward. If you decide to stay with ROW rom I recommend change the setting ####6030# to any country but CN, because doing this the Play Store became certified and NetFlix can be installed from Play Store.

blagoon52 said:
Thanks for the guide. I have succeed and now I am running ZUI 12.6. I did the updates OTA instead using adb. I setted the internal country code to 00, I had ROW rom before and the code was 02. I used GFil and was straightforward. If you decide to stay with ROW rom I recommend change the setting ####6030# to any country but CN, because doing this the Play Store became certified and NetFlix can be installed from Play Store.
View attachment 5498519
Click to expand...
Click to collapse
This is great. I already have 12.6.133 for the longest time and haven't been able to receive another update in OTA. I don't know if it is capable or not.

tenthofmay said:
This is great. I already have 12.6.133 for the longest time and haven't been able to receive another update in OTA. I don't know if it is capable or not.
Click to expand...
Click to collapse
Seems that there is an update to Zui 13 for the Pad Pro, so I will confirm if I can get it through OTA.

d1m-ON said:
Hello TB-J706F (aka XiaoXin Pad Pro) users !
Latest ZUI ROM cannot be found in the file repositories and on the Lenovo support site. However, you can download the initial version of ZUI for our tablet and update to the latest ZUI 12.6, getting 4 updates. However, in fact, we only need two of them. I kindly saved them for you and included in my superpack along with the necessary software.
Link: https://cloud.mail.ru/public/DHTp/9dm4g5e13
Second link: https://drive.google.com/file/d/1ELq8YIU1FRL_4OX5RSWba9m2korSRDxD
The archive contains all necessary soft:
​
Click to expand...
Click to collapse
!!! No more need !!! Latest ROM is here: https://forum.xda-developers.com/t/lenovo-tb-j706f-zui-12-6-133.4383047/

tenthofmay said:
but the QFIL is not letting me to backup my QCN. I can't click the button
Click to expand...
Click to collapse
I have the same problem. Why don't you share your solution?
Edit: solved by running "qpst configuration" application, adding the device (second tab), right-click and click "switch to diagnostic mode" or something like that.
Then rebooted the device to FFBM mode.

How To Guide [TB132FU-Mediatek Kompanio 1300T] Convert from Chinese to Global

NEW: Install official Global ROM on Chinese TB132FU running ZUI 14 or Fake global​DISCLAMER: Flashing on TB132FU is pretty much safe and a hard brick has not occured yet, but do it at your own risk. If anything goes wrong you can return to ZUI 14 using one of the restoration methods listed on the FAQ thread. ALL YOUR FILES WILL BE DELETED. Make a backup of your personal files before proceeding.
Did my work help you? Be free to buy me a coffee. PayPal me at @alsbvg​
Current version: TB132FU_S000094_221117_ROW
To see what works and what doesn't check below.
To flash this version you will need:
1 - A computer running Windows
2 - Flashtool (attached to the thread)
3 - ADB drivers or UsbDk drives & MTK drivers
4 - ZUI 14 installed on your TB132FU. If you have fake global you can flash as well, but having ZUI is recommended.
5 - Firmware file
6 - Attention to the really detailed tutorial below.
How to flash
Preparation:
1 - Download and install the drivers provided above. If you already have them installed skip this step.
2 - On your computer create a folder on your Desktop. Name it LENOVO.
3 - Download the firmware file (download link provided above) and un-zip it inside the LENOVO folder on your desktop. So inside your LENOVO folder now you should have a folder called TB132FU_S000094 Global.
4 - Download the attached flash tool and un-zip it inside the LENOVO folder on your desktop. Now you have a folder called TB132FU_S000094 Global and a folder called MTK_Flashtool.
5 - Power off your TB132FU and disconnect it from your computer in case you have it connected.
Flashing:
1 - Go to the LENOVO folder, and open the folder MTK-Flashtool. Inside this folder find flash_tool and double-click to open it.
2 - Once it opens click the TAB download. Do not click the green arrow.
3 - For the Download agent click Choose. Navigate to your Desktop > Lenovo > MT_Flashtool and select the file MTK_AllInOne_DA_onyx_signed
4- For Scatter-loading file click Choose. Navigate to your Desktop > Lenovo > TB132FU_S000094 Global and select MT6893_Android_scatter.txt. You will see two files with the same name. Click the one with the paper with lines icon. Wait for it to load.
5 - For Authentication File click Choose. Navigate to your Desktop > Lenovo > MT_Flashtool and select the file auth_sv5
6 - You will see white and green lines below. Scroll down and find the line that starts with lk_a and UNMARK it. All the other options should be marked, only lk_a should be unmarked.
Ex:
{
"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"
}
7 - Click the green arrow DOWNLOAD and plug in your tablet. Wait until it completes flashing the firmware.
And done. Once it is finished you can unplug your tablet and turn it on. You now should be running the latest global rom on your TB132FU;
What works:
Google Sync
HDR with true black
Productivity mode (PC mode)
And almost everything else. I'm still testing it.
What doesn't work:
OTA - once a new update is available it will be needed to be flashed manually losing all data. OTA did not work on a previous version.
Ultra-fast charging. It has Rapid charge but not the super fast charging available on ZUI
Some users reported L1 when flashing this global.
For users who lost L1 status, no solution to get it back from L3 yet. :/
"Scroll to the left" on the home screen to access the media center will not turn off even if you try manually setting it as off.
Time-zone issue: Factory reset it after the first boot to get it fixed.
You tell me what else is not working.

Thanks for the detailed explanation.
Some cuestions that you may have an answer for:
1. Has the bootloader to be unlock? What happens if I have the bootloader lock? (I lock mine with zui 14 in order to get L1)
2. Is there a way to change region code like in others lenovo models? Will it have any impact on OTAs?
3. Can you rollback to zui 14?
Thanks in advance. I think that will be able to have a full working rom with OTAs and L1 eventually. This is a huge step forward

als_bvg said:
What doesn't work:
Ultra fast charging. It has Rapidy charge but not the super fast charging available on ZUI
Click to expand...
Click to collapse
Out of curiosity, does the Chinese model have an Ultra fast charging?
My Global P11 Pro gen 2 does Rapid charge and my cable display caps out at 10w which I wouldn't say is rapid...
Same cable and charger gives me much faster speeds on my Galaxy S22U.

Pawnty said:
Out of curiosity, does the Chinese model have an Ultra fast charging?
My Global P11 Pro gen 2 does Rapid charge and my cable display caps out at 10w which I wouldn't say is rapid...
Same cable and charger gives me much faster speeds on my Galaxy S22U.
Click to expand...
Click to collapse
It does. The Chinese running ZUI has Ultra-fast charging with the original cable and charger.

tylerdanarg said:
Thanks for the detailed explanation.
Some cuestions that you may have an answer for:
1. Has the bootloader to be unlock? What happens if I have the bootloader lock? (I lock mine with zui 14 in order to get L1)
2. Is there a way to change region code like in others lenovo models? Will it have any impact on OTAs?
3. Can you rollback to zui 14?
Thanks in advance. I think that will be able to have a full working rom with OTAs and L1 eventually. This is a huge step forward
Click to expand...
Click to collapse
1 - You don't need the bootloader to be unlocked to flash this global version. I had Zui 14 with a locked bootloader and OEM locked, and the flashing worked. The OEM toggle will not be available once you use this version. It says you need to connect to the internet or contact your carrier.
2 - No way to change the region code so far. OTA will not work as described. It was tested on an older version. It will download and try to install but will fail. This is the latest rom so no OTA updates so far, we will have to wait to see if it will be the same.
3 - Yes, you can roll back to Zui 14. I did that quite a few times during my tests. Bricked the device more than 20 times and was always able to roll back to ZUI.

Thank you so much!
Generating User Accounts is working too? Wanted to use the tablet for the family, but ZUI doesn't offer accounts and Google Family doesn't work.

Hi. Thank you very much for the excellent work! Testing, so far so good. Do I have an L1 or am I misunderstanding something? Screenshot attached.

Thanks for the great work you do.
We have successfully implemented the global implementation.
My tablet is formatted with the SP Flash Tool. The serial number was lost at that time. (When I looked in the settings, the serial number was 0123456789ABCDEF.)
The serial number itself was recovered by rewriting the proinfo.bin. I think this formatting probably caused the Widevine-related settings to disappear and become L3.
I ask other L3 users, did you format with SP Flash Tool or python?

Flash mine today from ZUI 14 with bootloader lock, L1 and Google Play Certified to Global ROM and I kept L1, Google Certified Device and everything Is working. Even fast charging.
Thanks a lot! Let's see what happens when an OTA Will be available.

Hanswurstistda said:
Thank you so much!
Generating User Accounts is working too? Wanted to use the tablet for the family, but ZUI doesn't offer accounts and Google Family doesn't work.
Click to expand...
Click to collapse
I bought it for my daughter to use and have Family link for her Google Account and its all kinds of wonky (it shows my daughters account under Accounts then it vanishes. the only way I can add it back in is by signing into the Play store but then after an hour or so it goes. Works fine with my google account. Damn Family Link!)
(its on 14.0.413, and has an update pending for 14.0.640 ST). Not a clue how to check if its a modified ROM or what, but was going to try the above and see how it gets on.

Just to clarify fast charging Is shown on the screen but I don't if it's 10w ir 30w. I Will do some measures today and keep you posted

tylerdanarg said:
Just to clarify fast charging Is shown on the screen but I don't if it's 10w ir 30w. I Will do some measures today and keep you posted
Click to expand...
Click to collapse
Try the AccuBattery app, it may not be accurate, but it shows the charging current. I don't want to charge it yet. I will first discharge it and then install this app and start charging. It's convenient because it shows time to charge up to 100%.

daybreak7456 said:
Thanks for the great work you do.
We have successfully implemented the global implementation.
My tablet is formatted with the SP Flash Tool. The serial number was lost at that time. (When I looked in the settings, the serial number was 0123456789ABCDEF.)
The serial number itself was recovered by rewriting the proinfo.bin. I think this formatting probably caused the Widevine-related settings to disappear and become L3.
I ask other L3 users, did you format with SP Flash Tool or python?
Click to expand...
Click to collapse
Thanks for your input. I formated it before using the option "format + download" and serial number is now 012345678ABCDEF. I can try doing what you did with the file proinfo.bin. Any specific tutorial you used?

GeesRiK said:
I bought it for my daughter to use and have Family link for her Google Account and its all kinds of wonky (it shows my daughters account under Accounts then it vanishes. the only way I can add it back in is by signing into the Play store but then after an hour or so it goes. Works fine with my google account. Damn Family Link!)
(its on 14.0.413, and has an update pending for 14.0.640 ST). Not a clue how to check if its a modified ROM or what, but was going to try the above and see how it gets on.
Click to expand...
Click to collapse
Go to your settings menu. If you see the word ZUI anywhere, it's the Chinese model and you can flash the global if you want.

als_bvg said:
Go to your settings menu. If you see the word ZUI anywhere, it's the Chinese model and you can flash the global if you want.
Click to expand...
Click to collapse
Thanks! Yep, I have ZUI! I think its the family link attached to my daughters Google account that makes it annoying, but can't see any down sides in going to the Global to be honest. Can't get any worse... can it?!

GeesRiK said:
Thanks! Yep, I have ZUI! I think its the family link attached to my daughters Google account that makes it annoying, but can't see any down sides in going to the Global to be honest. Can't get any worse... can it?!
Click to expand...
Click to collapse
It shouldn't get any worse lol, but if your daughter is a kid you might benefit of a global rom, it has Kids space and the possibility of creating multiple users.

Awesome! Big thanks.

als_bvg said:
Thanks for your input. I formated it before using the option "format + download" and serial number is now 012345678ABCDEF. I can try doing what you did with the file proinfo.bin. Any specific tutorial you used?
Click to expand...
Click to collapse
What I did.
Install Python and mtkclient on a windows 10 computer.
python mtk rl --skip userdata "Destination path"
Backup everything but the user data with the above command
Open the backed up proinfo.bin with HxD and rewrite the serial number at the beginning.
python mtk wl "Destination path"
Flash the rewritten proinfo.bin with the above command.
GitHub - bkerler/mtkclient: MTK reverse engineering and flash tool
MTK reverse engineering and flash tool. Contribute to bkerler/mtkclient development by creating an account on GitHub.
github.com
Please check the commands and other information on the website.
I used to be able to do this, but I just tried it with a globalised tablet and it didn't work: the BROM mode (press power and volume plus simultaneously to connect the cable) is difficult to connect and even if it does, an error message appears and the process stops. When I get more time, I will switch back to zui14 and give it a try.

daybreak7456 said:
What I did.
Install Python and mtkclient on a windows 10 computer.
python mtk rl --skip userdata "Destination path"
Backup everything but the user data with the above command
Open the backed up proinfo.bin with HxD and rewrite the serial number at the beginning.
python mtk wl "Destination path"
Flash the rewritten proinfo.bin with the above command.
GitHub - bkerler/mtkclient: MTK reverse engineering and flash tool
MTK reverse engineering and flash tool. Contribute to bkerler/mtkclient development by creating an account on GitHub.
github.com
Please check the commands and other information on the website.
I used to be able to do this, but I just tried it with a globalised tablet and it didn't work: the BROM mode (press power and volume plus simultaneously to connect the cable) is difficult to connect and even if it does, an error message appears and the process stops. When I get more time, I will switch back to zui14 and give it a try.
Click to expand...
Click to collapse
Nice one! I can test it tomorrow. It's actually easier to pull the proinfo.bin file using MTK META Utility by using option Dump NV region. I was able to get and edit the file. Not sure how to flash it again on ZUI with a unlocked bootloader. But that's a start. I managed to get another Serial number by flashing another user's backup, but I still have L3, so might not be connected. I'll keep trying.

als_bvg said:
Nice one! I can test it tomorrow. It's actually easier to pull the proinfo.bin file using MTK META Utility by using option Dump NV region. I was able to get and edit the file. Not sure how to flash it again on ZUI with a unlocked bootloader. But that's a start. I managed to get another Serial number by flashing another user's backup, but I still have L3, so might not be connected. I'll keep trying.
Click to expand...
Click to collapse
I actually managed to get it back by flashing the edited proinfo.bin file using this command on ZUI with unlocked bootloader and OEM unlocked: fastboot flash proinfo proinfo.bin
Now let's see if it impacts or not L3. Testing...