I am using ATT htc one with developer edition OS. And I learned from the forum there was new radio released be att. So I tried to flash it.
However, since I want OTA work, I chose to stay with the stock recovery and therefore I cannot flash it via custom recovery like a lot of threads in here talking about. I searched and only found the procedure from other htc product's forum as below.
1) adb reboot-bootloader
2) fastboot flash radio radio.img
But "fastboot flash radio radio.img" has no response at all.
I got the img from http://forum.xda-developers.com/showthread.php?t=232556. It was extracted from Radio_4A.16.3250.24_10.38.1150.03.zip.
My current build is 1.29.1540.17, while baseband is still 4A.14.3250.13, which is the original. And Ive already s-offed and unlocked bootloader.
Any help about flashing? Thanks in advance.
lowirve said:
I am using ATT htc one with developer edition OS. And I learned from the forum there was new radio released be att. So I tried to flash it.
However, since I want OTA work, I chose to stay with the stock recovery and therefore I cannot flash it via custom recovery like a lot of threads in here talking about. I searched and only found the procedure from other htc product's forum as below.
1) adb reboot-bootloader
2) fastboot flash radio radio.img
But "fastboot flash radio radio.img" has no response at all.
I got the img from http://forum.xda-developers.com/showthread.php?t=232556. It was extracted from Radio_4A.16.3250.24_10.38.1150.03.zip.
My current build is 1.29.1540.17, while baseband is still 4A.14.3250.13, which is the original. And Ive already s-offed and unlocked bootloader.
Any help about flashing? Thanks in advance.
Click to expand...
Click to collapse
Did you try the fastboot flash command in RUU mode? Fastboot oem reboot RUU. This is just a guess on my part, but that's the mode for firmware flashing, so guessing it might work for the radio too.
In order for a radio to be flashed in fastboot it has to be packaged in a zip file that rubootRUU mode understands. It's easier for most people to just flash in recovery
gunnyman said:
In order for a radio to be flashed in fastboot it has to be packaged in a zip file that rubootRUU mode understands. It's easier for most people to just flash in recovery
Click to expand...
Click to collapse
Thanks, gunny. I had an idea that was how it worked, I appreciate the knowledge! Is the OP out of luck then? Is there any way for him to flash a radio if he's on stock recovery?
It's easy enough to flash custom recovery then radio then put stock recovery back on.
gunnyman said:
It's easy enough to flash custom recovery then radio then put stock recovery back on.
Click to expand...
Click to collapse
Oh, so like the normal way the rest of us did it lol! Thanks, gunny!
Thank you all. Looks like the only choice for me now is stop being lazy and use custom recovery, then flash it back to stock.
In the first place, I thought there was an easy method to use fastboot like other htc products.
gunnyman said:
In order for a radio to be flashed in fastboot it has to be packaged in a zip file that rubootRUU mode understands. It's easier for most people to just flash in recovery
Click to expand...
Click to collapse
So I guess the zip file I got was prepared for recovery use only, right? I have been comparing it with firmware zip file found in RUU flashing thread (http://forum.xda-developers.com/showthread.php?t=2365506&highlight=flash+latest+radio+fastboot). RUU flash's file includes android-info.txt to enable fastboot read the image inside zip file.
lowirve said:
So I guess the zip file I got was prepared for recovery use only, right? I have been comparing it with firmware zip file found in RUU flashing thread (http://forum.xda-developers.com/showthread.php?t=2365506&highlight=flash+latest+radio+fastboot). RUU flash's file includes android-info.txt to enable fastboot read the image inside zip file.
Click to expand...
Click to collapse
I forgot about this file that was posted in AT&T Developer Forum, it's a packaged firmware file with only radio updates. The post also contains the latest firmware that includes newest touch driver. Newest touch driver doesn't work with 4.1.2 ROMs and older recoveries.
http://forum.xda-developers.com/showthread.php?p=44260480
Sent from my HTC One using xda app-developers app
ilal2ielli said:
I forgot about this file that was posted in AT&T Developer Forum, it's a packaged firmware file with only radio updates. The post also contains the latest firmware that includes newest touch driver. Newest touch driver doesn't work with 4.1.2 ROMs and older recoveries.
http://forum.xda-developers.com/showthread.php?p=44260480
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Thanks for the finding:good:. I haven't read it before.
Related
hey guys, I'm using a G1 (HTC Dream). It runs on Cyangoenmod 4.2.15 right now with a radio version that starts with a 1 (I don't know the exact version, the phone is not with me).
I'm trying to flash the 2.22.19.26I radio version by going to "flash zip" option. It goes about half way and tells me that it's having a a verification error. Could it be that I'm doing something wrong?
Try and redownload the radio or use newer radio which is 2.2.23.02 I think
Or do it via fastboot.
ilostchild said:
Try and redownload the radio or use newer radio which is 2.2.23.02 I think
Click to expand...
Click to collapse
is there any harm in updating the radio???? and can we downgrade the radio if somthing goes wrong??
no harm updating radio, and yes if needed to you can go back to the 2.22.26I radio
How can I install it via fastboot? Both .zip files are giving me errors.
Shadowafs8 said:
How can I install it via fastboot? Both .zip files are giving me errors.
Click to expand...
Click to collapse
For fastboot you have to extract the .img file from the zip.
Okay, then what do I do with the radio image?
Shadowafs8 said:
Okay, then what do I do with the radio image?
Click to expand...
Click to collapse
First, as a general precaution for the future, make sure the radio you're trying to flash is compatible with the SPL. The wrong radio/SPL combination can brick your phone. Upgrading from a 1.x to a 2.x isn't a problem, I'm just mentioning it for the future. It would also be a good idea to verify the MD5 checksum of the files you download.
Place the extracted radio.img file in the same directory as the fastboot executable, and once you have verified fastboot connectivity the command to flash the radio is:
fastboot flash radio radio.img
oldnoob said:
First, as a general precaution for the future, make sure the radio you're trying to flash is compatible with the SPL. The wrong radio/SPL combination can brick your phone. Upgrading from a 1.x to a 2.x isn't a problem, I'm just mentioning it for the future. It would also be a good idea to verify the MD5 checksum of the files you download.
Place the extracted radio.img file in the same directory as the fastboot executable, and once you have verified fastboot connectivity the command to flash the radio is:
fastboot flash radio radio.img
Click to expand...
Click to collapse
So any radio version should be fine at this point right? Either one with 2. right?
Also how can I check the MD5?
Shadowafs8 said:
So any radio version should be fine at this point right? Either one with 2. right?
Also how can I check the MD5?
Click to expand...
Click to collapse
As long as we're talking about a t-mobile G1 (or an EBI0 Dream) a 1.x to 2.x radio upgrade should be no problem. Search on Google or Cnet for MD5 utilities, there should be several free ones out there.
Sent from my HTC Dream using XDA App
Alright, I'm trying to install using fastboot, however, my G1 won't go into it. It goes to the multicolor screen and when I press the back button, it just reloads the multicolor screen. The HBoot is 0.95.0000. I installed the 1.3.2003 SPL but I'm still getting the same thing.
Shadowafs8 said:
The HBoot is 0.95.0000. I installed the 1.3.2003 SPL but I'm still getting the same thing.
Click to expand...
Click to collapse
Hboot and SPL are the same thing, so if it's reading 0.95.0000 then 1.3.2003 didn't install and 0.95.0000 doesn't support fastboot. What recovery are you using?
Just remembered something else. Can you connect with ADB after the system is booted? If it works check the stickies at the top of this forum for more specifics, but you should be able to flash from there.
oldnoob said:
Hboot and SPL are the same thing, so if it's reading 0.95.0000 then 1.3.2003 didn't install and 0.95.0000 doesn't support fastboot. What recovery are you using?
Click to expand...
Click to collapse
I have the RA-Sapphire-v1.7.06 recovery. Perhaps the SPL not installing is due to the MTD script I applied here (http://forum.xda-developers.com/showthread.php?p=8002144#post8002144)
It has a USB-MS toggle option could that be used?
Also, it does connect on ADB, I checked the stickies, but I couldn't find anything about flashing the radio via adb, are you sure it should work?
Shadowafs8 said:
I have the RA-Sapphire-v1.7.06 recovery. Perhaps the SPL not installing is due to the MTD script I applied here (http://forum.xda-developers.com/showthread.php?p=8002144#post8002144)
It has a USB-MS toggle option could that be used?
Click to expand...
Click to collapse
Don't know about the MTD script, I use DangerSPL. Good thing you don't since it would brick your phone with the radio you have. One thing that seems strange to me is the RA-Sapphire recovery, that sounds like the Magic/MyTouch recovery not the Dream/G1 version.
Shadowafs8 said:
Also, it does connect on ADB, I checked the stickies, but I couldn't find anything about flashing the radio via adb, are you sure it should work?
Click to expand...
Click to collapse
No, I'm not sure, but since you can't use fastboot it's the other way to access the phone from the PC. Since you have root you should be able to flash the radio by putting the .img file on the SD card and using the flash_image command through the console or telnet.
I see that in the other thread you are being help by ezterry who is one of the most knowledgeable people around here and can give you way better suggestions than I can. Maybe a tongue lashing for cross posting too.
Shadowafs8 said:
I have the RA-Sapphire-v1.7.06 recovery. Perhaps the SPL not installing is due to the MTD script I applied here (http://forum.xda-developers.com/showthread.php?p=8002144#post8002144)
It has a USB-MS toggle option could that be used?
Also, it does connect on ADB, I checked the stickies, but I couldn't find anything about flashing the radio via adb, are you sure it should work?
Click to expand...
Click to collapse
If you applied MTD then don't flash SPL from there. You need to start over, by erasing exiting recovery and reflashing the recovery again.
Well here's the story, someone gave me their phone to root (i'm the official rooter in my city ) and i accidently skipped over a major step, infact a few of them.
1: I unlocked the phone and flashed clockwork touch recovery
2: Did not backup the original non rooted rom
3: Did not S-off the phone
4: Flashed Android Revolution HD
Now No rom is working, IT gets stuck on the white HTC logo. At least tried 2-3 of them. Cyanogen and ARHD to start with. Tried a few RUU but those aren't going through too. Tried extracting rom.zip from the RUU and flashing manually but they dont work.
Attached is an image with the details of the Firmware on the phone and radio atm
I checked the HTC CID and it's 044 ... Any sort of help would be appreciated.
I feel bad for your city where did you get cwm touch recovery?
Have you flashed the boot.img in fastboot?
If flashing the boot doesn't work. Couldn't you just attempt to s-off through fast boot and flash the RUU etc?
Sent from my Incredible S using xda premium
I feel sorry for them too, now that i screwed up, for the first time though
Well my hboot version is 2.01 and it wasn't supported in revolutionary.io 's s-off method. Didnt think it would work any other way. I dont know how to downgrade it to 1.13.
I got my clockwork recovery from http://forum.xda-developers.com/showthread.php?p=14693680 this post. If only i can find the original rom/RUU which i can flash and just reset it to the original factory rom. :| i tried 3-4 of the RUU in the filefactory folder that's listed in the incredible s shipped rom section but none of them work.
Can i change the CID in teh android_info text file in the rom.zip of the RUU ? would that work ? apparently the zip is claimed to be corrupt when i try adding the same file back.
shani248 said:
I feel sorry for them too, now that i screwed up, for the first time though
Well my hboot version is 2.01 and it wasn't supported in revolutionary.io 's s-off method. Didnt think it would work any other way. I dont know how to downgrade it to 1.13.
I got my clockwork recovery from http://forum.xda-developers.com/showthread.php?p=14693680 this post. If only i can find the original rom/RUU which i can flash and just reset it to the original factory rom. :| i tried 3-4 of the RUU in the filefactory folder that's listed in the incredible s shipped rom section but none of them work.
Can i change the CID in teh android_info text file in the rom.zip of the RUU ? would that work ? apparently the zip is claimed to be corrupt when i try adding the same file back.
Click to expand...
Click to collapse
I'll ask again, have you flashed the boot.img in fastboot? The link you provided has no touch recovery in the OP or am I required to read all 29 pages?
If you're using cwm from the OP, you should update. Here's the newest version I know of http://www.clockworkmod.com/rommanager
To your question about flashing an ruu with a modified android_info on an s-on device: no.
You can find what ruu you need by entering the command
Code:
fastboot getvar version-main
the number returned corresponds to the ruu that you should be looking for.
As you are an experienced rooter you probably already know to wipe cache and usually data when you flash a new Rom.
@vizzy how would you gain s-off in fastboot mode?
HTC Incredible S/Vivo cwm-4.0.1.4-vivo.img
md5 : a556a81054cd8cfe623eed5f4b8e518b
this is hte file i posted from the link i shared before. Which exact boot.img are you talking about ?? Also most of my rootings were done with either unrevoked or alpharev which required minimal tweaking . I'm no pro, just try to give it my best
Also the version that the fasboot command gave me was 3.11.707.1. (thanks for that tip, i'll remember it). Going to search for it
Also how can i S-off in hboot or fasboot atm ??
shani248 said:
HTC Incredible S/Vivo cwm-4.0.1.4-vivo.img
md5 : a556a81054cd8cfe623eed5f4b8e518b
this is hte file i posted from the link i shared before. Which exact boot.img are you talking about ?? Also most of my rootings were done with either unrevoked or alpharev which required minimal tweaking . I'm no pro, just try to give it my best
Also the version that the fasboot command gave me was 3.11.707.1. (thanks for that tip, i'll remember it). Going to search for it
Also how can i S-off in hboot or fasboot atm ??
Click to expand...
Click to collapse
Because the phone is s-on, the way you need to flash a custom rom is as follows:
Install zip from sdcard in cwm, then extract the boot.img file from the zip file and flash it in fastboot I.e
Code:
fastboot flash boot boot.img
these steps are included in the newbs guide sticky
THANKS !!!
Nonverbose said:
Because the phone is s-on, the way you need to flash a custom rom is as follows:
Install zip from sdcard in cwm, then extract the boot.img file from the zip file and flash it in fastboot I.e
Code:
fastboot flash boot boot.img
these steps are included in the newbs guide sticky
Click to expand...
Click to collapse
You, sir, are a gentleman, and a hero. I salute you for your help. ! The phone is fixed ! I see what i did wrong there, and thanks alot for helping me with it. I learned something that was quite frankly logical.
Again, thanks !!!!
So like a tard, I went and flashed a ROM for the One wanting a menu button. Unfortunately, this ROM was not specifically for a Sprint HTC One, but for the other One variants. Now my wifi and data are broken, and my phone constantly restarts itself, independent of the ROM I'm using ( I've flashed at least 3 ROMs to confirm this). Is there anything I can do to specifically re-flash the radios/prevent the constant restarting?
Boomchaos said:
So like a tard, I went and flashed a ROM for the One wanting a menu button. Unfortunately, this ROM was not specifically for a Sprint HTC One, but for the other One variants. Now my wifi and data are broken, and my phone constantly restarts itself, independent of the ROM I'm using ( I've flashed at least 3 ROMs to confirm this). Is there anything I can do to specifically re-flash the radios/prevent the constant restarting?
Click to expand...
Click to collapse
you have to flash a boot.img too- you shouldn't flash roms not specific to your phone, you'll brick it
Please read my post here before you brick your phone.
http://forum.xda-developers.com/showthread.php?p=40678263
Aldo101t said:
you have to flash a boot.img too- you shouldn't flash roms not specific to your phone, you'll brick it
Click to expand...
Click to collapse
I flashed viperBoy's stock Sprint ROM and that already had a boot.img in it. Are you saying I should flash that separately?
Boomchaos said:
I flashed viperBoy's stock Sprint ROM and that already had a boot.img in it. Are you saying I should flash that separately?
Click to expand...
Click to collapse
yes, if you are s-on not s-off you do, with s-on even if the rom has a boot image, it will not flash the boot.img you must pull the image boot from the rom zip and flash it via adb sdk tools in fastboot
Aldo101t said:
yes, if you are s-on not s-off you do, with s-on even if the rom has a boot image, it will not flash the boot.img you must pull the image boot from the rom zip and flash it via adb sdk tools in fastboot
Click to expand...
Click to collapse
Is there a particular order in flash the boot.img vs. the main rom? And should I have taken out the boot.img from the ROM before flashing the ROM? As in should the ROM not have the boot.img inside of it when being flashed?
Boomchaos said:
Is there a particular order in flash the boot.img vs. the main rom? And should I have taken out the boot.img from the ROM before flashing the ROM? As in should the ROM not have the boot.img inside of it when being flashed?
Click to expand...
Click to collapse
ROM first, then boot.img.
And no, flash as is or else you'll get errors.
CNexus said:
ROM first, then boot.img.
And no, flash as is or else you'll get errors.
Click to expand...
Click to collapse
Still restarting, and freezing up. Wifi works now though...baby steps haha.
Hi there.
So I wanted to install cyanogenmod on my htc incredible s. So i rooted my phone without big problems. Then I tried to install cyanogenmod through 4ext recovery via zip file. And now all I have is a static white screen. I tried over 10 ruu's that supposed to be installed from pc and phone. I tried another recovery, custom OS, hard reset through recovery and bootloader, goldcard and some other things that I cant even remember. I also tried to lock bootloader, unlock it, reset root etc.
android version before brick was 4.0.4, sense 3.6.
vivo s-on
hboot 2.02.0002
radio 3831.18.00.11_M
Also when i install cm or some other custom OS through 4ext zip install it says OK but when i reload nothing changes.
Help?
Killa_vatt said:
Hi there.
So I wanted to install cyanogenmod on my htc incredible s. So i rooted my phone without big problems. Then I tried to install cyanogenmod through 4ext recovery via zip file. And now all I have is a static white screen. I tried over 10 ruu's that supposed to be installed from pc and phone. I tried another recovery, custom OS, hard reset through recovery and bootloader, goldcard and some other things that I cant even remember. I also tried to lock bootloader, unlock it, reset root etc.
android version before brick was 4.0.4, sense 3.6.
vivo s-on
hboot 2.02.0002
radio 3831.18.00.11_M
Also when i install cm or some other custom OS through 4ext zip install it says OK but when i reload nothing changes.
Help?
Click to expand...
Click to collapse
With an unlocked bootloader 2.02.0002, you need to extract the boot.img from the CM ROM's zip.file and manually flash it in FASTBOOT USB mode.
You cannot simply flash a custom ROM from 4EXT recovery when you only have an unlocked bootloader. There are plenty of sticky threads in this forum that document the procedure you need to follow. You need to read, study and understand before you try modding your phone.
tpbklake said:
With an unlocked bootloader 2.02.0002, you need to extract the boot.img from the CM ROM's zip.file and manually flash it in FASTBOOT USB mode.
You cannot simply flash a custom ROM from 4EXT recovery when you only have an unlocked bootloader. There are plenty of sticky threads in this forum that document the procedure you need to follow. You need to read, study and understand before you try modding your phone.
Click to expand...
Click to collapse
Still stuck at HTC boot screen. Maybe bad cm file?
I readed many guides on tons of sites but all of them says different things =\
Killa_vatt said:
Still stuck at HTC boot screen. Maybe bad cm file?
I readed many guides on tons of sites but all of them says different things =\
Click to expand...
Click to collapse
if the cm.zip is bad; recovery itself tells BAD ZIP
BTW why dont you flash another rom??
there are much better roms than CM!!
try it!!
so that we will know whether the problem is in phone or rom that you are flashing???
prunzzz said:
if the cm.zip is bad; recovery itself tells BAD ZIP
BTW why dont you flash another rom??
there are much better roms than CM!!
try it!!
so that we will know whether the problem is in phone or rom that you are flashing???
Click to expand...
Click to collapse
I have already tried many ways to install many other roms. What will you recommend?
Killa_vatt said:
I have already tried many ways to install many other roms. What will you recommend?
Click to expand...
Click to collapse
what kind of errors did you get when you flashed other roms??
prunzzz said:
what kind of errors did you get when you flashed other roms??
Click to expand...
Click to collapse
If I am flashing from exe file through fastboot I get ERROR [131]: CUSTOMER ID ERROR.
If I use fastboot flash boot boot.img I get no errors but it still stucks on HTC screen.
If I flash using 4ext install zip mode I still get no errors but it stucks.
I also got error that I dont have boot.prop in my system.
I cant remember other errors that I had.
Killa_vatt said:
If I am flashing from exe file through fastboot I get ERROR [131]: CUSTOMER ID ERROR.
If I use fastboot flash boot boot.img I get no errors but it still stucks on HTC screen.
If I flash using 4ext install zip mode I still get no errors but it stucks.
I also got error that I dont have boot.prop in my system.
I cant remember other errors that I had.
Click to expand...
Click to collapse
have you tried flashing through HBOOT??
prunzzz said:
have you tried flashing through HBOOT??
Click to expand...
Click to collapse
That is done by renaming a file to PG98***?
Killa_vatt said:
If I am flashing from exe file through fastboot I get ERROR [131]: CUSTOMER ID ERROR.
If I use fastboot flash boot boot.img I get no errors but it still stucks on HTC screen.
If I flash using 4ext install zip mode I still get no errors but it stucks.
I also got error that I dont have boot.prop in my system.
I cant remember other errors that I had.
Click to expand...
Click to collapse
The ERROR 131 means that you are trying to flash an official RUU for a different carrier/region. You need to create a goldcard in order to successfully flash a RUU.
Why don't you try flashing a custom ROM from recovery and then flash the boot.img file.
tpbklake said:
The ERROR 131 means that you are trying to flash an official RUU for a different carrier/region. You need to create a goldcard in order to successfully flash a RUU.
Why don't you try flashing a custom ROM from recovery and then flash the boot.img file.
Click to expand...
Click to collapse
Ive created a goldcard.
I tried to flash a custom rom-still stuck at whitescreen.
Killa_vatt said:
Ive created a goldcard.
I tried to flash a custom rom-still stuck at whitescreen.
Click to expand...
Click to collapse
OK, after re-reading your posts, here are some additional tips:
When flashing a custom ROM from 4EXT, please make sure you do a full system wipe and then clear both Cache and Dalvik cache before you flash the ROM.
After you flash the ROM, then you need to immediately flash the ROM's boot.img file contained in the zip file using FASTBOOT USB mode.
As for trying to flash 10 different RUU's there ERROR 131 indicates that you have a bad goldcard.
Killa_vatt said:
That is done by renaming a file to PG98***?
Click to expand...
Click to collapse
Hey not PG98!!!!
PG32IMG.zip!!!!!
Try it now
Also consider what tpbklake said
HIT THANKS IF I HELPED YOU
tpbklake said:
When flashing a custom ROM from 4EXT, please make sure you do a full system wipe and then clear both Cache and Dalvik cache before you flash the ROM.
After you flash the ROM, then you need to immediately flash the ROM's boot.img file contained in the zip file using FASTBOOT USB mode.
Click to expand...
Click to collapse
prunzzz said:
Hey not PG98!!!!
PG32IMG.zip!!!!!
Try it now
Click to expand...
Click to collapse
I mean PG32IMG,forgot that.
I fully wiped everything.
I did not flashed rom's boot.img,thanks! Gonna try it later.
tpbklake said:
After you flash the ROM, then you need to immediately flash the ROM's boot.img file contained in the zip file using FASTBOOT USB mode.
Click to expand...
Click to collapse
Thank you very much! I feel dummy now =)
Flashing rom's boot.img fixed all problems. Most of roms works now. Thanked everyone in topic.
Hello, I flashed LOS with my m7 international version. Sadly, Lineage dropped the support. I then flashed back to stock ROM via twrp. However, the stock ROM always prompt me to install the OTA update and I couldn't because I replaced the stock recovery with twrp.
So, my question is can I just revert twrp back to stock recovery with the ROM being untouched. Or do I need to do so like this 100%?
Thanks.
If you can find the correct version of the stock recovery for your current firmware you can fastboot flash that.
Large Hadron said:
If you can find the correct version of the stock recovery for your current firmware you can fastboot flash that.
Click to expand...
Click to collapse
How can I find the stock recovery? My version is: 7.18.708.21
However, I cannot find it on google.com.
please help.
When I typed "HTC One M7 stock recovery" into Google the first result I got was this XDA thread: https://forum.xda-developers.com/showthread.php?t=2545227, so that's where I'd start looking.
As far as I can tell 7.18.708.21 is a HTC Asia HK software version. That thread has a recovery image for 7.18.708.2. I couldn't tell you whether the recovery changed at all between that and 7.18.708.21, so it's possible that that file will do what you want, but I cannot make any promises.
Otherwise you just have to try an RUU, as that guide you linked describes.
Yeah, I also got 7.18.708.2. However, I would not take the risk unless I found the right one. Thanks though.
jasonyellow said:
Yeah, I also got 7.18.708.2. However, I would not take the risk unless I found the right one. Thanks though.
Click to expand...
Click to collapse
Download your ota update
Select "install later"
Connect your phone to your compter and copy the ota zip file from the download folder to your desktop.
Use winrar to open the ota zip file and extract firmware.zip from it
Use winrar to open firmware.zip and extract the recovery.img file.
Thats the recovery you need, flash it with fastboot then reboot phone and install the post poned ota
If the ota fails to install, youll have to flash a ruu