[Windows 8 General] articsilverfox:
Hi all,

thought I would give my version of what to do to try and install these Bliss roms which look pretty cool, thanks to Alberto96 for providing the link

I am no rom installer genius but here it goes anyway..

I think so far I have had more luck with the Bliss roms, I have been installing/creating a bootable USB stick the same way for any particular rom download.

First creating a bootable USB stick using Rufus

Rufus https://rufus.akeo.ie/

Direct download link https://rufus.akeo.ie/downloads/rufus-2.16.exe

The creation of the bootable USB stick via these ISO roms for me is exactly the same as the Ubuntu USB installation stick guide for windows https://tutorials.ubuntu.com/tutorial/tutorial-create-a-usb-stick-on-windows#1

So far the best ISO to download and write to USB via Rufus has been this Bliss ISO https://downloads.blissroms.com/Bli...roid-7.1.2_r27_k4.13rc1-bt_m17.1.5_pwb_01.iso

These are in "bleeding_edge" folder the https://downloads.blissroms.com/Blis...bleeding_edge/

Ideally one of the roms from the "Stable" folder should work better but they haven't for me, maybe my Teclast X16 is broken in some way.

https://downloads.blissroms.com/Blis...al/x86/stable/

I recommend trying any of the roms that start with Bliss-v7.2-android_x86_64

To boot from the tablet I have and use the offical docking keyboard case..

I find I can only jump into bios if you hit the "delete" key once or twice in the first second or two of when you first power on the tablet, doing alt+ctrl+del then trying to jump into the bios doesn't seem to work for me, only fresh power on boots seem to allow me to jump into the bios %100 of the time.

If you don't have the official keyboard dock then you have to use a USB hub and have your keyboard and USB stick in the hub.

Once your in the bios use the right arrow keys and shift to the 3rd menu labeled inconveniently "Save & Exit", inside this menu arrow key down to the "Boot Override" section

Then choose the "UEFI: General UDisk 5.00, Partition 1" in the menu and hit "enter" on it and it will boot from the USB device.

I recommend trying the "live-cd" mode once it boots to give it a try, these for me seem to work 100% of the time, while a lot of the roms I fully install onto builtin mmc storage fail to fully boot into GUI for some reason.

To fully install onto builtin flash chose the Installation option from Grub instead of live-cd mode.

I chose to blow away my whole mmcblk0 built in storage and format it to ext4. If you see sda1 thats your USB device, no point trying to install on that, chose the mmcblk0 device.

If you want to blow away your whole drive on your Teclast X16 then during the installation wait for the "Choose Partition" menu to come up.

Choose "Create/Modify paritions"

Choose "mmcblk0"

I choose "yes" to the question "Do you want to use GPT"

Once you see the partitions in the black screen menu interface I just hit the "d" key on all partitions until its just one line saying "58.2gb free space"

Then hit "n" and then just keep hitting enter for all the defaults which creates 1 single linux partition for the whole mmcblk0 storage device.

Then hit "w" to write out the choices made and then hit "q" to quit.

After exiting disk partition chose the mmc device again and choose to format to ext4.

Then say "yes" to every question it asks.

Then choose "reboot"

UPDATE 1

The best rom that has worked for me so far is this one Bliss-v7.2-android_x86_64-OFFICIAL-20170703-1717_k4.9-ax86_wf_01.iso

I have managed to fully install it and boot from it on my mcc built in storage. It did take a while to boot with the "Bliss" logo on the boot screen for a fair while to the point where I didn't think anything would happen and then got a google setup android screen.

While wifi device was visible and my wifi-router was visible I initially couldn't connect to it. I then tried my mobile wifi-hotspot and it worked.

I decided my main home wifi-router must have some configuration that the Teclast/Bliss-rom didn't like so I changed my wifi-router security settings to WPA2-only and AES-only (no automatic) and I also shortened my wifipassword, I think shorting my wifipassword was key. Until I made these wifi-router changes Android would claim there is "no internet" on my wifi-router even if it accepted the connection to the wifi-router. All is good now.

Update 1.5) I reinstalled this rom on another partition and found it wouldn't initally connect to my wifi-router again. I decided just to "skip" everything until I hit the main Android screen and then added my wifi-router passphrase and it accepted it and connected online. For some reason it dislikes my wifi-router on the first inital setup screens.

So far with this rom everything works including bluetooth but there is no "sound"!

Dead quite on youtube, I tried plugging my earphones, still no sound.

I did alt+f1 and then lsmod | grep snd and I can see a lot of sound kernel modules loaded including the 5640 sound device kernel module, but still no sound, there are also a bunch of other sound chipset modules loaded, I dont know if that helps or hinders or if thats normal. (tip if you go intl console via alt+f1 you can get back out into GUI via alt+f7)

The most disturbing thing I have seen is this Android versions claims there is only 1GB ram on my device.

Update 2)

I have worked out why live-cd mode always more or less works for just about any rom but when installing them onto builtin flash they fail to reach GUI.

I think the first couple of gigabytes of my built-in flash memory is stuffed.

I worked this out because I split my 64gb mmc into 3 partitions each about 20gb each and installed the Bliss rom on the "last/3rd" partition and it booted up into the GUI fine.

I then tried to install the Bliss rom into the first partition and while the installation went fine it wouldn't boot all the way into the GUI (boot loader messages etc do come up) it just sits there on the Bliss animated logo for ever.

I then tried to install into my middle partition and that also worked just fine.

I have used windows 10 purely for most of my usage on the Teclast X16 and it may of worn out some of the first couple of gb's of mmc storage and maybe unlike SSD drives theres no firmware smarts to identify stuffed mmc sectors etc as bad and it instead continues to use all the storage whether its good or bad. I don't know if there is a way to fix this other than avoiding a certain amount of gb's of the mmc's storage by partitioning the storage into 2 or 3 segments. This has been an interesting little discovery for me.