Develop Bugs

[Guide] Eden Midas 8" Tablet

Moderators, please permit me to leave the tablet's Korean name (Eden Midas: 이든 마이다스) here so it shows up in google searches (if you don't have Korean fonts, it will probably show as garbage, but it really does say "Eden Midas" in Korean script).
This thread is intended as a place to collect together information about the Eden Midas tablet. It's quite possible that we will eventually find that the internals are the same as one of the Chinese tablets using the RK2918 chipset, in which case the thread may just turn into a pointer to that other thread.
What is the Eden Midas tablet?
In the form I have it, an 8" tablet based on the RK2918 chipset, with ICS 4.0.3 and kernel 3.0.8+ (whatever the plus may mean). It's quite nice, with a very clean 1024*768 screen. But like most RK2198 builds, severely locked down and marketed just as an entertainment station. At present, it seems to be only sold online in Korea. My build is V1.0.1.IMK74K.eng.root_20120508.165508_HW:1.0.0.0 (I wonder if the HW stands for huawei??).
Rooting[\B]
This is all I've done so far. Here's what I did:
On Linux
What's needed:
You may need to have root privileges on your linux system (you will need to mount some filesystems, and edit a udev rule file - depends on the linux system who is allowed to do these). You will also need rk2918tools ( https://github.com/lamegopinto/rk2918tools) - these are tools collected by lamegopinto, credits inside to the original authors; specifically, you will need ivop's rkflashtool.
In theory, this shouldn't remove your applications, data, and settings. In practice, on my machine, it did. So I'd back everything up first. And take out any external sd card so it's safe. Also, I better warn that I had a few scary moments getting to here, so please make sure you have really good backups. You will need (on your linux system) copies of su, Superuser.apk and busybox.
Connect the tablet by USB to your linux machine (real or virtual). Put the tablet into fastboot mode by holding down the whole +/- key, then pressing the start key for about 3 seconds. Keep holding the +/- key for up to ten seconds. If the system boots or goes into the boot screen (android open robot icon) you need to try again.
On the linux system, type lsusb (if you get an error, you probably need to install usbutils - how you do this depends on the linux system). If you see 2207:290a, you are OK. If you see 2077:0000, you missed fastboot mode and need to try again.
Tell linux about your device. You need to install udev rules.
Code:
cd /etc/udev/rules.d
sudo pico 61-android.rules
then create the content
Code:
# USB devices
SUBSYSTEM=="usb",ATTRS{idVendor}=="2207",ATTRS{idProduct}=="0000",MODE="0666",GROUP="users"
SUBSYSTEM=="usb",ATTRS{idVendor}=="2207",ATTRS{idProduct}=="290a",MODE="0666",GROUP="users"
This is for fedora 17. On current ubuntu the priority number (the 61 in the file name) probably needs to be different (maybe 51?). In earlier systems, the udev rule format is different, you're going to need to google this. The above rules also include one for adb mode, which will probably turn out useful. If you want adb mode, you will also need to do this:
Code:
pico ~/.android/adb_usb.ini
and create the content
Code:
0x2207
Create a directory called MIDAS inside the directory where you stored the rkflashtools. You need to have probably 2 times the capacity of your sdcard available (if you have an 8GB internal sdcard, I'd aim for 16GB+ free). Go into that directory.
Use ivop's rkflashtool to retrieve the first 2K blocks of memory:
Code:
../rkflashtool r 0x0 0x2000 > headers
This will create a file called headers. It's a binary file, but the important bit is readable. Try
Code:
more header
to read it, and carefully note down the partition locations (note that the order parameter order is the opposite to what rkflashtool uses. [email protected] means that the partition consists of X blocks starting at Y. Whereas for rkflashtool, you specify "rkflashtool (r or w) Y X (< or >) filename". The numbers X and Y are in hex notation (that's what the 0x at the start means). Note also that the MIDAS has a different layout to the tablet Ivop was discussing).
Now retrieve all the other partitions from the device, giving them descriptive names. For root, the only one you will actually need should be system.img. But get the rest just in case, as backups... Please note that there seem to be some funnies with this device, and rewriting partitions often causes it to reinitialise everything. It's probably doing some checksumming... Please keep these image files safe, and don't edit them! But you can gzip them to reduce the space they take up. Please note also that the last partition - usually the user partition - goes to the end of your card. So you need to convert your flash card size into a hex number (e.g. 8GB is 0x200000000 bytes, or 0x10000000 512B blocks). Suppose the user partition starts at 0x32A000. Then you need to put its length as 0x10000000 - 0x32A000 = CD6000 blocks (you may need a hex calculator for this).
Download su, Superuser.apk and busybox (these are all public domain) into your MIDAS directory
Code:
cp system.img system.new.img
mkdir mnt
sudo mount -t ext3 system.new.img mnt
Copy su into mnt/xbin, busybox into mnt/bin and Superuser.apk into mnt/app (simplest is to use a file manager to do this - or use linux commands). At this point, your image is complete!
Code:
umount mnt
../rkflashtool w (the system partition address and length for _your_ system image, which might be different from mine) < system.new.img
../rkflashtool b
Disconnect the USB cables
Your system should now reboot. If you're lucky (I wasn't) it will reboot as a rooted system with all your files intact. If you're semi-lucky, it will reboot as a rooted system, but without your files. Hope your backups were good... If you're really unlucky, it won't reboot. You may need to recreate all partitions from the copies you just made above, and try again. If the system seems completely bricked, the reset button (the tiny pinhole in the back, just above the external sd card door) is your friend. Pressing it and going into fastboot mode can allow you to reload all your partitions (you did make those backup copies of all partitions, didn't you)?
On Windows[\I]
Sorry, I have no idea. If someone drafts a guide, I'm happy to put it up. Alternatively, you can easily install a ubuntu virtual machine inside your windows box. It will probably be easier, and the linux experience won't go astray in working with android anyway.
[Tun Drivers and Openvpn]
For some reason known only to themselves, the manufacturers have removed the Tun drivers from the ics kernel build. The kernel doesn't have the ability to load modules. (This makes sense for phones, maybe, but I can't understand why anyone would remove the ability to load modules in a tablet. Perhaps the Chinese government doesn't want it to be too easy for people to set up vpns?) Anyway, you can install what appears to be a suitable Tun module using Tun.ko installer. It installs OK but when you try to use it, the system freezes for about 10 seconds, then reboots. If anyone finds a version of the 3.0.8+ kernel (maybe 3.0.8- kernel would be a better name), suitable for the Midas and with either a built-in tun driver, or the ability to load kernel modules, please let me know.
Complete Reflashes
Not sure if there are any that will work right now. If you're really stuck, the cyanogenmod version for Cube might work, but it sounds like it is still a work-in-progress.

Do you have the kernel of the tab?
- Oma -

Oma7144 said:
Do you have the kernel of the tab?
Click to expand...
Click to collapse
Sorry, no - and sorry for the delay in replying, I didn't get notification for the thread.

Dump the firmware and upload the files: http://forum.xda-developers.com/showpost.php?p=35298423&postcount=462
- Oma -

[DEV][WIP] xubuntu on tf300tg 0.1.2 (updated 130408)

*** ABOUT ***
This is an attempt to build a completely clean installation of xubuntu for the tf300tg (and probably tf300t). Most notably it does not reuse the ac100 ubuntu package.
I also want it to be as completely documented as possible starting from an official ubuntu repository and kernel source, until everything is working. Which does not mean it is for a complete beginner to reproduce...
It's not (yet) packaged : you at least need to be able to install a blob for the kernel, and a rootfs to a dedicated partition.
It's also not yet as cleaned up and documented as I would for the kernel side of things.
Everything is done on device on (and for) a tf300tg but as been reported to work on tf300t.
Most of the hard work was done by others. I mostly started from rabit's tf700 ubuntu, and added some insight from cb22 work on arch to get something working.
*** STATUS ***
What works :
- it boots into a clean xubuntu dm/desktop, with wifi (improved), 3g
- it also boots into android (stock, didn't try cm)
- 3g also works under android (new)
- touchpad / touchscreen
- 3d acceleration (version 16.3 of nvidia drivers)
- cpu and gpu overclock (respectively to 1,5 GHz and 446 MHz)
What I know doesn't work, isn't there yet :
- sound
- bluetooth
- some key remapping (esc, alt, ...)
Many other things I didn't check (sensors ?).
*** HOWTO install ***
0. of course you can break many things doing that ; you should have access to nvflash (never had to use it though) and with a recovery installed (I'm on twrp 2.4.3.0)
1. unpack xubuntu_tf300tg_rootfs-0.1.2.img.lzma to the internal storage and move / rename to linux/rootfs.img (/data/media/linux/rootfs.img)
1bis. you can change your keyboard layout in /etc/default/keyboard (replace "us" by whatever is your locale)
2. install the kernel blob using fastboot or "dd if=xubuntu_tf300tg_kernel-0.1.2oc.blob of=/dev/block/mmcblk0p4"
You should be able to reboot into xubunfu (or android).
3. log in as guest, from "user and groups" in the "settings manager", add one user, set password, change account type to administrator, add to sudo group (root password wil be asked : root)
4. logout, then login into your newly created user
5. open "language support" from the settings manager, and when it says missing locales, either choose install if you want "en" or "ask me later" if you want something else (in which case you can chose to install your own language, and configure them on the "regional format" page ; don't forget to apply system wide on both pages
6. change root password
Your second reboot should be more satisfying
*** HOWTO improve ***
1. find out what does not work and tell in the thread
2. understand what is documented bellow and propose correction / evolutions in the thread
3. don't hope for frequent updates : I do that alongside a more than full time job and tending to a two years old child. Still I will update.
*** DOWNLOAD ***
rootfs : http://d-h.st/vYf
kernel : http://d-h.st/UAy
misc config files : http://d-h.st/TEZ
nvidia drivers : http://d-h.st/pwQ
md5sum :
4f572c110c3f06f54699c826fed692f4 src-0.1.2.tar.lzma
249826271f4fadff4352217467e4ed2e xubuntu_tf300tg_kernel-0.1.2oc.blob
3263de707c2586d1e2177367f067361a xubuntu_tf300tg_rootfs-0.1.2.img.lzma
cf20b01281be3ef4b6d4631ae5cea67b R16.3.tar.lzma

*** HOW is it done / rootfs ***
I did it from ubuntu (rabits') on my tf300tg. Should be doable from another platform. Definitly doable from self.
As root.
# unset languages / locales
export LANG=C
unset LC_ADDRESS
unset LC_IDENTIFICATION
unset LC_MEASUREMENT
unset LC_MONETARY
unset LC_NAME
unset LC_NUMERIC
unset LC_PAPER
unset LC_TELEPHONE
unset LC_TIME
# mount a cleanly ext4 formated partition (futur root partition)
mount /dev/mmcblk1p2 /media/p1
# install initial minimal system
apt-get install debootstrap
debootstrap quantal /media/p1 http://ports.ubuntu.com/
# prepare to chroot
mv /media/p1/etc/apt/sources.list /media/p1/etc/apt/sources.list.orig
cp src/sources.list /media/p1/etc/apt/sources.list
mv /media/p1/etc/fstab /media/p1/etc/fstab.orig
cp src/fstab_chroot /media/p1/etc/fstab
mkdir /media/p1/run/user
# chroot into the new system and mount all special filesystems
chroot /media/p1
mount -a
# download xubuntu (avoiding unity which is recommended by lightdm)
apt-get update
apt-get upgrade
apt-get install xserver-xorg
apt-get --no-install-recommends install lightdm
apt-get install lightdm-gtk-greeter
apt-get install xubuntu-desktop
# install nvidia drivers and tuned nv.conf
tar xf R16.3.tar
update-alternatives --force \
--install /etc/ld.so.conf.d/arm-linux-gnueabihf_EGL.conf arm-linux-gnueabihf_egl_conf /usr/lib/nvidia-tegra/ld.so.conf 9000 \
--slave /usr/lib/xorg/modules/drivers/tegra_drv.so nvidia_drv /usr/lib/nvidia-tegra/xorg/modules/drivers/tegra_drv.abi13.so
ldconfig -v
update-rc.d ondemand disable
# change root password to something of your chosing and exit chroot
passwd root
# configure touchscreen and touchpad
apt-get install xserver-xorg-input-multitouch
exit
cp src/mtev.so /media/p1/usr/lib/xorg/modules/input
mkdir /media/p1/etc/X11/xorg.conf.d
cp src/50-elan* /media/p1/etc/X11/xorg.conf.d
# change hostname
# edit /media/p1/etc/hostname and replace tf300tg with your chosen hostname
# edit /media/p1/etc/hosts and insert a line (second one) with "127.0.0.1 yourhostname"
# hide the partitions from mmcblk0 (thanks cb22)
echo 'ENV{ID_PATH}=="platform-sdhci-tegra.3", ENV{UDISKS_IGNORE}="1"' > /media/p1/etc/udev/rules.d/80-hide_tf300tg_partitions.rules
# change keyboard defaults
# edit /media/p1/etc/default/keyboard ; replace "pc105" by "asus_laptop" ; you can also change "us" to your locale
# create mountpoints for system and data
mkdir /media/p1/system /media/p1/data
# configure for loading wifi module
echo bcm4329 >> /media/p1/etc/modules
#
cp /media/p1/etc/fstab.orig /media/p1/etc/fstab
*** HOW is it done / kernel ***
The kernel source is default asus 10.4.3.9 from asus' website download section. Patched to add cpu overclock from faux's kernel and gpu overclock from motley's kernel (diff file in src.tar.lzma).
Initial kernel config file is taken from stock 10.4.3.9 android, with options added to support ubuntu and oc. path to the nvram for bcm4329 modified.
Ramdisk is mostly that from rabbits 0.8.0, with some modificaitons to enable modem support under android.
*** Todo ****
- modify config / kernel to use nvidia's R16.3 tool to patch wifi ;
- build initramfs anew from tf300t/tg stock android initramfs (currently rabbits modified tf700) ;
- bluetooth and sound ;
- key remapping.

reserved 2

Sounds promising! Keep it up, hopefully other devs see this and help you out :good:

Re: [DEV][WIP] xubuntu on tf300tg 0.1.0
Good job, I will tray luck to night when I back from work.
P.S. I heave no dock - that means no keabord and mouse
Sent from my GT-I9100 using xda app-developers app

Keshukas said:
Good job, I will tray luck to night when I back from work.
P.S. I heave no dock - that means no keabord and mouse
Sent from my GT-I9100 using xda app-developers app
Click to expand...
Click to collapse
Thanks for your interest.
Although I would be happy to have some feedback, it may be a bit early if you don't have a dock : it's completely functionnal with a dock and mouse (I've been using it for work - and build - for a few days), without a keyboard and mouse, you will not go farther than xubuntu' login screen.
Anyway if you still wan't to try it, tell me if you reach xubuntu blue login screen.

Re: [DEV][WIP] xubuntu on tf300tg 0.1.0
On the rabbit Ubuntu for tf700 are virtual keabord (beside clock switch ) witch I use to login to Ubuntu
Sent from my GT-I9100 using xda app-developers app

Assuming this is a dual boot kernel, how does the kernel know where ubuntu is installed if not installed on internal sdcard? Also what's the minimum size partition that can be used?

Moved the thread for ya...

Yes!!! ) Thanks I wait for it )) Xubuntu is my lovely linux, I have it on PC, Notebook, installed on fathers PC and now for tablet!! :good::good::good:

Keshukas said:
On the rabbit Ubuntu for tf700 are virtual keabord (beside clock switch ) witch I use to login to Ubuntu
Sent from my GT-I9100 using xda app-developers app
Click to expand...
Click to collapse
I know that and it can be reproduced (look at rabits' /etc/X11/xorg.conf ; and needs packages xserver-xorg-input-multitouch and mtev).
But I have not yet abandonned all hope of doing it the ubuntu way (ie. with evdev).
TechyNut said:
Assuming this is a dual boot kernel, how does the kernel know where ubuntu is installed if not installed on internal sdcard? Also what's the minimum size partition that can be used?
Click to expand...
Click to collapse
Rabits modified the boot image so that it checks /dev/sda*, then /dev/mmcblk1p*, then an img file on /dev/mmcblk0p8. The first which looks to be an ubuntu partition is used as root. He also activated vt (having a console during boot) in is kernel configuration. I reproduced both.
NRGZ28 said:
Moved the thread for ya...
Click to expand...
Click to collapse
Thanks. Induced some noise on other threads

Ramdisk initrd.img in your kernel blob file is not a gzip !!!

Ok starting test
1. Yours kernel most start android if no Linux in /dev/sda1 or /dev/mmcblk1p* or on /dev/mmcblk0p8. Some I understand ?
Now making backup of me tablet ( TF300t ) and flashing kernel to test it.
2. I planing Make Linux on me ExtSDcard (MiniSD 8 gb) and plug sdcard in tablet and then reboot tablet. i hope to start Xubuntu

akurpiel said:
Ramdisk initrd.img in your kernel blob file is not a gzip !!!
Click to expand...
Click to collapse
No. It's lzma.
You can check rabits' git for details : https://github.com/rabits/tf700
Keshukas said:
Ok starting test
...
i hope to start Xubuntu
Click to expand...
Click to collapse
I hope too. Thanks for testing.

Can't mount linux
So I thought I'd give this a try. These are the steps I took to install this:
1. Formated 8gig SD card as ext4
2. Extracted rootfs to SD card.
3. Inserted SD in base
4. copy /system/vendor and /system/etc from your tf into /system on that partition ; copy /data/misc from your tf into /data on that partition
5. fastboot -i 0x0b05 flash staging xubuntu_tf300tg_kernel-0.1.0.blob
6. reboot
6. Kernel boots prompting option, select 1 (linux) and fails to mount partition and boots into android with no other problem.
What am I missing?

ColMustard said:
So I thought I'd give this a try. These are the steps I took to install this:
1. Formated 8gig SD card as ext4
2. Extracted rootfs to SD card.
3. Inserted SD in base
4. copy /system/vendor and /system/etc from your tf into /system on that partition ; copy /data/misc from your tf into /data on that partition
5. fastboot -i 0x0b05 flash staging xubuntu_tf300tg_kernel-0.1.0.blob
6. reboot
6. Kernel boots prompting option, select 1 (linux) and fails to mount partition and boots into android with no other problem.
What am I missing?
Click to expand...
Click to collapse
I have had some occurences of hitting return to fast at the prompt and init not detecting correctly the SD card. So maybe let it timeout into trying to boot linux.
If that does not work, you can choose "s" at the prompt, then from there check into /dev/ which disks / partitions are recognized. Provided that your linux partition is the first and only one on the SD card, you should have a /dev/sda and /dev/sda1. What do you see ?
Also remove any usb drive, which could appear as /dev/sda (and make the sd card appear as /dev/sdb).

Some RABIT write "In-device microSD really bad works." :crying:
I heave problems to boot from sd now i think extract xubuntu in /data/media/linux/rootfs.img
-- Update --
MicroSD - /dev/block/mmcblk1p1

schrdlu said:
I have had some occurences of hitting return to fast at the prompt and init not detecting correctly the SD card. So maybe let it timeout into trying to boot linux.
If that does not work, you can choose "s" at the prompt, then from there check into /dev/ which disks / partitions are recognized. Provided that your linux partition is the first and only one on the SD card, you should have a /dev/sda and /dev/sda1. What do you see ?
Also remove any usb drive, which could appear as /dev/sda (and make the sd card appear as /dev/sdb).
Click to expand...
Click to collapse
Well it looks like it's a no go for me. it could be that I used Minitool Partition Wizard to format because I could not get to my linux machine at the time.
I also tried flashing the kernel over 3 different ROM:
1. CROMI 3.4.4 - Keep failing with Encryption error after boot animation prompting me to reset the device.
2. Hydro 7 - Keep failing with Encryption error after boot animation prompting me to reset the device.
3. CM 10.1 - Failed to get pass boot animation.
I'll have to re-flash Asus stock ROM (10.4.2.20) in order to fully test this, I might have to reformat the sd on linux also.

ColMustard said:
Well it looks like it's a no go for me. it could be that I used Minitool Partition Wizard to format because I could not get to my linux machine at the time.
I also tried flashing the kernel over 3 different ROM:
1. CROMI 3.4.4 - Keep failing with Encryption error after boot animation prompting me to reset the device.
2. Hydro 7 - Keep failing with Encryption error after boot animation prompting me to reset the device.
3. CM 10.1 - Failed to get pass boot animation.
I'll have to re-flash Asus stock ROM (10.4.2.20) in order to fully test this, I might have to reformat the sd on linux also.
Click to expand...
Click to collapse
Me to. I can't boot to android at all
I still tray boot to xubuntu with this kernel and I make img on the internal card

Keshukas said:
Me to. I can't boot to android at all
I still tray boot to xubuntu with this kernel and I make img on the internal card
Click to expand...
Click to collapse
Yeah, I did notice that the kernel looks for the /data/media/linux/.img for a last effort. I was thinking on doing the same.

THBK1-10 thread: extend, root, hack !

Hello,
I'm the proud owner of an hybrid monster, called THBK1-10.
This is basically an affordable tablet, running both Windows 8 and Android 4.2.2.
10.1 display, running x86 Atom 4cores, 2Gb RAM, 32Gb eMMC, USB host enabled. It is shipped with an external keyboard/touchpad (no port, no battery, no extended storage on it). More informations: http://www.thomsoncomputing.eu/dualboot.html
Windows 8 comes in x86 flavor...
The boot process let you choose Windows or Android.
There is no play store. My main goal actually is:
- (ok) rooting Android part
- (ok) installing Play Store
- (ok) increasing space
- (nok) installing a recovery (CWM/TWRP) allowing you to flash non-signed updates
- (nok) running Linux from an external USB drive
Partition layout: http://forum.xda-developers.com/showpost.php?p=54095052&postcount=8
Rooting / play store guide: http://forum.xda-developers.com/showpost.php?p=55513404&postcount=23
Known clones: http://forum.xda-developers.com/showpost.php?p=54282229&postcount=10
Increasing space with external SD: http://forum.xda-developers.com/showpost.php?p=54914759&postcount=17
Timezone issue Android/Windows: http://forum.xda-developers.com/showpost.php?p=54945950&postcount=19
BIOS default (SlateDroid): http://www.slatedroid.com/topic/106594-thbk110-default-bios-values/
Have fun !

I know there are EXT2 drivers for Windows, and EXT3 is just EXT2 + Journaling (the journaling is an important feature, but it's not part of the security model). However, I'm not sure if any of those drivers can modify file permissions. Alternatively, one could of course hex-edit the Android partition and try to tweak the file permissions that way, but that would require much more understanding of the EXT filesystem than I have. The source code is all open, though...

Thank you. Here is what i did:
a) trying to handle EXT3 fs from Windows
-> with Ext2Fsd, i have accesses to all the partitions, including /system and /data, but unfortunatly, permissions are not correct
-> i trying with other tool (Explore2Fs) not luck
-> ltools seems to provide a lattr util that could do it, but i'm unable to see the files (certainly because of the GPT partition
b) trying to use VirtualBox with raw disk access for handling, with a linux guest, permissions:
-> up to partition 7, this seems correct
-> from partition 8 (/system), i can mount it in RO but it crashes in RW
c) trying to boot to any linux supporting EFI32 and GPT
-> thanks to paperwastage, i could achieve it (thread here: http://forum.xda-developers.com/showthread.php?t=2500078 )
-> i have strange troubles: the system only detect mmcblk0 to mmcblk7, and is throwing an error (error -110 + unknow command)
-> both, in clonezilla and ubuntu
d) tryed to use so android local tricks to force change mode, but once, i'm stuck with no eXecute flag. I dig around the local.prop or any stuff that would help me to achieve this goal. The recovery is not available (nor i found it) and the only thing i can do is factory reset.
It really seems only Windows got the proper drivers for this eMMC. This could explain why i had hard time to dump it (and, actually, i would not try to restore b/c i'm not sure everything is backuped correctly and don't want to brick my tablet), and why i could only write from Windows and why it cuts at partition7 (i have at least 12 partitions. NTFS windows main is the #11 iirc)
What i could try actually:
-> double check with newer ubuntu (when i started "install to disk", it seems it could detect the whole disk, have to look again)
-> double check with local THBK install (copy 3 apks bundled with the tablet, but perhaps a command script is available to be executed ?)
-> double check with virtual box & raw disk acces (i focused on /system, but perhaps /data is ok ?)
-> recompile Ext2Fsd to have different default properties
-> dig the hardware to see if a real recovery boot is not available, or change the recovery to something more usefull than factory reset
Thank you if you have more and more ideas

Quick notes:
- THBK1 does NOT connect to PC/MAC
- THBK1 does NOT have USB Debug activated. The micro-usb is aimed to put a (normal) cable, not an OTG one nor a charging cable. You can reach ADB only over Wireless.
-> Currently trying TowelRoot with different parameters, but for now not successfull. Basically this is a 4.2.2 kernel so i could expect a low resistance at exploits, it worths to be tested

Good news, i was able to boot from an USB stick (with EFI), and while the MMC is not accessible, i found a trick to change permissions.
I have now full R/W support on EXT3 partition.
But sadly SU is not enough to gain root accesses.... damn.
Anyone able to find doc or explain how root access is triggered ?

I found an update, and i'm now able to flash the whole system partition. Sadly, i could not flash another update.zip, so i guess this is signed (and sadly it is).
I have also tryed z4root, towelRoot exploits, not working.
Basically i could somehow bypass the sign system in applying myself the content of the update.zip (as long as it deals with /data and /system files & perms). I'll try that for at least google apps.
edit: ok i have now play store and the whole google suite is working after a big playstore update (talkback, vocal syntgetisis and so on). Only google+ is FCing but it should only be a matter of installation. I should remove it and reinstall it from the market.
Only thing missing is root
Status on Android forum side: http://forum.xda-developers.com/android/help/hacking-thbk1-10-getting-root-t2804631/post53896017

As today, the tablet is now rooted. It works flawlessly.
Next step is the handling of recovery to flash non-signed zip files. It would ease the process of installing GAPPS or rooting the tablet.
But i'll take a break before
TODO list, from top to crazy:
- recovery
- test and deploy various system tweaker sur as Xposed framework
- bugfix vibrator (only working when you hit Windows button, not in apps)
- new rom, new kernel

Here is the actual partition layout:
Code:
Model: MMC BIWIN (sd/mmc)
Disk /dev/mmcblk0: 30.9GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 1049kB 269MB 268MB fat16 ANDROID!bootloader boot, hidden, legacy_boot
2 269MB 337MB 67.1MB ANDROID!panic
3 337MB 873MB 537MB ext4 ANDROID!factory
4 873MB 2484MB 1611MB ANDROID!fake
5 2484MB 2618MB 134MB ext4 ANDROID!config
6 2618MB 4229MB 1611MB ext4 ANDROID!cache
7 4229MB 5303MB 1074MB ext4 ANDROID!logs
8 5303MB 7450MB 2147MB ext4 ANDROID!system
9 7450MB 11.7GB 4295MB ext4 ANDROID!data
10 11.7GB 11.7GB 1049kB ANDROID!misc
11 11.7GB 11.8GB 33.6MB ANDROID!boot
12 11.8GB 11.9GB 134MB ANDROID!recovery
13 11.9GB 11.9GB 33.6MB ANDROID!droidboot
14 11.9GB 12.3GB 315MB ntfs Basic data partition diag
15 12.3GB 12.5GB 273MB fat32 EFI system partition boot
16 12.5GB 12.7GB 134MB Microsoft reserved partition msftres
17 12.7GB 30.9GB 18.3GB ntfs Basic data partition msftdata
I'm not able to read the partition w/o filesystem (2, 4, 10, 11, 12, 13).
I tryed with yaffs2, but i'm not able to see them (and since it is not MTD...)
I'm working on dd image of the 32Gb MMC.
In example, hexdump of partition 12 shows it is a kernel. Certainly the recovery kernel directly flash, i should dig this.

Guide: installing Google Apps and Rooting the tablet
THIS POST IS DEPRECATED. See http://forum.xda-developers.com/showpost.php?p=55513404&postcount=23
:good: /!\ Please click thanks or offer me a coffee with donate if it was usefull for you /!\ :good:
This is rather technical, but i can help if you are stuck. Thank you for your comments.
Here is how you could install Google App suite to the THBK1-10 and certainly many ones based on Inside H2O bios, board name: CARD_B (see above for detailled specs)
Basically, to install some stuff, the concept is to get rid of all the caveats (special MMC drivers, EFI 32 bits with GPT, etc...) through actual Windows 8.1 installation. Everything takes place through classic Windows desktop. For convenience, personnally worked with TeamViewer, doing this with the dock/touchpad is pain in the ass. You can void your warranty and break the android part of your tablet, so operate carefully, i'm not responsible of what you do !
This leads to 3 phases:
a) accessing EXT4 Android partitions
b) transfer files from Windows to Android
c) change permissions
a) Accessing EXT4. I used coLinux to access and handle Android EXT4 partitions:
- download and install coLinux http://sourceforge.net/projects/colinux/files/latest/download?source=files. At the 'Choose components' screen, uncheck 'Root filesystem image Download', and accept everything (including TAP drivers)
- download and unzip Debian Squeeze image in coLinux folder (c:\program files\colinux). Warning, this leads to a 2Gb file, ensure you have proper space. You could unzip it in your external SDcard, but you would have to change the path to rootfs and swap in above squeeze.conf
http://sourceforge.net/projects/col... 6.0 Squeeze/Debian-6.0.1-squeeze.7z/download
- test it: click on the squeeze.bat file into c:\program files\colinux (if you have an error co-slirp, simply close colinux and restart it). Once you have the 'debian login:' prompt simply type root then enter. You are now under coLinux.
First, install your local keyboard (if needed)
Code:
apt-get update
apt-get install console-setup locales console-data
In case you miss the point for the keyboard:
(choose select keyboard from full list / pc azerty or whatever...)
Code:
dpkg-reconfigure console-data
- you should now update your /etc/apt/sources.list file:
Code:
nano /etc/apt/sources.list
- fill with the following lines (remove all before)
Code:
deb http://ftp.fr.debian.org/debian/ squeeze main contrib non-free
deb http://security.debian.org/ squeeze/updates main contrib non-free
- update your apt repository:
Code:
apt-get update
- you would like to sync the clock from Linux with Windows: edit /etc/default/rcS and change UTC=yes to UTC=no
Code:
nano /etc/default/rcS
You can exit coLinux, we have things to tweak now.You can then download the attached Squeeze.conf, and put it into your colinux folder, replacing the old. Remember, if you have changed the path for rootfs and swap, you must change them to reflect your current installation.
Squeeze.conf:
Code:
kernel=vmlinux
cobd0="c:\program files\coLinux\rootfs_2gb.img"
cobd1="c:\program files\coLinux\\swap_128mb.img"
cofs0="C:\share"
cobd8=\Device\HarddiskVolume8
root=/dev/cobd0 ro
initrd=initrd.gz
mem=256
eth0=slirp
b) transfer files from Windows to coLinux
We would create a share folder at the root of C:\.
You must have C:\share folder.
- Create a directory in /mnt
Code:
mkdir /mnt/win
- then mount the folder into your coLinux
Code:
mount -t cofs cofs0 /mnt/win
FOLLOW THE ABOVE ONLY FOR GAPPS:
- You must now download the google apps files. The operation is done under Windows:
download Android 4.2.2 ones: http://goo.im/gapps/gapps-jb-20130812-signed.zip and extract all the file into C:\share
This folder must contains the whole gapps (you 'll see folders named: system, META-INF, optional...).
You must directly DELETE 3 files and 1 folder:
file system\app\GooglePlus.apk
file system\app\LatinImeDictionary.apk
file system\lib\libjni_latinime.so
fodler system\tts
If everything is ok, browsing /mnt/win/ from coLinux (not windows)
Code:
ls /mnt/win
should show the share directory content (META-INF,system,optional,...).
FOLLOW THIS ONLY IF ROOT:
- You must now copy su binary to your tablet: download attached files, unzip, copy it to your windows desktop shared folder
Nota: this file is extracted from Koush' superuser APK. This is the x86 su binary. Feel free to replace with newest version if available or if you fear something
FOLLOW THIS IF ROOT & GAPPS
c) access to Android partition
- create a system folder in /mnt
Code:
mkdir /mnt/system
- mount android to system
Code:
mount /dev/cobd8 /mnt/system
- check you are ok with
Code:
ls /mnt/system
You must see app, bin, usr, etc .... folders.
*** at this point, /mnt/system contains ALL your android system. NO MISTAKE ! ***
FOLLOW THIS ONLY IF GAPPS
- part 1: removing files. Browse to /mnt/system/app and CAREFULLY delete the 8 files (some could be missing, don't bother):
Code:
cd /mnt/system/app
rm Provider.apk
rm Provider.odex
rm QuickSearchBox.apk
rm QuickSearchBox.odex
rm SetupWizard.apk
rm SetupWizard.odex
- part2: copy. Copy the files from Windows to Android - it could take up to 2 minutes -
Code:
cp -rp /mnt/win/system/* /mnt/system
- then fix the permissions:
Code:
chmod -R 755 /mnt/system/addon.d
chmod 755 /mnt/system/app/*
sync
At this point, this is over. You can exit from colinux, reboot to Android, and come back to windows uninstalling coLinux, if anything is ok
The whole GAPPS are installed. Enjoy !
FOLLOW THIS ONLY IF ROOT
- copy attached x86 su binary to android
Code:
cp -p /mnt/win/su /mnt/system/bin
- then fix the permissions:
Code:
chmod 755 /mnt/system/bin/su
chmod u+s /mnt/system/bin/su
ln -s /mnt/system/bin/su /mnt/system/xbin/su
sync
At this point, this is over. Reboot, you can now download and install superuser https://f-droid.org/repository/browse/?fdfilter=superuser&fdid=com.koushikdutta.superuser
Your tablet is now rooted. Enjoy !

Know clones (feel free to help):
- Danew i1012 dual boot (strictly identical to Thbk1)
- VOYO A1 (Windows 8 only).
- Cube U100GT (Windows 8 only)
Certainly clones:
- Ramos i10 pro (dual boot)
- Pipo W1 / Work W1 (Windows 8 only)
- ColorFly i106 (Windows 8 only)
- Toshiba WT8-AT01G (Windows 8 only)

Graveen said:
Know clones (feel free to help):
- Danew i1012 dual boot (strictly identical to Thbk1)
- VOYO A1 (Windows 8 only).
- Cube U100GT (Windows 8 only)
Certainly clones:
- Ramos i10 pro (dual boot)
- Pipo W1 / Work W1 (Windows 8 only)
- ColorFly i106 (Windows 8 only)
- Toshiba WT8-AT01G (Windows 8 only)
Click to expand...
Click to collapse
Considering getting a voyo a1 or a pipo w2. But 99% of my interest in windows 8 tablets is running old windows games on them. What's your experience with win 8 and older games for windows? Touchscreen make anything unplayable? Thinking old command and conquer or Warcraft 1-3 etc. With some RPG thrown in.
I hate the idea of being limited to just windows, but I'm hesitant to spend too much on what might not work like I hope.

StridAst said:
Considering getting a voyo a1 or a pipo w2. But 99% of my interest in windows 8 tablets is running old windows games on them. What's your experience with win 8 and older games for windows? Touchscreen make anything unplayable? Thinking old command and conquer or Warcraft 1-3 etc. With some RPG thrown in.
I hate the idea of being limited to just windows, but I'm hesitant to spend too much on what might not work like I hope.
Click to expand...
Click to collapse
Honestly,i installed Steam and played some to test. But, alas, it is not successfull. If you can wire a BT pad, let's say it is ok, but else, generally, the touchpad is not suitable, really.
Of course some point'n clic games should work nicely. But except theses, you 'll be forced to add keyboard/mouse. Or, as i mentionned, a bluetooth gamepad, with some keyboard mapping, such as XPadder, could work fine.

Graveen said:
Honestly,i installed Steam and played some to test. But, alas, it is not successfull. If you can wire a BT pad, let's say it is ok, but else, generally, the touchpad is not suitable, really.
Of course some point'n clic games should work nicely. But except theses, you 'll be forced to add keyboard/mouse. Or, as i mentionned, a bluetooth gamepad, with some keyboard mapping, such as XPadder, could work fine.
Click to expand...
Click to collapse
So basicly, the hardware ran things OK, but the interface sucks, oh well. Probably not worth the headaches of dealing with windows again. I'd imagine it's a real PITA to fix things if it gets a virus.

StridAst said:
So basicly, the hardware ran things OK, but the interface sucks, oh well. Probably not worth the headaches of dealing with windows again. I'd imagine it's a real PITA to fix things if it gets a virus.
Click to expand...
Click to collapse
Like a windows. The 'dock' is allowing light computer use, and Office 2013 home is shipped for free with the tablet. But yeah, Windows legacy is the key when dealing with windows

Hey mate,
I have one of these - http://www.ebay.co.uk/itm/390900023783?ssPageName=STRK:MEWNX:IT&_trksid=p3984.m1497.l2649
are you implying that I should be able to get it to dual boot Windows and Android following your guide?
Thanks
Karl

Hello Karl,
Yes it should be possible if strictly identical.

Increase data space with Link2SD
You can dedicate a part of external SD to increase /data size. Link2SD is ok for this, and will, in the free version, allows you to move APK to external partition.
Your tablet MUST be rooted !
1) ensure you have a FAT32 partition (primary, 1st position)
2) ensure you have an EXT2 or EXT4 partition (primary, 2nd position)
3) install Link2SD https://play.google.com/store/apps/details?id=com.buak.Link2SD
You can now use Link2SD which 'll create links and move your APKs to your new EXT partition.
Personnaly, i have a 32Gb SD with 24Gb FAT + 8Gb EXT4 partition.

Increase data space with Link2SD : Good news !!! You are the Boss. THNK1-10 is available at Carrefour (an another good news)

Time is changing between windows and Android
You can simply set timezone to GMT+0 and disable network time.
On Debian, you set UTC to YES, but need to seek where it takes place in Android.

bu3304 said:
Increase data space with Link2SD : Good news !!! You are the Boss. THNK1-10 is available at Carrefour (an another good news)
Click to expand...
Click to collapse
carrefour or conforama.
thomson carrefour and /danew in conforama.
even saw on internet that MSI is also having this tablet and just sticking there logo on it. atleast looked like this tablet.
---------- Post added at 12:05 AM ---------- Previous post was at 12:01 AM ----------
hum. i think i will go for the new asus transformer book t100 with atom z3775 processor.
i like the battery life of the asus.
but prefer the acer switch 10 in terms of look and the magnetic dock
but yeah choice of 11 hours of battery or 8. makes a difference
and the new 3775 or 3745. cpu

[LIVE][USB][T100] Asus T100-TA Magic Stick

Asus T100-TA Magic Stick
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Since development and hacking for the Asus T100 tablet has been rather slow these past few months, due to the many problems that plagued the kernel and missing drivers, I decided to make a simple-to-use toolchain that works well on the device out-of-the-box. Thus, I have bundled a fully working Ubuntu live CD image and an Android-x86 build into a single usb stick format (I call it the "Magic Stick"), to allow easy testing, booting and updating stuff on the tablet. You can also use it to recover your device and perform maintenance activities without the usual hassle. And you can use it for showing off to your friends and co-workers by triple booting your tablet.
T100 Magic Stick Features:
Dual-boot directly from USB stick into Android or Ubuntu!
Test and play with both systems to see if you like them
Ubuntu 15.04 Live:
Updated 4.0 kernel (thanks to Kirill Belyaev for the kernel build)
No more internal HDD errors (no more rpmb issues)
Suspend working!
Installer working with grub installation! Finally!!
microSD Card working correctly
Wi-Fi working stable since boot
Battery reporting
Hardware buttons
Additional tools by default (gparted, mc, uefi, efibootmgr, grub2)
Android CM13.0.2-rc1 Live:
No more internal HDD errors (no more rpmb issues)
Wi-Fi working
Bluetooth working
Battery reporting
Hardware buttons working
Google Services! (Play Store etc.)
Pre-rooted!
Writable system partition
Persistent data saving on stick (1GB internal storage)
Rotation sensor working
Shrink and change partition layouts
Install and repair bootloaders, grub2 and UEFI
Install, repair, debug and update any operating system
Download and Install:
The installation procedure is extremely simple:
Download the Magic Stick zip file from here: T100 Magic Stick download
Extract the ZIP file
Copy the contents of the extracted folder to a USB stick (at least 3GB free space required)
Disable secure boot in the UEFI firmware configuration (tap F2 at startup to enter configuration)
Boot from the USB stick (tap F2 at startup and choose the stick as boot device from the menus)
Thanks and credits:
Kirill Belyaev, Povilas Staniulis, rbg, Chih-Wei Huang, Brain WrecK, pstglia for their work and contribution + their dedication and their builds.
The whole Asus T100 Ubuntu Google+ Community (chck us out!);
The whole Android-x86 Google Group (check us out!);
Everyone else who contributed patches, fixes, ideas and suggestions!
Download:
v2.0-beta1: Download
Cheers,
C.

Changelog:
v1.5: Ubuntu: no changes or improvements, sorry...
v1.5: Android: microSD card support
v1.5: Android: no more FC bugs at boot...
v1.5: Android: display driver improvements (some games and apps which didn't work will start working now)
v1.5: Android: better overall performance (+2500 points in Antutu than previous version)
v1.5: Android: better browser support (chrome, firefox etc.)
v1.5: Android: streaming support less buggy
v1.5: Android: latest 4.4.2-r3 build included (much more stable)
v1.5: Android: improved bluetooth support (some issues still reported, though)
v1.4: Ubuntu: added bluetooth support (seems unreliable)
v1.4: Ubuntu: updated packages to latest versions
v1.4: Ubuntu: fixed Software Center problems
v1.4: Android: data is saved to the stick (1GB internal storage only!)
v1.4: Android: added bluetooth support (tethering not working, yet)
v1.4: Android: added accelerometer sensor support
v1.4: Android: added rotation sensor support
v1.3: Ubuntu installer does not crash anymore!
v1.3: Added suspend support in Ubuntu
v1.3: Updated to Ubuntu 15.04
v1.3: Added sound for Ubuntu
v1.2: Initial release
Known Issues:
Ubuntu: suspend doesn't work as it should, no bluetooth, no rotation, no camera, no microphone;
Android: suspend doesn't work as it should, no bluetooth, no rotation, no microSD, no camera, no microphone;
Android: at boot, Google text-to-speech will FC a couple of times. This is fixed once you log into google play and update the GApps;
[*]Android: sometimes the keyboard dock is not enabled at boot. This is caused by a race condition at boot and I won't fix it. If you run into it, reboot and try again; (didn't encounter it anymore)
You tell me...
Frequent Questions:
Can I remove the stick after boot?
Answer: No. This works like a live CD.
Will my data be saved?
Answer: In Ubuntu no. This works like a live CD. In Android yes, you can store up to 1GB of data (due to popular request).
Can I install Ubuntu?
Answer: Yes. This works like a live CD.
Can I install Android?
Answer: Yes, but not using the built-in installer.
How can I install Android-x86?
Answer: Manually, but it's easy. Maybe I will create a step-by-step guide later...
Will Android work with ART (before or after install)?
Answer: No.
Can I install xposed framework?
Answer: Yes, but not on the live version, you must install Android locally first.
How can I update the Android-x86 version on the stick?
Answer: Replace the files in the "x86" folder on the stick.
How can I update the Ubuntu version on the stick?
Answer: You can't (not easily anyway).

Windows Tools:
I recommend you download these and save them onto the USB stick you create yourself, to always have them on hand. I did not include them on the stick as they are licensed separately (even if "free") and all credits go to their respective authors. I also recommend downloading the Windows 8.1 drivers for the T100 and saving them to the same stick, just in case you have to re-install Windows. Just make a separate folder on the stick and save whatever you want there. It won't break any functionality.
EasyUEFI - Download
A tool which helps you manage UEFI boot entries, paths and configuration for booting with ease
Ext2Fsd - Download
A tool which helps you mount ro/rw the Android/Linux partitions in windows as regular drives
unsqashfs 4.0 - Download
A tool to extract the ".sfs" and ".squashfs" images to regular ".img" files (to make system.img writable, mountable etc.)
Advanced reboot script - Download
A Windows batch file that reboots the system so you can select the boot device using your touchscreen (boot in Android/Ubuntu directly without the dock attached etc.)
Linux how-to resources:
Unsquash FS: http://unix.stackexchange.com/questions/80305/mounting-a-squashfs-filesystem-in-read-write
Update grub: http://askubuntu.com/questions/281119/how-do-you-run-update-grub
Grub install to separate partition: http://askubuntu.com/questions/472669/install-grub-on-a-different-partition-on-triple-boot-system
Make IMG files: http://ubuntuhak.blogspot.ro/2012/10/how-to-create-format-and-mount-img-files.html
More grub: https://docs.oracle.com/cd/E26502_01/html/E28983/gkvif.html
Even more grub: http://superuser.com/questions/376470/how-to-reinstall-grub2-efi

Android How-to / guides section:
This section contains a set of guides to help you with some basic tasks and activities to easily manage your own installation(s) of Android. This is the part where the Magic Stick itself will prove to be useful and how you can use it to customize and repair or update anything. The Ubuntu related stuff is not documented here, as documentation and forums are available on the internet.
WARNING: These guides are not extremely detailed and include only the activities which have to be performed. Each configuration is different and you need to understand what you are doing to make sure you don't break anything. Worst case scenario is that you will lose all your data. However, you will still be able to boot the Magic Stick to repair or re-install everything (thank me later!)
DISCLAIMER: I am not responsible for any loss of data and you are at your own risk while using the tools, guides and information provided here. Back up your data and do not play around with systems that you use on a daily basis. Only follow these guides if you feel comfortable with the instructions and completely understand what you need to do at each step.
Make the Android system partition writable
When you download an Android-x86 release, you will find in the ZIP or ISO a bunch of files, including a file called "system.sfs" or "system.img".
If you have a file called "system.img" you can stop now, your Android system partition is writable and you can skip to the final step.
If you have a file called "system.sfs", then use the unsquashfs command to convert it into a writable format:
If you are using Windows, download the unsqashfs tool above and extract the zip. Drag and drop the "system.sfs" file on top of the unsqashfs executable to extract the system.img (you can find it inside the generated folder)
If you are using Linux, make sure squashfs-tools are installed and run this command from the folder containing the "system.sfs" file:
Code:
unsquashfs ./system.sfs
That's it, now you can mount the system.img file generated under linux using this command:
Code:
mount -o loop ./system.img /path/to/destination/
Resize the system partition
Usually, the system partition of Android-x86 is made as small as possible (you don't want to download "free space", right?) so if you want to add gapps or other packages to the system partition there will be no space left. Here's how to increase the size of the system partition:
Boot the Magic Stick into Ubuntu
Open a console using the Ctrl+Alt+T shortcut
Browse to the folder containing the system.img file (using 'cd' or 'mc')
Extend the system.img file by 200MB. Replace 200 with the amount of MB you want to add:
Code:
dd if=/dev/zero bs=1M count=200 >> ./system.img
Run gparted to also extend the partition inside the file:
Code:
sudo gparted system.img
In gparted, right click on the partition and select the option to shrink it down by only one MB (so it registers a change) and apply the changes
Close gparted. You're done.
Make space to install Android
Creating a new partition onto which to install Android usually requires shrinking an existing partition. If you want to install Android on the tablet (not the dock base) you will have to shrink the Windows system partition. Here's how to do it in a reasonably safe way:
Boot the Magic Stick into Ubuntu
Open a console using the Ctrl+Alt+T shortcut
Run gparted as root:
Code:
sudo gparted
In gparted, right click on the Windows system partition and select the option to shrink it down by at least 2GB. Make sure the partition actually has 2GB of free space, otherwise the process will not work.
Right click the free space and create a new partition and select to format it as ext4. It's important to make it ext4, so keep this in mind. Also give it a name such as "android".
Apply the changes and wait for the partition to be created.
Close gparted. You're done.
To have the partition available in Ubuntu Live, you have to mount it manually or just reboot (to have it mounted at boot automatically)
Install Android locally
Make sure you have the system.img, kernel, ramdisk.img and initrd.img files available. Make sure you have an ext4 partition mounted. The Android-x86 installation is in fact a simple process of copying the ISO/ZIP files onto the destination partition:
Boot the Magic Stick into Ubuntu
Open a console using the Ctrl+Alt+T shortcut
Copy the four relevant files to the ext4 partition using your method of choice
That's it, Android-x86 is installed (but not yet bootable!)
Enable data saving for Android
To enable data saving for Android-x86, you have many choices. However, the simplest one is to use an ext4 partition and create a dedicated "data" folder for android. Make sure Android-x86 is installed onto an ext4 partition:
Boot the Magic Stick into Ubuntu
Open a console using the Ctrl+Alt+T shortcut
Navigate to the root of the partition (the mount point folder)
Create a folder called "data":
Code:
mkdir -p data
You're done, Android will save data persistently across reboots.
Note that this only works for ext4 partitions.
Note that using ext2 or ext3 will output errors for Google Play if you use Lollipop builds.
You have been warned.
Install the grub2 boot loader
Resizing partitions and copying (read installing ) Android is a very simple process. However, the bootloader installation is a much more complicated business (usually!). Here's how to make sure everything is installed correctly:
In progress...
Add the Android menuentry to grub2
Once we have grub2 installed and ready to go, it's time to make Adroid-x86 bootable as easily as possible:
In progress...
Update Android with new releases
Once Android is set up and ready to go, all you need to do to update it properly is to overwrite the existing files and reboot. Make sure you have the updated system.img, kernel, ramdisk.img and initrd.img files available. Make sure you have the Android ext4 partition mounted:
Boot the Magic Stick into Ubuntu
Open a console using the Ctrl+Alt+T shortcut
Copy the four relevant files to the ext4 partition using your method of choice, overwriting the existing ones
That's it, Android-x86 is updated
Cheers,
C.

Reserved....

I am having some problems with this. Granted I am trying to use it for install on the Dell Venue 8 Pro. This tablet is a bay trail base, with most of the same hardware, minus the wireless/bt card. This works fantastic as a live cd, but when I install it I get problems. Is the ubuntu image only i386? When I was trying to change the kernel from the G+ group I kept getting the architecture mismatch (Kernel.deb file is amd64 and system is i386). Also the bootloader is kind of weird. All of the grub settings are correct, but if I want to boot ubuntu from the mmc I have to enter the advanced menu, then boot recovery mode. When recovery mode boots, I hit resume boot and then I am magically loaded into my installed system. Am I doing something wrong here?

The live image is i386 only. For the grub boot loader, try copying the entry contents into the stick boot menu and see if it works as intended. The menuentry file on the stick is in ./boot/grub/grub.conf.
I'll be releasing a new version of the stick with Ubuntu 15.04 (i386) and some additional sound fixes in the next few hours as well.
Cheers,
C.

Ok, v1.3 with new updates and fixes has been posted. Let me know of any improvements and/or problems.
Cheers,
C.

Thank you for great work! One promise: please, fix bug for HP Omni 10. My tablet can't boot in Ubuntu (but works perfectly with Android). Here is a link to the G+ posts with bug disc.
https://plus.google.com/105824122847813147186/posts/4G1BQgD5LNQ
https://plus.google.com/105824122847813147186/posts/gxqsVsNNJoq

The HP omni problem comes from the kernel, which I did not build and I do not maintain. Also, I don't have a HP omni, so I can't test it out.
The bottom line is that I can not promise to make it work, but I will update the kernel when possible. Keep in mind that this is a Asus T100 tool. Follow the thread and when an update for the kernel is posted, try the new version.
Cheers,
C.

Everything runs perfectly. Flawless Android and I'm still testing around Ubuntu. You've helped revitalize my T100! thanks!
Now I just need to figure out how to install the bootloader. Seems simple enough but your instructions say it may be a bit complicated so maybe I'm missing something

For some reason, after Ubuntu installed coulnd open the software manager and didnt have synaptics, also is there a way to turn of the white led,
second do i copy all the android files into the Ubuntu drive or i need to partition the ssd for another partition for android( what are the chances of 5.0/5.1)
thanks for the files and works good, only issue, not home dev but Linux/Ubuntu, that is not finger scroll friendly, and click and hold for right click(context menu) beside chromium that scroll with out having to hold the scroll bar like the rest of the system

It will be great, if you fix it. Thanks for reply!

""Login failed, impossible to establish a reliable connection to the server. This could be a temporary problem or your Android device may not be suitable for data services. If the problem persists, contact customer service. ""
Gives me this error every time I try to log in with my google account. Solutions?

Installation on hdd
I have installed ubuntu on my t100 on the hdd. It works great so manu thanks for that but I have on issue, I need to let the usb stick in on boot in order to make it boot. If I don't grub is in rescue mode saying that : "error : no such device : 25dc1ad7-c268…"

Is there any way to get touch screen working on a Toshiba Encore 2 Write? I know this thread is for the Asus T100, but I tried this flash drive image out on my device and it ran, minus touchscreen. It booted up fine and everything. If anyone is able to help me out, it would be greatly appreciated! I think the issue stems from the device having a Wacom touchscreen, but I can give any information needed!

@feduss: The connection problem did not appear in my tests and I am able to log into Google Services without any problems. Skip the account creation during the initial setup wizard and create it later and see if it works.
@alphaeagle777: try installing plasma-active. You can see it in action here: https://www.youtube.com/watch?v=mOMmp8iEaqY
@Macro le noir: Make sure you select /dev/mmcblk0 as the drive to install the grub2 boot loader during installation. Otherwise, the installer may detect the USB stick grub boot loader and install the OS selection menu for Ubuntu from there.
@FiendFyre: The stick will never have Encore 2 support unless one of the kernel developers include it in the configuration. I am not building the kernels myself, so it is best to ask the Android-x86 group for more info.
Cheers,
C.

I tried already to login later...maybe i'll solve the problem creating a new account

cheatman said:
@Macro le noir: Make sure you select /dev/mmcblk0 as the drive to install the grub2 boot loader during installation. Otherwise, the installer may detect the USB stick grub boot loader and install the OS selection menu for Ubuntu from there.
Cheers,
C.
Click to expand...
Click to collapse
Thanks for the reply. It was the correct issue, I didn't pay attention during installation. To solve the problem I juste reinstall grub at the right place.
edit : I speak to fast. Just reboot work, not after a shut down.
edit2 : after reinstalling ubuntu with grub at the rigth place, it still doesn't work. Can you explaim me how to install grub correctly ?

Grub entry
Hi cheatman, thanks for your great work and nice tutorials. Now I am trying to figured out, how to edit grub to add entry for android. It is situated in /dev/mmcblk0p5 in folder android. I have alrready installed ubuntu on keyboard HDD. Thanks.

[WinApp][v2.4-Beta][+RemixOS] Android-x86 Installer UEFI Version

Code:
*** Disclaimer
Use this software at your own Risk,I am not responsible for any damage that may be caused by this software.
I have tested it on all machines i have, don't know if you have any special cases.
Description
This Installer will let you install Android x86 on your PC like any other application, no risk to Damage HDD Partitions, Boot Data or User Data. After installation you will got an option at boot to select Windows or Android.
This Installer is currently targets only Windows 8 / UEFI-Enabled Devices​
System Requirements
UEFI-Enabled x86 PC
Secure Boot Disabled
Bitlocker disabled on target drive
Windows 8/8.1/10
.Net Framework 4.5
Android System image with UEFI Support
Screenshot
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Change log
v2.4
Update Detection of RemixOS image [Use RemixOS ver: B2016012301 or higher]
Fix UEFI Init Fail with Surface Pro devices
v2.3
Add support for RemixOS
v2.2
Fix reading large UEFI entries
Fix using img file from path with spaces
Trial period Removed
Add GPU Options to GRUB Bootlist
v2.1
User-defined Data size
Responsive UI
Installation Status update
Support Devices with 32-bit firmware
Support booting from NTFS with compression enabled
log includes more info about Device BIOS
v2.0
Initial Version
Features
Install/Uninstall Android directly from Windows
Support UEFI-Enabled devices
Support legacy BIOS devices [not available in Alpha version]
Install to Any FAT32/NTFS partitions
Instructions
Install
Download Android EFI Enabled img file from: [LINK]
Launch the Installer
Select the downloaded IMG file
Select "Data Size" for file which will be used to store downloaded Apps and User Settings
Select the partition which Android will be installed to.
Click Install and wait ... The installation will take about 5 min. or less, it is based on your hard drive speed.
How to Enter Android
Go to Windows power menu and Click on "Restart" while holding shift [Screenshot]
Select "Use a device"
Select "Android-OS"
Now your PC will reboot to Android
Uninstall
Launch the Installer
Select "Cleanup Android"
Under the hood
The installer will verify the system requirements on launch
directory: "<TargetPartition>AndroidOS" will be used for installation
Extract the IMG file
Create user data partition
Install grubx64 to UEFI partition
Install new UEFI boot entry for Android
Downloads:
For UEFI-Enabled PCs: [UEFIInstallerv24-5800.exe]
For Legacy-BIOS PCs: [Old Thread]
Important notes (Read it carefully)
This version for testers only, not for end users
Please don't redistribute this version of the installer
Please please report your device model and if installation was successful or not
Any bug/problem/issue reported shall have installer log (which can be found in your C: ) attached and a screenshot
you can read the log before sending it if you have any privacy concerns
The installer will not allow installation on non-UEFI Devices for now
Verify that you downloaded .IMG file not .ISO file
if you have found a bug inside Android you should contact android-x86 team not to post here
Your feedback is highly appreciated
XDA:DevDB Information
Android-x86 Installer for Windows, Tool/Utility for the Windows 8 General
Contributors
ExtremeGTX
Version Information
Status: Beta
Current Beta Version: V2.4
Beta Release Date: 2016-02-05
Created 2015-10-15
Last Updated 2016-02-13

Looks amazing, gonna try it for sure, thanks for this tool!
EDIT: Tried it (ASUS T100TAM, Windows 10 x86), installation failed unfourtunately. Adding log from installation:
================Installer Info================
Installer Directory:C:\Users\****\AppData\Local\Temp\droidinst_efi
Installer Version:2.0.5761.39882
Secure Boot ... Disabled
Manufacturer: ASUSTeK COMPUTER INC.
Model: T100TAM
Product: T100TAM
BIOS Version: T100TAM.204
Available GPU(s):
GPU: Intel(R) HD Graphics
=============[REQUIREMENTS CHECK]============
Administrator privilege ... ok
OS Type: ... fail
==========================================
====Install Started on 18.10.2015 10:52:53====
-ISO File: C:\Downloads\android-x86-4.4-r3.iso
-TargetDrive: C
-UserData: 1000k
-Setup Directories...
-Folder Created: C:\AndroidOS
-Extract ISO
#Launch:C:\Users\****\AppData\Local\Temp\droidinst_efi\7z.exex C:\Downloads\android-x86-4.4-r3.iso "kernel" "ramdisk.img" "initrd.img" "system.sfs" -oC:\AndroidOS
-Extract SFS
#Launch:C:\Users\****\AppData\Local\Temp\droidinst_efi\7z.exe x C:\AndroidOS\system.sfs "system.img" -oC:\AndroidOS
-Create Data.img
#Launch:C:\Users\****\AppData\Local\Temp\droidinst_efi\dd.exeif=/dev/zero of=C:\AndroidOS\data.img ibs=1k count=1000k
-Initialize Data.img
#Launch:C:\Users\****\AppData\Local\Temp\droidinst_efi\mke2fs.exe-F -t ext4 "C:\AndroidOS\data.img"
===Installing Boot Objects===
-Mounting EFI Partition...
#Launch:C:\Windows\System32\mountvol.exe Z: /S
-Setup Boot Directory...
-Boot Folder Created: Z:\EFI\Android\
-Copy Boot files
-Add UEFI Entry
UEFI Init Fail
==============Revert Installation==============
-Cleaning up Android Directory ... C:\AndroidOS
===Removing Boot Objects===
-Mounting EFI Partition...
#Launch:C:\Windows\System32\mountvol.exe Z: /S
Error Executing C:\Windows\System32\mountvol.exe with Args: Z: /S
Error output:
Folder is not empty.
-UEFI Init ... fail
-Cleaning up Android Directory ... Z:\EFI\Android\
-UnMounting EFI Partition...
#Launch:C:\Windows\System32\mountvol.exe Z: /D
==========================================
Click to expand...
Click to collapse

Check the New version
v2.1
User-defined Data size
Responsive UI
Installation Status update
Support Devices with 32-bit firmware
Support booting from NTFS with compression enabled
log includes more info about Device BIOS

ExtremeGTX said:
Code:
*** Disclaimer
Use this software at your own Risk,I am not responsible for any damage that may be caused by this software.
I have tested it on all machines i have, don't know if you have any special cases.
Click to expand...
Click to collapse
I get an error saying no kernel is installed
error no such device /AndroidOS/system.sfs
error file /AndroidOS/kernel not found
error you need to load the kernel first
EDIT: Also as a note both those files exist in C:\AndroidOS\system.sfs and C:\AndroidOS\kernel

ChrisJ951 said:
I get an error saying no kernel is installed
error no such device /AndroidOS/system.sfs
error file /AndroidOS/kernel not found
error you need to load the kernel first
EDIT: Also as a note both those files exist in C:\AndroidOS\system.sfs and C:\AndroidOS\kernel
Click to expand...
Click to collapse
it seems like bootloader can't access your Disk!
can you please post a screenshot of "Disk Management" :
- Open run and type: diskmgmt.msc then take screenshot like this [LINK]
- OR open start menu and type Disk Management

New version works perfectly! No problems at all, just tried Android x86 4.4 and Android x86_64 5.1 aswell on ASUS T100TAM (32GB version), both worked without any trouble - thanks a lot for this amazing tool!
Anyway a small question here - is it possible to create a shortcut in Windows, that could restart device directly into Android? Just a quick guess

spenat said:
New version works perfectly! No problems at all, just tried Android x86 4.4 and Android x86_64 5.1 aswell on ASUS T100TAM (32GB version), both worked without any trouble - thanks a lot for this amazing tool!
Anyway a small question here - is it possible to create a shortcut in Windows, that could restart device directly into Android? Just a quick guess
Click to expand...
Click to collapse
Thanks , kindly post the installation log found at C:\AndroidInstall_XXX.log as this give me info about conditions where installation is successful/unsuccessful
For booting to Android we may have 2 options:
- Desktop shortcut "Reboot to Android"
- Set GRUB as default bootloader

ExtremeGTX said:
Thanks , kindly post the installation log found at C:\AndroidInstall_XXX.log as this give me info about conditions where installation is successful/unsuccessful
For booting to Android we may have 2 options:
- Desktop shortcut "Reboot to Android"
- Set GRUB as default bootloader
Click to expand...
Click to collapse
I think, that setting GRUB as default bootloader would be definitely great way to do this. But, of course, whatever you think it's better and/or easier to do
Anyway, my device is (as stated before) ASUS T100TAM (Intel Atom z3775, 2GB RAM, UEFI device), running Windows 10 Home x86. Secure boot, of course, disabled. Adding install log as an attachment.

So to make it clear,
1. I don't have to re partition the SSD, right?
2. The android will be installed in c:/androidos?
3. What you mean about "create user data partition"? Is it going to change disk partition and create dedicated one for it?
Thanks
Sent from my Nexus 5 using Tapatalk

dokie80 said:
So to make it clear,
1. I don't have to re partition the SSD, right?
2. The android will be installed in c:/androidos?
3. What you mean about "create user data partition"? Is it going to change disk partition and create dedicated one for it?
Thanks
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
I am not the creator of this app, but since I used it succesfully, I can definitely answer these questions:
1. No, you don't need to worry about that.
2. Yes, exactly - all data will be in this folder (as it is on my TF100)
3. It creates "data.img" file inside the "C:\androidos" folder and you can select how big that .img file should be (for storing your Android data). No partitioning - basically everything happens inside the "androidos" folder.

Thanks for the reply.
Whats the benefit of this method over the magic stick one anyway ?
I'm going to try this tomorrow
Thanks
Sent from my Nexus 5 using Tapatalk

dokie80 said:
Thanks for the reply.
Whats the benefit of this method over the magic stick one anyway ?
I'm going to try this tomorrow
Thanks
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
The biggest benefit is (obviously) that you don't need any flash drive for this - everything is done from your tablet's memory (basically a dualboot) and it's very, very easy to do this.

AFAIK, you can install the android x86 to via magic stick, although I haven't try it yet. I'm using it for Ubuntu. Did you use it daily? How about battery life and performance? Can't wait to try
Sent from my Nexus 5 using Tapatalk

Well yeah, you can, but AFAIK you would have to do repartitioning as if you were installing regular dualboot system - that's something you don't have to do here.
Performance is great as expected, very snappy, I've been running KitKat 4.4-r3, Lollipop 5.1 was very unstable for me. Battery life seems great, too, not exactly sure though, since I've been playing with it for two days now

spenat said:
I think, that setting GRUB as default bootloader would be definitely great way to do this. But, of course, whatever you think it's better and/or easier to do
Anyway, my device is (as stated before) ASUS T100TAM (Intel Atom z3775, 2GB RAM, UEFI device), running Windows 10 Home x86. Secure boot, of course, disabled. Adding install log as an attachment.
Click to expand...
Click to collapse
Thanks for posting the log.
My only concern with setting GRUB as default bootloader if GRUB has a problem running on the device the user may think that the device is bricked and no longer usable, anyway we will check back on that.
dokie80 said:
So to make it clear,
1. I don't have to re partition the SSD, right?
2. The android will be installed in c:/androidos?
3. What you mean about "create user data partition"? Is it going to change disk partition and create dedicated one for it?
Thanks
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
exactly as @spenat told you.
the Advantage of this installer is you will not mess up anythings, no re-partitioning at all or corrupting the current installation of windows. All of the magic just live in <Drive:>\AndroidOS
and if you don't like it you can launch the installer and click on "Cleanup Android" you can check all installation steps in log if you have any concerns.
Thanks
spenat said:
I am not the creator of this app, but since I used it succesfully, I can definitely answer these questions:
1. No, you don't need to worry about that.
2. Yes, exactly - all data will be in this folder (as it is on my TF100)
3. It creates "data.img" file inside the "C:\androidos" folder and you can select how big that .img file should be (for storing your Android data). No partitioning - basically everything happens inside the "androidos" folder.
Click to expand...
Click to collapse
spenat said:
Well yeah, you can, but AFAIK you would have to do repartitioning as if you were installing regular dualboot system - that's something you don't have to do here.
Performance is great as expected, very snappy, I've been running KitKat 4.4-r3, Lollipop 5.1 was very unstable for me. Battery life seems great, too, not exactly sure though, since I've been playing with it for two days now
Click to expand...
Click to collapse
Thanks for your clear answers, appreciate your help

installing now. will I be able to change data size later?

dokie80 said:
installing now. will I be able to change data size later?
Click to expand...
Click to collapse
You can only change data size before you actually install the Android. If you wanna change it later, you need to remove Android and install it again with different data size, AFAIK.

working fine here T100TA, well.. the installation that is.
on android x86, I got a freeze on wifi setting... force close and re-set works fine..
if you dont mind me asking questions:
1. what method are you using for this to work? I dont need it to be detailed, I just curious what's it called, and how AndroidOS listed on device option on advanced boot
2. how to do nandroid backup? I assume for "dirty flash" : I backup data.img and put back after new installation? with the downside is data size is from previous setup?
3. I see that sdcard is mounted, but havent try to see it with file explorer, I assume the whole C: is mounted or probably only AndroidOS folder? so I can do Titanium Backup saved there?
4. for now, I have to boot to windows and boot to android using advanced boot? so without keyboard attached, I have to choose settings - recovery - advanced startup? will it be possible to boot using grub bootloader? I'm planning to dual boot with linux later. just realize that it also show up on boot selection.
many thanks for this. attached is the log found at C:

dokie80 said:
working fine here T100TA, well.. the installation that is.
on android x86, I got a freeze on wifi setting... force close and re-set works fine..
if you dont mind me asking questions:
1. what method are you using for this to work? I dont need it to be detailed, I just curious what's it called, and how AndroidOS listed on device option on advanced boot
2. how to do nandroid backup? I assume for "dirty flash" : I backup data.img and put back after new installation? with the downside is data size is from previous setup?
3. I see that sdcard is mounted, but havent try to see it with file explorer, I assume the whole C: is mounted or probably only AndroidOS folder? so I can do Titanium Backup saved there?
4. for now, I have to boot to windows and boot to android using advanced boot? so without keyboard attached, I have to choose settings - recovery - advanced startup? will it be possible to boot using grub bootloader? I'm planning to dual boot with linux later. just realize that it also show up on boot selection.
many thanks for this. attached is the log found at C:
Click to expand...
Click to collapse
Thanks for testing and posting the install log
Answers:
1. Check section "Under the hood" in the first post or check the installer log you have posted, it will give you an idea about the magic
2. This is an old request from a few users to allow reinstall/update android without removing userdata. Till now your workaround is valid, I think you will see message like this one [LINK] at the first boot after upgrade.
3. I 'm not sure right now.
4. here are 2 solutions to access Android:
a Shortcut on Desktop "Reboot to Android"
Set GRUB as default Bootloader, I can't do this right now as the app still in alpha stage and a lot of testing is needed. i don't want to mess up devices with something not ready yet, so currently i just add GRUB to UEFI Boot options but don't make it the default one.
Thanks for your feedback and questions

Just a quick tip to make dual-booting even easier:
Set the "Boot Option #1" in BIOS to Android-OS (instead of Windows Boot Manager), this way it will always boot to GRUB. Just one catch: You will need a keyboard to move in GRUB, or you will always boot to Android But, of course, you can anytime switch back to Windows Boot Manager as default, as long as you can access BIOS
Anyway, just tried this app on my brother's tablet (Lenovo Miix 3 10"), will add installation log ASAP.