Initial Commit
diff --git a/_faq/ADBSideload.markdown b/_faq/ADBSideload.markdown
new file mode 100644
index 0000000..1e7f887
--- /dev/null
+++ b/_faq/ADBSideload.markdown
@@ -0,0 +1,23 @@
+---
+layout: post
+title: "What is ADB Sideload and how can I use it?"
+---
+
+<div class='page-heading'>What is ADB sideload?</div>
+<hr />
+ADB sideload is a new feature that was added to AOSP recovery in Jelly Bean. As of version 2.3, TWRP now supports ADB sideload mode. ADB sideload is a different ADB mode that you can use to push and install a zip using one command from your computer. Most likely ADB sideload won't be very useful for your average recovery user, but ADB sideload can be a huge time-saver for a ROM developer.
+
+<div class='page-heading'>How do I use ADB sideload?</div>
+<hr />
+
+<ol>
+<li>Have a recovery installed on your device that supports ADB sideload like TWRP 2.3 or higher</li>
+<li>Have newer ADB binaries installed on your computer. If it's been a while since you installed ADB on your computer, you may need to get the latest ADB binaries in platform-tools from the Android SDK. You will need version 1.0.29 or higher (1.0.32 or higher is required for TWRP versions 2.8.2.0 and higher). You can find your current version by typing "adb version" at the command line.</li>
+<li>Set the device into ADB sideload mode. In TWRP you do this by going to Advanced then ADB Sideload.</li>
+<li>From the command line, type adb sideload /path/to/rom.zip</li>
+</ol>
+For TWRP versions lower than 2.8.2.0, the file will be copied to your device to whatever the current storage location is that you have selected in the mount page. It will always be placed in the root of that storage location and named sideload.zip (e.g. /sdcard/sideload.zip) and it will automatically delete / overwrite any existing sideload.zip you may have on your device. As soon as the file is copied to your device, it will automatically be installed. When the install is finished you will be presented with a reboot system button so that you can reboot to test your zip.
+
+TWRP versions 2.8.2.0 and higher will stream the zip from your PC without storing it on your device. If you wish to store the zip on your device for later, you should not use sideload and instead use adb push or some other method to copy the zip to the device.
+
+Note that sideload mode is a separate ADB mode. While in sideload mode, regular ADB commands will not work. Once the zip has been copied to the device and the install starts (or if you hit the cancel button) regular ADB mode will resume.
diff --git a/_faq/datamedia.markdown b/_faq/datamedia.markdown
new file mode 100644
index 0000000..eb2a7ed
--- /dev/null
+++ b/_faq/datamedia.markdown
@@ -0,0 +1,20 @@
+---
+layout: post
+title: "What is a data/media device?"
+---
+
+I'm writing this page because there seems to be a lot of confusion about how many of the newer Android devices work. Starting in Honeycomb 3.0 with the Xoom, Google changed the way that they handled storage. Instead of having a "data" partition with your apps and a separate "sdcard" partition for storage, Google started giving you a single, very large data partition. Inside /data is a folder at /data/media that contains all of the contents of what you think of as your internal sdcard.
+
+Since /data/media is part of /data, we pretty much never actually format the data partition. Formatting data, of course, also removes the media folder that contains the internal sdcard. When you choose a factory reset, instead of formatting, we use rm -rf commands to remove all the folders except for the media folder so that we can remove all of your apps and settings while leaving your "sdcard" intact. In TWRP we also have a wipe internal storage option that rm -rf's the media folder and a "Format Data" option that formats to recreate the entire file system in case something goes completely wrong or to remove device encryption.
+
+When you're booted to Android, Android fuses the media folder to /sdcard and emulates a FAT files system that doesn't have permissions for legacy apps. We don't currently have fuse in recovery, so we just add an extra mount command to mount /data/media to /sdcard so in recovery you still have to worry about permissions on /sdcard.
+
+Because the "internal sdcard" is not a true FAT file system, you can't mount it via USB storage. Well, that's not technically true, but the vast majority of people use Windows computers and Windows doesn't recognize ext4. If we were to allow you to mount the data partition via USB storage, Windows would claim that the device wasn't formatted and offer to format it for you, which, as you can imagine, would be a disaster. The whole ext4 setup is another reason that Android switched to using MTP for transferring files. Most of these devices don't have the necessary kernel configuration to even support USB storage mode, so it's not very easy to enable USB storage if we even wanted to try. With TWRP 2.8.0.0 and higher, we now support MTP. MTP is the protocol most newer devices use to transfer files on your PC. If for some reason MTP is not working for you or if you're using an older version of TWRP, you can use adb to push and pull files to and from your device.
+
+As a special note, if you choose to do a factory reset from your ROM, even if the ROM says that it will wipe everything including the internal storage, well, that's not what TWRP will do. A stock AOSP recovery would format data including the "sdcard" but TWRP will use its regular factory reset setup that leaves the internal storage intact.
+
+There are a couple of nice gains with using this setup vs the old data + FAT storage partition. With /data/media you, as the user get more control over how you use your storage. If you have a ton of apps, then that's no problem since you have a huge data partition to work with. If you don't have a lot of apps, you get more room to use for storing things like movies. Further, ext4 doesn't suffer from the 4GB file size limit that FAT has, so you can have a large, high-def movie on your device if you like. I'm sure another motivating factor was to get Android away from using FAT which is a Microsoft creation. Performance on ext4 in Android is also probably better than FAT. As a downside, data media devices tend to store a lot more app data in the "data" section and so backups on these devices tend to be larger.
+
+Android 4.2 has changed things with /data/media devices a little bit due to the multi-user support that came in 4.2. Each user is assigned a subfolder in /data/media. The main user gets /data/media/0 and subsequent users get /data/media/10 and /data/media/11 and so on. If you switch users in Android 4.2, the system will remount the /sdcard folder to point to the proper user's folder. TWRP has been updated to use the /data/media/0 folder starting in 2.3.2.0.
+
+Another "feature" of 4.2 is that when you "update" to 4.2 it may attempt to upgrade your /data/media to multi-user. If you're running an older version of TWRP than 2.3.2.0 or newer, a factory reset may trigger multiple upgrades, causing your "sdcard" to get moved to /data/media/0 then /data/media/0/0 and then /data/media/0/0/0 and so on depending on how many times you "upgraded". This may cause backups to not be visible in TWRP. Also, there currently isn't a good way to go back to a 4.1 ROM after using a 4.2 ROM without having to manually move your files around.
diff --git a/_faq/howtocompiletwrp.markdown b/_faq/howtocompiletwrp.markdown
new file mode 100644
index 0000000..e267ce9
--- /dev/null
+++ b/_faq/howtocompiletwrp.markdown
@@ -0,0 +1,6 @@
+---
+layout: post
+title: "How can I get TWRP for my device? (how to compile TWRP)"
+---
+
+We can't afford to buy every device made and many times certain devices are only available in other countries. TWRP is fully open source, so you can port TWRP to your device using our [compile guide here](http://forum.xda-developers.com/showthread.php?p=32965365).
diff --git a/_faq/noos.markdown b/_faq/noos.markdown
new file mode 100644
index 0000000..23566d8
--- /dev/null
+++ b/_faq/noos.markdown
@@ -0,0 +1,14 @@
+---
+layout: post
+title: "No OS Installed! Are you sure you wish to reboot?"
+---
+
+If you're seeing this message in TWRP, this usually means that, one way or another, you have wiped your system partition. How you can fix this issue depends on what device you have and how you want to go about fixing it.
+
+If you have a backup, you may be able to restore your backup to reinstate a working system or OS.
+
+You may be able to find a new "ROM" for your device at places like XDA or use Google to try to locate one. If you have TWRP 2.8.0.0 or newer you may be able to simply plug your device into your computer and use MTP to transfer files. If your device has a removable SD card you can use a card reader to easily transfer the flashable zip to the card then install it under the Install button in TWRP. On some devices you may also be able to use a USB thumb drive along with a special "On-The-Go" cable known as USB OTG to get the file installed. Some devices may support USB mass storage mode (found under the mount menu) to easily copy the file to the device. If all else fails, you can install ADB drivers and software to transfer files using adb push or pull. If you are using Windows (as most people do), it may be difficult to get your computer to properly recognize your device. Windows is really picky about its drivers. You may have to force install a driver or try something like universal or naked ADB drivers.
+
+If the above does not work for you, you can search again on XDA or Google to locate a guide for returning your device back to stock. The process varies depending on what type and brand of device you have. For HTC devices search for "RUU back to stock" plus your device's name. For Samsung search for "Odin back to stock" plus your device name. LG devices often use a "KDZ return to stock" plus your device name. Google posts factory images for Nexus devices here. Motorola posts factory images for some devices here.
+
+If you still can't get your device working, don't bother using the Contact Us button on our web page. We won't respond to these kinds of support requests.
diff --git a/_faq/officialota.markdown b/_faq/officialota.markdown
new file mode 100644
index 0000000..b495f18
--- /dev/null
+++ b/_faq/officialota.markdown
@@ -0,0 +1,14 @@
+---
+layout: post
+title: "Official OTA Updates and TWRP"
+---
+
+Installing official updates from your manufacturer or carrier is not supported by TWRP.
+
+Most official updates are differential in nature. On a completely stock device when used in the way that Google and manufacturers intend, users will never modify the system partition. A differential update means that the update does not replace the entire system. In many cases the update doesn't even replace entire files and instead just patches the difference between the old file and the new file to bring it up to date for the new version. This method makes the updates smaller which is good when you have thousands of devices that will be downloading the update over a carrier's data network, usually within a short time frame. Unfortunately this method also means that users who have modified their system by rooting, installing busybox, and removing unwanted system apps may experience unexpected behavior when they install a differential update.
+
+Also, device manufacturers may have made changes to their recoveries that we aren't aware of and device makers do not have to release source code for their recoveries (AOSP recovery is Apache license which does not require them to release their source for these changes). Those changes may not be present or supported by TWRP which may result in unexpected behavior, especially when it comes to updating items like radios, bootloaders, and modems.
+
+Installing official updates usually removes root and replaces your custom recovery with a copy of a stock recovery. Most of the time the best way to get a new update onto your device is to simply wait a couple of days for ROM makers for your device to come up with ROMs that are based on the new update that you can safely and easily install.
+
+If you've read all this and still insist that you want to install an official update from your manufacturer, the recommended process is to first return your device to completely stock including replacing TWRP with a copy of the stock recovery. Because the methods for returning to stock vary depending on the device, you will need to use Google to locate a guide for returning to stock and/or finding and installing a copy of the stock recovery. Note that there is no "uninstall process" for removing TWRP. In almost all cases the process is to simply install a different recovery.
diff --git a/_faq/removetwrp.markdown b/_faq/removetwrp.markdown
new file mode 100644
index 0000000..7e00b2e
--- /dev/null
+++ b/_faq/removetwrp.markdown
@@ -0,0 +1,8 @@
+---
+layout: post
+title: "How can I uninstall or remove TWRP from my device?"
+---
+
+For the vast majority of devices, you don't actually remove TWRP to get back to the stock recovery. Installing a different recovery is your only real option. Simply install whatever recovery that you want and that will overwrite or replace TWRP. Usually you can follow the instructions on our website for installing TWRP manually, only use the file for whatever recovery you are choosing to install instead of the TWRP file.
+
+Note, we don't keep or maintain a database of stock recoveries. If you are trying to reinstall the stock recovery, you will have to find a copy of the stock recovery on your own.
diff --git a/_faq/securetwrp.markdown b/_faq/securetwrp.markdown
new file mode 100644
index 0000000..82439c1
--- /dev/null
+++ b/_faq/securetwrp.markdown
@@ -0,0 +1,12 @@
+---
+layout: post
+title: "Why doesn't TWRP have password protection?"
+---
+
+I've had people ask enough for a protected TWRP that I'm creating this page as a response so I don't have to retype. If you're seeing this page, you're probably asking, "Why doesn't TWRP offer password protection?" You want to lock down your device so that a would-be theif won't be able to wipe your device to get past your lockscreen and/or so they can't wipe away that cool app you bought from the Play Store that will let you track your stolen device via GPS. Well, here's the short answer:
+
+Nothing trumps physical access to your device. If you've lost it, there's no way that TWRP can secure it.
+
+For a longer answer, it's very easy for anyone with just a little bit of knowledge to get around any kind of security that TWRP might have. All they have to do is flash one of the other recoveries that's available that doesn't have password protection to get around it. Most, if not all devices have ways to flash recovery without needing to boot to either Android or recovery (usually via fastboot or download mode / Odin). Quite literally the only way to truly secure your device would be to render the USB port completely unusable which isn't an option for most newer devices that don't have removable batteries. Even then most devices could still be worked with via jtag though it's unlikely that a thief will go to the trouble of paying for a jtag service on a device that has a broken USB port. (Note: I am not recommending that you purposely damage your USB port as it will also likely make it very difficult to recover your device if anything ever goes wrong!)
+
+I also don't want to offer a lockscreen / password protection because it offers such a superficial level of protection. Users rarely read and would skip over any disclaimers that we have that indicate that any protection that we displayed indicating that their device really isn't secure. If your device has fallen into someone else's hands, your best case scenario should be that you hope that they don't get your personal data. If you don't want someone getting your personal data, use Android's device encryption and a good lockscreen.
diff --git a/_faq/whattobackup.markdown b/_faq/whattobackup.markdown
new file mode 100644
index 0000000..2567467
--- /dev/null
+++ b/_faq/whattobackup.markdown
@@ -0,0 +1,8 @@
+---
+layout: post
+title: "What should I back up in TWRP?"
+---
+
+The default backup options in TWRP are system, data, and boot. For most cases, this is sufficient for backing up a ROM. (Note that in some rare cases, boot isn't available for backup on certain devices). If your device has the option, backing up android_secure and/or sd-ext may be a good idea. There's usually no reason to back up cache or recovery (recovery not available for backup on some devices).
+
+Some devices have "special partitions" like WiMAX, pds, efs, etc. These partitions almost never need to be included in a normal backup. It's usually a good idea to make a single backup of these partitions and hang on to them just in case. Make use of TWRP's keyboard feature and name your backup of these special partitions accordingly.
diff --git a/_faq/whattowipe.markdown b/_faq/whattowipe.markdown
new file mode 100644
index 0000000..e5e0a8b
--- /dev/null
+++ b/_faq/whattowipe.markdown
@@ -0,0 +1,16 @@
+---
+layout: post
+title: "What should I wipe in TWRP?"
+---
+
+If you are switching ROMs (changing from one ROM to a completely different one) then you should perform a factory reset. A factory reset wipes data and cache (which includes dalvik cache). A factory reset will also wipe sd-ext and android_secure if your device has those items. 99% of the time, this is all that you need to wipe and you only need to do it once, not three times as some people would lead you to believe.
+
+If you're installing a nightly update, then oftentimes you don't need to wipe anything at all. However, if you encounter strange behavior, then you may want to consider performing a factory reset. Of course, if the ROM maker recommends that you do a factory reset during an update, then it's a good idea to follow their recommendation.
+
+The vast majority of ROMs wipe system as part of the zip install. This means that in most cases you do not need to wipe system... ever.
+
+At this point, cache (not dalvik cache) is primarily used for recovery. It's used to store the recovery log and for storing OTA (Over The Air) updates. You probably don't need to wipe cache, and cache is already wiped as part of a factory reset.
+
+In most ROMs, dalvik cache is stored in the data partition, so if you do a factory reset, you've also wiped dalvik cache. In a few custom ROMs, especially on older devices with small data partitions, the ROM maker may have moved dalvik to the cache partition to provide you with more room for apps. Since we wipe cache with a factory reset, again, you probably don't need to wipe dalvik. There are a few situations where you may need to wipe dalvik cache when installing updates, but you will know that it's needed when you are greeted with force closes when trying to open some apps.
+
+Depending on your device and its configuration, you may have options for wiping internal storage, external storage, sd-ext, android_secure, and/or an option for formatting data. There's almost no reason that you would ever need to use these items. These options are there for convenience. For instance, if you're getting ready to sell your device, then it's a good idea to wipe everything on the device so that the new owner doesn't get your private data. Note that these wipe options may not be completely destructive. If you store especially sensitive information on your device or are really concerned about your private data, then you may need to look into other options to ensure that your data is fully destroyed.