yashsingh1/xdaforums huggingface dataset:
[General Topics] Sands207:
Good point. Will do! :)
[General Topics] Viva La Android R.I.P.:
And if you have any issues whatsoever, just leave a comment and I'll do my best to get you through it.
[General Topics] Sands207:
Thank you, I definitely appreciate it. I'm going to take a crack at it again later today. I'm currently developing for several other devices and got side tracked
[General Topics] rupe01:
Hi.....i am finding that all the Mega links are dead.....are there new links, please? Thanks.
[General Topics] rupe01:
Ah, OK.....just read your note saying you were moving the files. No problem....i can wait, thanks.
[General Topics] rootmeb100:
Viva I've rooted my scepter 8 several times and I'm able to restore it but I'm in need of the firmware. Thx for all your help
[General Topics] emmieb:
So are there any other sources for this firmware? I haven't been able to get it since I have been following this thread. I'm trying to fix my nieces pos tablet, she's five and she doesn't have another one to use in the meantime. Hard to believe this is the only source for this fw, but for the life of me I can't find a damn thing. Anyone have any suggestions? Would be much appreciated. Thanks
[General Topics] Viva La Android R.I.P.:
Which tablet do you have? The Gen 1 or Gen 2? Also, what are the first 2 letters of your serial number?
[General Topics] emmieb:
It's a gen 2 serial MD

thanks!
[General Topics] geekonabeach:
I’ve bricked it so hard that fastboot and recovery won’t come up. Only a blank screen with a bright backlight.

It says it’s an A100 chip with MD as a startling S/N

Can you link me with the firmware needed.
[General Topics] Viva La Android R.I.P.:
File on MEGA

mega.nz
[General Topics] geekonabeach:
I would have sworn that this tablet had the v9 and at one point I saw that it had an A133 chip in some recovery logs but I failed to document that. So we downloaded the v9 from before and we can’t get it to take under any route you’ve got.

Thanks for the firmware and I’ll try it tonight.

Attached you find the full SN.
[General Topics] Viva La Android R.I.P.:
You may have been running.a newer build than the v06 I sent. Your label indicates that the v06 is the correct package for your model, so it should flash properly. Here is a link also for the v09 build, but keep in mind that it is for the S/N CF model.

File on MEGA

mega.nz
[General Topics] geekonabeach:
We will try both and see....
[General Topics] emmieb:
thank you so much! ❤️
[General Topics] geekonabeach:
Bad news. I think we have our first bricked in a hard way tablet.

We have done every method that’s here and any other method, we’ve used every computer we have (Mac, archlinux, raspberry pi os, windows 10, the sd card, and crossed fingers mediums) but to no avail. We made sure the drivers were correct and used the logs to see activity but for not.

All we can get it to do is turn on with a blank but brightly lit screen and nothing more.

We can get it to be recognized in FES mode with the button presses method, but the programs time out like it can’t then transmit to the tablet. Like it’s not able to receive.

So we tested the cables and the connector on the board and sound no fault there.

At one point this thing work. Now it sets bricked and cannot find anything recommended to get it out of it.

So before you go asking, we have read the forums countless times, did EXACTLY as described multiple times and used the correct firmware (v6 then v9 for the trill) with no life being breathed in to the thing.

What ideas you have?
[General Topics] Viva La Android R.I.P.:
Well, I'm a staunch believer in the concept that Allwinnwer tablets cannot be hard bricked from user-end modifications. So the tablet is being recognized and flashing commences, but the process times out? That is an odd behavior I have not yet heard of.

Have you by any chance tried Method 4 with PhoenixCard? It allows you to flash the firmware image from an SD card.
[General Topics] geekonabeach:
Yes. And it will not run in at all.
[General Topics] Viva La Android R.I.P.:
I'll research your issue via the official Allwinnwer chipset release docs and see what I can find out.
[General Topics] rootmeb100:
Can you send the a100 cf chipset firmware and patched image to a fellow tenneseean?? Chattanooga here.
[General Topics] rootmeb100:
Sorry running android 12 a100 chipset and CF. I can't get firmware or patched boot. Also I noticed github has the tree files for twrp? Is it operational? And as for brickjng I agree. I've got my scepter 8 booting up with wrong firmware "Im guessing" but I have no screen. I know ghis bc I can run adb commands.
[General Topics] Viva La Android R.I.P.:
The firmware for the Gen 1 should be working on the links. I'll post you a patched boot image file shortly.

Magisk patched boot.img a100cf

On the TWRP tree, I was not aware. To the best of my knowledge no kernel source code has been released for either hardware variant of the Scepter 8.

In case link isn't working, a100 CF firmware

Scepter8_tablet_a100_cf_v09
[General Topics] rootmeb100:
Viva thx for your help and support. I'm not sure how but my device says its an a133 through running adb shell get prop. But under the back cover it's an a100.can you plz sen d a133 cf running 12 to try.
[General Topics] rootmeb100:
Still blank screen boot
[General Topics] rootmeb100:
I was in the sMe boat but I'm not very easily to give up on much. Here is what I did. Same scenario you have by flashing the wrong software countless times. Then I noticed my computer was picking up the ol scepter government 8 nexus 6 wannabe. Hold power button 10 sec to ensure its definitely off. Have computer booted up and on device manager. And yes I'm still blank screen now. Wink wink Viva my friend. Anywho. Power up you tablet and immediately plug in to your computer. Mine will go edl then it shows scepter as other devices and fortunately next it goes into adb device... blank screen. At this point you have options to work the adb kungu and then fastboot reboot bootloader. I've pulled it out of the same dead screen several times by fastboot flashing. Hope this helps. I'm hoping your device is in the same scenario. I think what's happened is we've flashed different chipset software and and our video drivers are not compatible. But I'm sure we can get out of brick state with correct firmware and patched img. I'm trying to make my own patch image rn with canary magisk and not having much luck. Either way hope this helps sir
[General Topics] omb714.1980:
I've got a completely different build number. Or am I missing something? Can someone pls tell me which firmware I should Use.
[General Topics] andrew1234abc:
I also have the same build and stuff. The link on the first page, the modified boot file is missing, and also the firmware downloads are missing or else I just make my own

Edit: not missing but mega took it down
[General Topics] Viva La Android R.I.P.:
Does your serial number begin with CF? If so, you can use any firmware from the Android 12 "CF" heading. I will be repairing all firmware links tonight, as well as links to the root boot images.
[General Topics] Viva La Android R.I.P.:
For any members needing Scepter 8 firmware images, I will be fixing all links tonight for all builds.
[General Topics] andrew1234abc:
Thx. Flashed the modified boot and it won't start now so thx for re uploading the firm wars files
[General Topics] Viva La Android R.I.P.:
Firmware builds for all models & variants are now available via the download links in the OP. The remaining dead links will be fixed very shortly .
[General Topics] omb714.1980:
Can you please just link me the boot.img file thats all I need. It should be less than 50mb not the whole img 2.2gb. If you have that it would be much appreciated then I can use Magisk to patch the boot.img then "adb reboot bootloader", then "fastboot flash boot boot.img", then "fastboot reboot" done. Just cant find that little boot.img file. By the way I'm using debian. Also I've found that the build numbers have to match up otherwise you run into issues and bricking. Also you should be able to post the boot.img here in the forums I see them in other threads for other devices.

Thanks for your time and hard work Viva La Android.
[General Topics] Viva La Android R.I.P.:
I fixed the link for the Android 12 patched boot image in the rooting thread. The build numbers do not need to match. The boot image on the Scepter 8 is based on the Android Common Kernel (ACK) implementation, which is fully backwards compatible. As long as the boot image is more recent than the boot image currently on your device, you'll have no issues. You can use an image extractor and unpack all the individual partition images from the firmware.
[General Topics] Viva La Android R.I.P.:
@omb714.1980, here is a link for an unmodified stock boot image from the Android 12 (Go Edition) v03_20220915 firmware package.

Stock boot.img & vbmeta.img (v03_20220915)

Looking back at your post, you left out a couple of the steps. You need to flash both slots of the /boot partition.

fastboot flash boot_a boot.img
fastboot flash boot_b boot.img

Next, you need to disable AVB/dm-verity using the vbmeta.img I linked above with this command:

fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img

Then,

fastboot reboot
[General Topics] Sands207:
Thank you for uploading them =)
[General Topics] Viva La Android R.I.P.:
No problem. I changed cloud hosting services and the transition took longer than expected.
[General Topics] omb714.1980:
You are correct and thank you for those images. I didn't know about an image extractor thanks for the tip
[General Topics] omb714.1980:
Can you please link an image extractor you use for .img files
[General Topics] Viva La Android R.I.P.:
This is the tool I use

ImgRepacker Allwinner Firmware Extractor

In a nutshell, download the archived tool and extract its contents to an empty folder on your desktop. Right click the file called Runner.bat and run as administrator. Drag and drop a Scepter 8 firmware package inside the interface. Tap Enter two times to start extracting. The tool will extract a number of .fex files, which are a type of image. You can simply rename the file extension to convert it to a raw image. For example rename boot.fex to boot.img.
[General Topics] omb714.1980:
That work perfectly. Thanks again for all you have done. I there a custom recovery for this device and if so how would I go about doing it.
[General Topics] Viva La Android R.I.P.:
TWRP custom recovery is an ongoing project I have been working on for a long time. To compile TWRP properly, the kernel source code is required. To date, I have been unable to acquire the source code from the manufacturer, but my efforts are ongoing.
[General Topics] Viva La Android R.I.P.:
@omb714.1980, although TWRP isn't available at this time, I did want to mention to you that the Scepter 8 is Treble supported, meaning that you can flash custom ROMs built with the GSI (Generic System Image) protocol. These ROMs can be flashed using dynamic fastboot (FastbootD) mode I have only tested one GSI ROM, a LineageOS 19.1 (Android 12L) build, and it ran surprisingly smooth. I can link some info and resources on GSI installation if you're interested.
[General Topics] omb714.1980:
That would be awsome. I've just recently started tinkering with the phones I've collected over the years, so i'm pretty new to all these methods but i'm a quick study. Thanks again for your help. I was just reading through this thread seems to have a ron of interesting tools https://xdaforums.com/t/tools-zips-...nds-multiple-devices-platforms.2239421/unread Check it out .
[General Topics] Viva La Android R.I.P.:
Indeed. @osm0sis is one of the most accomplished and innovative developers here on XDA. Many of his tools and mods are the cornerstones of modern custom Android projects. It's good you happened upon that thread. A great resource for learning some essential Android knowledge.

In any event, I'll post some links for Treble GSI ROMs and how to install them. No worries, if you foul up, the firmware restoration guide will always get you bank up and going again.

Project Treble

The Android 8.0 release includes Project Treble, a major re-architect of the Android OS framework designed to make it easier, faster, and less costly for manufacturers to update devices to a new version of Android. Treble is for all new devices launching with Android 8.0 and beyond.

xdaforums.com

This forum covers virtually all aspects of Project Treble and its application.
[General Topics] Viva La Android R.I.P.:
UPDATE: February 9, 2023: I have just received the latest firmware builds for the Gen 1 and Gen 2 models of the Scepter 8 tablet from the software developers at Hot Pepper Mobile. I will post links in the downloads section as soon as I am able to upload the files to my cloud hosting service, so keep watch for the latest updates.
[General Topics] Viva La Android R.I.P.:
The latest firmware images are live for the Gen 1 & Gen 2 models in the downloads section. Even the older Gen 1 with Android 11 (Go Edition) got updated builds. The MD variant was updated from v06 to v11, while the CF variant got an incremental update from v09 to v13. Those with the CF variant of Gen 2 have an.updated build of November 26, 2022.
[General Topics] JovialQuestion:
I just wanted to let you know I'm still around Viva. 😂. Just wanted to let you know every GSI I have tried without any Gapps works and boots. However with any Gapps at all they tend to fail. Or are to large. So if you want a GSI install try the vanilla version of it and it will boot. With no custom recovery I haven't found a way to flash a gapps.zip to it. Even with Magisk and Magic-Flash installed you cannot flash the Gapps within android. I wonder if adb can be activated within recovery by modification of the stock img. Just not having any luck on the gsi's with Gapps but this is the only one I've found that will run smoothly and actually makes it a little faster than the stock "In My Opinion" that is.

system-squeak-arm32_binder64-ab-vanilla.img.xz

https://github.com/phhusson/treble_experimentations/releases/download/v416/system-squeak-arm32_binder64-ab-vanilla.img.xz
[General Topics] Viva La Android R.I.P.:
@JovialQuestion, good to hear from you friend. There are a few more firmware builds on the thread now. Update your build version if you want more recent security patches. Good to see you back.
[General Topics] rootmeb100:
Viva I'm having trouble with my tablet going blank at the qlink splash screen. It is booting up and is rooted according to "adb shell mount" command. After a lot of back and forth getting to get the right firmware I'm stuck. My tablet shows it has the a133 chip according to "adb shell getprop" with 16 gigs of ram? I was under the assumption that the second Gen was 32 gigs? Is this possible? What do you need that I can provide through adb shell or fastboot to know what my problem js? Also m u s/n number shows CF at the beginning.
[General Topics] Viva La Android R.I.P.:
The Gen 1 has an Allwinner-A100, 1 GB RAM, 16 GB internal storage, and ships with Android 11 (Go Edition).

The Gen 2 has an Allwinner-A133,:2 GB RAM, 16 GB internal storage and ships with Android 12 (Go Edition).

So, both variants have only 16 GB internal storage.

Can you post a photo of the manufacturer's label on the rear housing of your tablet? That will definitively identify your model & variant. I'll work with you to get the black screen issue resolved.
[General Topics] rootmeb100:
No sir the sticker isn't legable
[General Topics] rootmeb100:
No sir sticker isn't legable.
[General Topics] Viva La Android R.I.P.:
No problem. Go to device Settings, About tablet, and locate your SN. Also post a photo of the software info. (Android version, firmware build, kernel Version, etc.). Well you can't boot up can you?

If possible, boot to bootloader mode (legacy fastboot, and not FastbootD mode). The same mode you used to unlock bootloader & root). Connect your tablet to your PC, open a command window and execute:

fastboot getvar all

Post the info returned by the command window.
[General Topics] JovialQuestion:
fastboot getvar all doesn't work in primary bootloader fastboot only fastbootD on this device..
[General Topics] Viva La Android R.I.P.:
@bencinilife I never heard anything back from you. Did you have any luck?
[General Topics] bencinilife:
Sorry was having browser technical difficulties lol

@bencinilife I never heard anything back from you. Did you have any luc

Er
[General Topics] JovialQuestion:
Are you in fastbootD fastboot getvar all only works in fastbootD not the green android guy screen
[General Topics] JovialQuestion:
I always flash vbmeta with fastboot flash --disable-verity --disable-verification vbmeta /path/2/vbmeta
[General Topics] bencinilife:
Com

Comes up with vbmetra command unknown
[General Topics] JovialQuestion:
Fastboot flash vbmeta --disable-verity --disable-verification
[General Topics] bencinilife:
I have my directory for images in internal storage fastboot flash --disable-verity --disable-verification vbmeta /internal/vbmeta.img even used emulated/vbmeta ?
[General Topics] JovialQuestion:
what system are you using to connect to your device. Windows? Linux? Otg cable? You need to have the vbmeta.img from the correct firmware. Are you able to enter recovery? With fastboot reboot-recovery are you able to get to fastbootD with fastboot reboot-fastboot ? In case I've missed the primary issue your trying to fix. What exactly is going on in as much detail as possible. Were you able to flash the device with the threads instructions already?
[General Topics] JovialQuestion:
The screen saying it cannot be checked is just the normal screen when bootloader is unlocked. I wouldn't relock it. You don't need to press power. However I need to know if you can get to recovery or fastbootD as it will tell me if your boot img is working. So please let me know if your able to. As I started iny prior post. If it's able to boot then we can focus on system being the culprit instead of boot img I just need more information. The bootloader screen is just a pause in the boot and without pushing any button it will boot in 5 seconds after the screen pops up
[General Topics] bencinilife:
It won't let me relock it unless I enable verify?
[General Topics] JovialQuestion:
You don't relock the device. Keep it unlocked. You will destroy the device if you lock it again without full stock working. I need more information as in the start of the issue to the end. You are not answering the questions I asked so I have no way to diagnose a device I cannot see without information to help. All I can advise without this information is to follow the instructions listed on this post to fully restore the device
[General Topics] JovialQuestion:
Is it able to boot with the non patched boot image? Some version of Magisk fail to boot on this device..
[General Topics] JovialQuestion:
Also does it boot into recovery mode from bootloader? I asked earlier and I did not see an answer
[General Topics] JovialQuestion:
You may need to wipe user data if you did not factory reset the device. Fastboot -w should erase userdata but I prefer doing t through recovery not fastboot as sometimes I've noticed it doesn't actually wipe data. An encryption error could be at fault and a factory reset will fix that. Keep in mind on first boot. This device hangs awhile on the qlink logo before booting completely
[General Topics] Viva La Android R.I.P.:
This is the factory image your device needs. Is this the one you tried? https://www.dropbox.com/s/g4ds71xlmnecgfi/Scepter8_Tablet_v01_20220711.rar?dl=0

Yes, you'll get errors trying to extract the firmware images unless you are using special extraction tools. Typical archive extractors won't work. ImgRePacker is an excellent tool for the job. Available here on XDA, too.

To restore your device, use the above firmware image and PhoenixSuit, which is perhaps the most intuitive flash tool of all of them. You don't need a working fastboot or recovery mode. The tool, like the others, will flash from a powered off state.

I may have misunderstood your meaning on errors regarding "images" within the ,"factory" (presumably the factory firmware). Let me know.
[General Topics] JovialQuestion:
I believe the errors were regarding extraction of the .img file in the link. If you don't use the mention tool to extract the img to get the .fex format image files to flash. There will be an error. So use the provided tool to extract the .img file in the link he provided
[General Topics] bencinilife:
No that one doesn't match my serial number it starts with MD
[General Topics] SamuEDL:
*Delete*
[General Topics] Viva La Android R.I.P.:
The firmware image I linked above is for the Gen 2, MD variant. I have the MD variant, too.
[General Topics] bencinilife:
That's where it stays
[General Topics] Viva La Android R.I.P.:
Your tablet is not being recognized. That's the issue. There are two recognition phases. The first one -- if your tablet is able to boot into the Android OS -- is the preliminary recognition phase via ADB Debugging mode. This is where the flash tool displays some device info in the interface while awaiting firmware image loading by the user. The flash tool will boot your device into FEL flash mode to install the firmware. However, if your device is unable to boot or otherwise bricked, the flash tool will rely upon FEL mode only to flash the firmware. Device recognition is crucial for FEL mode lest, as in your case, firmware flashing cannot begin. As you probably know, FEL mode is an Allwinner emergency firmware flashing protocol based on the Boot ROM (BROM) implementation. It is a powered off state, of course. By the photos you have posted, this is your issue -- your device is not being recognized in FEL mode, thus the firmware flashing process cannot commence. I want you to try this:​

Using PhoenixSuit again, load the firmware image to the tool as you previously done. Ensure your tablet is fully powered off. Press and hold the power key for up to ten seconds to ensure a powered off state;​

Plug one end of your data syncing cable into your PC or laptop. Do not connect the other end to your tablet yet;​

When the firmware image is loaded and you are ready to begin, press and hold volume down on your tablet. Without releasing volume down, plug the micro USB end of the data syncing cable into your tablet. While still continuing to hold volume down, press and release the power button, and continue doing so at one-second intervals, up to ten times.​

This will often force recognition of your device by the flash tool. If this works, you will be notified by PhoenixSuit that the flashing process has begun, as well as the percentage of completion in real time. At this point, don't do anything until PhoenixSuit indicates that flashing is complete. Then simply reboot your tablet.​

Also, because I hate to assume, I must ask if you installed the Allwinner USB device drivers linked in the firmware restoration guide?
[General Topics] Viva La Android R.I.P.:
Okay @bencinilife, have you previously installed the Allwinner USB device drivers?
[General Topics] bencinilife:
Yes sir
[General Topics] Viva La Android R.I.P.:
Ok are you using Windows?
[General Topics] Viva La Android R.I.P.:
Ok good. Thanks for your thoroughness. So now, while keeping your device connected as though you are waiting for firmware flashing to begin (per the screenshot you posted), right click your Windows Start icon and select Device Manager. Now locate your tablet on the list. I'm needing to know how Windows is recognizing your tablet in the powered off FEL state. You can post a screenshot of the list.
[General Topics] Viva La Android R.I.P.:
Can you post a photo?
[General Topics] bencinilife:
I will post it here again
[General Topics] Viva La Android R.I.P.:
It didn't show up the first time on my end. Thanks. Okay this is quite bizarre. Your tablet is showing up exactly how it is supposed to in FEL mode. The good news is, this is likely something very simple. I need to ask you the obvious. Have you changed USB ports and have you tried other data syncing cables?
[General Topics] Viva La Android R.I.P.:
Ok so I know you've used PhoenixCard and PhoenixSuit. Have you also tried LiveSuit and PhoenixUSB Pro?