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

Search This thread

ParODime710

Member
Apr 5, 2022
11
5
@ParODime710, if you have not yet had success on unlocking the bootloader, I'll be glad to walk you through a step-by-step troubleshooting session via Telegram or sone other platform that will enable us to correspond in real time. Just let me know.
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.
 
  • Like
Reactions: 13lack13ox
QLINK Scepter 8 Tablet

View attachment 5550933
Guide for Unlocking the
Bootloader & Rooting

OVERVIEW:
After a rather lengthy back-and-forth colloquy with Hot Pepper Mobile, we have finally been given access to factory firmware images for this tablet. To Hot Pepper Mobile's credit, most of the delay way due to a language translation issue regarding English to Chinese.
This guide will focus on two primary tasks: (1) unlocking the Scepter 8 bootloader; and (2) rooting the Scepter 8 using the latest stable release of Magisk. For purposes of this guide, we will be using the latest v9 firmware. If you have not yet updated to v9, head on over to my thread on restoring & upgrading the Scepter 8 firmware here Firmware Restoration Guide


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, and thus absolve 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 simple instructions.

PLEASE PLAY NICE & FOLLOW 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. As such, 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 topic by keeping all subject matter herein 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.


FIRMWARE SPECS:
OS/Version: Android 11 (Go Edition)
Build #: Scepter_8_Tablet_V9_20220221
Kernel Version: Linux v5.4.99
Android Security Patch: 02/05/2022
Build Date: February 21, 2022
API Level: 30
Partition Scheme: Dynamic

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 heading. This Installer will install ADB & Fastboot system-wide, as well as the Google USB device drivers.

•INSTALLING USB DEVICE DRIVERS•
This step is optional and only needs to be followed if you are having issues with your tablet being recognized by Windows while connected in fastboot mode.
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. Opt to install ADB system-wide. Next 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 step and may proceed with this guide. 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 wish to root your device, skip down to the rooting instructions 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 oem 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 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
Once the bootloader has been unlocked, rooting this tablet is very straightforward. To simplify this guide, I am providing a pre-rooted boot image file in the DOWNLOADS section below. This boot image has been patched with the latest stable Magisk systemless root script.
INSTRUCTIONS:
1. Download the Magisk patched boot image using the link 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 stub 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 complete setting up the root environment.

DOWNLOADS:
15-Second Driver Installer v1.5.6
Magisk Patched Boot Image
Magisk GitHub Official Releases


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, thanks to @EmmaDearest for taking the initiative to extract the firmware and for preparing a pre-rooted boot image. Also, a big thanks to @13lack13ox for being a huge help to thread members at times when I am not able.


It appears that the link for V9 is broken and unusable. Any suggestions?
 

rkbest

Member
Oct 12, 2007
18
0
Is there a custom rom or vanilla android that i can install on this. Followed your guide to root the bootloader and reset to stock. but I still see shipped apps installed or the laggy launcher that i want to get rid of? I haven't been using android since long so have lost touch on how to get rid of the bloatware. Any help is appreciated.
 

Moxiipc

Senior Member
I just received this tablet today in the mail and it seems even though We're using the same os we're on different builds. I think I am on a older build and wonder if this method will work on my build or do I need to update?

Specs
Android Version 11 Go
Android Security Update: June, 5th 2021
Kernel Version 5.4.99 june 18th 2021
Build number: Scepter_8_tablet_V4_20210618
 

Viva La Android R.I.P.

Recognized Contributor
Jul 31, 2019
1,648
751
Northeastern Tennessee
LG G Pad 8.3
Moto G
@Moxiipc, indeed this method should work regardless of your firmware build. I would encourage you, however, to first update to the V9 firmware prior to unlocking and rooting your tablet. Although it is not required, per se, the V9 build is more stable and responsive than previous builds.
The V9 firmware package and step-by-step upgrading tutorial can be found here https://xdaforums.com/t/guide-firmw...firmware-restoration-upgrading-guide.4412585/
Should you wish to unlock and root without upgrading your firmware, simply follow the instructions in this thread. But, keep in mind that applying OTA updates after rooting will be problematic. To subsequently update your firmware, it will be necessary to revert to a full stock configuration by manually upgrading the firmware, and then rooting your device again.
 
Last edited:

Viva La Android R.I.P.

Recognized Contributor
Jul 31, 2019
1,648
751
Northeastern Tennessee
LG G Pad 8.3
Moto G
For members with a Windows PC or laptop who are experiencing persistent problems with achieving bootloader unlocking or rooting via this guide, I am creating an alternative tutorial for a live Linux distro (FWUL), which can be booted from a DVD or USB drive on a Windows machine. This method requires no installation of USB device drivers or ADB & Fastboot drivers, which are already integrated within the live Linux distro by default.
 
  • Like
Reactions: Alkuam

Moxiipc

Senior Member
@Moxiipc, indeed this method should work regardless of your firmware build. I would encourage you, however, to first update to the V9 firmware prior to unlocking and rooting your tablet. Although it is not required, per se, the V9 build is more stable and responsive than previous builds.
The V9 firmware package and step-by-step upgrading tutorial can be found here https://xdaforums.com/t/guide-firmw...firmware-restoration-upgrading-guide.4412585/
Should you wish to unlock and root without upgrading your firmware, simply follow the instructions in this thread. But, keep in mind that applying OTA updates after rooting will be problematic. To subsequently update your firmware, it will be necessary to revert to a full stock configuration by manually upgrading the firmware, and then rooting your device again.
Your thread worked like a charm as well as your other thread you posted I updated to V9 and successfully rooted my device thank you very much! I did run into a driver issue with windows not recognizing it and as you mentioned in your thread it does happen & every time I plug my device to my pc I need to go to device manager and set it so it recognizes it for some reason. I am running on windows 7 and it was a little confusing for just a moment to figure out which usb was the tablet when you said "It will likely be located under either the Portable Devices or Android Device heading" since after following all the instructions it wasn't coming up in device manager but I figured it out it was coming up as "USB Developer" and once I followed your instructions with updating the driver boom no problem adb was able to read the device and I was able to sucessfully root it!


I have cleaned out almost all the bloatware apps to speed it up. You seem to have a lot of experience with this device so there are more questions I have.

There are system apps I am curious to remove but do not know if there will be any impact on my device so I am looking to know what the purpose of these apps are and is it safe to remove!
--------------------------------------------------------------------------------------------------------
• Allwinner
com.softwinner.theme.icon

• Allwinner
com.softwinner.theme.color

• Allwinner Package Override Application
com.allwinner.tech.packageoverride

• Android R Easter Egg
com.android.egg

• AwlogSettings
com.softwinner.awlogsettings

• Basic Daydreams
com.android.dreams.basic

• Bookmark Provider
com.android.bookmarkprovider

• com.android.providers.partnerbookmarks (app name & package folder)

• com.google.android.overlay.gmsconfig.assistantgo (app name & package folder)

• com.google.android.overlay.gmsconfig.gallerygo (app name & package folder)

• com.google.android.overlay.gmsconfig.go (app name & package folder)

• com.softwinner.settingsetup (app name & package folder)

• ConfigUpdater
com.google.android.configupdater

• Contacts Storage
com.android.providers.contacts

• Device Setup
com.google.android.apps.work.oobconfig

• Gboard
com.google.android.inputmethod.latin

• Google One Time Init
com.google.android.onetimeinitializer

• Google Partner Setup
com.google.android.partnersetup

• Google Sample Home Screen
com.google.android.gmsintergration

• Intent Filter Verification Service
com.android.statementservice

• Market Feedback Agent
com.google.android.feedback

• Sim App dialog
com.android.simappdialog

I mention these specifically because I am curious if removing them will cause any problems and I am also curious to know what the purpose of these apps. Some of them I know already but this is also good information for the public to know. The more you know *chimes* can be a great source of info for beginners and those seeking the info.

I also am curious of methods to speed this up I saw a post somewhere in the pages with you talking about making edits to the build.prop. (I will find it later when I am ready to tinker around) If I wanted to go almost completely google-less the minimum being just the play store & it's play services what else am I able to do to accomplish this? I would like to replace Gboard with something more privacy I don't know if touchwiz or something from samsung could be installed to replace the keyboard but I would like to know what I could replace it with?
 
Last edited:

Viva La Android R.I.P.

Recognized Contributor
Jul 31, 2019
1,648
751
Northeastern Tennessee
LG G Pad 8.3
Moto G
@Moxiipc that's great news that everything went smoothly. I assume you must have a fair amount of experience with Android modding, as most of the inexperienced members have difficulties on these guides to begin with. Allwinner powered devices are a bit distinct from other, more widely used chipsets in terms of modding and flashing methods. Either way, I commend your achievements on the Scepter 8.
So yes, after upgrading, unlocking.and rooting your tablet, it's certainly time to debloat unwanted apps, tweak some default parameters, and get this tablet running more smoothly. On the list of system apps you outlined, I noticed that the first five were vendor specific apps (except the Easter Egg app; it's a hidden game within the OS that you can safely uninstall). The apps with Allwinner referenced in the name are key to normal function of the tablet. Leave those alone. The Basic Daydreams app is your native interactive screensaver mode. Since it's a normal function within the OS and involves the display, leave it untouched. Almost all the rest of the apps you listed are components of the preinstalled Google Mobile Services (GMS) ecosystem. You can remove any of these you like, but keep in mind that removing core GMS components will have an impact on the Google app or service corresponding to the system app you uninstall. Experiment around with uninstalling these apps. If you inadvertently uninstall ah app that negatively affects another app or service that you use, you can always flash V9 again and fully restore your tablet to stock. The Google component apps with "overlay" in the package name are theme configurations for whichever app contains the overlay. Again, while safe to uninstall, the direct impact to related apps and services could prove unsatisfactory to your preferences.
One app you didn't list that you definitely want to uninstall is the preinstalled QLink WiFi autoconnect service that claims to connect you to thousands of free WiFi access points throughout the country. This service has an ulterior motive, however; it constantly collects "analytical data" from your device and sells that data to the highest bidder. This includes copious info about your location (it constantly tracks you) and even info about your browsing habits, interests, and personal data. Moreover, this service can turn your WiFi on automatically.at any time and against your wishes. It consumes a substantial amount of RAM and processing power, too. You will notice am immediate improvement once you uninstall it. I can't recall the package name off top, but you should know it when you see it.
When uninstalling system apps on this tablet, keep in mind that it uses the Dynamic partition scheme, meaning that your /system, /vendor and /product partitions are integrated into one /super partition. So you must use an app or file manager with dynamic partition support. I recommend using MiXplorer file manager (free of charge and ad free). It will allow you access to the logical partitions where your preinstalled apps are stored. You can go to apkmirror.com and search for MiXplorer. You will need to download the apk, install it, and go to app settings to enable root support. Preinstalled apps are in multiple directories. Here are the paths:
/system/app
/system/priv-app
/system-ext/app
/system-ext/priv-app
/product/app
/product/priv-app

For tweaking kernel parameters and build.prop values, you can follow the mods I laid out in the thread section you are referring to. Again, dynamic partitions complicate things. Use MiXplorer to manually edit the build.prop versus using an unsupported app, which will soft brick your device. I realize this is rather a lot of info. I likely won't be on XDA for a couple of days because I'm traveling for work. So if I don't reply to you in a timely manner, I haven't forgotten you. Good news is, these Allwinner devices are almost impossible to hard brick. They have a hardware embedded BROM bootloader protocol, so restoring the firmware is almost always an option if you mess up. I'll be putting a comprehensive guide together soon for modding the stock Android OS for optimal performance. I'm also actively porting LineageOS 18.1 for this tablet.
Good luck and talk to you soon.
 
Last edited:
  • Like
Reactions: Alkuam

Viva La Android R.I.P.

Recognized Contributor
Jul 31, 2019
1,648
751
Northeastern Tennessee
LG G Pad 8.3
Moto G
Is there a custom rom or vanilla android that i can install on this. Followed your guide to root the bootloader and reset to stock. but I still see shipped apps installed or the laggy launcher that i want to get rid of? I haven't been using android since long so have lost touch on how to get rid of the bloatware. Any help is appreciated.
Android 10 introduced dynamic partitions. Because the Scepter 8 runs on Android 11 Go Edition, dynamic partitioning is the standard. This done away with the mounting of logical partitions and combines key partitions into one larger /super partition. This changes the game on uninstalling system apps. See my post to @Moxiipc above for much more info on this and how to debloat your stock OS.
 

Moxiipc

Senior Member
@Moxiipc that's great news that everything went smoothly. I assume you must have a fair amount of experience with Android modding, as most of the inexperienced members have difficulties on these guides to begin with. Allwinner powered devices are a bit distinct from other, more widely used chipsets in terms of modding and flashing methods. Either way, I commend your achievements on the Scepter 8.
So yes, after upgrading, unlocking.and rooting your tablet, it's certainly time to debloat unwanted apps, tweak some default parameters, and get this tablet running more smoothly. On the list of system apps you outlined, I noticed that the first five were vendor specific apps (except the Easter Egg app; it's a hidden game within the OS that you can safely uninstall). The apps with Allwinner referenced in the name are key to normal function of the tablet. Leave those alone. The Basic Daydreams app is your native interactive screensaver mode. Since it's a normal function within the OS and involves the display, leave it untouched. Almost all the rest of the apps you listed are components of the preinstalled Google Mobile Services (GMS) ecosystem. You can remove any of these you like, but keep in mind that removing core GMS components will have an impact on the Google app or service corresponding to the system app you uninstall. Experiment around with uninstalling these apps. If you inadvertently uninstall ah app that negatively affects another app or service that you use, you can always flash V9 again and fully restore your tablet to stock. The Google component apps with "overlay" in the package name are theme configurations for whichever app contains the overlay. Again, while safe to uninstall, the direct impact to related apps and services could prove unsatisfactory to your preferences.
One app you didn't list that you definitely want to uninstall is the preinstalled QLink WiFi autoconnect service that claims to connect you to thousands of free WiFi access points throughout the country. This service has an ulterior motive, however; it constantly collects "analytical data" from your device and sells that data to the highest bidder. This includes copious info about your location (it constantly tracks you) and even info about your browsing habits, interests, and personal data. Moreover, this service can turn your WiFi on automatically.at any time and against your wishes. It consumes a substantial amount of RAM and processing power, too. You will notice am immediate improvement once you uninstall it. I can't recall the package name off top, but you should know it when you see it.
When uninstalling system apps on this tablet, keep in mind that it uses the Dynamic partition scheme, meaning that your /system, /vendor and /product partitions are integrated into one /super partition. So you must use an app or file manager with dynamic partition support. I recommend using MiXplorer file manager (free of charge and ad free). It will allow you access to the logical partitions where your preinstalled apps are stored. You can go to apkmirror.com and search for MiXplorer. You will need to download the apk, install it, and go to app settings to enable root support. Preinstalled apps are in multiple directories. Here are the paths:
/system/app
/system/priv-app
/system-ext/app
/system-ext/priv-app
/product/app
/product/priv-app

For tweaking kernel parameters and build.prop values, you can follow the mods I laid out in the thread section you are referring to. Again, dynamic partitions complicate things. Use MiXplorer to manually edit the build.prop versus using an unsupported app, which will soft brick your device. I realize this is rather a lot of info. I likely won't be on XDA for a couple of days because I'm traveling for work. So if I don't reply to you in a timely manner, I haven't forgotten you. Good news is, these Allwinner devices are almost impossible to hard brick. They have a hardware embedded BROM bootloader protocol, so restoring the firmware is almost always an option if you mess up. I'll be putting a comprehensive guide together soon for modding the stock Android OS for optimal performance. I'm also actively porting LineageOS 18.1 for this tablet.
Good luck and talk to you soon.
Yes I didn't mention the Qlink Wifi Autoconnect because that was the first system app I uninstalled then App services and when I did that oh it was mad every bloatware app was installing till I removed it. You should a seen the tablet lagging out as 30 apps were being installed at once from the app services. Lol I stopped it but it took some time to uninstall all the apps it installed.

Also thank you again you answered my next question before I was going to ask it. I was going to say I uninstalled these apps but they still come up in application inspector just says underneath not installed for this user and when I go to app info it just stays stuck on computing. There are no other users unless theres a hidden profile like the Serrano 3 I just got a few minutes ago that had owner account and a "Guest" profile account on the phone when I turned it on for the first time. I've used EZFile Explorer in the past I will look at MiXplorer and attempt your steps you mentioned earlier.

Also thank you for working on LineageOS for this tablet when you do finish it I will be looking forward to that thread I want to put LOS on all my devices starting with this scepter 8 tablet. I hope you also have a guide as well for the Serrano 3 since Qlink likes to do a combo deal for the serrano 3 & the scepter 8. That phone has the same junk in it only it seems the serrano 3 can't handle all that bloatware this phone is as hot as an iron and it's only been 15 minutes since I completed the init setup on the phone. The battery is going down really fast
and I would definitely like to set this phone free like I did the tablet with your help :D

I assume you must have a fair amount of experience with Android modding,
The only thing I ever did was root my samsung galaxy S5 with the help of this forum so many years ago. My experience is not much but I understand well and learn fast but it was truly your perfect set of instructions that got me the end result if you didn't mention the known issue with windows & drivers not being recognized I might have been coming back posting for help!

Enjoy your trip man i'll talk to you and pick your brain more when you get back!

You can let me know then what would be a good replacement for Gboard and probably explain more about those apps I mentioned yes I read about how most are possibly safe to uninstall but I still don't understand what some of these do like bookmark provider or partner setup. I would like to understand what they do and how they work but this is all another lesson for when you return!
 

Androxilogin

New member
Oct 1, 2021
4
4
Hello everyone. I'd like to say thank you to everyone who worked on getting to the bottom of this thing. It definitely went from complete trash to tolerable. While I won't really use it much ever, it's nice to have the option to be able to.

That being said, I took what I have found here and created a script that will do an automated install through step by step key press dialog in command prompt because I don't know any better. Hopefully this may help someone out who may be lost. It does include the 15 sec adb installer as well as boot_a.img and MiXplorer as another user mentioned here along with a list of directories that must remain on the device based on my personal experiences during the process. If providing any of the contents in a single package is a problem for anyone, please let me know and I'll remove them. I just wanted to hopefully make the process as easy as possible for those having problems getting this going. For those who might try this and perhaps skip a dialog and are unfamiliar with command prompt, you can right-click the script itself and hit 'edit' in the context menu to get a read out.
 

Attachments

  • Scepter 8 Unlock & Root.rar
    31 MB · Views: 159

Viva La Android R.I.P.

Recognized Contributor
Jul 31, 2019
1,648
751
Northeastern Tennessee
LG G Pad 8.3
Moto G
Hello everyone. I'd like to say thank you to everyone who worked on getting to the bottom of this thing. It definitely went from complete trash to tolerable. While I won't really use it much ever, it's nice to have the option to be able to.

That being said, I took what I have found here and created a script that will do an automated install through step by step key press dialog in command prompt because I don't know any better. Hopefully this may help someone out who may be lost. It does include the 15 sec adb installer as well as boot_a.img and MiXplorer as another user mentioned here along with a list of directories that must remain on the device based on my personal experiences during the process. If providing any of the contents in a single package is a problem for anyone, please let me know and I'll remove them. I just wanted to hopefully make the process as easy as possible for those having problems getting this going. For those who might try this and perhaps skip a dialog and are unfamiliar with command prompt, you can right-click the script itself and hit 'edit' in the context menu to get a read out.
Great work. Thanks for your hard work and contribution.
 
  • Like
Reactions: Androxilogin

Viva La Android R.I.P.

Recognized Contributor
Jul 31, 2019
1,648
751
Northeastern Tennessee
LG G Pad 8.3
Moto G
Thanks for making it possible.
If you wouldn't mind, I'd like to add your automated script tool to the OP as an alternative simplified option. I'd put it under it's own heading and outline the instructions for using it. Regardless of your decision on that, I truly appreciate your work. Thanks
Of course, I would credit you fully with the work
 

Viva La Android R.I.P.

Recognized Contributor
Jul 31, 2019
1,648
751
Northeastern Tennessee
LG G Pad 8.3
Moto G
@Moxiipc, I haven't forgotten about your request for a list of tweaks and mods for improving performance and overall functionality. What I have decided on is posting a modified stock ROM with several tweaks, mods and enhancements already baked in. I'm building it in the original Allwinner .img firmware format, so that it can be installed using PhoenixSuit, PhoenixUSB Pro, LiveSuit, etc. I'm actually working on this project this evening, so if you or any other members would like any specific features or add-ons, just leave a comment.
 

Androxilogin

New member
Oct 1, 2021
4
4
If you wouldn't mind, I'd like to add your automated script tool to the OP as an alternative simplified option. I'd put it under it's own heading and outline the instructions for using it. Regardless of your decision on that, I truly appreciate your work. Thanks
Of course, I would credit you fully with the work
No problem. I typed it up as I went along to share, I'm not worried about credit. Feel free to post it elsewhere, reupload, do with it whatever you'd like.
 

Viva La Android R.I.P.

Recognized Contributor
Jul 31, 2019
1,648
751
Northeastern Tennessee
LG G Pad 8.3
Moto G
No problem. I typed it up as I went along to share, I'm not worried about credit. Feel free to post it elsewhere, reupload, do with it whatever you'd like.
Thank you. Your script will undoubtedly be of great help to many new and inexperienced members who are not familiar with using ADB and fastboot command lines. The credit is well deserved. This was a great idea.
 

rustable

New member
Aug 3, 2022
3
0
im having an issue of the device showing up in fastboot, ive done everything, but when i try to install the drivers with device manager it doesnt show up at all
 

Top Liked Posts

  • There are no posts matching your filters.
  • 2
    sorry for my post.
    1
    pretty annoying that you'd just leave the links dead and not have the decency to update them.
    Please read this post by my esteemed team mate @Badger50 then you know why the links aren't updated any longer, and in turn you might want to consider to rephrase your currently inappropriate statement.

    Regards
    Oswald Boelcke
    Senior Moderator
  • 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