yashsingh1/xdaforums huggingface dataset:
[Android General] Viva La Android R.I.P.:
That's odd. Mine is fully open to change, with all 4 preset schedulers as options. I'll look into possible causes for this anomaly. It is possibly due to SELinux Enforcing Mode. Mine is set to Permissive. Try setting yours permissive under the Misc menu in Kernel Adiutor.

Also, here is an excellent up-to-date thread on governors, I/O schedulers & the like. https://xdaforums.com/t/ref-guide-m...pu-governors-i-o-schedulers-and-more.3048957/
[Android General] 13lack13ox:
My kernel version is 5.4.99 #2 Mon Feb 21 14:49 cst 2022

Also I didnt have that option to set permissive in any of the kernel editors.

I'm wondering if there is something different in v9 vs the older(v6? was it?) in the firmware. Maybe I should try to flash the old version, and see if it's tunable. I just did a complete wipe with v9 firmware. Still no go on the io sched.

Just curious did you flash v9? and format completely? or just flash on top of what was already existing.

Oh yeah forgot to say I'm also using the patchedboot.img that was provided. Maybe I should go about manually patching my own?
[Android General] 13lack13ox:
Haha don't flash v6 firmware. I take it it for a different device. Had to go about emergency recovery, The screen doesn't even render right on v6.

I take it there are 2 different tablets out there. AT least I know how to flash if you cant get to turn on adb debugging.

Hold power for about 10 seconds to power off device

press any button hold it and plug in usb cable

Tap power about 10 times.
[Android General] Shponglehead:
Wonderful. Thank you, Viva La Android and @EmmaDearest for you excellent work.
[Android General] Okay-peach22:
so ive unlocked the bootloader but it will not let me flash. it says file is corrupted. the patched_boot.img
[Android General] Viva La Android R.I.P.:
Re-download the boot image. I checked on my end and it's okay.
[Android General] Okay-peach22:
i figured it out i downloaded the wrong driver🤦‍♀️🤦‍♀️
[Android General] Viva La Android R.I.P.:
So are you now rooted?
[Android General] Shponglehead:
This is my first time rooting a device so I could use some help with magisk manager and TWRP. I've read a few articles in XDA but I'm confused with what version of TWRP I need. Does it have to be the device specific version of TWRP? And as far as magisk manager, how do I install it and is it similar to f-droid?

Thank you!
[Android General] Viva La Android R.I.P.:
You don't need TWRP to root. As it stands TWRP is a work in progress. Follow the above guide step-by-step to root your tablet.
[Android General] Viva La Android R.I.P.:
The V6 firmware is indeed for the Scepter 8. Allwinner devices don't play nice when trying to downgrade. I have warnings listed in the flashing instructions regarding V6 in the firmware restoration thread.
[Android General] Viva La Android R.I.P.:
My SELinux mode is set to permissive and that may be required in order to mod ZRAM.
[Android General] 13lack13ox:
Do you set permissive via boot script? Or /etc/selinux/config?
[Android General] Viva La Android R.I.P.:
You can download an app called the SELinix Switch. It's here on XDA by developer Ibuprophen. Here's a link

[APP][TOOL][2.0+][OFFICIAL]The SELinux Switch

The SELinux Switch . What's The SELinux Switch & What Makes It Different from The SELinux Toggler? I'll outline this in brief since it would take too much time and space in explaining everything in detail. Primarily, The SELinux Switch was...

xdaforums.com
[Android General] Shponglehead:
Oh I already had it rooted. I guess I thought that twrp was a separate thing from magisk. What about magisk manager?
[Android General] Viva La Android R.I.P.:
The Magisk app installed on your tablet is Magisk Manager. It sounds like you're good to go. If you are unlocked and rooted then you have completed the tasks.
[Android General] Viva La Android R.I.P.:
Can you confirm that the Magisk app is installed on your device? If so, when you open the app, in the top box of the app interface, you will see a heading labelled INSTALLED. Beside of that heading, if you are properly rooted, will be the Magisk version installed on your tablet. It should indicated 24.1 or 24.2.
[Android General] Viva La Android R.I.P.:
@13lack13ox let me know if setting SELinux to permissive mode enabled the I/O scheduler to be changed. Thx
[Android General] 13lack13ox:
That's a no go. I attempted beforehand using terminal to change to permissive. Using setenforce Then try to reinstall kernel apps to configure, and notta. I've tried format flashing v9 again and not installing busybox, notta.

I almost feel like there was something left over in v6 that can be carried over to v9 by flashing without formatting. Possibly yours was upgraded different? You didn't change anything else?

I'll have to try all that again, I never did a full format installing v6 then upgrade flashing v9 without a format. Maybe some kernel variables were left over by doing this? I don't know enough about it all. Kinda wish I could get the tablet to play nice doing a downgrade. Would be cool to mess around with v6.
[Android General] 13lack13ox:
Also I dunno if people had trouble getting phoenix usbpro to work right. It's a little weird how it all works.

Powered off device

select image hit start

now press a vol button on device and hold it

plug in usb

while still holding tap power 10 times

the program should pick up the device and start the flash.
[Android General] Viva La Android R.I.P.:
I am unpacking V6 and will install it using fastboot, flashing only the super.img and boot_a & boot_b. Just to experiment a little. Yeah there's a subtle difference somehow between your config and mine. I'm back on that road working tonight so I'm going to have little time to tinker. With that said, I don't know what your schedule looks like or if you would be willing, but I need somebody to answer questions and help members with issues on my Scepter 8 threads. Even if just a little bit. I'll even say please. 🙏

I'll be chiming in when I can and I'll only be away from home for a week. You are knowledgeable with Android so I wanted to ask.
[Android General] 13lack13ox:
Sounds good, I'll do my best.
[Android General] Johngrogers12:
So I'm stuck at one point in my attempting to unlock my bootloader and root my scepter 8 tablet v6 is where I started. Amazingly I was able to get to the point when you use the fastboot device command and actually got back the serial and I was ecstatic because I have been attempting to root a device, for a couple maybe more year with no success ill admit my attention wonders... a lot and with that my interest so if after a couple of days i did not get it i usually gave up but once i saw the this forum you have started Viva la android about the scepter I was like not giving up til im rooted or bricked. I have literally read over the 3 main threads you started multiple times and i think over installed some things, anyway im where you have the green android guy open with the numbers showing or rather no numbers but 16 squars ( not sure if thats spelt correct think not) um but yeah when you let off the power button there literally what seemed like no time before the green man showed up is that the point at which you release the volume down button or no. because I started out holding til i was pluged in and entered the fastboot command and also right after the green guys showed up where im stuck it since i got back the serial number back the one time and fallowed with the unlock command the didnt work i forget exactly what it said but i went on to the device manager i did the usb update. 2 things any suggestions and is there any way to use the phoenix suit to root it i tried using it to flash just the patched file thing i realized that would not work but is there a manor in which it would? not just viva la android any input would be greatly appreciated.
[Android General] 13lack13ox:
So you are having trouble running the command fastboot oem unlock?

in developer options tick on oem unlocking, and usb debugging

I assume you have adb working, plug in device and check: adb devices

If you get back serial number run command: adb reboot bootloader

An open android screen should appear.

Now run command to verify: fastboot devices

you should get back a serial# fastboot

If so run command: fastboot oem unlock

You should get a confirmation message, run command: fastboot reboot

The device will perform a reset.

You should be able to pick back up with rooting step using patched boot image, and magisk.
[Android General] Johngrogers12:
checking the adb device got back serial

adb reboot worked

checking fastboot devices after reboot into fastboot mode did not work and thats where i keep getting stuck.

thank you for your help
[Android General] Viva La Android R.I.P.:
Like many other Scepter 8 owners, you have encountered an incorrect or incompatible fastboot driver. I have the remedy. At the beginning of this thread, in the instructions, I outlined a troubleshooting section titled Installing USB Device Drivers, which outlines concise instructions on how to manually install/update the fastboot drivers and enable recognition/communication between your computer and tablet in fastboot mode.
[Android General] Johngrogers12:
and that was the issue ill start with i just put apk pure or something like that root checker and im rooted finally i had believed i did the driver update but again i tried put it into fastboot checked fastboot devices no go went to device manager yet one LAST time and this time i chost something adb which i thought i already had but apparently not then a bit of trouble rooting with it saying the file was corrupt so finally i redownloaded it and opended the command prompt form the directory i had only the one file and tada. Thank you so much

13lack13ox and viva la android you guys have been super cool and very helpful ive been trying to root a device and always said **** it til finally a device that actually needed it and a thread on forum with very welcoming and helpful people for which im am very greatful!!!
[Android General] SamuEDL:
I delete the message, to avoid misunderstandings ...
[Android General] Viva La Android R.I.P.:
To keep this thread on-point and in compliance with XDA rules & guidelines, I need to remind members that this thread is only for topics regarding rooting and/or unlocking the bootloader on the QLink Scepter 8 tablet. Posts about other devices are off-topic and will be removed if a moderator sees them. However, I believe such posts would be permitted under our QLink Scepter 8 General Info & Discussion thread which, by nature, allows more leeway regarding subject matter. https://xdaforums.com/t/index-guide-q-link-scepter-8-tablet-general-info-discussion-thread.4385631/
[Android General] SunSlide:
So I created a XDA account just to thank you Viva and the others that worked on this! I wanted to mention that this was super simple using a linux machine. No driver issues or nothing like that, but it kind of through me off when adb wasn't showing the tablet after 'adb reboot bootloader'. Apperently, as I read elsewhere else, adb and fastboot do not work at the same time and using 'fastboot devices' had no problem showing the tablet. Thanks Again!!!
[Android General] Viva La Android R.I.P.:
Linux always simplifies things it seems. Using Windows on procedures like this seems to always be buggy. I've got to start using Ubuntu or another Linux distro. Correct, ADB & Fastboot are two separate and distinct command-line modes that do not run simultaneously; each runs in its own user-initiated boot mode.

In any event, I'm glad this worked out for you and you accomplished the desired results. Congrats, and thank you for the kind words of encouragement. @13lack13ox has been a huge help to me in keeping up with support inquiries and general thread questions. I thank him. Now that you have created an XDA account, I hope you'll be a part of this amazing community. We need members like you.
[Android General] Alkuam:
I guess that explains why I didn't have the fastboot issues, I used linux mint.
[Android General] Shady8550:
so i managed to run cmd "fastboot oem unlock" but when i tried to run cmd "fastboot reboot" it didnt reboot and a page came up that said "your device cannot be checked for corruption lock the bootloader" then refered me to this page g.co/abh

so i locked the bootloader and know same page only it says "your device has loaded a differant operating system" and referred me to the same website i fixed it somehow
[Android General] Viva La Android R.I.P.:
When you unlock the bootloader -- and this is the case on many Android-based devices -- it is completely normal to get a warning prompt during the boot sequence. Disregard the warning and allow the device to boot up normal. The fact that the warning dialog screen appears is confirmation that you successfully unlocked your bootloader. Again, this is not an error; it is a merely a warning flag that is triggered when you unlock your bootloader. My device shows the same dialog during boot, as do the devices of all other members with an unlocked bootloader.

So your fastboot reboot command did in fact work. Your initial reboot after performing the unlock will include initialization of a factory data reset, after which the device will again shut down and begin a full boot sequence into the Android OS.

Many members, including myself, consider the warning dialog annoying during every boot sequence. A custom splash screen image can actually be flashed which will make it disappear. While I haven't got around to doing it yet, this is a project on my list.
[Android General] Shady8550:
Yeah I got that now I was able to root but now I had to reboot for one of my apps and now it won't boot at all
[Android General] Viva La Android R.I.P.:
What is the name of the app?
[Android General] Shady8550:
Ignore
[Android General] Shady8550:
2 minutes ago

Add bookmark

#62

Build.prop editor I think it was that app i was following the instructions you put out on page one to make the tablet run faster but it could be the kernel toolkit maybe
[Android General] Viva La Android R.I.P.:
Sounds like you may have entered a line or flag incorrectly. It's easy to do. Are you familiar with restoring the firmware using PhoenixSuit? Follow the steps in this guide to fully restore your firmware and revert your device to its stock factory state. https://xdaforums.com/t/guide-firmw...firmware-restoration-upgrading-guide.4412585/
[Android General] Shady8550:
Okay thanks for the help this only my second root I attempted this but was unable to get the device recognized by Phoenix suit should I be in fastboot mode or just leave it on
[Android General] 13lack13ox:
Try with PhoneixUSBPro_V4.0.0

Device powered off and unplugged.

open PhoneixUSBPro_V4.0.0 and select image hit start

hold a vol button and plug in

do not let go of vol, tap power button 10 times.

With phoenix suit I think you need to manually install the driver to work with it correctly, the device also needs to be able to power up and adb debugging on.
[Android General] Shady8550:
the thing is im like 60% sure i left debugging off but will give it a go just in case it is still on
[Android General] Viva La Android R.I.P.:
With PhoenixUSBPro, you don't need ADB Debugging to be enabled. It recognizes and flashes your device from a powered-off state. This is why @13lack13ox recommended this to you, as he explained above.

I had completely rewritten the firmware restoration guide for the PhoenixUSBPro utility, as it is more practical for devices which are stuck in a boot loop or unable to power up. After over an hour's work, I accidentally tapped the back button and lost every bit of my work. I'm too aggravated at this point to rewrite it again, but I plan on doing so later today after I've slept some. Big thanks to @13lack13ox for suggesting this tool over PhoenixSuit.
[Android General] 13lack13ox:
I think phoenix Suit can handle it too in the same way actually. IIRC, I remember reading some prompts about not being able to switch to bootloader mode or something. Which is why it needs adb usually. I think this is where I got the steps about holding vol and tapping power. It's getting hard to remember as I switch around and play with different devices.

But anyways yeah you should be able to recover using PhoenixUSBPro certainly using that vol hold and tap power trick. phoenix Suit was meant to use with adb debugging, even though it prompts you about not finding a device and gives you steps how to flash without it. I just suggested PhoenixUSBPro because I know it's a fail safe way to flash.
[Android General] 13lack13ox:
@Viva La Android may I ask how you extracted super.img? What tools do you suggest, as I get unexpected end using 7zip. You said about flashing super.img using fastboot awhile back to play around. I just want to take a look at the system img myself.

Would be nice to make a non bloated img to flash, if an event happens. Just to save some time. Since we dont have a decent recovery yet.
[Android General] Viva La Android R.I.P.:
Yeah the PhoenixUSBPro tool seems highly akin to SP Flash Tool for devices with MediaTek chipsets -- both can recognize and flash hard-bricked devices from a powered off state, without need of USB Debugging being enabled. I think the PhoenixUSBPro tool will be much less problematic for firmware restoration in terms of device recognition and USB driver configurations. I'm going to revise the firmware restoration guide later today, replacing PhoenixSuit in favor of PhoenixUSBPro v4.0.0. Thanks again for your input.
[Android General] Viva La Android R.I.P.:
There is a tool here on XDA that works well. The full guide with download links are here:

https://xdaforums.com/t/editing-system-img-inside-super-img-and-flashing-our-modifications.4196625/
[Android General] 13lack13ox:
Ill have to try to extract Scepter_8_Tablet_V9_20220221.img in ubuntu in vm.
[Android General] Viva La Android R.I.P.:
There is a Windows tool called Super.img Unpacker in the event you do not want to set up a virtual machine. https://forum.gsmdevelopers.com/general-android-unified/97307-android-super-img-file-unpacker.html

By the way, I have revised the firmware restoration thread, replacing PhoenixSuit with the PhoenixUSBPro_v4.0.0 tool.
[Android General] 13lack13ox:
Already tried that tool, I just get an error please select partition. None are listed to select. It's ok I actually like linux it's been awhile so it will be a good refresher.

EDIT

Bah I'm giving up everything I try I get header errors. I just can't get to the img's inside the img. for some reason. I should be able to
[Android General] Viva La Android R.I.P.:
Try the CRB Android Kitchen for Windows. It runs in Windows Subsystem Linux (WSL) mode via a Linux distro It includes a free and donate version, and it's also easy to set up it includes a ton of tools and utilities for unpacking and repacking super.img and building custom ROMs. Here's the link:

https://xdaforums.com/t/tool-windows-kitchen-crb-v3-0-0-beta14.3947779/
[Android General] 13lack13ox:
My problem is getting to the super.img. I can't pull any of them out without header errors. I'll have to try a different approach I was able to mount the v6 image in linux, just dont know where to go form there. I gotta do something on with the loop and pull out super.img I think. It's been a long long time, and not used to dealing with these dynamic partitions, and frankly firmware as .img

My thought was it all would of been as simple as extracting the boot_b that we patched with magisk. But it aint.
[Android General] Viva La Android R.I.P.:
If you need, I can upload the partitions I extracted from Super.img and send you a link There are three partition images: product_a.img, system_a.img and vendor_a.img I went a step further and extracted the contents of each of these three partitions. I have the directory folders for each. Do you want me to upload them and send you a link? If so, do you need them in .img format or as directory folders?
[Android General] Viva La Android R.I.P.:
In getting the Super.img, I pulled mine directly from my device using ADB shell with root:

dd if=/dev/block/by-name/super of=/sdcard/super.img

You can likewise use a terminal emulator with root permission. This will essentially dump your entire /super partition and save it as a raw .img file on your internal storage. Once you have super.img, use the Kitchen software I mentioned previously for extracting its contents
[Android General] 13lack13ox:
No worries, I can just pull from my device. I was trying to do the v6 rom to take a look at it. Maybe I can do the same with that as well. I check it out. My thought process wasn't thinking i could because the screen didn't render. But now that I'm thinking about it I could flash over and possibly still have adb shell available.

also I think i could use that dd command in linux right? My img is mounted /dev/loop8 (read only)

I'll figure it out.

Still don't understand how you have the io scheduler options maybe I would like a link to yours.
[Android General] Viva La Android R.I.P.:
I'll use the Kitchen to extract the V6 firmware. I've been meaning to do that anyway. Yeau i don't get the I/o scheduler optiins either. Very perplexing. Anyway when I get the V6 firmware extracted I'll send you a link to the files if you want.

I just caught what you're saying about installing my firmware dump on your device. At the time I pulled my /super partition, my system was completely unmodified. However, now that all my system and kernel mods are in place, I could pull my /super partition and boot.img, upload them to cloud storage, and give you a link Fastboot can be used to flash both images to your device. In theory, this should enable I/o scheduler changes on your device. Let me know.
[Android General] Viva La Android R.I.P.:
Hey @13lack13ox, I just extracted the V6 firmware package, and used the kitchen utility to extract the super.img file. What partition do you need from the extracted V6?
[Android General] 13lack13ox:
Sure send me what you got. I would def like your modified of v9 =-)
[Android General] Viva La Android R.I.P.:
Sorry for the delay friend. Today has been chaotic with work. An entire base station is offline with no apparent cause for the network drop. Tedious troubleshooting. Anyway, I'm ranting....

Here is the folder for the extracted V6 super.img: system_a.img, vendor_a.img, and product_a.img. These are in raw image format. I have also included the source V6 super.img. Keep in mind that these are uploading as we speak. If the folder doesn't yet contain the 4 items, they will become available as the upload progresses. If you need more partition images from the extracted V6 firmware, just let me know and I'll add those to the folder I linked you

Update: I went ahead and included all the key partitions in the folder, including /boot, /bootloader, /vbmeta, /misc, etc. I included a plain text file named partition_index that gives a complete breakdown of the partition mapping on the V6 firmware.

I will dump my tablet's modified v9 boot.img and super.img as soon as time permits; most likely, later tonight.

File folder on MEGA

mega.nz
[Android General] Viva La Android R.I.P.:
@13lack13ox, I have done a full firmware dump on my tablet of the v9 firmware images. I am uploading them and will get you a link to the folder shortly. Like with V6, these images will become available to you as the upload progresses. Other than super.img, most partitions are not large in size.

Update: here is the link. I'm at a Holiday Inn and uploading on WiFi but it's fairly quick

File folder on MEGA

mega.nz
[Android General] Viva La Android R.I.P.:
@13lack13ox here is a screenshot of my I/O scheduler using Kernel Toolkit. You should see these four options after flashing the v9 firmware from my device.

I have found kyber to be the most responsive by far. I've been tweaking the mq deadline scheduler as well. Also a good I/o scheduler preset.
[Android General] 13lack13ox:
Well I did flash the super.img and boot but I still didn't have that available. Still playing around. Do you know what UDISK.img is? I'm curious as it's 4 gigs. In original firmware.

Trying to package everything back into a flashable image via phoenix once. I don't know if I can manage it but I'm trying.