Can X98 run Chrome OS???
It seems the old dog needs a new trick and I am wondering anyone has any knowledge on how to flash a chrome OS onto an X98 pad
(not need to care the dual boot system anymore, but I don't want to brick the machine either...)
Thanks,
Tony
Update:
I do have a bootable usb and usb port hub for keyboard and mouse...
-Do enter the x98 pad Bios and change the boot sequence and it does not work.
-Do go to the win10 advance reboot and it does not work...
and then read other flash methods:
-Try using PhoneFlashTool but it do not recognize the ChromeOS zip image.
(should I flash the pad like flash a Linux system for the pad)
What can I do next...
Update #2
Using override boot in bios with a USB stick and it will install the whole thing at ease, however, there is no touchpad and sound...
However, when I install virtualbox in the ChromeOS and then reboot, the USB function is all gone!
Now I am stuck again...
(*use rufus can install any bootable OS on scandisk USB stick, highly recommended.)
Hi @grygry777, I'm also interested in installing chrome OS on my teclast, could you please share some insights from your experience?
Did you use chromefy (croissant)? what images? what is working / not working?
What's required for the flashing process? if you don't care to elaborate about this part a link would be great too.
What OS did you end up with?
Thanks
Hi @TrampGuy, I just using "[email protected]" one,
Use Rufus to install an image in a usb stick.
The flashing process is simple and forward in the bios setting, and the rest is pretty automatic... make sure you have a mini USB hub for mouse and keyboard all the time...
everything goes fine (and fun) but right after I install VM which recommended by them, the USB function is all gone...
(now the machine is a 'functional brick', since I have minimum knowledge in BIOS side, I don't know what to do now... The point is I cannot reflash the bios using those three files(IntelAndroidDrvSetup1.5.0, iSocUSB-Driver-Setup-1.2.0, PhoneFlashTool_5.3.2.0_win32), it's just can't find my device and I don't know why, really stuck here now)
Hi,
I have also such a thing lying around here and was wondering whether it will work to load ChromeOS on it.
Have you fixed your issues in the meantime? Or have you dropped the HW finally for scrap? What was the reason for installing VirtualBox inside of ChromeOS?
Tnx in advance! KR,
Hans.
grygry777 said:
...
(now the machine is a 'functional brick', since I have minimum knowledge in BIOS side, I don't know what to do now... The point is I cannot reflash the bios using those three files(IntelAndroidDrvSetup1.5.0, iSocUSB-Driver-Setup-1.2.0, PhoneFlashTool_5.3.2.0_win32), it's just can't find my device and I don't know why, really stuck here now)
Click to expand...
Click to collapse
The most information about those cheap China-made tablets will be on techtablets.com. In the forum you will find a dedicated section for the X98 Plus II. Fingers crossed you find someone there who can help unbrick the pad.
Have you succeded to get the touchscreen work before the machine went down? I have currently no idea how to solve that one.
Ah ... there are articles around, that you should never install virtuabox on chromeos (sorry, I know you already realized). Even though other articles state different messsages. Up until quite current kernels the HW virtualization support is not available in the kernels. Probably the discrepancy is related to specific processors ... I don't know.
grygry777 said:
Can X98 run Chrome OS???
It seems the old dog needs a new trick and I am wondering anyone has any knowledge on how to flash a chrome OS onto an X98 pad
(not need to care the dual boot system anymore, but I don't want to brick the machine either...)
Thanks,
Tony
Update:
I do have a bootable usb and usb port hub for keyboard and mouse...
-Do enter the x98 pad Bios and change the boot sequence and it does not work.
-Do go to the win10 advance reboot and it does not work...
and then read other flash methods:
-Try using PhoneFlashTool but it do not recognize the ChromeOS zip image.
(should I flash the pad like flash a Linux system for the pad)
What can I do next...
Update #2
Using override boot in bios with a USB stick and it will install the whole thing at ease, however, there is no touchpad and sound...
However, when I install virtualbox in the ChromeOS and then reboot, the USB function is all gone!
Now I am stuck again...
(*use rufus can install any bootable OS on scandisk USB stick, highly recommended.)
Click to expand...
Click to collapse
Try Brunch framework, CloudReady or Fyde OS
So if anyone is still thinking about installing ChromeOS on Teclast X98.
I managed to get it running using the guide on
(sorry there is no official website or blog on this guy's work). Look in the description of the video for written instructions.
I can use the OS if I have a bluetooth mouse and my bluetooth case keyboard connected. I'm trying to look for touch drivers to insert.
I have an air 3g teclast x98 I'm very interested to try to install chrome os as on the android side I'm stuck on android 5 and I can't do many things
drrayc said:
So if anyone is still thinking about installing ChromeOS on Teclast X98.
I managed to get it running using the guide on
(sorry there is no official website or blog on this guy's work). Look in the description of the video for written instructions.
I can use the OS if I have a bluetooth mouse and my bluetooth case keyboard connected. I'm trying to look for touch drivers to insert.
Click to expand...
Click to collapse
Hi drrayc,
did you manage to get the touchscreen working?
Manuellsen2k8 said:
Hi drrayc,
did you manage to get the touchscreen working?
Click to expand...
Click to collapse
Nope. Had to use the keyboard and Bluetooth mouse. I never figure out which driver to inject.
Related
Hello all.
First of all, before people shooting at me and saying "please search", I come from many Google and xda search with "MacOs, download mode, failure vm, virtual machine, odin , kies" in every combination you can imagine and no result.
So, the problem is the following one:
I remarked, with some friends from a french forum that we all succeed to use KIES in a virtual machine and connect the phone:
Click for full size - Uploaded with Skitch
That work like a charm.
Then w wanted to flash, then reboot the phone in Download mode ( yellow android at work ) and then there is a big crash telling us that the device is not recognized:
"unable to connect USB device to virtual machine"
Click for full size - Uploaded with Skitch
I would really be pleased to have more info on this issue and if we are only a little group to have this issue.
For info, I am using MacOS Snow Leopard and the trial of parallels desktops 6.
It doesn't work with VMware Fusion either. Must be something to do with the USB interface on Samsung.. I've heard some people have it going on Virtualbox running on Linux - but not Mac.
Works fine on VirtualBox on Ubuntu.
Why don't you give Heimdall a go? Haven't tried it personally, but OS X is in the list of supported OSes
Maybe I found the explanation , thanks to ed link:
Although Heimdall runs on OS X all Galaxy S phones tested thus far contain a bug in the secondary boot loader that prevents the phone registering itself with OS X. This may change if Samsung release an updated secondary boot loader.
Click to expand...
Click to collapse
Maybe there is the same problem.
Does the secondary boot loader has a link with download mode? If yes, that might be the problem!
profete162 said:
Maybe I found the explanation , thanks to ed link:
Maybe there is the same problem.
Does the secondary boot loader has a link with download mode? If yes, that might be the problem!
Click to expand...
Click to collapse
Saw that today too.. .pretty sure its the issue since it affects all parallels, fusion and virtualbox on Mac OSX.
profete162 said:
Maybe I found the explanation , thanks to ed link:
Maybe there is the same problem.
Does the secondary boot loader has a link with download mode? If yes, that might be the problem!
Click to expand...
Click to collapse
Yes, download mode functionality is provided by the secondary boot loader. If you really desperately want to get it working with OS X then you would need to download the source for, modify and install a custom IOUSBFamily.kext that contains a work-around specifically for the Galaxy S.
The only options for we Mac users right now are to find a Windows machine, install boot camp on your Mac (then point your vmware machine to it to save duplicate Windows wasted space), or possibly find a way to boot from an external drive with Windows (like a thumbdrive or livecd if possible).
distortedloop said:
The only options for we Mac users right now are to find a Windows machine, install boot camp on your Mac (then point your vmware machine to it to save duplicate Windows wasted space)
Click to expand...
Click to collapse
Exactly what i have done. And I HATE it :|
I had this same problem, and I just saw this thread after spending hours last night trying to figure out why XP in Parallels stopped recognizing the phone as soon as it went into download mode. So irritating!
it works for me on VMware 7 + WinXP SP3
because my Win7 64bit PC is crazy it won't recognize the phone randomly, twice it bricked my phone doing the Flash on the Host PC
so after setting up my ROM FLASH VMware machine, now i no longer have problem
stupid windows, no time to mess with the system registry to figure out what is the madness with the USB detection
i'm pretty sure you should have no problem as well if you use VMware 6.5
I posted this in the Heimdall thread but thought I should let followers of this thread know also.
I sent Samsung the OS X USB failure log and since then Samsung have informed me that the Froyo update (specifically the Nordic version released October 15) includes a fixed bootloader which should allow the phone to be recognised in OS X. I'm yet to verify this but hopefully this is the case!
Hello XDA!
I Pray for Help
I have a tablet: Teclast X98 Air 3G 32GB C9J8.
- It all started with the fact that when you install Windows 10 I formatted all partitions.
- Windows 10 install. Everything worked well, except for the battery. The battery not charging while working in Windows.
- It was decided to return the Android OS. But it was not there. I was not able to install android through Manufacturing Flash Tool, because the partitions have been deleted.
- For a long time I was looking for ways to solve this problem, but the solution I not found.
- Well, to hell with it with android - I said. But the problem is that while I was looking for a solution to this problem - I created another problem:
Now tablet not booting to Windows 10. After turning immediately goes into the BIOS. And when I try to run the install from a flash - nothing happens.
- I tried to boot from a live usb, but no result.
- I think something happened to the EMMC.
- But there are two workable options: EFI SHEll and WinPE5_TechAdmin_UEFI.
- EFI Shell works, but does not allow to load the installation Windows with usb flash by running and bootia32.efi or bootx64.efi.
- WinPE5_TechAdmin_UEFI: Run the menu with different options:
- Installation
-diskpart
- Acronis
- etc.
Windows installation runs but produces different error types: ACPI_Bios_Error or 0xc0000XXX - winload.efi
Acronis starts, but after entering my tpad hangs.
- Who can recommend?
Hello mate . Any changes? Did you fix it ? I got techlast x98 3g 64 gb fully working maybe i can help you with somethig to take my os to upload on a server . Maybe you can fix it . I have no ideea . Just trying to help
Hi everyone.
Any idea or problem solution?
Nothing happened in the meantime ?
I am in more or less the same situation. So I liked to hear what now is yours.
I am in the same situation as you, i cannot boot from any usb device, i also tried booting from the efi shell but of course i had to same problem as you. At least i still have my android 5.0 rooted that works fine but i would like my windows to also work
I have tried a lot of things but am also nearing a wall and was just about to make a similar thread as you.
Edit: My situation is not exactly the same as you as my windows 8.1 is not working instead of win10... When i try booting into windows 8.1 i instead get a blue screen and get to the recovery options for windows 8.1, but none of the options work. Of course i can use the CMD option but chkdsk and similar commands don't help
Have you tried to flash a custom android rom like mireks?
http://forum.xda-developers.com/showpost.php?p=62823666&postcount=9
With the windows manufacturing tool you can repartition your tablet. Maybe give it a try
Crazy_Oni said:
Have you tried to flash a custom android rom like mireks?
http://forum.xda-developers.com/showpost.php?p=62823666&postcount=9
With the windows manufacturing tool you can repartition your tablet. Maybe give it a try
Click to expand...
Click to collapse
My android is already running Mireks Rom Rooted. I'll guess i have to repartition indeed, i'll do this today and let you guys know tomorrow.
trylone said:
My android is already running Mireks Rom Rooted. I'll guess i have to repartition indeed, i'll do this today and let you guys know tomorrow.
Click to expand...
Click to collapse
And what happend? did it work?
Crazy_Oni said:
And what happend? did it work?
Click to expand...
Click to collapse
Sorry i was a little busy and lazy >.< .. I've set a notification in my phone and will be sure to do it tomorrow, now i'm going to bed reading novels on my teclast :3
Hey guys,
my x98 Air III will arrive in the next couple of days and I plan to run Windows 10 on it. i got the 32GB Android only version and hope since there is a 64GB dual boot version that the bios isn't locked and I can boot from USB. Has anyone tried this already?
mrchrister said:
Hey guys,
my x98 Air III will arrive in the next couple of days and I plan to run Windows 10 on it. i got the 32GB Android only version and hope since there is a 64GB dual boot version that the bios isn't locked and I can boot from USB. Has anyone tried this already?
Click to expand...
Click to collapse
http://techtablets.com/2015/09/teclast-x98-air-iii-gets-dual-boot-bios-and-files-released/
i want to give it a try but i'm a bit scared i mess up my shiny new tablet...
i found some more info and it looks like it should be possible to turn my tablet into a dual booting device. The 32GB version that I have is M5C5
http://bbs.teclast.com/thread-518225-1-1.html
i just connected a powerd hub and put teclast win10 on an external usb stick. i interrupted the boot by hitting esc on boot, tried to launch from usb, but it didnt work..
Ordered mine yesterday. My plan is also to put Win10 on it, so I'm collecting info/files on how to do it. Maybe Chris from TechTablets will make a video of the process before mine arrives?
he just released a review: http://techtablets.com/2015/11/teclast-x98-air-iii-review/
I've managed to install the dual boot bios on my Air III, but couldnt figure out why flashing was failing. Every time it would go to 10% and fail (when using that Intel's flash tool).
So how did you make it work? Could you post some instructions?
I was succeeded flashing dual boot bios,
and re flashing android 10G patition .
however, I cant boot windows to install it.
dual booting mod didn see windows logo.
I trid to make a booting USB, winpe USB.
didn work out.
zukera said:
I was succeeded flashing dual boot bios,
and re flashing android 10G patition .
however, I cant boot windows to install it.
dual booting mod didn see windows logo.
I trid to make a booting USB, winpe USB.
didn work out.
Click to expand...
Click to collapse
Im at that stage now as well. I couldnt flash the rom automatically so I had to manually input the fastboot commands. Got few things to try in regards of delpoying Windows on it, but that will have to wait until I get home though.
I will put together a guide once I manage to get Windows working, hopefully sooner rather than later
arczi19 said:
Im at that stage now as well. I couldnt flash the rom automatically so I had to manually input the fastboot commands. Got few things to try in regards of delpoying Windows on it, but that will have to wait until I get home though.
I will put together a guide once I manage to get Windows working, hopefully sooner rather than later
Click to expand...
Click to collapse
thank for ur reply
I was installed windows 10, today.
I tried orignal teclast x98 air III dual files to install it.
it works.
zukera said:
thank for ur reply
I was installed windows 10, today.
I tried orignal teclast x98 air III dual files to install it.
it works.
Click to expand...
Click to collapse
How did you manage to install Windows? Can you provide links to files needed to install it?
I'm pretty happy with Android right now, but I wonder if the UI response is more snappy under W10. I already have a USB prepared with the Teclast W10 version. Just waiting for instructions on how to flash bios etc..
I have done a clean Windows 10 Home 32bit (TH2 1511) install and use the driver package from HERE.
All works fine yet but i know one issue with screen brightness:
When i tap the brightness icon (with 25-100%) there came a point with 0% brightness and i tick it and the screen was off and no chance to find the right button without screen
I restart the tab with 15sec. power button but after the short welcome screen, the screen goes back to dark.
So i must use a keyboard and start the tab in rescue modus and set the power managment to "standard". After this the screen was on after next restart.
My question: is it possible to delete the 0% entry in screen brightness?
zukera said:
I was succeeded flashing dual boot bios,
and re flashing android 10G patition .
however, I cant boot windows to install it.
dual booting mod didn see windows logo.
I trid to make a booting USB, winpe USB.
didn work out.
Click to expand...
Click to collapse
How did you manage update BIOS? Did you flash it from Windows PC with USB Debugging enabled or from EFI Shell? My Windows desk cannot find Air III, it says 'no devices found'.
I have managed to put windows on it, by downloading all the files directly from Teclast forums. However, windows is in Chinese and I cant seem to change the language to anything else. Everytime I download a new language, it fails without oving me a reason any suggestions what to do?
arczi:
if you let me know how you flashed the bios and which files you used for the install, i will put it on my tablet as well and we can figure it out together
arczi19 said:
I have managed to put windows on it, by downloading all the files directly from Teclast forums. However, windows is in Chinese and I cant seem to change the language to anything else. Everytime I download a new language, it fails without oving me a reason any suggestions what to do?
Click to expand...
Click to collapse
Download it it directly from the Microsoft with the ISO file in the language of your choice. :angel:
Mikha777 said:
Download it it directly from the Microsoft with the ISO file in the language of your choice. :angel:
Click to expand...
Click to collapse
Thanks, did that and all is fine now. Only trouble was none of the drivers were included in the official ISO files, so I had to manually install a lot of things. The file that can be downloaded directly from teclast is optimized and preconfigured with all the drivers that are needed.
mrchrister said:
arczi:
if you let me know how you flashed the bios and which files you used for the install, i will put it on my tablet as well and we can figure it out together
Click to expand...
Click to collapse
First of all get this: http://pan.baidu.com/s/1kTyAH2f
Secondly, follow this tutorial to install all necessary drivers and tools: http://forum.xda-developers.com/showpost.php?p=62823535&postcount=5
Thirdly, manually edit "Update_Android.bat" file (comes with a package that you have downloaded as the first step) to make sure that all file paths are correct - most importantly the 4th line of this wile, where it points to Intel Manufacturing Flash Tool. Also make sure that there are no Chinese characters in any of the file paths.
Lastly, run "Update_Android.bat" and follow the instructions there I've found that unless you get everything right (all file paths and tool) there isnt much risk of something going wrong, as nothing will actually happen.
thanks for the info! just installing windows 10 on my m5c5 32gb air iii right now, seems to work bios flash was easy and painless. after flashing it took a while for the tablet to power back on. it also didnt see my win10 install usb stick at first. after a few trial and error attempts it eventually booted into windows install.
I'm installing stock windows. which drivers did you use to get the tablet fully working? right now I'm getting the July 2015 Air 3g Windows 10 drivers from techtablets
I have used the same package, majority of drivers can be downloaded using Windows, but there are some missing and thats where the package comes in useful.
I've inserted my pen drive with Win10, and a keyboard, onto a hub with the OTG cable that came with the tablet. I opened the BIOS with Esc, booted from the pen drive. It was stuck with the teclast chinese letters logo for about 2-3mins before displaying a Windows error message / blue screen with a face and the following error code: ACPI_BIOS_ERROR. I turned it off by pressing the power button for 8 seconds, then tried to boot again. Nothing. Zero. No reaction. I've plugged it into the charger and it's still dead. What the actual hell? What have I done that I can't even power the tablet on? I hope I didn't hardbrick it.... What happened and what can I do?
EDIT: I mean what the actual hell I bought a tablet, I boot from a pen drive, and it goes dead?? Doesn't even power on even when I plug it into the wall?? Guys what the f**, what happened? I'm freaking out a bit.
EDIT 2: I completely forgot: the tablet is an Air III (m5c5). Thanks for any help!
Sounds like you tried to boot from a x64 edition image and hardbricked the device.
cscz23 said:
Sounds like you tried to boot from a x64 edition image and hardbricked the device.
Click to expand...
Click to collapse
Okay, so what do I do now? How do I recover it?
Your BIOS has been corrupted as you've tried to boot an x64 image from an x86 EFI.
You'll have to replace/reprogram the BIOS chip on your device to unbrick.
cscz23 said:
Your BIOS has been corrupted as you've tried to boot an x64 image from an x86 EFI.
You'll have to replace/reprogram the BIOS chip on your device to unbrick.
Click to expand...
Click to collapse
Well, I didn't know that merely attempting to boot a x64 image hardbricked the tablet... :S Anyways, thanks. Do you have any guide on how to do that? I assume you need an EEPROM programmer, right? Also any guides on how to open up the tablet? Thanks.
Isn't there any other way to do it, that doesn't involve opening the tablet and buying a reprogrammer?
andrepd said:
Well, I didn't know that merely attempting to boot a x64 image hardbricked the tablet... :S Anyways, thanks. Do you have any guide on how to do that? I assume you need an EEPROM programmer, right? Also any guides on how to open up the tablet? Thanks.
Isn't there any other way to do it, that doesn't involve opening the tablet and buying a reprogrammer?
Click to expand...
Click to collapse
you can buy a ch341a on ebay or use an arduino or raspberry pi if you have one of those to reprogram the bios. The three of them will work. If you want the easiest method, go for the ch341a
iscle said:
you can buy a ch341a on ebay or use an arduino or raspberry pi if you have one of those to reprogram the bios. The three of them will work. If you want the easiest method, go for the ch341a
Click to expand...
Click to collapse
I have a raspberry pi. But apparently it works at 3.3V while the BIOS chip works at 1.8V. Is this a problem?
andrepd said:
I have a raspberry pi. But apparently it works at 3.3V while the BIOS chip works at 1.8V. Is this a problem?
Click to expand...
Click to collapse
no, it shouldn't be. the ch341a works on 3v3 also and it has worked for everybody. I think in XDA there is a tutorial for using the rpi as a bios flasher for the teclast.
iscle said:
no, it shouldn't be. the ch341a works on 3v3 also and it has worked for everybody. I think in XDA there is a tutorial for using the rpi as a bios flasher for the teclast.
Click to expand...
Click to collapse
There is, but someone was mentioning on that thread that the rpi GPIO working at 3.3V was a problem, that's why I asked just to make sure. Thanks!
andrepd said:
There is, but someone was mentioning on that thread that the rpi GPIO working at 3.3V was a problem, that's why I asked just to make sure. Thanks!
Click to expand...
Click to collapse
try it and tell us how it went!
Hey everybody,
I do own a X98 Air III (M5C5) and after long hours of reading on xda I am wondering if there is a single documented case of succesful installation of a dualbooting system on the M5C5 model. Most seem to fail at flashing Mireks ROM in the first place. The lack of clear, concise instructions looks to me as if there is no safe way of flashing this particular model right now. Does this sound right to you or is there something I overlooked?
Thanks a lot!
cubeikon said:
Hey everybody,
I do own a X98 Air III (M5C5) and after long hours of reading on xda I am wondering if there is a single documented case of succesful installation of a dualbooting system on the M5C5 model. Most seem to fail at flashing Mireks ROM in the first place. The lack of clear, concise instructions looks to me as if there is no safe way of flashing this particular model right now. Does this sound right to you or is there something I overlooked?
Thanks a lot!
Click to expand...
Click to collapse
I have successfully installed the dual boot v1.00 after a softbrick trying to install the 2.02 bios. I think the issue is that your tablet is not rooted, that is why you cant flash android. Look @ the ionioni tool to unbrick soft-bricked tabs on how to flash that dualboot bios. Keep reading you will get there
cubal1br3 said:
I have successfully installed the dual boot v1.00 after a softbrick trying to install the 2.02 bios. I think the issue is that your tablet is not rooted, that is why you cant flash android. Look @ the ionioni tool to unbrick soft-bricked tabs on how to flash that dualboot bios. Keep reading you will get there
Click to expand...
Click to collapse
Well, you flashed the BIOS and - as I was stating - first of all softbricked your device, due to lack of proper instructions. There is absolutely no comprehensible information on how to correctly flash or modify this model of the X98 Air III on these forums right now.
Also: did you simply install the 1.00 dualbooting BIOS or did you succesfully install both Andriod AND Windows at the same time? I guess flashing the BIOS can be achieved but again: theres no information on how to properly install Windows & Android on the M5C5. Anf if there's people like you out there who've done it, I don't understand why nobody bothered to document their process and share it with everyone..
Thanks!
cubeikon said:
Well, you flashed the BIOS and - as I was stating - first of all softbricked your device, due to lack of proper instructions. There is absolutely no comprehensible information on how to correctly flash or modify this model of the X98 Air III on these forums right now.
Also: did you simply install the 1.00 dualbooting BIOS or did you succesfully install both Andriod AND Windows at the same time? I guess flashing the BIOS can be achieved but again: theres no information on how to properly install Windows & Android on the M5C5. Anf if there's people like you out there who've done it, I don't understand why nobody bothered to document their process and share it with everyone..
Thanks!
Click to expand...
Click to collapse
Installing Windows and Android is the easy part, once you get the dual bios working. Look at this page (http://forum.xda-developers.com/x98-air/help/unbrick-bios-softbrick-withouth-eeprom-t3285054) to find the files and how to flash them. The only duil bios avaliable is that v1.00. When you successfully flashed that you can install android in dnx mode with partiotion tables with less than full partition size (I personally used the 3gb partiotion, you can find it in mirek190 roms) and than you just attach a otg hub with a bootable flash drive with windows 10 32 bit(never go for 64bit - you will brick), boot in bios by holding Esc on your keyboard (that you also have connected to the hub, as well as a mouse btw), than select the boot drive (you can find a tutorial @ Techtablets youtube page).
I have swapped between the v1.00 dual boot bios and the 2.05 android only bios a few times, and it works fine. Read all the posts in the page above to better understand how dual boot works.
Good luck!
cubal1br3 said:
Installing Windows and Android is the easy part, once you get the dual bios working. Look at this page (http://forum.xda-developers.com/x98-air/help/unbrick-bios-softbrick-withouth-eeprom-t3285054) to find the files and how to flash them. The only duil bios avaliable is that v1.00. When you successfully flashed that you can install android in dnx mode with partiotion tables with less than full partition size (I personally used the 3gb partiotion, you can find it in mirek190 roms) and than you just attach a otg hub with a bootable flash drive with windows 10 32 bit(never go for 64bit - you will brick), boot in bios by holding Esc on your keyboard (that you also have connected to the hub, as well as a mouse btw), than select the boot drive (you can find a tutorial @ Techtablets youtube page).
I have swapped between the v1.00 dual boot bios and the 2.05 android only bios a few times, and it works fine. Read all the posts in the page above to better understand how dual boot works.
Good luck!
Click to expand...
Click to collapse
Hi, thanks for detailing things a bit. :good: Is there any major disadvantage to using the dualbooting 1.00 BIOS as opposed to 2.5? Missing features? Other relates quirks with the 1.00 BIOS? I was wondering since you swapped back and forth with both versions.
Thanks!
cubeikon said:
Hi, thanks for detailing things a bit. :good: Is there any major disadvantage to using the dualbooting 1.00 BIOS as opposed to 2.5? Missing features? Other relates quirks with the 1.00 BIOS? I was wondering since you swapped back and forth with both versions.
Thanks!
Click to expand...
Click to collapse
Hi, there a few problems with the 1.00 dual boot bios and I think its because it wasn't meant to be used with the M5C5, our version of Air III is supposed to be Android only and we are basically hijacking the bios from c6j8, that works but its not perfect (at least for me). The main issues I have encountered is not really with any of the device capabilities - the cameras, wifi, hdmi and everything else works as good as it was intended but sometimes I run in to troubles when switching on the device. When I let the battery run out I will not be able to turn the devise on until it is charged up to 40% (that takes around 45 min) that can lead up to a few minor heart attacks the first couple of times you encounter that. The way I deal with that issue is by never letting the battery run lower than 20% so its not a problem for me but if you use your tablets in such a way that they run out of juice constantly I would suggest you just stick with the android only bios - the one you currently have or the 2.05 version (you might already have that on your device).
Now the advantages of dual boot are many - I believe Windows is a superior OS, in the way that it gives me a lot more productivity and multitasking capabilities that I personalty enjoy. For some reason the volume goes a lot louder on Windows than on any Android rom I have tried. I do believe we should get the most out of our devices and that's why I stick with dual boot for now. It is far form a perfect solution but everyone that reads this should evaluate the pros and cons - if you don't mind the stress of not being able to turn on your devise for 45 min or so you might enjoy the dual boot (or might be able to find a better dual boot bios).
As a conclusion experiences with Chinese tablets always vary from one to the other and it might be just my unit that is faulty (the boot up issue) so all you do is at your own risk, but if you keep on reading and trying out solutions you can get a lot of stuff working (just remember to breath)
cubal1br3 said:
Hi, there a few problems with the 1.00 dual boot bios and I think its because it wasn't meant to be used with the M5C5, our version of Air III is supposed to be Android only and we are basically hijacking the bios from c6j8, that works but its not perfect (at least for me). The main issues I have encountered is not really with any of the device capabilities - the cameras, wifi, hdmi and everything else works as good as it was intended but sometimes I run in to troubles when switching on the device. When I let the battery run out I will not be able to turn the devise on until it is charged up to 40% (that takes around 45 min) that can lead up to a few minor heart attacks the first couple of times you encounter that. The way I deal with that issue is by never letting the battery run lower than 20% so its not a problem for me but if you use your tablets in such a way that they run out of juice constantly I would suggest you just stick with the android only bios - the one you currently have or the 2.05 version (you might already have that on your device).
Now the advantages of dual boot are many - I believe Windows is a superior OS, in the way that it gives me a lot more productivity and multitasking capabilities that I personalty enjoy. For some reason the volume goes a lot louder on Windows than on any Android rom I have tried. I do believe we should get the most out of our devices and that's why I stick with dual boot for now. It is far form a perfect solution but everyone that reads this should evaluate the pros and cons - if you don't mind the stress of not being able to turn on your devise for 45 min or so you might enjoy the dual boot (or might be able to find a better dual boot bios).
As a conclusion experiences with Chinese tablets always vary from one to the other and it might be just my unit that is faulty (the boot up issue) so all you do is at your own risk, but if you keep on reading and trying out solutions you can get a lot of stuff working (just remember to breath)
Click to expand...
Click to collapse
Well that was very helpful. I might consider simply replacing stock android with mirek190 v7.0 at this point. It seems having Windows 10 available is not worth the hassle for me, when it comes to the bootup issues you described. Thanks for clearing things up significantly for me! :laugh:
Is there any proper dualboot bios other than v 1.00 for M5C5?
Hi folks,
I ordered a Air III a week ago and I haven't got my hands on it yet. But from what I found researching the forums is that there's a version of 2.05 bios that's been reported working with the Air III. Refering to the following 2 posts:
http://forum.xda-developers.com/x98...m-bios-x98-air-iii-32gb-t3310436#post65204355
Then I downloaded X98_Air_2_android_5.0_mirek190_v7.0-ultra-light, replaced /data/BIOS/2-05.bin with the one from the above mentioned link (https://mega.nz/#!dYxVTQrL!J9h-bk-hW...8TF6XXr-JwpgdU). Then I launched FLASH_tool_Teclast_x98_air_devices-v3.0, hit 4, then hit 2 and select 2.05. It updated the M5C5 to the most recent BIOS. You can tell because the tablet doesnt start up displaying chinese letters anymore but instead showing the latin letters TECLAST
If you want to keep your Windows installation I believe you have to change partition.tbl but not sure how this would work . I'm Android only now.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=65166671&postcount=87
DONE!
It's true the first boot logo is about BIOS. I made backup and flash it by mirek tool
Here you can find it: https://mega.nz/#!dYxVTQrL!J9h-bk-hW...8TF6XXr-JwpgdU
Just replace this file in \X98_Air_2_android_5.0_mirek190_v7.0\data\BIOS and run flash version 2.05
Click to expand...
Click to collapse
The only I'm not sure is if I have to (or can) flash Mirek rom using MFT BEFORE flashing the bios so it's pre-rooted.
Can anybody confirm this (@mrchrister ?) and also if you need the tablet to be rooted?
Thanks