diff --git a/Bliss OS/installation-guide/index.html b/Bliss OS/installation-guide/index.html
index 46e601e..29d0259 100644
--- a/Bliss OS/installation-guide/index.html
+++ b/Bliss OS/installation-guide/index.html
@@ -237,6 +237,30 @@
           
           
 
+
+  <li class="md-nav__item">
+    <a href="../installation-guide-misc/" title="Installation Guide (Misc)" class="md-nav__link">
+      Installation Guide (Misc)
+    </a>
+  </li>
+
+        
+          
+          
+          
+
+
+  <li class="md-nav__item">
+    <a href="../installation-guide-surface-devices/" title="Installation Guide (Surface devices)" class="md-nav__link">
+      Installation Guide (Surface devices)
+    </a>
+  </li>
+
+        
+          
+          
+          
+
   
 
 
@@ -280,6 +304,13 @@
 </li>
       
         <li class="md-nav__item">
+  <a href="#windows-installation-method" class="md-nav__link">
+    Windows installation method
+  </a>
+  
+</li>
+      
+        <li class="md-nav__item">
   <a href="#bootable-installation-method-mbruefiesp-3264-bit" class="md-nav__link">
     Bootable installation method - MBR/UEFI/ESP (32/64-bit)
   </a>
@@ -341,182 +372,6 @@
 </li>
       
         <li class="md-nav__item">
-  <a href="#windows-based-installer-uefiesp-64-bit" class="md-nav__link">
-    Windows-based installer - UEFI/ESP (64-bit)
-  </a>
-  
-    <nav class="md-nav">
-      <ul class="md-nav__list">
-        
-          <li class="md-nav__item">
-  <a href="#part-1-using-the-installer" class="md-nav__link">
-    Part 1 - Using the Installer
-  </a>
-  
-</li>
-        
-          <li class="md-nav__item">
-  <a href="#part-2-switching-the-uefiefi-boot-entry" class="md-nav__link">
-    Part 2 - Switching the UEFI/EFI boot entry
-  </a>
-  
-</li>
-        
-      </ul>
-    </nav>
-  
-</li>
-      
-        <li class="md-nav__item">
-  <a href="#use-syslinux-efi-to-run-bliss-os-7x10x11x" class="md-nav__link">
-    Use syslinux EFI to run Bliss OS 7.x/10.x/11.x
-  </a>
-  
-    <nav class="md-nav">
-      <ul class="md-nav__list">
-        
-          <li class="md-nav__item">
-  <a href="#part-1-grab-the-required-tools" class="md-nav__link">
-    Part 1 - Grab the required tools
-  </a>
-  
-</li>
-        
-          <li class="md-nav__item">
-  <a href="#part-2-get-bliss-os" class="md-nav__link">
-    Part 2 - Get Bliss OS
-  </a>
-  
-</li>
-        
-          <li class="md-nav__item">
-  <a href="#part-3-get-the-syslinux-efi-bootstrap" class="md-nav__link">
-    Part 3 - Get the syslinux EFI bootstrap
-  </a>
-  
-</li>
-        
-          <li class="md-nav__item">
-  <a href="#part-4-version-specific" class="md-nav__link">
-    Part 4 - Version specific
-  </a>
-  
-    <nav class="md-nav">
-      <ul class="md-nav__list">
-        
-          <li class="md-nav__item">
-  <a href="#if-you-are-using-bliss-7x" class="md-nav__link">
-    If you are using Bliss 7.x
-  </a>
-  
-</li>
-        
-      </ul>
-    </nav>
-  
-</li>
-        
-          <li class="md-nav__item">
-  <a href="#if-you-are-using-bliss-10x" class="md-nav__link">
-    If you are using Bliss 10.x
-  </a>
-  
-</li>
-        
-          <li class="md-nav__item">
-  <a href="#part-5-creating-the-data-image" class="md-nav__link">
-    Part 5 - Creating the data image
-  </a>
-  
-</li>
-        
-      </ul>
-    </nav>
-  
-</li>
-      
-        <li class="md-nav__item">
-  <a href="#custom-install-bliss-os-8x10x11x-uefiesp-64-bit" class="md-nav__link">
-    Custom Install - Bliss OS 8.x/10.x/11.x UEFI/ESP (64-bit)
-  </a>
-  
-    <nav class="md-nav">
-      <ul class="md-nav__list">
-        
-          <li class="md-nav__item">
-  <a href="#part-1-mounting-your-uefiesp-partition" class="md-nav__link">
-    Part 1 - Mounting Your UEFI/ESP Partition
-  </a>
-  
-    <nav class="md-nav">
-      <ul class="md-nav__list">
-        
-          <li class="md-nav__item">
-  <a href="#cmd-is-not-showing-up-what-should-i-do" class="md-nav__link">
-    cmd is not showing up, what should I do?
-  </a>
-  
-</li>
-        
-      </ul>
-    </nav>
-  
-</li>
-        
-          <li class="md-nav__item">
-  <a href="#part-1-alternate-esp-setup" class="md-nav__link">
-    Part 1 (alternate) - ESP setup
-  </a>
-  
-</li>
-        
-          <li class="md-nav__item">
-  <a href="#part-1-alternate-killing-the-explorerexe" class="md-nav__link">
-    Part 1 (alternate) - Killing the explorer.exe
-  </a>
-  
-</li>
-        
-      </ul>
-    </nav>
-  
-</li>
-      
-        <li class="md-nav__item">
-  <a href="#part-2-uefi-installation" class="md-nav__link">
-    Part 2 - UEFI installation
-  </a>
-  
-    <nav class="md-nav">
-      <ul class="md-nav__list">
-        
-          <li class="md-nav__item">
-  <a href="#part-4-the-manual-blissification-of-your-pc" class="md-nav__link">
-    Part 4 - The Manual Blissification of Your PC
-  </a>
-  
-</li>
-        
-      </ul>
-    </nav>
-  
-</li>
-      
-        <li class="md-nav__item">
-  <a href="#install-bliss-os-on-a-vm-virtualbox" class="md-nav__link">
-    Install Bliss OS on a VM (virtualbox)
-  </a>
-  
-</li>
-      
-        <li class="md-nav__item">
-  <a href="#specific-surface-model-instructions" class="md-nav__link">
-    Specific Surface model instructions
-  </a>
-  
-</li>
-      
-        <li class="md-nav__item">
   <a href="#conclusion" class="md-nav__link">
     Conclusion
   </a>
@@ -754,6 +609,13 @@
 </li>
       
         <li class="md-nav__item">
+  <a href="#windows-installation-method" class="md-nav__link">
+    Windows installation method
+  </a>
+  
+</li>
+      
+        <li class="md-nav__item">
   <a href="#bootable-installation-method-mbruefiesp-3264-bit" class="md-nav__link">
     Bootable installation method - MBR/UEFI/ESP (32/64-bit)
   </a>
@@ -815,182 +677,6 @@
 </li>
       
         <li class="md-nav__item">
-  <a href="#windows-based-installer-uefiesp-64-bit" class="md-nav__link">
-    Windows-based installer - UEFI/ESP (64-bit)
-  </a>
-  
-    <nav class="md-nav">
-      <ul class="md-nav__list">
-        
-          <li class="md-nav__item">
-  <a href="#part-1-using-the-installer" class="md-nav__link">
-    Part 1 - Using the Installer
-  </a>
-  
-</li>
-        
-          <li class="md-nav__item">
-  <a href="#part-2-switching-the-uefiefi-boot-entry" class="md-nav__link">
-    Part 2 - Switching the UEFI/EFI boot entry
-  </a>
-  
-</li>
-        
-      </ul>
-    </nav>
-  
-</li>
-      
-        <li class="md-nav__item">
-  <a href="#use-syslinux-efi-to-run-bliss-os-7x10x11x" class="md-nav__link">
-    Use syslinux EFI to run Bliss OS 7.x/10.x/11.x
-  </a>
-  
-    <nav class="md-nav">
-      <ul class="md-nav__list">
-        
-          <li class="md-nav__item">
-  <a href="#part-1-grab-the-required-tools" class="md-nav__link">
-    Part 1 - Grab the required tools
-  </a>
-  
-</li>
-        
-          <li class="md-nav__item">
-  <a href="#part-2-get-bliss-os" class="md-nav__link">
-    Part 2 - Get Bliss OS
-  </a>
-  
-</li>
-        
-          <li class="md-nav__item">
-  <a href="#part-3-get-the-syslinux-efi-bootstrap" class="md-nav__link">
-    Part 3 - Get the syslinux EFI bootstrap
-  </a>
-  
-</li>
-        
-          <li class="md-nav__item">
-  <a href="#part-4-version-specific" class="md-nav__link">
-    Part 4 - Version specific
-  </a>
-  
-    <nav class="md-nav">
-      <ul class="md-nav__list">
-        
-          <li class="md-nav__item">
-  <a href="#if-you-are-using-bliss-7x" class="md-nav__link">
-    If you are using Bliss 7.x
-  </a>
-  
-</li>
-        
-      </ul>
-    </nav>
-  
-</li>
-        
-          <li class="md-nav__item">
-  <a href="#if-you-are-using-bliss-10x" class="md-nav__link">
-    If you are using Bliss 10.x
-  </a>
-  
-</li>
-        
-          <li class="md-nav__item">
-  <a href="#part-5-creating-the-data-image" class="md-nav__link">
-    Part 5 - Creating the data image
-  </a>
-  
-</li>
-        
-      </ul>
-    </nav>
-  
-</li>
-      
-        <li class="md-nav__item">
-  <a href="#custom-install-bliss-os-8x10x11x-uefiesp-64-bit" class="md-nav__link">
-    Custom Install - Bliss OS 8.x/10.x/11.x UEFI/ESP (64-bit)
-  </a>
-  
-    <nav class="md-nav">
-      <ul class="md-nav__list">
-        
-          <li class="md-nav__item">
-  <a href="#part-1-mounting-your-uefiesp-partition" class="md-nav__link">
-    Part 1 - Mounting Your UEFI/ESP Partition
-  </a>
-  
-    <nav class="md-nav">
-      <ul class="md-nav__list">
-        
-          <li class="md-nav__item">
-  <a href="#cmd-is-not-showing-up-what-should-i-do" class="md-nav__link">
-    cmd is not showing up, what should I do?
-  </a>
-  
-</li>
-        
-      </ul>
-    </nav>
-  
-</li>
-        
-          <li class="md-nav__item">
-  <a href="#part-1-alternate-esp-setup" class="md-nav__link">
-    Part 1 (alternate) - ESP setup
-  </a>
-  
-</li>
-        
-          <li class="md-nav__item">
-  <a href="#part-1-alternate-killing-the-explorerexe" class="md-nav__link">
-    Part 1 (alternate) - Killing the explorer.exe
-  </a>
-  
-</li>
-        
-      </ul>
-    </nav>
-  
-</li>
-      
-        <li class="md-nav__item">
-  <a href="#part-2-uefi-installation" class="md-nav__link">
-    Part 2 - UEFI installation
-  </a>
-  
-    <nav class="md-nav">
-      <ul class="md-nav__list">
-        
-          <li class="md-nav__item">
-  <a href="#part-4-the-manual-blissification-of-your-pc" class="md-nav__link">
-    Part 4 - The Manual Blissification of Your PC
-  </a>
-  
-</li>
-        
-      </ul>
-    </nav>
-  
-</li>
-      
-        <li class="md-nav__item">
-  <a href="#install-bliss-os-on-a-vm-virtualbox" class="md-nav__link">
-    Install Bliss OS on a VM (virtualbox)
-  </a>
-  
-</li>
-      
-        <li class="md-nav__item">
-  <a href="#specific-surface-model-instructions" class="md-nav__link">
-    Specific Surface model instructions
-  </a>
-  
-</li>
-      
-        <li class="md-nav__item">
   <a href="#conclusion" class="md-nav__link">
     Conclusion
   </a>
@@ -1029,8 +715,25 @@
 </ul>
 <p>If the following information is not supplied, your inquiry will be <strong>ignored.</strong></p>
 <p>These instructions have changed quite a bit for Android Pie, so consider this section a <strong>work in progress.</strong> Thank you for your patience!</p>
+<h2 id="windows-installation-method">Windows installation method</h2>
+<p><strong>This is the current recommended method for beginners!</strong></p>
+<p>We recommend beginners to use this method as it is the least error-prone and non-destructive. The following instructions were adapted from the Android-x86 project, so some of the images are from them. <a href="https://www.android-x86.org/installhowto.html">To look at Android-x86's original installation guide, click here.</a></p>
+<p>When booting into the installer, choose "Installation - Install Android-x86 to harddisk":</p>
+<p><img alt="beginner-installation-install-1" src="https://i.imgur.com/gEnnGFp.png" /></p>
+<p>Once the installer boots, you will be asked to select the target drive. Choose the NTFS drive that houses your current Windows install. You do <strong>not</strong> need a separate partition, as the installer will create an image on your Windows partition.</p>
+<p><img alt="beginner-installation-install-2" src="https://i.imgur.com/fpMo5GS.png" /></p>
+<p>Choose "Do not re-format" on the next screen. It is important that you choose "Do not re-format", as any other option will cause the installer to continue with the <a href="#bootable-installation-method-mbruefiesp-3264-bit">"Bootable installation method"</a>, which <strong>will</strong> result in <strong>permanent data loss</strong>, including your Windows partition!</p>
+<p><img alt="beginner-installation-install-3" src="https://i.imgur.com/QSDt8ia.png" /></p>
+<p>Choose "Yes" when prompted about the <code>grub</code> bootloader:</p>
+<p><img alt="beginner-installation-install-4" src="https://i.imgur.com/PfmjHHi.png" /></p>
+<p>The installer will ask whether or not you want to make the system partition read/write-able. If you want to root your installation, you will choose "Yes" here. Otherwise, choose "No."</p>
+<p><img alt="beginner-installation-install-5" src="https://i.imgur.com/SXEeevy.png" /></p>
+<p>The installer will begin to write the changes to the disk. This will take some time. Go grab a coffee!</p>
+<p><img alt="beginner-installation-install-6" src="https://i.imgur.com/iQ4tEAD.png" /></p>
+<p>Then the installer will ask you how much space you want to allocate for the data image. Most users choose 8 GB, 16 GB, or 32 GB.</p>
+<p>Congratulations! You should now have a functional dual-boot with Bliss OS!</p>
 <h2 id="bootable-installation-method-mbruefiesp-3264-bit">Bootable installation method - MBR/UEFI/ESP (32/64-bit)</h2>
-<p><strong>This is the current recommended method!</strong></p>
+<p><strong>This is the current recommended method for advanced users!</strong></p>
 <p>Overview of the steps:</p>
 <ul>
 <li>Download the ISO file</li>
@@ -1066,200 +769,6 @@
 <p>The process will install and create the data directory/image, so be patient. When finished, the installer will then ask if you want to run Android-x86. You can just reboot here. Make sure you remove the USB drive.</p>
 <p>If we have followed all the directions correctly, you should be presented with a <code>grub</code> boot menu. You can choose your <code>bliss_android_x86</code> option (or <code>android-x86</code>), and it will boot into Bliss OS. If you want to customize your <code>grub</code> boot entry, search the web first. We use the same <code>grub</code> setup that the Android-x86 project uses, so their forums will contain just about all the info you will need. </p>
 <p>Congratulations! We hope you enjoy using Bliss OS.</p>
-<h2 id="windows-based-installer-uefiesp-64-bit">Windows-based installer - UEFI/ESP (64-bit)</h2>
-<p>This method is <strong>no longer supported</strong> due to too many people not understanding computer basics and breaking things. <strong>Proceed at your own risk.</strong> This method might be the easiest currently if you understand what you are doing.</p>
-<p>For the overall instructions on using this method, please refer to the <a href="https://forum.xda-developers.com/android/software/winapp-android-x86-installer-uefi-t3222483">tool's original thread</a>. The tools have been updated by Team Bliss for easy installation on UEFI/ESP machines. The <a href="https://github.com/BlissRoms-x86/Androidx86-Installer-for-Windows/tree/master/bin">builds we produce can be found here.</a> And the <a href="https://github.com/BlissRoms-x86/Androidx86-Installer-for-Windows">source for those builds can be found here.</a> This tool should work on Remix OS as well, but this has not been tested yet.</p>
-<h3 id="part-1-using-the-installer">Part 1 - Using the Installer</h3>
-<p>The installer has been updated to accept the <code>.iso</code> files for our 8.x/10.x/11.x releases. Just follow the prompts the installer gives. Refer to the original thread for any questions, and please search before asking.</p>
-<p>If you plan on using root, the process will require you to manually extract the system.img from within the system.sfs file. Then you must delete the system.sfs file after extracting. </p>
-<p><strong>Warning</strong> - for Pie, you will need to add <code>androidboot.hardware=android_x86_64</code> to the grub entry in order to boot!</p>
-<h3 id="part-2-switching-the-uefiefi-boot-entry">Part 2 - Switching the UEFI/EFI boot entry</h3>
-<p>Option one is to use the EasyUEFI tool, then switch the UEFI/EFI entry it created to boot first. Close and reboot. Option two is to use your BIOS to select the added UEFI boot entry.</p>
-<h2 id="use-syslinux-efi-to-run-bliss-os-7x10x11x">Use syslinux EFI to run Bliss OS 7.x/10.x/11.x</h2>
-<p>Thanks to @IcedCube for the original post! This method is <strong>NOT recommended</strong> as it is fairly bleeding-edge and experimental, but it should help booting on Chinese tablets that do not want to run <code>grub</code>.</p>
-<p>Use a Linux installation for the following procedure.</p>
-<h3 id="part-1-grab-the-required-tools">Part 1 - Grab the required tools</h3>
-<p>Install <code>unsquashfs</code> (part of <code>squashfs-tools</code>).</p>
-<h3 id="part-2-get-bliss-os">Part 2 - Get Bliss OS</h3>
-<p>Grab the latest build of Bliss OS 7.x/10.x/11.x.</p>
-<h3 id="part-3-get-the-syslinux-efi-bootstrap">Part 3 - Get the syslinux EFI bootstrap</h3>
-<p><a href="https://forum.xda-developers.com/showpost.php?p=74977694&amp;postcount=1237">Grab the <code>.zip</code> file from @IcedCube's original post</a>, and extract it to the root of the USB drive. This will bootstrap syslinux EFI onto it.</p>
-<p>Then, make a folder called <code>android</code>.</p>
-<p>Now, open up the <code>.iso</code> in an archive program. Extract the following files form the root directory of the <code>.iso</code> image to the USB drive's <code>android</code> folder:</p>
-<ul>
-<li><code>initrd.img</code></li>
-<li><code>ramdisk.img</code></li>
-<li><code>kernel</code></li>
-</ul>
-<p>Extract <code>system.sfs</code> to a folder somewhere, such as <code>/tmp</code>.</p>
-<p>Open a terminal and change directory (using <code>cd</code>) to <code>/tmp</code>. Run <code>ls</code> and confirm that <code>system.sfs</code> is shown in the file list. If there is no output, start over as the file is misplaced.</p>
-<p>Run the following:</p>
-<p><code>unsquashfs ./system.sfs</code></p>
-<p>This will make a new directory called <code>squashfs_root</code>.</p>
-<h3 id="part-4-version-specific">Part 4 - Version specific</h3>
-<h4 id="if-you-are-using-bliss-7x">If you are using Bliss 7.x</h4>
-<p>Change directory to <code>squashfs_root</code> and run <code>ls</code>. There should only be one file - a <code>system.img</code> inside the directory. Copy the file to the USB's <code>android</code> folder.</p>
-<h3 id="if-you-are-using-bliss-10x">If you are using Bliss 10.x</h3>
-<p>Change directory to <code>squashfs_root</code>. The structure is a complete Android root filesystem. To install Bliss OS, the files will need to be in a system image. The following steps will guide you through creating a 2 GB <code>system.img</code> file, formatting it, mounting it, and copying the contents of <code>squashfs_root</code> into the new disk image.</p>
-<p>Execute:</p>
-<pre><code>mkdir /mnt/tempMount
-truncate /tmp/system.img --size=2G
-mkfs.ext4 -m0 /tmp/system.img
-sudo mount -o loop /tmp/system.img /mnt/tempMount
-sudo cp -prv /tmp/squashfs_root/* /mnt/tempMount/
-sync
-sudo umount /mnt/tempMount
-</code></pre>
-<p>The <code>sync</code> command might take some time.</p>
-<p>Now copy the <code>/tmp/system.img</code> file to your USB's Android folder.</p>
-<h3 id="part-5-creating-the-data-image">Part 5 - Creating the data image</h3>
-<p>First, find where your USB drive is mounted. It is usually in <code>/mnt</code> or <code>/media</code> (ex. <code>/media/USB</code>).</p>
-<p><code>cd</code> into the <code>android</code> folder.</p>
-<p>We will create a 3 GB data image file. You can attempt to create a 4 GB image but FAT32 maxes out at 4 GB per file. If your system supports exFAT or NTFS, you may try and use it.</p>
-<pre><code>truncate data.img --size=3G
-mkfs.ext4 -m0 data.img
-sync
-</code></pre>
-<p>This will be an completely empty <code>ext4</code> disk image, but will be enough to run Bliss.</p>
-<p>Finally, check to ensure everything is in structured like so:</p>
-<pre><code>&lt;ROOT&gt;
-- syslinux.cfg
-- android/
--- kernel
--- system.img
--- data.img
--- ramdisk.img
--- initrd.img
-- EFI/
--- BOOT/
---- bootia32.efi
---- bootx64.efi
---- ldlinux.e32
---- ldlinux.e64
-</code></pre>
-<p>Need to add some kernel parameters? Open <code>syslinux.cfg</code> and add them before the <code>initrd=/android/initrd.img</code> statement.</p>
-<p>Unmount the USB from your computer. Plug it into your device and use the BIOS to boot from your UEFI USB Drive, partition 1. If all goes well, you will get a black screen with small white text saying "Booting Android..." followed by loading files. You should get the Linux kernel text, then see the Bliss boot animation play after a couple minutes depending on your USB drive read/write speed.</p>
-<h2 id="custom-install-bliss-os-8x10x11x-uefiesp-64-bit">Custom Install - Bliss OS 8.x/10.x/11.x UEFI/ESP (64-bit)</h2>
-<p>Just as a reminder, Team Bliss is <strong>NOT</strong> responsible for any damage caused by this guide. By continuing, you automatically agree to these terms.</p>
-<h3 id="part-1-mounting-your-uefiesp-partition">Part 1 - Mounting Your UEFI/ESP Partition</h3>
-<p>You will want to make sure you can view hidden and system files in Explorer options. Once you do that, hit the start menu, and type in <code>cmd</code>. Once "Command Prompt" shows up, right click on it and choose "Open as administrator".</p>
-<h4 id="cmd-is-not-showing-up-what-should-i-do"><code>cmd</code> is not showing up, what should I do?</h4>
-<p>Press the Windows key and the R key to bring up the "Run..." dialog. Type in <code>cmd</code>, and then press Ctrl-Shift-Enter. Press "Yes" on the UAC popup.</p>
-<p>Run the following:</p>
-<pre><code>mountvol X: /S
-</code></pre>
-<p>Then check to see if it is mounted already. Run "Task Manager" by either</p>
-<ul>
-<li>Pressing Ctrl-Alt-Del and then clicking on "Task Manager", or</li>
-<li>Pressing Ctrl-Shift-Esc</li>
-</ul>
-<p>Click on "File", "Run new task", "Browse", "This computer", and SYSTEM (X or type in <code>X:</code> in the filepath bar. If you cannot access <code>X:</code>, then that could mean one of three things.</p>
-<ul>
-<li>You have an ESP setup (follow the installation method below)</li>
-<li>You have a legacy MBR setup</li>
-<li>Your setup has a custom boot sequence</li>
-</ul>
-<h3 id="part-1-alternate-esp-setup">Part 1 (alternate) - ESP setup</h3>
-<p>Windows 10 sometimes has an EFI partition already mounted under drive letter <code>Z:</code>, hidden. A very quick and easy way to access the ESP (EFI System Partition) in Windows 10 without using the command line is to start "Task Manager" (check above if you forgot the steps), and then click on "File", "Run new task", "Browse", "This computer", and SYSTEM (Z or type in <code>Z:</code> in the filepath bar).</p>
-<p>Now go to <code>boot/grub/grub.cfg</code> and edit it accordingly with Notepad++ or another text editor. Save the file and your're ready to go!</p>
-<h3 id="part-1-alternate-killing-the-explorerexe">Part 1 (alternate) - Killing the <code>explorer.exe</code></h3>
-<p>Run <code>cmd</code> as admin and enter the following command:</p>
-<pre><code>taskkill /im explorer.exe /f
-</code></pre>
-<p>This will kill the <code>explorer.exe</code> process - don't be surprised if it shows a warning. This step is sometimes required, because by default <code>explorer.exe</code> is ran by the currently logged in user, and it has to be run by the "Administrator" in order to view the mounted system drive. <strong>The "Administrator" account is not the same as an account with administrative privileges.</strong></p>
-<pre><code>mountvol X: /s
-</code></pre>
-<p>This will mount the system partition that usually consists of UEFI related files. <code>X:</code> is the letter of the drive - you can use whatever letter you want, but it has to be free for assignment. Then type:</p>
-<pre><code>explorer
-</code></pre>
-<p>This will run <code>explorer</code> as "Administrator" and will allow you to browse the mounted system partition.</p>
-<p>The above may not work for all devices, as some handle UEFI differently.</p>
-<h2 id="part-2-uefi-installation">Part 2 - UEFI installation</h2>
-<p>Let's start by downloading the required files. <a href="https://www.androidfilehost.com/?w=files&amp;flid=143191">Here is a customized UEFI boot for 32/64-bit machines.</a></p>
-<p>Please note that if you came from our Nougat builds to our Bliss OS 8.x builds, you will have to edit the <code>grub.cfga</code>.</p>
-<p>If you are using Bliss OS 8.x/10.x, please use the <code>grub</code> entry below as a guide:</p>
-<pre><code>menuentry 'Bliss-x86' --class android {
-    search --file --no-floppy --set=root /AndroidOS/system.sfs
-    linux /AndroidOS/kernel root=/dev/ram0 SRC=/AndroidOS androidboot.selinux=permissive androidboot.hardware=android_x86_64 quiet DATA=
-    initrd /AndroidOS/initrd.img
-}
-</code></pre>
-<p>If you are installing on <code>ext3</code>/<code>ext4</code>, due to a bug in the install you will have to use the following <code>grub</code> entry setup:</p>
-<pre><code>menuentry 'Bliss-x86' --class android {
-    search --file --no-floppy --set=root /AndroidOS/system.sfs
-    linux /AndroidOS/kernel root=/dev/ram0 SRC=/AndroidOS  androidboot.selinux=permissive androidboot.hardware=android_x86_64 quiet DATA=
-    initrd /AndroidOS/initrd.img
-}
-</code></pre>
-<p>Now that we have the partition mounted, we can copy that <code>BOOT</code> directory to your UEFI partition using <code>explorer</code> as the Administrator or by using the "New Task" dialog from Task Manager. (See above if you forgot the steps!) Once it is copied, go back to the Administrator <code>cmd</code> prompt and type:</p>
-<pre><code>mountvol X: /D
-</code></pre>
-<p>or if you used <code>Z:</code>, type:</p>
-<pre><code>mountvol Z: /D
-</code></pre>
-<p>This will dismount the UEFI/ESP volume for safe reboot. We then suggest you use EasyUEFI here to create the UEFI boot entry. Open the app, and create a new entry. Select your UEFI partition, and in the "File" Path, click "Browse" and use the file manager window to browse to your <code>BOOT/grub/grubx64.efi</code> file. Click OK, and then choose the new <code>grub</code> entry and move it to the top. Make sure Secure Boot is turned off or else it likely will just boot back to Windows.</p>
-<h3 id="part-4-the-manual-blissification-of-your-pc">Part 4 - The Manual Blissification of Your PC</h3>
-<p>To do a manual "Wubi like" install of Bliss OS after you install the UEFI entry, you will need to open the Bliss OS <code>.iso</code>/<code>.img</code> with 7zip, and then drag all the <code>.img</code> &amp; <code>.sfs</code> files to <code>C:/android-x86</code> or whatever your target drive is (make sure your <code>grub</code> entries match where you are putting these). Then create your <code>data.img</code>. We suggest using a tool like RMXtools (use version 1.7) from XDA to create it. Check the tool's thread for detailed instructions. You will want to create your <code>data.img</code> inside that <code>android-x86</code> folder.</p>
-<p>You can now reboot if you have installed the custom UEFI entry right and selected it using EasyUEFI. You should boot right to the Android-x86 <code>grub</code> theme. There, you can use up and down to select, and return to boot that entry. You can also hit <code>e</code> to edit the selected entry. You will want to pay attention to which entry you select, since there will be one for <code>Bliss-x86(32bit)</code> and one or <code>Bliss-x86_64(64bit)</code>.</p>
-<h2 id="install-bliss-os-on-a-vm-virtualbox">Install Bliss OS on a VM (virtualbox)</h2>
-<p>This method is <strong>incomplete</strong>, a <strong>work-in-progress</strong>. Android in general do not run great in VMs, because they do not have the proper drivers. As such performance is greatly reduced if you use this method. Please only install Bliss OS in VMs for evaluation, and keep in mind that the performance exhibited by Bliss OS in such an environment is not a true representation of actual performance on bare metal. With that in mind, let's get started!</p>
-<p>First, make sure your CPU is capable of running VMs. For Intel, it is usually Intel VT-x and VT-d. For AMD, it is usually AMD-V. You may also need IOMMU support, although it is probably not necessary since you won't be passing through GPUs.</p>
-<p>Download the latest Bliss OS <code>.iso</code> from our website. Then, download the latest version of VirtualBox, and the latest VirtualBox <strong>extension pack</strong>. Install both executables.</p>
-<p>Once inside VirtualBox, click on "New." For the name, type "Bliss OS." For the type, select <code>Linux</code>, and then <code>Linux 2.6 / 3.x / 4.x (64-bit)</code> for the version. Set memory size to 2048 MB (2 GB) or more. For the disk, accept the default options for the disk type. For the size, set it to 20 GB. VirtualBox should initialize a new virtual machine.</p>
-<p>We need to tweak a couple more settings. Click on "Settings" on the top bar. Allocate more logical processors in System &gt; Processor. Drag the slider to the right, keeping it <strong>inside</strong> the green bar, as you want to leave a couple of logical processors for the host operating system. For the display, try allocating all of the VRAM. (128 MB most likely) Enable 3D Acceleration. Click OK to save settings.</p>
-<p>Now click on Start. VirtualBox will ask you for the CD image. Click on the folder with the green up arrow, and then select the ISO you downloaded earlier.</p>
-<p>Select "Installation - Install Bliss-OS to harddisk" Press D to detect devices. Press C to create and modify partitions. If asked, select No for GPT. Select New, Primary, full size, and then make it bootable. Write to disk. Quit. Select the partition and then reformat to ext4. Select Yes to install GRUB. Select Yes to make the /system directory writable.</p>
-<p>At this point the installation should be complete. But when you reboot, you will notice that the screen is completely black with a cursor at the top-left. This is because there is no display drivers for the virtual machine. Reset the instance, edit the boot parameters, and add <code>nomodeset</code> to the end. Bliss OS should then boot fully.</p>
-<p>Congratulations! You should have a fully working Bliss OS install in a VM, or at least something that works... even if it may be slow. Again, Android on VM is generally not a good idea and you will get a lot more performance if you install Bliss OS to the actual hardware.</p>
-<h2 id="specific-surface-model-instructions">Specific Surface model instructions</h2>
-<p>Reference posts <a href="https://forum.xda-developers.com/showpost.php?p=78015375&amp;postcount=76">here</a> and <a href="https://forum.xda-developers.com/showpost.php?p=76896155&amp;postcount=2107">here</a>.</p>
-<p>Many of you have a Surface device and would like to run Android on it. You're in luck, because this project was started with a Surface Pro 3 to test with back in Android Nougat. The device has since been retired and development has continued on a Surface Book, an IPTS device. This means it requires a specific set of firmware for proper functioning. For all other Surface models, the user must upgrade their own firmware, because it is too large of a burden to build for all Surface models without having those devices to test with.</p>
-<p>To start, you will need to grab the right firmware for your device.</p>
-<p>Surface Series Devices:</p>
-<ul>
-<li>Series 5 devices:</li>
-<li>Surface Book 2</li>
-<li>Surface Pro 2017</li>
-<li>Series 4 devices</li>
-<li>Surface Book</li>
-<li>Surface Pro 4</li>
-<li>Surface Laptop</li>
-<li>Series 3 devices:</li>
-<li>Surface Pro 3</li>
-</ul>
-<p>For the ipts_firmware files (series 4/5 devices only), please select the correct version for your device:</p>
-<ul>
-<li>v76 for the Surface Book</li>
-<li>v78 for the Surface Pro 4</li>
-<li>v79 for the Surface Laptop</li>
-<li>v101 for Surface Book 2 15"</li>
-<li>v102 for the Surface Pro 2017</li>
-<li>v137 for the Surface Book 2 13"</li>
-</ul>
-<p>For the i915_firmware files (series 3/4/5 devices), please select the correct version for your device:</p>
-<ul>
-<li>kbl for series 5 devices</li>
-<li>skl for series 4 devices</li>
-<li>bxt for series 3 devices</li>
-</ul>
-<p>All <a href="https://github.com/jakeday/linux-surface/tree/master/firmware">firmware files can be found here.</a></p>
-<p>For Surface Go users, you will have to remove some files and replace with @jakeday's firmware. Please <a href="https://www.reddit.com/r/SurfaceLinux/comments/9t53gq/wifi_fixed_on_surface_go_ubuntu_1810/">see this thread on Reddit</a> for detailed information.</p>
-<p>Once you have the right firmware you need, you should copy it to a folder on your Bliss install (<code>SD_card_root/surface</code>), making sure to put the right firmware in the right folders:</p>
-<ul>
-<li>IPTS firmware: <code>SD_card_root/surface/intel/ipts</code></li>
-<li>ath10k firmware (some models): <code>SD_card_root/surface/ath10k</code></li>
-<li>mrvl firmware (some models): <code>SD_card_root/surface/mrvl</code></li>
-<li>mwlwifi firmware (some models): <code>SD_card_root/surface/mwlwifi</code></li>
-<li>nvidia firmware for SB2: <code>SD_card_root/surface/nvidia</code></li>
-</ul>
-<p>Next, open a terminal (we include one you can enable in "Developer Options"). In the terminal, enter the following commands, giving permission to the superuser popup dialog when prompted:</p>
-<pre><code>su
-mv -f SD_card_root/surface/* system/lib/firmware/
-</code></pre>
-<p>Then you can restart:</p>
-<pre><code>reboot
-</code></pre>
-<p>It should recognize and load the correct firmware versions for your device upon reboot if you did everything correctly.</p>
 <h2 id="conclusion">Conclusion</h2>
 <p>Thanks for following along! If you want to check out the next guide, <a href="../extras/">click here!</a></p>
 <p>Having problems with your new installation? <a href="../troubleshooting/">Check out Troubleshooting.</a></p>
@@ -1283,7 +792,7 @@
     <div class="md-footer-nav">
       <nav class="md-footer-nav__inner md-grid">
         
-          <a href="../extras/" title="Extras" class="md-flex md-footer-nav__link md-footer-nav__link--prev" rel="prev">
+          <a href="../installation-guide-surface-devices/" title="Installation Guide (Surface devices)" class="md-flex md-footer-nav__link md-footer-nav__link--prev" rel="prev">
             <div class="md-flex__cell md-flex__cell--shrink">
               <i class="md-icon md-icon--arrow-back md-footer-nav__button"></i>
             </div>
@@ -1292,7 +801,7 @@
                 <span class="md-footer-nav__direction">
                   Previous
                 </span>
-                Extras
+                Installation Guide (Surface devices)
               </span>
             </div>
           </a>