Fastboot-unbrick your device with 'no display' - Micromax A57 Ninja

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 ?

Related

TUT SDK and Fastboot commands

Hi together!
Since this is a topic where people ask regularly, I try to make a little TUT.
I hope it is helpful.
I am a noob myself, so please don't go on me
Please feel free to correct me if I am wrong or if I missed some important stuff.
What you need:
1.
SDK Tool (type in your browser: developer.android.com/sdk/index.html)
Once you are on that page, download the package and install it.
2.
after the install process has finished, you have to install some packages.
Important is the platform-tools package (there you find the most important commands)
3.
Locate the folder on the harddisk of your PC
4.a)
Push the Windows(Start) Buttom and type: cmd
This opens the command prompt
Now get into the root of the android folder (e.g. cd.. until you get into root of your harddisk)
(on my PC, it looks like this:
cd android
cd platform-tools)
4.b)
Just one thing to make it a little easier to come into the right folder:
Open the folder with the fastbootfiles in a window.
Go to command line and type cmd and the cmd.exe will be shown in the menu.
Drag & Drop the cmd.exe into the opened fastboot folder.
When you now open this cmd, it shows the right folder at the start and you can easily type the commands without navigation through folders.
credits go to Neo XL
5.
Your phone has to be in fastboot-USB mode and connected to PC in order to understand the commands
6.
Once you are in platform-tools folder, you can type commands
Most common commands are:
fastboot erase cache (sometimes helps if phone is in HTC bootloop)
fastboot flash boot (name of boot image / e.g. boot_1.2.3.img) (this is, like the name says, to flash a boot image)
fastboot flash recovery (name of recovery.img
fastboot oem lock ( to relock your phone, in case you have or want to flash a RUU)
fastboot flash unlocktoken Unlock_code.bin (to unlock again, if you already got the unlock key from HTCDev)
Flash firmware.zip using following terminal commands:
Please rename first downloaded .zip package to firmware.zip
fastboot oem rebootRUU
fastboot flash zip firmware.zip
This is almost obsolete, since we have the new Recovery 5.8.3.1 with Mount USB, but it is still good to know
to push ROM to SD card, if you were running superwipe without copying the rom file onto sd
1. You need recovery.img in your fastboot directory
2. Go into bootloader and connect phone
3. Then use: "fastboot boot recovery.img" (thus booting your image from pc and not the installed recovery).
4. When in recovery, you can use the adb commands.
5. You can try with "adb devices" which should show you serial of phone.
6. command: adb push rom_rom.zip /sdcard
credits to broncogr for finding that adb works if you use fastboot boot command and to Jotha for helping me out!
Or try following:
Copy rom to your adb-directory on PC
Switch OFF phone
Connect phone to PC
Wait until you hear the "USB-Connect"-sound on PC
Go into command window in adb-directory
Type "adb push rom.zip /sdcard/"
(where rom.zip is name of rom-file)
pushing is rather slow so it will take a while. Eventually you get an "OK". Then you can go into recovery and flash it.
Credits go to Jotha
Updated link
[TOOL][27/04] Automated Fastboot Commands For HTC One X continued
http://forum.xda-developers.com/showthread.php?t=1634786
credits go to TeAm Hex
For now, this is what I can think of, for sure there are many more commands, but hopefully we don't need them, but like I said, feel free and put them in here
I hope this will help some noobs, like myself!
If this helped you, please push THANKS
thanks! this will stop us noob's, spamming up dev's thread's.
Thanks for you efforts
First time with real android phone, this is good!
Thanks mate
Sent from my HTC One X using xda premium
Can you add the command to push the custom rom to sdcard without mout USB via CWM ?
Just one thing to make it a little easyer to come into the right folder:
Open the folder with the fastbootfiles in a window.
Go to command line and type cmd and the cmd.exe will be shown in the menu. Drag & Drop the cmd.exe into the opened fastboot folder.
When you now open this cmd, it shows the right folder at the start and you can easyly type the commands without navigation through folders.
incident said:
Can you add the command to push the custom rom to sdcard without mout USB via CWM ?
Click to expand...
Click to collapse
Would be great, if this is possible! But as far as I know, it not possible.
Edit:
It is possible now! Updated post!
Sent from my HTC One X using XDA
hello I have problem with loading boot.img in fastboot
sdk is open, phone is conncted to comp on fastboot usb mode , image is on disc c in folder fastboot and still recive this info
c:\fastboot>fastboot flash boot boot.img
'fastboot' is not recognized as an internal or external command,
operable program or batch file.
c:\fastboot>
pls help me with that
ok I fix this, that was problem with missing fastboot.exe and was no connection betwen phone and computer
this link helps fix that
http://dottech.org/tipsntricks/21534/how-to-install-adb-and-fastboot-on-your-windows-computer-for-use-with-your-android-phone/
You have to copy the Boot.img into the folder, where fastboot-, adb commands are situated (c:/andoid/platform-tools)
Then Open cmd. Go to platform-tools folder and from there it should work.
Sent from my HTC One X using XDA
Thanx man, but is fixed now, I did this by follow the instr. in page from my last post, and goes perfect. I just flashed new rom with 1.8 base and iam now on the bright side of life.
PS sorry for my english
@OP, last time I tried fastboot boot command it gave me device not found message(no problem when fastboot flash). What's the correct approach to make it work? I recently updated to 1.28 and I want to stay in stock for the mean time.
Sent either from my Arc or One X using xda premium
You can add the adb and fastboot directory path to the environment path in windows settings. You can then use adb and fastboot outside of the platform tools directory, but still in command prompt of course
Sent from my HTC One X using Tapatalk 2
I'm following your tutorial to the letter but whenever i use fastboot boot recovery.img it refuses to go into recovery. But i can boot into recovery manually and when i do there still isnt any adb devices connected.
Stuart.upton666 said:
I'm following your tutorial to the letter but whenever i use fastboot boot recovery.img it refuses to go into recovery. But i can boot into recovery manually and when i do there still isnt any adb devices connected.
Click to expand...
Click to collapse
3. Then use: "fastboot boot recovery.img" (thus booting your image from pc and not the installed recovery).
4. When in recovery, you can use the adb commands.
5. You can try with "adb devices" which should show you serial of phone.
6. command: adb push rom_rom.zip /sdcard
In point 3, it is not supposed to boot into recovery. Its for booting your recovery.img (e.g. recovery-clockwork-touch-5.8.3.1-endeavoru.img ) from PC. After this step you will automatically boot into Recovery. From there you can use adb commands.
Did you try "adb devices"?
I tried it myself and it works!
This guide is great... Thanks!
Sent from my HTC One X using xda premium
tonyhagger said:
This guide is great... Thanks!
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Thank you, Sir! Some kind of feedback is always appreciated !
Hi about Push to SDCARD command
My questions in Blue
to push ROM to SD card, if you were running superwipe without copying the rom file onto sd
1. You need recovery.img in your fastboot directory - Should i use signed recovery ?
2. Go into bootloader and connect phone
3. Then use: "fastboot boot recovery.img" (thus booting your image from pc and not the installed recovery).
4. When in recovery, you can use the adb commands.
5. You can try with "adb devices" which should show you serial of phone.
6. command: adb push rom_rom.zip /sdcard
incident said:
My questions in Blue
to push ROM to SD card, if you were running superwipe without copying the rom file onto sd
1. You need recovery.img in your fastboot directory - Should i use signed recovery ?
2. Go into bootloader and connect phone
3. Then use: "fastboot boot recovery.img" (thus booting your image from pc and not the installed recovery).
4. When in recovery, you can use the adb commands.
5. You can try with "adb devices" which should show you serial of phone.
6. command: adb push rom_rom.zip /sdcard
Click to expand...
Click to collapse
Take the newest CWM recovery.
Sent from my Desire HD using XDA
incident said:
My questions in Blue
to push ROM to SD card, if you were running superwipe without copying the rom file onto sd
1. You need recovery.img in your fastboot directory - Should i use signed recovery ?
2. Go into bootloader and connect phone
3. Then use: "fastboot boot recovery.img" (thus booting your image from pc and not the installed recovery).
4. When in recovery, you can use the adb commands.
5. You can try with "adb devices" which should show you serial of phone.
6. command: adb push rom_rom.zip /sdcard
Click to expand...
Click to collapse
Asking about number 6,since after push rom into sd card using adb command. How long will it takes rom to place in sd card? My adb command just stuck after push rom without inform is it done or not.
And where did the push file goes? Seems I can't find it in CWM. I'm using latest cwm, but no zip file found in my sd card.
TEKONG84 said:
[/COLOR]
Asking about number 6,since after push rom into sd card using adb command. How long will it takes rom to place in sd card? My adb command just stuck after push rom without inform is it done or not.
And where did the push file goes? Seems I can't find it in CWM. I'm using latest cwm, but no zip file found in my sd card.
Click to expand...
Click to collapse
Rom should be on root of Sd.
If this is not working, you can try to use the command while phone is powered off. I am not a dev, but I read something like that:
"Switch off your phone, connect to pc, wait until it is detected by windows and use: adb push nameofrom.zip /sdcard/" thats what Jotha told someone on ARHD Thread.
Try that and tell us if it worked.
Sent from my Desire HD using XDA

[Q] Arc S, fastboot stuck at " sending 'boot' "

Hi,
I have wanted to try CM10 for some time, and unlocked my Arc S for the first time today. I followed the guides at freexperiaproject, so it seems that I was able to unlock the bootloader successfully. After it was unlocked I rebooted and all my user data was reset (as expected).
I downloaded "FXP150-cm-10-20121208-UNOFFICIAL-anzu" from rapidgator and "gapps-jb-20121011-signed" wich I found at the cyanogenmod wiki. I put both the zip files in the root of my SD card. When I try running "fastboot flash boot boot.img" it says "sending 'boot' <5616 KB>...", but nothing more happens. I let it stay for several minutes and I have to push Control+C to abort it. I also extracted "boot.img" to the platform-tools folder under android-sdk.
In the SDK Manager I have installed "Android SDK Tools", "Android SDK Platform-tools" and "Google USB Driver".
Am I doing something wrong? Is there anything more I should do before running fastboot? Sorry if I have missed a basic step here.
Espen
First, copy the file .img to the fastboot folder, if the file system.img means you have to run the command with the command: fastboot> fastboot flash system system.img, if the file userdata.img means that the command should be fastboot> fastboot flash userdata userdata.img .if the file xxxxboot.img mean form the command fastboot> fastboot flash boot xxxxboot.img
Iam using google translate.so,I hope I helped you and I hope you understand
Sent from my LT18i
The file from the zip file is called "boot.img". I have copied it to the fastboot folder, and I am running "fastboot flash boot boot.img", as the "how to-" says.
Reinstall drivers
Sent from my LT15i using xda premium
espenta said:
Hi,
I have wanted to try CM10 for some time, and unlocked my Arc S for the first time today. I followed the guides at freexperiaproject, so it seems that I was able to unlock the bootloader successfully. After it was unlocked I rebooted and all my user data was reset (as expected).
I downloaded "FXP150-cm-10-20121208-UNOFFICIAL-anzu" from rapidgator and "gapps-jb-20121011-signed" wich I found at the cyanogenmod wiki. I put both the zip files in the root of my SD card. When I try running "fastboot flash boot boot.img" it says "sending 'boot' <5616 KB>...", but nothing more happens. I let it stay for several minutes and I have to push Control+C to abort it. I also extracted "boot.img" to the platform-tools folder under android-sdk.
In the SDK Manager I have installed "Android SDK Tools", "Android SDK Platform-tools" and "Google USB Driver".
Am I doing something wrong? Is there anything more I should do before running fastboot? Sorry if I have missed a basic step here.
Espen
Click to expand...
Click to collapse
did you make the phone enter fastboot mode?
you should run "fastboot devices" to see.
Thanks for the replies!
I tried on a different computer this morning, and here it worked immediately. Not sure what was wrong on the other one, because I installed the same SDK packages and USB driver. Installing ROM at the moment.
[Edit]: Everything seems to be working fine. Very happy with CM10 at the moment
dewa999 said:
First, copy the file .img to the fastboot folder, if the file system.img means you have to run the command with the command: fastboot> fastboot flash system system.img, if the file userdata.img means that the command should be fastboot> fastboot flash userdata userdata.img .if the file xxxxboot.img mean form the command fastboot> fastboot flash boot xxxxboot.img
Iam using google translate.so,I hope I helped you and I hope you understand
Sent from my LT18i
Click to expand...
Click to collapse
I just tried to install cm 10 on Arc S mobile...
It's bootloader is unlocked & rooted...
but when I try to connect it in flashboot mode & In flashtool Press "Reboot into fastboot mode (via ADB) ,
It show error that "This action needs a connected device in ADB mode"
what I have to do to flash boot.img ?
I attached 2 screenshots of connecting & error....
device is connected in flashmode , I also attached blue noti. LED pic which on when connect...
How I connect device & flash boot.img ???
Can I flash that kernel directly by clicking "select kernel to flash" ?
& Why it is showing ADB error when I click "reboot into fastboot mode (via ADB) ??
In advance thank you...
Tech-G.ONE said:
I just tried to install cm 10 on Arc S mobile...
It's bootloader is unlocked & rooted...
but when I try to connect it in flashboot mode & In flashtool Press "Reboot into fastboot mode (via ADB) ,
It show error that "This action needs a connected device in ADB mode"
what I have to do to flash boot.img ?
I attached 2 screenshots of connecting & error....
device is connected in flashmode , I also attached blue noti. LED pic which on when connect...
How I connect device & flash boot.img ???
Can I flash that kernel directly by clicking "select kernel to flash" ?
& Why it is showing ADB error when I click "reboot into fastboot mode (via ADB) ??
In advance thank you...
Click to expand...
Click to collapse
You already asked for help in another topic, why here again?
Someguyfromhell said:
You already asked for help in another topic, why here again?
Click to expand...
Click to collapse
sorry bro....
But my main question is remain....
Why It is showing ADB error... I tried on two laptops, but result is same...
so I thought any one know the exact reason behind it.
ok I will try to flash kernel directly....
Tech-G.ONE said:
sorry bro....
But my main question is remain....
Why It is showing ADB error... I tried on two laptops, but result is same...
so I thought any one know the exact reason behind it.
ok I will try to flash kernel directly....
Click to expand...
Click to collapse
i dont like flashing kernel by flashtool, as far i done several 2011 devices the best method allways was over adb:good: & it pretty easy.
download android sdk & open the exe. leave all like it is (only may make sure google usb drivers are checked) & press on install.
after install place the boot.img here: ...\sdk\platform-tools
2. connect device into fastboot mode (blue led)
3.click in a empty space in the folder. now HOLD SHIFT & right click, choose ''open command line window here'' (<-- or sth like that sorry my setup is german)
4. enter 'fastboot devices' --> your device should be recognized as a bunch of numbers.
5. flash kernel by entering ''fastboot flash boot boot.img'' it tells you all done.
6. ''fastboot reboot''
7. enjoy new kernel

[Q] How to restore back to factory settings after using towel root

I have rooted my device using towel root which doesn't unlock the boot loader. I then used the twrp manager to install custom recovery. I am wondering how to restore everything back to factory as all the tutorials I have seen so far require an unlocked boot loader. Any help will be appreciated, thank you.
Flash a stock r for your phone
swagg blasted from TMO LG G3
jailbreakkid23 said:
Flash a stock r for your phone
swagg blasted from TMO LG G3
Click to expand...
Click to collapse
If I download a stock image from google and flash it from my nexus 7 using twrp will everything be restored to factory settings?
If the boot loader is locked does that mean I can just do a normal factory reset on the device and it will remove the recovery and root?
fastboot
Jordydaman said:
If the boot loader is locked does that mean I can just do a normal factory reset on the device and it will remove the recovery and root?
Click to expand...
Click to collapse
you have to install stock ROM by adb mode using fastboot command
you can't flash stock ROM via custom recovery.
@SidDev said:
you have to install stock ROM by adb mode using fastboot command
you can't flash stock ROM via custom recovery.
Click to expand...
Click to collapse
Would you mind finding a link for me ? I have never encountered this before as I have always unlocked the bootloader to root but this time I used towel root which was different as explained above.
Doesn't the boot loader have to be unlocked to flash a ROM via adb?
try this and press thanks
Jordydaman said:
Doesn't the boot loader have to be unlocked to flash a ROM via adb?
Click to expand...
Click to collapse
nope,
Step 1: Download the ADB/Fastboot files and the
USB drivers for Windows based PC first. The the
latest factory image for your Nexus device can be
downloaded directly from Google’s website .
ADB/Fastboot – Mac , Windows
USB drivers for Windows
Extract the contents of the ADB/Fastboot ZIP file
inside a new folder called ‘google’ on your desktop.
Extract and transfer the contents of the factory
image inside this folder as well. The list of files will
include a ZIP file containing the codename of your
Android device, two files with “flash-all” names, and
a bootloader image file. All the extracted contents of
the factory image should be inside the same folder
as the ADB and Fastboot file, otherwise you will get
a file not found error.
Make sure to install the ADB drivers as well if you
are running a Windows based PC.
Step 2: Now, reboot your Nexus device in bootloader
mode. This is usually done by switching off the
device, and pressing the Volume down + Volume Up
+ Power button simultaneously. If that does not
work, try the Volume down + Power button
combination.
After the device has booted into bootloader mode,
connect it to your PC.
Step 3: Open a new Terminal or Command Prompt
window, and navigate to the ‘google’ folder that you
created in Step 1. Before we start flashing the
factory image, we need to make sure that your
Nexus device is being detected by the PC.
fastboot devices
If you are using a Mac, then you need to prefix a “./”
before every Fastboot command. So, the above
command will look something like this on a Mac -:
./fastboot devices
The above command should confirm if your device is
indeed being detected by your PC or not. If it is,
then proceed to the steps below. If not, repeat the
steps above again. Make sure that you have properly
installed the drivers and are inside the correct
folder.
If you are running Windows, copy-paste the following
command in the command prompt window -:
flash-all.bat
On a Mac, copy-paste the following command -:
./flash-all.sh
The script will then automatically flash the full
factory image on your Nexus device. Once the
factory image has been flashed, your device will
automatically reboot. Keep in mind that the first boot
might take some time so please be patient.
If the flash-all.sh script gives you a fastboot not
found error on your Mac, open up the file in Text Edit
and add a “./” before every fastboot command.
The flash-all script included in the factory image
might not work for all. It has always been pretty
unreliable and has only worked once for me in the
last 2 years. If you are in the same boat as me, you
will have to flash each partition manually on your
device. This is slightly cumbersome though.
The command to manually flash a partition via
fastboot is “fastboot flash partition filename.img”. In
the factory image that you extracted in Step 1, you
will notice there is another ZIP file. Extract the
contents of that ZIP file inside the ‘google’ folder.
Now, its time to manually flash the partitions to your
Nexus device. We will first begin with the bootloader.
fastboot flash bootloader filename.img
Then, we will flash all other partitions. They don’t
necessarily need to be in the same order as I have
listed them below. The names of the image files in
the factory image will clearly indicate the partition
they are intended for as well.
fastboot flash boot filename.img
fastboot flash radio filename.img
fastboot flash recovery filename.img
fastboot flash userdata filename.img
fastboot flash system filename.img
Thank you very much I will try this today.
I couldn't flash all and when I flashed the bootloader it came up with failed bootloader is locked?
Enter this command to unlock the bootloader:
fastboot oem unlock
After unlocking, you can run flash-all.bat (or run manual fastboot commands to flash).

[TUT][Normal and PDANET Method] YUREKA-UNLOACK BOATLOADER, FLASH RECOVERY, ROOT

YU(YUREKA) - UNLOCK BOOTLOADER, FLASHING CUSTOM RECOVERY, ROOTING (NORMAL AS WELL AS PDANET METHOD)​
EXPLORE UNLIMITED POSSIBLITIES BY ROOTING YOUR DEVICE
ROOTING DOESN'T VOID YOUR YUREKA's WARRENTY
INSTRUCTIONS FOR
[ 64-Bit ] OFFICIAL STOCK CM12s (LOLLIPOP)​METHOD - 1 (NORMAL)
Requirements :
Laptop or Desktop with windows OS
USB Data cable
Files Required:
adb.zip : DOWNLOAD HERE
SuperSU.zip : DOWNLOAD HERE
TWRP Recovery :DIRECT LINK ..............OFFICIAL POST
CMW Recovery : DIRECT LINK ..............OFFICIAL POST
Download adb.zip file and extract it in your PC path C:/ADB
now place CWM recovery : "cwm_recovery.img" [or] TWRP recovery : "twrp_recovery.img" in that ADB folder
WARNING:
-> Unlocking bootloader will erase all your data. So backup your data before unlocking bootloader
PROCEDURE :
-> Now copy SuperSu.zip in Root of the SDcard in your device
-> Now Turn off the device and connect mobile to PC using USB cable
-> Now at the top you can see RED led glowing. Once you observe it keep pressing the Volume up rocker button and your device will move to fastboot mode.
-> Now navigate to ADB folder c:/ADB
-> Now open adb terminal by "shift + right click" and select "open command prompt here"
Now follow these steps in adb terminal:
Code:
[SIZE="4"]fastboot -i 0x1ebf oem unlock[/SIZE]
this command will unlocks your bootloader.
NOTE: If U are facing issue like "waiting for device" when U type the command then please follow METHOD 2
Code:
[SIZE="4"]fastboot -i 0x1ebf flash recovery cwm_recovery.img[/SIZE]
this will flash cwm recovery.
[OR]​
Code:
[SIZE="4"]fastboot -i 0x1ebf flash twrp_recovery.img[/SIZE]
this will flash philz recovery.
Note : if you download any other custom recovery which is named differently just replace "cwm_recovery.img" to ur recovery name "your_recovery.img" without quotes in above command.
Code:
[SIZE="4"]fastboot -i 0x1ebf reboot[/SIZE]
this will reboot your device.
that's it now your bootloader as been unlocked and installed CWM or TWRP custom recovery
NOTE: In this stage i suggest you take full nandroid backup which is very very very useful in future and dont delete that backup ever.
i always suggest CWM recovery which works on both touch interface as well as device hard keys.
TO ROOT YOUR DEVICE
-> Place "SuperSu.zip" in your internal or external Sd card
-> reboot to recovery and select install zip from storage and browse to the folder where you have downloaded the SuperSu.zip
that's it now your device has been rooted
For those who are facing Device Detection issue on adb​METHOD - 2 (USING PDANET SOFTWARE)
.​Requirements :
Laptop or Desktop with windows OS
USB Data cable
Files Required:
db.zip : DOWNLOAD HERE
SuperSU.zip : DOWNLOAD HERE
TWRP Recovery :DIRECT LINK ..............OFFICIAL POST
CMW Recovery : DIRECT LINK ..............OFFICIAL POST
PdaNet mobile app : DOWNLOAD HERE
PdaNet PC application : DOWNLOAD HERE
Download adb.zip file and extract it in your PC path C:/ADB
now place CWM recovery : "cwm_recovery.img" [or] TWRP recovery : "twrp_recovery.img" in that ADB folder
WARNING:
-> Unlocking bootloader will erase all your data. So backup your data before unlocking bootloader
PROCEDURE :
-> Download and install PdaNet mobile app : https://play.google.com/store/apps/details?id=com.pdanet
-> enable usb debugging in setting -> Developer options -> Mark ADB debugging and USB debugging
-> Install PdaNet software in PC : http://pdanet.co/a/
-> when PdaNet software in PC requested to connect mobile Keep mobile TURN ON and connect it using USB cable.
-> it will install the device drivers automatically, if already installed select reinstall option
-> Now unplug the device from USB cable
-> Now reboot PC as well as mobile
-> now keep mobile TURN ON and connect mobile to PC using USB cable
-> Now navigate to ADB folder c:/ADB
-> Now open adb terminal by "shift + right click" and select "open command prompt here"
Now follow these steps in adb terminal:
Code:
[SIZE="4"]adb devices[/SIZE]
if device is displaying in command window then type next command otherwise try reinstalling PdaNet in PC and mobile as well.
Code:
[SIZE="4"]adb reboot-bootloader[/SIZE]
then the devices goes to fastboot mode which is showing in the screen.
Code:
[SIZE="4"]fastboot -i 0x1ebf oem unlock[/SIZE]
this command will unlocks your bootloader.
Code:
[SIZE="4"]fastboot -i 0x1ebf flash recovery cwm_recovery.img[/SIZE]
this will flash cwm recovery.
[OR]​
Code:
[SIZE="4"]fastboot -i 0x1ebf flash twrp_recovery.img[/SIZE]
this will flash TWRP recovery.
Note : if you download any other custom recovery which is named differently just replace "cwm_recovery.img" to ur recovery name "your_recovery.img" without quotes in above command.
Code:
[SIZE="4"]fastboot -i 0x1ebf reboot[/SIZE]
this will reboot your device.
that's it now your bootloader as been unlocked and installed CWM or TWRP custom recovery
NOTE: In this stage i suggest you take full nandroid backup which is very very very useful in future and dont delete that backup ever.
i always suggest CWM recovery because which works on both touch interface as well as device hard keys
TO ROOT YOUR DEVICE
-> Place "SuperSU.zip" in your internal or external Sd card
->reboot to recovery and select install zip from storage and browse to the folder where you have downloaded the superuser.zip
that's it now your device has been rooted
INSTRUCTIONS FOR
[ 32 Bit ] OFFICIAL STOCK CM11s (KITKAT)​METHOD - 1 (NORMAL)
Requirements :
Laptop or Desktop with windows OS
USB Data cable
Files Required:
ADB.zip : DOWNLOAD HERE
Philz Recovery : DOWNLOAD HERE
SuperSU :DOWNLOAD HERE
Download ADB zip file and extract it in your PC path C:/ADB
now place philz recovery : "recovery_yuphilz.img" in that ADB folder
WARNING:
-> Unlocking bootloader will erase all your data. So backup your data before unlocking bootloader
PROCEDURE :
-> keep mobile Turn off and connect mobile to PC using USB cable
-> Now at the top you can see RED led glowing. Once you observe it keep pressing the Volume up rocker button and your device will move to fastboot mode.
-> Now navigate to ADB folder c:/ADB
-> Now open adb terminal by "shift + right click" and select "open command prompt here"
Now follow these steps in adb terminal:
Code:
[SIZE="4"]fastboot -i 0x1ebf oem unlock[/SIZE]
this command will unlocks your bootloader.
NOTE: If U are facing issue like "waiting for device" when U type the command then please follow METHOD 2
Code:
[SIZE="4"]fastboot -i 0x1ebf flash recovery recovery_yuphilz.img[/SIZE]
[OR]​
Code:
[SIZE="4"]fastboot -i 0x1ebf boot recovery_yuphilz.img[/SIZE]
this will flash philz recovery.
Note : if you download any other custom recovery which is named differently just replace "recovery_yuphilz.img" to ur recovery name "your_recovery.img" without quotes in above command.
Code:
[SIZE="4"]fastboot -i 0x1ebf reboot[/SIZE]
this will reboot your device.
that's it now your bootloader as been unlocked and installed philz custom recovery
NOTE: In this stage i suggest you take full nandroid backup which is very very very useful in future and dont delete that backup ever.
i always suggest philz which works on both touch interface as well as device hard keys.
TO ROOT YOUR DEVICE
-> Place "UPDATE-SuperSU-v2.45.zip" in your internal or external Sd card
-> reboot to recovery and select install zip from storage and browse to the folder where you have downloaded the superuser.zip
that's it now your device has been rooted
For those who are facing Device Detection issue on adb​METHOD - 2 (USING PDANET SOFTWARE)
.​Requirements :
Laptop or Desktop with windows OS
USB Data cable
Files Required:
ADB.zip : DOWNLOAD HERE
Philz Recovery : DOWNLOAD HERE
SuperSU : DOWNLOAD HERE
PdaNet mobile app : DOWNLOAD HERE
PdaNet PC application : DOWNLOAD HERE
Download ADB zip file and extract it in your PC path C:/ADB
now place philz recovery : "recovery_yuphilz.img" in that folder
WARNING:
-> Unlocking bootloader will erase all your data. So backup your data before unlocking bootloader
PROCEDURE :
-> Download and install PdaNet mobile app : https://play.google.com/store/apps/details?id=com.pdanet
-> enable usb debugging in setting -> Developer options -> Mark ADB debugging and USB debugging
-> Install PdaNet software in PC : http://pdanet.co/a/
-> when PdaNet software in PC requested to connect mobile Keep mobile TURN ON and connect it using USB cable.
-> it will install the device drivers automatically, if already installed select reinstall option
-> Now unplug the device from USB cable
-> Now reboot PC as well as mobile
-> now keep mobile TURN ON and connect mobile to PC using USB cable
-> Now navigate to ADB folder c:/ADB
-> Now open adb terminal by "shift + right click" and select "open command prompt here"
Now follow these steps in adb terminal:
Code:
[SIZE="4"]adb devices[/SIZE]
if device is displaying in command window then type next command otherwise try reinstalling PdaNet in PC and mobile as well.
Code:
[SIZE="4"]adb reboot-bootloader[/SIZE]
then the devices goes to fastboot mode which is showing in the screen.
Code:
[SIZE="4"]fastboot -i 0x1ebf oem unlock[/SIZE]
this command will unlocks your bootloader.
Code:
[SIZE="4"]fastboot -i 0x1ebf flash recovery recovery_yuphilz.img[/SIZE]
[OR]​
Code:
[SIZE="4"]fastboot -i 0x1ebf boot recovery_yuphilz.img[/SIZE]
this will flash philz recovery.
Note : if you download any other custom recovery which is named differently just replace "recovery_yuphilz.img" to ur recovery name "your_recovery.img" without quotes in above command.
Code:
[SIZE="4"]fastboot -i 0x1ebf reboot[/SIZE]
this will reboot your device.
that's it now your bootloader as been unlocked and installed philz custom recovery
NOTE: In this stage i suggest you take full nandroid backup which is very very very useful in future and dont delete that backup ever.
i always suggest philz because which works on both touch interface as well as device hard keys
TO ROOT YOUR DEVICE
-> Place "UPDATE-SuperSU-v2.45.zip" in your internal or external Sd card
->reboot to recovery and select install zip from storage and browse to the folder where you have downloaded the superuser.zip
that's it now your device has been rooted
Credits:
RDS for [64-Bit Rooting original post]
PRATHAM for 64-Bit CWM Recovery
@Santhosh M for 32-bit Philz Recovery & 64-bit TWRP recovery
@vishal_android freak for [32-Bit Rooting original post]
@[SIZE="4"]TechnoTrons(me)[/SIZE] for making this tutorial noob friendly
Reserved
Sent from my YUREKA using XDA Free mobile app
@TechnoTrons nice and thank you..but its not ctrl+right click...its shift+right click....so pls change it...
btw win 8.1 x64 users need to disable signature verification and here tut link add it also
http://www.howtogeek.com/167723/how...8.1-so-that-you-can-install-unsigned-drivers/
ansebovi said:
@TechnoTrons nice and thank you..but its not ctrl+right click...its shift+right click....so pls change it...
btw win 8.1 x64 users need to disable signature verification and here tut link add it also
http://www.howtogeek.com/167723/how...8.1-so-that-you-can-install-unsigned-drivers/
Click to expand...
Click to collapse
Thank u
Now edited ......:thumbup:
Sent from my YUREKA using XDA Free mobile app
thnx alot.i was trying this for more than 2 hours.but your pda method worked.
TechnoTrons said:
YU(YUREKA) - UNLOCK BOOTLOADER, FLASHING CUSTOM RECOVERY, ROOTING (NORMAL AS WELL AS PDANET METHOD)​
EXPLORE UNLIMITED POSSIBLITIES BY ROOTING YOUR DEVICE
ROOTING DOESN'T VOID YOUR YUREKA's WARRENTY​
METHOD - 1 (NORMAL)​
Requirements :
Laptop or Desktop with windows OS
USB Data cable
Files Required:
ADB.zip : DOWNLOAD HERE
Philz Recovery : DOWNLOAD HERE
SuperSU :DOWNLOAD HERE
Download ADB zip file and extract it in your PC path C:/ADB
now place philz recovery : "recovery_yuphilz.img" in that ADB folder
WARNING:
-> Unlocking bootloader will erase all your data. So backup your data before unlocking bootloader
PROCEDURE :
-> keep mobile Turn off and connect mobile to PC using USB cable
-> Now at the top you can see RED led glowing. Once you observe it keep pressing the Volume up rocker button and your device will move to fastboot mode.
-> Now navigate to ADB folder c:/ADB
-> Now open adb terminal by "shift + right click" and select "open command prompt here"
Now follow these steps in adb terminal:
Code:
[SIZE="4"]fastboot -i 0x1ebf oem unlock[/SIZE]
this command will unlocks your bootloader.
NOTE: If U are facing issue like "waiting for device" when U type the command then please follow METHOD 2
Code:
[SIZE="4"]fastboot -i 0x1ebf flash recovery recovery_yuphilz.img[/SIZE]
this will flash philz recovery.
Note : if you download any other custom recovery which is named differently just replace "recovery_yuphilz.img" to ur recovery name "your_recovery.img" without quotes in above command.
Code:
[SIZE="4"]fastboot -i 0x1ebf reboot[/SIZE]
this will reboot your device.
that's it now your bootloader as been unlocked and installed philz custom recovery
NOTE: In this stage i suggest you take full nandroid backup which is very very very useful in future and dont delete that backup ever.
i always suggest philz which works on both touch interface as well as device hard keys.
TO ROOT YOUR DEVICE
-> Place "UPDATE-SuperSU-v2.45.zip" in your internal or external Sd card
-> reboot to recovery and select install zip from storage and browse to the folder where you have downloaded the superuser.zip
that's it now your device has been rooted
For those who are facing connection issue between your PC and mobile follow​METHOD - 2 (USING PDANET SOFTWARE)​
Requirements :
Laptop or Desktop with windows OS
USB Data cable
Files Required:
ADB.zip : DOWNLOAD HERE
Philz Recovery : DOWNLOAD HERE
SuperSU : DOWNLOAD HERE
PdaNet mobile app : DOWNLOAD HERE
PdaNet PC application : DOWNLOAD HERE
Download ADB zip file and extract it in your PC path C:/ADB
now place philz recovery : "recovery_yuphilz.img" in that folder
WARNING:
-> Unlocking bootloader will erase all your data. So backup your data before unlocking bootloader
PROCEDURE :
-> Download and install PdaNet mobile app : https://play.google.com/store/apps/details?id=com.pdanet
-> enable usb debugging in setting -> Developer options -> Mark ADB debugging and USB debugging
-> Install PdaNet software in PC : http://pdanet.co/a/
-> when PdaNet software in PC requested to connect mobile Keep mobile TURN ON and connect it using USB cable.
-> it will install the device drivers automatically, if already installed select reinstall option
-> Now unplug the device from USB cable
-> Now reboot PC as well as mobile
-> now keep mobile TURN ON and connect mobile to PC using USB cable
-> Now navigate to ADB folder c:/ADB
-> Now open adb terminal by "shift + right click" and select "open command prompt here"
Now follow these steps in adb terminal:
Code:
[SIZE="4"]adb devices[/SIZE]
if device is displaying in command window then type next command otherwise try reinstalling PdaNet in PC and mobile as well.
Code:
[SIZE="4"]adb reboot-bootloader[/SIZE]
then the devices goes to fastboot mode which is showing in the screen.
Code:
[SIZE="4"]fastboot -i 0x1ebf oem unlock[/SIZE]
this command will unlocks your bootloader.
Code:
[SIZE="4"]fastboot -i 0x1ebf flash recovery recovery_yuphilz.img[/SIZE]
this will flash philz recovery.
Note : if you download any other custom recovery which is named differently just replace "recovery_yuphilz.img" to ur recovery name "your_recovery.img" without quotes in above command.
Code:
[SIZE="4"]fastboot -i 0x1ebf reboot[/SIZE]
this will reboot your device.
that's it now your bootloader as been unlocked and installed philz custom recovery
NOTE: In this stage i suggest you take full nandroid backup which is very very very useful in future and dont delete that backup ever.
i always suggest philz because which works on both touch interface as well as device hard keys
TO ROOT YOUR DEVICE
-> Place "UPDATE-SuperSU-v2.45.zip" in your internal or external Sd card
->reboot to recovery and select install zip from storage and browse to the folder where you have downloaded the superuser.zip
that's it now your device has been rooted
Credits:
@vishal_android freak for his original post & superuser.zip
@Santhosh M for Philz Recovery
@[SIZE="4"]TechnoTrons(me)[/SIZE] for making this tutorial noob friendly
Click to expand...
Click to collapse
thnx alot.i was trying this for more than 2 hours.but your pda method worked
Thanks
Thanks the first method worked for me. But there is one problem everything is done successfully but I am not able to boot in Philz recovery by pressing vol up and down key with power key. It boots to stock recovery.
Then I used the command of fastboot to boot in philz recovery. It booted in that but it doesnt boots while pressing the vol up and down key with power key simultaneously. Any idea why its not booting?
Thanks
TechnoTrons said:
YU(YUREKA) - UNLOCK BOOTLOADER, FLASHING CUSTOM RECOVERY, ROOTING (NORMAL AS WELL AS PDANET METHOD)​
EXPLORE UNLIMITED POSSIBLITIES BY ROOTING YOUR DEVICE
ROOTING DOESN'T VOID YOUR YUREKA's WARRENTY​
METHOD - 1 (NORMAL)​
Requirements :
Laptop or Desktop with windows OS
USB Data cable
Files Required:
ADB.zip : DOWNLOAD HERE
Philz Recovery : DOWNLOAD HERE
SuperSU :DOWNLOAD HERE
Download ADB zip file and extract it in your PC path C:/ADB
now place philz recovery : "recovery_yuphilz.img" in that ADB folder
WARNING:
-> Unlocking bootloader will erase all your data. So backup your data before unlocking bootloader
PROCEDURE :
-> keep mobile Turn off and connect mobile to PC using USB cable
-> Now at the top you can see RED led glowing. Once you observe it keep pressing the Volume up rocker button and your device will move to fastboot mode.
-> Now navigate to ADB folder c:/ADB
-> Now open adb terminal by "shift + right click" and select "open command prompt here"
Now follow these steps in adb terminal:
Code:
[SIZE="4"]fastboot -i 0x1ebf oem unlock[/SIZE]
this command will unlocks your bootloader.
NOTE: If U are facing issue like "waiting for device" when U type the command then please follow METHOD 2
Code:
[SIZE="4"]fastboot -i 0x1ebf flash recovery recovery_yuphilz.img[/SIZE]
[OR]​
Code:
[SIZE="4"]fastboot -i 0x1ebf boot recovery_yuphilz.img[/SIZE]
this will flash philz recovery.
Note : if you download any other custom recovery which is named differently just replace "recovery_yuphilz.img" to ur recovery name "your_recovery.img" without quotes in above command.
Code:
[SIZE="4"]fastboot -i 0x1ebf reboot[/SIZE]
this will reboot your device.
that's it now your bootloader as been unlocked and installed philz custom recovery
NOTE: In this stage i suggest you take full nandroid backup which is very very very useful in future and dont delete that backup ever.
i always suggest philz which works on both touch interface as well as device hard keys.
TO ROOT YOUR DEVICE
-> Place "UPDATE-SuperSU-v2.45.zip" in your internal or external Sd card
-> reboot to recovery and select install zip from storage and browse to the folder where you have downloaded the superuser.zip
that's it now your device has been rooted
For those who are facing connection issue between your PC and mobile follow​METHOD - 2 (USING PDANET SOFTWARE)​
Requirements :
Laptop or Desktop with windows OS
USB Data cable
Files Required:
ADB.zip : DOWNLOAD HERE
Philz Recovery : DOWNLOAD HERE
SuperSU : DOWNLOAD HERE
PdaNet mobile app : DOWNLOAD HERE
PdaNet PC application : DOWNLOAD HERE
Download ADB zip file and extract it in your PC path C:/ADB
now place philz recovery : "recovery_yuphilz.img" in that folder
WARNING:
-> Unlocking bootloader will erase all your data. So backup your data before unlocking bootloader
PROCEDURE :
-> Download and install PdaNet mobile app : https://play.google.com/store/apps/details?id=com.pdanet
-> enable usb debugging in setting -> Developer options -> Mark ADB debugging and USB debugging
-> Install PdaNet software in PC : http://pdanet.co/a/
-> when PdaNet software in PC requested to connect mobile Keep mobile TURN ON and connect it using USB cable.
-> it will install the device drivers automatically, if already installed select reinstall option
-> Now unplug the device from USB cable
-> Now reboot PC as well as mobile
-> now keep mobile TURN ON and connect mobile to PC using USB cable
-> Now navigate to ADB folder c:/ADB
-> Now open adb terminal by "shift + right click" and select "open command prompt here"
Now follow these steps in adb terminal:
Code:
[SIZE="4"]adb devices[/SIZE]
if device is displaying in command window then type next command otherwise try reinstalling PdaNet in PC and mobile as well.
Code:
[SIZE="4"]adb reboot-bootloader[/SIZE]
then the devices goes to fastboot mode which is showing in the screen.
Code:
[SIZE="4"]fastboot -i 0x1ebf oem unlock[/SIZE]
this command will unlocks your bootloader.
Code:
[SIZE="4"]fastboot -i 0x1ebf flash recovery recovery_yuphilz.img[/SIZE]
[OR]​
Code:
[SIZE="4"]fastboot -i 0x1ebf boot recovery_yuphilz.img[/SIZE]
this will flash philz recovery.
Note : if you download any other custom recovery which is named differently just replace "recovery_yuphilz.img" to ur recovery name "your_recovery.img" without quotes in above command.
Code:
[SIZE="4"]fastboot -i 0x1ebf reboot[/SIZE]
this will reboot your device.
that's it now your bootloader as been unlocked and installed philz custom recovery
NOTE: In this stage i suggest you take full nandroid backup which is very very very useful in future and dont delete that backup ever.
i always suggest philz because which works on both touch interface as well as device hard keys
TO ROOT YOUR DEVICE
-> Place "UPDATE-SuperSU-v2.45.zip" in your internal or external Sd card
->reboot to recovery and select install zip from storage and browse to the folder where you have downloaded the superuser.zip
that's it now your device has been rooted
Credits:
@vishal_android freak for his original post & superuser.zip
@Santhosh M for Philz Recovery
@[SIZE="4"]TechnoTrons(me)[/SIZE] for making this tutorial noob friendly
Click to expand...
Click to collapse
Followed all steps as mentioned....
Bootloader was unlocked
but when i try to reboot into recovery it reboots into stock recovery...
after that i tried flashing the super su zip through the stock recovery it shows error while installing
"E:failed to verify whole-file signature
E:signature verification failed"
Installation aborted.
amardeep434 said:
Followed all steps as mentioned....
Bootloader was unlocked
but when i try to reboot into recovery it reboots into stock recovery...
after that i tried flashing the super su zip through the stock recovery it shows error while installing
"E:failed to verify whole-file signature
E:signature verification failed"
Installation aborted.
Click to expand...
Click to collapse
I think u want to root ur device after ota update r8
Even I faced the problem in flashing recovery after ota update
So follow these steps to root ur device
-Use this command to flash ur recovery
Code:
fastboot -i 0x1ebf boot recovery_yuphilz.img
-After that ur device automatically reboots into recovery
-now flash supersu zip
-now reboot ur phone
- install flashify from play store
-copy the recovery.IMG to ur phone memory
-flash recovery.img using flashify software
-now reboot that's it
Sent from my AO5510 using XDA Free mobile app
TechnoTrons said:
I think u want to root ur device after ota update r8
Even I faced the problem in flashing recovery after ota update
So follow these steps to root ur device
-Use this command to flash ur recovery
Code:
fastboot -i 0x1ebf boot recovery_yuphilz.img
-After that ur device automatically reboots into recovery
-now flash supersu zip
-now reboot ur phone
- install flashify from play store
-copy the recovery.IMG to ur phone memory
-flash recovery.img using flashify software
-now reboot that's it
Sent from my AO5510 using XDA Free mobile app
Click to expand...
Click to collapse
yes i did the ota update but
there wasnt any error regarding recovery ..but even after flashing the custom recovery it always booted into stock cm recovery..
the above error was in installing super su zip using stock cm recovery..
raman_ said:
Thanks the first method worked for me. But there is one problem everything is done successfully but I am not able to boot in Philz recovery by pressing vol up and down key with power key. It boots to stock recovery.
Then I used the command of fastboot to boot in philz recovery. It booted in that but it doesnt boots while pressing the vol up and down key with power key simultaneously. Any idea why its not booting?
Thanks
Click to expand...
Click to collapse
Even I faced same issue after ota update
Did u successfully rooted ur device
If rooted
Flash recovery.img once again using flashify app which is available in play store
This will solve ur problem
Sent from my AO5510 using XDA Free mobile app
amardeep434 said:
yes i did the ota update but
there wasnt any error regarding recovery ..but even after flashing the custom recovery it always booted into stock cm recovery..
the above error was in installing super su zip using stock cm recovery..
Click to expand...
Click to collapse
Yes it won't show any kind errors
But recoveries are not at all flashing after ota update using adb
So follow above steps
The above given code will redirect u to recovery only once
At that time flash the supersu.zip. so that device get rooted
After that use flashify app to flash custom recovery for using multiple times
Sent from my AO5510 using XDA Free mobile app
TechnoTrons said:
Even I faced same issue after ota update
Did u successfully rooted ur device
If rooted
Flash recovery.img once again using flashify app which is available in play store
This will solve ur problem
Sent from my AO5510 using XDA Free mobile app
Click to expand...
Click to collapse
Thank you so much brother!!
Everything worked perfectly now!!
TechnoTrons said:
Yes it won't show any kind errors
But recoveries are not at all flashing after ota update using adb
So follow above steps
The above given code will redirect u to recovery only once
At that time flash the supersu.zip. so that device get rooted
After that use flashify app to flash custom recovery for using multiple times
Sent from my AO5510 using XDA Free mobile app
Click to expand...
Click to collapse
Thanks bro but one more question do we have to flash everytime we have to boot into the custom recovery?
raman_ said:
Thanks bro but one more question do we have to flash everytime we have to boot into the custom recovery?
Click to expand...
Click to collapse
No don't need to flash recovery every time
Just flash the recovery after rooting using flashify app
Then onwards you don't need flash again and again
Sent from my AO5510 using XDA Free mobile app
OK thanks for the help. BTW any idea why battery is draining so quickly even after flashing Sudeep bros First kernel? I am on stock ROM and followed the procedure mentioned in his post.
Sent from my AO5510 using xda premium
raman_ said:
OK thanks for the help. BTW any idea why battery is draining so quickly even after flashing Sudeep bros First kernel? I am on stock ROM and followed the procedure mentioned in his post.
Sent from my AO5510 using xda premium
Click to expand...
Click to collapse
Even I'm using it
Not only drains battery but also heats like hell
So better u revert back to stock kernel
Sent from my AO5510 using XDA Free mobile app
Thanks OP! The second method worked for me. The first kept giving me the error "Device not found." I was on Win 10 x64.
have a question
Thanks dude i have done with the process using method 2 and i have a question will i get the OTA update as now my phone is rooted and boot-loader unlocked
zaro143 said:
Thanks dude i have done with the process using method 2 and i have a question will i get the OTA update as now my phone is rooted and boot-loader unlocked
Click to expand...
Click to collapse
U need stock recovery to update
Place the stock recovery in sd card and
Just flash the stock recovery using flashify app available in play store and update
That's it
Now you can update
Sent from my AO5510 using XDA Free mobile app
TechnoTrons said:
U need stock recovery to update
Place the stock recovery in sd card and
Just flash the stock recovery using flashify app available in play store and update
That's it
Now you can update
Sent from my AO5510 using XDA Free mobile app
Click to expand...
Click to collapse
Ok, thanks
1. so if i flash Stock recovery whether my root will get disturbed ?
2. Stock recovery download link i could not find in the forum
3. If i flash stock recovery whether i will get the OTA update from Cyanogen ?

[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

Categories

Resources