Database Develop

Now it can be S-OFF, how to install a permanent ROOT?

Just finished the S-OFF using alpharevx, want to know how to do the permanent ROOT.
Any tips?

http://forum.xda-developers.com/showthread.php?p=14693680
check this out, pretty detailed

There is a Sticky at top of the IncS General Forum about this.

You need to install gingerbreak on your phone it's here http://forum.xda-developers.com/showthread.php?t=1044765 and Open Gingerbreak and click Root Device. that's all.

nikkuy said:
You need to install gingerbreak on your phone it's here http://forum.xda-developers.com/showthread.php?t=1044765 and Open Gingerbreak and click Root Device. that's all.
Click to expand...
Click to collapse
Not quite...
I have rooted 4 IncS wit GingerBreak now, and non of them succede first time.
2 got rooted thrid time i ran GB, and 2 of them i had to take the SD card out when the error message came.
But GinderBreak can root the IncS, but somthimes you need some "Ninja" tricks.

Are you done?

geeti said:
http://forum.xda-developers.com/showthread.php?p=14693680
check this out, pretty detailed
Click to expand...
Click to collapse
This just worked for me - it was simple in the end!
I used a spare SD card (I don't think I needed to), just copy/pasted the clockwork recovery .zip file to the card (not in a folder on the card) and rebooted, holding volume down on start-up. After that, it automatically prompted me to install the file, so I let it install.
Then, I rebooted the phone and deleted the above file from the SD card, and replaced it with the signed root .zip file and rebooted with the volume down button again.
Just follow the steps, one by one, 'To root:' in the above linked post, after you have installed the recovery file - it worked first time for me and was actually simple to follow!!
My phone works as it always has done (as you would expect/hope), but now I have root - confirmed with Root Explorer app from Market.
Thanks to all involved in the linked post above.
I also tried GingerBreak a few times but it just didn't work for me, so I gave this a go and it worked first time.

jkolner said:
Not quite...
I have rooted 4 IncS wit GingerBreak now, and non of them succede first time.
2 got rooted thrid time i ran GB, and 2 of them i had to take the SD card out when the error message came.
But GinderBreak can root the IncS, but somthimes you need some "Ninja" tricks.
Click to expand...
Click to collapse
My phone is still on 2.2 Froyo, Gingerbreak is for 2.3 correct?

geeti said:
http://forum.xda-developers.com/showthread.php?p=14693680
check this out, pretty detailed
Click to expand...
Click to collapse
I dont quite understand step 4, 5, 6:
4. Extract recovery.img from the archive and put it with fastboot.
5. Put the phone is Fastboot USB mode (HINT: Android is not up and running - access it from your hboot screen - see how below)
6. fastboot flash recovery <recovery.img> <<< from a command line (use root for Linux- sudo ./fastboot yadda)
Step 4, it says put it with fastboot, does it mean after i extracted the recovery.img, move it to the same folder with the fastboot app (i.e. to the folder android-win-tools where the fastboot app is located?).
Step 5, Fastboot USB mode, this is done by holding the volume down button and the pressing the power button, when the white screen comes up, select Fastboot, and then plug the phone back to the computer via USB?
Step 6, after the phone is plugged to the computer via USB, double click on the fastboot app (the one inside the android-win-tools folder) and when the black prompt screen comes up, type in Linux- sudo ./fastboot yadda?
Btw, I am on Windows computer, not Linux, so is the command prompt Linux- sudo ./fastboot yadda correct?
Also, if I want to bluetooth the su-2.3.6.1-ef-signed.zip to the phone, will it go directly to the SD root location? If not, when I do clockworkmod recovery and "install zip from sdcard", will it able to locate the file?

netwr said:
I dont quite understand step 4, 5, 6:
4. Extract recovery.img from the archive and put it with fastboot.
5. Put the phone is Fastboot USB mode (HINT: Android is not up and running - access it from your hboot screen - see how below)
6. fastboot flash recovery <recovery.img> <<< from a command line (use root for Linux- sudo ./fastboot yadda)
Step 4, it says put it with fastboot, does it mean after i extracted the recovery.img, move it to the same folder with the fastboot app (i.e. to the folder android-win-tools where the fastboot app is located?).
Step 5, Fastboot USB mode, this is done by holding the volume down button and the pressing the power button, when the white screen comes up, select Fastboot, and then plug the phone back to the computer via USB?
Step 6, after the phone is plugged to the computer via USB, double click on the fastboot app (the one inside the android-win-tools folder) and when the black prompt screen comes up, type in Linux- sudo ./fastboot yadda?
Btw, I am on Windows computer, not Linux, so is the command prompt Linux- sudo ./fastboot yadda correct?
Also, if I want to bluetooth the su-2.3.6.1-ef-signed.zip to the phone, will it go directly to the SD root location? If not, when I do clockworkmod recovery and "install zip from sdcard", will it able to locate the file?
Click to expand...
Click to collapse
No, follow step 6 you use command line like this: "fastboot flash recovery C:\recovery.img". After you choose "install zip from sdcard" you have to choose the location where you put the file you want to install.

coy1987 said:
No, follow step 6 you use command line like this: "fastboot flash recovery C:\recovery.img". After you choose "install zip from sdcard" you have to choose the location where you put the file you want to install.
Click to expand...
Click to collapse
So this is exactly how it should be typed in the command prompt?
fastboot flash recovery C:\recovery.img
Are the rest of other steps correct?

I am still getting stuck at the Clockworkmod installation part, without this I cannot get to the root step.
I extracted the android-win-tools.zip, which contains the following files:
adb
AdbWinApi.dll
AdbWinUsbApi.dll
android-info
fastboot
and then extracted the cwm-vivow-4.0.0.4-recovery.img.zip, contains the following:
recovery.img
then I moved all the above 6 files directly to the C: directory. After that went into cmd and typed the prompt exactly like following:
fastboot flash recovery C:\recovery.img
Did I miss anything? Because after typing that line and hit return it came out nothing. Is that prompt correct?

Why not root with superoneclick -> download clockworkmod from market and install recovery from app? Work perfectly for me...
Sent from my HTC Incredible S

adaca said:
Why not root with superoneclick -> download clockworkmod from market and install recovery from app? Work perfectly for me...
Sent from my HTC Incredible S
Click to expand...
Click to collapse
clockworkmod from market, is it aka ROM Manager?
This app won't work because it requires a ROOT phone, which is what I am trying to do.

Yes, and before use superoneclick.
Sent from my HTC Incredible S

adaca said:
Yes, and before use superoneclick.
Sent from my HTC Incredible S
Click to expand...
Click to collapse
How did you get it from market, is it not up currently

Superoneclick is not from market, use google. Its for rooting.
Sent from my HTC Incredible S

You can also try Gingerbreak if you can't get SuperOneClick to work (again you'll have to search for this as it's not in the market).

{
"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"
}
Just installed SuperOneClick and clicked Root, it said the phone is rooted successfully. Then clicked on the "allow non market apps" and the result said non-market apps enabled.
But then I went to market and installed a screen cap app (one needs root), launched the app and it said Root required - Your phone does not appear to be rooted or has not been given root privileges.
Did the SuperOneClick really root it?

doctorsax said:
You can also try Gingerbreak if you can't get SuperOneClick to work (again you'll have to search for this as it's not in the market).
Click to expand...
Click to collapse
Does Gingerbreak work with 2.2?

[GUIDE] Nexus 5 - How to Unlock Bootloader, Install Custom Recovery and Root

{
"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"
}
Setup, Preparation and Prerequisites
Basic tasks that I may refer to throughout this guide:
Open command prompt - Press Window Key + R, type in "cmd" (without the quotes), and hit enter.
Enter the bootloader - Turn the phone off. Hold volume down + power. The bootloader is also known as fastboot mode.
ADB and Fastboot Installation
Download the full Android SDK here (scroll to the bottom of the page>DOWNLOAD FOR OTHER PLATFORMS>SDK Tools Only) or get a slimmed version containing only the essential components(Thanks @El Daddy)
Link removed since it expired
Extract the zip and place the android-sdk-windows folder on your desktop.
**If you chose to download the slimmed sdk skip to step 5**
Only if you downloaded the full sdk: Go into the android-sdk-windows folder and run SDK Manager.exe. Install the following packages (there are a total of 4 packages):
- Tools > Android SDK Tools, Android SDK Platform-tools
- Extras > Android Support Library, Google USB Driver
Only if you downloaded the full sdk: Go back into the android-sdk-windows directory, and you should see a new folder named platform-tools. If you don't see this new folder, repeat the step above.
To confirm that it is indeed working, open a command prompt window and enter the following commands:
Code:
cd Desktop/android-sdk-windows/platform-tools
adb version
If it displays "Android Debug Bridge version x.x.xx" it is working. If it is gives an error saying that adb is not a recognized command, it has not been successful. Carefully repeat the steps above if this is the case. Close the command prompt window when you are done.
USB Debugging - On your phone go to Settings > About phone > Tap on Build number 7 times. This will enable Developer options. Now go back to Settings > Developer options > Enable USB debugging
Show File Extensions - Open a command prompt window and run "Control folders" (without the quotes). Go to the View tab and uncheck the "Hide extensions for known file types" option. This will help avoid confusion when renaming files.
Battery - Ensure that your phone has at least 60% battery remaining, and that your PC is plugged in and wont shut down spontaneously during the process. The procedure doesn't take very long (5-15 minutes), but its best to have enough charge in case something goes wrong.
Backup (Optional) - Unlocking the bootloader will completely wipe all data from the device. This includes apps, settings and even the contents of the internal sdcard (pictures, music, etc.). Copy all important files off the phone onto a PC or upload them to a cloud.
Driver Installation - Try this first, but if that doesn't work look here. Still having issues? Give this a try. None of these working? Hopefully this does the trick.
Downloads
Download a custom recovery of your choice and the SuperSU zip below. Place both files (recovery image and root zip) in the platform-tools folder located on your desktop within the android-sdk-windows folder.
Custom Recovery:
TeamWin Recovery Project (TWRP) or ClockworkMod (CWM)
Root:
SuperSU
Information
Rooting a nexus device is actually quite a simple and easy process. Before you begin, it is recommended that you at least try to understand what each part of the process will do. Although this guide will elongate each step in order to show all of the details, the method used can be broken up into 3 main steps: Unlocking the Bootloader, Installing a Custom Recovery and finally Rooting. Each new step relies on the previous step to have been completed, and a basic summary of each part is:
Unlocking Bootloader: Opens the door to the internal memory of the device to be written on to. This allows you to flash images onto the main partitions of the phone.
Installing a Custom Recovery: A custom recovery is flashed onto the recovery partition of the device and overwrites the stock recovery that exists by default. Custom recoveries bring lots of functionality and give you the ability to perform wipes, install flashable zips, create full backups of your NAND (Nandroid backup), and various other features. An unlocked bootloader is needed to install a custom recovery.
Rooting: You can gain root by either flashing via recovery a pre rooted custom rom, or flashing a zip containing the SuperSU binaries. A custom recovery is necessary to do this.
After completing these steps your phone will be rooted, the phone will have a custom recovery installed, and the phones bootloader will be unlocked. This, in my opinion, is the most practical and beneficial method for rooting your phone. It gives you some basic adb/fastboot knowledge, and should hopefully help you have a decent understanding of what is going on. Also this method will work regardless of what android version your phone has. Using a toolkit will only make things worse in the long run...learn to do it properly. It has been proven that every time you use a toolkit, god kills a kitten. Save the kittens.
If you are confused by anything in this guide, I would highly suggest getting it clarified being before moving on. Ask your question in this thread and I or someone else will likely answer. Also I'd suggest that you read over the whole thread a few times before actually doing anything to the phone.
Understand? Good...lets begin:
1. Unlocking Bootloader
Turn the phone off. Then boot it into the bootloader/fastboot mode by holding volume down + power.
Plug the phone into your PC, then open a command prompt window window and type:
Code:
cd Desktop/android-sdk-windows/platform-tools
Code:
fastboot devices
This command will list the connected devices. If your phones serial number shows up you are good to go and may continue. If the phone is NOT listed this indicates that your drivers are not installed correctly. In order for you to continue you must fix your drivers so that your phone is listed under fastboot devices.
If the phone has been recognized by the command above, proceed to unlocking the bootloader with the following command:
Remember that this step will wipe EVERYTHING off the phone
Code:
fastboot oem unlock
On the phone a screen should pop up asking whether or not you would like to unlock the bootloader. Use the volume rockers to highlight "Yes" then press power to confirm the action.
After the above command has finished excuting, run the following (DO NOT skip this step, it is more important than you think):
Code:
fastboot reboot
The phone will reboot. Next you will be presented with a screen containing an android logo and a progress bar (this may take up to ten minutes to complete). Wait until the phone has fully booted up into android, then proceed onto the next section of the guide.
Close the command prompt window.
2. Installing a Custom Recovery
Turn the phone off. Then boot it into the bootloader/fastboot mode by holding volume down + power.
Rename the recovery file that you downloaded above to recovery.img. *Make sure that you rename it to recovery.img NOT recovery.img.img* Remember that you should place the file in the platform-tools folder inside of the android-sdk-windows folder on your desktop.
Open command prompt and run the following commands:
Code:
cd Desktop/android-sdk-windows/platform-tools
Code:
fastboot flash recovery recovery.img
On the phone, use the volume buttons to scroll onto "Restart Bootloader" and hit power to select it. After the bootloader reloads, use the volume buttons to scroll onto "Recovery Mode" and power to select it. You should then be greeted with your newly installed custom recovery.
Close the command prompt window.
3. Rooting
Now that your phone has an unlocked bootloader and a custom recovery installed you have a two options to gain root (Pick one or the other. You don't need to do both)
Option A) Flash SuperSU binaries which will give you root with the stock rom
Confirm that you have downloaded the SuperSU zip from the downloads section above and that it is located in the platform-tools folder inside of the android-sdk-windows folder on your desktop.
Turn the phone off then boot into the bootloader. (volume down + power). Once in the bootloader use the volume rockers to scroll onto Recovery Mode, then press power to select it. This should bring you into your newly installed custom recovery. Leave the phone at the home page of the custom recovery.
Open a command prompt window and run the following commands:
Code:
cd Desktop/android-sdk-windows/platform-tools
Code:
adb push UPDATE-SuperSU-v[COLOR="Red"]X[/COLOR].[COLOR="red"]XX[/COLOR].zip /sdcard/
This will copy the SuperSU zip onto your phone. Once the command has completed continue.
Instructions for TeamWin Recovery Project (TWRP):
Install > browse to SuperSU zip and select the it
Swipe to confirm the installation. Then reboot.
Instructions for ClockworkMod (CWM):
install zip from sdcard > choose zip from sdcard.
Next, browse to the location where you previously copied the SuperSU zip and select the it.
To confirm the installation, scroll down to "Yes" and select it. The installation shouldn't take very long, and once it has completed you may reboot.
Option B) Flash a custom rom which will come pre-rooted
Note that not all custom roms will be pre rooted, however the majority of them are. Read the OP of the ROM thread to see what the verdict is.
Copy a custom rom (you can find these in the Nexus 5 Android Development and Nexus 5 Original Android Development section) onto the phone (remember the location where you copy it to)
Turn the phone off then boot into the bootloader. (volume down + power). Once in the bootloader use the volume rockers to scroll onto Recovery Mode, then press power to select it. This should bring you into your newly installed custom recovery. To install a custom rom the general procedure to follow is: factory reset, wipe cache + dalvik cache, flash ROM, flash GApps. Here are the recovery specific instructions:
Instructions for TeamWin Recovery Project (TWRP):
Wipe > Swipe to Factory Reset
Install > browse to the location where you previously copied the ROM zip and select it > Swipe to confirm the installation
Install GApps using same process as ROM, then reboot.
Instructions for ClockworkMod (CWM):
wipe data/factory reset
wipe cache partition
advanced > wipe dalvik cache
install zip from sdcard > choose zip from sdcard > navigate to the location of the rom > select the rom > confirm the installation by selecting "Yes"
After that you may install the GApps using the same method for flashing the rom, and finally reboot the phone.
Keep in mind that the first boot after installing a custom rom & wiping the phone may take longer than usual, as the phone will need to rebuild the dalvik cache and initialize other first boot stuff.
Congrats! That is all! Your phone now has an unlocked bootloader, a custom recovery installed and is rooted...Plus you saved a kitten. Enjoy

Troubleshooting & FAQ
Why am I seeing a red triangle with a dead android when booting into recovery even after I flashed a custom recovery?
What you are seeing is the stock recovery, meaning that the custom recovery that you flashed did not install correctly. Try the following suggestions:
Make sure you are using the USB cable that came with your phone. Only use other ones, if the stock one isn't working
Try using different USB ports. USB 2.0 ports (the ones that ARE NOT blue) are preferable. USB 3.0 ports (the blue ones) may cause problems with connectivity.
If you are on a desktop, use the ports on the back of the tower instead of the ones in the front. These ports are directly connected to the motherboard, rather than the ones in the front which are usually attached to a header cable which then indirectly connects to the motherboard.
My phone wont boot into android. I can only access the bootloader and custom recovery. What do I do?
Suggestion 1: Factory reset via recovery.
TWRP Instructions:
Boot into recovery
Wipe > Swipe to Factory Reset
Reboot
CWM Instructions:
Boot into recovery
wipe data/factory reset
wipe cache partition
advanced > wipe dalvik cache
Reboot
If that doesn't work continue onto Suggestion 2.
Suggestion 2: Push a ROM to your phone and flash it.
Download a ROM onto your computer. If you don't have time to look for a ROM, just download the stock ROM.
Move the downloaded ROM onto your desktop, and rename the file to "ROM.zip" (without the quotation marks)
Boot phone into recovery
Open command prompt and run the following commands:
Code:
cd Desktop
adb push ROM.zip /sdcard/
Wait for it to finish copying the file, then flash the ROM. If you need further details on how to flash a ROM take a look at the OP, section 3. Rooting, Option B)
If that doesn't work continue onto Suggestion 3.
Suggestion 3: Flash the factory images.
Flash the factory images
My phone wont boot into android. I can only access the bootloader. What do I do?
Flash the factory images
My phone exploded. What do I do?
Tape it back together then flash the factory images

Awesome post. Got a question: if I ONLY unlock bootloader will I still be able to get and install OTA updates?
Sent from my Nexus 4 using Tapatalk

dombera said:
Awesome post. Got a question: if I ONLY unlock bootloader will I still be able to get and install OTA updates?
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
Yes, if you only unlock the bootloader you will still be able to get ota's. The lock state of your bootloader will not affect your ability to receive ota's.

Chromium_ said:
Yes, if you only unlock the bootloader you will still be able to get ota's. The lock state of your bootloader will not affect your ability to receive ota's.
Click to expand...
Click to collapse
Awesome, thx
Sent from my Nexus 4 using Tapatalk

This is awesome, will come in handy.
Sent from my HTC Desire using XDA Premium 4 mobile app

Chromium_ said:
Yes, if you only unlock the bootloader you will still be able to get ota's. The lock state of your bootloader will not affect your ability to receive ota's.
Click to expand...
Click to collapse
What about if you unlock the boot loader and root, will you be able to get OTAs then? I guess a better question is what's the point of no return (without reflashing the factory image) where you break OTA updates? Thanks for the thread btw!

Can people please post confirmation of TWRP or CWM recoveries + rooting working without problems if they've done it? I know it's unofficially supported at this time, but getting some data collected would be useful.
---------- Post added at 01:43 AM ---------- Previous post was at 01:41 AM ----------
Xero258 said:
What about if you unlock the boot loader and root, will you be able to get OTAs then? I guess a better question is what's the point of no return (without reflashing the factory image) where you break OTA updates? Thanks for the thread btw!
Click to expand...
Click to collapse
If you unlock bootloader & root, and modify some system files, OTAs may not be able to pass some pre-install checks, at least this has happened to me on N4 before. I added one line to /etc/build.prop, also one of the older SuperSU versions had to be uninstalled for pre-install OTA checks to pass.

Whyzor said:
Can people please post confirmation of TWRP or CWM recoveries + rooting working without problems if they've done it? I know it's unofficially supported at this time, but getting some data collected would be useful.
Click to expand...
Click to collapse
There isn't *yet* a booting custom recovery for the Nexus 5. Give it a couple of days.

I see some Desire folks
Did u order one chromium?

Is unlocking the bootloader going to be the same as on my GNex, where it wipes the device in the process? If so, this will be the first thing I do when I get it out of the box on Monday.

talz13 said:
Is unlocking the bootloader going to be the same as on my GNex, where it wipes the device in the process? If so, this will be the first thing I do when I get it out of the box on Monday.
Click to expand...
Click to collapse
If you wipe cache exactly after you unlock the bootloader, without booting, no.

Nbsss said:
I see some Desire folks
Did u order one chromium?
Click to expand...
Click to collapse
Not yet. Hoping to eventually get it though.

Whyzor said:
Can people please post confirmation of TWRP or CWM recoveries + rooting working without problems if they've done it? I know it's unofficially supported at this time, but getting some data collected would be useful
Click to expand...
Click to collapse
There are currently no working custom recoveries, so it really only makes sense to unlock the bootloader for now. That way you'll be ready to continue on with the guide right when a stable recovery is released.
Sent using xda-developers app

Nbsss said:
I see some Desire folks
Did u order one chromium?
Click to expand...
Click to collapse
I'm not a really famous desire user but yes I bought it. Did you buy it to? Happy to see some other desire users.
Sent from my HTC Desire using XDA Premium 4 mobile app

Maybe it's a silly question, but can I unlock the bootloader before even booting up the phone for the first time? Can this cause some problems?

boysetsfire said:
Maybe it's a silly question, but can I unlock the bootloader before even booting up the phone for the first time? Can this cause some problems?
Click to expand...
Click to collapse
It should work fine, but whats wrong with booting it up for the first time?

Chromium_ said:
It should work fine, but whats wrong with booting it up for the first time?
Click to expand...
Click to collapse
Nothing wrong, just the laziness of not wanting to do the initial setup two times

Chromium_ said:
There are currently no working custom recoveries, so it really only makes sense to unlock the bootloader for now. That way you'll be ready to continue on with the guide right when a stable recovery is released.
Sent using xda-developers app
Click to expand...
Click to collapse
abaaaabbbb63 said:
There isn't *yet* a booting custom recovery for the Nexus 5. Give it a couple of days.
Click to expand...
Click to collapse
Ok, the wording in OP is:
"Currently neither recovery has official support for the Nexus 5, so the download links below are unofficial and may not be functioning 100% correctly."
and:
"**Warning: Currently there are no officially stable custom recoveries, so i would only recommend unlocking the bootloader for now**"
Which implied that it does work, just not thoroughly tested. Now from the recent replies you're saying it DOES NOT boot at all into recovery?

Whyzor said:
Ok, the wording in OP is:
"Currently neither recovery has official support for the Nexus 5, so the download links below are unofficial and may not be functioning 100% correctly."
and:
"**Warning: Currently there are no officially stable custom recoveries, so i would only recommend unlocking the bootloader for now**"
Which implied that it does work, just not thoroughly tested. Now from the recent replies you're saying it DOES NOT boot at all into recovery?
Click to expand...
Click to collapse
Yes that is correct, they do not boot. I will update the OP now, sorry for the confusion.
Originally I had read the following threads and it seemed that they were somewhat functioning, but it is now confirmed that neither one boots.
TWRP
CWM

[Tutorial][How to] Unlock Bootloader and Install Custom Recovery and Root

Hello,
I know there are some tutorials for this already but I felt like they missed out a few steps that might not be obvious to some who are new to this.
This tutorial applies to all of Android One Device (Micromax Canvas A1, Karbonn Sparkle V Blue, Spice Mi-498 Dream Uno).
Unlocking bootloader will lead to formating of your phone. The stuff inside your sd card is safe but all your apps and their data will be deleted.
Unlocking bootloader:
1. Download Universal ADB Driver installer from here.
2. Connect your phone and run the Universal ADB Driver installer. Click 'Install' button and a warning should pop up. Just click "Install anyway" and it should look like this:
{
"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"
}
3. Download ADT Bundle from here for Win-32 Bit and from here for 64-Bit . If you are unsure which version of windows you have just download the 32-Bit one.
4. Extract the zip file in your C:\ drive like this (You can install it wherever you like but this tutorials assumes this location for simplicity). Add adb and fastboot to system path by following this tutorial . This will allow you to run adb and fastboot commands from any location on cmdline.
3. Switch off your phone. Now, Press POWER BUTTON + VOLUME UP button for about 5 seconds. A menu should appear. Note: VOLUME UP allows to navigate the menu (move down the menu). Press VOLUME DOWN button for selecting/choosing fastboot. On your phone, it should say something like
Code:
=> FASTBOOT MODE...
Connect your phone to the computer if it wasn't already.
4. (Assuming Win 7) Click on start menu > Search for 'Command Prompt' and right click and select 'Run as Administrator'.
5. On command prompt, Type:
Code:
fastboot devices
If it shows something, that means we can proceed to unlocking bootloader. Otherwise, it means that the driver was not installed correctly.
6. Now, Type the following commands:
Code:
fastboot oem unlock
fastboot format userdata
fastboot reboot
Now, your bootloader is unlocked.
Install a custom recovery.
1. Download custom recovery from this thread.
2. Place the download file, 'recovery.img' file in C:\ drive. (Again, you can place it anywhere but this tutorial assumes this path).
3. Run the following command (Assuming already in fastboot mode again. If not, follow the above steps to go to fastboot mode). :
Code:
fastboot flash recovery c:\recovery.img
After doing so, it should look like this:
4. Reboot your phone and you are done by typing:
Code:
fastboot reboot
Now, you have installed CWM custom recovery. On to installing root.
Rooting your phone:
1. After installing custom recovery, download Super-Su .zip file.
2. Place the .zip file on your sd-card. If your computer doesn't show your phone as MTP device, download the drivers from here.
3. Boot into recovery, by pressing POWER OFF + Volume UP button for 5 secs and choosing Recovery by pressing Volume Down (NOTE: Use Volume UP for menu navigation)
4. After booting into recovery, Choose 'Install Zip'. You can use Volume UP and Volume Down for navigating here and Power Off button for selecting a menu item.
5. Now, select 'choose zip from /external_sd' and not '/sdcard'
6. Select the Super-Su zip file you placed on your sd card and install it.
Now, Reboot your phone. It might say something like 'su may have been removed' but ignore and press 'No'.
Tutorial Complete
Let me know if there are any errors in this Tutorial.

Hi, thanks for the tutorial. Can you explain the necessity for using "fastboot format userdata" given "oem unlock" command in addition to unlocking the bootloader clears user data.

littleromeo said:
Hi, thanks for the tutorial. Can you explain the necessity for using "fastboot format userdata" given "oem unlock" command in addition to unlocking the bootloader clears user data.
Click to expand...
Click to collapse
Someone in this thread reported that they got stuck on the recovery, meaning the phone boot normally.
The port maker for recovery for our phone mentioned formatting userdata command in his post, so I did the same. I didn't want newbies to experience any trouble.

nice guide ..
but I guess "add adb and fastboot to system path " shall be made optional .. this will make guide little simpler and shorter ..

Hey
Can anybody please insure any android device that has been successfully rooted by this method ? Also is waiting for towelroot worth it ??

tanuj123 said:
Can anybody please insure any android device that has been successfully rooted by this method ? Also is waiting for towelroot worth it ??
Click to expand...
Click to collapse
I have used this method myself, but I am also the OP so.... :victory:

Iam in a weird situation , I did flash many times before but I dont know how it made my device like this ... THE PROBLEM IS WITH DRIVERS and also SDcard
First I unlocked my bootloader then flashed cm11 on it ( Which was on lollipop official) and I forgot to download gapps so in connected my phone to pc only to find my computer doesnt recognise my phone it make sound but nothing shows up I tried clicking MTP again and again but nothing happens , WHEN I TRIED ADB it shows no devices in the list , I took out the sd card to copy files manually and the sd card says its write protected ..... GUYS HELP @stirredo

What are you using to read your SD card on your computer?
If you are using SD card adapter, make the sure write lock is turned off.

Man thankyou but After installing the driver you gave my phone gets detected by pc but only when I turn on usb debugging @stirredo
Sent from my Xperia P using XDA Free mobile app

Kaushik124 said:
Man thankyou but After installing the driver you gave my phone gets detected by pc but only when I turn on usb debugging
Sent from my Xperia P using XDA Free mobile app
Click to expand...
Click to collapse
That is the same issue faced by me .

Saurabh K said:
That is the same issue faced by me .
Click to expand...
Click to collapse
Did you find any solution
Sent from my Xperia P using XDA Free mobile app

Not yet, but trying....
Sent from my Sparkle V

thanks for this awesome tutuorial.... But i have a problem in unlocking the tutorial
The problem is that how can i unlock my bootloader when oem unlocking is turned off...
Recently i tried to flash CM12.1 on my YU YUNIQUE YU4711 without turning on OEM unlocking and now I am stuck at the Fastboot mode so i cant start up my phone.... So i wanted to know that how i can unlock the bootloader when OEM unlocking is turned off..
PS- I cant even go to recovery moded
thanks in advance

Format Userdata
stirredo said:
Someone in this thread reported that they got stuck on the recovery, meaning the phone boot normally.
The port maker for recovery for our phone mentioned formatting userdata command in his post, so I did the same. I didn't want newbies to experience any trouble.
Click to expand...
Click to collapse
I did got stuck at bootloader when I dedn't format Userdata. Thanx for the tip.
---------- Post added at 03:01 PM ---------- Previous post was at 02:53 PM ----------
When I opened SuperSu after installing SuperSu through recovery, it says "There is no SU binary installed, and SuperSU cannot install it. This is a problem! If you just upgraded to Android 4.3, you need to manually re-root - consult the relevant forums for your device!"
What do I do now?

stirredo said:
Hello,
I know there are some tutorials for this already but I felt like they missed out a few steps that might not be obvious to some who are new to this.
This tutorial applies to all of Android One Device (Micromax Canvas A1, Karbonn Sparkle V Blue, Spice Mi-498 Dream Uno).
Unlocking bootloader will lead to formating of your phone. The stuff inside your sd card is safe but all your apps and their data will be deleted.
Unlocking bootloader:
1. Download Universal ADB Driver installer from here.
2. Connect your phone and run the Universal ADB Driver installer. Click 'Install' button and a warning should pop up. Just click "Install anyway" and it should look like this:
3. Download ADT Bundle from here for Win-32 Bit and from here for 64-Bit . If you are unsure which version of windows you have just download the 32-Bit one.
4. Extract the zip file in your C:\ drive like this (You can install it wherever you like but this tutorials assumes this location for simplicity). Add adb and fastboot to system path by following this tutorial . This will allow you to run adb and fastboot commands from any location on cmdline.
3. Switch off your phone. Now, Press POWER BUTTON + VOLUME UP button for about 5 seconds. A menu should appear. Note: VOLUME UP allows to navigate the menu (move down the menu). Press VOLUME DOWN button for selecting/choosing fastboot. On your phone, it should say something like
Code:
=> FASTBOOT MODE...
Connect your phone to the computer if it wasn't already.
4. (Assuming Win 7) Click on start menu > Search for 'Command Prompt' and right click and select 'Run as Administrator'.
5. On command prompt, Type:
Code:
fastboot devices
If it shows something, that means we can proceed to unlocking bootloader. Otherwise, it means that the driver was not installed correctly.
6. Now, Type the following commands:
Code:
fastboot oem unlock
fastboot format userdata
fastboot reboot
Now, your bootloader is unlocked.
Install a custom recovery.
1. Download custom recovery from this thread.
2. Place the download file, 'recovery.img' file in C:\ drive. (Again, you can place it anywhere but this tutorial assumes this path).
3. Run the following command (Assuming already in fastboot mode again. If not, follow the above steps to go to fastboot mode). :
Code:
fastboot flash recovery c:\recovery.img
After doing so, it should look like this:
4. Reboot your phone and you are done by typing:
Code:
fastboot reboot
Now, you have installed CWM custom recovery. On to installing root.
Rooting your phone:
1. After installing custom recovery, download Super-Su .zip file.
2. Place the .zip file on your sd-card. If your computer doesn't show your phone as MTP device, download the drivers from here.
3. Boot into recovery, by pressing POWER OFF + Volume UP button for 5 secs and choosing Recovery by pressing Volume Down (NOTE: Use Volume UP for menu navigation)
4. After booting into recovery, Choose 'Install Zip'. You can use Volume UP and Volume Down for navigating here and Power Off button for selecting a menu item.
5. Now, select 'choose zip from /external_sd' and not '/sdcard'
6. Select the Super-Su zip file you placed on your sd card and install it.
Now, Reboot your phone. It might say something like 'su may have been removed' but ignore and press 'No'.
Tutorial Complete
Let me know if there are any errors in this Tutorial.
Click to expand...
Click to collapse
bro, my bootloader is already unlocked, so i was using the flash recovery command directly, and i was unable to flash recovery, everytime i go into recovery it opens stock recovery, what should i do to flash recovery now, no method is working, is it compulsary to unlock bootloader every time flashing recovery, mine is already unlocked, but cant able to flash recovery, please help ,its urgent.

I am on a custom ROM right now( Resurrection ) and have unlocked the bootloader
Can I relock the bootloader using Androidone tool
Will it format userdata?
Can I keep the Custom ROM after relocking?
Please help
Device-Mi-498

hi my device is not boot after restart.always need to run fastboot continue. have you any idea how to resolved ?

my phone showing device not found error in ADB driver installer. actually phone is unable to start, it is continuously looping in start logo

is the fastboot format userdata command required? what will happen if i fail to issue the fastboot format command following fastboot oem unlock command?

hello i want the unlocked bootloader file for my Micromax e313 please send me the link to get it please help me

[Q] HTC One, No OS

So I recently rooted my HTC One m7 (unlocked US gsm version) and everything seemed alright.
Somewhere between installing a new rom (ARHD 84.0) and restarting my phone, I managed to wipe my phone (everything is gone, no os).
I managed to get myself back into recovery mode but since my computer no longer recognises it, I have no way to put an OS back on.
I have tried:
adb sideload
adb push (although I might not be doing in right)
RUU
For clarification,
my bootloader is unlocked and I can access it from cmd
Upon restart, the phone just stays on the HTC logo screen
TWRP can be accessed, but the phone has no OS or rom to install
does anyone know what I can do to get my phone to a working state? (restore it, put a new rom, I don't really care)
Thank you very much

treeco72 said:
So I recently rooted my HTC One m7 (unlocked US gsm version) and everything seemed alright.
Somewhere between installing a new rom (ARHD 84.0) and restarting my phone, I managed to wipe my phone (everything is gone, no os).
I managed to get myself back into recovery mode but since my computer no longer recognises it, I have no way to put an OS back on.
I have tried:
adb sideload
adb push (although I might not be doing in right)
RUU
For clarification,
my bootloader is unlocked and I can access it from cmd
Upon restart, the phone just stays on the HTC logo screen
TWRP can be accessed, but the phone has no OS or rom to install
does anyone know what I can do to get my phone to a working state? (restore it, put a new rom, I don't really care)
Thank you very much
Click to expand...
Click to collapse
What custom recovery are you using and when in recovery does adb devices return you serial number?

treeco72 said:
So I recently rooted my HTC One m7 (unlocked US gsm version) and everything seemed alright.
Somewhere between installing a new rom (ARHD 84.0) and restarting my phone, I managed to wipe my phone (everything is gone, no os).
I managed to get myself back into recovery mode but since my computer no longer recognises it, I have no way to put an OS back on.
I have tried:
adb sideload
adb push (although I might not be doing in right)
RUU
For clarification,
my bootloader is unlocked and I can access it from cmd
Upon restart, the phone just stays on the HTC logo screen
TWRP can be accessed, but the phone has no OS or rom to install
does anyone know what I can do to get my phone to a working state? (restore it, put a new rom, I don't really care)
Thank you very much
Click to expand...
Click to collapse
Follow this guide:
Originally posted by @alrayHTC ONE M7_U/M7_UL - ADB PUSH & FLASH A ROM - DETAILED INSTRUCTIONS
Prerequisites:
You need ADB and FASTBOOT on your computer,
either by installing the Android SDK or Minimal ADB and FASTBOOT
You need to know how to start a fastboot/adb command prompt:
To open a command window prompt, in Windows go to Start Menu --> ''Run'' then type cmd. Change the directory to the ADB folder on your machine:
If using the default install location for the SDK:
Code:
cd C:\adt-bundle-windows-x86_64-<DATE>\sdk\platform-tools
If using the default install location of Minimal ADB and FASTBOOT:
Code:
cd C:\Program Files (x86)\Minimal ADB and Fastboot
Or hold left shift + right click a blank space inside the folder where adb and fastboot are located and select ''Open command window here'' from the contextual menu.
{
"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"
}
You need TWRP recovery on your device.
We still recommend to use version 2.6.3.3 for all roms
except if another version is specified in the rom OP.
Use 2.7.1.1+ for roms that require "block:by-name" support (CM11)
Unlock bootloader if not already unlocked:
Thanks to Electroz for the video tutorial
Flash TWRP Recovery:
Make sure the recovery.img file is in the same folder where adb and fastboot are located
(C:\adt-bundle-windows-x86_64-<DATE>\sdk\platform-tools or C:\Program Files (x86)\Minimal ADB and Fastboot)
reboot phone in bootloader mode
Flash the recovery:
Code:
fastboot flash recovery name_of_recovery.img
fastboot erase cache
fastboot reboot-bootloader
You need your HTC drivers correctly installed on your PC:
If not, follow this guide (thanks to nkk71):
originally from @nkk71: [GUIDE] [02-MAR-2014] nkk71's SuperGUIDE to returning 100% back to stock
follow the below instructions to fix
Open "Device Manager" -> select the unknown "One" -> right-click -> "Update Driver Software ..." -> "Browse my computer" -> "Let me pick" -> "Android USB Devices" -> select "My HTC ..." -> install that
just in case, HTC Drivers can be found here: [Drivers] HTC Drivers for Windows - Several Versions (credits to @mdmower)
though you should already have them since you have been using your phone any ways
for those who like a visual guide:
okay so I did a fastboot boot command, and as you can see it didn't install correct driver
Open "Device Manager"
there's the culprit
right click and Update Driver Software
select Browse my computer for driver software
select Let me pick from a list of device drivers on my computer
select Android USB Devices
select My HTC ... (if you have more than one version, choose the latest)
warning, select Yes
successful installation
now it looks better
and can confirm:
Code:
C:\ADB3>[B]adb devices[/B]
List of devices attached
HTxxxxxxxxxx recovery
Click to expand...
Click to collapse
​
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Procedure:
Make sure the ROM you want to flash is in the same folder where ADB and FASTBOOT are.
(C:\adt-bundle-windows-x86_64-<DATE>\sdk\platform-tools or C:\Program Files (x86)\Minimal ADB and Fastboot)
Here is a list of the HTC M7 roms. Some other roms can be found here.
Connect your phone to computer using usb cable
(if not using the official HTC USB calble, make sure
you are using a USB data cable and not only a charging
cable. Data cables have 4 contacts: 5V, GND, DATA+, DATA-.
Charging cable only have 5V and GND contact and will not work)
Reboot phone in recovery mode (TWRP):
If phone is booted in OS:
Code:
adb reboot recovery
if not booted or bootlooping, hold power button + volume down until phone boot in bootloader mode
then select BOOTLOADER then RECOVERY using volume up/down to navigate and power button to select.
Make sure your phone is booted in TWRP main menu:
transfer the rom to your /sdcard folder:
Code:
adb push name_of_rom.zip /sdcard/
Wait for the zip file to transfer, this can take several minutes (5-15) and there is no progress bar, the command prompt will be unresponsive for that duration. When the command prompt is responsive again and display how much bytes transferred in X seconds, the transfer is completed:
In TWRP main menu, select ''INSTALL''
Browse the installation menu and select your rom zip file inside /sdcard folder:
Swipe to confirm you want to flash the rom
Reboot phone
Click to expand...
Click to collapse
Click to expand...
Click to collapse

clsA said:
What custom recovery are you using and when in recovery does adb devices return you serial number?
Click to expand...
Click to collapse
Im using TWRP v2.6.3.0
and adb devices does NOT return a serial number

treeco72 said:
Im using TWRP v2.6.3.0
and adb devices does NOT return a serial number
Click to expand...
Click to collapse
your TWRP is too old and you can follow the Prerequisites above step 2 and 3 to get your driver fixed

In device manager, my phone has no errors related to driver (whether I choose "my htc" or "android adb interface") cmd still shows no devices.
when I try to push the file i get

treeco72 said:
In device manager, my phone has no errors related to driver (whether I choose "my htc" or "android adb interface") cmd still shows no devices.
when I try to push the file i get
Click to expand...
Click to collapse
update TWRP

clsA said:
update TWRP
Click to expand...
Click to collapse
forgive me if this is a stupid question but how do I update twrp if I can't access anything on the phone?
Thank you for your help

treeco72 said:
In device manager, my phone has no errors related to driver (whether I choose "my htc" or "android adb interface") cmd still shows no devices.
when I try to push the file i get
Click to expand...
Click to collapse
If you are in Android/OS then USB debugging needs to be enabled in Settings before ADB will recognize your phone. If you are in an updated Custom Recovery then ADB should recognize your phone.
---------- Post added at 03:25 PM ---------- Previous post was at 03:23 PM ----------
treeco72 said:
forgive me if this is a stupid question but how do I update twrp if I can't access anything on the phone?
Thank you for your help
Click to expand...
Click to collapse
Can you manually get the phone into bootloader? If so, with it connected to the computer do you see FASTBOOT USB?

treeco72 said:
forgive me if this is a stupid question but how do I update twrp if I can't access anything on the phone?
Thank you for your help
Click to expand...
Click to collapse
you flash recovery in fastboot USB
it's all in the steps posted above

clsA said:
you flash recovery in fastboot USB
Click to expand...
Click to collapse
ahh thank you, yeah dumb question. Do you recommend a specific version? or just the latest one

when I try to flash a new recovery image it says <waiting for device>
on my phone it says "FASTBOOT USB" and other (non related) software detects a connected device
thoughts?

treeco72 said:
ahh thank you, yeah dumb question. Do you recommend a specific version? or just the latest one
Click to expand...
Click to collapse
2.6.3.3
---------- Post added at 05:59 PM ---------- Previous post was at 05:58 PM ----------
treeco72 said:
when I try to flash a new recovery image it says <waiting for device>
on my phone it says "FASTBOOT USB" and other (non related) software detects a connected device
thoughts?
Click to expand...
Click to collapse
connect your phone to your computer, boot it in bootloader/fastboot usb mode. Open windows device manager and take a screenshot.
post the screenshot here

alray said:
2.6.3.3
---------- Post added at 05:59 PM ---------- Previous post was at 05:58 PM ----------
connect your phone to your computer, boot it in bootloader/fastboot usb mode. Open windows device manager and take a screenshot.
post the screenshot here
Click to expand...
Click to collapse
thanks for the help

treeco72 said:
thanks for the help
Click to expand...
Click to collapse
When in bootloader / fastboot usb mode your phone should be listed in windows device manager as a "Android USB Device --> My HTC" not "Android ADB interface"
Its either because you are trying to do fastboot commands when not booted in bootloader mode or because your drivers are not installed correctly.
install latest htc drivers, reboot in bootloader mode and try again
---------- Post added at 06:15 PM ---------- Previous post was at 06:08 PM ----------
latest drivers can be found here: https://www.mediafire.com/folder/jgt1b5bc2stwf/Drivers
4.14.0.001

updated the recovery image, turns out I needed to restart my computer. will post follow up

Everything seems to be working great again! I want to thank everyone who took the time to help me today, so thanks!

[GUIDE] Root/Flash for Xiaomi Redmi 2

AnandMore's How-To Guide For Beginners
Xiaomi Redmi 2
{
"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"
}
Intro:
This thread will serve as a location for basic how-to guides for the Xiaomi Redmi 2. I'm going to start off with a couple of the more obvious ones and go from there. If anyone has any suggestions for additions please feel free to let me know.
By attempting any of the processes listed this thread you accept full responsibility for your actions. I will not be held responsible if your device stops working, catches on fire, or turns into a hipster and claims to have been modified before it was cool.
Index:
Post #1 - Rooting your Redmi 2
Post #2 - Flashing Custom Recovery
Post #3 - Flashing Custom ROMs
Post #4 - Flashing Custom Kernels
Resources:
Everything you need for Xiaomi Redmi 2 is available in the below given thread -
[INDEX] Xiaomi Redmi 2

Rooting your Redmi 2:
This guide will root your device through Stock MI Recovery(Works with TWRP also), but this is not Native Root. A new app named SuperSU will be installed, which will give root Permission.
Note:
Rooting does not Void Warranty.
Caution:
This is a safe process, but I am not responsible for anything bad that happens to your phone.
In most cases this approach of rooting should not block OTA updates.
Steps to follow for rooting:
Download the Root.zip and Copy the file to the folder 'Internal storage' (root of internal storage).
(File at the end of thread)
Open the Updater app, Press the 3 dots at Right Top Corner, A menu will open. Tap on “Choose Update Package“ and select the Root.zip File.
Wait until device will reboot.
After reboot a new app SuperSu will be installed.
Open the app and Choose "Continue".
Choose "Normal", Don't Choose TWRP/CWM, device will go into Boot Loop.
Note - Don't Choose TWRP/CWM, it will brick your device.
After sucessful updation , press ok.
Your Phone has now Root Permission.
Open any app using Root permission and SuperSU will ask for Permission.
Enjoy your rooted Redmi 2.
Un Root The Device:
For Un Root , open the SuperSU app,tap on Settings, Choose Full Unroot.
Your Device is Un Rooted Sucessfully. The SuperSU app will be removed.

Flashing Custom Recovery:
From Mobile:
Install Flashify app from Playstore
Once installed, access the application through app drawer.
Allow root access now and get navigate to Flashify’s home screen.
First take a backup of your recovery in case something goes wrong. (RECOMMENDED)
Now tap on recovery image and by "Choose the file" menu locate the .img file you want to flash.
After successful flashing it will ask you to reboot your device.
Done! You have custom recovery on your phone.
From PC:
Enable USB debugging, go to settings>about phone and then tap on Android/MIUI version 5 times. Developer Options will be enabled. Now go back to settings>Developer options and enable USB debugging.
ADB and Fastboot Drivers installed on your PC. I can provide you the drivers but it would be a better option to install MiFlash to get all the necessary drivers and Miflash software with you for future use.
Install Miflash on your PC. Lets suppose we installed it in C:\Xiaomi folder.
You can see two folders, proceed to "adb' folder
Then proceed to "Google" folder.
Proceed to "Android" Folder.
We are at our destination.
Now Hold down "Shift" button on your computer keyboard and right click with mouse on an empty part of the window. You will see that in the menu that appears, you have an option - "open command window here". Click on that
To verify if ADB is working and installed correctly, type "adb version" in the command window that opened without the code. You should get the adb version which means its working fine.
Turn off your Phone. When its completely switched off, press and hold "Volume Down" and "Power" button together and then the phone will turn on in Fastboot mode.
Use the USB cable to connect Phone to PC.
Copy the Recovery.img in the Android folder where we are running the Command prompt. (C:\Xiaomi\adb\Google\Android in my case as i installed Mi flash in C:\Xiaomi folder)
Now go back to command promt and enter the following commands -
Code:
fastboot devices
Once you enter that command, you will get a non-empty name for the device meaning the device is connected. Proceed to enter the next command to flash recovery image -
Code:
fastboot flash recovery recovery.img
Once you enter this command, the recovery image will be flashed on your device. Once it is completed, enter the final command to reboot your phone -
Code:
fastboot reboot
Your phone will reboot.
You have have now completed flashing custom recovery replacing Stock Mi recovery on your Xiaomi Redmi 2.

Flashing custom ROMs:
Steps to Follow:
Download and transfer the custom ROM you wish to flash to your device’s storage.
Boot your device into TWRP recovery.
Select “Wipe” from TWRP main menu and do a “Swipe to Factory Reset” on the bottom of screen.
Note: This will factory reset your device. If your custom ROM doesn’t require a factory reset, then simply skip this step.
Go back to TWRP main menu, tap on “Install” and select the custom ROMs .zip file that you transferred to your device in Step 1.
After selecting the .zip file, do “Swipe to Confirm Flash” on the bottom of screen to begin the custom ROM installation process. This may take some time.
Once your ROM is successfully flashed, you’ll see “Wipe cache/dalvik” option, select it and then do “Swipe to wipe” on bottom of screen.
Once cache & dalvik wipe completes, hit the “Back” button on-screen and then select “Reboot System” button.
That’s all. Your device will now reboot with the custom ROM you just flashed. Since this will be the first reboot after flashing a new ROM, it might take some time to rebuild cache and finish boot, have patience.

Flashing Custom Kernels:
Steps to Follow:
Download and transfer the custom Kernel you wish to flash to your device’s storage.
Boot your device into TWRP recovery.
In the TWRP main menu, tap on “Install” and select the custom Kernel .zip file that you transferred to your device in Step 1.
After selecting the .zip file, do “Swipe to Confirm Flash” on the bottom of screen to begin the custom Kernel installation process. This may take some time.
Once flashing completes, hit the “Back” button on-screen and then select “Reboot System” button.
That’s all. Your device will now reboot with the custom Kernel you just flashed. Since this will be the first reboot after flashing a new Kernel, it might take some time to rebuild cache and finish boot, have patience.

For list of all available Roms visit this thread :
http://forum.xda-developers.com/redmi-2/how-to/available-custom-marshmallow-roms-redmi-t3278535
Click to expand...
Click to collapse
Better if you make lollipop ROMs thread too

Superb work bro thanks ...u

Isn't MIUI rooted out of the box already? [emoji52]

Stachura5 said:
Isn't MIUI rooted out of the box already? [emoji52]
Click to expand...
Click to collapse
Developer ROMs are. Global ROMs aren't.
Device comes with global ROM :3

noobpremium said:
Better if you make lollipop ROMs thread too
Click to expand...
Click to collapse
I made both lollipop and marshmallow roms in one thread. So you think i should make seperate one for lollipop.

Stachura5 said:
Isn't MIUI rooted out of the box already? [emoji52]
Click to expand...
Click to collapse
All roms(Beta,developer,stable) for Redmi 2 are not Pre rooted.

Added videos tutorials for better understanding.

Great info, thanks a lot!
I have a very basic, very likely extremely stupid question: I flashed an early CM12.1 build (using CWM afaik) and for unknown reasons, I cannot boot into recovery and don't have root. How can I re-gain root access from here?

my phone also rebooting. please help me. how to go to recovery?

srmohanrajan said:
my phone also rebooting. please help me. how to go to recovery?
Click to expand...
Click to collapse
1) Switch off the phone.
2) Press the Volume Down, Volume Up and the Power Button at the same time, about 2-3 seconds until the mi logo shows up.
3) Recovery mode menu will appear.

Fr3ak23 said:
Great info, thanks a lot!
I have a very basic, very likely extremely stupid question: I flashed an early CM12.1 build (using CWM afaik) and for unknown reasons, I cannot boot into recovery and don't have root. How can I re-gain root access from here?
Click to expand...
Click to collapse
Follow the same steps to boot into recovery and flash SuperSU v2.4.6 zip via recovery
(And remember you are responsible if anything happens to the device)

omg, I am so stupid. I tried vol up + power, vol down + power and all possible combinations including the home button, but never vol up + vol down + power button. Thank you!

Fr3ak23 said:
omg, I am so stupid. I tried vol up + power, vol down + power and all possible combinations including the home button, but never vol up + vol down + power button. Thank you!
Click to expand...
Click to collapse
No problem bro !
✌

Great !

New CM 12.1 is awesome, finally the camera works
I am curious on why I keep on losing root access. I never had that issue with any other phones and custom ROMs.