Related
Stock firmware
Rogers B05 Firmware
https://www.androidfilehost.com/?fid=1395089523397891291
Separate Firehose download
https://www.androidfilehost.com/?fid=1395089523397891292
ZTE Kernel source mirror (We are codenamed Helen)
https://www.androidfilehost.com/?fid=1395089523397891289
Here is a step by step guide on how to flash the stock rom with QFIL and by extension any image.
Download and install the Qualcomm drivers from here
Download the firmware from above
Extract the firmware to a folder that you can easily access them from like your desktop
Download and install QPST from here
Open the QFIL application (Find it in your start menu)
In the "Select Build Type" field select Flat Build
In the "Select Programmer" field navigate to the folder you extracted the firmware and support files to and select the prog_emmc_firehose_8909.mbn file
Select the "Load XML" button and navigate to the folder you extracted the firmware and support files to and select the rawprogram0.xml and then the patch0.xml when prompted.
Plug in your tablet
Run the following adb command "adb reboot edl" (Now the screen should be blank but the led light should be red)
If the text at the top of the QFIL application says "No Port Available" click the "Select Port..." option and pick your device. If your device isn't showing up there you didn't install the drivers properly.
Click the Download Button to begin flashing your device
So the above explains how to flash everything if you want to flash just boot or recovery use the tool in the 2nd post it is a lot easier
Warning
This is a dangerous tool. It can render your device permanently unusable. If you use it, your warranty will likely be void. You accept all responsibility for the consequences.
Acknowledgments
Special thanks to @tdm for taking the firehose I got and creating the k81tool with it!
Note Well
The first rule of intelligent tinkering is to save all the parts.
Always backup your partitions before writing new contents, so that you can get back to where you started.
Never write both boot and recovery in one session. Always make sure that you can boot into the other partition in case something fails.
Preparation
Download magisks patched boot.img from here.
Download k81tool from here.
Setup your computer.
Setup for Windows
Download zadig.
Boot your device in EDL mode (see below).
Windows will want to install the Qualcomm USB driver. We won't be using it so cancel.
Run zadig. Find device 05c6:9008 and install the WinUSB driver for it.
Reboot your device and rerun steps to go back to EDL mode
Booting in EDL mode
Code:
adb reboot edl
Usage
Code:
k81tool.exe <read|write> <boot|recovery> <filename>
Example:
Code:
k81tool.exe read boot stock-boot.img
Code:
k81tool.exe write boot patched_boot.img
Multiple Operations
This is a "one-shot" tool. After performing an operation, it will reset the device with a 5 second countdown. If you wish to perform multiple operations (eg. backup, flash), simply re-enter EDL mode.
Common Problems
Device was not found
First enter EDL mode, then run the tool.
Device is visible in device manager but cannot be found by the tool.
Connect directly to the PC, not through a hub.
Windows says bad file descriptor
The WinUSB driver is not installed.
Once you flash the patched_boot.img all you need to do is install the magisks manager and you will have root enjoy!
Proof of root:
{
"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"
}
Place Holder for TWRP
bad links??
Hi
First, thank-you, thank-you, thank-you x 100. I've been looking for a method to root this device from the day I got it as an add on to my cell plan. Not sure if I am missing something but when I click on the androidfilehost links I get taken to a home page but there is no file to download for all three links. Initially I thought I might have to register so I did that but the links still just take you to the Home advert page Could you update the links when you get a chance - thanks !!
edit - I have a couple of questions -As you have been the first to root the device there are obviously no custom firmware builds available so we stick with stock, correct? We will be able to remove the bloatware on stock because it's rooted though, correct? I also use tasker and the AutoApps suite for automation and I need root for some of my tasks so this is a huge step in the right direction. Lastly in order to root the device do we need to do follow all steps in the first post and then complete the steps in the second post? Or is the second post just a different way to do what was done in post 1? I'm excited to root this so thanks for fixing those links! Thanks again for all your work.
ryanoc75 said:
Hi
First, thank-you, thank-you, thank-you x 100. I've been looking for a method to root this device from the day I got it as an add on to my cell plan. Not sure if I am missing something but when I click on the androidfilehost links I get taken to a home page but there is no file to download for all three links. Initially I thought I might have to register so I did that but the links still just take you to the Home advert page Could you update the links when you get a chance - thanks !!
Click to expand...
Click to collapse
Sorry about that somehow the links broke, I have updated them so now they are proper.
Hey guys. Having a little trouble. I keep on running into "Failed: unknown error" when I try to flash the patched boot.img that was provided. I managed to read the stock boot image with no problems, but writing just runs into this error.
Thoughts?
I am using the Bell variant so I hope that isn't the source of it
Post Root questions
Hi
I'm about to try to root the device, assuming it goes according to plan, can we then install SuperSU? Do we need a TWRP for the device if we want to install another ROM and are there generic ROMS out there that would work on this tablet? Sorry if these are noob questions, I've been an apple jailbreaker for years and just bought and rooted and installed a custom ROM on a Samsung Galaxy S4. I installed a new android tablet NAV in my BMW and I needed a device to act as a hotspot, so I use Tasker and AutoApps with it to automate the process and it works really well. When I rooted the Galaxy S4 there are a ton of ROMS available for every variant so it was easy to follow the instructions. However, this is totally new territory for me. This device isn't nearly as popular so I wondered what options are available to us once we have it rooted?
same issue failed unknown error
Hi
I am using the Rogers K81 and I am encountering the same failed unknown error when I try to write the patched boot file. I also was able to read the firmware file without issue. I rebooted into edl mode and then tried to write the patched file -
NB - for those who have yet to try, move the k81tool.exe and the patched boot file to your c drive and make sure your at the root of c and then remove the B05 in the patch file name so that it can find the file if you are just cutting and pasting the command line instructions above, otherwise you'll get an error that it can't find the file. If the k81tool.exe isn't in the current directory you are in you will get an error saying k81tool.exe is not a known command ..etc.etc. This might seem obvious to some but for those with little command line experience, it will save you from having to post questions about your errors.
There is a product ZTE primetime K92 which is a successor of a ZTE K81.
Do you plan to support root for ZTE Primetime K92?
huaji2333 said:
There is a product ZTE primetime K92 which is a successor of a ZTE K81.
Do you plan to support root for ZTE Primetime K92?
Click to expand...
Click to collapse
A friend of mine has the k92, and currently it has a locked bootloader even with the firehose and all. So he is working to find an exploit to allow it to be unlocked. But no ETA at this time.
Sent from my iPhone using Tapatalk
Thank you for providing this. I have the Virgin Mobile device currently. Just a question before I try this. My past experience with a tablet from Rogers a few years ago was that whenever you put a different sim card in, it would force you to reset the entire device. To get around this, I was lucky that there were other generic firmware available for that device. Does the Rogers firmware that you provide force a reset if you change the sim? I'd ideally like to have the option to change sims when traveling. Thanks.
I own a Virgin Mobile Canada ZTE K81 tablet. As much as I like a rooted device, my goal, if possible, is to replace the Bell firmware with the Rogers firmware. The reason I would want to do this is because Bell has done some nasty things with this tablet. The SIM card is IMEI locked to this tablet, I cannot use the SIM card on anything else. So I decided this tablet could be used as a wifi hotspot. Unfortunately, Bell did something to the firmware to make wifi and bluetooth tethering impossible.
I guess the other question I have is will the IMEI lock still work on this Bell tablet after the Rogers firmware is installed?
wow i didn't think development for this device would've gotten this far already. we're gonna need our own device forum soon
---------- Post added at 12:20 PM ---------- Previous post was at 12:19 PM ----------
bridonca said:
I own a Virgin Mobile Canada ZTE K81 tablet. As much as I like a rooted device, my goal, if possible, is to replace the Bell firmware with the Rogers firmware. The reason I would want to do this is because Bell has done some nasty things with this tablet. The SIM card is IMEI locked to this tablet, I cannot use the SIM card on anything else. So I decided this tablet could be used as a wifi hotspot. Unfortunately, Bell did something to the firmware to make wifi and bluetooth tethering impossible.
I guess the other question I have is will the IMEI lock still work on this Bell tablet after the Rogers firmware is installed?
Click to expand...
Click to collapse
imei locks are independent of the device itself. you need to get the carrier to give you an unlock code
Online Gravy said:
wow i didn't think development for this device would've gotten this far already. we're gonna need our own device forum soon
---------- Post added at 12:20 PM ---------- Previous post was at 12:19 PM ----------
imei locks are independent of the device itself. you need to get the carrier to give you an unlock code
Click to expand...
Click to collapse
I got Bell to IMEI lock the SIM to another, better tablet, a LG G Pad IV 8.0 FHD (LGV533) from Fido. The SIM works perfectly, I can now wifi tether!
That makes it an easier choice to hack at the Bell K81, now that the IMEI lock is not tied to this K81 tablet anymore. If the Bell K81 works with the Rogers firmware, bonus. If it bricks, not the end of the world. My data plan will still work. I just need to find the time to do the hack!
bridonca said:
I got Bell to IMEI lock the SIM to another, better tablet, a LG G Pad IV 8.0 FHD (LGV533) from Fido. The SIM works perfectly, I can now wifi tether!
That makes it an easier choice to hack at the Bell K81, now that the IMEI lock is not tied to this K81 tablet anymore. If the Bell K81 works with the Rogers firmware, bonus. If it bricks, not the end of the world. My data plan will still work. I just need to find the time to do the hack!
Click to expand...
Click to collapse
I have flashed my Bell k81 with Rogers firmware and it works properly.
Sent from my iPhone using Tapatalk
any chance of getting Pie GO installed on this thing, mine lags to even tap and the stock settings leave only 400mb free of ram
I can't successfully flash the rogers firmware on the VM (Bell) device. When the flashing process gets to 'reading through the sparse file' for the userdata.img file, I get an error. The log reads:
{ERROR: sparse_open:1939 Didn't properly read the sparse_header!
If I delete this file as a test (not sure if that was a good idea), it continues on to reading the ddr.img file, but halts again and the error refers to this file being 0 bytes.
I may have missed a step. When is the kernel file used? Is the Rogers firmware file complete?
s_021 said:
I can't successfully flash the rogers firmware on the VM (Bell) device. When the flashing process gets to 'reading through the sparse file' for the userdata.img file, I get an error. The log reads:
{ERROR: sparse_open:1939 Didn't properly read the sparse_header!
If I delete this file as a test (not sure if that was a good idea), it continues on to reading the ddr.img file, but halts again and the error refers to this file being 0 bytes.
I may have missed a step. When is the kernel file used? Is the Rogers firmware file complete?
Click to expand...
Click to collapse
Delete DDR as well and any of the ones it complains about that are empty. When I have sometime I'll upload a new package with those removed.
Decided to try the k81tool to just root instead, but I'm getting the same Failed:unknown error as others have posted.
(Using VM stock firmware)
---------- Post added at 11:20 PM ---------- Previous post was at 11:14 PM ----------
If you put in a Rogers sim, does it attempt to do a hard reset or just the usual reboot?
thanks
deadman96385 said:
I have flashed my Bell k81 with Rogers firmware and it works properly.
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
deadman96385 said:
Delete DDR as well and any of the ones it complains about that are empty. When I have sometime I'll upload a new package with those removed.
Click to expand...
Click to collapse
Deleting the files also fails. The error is {ERROR: handleProgram:8615 'ddr.img' not found. You could possibly try --notfiles=ddr.img,OtherFileToSkip.bin (note, exiting since you specified --noprompt)
Adding back ddr.img, the error is
{ERROR: handleProgram:8666 Filesize is 0 bytes. This is usually a mistake!! Please check 'C:\ZTE\rogers\ddr.img'
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.
Hi there,
So After seen many tutorials I wanted to proceed to unlock the bootloader of my Huawei Mediapad T5 , here are the specs
```
Model: AGS2-W09
Build No: AGS2-W09 8.0.0.360(OCEC431)
CPU : Hisilicon Kirin 659
Android Version: 8.0
```
I have downloaded the last build of `potatoNV` along with the SER Drivers ,
I have booted in untrusted driver mode (on Win10) and have installed `usbser.sys` as far as I recall
I proceed opening the Tablet from inside and shorting the "short point" and I get connection with the Computer , I installed the drivers , and tried on `potatoNV` with `Kirin 65x (A)` .
I get to the end of the progress bar , and then I get the problem as there is no confirmation that the process has been performed correctly. The connection dissapears , and If I try to boot on rescue mode and I do `.\fastboot.exe devices` or `fastbook.exe oem device info` it doesnt show no device at all.
Also the `rescue mode` menu says `Phone locked , FRP Unlocked` So I guess I had no luck
Please see the video on the link (note that the 2 takes are not synchronized)
doubt-mediapadt5-bootloaderunlock.mp4
drive.google.com
What I may be possibly doing wrong ? May it be the USB connection (cables or connectors) ? or the drivers I downloaded?
Please any assitance will be appreciated.
Thanks
Maybe I can help you with this. Recently rooted this tab myself. Please give me a reminder tomorrow
Hey there I just saw the message . Please if you can guide me a bit of what I may be doing wrong? Also If there is a way to share the Drivers files that you used that would be great (I'm not sure if it was a matter of drivers or general clumsiness , please If you have a minute to check the video tell me what may be wrong on my "Technique") Thank you!!
freddieventura said:
Hey there I just saw the message . Please if you can guide me a bit of what I may be doing wrong? Also If there is a way to share the Drivers files that you used that would be great (I'm not sure if it was a matter of drivers or general clumsiness , please If you have a minute to check the video tell me what may be wrong on my "Technique") Thank you!!
Click to expand...
Click to collapse
Just saw your responce now (please use reply next time, I will get an notification then ).
The "Kirin 65x (A)" you've used is the correct bootloader. So guess it would have been something going on with the drivers or the procedure.
I recently (about 1 month ago) rooted this tab myself so I think I will have quite recent files for doing so. Maybe I can send them to you if you like. But I should have save the websites where I got them from too. But need to check it up for you then.
{
"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"
}
Did you have used the settings above?
You did had recieved the "New unlock code" message?
I have to go to work now, but I could help you further later this evening if you need further assistance
Rockel said:
Just saw your responce now (please use reply next time, I will get an notification then ).
The "Kirin 65x (A)" you've used is the correct bootloader. So guess it would have been something going on with the drivers or the procedure.
I recently (about 1 month ago) rooted this tab myself so I think I will have quite recent files for doing so. Maybe I can send them to you if you like. But I should have save the websites where I got them from too. But need to check it up for you then.
View attachment 5391207
Did you have used the settings above?
You did had recieved the "New unlock code" message?
I have to go to work now, but I could help you further later this evening if you need further assistance
Click to expand...
Click to collapse
Hi, thanks for assisting me. Yeah well, the version I used of PotatoNV(the last build) just had the option of Disable FBlock so I did that.
Also I tried wth a previous build that was showing both versions as you are showing and it happened the same thing.
My guess are more focused on 2 probable mistakes by my side either:
- When shorting the short point Im not doing it correctly. (not sure if this, as the device gets detected by PotatoNV and initiates the process)
- (Most likely thisone). Wrong drivers, I have downloaded them through a link found in a youtube video, and the video was not specific about this Tablet. Also there were a bunch of drivers within the same file so I installed one that looked like the correct one (but not 100% sure)
Anyways thanks for taking your time really and appreciate a reply but always whenever you find free time obviously. Take it easy today at work
freddieventura said:
Hi, thanks for assisting me. Yeah well, the version I used of PotatoNV(the last build) just had the option of Disable FBlock so I did that.
Also I tried wth a previous build that was showing both versions as you are showing and it happened the same thing.
My guess are more focused on 2 probable mistakes by my side either:
- When shorting the short point Im not doing it correctly. (not sure if this, as the device gets detected by PotatoNV and initiates the process)
- (Most likely thisone). Wrong drivers, I have downloaded them through a link found in a youtube video, and the video was not specific about this Tablet. Also there were a bunch of drivers within the same file so I installed one that looked like the correct one (but not 100% sure)
Anyways thanks for taking your time really and appreciate a reply but always whenever you find free time obviously. Take it easy today at work
Click to expand...
Click to collapse
Not sure, I should get into it again, but I'm not sure of potato is able to start the procesure or finding the divice if not shorted correctly.
Do you have a screenshot of your potato output/ results?
How are you performing the shorting procedure?
I can see if I can look for you for the right drivers tonight.
Rockel said:
Not sure, I should get into it again, but I'm not sure of potato is able to start the procesure or finding the divice if not shorted correctly.
Do you have a screenshot of your potato output/ results?
How are you performing the shorting procedure?
I can see if I can look for you for the right drivers tonight.
Click to expand...
Click to collapse
I hve uploaded the video which shows all the output and how Im shorting the point. The video though is composed by two takes and are not synced in time but that is how I do it.
doubt-mediapadt5-bootloaderunlock.mp4
drive.google.com
Let me know if you can watch it on there. Thanks
freddieventura said:
I hve uploaded the video which shows all the output and how Im shorting the point. The video though is composed by two takes and are not synced in time but that is how I do it.
doubt-mediapadt5-bootloaderunlock.mp4
drive.google.com
Let me know if you can watch it on there. Thanks
Click to expand...
Click to collapse
Oh yes, forgot about the video in the OP...
Seems you're folowing the wrong procedure with the shorting proces.
And seems your potato version is a bit outdated. But don't think this will be much of an issue.
- Your tablet needs to be turned off.
- cable removed from the tab.
- start potato
- then short the circuit (tab turned off).
- keep it shorted and insert the usb cabel (the other end should be in the computer already)
- the tablet starts (i believe in somekind of flash mode. And i believe you should not be able to see the Huawei logo in this procedure).
- after 2 or 3 seconds after booting, release the shorted circuit.
- i believe it should display you now some info about the tab itself in potato when you press start.
P.s. Don't forget to make a screenshot of the results or write down the newly given unlock code. So you can use it afterwards to lock or unlock your bootloader at a later moment, without opening the tab again.
P.s. 2 I just read in your comment that the recordings are not synchronised. So it's possible you were following the correct steps above. Correct me if I'm wrong please
freddieventura said:
I hve uploaded the video which shows all the output and how Im shorting the point. The video though is composed by two takes and are not synced in time but that is how I do it.
doubt-mediapadt5-bootloaderunlock.mp4
drive.google.com
Let me know if you can watch it on there. Thanks
Click to expand...
Click to collapse
I'm home (finally)...
If the steps mentioned above didn't worked out, I would like to ask you to do axactly as I did. Just unlocked my Mediapad T5 just 1 month ago or so, so everything I've used should be recent enough I guess.
First:
- Un-install your potato version.
- Un-install your Mediapad T5 USB drivers.
So we can begin from scratch
Also:
- turn on OEM-unlock and USB-debugmode in developer settings.
I asume you have a decent and working ADB version installed on your PC?
If not, or when you're not sure, uninstall it too.
I was using the Minimal ADB and Fastboot from here:
[TOOL]Minimal ADB and Fastboot [2-9-18]
Introduction ADB and Fastboot are arguably two of the most indispensable tools used when working with Android devices. If you really want to modify, debug, and tweak along with their countless uses in rooting, and other procedures ADB and...
forum.xda-developers.com
Then:
1) Install the Huawei USB drivers from here:
Support area | files.dc-unlocker.com
(this) or (this) are the "official" sites I got this from.
2) Install the latest version of PotatoNV from here:
GitHub - mashed-potatoes/PotatoNV: Unlock bootloader of Huawei devices on Kirin 960/95х/65x/620
Unlock bootloader of Huawei devices on Kirin 960/95х/65x/620 - GitHub - mashed-potatoes/PotatoNV: Unlock bootloader of Huawei devices on Kirin 960/95х/65x/620
github.com
Open potatoNV and use these settings marked in red:
3) Plug the USB-cable into your PC already, but don't connect the other side to the tablet. And make sure your tablet is turned off.
4) Now short the testingpoint with a shielded part. I just used a thick copper wire and used it between testingpoint and metalshield just next to it. Metal pliers as used in your video should work too ofcourse.
P.S. I see that you also disconnected your screen in the video? It seems that it's verry important not to see a charging icon in the next step, so maybe it's better to connect it again for this step.
5) While still shorting the testingpoint with the shield, connect the USB cable to your tablet and be sure no charging icon pops up (This can be a bit difficult doing on your own. Easiest way is to have someone around te help in this step). After a few secconds when connected (without seeing an charging icon) remove the shorting between testingpoint and shield.
6) Make sure that the Huawei USB COM is selected in PotatoNV (and that the other settings are the same as the screenshot)
7) And pres "Start!"
8) You should get similar results now:
PotatoNV v2.2.1
User manual: https://kutt.it/pnv-en
Verifying images...
Uploading hisi65x_a...
- xloader
- fastboot
Waiting for any device...
Connecting...
Serial number: FQB***************
Board ID: FQB*************
Model: AGS2-W09
Build number: AGS2-W09 8.0.0.360(OCEC431)
FBLOCK state: unlocked
Saved key: 6BN**************
Writing FBLOCK...
Writing WVLOCK...
Writing USRKEY...
Rebooting...
New unlock code: 3BS*************
p.s. In your video it seemed your device got disconnected somehow while uploading. You should not see that "timeout" message here now annymore.
9) Make a screenshot of your results, copy them to a text file or write down at least your "new unlock code"
So you won't have to open your tablet annymore in the future. You can use this newly obtained unlock code now to lock and unlock your tablet without opening again.
10) You should now see a warning screen everytime you reboot the tab. It warns you about that the device can't be trusted annymore because of the unlocked bootloader.
You can also enter Fastboot to check it
Fastboot/ Bootloader mode:
1. Turn off the device by holding the Power key for a few seconds.
2. Connect tablet to PC/laptop using the USB-cable.
3. Hold down Volume-Down.
4. Hold down the Power button until device starts (while still holding Volume-Down and USB connected).
4. Tablet boots now into Fastboot-mode.
You should see the following screen then (pay attention on the 2 red lines at the bottom):
You can close your tablet now!
Rockel said:
I'm home (finally)...
If the steps mentioned above didn't worked out, I would like to ask you to do axactly as I did. Just unlocked my Mediapad T5 just 1 month ago or so, so everything I've used should be recent enough I guess.
First:
- Un-install your potato version.
- Un-install your Mediapad T5 USB drivers.
So we can begin from scratch
Also:
- turn on OEM-unlock and USB-debugmode in developer settings.
I asume you have a decent and working ADB version installed on your PC?
If not, or when you're not sure, uninstall it too.
I was using the Minimal ADB and Fastboot from here:
[TOOL]Minimal ADB and Fastboot [2-9-18]
Introduction ADB and Fastboot are arguably two of the most indispensable tools used when working with Android devices. If you really want to modify, debug, and tweak along with their countless uses in rooting, and other procedures ADB and...
forum.xda-developers.com
Then:
1) Install the Huawei USB drivers from here:
Support area | files.dc-unlocker.com
(this) or (this) are the "official" sites I got this from.
2) Install the latest version of PotatoNV from here:
GitHub - mashed-potatoes/PotatoNV: Unlock bootloader of Huawei devices on Kirin 960/95х/65x/620
Unlock bootloader of Huawei devices on Kirin 960/95х/65x/620 - GitHub - mashed-potatoes/PotatoNV: Unlock bootloader of Huawei devices on Kirin 960/95х/65x/620
github.com
Open potatoNV and use these settings marked in red:
View attachment 5391609
3) Plug the USB-cable into your PC already, but don't connect the other side to the tablet. And make sure your tablet is turned off.
4) Now short the testingpoint with a shielded part. I just used a thick copper wire and used it between testingpoint and metalshield just next to it. Metal pliers as used in your video should work too ofcourse.
View attachment 5391623
P.S. I see that you also disconnected your screen in the video? It seems that it's verry important not to see a charging icon in the next step, so maybe it's better to connect it again for this step.
5) While still shorting the testingpoint with the shield, connect the USB cable to your tablet and be sure no charging icon pops up (This can be a bit difficult doing on your own. Easiest way is to have someone around te help in this step). After a few secconds when connected (without seeing an charging icon) remove the shorting between testingpoint and shield.
6) Make sure that the Huawei USB COM is selected in PotatoNV (and that the other settings are the same as the screenshot)
7) And pres "Start!"
8) You should get similar results now:
PotatoNV v2.2.1
User manual: https://kutt.it/pnv-en
Verifying images...
Uploading hisi65x_a...
- xloader
- fastboot
Waiting for any device...
Connecting...
Serial number: FQB***************
Board ID: FQB*************
Model: AGS2-W09
Build number: AGS2-W09 8.0.0.360(OCEC431)
FBLOCK state: unlocked
Saved key: 6BN**************
Writing FBLOCK...
Writing WVLOCK...
Writing USRKEY...
Rebooting...
New unlock code: 3BS*************
p.s. In your video it seemed your device got disconnected somehow while uploading. You should not see that "timeout" message here now annymore.
9) Make a screenshot of your results, copy them to a text file or write down at least your "new unlock code"
So you won't have to open your tablet annymore in the future. You can use this newly obtained unlock code now to lock and unlock your tablet without opening again.
10) You should now see a warning screen everytime you reboot the tab. It warns you about that the device can't be trusted annymore because of the unlocked bootloader.
You can also enter Fastboot to check it
Fastboot/ Bootloader mode:
1. Turn off the device by holding the Power key for a few seconds.
2. Connect tablet to PC/laptop using the USB-cable.
3. Hold down Volume-Down.
4. Hold down the Power button until device starts (while still holding Volume-Down and USB connected).
4. Tablet boots now into Fastboot-mode.
You should see the following screen then (pay attention on the 2 red lines at the bottom):
View attachment 5391639
You can close your tablet now!
Click to expand...
Click to collapse
Thanks very much for your explanation , I will do this when I am back at home and let you know .
Cheers!!
freddieventura said:
Thanks very much for your explanation , I will do this when I am back at home and let you know .
Cheers!!
Click to expand...
Click to collapse
Are you btw sure that the pliers you used in in the video are making a circuit from one point to the other? Maybe worthwile to measure the resistance first?
I just used a thick copper wire and bended it to an easy to use U-shape.
Rockel said:
Are you btw sure that the pliers you used in in the video are making a circuit from one point to the other? Maybe worthwile to measure the resistance first?
I just used a thick copper wire and bended it to an easy to use U-shape.
Click to expand...
Click to collapse
Sorry Rockel I have been very busy this week , I'm gonna try and find a little bit of time to get this done this weekend . Thank you!!
freddieventura said:
Sorry Rockel I have been very busy this week , I'm gonna try and find a little bit of time to get this done this weekend . Thank you!!
Click to expand...
Click to collapse
No problem, take your time. Hope these steps wil solve your problem. Please keep me informed when you have time
Rockel said:
No problem, take your time. Hope these steps wil solve your problem. Please keep me informed when you have time
Click to expand...
Click to collapse
Do angels wear capes? because I haven't seen yours .
Much much much appreciate your help with this, I have just done it perfectly it didn't take me much time to do it.
Whatever I was doing wrong (probably the drivers , probably the shorting point thing not doing it properly) , whatever who cares!!.
I was also a bit not confident to do it that's why it took me time to get into doing it , but you definitely coached me with your messages .
Really thanks very much Rockel . For anything we keep in touch mate
freddieventura said:
Do angels wear capes? because I haven't seen yours .
Much much much appreciate your help with this, I have just done it perfectly it didn't take me much time to do it.
Whatever I was doing wrong (probably the drivers , probably the shorting point thing not doing it properly) , whatever who cares!!.
I was also a bit not confident to do it that's why it took me time to get into doing it , but you definitely coached me with your messages .
Really thanks very much Rockel . For anything we keep in touch mate
Click to expand...
Click to collapse
Hehehehe, thanks for your nice responce!
So I asume You've managed to root unlock the device now!
It was a pleasure assisting you in this.
If you need anny other information regarding this rooted device, please let me know. I'm not a pro with this. But had to solve a few problems myself. And came there with the help of others aswell.
What is the use of New unlock code?
do anyone have system, boot, cust, recovery, userdata.img with you i want to try with multi-tool to unbrick my tab
The unlock code can be used to unlock bootloader (using something like "adb oem unlock <code>" from PC)
I have saved the OTA folder form huawei system update app just before updating from 8.0.0.320(C432) to 8.0.0.371(C432), it can be found in /data/HwOUC folder after updater finished downloading. This version cannot be found on HuaweiFirmwareFinder site but I have temporary shared then here. Perhaps we could contact the authors to upload this version.
You can later use HuaweiFirmwareExtractor to extract different images from the zip files (no clue why there are 3 of them).
You need to disable "Verify Header checksums" in the "Settings" to open the extracted update.app files from the zips.
Good luck!
denzelcris said:
The unlock code can be used to unlock bootloader (using something like "adb oem unlock <code>" from PC)
I have saved the OTA folder form huawei system update app just before updating from 8.0.0.320(C432) to 8.0.0.371(C432), it can be found in /data/HwOUC folder after updater finished downloading. This version cannot be found on HuaweiFirmwareFinder site but I have temporary shared then here. Perhaps we could contact the authors to upload this version.
You can later use HuaweiFirmwareExtractor to extract different images from the zip files (no clue why there are 3 of them).
You need to disable "Verify Header checksums" in the "Settings" to open the extracted update.app files from the zips.
Good luck!
Click to expand...
Click to collapse
thank you .. but i extract app didnt uderstand which img file to install there no exact name for boot.img, recovery.img, cust.img, can you plz tell me which file equal to those file..
I don't think Huawei has boot.img or recovery.img, they may have a different layout and names (someone correct me if I'm wrong). I know the equivalent of boot.img is ramdisk.img or kernel.img (I flash both when restoring to be sure) and recovery should be recovery_ramdisk.img. The names from HuaweiExtractor should match with the images. Cust.img can be found in the other zip: update_full_AGS2-W09_hw_eu.
There is also this partition layout table which I don't know how it works for Huawei but I know that it may change for different firmwares so it is usefull to have remembered what version you had previously or use a safe tool to flash that also.
QLink Scepter 8 TabletBy Hot Pepper Mobile
{
"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"
}
Bootloader Unlocking
& Rooting Guide
For Gen 1 & Gen 2 Models
TABLET MODELS & VARIANTS:
For those members familiar with the firmware restoration thread, there are a total of four model variants of the QLink Scepter 8 tablet: two variants of the Gen 1 model, and two variants of the latest Gen 2 model. Determining which Scepter 8 you have is a very simple two-part check. First, if you don't already know your Android OS version, go to device Settings> About tablet, and locate your Android version. If you are running Android 11 (Go Edition), you have the original Gen 1 model. If you are running Android 12 (Go Edition), your tablet is the latest Gen 2 model. Secondly, you will need to locate the device S/N in order to determine your tablet variant. Your S/N is printed on the manufacturer's label affixed to the exterior of the tablet's rear housing. From the Android OS, you can also locate your S/N by opening device Settings>About tablet>Model. Regardless of whether you have the Gen 1 or the Gen 2, the first two letters of your S/N will be either CF or MD. This is the codification of your tablet variant. To alleviate some of the legwork of rooting, and to keep this thread simple to follow, I have provided boot images pre-patched for Magisk v25.2 systemless root support. I have categorized the download links for each of the boot images in accordance with the respective model and S/N variant. To avoid potential bugs, instabilities, boot loops and the like, it is crucial that you download the boot image that corresponds with your model & variant. OVERVIEW:
This guide outlines step-by-step instructions for unlocking the bootloader and rooting all variants of the Gen 1 & Gen 2 QLink Scepter 8 tablet. This guide also includes a detailed section on properly installing the ADB, fastboot, & USB device drivers on your Windows PC or laptop, as well as steps to troubleshoot & manually update these drivers in the event the tablet is not being recognized while in fastboot mode.
DISCLAIMER:
Unlocking your bootloader and rooting your device are both procedures that carry inherent risks. Because these procedures involve modifying the device from it's stock factory configuration, it is possible to corrupt, damage, or even render your tablet completely inoperable. By proceeding further, you are assuming sole responsibility for the integrity and operability of your device, therefore absolving me of any liability in the event something goes south. I have, however, tested these guides and feel confident that things will go smoothly as long as you follow the instructions carefully. Moreover, I encourage all members to read the instructions fully before starting the steps, in order to first gain a fundamental understanding of the concepts and methods involved.
PLEASE PLAY NICE & FOLLOW XDA RULES:
This thread was created with the intent of being a noob-friendly forum. This simply means that new and inexperienced members are fully welcome here, and will be provided with extra guidance and assistance if needed. Please keep in mind that XDA is a global community of developers, enthusiasts and device users. As such, and although English is the only permitted language in the forums & threads, not all members speak English as their first language, and often rely on text translation tools when asking questions & posting. Accordingly, it is very common for words to be misconstrued, meanings to be misinterpreted, and the context as a whole lost in translation. I ask members to be patient, compassionate and respectful to others on this thread. Those members with the knowledge to do so are urged and asked to help newer members, and recall back when you were new here and others helped you.
Please help me with keeping this thread on point by ensuring that all subject matter herein be kept relevant to the topics of rooting and OEM unlocking the QLink Scepter 8. Any posts about other devices or subject matter run afoul of XDA rules and are subject to removal by moderators -- and potential sanctions imposed upon the offending member. Moreover, an on-topic thread keeps things organized and easier to follow. Thank you for your consideration.
PREREQUISITES:
To unlock the bootloader and root the QLink Scepter 8 tablet, you will need a laptop or PC running on Windows 7/8.1/10/11. (A Mac or Linux machine can also be used. For purposes of this guide, however, I am focusing on a Windows setup.) You will also need the OEM-supplied or a quality equivalent micro USB to USB-A data sync cable. Last but not least, you will need to install compatible USB device drivers for ADB & Fastboot on your PC/laptop. I have included the 15-Second ADB Driver Installer below, under the DOWNLOADS section. This Installer will configure ADB & Fastboot system-wide, and installs the universal Google USB device drivers. I would encourage members to first read the instructions in their entirety prior to actually starting the guide.
•INSTALLING USB DEVICE DRIVERS•
This section is included to install and configure ADB, Fastboot and the proper USB device drivers on your Windows computer. This section can also be used to troubleshoot and fix issues involving your tablet not being recognized by Windows while connected in fastboot mode. If you have already installed the ADB & Fastboot tools (& the proper USB device drivers), and you are not experiencing fastboot recognition issues, you may skip this section and proceed to the bootloader unlocking section.
Many members have reported issues with device recognition while in fastboot mode. I have also noticed a persistence problem with Windows drivers on this tablet. I can manually update the driver using Windows Device Manager, enabling fastboot recognition; yet, once the tablet is disconnected from my PC the updated driver does not always persist, requiring a manual driver update each time fastboot mode is needed. Follow these steps to enable fastboot recognition of your device.
• 1. If you have not yet done so, install the 15-Second ADB Installer from the link below on your Windows PC or laptop. Open the utility and follow the prompts to install the ADB & Fastboot drivers. Next, opt to install ADB system-wide. Lastly, you will be prompted to install the Google USB device drivers. Select Y and install them. You should see an interface informing you that the drivers were successfully installed. NOTE: If you get a warning notification that the drivers are unsigned, select the option to install anyway;
• 2. With your tablet powered off, hold the Power and Volume Down buttons simultaneously until the QLink logo appears, at which time you release the Power button but continue holding Volume Down. When a green Android graphic appears on your display, you are in fastboot mode;
• 3. Connect your tablet to your Windows machine using the OEM-supplied or a quality equivalent micro USB to USB-A data sync cable;
• 4. Open a command window in the path of your ADB/Fastboot directory. Execute this command:
Code:
fastboot devices
If properly connected, the command window will return an alphanumeric string which is synonymous with your tablet serial number. If this occurs, you are finished with this section and may proceed to the instructions for unlocking the bootloader/rooting. If the command window displays Waiting on Any Device, or if your serial number is not displayed, continue with the following steps;
• 5. Keeping your device connected to your Windows PC/laptop, right click your Windows Start icon and select Device Manager. Locate your tablet in the menu. It will likely be located under either the Portable Devices or Android Device heading;
• 6. Right click your device and select Update Driver. Next, select Browse My Computer for Drivers. On the next screen choose the option for Let Me Pick From a List... Now you will see a list of drivers to select from. Depending on the manner in which Windows recognized your tablet in the Device Manager menu, the driver selection menu can vary. If you see an option for Android Device, select that option and then select Android Composite ADB Interface. Or, you may be directly presented with options for Android Bootloader Interface, Android ADB Interface and Android Composite ADB Interface. In any event, choose Android Composite ADB Interface and then click Next. Click Yes in the Update Driver Warning dialogue screen, at which time the drivers will be installed.
• 7. Return to your command window and again execute the fastboot devices command. If your serial number is displayed, your drivers are now properly installed. If you are still experiencing fastboot recognition issues, try using another data sync cable, change USB ports on your computer, and/or reinstall the drivers using the 15-Second ADB Installer.
I. UNLOCKING THE BOOTLOADER:
If you plan on rooting your tablet, this step is mandatory. If your bootloader is already unlocked and you only wish to root your device, skip down to the rooting instructions in the next section below.
WARNING: Unlocking your bootloader forces the device into a factory data reset, which will effectively wipe all saved user data from the device. Make a backup at this point if there are files and media on your tablet that you wish to keep.
INSTRUCTIONS:
1. Enable Developer Options on your tablet by going to device Settings>About tablet and tap Build number approximately seven times. Android will notify you that Developer Options are enabled; this menu will appear under device Settings>System>Advanced.
2. Enable USB Debugging and OEM Unlocking in the Developer Options menu. NOTE: Users have reported the OEM Unlocking option being greyed-out unless you are signed in to your Google account.
3. Now to boot into fastboot mode, and this particular step is extremely important. Android 10 introduced a new fastboot mode for dynamic partitions, known as FASTBOOTD, which is relocated from the bootloader to userspace. This particular fastboot mode supports resizeable partitions within the dynamic scheme, and enables the user to create, resize and delete various logical partitions. However, FASTBOOTD mode cannot be utilized to unlock the bootloader, and will not recognize the unlock command. As such, the user must rely upon legacy fastboot mode in order to unlock the bootloader. From stock recovery mode, you may simply choose the option to reboot to bootloader. DO NOT CHOOSE THE OPTION TO ENTER FASTBOOT, as this option will boot to FASTBOOTD. From the Android OS, you can boot into legacy fastboot mode by executing:
Code:
adb reboot bootloader
Once you see a green Android graphic appear in the center of your display, you are in the correct fastboot mode.
4. Connect your tablet to your PC/laptop using the OEM-supplied or a quality equivalent micro USB to USB-A data sync cable. Next, open a command window in the path of your ADB/Fastboot directory. Check your connection by executing this command:
Code:
fastboot devices
If you are properly connected, the command window will return an alphanumeric string synonymous with your device's serial number. If you do not see this, there is a problem with communications between your tablet and PC/laptop. To troubleshoot the issue, switch to another USB port, try another data sync cable, and/or reinstall the ADB/Fastboot drivers on your PC or laptop. Also, see my instructions above on installing USB device drivers on your Windows computer;
5. Once a proper connection has been verified, execute this command:
Code:
fastboot oem unlock
Once you see the Okay notification in the command window, your bootloader is now unlocked. Execute this command:
Code:
fastboot reboot
Your tablet will now initiate a factory data reset and then reboot into the initial setup for the Android OS.
II. ROOTING THE QLINK SCEPTER 8
Now that the bootloader has been unlocked, rooting this tablet is very straightforward. Again, I have provided pre-rooted boot image files in the DOWNLOADS section for all four models & variants.
INSTRUCTIONS:
A. Gen 1 QLink Scepter 8Android 11 (Go Edition)
NOTE: If your tablet is running Android 12 Go Edition, you're in the wrong place. Skip down to the next section.
1. Download the Gen 1 patched boot image that matches your S/N variant using the links below, and save the file on your PC/laptop in the ADB/Fastboot directory. Note that the file is named patched_boot.img. The flashing command below assumes that you leave this file name unchanged;
2. Go to device Settings>About tablet and tap Build number 7 times or until Developer Options are enabled. (This step is necessary if you unlocked your bootloader using the previous section, due to the factory data reset.) Enable USB Debugging in the Developer Options menu;
3. Power your tablet off. Hold the Power and Volume Down keys simultaneously until the QLink logo appears, at which time you release Power but continue holding Volume Down. The green Android will appear on the display to indicate fastboot mode;
4. Connect your tablet to your PC or laptop using a quality data sync cable. Verify your connection using the instructions in Step 4 of the bootloader unlocking section above;;
5. Once a solid connection is verified, execute these commands:
Code:
fastboot flash boot patched_boot.img
fastboot reboot
NOTE: Your active boot slot should be boot_a. Regardless, the above command flashes your active slot by default, without having to specify slot _a or _b.
Upon reboot, your tablet will be rooted with the latest Magisk systemless root strategy. If you do not see the Magisk app or the placeholder stub in your app drawer, go ahead and download the latest version from the link below and install the APK on your tablet. Open the Magisk app, grant the prompted permissions, and follow any prompts to complete setting up the root environment.
B. Gen 2 QLink Scepter 8Android 12 (Go Edition)
NOTE: If your tablet is running Android 11 Go Edition, you're in the wrong place. Go back to the previous section. .
1.Download the Gen 2 patched boot image that matches your S/N variant and the empty vbmeta.img using the links below, and save the files on your PC/laptop in the ADB/Fastboot directory. Note that the boot image file is named patched_boot.img, and the vbmeta image is named vbmeta.img. The flashing commands below assume that you leave these file names unchanged;
2. Go to device Settings>About tablet and tap Build number 7 times or until Developer Options are enabled. (This step is necessary if you unlocked your bootloader using the previous section, due to the factory data reset.) Enable USB Debugging in the Developer Options menu;
3. Power your tablet off. Hold the Power and Volume Down keys simultaneously until the QLink logo appears, at which time you release Power but continue holding Volume Down. The green Android will appear on the display to indicate fastboot mode;
4. Connect your tablet to your PC or laptop using a quality data sync cable. Verify your connection using the instructions in Step 4 of the bootloader unlocking section above;;
5. Once a solid connection is verified, execute this command:
Code:
fastboot flash boot patched_boot.img
Now, continuing in fastboot mode, you will need to disable dm-verity/Android Verified Boot (AVB) by flashing an empty vbmeta.img via executing the following command:
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
Next, execute this command to reboot your device:
Code:
fastboot reboot
Upon reboot, your tablet should now be rooted with the Magisk systemless root strategy. If you do not see the Magisk app or the stub placeholder in your app drawer, go ahead and download the latest version from the link below and install it on your tablet. Open the Magisk app, grant the prompted permissions, and follow any prompts to update Magisk and/or complete setting up the root environment.
IMPORTANT NOTE:
In the unfortunate event you have a mishap with rooting your tablet and get stuck in a boot loop, or if your tablet will not otherwise boot into the Android OS, have no worries. My tutorial on firmware restoration for the QLink Scepter 8 will revert your device back to its original stock factory state. You can then return here and give it another try.
QLink Scepter 8 Firmware Restoration Guide
DOWNLOADS:
• 15-Second ADB Installer
• Gen 1 (CF) Patched Boot Image
• Gen 1 (MD) Patched Boot Image
• Gen 2 (CF) Patched Boot Image
• Gen 2 (MD) Patched Boot Image
• Empty vbmeta.img
• Official Magisk Releases / GitHub Repo
THANKS & MENTIONS:
Thanks goes out to Hot Pepper Mobile CEO Shawn Sun and Support Specialist Joshua G for providing stock firmware images for this device.
Also, I wish to recognize and thank @13lack13ox for being a huge help to thread members at times when I was not able.
For some reason, I'm stuck on the part where you have to use the fastboot option. So basically, I got my tablet in fastboot mode (the secondary one with the green android graphic), but when I tried to use the adb function, it doesn't detect my tablet. And also, the command, "fastboot devices" doesn't do anything, and when I try to use "fastboot device" it just says waiting for any device and just... stays there, not detecting my tablet. I tried multiple computers, tried both PowerShell and the command prompt with admin privileges, to no avail. For information, it worked when my tablet was on my tablet is the V9 firmware, but it slightly newer since I just updated to V9_20220224... so maybe that might have something to do with it...
64Star said:
For some reason, I'm stuck on the part where you have to use the fastboot option. So basically, I got my tablet in fastboot mode (the secondary one with the green android graphic), but when I tried to use the adb function, it doesn't detect my tablet. And also, the command, "fastboot devices" doesn't do anything, and when I try to use "fastboot device" it just says waiting for any device and just... stays there, not detecting my tablet. I tried multiple computers, tried both PowerShell and the command prompt with admin privileges, to no avail. For information, it worked when my tablet was on my tablet is the V9 firmware, but it slightly newer since I just updated to V9_20220224... so maybe that might have something to do with it...
Click to expand...
Click to collapse
Sounds like you have a common driver issue. Do this: with your device connected to your PC in fastboot mode, right click your Windows start button and open Device Manager. What is your tablet showing up as? We will need to update your driver. I can walk you through it. Did you install the Google driver from the 15-Second ADB Installer? I am nearly finished writing a guide on properly installing the device drivers. I will link it here when posted. It will give you a detailed step-by,-step outline. I don't think it's an issue with the firmware builds. Fastboot detection issues are common with this tablet due to some type of instability with driver persistence. For example, I often need to update my driver every time I use fastboot mode because, for some odd reason, the updated driver doesn't persist once the tablet is disconnected from the PC and then reconnected.
i dont have this tablet but another hot pepper device called the poblano. with that i was able to boot into ffbm from the bootloader and have root adb access. then i ran dd on my boot partition and patched it with magisk and flashed it back
wondering if hot pepper still makes their devices like that or they patched it. either way props to you for getting the fw straight from the oem
luridphantom said:
i dont have this tablet but another hot pepper device called the poblano. with that i was able to boot into ffbm from the bootloader and have root adb access. then i ran dd on my boot partition and patched it with magisk and flashed it back
wondering if hot pepper still makes their devices like that or they patched it. either way props to you for getting the fw straight from the oem
Click to expand...
Click to collapse
The Scepter 8 does not ship with adb root shell (adbd) enabled. In fact, the bootloader was not even intended to be unlocked. The unlock command is disabled in standard fastboot mode. Luckily, the Scepter 8 is integrated with a second fallback fastboot mode, which we were able to use to to the oem unlock.
Many AllWinner tablets and other Chinese devices do, as you pointed out on your Hot Pepper device. When the Scepter 8 was first released I was able to pull a boot image using a Phoenix Suite tool that had been reverse engineered and modded. As luck would have it, I got rid of the tablet and lost my files along with access to the Phoenix Suite tool. So I've been weeks quarreling with Hot Pepper Mobile to provide firmware and the kernel source code. To their credit, the Hot Pepper CEO and support team were very helpful once they understood what I needed. Hot Pepper's software developers are in China, so a language translation issue hindered my request for some time.
Anyway thank you for your kind words and it is a pleasure making your acquaintance.
@64Star I have updated the thread above with some detailed instructions on updating your device drivers. Hope this helps.
Viva La Android said:
@64Star I have updated the thread above with some detailed instructions on updating your device drivers. Hope this helps.
Click to expand...
Click to collapse
It does, I've unlocked the bootloader and now i'm gonna go root it. Thanks for your help!
I have an unfortunate update: When I went to turn on my tablet, I've noticed there was a noticeable crack on the top left corner of the screen... and then when I tried to use it... the touchscreen no longer functions. I have no clue where that crack came from, cause that wasn't there yesterday, and I've kept it safe in a drawer until now, so I have no clue how it's possible. Guess the software isn't the only thing that's cheap, cause my 2020 Moto G Power survived way worse without even a single crack.
TL,DR: Touch screen somehow broke overnight, meaning I can't get past the setup screen, so GG no re, this $10 qlink tablet ****ing sucks.
64Star said:
I have an unfortunate update: When I went to turn on my tablet, I've noticed there was a noticeable crack on the top left corner of the screen... and then when I tried to use it... the touchscreen no longer functions. I have no clue where that crack came from, cause that wasn't there yesterday, and I've kept it safe in a drawer until now, so I have no clue how it's possible. Guess the software isn't the only thing that's cheap, cause my 2020 Moto G Power survived way worse without even a single crack.
TL,DR: Touch screen somehow broke overnight, meaning I can't get past the setup screen, so GG no re, this $10 qlink tablet ****ing sucks.
Click to expand...
Click to collapse
@64Star I hate to hear that but I know exactly how it goes. I've cracked many a screen in my day. But, on a positive note, if you have the extra funds, there are a ton of these tablets available on eBay within the $35 to $40 price range.
Viva La Android said:
@64Star I hate to hear that but I know exactly how it goes. I've cracked many a screen in my day. But, on a positive note, if you have the extra funds, there are a ton of these tablets available on eBay within the $35 to $40 price range.
Click to expand...
Click to collapse
LOL really turning a profit!
13lack13ox said:
LOL really turning a profit!
Click to expand...
Click to collapse
Haha. No doubt
Sorry about the delay on TWRP guys. My mounting issues are actually encryption issues. TWRP isn't decrypting the /userdata or /vendor partitions with the default key. I'm going to chat with one of my friends over at TeamWin and see if I can get a little guidance.
Viva La Android said:
@64Star I hate to hear that but I know exactly how it goes. I've cracked many a screen in my day. But, on a positive note, if you have the extra funds, there are a ton of these tablets available on eBay within the $35 to $40 price range.
Click to expand...
Click to collapse
You really expect me to shell out around 35$ to 40$ on a slow, laggy 10$ tablet just to experiment on? Hahahahahaha....
Spoiler
Perhaps
64Star said:
You really expect me to shell out around 35$ to 40$ on a slow, laggy 10$ tablet just to experiment on? Hahahahahaha....
Spoiler
Perhaps
Click to expand...
Click to collapse
Not really. I was only providing you info as to where they were available. I found one for $19 which is more than I really wanted to give.
As it stands now,.all the lag is gone in mine. I debloated everything that wasn't essential for normal operations. Then I edited the system/build.prop to increase responsiveness and I limited background apps & processes. Finally, I installed a kernel tuner and set the LMK to very aggressive, tweaked the I/o scheduler parameters, and increased entropy from the available pool. And set SELinux to permissive mode. I'm using Nova Launcher Premium with the launcher locked into memory. Believe it or not, the tablet is now very responsive considering the specs. I'm looking into overclocking the CPU a bit, but 1.46 GHz seems to suffice once RAM is optimized. It's a difference in night and day. It's good for a project tablet but that's about it.
There's another government tablet floating around called the Maxwest Nitro 7Q. 4G/LTE supported with a lot better specs. I think I have one located to buy for cheap.
Lots of tweaks it doesnt run too bad just removing bloatware. Would be cool to get your params on your tweaks etc. If you ever got time could you post it up? Maybe the rom you were talking about in another post has all that included? Anyways if not no biggie, this thing is just for playing around on.
13lack13ox said:
Lots of tweaks it doesnt run too bad just removing bloatware. Would be cool to get your params on your tweaks etc. If you ever got time could you post it up? Maybe the rom you were talking about in another post has all that included? Anyways if not no biggie, this thing is just for playing around on.
Click to expand...
Click to collapse
Absolutely. I'll list those for you here in just a little bit. I have a pure stock ROM built with a TWRP installer, but my TWRP has run into a snag. I've reached out to TeamWin for guidance on that.
All in good time, man. Just glad someone with knowledge is doing all this. Wish I could help more. My ability to program and compile is equivalent to stick poking. I've done it once with aosp 6 that was awhile ago.
13lack13ox said:
All in good time, man. Just glad someone with knowledge is doing all this. Wish I could help more. My ability to program and compile is equivalent to stick poking. I've done it once with aosp 6 that was awhile ago.
Click to expand...
Click to collapse
You seem to know your way around the Android OS pretty well. I'm a developer in training myself. Learning every day. Yeah AOSP 6, I still love working with the Marshmallow builds.
Ok first things first. I notice a huge performance boost from some kernel level mods. Here is a link to Kernel Toolkit. Install both APKs. https://mega.nz/folder/QYwA0QTA#O_Zg3h_iVkHOdeyU_yOmLw
First go to the CPU heading and change the scaling governor to Ondemand. Under CPU Governor Params, tap on Performance Profile and select Maximum Performance (you may personally want to scale back to Aggressive or Balanced, depending on your need for battery life). Now, close Kernel Toolkit and restart the app. Next go to the I/O heading. Choose kyber as the I/o scheduler and set the read ahead buffer to 512 KB. Go down to ZRAM and increase to the maximum of 1000 MB. Set Swappiness to 100. Go over to the Profiles heading, create a profile will all settings and give it a name recommended from the list. When complete, tap on the profile, select save settings and then apply settings.
Now go to the menu button in the upper left of the app. Go down and enable Apply Settings on Boot. Select All and set a 5 second delay.
Next, download a build.prop editor from Play Store. There are tons of free ones and any will suffice. Make a backup of your system/build.prop before you tweak anything. Open the editor and grant root permission.
For build.prop edits, locking your launcher into memory helps a lot with responsiveness. Add this line to system/build.prop
ro.HOME_APP_ADJ=1
This basically prevents the launcher from being killed by Android's native LMK.
To increase touch responsiveness, add these lines as well.
debug.performance.tuning=1
video.accelerate.hw=1
Disable the boot animation for faster boot time.
debug.sf.nobootanimation=1
Reboot to enable the tweaks.
Give these a try and let me know your feedback. I'm working on a few more mods to optimize this tablet and I'll keep you posted on those as well.
Thx great changes so far. Yeah more "snappyness" for sure. I'll have to play around and open up as much as i can swap around.
I can't change I/O scheduler though, I get a contact developer message.
13lack13ox said:
Thx great changes so far.
Click to expand...
Click to collapse
Yw. Do you notice a decent improvement?
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...