[INDEX][GUIDE] Q-Link Scepter 8 Tablet / General Info & Discussion Thread

Search This thread

Viva La Android

Senior Member
Everthing works great, now i can see if i can make this a bit lag free. If there's any roms i can download let me know, something that's android 10 since android 11 and 12 are buggy imo.
and thanks a lot for your service helped a lot
You can always go the GSI route, since the Scepter 8 is Treble supported. I'll get you a XDA link for a repo of GSI builds. They can be a bit tricky to install on a dynamic partitioned device like this one, but there are some good guides posted as well in the GSI forums.
 

Viva La Android

Senior Member
By the way, having an android 12 vendor will only support GSI roms from android 12 or higher. So you will not be able to use GSI roms based on Android 10 and 11😅
Yeah @SamuEDL I forgot all about the Android 12 /vendor partition rule. As far as Android 12 GSIs go, what has been your best experience? The only ones I've tried are the LineageOS 19.1/L ROMS.
 

SamuEDL

Senior Member
Aug 1, 2011
181
71
Yeah @SamuEDL I forgot all about the Android 12 /vendor partition rule. As far as Android 12 GSIs go, what has been your best experience? Tie only ones I've tried are the LineageOS 19.1/L ROMS.
In my case, on my tablet I have not had good results with Android 12 (Keep in mind that my vendor is android10 and I have a lower kernel(4.9)). Lineageos 19.1 does not start me and in the AOSP PPH I have a lot of lag).
 
  • Like
Reactions: Viva La Android

Aquaires

New member
Apr 3, 2019
4
0
I am STUCK

md 2207ap13023131
Tried to downgrade upgrade everything I can think of. With bootloader locked it states different OS will not boot in RED unlocked either boot loops message in YELLOW your bootloader needs locked then hangs on splash till I send back to fastboot or battery turns dead. This is my first split A/B root. I've done Blu vivo 11+ rooted made it Verizon 1 sim card then back to original back to 2 sim card. I know some what of what to do. I can always get it back to bootloader to fastboot but that is it.. It loops or hangs on splash screen or I can get it to fastboot to flash. Phoenixesusbpro wont work nor will the Phoenix's Suit. Cant find device but bugview in UsbPro does produce some limited lines of info. First time with Phoenix's have used Miracle box and Spflash

prousbdebugview

[2868] Load "privatedata.ini" Failed: .\ProProcMan.cpp @ 2107

dont know if luck or timing for unplug re-plug for getting back into fastboot
side buttons do not work to send to anything but power on and off

C:\Program Files (x86)\ADB and Fastboot>fastboot reboot
rebooting...

finished. total time: 0.011s

C:\Program Files (x86)\ADB and Fastboot>fastboot reboot fastbootd
< waiting for any device >
^C
C:\Program Files (x86)\ADB and Fastboot>adb reboot boootloader
adb server version (31) doesn't match this client (39); killing...
* daemon started successfully
error: no devices/emulators found

C:\Program Files (x86)\ADB and Fastboot>adb reboot boootloader
adb server version (31) doesn't match this client (39); killing...
* daemon started successfully
error: no devices/emulators found

C:\Program Files (x86)\ADB and Fastboot>adb reboot boootloader
error: no devices/emulators found

C:\Program Files (x86)\ADB and Fastboot>adb reboot boootloader
error: no devices/emulators found

C:\Program Files (x86)\ADB and Fastboot>fastboot reboot fastbootd
< waiting for any device >
^C
C:\Program Files (x86)\ADB and Fastboot>fastboot reboot bootloader
< waiting for any device >
^C
C:\Program Files (x86)\ADB and Fastboot>adb reboot boootloader
* daemon not running; starting now at tcp:5037
* daemon started successfully
error: no devices/emulators found

C:\Program Files (x86)\ADB and Fastboot>adb reboot boootloader
error: no devices/emulators found

C:\Program Files (x86)\ADB and Fastboot>adb reboot boootloader
error: no devices/emulators found

C:\Program Files (x86)\ADB and Fastboot>adb reboot boootloader
error: no devices/emulators found

C:\Program Files (x86)\ADB and Fastboot>adb reboot boootloader
error: no devices/emulators found

C:\Program Files (x86)\ADB and Fastboot>adb reboot boootloader
error: no devices/emulators found

C:\Program Files (x86)\ADB and Fastboot>adb reboot boootloader
error: no devices/emulators found

C:\Program Files (x86)\ADB and Fastboot>adb reboot boootloader
error: no devices/emulators found

C:\Program Files (x86)\ADB and Fastboot>adb reboot boootloader
error: no devices/emulators found

C:\Program Files (x86)\ADB and Fastboot>fastboot reboot fastbootd
< waiting for any device >
^C
C:\Program Files (x86)\ADB and Fastboot>adb reboot boootloader
error: no devices/emulators found

C:\Program Files (x86)\ADB and Fastboot>adb reboot boootloader
error: no devices/emulators found

C:\Program Files (x86)\ADB and Fastboot>ADB SHELL
adb: usage: unknown command SHELL

C:\Program Files (x86)\ADB and Fastboot>fastboot oem unlock
...
FAILED (remote: system is already unlocked)
finished. total time: 0.678s

C:\Program Files (x86)\ADB and Fastboot>fastboot flash boot_a C:\Users\DragoAquaires\Downloads\patched_boot.img
target reported max download size of 33554432 bytes
Invalid sparse file format at header magic
sending sparse 'boot_a' 1/2 (31812 KB)...
OKAY [ 1.211s]
writing 'boot_a' 1/2...
OKAY [ 3.257s]
sending sparse 'boot_a' 2/2 (15276 KB)...
OKAY [ 0.595s]
writing 'boot_a' 2/2...
OKAY [ 2.548s]
finished. total time: 7.616s

C:\Program Files (x86)\ADB and Fastboot>fastboot flash boot_b C:\Users\DragoAquaires\Downloads\patched_boot.img
target reported max download size of 33554432 bytes
Invalid sparse file format at header magic
sending sparse 'boot_b' 1/2 (31812 KB)...
OKAY [ 1.210s]
writing 'boot_b' 1/2...
OKAY [ 2.788s]
sending sparse 'boot_b' 2/2 (15276 KB)...
OKAY [ 0.594s]
writing 'boot_b' 2/2...
OKAY [ 2.486s]
finished. total time: 7.083s

C:\Program Files (x86)\ADB and Fastboot>fastboot -w
wiping userdata...
Erase successful, but not automatically formatting.
File system type not supported not supported.
wiping cache...
Erase successful, but not automatically formatting.
File system type not supported not supported.
erasing 'userdata'...
OKAY [ 1.375s]
erasing 'cache'...
OKAY [ 0.025s]
finished. total time: 1.402s

C:\Program Files (x86)\ADB and Fastboot>fastboot reboot
rebooting...

finished. total time: 0.010s

C:\Program Files (x86)\ADB and Fastboot>

getting back to fastboot
only works by repluging into pc I believe it is kinda like the brick fix for SPflash and Phoenix
umidigi phone had a similar placement with the side button sequence for when screen blacked out.

Files I have used has only been from here in this thread. even for attempt to downgrade
right now it is stuck on splash screen after yellow warning of locking bootloader press power to pause boot press power restarts do nothing stays on splash screen...

Any perspectives on this project
 

Viva La Android

Senior Member
I am STUCK

md 2207ap13023131
Tried to downgrade upgrade everything I can think of. With bootloader locked it states different OS will not boot in RED unlocked either boot loops message in YELLOW your bootloader needs locked then hangs on splash till I send back to fastboot or battery turns dead. This is my first split A/B root. I've done Blu vivo 11+ rooted made it Verizon 1 sim card then back to original back to 2 sim card. I know some what of what to do. I can always get it back to bootloader to fastboot but that is it.. It loops or hangs on splash screen or I can get it to fastboot to flash. Phoenixesusbpro wont work nor will the Phoenix's Suit. Cant find device but bugview in UsbPro does produce some limited lines of info. First time with Phoenix's have used Miracle box and Spflash

prousbdebugview

[2868] Load "privatedata.ini" Failed: .\ProProcMan.cpp @ 2107

dont know if luck or timing for unplug re-plug for getting back into fastboot
side buttons do not work to send to anything but power on and off

C:\Program Files (x86)\ADB and Fastboot>fastboot reboot
rebooting...

finished. total time: 0.011s

C:\Program Files (x86)\ADB and Fastboot>fastboot reboot fastbootd
< waiting for any device >
^C
C:\Program Files (x86)\ADB and Fastboot>adb reboot boootloader
adb server version (31) doesn't match this client (39); killing...
* daemon started successfully
error: no devices/emulators found

C:\Program Files (x86)\ADB and Fastboot>adb reboot boootloader
adb server version (31) doesn't match this client (39); killing...
* daemon started successfully
error: no devices/emulators found

C:\Program Files (x86)\ADB and Fastboot>adb reboot boootloader
error: no devices/emulators found

C:\Program Files (x86)\ADB and Fastboot>adb reboot boootloader
error: no devices/emulators found

C:\Program Files (x86)\ADB and Fastboot>fastboot reboot fastbootd
< waiting for any device >
^C
C:\Program Files (x86)\ADB and Fastboot>fastboot reboot bootloader
< waiting for any device >
^C
C:\Program Files (x86)\ADB and Fastboot>adb reboot boootloader
* daemon not running; starting now at tcp:5037
* daemon started successfully
error: no devices/emulators found

C:\Program Files (x86)\ADB and Fastboot>adb reboot boootloader
error: no devices/emulators found

C:\Program Files (x86)\ADB and Fastboot>adb reboot boootloader
error: no devices/emulators found

C:\Program Files (x86)\ADB and Fastboot>adb reboot boootloader
error: no devices/emulators found

C:\Program Files (x86)\ADB and Fastboot>adb reboot boootloader
error: no devices/emulators found

C:\Program Files (x86)\ADB and Fastboot>adb reboot boootloader
error: no devices/emulators found

C:\Program Files (x86)\ADB and Fastboot>adb reboot boootloader
error: no devices/emulators found

C:\Program Files (x86)\ADB and Fastboot>adb reboot boootloader
error: no devices/emulators found

C:\Program Files (x86)\ADB and Fastboot>adb reboot boootloader
error: no devices/emulators found

C:\Program Files (x86)\ADB and Fastboot>fastboot reboot fastbootd
< waiting for any device >
^C
C:\Program Files (x86)\ADB and Fastboot>adb reboot boootloader
error: no devices/emulators found

C:\Program Files (x86)\ADB and Fastboot>adb reboot boootloader
error: no devices/emulators found

C:\Program Files (x86)\ADB and Fastboot>ADB SHELL
adb: usage: unknown command SHELL

C:\Program Files (x86)\ADB and Fastboot>fastboot oem unlock
...
FAILED (remote: system is already unlocked)
finished. total time: 0.678s

C:\Program Files (x86)\ADB and Fastboot>fastboot flash boot_a C:\Users\DragoAquaires\Downloads\patched_boot.img
target reported max download size of 33554432 bytes
Invalid sparse file format at header magic
sending sparse 'boot_a' 1/2 (31812 KB)...
OKAY [ 1.211s]
writing 'boot_a' 1/2...
OKAY [ 3.257s]
sending sparse 'boot_a' 2/2 (15276 KB)...
OKAY [ 0.595s]
writing 'boot_a' 2/2...
OKAY [ 2.548s]
finished. total time: 7.616s

C:\Program Files (x86)\ADB and Fastboot>fastboot flash boot_b C:\Users\DragoAquaires\Downloads\patched_boot.img
target reported max download size of 33554432 bytes
Invalid sparse file format at header magic
sending sparse 'boot_b' 1/2 (31812 KB)...
OKAY [ 1.210s]
writing 'boot_b' 1/2...
OKAY [ 2.788s]
sending sparse 'boot_b' 2/2 (15276 KB)...
OKAY [ 0.594s]
writing 'boot_b' 2/2...
OKAY [ 2.486s]
finished. total time: 7.083s

C:\Program Files (x86)\ADB and Fastboot>fastboot -w
wiping userdata...
Erase successful, but not automatically formatting.
File system type not supported not supported.
wiping cache...
Erase successful, but not automatically formatting.
File system type not supported not supported.
erasing 'userdata'...
OKAY [ 1.375s]
erasing 'cache'...
OKAY [ 0.025s]
finished. total time: 1.402s

C:\Program Files (x86)\ADB and Fastboot>fastboot reboot
rebooting...

finished. total time: 0.010s

C:\Program Files (x86)\ADB and Fastboot>

getting back to fastboot
only works by repluging into pc I believe it is kinda like the brick fix for SPflash and Phoenix
umidigi phone had a similar placement with the side button sequence for when screen blacked out.

Files I have used has only been from here in this thread. even for attempt to downgrade
right now it is stuck on splash screen after yellow warning of locking bootloader press power to pause boot press power restarts do nothing stays on splash screen...

Any perspectives on this projec
 
Aug 18, 2022
42
18
I've gotta say that I am impressed with this little cheap tablet. While using it with the new setup (Thanks to Viva La Android!), I was able to create a very useful device. This is something that could never be done with a smartphone, if only because of the reasonable screen size.

While using it I noticed that after looking at the screen for a while and then turning to look at my computer monitor, the monitor seemed very dim. Well, the problem appeared to be that it was I that was dim. ;)

All I had to do was to reduce the brightness of the tablet down to a level matching my monitor output, which was more than enough. But I received a huge benefit for so doing. The battery life just jumped way up.

I took the tablet along to an out-of-town appointment yesterday after charging it up almost fully. In a waiting situation, I pulled it out to use it. From that time on until I got back home, it remained on. The screen only blanks after 10 minutes of non-use.

Well I noticed this morning that the thing was still on, but the battery level was still at least 3/4 full! That is really great in my book.

If only the government had required this sort of setup to begin with, people would have had something useful, right out of the box, without the privacy risks of google.
 
  • Like
Reactions: Viva La Android

ScarletWizard

Senior Member
Aug 31, 2022
119
21
Can you access bootloader/fastboot this way?

Powered off
hold any vol button and keep holding
plug in usb
while holding a vol button tap power 10 times
Same thing happen to me. Fastoot seemed broken but it’s not. Power off the tablet and let it rest for a good while then plug it in to a wall outlet let it charge for a good 15 minutes. When you see the battery icon it’s a good sign. Attempt at this stage to enter fastboot
 
  • Like
Reactions: Viva La Android

Top Liked Posts

  • There are no posts matching your filters.
  • 1
    I've gotta say that I am impressed with this little cheap tablet. While using it with the new setup (Thanks to Viva La Android!), I was able to create a very useful device. This is something that could never be done with a smartphone, if only because of the reasonable screen size.

    While using it I noticed that after looking at the screen for a while and then turning to look at my computer monitor, the monitor seemed very dim. Well, the problem appeared to be that it was I that was dim. ;)

    All I had to do was to reduce the brightness of the tablet down to a level matching my monitor output, which was more than enough. But I received a huge benefit for so doing. The battery life just jumped way up.

    I took the tablet along to an out-of-town appointment yesterday after charging it up almost fully. In a waiting situation, I pulled it out to use it. From that time on until I got back home, it remained on. The screen only blanks after 10 minutes of non-use.

    Well I noticed this morning that the thing was still on, but the battery level was still at least 3/4 full! That is really great in my book.

    If only the government had required this sort of setup to begin with, people would have had something useful, right out of the box, without the privacy risks of google.
    1
    Can you access bootloader/fastboot this way?

    Powered off
    hold any vol button and keep holding
    plug in usb
    while holding a vol button tap power 10 times
    Same thing happen to me. Fastoot seemed broken but it’s not. Power off the tablet and let it rest for a good while then plug it in to a wall outlet let it charge for a good 15 minutes. When you see the battery icon it’s a good sign. Attempt at this stage to enter fastboot
  • 4

    Q-LINK SCEPTER 8


    images (1).jpeg
    images.jpeg

    QLINK SCEPTER 8 VARIANTS:
    To date (September 7, 2022), two primary hardware variants of the QLink Scepter 8 tablet have been released by Hot Pepper Mobile. The original variant is powered by the Allwinner-A100 chipset platform, has 1 GB RAM, and shipped with the Android 11 Go Edition OS. The newer variant, released only a few weeks ago, includes an upgraded Allwinner-A133 chipset, has 2 GB RAM, and ships with the latest build of Android 12 Go Edition preinstalled. The CEO of Hot Pepper Mobile, Mr. Shawn Sun, has most graciously provided me with factory firmware images for both variants. Those firmware packages are available over in my stock firmware restoration guide linked in the downloads section below. Likewise, instructions for unlocking the bootloader and attaining root access on both variants can be found on my below-linked guide as well.​

    OVERVIEW:
    This is a general info and discussion thread for any topics relating to the Q-Link Scepter 8 tablet. This is an 8" budget Android tablet manufactured specifically for eligible recipients of the Emergency Broadband Benefit (EBB) Program, a federally funded FCC initiative to help families and households struggling to afford internet service during the Covid-19 pandemic. As of December 31, 2021, the EBB was renamed the Affordable Connectivity Program (ACP). Ironically, even though the EBB was originally intended specifically for assistance with internet service, and although this tablet is branded by Q-Link, a major mobile service provider of the federal Lifeline program, the Q-Link Scepter 8 is a WiFi-only device and does not support cellular connectivity. Because there is very little info available online for this device, a general info and discussion thread was needed as a collective forum and resource for device owners.

    DEVELOPMENT STATUS:
    This tablet is supported for bootloader unlocking by way of the standard fastboot mode procedure. Root access can be attained by the standard Magisk systemless strategy of ramdisk patching. Unfortunately, I no longer own one of these tablets and I did not save copies of any of the firmware images I was able to pull from the device by way of a flash tool in read-back mode. Likewise, as luck would have it, the modded flash tool is no longer accessible due to a broken download link online and no working mirrors As it stands, we are lacking a stock boot/recovery image with which to patch the ramdisk for root. To date, despite numerous formal requests made to the manufacturer, the kernel source code has not been released to the public. Likewise, the manufacturer has released no factory images or stock firmware for this device, making custom development a futile effort at this point. I am presently attempting to locate a chipset-supported version of an Allwinner flashing utility which can be used to dump partition images.
    This thread is intended for general discussion of any topics relating to the Q-Link Scepter 8. As resources for source code, firmware, etc., become available, additional development threads will be posted and maintained. For now, however, this is the catch-all device thread. Although I no longer own one of these devices, I will try to diligently maintain this thread and make efforts to break ground on custom development projects. A couple of days ago, on January 11th, I emailed support for Hot Pepper, Inc., and made formal written requests for both the kernel source code (which the manufacturer is required to provide pursuant to the GNU General Public License) and factory images or a stock firmware package for this tablet. Because Hot Pepper, Inc., recently changed hands in terms of ownership and operations, I am hopeful that at least one of my requests Is granted.
    UPDATE: On January 27th, I received a reply from a support specialist of Hot Pepper, Inc. His correspondence advised me that my request for kernel source code had been forwarded to Hot Pepper's software developers in China, who should be returning to the office from Chinese Holiday on February 6th. Accordingly, access to the kernel source code should be forthcoming in just a matter of days.
    Update: February 22, 2022:
    I have received correspondence from the CEO of Hot Pepper Mobile regarding my request for stock firmware and kernel source code for the Scepter 8. It appears that the delay was merely an issue of English--Chinese translation with respect to my original request. This is the correspondence in full:
    Screenshot_20220222-024927.png

    Per the CEO's instructions,, I have clarified my requests and provided specific examples. It now looks as though development for this tablet is imminent. I will, of course, keep this thread updated accordingly and post links to stock firmware/source code here just as soon as Hot Pepper Mobile grants access.
    Update: February 23, 2022:
    Finally, after weeks of back-and-forth correspondence, the CEO of Hot Pepper Mobile has provided me with two factory images for the QLink Scepter 8: one package is V6 and the other appears to be the latest build, V9. Both firmware images are available in my Stock Firmware Restoration Guide, which I have linked below. Although I did not receive the actual kernel source code, I'm content that the factory images will advance our efforts for rooting and a TWRP port build, which I will be working on as soon as free time permits.
    UPDATE ON TWRP: As it currently stands, the TWRP port for this device is at a standstill. Because this tablet is Allwinner-based, uses the Dynamic partition scheme, and supports seamless updates (A/B), there are simply too many obstacles to complete the build at this time. I am requesting assistance from a TeamWin developer on this project. I will keep this thread updated with the status on the unofficial TWRP port. However, on a positive note, I am currently porting LineageOS 19.1 (Android 12) to this tablet, which will be installable with PhoenixSuit, LiveSuit, or PhoenixUSBPro. Believe it or not, a custom ROM is child's play in comparison to porting TWRP.

    DOWNLOADS & LINKS:

    Q-Link Scepter 8 User Manual (PDF)
    Q-Link Scepter 8 FCC Report
    Bootloader Unlocking & Rooting Guide
    Stock Firmware Restoration Guide

    PLEASE CONSIDER:
    Please keep this thread on topic and post only about subject matter relating to the Q-Link Scepter 8. While all discussion and questions are welcome, please keep it device specific. Also, please be respectful to others when posting or replying. Keep in mind that English is not the primary language of every member, as the XDA community spans the entire globe. As such, it is often easy to misinterpret text which has been translated into English, or to take statements out of context. Be patient with, and kind to, new members who seek knowledge and answers. Remember when you were a noob and others patiently assisted you here on XDA. In short, it is my wish to keep this thread an open and welcome platform for all members, regardless of language, experience, nationality, etc. Please be respectful.

    THANKS & MENTIONS:
    Thanks goes out to Hot Pepper Mobile, Inc., for providing factory firmware images for this device. Specifically, I want to thank Hot Pepper Support Specialist Joshua G. and Hot Pepper CEO Shawn Sun for their professional assistance.

    4
    Update: The manufacturer of this tablet, Hot Pepper, Inc., has replied to my formal requests for kernel source and factory images. I was asked to elaborate more on my requests, which I have done. Hopefully they will accommodate soon.
    4
    I got a successful root with magisk! I'll include a rough how-to
    1. enable USB debugging in developer options. (unlock by tapping 5x on build number in settings>about tablet)
    2. enable OEM Unlocking in developer options. Mine was originally greyed out, but it corrected after I linked a google account in setup.
    install minimal adb/fastboot on your pc, connect tablet via microusb https://androiddatahost.com/uq6us
    run cmd-here.exe, and type: adb reboot bootloader, and then fastboot oem unlock
    3. download firmware v9 to pc
    4. open firmware img with 7zip, and extract boot_a.img
    5. transfer that boot img file back into your tablets storage.
    6. install Magisk on github, go to install, and select that boot image when prompted.
    7. copy the img it spits out onto your computer, into the root directory of your adb/fastboot. Rename it something simple like patchedboot.img
    8. download and install Phoenix Suite https://androidmtk.com/download-phoenixsuit
    9. enable USB debugging on your tablet and keep it connected. you can verify a good connection if 'adb devices' in cmd shows a device.
    10. Phoenix Suite will recognize your adb device. proceed to install the v9 firmware to your tablet
    11. after its finished, in CMD enter: adb reboot fastboot
    12. enter: fastboot flash boot patchedboot.img
    13. reboot your tablet, and check in magisk to see if it you're rooted, it will show: Installed 24.1 instead of N/A
    14. I highly reccomend sideloading librechair for a launcher, and Openboard for keyboard; they use minimal ram and run reliably on such a low spec tablet. My tablet no longer freezes doing light tasks.
    https://t.me/librechair/7269
    https://f-droid.org/en/packages/org.dslul.openboard.inputmethod.latin/
    https://www.bromite.org/ for going full degoogled

    here's the patched v9 boot.img to save people some time
    3
    Ok folks now we are making progress on source code. After being forwarded to Hot Pepper's lawyers, my request has now been sent to the actual developers of the tablet's firmware in China. The following is support's response:
    Screenshot_20220129-203511.png

    So the best I can tell, we will have source code in early February. Hopefully, shortly after. Feb 9th. I'm not having luck with the Phoenix tool so far, so the source code may be our savior here.
    3
    Just an update they did bill me (and I paid with a PayPal key in which I changed the CVC right after) $10.01 for the silly tablet.
    Yeah the person I bought my original tablet from jokingly said that the government had a $10.01 lien on the tablet. Except, he wasn't actually joking because QLink had billed him for $10.01 a couple weeks after he received it. My guess is, half the recipients of the Scepter 8 probably will never pay QLink a dime.