TechTablets › Forums › Chuwi Forums › Chuwi Hi10 Discussion › New Bios Fix for Hi10 64bit serials HI10 64G42151105000 and higher
Tagged: Chuwi Hi10 bios
- This topic has 37 replies, 18 voices, and was last updated 10 years ago by
fuorigioco1981.
-
AuthorPosts
-
April 10, 2016 at 4:06 pm #32931
Anonymous
Inactive- Posts: 1
Help,
I flashed this bios to my 64G4216xxxxxxx and now it won’t turn on 🙁 The flash seem to go well, but then it just shut down and after that it refused to power up again 🙁April 11, 2016 at 4:27 pm #33057Anyone? Is my previous comment the correct procedure? Sorry for the double post, perhaps I’m being overly cautious, I just wanted to make sure due to the VERY limited support available. Thanks.
Or do what I accidentally did the other day and flashed it straight from the windows download folder whilst still in W10 with less then half a battery. It was a heart stopping moment I can tell you but went without a hitch.
April 13, 2016 at 4:25 pm #33319@Cyberheater: You are lucky – I accidentally did this with this update on another PC and it bricked my motherboard 🙁 – it isn’t even checking what hardware it is flashing.
My ChuWi is now bricked too – update seemed to run OK (directly from WIN), but it didn’t turn on anymore afterwards.
Does somebody know how to unbrick it?
I have HI10 Q64G421602XXXXXX and I’ve unfortunately find the notice about bricking the 2016batch just after flashing it.
April 20, 2016 at 3:02 am #34352Chuwi Hi10 SD card problems. (SN# Q64G42151106060)
I received my Chuwi Hi10 in January 2016. Things worked fine for 2 months. I had installed a 64gig Samsung Evo xc SD card, which worked great. I started running out of room on the card and decided to try a Sandisk 128gig which was also working fine for about a week or two. The extra storage was great! Then the 128gig SD card started failing.
Sometimes the SD card would work and sometimes Win10 would not recognize the memory card at all. Checking the Device Manager I could see an error in the SD Storage Class Controller.
This device cannot start. (Code 10)
{Operation Failed}
The requested operation was unsuccessful.
I tried uninstalling the driver but the error returned on reboot. The original 64gig Samsung card also produced the same error. I also bought a brand new Samsung 32gig with the same problem. It is definitely not the SD cards. I used an SD to USB card reader and all the cards work perfectly. I even installed the SD cards in my Laptop they all work great. I can read and write to each card using the SD to USB reader.
The weird part is that I installed an 8gig Sandisk (HC) SD card, this card works great. I can read and write to the card with no problems and I have yet to have any problems with it.
I flashed the BIOS with the file I found in the Techtablets forum with no change. I am really at a loss to understand what is going on. I also went to Chuwi and downloaded the new BIOS update C106_B101UAN.608 and reflashed the BIOS again. No help, same problem.
I was wondering if it has anything to do with how much memory I have left in my internal memory. I only have 10gig left of internal storage. Maybe it’s similar to needing hard drive space to page virtual memory. The only way to figure that out would be to reset the Hi10 and start over or keep removing software and see if the SD card starts to work. It took me a while to setup the Hi10 with all the software I like. I would hate to have to wipe everything out and start over.
It is a real bummer, this was a big selling point for me and now it doesn’t work correctly. I can and do limp along with the USB card reader. It would be nice if the storage was internal. I am amazed at the driver date. (SD Storage Class controller Date) is 6/21/2006
I ordered a new HP Spectre laptop. When I receive my new laptop and set it up with the same software I will be able to start deleting software and maybe even restore the Hi10.
If anyone has anything to add please let me know.
Thanks
Michael A. Sousa
April 21, 2016 at 5:50 pm #34555So can anyone help in fixing my bricked Q64G421602XXXXXX? Can it be done with a EZPorgrammer and where can I get correct bios file or is there an alternative way in doing this?
April 21, 2016 at 5:59 pm #34556This http://techtablets.com/forum/topic/chuwi-hi10-bios-update-for-x64/page/3/ seems promissing.
My 2016 Hi10 has unfortunately a 1.8V version of the flash chip, so I’m waiting for some parts to build a level converter (3.3V Pi isn’t usable directly).
Correct firmware should be avaliable on http://forum.chuwi.com/thread-229-1-1.html
Opening the tablet and removing metal tab is easy, connecting testclips is much worse.
Correct datasheet for the 1.8V flash is on https://www.winbond.com/resource-files/da00-w25q64fwc1.pdf
I hope I’ll be able to fix my tablet.
April 21, 2016 at 6:44 pm #34561To all who bricked use this file from Chuwi forums with SPI/EZProgrammer to revive your tab.
I flashed and bricked like some of you with the newer 2016 version with serial number 64G2416xxxxxx.
https://www.dropbox.com/s/zk79w64jxz48is4/Hi10%20BIOS%202216020001-5000.rar?dl=0
I flashed about 7 different bios files before this one finally brought it back to life.
I do not have a voltage step down attached to my SPI programmer and I’m fairly certain its not required.
I had messaged Chris on XDA sometime ago about similar voltage concern for a teclast I needed to flash.
April 21, 2016 at 6:56 pm #34564Big THNX for the answer I have access to a programmer at work, so I’ll give it a go!
April 21, 2016 at 7:43 pm #34568Please let us know if it worked for you also.
Would be nice to get a confirmation from someone else.
Big thing for programming these things is doing an erase/wipe/program/verify as a few times it looked like it programmed properly but failed verification.
April 21, 2016 at 8:20 pm #34574I wouldn’t use 3.3V even if the flash chip may survive it (according to the datasheet it is well out of its max range) – it could fry something else on the board (even cpu) – by powering the flash we are potentially powering all the 1.8V power branch, who knows what that might do.
April 21, 2016 at 8:49 pm #34583Totally up to you but it worked for me is all I can say.
April 22, 2016 at 3:20 am #34614@Anton: And do you have the q64fW version of the chip? It is true that without building a level converter it would be much simpler. Thanks for info.
April 22, 2016 at 5:42 am #34618🙁 It seems my PMIC didn’t survive the 3.3V flashing. Flashed, verified, but it just flashes USB HUB power led and nothing more…
April 22, 2016 at 5:20 pm #34693Which USB power led do you mean? I assume you tried to power on multiple times?
When I first plugged in micro usb charging wire the charging led did no flash and it did not power on immediately.
I had to try powering it on several times before it actually powered on and then the charging led started blinking.
I closed up my tablet already and I didn’t look at which version chip I have…if I have to open it up again I will look for the specific model of the chip.
<edit> I opened it up again, I do indeed have the 25Q64FWSIG chip. </edit>
However, having programmed a teclast that I know had the 1.8v chip without a level convertor I would be surprised if the 3.3v caused a burn out in your pmic. I suppose it could happen though.
April 22, 2016 at 5:54 pm #34698Well mine is dead as well :/ I’ve tried to flash it with my raspberry pi, but it doesn’t recognize the chip. did any of you had that problem?
I did use an logic level converter, however i had some problems finding 1.8v supply, but found a small resistor on the rpi which gave out 1.8v, so i soldered it onto that one.
Now i don’t know what to do, lol 😛
-
AuthorPosts
- You must be logged in to reply to this topic.

