Develop Bugs

Crypted Virtual Container for XPERIA!!!

FreeOTFE is a free, open source, "on-the-fly" transparent disk encryption program for PCs and PDAs
Using this software, you can create one or more "virtual disks" on your PC/PDA. These disks operate exactly like a normal disk, with the exception that anything written to one of them is transparently, and securely, encrypted before being stored on your computer's hard drive.
Features include:
Source code freely available
Easy to use; full wizard included for creating new volume
Both PC and PDA versions are available; data encrypted on your PC can be read/written on your PDA, and vice versa
No need to install it; making it ideal for use on USB memory drives, etc
It's powerful: Supporting numerous hash (including SHA-512, RIPEMD-160, Tiger) and encryption algorithms (including AES, Twofish and Serpent), and provides a greater level of flexibility than a number of other (including commercial!) OTFE system
Encrypted volumes may either be file, partition, or even disk based
Much more!
http://www.freeotfe.org/
WORKS FLAWLESS!!

Big THX for sharing!

Thank you for sharing.

Creating EXT2 Partitions the easy way

This method will work in windows for:
SD Cards in memory card readers/laptops
Phone set in memory card mode
HISTORY
Ok i ran into a wall with this one because of three reasons:
1. Laptops SD reader requires drivers to work, ok in windows useless in linux without the driver, so gpart and hirens boot cd out the window there.
2. My kaiser has a 6.1 rom on it and as far as i can remember it doesnt have a work as a memory stick option that appears on later roms like my touch pro had.
3. the touch pro has a broken digitiser and wont register my finger, so i can get the dam thing into usb memory stick mode.
So skip ahead if you dont want the long story of how i got it to work and made it a little easier for other.
Ok first job created a virtual pc with blank 8gb virtual disk and created the file system 1 x fat32 and 2 x ext2 partitions using hirens bootcd. Next i cloned the disk to a ghost32 compressed image file, as its only the file table and no files its really small (36K). So i rar'ed it up and uploaded so other people can use it as well. (5K)
HOW TO DO IT
Download my blank ghost image from :
Then you need ghost32.exe this can be extracted or ran from hirens bootcd and found as part of a Trialware download at Symantecs site: https://www4.symantec.com/Vrt/offer?a_id=32763 (you will need to create a login to download)
From there just run ghost32.exe and have your sd card ready and connected to the machine, be it in reader or a phone set in memory card mode. Select Disk from Image and select the image file on your hard disk. Then select the SD card and adjust the volume sizes as your require, it will complain about locking the drive and took an age on mine (2 mins), but eventually it was done from there just follow your droid guides for installing.
I know this doesnt help the vast amount of people, but if your stuck like i was and could get access to the card under windows and nothing else it works a treat. If however you can access it under dos etc, you may also want to use this way as its much faster than having to burn an ISO and reboot your entire PC just for partition an SD Card.
Hope this helps someone out.
PASSWORD: Android
http://www.megaupload.com/?d=D64ZX4ZH - 5K

Nice solution, I can see this coming in handy for many who may be in a similar situation.

plazma247 said:
HOW TO DO IT
Download my blank ghost image from :
http://rapidshare.com/files/404732241/Android-SD-Image.rar - 5K
Click to expand...
Click to collapse
Since it's only 5k, do you mind posting it here? The link has reached limit, 10 downloads.

Re-mirrored and added to the main post, lol ur lucky it was deleted from the main machine, tho the laptop still had the ghost image

Nice, but can you make one for 4gb sd card
Thanks.

plazma247 said:
Re-mirrored and added to the main post, lol ur lucky it was deleted from the main machine, tho the laptop still had the ghost image
Click to expand...
Click to collapse
Thank you! I'll try it out ..

Dude it will suit any size memory stick you can adjust the partition sizes as it writes them

plazma247 said:
Dude it will suit any size memory stick you can adjust the partition sizes as it writes them
Click to expand...
Click to collapse
gotcha *thumbs up*

Brilliant solution! One of those "Why did nobody think of this before" things.

[GUIDE]How to run Windows 8 Pro from an External Disk

Guide to run Windows 8 Pro from a External Disk using a VHD (Virtual Hard Disk)​
I created this guide to have the option to install windows 8 pro in an external disk with the purpose to test it without touching my current disk and also to have the hability to boot from it directly when i connect the disk to my notebook, and when it was disconnected still using my notebook as if it were not installed. It is also useful when you haven't space on your disk and you can not replace it
I use a VHD because i think is the best way to test the new windows 8 using all the capacity the your PC, to difference where you are using a Virtual Machine where only use a part of the capacity of your pc.
Anyway exist many way to do this, this is only one that worked for my and i wanted to share with you.
Thing that need before begin:
you need a External Disk at least 40 GB
booteable pendrive with windows 8 Pro or Dvd
you need to create a VHD disk
Remember backup your information, this guide worked for me and others, that's not mean that works for everybody
Step to Make a USB stick​​I used "Windows 7 USB/DVD download tool" from Here, I don't explain this because is easy and only you need to follow the step that the app provide
Step to create a vhd disk​ ​
What is a VHD:
VHD (Virtual Hard Disk) is a file format which represents a virtual hard disk drive (HDD). It may contain what is found on a physical HDD, such as disk partitions and a file system, which in turn can contain files and folders. It is typically used as the hard disk of a virtual machine.
Open Computer Management, select Storage and select Disk Management.
Now you can see all the disk in your Computer.
{
"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"
}
The picture is only a reference, is not shown the real disk
Select the External Disk
In the right side, there is a option that say; "more action", click there and select "create a VHD".
You'll see a screen like this:
Choose where you want save the vhd disk and the name for the vhd disk. (i personally save it in my external disk)
Now you'll see this screen:
Close Computer Management and open it again to Initialize the Virtual Disk.
Right-click and you new unallocated space and select "new simple volume"
The wizard start, click next
Dont modified the size of the disk and next
Assing the letter and next
Format as ntfs and next
Click finish, now you create a vhd disk to install windows 8
Remember what name you used for the vhd disk and where you saved it.
Step to install windows 8 Pro using a VHD disk​
Restart your computer with your new USB key plugged in and startup your BOOT MENU
Select your USB Unit to run Windows 8 Pro Installer.
Start the SETUP process and click in install now
Stop In the screen that show the hard drive and NOT SELECT THE DISK
Instead hit SHIFT-F10 to get to a console. We want to attach our VHD and install to THAT instead.
In the cmd screen type DISKPART, now attached the VHD with these commands:
Code:
DISKPART> select vdisk file=d:\VMs\Win8.vhd
DISKPART> attach vdisk
In my case D but you assign the letter where you have saved the vhd disk.
[B]Tip: Before you enter Diskpart, I recommend "CD x:" to find your actual Storage Device. (X - Multiple possible Drive letters, not the same as when you're in Windows).[/B]
Next, ALT-TAB back over to the list of disks and hit REFRESH, You'll see your VHD show up.
Select it and click on next, Note that installation will warn you that this VHD can't be booted to, go ahead and install to that empty VHD.
Here i let windows install for itself, and that it reboot a couple of time.
Now we come to this screen:
Proceed with installation, personally i used a windows account to get all the functions of windows 8 pro, later you can change to local account.
When you finish you will get into you new Windows 8 Pro booting from your vhd disk
Now when you reboot you will have the new windows 8 bootloader menu:
but here the Problem, remember that i using a external drive, and when i disconnected it windows does not boot anymore or having to do lots of commands to achieve a successful start, forcing you to connect the external disk to boot the computer, to avoid this:
Boot into Windows 7
Run msconfig
In the Boot tab you will see the following:
Code:
windows 8 Default OS
windows 7 Current OS
Select Windows 7 and press make default. Now you get this:
Code:
windows 8
windows 7 Current OS; Default OS
With this simply step we can use the windows 7 bootloader to Dualboot our pc and no longer requires us to have connected external disk when we only use windows 7.
Any questions you want to ask me I'm here to help you as much as I can. I would be appreciated any comment or suggestion about this guide or simply it like you, let me know about it and press the Thanks Button ​

I have some modifications for you...
1.) You do not need a 40GB Hard Drive (not sure why so many tutorials make this claim) as you could make a 5GB VHD and still run Windows 8 but will be limited on data to install/store (which any important data should be saved to SkyDrive (or your Cloud solution) or an external Partition (or use "Local Disk" aka your actual Windows X Edition).
2). Do not use a Dynamic Expanding VHD, always Fixed (just a personal success story for me)
** OPTIONAL: Save the VHD on the Hard Drive you're making the VHD from **
3). I would simply just rename (NO SPACES for 1st TIMERS) the new VHD once initialized as Windows will Format/Do its magic in the Install.
4). Depending on how many "Storage" devices you have will depend on the Drive letter, usually goes from C - I.
Tip: Before you enter Diskpart, I recommend "CD x:" to find your actual Storage Device. (X - Multiple possible Drive letters, not the same as when you're in Windows).
5). During the hard drive select option, you won't get a warning about the hard drive if you follow step #3.
6). No need for MSCONFIG as your new Windows 8 created a new MBR (Master Boot Record) on the actual hard drive, which you should warn people upfront. Therefore even if your other Hard Drive (assuming you're doing external) is disconnected and holds your VHD, since it already detected another Windows OS, it automatically adds it to the Boot Record as the MBR Shows that purdy Windows 8 Startup Drive/OS Selector.
Otherwise, good tutorial . As for the above, that is strictly from my own personal experience as a developer/IT Prof & blah blah, I have done this probably 30 times now just for Windows 8 as we have multiple Tablet/Slates & Laptop + Desktops that needed this done for our Tech Support, Dev's, and our EU/Product Testers.
Should also mention, if you mess up or don't like your new Windows 8? Simply delete the VHD (in other Windows) and go to MSCONFIG and remove the Windows 8 entry from the MBR/Startup.

@lseidman
Thanks for your feedback mate , about it:
for the point 1: i suggest this space because it is the space the microsoft suggest always when install windows and how this guide is for everybody i don´t wanted change it, i know that can be used a lower space.
for the point 4: i forgot to mention it, i have already changed it into the post
for the point 6: i add the part about msconfig and this is my personal experience i don´t know if is good or bad when i leave the windows 8 boot and i disconnected the external disk, the current operating system does not boot (windows 7), i get always a windows error: "windows can not initialize the component winload.exe" and i tried many config when i have installed it but again it is just a way to do it. Anyway mate, i really appreciate your answer :good:

2k of view and no comments , feel free to post
Sent from my GT-I9100 using Tapatalk 2

win 8
can it be installed in simple partition of the external drive not virtual one.
I have two partitions on the external drive can i simply install it one of them.?

addy89 said:
can it be installed in simple partition of the external drive not virtual one.
I have two partitions on the external drive can i simply install it one of them.?
Click to expand...
Click to collapse
Personally i have some trouble when i tried in that way.... You can try but always make backup of your files
Sent from my GT-I9100 using Tapatalk 2

win 8
I have done according to the guide but the problem is it cannot locate boot device(ext hdd).
and another thing i have a hp netbook mini 1001tu.its hard disk crashed.and not getting new spare.
i so i wanted to know that if i create a windows 8 external and put it in use with the mini.so that it can be used.:cyclops:

addy89 said:
I have done according to the guide but the problem is it cannot locate boot device(ext hdd).
and another thing i have a hp netbook mini 1001tu.its hard disk crashed.and not getting new spare.
i so i wanted to know that if i create a windows 8 external and put it in use with the mini.so that it can be used.:cyclops:
Click to expand...
Click to collapse
My question is...does this method erase space from the external HDD permanently? Or once I don't want to boot can I delete the vhd file and get back all the space?

tpma4life said:
My question is...does this method erase space from the external HDD permanently? Or once I don't want to boot can I delete the vhd file and get back all the space?
Click to expand...
Click to collapse
If u deleted the vhd u get the space again, but do it through disk management
Sent from my GT-I9100 using Tapatalk 2

Very nice

Would this allow me to boot into windows 8 pro on a windows 8 rt surface device?

mikexmayhem said:
Would this allow me to boot into windows 8 pro on a windows 8 rt surface device?
Click to expand...
Click to collapse
I dont test it. I only test it in notebook and desktop pc with windows 7.
Sent from my GT-I9100 using Tapatalk 2

mikexmayhem said:
Would this allow me to boot into windows 8 pro on a windows 8 rt surface device?
Click to expand...
Click to collapse
No. RT uses ARM, Pro uses x86.

Too difficult this method... Check my old how-to :highfive:
http://forum.xda-developers.com/showthread.php?t=1597261

PYCON said:
Too difficult this method... Check my old how-to :highfive:
http://forum.xda-developers.com/showthread.php?t=1597261
Click to expand...
Click to collapse
I would not say too difficult, is only other method, to help people

Easy! not diffcult at all
PYCON said:
Too difficult this method... Check my old how-to :highfive:
http://forum.xda-developers.com/showthread.php?t=1597261
Click to expand...
Click to collapse
I just installed Windows 8 on a VHD it was not a difficult procedure and everithing is working fine.
The advantage of this method is that a backup of Windows is very simple now: just drag the .vhd file to another disk
One remark: When my BIOS is setting to startup from USB it will not start the bootloader...
Thanks DeltaSync!

For those who are able to Windows To Go does this. Requires Enterprise though.
http://en.wikipedia.org/wiki/Windows_To_Go

Tréo500 said:
I just installed Windows 8 on a VHD it was not a difficult procedure and everithing is working fine.
The advantage of this method is that a backup of Windows is very simple now: just drag the .vhd file to another disk
One remark: When my BIOS is setting to startup from USB it will not start the bootloader...
Thanks DeltaSync!
Click to expand...
Click to collapse
Thanks for your words mate, glad all working fine for u
Sent from my GT-I9100 using Tapatalk 2

Thanks this is exactly what i'm looking for!
I'll try it soon.

Some New Information Regarding the KIN 2M Filesystem

I have been following the xda-developer website for awhile now, as I have a KIN 2m of my own and I have been interested in finding a way to root or replace the current OS with a new one. Since I haven't seen anymore progress with the phone itself, I decided to do some digging and see what I could do myself (I am a programmer and IT Specialist). What I found might be helpful.
According to other posts, and what is floating around the internet, the KIN 2m flash memory is based on the Samsung MoviNAND 8G architecture. The chip itself is the Samsung MoviNAND KLM8G4DEDD-B101 which supplies 8GB of flash memory to the phone. Since this is also a Flash based NAND memory, I decided to investigate into the actual filesystem (FS) which makes up the chip and which WindowsCE 6.0 is based.
Apparently, this particular NAND memory is based on the YAFFS2 (Yet Another Flash File System rev2.0) which supports both little- and big-endian (32 and 64-bit architecture and some 16-bit systems), respectively. Also, the operating systems that are built on this particular FS are WindowsCE, Android, Linux, pSOS, eCos, and ThreadX.
Going off what I had found, I discovered that with regard to WindowsCE in particular, there are four different parts to the KIN NAND set-up: A Portable YAFFS "Core", a YAFFS Direct Interface, the WindowsCE wrapper, and then of course the WindowsCE OS itself. For WindowsCE, the WindowsCE wrapper accesses the YAFFS Direct Interface, not the core directly. In order to write instructions to the NAND and the "core", a set of instructions in three different types are necessary. These types are a POSIX Application Interface, an RTOS Integration Interface, and finally Flash Configuration and Access Interface. I have attached (and pasted) below a diagram of the above description and I have attached a document which was provided by yaffs.net which also covers some of these details.
View attachment 1461518
The POSIX Application Interface allows execution of application code to access the filesystem. These commands that are executed are typically open, close, read, write, etc. The RTOS Integration Interface consists of functions which allows for YAFFS to access the RTOS system resources. The commands are things like lock, unlock, initialize, get time, set error, etc.. Finally, we have a Flash Configuration and Access Interface which allows YAFFS to access the NAND directly and it executes commands such as initialize, read chunk, erase block, etc.)
So this is what I have discovered so far, and I am currently working on seeing where I go from here. I am currently trying to mount my KIN and browse it as a YAFFS filesystem on my computer, and once I do that, I am thinking that I might be able to execute instructions to access the ROM and NAND chip. On the YAFFS.net website there are a lot of good documents on how this FS works and how commands are executed. I am currently trying to read all I can and see if there is anything I can do.
And the plus side is, after all of this digging and experimenting...my KIN still works!!

very interesting.
wouldn't instructions be executed on the ARM?
http://en.wikipedia.org/wiki/ARM_architecture#Instruction_set
the trick would just be getting something on there and running...
Edits:
actually we may have already found a way to execute. it involves XNA or Silverlight and its on these forums somewhere. now compiling something...
must note that this could probably end very poorly.
so how we write android to NAND?
http://source.android.com/
BOOM
http://infocenter.arm.com/help/topic/com.arm.doc.ddi0290g/DDI0290G_arm1156t2fs_r0p4_trm.pdf
if we can access a console on the actual kin device we can compile code. now, how exactly we could do that is a mystery to me. the kinOS is running on top of windows CE kernel, so there may be one in there...
that console would be "run23"
http://support.microsoft.com/kb/194302
http://developer.download.nvidia.com/tegra/docs/tegra_250_hw_setup.pdf
check out page 12. to put the kin in recovery mode, you hold u+s+b+power.
also relevant
http://forum.xda-developers.com/showthread.php?t=894130&page=2

BOOM
infocenter.arm.com/help/topic/com.arm.doc.ddi0290g/DDI0290G_arm1156t2fs_r0p4_trm.pdf
if we can access a console on the actual kin device we can compile code. now, how exactly we could do that is a mystery to me. the kinOS is running on top of windows CE kernel, so there may be one in there...
that console would be "run23"
support.microsoft.com/kb/194302
Click to expand...
Click to collapse
That is a good thought. However, according to what I have found, there is no reason to go looking for a console on the device itself with which to compile/execute code. What I have found, to date, is that because the device is a YAFFS filesystem, if we have the correct drivers installed on our host machine (which can be gained from the internet), we can mount the device as a drive and using Command Prompt on the host machine we can compile and execute the code from there. We can use the commands NVFlash, mount, write, flash_eraseall, etc.
Sorry if this doesn't seem to make an sense at the moment...I am trying to multitask, and I believe I am failing miserably. I will hopefully have more information later.

IT_Tech said:
we can mount the device as a drive and using Command Prompt on the host machine we can compile and execute the code from there. We can use the commands NVFlash, mount, write, flash_eraseall, etc.
Click to expand...
Click to collapse
ooh, that's a good one. i think JohnKussak was doing something like that using the NVidia tegra toolkit, but he was not able to connect for some reason.
http://forum.xda-developers.com/showthread.php?t=894130&page=2
now, from what i understand of YAFFS (which is admittedly very little) it's just a partition of the memory right? or is the YAFFS system on a completely separate piece of memory?
i was reading about the MPU (memory protection unit) in the ARM manual and it described the layout of memory. basically it supports up to 16 blocks, all with 32 bit addresses (4294967295 bytes = 4gb). since there's 8 gb of storage on the kin, it can probably be assumed that 2 of those blocks are used for storage. another block is probably for RAM (256mb). now, the YAFFS system has to be accessible to the ARM somehow (maybe), so there are several possibilities.
1) the YAFFS file system is on a partition of the 8gb storage space
2) the YAFFS file system is on a partition of the 256mb RAM (pretty sure this isn't the case)
3) the YAFFS file system has its own block of memory
regardless, the MPU can be disabled. when it's disabled, no permissions are checked (ever) and we can read/write anywhere we please, including the YAFFS, wherever it may be. i'm not totally sure this is necessary, but i know we've had problems accessing system folders in the past. i suspect disabling the MPU could fix that, if we could manage.
i also suspect that the YAFFS is accessible when the phone is in recovery mode (u+s+b+power), we just need the correct drivers to flash a Tegra 2600 APX chip. i believe i read on the tegra thread that somebody couldn't find that particular driver. it may need to be written.
edit:
just found this https://developer.nvidia.com/tegra-2-technical-reference-manual
you have to apply for access and it can take up to a month i guess. i'm working on that right now. the main item of interest is "16.0 NAND Flash Controller". i'm gonna try looking in some shady places and see if i can't dig that up...
double edit:
just realized that tegra 2 is different than tegra APX, NVidia does not offer an APX manual anymore, if they ever did.
triple edit:
ooooookay. http://viewsonic-gtablet-for-dummies.webs.com/nvflash.htm
just grabbed source for drivers. unfortunately, NVflash does not run on 64 bit systems, which is causing a bit of problems for me...

slimeq said:
now, from what i understand of YAFFS (which is admittedly very little) it's just a partition of the memory right? or is the YAFFS system on a completely separate piece of memory?
Click to expand...
Click to collapse
From what I understand, YAFFS is a partitioning system. It does not need to be stored as a separate system on a separate piece of memory. However, it does also have the capabilities to be partially RAM based... Which may end up confounding things. If you get a chance, you may have done this already I don't know, but read up on the YAFFS file system on the yaffs.net website--it has a ton of documents on how the system works and the commands it executes, its architecture, etc.
slimeq said:
i was reading about the MPU (memory protection unit) in the ARM manual and it described the layout of memory. basically it supports up to 16 blocks, all with 32 bit addresses (4294967295 bytes = 4gb). since there's 8 gb of storage on the kin, it can probably be assumed that 2 of those blocks are used for storage. another block is probably for RAM (256mb). now, the YAFFS system has to be accessible to the ARM somehow (maybe), so there are several possibilities.
1) the YAFFS file system is on a partition of the 8gb storage space
2) the YAFFS file system is on a partition of the 256mb RAM (pretty sure this isn't the case)
3) the YAFFS file system has its own block of memory
Click to expand...
Click to collapse
Let me begin here and differentiate between YAFFS types...there are two types of YAFFS formatting--YAFFS1 and YAFFS2. The KIN is formatted using YAFFS2 because it has 8g of space. Yaffs2 is different from Yaffs1 in the fact that it allows for memory sizes greater than 4GB because it supports 4KB pages rather than 512byte pages (Yaffs1). I will spare all the details as they are lengthy, but check out:
yaffs.net/documents/how-yaffs-works and yaffs.net/yaffs-original-specification (paying attention to Yaffs2 and how it relates to it foundation off of Yaffs1). Also, since Yaffs only uses a RAM based system for emulation purposes when the kernel is not being run on a true NAND (or NOR) storage, we can eliminate Option 2. Option 3, may be viable, but I am not sure as to how. Option 1 seems to make the most logical sense (pun intended), because of how the YDI (YAFFS Direct Interface) works with the YAFFS kernel and filesystem, as well as the WindowsCE Wrapper, etc.
Now as for the MPU. Yaffs has a built in code to handle MPU and a way to disable it through a console session on a host machine, but I don't remember where I read it, I believe it was on the yaffs.net website in one of the technical documents... I will work to remember where I found it.
I hope we can get some more people on-board helping with this YAFFS thing. If we could, it might make this go a bit faster, and have more heads working on it. Plus they might see something we don't.
P.S: These are the HARDEST captchas I have ever seen in my entire life!

kin
Hopefully you get access to the filesystem with this IT_Tech :fingers-crossed:

Every once in a while, it's fun to revisit Dev on the Kin
I remember going through the Tegra 2500 APX links on the wayback machine:
http://web.archive.org/web/20100813070722/http://www.nvidia.com/object/product_tegra_apx_us.html
If you click the Specifications tab, you can see that the 2600 and 2500 are virtually identical, aside from some video features.
Also, the ZuneHD is the only other product listed as using the 2500 chip. I don't have one, so I wouldn't know for sure, but I wonder if its drivers could be tweaked to allow access to the Kin, in the same way as the Zune. I remember trying to hack into other Windows Mobile drivers (for other WinMo 6.x devices I have) but never getting anything further, even when in other USB modes on the device.

[WORKING] [ROOT] Windows To Go Drive on Sprint Galaxy Nexus

Hi All
After many many issues and tests, I have finally managed to boot a copy of Windows 8 stored on my Galaxy Nexus 32GB which can be loaded up on any machine and used as a WINDOWS TO GO drive. I'm making this thread from this setup and I honestly cannot feel the speed difference.
Method:
1. Procure official Windows 8 DVD and extract install.wim from 'sources' folder
2. Procure Wimlib from http://sourceforge.net/projects/wimlib/
3. Download DriveDroid from Google Play
4. Set up DriveDroid for Standard Android Kernel and create a 10GB image file on the phone. Do not create a partition table for it just yet.
5. Mount the image to a Windows 8 PC.
6. Use diskpart - select the disk, clean, create primary partition, format quick ntfs, set active
7. Use Wimlib to APPLY the image to the Removable Disk Drive that you just made (use the --strict-acls switch)(read the additional documentation)
8. Once the image is applied, use the command "BCDboot X:\Windows /s X: /f ALL" where X is the drive letter of the removable disk you made.
9. All done! Reboot and boot regularly (haven't tried UEFI yet) Will take time to install drivers and screen will be inactive for some time. Let it complete everything and start up.
Attached screenshots.
Note - ImageX and DISM have created problems for me before. Avoid using those.