yashsingh1/xdaforums huggingface dataset:
[Windows 8 Development and Hacking] robif:
I installed a new program on my T100TA. When I restarted it would not boot. Wants to recover. Recovery does not work either. Maybe it is a problem with the drive, maybe not.

I am ready to reinstall Windows or alternatively UBUNTU. In the BIOS there is no way to change boot sequence to boot from USB. I tried everything. The only thing that worked is if I create a USB of Windows 10 using RUFUS and UEFI, after disabling secure boot. I could probably do this for UBUNTU as well.

This USB loads automatically and I started the reload process. When it reached the disk allocation step it said it could not use the present allocations. I was afraid to wipe the disk and proceed.

My question is: Should I wipe the disk and proceed? Would it work? Would I be better off using UBUNTU? Is there a way to fix the BIOS so I can boot from USB? Is there a way to determine if my disk is bad (remember nothing is running now)? There is no Factory Recovery on the disk anymore.

Any help would be much appreciated.
[Windows 8 Development and Hacking] robif:
I managed to do a Factory Reset to Windows 8.1. Since 8.1 is no longer supported the store is not available.

The only problem is that there is no File Explorer so I really cannot do anything.

Internet Explorer 11 does not work either.

Anybody has a suggestion?
[Windows 8 Development and Hacking] robif:
I managed to complete the recovery to 8.1 and everything is working well except the HDMI connection to a TV. It actually connects to the TV, it shows that both are connected, however the second screen (i.e. the TV) remains black. I have the latest Intel driver installed and the resolution (1360X768) is the same where I can connect my other la[top to the TV.

Anybody has any suggestion?
[Windows 8 Development and Hacking] AdamWill:
Cool. I'm working with a couple of kernel folks ATM to get past the crasher bug I'm hitting in the kernel, which I _think_ wouldn't be limited to the V8P but would likely hit other Bay Trail systems too. If I can get something which gets further than that I'll send it over to you to try as well.

20 Alpha is pretty old at this point, I'm building from the latest stuff in the 20 repos plus kernels from rawhide.
[Windows 8 Development and Hacking] paperWastage:
lspci / lsusb doesn't show any wifi/sound hardware for asus T100 either... (sound still doesn't work yet, wifi works with a broadcom sdio kernel driver)

going to hunt around for more documentation on Bay Trail SoC... maybe something different/unique for the sound problem.

it's final year rush @ work, haven't had chance to play with my t100 these past days
[Windows 8 Development and Hacking] Sacob:
will android-ia project work in this tablet?
[Windows 8 Development and Hacking] SixSixSevenSeven:
Probably not right now, in future perhaps
[Windows 8 Development and Hacking] Sacob:
do you know if there's someone trying to get this to work? i mean android and ubuntu.. or do we have to forget the idea of having a stable versions of this OSs
[Windows 8 Development and Hacking] SixSixSevenSeven:
Whats the entire thread for? People trying to get alternate operating systems working.
[Windows 8 Development and Hacking] pastime1971:
great. i will be joining you soon.

on a side note, you name sounded familiar. then i realized that i was following you on poulsbo driver. (i still have acer aspire one netbook atom Z520 processor. in fact i bought T100 to replace that.)
[Windows 8 Development and Hacking] AdamWill:
Yeah, I'm a sucker for awkward hardware :/ I gave up on Poulsbo in the end, sold that system and bought a snowboard instead. :P
[Windows 8 Development and Hacking] lufasponge:
If you find any good resources for bay trail sound, please post a link.
[Windows 8 Development and Hacking] jesmon:
I have built AndroidIA from source with 32bit uefi support. I have managed to get it to boot to the android ia boot options menu (run android ia live, install etc.) but then I get an error saying unsupported EFI handover protocol when I try to select one.

I will try and compile again with different options but it may be beyond my skill level to solve.
[Windows 8 Development and Hacking] Sacob:
that's great! please keep me updated!
[Windows 8 Development and Hacking] AdamWill:
Update on my Fedora pokings: https://bugs.freedesktop.org/show_bug.cgi?id=71051 may well be the fix needed for modesetting on 3.13, but I haven't tested yet, I have a build running with it now. A simple hack to disable some non-essential code (suggested by matthew garrett) got 3.13 booting successfully on my V8P with nomodeset: https://bugzilla.kernel.org/show_bug.cgi?id=65841#c17 , and the touchscreen works out of the box with 3.13.

I'm building a kernel with the possible display fix and a few other tweaks ATM and will see if that boots with modesetting. If so I'll see whether I can get the wireless going, and if I could, then it'd be in workable state. Still other stuff to try and get working, but it'd be usable at that point.
[Windows 8 Development and Hacking] iAppleDev:
OSX from grub2
[Windows 8 Development and Hacking] sqalg:
Hello

Thanks for your feedback.

Did you try to install Android on this computer with the binaries provided by the Intel Project ?

https://01.org/android-ia/
[Windows 8 Development and Hacking] paperWastage:
no, because android-ia only had the 64-bit bootloader... was going to recompile, but the other guy a few posts above had problems too
[Windows 8 Development and Hacking] williambs:
Can anyone tell me how to reimage my Asus T100 32bit windows 8.1 to windows 8.1 pro 32bit?
[Windows 8 Development and Hacking] SixSixSevenSeven:
You dont need to reimage, you can purchase and download the pro upgrade from the microsoft site and apply it to the device directly.
[Windows 8 Development and Hacking] williambs:
I did that and it worked, thanks :)
[Windows 8 Development and Hacking] williambs:
Still not able to upgrade to Pro

After the key activated it deactivated and I was forced to send my tablet back to ASUS to be reimaged. Is there a better way to create an image from a pro version that uses a volume key or even another option that works?

Thanks in advance.
[Windows 8 Development and Hacking] jhbhacker:
Win 7 32bit

Has anyone managed to load Windows 7 32-bit in either a dual boot or single configuration on the T100TA?
[Windows 8 Development and Hacking] rodion.zissou:
Let's get back on topic with the Android build for our T100!

Exclamation for excitement, not pushiness.
[Windows 8 Development and Hacking] costcutter:
Android on the ASUS T100 would be amazing
[Windows 8 Development and Hacking] rodion.zissou:
It seems to be getting there. Android can run on x86 architecture, it's been done, it just needs to be optimized.
[Windows 8 Development and Hacking] KILLplay:
No x86 UEFI bootloader can't be too bad of a limitation. I'm trying to research it. was there a thread?
[Windows 8 Development and Hacking] zombie673:
A little incentive...

With the market flooding with the T100TA, I'm sure that there are going to be a lot of people looking for mods here. I'm throwing $20 to whoever figures out the kinks and gets a viable version of Android working on this machine. I have android tablets and just got the T100. I don't want to need both. We all know the benefits of both OSs and I think that dual booting this model would be make it the ultimate mobile computing tool, especially with x86 dropping their 4.4 release now. Keep up the development guys!!

Also, if anyone is looking for a fitted case, they're now available on ebay for about $20.
[Windows 8 Development and Hacking] tydem:
There are a few viable x86 EFI bootloaders for our device. Making the T100 dual boot Windows and (desktop) Linux is pretty easy if you install rEFInd onto the EFI partition, and from there you can boot anything including Windows, Linux kernels, and other bootloaders like GRUB2. Sadly rEFInd has a bug (that causes module version mismatch) with 3.13 kernels so booting directly with it is not recommended, it is better to just use it as a main menu and chain grub2 from there.

I tried Arch, openSUSE 13.1 and Kubuntu 14.04 (daily snapshot) and out of those, only Ubuntu and its derivatives recognize the touchscreen. SUSE has issues with the wireless, even after applying a custom kernel with the required modules and firmware. Also, since space is very limited on my 32GB model, with Windows giving me some 4,5 GB after shrinking, I installed Kubuntu into a compressed btrfs partition and placed GRUB and rEFInd on the EFI partition. Then I grabbed the 3.13 rc3 kernel debs from the mainline kernel repo and installed them. Amusingly, the pre-alpha Kubuntu 14.04 is far more stable than Windows 8.1 on this device, however there are a lot of missing drivers. All distributions I tested were 32-bit versions. Here's a list of missing or partially missing hardware features:

Partially working:

Display: efifb works fine if you uninstall the xorg vesa drivers, but is really slow on 3.12 kernels. On 3.13 it's much better, but still nowhere near smooth as it has no GPU acceleration at all. The modesetting driver, i915, does not work on either kernel. On 3.12 it shows a corrupted screen with a flickering bottom part and on 3.13 rc3/rc4 it just shows a blank screen upon setting the kernel graphics mode. So nomodeset is needed to boot correctly as of now.

Wireless: The brcmfmac driver works, but has very poor connection quality, to the extent that NetworkManager always fails to connect with it. With Wicd it is usable, provided the required firmware and nvram are present. (Thanks to lufasponge for providing instructions in this thread)

Touchpad: While the touchpad works, it is recognized as a basic mouse and lacks gesture support.

Not working:

Audio

Backlight control

Suspend to RAM (sleep)

Shutdown and reboot (it just hangs and you need to hold power to shut it down)

SD card reader

Camera

Battery level reporting

Orientation sensor

...and some I might have forgotten.

So to sum it all up the Linux support on this device is really basic, and it is nowhere near ready to be a daily driver. I hope someone can get modesetting on 3.13 to work as I have tried everything and all I got was the choice between a black screen or a garbled one. I will also see if I can get linux-next (the bleeding edge kernel from git) to build and then check if more features work.
[Windows 8 Development and Hacking] nemuro:
Now charging my t100 before first time use.

Glad to see someone is on track to a working android version on this wonderful device. Good job guys!
[Windows 8 Development and Hacking] sqalg:
hello

no more news of this android version ?
[Windows 8 Development and Hacking] SixSixSevenSeven:
People may still be busy pigging out on mince pies rather than working on android :P
[Windows 8 Development and Hacking] TheMoro:
The i915 GPU driver does work fine *almost* out of the box for the 3.12 kernels. I havn't tested 3.13 yet, but the problem may be similar. The garbled screen is simply due to an incorrect resolution. It doesn't seem to detect our native resolution right. Using the boot parameter video=VGA-1:1366x768 works, at least when I tested it on Arch. For Ubuntu, the same boot parameter worked, but only for the console.The X session was still bad. From there I had to use xrandr to create a new video mode, and somehow manage to use the (still garbled) screen to access a terminal window. It worked, but I wouldn't recommend it ;) You might also be able to setup an Xorg config to set the resolution on startup.

Just letting folks know, the GPU works at least in 3.12 kernels.
[Windows 8 Development and Hacking] zombie673:
So I just went back and read the entire thread. I am an experienced user of Windows and Android and have done a fair amount of tweaking, modding, and rooting and I can honestly say that I am ashamed to have thought I knew ANYTHING about modern mobile computing. Can someone take a minute to put into simpler terms what we are looking at or where things stand for getting a dual boot of android on our machines? It makes me feel like a complete noob to be this lost.

Thanks guys!
[Windows 8 Development and Hacking] paperWastage:
(this below applies for any operating system that you try to put onto the Asus T100)

You need a 32-bit EFI bootloader

You need GPU driver for GPU-accelerated graphics

for basic linux distros, (1) means you need to compile grub2 in 32-bit EFI mode (or whatever your distro uses)

(2) - intel has GPU driver (i915), but it's buggy (as TheMoro mentioned two posts above this one)

for android, we have android-ia and android-x86 distros

(1) is tough, because compiling android is slightly more complicated than playing with ubuntu

(2) android-x86 has i915 support, but dunno if the latest is merged into the android-x86 codebase. right now, buggy as well

I haven't played with my t100 in december... maybe I'll find time this weekend
[Windows 8 Development and Hacking] devkon:
paperwastage please tell me what i have to do in bcdedit to boot ubuntu 13.10,

i have installed it on internal emmc, installed grub on mmcp2 but nothing work on boot i have an error

with my bcd config.

thanks in advance
[Windows 8 Development and Hacking] paperWastage:
copy pasty from a post I made somewhere else
[Windows 8 Development and Hacking] devkon:
thanks it worked
[Windows 8 Development and Hacking] paperWastage:
PM from olymk2 who doesn't have post access to this thread yet
[Windows 8 Development and Hacking] julyaann:
Here I am biting my nails waiting for the king :D... paperwastage magician do magic and can enjoy our t100 Android dualboot ...

Thanks a lot
[Windows 8 Development and Hacking] Husky997:
Anyone try dualboot or make a Android distro, It is possible or not. And maybe who's try Rom Image from Z27xx smartphones?

Win8.1 killing Android tablets if have a dualboot. Toshiba Encore and T100:)

BTW Maybe ASUS Transformer Book Trio Image works on T100?
[Windows 8 Development and Hacking] sarman_1998:
Boot android-x86 with one thumb drive

First thanks to everyone on this thread! I've been working hard to get android running on this think and all the info here is very helpful!

Here are a few thinks i've found

I figured out how to boot to android with just one drive instead of two.

Short version is, make a second partition on your thumb drive about 300mb ext4. i used a gparted live image to shrink the existing partition and add this new ext4 partition. For me it was /dev/sde2

Next do the step you used to do on the second drive

dd if=android-x86.iso of=/dev/sde2 (be sure to use the correct partition in your case. parted -l should get you a list to guess from)

I know at least parly why the install won't work. I was looking at the scripts under bootable/newinstaller in the source tree and i found when its searching for drives to install on, it is looking for /dev/sda* or /dev/hda*. On the T100, the storage is /dev/mmcblk0p*. I started changed scripts in there but that was a tangent from my main effort so I'm leaving it alone for now.

I've got the i915 graphics driver loading and partly working. It works when i'm still in text mode, but when i start the android graphics up, it switches from 1368x768 to 1024x768 then i just get a blank screen. I'm trying to trace that down now. Currently it looks like gralloc/kms is not passing the native resolution mode.

Eric
[Windows 8 Development and Hacking] simkad:
I've no knowledge about development on windows/android. This is my first win8.1 tablet/laptop.

Thanks for all the effort for bringing android dualboot for t100. Keep up ur good works guys..
[Windows 8 Development and Hacking] Sacob:
good luck! we hope to hear some good news soon :)
[Windows 8 Development and Hacking] sarman_1998:
Android good news and bad

Well, after a few more very late nights, i was able to get to the android main screen, once. Unfortunately, its completely unrepeatable. After a lot of looking around, I think the main problem is that the drivers for the graphics that are in android-x86 are just not new enough. I did find here, repositories for the latest intel graphics driver sources. https://01.org/linuxgraphics/community?qt-projects_aggregated_links=2.

However, I talked to a friend at Intel who works on android and according to him, Intel is going to be releasing a public beta for android on Bay Trail in the next 3 weeks. So I'm going to wait for that before I try again.

If anyone wants to work on it before then, the main change I made to get the i915 driver to at least load and work for text console was in kernel/driver/gpu/drm/i915/i915_drv.c.

around line 118, change

unsigned int i915_preliminary_hw_support __read_mostly = 0;
to
unsigned int i915_preliminary_hw_support __read_mostly = [B]1[/B];

I couldn't find another way to change this besides changing the source.

Here is a pic of the one time i got to the main android screen.
[Windows 8 Development and Hacking] Sacob:
that's great news! thank you for sharing
[Windows 8 Development and Hacking] imapirate:
Just finished reading all pages of thread. Would I encounter the same difficulty on my Asus Vivotab 810c (Full windows 8.1) as is being produced on Asus t100? Thank you, subscribed.
[Windows 8 Development and Hacking] SixSixSevenSeven:
More difficulty as the clovertrail cpu in the 810c is totally locked
[Windows 8 Development and Hacking] TheMoro:
I would think you would run into a completely different set of problems as we face with the T100. There isn't much wrong the the CPU on the T100 PER SE, that actually works alright! its just about everything else we've had trouble with.

We've had issues with (IMO in order of importance):

- The bootloader/EFI system. This will vary from device to device, and you may or may not have problems on another device.

- The Graphics card. The Baytrail processors are completely different in this regard to clovertrail.

- The Wifi chip. You will most likely have a completely different chip on another device, that may, or may not work well under linux.

- Just about ALL power management features (Suspend, backlight, shutdown, etc). The main problem here is the Device Specific implementation of things. yet again, you will find something totally different on any other device, baytrail or not.

- All the other hardware features like bluetooth, accelerametre, sd card, etc. Not sure if anyone has tried the camera yet? I seem to be repeating myself a lot here, but, This is going to be totally different for any other device.

Sadly with the t100, we happen to just get a really sucky combination of stuff going wrong here :P

Ontop of any other problems specific to your device, clovertrail CPU's don't have official support from intel for use with anything other than windows. That means that although you may get it to run something, (still being an x86 based CPU), its not going to be anywhere near as efficient, or have all the features you get with windows. Intel has already expressed that they have no interest in releasing linux drivers for clovertrail cpu's. That might bring about a whole new set of problems.

If after reading this, you still feel up to the challenge, congrats and good luck! If you do run into the same problems, you know where to find us! I'm sure there are other people who want the same thing you do and are willing to help.
[Windows 8 Development and Hacking] cold0ero:
Hello all. I just wanted to ask a question to those that own this device and hopefully I can get an answer for something else I'm working on. From my understanding, the device is booting a 32 bit Windows 8.1 in UEFI mode. I'm curious if the disk is setup as a GPT disk or if it is an MBR disk. Also, any information on how the device is actually booting with 32 bit Windows would be most appreciative.

For those that are curious what this project is, I'm attempting to build a nice Windows 2 Go flash drive with a 32 bit install of Windows that could boot from both bios and UEFI. I'd prefer to make the disk GPT if possible and if this system is setup with a GPT disk layout, I'm curious how they achieved it and hopefully I could duplicate the results on my flash drive.

I was able to get my hands on the tablet itself for a few hours and it seems like a very nice machine to play around with. I hope to actually own one soon. If I don't get the answer I need here, maybe I can go to a store and play around with their model for a little bit to get my answers that I seek.

PS, if I get one of these devices, what Linux interface do you all recommend for a touch interface in Linux. I was thinking Gnome 3 might be alright but not sure.

Anywho, happy hacking!
[Windows 8 Development and Hacking] paperWastage:
gpt
[Windows 8 Development and Hacking] cold0ero:
Any idea on how they managed to get a 32 bit version of windows to boot from a GPT disk? I'm guessing that means they designed a 32 bit EFI firmware to allow for it now in Windows 8.1. Does it list a bootable flag of any kind? From my understanding, GPT isn't supposed to use a bootable flag; but if it does, there might be a way to get a bios machine to boot from a GPT scheme that is similar which would assist with my Win 2 Go idea.

And thank you for the answer paperWastage. =)
[Windows 8 Development and Hacking] terminander:
Well I finally got the Dell Venue 8 Pro to boot to a usable Ubuntu 13.10 live image. Following the instructions here it boots in Portrait mode, which is the Dell default. The live image won't let me rotate the screen. l ran the install to a Usb drive, but I'm not having any luck booting it. I'll have to reread theses pages.

Interesting if I boot straight to the live disk, after dumping vesa I get maybe a 800x600 screen, very stretched in portrait mode. If I boot the live usb from Windows, I get a true 800x1280 screen.
[Windows 8 Development and Hacking] diablow:
Lenovo Miix 2 8

I have a tablet with similar specs and limitations (32-bit bootloader) - Lenovo Miix 2 8. After reading this thread I have done some testing on it and here are the results.

Ununtu 13.10

boots up, needs vesa driver removal to boot to graphical desktop. Screen resolution is correct, but fixed to portrait mode. Touchscreen works, but there's no wifi or sound.

Android-x86 4.3

managed to boot up with two partitions on USB, but I get wrong resolution - screen doubled and colors are messed up. Currently found no easy way to fix this.

Trying same boot method on android_x86-4.4.2-userdebug-20140118.iso failed to boot, stuck on command line.

My goal is to have a dual boot Windows/Android installation with minimal interference to default system setup. Also, it should be portable, so USB flash drive boot is out of the question. Would it be possible to boot from SD card? Or even boot from file on Windows filesystem, like was done with Wubi? I found that EasyBCD has an option to boot from raw disk image, but still haven't figured out how to set it up in Windows 8.1.
[Windows 8 Development and Hacking] julyaann:
My goal is to have a dual boot Windows/Android installation with minimal interference to default system setup. Also, it should be portable, so USB flash drive boot is out of the question. Would it be possible to boot from SD card? Or even boot from file on Windows filesystem, like was done with Wubi?

There are a Winapp ( http://xdaforums.com/showthread.php?t=2142563 ) that make exactly this, the problem is that only works if the boot manager is WBootmanager\NTDLR & our toy are build in UEFI :crying:

I don't have knowlegde & probable Im saying silly, but could have some possibility to make a winapp to install android like wubi in our T100?

I have a old PC Dell vistro 1500 & Android works very well on this way.

http://xdaforums.com/showthread.php?t=2142563

Know Issues:

Not Work if GRUB is the default bootloader

EFI Not Supported

Change Log:

Version 1.2:

- Support Windows 2000/XP [waiting for Users Reports]

- Logging Installation Process

Version 1.1: automatically detect if VGA Card require xforcevesa nomodeset, no more android black screen

Version 1.0: initial version

Some Notes:

you can install Android on "USB Disk" or "SD Card"

you can install Android on Windows partition (Drive C: ), no problems at all