Update Trekstor Ventose
Which tool do I need to use to flash the single huge stock recovery img:ST10216-2AV05.img - 495 021 284 bytesThis must not be done with RKAndroidTool, right!?I don't even know how to do this with my stock recovery partition, as it seems to expect the img file to reside in the external SD, but have a specific name in order to find it.!?Sorry for my newbie questions.Will also provide dmesg and logcat output for the Bluetooth chip once I have restored the correct (non-standard) MTD layout and reinstalled CM 10.1.Thanks again,awl. Thanks a million for your kind help!OK, I noticed that the new 'model fix' patch now additionally includes a Bluetooth kernel module! Great!In the meantime, I have successfully recovered my old proper MTD partition setup by flashing the stock img (ST10216-2AV05.img, see above) using RKBatchTool 1.8.So I will now (maybe tomorrow, as it's getting close to midnight.) try to install CM 10.1 again from step 1, but keeping the stock recovery img.
Hopefully this will keep the Ventos MTD layout - otherwise now I at least know how to restore it.Thanks again & have a good night!awl. Hello Oma,bad news: With the updated model fix from post 15, things are even worse: Neither WLAN nor Bluetooth now works, and we have a lot of error messages about OutOfMemory and OpenGL renderer in the catlog.For WLAN, the issue seems to be:02-13 19:14:28.740 E/wpasupplicant(1815): wlan0: Unsupported driver 'wext'for Bluetooth, Idn't even find any error messages, but it's simply not working.Please find both catlog and dmesg output with this setup attached.As I will only have time to look into this again after the weekend, please take your time - no need to hurry.
And in case it looks like there is no easy remedy, I think we'll simply stay with the stock 4.1.1 ROM for this device.Thanks again & best regards,awl. Bad news: There are even two issues that need to be resolved with the most recent model fix from post #22:(1) Even though the MT5931 driver must be included statically in the kernel:CONFIGMT5931=yin the kernel config, and I do not have any mt5931.ko on Trekstor's Android 4.1.1 stock ROM, with the most recent model fix on CM10.1, I still cannot activate WLAN either.(2) Also, Bluetooth still cannot be activated. I think that the model fix still contains a wrong Bluetooth driver.
Trekstor Ventos 10.1 Android Update
While you seem to have included Bluetooth drivers for MT6622 (systemetcfirmwareMTKMT6622E2Patch.nb0 and libbluetoothmtk.so), the Ventos tablet has BCM4329 as its Bluetooth chip:CONFIGBTHCIBCM4325=yin the kernel config file and the dmesg file for the Trekstor 4.1.1 stock ROM says:BTRFKILL: bcm4329 module has been initialized,rc=0x0This also means that the stock kernel should already include the Bluetooth driver (as well as the WLAN driver). Still, CM10.1 does not seem to detect both drivers.!?Do you have any idea why neither WLAN nor Bluetooth do work with the CM10.1 ROM even though the kernel should include the drivers?In the meantime, I try to set up a 3.0.8 kernel compile environment for the source provided by Trekstor and will try to compile both WLAN and Bluetooth as kernel modules. I'll report back on my success.Many thanks one more time!awl. Sorry, that won't work: I cannot open the Trekstor without breaking it - it is completely sealed.But I seem to have found the solution: It turns out that the device now registers in Windows with device ID 18d1:d001, and I was missing the driver for this, but I managed to override Windows to accept the generic driver from the Android SDK.So I can now connect via adb to my device when in stock recovery mode - this did work before, but with a Trekstore USB vendor ID.Seems that I'll be back on track shortly. OK, so finally, I'm back on track without opening the tablet:What was needed was to clean up, deinstall and reinstall the Windows adb drivers in order to deal with the perturbing number of different device IDs that stock ROM, stock recovery, CWM recovery, CWM ROM and bootloader are using: a nightmare! The Windows tool 'USBDeview' was a tremendous help with this - otherwise I would have failed.But with the correct driver, I was able to connect again with adb while CWM recovery was running, and switch the device back to bootloader mode using 'adb reboot recovery' in oder to flash again.So I have now tried once again to install the kernel that I had successfully compiled before, and this time, I succeeded.
Trekstor Ventos 10.1 Firmware Update
Not original firmware but is working very well PS: not ventos 7.0 HD its normal ventos 7.0 (ST70208-2). Don't forget to set USB Burning. Amazon.com: UpBright NEW 5V AC / DC Adapter For TrekStor SurfTab ventos 8.0/10.1 Tablet PC Switching Power Supply Cord Cable Wall Charger Mains PSU: Computers & Accessories. If you are a seller for this product, would you like to suggest updates through seller support? Would you like to tell us about a lower. In the kernel config, and I do not have any mt5931.ko on Trekstor's Android 4.1.1 stock ROM, with the most recent model fix on CM10.1, I still cannot activate WLAN either. (2) Also, Bluetooth still cannot be activated. I think that the model fix still contains a wrong Bluetooth driver.