initial commit

2 files changed, 458 insertions, 0 deletions

diff --git a/files/tr/archive/b2g_os/phone_guide/flame/index.html b/files/tr/archive/b2g_os/phone_guide/flame/index.html
new file mode 100644
index 0000000000..87535ba7cc
--- /dev/null
+++ b/files/tr/archive/b2g_os/phone_guide/flame/index.html
@@ -0,0 +1,401 @@
+---
+title: Flame
+slug: Archive/B2G_OS/Phone_guide/Flame
+translation_of: Archive/B2G_OS/Phone_guide/Flame
+---
+<div class="note">
+<p><strong>Flame'inizdeki Güncellemeler</strong>: Flame cihazınızla ilgili periyodik yazılım güncellemeleri ve diğer haberleri almak için aşağıdaki e-posta listesine katılmanızı öneririz: <a href="https://mail.mozilla.org/listinfo/flamenews">https://mail.mozilla.org/listinfo/flamenews</a></p>
+</div>
+
+<p><img alt="A picture of the Flame device, showing the Firefox OS homescreen containing several app icons." src="https://mdn.mozillademos.org/files/8373/flame-dev-hud.png" style="float: left; margin-bottom: 20px; margin-right: 50px; width: 25%;"></p>
+
+<h2 id="Available_to_order" style="margin: 0px; height: 0px; text-indent: 100%; overflow: hidden; white-space: nowrap;">Available to order</h2>
+
+<p><span class="seoSummary">Flame geliştirici referans telefonu Firefox OS cihaz sürümleri içinde bir dönüm noktasıdır. Flame donanımı geliştiricilerin mükemmel içerik ve deneyimler inşa etmesine yardımcı olmak için - FWGA ekran ve çift-çekirdek işlemci gibi - birtakım temsili özellikler sunmaktadır. Aygıt modeline özgü hataları dert etmeden adresle ilgili yazılım sorunlarını test etmeyi kolaylaştıran tek bir test platformu da test edenler için faydalı olacaktır.</span></p>
+
+<p>If you have your phone in hand and want to start playing with it, developing and distributing apps, or contributing to the Firefox platform, the following links will also get you where you need to go:</p>
+
+<ul>
+ <li><a href="/en-US/Firefox_OS">Firefox OS zone</a>: For creating your own Firefox OS builds and contributing to the B2G and Gaia projects.</li>
+ <li><a href="/en-US/Apps">App Center zone</a>: For building open web apps compatible with Firefox OS.</li>
+ <li><a href="/en-US/Marketplace">Marketplace zone</a>: For information on publishing and distributing apps.</li>
+ <li><a href="https://marketplace.firefox.com/">Firefox Marketplace</a>: The best place to find and publish new Firefox OS apps.</li>
+</ul>
+
+<p>If you’d like to find out more about updating the operating system, recovering it, pushing apps to it, or phone specs, you’ll find the information you need below.</p>
+
+<h2 id="Purchasing_a_device">Purchasing a device</h2>
+
+<p>Our device manufacturer partner has made the device <a href="http://www.everbuying.com/product549652.html">available to order</a> on everbuying.com, for US$170 including global shipping (device cost is $145, shipping is $25 and custom fees may still apply, depending on the destination country). The device is bootloader- and carrier-unlocked, and it utilizes a quad-band GSM+UMTS radio so that it can work with a wide variety of operators/carriers.</p>
+
+<h2 id="Important_steps_to_follow_first">Important steps to follow first</h2>
+
+<p>There are a couple of steps you should make sure you follow for your particular operating system, before you start trying to update your device, for example by updating your Flame's version of Firefox OS, or pushing apps to your phone (both are covered below.)</p>
+
+<h3 id="All_operating_systems">All operating systems</h3>
+
+<p>You need to install ADB and Fastboot on your computer — these are applications that allow you to interact with your phone from your computer when the two are connected via the phone's USB charger cable. They are needed for Flashing your phone to a new version of Firefox OS, recovering from an unresponsive state, pushing apps to your phone, etc.</p>
+
+<div class="note">
+<p><strong>Note</strong>: If you are on Ubuntu you can install ADB and Fastboot simply by using <code>sudo apt-get install android-tools-adb android-tools-fastboot</code> on the command line.</p>
+
+<p><strong>Note</strong>: If you are on Mac OS you can install ADB and Fastboot simply by using Homebrew on the command line. See <a href="//developer.mozilla.org/en-US/Firefox_OS/Debugging/Installing_ADB">Installing and using ADB</a>.</p>
+</div>
+
+<p>ADB and Fastboot are available in the <a class="external external-icon" href="http://developer.android.com/sdk/index.html" title="Android Developer Tookit">Android Developer Toolkit</a>:</p>
+
+<ol>
+ <li>Go to the above link.</li>
+ <li>Press the <em>Download Eclipse ADT</em> button.</li>
+ <li>Agree to the license conditions.</li>
+ <li>Choose between the 32-bit and 64-bit version (32-bit will do if you are not sure).</li>
+ <li>Click the final <em>Download Eclipse ADT with the Android SDK...</em> button.</li>
+ <li>Once the download is complete, unzip the zip file's contents onto your computer's desktop.</li>
+ <li>The folder name is a bit complicated; rename it to just <em>adt.</em></li>
+</ol>
+
+<p>ADB is a tool that you run from the command line. If you open your terminal/command prompt, go to adt/sdk/platform-tools and run the <code>adb</code> command, you should see a load of information thrown back at you about what you can do with ADB. Running <code>adb devices</code> should return the line <code>List of devices attached</code>, and nothing else, because you haven't got any devices attached yet.</p>
+
+<p>But at this point, you need to set the PATH variable to point to the ADB tool, so you can run it from anywhere, not just when you are in the exact directory that ADB is in.</p>
+
+<p>To do this on Windows 8 (Windows 7 will be very similar, but with slightly different menu options):</p>
+
+<ul>
+ <li>Right click on the Windows button in the bottom left and select <em>Control Panel</em> &gt; <em>System and Security</em> &gt; <em>System</em> &gt; <em>Advanced System settings</em> &gt; <em>Environment Variables</em>.</li>
+ <li>In the <em>System variables</em> list, find the one called <em>Path</em>, select it, then click <em>Edit...</em></li>
+ <li>In the <em>Variable value</em> text field of the resulting dialog box, make sure you are at the end of the big string of characters in the box, then type a semi colon (;), followed by the location of the adb tool on your system, which should be <em>C:\Users\[YOUR USER NAME]\Desktop\adt\sdk\platform-tools</em>.<br>
+  <br>
+  So if your user name is jamessmith, you would enter ;<em>C:\Users\jamessmith\Desktop\adt\sdk\platform-tools</em>.</li>
+ <li>Press <em>OK</em> on all the dialog boxes you opened up in this section.</li>
+ <li>Close your command prompt, open a new one, and test it by typing <code>adb devices</code>. If it comes up with <code>List of devices attached</code>, you are successful!</li>
+</ul>
+
+<div class="note">
+<p>Note: To open command prompt, Right click on the Windows button in the bottom left and select Command Line</p>
+</div>
+
+<p>On Mac/Linux:</p>
+
+<ul>
+ <li>In the Finder app, go to your home folder (the one with the house icon.)</li>
+ <li>If you can't already see hidden files (for example, system files with dots (.) at the beginning), go to Terminal and enter the command <code>defaults write com.apple.finder AppleShowAllFiles YES</code>, then restart Finder.</li>
+ <li>Open your <code>.bash_profile</code> or <code>.bashrc</code> file in a plain text editor like Text Wrangler or Sublime Text (it needs to be a plain text editor.)</li>
+ <li>Inside the file, add a new line <code>PATH=/Users/<em>[YOUR USER NAME]</em>/Desktop/adt/sdk/platform-tools:$PATH</code></li>
+ <li>Save and close the file.</li>
+ <li>Restart your terminal, and test it by typing <code>adb devices</code>. If it comes up with <code>List of devices attached</code>, you are successful!</li>
+</ul>
+
+<h3 id="Extra_steps_for_Linux_and_Mac">Extra steps for Linux and Mac</h3>
+
+<p>No additional steps should be required if you are using a Linux or Mac system, although depending on your Linux distro, you will likely need to <a href="/en-US/Firefox_OS/Firefox_OS_build_prerequisites#For_Linux.3A_configure_the_udev_rule_for_your_phone">add a udev rule</a> for your phone.</p>
+
+<p>To discover the vendor ID of your device, attach your phone via USB and use the command <code>lsusb</code> to view the devices deteced on the USB subsystem. Find your phone in the list, and note the initial four digits immediately following "ID". A common ID for the Flame is <code>05c6</code>, so a udev rule in this case would be:</p>
+
+<pre>SUBSYSTEM=="usb", ATTRS{idVendor}=="05c6", MODE="0666"
+</pre>
+
+<p>If your device lists a different number, use that instead. For instance:</p>
+
+<pre>SUBSYSTEM=="usb", ATTRS{idVendor}=="18d1", MODE="0666"
+</pre>
+
+<p>Make sure to run <code>udevadm control --reload-rules</code> (could be automatic depending on your setup), then unplug and replug and your device before continuing.</p>
+
+<h3 id="Extra_steps_for_Windows">Extra steps for Windows</h3>
+
+<p>To access the Flame device with the <a href="/en-US/Firefox_OS/Debugging/Installing_ADB">ADB</a> and Mozilla dev tools like <a href="/en-US/Firefox_OS/Using_the_App_Manager">App Manager</a>/<a href="/en-US/docs/Tools/WebIDE">WebIDE</a>, a USB driver is required. Follow the steps outlined in the below sections to install it.</p>
+
+<h4 id="Downloading_the_driver">Downloading the driver</h4>
+
+<p><a href="http://cds.w5v8t3u9.hwcdn.net/Alcatel_USB_Driver_Q_4.0.0_2013_11_11_noinstall.zip">Download the Windows driver from this location</a>. Once downloaded, extract the contents of the ZIP file to a suitable place on your hard drive.</p>
+
+<div class="note">
+<p><strong>Note</strong>: The Android Debug Bridge (<a href="/en-US/Firefox_OS/Debugging/Installing_ADB">ADB</a>) must be installed first: see instructions above if you've not already done this.</p>
+</div>
+
+<h4 id="Installing_the_USB_Driver">Installing the USB Driver</h4>
+
+<p>At this point, connect your Flame device to your computer using a USB cable.</p>
+
+<p>To install the driver, open the <code>Alcatel_USB_Driver_Q_4.0.0_2013_11_11_noinstall</code> directory within the extracted ZIP file and double click on the <code>DriverInstaller.exe</code> executable. You may receive a warning at this point that the executable is from an unknown publisher. If so, select the <em>Yes</em> button and the executable will be launched.</p>
+
+<p><img alt="Simple dialog box showing a picture of a phone along with install and uninstall buttons." src="https://mdn.mozillademos.org/files/8079/driver-install.png" style="display: block; height: 523px; margin: 0px auto; width: 358px;"></p>
+
+<p>Click on the <em>Install</em> button to install the driver.</p>
+
+<p>After the driver installs, you can check that it is working by opening a command line window and typing <code>adb devices</code>. This should list the connected device with an output something like:</p>
+
+<pre>List of devices attached
+3561d02a          device</pre>
+
+<p>If your device is not showing up here, check in the Windows Device Manager. Your Flame may be showing up as "ACER ADB Interface". You can confirm this by unplugging the device and seeing if it disappears from the device manager. Uninstall the driver software by right-clicking on "ACER ADB Interface" and clicking uninstall.  Be sure to check the box in the dialog to delete the driver software.  Now re-run the installer above. It is advisable to set the screen timeout on your Flame to something high (<em>Settings</em> &gt; <em>Display</em> &gt; <em>Screen timeout</em>) as Windows sometimes appears to reinstall the default drivers when the screen turns off.</p>
+
+<h2 id="Updating_your_Flame's_software">Updating your Flame's software</h2>
+
+<p>We will have two main "channels" of Firefox OS software version releases for the Flame phone:</p>
+
+<ul>
+ <li>The first channel is our release channel. Flames ship with this channel and will receive over-the-air updates for future major versions, that is, Flames will update from 1.3 to 2.0 to 2.1, etc.</li>
+ <li>The second channel is our nightly channel. Flames can be flashed to this channel, and after the initial flashing will get over the air updates on a daily or nearly daily basis.</li>
+</ul>
+
+<p><a name="Base Image">You can get recovery files and tools at the following storage location:</a></p>
+
+<ul>
+ <li><a href="http://cds.w5v8t3u9.hwcdn.net/v188.zip">Base image v188.zip</a>: The latest archive containing the Flame's base image of Firefox OS 2.0.</li>
+ <li><a href="http://cds.w5v8t3u9.hwcdn.net/Flame_2.0_v180_1.zip">Base image v180.zip</a>: An older archive also containing the Flame's base image of Firefox OS 2.0.</li>
+ <li><a href="http://cds.w5v8t3u9.hwcdn.net/v123.zip">Base image v123.zip</a>: A discontinued image based on Android Jellybean; you shouldn't use this anymore.</li>
+</ul>
+
+<div class="note">
+<p><strong>Note</strong>: Firefox OS images v180 and above are based on Android KK (Kitkat, 4.4); JB (Jellybean, 4.1–4.3) builds have now been discontinued and are no longer supported, so don't use anything older than v180.</p>
+</div>
+
+<div class="note">
+<p><strong>Note</strong>: You can find out what base image your device is running using the following command: <code>adb shell getprop ro.bootloader</code></p>
+</div>
+
+<div class="warning">
+<p><strong>Important</strong>: When running a shallow or full flash, your phone data will be overwritten: you should therefore back up your data before updating! See the {{anch("Backing up and restoring your Flame data")}} section for more details.</p>
+</div>
+
+<p>To install the base image on your device:</p>
+
+<ol>
+ <li>Make sure remote debugging is enabled on your Flame, using the <em>Remote debugging/Debugging via USB</em> option in the device's <a href="/en-US/Firefox_OS/Debugging/Developer_settings">Developer settings</a> (the option is different, depending on whether you have Firefox 1.3 and under, or Firefox 1.4+ installed).</li>
+ <li>Connect your Flame to your computer via a USB cable if it isn't already. Verify that the computer is connected to the device by running the <code>adb devices</code> command in a terminal.</li>
+ <li>Download the <code>.zip</code> file referenced above. Unzip it onto your Desktop.</li>
+ <li>Go into the directory you extracted the software into and run it:
+  <ul>
+   <li>On Windows, enter the directory in your command prompt, then run the <code>flash.bat</code> script using <code>flash.bat</code> (or double click the file in explorer.)<br>
+    <strong>Note</strong>: If <code>flash.bat </code>is missing, simply rename the <code>flash.sh</code> file to <code>flash.bat</code>, then run that. Make sure you have <code>adb</code> and <code>fastboot</code> installed and available on <code>PATH</code>.</li>
+   <li>On Linux / OSX, enter the directory in your terminal, then run the <code>flash.sh</code> script using <code>./flash.sh</code> (previous instructions encouraged you to use sudo. Don't. It is <strong>really dangerous</strong> to use sudo with things you download from the Internet. If the flash script fails to see your device, please double-check that your <a href="/en-US/Firefox_OS/Firefox_OS_build_prerequisites#For_Linux.3A_configure_the_udev_rule_for_your_phone">udev rules</a> are correct). If you do not see a <code>flash.sh</code> file, simply rename <code>flash.bat</code> to <code>flash.sh</code> first and then use the above command.</li>
+  </ul>
+ </li>
+</ol>
+
+<div class="note">
+<p><strong>Note</strong>: You are also welcome to build your own builds to install on the Flame: see <a href="/en-US/Firefox_OS/Building_and_installing_Firefox_OS">Building and installing Firefox OS</a>.</p>
+</div>
+
+<h4 id="Font_fix">Font fix</h4>
+
+<p>After updating Gecko and Gaia to nightly with the v180 base image, there will be a mismatch between the fonts that Gecko and Gaia expects and what the base image provides. To fix this, download our <a href="https://people.mozilla.org/~mwu/fira-font-update.zip">font update package</a>, extract it, navigate into the directory created by extracting, and run the supplied <code>flash.sh</code> script.</p>
+
+<div class="note">
+<p><strong>Note</strong>: Another option is to use the <a href="https://github.com/Mozilla-TWQA/B2G-flash-tool/blob/master/update_system_fonts.sh"><code>update_system_fonts.sh</code></a> script, which will download and flash the system fonts automatically.</p>
+</div>
+
+<h3 id="Updating_your_Flame_to_a_nightly_build">Updating your Flame to a nightly build</h3>
+
+<div class="note">
+<p><strong>Note</strong>: For this current build, Nightly development builds of Firefox OS do not support A-GPS, which may lead to slow performance of GPS functionality. We plan to resolve this in an updated future Nightly channel.</p>
+</div>
+
+<div class="warning">
+<p><strong>Important</strong>: When running a shallow or full flash, your phone data will be overwritten: you should therefore back up your data before updating! See the {{anch("Backing up and restoring your Flame data")}} section for more details.</p>
+</div>
+
+<ol>
+ <li>Before updating your phone to a Nightly build you should flash the latest base image to make sure the underlying systems are up to date. Download a base image and use it to update your device's software, as explained above.</li>
+ <li>Because the above step installs a fresh operating system on your device, you'll need to enable remote debugging on your Flame again, using the <em>Remote debugging </em>option in the device's <a href="/en-US/Firefox_OS/Debugging/Developer_settings">Developer settings</a>.</li>
+ <li>Next, choose a build to install (found on <a href="http://ftp.mozilla.org/pub/mozilla.org/b2g/nightly/">http://ftp.mozilla.org/pub/mozilla.org/b2g/nightly/</a>.) You'll want one of the following:
+  <ul style="margin-left: 40px;">
+   <li>Production builds (including locales)
+    <ul>
+     <li><a href="https://ftp.mozilla.org/pub/mozilla.org/b2g/nightly/latest-mozilla-central-flame-kk/">Latest master builds</a> (currently 2.2)</li>
+     <li><a href="https://ftp.mozilla.org/pub/mozilla.org/b2g/nightly/latest-mozilla-b2g34_v2_1-flame-kk/">Latest aurora builds</a> (currently 2.1)</li>
+     <li><a href="https://ftp.mozilla.org/pub/mozilla.org/b2g/nightly/latest-mozilla-b2g32_v2_0-flame-kk/">Latest release builds</a> (currently 2.0)</li>
+    </ul>
+   </li>
+   <li>Engineering builds (with test apps and only pseudo-locales)
+    <ul>
+     <li><a href="https://ftp.mozilla.org/pub/mozilla.org/b2g/nightly/latest-mozilla-central-flame-kk-eng/">Latest master builds</a> (currently 2.2)</li>
+     <li><a href="https://ftp.mozilla.org/pub/mozilla.org/b2g/nightly/latest-mozilla-b2g34_v2_1-flame-kk-eng/">Latest aurora builds</a> (currently 2.1)</li>
+     <li><a href="https://ftp.mozilla.org/pub/mozilla.org/b2g/nightly/latest-mozilla-b2g32_v2_0-flame-kk-eng/">Latest release builds</a> (currently 2.0)</li>
+    </ul>
+   </li>
+  </ul>
+ </li>
+ <li>Pick a version and download both the <code>b2g-XX.XX.en-US.android-arm.tar.gz</code> and <code>gaia.zip</code> files. Save them inside a directory on your Desktop called something like <code>fxos</code>.</li>
+ <li>Download the <a href="https://github.com/Mozilla-TWQA/B2G-flash-tool/blob/master/shallow_flash.sh">shallow flash script</a> and save it in  the same directory as the above two files: follow the link, press the <em>Raw</em> button, then use your browser's save functionality to save the page directly as <code>shallow_flash.sh</code>.</li>
+ <li><strong>For Windows users:</strong> Also download the <a href="https://raw.githubusercontent.com/Mozilla-TWQA/B2G-flash-tool/master/shallow_flash.bat">shallow_flash.bat</a> windows script and install <a href="https://cygwin.com">Cygwin</a> which provides a Linux-like command environment on Windows. You will need to install the default Cygwin <em>base</em> category plus the <em>unzip</em> package but shallow_flash.bat will do this for you if you download and copy the Cygwin setup*.exe to the same folder as the script.</li>
+ <li>
+  <p>In your Terminal, <code>cd</code> into the directory you saved the files in and Flash the builds to your phone using the following:</p>
+
+  <p><strong>Linux</strong>:</p>
+
+  <pre class="brush: bash">./shallow_flash.sh --gaia=gaia.zip --gecko=b2g-XX.XX.en-US.android-arm.tar.gz
+</pre>
+
+  <p><strong>Mac</strong>:</p>
+
+  <pre class="brush: bash">./shallow_flash.sh --gaia gaia.zip --gecko b2g-XX.XX.en-US.android-arm.tar.gz</pre>
+
+  <p><strong>Windows</strong>:</p>
+
+  <p>Double click <code>shallow_flash.bat</code> (with cogs icon) or run it from a command shell. It will flash <code>gaia.zip</code> and a single <code>b2g-XX.XX.en-US.android-arm.tar.gz</code> file.</p>
+ </li>
+</ol>
+
+<div class="note">
+<p><strong>Note</strong>: If you get a "permission denied" error when running the above commands, your shell script probably doesn't have the right permissions. Running <code>chmod +x shallow_flash.sh</code> on it should solve this problem.</p>
+</div>
+
+<div class="note">
+<p><strong>Note</strong>: A "shallow flash" updates <a href="/en-US/docs/Mozilla/Gecko">Gecko</a> and <a href="/en-US/Firefox_OS/Platform/Gaia">Gaia</a> plus data directories, as opposed to a full flash, which updates Gecko/Gaia, but also the underlying <a href="/en-US/Firefox_OS/Platform/Gonk">Gonk</a> layer and associated binaries particular to that device type. This is why it is a good idea to update to the official base image first, as suggested above, then shallow flash over the top of that, once you've got the Gonk/binary layer right.</p>
+</div>
+
+<p>Once the install procedure finishes the phone should reboot into the updated build and display the first time user workflow.</p>
+
+<h4 id="Switch_to_nightly_update_channel">Switch to nightly update channel</h4>
+
+<ol>
+ <li>Make sure remote debugging is enabled on your Flame, using the <em>Remote debugging/Debugging via USB</em> option in the device's <a href="/en-US/Firefox_OS/Debugging/Developer_settings">Developer settings</a></li>
+ <li>Download the <a href="https://github.com/Mozilla-TWQA/B2G-flash-tool/blob/master/change_channel.sh">change channel</a> script: follow the link, press the <em>Raw</em> button, then use your browser's save functionality to save the page directly as <code>change_channel.sh</code>.</li>
+ <li>In your Terminal, <code>cd</code> into the directory you saved the script in and change the update channel on your phone using the following command:<br>
+
+  <pre class="brush: bash">./change_channel.sh -v nightly</pre>
+ </li>
+ <li>Once the phone reboots, check for updates by going into <em>Settings &gt; Device information &gt; Check now</em></li>
+</ol>
+
+<p>You should now get nightly OTA updates to your phone.</p>
+
+<div class="note">
+<p><strong>Note:</strong> You can choose between several different update channels. Run "<code>./change_channel.sh -h</code>" to see the other channel options.</p>
+</div>
+
+<h3 id="Fastboot_mode">Fastboot mode</h3>
+
+<p>If flashing a new build to your phone fails to work, your phone may become unresponsive, leading to the phone rebooting in recovery mode. The recovery mode provides few options (<em>Reboot</em>, <em>Update from adb</em>, <em>Wipe data</em>, <em>Wipe cache</em>, and <em>Update from sdcard</em>). Unfortunately, selecting <em>Update from adb</em> triggers a sideload mode in which you cannot use the other adb commands. The <code>adb sideload</code> command would work but the various flash scripts rely on other adb commands.</p>
+
+<p>You can force fastboot mode as follows:</p>
+
+<ol>
+ <li>Power off the phone (which may involve removing the battery in extreme cases...)</li>
+ <li>Plug in the USB cable.</li>
+ <li>Power the phone up again by pressing the Volume Down and Power buttons together.</li>
+</ol>
+
+<p>The phone should now display the text "FASTBOOT": it is in fastboot mode and is waiting for a USB connection. At this point, a USB-connected, computer with adb installed should see the phone listed when the <code>fastboot devices</code> command is run. Note that regular adb would not see the device — only fastboot sees it. In this mode, you can use the flash script to install the last <a href="#Base Image">base image</a> as explained above. As the script does use both adb and fastboot commands, you may see some initial error and warnings from adb, but the device should be flashed properly at the end of the procedure.</p>
+
+<h3 id="Emergency_download_mode">Emergency download mode</h3>
+
+<p>If flashing a new build to your phone fails to work, your phone becomes unresponsive, and the phone cannot enter fastboot mode, you can use emergency mode for recovery. A USB cable and the <a href="http://cds.w5v8t3u9.hwcdn.net/Flame%20Rescue%20Tool.zip">Emergency Download Tool</a> are required to enter emergency download mode. Install this tool and follow the instructions.</p>
+
+<div class="note">
+<p><strong>Note</strong>: The tools provided are Windows only</p>
+</div>
+
+<h3 id="Recovery_mode">Recovery mode</h3>
+
+<p>You can enter recovery mode to clear your phone data or manually update the firmware. There are two ways to enter this mode:</p>
+
+<ul>
+ <li>If <a href="/en-US/Firefox_OS/Debugging/Installing_ADB">ADB</a> tools are available, make sure Remote debugging is turned on in the phone's <a href="/en-US/Firefox_OS/Debugging/Developer_settings#Remote_debugging">Developer settings</a>, connect your phone to your computer via USB and enter <code>adb reboot recovery</code> on the command line.</li>
+ <li>If your phone is powered off, press the Volume Up + Power buttons together.</li>
+</ul>
+
+<p>When in recovery mode, press the Volume up/down keys to move the selection highlight, and the Power key to select. Make sure you have your phone data (Contacts, SMS, etc.) backed up before clearing data, and your upgrade packages downloaded before updating.</p>
+
+<h2 id="Backing_up_and_restoring_your_Flame_data">Backing up and restoring your Flame data</h2>
+
+<p>When using a Flame, you won't want to lose your phone's contacts and other data while upgrading to a new build (as explained earlier in this article). To backup and restore data you can use our <a href="https://github.com/Mozilla-TWQA/B2G-flash-tool/blob/master/backup_restore_profile.sh">Backup and restore profile</a> tool.</p>
+
+<ol>
+ <li>To use this, first download it from Github at the above link. The easiest way to save it is to press the <em>Raw</em> button, then save the raw code as a <code>.sh</code> file using your browser's <em>Save As...</em> option.</li>
+ <li>Next, make sure you'll have the necessary permissions to execute this file: <code>cd</code> into the directory where you saved the file, and run the following command:
+  <pre class="brush: bash">chmod +x backup_restore_profile.sh</pre>
+ </li>
+</ol>
+
+<div class="note">
+<p><strong>Note</strong>: When using this tool, you'll also need to make sure that your phone is connected via USB to your computer, and that ADB (see {{anch("Important steps to follow first")}} above) and Debugging via USB (in your device's <a href="/en-US/Firefox_OS/Debugging/Developer_settings">Developer settings</a>) are enabled.</p>
+</div>
+
+<div class="note">
+<p><strong>Note</strong>: These instructions should work on Mac and Linux out of the box. To use the backup and restore feature on Windows you'll have to install <a href="https://www.cygwin.com/">Cygwin</a> and run it from inside that.</p>
+</div>
+
+<h3 id="Backing_up_data_from_your_phone">Backing up data from your phone</h3>
+
+<p>In the directory where you saved the <code>backup_restore_profile.sh</code> file, run the following:</p>
+
+<pre class="brush: bash">./backup_restore_profile.sh -b</pre>
+
+<p>This should save your device profile to a directory called <code>mozilla-profile</code>, in the same directory as the script is located.</p>
+
+<h3 id="Restoring_data_to_your_phone">Restoring data to your phone</h3>
+
+<p>In the directory where your <code>mozilla-profile</code> directory is located (see above section), run the following:</p>
+
+<pre class="brush: bash">./backup_restore_profile.sh -r</pre>
+
+<h3 id="Other_options">Other options</h3>
+
+<p>The full list of options available for the <code>backup_restore_profile.sh</code> script is as follows:</p>
+
+<ul>
+ <li><code>-b</code> or <code>--backup</code> — Backup user profile.</li>
+ <li><code>-r</code> or <code>--restore</code> — Restore user profile.</li>
+ <li><code>--sdcard</code> — Also backup/restore the SD card.</li>
+ <li><code>--no-reboot</code> — Do not reboot B2G after backup/restore.</li>
+ <li><code>-p</code> or <code>--profile-dir</code> — Specify the profile folder. The default is <code>./mozilla-profile</code>.</li>
+ <li><code>-h</code> or <code>--help</code> — Display help.</li>
+</ul>
+
+<h2 id="Pushing_apps_to_your_Flame">Pushing apps to your Flame</h2>
+
+<p>The <a href="/en-US/Firefox_OS/Using_the_App_Manager">App Manager</a> and <a href="/en-US/docs/Tools/WebIDE">WebIDE</a> tools make it easy to push apps to your phone, for testing, etc.</p>
+
+<h2 id="RAM_adjustment">RAM adjustment</h2>
+
+<p>You can adjust the available RAM capacity to see how apps perform on Firefox OS phones with lower memory footprints.</p>
+
+<p>This is accomplished by entering fastboot mode (install fastboot first, which is available on the same SDK page as <a href="/en-US/Firefox_OS/Debugging/Installing_ADB">ADB</a>) and typing:</p>
+
+<pre class="brush: bash">adb reboot bootloader
+fastboot oem mem [0|256-1024]</pre>
+
+<p>“0” is the memory automatically detected and “256-1024” is the number of megabytes. For example, if you want to adjust device RAM capacity to 512M, enter <code>fastboot oem mem 512</code>.</p>
+
+<p>You'll need to then reboot your device for the settings to take effect. This can be done using:</p>
+
+<pre class="brush: bash">fastboot reboot</pre>
+
+<p>The current memory size can be returned by entering fastboot mode and typing:</p>
+
+<pre class="brush: bash">fastboot getvar mem
+</pre>
+
+<h2 id="Network_and_Device_specs">Network and Device specs</h2>
+
+<p><strong>Network</strong>:</p>
+
+<ul>
+ <li>802.11b/g/n wireless internet</li>
+ <li>GSM 850/900/1800/1900MHz</li>
+ <li>UMTS 850/900/1900/2100MHz</li>
+</ul>
+
+<p><strong>Hardware</strong>: You can find more of the hardware features listed on our <a href="/en-US/Firefox_OS/Developer_phone_guide/Phone_specs">Phone and device specs page</a>.</p>
+
+<p>Additional features include:</p>
+
+<ul>
+ <li>NFC</li>
+ <li>Bluetooth 3.0</li>
+ <li>Accelerometer</li>
+ <li>FM radio</li>
+ <li>Proximity Sensor</li>
+ <li>GPS W / A-GPS support</li>
+ <li>Ambient Light Sensor</li>
+</ul>
+
+<h2 id="See_also">See also</h2>
+
+<ul>
+ <li><a href="https://hacks.mozilla.org/2014/08/videos-getting-started-with-your-flame-device/">Getting started with your Flame</a>: How-to videos by Chris Heilmann</li>
+ <li><a href="http://mozilla.github.io/flame-on/">Flame On</a>: a great starting page for all Flame owners created at Mozilla Festival 2014</li>
+</ul>
diff --git a/files/tr/archive/b2g_os/phone_guide/index.html b/files/tr/archive/b2g_os/phone_guide/index.html
new file mode 100644
index 0000000000..c6d2c31ff5
--- /dev/null
+++ b/files/tr/archive/b2g_os/phone_guide/index.html
@@ -0,0 +1,57 @@
+---
+title: Firefox OS developer phone guide
+slug: Archive/B2G_OS/Phone_guide
+tags:
+  - B2G
+  - Firefox OS
+  - Landing
+  - NeedsTranslation
+  - Phones
+  - TopicStub
+translation_of: Archive/B2G_OS/Phone_guide
+---
+<div class="summary">
+ <p><span class="seoSummary">This section contains developer information relevant to specific phones that run Firefox OS.</span> We have general information available on <a href="/en-US/docs/Mozilla/Firefox_OS/Building_and_installing_Firefox_OS" title="Building and installing Firefox OS">Building and installing Firefox OS</a> and <a href="/en-US/docs/Mozilla/Firefox_OS/Hacking_Firefox_OS" title="/en-US/docs/Mozilla/Firefox_OS/Hacking_Firefox_OS">Hacking Firefox OS</a>, so please go there for information about building and installing the platform from scratch. Developers with specific phones in their possession may however find the following articles useful.</p>
+</div>
+<h2 id="Specific_device_information">Specific device information</h2>
+<dl>
+ <dt>
+  <a href="/en-US/docs/Mozilla/Firefox_OS/Phones">Firefox OS phone data</a></dt>
+ <dd>
+  In this article we list the various available Firefox OS phones along with information such as their code names, availability, and specific hardware features.</dd>
+ <dt>
+  <a href="/en-US/Firefox_OS/Developer_phone_guide/Flame">Flame</a></dt>
+ <dd>
+  Information on Mozilla's high-end Firefox OS reference phone, codenamed the Flame, and produced in partnership with T<sup>2</sup>Mobile.</dd>
+ <dt>
+  <a href="/en-US/Firefox_OS/Developer_phone_guide/Geeksphone">Geeksphone</a></dt>
+ <dd>
+  In this article we cover some basic tips on how to keep your Geeksphone up-to-date and how to tweak the system Gaia applications.</dd>
+ <dt>
+  <a href="/en-US/docs/Mozilla/Firefox_OS/Developer_phone_guide/ZTE_OPEN">ZTE OPEN</a></dt>
+ <dd>
+  This article contains information on the ZTE OPEN Firefox OS device.</dd>
+ <dt>
+  <a href="/en-US/Firefox_OS/Developer_phone_guide/ZTE_OPEN_C">ZTE OPEN C</a></dt>
+ <dd>
+  The ZTE Open C is an updated ZTE-produced Firefox OS device, with higher end hardware and newer software.</dd>
+ <dt>
+  <a href="/en-US/Firefox_OS/Developer_phone_guide/Symphony_GoFox_F15">Symphony GoFox F15</a></dt>
+ <dd>
+  The Symphony GoFox F15 is the first Firefox OS Device to come with 3G video calling capability, launched in Bangladesh.</dd>
+</dl>
+<h2 id="General_Firefox_OS_information">General Firefox OS information</h2>
+<dl>
+ <dt>
+  <a href="/en-US/Firefox_OS/Developer_phone_guide/Firefox_OS_device_features">General device features</a></dt>
+ <dd>
+  This page lists typical Firefox OS hardware features and minimum hardware requirements.</dd>
+ <dt>
+  <a href="/en-US/docs/Mozilla/Firefox_OS/Troubleshooting">Troubleshooting</a></dt>
+ <dd>
+  This article provides tips for resolving common problems you may have while using Firefox OS.</dd>
+ <dt>
+  <a href="/en-US/Firefox_OS/Developer_phone_guide/Best_practices_open_reference_devices">Best practices for open reference devices</a></dt>
+ <dd>
+  A set of best practices that we believe should come highly recommended for any widely available open reference devices. All of the recent Firefox OS reference devices have followed these practices.</dd>
+</dl>