Related
HTC DESIRE UNROOTING PROCESS, AND THE ANDROID HBOOT, FASTBOOT, AND RECOVERY MENU OPTIONS
(How to Revert to Stock/ What to do before taking my phone back to the service centre?/ How to restore my phone after a failed OTA update on a Rooted phone/My phone is stuck at the HTC Quietly brilliant screen/My boot animation keeps looping, What to do?)
by
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Courtesy:
To EddyOS for the Tutorial on getting the PB99IMG from the RUU
I didnt find any newbie friendly guides for unrooting the HTC Desire, on XDA. Even some external ones arent that easy to follow, unless you have a very good idea about what is going on.
The main purpose of this post is to benefit people who have got an SLCD bricked device on their hands with nothing displayed except a blank screen, and cannot remember the key sequences necessary to activate the unrooting process, or to run the OTA Update and get to Android recovery. You will note that I have added the time taken at each step in the process. This will benefit people with SLCD bricks waiting anxiously without seeing anything on screen.
For a complete guide on Unbricking an HTC Desire, please see my thread here.
There are two methods of unrooting an HTC Desire.
Methods:
Get the latest RUU for your region from Shipped Roms. This is an exe file. You can run this file directly from PC. Then connect your device when so prompted.
The second method is to flash the rom.zip directly from the Android bootloader interface, after renaming the Rom.zip (which is actually obtained from the RUU) to PB99IMG.zip [See EddyOS's excellent step-by-step guide for dummies, in the FAQ below]
Method1 does not need any explanation (If necessary, I will add illustrations of this process later along with error codes)
Method2 is illustrated below.
Note: The following post illustrates the actual steps necessary to unroot your HTC Desire by running the PB99IMG.zip. This is also the method to upgrade the software with the RUU, the last method to fix bootloops cause by a bad boot, and also the way to unbrick an SLCD bricked Desire. Note that another simple method exists to unroot the device, and that is by directly running the exe file of the RUU from Windows. Though simple, this is slightly riskier, since complications with Windows drivers, or a sudden power surge or PC reboot can semibrick/brick your device. The following method using PB99IMG.zip eliminates those problems.
Unrooting is just one of the steps necessary to unbrick an SLCD bricked HTC Desire. The process is a pain for these users because they cant see anything on the screen and left pressing keys in sequence, whose function they can only guess. Also they need to wait specific amounts of time before pressing the sequences.
I'm making visible the steps which the Android system proceeds through, when you run a PB99IMG.zip to unroot your Android device. I've also included the time taken before each step while running the WWE 2.29 RUU as PB99IMG.zip. The time isnt much different for other ROMs. To be sure, just give it about 30secs more than the time I've noted.
Initial steps:
Create a goldcard if you want to convert a branded Desire to unbranded, or vice versa, or to make a Desire of one region (CID) accept software written for a phone of another region.
After creating the goldcard, format it as FAT32. If more than one partition exist, delete the rest, and format one as Primary and FAT32.
Put the file PB99IMG.zip into the root of the goldcard. Note that the name must be PB99IMG.zip and not PB99IMG.zip.zip. Windows has a tendency to rename it as the latter.
If you dont already have the PB99IMG.zip, you can get it by running the RUU, and while the RUU is loaded (dont start the RUU upgrade. Just click on the exe, and when the welcome screen of RUU shows up,) search in your Temp folder for the file rom.zip. Hint: To quickly navigate to Temp, Type the following into the Run window: %TEMP% [If you still get this step confused, see EddyOS's excellent tutorial on this, in the FAQ below]
To run the PB99IMG.zip, just reboot with Vol- and power button pressed.
I'm describing the whole boot process below for Reference, though.
Hboot mode (Vol- & Power key. Key them pressed for a 5-6 secs
FOR INSTALLING ANY RUU AS PB99IMG.ZIP
Press Vol- , then w/o releasing it, press Power button + Vol –
After 3-4 secs, the following screen shows up momentarily:
· Fastboot
· Recovery
· Clear Storage
· Simlock
This shows the above few options for 2-3 seconds, and then directly checks for PB99IMG.ZIP. It displays:
SD Checking…
Loading…
PB99DIAG.ZIP
Pb99DIAG.nbh
PB99IMG.ZIP
When it finds PB99IMG.zip, it starts to load it (13 secs after you press the Vol- & power key)
It gives the next options after 2min 20seconds (for the WWE 2.29 RUU) from the initial key press of Vol- and Power key.
Parsing………………….[SD zip]
1. Bootloader
2. Radio V2
3. Radio_Cust
4. Boot
5. Recovery
6. System
7. Userdata
8. Splash1
9. Splash2
Do you want to update device?
<Vol Up> Yes
<Vol Down> No
So, net key sequences involved:
· Back+Power
· Power again
· Vol Up
If we chose No, next option:
Do you want to reboot device?
<Vol Up> Yes
<Vol Down> No
If you pressed Yes, then:
Update is in progress..
Do not power off your device.
1. Bootloader -OK
2. Radio V2 -OK
3. Radio_Cust -OK
4. Boot -OK
5. Recovery-Unzipping/Updating
6. System
7. Userdata
8. Splash1
9. Splash2
It cycles through each of these in turn. For me, it took exactly 2 min 17 secs for time when I chose to apply update, to when update was completed.
(Note: At times, it may update the bootloader and reboot. If you have an SLCD screen, when the device reboots, you may not see anything onscreen (black). At this point, it is notable that the device boots to Fastboot instead of Bootloader, so you will need to press Power button again to get it to resume the update process. Once it completes, you will be presented the options to reboot the device. So you just need to Press Vol + after some time)
It displays:
Update complete
So you want to reboot device?
<Vol Up> Yes
<Vol Down> No
Congratulations. Your phone is now officially unrooted.
On rebooting, HTC screen shows up for a few seconds.
Then a green Down arrow in a green circle shows up for another 5-6 seconds.
Then, HTC screen again.
Finally, HTC screen disappears and the HTC Quietly brilliant logo shows.
Your device now boots into the Android phone.
Total time taken: 6min 30 seconds.
If the Rom is incompatible with your SLCD device, at the reboot stage, you will hear the momentary vibration. Then after about 10-20secs, you will hear the HTC Quietly Brilliant tone. The phone will boot, and the keys light up after about a min, indicating that the Android system has booted up. Since the Rom is incompatible, there's still nothing on screen. To shutdown the booted up phone, press power key, then swipe your finger vertically up-down like you do to unlock your phone normally, which is exactly what you're doing. Then keep Power button pressed until the phone vibrates. This means it is presenting you with the Power menu. At this point press the trackball once, then once more. The phone will now shutdown. At this point you can flash your SLCD compatible update.zip (OTA) and unbrick it.
FASTBOOT mode
Back+Power key:
4 options:
· Bootloader (For running PB99IMG.zip)->Choose with Power key (This loads the Bootloader/Hboot mode)
· Reboot
· Reboot bootloader
· Power down
Bootloader (Hboot mode) or PB99IMG update mode.
Performs the following check on the PB99IMG.zip:
1. Bootloader
2. Radio V2
3. Radio_Cust
4. Boot
5. Recovery
6. System
7. Userdata
8. Splash1
9. Splash2
Do you want to start update?
Vol Up: Yes
Vol Down: No
So, net key sequences involved:
· Back+Power
· Power again
· Vol Up
If we chose No, next option:
Do you want to reboot device?
<Vol Up> Yes
<Vol Down> No
No brings up the following options:
· Fastboot
· Recovery
· Clear Storage
· Simlock
Frequently Asked Questions (FAQs) for Newbies
Frequently Asked Questions (FAQs) for Newbies
1. Why do I need to Unroot?
To take the device to service centre for warranty
To fix problems with Boot and Recovery unsolved by other methods
2. What are the methods of unrooting? Which is safer?
Basically both methods are the same. It is the process of flashing an original HTC software onto your ROM. One method involves running an .exe file from Windows, and the other is by running a file extracted from this exe file from the sdcard. The latter method is called the PB99IMG.zip method, because it involves renaming the rom file so extracted as PB99IMG.zip. This method is generally safer because the whole process can be completed from your phone itself. The method of running the exe is prone to corruption because of problems with Windows drivers, your Usb cable, Battery issues, and even a Windows System Failure or System Crash or Power Failure!
3. How do I get a PB99IMG.zip? [EddyOs's complete tutorial for Dummies]
(The illustrations and answer to this question has been provided by EddyOS)
If you still get lost, dont even bother to ask!!
1. Double-click on the RUU file and wait until you get to the first main screen
2. Move the window to the bottom of your screen because it can’t be minimised and will sit on top of all other windows
3. 3. Click on Start>Run and type ‘%temp%’. Then click ‘OK’
4. Look for the newest folder in the temp folder. Double-click on it
5.Copy the file called ‘rom’ to your Desktop
6. Rename the file called ‘rom’ to ‘PB99IMG’
7. Copy this file to the root of your SD card (root = not in any folders)
4. Do I need a Goldcard?
If you have a recent version of the RUU for your Device, available on Shipped Roms, you dont need a goldcard. This is the usual scenario for people who purchased their Desire in Europe, and so have an unbranded Desire. All Branded Desires need a correct branded version of the RUU, and any other RUU including WWE (Worldwide English, or European) RUU will not work for them. Also if an unbranded Desire user wishes to change RUU to a branded version, he will need a Goldcard. This is because all Desires have a particular software tag in the Rom, called the InfoCID. This dictates the Region code. For Eg. An Indian Desire is branded and has InfoCID of HTC__038. When you change a RUU to different region, what you actually do is reset the InfoCID setting. Changing the InfoCID setting requires a Goldcard.
5. What is a Goldcard?
It is a normal MicroUSB card specially prepared in such a way that its Sector 0 (which normally doesnt hold anything useful) is modified, so that it signals to the HTC RUU that the InfoCID may be changed.
6. How do I create a Goldcard?
Just download this tool (Credits and All Rights by [email protected]), and run it.
In case your card in phone cannot be detected by the PC, download and install Goldcard Helper from the market and use it to generate the Reverse CID
7. Can you tell me more about Goldcards?
Sure. I've already posted it for you. Read the FAQs in this thread.
8. I think I've bricked my Desire. I cant unroot it with your method. What can I do?
Follow my thread on Unbricking a Bricked Desire. Though it's written for SLCD device, it will work for AMOLED too. The chance of success depends on two essentials: 1-That you have a working goldcard, and 2-You have a compatible RUU (of version higher or equal to the current version)
Reserved for the future...
Hi,
Thanks for informative article. Can I install PB99IMG.zip using the standard clockworkmod @ recovery mode?
Edited: I tried using windows, it failed. I tried the 2nd method, but Desire does not reconize the PB99IMG.zip file and so nothing happens.
medomedo said:
Hi,
Thanks for informative article. Can I install PB99IMG.zip using the standard clockworkmod @ recovery mode?
Edited: I tried using windows, it failed. I tried the 2nd method, but Desire does not reconize the PB99IMG.zip file and so nothing happens.
Click to expand...
Click to collapse
When you mean you tried it in Windows, do you mean you connected the cable and ran the exe file? If so, what error did it give you?
You cant flash it via Clockwork. And you dont have to.
Assuming you have only one partition on your sdcard and it is formatted correctly as FAT32 and the PB99IMG.zip is placed in the root folder, and you press Vol- & Power button to start your Desire, it will detect the file and start the update process. Problems usually happen when the card is not formatted correctly, and the file is named PB99IMG.zip.zip and not just PB99IMG.zip. This is because Windows may not display the full filename including the zip extension.
one simple question
i wanted to root my phone so i could flash to a custom ROM, but i have since updated to 2.13.707.2 OTA, but i cant seem to find the RUU in shipped ROMs site...
could i use the 2.13.707.1 RUU to unroot?
Hi droidzone,
Thanks for the quick response. The error I got from windows 7 pro was (translated from German):
error 170: USB connection failure. The update software was not able to connect to mobile. Make sure the cable is connected to both PC and mobile.
My SD card is partitioned into FAT32 and a small parition ext3 for apps. This configuration is defacto for DeFrost, OpenDesire, and Oxygen ROMs. I moved the rom.zip file and renamed it using rootExprorer application to be 100% sure. When I go to recovery mode and then to Clockwork I can see the exact file name and its correct PB99IMG.zip (I am not sure if the system is case sensitive) but PB99IMG.zip is the exact name. Of course I restarted win7 few times but nothing changed. I need this because my mic is bricked like described in this thread
http://forum.xda-developers.com/showthread.php?p=9951668&posted=1
What can I try next? thanks!
medomedo said:
Hi droidzone,
Thanks for the quick response. The error I got from windows 7 pro was (translated from German):
error 170: USB connection failure. The update software was not able to connect to mobile. Make sure the cable is connected to both PC and mobile.
My SD card is partitioned into FAT32 and a small parition ext3 for apps. This configuration is defacto for DeFrost, OpenDesire, and Oxygen ROMs. I moved the rom.zip file and renamed it using rootExprorer application to be 100% sure. When I go to recovery mode and then to Clockwork I can see the exact file name and its correct PB99IMG.zip (I am not sure if the system is case sensitive) but PB99IMG.zip is the exact name. Of course I restarted win7 few times but nothing changed. I need this because my mic is bricked like described in this thread
http://forum.xda-developers.com/showthread.php?p=9951668&posted=1
What can I try next? thanks!
Click to expand...
Click to collapse
i wanted to root my phone so i could flash to a custom ROM, but i have since updated to 2.13.707.2 OTA, but i cant seem to find the RUU in shipped ROMs site...
could i use the 2.13.707.1 RUU to unroot?
Click to expand...
Click to collapse
It's worth a try.Normally an older version cant be used on top of a newer version. It will give a "main version is newer" error. A newer version will always work. If it still doesnt work for you, downgrading may be the only resort. Get Teppic's downgrade tool for that.
error 170: USB connection failure. The update software was not able to connect to mobile. Make sure the cable is connected to both PC and mobile.
Click to expand...
Click to collapse
Could be a Windows driver issue. The PB99IMG.zip method should work for you though. Remove the ext partition, and partition the whole card as one big FAT32 partn, format it once, and then put the file there again. It should work.
If it still wont work, use another sdcard, repeat these steps.
droidzone said:
It's worth a try.Normally an older version cant be used on top of a newer version. It will give a "main version is newer" error. A newer version will always work. If it still doesnt work for you, downgrading may be the only resort. Get Teppic's downgrade tool for that.
Click to expand...
Click to collapse
Thanks for clearing up for me...i know now what to prepare...
FYI, I used another SDcard with only FTA32 partition and it worked. Howerver it did not fix the mic problem. Thanks!
medomedo said:
FYI, I used another SDcard with only FTA32 partition and it worked. Howerver it did not fix the mic problem. Thanks!
Click to expand...
Click to collapse
Good..If even a new RUU installation didnt work, I'm guessing Hardware issues. Maybe a good time to get it checked.
I have a debranded Desire on 2.2, accidentally updated with an OTA yetserday without goldcard and have now lost wifi.
trying to downgrade with goldcard but it failing
tried PB99IMG method but get the following
On HBOOT , loads PB99IMG but states main version older update failed.
In recovery fails to open E: signature verification failed.
Any help gratefully received
stevep999 said:
I have a debranded Desire on 2.2, accidentally updated with an OTA yetserday without goldcard and have now lost wifi.
trying to downgrade with goldcard but it failing
tried PB99IMG method but get the following
On HBOOT , loads PB99IMG but states main version older update failed.
In recovery fails to open E: signature verification failed.
Any help gratefully received
Click to expand...
Click to collapse
You have a debranded Desire, you said.
Well then, the PB99IMG of the latest RUU should work for you.
Just flash it as I've described from Hboot.
Put the goldcard in just for safety, and do it.
Should work.
Hi Droid
Thanks for quick reply.
Can I just confirm a few bits . . .
Goldcard leaves 3 folders on SD ( android_secure, footprints,lost.dir)
Then copy and rename the RRU to PB99IMG and copy to SD.
Reboot to HBOOT and then get previous messages :-(
stevep999 said:
Hi Droid
Thanks for quick reply.
Can I just confirm a few bits . . .
Goldcard leaves 3 folders on SD ( android_secure, footprints,lost.dir)
Then copy and rename the RRU to PB99IMG and copy to SD.
Reboot to HBOOT and then get previous messages :-(
Click to expand...
Click to collapse
To be safe, do the foll verbatim:
Delete any additional partitions on goldcard (if any). The goldcard should have one big FAT32 partition
Format it as FAT32 once again with original allocation size
Transfer the PB99IMG.zip that I have linked in my post to the root.
Check the filename and be sure that it is not PB99IMG.zip.zip
Reboot in Hboot by Pressing the Vol- & Power key
The file will be detected and presented with menus
Follow the instructions in the OP
I'm guessing I don't need a goldcard with my unbranded desire?? But screwed if it does. Also what is the unbranded ruu currently as there is literally hundreds? Thanks
Sent from my HTC Desire
BTW, what does it mean WWE rom?
WWE - World Wide English
To others, if you've flashed the OTA without your gold card do it again manually WITH your gold card and you're good to go. Flashing a full RUU is only need if you can't fix it manually
HTC 123 said:
I'm guessing I don't need a goldcard with my unbranded desire?? But screwed if it does. Also what is the unbranded ruu currently as there is literally hundreds? Thanks
Sent from my HTC Desire
Click to expand...
Click to collapse
medomedo said:
BTW, what does it mean WWE rom?
Click to expand...
Click to collapse
EddyOS said:
WWE - World Wide English
To others, if you've flashed the OTA without your gold card do it again manually WITH your gold card and you're good to go. Flashing a full RUU is only need if you can't fix it manually
Click to expand...
Click to collapse
Try what Eddy said. If it still gives you trouble, do what I listed.
WWE ->European Unbranded version
The latest is what I linked.
Eddy
Got the link, can you just confirm process, please
Thanks in advance
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.
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??
Hi all,Any help will be greatly received,
my stock 10 started having random lock ups,freezes and reboots ,
it has now even decided to give itself a factory reset on its own WTF?
so i thought software has gone corrupt, so ive downloaded the correct firmware and put it on the sd,when i boot into download
mode from bootloader it says sd not mounted?? tried formatting sd card to fat 32 and ntfs.
it also has lost its recovery as just get the red exclamation icon,
and because it factory reset itself without me entering my pin google has set the 24hrs timer so i cant even get further than the google sign in page to root it and flash it that way...
please help
cheers
Markieboy said:
Hi all,Any help will be greatly received,
my stock 10 started having random lock ups,freezes and reboots ,
it has now even decided to give itself a factory reset on its own WTF?
so i thought software has gone corrupt, so ive downloaded the correct firmware and put it on the sd,when i boot into download
mode from bootloader it says sd not mounted?? tried formatting sd card to fat 32 and ntfs.
it also has lost its recovery as just get the red exclamation icon,
and because it factory reset itself without me entering my pin google has set the 24hrs timer so i cant even get further than the google sign in page to root it and flash it that way...
please help
cheers
Click to expand...
Click to collapse
Have you checked your Google account on a PC or other device ? check all is well there first
Lol flash twrp and install any rom.
if you are ok with losing all your data you can use a RUU to restore the system from your current state.
1. download this: https://androidfilehost.com/?fid=24671318762849095
2. rename the zip file to 2PS6IMG.zip
3. put it on your SD card and put it in your phone.
4. boot into download mode, it will recognise the zip and begin the ruu process.
5. once it's finished it will reboot; it might take a little longer than usual to boot but just wait about 5min or so.
done.
at a guess i'd say that if it doesn't work or it happens again then your board is probably cooked and you should start looking for a new phone...
---------- Post added at 07:50 PM ---------- Previous post was at 07:48 PM ----------
also when booting into stock recovery the red exclamation mark screen is normal; what you have to do is hold down the power button and press vol up and the recovery menu should appear.
diagonals said:
if you are ok with losing all your data you can use a RUU to restore the system from your current state.
1. download this: https://androidfilehost.com/?fid=24671318762849095
2. rename the zip file to 2PS6IMG.zip
3. put it on your SD card and put it in your phone.
4. boot into download mode, it will recognise the zip and begin the ruu process.
5. once it's finished it will reboot; it might take a little longer than usual to boot but just wait about 5min or so.
done.
at a guess i'd say that if it doesn't work or it happens again then your board is probably cooked and you should start looking for a new phone...
---------- Post added at 07:50 PM ---------- Previous post was at 07:48 PM ----------
also when booting into stock recovery the red exclamation mark screen is normal; what you have to do is hold down the power button and press vol up and the recovery menu should appear.
Click to expand...
Click to collapse
Are you sure this is the proper RUU for him? First of all, that RUU is super old. Probably too old for the OP to use unless he's S-Off (you can't go backwards with firmware while S-On)
Second of all, you don't even know which model he has. That RUU is for WWE/European. It won't work on US Unlocked/Sprint/Verizon/o2/T-mo etc...... but ONLY on a WWE branded device. You need matching MID and CID for the RUUs to work.
@Markieboy don't use that RUU. Boot to download mode and post here what it says next to "OS" and I or someone else can provide you with the appropriate one to use (although I'm not sure if it will work in this case).
Try this: If you can boot to download mode, you should be able to flash TWRP via fastboot (your bootloader is unlocked, correct?).
Then boot to TWRP > advanced > file manager then navigate to /data/system/ and delete the locksettings.db file. This will disable your lockscreen PIN/password.
xunholyx said:
Are you sure this is the proper RUU for him? First of all, that RUU is super old. Probably too old for the OP to use unless he's S-Off (you can't go backwards with firmware while S-On)
Second of all, you don't even know which model he has. That RUU is for WWE/European. It won't work on US Unlocked/Sprint/Verizon/o2/T-mo etc...... but ONLY on a WWE branded device. You need matching MID and CID for the RUUs to work.
@Markieboy don't use that RUU. Boot to download mode and post here what it says next to "OS" and I or someone else can provide you with the appropriate one to use (although I'm not sure if it will work in this case).
Try this: If you can boot to download mode, you should be able to flash TWRP via fastboot (your bootloader is unlocked, correct?).
Then boot to TWRP > advanced > file manager then navigate to /data/system/ and delete the locksettings.db file. This will disable your lockscreen PIN/password.
Click to expand...
Click to collapse
Hello, i have exactly the same issue battery health is like 65 percent when i look at accubattery and it crashes often wen battery is lower than 25% or so. It closes and never opens. Enters a boot loop. Sometimes it shuts down and enters boot loop too. Here is information that i see at download mode :
hTC download mode
*** LOCKED ***
htc_pmeuhl PVT S-ON
LK-1.0.0.0000
RADIO - [email protected]
OpenDSP - v.20.0.8996.00007_0809
OS-2.41.401.41
Aug 2 2017, 12:18:15(857212)
system info
show barcode
bla bla
Security checking falied GT_CONNECT_FAI
L
Security Warning
if you flash this phone with any rom bla bla
SD Mounted
OTG NOT MOUNTED
File NOT FOUND
xunholyx said:
Are you sure this is the proper RUU for him? First of all, that RUU is super old. Probably too old for the OP to use unless he's S-Off (you can't go backwards with firmware while S-On)
Second of all, you don't even know which model he has. That RUU is for WWE/European. It won't work on US Unlocked/Sprint/Verizon/o2/T-mo etc...... but ONLY on a WWE branded device. You need matching MID and CID for the RUUs to work.
@Markieboy don't use that RUU. Boot to download mode and post here what it says next to "OS" and I or someone else can provide you with the appropriate one to use (although I'm not sure if it will work in this case).
Try this: If you can boot to download mode, you should be able to flash TWRP via fastboot (your bootloader is unlocked, correct?).
Then boot to TWRP > advanced > file manager then navigate to /data/system/ and delete the locksettings.db file. This will disable your lockscreen PIN/password.
Click to expand...
Click to collapse
Hi no unfortunately the phone is bog standard I haven't unlocked the bootloader or anything. It's a non branded wwe firmware version....
i'd say pay for the s-off, there's no other way to fix your phone. but i still think your board is cooked.
Markieboy said:
Hi no unfortunately the phone is bog standard I haven't unlocked the bootloader or anything. It's a non branded wwe firmware version....
Click to expand...
Click to collapse
Sorry for taking so long to respond. This is the RUU.zip you should use. You can follow the instructions a few posts back, just use this download instead of the one linked.
Markieboy said:
Hi no unfortunately the phone is bog standard I haven't unlocked the bootloader or anything. It's a non branded wwe firmware version....
Click to expand...
Click to collapse
Many thanks... Things have been resolved now,, the missus took it into carphonewarehouse, and they said because it's a software issue it'll be repaired free! Phones about a year old...
Well it came back with the repair report...
NEW MAIN BOARD firred
NEW USB C PORT fitted
NEW BATTERY fitted
wow.. Don't mind if I do.. Lol
Markieboy said:
Many thanks... Things have been resolved now,, the missus took it into carphonewarehouse, and they said because it's a software issue it'll be repaired free! Phones about a year old...
Well it came back with the repair report...
NEW MAIN BOARD firred
NEW USB C PORT fitted
NEW BATTERY fitted
wow.. Don't mind if I do.. Lol
Click to expand...
Click to collapse
Are you saying they replaced those? on the house? I'm
Markieboy said:
Many thanks... Things have been resolved now,, the missus took it into carphonewarehouse, and they said because it's a software issue it'll be repaired free! Phones about a year old...
Well it came back with the repair report...
NEW MAIN BOARD firred
NEW USB C PORT fitted
NEW BATTERY fitted
wow.. Don't mind if I do.. Lol
Click to expand...
Click to collapse
The question is, what were doing on that phone to cook all these? Mining Bitcoin?
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.