[Q] stock recovery or firmware 6.10.531.9 - T-Mobile HTC One (M7)

earlier today I flashed the V5.14.531.9 firmware and went from TWRP running on my 4.4.2 V5.14.531.9, to stock.
This was so I could be stock and flash the OTA.zip and get to 6.10.531.9 that I'm at now.
I've since flashed TWRP again so that I could make a Nandroid of the "stock" ROM, jic.
Where or how can I extract the firmware/stock recovery of 6.10.531.9 so I have it for the next time?
Or would re-flashing the OTA.zip do just that?
Dumb question prolly. But you'll get over it.

---

metropical said:
earlier today I flashed the V5.14.531.9 firmware and went from TWRP running on my 4.4.2 V5.14.531.9, to stock.
This was so I could be stock and flash the OTA.zip and get to 6.10.531.9 that I'm at now.
I've since flashed TWRP again so that I could make a Nandroid of the "stock" ROM, jic.
Where or how can I extract the firmware/stock recovery of 6.10.531.9 so I have it for the next time?
Or would re-flashing the OTA.zip do just that?
Dumb question prolly. But you'll get over it.
Click to expand...
Click to collapse
You can get the stock recovery from the OTA, just unzip it then unzip firmware.zip the recovery.img can be extracted from the zip. You can also extract the firmware, but just check it closely to see if all of the files are there sometimes OTA firmwares are short some files. I would compare it against an older firmware that has worked for you in the past.
Also, if you are S-OFF to make a completely stock nandroid you would need to downgrade to hboot 1.44 then you can use the fastboot boot recovery.img command. You would rename your custom recovery to recovery.img for this to work. Then you would go into the custom recovery and backup the system, cache, recovery etc. After the successful backup then you would boot in bootloader, change your hboot back to original and flash the custom recovery.

---

majmoz said:
You can get the stock recovery from the OTA, just unzip it then unzip firmware.zip the recovery.img can be extracted from the zip. You can also extract the firmware, but just check it closely to see if all of the files are there sometimes OTA firmwares are short some files. I would compare it against an older firmware that has worked for you in the past.
Also, if you are S-OFF to make a completely stock nandroid you would need to downgrade to hboot 1.44 then you can use the fastboot boot recovery.img command. You would rename your custom recovery to recovery.img for this to work. Then you would go into the custom recovery and backup the system, cache, recovery etc. After the successful backup then you would boot in bootloader, change your hboot back to original and flash the custom recovery.
Click to expand...
Click to collapse
first off. thanks. I think this may be the most concise and direct answer I've ever received in the 4 or 5 years I've been on XDA, sad to say.
I did as you suggested and unzipped the OTA and the Firmware after. Unzipping the firmware got me a slightly smaller copy of it with a .cpgz extension.
How would one one downgrade to HBOOT 1.44? I'm at 1.57 with this OTA'd ROM.

---

metropical said:
first off. thanks. I think this may be the most concise and direct answer I've ever received in the 4 or 5 years I've been on XDA, sad to say.
I did as you suggested and unzipped the OTA and the Firmware after. Unzipping the firmware got me a slightly smaller copy of it with a .cpgz extension.
How would one one downgrade to HBOOT 1.44? I'm at 1.57 with this OTA'd ROM.
Click to expand...
Click to collapse
Go to nkk71's SuperGuide in my signature he explains how to do it. Once you download the hboot_1.44.zip I would make a copy of it and name it hboot_1.57.zip. Then I would extract the hboot from the OTA firmware and put it in the hboot_1.57.zip. This way you have an file that you can flash in fastboot. When you download the hboot_1.44.zip check the android_info.txt file to ensure your MID & CID are present. I believe they are but I would double check to be sure.

---

hboot
majmoz said:
Go to nkk71's SuperGuide in my signature he explains how to do it. Once you download the hboot_1.44.zip I would make a copy of it and name it hboot_1.57.zip. Then I would extract the hboot from the OTA firmware and put it in the hboot_1.57.zip. This way you have an file that you can flash in fastboot. When you download the hboot_1.44.zip check the android_info.txt file to ensure your MID & CID are present. I believe they are but I would double check to be sure.
Click to expand...
Click to collapse
dl'd hboot 1.44. my mid and cid are both there, with * in the last few places.
do you know where in the OTA unzipped the hboot resides and is it named something else?
and about unzipping the firmware.zip in the OTA, any idea on why the .cpgz extension?
another question.
this: RUU_M7_UL_K443_SENSE60_MR_TMOUS_6.10.531.9_Radio_4T.28.3218.04_10.33E.1718.01L_release_387953_signed_2.exe
and this :
OTA_M7_UL_K443_SENSE60_MR_TMOUS_6.10.531.9-5.14.531.1_R_release_387954jjhcxbzgi6808nml.zip
in theory are the same thing except one is .exe and the other .zip. Since I'm on a Mac, the .exe is useless to me unless I install W7 again.
If the same I'd toss the .exe.
also is stock recovery still available after flashing TWRP by doing it manually from the phone (rather than Terminal) or does the flash of TWRP blow stock out?
Thanks again,

---

metropical said:
dl'd hboot 1.44. my mid and cid are both there, with * in the last few places.
do you know where in the OTA unzipped the hboot resides and is it named something else?
and about unzipping the firmware.zip in the OTA, any idea on why the .cpgz extension?
another question.
this: RUU_M7_UL_K443_SENSE60_MR_TMOUS_6.10.531.9_Radio_4T.28.3218.04_10.33E.1718.01L_release_387953_signed_2.exe
and this :
OTA_M7_UL_K443_SENSE60_MR_TMOUS_6.10.531.9-5.14.531.1_R_release_387954jjhcxbzgi6808nml.zip
in theory are the same thing except one is .exe and the other .zip. Since I'm on a Mac, the .exe is useless to me unless I install W7 again.
If the same I'd toss the .exe.
Thanks again,
Click to expand...
Click to collapse
Inside of the OTA is firmware.zip; inside firmware.zip is hboot_signedbyaa.img this is your hboot. I don't know about the .cpgz extension and on the OTA I got when I downloaded it from the phone doesn't have it in firmware.zip. The difference between the RUU and the OTA is the OTA is just an update and may or may not have all of the files necessary to completely rebuild the phone. The RUU has all of the files. Oftentimes, the update will only have those files that the service provider/manufacturer made a change to the original files, while the RUU has all of the files regardless where or not it was updated. Keep the RUU file and if you happen to have a Windows machine around you can make a RUU rom.zip. Here is how:
Extract the RUU and grab the rom.zip file. This is the most important file you need from the RUU and afterwards you can delete the RUU exe if you want. To get the rom.zip from your RUU exe file, you just need to run the RUU exe file once, and then when the window is ready and waiting for you to press on the "Next" button, just leave it open and go to your temp folder. I'm using Windows XP SP3 32-bit and my temp folder is located at this path: C:\Documents and Settings\Administrator\Local Settings\Temp. Now, you will see several files and folders. Sort everything in that temp folder based on "Date Modified" with the most recent folder showing up above all other folders. This is the folder you want. The folder name will be bunch of letters and numbers. Inside that folder you will find several files, but what you need is rom.zip and android-info.txt. Copy both these files and paste them somewhere safe on your hard drive. The android-info.txt contains crucial information about the compatibility of that RUU for your phone. Here's the android-info.txt extracted from my RUU exe:
Code:
[B]modelid: PN0713000
cidnum: T-MOB010
mainver: 6.10.531.9
btype:1
aareport:1
hbootpreupdate:3[/B]
You can then verify that you have the correct RUU if the MID matches that of your phone and if you can see your CID in that list. If either (or both) of the MID or CID does not match that of your phone, the RUU process will fail. The mainver is the firmware that is going to be flashed onto your phone. For easy reference, create a new folder and name it exactly like the RUU exe file and put the rom.zip and android-info.txt in there so you won't have trouble identifying that rom.zip file later if you need to flash it again. Now, you can close the RUU installation window and all the files in that temp folder containing rom.zip will be instantly erased. Note that if you open the rom.zip with WinZip/WinRAR, you will see a list of all the files but if you try to extract or double-click to open any of these files, you will get an error saying that the file is corrupt. This warning is only due to the files being encrypted by HTC, since the RUU is an official release and is digitally signed. To access those encrypted files, you will need to decrypt them on Linux.
Click to expand...
Click to collapse

---

majmoz said:
Inside of the OTA is firmware.zip; inside firmware.zip is hboot_signedbyaa.img this is your hboot. I don't know about the .cpgz extension and on the OTA I got when I downloaded it from the phone doesn't have it in firmware.zip. The difference between the RUU and the OTA is the OTA is just an update and may or may not have all of the files necessary to completely rebuild the phone. The RUU has all of the files. Oftentimes, the update will only have those files that the service provider/manufacturer made a change to the original files, while the RUU has all of the files regardless where or not it was updated. Keep the RUU file and if you happen to have a Windows machine around you can make a RUU rom.zip. Here is how:
Click to expand...
Click to collapse
for some reason unzipping on a Mac seems to give different results than on windows.
I'll keep both and perhaps reinstall the W7 partition on BootCamp again.
Thanks for the clear info , again.