yashsingh1/xdaforums huggingface dataset:
[Android General] EmmaDearest:
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

patchedboot.img

drive.google.com
[Android General] Gborg3:
Can someone type up clear instructions for getting ADB wrking with this tablet and Windows 10? No matter what I do I keep getting waiting for devices and nothing works. adb devices shows the tablet is there when it i turned on but the open android screen does nothing to help. The tablet stops showing up when it is in that mode. Phoenix suit says its adb out of date and closes it. Now I tried manually installing the driver and I got a brand new type of error. This is why I am asking for help. None of these directions to accomplish any of this are working. Just errors and errors and errors.
[Android General] Gborg3:
I am not even able to unlock my bootloader since it just eternally waits for devices. I am following every direction I can and nothing at all in any way is doing any of what is apparently working for everyone else.
[Android General] menace211:
I can't get the Phoenix Suit to work
[Android General] SamuEDL:
Someone has managed to flash the ROM with Phoenix?
[Android General] Viva La Android R.I.P.:
I love it when a plan comes together. Thank you for your efforts and your contributions. Glad to hear you are rooted.
[Android General] Hippychic1us:
At first it wouldn't download any updates Google play was offering. It hasn't offered me an Android system update yet. It now has updated all the apps google wanted updated and now I see it has a setting disabled that cannot be enabled and it makes it impossible to use an app I use called Mistplay. I want to root it and I am happy to learn how to repartition it. I am grateful to everyone here that is working on this and for your replies as well.
[Android General] Duhjoker:
you rock ty for the patched boot.img.

i had a thought on the kernel. it would take a bit of dedication and time but i believe that if can pull the /proc/config.gz for the defconfig one could find all the neccasary drivers needed to build a new kernel.

edit: tried to fastboot boot patchedboot.img as a precaution but no go so i went ahead and flashed the image and now im rooted. i was a lil freaked as first boot after that was really long. i never really used it before today so i couldnt say anything about speed after but seems more responsive.
[Android General] Viva La Android R.I.P.:
Yeah I always take the safe route of booting before flashing too, but great news that the flash was successful. My guess is, we should be able to flash any of the partition images via fastboot, versus having to use the Phoenix tool. So you found all necessary blobs in the /proc/config.gz?

By the way, if you don't mind doing it and if you have time, could you post a full partition map for this tablet? I think /proc/partitions/ should list a full index. Thanks.
[Android General] Viva La Android R.I.P.:
Friend, have you had any luck with ADB communication between your device and PC yet? I'll try to walk you through setting up ADB manually if you're still stuck, by way of the Windows Device Manager.
[Android General] Viva La Android R.I.P.:
We are glad to have you on board. Now that firmware has been forthcoming, development will follow. It seems we have a couple of members here who are knowledgeable with compiling as well. I will get a full rooting tutorial posted soon. If you want to root now, the instructions posted by @EmmaDearest on the previous page are solid.
[Android General] Gborg3:
I will be trying with some different cables and the last possible USB port tomorrow.
[Android General] Viva La Android R.I.P.:
When you open Device Manager in Windows, what is your tablet showing up as?
[Android General] 13lack13ox:
I keep getting Oem unlock ability is 0, fastboot error when running oem unlock. Developer option is flagged on.

Do I have to flash the Stock Firmware Image v9 to be able to unlock the bootloader? I just dont understand how in developer options its set to allow unlocking, yet the command fails.

Maybe wrong fastboot version? Not sure what it could be at this point. Fastboot devices reports back serial number.

In the process I did noticed the option in developer options greyed out until you finished the setup, with a connection >.>. What's that all about? Can only be a developer and allow bootloader unlocking if you have a connection?

Glad there are people here messing with this thing, it's not even worth the $10 i got jipped for, nowhere did I read I would have to pay, in fact it said free. How can I pay $10 if I need to have FREE cell service, using qlink?

I've also tried holding vol up + power, until open android. Fastboot commands just say waiting for device.
[Android General] Viva La Android R.I.P.:
It's the manner in which you boot into fastboot mode. Look back through the thread and there are instructions how to boot into fastboot to unlock the bootloader. No you don't need to flash any firmware in order to unlock. Look back on Page 2 of this thread.
[Android General] 13lack13ox:
I have been trying that. VolUP+Power takes you to recovery. How are you guys using fastboot commands in recovery? VolDWN+Power Is download mode I assume, Which also does not accept fastboot commands.

What do I just keep pressing VolUP+Power until I get that android open screen? Cuz all I get is recovery doing it.

This is why I'm so confused..... The only thing I ever get too is fastbootd which give me that error while attempting oem unlock. I've read and reread that page 2. Attempted, THEN came onto the forums.

I see an open android for a split second while booting into recovery via vol and power. But it's never there for long. No way to do fastboot commands in that time. I've even left it waiting for device while doing that, and nothing. I can get to fastbootd via recovery and adb. But for the life of me no Idea how you guys unlocked by booting into fast boot some weird way. I've tried and tried with vol+power. I'm fully aware fastbootd you cannot unlock as it's been said. Just how do you get or boot into fastboot?
[Android General] 13lack13ox:
Turns out it was just a driver issue. I just selected generic android bootloader interface, and wala the command went through.

I feel dumb.
[Android General] Gborg3:
adb shows the device, adb reboot reboots into anything I want, then with the open android screen I wait interminably still with waiting for any device. Device Manager under Other devices it shows USB Developer while in the bootloader. When booted into android it is under Portable devices then Scepter 8 Tablet. ADB devices shows MD2112AP.., a blank space then 'device'
[Android General] 13lack13ox:
Something to try while in bootloader. In device manager yours shows USB developer?

Select that update driver

browse my computer for drivers

let me pick from a list of available drivers

Do you have Google, Inc > Android Bootloader Interface?
[Android General] Gborg3:
Google, Inc is not there and when trying to update the driver with the driver downloaded for it gives me yet another new error.

Luckily I went into device manager again on the computer and searched until I found a Le eco connected device or something and selected it to update the driver. Android bootloader interface and ADB options finally showed up. I installed the bootloader interface, opened up minimal adb and fastboot, fastboot oem unlock, it worked no problem and verified it when I booted up. This is a process in motion now and why is it always driver issues with windows? 🤔
[Android General] Gborg3:
Was there a long wait for anyone else with flashing the V9 firmware? It has said Caution Beginning Firmware Upgrade for a while with no progress and no time elapsed. It finally showed a pop up message saying it failed.
[Android General] Gborg3:
Was there any trick to getting PhoenixSuit to flash the V9 firmware or should I wait on it warning me Caution: Beginning Firmware Upgrade? When it started, the computer turned the tablet off but that is as much as it has done. No progress on the firmware installation is happening that I can see. Can anyone suggest anything/help?
[Android General] 13lack13ox:
Almost sounds like a time out, maybe another driver issue. It seems like it waiting for device....

I didn't flash anything other the patcedhboot img for root. I figured it would be "a ok" I'll check to see if I have device communication.

Maybe try a different usb cable?
[Android General] 13lack13ox:
Are you using https://androidmtk.com/download-phoenixsuit ?
[Android General] Gborg3:
I have tried multiple different cables with no difference and that is the exact link I went to for PhoenixSuit. ADB works with no issue, the tablet shows up as the Scepter 8 while in Android and plugged into the computer. I have tried forcing the driver to update but it shows everything up to date exactly as it is supposed to be. I will look for more drivers to disable and get rid of.
[Android General] Viva La Android R.I.P.:
Once the firmware image has been extracted into its individual partition images, the images can be flashed via fastboot mode versus Phoenix suite. As soon as I get a full partition map I will post fastboot instructions. I have free time coming this week.
[Android General] 13lack13ox:
OK I have successful flash using PhoenixSuit 1.10

What I did was have tablet on in usb debugging

plug it in run phoenixsuit 1.10

tablet will be detected

select image

then tablet will boot into some kind of download mode

I looked in dev manager and saw unknown device

I hit update driver and have disk, browsed to phoenixsuit directory > drivers > AW_Driver

Got a prompt about unsigned drivers installed

windows detected the usb device

flash went fine after that.
[Android General] Viva La Android R.I.P.:
Glad you got it. I plan on posting threads for rooting and flashing firmware. On the firmware flashing I'd like to separate the thread into using Phoenix and using fastboot. It's good to know you got the flash to complete successfully using Phoenix. So I'm assuming you are rooted and all is well there?
[Android General] Gborg3:
It does not show up as unknown device for me. It shows USB Device(VID_1f3a_PID_efe8) and trying to update its driver that way it says the best driver is already installed.
[Android General] Duhjoker:
Using Ubuntu (not wsl or wsl2) makes things a whole lot easier for using fastboot. Also from inside system run adb reboot bootloader. when it gets to the screen where the lil android guy is laying down with its hatch open, that is fadtboot.

i was doing some thinking and twrp has a device tree maker. it would take some hard work and experimentation but one can build a recovery and/or rom with a prebuilt kernel. we would have to make a vendor though by hand.

im still looking researching where i can pick up the gki module source but for the most part it seems to use mainline kernel source.

at this moment i dont know too much about gki as my current device doesnt use it but im still hoping the manufacturer will give you the kernel source
[Android General] Gborg3:
It says it is an MTP USB Device
[Android General] 13lack13ox:
Yeah all is well, actually rooted twice, lol

Just experimenting with different things now trying to pull from it.
[Android General] 13lack13ox:
Thats very similar to my device name. What you posted USB Device(VID_1f3a_PID_efe8) looks legit to me.
[Android General] Gborg3:
I wonder how booting the computer into test mode would affect things. I have had to use it for dealing with Oppo Find 7 phones. I am going to try whatever sounds fun until it works.
[Android General] Viva La Android R.I.P.:
Test mode should definitely let you install the unsigned drivers on Windows 10 (64-bit) or Windows 11.
[Android General] 13lack13ox:
Yeah maybe I should of mentioned I have policy changes on my pc, I get warnings, but are allowed to do certain things. I've run my pc's like this for so long, I forgot how it's like for most people.

Driver signature enforcement. Oddly enough, the installers for those tools (the ones that have installers, Tried a few different ones.) don't seem to trigger the warning. Just report back failed, or no notice at all. Which leads me to believe that people just think everything went ok. At least this was my experience, having to manually install drivers. Maybe it should be something to report a bug. Maybe not. Anyways it's outside the scope of this topic. I'll leave it at that.
[Android General] Viva La Android R.I.P.:
Ok guys I finally have a little time off work. I'm going to be working on a full rooting tutorial thread and a firmware restoration thread for any of you who need step-by-step instructions. Also, I have a TWRP port build for the Scepter 8 that is almost stable enough to post. I'm getting it ironed out now. I have posted a step-by-step rooting guide if anybody needs instructions. https://xdaforums.com/t/guide-root-...8-bootloader-unlocking-rooting-guide.4410341/
[Android General] 13lack13ox:
That's awesome, I want to give some xposed framework variants a try.
[Android General] Viva La Android R.I.P.:
@13lack13ox, I have an inquiry for you. By any chance, have you disassembled one of these tablets or at least had the back cover off? AllWinner chipsets, as you probably know, have the series and version printed on the SoC itself in white lettering. I'm running across some conflicting info in the /system/build.prop and some of the /system/proc files regarding the chipset version. There are several indications that the Scepter 8 may have the AllWinner-A133 versus the -A100 I had initially thought. Both chipsets integrate quad-core Cortex-A53 CPUs. CPU-Z lists it as a sun50iw10p1, which can also be either the -A100 or the -A133. I'm presently porting an unofficial TWRP

I'm hoping to have it ironed out today or tomorrow. These devices that use the dynamic partitioning scheme can be problematic when it comes to porting or compiling TWRP.

I was having some issues with dm-verity but I have those fixed now. Aside from a couple of partition mounting issues and touch screen sensitivity, it's looking good. My goal tonight is to resolve the fstab flags so that all partitions are recognized and mount correctly. I just now figured out that our /userdata partition uses the f2fs filesystem format, so I hope changing that from ext4 will fix that mounting problem.

Yeah I'm anxious to play around with some Xposed frameworks myself and perhaps Gravity Box. I already have a TWRP flashable stock ROM put together as well.
[Android General] 13lack13ox:
Some cool news my friend. Regarding the series number. I haven't had the back off, but I can sure take a look for you. I'll get back to you as soon as I find out.

easy enough.

A100-863-v1.0-20B I assume that's a100 there. That's written on the white tag. Under the back cover.
[Android General] Viva La Android R.I.P.:
Thank you very much my friend. That sets my mind at ease. Our firmware is actually from an A133 build, but the A100 and A133 have nearly identical core configurations, so that explains the compatibility. But as far as TWRP goes, I need to be exact, so again thank you much. You've been a great help on this device.

I've noticed that a few members are having trouble with device recognition with ADB, fastboot and Phoenix Suite, so I'm going to outline some step-by-step instructions in the rooting thread for setting up the drivers on Windows.
[Android General] J-Mizzle:
How is the TWRP and recovery flashable firmware coming along? All of my systems run Linux and I softbricked my Scepter 8. I tried flashing GSI builds via fastboot just for the hell of it. No dice, so if anybody else is thinking about trying a GSI, don't do it for now. I know I could install Windows or spin up a VM but I have no interest in doing so. I basically plan on continuing to use this tablet as a comic reader and nothing else, so I'm in no rush to fix it, just curious how the recovery build and flashable stock rom is coming.

Side note: seems that mainlining the Allwinner a100 is being worked on, so we may be able to run PostmarketOS and other Linux distros on it someday.
[Android General] Viva La Android R.I.P.:
My TWRP is stuck on a snag related to decryption of /userdata and /vendor. I'll keep a status on things posted in the beginning of the thread. Have you tried using Linux to fastboot flash your device with the partition images contained in the firmware image file?
[Android General] J-Mizzle:
The RAR file fails to extract. I've downloaded on 3 PC's and 2 mobiles using 2 different connections. Fails every time.

Edit:

I managed to extract the img file from the rar archive. Getting errors extracting the partition errors from the .img file. Seems to be more partitions then I remember from last time I flashed manually to a device via fastboot. I guess I'll wait and keep an eye on progress here.
[Android General] Viva La Android R.I.P.:
Let me know. It sounds as though I may have a corrupt archive on my cloud storage. I'll check it thoroughly. Thanks for the feedback. What's odd, is I have gotten errors as well when extracting the actual .img firmware file. However, when I flash the image using PhoenixSuit, everything goes fine and without errors. I'm going to use root terminal to pull the partition images directly from my device. I already have the super.img pulled (which contains system.img and some vbmeta files). I'll archive the images I pull and upload them for those who want to use fastboot for firmware installation.
[Android General] sketchscarz:
awesome i got it rooted the patching went great and the magisk showed in the app drawer. I updated magisk .. it asked for root permissions then i went to direct install and it patched something else.. just wondering if there is any twrp support.. I cant remove apps via ADBAppControl, says the device is not supported.
[Android General] sketchscarz:
I also installed titanium backup, and putting forth a little effort to create a custom ROM. Any advice?
[Android General] J-Mizzle:
Putting it up for tonight, I may have rendered it useless with my GSI attempts as I can no longer access fastboot, recovery or bootloader. Looking like a made a new paperweight.
[Android General] Viva La Android R.I.P.:
There are guides here on XDA for porting custom ROMs. As a base ROM, you'll first want to find one with specs similar to the Scepter 8, but especially.with the same chipset platform - Allwinner-A100. From there use a porting guide to create the ROM. It's a tedious process.
[Android General] Viva La Android R.I.P.:
You don't need ADB to remove system apps once you are rooted. Install a good file management app such as MiXplorer (it's free and hosted here on XDA). Grant the file manager root permission. Most of the preinstalled apps are located at /system/app, system/priv-app, /product/app and product/priv-app. Be careful on what you remove. As you may know, having root access gives you the power to mess things up within the core system. There are also some preinstalled apps in the path of system_ext/priv-app.

For a simpler route, just install a system app remover from the Play Store. If you're unsure what to use I can try to find you one that will suffice.
[Android General] 13lack13ox:
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
[Android General] J-Mizzle:
Never heard of that but no, it doesn't work. I think I'm just going to toss it in the garbage tbh. Not losing much.
[Android General] 13lack13ox:
I was unable to access adb debugging and this saved me, using phoenix suite. Was thinking maybe it could of worked for you too. At least to flash back the default v9. Guess you got to some pretty vital partitions. I'd take it off your hands but prolly costs more to ship it then it costs. lol
[Android General] Viva La Android R.I.P.:
Fastboot mode and download mode are both low-level bootloader functions used to enable device flashing from a host terminal. Fastboot mode is often confused with download mode and vice versa. This is especially true in light of the Scepter 8's secondary fallback fastboot mode, which is the mode needed to unlock the bootloader.

To enter the relevant fastboot mode, power your tablet off. Hold Power and Volume Down together until the QLink logo appears, at which time you'll release Power but continue holding Volume Down. When a green Android graphic appears on screen, you are in fastboot mode. .

Download mode is the function used by PhoenixSuit to flash firmware images. The screen is completely blank in this mode but you will notice a dim backlight. To manually enter download mode, use the steps provided by @13lack13ox.
[Android General] J-Mizzle:
I am aware what fastboot mode is and am more than familiar with it, my point was that I am no longer able to access fastboot or the bootloader after playing around with attempts to flash GSI images to the device. The normal button combinations nor terminal commands work anymore. I do have a dim backlight when trying to boot the device, so maybe it is booting into download mode. I'd have to check if the device is still detected by when plugged in via USB next time I am able. I'm not overly concerned about it but if you want to explain how to determine if it is in fact entering download mode, I'll gladly post if it is in case it can help somebody else facing similar issues here in the future.
[Android General] J-Mizzle:
It didn't seem to do anything when I tried it. Maybe I'll try again. Right now the screen remains blank with only the backlight on. Not sure if it's booting straight to download or not. I most liking messed up some vital partitions as you said, I wasn't cautious at all while messing around since it wasn't a device I really cared about, all I had used it for was reading digital comics and it sometimes even struggled to do that. Lol. I do believe Phoenix Suite needs Windows to run, yes? I'm not interested in installing Windows even on a VM, so that's not an option for me either. But yes, it probably would cost more to ship than it is worth. Not sure where you live but I live in Maine.