Need flash BIOS but no Windows. Oher methods?

[Jonathan]

Do you have the correct BIOS for your tablet? Sounds like it should be possible to flash from UEFI shell.

A lot of people with the Teclast X98 Pro used to get this error trying to install 64bit Windows with a 32 bit UEFI BIOS. Someone posted a simple possible fix for this, I don’t know if anyone tried it.

What did you do to get this error?

DO NOT change any BIOS settings at this point, especially anything USB related (even if it looks harmless).

[OptoMan]

I think telcast tablets in question are slightly older — and only slightly related is that cube seems to like doing 64 bit efi at least now.  and it’s included shell is 64 bit, but the BIOS updates from cube come with a 32bit efi updater.  they don’t want to support this.  so, different shell, which seems it might require to be placed on EFI partition instead of just USB — or find a 64 bit flash updater, which I’m really not going to try.  when a company purchases bios code, they don’t have to release the exact same stuff that another company might, as in the flash update utility might not be the same anymore because it’s been sold and modified.

felix: saw your post in the other thread first in my notification so I put a reply there .. the windows bios update is the way to go.  it does do the same thing and it really is easier, especially since you already have the microhdmi cable — if you had killed windows, I’d still hook up the hdmi and install windows again to have windows and for bios upgrade.  in my experience, the display/digitizer only affects windows, android seems fine as can be.  random, but an interesting observation — differences between how windows learns of hardware and so android

 

[Jonathan]

OK, gettings Windows running sounds like a good plan then.

If that doesn’t pan out I’ll look at getting the OP hooked up with a 64 bit updater, if it’s a last resort before having to open the tablet it’s not going to matter that much. A file compare on the 32 bit versions would help determine if the update utility has been modified, generally Chinese manufacturers don’t even bother to change ID strings in the BIOS or even remove options that will brick the tablet so I doubt they’d modify the updater but you are correct that they might have 🙂

[OptoMan]

there’s actaully nothing wrong with using a windows updater and it is a user friendly wizard =) .. we could file compare all the 64 bit updaters that chinese tablet makers have released but we don’t have one from cube.  we could comp cube’s 32 to other’s but that’s not 100% either.  the 32 fpt tool that cube bios comes with is an intel tool and requires the txt file in there with flash chip specs .. so beware of the ami flash update tools that use ROMs instead of BINs.  that’s why people say ‘could use afu but it tends to break things’ .. uh ya

a modern and trustworthy 32 bit efi shell can be had, but what I’ve done so far I’ve not booted to one from udisk, but keeps falling back to on-system 64 bit shell.  seems to be the directory structure on the udisk is last for me to try — some BIOS (uefi really) will refuse to boot shell from udisk all together and want it on-device, so EFI partition.  I’m not going that far any time soon… my stuff’s not broken

I think I’m just saying, that because the 32 intel tool is there doesn’t mean finding a 64 bit version would necessarily work — would the bios accept a flash? I don’t think we know for sure, and really for 32 bit either. not sure who has time to find out, yet, waiting till it’s absolutely needed isn’t right either.  someone’s not going to like the idea that they need their win10 on there to flash bios, but I’m saying that’s a dumb mental-block hah =P

 

 

[felix]

Fixed It!! Thanks!

[Rino Adi Pratama]

felix wrote:

Fixed It!! Thanks!

how? can you tell the steps? since i got the same problem too

[OptoMan]

If you read back around there’s not a whole lot of posts in here, iWork8 — for the most part, if you flashed the wrong bios, your graphics and touch screen are messed up, right?

further, if you have the ACPI error, where that surely came from is a setting in your BIOS — under Advanced > System Component, “OS Image ID”.  manually set it to Windows 10.  windows will not boot unless it’s set to that .. if you can understand this, the main boot selector for android/windows will change that setting in the bios if you select what it’s not already at .. then the chosen operating system will read that from the bios and be satisfied.

so .. if graphics/touch screen broken, need micro-hdmi cable to see, and you might be okay touching the screen in different places, or might have to OTG a USB mouse to it .. fix acpi setting, boot to windows if it’s still there and flash bios.  if windows aint there, install it while using the hdmi/mouse! =)

 

[Author]

Posts