Android no sound Chuwi VI10Pro after flashing

[Jonathan]

You might have the wrong BIOS; or else you’ve flashed the wrong Android version for your tablet; or there’s a BIOS setting issue or a H/W problem. Could also be any combination of the issues.

Did the tablet work when you got it?

Have you changed the BIOS since then?

If I remember correctly you flashed a different Android image?

[Jonathan]

According to the serial you posted (221511) and ImADev’s table here you should be using J1D_S165C_206 BIOS dated 10/30/2015. You are of course using G1D_S165_206.

Get the proper version from here, the password for the download site is: en.chuwi.com

1. Charge your tablet fully.
2. Plug your tablet into its charger.
3. Extract the BIOS rar file onto a FAT32 formated USB drive and plug it into your tablet directly (no hub).
4. Restart your tablet and immediately press escape until you get to the 6 icon boot options screen.
5. Select Boot Manager and choose the Internal EFI shell.
6. Type: “fs1:” <enter> (if you get = ‘-‘ instead of ‘:’ you have numlock on, press Fn+ Insert to turn it off).
7. Type: “startup” <enter>
8. Wait, be patient if you interrupt this process you’ll brick your tablet.

 

[Jonathan]

On the other thread you told me you got an error when trying to flash the BIOS, what error please? Security issue perhpaps?

[Javier González]

the error closes the shell real fast, but I think is something like EFILINUX ERROR or something similar.

[ImADev]

It could be that Javier’s flashed the wrong Android image, since they’re version specific. It’s either that or he’s using the completely wrong BIOS version.

Vi10 Pro 221511 BIOS: https://mega.nz/#!wBZmFDCT!P2Ss3pyWggPlzPNjk6lRcMNtltJYrURofQQ_yTd4zm8

1. Format a USB drive as FAT32 and extract the contents to the USB
2. Plug the USB drive and USB keyboard into your tablet
3. Tap ESC as you power on your tablet to boot to your BIOS’s boot manager
4. Select the EFI USB device

Everythings automated so the tablet will reboot when it’s done.

[Javier González]

The error persists even with the latest BIOS image you gave me, and I still have the G1D BIOS version.

[Jonathan]

@Javier, you might get find that things go smoother if you go to the Secure Boot Options and disable Enforce Secure Boot. Linux shouldn’t come into play with the shell.

@ImADev, you are probably better placed to deal with this issue than me, do you want to take it from here?

[ImADev]

@Jonathan
You’re actually on the right track. Secure boot may be an issue here.

If Javier can boot to or install Windows then he could just use the 221511 flasher that I released before.

[Jonathan]

@ImADev, regarding the Window’s flasher, he could indeed then after the BIOS is fixed go ahead with driver installation. Sounds like a plan. (By the way I love the way that Windows is trusted by Secure Boot but then lets applications do whatever they want if they have end user permission, almost as good as not having Secure Boot to start with…)

[Author]

Posts