Database Users

[Tutorial] Restoring Recovery Mode while working only Fastboot Mode*ALL METHODS HERE*

Hello!
Yesterday I found myself in a very terrible situation. I spend about 6-7 hours...
It just happened that I deleted the recovery (through fastboot), and before that deleted firmware of the phone. That is, there remained only mode HBOOT (fastboot). Around the internet and google there are no guides on how to return
recovery by the alternative methods or how to flash a new ROM through
fastboot.
Thats why i want to present to you my little guide... Coz i think it will be very useful for some ppls like me with the same trouble.
So, if you're in a situation where you do not have Recovery, and the phone is not started in boot ROM then first try a standard way to flash a new Recovery through fastboot mode
Standart way of flashing new recovery via fastboot​
1.Connect your phone with PC via USB and power off your phone (if it up).
2.Than start up in fastboot mode - (in my situation, fastboot mode is CAMERA+POWER, then button "send") in all other (as i know) this is starting the phone while pressing button BACK.
3.Open -> Start->Run->cmd (open command prompt in windows*) and write:
Code:
fastboot devices
Than you must see your device serial number like this:
Code:
H94XTGAMSHDY
and should say "fastboot".
If all right - go next. If not - check fastboot mode (is on?) and USB cable.
4.Than change directory via cmd to where you have saved your recovery image (NEW recovery.img !!! ALWAYS CHECK MD5 SUM)
5. Than type this :
Code:
fastboot flash recovery recovery.img [enter]
(while you are stay in the same dir where you saved recovery.img)
(if you got some error about previously version or smth like this you can try to use this: fastboot erase recovery and only than try to flash new recovery from step №5)
6.Check your phone's display, as recovery is being sent and flashed to your device. And check your command prompt/shell to make sure the process is over.
7.Reboot into recovery by holding Home and Power (before it power off device).
Thats all! You can use any recovery, all what you like. I use Amon_RA's recovery.
IF WHILE FLASHING YOU GOT :
Code:
sending 'recovery' <4594kb>... OKAY [ 1.734s]
writing 'recovery'... INFOsignature checking...
FAILED <remote: signature verigy fail>
finished. total time: 3.125
Use next steps (my Alternative method)
And IF you can't flash recovery by this method it is not big trouble as you think now
Alternative way of BOOTING new recovery via fastboot​ checked and founded by me
Everything here is much easier and faster!
Do not be scared as I did it yesterday
Only what you need it :
Change directory via cmd to where you have saved your recovery image (NEW recovery.img !!! ALWAYS CHECK MD5 SUM)
And than TYPE:
Code:
fastboot boot recovery recovery.img
And your phone will be rebooted about 2 seconds in RECOVERY MODE. Yes!
After this you can use your old Nand Back up (restore it) and start up your old ROM. Or you can wipe all and try to flash new ROM and many operations what you can use via recovery. When you will get working ROM and flash it - you can flash recovery via adb. Or Use Rom Manager (Not recommended!)
Why we use this method? Because if you got error while flashing - FAILED <remote: signature verigy fail> you CAN'T FLASH ANY .img. Why? I Don't know, i hope some android guru's help us with it theory
(ALL AFTER THIS LINE ALL TEXT COPYED FROM WIKI.CYANOGEN.COM CREDITS GOES TO Cyanogen. Thx you, god)
If you want to flash recovery via adb (using power on phone with working firmware) (This method working 100% but strongly need working phone with working ROM)
Working only with HTC DREAM (G1) - Attention.
adb method by cyanogen version
Restoring the custom recovery image
Download the flash_image tool (HERE LINK
Next, place the file on your desktop
Change the directory to where "flash_image" is located, e.g. in Windows: cd C:\<path-to-flash_image-location>, in Linux: cd /home/USERNAME/path/to/flash_image on a Mac: cd /Users/USERNAME/path/to/flash_image)
IMPORTANT: Turn on USB debugging. Settings -> Applications -> Development -> check the box "USB Debugging"
Open up and adb shell
With your phone booted, type the following command
s:
Code:
adb root
This will start ADB as root, or notify if it is already running as root.
Code:
adb remount
This will mount the system partition (/system) as writable, allowing the following
Code:
adb push flash_image /system/bin
This will send the flash_image script into the /system/bin, so we can use it from within the shell
Code:
adb shell chmod 0755 /system/bin/flash_image
Finally, change the permissions of the script to allow it to perform the desired action.
Now that the script is installed, we are ready to proceed with flashing the custom recovery, saved on the root of the SD card earlier:
Code:
adb shell flash_image recovery /sdcard/recovery.img
P.S. If you want i can post here method by flashing original 1.6 ADP Rom via fastboot (but as i think it is on htc dev web... But i can post here cut version of this - coz original version have many not needed things.)
Credits:
Cyanogen
all xda cool ppls
ANtiHazarD

hey ANtiHazarD i have a desire so im not sure if this is suppose to work but all 3 methods fail for me, any advice, thanks in advance

Nice steps! man hope this gets a good stick or added to the rom bible, you do know though fastboot method is a common way to flash recovery

ilostchild said:
Nice steps! man hope this gets a good stick or added to the rom bible, you do know though fastboot method is a common way to flash recovery
Click to expand...
Click to collapse
That's what I was thinking... Seems almost pointless for a guide since there's instructions how to fastboot on every recovery thread.
Either way, nicely written guide. Someone will probably find this useful.

pablo34 said:
hey ANtiHazarD i have a desire so im not sure if this is suppose to work but all 3 methods fail for me, any advice, thanks in advance
Click to expand...
Click to collapse
With a desire this is quite different, as it has an activated nand flash protection (s-on), so no fastboot flash recovery here. Although this should prevent you from not having a recovery at all...
* note: I don't have a desire (yet) so this is speculation *
Best is probably something similar to this http://forum.xda-developers.com/showthread.php?t=750852
I guess if you get the correct PB99IMG.zip for exactly your device/brand you will not need a goldcard, so don't follow the howto blindly (it is for the newer SLCD versions, but the basics will still be applicable to AMOLED devices). Best would be a PB99IMG.zip that still has a hboot version < 0.92, otherwise you will need to downgrade to root. If you already have 0.92, then just take the newest image, as older ones are normally not flashable.
After step 7 of the howto, you are either done, or you will need to find instructions to downgrade if you want to root.
As soon as you have a working system, with a 0.8* hboot you can just use unrevoked to root and flash a custom recovery.
Enough OT... @ANtiHazarD: Very useful overview. Thanks.

WAY WAY WAY more complicated than it should be...
It is a simple matter of:
fastboot flash recovery recovery.img
Done.

lbcoder said:
It is a simple matter of:
fastboot flash recovery recovery.img
Done.
Click to expand...
Click to collapse
Its not quite that simple,
1) if eng spl use fastboot instructions from RA recovery post (fastboot flash recovery recovery.img)
2) if older stock spl with fastboot ruu modes (1.33.000*) where the * is

lbcoder said:
WAY WAY WAY more complicated than it should be...
It is a simple matter of:
fastboot flash recovery recovery.img
Done.
Click to expand...
Click to collapse
maybe so
but i want to post here ALL known methods thats why so much text is here
why? coz it was a trouble and the method with
fastboot flash recovery recovery.img
not working! thats why - all ways is here.
(all pre-info into 1st post in the top)

pablo34 said:
hey ANtiHazarD i have a desire so im not sure if this is suppose to work but all 3 methods fail for me, any advice, thanks in advance
Click to expand...
Click to collapse
oh... i want to give to you some advice, but don't know what exact. because i don't have desire at my hands... and can't test.
so... thats why only - sorry
maybe there is some guide in the same way in desire section?
p.s. and thanks one more time to ezterry for old support

Can you please help me,
I have stuck here with the G1 phone,
it starts up and stucks on the G! logo.
I can get into fastboot bet have the same problem :
writing 'recovery'... INFOsignature checking...
FAILED <remote: signature verigy fail>
I get into fastboot with thre android logos on skates,
even tried to restore nandroid using fastboot but I get the same error? could you help me out?
I have HTC DREAM with 1.33.0013d and radio 2.22.27.08
I am really frustrated,
I tried all you gave up here but none worked for me.

Also when I try to get into recovery I see a G1 logo with a fastboot usb written on top left in red.

behzadbayat said:
Can you please help me,
I have stuck here with the G1 phone,
it starts up and stucks on the G! logo.
I can get into fastboot bet have the same problem :
writing 'recovery'... INFOsignature checking...
FAILED
I get into fastboot with thre android logos on skates,
even tried to restore nandroid using fastboot but I get the same error? could you help me out?
I have HTC DREAM with 1.33.0013d and radio 2.22.27.08
I am really frustrated,
I tried all you gave up here but none worked for me.
Click to expand...
Click to collapse
Did you read everything before you flashed the 1.33.0013d SPL?
If yes, you would have noticed, that this SPL is not able to flash a recovery or radio using fastboot. You have to flash the orange-...nbh file to get back a full engineering SPL, but you will loose everything you have installed on the phone ...
Send from my G1 with HTCClay's UNOFFICIAL Superfly 1.6 D/S ADS using XDA App

i don't know about this spl, but all what you can do (what i know) you can use this method which named in prev. post. with RC29 or RC7 stock firmware *.nbh
after flashing all data, radio, recovery will be reflashed by a stock data. All must be fine after this... i hope
ezterry can give for your advanced advice, may be

ANtiHazarD said:
i don't know about this spl, but all what you can do (what i know) you can use this method which named in prev. post. with RC29 or RC7 stock firmware *.nbh
after flashing all data, radio, recovery will be reflashed by a stock data. All must be fine after this... i hope
ezterry can give for your advanced advice, may be
Click to expand...
Click to collapse
Don't use RC29.. its once of the most annoying NBH files to need to re-root for the dream.
If you have 1.33.0013d note the orange.nbh posted on the new radio OP post: here
ezterry said:
If you find yourself stuck without recovery!!
Dream
1) Download: orange-1.58.73.2.nbh (MD5: aca4dee0c1ece7e9773f2ecbdfbba7c0) (mirror)
2) enter fastboot and run 'fastboot flash nbh orange-1.58.73.2.nbh'
3) wait for the entire nbh to flash
4) boot into the bootloader again (it will be an engineering SPL 1.42.2000)
5) You can now re-flash the radio/hboot/recovery via fastboot that you wish to have installed.
​
Click to expand...
Click to collapse
basically if you intend to still use the new radio; after installing 1.58.73.2 you can reboot-bootloader; and use my fastboot installation steps at the top of that post
You can do this without a goldcard because I bypass various checks in 1.33.0013d
(It will let you install any other signed NBH but that will still wipe the phone completely; and if it fails to flash cleanly it will leave you without an engineering SPL thus make it harder to make android go again)

hey i tried to flash the MTD too and now i keep getting "E:cant open CACHE:recovery/log" when i go into recovery . I can flash roms but when i reboot my phone my phone stays in the G1 Logo . and when it does make it to the rom i can not get my market or gapps no matter what i do . please help me guys .
EDIT: theres times when i get past the g1 logo but itll just stay on the roms boot screen forever until the phone dies . does anyone have any ideas ?

try to 'fastboot wipe system -w'
after
wipe all (data/cache, cache, dalvik, ext, stats)
and move log to sd

ANtiHazarD said:
try to 'fastboot wipe system -w'
after
wipe all (data/cache, cache, dalvik, ext, stats)
and move log to sd
Click to expand...
Click to collapse
ive never really done fastboot tho . is there any other way ?

breezy169 said:
ive never really done fastboot tho . is there any other way ?
Click to expand...
Click to collapse
It's worth learning to use it ...
Really, especially when using the 14MB-hack or CustomMTD and it's not so difficult. There should be a tutorial on adb and fastboot here in the forum.

AndDiSa said:
It's worth learning to use it ...
Really, especially when using the 14MB-hack or CustomMTD and it's not so difficult. There should be a tutorial on adb and fastboot here in the forum.
Click to expand...
Click to collapse
i agree but i just finished reading the forum that shows how to do it but it sounds so complicated .
EDIT: i ended up flashing another recovery and that solved the problem . that was the weirdest thinq ive ever seen . and honestly i thought i bricked my phone but it was a simpleee fix lol . thanks for the advice tho

I am hanging at booting while trying to do this any ideas?

[Q] MT3G bad recovery flash, stuck

Hi,
I have a mt3g, TMobile. CyanogenMod 6.1.0, ClockWork recovery. Used ROM Managed to flash Amon Ra recovery, since I needed to re-calibrate the battery. It asked me to pick phone model, picked Ion/MyTouch 3G. After reboot:
- Stuck on splash screen if I try to go to recovery
- When booted up - a bunch of force closures, keeps playing a ringtone over and over and...
Everything I tried to do through ROM Manager didn't help.
Any help is appreciated.
Thanks.

truss said:
Hi,
I have a mt3g, TMobile. CyanogenMod 6.1.0, ClockWork recovery. Used ROM Managed to flash Amon Ra recovery, since I needed to re-calibrate the battery. It asked me to pick phone model, picked Ion/MyTouch 3G. After reboot:
- Stuck on splash screen if I try to go to recovery
- When booted up - a bunch of force closures, keeps playing a ringtone over and over and...
Everything I tried to do through ROM Manager didn't help.
Any help is appreciated.
Thanks.
Click to expand...
Click to collapse
Do you still have root? If you can get into ROM manager, reflash clockwork recovery, then wipe cache, dalvik, and run a fix permissions. That should get you back up and running long enough to try again to flash amon ra.
Not sure if the oem spl will let you fastboot flash a new recovery but that's your most reliable bet.
It sounds like it might be time to do a full wipe and reflash anyway. Have you heard of Ohsaka's SuperWipe?

I tried reflashing Clockwork through ROM Manager. It says "root granted", "clockwork flashed" immediately. When I try to boot into recovery - I get stuck on green MyTouch screen forever. Battery pull is the only way out.
I guess the problem is that I cannot get to any recovery anymore. Any ideas?

Do you have fastboot. If so you can flash recovery from there.

kodjo said:
Do you have fastboot. If so you can flash recovery from there.
Click to expand...
Click to collapse
Can I do that through adb shell? I don't think I built fastboot.

truss said:
Can I do that through adb shell? I don't think I built fastboot.
Click to expand...
Click to collapse
Fastboot is a different mode. Boot into hboot (vol down + power I think) and then select fasboot from the menu. Then plug into computer. From a command prompt type:
fastboot flash recovery recovery.img
The recovery needs to be in your tools or platform-tools folder and named recovery.img for this to work. Otherwise it would be fastboot flash recovery c:\path\to\recoveryfilename.img. Make sense?
Link to Amon_Ra Recovery 1.7 for MT3G 32B. http://www.filefactory.com/file/caa48b0/n/recovery-RA-sapphire-v1.7.0G-cyan.img
Otherwise keep trying with ROM Manager. Might take a few attempts to get recovery to stick, even temporarily. It did for me. Flash once then flash again. There's also an option in ROM Manager settings to erase recovery prior to flashing. Check that and see if it helps.

Phateless said:
Fastboot is a different mode. Boot into hboot (vol down + power I think) and then select fasboot from the menu. Then plug into computer. From a command prompt type:
fastboot flash recovery recovery.img
The recovery needs to be in your tools or platform-tools folder and named recovery.img for this to work. Otherwise it would be fastboot flash recovery c:\path\to\recoveryfilename.img. Make sense?
Link to Amon_Ra Recovery 1.7 for MT3G 32B.
Otherwise keep trying with ROM Manager. Might take a few attempts to get recovery to stick, even temporarily. It did for me. Flash once then flash again. There's also an option in ROM Manager settings to erase recovery prior to flashing. Check that and see if it helps.
Click to expand...
Click to collapse
I appreciate your help.
When I try to flash recovery.img, I get this: error: cannot load `recovery.img`
When I try running fastboot with absolute path, I get: FAILED (remote: not allow). Is there a way to fix this?
Tried flashing through ROM Manager many times - no result.

truss said:
I appreciate your help.
When I try to flash recovery.img, I get this: error: cannot load `recovery.img`
When I try running fastboot with absolute path, I get: FAILED (remote: not allow). Is there a way to fix this?
Tried flashing through ROM Manager many times - no result.
Click to expand...
Click to collapse
Interesting... Where are you trying to flash recovery.img and getting that error? What method are you using? Are you sure you have the path to recovery.img correct?
As for fastboot, you need an S-OFF/engineering spl so I guess that's out.
What happens if you use Terminal Emulator?
su
flash_image recovery sdcard/recovery.img
Does that work? Keep at it, you have root so not all is lost. Eventually you will get there.
EDIT - make sure you rename the recovery to "recovery.img" and leave it on the root of your sdcard for my italicized instructions above to work. What ROM are you running? If flash_image doesn't work I need to know which version of the binary to give you.

Phateless said:
Interesting... Where are you trying to flash recovery.img and getting that error? What method are you using? Are you sure you have the path to recovery.img correct?
As for fastboot, you need an S-OFF/engineering spl so I guess that's out.
What happens if you use Terminal Emulator?
su
flash_image recovery sdcard/recovery.img
Does that work? Keep at it, you have root so not all is lost. Eventually you will get there.
EDIT - make sure you rename the recovery to "recovery.img" and leave it on the root of your sdcard for my italicized instructions above to work. What ROM are you running? If flash_image doesn't work I need to know which version of the binary to give you.
Click to expand...
Click to collapse
Thank you very much.
Running flash_image recovery command using adb shell a few times did the trick. I was able to boot to Amon RA recovery, wipe and flash CyanogenMod 6.1.0.

truss said:
Thank you very much.
Running flash_image recovery command using adb shell a few times did the trick. I was able to boot to Amon RA recovery, wipe and flash CyanogenMod 6.1.0.
Click to expand...
Click to collapse
Nice! Glad you got it sorted out.

Help ... I cannot use the recovery image to restore image now....

For example
http://forum.xda-developers.com/wiki/index.php?title=Dell_Streak
I use the recovery apps to resotre official ROM .... it always reboot halfway .... and enter into emergency mode....
Any help ???
Now I can only use other 3rd party recovery such as Recovery-v0.3.2.8-beta ...and restore Zip files format.....

Have you tried flashing the recovery.img and the corressponding rom image?
You can get these from the wiki
If all else fails, and you cannot recover using fastboot etc, then try QDLTool again from the wiki

(InsertNameHere) said:
Have you tried flashing the recovery.img and the corressponding rom image?
You can get these from the wiki
If all else fails, and you cannot recover using fastboot etc, then try QDLTool again from the wiki
Click to expand...
Click to collapse
Yes I did ......
Ok will try .............

trichard said:
Yes I did ......
Ok will try .............
Click to expand...
Click to collapse
Yes you did WHAT?
Normally installing stock ROM will cure most things unless you have internal issues.
Flash stock recovery.img for the stock ROM you want to get back to... I would suggest 360. You should already have downloaded the stock ROM update.pkg file that corresponds to the stock recovery.img you flashed in fastboot. Make sure you don't have any other files on the root of your SD that conflict with you update.pkg and MOST importantly, make sure it's named "update.pkg"
Boot into recovery and choose option 2 to update. IF it gets stuck (now this first boot after installing stock ROM may take 20 minutes or so), then pull the battery, boot into recovery, and choose to do a factory reset again

Hi guys
I'm hoping somebody could please help me with my somewhat-bricked device..bricked in the sense that I don't know what to do with it. (i'm a noob to this). I've tried installing a custom rom and completely screwed up my dell streak 5.
So the phone doesn't boot anymore and just takes me to the option to install update.pkg off the sd card. I added the file along with recovery.img to the sd card.
360 17397 00 May 31, 2011 PKG Recovery Hash Latest Retail rom
My problem is that I cannot for whatever reason get Flashboot to work in order to flash the recovery.img first. under device manager you see android phone/android adb interface but still can't manage the connection to use cmd prompt/fastboot.
Is there any other way of getting the recovery.img to work without fastboot/thru the sd card. I have no idea what i'm doing anymore. I've tried installing the update.pkg but after installation it just stays on the dell logo loading screen forever.
PLEASE help if you can.

Try QDLTool

cdzo72 said:
Yes you did WHAT?
Normally installing stock ROM will cure most things unless you have internal issues.
Flash stock recovery.img for the stock ROM you want to get back to... I would suggest 360. You should already have downloaded the stock ROM update.pkg file that corresponds to the stock recovery.img you flashed in fastboot. Make sure you don't have any other files on the root of your SD that conflict with you update.pkg and MOST importantly, make sure it's named "update.pkg"
Boot into recovery and choose option 2 to update. IF it gets stuck (now this first boot after installing stock ROM may take 20 minutes or so), then pull the battery, boot into recovery, and choose to do a factory reset again
Click to expand...
Click to collapse
Hi
Yes I did all these step .... take the recovery img and flash using fastboot ... and restore the full ROM image .... still half way .... reboot ... and into recover mode.... and then next rstore will have error ........

(InsertNameHere) said:
Have you tried flashing the recovery.img and the corressponding rom image?
You can get these from the wiki
If all else fails, and you cannot recover using fastboot etc, then try QDLTool again from the wiki
Click to expand...
Click to collapse
How to use Fast boot to restore complete image ROM ?
Command line is ?

trichard said:
How to use Fast boot to restore complete image ROM ?
Command line is ?
Click to expand...
Click to collapse
once in fastboot your command line is
fastboot flash recovery recovery.img (will take just about 3 or 4 seconds then type)
fastboot reboot (it will begin to reboot and you should press the volume up and down keys to get into recovery, you should already have the package on your sd card, choose option 2 to update... if it hangs, you don't have to flash recovery again, just boot into recovery and try a factory reset, if it hangs, well flash the ROM again

cdzo72 said:
once in fastboot your command line is
fastboot flash recovery recovery.img (will take just about 3 or 4 seconds then type)
fastboot reboot (it will begin to reboot and you should press the volume up and down keys to get into recovery, you should already have the package on your sd card, choose option 2 to update... if it hangs, you don't have to flash recovery again, just boot into recovery and try a factory reset, if it hangs, well flash the ROM again
Click to expand...
Click to collapse
No problem to get the recovery.img flash in FastBoot ...
It is getting the 150MB .pkg to install ....
Can FastBoot flash .pkg ?

Camera key don´t work
cdzo72 said:
Yes you did WHAT?
Normally installing stock ROM will cure most things unless you have internal issues.
Flash stock recovery.img for the stock ROM you want to get back to... I would suggest 360. You should already have downloaded the stock ROM update.pkg file that corresponds to the stock recovery.img you flashed in fastboot. Make sure you don't have any other files on the root of your SD that conflict with you update.pkg and MOST importantly, make sure it's named "update.pkg"
Boot into recovery and choose option 2 to update. IF it gets stuck (now this first boot after installing stock ROM may take 20 minutes or so), then pull the battery, boot into recovery, and choose to do a factory reset again
Click to expand...
Click to collapse
hey buddy, when I enter the recovey mode, and will install a new rom or another option, the camera button does not work. What can I do?

[Q] Bootloop on rebooting into recovery?

I rooted through cyanogenmod method, then unrooted (went back to stock 2.2.1) with the stock P15100.zip. I had another hardware issue with my phone (microphone failing) and thought it could be software. The mic was still broken and I wanted to root again so went through cyanogen method again flashing CWM. I was able to reboot once into recovery to flash synth's ICS. When I try to fully reboot, then reboot into recovery again, I got bootloop for a minute, then eventually booted into the rom. I tried flashing 4ext and same issue. I tried flashing CWM again from app and still have the issue. I'm just guessing recovery is corrupted and it needs to be formatted and re-flashed? Anyone know how to format recovery via adb and then push cwm or 4ext?
Any help much is appreciated.

You can flash a recovery through terminal emulator. As I recall, the commands are:
su
flash_image recovery recoveryname.img
Sounds like you might be having bigger issues, though. I hope your recovery partition isn't going kaput.
Jack_R1 might have an idea.

Man, Jack_R1 is still around these parts? But as for OP, definitely sounds like your recovery is corrupt. What you want to do is if you have any fastboot/ADB knowledge is you're going to want to download the recovery.img of your choice, name it "recovery.img" then place it in your ADB folder, plug your phone in in Fastboot mode and then type in the following commands:
Code:
Fastboot devices
it should show you a number followed by "fastboot" after this type
Code:
fastboot delete recovery
it should spew out how long it took followed by "recovery deleted" or something like that.
lastly you're going to flash the recovery that you downloaded. Type
Code:
fastboot flash recovery recovery.img
That should do it! PM me if you need any other help

Yes, I still visit here
OP, what phone do you have? You're writing a wrong name for PD15IMG.
In any case, if you indeed have PD15IMG - find "root for S-OFF users" thread in Development, get the PD15IMG with CWM from there, flash it just like you flashed return-to-stock package, and boot into recovery. If it doesn't work - it means that it's not the recovery that's corrupted.
And I suspect that you're just not understanding correctly what your phone does, and/or not actually booting into recovery.

Nicgraner said:
Man, Jack_R1 is still around these parts? But as for OP, definitely sounds like your recovery is corrupt. What you want to do is if you have any fastboot/ADB knowledge is you're going to want to download the recovery.img of your choice, name it "recovery.img" then place it in your ADB folder, plug your phone in in Fastboot mode and then type in the following commands:
Code:
Fastboot devices
it should show you a number followed by "fastboot" after this type
Code:
fastboot delete recovery
it should spew out how long it took followed by "recovery deleted" or something like that.
lastly you're going to flash the recovery that you downloaded. Type
Code:
fastboot flash recovery recovery.img
That should do it! PM me if you need any other help
Click to expand...
Click to collapse
I have used adb a bit (for root with cyanogen method). I'm guessing that the delete command will reformat the recovery partition? I'll give this a go when I get home and get back to ya. Thanks for the reply! Is there a way to download the 4ext recovery img file?
Edit:
I downloaded the CWM touch img and connected to the phone in fastboot. Was able to follow your instructions, but the command is erase not delete. When I put in the delete command it came up with the instructions and was able to figure it out. Flashed recovery and I can now boot into recovery every time from fastboot, terminal, adb, and from power prompt in rom! BOOYAH! Thanks a ton!

Jack_R1 said:
Yes, I still visit here
OP, what phone do you have? You're writing a wrong name for PD15IMG.
In any case, if you indeed have PD15IMG - find "root for S-OFF users" thread in Development, get the PD15IMG with CWM from there, flash it just like you flashed return-to-stock package, and boot into recovery. If it doesn't work - it means that it's not the recovery that's corrupted.
And I suspect that you're just not understanding correctly what your phone does, and/or not actually booting into recovery.
Click to expand...
Click to collapse
Hey Jack,
I have HTC Glacier. Was a typo for the PD15IMG name. I think I have a decent understanding of the phone, and most likely have a corrupted recovery partition. Seems that instead of just flashing a recovery over a recovery, I may need to reformat the partition and then flash? I'll try flashing the file you suggest and report back. If it is not the recovery that is corrupted, what else could be the issue? Possibly an issue with the bootloader not allowing the phone to boot into recovery? Thanks for the reply.

Flashing recovery isn't copying a file. When you flash IMG through bootloader, it is flashed just like what it is - a complete image. Formatting the partition doesn't do anything, since it has no "format" - the image flashed by the bootloader contains both the structure and the data, just like a CD/DVD image does, for example.
The possible options I can think of are:
1) Your recovery partition is physically bad - unlikely.
2) Your bootloader is corrupted - could possibly lead to you being unable to enter recovery.
3) Something that prevents your phone from entering recovery - i.e. a stuck button or something - or you're doing it wrong. I'm afraid that what you're describing as "phone bootloops for a minute and then boots a ROM" isn't really a bootloop - because these phones can't get out of bootloop on their own, if booting failed once - it'll fail always. Logcat can confirm this. I believe it's just the ROM that's booting normally when you try to enter recovery, so, in this case, since you didn't specify how exactly you're trying to enter recovery - it seems like you're either doing it wrong, or when you try to enter recovery you're not getting there.
To help people help you, please write down the exact way you're using when trying to enter recovery, and if you know more than one way - try them all (from bootloader, by adb reboot recovery, directly booting without flashing by "fastboot boot", etc). And post your HBOOT version.

Jack_R1 said:
Flashing recovery isn't copying a file. When you flash IMG through bootloader, it is flashed just like what it is - a complete image. Formatting the partition doesn't do anything, since it has no "format" - the image flashed by the bootloader contains both the structure and the data, just like a CD/DVD image does, for example.
The possible options I can think of are:
1) Your recovery partition is physically bad - unlikely.
2) Your bootloader is corrupted - could possibly lead to you being unable to enter recovery.
3) Something that prevents your phone from entering recovery - i.e. a stuck button or something - or you're doing it wrong. I'm afraid that what you're describing as "phone bootloops for a minute and then boots a ROM" isn't really a bootloop - because these phones can't get out of bootloop on their own, if booting failed once - it'll fail always. Logcat can confirm this. I believe it's just the ROM that's booting normally when you try to enter recovery, so, in this case, since you didn't specify how exactly you're trying to enter recovery - it seems like you're either doing it wrong, or when you try to enter recovery you're not getting there.
To help people help you, please write down the exact way you're using when trying to enter recovery, and if you know more than one way - try them all (from bootloader, by adb reboot recovery, directly booting without flashing by "fastboot boot", etc). And post your HBOOT version.
Click to expand...
Click to collapse
Sorry if I wasn't more descriptive. I really appreciate your help and everything you have done for this community. Seems the recovery was corrupted by the 4ext app. I was able to extract the recovery.img from the 4ext download and was able to flash it via fastboot. Everything boots properly now. HBoot is 0.85.2007 FYI. Thanks again!

Warning - XT1060 Blur_Version.212.55.26 blocks custom recoveries

Exactly as the title says ... after flashing this update, even if unlocked, you can no longer flash a custom recovery.
Fastboot will show a successful flash, e.g. :
mfastboot.exe flash recovery twrp-2.8.6.0-ghost.img
sending 'recovery' (9488 KB)...
OKAY [ 0.849s]
writing 'recovery'...
OKAY [ 0.969s]
finished. total time: 1.819s
Click to expand...
Click to collapse
But when you try to boot recovery, it's stock recovery.
This makes any attempt to flash a rom, regain root, etc. impossible.

And you are booting straight to recovery after flashing via volume down and then volume up to select not the power button?

_litz said:
Exactly as the title says ... after flashing this update, even if unlocked, you can no longer flash a custom recovery.
Fastboot will show a successful flash, e.g. :
But when you try to boot recovery, it's stock recovery.
This makes any attempt to flash a rom, regain root, etc. impossible.
Click to expand...
Click to collapse
After you flash TWRP, at the command prompt type:
fastboot reboot-bootloader
I can't remember where I read it but some people said they had to do that to get the custom recovery to stick.
THEN unplug your device from your computer and reboot into recovery by scrolling down with the volume down button to highlight recovery and then hitting the volume up button to select recovery.

Ok, figured this out ...
(was able to back down to the original 4.4.4 w/rsd-lite and regain TWRP ... to develop this process)
So ... the following can be done to upgrade to this new version, and retain TWRP (plus you have the new recovery later on for 5.1 when it comes along ...)
First, the presumption here is you are unlocked. If you are not, none of this will work.
Also, you will need RSD-Lite installed and operational.
Download :
https://dl.dropboxusercontent.com/u...RIZON_4.4.4_KXA21.12-L1.26-3_cid2_1FF.xml.zip
https://dl.dropboxusercontent.com/u...4.4.4_KXA21.12-L1.26-3/twrp-2.8.6.0-ghost.img
https://dl.dropboxusercontent.com/u/22067374/GHOST_VERIZON_4.4.4_KXA21.12-L1.26-3/servicefile.xml
Unpack the GHOST zip file, and overwrite the "servicefile.xml" in the unpacked folder w/the one you downloaded, then copy the twrp .img in there.
Fire up RSD-Lite, put your phone in fastboot, and apply this update by loading the servicefile.xml as the update.
It will update everything, installing the TWRP instead of the new stock recovery.
Note: you can delete the twrp line in servicefile.xml if you wish to retain your existing custom recovery.
When done, you should reboot, update, and be up and running with the new 4.4.4 and TWRP ... so easy path back to root via TWRP.

_litz said:
Ok, figured this out ...
Click to expand...
Click to collapse
I think all that needs to happen is after you flash TWRP - you don't boot into recovery. Instead, reboot into bootloader mode. This has been a problem from the beginning for some people with their MX13's and not a new thing. I don't think it has anything to do with the update. Some people have to reboot into bootloader after flashing TWRP in order to get it to stick for some reason.

@_litz Please understand that @JulesJam is correct... the proper way to flash a recovery is as follows...
Start the phone to the Fastboot AP/Bootoader menu
using moto's fastboot (aka mfastboot) exectue the following...
mfastboot flash recovery RecoveryYouWishToFlash.img
mfastboot reboot-bootloader
Then use the volume/power keys to enter recovery.
Once in the recovery, it is safe to Reboot the phone normally.
that mfastboot reboot-bootloader step has been crucial for getting the newly flashed recovery (3rd party OR Stock!) to "stick" on the phone.
Flashing with RSDLite is over kill.

You'd think that would be the case, right?
Except those EXACT STEPS ... didn't work.
If you attempted to boot into recovery directly from the bootloader, it rebooted the phone, which booted the OS.

_litz said:
You'd think that would be the case, right?
Except those EXACT STEPS ... didn't work.
If you attempted to boot into recovery directly from the bootloader, it rebooted the phone, which booted the OS.
Click to expand...
Click to collapse
And you used volume up to enter recovery after flashing twrp? That is the most common problem I see.

_litz said:
You'd think that would be the case, right?
Except those EXACT STEPS ... didn't work.
If you attempted to boot into recovery directly from the bootloader, it rebooted the phone, which booted the OS.
Click to expand...
Click to collapse
That is because you are pressing the power button when you should be pressing the volume up button.

Yep ... ain't my first rodeo ....
It flat out refused to take recovery.
I had to back it back down to the old 4.4.4 version, reflash TWRP, then I simply applied the whole RSD package (sans recovery) to re-upgrade it to the new 4.4.4.
Worked like a charm.
(Plus it gave me a chance to extract the fxz from the moto manager app)

Travisdroidx2 said:
And you used volume up to enter recovery after flashing twrp? That is the most common problem I see.
Click to expand...
Click to collapse
yes, that is what is happening.

See above ... this isn't my first time at this. Was not working as described.

_litz said:
See above ... this isn't my first time at this. Was not working as described.
Click to expand...
Click to collapse
Was not trying to insult your knowledge. That is a very common problem that many do. So I had to ask.

_litz said:
See above ... this isn't my first time at this. Was not working as described.
Click to expand...
Click to collapse
You needed to reboot into bootloader by typing fastboot reboot-bootloader after your flashed TWRP. THEN disconnect your phone from your computer and boot into recovery by using the volume down to highlight recovery and volume up to select recovery.
If you follow those instructions, you will flash TWRP fine. No need to go through that long drawn out process you came up with.

Probably should rename or delete this thread, since its fairly misleading.

Check in the /system partition for a file named recovery-from-boot.p or something similar. If that file is there it will reflash the stock recovery when you reboot, and I've seen it reflash when booting into recovery.

I just used the TWRP manager app from the Play store after reverting to stock recovery and installing the OTA. It worked perfectly the first time.
https://play.google.com/store/apps/details?id=com.jmz.soft.twrpmanager

_litz said:
You'd think that would be the case, right?
Except those EXACT STEPS ... didn't work.
If you attempted to boot into recovery directly from the bootloader, it rebooted the phone, which booted the OS.
Click to expand...
Click to collapse
I'm curious as to what is different.. because the other day after flashing stock recovery back on my phone, taking the update to 212.166.3 KXA21.12-L1.26-3 which Verizon just pushed, I used those EXACT STEPS to put TWRP back on my phone and had no problems.

Beats me ... for me, it didn't work ...
So after I got things back onto the old 4.4.4 version, I put together the FXZ with the modified xml file, and simply re-updated, applying both the update, and TWRP, all in one go.
anyone else on old 4.4.4 can do the same thing if they wish, which was why I posted the links and the instructions.

not to bump this thread, but I had zero issues going from stock with 212.55.26 ota update installed and flashing twrp. it just worked like normal.
i would agree with @superkeest seems like this thread should get renamed.