[GUIDE][FIRMWARE] QLink Scepter 8 Stock Firmware Restoration & Upgrading Guide

Search This thread

mdtryme

Member
Apr 1, 2021
7
4
Portland, OR
since i use linux mint cinnamon should i assume i dont need etcher or the live usb ? cant i do the same job without doubling up on the obvious if not let me know ok. thank you
 

Viva La Android

Senior Member
Has anybody tried the fastboot method yet? Seemed to work great on my device but I'd like to get input from other members, good or bad. Is there anything I could improve upon or change? My goal with this method was to alleviate the device recognition issues often experienced by members with Windows.
Let me know.
 

SunSlide

Member
Mar 18, 2022
34
10
Has anybody tried the fastboot method yet? Seemed to work great on my device but I'd like to get input from other members, good or bad. Is there anything I could improve upon or change? My goal with this method was to alleviate the device recognition issues often experienced by members with Windows.
Let me know.
Tried it today. Copied the script to a file in the unzip location and put a she bang at the top. Worked great in fastbootd to restore the original firmware and unbrick a boot loop into recovery. What did not work was the last two commands. I had to reboot into the bootloader where fast boot also works and run those command by them selfs. Now I can't flash a GSI to my system partition anymore. I shoulda just left it alone when it was working how I wanted lol.
 

Viva La Android

Senior Member
Tried it today. Copied the script to a file in the unzip location and put a she bang at the top. Worked great in fastbootd to restore the original firmware and unbrick a boot loop into recovery. What did not work was the last two commands. I had to reboot into the bootloader where fast boot also works and run those command by them selfs. Now I can't flash a GSI to my system partition anymore. I shoulda just left it alone when it was working how I wanted lol.
If you're getting an error when flashing a GSI, try this while in FASTBOOTD mode.
Code:
fastboot delete-logical-partition product_a
fastboot delete-logical-partition product_b
The /product partitions are not needed when running a GSI. Deleting both /product slots frees up available space in the dynamic /super partition, and should make room for a GSI.image. But remember, this cannot be performed in legacy fastboot mode. You'll need to boot into FASTBOOTD mode by executing:
Code:
adb reboot fastboot
Or, just select the option for entering fastboot mode from stock recovery.
 
Last edited:

Viva La Android

Senior Member
Tried it today. Copied the script to a file in the unzip location and put a she bang at the top. Worked great in fastbootd to restore the original firmware and unbrick a boot loop into recovery. What did not work was the last two commands. I had to reboot into the bootloader where fast boot also works and run those command by them selfs. Now I can't flash a GSI to my system partition anymore. I shoulda just left it alone when it was working how I wanted lol.
If you're getting an error when flashing a GSI, try this while in FASTBOOTD mode.
Code:
fastboot delete-logical-partition product_a
fastboot delete-logical-partition product_b
 

SunSlide

Member
Mar 18, 2022
34
10
If you're getting an error when flashing a GSI, try this while in FASTBOOTD mode.
Code:
fastboot delete-logical-partition product_a
fastboot delete-logical-partition product_b
Yeah, deleting partition product a is what originally started my issues. Didnt try both but dont see that helping at the momment. So long story short, i had linageos18 installed and working because it was the only one that installed no problem and booted. I then wanted to see if v17 or 19 would run better so i ended up deleting product_a(instructed by the tutorial i was goin through from asop) and flashed system_a but that ended in a boot loop to recovery. After trying to reflash v18 with no progress i used your the script to recover the stock firmware. Now from fastbootd (fastboot reboot fastboot) when i try to flash the system partition it's saying it cant write to the partition table when it does the resize on it. When i try from the bootloader,(fastboot reboot bootloader, fastboot flash system rom.img) it says it cant find the system partition but i can wipe the system partition. Something wierd is that i cant seem to flash roms from boot loader mode but cant erase partitions(fastboot erase part-name) from fastbootd mode. In other words, i have to flash in fastbootd and then reboot to boot loader to wipe partitions. Ive tried flashing the modified boot a time or two but that didnt help. I havnt had the time, but i was going todo the full restore again and root it from the top to get back to where i was the first time i installed lineage18.... Unless you or anyone else may have better ideas? I'd like to just know what im doing here.

Also, I was thinking about trying to port twrp to this as a learning exsperiance, would reflashing the stock rom fix anything i mess up? I noticed it reflashes the boot partitions and was thinking i could use it as a fail safe.
Edit: i do fully understand i can brick the device but this particular unit is 'desposible' enough im willing to take the chance to learn.
 
Last edited:

Viva La Android

Senior Member
Yeah, deleting partition product a is what originally started my issues. Didnt try both but dont see that helping at the momment. So long story short, i had linageos18 installed and working because it was the only one that installed no problem and booted. I then wanted to see if v17 or 19 would run better so i ended up deleting product_a(instructed by the tutorial i was goin through from asop) and flashed system_a but that ended in a boot loop to recovery. After trying to reflash v18 with no progress i used your the script to recover the stock firmware. Now from fastbootd (fastboot reboot fastboot) when i try to flash the system partition it's saying it cant write to the partition table when it does the resize on it. When i try from the bootloader,(fastboot reboot bootloader, fastboot flash system rom.img) it says it cant find the system partition but i can wipe the system partition. Something wierd is that i cant seem to flash roms from boot loader mode but cant erase partitions(fastboot erase part-name) from fastbootd mode. In other words, i have to flash in fastbootd and then reboot to boot loader to wipe partitions. Ive tried flashing the modified boot a time or two but that didnt help. I havnt had the time, but i was going todo the full restore again and root it from the top to get back to where i was the first time i installed lineage18.... Unless you or anyone else may have better ideas? I'd like to just know what im doing here.

Also, I was thinking about trying to port twrp to this as a learning exsperiance, would reflashing the stock rom fix anything i mess up? I noticed it reflashes the boot partitions and was thinking i could use it as a fail safe.
Edit: i do fully understand i can brick the device but this particular unit is 'desposible' enough im willing to take the chance to learn.
Ok thanks for expounding on the specifics. I'm fairly certain you've corrupted the /super partition or perhaps inadvertently resized it while in fastboot mode. The good news is,.repairing the partition index is not complicated. You'll need to perform the v9 firmware installation using one of three tools:
• PhoenixUSB Pro; or
•PhoenixSuit; or
• LiveSuit
Installing the firmware using the fastboot script , unfortunately, does not reconfigure the partition index to its factory default. I outlined instructions for restoring firmware using PhoenixUSB Pro; however, the setup is for Windows. If you are running Linux, LiveSuit will do nicely. Once you restore the firmware using LiveSuit, your issue will be resolved. All three tools I listed were developed by Allwinner. I'll get you a link and instructions for using it now.

• LiveSuit Downloads - All Versions
• How to Flash Firmware Using LiveSuit

If you have a Windows PC or laptop, simply follow my instructions in the PhoenixUSB Pro section.
 
Last edited:

SunSlide

Member
Mar 18, 2022
34
10
Ok thanks for expounding on the specifics. I'm fairly certain you've corrupted the /super partition or perhaps inadvertently resized it while in fastboot mode. The good news is,.repairing the partition index is not complicated. You'll need to perform the v9 firmware installation using one of three tools:
• PhoenixUSB Pro; or
•PhoenixSuit; or
• LiveSuit
Installing the firmware using the fastboot script , unfortunately, does not reconfigure the partition index to its factory default. I outlined instructions for restoring firmware using PhoenixUSB Pro; however, the setup is for Windows. If you are running Linux, LiveSuit will do nicely. Once you restore the firmware using LiveSuit, your issue will be resolved. All three tools I listed were developed by Allwinner. I'll get you a link and instructions for using it now.

• LiveSuit Downloads - All Versions
• How to Flash Firmware Using LiveSuit

If you have a Windows PC or laptop, simply follow my instructions in the PhoenixUSB Pro section.
Yeah, i dunno Viva. I have a dual boot system so that wasnt an issue but i couldnt get phoenix or livesuite to reconize it. I could get it to the point where it poped up with the message box that said connecting and would hang until i un plugged the device from my laptop. Livesuite was a simular exsperiance on windows. I tried to install live suite on several different linux boxes and a vmmachine and just couldnt get it to install. I got it where it boots and is rooted so that suites my purposes. I think im gonna give up on the gsi for now though. After hours of reading,rebooting, and tapping the power button, i still cant modify the partitions. Is there a particular linux that livesuite works on? I tried manjaro, arco, ubuntu server and debian. It just said no to the arch based distos and complained about the dkms modules in the otger two.

Anyway, thanks for your help!
 

Viva La Android

Senior Member
Yeah, device recognition has been an issue for many users. The Allwinner based tools like PhoenixUSB Pro flash the device while in BROM mode, which is the hardware embedded bootloader. Since you have Windows and Linux, use my PhoenixUSB Pro instructions in this thread. I have included a step-by-step section titled "Installing USB Device Drivers" in the guide, which you should give close attention. Start from scratch and follow all steps to the letter.
 
Last edited:

SunSlide

Member
Mar 18, 2022
34
10
Yeah, device recognition has been an issue for many users. The Allwinner based tools like PhoenixUSB Pro flash the device while in BROM mode, which is the hardware embedded bootloader. Since you have Windows and Linux, use my PhoenixUSB Pro instructions in this thread. I have included a step-by-step section titled "Installing USB Device Drivers" in the guide, which you should give close attention. Start from scratch and follow all steps to the letter.
I might go ahead and give it another go tonight when i get home. Is there a difference in clickin the power button 3 times like you say and 10 times like the live suite says? Also, do you know how to modify the permissions or modify the partitions them selfs? Other then with the fastboot commands create/delete/resize_logical_partition? Ive scoured the net lookin for a way.
 

Viva La Android

Senior Member
I might go ahead and give it another go tonight when i get home. Is there a difference in clickin the power button 3 times like you say and 10 times like the live suite says? Also, do you know how to modify the permissions or modify the partitions them selfs? Other then with the fastboot commands create/delete/resize_logical_partition? Ive scoured the net lookin for a way.
No real difference. It can be recognized in as few as 3 to 4 clicks, or it can take as many as 8 to 10.
There are Linux based tools like parted that can be used to repartition flash memory. But you shouldn't need anything like that here. The Scepter 8 uses the Dynamic partition scheme, as you know. In addition, it uses the A/B seamless update partition scheme. Your issue comes down to needing to revert the partition index to the factory default. The only practical way of doing that is to flash a stock firmware using one of the three Allwinner based tools. I.corrupted my tablet too when first tinkering around with modding, rooting it and such. such. Once you flash the firmware with an official tool, it will go back to normal. Fortunately, Allwinner tablets are almost impossible to hard brick because they have hardware embedded bootloader code. The Allwinner based flashing tools communicate directly with that component when restoring firmware.

I do have a tip for you: whenever the flashing tool prompts you to begin with the hardware key combo and connecting the USB, your device has been booted into BROM mode. This is where you are having trouble with recognition. If, after following the instructions, your tablet still isn't recognized, keep it connected and right click on the Windows Start button. Open Device Manager and locate your tablet in the list. Let me know how Device Manager is listing your tablet. I can troubleshoot it and maybe resolve this issue if I have that info.
 
Last edited:

SunSlide

Member
Mar 18, 2022
34
10
No real difference. It can be recognized in as few as 3 to 4 clicks, or it can take as many as 8 to 10.
There are Linux based tools like parted that can be used to repartition flash memory. But you shouldn't need anything like that here. The Scepter 8 uses the Dynamic partition scheme, as you know. In addition, it uses the A/B seamless update partition scheme. Your issue comes down to needing to revert the partition index to the factory default. The only practical way of doing that is to flash a stock firmware using one of the three Allwinner based tools. I.corrupted my tablet too when first tinkering around with modding, rooting it and such. such. Once you flash the firmware with an official tool, it will go back to normal. Fortunately, Allwinner tablets are almost impossible to hard brick because they have hardware embedded bootloader code. The Allwinner based flashing tools communicate directly with that component when restoring firmware.

I do have a tip for you: whenever the flashing tool prompts you to begin with the hardware key combo and connecting the USB, your device has been booted into BROM mode. This is where you are having trouble with recognition. If, after following the instructions, your tablet still isn't recognized, keep it connected and right click on the Windows Start button. Open Device Manager and locate your tablet in the list. Let me know how Device Manager is listing your tablet. I can troubleshoot it and maybe resolve this issue if I have that info.
Ill try when i get home but that wont be for awhile so ill update ya overnight. Thank you for that explination. Ill have to read up on this brom mode a little bit. What should i exspect from the tablet when im in this mode? Ill double check the drivers and what not. I feel like im getting there because windows makes the little doot-da-doo after i click the power 5 times or so. That dont mean my drivers are right though. What driver should appear when im in that mode?
 

Viva La Android

Senior Member
Ill try when i get home but that wont be for awhile so ill update ya overnight. Thank you for that explination. Ill have to read up on this brom mode a little bit. What should i exspect from the tablet when im in this mode? Ill double check the drivers and what not. I feel like im getting there because windows makes the little doot-da-doo after i click the power 5 times or so. That dont mean my drivers are right though. What driver should appear when im in that mode?
The tablet should closely resemble a hard bricked device while in BROM mode: blank screen, unresponsive, hardware key actions
seemingly ineffective. This is why it's sometimes difficult to get a device out of BROM mode.
The driver should be a composite bootloader interface type. I have no doubt that the tool is properly booting your tablet into BROM mode; I think the sole issue is the driver. I can walk you through manually updating the driver while in BROM mode.
 
Last edited:

Top Liked Posts

  • There are no posts matching your filters.
  • 2
    im going to attempt this now.

    also Windows 7 32 bit? what country do you live?

    i have 4 laptops, perhaps i can ship you one of them
    Lol. I am not a windows user. So I honestly have no idea. It's a mini acer laptop that I keep in a drawer lmao 🤣.
    1
    I wish to reverse my opinion of the tablet screen. After a little while, the screen sensitivity came back and with a vengeance. The touch and feel is one of the best I've experienced, and I love the larger screen that a tablet allows.

    I do not know what happened, but it is great now. No doubt the better build helps a great deal. It is very fast and responsive. Thanks again to Viva La Android.
    1
    Hi, I'm new here but would there be any hope in porting lineage OS to this tablet, additionally is the Andriod 12 Go image above a stock image or a bloated image that comes standard with the specter 8, thanks.
    1
    how do i extract the vbmeta from boot,img'?
    1
    Aw, well. What can we do.
  • 2
    im going to attempt this now.

    also Windows 7 32 bit? what country do you live?

    i have 4 laptops, perhaps i can ship you one of them
    Lol. I am not a windows user. So I honestly have no idea. It's a mini acer laptop that I keep in a drawer lmao 🤣.
    1
    QLink Scepter 8 Tablet
    Stock Firmware Restoration
    And Upgrading Guide


    Download-Allwinner-USB-Drivers.jpg


    OVERVIEW:
    The manufacturer of this tablet, Hot Pepper Mobile, has released some stock firmware images for both hardware variants. Accordingly, I wanted to follow up with a comprehensive guide for performing a full firmware restoration and/or upgrading the firmware to a newer build version. This guide can be used to restore a device stuck in a boot loop, a bricked device, or a device which has become unstable due to issues with the Android OS or corresponding firmware. This guide can also be used for members who wish to upgrade the firmware from an earlier build version.
    This guide will be outlined to provide four firmware installation methods, all of which will focus on a Windows-based setup: (1) PhoenixUSB Pro; (2) LiveSuit; (3) PhoenixSuit; and (4) PhoenixCard. These four utilities were developed and released by Allwinner Technology Co, LTD. As such, each proprietary tool provides a comprehensive solution for restoring your device to its stock factory state. While any of the four outlined methods will ultimately achieve the same end result, members may find that one particular utility is simpler to use or works better than the others. In short, versatility is the focal point. The first three methods are standard proprietary strategies for flashing vendor-specific firmware images to eMMC NAND storage. These tools flash your tablet from a powered-off state known as FEL mode, a proprietary flashing protocol based on BROM. It should be noted here that many members experience device recognition issues while using PhoenixUSB Pro, PhoenixSuit and LiveSuit. For members who are experiencing insurmountable device recognition issues, I e. the flash tool not recognizing your tablet once it is in the powered off FEL flash mode, I have included a section at the very end of this guide for troubleshooting this dilemma. Also, the 4th method, PhoenixCard, may provide you with a viable solution to device recognition problems. PhoenixCard enables users to write a full firmware image to a micro SD card which, in turn, is inserted into the tablet's micro SD card slot. The tablet is then booted, at which time the firmware image on external storage is written to NAND/eMMC flash memory, thus fully restoring the tablet to its factory state. The PhoenixCard method is ideal for users with unresolved device recognition issues, or in scenarios where the partition index has incurred major corruption and fails during standard firmware restoration procedures.

    CHOOSE THE CORRECT VARIANT:
    Before proceeding, it is imperative that you know which variant of the QLink Scepter 8 you own. As mentioned previously, the first tablet variant shipped with Android 11 Go Edition, while the second, most recent variant, shipped with Android 12 Go Edition. If you have the first variant, flash only the v9 firmware package, which is based on Android 11 Go Edition. If you have the second, most recent variant, flash only the firmware listed under the Android 12 Go Edition heading of the downloads section. To avoid confusion, I have categorized the firmware in the downloads section below to correspond with each package's respective Android version.
    INSTALLING USB DEVICE DRIVERS:
    If you have previously installed ADB & Fastboot, as well as the proper USB device drivers on your Windows computer, skip down to the instructions for your preferred firmware restoration method. Otherwise, download the 15-Second ADB Installer v1.5.6 from the link below. Extract the contents of the archive to a folder on your desktop, or to another convenient directory on your PC or laptop. Open the utility and press the "Y" key when prompted to install the ADB & Fastboot drivers. Select "Y" again when prompted to install ADB as system-wide. Next, you will be given an option to install USB device drivers. Once again, press the "Y" key. A Device Drivers Installation Wizard window will be launched. Click the Next box in the lower right-hand section. If you receive a red warning notification that the drivers are unsigned, choose the option to install anyway. The Google universal USB device drivers will be installed on your computer. It' is recommended to reboot your PC or laptop once you see the notification that the drivers were successfully installed. That's it. Your Windows computer should now be configured with the proper drivers.

    DISCLAIMER:
    This guide involves flashing the partitions of your device with stock firmware. As such, there are always risks involved. By proceeding further, you are assuming sole responsibility and liability for the integrity and operability of your tablet. I am not responsible or liable in the event you damage your device or render it otherwise inoperable on the basis of this guide. Follow the instructions carefully and I'm confident things will go smoothly. If there is something you are unclear about, this thread is noob-friendly, so feel free to ask questions in comments.
    Furthermore, some of the firmware restoration methods outlined below will result in all user data being wiped on your device. Before proceeding, and if possible, make a backup up any important files and media that you wish to preserve.


    I. METHOD 1
    PhoenixUSB Pro For Windows

    PREREQUISITES:
    For prerequisites, you will need a PC or laptop running on Windows 7/8.1/10/11, the latest PhoenixUSBPro v4.0.0 flash tool (I have provided a link below), the OEM-supplied or a quality equivalent micro USB to USB-A data sync cable, and a factory firmware image that corresponds with your tablet variant (link provided below). In this first section, we will be using PhoenixUSBPro v4.0.0 for Windows. This particular tool is ideal for firmware restoration on devices which are either bricked or otherwise unable to boot into the Android OS. Enabling USB Debugging beforehand is not required, as this tool recognizes the device and initiates firmware installation from a powered-off state, via FEL mode.
    Also, this guide assumes that you have already installed the correct USB device drivers on your Windows computer.

    FIRMWARE RESTORATION/UPGRADE
    This will restore your device to its stock factory configuration, removing any system-level mods, root binaries, custom software, etc. These steps can also be followed to upgrade your firmware in the event you are running an older firmware build version.​
    1. Download PhoenixUSBPro v4.0.0 from the link below and extract the contents of the archived file to your computer desktop or to another directory which is easily accessible;​
    2. Download the correct stock firmware package for your tablet variant from the link below and extract the firmware image (.img file) to a convenient directory on your computer;​
    3. Power off your Scepter 8 tablet;​
    4. In the directory where you extracted the flash tool, open PhoenixUSBPro.exe. Once it launches, click on the Image box in the upper left of the interface. A file explorer will be launched. Navigate to the directory where you saved the firmware image (.img file). Select the image and then click Open in the lower right section of the window;​
    5. Now, click the Start button located in the upper section of the interface. A large green checkmark will appear in the upper right-hand corner, indicating that the firmware is now ready for installation;​
    6. Connect the USB data sync cable to your computer, but not yet to your tablet. Ensuring it is powered off, hold the Volume Down key on your tablet and connect the data sync cable to the micro USB port. While continuing to hold Volume Down, tap the Power key continuously until PhoenixUSB Pro recognizes your device, then release Volume Down. You will know your device has been recognized by an on-screen prompt indicating that the firmware installation is initiating;​
    7. The flashing process typically takes about four minutes. A progress bar on the PhoenixUSB Pro interface will show the percentage of completion in real time. When complete, you will see a green checkmark and a notification that the installation has finished;​
    8. Now, close the PhoenixUSBPro flash tool and disconnect your tablet from your computer. That's it. Upon reboot, your tablet will be reverted to its stock factory state and running on an unmodified stock firmware build.​
    Factory Firmware Images
    Android 11 Go Edition
    Build: Scepter8_tablet_V06_1202**
    Build: Scepter8_tablet_V09_20220221

    Android 12 Go Edition:
    Build: Scepter8_tablet_V01_20220607

    Build: Scepter8_tablet_V01_20220711
    Build: Scepter8_tablet_V02_20220726


    ** The V6 firmware is provided as a resource only. Unless your tablet is presently running on V6 or an earlier firmware build, it is not recommended for installation. Allwinner-based devices are not known to play nice when it comes to downgrading the bootloader partitions in some instances. I have not personally tested downgrading the Scepter 8; therefore I cannot vouch for the stability or feasibility of downgrading the firmware.

    II. METHOD 2
    PhoenixSuit For Windows


    PREREQUISITES:
    As with the previous section, you will need a PC or laptop running Windows 7/8.1/10/11, the OEM-supplied or a quality equivalent micro USB to USB-A data syncing cable, the PhoenixSuit v1.10 flashing utility (link provided below), and a factory firmware image for your QLink Scepter 8 variant (links provided above). This section presumes that the correct ADB, fastboot & USB device drivers are installed on your Windows computer. If you have not installed these, see my section above titled INSTALLING USB DEVICE DRIVERS, then return here once you have completed those instructions.

    FIRMWARE RESTORATION/UPGRADE:
    1. Download PhoenixSuit v1.10 from the link above and extract the contents of the archived file to your computer desktop, or to another directory which is easily accessible;​
    2. Download the correct stock firmware package for your tablet variant from the link above, and extract the firmware image (.img file) to a convenient directory on your computer;​
    3. Launch/Open PhoenixSuit by double clicking PhoenixSuit.exe from the directory you extracted in the first step;​
    4. Click on the Firmware tab in the top section of the interface and click on the blue Image tab. Windows File Explorer will be launched; navigate to the location of the firmware .img file you downloaded and extracted in the second step;​
    5. Power off your tablet;​
    6. Connect your data sync cable to your PC but not to your tablet. Hold Volume Down and, while continuing to hold the key, connect the micro USB end of the data sync cable to your tablet. Now tap the Power button (up to ten times) until PhoenixSuit indicates recognition of your device;​
    7. You will be prompted to perform a mandatory format. Select Yes to proceed;​
    8. PhoenixSuit will initiate the firmware installation. Once complete, an Upgrade Firmware Succeed notification will be displayed. Press Ok to finish the process.​
    9. Disconnect and reboot your device. . Your tablet should be now be restored to its factory stock state.​
    III. METHOD 3
    LiveSuit For Windows

    Like the previous two methods, LiveSuit is a proprietary NAND flash tool developed and released by Allwinner Technology. LiveSuit is available for the Windows, Mac and Linux operating system platforms. This particular guide, however, will focus strictly on a Windows setup. You can download LiveSuit for both the Mac and Linux platforms here: https://androidmtk.com/download-livesuit-all-versions
    The tools available for download are trusted, verified, and have been thoroughly scanned for viruses and other types of malicious code. A comprehensive guide for using LiveSuit for Linux can be found here: https://linux-sunxi.org/LiveSuit
    Without further ado,.let us proceed with LiveSuit for Windows.

    PREREQUISITES:
    Once again, you will need a PC or laptop running on Windows 7/8.1/10/11; the factory-supplied or a quality equivalent micro USB to USB-A data syncing cable; LiveSuitPack v1.11 (link available above); a firmware image compatible with your model/variant of the QLink Scepter 8 (links provided above); and the proper USB device drivers installed on your Windows computer. If you have not yet installed the driver's, follow my section above titled INSTALLING USB DEVICE DRIVERS. Return here after following those steps.

    FIRMWARE RESTORATION/UPGRADE
    1. Download LiveSuitPack v1.11 from the DOWNLOADS section above. Extract the contents of the archive to a folder on your desktop or to another convenient directory;​
    2. Download a firmware package compatible with your model/variant of the Scepter 8. In the simplest terms, if your tablet shipped with Android 11 Go Edition, then you must use a firmware package that corresponds with the Android 11 Go Edition build. If you have the newer variant that shipped with Android 12 Go Edition, then use firmware from that heading only. Once downloaded, extract the .img firmware file from the archive and save it to your desktop or another easily accessible location;​
    3. Open the LiveSuit flash tool by double clicking LiveSuitv1.11.exe in the directory you extracted in the first step. Once launched, select YES to follow the Upgrade Wizard;​
    4. Click the Upgrade Mode tab and then select Mandatory;
    5. Disconnect any connected mobile devices from your computer, and select Next;
    6. Select the Yes option, then.Next, and select the firmware .img file you extracted in the second step. Now click Yes but do not select Finish;
    7. Ensure your tablet is powered off. Connect the data sync cable to your PC but not yet to your tablet. Hold the Volume Down button on your tablet. While continuing.to hold the botton, connect the micro USB end of the data sync cable to your tablet. Without releasing the Volume Down button, press the Power key 5 to 10 times, or until you are notified by LiveSuit that your tablet has been recognized. Click Yes to proceed with firmware installation;​
    8. A progress bar on the LiveSuit interface will reflect the percentage of completion in real time. Once complete, an Upgrade Succeeds notification will be shown. Click Ok and then Exit.
    9. Reboot your tablet, which should now be restored to its stock factory state.​

    IV. METHOD 4
    PhoenixCard for Windows

    PREREQUISITES:
    As referenced previously, PhoenixCard is an Allwinner proprietary tool for burning a factory firmware image onto an external storage medium such as a micro SD card. In turn, the micro SD card is inserted into the tablet's card slot. Once the tablet is powered on, the firmware image burned to the micro SD card will then be written to the tablet's eMMC flash storage, thus restoring the device to its stock factory condition
    As you may have guessed, you will need a PC or laptop running Windows 7/8.1/10/11; a micro SD card with a recommended minimum capacity of 8 GB; a USB-type micro SD card reader/writer; a compatible factory firmware image for your tablet (links provided above); and the PhoenixCard v3.1.0 image burning tool (link provided above).

    FIRMWARE RESTORATION/UPGRADE
    1. Ensure that you have no external storage devices, mobile devices, or any other USB-type devices connected to your PC or laptop;​
    2. Download a factory firmware image from the downloads section above that is compatible with your tablet variant. Save the image on your computer desktop or another convenient directory;​
    3. Download the PhoenixCard v3.1.0 image burning tool onto your Windows computer. Extract the contents of the archive to a folder on your desktop or to another easily accessible location;​
    4. Double click PhoenixCard.exe to launch the tool;​
    5. Place your micro SD card into a suitable card reader/writer and connect it to your PC or laptop;.​
    6. Click on the Img File box located in the upper-left section of the PhoenixCard interface;​
    7. Select the firmware image (.img file) you downloaded in the second step;​
    8. Click the box marked Burn in the lower left section of the interface. The firmware image will be burned to the micro SD card. The process can take from 5 to 10 minutes to complete, at which time the output window of the interface will indicate Burn End;
    9. Remove the micro SD card from the card reader and insert it into the micro SD card slot of your QLink Scepter 8.tablet. Ensure that your tablet is powered off;​
    10. To begin the firmware installation process, long press your power button. Your tablet display will show a progress bar indicating that the firmware image on the micro SD card is being written to eMMC flash memory;​
    11. Once the process is complete, remove the micro SD card from your tablet and boot the device normally.​
    Upon reboot, your QLink Scepter 8 should be restored to its factory stock state.

    FIXING DEVICE RECOGNITION ISSUES
    This section outlines steps to resolve device recognition problems with any of the Allwinner flash tools and the tablet while in FEL/BROM mode. As mentioned previously, PhoenixUSB Pro, LiveSuit and PhoenixSuit restore factory firmware by flashing the NAND/eMMC directly, with the device in a powered-off state known as FEL mode. FEL mode is the Allwinner proprietary firmware flashing protocol based on the hardware embedded Boot ROM (BROM) code. All three of these tools utilize FEL mode when flashing firmware to your tablet's NAND/eMMC internal storage device. FEL mode is initiated one of two ways: (1) if the tablet is booted into the Android OS while connected to your computer, the tool will recognize your device, via USB Debugging, and once firmware flashing is ready to commence, the tool will boot your tablet into FEL flash mode which, again, is a powered off state; or (2) if your device is bricked, stuck in a boot loop, or is otherwise unable to boot up, FEL mode can be initiated manually by performing a particular hardware key sequence while connecting the powered-off device to your computer. In either scenario, your tablet will not be recognized by whichever flash tool you are using unless the proper drivers are installed on your Windows PC or laptop.

    Typically, on both Windows 10 and 11, generic drivers bundled with the operating system will enable proper recognition of your tablet while in FEL flash mode. However, in the event that your device is not being recognized by these flash tools while in FEL mode, and the firmware flashing process will not commence, download the Allwinner FEL Driver v1.0.0 from the link provided above, and extract the contents of the archived file to your PC or laptop. Right click either dpinst_x86.exe (for 32-bit Windows) or dpinst_x64.exe (for 64-bit Windows), and choose to run the application as an administrator. Follow the prompts on the driver installation wizard to install and configure the drivers on your computer. Once complete, a notification will indicate that the installation was successful. Select Finish and reboot your computer. Your tablet should now be recognized by the respective flash tool while in FEL mode, thus enabling the firmware restoration process to be completed.​
    1
    QLink Scepter 8 Tablet
    Stock Firmware Restoration
    And Upgrading Guide

    View attachment 5554999
    OVERVIEW:
    Now that the manufacturer has released some stock firmware images for this tablet, I wanted to follow up with a comprehensive guide for installation using the Phoenix Suite flash tool. This guide can be used to restore a device stuck in a boot loop, a bricked device, or a device which has become unstable due to issues with the Android OS or corresponding firmware. This guide also outlines the procedure for upgrading your QLink Scepter 8 to a newer firmware build.

    PREREQUISITES:
    There are a number of flash tools that can be used for installing firmware on the Scepter 8. As most of you already know, this tablet is powered by the Allwinner-A100 SoC platform. In this guide, we will be using Phoenix Suite v1.10 for Windows. Accordingly, you will need a PC or laptop running on Windows 7/8.1/10/11, the Phoenix Suite flash tool (I have provided a link below), the OEM-supplied or a quality equivalent micro USB to USB-A data sync cable, and a factory firmware image (link provided below). Also, this guide assumes that you have already installed the correct USB device drivers on your Windows computer. Should you have difficulties in this regard, I have outlined the steps for manually updating your drivers below.


    DISCLAIMER:
    This guide involves flashing the partitions of your device with stock firmware. As such, there are always risks involved. By proceeding further, you are assuming sole responsibility and liability for the integrity and operability of your tablet. I am not responsible or liable in the event you damage your device or render it otherwise inoperable on the basis of this guide. Follow the instructions carefully and I'm confident things will go smoothly. If there is something you are unclear about, this thread is noob-friendly, so feel free to ask questions in comments.



    I. FIRMWARE RESTORATION/UPGRADE
    This will restore your device to its stock factory configuration, removing any system-level mods, root binaries, custom software, etc. These steps can also be followed to upgrade your firmware to V9 if you are running an older build version. Warning: this procedure will erase all userdata from your tablet. Before proceeding further, create a backup of all important files and media that you wish to keep.

    1. Download Phoenix Suite 1.10 from the link below and install it on your Windows computer. Once installed, open the tool and grant any prompted permissions;
    2. Download the V9 stock firmware image from the link below and save it on a convenient directory on your PC or laptop. The firmware will be in an archived .rar file format. Use WinZip, WinRAR or other utility to extract the firmware image from the archive. Safe the image to a convenient directory on your computer;
    3. Ensure that USB Debugging is enabled in the Developer Options menu on your tablet;
    4. Connect your tablet to your Windows computer using a proper data sync cable. Watch your device display for the USB Debugging authorization prompt, then grant the request;
    5. If your tablet is being properly recognized by Phoenix Suite, an indicator in the bottom-left of the interface will indicate Device Connected.
    6. Click on the Firmware option in the upper panel of Phoenix Suite. Click on Image and then select the saved location of the firmware image you downloaded. Highlight the firmware image by clicking it, then select Open in the bottom-right of the interface.
    7. When ready to begin the restoration process, click the green Upgrade button in Phoenix Suite. Your device will automatically boot into a low-level flashing mode. When prompted, choose the option for full format. The firmware will begin installation. Phoenix Suite will indicate the progress of the installation and your tablet will automatically reboot to the OS once the process is complete. The flashing process will take between 3 and 4 minutes in duration. You are finished. Your device should now be fully restored to its factory stock state and running on the V9 firmware build.
    8. If the firmware did not commence installation due to a no-device-connected error, see the next section below on drivers.

    UPDATING USB DEVICE DRIVERS:
    Perform these steps only if the firmware did not install and you are receiving an error that no device is connected. As mentioned previously, once you select a firmware image, Phoenix Suite will boot your device into a low-level flashing mode (Download Mode) to begin the flashing process. Leave the device in this mode and keep it connected to your Windows computer. Right click the Windows Start button and select Device Manager. Your tablet should be listed under the Portable Devices heading as Unknown Device. Right click Unknown Device and choose Update Driver. On the next screen select the option to Browse My Computer. Next, click on the Browse icon box in the upoer-right of the menu. Navigate to the saved location of the folder from which you open the Phoenix Suite flash tool. It should have a folder name of PhoenixSuite_V1.10. Left click on the folder and look below it for a folder named Drivers. Select Drivers and then choose OK. Now click Next at the bottom-right of the menu. You may get a warning notification that the drivers are unsigned. Select the option to install anyway. Once installed, Phoenix Suite will immediately recognize your device on flash mode and the firmware installation will start automatically. Return to the Phoenix Suite flash tool interface to see the installation progress.

    DOWNLOADS:
    PhoenixSuite v1.10
    Stock Firmware Image V6
    Stock Firmware Image V9

    ** The V6 firmware is provided as a resource only. Unless your tablet is presently running on V6 or an earlier firmware build, it is not recommended for installation. PhoenixSuite is not known to play nice when it comes to downgrading. I have not personally tested downgrading the Scepter 8; therefore I cannot vouch for the stability or feasibility of downgrading the firmware.


    View attachment 5555371
    The Version 1 illustration reflects a tablet that shipped with the V6 firmware build.
    The Version 2 illustration reflects a tablet that shipped with the most recent V9 build.




    Thank you very much for all the work you've done on this. It has been a big help. I've been following along since the beginning of this topic and I've been using XDA for years but this is my first post, I think, maybe second, idk.


    I have been able to do pretty much everything but get this firmware to flash, it consistently gets to the part where it says on the bottom left of the phoenix suite window "beginning flash operation" or something similar, the selection form is replaced with an empty progress bar and i can't recall exactly whats written under the progress bar but it something to the effect of "firmware flash starting". But that's it it does nothing after that, I've left it 20 and 30 mins and nothing, no error message or any message but If I unplug the USB cable from the tablet, I get a message about the device being disconnected.

    I rooted the tablet without issue close to the day after the stock firmware was posted. I used a program called "ImgRepacker" to extract the contents of the firmware image which were mostly ".fex" files. I read somewhere that you can simply rename the boot.fex file to boot.img and that worked. I patched it with Magisk and flashed it using fastboot and just like that, rooted.

    And its been working fine until yesterday when i was messing with the build.prop file. I think its you who posted some performance tweaks in a different thread. I think I may have entered something incorrectly and rebooted and now it gets stuck right where the boot animation would normally start.

    Its not an emergency but I just can't get this stock image to flash.. I have deleted the pheonix tools i was using and I downloaded the one posted here.

    Bootloader is unlocked
    USB ADB Debugging is enabled (well last I was booted up)

    I can boot to recovery.
    I can boot to bootloader (fastboot).
    i can boot to fastbootd.

    drivers have been a bit tricky:

    when i was connected via usb to my pc (i'm using windows 11 btw)

    with adb debugging enabled, as and also i had to enable file transfer mode to get "ADB Device" to appear. I would then have an "ADB Device" under the NEW heading "USB Devices" as well as "Scepter 8" under the heading "Portable devices" ADB commands seemed to work perfectly and I could copy files to "internal storage " so I didn't bother too much but I tried to update the drivers for "ADB Device" with the Google Android drivers and also with the ADB drivers included with Pheonix Tool but on both counts I was not able to and the message from windows was the driver files I selected were not the correct files for the selected device (period). Like i said that was working so...

    Booting into recovery I was then able to install the ADB Drivers in the pheonix tool directory
    Under "Android" heading was " Composite ADB Interface"

    Booting Bootloader or fastbootd I was able to install "Bootloader Interface"

    The Pheonix tool would recognize my device with ADB debugging, then i click upgrade with the v9 firmware selected and my tablet will reboot to download mode presumeably and the driver i was able to install for it shows up under the heading
    "Universal Service Bus Controllers" as "USB Device(VID_1f3a_PID_efe8)"




    Any Idea why I can't get the stock image to flash?

    Why it looks like its about to start the flash but never does?


    (sorry if that's too much info... :) and thank you for any help you are able to offer)
    1
    Your issue sounds exactly like a driver issue -- and that is very common with Allwinner devices. In the above instructions I've included a guide for updating the USB drivers. Just because PhoenixSuite initially recognized your device does not mean it will also be recognized when it boots to download mode and begins the flash. It sounds like yours is first recognized fine and then when the flash begins, sync between the tablet and the flashing tool is lost. Follow my update USB drivers section above and see if that fixes your issue. Remember, your tablet needs to remain in download mode and connected to your PC when you follow the update USB drivers steps.
    1
    Aw, well. What can we do.