[Dirkblaster]

Awesome! Hoping the ZTE ROM isn’t too heavy and lets the hardware shine. Am really interested in seeing the camera samples and how it measures up to the Mi6

[Dirkblaster]

Remix has steps included for manually flashing OpenGapps, the AURA rom has play store built in

[Dirkblaster]

AURA runs like a dream, exactly what the tablet should have launched with. No lag and butter smooth on everything I’ve run so far (I’m not a heavy gamer, so take that with a grain of salt), multitasking is worlds better and there are no issues with Youtube like the RemixOS rom. All the MIUI features like smart cover and read mode work. It’s working so well I’m happy staying with MIUI rather than adding on a different launcher.  The included bootloader removes the error 03 on startup from having a custom rom and they’ve even included a new TWRP recovery that looks a lot nicer on the tablet form factor (nice touch!). Amazing job considering the state it was in just a few weeks ago where apparently nobody had source or a way to develop for this tablet.

Only bug I’ve found so far is that when you install new apps the icons don’t appear until after the launcher refreshes (usually a reboot, or by changing a setting that forces a launcher redraw).

[Dirkblaster]

Okay, massive headache installing using the supplied batch file with the AURA rom, managed to temporarily brick my device but was luckily able to restore using the DNX fastboot method (phew! Thanks Chris)

I’ve extracted the files and ran the following commands from the batch file manually:

(Assuming you already have oem unlock)

1: Go into Fastboot
2: fastboot flash data  %~dp0images\userdata.img
3: fastboot flash system  %~dp0images\system.img
4: fastboot flash boot  %~dp0images\boot_init_d.img
5: fastboot flash recovery  %~dp0images\new_twrp_2.8.7.3_mtp_bootloader.img
6: fastboot flash bootloader  %~dp0images\bootloader2.img
7: fastboot flash oemvars %~dp0\platform-tools\oemvars.txt
8: fastboot flash oemvars %~dp0\platform-tools\oemvars-battery-config-fake.txt
9: fastboot flash oemvars %~dp0\platform-tools\oemvars-battery-config-fake-disabled.txt

%~dp0 is the path up to the directory you extracted the files to

[Dirkblaster]

Given that the MiPad 2 has an Atom Z8500 as well as the Teclast X98 Pro, what would be involved to port over the improvements from Mirek’s ROM into this AOSP build? From browsing the MIUI forums nobody seems to be keeping it up to date, it is some sort of leaked developer build.

[Dirkblaster]

Maybe worth grabbing the factory image from the downloads section and reflashing windows from scratch (just in case recovery partition has malware inside too) if you’re concerned?

[Dirkblaster]

If you’re not too invested in your Windows partition maybe fully wiping it and starting from scratch would be your best option?

Step 13 from here will reinstall your Windows from scratch (not sure if you’d need to manually wipe the drive first, or if the WinPE will do it for you, as mine was wiped when I started off): http://techtablets.com/forum/topic/how-to-dualboot-androidwindows-on-k9c3/

[Dirkblaster]

Blandroid wrote:

Time Chijo wrote:

I have techclast tpad x98 pro . I can’t charge it when using OTG cable .. Because it is in the same charging point the charger cable is plug .. Any help please?

It’s not possible – it’s an either/or choice.

Chris put up a video where there are special hubs that can do charging+USB https://www.youtube.com/watch?v=Jg6AcRvmb8w

[Dirkblaster]

Unless the screen has been specially designed to accept a stylus (like Surface/Surface pro), the only type of stylus that will work are the soft rubber tip fat iPad type ones you can buy from ebay for $1, etc. It will do the job but won’t be much finer than your fingerprint

[Dirkblaster]

Are you running in Tablet mode (home screen is your start menu icons)? It may be hiding the icons in the system tray. Swipe from the right hand side of the screen towards the left and see if  ‘Tablet Mode’ is highlighted

[Dirkblaster]

francisco wrote:

hola me acabo de comprar una teclast x98 pro dual boot y quisiera saber si esta rom sirve para instalarla en el modelo que yo he comprado que es el dual boot es que he visto videos en youtube pero no deja nada claro si la tablet en la que realiza la instalacion de esta rom era version dual o no. gracias espero respuestas

From the first post, this is for the dual boot X98 Pro (K9C6) or the single boot Windows 10 (K9C3) which has been converted to dual boot as per this thread: http://techtablets.com/forum/topic/how-to-dualboot-androidwindows-on-k9c3/

(hoping google translate works)

 Desde el primer mensaje, esto es para el arranque dual X98 Pro (K9C6) o la única de inicio de Windows 10 (K9C3), que se ha convertido en un arranque dual según este hilo

 

[Dirkblaster]

Dirkblaster wrote:

Out of interest I tried loading the official Teclast Android ROM and it was unusable, not even registering touches. Any clues on why this is happening only in Android? When it was a Windows 10 only tab it was okay.

As a last resort I’ve reflashed the mirek ROM over the top of the official ROM and now it seems to finally be responding to touch normally (knock on wood!)

I’d previously tried repartition reflashing, clean flashing and dirty flashing over the top with no success, but putting the (still unusable) Teclast ROM first and then the mirek ROM has apparently fixed the issue this time??

—

Edit: After installing a few apps, the whole android partition has ground to another laggy mess. I don’t know what’s causing this as I’m not installing anything out of the ordinary, the hardware buttons are responding instantly. It just seems like the touchscreen can’t keep up?? Antutu is benchmarking at 70k+

Windows partition has been reinstalled and is as smooth as butter, so I’m at a loss as to what is causing this issue?

—

Edit 2: This definitely seems to be related to the touch screen driver in Android somehow. I’ve plugged in a keyboard/mouse using the OTG and Android is smooth as butter. Perhaps it’s something with the K9C3 hardware??

—

Edit 3: This seems to be a known issue for the old X98 Air models due to some component issue and differences between Android 4.4/5.x according to TecKnight’s post here. Is there a chance there is a modified boot.img for the X98 Pros?  http://techtablets.com/forum/topic/ttt-fix-x98-air-devices-touchscreen-functionality-in-android/

—

Edit 4: I’ve tried flashing the boot.img from the v5 ROM (same as v6), the original Teclast Android ROM (okay, but still laggy) and an X16 ROM based off of mirek’s v4 (Screen upside down, doesn’t respond to touch). There’s definitely something specifically wrong with the touch screen driver in Android as the tab’s touch response runs perfectly in Windows and the BIOS

 

[Dirkblaster]

Out of interest I tried loading the official Teclast Android ROM and it was unusable, not even registering touches. Any clues on why this is happening only in Android? When it was a Windows 10 only tab it was okay.

[Dirkblaster]

Have just flashed v6, thanks mirek for the amazing work with the ROM and flasher tool. It seems to be super choppy for me to the state of being unusable, where touches are not being responded to or have a 5-8 second lag and then brief flashes of being smooth as butter.

Not sure if there’s a ‘bedding down’ period where it needs to do something in the background? Have tried installing Nova launcher and switching everything to fast but no luck.

I’ve gone from a Win10 only K9C3, flashed the new dual boot BIOS and immediately used your flashtool to install your ROM, not sure if that is what has caused this?

Also – I chose option 3 in the flash tool to repartition and wipe windows, but the guides to reinstall the windows partition say to choose the Windows option from the dual boot at BIOS which is now gone. Do you know what I would need to do next?

[Dirkblaster]

I finally gave up and rolled back to the 10.x drivers. Definitely seems to be more stable and even possibly snappier/more accurate with the touchscreen than the 15.x drivers

[Author]

Posts