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

[How To] Flash Custom recovery and ROMS after 2.20 root

I'm sure there will be a lot of people running the 2.20 root then not knowing what to do. So follow this guide.
Make sure you have adb and fastboot available to use.
Download custom recovery, TWRP is preferred: http://teamw.in/project/twrp2/99
Download the ROM you want to run, plus associated gapps to your phone, place them in the download folder (look in the android development and android original development threads)
1. Put phone into bootloader mode (easy way is: 'adb reboot bootloader')
2. Run the following command:
'fastboot flash recovery openrecovery-twrp-2.3.1.0-evita.img' (make sure img file is in same folder as your adb stuff)
then 'fastboot reboot'
3. Run the following command after the phone is rebooted:
'adb reboot recovery'
4. You should be in the new TWRP recovery. From there it is recommended to do a factory reset before flashing the new ROM.
If you have the newer HBOOT 1.14 (you probably do if coming from stock 2.20), boot.img's will have to be flashed separately via fastboot. Extract the boot.img from you ROM zip of choice and put it in the same directory as fastboot. Reboot your device into boot loader and run "'fastboot flash boot boot.img' (no quotes)
You can then flash the ROM and gapps via recovery and reboot and enjoy.

GuyIncognito721 said:
I'm sure there will be a lot of people running the 2.20 root then not knowing what to do. So follow this guide.
Make sure you have adb and fastboot available to use.
Download custom recovery, TWRP is preferred: http://teamw.in/project/twrp2/99
Download the ROM you want to run, plus associated gapps to your phone, place them in the download folder (look in the android development and android original development threads)
1. Put phone into bootloader mode (easy way is: 'adb reboot bootloader')
2. Run the following command:
'fastboot flash recovery openrecovery-twrp-2.3.1.0-evita.img' (make sure img file is in same folder as your adb stuff)
then 'fastboot reboot'
3. Run the following command after the phone is rebooted:
'adb reboot recovery'
4. You should be in the new TWRP recovery. From there it is recommended to do a factory reset before flashing the new ROM.
If you have the newer HBOOT, radio and boot.imgs will have to be flashed separately via fastboot. Extract the boot.img and radio.img from you ROM zip of choice and put it in the same directory as fastboot. Reboot your device into boot loader and run "'fastboot flash boot boot.img' (no quotes) and 'fastboot flash radio radio.img'
You can then flash the ROM and gapps via recovery and reboot and enjoy.
Click to expand...
Click to collapse
Also, this thread will be useful for flash-aholics :http://forum.xda-developers.com/showthread.php?t=1910294

What if I only see the boot.img and not the radio. The rom is CleanRom V5

may I ask which ROM for a stable AOSP experience ? I daresay none of us 2.20 sufferers have been frequenting the ROM sub-forums

JustTheHustle said:
What if I only see the boot.img and not the radio. The rom is CleanRom V5
Click to expand...
Click to collapse
Sorry, I removed the part about flashing radios. You ca't with the newer HBOOT. Only if we had S-OFF.

GuyIncognito721 said:
1. Put phone into bootloader mode (easy way is: 'adb reboot bootloader')
Click to expand...
Click to collapse
Would you mind expanding on that? I'm new to this even though I've had the phone since May. I'm unable to put the phone into bootloader mode by holding power and volume down (phone just boots normally) so I need another way.
Thanks

sandys1 said:
may I ask which ROM for a stable AOSP experience ? I daresay none of us 2.20 sufferers have been frequenting the ROM sub-forums
Click to expand...
Click to collapse
RebelMOD. Jelly Bean and everything works.
Sent from my HTC One XL

Epos7 said:
Would you mind expanding on that? I'm new to this even though I've had the phone since May. I'm unable to put the phone into bootloader mode by holding power and volume down (phone just boots normally) so I need another way.
Thanks
Click to expand...
Click to collapse
More specifically I'm not sure how to connect to the device in cmd. If I run 'adb reboot bootloader' it returns "device offline"
edit - closing/re-opening cmd appears to have solved the problem.

I'm not sure what I did, but I can no longer boot into bootloader mode. When I try now, I see a phone with a red exclamation mark inside a triangle. Does anyone know what I've done wrong or how to fix this? After a minute or two the phone reboots normally.
edit - I re-ran the script for 2.20 root to create a new backup and am now back in bootloader mode.

When i wrote adb rebot recovery it did not work what happened?

so say i want to run the viper rom i just pull the boot.img out of the rom and place it with my fastboot.exe file ( i have that and my adb files from when i unlocked the bootloader in the same folder) and flash it then i boot into recovery and wipe everything and install like normal? i came from a mytouch 4g and it was as simple as putting on the sd card wiping and flashing. this has got me a little worried i may screw up somewhere
another thing, the file is just named boot do i need to rename it boot.img before i flash it?

jrlatta said:
another thing, the file is just named boot do i need to rename it boot.img before i flash it?
Click to expand...
Click to collapse
I'm guessing the filename extension is just being hidden. Did you try typing boot.img in cmd? If that works you know the extension is there.

i went ahead and flashed everything and its finished now, hopefully everything boots, well i just got a snake so i guess so far so good

ImmenseGT said:
When i wrote adb rebot recovery it did not work what happened?
Click to expand...
Click to collapse
FWIW I had to flash TWRP twice. Didn't stick the first time for some reason.
Sent from my cm_tenderloin using xda app-developers app

if I am already in the bootloader and flashing the boot.img, can I run reboot recovery from my computer right after to go straight to my recovery and flash the rom?
---------- Post added at 03:12 AM ---------- Previous post was at 03:08 AM ----------
Zonen said:
if I am already in the bootloader and flashing the boot.img, can I run reboot recovery from my computer right after to go straight to my recovery and flash the rom?
Click to expand...
Click to collapse
also do I do a factory reset in recovery before I do my fast boot flash boot.img? or do I first flash the boot.img, then reboot to recovery and do factory reset?

Zonen said:
if I am already in the bootloader and flashing the boot.img, can I run reboot recovery from my computer right after to go straight to my recovery and flash the rom?
Click to expand...
Click to collapse
I believe so. That is what I have been doing.

Epos7 said:
................................oops
Click to expand...
Click to collapse
what?
---------- Post added at 03:24 AM ---------- Previous post was at 03:18 AM ----------
Epos7 said:
I believe so. That is what I have been doing.
Click to expand...
Click to collapse
did you get venom installed ok like that?

Zonen said:
if I am already in the bootloader and flashing the boot.img, can I run reboot recovery from my computer right after to go straight to my recovery and flash the rom?
---------- Post added at 03:12 AM ---------- Previous post was at 03:08 AM ----------
also do I do a factory reset in recovery before I do my fast boot flash boot.img? or do I first flash the boot.img, then reboot to recovery and do factory reset?
Click to expand...
Click to collapse
i booted into recovery and wiped everything and then went and flashed the boot image then from bootloader, used the volume keys to get to recovery, booted into recovery and selected the file i wanted to flash let it run and presto it worked, i did not choose to wipe again since i wiped before flashing the boot image because i was afraid it would erase it

Just let you guys know, my toolkit allows you to flash boot.img. Just place the boot.img in the /Data/Kernels folder and press "With this command" and it'll flash it!
http://forum.xda-developers.com/showthread.php?t=1952426

yep working for me too.

[Q] HTC one X bootloop

Hi, Recently brought HTC one X at&t. Successfully unlocked it and also installed twrp recovery and rooted.
But when i installed 4.2.2 CM10 my phone is not able to boot anymore and when i try to boot in recovery its going in bootloop.
I also tried to install different recovery via fastboot but getting same issue, also tried fastboot recovery cache clean.
I also tried to s-off but its not getting off.
PLZ help my phone is not booting up.. its stuck in bootloop.
Attach are details of phone..

o0k00l said:
Hi, Recently brought HTC one X at&t. Successfully unlocked it and also installed twrp recovery and rooted.
But when i installed 4.2.2 CM10 my phone is not able to boot anymore and when i try to boot in recovery its going in bootloop.
I also tried to install different recovery via fastboot but getting same issue, also tried fastboot recovery cache clean.
I also tried to s-off but its not getting off.
PLZ help my phone is not booting up.. its stuck in bootloop.
Attach are details of phone..
Click to expand...
Click to collapse
I believe you must flash the boot.img separately prior to flashing the rom.

you have to fastboot flash the boot img if you dont know how read this
http://forum.xda-developers.com/showthread.php?t=1754018

mominn8266 said:
I believe you must flash the boot.img separately prior to flashing the rom.
Click to expand...
Click to collapse
Yes that is correct. You need to extract the boot.img out of the zip file. Put it int he same folder as your adb and fastboot files. Put your phone into the bootloader and select fastboot. Then hook it up to your computer, and it should change to fastboot usb. now in the adb/fastboot folder, hold down shift and right click,and select open command prompt. type the following command: fastboot flash boot boot.img once it says OKAY, on your phone select reboot, and it should boot up normal

Herc08 said:
Yes that is correct. You need to extract the boot.img out of the zip file. Put it int he same folder as your adb and fastboot files. Put your phone into the bootloader and select fastboot. Then hook it up to your computer, and it should change to fastboot usb. now in the adb/fastboot folder, hold down shift and right click,and select open command prompt. type the following command: fastboot flash boot boot.img once it says OKAY, on your phone select reboot, and it should boot up normal
Click to expand...
Click to collapse
Have flashed .img file but now phone is stuck is boot animation.

Weird. Try to reflash the zip again, and once you are done, go back to boot loader and flash the boot image
Sent from my Carbon-ize Evita using xda-developers app

Herc08 said:
Yes that is correct. You need to extract the boot.img out of the zip file. Put it int he same folder as your adb and fastboot files. Put your phone into the bootloader and select fastboot. Then hook it up to your computer, and it should change to fastboot usb. now in the adb/fastboot folder, hold down shift and right click,and select open command prompt. type the following command: fastboot flash boot boot.img once it says OKAY, on your phone select reboot, and it should boot up normal
Click to expand...
Click to collapse
Herc08 said:
Weird. Try to reflash the zip again, and once you are done, go back to boot loader and flash the boot image
Sent from my Carbon-ize Evita using xda-developers app
Click to expand...
Click to collapse
Just to remind you i am not able to boot in recovery, phone goes in bootloop when i try to go in recovery.
Have already tried erasing cache of recovery and re-installing recovery but still same issue..

Try to reflash the recovery and make sure you have the Evita twrp and not the endeavor
Sent from my Carbon-ize Evita using xda-developers app

Herc08 said:
Try to reflash the recovery and make sure you have the Evita twrp and not the endeavor
Sent from my Carbon-ize Evita using xda-developers app
Click to expand...
Click to collapse
Thanks that helps me and now i am able to boot in recovery... Now i see i have no ROM zip in mobile storage to flash how to transfer one in mobile... :fingers-crossed:
SOL : - Finally my phone is up & working.. So issue was recovery version.....
Thanks for support.

Connect to pc, mount usb storage, copy rom.zip from pc to phone, unmount usb storage, flash.
Sent from my One XL using XDA Premium

o0k00l said:
Thanks that helps me and now i am able to boot in recovery... Now i see i have no ROM zip in mobile storage to flash how to transfer one in mobile... :fingers-crossed:
Click to expand...
Click to collapse
timmaaa said:
Connect to pc, mount usb storage, copy rom.zip from pc to phone, unmount usb storage, flash.
Sent from my One XL using XDA Premium
Click to expand...
Click to collapse
Sweet. Do exactly what timmaaa said. To Mount it, go to Mount > Mount USB storage. And it should pop up on your PC. Then copy and flash like normal.
Sent from my Carbon-ize Evita using xda-developers app

[Q] Phone soft bricked - tried everything!

Hi, if anyone can help me solve this, I will be eternally grateful.
So I was following the CyanogenMod guide for installing the ROM on my HTC One S, but I foolishly flashed the ROM as a .zip, instead of the boot.img.
I can access the bootloader screen, and also the TeamWin recovery screen, but I cannot seem to use flashboot.
It always comes up as <waiting on device>.
I am lost, because I obviously used flashboot to flash the recovery and the ROM across to my phone, and all the files are still in the same folder.
Basically, I cannot start my phone, other than into the recovery screen or the bootloader screen. I cannot seem to flash anything across either.
If anyone can solve this issue from this poor explanation I will be more than impressed.
Many thanks.

trentarmy said:
Hi, if anyone can help me solve this, I will be eternally grateful.
So I was following the CyanogenMod guide for installing the ROM on my HTC One S, but I foolishly flashed the ROM as a .zip, instead of the boot.img.
I can access the bootloader screen, and also the TeamWin recovery screen, but I cannot seem to use flashboot.
It always comes up as <waiting on device>.
I am lost, because I obviously used flashboot to flash the recovery and the ROM across to my phone, and all the files are still in the same folder.
Basically, I cannot start my phone, other than into the recovery screen or the bootloader screen. I cannot seem to flash anything across either.
If anyone can solve this issue from this poor explanation I will be more than impressed.
Many thanks.
Click to expand...
Click to collapse
It is waiting for device because the phone isn't in bootloader (fastboot USB) connected to pc...most likely.
So with phone in bootloader and it reads fastboot USB
from your fastboot folder press shift and right click to open command window.
fastboot flash boot boot.img
(this assumes you have put the boot.img in the fastboot folder)
Then go to recovery
install rom.zip
wipe the caches
If you don't have the rom.zip on your phone then mount usb storage in twrp and move the rom.zip from your pc to your phone.
Hopefully your Hboot is 2.15 or you will just bootloop.

tivofool said:
It is waiting for device because the phone isn't in bootloader (fastboot USB) connected to pc...most likely.
So with phone in bootloader and it reads fastboot USB
from your fastboot folder press shift and right click to open command window.
fastboot flash boot boot.img
(this assumes you have put the boot.img in the fastboot folder)
Then go to recovery
install rom.zip
wipe the caches
If you don't have the rom.zip on your phone then mount usb storage in twrp and move the rom.zip from your pc to your phone.
Hopefully your Hboot is 2.15 or you will just bootloop.
Click to expand...
Click to collapse
So can I clarify that I need to flash both the boot.img file and the rom.zip separately. Then install the rom.zip, not the boot.img?
Because I install the rom.zip last time without the boot.img being flash, and thats when it messed up.
Basically, am I installing the .zip or the .img?
Thanks a million.

trentarmy said:
So can I clarify that I need to flash both the boot.img file and the rom.zip separately. Then install the rom.zip, not the boot.img?
Because I install the rom.zip last time without the boot.img being flash, and thats when it messed up.
Basically, am I installing the .zip or the .img?
Thanks a million.
Click to expand...
Click to collapse
.img , you need to extract boot.img from ROM zip and than just "fastboot flash boot boot.img" ,no quotes in command -that is for boot.img and you do flash ROM as a zip

luxandroid said:
.img , you need to extract boot.img from ROM zip and than just "fastboot flash boot boot.img" ,no quotes in command -that is for boot.img and you do flash ROM as a zip
Click to expand...
Click to collapse
Thanks!
Next issue. I have flashed the boot.img to the phone, now I need to get the rom.zip onto the phone.
Everytime I click mount on TWRP, my computer tells me that I must format the disk before I can use it.
I can't seem to use adb, I always get "no device found".
Any ideas?

adb push ROM.zip /sdcard ,ROM needs to be in fastboot folder, are U s-off or s- on ,did U flash ROM zip before soft brick, can U see files from TWRP when U go to install from sd...some info that is important,if all fails think you'll have to run RUU to fix memory partitions
Sent from my HTC One S using XDA Premium 4 mobile app

luxandroid said:
adb push ROM.zip /sdcard ,ROM needs to be in fastboot folder, are U s-off or s- on ,did U flash ROM zip before soft brick, can U see files from TWRP when U go to install from sd...some info that is important,if all fails think you'll have to run RUU to fix memory partitions
Sent from my HTC One S using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Everything is in the same folder. adb push function still won't work.
I am s-on.
I did flash the rom.zip before the soft-brick, but when it bricked, I wiped the memory and cache, reset to factory settings. So there is currently no files on the phone.

U wiped all this in bootloader ?
Sent from my HTC One S using XDA Premium 4 mobile app
---------- Post added at 07:49 PM ---------- Previous post was at 07:47 PM ----------
Anyway best thing is to flash RUU and do all over again...
Sent from my HTC One S using XDA Premium 4 mobile app

luxandroid said:
U wiped all this in bootloader ?
Sent from my HTC One S using XDA Premium 4 mobile app
---------- Post added at 07:49 PM ---------- Previous post was at 07:47 PM ----------
Anyway best thing is to flash RUU and do all over again...
Sent from my HTC One S using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I wiped it all via the TWRP recovery.
Any chance you could walk me through RUU? Or at least point me in the right direction.
It does sound like it would be easiest just to start all over again. What's the best way to do this?
Thank you for your help.

trentarmy said:
I wiped it all via the TWRP recovery.
Any chance you could walk me through RUU? Or at least point me in the right direction.
It does sound like it would be easiest just to start all over again. What's the best way to do this?
Thank you for your help.
Click to expand...
Click to collapse
what happened when you tried to push the rom.zip via adb?

ThudButt said:
what happened when you tried to push the rom.zip via adb?
Click to expand...
Click to collapse
I just get "error: device not found"
Any ideas?
If not, could someone please run me through just wiping everything and starting again?
Cheers

luxandroid said:
U wiped all this in bootloader ?
Sent from my HTC One S using XDA Premium 4 mobile app
---------- Post added at 07:49 PM ---------- Previous post was at 07:47 PM ----------
Anyway best thing is to flash RUU and do all over again...
Sent from my HTC One S using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Not sure if this makes a difference, but when connected to my PC, my phone is called "My HTC".
I remember reading somewhere that it should be called an Android ADB Device or something similar?

Problem with Nexus Root Toolkit v1.8.4 and nexus5

Hi to all,
I want to install a cwm (the last one) becouse the android update 4.4.4 has erase my recovery.
I run the program, i go to launch and I click Recovery in boot/Flash image.
The program download the last version of recovery anche restart nexus5 in bootloader menu and instal a recovery.
After that restart the phone again and it works perfectly but when I go to recovery mode, it doesn't work. I try more times but doesn't work!
The phone is unlocked and before update 4.4.4 the recovery worked perfectly.
Somebody can resolve thi problem?
Thanks.

Fastboot
moscast said:
Hi to all,
I want to install a cwm (the last one) becouse the android update 4.4.4 has erase my recovery.
I run the program, i go to launch and I click Recovery in boot/Flash image.
The program download the last version of recovery anche restart nexus5 in bootloader menu and instal a recovery.
After that restart the phone again and it works perfectly but when I go to recovery mode, it doesn't work. I try more times but doesn't work!
The phone is unlocked and before update 4.4.4 the recovery worked perfectly.
Somebody can resolve thi problem?
Thanks.
Click to expand...
Click to collapse
Flash through fastboot and see if it works, but that's the wrong section to ask a question..

thunder_bolt96 said:
Flash through fastboot and see if it works, but that's the wrong section to ask a question..
Click to expand...
Click to collapse
ok thanks but can i use this tool?
http://forum.xda-developers.com/goo...tool-nexus-5-multi-tool-3-unlock-cwm-t2509428
The problem is that the link for downloading it does't work.
The firs time that I unlock, and flash recovery and root I used that software.
Can you replace it or give me another link?
Thanks again anche sorry for wonge section....

No. Do NOT use tools like this.
OTA removes root and replaces recovery.
If you want a recovery Download cwm, philz or twrp and fastboot flash recovery image from your pc
If you click the link to the sticky roll-up in my signature, you will find a thread there in section 1 called "adb and fastboot, what is it?". Please read it. You will know everything you need to know
Sent from my Nexus 5 using Tapatalk

moscast said:
ok thanks but can i use this tool?
http://forum.xda-developers.com/goo...tool-nexus-5-multi-tool-3-unlock-cwm-t2509428
The problem is that the link for downloading it does't work.
The firs time that I unlock, and flash recovery and root I used that software.
Can you replace it or give me another link?
Thanks again anche sorry for wonge section....
Click to expand...
Click to collapse
Fastboot flashing a recovery would take less time than it took for you to type out that post.

Thanks all.
I read and I understand that I have to send this commands:
Adb reboot and when device go to bootloader a send:
Fastboot flash recovery recovery. Img
Is it correct?
Sent from my Nexus 5 using XDA Premium 4 mobile app

moscast said:
Thanks all.
I read and I understand that I have to send this commands:
Adb reboot and when device go to bootloader a send:
Fastboot flash recovery recovery. Img
Is it correct?
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Multiple ways to get into the bootloader. Another is hold vol down whilst turning on your phone
Since I suggested you read my adb and fastboot thread, I added a new section about command prompt. It explains that you need to tell cmd where the recovery image is but otherwise correct.
Sent from my Nexus 5 using Tapatalk

rootSU said:
Multiple ways to get into the bootloader. Another is hold vol down whilst turning on your phone
Since I suggested you read my adb and fastboot thread, I added a new section about command prompt. It explains that you need to tell cmd where the recovery image is but otherwise correct.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Hi,
I installed recovery by fastboot on this way:
- adb reboot bootloader (and the phone was run in bootloader mode)
- fastboot flash recovery recovery.img
Now the recovery works perfectly. THANKS!!!!!!!!!!!

moscast said:
Hi,
I installed recovery by fastboot on this way:
- adb reboot bootloader (and the phone was run in bootloader mode)
- fastboot flash recovery recovery.img
Now the recovery works perfectly. THANKS!!!!!!!!!!!
Click to expand...
Click to collapse
sweet, and you did it the right way. now honestly, compared to a root toolkits, isnt the right way easy?

moscast said:
Hi,
I installed recovery by fastboot on this way:
- adb reboot bootloader (and the phone was run in bootloader mode)
- fastboot flash recovery recovery.img
Now the recovery works perfectly. THANKS!!!!!!!!!!!
Click to expand...
Click to collapse
I'm so glad you took the time to read, understand and do. Now when you have other issues, the knowledge you just learnt will be invaluable.
Sent from my Nexus 5 using Tapatalk