BIOS reset - Larkbox

If you can RMA, you should do it. When I interact with support, when I rewrite the BIOS, Windows 10 authentication may not pass, what should I do? I was asked. For me, I didn’t care about authentication and was offered my own BIOS. Therefore, I don’t think it’s good to provide it to other people easily. I’m also contacting support and some people are in trouble, can I provide it? I am contacting you. I think it feels like a contradiction. CHUWI has a strong partnership with Microsoft. That’s why authenticating with my BIOS can be a violation.
I don’t think this is good for you and me. Therefore, getting the BIOS provided by CHUWI support is the best solution, and I think RMA is also the solution. If my BIOS is okay, I can provide it, but it’s not possible right now. As for the BIOS upload, I only know where I was taught by CHUWI supporters. Rewriting is very simple, but if you don’t see the screen, you won’t know how far you’re going. When the rewriting is completed, the power will be turned off automatically. So, I can figure it out, but if it fails, RMA may not be applicable, so I think it is necessary to contact CHUWI support. I’d like to ask one question, isn’t it possible to enter the BIOS settings even if I press the power button and immediately press the esc key repeatedly?

2020年10月29日(木) 14:28 Sanjay Khandagale via CHUWI | Official Forum <chuwi@discoursemail.com>:

Okay understood, thanks.
For me its No display, no keyboard shortcuts work. Just Larkbox blue LED and Keyboard lights glow thats it.
Lets see what support says, I have already emailed them waiting for their reply.

I decided. To your challenging spirit.

http://chuwi.mediafire.com/file/dmshqp6xknotmjx/GB01_ZW_1_03_202007091733_%25E7%258F%25BE%25E5%259C%25A8%25E5%2585%25A5%25E3%2581%25A3%25E3%2581%25A6%25E3% 2584% 25E3% 2582% 258B% 25E6% 25AD% 25A3% 25E5% 25BC% 258F% 25E3% 2581% 25AEBIOS.rar / file

There is a file in. Transcend’s USB memory is the best choice. Because you don’t have to write boot. After formatting with fat32, transfer the unzipped file to USB memory, insert it into the usb port of LarkBox, and turn on the power. Please judge that the rewriting is completed by the blue led of LarkBox. Be prepared for the time to take more than 10 minutes. Good lack :+1:

2020年10月29日(木) 14:28 Sanjay Khandagale via CHUWI | Official Forum <chuwi@discoursemail.com>:

1 Like

I’m not good at English. I made a mistake. Good luck to you👍

2020年10月29日(木) 19:17 Sanjay Khandagale via CHUWI | Official Forum <chuwi@discoursemail.com>:

When the rewrite is complete, the blue LED will go out. Your PC has shut down. Rewriting is dangerous. Be careful not to make it a box.

2020年10月29日(木) 19:17 Sanjay Khandagale via CHUWI | Official Forum <chuwi@discoursemail.com>:

1 Like

Okay thanks alot for your help, will give it a go this weekend.

Hi,

I will do my best for you too. Good luck :+1:

2020年10月29日(木) 21:19 Sanjay Khandagale via CHUWI | Official Forum <chuwi@discoursemail.com>:

Just an update yesterday Chuwi Support team replied for the Bios Reset query asking serial number which I provided yesterday iteself.
Waiting for them to provide bios/instructions to reset it. Lets see.
Will keep you guys updated here.

I really hope there’s a fix. It was a really cool product until it became bricked.

Someone over on the Indiegogo comments of the “other” mini PC vendor mentioned a way to reset the BIOS on his Larkbox. Below is their post. Good Luck


Not sure if this helps. The BIOS is fragile, alot of settings can brick it. Chuwi forums has a lot of bricked Larkboxes but i found no solution. In the end i gave up waiting for support, opened up the unit and removed the CMOS battery. Press & hold power for 15s, let it sit over dinner then after putting it back together, BIOS was reset and it booted up for me! The setting that bricked mine was Chipset > South Bridge > OS selection.

2 Likes

…good eye, this could help a lot of people if it works !

-Rob

Thought I’d share my experience.
I found that my Larkbox Pro was unreactive after a big windows update. After restart it would show logo, spinning dots and then stay dark.
I forced a reset by holding the button down a few times and then then eventually I got a ‘please wait’ on screen also. Then it booted in to a troubleshooting mode. Then I navigated menu options until i got to an uninstall update option - there are 2 of them. I could only choose 1 of them, so I did. It took a while - about 1/2 hour I think. Then at least it would boot to windows. I read here that the problem is probably the graphics driver in the windows update so I went here… https://www.intel.com/content/www/us/en/support/detect.html and let it update the graphics driver ( also wifi and bluetooth) - chose - ‘restart later’., let it finish all then restarted. It’s been working ever since.

1 Like

Giving it a try today lets see, have disconnected battery pressed power btn 15secs and kept it aside without battery will check tomorrow and update you guys.

Successfully bricked mine via BIOS settings, standard blue light and no video or any reaction on usb. I think that NVRAM in firmware is damaged, or have settings, that cause failure. Interesting thing: if i’ll power it on, and wait 1-5 minutes, chuwi logo is displayed, but none happens after that (and fan also don’t work, so after 15-20 minutes box is getting really hot). In that mode USB is non-functional - checked with usb sniffer - only power applied, no command/data/protocol exchange is going. Main flash (with bios image) is 25LB64 - i’ll try to flash it with external programmer with provided image from this topic (better to have a valid dump from working larkbox, but i’m out of luck and don’t want to brick another one while soldering it).
P.S. If somebody notice button pins near power button - this is reset button, but it simply reset system, not bios settings.
P.P.S. CHUWI really needs BIOS/UEFI Specialist to make a normally working firmware - currently they simply adopts development board firmware with minimal changes and no QA/QC (and a lot of bricked devices as result).

1 Like

Solution found, but it will void warranty and require soldering skills, good soldering station & spi flash programmer, that supports 1.8v chips (GD25LB64C is 1.8v chip, ch341 and other cheap versions will burn it, so don’t use it without level convertor). Disassembly larkbox, remove mainboard, find soic-8 chip with 25LB64CVIG on second line, desolder it, erase & programm with BIOS image from BIOS reset - Larkbox , solder it back, assembly larkbox & power it on. First power on will ended in power off & restart, after that larkbox will resume normal operation.
P.S. I don’t take any responsibility for damaged hardware, or anything else.

1 Like

Larkbox works fine for a few days then it bricks. Leave it for a few days and its ok again. Saw IT guy at work and he thinks it needs the firmware updating. see logged error.

Are you still on the OEM Windows 10, or 20H2? I have this exact same error after a clean 20H2 install (from USB media) and haven’t been able to fix it, but am not sure if the clean install caused it vs. an in-place update or if this was already an issue out of the box.

Edit: link to my post about the issue. Apparently another member did the exact same without ending up with the error, which makes me wonder if there are differing hardware or firmware revisions out there. LarkBox Pro: Updated but missing drivers (20H2) - MiniPC - CHUWI | Official Forum

1 Like

No, I was still on 1909. I don’t think its the version of windows that’s causing this. What we need is an updated firmware and bios from CHUWI. I think it feels like this because after it has been on for while (downloading/checking/installing windows update) and then it restarts. At that point it bricks. 1 blue blip of the light next to the power button then it disappears for a few seconds and then comes back solid again but bricked…

Reached-out to Chuwi France and they told me there’d be no updates for the firmware/bios for the Larkbox Pro. So, I’ve had enough of the abysmal after sales service and I’ve sent it back and got a refund (Amazon never quibble). When this little device works, it’s great - Quake 3 at 1920 X 1080p at a solid 80fps for example, but if I can’t rely on the thing starting-up the next day then what is the point ? BTW I did update to 20H2 wiped it and did a complete re-install. It was great - and did everything I wanted - streaming 4k video, many tabs open, copying files and a game demo - all at the same time. I thought it had been fixed - until I tried to turn it off and on again. Anyway, I don’t think I’ll be buying anything from Chuwi again. Bye.

That is terrible after sales support. Almost seems like Chuwi regards the LarkBox as a failed experiment, and just gave up on it. Such a shame, because the device is so very close to being awesome. For me, at least good to know that I did not cause that error message with mine, and that I won’t have to hold my breath for a potential fix in the future.