Exactly. This is not about compulsory or optional update: it showed on our Windows Update and we installed accordingly.
I think the point is that we should find the proper files for our device on an dedicated page on the official site and not rely on posts where some user generously collects and shares their driver back up or something else.
This is a really good device with a fair prize: it is sad to not use it at its full potential.
Thatās all confusing! The only downside I have with this BIOS upgrade is the boot screen with Chinese text, a cosmetic problem so far. I was scared when I read the forum and found that several users were severely prejudicated by this upgrade.
Hi harlleysathler,
I was able to reinstall some drivers (mixing some older ones found on the net, some from different sources for other chuwi products) and recovered some sound options like before, but still no sound and a strange behavior from one driverā¦ could you please do only two more screenshots from your device manager please to be sure to have all the same, that woud be so great!
I would need:
A big thanks in advance for your precious help!
Hi, @Pirhana-A,
I canāt find anything related to Audio Process Obeject thoughā¦
Regarding to my stylus problem, does anybody know what device is the controller regarding to the digitizer?
[EDIT] Nevermind about the digitizer controller. I just solved the problem in the pen itself.
Having also installed the G8320 firmware update from within Windows 11, I also fell foul of audio issues whereby Device Manager showed new audio hardware that never existed previously. Furthermore, having successfully installed the drivers for the new hardware, there was no sound - not surprising since the actual hardware does not exist. After installing the drivers, Device Manager complained about missing drivers for ACPI.
I pointed Chuwi support to this thread but they deny there is a problem and I also told them that there appears to be a serious issue with their database where certain Hi10x serial numbers are being linked to the incorrect firmware updates. This, of course, has cascaded itself onto the Windows 11 update with disastrous consequences.
Eventually, I asked Chuwi support and asked for the original firmware, which I subsequently downloaded in good faith and installed. The device is now non responsive, except for the red LED at the top being permanently on. Unequivocally, this is completely the fault of Chuwi and I have asked them send me a replacement Hi10x. Since this request, there has been no further reply to my emails. I am not sure if legal action will get me anywhere but I am prepared to take other action that will hurt them.
It is not the first time that Chinese tech manufacturers have taken a lackadaisical approach to firmware updates. Both Teclast and Chuwi have been guilty of this back in 2016, resulting in non-responsive devices. I would have thought they would have learnt from their lessons but no, they continue to take these destructive actions seemingly without a single care or thought for the consequences and seemingly without any testing.
Although Chuwi did send me the download link for the firmware that completely rendered my Hi10x unresponsive, I am not going to post the link here, so please donāt ask - I donāt want some numbskull to download it and blame me for their actions (as has been the case in other forums I have encountered).
Iāve learnt valuable lessons from owning Chuwi and Teclast tablets and that is I will now avoid all these budget Chinese brands. Yes, I will pay three times the amount for a Lenovo Yoga, but at least I know they do take more care in how they test and release updates!
i spent 3x for a lenovo duet 3i.
didnāt think service is better.
they got their own problems.
it wont help you bring back your 3GB ram and the sound card, sorry.
WTH you got a bricked device,
oh my god.
I feel very very sorry for you.
Go get them, i support you!
Hi
Me too, I have the same problem with Hi10X and with Win10 optional update, shown as G8320 Firmware Update.
After installing the Firmware update,
1. at boot, just after Chuwi boot logo screen, it appears another screen with a message in chinese which Iām not able to decipher.
2. sound drivers went missing
Chuwi Hi10 X
Intel(R) Celeron(R) N4120 CPU @ 1.10GHz 1.10 GHz
But at least Lenovo do not release firmware updates without testing. Who in the right frame of mind would do such a thing? Only a complete moron would. By the way, itās not just audio and missing 3GB RAM that has weakened my Hi10x. The whole machine is lifeless and Chuwi donāt want to know. Theyāve done this in the past and theyāve done it again! Darwin Award for the most moronic action goes to Chuwi for pushing a firmware update that is incompatible with certain models - idiots, the whole lof of them!
@harlleysathler How crazy it would be if weād buy you this USB BIOS programmer and ask you open your tablet like this, read your working BIOS like this using the USB BIOS programmer connected to another computer and share the bin file with us, the unfortunate plebs who got their BIOS corrupted?
I know itās a lot, Iām only asking if you have the means, time, etc to do it or the confidence to do it yourself. If not, itās totally understandable.
Hi, @chrisc, it could be done, but I donāt think we need to go this way. The Hi10X firmware is an AMI Aptio, for which AMI distributes utilities to dump and write BIOS images. I will try to dump my firmware images with these utilities and report back.
However, I downloaded the same update as yours, but my tablet didnāt get screwed. Is it possible that even if I dump the SPI memory content as the videos you linked and you write it to your Hi10X, the problem can persist?
[EDIT] I found Aptio Utilities on the AMI website. Does anybody know if we have Aptio V or Aptio 4?
told you people send to the chinese youtuber to repair.
he is qualified, you could read his youtubes first.
he have tools to read/write bios already, why re-invent the wheel?
if he survied, heās using the intel sound chip variant.
check my old posts.
i cant help if you people are that level.
you better state what variant you are using first.
those who suck are the Hi10X + N4120 ā ESS386 sound chip.
anyone NOT with this combination will survive.
itās not luck, itās science, itās technology, itās facts.
@harlleysathler AMI Aptio 4 fails to create the dump, and AMI Aptio V works, but the tool does not show some of the information about the firmware, so not sure if the created image is complete/valid.
However, when the image is scanned with UBU tool, it displays the correct version that is currently flashed, so the created image file contains at least some parts correctly.
Scanning BIOS file afuwin.rom.
Please wait...
Manufacturer - To be filled by O.E.M.
Model -To be filled by O.E.M.
BIOS release - V0.6.0_P4S0M2E0F0L8B0T6P0G48A1U0D701 05/29/2023
BIOS platform - AMI Aptio 5
You can try create a BIOS dump with AMI Aptio V, and one of us can try flash it after we have acquired the USB BIOS programmer for backup, in case it bricks.
I just tried both and, strangely, I couldnāt run any of them: Version 4 closes as soon as I run and version V causes me a BSoD. Is there anything I must do before running the utility?
No, just run Aptio_V_AMI_Firmware_Update_Utility.zip\afu\afuwin\64\AfuWin64.zip\AfuWin64\AFUWINGUIx64.EXE (unzipped along with other files, donāt run it from within the zip) and click save.
Yeah, this was what I did. As soon as I grant admin privileges to AFUWINGUIx64.EXE, I get a BSoD. Today, at the end of the day, I will try to generate a bootable FreeDOS thumb drive with AFUDOS.EXE to try again to dump the firmware.