[Fame]

Sorry for the late response yes, albeit the boot.img has to be swapped/modded to load the necessary kexts. These Chinese tablets are all the same, the companies selling aren’t manufacturers, they are distributors sourcing products from the same manufacturer to repackage/rebrand.

The X16 shipped with Remix OS II and all ports originated from that. Your X10’s (or any 3G tablet) rom was finicky due to unknown modems being used, but you could get Remix OS II to work but not necessarily 3g support. Either way ou would have been upgrading to 5.1 if you’d applied it and my advice; run these devices solely on Android as Windows 10 64bit consumes 22 GB before updates , the Ram on these machines isn’t enough to support 64bit OSes

Jide really put effort into optimizing their Remix builds, they were superior to all the stock Chinese roms especially Play Store compatibility with phone apps. Upgrade issues are reversible, I was always able to go back and I did some completely unnecessary things during testing. ABD support was built directly into the chipsets so there is no way to permanently corrupt a Cherry Trail device with a bad flash unless you damage your USB port.

I know some people thought they bricked their devices but it simply couldn’t be the case. Your issue sounds like the bios setting as Cherry Trail devices had a habbit of defaulting to an incorrect setting on these dual boot tablets once an OS was corrupted. That is where I would start before completely  re-flashing.

[Fame]

Hey, Machetekills I owe you quite a bit (Remix OS 2.0 fully ported). I tested your rom,  some issues with Google services, related apps crashing and force closing, could not update either. I think repacking with x80 v1.09 stock files for services will fix this. Thanks for all your work.

[Fame]

It’s normal but not frequent behavior on these Chinese OEM roms. Blame Intel for the kernels they provide. You don’t have to worry too much about flashing, after charging to 100% it will re-calibrate. If it happens again just do the same thing.

[Fame]

First: Download X80H fastboot firmware from repository here or from Teclast’s English website (Google),  Always have these handy.

Leave it charging powered off for a full day. (Sometimes battery.manager fails on these rom. It can  even take over 13 hours to charge back to 50%)

Hold Power + Volume Down for 15 seconds. (Hard Reset)

Power On. (If the device boots, wait until home screen. Even if your usb prompt warning is gone flash the official firmware you downloaded. There are tutorials here and in the archive itself.)

Go to settings > developer (if not there go to about>tap build version untils you activate developer options). Turn on Dev options and USB debugging. Proceed to flash rom.

[Fame]

We have been looking for a method as Martin requested. The custom gpt.bin files available are still leaving a lot of space unallocated. Other forums have posted varying sizes but none have true 32GB or 64GB configuration. Closest configurations we found so far are 25GB (found here) and 53GB (found elsewhere) and both are leaving around 5GB unallocated (neither used nor reserved). Any help would be appreciated.

We tried downloading firmware of other 32gb and 64gb Teclast Tablets to retrieve gpt.bin files from those roms but the formats are quite different.

[Fame]

Is it possible to root without kernel source code? I ask because someone has already unlocked the boot loader and rooted this model with full custom recovery, superuser etc. and the process is pretty simple. A tutorial was uploaded on YouTube.

[Fame]

Just repartition Wi<span style=”line-height: 1.5;”>ndows by allocating more space in the disk text file on your winpe: drive. The Android partitioning on the tablets was botched within the ROM. </span>

<span style=”line-height: 1.5;”>Most people will see Flash Disk size as 10gb yet actual space is around 4.84 with 4.64gb going to waste. Swap the gpt.bin file with a true 10gb configuration (files can be found in another thread here) or lower if you want to give Windows more space. </span>

<span style=”line-height: 1.5;”>Either way if we want Windows updates complete reinstalls of both Android and Windows need to be done as more and more space will be required in the future. Its honestly better to just decide on one OS.</span>

[Fame]

Android needs priority when dual booting. You have to flash Android first which will wipe your disk then allocate remaining disk space to Windows.

[Fame]

Thank you very much. We were holding custom gpt.bin files in variation from 2GB through to 53GB but missing one for 32GB but could not find 32GB. The closest we had was 20GB.

Dear OP, any idea how these are created? Flash Tool determines total available disk space for rom installation a little larger than what these files allocate. For example. gpt.bin for a 16GB tablet will allocate 12.5GB, 32GB at 26GB and 64GB at 53GB.

Would love to recover some of that unallocated space.

For anyone who would like to allocate other sizes we’ll attach what we could find. We figure 20gb allocation would be pointless as OP gave us 26GB but we added 53GB for those with 64GB tablets who want to use Android only. Rename to “gpt.bin” before flashing. Remember to backup originals.

Attachments:

You must be logged in to view attached files.

[Author]

Posts