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

[Solved] wont boot after chainfire3d in JB. Fastboot- showing error

I tried installing chainfire3d driver in jellybean( i didnt know then that it is not for JB). Now my nexus wont boot into os. it just stays at the unlocked bootloader logo.
1. I can get into recovery mode
2. I have wiped out the cache and factory reset
3. I dont have a update file in my phone.since nexus dont have an external sd card i cant put any file in it directly.
4. I have tried fastboot -it shows my serial ID and i am able to reboot my phone using it but whenever i try to flash recovery.img or update update.zip it shows "cannot load recovery.img" or "cannot update update.zip"
5. I have tried ADB - on using adb shell it shows "error:device not found"
6. on using Odin (not sure whether it is compatible with Nexus s) it detects my phone. when i tried to flash the stock fireware it fails and my device shows "verify image (radio) fail"
Plz help.Is my phone bricked???????

Ok I don't want to be insulting, but you really REALLY need to read on the whole process of Nexus S rooting and using it.
You don't have to use ODIN at all for something so simple. You simply need to reflash a ROM/your ROM.
Mount your SD from within Clockworkmod recovery and transfer a ROM. Then flash it. Done.

What polo says go to recovery- mount and formay- all the way down "mount sd card". Now your phone will be like a usb drive
Sent from my Nexus S

polobunny said:
Ok I don't want to be insulting, but you really REALLY need to read on the whole process of Nexus S rooting and using it.
You don't have to use ODIN at all for something so simple. You simply need to reflash a ROM/your ROM.
Mount your SD from within Clockworkmod recovery and transfer a ROM. Then flash it. Done.
Click to expand...
Click to collapse
thank u for the suggestion. I just have the stock recovery right now. I tried installing clockwork recovery through fastboot but as i mentioned in my first post i get "error:cannot load recovery.img" .Is there any other way of installing a clockwork recovery?

kwibis said:
What polo says go to recovery- mount and formay- all the way down "mount sd card". Now your phone will be like a usb drive
Sent from my Nexus S
Click to expand...
Click to collapse
thank u for the suggestion. I just have the stock recovery right now. I tried installing clockwork recovery through fastboot but as i mentioned in my first post i get "error:cannot load recovery.img" .Is there any other way of installing a clockwork recovery?

amvignesh said:
thank u for the suggestion. I just have the stock recovery right now. I tried installing clockwork recovery through fastboot but as i mentioned in my first post i get "error:cannot load recovery.img" .Is there any other way of installing a clockwork recovery?
Click to expand...
Click to collapse
is your boot loader unlocked??? (command: fastboot oem unlock)
then in the folder that is your fasboot exe, there is the recovery too?
http://nexusshacks.com/nexus-s-hacks/how-to-root-nexus-s-or-nexus-s-4g-new/

Cascabreu said:
is your boot loader unlocked??? (command: fastboot oem unlock)
then in the folder that is your fasboot exe, there is the recovery too?
Click to expand...
Click to collapse
yes it is unlocked(using the command in fastboot also shows already unlocked) and yes the recovery image is in the same folder as that of fastboot.

amvignesh said:
yes it is unlocked(using the command in fastboot also shows already unlocked) and yes the recovery image is in the same folder as that of fastboot.
Click to expand...
Click to collapse
Instead of writting fastboo flash recovery (file name)
Do this fastboot flash recovery (drag and drop file)

Cascabreu said:
Instead of writting fastboo flash recovery (file name)
Do this fastboot flash recovery (drag and drop file)
Click to expand...
Click to collapse
Thanks a lot Cascabreu.it worked . i never knew one could drag and drop files in command prompt(wonder y it didnt work otherwise, I had specified the path correctly).Thanks again..will change the thread topic accordingly....

Yes!!!!! Finally i helped someone!!!!! Hit the thanks button please.
sent from my Nyan NeXus S

I just lolled xD
Sent from my Nexus S

kwibis said:
I just lolled xD
Sent from my Nexus S
Click to expand...
Click to collapse
helppp..im also facing the same prob...i dun know how to run adb shell and those stufff after that...:crying:

C4SCA said:
Yes!!!!! Finally i helped someone!!!!! Hit the thanks button please.
sent from my Nyan NeXus S
Click to expand...
Click to collapse
Good job.. I wouldn't have thought of that...
Sent from my Nexus S using XDA Premium 4 mobile app

C4SCA said:
Yes!!!!! Finally i helped someone!!!!! Hit the thanks button please.
sent from my Nyan NeXus S
Click to expand...
Click to collapse
hi there i also need help with almost the same problem, im using alcatel one touch pop c1, i have rooted it a while ago and the decide to install chainfire 3d i didnt know it doesnt work on jelly bean and now my phone cant boot, i tried doing factory reset but nothing happens it just shows the logo and plays that start up sound but can go past that, i have no back up or anything, and please try to explain in a best possible way im not so good when it comes to computers thanks in advance

tlangey said:
hi there i also need help with almost the same problem, im using alcatel one touch pop c1, i have rooted it a while ago and the decide to install chainfire 3d i didnt know it doesnt work on jelly bean and now my phone cant boot, i tried doing factory reset but nothing happens it just shows the logo and plays that start up sound but can go past that, i have no back up or anything, and please try to explain in a best possible way im not so good when it comes to computers thanks in advance
Click to expand...
Click to collapse
either u can find onlien a way to flash back to stock.
or ur best bet is to go to the store and say u got an update but it failed and that now its not turning on. Warranty will cover that

[Q] 2 Issues when rooting: No SU binary installed, & red triangle on dead android.

[Q] 2 Issues when rooting: No SU binary installed, & red triangle on dead android.
This is my second root ever, I am still very new to this process but my first root went smoothly.
So basically the problem started when I copied the SuperSU file onto my phone using the command
adb push UPDATE-SuperSU-vX.XX.zip /sdcard/
Click to expand...
Click to collapse
After that, I tried finding the zip file through the TWRP recovery screen but I couldn't. I figured I'd go reboot my device. Once I pressed on reboot, a screen popped up asking if I wanted to install SuperSU, "ok cool" I thought and swiped to the right to install. At this point I thought my phones rooted.
I open up SuperSU and I get the error message:
There is no SU binary installed, and SuperSU cannot install it. This is a problem!
If you just upgraded to Android 4.3, you need to manually re-root - consult the relevant forums for your device!
Click to expand...
Click to collapse
I'm on 4.2.2
I decided to go back to recovery mode and that's when I saw the red triangle over the dead android. I thought I had bricked my phone but i'm back to my regular home screen.
Can anyone help me please?

How did you apply TWRP? Did you boot it or flash it. If you chose to boot it, the custom recovery won't stick.
The dead android you are seeing is the stock recovery.
My advice is to boot back into the bootloader and flash the recovery, then flash the SU,zip

FrostedFluke said:
This is my second root ever, I am still very new to this process but my first root went smoothly.
So basically the problem started when I copied the SuperSU file onto my phone using the command
After that, I tried finding the zip file through the TWRP recovery screen but I couldn't. I figured I'd go reboot my device. Once I pressed on reboot, a screen popped up asking if I wanted to install SuperSU, "ok cool" I thought and swiped to the right to install. At this point I thought my phones rooted.
I open up SuperSU and I get the error message:
I'm on 4.2.2
I decided to go back to recovery mode and that's when I saw the red triangle over the dead android. I thought I had bricked my phone but i'm back to my regular home screen.
Can anyone help me please?
Click to expand...
Click to collapse
The red triangle with the android is just the stock recovery. What commands are you using to flash TWRP? I'm assuming you unlocked the boot loader.
You should type in "fastboot flash recovery name_of_twrp_file.img"
Download the supersu.zip from http://download.chainfire.eu/376/SuperSU/UPDATE-SuperSU-v1.89.zip and put it on your phone while the phone is on and connected to a computer. (Just drag it in)
Then reboot into TWRP and flash that file.
Say NO..again NO to the part when it asks you if you want to root. It shouldn't ask you, but if it does, say no.

El Daddy said:
How did you apply TWRP? Did you boot it or flash it. If you chose to boot it, the custom recovery won't stick.
The dead android you are seeing is the stock recovery.
My advice is to boot back into the bootloader and flash the recovery, then flash the SU,zip
Click to expand...
Click to collapse
I used this guide http://forum.xda-developers.com/showthread.php?t=2507905
and by flashing the recovery, you mean by reflashing it? using "flashboot flash recovery recovery.img" as the command?
aooga said:
The red triangle with the android is just the stock recovery. What commands are you using to flash TWRP? I'm assuming you unlocked the boot loader.
You should type in "fastboot flash recovery name_of_twrp_file.img"
Download the supersu.zip from http://download.chainfire.eu/376/SuperSU/UPDATE-SuperSU-v1.89.zip and put it on your phone while the phone is on and connected to a computer. (Just drag it in)
Then reboot into TWRP and flash that file.
Say NO..again NO to the part when it asks you if you want to root. It shouldn't ask you, but if it does, say no.
Click to expand...
Click to collapse
I mentioned above in my first reply that I flashed the recovery using this command "flashboot flash recovery recovery.img"
And it's odd, I have SuperSU zip 1.80, you think that's the problem? I took it straight off this guide though http://forum.xda-developers.com/showthread.php?t=2507905

FrostedFluke said:
I mentioned above in my first reply that I flashed the recovery using this command "flashboot flash recovery recovery.img"
And it's odd, I have SuperSU zip 1.80, you think that's the problem? I took it straight off this guide though http://forum.xda-developers.com/showthread.php?t=2507905
Click to expand...
Click to collapse
Maybe, try using the new zip. Flash TWRP again. It shouldn't be going back to the stock recovery when you reboot unless you chose to just boot it and not flash it.

FrostedFluke said:
I used this guide http://forum.xda-developers.com/showthread.php?t=2507905
and by flashing the recovery, you mean by reflashing it? using "flashboot flash recovery recovery.img" as the command?
I mentioned above in my first reply that I flashed the recovery using this command "flashboot flash recovery recovery.img"
And it's odd, I have SuperSU zip 1.80, you think that's the problem? I took it straight off this guide though http://forum.xda-developers.com/showthread.php?t=2507905
Click to expand...
Click to collapse
Yep, that is the correct command. I would recommend using the most recent SU.zip as well.

aooga said:
Maybe, try using the new zip. Flash TWRP again. It shouldn't be going back to the stock recovery when you reboot unless you chose to just boot it and not flash it.
Click to expand...
Click to collapse
I'll install the SuperSU you linked to me thanks! would you mind explaining to me how to flash it again?
I just open bootloader, command window then flash the recovery file once more?

FrostedFluke said:
I'll install the SuperSU you linked to me thanks! would you mind explaining to me how to flash it again?
I just open bootloader, command window then flash the recovery file once more?
Click to expand...
Click to collapse
Yeah just download THIS FILE first then boot into the bootloader and type in "fastboot flash recovery openrecovery-twrp-2.6.3.4-hammerhead.img" without the quotes in a CMD window.
After it says finished, use the volume keys to select "Recovery Mode" and press the power button to go into it. Then flash the supersu file that you transferred earlier. (the new version).

aooga said:
Yeah just download THIS FILE first then boot into the bootloader and type in "fastboot flash recovery openrecovery-twrp-2.6.3.4-hammerhead.img" without the quotes in a CMD window.
After it says finished, use the volume keys to select "Recovery Mode" and press the power button to go into it. Then flash the supersu file that you transferred earlier. (the new version).
Click to expand...
Click to collapse
I'm in Recovery mode and I still can't find the SuperSU zip file even after i've used the command "adb push"

FrostedFluke said:
I'm in Recovery mode and I still can't find the SuperSU zip file even after i've used the command "adb push"
Click to expand...
Click to collapse
Try adb sideloading it.
Put the Su.zip on your computer in the same folder as your adb.exe
Choose adb sideload on twrp.
Then the command: adb sideload SU.zip

El Daddy said:
Try adb sideloading it.
Put the Su.zip on your computer in the same folder as your adb.exe
Choose adb sideload on twrp.
Then the command: adb sideload SU.zip
Click to expand...
Click to collapse
you mean "adb sideload UPDATE-SuperSU-v1.89.zip"? (sorry I just want to be 100% sure so I make no mistakes)

FrostedFluke said:
you mean "adb sideload UPDATE-SuperSU-v1.89.zip"? (sorry I just want to be 100% sure so I make no mistakes)
Click to expand...
Click to collapse
Yep! I didn't know what the file was named so I just shortened it up to SU.zip
Pro-tip: You can rename files to something shorter such as SU.zip to make it quicker to type in command and eliminate the possibility of mistakes.

El Daddy said:
Yep! I didn't know what the file was named so I just shortened it up to SU.zip
Pro-tip: You can rename files to something shorter such as SU.zip to make it quicker to type in command and eliminate the possibility of mistakes.
Click to expand...
Click to collapse
I get this on my command prompt: "error: closed"

FrostedFluke said:
I get this on my command prompt: "error: closed"
Click to expand...
Click to collapse
run the command: adb usb
Then try sideloading

El Daddy said:
run the command: adb usb
Then try sideloading
Click to expand...
Click to collapse
same error.
I have the option to "swipe to start sideloading" should I swipe first? then run the command?

FrostedFluke said:
same error.
I have the option to "swipe to start sideloading" should I swipe first? then run the command?
Click to expand...
Click to collapse
yes

El Daddy said:
yes
Click to expand...
Click to collapse
It worked, thanks so much man I appreciate the help! you're a lifesaver!
one other quick question. Just to be sure, is there anyway of knowing whether or not my device has been rooted? how will I know for sure?

FrostedFluke said:
It worked, thanks so much man I appreciate the help! you're a lifesaver!
one other quick question. Just to be sure, is there anyway of knowing whether or not my device has been rooted? how will I know for sure?
Click to expand...
Click to collapse
You are welcome. I am always glad to help someone doing things the right way!
Run an app that requires root. If SuperSu requests access, you are rooted.

El Daddy said:
You are welcome. I am always glad to help someone doing things the right way!
Run an app that requires root. If SuperSu requests access, you are rooted.
Click to expand...
Click to collapse
Yup! it's rooted :victory:

FrostedFluke said:
Yup! it's rooted :victory:
Click to expand...
Click to collapse
Congrats!

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

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