HTC One XL Terminology Glossary v1.2 [2012/09/30] - AT&T, Rogers HTC One X, Telstra One XL

Ever wonder what a Rosie is? Ever wonder if someone is slaying a snapdragon? Ever wonder why someone would want to desense a ROM? If you're like me, your first few weeks parusing the forums for your shiny new HTC One X was frought with strange words and terms that make you wonder if they're talking about an Android device or a Disney movie. But even after those first few weeks, you finally feel comfortable with the vernacular, and wouldn't you know it but a new word comes up!
The purpose of this thread is to capture the definitions of words and terms that come up frequently in discussions of ROMs and MODs specifically for the HTC One X/XL. General terms like "RUU" and "TWRC" will not normally be defined here, unless there is something specific or innate to the HTC One XL. The idea is that when questions about these terms come up in discussions that one need only reply with a link to this thread. Please reply to this thread to suggest terms for inclusion or point out corrections and omissions in the definitions themselves. However, please do not use this thread to ask questions... start a new thread in the Q&A forum for that, optionally linking back to this thread.
3-Button Mod See "Button Remap"
ADB Acronym for "Android Debug Bridge"
Advanced Power Menu A mod that adds additional options to the menu that displays by pressing-and-holding the power key. Additional options include "Screenshot" and "Recovery" (in the menu that displays after selecting "Reboot").
Android Debug Bridge The command used to perform developer-style operations on an Android device from a PC. The "adb" command is included as part of the Android SDK and allows one to perform actions like installing applications, copying files, gathering logs, and running arbitrary shell commands. Communication occurs via the USB cable, or possibly via Wi-Fi, if enabled on your ROM.
Android Open Kang Project Often abbreviated "AOKP", the name of a custom AOSP-based ROM distribution. AOKP officially supports many different devices, but (at the time of writing) only unofficially supports the HTC One XL. AOKP and Cyanogenmod are two of the more popular AOSP-based ROMs. The official AOKP web site is http://aokp.co and the xda-developers thread about the HTC One X port is http://forum.xda-developers.com/showthread.php?t=1751134.
Android Open Source Project The publicly-released open source code of the Android OS released by Google at http://source.android.com. The acronym "AOSP" is commonly used.
AOSP Acronym for "Android Open Source Project". Often it is used as an adjective to refer to the version of a given application taken from the Android Open Source Project as opposed to a vendor-modified version (eg. AOSP lock screen). It can also refer to the basis of a ROM; for example Cyanogenmod9 is "AOSP-based" whereas CleanROM is "HTC Sense-based".
AOKP Acronym for "Android Open Kang Project" (suggested by theking_13)
APM Acronym for "Advanced Power Menu"
Aroma Installer A ROM installer that runs on an Android device from Recovery. The installer provides an improved user experience by presenting install-time options to the user in a friendly, touch-based UI. Custom ROMs can use Aroma to allow the user to select customizations like using the AOSP keyboard, installing certain user-space applications, and overlocking the CPU. See http://www.xda-developers.com/android/touch-and-customizable-rom-installer-aroma
Bootloader The first thing that "runs" when the device is powered on. The bootloader is responsible for starting the OS, which by default is (of course) Android but can also be recovery. When the bootloader is "locked" it first checks that the OS is signed by HTC and refuses to boot if the signature validation fails. Since custom ROMs are by definition not signed by HTC, a locked bootloader will refuse to boot a custom ROM. You need to unlock your bootloader using the steps at http://htcdev.com before loading any custom ROMs. (suggested by kleeman7)
Button Remap Refers to re-assigning the functions of the 3 capacitive LED keys on the bottom of the device. Stock HTC has Back, Home, and Recent Tasks keys. Many custom ROMs re-assign the keys so that pressing-and-hold the Back key will kill the application, pressing the Recent Tasks key will actually bring up the menu, and pressing-and-holding the Home key will bring up the Recent Tasks.
ClockWorkMod Often abbreviated "CWM", a custom recovery that can be installed on the HTC One XL. Although hotly debated, it tends to be less favoured than its main competitor, TeamWin Recovery Project (TWRP), for the HTC One XL because CWM was "not ported correctly". See http://forum.xda-developers.com/wiki/ClockworkMod_Recovery for general information about CWM.
CWM Acronym for "ClockWorkMod"
Endeavoru Code name for the "International" variant of the HTC One X, that uses the nVidia Tegra3 SoC. Do not attempt to flash a ROM for the endeavoru device, such as "Revolution HD", onto an evita (North American One X), as it will not work and has a high chance of permanently bricking the device (eg. here, here). Antonym: Evita.
Evita Code name for the "North American" variant of the HTC One X, that uses the Snapdragon S4 SoC, often referred to as the "XL" (instead of just the "X"). Carriers such as AT&T and TMobile (United States), Rogers (Canada), and Telstra (Australia) use this variant, while the rest of the world uses the Endeavoru. Antonym: Endeavoru.
Fastboot A protocol used to update the flash filesystem in Android devices from a host over USB. It allows flashing of unsigned partition images (1). The "fastboot" command is an executable command that is included as part of the Android SDK. The most common commands used are "fastboot oem unlock" to unlock the bootloader and "fastboot flash boot boot.img" to flash a boot image to the boot partition.
FC Acronym for "Force Close". This refers to the dialog that displays when and application crashes and is killed by the Android OS. Often it is used as a verb (eg. "The phone FC'd on me").
GSM Patch A mod that fixes a common radio issue with HTC One X custom ROMs (please post if you have a link and/or more details)
Hot Reboot An option available in the Advanced Power Menu. It reboots the device directly to the boot animation. It is less "drastic" than performing a normal, full reboot, which is effectively powering the device off then back on. As a result, a hot reboot brings the device back to the home screen more quickly than a full reboot, but is less thorough. (thanks to wongSlam for some of this info)
HOX Acronym for "HTC One X"
hoXl Acronym for "HTC One XL" (suggested by freakboy13)
HQ Camera A modified version of the stock HTC Camera application that captures higher-quality images and videos. This is done by reducing the amount of compression applied to the captured media. The file sizes of images and videos are larger when captured with the HQ Camera but are of higher quality. The HQ Camera APK replaces the stock camera's APK in the /system folder; the HQ and non-HQ camera cannot coexist. (related: "Sense Camera") (see http://forum.xda-developers.com/showthread.php?t=1533238 for details)
LTE Backdoor A special key sequence when entered into the phone will take you into a phone settings screen, allowing configuring which network technologies are used. This screen is often referred to when one is having difficulty achieving LTE, to make sure that LTE is actually enabled. In order to get to this screen, go into the phone and type: *#*#4636#*#*
Multitasking MOD A MOD for Sense-based ROMs that adjusts the background process killing policy. Stock HTC software aggressively kills background applications, presumably to conserve battery, and is "operating normally" according to HTC (6). The drawback of this policy is that apps tend to "restart" frequently after switching to other apps then switching back. There are MODs that adjust the policy called "Multitasking v1", which is less aggressive, and "Multitasking v2", which is less aggressive still. See Multitasking Mod *v2* - Improve Multitasking Performance for more information.
Odex The process of optimizing the dex bytecode of an Android application's APK file. Each APK file is actually a ZIP file that contains a file named "classes.dex", which contains all of the compiled Java bytecode. This "dex" file may be run through a tool to optimize it for the device, producing an "odex" file. A "dex" file is more flexible than its "odex" counterpart, as odex files cannot be used with other ROMs or even on other devices with different hardware configurations. See Odex files deodexing and zipalign explained and (How-To) Re-Odex a Rom for more information.
Nandroid Informal term referring to a complete backup of a device (typically captured while booted into recovery) that allows restoring the device to that exact state at a later point in time, especially if flashing a ROM fails.
Radio Interface Layer Often abbreviated "RIL", a stack of two components: a RIL Daemon and a Vendor RIL. The RIL Daemon talks to the telephony services and dispatches "solicited commands" to the Vendor RIL. The Vendor RIL is specific to a particular radio implementation, and dispatches "unsolicited commands" up to the RIL Daemon. (5). Basically, the RIL is the software library through which the Android OS communicates with the phone's cellular radio and modem hardware. The RIL libraries are located in /system/lib/*ril* on an Android device.
Recovery Recovery is in many ways an alternate operating system for Android phones that allows performing low-level operations outside of the Android OS, such as installing ROMs, backing up files, and wiping filesystems. To enter Recovery on the HTC One XL, reboot your phone and hold the volume down key; then scroll to "Recovery" using the volume keys and press the power key to select it.
RIL Acronym for "Radio Interface Layer" (suggested by kleeman7)
ROM Upgrade Utility Commonly abbreviated "RUU", a software package provided by manufacturers and/or carriers that runs on a PC and loads a stock ROM onto a device via USB cable. It is commonly used to restore a device back to a supported configuration before selling it or returning it on warranty. For an excellent guide on loading RUUs, see "Update your phone via RUU in Linux/Mac" by JeepFreak at http://forum.xda-developers.com/showthread.php?t=1668156
Rosie The internal codename used by HTC for the Sense launcher application. This term tends to be used frequently when discussing the HTC launcher and app drawer.
RUU Acronym for "ROM Upgrade Utility"
S-OFF Short for "Security Off", specifically referring to the security that protects the low-level partition table of the device. All devices come "S-ON" which prevents flashing ROMs that are not signed by HTC, unless you have followed the steps to unlock your bootloader. To check if your device is S-ON or S-OFF boot into the bootloader and look at the top of the screen (where you might see "unlocked" and "tampered") and around there you will also see either "S-ON" or "S-OFF". As of the time of writing (Aug 17, 2012) achieving S-OFF is currently not possible. If/when S-OFF is achieved, it will fully unlock the device, making full development possible. S-OFF is different from rooting but related to unlocking the bootloader. See S-OFF explained - by a Developer for an excellent explanation of S-OFF and (WIP)(DEV) S-Off to track the work going into achieving S-OFF.
S4 See "Snapdragon"
Sense The UI customizations of stock Android done by HTC and shipped in the stock images of HTC devices. This includes the launcher, calendar, app drawer, several widgets, and a framework that can be leveraged by third-party applications.
Sense Camera The camera application that is included in the stock HTC Sense OS factory-installed on HTC devices, marketed by HTC as "ImageSense". The Sense camera includes features like VideoPic, Instant Capture, Continuous Shooting, HDR, and SmartFlash. Many, if not all, of these features are not (as of July 2012) available in AOSP-based ROMs because the Sense camera is deeply integrated into the Sense framework and proprietary camera drivers. For a fantastic explanation of this issue, see "PSA: The Sense Camera and AOSP-based ROMs" by rohan32 at http://forum.xda-developers.com/showthread.php?t=1780038. Also, see http://www.htc.com/www/htc-sense/camera for details. (related: "HQ Camera")
Snapdragon "A family of mobile system on chips (SoC) by Qualcomm. Qualcomm considers Snapdragon a "platform" for use in smartphones, tablets, and smartbook devices." (2) This is the SoC used in the North American (a.k.a. "evita") variant of the HTC One X. This is in contrast to the Tegra3, which is used on the International variant.
SuperCID A hack that changes the Carrier ID ("CID") of the HTC One X from the carrier-specific ID (eg. "ROGER001" for Rogers) to the generic carrier, 11111111. This allows installing RUUs from other carriers that would otherwise fail due to the CID mismatch. AT&T devices actually require SuperCID before the bootloader can be unlocked. [4] (suggested by kleeman7)
TeamWin Recovery Project Often abbreviated "TWRP", a custom recovery that can be installed on the HTC One XL. Although hotly debated, it tends to be reported to be more stable than its main competitor, ClockWorkMod (CWM) for the HTC One XL because CWM was "not ported correctly".
Tegra3 "A system on a chip (SoC) series developed by Nvidia for mobile devices such as smartphones, personal digital assistants, and mobile Internet devices." (3) This is the SoC used in the International (a.k.a. "endeavoru") variant of the HTC One X. This is in contrast to the Snapdragon, which is used on the North American variant.
TWRP Acronym for "TeamWin Recovery Project"
XL Informal name to refer to the North American variant of the HTC One X.
Bibliography:
1. "[Newbie Guide] adb/fastboot/bootloader/android 101" http://forum.xda-developers.com/showthread.php?t=619153
2. "Snapdragon (system on chip)" http://en.wikipedia.org/wiki/Snapdragon_(system_on_chip)
3. "Tegra" http://en.wikipedia.org/wiki/Tegra3#Tegra_3
4. "[HOW TO] How to do virtually everything to your ONE X ..." http://forum.xda-developers.com/showthread.php?t=1678308
5. "Radio Interface Layer" http://en.wikipedia.org/wiki/Radio_Interface_Layer
6. "HTC: One X multitasking is 'operating normally,' but tweaked for Sense" http://www.theverge.com/2012/5/16/3024854/htc-one-x-multitasking-operating-sense
Change Log:
1.2 - Sept 28, 2012
added LTE Backdoor
1.1 - Aug 17, 2012
added a note to "Endeavoru" that flashing an endeavoru ROM onto an evita device will never work and has a high risk of bricking it.
added "Multitasking MOD", "Odex", and "S-OFF"
added link to the development thread of "HQ Camera"
1.0 - July 19, 2012
Initial Version

Very nice, sticky pl0x
Might I also suggest:
Fastboot
ADB
AOSP

Might be a little overkill but:
Root
Unlock/Relock Bootloader
SuperCID
Radio/Ril
And how to boot into recovery from phone powered off.
Great guide. I'm sure it will help a lot of people.
Sent from my HTC One X using xda premium

denversc said:
Carriers such as AT&T and Verizon (United States),
Click to expand...
Click to collapse
Might wanna get rid of Verizon... ;-)
Sent from my Xoom using Tapatalk 2

rohan32 said:
Might I also suggest:
Fastboot
ADB
AOSP
Click to expand...
Click to collapse
Done. Thanks for the suggestion.

kleeman7 said:
Might be a little overkill but:
Root
Unlock/Relock Bootloader
SuperCID
Radio/Ril
And how to boot into recovery from phone powered off.
Click to expand...
Click to collapse
I've added bootloader and SuperCID. I put in a placeholder for RIL since I don't really understand what it is. If you have a defintion, I'd be glad to include it. I agree that root is overkill so I left it out.
EDIT: And what were you referring to by "how to boot into recovery from phone powered off"? I had included the trick to hold the volume down key during reboot (although I cleaned up the definition after reviewing it because of your feedback). Were you thinking of something else?
Thanks for the suggestions.

Rblacula said:
Might wanna get rid of Verizon... ;-)
Click to expand...
Click to collapse
Oops haha. Done. Replaced with TMobile, which is what I meant to put in the first place. I'm on Rogers in Canada so all of the US carriers are just names to me.

You could add "hoXl" the proper acronym for the HTC one XL
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2

What about AOKP?
And for RIL, radio interface layer, basically what communicates between the hardware radio and the software?
Sent from my HTC One X using Tapatalk 2

denversc said:
I've added bootloader and SuperCID. I put in a placeholder for RIL since I don't really understand what it is. If you have a defintion, I'd be glad to include it. I agree that root is overkill so I left it out.
EDIT: And what were you referring to by "how to boot into recovery from phone powered off"? I had included the trick to hold the volume down key during reboot (although I cleaned up the definition after reviewing it because of your feedback). Were you thinking of something else?
Thanks for the suggestions.
Click to expand...
Click to collapse
I have seen many threads in people saying they are unable to boot into hboot, when the phone is "off", but the phone is not really off. To achieve a true off state and not a standby state you need to disable fastboot in the power setting menu. If you don't your phone is is essentially hibernate and won't boot into hboot no matter how hard you try.
Borrowed from wikipedia:
A Radio Interface Layer (RIL) is a layer in an operating system which provides an interface to the hardware's radio and modem on e.g. a mobile phone.
Android RIL
The Android Open Source Project provides a Radio Interface Layer (RIL) between Android telephony services (android.telephony) and the radio hardware.
It consists of a stack of two components: a RIL Daemon and a Vendor RIL. The RIL Daemon talks to the telephony services and dispatches "solicited commands" to the Vendor RIL. The Vendor RIL is specific to a particular radio implementation, and dispatches "unsolicited commands" up to the RIL Daemon.
Sent from my HTC One X using xda premium

For me the Hot Reboot is booting to the Boot Animation. A Normal reboot is like booting cold or rebooting after going into recovery mode, shows the green HTC text with the white background.

Thanks. I didn't even know what AOSP stood for. I just assumed it meant "stock". I was making things up like Android Original Stock Program or something like that....hah.

Nice job looks very helpful
Sent from my Nocturnalized Beast

freakboy13 said:
You could add "hoXl" the proper acronym for the HTC one XL
Click to expand...
Click to collapse
Done. Thanks for the suggestion! Make sure I got it right

theking_13 said:
What about AOKP?
Click to expand...
Click to collapse
Done. Thanks for the suggestion!

kleeman7 said:
I have seen many threads in people saying they are unable to boot into hboot, when the phone is "off", but the phone is not really off. To achieve a true off state and not a standby state you need to disable fastboot in the power setting menu. If you don't your phone is is essentially hibernate and won't boot into hboot no matter how hard you try.
Click to expand...
Click to collapse
Thanks for this info. I've included it in the definition of "fastboot".
kleeman7 said:
Borrowed from wikipedia:
A Radio Interface Layer (RIL) is a layer in an operating system which provides an interface to the hardware's radio and modem on e.g. a mobile phone.
Android RIL
The Android Open Source Project provides a Radio Interface Layer (RIL) between Android telephony services (android.telephony) and the radio hardware.
It consists of a stack of two components: a RIL Daemon and a Vendor RIL. The RIL Daemon talks to the telephony services and dispatches "solicited commands" to the Vendor RIL. The Vendor RIL is specific to a particular radio implementation, and dispatches "unsolicited commands" up to the RIL Daemon.
Click to expand...
Click to collapse
I've included some of this info and the wikipedia link in the definition of "Radio Interface Layer". Thanks!

wongSlam said:
For me the Hot Reboot is booting to the Boot Animation. A Normal reboot is like booting cold or rebooting after going into recovery mode, shows the green HTC text with the white background.
Click to expand...
Click to collapse
Thanks for this info. I've included some of this info in the definition for "Hot Reboot".

would like to this in here [INDEX] AT&T/ROGERS One X Resources Compilation Roll-Up

bump

Related

[REF] Ivo's Introductory Guide to this forum (READ ME FIRST)

Desire HD development is now in full swing.
This guide/overview will hopefully show you all about how to customize your Desire HD.
NOTES: If this reference contains any mistakes/needs updates, please PM me. If you would like something added, either PM or include it in a reply.
Legend said:
* means something requires root
^ means something requires S-OFF
Click to expand...
Click to collapse
WARNING: At the time of writing, the newest HTC update (to android 2.2.1) will make your phone unrootable. Do not perform a phone update if you want to be able to follow the majority of this guide!
Follow this guide to downgrade 1.72/1.84 (Android 2.2.1) [if you have updated to it] back to the rootable/moddable 1.32 before following this guide.
Files
A lot of the files and ROMs found here have been kindly mirrored by mousey_ at his site, here. (Getting outdated )
Another link to downloads is at http://www.iloveabath.co.uk/
Tools
Alot of these tools might be needed at some stage or another.
Android SDK - gives you tools like adb, used for all pc-based android development
HTC Sync - Has correct USB drivers for the DHD and lets you sync up various data
Fastboot - lets you flash .img's to your phone easily through it's fastboot interface
Flasher^ - lets you flash boot and recovery and create new bootanimation flashes.
QtADB - Useful graphical interface for using adb, also fastboot and recovery
Root
Note: If you just want to fully root your device as easily as possible, you might try this tool by liquidperfection. Check Default, ENG HBOOT and PERM ROOT. This will give you Root, S-OFF and Eng bootloader.
Root means that you can do things on your android that require the root user's access (the super-administrator account on linux). You manage this account by installing SuperUser and su. In the DHD, only having root access does not mean you can do all things usually associated with 'rooting your phone'. Alot of things (such as installing custom ROMs) need S-OFF as well.
NOTE: Custom ROMs are almost always pre-rooted. You will not need to 're-root' after installing a custom ROM.
VISIONary - An exploit app that gives you root.
- Needs USB Debugging on. might need 'Unknown Sources' on to install.
- You only need a temproot to achieve S-OFF (which will give you root thereafter), otherwise you can do a temproot followed by a Permaroot.
- Use it on 1.32 build rom only
PSNeuter - is a script that will let you get root access in 1.32 or 1.72 builds.
Superuser* - The su and Superuser app, for managing root access on your phone. Visionary installs this for you. This is the market link.
S-OFF*
This means Security-Off, which is a flag in the DHD's internal memory that lets you write to protected partitions of it, like /system and all of the boot partitions. Having this effectively gives you 'full' root access and is needed in addition to root for many of the more interesting rooting activities (modding, etc).
There are two ways to achieve S-OFF on your phone:
A) Load the engineering hboot, which makes the phone think it's S-OFF - this is called ENG S-OFF
B) Flip the internal 'switch' in the phone's Radio to S-OFF status. This is called Radio S-OFF
ENG S-OFF is 'softer' than Radio, it can be undone by a software update. You only need ENG S-OFF for updating ROMs. You need both for updating radios.
Radio S-OFF will never need to be redone. It is one of the most permanent changes you can make to your phone. Eng S-OFF can be cleared by a new hboot (i.e from a stock RUU, explained later).
ENG Hboot S-OFF Tool* - installs a new hboot img to your phone, which puts the internal memory card in S-OFF at boot.
- ENG Hboot scripts A guide for doing this is can be found here
- A completely manual guide to achieving S-OFF can be found here.
Radio S-OFF tool* - turns on permanent S-OFF in the radio. Doing this, even the normal bootloader will recognise that the phone is in S-OFF state.
- Using the gfree script, there's a manual way to do it
- Do this on a 1.32 rom only, it will stay thereafter.
root adb boot.img^ - Flashing this boot.img will give adb root permissions without having to ask.
Stock Roms
These are complete stock roms for the DHD, returning it to its original state.
The only thing not touched by these would be a Radio S-OFF.
The Vanilla HTC Stock roms are RUUs which can be run from the PC.
Others have uploaded clockworkmod backups from their phones to have near-perfect copies of Vendor's ROMs. Near-perfect because S-OFF is still required to do the backup.
Use clockworkmod to restore them.
HTC WWE Stock RUUs - (World Wide English), for stock devices. These are RUUs to completely flash the device from the PC.
- If you are having trouble with them not connecting to your phone, try my guide here.
Source of more Roms and 2.36 (Gingerbread) WWE RUU
O2 1.31.207
H3G UK 1.31.771
HTCCN CHS 1.31.1400
O2 1.32.207
HTC Asia 1.32.707
TMO DE 1.39.111
Orange UK 1.40.61
Vodafone AU 1.32.178
Three/Hutchinson AU 1.32.861
HTCCN CHS 1.60.1400
Clockworkmod Recovery^
This recovery.img allows you to do easy backups and restores of ROMs, as well as apply custom, unsigned roms and imgs.
To get to recovery mode on the DHD, power off the device fully (makesure fast booting is off), then when turning on, hold down the power and volume down buttons.
Rom Manager^ - This is a market app that will install the latest ClockWorkMod for you.
- The actual images are available here. The Desire HD is called 'ace'. 2.5.1.3 is most stable for ROMs using 2.2.1 android, 3.0.0.6 and above is most stable for ROMs using 2.3 android.
- flash these to the recovery partition using fastboot, as shown below in the guide
Almost all custom ROMs use this to install. A normal process is:
Backup apps and/or data. Be careful about backing up system data, moving from one ROM to another and restoring it will almost always screw with them.
Download the zip for the ROM, and it's easiest to put it in the root directory of your sdcard.
Restart the phone into recovery mode, to get to clockworkmod.
Perform pleliminary steps: perform a backup first. For wiping a new ROM: Make sure battery is 100%, wipe cache, dalvik cache, battery stats and factory data. (see the tip at the end of Custom Roms section for this)
Choose to install a zip, from sd card. Find the zip you downloaded and install!
Wait patiently for the 1st boot-up, it almost always takes longer.
Custom Roms^
These are customized ROMs from the community, promising different combinations of speed, performance, features and looks over HTC's sense.
The easiest way to install them is through clockworkmod.
Here are some of the most popular ROMs for the DHD at the moment. It is in no way an exhaustive list.
Also see this list.
LeeDroid Froyo - A Customisation of HTC's Sense, with aims of long battery life and reserved improvement. Comes with his own custom kernel.
LeeDroid Gingerbread - Same as above, based on HTC's Gingerbread Sense (leaks).
Android Revolution HD Froyo - Customisation of Sense, with Apache14's kernel. Also aims to improve on all aspects of the ROM while not modifying its look.
Android Revolution HD Gingerbread - Same as above, based on HTC's Gingerbread Sense (leaks).
CoreDroid Froyo & Gingerbread - Customisation of Sense, with the developer's own UI tweaks and enhancement to add a shinier look and feel.
GingerX Gingerbread - Gingerbread Sense customisation with some added UI tweaks as well.
RCMixHD Gingerbread - Another Gingerbread HTC Sense ROM.
RCMixHD Froyo Rotating - Includes the Desire Z's rotating Sense UI.
CyanogenMod 7 - Cyanogen's famous version of Android, released for the DHD.
CyanongenMod Nightlies - Nightly builds of the above.
CleanDHD - Clean, minimal ROM with bases of CM6 and CM7 to keep things fast and let you choose what to install.
MIUI 1.4.x - MrGarak's mostly vanilla version of this Chinese customisation of Android. Has a completely new look and feel. (Don't worry, it's in English).
Ray's MIUI 1.4 - Ray-619's customisation of MIUI.
This thread may be handy for wiping your phone with a zip, before changing from one ROM to another.
Kernels^
Custom kernels for the DHD, hopefully allowing better performance, features or overclocking of the phone.
These are designed for 1.72/1.84 ROMs, or for Cyanogen when stated.
Gingerbread custom kernels will come when HTC release source for that.
Clockworkmod can be used to install some, or fastboot using the zimage partition (plus some additional modules may be required to fix WiFi).
See their thread for details.
SetCPU - (forum link) - Available on the Android Market, this is almost essential to make use of overclocked kernels.
Buzz OC/UV 1.51ghz
Buzz OC/UV 1.22ghz
kAmMa's OC Kernel
LeeDroid's Kernel
LorDMod CM / MIUI Kernel - Warning: do not flash for sense ROMs!
Kali's CM Kernel - Also CM only kernel
Jkoljo's Kernal Flasher - a windows based tool for automagically flashing kernels without the fuss of manual fastboot.
Radios^
Radios contain the firmware for the chipsets in your device that control the phone, gps, wifi, etc. There are many different versions out there.
A better ('ideal') radio will give you better reception while using less battery power.
It is a general consensus by the community that newer radios have generally gotten better from the original that you might have on your phone.
You can flash a radio .img onto your phone by using fastboot, into the radio partition. How to do this is shown below in this thread.
Please be sure to have both Eng and Radio S-OFF before doing so.
Always check the md5 hash of the image you want to flash, to be sure it is a non-corrupt file. (use something like this or this to check an md5 hash)
It is one of the most crucial parts on your phone and you always want to make sure you flash a working one on.
User Drakknar has compiled an excellent, almost exhaustive list of DHD radios in his thread.
It might be helpful to install the RIL profile associated with the radio you install. This helps how android natively communicates with your phones radio. See jkolo's thread here for CWM installable zips.
Otherwise just use the radio that your rom developer recommends.
Guides
Step by Step guide on going from a stock DHD to a rooted, Custom one
On rooting, S-OFF and clockwork
Another on root and S-OFF
S-OFF, the 'manual' (hard) way
Clockworkmod installation for mac users
Guide to installing new radios
Uninstalling system apps with Titanium
Or disabling them through the shell
If you are having trouble installing RUUs
Flashing ROMs through your phone
Editing apk skins
Using fastboot
In order to use this with anything not signed by HTC, you will need S-OFF.
If you follow things carefully, it is not hard to do this properly. Doing things wrong with fastboot, however, is the easiest way to brick your phone.
Download and install HTC Sync to get correct USB drivers.
Download fastboot and put it in a convenient directory ( e.g. C:\desirehd\ or C:\android\, or replace the one in your SDK installation)
Turn off / restart the phone (fully); while it is restarting, hold down POWER and VOLUME DOWN buttons until it boots into the bootloader.
Select the fastboot option, and connect the phone to your PC.
Start a cmd prompt / terminal, and navigate to fastboot's directory.
type fastboot devices, and check that it has one device listed there as your phone in fastboot.
To flash an img, type fastboot flash <partition> <path/to/new.img>
Partitions:
hboot - flash the ENG hboot here to achieve S-OFF
boot - the bootloader
zimage - contains kernel
recovery - used for clockworkmod
radio - the firmware for your phone's radio chip
system - the /system partition
splash1 - contains the splash screen on initial boot
Always make sure the .img you have is the correct one for that partition and is a working/non-corrupt file!
Example for flashing clockworkmod:
Download clockworkmod and unzip the .img so that it is in the same directory as fastboot
Connect/setup up your phone as instructed above
Use a command similar to this: fastboot flash recovery recovery-clockwork-2.5.1.3-ace.img
After it's finished, reboot into your bootloader, choose the recovery option, and you should load into clockwork's recovery!
Useful Apps
These are mostly useful utility / customisation apps, which a high percent of people might have, and/or are to do with this guide.
Most are available on the Android Market.
BusyBox Installer^ - A prerequisite tool for a lot of other apps, providing some useful base linux functionality not present by default on android. (comes preinstalled in a lot of custom ROMs)
Superuser* - used to manage root user rights on other apps (also usually comes preinstalled).
Titanium Backup* - Extremely useful for backing up applications and settings. Will need S-OFF to restore system app backups.
SetCPU* - Allows for overclocking and profiling of the CPU
Typefresh^ - Lets you change Android's default font.
MetaMorph - A meta-app for changing styles and icons in other apps and skins.
Root Explorer* - 'The' root file explorer app. For getting down and dirty with android's file system.
ES File Explorer - IMO, one the best free normal file explorers. Also capable of root access.
AdFree^ - incase you don't like supporting ad-based free apps
Terminal Emulator - shell access to your phone. Can make use of root with the su command.
ConnectBot - I think an even better shell and ssh client. Same as above.
FasterFix and GPS Status - allow you to optimise your GPS chip, to get as fast a fix as possible. Set your region with FasterFix and download new A-GPS data with GPS Status.
Links
Useful links:
HTC Source Code
HTC Developer guide - on tools, adb and flashing
MoDaCo Forums - another great android development community
VillainROM forums - and yet another
XDA Desire HD Wiki page
Excellent all-in-one thread. I think DHD deserves a thread like this, thanks a lot @ivolol.
It should be sticky!!!
Better and more complete than the first thread ([REF] DesireHD | GUIDES | LINKS | FAQ's | READ BEFORE STARTING NEW THREADS)
liljom said:
It should be sticky!!!
Better and more complete than the first thread ([REF] DesireHD | GUIDES | LINKS | FAQ's | READ BEFORE STARTING NEW THREADS)
Click to expand...
Click to collapse
+1 Sticky please
Absolutely a must read! Thanks, didn't visit this forum for a while and all the new terms like s-off, hboot etc. made me a bit dizzy. You made my day.. Did I thank you already? if not: thanks
+1 for the sticky request
Is there also a thread which shows you have to edit a HTC ROM.
So get the system.img boot.img etc out of it.
And repack it as a .zip so you can flash trough recovery... ???
Awesome job of summarizing all threads and 'tweak' info on DHD!!
I had read most of this already, but as I was not reading the forum for 1 week now, I was just looking at where to begin reading again.
This is exactly what I need.
For all 'noobs' (me included ) it might be usefull to provide some general guidelines:
- get visionary for perm root, then
- blabla to s-off, then
- blabla to fastboot
etc...
AWESOME job
paulus_01 said:
Awesome job of summarizing all threads and 'tweak' info on DHD!!
I had read most of this already, but as I was not reading the forum for 1 week now, I was just looking at where to begin reading again.
This is exactly what I need.
For all 'noobs' (me included ) it might be usefull to provide some general guidelines:
- get visionary for perm root, then
- blabla to s-off, then
- blabla to fastboot
etc...
AWESOME job
Click to expand...
Click to collapse
Installing and using VISIONary is pretty easy imo, and I have linked to already good guides for how to write your hboot to achieve S-OFF;
I have however added a general guide on how to use fastboot.
ivolol said:
Installing and using VISIONary is pretty easy imo, and I have linked to already good guides for how to write your hboot to achieve S-OFF;
I have however added a general guide on how to use fastboot.
Click to expand...
Click to collapse
it is easy to install indeed...guess I was saying to include a small how-to (how to install custom rom; get visionary & perm root, get s-off with..., etc...)
But yes, the guides are good enough....
Brilliant thread, got everything needed to get started cheers.
I'm a little gutted that you have to s-off to install custom roms, prefered the standard desires way, nevermind.
Does anyone know where to find a uk Vodafone stock 2.2 Rom?? Don't want to do anything till I have a copy of that, also does s-on go back to s-off when you flash a stock Rom??
Cheers again for the thread and any help you can give.
Blinky
Sent from my Desire HD using XDA App
Blinkydamo said:
Brilliant thread, got everything needed to get started cheers.
I'm a little gutted that you have to s-off to install custom roms, prefered the standard desires way, nevermind.
Does anyone know where to find a uk Vodafone stock 2.2 Rom?? Don't want to do anything till I have a copy of that, also does s-on go back to s-off when you flash a stock Rom??
Cheers again for the thread and any help you can give.
Blinky
Sent from my Desire HD using XDA App
Click to expand...
Click to collapse
You need S-OFF to do any sort of backups and/or flashes of custom roms.
However after restoring one of these it's possible to just reflash the hboot and recovery partitions with stock WWE ones and your extremely close to being right back at vanilla
successfully rooted, s-off and clockwork mod.....used your links, which do provide good instructions (obviously created by others).
These links are a handy startpage, now, just 1 question, why would I use nandroid, if I have clockwork mod set?
Nandroid allows you to backup and recover your existing Rom and settings before flashing another rom or kernel. Always backup before flashing.
Sent from my Desire HD using XDA App
Blinkydamo said:
Nandroid allows you to backup and recover your existing Rom and settings before flashing another rom or kernel. Always backup before flashing.
Sent from my Desire HD using XDA App
Click to expand...
Click to collapse
Thanks, I understand that, but yesterday I made a backup on my sd with clockwork recovery.
Isn't that enough?
paulus_01 said:
Thanks, I understand that, but yesterday I made a backup on my sd with clockwork recovery.
Isn't that enough?
Click to expand...
Click to collapse
They are alternate methods for achieving the same goal.
ivolol said:
They are alternate methods for achieving the same goal.
Click to expand...
Click to collapse
That is what I have understood, was a bit unclear to me, why a lot of guides say, need to do android backup etc....as the clockworkmod does the same.
Actually, some further investigation indicated that a nandroid backup is made by cw mod
hurray, it's sticky : )
Thanks, I'm yet to root my phone but when I do this thread will come in useful. I'm probably going to wait until gingerbread or other roms with major improvements are available.
hey,
QtADB is graphical interface for: adb,fastboot and recovery (including nandroid) not only adb
Credit to the OP
An excellent one stop shop for any Desire HD questions
Thanks

[GUIDE] The Mesmerize Glossary

Introduction
Welcome to the Mesmerize Glossary!
This glossary is written specifically with the Samsung Mesmerize, the US Cellular version of the Samsung Galaxy S, in mind. The terms defined below may loosely apply to similar Galaxy S models, or on a case-by-case basis for other devices. It is written for the "advanced beginner"; if you aren't sure what 3G or 4G is, or what the difference is between GSM and CDMA, I would instead recommend starting with the XDA Wiki's Acronyms and Glossary pages to start building your knowledge base from. A few terms from those pages may also appear here if they are especially applicable.
This glossary is intended to both define and describe terms you might see frequently here in the forums, such that no external wiki or forum thread link should be required, though links may still be offered for further reference at the reader's option. Enough information should ideally be provided on each term to offer a strong understanding of the term in the context it is commonly used, but generally, neither advanced knowledge nor in-depth guides or walkthroughs really belong here.
Should you notice that a term you know a definition of--or would like to have defined--is not present, please post to this thread to request it be added or explained.
Using the Glossary
For completeness and ease-of-use, some information may be repeated across the glossary for users searching just for one particular term. The Glossary has been created so that a visual scan of the bolded terms allows users to search the glossary in that way.
If you prefer to search for a term via your browser's Find function, search for "((term)) -" (that is, your desired term, a space, and a hyphen). This should result in locating the exact term you're searching for. Additional wordings of terms (such as nicknames, acronyms of other terms, etc.) have also been included to allow for better search results when using a browser's Find function. Note that these additional wordings may not themselves fit alphabetically, but have been included with their associated term in order to conserve post space.
Terms
Sorted alphabetically.
AOSP - Acronym, also Custom ROM.
Acronym: Android Open Source Project. The group created by Google that continues to develop the Android operating system. Also includes any non-Google member of the Android development community.
Custom ROM:
Author: many various authors and porting contributors.
"Ported" for Mesmerize (and many other devices) from the most generic version of Android available.
Platform Info: Android 2.2 (Froyo), AOSP based.
Kernel: Voodoo-compatible AOSP Kernel included, though a separate download of the ROM.
In the context of a Mesmerize, the Samsung- and US Cellular-free version of the Android operating system as ported (at least in terms of how Android interacts with the Kernel) to the Mesmerize. Excellent battery life with the voodoo-compatible AOSP kernel, and very fast without the Samsung or US Cellular apps. Note that AOSP ROMs and Kernels are NOT compatible with TouchWiz ROMs or Kernels.
Amend Scripting -
Amend Script -
Amend - Scripting Language. An old scripting language used to flash ROMs and Mods to a phone within a recovery or other automated flashing process. Google deprecated Amend in Android 1.5, and has since switched to Edify scripting. Supported only by CWM 2.5.x. (see also: Edify)
BLN - Mod. Backlight Notification mod. Some Android devices have LED indicators to show when you've received a text or e-mail without turning the screen itself on. Since Galaxy S devices do not have LEDs, the Backlight of the soft buttons (Menu, Home, Back, and Search) to fill that role. Note that this requires a BLN app to control. Newer ROMs may not need this mod, or have its functionality included in the ROM/Kernel.
Bootloader - Framework. The text interface that allows interaction with the kernel, application framework, and so on, for the purpose of flashing custom ROMs and other development functions. Note that on many Android devices, either the manufacturer or the carrier have chosen to run a locked framework, making development for the device much more difficult.
Specific to the Mesmerize (as well as the Fascinate and Showcase, at least), Samsung and US Cellular both chose to leave the bootloader unlocked, and the Mesmerize was easily rooted the day after it was released. The Bootloader is what is technically seen when using either the stock recovery, or the custom CWM recovery. Note that users who have loaded the QuickBoot app will simply reboot their phone when selecting the "Bootloader" option.
"Blue" Recovery -
Blue Recovery - Framework. The stock Android recovery. Named for the blue text the menu options use.
Clockworkmod -
Clockworkmod Recovery -
CWM -
CWM Recovery - Framework. The custom Recovery portion of the ROM Manager app originally created by Koush. By way of the Bootloader interface, it allows you to create or restore a Nandroid backup (everything but the kernel is saved to SD card in clockwork/backups/), wipe the system data and cache (Dalvik) partitions (sometimes necessary before flashing a new ROM), flash .ZIP packages saved on the SD card containing ROMs, Mods, Kernels, etc.
Originally, the Mesmerize was restricted to CWM Red, a modified version of CWM 2.5.x which recognized both Amend and Edify scripting types. Since then, several versions of modified CWM 3.0.x have been made available, and have been themed to come in several different colors. These can be found as stand-alone flashes, or bundled into ROMs. CWM 3.0.x only recognizes Edify scripting. Though previously it was recommended to stick with CWM Red for its support of Amend scripting as well as Edify, nearly all of the modern ROMs and Mods available have been written to use Edify. The newer MTD-based ROMs use CWM 4.x, which uses the original orange coloring.
NOTE: Certain MTD-based ROMs for the Mesmerize (and Fascinate and Showcase) are now fully supported by ROM Manager, so users using those ROMs can now install CWM 4.x via ROM Manager.
CWM also offers functions to enable or disable the Lagfix function of the Voodoo kernel (note that a Voodoo-compatible kernel must also be loaded for this menu to function). (see also: Amend, Bootloader, CWM Red, Edify, Lagfix, Nandroid, Voodoo)
Dalvik - The name of the Android-specific Java-based virtual machine (VM) that executes the code for apps. Each app runs in its own Dalvik VM. This allows for a smoother user experience since, for example, if an app crashes, it doesn't crash the entire operating system, but simply the virtual machine in which it was running.
Before running an Android app, Dalvik converts it into a Dalvik Executable, or DEX file. Prior to being converted to a DEX file, an Android app has certain Java classes stored within it for easy execution; these classes are similar to DLLs on a Windows system.
An Optimzed DEX file, or ODEX, is a cache of the Android App's Java classes converted for use with a DEX file. This makes executing those functions faster since they are cached, but makes editing or hacking the apps more difficult, since not all the code is contained within just the APK file; you can often find APK and ODEX files by the same name when browsing with a powerful enough file manager app.
Dalvik was originally developed by Dan Bornstein, and he named it after the fishing village of Dalvik, Iceland, where some of his ancestors lived.
Deodex - Verb. To literally De-ODEX an app or ROM. Specifically, this takes the ODEX cache and compiles it back into the APK file, leaving just the APK file. This makes altering the APK file much easier. (see also: Dalvik, ODEX)
Download Mode - Process. The process by which the phone is prepped for flashing with Odin or Heimdall. Remove the battery and connect the phone to a computer via the USB cable. Hold the Volume Down button until a screen with yellow text saying "Download Mode" and an Android shoveling rubble appears. In the Odin window, a small box should change to yellow, indicating it has recognized the device and it is ready for flashing. Note that no indicator will be present in Heimdall.
EA11 -
EB11 -
EB16 -
EC10 - Android Version. EC10 is the current release build of Froyo (Android 2.2.1) as released by US Cellular for the Mesmerize. Previous (leaked) builds include EA11 and EB16. Note that EB11 is specifically a Showcase build, and not for Mesmerize. This version is partially deprecated now as Samsung has recognized a "Missed Calls" issue with this build, as well as in their Eclair builds, although no official ROM has been released yet. That said, the EE19 leaked ROM addresses this "Missed Calls" issue. (see also: EE19)
EC01 Radio - Mod. This is actually the radio from a recent source drop from the Fascinate. Some users have reported faster 3G speeds and faster GPS pinpointing while using this radio. It also allows for the use of Fascinate ROMs without the need for porting, since Fascinate handles certain things different than the Mesmerize (such as SMS padding, etc.). Note that this radio was renamed from the original "ED01" source drop.
Eclair - Android Version. - The Google-specified codename of Android 2.1. Of note is the alphabetically progressing, food-themed naming convention.
Edify Scripting -
Edify Script -
Edify - Scripting Language. The current scripting language used to flash ROMs and Mods to a phone within a recovery or other automated flashing process. Google deprecated Amend--the previous scripting language--in Android 1.5, and at that time switched to Edify scripting. Supported by CWM 2.5.x, CWM 3.0.x, and CWM 4.x. (see also: Amend)
EE19 - A leaked version of Froyo (Android 2.2.1) that addresses the "Missed Calls" issue identified by Samsung for US Cellular customers. The naming convention puts the release date on or about May 19th, so this is the freshest version of Froyo available to the Mesmerize. At this time, work is still being done to build custom ROMs off of this release.
ESKBL - Mod. Stands for "Extended Soft Key Back Light". A mod specifically for the Mesmerize that allows you to alter how the backlight on the softkeys function.
Fascinate - Device Model. Specifically, this is the model of Samsung Galaxy S available for Verizon customers. Because its model number is SCH-I500, as the Mesmerize's model is, certain components such as mods, ROMs, and themes have been more readily ported between the two models. NOTE: Always ensure the Fascinate component you wish to use on your Mesmerize is actually compatible, some are not.
NOTE: The Fascinate has recently been retired on the Verizon website in favor of a newer Samsung model, likely the not-yet-released Samsung Stratosphere.
Flash - Verb. To transfer or "write" a ROM image, Kernel, Recovery, or complete package of any of the three onto the "flashable" (or writable) memory (ROM) of the Android device.
Framework - At least within the context of Android devices and this glossary, the basic components that make up the core of a complete Android installation; they include the Recovery, Kernel, and OS.
Froyo - Android Version. The Google-specified codename of Android 2.2. Short for "Frozen Yogurt". Of note is the alphabetically progressing, food-themed naming convention.
GAPPS - Mod. An abbreviation for a collection of "Google Apps" for Android devices; Gmail, Google Talk, the Android Market, and so on. This package varies by ROM, and depends on which apps the ROM author chose to include.
Hienz 57 -
H57 -
Heinz 57 - Custom ROM.
Author: Created by dfgas, now being managed by BakedTator. Froyo version based on EC10 Pick-n-Pack v0.3 by phidelt82; Gingerbread version based on ??
Designed for Mesmerize/Showcase.
Platform Info: Android 2.2 (Froyo), or Android 2.3 (Gingerbread); TouchWiz-based, EC10 build (Froyo), ?? build (Gingerbread).
Kernel: Voodoo-compatible TouchWiz kernel included.
This ROM bundles a lot of different mods and customizations commonly requested. The name refers to the fact that portions from several different ROMs were included to some degree; Some ED01 frameworks were included to allow sbrissen's 6-lock mod to work (settings for this mod have been included in the settings menu), while it contains the MIUI Music Player. The Phone.apk and Dialer tab are from sFc, and it includes the Mr. Home launcher, essentially a version of ADW Launcher with some additional mods. It includes nemesis2all's OTB TouchWiz kernel, as well as the voltage control app. (see also: Pick-N-Pack)
Kernel - Framework. Specifically, it is a bridge between the applications in an operating system and the processing components of the hardware. In short, it connects the software to the hardware.
In the context of an Android device, because the hardware drivers are contained within it, it can be replaced with a different kernel to change the way your device's hardware functions; overclocking, undervolting, sound and graphics tweaks, and so on are all customization options offered by using a custom kernel.
For additional information, see the XDA ROM vs. Kernel wiki page.
Kies - Software. The Samsung-created flashing software designed for flashing official Samsung/US Cellular-created ROMs to your device.
Lagfix - Mod. The process by which a Galaxy S device is sped up, typically by tweaking or entirely replacing the file system.
Samsung chose to utilize the RFS filesystem on the Galaxy S, but as a result, the way in which the device access the file system is notably slow. Some lagfixes will encapsulate an Ext2-based filesystem within the RFS filesystem, but since part of the filesystem is still RFS (not to mention that this method wastes a large portion of memory), it is not optimal.
The preferred Lagfix method is the Voodoo custom kernel, which backs up the device's data to the SD card, erases the RFS filesystem and then creates a much more modern Ext4 filesystem, and then writes the device's data back to the newly created filesystem.
Put simply: The older, slower filesystem is replaced with a newer, faster one, and the device operates notably quicker for many users.
Note that users running an MTD-based ROM do not need to enable Lagfix (and in fact, cannot disable it), since the ROM is build to inherently use Yaffs2/Ext4 filesystems.
WARNING: It is nearly always recommended to DISABLE LAGFIX when flashing your device. There may be times when this is not needed, but it is best practice to be prepared to disable this when flashing anything to your device. Flashing anything to your device while any Lagfix is enabled can result in soft-bricking your device.
MIUI MTD -
MIUI - Custom ROM.
Author: many various authors and porting contributors.
Originally designed for the Nexus One and HTC Desire, later ported to many other devices, including the Mesmerize and Showcase by way of the Fascinate port.
Platform Info: Android 2.3 (Gingerbread), AOSP based.
Kernel: MTD-compatible AOSP Kernel included. Non-lagfix Voodoo features supported.
Originally a Chinese-developed ROM based on AOSP, this unique Custom ROM is a visual blend of AOSP and Apple's iOS, all the while delivering the fast and powerful AOSP performance. Some parts of the ROM may still be in Chinese (most notably online themes), and some users have complained about an increase in battery usage; also, not all features are currently working for the Mesmerize-specific port (as with any AOSP build for the Mesmerize). As with iOS, there is no App Drawer, and any app downloaded is immediately displayed on one of the main screens. Deleting the icon will uninstall the app. However, folders like those in iOS are also present to allow for app sorting. There is also extensive theming support available for MIUI directly accessible from the Theme Manager app, allowing the ROM to be very highly customizable without rebooting or reflashing.
No definition of what "MIUI" stands for as an acronym was available after extensive research; it is thought by some that the name is not actually an acronym, but instead possibly a phonetic name pronounced as either "My UI" or "mee-oo-ee".
Nandroid - App, now Genericized Trademark. A Portmanteau of the terms "NAND Backup" and "Android". The original app, called Nandroid Backup, performed complete NAND backups, and the term "Nandroid" has simply become the colloquial term to refer to a NAND backup (in the same way one might make a Xerox--a photocopy--or ask for a Kleenex--a facial tissue). (see also: NAND Backup)
NAND Backup - Process. Capturing a complete system backup, called an Image, of the contents of the main OS partition of the onboard storage memory of an Android device. Note that this DOES NOT backup the Kernel or Recovery. NAND Flash Memory is the specific type of flash memory commonly used for USB drives, SD cards, Solid-State Drives, and other such non-volatile memory consumer products.
No AM/PM - Mod. Similar to No-Clock, but removes the "AM/PM" notation from your status bar (the area at the top of your screen) as some prefer to see the time in the top right, but want to conserve space in the status bar by removing AM/PM.
No-Clock - Mod. Removes the clock from your status bar (the area at the top of your screen) as some prefer to rely on their widget clock or other preferences.
ODEX - Process. The process (usually done automatically when an APK is run by the Dalvik virtual machine) by which the Dalvik cache of an APK or ROM is separated from the actual executable in order to more quickly run the App. Lets the app run faster, but since not all of the code is contained within the APK, makes it harder to develop or edit the APK. Stands for "Optimized Dalvik Executable. (see also: Deodex, Dalvik)
Odin - Software. A device-flashing utility for Windows created by Samsung, used for flashing ROM images and other OS components onto your Samsung device. Utilizes TAR files, and occasionally also PIT files depending on what you're flashing. Though many prefer it to flashing via recovery when given the option, Odin can potentially flash images to your device when Recovery cannot (or your recovery is damaged). Leaked releases from Samsung/US Cellular will most often be found formatted for Odin flashing.
CWM Orange -
"Orange" Recovery -
Orange Recovery - Framework. The original custom Recovery as installed by the ROM Manager app. Note that Galaxy S devices running Froyo should not typically be running Orange Recovery, as it is not fully compatible. However, devices running MTD ROMs will use CWM Orange 4.x, which is normal (and the only custom recovery available that supports the MTD file formatting). (see also: ROM Manager)
PnP -
Pick-n-Pack - Custom ROM.
Author: Phidelt82.
Designed for Mesmerize.
Platform Info: Android 2.2 (Froyo), TouchWiz-based, both EC10 and EE19 builds.
Kernel: Kernel not included. Use a TouchWiz-based kernel.
This ROM is specifcally designed to allow the user to "Pick" and choose which Samsung- and US Cellular-designed apps they wish to have loaded on their device, "Pack" them into a flashable ZIP file, and flash that ZIP onto the phone as a Mod pack. Also includes Mods such as Puzzle Lock and Accurate Battery Mod.
Port - Verb. To bring a mod, ROM, theme, or other component from one device to another.
In the context of the Mesmerize, this is most often done with components to or from the Fascinate or Showcase, as they are similar/nearly identical models, but occasionally from other phone models as well. (See also: Fascinate, Showcase)
Puzzle Lock - Mod. A mod which alters TouchWiz itself by removing the standard "slide glass to unlock" screen and replacing it with a puzzle lock screen (while using a stock ROM, this is normally only seen if you miss a call or message while your phone is locked)
Recovery - Framework. A Pre-boot environment similar in appearance to BIOS on a PC which allows you to recover your device by, at the very least, flashing back to the original stock configuration (factory reset). Also refers to the partition of any Android device where the data to perform recovery options is stored. Because it is a partition separate from the actual Android operating system, it may or may not be affected by changes or customizations you make to your device. Flashing stock ROMs will always change your Recovery to a stock Recovery. Custom ROMs may or may not alter your Recovery. A common example of a custom recovery would be CWM Recovery.
CWM Red -
"Red" Recovery -
Red Recovery - Framework. This refers specifically to an altered version of Clockworkmod (aka CWM) 2.5.x specifically designed to be compatible with the Galaxy S device. Note that ANY Mesmerize user running Froyo (Android 2.2) can only run either Red Recovery, or a Fascinate/Mesmerize custom 3.0.x CWM, as the original Orange Recovery as installed by ROM Manager is not compatible with the Mesmerize based on the type of scripting used. Note also that Mesmerize users running Eclar (Android 2.1) can also opt use Red Recovery.
Note that this recovery has been partially deprecated in favor of modified CWM recoveries based off of CWM 3.0.x, since more or less all modern ROMs and Mods use the Edify scripting language.
ROM - Android Image. A shortening of the term "ROM image". The ROM (Read-Only Memory) image is at least a full install of the OS framework, and may or may not include a Kernel or Recovery as well.
Official or "stock" ROMs include all three frameworks (OS, Kernel, and Recovery), as well as apps and services pre-installed, including those from both the device manufacturer and cellular service carrier (in the case of the Mesmerize, that would be Samsung and US Cellular, respectively).
Custom ROMs are typically based on Official ROMs, but have had one or more components altered or replaced; Custom ROMs may or may not include a kernel (stock or custom), a recovery (again, stock or custom), as well as additional apps and services installed, or even the removal of the apps and services normally installed by the manufacturer and carrier. Most frequently, a custom ROM will not include a recovery as it is typically flashed to the device while booted to recovery, but whether a kernel is included is largely up to the author. A thread containing a custom ROM would ideally state whether it contains a kernel, if which.
For additional information, see the XDA ROM vs. Kernel wiki page.
ROM Manager - App. The app that, among other things, installs the original Clockworkmod. Also allows for other functionality for ROMs, recoveries, recovery boot behavior, and so on. The original CWM that ROM Manager installs has orange text, and is therefore referred to as "Orange" recovery (this, and the app's icons, and the main website directly reference the film "A Clockwork Orange").
NOTE: At this time, if you're using a Samsung Galaxy S device that has been upgraded to Froyo (Android 2.2), you SHOULD NOT have ROM Manager installed, as the "Install CWM" and "Reboot to Recovery" options within that app are NOT compatible with Galaxy S devices running Froyo. You should be using the "Red" recovery instead, or a modified 3.0.x-based CWM recovery. It's worth noting that the Red recovery also works with Eclair (2.1) (this has not been tested with 3.0.x-based custom CWM recoveries). On the other hand, users running MTD-based ROMs will find CWM Orange 4.x flashed to their device, as it is the only custom recovery that supports MTD file formatting. As a result, certain MTD-based ROMs for the Mesmerize (and Fascinate and Showcase) are now fully supported by ROM Manager, so users using those ROMs can now install CWM 4.x via ROM Manager. (see also: Clockworkmod, Red Recovery, Orange Recovery)
Root - verb. To provide Superuser access to an Android device. Some apps require your device to be rooted in order to function. Term originated from from the Unix term of the same name, which described the user given full and total permissions over a Unix system (similar to Administrator on a Windows system). (See also: Superuser)
SGS - Acronym. Short for "Samsung Galaxy S".
Showcase - Device Model. Specifically, this is the model of Samsung Galaxy S available for Cellular South customers. Because its model number is SCH-I500, as the Mesmerize's model is, certain components such as mods, ROMs, and themes have been more readily ported between the two models. Potentially even closer to the Mesmerize than the Fascinate. NOTE: Always ensure the Showcase component you wish to use on your Mesmerize is actually compatible, some are not.
Su -
Superuser - user permission, also app.
User Permission: Another name for a Root user, someone with full and complete access to all portions of an OS. (See also: Root)
App: An app that allows you to control which apps may request Superuser access, view a log of apps that have done so, and control the way in which both you and other apps interact with the device while having Superuser permissions.
Three Finger Method -
Three Button -
Three Button Method - Process. The manual process of entering recovery mode. First, power the phone off. Then, simultaneously hold down the Volume Up, Volume Down, and Power buttons. The Samsung logo will appear; continue holding the buttons. Once the Samsung logo disappears and reappears again, release the buttons. You should now be in recovery mode.
As an alternative, you can use the following method if the first does not work. Once again, power off the phone first. Then, Simultaneously hold down the Volume Up, Volume Down, and Power buttons. The Samsung logo will appear; slide the finger on the volume button down so that it's only holding down the Volume Down button. The Samsung logo should disappear and reappear. Release the buttons. You should now be in recovery mode. Note that this does not work for users running an MTD-based ROM, since such a ROM flashes CWM Orange 4.x, which does not recognize this key combination. (see also: Recovery)
TouchWiz - Framework. The default Samsung-created graphical user-interface, or Shell, that provides touch sensitivity, app launching, and other user interface functions on all stock Galaxy S devices (and other specific Samsung devices). Can be replaced with other Shells. (see also: TWLauncher)
TWLauncher - App. The default TouchWiz Launcher; the actual application part of TouchWiz. Alternatives such as Launcher Pro, ADW Launcher, and so on are available on the market.
UV - Verb. The term is a shortening of "Undervolting", which is the process of providing the device with less power than it was originally designed to receive in order to achieve better battery longevity. This is done within the kernel.
Voodoo - Framework. A series of custom kernels designed specifically for the Galaxy S device and originally created by Supercurio. Voodoo's primary features are to allow the user to enable Lagfix, as well as color "temperature" (some Galaxy S devices apparently have a slightly blueish tint to them), and sound tweaks. Kernels that are voodoo compatible (i.e. not specifically by Supercurio but including the code that enables those functions) may also include functions such as BLN, UV, and so on. (See also: BLN, UV, Lagfix)
Credits
Names listed alphabetically.
Authors: Bdemartino, ChromWolf.
Editors: Bdemartino, Phidelt82.
Sources: XDA Forums, Wikipedia.
Term Contributors: butcher1966 (bootloader), getosquirrel (for Download Mode and Three Button Method), Legato525 (for BLN), Phidelt82 (for ESKBL, GAPPS, and sFc history)
Special Thanks: Sd73ta, for his additions to the Glossary XDA Wiki page and the ROM Vs. Kernel XDA Wiki page. Supercurio, for his explanation on the Project Voodoo site for how Voodoo changes the file system. Svetius, for his work on the Acronyms and Glossary XDA Wiki pages.
Post reserved for future additions.
...I figure this'll be a work in progress. I've had a couple people edit this so far, and it'll only get better as the community tweaks it, adds to it, and corrects it. It'll always be evolving, but especially now. So if you see something you think is incorrect, post constructively, and I'll do my homework and fix up what needs fixing.
In the end, I just hope it helps people get a better beginner's understanding of Android, and the Mesmerize in particular; a one-stop-shop for all the terms. Hope it helps.
o/
Excellent glossary ChromWolf!
Thanks to all that helped!!
Sent from my SCH-I500
Thanks for handling this ChromWolf! I pm'd jerdog to get this stickied.
Great work man!!!
How bout adding three button method and download mode?
getosquirrel said:
Great work man!!!
How bout adding three button method and download mode?
Click to expand...
Click to collapse
Adding.
ChromWolf said:
Adding.
Click to expand...
Click to collapse
Just a little addition to the 3 button method, it works best if you hold all 3 buttons until you see samsung, then drop your thumb down to just holding volume down the rest of the way(if holding with the hand placed on the back of the phone palm facing you, thumb on volume side and forefinger on power). sometimes it's easier to do with the back case off (makes the buttons more exposed)
bdemartino said:
Just a little addition to the 3 button method, it works best if you hold all 3 buttons until you see samsung, then drop your thumb down to just holding volume down the rest of the way(if holding with the hand placed on the back of the phone palm facing you, thumb on volume side and forefinger on power). sometimes it's easier to do with the back case off (makes the buttons more exposed)
Click to expand...
Click to collapse
I can certainly agree on it being easier with the case off, but I've not had any troubles just holding both Volume Up and Volume Down... Maybe I just have big hands though. The process you're describing seems more of a 2-button method though. Does it rely on enough pressure being applied to the Volume Down button such that the Volume Up button is still being pressed down, or is it more that you've already hit it for long enough into the process that it doesn't need to be held down anymore?
Sounds like at the very least, I need to update to say it can take a few attempts, make sure you're pressing hard enough for both buttons, and how to properly hold the phone. How have other people fared?
ChromWolf said:
I can certainly agree on it being easier with the case off, but I've not had any troubles just holding both Volume Up and Volume Down... Maybe I just have big hands though. The process you're describing seems more of a 2-button method though. Does it rely on enough pressure being applied to the Volume Down button such that the Volume Up button is still being pressed down, or is it more that you've already hit it for long enough into the process that it doesn't need to be held down anymore?
Sounds like at the very least, I need to update to say it can take a few attempts, make sure you're pressing hard enough for both buttons, and how to properly hold the phone. How have other people fared?
Click to expand...
Click to collapse
When I first tried getting my phone into recovery by holding all 3 buttons the whole time, it wouldn't work - so I asked around and the instruction I posted is what was given to me to assist - and it worked like a charm. Since then - it's second nature for me to do it this way - but if others aren't haven't issues then maybe there isn't a need to reference it
And to answer your question no, the pressure is on both volume up and down (and power) 3 button, then once the samsung screen comes up i slide the thumb down to only holding down - that is what works 100% of the time for me.
Sweet .....
BootLoader ?
I definitely need to do an update again for 3-button, Bootloader, and EC01 Radio. Maybe sometime tonight if reflashing my phone doesn't take too long. Thanks for the suggestion, butcher1966!
Finally had a chance to update the Glossary; added Bootloader and EC01 radio, as well as updating a few terms like Three Button Method and MIUI, and also a few minor cleanups.
Very nice work, very well done and thought out. Thank you.
This is an amazing guide! Well done, it helped me alot when I was confused on a few things. Thanks for making this!
Updated to add Heinz 57, and update sFc, plus a couple "additional" spellings to enhance the browser search functionality.
Wow, very nice!!!! This is an excellent reference esp for those that don't get here that often and can't keep up with the devs! Thanks much!
How about the new AmendtoEdify and thenewer red cwm?
butcher1966 said:
How about the new AmendtoEdify and thenewer red cwm?
Click to expand...
Click to collapse
Sorry I haven't gotten back to this sooner! I've had my head buried in MIUI builds (which haven't gotten anywhere thus far)...
I can definitely update the CWM entry, and should also note that themed CWM recoveries are available (I'm rocking the H57 green recovery, because green is cool).
I'm unsure if I should include Amend-to-Edify though; that's something only an advanced user would really need to care about, and this is really more geared towards "advanced beginners"... That said, I dislike the idea of just arbitrarily excluding information based on my own judgments of its validity to the target audience, so I think I'll open this one up to the floor: For those still watching, do you think the intelligent-but-not-yet-experienced user should know what Amend-to-Edify is?
If you were to add it I think it should go into a section labeled advanced with a label saying if you don't know what amend and edify and cannot fix a bricked phone. This may not be for you. As someone who does tech support there are times that you should withhold info. So really its up to you. I don't think it would hurt but then again I don't know the possible worse case scenarios from someone like me experimenting with it as well as don't want to see a influx of post to fix things that really should have never been broke in the first place. That goes back to if you cannot fix a bricked phone this is not for you deal.
Anyway those are my thoughts on it.
Tap-a-Talked

Read this before posting. MT4G Slide Compendium

The Almost Complete Compendium for MT4G Slide (Read This before Posting)
Note as of 12/22/2011 the ota update is not rootable (H boot 1.45.0013)
and s-off cannot be obtained. If you updated with s-off it is possible to revert back. [url='http://forum.xda-developers.com/showthread.php?t=1421258"] Reference thread [/url]
Also, people who used HTC unlock and have s-on will have trouble flashing roms that are not gingerbread based.
Table Of Contents
1. XDA Lingo
2. MT4G Slide Specs.
3. S-Off, Root, Recovery, Backup, Unroot
4. ROMS, Kernels, Fixes, Mods
5. Network (Unlocking, Backtrack)
6. Apps
7. Development Section
8. Credits
Section One
READ FIRST
READ SECOND
READ THIRD
This is really helpful if a person is new to the forums. Some Lingo, Jargon!!
S-Off: This term is used when describing the security radio. With S-on only signed ROMs may be flashed, when S-off unsigned ROMs may be flashed IE custom ROMs.
Root: This means the user will have unrestricted full access to almost the entire system stack. Another way of describing it would be, having administrator rights on a windows computer
Custom Rom: This stands for “read only Memory”. With Android OS, a custom rom allows you to change things that were un-changeable.
Hybrid ROM: When referring to the MT4G Slide. This ROM contains both HTC Sense and AOSP Theme.
(Unlocked)Bootloader: Loads the core operating system. Unlocked bootloader means users can modify what files the bootloader opens.
H-Boot: Hitting power+volume down after a power down or restart brings up the H-boot (skating androids). This is used to get into recovery and can also be used to flash files using the proper file name.
Fastboot: Fastboot is the name of a tool used to manipulate the flash partitions of the Android developer phone. It can also boot the phone using a kernel image or root filesystem image which reside on the host machine rather than in the phone flash
Zipalign: Is an archive alignment tool. The benefit of zipalign is a reduction in the amount of RAM consumed when running the application.
A.O.S.P "Android Open Source Project": Pure google source untouced by carriers and phone manufacturers.
SDK ADK: “Software Development Kit”” Android Development kit” A suite of tools that helps developers create software for the Android OS.
ADB: “Android Debug Bridge” Allows a user to control and interface with the Android OS.
SBF: System binary file. “I sbfed back to stock” Meaning, I reverted my phone back to stock using a system binary file with a stock image.
Kernel: This is the center of the computer operating system. It provides basic services to the other parts of the system.
Overclock: Forcing the processor to increase its clock rate (therefore more cycles per second). Normally used to get better performance.
Underclock: Reducing the processor clock rate (less cycles per second). This is used to get battery performance and increase processor life.
Undervolt: Lowering the voltage while still maintaining clock rate. This is used to help save power and heat reduction.
Frosted/Defrost: A term used when freezing (frosted) an application or unfreezing (defrost).
Bloatware/Debloat: The many useless applications that carriers add onto the stock os (bloatware). Debloat means that the bloatware has been removed.
Master Subsidy Lock (MSL): Many phones are sold below cost, (at a loss to the carrier,) with the expectation that the money will be recouped in the cost of the monthly service plan. The up-front loss that is later recouped is called a Subsidy.For this to work financially for the carrier, the user must not buy the phone and then use it with a different carrier.The carriers slap on a MSL so the user cannot switch service providers.The term "unlock" means to get the MSL code to free the phone from the carriers lock.
Section Two
MT4G Slide Specs.
Phone specs:
Phone Scoop
[url='http://www.t-mobile.com/shop/Phones/cell-phone-detail.aspx?cell-phone=T-Mobile-myTouch-4G-Slide-Black"]T-Mobile[/url]
HTC
Snapdragon
"Best Still Image shooter" according to PC World
T.V Out
Section Three
S-Off, Root, Recovery, BackUp.
S-Off and Root
How to find out S-On or S-Off / Booting Into Hboot
Radio - Necessary to recover botched radio install Stock Radio Another Stock Radio Thread
S-OFF for Retail (S-ON) Devices, NOTE ADDED 8/17/11
Revolutionary's site also has the root zip that is needed. Does this give me root?
Boot into H-boot, then recovery, use camera button and select "install zip from sd card". When zip is done reboot phone, check superuser.
PERMANENT-ROOT (NEW!) & Temp-Root (v2) for any MT4GS (Windows) Great Guide with very good information!
Recovery
[RECOVERY] Official CWM Recovery v5.0.2.7
Thanks Undeadk9 for install guide.
Also, if using an older ROM version of Sense On Crack, Senseless, Virtrous, etc both the system and data need to be mounted.
ROM Manager is also supported for flashing CWM Recovery. Simply download ROM manager, click flash recovery at the top. Then select our phone. Follow the directions.
Directions:
1. Make Sure Your On a WiFi connection.
2. Go here: http://www.clockworkmod.com
Go to recoveries, Download v5.0.2.7 recovery for doubleshot
3. Download Term Emulator
4. Using root explorer, move the recovery image to /data/local, then mount System r/w in root explorer, then press the home button.
5. Then open Term emulator and this....
su
dd if=/data/local/recovery-clockworkmod-5.0.2.7-doubleshot.img of=/dev/block/mmcblk0p21
Press ENTER
6. It should say transferring bytes blah blah
7. Open ROM manager and press reboot into recovery.
8. If it says v5.0.2.7 then You are done.
ClockworkMod Recovery 4.0.0.9 for the T-Mobile myTouch 4G Slide (MoDaCo edition)
*Older Version*
I took out the terminal emulator post in the thread which is how I upgraded my recovery. The words and numbers must be exact.
here is the OP Thanks
1. Download Recovery 4.0.0.9 from Modaco's website
2. Using Root Explorer, find the file in your downloads folder on the sdcard.
3. Paste the recovery img file into your phone's /data/local folder.
4. In terminal emulator, first type "su" and then type "'dd if=/data/local/doubleshot.clockworkmod.4.0.0.9.modaco.img of=/dev/block/mmcblk0p21" and let it transfer the recovery file.
Re-Cap How To Turn S-Off, Install MoDaCo Clockworkmod Recovery, and Install a Rom For Dummie
Backup (Read and Re-Read this section)
Backups - After Rooting, before ROMing, take this step
Unroot
For The What Ifs
Section Four
Roms!Roms!Roms
Difference between full rom and patch
Basic Installation of a NEW ROM
1. MAKE NANDROID BACKUP OF STOCK ROM
2. REBOOT INTO RECOVERY
3. WIPE DATA AND CACHE
4. FORMAT DATA
5. FORMAT SYSTEM
6. WIPE BATTERY STATS "OPTIONAL BUT HIGHLY RECOMMENDED"
7. WIPE DALVIK CACHE
8. INSTALL ROM
9. REBOOT
10*. LET PHONE SET FOR 5-7 MINUTES.(see below)
*The system is still building symlinks and installing things behind the scenes on first boot of a fresh installation. If you choose to play with it before the 5 minute mark, you risk losing data that has yet to be written. This can lead to buggy performance and issues the DEVS will have a hard time figuring out.
For patches
Backup
1. Wipe cache
2. Wipe davik
3. Flash Patch
4.Reboot
Stock Roms
12/Aug 1.28.531.9 r1 - HTC Doubleshot Stock ROM Rooted and decodexed
Pure Stock Doubleshot, Root/Deodex/Busybox/Opt/Zip
Ice Cream Sandwhich
[ROM][Jan 5 2012] Pyr-o-Ice ICS 0.3.0 alpha (Android 4.0.1) |Camera(photo)|FaceUnlock
Android Open Source Project (AOSP) Roms
CM7
Sense Roms
Virtrous
Crack Injected Sense
BulletProof
Touch 4G Slide DoubleShot Lite
*These Roms Have active Developer support. If I missed a ROM please message or post and I will fix.
Kernels
BoneStock Kernel
Unity V2
Kanged
Fixes, Mods
GPS Fix
Safe Bloatware Removal
Turn off system update for good
*Data Connectivity Fix
*Clutter Cleanup
*indicates stock ROM safe
Section Five
Networking(Unlock,Backtrack)
Unlock:Use method one
Another Way to Unlock the MSL
Backtrack (offensive network secruity)
Section Six
Apps
Good App suggestions and reviews
Section Seven
Development Section
This section is intended for DEVS and beginner DEVS. If you have a question ask before doing something.
MT4GS Stock App Developers Reference
Partions - memory address listing
ADB,SDK,JDK
Fastboot.Exe is in the attachments incase you did not get it. Put the .Exe in platform-tools folder.
Blue61x's Guide to setting up a fresh Dev Computer XP
ADB Workshop by Adrynalyne and Guide by Captainkrtek
Understanding Basic ADB Commands
Dev guide to adb
Key Mapping
Genius button to search
Hardware Key mapping and Flashable zips and requests
LockRing Editing
[How-To] Custom Sense Lockring on the MT4GS - easy step-by-step.Part 1
[How-To] Edit .9.png files for the MT4GS - step-by-step.Part 2
[How-To] Edit Mode10 Files for the MT4GS - step-by-step. Part 3
Tools and Dowloads
MR.Root by XMC Wildchild22 Great scripts!!!
SuperOneClick Root
Section Eight
Credits
I am adding more sections, more links and more information as well as some more jargon.
Pm's welcome for mistakes, more information, etc. ( I am human).
Thanks Blue6IX,Very involved with the creation of this compendium
I thank all the Devs, Mods,end users, supporters and noobs for helping me compile this information. I take no credit for this as it's an orangized Hub for all of our information.
Change Log: 11/02/2011 Added New CWM Recovery, CM7, Mods and Fixes section. Changed name of Unlocking section to networking. Added backtrack.
11/06/2011: Added new terminology.Updated and split the ROM section into aosp and sense roms. Added another way to obtain an unlock code. Added development Section.
11/11/2011: Added new terminology. Added new section to ROM: Hybrid. Added Doubleshot Lite to ROM section. Moved Key mapping section to dev. section. Added ADB section to dev. section. Edits.
11/22/2011: Added new terminology. Added Rom Manager is now supported for flashing CWM. Minor Edits.
12/21/2011: Updated Dev. Section and added fastboot.exe to attachments
1/05/12 : Added ICS Rom section, Added tools and download section, Added Blue's guide and XMC's root tool.
This should help clear up some of the oft-asked questions for people new to the device.
Droidmoder really put a lot of effort into making this happen!
Edit - How did I forget to click thanks on the OP? Dec 14th, 2011
Blue6IX said:
This should help clear up some of the oft-asked questions for people new to the device.
Droidmoder really put a lot of effort into making this happen!
Click to expand...
Click to collapse
Blue6IX,
thanks for your help. You helped more than you think you did!
Blue6IX said:
The system is still building symlinks and installing things behind the scenes on first boot of a fresh installation. If you choose to play with it before the 5 minute mark, you risk losing data that has yet to be written.
The system will serve you, the user, before itself, and will drop from memory things it still needs to write to process your requests. This can result in buggy performance or problems down the line, and lead to frustrating issues that developers of the ROM can't figure out - because no one else will have these problems. Please be advised of this.
Click to expand...
Click to collapse
Added to step ten.
Very nice write up =D.
ekoee said:
Very nice write up =D.
Click to expand...
Click to collapse
Yes, thank you very much! Now the goal is to keep it up to date which will probably turn into more work than you want, but thank you!
unclespoon said:
Yes, thank you very much! Now the goal is to keep it up to date which will probably turn into more work than you want, but thank you!
Click to expand...
Click to collapse
No problem.
Sent from my Crack Injected Doubleshot using xda premium
Great Job!
Suggestion: a section on key remapping? (there was a thread somewhere but never got completed)
Etn40ff said:
Great Job!
Suggestion: a section on key remapping? (there was a thread somewhere but never got completed)
Click to expand...
Click to collapse
I'm going to add this tonight. At work. I have that thread alreay
Sent from my Crack Injected Doubleshot using xda premium
Etn40ff said:
Great Job!
Suggestion: a section on key remapping? (there was a thread somewhere but never got completed)
Click to expand...
Click to collapse
Two threads actually.
Original
Then I made one for requests that people want in flashable zip form:
Requests
So technically, there is no need to 'finish' the first one, and I support my request thread as time allows. It's set up so any dev can come in and handle requests, and there are a few floating around here that would be more then happy to help.
by finish I refer to ekoee's post on shift+alt keys, either it never appeared or i could not find it at the time
Etn40ff said:
by finish I refer to ekoee's post on shift+alt keys, either it never appeared or i could not find it at the time
Click to expand...
Click to collapse
Ah, good catch - i'd forgotten about that with everything else that's been going on.
Wonder if someone will put time into figuring it out?
I bet the answer to that will also lead to the answer for getting other languages supported on the hardware keyboard.
Yeah sorry about that, I haven't had the time to start pulling apart key mappings. Ill make sure to get on it when work settles down.
ekoee said:
Yeah sorry about that, I haven't had the time to start pulling apart key mappings. Ill make sure to get on it when work settles down.
Click to expand...
Click to collapse
I thinking about moving key mapping in the dev section. Wouldn't it be more of a devlopmental thing?
Btw I'm going to refurb the dev sections with links and guides on adk adb and fastboot .
sent from my sense on crack MT4G Slide using xda premium
What does "nandroid" backup mean?
I have backed up with the recovery and I have backed up with ROM manager. What is nandroid?
sandiegoan said:
I have backed up with the recovery and I have backed up with ROM manager. What is nandroid?
Click to expand...
Click to collapse
Nandroid is what clockwork mod calls the actual backup file.
Backup means to create a backup.
Nandroid is the file backup of your system . Hence nan (small) and droid the os. So you can also say you made a small android os .
Ill add this to terminology when I get to it. Hope this helped.
sent from my Agent Orange MT4G Slide using xda premium
Very helpful info, I unrooted, but theunlockr guide stated that this would turn the phone back to S-ON, but it hasnt, i have the stock tmobile rom back on the phone, but HBOOT states I still have S-ON, is this a problem? is there a way to get S-ON again so I can start the root process over? or am is there shortcuts I can take to root now that I have S-off?
I actually do not know. I would assume s on is attainable. Why would you want s on, you can re root without going threw rev again.
Follow the root guide its easy enough.
sent from my Agent Orange MT4G Slide using xda premium
You mean the guide from theunlockr? or another guide? if its another guide please post it? as far as following theunlockr method, in order to gain perm root it stated I have to first boot into recovery, and then flash the ZIP file, but when I try to go into recovery, I get a red exclamation mark, even though I have S -OFF

[GUIDE][VZW Edition]How to root your Galaxy SIII & More!(ROMs/CWM/Stock)

Here is a guide I have put together for the VZW Samsung SCH-I535 Galaxy S3
------------------
This guide contains 7 sections:
Section 1: How to Root/Unlock bootloader/Flash CWM recovery coming from stock 4.0.4 ICS
Section 2: How to flash a Custom Touchwiz 4.0/4.1 rom
Section 3: How to flash a CM10/AOSP/AOKP JellyBean rom
Section 4: How to flash a Custom Kernel
Section 5: How to Odin back to Stock from any rom/recover from a soft brick/flash a stock radio
Section 6: Directory
Section 7: Glossary
-----------------
This Guide Is For The D2VZW SCH-I535 ONLY!! DO NOT ATTEMPT TO FLASH ANYTHING FROM THE I9300 International GS3 Or You Will Hard Brick The Device!!
-----------------
*I am not liable for what you do to your DEVICE!!
*I take no credit for links posted in this thread... This is just a guide or more so a collaboration of different guides all put into one thread!!
*This Guide will not trip your flash counter!! Flashing any custom software via odin will infact trip the flash counter!! Thats why I use these methods and the only thing I use odin is for flashing STOCK firmware Only!!!
-----------------
*** Before going any further I strongly suggest reading and performing this action before flashing any custom roms!!! ***
[HOWTO]Comprehensive IMEI/EFS Backup- http://forum.xda-developers.com/showthread.php?t=1852255
------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Section 1: ( For Windows OS)How to Root/Unlock bootloader/Flash CWM recovery coming from Stock 4.0.4 ICS
*This works with all current Stock 4.0.4 ICS builds...VRALF2, VRALG1, VRALG7, VRALHD, and VRALHE.
*However RootdebugFS does not work for 4.1.1 JellyBean. If you want Stock rooted Jellybean then there are 2 options! .
*Option 1 is to proceed to section 5 and use odin to flash a Stock pre-rooted Jellybean rom. Then follow steps 8-12 from this section for unlocking and flashing a custom recovery.
*Option 2 is to complete this section 1, then proceed to section 2 and flash a Jellybean rom via CWM or TWRP recovery.
Step 1: Download these files to your pc:
Samsung Driver- http://tinyw.in/Fdoz
RootDebugFS- http://goo.im/devs/invisiblek/i535/Root%20Debug%20FS.7z
Step 2: Install samsung drivers to the pc and unzip the RootDebugFS tool to desktop.
Step 3: Connect the device with the oem usb cable to pc.
Step 4: On your device, Make sure USB Debugging(settings/developer options/usb debugging) and Install of Unknown Sources(settings/security/unknown source) is checked.(Also, make sure there are no other android devices, emulators, or any tethering programs running!!).
Step 5: From the PC, Open the Root Tool folder you downloaded in step 1 and Double click "RootDebugFS". press 1 then hit enter.
Step 6: Agree to all of the disclaimers by pressing Y after each one pops up.
Step 7: Once the root process starts DO NOT UNPLUG YOUR DEVICE until it completes!
*Congrats you should now be rooted! Continue following instructions for unlocking bootloader and flashing a custom recovery*
*TAKE NOTE THAT IF YOU EVER OTA UPDATE YOUR BOOTLOADER WILL BE LOCKED*
Step 8: Open up the SuperUser application from your app drawer and make sure the binaries are up to date! You can do this by sliding over to the info screen and selecting update binary.
Step 9: Download the EZ-Unlock app to your device from HERE.(Only use version 1.1 or 1.2 for now as the latest versions have issues!)
Step 10: Open the app and select unlock! Now your unlocked...yup its that easy!
Step 11: Download the EZ-recovery app to your device from HERE.
Step 12: Open app, select CWM recovery, tap the pulldown menu, choose CWM 6.0.1, select flash, then reboot recovery.
Step 13: Congrats you are now rooted, unlocked, and have a custom recovery installed!! If you want to flash a custom rom proceed to section 3 or 4.
*Credit goes to Adam Outler, Noxious Ninja, mmmeff, and all others involved!!!
*(Mac/Linux) users read HERE for Rooting!
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Section 2: How to flash a Custom TouchWiz 4.0/4.1 rom from CWM recovery
**YOU MUST BE ROOTED AND HAVE BOOTLOADER UNLOCKED!**
Step 1: Download one of the roms below to the root of your internal sd card(/mnt/sdcard):
ICS 4.0.4
Bean's Custom Stock-http://forum.xda-developers.com/showthread.php?t=1768209
Rooted Stock VRALHD- http://forum.xda-developers.com/showthread.php?t=1911118
TW JellyBean 4.x
Incubus JellyWiz- http://forum.xda-developers.com/showthread.php?t=1853337
Eschelon's Synergy- http://forum.xda-developers.com/showthread.php?t=1792499
Scrosler's CleanRom- http://forum.xda-developers.com/showthread.php?t=1832070
Puremotives Galaxy Mod- http://forum.xda-developers.com/showthread.php?t=1953008
Beans JellyBeans- http://forum.xda-developers.com/showthread.php?t=1973982
Stock rooted VRBLK3 4.1.1- http://www.androidfilehost.com/?fid=9390214368362234071
Stock rooted VRBMB1 4.1.2- http://forum.xda-developers.com/showthread.php?t=2178482
Step 2: Download and install the EZ recovery App from HERE (If your coming from section 1 and already have a custom recovery, reboot recovery and skip to step 4).
Step 3: Open app, select CWM recovery, tap the pulldown menu, choose CWM 6.0.1, select flash, then reboot recovery.
Step 4: Perform a Nadroid Backup from the "back up/restore" menu(optional but recomended)!
Step 5: Wipe Data/Factory reset, then under the "mounts & storage" menu Format System.
Step 6: Navigate to "install zip from sdcard", then from there "choose zip from sdcard", and finally install the rom you downloaded in step 1.
Step 7: Reboot.
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Section 3: How to flash a CM10/AOSP/AOKP Jelly Bean rom
**YOU MUST BE ROOTED AND HAVE BOOTLOADER UNLOCKED!**
Step 1: Choose and download one of the roms in part A and the file in part B to the root of internal sd card(/mnt/sdcard):
A.
CM11- http://forum.xda-developers.com/showthread.php?t=2558946
CM10.2- http://forum.xda-developers.com/showthread.php?t=2405425
Pac-Man http://forum.xda-developers.com/showthread.php?t=2028443
Eclipse- http://forum.xda-developers.com/showthread.php?t=1934572
B.
Kit Kat Gapps https://plus.google.com/107979589566958860409/posts/FYkuneXi3J7
JB Gapps- http://goo.im/gapps
Inverted JellyBean Gapps- http://forum.xda-developers.com/showthread.php?t=1797292
Step 2: Download and open the EZ recovery app from HERE (If your coming from section 1 and already have a custom recovery, reboot recovery and skip to step 4).
Step 3: Open app, select CWM recovery, then tap the pulldown menu, choose CWM 6.0.1, select flash, then reboot recovery.
Step 4: From CWM recovery, Perform a nandroid backup from the "backup/restore" menu(Optional but recomended).
Step 5: Wipe data/factory reset, then under the "mounts & storage menu" Format System.
Step 6: Navigate to "install zip from sdcard", from there "choose zip from sdcard", and finally install the rom you downloaded in step 1 part A.
Step 7: Again, Navigate to "install zip from sdcard", from there "choose zip from sdcard", and finally install the gapps package you downloaded in step 1 part B.
Step 8: Reboot.
*This same method can be of use to revert back to Touchwiz ICS or JellyBean aswell...no extra steps are needed. Simply wipe data in cwm recovery and flash rom or restore nandroid.
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Section 4: How to flash a Custom Kernel
**YOU MUST BE ROOTED AND HAVE BOOTLOADER UNLOCKED!**
Step 1: Download one of these kernels to the root of your Internal SD Card(/mnt/sdcard):
-------------
TouchWiz ICS 4.0.4 Kernels
Imoseyon LeanKernel- http://rootzwiki.com/topic/31329-imoseyon-test-leankernel-tw-729-v111-kexec/
Scrosler's CleanKernel- http://forum.xda-developers.com/showthread.php?t=1850495&page=2 (DOES NOT work on BEANS)
Morfic's Trinity GST- http://forum.xda-developers.com/showthread.php?t=1874720 (Works on CM9 or TouchWiz)
--------------
ICS & JellyBean Kernels(CM9/CM10/AOKP/AOSP)
Imoseyon LeanKernel- http://rootzwiki.com/topic/32286-kernel-aosp-jb-leankernel-minimalistic-kernel-v02-beta-81312/
Ktoonsez KT747- http://forum.xda-developers.com/showthread.php?t=1853816
Faux (CM9/CM10/AOKP/AOSP)- http://forum.xda-developers.com/showthread.php?t=1905141
---------------
Step 2: Download the EZ Recovery app from- HERE (If your coming from section 1 and already have a custom recovery, reboot recovery and skip to step 4).
Step 3: Open app, select CWM recovery, tap the pulldown menu, choose CWM 6.0.1, select flash, then reboot recovery.
Step 4: From CWM recovery, wipe cache, then navigate to the "advanced" menu and wipe dalvik cache.
Step 5: Navigate to "install zip from sdcard" and then from there "choose internal sdcard".
Step 6: Install the kernel.zip that you downloaded in step 1.
Step 7: Reboot.
*Credit goes to Imoseyon, BMc08GT, Invisiblek and all other devs involved.
*These steps work for any .zip file such as themes, custom boot animations, and what not...just replace the .zip file in step 1 with the one your trying to flash!
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Section 5: How to Odin back to Stock from any rom/recover from a soft brick/flash a stock radio
* If your device is currently running a 4.0-4.2 base and you forgot to unlock your bootloader before flashing a custom rom, you probably were greeted with the yellow triangle....Dont Panic! Simply power off the device and follow directions below. Odin will recover your device!! Make sure to only use a 4.0-4.2 Odin file to restore back to stock.
***NOTE*** If you did not take the 4.3 OTA then do not use the 4.3 files in link below. These will permanently lock your bootloader and you will be limited to using safestrap from here on out.
Step 1: Download and install these files to your pc:
Odin- http://forum.xda-developers.com/attachment.php?attachmentid=1165122&d=1340993443
Samsung Driver- http://forum.xda-developers.com/showthread.php?t=2038555
Step 2: Download one of the Factory Stock roms below to your PC:
*These are Official full wipe versions that will format the internal sd and lock bootloader!!
All Official Stock Builds- http://samsung-updates.com/device/?id=SCH-I535(Only use these files if you have a locked 4.3 bootloader.)
VRALG1 4.0 ICS-http://www.mediafire.com/download/kkhq5wtj4r3fpwf/COMBINATION_I535VRALG1_I535VZWALG1_743127_REV09_user_low_ship.tar.zip(Do Not use this if your device took the 4.3 OTA)
*In the link below are PRE-ROOTED full wipe versions that will lock the bootloader(Thanks Mr. Robinson!!) See section 1. steps(8-12) for unlocking and flashing a custom recovery.
http://forum.xda-developers.com/showthread.php?t=1984436
Please Remember to back everything up to a pc or external sd before flashing!!
Step 3: Power device off, hold the volume down/home/power keys until you see a yellow triangle, then press the volume up key to access "odin or download mode".
Step 4: Open odin and connect the oem usb cable from pc to device. There should be a "comport number" in upper left hand corner of odin indicating communication between the pc & device.
Step 5: Click on the PDA function of odin. Select the stock rom you downloaded in step 2, then select start. This operation should take less than 8 minutes before odin will say pass/reset and your device will reboot.
------------------
*Flashing a Stock Radio with Odin or a Custom Recovery
Download's:
Stock Radios- http://rootzwiki.com/topic/34053-officialmodems-vrlhd-verizon-sgs3-sch-i535-odin-or-recovery-flashable/
Odin Method:
Step 1: Download one of the files above to your pc.
Step 2: Power device off, then hold the volume down/home/power keys until you see a yellow triangle, then press the volume up key to access "download mode".
Step 3: Open Odin and connect the oem usb cable to pc & device, you should see a "comport #" in upper left hand corner of odin.
Step 4: Make sure auto reboot is checked.
Step 5: Click on the PDA function of odin and select the file you downloaded in step 1, select start, should take roughly 1min, then odin will say pass/reset.
Step 6: Your device should Reboot.
CWM or TWRP Recovery method:
Step 1: Download files A and B(optional) to the internal sd.
A) Choose a Recovery flashable radio- http://rootzwiki.com/topic/34053-officialmodems-vrli5-verizon-sgs3-sch-i535-odin-or-recovery-flashable/
B) RPM.zip(Optional)-
* A great explanation about RPM cand be found HERE
VRABLI5- https://app.dumptruck.goldenfrog.com/#p/_DeLB5rDRb
VRABLJ1- http://myandroidfiles.com/beanstown106/VRALJ1.rpm.zip
VRABLK1- http://myandroidfiles.com/beanstown106/VRBLK1.rpm.zip
VRABLK3- http://www.androidfilehost.com/?fid=9390214368362234078
Step 2: Reboot recovery via the power menu or power off and use the three finger method.
Step 3: Select install zip from sd and flash the radio.zip you downloaded in step 1A.
Step 4: Slect install zip from sd and flash the rpm.zip you downloaded in step 1B.
Step 5: Reboot.
Section 6: Directory
[APP][MOD] MOBILE ODIN- http://forum.xda-developers.com/showthread.php?t=1347899
[APP][MOD] SIII AOSP Camera- http://forum.xda-developers.com/showthread.php?t=1746611
[APP][MOD] AC!D Audio Technology | v4.0 (22.10.12)- http://forum.xda-developers.com/showthread.php?t=1883262
----------
[GUIDE] Unsure about your ROM choice- http://forum.xda-developers.com/showthread.php?t=1950824
[GUIDE] Verizon Galaxy SIII Downloads List- http://forum.xda-developers.com/showthread.php?t=1850506
[GUIDE] Set up Verizon Galaxy S3 as World GSM Phone (confirmed working)- http://forum.xda-developers.com/showthread.php?t=1809314
[GUIDE] Enable UMS Mode for External SD Card- http://forum.xda-developers.com/showthread.php?t=1785243
[GUIDE]Google Wallet - Everything you need to know before you flash or root- http://forum.xda-developers.com/showthread.php?t=1764428
[GUIDE] for dual booting CM9- http://forum.xda-developers.com/showthread.php?t=1774795
[GUIDE][HOW TO] Edit Earphones Connected-http://forum.xda-developers.com/showthread.php?t=1782155
----------
[HACK] for removing wifi reminder-http://forum.xda-developers.com/showthread.php?t=1770622
[HOW-TO] Unbrick your soft bricked Galaxy S III- http://forum.xda-developers.com/showthread.php?t=1840030
[How To] Backup and restore your IMEI / MEID / EFS Data- http://forum.xda-developers.com/showthread.php?t=1791291
[How To] invoke self hardware test-http://forum.xda-developers.com/showthread.php?t=1767247
[HOWTO]Comprehensive IMEI/EFS Backup- http://forum.xda-developers.com/showthread.php?t=1852255
----------
[MOD][VRBLK3] PDroid Privacy Protection- http://forum.xda-developers.com/showthread.php?t=2043699
[MOD]AOSP Lock Screen with Toggle- http://forum.xda-developers.com/showthread.php?t=2002620
[MOD]Super Simple 5 minutes Wireless Charging Mod for Samsung SG3- http://forum.xda-developers.com/showthread.php?t=1877191
[MOD]Enable wifi in notfication bar- http://forum.xda-developers.com/showthread.php?t=1775235
[MOD]App2ExtSD2 [Works for all U.S. Galaxy S3!]- http://forum.xda-developers.com/showthread.php?t=1849860
[MOD] Latest Google Wallet (10/23/12)- http://forum.xda-developers.com/showthread.php?t=1810040
[MOD]AGPS Patch Galaxy S III 3.1 & 2.2 | NEW SIII SPECIFIC BUILD | Tentative Support - http://forum.xda-developers.com/showthread.php?t=1880411
[MOD] OTA updates - keep root, custom recovery, unlocked bootloader and Google Wallet- http://forum.xda-developers.com/showthread.php?t=1964502
----------
[OFFICIAL] Tips and Tricks thread-http://forum.xda-developers.com/showthread.php?t=1732018
[OFFICIAL][MODEMS] Verizon SGS3 (SCH-I535)- http://forum.xda-developers.com/showthread.php?t=1788313
----------
[ROOT][TOOL] Root the Verizon GSIII without flashing-http://forum.xda-developers.com/showthread.php?t=1792342
[ROOT][TOOL][2012-09-12] SuperSU-Version_Debugfs: Root VZW SGS3 w/out Flashing ROM- http://forum.xda-developers.com/showthread.php?t=1883984
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Section 7: Android Glossary
Download Mode - This is a setting in which you will put your phone when using Odin. There are other ways, but most noobs will reach download mode by powering down, removing the battery, and holding volume down while plugging the factory usb cord into the computer and phone. Odin can only communicate properly with your phone if the phone is in download mode.
F. Reset Time - This is a check box in Odin. It's not clear that anyone knows the exact details of what it actually does, nor is it clear what will happen if you leave it unchecked vs checked. It seems to reset some arbitrary counter in your phone. As a general rule, you can either follow the instructions of whatever guide you're using or just leave the checkbox how you found it.
Fast Charge - This is a feature on some ICS ROMs that can be turned on or off. When enabled, it allows your phone to draw as much charge as possible regardless of the charging source. Without fast charge, your phone will place artificial speed limits on charging when plugged, for example, into the USB slot on your computer. Fast charge bypasses these limits, letting your phone believe it is always plugged into a wall charger. It is worth noting that your phone will not be recognized by your computer as a USB device when fast charge is enabled. It will only charge.
FC - Force Close - This is when an app stops working unexpectedly. This can happen to both rooted and unrooted phones. It doesn't cause any damage to the phone. In most cases, the app can just be opened right back up. It seems to depend on a lot of factors, including the quality of the app itself. ROMs and kernels that experience very few FCs are said to be "stable."
Flash - This is a term used to describe the installation of software onto your phone. It refers to fundamental changes in your phone's operating system. It is different from just installing an app from the Marketplace (Google Play). Commonly, people will flash ROMs, kernels, patches, and radios. There are basically two ways to flash new software onto your phone:
1. Odin
2. CWM Recovery (or a comparable recovery program)
Freeze - There are two meanings in general use. One might use this term to refer to his or her phone becoming unresponsive. More commonly, though, it refers to a special ability of a program called Titanium Backup. This program can be downloaded from the Android Marketplace (Google Play), but it requires a rooted phone to work. When Titanium Backup is used to freeze an app or process, that app or process is essentially gone from the phone. It won't show up in the app drawer, and it won't be running in the background. The difference between freezing and uninstalling, though, is that anything frozen can be quickly "thawed," also with Titanium Backup. With the touch of a button, the missing app or process is right back where it used to be. This is a convenient way for newly rooted users to test the waters of debloating.
Gapps - Google Apps - When flashing custom ROMs, the apps on the phone are usually deleted. As an alternative to going to the Marketplace (Google Play) and re-installing all the favorites (Google Maps, Google Talk, Google Voice, etc.), many devs have packaged these into a tidy zip file that can be flashed via CWM. Why don't they just put the Google Apps in the ROM, you ask? Custom ROMs and Google Apps get software updates at different rates, so keeping the two separate allows users to always have the most up-to-date version of each. On MTD ROMs such as CM7 or anything ICS, you generally must flash the gapps package to get the Android Marketplace (Google Play).
GB - Gingerbread - Android 2.3. Google likes to name its Android releases after sweet foods. Most of our stock phones are running on this release of Android. There are numerous ROMS and kernels compatible with Gingerbread. These are a good starting point for newly rooted users, as they will feel quite familiar.
Github - This is a web-based service where developers can post their code. Depending on the situation, their code can be accessed by other users, modified, or just shared with the world. The site encourages the kind of open source development for which Android is famous.
Governor - This refers to the type of logic your phone uses to control how fast its processor ramps up when needed or slows down when not. The choice of governor can influence overall performance and battery life. The governor can be selected using an OC/UV program such as Voltage Control or NS Tools. No one governor is right for everyone. The fun is in experimenting. Here are some examples and brief descriptions:
performance: Keeps the processor always ramped up to to maximum; useful for benchmarking
ondemand: Rapidly ramps up the processor when needed; gradually slows it down when not needed
conservative: Similar to ondemand, but ramps up more slowly
userspace: The user can define the parameters (for advanced users only).
lazy: This was developed specifically for Android by xda dev Ezekeel. He states it is an enhanced version of ondemand, tuned to our phones' capabilities. Don't be fooled by the name. He tested it with numerous processor-intensive applications.
interactive: Uses a logic to try to predict how quickly it needs to ramp up processor speed, attempting to balance battery life and performance
interactiveX: A tweak on interactive (by dev imoseyon), which locks the processor at the minimum speed when the screen is off
smartass & smartassV2: Modified interactive governors by dev erasmux, they use logic to determine how quickly to ramp up or slow down; designed to optimize battery life without sacrificing performance.
powersave: This keeps the processor always set at the minimum frequency. The name may be a bit misleading, as certain processes will just take longer, using up more battery.
Heimdall - This program is similar to Odin. It was created by an Australian software company called Glass Echidna. It can be used to flash files onto your phone. Some users prefer this program over Odin. Heimdall can be used with Mac computers, whereas Odin can not. Many high level users regularly use both Heimdall and Odin.
ICS - Ice Cream Sandwich - Android 4.0. Google likes to name its Android releases after sweet foods. It comes pre-installed on the Samsung Galaxy Nexus from Verizon. Several developers have created ways to install ICS on the Samsung Fascinate.
init.d - This is a type of script used by developers when they modify Android code. You hear the term a lot because modifications using this type of script have far-reaching effects in the overall performance of the phone. High level users (who aren't quite devs) can even insert bits and pieces of init.d scripts to make minor tweaks to their phones.
Inverted - By default, most Google apps consist of a white screen with dark lettering. Inverting changes this to a dark screen with light letters. There are several advantages to this. Beyond the aesthetic advantages, it tends to be easier on the eyes in low light situations and reduce battery consumption. Inversion is done by talented individuals called themers.
I/O Scheduler - This refers to the type of logic your phone uses to order and process read and write requests to your phone's hard drive. There are several types, which are listed below, but there is no magic bullet. The joy is in finding the one that works for you in terms of performance and battery life. It is worth noting, though, that certain schedulers were designed to be used with mechanical rotating hard drives, taking the drive's rotational position into account. This does not apply to our phones, which use solid state drive technology. A scheduler can be selected by using an OC/UV control program such as Voltage Control or NS Tools. Specific descriptions are beyond the scope of this glossary, but simple Internet searches can expand on any of schedulers listed.
Examples: noop, deadline, cfq, bfq, sio, vr, bfs
* In the absence of a dev's recommendation, if you don't feel like reading up on the subject, you can leave the scheduler at the default or choose noop or sio.
JB - Jelly Bean - Android 4.1. Google likes to name its Android releases after sweet foods. This is the latest version of Android to hit the streets, and devs are flocking to it , making all JB development new and exciting.
Jig - This is a tiny Frankensteinian device made of a small chip, a transistor, and the tip of the little micro-USB connector that you plug into your phone to charge it or attach it to your computer. When your phone will not go into download mode through normal means, putting a jig into the phone when the battery is in will make your phone go into download mode. You can make one yourself or buy one online for less than $10.
Kang - Generally used as a verb, this means to take bits and pieces of someone else's coding and to then integrate it into your own. Granted, noobs won't be doing this, but devs do it all the time. For the most part, this is considered a welcome practice among friendly devs, provided it is done correctly and politely. Kanging often serves to better the community as a whole. The key for devs is to give credit to the other devs from whom they have kanged.
Kernel - This is one of the two main components (ROM being the other) of the software running on an Android phone. It is the piece of software that connects the hardware (screen, softkeys, vibration, speakers, etc.) to the other software components. An unrooted phone comes with a stock kernel. It is stable but somewhat slow. Practically speaking, installing (flashing) a custom kernel will make your phone feel much faster and smoother as it moves through screens and opens apps. Generally speaking, installing a new kernel will not change the basic appearance of your phone or erase any of your phone's information. Custom kernels can also unlock several abilities of rooted phones. Examples include:
-wireless tethering (ignoring that pesky $30/month charge from Verizon)
-control over how and when the softkeys at the bottom of the screen light up
-overclocking/undervolting
-voodoo lagfix (This only applies to phones with BML-based ROMs. MTD ROMs don't need lagfix.)
-custom boot animations
Lean Kernel - Created by imoseyon, He intentionally leaves out a lot of the "bells and whistles" to keep the experience simple, smooth, and fast. Imoseyon works with several phones, so it is imperative that you have the correct version of Lean Kernel, the one appropriate for your phone.
Linaro - This is a team of software engineers developing open source software for numerous platforms, particularly as it relates to getting maximum bang for the buck from systems with memory and hardware limitations. For our purposes, many Linaro modifications are making their way into our custom ROMs, promising increased speed and responsiveness.
Logcat - This is a log of all of the processing activity your phone did over a certain period of time. This is useful for bug reporting, as devs can examine logcats and attempt to determine the source of the error(s). Many threads in the development forum request logcats to go alongside any bug reports. A logcat can be generated through adb, and there are also some apps that will do it for you. Random complaints aren't terribly useful for devs, but logcats generally are. This classic cartoon illustrates how many devs feel about disorderly complaints about their work, even though most are far too polite to say anything.
Milestone - Devs are always trying to incorporate the latest and greatest features into their ROMs. The add-ons are incorporated as parts of new releases, or "builds." This is what makes development exciting, but it also leads to bugs. Milestone builds occur when the devs sit back, roll up their sleeves, and work the bugs out of all the awesome features they've crammed into their work. The milestones are considered the relatively safe and stable builds. When installed correctly, they rarely experience major bugs.
MIUI - This term is a transliteration of a Chinese name for a special customization of Android actually developed in China. MIUI ROMs can be installed on the Fascinate. They change the look and feel of the Android system, moving it closer to something resembling iOS, the iPhone's operating system. A lot of custom development has been done with the software code from the MIUI system. Many devs will integrate bits and pieces of MIUI into their own ROMs. For example, the TSM Resurrection ROM allows you to use the MIUI battery indicator, which looks completely different from the standard battery indicator.
MTD - This is a technical term used by devs to describe the software organization in your phone, as it relates to things called partitions. The bottom line is that the stock organizational system, called BML, is somewhat fixed and limited, whereas MTD offers devs a great deal of flexibility. Heavily customized ROMs like those from CyanogenMod or anything MIUI rely on MTD file organization. All of our ICS ROMs use MTD. MTD ROMs, generally speaking, experience very little lag, as compared to BML ROMs. When returning to a normal BML ROM from an MTD ROM, special precautions need to be taken.
Nandroid - This is a backup of your entire phone as it stands at that moment in time (ROM, kernel, text messages, your Angry Birds progress, etc.). It is stored on your sd card, which is somewhat immune to your tinkering. A Nandroid backup is a good failsafe for the times when you might want to try out that new experimental kernel your favorite dev has been working on. The files can also be saved on a home computer/flash drive/etc. for safe keeping. Nandroid backups are created using a recovery program like Clockworkmod Recovery. CWM can also use old Nandroids to restore a phone to its previous condition.
Nightly - Nightlies - Some rooted users like the idea of having the most stable, tested, and reliable ROMs available. Others prefer the excitement of being on the cutting edge. Nightlies are the untested regular releases of whatever a certain dev happens to be working on at the time. They package them up, post them online, and let the discussions ensue. These are not for the faint of heart. They are for people who are comfortable addressing freezes, boot loops, and force closes.
Noob - If you have to ask what this means, this is what you are. It's a derivation of "newbie" or "newb," someone who's new to the activity at hand. In many ways, the noob is defined by his actions rather than by the amount of time he's spent rooting phones or posting on xda. Here are a few standard behaviors that will immediately brand someone as a noob:
-Posting new threads to ask questions that have been answered dozens of times. (Hint: It's best to search before posting)
-Posting ROM complaints (without logcat), beginner questions, and other non-development topics in the development forums (It has been theorized that this will ultimately be the end of xda)
-Diving in and flashing away without reading and then posting about your problems (Everyone needs to read the Guide.)
NSTools - This is an app that requires superuser permissions. It can be used to control a variety of the phone's features that are unlocked when running a custom kernel. It can enable fast charge, BLN, overclocking, and undervolting. It often comes pre-installed with ICS ROMs.
OC - Overclocking - Computer processors operate at a variety of speeds. When a manufacturer sells a product (like a phone) to the general public, they strictly limit the speed at which the built in processor can operate, even though the processor may be capable of more. This is to promote stability and reliability. Rooted users can overclock their phone's processor, raising the maximum speed at which it can operate. This can be done through various apps, including Voltage Control and NS Tools. Some ROMs even have the controls built into their settings. There are limits, though. Running a processor at too high a speed can cause overheating and/or glitches.
Odin - This is a program of seemingly mysterious origins that allows your home computer to communicate with your phone. You download it to your home computer. Good communication with your phone requires the installation of Samsung drivers on your computer as well as the use of the USB cable that came with your phone. Among other things, Odin can be used to root your phone, install CWM Recovery, install custom ROMs and kernels, and return your phone to stock after you've screwed it up.
*NEVER touch the "Phone" button on Odin. It should be labeled "Destroy your Phone"
OP - Original Post - This refers to the first post in any given thread, the one that started the thread in a discussion forum. A common noob mistake is to hop into a thread on page 27, read for 30 seconds, and then chime in with a question. He is often directed to the OP, which contains the answer to his question.
OTA - Over the Air - These are the official firmware upgrades that Verizon has released over the life of this phone. They were either pushed out to our phones in the middle of the night or offered up for us to download at our convenience. The latest one, EH03, came in December of 2011. Generally speaking, rooted users do not receive OTA updates. Also generally speaking, this doesn't really matter. The updates can be found on xda, and it is unlikely that the Fascinate will ever receive another OTA update.
Patch - This generally refers to a zip file that can be flashed using CWM. The file usually contains updates or small modifications to an existing ROM or kernel. A great example is the patch that reprograms the phone dialer's voicemail button to open Google Voice instead of the standard voicemail or Visual Voice Mail.
PDA Button - This is the button you will want to use when using the Odin program. You should always avoid the "Phone" button.
Pit file - This is a type of file used with Odin when returning your phone to stock. There is a "Pit" button on Odin you can push to enter the pit file you wish to use. An example of a pit file that you will probably use is Atlas_v2.2.pit. To return to stock, you would use a pit file along with a stock ROM, putting both into Odin at the same time. Droidstyle's guide provides detailed instructions.
Project Butter - This is a Google initiative, launched with Jelly Bean, aimed at reducing phone lag, both real and perceived. It involves research into human visual perception, the pairing of GPU and CPU, graphics buffering, and so on. It's purpose is to make your Android phone run "like buttah."
Radio - a.k.a. Modem - This generally refers to the software that manages the phone's connection to the outside world, not the physical device itself. Verizon would release new versions of this software from time to time in their OTA updates. The two most popular ones are currently EH03 (the latest) and EC09. Both of these work with Android 2.3 and the various Android 4.0 ROMs. The choice of radio can determine your 3g download speeds. It's difficult to say that one is better than another. Different users find good results with each one. Both radios are available as zip files that can be flashed in CWM.
Recovery - Your phone comes with a recovery program. You have to choose to boot it up as an alternative to booting up your phone's normal touchscreen interface. An ordinary phone user would probably never even see this program. It's not pretty. It's just functional. It is basically a list of commands and technical terms that you can navigate using the phone's softkeys, volume up & down buttons, and the power button (to select). Essential to rooting are the special recovery programs such as CWM Recovery. A special recovery program, which is flashed via Odin, will replace the stock recovery program for a rooted user.
Re-Partition - This is one of the check boxes in Odin. This box should be checked only when returning your phone to stock. Of Odin's various check boxes, this is the only one for which widespread agreement of its use exists.
ROM - This is one of the two main components (kernel being the other) of the software running on an android phone. It generally determines the overall appearance of your phone, including which apps are installed by default. The ROM that comes installed on your phone right out of the box is known as the stock ROM. Created by devs, there are numerous custom ROMs available for the Fascinate. Popular ROMs a newly rooted user might try are Superclean3, PWGB, and GeeWiz. The process of flashing a custom ROM to your phone will, generally speaking, erase everything on your phone. The most popular ROM for the Fascinate right now is probably the AOKP version of ICS.
Root - When you buy your phone from Verizon, Verizon still controls it. You are simply a user who is allowed to perform various Verizon-approved activities on it. Gaining root access to your phone grants you the control that Verizon had previously held. Rooting quite literally makes you the "Superuser," opening numerous possibilities for improvement, customization, and ruin. Root access is essential to having a fast, fully customized phone.
Root Explorer - This is an app downloadable from the Android Marketplace (Google Play). As it requires Superuser permissions, it is only functional for rooted users. Its abilities far exceed those of standard file management apps. For example, Root Explorer can copy .apk files directly into the system/apps folder in Android. It's a great way to get that obscure Samsung widget reinstalled on your phone after your favorite developer's ROM washed it away and called it bloat.
Samsung Drivers - This is a small piece of downloadable software that will need to be installed on your home computer before it will be able to communicate with your phone (via Odin or adb).
Skin - This is a program that a phone manufacturer creates with the goal of making its phones more user friendly. It is basically an interface that sits on top of the pure Android guts underneath, hence the term "skin." The skin that comes with Samsung phones is called TouchWiz. This is why our phones don't look quite the same as our friends' HTC or Motorola phones, even though they are all using Android. Some people love TouchWiz. Some people hate it. Some custom ROMs are designed to be used with TouchWiz. Others are designed to be rid of it.
SOD - Sleep of Death - This is when your phone goes into standby mode but then goes into a catatonic state somewhere between being asleep and completely powered down. Users report various degrees of SOD. Some ROMs and kernels have been associated with it, as have certain apps, certain radios, and certain SD cards. Experimenting with fringe OC/UV and didle settings are often responsible these days. Generally, a battery pull (or better, Volume Up + Power) will revive the phone. Once a phone experiences a SOD, it seems likely that it will happen again, so a fix will need to be instituted. A modification of OC/UV settings or a return to stock and clean installation of your ROM, kernel, and apps are recommended.
Superuser - A rooted phone will have a new icon in the list of apps called Superuser. This is what distinguishes a rooted phone from a non-rooted phone. There are numerous apps available on the web and Android Marketplace (Google Play) that require "Superuser permission" to do what they do. Common examples of these apps include NS Tools, Titanium Backup, Root Explorer, Voodoo Sound, NS Tools, and Voltage Control. When a rooted user first runs one of these special apps, the app will ask for Superuser permission. Since you are now the Superuser, you get to press the button that says allow or one that says deny.
S Voice - Korean Siri, courtesy of Samsung.
Swype Beta - One of the early perks of rooting, the latest version of Swype is not available to unrooted users because the Fascinate comes with a special pre-installed (and perhaps outdated) version of Swype. Upgrading gives a slicker version of Swype with a more advanced word selection logic. You must follow a few steps to do it correctly:
1. Change the input method to the Android keyboard (settings->language & keyboard).
2. Uninstall Swype using Titanium Backup.
3. Go to the Swype website, give them your email address, and then follow their lead.
*ICS ROMs don't contain any traces of Swype, so steps 1 and 2 can be skipped for them
.tar - This is the file extension for the files that get flashed via Odin. The file to install CWM, for example, is a .tar file. Another example is the file that returns your phone back to stock.
TB - TiBu - Titanium Backup - This is an app available on the Android Marketplace (Google Play). It is for rooted users only, and it requires Superuser permissions to operate normally. Its two main functions are:
1. Creating backups of your phone (or parts of it) in case you screw it up
2. Freezing or uninstalling apps and other stuff you don't want (i.e. debloating)
Thanks button - Once you have created an established account at xda and made a post or two, you will begin to see a button with a little thumbs up sign next to the word "Thanks." This can be found on the lower right corner of someone's post. Pushing this button lets the person who posted know that their work is appreciated. It is considered polite to thank anyone who has helped you, whether or not it was in direct response to your own question. It is always polite to thank the devs whose software you are using. Xda tallies these thanks and gives experienced users a quantifiable measure of their contributions to the community. You will see a thanks meter under other users' names. Helpful people and prolific devs can have hundreds or thousands of thanks.
Troll - This describes a person who attempts to transform a civil forum discussion into a battle of harsh words. They generally lure people into a massive argument by posting inflammatory remarks that are just slightly off topic. They then sit back and laugh to themselves as the argument develops into the nerd equivalent of a bar fight. To feed a troll and make him stronger, just respond to him. To weaken him, report his posts to moderators.
TW - TouchWiz - see "Skin"
TWRP - TeamWin Recovery Project - This is an alternative to the traditional recovery program. Rather than using the volume rocker, softkeys, and power button to interact with it, a touchscreen interface is used. While it offers some interesting potential, it is still under development in terms of compatibility with the Fascinate and our popular ROM/kernel setups.
UV - Undervolting - This is a means of attempting to reduce battery consumption when using custom kernels. Rooted users can accomplish this through one of several apps, with Voltage Control and NS Tools being common examples. The point of whether UV reduces battery consumption is highly contentious, but there does seem to be a theoretical basis for its validity, as well as a preponderance of anecdotal evidence.
Voltage Control - This is an app available on the Android Marketplace (Google Play). It requires root access (i.e. Superuser permissions). When used with compatible kernels, it allows you to overclock and undervolt your phone.
Voodoo - Project Voodoo is a collaborative software development effort started by dev supercurio back when Galaxy S phones first hit the market. Its goal was to optimize the Galaxy S, bringing it up to its full potential. Voodoo innovations have been used by countless rooted users. Voodoo features can only be used on compatible custom kernels. The project consists of three main branches:
1. Voodoo Color - optimizes screen images/video *Not really available in most modern Fascinate setups, but people still talk about how they miss it.
2. Voodoo Sound - optimizes sound quality for audiophiles *The Voodoo Sound app is available from the Marketplace (Google Play) to control settings.
Wipe x3 - This term refers to the act of wiping the slate clean on your phone. It removes all apps you have installed and any data associated with those apps. It will not erase Android, your ROM, your kernel, or anything on your sd card (your photos and videos are on your sd card by default). The Wipe x3 is often done before making major changes to your phone's system. The process is accomplished through a recovery program such as CWM. Here are the 3 commands (hence the "x3"):
1. wipe data/factory reset
2. wipe cache partition
3. wipe dalvik cache
*Note, performing a wipe data/factory reset will reportedly wipe the cache partition and the dalvik cache, so steps 2 & 3 may be redundant.
zip - For our purposes, this refers to the file type for files that can be flashed with CWM or other recovery programs.
*Credit goes to Jawman27 for a great glossary! I just edited a bit for the gs3!
did this man just collect the $1000 bounty?
Sent from my SGH-T999 using xda app-developers app
lol I wish I was that intelligent. This is merely just a guide of whats already posted in the dev section, just consolidated into one thread. I made a guide like this for the SCH-I500 Fascinate and was very popular because all the files and steps needed are in the op... No need to search for anything!!! Its pretty basic now, but once development takes off it should be benificial to new android users...should also help keep the bricks to a minimum.
This will definitely be useful to us first time Samsung peeps who haven't used Odin before. Thank you for taking the time to put this together!
Sent from my ADR6425LVW using Tapatalk 2
Marcismo55 said:
This will definitely be useful to us first time Samsung peeps who haven't used Odin before. Thank you for taking the time to put this together!
Sent from my ADR6425LVW using Tapatalk 2
Click to expand...
Click to collapse
Glad you like! Now all we need is for development to get rollin and more will be added. All in due time...guess Im a little anxious, since this is the first device that I purchased before actual release date :highfive:
Nice man! I have years of HTC experience behind me, but coming to Sammy is totally new with odin. Definitely using this guide on Thursday
Sent from my ADR6425LVW using xda premium
Do you think you could add the dialer programming codes? I'm coming from a Thunderbolt and was curious if *#*#4636#*#* worked or were there other codes I haven't come across yet?
Thanks for this my first time to a Samsung device coming from HTC gonna wait on rooting till the bootloader issue is resolved but nonetheless added this thread to my favorites list
Sent from my HTC ThunderBolt using xda premium
I have always been hesitant about rooting devices before the 1year Verizon warranty has expired, but I don't think I'll be able to make it that long with this phone. As such, I have two questions for y'all...
1.) Will following the return-to-stock instructions leave me with a device that is indistinguishable from one that had never been rooted at all? Will there be any way to tell that it had been rooted?
2.) While I understand that if you follow directions it's unlikely that you'll brick your device, it is still something that concerns me a little... I have heard that an unlocked bootloader is something that is required for moth methods of recovering from a soft brick. Is this true? If so, I assume that Verizon's bootloader would pose a problem in this regard?
I just want to understand the risks before I jump in. Thanks in advance.
Seems from experience with my phone, enabling root will not force custom screen at boot, installing custom recovery will. Idk if it ups the flash counter though. If you only root and one day revert back, I'd imagine it will be indistinguishable.
Sent from my rooted SCH-I535 using xda premium
Will this trip the counter? Also, is CWM in the first root?
Solar257 said:
Do you think you could add the dialer programming codes? I'm coming from a Thunderbolt and was curious if *#*#4636#*#* worked or were there other codes I haven't come across yet?
Click to expand...
Click to collapse
Ill look into it thx!
No this root method does not trip the counter....yes going back to stock erases all traces of being rooted. Thx to odin this device is damn near unbrickable.
droidstyle said:
No this root method does not trip the counter....yes going back to stock erases all traces of being rooted. Thx to odin this device is damn near unbrickable.
Click to expand...
Click to collapse
thanks for the detailed Guide I am sure this will help a lot of people out.
Section 1 updated with new root.img
Updated!! Consolidated the three sections into one and added section 2 for Recoveries.
Sorry if this is a total nub question:
Will flashing this cause my current data to be wiped?
I just got the phone how I like it, not complaining cause root>most things I can stock but I wanna plan for it just in case my apps/settings/contacts/etc. go bye bye.
voted to counter the trolls who think its funny to 1 star threads.

[GUIDE] [NOOB] [ANDROID] Everything that You Want to Know ! !

This post is going to help you if you have done a fresh entry in the unending world of Android. Android being an open source operating system for mobile phones, offers limitless possibilities of optimization and customization as per your requirements. Brand new android device comes with stock ROM and locked bootloader but half the charm of an Android phone lies in the root-based apps, beautiful mods and patches, and custom ROMs. Let me first explain these terms:
BOOTLOADER:
Every Android phone has a bootloader that instructs the operating system kernel to boot normally. But you need to understand one thing here that as Android OS is an open source OS and is available on a variety of different hardware, every manufacturer has their own version of bootloader specific for the hardware present in it’s environment. In literal terms, bootloader is code that is executed before any Operating System starts to run. The concept of bootloaders is universal to virtually all Operating systems that inculcates operating systems on your PC, laptop, smartphones, and other such devices.
Why is Bootloader Locked??
A bootloader is usually locked on an Android device because although it’s an open source OS, still the manufacturers want you to stick to their Android OS version specifically designed for the device. In order to apply this concept, manufacturers lock the bootloader. With a locked bootloader on Android devices, it is virtually impossible to flash a Custom ROM and forced attempts void warranty as well as usually end up in bricks. Therefore, the first step is to always unlock the bootloader. A lot has been said about bootloaders being “locked” and even the developer-friendly Nexus devices shipped with a locked bootloader (Nexus devices and a couple tablets are easily unlocked with a single command).In fact, a lot bootloaders are locked and encrypted, meaning simple commands like “fastboot oem unlock”, won’t do a thing.
Why To Unlock Bootloader On Android Devices??
The explanation to this question is really simple. If you want root, you’d be wanting to flash Custom ROM post-root, and if you want to install a Custom ROM, you’d need to have your stock bootloader unlocked. In simple terms Unlocking the bootloader allows you to install custom Firmware on your Android phone.
Warning: Unlocking your phone’s bootloader voids its warranty. It also completely wipes (formats) your Android phone’s internal memory including applications, contacts, SMS and MMS messages etc.
ROOTING:
Half the charm of an Android phone lies in the root-based apps, beautiful mods and patches, and custom ROMs. If you have not rooted your phone yet, believe me you are not getting the most out of it. Rooting offers many advantages indeed but, at the same time it is also a little risky as it breaks into the wall of security build by the operating system.
According to a survey, 80% of Android phone users live happy with an unrooted device and the reasons for this are various- some people think of it as a sort of criminal activity, some are afraid of losing warranty, some are afraid of bricking their phone, while most people do not even know about the existence of a term like “rooting”.
ROOTING is one of the most loved and equally disdained terms in the world of Android. Android phone users can generally be divided into three sects on the basis of their opinion towards rooting stuff. First of all, there are those who are willing to unlock and root their phones as soon as they get it or update it with a stock firmware. Then there are larger class that are happy with keeping their phones in a state they bought it and keep miles away from rooting. Finally, there is a moderate group that keeps wondering- “To root or not to root!”
What is Rooting??
The term “root” comes from the Unix/Linux world and is used to describe a user who has “superuser” rights or permissions to all the files and programs in the software OS. Thus rooting is a kind of hacking procedure where you seek to obtain access to the hidden system files. It’s like seeing a tree with its roots that remain immersed in the earth. By rooting your Android phone, you can have capability to modify and change the internal files of your device which otherwise remain locked and hidden.
Why Not to Root Your Phone??
Rooting Voids the Warranty:
It may be that you skip all other harms associated with rooting, but one thing you cannot escape is that it will surely void the warranty of your phone as soon as you root it. Suppose you have rooted your device which is still under warranty period. One day it stops working suddenly or shows signs that demand repairing. In that case you will not be entitled to claim the warranty because it is void due to installing a modified kernel. However, there are methods that can uproot your device and you can reclaim the warranty.
Rooting Can Brick your Device:
Another solid reason for not attempting to root your device is the potential risk of “bricking” it. There are thousand of tech blog over the web that are full of rooting tutorial for almost every Android phone and tablet. I have known some people who, searching for a rooting tutorial for their device, stumbled upon a tutorial written by some raw-hand person and bricked or almost made it unusable. Moreover, in most cases it is the fault of the device owners, who being a raw-hand themselves, do not follow the procedure to the letter or carefully and turn their phone into a costly paper-weight.
Rooting Does not Let You Get Official Updates:
As soon as you root your Android phone, you will not be able to receive the Over-the-Air updates released by the manufacturer. It is another thing that you install the updates manually if you find the OTA update zip file.
Rooting might Threaten the Security:
Most of us store vital and private data such as passwords and credit card details on our smartphones and this has necessitated a greater need for security than ever before. According to a recent survey, one-third of Android apps contain a certain level of malware as they require our personal data to run. There are so many keyboard app apps, for instance, that store a database of everything you type on your Android phone- whether it be a common word or a password and login details. You are open to such risks even without rooting your Android device. The open nature of the Android OS is the reason why android users are more prone to these attacks.
Here are a few simple tips that might help you make your phone’s data more secure:
Install a Mobile Security/Antivirus App- The best ways to get started is to download and install a complete android Mobile Security App to protect your android smartphone or tablet. These security apps are specifically designed for mobile platform and offer browser protection and safety against potentially dangerous sites.
Granting Permissions to Apps Carefully- You should be a bit more aware when you are installing all those cool new apps and do read and grant permission to data that you are only comfortable sharing. If you are not happy with any of the “requests for permission”and feel it is information you rather not share, then discontinue using the app.
Avoid Installing Apps from Unknown Sources- While we do not say that you take a complete blanket approach towards apps from unknown sources and disallow them completely, if you want to install one, be absolutely sure that they are completely safe. Remember that no system or set of guidelines are ‘absolutely safe’, but reducing risks helps a great deal.
Advantages of Rooting:
Most Android enthusiasts or advanced users believe that it is impossible to make the most of and Android smartphone without rooting and installing a custom recovery on it. While keeping you Android device gives you a feeling of safety and insurance, rooting denotes to a state of freedom, adventure and wilderness. No doubt it involves risk, but it has big rewards too. Let’s consider them too. I see many people asking,”I have rooted my phone, now what?” Here are a few reasons why one should root one’s Android phone/tablet.
1. Truly own your device
2. Unlock hidden features and install incompatible apps
3. Boosts your phone speed and battery life
4. Uninstall pre-installed apps
5. Block ads in any app
6. Flash a custom Rom/Kernel
7. Enter into dark word of Android
8. Move all apps to SD card
9. Link SD card with internal memory
10. Choose Startup and background apps
11. Quick optimization and clean up
12. Get root explorer and terminal emulator
13. Fully customize your OS in your own way
14. Directly install apps to SD
15. Be able to use roundr, GMD, ROM toolbox
16. Get font installer and boot animations for better fonts
17. More internal storage
Rooting Opens a World of Possibilities:
There are many people who opt to root their device only to be able to install certain apps that need root privileges. Among these apps, there include some life-savers like Titanium Backup, Apps2SD, Root Explorer, Triangle Away, Juice Defender, ROM Manager, and so on. Thus on you rooted Android phone or tablet, you can backup your Apps and Games, move the apps to the external SD card, extend battery backup, unlock your SIM-locked phone and what not.
Ability to Install Custom ROM and Mods:
Another major, or probably the greatest, advantage of rooting your Android device is that it open the world of customization for you. Having in full control of your phone by rooting it, you can do what those with non-rooted device can only dream of. You may have heard of people installing custom ROMs on their devices. There are many great custom ROM’s available that can make your Android device look and perform drastically different.
Why a custom ROM is so important for many people has many reasons. You rooted phone with a good custom ROM installed on it can perform better, faster and smoother. There are many custom kernels that give you great battery-life. The stock Android ROM does not support theming, but there are great custom ROMs like the CyanogenMod and MIUI ROM that have great theming capabilities that add to the freshness of your phone.
The option of changing ROM does not let you get bored of the same look and feel of your Android device. Most Android phones see a single firmware upgrade from the manufacturer. If you buy an Android device with Android 4.0 Ice Cream Sandwich, it will only see an upgrade to Android 4.1 Jelly Bean. Thanks to our ROM developers who bring the highest version of Android OS to the lowest-priced phones. It is only the magic of custom ROMs that we see a Galaxy Ace or Optimus One user enjoying Jelly Bean.
Best Apps For Rooted Users:
I have been using mobile phone’s since the days when it used be bulky like a walkie and had an antenna on the top. Just go back a few years ago and compare the phones of the day to the smartphones that we own today, and you’ll realize that their evolution has been fantastic. I have also been lucky enough to experience all major platforms, from java-based devices down to Symbian, Android and the newer Windows Phone too. I first, first came to know about Android during the days when the smartphone world was ruled by Nokia-made Symbian devices. For many, Android was just a thing of curiosity then.
Having got bored of Symbian, it was much later that I decided to switch to Android and bought my first device the Galaxy S. the new OS was attractive but after a few months, I was still unable to figure out why it was so popular. The difference between my old and new OS’s seemed marginal. Having spent about 4 months with my first Android phone in its virgin state, I came to know about a new thing called “rooting” that sounded to me synonymous to “bricking” my phone.
Anyway, I finally took that bold step with bouncing heart and only after after that adventure, I was able to get a deeper peep into Android. I believe that anyone reading these lines would not deny that it is impossible to enjoy Android to its full without rooting it. Voiding one’s phone’s warranty might sound a good idea to all, but rooting pays for it pretty well. Now, I own Moto E and within a month of its purchase, I rooted it ! If you wish to enrich your experience with your phone or tablet, rooting is the only way to achieve the ultimate performance and customization whether it be getting speedy response, better battery, enhanced features, tweak system or make visual changes.
Today, we’ll see some really good, and also popular, apps that can help you get most out of your Android device. As the very title of the present article makes it evident, all these apps require root access to function. And therefore, you must have a rooted device before you can use them.
So, here begins our list of some of the best apps for rooted Android phones and tablet devices:
JuiceDefender Ultimate:
The bigger the screen, the better the fun, isn’t it? We all like a smartphone or tablet with a big screen that show everything with minutest detail and vivid colors. In most cases, OEM’s use battery according to the screen size of a device. Then why it is that the bigger the screen, the least the battery runs? You’ll hardly find a guy who is happy with the battery performance. In a situation where we cannot extend the capacity of the battery of our device, it’s wise to manage the battery power to get better performance out of it. Battery drain is the biggest concern of any smartphone user but if you have root, you can enjoy better performance using a 3rd-party power-save app. While you can find hundreds of battery-saver apps at the Play Store, there are just a few that really possess the magic wand. And among such apps, JuiceDefender Ultimate is probably the king of all. It is a mighty power manager app packed with advanced functions that controls, checks and manages all features and resources that devour the battery juice of your device. The app employs a bunch of effective measures to give you the best possible battery backup, and it does so by intelligently managing the channels that suck the battery most. It features highly customizable options to curb battery drain and get it up to your expectations.
Xposed Framework:
Root access on an Android device gives you the license to do almost anything and when it comes to personalization of your device, modifying the available features and adding new things to it, Xposed Framework is an ultimate tool. It is a custom framework that replaces the default framework of your devices and adds the ability to be modified via compatible modules. The presence on Xposed framework and its modules ensure that you get the power to control the visual elements on your device in your hands. You can customize things like the statusbar items, notification panels, extend reboot menu options, enable call recording, manage connectivity features, install third-party icon packs on stock launcher and thousands of such tasks very easily without having the knowledge of editing system apps and XML codes.
Tasker:
Extending our list of best apps for rooted devices, I’m now going to talk about an app that hardly requires any introduction if you not a novice with Android. Tasker for Android is a must have app if you are an advanced or power user, but it offers much even if you are new to it. It is a kind of personal genie that is capable of granting your daily mobile wishes. Tasker is a task control and automation tool that, if used wisely, can multiply your mobile experience many times. The app has lots of advanced features that let you
program your devices by adding tasks to make your device do things according to the rules defined by you. It lets you determine the behavior of apps and features as you might wish them to behave, whether it be to assign a task based on sensors, schedule app automation, control data and network connectivity and so on. It can do almost anything you can imagine. If you are a hardcore Android user, Tasker might prove a
dream app for you.
ROM ToolBox Pro:
ROM ToolBox Pro is a perfect example that shows the immense possibilities offered by root access on Android. As its very name proclaims, it is not just a tool for rooted Android devices, but a collection of various advanced useful tools with plethora of options for customizing the performance and user interface of your phone or tablet. Here is a list of the major tools that Root ToolBox Pro combines:
App manager
ROM management
DNS changer
Terminal Emulator
Task manager
Scripter
Root file browser
SD Booster
build.prop editor
CPU control
Kernel tweaks
Font installer
Theme manager
Theme chooser
Boot animation changer
Icon changer
Reboot manager, and lots more ! !
On expanding each of the listed tools, you’ll get more options related to specific tools.
Any app that has so much to give you at the price of one is definitely good !
Greenify:
While apps like JuiceDefender Ultimate and ROM ToolBox Pro aim at giving you better battery life and enhanced performance on your Android device respectively, Greenify targets both ends at the same time. Greenify lets you select apps that remain active and run as background processes even when they are not actively running. Now, such apps not only eat your phone’s ROM, making it slow and laggy, but also keep draining the precious battery juice continuously. If you are one who is fond of installing a lot of apps, Greenify can save you from being worried about performance and battery life. It lets you identify rogue apps and allows you put them in hibernation mode so that they do not keep eating CPU and RAM resources and leeching battery power. The app is pretty easy to use. Simply add the applications you want to hibernate when they move to the background, and let Greenify do its spell.
Titanium Backup:
Good battery life, awesome performance and cool customization— we have seen one or more apps for these things. Now let’s see another must have and one of the most rated apps for rooted Android devices. If you got root privileges on your device, Titanium Backup is a highly recommended app for you. You might find a number of backup apps at the Google Play Store, but none of them does the job so perfectly and nicely. The only negative thing about the app is it user interface that feels outdated, but when it comes to functionality, Titanium Backup surpasses them all.This best in class app can backup all apps (including system apps) and games on your apps with all app settings and data. You can backup apps individually, in groups or all at once. Also, before backing up or restoring the apps, you can choose whether to do the operation just with the apps, settings and data or a combination of all three. Besides, it also lets you schedule your backups. If you purchase the Pro key, you will also be able to use some premium features like—
Data migration (important for those who are fond of switching ROMs)
Dropbox sync and restore
Multiple backups per app support
Zero-tap batch restore
App freezer for keeping an app unchanged
Backup apps without closing any app
And more.
NoBloat:
As the name suggests, No Bloat allows you to remove all the bloat from your Android device. For rooted users, the app should come in handy to remove all the useless apps and bloat that carriers or OEMs ship in their phone right out of the box, and free up some resources that should improve performance and battery life,
No Bloat is pretty simple to use, and even has an handy option to backup the APKs before deleting them, in case things go wrong.
RoundR:
The only purpose of RoundR is to make the edges of your screen rounded, instead of flat, like in iOS. While this may seem like a very minor change, it somehow ends up making a very noticeable difference in day-to-day usage.
It is very tough to explain how rounded corners can affect the UI so much, but in the end it does. RoundR is one of those apps that you must try to know the difference. The app can be downloaded for free from the Play Store.
GMD Gesture Control:
GMD Gesture Control is particularly useful for Android tablet owners. Using this app, users can assign certain gestures to perform certain tasks. For example, you can setup a four finger swipe across the screen to automatically take you to the previous app you were using as in the iPad. You can easily emulate all the gestures that the iPad has using GMD Gesture Control.
Even Note and other Phablet owners can use GMD Gesture Control for navigation purposes. Instead of hitting the back button, they can assign a gesture which they can draw on the screen to imitate the back button.
Rom Manager:
Rom manager is one great app for all you enthusiasts who want to flash new ROMs and taste new versions of android in your smartphones.This app gives you a list of all the famous ROMs available for your device.You can also download them through this app and this also saves you a lot of time searching for it on the net.The pro version of this app is worth a try.
SoftKeyZ:
Bored out of the normal looks of your navigation buttons? Wanna add some colours to your screen? Go try this app.This app can personalize your navigation buttons(soft keys) into a lot many styles.It has 150+ themes to choose from.This is an awesome app for those who want your smartphone to be just like you want it to be...
Solid Explorer:
This is the best file manager out there.The basic idea of this explorer is just awesome.This app provides you two panels when positioned in the landscape view.You can simply copy-paste any file or move any file from one panel to the other without the fuzz of remembering the path of the locations separately.It also has additional features like FTP connection,etc... This is a must have app for all the android users.
NOTE:You also need to install solid explorer unlocker to use the complete features.
At the moment it has some glitches working in android kitkat.
Font Installer:
This app comes with hundreds of custom fonts ready for you to install. Use any custom fonts just by saving it into your device and install it from your device storage.
Link2SD:
It is one of the best app you should have after rooting your phone. This app links all the files and folders to your external SD card, hence virtually increasing internal memory.
RECOVERY:
Android devices come with Google’s recovery environment, which is often referred to as the “stock recovery.” You can boot to the recovery system by pressing device-specific buttons as your phone or tablet boots or by issuing an adb command that boots your device to recovery mode. The recovery menu provides options to help recover your device — for example, you can reset your device to its factory default state from here. The recovery mode can also be used to flash OTA update files. if you want to flash a new ROM to your device — or re-flash the factory default ROM file — you’ll need to boot to recovery mode first.
The stock recovery is a minimal, limited system. It’s designed to be ignored, and it can generally only flash OTA updates and ROMs provided by the device’s manufacturer, not third-party ROMs.
A custom recovery is a third-party recovery environment. Flashing this recovery environment onto your device replaces the default, stock recovery environment with a third-party, customized recovery environment. This is a bit like flashing a custom ROM like CyanogenMod — but, instead of replacing your device’s Android operating system, it replaces the recovery environment.
A custom recovery environment will do the same things as the stock Android recovery. However, it will also have additional features. Custom recoveries often have the ability to create and restore device backups. Custom recoveries allow you to install custom ROMs. ClockworkMod even offers a “ROM Manager” app that allows you to access many of these features from a running Android system — this app requires a custom recovery installed to function.
Popular Custom Recovery:
The Android Recovery which comes installed on any device has several issues, so that’s exactly why we finally consider that a custom recovery could be a much better choice as long as it find a way to reset your device when it may be impossible to boot into it.
Clockworkmod is available for quite a while and it has managed to win the title of the most popular stock recovery replacement thanks to all its features. But another player had also entered the game being known as TeamWin Recovery Project (or simply TWRP) and we bet that you are curious about it as well ! !
This fully touch-based custom recovery was initially dedicated exclusively to Nexus devices, but things have changed and now it is available for a variety of other smartphone and tablet models too, in form of official or thirdparty builds.
But which of these apps should you choose? CWM Recovery wins over TWRP Recovery or not? Here we have a detailed analysis of the most important aspects of these two custom recoveries which will help you taking the best decision:
The Graphic User Interface:
ClockworkMod’s interface is completely different if we compare it to the interface of
TWRP. This one comes with larger buttons that make it even easier than before to spot the feature that you are looking for and select it with a simple tap. And don’t forget about the soft buttons for Home and Back here, or about the option to turn the display off after a certain amount of time. But this doesn’t necessary have to mean that the interface of TWRP is necessarily much better, but simply with some differences that can offer us a more comfortable and faster experience.
Installing ZIPs:
This is one of the most used features in a recovery, but we must admit that we cannot actually compare CWM Recovery with TWRP Recovery at this chapter. They both work flawless when it comes to installing zip files, but some of you might consider that is easier to locate the zip file you want to install it in TWRP Recovery; and the built file manager is the one that makes the difference.
Backing Up option:
If you select the backup option in ClockworkMod, the backing up procedure starts immediately for all the partitions, while TWRP proves to be ideal as long as it allows you to backup only one partition. To be more specific, it presents you several options that you can choose from, giving you the possibility to control exactly which partition you want to backup or in which storage you want this backup to take place. So here, we can definitely say that TeamWin Recovery Project can successfully replace ClockworkMod.
Restoring Backups:
This time, when it comes to restoring backups, ClockworkMod recovery comes with an advanced restore option which lets you restore just one partition, while TWRP recovery gives you the possibility to select as many partitions as you might want. Even more, partitioning the SD card in ClockworkMod is by default set to ext3 file system and you have no chance to change it. TWRP instead lets you change it to ext4. So, TWRP seems once again to have won the battle, but we must tell you that besides the interface or the backing up and restoring backups options, it actually provides the same features as ClockworkMod. But ClockworkMod comes with one click installation (via Clockworkmod’s own ROM Manager app), while TWRP can be installed with some adb commands, so this aspect comes in favor of ClockworkMod recovery.
Check the next thread for more info
Review the Risks ! !
Customize your Android
Hit thanks, if helped :good:
TWRP Recovery – Explored and Explained !
Most of us here are very well aware of what TWRP is, especially people who flash ROMs every
now and then. Today, I’m here to explore this simple yet very unique recovery and explain in
detail the functionality of all of its features. I will also help you on how to flash a Custom
ROM/Kernel/Mod using TWRP. To get on with that, I need to let you know, what TWRP is ! !
What is TWRP?
TeamWin Recovery Project or in short; TWRP, initiated in 2011, is an Android Custom Recovery
with full touch UI. This Recovery brought in and created a new trend of Touch-based
recoveries. It adds customization support and enormous other amazing features to the AOSP
recovery code which makes it one of the best Android Custom Recoveries available till date.
The GUI is fully XML based, so you can modify each and every aspect of this
recovery according to your desires, provided that you have appropriate knowledge of XML and
Android.
Why choose TWRP over others?
TWRP was the first to bring in the concept of touch-based UI on recoveries,
which in turn defines its uniqueness. Since the early days, this recovery has evolved more than
any other recoveries available, bringing in huge changes in the code and UI. If you choose
TWRP, you’re assured to be updated regularly with more and more features accompanied by
stability.
Exploring the Main Menu:
As soon as you boot your Android into the latest build of TWRP, the following menu will serve
you, known as the main menu. The main menu consists of 8 tabs (Install, Wipe, Backup, Restore, Mount, Settings, Advanced &
Reboot), each having its own sub-tabs and functions. Let us now begin with the first tab on the
screen.
Install:
The Install tab is simple and make its role in flashing files (ROMs/Kernels/Mods). Another thing
that is unique here, is that you can add a queue of files and the same will be flashed in the
respective order.
Now, lets get to know how simply this works.
1. Press on the “Install” tab.
2. Browse and choose the file that you desire to flash.
3. Press on Add more zips if you desire to flash another zip(s).
4. Swipe the round button present on the bottom of the screen to initiate the flashing
process.
Wipe:
This tab serves the function of wiping the partitions on your device. Wipe-able partitions
include System, Data, Cache, Dalvik Cache, Internal Storage and USB-OTG (if any). Wiping the
partitions is necessary as a pre-flashing process and is different for Installing
ROMs/Kernels/Mods and updating them. So, before you set yourself for opening this menu,
make sure to know what you’re doing.
Here, I’m gonna mention some basic wiping steps for Installing ROMs/Kernels. Note that these
are universal for every ROM and Kernel, until and unless the developer himself states some
specific steps.
Wiping before Installing a Custom ROM:
1. Press on “Wipe” tab.
2. Press on “Advanced Wipe”.
3. Select the partitions: Dalvik Cache, System, Data & Cache.
4. Swipe the round button present on the bottom of the screen to initiate the wiping process.
Wiping before Installing a Custom Kernel:
1. Press on “Wipe” tab.
2. Press on “Advanced Wipe”.
3. Select the partitions: Dalvik Cache & Cache.
4. Swipe the round button present on the bottom of the screen to initiate the wiping process.
Backup:
The Backup tab holds a very important and useful function. Situations might arise when you
accidentally Install a wrong (corrupted/damaged) or may be un-desirable ROM/Kernel/Mod.
Post these situations, we find ourselves stuck. So, the Backup option gives us an helping hand to come out. This option is also well known as Nandroid Backup, but is now certainly referred
to as a common term; Backup.
TWRP offers some unique privileges in the Backup option too. A user can simply select the
partitions that he/she might want to backup viz Boot (Kernel & Ram-disk), Recovery (Present
Recovery), System (Firmware files), Data (User Apps and Information) & Cache (Dalvik Cache
and Cache).
To Backup your current ROM, simply follow these steps:
1. Press on “Backup” tab.
2. Select the partitions you want to backup (Usually, ROM backup includes System, Data,
Cache & Boot).
3. Swipe the round button present on the bottom of the screen to initiate the backup
process.
Apart from backing up, you can also Set Backup Name (set a specific name for your backup),
Enable compression and Skip md5 generation during backup.
Restore:
The Restore option in simple words, restores the Backup. A backup made with the Backup tab
is to be restored from this tab. This option also allows you to delete a previous backup and
even enable md5 verification. Restoring a backup is quite easy:
1. Press on “Restore” tab.
2. Press on the backup you want to restore.
3. Swipe the round button present on the bottom of the screen to initiate the restore process.
Mount:
It certainly is essential to mount partitions while flashing some specific files. Mount-able
partitions includes: System, Data, Cache, Internal Memory, SD-card and USB-OTG (if any). To mount a partition:
1. Press on “Mount” tab.
2. Select the partitions to mount.
Settings:
This tab holds all the settings related to the recovery subsystem. The following come under this tab:
1. zip file signature verification (Enable flashing only if the zip file is signed properly).
2. Use rm -rf instead of formatting (Option enables manual rm -rf command to wipe instead
of automatic formatting)
3. Skip md5 generation during backup (disables the generation of md5 sum during backup
process)
4. Enable md5 verification of backup files (enables restore of backup, only if md5 sum verifies)
5. Use military time (Use the time format followed by Military/Army)
6. Simulate actions for theme testing (enables modification of actions during theme testing)
7. Time Zone (Set time zone according to your country)
8. Screen (Enable/disable/set screen timeout)
9. Restore defaults (Restores all the settings to their default value)
Advanced:
It provides all the advance functions of the TWRP recovery. Advanced functions include:
1. Copy Log to SD (Transfers the error log generated to the SD card)
2. Fix permissions (Fixes the permissions of the System files to fix errors)
3. File Manager (In-built recovery file manager to manage files on Internal and External
memory)
4. Terminal Command (In-built terminal emulator to execute commands)
5. Reload Theme (Reloads the theme from TWRP/theme, necessary when applying a new
theme)
6. ADB sideload (Initiates sideload over ADB to flash zips)
Reboot:
This menu lists ways to reboot the device to various locations. You can reboot your device into
the following modes just with a simple gesture. You can perform the following actions within
the Reboot menu:
System (Boot your device normally into the OS)
Power Off (Powers down your device completely)
Recovery (Reboots into the recovery mode)
Bootloader (Reboots the device into bootloader/fastboot mode)
To reboot:
1. Press on “Reboot” tab.
2. Press on the desire button where you’re willing to boot.
3. Swipe the round button present on the bottom of the screen to initiate the rebooting
process.
That’s all about TWRP, that every user needs to know and understand.
Things to Do Before and After Installing a Custom ROM:
Become familiar with Recovery and its working
Ensure a decent battery level
Backup your current ROM using recovery(It will help you if in case you are stuck in bootloop in future or if you want to go back to Stock
Go to settings and do factory reset
Reboot to recovery and flash ROM zip and Gapps
Clear cache and dalvik/ART cache
Reboot
ROM: Although ROM in computers mean Read Only Memory (memory storage which once written, can’t be edited or deleted) but When it comes to smartphones and tablets, the term ROM is used to refer to the firmware stored in the internal memory of the device, rather than the internal memory itself. It can also refer to a file prepared for the purpose of replacing this firmware with another version of using a special method.
Thus, when you are told by someone to download a ROM, they are referring to the file that contains the firmware in a format ready to be installed to your phone to replace it’s existing firmware. Similarly, when asked what ROM is your phone running or when told by someone their phone is running a particular ROM, they are again talking about the particular variant of the firmware.
ROM Distinction:
Truly Stock ROMs / firmware:
This is the operating system in its default form, without any modifications made to it except for any device-specific support required to run it on the particular device. Truly stock firmware provides the standard user experience of the operating system without any cosmetic or functional changes made. These days, truly stock firmware is primarily found in cases where both the device and the operating system is built by the same company. Amongst modern mobile devices, examples of truly stock firmware can be found on Nexus and (new) Moto devices.
Manufacturer or Carrier branded Stock ROM / Firmware:
This type of firmware has had enhancements added over the default operating system by the device manufacturer or the mobile service carrier. This often includes interface enhancements, proprietary applications and in most cases, restrictions intended to limit the use of the device with a specific carrier or region. There are often further restrictions preventing installation of firmware not released by the carrier or manufacturer.
Custom ROM / firmware:
Almost all devices ship with either of the above two categories of firmware, though things don’t end there. Independent developers who like to customize their devices beyond the standard options provided often tend to release the fruits of their labor for the rest to enjoy, in form of custom ROMs. The more open the platform, the more independent development it attracts, a good example of which is the independent custom ROM development for Android.
Stock v/s Custom ROMs:
Stock firmware is the result of a lot of research and testing done by the operating system vendor, the device manufacturer and/or the mobile service carrier. Therefore, it carries several advantages:
It is usually quite stable upon release.
Almost all bugs are patched during the extensive beta testing before release.
It carries the official support by the firmware vendor, device manufacturer and the mobile service carrier.
Updates are pushed automatically to the device by the carrier.
Along with its advantages, stock firmware also carries its disadvantages and these include:
Updates aren’t frequent, as development is done mostly by corporations who have to follow a scheduled release cycle.
Updates are often released first in the United States, leaving the rest of the world waiting. (A world does happen to exist beyond the United States, we’ve confirmed it ourselves!)
Worse still, when manufacturers choose to no longer release official updates for their older devices in favor of newer ones, their users are essentially stuck with old versions of the operating system. This case is evident with many Android devices barely a year and a half old.
Advantages & Disadvantages of Custom ROMs
Custom ROMs are as good or as bad as the effort put into them by their developers. Key advantages of custom ROMs are:
First and foremost, choice! There are thousands of custom ROMs out there for a range of devices, each offering a diverse set of features not found in the stock ROM.
Update frequency – custom ROMs are often under active development and newer releases of the core operating system are incorporated in them way before updated official ROMs are released. This is particularly true in case of Android devices, where developers start porting newer versions of Android to several devices as soon as they are released.
Custom ROMs usually have all the extra restrictions removed, enabling users to sideload apps, tether their mobile data connection to their computer without paying extra for it, gain root access, use their device in any region etc. without any need for circumventing the protection themselves.
Performance enhancements and optimizations found in many custom ROMs can make them much faster than stock ROMs, enabling users to get the most out of their devices.
Overclocking options are built into some custom ROMs, further speeding up the devices.
Undervolting options found in some ROMs on the other hand result in improved battery life.
Old phones with little internal memory can benefit most from custom ROMs that allow them to use the external SD card memory for the apps exactly the way they would use the internal memory.
So with all these advantages, there should be no reason to stick with the stock ROM, right? Not necessarily! Like all things in life, custom ROMs come with their disadvantages as well:
Due to the lack of extensive testing prior to release, many custom ROMs can be buggy in the beginning and installing a ROM with missing or corrupt critical files can even brick your phone.
Several custom ROMs that are ports of ROMs from other phones can have missing functionality that hasn’t been made to work on your phone with the ROM yet.
Installing a custom ROM usually involves wiping your phone to factory settings, so you lose your data and start from scratch. Fortunately, Android’s built-in contact syncing along with apps offering message, call log and app backup/restore make this process easier, letting you retain your data.
The installation process itself can be cumbersome and may require you to root your phone and often circumvent its security features to allow for custom ROM installation in the first place.
Installing a custom ROM will in most cases void your phone’s warranty, though often the process is reversible, meaning you can turn your phone back to stock as long as it isn’t bricked.
Installing a ROM to your phone requires you to root it first in most cases. While rooting most phones is easy, some phones require a complicated procedure to be followed before you can install a ROM to it and often, such procedures involve a risk of bricking your device if things go wrong.
Making the Choice
Choosing between a stock ROM and a question ROM is really a matter of your requirements. If the stock ROM on your phone lets you do all that you ever want to do with your phone and doesn’t feel slow, there isn’t any need to go through the trouble of circumventing your phone’s security and installing a custom ROM to it.
However, if you want to take your phone beyond what it currently offers, don’t care much about the warranty and are ready to take the risk of whatever may happen if things go wrong to be able to customize it the way you want, a custom ROM is at times the only solution. Choose wisely!
Review the Risks ! !
Customize your Android
Check next for more
Hit thanks, if helped :good:
BootLoop:
“Bootloop” is a very familiar term for smartphone users whatever OS they use, but it is definitely more familiar to Android phone users. Android being an Open Source operating system, is open to third party modifications. If you have a basic or advanced knowledge of Linux coding, you can develop a custom ROM or a modify a system file of your Android phone. Such openness has opened vistas for our great developers to cook ROMs, mods and hacks. It has enriched our experience with our phones at one hand, and posed a few problems like bootloop or a bricked phone in rare cases.
Most of phone- freaks like me spend their days doing nothing but trying almost all custom ROMs and mods available out there to tell other what is good for them. In doing so we often face a bootloop but that is not to say that only the third- party ROMs and mods are responsible for the problem. In most cases, however, it is some incompatible file imposed from outside that hinders the system files to work normally, resulting in a bootloop.
Thus, bootloop is a situation where the Android smartphones refuses to boot normally. There’s something wrong with the Android device, which is preventing it from completing the boot cycle and is stuck between the boot animation and the unlock screen. Bootloop is mainly caused when system files interfere with each other, causing instability, and crashes at the boot sequence.
While getting a bootloop on an Android phone is not a serious concern for an advanced user, it is surely enough to make a newbie or a noob tremble a little. Very often an average user begin to wonder if his phone is bricked or dead. In the present article I shall try to share with you some solutions that might help you recover your Android device from a bootloop.
Precautions to Avoid and Prevent Data Loss:
Bootloop is definitely one of the most undesirable situations a smartphone user can get into. It is shocking enough to make a new or basic user believe that he/she has bricked the device. It is true that in most cases you can recover your device to normal state but if you take precautionary steps, you could avoid it. Prevention is always better than the cure!
However, precautions cannot guarantee that you device is bootloop- proof. Therefore, it is also necessary that you always keep your phone’s data backed up. Remember, if your device gets into a bootloop, there are 90% chances that you will loose all your data, apps, settings and files stored on the internal SD of your device.
Things to be taken care of:
Before installing any stock or custom ROM, do not forget to confirm that it is made for your device and, more important, the same model number.
Before installing any custom Kernel, mod, patch or ROM, do not forget to backup your ROM. Also backup your phone’s apps, games, contacts, messages or any important data to an external storage-memory card, USB storage or your computer.
Avoid installing apps from outside Play Store and only those that are compatible with your device.
If your device is not rooted, you can use the official PC Suite from your device manufacturer.
Possible Reasons of a Bootloop on Android Device:
The reasons for getting a bootloop on your Android device might be anything. If you wish to know the reason why your Android phone is stuck on the bootloop, you need not type your problem on the Google search box. Just calm yourself for a while and think what you did just before. It could be anything! Here are some major reasons why your Android device is caught in a bootloop.
After installing an official or custom ROM
Flashing a wrong ROM or Kernel
Running an incompatible app or game
Wrong Permissions fix for an app or file
Installing a custom mod or theme
Most often we face a bootloop just after flashing a stock or custom ROM over an old one. This might be a major factor behind the bootloop issue on your device. Suppose you have flashed a new version of firmware over the old version. Your old data still remains on the device and the new firmware will use the Dalvik Cache from the old ROM that might not be compatible with the new system files and it will result in a bootloop. It mostly happen just when your device tries to reboot after you have flashed a stock or custom ROM. If this is the case, here is the solution.
If your device is on stock firmware, that also means it does not have a custom recovery like TWRP/CWM installed in it. Then do these steps:
1. Pull out the the battery of your phone, wait for about 30 seconds and reinsert it to its place.
2. Boot your device into ASR(Android System Recovery) mode. The method involves a hardware key combination and varies from one phone to another. For Samsung phones, for example, the key combination is Volume Up+Home + Power keys. The tablets which generally have no Home button, you can enter the Recovery mode bypressing and holding the Volume Up + Power keys simultaneously.
3. In the Android System Recovery, scroll down to “wipe cache partition” option using the volume rockers and select it using the power key.
4. When you have wiped the data/factory, go back to the main menu and reboot the device by “reboot system now” option.
5. If the device is still stuck on Boot animation pull out the battery again and repeat the above steps. This time also “wipe data/factory reset ” and then reboot device.
The bootloop problem should be fixed now.
If you have a rooted device with CWM recovery installed in it,and your phone is caught into a bootloop after flashing a custom ROM or mod, do as follows:
1. Pull out the battery, reinsert it after 30 seconds and boot the device into CWM Recovery: Volume Up+ Home + Power keys simultaneously.
2. Go to “Advanced”
3. Choose “Wipe dalvik-cache”
4. Now go to “Mounts & Storage”
5. Choose “Wipe/cache”
6. Reboot your phone
The bootloop should be gone now. If it still persists, do this.
1. Boot the phone again into CWM Recovery
2. Now go to “Mounts & Storage”
3. Choose “Wipe/data”
4. Choose “Wipe/cache”
5. Then reboot your phone.
Now the phone should reboot normally. Next time when you install a ROM, follow the instructions prescribed by the developer. Be more attentive to the warnings before experimenting with any third party ROM or mod. Always ensure what you are about to install is meant for your device.
If the Above Methods Do Not Work!
In case you are not able to get your device come out of bootloop, your final option should be to install or restore a previously backed up ROM by putting the device in recovery mode, or to install the official firmware/factory image to your phone your tablet.
Xposed Framework and Modules
Customization and flexibility lie at the core of Android and it is this potential that draws more and more people to it, making it the most loved platforms for mobile devices. I see Android as an assertion of freedom against some other major operating systems like iOS and Windows Phone. At the same time, it must be admitted that this liberty comes tagged with a check and can be experienced by only those who are adventurous in nature. An Android device in its maiden state is just a little better than devices from its opponents, but once rooted, its leaves all others far behind.
I do not mean that customization is not possible altogether on an unrooted phone or tablet. You can install 3rd party launchers and icon packs and decorate your home screens with a variety of widgets. However, the range of such type of personalization is limited to a certain level. By rooting your Android device, you get the key to unlock the whole next level of customization. If you have root access on your device, you can flash custom ROMs and mods to achieve not only true customization, but also improve its performance significantly not possible otherwise.
What is a Custom Framework?
In case you have a rooted device but you do not wish to install custom ROMs or mods, or a custom recovery is not available for it, there is yet another way of tasting the custom flavors of Android. And this can be done by installing a custom framework on your phone or tablet. All such frameworks modify the system.bin file replacing the original codes with those of the custom framework. The hacked system core then starts allowing changes imposed via custom modules. The best part of this whole business is that you can customize your device with stock firmware.
If you are not new to Android, you must have heard about some custom frameworks for Android like JKay, Xposed, 3Minit, etc. Developed by XDA member rovo89 is most popular of all its peers because of its potential and compatibility with almost all Android devices with Android 4.0 or above that house an ARM processor within them and are rooted.
How to Install Xposed Framework:
Download the latest Xposed Installer app. “Installing a custom framework” might sound a little geeky and complicated task to most new users. On the contrary, Xposed Framework can be installed very easily like a simple APK. All you have to do is to download the Xposed Installer app and install it on your device. Then open the app, select FRAMEWORK and tap on the “Install/Update” button. The app will ask you to grant
root permission, do it and wait for a while till you get an on-screen confirmation that the framework has been installed on your phone.
Now you have a custom base framework that can change the way you use your device with the help of compatible modules. Xposed Framework will not add any functionality to your device that can be used individually. Just search for Xposed modules and then you will be able to customize your device in various ways. The module files for the framework come as simple APK files and can be installed normally.
How to Install Xposed Framework Modules:
As I already mentioned above, it is the modules that let you customize your device and therefore, you will have to find and download the desired modules and install them separately on your device. Fortunately, the developer has now added the option to download modules right from the app’s interface. Open Xposed Installer and tap on “Download” option. You will now see a long list of available Xposed modules that can be downloaded. Just select the module you like and hit the Download button.
Besides the modules available in the app, you can find more at forums like XDA and others. After installing the modules, do not forget to select them in Xposed Installer. Launch the app, tap on “Modules” and check the newly installed module.
MultiROM:
MultiROM is one-of-a-kind multi-boot mod for Nexus 7. It can boot any Android ROM as well as other systems like Ubuntu Touch, Plasma Active, Bohdi Linux or WebOS port.Besides booting from device's internal memory, MultiROM can boot from USB drive connected to the device via OTG cable. The main part of MultiROM is a boot manager, which appears every time your device starts and lets you choose ROM to boot. You can see how it looks on the left image below and in gallery. ROMs are installed and managed via modified TWRP recovery. You can use standard ZIP files to install secondary Android ROMs, daily prebuilt image files to install Ubuntu Touch and MultiROM even has its own installer system, which can be used to ship other Linux-based systems.
Features:
* Multiboot any number of Android ROMs
* Restore nandroid backup as secondary ROM
* Use for example Ubuntu Touch (will be there in future) or Desktop alongside with Android, without the need of device formatting.
Currently, it has been ported to many Android devices !
Brick:
The term "brick" usually refers to the stone, which means: "device can only be used as paper-weight". Taken literally, there's no way to "unbrick".
However, you also find terms like "hard-brick" and "soft-brick" used, which makes the term "brick" less absolute: A soft-brick is something you easily can recover from (count it as a "temporary paper-weight"), mostly by software-based solutions (e.g. re-flash your phone) -- while a "hard-brick" is rather meant in the way the original term points to.
Still, technically spoken, even a "hard-bricked" device could be "unbricked" -- but mostly this is more expensive then getting a new device.
As for the warranty declaration you quoted: For a normal user, it's almost impossible to (hard-) brick his device. Even when flashing a custom ROM, this can rarely happen, as there are many security-layers involved. Almost always you can boot your device into some fall-back mode where it is at least recognized by some "flashing software", so you could simply flash another/the original firmware back. Which means, the risk you are taking is to "soft-brick" your device. A "hard-brick" is quite unlikely with "normal operations" like rooting or flashing custom ROMs.
Brick is a much-hyped word that gets bandied about with-out understanding what it is.
There's two types of brick, hard and soft. Lets go through this to make the distinction clearer.
Hard this is where the handset will absolutely refuse to boot at the press of the power button. Diagnostics: Dead screen, no power. That is the symptom of a hard brick. Reason: This can happen by inadvertently pulling the cable when flashing a ROM or even an update via the handset's supporting software such as Samsung Kies, Sony's PC Companion Suite etc. That is the worst case, that is why in this scenario, always, make, sure that no cable gets pulled unless told so by the supporting software in question. The other way is this, flashing in that manner when the battery power is low. Hence for that reason, it is recommended to have at least 75% of battery power in place prior to doing the update in that fashion. Its known as hard-brick, and requires specialist cables and stripping the device down to the circuitary board to revive it via JTAG cables.
Soft - this can happen through a bad flashing of the ROM in which yields the following. Diagnostics: it has power when the power button is pressed, and/or, the screen comes on. Reason: It can be a user error on this part. For example, failing to clear/wipe the data/cache, can cause Android to go into a boot-loop because of the mis-matches with the Android's virtual machine and the apps installed, or more than likely, a corrupted dalvik cache. The other, is flashing a ROM that is not designated for the handset which can cause the kernel to go into a boot-loop. This is generally easier to fix, but hangs, that is known as a soft-brick.
Review the risks ! !
Customize your Android
Hit thanks, if helped :good:
prince.d.emperor said:
Review the Risks ! !
Customize your Android
Hit thanks, if helped :good:
Click to expand...
Click to collapse
Thanks
Android's been here for quite a while noobs are champs now. But still a nice guide ..
I hope people using various kinds of vendor devices HTC,samsung , xperia , motorola will find this useful.
I also know this thread will be visible to few and not when needed .
kapil.git said:
Thanks
Android's been here for quite a while noobs are champs now. But still a nice guide ..
I hope people using various kinds of vendor devices HTC,samsung , xperia , motorola will find this useful.
I also know this thread will be visible to few and not when needed .
Click to expand...
Click to collapse
Then what is needed to be done??
Thnx

Categories

Resources