[FAQ] Asus T100: Installing custom OS (android/ubuntu/*nix/Windows 7/Windows 8 x64)

Search This thread

tasadar

Senior Member
Sep 11, 2007
134
18
@feherneoh,
Sorry to hear that, I hope you restore it soon. How you do that(using the booting from the free space from c:\ alongside with windows without partitioning ?). Please write it step by step or if it's ok to make small video tutorial !?

Thank you in advance
 

tasadar

Senior Member
Sep 11, 2007
134
18
do we have the tutorial ready ? Don't know how to copy the remix folder to the ESP partition, and probably most of us. Also the Remix on Usb pendrive I am using, sometimes(very rare) loads and most of the times it just goes black screen when selecting Residnt or Guest mode. Why sometime it happens and most of the time it does not load ?
 
Last edited:

tasadar

Senior Member
Sep 11, 2007
134
18
The Remix version from Reddit.com(AndroidOS and Efi folders copied to separate formated fat32 partition) is working no problem from my Hard drive, but the newest one from jide.com is not working which is made with usb tool to Pendrive an then copied the filels to the Remix partition(only show black screen after selecting Resident or Guest modes). Why the first works, but the newer does not, can you tell ? Am I missing something !?
 
Last edited:

Sacob

Senior Member
Jan 8, 2011
918
84
The Remix version from Reddit.com(AndroidOS and Efi folders copied to separate formated fat32 partition) is working no problem from my Hard drive, but the newest one from jide.com is not working which is made with usb tool to Pendrive an then copied the filels to the Remix partition(only show black screen after selecting Resident or Guest modes). Why the first works, but the newer does not, can you tell ? Am I missing something !?

because the version from reggit has a custom EFI that made it possible to boot from 32bits EFI (the case of the t100), the second one only works in a 64bit EFI. Or something like that xD

i think you can make the second one boot if you replace the efi folder content from the ones from reggit
 

tasadar

Senior Member
Sep 11, 2007
134
18
Now the reddit version also stopped working , only black screen after selecting in the boot menu !!! Stupid thing !!!
 

tasadar

Senior Member
Sep 11, 2007
134
18
when I load the OS for the first time it is Ok, but whe I try do start it the second time it goes black screen and have to reset all the procedure(using the reddit version with new release "system sfs" file). I can't make it permanent for booting
 
Last edited:

philcurious

Member
Aug 21, 2008
41
11
I've fixed the login issue, the login wizard is not quite stable yet but it does get the job done and after this you will have a functional device.
I'm rebuilding the images now and will be releasing them including a new tutorial.

Google Play store is working fine, so i'm not including a browser into the image right now as you can install any browser from the Play Store.
More details will be released later.

---------- Post added at 02:25 PM ---------- Previous post was at 01:38 PM ----------

Hello everybody,
my previous image was not fully working, i've been working on a fix for the past few weeks, and i've gotten a solution.

what is new in this image:
- WPS fixed, you should now be able to use WPS without any issue
- Login issue fixed
- Includes a file manager

Link: https://drive.google.com/file/d/0B8jVq7lqQUtvUkFyT0RhR2lJT28/view?usp=sharing
(The image is highly compressed again to save space, I would recommend using 7zip to unzip the image)

Here is the installation tutorial, it is based on the previous one but has some modifications. The old tutorial is outdated, use this one:



Know bugs:
- No camera
- Random force closes when installing a new app from the Play Store, just ignore them they do not affect the working of the tablet.
- No auto-screen rotate.

I think i'm gonna look into the rotation issue for the next release.
Do i let the Android Live boot go all the way through? And how long is "quite some time", because i left it on for about 30 minutes without anything coming up.
 

toniolol

Senior Member
Jul 30, 2007
244
5
46
you can use the 64 bit version, but you need the 32 but GRUB used by stuff like the T100 magic stick
Hi,
I'm sorry but not sure to understand.
You mean I could install 64 bits on internal hard drive (not the one in keyboad) and I need install GRUB 32 from other source ?

Regards
 
Last edited:

toniolol

Senior Member
Jul 30, 2007
244
5
46
I suggest a manual install by using the 64 bit image and grub from magic stick
You only have to replace kernel commandline with remix one
Sent from my D5803 using XDA-Developers mobile app

Thanks for your help.
I tried serveral versions on USB and I want to install the x86-4.4r5 from Android X86.
Do you think I can used the magic stick installer if I replace some files to upgrade MS to 4.4r5 ? It's write experimental do not use on the installer part.
Or this way : https://louislam.net/blog/2015/08/tutorial-installing-a-stable-android-os-on-asus-t100ta/

Regards,
 

toniolol

Senior Member
Jul 30, 2007
244
5
46
Thanks,
I'll try as soon as I'll manage to shrink my C: partition whitch is not available now beacause of strange reason of residentials Windows files that defrag can't move. I'm working on it !
 

toniolol

Senior Member
Jul 30, 2007
244
5
46
I'd like to have dual boot Windows 10 and Android.
All howto I read explain to create another partition.

Envoyé de mon Honor 5X en utilisant tapatalk
 

toniolol

Senior Member
Jul 30, 2007
244
5
46
Thanks feherneoh for this great news !
How do you dual boot on it ? With easyUEFI ?
 

danil74

New member
Oct 30, 2007
1
0
Thank you very much for your answer.
I am still missing something.
Come to boot selection --> andorid --> then came a black screen with multiple choices
Picked the first one , android load smoothing but find the apk in any folder.
I installed all the package in an hard disk partition.
the only files I can see in USB folder are in USB 0 folder ( EFI folder LOST.DIR folder bootsect.bak file)
I transfered the google service apk file with pendrive to t100, checked permissions (0770), checked untrasted source , but I still have error parsing file error , alsot tried to download again the file , no luck
also tried to install other apk files but I had the same error " there was a problem parsing the package"

UPDATE:
I solved the error deleting the data file and and making a new one.
I suppose my error was to pick an ext3 format.
Now is perfect and run flawless great work. thx

Hi,
i've the same problem. After android installation I can't see any apk file.
I can see USB3,2,1,0, but only in 3 i see what you saw in usb (EFI folder LOST.DIR folder bootsect.bak file).
In addition, if I plug in an usb stick, android don't reconize it.
Can you help me?

thanks
Dan
 

jrk190

Senior Member
Sep 4, 2012
1,395
167
McLeansville
My Asus vivotab note 8 has similar hardware and almost everything works on the latest build from android x86.net. Wifi, rotation work, the only things not working are sound, cameras, and turning the screen off. Would the patches for ubuntu work on android?
 

henkpeters

Member
Aug 16, 2011
21
2
...

Until someone is willing it dig into it and make proper patches for ACPI troubles, a unified kernel doesn't seem too likely.

Had this sleep / standby / screen off issue been resolved somewhere yet? I'm running into the problem trying to run both KitKat / Remix . both os really run great besides thuis issue...
 

pierro78

Senior Member
which image fixes the sleep issue ?

Hello,

I tried to install android using android-x86_64-5.1-rc1.img or android-x86-4.4-r3.img with UEFIInstallerv24-5800 extremegtx method but both times my T100TA would not go to sleep (screen and camera light always stay on) :(

Anybody knows if above http://forum.xda-developers.com/showpost.php?p=62279669&postcount=573 domini99 image and method has the sleep issue ????

Or how to fix this "sleep issue" ???

(maybe it s "by design" and it can't really be fixed ?)

Thanks folks for feedback !
 
Last edited:

Top Liked Posts

  • There are no posts matching your filters.
  • 16
    [4 April 2014]I haven't had time to play with my device or update fully the info in this post
    Jhong2 has an updated post on how to get ubuntu working on the Asus T100
    http://forum.xda-developers.com/showpost.php?p=51291244&postcount=181
    http://www.jfwhome.com/2014/03/07/perfect-ubuntu-or-other-linux-on-the-asus-transformer-book-t100/

    (do search for the specific topic headers to jump to them)
    Post 1: Global Info
    UEFI:
    Bootloader auto-detection path:
    Secure Boot
    Partition Table for Live USB sticks:
    How to boot from USB stick
    Info for various operating systems:
    Hardware info:
    /cpu/cpuinfo:

    Post 2: <backup/ archived infomation>

    Post 3: Files
    grub2 2.00-13ubuntu3 (13.04 raring sources) compiled for grub-efi-ia32 (x86) - bootia32​




    ---------------------------------------------------------------------------------------


    Global information
    for BIOS 214 (2013.09.25), version loaded on retail T100 units

    UEFI:

    Bootloader auto-detection path:
    (bootloader is only 32-bit compatible)
    /efi/BOOT/bootia32.efi
    WILL NOT pick up the x64 location /efi/BOOT/bootx64.efi

    Secure Boot

    You should disable Secure Boot in UEFI/Setup-Utility-Menu-> Security tab-> Secure Boot Menu -> Disable


    Partition Table for Live USB sticks:
    GPT or MBR works
    Use Rufus (works for Windows/Unix ISOs) or Windows 7 USB Download Tool (works for Windows 7 / Windows 8)

    How to boot from USB stick

    NOTE:

    If you don't see the USB drive on the boot list or the UEFI/Setup-utility, this means you have a badly prepped USB live drive, or the boot-list/UEFI/Setup-utility was loaded before the USB drive was read.
    If you are on the boot list, boot into UEFI/Setup-utility. Then, go to the last tab, save changes and restart while holding F2 (to force the next reboot to go back into UEFI/Setup-utility). If you still don't see the USB drive after doing this multiple times, then you have a badly prepped USB drive.

    I find using Rufus (GPT for UEFI + FAT + 64 kb+ bootable disk using ISO Image) to consistently get a working bootable USB drive

    Option 1a) Boot to UEFI USB drive from Windows (works only if your USB is correctly prepped)
    1. Boot into Windows
    2. Swipe from right, click on settings.
    3. Click on Power. Press and hold the shift key, and then click on Restart
    4. A Blue menu should show up. Click on Use a device->click on the device name (might not show up if USB isn't prepped properly)
    5. Device should reboot into the USB

    Option 1b) Boot to UEFI/Setup-Utility-menu from Windows (easiest, and almost no way to screw it up)
    1. Boot into Windows
    2. Swipe from right, click on settings.
    3. Click on Power. Press and hold the shift key, and then click on Restart
    4. A Blue menu should show up. Click on Troubleshoot-> Advanced Options-> UEFI Firmware Settings
    5. Inside UEFI/Setup-Utility-menu, go to the last tab, and select the USB Drive

    NOTE:
    For options 2a and 2b, if you see the ASUS logo and circle loading icon, you either:
    • Pressed button (ESCAPE/F2) too late. Solution: Reboot and try again
    • Have Fast startup enabled, and did the steps with the device in shutdown mode. Windows will cache the kernel/other stuff, and you might not be able to get to UEFI. Solution: Reboot from Windows and try again(reboot does not trigger caching). Or disable Fast Startup


    Option 2a) Boot to UEFI/Setup-Utility-menu
    1. Inside Windows, restart system. Press and hold the F2 key
    2. You should get into the Aptio Setup Utility screen
    3. Inside UEFI/Setup-Utility-menu, go to the last tab, and select the USB Drive

    Option 2b) Boot Menu
    1. Inside Windows, restart system. When screen goes blank, press and hold the ESCAPE key (if you press it too early, Windows might interpret you as cancelling the restart process)
    2. You should get a list of bootable devices
    3. If you see the ASUS logo, you've pressed the ESCAPE key too late. Restart and retry

    Info for various operating systems:

    You should backup the recovery partition to a separate USB key. Alternatively, you can do it with this ASUS utility Backtracker that HatesForums pointed me to

    Windows:



    Windows 8.1

    • x86: (Status: Works but missing drivers)
      Used Windows 7 USB Download Tool or Rufus to create bootable USB. Using en_windows_8_1_x86_dvd_2707392 from MSDN (x86 8.1 Regular & Pro ISO), able to install W8.1 x86 and boot to it (missing a few drivers, eg touch screen doesn't work, no sound). Windows is automatically activated without need for key. First boot had 25.7GB free out of 33.6GB.
    • x64: (Status: Not yet working)
      Used Windows 7 USB Download Tool or Rufus to create bootable USB. ISO does not contain bootia32.efi. Copied that file from the x86 ISO to USB, able to boot, but the installer complains that the processor isn't 64-bit compatible
    Windows 7

    • x86: (Status: unknown)
      ISO does not contain efi
    • x64: (Status: unknown
      ISO only contains x64 efi
    Unix:

    Ubuntu:

    You need an EFI-compatible distro. For ubuntu, x64 EFI is enabled since 12.04-2. However, we'll need to include x86 EFI because our bootloader only reads x86 EFIs
    • 13.04 x64 desktop- (Status: boots to GUI using fbdev)
      Used Rufus(GPT for UEFI + FAT + 64 kb+ raring x64 as bootable disk using ISO Image) to create bootable USB. Copied over the bootia32 to /efi/boot/
      there is a bug in VESA where it queries for a BIOS-only command and crashes. Forcing xserver to use fbdev fixes this problem
    • 13.10 x64 desktop- (Status: boots to GUI using fbdev
      Same problems as 13.04 x64 plus one addition efifb problem
      see post for more details - touchscreen works, but no wifi

    Android:
    • android-ia - (Status: No x86 UEFI bootloader)
      Generic UEFI Installer android-4.2.2_r1-ia3 does not come with x86 UEFI bootloader. it does not use grub, so can't just use ubuntu's x86 grub2 efi. Need to compile it from source
    • android-x86 - (Status: Bootable but slow)
      Uses grub, can piggy-back on the ubuntu x64 13.10 bootia.efi grub. Some workarounds needed, see this post
      external/efitools/Android.mk
      # TODO: support ia32 prebuilt

      ifeq ($(TARGET_KERNEL_ARCH),x86_64)

      arch_name := x86_64


    /cpu/cpuinfo:
    taken from a x64 13.04 live USB
    processor : 0
    vendor_id : GenuineIntel
    cpu family : 6
    model : 55
    model name : Intel(R) Atom(TM) CPU Z3740 @ 1.33GHz
    stepping : 3
    microcode : 0x312
    cpu MHz : 1333.387
    cache size : 1024 KB
    physical id : 0
    siblings : 4
    core id : 0
    cpu cores : 4
    apicid : 0
    initial apicid : 0
    fpu : yes
    fpu_exception : yes
    cpuid level : 11
    wp : yes
    flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm sse4_1 sse4_2 movbe popcnt tsc_deadline_timer aes rdrand lahf_lm 3dnowprefetch ida arat epb dtherm tpr_shadow vnmi flexpriority ept vpid tsc_adjust smep erms
    bogomips : 2666.77
    clflush size : 64
    cache_alignment : 64
    address sizes : 36 bits physical, 48 bits virtual
    power management:

    processor : 1
    vendor_id : GenuineIntel
    cpu family : 6
    model : 55
    model name : Intel(R) Atom(TM) CPU Z3740 @ 1.33GHz
    stepping : 3
    microcode : 0x312
    cpu MHz : 1333.387
    cache size : 1024 KB
    physical id : 0
    siblings : 4
    core id : 1
    cpu cores : 4
    apicid : 2
    initial apicid : 2
    fpu : yes
    fpu_exception : yes
    cpuid level : 11
    wp : yes
    flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm sse4_1 sse4_2 movbe popcnt tsc_deadline_timer aes rdrand lahf_lm 3dnowprefetch ida arat epb dtherm tpr_shadow vnmi flexpriority ept vpid tsc_adjust smep erms
    bogomips : 2666.77
    clflush size : 64
    cache_alignment : 64
    address sizes : 36 bits physical, 48 bits virtual
    power management:

    processor : 2
    vendor_id : GenuineIntel
    cpu family : 6
    model : 55
    model name : Intel(R) Atom(TM) CPU Z3740 @ 1.33GHz
    stepping : 3
    microcode : 0x312
    cpu MHz : 1333.387
    cache size : 1024 KB
    physical id : 0
    siblings : 4
    core id : 2
    cpu cores : 4
    apicid : 4
    initial apicid : 4
    fpu : yes
    fpu_exception : yes
    cpuid level : 11
    wp : yes
    flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm sse4_1 sse4_2 movbe popcnt tsc_deadline_timer aes rdrand lahf_lm 3dnowprefetch ida arat epb dtherm tpr_shadow vnmi flexpriority ept vpid tsc_adjust smep erms
    bogomips : 2666.77
    clflush size : 64
    cache_alignment : 64
    address sizes : 36 bits physical, 48 bits virtual
    power management:

    processor : 3
    vendor_id : GenuineIntel
    cpu family : 6
    model : 55
    model name : Intel(R) Atom(TM) CPU Z3740 @ 1.33GHz
    stepping : 3
    microcode : 0x312
    cpu MHz : 1333.387
    cache size : 1024 KB
    physical id : 0
    siblings : 4
    core id : 3
    cpu cores : 4
    apicid : 6
    initial apicid : 6
    fpu : yes
    fpu_exception : yes
    cpuid level : 11
    wp : yes
    flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm sse4_1 sse4_2 movbe popcnt tsc_deadline_timer aes rdrand lahf_lm 3dnowprefetch ida arat epb dtherm tpr_shadow vnmi flexpriority ept vpid tsc_adjust smep erms
    bogomips : 2666.77
    clflush size : 64
    cache_alignment : 64
    address sizes : 36 bits physical, 48 bits virtual
    power management:


    Hardware info:

    • The microUSB slot is USB-HOST-capable (i.e. with a USB OTG cable or Y cable, you can connect a USB flash drive to the microUSB slot
    • Amazon.de and Asus.de posted a T100 version with 500GB drive on the keyboard base. No pictures yet
    • Internal eMMC, 108MB/s 44MB/s read/write on sequential. CrystalDiskMark here
    • External microSD(HC/XC) reader is NOT UHS-1 compatible. Someone over at liliputing comments posted his atto benchmark

      64GB Samsung microSDXC card came in the mail today, I did some ATTO disk tests using the T100's built-in microSD reader and a USB 3.0 reader from Transcend.

      Unfortunately, it looks like the built-in reader is connected via USB 2.0. It maxed out at 23.8 MB/s read and 17.2 MB/s write, while the USB 3.0 reader maxed out at 71.3 MB/s read and 21.3 MB/s write. The card is rated at 70 MB/s read and 20 MB/s write.
    7
    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
    Code:
    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.

    Android_on_t100_small.jpg
    7
    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.
    6
    Made a fair bit of progress.

    Managed to get 3.14-rc2 booting no problem, and grub installed properly, so am booting up normally; it just needs the video=VGA-1:1366x768e parameter.

    Xrandr works fine, so screen rotation will be no problem once we have the accelerometer / orientation sensor cracked.

    I got wifi working using the brcmfmac43241b4-sdio driver, but signal strength was weak. I believe this was because the nvram obtained through nvramtool was not correct; AFAIK (and I'm still learning on this), since uefi is 32-bit, access to uefi / nvram vars is unavailable from within a 64-bit linux. So instead I tried to extract nvram from a uefi shell, and converted the hexdump to ascii. This seems to work much better. I've attached the nvram as brcmfmac4321b4-sdio.txt. This just needs to be copied to /lib/firmware/brcm along with the firmware.

    All ACPI is basically still broken, but I'll see what we can get.

    Sound seems a long way off. ACPI IDs have been added for the "Intel SST audio device" since kernel 3.13, but Intel hasn't provided a driver yet. Haven't looked closely yet.

    It seems someone is working on the battery monitor.

    WYgvptb.jpg
    6
    Iconia8 source

    I started messing with 3.17 kernel to see if anything works better. Had lots of trouble getting my kconfig correct of all things, but looks like some positive progress. 3.17 combined with some code i ripped from iconia8 gives me 100% good wifi and also the eMMC is working much better and is now in HS200 mode. Apparently chip can not enter C6 during eMMC write. This is very difficult to ensure using acpi_idle driver. I have something hacked together by accessing /dev/cpu_dma_latency but it wastes a lot of power and isn't a permanent solution.

    If only I could get backlight control to work :/ Would also be nice to have the two finger scroll function. No scroll on the small screen is a serious pain.

    Edit:

    Have a reasonable solution to the c6 wake lock. Also got some backlight control working. Can adjust, still missing stuff for completely turning it off/on. Code here on top of vanilla 3.17. https://github.com/jonpry/t100_patches Doesn't include battery, everything else works pretty good. I wrote couple hundred GB to eMMC without error. No problems with wifi either. I think there is one more eMMC patch we need but only effects samsung chips which i apparently don't have. Use included kconfig or you will have problems!