yashsingh1/xdaforums huggingface dataset:
[General Topics] Viva La Android R.I.P.:
So @bencinilife here is what I'm going to be doing for you. I'll make you a fastboot package for flashing firmware and restoring your tablet. Your tablet is recognized in fastboot mode, correct?
[General Topics] Viva La Android R.I.P.:
So you did make some progress with PhoenixCard? Please elaborate a little on the issue witt booting after flashing with PhoenixCard
[General Topics] Viva La Android R.I.P.:
Okay try the Volume key, plug in USB cord, and tap power repeatedly. The steps you tried for PhoenixSuit. You're very close to this working. It is bound to be a simple issue that you and I both have overlooked.
[General Topics] Viva La Android R.I.P.:
Ok try the same steps with LiveSuit
[General Topics] bencinilife:
Screen shot
[General Topics] bencinilife:
Initialization fails (200) second time I tried is says initialization fails (513)
[General Topics] Viva La Android R.I.P.:
Okay. With your device in FEL state once again, open your Windows Device Manager, locate the entry for your tablet, right click the device and select UNINSTALL. Do not tick the box for uninstalling the drivers, however. Then reboot your PC, at which time Windows will reconfigure these parameters. Once rebooted, try the flagg tools again.
[General Topics] Viva La Android R.I.P.:
Ok @bencinilife I am home now. I have the same model and variant as you. I'm going to flash my device after a fresh Windows 11 install with PhoenixUSB Pro. I'll try to resolve your issue. I will be a little while with everything because I'm extracting and converting a factory image for another member, but I'll get back with you later tonight.
[General Topics] bencinilife:
Sounds great
[General Topics] JovialQuestion:
I just want to point out. When helping another user. When the device have been in bootloader too long the battery won't charge and it stays on but when trying to load the OS the boot fails and the device will if plugged in reboot like a boot loop. Also the PC software that detected the device also caused it to send a reboot command automatically to it once adb is active during boot. So after your PC flashed the software did you unplug it from the PC?
[General Topics] mdtryme:
i just used it Use the mega app

Cool. I thought so but if i would not have asked....do u have a recomender flasher to use for this. Or can it be done strictly with fastboot??
[General Topics] Viva La Android R.I.P.:
The fastboot flashing script restores the stock firmware in its entirely. I tested it on my own device before finishing the guide.
[General Topics] Viva La Android R.I.P.:
Has anybody tried the fastboot method yet? Seemed to work great on my device but I'd like to get input from other members, good or bad. Is there anything I could improve upon or change? My goal with this method was to alleviate the device recognition issues often experienced by members with Windows.

Let me know.
[General Topics] SunSlide:
Tried it today. Copied the script to a file in the unzip location and put a she bang at the top. Worked great in fastbootd to restore the original firmware and unbrick a boot loop into recovery. What did not work was the last two commands. I had to reboot into the bootloader where fast boot also works and run those command by them selfs. Now I can't flash a GSI to my system partition anymore. I shoulda just left it alone when it was working how I wanted lol.
[General Topics] Viva La Android R.I.P.:
If you're getting an error when flashing a GSI, try this while in FASTBOOTD mode.

fastboot delete-logical-partition product_a
fastboot delete-logical-partition product_b

The /product partitions are not needed when running a GSI. Deleting both /product slots frees up available space in the dynamic /super partition, and should make room for a GSI.image. But remember, this cannot be performed in legacy fastboot mode. You'll need to boot into FASTBOOTD mode by executing:

adb reboot fastboot

Or, just select the option for entering fastboot mode from stock recovery.
[General Topics] Viva La Android R.I.P.:
If you're getting an error when flashing a GSI, try this while in FASTBOOTD mode.

fastboot delete-logical-partition product_a
fastboot delete-logical-partition product_b
[General Topics] SunSlide:
Yeah, deleting partition product a is what originally started my issues. Didnt try both but dont see that helping at the momment. So long story short, i had linageos18 installed and working because it was the only one that installed no problem and booted. I then wanted to see if v17 or 19 would run better so i ended up deleting product_a(instructed by the tutorial i was goin through from asop) and flashed system_a but that ended in a boot loop to recovery. After trying to reflash v18 with no progress i used your the script to recover the stock firmware. Now from fastbootd (fastboot reboot fastboot) when i try to flash the system partition it's saying it cant write to the partition table when it does the resize on it. When i try from the bootloader,(fastboot reboot bootloader, fastboot flash system rom.img) it says it cant find the system partition but i can wipe the system partition. Something wierd is that i cant seem to flash roms from boot loader mode but cant erase partitions(fastboot erase part-name) from fastbootd mode. In other words, i have to flash in fastbootd and then reboot to boot loader to wipe partitions. Ive tried flashing the modified boot a time or two but that didnt help. I havnt had the time, but i was going todo the full restore again and root it from the top to get back to where i was the first time i installed lineage18.... Unless you or anyone else may have better ideas? I'd like to just know what im doing here.

Also, I was thinking about trying to port twrp to this as a learning exsperiance, would reflashing the stock rom fix anything i mess up? I noticed it reflashes the boot partitions and was thinking i could use it as a fail safe.

Edit: i do fully understand i can brick the device but this particular unit is 'desposible' enough im willing to take the chance to learn.
[General Topics] Viva La Android R.I.P.:
Ok thanks for expounding on the specifics. I'm fairly certain you've corrupted the /super partition or perhaps inadvertently resized it while in fastboot mode. The good news is,.repairing the partition index is not complicated. You'll need to perform the v9 firmware installation using one of three tools:

• PhoenixUSB Pro; or

•PhoenixSuit; or

• LiveSuit

Installing the firmware using the fastboot script , unfortunately, does not reconfigure the partition index to its factory default. I outlined instructions for restoring firmware using PhoenixUSB Pro; however, the setup is for Windows. If you are running Linux, LiveSuit will do nicely. Once you restore the firmware using LiveSuit, your issue will be resolved. All three tools I listed were developed by Allwinner. I'll get you a link and instructions for using it now.

• LiveSuit Downloads - All Versions

• How to Flash Firmware Using LiveSuit

If you have a Windows PC or laptop, simply follow my instructions in the PhoenixUSB Pro section.
[General Topics] SunSlide:
Yeah, i dunno Viva. I have a dual boot system so that wasnt an issue but i couldnt get phoenix or livesuite to reconize it. I could get it to the point where it poped up with the message box that said connecting and would hang until i un plugged the device from my laptop. Livesuite was a simular exsperiance on windows. I tried to install live suite on several different linux boxes and a vmmachine and just couldnt get it to install. I got it where it boots and is rooted so that suites my purposes. I think im gonna give up on the gsi for now though. After hours of reading,rebooting, and tapping the power button, i still cant modify the partitions. Is there a particular linux that livesuite works on? I tried manjaro, arco, ubuntu server and debian. It just said no to the arch based distos and complained about the dkms modules in the otger two.

Anyway, thanks for your help!
[General Topics] Viva La Android R.I.P.:
Yeah, device recognition has been an issue for many users. The Allwinner based tools like PhoenixUSB Pro flash the device while in BROM mode, which is the hardware embedded bootloader. Since you have Windows and Linux, use my PhoenixUSB Pro instructions in this thread. I have included a step-by-step section titled "Installing USB Device Drivers" in the guide, which you should give close attention. Start from scratch and follow all steps to the letter.
[General Topics] SunSlide:
I might go ahead and give it another go tonight when i get home. Is there a difference in clickin the power button 3 times like you say and 10 times like the live suite says? Also, do you know how to modify the permissions or modify the partitions them selfs? Other then with the fastboot commands create/delete/resize_logical_partition? Ive scoured the net lookin for a way.
[General Topics] Viva La Android R.I.P.:
No real difference. It can be recognized in as few as 3 to 4 clicks, or it can take as many as 8 to 10.

There are Linux based tools like parted that can be used to repartition flash memory. But you shouldn't need anything like that here. The Scepter 8 uses the Dynamic partition scheme, as you know. In addition, it uses the A/B seamless update partition scheme. Your issue comes down to needing to revert the partition index to the factory default. The only practical way of doing that is to flash a stock firmware using one of the three Allwinner based tools. I.corrupted my tablet too when first tinkering around with modding, rooting it and such. such. Once you flash the firmware with an official tool, it will go back to normal. Fortunately, Allwinner tablets are almost impossible to hard brick because they have hardware embedded bootloader code. The Allwinner based flashing tools communicate directly with that component when restoring firmware.

I do have a tip for you: whenever the flashing tool prompts you to begin with the hardware key combo and connecting the USB, your device has been booted into BROM mode. This is where you are having trouble with recognition. If, after following the instructions, your tablet still isn't recognized, keep it connected and right click on the Windows Start button. Open Device Manager and locate your tablet in the list. Let me know how Device Manager is listing your tablet. I can troubleshoot it and maybe resolve this issue if I have that info.
[General Topics] SunSlide:
Ill try when i get home but that wont be for awhile so ill update ya overnight. Thank you for that explination. Ill have to read up on this brom mode a little bit. What should i exspect from the tablet when im in this mode? Ill double check the drivers and what not. I feel like im getting there because windows makes the little doot-da-doo after i click the power 5 times or so. That dont mean my drivers are right though. What driver should appear when im in that mode?
[General Topics] Viva La Android R.I.P.:
The tablet should closely resemble a hard bricked device while in BROM mode: blank screen, unresponsive, hardware key actions

seemingly ineffective. This is why it's sometimes difficult to get a device out of BROM mode.

The driver should be a composite bootloader interface type. I have no doubt that the tool is properly booting your tablet into BROM mode; I think the sole issue is the driver. I can walk you through manually updating the driver while in BROM mode.
[General Topics] SunSlide:
So I screenshotted what I'm looking at and attached it for you. You can see the files I downloaded, the driver name , and Phoenix actively i. This is a brand new fresh windows install on a desktop computer that I have but the drivers where the same on my laptop, includeing the messed up one. For some reason one has failed? I included the properties dialogs.

I can varify that the device is getting into a flashing mode through lsusb in linux. I can see the driver change when I'm in and out of flashing mode. It says : Allwinner Technology sunxi Soc OTG connector in FEL/flashing mode. It will stay like that untill I get it to reboot and then list a google driver.
[General Topics] Viva La Android R.I.P.:
Okay, good info here. I'm going to look things over and outline some steps to get the correct driver in place.
[General Topics] Viva La Android R.I.P.:
@SunSlide, I realize you've probably already covered your bases on troubleshooting this issue, but just so I'm not making any assumptions, I'd like to clarify some things.

When launching PhoenixUSB Pro on your PC, are you first clicking on the IMAGE option and then selecting the v9 firmware image saved on your PC? Next, are you selecting START and waiting on the green prompt before connecting your tablet to your PC via a data sync cable?
[General Topics] SunSlide:
Yes, just like the instructions. From a clean install I installed the 15-second drivers and then phoenixusb. I open up phoenix and click the img button. Open file opens up and I navigate to the img location and select it. Press the start button and it turns from red x to green check mark. At this point if i havn't already I'll make sure that the tablet is properly powered off. IE: hold the power button to insuire it powers down from preveious attempt, turn it back on so it loads to the boot screen and then hold the power button till it shuts off. Or if its on the recovery screen I just hold the power button till it shuts off. I like to wait a few seconds to make sure its fully shutdown but try todo this step early on to give it more time. Hold the vol down button and plug in the usb cable, then press the power button several times(around 5-7 works nicely). The green circle turns to red x like its supposed to and nothing else happens. I've left it to sit there for up to 10 minutes. In your post it says it takes about 4 minutes so I don't wait too long. If I try to push the stop button while it's hooked up it only pops open a dialog that says device connecting. It wont let me close the program until I unhook the device(red turns to green so program not frozen) and push stop. At this point I can unplug it from my desktop and plug it into my laptop running linux and verify that it's in flashing mode.

I did manage to get livesuite working on linux but still didn't help. It was complaining that the img file was corrupted. I did a fresh download of all the components when I did the windows install. I tried opening another img file from the linux flash zip but it also said it was corupted so I dunno. I tried to run the linux flash script again and it ended in a recovery bootloop. To be honest I've kinda just given up on it for the momment. Ill keep trying if you have other ideas but I have a handful of other projects that this tied into along with other android devices that can take it's place and was going to wait to play with it more when I have time to get the sunxi tool suite working.
[General Topics] Viva La Android R.I.P.:
Hmmmmm. I'm going to check the firmware with md5 from the link I posted in the instructions. The issue could very possibly be a corrupt firmware image. Thanks for detailing everything. I know how frustrating this can be. I'll let you know later this evening on the integrity of the firmware. I have a master copy if I need to upload it.
[General Topics] Viva La Android R.I.P.:
@SunSlide, to ascertain that the firmware on my cloud storage isn't corrupted, I checked my master copy and re-uploaded it. I ran md5 to check the integrity and all looks good. Here is a link. I am also replacing the link in the instructions.

File on MEGA

mega.nz
[General Topics] JovialQuestion:
Twrp img? There is no twrp img I am aware on that works. To flash with fastboot you need to download the factory img that was provided then extract the .img file with the correct tool once you have that extract and they appear as .fex files. Such as boot.fex vendor_boot.fex super.fex and so on. If you extract and it looks like 10.boot.img it's not extracted correctly. You only need to flash in fastbootD super.fex as fastboot flash super /path/to/super.fex and in primary bootloader/download (the green Android logo) fastboot flash boot/path/to/boot.fex if you changed your vbmeta then flash the vbmeta.fex from this bootloader as fastboot flash vbmet /path/to/vbmeta.fex then fastboot continue and it should boot. Do not try to flash a patched boot img at this point try to get factory to load and setup the device. Leave the bootloader unlocked. I've completed this using Fedora and Bugjaeger with a OTG cable. Windows was tricky with driver conflicts
[General Topics] Viva La Android R.I.P.:
We have TWRP compiled for both models, from source. The bootloader on both models will need to be modified to install it. Since the Scepter 8 has no /recovery partition, TWRP has to be installed to the /boot partition. To install it, the image must first be booted via fastboot, then flashed by way of the TWRP GUI. However, at this time, our stock bootloader does not permit booting the image initially. I'm in the works of getting an engineer bootloader from the manufacturer that will enable TWRP to be installed.
[General Topics] vtails:
I haven't been here for a decade so few ? First I can't get to first page so I can read what's been happening and if this Scepter tab is going to be useful if I TRY and root it ! As of now this tab has been restored 20 or more times because it doesn't work hardly I first tryed to get my money back for it$10 dollars, but I'll get back to first problem - I can't get to frist page to inform myself of issues a screen keeps dropping down with a post from scarlet letter think that's the name and the page is sent to 9 Why is this I'm trying to read on my iPad now can't seem to navigate this forum, if someone might have idea of what I'm doing wrong . Second question is rooting this tablet does it run with out the problems it seems to have sorry to ask Stupid ? but after trying to read here for awhile couple different times it's getting frustrating a bit. Somewhere I saw where files were down for a while all I can read is broken bits of this forum I'll stop Thanks folks
[General Topics] Viva La Android R.I.P.:
You're certainly not the only member who has experienced difficulty navigating on XDA since the platform's migration over to XenForo from vBulletin in late 2020.

It is simpler to navigate if you are using the official XDA app. The first thing you need to do is tap your account icon, which is the third icon to the right in the lower navigation bar. Then select Settings and disable the Thread Preview option. Now, when you open a thread, by default you will be viewing the full version versus the preview version. Next, go to the thread you want to begin on Page 1. At the bottom of each thread page, you will see a navigation toggle that looks like this:

​

This will reflect the current page of the thread you are currently on. To go back one page, tap the blue Prev box. To go all the way back to Page 1, tap the double arrows to the left of the Prev box.

If you've been gone 10 years, navigating XDA will take some practice for sure. Welcome back.

Insofar as your inquiries on the Scepter 8, this thread would be a good place to begin. Scepter 8 General Info & Discussion
[General Topics] JovialQuestion:
You can also use the website via chrome if you open it in desktop mode. It's small text but you can zoom in and out. You can also use landscape mode just know the keyboard will cover most of it. On safari I'm not sure how to request desktop mode. And yes the XDA app works much better..
[General Topics] JovialQuestion:
@Viva La Android wouldn't it be possible to flash slot B with the twrp.img. You can update the boot slot to B with this bootloader with fastboot --set-active=b and once you boot slot B it is empty and the device boots back to slot A after a reboot. Just curious. I used to do this with the pixel XL as the Device didn't support it at the time. It also has the A/B boot only both boot slots have the ability to boot. This tablet will only boot slot A when you switch to B even with the correct boot IMG it still fails and switches back to A same as what would happen flashing a A/B ota
[General Topics] Viva La Android R.I.P.:
In theory, that's a plausible idea. However, when there is no /recovery partition, the TWRP image cannot be flashed to either /boot slot via fastboot. You must first

fastboot boot twrp.img

Once TWRP has been booted, it must then be installed using the TWRP user interface. This is just a peculiarity of installing TWRP to the boot-ramdisk versus recovery-ramdisk.

I will have a modified bootloader tomorrow that should permit TWRP to first be booted via fastboot mode.
[General Topics] vtails:
I've run into this issue of changing formats and it does cause some frustration ! And as i was looking for info on this tablet I unfortunately went to a russia site by accident and they wrecked my ipad so I'm trying to get it fixed and that also was part of the issue trying to navigate this site thought i had it but looks like a week of reading on how to fix!

I will see about deleting my post it was stupid and is all other the place i can't figure out what i asked after rereading it.

As for the tablet i have read few others post how they fixed it up and was working fine (WTF) i called Qlink and asked if they could help and first wanted it restored which i did it worked a bit better but still locked up and I'd have to reboot it but after so many times i just asked for the money which was n't going to happen then asked for another and that was a NO WAY so I put it away for few months then I saw this so why not and I have killed some S3 and S4's with the program you mentioned, I just hope that its not a waste of time,I thought if it just worked Chrome to surf then it be a win, Anyway Thank you for taking the time to respond I hope I didn't look like to much of an IDIOT and hopefully I can learn something !
[General Topics] vtails:
I forgot to mention that I have fairly sure a GEN 2 FCC ID AP15 and the Ser. is MD so I'm going to see if I kill it or make it better, Ill let everyone know cause if I can get it done then anybody should without any issue's!

But any advice is always appreciated
[General Topics] Viva La Android R.I.P.:
I have the same model as you. I can confirm that with root, a few tweaks, and some debloating, the overall performance boost is remarkable.
[General Topics] bencinilife:
Hahah risk it for the biscuit 🤣
[General Topics] vtails:
I was going though the settings and turned on devmode and looking at info there it has switch for bootloader to be unlocked , I have read the rooting guide completely yet but I did turn some of the options on and I'm guessing you should turn some of these on I'm guessing but should that option for opening bootloader should be on before trying to Root?

I'm sure when I read instructions it will tell what to turn on Thanks for the info. It'll take me few days to finish rooting this tablet hope there is recovery but if not not a big deal.
[General Topics] Viva La Android R.I.P.:
Yes the OEM Unlocking option must be toggled on prior to initiating the actual bootloader unlock sequence via fastboot mode. Yes, the instructions are clear and straightforward on both the bootloader unlocking and rooting procedures. However, if you encounter any issues, just comment on that thread and either myself or another member will help guide you.
[General Topics] bencinilife:
A twrp boot recovery would help alot hahah
[General Topics] Viva La Android R.I.P.:
Indeed it would. We actually have one. It's getting TWRP to install that's the issue.
[General Topics] mrdukes:
Relink please?
[General Topics] bencinilife:
Relink please
[General Topics] Viva La Android R.I.P.:
I don't have a link for those files. If you're needing them, I can extract the images from firmware, upload them and provide you a link.
[General Topics] mrdukes:
Please do. Would help a ton.
[General Topics] Viva La Android R.I.P.:
Which images do you need from the firmware package? Only super.img and boot.img? And please specify which model and variant you have.