Related
Hello everyone.
You should know that time ago Motorola decided to stop updating our Xoom, but we showed (and we are still showing) them that our tablet is still alive and kicking.
Let me update this with the last news (a big win, indeed) from @bigrushdog:
IMPORTANT: It should be harmless for your Xoom, but you need to do it at your own risk. Nobody will give you any kind of warranty and we will be not guilty if your Xoom bricks, dies, loses the data, gets cursed, your cow starts to give bitter milk or if it unchains a thermonuclear war.
bigrushdog said:
BigPart Repartition Upgrade and Resource Center
Credits
Much love, credit, and respect go out to @Schischu and @rchtk! Your insight on the kernel patch paved the way! The Motorola Xoom cheats death once again!
Repartition Guide
1) Your data will be totally wiped! If you have Nandroids, TitaniumBackups, or anything of any value on your internal storage, copy them to your microsd or computer! They will be gone forever! Your microsd card is the only safe haven on your Xoom during this process.
2) Put all needed resources on your microsd card! You will need the original TWRP 2.6.3.0 touch recovery from @runandhide05, TWRP 2.6.3.0 BigPart version, your desired rom, and the BigPart boot image that goes with your desired rom. The BigPart boot images can be found in the next section.
3) Reboot into recovery. Flash TWRP BigPart. Don't reboot just yet.
4) Go back into wipe menu and wipe everything but /sdcard.
5) Go to reboot menu and reboot into recovery. Disregard the "No OS" warning and don't install SuperSU when asked.
6) When you come back into recovery, it will think your data is encrypted but it's not. Go into wipe menu and "format data". Type "yes" when prompted. When done, go back into wipe menu. Select "Advanced Wipe". Check "system" and "cache" and wipe them.
7) Hit Home then go to reboot menu and reboot recovery. Once again, disregard "No OS" warning and don't install SuperSU when asked
8) When you come back into recovery, go into mount menu. You should see "cache" and "data" checked. "System" will be unchecked. Check it to confirm it mounts, then uncheck it. Congratulations! You are now repartitioned!
9) Go into install. Recovery should show your microsd storage by default. If not, using the navigation panel, navigate to root then go into "sdcard". Flash your rom, BigPart boot image package, and any other resources as you normally would.
10) Reboot into system. You are done!
Later.... How to restore to stock partitions.
TWRP 2.6.3.0 R.A.H BigPart Edition Recovery
TWRP 2.6.3.0 BigPart
BigPart Eos 4 boot images with the usual modules
WARNING: You must have already executed the repartition before using these boot images. If not, follow the guide above! These will soft brick your device otherwise!
Eos 4 BigPart Wingray Boot Image
Eos 4 BigPart Stingray / Stingray_CDMA Boot Image
Eos 4 BigPart Everest Boot Image
CM10.1 BigPart Kernel by @matt4321
http://d-h.st/IzQ
For CM10.1, follow instructions in the OP but when getting to the flashing of ROMs, flash CM10.1, then flash thi
BigPart @dreamcwli MyWingray 4.3 (or in theory any 4.3) boot image with the usual modules
Note: This is a new kernel rebased on @dreamcwli 's tree. No overclock or gpu overclock yet, but soon ;D
WARNING: You must have already executed the repartition before using these boot images. If not, follow the guide above! These will soft brick your device otherwise!
MyWingray 4.3 BigPart wingray Boot Image
Click to expand...
Click to collapse
Q&A
Q: OK to understand this right, now we have a new recovery and boot. Which ROM do we use? The same as before? And BigPart @dreamcwli MyWingray 4.3 is only for wingray?
A: Yes, we have new recovery and boot. For this recovery and boot you need to use the new BigPart roms. If you are not using BigPart roms, you will need to install old recovery and boot and format everything again. And yes, it seems like @dreamcwli MyWingray 4.3 is only for wingray at the moment, but brd published a version of the last EOS4 stable with the new kernel working for BigPart.
Q: Does this new space mean we can start using full blown GApps Instead of the scaled down versions we had been previously?
(I understand there may be NEON ramifications causing a NO Answer here)
A: You can use the GApps that you prefer. Now we have space enough, but scaled down versions might be slightly faster as it uses less resources (I guess).
Q: Seems like a good time to ask and reveal my limited understanding of why user space is formatted vfat. I'm a linux fan who dislikes being limited to 4096 Mb when creating a linux.img. A yes or no answer will suffice. As long as the devs are pushing the limits, can the user space (sdcard) be formatted ext2, 3 or 4?
A: I think that that is something to implement in the kernel. I think that it is easy to do and our bakers eventually will implement it.
Q: Can cm10.2 be flashed instead of an eos4 rom after the repartition?
A: You need to replace BOOT.img in the CM zip with the BigPart compatible with your Xoom, and if the kernel is compatible with CM it will work.
Q: I'm on stingray_cdma.....unless i can flash a wingray rom and boot.img after the repart?
A: No idea, but it's safer to use roms build for your device. Take a look to the previous question.
Q: im on stingray and i tried using cm10.1 as my rom and it didnt get to the bootanimation so i tried eos 3 and it works well. couldnt get eos 4 to download from goo.im
A: brd published some EOS4 working with BigPart (see http://forum.xda-developers.com/showpost.php?p=47005701&postcount=1 )
Q: I am asking again to understand this right, now we have a new recovery and boot.
Which ROM do we use? The same as before? Do we have to change the boot IMG in the ROM with the big part one?
And BigPart @dreamcwli MyWingray 4.3 is only for wingray or it can be used with everest as well? And what is its difference with the other big part in the kernel?
A: Use only BigPart roms. You will need to change the boot.img from the rom if the rom is not compatible with BigParts, but if the rom is not compatible with the new kernel, it is useless... MyWingray is compatible with Everest but you will not have 3G, I guess... But I'm not sure.
Q: That's great. @bigrushdog @realjumy Is there a way to get the radios for everest and stingray on a separate zip?
A: The rom must be cooked with the radios...
Q: I wanna ask you because i have my xoom forma two years, and laste time i format it and give me error with dev block mmblck or something else and i think that i could have my internal storage corrupt.. If i install your 4.3 image modded, and then the repartition, Will it works fine?? Thanks and sorry me
A: No idea.
Q: Followed the instructions for the re-partitioning. Everything worked except the Xoom cannot see the external sd card in recovery. I have re-formated it as fat32 and tried another card. When I view the files in the PC they are there. Any ideas?
A: Something something went wrong... Copy the data from the SD to your PC, format SD and put back data. Let's see if that works...
Q: How can we identify which ROMs are for the new partition layout? Just assume everything 4.3 and later? It would be nice if we added [BigPart] to the thread title to make them more easily identifiable.
A: Only roms with BigPart in their name can be used with the new layout.
Q: I was under the impression that we could use old roms provided we replaced the boot.img in the zip with the NEW BIGPART boot.img for our unit? (Only after repartitioning has been completed) Is that wrong and we need to wait for a particular build?
A: Not all the roms are compatibles with the boot.img method (kernel method). You will need to try to be sure. EOS4 and Dream's have proper versions. If you want to use, for example, CM you will need to:
option 1.- Build it yourself patching the kernel
option 2.- Use CM and try to use a different kernel
option 3.- Ask to the CM maintainer to release BigPartition versions.
There is a lot of 4.2.2 projects running, some 4.3 and if we are successful, MAYBE we will be able to port 4.4 to our devices. One of the main problems (but not the only one) is the internal storage structure of the tablet. It seems that is not too hard to solve, as in other devices (mainly Samsung) is common to change it.
The aim of this project is to compare how the internal partitions are setted up in order to change them and have more room for system and apps. This will improve all the ROMS (4.1, 4.2.*, 4.4). @bigrushdog is doing a big effort to change it but we need more data from all models to compare and be sure that we don't break anything.
It will take up to 3 hours (depends on the model) but is something that can work while you are sleeping or not using the tablet. With the data provided by you, we can compare and choose the best changes.
IMPORTANT: It should be harmless for your Xoom, but you need to do it at your own risk. Nobody will give you any kind of warranty and we will be not guilty if your Xoom bricks, dies, loses the data, gets cursed, makes your cow begin to give bitter milk or if it unchains a thermonuclear war.
IMPORTANT: It should be harmless for your PC, but you need to do it at your own risk. Nobody will give you any kind of warranty and we will be not guilty if your PC bricks, dies, gets cursed, loses the data, makes your cow begin to give bitter milk or if it unchains a thermonuclear war.
What are you going to do:
You are going to do a 1:1 copy of your internal storage into your PC. Then, we will detect the partitions and where begins and ends each one. Nothing else. We will compare the different versions and in the future a tool will be released to make the changes.
What you will need:
Linux (maybe you can use a Live DVD / USB?). It should be a way to do this process under Windows. If you know how to do it, please, share the info.
33GB of disk space in your computer, anywhere.
Android SDK working (that means that if you plug your tablet turned on and run
Code:
./adb devices
in the folder "platform-tools" of your SDK will provide a serial number): http://developer.android.com/sdk/index.html
3 hours (can be done while sleeping, not using the tablet, etc) if you have a 32GB Xoom.
Rooted Xoom.
Before you begin:
DO A NANDROID BACKUP!!!!!
READ EVERYTHING AND ASK IF YOU DON'T UNDERSTAND SOMETHING
Step by step:
Full charge your tablet (or keep it connected to AC?) and turn it on WITHOUT SDCARD.
If your Android SDK is not installed or working properly, fix it now: http://developer.android.com/sdk/index.html
Install the dependencies. For Ubuntu / LinuxMint / Debian:
Code:
apt-get install testdisk netcat pv extundelete testdisk
Activate USB Debug on your device (in order to connect with adb). You can find it under Settings > Developer options.
Note: On Android 4.2 and newer, Developer options is hidden by default. To make it available, go to Settings > About phone and tap Build number seven times. Return to the previous screen to find Developer options.
Click to expand...
Click to collapse
Plug your tablet (it must be on) and run
Code:
./adb devices
in the folder "platform-tools" of your SDK. If you don't get as a result a serial number, STOP. Something is wrong with your SDK. Please, fix it to continue.
Open a terminal on your computer, go to the Android SDK directory's subdirectory sdk/platform-tools (where adb is located).
We will setup a forward port to be able to download the data to our PC:
Code:
./adb forward tcp:5555 tcp:5555
Now we will connect to the tablet
Code:
./adb shell
Maybe you need to grant permission to do it. Take a look to your tablet's screen.
We become superuser:
Code:
su
Grant permanent permissions when asked. You can revoke the permissions later if you want.
With this we will transfer the data to the port that we set previously:
Code:
/system/xbin/busybox nc -l -p 5555 -e /system/xbin/busybox dd if=/dev/block/mmcblk0
DON'T CLOSE THAT TERMINAL. An now OPEN A NEW ONE IN THE PC.
Go again to the folder "platform-tools" of your SDK and let's collect the data:
Code:
./adb forward tcp:5555 tcp:5555
Code:
nc 127.0.0.1 5555 | pv -i 0.5 > mmcblk0.raw
If you want to save the file in a different place/partition, change what is after ">". For example, if I want to save the file in my home folder, I will write /home/jumy/mmcblk0.raw. If you are not sure or don't know how to do it, don't change it.
You will to wait up to 3 hours until it finish.
When the transfer is finished, run this in the folder where the dump is located (if you changed nothing, it is located in the older "platform-tools" of your SDK):
Code:
testdisk mmcblk0.raw
First restore the GPT partition table. Select mmcblk0.raw in the TestDisk interface and choose Proceed.
Choose EFI GPT.
Then select Analyse.
Choose Quick Search.
The search will return a table that you should copy and paste in this thread.
Now you can exit and remove the dumped file (mmcblk0.raw).
Please, when you provide the data, tell us which model, storage size, ROM name and version and indicate if it is the Hong Kong model.
Info collected from http://www.df.lth.se/~jokke/androidfilerecovery/ --> Visit it if you want some screenshots.
Everest, 32GB, using EOS4 V170, NOT Hong Kong model.
Code:
Partition Start End Size in sectors
>P MS Data 47104 51199 4096
P MS Data 61440 65535 4096
P MS Data 122880 647159 524280
P MS Data 647168 993279 346112
P MS Data 993280 62319583 61326304
Ill Help!
Testing in progress... =]
Device: XOOM 32GB Wingray MZ604
Android: 4.2.2
ROM: EOS4 Nightly 203
EDIT: i did my bloody SD card... did it again and now heres the internal 32GB
Code:
Disk mmcblk0_1.raw - 31 GB / 29 GiB - CHS 3880 255 63
Partition Start End Size in sectors
P MS Data 47104 51199 4096
P MS Data 61440 65535 4096
P MS Data 122880 647159 524280
P MS Data 647168 993279 346112
P MS Data 993280 62319583 61326304
4.4
No problem for test
Would love to test
I would really love to test Android 4.4 on my Xoom... The new platform seems to be much faster and my Xoom feels very slow and clumpy on Android 4.2 and even 4.1
djripster said:
I would really love to test Android 4.4 on my Xoom... The new platform seems to be much faster and my Xoom feels very slow and clumpy on Android 4.2 and even 4.1
Click to expand...
Click to collapse
4.4 will have the same problem that 4.2.* and 4.3 as it is a problem with the storage. That is the reason why we need so badly to change the partitions, and that is why we are asking for help to collect this data.
I'm running it now!
Sent from my Xoom
notbrodie said:
I'm running it now!
Sent from my Xoom
Click to expand...
Click to collapse
That's great!!!!
i got no Linux box. will see if i can do some research over the weekend on Windoze tools.
I derped my development laptop so I was down a few days. I think we have what we need for a repartition script. As some of you know kitkat source dropped. Under the hood, not much changed. At least from what I hear. So I'll slap together a theoretical repartition script. Any volunteers?
realjumy said:
That's great!!!!
Click to expand...
Click to collapse
Disk mmcblk0.raw - 1967 MB / 1875 MiB - CHS 240 255 63
Partition Start End Size in sectors
>P MS Data 47104 51199 4096
P MS Data 61440 65535 4096
P MS Data 122880 647159 524280
P MS Data 647168 993279 346112
P MS Data 1860958 1862168 1211 [\^I]
Xoom WiFi 32GB EOS-203, Not Hong Kong.
also: 3 hours... lol. it took 18 minutes
---------- Post added at 08:09 PM ---------- Previous post was at 08:06 PM ----------
bigrushdog said:
I derped my development laptop so I was down a few days. I think we have what we need for a repartition script. As some of you know kitkat source dropped. Under the hood, not much changed. At least from what I hear. So I'll slap together a theoretical repartition script. Any volunteers?
Click to expand...
Click to collapse
Count me in! i've got a nandroid on my external sdcard, though I'm not sure what good that'll do if the repartitioning fails...
---------- Post added at 08:18 PM ---------- Previous post was at 08:09 PM ----------
about to load 4.4 on my N4... let's see if this super-hyped new android is really that much different/better than 4.3!
Model: MZ604 (wifi-only)
Storage size: 32GB
ROM: EOS Stable release 3.0
NOT Hong Kong model
testdisk output:
Code:
Disk mmcblk0.raw - 32 GB / 29 GiB - CHS 3892 255 63
Partition Start End Size in sectors
>P MS Data 43008 47103 4096
P MS Data 57344 61439 4096
P MS Data 118784 643063 524280
P MS Data 643072 989183 346112
P MS Data 989184 62512095 61522912
Took a bit more than 3 hours...
notbrodie, there may be something wrong in your experiment as the dump file is only around 2GB. Or maybe you just have non-standard partitioning, I am not sure...
PS: Small correction to the instructions (just to make it perfect):
- closing code tag seems to be lost in ./adb shell command
- A typo in "If you want to save the fine"
Thank you guys!
Sent from my Nexus 4 using Tapatalk
DaniLoveSky said:
Model: MZ604 (wifi-only)
Storage size: 32GB
ROM: EOS Stable release 3.0
NOT Hong Kong model
testdisk output:
Code:
Disk mmcblk0.raw - 32 GB / 29 GiB - CHS 3892 255 63
Partition Start End Size in sectors
>P MS Data 43008 47103 4096
P MS Data 57344 61439 4096
P MS Data 118784 643063 524280
P MS Data 643072 989183 346112
P MS Data 989184 62512095 61522912
Took a bit more than 3 hours...
notbrodie, there may be something wrong in your experiment as the dump file is only around 2GB. Or maybe you just have non-standard partitioning, I am not sure...
PS: Small correction to the instructions (just to make it perfect):
- closing code tag seems to be lost in ./adb shell command
- A typo in "If you want to save the fine"
Click to expand...
Click to collapse
Thanks mate. I will correct the post later from the PC.
Sent from my Nexus 4 using Tapatalk
I'm dumping stingray right now. From what i can see, it already looks like the offsets are different for different models. That's very good to know. So calculations will need to be made for each version. After talking with @Roach2010 he says there may be partition table info that needs updating somewhere in the NAND dump. However, it doesn't appear that is the case for all devices. Once i get this dump we can play some more.
EDIT: found some interesting information http://forum.xda-developers.com/showthread.php?t=1388996
You guys... are brilliant... I'm in. My Xoom is just collecting dust since Eos shutdown.
also guys im getting my nexus 5 by the end of the week, let me know if you want any information extracted from that ! will be rooting that m*****f***er soon as! which leaves me with 2 dev devices XOOM and S2
I have a mz605 umt_everest model, at monday in my lab I will do this and post here.
bigrushdog said:
I'm dumping stingray right now. From what i can see, it already looks like the offsets are different for different models. That's very good to know. So calculations will need to be made for each version. After talking with @Roach2010 he says there may be partition table info that needs updating somewhere in the NAND dump. However, it doesn't appear that is the case for all devices. Once i get this dump we can play some more.
EDIT: found some interesting information http://forum.xda-developers.com/showthread.php?t=1388996
Click to expand...
Click to collapse
Nice find, so by doing this research and analysis it will be possible to create a universal partition structure (in terms of the XOOM versions). am i right in thinking this?
LOGMD said:
Nice find, so by doing this research and analysis it will be possible to create a universal partition structure (in terms of the XOOM versions). am i right in thinking this?
Click to expand...
Click to collapse
No... Whit this we will be able to:
1.- Check if every Xoom version have the same or different partition structure (done, each model has a different structure).
2.- See how every model need to be restructured (pending, that will be next step).
3.- Provide a script to make it easy to do (we need to do the 2nd step first).
Sent from my Nexus 4 using Tapatalk
MANIFEST:
Hi again dear magldr users. We have a superb multi os bootloader, magldr and its OS flashers, DAF and DWI since 2011. They are important tools for our Leos, as you already know. But espacially DAF has limitations about flashing size. For example; if you use tmous hd2 with 1024mb nand memory, you cant create 600 MB system partition. If you use eu (wwe) with 512mb nand memory, you cant access full of your nand memory and you can only use its 400mb.
So I tried to remove this limitations and I success. As I writed detailed before, I understood magldrs mtty partition structure and said "I will write an android flasher with this info" on that thread. The day came You can see this: http://androidforum.tytung.com/understanding-amagldr-s-partition-structure-via-mtty-t56.html
I used batch, vbs, mortscript scripts and created a tool which communicates with magldr via mtty bridge and can partition nand memory without any limitation.
Click to expand...
Click to collapse
FEATURES:
- You can use your full nand on eu (up to 444mb) and tmous (up to 956mb) with use last 24 mb feature(1mb reserved for misc partition)
- You can create system partitions on eu up to 420mb (for dataonext method) and tmous up to 850mb.
- It calculates data partition size automatically. So you only enter recovery, boot, system and cache size. Tool will show you remained free storage every step.
- You can skip partitions. For example, you can remove cache partition and can create only system,data,boot partitions. If you skip all partitions, it adds all size data partition. (WTF, What should I do rather)
- Its partition table like this; misc, recovery, boot, system, cache, data. And this tool doesnt erase your nand memory. So for example you can resize system partition without losing misc, recovery and boot partitions. (You should wipe system, cache and data partitions and restore them from backup)
- Finally this tool totally opened, you can open it with winrar and modify.
Click to expand...
Click to collapse
TEST STAGE:
I tested it for 18 hour with nearly 100 repartition process on my EU HD2. It didnt make badblocks etc...
Click to expand...
Click to collapse
HOW TO USE:
- Well. You should have "mtty-specific wince drivers" This is hardest stage of this. Please look this thread for it: http://forum.xda-developers.com/showpost.php?p=5456461&postcount=2
- I recommend to use aMagldr 1.13.07 above. Older versions will cause problems. Please look this thread for getting lastest aMagldr: http://androidforum.tytung.com/amagldr-v1-13-07-t183.html
- Run tool and select your Leo model from menu.
- Enter your sizes for each partitions and press Ok button. You can skip partitions with Cancel button.
- After these it will prompt for connecting phone to PC.
- Run aMagldr and select USB Mtty option.
- Connect phone to PC.
- Press Continue button ready and wait. Tool does all things automatically.
- If mtty app stops with error, please try again. It isnt caused by my tool and it wont hurt anything.
Click to expand...
Click to collapse
HOW TO INSTALL ANDROID OR RESTORE BACKUPS
aMagldr's mtty utility hasnt any command to write any type data on nand. So you should use a "SD Recovery" for flashing a nand recovery on nand partition, installing rom and wiping partitions. I recommend to use kokotas extwrp sd version to flash recovery and/or rom and wipe partitions. You can install sd and nand version of this recovery from: http://androidforum.tytung.com/extended-twrp-2-6-0-0-touch-recovery-for-the-hd2-leo-t42.html
-Copy sd recovery's initrd.gz and zimage files to your memory cards root directory.
-Run amagldr and select Boot AD SD option to run recovery
- If it gives "SD kernel open failed" error;
* You should move this 2 files on sdcard/twrp folder (if twrp folder not there, create it manually)
* Run amagldr and select SD directory from Services>Bootsettings>AD SD dir option firstly. (Select twrp from here)
* After that, select Boot AD SD from amagldr's main menu.
Click to expand...
Click to collapse
CHANGELOG:
v1.20
- improved general speed and stability
- added checking phone connection feature
- attempting to fix mtty startup problem
- added use last Partition Table feature
- fixed invalid commands actions
- changed color scheme
- codes cleaned
v1.11
- fixed remained size calculation
- fixed some strings
- fixed userdata flag
v1.10
- added use and dont use last 24mb option
- added changelog menu
- fixed some strings
v1.00
- Initial release
Click to expand...
Click to collapse
SCREENSHOTS:
http://n1311.hizliresim.com/1h/t/uvrl6.png
http://k1311.hizliresim.com/1h/p/urq7u.jpg
http://t1311.hizliresim.com/1h/p/urq87.jpg
Click to expand...
Click to collapse
WHAT WILL BE NEXT VERSIONS?:
Who knows?
Click to expand...
Click to collapse
DOWNLOAD LINK: http://androidforum.tytung.com/amagldr-partiton-wizard-v1-0-t185.html
symbuzzer said:
DOWNLOAD LINK: http://androidforum.tytung.com/amagldr-partiton-wizard-v1-0-t185.html
Click to expand...
Click to collapse
1 st. thanks super work.
2nd thanks
thanks. this is revolution.
thank you very much, super convenient !
Tool updated to v1.10. Changelog and download link on first post.
Tool updated to 1.11. Please look first post for changelog and download links.
Hi symbuzzer,
I just wanted to wake up my good old HD2 with a new ROM. But to install Slimrom I needed a larger Nand Partition. At the moment i have just 120 MB and that is too small.
I tried to use your wizard but I always get a problem with the mtty connection to my PC. The phone seems to freeze and nothing happens. After a while the tool shuts down without doing anything.
Do you have an idea of a solution? I would be very happy to reactivate that good old piece.
Thanks
Frank
frankhell said:
Hi symbuzzer,
I just wanted to wake up my good old HD2 with a new ROM. But to install Slimrom I needed a larger Nand Partition. At the moment i have just 120 MB and that is too small.
I tried to use your wizard but I always get a problem with the mtty connection to my PC. The phone seems to freeze and nothing happens. After a while the tool shuts down without doing anything.
Do you have an idea of a solution? I would be very happy to reactivate that good old piece.
Thanks
Frank
Click to expand...
Click to collapse
Hi, probably you didnt install correctly mtty specific wince drivers. Please look 1st post again for right drivers.
symbuzzer said:
Hi, probably you didnt install correctly mtty specific wince drivers. Please look 1st post again for right drivers.
Click to expand...
Click to collapse
Thanks for your help. I cant get it to work.
I took the good old HD2 Toolkit and it worked fine.
Tool updated to v1.20. Changelog and download link in first post. Probably this is final version.
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
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.
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.