Minibook dead on arrival - battery troubles

Happily and excitedly received the Minibook (8100y, EU version, 16/512 GB), unboxed it and after charging it overnight (I always first charge my new devices) tried to switch it on next morning.
Surprise: still dead. I recall the charging led being steady red all night, but at that time haven’t paid too much attention.
I connected the Minibook to the charger and able to boot it and configure Windows.
But device still not charging and indicating no battery available and 255% power (definitely from the charger)
Have sent an e-mail to Chloe, she very fast and efficiently answered suggesting me to reflash the EC and attached the download link for the new ones.
Full of hope, did it as instructed.
Same result.
Battery undetectable. Reboot device…same again…no battery.
I tried my luck entering the BIOS menu and, without changing anything) only FN+F4 (SAVE&EXIT) this time…voilá…I had the so desired battery icon in Windows bar and battery detected.
Full of trust and hope I let the device charging for several hours.
But when I tried to reboot it, again…no battery available…
Well, end of emotions…what to do know ? R&D of course…Started to read comments and threads on forum.chuwi.com and on Chuwi Minibook supporter’s Facebook page.
Find out I was not alone.
In my sufferings but also in my hopes to getting the expected functionality of my brand new Minibook.
Also installed AIDA 64 helping me to get a clear view that the battery was not detectable.
Have found the hidden battery controller in the MANAGE DEVICES, it was indicating “all systems go” :thinking: :upside_down_face: :lying_face:, tried to disable and back enabled it but the same final outcome: no battery…
Since most of the comments and suggestions were indicating that disconnecting the battery helps solving the problem…I have crossed the Rubicon. Opened the gadget…yes…had to remove the tiny (warranty :frowning: sticker) to remove the last screw and as so precisely indicated on forum posts, I disconnected and connected again the battery.
Voilá again: now having battery. quite uncharged (6%) but now charging and charging LED flashing blue-red this time.
Also detected by AIDA 64 even with a strange serial number: 123456789 :+1: Feeling better now.
Don’t think I had won the battle…
Charging process stopped at 60%.
Reboot the gadget.
Charging process continues: 61%, 62%…well, me crossing fingers and hoping for the best.
Start Aida 64 again and everything seeming to go fine.
But for each 2% of battery charge, AIDA was indicating an additional 1% battery wear…
Well, not so good for now…Also the charging process stopped several times and was only able to continue it after rebooting the device.
When arrived at 80% charge level and 17% battery wear :anguished: I stopped.
Meaning I turned off the Minibook and let it connected to the charger.
At that time I noticed it was warm but not hot in the area of the battery. Somewhere around 40ºC.
Charging LED was flashing red-blue.
Hoping for a better faith and luck next day. I left the Minibook charging again overnight.
Next morning, as a child waiting to see what Santa left under the tree…found the Minibook with the charging LED steady red.
Disconnect it from the charger, boot it up and find the battery icon in the windows bar. That’s good news and again hope.
Charge level: 84% and battery wear indicated by AIDA64 at 18%…What a …you name it…
In less than 3 minutes of functioning, the device stops…battery drained from 84% (really… George ???) to, will figure it latter, 5% and gadget stops.
What to do now ?
Connect charger, flash again EC, reboot the device, (new element, on the CHUWI booting screen, get for the first time an orange warning BATTERY LOW).
Well, new inputs, new hopes.
Boot the device, seems everything goes well, indicated me battery level low (5%) but have it charging. Open AIDA64, indicating me same info and a battery wear of 0%, good news and again naive hopes…


Process ends at 6%. No way to go further. Charging LED stubbornly getting steady red instead of flashing red-blue.
END OF STORY.
What next ? Publish it on forum and FB and will wait for CHUWI support. Really feeling as “dead” as my device which was DEAD ON ARRIVAL and after trying to do all I know&could to resuscitate it, had to give up.
With an important travel in 6 days from now, when I was expecting to use the Minibook as a most needed tool.
Having to pay now extra money to send it back for repair (wouldn’t be quite ethically fair because I can’t skip I received it already dead…) and perhaps even CHUWI to tell me I voided the warranty…
Feeling hurt and bit deceived.
I need that tool. I’m a traveller and content creator for several social-media. I need a tool allowing me to travel light because I have plenty of other photo&video gear to carry. Still think this is the device I need. And still happy I have supported Chuwi and the project. And even being able to understand it might not be easy to create such device from scratch. Having a sort of not so happy thoughts for the gentleman or lady who put the sticker A2/CHUWI/QC on my device’s lid. Because this was not Quality Control…That device It should have not left the factory as it did.
Yes, I feel now unhappy also of having crossed the Rubicon when opening that lid, disconnecting and reconnecting the battery, but…what if…the device would have arrived as I think it should: 100% functional allowing me to focus on my creating, editing, photo video job and not to have to search and find ways to make it come to life.
Well, that’s my story and grim experience for now, still hoping to have, the soonest the better, that tool I believed (and believe in + need) when I ordered my CHUWI MINIBOOK.

You sir must be a highly acclaimed writer. What a story! The problem that you have described is a lot like the still-unresolved “plugged-in not charging” issue that have afflicted a few generations of laptops since 1990. Many have tried and the solutions are always episodic. It now appears a miscommunication between the battery and the BIOS/OS. The firmware in the battery is either outdated or corrupted, or both (in your case, possibly a corrupted firmware). Manufacturers are of course ultimately responsible; although it is not practical for them to recall every single battery. So DOA is an apt description. Hope you get the problem resolved soon.

Thank you Sir, your answer is crystal clear to me now and really appreciate your effort to help me.

Will see what feedback to receive from Chuwi Aftersale/Service and hope to get the problem sorted soon. Thanks again

:heart::heart::heart::heart::heart::heart::heart::heart::heart::heart::heart::heart::heart::heart::heart::heart::heart::heart::heart::heart:︎ Good luck with that! =)

This trouble is really common on Chuwis. And like almost all chinese business factories they are unfair. When they have received the money they think the relationship is ended. Nothing is as false as this assumption.
I think that the quality of the batteries they use is very poor, furthermore i think they leave these batteries discharging under the damaging level, so they arrive damaged. At the first charge you will definitely kill it. Battery controller and related peripherals become crazy, nothing more, nothing less. No EC flashing, reboot, or anything like this will solve the problem. Only if the battery is in good condition, if not detected, it can be solved removing the peripheral and rebooting the minibook.