Develop Bugs

[HOWTO] Install Google SDK and ADB drivers in Windows 7

I'm posting this guide because my Galaxy Nexus I9250 I purchased from Google Play would not to recognize in any way, shape or form the official Google drivers provided into Android SDK. Obviously, if you installed any Samsung drivers, you will have to uninstall them. Personally, I always connect the device to my PC and let Windows Update find the best driver. In this way, the basic Windows interface is handled by Microsoft drivers:
{
"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"
}
Google SDK 64bits Setup
This is a quick howto for those who actually want to setup their SDK properly in Windows 7 64bits. I saw a lot of craziness on the Internet so I wanted to share how I set a proper 64bits development environment.
Android SDK: http://developer.android.com/sdk/ (installer_r21-windows.exe)
Java JDK: http://www.oracle.com/technetwork/java/javase/downloads/ (jdk-7u5-windows-x64.exe)
Eclipse Classic: http://www.eclipse.org/downloads/ (eclipse-SDK-4.2-win32-x86_64.zip)
First, download the 64bits software versions, not 32bits. Android SDK is the only 32bits package but it will work fine with 64bits development tools, if you know what you are doing. Obviously, if you are on a 32bits OS download the 32bits software versions. We are discussing a 64bits setup, so let's move on.
Install Java JDK and only if you run a 64bits OS, set a JAVA_HOME variable with value "%ProgramFiles%\Java\jdk1.7.0_05" into Environment Variables (adjust the value with whatever version you downloaded):
Reboot your PC to enable all the settings done above.
Next, install Android SDK. You only need to download Android SDK Tools, Android SDK Platform-tools and Google USB Driver, if you just want to play with the phone. If you plan to develop apps, install also the API of your choice and Eclipse Classic (yes, that is the recommended version by Google devs).
To make available everywhere your platform tools (adb, fastboot, etc.), add your platform-tools directory to Path:
Myself, I installed the SDK in "C:\Program Files (x86)\Android\sdk" directory, so my path looks like:
Code:
%SystemRoot%\system32;%SystemRoot%;%SystemRoot%\System32\Wbem;%SYSTEMROOT%\System32\WindowsPowerShell\v1.0\;%ProgramFiles(x86)%\Android\sdk\platform-tools
Technically, you need to add the ";%ProgramFiles(x86)%\Android\sdk\platform-tools" location at the end of your current path.
Reboot your PC to enable all the settings done above.
Now, on with the fun part. There are 2 drivers needed for Google Nexus, the Composite ADB and Bootloader (Android 1.0).
Android Composite ADB Interface Driver
First, enable USB Debugging in your phone:
Plug your USB cable, you will notice in Device Manager the failed driver notice:
Right-click on it and select "Update Driver Software...", then "Browse my computer for driver software". Don't bother browsing to your ADB USB driver location, it will not install the proper driver. Instead, click on "Let me pick from a list of device drivers on my computer" button:
Make sure "Show All Devices" is selected and click on Next button:
With the list of devices displayed, click on Have Disk button:
Browse to your Google Driver location, mines is set in "C:\Program Files (x86)\Android\sdk\extras\google\usb_driver":
Pick the "Android Composite ADB Interface" driver and click on Next button:
You will be asked to accept the driver installation, do it and be done with this part of drivers setup:
Android Bootloader Interface Driver
Make sure USB Debugging is still enabled in your phone. With the USB cable connected, manually boot into Bootloader mode by powering down your phone and restarting it with all 3 buttons pressed (Volume Up + Volume Down + Power). You will notice in Device Manager the new unrecognized Android 1.0 device. Follow the same steps explained above and when you reach the driver selection, choose "Android Bootloader Interface":
To test the setup, run few basic commands:
Code:
adb devices
adb reboot bootloader
fastboot reboot
You are done, enjoy the official USB drivers from Google.

Quick Root Command references
Nexus Images: https://developers.google.com/android/nexus/images#mysid
CWM: http://www.clockworkmod.com/rommanager/
Superuser: http://hosted.androidsu.com/superuser/
SuperSU: http://download.chainfire.eu/205/SuperSU/
Root Device
1) Unlock the bootloader (if locked):
Code:
adb reboot bootloader
fastboot oem unlock
2) Install Supersuer + Root (match the file names with the ones downloaded):
Code:
adb push Superuser-3.1.3-arm-signed.zip /sdcard/
adb reboot bootloader
fastboot boot recovery-clockwork-6.0.1.0-maguro.img
Flash Superuser: On device, select "install zip from sdcard", then "choose zip from sdcard" and select "Superuser-3.1.3-arm-signed.zip". Confirm install, then "+++++Go Back+++++" and "reboot system now".
3) Lock the bootloader (optional):
Code:
adb reboot bootloader
fastboot oem lock
Stock Device
1) Unlock the bootloader (if locked):
Code:
adb reboot bootloader
fastboot oem unlock
2) Install the image files (match the file names with the ones downloaded).
Commands are listed inside flash-all.sh shell script, validate them:
Code:
adb reboot bootloader
fastboot flash bootloader bootloader-maguro-primelc03.img
fastboot reboot-bootloader
fastboot flash radio radio-maguro-i9250xxlf1.img
fastboot reboot-bootloader
fastboot -w update image-takju-jro03c.zip
3) Lock the bootloader:
Code:
adb reboot bootloader
fastboot oem lock
Backup Device
Code:
adb backup -apk -shared -all -f backup.ab

TECK said:
Nexus Images: https://developers.google.com/android/nexus/images
CWM: http://www.clockworkmod.com/rommanager/
Superuser: http://hosted.androidsu.com/superuser/
Root Device
1) Unlock the bootloader (if locked):
Code:
adb reboot bootloader
fastboot oem unlock
2) Install Supersuer + Root (match the file names with the ones downloaded):
Code:
adb push Superuser-3.1.3-arm-signed.zip /sdcard/
adb reboot bootloader
fastboot boot recovery-clockwork-6.0.1.0-maguro.img
Flash Superuser: On device, select "install zip from sdcard", then "choose zip from sdcard" and select "Superuser-3.1.3-arm-signed.zip". Confirm install, then "+++++Go Back+++++" and "reboot system now".
3) Lock the bootloader (optional):
Code:
adb reboot bootloader
fastboot oem lock
Stock Device
1) Unlock the bootloader (if locked):
Code:
adb reboot bootloader
fastboot oem unlock
2) Install the image files (match the file names with the ones downloaded).
Commands are listed inside flash-all.sh shell script, validate them:
Code:
fastboot reboot-bootloader
fastboot flash bootloader bootloader-maguro-primelc03.img
fastboot reboot-bootloader
fastboot flash radio radio-maguro-i9250xxlf1.img
fastboot reboot-bootloader
fastboot -w update image-takju-jro03c.zip
3) Lock the bootloader:
Code:
adb reboot bootloader
fastboot oem lock
Click to expand...
Click to collapse
This is nice I wish this was around 2 weeks earlier when I got this phone this would have made setting up a lot easier. This deserves to be sticky
Sent from my Galaxy Nexus using Tapatalk 2

I added also a quick Howto for the Android SDK setup in Windows 64bits. Lots of crazy info out there on the Internet so I said might as well post it so others can do it right in their computers.

TECK said:
I added also a quick Howto for the Android SDK setup in Windows 64bits. Lots of crazy info out there on the Internet so I said might as well post it so others can do it right in their computers.
Click to expand...
Click to collapse
glad i came across this post. I'm going to use your instructions to return my daughter's GSM Galaxy Nexus to stock JB so we can determine if the proximity sensor is bad or if it's due to the other JB ROMs i've put on her phone. right now, the proximity sensor does not turn the screen off when she places the phone to her ear during phone calls.
question: i prefer not to overwrite the CWM recovery, so i'm planning to remove the recovery.img from the image-yakju-jro03c.zip file before updating via fastboot. next i'll reboot to recovery and flash the superuser zip file to gain ROOT access. my question is this: will removing the recovery img cause the update via fastboot to fail? thanks to anyone who replies to my question.

I would simply flash the entire stock image without skipping any files. Then temporarily flash back the CWM, just to keep the phone stock.
Code:
adb reboot bootloader
fastboot boot recovery-clockwork-6.0.1.0-maguro.img
This will not write CWM to the phone, but rather use it once to bypass the stock recovery. Personally, I'm only interested to root the device and will not install custom ROM's. But even if you do install custom ROM's, you rarely need CWM... and if you do, you will work near your computer where you have access to adb.

This is a splendid guide!
Absolutely what all new Androiders need.
Sent from my Transformer TF101 using Tapatalk 2

Did everything you said and got to the point where I was testing those commands, and it says devices attached but my device isnt listed. I was still in boootloader and fastboot usb was attached. is that correct? any ideas? I do have CM9 installed and there are plenty of options regarding root access.

TECK said:
To test the setup, run few basic commands:
Code:
adb devices
adb reboot bootloader
fastboot reboot
Click to expand...
Click to collapse
Mate, when I type "adb devices" I am getting an error saying that "'adb' is not recognized as an internal or external command, operable program or batch file"
I installed Android SDK and Java SE JDK and it all went well. I installed the drivers and when in fastboot mode, I get "Samsung Galaxy Nexus BootLoader Interface" in Device Manager, which I think is what I should be getting.
Would you know what is it that I am missing? Could it be something that I haven't installed from the Android SDK? Thanks again for the tutorial.

You need to change to the directory in which you installed the SDK
So like:
cd <insert directory here and remove the arrow brackets>
Sent from my Galaxy Nexus using Tapatalk 2

geoffcorey said:
You need to change to the directory in which you installed the SDK
So like:
cd <insert directory here and remove the arrow brackets>
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
I'll try that, thanks.
His screenshot shows that he is not in the SDK installed folder though.
My phone was in fastboot mode when I tried that. I hope that's the correct mode.
One more thing, when I choose go to Recovery in fastboot, the red triangle comes up, but Volume Up + Power doesn't do anything and I have to take out the battery in order to reboot.

bozint said:
I'll try that, thanks.
His screenshot shows that he is not in the SDK installed folder though.
My phone was in fastboot mode when I tried that. I hope that's the correct mode.
Click to expand...
Click to collapse
That is because you missed this part:
TECK said:
[snip]
To make available everywhere your platform tools (adb, fastboot, etc.), add your platform-tools directory to Path:
Myself, I installed the SDK in "C:\Program Files (x86)\Android\sdk" directory, so my path looks like:
Code:
%SystemRoot%\system32;%SystemRoot%;%SystemRoot%\System32\Wbem;%SYSTEMROOT%\System32\WindowsPowerShell\v1.0\;%ProgramFiles(x86)%\Android\sdk\platform-tools
Technically, you need to add the ";%ProgramFiles(x86)%\Android\sdk\platform-tools" location at the end of your current path.
Reboot your PC to enable all the settings done above.
Click to expand...
Click to collapse
bozint said:
One more thing, when I choose go to Recovery in fastboot, the red triangle comes up, but Volume Up + Power doesn't do anything and I have to take out the battery in order to reboot.
Click to expand...
Click to collapse
What you are seeing is the main screen for the stock recovery. To access the menu from that screen, hold power and press volume up.

efrant said:
That is because you missed this part
Click to expand...
Click to collapse
I did add a line in the Environment Variables, I installed the Android SDK in the root of "C" though (C:\!Android\.....). It might be the issue, and I will use default path after I uninstall it and then install it again. I also added the Java SE in the Environment Variables.
efrant said:
What you are seeing is the main screen for the stock recovery. To access the menu from that screen, hold power and press volume up.
Click to expand...
Click to collapse
Thanks for this, I got into now. I guess all the time I was holding vol.up and then power.
I am on stock now, so in order to root, should I be following the following procedure?
Stock Device
1) Unlock the bootloader (if locked):
Code:
adb reboot bootloader
fastboot oem unlock
2) Install the image files (match the file names with the ones downloaded).
Commands are listed inside flash-all.sh shell script, validate them:
Code:
fastboot reboot-bootloader
fastboot flash bootloader bootloader-maguro-primelc03.img
fastboot reboot-bootloader
fastboot flash radio radio-maguro-i9250xxlf1.img
fastboot reboot-bootloader
fastboot -w update image-takju-jro03c.zip
3) Lock the bootloader:
Code:
adb reboot bootloader
fastboot oem lock
My baseband is XXLF1, and the build is JRO03C.I9250WLH2, if this helps in any way.
Thanks for the comment guys, much appreciated.
====================================================
EDIT: @efrant, I just checked your guide on rooting without unlocking the bootloader, so should I fail with the backup you also referenced in you guide, I will give it a try. The phone is rather new though, so even if I lose some apps it's not that big a deal.

bozint said:
[snip]
I am on stock now, so in order to root, should I be following the following procedure?
Click to expand...
Click to collapse
I think you are confusing a few things. Unlocking the bootloader is not the same as getting root. You should have a look at the "basics" link in my signature.

bozint said:
I did add a line in the Environment Variables, I installed the Android SDK in the root of "C" though (C:\!Android\.....).
Click to expand...
Click to collapse
So the path was not the issue. Originally I had this in Path in the Environment Variables: "....;%!Android%\Google_Dev\android-sdk\platform-tools" and adb did not work unless I went directly inside the platform-tools folder in command prompt.
I then tried to add additional line in Environment Variables for the whole path, without the % symbol (C:\!Android\Google_Dev\android-sdk\platform-tools). And it worked, now adb lists the device at any time and location.
The final line in Path looks like this: ....bunch of lines......;%!Android%\Google_Dev\android-sdk\platform-tools;C:\!Android\Google_Dev\android-sdk\platform-tools

bozint said:
Mate, when I type "adb devices" I am getting an error saying that "'adb' is not recognized as an internal or external command, operable program or batch file"
Click to expand...
Click to collapse
If you add adb to the Windows path, you will not get this error. I explained into tutorial what to do.
Edit: Never mind, efrant explained well what to do.

efrant said:
I think you are confusing a few things. Unlocking the bootloader is not the same as getting root. You should have a look at the "basics" link in my signature.
Click to expand...
Click to collapse
I got it rooted now, but I need to do some additional reading yes. I'll read the guide and hopefully things will be more clear. Thanks guys.

bozint said:
I am on stock now, so in order to root, should I be following the following procedure?
Click to expand...
Click to collapse
No. The tutorial has separate sections, Root Device" and "Stock Device", not "Rooted Device". You want to root, so you follow the "Root" procedure, right?

Does anyone have a separate link to the ADB drivers for windows? I need this pc to recognize my N7 in bootloader etc but I don't want to go through the whole Java SDK etc hassle to get ADB just to get the drivers, it's not my pc.
Thanks

Logic_ said:
Does anyone have a separate link to the ADB drivers for windows? I need this pc to recognize my N7 in bootloader etc but I don't want to go through the whole Java SDK etc hassle to get ADB just to get the drivers, it's not my pc.
Thanks
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1379875

Fastboot-unbrick your device with 'no display'

How to USE FASTBOOT commands in case your Device got Soft-Bricked with NO DISPLAY
Click to expand...
Click to collapse
Let's describe Softbrik:-Anything caused to your phone except damage to Hardware of your phone which put your Device into a state where it is not booting up and kept showing White, Gray, Blue or Black Screen or Either It gets stuck at Company logo Screen. This may occur if something goes wrong during Rooting, flashing Recovery or ROMs or during Updating in Recovery Mode or either being caught by some wrong software or VIRUS !!!
Preface to the Guide:
Fastboot is a command line tool used to directly flash the filesystem in Android devices from a host computer via USB. It allows flashing of unsigned partition images and also can erase partitions. Its a part of Android Developement Kit (Android SDK).
Use of FASTBOOT is disabled in production devices since USB support has been disabled in the bootloader. You must have an Engineering SPL, or an SPL that is S-OFF or Unlocked bootloader to use 'fastboot'.
After installing the Android SDK or ADB Standalone you can use 'fastboot' in addition to the more common ADB.
One can use the attached .android folder if u want to skip downloading Android SDK. (Refer Attachment)
Verify SPL S-OFF or Bootloader Unlocked:
Not required for Micromax !! But certain Production Devices like Sony HTC LG etc may need bootloader to be unlocked before carrying out this process. My simple advice to people is.. "If you enjoy experiments on your device, you must be ROOTED and to ROOT you device you may need to have unlock bootloader"
Preparations:
(1) Download attached .android.zip, Extract and place .androidfolder on C:/ drive of your PC. So the path of this folder will look likeC:/.android
(Never remove this ".android" folder from C:/ coz you will require it whenever u want to experiment with you Droid using ADB or FASTBOOT methods. I assure... You can do a lot more with it; if you really explore how to use various commands !!!)
.android folder is containing adb.exe, fastboot.exe and related drivers adb_usb.ini, android_winusb.ini AdbWinApi.dll and AdbWinUsbApi.dll and other files; all together not more than 800KB
(2) Connect Device in 'USB debugging ON' mode.
Ensure Drivers for your Device are already installed on the host computer
Note: I recommend you should always keep USB Debugging opetion 'ON' as it only can help you, in case, your device get SoftBricked and you cant see anything on Device Screen. Remember that with USB debugging 'OFF' your Device can't communicate with your Host Computer.
(3) Host Computer Ability to Launch Command Prompt:
On Windows-XP or earlier, to start ADB (Android Debug Bridge) You need to locate your folder containing adb.exe where as Windows-7/Vista/Other-Latest-OS can directly launch command prompt from the Folder itself by Shift+Right Click on Mouse and Selecting "Open Command Prompt from here".
Hence 'Locating 'adb' folder-steps' are for XP users only, However higher OS users can skip it and can directly start giving 'adb' commands after opening cmd from .android folder.
(4) So now, Open Command Prompt (in Windows XP), it will return like this:
Code:
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\USERNAME>
(As our adb.exe is in C:/.android.... we will type: Cd C:\.android)
C:\Documents and Settings\USERNAME>Cd C:\.android (Hit Enter)
C:\.android>
Let's give command to detect attached device by writing: 'adb device'. On hitting enter it will list all devices attached to your PC.
Code:
C:\.android>adb devices
List of devices attached
XXXXXXXX-XXXX device
Now u can do a lot while your Device is attached in 'adb mode' e.g.:
Code:
1. Rebooting into Bootloader (FASTBOOT)
2. Installing apps on as /system/app or /data/app
3. Copying Files to/from your SDCARD
4. Pulling Files or Apps already installed on your /system or /data partition
To Understand adb commands and how they work please read:
http://developer.android.com/tools/help/adb.html#commandsummary
Let's come back to ISSUE: "We have a SOFTBRICKED devices !!!"
(1) Booting into FASTBOOT mode:
Let's come back to'fastboot' as we need to flash new ROM or to apply update.zip in a Softbricked deviceNote: Let your device remain connected to PC and don't disconnect untill You finish you job-successfully and get your Device again in working Factory Condition.
""fastboot reboot-bootloader" This command is used to reboot your device into bootloader i.e into fastboot mode) and In this Mode your device will stuck into boot logo only and u cant operate it. ;D Well we are not concerned as we already have a bricked device with no screen display !!!. Lets go ahead...on cmd follow:
Code:
C:\.android>adb reboot-bootloader
C:\.android>fastboot devices
XXXXXXXXXXXX fastboot
(2) Unlocking-ReLocking Bootloader:
(Skip if u working with pre-unlocked devices)
C:\.android>fastboot oem unlock
...
SUCCESSFUL
finished. total time: 118.063s
Click to expand...
Click to collapse
(Accept/Decline warning on your devices screen. Select YES to Unlock)
(Once ROM is flashed) To relock Bootloader use command: fastboot oem lock:
Code:
C:\.android>fastboot oem unlock
...
SUCCESSFULL
finished. total time: 118.063s
(Accept/Decline warning on your devices screen. Select YES to ReLock)]
(Skip if u working with pre-unlocked devices)
(3)Get 'Recovery.img' and 'Update.zip' for your Device:
Lets Wipe the Data and then proceed to Flash new ROM/Update.zip
IMPORTANT: Copy the stock recovery.img and your devices' Update.zip[ in .android folder(You can get it even by searching it in this forum or by Googling for it..) So I assume that you have it....in your .android
Abbreviations:
recovery.img = Stock Recovery of your Device
Update.zip = Update Package/Stock ROM of your Device
Let's start wiping and updating process with following commands:
(4)Wiping Old Data and Flashing new Update.zip:
Code:
C:\.android>fastboot -w
SUCCESSFUL
C:\.android>fastboot update Update.zip
(Here Replace Update with Full Name of your any Update.zip that you copied to .android folder)
Your phone will update and automatically reboot into the Factory State. Cheers !!!
Note: Its important to spell the file name correctly that u want to flash/update. No space between name are allowed. This process will only be successful if your device is still carrying recovery partition 'intact'.
.....If above wiping/updating FAILS....
If you still in "No Display State", extract update.zip to .android folder (U can use 7zip).
You will find following main .img files, each incorporate specific partition on any android device. In our case we can extract following:
boot.img -The main kernel and initrd
recovery.img -A 'backup' kernel, initrd, and OS 4 sysm recovery/maintanance
sytem.img -The main OS
userdata.img -User data and settings
splash.img -Has Boot image. can be splash1 as well.
cache.img -Temp storage
...there can be similar partition names depends on your device type.... but basically these 6 partitions constitute a ROM. Copy all of (6) files to .android folder. (Henceforth, we can use this recovery.img as stock recovery for your device.)
"As your device is bricked/corrupted, we need to erase all old Partitions and flash (rewrite) new partitions that we have extracted from Update zip and placed in .android."
(1) Lets erase all partitions first (one by one)using: fastboot erase <partition>
Code:
C:\.android>fastboot erase system
Successful
C:\.android>fastboot erase recovery
Successful
C:\.android>fastboot erase boot
Successful
C:\.android>fastboot erase userdata
Successful
C:\.android>fastboot erase splash
Successful
C:\.android>fastboot erase cache
Successful
(2) Continuing with Flashing new partionsusing the Images copied in .android:
Command: fastboot flash <partition> <partition_name.img>
Code:
C:\.android>fastboot flash boot boot.img
Successful
C:\.android>fastboot flash recovery recovery.img
Successful
C:\.android>fastboot flash system system.img :(here people gen. get stuck
Successful
C:\.android>fastboot flash userdata userdata.img
Successful
C:\.android>fastboot flash splash splash.img
Successful
C:\.android>fastboot reboot
If all successful, Your phone will update and automatically reboot into the Factory State. Cheers !!!
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
..If you are Unable to flash 'system.img' successfully...
Reason: Your device is not allowing to format and rewrite 'system' partition manually. If your device is Rooted then probably such failure will never occur.
Let's overcome this Issue as well...Try Following...
First, Understand current State of Device...
We Wiped out old partitions and Flashed new partitions except :-\ system :-\ So No System on your Device at present.
What we will do now..
We will now wipe all partitions again
We will then flash only recovery.img saved in .android folder
We will use update.zip saved in .android folder to Flash it using SD Card.
We will copy update.zip on SD Card (using adb). If you can do it manually using a card reader skip step-II in below process.
Step-I: Wiping 'partitions' and Flashing 'recovery.img':Let's wipe all partitions again:
Code:
C:\.android>fastboot -w
C:\.android>fastboot reboot-bootloader
C:\.android>fastboot flash recovery recovery.img
C:\.android>reboot
Step-II: Copy update.zip on SDCARD
Code:
C:\.android>adb push update.zip /data/sdcard
Step-III: As you can't manage to see what is happening on screen(No Display) hence Don't do mistakes here, read carefully and follow exactly:
1.Reboot Device into Recovery Mode:
On cmd type:
Code:
C:\.android>adb reboot recovery
2.Now Press 'Volume(-)' button ONCE. (Once means 'once only'-if you did mistake here repeat the Step-III)
3.Press 'Power' Button TWICEand Leave you Device for some 10 Minutes time.
If phone don't get alive in 10 Minutes Repeat Step-III again.
You may not able to see but Your phone will update and automatically reboot into the Factory State. Cheers !!!
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Explaining Last Step:
We used simple logic in last procedure/ Its nothing but updating using Recovery Mode. Always remember Custom Recovery of Micromax A56/57 has following options: (May be diferent for other devics)
As the default curser in recovery UI remains on Option-1 and we needed to choose Option-2.
Hence to select "Apply update for sdcard" we pressed 'Vol(-)'ONCE and then to Confirm and execute that option Tapped 'POWER' button TWICE.
Hope this Guide helped you or ...will Help you to help others !!! ​

One quick question...
What if my device detected in fastboot but not in adb devices?
How to enter recovery or solve my softbricked issue?

RmatriX1218 said:
One quick question...
What if my device detected in fastboot but not in adb devices?
How to enter recovery or solve my softbricked issue?
Click to expand...
Click to collapse
bro if your volume + key is not working so how can u say that your device is soft bricked...
i think you should repair your volume keys and than try to move to recovery...
& one more thing without installing all drivers/thing u will not be able to access fastboot mode.....

Hey!!
Please please help me!!
I have MICROMAX a54 ninja 3.5.my mobile stuck in bootloop and soft bricked!!
When I turn on my devices it stuck in logo ninja 3.5.
I also try to go in recovery mode by pressing volume up+home key+lock key!
But it doesn't enter in recovery mod!!
Now what am I do??
Please please help me.
Thank you in advance..

I think for going in recovery:-
1. Press and hold power button.
2. While holding power key, press and hold both volume keys, (vol+ & vol-)
3. When mmx logo comes it will display a message vol(+) for recovery and vol(-) for fast boot then again press vol(+) for once,
And now your in recovery

I lost my recovery.
And I can't go into recovery mod!!
Please help me
Sent from my YU5010 using XDA Free mobile app

What do u mean by, lost your recovery???

I am not able to go to recovery!!
When I m try to gobto recovery mod it doesn't happen only logo ninja 3.5 is there
Sent from my YU5010 using XDA Free mobile app

Ok ok just try flashing your official rom
---------- Post added at 10:35 AM ---------- Previous post was at 10:17 AM ----------
Aakash mehta said:
I am not able to go to recovery!!
When I m try to gobto recovery mod it doesn't happen only logo ninja 3.5 is there
Sent from my YU5010 using XDA Free mobile app
Click to expand...
Click to collapse
Just download your official rom, Your device driver for pc, and install the rom to your device using "sp flash tool"

Please give me steps and link of above method!!!
Thank you for help me
Sent from my YU5010 using XDA Free mobile app

Aakash mehta said:
Please give me steps and link of above method!!!
Thank you for help me
Sent from my YU5010 using XDA Free mobile app
Click to expand...
Click to collapse
1.First download your stock recovery for your mmx a54 from here http://d-h.st/D7G
2. Now download sp flash tool from here https://drive.google.com/file/d/0B9S_ERLSMngHVE9Qc25ObGU1UU0/edit?pli=1 install it to your pc.
3. Download drivers for a54 from here singledrivers.blogspot.in/2013/12/micromax-ninja-a54-usb-driver-for.html?m=1 install the driver to your pc.
4. Download your phone stock rom from here http://d-h.st/fg2 place it in your external sd card(mmc) of your device.
5. Download scatter file from here www.mediafire.com/view/rvz1c5tiifx7yck/MT6575_Android_scatter.txt
6. Now run sp flash tool in your pc, browse to the scatter file.txt, turn off your phone remove the battery and connect it through usb to your pc. (Connect the device without battery)
7. Now select the recovery tab in sp flash tool browse to the recovery.img file (Which we hv downloaded before). Now select the option download in sp flash tool it will Start flashing your stock recovery to the device, A green tick marked will be comes as the flashing complete, now remove your device from pc.
8. Now goto recovery by vol key combination.
9. Now select apply update from sd card and select the stock rom.zip file
10. When flashing done then, Wipe Cache Partition and factory data reset of your device.
Now just select reboot device now it will take around 10min to boot for the first time so wait. Hope this helps you

Thank you for giving me whole information!!
Sent from my YU5010 using XDA Free mobile app

Aakash mehta said:
Thank you for giving me whole information!!
Sent from my YU5010 using XDA Free mobile app
Click to expand...
Click to collapse
Don't say thanks my Buddy just press thanks button.

Hello
I tried sp tool flasher!!
I followed all steps which were given by you!!
BT although not any change in my mobile..
When I tick recovery and then browse recovery.img file and click download button but nothing had happened..
It didn't detect my mobile and didn't go for procedure!!
So now what am I do???
You helped me very much!!
Bu please further help me...
Sent from my YU5010 using XDA Free mobile app

Hv u installed driver properly, just trust me try different usb ports

Yeah i installed drivers properly!!!
Sent from my YU5010 using XDA Free mobile app

So your device is not recognizing by sp flash tool r8

I think so
Sent from my YU5010 using XDA Free mobile app

micromax a210
I have a problem with fastboot stuck on system erasing on adb fastboot mood also userdata and cache only flash recovery and boot img sp flash not working with this phone I do other mtk android with sp tool successfully what I do

What if the device is recongised in adb as : (device name) recovery, but can't actually boot into recovery (twrp) and thus when entering the command : adb reboot fastboot it can never actually boot into fastboot ?
Are there any adb commands that can do the trick or is it game over ?

[RECOVERIES & ROOT] Yureka custom recoveries & Root without Changing Stock Recovery

[RECOVERIES & ROOT] Yureka custom recoveries & Root without Changing Stock Recovery
Note : This tutorial is for YU Yureka based on CM11 (KK 4.4.4) 32bit architecture
and
do it on your own risk, I will not be responsible if you brick your phone
Here is the detailed guide and collection of stock and all custom recoveries for YU Yureka and detailed guide to Root YU Yureka without changing Stock Recovery
Requirements
1. YU Yureka (obviously) with USB Data cable
2. PC / Laptop (Having Windows installed at least Windows 7 or above)
3. Drivers (Windows Automatically detect and install the required drivers)
4. ADB & Fastboot binary package that can be downloaded from XDA 15 seconds ADB Installer v1.4.2']http://forum.xda-developers.com/showthread.php?t=2588979
5. Custom Recovery (Anyone in which you are interested CWM, PhiZ, TWRP)
6. Latest SuperSU.zip file to root your phone
Warning: This process may delete all data stored in internal storage so better backup all the files stored in internal storage.
Step One
Enable USB Debugging on your device you can just follow these steps:
Go to Settings> About phone and keep taping on build number at least 7 times or till it appears "You are a developer now",
Now again go to settings>developer option (only after the previous step it will be enabled)> check/select USB debugging.
Step Two
Unlock your bootloader to flash custom recovery and root.
Here is the process
1. Download the adb & fastboot binary package and install it.
2. Put your phone into FASTBOOT mode by following anyone from below methods :
Method 1 (easiest)
-------------------
a. Power down phone
b. Plug USB cable to your PC
c. Press and hold Vol Up button and plug other end of USB to your device, soon you will see the fastboot screen.
(or without plugging USB Cable, Press and Hold Power and Vol Up buttons simultaneously, until you see the screen
"FASTBOOT MODE"
Method 2
---------
a. While your phone is Power On, plug USB Data Cable with PC and Phone (USB Debuging must be Enable)
b. Open Command Prompt on your PC (with Administartor rights) and type the following command
adb -s 0x1ebf devices
You will get results something like that :
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
3a289c2 device
*Note : If you get "authorization message" then look on your mobile screen and authorize your PC and run the command again.
c. Now note down the device no. (for e.g. in above "3a289c2") and type the following command
adb -s 3a289c2 reboot bootloader
[*Note replace the device id with your id (here 3a289c2), that you got in last command]
Now your phone must be booted into fastboot mode. A screen with "Fastboot Mode" should be appear on your phone.
3. Device drivers will get installed by windows (please wait for the driver installation to complete)
4. After driver installation is done go to the folder where you have extracted the package
5. Now open elevated DOS command prompt (terminal) on your PC and go into the same folder where you saved the recovery file
(*Note : to start command prompt directly from desired folder, while holding the Shift Key Right Click on folder and select start "open command window here")
6. Type the following command to check if the device was detected in fastboot mode
fastboot -i 0x1ebf devices
you should get output like : 2a25d00 fastboot
if you don't get similar output it means that the drivers weren't correctly installed or the device wasn't connected properly
7. If the output is similar to above then run the following command:
fastboot -i 0x1ebf oem unlock
you should get output something like :
.....
OKAY [ 0.003s]
finished. total time: 0.004s
8. Now your bootloader is now unlocked.
*Note : if you want to re-lock your bootloader again (for warranty on any other reason), again boot into fastboot mode and this time type the following command and enter
fastboot -i 0x1ebf oem lock
Step Three
Boot your phone into recovery (temporarily or permanently) and root your phone
1. Download SuperSU.zip and put it on root of your internal or external SD card
2. To load custom recovery (CWM / TWRP / PhiZ) temporarily, now type this command in terminal :
fastboot -i 0x1ebf boot CWM_6.0.5.1_recovery-yu.img
*Note 1 : if you want to flash the custom recovery permanently then us the following command
fastboot -i 0x1ebf flash CWM_6.0.5.1_recovery-yu.img
*Note 2 : if your download custom recovery is named differently (here CWM_6.0.5.1_recovery-yu.img) then while writing the above commands you need to put the name of the recovery same as as your saved file name (anyone CWM / Phiz / TWRP)
3. Done ! You loaded custom recovery temporarily, if command used with "boot" hence to root your phone, proceed to next section (step 5).
or
If you flashed recovery permanently, using command with "flash" then boot your phone into recovery. To do so, you have Two options
i) type the following command and press enter : adb -s 3a289c2 reboot recovery
or
ii) power off your phone, after then press and hold "Vol up+ Vol down + Power" buttons simultaneously to boot into custom recovery.
Now to root your phone proceed with next section (step 5).
Root your phone
5. To gain root access, flash SuperSu.zip that is stored on your internal or external SD card (in step 1)
6. Choose reboot phone and enjoy rooted phone with stock or custom recovery !
Special Note 1
I didn't tested, but came to know that root doesn't effect OTA update on Yureka.
You can get OTA updates with root but after the OTA update is flashed you will loose root access. To keep it or to avoid this please go to System Settings -> Developer Options -> UNTICK -"Update CM Recovery" (update recovery while installing system updates)
Even though if someone want to go back to Stock recovery, then download the official stock recovery (link no. 6 above) and flash it using command in fastboot mode (second command in step 2 under head "STEP THREE")
Downloads
1. 15 seconds ADB Installer v1.4.2 http://forum.xda-developers.com/showthread.php?t=2588979
2. Super SU latest v2.46 http://download.chainfire.eu/696/SuperSU/UPDATE-SuperSU-v2.46.zip
3. CWM 6.0.5.1 https://s.basketbuild.com/devs/vishal_android_freak/yu/yureka
OR http://d-h.st/ElAe
4. PhilZTouch 6.59 based on CWM v6.0.5.1 http://www.androiddevs.net/downloads/
OR http://d-h.st/UqWK
5. TWRP 2.8.5.0 http://techerrata.com/browse/twrp2/tomato
OR https://www.androidfilehost.com/?fid=95916177934528156
OR http://d-h.st/5wDD
6. YU Yureka Official Stock Recovery http://d-h.st/tQ1k
Special Note 2
Without the vendor id, phone will not get detected in fastboot mode.
Like if you want to check fastboot type this :
fastboot -i 0x1ebf devices
therefore, always add "i -0x1ebf" after fastboot and then write your command

aabidhashmi said:
Here is is collection of all custom recoveries for YU Yureka and detailed guide to Root YU Yureka without changing Stock Recovery
Requirements
1. YU Yureka (obviously) with USB Data cable
2. PC / Laptop (Having Windows installed at least Windows 7 or above)
3. Drivers (Windows Automatically detect and install the required drivers)
4. ADB & Fastboot binary package that can be downloaded from XDA 15 seconds ADB Installer v1.4.2']http://forum.xda-developers.com/showthread.php?t=2588979
5. Custom Recovery (Anyone in which you are interested CWM, PhiZ, TWRP)
6. Latest SuperSU.zip file to root your phone
Warning: This process may delete all data stored in internal storage so better backup all the files stored in internal storage.
Step One
Enable USB Debugging on your device you can just follow these steps:
Go to Settings> About phone and keep taping on build number at least 7 times or till it appears "You are a developer now",
Now again go to settings>developer option (only after the previous step it will be enabled)> check/select USB debugging.
Step Two
Unlock your bootloader to flash custom recovery and root.
Here is the process
1. Download the adb & fastboot binary package and install it.
2. Power down phone
3. Plug USB cable to your PC
4. Press and hold Vol Up button and plug other end of USB to your device, soon you will see the fastboot screen.
(or without plugging USB Cable, Press and Hold Power and Vol Up buttons simultaneously, until you see the screen
"FASTBOOT MODE"
5. Device drivers will get installed by windows (please wait for the driver installation to complete)
6. After driver installation is done go to the folder where you have extracted the package
7. Now open elevated DOS command prompt (terminal) on your PC and go into the same folder where you saved the recovery file
* to start command prompt directly from desired folder, while holding the Shift Key Right Click on folder and select start "open command window here"
8. Type the following command to check if the device was detected in fastboot mode
fastboot -i 0x1ebf devices
you should get output like : 2a25d00 fastboot
if you don't get similar output it means that the drivers weren't correctly installed or the device wasn't connected properly
9. If the output is similar to above then run the following command:
fastboot -i 0x1ebf oem unlock
you should get output something like :
.....
OKAY [ 0.003s]
finished. total time: 0.004s
10. Now your bootloader is now unlocked.
Step Three
Root your phone without changing your stock recovery
1. Download SuperSU.zip and put it on root of your internal or external SD card
2. To load custom recovery (CWM / TWRP / PhiZ) temporarily, now type this command in terminal :
fastboot -i 0x1ebf boot recovery CWM_6.0.5.1_recovery-yu.img
*Note : if your download custom recovery is named differently (here CWM_6.0.5.1_recovery-yu.img) then while writing the above command you need to put the name of the recovery same as as your saved file name (anyone CWM / Phiz / TWRP)
Done ! You flashed custom recovery temporarily.
3. Now press and hold "Vol up+ Vol down + Power" buttons simultaneously to boot into custom recovery.
4. To gain root access flash SuperSu.zip that is stored on your internal or external SD card (in step 1)
5. Choose reboot phone and enjoy rooted phone without changing stock recovery !
Downloads
1. 15 seconds ADB Installer v1.4.2 http://forum.xda-developers.com/showthread.php?t=2588979
2. Super SU latest v2.46 http://download.chainfire.eu/696/SuperSU/UPDATE-SuperSU-v2.46.zip
3. CWM 6.0.5.1 https://s.basketbuild.com/devs/vishal_android_freak/yu/yureka
OR http://d-h.st/ElAe
4. PhilZTouch 6.59 based on CWM v6.0.5.1 http://www.androiddevs.net/downloads/
OR http://d-h.st/UqWK
5. TWRP 2.8.5.0 http://techerrata.com/browse/twrp2/tomato
OR https://www.androidfilehost.com/?fid=95916177934528156
OR http://d-h.st/5wDD
Special Note
Without the vendor id, phone will not get detected in fastboot mode.
Like if you want to check fastboot type this :
fastboot -i 0x1ebf devices
therefore, always add "i -0x1ebf" after fastboot and then write your command
Click to expand...
Click to collapse
Few errors noted:
1. You can't say flashing recovery when you are booting it.
2. In step 3 point 3 is not valid because when your command is to boot it will automatically boot into recovery you need not use combination keys.
3. Last point vender id is wrong !!!
Few suggestions:
1. It feels like you have not tested this by yourself
2. There is already a guide for "rooting without flashing recovery". Search before posting.
Regards
aashking

aashking said:
Few errors noted:
1. You can't say flashing recovery when you are booting it.
2. In step 3 point 3 is not valid because when your command is to boot it will automatically boot into recovery you need not use combination keys.
3. Last point vender id is wrong !!!
Few suggestions:
1. It feels like you have not tested this by yourself
2. There is already a guide for "rooting without flashing recovery". Search before posting.
Regards
aashking
Click to expand...
Click to collapse
Dear aaskking
Thanks to inform. Here is the corrections
1 & 2 - Tutorial updated with "boot" and "flash" commands separately.
3 + Vendor ID is correct nothing wrong in it.
4 - I already tested all those procedures and commands. I never post anything without testing.
5 - Yes, I also seen that available guide, but that is not so much detailed and also required files links are not provided.
Anyway, thanks for your suggestions.

aabidhashmi said:
Dear aaskking
Thanks to inform. Here is the corrections
1 & 2 - Tutorial updated with "boot" and "flash" commands separately.
3 + Vendor ID is correct nothing wrong in it.
4 - I already tested all those procedures and commands. I never post anything without testing.
5 - Yes, I also seen that available guide, but that is not so much detailed and also required files links are not provided.
Anyway, thanks for your suggestions.
Click to expand...
Click to collapse
EDIT : You can get OTA updates with root..
After the update is flashed you will loose root access ..
To keep it or to avoid this please write the following step
STEP) In Developer Option UNTICK -"Update CM Recovery".
That's it.. Cheers mate wonderful thread.. @aabidhashmi @aashking

arjunsingh1000 said:
EDIT : You can get OTA updates with root..
After the update is flashed you will loose root access ..
To keep it or to avoid this please write the following step
STEP) In Developer Option UNTICK -"Update CM Recovery".
That's it.. Cheers mate wonderful thread.. @aabidhashmi @aashking
Click to expand...
Click to collapse
Thanks Arjun Singh @arjunsingh1000 for suggestion and appreciation
Post updated ...

aabidhashmi said:
Thanks Arjun Singh @arjunsingh1000 for suggestion and appreciation
Post updated ...
Click to expand...
Click to collapse
Great mate cheers just checked and tried that ota updates are available and work.. On stock recovery... Locked bootloader and with root..
Achieved this by downgrading to the very first cm11 firmware and got then rooted it and locked the bootloader then I just booted it and got the incremental update .. Downloaded and flashed .. Works perfectly.. Root not lost due to the untick in dev options..

Thanks again Arjun Singh, for confirming OTA updates are working.
I am already on Stock ROM & recovery {rooted} and tried the same procedure {locked the bootloader}, but no updates for me.
Is updates are really there, or something wrong with me ?
Sent from my AO5510 using Tapatalk

I am simply unable to get the device listed in command prompt after fastboot mode is enabled. my phone has option to boot into fastboot mode in power options. i tried that option, i tried using command to boot into fastboot. But somehow, when phone is in fastboot mode, it does not get detected by fastboot application (even though windows installs drivers successfully).
I have tried 3 different laptops. All had same problem. No idea how to solve this.

aabidhashmi said:
Thanks again Arjun Singh, for confirming OTA updates are working.
I am already on Stock ROM & recovery {rooted} and tried the same procedure {locked the bootloader}, but no updates for me.
Is updates are really there, or something wrong with me ?
Sent from my AO5510 using Tapatalk
Click to expand...
Click to collapse
Well I guess you are on the latest build XN0PHQ I guess? Another beta update was made but not rolled out it is um XNPH08P I know its a little late but just in case you don't know..
---------- Post added at 05:30 PM ---------- Previous post was at 05:28 PM ----------
jitendragarg said:
I am simply unable to get the device listed in command prompt after fastboot mode is enabled. my phone has option to boot into fastboot mode in power options. i tried that option, i tried using command to boot into fastboot. But somehow, when phone is in fastboot mode, it does not get detected by fastboot application (even though windows installs drivers successfully).
I have tried 3 different laptops. All had same problem. No idea how to solve this.
Click to expand...
Click to collapse
Ahahahaah... I know just the way... Do not reboot via adb ...
Switch off your phone remove your battery and put it back in do not turn it on.. But connect your USB cable and at the same time hold the power up or maybe down button .. Voila your in fastboot which will get detected .. Don't forget to use the vendor id.

arjunsingh1000 said:
Ahahahaah... I know just the way... Do not reboot via adb ...
Switch off your phone remove your battery and put it back in do not turn it on.. But connect your USB cable and at the same time hold the power up or maybe down button .. Voila your in fastboot which will get detected .. Don't forget to use the vendor id.
Click to expand...
Click to collapse
I tried this method but phone does not get detected in fastboot mode at all. I have drivers installed for all different modes I connect my phone as. No luck at all.
Also, weird thing is, I have an option to directly go to fastboot mode from the power menu.

Jitendra Garg
Your driver's are not installed
As there is no special drivers setup, so connect your PC with Internet then plug your phone and let Windows install drivers automatically.
Sent from my AO5510 using Tapatalk

Total Nub's guide to rooting Qmobile Q Infinity & Micromax Canvas Inifinity

After failing some 1-click rooting methods, for the first time I tried to do it the hard way.
That turned out to be a pretty easy way thanks to some handy links to drivers and other files I found.
Infinity thanks to the thread I found platform-tools from and the website called "getdroidtips" for the Custom TWRP for the HS2.
NOTE: THIS GUIDE WILL WIPE YOUR DEVICE SO BE PREPARED
Standard warning: FOLLOW THIS GUIDE AT YOUR OWN RISK. REMEMBER, AS PER MY NAME I AM A TOTAL NUB. I DO NOT TAKE RESPONSIBILITY FOR YOUR PHONE MALFUNCTIONING, BRICKING, BLOWING UP OR DROWNING IN COOKING OIL (rip my Elephone S7)
Pastebin code for missing links: F2RGqM1A
1) Preparation
Download the latest Flashable.Zip from [ ]
Place SuperSu.zip in your sd card or internal storage
Enable Developer Options by going to Settings -> "About Phone" -> Click "Software Version" 7-8 times
Go to developer Options in Settings
Enable OEM Unlocking
Enable USB Debugging
Shutdown your phone by holding the power button
Boot into fastboot by holding the Volume Up key + Power Button
Press Volume Down key to get into fastboot
2) On your Windows PC:
Download the file from [ ] and extract the platform-tools folder (I extract to "D:\Downloads" in this example)
Download the Custom TWRP from [ ] and place it inside the platform-tools folder
Connect your device to your computer
press Win+R, type cmd and press enter
2.1) (not always needed)
If your device won't connect or the steps below don't work, try updating drivers:
Connect your phone while it's in fastboot
open start menu, search and open Device Manager
check inside Portable Devices or Android Devices for your phone's name
or look for Android Bootloader Interface
if it's not there, it might be named something else, with an icon that has a yellow triangle inside it.
Right click it, Update Driver
> Browse my computer for driver software
> Let me pick from a list of available drivers on my computer
> select Android Bootloader Interface
to check if you are connected, type "fastboot devices" in cmd and you'll see a device code
3) Unlocking Bootloader
In cmd, enter the following commands:
Code:
D:
cd D:\Downloads\platform-tools
fastboot oem unlock-go
THIS STEP WILL WIPE YOUR DEVICE DATA
wait for restart
4) Booting into TWRP
Go to device Settings again and ensure OEM Unlocking and USB Debugging are still Enabled. Reboot into fastboot.
In cmd:
Code:
fastboot boot twrp-3.1.1-0-20171128-UNOFFICIAL-HS2.img
(In case above cmd line doesn't work, type "fastboot boot twrp" and press Tab)
5) Backing up your rom and data (Optional but recommended)
Inside TWRP, Click Backup, tick everything, select desired directory and swipe to backup.
Reboot and follow step 5 again if needed
6) Installing SuperSU with root privileges
Inside TWRP, Click Install and select SuperSU.zip
Swipe to install and reboot
Enjoy

Please port miui 9 or lineage os 15 for micromax canvas infinity hs2

NubbyMcNubNub said:
After failing some 1-click rooting methods, for the first time I tried to do it the hard way.
That turned out to be a pretty easy way thanks to some handy links to drivers and other files I found.
Infinity thanks to the thread I found platform-tools from and the website called "getdroidtips" for the Custom TWRP for the HS2.
NOTE: THIS GUIDE WILL WIPE YOUR DEVICE SO BE PREPARED
Standard warning: FOLLOW THIS GUIDE AT YOUR OWN RISK. REMEMBER, AS PER MY NAME I AM A TOTAL NUB. I DO NOT TAKE RESPONSIBILITY FOR YOUR PHONE MALFUNCTIONING, BRICKING, BLOWING UP OR DROWNING IN COOKING OIL (rip my Elephone S7)
Pastebin code for missing links: F2RGqM1A
1) Preparation
Download the latest Flashable.Zip from [ ]
Place SuperSu.zip in your sd card or internal storage
Enable Developer Options by going to Settings -> "About Phone" -> Click "Software Version" 7-8 times
Go to developer Options in Settings
Enable OEM Unlocking
Enable USB Debugging
Shutdown your phone by holding the power button
Boot into fastboot by holding the Volume Up key + Power Button
Press Volume Down key to get into fastboot
2) On your Windows PC:
Download the file from [ ] and extract the platform-tools folder (I extract to "D:\Downloads" in this example)
Download the Custom TWRP from [ ] and place it inside the platform-tools folder
Connect your device to your computer
press Win+R, type cmd and press enter
2.1) (not always needed)
If your device won't connect or the steps below don't work, try updating drivers:
Connect your phone while it's in fastboot
open start menu, search and open Device Manager
check inside Portable Devices or Android Devices for your phone's name
or look for Android Bootloader Interface
if it's not there, it might be named something else, with an icon that has a yellow triangle inside it.
Right click it, Update Driver
> Browse my computer for driver software
> Let me pick from a list of available drivers on my computer
> select Android Bootloader Interface
to check if you are connected, type "fastboot devices" in cmd and you'll see a device code
3) Unlocking Bootloader
In cmd, enter the following commands:
THIS STEP WILL WIPE YOUR DEVICE DATA
wait for restart
4) Booting into TWRP
Go to device Settings again and ensure OEM Unlocking and USB Debugging are still Enabled. Reboot into fastboot.
In cmd:
(In case above cmd line doesn't work, type "fastboot boot twrp" and press Tab)
5) Backing up your rom and data (Optional but recommended)
Inside TWRP, Click Backup, tick everything, select desired directory and swipe to backup.
Reboot and follow step 5 again if needed
6) Installing SuperSU with root privileges
Inside TWRP, Click Install and select SuperSU.zip
Swipe to install and reboot
Enjoy
Click to expand...
Click to collapse
Hi please help me, after flashing recovery my phone is on bootloop now, what do i do

Hem97 said:
Please port miui 9 or lineage os 15 for micromax canvas infinity hs2
Click to expand...
Click to collapse
I wish I could.
Sudhangshu said:
Hi please help me, after flashing recovery my phone is on bootloop now, what do i do
Click to expand...
Click to collapse
Did you try "flashboot boot twrp..." like in my guide or "flashboot flash twrp..."?
And which twrp image did you use?
In any case, if you can still get to the fastboot screen, try booting with the twrp image in Step 4 above (download links in the pastebin link)

NubbyMcNubNub said:
I wish I could.
Did you try "flashboot boot twrp..." like in my guide or "flashboot flash twrp..."?
And which twrp image did you use?
In any case, if you can still get to the fastboot screen, try booting with the twrp image in Step 4 above (download links in the pastebin link)
Click to expand...
Click to collapse
Hi, "flashboot boot twrp" wasnt working at all, so i tried "flashboot flash twrp" and all i have is a bootloop. So after flashing recoveru i booted my phone to fastboot and run the command, " flashboot boot recovery recovery.img" where recovery is the custom recovery image and it booted into recovery. Then there is one more step to do that allowed me to finally boot into my os. Its working fine and i still have twrp installed on my phone
---------- Post added at 06:53 PM ---------- Previous post was at 06:49 PM ----------
NubbyMcNubNub said:
I wish I could.
Did you try "flashboot boot twrp..." like in my guide or "flashboot flash twrp..."?
And which twrp image did you use?
In any case, if you can still get to the fastboot screen, try booting with the twrp image in Step 4 above (download links in the pastebin link)
Click to expand...
Click to collapse
Btw i dont find any pastebin links, im sorry im just a noob too..... Lol

Want custom rom for Qmobile Qinfinity
I want a custom rom for Qmobile Qinfinity.
Because its own rom lags and does not have full features. Please give the rom like lineage os,RR,Or Stock
Please Help?:good:

hi bro,recently i just buy a new phone which is micromax canvas infinity.i have rooted my phone successfully,but there are no custom roms available for this phone.can you develop any custom rom for this phone?that will be very helpful...

How To Guide Flash/Install TWRP on Realme GT Master Edition RMX3360 (Indian variant)

TWRP flashing guide for Realme GT Master edition RMX3360​
Flash at your own risk. You might LOSE all data on your phone.
( I will be not responsible for any damage to your device )​
Prerequisites :
Your Bootloader Should be Unlocked. Click Here For Instructions.
First Back up all of your data and files present on the phone because the phone might be erased from the process.
Install Minimal ADB and Fastboot tool from here: LINK
Get the A.09 vbmeta.img files for the Stock firmware. If you are using A.09 firmware then vbmeta.img is needed from A.09 firmware file. LINK
Get the TWRP image file and rename it to twrp.img . Unofficial TWRP Link
The process to disable verity/Verification (Important for Flashing TWRP Recovery):
Reboot the phone to fastboot (Vol Down + Power ).
Connect the phone to the computer using an USB data cable. Preferred to use the stock USB cable.
Search for Minimal adb and fastboot icon in the 'Windows search' and right-click for 'Locate file location' option.
Copy and Place that vbmeta.img in the Minimal adb and fastboot folder.
Hold Shift and Right-click in that directory and click on the options 'open cmd terminal there'.
Type fastboot --disable-verification --disable-verity flash vbmeta vbmeta.img in the cmd terminal.
Reboot the phone again to fastboot mode.
Follow the further process.
The process to install TWRP :
Reboot the phone to fastboot (Vol Down + Power ).
Connect the phone to the computer using an USB data cable. Preferred to use the stock USB cable.
Search for Minimal adb and fastboot icon in the 'Windows search' and right-click for 'Locate file location' option.
Copy and Place that twrp.img in the Minimal adb and fastboot folder.
Hold Shift and Right-click in that directory and click on the options 'open cmd terminal there'.
Type fastboot boot twrp.img in the cmd terminal.
The phone will boot in TWRP recovery and after that go to Advanced > Flash Current TWRP.
Done you have installed TWRP in your device.
TWRP flashed now Enjoy Flashing Custom files and ZIPS.​

pkm774 said:
TWRP flashing guide for Realme GT Master edition RMX3360​
Flash at your own risk. You might LOSE all data on your phone.
( I will be not responsible for any damage to your device )​
Prerequisites :
Your Bootloader Should be Unlocked. Click Here For Instructions.
First Back up all of your data and files present on the phone because the phone might be erased from the process.
Install Minimal ADB and Fastboot tool from here: LINK
Get the A.09 vbmeta.img files for the Stock firmware. If you are using A.09 firmware then vbmeta.img is needed from A.09 firmware file. LINK
Get the TWRP image file and rename it to twrp.img . Unofficial TWRP Link
The process to disable verity/Verification (Important for Flashing TWRP Recovery):
Reboot the phone to fastboot (Vol Down + Power ).
Connect the phone to the computer using an USB data cable. Preferred to use the stock USB cable.
Search for Minimal adb and fastboot icon in the 'Windows search' and right-click for 'Locate file location' option.
Copy and Place that vbmeta.img in the Minimal adb and fastboot folder.
Hold Shift and Right-click in that directory and click on the options 'open cmd terminal there'.
Type fastboot --disable-verification --disable-verity flash vbmeta vbmeta.img in the cmd terminal.
Reboot the phone again to fastboot mode.
Follow the further process.
The process to install TWRP :
Reboot the phone to fastboot (Vol Down + Power ).
Connect the phone to the computer using an USB data cable. Preferred to use the stock USB cable.
Search for Minimal adb and fastboot icon in the 'Windows search' and right-click for 'Locate file location' option.
Copy and Place that twrp.img in the Minimal adb and fastboot folder.
Hold Shift and Right-click in that directory and click on the options 'open cmd terminal there'.
Type fastboot boot twrp.img in the cmd terminal.
The phone will boot in TWRP recovery and after that go to Advanced > Flash Current TWRP.
Done you have installed TWRP in your device.
TWRP flashed now Enjoy Flashing Custom files and ZIPS.​
Click to expand...
Click to collapse
I am getting an error in the last step (Flash current TWRP): "failed to create ramdisk to flash". Any idea?

aprilfoo said:
I am getting an error in the last step (Flash current TWRP): "failed to create ramdisk to flash". Any idea?
Click to expand...
Click to collapse
Maybe more help for the issue i just mentioned above: in the temporary TWRP, the file ramdisk-files.txt contains a line for "mnt/vendor/persist", which does not exist, and thus the cpio command fails.

aprilfoo said:
Maybe more help for the issue i just mentioned above: in the temporary TWRP, the file ramdisk-files.txt contains a line for "mnt/vendor/persist", which does not exist, and thus the cpio command fails.
Click to expand...
Click to collapse
Screenshot can help better, try taking and sending it here.

{
"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"
}

hello sir is it compatible with rmx3363 ?

Okay Stupid question: Has Realme officially released bootloader unlock tool? I know they have released kernel and drivers.

xeltos said:
Okay Stupid question: Has Realme officially released bootloader unlock tool? I know they have released kernel and drivers.
Click to expand...
Click to collapse
well yes for some phones but deeptest somehow works for others if your lucky test them all and see ^^

pkm774 said:
TWRP flashing guide for Realme GT Master edition RMX3360​
Flash at your own risk. You might LOSE all data on your phone.
( I will be not responsible for any damage to your device )​
Prerequisites :
Your Bootloader Should be Unlocked. Click Here For Instructions.
First Back up all of your data and files present on the phone because the phone might be erased from the process.
Install Minimal ADB and Fastboot tool from here: LINK
Get the A.09 vbmeta.img files for the Stock firmware. If you are using A.09 firmware then vbmeta.img is needed from A.09 firmware file. LINK
Get the TWRP image file and rename it to twrp.img . Unofficial TWRP Link
The process to disable verity/Verification (Important for Flashing TWRP Recovery):
Reboot the phone to fastboot (Vol Down + Power ).
Connect the phone to the computer using an USB data cable. Preferred to use the stock USB cable.
Search for Minimal adb and fastboot icon in the 'Windows search' and right-click for 'Locate file location' option.
Copy and Place that vbmeta.img in the Minimal adb and fastboot folder.
Hold Shift and Right-click in that directory and click on the options 'open cmd terminal there'.
Type fastboot --disable-verification --disable-verity flash vbmeta vbmeta.img in the cmd terminal.
Reboot the phone again to fastboot mode.
Follow the further process.
The process to install TWRP :
Reboot the phone to fastboot (Vol Down + Power ).
Connect the phone to the computer using an USB data cable. Preferred to use the stock USB cable.
Search for Minimal adb and fastboot icon in the 'Windows search' and right-click for 'Locate file location' option.
Copy and Place that twrp.img in the Minimal adb and fastboot folder.
Hold Shift and Right-click in that directory and click on the options 'open cmd terminal there'.
Type fastboot boot twrp.img in the cmd terminal.
The phone will boot in TWRP recovery and after that go to Advanced > Flash Current TWRP.
Done you have installed TWRP in your device.
TWRP flashed now Enjoy Flashing Custom files and ZIPS.​
Click to expand...
Click to collapse
hello sir is it compatible with rmx3363 ?

is this method work for latest Android 12 for installing twrp ?

pankaj9pankaj9334 said:
is this method work for latest Android 12 for installing twrp ?
Click to expand...
Click to collapse
Currently, A12 Twrp is under development by twrp team. So you have to wait.

ites working with rmx3363 finally i got twrp to work ^^ thanks

NextB said:
ites working with rmx3363 finally i got twrp to work ^^ thanks
Click to expand...
Click to collapse
Allright, you are the best.
Without any modification of twrp.img ?
On Android 11 Firmware ?

guizzzmo said:
Allright, you are the best.
Without any modification of twrp.img ?
On Android 11 Firmware ?
Click to expand...
Click to collapse
without any

NextB said:
without any
Click to expand...
Click to collapse
I can boot this twrp with fastboot boot twrp.img
but if i try to do Advanced > Flash Current TWRP
i have the same error than as @aprilfoo above

guizzzmo said:
I can boot this twrp with fastboot boot twrp.img
but if i try to do Advanced > Flash Current TWRP
i have the same error than as @aprilfoo above
Click to expand...
Click to collapse
Actually i found a workaround but i prefer not even to share it because of a bigger issue: the OP forgot to mention that: 'Installing Magisk is must if you are planning to press "Flash Current TWRP" when flashing alongside stock ROM'. I did not install Magisk and ended up with a completely dysfunctional phone and had to flash again the stock OS.
So i suggest to wait a bit more (some ROMs are in release candidate in the Telegram group)

aprilfoo said:
Actually i found a workaround but i prefer not even to share it because of a bigger issue: the OP forgot to mention that: 'Installing Magisk is must if you are planning to press "Flash Current TWRP" when flashing alongside stock ROM'. I did not install Magisk and ended up with a completely dysfunctional phone and had to flash again the stock OS.
So i suggest to wait a bit more (some ROMs are in release candidate in the Telegram group)
Click to expand...
Click to collapse
ok thanks for the reply. wich telegram group?

guizzzmo said:
ok thanks for the reply. wich telegram group?
Click to expand...
Click to collapse
@realmegtmasterupdates - telegram channel publications statistics Realme GT Master | UPDATES
telegram channel publications statistics of Realme GT Master | UPDATES telegram channel. All about Realme GT Master - RMX3366 ROMs, Kernels, Guides, Mods, NEWS, everything. Stay up-to-date with us! Official Group: @RealmeGTMaster Photography : @RMGTMasterPhotography Gaming : @RMGTMasterGaming...
telemetr.io

Use This
https://www.getdroidtips.com/twrp-recovery-realme-gt-master-edition/

Oh i see the problem, it's because the new partition slot A/B.
Ok i have magisk installed on stock rom but i think i will waiting. I stay on UI 2.0 with full root, magisk, lsposed, safetynet, and no bugs