Chuwi HI10 BIOS Update for x64

[fbrozovic]

Marcin Kruszyński wrote:

Mine Hi10 (first VC Lemon x32 batch) is not booting anymore and your SPI flashing seems like rescue. I’m new to this so can you write or PM some short tutorial how to flash Winbond using rPi? Can it be done using other PC or do i have to own SPI programmer? Thanks.

Alright, here goes:

You need a Raspberry Pi or a similar board with a 3.3V SPI interface and Linux. On the Pi, install Raspbian and enable SPI via raspi-config, after rebooting the device file /dev/spidev0.0 should be present.

Download flashrom and its prerequisites:

$ sudo apt-get update
$ sudo apt-get install libusb-dev libpci-dev
$ wget http://download.flashrom.org/releases/flashrom-0.9.8.tar.bz2
$ tar xf flashrom-0.9.8.tar.bz2
$ cd flashrom-0.9.8
$ make && sudo make install

Next, hook up the SPI flash to the RPi. Be very careful about shorting anything on the board, in particular the VCC pin of the flash. There is a small capacitor nearby connected to ground, and if you short the two together, you will break the PMIC on the board. The pinout of the flash can be found here: http://www.winbond-usa.com/resource-files/w25q64fv_revl1_100713.pdf

/CS -> SPI_CE0
DO -> SPI_MISO
GND -> GND
DI -> SPI_MOSI
CLK -> SPI_CLK
VCC -> 3.3V

flashrom should now be able to recognize the chip:
$ flashrom -p linux_spi:dev=/dev/spidev0.0
flashrom v0.9.8-r1888 on Linux 4.1.13+ (armv6l)
flashrom is free software, get the source code at http://www.flashrom.org
Calibrating delay loop… OK.
Found Winbond flash chip “W25Q64.W” (8192 kB, SPI) on linux_spi.

If it does, go ahead and flash the BIOS image:
$ flashrom -p linux_spi:dev=/dev/spidev0.0 -w BIOS.BIN
flashrom v0.9.8-r1888 on Linux 4.1.13+ (armv6l)
flashrom is free software, get the source code at http://www.flashrom.org
Calibrating delay loop… OK.
Found Winbond flash chip “W25Q64.W” (8192 kB, SPI) on linux_spi.
Reading old flash chip contents… done.
Erasing and writing flash chip… Erase/write done.
Verifying flash… VERIFIED.

[Alvaro]

Hello. Sorry, I cant reply on this days.

Yes, Im the first who tries with chinese instructions and my HI10 is broken. No charge light, nothing. Dont start, dont boot. I claim to Chuwi and VC Mall and they tell me that there is an easy way to repair. They are making a guide/manual and they will send me asap.

 

If not I will try the SPI interface…

🙁

[Valentin]

HI everyone !

@fbrozovic how did-you do for using SPI method? my chuwi is bricked (no bios) and I’ll probably try this but I can’t find anything about SPI on HI10..

 

Thank you

[fbrozovic]

Valentin wrote:

@fbrozovic how did-you do for using SPI method? my chuwi is bricked (no bios) and I’ll probably try this but I can’t find anything about SPI on HI10..

Have a look at the picture here: http://techtablets.com/forum/topic/chuwi-hi10-bios-update-for-x64/page/2/#post-20959

You need to open up the tablet (use a guitar pick or credit card along the sides), the SPI flash is located under the metal shield on the PCB.

[Ciro]

After Bios and Windows update the tablet can’t recognize my 64 Gb microsd anymore . I have tried smaller microsd without problem. Before update 64 Gb worked.

Probably  the problem is some driver. What can I do? I would like to avoid to reinstall everything from zero.

[Steve]

Przemo wrote:

I’m downloading files now. I have Baidu account, but transfer is bad. Mirror will be at: https://drive.google.com/folderview?id=0B7UJF0mw6LjJaExLQl9wRG9WVHM&usp=sharing Edit: All files uploaded

I updated my 64 bit chuwi hi10 using the v300 firmware. I attempted to follow the english instructions but the setup kept aborting complaining of missing “w:” drive and being unable to locate a path on drive “w:”

So i investigated a little bit, and found the Main.cmd from the scripts folder performs all the checks and installs the upgrade.

I determined that diskpart returned Disk number as 3 where it should have been 0 in order for the script to work. That’s why the diskpart script was failing because it was trying to clean and create new partitions in disk number 3 while it should have been doing that to drive 0.

As a result, drive w and drive r were not created and all subsequent script lines failed. (refer Main.cmd under Scripts directory in USB1 folder to know more)

So I manually executed each line and used 0 as disk number. I had to use a

1. hub reader combo 2.0,
2. two flash drives 14Gb each (cruzer blade and cruzer edge) and
3. a desktop USD keyboard
4. a USB OTC Cable (HUB had a USB opening).

Excluding the typing time, Windows was up in 15 minutes total. 5 minutes for flashing, 10 minutes for first boot, setting up etc.

Before updating the BIOS after having updated the new v300 software, I could still see the black and white annoying lines as shown in the attached image.

I updated the AMI firmware to 5.08 usng the EXE version from within windows once windows was up.

I have yet to check if these still appear after the  bios update.

Just thought these details might help someone updating the 64 bit firmware on 64 bit Hi10 devices…

Attachments:

You must be logged in to view attached files.

[SwanS]

Hello, since the other thread about the 64 bits upgrade (Chuwi H10 32to64bit upgrade [V200] + NEW BIOS and image [V300]) has stopped working, I paste here the answer from Przemo with the link to the new stable 64bits firmware for V200 batch (id 1231) in Mega server.

Mirror: m e g a . n z /#F!r8N2EAJL!obFGbr7l7C_Mj8Q3_QVcfg    (delete spaces)
File: V200/C106.CHUWI.S.10.TH2.ZH&US&HK&RU&ES.1231.X64.V200.rar

[Anonymous]

But be careful, when doing SPI flash, because there at least one version (which I have) with Winbond W25Q64FW (W vs V)which is only for 1.8V and RPi uses 3.3V so you need some logical voltage converter.

[Steve]

Steve wrote:

Przemo wrote:

I’m downloading files now. I have Baidu account, but transfer is bad. Mirror will be at: https://drive.google.com/folderview?id=0B7UJF0mw6LjJaExLQl9wRG9WVHM&usp=sharing Edit: All files uploaded

I updated my 64 bit chuwi hi10 using the v300 firmware.
……………………………………

Excluding the typing time, Windows was up in 15 minutes total. 5 minutes for flashing, 10 minutes for first boot, setting up etc. Before updating the BIOS after having updated the new v300 software, I could still see the black and white annoying lines as shown in the attached image. I updated the AMI firmware to 5.08 usng the EXE version from within windows once windows was up. I have yet to check if these still appear after the bios update. Just thought these details might help someone updating the 64 bit firmware on 64 bit Hi10 devices…

So after updating the firmware, the issue didn’t disappear. However, I found a BIOS update after a weeks here which fixed the issue completely.

http://techtablets.com/2016/01/chuwi-hi10-bios-update-bug-fix/

Please note that I have a 64 bit CHUWI Hi10 from the 3rd batch.

Moreover, Latest firmware files for the 3rd batch can be found here:

Firmware Files for the 3rd batch

Hope it helps someone.

[tmoyashi]

fbrozovic wrote:

Marcin Kruszyński wrote:

Mine Hi10 (first VC Lemon x32 batch) is not booting anymore and your SPI flashing seems like rescue. I’m new to this so can you write or PM some short tutorial how to flash Winbond using rPi? Can it be done using other PC or do i have to own SPI programmer? Thanks.

Alright, here goes: You need a Raspberry Pi or a similar board with a 3.3V SPI interface and Linux. On the Pi, install Raspbian and enable SPI via raspi-config, after rebooting the device file /dev/spidev0.0 should be present. Download flashrom and its prerequisites: $ sudo apt-get update $ sudo apt-get install libusb-dev libpci-dev $ wget http://download.flashrom.org/releases/flashrom-0.9.8.tar.bz2 $ tar xf flashrom-0.9.8.tar.bz2 $ cd flashrom-0.9.8 $ make && sudo make install Next, hook up the SPI flash to the RPi. Be very careful about shorting anything on the board, in particular the VCC pin of the flash. There is a small capacitor nearby connected to ground, and if you short the two together, you will break the PMIC on the board. The pinout of the flash can be found here: http://www.winbond-usa.com/resource-files/w25q64fv_revl1_100713.pdf /CS -> SPI_CE0 DO -> SPI_MISO GND -> GND DI -> SPI_MOSI CLK -> SPI_CLK VCC -> 3.3V flashrom should now be able to recognize the chip: $ flashrom -p linux_spi:dev=/dev/spidev0.0 flashrom v0.9.8-r1888 on Linux 4.1.13+ (armv6l) flashrom is free software, get the source code at http://www.flashrom.org Calibrating delay loop… OK. Found Winbond flash chip “W25Q64.W” (8192 kB, SPI) on linux_spi. If it does, go ahead and flash the BIOS image: $ flashrom -p linux_spi:dev=/dev/spidev0.0 -w BIOS.BIN flashrom v0.9.8-r1888 on Linux 4.1.13+ (armv6l) flashrom is free software, get the source code at http://www.flashrom.org Calibrating delay loop… OK. Found Winbond flash chip “W25Q64.W” (8192 kB, SPI) on linux_spi. Reading old flash chip contents… done. Erasing and writing flash chip… Erase/write done. Verifying flash… VERIFIED.

You made my day, fbrozovic!
My dead Hi10(even no charging light) was unbricked by re-flashing the BIOS.

I don’t understand what was going on (the power resetting triggered by a flat battery while booting collapsed the EEPROM ?).

Anyway, Thank you very much for posting such helpful information.

[Cupidz]

Sorry Tmoyashi:

What is the serial of your tablet?

Wich bios did you flash?

 

Today has arrived my Raspberry 3, and tomorrow i’ll test this procedure.

I hope to solve my problem like your!!

[tmoyashi]

Hi Cupidz,
Here is my configuration:
* Hi10 : V300, 64G421512xxxxx
* BIOS : 608? (downloaded from here)
* Writer : OrangePi PC + flashrom-0.9.8

You may want to desolder the red wire between the MoBo and the LiPo before flashing.
I wish you good luck.

[Cupidz]

tmoyashi wrote:

Winbond W25Q64FW

Thank you very much.

I’ve the Winbond W25Q64FW so i must buy a logical voltage converter.

My tab has the same serial of yours.

I’ll write back my results when i’ll try to flash.

Bye Cupidz

[Cupidz]

Finally i’ve tried this method.

The result is a full faulty 🙁

The Chip is recognized, the erase/write is complete without problems, but verify not!

Tomorrow or this weekend i’ll try another model of logical voltage converter, hoping that it is the problem, otherwise i’ll buy another eprom, on ebay.

 

Bye!!

[fuorigioco1981]

1200564 these are the last numbers of the serial number of my hi 10 win only 64bit. do i have a bios update?and how do we see the bios version?thank you

 

 

 

[Author]

Posts