Full Android instructions inside

[Lowers]

Android Secret Dial Codes

These codes are listed below:

*#*#4636#*#* - Phone Information (allows you to change the SMS service centre number and more)

*2767*3855# - HARD RESET (will fully wipe and restore firmware. USE WITH CAUTION

*#*#34971539#*#* Shows completes information about the camera

*#*#7594#*#* Changing the power button behavior-Enables direct poweroff once the code enabled

*#*#273283*255*663282*#*#* For a quick backup to all your media files

*#*#197328640#*#* Enabling test mode for service activity

*#*#232339#*#* OR *#*#526#*#* OR *#*#528#*#* Wireless Lan Tests

*#*#232338#*#* Displays Wi-Fi Mac-address

*#*#1472365#*#* For a quick GPS test

*#*#1575#*#* A Different type GPS test

*#*#0283#*#* Packet Loopback test

*#*#0*#*#* LCD display test

*#*#0673#*#* OR *#*#0289#*#* Audio test

*#*#0842#*#* Vibration and Backlight test

*#*#2663#*#* Displays touch-screen version

*#*#2664#*#* Touch-Screen test

*#*#0588#*#* Proximity sensor test

*#*#3264#*#* Ram version

*#*#232331#*#* Bluetooth test

*#*#7262626#*#* Field test

*#*#232337#*#* Displays bluetooth device address

*#*#8255#*#* For Google Talk service monitoring

*#*#4986*2650468#*#* PDA, Phone, Hardware, RF Call Date firmware info

*#*#1234#*#* PDA and Phone firmware info

*#*#1111#*#* FTA Software version

*#*#2222#*#* FTA Hardware verion

*#*#44336#*#* Displays Build time and change list number

*#06# Displays IMEI number

*#*#8351#*#* Enables voice dialing logging mode

*#*#8350#*#* Disables voice dialing logging mode

**05***# Execute from Emergency dial screen to unlock PUK code

 

[Lowers]

answer: Full Android instructions inside

*#*#7780#*#* Wipe data/factory reset

 

[Lowers]

answer: Full Android instructions inside

The Android Dictionary

ADB

ADB (Android Debug Bridge) is a PC command-line tool included with the Google Android SDK. ADB provides an interface for managing and debugging a USB connected Android device. Common ADB tasks include: *Collecting a log via logcat* Installing APK packages* Pushing or pulling files* Accessing the device shell.

For additional details about ADB please see the ADB guide.

APK

An APK is an Android application package (Android Package). It is commonly used to store an app, or program run on the device. These files are essentially zip files, in that they contain other files which make up the program. They can be obtained through various methods, such as installing an app through the market, downloading from a website, or creating yourself in Java. If you have an apk file on your computer, and wish to install it on your phone, you can run the command 'adb install apkname.apk' to copy the file over USB to your phone.

The APK files reside on the phone in the directory /data/app/filename.apk. This directory is not normally accessible unless a #root|rooted ROM is used on the phone, in order to protect paid-for applications. On a rooted ROM, it is possible to copy applications manually into this folder using the command 'adb push' or similar. Once a file is in the /data/app directory, it is installed on the phone. There is not normally an installation process for apps on Android.

It is also possible to install an app to the system partition of a rooted phone. This has the added benefit that the application cannot be uninstalled from the device, making it useful for security/anti-theft applications such as WaveSecure and MobileDefense. These [[#system]] applications are stored in /system/app. The applications in this folder are normally part of the Android operating system, and should not be modified or deleted unless you either put the file there yourself, or know what you are doing.

APK files can be uninstalled using the market application (if the application was installed from the market), the 'adb uninstall apkname.apk' command, the Settings | Applications | Manage Applications menu, or by manually removing the files from the /data/app directory as a last resort. Normally, the preferred method is through the market or applications menu.

Bart

Bart is used from Recovery to backup your phone or to restore a backup.This basically creates an exact copy of your phone (Sdcard + Sd-Ext excluded, unless it says it will backup SD-Ext), which later can be restored with no losses in data.

Boot

In contrast to other linux-based operating systems, Android has a boot partition (containing the contents of a boot.img file), as opposed to a direct booting system. This partition contains a read-only 'ramdisk', and a couple of other files. The ramdisk contains files critical to booting, such as init.rc and default.prop. This 'partition' actually sets up the directory structure of the device, having empty folders for /data, /dev, /proc, /sbin, /sys and /system.

Bootloader

The bootloader, or HBOOT, is firmware on the phone which runs on every startup.

Since the bootloader controls access to Fastboot, it can be desirable to change the version of the bootloader on a phone. The current version of the bootloader can be viewed by entering bootloader mode. To do so, turn on the phone with the back button held down. Release the back button after about 1 second. The version information will be displayed at the top of the screen next to the word HBOOT, and will appear in the form 'V1.76.0004' or similar.

From within the bootloader, Fastboot can be used to execute an img file stored on your PC or flash an img file to the device.

If your device has HBOOT version 1.73.007, it is no longer possible to use Fastboot, so it is often desirable to downgrade the HBOOT using the Goldcard method in order to get the 1.73.004 version, which is Security-Off, allowing Fastboot.

CID

The Carrier ID is a number embedded in your Phone's SPL that identifies what if your phone is a network branded Hero. For example, T-Mobile UK phones have a different CID to generic HTC phones. The CID prevents you from [[#Flash|flashing]] an 'incorrect' [[#RUU]] to your phone. Note that the RUUs will all function on any of the phones, but the CID locking prevents you from 'debranding' your phone by installing a generic [[#RUU]]. Additionally, the CID-related software also prevents you from installing an older RUU than what you are currently running.

It is possible to bypass the CID check on an [[#RUU]] using a [[#Goldcard]]. This pretends your phone has the 'Super-CID', which allows any branding of ROM to be installed, and allows you to downgrade the software on your phone.

 

[Lowers]

answer: Full Android instructions inside

Data

The data partition on the device contains the user-related data, such as installed applications and settings for those apps, as well as your SQLite database containing Android settings and messages. Normally, the directory /data/app is off-limits through the 'adb shell' command, as well as other terminal applications that can run on the device, since this directory contains the apk files for apps. On a rooted phone, using the [[#su]] command will allow full access to this partition. This partition can be flashed using Fastboot or Nandroid.

Ext

Ext is an abbreviation of the extended filesystem, one of the filesystems supported by Android and other Linux based systems. An ext filesystem partition is required for using Apps2SD or Dalvik2sd.

Fastboot

Fastboot is a means to execute or Flash an img file on your device. First, set up your PC for ADB, and ensure that it works correctly. After putting your phone into Bootloader mode, and selecting Fastboot by pressing back (if you let go of the back key early), the device awaits a command via USB.

On your computer, execute the command 'fastboot devices', which should display your device serial number. This confirms you are ready to use Fastboot. To execute (ie. run without changing your system) and img file, type the command 'fastboot boot imagename.img'. This command allows you to run a custom recovery image without flashing it to the device.

If you wish to flash an img file to the device, the command 'fastboot flash IMGTYPE imgtype.img' should be used. Note that IMGTYPE should be replaced by the type of img file you are flashing. For example, to flash a recovery image, the command 'fastboot flash recovery patched_recovery.img' should be used. The following are valid types of image to flash; boot, recovery, system,

Flash

Flashing is the process of writing data to the internal memory on your phone. Normally, you would flash a [[#ROM]] image to the phone, which would give you a different version of system software on your phone. Flashing can also refer to updating/writing to any of the other parts of the phone, such as the SPL, Radio etc.

Flash Memory

Flash memory, also known as NAND memory, is nonvolatile - keeping information even when the device is off. Flash memory in the device is equivalent to the hard drive in a computer. This is where the device's operating system (sometimes called firmware) and applications are stored. Flash memory is slower than RAM, but is (almost always) faster than SD cards.

Flashrec

Flashrec is an application/tool you use to flash the recovery image to your phone. (Found on [Only Registered and Activated Users Can See Links. Click Here To Register...] current firmwares are patched so you can not use flashrec on these, you will receive the error message "Could not run command"Most 1.5 (cupcake) firmwares can still use this, but some has been patched already.The current version is 1.1.3 and was updated 2009-08-16.Note: Do not flash cyanogen's theme templates after you have started the installed recovery image, this will brick your phone!

Goldcard

A goldcard is the name given to a specially modified microSD memory card for your phone that allows you to install software to your phone that is in an RUU file, but not from the same network provider as your phone is from. It does this by bypassing the CID check of the RUU update. Additionally, the goldcard allows you to install an earlier version of system software onto your phone than what is already on it (called downgrading). This can make it easier to root a phone and install a custom ROM on it, if the software installed on it at present cannot easily be rooted.

 

[Lowers]

answer: Full Android instructions inside

HBOOT

See Bootloader.

logcat

Using adb (see ADB), type in "adb logcat >logcat.txt". This will help us when resolving issues and bugs.There is also a tool in the market you can use for this, called aLogcat. It can show different categories (severity of errors ect.) too, adb logcat can not do this.

Market

The market on Android is a place where you can purchase or download applications for your phone in the [[#APK]] format. When you download through the market, the installation process is transparent (as in you don't have to deal with the APK files yourself), and there is the facility to rate apps and post comments which are visible to other users. Frequently, the developers of apps actually take onboard the feedback in the comments (mainly the smaller apps with slightly less feedback to sift through).

When an app is installed from the market, it is copied to '/data/app/apkname.apk', as the act of 'installing'. An app can store its data in the folder '/data/data/apkname'. It is possible to clear the data stored by an application by using the Manage Applications feature in Settings | Applications | Manage Applications.

Nand

See Flash Memory.

Nandroid

Nandroid is used to backup or restore backups from Recovery.You can chose to either do a regular backup (Phone only) or a backup + sd-ext (Phone + Apps2sd ext.)Both will backup your whole system, the second will include apps saved on your sdcard's sd-ext.

Radio

The Radio on a Hero is the part of the phone that deals with mobile connections. It handles talking to the GSM/3G network, Bluetooth, WiFi and GPS. The radio contains software that controls how it operates, and newer versions of radio firmware are made available from time to time in [[#RUU]] updates. These updates are transparent to the user, although users who elect to install custom software can update their radio using an update.zip file made available by members of the modding community.

Flashing the radio is potentially risky, and you should NEVER pull the battery out of a phone that is [[#Flash|flashing]] the radio. If you do so, it is possible your phone will be bricked. Nevertheless, it can give improved battery life, signal strength and data performance, so is often done by users moving to later versions of ROMs.

Care should be taken to only flash the correct type of radio to a phone. NEVER attempt to flash a CDMA phone with a GSM radio or vice-versa. It is likely you will brick the phone if you attempt to do so.

ROM

ROM is literally "read-only memory" but it's usage has changed over time. Today ROM can refer to the non-volatile area of a device's flash memory on which read-only data resides or the packed image to be written to that flash area.

Root

Root is the name of the highest level superuser (su) on Unix-like systems such as Android. The root user, and applications run by the root user, have administrative access to protected files and services which makes it dangerous for normal daily use.

A 'rooted' device one which has been hacked to provide privilege escalation from a standard user to superuser. Rooting a device is usually the first step in installing cooked ROMs.

RUU

An RUU is a ROM Upgrade Utility, which is a Windows executable (exe) file that upgrades the software on your phone. Using the USB connection with the phone, the RUU communicates with the phone's SPL, checking the CID of the device to ensure the user is not installing the ROM on a network branded device (since the networks release their own RRUs with customisations and branding). The RUU is capable of flashing almost everything on the phone, including System, Data, Recovery, HBOOT and Boot. As such, an RUU is a good way to return your phone to the way it came out the box if a warranty repair is needed (be aware that using a new RUU could make it difficult, or even prevent you from rooting the phone in future. It is normally better to upgrade using update.zip files to prevent this, as they do not update the HBOOT to prevent Fastboot in future.

 

[Lowers]

answer: Full Android instructions inside

S-OFF/S-ON

This refers to an unlocked/locked NAND drive. HTC lock the NAND on some phones to prevent writing to the /system. S-OFF can generally be obtained by an exploit, by flashing an engineering SPL, or by using an XTC Clip.

SPL

The Secondary Program Loader is a piece of bootcode that initiates the startup of the phone, displaying the initial splashscreen for the device, and loading the initial files from ROM.

It checks to see if a button combination is pressed on bootup (such as that to enter Recovery Mode or the bootloader ), and loads the relevant system software. If no special instruction is given by holding keys, the bootloader loads the normal system software by initialising the boot process from the boot partition.

Flashing your SPL is risky, as the process failing will probably result in a broken, or bricked phone, since the SPL is executed very early on in the boot process, and any error here will prevent access to the recovery or bootloader features.

If you do flash the SPL though, it unlocks the Carrier-ID CID from the device, essentially allowing any RUU to be installed to the device, and allows flashing alternative or custom bootscreens.

Stock

The term stock is often used to refer to a file or part of the software which is unmodified or untouched by developers. For example, a stock ROM would be one which was produced by HTC and which had not been modified or rooted by someone. The term is often used when comparing performance of different ROMs, as a way to refer to the phone as it came out the box.

su

su (substitute user) is a Linux command which, when run without a username parameter, gives the user full 'root' permissions. By default, this command binary (ie. Linux equivalent of an executable file) is not included on Android systems, but the process of "rooting" a phone copies this file to the '/system/bin/' directory thereby enabling the command. Since root privileges can be abused by malicious applications it's highly recommended to install an app to grant and manage access to su, similar to UAC on Windows. VillainROM includes the app called "Superuser" for this.

System

The /system directory on your device is where the main operational software for the Android OS is stored. It has a number of sub-direcories of which /system/apps (where application apk's are stored) is probably the only one users would have need to access. The /system folder is read-only by default and needs remounted via 'adb' to allow write access.

 

[Lowers]

answer: Full Android instructions inside

Recovery

The recovery partition is a boot-mode for your phone that allows you to wipe your settings from the Data partition of the phone (a hard wipe), or perform an update using an update.zip file on the root of the microSD card. It is common (although not necessary) to flash a patched Recovery image, such as Amon RA's one. This allows you to run Nandroid backup from the device, and flash modifications, such as [[#update.zip]] files to the device, essentially becoming a means to install sotware to the device. Recovery mode is separate from 'normal' mode, and can be entered by holding down home whilst turning the phone on.

update.zip

An update.zip (does not have to actually be called update.zip if you have a patched Recovery image) is a file containing some files which will be copied to the phone's internal memory. Normally, a new system update or ROM is stored in the file, but update.zip files are commonly used to install modifications such as themes or applications that are installed on the System partition to prevent uninstallation.

To flash one of these files, which commonly would contain a custom ROM for your phone, you would boot your phone to a patched recovery image (whether using Fastboot, or the home+power method if you have a patched Recovery image flashed on your phone)

Update.zip files are cryptographically signed, and more information on how to sign your own files can be found online.

WWE

Stands for World Wide English version of the ROM. There can be local versions of ROMs too. For example VR10 is based on the Taiwan version, VR12 on the WWE one. Interestingly, WWE excludes the English (US) locale.

 

[Lowers]

answer: Full Android instructions inside

Fastboot Guide

What is Fastboot?

Fastboot is a command line tool used to directly flash the filesystem in Android devices from a host via USB. It allows flashing of unsigned partition images. It is disabled in most production devices since USB support has been disabled in the bootloader. In order to use Fastboot, you must have an unlocked bootloader or an Engineering SPL

Pre-requisites

- You must have ADB drivers installed for your device. Some devices have fastboot specific drivers too, so Google that for your device.

- Fastboot package, available [Only Registered and Activated Users Can See Links. Click Here To Register...].

Typical Partition Layout


recovery

N/A

A 'backup' kernel, initrd, and OS
for system recovery / maintenance

mtdblock1

Can flash custom recovery.img (Amon_Ra, ClockworkMod, etc).

boot

boot.img

The main kernel and ramdisk

mtdblock2

Can flash custom boot.img

system

system.img

The main OS

mtdblock3

This is the /system partition

cache

cache.img

Temp storage

mtdblock4

Unused.

userdata

data.img

User data and settings

mtdblock5

This is the /data partition

Examples

Manual Nandroid restore

Make a Nandroid backup, and copy the folder off your SD card to your desktop.

cd ~/Desktop/path/to/backup/
fastboot flash userdata data.img
fastboot flash system system.img
fastboot flash boot boot.img
fastboot reboot

Flash Custom Recovery.img

fastboot flash recovery /path/to/.img
fastboot reboot

Flash Custom boot.img

You should make a Nandroid backup first, in case you need to recover your boot.img

fastboot flash boot /path/to/.img
fastboot reboot

Development

If you are developing a kernel, you may find it helpful to delete your boot.img and recovery.img to force booting into fastboot:

fastboot erase boot
fastboot erase recovery

You can then manually boot from your custom kernel and a ramdisk:

fastboot boot

Once you have a working kernel and ramdisk, you can automagically combine them within fastboot:

fastboot flash:raw boot

 

[Lowers]

answer: Full Android instructions inside

What is Root/Rooting?

For the newbies out there, let me start at the beginning. Rooting/getting root/obtaining root priviliges (however you want to put it) is modifying the operating system on your handset to give you FULL CONTROL over it. Those of you coming from the dreaded (and somewhat douchey) iPhone, will be familiar with the term ‘jailbreaking’. Well... jailbreaking is pretty much rooting.

Rooting allows you to break free of the (often needless) limitations placed upon your phone by its manufacturer, or the supplying network provider (carrier). Furthermore, rooting allows the installation of custom ROMs (community made operating systems), custom recovery images (that offer additional functionality such as ROM backups and restores), and many more features.

Whilst I’m on the subject, I’d like to take a moment to dispel a common misconception and clarify one important point:

Rooting does not mean installing a custom ROM

Installing a ROM typically requires root access, but rooting itself is often a simple process, taking only a couple of minutes.

FYA features rooting guides for each and every Android handset on the market.

 

[Lowers]

answer: Full Android instructions inside

How to install and set up the Android SDK

The Android SDK (Software Developer's Kit) is a software suite intended for developing software for Android devices. The SDK, however, is not only useful for developers; it provides an easy way to access your device from a computer, and makes simple tasks such as installing applications that much simpler. In addition, it can also be used for more complex Android firmware development tasks.

To use the Android SDK, you need to install it to your computer. Below, we outline the necessary steps to install the SDK to your Linux, Mac OS-X or Windows PC.

​

Before you begin:

- Ensure you have the Java Development Kit (JDK)

- and that your computer meets the minimum system requirements

​

Download the SDK Starter Package

The Starter Package downloads the basic SDK tools necessary to download the rest of the SDK. Download it HERE.

Download Other Components

Windows: Double-click the SDK Manager.exe file at the root of the SDKdirectory

Mac/Linux: Open a terminal and navigate to the /tools directory in the SDK then execute:

./android

By default, there are two repositories of components for your SDK Repository and Third party Add-ons.

The Android Repository offers these components:

SDK Tools (pre-installed in the Android SDK starter package) - Contains tools for debugging and testing your application and other utility tools. You can access these in the /tools/ directory of your SDK and read more about them in the Tools section of the developer guide.

SDK Platform-tools — Contains tools that are required to develop and debug your application, but which are developed alongside the Android platform in order to support the latest features. These tools are typically updated only when a new platform becomes available. You can access these in the /platform-tools/ directory. Read more about them in the Tools section of the developer guide.

Android platforms — An SDK platform is available for every production Android platform deployable to Android-powered devices. Each platform component includes a fully compliant Android library and system image, sample code, emulator skins, and any version specific tools. For detailed information about each platform, see the overview documents available under the section "Downloadable SDK Components," at left.

USB Driver for Windows (Windows only) — Contains driver files that you can install on your Windows computer, so that you can run and debug your applications on an actual device. You do not need the USB driver unless you plan to debug your application on an actual Android-powered device. If you develop on Mac OS X or Linux, you do not need a special driver to debug your application on an Android-powered device. (See Developing on a Device for more information about developing on a real device.)

Samples — Contains the sample code and apps available for each Android development platform. If you are just getting started with Android development, make sure to download the samples to your SDK.

Documentation — Contains a local copy of the latest multiversion documentation for the Android framework API.

 

[Lowers]

answer: Full Android instructions inside

How to install and set up the Android SDK

The Android SDK (Software Developer's Kit) is a software suite intended for developing software for Android devices. The SDK, however, is not only useful for developers; it provides an easy way to access your device from a computer, and makes simple tasks such as installing applications that much simpler. In addition, it can also be used for more complex Android firmware development tasks.

To use the Android SDK, you need to install it to your computer. Below, we outline the necessary steps to install the SDK to your Linux, Mac OS-X or Windows PC.

​

Before you begin:

- Ensure you have the Java Development Kit (JDK)

- and that your computer meets the minimum system requirements

​

Download the SDK Starter Package

The Starter Package downloads the basic SDK tools necessary to download the rest of the SDK. Download it HERE.

Download Other Components

Windows: Double-click the SDK Manager.exe file at the root of the SDKdirectory

Mac/Linux: Open a terminal and navigate to the /tools directory in the SDK then execute:

./android

By default, there are two repositories of components for your SDK Repository and Third party Add-ons.

The Android Repository offers these components:

SDK Tools (pre-installed in the Android SDK starter package) - Contains tools for debugging and testing your application and other utility tools. You can access these in the /tools/ directory of your SDK and read more about them in the Tools section of the developer guide.

SDK Platform-tools — Contains tools that are required to develop and debug your application, but which are developed alongside the Android platform in order to support the latest features. These tools are typically updated only when a new platform becomes available. You can access these in the /platform-tools/ directory. Read more about them in the Tools section of the developer guide.

Android platforms — An SDK platform is available for every production Android platform deployable to Android-powered devices. Each platform component includes a fully compliant Android library and system image, sample code, emulator skins, and any version specific tools. For detailed information about each platform, see the overview documents available under the section "Downloadable SDK Components," at left.

USB Driver for Windows (Windows only) — Contains driver files that you can install on your Windows computer, so that you can run and debug your applications on an actual device. You do not need the USB driver unless you plan to debug your application on an actual Android-powered device. If you develop on Mac OS X or Linux, you do not need a special driver to debug your application on an Android-powered device. (See Developing on a Device for more information about developing on a real device.)

Samples — Contains the sample code and apps available for each Android development platform. If you are just getting started with Android development, make sure to download the samples to your SDK.

Documentation — Contains a local copy of the latest multiversion documentation for the Android framework API.

 

[Lowers]

answer: Full Android instructions inside

OS Specific Instructions

Windows

1. Download the latest Android SDK.

2. Unzip the package to the root of C:\ or run the executable.

NOTE: This will output a folder called "android-sdk-windows".

3. Open up the android-sdk-windows folder and launch the SDK Manager.

4. When you launch the SDK Manager for the first time it will ask for which packages to install. The only package we are concerned with at this time is "Android SDK Platform-tools, revision 4". You can reject all the others if you are not interested in them.

5. Once that is finished, you will need to install the USB drivers included with the Android SDK.

a. Click on"Available Packages" on the left.

b. Expand "Third party Add-ons".

c. Expand "Google Inc. add-ons".

d. Check "Google USB Driver package, revision 4".

e. Installed Selected.

6. Once that's finished installing, you can close the SDK Manager.

7. Go to the Control Panel, and select the System Properties (Windows XP) or System (Windows Vista/7).

8. Select the Advanced settings;

- Windows XP: Click on the Advanced tab.

- Windows Vista/7: Click on Advanced system settings on the left.

9. Click on Environment Variables.

10. Under the "System variable" section, you will look for "Path". Double-click on it.

11. In the "Variable values" section, add at the very end the location of the tools & package-tools folder, with a semicolon separating these two paths from the rest, e.g. %SystemRoot%;C:\android-sdk-windows\platform-tools;C:\android-sdk-windows\tools.

12. On the device, ensure that USB Debugging in enabled (Settings » Applications » Development).

13. Plug the device into the computer via USB cable. The computer will attempt to install the drivers automatically.

14. On success, open the command prompt on the computer, and type in the following command to sure everything is setup properly:

adb devices

15. If it lists any devices, everything is fine and you are finished. If not, the drivers may not be installed correctly, please continue.

16. Open the Device Manager.

a. Right-click on My Computer (Windows XP) or Computer (Windows Vista/7).

b. Click on Manage.

c. Click on Device Manager on the left.

17. You will probably see Unknown Device with ADB listed under it with a yellow exclamation mark.

18. Right-click on ADB.

19. Click on "Update Driver Software".

20. Click on "Browse my computer for driver software".

21. Click on "Let me pick from a list of device drivers on my computer".

22. Click on "Have Disk".

23. Click on "Browse".

24. Navigate to "C:\android-sdk-windows\google-usb_driver" and select "android_winusb.inf".

25. Click on "Android ADB Interface".

NOTE: You will get an Update Driver Warning, click on "Yes".

26. Once finished installing the driver, open the command prompt on the computer, and type in the following command to sure everything is setup properly:

 

[Lowers]

answer: Full Android instructions inside

adb devices

27. If it lists any devices, everything is fine and you are finished. If not, you may have further issues and will have to do further research on your own.

Mac OS X

Installing the Android SDK

1. Download the latest version of the Android SDK

2. Unzip it and move it where needed

unzip Downloads/android-sdk_r09-mac_86.zip -d~/bin

3. Open Terminal.app (in /Applications/Utilities)

4. Edit ~/.profile and append

export PATH=~/bin/android-sdk_r09-mac_86/platform-tools:~/bin/android-sdk_r09-mac_86/tools:$PATH

5. Load new .profile

source .profile

6. Run Android SDK Manager

android

 

[Lowers]

answer: Full Android instructions inside

How to take Screenshots through the Android SDK

Pre-requisites

- Ensure you have set up the Android SDK. If you haven't done so already, use our guide entitled "How to install and set up the Android SDK"

- Ensure you have the correct ADB drivers installed for your phone (Windows)

The procedure

1. Ensure USB debugging is enabled on your phone (Settings>applications>development), and connect it to your computer

2. Locate the folder you unzipped the Android SDK in, open the Platform-Tools (Could just be tools, depending on version) folder and double-click ddms.bat (it might be titled just ddms if you don’t show extensions).

3. The first time you open DDMS, you’ll be prompted with a window (see below) asking if you’re willing to send usage statistics to Google. Click the Proceed button to finish opening DDMS.

4. Next, the Dalvik Debug Monitor will open. Make sure your device is listed in the upper-left window, and select it by clicking on it once to highlight it (see below).

5. Now, to take a screenshot, go to Device (at the top), then Screen Capture (see below)

6. The Device Screen Capture window will open and show you whatever is currently on your phone screen. Simply navigate on your phone to the screen you want to take the screenshot of, and then press REFRESH.

7. Once you're happy with the image being shown to you in the Screen Capture window, press SAVE, and name it!

Now... take as many as you like by repeating steps 6 and 7!

 

[Lowers]

answer: Full Android instructions inside

How to Flash an RUU (HTC)

Method 1, using an .EXE file:

Most HTC devices will have an executable RUU file which will do all the flashing work for you. If not then you need to use method 2.

1. Go to Shipped ROMs and select your device.

2. Download the file which is relevant to your device, ie; if you want to stock Gingerbread on the Nexus one then you would pick -

PASSIMG_Passion_Google_WWE_3.10.1700.1_GRJ22_relea se_signed.zip
(Note this isn't an .EXE file but as the Nexus One doesn't make use of them, pay attention only to the file name.)

WWE - World Wide English, this tells us it is meant for devices all over the world and is a generic update.

3.10.1700.1 - This is the radio version,

GRJ22 - This build is the build ID, GRJ tells us it's Gingerbread.

3. Once the file has finished downloading, connect your device via USB and double-click on the .EXE file you downloaded.

4. The program will check your device's compatibility and if all is well, it will start the update procedure.

NOTE: If you are using a stock ROM and you are using the RUU to downgrade, you will first need to create a goldcard.

Method 2, using a .ZIP or .IMG file:

1. Go to Shipped ROMs and select your device.

2. Download the file which is relevant to your device, ie; if you want to stock Gingerbread on the Nexus one then you would pick -

PASSIMG_Passion_Google_WWE_3.10.1700.1_GRJ22_relea se_signed.zip

WWE - World Wide English, this tells us it is meant for devices all over the world and is a generic update.

3.10.1700.1 - This is the radio version,

GRJ22 - This build is the build ID, GRJ tells us it's Gingerbread.

3. Copy the file to the root of your sd card (IMPORTANT!)

4. Reboot into the bootloader using the button combo for your device or using ADB type, "adb reboot bootloader"

5. Wait a few seconds for the device to detect the update file.