Originally Posted by Nitro_123
@trevd Do you have anything to say about this ?
I've not got a device in my hands yet to be able to give a proper device focused opinion on this.
but since you ask, I will say It really all depends on the bootloader setup on the device and how accessible that is, it could well be a proprietary Samsung Design in which case I wouldn't want to "mess" with it unless you had a JTag handy for when s**t goes wrong, otherwise you'll be holding a very expensive brick.
Even without bootloader access theoretically you could create a 3rd stage bootloader ( possibly Grub2/uboot ) which sits in place of the kernel in the boot image ( or recovery image ) , this would give the Option to load android or chainload into the windows boot manager, this is how things are done on classic x86.
If you have to go with a 3rd Stage Loader then the first steps is to get your own code running instead of the Standard Kernel Initialization inside an android boot image, There's all sorts of fun to be had after that as basically you'd need to place things in memory where the Kernel or the Boot Manager is expecting to find them amongst many other things.
Standard Windows 7/8 Installations setup a "hidden ( not assigned a drive letter in windows) " 100MB NTFS partition which contains the bootmgr.exe ( TRIVIA : boot manager replaced NT LOADER ( NTLDR ) which was used by Windows XP ). The boot configuration datafile ( BCD ) contains the settings for loading the actual operating system.
I wouldn't be too concerned about the closed source nature of Windows as there's still plenty of folks doing some absolutely bonkers **** with Windows/Windows Booting. Check out http://reboot.pro
if you want to see some of that. My favourite is the 10MB WindowsXP that boots cmd.exe and nothing else LOL WAT!?! . I'm not saying you'll find the answers there but I'd consider it the "state of the art" when booting windows in unusual ways.
Without getting too far ahead, if you did get it booting then it appears the Asus Memo Pad FHD 10 which is a windows 8 device has the same SOC so I would expect there to be driver support already present ( or available ).
Additionally I've not even considered UEFI and how that would affect the whole scenario as I've not delved into the UEFI chaos yet.
Personally I've not used Windows in anger for a couple of years and I've only booted Windows 8 in VM's just to have a look, so my "WindowsFu" is getting a little rusty.
In Summary : Technically Possible ( anything is possible ) - All depends on the bootloader and how much you want it! and to paraphrase @wranglerray
"If it was easy, everyone would be doing it"
Don't forget to click Thanks If this post has helped. It gives me a little warm feeling inside
I WILL NOT RESPOND TO PM'S REQUESTING TECHNICAL SUPPORT
Development Work: Git Hub (https://github.com/trevd)
| Huawei Dongle Support : Archos G9 , Asus Nexus 7
| adb extended version ( adbx ) [Always WIP]
| The No Script, No Cygwin Standalone Boot Image Utility [WIP]
Other Work : Custom framework-res.apk resources.arsc using vendor overlays
| [GUIDE][HACK]Cross Compiling for OSX on Linux with AOSP
A bug report without logs is just trivia!
adb shell dmesg ; adb logcat -b system -b radio -b events -b main