Database Info

[ROM][6.0.1][CM13][UNOFFICIAL] Cyanogenmod 13 for Lenovo A760

DISCLAIMER: I do not own/build this ROM, This is not my work. I am posting this thread to help other Lenovo A760 users.
How to Install CM13 (Cyanogenmod 13) UNOFFICIAL 6.0.1 Marshmallow on Lenovo A760​
***** Android Rooting/Modifying Disclaimer *****
You are making these modifications to your device. I am not responsible for whatever happens to your phone, shall this process fail. You understand that I cannot be held responsible if you do not follow directions and brick your device. You are the only person responsible if you brick your device, as you are the one choosing to modify your device. You are voiding your warranty by rooting, making modifications, and install custom roms. I encourage you to READ CAREFULLY before following along and continuing to void your warranty. A fair knowledge of ADB and ROM flashing might be needed . You have been warned! Not following directions CAN result in a soft or hard brick. Thank you for if you read all of this!
Screenshots:​
{
"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"
}
Known Bugs:​
- No FM Radio
- Screen Recorder app causing phone to reboot (please do not use the app)
(All the links for download will be available at the end of these steps)
Step 1
Download cm-13.0-20160502-UNOFFICIAL-audi.zip and A-GAPPS 6.0.1.zip and save it under root directory in your phone's SD Card.
WARNING!! Step 4 to Step 9 will erase your Internal Storage. PLEASE BACKUP of all your files in Internal Storage (NOT SD Card) before proceed further!!
Step 2
Download the Qualcomm QPST zip, and install it on your Computer. (You may restart the computer after finished installation to make sure the driver is in effect)
Step 3
Power off your phone, take the battery out. Connect it with USB cable to the computer.
Step 4
Press & Hold (Vol +), (Vol -) & (Power Button) while its connected to your computer until you feel its vibrate 2x times. (check at the computer taskbar and see if device called Qualcomm CDMA Technologies MSM connected) DO NOT press FORMAT/ERASE drive if your computer prompt it. Just click cancel if the message appear.
Step 5
Download the HDD Raw Copy Tool and double click it to execute the application. You can now see 'Qualcomm MMC Storage' shown in the software.
Step 6
Download Lenovo_A760.imgc. Under the 'Qualcomm MMC Storage' line, there is another 'FILE' line, double click the line and select your downloaded Lenovo_A760.imgc
Step 7
Once your Lenovo_A760.imgc selected, it will display 'Please select TARGET' message. Click the 'Qualcomm MMC Storage' line and click the Continue>> button
Step 8
Click START and confirm to continue the process. This will take up to 20minutes.
Step 9
Once it shows 100% complete, you may remove the phone from USB cable, and insert back the battery. DO NOT power it on yet.
Step 10
Press & Hold (Vol +), (Vol -) & (Power Button) to go to Recovery Mode. Once you are in TWRP recovery, press ‘Wipe’, and swipe to proceed wipe/factory reset.
Step 11
Press 'Install' and select your cm-13.0-20160502-UNOFFICIAL-audi.zip.
Swipe to Install your zip. Press ‘Reboot system’ at the bottom.
Voila! you will be greeted with Cyanogenmod Boot Animation. Please proceed with the necessary steps to setup your phone for first time.
Step 13
Once booted up, go to Settings, scroll down until ‘About phone’. Tap on ‘Build Number’ for few times until a message appear: ‘You have enabled development settings!’.
Step 14
Go back once, and tap on ‘Developer options’. Turn on ‘Advanced reboot’ in Developer options, and scroll down a bit to set ‘Root access’ to ‘Apps and ADB’.
The following steps are only for those of you who want to install Google Apps:
Step 15
Press & Hold the Power button, select Reboot, and then select ‘Recovery’
Step 16
In the Recovery, press 'Install' and select your A-GAPPS 6.0.1.zip. Swipe to Install your zip. Once finished, just Press the ‘Wipe dalvik/cache’ button at bottom. After that, press ‘Reboot system’ again.
If your google Contacts does not sync, download the 'Google Contact Sync 6.0.1' apk and install & replace the current version in your phone.
Click to expand...
Click to collapse
If you are facing the ‘Unfortunately Setup Wizard Has Stopped’ or ‘Unfortunately Google Play Services Has Stopped’ errors, you may follow this steps:
For Setup Wizard, go settings, scroll down to ‘Memory’ > ‘Memory used by apps’ > ‘Setup Wizard’ > (Press i in the circle) > ‘Permissions’ > Turn on the options for ‘Contacts’ & “Phone’
For Google Play services, go settings, scroll down to ‘Memory’ > ‘Memory used by apps’ > ‘Google Play services’ > (Press i in the circle) > ‘Permissions’ > Turn on all the options
Download links
Qualcomm QPST: http://www.x-drivers.com/catalog/flash/mobile_phones/companies/qualcomm/models/qpst/12051
HDD Raw Copy Tool: http://viid.me/q0YITi
Lenovo_A760.imgc: http://viid.me/q0YH1w
Download CM13 Unofficial: http://viid.me/q0I8UI
Google Apps for Android 6.0: http://viid.me/q0I6nC
Google Contact Sync 6.0.1: http://viid.me/q0HCDh
--------- PLEASE SUBSCRIBE TO MY YOUTUBE ---------
Please Subscribe: https://goo.gl/Mr3YMF
Visit my website: http://tekmastah.blogspot.com
Credits
• Vlad Den from Youtube for HDD RAW Copy flash guide: https://goo.gl/i6bK9k
• Weritos from 4pda.ru forum for Cyanogenmod 13 UNOFFICIAL Rom: https://goo.gl/NdYfuS
• A-TEAM from XDA developers forum for Gapps: https://goo.gl/7A6kyX
• ZENELKA MILKO from Lenovo A706 Indonesia FB Group: https://goo.gl/wFKOsZ
• APKMirror for Google Contact Sync: https://goo.gl/mRJH8y

Hi mellomade,
Thanks for this ... I'm using another phone now running Lollipop, but still have the A760 running unofficial CM11.0. as a backup, I've downloaded all files, and will give it a go at a later date ... I'm between cataracts eye operations right one fixed, left should be done soon, I can't get new reading glasses until then, so I'm struggling with anything close-up right now. ...Jack

jachol said:
Hi mellomade,
Thanks for this ... I'm using another phone now running Lollipop, but still have the A760 running unofficial CM11.0. as a backup, I've downloaded all files, and will give it a go at a later date ... I'm between cataracts eye operations right one fixed, left should be done soon, I can't get new reading glasses until then, so I'm struggling with anything close-up right now. ...Jack
Click to expand...
Click to collapse
Hi Jachol. Good to hear some of us are still hang on to A760. No worries, do post here if you have any questions about the installation process. Get well soon!

mellomade said:
Hi Jachol. Good to hear some of us are still hang on to A760. No worries, do post here if you have any questions about the installation process. Get well soon!
Click to expand...
Click to collapse
mellomade ... The A760 has always worked well for me, I wouldn't scrap it, I only have the newer one because it came as a present ( so far it's been equally as good).
I've been studying the instructions, and guess steps 1-9 install the new TWRP recovery, the new ROM installation is then normal TWRP procedure.
I do have TWRP recovery v.2.6.3.0 already installed, but I'm sure it isn't compatible with latest android versions, so no chance of an install via that
It will be interesting to see if others from the old thread pick up your link.Thanks again. .. Jack

jachol said:
mellomade ... The A760 has always worked well for me, I wouldn't scrap it, I only have the newer one because it came as a present ( so far it's been equally as good).
I've been studying the instructions, and guess steps 1-9 install the new TWRP recovery, the new ROM installation is then normal TWRP procedure.
I do have TWRP recovery v.2.6.3.0 already installed, but I'm sure it isn't compatible with latest android versions, so no chance of an install via that
It will be interesting to see if others from the old thread pick up your link.Thanks again. .. Jack
Click to expand...
Click to collapse
Great! Actually, Starting from lollipop, rom installs require larger internal space. Since we barely have sufficient space for system on our A760, the internal storage needs to be repartition (done by HDD Raw copy tool). Luckily the provided image 'Lenovo_A760.imgc' will automatically install the updated recovery TWRP 2.8.7 (compatible for the rom install) so we dont have to.
I do think others from the old thread already shifted to other phones

The QPST link given is no more. Any chance you have another download link? Preferably one without malware, as there seems to be some of them floating around.
Thanks

astudent said:
The QPST link given is no more. Any chance you have another download link? Preferably one without malware, as there seems to be some of them floating around.
Thanks
Click to expand...
Click to collapse
I have updated with new download link (now its working). Sorry for the ads. You can click the 'Skip the ad' button after waiting for 5 seconds, or you can Google Qualcomm QPST if you prefer not to click it.

GM mellomade,
I have CM13 flashed OK now + the updated recovery, I'm finding heavy it on battery consumption,
mine loses 25% overnight with no additional apps installed as yet.
This is much higher than the unofficial CM11 Rom I have been using,
I've restricted some of google services in Privacy guard, this has helped a little
but I see no other way of reducing battery drain.
How do you find yours ?, and any suggestions please ?. ... J.

jachol said:
GM mellomade,
I have CM13 flashed OK now + the updated recovery, I'm finding heavy it on battery consumption,
mine loses 25% overnight with no additional apps installed as yet.
This is much higher than the unofficial CM11 Rom I have been using,
I've restricted some of google services in Privacy guard, this has helped a little
but I see no other way of reducing battery drain.
How do you find yours ?, and any suggestions please ?. ... J.
Click to expand...
Click to collapse
I was having the same experience too. I use Greenify App from play store, and put ALL apps into hibernation, except the one I required their notification to be alive (e.g; WhatsApp). That helps too. I guess that is one of disadvantages having an unofficial build, because it is not natively supported for our phone. Hence the high battery drain issue. On the bright side, we get to experience the latest (even though not updated) ROM :victory:

mellomade said:
I was having the same experience too. I use Greenify App from play store, and put ALL apps into hibernation, except the one I required their notification to be alive (e.g; WhatsApp). That helps too. I guess that is one of disadvantages having an unofficial build, because it is not natively supported for our phone. Hence the high battery drain issue. On the bright side, we get to experience the latest (even though not updated) ROM :victory:
Click to expand...
Click to collapse
OK, Thought I may have a problem with ROM download, I did try a reflash which didn't help any. I'll try Greenify later, one thing I like about this ROM is the minimal system apps used (no bloatware).
My present phone (X-BO 06) running Lollipop, has a setting which allows the phone to switch off/on automatically overnight which is great for battery saving, I must see if i can find an app that does the same. Thanks again for the info. ... J. :highfive:

jachol said:
OK, Thought I may have a problem with ROM download, I did try a reflash which didn't help any. I'll try Greenify later, one thing I like about this ROM is the minimal system apps used (no bloatware).
My present phone (X-BO 06) running Lollipop, has a setting which allows the phone to switch off/on automatically overnight which is great for battery saving, I must see if i can find an app that does the same. Thanks again for the info. ... J. :highfive:
Click to expand...
Click to collapse
aah.. we do have that auto start & shutdown setting on our official rom (4.1.2). Im guessing you want that functionality without installing any new apps right? If not, you may look into Phone Schedule from play store. It support android 6.0. No prob

mellomade said:
aah.. we do have that auto start & shutdown setting on our official rom (4.1.2). Im guessing you want that functionality without installing any new apps right? If not, you may look into Phone Schedule from play store. It support android 6.0. No prob
Click to expand...
Click to collapse
mellomade,
Are you saying that we do have the Off/On option with this lollipop ROM ?, if so I haven't found that it in settings, I will take another look, it does make a big difference to battery saving. ... J.

jachol said:
mellomade,
Are you saying that we do have the Off/On option with this lollipop ROM ?, if so I haven't found that it in settings, I will take another look, it does make a big difference to battery saving. ... J.
Click to expand...
Click to collapse
No no no. I think you may have misinterpreted my message there. I did mention, on our official rom, which is 4.1.2, the A760_1_A_2_0057_130828 updates from Lenovo. Sadly not on this unofficial cm build. However you can check out greenify, it does makes a lot difference if you hibernate unused apps. Hence, if this is your secondary phone, you may even hibernate all apps (which can significantly reduce battery consumption) without have to worry about any incoming notifications, am I right.

mellomade said:
No no no. I think you may have misinterpreted my message there. I did mention, on our official rom, which is 4.1.2, the A760_1_A_2_0057_130828 updates from Lenovo. Sadly not on this unofficial cm build. However you can check out greenify, it does makes a lot difference if you hibernate unused apps. Hence, if this is your secondary phone, you may even hibernate all apps (which can significantly reduce battery consumption) without have to worry about any incoming notifications, am I right.
Click to expand...
Click to collapse
Ah yes !, gotcha now ... total misunderstanding this end, and yes I've installed greenify, it helps a lot. Thanks again. ... J.

Can you please give a device tree of this rom.I really need it.

Twrp 3.3.1. UmiDIGI Power 4G

TWRP 331 Porting Thread for New UMIDIGI Power 4G
New thread for the new model UMIDIGI Power 4G Helio P35 Octa core Mtk 6765
Umidigi Power 4G MT6765 Octa Core 4G 4GB 64GB Android 9 Smartphone 6,3 inches
Everybody are Welcome!:good:
MANY THANKS TO OUR MODERATORS TO OPEN AGAIN THIS THREAD !
More attention to the Xda-developers Rules:
http://forum.xda-developers.com/announcement.php?f=256
Many thanks to "SUPER ADMIN" MR. MIKE​

New twrp 331-test 1 for this device is builded!
Now need period of tests...
http://www.mediafire.com/file/cnqw8d2qkjqtp6k/Twrp_331_test1_Umi_Power.rar/file

reserved 1

Reserved 2

TWRP Not Working for Me
Finally received the phone today. Spent a few hours trying to get your TWRP port installed with no luck unfortunately. After flashing it via SP Flash Tool, I ran into an "Orange State" unlock warning (which I assume is normal). However it's followed by a bootloop. I can only get the phone to boot using the stock recovery.img. Any modifications to the recovery causes a loop.
On the other hand though, I was able to get root through Magisk (I'm using the latest 19.3 version), and patching the stock boot.img through the app, then flashing the patched boot.img to the phone with SP Flash Tool. I have Viper4Android working, which was my main reason for wanting root, so I'm satisfied for the most part. Can't wait to try this phone out as my daily driver!

SeekerofLight.iz said:
Finally received the phone today. Spent a few hours trying to get your TWRP port installed with no luck unfortunately. After flashing it via SP Flash Tool, I ran into an "Orange State" unlock warning (which I assume is normal). However it's followed by a bootloop. I can only get the phone to boot using the stock recovery.img. Any modifications to the recovery causes a loop.
On the other hand though, I was able to get root through Magisk (I'm using the latest 19.3 version), and patching the stock boot.img through the app, then flashing the patched boot.img to the phone with SP Flash Tool. I have Viper4Android working, which was my main reason for wanting root, so I'm satisfied for the most part. Can't wait to try this phone out as my daily driver!
Click to expand...
Click to collapse
I confirm the first part of this, same issue here... i'd like to flash a twrp for gsi purposes, but for now no luck

SeekerofLight.iz said:
On the other hand though, I was able to get root through Magisk (I'm using the latest 19.3 version), and patching the stock boot.img through the app, then flashing the patched boot.img to the phone with SP Flash Tool. I have Viper4Android working, which was my main reason for wanting root, so I'm satisfied for the most part. Can't wait to try this phone out as my daily driver!
Click to expand...
Click to collapse
Can you write how you got the root of the law? Instructions for inexperienced users.
Thank you in advance.

Root UMIDIGI Power with Magisk
mr A V said:
Can you write how you got the root of the law? Instructions for inexperienced users.
Thank you in advance.
Click to expand...
Click to collapse
Sure thing! Here's a Magisk root guide for anyone just getting started that I wrote up just now. (All mentioned files are provided in the zip.)
Step 0 - Download the Attached Zip File Below
Google Drive Mirror
Mediafire Mirror
MEGA Mirror
Step 1 - Drivers
Install the MediaTek drivers by running "DriverInstaller.exe". These are the drivers that worked for me. But if you have issues with them in Step 5, Google "Mediatek MT65xx USB VCOM Drivers" (or some variation of that) and try some others you can find.
-----------------------------------
Step 2 - Install ADB Interface
Install the Android SDK (ADB Interface). To do this drop the platform-tools folder (from the Step 2 folder) into your C:\ directory. Press the windows start button and search for "Environment Variables" and click on "Edit environment variables" from the results. Under SYSTEM VARIABLES on the bottom (not User variables above it) click on the "Path" variable, and click edit. In the new window that appears, hit "Browse..." and click on the "platform-tools" folder that you placed in your C:\ directory.
All this does is allows you to easily input adb commands into command prompt with no issues. This will be used to verify that the device is appearing properly and issue commands in case of emergency.
{
"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"
}
-----------------------------------
Step 3 - Install Magisk
Copy the Magisk.apk to your phone and install it.
(This is where you can then copy the boot.img to your device and patch it via the Magisk app to create the "magisk_patched_boot.img" file, however I have included the already patched file in Step 6 for the UMIDIGI Power so you don't need to.)
Also, this is the Magisk v19.3 Beta, but you can install another version.
-----------------------------------
Step 4 - OEM Unlocking/USB Debugging Mode
On your phone, go to Settings >> System >> Developer Options. (If you haven't activated Developer Options yet, do that by going to About Phone >> Build number, and tap it a bunch of times, but I'm sure you already know this lol)
In Developer Options, turn on "OEM Unlocking" to unlock the bootloader, and USB Debugging.
-----------------------------------
Step 5 - Verify That Your Phone is Detected with ADB
Connect your phone to your PC. Make sure you click "Allow USB debugging" on your phone. Then open up Command Prompt. (Protip: Type "color a" and press Enter if you want to feel like a REAL HACKERMAN.) Now, type in "adb devices" and verify that your phone is detected by your computer. If it's detected, then that's perfect you can move on to Step 6. If not, then uh... you may have to try and find some other MediaTek drivers mentioned in Step 1.
-----------------------------------
Step 6 - Set up SP Flash Tool
Open up SP Flash Tool on your computer by running "flash_tool.exe" in the SP Flash Tool Folder. (If at any time it shows a "Processing" window for some reason, just close and reopen the program if it doesn't go away on its own.)
On the first line choose "MTK_AllInOne_DA.bin". And the third line "Authentication File" can be left blank.
On the second line where it shows "Scatter-loading File", hit "choose" and find the "MT6765_Android_scatter.txt" file in the Step 6 folder. It'll load up and show a bunch of green/white rows in the space below.
Now this looked intimidating to me at first, but it's actually quite simple. As far as I understand (and I could be wrong but), the scatter file just tells the program where to place certain files, like a map for the program to follow. The scatter file I provided is for the UMIDIGI Power. The only thing we'll worry about for now is the boot.img file (but in the future, this is where you could also install a TWRP recovery once we get one that is confirmed to work.)
So in the white/green list, scroll down to where it says "boot" in the "Name" column, and click on the blank area in the "Location" column. It will bring up a window where you can browse to the "magisk_patched_boot.img" that I provided.
-----------------------------------
Step 7 - The Big Huzzah (Rooting)
Power off your phone and make sure it's UNPLUGGED. On SP Flash Tool, click "Download". This prepares the program to begin flashing your phone as soon as it is connected. Grab your phone with one hand, and with your other hand plug in the USB cable (if you only have one hand, use your mouth I guess). Your screen should not turn on at all throughout this process, but if it's successful, you should see that the program begins to flash your device after a second or two. Now just wait until it reaches 100% and says "Download Ok" with a green checkmark. And you're pretty much done!
You can then boot up your phone and check the Magisk app, as well as download a root checker from the Play Store to confirm that your phone has root access! Have fun!

Thank you, far-away friend from me, that you are such a sympathetic person! Thank you for writing everything so quickly and in detail. As soon as I receive my phone, I will definitely try to do everything as you wrote.
Tell me, do you plan to install any firmware on this device? For example, Miui. Or are you satisfied with the stock?

mr A V said:
Thank you, far-away friend from me, that you are such a sympathetic person! Thank you for writing everything so quickly and in detail. As soon as I receive my phone, I will definitely try to do everything as you wrote.
Tell me, do you plan to install any firmware on this device? For example, Miui. Or are you satisfied with the stock?
Click to expand...
Click to collapse
No problem! Unfortunately I don't see many custom ROMs coming to this phone, considering it's not a very popular device. I'd guess our best bet is to hope that the UMIDIGI F1 gets some support, and that anything on there can hopefully be ported over to this phone, but even that device isn't very popular either. For me though, that's not a huge issue because I'm actually quite satisfied with the stock firmware it has on board. It's basically stock Android Pie, and I've been able to add all the extra goodies I want into the phone through Magisk Manager and EdXposed with very minor issues. Most notably Viper4Android to fix the slightly tinny speakers and pump up the overall headphone experience too, and Gravity Box for some extra minor software customization.
Overall, I'd say the biggest downside to this device is the limited camera capabilities, and its somewhat limited performance for heavier tasks like 3D games / game streaming. But other than that, this feels like a very premium device. :good:

I thought about the fact that it is you who can transfer other firmware to this device. As a developer, let's say.
On the F1 already installing the firmware AOSP, LOS and other projects. But need to flash these firmware through TVRP recovery. For our device, there is no such recovery yet.
I have little understanding of the intricacies of the android. Sorry if my questions seem silly.
If we take the firmware for F1, for example AOSP, will it have to be somehow changed for our UD Power? Or can just take the archive, as it is, and flash it?
The processor of our smartphone is not very strong, so it is not for games. It is also not clear what RAM is installed. It looks like the manufacturer has installed a cheap part. Put single-channel LDDR 3. So he made a low price. At the expense of device performance.

mr A V said:
I thought about the fact that it is you who can transfer other firmware to this device. As a developer, let's say.
On the F1 already installing the firmware AOSP, LOS and other projects. But need to flash these firmware through TVRP recovery. For our device, there is no such recovery yet.
I have little understanding of the intricacies of the android. Sorry if my questions seem silly.
If we take the firmware for F1, for example AOSP, will it have to be somehow changed for our UD Power? Or can just take the archive, as it is, and flash it?
The processor of our smartphone is not very strong, so it is not for games. It is also not clear what RAM is installed. It looks like the manufacturer has installed a cheap part. Put single-channel LDDR 3. So he made a low price. At the expense of device performance.
Click to expand...
Click to collapse
I definitely consider myself to be a major noob with the more advanced Android development stuff. I only know enough to find my way around the internet and flash compatible software, haha. I've never looked into creating ports myself, but it's certainly something I think might be worth learning, especially with the limited device support on these phones.
And yeah, in terms of performance I don't expect much out of a phone at this price point, but for all the essentials - music, 1080p YouTube, web browsing, and mid to light gaming, it's surprisingly great considering the price. I haven't had any issues with the memory as of yet, so I wouldn't be too concerned, although you're definitely right in that they probably source some pretty cheap parts for these kind of phones.

SeekerofLight.iz said:
Sure thing! Here's a Magisk root guide for anyone just getting started that I wrote up just now. (All mentioned files are provided in the zip.)
"stubbed guide"
Click to expand...
Click to collapse
It works like a charm, thank you! by the way, were you able to boot that twrp or still nothing? and if you made it, were you able to flash a gsi over that too? i'm unable even to boot that twrp
---------- Post added at 09:30 AM ---------- Previous post was at 09:29 AM ----------
ghost45 said:
TWRP 331 Porting Thread for New UMIDIGI Power 4G
New thread for the new model UMIDIGI Power 4G Helio P35 Octa core Mtk 6765
Umidigi Power 4G MT6765 Octa Core 4G 4GB 64GB Android 9 Smartphone 6,3 inches
Everybody are Welcome!:good:
MANY THANKS TO OUR MODERATORS TO OPEN AGAIN THIS THREAD !
More attention to the Xda-developers Rules:
http://forum.xda-developers.com/announcement.php?f=256
Many thanks to "SUPER ADMIN" MR. MIKE​
Click to expand...
Click to collapse
Can i ask you a guide on how were you able to boot it? i'm only getting a bootloop after flashing that from SPFlash

I will build one other version of recovery soon...

mg95tux said:
It works like a charm, thank you! by the way, were you able to boot that twrp or still nothing? and if you made it, were you able to flash a gsi over that too? i'm unable even to boot that twrp
Click to expand...
Click to collapse
Glad to hear it worked for you!
Still nothing. Unfortunately I haven't had any luck with booting into TWRP since I last tried it. Hoping ghost45 will be able to help us out with that when he gets the chance.

Bootloop - Secureboot
Nevermind, bootloader locked.
just type on CMD:
adb reboot bootloader
then
fastboot flashing unlock

Andre_Filho said:
Nevermind, bootloader locked.
just type on CMD:
adb reboot bootloader
then
fastboot flashing unlock
Click to expand...
Click to collapse
remember to allow oem unlock from developer settings in stock rom, otherwise it will fail!

SeekerofLight.iz said:
Finally received the phone today. Spent a few hours trying to get your TWRP port installed with no luck unfortunately. After flashing it via SP Flash Tool, I ran into an "Orange State" unlock warning (which I assume is normal). However it's followed by a bootloop. I can only get the phone to boot using the stock recovery.img. Any modifications to the recovery causes a loop.
On the other hand though, I was able to get root through Magisk (I'm using the latest 19.3 version), and patching the stock boot.img through the app, then flashing the patched boot.img to the phone with SP Flash Tool. I have Viper4Android working, which was my main reason for wanting root, so I'm satisfied for the most part. Can't wait to try this phone out as my daily driver!
Click to expand...
Click to collapse
How do you manage to work Viper.
Cause i'm having some problems, tested all versions and my Driver always stays on "Active: NO Format: Unsuported.... Abnormal"
BusyBox also don't seens to work.
:/
Some help?

Andre_Filho said:
How do you manage to work Viper.
Cause i'm having some problems, tested all versions and my Driver always stays on "Active: NO Format: Unsuported.... Abnormal"
BusyBox also don't seens to work.
:/
Some help?
Click to expand...
Click to collapse
The trick to getting Viper4Android to work is to make sure you have SELinux set to "PERMISSIVE" rather than "ENFORCING" on your phone. Here's a handy little app designed to automatically set it to permissive on boot!
https://forum.xda-developers.com/devdb/project/?id=1561#downloads
And for BusyBox, I was having issues too at first because I think with systemless root, BusyBox can only be installed in /sbin, which gets wiped after each boot. So I searched for "BusyBox" in the Magisk app and found a module called "BusyBox for Android NDK" which has worked perfectly for me.
One thing to note...
Sometimes SELinux doesn't always get changed automatically everytime you boot up. It's pretty consistent, but every once in awhile you may need to manually set it to permissive mode again if things don't seem to be working. But it's literally just pressing a single button, so not a big deal.
The other thing is with Viper itself- At times when I launch the app, the driver status says "abnormal" even after I've toggled SELinux to permissive. If you go into settings and toggle "compatibility mode" or "attach audio effects" on and then off that seems to refresh the driver status. Not sure why, but it works.
Let me know if you have any issues.

TWRP for UMIDIGI POWER
I ask for help in creating TWRP for UMIDIGI POWER firmaware ROM v1.5
Please make for this model TWRP
I am very grateful to you - I unlocked the phone and got the rights Root rights.
It remains only to create a TWRP for UMIDIGI POWER
At this forum, competent specialists and for other models everything is already done.
Maybe there is a website where you can make an order to create a TWRP?
Unfortunately, I do not know English and I do not know how to apply.
I would be very grateful and ready to test your work.

[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.

Install Any GSI ROM on the V60

I AM NOT RESPONSABLE IF YOU BREAK YOUR DEVICE OR ANY DAMAGE CAUSED BY NOT FOLLOWING INSTRUCTIONS.
Requirements:
Unlocked Bootloader
Removed Vbmeta verity (Boot Patched with magisk)
ADB and Fastboot: Adb
A GSI Rom: GSI Rom List
ENG ABL (In case you brick the device and you want to go to fastboot)
Enabled USB debugging on developer Options
Developer Options go to Settings => System => About Phone => Software Information and tap Build Number until it either asks you for your password or says you are a developer at the bottom
A Brain
Instructions:
Before doing anything make sure you have a backup of your device partitions.
All your data of the internal memory will delete.
1. Put the GSI you have downloaded from your choise (Make sure you have extracted the File) on the same folder than your Fastboot)
{
"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"
}
2. Open a CMD window on the same folder than Fastboot ( Right click + shift key on the fastboot folder and select open command prompt)
3. Run adb devices and make sure it says Device and not Unauthorized.
4. Write the command Adb reboot fastboot
5. On the Phone You will see a Fastbootd screen ( Image is an example, I dont have a camera with me at the time of doing this Guide)
6. Run Fastboot Devices and make sure your device is showing there
7. write the command fastboot getvar all to check your boot slot
8. Execute fastboot flash system_(Put your slot from previous step) the image name of your gsi.img, and wait until everything download and make sure that every single sparse sent says Okay
8. After Last step just execute fastboot erase userdata
9. just reboot the device and enjoy
Any additional question or issue just let me know and I will help you Gladly as soon as I can

Worked perfectly on my att LG v60. Cheers. it's my backup phone but thanks for giving it new life. LG software sucks. Doing this later on with my second LG v60.

Jaimesco12 said:
Worked perfectly on my att LG v60. Cheers. it's my backup phone but thanks for giving it new life. LG software sucks. Doing this later on with my second LG v60.
Click to expand...
Click to collapse
I agree. Oem software is so loaded with bloatware and bull****. And then of course ALL the carriers pile on their **** and suddenly you have a smartphone that's not really a phone anymore. It's now just a tracking/marketing device that happens to let you make phone calls, send emails. and surf the web so you can provide cookies to be uploaded when you're not looking.
I do give credit to Apple for pulling in the reins on Facebook. Hopefully, Google will be forced to do the same. They're the biggest tracker/marketer of information out there.

Btw, I've been running an a12 gsi rom for several weeks now. First, I tried the Andy Yan LOS19 vndklite secured rom but unfortunately it didn't gapps capability which is sort of a no go for a lot of people. I then switched to Phhusson' vndlite secure with gapps rom and it's been great. So far everything seems to work great except Qdaq.

Damn. Now I may have to build my phone for the second time in a week. One question:
1) How/where do I get the LG apks to properly make use of the phone's hardware? I'm thinking camera, FM Radio and DAC specifically. Plus any others I may be missing. Or is that step not necessary?
[NG]Owner

NGOwner said:
Damn. Now I may have to build my phone for the second time in a week. One question:
1) How/where do I get the LG apks to properly make use of the phone's hardware? I'm thinking camera, FM Radio and DAC specifically. Plus any others I may be missing. Or is that step not necessary?
[NG]Owner
Click to expand...
Click to collapse
I'm already working on porting stock apps to Custom including the Quad-Dac, i dont have an ETA for ir right now but its on the way

Jaimesco12 said:
Worked perfectly on my att LG v60. Cheers. it's my backup phone but thanks for giving it new life. LG software sucks. Doing this later on with my second LG v60.
Click to expand...
Click to collapse
I'm happy to hear that it helped you

Does Android Pay work on this?

Will this process also work for the v40 as well? And if so, can I expect the IMS stack to work on the v40 such that VoLTE and WiFi Calling on Tmo can be enabled?
For that matter do/will VoLTE and WiFi Calling work on TMo using GSI ROMs on a v60?
[NG]Owner

failed, kernel crash, dont't know the reason
update: show no command

I'm assuming that if I install a GSI on the V60, I lose dual-screen usage correct?

jblparisi said:
Does Android Pay work on this?
Click to expand...
Click to collapse
Depends of the GSI you have chosen, some of them comes with Safetynet already approved

peterwode said:
failed, kernel crash, dont't know the reason
Click to expand...
Click to collapse
Make sure alll sparces says OK, also if you are on android 11 you cannot flash a GSI with android 10

Play4Zeta said:
I'm assuming that if I install a GSI on the V60, I lose dual-screen usage correct?
Click to expand...
Click to collapse
I havent tested that, I broke mine a while ago

Kratos574 said:
I havent tested that, I broke mine a while ago
Click to expand...
Click to collapse
Any reason you would think it wouldn't? Mostly just have my V60 for the dual screen.

Jaimesco12 said:
Worked perfectly on my att LG v60. Cheers. it's my backup phone but thanks for giving it new life. LG software sucks. Doing this later on with my second LG v60.
Click to expand...
Click to collapse
Hey mate, you could tell me how you did the prep work to install the GSI room on the ATT variant? Ive been trying to unlock it and installing TWRP but i havent found a reliable way of doing it.

Do you know what rooms work well with the v60? (like having QDAC functionality for instance)

Kratos574 said:
I'm already working on porting stock apps to Custom including the Quad-Dac, i dont have an ETA for ir right now but its on the way
Click to expand...
Click to collapse
wait Quad-Dac

Just wanted to say a big thanks to Kratos for putting this post together. I had some early issues but it turns out that's because I was using 'Minimal ADB and Fastboot'
For whoever comes next here's how I fixed a couple of problems as I went.
ERROR: Failed: remote partition not found - You need to be in fastbootD via ADB REBOOT FASTBOOT, not the fastboot/bootloader via turning off device, holding vol down and plugging in a usb cable.
ERROR: Remote: Operation not permitted. - Minimal ADB and Fastboot is not new enough - download latest SDK platform tools and open an administrator CMD prompt from that directory instead.
Other errors or failure of individual parse files can be fixed by using a better quality cable - you're sending a lot of data via fastbootd. Give yourself the best shot at success.
I installed OctaviOS yesterday and was absolutely blown away - it's extremely fast, the battery life is incredible and the level of deep customisation rivals any rom I've ever used.
Unfortunately, haptic feedback / vibration does not work AT ALL, and nor does the 3.5mm Jack. Also GCAM, nor any other camera app I tried was able to access the wide angle lens so I'll be trying to figure out how to get back to EA firmware today for now.
If someone with the skills could manage a non-gsi port of OctaviOS with cam, haptic and 3.5mm working properly I'd be on it in a heartbeat. THAT is what Android should be. Bloat free but highly customisable.

bandario said:
Just wanted to say a big thanks to Kratos for putting this post together. I had some early issues but it turns out that's because I was using 'Minimal ADB and Fastboot'
For whoever comes next here's how I fixed a couple of problems as I went.
ERROR: Failed: remote partition not found - You need to be in fastbootD via ADB REBOOT FASTBOOT, not the fastboot/bootloader via turning off device, holding vol down and plugging in a usb cable.
ERROR: Remote: Operation not permitted. - Minimal ADB and Fastboot is not new enough - download latest SDK platform tools and open an administrator CMD prompt from that directory instead.
Other errors or failure of individual parse files can be fixed by using a better quality cable - you're sending a lot of data via fastbootd. Give yourself the best shot at success.
I installed OctaviOS yesterday and was absolutely blown away - it's extremely fast, the battery life is incredible and the level of deep customisation rivals any rom I've ever used.
Unfortunately, haptic feedback / vibration does not work AT ALL, and nor does the 3.5mm Jack. Also GCAM, nor any other camera app I tried was able to access the wide angle lens so I'll be trying to figure out how to get back to EA firmware today for now.
If someone with the skills could manage a non-gsi port of OctaviOS with cam, haptic and 3.5mm working properly I'd be on it in a heartbeat. THAT is what Android should be. Bloat free but highly customisable.
Click to expand...
Click to collapse
Just go to Phh Settings and click on Alternate audio policy, That fixes 3.5mm jack

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...