Hi All,
I've been wanting to create a Windows To Go Drive on my Android so that I can simply plug in my phone into any PC i want and voila, my own Windows 8.1!
I've only had limited success so far.
What I Used:
Sprint Galaxy Nexus (Rooted, 4.3)
DriveDroid
Sony Vaio Laptop running Windows 8 (Win7 and below dont have latest DISM or Diskpart) (Capable of UEFI booting)
What I Did:
1. Used DriveDroid to create a 10GB image file. It made the file, so i'm guessing that the internal sdcard of the Nexus is not FAT32. No Partition Table and no File System (Yet)
2. Plugged in the phone. Recognized it as a USB Drive.
3. Used Diskpart to clean drive, create primary partition, format as ntfs and set active
4. Extracted install.wim from Windows 8.1 Disc
5. Used DISM to copy image onto Blank USB Drive (Took around 2 hours)
**It's better to use DISM in comparison to ImageX, since ImageX is older and has mixed results
6. Used BCDBoot to copy boot files onto USB Drive
7. Rebooted. UEFI Boot Failed (Didnt even attempt to recognize the drive)
8. Legacy Boot worked! Reached Windows Boot Manager
9. Reaches the Windows 8 Boot Logo and the Spinning Circle
From here though, it just keeps spinning on and on and on.....doesn't stop spinning but doesn't go further than that either.
While it does that, there is
a) No HDD activity
b) No response from Num Lock and Caps Lock key lights
c) No BSOD or response when the phone is unplugged
It's like it doesn't care. Just keeps spinning
Related
Boot UBCD (Ultimate Boot CD) from your Android phone (T-Mobile G1)
Step 1:
Get a microSD or SDHC card that is at least 500Mb and install it in your G1. For newbies: the slot flips open just below the green call button, you’ll have to put the keyboard up to see it.
Step 2:
Get a USB cable and hook your G1 into your computer. Slide the notification pane down and select the item named ‘USB Connected’ then choose ‘Mount’ from the popup options.
Step 3:
Download and install UBCDfix2.exe which I have re-hosted on this blog here. If you don’t trust me, an alternate location is listed on the pendrivelinux.com post. Run the EXE and extract the files to a folder named UBCD on your desktop.
Step 4:
Download the most current UBCD image. Here’s a link. Move it into the root of the UBCD folder you created on your desktop and pout the UBCDfix2 files in.
Step 5:
From the UBCD folder on your desktop, click fixubcd2.bat and follow the onscreen instructions.
DONE! You should now be able to reboot into your thumb drive. Be sure your motherboard both supports booting from a USB device and has the priority for that set above the normal hard drive. On a newer Dell, you can hit F12 to directly choose what to boot off of. Not only can you still save data to your thumbdrive from your G1 like usual, but you can get to all the stuff on your G1 via the UBCD you boot off of too.
Click to expand...
Click to collapse
Now, can you boot Ubuntu from your android device?
skyred said:
Now, can you boot Ubuntu from your android device?
Click to expand...
Click to collapse
Of course, it supports USB mass storage. There is nothing new to see here, really.
Yup. the latest version of Ubuntu even includes a utility to do the dirty work for you. It can install to any USB media.
hi all
i have got the eu pro 2 image files downloaded but i dont klnow how to create a bootable USB stick with these files so i can boot from it on my pro and reinstall from scratch.
Any guides anywhere ???
thanks
paul
Haven't tried it with a recovery image specifically, but I've done this plenty with an install image. There are tools, but I do it semi-manually:
1. Locate suitable flashdrive whose contents you can erase (back them up if needed) and plug it in.
2. Run CMD or Powershell (as Administrator).
3. Run "diskpart" (all commands are given in quotes and should be typed without quotes) and accept the UAC prompt if needed.
4. In diskpart, type "list disk" to see the list of disks, then type "sel dis [#]" (replace [#] with the disk number for the flashdrive).
5. Type "lis par" to see all partitions on the disk (typically only one) then "del par [#]" for each one to delete them.
6. Type "create par primary" to create a new partition spanning the whole flashdrive, then "lis par" to make sure it's selected (star next to it).
7. Type "format quick" to create a file system on the new partition, then "assign" to give it a drive letter.
8. Type "active" to make the new partition the one the OS will attempt to boot from, when booting off that drive.
9. Assuming everything succeeded, you can now exit diskpart ("exit").
10. Either unpack (using a program like 7-Zip) or mount (Win8 can do this automatically, or there's lots of software for older Windows versions) the disk image.
11. Copy the entire contents of the disk image (you can just use Explorer for this part if you mounted it) to the flashdrive.
Congrats, you have a bootable flashdrive containing a Windows installation (or recovery) image.
GoodDayToDie said:
Haven't tried it with a recovery image specifically, but I've done this plenty with an install image. There are tools, but I do it semi-manually:
1. Locate suitable flashdrive whose contents you can erase (back them up if needed) and plug it in.
2. Run CMD or Powershell (as Administrator).
3. Run "diskpart" (all commands are given in quotes and should be typed without quotes) and accept the UAC prompt if needed.
4. In diskpart, type "list disk" to see the list of disks, then type "sel dis [#]" (replace [#] with the disk number for the flashdrive).
5. Type "lis par" to see all partitions on the disk (typically only one) then "del par [#]" for each one to delete them.
6. Type "create par primary" to create a new partition spanning the whole flashdrive, then "lis par" to make sure it's selected (star next to it).
7. Type "format quick" to create a file system on the new partition, then "assign" to give it a drive letter.
8. Type "active" to make the new partition the one the OS will attempt to boot from, when booting off that drive.
9. Assuming everything succeeded, you can now exit diskpart ("exit").
10. Either unpack (using a program like 7-Zip) or mount (Win8 can do this automatically, or there's lots of software for older Windows versions) the disk image.
11. Copy the entire contents of the disk image (you can just use Explorer for this part if you mounted it) to the flashdrive.
Congrats, you have a bootable flashdrive containing a Windows installation (or recovery) image.
Click to expand...
Click to collapse
I've been building windows deployment images for years and I build my boot drives similarly to how you describe. The problem I've had is in getting a uefi bootable drive which I can use to take a drive image before I deploy a new one. In the past I've used tools like Make PE3 to make some useful boot drives but i'm not having nay luck with the newer pe4 or getting an older pe3 image to boot.
Secure boot is off, windows detects the drive and lsit it in the boot menu it just doesn't boot. Any suggestions?
Will_nonya said:
I've been building windows deployment images for years and I build my boot drives similarly to how you describe. The problem I've had is in getting a uefi bootable drive which I can use to take a drive image before I deploy a new one. In the past I've used tools like Make PE3 to make some useful boot drives but i'm not having nay luck with the newer pe4 or getting an older pe3 image to boot.
Secure boot is off, windows detects the drive and lsit it in the boot menu it just doesn't boot. Any suggestions?
Click to expand...
Click to collapse
Try pressing VOL - (I think its -, might be +) as it boots with the flash drive plugged in
lopezk38 said:
Try pressing VOL - (I think its -, might be +) as it boots with the flash drive plugged in
Click to expand...
Click to collapse
Thanks friend but that is not the issue. I can initiate the boot from USB but none of the boot images I've used in the past or that I've create new successfully boot. This problem is limited just to the surface pro.
Hi All,
I've been wanting to create a Windows To Go Drive on my Android so that I can simply plug in my phone into any PC i want and voila, my own Windows 8.1!
I've only had limited success, so I wanted to ask the dev community what could be going wrong.
What I Used:
Sprint Galaxy Nexus (Rooted, 4.3)
DriveDroid
Sony Vaio Laptop running Windows 8 (Win7 and below dont have latest DISM or Diskpart) (Capable of UEFI booting)
What I Did:
1. Used DriveDroid to create a 10GB image file. It made the file, so i'm guessing that the internal sdcard of the Nexus is not FAT32. No Partition Table and no File System (Yet)
2. Plugged in the phone. Recognized it as a USB Drive.
3. Used Diskpart to clean drive, create primary partition, format as ntfs and set active
4. Extracted install.wim from Windows 8.1 Disc
5. Used DISM to copy image onto Blank USB Drive (Took around 2 hours)
**It's better to use DISM in comparison to ImageX, since ImageX is older and has mixed results
6. Used BCDBoot to copy boot files onto USB Drive
7. Rebooted. UEFI Boot Failed (Didnt even attempt to recognize the drive)
8. Legacy Boot WORKED! Reached Windows Boot Manager
From here though, the Boot Manager simply refuses to recognize the existence of a Bootable OS. (Screenshot uploaded) :crying:
I've been using EasyBCD to change the configuration to make it work. No results yet.
I dunno how close I am to making this work - Maybe really close or probably a gazillion miles away. But I've put a lot of thought and effort into this and was really hoping it would work. :laugh:
Any advice as to where i could be going wrong?
Hi all!
I managed to get to make it boot!
It reaches the windows 8 boot logo and the spinning circle just keeps spinning on and on and on.....doesn't stop spinning but doesn't go further than that either.
When it does that, there is
a) No HDD activity
b) No response from Num Lock and Caps Lock key lights
c) No BSOD or response when the phone is unplugged
It's like it doesn't care. Just keeps spinning
Any ideas to what could be wrong The drive is definitely NTFS, with extra space present. I've tried this on multiple PCs
I think I'll try making it again
Regards,
Xyan
Earlier this week, I posted a thread here asking for help with my hybrid android/windows tablet (Neo Shift N81) that wouldn't boot anymore into Windows. Nobody was able to help here and I ended up going back to the store where I got myself a windows recovery USB. After several attempts, it finally loaded the thumb drive. It reinstalled windows, but what the installation ended up doing was reformat the WHOLE disk on my tablet thereby effectively erasing the partition containing android as well. crying: FML)
So now I have the opposite problem. Windows boots and android doesn't. A little bit of googling led me to Android x86, which is able to run on Intel processors like the one on my tablet. I ended up downloading the 4.4 rc5 iso since it said that would compatible with my 32-bit EFI firmware. I created a 7gb partition by shrinking the main windows one and formatted it as ext4. I placed the iso onto a 2GB fat-32 USB using UNetbootin. I was able to boot it by going into the BIOS and force booting it. I tried testing it by running the live option, but it didn't boot although I suspect that may have also been because the thumb drive I used was ancient (from 2008). Then I installed it to the partition I created earlier. I initially tried to select "do not format", but when I got to the GRUB install windows it wouldn't proceed when I selected "yes" (it just started what looks like a command prompt, except no commands were accepted and would just continue creating multiple lines). Reboot and I selected it to format the partition into ext3. This time, it would proceed beyond "yes" and installed normally. Except it still didn't boot into Android. There was no grub menu or anything and the tablet just automatically boots into Windows 10. (I do have secure boot and fast boot disabled in BIOS) When I check the BIOS, it also doesn't have Grub as one of the options.
What I then tried was the instructions at this link where I select "skip" upon the grub install window during android installation. Grub2Win does show up upon the boot options, but even if I try to force boot that option, it doesn't do anything.
So what now? is there another bootloader I could try? Did I even install android correctly or did I select an .iso not compatible with my hardware?? (Prior to android being erased by the windows installation, the android on my tablet was 4.4) The info page mentioned that the "second" is an EFI image, does that mean I should download the .img file? Please help.
I followed instructions mostly from here.
I had made a copy of ISO file of Windows Media file on a USB drive.
In my new MSDOS laptop, I inserted my pen drive and started installing Windows.
After installation black screen appeared and it again asked me to install windows.
I tried to install it again but while choosing the partition it showed me an error:
There was an error installing Windows
I pressed the power button and the laptop switched off.
I turned it on but the same error persisted while installing the Windows.
Somewhere I found the option for System Recovery and clicked on it.
It showed an error something like:
The installation media could not be found in the external disk.
Contact your system administrator for a media file.
Error code:0xc000000f
The error was quite longer than this but the main points were these.
And every time I am turning on my pc I find the above-given error.
I think I had done some mistake choosing the partition while installing the Windows 10 for the first time.
There were two partitions 1 and 2 and an unallocated space for more than 950GB.
I chose the unallocated space.
HP 15-BW096AU 2017 15.6-inch Laptop (A6-7310/4GB/1TB/DOS/Integrated Graphics)
Insert your USB drive again, reboot, choose "Advanced (options)", open a command line, then enter the following commands:
bootrec /fixboot (press Enter)
bootrec /fixmbr (press Enter)
Restart your PC, and try to install Windows again.
EDIT: see here for more info https://neosmart.net/wiki/0xc000000f-error-read-boot-configuration-data/
@moderators: it would be nice to be prompted to identify ourselves BEFORE we start to reply, instead of after, so as not to lose everything we've entered in the reply box...