I make a bootable FreeDOS thumb drive but could not boot it as Hi10X apparently can’t boot in CSM mode. I also tried to use AFUEFI, but I also could note boot into the EFI prompt. At this point, I’m out of new ideas.
Do you or anyone else know how to enable CSM boot or EFI prompt?
I noted one difference in our screenshots: You’re using Windows 10 while I use Windows 11. I made a Windows to Go installation of Windows 10 on a memory card and was finally able to run AFUWIN. I successfully dumped my BIOS image: https://www.mediafire.com/file/p2bz7co7mfwb7qp/Hi10X_rom.zip/file
To be safe, I’ll buy an USB BIOS programmer, backup the current BIOS, and then try yours.
Hope I don’t mess up. I never done this before.
Thank you for your troubles.
Hi, it’s been quite a few weeks since my last message. @harlleysathler: I’ve just read about your work in dumping the BIOS. Really a generous action!
Unfortunately I made the stupid move to flash a BIOS file I have found on the Forum some time ago, but I corrupted the tablet. Led blinks one time, but screen is black and there is no sign of life. If I plug the AC charger the red led remains static but no sign of life at all…
I bought a CH341A programmer and, at this state, I decided to give a try to your file. Neoprogrammer detect the chip XM25QU64A [1.8V] by XMC manifacturer. I don’t know if this information can help.
I tried some minutes ago. Process goes well. But, still, red led blinks only one time while not plugged to AC charger and screen is black. I don’t know if I damaged some wire while opening the case. I seems all fine but I can’t be sure. At this moment, I don’t know what to try. I can’t be a reliable source about your firmware unfortunately.
I made a stupid move flashing a file I was not sure of its origin (i’m talking about the other file I’ve found here on the forum).
We can’t determine if your file isn’t working in my opinion. It can be that my problem relates to something else and not the bios flash itself. I don’t know.
Anyway, it seems that now there are variants with 8gb of RAM of this device. A lot of fragmentation!
I’ve managed to restore V0.5.0_P4S0M2E0F0L8B0T6P0G48A1U0D701 01/14/2021 BIOS on my tablet with a copy provided from support. Followed the instructions in the doc file, the BIOS flash went well (the EC flash failed though, but doesn’t matter, hex dump looks the same) and now it shows 6GB RAM.
I didn’t have to use CH341A programmer. I tried it with the 1.8V adapter, but it wasn’t detecting the chip and reading manually would always return 00. Maybe it works only out of the PCB, but I didn’t bother, I just risked it and flashed it without knowing if EEPROM programmer was going to work as a backup. Thankfully I didn’t need the backup .
Hi chrisc,
thats it!!! I had the same idea but the big question was: What is the right BIOS file?! You found it.After your post I took the risk and used your link file appropriate the description in the containing docx file. And what shell I say? … It works great for me! Now I have the 6 GB RAM again and the sound works as well!!!
Many, many thx to you, you saved my Hi10X.
What you did, I expected from Chuwi!!!
What should they do?:
Stop at once this dammed update for the Hi10X’s in Windows update to prevent more users from destroying their tablet/PC
Show all affected users how to flash the old firmware - what you did
Investigate the problem to find the reason - for this they have time because I can no see why we need this update now urgently.
For me, and I think for many others the problem should be solved … for the moment. The bad is that Chuwi leave the users out in the rain. And although I like my little Hi10X, my future will be w/o Chuwi.
I took a chance on this because I was going to sell this machine for parts if I could not get it fixed (I could have worked around the sound issue, but the 3 GB RAM was something I could not take. I got this machine to replace a 4 GB Windows tablet after all). And it worked! At first it gave me a bunch of unrecognized devices until I uninstalled the Realtek sound drivers completely and shut down, waited a few minutes, then booted the machine.
I still have one unrecognized device, named “System Firmware G8320 V06”, under the category “Firmware”. Did the same happen to you as well? If so what did you do? As it doesn’t seem to affect the performance of the machine, I am tempted to just hide it or disable it, but I am worried it might reinstall itself somehow (can firmware be reinstalled via the device manager? I never had such an issue before so I am not so sure).
Any advice on the matter would be appreciated.
Edit: changed “hide it” to “hide it or disable it”
UPDATE: For some insane reason, after rolling back the firmware, it reinstalls it upon restart. So every time I have to use the machine I have to reflash it. This is insane. I’m trying to look for answers on the net, but did anyone encounter this issue upo restart? and if so, how did you fix it?
I had exactly the same problem, flashing the BIOS bring my 6 Go back, but everytime it auto rolled back to the wrong Zhiwei 8320 V0.6 MicroFirmware with 3Go,
I solved it by manually desinstalling the MicroFirmware Zhiwei 0.6 in the windows devices manager with the “remove the driver file from my computer” option,
then restart and flashing the BIOS a last time and it never roll back again…
and now I have a “default” system MicroFirmware (no Zhiwei 8320 V0.6 anymore) in windows devices manager without any error.
But unfortunately I never got my sound back…
How did you guys manage to restore the speaker sound?
(Under Sound-Video-Game in devices manager I have the ESAuDriver installed and the devices is indicated to be started and working, but windows find no sound output available,)
do anybody has a link to the compatible Everest Semiconductor Driver pack for the ES2386 soundchip variant?
Thanks in advance for your help,
(and thank you very much Chrisc for your working BIOS!!)
This is how I fixed it. First, flash your BIOS again. Then once you boot into Windows, go to Device Manager. If you still see the Firmware, then go to your C drive, Windows folder, Firmware Subfolder. If there is a BIN file (BIN being the file suffix) delete said file. Then reboot Windows. Now, you’ll always have the Firmware showing up in device manager, but since it has nothing to update it from (that is why you had to delete that BIN file in the Firmware subfolder), it will not update the Firmware anymore. You’ll have a working machine and sound. I have been using my machine for a while now and it has not tried to update the firmware so far.
Well, to be clear, this issue affects the Hi10X that has the N4120 and 6GB. Just do what we did, contact support, indicate your model and serial number, and they will send you the proper BIOS file. Just keep in mind you may or may not have to manually the rogue BIOS file update from the Windows folder so it does not keep auto switching to the faulty BIOS.