(INTRODUCTION TO ROOTING) New to rooting/flashing ANY Android? See this guide! - Android Software/Hacking General [Developers Only]

(INTRODUCTION TO ROOTING) New to rooting/flashing ANY Android? See this guide! - Android Software/Hacking General [Developers Only]

ROOTING
Rooting is a very popular thing to do with your android phone these days. It allows you to do a number of things you wouldn't normally be able to do, such as use apps that require root permissions (wifi tethering, real backups, etc), flash custom/cooked ROM's, flash kernels, remove bloatware. and overclocking. Before you attempt rooting however, there are several things you should know first:
"Rooting" is, in vernacular terms, the Android OS equivalent of say, jailbreaking an iPhone.
To be exact, it means several things:
Name for an administrator on Android or any other Linux system.
The lowest level in a file system (for example: the root of your SD card would be the screen that comes up when you first open it, no other sub-folders.)
It also means having administrative powers over your phone.
It also voids your warranty if your phone company finds out.
So basically, by extension, rooting a phone means giving yourself rooting privileges. Think of it like this: Say you have an HTC Evo. Android is open-source, but you're only allowed to do on the phone what Sprint allows you to. Sprint wants to charge people $30 or $40 per month to do wifi tethering. A rooted phone could do wifi tethering for free, as you would be the administrator, and override the block.
PROS and CONS
1. Pros
Superuser permissions (full control over your phone, down to terminal commands).
Use root-requiring apps (wifi tether, backups, etc).
Over/underclocking
Ability to use a custom recovery.img (for flashing).
Flash custom ROMs and kernels
Flash other .zip files
Removing bloatware (apps that you don't want or need but can't normally delete)
Upgrading your firmware to later versions (such as phones that won't get the Froyo update)
2. Cons
Voided warranty
Possibility of bricking device
Possibility of damaging hardware
The cons are easy to avoid, as long as you do everything correctly and do your research first. As for your warranty, it's often just easier to say your phone was lost. If it's still covered by warranty, then you could be covered for it.
ROOTING METHOD
For how to root your phone, the internet is your best friend. However, if you are not comfortable, then look to see if you can get someone experienced to do it! All rooting will require you to put your phone in USB Debugging mode as well, which is turned on by going to Menu-->Settings-->Applications-->Check the USB Debugging box. My personal favorite resources are:
Software/apps:
Unrevoked
OneClick
SuperOneClick
z4root
Written Instructions:
Cyanogenmod Wiki
My Blog! (Still growing)
XDA Developers
Video Instructions:
Youtube
(See my youtube vids)
The Unlockr
For having someone do it for you: See craigslist. Someone may be offering the service or you can ask for it.
ALWAYS DO YOUR RESEARCH FIRST!
GROUND BASICS OF OPERATING A ROOTED PHONE:
A rooted phone acts the same as a non-rooted phone. The difference is usually under the hood.
You will need an application called "Superuser", downloadable from the app market. Most rooting methods install this automatically. It will have one of these two icons:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Any time something requires root permissions, it will ask for them. The first time around, you'll get a popup screen like this.
Just checkmark next to "remember" and you won't be prompted in the future.
Some popular apps that require superuser permissions:
Wifi Tethering - Self explanatory.
Titanium Backup - A powerful app for backing up your apps and data and restoring them (very useful if switching phones or if you wipe yours).
Autokiller - A powerful memory optimizer, helps with battery.
Overclock Widget - A widget that lets you overclock or underclock your processor. This requires a compatible kernel, which we'll get to in a second.
ROMs
ROM technically means "Read Only Memory", or your flash memory. In Android context though, it means porting a different firmware onto the phone. This is really where the magic of open-source comes into play:
ROMs usually come in ".zip" file format. DO NOT upzip them
ROMs are customized firmwares for your phone. "Customized" and "Cooked" are synonymous in Android context, and developers are the chefs. A ROM can be:
A minimalistic, fast firmware, and have certain features unlocked.
Upgrade your phone to 2.2 or 2.3 if you're stuck on an older firmware.
A completely new look and feel for people who don't like how their phone UI currently is (prevalent with many HTC Sense users).
An overclocking monster.
An undervolted battery saver.
Some combination of the above.
A quick way to brick your phone.
Bricking means your phone is an expensive paperweight, a "brick". Dead.
Notice the last bit about bricking. This is the biggest underlying risk in the rooting business. Many phones have corresponding software that will root the phone for you (Unrevoked, OneClick, SuperOneClick, z4root), but flashing is done manually, and someone who doesn't know what they're doing can brick their phone. Here is a basic guide to flashing:
Download a ROM
Good places to look are XDA or Cyanogenmod.
ROM Labels:
Vanilla - The stock ROM that comes standard on a phone.
CM - Cyanogenmod (or based on)
BACK UP YOUR INFORMATION.
This includes apps, contacts, texts (optional), and call logs (also optional).
You need to install a custom recovery, such as Amon Ra or Clockworkmod. They are both usually as easy to flash, and work generally the same.
Many softwares for rooting, such as Unrevoked, flash a new recovery image automatically.
If your method didn't, you can download an app called ROM Manager from the market. After installation, open it, and click "Flash Clockworkmod Recovery".
If the first two steps didn't work, then you'll have to research a way how.
Go to recovery mode, either from ROM Manager or manually.
Look up how to boot into recovery. For most phones, you'll navigate to it from the bootloader. which is started by turning on your phone while holding some combination of volume/camera buttons and the power button. Bootloader looks like this on most phones, though some vary (particularly Galaxy phones):
Your recovery will look like this:
Now there are a couple of important rules of thumb with flashing:
Always make a NANDROID backup. Navigate to it from the "nandroid" option in recovery. This is a little different than just backing up your contacts and pictures. It backs up your phone system as-is, like a sort of picture (metaphorically of course) of that moment. This gives you something stable to come restore to if something goes wrong.
When flashing a new ROM, if it's not just an update of the one you currently have, you SHOULD "wipe data/factory reset" and "wipe cache partition". Your information we backed up earlier is on your SD card, which remains untouched.
Now, ready to continue?
Select "install zip from sdcard", then "choose zip from sdcard".
Navigate to your ROM zip(s).
Select it, then scroll down to "YES".
LET IT FINISH. DO NOT TOUCH ANY BUTTONS.
Steps 1-4 of this section are what "FLASHING" means.
When it's done, repeat steps 1-4 of this section for any other zip files associated with it (themes, kernels, tweaks, etc)
When you're done, navigate back to the initial screen of your recovery mode using the "***go back***" options at the bottom of each list. From here, select "reboot phone now".
It will install any remaining packages now. Again, LET IT DO ITS WORK.
Your phone will reboot. If it locks up on boot, try reflashing, or if it just won't work, restore from a NAND backup.
There you have it. A new ROM is a big plus to many with androids. Those who are stuck with 2.1, or even 1.6 and 1.5 now can get a 2.2 ROM and upgrade their firmware, etc. You will no longer receive updates from your provider though, so it is your responsibility to keep your phone up to date by checking the developer's ROM updates, or if you like it as is and don't mind, just keep it like it is for all time.
KERNELS
Kernels are the lowest part of a system's software. It controls memory related things as well as processor things. It manages the communication between the hardware and the software, and caution should be exercised.
Kernels are flashed the same way ROMs are.
Many developers will recommend or develop a kernel to go along with their ROM.
Custom kernels are often needed to do overclocking, or undervolting (for battery optimization), etc.
Also downloaded from XDA and such.
Make sure you do your research and that it's compatible with your phone and/or ROM!
RADIOS, WIMAX, AND OTHERS
Often time you can flash updated versions of your phone's radio and wimax. Download and flash these like you would a ROM.

Thank you! Great guide, simple and clear

Thanks! Please continue commenting to keep this thread from getting buried.
Sent from my PC36100 using XDA App

Do i need a new kernel (patched) to create a custom recovery or i can use the original kernel with moded ramdisk?
Can you give same direction for create a custom recovery?
Thank you.
Sent from my Ideos S7 using Tapatalk

Just curious, but any reason you don't have the UniversalAndroot app on your list? I have used it for my old HTC (GSM) Hero, Moto Milestone and a Chinese Android tablet.

I just listed a few off the top of my head, I didn't mean to diss any software

awesome thread... thank you

Can you post a guide to getting usb debugging to work if it is not inside settings? I can't figure out how to do that.

pandafloski said:
ROOTING
Rooting is a very popular thing to do with your android phone these days. It allows you to do a number of things you wouldn't normally be able to do, such as use apps that require root permissions (wifi tethering, real backups, etc), flash custom/cooked ROM's, flash kernels, remove bloatware. and overclocking. Before you attempt rooting however, there are several things you should know first:
"Rooting" is, in vernacular terms, the Android OS equivalent of say, jailbreaking an iPhone.
To be exact, it means several things:
Name for an administrator on Android or any other Linux system.
The lowest level in a file system (for example: the root of your SD card would be the screen that comes up when you first open it, no other sub-folders.)
It also means having administrative powers over your phone.
It also voids your warranty if your phone company finds out.
So basically, by extension, rooting a phone means giving yourself rooting privileges. Think of it like this: Say you have an HTC Evo. Android is open-source, but you're only allowed to do on the phone what Sprint allows you to. Sprint wants to charge people $30 or $40 per month to do wifi tethering. A rooted phone could do wifi tethering for free, as you would be the administrator, and override the block.
PROS and CONS
1. Pros
Superuser permissions (full control over your phone, down to terminal commands).
Use root-requiring apps (wifi tether, backups, etc).
Over/underclocking
Ability to use a custom recovery.img (for flashing).
Flash custom ROMs and kernels
Flash other .zip files
Removing bloatware (apps that you don't want or need but can't normally delete)
Upgrading your firmware to later versions (such as phones that won't get the Froyo update)
2. Cons
Voided warranty
Possibility of bricking device
Possibility of damaging hardware
The cons are easy to avoid, as long as you do everything correctly and do your research first. As for your warranty, it's often just easier to say your phone was lost. If it's still covered by warranty, then you could be covered for it.
ROOTING METHOD
For how to root your phone, the internet is your best friend. However, if you are not comfortable, then look to see if you can get someone experienced to do it! All rooting will require you to put your phone in USB Debugging mode as well, which is turned on by going to Menu-->Settings-->Applications-->Check the USB Debugging box. My personal favorite resources are:
Software/apps:
Unrevoked
OneClick
SuperOneClick
z4root
Written Instructions:
Cyanogenmod Wiki
My Blog! (Still growing)
XDA Developers
Video Instructions:
Youtube
(See my youtube vids)
The Unlockr
For having someone do it for you: See craigslist. Someone may be offering the service or you can ask for it.
ALWAYS DO YOUR RESEARCH FIRST!
GROUND BASICS OF OPERATING A ROOTED PHONE:
A rooted phone acts the same as a non-rooted phone. The difference is usually under the hood.
You will need an application called "Superuser", downloadable from the app market. Most rooting methods install this automatically. It will have one of these two icons:
Any time something requires root permissions, it will ask for them. The first time around, you'll get a popup screen like this.
Just checkmark next to "remember" and you won't be prompted in the future.
Some popular apps that require superuser permissions:
Wifi Tethering - Self explanatory.
Titanium Backup - A powerful app for backing up your apps and data and restoring them (very useful if switching phones or if you wipe yours).
Autokiller - A powerful memory optimizer, helps with battery.
Overclock Widget - A widget that lets you overclock or underclock your processor. This requires a compatible kernel, which we'll get to in a second.
ROMs
ROM technically means "Read Only Memory", or your flash memory. In Android context though, it means porting a different firmware onto the phone. This is really where the magic of open-source comes into play:
ROMs usually come in ".zip" file format. DO NOT upzip them
ROMs are customized firmwares for your phone. "Customized" and "Cooked" are synonymous in Android context, and developers are the chefs. A ROM can be:
A minimalistic, fast firmware, and have certain features unlocked.
Upgrade your phone to 2.2 or 2.3 if you're stuck on an older firmware.
A completely new look and feel for people who don't like how their phone UI currently is (prevalent with many HTC Sense users).
An overclocking monster.
An undervolted battery saver.
Some combination of the above.
A quick way to brick your phone.
Bricking means your phone is an expensive paperweight, a "brick". Dead.
Notice the last bit about bricking. This is the biggest underlying risk in the rooting business. Many phones have corresponding software that will root the phone for you (Unrevoked, OneClick, SuperOneClick, z4root), but flashing is done manually, and someone who doesn't know what they're doing can brick their phone. Here is a basic guide to flashing:
Download a ROM
Good places to look are XDA or Cyanogenmod.
ROM Labels:
Vanilla - The stock ROM that comes standard on a phone.
CM - Cyanogenmod (or based on)
BACK UP YOUR INFORMATION.
This includes apps, contacts, texts (optional), and call logs (also optional).
You need to install a custom recovery, such as Amon Ra or Clockworkmod. They are both usually as easy to flash, and work generally the same.
Many softwares for rooting, such as Unrevoked, flash a new recovery image automatically.
If your method didn't, you can download an app called ROM Manager from the market. After installation, open it, and click "Flash Clockworkmod Recovery".
If the first two steps didn't work, then you'll have to research a way how.
Go to recovery mode, either from ROM Manager or manually.
Look up how to boot into recovery. For most phones, you'll navigate to it from the bootloader. which is started by turning on your phone while holding some combination of volume/camera buttons and the power button. Bootloader looks like this on most phones, though some vary (particularly Galaxy phones):
Your recovery will look like this:
Now there are a couple of important rules of thumb with flashing:
Always make a NANDROID backup. Navigate to it from the "nandroid" option in recovery. This is a little different than just backing up your contacts and pictures. It backs up your phone system as-is, like a sort of picture (metaphorically of course) of that moment. This gives you something stable to come restore to if something goes wrong.
When flashing a new ROM, if it's not just an update of the one you currently have, you SHOULD "wipe data/factory reset" and "wipe cache partition". Your information we backed up earlier is on your SD card, which remains untouched.
Now, ready to continue?
Select "install zip from sdcard", then "choose zip from sdcard".
Navigate to your ROM zip(s).
Select it, then scroll down to "YES".
LET IT FINISH. DO NOT TOUCH ANY BUTTONS.
Steps 1-4 of this section are what "FLASHING" means.
When it's done, repeat steps 1-4 of this section for any other zip files associated with it (themes, kernels, tweaks, etc)
When you're done, navigate back to the initial screen of your recovery mode using the "***go back***" options at the bottom of each list. From here, select "reboot phone now".
It will install any remaining packages now. Again, LET IT DO ITS WORK.
Your phone will reboot. If it locks up on boot, try reflashing, or if it just won't work, restore from a NAND backup.
There you have it. A new ROM is a big plus to many with androids. Those who are stuck with 2.1, or even 1.6 and 1.5 now can get a 2.2 ROM and upgrade their firmware, etc. You will no longer receive updates from your provider though, so it is your responsibility to keep your phone up to date by checking the developer's ROM updates, or if you like it as is and don't mind, just keep it like it is for all time.
KERNELS
Kernels are the lowest part of a system's software. It controls memory related things as well as processor things. It manages the communication between the hardware and the software, and caution should be exercised.
Kernels are flashed the same way ROMs are.
Many developers will recommend or develop a kernel to go along with their ROM.
Custom kernels are often needed to do overclocking, or undervolting (for battery optimization), etc.
Also downloaded from XDA and such.
Make sure you do your research and that it's compatible with your phone and/or ROM!
RADIOS, WIMAX, AND OTHERS
Often time you can flash updated versions of your phone's radio and wimax. Download and flash these like you would a ROM.
Click to expand...
Click to collapse
I have a Galaxy 3 phone and am completely new to rooting and based in Bangalore, India. Is there a one-click app for G3 which can root my phone automatically without much of my intervention and is it safe to use this app?

Informative thread, thanks.

I'm not sure there's a way to do that

I have noooo idea. I have no experience with that phone :/

Zinglife rooting is making me mad , pls help!
how to install adb drivers if no drivers are provided , superoneclick ,z4root all fail rooting my zinglife tablet..link to my thread in my signature

Related

[CDMA][TUTORIAL SET]CDMA Desire Informational Thread

HTC Desire CDMA (BravoC) Thread
I wanted to create this thread to show that there are CDMA Desire users that there are users that want to help ourselves, and we need more ROMs! With the addition of 1.06 HBOOT Desire's being able to be rooted now, there is a large influx of these users new to rooting.
Most of the content was rewritten by me, but I must give thanks to the XDA Forums, Cyanogenmod Forum, Team US Cellular Forums, MIUI forums, and 2fast ROMS! This took a while to put together for me!
Of course, thanks to fllash for the Desire Index thread and for being awesome, but with the influx of CDMA users, it's time to branch off slightly.
This was written by a US Cellular user, but most information is for all CDMA phones. I have owned both a 0.98 HBOOT and a 1.06 HBOOT device.
Contents:
Tips
ROM List
Rooting Guide 0.98
Rooting Guide 1.06
Backup Guide
USCC Return to Stock Guide
USCC Lost 3G Fix - ADDED 7/24
Tips for CDMA Users:
Red comments are by 2fast4u88
Blue comments are rebuttals by me.
Most things in this forum are for GSM users, the CDMA Desire was added a year ago but never got an official forum on XDA.
Your phone is CDMA if you do not have a SIM card port by your SD card.
CDMA users do not need to worry about radio's as much as GSM users do. Most CDMA desire's only have 1 or 2 different radio's depending on the carrier.
It is recommended to not mix h-boots and radios. Use the radio with the right h-boot. The newer radio's have better battery life. The older radio's have better signal strength
Don't worry people, I haven't seen a ROM that updated your radio without specifying it very well before you download!
CDMA users do not need to use different HBOOT images for ROMs.
Gsm roms do not need h-boots. All the modded h-boots are for is for memory like cmtd does for us.
Backup your APNs!
You do not need to backup your apn list when the rom dev supply's the zips to flash.
Not all ROM devs supply this unfortunately, and it's always useful to have one just in case, especially with easy apps like APNs Backup & Restore!
There is no Gingerbread Sense ROM for CDMA users yet. Official Gingerbread for the Desire will not have Sense built in due to the limited space on the Desire's memory.
Gingerbread update will have sense but with some stuff downloadable last I heard. Even the the uscc desire will not have it along with probably other carriers. Uscc made it public one update per device.
Yeah, unfortunately it's not likely to happen for us CDMA users.
If you do any fixes to your phone like repairing your 3G service (detailed below for USCC members) or getting your MSL Number, you must do so on a Sense ROM with EPST.apk, which most Sense ROMs have. Keep a backup of your original ROM! The official 2.3 update should fix this problem, but no guarantees.
What are you even talking about here in all honesty? There is no issue flashing anything that I am aware to break 3g?
On the Cyanogenmod forums, a lot of people happen to ask about lost 3G service for US Cellular, and many of these people are roaming. I've had this happen to me and found the official fix by the USCC Roaming Tech Support. Guide added to the third post!
If you ever ask for support, specify you're a CDMA user and your carrier.
Use BravoC recoveries, not Bravo!
If you need more space for apps, use either App2SD, Data2SD/EXT, CMTD, or for CM7: S2E from the market.
This a problem a little bit and bugs me everytime I see it. Skuddy is the only one to use data2sd. All the other roms running what is to be called data2sd is a knock of of darktremors apps2sd+ with out dalvik moved. Also every rom has one built in so using a app to do it is going to cause issues.
The market app S2E seems to be a universal Cyanogenmod addon that works on most devices. I personally use and love it.
DO A NANDROID BACKUP
Only needed for having a backup of sense. If you have a ruu it isn't needed. You can of course due backups of a rom if you want but isn't needed everytime. I don't waist my time with backup's anymore.
Yes, but it's good practice for those who are just starting, as they're very likely to miss a step when flashing a ROM, or trying out CMTD for the first time.
-------------------------------------------
ROM List:
Gingerbread (Android 2.3.x) ROMS:
Oxygen - http://forum.xda-developers.com/showthread.php?t=971904 USE THE CDMA LINK TO DOWNLOAD
Cyanogenmod 7.0.3 (CM7 CDMA) - http://forum.cyanogenmod.com/topic/20119-cyanogenmod-7-for-the-htc-desire-cdma-v703-5-may-2011/
Cyanogenmod 7.1-RC1 - http://forum.cyanogenmod.com/topic/...or-the-htc-desire-cdma-v710-rc1-26-june-2011/
Etheral - http://teamuscellular.com/Forum/viewtopic.php?f=27&t=381
MIUI - http://2fastroms.com/viewtopic.php?f=23&t=139
Dirty Money - http://2fastroms.com/viewtopic.php?f=23&t=128&sid=4c702bfc9aeb69582f22198bf5c04eaa
Phoenix 2.x - http://2fastroms.com/viewtopic.php?f=23&t=46&sid=4c702bfc9aeb69582f22198bf5c04eaa
Froyo (Android 2.2.x) ROMS:
Rooted US Cellular Stock 2.2 - http://forum.xda-developers.com/showthread.php?t=947481
ThunderSense - http://www.teamuscellular.com/Forum/viewtopic.php?f=71&t=427
SleekSense Stable - http://2fastroms.com/viewtopic.php?f=23&t=16&sid=4c702bfc9aeb69582f22198bf5c04eaa
Sensible 1.1 - http://2fastroms.com/viewtopic.php?f=23&t=12&sid=4c702bfc9aeb69582f22198bf5c04eaa
LeeDroid CDMA Port - http://forum.xda-developers.com/showthread.php?t=1183020
RUUs (Stock ROMs, used to update or return to stock)
US Cellular Stock 2.2 Update - http://www.htc.com/us/support/desire-uscellular/downloads/ Look at the third post for more information.
Alltel - http://shipped-roms.com/download.ph...8.11_NV_Alltel_1.70_release_150765_signed.exe
-------------------------------------------
More information in the next 2 posts!

Rooting Guides
DISABLE HTC SYNC ON YOUR PC
THIS WILL VOID YOUR WARRANTY, at least software wise. Insurance should still cover physical damage I believe.
-------------------------------------------
How to root HBOOT 0.98:
To make this easier, create a new folder on your desktop (or wherever you prefer) to hold everything. Let's name it Rooting.
Download unrEVOked: http://unrevoked.com/recovery/
If you're on Windows, you'll need special drivers. Linux and Mac user's have it easy for this one.
When I rooted my first Desire, they instructed to install HTC Sync then uninstalling it, which keeps the drivers on your system. While some say these drivers aren't the best ones, they will most likely work anyway.
You must also install the unrEVOked HBOOT drivers located here: http://unrevoked.com/rootwiki/doku.php/public/windows_hboot_driver_install
You can either follow the guide in the link above, or follow this one:
Driver Download (WINDOWS ONLY): http://unrevoked.com/rootwiki/lib/e...unrevoked.com/recovery/android-usb-driver.zip
New recovery (ClockworkMod 4.0.1.0 by 2fast4u88): http://2fastroms.com/viewtopic.php?f=22&t=40
Open the zip and place the recovery image in the folder like pictured below.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
1) If on Windows: Unzip the contents of the driver zip file into a folder inside the folder we're using to keep everything together. Let's rename this folder to Android HBOOT Driver. Download the UnrEVOked program and place into the rooting folder. Save the recovery to the same folder.
2) Turn off the phone and make sure it's unplugged. Hold down the Volume Down button first, then hold the power button. You should see 3 Androids on the bottom of the screen, you are now in HBOOT. It will check your SD card whenever it goes in here, so don't worry if it takes a second.
3) Make sure your HBOOT is 0.98, the second line of text should say something like HBOOT-0.98. If it is 1.06, check the other guide.
4) Plug in your phone. If you're on Linux or Mac, skip the rest of this step. Windows will look for a driver and likely fail, and your phone should say HBOOT USB PLUG. We will now install the driver. Make sure you're an administrator on your computer! Click on the Start button and right click on Computer, then click on Manage. A window will open, and click on Device Manager on the left hand side. (OR just search for Device Manager in the search bar). Look for Other Devices, expand the list and you'll see Android 1.0. Right click on this and choose Update Driver Software, click browse and find the folder you extracted your driver files to. You'll get a warning about unsupported drivers and clikc Yes/OK. You should now see Android Phone at the top with an entry named Android Bootloader Interface. It is recommended to restart your PC after this. Might want to bookmark this thread and return!
5) Now unplug your phone and turn if off (Pull out the battery or use the Volume Buttons and Power button to navigate the menu to select fastboot, then select reboot). Once rebooted, go to your home screen and press Menu and choose settings. Go to Connect to PC, select Default connection type, select Charge only and uncheck Ask me.
6) Go back to settings, choose Applications, select Development, and check USB Debugging, and go back to Applications and check the Unknown Sources.
7) Run reflash_package.exe and select custom recovery, and select recovery-bravoc-3.0.2.8.img.
8) Plug in your phone and start the process. Your phone will reboot a few times, DO NOT UNPLUG YOUR PHONE. Wait until unrEVOked says done! You should be rooted,S-OFF, and custom recovery! Install Titanium Backup from the market to make sure your phone is rooted then follow the Backup Guide! Backup your APNs as listed below!
-------------------------------------------
-------------------------------------------
How to root HBOOT 1.06:
To make this easier, create a new folder on your desktop (or wherever you prefer) to hold everything. Let's name it Rooting.
Download AlphaRevX Beta: http://alpharev.nl/x/beta/
Keep this page open, because while running the program you'll need to generate a key.
Clockworkmod 4.0.1.0 by 2fast4u88 Fastboot Recovery Image A.K.A. PB99IMG for ClockworkMod: http://2fastroms.com/viewtopic.php?f=22&t=40
Extract the zip file and place PB99IMG.zip like pictured below.
If you're on Windows, make sure to install the Windows drivers provided on the page or get them from here: http://www.multiupload.com/2OFYWZFCCR
1) Turn off the phone and make sure it's unplugged. Hold down the Volume Down button first, then hold the power button. You should see 3 Androids on the bottom of the screen, you are now in HBOOT. It will check your SD card whenever it goes in here, so don't worry if it takes a second. Make sure you have HBOOT 1.06 and you have S-ON. If your Desire has S-OFF, skip to step 7.
2) Unzip the AlphaRevX file into a folder inside the rooting folder and name it AlphaRevX. Place the other 2 files in the rooting folder.
3) Install the HTC Drivers, it should be fairly easy to follow its instructions.
4) Go to your home screen and press Menu and choose settings. Go to Connect to PC, select Default connection type, select Charge only and uncheck Ask me. Go back to settings, choose Applications, select Development, and check USB Debugging, and go back to Applications and check the Unknown Sources.
5) Plug in your phone, and run AlphaRevX. Go back to the AlphaRevX download page and enter in the details provided to you. Copy the serial number, and right click paste into the window. If right click doesn't work, right click the top left icon in the window, choose Edit>Paste. Hit enter, and it should follow the process. It will reboot your phone, DO NOT UNPLUG YOUR PHONE UNTIL IT IS SAFE.
6) Once completed, your phone should be rooted and S-OFF, but not recovery. Close AlphaRevX and install Titanium Backup from the market to see if you have root, and follow the Backup guide after finishing the next few steps. In case you're just S-OFF, but no root access, you have two options: Try SuperOneClick: http://forum.xda-developers.com/showthread.php?t=803682 Or Try unrEVOked found in the 0.98 HBOOT Guide.
7) Now we must install custom recovery, place the PB99IMG.zip file onto the the SD card, do not place it into a folder. Once copied, unplug your phone and turn it off. Go back into HBOOT by holding down Volume Down and then the Power button. This time, when it does its scan, it will find the PB99IMG.zip file. It should say Press Volume Up to apply update or something like that. Your phone will reboot normally, and then remove PB99IMG.zip from your SD card. Finally, turn off your phone again, boot into HBOOT and select recovery, and you should see ClockworkMod 3.0.2.8 boot up. Finally you are done with the rooting process!
-------------------------------------------

-------------------------------------------
Backup Guide
There are many processes to backup your phone. We can divide these processes into 2 categories:
DATA BACKUP and NANDROID BACKUP
Data backups are backups of certain things such as Apps, Data, Text messages, and even system preferences.
-------------------------------------------
Nandroid backups are backups of everything on the phone, from every partition of SYSTEN, DATA, BOOT, SD-EXT, CACHE, and .ANDROID_SECURE. This is a byte-for-byte copy of everything on your phone (and if you have a partitioned SD Card).
System is your phone's ROM area, holding the internal components of the ROM and the built in apps.
Data is the area where applications and app data is kept if not installed to the SD Card.
Boot is the ROM's boot image. You will have very little interaction with this.
SD-EXT is on your SD Card, standing for SD EXT Partition. EXT2/3/4 is a file system used by linux (which android uses) and can be used to store data. Commonly used for Apps2SD or Data2SD/Data2EXT.
Cache is the area on your phone that data is temporarily written to, like web page content and app data.
.Android_secure is used for the normal Android Apps to SD system. Some apps keep data on your sd card.
Before you EVER DO ANYTHING like flashing another ROM, or try a modification like Data2SD or other ROM modifying scripts, DO A NANDROID BACKUP. This is the most important thing you'll ever need in case soemthing goes wrong.
-------------------------------------------
Data backups are backups of parts inside the phone, and certain parts such as user apps and app data can be applied to whatever ROM you use. Say you are going from your Stock Sense ROM and you want to try Cyanogenmod, but you don't want to replay all your games like Plants Vs Zombies and Angry Birds. Using an app like Titanium Backup, you can backup the app and all of its data and restore it on another ROM like nothing happened.
Data backups can even include things like ringtone settings, text messages, preferences, and contact data.
If you care about anything like those on your phone, you should do a weekly backup.
-------------------------------------------
Nandroid backups are completed by your recovery image. Say you want to do a Nandroid backup on Clockworkmod, you simply boot into recovery, select Backup and Restore, and choose Backup (make sure you have enough space on your SD card, such as 1GB free). The process will copy everything on your phone and place into a folder on your SD card, and you can restore these backups any time you like.
Data backups are done by certain apps. Titanium Backup and My Backup (Normal or Pro) are the common suggestions. Titanium Backup has been around forever and works great, but My Backup will also backup other things like text messages, call logs, and other core phone features. I personally use Titanium Backup, SMS Backup and Restore (https://market.android.com/details?id=com.riteshsahu.SMSBackupRestore His other apps are useful as well).
-------------------------------------------
Titanium Backup Guide
Once you are rooted and install Titanium Backup, if you're on Stock ROM, open up Titanium Backup, and hit the Problems? button in the bottom center. There should be a Upgrade or install Superuser button, which is required for many root options and required for backing up! Install it!
For a quick and easy app backup, just go to Titanium Backup and hit Menu, then select batch. Find the Backup all user apps + system data option with the button that says RUN in black. Hit Run the batch operation at the top, and make sure you have enough space on your SD card, around 200mb. It will now start the backup and complete in a few minutes. The more apps, the more time it takes.
When you install your new ROM, install Titanium backup (Superuser is built into most custom ROMS) and hit menu, Batch. Find Restore missing apps + all system data. Some ROM apps will clash, like camera and dialer, so uncheck those and reinstall them manually.
-------------------------------------------
One of the most important things to do is to backup your APNs. APNs are what allow for picture messaging/MMS and in some cases internet browsing. This app will streamline the process: https://market.android.com/details?id=com.riteshsahu.APNBackupRestore
Simply backup the APNs from your stock ROM and restore them onto any ROM you'd like.
If you must remake your APN and you are on a US Cellular Desire, this should help you:
http://teamuscellular.com/Forum/viewtopic.php?f=72&t=60
I would suggest making a Sense APN backup and a non-Sense APN backup and restore one to whichever ROM you're using.
-------------------------------------------
-------------------------------------------
Returning to Stock (US Cellular users)
So say your phone screen cracked somehow, like your girlfriend had it in her lap, and she got out of the car. Concrete + perfect angle + force of gravity = cracked glass. (I still love her don't worry)
Hopefully you have insurance on your phone, and the software works fine and the touch screen works.
For those returning it, you should definitely flash back to the stock ROM or apply the 2.2 Update. This will not S-ON your phone, but it likely won't matter.
To do this, proceed to http://www.htc.com/us/support/desire-uscellular/downloads/ and follow its instructions for installing the update. However, many people have problems with this, but don't worry, I found out how to install the update without the program working.
1) Download the update and open the executable file. It will unpack the files to the temporary directory (%temp%) but we can find this easily. After opening it and waiting for it to complete unpacking, open your task manager and find either ARUWizard.exe or ISBEW64.exe. Right click on one of these files, click Open File Location. Find rom.zip, which should be about 163mb. Copy this into a folder of your choosing, like Rooting/Stock Froyo.
2) Do a Nandroid Backup on your phone!
3) Rename the rom.zip into PB99IMG.zip and place onto your SD Card of your phone.
4) Reboot into HBOOT (Hold Volume Down and Power) and it should find it with seconds, but will take a minute to load.
5) Apply the update, and you should be back to Stock Froyo. Your HBOOT will be 1.06, but you will be S-OFF still. They most likely won't care.
Optional steps!
6) Say you're on US Cellular, and need to send it back to Assurant Solutions, the insurance carrier of US Cellular. You will need a $100 deductable payment. They should send your new Desire in the mail pre-loaded with Froyo, along with a return envelope. Take out your SD card of your old phone, and place your old phone in the envelope.
7) Take your new phone and activate it by calling 888-944-9400 on another phone or Google Voice on the desktop, follow the menu to talk to a representative by dialing zero as your last step. Make sure to have the ESN DEC number of the new phone (Under the phone or on the box), the last 4 digits of the account holder's Social Security Number, and of course the phone number.
8) The person you speak to will activate the phone and ask you to dial *228 to update the PRL, which will take about 2 minutes. Say thanks to the helpful representatives!
9) Follow the rooting guide for HBOOT 1.06, restore ClockworkMod, (optionally nandroid the stock ROM), and restore the update for your previous ROM.
10) Go get a good protective case for your phone and KEEP IT ON.
-------------------------------------------
-------------------------------------------
Lost USCC 3G/1x Fix
For some reason, for a select few users, they lose 3G service, and in some cases 1x all together! If this happens to you, don't fret! USCC Tech Support is great, just don't tell them that you're rooted. In most cases, these fixes are only avaliable for Sense ROMs, because EPST.apk is a Sense-Framework only tool that handles core functions of the phone, such as programming the number and other items. If you need to call tech support, flash a Sense ROM or the best case: your stock ROM. Keep a Nandroid restore set of your stock rom backup up on your computer or dropbox just in case this happens. This is the official fix they gave me.
While attending college 100 miles away from all US Cellular Towers, my 3G lost service. When you roam on a USCC device, you're bouncing off of Verizon towers, and sometimes they block your device for some reason. Not even Tech Support always knows why. I had them send me the fix since I had to run to class, and I noticed on the Cyanogenmod forums a lot of people lose their data signal, so I shared it for them.
[COLOR="#FF00000"]YOU MUST DO THIS ON A SENSE ROM, STOCK IS PREFERRED. ROOTED OR NOT.
CALL TECH SUPPORT FIRST, THEY'LL GIVE YOU YOUR SUBLOCK CODE AND GUIDE YOU THROUGH THIS.[/COLOR]
You can find your Sublock code (MSL) by getting the MSL Reader app from market and running it on your stock ROM.
When finished, make sure your data works, and then you can boot back into whatever ROM you'd like.
HTC Desire
1. Press "Phone," dial ##778#.
2. The screen will display EPST "View Mode," "Edit Mode," Select "Edit Mode."
3. Enter the SUBLOCK code, press "Ok."
4. The screen will show about 20 different fields.
5. Tap on "Modem Settings."
6. Tap on "Preferred Mode.
7. Tap on “CDMA Only”, Press "OK".
8. Tap on "HDR Hybrid Preferred."
9. Tap on "Disable". Press "OK."
10. Press the "Menu" button at bottom of phone.
11. Tap on Commit Modifications.
12. Press OK to reset device.
13. The phone will reboot and "1X" will appear at the top. . Your customer should now be able to access data.
14. When the customer returns to our coverage area, go through the same process and reselect "Automatic" in the "Preferred Mode" and "Enable" in the "HDR Hybrid Preferred."
Click to expand...
Click to collapse

great thread, we needed something like this for us unloved cdma users. its good to have all the cdma stuff in one place for everyone to access.

Wow! Thundersense is not one im familar with..

http://2fastroms.com/viewforum.php?f=23
Add those to the roms. Sleeksense is the only froyo rom with working undervolt and faster than any of the other sense roms also.

Added a couple of those that seem to be updated the most. Also, since you know your ROMs, what is your explanation on why we don't have CDMA Gingerbread Sense ROMs?

Change the miui links as my forum has the most up to date miui's since myself and skuddy does them for miuiandroid.
As for why we don't have gingerbread sense. It would probably be because we don't have a leak. No leak no kernel. No source no kernel made easy.

2fast4u88 said:
Change the miui links as my forum has the most up to date miui's since myself and skuddy does them for miuiandroid.
As for why we don't have gingerbread sense. It would probably be because we don't have a leak. No leak no kernel. No source no kernel made easy.
Click to expand...
Click to collapse
So I'm guessing there's no way to port the GSM leaked kernel? After all, the EVO 4G uses the same processor, or does this factor other things like the built in memory and others?

any way we can help get the kernel out faster? like email htc once a day asking about a kernel source for the desire?

darkmage1991 said:
any way we can help get the kernel out faster? like email htc once a day asking about a kernel source for the desire?
Click to expand...
Click to collapse
Unfortunately, that's not likely to happen. Then again we'll never know until we try. Still doubt it though.

um, probably a stupid question but at http://developer.htc.com/ it shows the us cellular desire having the source code, though it says eclair im guessing that is not what we need?

Correct. We want a Froyo or Gingerbread Kernel.

Even though a phone has the same cpu doesn't mean a thing. The kernel controls more than a cpu. Like anything setup on the board. The cdma and gsm has a difference in the board. Which our phones really are not all that common to the gsm.
Though the difference between a gsm and cdma kernel source isn't all that different. Just stuff missing in the gsm source. I believe the gsm source could be used if we port the cdma stuff up to froyo (Not even sure that would be needed) the port the cdma stuff over to the gsm stuff.
Now I was going to try to do that if it was possible. But I don't understand it really all that much. I can tweak the kernel source, build source and tweak, port roms and look at the main differences in stuff. When you ask for some help you either get confronted by a why or the dev you pm ignores you. I believe I have pm'd nearly every gsm dev to the point of having a ? with doing a kernel or porting something. The only one I ever got a reply from was benne. Now the ones with other devices seem to be willing to help though.
Which takes me to have sense hd. I have it all ported, setup what I believe to be correct. Where it starts to boot and freezes at a couple .jar files saying they can't be found when they are in the sense hd rom any way. Have yet to figure that one out.
Though thinking logical why waist time porting the sense froyo kernel when we should have the source? Every other phone has the source code after every update. I was told I would get it no later than a 120 days I think it was. Then they weren't in a gpl bind as android was w/e it is. I think it has been 6 months no with out the source. Where they are in violation of gpl as the android kernel is a linux kernel under gpl.
With that said if you search on here other devices got the same reply's to e-mails some of us have got. Which they got in no later than a month by doing constant e-mail's from people. They posted a generic type e-mail to send demanding the kernel source. Which is all it would take. This is honestly what I recommend to do since you will have issues starting out porting it. When you could start with something that works like it should.
Edit: Also the desire never got a official gingerbread sense. They got a leak which as I am aware all the gingerbread roms still use the stock kernel that was leaked with it. If it is using a different one I am guessing it was ported. Which leads to the other thing. Porting a gsm rom to cdma most will work but you will get force closes on some things. This is likely due to stuff in the frameworks for the cdma that is missing. I haven't looked into it much in all honesty. As sense is a different animal then aosp.
With that said though uscc said one update per device. Where my leak inside uscc said no gingerbread a month ago. Where uscc I figure would be the first to get it. So if we done get it. It would depend on the other carriers. If they don't I doubt we see it.

Jereso said:
Correct. We want a Froyo or Gingerbread Kernel.
Click to expand...
Click to collapse
Ok this is the first warning before contacting a admin. You never contacted me to use my clockworkmod files. Let alone ask to host them yourself. Heck you never even gave credit for the files. You also never contacted lohp75 to use the pb99img.zip on top of it.
Being it is known that myself or weasel compiles the cwm files. I had a feeling you jacked them off my forum with out permission. My forum is open pubicly for people to stop in and download w/e. This doesn't me take the gift of getting something for free. Upload it to a different host and claim it as your own.
A little hint what do you think the 2fs after the clockworkmod is for? Sure isn't for looks.
So since you never contacted me to re host them or use in your guide. You will not have my permission to have them in your guide. You also jacked all the info in this guide from other guides and posts with out giving credit. Thanks for trying to take credit for nothing you did

Official gingerbread update?
HTC released the official gingerbread update for the Desire recently.
Is that only for GSM? Is there a way to get it on our cdma phone. I currently have CM7, but I miss sense.
Maybe someone made a rom that's basically the official Desire gingerbread, but works on the CDMA Desire?
Thanks

2fast4u88 said:
Ok this is the first warning before contacting a admin. You never contacted me to use my clockworkmod files. Let alone ask to host them yourself. Heck you never even gave credit for the files. You also never contacted lohp75 to use the pb99img.zip on top of it.
Being it is known that myself or weasel compiles the cwm files. I had a feeling you jacked them off my forum with out permission. My forum is open pubicly for people to stop in and download w/e. This doesn't me take the gift of getting something for free. Upload it to a different host and claim it as your own.
A little hint what do you think the 2fs after the clockworkmod is for? Sure isn't for looks.
So since you never contacted me to re host them or use in your guide. You will not have my permission to have them in your guide. You also jacked all the info in this guide from other guides and posts with out giving credit. Thanks for trying to take credit for nothing you did
Click to expand...
Click to collapse
Koush is the maintainer of CWM, and personally I would appreciate it if you didn't put "2fs" after the version because it looks silly and nobody really gives a hoot who compiled it.

Zhenya13 said:
HTC released the official gingerbread update for the Desire recently.
Is that only for GSM? Is there a way to get it on our cdma phone. I currently have CM7, but I miss sense.
Maybe someone made a rom that's basically the official Desire gingerbread, but works on the CDMA Desire?
Thanks
Click to expand...
Click to collapse
No there's no official CDMA Gingerbread kernel. There is a Sense 2.0 ROM testing right now from 2fast4u88.

[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] [INTRO] Getting started with Android and rooting

Introduction to Rooting:
This is meant as a very basic discussion for people relatively new to rooting and Android or people that go through the steps but don't have a good idea of WHY. As a result, it will omit many details and simplify others. Also, it's not meant to be a rooting guide (as there are excellent ones out there already) so much as an explanation of concepts most of us take for granted, but noobies don't. All of this info is out there, but when you're new you may not know how to find it or even that you should be looking for it.
DISCLAIMER: I, nor anyone else, am not responsible for what you do with your phone. Rooting and otherwise altering your phone has the potential to brick your device, void your warranty, and many other bad things. Perform these actions at your own risk.
Post 1: before you root
What is rooting?
Phone Partitions
Intro to ROMS and kernels
Post 2: rooting and flashing
Steps of rooting
How to flash ROMs
What is root/rooting?
In Unix-style operating systems, "root" is the name of the user who has all permissions and is therefore able to run/modify/change/delete just about anything. If you're familiar with Windows, this account is called Administrator. The default account (that's you!) on an Android phone does NOT have these privileges. Rooting is the process of obtaining them (i.e. obtaining root access). Once you root, you can "flash" new software onto your phone without (much) restriction. This is great because you now have control over what programs are on your phone, how your phone handles resources, what kernels you run, and more!
Once your phone is rooted, you don't always wield all of that power. You control your access to all these new abilities with a program called SuperUser (available on the market and baked into ROMS). This program can grant these special rights to any other program that requests them. So let's say a program wants to write data to a place it's not normally allowed. It will ask SuperUser to up its privileges and then BAM! it can write where it wants to. You yourself can gain SuperUser privileges in a shell by typing su. Then YOU can read, write, and execute to your hearts desire.
Before you root:
Before rooting, there are some basic things you should know.
Phone partitions: Your phone has a number of partitions. The important ones to know at first are:
1. System - this partition is essentially what you think of when you think of the operating system, the Android UI, and preinstalled apps. When people talk about flashing ROMs (e.g. CyanogenMod, Synergy, etc), they are talking about flashing a new system partition...with some exceptions to be discusse later.
2. Boot - this is the kernel and ramdisk. The kernel is responsible for managing the interactions between the phones software (including the ROM) and the hardware. Altering the kernel can increase/decrease performance, battery life, and more because it manages applications and system resources. When you flash a new kernel, it flashes to the boot partition. You may not notice a big difference like you do when changing ROMS, but behind the scenes, your phone's performance can be drastically altered. A *LOOSE* analogy is that the ROM is like the body and interior of your car (including color, AC, stereo, heated seats, TV in headrests, etc.) and the kernel is like the engine. You may not see it, but you'll know it's there if it's awesome or it sucks.
3. Aboot - this was largely unimportant for newbies until the bootloader lock/unlock situation. The short story is that aboot contains functions which authenticate the boot partition (that's the kernel, remember?). It checks to see if your boot partition is Verizon legal and if not, it aborts the boot process and politely tells you to contact Verizon. This authentication is what is referred to as a "locked" bootloader. It prevents you from completely booting the phone with a custom kernel. The bootloader is "unlocked" by replacing the stock aboot partition with one that does NOT check up on the boot partition. This is important because it allows us to run whatever kernel we want without bothering with kexec.
4. Data - this contains user installed apps, settings, contacts, bookmarks, etc, etc, etc. You can wipe this partition (as opposed to the above partitions) and still boot into the operating system. However, you will have lost all your setting and user installed apps. This is also called a factory/data reset.
5. Cache - this is stuff that you frequently use so it's kept available by Android. You can wipe it without much consequence and SHOULD wipe it when flashing new ROMs.
6. Recovery - this partition contains a separate operating system that allows you to recover from a corrupted/absent/otherwise jacked up Android operating system. It has a number of other functions as well. The big ones are to backup your device and restore said backups, to wipe certain partitions, and to flash things to your phone (i.e. install new ROMs, recoveries, or other programs). The stock recovery is limited so you will definitely want a custom recovery, created by the fine devs in the community, on your device.
What is a ROM and what is a kernel?
I touched on this above. A ROM is what goes on the system partition. It contains what you think of as the Android OS including the UI and preinstalled apps. It controls how programs interact with you, the user. A kernel controls how those programs interact with the phones hardware. You need both a ROM and a kernel to have a functional phone. Not only that, but not all ROMs and kernels are compatible. A ROM based on Touchwiz (TW) needs a TW kernel and an AOSP (Android Open Source Project) ROM needs an AOSP kernel.
Kernels come as standard kernels, as described above, and kexec kernels. As the bootloader is unlocked, there's really no need for kexec on OUR device. However, it does bear mentioning...sooooo, kexec is a method of getting a custom kernel running without having it reside on the boot partition. Once the kernel is loaded, the phone doesn't care where it came from. Your phone has already checked the boot partition, OK'ed it, and loaded the kernel. The custom kernel that you actually WANT running is waiting patiently on your SD Card. The phone boots into a kexec enabled recovery, which loads the custom kernel while the over the current one (the boring stock kernel) while it is still running. The old bait and switch.
What is a recovery and which one should I use?
A recovery, as mentioned above, is a separate operating system that loads from the recovery partition and allows you to make changes to your phone should it need to be "recovered". It goes beyond this though, allowing you to backup and restore your phone, flash ROMs, flash a different recovery, install programs, mods, etc. On the d2vzw, you can enter recovery by powering down your phone and holding down volume up, home, and power. There are also ways to reboot into recovery easily through programs and mods commonly found in custom ROMs.
Backups of your phone are called nandroids and they contain the contents of the system, data, cache, recovery, and boot partitions. This means when you create a nandroid, you are backing up all that stuff.
I'm not going to tell you which one to use because for the most part it's a matter of preference. There are anecdotal stories about one recovery or another causing issues, but I've personally never had those issues and each recovery has its die hard supporters. I WILL say that if you want to use a ROM with a kexec kernel, you need a kexec enabled recovery. Lastly, if you decide to use kexec, your phone will look like it's bootlooping. That's normal.

I'm ready to start rooting/flashing!
There is an excellent guide stickied in the development thread here http://forum.xda-developers.com/forumdisplay.php?f=1672 (big thanks to droidstyle). However, many of us forget what it's like to be a COMPLETE newbie and to someone who has no idea about anything, even that guide can be a little intimidating. You can follow the instructions, but may not understand what you're doing. The steps to take to start out with are:
1. Make sure you understand what I've written above. Make sure you are comfortable with the possibility of bricking your phone.
2. Root your device. As I said above, this is simply gaining root/Admin/whatever you want to call it access on your phone. In and of itself, it does NOT alter the ROM or kernel. However, there are many different ways to obtain root and some of them DO alter these things. The easiest and safest way to root (IMO) is to use Noxious Ninjas excellent tool. http://forum.xda-developers.com/showthread.php?t=1792342. If you like it, I encourage you to donate or at least "Thanks" him. It works by taking advantage of debugfs permissions to get the su binary (remember this from above??) onto your phone with permissions set so you can run it. It therefore doesn't change ROMs or anything else. You won't lose data, apps, or anything else. It just sneaks su right onto your current setup.
3. Install a custom recovery. This will allow you to do all the fun stuff I talked about above. I recommend installing EZ-recovery from the market and flashing CWM 6.0.1.0.
-- Install EZ-recovery
-- Under the "Recovery" heading, click the Recovery radio button and select CWM 6.0.1.0
-- Click flash
4. Backup everything as if your life depended on it. This means backing up your NV/IMEI as shown here http://rootzwiki.com/topic/32397-tutorial-imei-backup-nv-with-qpst-us-variants/ and making a nandroid (see above). You can restore a nandroid backup and you'll be right back where you were before flashing or changing things around. You should also back up texts, anything on your internal sd card, and programs SEPARATELY from a nandroid (see below) so that you can easily replace them after flashing a new ROM. The steps to making a nandroid are (similar steps to restore):
-- Turn off your phone.
-- Hold down volume up, home, and power until recovery appears.
-- Use the volume rocker to go to "backup and restore" and hit the power button
--- Select backup and then select the external or internal SD card
5. Unlock the bootloader. See the aboot partition discussion above for what this means. You must do this seperately from flashing ROMs and kernels. Refer to this thread http://forum.xda-developers.com/showthread.php?t=1839791 and give appropriate thanks! A warning...if you mess up your aboot partition, there's really nothing (that I know of) you can do to revive your phone besides sending it to someone with JTAG.
A quick note about backing up apps. Personally, I use Titanium backup because I've used it forever...and I think it's a great app. I'm not going to go into details, because it's not too tough to do a few basic things with it and because I want to stick to things that will help prevent bricks.
You're now ready to start flashing ROMs!
As a precursor, there are ROMS that are based on TouchWiz modified Android from Verizon/Samsung and there are ROMS based on AOSP (e.g. CyanogenMod). TW roms need a TW kernel and AOSP roms need an AOSP kernel. Until you get comfortable with everything, I would stick with TW, but that's just my opinion. Don't worry, you'll get comfortable pretty quickly.
Also, some roms come with kernels and will flash the kernel to your boot partition in addition to flashing the ROM to your system partition. Some ROMs don't come with kernels. If the ROM you choose comes with a kernel, that's great. If not, you'll still have the kernel you are currently running and you need to make sure there are no incompatibilities with your new ROM. ALWAYS ALWAYS ALWAYS read the OP of a rom you want to flash to find out kernel information as well as how to install the rom and anything else you may need to know. The general steps to flashing a ROM are (remember to read the OP for specifics):
1. Backup apps, data, call log, contacts, messages, etc. My program of choice for much of this is Titanium Backup available on the market. If you choose to use it, buy it as you'll use it a billion times.
2. Download the ROM you want and check the MD5
3. Place the ROM on the root of your SD card. Do NOT unzip it.
4. Reboot into recovery and make a nandroid backup
5. Wipe data/factory reset and wipe cache. Wipe it more than once if paranoid. People sometimes talk about wiping Dalvik cache. It's an option in your recovery, but it's not necessary IF you did a factory/data reset because the Dalvik cache is on the data partition which is wiped in the reset. You may want to wipe the Dalvik cache for some other purpose however.
6. Go to "install zip from sdcard" and select the ROM you want
7. If you want/need to flash a kernel, install that zip from the sdcard too.
8. Reboot and restore all that you backed up
If you want to flash a kernel without flashing a ROM, all you need to do is reboot into recovery, make a nandroid, wipe cache and Dalvik cache, and install the zip from your sd card.
Remember:
-- ALWAYS read the OP before installing anything
-- backup before making changes
-- verify MD5 checksums
-- wipe data and cache when flashing a new ROM (unless told not to by the ROM dev...sometimes referred to as a dirty flash)
-- NEVER accept an OTA (having a custom recovery should block OTAs anyway)
That's it for now. If people like this or have requests about other good noob topics, I'll consider adding to it. If not, then screw you!

Reserved

I didn't realize it was that easy to flash a custom kernel. Cool. The guide is very helpful.

Nice writeup, a lot if good information. I think I've successfully graduated from noob but still like to read more. One minor problem I noticed. All your rooting, and unlocking links are for ICS I don't think anyone is still on it. You may want to link to open your eyes guide for JB.... which will probably require a whole post to explain what is going on.
Sent from my VS920 4G using xda app-developers app

Great post OP.

GUIDE SGS4 GSM vs CDMA, Unlocking, Rooting,Info on XDA, Flashing,4 noobs & beginners

GUIDE SGS4 GSM vs CDMA, Unlocking, Rooting,Info on XDA, Flashing,4 noobs & beginners
First off: if you find this useful, please hit the THANKS button, instead of posting thank you in the comments
Over the course of the past three months (and more specifically, over the past week), I'd like to think I've gone from complete noob to proficient android ROM flasher/ phone dude. However, it took many, many hours of searching for info scattered across this site and others, so I figured I'd give compiling all I've learned a shot, into one comprehensive thread that really covers all the stuff you need to learn from the ground up.
Will do so in the next couple 10 posts, topics being:
*Step (-1): What type of network/ phone technology does your phone use?
*Step (0): is your phone networked locked?
*Step (0.5): DECIDING YOU WANT TO ROOT YOUR DEVICE!/ Put a custom operating system on that thaaaang
*Step1: figure out what your device is- specific phone and model
*Step2: figure out how to root (gain root access to) your device looking at XDA forums
*Step3: Follow instructions, root device
*Step4: backup all your apps and app data
*Step5: Install a custom recovery either ClockWorkRecovery (CWR) or Team Win Recovery Project (TWRP), and do a nandroid backup!
*Step6: Choose which ROM or multiple ROMS you want to try out, and download the zipfile to your phone's internal memory or
*Step7: Step 7: flash the ROM and restore your apps!
NOTE: YOU TWEEK YOUR PHONE/ FOLLOW MY ADVICE AT YOUR OWN RISK
I just learned this stuff myself, so I thought now would be a good time to explain it, while I can still remember what if feels like to have no idea what I'm doing haha.
Before I go further, there are similar intro threads to this...for example, this one does a decent job of explaining that by modding your phone, you may void the warranty (although there are ways to restore your device to a state such that you can't tell you ever modded, it, like triangle away, etc.) http://forum.xda-developers.com/showthread.php?t=1118120
I posted this here because a couple of these steps use the Galaxy S4 i9500 as an example...so if you have that phone this thread should be particularly helpful.

Step(-1): What type of network/ phone technology does your phone use?
If you are OUTSIDE the USA, 99% chance the answer to this question is GSM, meaning your phone number is attached to a little plastic sim card that you can put into/ out of your phone...you should check anyways though to be sure.
If you are in the US, you may have a phone which uses CDMA, a technology that does not use Sim cards (true if your carrier is Verizon or Sprint). Phones that JUST use CDMA are sort of "Hardwired" to their networks, making it much more of a hassle to switch carriers; plus, basically everywhere else in the world uses GSM, so if you plan on traveling outside the USA, you probably won't be able to use your phone abroad. If you have a fancy new smart phone, it may have the hardware to use both CDMA and GSM networks, (for example, all Iphones models 4s and above), so check your phone specs.
In the US, the major carriers that use GSM are ATT and Tmobile. I prefer getting phones from these guys, because I know I'll be able to relatively easily use my phone anywhere in the world, and easily switch between cheap, prepaid, contract free plans (like straight talk or ultramobile), which rent out the networks of major carriers like ATT and Tmobile.

Step(0): is your phone networked locked?
ans: This is mostly a non-issue to folks outside the US, or if you don't plan on switching your carrier, but if you plan on travelling abroad or switching your carrier, and have a CDMA phone, you have a tough road ahead that I cannot advise you on . I would suggest checking out this site and buying a slightly used android gsm phone (att or tmobile branded) http://swappa.com/ .
However, if you have a GSM phone you got in the US, your phone may be configured so that putting sim cards from different carriers in it won't give you any service (aka "locked" or "network locked"). Check by taking a friend's Sim card using a different network than you and popping it into your phone; if you have service/ can make and receive calls, the phone is NOT locked. There are probably more sophisticated ways of checking if your phone is network locked, but above is probably the most straightforward.
There are some methods of unlocking your phone for free, but if you have a newer phone it may not work. Plenty of online sites that sell you unlock codes for between $7-$25, and send the code over email either instantly or a day at most after you buy it. Definitely worth it in my opinion; one site I've used a bunch is http://www.cellunlocker.net/
NOTE: if you have your phone on a contract, you are still obligated to pay your carrier throughout the time of your contract, else you pay some cancellation fee. So be aware of that.

Step 0.5 DECIDING YOU WANT TO ROOT YOUR DEVICE!/ Put a custom operating system (ROM)
SO, now let's say you've network unlocked your awesome GSM android smartphone, and you want to travel with it to another country, like for example, India. Because you unlocked it, you can buy a cheap local Sim card and use it in your phone, fully enjoying mobile 4g data (well, more like 3.5G, using HSPA+, not so much 4G LTE in India yet, but I digress). OR, you can use a $45 a month prepaid plan where you get unlimted everything and have no contract, instead of paying $80 a month or some garbage. AWESOME!
However, let's say you got a Tmobile phone and want to use the phone's capability of being a portable wifi hotspot, broadcasting the mobile data it's getting to your computer...turns out you can't do that in India (or on cheap prepaid plans in US, for that matter). I discovered that since I was using a Tmobile branded phone, the Tmobile "stock" operating system of the phone won't let you use the wifi hotspot unless you have Tmobile's special "hotspot plan"...it also hard codes a bunch of shi**y bloatware apps on your phone that suck. Some BULLS**T, eh?
Luckily, there are plenty of free and easy ways to "root" (gain root acccess) to your phone (and plenty of resources telling you how to do so!), and install custom android operating systems on your phone, which
1.) don't have any stupid bloatware apps
2.) let you use all the hardware features of your phone regardless of carrier
The result is a more powerful phone that runs faster, uses less battery life, and is generally just way more badass. Probably the best resource for how to do all of this is the xda-developers forums (http://forum.xda-developers.com/ ) Very vibrant community, and lots of people will help...just follow the rules though, explained tongue and cheeck in the following video ( http://www.youtube.com/watch?v=JmvCpR45LKA ). The main site for xda-developers is www.xda-developers.com, they also do cool vides and stuff on what's up with phone stuff. HOWEVER, if you are not careful you can mess up your phone, so that it's about as good as a paperweight (called "bricking" your phone). So just read all the instructions before you do stuff, yeah?
The following is more or less the beginning steps I did to root and install a custom ROM on a friend's Galaxy S4, which is an international model and so not network locked. The same general process could be applied to your phone as well, but again--this is only a general guide--your phone can (and probably will) have it's own exceptions to the general process. LOOK THEM UP!

Steps 1,2,3: find device model, research how to gain root, ROOT!
Step1: figure out what your device is- specific phone and model
ans: for example, my friend's phone I am setting up for him is the Samsung Galaxy S4 model i9500
**************************************************
Step2: figure out how to root (gain root access to) your device
ans: Off all the devices on xda forums (http://forum.xda-developers.com/index.php?tab=top), found my device ( http://forum.xda-developers.com/galaxy-s4) , found the proper forum (http://forum.xda-developers.com/galaxy-s4/help) , then searched in that specific forum to find the proper thread http://forum.xda-developers.com/showthread.php?t=2419762 , see Q4
**************************************************
Step3: Follow instructions, root device
ans: Instructions are at http://forum.xda-developers.com/showthread.php?t=2292615
NOTE: You must have the proper USB drivers installed, meaning either installing the sdk (software developer kit) from google and getting adb (android debugging bridge) set up (this is the best way to do it, really, especially if you want to mess around with phones more...tutorial on how to setup adb here http://androidcentral.us/2013/08/how-to-install-android-adb-and-fastboot-on-windows/ ) . If you can already transfer music and stuff from your computer, it may work without adb. Be sure your USB cable is not too beat up, and if possible, is the one that came with the device.
adb is very useful for communicating between pretty much any android phone and your computer. You can use it to push files on the computer through the terminal interface, even if the phone's file system doesn't show up for whatever reason on the computer when you connect it via USB ( more on that here http://log.amitshah.net/2012/05/using-adb-to-copy-files-to-from-your-android-device/ ), and a cool little program to send files from your computer to the device in a slightly more straightforward way, if you already have adb installed (http://www.xda-developers.com/android/push-files-to-your-device-with-quick-adb-pusher/)
Also, make sure you have USB debugging enabled. It should be in the Develpors options, which you may have to "activate" to see...see here http://gs4.wonderhowto.com/how-to/enable-hidden-developer-options-your-samsung-galaxy-s4-0146687/
If you are rooting a samsung device, you will probably have to use a program called ODIN. Other android devices allow you to do root through a method called flashboot. In general there are tons of ways to root devices, just make sure the one you are using has been tested and you follow the instructions exactly.
CONGRATS! you are rooted. That's half the battle. Rooting the phone will add a "Super User" app of some kind, which will basically controll which apps have access to the internal files of the phone (located on the "root" of the phone's flash drive). Some apps that are very useful for flashing custom ROMS (like ROM manager) and backing up your apps and their associated data (like Titanium backup) require root access, so you'll need to have rooted your phone first, and then when you open those apps for the first time, tap "allow" when it asks about granting root access.
some cool apps can only be downloaded if your phone has Root, like this gameboy emulator: https://play.google.com/store/apps/details?id=eu.codlab.src.game&hl=en
and here are some good Root apps to have, apparently
http://www.youtube.com/watch?v=jX4ir9r84YA

Step4: backup all your apps and app data
When you do eventually install a custom ROM on onto your phone, it will start out with little to no apps. The best way to get up and running again as quick as possible is to back up all your apps and data with Titanium Backup (mentioned above), which requires root access. Here's a great video on How to use the free version: http://www.youtube.com/watch?v=gQWoWfTA88k ....the video makes a good point in that if you are backing up your apps for a new ROM you are about to flash, you should only backup the User apps. Backing up and restoring the system data as well might cause some problems in the new ROM
While you don't need to to buy the pro version, I would recommend it--7 bucks, but it allows you to restore all the apps you've backed up much faster by letting you back them up into a zip file that you'll later be able to flash on your phone. Very useful, more on that in a bit...video talking about that here: http://www.youtube.com/watch?v=dRR5FONGJUA

Step5: Install a custom recovery either ClockWorkRecovery (CWR) or Team Win Recovery
By "custom recovery", i mean a custom version of the boot/ recovery interface, which lets you do a lot more with your device besides just restore it to factory settings. These custom recoveries will let you do a full backup of your device (often called a "nandroid backup"--this should be the first thing you do after you root your device!), as well as flash custom phone operating systems (ROMS) onto your phone; useful if you want to fully use all the hardware features of your phone, and not have the bloatware apps from the manufacurers hard-coded into your phone.
It's worth noting here that it's VERY important to install the correct version of CWR or TWRP. Usually to download CWR for your device, you can just download an app called ROM manager (again, after you've rooted your phone), which will recognize your device and then install the proper CWR version on it.
NOTE: If you have a more esoteric model of phone (like I do--the Samsung Galaxy S3 T999L, an LTE version of the S3 that came out in 2013, a while after the initial S3 launch), you may have to flash a custom recovery of a similar and more popular phone model to flash some custom ROMS (in my case, I had to flash the the Galaxy S3 model T999 version of CWR). For weird esoteric cases like this, it may be worth it to buy a useful app, ROMToolbox pro, which will let you flash a custom recovery for a userdefined device onto your phone in the paid version (it's like $5). Most times you shouldn't have to worry about this stuff, but just make sure you read any instrutions on XDA forums carefully before doing stuff.
As mentioned before, before messing around with your phone anymore, do a nandroid backup--super easy and essential if you make a mistake installing the wrong ROM or Recovery. Doing a nandroid backup will create a .zip file that contains a full "image" of your phone--all your data, apps, settings, a snapshot of your phone exactly the way it was when you took it. In creating this backup you can save it to your phone's micro SD card, or the phones internal memory. Regardless, always a good idea to save a copy on your computer too when you are done.
For the Samsung galaxy S4 i9500, looks like TWRP is the recovery to flash: http://forum.xda-developers.com/showthread.php?t=2361122

Step6: Choose which ROM or multiple ROMS you want to try out, and dl zipfile to phone
Now comes the fun part. Do some research on what custom ROM you'll want to try out. Some basic principles about ROMS:
Roms based on the Stock OS: These ROMS are based on the manufacturer firmware/ OS that the phone shipped with. So for Samsung devices, for example, these types of ROMS are Touchwiz based (because "TouchWiz" is the name Samsung has given to it's proprietary software that is responsible for a lot of the bell and whistle tricks you see in Galaxy S4 commercials, for example) These Roms are usually about 700 MB in size, and may still have some of the samsung apps installed if you do like to use them.
AOSP or AOKP ROMS:
AOSP (Android Open Source Project) ROMS are those that ship with "vanilla" android, meaning they don't have any manufacturer bloatware--they come with more or less the bare bones apps required to run the system. These ROMS will be much smaller, around 100-150 MB in size. The most popular of these is CyanogenMod, which is often referred to as just CM (for example, CM11.0.1 stands for CyanogenMod version 11.0.1). The guy who made clockworkrecovery, Koush (a legendary android developer of sorts, it seems), now works for the CyanogenMod development team ( think)
AOKP is the name of another popular AOSP based ROM. AOKP stands for Android Open Kang Project, Kanging being some jargon for stealing code and messing with it or something. Apparently it was used as a joke and then stuck, in the same sense that their mascot being a unicorn stuck (which I think is awesome haha).
IMPORTANT POINT ABOUT AOSP ROMS:
If you flash an AOSP Rom, the google play store will NOT be installed by default. In order to fix that, you'll need to flash another zip file containing the play store app as well as other basic google apps (gapps for short) as soon as you flash the Rom itself. You can find the proper gapps zips that go with the proper AOSP roms here: http://goo.im/gapps
There are couple apps that will let you download the ROM files directly to your interal storage from the app itself, like Rom Manager. However, to make sure you have the most up to date version of the ROM, you should visit the ROM's website directly.
Custom ROMS will often have a most recent stable build, and a most recent "nightly" build. The nightly builds may have some new experimental features, but may be a little buggy.

Step 7: flash the ROM and restore your apps!
So here's a pretty good short video walking through how to flash a ROM, although uses a different recovery interface besides CWR or TWRP : http://www.youtube.com/watch?v=nxTwGwtUBbk ....this does a good job of explaining the basic idea, however--
A.)you get the zip file of the ROM you want to flash on your internal or removable SD card
B.) reboot into recovery mode (often by holding down the volume down key and power button at the same time when your power is off, but you should look up what it is for your specific device)
C.) do a Wipe or Factory Reset. THis should not wipe the data on your SD card or phone's Internal SD card
D.) Wipe the Cache or the Dalvik Cache, whatever it is called (though on TWRP, the wipe feature does both a factory reset and cache wipe at once)
E.) install from SD card the zip file containing the ROM you are going to flash
F.) If the Rom is an AOSP based ROM, install the zip file containing the proper package of google apps
G.) reboot system
Again, the above are just general steps. If you want to see someone flashing a ROM with the recovery you are using (and I would recommend CWR or TWRP), just search for it on Youtube.
Now, if you plan on restoring your apps by flashing a Titanium Backup zip file, you first want to reboot into the new ROM, and skip the part when it asks you if you want to restore your phone using your google account (you can do that later). Then reboot into recovery and flash the Titanium backup zip file. got this info here: http://www.s3forums.com/forum/galax...backup-pros-update-zip-restore-your-apps.html
And that's about it! let me know if I got anything wrong. If you do have questions, I'll try my best to answer them, but again, I've just learned all this stuff as well, so I may not know.

[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

Database Info

welcome