thank you so much!

thank you so much!
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.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?
Yes. And it will not run in at all.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.
I'll research your issue via the official Allwinnwer chipset release docs and see what I can find out.
Can you send the a100 cf chipset firmware and patched image to a fellow tenneseean?? Chattanooga here.
The firmware for the Gen 1 should be working on the links. I'll post you a patched boot image file shortly.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.
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.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
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 sirWell, 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.
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 ownI've got a completely different build number. Or am I missing something? Can someone pls tell me which firmware I should Use.
View attachment 5829743
View attachment 5829169
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.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
Thx. Flashed the modified boot and it won't start now so thx for re uploading the firm wars filesFor any members needing Scepter 8 firmware images, I will be fixing all links tonight for all builds.
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.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.
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.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.
Hey there my friend. I am seeming to be having issues trying to installWhat links are you referring to? All firmware links are working. Also the v6 and v9 firmware packages are for two different variants of the Scepter 8.
Okay I think I know what links you are referring to. Not the main firmware links on the first page, but some links within the thread which were extracted firmware packages (containing super.img, boot.img, bootloader.img, etc.). And yes you are correct that those links are probably no longer valid. However, if you are needing an extracted firmware I can help. What package are you needing extracted?
Me again lol having some issues setting up the scepter to install lineages os. The patched boot img I've patched through Magisk flashes great but then only loads to qlink image and that's it. I have to reflash with original img to get it back going. What am I doing wrong ?There are actually 4 variants: two variants of the Gen 1 model; and 2 variants of the Gen 2 model. But, both Gen 1 variants have the Allwinner-A100. Some CPU identifier apps may falsely detect the A100 as an A133. The reason for this is due to A133 notations in /system/bulld.prop and /vendor/build.prop. For all intents and purposes, the A100 and A133 are fully compatible with one another in terms of firmware and software support. It would appear that the device maker originally intended to use the A133 in the Gen 1, but for whatever reason - perhaps cost efficiency - opted for the A100.
But, to ascertain the identity of your chipset with 100% certainty, you may remove your tablet's back cover with ease. Use a guitar pick or edging tool and the back cover snaps off without screws or adhesive. Embossed on your chipset should be the nomenclature A100 in a white font.
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.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
Thank you for uploading them =)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 .
Lol. I am not a windows user. So I honestly have no idea. It's a mini acer laptop that I keep in a drawer lmaoim going to attempt this now.
also Windows 7 32 bit? what country do you live?
i have 4 laptops, perhaps i can ship you one of them