How to Make a MULTI-UEFI Bootable USB! (Windows/Easy Method)

Making a bootable USB has never been easier with the amount of software freely available on the Internet. My favorite happens to be Rufus, but there are many to choose from. And while there are several multi-boot USB programs for MBR, or single-boot GPT USB programs, making a multi-boot GPT USB in Windows is somewhat unheard of. I want to share with you how to make a multi-boot GPT USB easily in Windows.

How To Use YUMI UEFI

BIOS vs. UEFI

In the past there was only BIOS, but in recent times UEFI and EFI have become the new standard for motherboards to use. The main reason for this is that BIOS has space constraints that UEFI improves upon. Much like many protocols, BIOS was made and meant for a certain era, while UEFI attempts to modernize and supplant BIOS.

The simplest way to think of UEFI is like a better BIOS.

Multi-UEFI (GPT) Bootable USB

I want to start off stating that Linux and Unix users have had the capability to use a multi-UEFI bootable USB's for quite some time, albeit through a CLI (Command Line Interface). But Windows users have really not had the ability to do this--until now...

Why is a multi-UEFI bootable USB a good thing? Because you may have several rescue CD's or Windows/Linux Live CD's that you want on one USB as opposed to several. For example, if you were IT for a company that fixed systems, it would be a big hassle to use several USB's, and even worse if none were labeled!

Is It Necessary To Use UEFI?

I would argue that currently it is unnecessary. I have never come across a motherboard for either a desktop or laptop that primarily used UEFI (or EFI), but did not have a "legacy" mode that would allow for a BIOS-compatibility mode.

In essence, this is a switch to change between BIOS or UEFI.

That being said, it should be noted that it is likely that this will not always be the case. It may take a long period, but I doubt that this legacy mode will always be around. And, for the sake of simplicity, it is much nicer to be able to just plug in a USB and not fiddle around with UEFI settings beforehand to get a USB to be recognized.

While having to switch a couple of settings does not sound like a chore, it certainly can be. Last week I had to do a lot of testing in legacy mode; so I had to go into the UEFI, switch to legacy mode, test a USB, go back into the UEFI, switch back to UEFI mode, then restart to get back to Windows. It was not fun.

Introducing YUMI

Some of you may already know of YUMI, it is most commonly known as a multi-boot USB for BIOS (MBR) systems. It is simple to use, portable, and has an intuitive interface.

What most people may not know is that YUMI now offers a UEFI beta version of their program. This only works with 64-bit systems, so be aware that any 32-bit system will not be able to utilize this version of YUMI. (A 32-bit version is being worked on). You must also disable Secure Boot if it is enabled in your UEFI.

There are a few (known) restricted rescue CD's and Live CD's that will not work with YUMI UEFI, which is not something the YUMI creators can fix.* That is because these CD's were not made to work with UEFI, so support for this CD's would have to come from the CD creators.

And while there is a list in YUMI of CD's that can be used, CD's that are not on the list are not guaranteed to work or not work. You will have to try such CD's to find out if they can boot and work properly.

*In this list, CD's that cannot work in UEFI will have a note next to the name stating "BIOS ONLY".

How To Use YUMI UEFI

Using YUMI UEFI is very simple, but I will outline the steps for those who would rather get a sense of what to do first:

Go to the YUMI homepage.

Scroll down to "Beta Download -> UEFI YUMI - Windows".

Download YUMI UEFI by clicking on the "UEFI YUMI - Windows" text only.

Double-click the "UEFI-YUMI-BETA-0.0.0.#.exe".

Press "I agree".

Click the dropdown arrow under "Step 1".

Select the USB flash drive you have inserted.*

Click the dropdown arrow under "Step 2". This will show you a menu of every known rescue and Live CD that YUMI supports.

If you do not have one already, download a rescue or Live CD you wish to use.

Click the dropdown arrow under "Step 2" again.

Select the rescue or Live CD you have ready. If your rescue or Live CD is not in the supported list, you can either choose a supported rescue or Live CD that from the list that may be similar so you can move onto "Step 3".

Press "Browse" under "Show All ISOs?". Check off "Show All ISOs?" if your rescue or Live CD is unsupported, or if you have changed the original name.

Browse for your ISO and double-click it.

Check off "Format #: Drive (Erase Content?)".

Click "Create".

YUMI will not show a progress bar, and when full, it will display a "Finished" button. Click "Finished".

*Note I: If you do not have a USB flash drive inserted, do so now, or check off "Show All Drives?", then select any drive. But be careful, you do not want to accidentally format your OS drive.

Note II: An external USB HDD/SSD (and in fact an installed HDD/SSD) can also be used to create a Multi-UEFI bootable device. To find these options, check off "Show All Drives?" in YUMI.

To test your multi-UEFI bootable USB, first ensure that Secure Boot is disabled in your UEFI. Reboot your computer and click the F# key to get to your Boot Priority screen (or go into your UEFI and either rearrange for USB devices to be found first, or select the USB to boot from it). If the multi-UEFI USB is working, the Boot Priority screen will just show a USB, instead of a designated name that you might find using a BIOS.

Recommendations?

While in theory this should work with any USB and USB port, I would recommend using a USB 2.0 flash drive, however, a USB 3.0 flash drive may work fine. But even moreso, be sure to test on a USB 2.0 port, if possible.

The reason I mention this is because I have found USB 3.0 ports to be finicky at times, especially during POST. I did not have this problem with my multi-UEFI bootable USB, but I tested with a USB 2.0 flash drive in a USB 2.0 port...

Too Simple?

No, it really is that simple. There are a few useful rescue CD's that cannot be booted from UEFI, but the majority you may know of are all available for UEFI.

For someone like me who may need to diagnose or repair a UEFI system every-so-often, a multi-UEFI is worth its weight in gold! And I know that more than a few people have been waiting for an easy method to make a multi-UEFI from Windows.

How to Install Android 5.1.1 (Lollipop) on Nexus 7 (2012) without OTA or ADB Sideload + Root & Recovery! (UPDATE!)

UPDATE: Lollipop 5.1.1 has been rolled out to the Nexus 7 (2012) WiFi tablet. Google's page provides very little help in updating the tablet, and while there are a few articles that explain it better, it is still a hassle. The method described here is still the easiest and safest method to install the update...

I love the Nexus 7 (2012) tablet. Not because it's the best, or because it has features others don't. Simply because it has so much support, even from Google! There are so many good tricks for it such as gaining the ability to do Miracast, or enabling 3G data (on the WiFi version). The "trick" I'll be doing today is how to easily upgrade to Lollipop. Just remember, there are always some risk involved in these techniques, however they are minimal, and if you do everything correctly you should be fine.

Android 5.1 (Lollipop), Root & Recovery

DISCLAIMER:  This is for the Nexus 7 (2012) WiFi tablet. If you decide to try this with the mobile data (or the WiFi) version, you assume all responsibility.

OTA & ADB Sideload
When I first found out that the Nexus 7 had received Lollipop, I was pretty excited. I was already on KitKat, and wasn't sure that an official Lollipop build would even come anytime soon given its age (among other factors). I immediately looked up some articles to find an easy way to get Lollipop onto my Nexus 7. Many of the articles - which are usually just copies of each other - were stating two methods: OTA (Over The Air update) and ADB (Android Debugging) Sideload.

I had already rooted and was on a custom ROM, so OTA was out of the question unless I went back to a stock factory image and updated. The second method seemed a bit less time-consuming, but I was wrong. After downloading the files necessary and getting to my recovery's ADB option, the ADB interface would not start through my recovery. Just my luck.

I then figured out an even simpler method that should work for anyone, rooted or not...

Nexus Root Toolkit
The first thing you will need to do is download the Nexus Root Toolkit. It is a fabulous toolkit that works for all Nexus devices. It is fairly intuitive, if you are already familiar with the workings of rooting and ROMs.

1. Download the newest file here.
2. Install the program and allow it to check for updates.
3. A message about choosing your Nexus device and ROM will come up. Choose "Nexus 7 (WiFi Tablet)".
4. Click "Apply".
5. It will then pop up with the main menu.

Google & ADB Drivers
The first thing you need to do in preparation for the below method, is to ensure that your computer can see your Nexus 7 when connected by USB. If you do not see it in Computer (My Computer), then either the drivers you have aren't working correctly, or you don't have them.

To install the Google drivers:

1. Open Nexus Root Toolkit.
2. Select the "Full Driver Installation Guide - Automatic + Manual".
3. Click tab "Step 3".
4. Push the "Google Drivers" button.
5. Install the "Google Drivers" by clicking "Next" in the window that appears, and confirming any other prompts.

You should now be able to see the Nexus 7 from Computer as a viable device with storage.

If you already have ADB drivers installed, and cannot get ADB to recognize (authorize) the device, ensure that you have enabled USB debugging in "Developer Options" in the "Settings" menu. If not:

1. Click on the Settings app.
2. Select "About tablet".
3. Click on "Build number" area 7 times (it will count it down for you).
4. Go back into the "Settings" menu.
5. Select "Developer options".
6. Check off "USB debugging".

Note: If you already have "Developer options" as a selection, you do not need to perform steps 2-4.

If you still cannot get ADB to recognize your device, or you checked off "Always allow from this computer" on the RSA fingerprint prompt every time you plug in your Nexus 7 to your computer (as this caused a lot of issues with my LG G2), or if you have never done anything with ADB before, follow these steps:

1. Download the ADB Driver Installer.
2. Install the ADB Driver Installer.
3. Once completed, a window should pop up showing your device. If there is an issue with it for ADB, it will show a red stop sign-like image.
4. Click "Install" to give a successful green.

Note: If nothing shows up in ADB Driver Installer, or it is already green, then there are likely other issues going on (i.e. driver conflicts, faulty cable, etc.).

OEM Lock
If you are already rooted and/or using a custom ROM, you can skip down to obtaining Lollipop. Otherwise, we need to unlock the bootloader. You may also want to backup all your data first as this procedure will wipe all data:

1. Open Nexus Root Toolkit.
2. Click on the "Unlock" button.
3. Follow and confirm any prompts.

Your phone will likely turn off and boot back up a couple times during this procedure. It should be completely automated, so you should not have to do anything but wait.

Android 5.1 (Lollipop) Factory Image
While there is already a ROM with the ability to keep your current root and recovery, it is not the official stock factory image. The OTA method is by far the easiest of the three to do, but it can be very time consuming, especially if you haven't been upgrading. The ADB sideload method should be the fastest, but if you are not experienced with it (or able to use it like in my case), then you might want something that is more automated. This method will use the official Google factory image to install Lollipop.

If you haven't already, download the Nexus Root Toolkit and install it or you will not be able to perform the following:

1. Connect the Nexus 7 via USB to your computer.
2. Click "OK" when you see the RSA fingerprint on your tablet.
3. Open Nexus Root Toolkit.
4. Click on the "Flash Stock + Unroot".
5. Click "OK".
6. Select "NAKASI-GROUPER: Android 5.1.1 - Build: LMY47V".
7. Select " Automatically download + extract the factory image above for me." This is under "Choice". If it cannot, choose to download manually and it will provide a link to download from. A message to browse for the image will already have popped up. Browse for the downloaded image and select it. Then click "OK" to proceed. The image should then merge into the Nexus Root Toolkit.
8. Click "OK". The Lollipop factory image will then download. Once done, Nexus Root Toolkit will check for ADB status...
9. If successful, the Nexus Root Toolkit may also try to download TWRP recovery. If it is not, you will go through the same additional steps above required if you cannot download it automatically.
10. The Nexus 7 should then turn off and go into bootloader as it tries to flash the rooted boot image. It will boot up again, but leave it alone. The tablet will turn off again and go into bootloader as it tries to flash the root kernel. Once done, it should temporarily boot into TWRP recovery.
11. Finally, it should reboot into Lollipop. It may seem like it is stuck in a bootloop, but give it 5-15 minutes to load and it should finish.

Note: I already had the newest TWRP recovery image integrated with Nexus Root Toolkit, so I did not get a prompt to download it (step 9) during this process.

Root & Recovery
If you want your Nexus 7 rooted with recovery follow these steps. You can also just have it rooted if you don't want recovery. And if you just want to make a full backup (Nandroid) without recovery, you can actually perform a temp recovery:

1. Connect the Nexus 7 via USB to your computer.
2. Click "OK" when you see the RSA fingerprint on your tablet.
3. Open Nexus Root Toolkit.
4. Click on the "Launch" button.
5. Select the "Boot (Temporary)" radio button under "Boot/Flash Image".
6. Click on the "Recovery" button.
7. Select "TWRP". This should start an automatic download. If it does not work, it may give a link to download it. If it just wants you to browse to a folder that has it (as I already had it before trying this), you can download the newest, official, working version of it from here.
8. The tablet should then reboot into TWRP where you can make a backup or whatnot.

Note: If you already have the TWRP recovery image for step 7, then you can select "Manual" and browse for it instead.

If you want to root and add a recovery (or just root) follow these steps:

1. If you do not already have the free BusyBox and SuperUser apps downloaded, you can save a little time by downloading them now. (You cannot use them until you are rooted).
2. Connect the Nexus 7 via USB to your computer.
3. Click "OK" when you see the RSA fingerprint on your tablet.
4. Open Nexus Root Toolkit.
5. Check off "Custom Recovery" under "Root" if you want to add root and recovery.
6. Click the "Root" button.
7. Click "OK".
8. The Nexus Root Toolkit will then check for the root boot image. If not present, it will try to automatically download it. If it cannot, choose to download manually and it will provide a link to download from. A message to browse for the boot image will already have popped up. Browse for the downloaded root boot image and select it. Then click "OK" to proceed. The root boot image will merge into Nexus Root Toolkit.
9. The root kernel will now try to download. If it cannot, you will go through the same additional steps above required if you cannot download it automatically.
10. The Nexus Root Toolkit may also try to download TWRP recovery, and will also require the additional steps for the root boot image if it is unsuccessful.
11. The Nexus 7 should then turn off and go into bootloader as it tries to flash the rooted boot image. It will boot up again, but leave it alone. The tablet will turn off again and go into bootloader as it tries to flash the root kernel. The turn off and boot off process will likely happen once more to place TWRP recovery permanently. Once done, it should temporarily boot into TWRP recovery.
12. When you are back in Lollipop, Nexus Root Toolkit should tell you to get the SuperUser and BusyBox apps.
13. Open the SuperUser app.
14. Go to "Settings".
15. Check off "Enable Superuser".
16. Ensure to select "[Prompt]" or "[Grant]" under "Default access". "[Grant]" just skips asking you for superuser permissions when accessing an app.
17. Open the BusyBox app. If you selected "[Prompt]" in SuperUser, you will get a prompt to give superuser permissions to BusyBox.
18. It should give you some message about buying it, close it.
19. Click "Install".
20. Less than a minute later you should get a successful message.

Note: I had the tablet hang while trying to flash the root kernel during step 9. If it takes more than 5 minutes at this stage, then the procedure is stuck. To fix this, I rebooted the tablet then restarted the process, which then succeeded.

Obviously, the steps for the TWRP recovery won't be applicable to those who only chose to root the tablet. And you can delete the image files you downloaded once they have been integrated with Nexus Root Toolkit. To be safe, I would wait until the entire process is done.

Steps for Images Unsuccessfully Downloading
Reading those additional steps should be unnecessary as everything is meant to be automated. But for some reason my downloads would finish almost instantaneously [it should take some time] and then have a hash mismatch.

I partially blame my computer for this as it always has this problem with Nexus Root Toolkit for anything, including updating itself! Thankfully, it did download the factory Lollipop image without an issue.

Have Fun Nexus 7 (2012) Users!
I hope this helps anyone who find themselves in the same situation I was in. While there are a lot of steps, none are difficult to accomplish. So enjoy Lollipop, root status, and a custom recovery (if you went through everything like I did). I know I am!

USB Flash Drive Getting Sluggish? Here's a Quick Method to Speed it Up (Torrent Fix)

I have a plethora of USB flash drives at my disposable. I have three Toshiba's that include one 16GB and two 32GB versions. I then have two generic USB flash drives, one is 64GB and the other is 128GB. They all serve various purposes and I usually only have one that is "resting". Until recently, I never really saw an unbearable lag on any of these USB flash drives. And when I did, only one thing actually fixed it...

Speed (Performance) Trick

A Download Story
As I have written before, I find it good practice to actually use a USB flash drive as the location for all my downloads. They are inexpensive to replace, and will help deter against running down your hard drive or SSD.

To give a better perspective of how tough I can be on these USB flash drives, I could be running anywhere between 1-5 downloads from a download manager, while using a torrent client from 1-10 different torrents, and still using my browser to download files like a PDF, ZIP, or EXE.

As such, I started with one of my 32GB USB flash drives. It did well and I cannot recall ever watching it show lag more than a few seconds (when applicable). I soon realized that I would often run out of room, and instead of just slowing down my download agenda, I decided to upgrade to a 64GB USB flash drive. After rearranging all the locations for my browsers and download manager to point to the 64GB, I started up my downloading frenzies again. It too did a phenomenal job and I saw no real performance hit compared to the 32GB. The thing was that I yet again noticed my storage space was insufficient for my needs.

So, I decided to try a 128GB USB flash drive. I purchased a generic one for about $10 that included shipping from China. I should mention that the 32GB was a brand name USB flash drive (Toshiba) purchased for around $30-$40 when it was brand new a few years ago. The 64GB USB flash drive was also a generic brand, very likely Chinese considering where I got it from, and was bought for less than $20.

128GB Too Much?
Before I designated the 128GB as my main drive for downloads, I tested it out to make sure it worked. It seemed to, so I made the necessary arrangements and began my downloading.

At first, everything was fine. I wasn't downloading nearly as much as normal, but downloads were completing in good time with little to no lag. I started off with one torrent at a time, which seemingly did well. However, when I started adding multiple torrents (e.g. two or three), I started to notice how sluggish the 128GB would get...

It was so bad that downloads on my download manager would complete and then take anywhere between 15-45 minutes to actually finish. My torrent client would suddenly freeze for similar amounts of time. And when I would try to transfer files off of the drive, it could take up to 30 minutes. Sometimes all three of these things would be occurring increasing the already lengthy times to double those amounts!

I had even used the Task Manager to end the torrent client process on numerous occasions, and while it would be speedy on startup, it would soon revert back to a sluggish state. After reformatting the 128GB USB flash drive a few times, it would always start the same, speedy. But it would always end up the same with lag coming back into play.

The Speed (Performance) Trick
Then I recalled a trick that I had seen while looking up some other information. If you are using a lot of generic USB flash drives, or have a lot of the same name brand drives, you will either want to take them all out save the one in question, or already know the generic name given to that USB drive, in preparation of this method:

1. Open up "My Computer".
2. Right-click on the USB flash drive (any drive will actually do).
3. Click "Properties".
4. Click the "Hardware" tab.
5. Choose the generic name of the USB flash drive.
6. Click on "Properties".
7. Click the "Policies" tab.
8. Click the "Better performance" radio button. (If this is already selected, you are out of luck.)
9. Click "OK".
10. Click "OK".

Note: Changing to "Better performance" only has one downside. It will force you to eject the USB flash drive every time you want to remove it (something you should be doing regardless). If you don't, you could compromise data integrity and cause a loss of data.

This technique should work on Windows XP, Vista, 7, 8/8.1, and 10; and can be done from the Device Manager if preferred. It is not a speed increase in the normal sense, but if your USB flash drive is sluggish, it will help speed it back up to what it should already be able to do.

This technique does not require or perform a format to your USB flash drive, so your data should remain intact. However, as a safety precaution, you may want to copy all the data on the USB flash drive to another safe location.

Test Results
I immediately noticed a difference in the lag, as it had dwindled itself to that of the 32GB or 64GB USB flash drives (if not a tad better). To test this I started two downloads with my download manager and one torrent with my respective client.

When the first download from the manager completed, it took very little time to finish and transfer it. Transferring took a minimal amount of time despite being a large file and using the move command (which I've noticed takes more time than copying). The second download from the manager then completed, which took a bit more time to actually finish. To transfer I decided to use the copy command, which still took more time than the first, but it was on par with the 32GB or 64GB.

Throughout this time the torrent never hung once, which indicated to me that this trick was indeed working, and could also be accounted for the lag on the second download (given the increase in speed the torrent client got after each download completed).

The torrent never stopped. Not even while opening another torrent. I did notice that trying to download initial torrent files (to start a torrent), and magnetic links clicked while waiting for the initial torrent files to download, did take an abnormal amount of time. Possibly about as much as when it was sluggish. Regardless, the torrent chugged along only freezing when I had clicked a good amount of magnetic links that were failing to open quickly. Eventually, the magnet links worked.

At one point the torrent froze completely, likely due to me trying to add another additional torrent while I had other magnet links popping up. This shouldn't have been a problem for a "normal" USB flash drive, but given this 128GB's history, it certainly could be a remaining issue.

I started the torrent client again, which did take some time before it was functioning properly. By this time I had two torrents running, one nearly finished, another one just starting. The first finished and started flushing to disk. I had to go before it would be transferable, and the second finished before I got back, so I can't say if it took an extremely long time before I could actually do anything with the files.

To retest the torrents and see them through, I started up a single download with my download manager, and three torrents with my client. When the download from the manager completed, it did end up freezing the torrent client as it finished. But once it finished, the torrents started back up. I used the move command to transfer the file and I would say it wasn't as fast as the first download with the manager, but quicker than the second.

Note: It seemed to put a little less stress (and lag) on the USB flash drive to already have its folder opened before moving or copying anything from it.

The first of the three torrents to complete was about half the size of the very first torrent I had downloaded. It took about 4 minutes to flush to disk. I at first had an issue with trying to move another file I had downloaded with the manager while waiting. I had to restart Windows Explorer. After doing so, and when I could get back to the directory of my torrents, I used the copy command which was by far the fastest transfer yet. I then redid my transfer (with the copy command) of the file that had caused Windows Explorer to crash. It too was extremely quick.

At this time, I had closed my torrent client as I needed the extra bandwidth for something else. I came back and restarted the client. Another torrent file completed soon after, that was about 3/4 of a gigabyte. About 2 minutes later it was fully flushed to disk. I made the mistake of opening another folder with the torrent client (which took another two minutes). I then copied the file over, which took another minute or two to start, but the actual copying took a few seconds. The second download finished in about 2-3 minutes. I used my pre-opened folder of the USB flash drive and copied the download. It took around a minute or so to finish transferring.

One additional note, while the last two torrents were finishing the third had stopped downloading from lack of seeders. This may have helped somewhat in moving things along. 

The Lesson Here
While this simple method can help a sluggish USB flash drive, it should be noted that my problem seemed to really stem from torrents. I open several initial torrent files and magnet links in an attempt to add more trackers. Sometimes this is beneficial for torrents with few seeds or peers. Other times it is not. While this helps perpetuate the lag I experienced, the torrent and client itself were still the main culprits.

That being said, whether using the method or not, I still noticed quite a lag to navigate or perform actions on items in my USB flash drive while using the torrent client.

Moreorless, don't use torrents. If you do, try to keep to a maximum of 2 for best results. Three is when things start adding lag for me. And try to download via magnetic links. If you must use initial torrent files, download and open them one at a time and be patient.

Everything Comes to an End
So, there you have it. A way to speed up your USB flash drive. Some people may try it and notice no difference, but they should really perform tests on it first to see if there was truly a significant difference. Others may be using torrent clients and realize that this is a method to aid them in their downloading endeavors.

Part of my thoughts as to why this happened is because it is a larger USB flash drive making it more susceptible to slower write speeds (as evident with SSD's, which are essentially what USB flash drives are). But this could happen to USB flash drives of any size, and performing the above steps should help.

If you feel jilted, then I apologize. There is only one real technique I know of to get USB flash drives to increase their read/write speeds. Come back to my blog later to find out...