I used the linux Utility "dd" to make a backup from mine. Its a block level image so it will preserve the exact state of the stick including any recovery partitions. I can put some instructions together if you wish. Is your stick running the Intel official image?
Yep, running Intel's patched 8.1 image. Some docs would be helpful (to myself and others I'm sure). Many thanks in advance!
DISCLAIMER: This imaging process is not supported by Intel and is no one way linked to Intel or Microsoft. The method used here has been tested and shown to work. You do this process at your own risk and assume all responsibility for what happens while doing it
I put together this Doc with pretty pictures and what not. Give it a shot or PM me if you have questions so I can update it. If your willing to send me image once you get it would be greatly appreciated (want to get a working factory image on mine fine if you don't want to).
Here is a link to the PDF
Hmm.. Your doc says Ubuntu 10.04, I think you meant 14.04..?
Hmm. You say to use Rufus. Just wanted to let you know earlier today I used dd to write an iso image of 14.04 out to a microSD card (dd if=ubuntu.iso of=/ssdcard bs=1m) from a Mac. It boots just fine. I'm guessing Win32DiskImager would work under Windows, and dd from a linux box.
I'm messing with Rufus right now, but it's damn slow copying the ISO out to another microSD card.
Trying to make the guide easy for everyone to use there are plenty of optimization that could be done. Also I'm assuming people will be using windows. People familiar with Linux will likely find the guide obvious
Just wanted to confirm, writing the iso out to a 2G microSD card with Win32DiskImager results in a bootable card.
Booted my system from microSD, have a 32G jump drive, keyboard and mouse plugged into a USB hub that is in the single USB port on the Stick. Backing up with
dd if=/dev/mmcblk0 bs=1M | gzip -9 > /path/to/usb/win.img.gz
worked for me.
Thanks for the assistance. I really was just unsure what the block device was for the internal flash. I'm a linux guy, not really a windows guy.. :-)
If you wan to use -9 with gzip you will likely get a better space savings by zeroing out the free space on the windows partition first. You can do that by mounting it somewhere and then doing something like "dd if=/dev/zero of=/my/mounted/image/zero.file bs=1M" until you get an out of space error. then simply unmount the windows partition and image as normal. Depending on how many things you have installed / uninstalled / deleted this could be a considerably samller image.
you're saying wipe out the existing installed image, you're then relying on the recovery image for the OS?
1 of 1 people found this helpful
no not at all. this should be completely non destructive
make yourself root first "sudo su -"
will show you all the disks and partitions. Look for disk /dev/mmcblk0 and the for the largest partion on it which will likely be named "Basic data partition". That will be your windows C drive. Mount it using something like:
mkdir -p /mnt/my_c_drive
mount /dev/mmcblk0p<partition number> <--- mine was 4 but i am not using the intel image
with it mounted you may also want to delete hiberfil.sys, pagefile.sys, and swapfile.sys although this might **** off windows at next boot but everything will still be fine. this is completely optional and you dont need to do it.
then do something like:
dd if=/dev/zero of=/mnt/my_c_drive/zero.file bs=1M
this will fill the c drive with one big emtpy file. Once it exits on out of space just delete the file and unmount the drive
rm -f /mnt/my_c_drive/zero.file
then just image as normal. I was able to shrink my image from 9.5gb to 5.1gb
Windows doesn't run off of the C drive?
I don't have my Stick with me for the weekend. I'll have to check the partitions.. I understand what you're saying, I just didn't realize there were separate data and OS partitions.. I didn't think that was the case with mine.
Windows does run on the C drive. you are not erasing anything you are filling all the free space with zeros. There is no seperate data drive you are filling the OS drive
i really shouldn't be on the computer when i'm tired. duh. for some reason i thought of was the partition, i didn't pay attention you were writing to a file. my bad. glad i didn't even attempt this while sleep-typing. yeah. what you said makes sense now. sorry.