Database Info

[Recovery] official cwm 6.0.1.9 [update 11/16]

Removed all my Dropbox links because they disabled my account due to too much traffic, if you guys want them back please consider donating a buck or two for a Mediafire Pro account...​I didn't develop this, just getting the word out that's it's officially available for the Nexus 7. You can either install the "normal" version or touch version from ROM Manager
UPDATE 11/16 new version posted by Koush 6.0.1.9
CWM Regular
CWM Touch
Here is the CWM ZIP by osm0sis:
Touch 6.0.1.9
Regualr 6.0.1.9
You NEED an unlocked bootloader in order to flash this check this thread on how-to unlock/root etc Nexus 7 Toolkit
If you just want to apply an OTA update and you haven't got it, you can do so by booting into CWM without installing it or having root.
first download and save OTA files from OTA 4.1.1 files and save to your /sdcard
then use
./adb reboot bootloader
./fastboot boot recovery-clockwork-touch-6.0.1.9-grouper.img
select install zip from sdcard
toggle signature verification and make sure it's disabled
select the file you downloaded earlier and install
reboot and you will be updated
Click to expand...
Click to collapse
If you want to have CWM permantly installed, first make sure you have root...use Root Explorer or any other file manager with root access and go to /system and delete recovery-from-boot.p
now use
./adb reboot bootloader
./fastboot flash recovery recovery-clockwork-touch-6.0.1.9-grouper.img
./adb reboot
Click to expand...
Click to collapse
You now have CWM installed.
I'm not responsible if you brick your tablet, it blows up mid flash etc
Make sure you know how to use ADB and have the SDK installed, you need that in order to do all of the above steps
Also make sure you have the recovery files saved to /sdk/platform-tools and also fastboot.exe has to be there also
Any commands that start with ./ are for linux/osx...just remove those when using windows
Click to expand...
Click to collapse

If you already have CWM or another recovery installed and would like to replace it with 6.0.0.6 Touch, I have packaged this file as a flash able zip file.
Download the zip file from http://db.tt/t13uCIRV and flash in recovery. To test, go to advanced -> reboot recovery and CWM Touch 6.0.0.6 should load up.
** edit 7/21/12**
Here's the zip file for the new touch recovery 6.0.1.0 http://db.tt/pLDeKXEf
Feel free to mirror!
Sent from my Nexus 7 using xda app-developers app

Flashing when I get home thanks.
Sent from my Galaxy Nexus using xda app-developers app

I flashed this from rom manager and so far have not had any of the problems I have had in some of the interim CWM's like inability to delete back ups or mounting system.

hey dude it's 6.0.0.6 not 6.0.6

mrich137 said:
If you already have CWM or another recovery installed and would like to replace it with 6.0.0.6 Touch, I have packaged this file as a flash able zip file.
Download the zip file from http://db.tt/t13uCIRV and flash in recovery. To test, go to advanced -> reboot recovery and CWM Touch 6.0.0.6 should load up.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Shano56 said:
hey dude it's 6.0.0.6 not 6.0.6
Click to expand...
Click to collapse
oops, typo...thanks, I will fix it now

Same here. Flashed via CWM with no issues what so ever. Shocking how much faster backups are now!
Sent from my Nexus 7 using xda premium

I am still not able to access recovery from bootloader. Just makes me kinda nervous to soft brick my nexus 7 and not be able to get into recovery to restore.
Any known fix for this?
Thanks

BCD90 said:
I am still not able to access recovery from bootloader. Just makes me kinda nervous to soft brick my nexus 7 and not be able to get into recovery to restore.
Any known fix for this?
Thanks
Click to expand...
Click to collapse
It works as long as you're connected to a computer, so you can access recovery from bootloader you just need to be hooked to a computer.

I know right,,,almost seems like it is not doing it right but I have went back to a previous backup and it flashed fine!
JoeM01 said:
Same here. Flashed via CWM with no issues what so ever. Shocking how much faster backups are now!
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
---------- Post added at 05:27 PM ---------- Previous post was at 05:26 PM ----------
If you know how to use ADB you can always fastboot a recovery.img,,,,this thing is almost impossible to truly brick. IN order to get into fastboot just connect to your computer and run adb with these commands
adb reboot bootloader
once in fastboot mode write this
fastboot devices
that will tell you if your device is connected and reading in fastboot mode if it is you will see something like fastboot and some numbers next to it. If nothing you do not have the fastboot drivers installed.
then to fastboot flash a recovery.img write this
fastboot flash recovery r3-recovery-clockwork-touch-6.0.0.4-nexus7-modaco.img (or whatever recovery.img you are using or have in your tools folder of you SDK location).
and in order to get right into CWM if you cant boot write this
fastboot boot r3-recovery-clockwork-touch-6.0.0.4-nexus7-modaco.img
hope that helps
BCD90 said:
I am still not able to access recovery from bootloader. Just makes me kinda nervous to soft brick my nexus 7 and not be able to get into recovery to restore.
Any known fix for this?
Thanks
Click to expand...
Click to collapse

camblue said:
I know right,,,almost seems like it is not doing it right but I have went back to a previous backup and it flashed fine!
Click to expand...
Click to collapse
Flashed fine here also. Works without flaw so far.

BCD90 said:
I am still not able to access recovery from bootloader. Just makes me kinda nervous to soft brick my nexus 7 and not be able to get into recovery to restore.
Any known fix for this?
Thanks
Click to expand...
Click to collapse
Did you install the ota after you rooted and installed the recovery? I soft bricked too and I think that was the reason why. Something about the ota overwrote the recovery partition. Best thing to do is download ROM manager and click the first option to flash cwm. Then click the next button to boot into recovery. Then just flash the zip I posted to upgrade to touch.
**edit** just tried to boot into recovery from the boot loader and got stuck at the Google screen too. Holding all three buttons rebooted and started up as normal. Maybe the boot loader boot into recovery is pointing to a different partition for some reason?
Booting into recovery from ROM manager works though. That's how I've been getting in.
Sent from my Galaxy Nexus using xda app-developers app

thanks for the heads up

BCD90 said:
I am still not able to access recovery from bootloader. Just makes me kinda nervous to soft brick my nexus 7 and not be able to get into recovery to restore.
Any known fix for this?
Thanks
Click to expand...
Click to collapse
What did you try?

Can you adb boot into recovery from the bootloader?
Oh and you can't 'adb reboot' in fastboot just hit the power button.

yes and can do this while in fastboot (bootloader mode)
fastboot boot r3-recovery-clockwork-touch-6.0.0.4-nexus7-modaco.img (or whatever the name of your recovery.img is)
BennyJr said:
Can you adb boot into recovery from the bootloader?
Oh and you can't 'adb reboot' in fastboot just hit the power button.
Click to expand...
Click to collapse

camblue said:
yes and can do this while in fastboot (bootloader mode)
fastboot boot r3-recovery-clockwork-touch-6.0.0.4-nexus7-modaco.img (or whatever the name of your recovery.img is)
Click to expand...
Click to collapse
The thing is when im in bootloader mode i can not access adb. I have tried this but it will not let me.

BCD90 said:
The thing is when im in bootloader mode i can not access adb. I have tried this but it will not let me.
Click to expand...
Click to collapse
Bootloader = fastboot. Any adb commands wont work

BCD90 said:
The thing is when im in bootloader mode i can not access adb. I have tried this but it will not let me.
Click to expand...
Click to collapse
Which is correct. You won't be able to do adb commands in the bootloader. The command he asked you to try was a fastboot command, which should work
Sent from my Galaxy Nexus using xda app-developers app

Make sure the drivers are installed had this problem with windows 7 download the naked driver pack and follow the instructions
Sent from my Nexus 7 using xda premium

adb sideload update.zip and "device not found"

EDIT: made a typo the first few tries!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
please see post #2

i was making a mistake. the correct command line is
adb devices
adb reboot bootloader
adb sideload update.zip
in this last command line it says:
loading : 'update.zip'
error: device not found
what now? when i type adb devices it sees my phone before rebooting into bootloader. after i reboot into bootloader and i type adb devices it does not give me any result

cesar.maranhao said:
i was making a mistake. the correct command line is
adb devices
adb reboot bootloader
adb sideload update.zip
in this last command line it says:
loading : 'update.zip'
error: device not found
what now? when i type adb devices it sees my phone before rebooting into bootloader. after i reboot into bootloader and i type adb devices it does not give me any result
Click to expand...
Click to collapse
If you're booted in to the bootloader you need to use fastboot commands, fastboot devices. That still doesn't address your problem though. You need to be booted into recovery to sideload the zip, not the bootloader
Sent from my Nexus 9 using XDA Free mobile app

jd1639 said:
If you're booted in to the bootloader you need to use fastboot commands, fastboot devices. That still doesn't address your problem though. You need to be booted into recovery to sideload the zip, not the bootloader
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
thanks, I see I am doing it all wrong..
i have found this guide
http://forum.xda-developers.com/showthread.php?t=2559200
when i get to the
adb usb
it also says device not found despite the deamon starting successfully on port 5037... i will need help please

cesar.maranhao said:
thanks, I see I am doing it all wrong..
i have found this guide
http://forum.xda-developers.com/showthread.php?t=2559200
when i get to the
adb usb
it also says device not found despite the deamon starting successfully on port 5037... i will need help please
Click to expand...
Click to collapse
First off, you need the stock recovery, not twrp or cwm to flash the update.zip. If you don't have the stock recovery you'll need to flash it in fastboot with the recovery.img from 5.0. Are you on the stock recovery? Also, are you rooted?
Sent from my Nexus 9 using XDA Free mobile app

jd1639 said:
If you're booted in to the bootloader you need to use fastboot commands, fastboot devices. That still doesn't address your problem though. You need to be booted into recovery to sideload the zip, not the bootloader
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
jd1639 said:
First off, you need the stock recovery, not twrp or cwm to flash the update.zip. If you don't have the stock recovery you'll need to flash it in fastboot with the recovery.img from 5.0. Are you on the stock recovery? Also, are you rooted?
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
yes, i am rooted with twrp custom recovery.
i tried to install the ota zip from the custom recovery. the ota file i downloaded and it failed. i tried all three options you see in this topic:
http://forum.xda-developers.com/google-nexus-5/general/ref-nexus-5-stock-ota-urls-t2475327
what should i do then?

1. Its adb reboot-bootloader to reboot into the bootloader.
Have to choose recovery from the bootloader, then press and hold power button then press volume up once to be able to choose adb sideload and press power. Once choosing this option from recovery then check adb devices. If it doesn't recognize your device then the USB drivers are not installed properly. Go to device manager on your PC to install the correct drivers. There are a few post already about this. Alternately you can use universal naked drivers. These work very well with Nexus devices.
2. Have to be completely stock to apply the OTA. Simply clicking unroot via supersu does not allow the update to apply.
---------- Post added at 03:50 PM ---------- Previous post was at 03:48 PM ----------
http://forum.xda-developers.com/goo...nosing-usb-driver-adb-issues-windows-t2514396

cesar.maranhao said:
yes, i am rooted with twrp custom recovery.
i tried to install the ota zip from the custom recovery. the ota file i downloaded and it failed. i tried all three options you see in this topic:
http://forum.xda-developers.com/google-nexus-5/general/ref-nexus-5-stock-ota-urls-t2475327
what should i do then?
Click to expand...
Click to collapse
First unroot using the full unroot option in supersu settings. Then you'll need to flash the system, recovery, and boot images from 5.0 with fastboot. Then you can sideload the update.zip in the stock recovery. If you've changed the radio you'll have to flash that from 5.0 too
It's a pita. The other option is to just flash in fastboot the radio, system, and boot images from 5.0.1 and forgo the ota.
Either option won't wipe data
Sent from my Nexus 9 using XDA Free mobile app

Jnewell05 said:
1. Its adb reboot-bootloader to reboot into the bootloader.
Have to choose recovery from the bootloader, then press and hold power button then press volume up once to be able to choose adb sideload and press power. Once choosing this option from recovery then check adb devices. If it doesn't recognize your device then the USB drivers are not installed properly. Go to device manager on your PC to install the correct drivers. There are a few post already about this. Alternately you can use universal naked drivers. These work very well with Nexus devices.
2. Have to be completely stock to apply the OTA. Simply clicking unroot via supersu does not allow the update to apply.
---------- Post added at 03:50 PM ---------- Previous post was at 03:48 PM ----------
http://forum.xda-developers.com/goo...nosing-usb-driver-adb-issues-windows-t2514396
Click to expand...
Click to collapse
jd1639 said:
First unroot using the full unroot option in supersu settings. Then you'll need to flash the system, recovery, and boot images from 5.0 with fastboot. Then you can sideload the update.zip in the stock recovery. If you've changed the radio you'll have to flash that from 5.0 too
It's a pita. The other option is to just flash in fastboot the radio, system, and boot images from 5.0.1 and forgo the ota.
Either option won't wipe data
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
I am so confused.. when i bought my nexus 5 i upgraded kitkat several times by flashing a downloaded OTA from xda forums inside custom recovery. i just flashed the update and flashed the supersu afterwards to keep root.
i do not understand what is happening now, i never done such steps before.
were those kitkat ota's modified by xda members to help not so knowledgeable users like me to update?
this is what I have been using:
EDIT:
Section B: Flashing in a Custom Recovery (TWRP- CWM)
(For Flashing 4.4.4 OTAs and Below ONLY!)
1) Download the OTA.zip and copy to your phone.
2) Boot into recovery.
3) Flash the OTA just like you would a ROM.
4) Reboot.
http://forum.xda-developers.com/google-nexus-5/general/info-nexus-5-ota-help-desk-t2523217
Click to expand...
Click to collapse
Just noticed thisis only for 4.4.4 OTA's and below only.

cesar.maranhao said:
I am so confused.. when i bought my nexus 5 i upgraded kitkat several times by flashing a downloaded OTA from xda forums inside custom recovery. i just flashed the update and flashed the supersu afterwards to keep root.
i do not understand what is happening now, i never done such steps before.
were those kitkat ota's modified by xda members to help not so knowledgeable users like me to update?
Click to expand...
Click to collapse
No the difference is 5 lollipop. They've changed the way it needs to be update. Before you could easily flash it in a custom recovery. You can't do that any more.
The easiest, and what I did is to just flash the radio, system and boot images from 5.0.1 in fastboot. Just download the factory image, it's a .tgz file. Extract it using 7-zip. Inside is a zip file, extract that too. In the first file is the radio image, it has a long name. In the zip file you extract is the system and boot images. You'll want to put those files in the same directory as you have fastboot.exe.
Then boot in to the bootloader and open a command window in the same folder as fastboot.exe and type the commands
fastboot flash radio radio.img (note, use the full file name of the radio)
fastboot flash boot boot.img
fastboot flash system system.img
Then you're done
Sent from my Nexus 9 using XDA Free mobile app

jd1639 said:
No the difference is 5 lollipop. They've changed the way it needs to be update. Before you could easily flash it in a custom recovery. You can't do that any more.
The easiest, and what I did is to just flash the radio, system and boot images from 5.0.1 in fastboot. Just download the factory image, it's a .tgz file. Extract it using 7-zip. Inside is a zip file, extract that too. In the first file is the radio image, it has a long name. In the zip file you extract is the system and boot images. You'll want to put those files in the same directory as you have fastboot.exe.
Then boot in to the bootloader and open a command window in the same folder as fastboot.exe and type the commands
fastboot flash radio radio.img (note, use the full file name of the radio)
fastboot flash boot boot.img
fastboot flash system system.img
Then you're done
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
you missed my last edit while you were replying.
EDIT:
Section B: Flashing in a Custom Recovery (TWRP- CWM)
(For Flashing 4.4.4 OTAs and Below ONLY!)
1) Download the OTA.zip and copy to your phone.
2) Boot into recovery.
3) Flash the OTA just like you would a ROM.
4) Reboot.
http://forum.xda-developers.com/google-nexus-5/general/info-nexus-5-ota-help-desk-t2523217
Click to expand...
Click to collapse
Just noticed thisis only for 4.4.4 OTA's and below only.
Click to expand...
Click to collapse
it is more clear for me now. i used all those fastboot command line when i flashed 5.0.0, one line for each image.
i will do that for 5.0.1. thanks a lot mate for all the clarification.
one last question: will I lose any data/configurations by apllying this method?

cesar.maranhao said:
you missed my last edit while you were replying.
it is more clear for me now. i used all those fastboot command line when i flashed 5.0.0, one line for each image.
i will do that for 5.0.1. thanks a lot mate for all the clarification.
one last question: will I lose any data/configurations by apllying this method?
Click to expand...
Click to collapse
No data will be lost. Everything will still be there
Oh, you're custom recovery will be gone and you'll have to re-root but that's easy. If you have problems let me know.
Sent from my Nexus 5 using XDA Free mobile app

jd1639 said:
No the difference is 5 lollipop. They've changed the way it needs to be update. Before you could easily flash it in a custom recovery. You can't do that any more.
The easiest, and what I did is to just flash the radio, system and boot images from 5.0.1 in fastboot. Just download the factory image, it's a .tgz file. Extract it using 7-zip. Inside is a zip file, extract that too. In the first file is the radio image, it has a long name. In the zip file you extract is the system and boot images. You'll want to put those files in the same directory as you have fastboot.exe.
Then boot in to the bootloader and open a command window in the same folder as fastboot.exe and type the commands
fastboot flash radio radio.img (note, use the full file name of the radio)
fastboot flash boot boot.img
fastboot flash system system.img
Then you're done
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
jd1639 said:
No data will be lost. Everything will still be there
Oh, you're custom recovery will be gone and you'll have to re-root but that's easy. If you have problems let me know.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
nice! i suppose i need to flash the custom recovery and root again right?

cesar.maranhao said:
nice! i suppose i need to flash the custom recovery and root again right?
Click to expand...
Click to collapse
Yep, flash the twrp.img in fastboot, fastboot flash recovery twrp.img (I recommend twrp, if you have a problem with this step let me know. It may try to keep the stock recovery). Then flash supersu 2.4 in twrp
Sent from my Nexus 9 using XDA Free mobile app

jd1639 said:
Yep, flash the twrp.img in fastboot, fastboot flash recovery twrp.img (I recommend twrp, if you have a problem with this step let me know. It may try to keep the stock recovery). Then flash supersu 2.4 in twrp
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
will you stay online for a while? if I run into trouble you already know what is going on

cesar.maranhao said:
will you stay online for a while? if I run into trouble you already know what is going on
Click to expand...
Click to collapse
I'll be here
Sent from my Nexus 9 using XDA Free mobile app

jd1639 said:
I'll be here
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
hey there!
already flashed everything! after i flashed the twrp custom recovery, it said i wasn't rooted so i installed the root from there.
it then upgraded some apps and i confirm i am now in 5.0.1. however, root checker says i am not rooted and need to confirm in the specific forum how to root my device..
after this, i tried to go to twrp again but i have an android with a red exclamation mark upon its belly.
wht should i do?

cesar.maranhao said:
hey there!
already flashed everything! after i flashed the twrp custom recovery, it said i wasn't rooted so i installed the root from there.
it then upgraded some apps and i confirm i am now in 5.0.1. however, root checker says i am not rooted and need to confirm in the specific forum how to root my device..
after this, i tried to go to twrp again but i have an android with a red exclamation mark upon its belly.
wht should i do?
Click to expand...
Click to collapse
Put SuperSU beta flashable zip on your sdcard then fastboot flash TWRP. Boot directly into recovery and flash SuperSU

cesar.maranhao said:
hey there!
already flashed everything! after i flashed the twrp custom recovery, it said i wasn't rooted so i installed the root from there.
it then upgraded some apps and i confirm i am now in 5.0.1. however, root checker says i am not rooted and need to confirm in the specific forum how to root my device..
after this, i tried to go to twrp again but i have an android with a red exclamation mark upon its belly.
wht should i do?
Click to expand...
Click to collapse
I thought that would be the problem. You'll want to boot twrp, flash supersu and the flash twrp
fastboot boot twrp.img
Then flash supersu in twrp
Then boot back into the bootloader and
fastboot flash recovery twrp.img
There are couple of scripts, one in /system and one in /system/bin that put the stock recovery back on. You could remove the scripts put I find this easier
Sent from my Nexus 9 using XDA Free mobile app

jd1639 said:
I thought that would be the problem. You'll want to boot twrp, flash supersu and the flash twrp
fastboot boot twrp.img
Then flash supersu in twrp
Then boot back into the bootloader and
fastboot flash recovery twrp.img
There are couple of scripts, one in /system and one in /system/bin that put the stock recovery back on. You could remove the scripts put I find this easier
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
rootSU said:
Put SuperSU beta flashable zip on your sdcard then fastboot flash TWRP. Boot directly into recovery and flash SuperSU
Click to expand...
Click to collapse
i am having problems in putting the supersu file into my nexus 5, it says the device has either stopped or has been disconnected.. this never happened before. i haveit setup as MTP. also tried ptp without success

Unable to boot in to recovery mode!!!! Help!!!!!!!!!!!!!

I have an Honor 6 L02. After i used the honor 6 multitool to flash my CWM recovery back in to stock, i did not get the recovery screen when i pressed down the buttons, nor when i downloaded an app that would do that for me, also my OTA updates fails, i thought rooting was the problem so i unrooted, now Freedom stopped working so i cant use google play and youtube. PLEASE HELP!

also my phone was rooted so i unroot it

Please help

come on guys please

for the rooted phones you can try "Quick boot" from Google play store. It has option to "Boot into recovery"...
can you also try to send CWM again via Multitool and to see if you can get into CWM?

Bill Cui said:
I have an Honor 6 L02. After i used the honor 6 multitool to flash my CWM recovery back in to stock, i did not get the recovery screen when i pressed down the buttons, nor when i downloaded an app that would do that for me, also my OTA updates fails, i thought rooting was the problem so i unrooted, now Freedom stopped working so i cant use google play and youtube. PLEASE HELP!
Click to expand...
Click to collapse
Don't freak out. Stay calm...
Follow the steps:
Installing ADB / Fastboot and Necessary Drivers
Download 15 Seconds ADB and Fastboot Drivers. Visit the official XDA forum for download and installation instructions.
Install Fastboot drivers by downloading and installing Huawei HiSuite via this link.
Installing Custom Recovery
Ensure that you have successfully installed all necessary tools and drivers mentioned above.
Download the CWM recovery image according to your EMUI version. See this XDA Thread for download links.
Power off your device. While holding Volume Down button use a USB cable to attach your device to computer. Device will automatically boot to fastboot mode.
Open Command Prompt in the directory where you have extracted/downloaded the files by holding Shift and Right Mouse Button and finally click Open Command Prompt window here in the context menu.
Now execute the following command one at a time (replace recovery name with the one you downloaded);
Code:
fastboot flash recovery [I]recovery_name.img[/I]
fastboot reboot
Ta Da!!!

mfbcool said:
Don't freak out. Stay calm...
Follow the steps:
Installing ADB / Fastboot and Necessary Drivers
Download 15 Seconds ADB and Fastboot Drivers. Visit the official XDA forum for download and installation instructions.
Install Fastboot drivers by downloading and installing Huawei HiSuite via this link.
Installing Custom Recovery
Ensure that you have successfully installed all necessary tools and drivers mentioned above.
Download the CWM recovery image according to your EMUI version. See this XDA Thread for download links.
Power off your device. While holding Volume Down button use a USB cable to attach your device to computer. Device will automatically boot to fastboot mode.
Open Command Prompt in the directory where you have extracted/downloaded the files by holding Shift and Right Mouse Button and finally click Open Command Prompt window here in the context menu.
Now execute the following command one at a time (replace recovery name with the one you downloaded);
Code:
fastboot flash recovery [I]recovery_name.img[/I]
fastboot reboot
Ta Da!!!
Click to expand...
Click to collapse
Thank you, i did successfully flash the recovery, but i still cannot boot in to recovery mode, and now i cant turn my phone off because it will reboot by itself

Bill Cui said:
Thank you, i did successfully flash the recovery, but i still cannot boot in to recovery mode, and now i cant turn my phone off because it will reboot by itself
Click to expand...
Click to collapse
Does it reboot when you try to enter recovery or it restarts itself at boot process i.e honor boot animation shows up and then it restarts (bootloop).
I really don't know why you are still unable to boot to recovery. Were you able to boot to stock recovery before flashing custom? Also, is your bootloader unlocked?
Your best bet at this stage would be to flash stock recovery and then completely flash stock ROM. This would wipe your data but will resurrect your device from bootloop.
---------- Post added at 11:47 AM ---------- Previous post was at 11:42 AM ----------
You mentioned a warez app in your original post OP. Please note that any mentioning or discussion of such apps violates XDA's code of conduct and terms. Be careful in future

Cant flash TWRP ! S.O.S!

hi, dont send for googling please, i have spent several hours reading
i cant flash TWRP because i cant login into it, after a flash i reboot, and try to press power button, but its resets or cynogenmod is booting, so its probably overwrite the TWRP recovery ...
all this after cm13 update, i know i need old TWRP and stock ROM, but just cant flash it
i use adb
screenshot is attached

talboris said:
hi, dont send for googling please, i have spent several hours reading
i cant flash TWRP because i cant login into it, after a flash i reboot, and try to press power button, but its resets or cynogenmod is booting, so its probably overwrite the TWRP recovery ...
all this after cm13 update, i know i need old TWRP and stock ROM, but just cant flash it
i use adb
screenshot is attached
Click to expand...
Click to collapse
After flashing twrp you have two options. Either turn off your phone by long pressing power button and then use volume down + power button combo to boot into recovery.
Second option is after flashing it do fastboot reboot and immediately hold down the volume down button. It will boot into recovery
Sent from my A0001 using Tapatalk

talboris said:
After flashing twrp you have two options. Either turn off your phone by long pressing power button and then use volume down + power button combo to boot into recovery.
Second option is after flashing it do fastboot reboot and immediately hold down the volume down button. It will boot into recovery
Click to expand...
Click to collapse
I am trying, but it jumps to CM rom, i cant reach twrp recovery..
do you know why reboot twrp.img doesnt work?

Renosh said:
After flashing twrp you have two options. Either turn off your phone by long pressing power button and then use volume down + power button combo to boot into recovery.
Second option is after flashing it do fastboot reboot and immediately hold down the volume down button. It will boot into recovery
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
talboris said:
hi, dont send for googling please, i have spent several hours reading
i cant flash TWRP because i cant login into it, after a flash i reboot, and try to press power button, but its resets or cynogenmod is booting, so its probably overwrite the TWRP recovery ...
all this after cm13 update, i know i need old TWRP and stock ROM, but just cant flash it
i use adb
screenshot is attached
Click to expand...
Click to collapse
talboris said:
I am trying, but it jumps to CM rom, i cant reach twrp recovery..
do you know why reboot twrp.img doesnt work?
Click to expand...
Click to collapse
if i choose the second option FASTBOOT REBOOT ,should i unplug the phone from the pc, or it doesnt matter..
i dont understand what is my problem, i am not that dumb, i start to believe that it says ok, like in screenshot, but twrp is not really there, so when OS doesnt find the recovery its jump to CM rom..
tnx

talboris said:
I am trying, but it jumps to CM rom, i cant reach twrp recovery..
do you know why reboot twrp.img doesnt work?
Click to expand...
Click to collapse
i have the same problem then i used Bacon Root Toolkit for oneplus one from there i flashed twrap .img and i got twrap recovery

commgo said:
i have the same problem then i used Bacon Root Toolkit for oneplus one from there i flashed twrap .img and i got twrap recovery
Click to expand...
Click to collapse
please explain me, i am already 2 days on that problem, can you please guide me?

i found this one http://www.wugfresh.com/brt/
but no tutorial how to use...

commgo said:
i have the same problem then i used Bacon Root Toolkit for oneplus one from there i flashed twrap .img and i got twrap recovery
Click to expand...
Click to collapse
talboris said:
i found this one http://www.wugfresh.com/brt/
but no tutorial how to use...
Click to expand...
Click to collapse
installed bacon root, i try to run ROOT with TWRP it says " ADB DEVICE NOT FOUND"
but if i do fastboot devices via cmd i see my device?
i am so exhausted...

talboris said:
installed bacon root, i try to run ROOT with TWRP it says " ADB DEVICE NOT FOUND"
but if i do fastboot devices via cmd i see my device?
i am so exhausted...
Click to expand...
Click to collapse
If you're in fastboot then only fastboot devices command will work. Adb commands are done when the phone is booted in OS. I saw that photo you posted and it seems you know how to flash TWRP (fastboot flash recovery *****.img). Flash TWRP 2.8.6.0 image if it says successful. Then turn off your phone and use button combo. Can't be any simpler.
Sent from my A0001 using Tapatalk

Renosh said:
If you're in fastboot then only fastboot devices command will work. Adb commands are done when the phone is booted in OS. I saw that photo you posted and it seems you know how to flash TWRP (fastboot flash recovery *****.img). Flash TWRP 2.8.6.0 image if it says successful. Then turn off your phone and use button combo. Can't be any simpler.
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
i am really thankful Renosh for you, that image of TWRP really worked, now how can i flash a stable ROM ?
previously i have updated CM 13 and it ****ed up all the system, it happened to a lot people, same issues to everybody, now i need a good ROM, can i have 2 ROMS with TWRP ?
which way is better, adb or bacon root ?
i am so thankful to you Renosh, if you send me your address in private i will send you a post card or something for my gratitude

ok, now what do i do? i can reach the twrp, how can i flash ROM now? i cant to put a ROM into the phone, since firstly i need to mount, but the pc cant mount it
i have ADB and bacon..

talboris said:
ok, now what do i do? i can reach the twrp, how can i flash ROM now? i cant to put a ROM into the phone, since firstly i need to mount, but the pc cant mount it
i have ADB and bacon..
Click to expand...
Click to collapse
In twrp you can copy files just like if you had it on. Just connect to PC and transfer ROM + gapps. Latest CM13 + Open gapps should work perfectly as long as you use TWRP 2.8.6.0. Make sure you have the right drivers for your phone. Google search or go to YouTube you'll find the right drivers
Sent from my A0001 using Tapatalk

Renosh said:
In twrp you can copy files just like if you had it on. Just connect to PC and transfer ROM + gapps. Latest CM13 + Open gapps should work perfectly as long as you use TWRP 2.8.6.0. Make sure you have the right drivers for your phone. Google search or go to YouTube you'll find the right drivers
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
when i connect it to the PC, i dont see it , so i cant transfer the files..
my problem is that i cant transfer the files...
when i connect my other phone a have got a prompt window, but in this case no prompt window, so i guess i need to mount it
but even with mounting i can understand where and how to transfer the files
10x!

update :
i have managed to install TWRP again
so how do i install ROM manually now ?
bacon doesnt help me, PC cant mount TWRP again...

talboris said:
update :
i have managed to install TWRP again
so how do i install ROM manually now ?
bacon doesnt help me, PC cant mount TWRP again...
Click to expand...
Click to collapse
Use ADB Sideload

Honor 6 - Unable to access recovery mode. Stuck at boot screen (honor logo)

Hi,
My Honor 6 (Indian Version) was stuck in boot loop post OTA upgrade from B822 to B831. In order to fix this issue, I went through many forums available online and then decided to use the Multi Tool to downgrade to Android L & EMUI 3.1.
To get this done I have followed the below steps:
1. Unlock bootloader
2. Extract BOOT, CUST, RECOVERY and SYSTEM files from the update package downloaded from Honor.in site. //(Honor 6_Firmware_H60-L04_Android 5.1.1_EMUI 3.1_C675B570_India_Flipkart)//
3. Used Multi Tool to unbrick.
Post this the phone is not able to get into recovery mode; it's stuck at the logo screen. It doesnot recognise the 3 button command to boot into recovery mode.
I have tried using the 'boot to recovery' command in Multi Tool but it throws error "daemon not running starting on port 5037".
I have also tried adb command but for some reason my computer does not recognise my mobile.
i.e. adb devices --> doesnot show my device. (yes, I have updated the abb drivers). So I am not able to use any adb commands.
Then i tried installing/flashing CWM & TWRP recovery. None helped. :crying:
Now I am here, out of options and do not know how to proceed.
Could someone in this forum help me fix the current issue? Please.
In addition, I would like to know a few things:
a. How to install a new OS/ROM on a dead phone? (Healthy hardware with corrupt software)
b. How to format any phone and start a fresh installation?
c. How to read internal memory of a phone which has no ROM or corrupt software?
I am new to all this. Please bear with me.
Thanks,
Sampath

sampathnayak09 said:
Hi,
My Honor 6 (Indian Version) was stuck in boot loop post OTA upgrade from B822 to B831. In order to fix this issue, I went through many forums available online and then decided to use the Multi Tool to downgrade to Android L & EMUI 3.1.
To get this done I have followed the below steps:
1. Unlock bootloader
2. Extract BOOT, CUST, RECOVERY and SYSTEM files from the update package downloaded from Honor.in site. //(Honor 6_Firmware_H60-L04_Android 5.1.1_EMUI 3.1_C675B570_India_Flipkart)//
3. Used Multi Tool to unbrick.
Post this the phone is not able to get into recovery mode; it's stuck at the logo screen. It doesnot recognise the 3 button command to boot into recovery mode.
I have tried using the 'boot to recovery' command in Multi Tool but it throws error "daemon not running starting on port 5037".
I have also tried adb command but for some reason my computer does not recognise my mobile.
i.e. adb devices --> doesnot show my device. (yes, I have updated the abb drivers). So I am not able to use any adb commands.
Then i tried installing/flashing CWM & TWRP recovery. None helped. :crying:
Now I am here, out of options and do not know how to proceed.
Could someone in this forum help me fix the current issue? Please.
In addition, I would like to know a few things:
a. How to install a new OS/ROM on a dead phone? (Healthy hardware with corrupt software)
b. How to format any phone and start a fresh installation?
c. How to read internal memory of a phone which has no ROM or corrupt software?
I am new to all this. Please bear with me.
Thanks,
Sampath
Click to expand...
Click to collapse
First of all hold and press power + vol down to boot into bootloader mode and type
Fastboot devices
After connecting your phone to PC and opening a command window in platform-tools. Your device should be listed.
adb devices works only when your phone is already booted into Android or running twrp.
Copy and paste the four image files to platform-tools folder and fire these commands
Fastboot flash boot boot.img
Fastboot flash recovery recovery.img
Fastboot flash system system.img
Fastboot flash cust cust.img
And then use the 3 button command.
(Platform-tools folder can be downloaded after installing latest Android SDK software)

How to return back to Stock Recovery & Install Stock Rom.
muradulislam said:
First of all hold and press power + vol down to boot into bootloader mode and type
Fastboot devices
After connecting your phone to PC and opening a command window in platform-tools. Your device should be listed.
adb devices works only when your phone is already booted into Android or running twrp.
Copy and paste the four image files to platform-tools folder and fire these commands
Fastboot flash boot boot.img
Fastboot flash recovery recovery.img
Fastboot flash system system.img
Fastboot flash cust cust.img
And then use the 3 button command.
(Platform-tools folder can be downloaded after installing latest Android SDK software)
Click to expand...
Click to collapse
I am in a bit different situation, let me explain.
Till day before yesterday I was on B570 Rom, then I upgraded over OTA to B831, then Unlocked Bootloader, Rooted, Installed Latest TWRP Recovery & Installed Latest Xposed Framework, everything went successfull & My phone is running fine.
But the question that arises to me is that none of the Stock Marshmallow update for Honor 6 - H60-L04 has been stable as compared to Lollipop Version & I found B570 super stable & the possibility of myself reverting back to B570 is more. What would be the procedure to revert back to B570.. I think first of all I would have to revert back to stock recovery & then flash the rom package, but how to do this successfully.
Kindly advice.

muradulislam said:
First of all hold and press power + vol down to boot into bootloader mode and type
Fastboot devices
After connecting your phone to PC and opening a command window in platform-tools. Your device should be listed.
adb devices works only when your phone is already booted into Android or running twrp.
Copy and paste the four image files to platform-tools folder and fire these commands
Fastboot flash boot boot.img
Fastboot flash recovery recovery.img
Fastboot flash system system.img
Fastboot flash cust cust.img
And then use the 3 button command.
(Platform-tools folder can be downloaded after installing latest Android SDK software)
Click to expand...
Click to collapse
Thank you for your response. :good:
I have flashed all the files using the fastboot mode, but my phone does not recognise the 3 button command.
It either displays the Honor logo or restarts with a quick vibration. the only command it recognised is 'Vol Down + USB plugged into a computer' (for fastboot).
When flashed with Honor Custom or CWM recovery the phone does not recognise:
1. Vol up + Vol down + Power - for recovery mode
2. Vol down + Power - for hard reset/clear cache partition
When flashed with TWRP recovery the phone only recognises: Power + Vol Up button which boots into recovery mode; however this works only when connected to a power source, the moment I disconnect the power cable the phone switches off.
I tried to install Honor 6 custom ROM EMUI4.0 using TWRP. Need guidance on the below two scenarios.
1. TWRP only recognises .zip files. HONOR custom ROMs are in .app format. What should I do?
2. As a work around, I have downloaded 'Honor 6_Firmware_H60-L04_Andriod 6.0_EMUI 4.0_C432B820_Channel-Others.zip' from xda forum and tried installing it, but TWRP throws a 'no md5 file found' error.
To address this I tried using WinMD5.exe to get the MD5 code and manually created a .MD5 file, but TWRP did not recognise it. Please guide.
Thanks,
Sampath

sampathnayak09 said:
Thank you for your response. :good:
I have flashed all the files using the fastboot mode, but my phone does not recognise the 3 button command.
It either displays the Honor logo or restarts with a quick vibration. the only command it recognised is 'Vol Down + USB plugged into a computer' (for fastboot).
When flashed with Honor Custom or CWM recovery the phone does not recognise:
1. Vol up + Vol down + Power - for recovery mode
2. Vol down + Power - for hard reset/clear cache partition
When flashed with TWRP recovery the phone only recognises: Power + Vol Up button which boots into recovery mode; however this works only when connected to a power source, the moment I disconnect the power cable the phone switches off.
I tried to install Honor 6 custom ROM EMUI4.0 using TWRP. Need guidance on the below two scenarios.
1. TWRP only recognises .zip files. HONOR custom ROMs are in .app format. What should I do?
2. As a work around, I have downloaded 'Honor 6_Firmware_H60-L04_Andriod 6.0_EMUI 4.0_C432B820_Channel-Others.zip' from xda forum and tried installing it, but TWRP throws a 'no md5 file found' error.
To address this I tried using WinMD5.exe to get the MD5 code and manually created a .MD5 file, but TWRP did not recognise it. Please guide.
Thanks,
Sampath
Click to expand...
Click to collapse
@DigiGoon

@sampathnayak09
You need to flash stock recovery first, by executing this command:
Code:
fastboot flash recovery recovery.img

@sampathnayak09
Make sure your power button is working correctly. If the files can be flashed successfully, you should be able to boot into recovery.
Honor firmware can only be flashed using three button method. You can search online for making .zip from .app but I am not sure that will solve your problem.
---------- Post added at 04:10 AM ---------- Previous post was at 04:06 AM ----------
mahadikrs said:
I am in a bit different situation, let me explain.
Till day before yesterday I was on B570 Rom, then I upgraded over OTA to B831, then Unlocked Bootloader, Rooted, Installed Latest TWRP Recovery & Installed Latest Xposed Framework, everything went successfull & My phone is running fine.
But the question that arises to me is that none of the Stock Marshmallow update for Honor 6 - H60-L04 has been stable as compared to Lollipop Version & I found B570 super stable & the possibility of myself reverting back to B570 is more. What would be the procedure to revert back to B570.. I think first of all I would have to revert back to stock recovery & then flash the rom package, but how to do this successfully.
Kindly advice.
Click to expand...
Click to collapse
There are rollback packages for going back. I have read those threads on XDA but could not find them again. Will look for them and will send you a link as soon as I found one.

muradulislam said:
@sampathnayak09
Make sure your power button is working correctly. If the files can be flashed successfully, you should be able to boot into recovery.
Honor firmware can only be flashed using three button method. You can search online for making .zip from .app but I am not sure that will solve your problem.
---------- Post added at 04:10 AM ---------- Previous post was at 04:06 AM ----------
There are rollback packages for going back. I have read those threads on XDA but could not find them again. Will look for them and will send you a link as soon as I found one.
Click to expand...
Click to collapse
Thanks for the reply.
If I extract the recovery.img from the B831 Rom Package & flash the same using the below command will it give me back my stock recovery.
fastboot flash recovery recovery.img
And if once I am on Stock Recovery I hope I can again Install a full fresh copy of the B831 Package which will be with Stock Recovery i.e NO TWRP Recovery & root free. And after that when I get the rollback package I can revert back to B570. Pls advice am I going right or is there any possibility that I will brick my phone.

sampathnayak09 said:
Thank you for your response. :good:
I have flashed all the files using the fastboot mode, but my phone does not recognise the 3 button command.
It either displays the Honor logo or restarts with a quick vibration. the only command it recognised is 'Vol Down + USB plugged into a computer' (for fastboot).
When flashed with Honor Custom or CWM recovery the phone does not recognise:
1. Vol up + Vol down + Power - for recovery mode
2. Vol down + Power - for hard reset/clear cache partition
When flashed with TWRP recovery the phone only recognises: Power + Vol Up button which boots into recovery mode; however this works only when connected to a power source, the moment I disconnect the power cable the phone switches off.
I tried to install Honor 6 custom ROM EMUI4.0 using TWRP. Need guidance on the below two scenarios.
1. TWRP only recognises .zip files. HONOR custom ROMs are in .app format. What should I do?
2. As a work around, I have downloaded 'Honor 6_Firmware_H60-L04_Andriod 6.0_EMUI 4.0_C432B820_Channel-Others.zip' from xda forum and tried installing it, but TWRP throws a 'no md5 file found' error.
To address this I tried using WinMD5.exe to get the MD5 code and manually created a .MD5 file, but TWRP did not recognise it. Please guide.
Thanks,
Sampath
Click to expand...
Click to collapse
If the phone keeps going off you tried charging for a while? Battery might not be charging due to no OS.
Sent from my H60-L04 using XDA Labs

mahadikrs said:
Thanks for the reply.
If I extract the recovery.img from the B831 Rom Package & flash the same using the below command will it give me back my stock recovery.
fastboot flash recovery recovery.img
And if once I am on Stock Recovery I hope I can again Install a full fresh copy of the B831 Package which will be with Stock Recovery i.e NO TWRP Recovery & root free. And after that when I get the rollback package I can revert back to B570. Pls advice am I going right or is there any possibility that I will brick my phone.
Click to expand...
Click to collapse
Try out this thread...
http://forum.xda-developers.com/hon...wngrade-eu-h60-l04-indian-b810-t3367031/page1
My honor 6 bricked about a month ago so can not verify this method but to get out of bootloop, always keep a nandroid backup of your device somewhere safe.
You can make a nandroid backup using twrp. Save it to SD card and then copy it to your PC to keep it safe.

muradulislam said:
Try out this thread...
http://forum.xda-developers.com/hon...wngrade-eu-h60-l04-indian-b810-t3367031/page1
My honor 6 bricked about a month ago so can not verify this method but to get out of bootloop, always keep a nandroid backup of your device somewhere safe.
You can make a nandroid backup using twrp. Save it to SD card and then copy it to your PC to keep it safe.
Click to expand...
Click to collapse
Thanks for your response.
I was able to do as per the steps I mentioned in my earlier post & now I have successfully Downgraded to B570, With Unlocked Bootloader, Rooted, TWRP & Xposed Installed. So its time for me to change my signature.
P.s : Also Updated TWRP to the Latest Version i.e TWRP 3.0.2-0

DigiGoon said:
@sampathnayak09
You need to flash stock recovery first, by executing this command:
Code:
fastboot flash recovery recovery.img
Click to expand...
Click to collapse
Hi,
I did flash the stock recovery, but my phone keeps rebooting and doesn't get into recovery mode.
I am sure it has sufficient battery charge. (Close to 90%).
Is there a way to do a clean install on Android phones? Like the way we install Windows OS on computers. Format hard disks, create partitions and then install a fresh OS?
Thanks

mahadikrs said:
Thanks for your response.
I was able to do as per the steps I mentioned in my earlier post & now I have successfully Downgraded to B570, With Unlocked Bootloader, Rooted, TWRP & Xposed Installed. So its time for me to change my signature.
P.s : Also Updated TWRP to the Latest Version i.e TWRP 3.0.2-0
Click to expand...
Click to collapse
Hi,
Could you please provide links to
1. The downgrade transition package.
2. Latest TWRP version.
Also plz help me understand the benifits of TWRP when it cannot be used to install the stock ROM?

sampathnayak09 said:
Hi,
Could you please provide links to
1. The downgrade transition package.
2. Latest TWRP version.
Also plz help me understand the benifits of TWRP when it cannot be used to install the stock ROM?
Click to expand...
Click to collapse
Find attached below the required links for Rollback package & TWRP.
1) https://club.hihonor.com/in/honor6.217/downgrade-link-from-marshmallow-b831-to-lollipop-b570.7935
2) https://twrp.me/devices/huaweihonor6.html
Regarding TWRP, it lets you install custom roms & other apps which cannot be installed thru stock recovery e.g Xposed Framework. Further TWRP is useful for restoring the phone as it allows to restore the phone by using Nandroid backups taken earlier, provided the Nandroid backups are stored in SD Card. There may be more advantages which I am still trying to find out.

mahadikrs said:
Find attached below the required links for Rollback package & TWRP.
1) https://club.hihonor.com/in/honor6.217/downgrade-link-from-marshmallow-b831-to-lollipop-b570.7935
2) https://twrp.me/devices/huaweihonor6.html
Regarding TWRP, it lets you install custom roms & other apps which cannot be installed thru stock recovery e.g Xposed Framework. Further TWRP is useful for restoring the phone as it allows to restore the phone by using Nandroid backups taken earlier, provided the Nandroid backups are stored in SD Card. There may be more advantages which I am still trying to find out.
Click to expand...
Click to collapse
Thank you for providing the links. Let me try installing these.

muradulislam said:
First of all hold and press power + vol down to boot into bootloader mode and type
Fastboot devices
After connecting your phone to PC and opening a command window in platform-tools. Your device should be listed.
adb devices works only when your phone is already booted into Android or running twrp.
Copy and paste the four image files to platform-tools folder and fire these commands
Fastboot flash boot boot.img
Fastboot flash recovery recovery.img
Fastboot flash system system.img
Fastboot flash cust cust.img
And then use the 3 button command.
(Platform-tools folder can be downloaded after installing latest Android SDK software)
Click to expand...
Click to collapse
goldfinv said:
If the phone keeps going off you tried charging for a while? Battery might not be charging due to no OS.
Sent from my H60-L04 using XDA Labs
Click to expand...
Click to collapse
Phone has 75% + charge as shown in TWRP recovery.

sampathnayak09 said:
Phone has 75% + charge as shown in TWRP recovery.
Click to expand...
Click to collapse
Maybe try flashing one of the custom EMUI ROMs via TWRP?
Sent from my H60-L04 using XDA Labs

@mahadikrs @muradulislam @goldfinv
Thank you for your input guys. I am now able to enter stock recovery mode (3 button mode); however, the installation stops at 5%.
Any suggestions?

sampathnayak09 said:
@[email protected]@goldfinv
Thank you for your input guys. I am now able to enter stock recovery mode (3 button mode); however, the installation stops at 5%.
Any suggestions?
Click to expand...
Click to collapse
Give it a couple of tries. Users have suggested that it usually gets stuck somewhere but trying for 2,3 times gets the job done.
Sent from my PLK-L01 using XDA Labs

sampathnayak09 said:
@mahadikrs @muradulislam @goldfinv
Thank you for your input guys. I am now able to enter stock recovery mode (3 button mode); however, the installation stops at 5%.
Any suggestions?
Click to expand...
Click to collapse
Let me know which Rom version is your phone running now & which version you are trying to migrate to.
Also if 3 button Force update is not working then you can try the project menu option.
But first let me know what state your phone is currently in.