Database Info

[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] No OS, can't get to bootloader or recovery

Hey everyone, I just went through the process of rooting my phone using the Hasoon200 tool (http://forum.xda-developers.com/showthread.php?t=1952426). Everything worked fine; I unlocked the bootloader, flashed the TWRP recovery, and installed CM10. However I couldn't get past the CM10 loading screen so I went back to recovery and wiped everything I could (cache, dalvik, system, factory restore) then rebooted. After that I can't get past the white HTC "Quietly Brilliant" splash screen. No bootloader or recovery. Hasoon2000's tool can't reach the phone to do anything. Holding Down Volume and Power buttons just reboots to the splash screen. When I plug the USB into my computer it must be recognized somehow because it connection notification sound plays but I don't see the drive. What can I do now?

Turn on, hold power 10-15 seconds, until screen goes black, let off, press n hold volume down, press power just 2-3 seconds, let off power button but continue holding vol. Down
Than select recovery
And once in bootloader check if you have hboot 1.14
---------- Post added at 03:37 AM ---------- Previous post was at 03:36 AM ----------
When you get back into recovery do the same wipe process than flash the Rom...if you have hboot 1.14 you have to flash the boot.img manually

Yea what box of kittens says ^^^^^^^
http://forum.xda-developers.com/showthread.php?p=33303798
(This thread might help as well.= if your 1.14 hboot) And make sure your thanks button isn't broken at least for the member above who took time to help. :thumbup:
Sent from my HOX w/CM10.1

a box of kittens said:
Turn on, hold power 10-15 seconds, until screen goes black, let off, press n hold volume down, press power just 2-3 seconds, let off power button but continue holding vol. Down
Than select recovery
And once in bootloader check if you have hboot 1.14
---------- Post added at 03:37 AM ---------- Previous post was at 03:36 AM ----------
When you get back into recovery do the same wipe process than flash the Rom...if you have hboot 1.14 you have to flash the boot.img manually
Click to expand...
Click to collapse
Thanks for the response. I'm able to reach the bootloader now, but when I select recovery it freezes once again on the white HTC splash (but this time with the HTC Dev red text below). And I do have hboot 1.14

subarudroid said:
Yea what box of kittens says ^^^^^^^
http://forum.xda-developers.com/showthread.php?p=33303798
(This thread might help as well.= if your 1.14 hboot) And make sure your thanks button isn't broken at least for the member above who took time to help. :thumbup:
Sent from my HOX w/CM10.1
Click to expand...
Click to collapse
Thanks [email protected] reflash your recovery so fastboot flash recovery recovery.img(whatever you have it named but has to end with .img)

Reflash your recovery image. Then try again
Sent from my DROID RAZR using Tapatalk 2

Thanks everyone, I'm back to recovery! Hopefully I can figure it out from here.

If you need anything else just post here.
Sent from my HTC One X using Tapatalk 2

ltjska04 said:
Thanks everyone, I'm back to recovery! Hopefully I can figure it out from here.
Click to expand...
Click to collapse
Easy peasy...
Flash rom,
boot into boot loader,
drop the boot.img inside your adb/fastboot folder,
Right click on you adb/fastboot folder and choose open command prompt here. The type
Fastboot flash boot boot.img
Reboot that beast and enjoy the profits
Sent from my HTC One XL using Tapatalk 2

New to this phone and was a little overeager. I unlocked bootloader, rooted, installed TWRP and flashed CM but didn't flash the boot img before flashing CM so it boots forever, of course (I'm so dumb...)
I can get back to the bootloader where I try to flash my CM boot img but adb won't detect the device (presumably because usb debugging isn't selected since I can't boot into the rom). How can I either 1) get adb to detect so that I can flash the boot img with adb or 2) flash the boot img without adb?
Stumped. Thanks in advance for any/all that can help with this.

_atlien_ said:
New to this phone and was a little overeager. I unlocked bootloader, rooted, installed TWRP and flashed CM but didn't flash the boot img before flashing CM so it boots forever, of course (I'm so dumb...)
I can get back to the bootloader where I try to flash my CM boot img but adb won't detect the device (presumably because usb debugging isn't selected since I can't boot into the rom). How can I either 1) get adb to detect so that I can flash the boot img with adb or 2) flash the boot img without adb?
Stumped. Thanks in advance for any/all that can help with this.
Click to expand...
Click to collapse
Sigh you flash boot img through fastboot

Get phone into bootloader. (White screen, 3 skating droids)- make sure it says "fastboot USB" in red
Right click on your adb/fastboot folder, choose "open command prompt here"
Type--> fastboot devices
See if anything shows up.
Sent from my One X using Tapatalk 2

a box of kittens said:
Sigh you flash boot img through fastboot
Click to expand...
Click to collapse
Hey! Thanks for replying. I'm stuck here. Fastboot flash of the boot img requires the phone to be usb detected, yes? I go to fastboot but when I type 'adb devices' I gets nothing back.
I don't think I was clear in my earlier post. I have CM and gapps flashed but it won't boot into the OS because I didn't flash the boot img first but now I can't get the phone to be detected by adb so I don't know how else to flash the boot img. Thanks for taking the time to reply to me. I realize you didn't have to.

Thanks to all! My phone rides again!

_atlien_ said:
Thanks to all! My phone rides again!
Click to expand...
Click to collapse
Lol what did to do to be able to fastboot flash
Sent from my One X using Tapatalk 2

Hey,
I was stuck too... Managed to get the recovery working but the fastboot flash boot boot.img thing is not working can anyone guide me through this?
I did try the forum ways but still isn't solving the problem...

strommer666 said:
Hey,
I was stuck too... Managed to get the recovery working but the fastboot flash boot boot.img thing is not working can anyone guide me through this?
I did try the forum ways but still isn't solving the problem...
Click to expand...
Click to collapse
Drop the boot.img INSIDE of your adb/fastboot folder.
Boot into bootloader
Right click on your adb/fastboot folder. Choose "open command prompt here" type --> fastboot flash boot boot.img
Sent from my One X using Tapatalk 2

Stuck in bootloader loop
Folks, I was stuck in similar situation as well; I had missed copying the boot.img step initially and after i did a factory reset on the boot loader i got stuck in HTC logo screen with red lines warning.
I followed the directions provided on this thread and am now able to get into TWRP recovery screen. What would be the steps for me now to flash a rom onto the device again. I had flashed the ViperXL rom prior to me stupidly doing the factory reset.
Per directions on another thread, I was trying to first have the rom and boot.img loaded using the mount from TWRP. However when i do the the step of 'Mount USB storage', I get the warning that on my computer that i need to 'Format Disk drive'. Not sure why would i need to do it.
Please help!
Thanks

singh.bobby said:
Folks, I was stuck in similar situation as well; I had missed copying the boot.img step initially and after i did a factory reset on the boot loader i got stuck in HTC logo screen with red lines warning.
I followed the directions provided on this thread and am now able to get into TWRP recovery screen. What would be the steps for me now to flash a rom onto the device again. I had flashed the ViperXL rom prior to me stupidly doing the factory reset.
Per directions on another thread, I was trying to first have the rom and boot.img loaded using the mount from TWRP. However when i do the the step of 'Mount USB storage', I get the warning that on my computer that i need to 'Format Disk drive'. Not sure why would i need to do it.
Please help!
Thanks
Click to expand...
Click to collapse
Doing a factory reset from the bootloader killed your SD partition. You'll need to format it as fat32 before you can access it again. You've lost everything on there.
Sent from my One X using xda app-developers app

exad said:
Doing a factory reset from the bootloader killed your SD partition. You'll need to format it as fat32 before you can access it again. You've lost everything on there.
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
I did the reformat for my SDCard; how do i proceed now? should i move the zip file for the rom to the sd card and try installing it ?What would be the next steps i would need to do to get back to the ViperXL rom i have downloaded; or is there a way for me to go back to the original HTC sense rom i had prior to flashing
Thanks
---------- Post added at 11:44 PM ---------- Previous post was at 11:18 PM ----------
exad said:
Doing a factory reset from the bootloader killed your SD partition. You'll need to format it as fat32 before you can access it again. You've lost everything on there.
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
singh.bobby said:
I did the reformat for my SDCard; how do i proceed now? should i move the zip file for the rom to the sd card and try installing it ?What would be the next steps i would need to do to get back to the ViperXL rom i have downloaded; or is there a way for me to go back to the original HTC sense rom i had prior to flashing
Thanks
Click to expand...
Click to collapse
I was able to flash ViperXL rom again; I placed the zip file for the rom in the TWRP folder after i mounted the device. Thereafter i was able to install the rom from the recovery. All good for now . Although all my data from Sd card got wiped :crying:

[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] boot loop cannot get PC to read device

Okay I was flashing a ROM for the S4 version and the phone began rebooting in the middle of the flash. I realize my error so lets not focus on that Im just trying to fix the boot loop issue. Im trying to use fastboot to fix it but when the phone is connected to my windows 7 PC it makes the connected sound but the device cannot be found by fastboot and it is not shown in the sidebar tree. I cannot get into recovery the TRWP splash screen is displayed for 10 seconds then it goes to the HTC developers use only screen. Please help. Are there any options to repair the damage?

sideshow03 said:
Okay I was flashing a ROM for the S4 version and the phone began rebooting in the middle of the flash. I realize my error so lets not focus on that Im just trying to fix the boot loop issue. Im trying to use fastboot to fix it but when the phone is connected to my windows 7 PC it makes the connected sound but the device cannot be found by fastboot and it is not shown in the sidebar tree. I cannot get into recovery the TRWP splash screen is displayed for 10 seconds then it goes to the HTC developers use only screen. Please help. Are there any options to repair the damage?
Click to expand...
Click to collapse
Okay so can someone confirm then that I am out of luck on this one:?

sideshow03 said:
Okay so can someone confirm then that I am out of luck on this one:?
Click to expand...
Click to collapse
What is device manager showing when your phone is connected to pc while in bootloader (fastboot USB)
for example here is mine:

tivofool said:
What is device manager showing when your phone is connected to pc while in bootloader (fastboot USB)
for example here is mine:
Click to expand...
Click to collapse
It looks the same as yours. But Im not able to connect to the pc to transfer the ROM over. What do I need to do please and thank you?

sideshow03 said:
It looks the same as yours. But Im not able to connect to the pc to transfer the ROM over. What do I need to do please and thank you?
Click to expand...
Click to collapse
well don't give up then, it isn't bricked.
I'm guessing the way you worded it, you have a villeC2 (S3) version and you flashed (S4) ROM? So just make sure you have the S3 version of TWRP flashed and flash a boot.img and rom. wipe caches and you should be fine.
Never mind that if your phone is S4 and I misinterpreted that.
With phone in Bootloader, (fastboot USB) try and check fastboot devices again. Opening your folder with fastboot in it and shift right click, pick open command window.
fastboot devices
(should show a serial #)
flash recovery again, since it was bootlooping. That will probably allow it to be stable again so you can mount USB storage.
If you are in bootloader (fastboot USB) and command window on pc is ran from the correct folder but it still shows device cannot be found then reinstall fastboot drivers. That should fix it for you.

tivofool said:
well don't give up then, it isn't bricked.
I'm guessing the way you worded it, you have a villeC2 (S3) version and you flashed (S4) ROM? So just make sure you have the S3 version of TWRP flashed and flash a boot.img and rom. wipe caches and you should be fine.
Never mind that if your phone is S4 and I misinterpreted that.
With phone in Bootloader, (fastboot USB) try and check fastboot devices again. Opening your folder with fastboot in it and shift right click, pick open command window.
fastboot devices
(should show a serial #)
flash recovery again, since it was bootlooping. That will probably allow it to be stable again so you can mount USB storage.
If you are in bootloader (fastboot USB) and command window on pc is ran from the correct folder but it still shows device cannot be found then reinstall fastboot drivers. That should fix it for you.
Click to expand...
Click to collapse
Im on the S4 variant my error was not flashing the boot.img separately
Im needing to run the cmd as admin so Im opening it up from the start button and changing the directory to the folder fastboot is in. I did get a serial # HT251W408295 fastboot. as shown
Just to confirm my next step is to flash recovery so my command line should be C:\Android fastboot flash recovery twrp2.1.6-ville.img
Correct?
Im using an older twrp cause I read that the newest one is not the best for HTC one S devices.
Thanks

sideshow03 said:
Im on the S4 variant my error was not flashing the boot.img separately
Im needing to run the cmd as admin so Im opening it up from the start button and changing the directory to the folder fastboot is in. I did get a serial # HT251W408295 fastboot. as shown
Just to confirm my next step is to flash recovery so my command line should be C:\Android fastboot flash recovery twrp2.1.6-ville.img
Correct?
Im using an older twrp cause I read that the newest one is not the best for HTC one S devices.
Thanks
Click to expand...
Click to collapse
That would work, BUT:
I see Maximus HD in that pic. For Maximus and any other ROM that uses 2.16 HBoot you can only use the recovery provided in the Maximus original post. It has been modified to work with the new partitions.
If you have moved back to or are still on HBoot 2.15 older firmware, then yes go ahead and flash like you are.
---------- Post added at 07:07 PM ---------- Previous post was at 07:04 PM ----------
oh, and usb storage (mount sd card) will not be available on this new recovery.
Easy way to move a ROM onto the phone while in this recovery is adb push
put ROM.zip in the adb folder and type in command window:
adb push filename.zip /sdcard

tivofool said:
That would work, BUT:
I see Maximus HD in that pic. For Maximus and any other ROM that uses 2.16 HBoot you can only use the recovery provided in the Maximus original post. It has been modified to work with the new partitions.
If you have moved back to or are still on HBoot 2.15 older firmware, then yes go ahead and flash like you are.
---------- Post added at 07:07 PM ---------- Previous post was at 07:04 PM ----------
oh, and usb storage (mount sd card) will not be available on this new recovery.
Easy way to move a ROM onto the phone while in this recovery is adb push
put ROM.zip in the adb folder and type in command window:
adb push filename.zip /sdcard
Click to expand...
Click to collapse
Ok I have both packages now but when I try to flash twrp is shows FAILED (remote: image error! (BootMagic check fail)).
I have verified the md5 with HASHCALC.
Im lost but feel like Im getting somewhere

sideshow03 said:
Ok I have both packages now but when I try to flash twrp is shows FAILED (remote: image error! (BootMagic check fail)).
I have verified the md5 with HASHCALC.
Im lost but feel like Im getting somewhere
Click to expand...
Click to collapse
Is your bootloader locked? Can't install recoveries with locked bootloader.

tivofool said:
Is your bootloader locked? Can't install recoveries with locked bootloader.
Click to expand...
Click to collapse
No I am Unlocked S-off CID 11111111

sideshow03 said:
No I am Unlocked S-off CID 11111111
Click to expand...
Click to collapse
Sorry, you need to extract that zip on your pc and put the recovery.img in your folder. Or I guess just extract it in that same folder you are using.
then depending on the name of the recovery.img flash that. But I think that extracts to recovery.img
so
fastboot flash recovery recovery.img

tivofool said:
Sorry, you need to extract that zip on your pc and put the recovery.img in your folder. Or I guess just extract it in that same folder you are using.
then depending on the name of the recovery.img flash that. But I think that extracts to recovery.img
so
fastboot flash recovery recovery.img
Click to expand...
Click to collapse
Ok Ive completed that and the phone went into recovery, i can see the ROM when I click on the install tab. But when I trying to install the ROM i get E: Unable to open zip file Error flashing zip

sideshow03 said:
Ok Ive completed that and the phone went into recovery, i can see the ROM when I click on the install tab. But when I trying to install the ROM i get E: Unable to open zip file Error flashing zip
Click to expand...
Click to collapse
One of the possibilities with that error is a bad download. You may have to redownload the ROM.
Another is if you change the name of the rom, just in case you did that.

Solved
tivofool said:
One of the possibilities with that error is a bad download. You may have to redownload the ROM.
Another is if you change the name of the rom, just in case you did that.
Click to expand...
Click to collapse
Yes it was a bad download. Thanks for all of your help I really appreciate your time to help me get back up and running. :victory:

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