Verizon RUU 6.22.605.6 PN07IMG Signed
PN07IMG_M7_WL_L50_SENSE60_MR_VERIZON_WWE_6.22.605.6_HSM_Radio_1.13.41.1209_NV_VZW_4.64_002_release_460480_signed_1
Disclaimer:
Flash at your own risk!
This will wipe your entire phone, including internal sdcard. Back up your files to your pc first.
This will not effect s-off status.
How To Flash:
Check MD5 sum and make sure it is correct
Rename file to exactly PN07IMG.zip (PN[ZERO]7IMG.zip)
Place file on fat32 formated sd card or usb drive in no folders
Connect the sd card or usb drive to your phone using a usb-otg cable.
Boot to hboot (power off phone, hold volume down and power at the same time)
Once in hboot it should automaticly find the file, and prompt you to press volume up to flash it.
Phone will reboot several times. Once its done, the phone will try to boot but will bootloop.
Boot back to hboot ( hold vol down and power untill hboot comes up), and select factory reset.
The phone will rboot several times, once its done it will boot up to stock 6.22.605.6
DOWNLOAD
PN07IMG_M7_WL_L50_SENSE60_MR_VERIZON_WWE_6.22.605.6_HSM_Radio_1.13.41.1209_NV_VZW_4.64_002_release_460480_signed_1 zip
MD5:574ed7acdcf77263ac60943e2f001d2a - 1.4gb
.
Other M7 6.22.605.6 Files:
https://androidfilehost.com/?w=files&flid=46152
Reserved Too
Merry Christmas!
cmlusco said:
Verizon RUU 6.22.605.6 PN07IMG Signed
Quoted material removed......
Click to expand...
Click to collapse
I don't think this is exactly what you think it is.. it's only 419 megs large
What is it then? I have successfully flashed the phone with it after being wiped in twrp. It has also been downloaded more than 40 times, and no one has said anything about any issues. If its not i dont want to misrepresent it, especially if it will mess up someones phone. I think i know quite a bit about htc phones, but i am definitley no expert. All i know is it worked for me more than once, on two different m7's.
cmlusco said:
What is it then? I have successfully flashed the phone with it after being wiped in twrp. It has also been downloaded more than 40 times, and no one has said anything about any issues. If its not i dont want to misrepresent it, especially if it will mess up someones phone. I think i know quite a bit about htc phones, but i am definitley no expert. All i know is it worked for me more than once, on two different m7's.
Click to expand...
Click to collapse
I will tear it open tomorrow and take a look but the previous signed ruu were almost 1.4gb. Double check the size of the file you uploaded to make sure too. Just the system partition alone dd'd and trimmed and zipped would be larger than 419megs.
Sent from my SM-T810 using Tapatalk
dottat said:
I will tear it open tomorrow and take a look but the previous signed ruu were almost 1.4gb. Double check the size of the file you uploaded to make sure too. Just the system partition alone dd'd and trimmed and zipped would be larger than 419megs.
Sent from my SM-T810 using Tapatalk
Click to expand...
Click to collapse
The file sizes and md5's match on my pc and on afh. This is a link to the original file as i got it. https://www.androidfilehost.com/
cmlusco said:
The file sizes and md5's match on my pc and on afh. This is a link to the original file as i got it. https://www.androidfilehost.com/?fid=24352994023707485
Click to expand...
Click to collapse
So I opened it today and it's not an RUU.
One is 1.4gb and one is 419Meg. I believe the file posted in the OP is the sync version of "update"... not an actual RUU. You should straighten up the OP to reflect this file link you posted (and is quoted in my post) here because it's the actual 1.4gb RUU. Unlike a rom, a bad RUU on a the wrong phone will lead to a brick so be very careful in what you post RUU wise.
Also, I believe you cut copied and pasted your RUU from the m9 thread you posted... the line below needs a little tweaking from the RUU.
The phone will rboot several times, once its done it will boot up to stock 3.10.605.7
Sent from my SM-T810 using Tapatalk
dottat said:
So I opened it today and it's not an RUU.
One is 1.4gb and one is 419Meg. I believe the file posted in the OP is the sync version of "update"... not an actual RUU. You should straighten up the OP to reflect this file link you posted (and is quoted in my post) here because it's the actual 1.4gb RUU. Unlike a rom, a bad RUU on a the wrong phone will lead to a brick so be very careful in what you post RUU wise.
Also, I believe you cut copied and pasted your RUU from the m9 thread you posted... the line below needs a little tweaking from the RUU.
The phone will rboot several times, once its done it will boot up to stock 3.10.605.7
Sent from my SM-T810 using Tapatalk
Click to expand...
Click to collapse
So you are saying that the whole file is the ruu? Will that flash with zip's inside of a zip? Thanks for looking at it, learn something new every day.
cmlusco said:
So you are saying that the whole file is the ruu? Will that flash with zip's inside of a zip? Thanks for looking at it, learn something new every day.
Click to expand...
Click to collapse
The [email protected] zip format HTC uses has always contained multiple zips. Usually one or two contain firmware and a half dozen or so contain system broken into pieces.
Sent from my Nexus 6 using Tapatalk
dottat said:
The [email protected] zip format HTC uses has always contained multiple zips. Usually one or two contain firmware and a half dozen or so contain system broken into pieces.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
I tried flashing the whole file both with fastboot flash, as a PN07IMG.zip, and as an update.zip from stock recovery, and all failed with errors. Fastboot flash gave error "read zipped android-info fail", PN07IMG.zip hboot said "no img wrong img", and recovery just said "installation aborted" after about 30 seconds. Any ideas, i have pulled the links for now.
cmlusco said:
I tried flashing the whole file both with fastboot flash, as a PN07IMG.zip, and as an update.zip from stock recovery, and all failed with errors. Fastboot flash gave error "read zipped android-info fail", PN07IMG.zip hboot said "no img wrong img", and recovery just said "installation aborted" after about 30 seconds. Any ideas, i have pulled the links for now.
Click to expand...
Click to collapse
How did you extract the smaller zip from the larger might I ask?
Sent from my Nexus 6 using Tapatalk
dottat said:
How did you extract the smaller zip from the larger might I ask?
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
With a program called universal extractor. Think thats my problem, what program should i use?
cmlusco said:
With a program called universal extractor. Think thats my problem, what program should i use?
Click to expand...
Click to collapse
Ok... so the larger zip simply gets extracted.. that gives you two things. 1) the bootloader in a flashable zip and 2) the RUU itself (which is 1.4gb).
I am uploading a copy of the correct RUU file shortly. I believe that app you used only extracted one system chunk/zip. There are a couple tools i use to extract the RUU file down into separate zips. See the screenshot i attached.... original RUU/signed zip at the top and the resulting RUU below... first one is the firmare, 2,3 and 4th are system split up and the 5th is boot and tp zipped.
Here's the firmware only zip
https://www.androidfilehost.com/?fid=24367857647223006
Full flashable signed RUU zip (1.4gb)
https://www.androidfilehost.com/?fid=24367857647223007
dottat said:
Ok... so the larger zip simply gets extracted.. that gives you two things. 1) the bootloader in a flashable zip and 2) the RUU itself (which is 1.4gb).
I am uploading a copy of the correct RUU file shortly. I believe that app you used only extracted one system chunk/zip. There are a couple tools i use to extract the RUU file down into separate zips. See the screenshot i attached.... original RUU/signed zip at the top and the resulting RUU below... first one is the firmare, 2,3 and 4th are system split up and the 5th is boot and tp zipped.
Here's the firmware only zip
https://www.androidfilehost.com/?fid=24367857647223006
Full flashable signed RUU zip (1.4gb)
https://www.androidfilehost.com/?fid=24367857647223007
Click to expand...
Click to collapse
Thank you, i will update the op.
cmlusco said:
verizon ruu 6.22.605.6 pn07img signed
pn07img_m7_wl_l50_sense60_mr_verizon_wwe_6.22.605.6_hsm_radio_1.13.41.1209_nv_vzw_4.64_002_release_460480_signed_1
disclaimer:
flash at your own risk!
This will wipe your entire phone, including internal sdcard. Back up your files to your pc first.
This will not effect s-off status.
how to flash:
check md5 sum and make sure it is correct
rename file to exactly pn07img.zip (pn[zero]7img.zip)
place file on fat32 formated sd card or usb drive in no folders
connect the sd card or usb drive to your phone using a usb-otg cable.
Boot to hboot (power off phone, hold volume down and power at the same time)
once in hboot it should automaticly find the file, and prompt you to press volume up to flash it.
Phone will reboot several times. Once its done, the phone will try to boot but will bootloop.
Boot back to hboot ( hold vol down and power untill hboot comes up), and select factory reset.
The phone will rboot several times, once its done it will boot up to stock 6.22.605.6
download
pn07img_m7_wl_l50_sense60_mr_verizon_wwe_6.22.605.6_hsm_radio_1.13.41.1209_nv_vzw_4.64_002_release_460480_signed_1 zip
md5:574ed7acdcf77263ac60943e2f001d2a - 1.4gb
.
Click to expand...
Click to collapse
the process didnt work on my phone . Sohould i use adb fastboot tools??
Related
Who should read this post?
You have updated your One X to a newer version via OTA, then you want to restore the software/ return stock but the latest RUU is not available. (boot to fastboot mode and type the following command "fastboot getvar version-main", This is the true version of your phone!)
You have some basic skills to flash things using "fastboot"
Those who want to back to stock and wait for the JB OTA.
Those with ICS hboot should works without any problem, someone had test it on JB hboot and works(updated in step 6, 7). but we need more testers.
The concept behind.
1. Fool the RUU to make it believe that it is flashing the latest ROM, but actually, we are flashing an older version.
2. after that, boot up the phone with older version of software, then OTA and update the phone to latest software.
How to do that?
0. backup all your stuff including those in SD, all your stuff in your phone will be lost. Then wipe all data (including SD) using your custom recovery. (important! Otherwise, you may not be able to receive OTA).
1. You have to download a "custom RUU" that can be found here.
http://db.tt/z8ajRTuH
Feel free to give a thanks to billd2439, he provide this working link to download the custom RUU.
Just go to #115 http://forum.xda-developers.com/showthread.php?p=35139501#post35139501 and give him a thanks
2. Download the ROM file, it should be in zip format. (You can also extract the rom file by running a RUU, just run the RUU, don't click anything and search the computer for "rom.zip") (In my case, I have an older version 1.29.708.15 rom extracted from RUU)
you may want to find RUU here http://www.htcruu.com
3. unzip the customRUU.zip to a folder, e.g. "customRUU"
4. unzip and extract "android-info.txt", "boot_signed.img" and "system.img" to a folder
5. open android-info.txt with "notepad" (notepad++ is highly recommended)
6. type the following command to get the information from your phone.
fastboot getvar all
you should pay attention to the following information
modelid:
cidnum:
mainver:
hbootpreupdate:
7. edit the value of "modelid", "cidnum", "mainver" and "hbootpreupdate" to match the information you get from step 6.
by doing this your will try to fool the RUU to belive that you are going to flash a newer version e.g (I have OTA my phone to 2.17.708.7, but now I want to fool the RUU with this old rom with a version number of 1.29.708.15, so I change the value to 2.17.708.7 )
Thanks ahmedaljaf for telling me to modify hbootpreupdate to makes JB downgrade works
8. save the file.
9. zip "android-info.txt", "boot_signed.img" and "system.img" and rename the zip to "rom.zip". (remember only zip the files, not the whole folder!)
10. place the "rom.zip" you just created to the "customRUU" folder
11. make sure your phone is still "unlock", remember to turn on USB Debugging, unplug the USB cable and reboot your phone, then goto fastboot mode and connect the USB cable.
(important, do the above to avoid error messages in RUU)
12. run the file "ARUWizard.exe" inside the folder "customRUU" (see the Attached Readme_Eng.pdf if the customRUU cannot display in correct language)
You can change the customRUU to English version by just delete or rename the language file "ARUWizard_Eng.lng" (Thanks ahmedaljaf for telling me this :good
13. follow the on screen instruction,
14. your phone should reboot and boot up with and old version of software.
15. restart the phone and go to fastboot mode.
16. extract the "recovery_signed.img" from your old "rom.zip" (not the rom.zip you create! ) and place it to some where.
17. flash the recovery by typing the following command "fastboot flash recovery recover_signed.img"
18. relock the phone
19. boot up the phone and try OTA
18. if the OTA download finish but fail to reboot to recovery update automatically, just manually boot to recovery and the update will be ok.
If you can return stock with this method, please reply and list the version here. And you can give me a "thanks" :good:
I wonder, if you put in the "rom.zip" the "hboot_0.95.0000.img" from an older RUU will you be able to downgrade the 1.28 hboot also?
There's NO way to downgrade hboot unless you have s-off.
Sent from my HTC One X using xda premium
ionut.micu said:
I wonder, if you put in the "rom.zip" the "hboot_0.95.0000.img" from an older RUU will you be able to downgrade the 1.28 hboot also?
Click to expand...
Click to collapse
They are somebody on chinese forum who use this method claimed he was able to do hboot downgrade through this method, but no one seem suceed so for.
Well, technically this method able to get you spoof ROM version because it check on your PC. While for hboot it validate the signature and version on the phone before upgrading itself. You can see the process if you push the firmware yourself via fastboot.
HebeGuess said:
They are somebody on chinese forum who use this method claimed he was able to do hboot downgrade through this method, but no one seem suceed so for.
Well, technically this method able to get you spoof ROM version because it check on your PC. While for hboot it validate the signature and version on the phone before upgrading itself. You can see the process if you push the firmware yourself via fastboot.
Click to expand...
Click to collapse
What if we hex edit the 0.95.0000 before we put it into the rom.zip to make it think that it's a newer version, will that brake the signature?
Sorry but I don't have the guts to try it myself
a good link
hokoonho said:
Who should read this post?
You have updated your One X to a newer version via OTA, then you want to restore the software/ return stock but the latest RUU is not available.
You have some basic skills to flash things using "fastboot"
Those who want to back to stock and wait for the JB OTA.
The concept behind.
1. Fool the RUU to make it believe that it is flashing the latest ROM, but actually, we are flashing an older version.
2. after that, boot up the phone with older version of software, then OTA and update the phone to latest software.
How to do that?
0. backup all your stuff including those in SD, all your stuff in your phone will be lost.
1. You have to download a "custom RUU" that can be found here (you can also found a rom that for One X for HK only).
http://pan.baidu.com/share/link?shareid=64762&uk=1042525484
If your phone is from other region, you may want to find the rom or RUU here http://www.htcruu.com
2. Download the ROM file, it should be in zip format. (You can also extract the rom file by running a RUU, just run the RUU, don't click anything and search the computer for "rom.zip") (In my case, I have an older version 1.29.708.15 rom extracted from RUU)
3. unzip the customRUU.zip to a folder, e.g. "customRUU"
4. unzip and extract "android-info.txt", "boot_signed.img" and "system.img" to a folder
5. open android-info.txt with "notepad" (notepad++ is highly recommended)
6. edit the value of"cidnum" to match your phone, e.g. ("HTC__622" for HK, "HTC__621" for Taiwan)
7. edit the value of "mainver" to the current software version your phone. e.g (I have OTA my phone to 2.17.708.7, but now I want to fool the RUU with this old rom with a version number of 1.29.708.15, so I change the value to 2.17.708.7 )
8. save the file.
9. zip "android-info.txt", "boot_signed.img" and "system.img" and rename the zip to "rom.zip". (remember only zip the files, not the whole folder!)
10. place the "rom.zip" you just created to the "customRUU" folder
11. make sure your phone is still "unlock"
12. run the file "ARUWizard.exe" inside the folder "customRUU"
13. follow the on screen instruction,
14. your phone should reboot and boot with and old version of software.
15. restart the phone and go to fastboot mode.
16. extract the "recovery_signed.img" from your old "rom.zip" (not the rom.zip you create! ) and place it to some where.
17. flash the recovery by typing the following command "fastboot flash recovery recover_signed.img"
18. relock the phone
19. boot up the phone and try OTA
18. if the OTA download finish but fail to reboot to recovery update automatically, just manually boot to recovery and the update will be ok.
Click to expand...
Click to collapse
link to custom ruu its dead. any alternative?
ionut.micu said:
I wonder, if you put in the "rom.zip" the "hboot_0.95.0000.img" from an older RUU will you be able to downgrade the 1.28 hboot also?
Click to expand...
Click to collapse
No, if you include the old hboot, the process will be fail.
Sent from my HTC One X using xda premium
darckreign1984 said:
link to custom ruu its dead. any alternative?
Click to expand...
Click to collapse
link updated, enjoy
Sent from my HTC One X using xda premium
or you could just cook yourself a flashable zip from the rom.zip. Then fastboot flash rec and boot. Chances are ics wont boot on the newer hboots. Still the ota can be flashed as update.zip maybe.
usefull for some case
bookmarked
BRILLIANT! Absolutely brilliant! Thanks a million hokoonho. This method worked like a treat on my HK_621 HOX which was running ARHD 9.7.2
unsucces
speedofheat said:
BRILLIANT! Absolutely brilliant! Thanks a million hokoonho. This method worked like a treat on my HK_621 HOX which was running ARHD 9.7.2
Click to expand...
Click to collapse
arhd 12 and hboot 1.28 - not working
the 10 min time to flash its useles.... nothing its flashing in this time
darckreign1984 said:
arhd 12 and hboot 1.28 - not working
the 10 min time to flash its useles.... nothing its flashing in this time
Click to expand...
Click to collapse
The method works well with ICS, even with other HTC model as well, but I am not sure if it still work will JB and latest hboot. But it won't kill your phone.
Sent from my HTC One X using xda premium
I have followed the instructions, and now I am at the point where I run "ARUWizard" and follow the onscreen instructions...
However, The test is not English, it is funny looking as if the language is corrupt/unrecognised.
See attachment.
Any advice?
lukems said:
I have followed the instructions, and now I am at the point where I run "ARUWizard" and follow the onscreen instructions...
However, The test is not English, it is funny looking as if the language is corrupt/unrecognised.
See attachment.
Any advice?
Click to expand...
Click to collapse
It's OK, The RUU may not be able to select the right language to display, but It still works, since the RUU only use adb and fastboot to finish its process, and all these adb and fastboot are run in English...
A brief translation was made for those cannot Open the customRUU in correct language. go to OP for the pdf file
hokoonho said:
It's OK, The RUU may not be able to select the right language to display, but It still works, since the RUU only use adb and fastboot to finish its process, and all these adb and fastboot are run in English...
I am translating the Text to English and will upload a guide, just follow the guide to click the buttons... wait for a few minutes please.
Click to expand...
Click to collapse
No problem, I have found an English version.
I am finding that I get a Error 170 USB error... I believe this is because I have an unlocked bootloader.
So I re-locked the bootloader... and found myself unable to get past the bootloader.
I managed to run the RUU whilst phone was at the bootloader screen,
Replaced the temp rom.img with the created rom.img in your guide,
But it ended up failing with a Error 132 signature check.
I am not sure how to proceed.
lukems said:
No problem, I have found an English version.
I am finding that I get a Error 170 USB error... I believe this is because I have an unlocked bootloader.
So I re-locked the bootloader... and found myself unable to get past the bootloader.
I managed to run the RUU whilst phone was at the bootloader screen,
Replaced the temp rom.img with the created rom.img in your guide,
But it ended up failing with a Error 132 signature check.
I am not sure how to proceed.
Click to expand...
Click to collapse
Could you provide a ling to the English version you've got ? Thanks
lukems said:
No problem, I have found an English version.
I am finding that I get a Error 170 USB error... I believe this is because I have an unlocked bootloader.
So I re-locked the bootloader... and found myself unable to get past the bootloader.
I managed to run the RUU whilst phone was at the bootloader screen,
Replaced the temp rom.img with the created rom.img in your guide,
But it ended up failing with a Error 132 signature check.
I am not sure how to proceed.
Click to expand...
Click to collapse
Don't relock at this moment, otherwise, you will not be able to flash the stock recovery. Unlock it first. Make sure USB debugging is on, then REBOOT to fastboot and start the RUU. Or...Try another USB cable, DON'T connect via a USB hub...
Sent from my HTC One X using xda premium
hokoonho said:
Don't relock at this moment, otherwise, you will not be able to flash the stock recovery. Unlock it first. Make sure USB debugging is on, then REBOOT to fastboot and start the RUU. Or...Try another USB cable, DON'T connect via a USB hub...
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Ok will try now.
Edit: I am now waiting for it to finish... we will see soon enough if it works.
Screenshot showing upgrade screen uploaded.
Edit 2: It completed successfully
build downgraded from 2.17.401.2 to 1.28.771.9
lukems said:
I have followed the instructions, and now I am at the point where I run "ARUWizard" and follow the onscreen instructions...
However, The test is not English, it is funny looking as if the language is corrupt/unrecognised.
See attachment.
Any advice?
Click to expand...
Click to collapse
lukems said:
Ok will try now.
Click to expand...
Click to collapse
I have updated step 11. should disconnect the USB cable during reboot. If it still not work, restart both your phone and PC.
These are totally standard and have not been altered in any way.
Taiwan - https://drive.google.com/open?id=0B01V_alsJMzLMVIyMERISGFkbEk
Japan - https://drive.google.com/open?id=0B01V_alsJMzLcDFvc240dkpqVU0
These are here with BIG thanks to mrquyen1993 who sent them to me because the link from the Q&A video is unreliable to the rest of the world!
Fully fixed version will be uploaded in a few hours
Gixermouse said:
These are totally standard and have not been altered in any way.
Taiwan - https://drive.google.com/open?id=0B01V_alsJMzLMVIyMERISGFkbEk
Japan - https://drive.google.com/open?id=0B01V_alsJMzLcDFvc240dkpqVU0
These are here with BIG thanks to mrquyen1993 who sent them to me because the link from the Q&A video is unreliable to the rest of the world!
Fully fixed version will be uploaded in a few hours
Click to expand...
Click to collapse
Thanks very much! I will wait for the fixed ones as well!
---------- Post added at 07:39 PM ---------- Previous post was at 06:58 PM ----------
I downloaded the taiwan rom my friend and the zip file is not working.. Gives an error of 'decompression failed' / 'invalid archive' when I try to open it..
Coolio!
The Easiest way: My Guide
http://forum.xda-developers.com/butterfly-3/development/stock-rom-stock-5-0-2-cure-t3356875
moizjazz is correct (bottom comment), but flashing is soooo much easier.
Gixermouse said:
These are totally standard and have not been altered in any way.
Taiwan - https://drive.google.com/open?id=0B01V_alsJMzLMVIyMERISGFkbEk
Japan - https://drive.google.com/open?id=0B01V_alsJMzLcDFvc240dkpqVU0
These are here with BIG thanks to mrquyen1993 who sent them to me because the link from the Q&A video is unreliable to the rest of the world!
Fully fixed version will be uploaded in a few hours
Click to expand...
Click to collapse
Gixermouse can you please upload the TW stock rom to another link (dropbox?). The google drive link gives the same error (decompression failed) at the end of the download.
moizjazz said:
Gixermouse can you please upload the TW stock rom to another link (dropbox?). The google drive link gives the same error (decompression failed) at the end of the download.
Click to expand...
Click to collapse
Hi,
I have test the TW stock rom, it's fine that you can't decompression this special zip file.
And I found another way to update this RUU into the Butterfly3.
The system will check the file "0PL2IMG.zip" from ext-SD everytime you boot into download mode(Pow+Vol down), so i change
the stock Rom's name and put it to the root of my EXT SD card, then boot your phone into download mode again, it will show up
some words at the bottom of the screen asking you whether to update the system or not.
Be sure you have done the "wipe data/factory reset" and "wipe cache partition" at recovery mode before you do this.
Enjoy~
SeaturtleSTO said:
Hi,
I have test the TW stock rom, it's fine that you can't decompression this special zip file.
And I found another way to update this RUU into the Butterfly3.
The system will check the file "0PL2IMG.zip" from ext-SD everytime you boot into download mode(Pow+Vol down), so i change
the stock Rom's name and put it to the root of my EXT SD card, then boot your phone into download mode again, it will show up
some words at the bottom of the screen asking you whether to update the system or not.
Be sure you have done the "wipe data/factory reset" and "wipe cache partition" at recovery mode before you do this.
Enjoy~
Click to expand...
Click to collapse
I have successfully flashed the TW rom from the original link shared by Gixermouse and mrquyen1993. The zip file does give the error but it is meant to be that way (as mentioned by seaturtleSTO).. However, I was still getting errors when trying to flash it on using power + vol down and then vol up.. I had to change the MID of the phone first to 0PL220000 ("command: fastboot oem writemid 0PL220000" in fastboot mode through cmd). I had to then format my external SD card to match byte size of 4096 (initially it was 32Kbytes) NOTE: IF THIS IS NOT DONE THEN YOU CAN'T COPY THE FILE AS IT IS (IN WINDOWS) AND CANNOT FLASH. THE BYTE SIZE HAS TO BE 4096.
After this I copied the file again to ext SD card and flashed it through power + vol down and then vol up. It worked this time !
After the above I followed the guide provided by mrquyen1993 to install the OTA of Marshmallow 6.0 (https://htchtv31.wordpress.com/2016...hat-android-6-0-1-dai-loan-cho-htc-b3-htv-31/). You have to change the CID of the phone to HTC__621 (fastboot oem writecid HTC__621) to successfully download and install Marshmallow.
Thanks everyone for the help and I hope what I have mentioned above will be helpful to others!
NOTE: I have S-OFF only with no bootloader unlocked, no root and no TWRP installed. This works for stock phones but needs S-OFF I assume.
moizjazz said:
Thanks very much! I will wait for the fixed ones as well!
---------- Post added at 07:39 PM ---------- Previous post was at 06:58 PM ----------
I downloaded the taiwan rom my friend and the zip file is not working.. Gives an error of 'decompression failed' / 'invalid archive' when I try to open it..
Click to expand...
Click to collapse
You don't extract file rom by rar because it was embedded certificates HTC.
You can install using adb or hboot
Hi,
Can I install these ROMs using the TWRP restore function? Or install?
moizjazz said:
I have successfully flashed the TW rom from the original link shared by Gixermouse and mrquyen1993. The zip file does give the error but it is meant to be that way (as mentioned by seaturtleSTO).. However, I was still getting errors when trying to flash it on using power + vol down and then vol up.. I had to change the MID of the phone first to 0PL220000 ("command: fastboot oem writemid 0PL220000" in fastboot mode through cmd). I had to then format my external SD card to match byte size of 4096 (initially it was 32Kbytes) NOTE: IF THIS IS NOT DONE THEN YOU CAN'T COPY THE FILE AS IT IS (IN WINDOWS) AND CANNOT FLASH. THE BYTE SIZE HAS TO BE 4096.
After this I copied the file again to ext SD card and flashed it through power + vol down and then vol up. It worked this time !
After the above I followed the guide provided by mrquyen1993 to install the OTA of Marshmallow 6.0 (https://htchtv31.wordpress.com/2016...hat-android-6-0-1-dai-loan-cho-htc-b3-htv-31/). You have to change the CID of the phone to HTC__621 (fastboot oem writecid HTC__621) to successfully download and install Marshmallow.
Thanks everyone for the help and I hope what I have mentioned above will be helpful to others!
NOTE: I have S-OFF only with no bootloader unlocked, no root and no TWRP installed. This works for stock phones but needs S-OFF I assume.
Click to expand...
Click to collapse
I think this only happened because you went from a KDDI ROM to a Taiwan one (which wouldn't work with the wrong CID).
I went from an older KDDI ROM to this one and I didn't need to do anything but the confirmation after download mode.
As for the SD Card, I didn't need to do anything either. I had it formated in exFAT and it just worked.
HI, i have big problem with my htc beutiful ,when i press to start my mobile phone it stoped in first pic of htc without continiu to log on
the thing is this i deleted my os whilest trying to root my phone and the only access i have on my phone is in download mode and into the recovery . I download stock rom on my phone from deferent site they all can extract and now i just download from here and i again i cant extract i tried to use winzip,7zip and winrar to open but they all cant extract. my phone htc butterfly 3
cid=1111111
mid=opl220000
lk=1.0.0.0000
radio=-01.01-u11440541-63.01.50827BG-F
os=2.10.709.1
thanks in advance
Gixermouse said:
These are totally standard and have not been altered in any way.
Taiwan - https://drive.google.com/open?id=0B01V_alsJMzLMVIyMERISGFkbEk
Japan - https://drive.google.com/open?id=0B01V_alsJMzLcDFvc240dkpqVU0
These are here with BIG thanks to mrquyen1993 who sent them to me because the link from the Q&A video is unreliable to the rest of the world!
Fully fixed version will be uploaded in a few hours
Click to expand...
Click to collapse
LINK not working
KHAN JAN said:
LINK not working
Click to expand...
Click to collapse
So sorry mate, the link died after I lost my HTV31 three years ago and I don't have any of the files anymore
Good morning,
I tried to revert back to stock as I had to send my 10 to service.
So, I took an old NAND (which was working fine when updating firmware) and restored it in TWRP. I'm S-On with unlocked bootloader.
NAND went through but then I was stuck on boot screen.....
Power + Vol down brought me back to "stock!!!recovery. From there to bootloader and then back to TWRP.
Getvar all showed me nothing, just lines without any values.
I finally flashed the MM Viper rom with a full wipe and it booted again.........with all apps and setting.
I have no clue what happened. I only want to get back to stock.
same problem as you, no idea why
Glad, I'm not the only one facing that issue. Sad we don't know what it caused.
Maybe the NAND backup does not harmonize with the newer firmware? No clue.
But now I can't handle that chaotic system.
nerodarknight said:
same problem as you, no idea why
Click to expand...
Click to collapse
Prinz069 said:
Glad, I'm not the only one facing that issue. Sad we don't know what it caused.
Maybe the NAND backup does not harmonize with the newer firmware? No clue.
But now I can't handle that chaotic system.
Click to expand...
Click to collapse
Are you on N firmware, or MM firmware?
Try find RUU for your firmware, flash that, it will clean reset your phone back to everything stock.
Btw the "stock recovery" you found by pressing power + vol down, is not recovery at all. It is download mode (same thing as fastboot mode.)
Newer HTC devices will have this enhanced Download mode from now on.
If you can find an RUU zip then just place it in SDcard and reboot to Download mode and you can easily flash the RUU without needing to run a program on your computer.
I prefer this because I use Linux at home, and RUU.exe won't work on linux.
MM firmware, but Im s-on
Prinz069 said:
MM firmware, but Im s-on
Click to expand...
Click to collapse
Perfect, it will be very straight forward then...
Find RUU for your firmware, make sure mid and cid match.
Once you flash that, relock your bootloader and send it back to HTC for service.
Your warranty won't be void.
Cant read out cid as getvar shows now values
Prinz069 said:
Cant read out cid as getvar shows now values
Click to expand...
Click to collapse
Then make an estimated guess.
You are from germany, so your phone would probably be an european variant right?
Could be a GSM unlocked variant, or a carrier unit.
Find what version your phone is, and find the RUU for that version and hope that the CID/MID matches.
What about the non working getvar command? Ill post a screenshot later.
Prinz069 said:
What about the non working getvar command? Ill post a screenshot later.
Click to expand...
Click to collapse
That i do not know, i just hope your phone is not hard-bricked.
Try to RUU until something happens.
Good luck haha
You can check your CID onscreen when in download mode.
To get there Start device with Power + Vol- pressed.
As far as I know you then could try a CID/MIP matching RUU, that has to be same or newer version then the one you're running to flash that with S-ON. But don't nail me on that.
When you say "stuck on boot screen", what, exactly, does that mean? For how long? First boot can take 20+ mins easy before hitting the "configuring app X of Y" screen.
Download mode tells you your CID, MID, firmware version, etc.
Since you're sending it back in for service, yes, RUU it (via SD card zip). It's easy and thorough.
Boot into download mode and read your firmware. If you are MM/Germany you probably have 1.95.401.X firmware (same as mine - MM/Ger/Unlocked).
Go to RUU thread and download RUU zip that is exactly or higher firmware as yours.
Rename as instructed in that thread (2PS6IMG.zip or something like that) and put it on your SDcard.
Reboot Download mode, it will detect the zip and ask if you want to flash it.
Confirm and let it reboot.
Thank you guys, you're all awesome...wish we could have a couple of drinks together:good:
Prinz069 said:
Thank you guys, you're all awesome...wish we could have a couple of drinks together:good:
Click to expand...
Click to collapse
Perfect, you have a ".401" phone.
It's an unlocked version, same as mine. (and most lol).
You could try running RUU.exe...if it doesn't work, use TWRP to mount the sdcard (internal, not the external one) and transfer the RUU.zip to your phone.
Go back into download mode and flash RUU there.
There's an RUU decrypter tool to extract the zip elsewhere in this forum.
[RESTORE STARTED]
Restore folder: '/external_sd/TWRP/BACKUPS/FA65XBN06916/1.95 Backup'
Skipping MD5 check based on user setting.
Calculating restore details...
I:InfoManager file '/external_sd/TWRP/BACKUPS/FA65XBN06916/1.95 Backup/boot.info' not found.
I:Restore file system is: 'emmc'.
I:InfoManager file '/external_sd/TWRP/BACKUPS/FA65XBN06916/1.95 Backup/system_image.info' not found.
I:Restore file system is: 'emmc'.
Restoring 2 partitions...
Total restore size is 4784MB
I:Restore filename is: boot.emmc.win
I:Restore file system is: 'emmc'.
Restoring Boot...
I:Reading '/external_sd/TWRP/BACKUPS/FA65XBN06916/1.95 Backup/boot.emmc.win', writing '/dev/block/mmcblk0p59'
[Boot done (2 seconds)]
I:Restore filename is: system_image.emmc.win
I:Restore file system is: 'emmc'.
Restoring System Image...
I:Reading '/external_sd/TWRP/BACKUPS/FA65XBN06916/1.95 Backup/system_image.emmc.win', writing '/dev/block/mmcblk0p62'
Truncating string cache entries.
Truncating string cache entries.
I:Error writing destination fd (No space left on device)
This is the error I got for restoring the backup, can some explain the error for me?
nerodarknight said:
I:Error writing destination fd (No space left on device)
Click to expand...
Click to collapse
Could it be that?
dj_chapz said:
you probably have 1.95.401.X firmware
Click to expand...
Click to collapse
My Build is 1.95.401 when I check in Settings, But Downloade Mode says OS is 1.30.401.
Prinz069 said:
My Build is 1.95.401 when I check in Settings, But Downloade Mode says OS is 1.30.401.
Click to expand...
Click to collapse
Then you can flash pretty much any RUU zip to go back. Best bet would be the first newer RUU than 1.30.
Hello,
Hello, I mistakenly removed my phone's operating system. Can you help me put it back please?
hTC dowload mode
*** UNLOCKED ***
htc_himauhl PVT S-ON
LK-1.0.0.0000
RADIO-01.01_U114401011_117.00.61117G_2
OpenDSP-20.7.3.00535.8994_1012
OS-4.30.709.12
May 2 2017, 18:52:29(894012)
SD NOT MOUNTED
OTG NOT MOUNTED
File NOT FOUND
Flash the stock firmware via external sdcard. Your firmware is the same as what is written under "OS". All data will be lost.
shivadow said:
Flash the stock firmware via external sdcard. Your firmware is the same as what is written under "OS". All data will be lost.
Click to expand...
Click to collapse
Hello,
Can you help me ?
A tutorial would help me.
Thank you
dexterbot80 said:
Hello,
Hello, I mistakenly removed my phone's operating system. Can you help me put it back please?
hTC dowload mode
*** UNLOCKED ***
htc_himauhl PVT S-ON
LK-1.0.0.0000
RADIO-01.01_U114401011_117.00.61117G_2
OpenDSP-20.7.3.00535.8994_1012
OS-4.30.709.12
May 2 2017, 18:52:29(894012)
SD NOT MOUNTED
OTG NOT MOUNTED
File NOT FOUND
Click to expand...
Click to collapse
Google 4.30.709.12 htc ruu zip and look for androidfilehost links. Download the zip (2gb) to your computer / phone / tablet or whatever else you use.
Rename the zip file to 0PJAIMG.ZIP and copy it to the "external sd card" (not in a folder).
Reboot the phone into download mode via vol- and power. It should have written at the bottom of the screen "press up to flash".. Flash and wait for 5 minutes or so. If it fails to flash and you know you have the correct file just repeat the download mode then up to flash process.
Your data will be lost.
Good luck.
shivadow said:
Google 4.30.709.12 htc ruu zip and look for androidfilehost links. Download the zip (2gb) to your computer / phone / tablet or whatever else you use.
Rename the zip file to 0PJAIMG.ZIP and copy it to the "external sd card" (not in a folder).
Reboot the phone into download mode via vol- and power. It should have written at the bottom of the screen "press up to flash".. Flash and wait for 5 minutes or so. If it fails to flash and you know you have the correct file just repeat the download mode then up to flash process.
Your data will be lost.
Good luck.
Click to expand...
Click to collapse
Hello ,
1. I downloaded :
Asia TW Nougat Version (4.30.709.12)
M9_Deodexed_4.30.709.12.zip
md5: cebdefdd55c7215835c9de8889e98f5f
2. I renamed to 0PJAIMG.ZIP
3. I copy it to micro sd card
4. I insert the card in to the phone
5. I put the phone in download mode using Vol - and Power button
6. I get this message :
Security Warning
If you have a flash drive that is not officially released by HTC, you risk releasing your personal and financial information to unknown sources.
SD NOT MOUNTED
OTG NOT MOUNTED
FILE NOT FOUND
The firmware you have downloaded is not original. Find an original HTC file. It must be "signed".
Guys, some of the terms you're using aren't used correctly. That might cause confusion if someone who doesn't know it better reads this thread at a later point.
There's a difference between rom & firmware. (The original source isn't available anymore. That's why I linked an archived version.)
The deodexed file that is mentioned in this thread is a custom rom and not a firmware.
And there are no "signed firmware packs" that could save this phone since a firmware pack doesn't contain a rom. Since the phone's problem is that the rom got deleted re-flashing all partitions except for the system partition is quite pointless. Not to mention that there are no official firmware packs you could flash with S-ON. You'd need to extract the individual firmware files from either an OTA (since they're incremental you'll never get a complete set of firmware files this way) or a RUU (these actually contain the full firmware) and to flash them manually one after another. The firmware packs provided by Sneakyghost are custom made and can only get flashed with S-OFF.
What you're actually looking for is a RUU. It contains the firmware and the rom/system of a dedicated firmware version. However, these RUUs aren't "official" although they're made by HTC. HTC only distributes RUUs for their US M9 customers. The RUUs for the rest of the world got leaked by insiders. That's why you might need to pay for a download if no one else already re-uploaded a certain RUU to a free-to-download file hoster. One of those pay-wall websites where you can find a whole bunch of RUUs is e.g. easy-firmware.
Further Info can be found in the ReadMe thread.
Sent from my HTC U12+ using XDA Labs
You can use the M9 ReadMe Thread to get everything you need. Go to post #6 for the RUU section. There are multiple methods and downloads for your device there.
Moderator information: off topic posts are removed from this thread.
What is the issue:
Bootloop when charging from empty battery.
Vol-down + power: grey htc-logo for 20 seconds and reboots back to white htc-logo-splash-screen and keeps rebooting
Vol-up + Vol-down + power: white screen (bootloader-selection-screen)
At this moment fastboot recognizes the mobile on my win10-laptop.
Tried several roms with RUU through fastboot flash zip <rom.zip>
but Always get that it can't write to partition when S-mode = on.
Putting the rom.zip named P256IMG.zip on SD-card doesn't involve a prompt to update.
Could this be due to that it needs to be a newer or equal version? (latest version on the Phone is received through OTA and HTC didn't release a full RUU with the latest version.
At this moment I'm a bit lost what else I can do.
mistercash said:
What is the issue:
Bootloop when charging from empty battery.
Vol-down + power: grey htc-logo for 20 seconds and reboots back to white htc-logo-splash-screen and keeps rebooting
Vol-up + Vol-down + power: white screen (bootloader-selection-screen)
At this moment fastboot recognizes the mobile on my win10-laptop.
Tried several roms with RUU through fastboot flash zip <rom.zip>
but Always get that it can't write to partition when S-mode = on.
Putting the rom.zip named P256IMG.zip on SD-card doesn't involve a prompt to update.
Could this be due to that it needs to be a newer or equal version? (latest version on the Phone is received through OTA and HTC didn't release a full RUU with the latest version.
At this moment I'm a bit lost what else I can do.
Click to expand...
Click to collapse
There is already a thread about boot loops right above yours.
Then, RUU zip file needs to be named 2PS6IMG.ZIP
Tarima said:
There is already a thread about boot loops right above yours.
Then, RUU zip file needs to be named 2PS6IMG.ZIP
Click to expand...
Click to collapse
Yes, was a typo. I renamed rom.zip to 2PS6IMG.zip, but didn't work.
This is the latest version available, but this one is a OTA: OTA_PERFUME_UHL_M60_SENSE80GP_HTC_Europe_1.30.401.1-1.21.401.4_release_477325muqkxdpcc3r4aks3.zip
version lower is this one: 2PS6IMG_PE[email protected]60331.4_41.13_F_release_478442_signed_2_4.zip
But this rom.zip contains like 20 zip files like rom.zip_01.zip till _020.zip and one bin-file. is this ok to use?
Don't know if this the correct RUU to use.
My box says this as part-number: 99HAJH018-00, Model ID: 2PS6200
But this is probably a version too low to get recognised as equal or higher version by the downloader when put on sd-card.
I have read the complete threads here, but didn't get it to work.
mistercash said:
Yes, was a typo. I renamed rom.zip to 2PS6IMG.zip, but didn't work.
This is the latest version available, but this one is a OTA: OTA_PERFUME_UHL_M60_SENSE80GP_HTC_Europe_1.30.401.1-1.21.401.4_release_477325muqkxdpcc3r4aks3.zip
version lower is this one: 2PS6IMG_PE[email protected]60331.4_41.13_F_release_478442_signed_2_4.zip
But this rom.zip contains like 20 zip files like rom.zip_01.zip till _020.zip and one bin-file. is this ok to use?
Don't know if this the correct RUU to use.
My box says this as part-number: 99HAJH018-00, Model ID: 2PS6200
But this is probably a version too low to get recognised as equal or higher version by the downloader when put on sd-card.
I have read the complete threads here, but didn't get it to work.
Click to expand...
Click to collapse
What is your current software version? Post the output of getvar all
The thread can be closed, sorry for the disturbance.
But the mobile is not recognized anymore in windows. Think it completely got bricked.