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.
Related
DISCLAIMER: all operations descripted here should be done *only* by trained & expert guys... as every "hacking" operations, they involve the risk of soft/hard bricking your device making it unusable temporary or permanently. I will not be responsable in any way for it. So, pay attention and, if not sure, simply don't do it.
WARNING #1: this is a fast guide describing needed steps and providing needed files only for expert guys. It is *not*suitable* for newbies who need detailed instructions on how to install drivers, programs, flash partitions, etc...
WARNING #2: on this phone there are (strangely...) close ties between boot.img and recovery.img content. This involves that changing contents of recovery.img can produce bootloop and changing contents of boot.img can prevent to access recovery too, creating a soft brick condition. I don't know exactly why, BUT you are warned.
WARNING #3: the procedure and files provided are *only* for ROM1 firmware version 14 of 13 Aug 2016. It is indicated as OUKITEL_C4_V14.0_20160813 in "About phone" and as t637d-oq-s08-fdd3m-hd-64g8g-sd internally. If you are on a differently indicated version and/or release date, *don't*even*think* about trying to apply the provided files: bootloops and (at least) soft bricks are easy coming, expecially because of warning #2...
WARNING #4: all provided files are in .zip format only due to forum rules and limitations. They *all* need to be *unpacked* before use them.
CREDITS: this TWRP recovery has been compiled by Jemmini on 4PDA forum. Since of the Russian only language of that forum and the very hard way to subscribe on it for not Russians (needed to download files too...), I'm reporting it here with more explanations and my hints & experiences too...
Said that... Let's start! :highfive:
IF (and *only* if...) your firmware version is reported as OUKITEL_C4_V14.0_20160813 in your phone, these are the steps to follow:
- unlock your bootloader (no special code needed, just enable the apposite option slider in Developers section of Settings and unlock it by the standard fastboot command in fastload mode... you need adb, fastboot and adb/fastboot drivers installed in your pc obviously )
Please remember that, as ever, unlocking your bootloader will factory reset your phone (and void your warranty...), so take it in proper account....
- using SP Flash Tool (recent versions since of the new MT6737 used in C4... tested one is the v.5.1644, just Google for it) just flash the provided twrp-c4.img (by Jemmini on 4PDA) selecting "Download only" on top, using the provided scatter file and selecting only the recovery row (browsing to twrp-c4.img file). Then press Download button and connect your phone in OFF status. If all was OK and you have MTK drivers properly installed (Google for them... search for MT6737 drivers. To test them just try to connect your phone to PC as storage to check if it is properly seen...), you should see a green checking sign "v" on top of SP Flash tool.
If nothing happens, try to reinstall drivers and/or doublecheck your phone is in OFF status when connected.
- don't try to boot to system now. It simply doesn't anyway.
For some unknown reason connected to warning #2, flashing twrp introduces a bootloop (soft brick...) on this phone.
Nothing to be worried of anyway: systemless rooting will fix it!
To root simply flash by TWRP (yes, you need to enable /system modification on first twrp boot...) SuperSU v.2.78 "standard" version in zip format (just Google for it...).
For standard is intended the released one, not SRx or "forced to system" one... (tested version is SuperSU-v2.78-201609011115.zip) .
Just remember that, since of unability to boot system before flashing SuperSU, its zip have to be already on your device before flashing TWRP. Otherwise you can use a microSD card to flash from it...
If you do all fine you now have your rooted & TWRP 3.0.2-x provided Oukitel C4!!! :highfive:
If you are in a bootloop condition you aren't able to fix, just turn off your phone and, ever using SP Flash Tool in the same way, simply reflashing stock boot.img and recovery.img (both provided as zipped-to-to-be-unzipped attachment for... emergency reasons ).
After, if you want, you can install Xposed (in system mode) or busybox by app (it will be automatically installed in systemless mode since of supersu installation method...).
Don't even try to install Magisk v.9 instead: it will not work and will produce a soft brick (with no recovery access too...) that will requires a boot.img and recovery.img reflashing to be solved (with all this procedure to be redone one more time...).
This said... if you have questions... I'm here to answer them. Otherwise... have a nice time with your TWRP provided and systemless Rooted Oukitel C4!!! :fingers-crossed:
Reserved. :silly:
Can you please provide the 4PDA forum link of TWRP for this phone? Thanks for your post anyways
[email protected] said:
Can you please provide the 4PDA forum link of TWRP for this phone? Thanks for your post anyways
Click to expand...
Click to collapse
Added in OP. Don't expect to find more anyway...
I can confirm that this TWRP build also works fine with the newest OUKITEL_C4_V17.0_20161124 Firmware. Important: before flashing TWRP disable your boot lock code, otherwise you will softbrick your device.
Entec do you have an 4pda Account? If yes it would be really awesome if you could add the second TWRP recovery image for oukitel phones with the Rxx_xxxx ROM to OP.
EDIT:
I successfully installed XPOSED on my C4! This rocks the **** out of an 50 EUR budget phone!
Hello thank you for your information, could you provide us also TWRP for 32bits version (R06), I have tried to download from de forum but file is not avalaible.
regards
salvarez01 said:
Hello thank you for your information, could you provide us also TWRP for 32bits version (R06), I have tried to download from de forum but file is not avalaible.
regards
Click to expand...
Click to collapse
We need someone with 4PDA Account....
However, have you tried to install the 64Bit rom? You can get the Stock 64 Bit Rom from needrom.com. I advise you to do the software update before flashing TWRP linked in this thread.
[email protected] said:
We need someone with 4PDA Account....
However, have you tried to install the 64Bit rom? You can get the Stock 64 Bit Rom from needrom.com. I advise you to do the software update before flashing TWRP linked in this thread.
Click to expand...
Click to collapse
Hello thank you I have flashed 64 bits Rom and updated to V17, now all OK with TWRP and SuperSU.
Seam 64 bits version more slow than R06, but OK.
Thanks.
Hello I have tried to use native sip editing the files in /system/etc/permissions but the option is not available in phone menu. Someone know how to activate?
Enviado desde mi Redmi Note 4 mediante Tapatalk
[email protected] said:
Entec do you have an 4pda Account? If yes it would be really awesome if you could add the second TWRP recovery image for oukitel phones with the Rxx_xxxx ROM to OP.
Click to expand...
Click to collapse
[email protected] said:
We need someone with 4PDA Account....
However, have you tried to install the 64Bit rom? You can get the Stock 64 Bit Rom from needrom.com. I advise you to do the software update before flashing TWRP linked in this thread.
Click to expand...
Click to collapse
I managed to create an account on 4pda.ru and downloaded twrp for all firmware versions!
Files are attached!
Use twrp_recovery_C4_V.zip if your phone uses the OUKITEL_C4_VXX.X_XXXXXXXX firmware (Tested with OUKITEL_C4_V17.0_20161124)
Use twrp_recovery_R0x.zip if your phone uses the R0X_XXXXXX firmware. (Tested with R06_102033)
Where is OUKITEL_C4_V17.0_20161124 firm now?
I can't find it at needrom.com.
pop003 said:
Where is OUKITEL_C4_V17.0_20161124 firm now?
I can't find it at needrom.com.
Click to expand...
Click to collapse
Which rom do you have on your device?
Now I have R06_102033 on my C4
pop003 said:
Now I have R06_102033 on my C4
Click to expand...
Click to collapse
No problem, just use the twrp_recovery_R0x.zip from my previous post.
https://forum.xda-developers.com/showpost.php?p=71584701&postcount=10
[email protected] said:
No problem, just use the twrp_recovery_R0x.zip from my previous post.
https://forum.xda-developers.com/showpost.php?p=71584701&postcount=10
(do not forget to give it a like)
Click to expand...
Click to collapse
Thank you. twrp_recovery_R0x installed successfully.
However, in my environment, I needed the latest version of SP_Flash_Tool_v 5.1712_Win.
With other versions of sp_flash_tool, I did not succeed any number of times.
pop003 said:
Thank you. twrp_recovery_R0x installed successfully.
However, in my environment, I needed the latest version of SP_Flash_Tool_v 5.1712_Win.
With other versions of sp_flash_tool, I did not succeed any number of times.
Click to expand...
Click to collapse
Glad to hear it worked!
salvarez01 said:
Hello I have tried to use native sip editing the files in /system/etc/permissions but the option is not available in phone menu. Someone know how to activate?
Enviado desde mi Redmi Note 4 mediante Tapatalk
Click to expand...
Click to collapse
You can configure SIP by using an App called Activity Launcher.
Download and Install Activity Launcher
Start Activity Launcher
Choose 'All Activities'
Search for 'Phone'
Open 'Phone'
Search and Click 'Sip Settings', 'com.android.phone.services.telephony.sip.SipSettings'
{
"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"
}
Hello, yes I know this app to find secret menu. With this you can configure sip settings but when you try to make a call the dialer not offer choice to select calls with sip account
Enviado desde mi Redmi Note 4 mediante Tapatalk
salvarez01 said:
Hello, yes I know this app to find secret menu. With this you can configure sip settings but when you try to make a call the dialer not offer choice to select calls with sip account
Enviado desde mi Redmi Note 4 mediante Tapatalk
Click to expand...
Click to collapse
After you added an Sip account you can choose you default dailing method as follows: Dailer -> Settings -> Accounts -> Dail With
You also see your SIP account as "additional SIM Card" when Opening the dailer!
Thank you!
EDIT: FIXED. I flashed persist.img from version "S250260_210804..." (unzip, flash via `fastboot flash persist persist.img`) https://mirrors.lolinet.com/firmware/lenovo/Tab_P11_Pro/TB-J706F/
Hello dear community,
I am in need of some help. So here is what I did:
* Coming from latest Android 11 ROW, flashed ZUI using QFIL from here: https://mirrors.lolinet.com/firmware/lenovo/Tab_P11_Pro/TB-J706F/
* tried upgrading to ZUI 12.5, 12.6 and 13 but didn't work
* used fastboot to unlock and unlock_critical (i know, i know...)
* used payload_dumper (from some github repo) to extract zui 13 update.zip
* flashed every image I extracted manually using fastboot (I know, I'm stupid)
* Got ZUI 12.0 working, didn't like it and wanted ROW android 11 back
* flashed latest ROW rom using QFIL from lolinet url -> bootloop
* flashed oldest ROW rom using QFIL, updated 3x via OTA to latest version -> few bootloops, then device booted back to android 10 and created notification "failed to install ota"
So I can install any version between TB-J706F_S210002_201015_ROW and TB-J706F_S250260_210804_ROW from lolinet url, but nothing above that. Neither through QFIL, nor using lenovo smart rescue assistent, nor using OTA update from android 10 (which is working fine).
I tried following things to fix this:
* ####6030# -> change to CN and change the NV value to 00
* ####6030# -> change to DE and change the NV value to 02 or 00
* flash latest ROW using QFIL, then change NV value from 02 to 00
nothing of that worked and I'm starting to believe, that I ****ed up some partitions using fastboot. Because I flashed images from ZUI android 11 and I can't install ROW android 11 now.
Could I possibly try restoring a TWRP backup from some other user?
What else could I do to install android 11?
PS: I used QFIL backup and restore tool to change the NV value. Because the nv reader/writer tool didn't seem to work.
It might help, if someone would be kind enough to provide me with the following images (by backing them up with twrp):
* abl
* xbl_a
* xbl_b
Hi there, I also got into this trouble that can't flash any global ROM including TB-J706F_S250260_210804_ROW. What I did is change the NV value to 02 and not 00 using QFIL. After that I was able to update via OTA and currently on the latest global ROM.
Thanks to this thread: https://forum.xda-developers.com/t/check-region-unlock-p11-tb-j606f-l-n.4356451/
MateUserHHTTI have similar problem before, can not flash to Android 11, even ROW or ZUI, bootloop~
please check your J706F screen auto rotate and auto brightness(and pair bluetooth devices) still functional?
If not functional, I'm following below post instruction to flash presist.img, and can upgrade to Android 11, both of ROW & ZUI are available.
<TB-J706F> Auto-rotation & Auto Brightness Broken.But Serial Number shows 123456789ABCDEF, wifi /bluetooth MAC shows 00:00:00... still not solve even functional.
auston said:
But Serial Number shows 123456789ABCDEF, wifi /bluetooth MAC shows 00:00:00... still not solve even functional.
Click to expand...
Click to collapse
I may found a fix for Bluetooth MAC by generating a file for the "NV-items_reader_writer.exe" and wrote it to NV item 447 (some one sait this is BT). Problem was that this item (447) was NOT present at this time inn QCN.
WARNING! May my guess of "Items size" 128 is wrong, I don't know. Use at your own risk and change the file to your MAC.
After that I flashed "persist.img" (matching the actual ROM), some one wrote that this fixed the autorotate. I can confirm this.
But still not found solution for serial, the correct serial is still in NV item 2497.
Okay, Serial number restore can be done the same way.
See here https://forum.xda-developers.com/t/tab-j706f-serial-number.4318901/
Best would be to have the full original QCN file (or an editor for this files)
MateUserHHTT said:
* abl
* xbl_a
* xbl_b
Click to expand...
Click to collapse
abl (_a and _b) = abl.elf
xbl (_a and _b) = xbl.elf
You will find both in the ROM Zip's at lolinet.
Mine updates successfully from 10 to 11 after I have restored BT, Wifi, SN, PN and region lock. And flashed persist.img.
Oh, and you have to set region code in QCN NV 6858, somebody found out that Android 11 checks that value. If it is wrong, device boot loops.
auston said:
please check your J706F screen auto rotate and auto brightness(and pair bluetooth devices) still functional?
Click to expand...
Click to collapse
Firstly, let me thank you for your reply! It's interesting, I indeed noticed just a few days ago, that auto rotation isn't working!
I will follow the guide you linked and update my post accordingly.
Edit: THANK you very much indeed! My problem was solved instantly by this!
Flashed persist.img via fastboot, flashed the latest ROM from lolinet using QFIL and had no issues whatsoever.
Oh, and you have to set region code in QCN NV 6858, somebody found out that Android 11 checks that value. If it is wrong, device boot loops.
Click to expand...
Click to collapse
as I said in my post, I did tried both 00 and 02. I read the thread about the second region code checking.
CryptMan said:
Mine updates successfully from 10 to 11 after I have restored BT, Wifi, SN, PN and region lock. And flashed persist.img.
Click to expand...
Click to collapse
I don't have any problem but just in case...
I guess PN is Product Number where did you change it and where do you get the correct value? I only found a code before the SN that looks unique per tablet but it's not in the box.
MrCrayon said:
I guess PN is Product Number where did you change it and where do you get the correct value?
Click to expand...
Click to collapse
Well I changed the PN in NV item 2497
I found this PN number here: https://forum.xda-developers.com/t/tab-j706f-serial-number.4318901/#post-86315607
My other device, P11 (TB-J606F), has this number: 8SSP69A6PB5XHA6213L0864
Because they look pretty same (length, etc.) I decided to try it.
May somebody would confirm if this PN are the same on all device.
Open settings and type in the search bar "####2222#". That will display PN and SN.
One issue persists though, which is that my widewine level is set to L3.
1. I flashed persist.img from TB-J706F_S250260_210804_ROW
2. I then installed the TB-J706F_S620150_211226_ROW via QFIL and
3. updated to TB-J706F_S630185_220128_ROW via OTA in system settings.
My serial number is also 1-9A-F. My device is locked. I'm unlocking my device and flashing the persist.img of the latest ROM. If that doesn't work, what are my options to restore L1?
CryptMan said:
Well I changed the PN in NV item 2497
I found this PN number here: https://forum.xda-developers.com/t/tab-j706f-serial-number.4318901/#post-86315607
My other device, P11 (TB-J606F), has this number: 8SSP69A6PB5XHA6213L0864
Because they look pretty same (length, etc.) I decided to try it.
May somebody would confirm if this PN are the same on all device.
Open settings and type in the search bar "####2222#". That will display PN and SN.
Click to expand...
Click to collapse
Ah ok, so the number before SN is the PN.
I have two J706F and they have different PN, The last 8-9 digits are different and the other ones are the same.
I could not find that code anywhere else.
MateUserHHTT said:
One issue persists though, which is that my widewine level is set to L3.
Click to expand...
Click to collapse
If you check in play store settings does it say your device is certified?
On my J706F, the one on which I have lost QCN with SN MAC etc. , I have the same problem as MateUserHHTT.
The device lost L1 cert. PlayStore says NOT certified and "DRM Info" app says L3.
I also have a property "sys.lenovo.widevine_security_level" with value "L3".
My guess it that there is a file or partition holding this certifications, but I don' t know which.
And of course I don't have a backup ...
If you check in play store settings does it say your device is certified?
Click to expand...
Click to collapse
It says "Device is not certified"
Now that's curious: my tablet, running the latest Android 11 ROW version, is offering me to upgrade my device to Android Kitkat 4.4. Now that's an offer I can't resist (yes, of course I clicked "update". I want all the new features!)
{
"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"
}
CryptMan said:
The device lost L1 cert. PlayStore says NOT certified and "DRM Info" app says L3.
I also have a property "sys.lenovo.widevine_security_level" with value "L3".
Click to expand...
Click to collapse
Is your bootloader unlocked or did you unlock it previously and relocked?
MateUserHHTT said:
It says "Device is not certified"
Now that's curious: my tablet, running the latest Android 11 ROW version, is offering me to upgrade my device to Android Kitkat 4.4. Now that's an offer I can't resist (yes, of course I clicked "update". I want all the new features!)
Click to expand...
Click to collapse
Maybe the OTA app is getting some wrong data / not set data and that's the result
I tried to decompile that app to get the address called to download updates but my knowledge of android programming is really basic and did not have enough time.
MrCrayon said:
Is your bootloader unlocked or did you unlock it previously and relocked?
Maybe the OTA app is getting some wrong data / not set data and that's the result
I tried to decompile that app to get the address called to download updates but my knowledge of android programming is really basic and did not have enough time.
Click to expand...
Click to collapse
I previousl, unlocked and afterwards relocked it (both flashing lock and flashing lock_critical)
Yes, I once said "erase all before download" and accidentally deleted my original qcn file so some NV fields seem to be missing. Maybe that caused the app to default back to 4.4 it was Lenovo Feature Updater by the way, not the settings - system - update.
If you share your past work in a git repo I will take a look at it. I'm no expert for sure but I'm developing fir android for some years and have stuck my nose a tiny bit under the surface of android rom development (1mm and it was very painful still).
My widewine lvl is L3. Any chance of resetting to L1 myself? I don't know much about how trust attestation works. :/
MateUserHHTT said:
It was Lenovo Feature Updater by the way, not the settings - system - update.
Click to expand...
Click to collapse
I disabled that as soon as I saw it
MateUserHHTT said:
If you share your past work in a git repo I will take a look at it. I'm no expert for sure but I'm developing fir android for some years and have stuck my nose a tiny bit under the surface of android rom development (1mm and it was very painful still).
Click to expand...
Click to collapse
Not much really, I'm not at my desk now but I extracted LenovoOTA from stock ROM and decompiled it with apktools, but even with online tools is probably ok.
Then I see two options:
Recompile that package changing package name and adding a log with full address and parameters or get the code that construct the URL and put it in a new app.
For you probably the last one is easier.
I went for a third I was trying to understand if i could get the data with adb or in files but I did not find documentation.
MateUserHHTT said:
My widewine lvl is L3. Any chance of resetting to L1 myself? I don't know much about how trust attestation works. :/
Click to expand...
Click to collapse
I don't think there is a way to force it, this widevine a thing is a pain.
MrCrayon said:
Is your bootloader unlocked or did you unlock it previously and relocked?
Click to expand...
Click to collapse
Locked, and was never unlocked before.
I tried to unlock now, but does not succeed with flashing sn.img.
Because I'm not interested on Custum ROM, I will leave it locked.
Do you know where the device certification is stored?
I unlocked without flashing sn.img. Does that make a difference?
Did you try monitoring the network traffic with wireshark?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This is the support thread of PixelFlasher
(PixelFlasher is an open-source self contained GUI tool to facilitate Pixel phone device flashing/rooting/updating with extra features).
Note: This thread is meant for issues and problems faced in Google Pixel 6a devices, generic issues that are device agnostic should be discussed in the main thread.
For full details on where to download / usage and feature set of the tool, visit the main thread at XDA or the project's Github page.
Troubleshooting:
If you need support or assistance, the best way to get is by generating a support file from within PixelFlasher.
You can hit that big Support button on the main screen, or select it from the Help menu.
The generated support.zip file is sanitized (redacted) to keep your sensitive information (username device id ...) private.
This seems interesting. I was just looking into options to disable verity and or verification, root, and flash a custom kernel. It seems this application is an all in one. If all goes as planned, will my data and apps remain? Or am I basically starting all over. My bootloader is already unlocked. Thanks for sharing.
chopt51 said:
This seems interesting. I was just looking into options to disable verity and or verification, root, and flash a custom kernel. It seems this application is an all in one. If all goes as planned, will my data and apps remain? Or am I basically starting all over. My bootloader is already unlocked. Thanks for sharing.
Click to expand...
Click to collapse
If you don't choose wipe data, or force in flash options, then you should keep your data.
I have my 6a connected with usb. I chose where my platform tools are in a directory but it doesnt find a device via adb. Yet cmd shows an adb connection.
USB debugging turned on?
tlxxxsracer said:
Yet cmd shows an adb connection.
Click to expand...
Click to collapse
Explain what you mean by that?
badabing2003 said:
Explain what you mean by that?
Click to expand...
Click to collapse
usb debugging was on. when I run an adb/fastboot in cmd within the same directory my device is recognized
tlxxxsracer said:
usb debugging was on. when I run an adb/fastboot in cmd within the same directory my device is recognized
Click to expand...
Click to collapse
Please be clear and explicit, exactly what you ran and what response you got, please also generate support.zip file from the help menu of PixelFlasher and post it here.
There is no reason for it not to be detected if you're command detects it.
New Release:
Aug 24, 2022 v3.6.0 release
When a device is selected, the Bootloader version is displayed. (Useful for Pixel 6* devices with ARB). Works in adb and fastboot modes.
Added a button to dump full device info (useful for troubleshooting). Works in adb and fastboot modes.
Improved tooltips.
Hello,
I have a pixel 6a on A12 rooted with Magisk.
I tried to upgrade to A13 with PixelFlasher (v3.6.0) with the option to flash all the slots and now I'm stuck in loop.
I tried to use fastboot command to flash again with A13 with no result. I also tried to change the current slot.
The weird thing is that I still have the message that said the bootloader is unlocked...
Any ideas?
jpdurand31 said:
Hello,
I have a pixel 6a on A12 rooted with Magisk.
I tried to upgrade to A13 with PixelFlasher (v3.6.0) with the option to flash all the slots and now I'm stuck in loop.
I tried to use fastboot command to flash again with A13 with no result. I also tried to change the current slot.
The weird thing is that I still have the message that said the bootloader is unlocked...
Any ideas?
Click to expand...
Click to collapse
If you can post support.zip file from help menu I can take a look.
If you want more info, i'm 100% available!
jpdurand31 said:
If you want more info, i'm 100% available!
Click to expand...
Click to collapse
Hmmm ...
I don't see any flashing logs in PixelFlasher, are you sure you flashed in PixelFlasher?
I see you started with PixelFlasher 3.4.0 and upgraded to 3.6.0; good
I see at first you did not have Android Platform Tools installed, and then had version 28.0.2-debian; bad, this is an old version, you should click on the blue link next to the Android Platform Tools and download the latest (don't install from package manager, those are usually old, just download the latest and unpack wherever you want, and point to it in PixelFlasher)
You started in adb mode (good), processed the firmware in PixelFlasher, but that is where you stopped, you did not attempt flashing in PixelFlasher (not sure what you did, but it would help to know)
On next attempt (one hour later) your device was in bootloader mode.
Then you tried disabling magisk, which didn't work because that feature requires adb mode, and your phone is stuck in fastboot mode.
You cannot create a patch file in fastboot mode, it needs to be in adb mode.
And please please don't dare to lock your bootloader, I see you attempted and then cancelled,
Code:
2022-09-02 18:25:29 Lock Bootloader
WARNING!!! WARNING!!! WARNING!!!
NEVER, EVER LOCK THE BOOTLOADER WITHOUT REVERTING
TO STOCK FIRMWARE OR YOUR PHONE WILL BE BRICKED!!!
Do you want to continue to Lock the device bootloader?
Press OK to continue or CANCEL to abort.
2022-09-02 18:25:42 User Pressed Cancel.
Aborting ...
If you lock your bootloader before fixing your device, you will be locked out forever (bricked)
So at this point what are your choice and how can you fix this?
1- get the latest Android Platform Tools
2- If PixelFlasher detects your device, check if it is in fastboot mode (f.b) or adb mode.
Select the firmware, process it, this will show the boot.img file
Select the boot.img file and choose keep data and hit Flash.
Yes I know, you will lose root because you're not flashing a patched boot.img, but you can always re-root if you recover your device.
Alternately, what happens if you select in PixelFlasher to reboot the device into System.
Does it reboot? and if it does, does it end up in adb mode of fastboot mode?
One other option you have is to flash OTA in sideload mode.
Report back, and make sure you capture all the manual steps you perform outside of PixelFlasher.
PixelFlasher logs would tell me everything you do in PixelFlasher, you can submit a new one after your operations.
Good luck
Thanks for your response and the detailed process.
I was fooled by the version of the package that was in 33...
By upgrading the Android Platform Tools to the latest version, I could update to Android 13.
Thanks a lot for the help and the reactivity!
New Release:
Sep 04, 2022 v3.7.0 release
New Feature: Install Magisk into the phone, PixelFlasher displays information about the latest available Magisk versions (stable, beta, canary, debug) and offers the choice to install a selection.
New Feature: Install compatible apk file onto the device from PixelFlasher menu.
Check Android Platform Tools version and warn if it is old.
Block flashing when stock flash_all.bat file is tampered with.
Don't bother with flashing if bootloader is locked.
More validations and exceptions handling.
Improved logging.
3.7.0 does not start for me on Windows 10. It never appears in my task list as running. 3.6.0 is working fine.
JudasD said:
3.7.0 does not start for me on Windows 10. It never appears in my task list as running. 3.6.0 is working fine.
Click to expand...
Click to collapse
Thanks for reporting and sorry for your troubles.
Can you please open a command prompt, navigate to PixelFlasher 3.7.0 and run it from command prompt (just type PixelFlasher.exe), see if it displays an error in the console.
Can you also please generate a support.zip file using PixelFlasher 3.6.0 ?
It should capture the error PixelFlasher 3.7.0 encountered.
Thank you for the help. The issue has now been resolved after reboot.
Launching 3.7.0 via cli displayed no error message. I went to create support.zip with 3.6.0 and my computer BSODed. After reboot, 3.7.0 runs just fine. Apologies for the false alarm.
JudasD said:
Thank you for the help. The issue has now been resolved after reboot.
Launching 3.7.0 via cli displayed no error message. I went to create support.zip with 3.6.0 and my computer BSODed. After reboot, 3.7.0 runs just fine. Apologies for the false alarm.
Click to expand...
Click to collapse
No need for apology, happy to hear that the issue now resolved.
Not sure if this should be of concern, but upgrading to today's Android release, I got this (very early on, while selecting the device and firmware):
Code:
2022-09-12 18:44:06 ERROR: Exception during Magisk modules processing
Exception: not enough values to unpack (expected 2, got 1)
Everything seemed to work fine, though.
Read carefully:This is a dedicated post for general questions only. If you need technical support about flashing or restoring your device, please use the general topic for TB132FU. Please search for your question below before asking.NEW: How to restore the lost Serial Number (on the second response)
How to flash Official global romDid my work help you? Be free to buy me a coffee. PayPal me at @alsbvg
FAQ:
Why so many versions of TB132FU and why so much confusion about the Android system, updates, etc?
There are currently 3 systems available for the tablet known as TB132FU and is really important to find which one you have.
Fake Global version - Modified Android 12
Official International version - Official Android 12 or latest by Lenovo international
Chinese version - Zui 14 based on Android 12 or latest by Lenovo China
But why so many versions then? The Chinese model is apparently cheaper than the international version, so Chinese sellers are selling online the Chinese model with a modified android version to look like the international version.
How to identify which version of TB132FU I have? By the seller:If you purchased your tablet online from china like on Aliexpress or from a seller that sells items from china, you most likely have the “Fake” Global version.
If you purchased your tablet on Lenovos’s website or a certified local or national seller in your country, you most likely have the International version. This version usually costs more.
If you purchased from china or anywhere else, but your tablet has a Chinese interface, you have the Chinese version running ZUI 14 or latest.
How to identify which version of TB132FU I have? By the system version:To make sure which one you have you can also do the following:
On your tablet go to SETTINGS > ABOUT DEVICE > and find your system version.
If it starts with TB132FU_S3 you have the Chinese version running an unofficial android version. The number S3 confirms it’s a modified OS. You will never get any updates.
If it says TB132FU_S0 you have the official international version. This is the official version, so you already have the best compatible system for your tablet. You will get official updates.
If you open the settings and see on the About device menu the system version ZUI, well you have the chinese official device and system.
Can I convert my Chinese TB132FU into the international version?The answer currently is no. Why? To keep it short: There is a code inside your tablet saying “This is the Chinese tablet” and because of this code you can't install the international android system. Maybe in the future, someone from the community will be able to find that code and change it so the tablet thinks it is the international version.
Can I convert my Official Lenovo-bought TB132FU to the Chinese version to use ZUI?Same as the answer above. We need to find the code and how to modify it first.
Can I use Lenovo’s Rescue and Smart Assistant software to convert my Chinese TB132FU into the international version?No. You will brick your device if you try to update your system using this tool.
What are the differences between the Chinese TB132FU and the International version?Chinese version with ZUI 14
Software: It comes with an Android flavor called ZUI currently based on android 12. Updates will be available.
System languages: English and Chinese only.
Full support for super fast charging with the original charger. Full charge in less than 90 minutes in most cases.
Computer mode: No longer available. The online community is pushing Lenovo to enable this option again.
HDR and L1 status: Fully functional HDR and L1 status for HD content on Netflix in most cases.
Chinese version with Fake global version
Software: It comes with a modified Android 12. No updates will be available.
System languages: All languages available.
Slow charging. Can take up to 3 hours to fully charge.
Computer mode: Available.
HDR and L1 status: Falty HDR on most apps. L1 status for HD content on Netflix.
Official International Version
Software: It comes with Android 12. Updates will be available by Lenovo.
System languages: All languages available.
Slow charging. Can take up to 3 hours to fully charge. (By some reports online) This information hasn't been confirmed yet as the community with the official international version is still small.
Computer mode: Available.
HDR and L1 status: Working HDR. L1 status for HD content on Netflix.
(Under construction)
How-tos and tutorials links:
How to install/restore ZUI on my fake global version?There are three options available. Please read all 3 below and decide which one you want to try.
OPTION ONE: If you are in a hurry and have technical knowledge download the file our community colleague @Fatperman managed to upload and install it using the SP flash tool. Thread here. A Step-by-step tutorial will be provided by another community member soon. A link will be provided once available.
OPTION TWO: If you are not in a hurry and don't have the technical knowledge to flash the system, there is an easier way, but it takes one or two days.
1 - Download Lenovo’s Rescue and Smart Assistant software here.
2 - Open the software and create an account. Connecting to Google is easier.
3 - Once connected to an account, find the SMALL blue FEEDBACK button on the right side bottom of your screen and click there.
4 - Put your email address and in COMMENTS write that you have problems flashing the Chinese version of TB132FU and that you would like to restore it to the original ZUI 14 software. PLEASE USE YOUR OWN WORDS.
5 - After one or two days (usually), INSIDE the software you will receive a response with instructions on how to install ZUI more easily. Note: You will not get a response via email, you will receive institutions inside Lenovo’s Rescue and Smart Assistant software.
The instructions are pretty simple. READ THEM carefully once you receive them. It's really easy. Basically, they will send you a link to download a special rescue tool and some credentials. Take a screenshot of the instructions as you will need to uninstall the official Rescue software and will lose the message.
{
"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"
}
Download and install the software they sent, enter using the temporary credentials (the credential are confidential and should not be shared), and follow the instructions on the screenshot you took. You will just need to turn off the tablet, click to restore, and connect the cable. After a few minutes, you will have the original ZUI 14 software.
Thanks again for the amazing help of our colleague @Fatperman for his exceptional work!
NEW - OPTION THREE:
This is by far the easist way to recover or flash the original ZUI 14 on our TB132FU. DON'T CLICK to Restore before reading all the steps.
Step 1: Download the original ZUI firmware here. Extract the files to a new folder. Password is on the table. Read carefully.
Step 2: Download and log in on the official rescue and smart assistant.
Step 3: Select to rescue your device and select as in the picture below:
Step 4: Click to download the firmware.
Step 5: Wait for the download to be completed until you see START Rescue. But don't click there yet. Don't close the program.
Step 6: Click the donwloads icon at the top and identify the folder where the download was saved.
On mine it was saved at C:\ProgramData\RSA\Download\RomFiles
Step 7: Access and Open the folder of the downloaded firmware and DELETE all files there, but don't delete the folder.
Step 8: Go to the ZUI firmware you downloaded before and copy all files inside the folder. Paste them inside the folder where you just deleted all files.
It should look something like this:
Step 9: TURN OFF YOUR TABLET and Go back to the rescue tool and now click the blue button Start Rescue. Follow the instructions on your screen.
Wait for the tablet to restar and DONE. You recovered or donwloaded the original ZUI on your tablet.
How to debloat my recently installed ZUI 14 and remove the Chinese apps and make it look better?1 - After starting your device, select English and connect to your wifi network.
2 - Once you are set, press the home screen for 3 seconds. Click Desktop Settings.
Switch off the "Left one screen".
Change to "Drawer Style"
3 - Find the setting button and go to General Settings > Language & input > Current Keyboard. Change it to English. (You can download Gboard or another keyboard later)
4 - Go back to the original setting screen and click on the search box. Search for google play services. Click to enable. Then search for Google Play Store and enable it as well.
5 - Before opening the Play store and connecting to your account, go to Apps management and uninstall any apps with Chinese characters you may find. Do not uninstall the HD browser just yet in case you need to download something later. Then restart your device.
6 - Open the Google Play store, and connect your account. Now you can update and download all your apps.
(If you see an error saying Google can't connect please follow the steps in this tutorial)
7 - Unistall HD Browser and done.
How to ROOT my TB132FU running ZUI 14?DISCLAMER: You will lose your data, so backup. It can brick your device if you don't know what to do. You need to know how to use ADB and fastboot commands. The tutorial is for advanced users that knows how to use ADB. Do your research first. If anything goes wrong, flash the ZUI firmware again.
For this tutorial you will need:
Windows computer with all necessary drivers installed
Know how to use ADB
The latest MAGISK manager app.
The latest ZUI firmware for TB132FU
Some minutes to complete all the steps.
Step 1: Go to SETTINGS Menu and click multiple times on your ZUI version. This will give you Developer access.
Step 2: Go General Settings menu > Developer options
Step 3: Click to enable OEM unlocking, also enable debugging mode.
Step 4: Connect your USB cable and run the following command:
adb reboot bootloader
Step 5: Run the fllowing command:
fastboot flashing unlock
On your tablet Click volume UP to unlock your bootloader
Wait for the confirmation on the tablet screen
Step 6: Run command:
fastboot reboot
This will make your tablet restart. Skip all configuarion steps on your tablet and install the latest version of MAGISK on your tablet.
Step 7: On your computer, go to the Firmware folder and copy the file boot.img to your tablet.
Step 8: Open MAGISK and click Select and patch a file. Find the boot.img you copied and patch this file. Wait for the process to be completed.
Step 9: Connect your tablet to your computer and access the folder Downloads in your tablet. There you will see a new boot image Magisk created. Rename that file to boot.img
Step 10: This is the most important step. You will now flash this boot.img file using the following commands:
adb reboot bootloader - to reboot to fastboot
fastboot flash boot boot.img
Wait for it to complete then:
fastboot reboot
Done, your tablet is now rooted. You can install Magisk again and root checker to make sure.
How to UNLOCK the bootloader of my TB132FU running ZUI 14?This will delete all you data
Step 1: Go to SETTINGS Menu and click multiple times on your ZUI version. This will give you Developer access.
Step 2: Go General Settings menu > Developer options
Step 3: Click to enable OEM unlocking, also enable debugging mode.
Step 4: Connect your USB cable and run the following command:
adb reboot bootloader
Step 5: Run the fllowing command:
fastboot flashing unlock
On your tablet Click volume UP to unlock your bootloader
Wait for the confirmation on the tablet screen
Step 6: Run command:
fastboot reboot
Done! Your bootloader is now unlocked.
How to Install and use GOOGLE PLAY on my TB132FU running ZUI 14?First you have to download and install a compatible Google Framework app. Got to APKmirror and search for google framework. Click the one that says Google Services Framework 12. Scroll down and find the version "December 17, 2021 GMT-0300". Install this version. Only this or older version will work. Do not try a different one. It will update automatically eventually.
Then go to settings and search for Google Play and enable the app. Done. You can now log in and use the PLay Store
How to RESTORE lost S/N Seria number?
Step 1 - Go back to ZUI 14. Use one of the options provided in this thread.
Step 2 - Unlock bootloader and OEM. Please refer to the tutorial to unlock the bootloader in this thread.
Step 3 - Once your bootloader is unlocked go and install on your computer MTK META Utility. Link here. Also install HxD here.
Step 4 - Turn off your tablet, disconnect the USB cable and open MTK META.
Step 5 - Click the option Dump NV region. Wait for it to finish reading. It will open a folder.
Step 6 - On the folder that opened, right-click with your mouse the file proinfo.bin and click to open with HxD, or open the software and drag and drop the file there.
Step 7 - Edit the proinfo.bin to add your Serial Number. Change the 12345ABCDE you see to your actual S/N. It's on the back of your tablet on a small sticker.
Step 8 - On the same folder press SHIFT on your keyboard and right-click on an empty space and click OPEN CMD/SHELL terminal here. Or if you use a ADB folder, copy the proinfo.bin file to it so you can flash it.
Step 9 - Turn on your tablet, make sure Debugging is active, connect your tablet to the computer and send these two commands:
adb reboot bootloader
(this will reboot your tablet to fastboot although the line says bootloader)
Once you see the red lines send the command:
fastboot flash proinfo proinfo.bin
And done. You can check in your setting menu if your serial number changed.
Now you can reflash ZUI or the global rom.
thanks man
Great job !
als_bvg said:
How to debloat my recently installed ZUI 14 and remove the Chinese apps and make it look better?
4 - Go back to the original setting screen and click on the search box. Search for google play services. Click to enable. Then search for Google Play Store and enable it as well.
5 - Before opening the Play store and connecting to your account, go to Apps management and uninstall any apps with Chinese characters you may find. Do not uninstall the HD browser just yet in case you need to download something later. Then restart your device.
6 - Open the Google Play store, and connect your account. Now you can update and download all your apps.
(If you see an error saying Google can't connect please follow the steps in this tutorial)
7 - Unistall HD Browser and done.
(Under construction)
Click to expand...
Click to collapse
bro im on zui14 and uninstall all apps, i download the google services and play store but cant still connecting to google account, i dtryed the google installer and stay on 3%... any help?
did it, first intall google services framwork, then google play and restart before log in
Hi can you please guys share the Chinese version of the Lenovo RSA no need for the personal credentials, I tried too contact them as you said but I haven't received any answers thanks
Swanzzl said:
Hi can you please guys share the Chinese version of the Lenovo RSA no need for the personal credentials, I tried too contact them as you said but I haven't received any answers
Click to expand...
Click to collapse
I don't think there's a Chinese version of the software. The credentials are needed. They may be off for the holidays so you will need to wait. Hopefully someone gets back to you during this week. Otherwise I would recommend writing again.
after install zui14 my device show message "orange state" in boot, I can't update even with vpn.
can i lock bootloader after installing zui14 in chinese version? how to proceed?
Yes you can. If anything goes wrong you can do everything again. I Unlocked the bootloader and tried flashing a recovery, bricked the tablet and used the tool to fix again.
ednardo777 said:
after install zui14 my device show message "orange state" in boot, I can't update even with vpn.
can i lock bootloader after installing zui14 in chinese version? how to proceed?
Click to expand...
Click to collapse
als_bvg said:
5 - After one or two days (usually), INSIDE the software you will receive a response with instructions on how to install ZUI more easily. Note: You will not get a response via email, you will receive institutions inside Lenovo’s Rescue and Smart Assistant software.
Click to expand...
Click to collapse
Where do I find the instructions in the software? Do they appear as a notification? p.s. I sent the message (feedback) two days ago and still haven't received a answer.
als_bvg said:
Sim você pode. Se algo der errado, você pode fazer tudo de novo. Desbloqueei o bootloader e tentei fazer uma recuperação, bloqueei o tablet e usei a ferramenta para consertar novamente.
Click to expand...
Click to collapse
thanks man
eamcardoso said:
Where do I find the instructions in the software? Do they appear as a notification? p.s. I sent the message (feedback) two days ago and still haven't received a answer.
Click to expand...
Click to collapse
It will popup as a notification inside the rescue tool. They might be off for the holidays. I'll share another method tonight.
Third method on how to flash ZUI or restore the tablet added to the FAQ. Enjoy! Also Tutorial on how to root the device.
als_bvg said:
Third method on how to flash ZUI or restore the tablet added to the FAQ. Enjoy! Also Tutorial on how to root the device.
Click to expand...
Click to collapse
This method worked for me thanks bro
After unlocking the bootloader every time you boot up the device the following text will be displayed on the screen:
Code:
Orange State
Your device has been unlocked and can't be trusted..
Your device will boot in 5 seconds
To remove this text warning and 5s delay you need to change the file "lk.img" (firmware folder):
Open "lk.img" with a hex editor (for example, HxD)
In menu toolbar click "Search-Find" and select "Hex-values" tab.
Search 08 B5 0E 4B 7B 44 1B 68 1B 68 02 2B
Copy text 08 B5 00 20 08 BD 1B 68 1B 68 02 2B
Return back to hex editor window then right click on the highlighted items and select "Paste Insert"
The newly modified 24 characters will be displayed in red
Click "File" and select "Save".
Flash the modified "lk.img" in fastboot mode
fastboot flash lk lk.img
ZUI_14.0.691
The firmware already includes Google Services Framework.
/system/system_ext/priv-app/GoogleServicesFramework/GoogleServicesFramework.apk
com.google.android.gsf - version 12-7567768
It is disabled by default.
When you turn on "Settings - Apps management - Google Basic Services" the application status changes to enabled (installed).
ug0o said:
After unlocking the bootloader every time you boot up the device the following text will be displayed on the screen:
Code:
Orange State
Your device has been unlocked and can't be trusted..
Your device will boot in 5 seconds
To remove this text warning and 5s delay you need to change the file "lk.img" (firmware folder):
Open "lk.img" with a hex editor (for example, HxD)
In menu toolbar click "Search-Find" and select "Hex-values" tab.
Search 08 B5 0E 4B 7B 44 1B 68 1B 68 02 2BView attachment 5799489
Copy text 08 B5 00 20 08 BD 1B 68 1B 68 02 2B
Return back to hex editor window then right click on the highlighted items and select "Paste Insert"View attachment 5799501
The newly modified 24 characters will be displayed in redView attachment 5799503
Click "File" and select "Save".
Flash the modified "lk.img" in fastboot mode
fastboot flash lk lk.img
Click to expand...
Click to collapse
Nice work! Do you have any idea where the code for text on the picture below might be? Technically, if we are able to find this code and modify it, it should allow us to use the Offical Global rom. I tried to replicate these steps and these steps with no success. I can flash the image using fastboot but the message doesn't disappear.
Protip: The version TB132FU_USR_S000034_2206180119_MPR0_ROW allows the bootloader to remain unlocked. Useful for tests with the Global version
While the version "TB132FU_USR_S000089_2210200620_MPR0_ROW" will lock the bootloader and the commands to unlock will not work.
Let me know if you have any insights.
als_bvg said:
Protip: The version TB132FU_USR_S000034_2206180119_MPR0_ROW allows the bootloader to remain unlocked. Useful for tests with the Global version
While the version "TB132FU_USR_S000089_2210200620_MPR0_ROW" will lock the bootloader and the commands to unlock will not work.
Click to expand...
Click to collapse
I had TB132FU_S000034_220618_ROW installed.
I flashed ZUI 14.0.691.
And now I can't flash any firmware through the flashtool. I can't flash my backup of TB132FU_S000034_220618_ROW.
That's why I'm still on the ZUI 14.0.691.
I'm getting used to it
ug0o said:
I had TB132FU_S000034_220618_ROW installed.
I flashed ZUI 14.0.691.
And now I can't flash any firmware through the flashtool. I can't flash my backup of TB132FU_S000034_220618_ROW.
That's why I'm still on the ZUI 14.0.691.
I'm getting used to it
Click to expand...
Click to collapse
Awesome. Just a note: The fake global was TB132FU_S300062_220921_ROW, and the version we could use to try removing the code is TB132FU_USR_S000034_2206180119_MPR0_ROW. This version is flashable via the Third method on the FAQ. I tried to flash a backup using the Flash Tool and even splitting the dump using Wwr MTK tool and using the third flashing method, but no success with the backup either.
But If we manage to locate the 'Incompatible software' code we could use an official ROM.
NEW: Install official Global ROM on Chinese TB132FU running ZUI 14 or Fake globalDISCLAMER: 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...