Database Info

RUU Updates HTC: BE CAREFUL

--- Updated and simplified
Updates from HTC are randomly released for countries and regions. These Update may lock your phone. As of today, phones can be unlocked again by using the GOLDCARD approach. However, there is a much simpler way to prevent bad things from happening:
If you like flashing HTC roms and have no intention to lock your phone, follow these steps:
On the PC
1. Double Click the .exe from the update. Wait for the first window to appear (DO NOT CONNECT YOUR PHONE). Don't close the application but do not continue
2. Open explorer and navigate to the hidden directory:
Windows 7: \users\$username$\AppData\Local\Temp\... followed by something like ...\{2A3DF7FC-1693-4C53-8883-6CF09DED700D}\...
Vista: documents and settings\.....
3. You should find the install application files along with a file "Rom.zip" (40 to 90 Megs)
4. Extract the ROM.zip to your SDK Tools directory, where fastboot.exe resides
5. open command shell and navigate to your Tools directory (supposing SDK, adb and fastboot are installed)
On the Phone
6. Enter recovery console on phone (press "home" + then "on")
7. Do a nandroid backup
8. Select Wipe your phone
9. Hold "back" and select "reboot system" in recovery to enter Fastboot mode
On the PC
10. Type: "fastboot flash boot boot.img" .... wait to complete
11. Type: "fastboot flash system system.img" .... wait to complete
12. Type: "fastboot flash userdata userdata.img" .... wait to complete
13. [Optional] Type: "fastboot flash radio radio.img" .... wait to complete (note: some HTC radios locked windows mobile phones. I am not sure whether this applies for Android)
14. Reboot your phone
15. Keep the update if you like it, revert to backup via recovery and nandroid in case you don't
And sorry for any confusion caused...
Regards,
fde

Thanks a lot mate... I will try the official sense for my magic then using this method first =D...

Are you sure....
That this will work? I have made the RUU Flash: RUU_Sapphire_HTC_Europe_2.20.401.2_HTC_Nordic_release_signed_NoDriver
And that resulted in:
HBOOT-1-33-0014
CPLD-12
RADIO-3-22-23-18
I don't understand what you are meaning about the Radio.img file.
And what about the HBOOT file?

Yes it works. Just verfied it aigain. What the RUU package does is:
1. Extract the application to a temp file
2. Use ADB to flash the ROM to your phone
By the approach described in the first post, the application unpacks itself into a temp directory. This allows you to access the ROM-File which is stored as ROM.zip or something similar. By moving only the vital Boot, System and Userdata, you avoid flashing your Recovery console or Bootloader (Hboot).
It implies of course, that you DO NOT continue with the RUU application as soon as the first window becomes visible. (I will adjust the above Tutorial and make it simpler).

Problem
But the problem is that I allready have flashed my phone, is this the way to revert is så I can root it again and put custom roms on it again?

same here
ZeaDK said:
But the problem is that I allready have flashed my phone, is this the way to revert is så I can root it again and put custom roms on it again?
Click to expand...
Click to collapse
I also want to know how I can flash new ROM since people said that my spl is perfected after upgrading
I was learned that we need to use goldcard method to root again.
In our case, any idea which ROM to use as we gotta use higher ROM?
Or are we able to gain root access without touching the existing ROM?
Now even cannot boot to recovery mode.
So stupid to upgrade it although the ROM is stable and fast but no root access sucks.
any help would be appreciated.
thanks,
thihaz

Well I guess my post was too late then.
However, the GOLDCARD approach, is said to allow succesful flashing of the engineering SPL or 1.33.0009. Do that and your back in business.
Regards,
fde

feicher said:
Well I guess my post was too late then.
However, the GOLDCARD approach, is said to allow succesful flashing of the engineering SPL or 1.33.0009. Do that and your back in business.
Regards,
fde
Click to expand...
Click to collapse
The problem with the goldcard method is that you lose the roms as well...

Sir, would you please let me know how to flashing engineering SPL, right now i have HBoot-1.76.007 which shipped with the Singapore HTC sense rom.
BTW: i don't care i will lose the rom or not.
Many thanks!
I flashed using RUU_Sapphire_HTC_Asia_WWE_2.16.707.3_SG_release_signed_NoDriver.exe with golden card, but got "check main rom verion" error msg.
then flashed using RUU_Sapphire_HTC_Asia_WWE_2.53.707.2_SEA_test_signed_NoDriver.exe with golden card, same error msg again.
I really have no idea how to flash back to engineering SPL, i'm stuck in Singapore HTC sense rom.
feicher said:
Well I guess my post was too late then.
However, the GOLDCARD approach, is said to allow succesful flashing of the engineering SPL or 1.33.0009. Do that and your back in business.
Regards,
fde
Click to expand...
Click to collapse

i got 1 rom.zip(11mb) & another one rom1.zip(89mb).
But both I also can't unzip. Any idea? Thanks.

radonsg said:
i got 1 rom.zip(11mb) & another one rom1.zip(89mb).
But both I also can't unzip. Any idea? Thanks.
Click to expand...
Click to collapse
I did this twice on a Swiss Update, which btw wasn't worth applying. Just by the Size it's rom1.zip.
Let me download the Singapore and see what I can do.... But then looking at the guys post it seems the second file in the post is what you need. Download this package and only flash boot, system and data in fastboot mode. (From Step 4. onward in the guide). Anyway I will have a look.

phygee said:
Sir, would you please let me know how to flashing engineering SPL, right now i have HBoot-1.76.007 which shipped with the Singapore HTC sense rom.
BTW: i don't care i will lose the rom or not.
Many thanks!
I flashed using RUU_Sapphire_HTC_Asia_WWE_2.16.707.3_SG_release_signed_NoDriver.exe with golden card, but got "check main rom verion" error msg.
then flashed using RUU_Sapphire_HTC_Asia_WWE_2.53.707.2_SEA_test_signed_NoDriver.exe with golden card, same error msg again.
I really have no idea how to flash back to engineering SPL, i'm stuck in Singapore HTC sense rom.
Click to expand...
Click to collapse
Please follow the GOLDCARD method. I am not a recovery expert. I try to be cautious and was lucky until now (so I never tried it myself, but it is reported to work). Sorry for that. If :No-Frost: knows of a better guide with regard to GOLDCARD, please post!
Regards,
fde

feicher said:
Please follow the GOLDCARD method. I am not a recovery expert. I try to be cautious and was lucky until now (so I never tried it myself, but it is reported to work). Sorry for that. If :No-Frost: knows of a better guide with regard to GOLDCARD, please post!
Regards,
fde
Click to expand...
Click to collapse
For now the only method I know is the goldcard one... But in my country, using the goldcard method, makes the magics lose the 3g, edge or any internet mobile connection... =(...

Be careful, by using this method you can not upgrade to Snese UI (example TW). The reason being system image in Sense UI is larger than the previous 1.5 ROM system image, so system partition needs to be re-sized, which the RUU update does it for you. Otherwise you are struck with failed system image flashing.

signiture verifiaction fail
I get a signiture verifiaction fail when trying to write the .img files using fastboot. Any suggestions?

[Tutorial][S4/S3] How to use OTA zip to get back to Stock OS

Lately, many people, including myself, have been at a disadvantage of not having an official RUU for JellyBean so that stock environment can be achieved. Although sometimes, OTA's are available which can do the job. Hence this Tutorial. Also this saves the effort to do S-OFF/SuperCID which often brings along more problems.
This Tutorial, in principle, can be applied to both S4 and S3 variants.
All thanks to @xander1993 at the VilleC2 Development Section who created the original thread Here. Though somewhat unclear and related to VilleC2, I thought of making a thorough guide for Ville with some minor changes.
/////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////
For T-MOBILE UK Users: (UK people with other operators e.g Three, Vodafone etc can also try the Jellybean Nandroid backup IF their firmware is upgraded to that of Jellybean)
ICS Users: Those stuck on ICS custom ROMs and can't get stock, Use This RUU to get to stock ICS and then update to Jellybean via System Updates Check. Thanks to @ppm48
Jellybean Users:Those stuck on Jellybean custom ROMs wanting to get stock, I have a Stock Jellybean 4.1.1 Nandroid backup for you guys Here Since there isn't any OTA.zip for T-Mobile UK for Jellybean. You can just flash this Nandroid right away without using this tutorial. Again, Thanks to @ppm48 for this. Also, if you have bootloops after restoring this backup, flash a Jellybean Sense boot.img.
Additionally refer to this post by @mkoev , should prove a lot helpful. Then you can follow the tutorial.
/////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////
For OPTUS Users with CID OPTUS001: (All thanks to @salac)
Get the modified OTA.zip Here. by @salac
salac said:
Follow the instructions from step 12.
Step 14. Flashing the firmware.zip worked the second try for me
Step 22. I did flash the boot.img to make sure it will work since I don't think I had the original one.
Good Luck
Click to expand...
Click to collapse
Optus users please follow @salac 's post above to flash the OTA.zip
/////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////
Pre-requisites:
1. Notepad++
2. 7-Zip (Recommended)
3. ADB+Fastboot (Get it Here)
4. HTC drivers (Standalone OR HTC Sync Manager Drivers)
5. Unlock_code.bin from HTCDev to unlock bootloader.
6. Any OS (Custom/Stock) present on the phone. (I have not tested it for phones without any OS, you may try it at your own risk and post results here) Not Needed anymore.
Common Steps:
In this guide, I will ask you to go to fastboot/adb so you should know how you would do that. (All fastboot/adb commands are to be given via Command Prompt from PC)
To execute Fastboot Commands:
- Go to fastboot folder on your PC
- Go to fastboot via bootloader on your phone
- Connect the Phone to PC and on the Phone it should say Fastboot - USB Mode
- Now in the fastboot folder on your PC, Hold Shift + Right-Click and click Open Command Window Here
- Now you can enter commands given in the guide for fastboot.
To execute ADB Commands:
- Same procedure except that you don't need to go to fasboot on your phone. You can execute adb commands while in Android OS/desktop.
To boot into Bootloader:
- While the phone is turned off, Press Volume Down + Power Button simultaneously.
OR
- If you are in Android OS, use the following adb command to boot into bootloader:
Code:
adb reboot bootloader
OR
- If you want to reboot into bootloader from fastboot:
Code:
fastboot reboot-bootloader
/////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////
Caution for SuperCID users: Please click the CROSS button on your Browser Tab, as flashing this is not intended for you. Either don't flash the OTA.zip, which will brick your phone if you do, OR change your CID to original one. e.g. H3G__001, BM___001, ORANG001
/////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////
Procedure:
- ** - ** - ** - Make Nandroid Backups before you do anything, remember you are doing this at your own risk - ** - ** - ** -
1. Download a OTA.zip – Most likely from Here. (You can rename the OTA file which usually has a long name to simply OTA.zip for ease)
2. Extract firmware.zip from OTA.zip. Then extract boot.img from firmware.zip. For now, copy Boot.img to ADB+Fastboot Folder..
3. Now to match the CID of your phone. You can get the CID of your phone via CID Getter from Play Store. Once opened, at the top will be your CID in Red color.
Alternatively, You can also get CID of your phone via Fastboot. Command for that is:
Code:
fastboot getvar cid
and it should display your CID.
4. Inside firmware.zip, look for android-info.txt. Supported CIDs should be mentioned inside this file. If it matches with that of your phone, Proceed otherwise stop and don't put yourself into more problems. (CID Match Exception: This 4th step may not be applicable to you if & only if you are to skip steps 11 to 16, if this is the case, you may flash OTA.zip skipping steps 11 to 16; Read step 10 for more info and then come back here)
5. We need to remove some code lines from inside the OTA.zip. For this, Open the OTA.zip with 7-zip (Right-click ---> 7-zip ---> Open Archive).
6. Head over to META-INF\com\google\android and find a file named updater-script. Drag it out of the archive to the folder/desktop where you can edit it. You should make an extra copy of this file.
7. Once you drag it out, delete the original updater-script inside the archive. It will recompress OTA.zip.
8. Edit with Notepad++ the extracted updater-script file. Find these lines (in the beginning of the file) and delete them altogether:
Code:
[COLOR="Purple"]assert(check_cid(getprop("ro.cid"), "00000000" , "11111111" ,
"22222222" , "33333333" , "44444444" , "55555555" , "66666666" ,
"77777777" , "88888888" , "99999999" ,
"BM___001") == "t");[/COLOR]
ifelse( is_ship_bootloader(getprop("ro.bootloader")) == "t" ,
assert(check_mid("full", "PJ4011000") == "t");,
assert(check_mid("simple", "PJ4011000") == "t");
);
You should delete these lines up to exact semi-colon ; at the end. (the purple lines with different CIDs can be different from those mentioned here, so no need to panic, just delete them)
9. Once edited, Copy this edited updater-script into the OTA.zip archive at the same location from which it was removed. It will recompress OTA.zip. You may now transfer OTA.zip to your SD-Card on your phone.
10. If you previously updated to JellyBean via OTA (Or if you have the exact or newer firmware on your phone than that present inside OTA.zip), skip steps 11 to 16. For example, if you have HBOOT Version 2.15.0000/2.13.0000 or above, it means you have already upgraded to Jellybean firmware so no need for Steps 11 to 16.
In case, if you are to proceed to step 11, that is if you are to flash firmware.zip, make sure to match CID as mentioned in step 4 to avoid any bricks. This is especially useful for those who have ICS and want to get stock JB or those on JB but want complete stock HBOOT, recovery etc.
11. Place firmware.zip extracted from OTA.zip inside ADB + Fastboot Folder.
12. Lock the bootloader, if unlocked. For this, go to fastboot on your phone and give the command:
Code:
fastboot oem lock
The phone reboots after this.
13. While in Android OS/Desktop, fire up Command window on PC to give the following ADB command to boot into OEM Update Mode.
Code:
adb reboot oem-78
OR (if you can't access OS to execute adb)
From Fastboot:
Code:
fastboot oem rebootRUU
You should be seeing HTC logo.
14. While in OEM Update Mode, give the following fastboot command to flash firmware:
Code:
fastboot flash zip firmware.zip
If it fails with error and doesn't show any Green Progressbar, keep trying the above command. Usually works after a few tries.
********** DO NOT REBOOT MANUALLY UNTIL IT FINISHES FLASHING FIRMWARE OR YOU'LL BRICK YOUR PHONE *************
15. Once firmware is updated, reboot into bootloader. Go into fastboot.
16. Place Unlock_code.bin inside ADB + Fastboot Folder. Use the following fastboot command to unlock your bootloader again. (This will wipe your phone except for SD, so you must make a backup before doing this)
Code:
[COLOR="Blue"]fastboot flash unlocktoken Unlock_code.bin[/COLOR]
17. Download a recovery. Preferred Recovery is TWRP 2.3.3.0 and I have not tested this guide with any other version. Put the recovery in the ADB + Fastboot folder.
18. Now go into bootloader again. This time to flash the recovery anew.
Code:
fastboot flash recovery recovery.img
19. Now go to the recovery via bootloader. Wipe data/factory reset, cache, dalvik.
20. Restore the Nandroid backup you had made earlier.
21. Now Flash the OTA.zip which is on your SD-Card. It should flash fine.
22. Go to fastboot via bootloader. We are now going to flash kernel with the following command, boot.img you had earlier copied to ADB+Fastboot folder.
Code:
fastboot flash boot boot.img
23. Reboot to the OS and you should see complete stock JB OS.
--------------------------------------------------------------------------------------------------------------------------------------------------------
Please Rate the thread and Hit the Thanks button if this tutorial helped you!

I am trying to use your method to get back to stock instead of the RUU method since I am on Mac.
The problem I am running into is that the best OS X alternative to 7zip is an app called BetterZip with wich the recompressed OTA.zip is of different size compared to the original (633MB vs. 647.3MB).
Do you think this is likely to cause problems when flashing the modified OTA.zip?

mortek said:
I am trying to use your method to get back to stock instead of the RUU method since I am on Mac.
The problem I am running into is that the best OS X alternative to 7zip is an app called BetterZip with wich the recompressed OTA.zip is of different size compared to the original (633MB vs. 647.3MB).
Do you think this is likely to cause problems when flashing the modified OTA.zip?
Click to expand...
Click to collapse
Well, When I edited OTA.zip, it was the same size before/after. But maybe OS X uses different compression values.
I think you should go ahead with it and try it.

I am stuck.
Since my phone is bricked and it can't boot into the ROM I cannot issue the ADB command from step 13 while in fastboot :/

mortek said:
I am trying to use your method to get back to stock instead of the RUU method since I am on Mac.
.......................
Do you think this is likely to cause problems when flashing the modified OTA.zip?
Click to expand...
Click to collapse
Can you use Winzip/Winrar? Might want to check with those two..

mortek said:
I am stuck.
Since my phone is bricked and it can't boot into the ROM I cannot issue the ADB command from step 13 while in fastboot :/
Click to expand...
Click to collapse
last time you flashed was a Viper rom I think. So What firmware did you flash? if it was that of JB firmware then it's ok to skip the Firmware Flashing steps.
Edit: I have updated step 13. If you can't use ADB, use the fastboot command.

khan.orak said:
last time you flashed was a Viper rom I think. So What firmware did you flash? if it was that of JB firmware then it's ok to skip the Firmware Flashing steps.
Edit: I have updated step 13. If you can't use ADB, use the fastboot command.
Click to expand...
Click to collapse
The OTA.zip was flashed successfully but in the recovery's log there is a line which reads "E:unknown command [firmware]".
The last ROM i flashed was indeed ViperRom but I didn't flash any firmware manually. Should I have done so? I didn't see such an instruction in the respective thread.
Edit:
I just saw your edit. I'll try the fastboot command and report back asap. Thanks.

mortek said:
The OTA.zip was flashed successfully but in the recovery's log there is a line which reads "E:unknown command [firmware]".
The last ROM i flashed was indeed ViperRom but I didn't flash any firmware manually. Should I have done so? I didn't see such an instruction in the respective thread.
Edit:
I just saw your edit. I'll try the fastboot command and report back asap. Thanks.
Click to expand...
Click to collapse
Actually, I had read your post where you mentioned that you used AOSP firmware. Maybe that is a bit different than the stock firmware. If it poses problems, you might need to flash the stock one, present inside OTA.zip.
Also flash the stock kernel if you find that the ROM is behaving oddly.

khan.orak said:
Actually, I had read your post where you mentioned that you used AOSP firmware. Maybe that is a bit different than the stock firmware. If it poses problems, you might need to flash the stock one, present inside OTA.zip.
Also flash the stock kernel if you find that the ROM is behaving oddly.
Click to expand...
Click to collapse
The fastboot command worked fine so I flashed the stock firmware and the stock kernel, flashed the OTA.zip, rebooted and I am again stuck in a bootloop :/
Might be the OS X recompression. I will try again with different options.
Most likely the solution should be to get stock recovery, perform a "clear storage" command and then resume flashing. Problem is I am not aware of an alternative to the RUU method for that.

mortek said:
The fastboot command worked fine so I flashed the stock firmware and the stock kernel, flashed the OTA.zip, rebooted and I am again stuck in a bootloop :/
Might be the OS X recompression. I will try again with different options.
Most likely the solution should be to get stock recovery, perform a "clear storage" command and then resume flashing. Problem is I am not aware of an alternative to the RUU method for that.
Click to expand...
Click to collapse
Hmmm that's strange.
I had read somewhere that formatting SD card with Stock Recovery corrects some problems while using SD.
Stock Recovery is present inside firmware.zip by the name of recovery.img. might want to flash it and clear storage. Stock recovery can be flashed using the same method as custom recovery. Refer to Steps 17,18 to flash it.

khan.orak said:
Hmmm that's strange.
I had read somewhere that formatting SD card with Stock Recovery corrects some problems while using SD.
Stock Recovery is present inside firmware.zip by the name of recovery.img. might want to flash it and clear storage. Stock recovery can be flashed using the same method as custom recovery. Refer to Steps 17,18 to flash it.
Click to expand...
Click to collapse
I flashed the stock recovery but I am still having bootloops with the stock ROM
Although, I flashed Viper rom and after several reboots it finally booted!
The truth is that I am not sure the sdcard won't get corrupt the next time my phone reboots, but its better than having a bricked phone.
I'll keep on digging on the sdcard corruption by reboot issue.
Thanks again.

mortek said:
I flashed the stock recovery but I am still having bootloops with the stock ROM
Although, I flashed Viper rom and after several reboots it finally booted!
The truth is that I am not sure the sdcard won't get corrupt the next time my phone reboots, but its better than having a bricked phone.
I'll keep on digging on the sdcard corruption by reboot issue.
Thanks again.
Click to expand...
Click to collapse
After this, the last thing on my mind is the HBOOT. You can flash original HBOOT 2.15 anew with the help of this post http://forum.xda-developers.com/showpost.php?p=39216236&postcount=274
But if the bootloops persist even after trying all of this, maybe the car charger has done something to the battery or some other hardware part.
Best of luck!

khan.orak said:
After this, the last thing on my mind is the HBOOT. You can flash original HBOOT 2.15 anew with the help of this post http://forum.xda-developers.com/showpost.php?p=39216236&postcount=274
But if the bootloops persist even after trying all of this, maybe the car charger has done something to the battery or some other hardware part.
Best of luck!
Click to expand...
Click to collapse
I rebooted the phone in order to flash an OTA for the Viper ROM and I went into the familiar bootloop again.
So I tried flashing the original HBOOT 2.15 using the method you pointed out and I got this reply:
sending 'zip' (400 KB)...
OKAY [ 0.226s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (remote: 99 unknown fail)
finished. total time: 1.735s
I then tried clearing storage with stock recovery but once again I am stuck with that bootloop. :s

mortek said:
I rebooted the phone in order to flash an OTA for the Viper ROM and I went into the familiar bootloop again.
So I tried flashing the original HBOOT 2.15 using the method you pointed out and I got this reply:
...........
I then tried clearing storage with stock recovery but once again I am stuck with that bootloop. :s
Click to expand...
Click to collapse
I suspect hardware failure.
Sent from my HTC One S using Tapatalk 4 Beta

Trying to get back to stock so I can send my phone in for repairs, followed all your steps, and I'm coming from TrickDroid 10. Previously, I had the Rogers/Fido 4.1.1 OTA which brought my hboot to 2.15. I downloaded this OTA , followed all your steps exactly but when I tried flashing the OTA.zip I get the following error:
E:Error in /sdcard/OTA.zip
(Status 6)
Error flashing zip '/sdcard/OTA.zip'
Updating partition details...
Then in bold, red letter it says "Failed" near the menus.

booenson said:
Trying to get back to stock so I can send my phone in for repairs, followed all your steps, and I'm coming from TrickDroid 10. Previously, I had the Rogers/Fido 4.1.1 OTA which brought my hboot to 2.15. I downloaded this OTA , followed all your steps exactly but when I tried flashing the OTA.zip I get the following error:
E:Error in /sdcard/OTA.zip
(Status 6)
Error flashing zip '/sdcard/OTA.zip'
Updating partition details...
Then in bold, red letter it says "Failed" near the menus.
Click to expand...
Click to collapse
What recovery did you use? And did you edit updater script using notepad++?
Edit: Yup, after searching, Error Status 6 appears when you edit the UPDATER-SCRIPT using wordpad/windows editor which messes all that is inside it. Use Notepad++

khan.orak said:
What recovery did you use? And did you edit updater script using notepad++?
Click to expand...
Click to collapse
TWRP 2.4.1.0. No, I used notepad, but after googling and reading the differences between notepad++ and notepad, I will have to re edit with notepad++. Will try again tomorrow when I have more time, I still need to use this phone for work and can't have it bricked lol

Tried this again, flash went through and then flashed the boot.img included with the OTA zip, and my phones stuck at the "htc one" loading screen
Edit: relocked, flashed the stock recovery, thought it was still stuck at the loading screen so I unlocked it then went to install TWRP again to restore my nandroid, and it decided to finally boot. I guess I just needed to give it more time, currently back on 4.1.1, time to send this thing in under warranty so I can get my 3G/HSPA+ fixed. Thanks!

Just wondering, am I able to use an ota from another carrier to update my firmware and hboot as long as it fits my Cid? I believe my Cid is the global 001
Sent from my One S using xda app-developers app

asdfasdfvful said:
Just wondering, am I able to use an ota from another carrier to update my firmware and hboot as long as it fits my Cid? I believe my Cid is the global 001
Sent from my One S using xda app-developers app
Click to expand...
Click to collapse
I think yes. You can check if you CID is supported. It is inside the OTA.zip\firmware.zip, a file named android-info.txt and the supported CIDs will be there.
Edit: You should first check your CID. Download CID GETTER from Play Store. Shows CID in red on top.

Marshmallow Rom that will update all??

I'm currently on Verizon Version :5.0.1 Software :4.17.605.5. Is there a Marshmallow Rom that I can flash that will update firmware and give me the security/stagefrieght patches that verizon put out months ago? I'm rooted and S-off.

beeper10 said:
I'm currently on Verizon Version :5.0.1 Software :4.17.605.5. Is there a Marshmallow Rom that I can flash that will update firmware and give me the security/stagefrieght patches that verizon put out months ago? I'm rooted and S-off.
Click to expand...
Click to collapse
You can run MM ROMs, yes. There is one from Santod040 that is based off HTC Sense, and one by enewman17 that is based off GPe (Google Play edition)
There is no MM firmware however, until HTC releases it to us.
You can flash the latest 4.17.605.9 LP firmware, and run those above said MM ROMs

Where would I find and how would I flash the firmware..... Through twrp?

beeper10 said:
Where would I find and how would I flash the firmware..... Through twrp?
Click to expand...
Click to collapse
Verizon m8 Development forum: LINK
Latest Verizon firmware and instructions: LINK
Marshmallow Google Play Edition for Vzw m8: LINK
Marshmallow Sense 7 for Vzw m8: LINK

I tried updating the firmware with installing the above zip and it fails.

I've tried to flash the all in one update a bunch of times and it continuously fails.

beeper10 said:
I've tried to flash the all in one update a bunch of times and it continuously fails.
Click to expand...
Click to collapse
Need more info then "it fails".
Exact error or issue you encounter.
Pasting the terminal input and output here would be most useful.
Hard to instruct you any further from what little info you gave.

I'm doing it from the phone and there's no way I can copy and paste the results..... I tried to take a screen shot but that wouldn't work either. It doesn't give a reason it just goes to install and fails. Not sure how to give more info?

Here's a couple pictures of the issue.

beeper10 said:
Here's a couple pictures of the issue.
Click to expand...
Click to collapse
You don't flash it in recovery...
It fails because you aren't following the instructions given...
Copied from Santods thread:
http://forum.xda-developers.com/showpost.php?p=62734094&postcount=2
Place the zip in your fastboot/adb directory on your computer.
Put the device in fastboot mode
(Volume down and power until menu appears, select fastboot using power button)
Connect the device to the computer
Enter the following commands from terminal/command prompt in the fastboot directory, one at a time:
fastboot oem rebootRUU (this puts the device in RUU mode)
fastboot flash zip firmware.zip (rename file to firmware.zip to make it simple/optional)
It will say that the update did not finish, to flush again, so repeat the above step:
fastboot flash zip firmware.zip
Important: the flash process halts at around 75% to 90% on phone screen! This is normal and a safety precaution!
The last few percent is the reboot, which is NOT happening automatically, so you get a chance to check the console output before reboot to make sure it is safe to reboot!
The bar will only fill up to 100% once you type the following command:
fastboot reboot-bootloader (this reboots the device to bootloader)

I left my computer at work... Is there anyway to do it from the phone?

beeper10 said:
I left my computer at work... Is there anyway to do it from the phone?
Click to expand...
Click to collapse
Yes... By using an sdcard...
Rename file to 0P6BIMG.zip and Copy 0P6BIMG.zip to root of a physical SD. No exfat! No internal storage!
Reboot phone to bootloader and follow prompts once furmware is detected by phone.

That I have! That's were I was trying to flash it from.

beeper10 said:
That I have! That's were I was trying to flash it from.
Click to expand...
Click to collapse
Again.... You do NOT flash in recovery.
And I'll post again...
Please follow the instructions.
Rename file to 0P6BIMG.zip and Copy 0P6BIMG.zip to root of a physical SD. No exfat! No internal storage!
Reboot phone to bootloader and follow prompts once firmware is detected by phone.

Flash RUU with SD card method

Hi all, I am not sure if any of you is useing this method to RUU back your device but if you dont want to mess with fastboot and so on there is actually a very easy way to do it. the ony thing you need is RUU and sdcard.
1. rename RUU to 2PQ9IMG.zip
2. copy zip in the root of your sd card. - external card / not internal - it will not work
3. reboot to download mode, if for some reason you cant/are not able to/, reboot to bootloader and then select download mode
4. your device will pick up the zip file and flash it.
5.follow on screen instructions and enjoy your RUU-ed htc one a9
This method of flashing ruu is not new, it has been around for a while, just the name of the zip is always different.
I learned this when i had htc one S and htc one m8.

Will it work with S-off too ? I have sprint variant and want to get back to stock and receive OTAs

Yes, works with S-Off!
With S-off you can install any RUU by setting up the correct SID/MID before flashing the RUU.

Fischfuss said:
Yes, works with S-Off!
With S-off you can install any RUU by setting up the correct SID/MID before flashing the RUU.
Click to expand...
Click to collapse
and how we are supposed to do that ? well I got this phone in used condition.. its sprint and im using it outside US.. so it is network unlocked and twrp installed .. I'm an old htc user but not new to flashing and rooting .. never tried to s-off any of my devices before.. so I was wondering what more is needed to flash ruu to get back stock when I'm S-off

If you just want to get back to the stock system the Phone came with, theres nothing more to do then flashing the correct RUU.
Only if you want to change from sprint to for example Europe version, you have to setup the correct SID/MID before flashing and for this you need to be S-Off

Probably self-evident, but where do I download the RUU.zip?

OS and Radio needed
fahadmeyo said:
and how we are supposed to do that ? well I got this phone in used condition.. its sprint and im using it outside US.. so it is network unlocked and twrp installed .. I'm an old htc user but not new to flashing and rooting .. never tried to s-off any of my devices before.. so I was wondering what more is needed to flash ruu to get back stock when I'm S-off
Click to expand...
Click to collapse
I accidently deleted the OS and gave my phone for repairing as I am not used to flashing and rooting stuff.
but after that I am not able to use my cellphone on data connections, mobile data disconnected error .
Can you please send me the radio version and OS version details so I can install the same to use my cellphone. Mine is also Sprint A9. Also any further help will be highly appreciated.

Tominozh, thanks for your post. I'm having some troubles with my HTC One a9 and would like to reinstall the official ROM.
My questions:
a) The RUU provided by HTC is a file with exe extension. Do I have to convert to zip and then rename it?
b) When I "Reboot to Bootloader" (Download Mode doesn't work) and select "Boot Download Mode", HTC only says "SD Mounted" and goes back to the previous menu. My device didn't pick up the file
tominozh said:
Hi all, I am not sure if any of you is useing this method to RUU back your device but if you dont want to mess with fastboot and so on there is actually a very easy way to do it. the ony thing you need is RUU and sdcard.
1. rename RUU to 2PQ9IMG.zip
2. copy zip in the root of your sd card. - external card / not internal - it will not work
3. reboot to download mode, if for some reason you cant/are not able to/, reboot to bootloader and then select download mode
4. your device will pick up the zip file and flash it.
5.follow on screen instructions and enjoy your RUU-ed htc one a9
This method of flashing ruu is not new, it has been around for a while, just the name of the zip is always different.
I learned this when i had htc one S and htc one m8.
Click to expand...
Click to collapse

2nd attempt:
a) Downloaded HTC ROM Unlocked from official web page: RUU_PERFUME_WL_N70_SENSE80GP_MR_NA_Gen_Unlock_2.41.617.3.exe
b) Converted the file to zip and renamed to 2PQ9IMG.zip
c) Saved that file to SD Card
d) Power on + Vol Down
e) HTC Recognized SD Mounted >>> Vol Up to Start Flash
Results:
- Message "12 RU_ZIP_ERROR" :crying:
- Message "Fail12 RU_ZIP_ERROR" :crying:
tominozh said:
Hi all, I am not sure if any of you is useing this method to RUU back your device but if you dont want to mess with fastboot and so on there is actually a very easy way to do it. the ony thing you need is RUU and sdcard.
1. rename RUU to 2PQ9IMG.zip
2. copy zip in the root of your sd card. - external card / not internal - it will not work
3. reboot to download mode, if for some reason you cant/are not able to/, reboot to bootloader and then select download mode
4. your device will pick up the zip file and flash it.
5.follow on screen instructions and enjoy your RUU-ed htc one a9
This method of flashing ruu is not new, it has been around for a while, just the name of the zip is always different.
I learned this when i had htc one S and htc one m8.
Click to expand...
Click to collapse

Browniano said:
2nd attempt:
a) Downloaded HTC ROM Unlocked from official web page: RUU_PERFUME_WL_N70_SENSE80GP_MR_NA_Gen_Unlock_2.41.617.3.exe
b) Converted the file to zip and renamed to 2PQ9IMG.zip
c) Saved that file to SD Card
d) Power on + Vol Down
e) HTC Recognized SD Mounted >>> Vol Up to Start Flash
Results:
- Message "12 RU_ZIP_ERROR" :crying:
- Message "Fail12 RU_ZIP_ERROR" :crying:
Click to expand...
Click to collapse
To my understanding, the RUU exe file you downloaded is a tool to download the actual firmware onto the device and is not a zip that can be flashed in a straightforward manner.
Check https://forum.xda-developers.com/one-a9/general/wip-ruu-htc-one-a9-t3240344 for flashable RUU zips

i used the method of ruu via memory card but got an error like the picture, the device is now out of the boot loop logo, how to fix that problem, seems to have reported a sensor error

Save my bricked U12+ with the rom from another U12+?

So I've soft bricked my phone trying to downgrade android. I forgot to install TWRP and then flashed the ROM, only to discover I stupidly forgot to S OFF when I tried to flash an android 8 RUU. Because my phone is S ON I can't downgrade, and there is no stock android 9 RUU for me to flash back on. I was just going to send the phone to HTC for repairs when I had an idea, I have another HTC U12+ (same region some software as the original android 9). Can I not simply copy the ROM from this U12 and flash it onto my bricked U12? The working U12+ is on stock and is not rooted. I'd prefer not to root but am willing to if this will work. Can anyone let me know if this is possible or give any other advice? Btw if anyone has any other ideas on how to fix the bricked U12+ I'm open to suggestions. Thank you all.

wiliestseven51 said:
So I've soft bricked my phone trying to downgrade android. I forgot to install TWRP and then flashed the ROM, only to discover I stupidly forgot to S OFF when I tried to flash an android 8 RUU. Because my phone is S ON I can't downgrade, and there is no stock android 9 RUU for me to flash back on. I was just going to send the phone to HTC for repairs when I had an idea, I have another HTC U12+ (same region some software as the original android 9). Can I not simply copy the ROM from this U12 and flash it onto my bricked U12? The working U12+ is on stock and is not rooted. I'd prefer not to root but am willing to if this will work. Can anyone let me know if this is possible or give any other advice? Btw if anyone has any other ideas on how to fix the bricked U12+ I'm open to suggestions. Thank you all.
Click to expand...
Click to collapse
Hi,
If your U12 is S-on, why not iron it S-Off? Or is it not booting? It is not possible at the moment to copy a complete rom Pie, a backup will not have the party 'vendor' so will not work! Without S-Off impossible to flash a TWRP recovery and anyway it is necessary the base vendor of the same version! Or it will have to wait until a complete RUU sort for Pie !!

to research for myself ( see my other thread about strange things on my u12+) did the same thing today, reverted from pie to oreo
note that my phone is european dual sim and cid 034
i only unlocked it but it's still s-on so it's possible to downgrade with s-on and locked/unlocked
just follow this procedure and be sure to use an oreo RUU compatible with your phone ( single/dual sim, same cid etc ) and rename the ruu only leaving the first 7 digit and letter
take your time to download the file because it's slow and don't rush because I know the feeling as in one step I tought to have lost my phone too!
https://forum.xda-developers.com/u12-plus/how-to/downgrade-s-t3930103
note: i needed to flash the ruu in download mode from sdcard two times because the first didn't work, when working it will say that is impossible to boot, will ask to reset data, do that and good to go wait a bit after logo
i can guarantee it worked from 2.55 to 1.30 firmware so it was a giant leap back!

SIRKRA said:
to research for myself ( see my other thread about strange things on my u12+) did the same thing today, reverted from pie to oreo
note that my phone is european dual sim and cid 034
i only unlocked it but it's still s-on so it's possible to downgrade with s-on and locked/unlocked
just follow this procedure and be sure to use an oreo RUU compatible with your phone ( single/dual sim, same cid etc ) and rename the ruu only leaving the first 7 digit and letter
take your time to download the file because it's slow and don't rush because I know the feeling as in one step I tought to have lost my phone too!
https://forum.xda-developers.com/u12-plus/how-to/downgrade-s-t3930103
note: i needed to flash the ruu in download mode from sdcard two times because the first didn't work, when working it will say that is impossible to boot, will ask to reset data, do that and good to go wait a bit after logo
i can guarantee it worked from 2.55 to 1.30 firmware so it was a giant leap back!
Click to expand...
Click to collapse
Hi,
Yes all resume from the RUU '2Q55IMG_IMAGINE_DUGL_O80_SENSE10GP_HTC_Europe_1.53.401.5_Radio_sdm845-000201b-1807311356_release_532179_signed_2_4.zip' renamed to 2Q55IMG.zip copied to the sd.
Reinstalled all from the downloade mode.

SIRKRA said:
to research for myself ( see my other thread about strange things on my u12+) did the same thing today, reverted from pie to oreo
note that my phone is european dual sim and cid 034
i only unlocked it but it's still s-on so it's possible to downgrade with s-on and locked/unlocked
just follow this procedure and be sure to use an oreo RUU compatible with your phone ( single/dual sim, same cid etc ) and rename the ruu only leaving the first 7 digit and letter
take your time to download the file because it's slow and don't rush because I know the feeling as in one step I tought to have lost my phone too!
https://forum.xda-developers.com/u12-plus/how-to/downgrade-s-t3930103
note: i needed to flash the ruu in download mode from sdcard two times because the first didn't work, when working it will say that is impossible to boot, will ask to reset data, do that and good to go wait a bit after logo
i can guarantee it worked from 2.55 to 1.30 firmware so it was a giant leap back!
Click to expand...
Click to collapse
I've got the exact same phone/cid as you. So im trying to follow that thread but i cant install twrp. I've downloaded the latest version and tried previous versions (note my software version as shown in download mode is 1.30.401.2) and all i get in the command prompt is:
PS C:\Users\User\Downloads\platform-tools_r29.0.2-windows\platform-tools> .\fastboot boot twrp-3.2.3-1-ime.img
Sending 'boot.img' (31196 KB) OKAY [ 1.940s]
Booting
and then its stuck on that screen, the phone just says:
flash image success (1/1)
Start downloading.
What am i doing wrong? Secondly ADB commands no longer work, im guessing because of the device being bricked (i've tested on my other htc and adb works fine on that). Fastboot commands still work fine though.

Alan-B said:
Hi,
If your U12 is S-on, why not iron it S-Off? Or is it not booting? It is not possible at the moment to copy a complete rom Pie, a backup will not have the party 'vendor' so will not work! Without S-Off impossible to flash a TWRP recovery and anyway it is necessary the base vendor of the same version! Or it will have to wait until a complete RUU sort for Pie !!
Click to expand...
Click to collapse
It's soft bricked and not booting, i can still enter download mode/bootloader but if i try to boot it is just stuck on black boot screen with the HTC logo.

wiliestseven51 said:
I've got the exact same phone/cid as you. So im trying to follow that thread but i cant install twrp. I've downloaded the latest version and tried previous versions (note my software version as shown in download mode is 1.30.401.2) and all i get in the command prompt is:
PS C:\Users\User\Downloads\platform-tools_r29.0.2-windows\platform-tools> .\fastboot boot twrp-3.2.3-1-ime.img
Sending 'boot.img' (31196 KB) OKAY [ 1.940s]
Booting
and then its stuck on that screen, the phone just says:
flash image success (1/1)
Start downloading.
What am i doing wrong? Secondly ADB commands no longer work, im guessing because of the device being bricked (i've tested on my other htc and adb works fine on that). Fastboot commands still work fine though.
Click to expand...
Click to collapse
( adb commands works only when the phone is in android while fastboot when in download/bootloader so this is normal )
Download this ruu https://androidfilehost.com/?fid=11410932744536984886
Download this twrp https://eu.dl.twrp.me/ime/twrp-3.3.1-0-ime.img ( for now optional )
Rename the RUU in 2Q55IMG.zip
Place the RUU zip in Sdcard
Put the phone in Bootloader Mode, open cmd and type fastboot devices ( for now optional, is the phone recognized? , your pc has intel or amd cpu? )

Hi,
https://mega.nz/#!YxZUWa5I!9o1pOtRDgNvM8f-ZvW5xVji6bPRgUogd8Cm3JvrIGvk
RUU 1.53.401.5 ful
remame to 2Q55IMG.zip anc copy to sdcard max 32 giga
Switch to download mode
message in yellow then push volume +
follow the instructionsLet all settle down
PS, RUU to cid-34 an dual sim
SIRKRA !! No need for adb or others! just copy on the SD and go into downloade mode! no bootloade. (my version is newer!)

wiliestseven51 said:
So I've soft bricked my phone trying to downgrade android. I forgot to install TWRP and then flashed the ROM, only to discover I stupidly forgot to S OFF when I tried to flash an android 8 RUU. Because my phone is S ON I can't downgrade, and there is no stock android 9 RUU for me to flash back on. I was just going to send the phone to HTC for repairs when I had an idea, I have another HTC U12+ (same region some software as the original android 9). Can I not simply copy the ROM from this U12 and flash it onto my bricked U12? The working U12+ is on stock and is not rooted. I'd prefer not to root but am willing to if this will work. Can anyone let me know if this is possible or give any other advice? Btw if anyone has any other ideas on how to fix the bricked U12+ I'm open to suggestions. Thank you all.
Click to expand...
Click to collapse
I downgraded on pie, do a getvar see what the build number & cid mid, I was on 2.47.709.1 my build was 1.53.709.7 , I found the right ruu(1.53.709.7), then decryped it, put system image & boot image in adb file. Renamed the ruu 2Q55IMG flashed it from Sdcard (32gb or less) it hangs on boot up, pressing on off it restarts & boots eventually, then I adb reboot download getvar again to make sure a partition is active. Then flash the boot image on b, then the system on b, if it hangs on system just wait, there's a delay it might initially fail but let it run through ,as it can't flash the wholes system at once, it breaks it up, takes a couple of mins, restart, it update fine, I've done it three times, never bricked an HTC b4 lol

SOLVED
wiliestseven51 said:
So I've soft bricked my phone trying to downgrade android. I forgot to install TWRP and then flashed the ROM, only to discover I stupidly forgot to S OFF when I tried to flash an android 8 RUU. Because my phone is S ON I can't downgrade, and there is no stock android 9 RUU for me to flash back on. I was just going to send the phone to HTC for repairs when I had an idea, I have another HTC U12+ (same region some software as the original android 9). Can I not simply copy the ROM from this U12 and flash it onto my bricked U12? The working U12+ is on stock and is not rooted. I'd prefer not to root but am willing to if this will work. Can anyone let me know if this is possible or give any other advice? Btw if anyone has any other ideas on how to fix the bricked U12+ I'm open to suggestions. Thank you all.
Click to expand...
Click to collapse
Thanks everyone for the help. My U12+ is now unbricked and I'm back to running Android 8. You've all just saved me a ton of grief genuinely thank you.

wiliestseven51 said:
Thanks everyone for the help. My U12+ is now unbricked and I'm back to running Android 8. You've all just saved me a ton of grief genuinely thank you.
Click to expand...
Click to collapse
Glad to hear that your issue is resolved. I should have just flashed a RUU before trying to boot TWRP, I just didn't realize that I likely overwrote the bootloader on the RUU mode flash. Oh well.