Can you send the a100 cf chipset firmware and patched image to a fellow tenneseean?? Chattanooga here.
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.
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot reboot
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 .
No problem. I changed cloud hosting services and the transition took longer than expected.
You are correct and thank you for those images. I didn't know about an image extractor thanks for the tip@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.
Next, you need to disable AVB/dm-verity using the vbmeta.img I linked above with this command:Code:fastboot flash boot_a boot.img fastboot flash boot_b boot.img
Then,Code:fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
Code:fastboot reboot
This is the tool I use
Build: Scepter8_Tablet_v01_20230526
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 .