I've managed to get root on my Surftab ventos 10.1 (cause is already there) after reading the the others ventos (9.7 - 8) It's really easy: Just install from market SuperSU and it will work. After rooting the tablet I got rid of most of the default app and garbage put in by the vendor, after a backup with titanium. With terminal emulator I managed to dump the recovery partition su dd if=/dev/mtd/mtd3 of=/sdcard/recovery.img And here is what Recovery builder did to it: I'm still not sure if it will work, will post how it goes. I can confirm that the Root method posted by SCRAX (thanks to him and to TheSSJ!!!!) runs perfectly!!!! Before that I needed to: - Update/upgrade firmware using the file ST10216-v2_FW_pack.zip downloadable from into-trekstor.de/fw/surftab/ site (user: guest - pass: guest) (it seem to be necessary to allow the installation of the RK3066 chipset drivers on the pc, contained in the zip file) - install a new CWM to enable a former complete backup of the unit, using (thanks to androtab.info site!): RK_Android_Tool_v1.35 + RK30 Driver (you can find them googleing.) RK30GENERIC_CWM (files.androtab.info/rockchip/rk307/RK30GENERIC_CWM.zip) And, finally, following the Scrax/TheSSJ method!!!! Bye everybody! And thanks everybody for the help!

Aug 11, 2013 Das TrekStor SurfTab Ventos 7.0 HD im Test.

Quote: Originally Posted by grinchio I can confirm that the Root method posted by SCRAX (thanks to him and to TheSSJ!!!!) runs perfectly!!!! Before that I needed to: - Update/upgrade firmware using the file ST10216-v2_FW_pack.zip downloadable from into-trekstor.de/fw/surftab/ site (user: guest - pass: guest) (it seem to be necessary to allow the installation of the RK3066 chipset drivers on the pc, contained in the zip file) - install a new CWM to enable a former complete backup of the unit, using (thanks to androtab.info site!): RK_Android_Tool_v1.35 + RK30 Driver (you can find them googleing.) RK30GENERIC_CWM (files.androtab.info/rockchip/rk307/RK30GENERIC_CWM.zip) And, finally, following the Scrax/TheSSJ method!!!!

Bye everybody! And thanks everybody for the help!

Which tool do I need to use to flash the single huge stock recovery img: ST10216-2A_V05.img - 495 021 284 bytes This 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! In the meantime, I have successfully recovered my old proper MTD partition setup by flashing the stock img (ST10216-2A_V05.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! 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/wpa_supplicant(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. Hello again, final update from me before the weekend. I have finally managed to create dmesg and catlog output after trying to activate Bluetooth: see attachments. This has been quite difficult, as typically, just a few seconds after trying to unsuccessfully activate Bluetooth for the first time, the kernel crashes: The tablet becomes hung/unresponsive, and I get kicked out of 'adb shell' with this message: error: protocol fault (no status) Also, I noticed that with the original stock Android 4.1.1, the WLAN driver (compiled statically into the kernel) states in dmesg log: MT5931 SDIO WiFi driver (Powered by Rockchip,Ver 2.07) init. While with your CM 10.1 (but the exact same 3.0.8+ kernel), the WLAN driver states on init (from mt5931.ko): MT5931 SDIO WiFi driver (Powered by Rockchip,Ver 1.08) init.

Many thanks again in advance & have a nice weekend, 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: CONFIG_MT5931=y 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. While you seem to have included Bluetooth drivers for MT6622 (system etc firmware MTK_MT6622_E2_Patch.nb0 and libbluetooth_mtk.so), the Ventos tablet has BCM4329 as its Bluetooth chip: CONFIG_BT_HCIBCM4325=y in the kernel config file and the dmesg file for the Trekstor 4.1.1 stock ROM says: [BT_RFKILL]: bcm4329 module has been initialized,rc=0x0 This 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! OK - now it's even worse: I fear that I have bricked my tablet.

And I was so happy, because I had succeeded to recompile the kernel from the source as provided by Trekstor and had created a kernel.img file from this kernel Image as well as the missing mt5931.ko module in version 2.07. But after I flashed this new kernel.img (created by me) into the tablet, I got fatally stuck: The tablet now does no longer boot in normal mode, but only in recovery mode, and unfortunately, I currently don't have CWM on the recovery partition, but only the stock recovery image with its limited capabilities. I have tried to use 'update rkimage from external storage' with the ST10216-2A_V05.img (renamed to update.img in the root directory of the external SD card), but no luck: 'Find and check firmware. Cannot found firmware image or invalid image. Update rkimage complete.' Is there a way to enter bootloader mode using the hard keys on the Ventos (I only know how to enter the recovery partition, which seems unable to recover from this mistake.)? If not, then I am really horribly stuck.

Do you have any idea whether it is possible to revive this tablet, or can I now dispose of it as it is unrecoverably bricked now? If you are able to help me revive my tablet, I promise you will receive a well-deserved first donation. Thanks a million in advance! 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. I still don't know what went wrong when I tried this for the very first time, but now it worked anyway.

In the meantime, I have found out that indeed from booting with the stock 4.1.1 ROM and examining locgcat output that indeed, my Bluetooth chip is MT6622 and not BCM432x, even though there also is a log entry stating that the tablet also seemingly successfully activates BCM4329, but it doesn't really do this. I am now all set for further experiments with CM10.1: Even though I am now able to manually successfully insmod mt5931.ko (in my newly compiled 2.07 version) as well as the old wlan.ko from the stock ROM successfully on top, I have not yet managed to activate WLAN again using this configuration. Maybe I need to rebuild wlan.ko myself as well.!? And you are indeed correct in terms of the vendors providing corrupt kernel sources, or - as in my case - kernel sources that only compile without changes on a particular gcc 4.3 version, but fail with any later gcc.

Let's see whether I will be able to sort something out - I will try to do so for some more hours until I either succeed or consider this an interesting, but frustrating and futile experience. I will keep this thread updated. Thanks anyway for your help & best regards, awl. Hello again, Oma, do you already know this git repository for a tablet-centric rk3066 3. Vista Sp1 Compcln Exe Downloads there. 0.36 kernel?

No opinion added. Your opinion '%s' has been saved. Your opinion has been updated to '%s'. Your opinion '%s' has been removed. There was a problem saving your opinion.

Please try again or contact DeviceAtlas support. There was a problem updating your opinion.

Please try again or contact DeviceAtlas support. There was a problem removing your opinion. Please try again or contact DeviceAtlas support.

Only integer values are permitted for this property. Only alphanumeric characters and, _.

- ^ / + [space] are permitted for this property. Only boolean values are permitted for this property. Please choose or enter an opinion value.