POV Mobii 7 PROtab2 stuck on boot screen

RFZ

Member
Jan 7, 2009
40
0
0
Hi,
I've got a Point of View POV Mobii 7 Bussinessline PROtab2 ( TAB-7C-4GW-1 ) which is stuck on the bootscreen.
- it does not power off when I press "power" for >10s
- the reset switch on the back powers it off
- pressing "home" while powering on results in an update screen after ~5s (little green android with box and arrow next to it) which changes to recovery ~1s later (android with exclamation mark) where recovery menu can be entered/hidden by pressing "home"
- wipe cache or factory reset in recovery didn't help
- "reboot system now" in recovery actually powers device off

I've downloaded the latest firmware from http://81.21.136.56/downloads/Tablets/ 7 Inch Tablets/TAB-7C-4GW-1 Firmware Upgrade/ which I was able to flash few years ago...

I've installed Telechips VTC driver which is part of the download.

Connecting the device via USB results in four "Telechip s, Inc.M801_88 USB Device" beeing recognized by windows as mass storage (empty drives) and an unknown device "M801_88" where no driver can be found.
It is the same in recovery mode and after regular boot. A usb reconnect is done when the device switches from update to recovery mode, but device constellation keeps the same.

Telechips Update-Tool "FWDN V7" (also part of the download) does not see a device (it should show a popup when a device connects, I guess)...

I've tried manually assigning the VTC driver to the unknown device, but that doesn't work. The driver supplied is just an installer... I found inf-files on the system after installing it, but assigning them says that they aren't drivers. Also listing all systems drivers doesn't who a driver from Telechip to select...

I've tried it on Windows 10 and in a Windows XP VM with identical results...

Any ideas what to do?

Edit: I managed to assign a generic ADB driver to the unknown device. It lists as "0123456789ABCDEF device" and limited shell is available (recovery?)
 
Last edited:

RFZ

Member
Jan 7, 2009
40
0
0
The device is okay again. I really hate it when things aren't reproducible, but after performing a factory reset in the recovery once again, it booted just fine...