ive downloaded many different roms trying to pull the rom.zip from each version to get recoveey backups etc.
my problem is that when i successfully copy the rom.zip, when i open and try to extract recovery.img and android.txt it's saying file corrupt.
any ideas.
ruu works fine and flashes fine. but i cannot extract all files from rom.zip
tried different zip repair tools, and all saying same thing, crc mismatch on recovery.img probably unrecoverable
japodude said:
ive downloaded many different roms trying to pull the rom.zip from each version to get recoveey backups etc.
my problem is that when i successfully copy the rom.zip, when i open and try to extract recovery.img and android.txt it's saying file corrupt.
any ideas.
ruu works fine and flashes fine. but i cannot extract all files from rom.zip
tried different zip repair tools, and all saying same thing, crc mismatch on recovery.img probably unrecoverable
Click to expand...
Click to collapse
That's because the ruu you tried to use is encrypted. If you want to take one apart use the decrypted one
Sent from my HTC6525LVW using Tapatalk
Related
im rooted. i have s-off but i still cant flash any roms or radios. when i try and flash PG86IMG.ZIP i get wrong zipped file and when itry and install a rom i get (E:Bad)
bobbycarver said:
im rooted. i have s-off but i still cant flash any roms or radios. when i try and flash PG86IMG.ZIP i get wrong zipped file and when itry and install a rom i get (E:Bad)
Click to expand...
Click to collapse
Open the zip file, if it contains few folders and a boot.img , then you should flash it from recovery not the bootloader.
And if it contains some files with img extensions then you should flash it through bootloader.
Anyone out there with the Stock ICS Nandroid backup from a Wind Mobile Amaze 4G I need your files!
Long story short I lost my Nandroid back up and now can't return to stock. Please help! Thank you in advance.
Just download an ruu or rooted ota from dev section and flash. Nandroid backups have personal information as well so I doubt anyone will offer that
Sent from my HTC_Amaze_4G using xda premium
I have tried that, it fails every time, gets to parsing PH85IMG then goes back hboot. From what I have read it seems that because the ICS update for Wind, Telus, Mobilicity, was OTA it can only be installed as an update. I can't install a previous version because I already updated to ICS while I was using stock. I have found threads of the Nandroid backups for other Canadian Carriers, just not Wind.
If I am wrong and you have any suggestions as to why the stock RUU's would fail to install please share them! I ran out of options and getting a Nandroid was the only other idea I could find that might work.
Thank you!
koroth said:
I have tried that, it fails every time, gets to parsing PH85IMG then goes back hboot. From what I have read it seems that because the ICS update for Wind, Telus, Mobilicity, was OTA it can only be installed as an update. I can't install a previous version because I already updated to ICS while I was using stock. I have found threads of the Nandroid backups for other Canadian Carriers, just not Wind.
If I am wrong and you have any suggestions as to why the stock RUU's would fail to install please share them! I ran out of options and getting a Nandroid was the only other idea I could find that might work.
Thank you!
Click to expand...
Click to collapse
Are you S-Off? Unlocked? Rooted? Or what? We need more information.
I am unlocked, rooted, s-on, using Speed ROM 6.
When trying the install I had the zip file on the SD Card renamed to PH85IMG.zip (only one .zip), with relocked bootloader. I even tried extracting the recovery.img and boot.img and flashing them first. Every time I just ended up at the HTC boot screen.
EDIT: And using 4EXT Recovery
koroth said:
I am unlocked, rooted, s-on, using Speed ROM 6.
When trying the install I had the zip file on the SD Card renamed to PH85IMG.zip (only one .zip), with relocked bootloader. I even tried extracting the recovery.img and boot.img and flashing them first. Every time I just ended up at the HTC boot screen.
Click to expand...
Click to collapse
You could try unlocking your bootloader, then extracting the OTA zip, and then grab the img files, and then flashing the boot.img, system.img, and data.img (and recovery.img if you want to restore it to as stock as possible)
You would effectively have a stock ROM.
The commands:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash data data.img
fastboot flash recovery recovery.img
That sounded very straight forward before I got the OTA update downloaded and extracted. The boot and recovery files are obvious. The data and system files not so much.
There are two files that could be the data ones, called rcdata and mdmrcdata. Then there is only directories called system, no image files. One is in the root directory and the other is in a patch directory. Can I just compress the root system directory into an image file? Will it function the same? And do you know which data file I should use?
Thanks again for your help.
Thanks for the help, finally gave up and gained S-OFF. Flashed an old hboot and ran the wind mobile ruu.exe from the wiki. Currently downloading OTA update from a stock wind mobile ROM!
im on hboot 1.15 and i understand i need to flash the cm10 Boot.img but how do i get it I cant seem to extract the cm10 zip file for some reason
Its in the rom. Just pull it out and put it in your adb folder
cortes742 said:
im on hboot 1.15 and i understand i need to flash the cm10 Boot.img but how do i get it I cant seem to extract the cm10 zip file for some reason
Click to expand...
Click to collapse
my free application, Flash Image GUI, will automatically extract the boot.img file and flash it. Then the next step is to reboot into the custom recovery and install the exact same rom.zip file.
essentially with htc's unlock method, the kernel portion of a ROM .zip can't be loaded from the standard recovery boot mode. my application, Flash Image GUI, loads the kernel portion of the ROM .zip from Android mode, easily allowing you to reboot into the custom recovery and apply the system portion of the ROM .zip.
if you're interesting in the more manual/command line route, which requires access to a desktop, the command you'll need is fastboot flash boot boot.img. in addition, the ROM .zip file should be the same as any other .zip file. if it doesn't open properly, might be a corrupt download. the boot.img is generally located in the root of the rom.zip file, or sometimes in a sub folder called kernel or boot. Flash Image GUI is very good at searching/locating the boot.img file in valid ROM .zip files.
hope the suggestions and some of those technical details help!
joeykrim said:
my free application, Flash Image GUI, will automatically extract the boot.img file and flash it. Then the next step is to reboot into the custom recovery and install the exact same rom.zip file.
essentially with htc's unlock method, the kernel portion of a ROM .zip can't be loaded from the standard recovery boot mode. my application, Flash Image GUI, loads the kernel portion of the ROM .zip from Android mode, easily allowing you to reboot into the custom recovery and apply the system portion of the ROM .zip.
if you're interesting in the more manual/command line route, which requires access to a desktop, the command you'll need is fastboot flash boot boot.img. in addition, the ROM .zip file should be the same as any other .zip file. if it doesn't open properly, might be a corrupt download. the boot.img is generally located in the root of the rom.zip file, or sometimes in a sub folder called kernel or boot. Flash Image GUI is very good at searching/locating the boot.img file in valid ROM .zip files.
hope the suggestions and some of those technical details help!
Click to expand...
Click to collapse
I tried using that method but your app says it could not locate the right zimage from the CM10Zip that i downloaded of Xda i was really confused as to why i couldnt even open the cm10 zip without getting and error on my desktop let alone the app. any thoughts?
cortes742 said:
I tried using that method but your app says it could not locate the right zimage from the CM10Zip that i downloaded of Xda i was really confused as to why i couldnt even open the cm10 zip without getting and error on my desktop let alone the app. any thoughts?
Click to expand...
Click to collapse
Try downloading the ROM again and use a program like 7zip to unzip the ROM. I'm pretty sure you can go into the ROM with esfile explorer from your phone. Then use flash image GUI and select the boot.IMG exactly.
Sent from my EVO using xda premium
Never mind....
cortes742 said:
I tried using that method but your app says it could not locate the right zimage from the CM10Zip that i downloaded of Xda i was really confused as to why i couldnt even open the cm10 zip without getting and error on my desktop let alone the app. any thoughts?
Click to expand...
Click to collapse
Sounds like a bad download of the ROM .zip file. Downloading a 2nd time should resolve the issue. Many times you can check the md5sum of the downloaded file to ensure the download is correct.
If you still get the error from my app, after downloading the file again and ensure the md5sums match, link me to the exact file? I'd like to take a look.
Hope that helps!
joeykrim said:
Sounds like a bad download of the ROM .zip file. Downloading a 2nd time should resolve the issue. Many times you can check the md5sum of the downloaded file to ensure the download is correct.
If you still get the error from my app, after downloading the file again and ensure the md5sums match, link me to the exact file? I'd like to take a look.
Hope that helps!
Click to expand...
Click to collapse
thanks bro after downloading it a couple times it still wasnt working for me but after the 8/29/2012 update i downloaded it unzipped like a charm. =0 thanks for the amazing support!
So i was able to get the cm10 boot.img and flash it through the flash Gui app. once i did that flashed the cm10 rom in recovery. i triedd to boot into it and i keep getting sent back to the bootloader. I wiped cache davlik factory reset and wiped the system. was i not supposed to wipe the system? now i cant even restore to a sense rom is it because i flashed the cm10 boot.img? i am assuming i need to FASTBOOT a sense boot.img since i cant get into a sense rom.
So finally after flash gui not working for me i Fastbooted the Boot.img through adb and was able to flash cm10 zip again and it BOOTED! i tried this method after downloading the 8/31/2012 cm10 zip. I think i wiped system last time which messed up the whole thing!
cortes742 said:
So finally after flash gui not working for me i Fastbooted the Boot.img through adb and was able to flash cm10 zip again and it BOOTED! i tried this method after downloading the 8/31/2012 cm10 zip. I think i wiped system last time which messed up the whole thing!
Click to expand...
Click to collapse
Wiping the system and then trying to boot will definitely cause issues. Glad everything worked out!
For future reference, if you do experience any issues you think are related to how Flash Image GUI functions, feel free to post up in that thread. I do my best to respond as soon as possible!
Allright , my computer gave its last breath this morning im s on is there a way to flash the boot without the pc
Yes, if you have a PH98IMG of the kernel. A lot of ROMs now will make the PH98IMG of the boot.img for you during install though, so all you need to do is accept the "update" after you flash the ROM. Or, some ROMs come with the kernel in a PH98IMG file posted in the OP that you can download. You just put that on your sd card and flash it in hboot.
If the ROM you want to use doesn't have one you can make one by swapping out the boot.img inside a PH98IMG file that is already made. Just make sure the android-info.txt file has the correct mainver listed in it.
I've attached a PH98IMG of an OLD stock boot.img you can use as a template (do not flash this kernel). Delete the boot.img in it and replace it with the one you want to use and edit the android-info.txt file to your mainver since this one is from GB days. If you don't know it and can use the pc to get it put the phone in fastboot and type
fastboot getvar all
(hm... can you do all that on your phone? I'm not sure...)
In case you can't use your pc at all and it helps, I'm currently on the global leak and my mainver is... huh... mine is blank when I use "fastboot getvar all". Hmph.
Or, is there a particular kernel you need to flash now? If you post your mainver I or someone else can make a PH98IMG file of it for you.
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.