[GUIDE][ROOT] QLink Scepter 8 Tablet (Gen 1 & Gen 2) | Bootloader Unlocking & Rooting Guide

Search This thread

Joy28

Member
Jan 21, 2023
48
8
Hi I am stuck here : Download the Magisk patched boot image using the link below and save the file on your PC/laptop in the ADB/Fastboot directory

How do I save there i am not allowed to use flashes nor do I know what and where this directory is...
When I go to type in command it says it cannot find img i didn't change the name its saved to my downloads in desktop automatically ...??

Thank you so much!
 
Last edited:

Viva La Android

Recognized Contributor
Jul 31, 2019
1,523
654
Northeastern Tennessee
LG G Pad 8.3
Moto G
UPDATE: February 9, 2023
I just received the latest firmware builds for both the Gen 1 and Gen 2 models of the Scepter 8. Accordingly, I will be updating the patched boot images in the downloads section when free time permits. Because the upstream Android kernel is backwards compatible with previous versions, the updated boot images will be compatible with any firmware build corresponding to their respective Android release version. In other words, just ensure that you download the patched boot image that matches your Android version: Android 11 (Go Edition) for Gen 1 models; and Android 12 (Go Edition) for Gen 2 models.
 
Last edited:

Viva La Android

Recognized Contributor
Jul 31, 2019
1,523
654
Northeastern Tennessee
LG G Pad 8.3
Moto G
The rooting instructions and download links have been updated with patched boot images corresponding to the latest firmware builds. In addition, to alleviate the possibility of bugs, instabilities and compatibility issues, I have categorized these patched boot images in the form of the CF & MD variants of the Gen 1 model, as well as the CF & MD variants of the Gen 2 model, equating to one boot image for each of the four possible models & variants. To prevent confusion in this regard, I will revise the wording of he guide later today in a manner that simplifies which boot image members need to download based on the model & variant being rooted.
 
Last edited:

vtails

Senior Member
Mar 13, 2012
69
7
Well I have wasted an afternoon trying to get your drivers to work but it looks like a lost cause as I read it seems a lot of people are having same issue . I did as stated cable computer drivers so I had couple friends stop by that do IT they weren’t able to get it to work either and it started with the program 15 second ADB had issues we moved it around to diff computer process of elimination cable drivers program somewhere all the files I got here didn’t want to work for us, but what bothers me is people say they got it but Never say a word about How they got it which I know if I got it to work I’d be laying out how and what order I did it in, but hay you never know maybe someday someone will let the rest of us know how to make all this work, Luck be with you but I’m going to put my toys away for later date …
 
  • Like
Reactions: Viva La Android

Viva La Android

Recognized Contributor
Jul 31, 2019
1,523
654
Northeastern Tennessee
LG G Pad 8.3
Moto G
Well I have wasted an afternoon trying to get your drivers to work but it looks like a lost cause as I read it seems a lot of people are having same issue . I did as stated cable computer drivers so I had couple friends stop by that do IT they weren’t able to get it to work either and it started with the program 15 second ADB had issues we moved it around to diff computer process of elimination cable drivers program somewhere all the files I got here didn’t want to work for us, but what bothers me is people say they got it but Never say a word about How they got it which I know if I got it to work I’d be laying out how and what order I did it in, but hay you never know maybe someday someone will let the rest of us know how to make all this work, Luck be with you but I’m going to put my toys away for later date …
A couple of weeks ago, for the sake of clarity, I done 6 fresh installations of Windows 10 & 11 on 3 different laptops and PCs, installing the drivers from scratch each time. My Scepter 8 was recognized in all six instances with no issues. So there are no issues with the drivers. Your issue is most likely due to a driver conflicts or user error installing and setting up the drivers. The 15 second ADB installer has no issues. I did take the time to test it again to make sure the installer wasn't corrupt.
Honestly, I'd be quite embarrassed to call myself an IT tech and not be able to get a tablet recognized on a PC. They should probably go back to school for a while.
The people on here stating that they got their devices rooted done so by following the instructions, which I have outlined so even a child can follow them. If you're having trouble with things, just ask for sone help. Either myself or another able member will help you. But don't blame the drivers or the guide. This guide has been successfully carried out on hundreds of Scepter 8 tablets. It's tried and true.
 
Last edited:

vtails

Senior Member
Mar 13, 2012
69
7
For the sake of clarity, I have done 6 fresh installations of Windows 10 & 11 on 3 different laptops and PCs, installing the drivers from scratch each time. My Scepter 8 was recognized in all six instances with no issues. So there are no issues with the drivers. Your issue is most likely due to a driver conflicts or user error installing and setting up the drivers. The 15 second ADB installer has no issues. I did take the time to test it again to make sure the installer wasn't corrupt.
Honestly, I'd be quite embarrassed to call myself an IT tech and not be able to get a tablet recognized on a PC. They should probably go back to school for a while.
The people on here stating that they got their devices rooted done so by following the instructions, which I have outlined so even a child can follow them. If you're having trouble with things, just ask for sone help. Either myself or another able member will help you. But don't blame the drivers or the guide. This guide has been successfully carried out on hundreds of Scepter 8 tablets. It's tried and true.
WOW
 
  • Like
Reactions: Viva La Android

Viva La Android

Recognized Contributor
Jul 31, 2019
1,523
654
Northeastern Tennessee
LG G Pad 8.3
Moto G
The
First off the command to disable dmverity is WRONG! You have it : fastboot --disable-verity -- disable-verification FLASH dmverity dmverity.img however, the correct command is: fastboot FLASH --disable-verity --disable-verification dmverity dmverity.img (flash does not need to be in caps, that was just to show where its supposed to be). That screwed me up for a bit.
Second, I don't understand how Magisk is supposed to be installed if it's not flashed to device? Can anyone explain that to me?
Lastly, Is there a custom recovery for this tablet? How about any custom roms?
The command to disable dm-verity is indeed correct. I did double check it just to make sure. Magisk is flashed to the device, by way of the patched boot image you flash via the instructions.
If you follow the instructions to the letter you will unlock your bootloader and achieve root. By the way, you quoted my instructions completely wrong. So if you executed the command per the syntax you quoted, it is definitely incorrect.
This tutorial has worked on dozens of tablets, so my instructions are not all of the sudden incorrect. Your adherence to the instructions, or lack thereof, on the other hand, is the root of your problem (pun intended). Simply follow the instructions in the guide (as I outlined them, and not in the manner you quoted them), and you will achieve bootloader unlocking and root.
 
Last edited:

Viva La Android

Recognized Contributor
Jul 31, 2019
1,523
654
Northeastern Tennessee
LG G Pad 8.3
Moto G
Well it didn't work for me at all until I changed where "flash" was put in the command. I got the info from a post by somebody because he'd received so many complaints about the same command you posted not working so I don't know what to say bout that. I finally got it disbled and got the tablet rooted but I Magisk also did not install.
Thank you for the reply & thank you for your work on rooting this tablet.
Yeah there is more than one way to disable verity. One way is when using an empty vbmeta.img and the other is with using a stock vbmeta.img. So you'll see different commands to disable verity via fastboot. For this guide and vbmeta.img, the command listed is correct. You can actually copy the command and paste it to your command window to make things easier.
Okay once you flash the patched boot image, if the Magisk app doesn't show up when you reboot, download the app from the link provided and install it on your tablet. Then open the app and follow any prompts. (The Magisk root framework is already installed by way of the patched boot image you installed). On a final note, ensure you are flashing the correct patched boot image for your model and variant. It sounds as though you are close to successfully rooting your device. I will try to get you through the process.
 
Last edited:

Viva La Android

Recognized Contributor
Jul 31, 2019
1,523
654
Northeastern Tennessee
LG G Pad 8.3
Moto G
Yes I did. I had to change the flash command & Magisk didn't install but it is rooted.
If Magisk isn't installed you cannot be rooted. Magisk is the root solution, so without it there can be no root access. There is no need to change any flash commands from my instructions. They are 100% correct and have been tried on dozens of tablets. But, unless you have unlocked your bootloader using fastboot, and without Magisk being installed, I am perplexed as to your statement that your device is rooted. Please feel free to post screenshots as proof of your claims.
 
Last edited:

mrdukes

Member
Oct 9, 2022
40
10

QLink Scepter 8 Tablet

By Hot Pepper Mobile
View attachment 5550933
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 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 8
Android 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 8
Android 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 and 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.



💪💪💪
 
  • Like
Reactions: Viva La Android

Viva La Android

Recognized Contributor
Jul 31, 2019
1,523
654
Northeastern Tennessee
LG G Pad 8.3
Moto G
would you be interested in a logcat so we can determine if I'm an idiot or if I found the one of these china tablets that is resisting freedom even though I followed your directions as absolutely perfectly as I humanly could?
I'm not understanding. A logcat for what? Please explain what it is you done and what you're having trouble with. Be detailed with every step you have taken and where you ran into trouble. Moreover, if possible, post a photo of the manufacturer's label on the rear of your tablet. I will cross reference your model and variant to validate that the boot image you flashed is the correct one. Your issue is likewise something very simple. I'll try to help you through the dilemma.
 
Last edited:
I'm not understanding. A logcat for what? Please explain what it is you done and what you're having trouble with. Be detailed with every step you have taken and where you ran into trouble. Moreover, if possible, post a photo of the manufacturer's label on the rear of your tablet. I will cross reference your model and variant to validate that the boot image you flashed is the correct one. Your issue is likewise something very simple. I'll try to help you through the dilemma.
I'm trying again right now, been busy all day chasing fillys across hell and gone since assbags don't know how to not drive through 2 4' barb wire fences... will update shortly. I have a Scepter8 SER# CF2210AP15095396 running BigdroidOS 2.0.0.131 (Android 12 GO build#v03-20220809) and set it up last time with Owner enabled via AllianceSHIELD X so I'm setting up naked and unlocked this time to see if that was the problem with some access denied script entries in the LogCat (crash dump logs)

THREE attempts have now been made at full speed from dead cold stock boot to nothing but a blank, black screen, I updated firmware to the v1 version, on your fimware recovery page and followed every. single. step. verbatim and i get the same result every time///\\\

GOT IT
 
Last edited by a moderator:
  • Like
Reactions: Viva La Android
Out of curiosity, what was the dilemma exactly?
dud brain betray thinking human sleepy and tried to use files from ****ty spreadtrum tablet was sitting me next to... **** I NEED MORE SLEEP AND LESS COFEVE

Speaking of Spreadtrum/UNISOC, is there any chance you'd be able to get your hands on a Maze Speed t8 tablet and tackle getting the bootloader unlocked on one of those bass turds? I've tried just about everything and can't even put a chink (pun intended) in the armor their "custom ROM" has built around that poor little bootloader.

also, this tablet in particular calls itself a "phone" lol
 
  • Like
Reactions: Viva La Android

Top Liked Posts

  • There are no posts matching your filters.
  • 6

    QLink Scepter 8 Tablet

    By Hot Pepper Mobile
    scepter_8_front.png

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



    3
    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.
    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.
    3
    Bootloader is unlocked but my battery died after the factory reset, so I’m just waiting for a few more to flash the patched image file. But idk what I did differently, I started from a fresh win10 install and just installed 15 second adb again like before and it all worked this time.
    ROOT Successful
    2
    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...
    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.
    2
    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