[Hi10 Pro] [Official Version] Chuwi Hi10 Pro Windows, Android, Bios, Driver, tutorial Download

Thank you so much, you saved me and saved my device!

1 Like

im glad to see that¡

@manonegra222 coge los archivos

Unfortunately, it did not solve the problem, the device is still dead, I think it’s a goodbye for it, if anyone else knows something I can try, I appreciate it.

maybe @manonegra222 or @coyotefert have any other ideas on how to alive an old tablet :wink:

Can you explain what happened and what situation the device is in? It is very difficult to give a diagnosis from a distance and even more so if nothing is explained. You must be more explicit

Sure, I’ll try to explain it in the best possible way.

I was using it normally, and it gave a blue screen and it didn’t turn on anymore, I was using a Baseus 65W charger (Power Delivery) and charging it through USB C.

I noticed that sometimes when I connected it to the charger (the cable has a display that shows the consumption [Watts] and whether it’s using the PD protocol or not) the cable blinked for a moment (as if it was trying to activate Power Delivery), but it quickly returned to normal and the charging happened normally.

After it turned off (after the blue screen) it simply didn’t turn on anymore, I even disassembled it and made the measurements (it’s in the following topic: Hi 10 Pro (CWI529) - Don't turn on - #5 by Lopesleo)

I also noticed that it’s as if it’s in a loop, trying to turn on, I noticed this due to the variations in the voltages in all the parameters, which zero out and then return after a few seconds.

No light turns on on the board and neither the processor nor the power controller heats up.

I’ve already tried to reflash the BIOS but without success, there was no change in the symptoms.

I think there may be a Bios lock and that’s why it doesn’t start. You should try to do the following:

  1. You should put the charger in and charge for a few hours.
  2. Once charged, press the power button for 30 seconds
  3. press the power button intermittently 3 times (half-second presses)
  4. put the charger in and try to turn on now.

Hola . Después de instalación nueva de Windows e conseguido que funcione todo menos la pantalla táctil , (funciona cuando eliges si iniciar con Android o Windows pero una vez iniciado Windows va mal) el número de serie HQ10 HQ64G42171204018 .
Gracias de antemano y un saludo

Hola . Después de instalación nueva de Windows e conseguido que funcione todo menos la pantalla táctil , (funciona cuando eliges si iniciar con Android o Windows pero una vez iniciado Windows va mal) el número de serie HQ10 HQ64G42171204018 .
Gracias de antemano y un saludo…

Aquí tienes los drivers.

Como norma, antes de reinstalar un sistema, debes hacer copia de los drivers ya que hay dispositivos que no funcionarán con los genéricos de Windows.

https://1drv.ms/f/s!AqpKvT8-VB_8gcMCN8VnV_kkyB99Tw

gracias pero como instalan estos tipos de archivos y quien de estos va a funcionar a mi pantalla tactil

Aquí envio todos los archivos, incluidos los drivers mira a ver si en estos puedes encontrar el de la pantalla.

Flashtool

para instalar los drivers sigue las instrucciones del punto 8 este tutorial: [TUTORIAL] How to remove Android and install Windows on a dualboot tablet (Intel Processors) - Download&Tutorial - CHUWI | Official Forum

Hi @manonegra222,
I need assistance with my CHUWI HI10 Pro.
I have attempted to reinstall the windows install but it fails with errors in the screenshot
image

The Android installation process is not clear.
Most likely the phone is not detected during the android reset process.

Hi can you give me bios for HQ64G42170703320?

bios;

windows:

driver:

But I cant even reach to f7 menu. Can you help?

@manonegra could you try to see whats the problem?

Same problem happened to me. It was disconnected after first flashing stage.

The problem is the the device is not recognized in the Windows Device Manager. It is shown as “Cherry Trail CR” unrecognized device.
To fix the problem I updated the unrecognized device driver choosing manually option, choosing a “Android phone” and browsing the proper driver file.

@manonegra222