Database Info

Boot UBCD

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.

installing pro 2 image files from usb

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.

[WIP] Create Windows To Go Drive on Android

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

Grub2win doesn't load when turning on tablet

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.

Android X-86 Guide for multi-boot with Windows 10 (dont do what i did)

So it has been a hectic few days for me as I had alas managed to wipe my system reserved partition thinking that installing android x86 as multi-boot would actually boot windows for me. Wrong!!! My first poor encounter was the fact that when I had installed windows it had created the system reserved partition as ntfs... I had not realized this when attempting to install android x-86 as multi-boot. I will tell you the result, when booting it would appear to go to grub, however instead it just booted the first menu on the list without hesitation and gave no menu at all. To remedy this I had to use the windows 10 usb i had created for my initial install. I am still not sure how i managed to get it to boot the first time I think it may have just been dumb luck. When windows booted up i went to Disk Management (right click the windows menu and select from the drop down) where I then proceeded to delete the system reserved partition and reformat it fat32. At this point I was satisfied that android would point the out the windows boot, boy was I wrong. After installing Android x86 (_64 8.1 r3) I finally achieved the grub menu boot correctly. I also noted that when installing android x86 the only way it gave me option to add windows to grub was if i had installed without formatting first. (this can be done a few ways including just reinstalling much the same way you would dirty flash a rom on a phone) or you could use a tool to format the partition such as gparted or a linux live cd/usb. I suggest ext4. Oh wait my nightmare hadn't finished yet... Android x86 install had no problems at all (select partition to install(ext4)... do not format... install grub... yes to windows... yes read write... and then reboot) on reboot windows was in the grub menu and I selected it... oops there is no operating system!!! Well that is unsettling... ( I managed to get back into windows using the install media) and not so sure how. At this point i notice that my system reserved partition was now sda 3) So my next objective was to create a boot record for windows which could have been done easily from windows had I considered using bcdedit tool for windows. But since i knew that the partition was sda 3 I figured I could just point the grub menu to the correct drive... again wrong (there was still no boot mbr on that partition *sigh) Well I found that when i went into command line from the windows repair tool it would say I do not have permission to fixboot... wow nice job microsoft... after doing a bit more research I learned that the newer builds give this error when attempting to fix boot. I found a video on youtube which helped me alot but took quite a while to download the older working repair tool(installation media) but his video was fairly well put together. link here (https://www.youtube.com/watch?v=lRCyb7FzWFY). I followed his guide and this time with the repair tool that he shared in the description of his video, I was able to perform the fixboot (bootrec /fixboot) however one of his commands required the copying of bcd to the system reserved partition. The copy failed, however at this time running all the other bootrec commands seemed to go fine. So I exited command and went to the automatic startup repair, which to my surprise worked perfectly... (after a whopping 30 some hours of pulling my hair out of my head over this mess) And windows began to boot. At this point I gave my thanks to the poster of the video and shared my experience with his video in the comments below.) Now When windows booted up I downloaded the bcdedit tool. Personally I used the multi boot tool from this site (https://www.boyans.net/dual-boot-repair-windows-10.html) and selected repair mbr and boot record. This fixed my boot issue windows would boot normal at reset. However now my android was gone but thats okay.
At this point I just reinstalled the android x86 again over the same ext4 partition without formatting and added the windows to grub. This was perfect however when selecting windows did not boot. To fix this I had to edit the grub menu.lst and change the drive from hd(0,0) to hd(0,2) to point to the fat32 partition which had been somehow displaced to sda3. In order to do this I ran android in debug... when debug is running just hit enter and it give you a prompt... from prompt type without quotes "cd /mbr/grub" when the next prompt comes up you should be in the grub directory where the menu.lst is. Now type without quotes "vi menu.lst" this will take you into a text editor (note you can also change your monitors and resolution permanently in grub menu this way) using the arrow keys navigate to the line you want to edit, in my case the last entry which was windows entry when you get to where you need to edit hit the "i" key this will allow you to now enter and edit the text. After making changes hit "esc" to save changes type ":w!" then hit enter. To exit type ":q!" this will take you back to prompt. Now reboot your system and finally the results I had originally hoped for a multi-boot system with windows 10 and android. Now if you are attempting to do this and are looking for a guide to install I will make this just a little longer to make sure you dontt make the same mistakes I made.
1a) before you attempt to install a dual boot with grub... make sure your system reserved partition is fat32 if it is not you need to change it to fat32. as grub will not boot on ntfs partitions.
1b)you will need to have a blank partition, if you have spare room on the drive you can shrink your volume and create a new one. There are plenty of tools out there to format ext4 even from windows. Make sure you format it before installing. (if you are lazy like me you can format ext 4 from the installation, but there is a chance that you would need to reinstall again and choose not format to get the windows entry in grub)
1c)once your partitions looks the way you need and you have a working fat32 system reserved partition you are ready to move on. ( If you have to change a ntfs partition to fat32 I highly suggest you dont install anything until you have repaired the boot menu and tested it first to make sure it works)
2)create your install media... I prefer to use rufus as it is quick and easy, and I prefer the official android x86 as the 8.1 r3 is stable and works great, you can use whatever image you want though, lord knows i test newer versions as they come out. when you have rufus and the android x86 iso of your choice load rufus select your usb drive and select the iso with the browse button. then just hit start allow it to format and when it is done you can boot into your usb
3)To boot into your usb you may actually need to edit your bios and enable virtualization and make sure safeboot is not enabled, also you need a uefi system for x64 distros so if you have an older legacy bios you will need the x86 version instead or the system wont boot
4)When you finally get it to boot you will find the menu to use it as a live cd or install, select the install.
5a) You will now be asked where to install to. Pick the ext 4 partition you created for it.
5b) Now it will ask you to format choose do not format (again if you hadn't formatted the partition ext4 you may do it now, but you may have to reinstall and not format the next time to add windows to the grub menu)
6) You will now be asked to install grub answer yes, if you do not answer yes you wont be able to get back into your android partition again until you do.
7) Now it will tell you that it found a windows partition and asks you if you want to add an entry, select yes... if you do not you will have to make your own grub entry to get back into windows later or completely delete grub from the partition later.
8) Finally it will ask you if you want to make the system read write... select yes, if you select no i can not guarantee you will be able to install anything inside of the system.
10) The end... Installation finishes but do not click launch... instead click reboot. The reason for this is that I have noticed if you launch at the end of installation the grub somehow manages to disappear and you end up having to completely start over.
Enjoy your android x86 / windows multi-boot system.

make sure your system reserved partition is fat32
Click to expand...
Click to collapse
There is no system reserved partition on my laptop since I have a UEFI laptop.
Should I proceed ?